diff options
| author | Pau Espin Pedrol <pespin@sysmocom.de> | 2021-09-27 12:01:14 +0200 |
|---|---|---|
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2021-09-29 15:39:17 +0200 |
| commit | 464227d07140f1da368198e1c008415856c5721b (patch) | |
| tree | 000c6cddd7bd55c50b8144e7d5b79013e6aff18f /doc | |
| parent | 1b90b3d27a2d93df232e247f11049ce089672af7 (diff) | |
MS Power Control Loop: Allow Turn off/on C/I independent from value setting
Improve the current VTY support to allow enabling/disabling C/I logic
independent from value setting. This way C/I support can be quickly
disabled & enabled.
Reminder: changing power parameters still require VTY Command "bts NR
resend-power-control-defaults" to be excuted prior to new parameters
being applied on the BTS.
Related: SYS#4917
Change-Id: Id1224c2d9a52db2ed805c49e048d3086ed0167f5
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manuals/chapters/power_control.adoc | 18 |
1 files changed, 11 insertions, 7 deletions
diff --git a/doc/manuals/chapters/power_control.adoc b/doc/manuals/chapters/power_control.adoc index bc112aadc..51a38cb87 100644 --- a/doc/manuals/chapters/power_control.adoc +++ b/doc/manuals/chapters/power_control.adoc @@ -33,6 +33,7 @@ ignore some of the received parameters due to incomplete implementation. On the other hand, OsmoBTS may support some extra parameters coming in Osmocom specific IEs not supported by nanoBTS, such as those configuring C/I measurement thresholds. +[[apply_pwr_ctrl]] ==== When the parameters come into effect? It depends on how the power control parameters are signaled to the BTS. If a given @@ -337,21 +338,24 @@ network bts 0 ms-power-control mode dyn-bts <1> - ci-thresh amr-fr lower 7 upper 11 <2> - ci-thresh-comp amr-fr lower 2 10 <3> upper 3 4 <4> + ci-thresh amr-fr enable <2> + ci-thresh amr-fr lower 7 upper 11 <3> + ci-thresh-comp amr-fr lower 2 10 <4> upper 3 4 <5> ---- <1> MS power control is to be performed by the BTS autonomously. -<2> L_CI_AMR_FR_XX_P=7, U_CI_AMR_FR_XX_P=11. -<3> P0=2 out of N1=10 averages < L_CI_AMR_FR_XX_P => increase power. -<4> P1=3 out of N2=4 averages > U_CI_AMR_FR_XX_P => decrease power. +<2> MS power control loop should take C/I into account. +<3> L_CI_AMR_FR_XX_P=7, U_CI_AMR_FR_XX_P=11. +<4> P0=2 out of N1=10 averages < L_CI_AMR_FR_XX_P => increase power. +<5> P1=3 out of N2=4 averages > U_CI_AMR_FR_XX_P => decrease power. NOTE: The BSC can instruct a BTS to disable C/I related logic in its autonomous MS Power Control Loop for a given channel type (hence not taking C/I measurements into account) by means of setting both related LOWER_CMP_N and UPPER_CMP_N parameters to zero (see _ci-thresh-comp_ VTY command). For the sake of easing configuration, a placeholder VTY command to disable C/I for all -channel types is available under VTY node _ms-power-control_ as *_ci-thresh-comp -disable all_*. +channel types is available under VTY node _ms-power-control_ as *_ci-thresh +all disable_*. Afterwards, the new configuration must be deployed to the target +BTS (see <<apply_pwr_ctrl>>). ==== Measurement averaging process |