Project

General

Profile

Feature #1573

ENHANCED MEASUREMENT REPORT

Added by laforge over 5 years ago. Updated 7 days ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
02/23/2016
Due date:
% Done:

0%

Spec Reference:

Description

We don't support this yet, neither the associated Bter frame format

Whether or not this message is needed is primarily dependent on whether
the BSC instructs the MS to use ENHANCED MEASUREMENT REPORT.

The same topic exists with EXTENDED MEAUSUREMENT REPORT / EXTENDED
MEASUREMENT ORDER.

OsmoBSC / OsmoNITB use neither, so it is not a requirement to OsmoBTS,
unless you want to use it with a different BSC.

History

#1 Updated by pespin 7 days ago

References:
  • 3GPP TS 45.008 version 13.0.0 Release 138.4.8 Enhanced Measurement Reporting
  • 3GPP TS 44.018 version 10.3.0 Release 10:
    • 3.4.1.2 Measurement Report and Enhanced Measurement Report
    • 9.1.55 ENHANCED MEASUREMENT REPORT
  • REPORTING_QUANTITY (6 bits): Measurement quantities are defined in 3GPP TS 45.008 (6 bits, it's actually RXLEV for GSM AFAIU).
  • BSIC Description, see sub-clause 3.4.1.2.1.2 ("Deriving the GSM Neighbour Cell list from the BSICs and the BA (list)").

Further interesting short snippets from spec summarizing the feature:

The Mobile Station shall use ENHANCED MEASUREMENT REPORT messages instead of MEASUREMENT REPORT messages if that is indicated by the parameter REPORT_TYPE and if at least one BSIC is allocated to each BA (list) frequency.

BSIC list received in one or more instances, in ascending order of SI2quater_INDEX, of the SI2quater message. When the BA_IND is changed the MS shall rebuild the combined list (the BSIC list shall also be rebuilt).

If GPRS BSIC Description is provided in the SI2quater message (see sub-clause 3.4.1.2.1.6), it shall be saved and used by a non-GPRS mobile station as initial BSIC information in connected mode.

So my understanding is that the "BSIC list" in SI2quater is actually the field defined as "GPRS BSIC Description", which is used also for non-GPRS purposes.

Here's what's needed in order to support EMR in both osmo-bts and osmo-bsc:

  • Set "MEASUREMENT PARAMETERS=>REPORT_TYPE" in SI2quater Rest Octets to 1 (or make it configurable via VTY)
  • Make sure we send EMR BSIC list in either SI2quater or SI2n (Hardcoded "0" in osmo_gsm48_rest_octets_si2quater_encode, pass list in osmo-bsc)
  • osmo-bts: Support parsing Enhanced Measurement Reporting packet & forarding: add support in rslms_is_meas_rep() and lchan_bs_pwr_ctrl() (and repeated_dl_facch_active_decision() too?), other stuff should be fine, since it's mostly forwarding l3 which is transparent to BTS
  • osmo-bsc: Feeding information from Enhanced Measurement Reporting into existing measurement infrastructure: add support in rsl_rx_meas_res (add new function like gsm48_parse_meas_rep()), add support in dispatch_dtap()

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)