diff options
| author | Vadim Yanitskiy <vyanitskiy@sysmocom.de> | 2020-11-26 21:21:45 +0100 |
|---|---|---|
| committer | Vadim Yanitskiy <vyanitskiy@sysmocom.de> | 2020-12-06 18:57:43 +0100 |
| commit | 0698c58ebe1f0e196240dab152f413759c47feb9 (patch) | |
| tree | a886ca56462cf34999ac9aec09c708edc521174e /.gitignore | |
| parent | 0ced8dd03e1eac2e2dbffbbd0a5f86feeac8ca67 (diff) | |
power_control: implement BS (Downlink) Power Control
We already have MS Power Control, which according to 3GPP 45.008
shall be implemented in the MS to minimize the transmit power in
the Uplink direction. The BS Power Control may optionally be
implemented by the network side for the same purpose.
Using Downlink signal measurements reported by the MS, the BSS
(either BSC, or BTS) may control Downlink attenuation in a way
that the transmit power remains as low as possible, or remains
in a specific range corresponding to good RxLev values on the
MS side. This change implements autonomous BS Power Control,
that can optionally be enabled by the BSC.
BS Power Control re-uses parts of the MS Power Control code,
so all parameters can be configured in the same way - via the
VTY interface or a configuration file. This basically means
that features like hysteresis and EWMA based filtering are
also available for BS Power Control.
The only difference is that RxQual values higher than 0 would
trigger the logic to reduce the current attenuation twice.
Note that one of the unit tests ('TC_rxlev_max_min') fails,
as the power step limitations for raising and lowering look
wrong to me, and the related discussion is still ongoing.
Change-Id: I5b509e71d5f668b6b8b2abf8053c27f2a7c78451
Related: SYS#4918
Diffstat (limited to '.gitignore')
| -rw-r--r-- | .gitignore | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -64,6 +64,7 @@ tests/handover/handover_test tests/tx_power/tx_power_test tests/ta_control/ta_control_test tests/power/ms_power_loop_test +tests/power/bs_power_loop_test tests/testsuite tests/testsuite.log |