Feature #3054
open
Extended (11-bit) RACH support in OsmoTRX
Added by laforge about 6 years ago.
Updated about 5 years ago.
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 */
- Related to Bug #1854: 11-bit RACH support breaks default 8-bit RACH: collisions are possible added
- Has duplicate Bug #1834: Extended (11-bit) RACH is not properly handled added
- 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
- Related to Bug #1548: 11bit RACH support added
- Has duplicate deleted (Bug #1834: Extended (11-bit) RACH is not properly handled)
- Related to Bug #1834: Extended (11-bit) RACH is not properly handled added
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.
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.
Also available in: Atom
PDF