OsmoBTS power control incompliant to TS 05.08 and TS 08.58
The way how OsmoBTS interprets the A-bis RSL information elements regarding MS and BS power control is wrong.
For a description of the current behavior, see http://openbsc.osmocom.org/trac/wiki/GsmPowerControl
Furthermore, even the actual power control loop is completely simplistic, results in oscillations and doesn't implement any of the configurable averaging as specified in TS 05.08.
What needs to be done is:
correctly parse and interpret the various MS / BS power related IEs on RSL
implement Annex A of TS 05.08 (measurement averaging, MS power control)
- fix behavior on BSC side (always send MS power parameters in RSL CHAN ACT)
- fix behavior on BTS side: autonomous UL power control ony if MS power parametrs IE was sent
- TTCN3 tests for static MS power level in RSL CHAN ACT
- TTCN3 tests for static MS power level in MS POWER CONTROL
- TTCN3 test for autonomous MS power control after RSL CHAN ACT
- TTCN3 test for autonomous MS power control after MS POWER CONTROL
- Ensure the ms power level is actually interpreted as the maximum allowable power level if a ms power parameters IE is present
See src/osmo-bts-trx/loops.c, where 'ms_power_diff()' computes
the difference between the MS receive power target value and store it in
Admittedly, loops.c is one of the parts of the osmo-bts code bases that are rather hard to read and of bad structure. See #1851 for another related issue to generalize and refactor those loops, particularly also across BTS models.
The code in src/common/l1sap.c:l1sap_ph_rts_ind() then patches this value
into the L1 header of every downlink SACCH block:
p0 = lchan->ms_power_ctrl.current
Since the function that sets the MS power level bts_model_adjst_ms_pwr() is
a stub. This function is called by power_control.c and by rsl.c when the
BSC wants to set the MS power level via an MS POWER CONTROL message.
Yes, but the very same function also changes lchan->ms_power_ctrl.current
before. As osmo-bts-trx automatically uses that value during every DL SACCH
transmission, I would actually expect it to work.
The explicit bts_model_adjst_ms_pwr() function is just required for proprietary
PHYs that have their own TDMA scheduler and maintain that state in the PHY,
where hence we have to actively tell the PHY that the MS power level has changed.
So the first step from my point of view is to implement tests for this in BTS_Tests.ttcn,
considering cases like:
- MS POWER IE present in RSL CHAN ACT
- MS POWER IE being sent using a "RSL MS POWER CONTROL" message for an already-active
and then running those tests with OsmocomBB against osmo-bts-trx, osmo-bts-sysmo, etc.
From my reading of the code, the feature "static MS power control" is looking for should already work if the level is communicated via the RSL MS POWER CONTROL message, and not via the RSL CHANNEL ACTIVATE, as the former is setting lchan->ms_power_ctrl.fixed = 1 where the latter is setting it to 0. Having TTCN3 tests for this would allow us to ascertain this for sure and ensure it keeps working.
There is now a TTCN3 test that sends RSL MS POWER CONTROL and simultaneously checks that the L1 header of the SACCH channel contains the expected power level. From what I can see so far in the tests the external power control should work fine.
- Checklist item fix behavior on BSC side (always send MS power parameters in RSL CHAN ACT) added
- Checklist item fix behavior on BTS side: autonomous UL power control ony if MS power parametrs IE was sent added
- Checklist item TTCN3 tests for static MS power level in RSL CHAN ACT added
- Checklist item TTCN3 tests for static MS power level in MS POWER CONTROL added
- Checklist item TTCN3 test for autonomous MS power control after RSL CHAN ACT added
- Checklist item TTCN3 test for autonomous MS power control after MS POWER CONTROL added
- % Done changed from 0 to 20
- if the optional MS power parameters IE is present (we don't care about contents), the BTS performs MS power control autonomously
- if the optional MS power parameters IE is absent, we switch to static MS power according to the MS Power IE.
- Checklist item Ensure the ms power level is actually interpreted as the maximum allowable power level if a ms power parameters IE is present added
As the spec states "If the MS Power Parameters element is present it indicates that the MS power control is to be performed by TRX. The MS Power element then indicates the maximum MS power to be used. "
This is currently not working at all, the loop will just ignore this maximum ms power.