Feature #1569: Report RF interference levels as part of RF RESOURCE INDICATION - OsmoBTS - Open Source Mobile Communications

Report RF interference levels as part of RF RESOURCE INDICATION

Added by laforge almost 8 years ago. Updated over 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

fixeria

Category:

Target version:

Start date:

02/23/2016

Due date:

% Done:

100%

Spec Reference:

3GPP TS 48.058 Ch. 6.1 and 8.6.1

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.

Hide closed

Checklist

BTS side implementation
TTCN3 tests in BTS_Tests.ttcn (see #3750)

Related issues

Actions

Copy link

Updated by laforge about 7 years ago

Actions

Copy link

Updated by laforge about 7 years ago

Spec Reference set to 3GPP TS 48.058 Ch. 6.1 and 8.6.1

Actions

Copy link

Updated by laforge about 7 years ago

Related to Feature #1866: Make use of RSL RF RESOURCE INDICATION (interference measurements) added

Actions

Copy link

Updated by laforge almost 7 years ago

Assignee set to dexter

Actions

Copy link

Updated by pespin almost 6 years ago

Related to Bug #2735: Malformed RF RESource INDication added

Actions

Copy link

Updated by laforge over 5 years ago

Priority changed from Normal to Low

Actions

Copy link

Updated by fixeria about 5 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...

Actions

Copy link

Updated by Hoernchen over 4 years ago

Related to Feature #3750: Extension of BTS_Tests.ttcn test coverage added

Actions

Copy link

Updated by Hoernchen over 4 years ago

Related to Feature #4006: TRX protocol: wind of change added

Actions

Copy link

#10

Updated by laforge over 4 years ago

Assignee deleted (~~dexter~~)

Actions

Copy link

#11

Updated by laforge over 3 years ago

Checklist item BTS side implementation added
Checklist item TTCN3 tests in BTS_Tests.ttcn (see #3750) added

let's implement tests within the scope of this issue, allows us to resolve #3750

Actions

Copy link

#12

Updated by fixeria over 2 years ago

Status changed from New to In Progress
Assignee set to fixeria
Priority changed from Low to Normal

Actions

Copy link

#13

Updated by fixeria over 2 years ago

Checklist item BTS side implementation set to Done
% Done changed from 0 to 80

From what I can see in Wireshark, my implementation seems to work:

https://gerrit.osmocom.org/c/osmo-bts/+/24612 Report interference levels in RSL RF RESource INDication [NEW]
https://gerrit.osmocom.org/c/osmo-bts/+/24613 osmo-bts-trx: report interference levels to the upper layers [NEW]

Actions

Copy link

#14

Updated by fixeria over 2 years ago

I also implemented a TTCN-3 test case:

https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/24567 BTS: add a test case for RF RESource INDication [WIP]

However, I somehow need to make fake_trx.py send NOPE indications with a certain RSSI values. Currently this is not supported: we don't have NOPE indications in our virtual Um environment at all. I'll investigate the easiest way to implement this.

Actions

Copy link

#15