Project

General

Profile

Actions

Feature #2977

open

OsmoBTS measurment processing at L1SAP too complex / pass measurements along with data

Added by laforge almost 4 years ago. Updated over 1 year ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/21/2018
Due date:
% Done:

80%

Spec Reference:

Description

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.


Files

notes.txt notes.txt 5.18 KB dexter, 01/21/2019 03:25 PM
notes.txt notes.txt 7.12 KB dexter, 01/23/2019 12:51 PM

Checklist

  • osmo-bts-trx
  • osmo-bts-sysmo
  • osmo-bts-litecell15
  • osmo-bts-oc2g
  • osmo-bts-virtual (?)

Related issues

Related to OsmoBTS - Bug #3032: (Wrong?) measurement of both RSSI and ToA on TCH channelsResolvedfixeria03/05/2018

Actions
Related to OsmoBTS - Bug #2975: OsmoBTS doesn't generate measurement indications in absence of uplink burstsResolveddexter02/21/2018

Actions
Related to OsmoBTS - Feature #3530: merge PRIM_INFO_MEAS into PRIM_PH_DATA and PRIM_TCHRejecteddexter09/06/2018

Actions
Related to OsmoBTS - Feature #3428: Implement handling of NOPE / IDLE indications from TransceiverResolveddexter07/28/2018

Actions
Related to OsmoPCU - Bug #3395: Uplink CS/MCS control is broken osmo-pcu is used with osmo-bts-trx/osmo-trxResolvedpespin07/14/2018

Actions
Related to OsmoPCU - Feature #1526: Acquire/update timing advance (TA)Stalledfixeria02/22/2016

Actions
Related to OsmoBTS - Bug #3803: fix frame number calculation in scheduler_trxResolveddexter02/15/2019

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)