Project

General

Profile

Actions

Feature #1752

closed

Improve RACH detection / rejection

Added by laforge almost 8 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
06/14/2016
Due date:
% Done:

100%

Spec Reference:

Description

The current RACH burst detection/rejection logic in osmo-bts is quite sub-optimal.

At least for osmo-bts-sysmo and osmo-bts-lc15, we currently only have a threshold based on the fLinkQuality parameter.

However, there is no threshold based on the RSSI, and particularly none on the BER.

According to some theoretical analysis, it seems like a good choice for the BER threshold is "7/41", i.e. 7 out of the 41 bits of the RACH training sequence can be wrong, but 35bits should be correct.

To quote from Martin Kollár: METHOD FOR EVALUATION OF OUTAGE PROBABILITY ON RANDOM ACCESS CHANNEL IN MOBILE COMMUNICATION SYSTEMS

the theoretical BER limits of GMSK and BPSK based on Eb/N0 = 0 dB, the BER of
GMSK is 0.16. For the GSM where 41 represent the total number of bits in a 
RACH synchronization sequence this corresponds to ratio 7/41. So the threshold
k can be set to 7.

So we should have a configurable but default fBER limit of 7/41 = 0.17073170

It probably makes sense to pass BER, Link Quality and RSSI up into the common part via L1SAP, and
have the thersholds implemented there. This ensures uniform behavior accross hardware.


Files

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)