Changes
Started by upstream project gerrit-osmo-ttcn3-hacks #3888
Started 1 day 1 hr ago
Queued 6.3 sec
Took 37 sec
on built-in
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
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