Project

General

Profile

Actions

Feature #3054

open

Extended (11-bit) RACH support in OsmoTRX

Added by laforge over 3 years ago. Updated almost 3 years ago.

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

90%

Spec Reference:

Description

OsmoTRX is currently only correlating with one of the three RACH sync sequences indicated in TS 05.02 5.2.7. We need to define TS1+TS2 as well as correlated against thosee during RACH detection

 const BitVector GSM::gRACHSynchSequence("01001011011111111001100110101010001111000");
+const BitVector GSM::gRACHSynchSequenceTS1("01010100111110001000011000101111001001101");       /* EGPRS with 8PSK in uplink */
+const BitVector GSM::gRACHSynchSequenceTS2("11101111001001110101011000001101101110111");       /* EGPRS without 8PSK in uplink */

Checklist

  • sigProcLib: introduce both TS1 and TS2 RACH synch. sequences
  • sigProcLib: add a CorrType for extended (11-bit) RACH
  • Distinguish handover RACH
  • Extend TRXC interface

Related issues

Related to OsmoBTS - Bug #1854: 11-bit RACH support breaks default 8-bit RACH: collisions are possibleResolvedfixeria11/18/2016

Actions
Related to OsmoPCU - Bug #1548: 11bit RACH supportResolvedfixeria02/23/2016

Actions
Related to OsmoPCU - Bug #1834: Extended (11-bit) RACH is not properly handledClosedmsuraev10/25/2016

Actions
Related to Cellular Network Infrastructure - Feature #4006: TRX protocol: wind of changeStalledfixeria05/17/2019

Actions
Actions #1

Updated by laforge over 3 years ago

  • Related to Bug #1854: 11-bit RACH support breaks default 8-bit RACH: collisions are possible added
Actions #2

Updated by fixeria about 3 years ago

  • Has duplicate Bug #1834: Extended (11-bit) RACH is not properly handled added
Actions #3

Updated by laforge about 3 years ago

  • Assignee set to tnt
Actions #4

Updated by fixeria about 3 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from 11bit RACH support in OsmoTRX to Extended (11-bit) RACH support in OsmoTRX
  • Status changed from New to Feedback
  • % Done changed from 0 to 80

Initial work has already been done, please see:

https://gerrit.osmocom.org/11390/ sigProcLib: introduce both TS1 and TS2 RACH synch. sequences
https://gerrit.osmocom.org/11422/ sigProcLib: add a CorrType for extended (11-bit) RACH
https://gerrit.osmocom.org/11423/ VTY: add extended (11-bit) RACH detection toggle

Actions #5

Updated by msuraev about 3 years ago

  • Related to Bug #1548: 11bit RACH support added
Actions #6

Updated by msuraev about 3 years ago

  • Has duplicate deleted (Bug #1834: Extended (11-bit) RACH is not properly handled)
Actions #7

Updated by msuraev about 3 years ago

  • Related to Bug #1834: Extended (11-bit) RACH is not properly handled added
Actions #8

Updated by msuraev almost 3 years ago

All except gerrit 11423 are merged already. There's still room for improvements on top of that to avoid extended RACH detection when we know for sure it's not going to arrive (HO case etc) before we can enable vty option from 11423 by default.

Actions #9

Updated by fixeria almost 3 years ago

  • Checklist item sigProcLib: introduce both TS1 and TS2 RACH synch. sequences added
  • Checklist item sigProcLib: add a CorrType for extended (11-bit) RACH added
  • Checklist item Distinguish handover RACH added
  • Checklist item Extend TRXC interface added
  • Status changed from Feedback to Stalled
  • % Done changed from 80 to 90

Since I1aee998d83b06692d76a83f79748f9129a2547e8 is merged, OsmoTRX can now be instructed to enable the both TS1 and TS2 sequences. There is still some room for (performance) improvements though. As suggested by Harald, we can extend the TRXC (TRX Control) interface in order to be able to indicate whether to enable TS1/TS2 detection on a given timeslot.

Actions #10

Updated by fixeria over 2 years ago

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)