Feature #1569
Report RF interference levels as part of RF RESOURCE INDICATION
0%
Description
This means that the BSC does not have any information about the interference level within each (unused) timeslot of the given BTS.
Such interference is typically created by surrounding cells at some distance, which use the same frequency (frequency reuse) as the current cell.
OpenBSC currently doesn't use this information, but in an actual macro network deployment with high cell and frequency reuse density, the channel allocator in the BSC should prioritize assignment of new channels to thos with the least interference.
Checklist
- BTS side implementation
- TTCN3 tests in BTS_Tests.ttcn (see #3750)
Related issues
History
#1 Updated by laforge about 4 years ago
#2 Updated by laforge about 4 years ago
- Spec Reference set to 3GPP TS 48.058 Ch. 6.1 and 8.6.1
#3 Updated by laforge about 4 years ago
- Related to Feature #1866: Make use of RSL RF RESOURCE INDICATION (interference measurements) added
#4 Updated by laforge almost 4 years ago
- Assignee set to dexter
#5 Updated by pespin about 3 years ago
- Related to Bug #2735: Malformed RF RESource INDication added
#6 Updated by laforge over 2 years ago
- Priority changed from Normal to Low
#7 Updated by fixeria over 2 years ago
AFAIU, OsmoTRX actually does the noise measurements on UL:
https://git.osmocom.org/osmo-trx/tree/Transceiver52M/Transceiver.cpp#n929
but, as one can see, noise level is not being forwarded towards the BTS...
#8 Updated by Hoernchen over 1 year ago
- Related to Feature #3750: Extension of BTS_Tests.ttcn test coverage added
#9 Updated by Hoernchen over 1 year ago
- Related to Feature #4006: TRX protocol: wind of change added
#10 Updated by laforge over 1 year ago
- Assignee deleted (
dexter)
