aboutsummaryrefslogtreecommitdiffstats
path: root/include/osmocom/bsc
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2021-09-13 17:35:31 +0200
committerPau Espin Pedrol <pespin@sysmocom.de>2021-09-13 17:48:48 +0200
commit8367411772647ed7d10b57dee8acd706934740a0 (patch)
tree2f09f8289026e4f49ac3580735a87d329b190f1d /include/osmocom/bsc
parent506aa70d77cf4dfef92a7d9cb19ccb71e877d708 (diff)
Power Control Loop: Set P_CON_INTERVAL to 1 by default
TS 45.008 section 4.7.1: """ Upon receipt of a command from an SACCH to change its power level on the corresponding uplink channel, the MS shall change to the new level at a rate of one nominal 2 dB power control step every 60 ms (13 TDMA frames), i.e. a range change of 15 steps should take about 900 ms. The change shall commence at the first TDMA frame belonging to the next reporting period (as specified in subclause 8.4). The MS shall change the power one nominal 2 dB step at a time, at a rate of one step every 60 ms following the initial change, irrespective of whether actual transmission takes place or not. """ Since the reported MS_PWR in L1 SACCH Header is, according to specs, the one used for the last block of the previous SACCH period, it becomes clear the first SACCH block after a requested MS Power Level change by the network may contain mismatches between the announced MS_PWR by the MS and the measured Rxlev/RxQual. Hence, let's better use a P_CON_INTERVAL of 1 which retriggers the MS Power Control Loop every second SACCH block. Related: SYS#5371 Change-Id: Iade5b597e0e56b07c6d78995fcec7c641e4e643f
Diffstat (limited to 'include/osmocom/bsc')
0 files changed, 0 insertions, 0 deletions