diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2021-07-08 06:45:37 +0200 |
|---|---|---|
| committer | laforge <laforge@osmocom.org> | 2021-07-16 16:04:18 +0000 |
| commit | 9c61446423d6aea9391ff7de54ea69ecba5a21ad (patch) | |
| tree | 2f09f27aeb7d77e7edf9c37d1e8f101af01b44fd /tests/interf_meas.vty | |
| parent | ae0b737c62e4f8953dc64b67515fff5f2b330fea (diff) | |
vty 'interference-meas level-bounds': explain duality in ordering
Related: SYS#5313
Change-Id: If71e20e95d29e7f03739ee04e1ef429bf8bd51ed
Diffstat (limited to 'tests/interf_meas.vty')
| -rw-r--r-- | tests/interf_meas.vty | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/interf_meas.vty b/tests/interf_meas.vty index 76b33e56d..c6d8fb4e9 100644 --- a/tests/interf_meas.vty +++ b/tests/interf_meas.vty @@ -12,7 +12,7 @@ OsmoBSC(config-net-bts)# interference-meas? interference-meas Interference measurement parameters OsmoBSC(config-net-bts)# interference-meas ? avg-period Averaging period (Intave) - level-bounds Interference level Boundaries + level-bounds Interference level Boundaries. 3GPP do not specify whether these should be in ascending or descending order (3GPP TS 48.058 9.3.21 / 3GPP TS 52.021 9.4.25). OsmoBSC supports either ordering, but possibly some BTS models only return meaningful interference levels with one specific ordering. OsmoBSC(config-net-bts)# ### Averaging period OsmoBSC(config-net-bts)# interference-meas avg-period ? |