aboutsummaryrefslogtreecommitdiffstats
path: root/src/common/l1sap.c
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2017-12-02 21:34:33 +0100
committerHarald Welte <laforge@gnumonks.org>2017-12-04 13:25:34 +0000
commit70c4dc8d706973c65e6bf088156f5862f4e036b4 (patch)
tree52b2afb28a49d7be2c2b967eb3ab604f818fcdb1 /src/common/l1sap.c
parentbe4a2088098a7b4fbfc1a5046e4c2ceb21ce1b1d (diff)
osmo-bts-trx: Fix reported frame number during PRIM_INFO_MEAS
The upper layers (L1SAP, the common part of L1) *always* require frame numbers in the uplink direction to be reported as the frame number of the *first* burst, not the last burst of a given block. This is particularly important in the case of passing up measurement information, as we use this frame number to detect if the measurement interval for that specific timeslot has just ended (and hence we must process the measurements and send an uplink measurement report to the BSC. Before this patch, the measurement results were reported with the *last* frame number, which caused the common/measurement.c code never detect the end of a measurement window. On TS2, tons of the following log messages were observed: <0004> measurement.c:199 (bts=0,trx=0,ts=2,ss=0) no space for uplink measurement, num_ul_meas=104 With this patch, it behves as expected: the measurements of 25 blocks (= 100 bursts) are aggregated, after which point the report is computed and sent. Subsequently, num_ul_meas is reset to 0 and the cycle restarts. Related: OS#2329 Change-Id: I1065ae9c400bb5240a63ab8213aee59aeb9ceeff
Diffstat (limited to 'src/common/l1sap.c')
0 files changed, 0 insertions, 0 deletions