Project

General

Profile

Feature #1854

11bit RACH support in osmo-bts-trx

Added by laforge over 2 years ago. Updated 25 days ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
osmo-bts-trx
Target version:
Start date:
11/18/2016
Due date:
% Done:

50%

Spec Reference:

Description

osmo-bts-trx currently can only do 8bit RACH, unlike other BTS models


Related issues

Related to OsmoPCU - Bug #1548: 11bit RACH supportStalled2016-02-23

Related to OsmoTRX - Feature #3054: Extended (11-bit) RACH support in OsmoTRXStalled2018-03-10

History

#1 Updated by laforge over 1 year ago

  • Assignee set to msuraev

#2 Updated by msuraev over 1 year ago

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

#3 Updated by msuraev over 1 year ago

  • Status changed from New to In Progress

Encoding/decoding support for 11-bit RACH for libosmocoding is available in gerrit 5062.

#4 Updated by msuraev over 1 year ago

  • % Done changed from 0 to 10

Support was merged to libosmocoding. README update is in gerrit 5833. The next step is to implement it in osmo-bts-trx and test.

#5 Updated by msuraev about 1 year ago

  • Status changed from In Progress to Stalled

#6 Updated by msuraev about 1 year ago

The tests with gerrit 6315 is not working with current master of omopcu. We should re-test with sysmobts andimplement missing pieces.

#7 Updated by laforge about 1 year ago

  • Assignee changed from msuraev to sysmocom

#8 Updated by laforge about 1 year ago

  • Related to Feature #3054: Extended (11-bit) RACH support in OsmoTRX added

#9 Updated by laforge about 1 year ago

Please note not even OsmoTRX currently has support for this, see #3054

#10 Updated by laforge 6 months ago

  • Assignee changed from sysmocom to msuraev

#12 Updated by msuraev about 2 months ago

  • Status changed from Stalled to In Progress
  • % Done changed from 10 to 40

After merging https://gerrit.osmocom.org/c/osmo-bts/+/6315 and corresponding https://gerrit.osmocom.org/c/osmo-trx/+/11423 and related OsmoTRX patches there's TTCN-3 failure in TC_rach_content() and TC_rach_count() due to some (about 16 out of 1000) RACH being "lost". So far I'm unable to reproduce this using real phone. I'm not sure yet what's so special about the lost RACH (e. g. '0xCF') which makes a difference or whether rach content itself has anything to do with it at all. Investigation is ongoing.

The error constantly appears only with '0xCF', '0xBE' and '0x00' RA values for different FN.

#13 Updated by msuraev 25 days ago

  • Status changed from In Progress to Stalled
  • % Done changed from 40 to 50

Related https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/13128 might be useful for local testing.
Once the issue is fixed, https://gerrit.osmocom.org/c/osmo-bts/+/5833 should be merged as well.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)