aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2021-10-04 17:25:11 +0200
committerpespin <pespin@sysmocom.de>2021-10-07 10:47:00 +0000
commit3c32cce0870b883663b7d3e8b0f2c313f736ac84 (patch)
tree91c2975c2b4d5e56e1ea0baec3fdb4fe726d2acb /include
parent77e014f0612960c1b2cf04401a726362cae962c4 (diff)
MS Power Control Loop: Use P_CON_INTERVAL=2 by default
Have a more stable loop with less temporary oscillations at the expense of increased reaction time. 4 SACCH blocks (P_CON_INTERVAL=2) is the minimum interval to get stable measurements for the last requested MS Power level. With P_CON_INTERVAL=1, are also made during a period with stable power being use to transmit, but the MS Power level used (and announced in MR) is not the last one requested by the BTS, but the one requested in the previous loop iteration. This can make the MS and BTS bounce 2 values forth and back, and create some temporary oscillation. See osmo-bsc User manual section "Power Control" for more information. Related: SYS#5371 Change-Id: I91c505447f68714239a4f033d4f06e91893df201
Diffstat (limited to 'include')
-rw-r--r--include/osmo-bts/gsm_data.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/osmo-bts/gsm_data.h b/include/osmo-bts/gsm_data.h
index b73df5f6..8ae36ca1 100644
--- a/include/osmo-bts/gsm_data.h
+++ b/include/osmo-bts/gsm_data.h
@@ -223,6 +223,7 @@ struct gsm_power_ctrl_params {
/* Default MS/BS Power Control parameters */
extern const struct gsm_power_ctrl_params power_ctrl_params_def;
+void power_ctrl_params_def_reset(struct gsm_power_ctrl_params *params, bool is_bs_pwr);
/* Measurement pre-processing state */
struct gsm_power_ctrl_meas_proc_state {