fixeria has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/42127?usp=email )
Change subject: bts: as_rsl_meas_res(): tolerate low RxLev in early reports ......................................................................
bts: as_rsl_meas_res(): tolerate low RxLev in early reports
The MS is not guaranteed to begin transmitting immediately after activation of the respective logical channel. There is typically a short interval during which the BTS receives no bursts. Consequently, the initial RSL measurement reports are expected to indicate poor RxLev/RxQual values.
We already tolerate bad RxQual values; however, sporadic failures still occur due to low RxLev in the very first report. Extend the logic in f_build_meas_res_tmpl() to tolerate low RxLev as well.
Change-Id: Ic632917d429ec597dba524bf79749944cf1fc628 Related: 8ce558dd ("bts: as_rsl_meas_res(): tolerate bad RxQual in early reports") Related: OS#6933 --- M bts/BTS_Tests.ttcn 1 file changed, 4 insertions(+), 2 deletions(-)
Approvals: pespin: Looks good to me, but someone else must approve osmith: Looks good to me, approved Jenkins Builder: Verified
diff --git a/bts/BTS_Tests.ttcn b/bts/BTS_Tests.ttcn index 9646df4..54238f5 100644 --- a/bts/BTS_Tests.ttcn +++ b/bts/BTS_Tests.ttcn @@ -2315,9 +2315,11 @@ rxq_s_u := f_tolerance(l1p.meas_ul.sub.rxqual, 0, 7, mp_tolerance_rxqual), supp_meas_info := omit }; - /* Bit errors are expected during early stage of channel establishment. - * Ignore bad RxQual in the very first reports (4 * 0.480s = 1.92s). */ + /* Low signal and bit errors are expected during early stage of channel establishment. + * Ignore bad RxLev/RxQual in the very first reports (4 * 0.480s = 1.92s). */ if (g_rsl_meas_res_nr < 4) { + ul_meas.rxlev_f_u := ?; + ul_meas.rxlev_s_u := ?; ul_meas.rxq_f_u := ?; ul_meas.rxq_s_u := ?; }