Project

General

Profile

Bug #2975

OsmoBTS doesn't generate measurement indications in absence of uplink bursts

Added by laforge 3 months ago. Updated 3 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
osmo-bts-trx
Target version:
-
Start date:
02/21/2018
Due date:
% Done:

0%

Spec Reference:

Description

If there are no uplink bursts received (but timestamp indications sent) from OsmoTRX, osmo-bts-trx doesn't appear to generate RSL MEAS REP messages at every SACCH multiframe (103 frames), as expected. Odd.


Related issues

Related to OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCH Resolved 02/19/2018
Related to OsmoBTS - Bug #2987: OsmoBTS RxQual/RxLev averaging broken if bursts are missign New 02/23/2018

History

#1 Updated by laforge 3 months ago

  • Related to Bug #2965: No measurement reports sent for channels other than TCH added

#2 Updated by laforge 3 months ago

The entire measurement computation + reporting process is driven by lchan_meas_check_compute(), which is only called from the l1sap whenever a PRIM_INFO_MEAS is reported up. In absence of bursts/blocks, this primitive is not reported and subsequently no measurement reports are generated.

What we should do instead is track the frame number and whenever the SACCH multiframe ends, we should trigger a RSL MEAS REP. the missing uplink bursts all have to count as erroneous, i.e. 100% bit errors.

The entire dualism of PH_DATA.ind / PH_TCH.ind containg (unsued) measurement data, but then having a separate PRIM_INFO_MEAS is odd to begin with. The measurements should always accompany the PH-DATA.ind / PH-TCH.ind and PRIM_INFO_MEAS should be abandoned.

#3 Updated by laforge 3 months ago

  • Status changed from New to In Progress

#4 Updated by laforge 3 months ago

#5 Updated by laforge 3 months ago

#6 Updated by laforge 3 months ago

  • Related to Bug #2987: OsmoBTS RxQual/RxLev averaging broken if bursts are missign added

Also available in: Atom PDF