03 HW1 Parameters Analysis Guideline - WCDMA Power Control v1.5.1
03 HW1 Parameters Analysis Guideline - WCDMA Power Control v1.5.1
Development Project
1 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Huawei WCDMA Power Control
Algorithm and Parameters
26-09-2017
2 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
• Overview of Power Control
• Open Loop Power Control
• Closed Loop Power Control
• Enhancement
3 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Overview of Power Control
4 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Overview of WCDMA Power Control
WCDMA system is an interference-limited system, and the most important way to restrain system interference is power control. The
main purpose of power control is to minimize the power of transmitting signals while ensuring Quality of Service (QoS).
On the uplink, an UE emitting too high power will cause unacceptable competing interference on the NodeB in comparison to signals
coming from UEs at the cell edge. This is called near-far effect. To avoid near-far effect, uplink power control is required.
On the downlink, the system capacity is determined by the total code power. Therefore, it is necessary to keep the transmit power at
the lowest possible level while still ensuring signal quality at the UE.
During the open loop power control, the initial transmit power is calculated. This method is rather inaccurate and it is only applied at
the beginning of a connection setup.
During the closed loop power control, the transmitter dynamically adjusts its transmit power according to the feedback from the
receiver of the other side. Closed loop power control is further classified into following types:
• Inner loop power control directly adjusts the transmit power of the transmitter by using power control commands.
• Outer loop power control indirectly controls the transmit power of the transmitter.
5 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Purpose of Uplink Power Control
Uplink power control can guarantee the service quality and minimize the required transmission power. It will resolve the near-far
effect and resist fading of signal propagation. Reducing uplink interference level will increase the system capacity.
6 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Purpose of Downlink Power Control
Downlink power control can also guarantee the service quality and minimize the required transmission power, so the
capacity is maximized while interference is lowered.
7 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Power Control Types
Power control is classified into following types
based on channel types:
• Common Channel Power Control
• DCH Channel Power Control
• HSDPA Power Control
• HSUPA Power Control
8 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Channel Power Control
The common channels include the uplink common channel and downlink common channel.
The uplink channel includes the PRACH, whereby open loop power control is used.
The fixed power or power offset is used on the downlink channels as listed below:
• Primary Common Pilot Channel (P-CPICH)
• Primary Synchronization Channel (P-SCH)
• Secondary Synchronization Channel (S-SCH)
• Primary Common Control Physical Channel (P-CCPCH)
• Secondary Common Control Physical Channel (S-CCPCH)
• Acquisition Indicator Channel (AICH)
• Paging Indicator Channel (PICH)
• Broadcast Channel (BCH)
• Forward Access Channel (FACH)
9 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Power Control Classification
There are two methods of power control use in WCDMA system, which
is Open Loop Power Control and Close Loop Power Control
For uplink, the UE transmission power is adjusted
For downlink, the NodeB transmission power is adjusted.
10 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Power Control for Physical Channel
Table below describes the power control method and the related UL and DL channels.
11 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Power Control for Physical Channel (Cont.)
Channel Types related to Power Control Power Control Types Channel (Uplink) Channel (Downlink)
Primary Common Pilot Channel (P-CPICH) P-CPICH
P-SCH
Primary Synchronization Channel (P-SCH)
S-SCH
Secondary Synchronization Channel (S-SCH) P-CCPCH
Common channel power
Primary Common Control Physical Channel (P-CCPCH) PRACH S-CCPCH
control
AICH
Secondary Common Control Physical Channel (S-CCPCH)
PICH
Acquisition Indicator Channel (AICH) & Paging Indicator Channel (PICH) BCH
Broadcast Channel (BCH) & Forward Access Channel (FACH) FACH
DPCH, including the
Downlink Physical Dedicated Channel (DPDCH) DPCH, including the following:
following:
Downlink Physical Common Channel (DPCCH) DCH channel power control DPCCH DPCCH
DPDCH DPDCH
Dedicated Channel (DCH) & Enhanced Dedicated Channel (E-DCH)
F-DPCH
Fractional Dedicated Physical Channel (F-DPCH)
Dedicated Physical Channel (DPCH) WRFD-01061004 HSDPA HS-PDSCH
HS-DPCCH
Power Control
High Speed Physical Downlink Shared Channel (HS-PDSCH) HS-SCCH
High Speed Shared Control Channel (HS-SCCH) E-DCH, including: E-AGCH
WRFD-01061203 HSUPA
E-DPCCH E-RGCH
Enhanced Absolute Grant Channel (E-AGCH) Power Control
E-DPDCH E-HICH
Enhanced Relative Grant Channel (E-RGCH)
Enhanced HAQR Indicator Channel (E-HICH) Table above describes the power control type and the related UL&DL channels
12 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters
MaxTxPower (MO : Radio-> UNodeB -> UCell -> UCELL) Impact Area - Capacity
Parameter name: Max transmit power of cell
GUI Value Range : 0~500
Actual Value Range : 0~50
Recommended value: 430, namely 43dBm (430 x 0.1dBm)
Set this parameter through ADD UCELLSETUP and modify it through MOD UCELL.
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
This parameter is configured during network planning. If this parameter is set to a small value, downlink capacity and coverage are
restricted. However, the maximum value should not exceed the processing capability of the NodeB
13 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters (Cont.)
PCPICHPower (MO : Radio -> UNodeB -> Ucell -> UPCPICH ) Impact Area -Capacity
Parameter Name: PCPICH Transmit Power
GUI Value Range :
Actual Value Range : -10~50
Recommended value : 330, namely 33dBm (330 x 0.1dBm)
Feature ID : (WRFD-150236, WRFD-020104, WRFD-020501)
Feature Name : (Load Based Dynamic Adjustment of PCPICH, Intra Frequency Load Balance, Open Loop Power Control)
Guidance Notes:
If the maximum transmit power of the P-CPICH is set very high, the P-CPICH will consume a large amount of cell resources and strongly
interfere downlink traffic channels. Decreasing cell capacity.
If the maximum transmit power of the P-CPICH is set very low, the downlink cell coverage area will be very small. It will cause issues on: Cell
resources cannot be fully utilized; Cell capacity will decrease; Will cause coverage holes and cell edge UEs cannot access network.
14 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters (Cont.)
PSCHPower and SSCHPower (MO : Radio-> UNodeB -> Ucell ->UPSCH/USSCH) Impact Area - Capacity
Parameter name: PSCH / SSCH transmit power
GUI Value Range : -350~150
Actual Value Range : -35~15
Recommended value: -50, namely -5dB (-50 x 0.1dB)
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
If the value is set excessively low, UEs at the cell edge will fail on network searching, impacting the coverage of downlink common channel.
This affects the cell coverage.
If the value is set excessively high, the power resources are wasted, and other channels are interfered seriously, thus the cell capacity will be
impacted.
15 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters (Cont.)
UBCH (MO : Radio -> UNodeB -> UCell -> UBCH) Impact Area - Capacity
Parameter Name: BCH transmit power
GUI Value Range : -350~150
Actual Value Range : -35~15
Recommended value: -20, namely -2dB (-20 x 0.1dB)
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
If the value is set too small, the UEs on the cell edge cannot receive the system messages properly. This impact the coverage of the
downlink common channel and cell coverage.
If the value is set too high, it causes interference to other channels, consuming downlink transmit power, and affects the cell capacity.
16 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters (Cont.)
MaxFachPower (MO : Radio -> UNodeB -> UCell -> UFACH) Impact Area - Capacity
Parameter name: max transmit power of FACH
GUI Value Range : -350~150
Actual Value Range : -35~15
Recommended value: 10, namely 1dB (10 x 0.1dB)
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
If MaxFachPower is set excessively low, UE located at the cell edge may fail to receive the services and signalling carried over the FACH. This
will impact the downlink common channel coverage and cell coverage.
If MaxFachPower is set excessively high, other channels will be interfered and more downlink power resources will be consumed. This will
impact the cell capacity.
17 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters (Cont.)
PCHPower (MO : Radio -> UNodeB -> UCell -> UPCH) Impact Area - Capacity
Parameter Name: PCH transmit power
GUI Value Range : -350~150
Actual Value Range : -35~15
Recommended value: -20, namely -2dB (-20 x 0.1dB)
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
If the value is set too small, the UEs on the cell edge cannot receive the paging message properly. This problem affects the coverage
of the downlink common channel and cell coverage.
If the value is set too high, it causes interference to other channels, occupies the downlink transmit power, and affects the cell
capacity.
18 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Common Physical Channel Power Parameters (Cont.)
AICHPowerOffset (MO : Radio -> UNodeB -> UCell -> UCHPWROFFSET) Impact Area - Capacity
Parameter Name: The difference between the transmit power of AICH and PCPICH.
GUI Value range: -22 to 5
Actual value range: -22~5
Recommended value : -6dB
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
PICHPowerOffset (MO : Radio -> UNodeB -> UCell -> UCHPWROFFSET) Impact Area - Capacity
Parameter Name: The difference between the transmit power of AICH and PCPICH.
GUI Value range: -10~5
Actual value range: -10~5
Recommended value : -7dB
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Set this parameter through ADD UCHPWROFFSET, query it through LST UCHPWROFFSET, and modify it through MOD
UAICHPWROFFSET.
19 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
• Overview of Power Control
• Open Loop Power Control
• Closed Loop Power Control
• Enhancement
20 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Open Loop Power Control
21 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Open Loop Power Control
2.1 Open Loop Power Control Overview
2.2 PRACH Open Loop Power Control
2.3 Downlink Dedicated Channel Open Loop Power Control
2.4 Uplink Dedicated Channel Open Loop Power Control
22 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Open Loop Power Control Overview
Diagram below describe the purpose, principle and the application of Power Control.
In downlink open loop power control, the initial transmission power is calculated according to the downlink path loss between NodeB and
UE.
In uplink, since the uplink and downlink frequencies of WCDMA are in the same frequency band, a significant correlation exists between the
average path loss of the two links. This make it possible for each UE to calculate the initial transmission power required in the uplink based
on the downlink path loss.
However, there is 90MHz frequency interval between uplink and downlink frequencies, the fading between the uplink and downlink is
uncorrelated, so the open loop power control is not accurate.
23 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Open Loop Power Control
2.1 Open Loop Power Control Overview
2.2 PRACH Open Loop Power Control
2.3 Downlink Dedicated Channel Open Loop Power Control
2.4 Uplink Dedicated Channel Open Loop Power Control
24 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control
25 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control
In access procedure, the first signalling “RRC CONNECTION REQUEST” is sent in the “message part” on PRACH.
Before PRACH “message part” been sent, UE will transmit PRACH preamble, and the transmission power of first preamble is calculated by this
PRACH open loop power control.
26 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control (Cont.)
After UE transmit the first Preamble on PRACH, it will wait for the corresponding AI (Acquisition Indicator) on the AICH.
• If no positive or negative AI on AICH is received after Ʈp-a time, UE shall increase preamble power by PowerRampStep, and retransmit
preamble.
• A preamble ramping procedure consists of several preamble ramping cycles, which cannot exceed Mmax. In each cycle, the UE
retransmits preamble until the UE receives the acquisition indicator or the number of retransmissions has reach PreambleRetransMax.
If a negative AI on AICH is received by the UE after Ʈp-a time,
• It’s indicates rejection of the preamble, the UE shall wait for a “Back-off Delay” and re-initiate a new random access process. The
parameters NB01min and NB01max define the lower and upper limits of the back-off delay. If the value of NB01min is equal to NB01max, it
means that the retransmission period of the preamble part is fixed.
27 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control (Cont.)
When a positive AI on AICH is received by UE after Ʈp-a time, it will transmit the random access message after the uplink access slot of the last
preamble.
The “message part” consists of two parts: the control part and the data part. The power of the control part is the same as the power of the last
transmitted preamble plus a value defined by the PowerOffsetPpm parameter.
PowerOffsetPpm must be set for each instance of PRACH TFC.
28 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control (Cont.)
When UE needs to set up a RRC connection, the initial power of uplink PRACH preamble can be calculated according to the following formula:
The initial value of PRACH power is set through open loop power control.
UE operation steps are as follows:
1. Read “Primary CPICH DL TX power”, “UL interference” and “Constant value” from system information
2. Measure the value of CPICH_RSCP
3. Calculate the Preamble_Initial_Power of PRACH
29 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters
Constantvalue (MO : Radio -> UNodeB -> UCell -> UPRACHBASIC) Impact Area - Capacity
Parameter Name: Constant value for calculating initial TX power
GUI Value range: -35 to -10
Actual Value Range: -35~-10
Recommended value: -20, namely -20dB
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
If the parameter value is high, the transmit power of the first preamble to be used in the random access procedure is strong. The
access delay decreases but the impact on the uplink capacity increases.
If the parameter value is small, the transmit power of the first preamble to be used in the random access procedure is limited. The
impact on the uplink capacity decreases but the access delay increases.
30 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
AICHTxTiming
AICH transmission timing
Content
When AICHTXTIMING = 0,
Ʈp-p,min = 15360 chips, Ʈp-a = 7680 chips, Ʈp-m = 15360 chips
When AICHTXTIMING = 1,
Ʈp-p,min = 20480 chips, Ʈp-a = 12800 chips, Ʈp-m = 20480 chips
Recommended value: 1
After UE transmit the first Preamble on PRACH, it will wait for the corresponding AI (Acquisition Indicator) on the AICH.
The timing relationship of PRACH and AICH is as follow:
There are 3 parameters used to define the timing relationship:
Ʈp-p: time interval between two PRACH preambles. Ʈp-p is not a fixed value, it is decided by selecting access slot of PRACH preambles.
Here Ʈp-p has one restriction, it must be longer than a minimum value Ʈp-p min, namely Ʈp-p. ≥ Ʈp-p min
Ʈp-a: time interval between PRACH preamble and AICH Acquisition Indicator. If UE sends the PRACH preamble, it will detect the responding
AI after Ʈp-a time.
Ʈp-m: time interval between PRACH preamble and PRACH message part. If UE sends the PRACH preamble and receives positive AI from the
AICH, it will send the message part after Ʈp-m time.
31 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
AICHTxTiming (MO : Radio -> UNodeB -> UCell -> UAICH)
Parameter Name: AICH Transmission Timing.
GUI Value range : 0~1
Actual Value Range : 0~1
Recommended value : 1
Feature ID : (WRFD-020504, WRFD-021308, WRFD-020501)
Feature Name : (Inner Loop Power Control, Extended Cell Coverage up to 200km, Open Loop Power Control)
Set this parameter through ADD UAICH, query it through LST UAICH, and modify it needs de-activated the cell through DEA UCELL.
After the old configuration of AICH is deleted through RMV UAICH, a new AICH can be established through ADD UAICH.
32 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
PowerRampStep (MO : -> Radio -> UNodeB -> UCell -> UPRACHBASIC) Impact Area - Capacity & Load
Parameter Name: Power increase step
GUI Value Range : 1~8
Actual Value Range : 1~8
Recommended value: 2, namely 2dB
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes:
A high value of this parameter shortens the access procedure but increases power consumption. In this case, uplink load congestion
is easily happen if simultaneous access of multiple users occurs.
A small value of this parameter extends the access procedure but decreases the power consumption. In this case, the uplink load is
low.
33 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
PreambleRetransMax (MO : -> Radio -> UNodeB -> UCell -> UPRACHBASIC) Impact Area - Accessibility
Parameter Name: Max preamble retransmission
GUI Value Range : 1~64
Actual Value Range : 1~64
Recommended value: 20
Feature ID : (WRFD-020501)
Feature Name : (Open Loop Power Control)
Guidance Notes :
If the parameter value is too low, the preamble power fails to ramp to the required value, resulting in UE access failures.
If the parameter value is too high, the UE repeatedly increases the power and makes access attempts, resulting in interference to other UEs.
34 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
Mmax (MO : Radio -> UNodeB -> UCell -> URACH) Impact Area - Accessibility
Parameter Name: Max preamble loop
GUI Value Range : 1~32
Actual Value Range : 1~32
Recommended value: 3
Feature ID : (WRFD-010401, WRFD-020501)
Feature Name (System Information Broadcasting, Open Loop Power Control)
Guidance Notes :
If the parameter value is too small, the UE access success rate is reduced.
If the parameter value is too large, the UE at the cell edge repeatedly spends a long time to access the network, which increases the uplink
interference.
35 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
NB01min / NB01max (MO : Radio -> UNodeB -> UCell -> URACH) Impact Area - Accessibility
Parameter Name: Random back-off lower / upper limit
GUI Value Range : 0~50
Actual Value Range : 0~50
Recommended value: 0 for both NB01min / 10 for NB01max
Feature ID : (WRFD-010401, WRFD-020501)
Feature Name (System Information Broadcasting, Open Loop Power Control)
NB01max
Guidance Notes : If the parameter value is large, the period in which the next random access is allowed to be initiated is long after the AICH
receives an NACK message. The random access delay increases. The conflict possibility is low in the random access procedure.
If the parameter value is small, the period in which the next random access is allowed to be initiated is short after the AICH receives an NACK
message. The conflict possibility is high in the random access procedure.
NB01min
Guidance Notes : f the parameter value is small, the period in which the next random access is allowed to be initiated is long after the AICH receives
an NACK message. The conflict possibility is low in the random access procedure.
If the parameter value is large, the period in which the next random access is allowed to be initiated is short after the AICH receives an NACK
message. The conflict possibility is high in the random access procedure.
36 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
The power offset between the last access preamble and the message control part. The power of the message control part can be obtained by
adding the offset to the access preamble power.
The power of the data part is calculated with the following formula:
P data = P control x (βd/ βc)2
βd is the power gain factor for the data part. The value is defined by the GainFactorBetaD parameter.
This parameter specifies the power gain factor of the data part. For detailed information of this parameter, see 3GPP TS 25.214.
βc is the power gain factor for the control part. The value is defined by the GainFactorBetaC parameter.
This parameter specifies the power gain factor of the control part. For detailed information of this parameter, see 3GPP TS 25.214.
37 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
The power offset between the last access preamble and the message control part. The power of the message control part can be obtained by
adding the offset to the access preamble power.
For detailed information of this parameter, see 3GPP TS 25.213.
PowerOffsetPpm (MO : Radio -> URNCBASIC -> UNodeB -> UCell -> UPRACHBASIC -> UPRACHTFC)
Parameter Name: Power Offset
GUI Value range: -5~10
Actual value range: -5~10
Recommended value :
1.In signalling transmission mode, set PowerOffsetPpm to -3; in service transmission mode, set PowerOffsetPpm to -2.
2. If "RESERVED_SWITCH_6_BIT4" under the "RsvSwitch6" parameter in the "SET UCELLALGORSVPARA" command is modified from 0 to 1, increase the
value by 5 dB.
3. If "RESERVED_SWITCH_6_BIT4" under the "RsvSwitch6" parameter in the "SET UCELLALGORSVPARA" command is modified from 0 to 1 and then to 0,
retain the original value.
Guidance Notes:
If the parameter value is too small, the probability for UTRAN to correctly receive signalling and service data carried on the RACH decreases,
affecting the uplink coverage.
If the parameter value is too large, the uplink interference increases and the uplink capacity is reduced.
38 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
PRACH Open Loop Power Control Parameters (Cont.)
The transmit power on the PRACH cannot be greater than the maximum allowed uplink transmit power
MaxAllowedUlTxPower (Under MO : Radio ->UNodeB -> UCell ->UCELLSELRESEL)
Parameter name: Max allowed UE UL TX power
(The maximum allowed uplink transmit power of a UE in the cell, which is related to the network planning)
GUI Value range: -50~33
Actual value range: -50~33
Recommended value: 24, namely 24dBm
Feature ID : (WRFD-010801, WRFD-010802) ; Feature Name : (Intra RNC Cell Update, Inter RNC Cell Update)
Guidance Notes :
If the parameter value is too large, it is possible that UL coverage will become wider than downlink coverage, and it will
cause the service unbalanced between UL and DL coverage.
If the parameter value is too small, the uplink coverage will become limited and smaller than the downlink coverage, it will
cause the service unbalanced between UL and DL coverage.
39 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Open Loop Power Control
2.1 Open Loop Power Control Overview
2.2 PRACH Open Loop Power Control
2.3 Downlink Dedicated Channel Open Loop Power Control
2.4 Uplink Dedicated Channel Open Loop Power Control
40 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Dedicated Channel Open
Loop Power Control
41 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DL DPCH Open Loop Power Control
• According to the RRC connection establishment procedure, after RNC received the “RRC CONNECTION REQUEST” message, RNC will set up the RRC
Connection in Dedicated Channel and then it will tell NodeB to set up the radio link for this particular UE. Iub interface resources will now be
established between NodeB and RNC.
• When DCH-FP of Iub interface finished downlink and uplink synchronization, the downlink DPCH starts to transmit, and DPCH initial transmission
power is calculated through open loop power control.
42 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DL DPCH Open Loop Power Control (Cont.)
• The below formula will use for DL DPCH Open Loop Power Control
• Initial power of DL DPDCH can be calculated based on the measurement results in the RACH IE of RRC connection request from UE, calculation
formula
43 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DL DPCH Open Loop Power Control (Cont.)
Related Figure show the transmit power offset of TFCI (PO1)/ TPC (PO2) / Pilot (PO3) to
Data fields in timeslot.
• PO3 : Transmit power offset of pilot bit fields in a secondary common control
physical channel's timeslot to data fields in the timeslot.
• PO2 : Power offset between TPC command transmit power on the F-DPCH channel
and reference F-DPCH TX power (carried by the Initial DL Transmission Power IE sent
to the NodeB).
44 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DL DPCH Open Loop Power Control (Cont.)
Configuration Parameters of PO1, PO2 and PO3:
PO1 ( MO : Radio -> UNodeB-> Ucell-> USCCPCHBASIC) Impact Area (Capacity)
Parameter Name: Power Offset 1
GUI Value Range : 0~24
Actual Value Range : 0~6
Recommended value : 8. Actual value : 2dB (8 x 0.25dB)
!
Parameter Name: Power Offset 3
GUI Value Range : 0~24
Actual Value Range : 0~6
Recommended value : 8. Actual value : 3dB (12 x 0.25dB)
Guidance Notes :
If the parameter value is too large, interference on other channels will increases and the cell capacity decreases.
If the parameter value is too small, the SCCPCH coverage decreases and the downlink coverage of the cell will decreases.**
45 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DL DPCH Open Loop Power Control (Cont.)
FdpchPO2 (MO : Radio -> URNC -> UFDPCHPARA) Impact Area (Capacity, QOS)
Parameter Name: F-DPCH Power Offset
GUI Value Range : 0~24
Actual Value Range : 0~6
Recommended value : 8. Actual value : 3dB (12 x 0.25dB)
Feature ID : (WRFD-010652) ; Feature Name : (SRB over HSDPA)
Guidance Notes :
The larger the value of this parameter, the greater the maximum transmit power of the F-DPCH, the larger the downlink coverage area, the
stronger the interference to other channels. This will reduces the downlink capacity and affects the downlink user throughput and user experience.
The smaller the value of this parameter, the lower the maximum transmit power of the F-DPCH and the smaller the downlink coverage area will
cause higher downlink TPC bit error rate for the cell edge users (CEUs). As a result, the accuracy in adjusting UE transmit power decreases, the
uplink RTWP fluctuation increases, and the uplink capacity decreases, affecting uplink user throughput and user experience.
46 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Power Control Restriction
The power of downlink dedicated channel is limit by an Upper and Lower limit for each radio link
RlMaxDLPwr (MO : Radio -> UNodeB -> Ucell -> UCELLRLPWR) Impact Area - Capacity & QOS
Parameter name: RL Max DL TX power
GUI Value Range : -350~150
Actual Value Range : -35~15 (GUI Value x 0.1dB)
Recommended value : Please refer to the next page for Huawei Recommended Values.
Feature ID : (WRFD-140205, WRFD-020501) ; Feature Name : (Voice Service Experience Improvement for Weak Reception Ues, Open Loop Power
Control)
Configuration constraints:
[UCELLRLPWR:RLMAXDLPWR] >= [UCELLRLPWR:RLMINDLPWR]
Guidance Notes :
Setting this parameter to a large value increases the downlink transmit power of a single radio link, thereby reducing the downlink capacity.
Setting this parameter to a small value reduces the coverage area for services and increases the probability of call drops.
47 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Power Control Restriction (Cont.)
The power of downlink dedicated channel is limit by an Upper and Lower limit for each radio link
RlMinDlPwr (MO : Radio -> UNodeB -> Ucell -> UCELLRLPWR) Impact Area - Capacity & QOS
Parameter name: RL Min DL TX power
GUI Value Range : -350~150
Actual Value Range : -35~15 (GUI Value x 0.1dB)
Recommended value : Please refer to the next page for Huawei Recommended Values.
Feature ID : (WRFD-140205, WRFD-020501) ; Feature Name : (Voice Service Experience Improvement for Weak Reception Ues, Open Loop Power
Control)
Configuration constraints:
[UCELLRLPWR:RLMAXDLPWR] >= [UCELLRLPWR:RLMINDLPWR]
Guidance Notes :
If this parameter is set to a small value, the value range of the downlink transmit power becomes large and the probability of downlink transmit
power drift increases.
If this parameter is set to a large value, the downlink power of a single radio link may exceed the required power, which wastes the downlink power.
48 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Power Restriction Parameters
Table below show the Recommended DL Power Restriction configurations parameters for typical services such RL Max Downlink Transmit Power
and RL Min Downlink Transmit Power which all related to different downlink SF (Spreading factor)
49 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Open Loop Power Control
2.1 Open Loop Power Control Overview
2.2 PRACH Open Loop Power Control
2.3 Downlink Dedicated Channel Open Loop Power Control
2.4 Uplink Dedicated Channel Open Loop Power Control
50 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Dedicated Channel Open
Loop Power Control
51 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
UL DPCH Open Loop Power Control
• According to the RRC connection establishment procedure, after RNC sent the “RRC CONNECTION SETUP” message, UE will try to synchronize with
NodeB, and then uplink DPCCH starts to transmit, hence DPCCH initial transmission power is calculated through open loop power control.
• The power of the uplink DPDCH is set as a power offset (βd/βc) reference to the uplink DPCCH. The uplink DPCCH and DPDCHs are transmitted
through different channel codes. To meet a given QoS requirement on the transport channels, different TFCs use different power offsets.
• The RNC has a set of reference values (βc,ref and βd,ref) that are stored for each predefined Radio Access Bearer (RAB) or Signaling Radio Bearer
(SRB). βc,ref and βd,ref can be configured by BETAC and BETAD on the RNC.
• The RNC calculates a new power offset for each TFC based on the reference values dynamically and sends the power offset to the UE
52 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
UL DPCH Open Loop Power Control
The initial power of the uplink DPCCH can be calculated according to the following formula
DPCCH_Initial_Power = DPCCH_Power_Offset – CPICH_RSCP
Where:
DPCCH_Power_Offset is provided by the RNC to the UE via RRC signaling
CPICH_RSCP is the received signal code power of the PCPICH
Based on the upper formula, the initial power calculation formula for the uplink DPCCH can be changed to the following , it’s similar to
the formula for PRACH :
DPCCH_Initial_Power = PCPICHPower – CPICH_RSCP + UL Interference + DefaultConstantValue
Where :
The DefaultConstantValue parameter reflects the target Ec/No of the uplink DPCCH.
53 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
UL DPCH Open Loop Power Control Parameter
DefaultConstantValue (MO : Radio-> URNCBASIC -> UFRC) Impact Area - Capacity
Parameter Name: Constant value configured by default
GUI Value Range : -35~-10
Actual Value Range : -35~-10
Recommended value: -22, namely -22dB
Feature ID : (WRFD-020501) ; Feature Name : (Open Loop Power Control)
Guidance Notes :
If the parameter value is small, the probability of uplink synchronization failures increases for UEs at the cell edge during initial link
setup. In this situation, the performance of uplink coverage decreases.
If the parameter value is large, instantaneous interference caused by uplink cell RTWP becomes strong, affecting the uplink system
capacity.
54 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
• Overview of Power Control
• Open Loop Power Control
• Closed Loop Power Control
• Enhancement
56 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Closed Loop Power Control
57 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Closed Loop Power Control
3.1 Closed Loop Power Control Overview
3.2 Uplink Inner Loop Power Control
3.3 Downlink Inner Loop Power Control
3.4 Outer Loop Power Control
58 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Closed Loop Power Control
Overview
59 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Closed Loop Power Control Overview
Why closed loop power control is needed?
• Open loop power control is not accurate enough, it can only estimate the initial transmission power
• Closed loop power control can guarantee the QoS with minimum power. By decreasing the interference, the system capacity will be increased.
61 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop Power Control
62 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop Power Control Parameters
PwrCtrlAlg (MO : Radio -> RNCBASIC -> UFRC) Impact Area - QOS
Parameter Name: Power control algorithm selection
GUI Value Range : ALGORITHM1, ALGORITHM2
Actual Value Range : ALGORITHM1, ALGORITHM2
Recommended value: ALGORITHM 1
Feature ID : (WRFD-020504) ; Feature Name : (Inner Loop Power Control)
Guidance Notes :
If this parameter is set to ALGORITHM1, the fast power control mode is used. This will guarantees the QoS on a low-speed attenuation channel but
wastes the power on a high-speed or Gaussian channel.
If this parameter is set to ALGORITHM2, the slow power control mode is used. This may increases the bit error rate and cannot guarantee the QoS
on a low-speed attenuation channel, but can save the power on a high-speed or Gaussian channel on the assumption of guarantee of the QoS.
63 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop Power Control
Diagram beside describe the process flow of the Uplink Inner Loop
Power Control which include PCA1 and PCA2 (Power Algorithm 1 & 2)
There are two type of algorithms used in Uplink Inner Loop Power
Control, such as PCA1 (Power Control Algorithm 1) or PCA2 (Power
Control Algorithm 2)
• NodeB compares the measured SIR to the target SIR, then derives
TPC and sends the TPC decision to UE
• RNC sends SIRtar (target SIR) to NodeB and then NodeB compares
SIRmea (measured SIR) with SIRtar:
If the estimated SIR is greater than the target SIR, NodeB sends TPC
“0” to UE on downlink DPCCH TPC field;
Otherwise, NodeB sends TPC “1” to UE.
After reception of one or more TPC, UE shall derive a single TPC_cmd
(TPC command, with value among -1, 0, 1):
Two algorithms could be used by the UE for deriving the TPC_cmd,
those are PCA1 and PCA2 (PCA means Power Control Algorithm).
For UE is in soft handover state, more than one TPC is received, so
firstly multiple TPC_cmd is combined.
64 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop Power Control (Cont.)
NodeB compares the measured SIR to the target SIR, then derives TPC
and sends the TPC decision to UE
When deriving the combined TPC_cmd, UE shall adjust the transmit
power of uplink DPCCH with a step “UL Closed Loop Power Control Step
Size“, as following:
• △DPCCH =△TPC × TPC_cmd
• Where :
• This adjustment is executed on the DPCCH, then associated
△DPCCH is power increment/reduction on DPCCH
• TPC_cmd is calculated by the PCA1 or PCA2 according to the
TPC
• △TPC is the step of power control. For PCA1, it’s determined
by UlTpcStepSize. For PCA2, the step size is fixed to 1dB.
DPDCH transmit power is calculated according to DPDCH / DPCCH power
ratio βd / βc.
Pdpdch = Pdpcch × (βd / βc)2
65 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop PCA1 with Single Radio Link
Diagram beside describe the TPC control and command for PCA1 with single radio link.
For single radio link and PCA1, UE derives one TPC_cmd in each time slot as follows:
• When UE has single radio link, only one TPC will be received in each slot. In this case, the value of TPC_cmd shall be derived by PCA1 as follows:
• If the received TPC is equal to 0, then TPC_cmd for that slot is -1;
• If the received TPC is equal to 1, then TPC_cmd for that slot is 1.
• According to DPCCH channel structure, there are 15 time slots in a 10ms radio frame, and the control is performed once in each time slot, so the
frequency of uplink inner loop PCA1 is 1500Hz.
66 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop PCA2 with Single Radio Link
Diagram beside describe the TPC control and TPC command of PCA2 with single radio link.
For single radio link and PCA2, UE derives one TPC_cmd in each 5-slot group as follows
When UE has single radio link, only one TPC will be received in each slot. In this case, the value of TPC_cmd shall be derived by PCA2 as follows:
For the first 4 slots of a set, TPC_cmd = 0.
For the fifth slot of a set, UE make the decisions on as follows:
• If all 5 TPCs within a group are 1, then TPC_cmd = 1 in the 5th slot;
• If all 5 TPCs within a group are 0, then TPC_cmd = -1 in the 5th slot;
• Otherwise, TPC_cmd = 0 in the 5th slot.
According to DPCCH channel structure, there are 15 time slots in a 10ms radio frame, and the control is performed once in each 5-slot group, so
the frequency of uplink inner loop PCA2 is 300Hz.
67 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop Power Control with Soft Handover
When UE enters soft handover state, on the NodeB side, there are two phases:
• Uplink synchronization phase
• Multi-radio link phase
On UE side, UE will receive different TPCs from different RLS in one time slot, Therefore, the UE should combine all the TPCs to get a unique
TPC_CMD
On the NodeB side, there are two phases during the soft handover state:
Uplink synchronization phase
The NodeB should send “TPC = 1” continously to the newly-added RL before successful uplink synchronization.
Multi-radio link phase
Each cell will estimate the SIR individually and the generate TPC individually.
Especially , when UE is in softer handover state, it means UE has radio links to the same NodeB, in this case these RLs(Radio Link) belong to the
same RLS(Radio Link Set), and the all TPCs are the same from each RL.
Therefore , when UE enters soft handover state, the UE may receive different TPC from different RLS, and the UE should combine these TPCs
before deriving TPC_CMD.
68 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop PCA1 with Soft Handover
When UE is in soft handover state, multiple TPC will be received in each
slot from different cells in the active set. UE will generate the TPC_cmd
by PCA1 as follows:
1. Combine the TPCs from the same RLS and derive the Wi
When the RLs (Radio Link) are in the same RLS (Radio Link Set), they
will transmit the same TPC in a slot. In this case, the TPCs from the
same RLS shall be combined into one.
After combination, UE will obtain a soft symbol decision Wi for each
RLSi.
2. Combine the TPCs from different RLSs and derive the TPC_cmd
UE derives TPC_cmd, it is based on a function γ and all the N soft
symbol decisions Wi:
TPC_cmd = γ (W1, W2, … WN),
Where TPC_cmd can only take the values 1 or -1.
If the TPCs from all RLSs are “1”, the output of γ shall be equal to “1”;
If one TPC from any RLS is “0”, the output of γ shall be equal to “-1”.
69 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop PCA2 with Soft Handover
When UE is in soft handover state, multiple TPC will be received in
each slot from different cells in the active set. UE will generate the
TPC_cmd by PCA2 as follows:
1. Combine the TPC from the same RLS
When the RLs are in the same RLS, they will transmit the same TPC
in a slot. In this case, the TPCs from the same RLS shall be
combined into one.
2. Calculate the TPC_tempi for each RLS
UE derives TPC_tempi through the same way in the last slide, as
follows:
For the first 4 slots of a group, TPC_tempi = 0.
For the 5th slot of a group:
If all 5 TPCs within a group are 1, then TPC_tempi = 1 in the 5th
slot;
If all 5 TPCs within a group are 0, then TPC_tempi = -1 in the 5th
slot;
70 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop PCA2 with Soft Handover (Cont.)
Diagram beside describe the TPC control and TPC command of PCA2 with
soft Handover scenario.
3. Calculate the TPC_cmd
Otherwise, TPC_cmd = 0.
71 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Inner Loop Power Control Parameters (Cont.)
UlTpcStepSize (MO : Radio -> RNCBASIC -> UFRC) Impact Area - Capacity
Parameter Name: UL closed loop power control step size
GUI Value Range : 1~2
Actual Value Range : 1~2
Recommended value: 1, namely 1dB
Feature ID : (WRFD-020504) ; Feature Name : (Inner Loop Power Control)**
Guidance Notes :
The larger the value of this parameter, the faster the power adjustment. As a result, more power is wasted and the system capacity decreases on a
low-speed channel, and channel attenuation speeds up and the system capacity increases on a high-speed channel.
The smaller the value of this parameter, the slower the power adjustment. As a result, more power is saved and the system capacity increases on a
low-speed channel, and the channel attenuation slows down and the system capacity decreases on a high-speed channel.
72 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Closed Loop Power Control
3.1 Closed Loop Power Control Overview
3.2 Uplink Inner Loop Power Control
3.3 Downlink Inner Loop Power Control
3.4 Outer Loop Power Control
73 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Inner Loop Power Control
74 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Inner Loop Power Control
Diagram beside describe the DL Inner Loop Power Control Algorithm which is
DPC_Mode.
UE L1 compares the measured SIR to the target SIR, then derives the TPC and
sends the TPC Decision to NodeB
Basically the downlink inner loop power control process is similar with uplink,
UE L3 sends SIRtar to UE L1 and then UE L1 compares SIRmea with SIRtar:
▪ If the SIRmea is greater than the SIRtar, UE sends TPC “0” to NodeB on
uplink DPCCH TPC field;
▪ Otherwise, UE sends TPC “1” to the NodeB.
The UE shall check the downlink power control mode before generating the
TPC, two algorithm DPC_MODE 0 and DPC_MODE 1 could be used by UE to
derive the TPC.
Upon receiving the TPC,
▪ if the DPC_MODE is 0 , the NodeB shall use the TPC to generate the
TPCest(k).
▪ If the DPC_MODE is 1, the NodeB shall use the three continuous TPCs
received to generate the TPCest(k).
Then the NodeB will use TPCest(k) to calculate PTPC(k), PTPC(k) is the downlink
power adjustment.
In the end, the NodeB shall adjust the current downlink power P(k-1) to a new
downlink power P(k), and adjust the power of the DPCCH and DPDCH with the
same amount, since power difference between them is fixed.
75 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Inner Loop Power Control Mode Parameters
DpcMode (MO : Radio -> RNCBASIC -> UFRC) Impact Area - QOS
Parameter name: Downlink power control mode
GUI Value Range : SINGLE_TPC, TPC_TRIPLET_IN_SOFT, TPC_AUTO_ADJUST
Actual Value Range : SINGLE_TPC, TPC_TRIPLET_IN_SOFT, TPC_AUTO_ADJUST
Recommended value: SINGLE_TPC, namely DPC_MODE = 0
Feature ID : (WRFD-020504) ; Feature Name : (Inner Loop Power Control)
Guidance Notes:
If this parameter is set to SINGLE_TPC, the fast power control mode is used. This will guarantees the QoS on a low-speed attenuation channel but
wastes the power on a high-speed or Gaussian channel.
If this parameter is set to TPC_TRIPLET_IN_SOFT, the slow power control mode is used. This will increases the bit error rate and cannot guarantee
the QoS on a low-speed attenuation channel, but can save the power on a high-speed or Gaussian channel on the assumption of guaranteeing the
QoS.
If this parameter is set to TPC_AUTO_ADJUST, the value of DPC_MODE is modified by RNC based on SHO state:
For a single link, the fast power control mode is used, and for a soft handover, the slow power control mode is used. This reduces the impact of
power drift.
76 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Inner Loop Power Control Mode Parameters (Cont.)
After decoding received TPC, NodeB shall set the new downlink power P(k) according to the following formula:
P(k) = P(k-1) + PTPC(k) + Pbal(k)
Where
• P(k-1) is (k-1): th downlink transmission power
• PTPC(k) is the power adjustment due to TPCest(k)
• Pbal(k) is correction value according to the downlink power balance procedure. For a single radio link, Pbal(k) equals 0
77 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Inner Loop Power Control Mode Parameters (Cont.)
PTPC(k) is calculated according to the following:
▪ If the value of “Limited Power Increase Use” parameter is “Not Used”, then:
Where:
▪ TPCest(k) is the estimated TPC
▪ ∆TPC is downlink power adjustment step size, it is determined by the parameter FddTpcDlStepSize
▪ If the value of “Limited Power Increase Use” parameter is “Used”, then:
Where:
From the definition above, ∆sum(k) indicates the sum of downlink power adjustment in the latest
DL_Power_Average_Window_Size
Power_Raise_Limit is set to 10dB.
DL_Power_Averaging_Window_Size is set to 20.
78 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Inner Loop Power Control Mode Parameters (Cont.)
PcSwitch -> PC_INNER_LOOP_LMTED_PWR_INC_SWITCH (MO : Radio -> UCORRMALGOSWITCH) Impact Area - Capacity
This is one switch in PcSwitch (Power control switch) parameter.
GUI Value range: 1, 0
Actual value range: ON, OFF
Set this parameter through SET UCORRMALGOSWITCH.
Guidance Notes : When PC_INNER_LOOP_LMTED_PWR_INC_SWITCH is enabled, you are advised to enable DRA_DCCC_SWITCH to optimize the effect
of the related functions.
79 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Power Balance
The purpose of this procedure is to reduce power drifts between radio links in the macro diversity
system
The start and stop of the DPB when the DPB switch is on
For the UEs in softer handover, the RNC evaluates the power difference of the radio links and
decide whether to start or stop DPB
For the UEs in soft handover, DPB is always active
During soft handover, the UL TPC is demodulated in each RLS, then due to demodulation errors, the
DL transmit power of the each branch in soft handover will drift separately, which causes loss to the
macro-diversity gain.
During softer handover, the power among all radio links may drift because of initial power difference.
• The DL Power Balance (DPB) algorithm is introduced to reduce the power drift between links
during the soft handover or softer handover.
PcSwitch -> PC_DOWNLINK_POWER_BALANCE_SWITCH (MO : Radio -> UCORRMALGOSWITCH)
Impact Area - Capacity
This is one switch in PcSwitch (Power control switch) parameter.
GUI Value range: 1, 0
Physical value range: ON, OFF
Set this parameter through SET UCORRMALGOSWITCH
80 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Closed Loop Power Control
3.1 Closed Loop Power Control Overview
3.2 Uplink Inner Loop Power Control
3.3 Downlink Inner Loop Power Control
3.4 Outer Loop Power Control
81 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Outer Loop Power Control
82 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Outer Loop Power Control
Why we need outer loop power control ?
The main reason of outer loop power control:
• The QoS of Signalling or Traffic is BLER, not SIR.
The purpose of outer loop power control:
• The aim is to maintain the communication quality at
the level required by the service through adjustment
of SIR target.
83 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Outer Loop Power Control (Cont.)
There are two types of outer loop power control, such as DCH outer loop power control algorithm and E-DCH outer loop power control algorithm.
This section describes the DCH outer loop power control algorithm based on the BLER or bit error rate (BER).
Outer loop power control is a part of the closed loop power control, used to maintain the communication quality at the level required by the
service bearer through adjustment of the SIRtarget. This power control acts on each DCH belonging to the same RRC connection.
The SIRtarget needs to be adjusted when the UE speed or the multi-path propagation environment changes, so that the communication quality can
remain unaffected.
The adjustment of the SIRtarget is based on the BLER or BER. When PC_OLPC_SWITCH under the PcSwitch parameter is selected, there are two
cases:
If there is data transmission in the uplink, the SRNC adjusts the SIRtarget based on the BLER.
If there is no data transmission in the uplink, the SRNC adjusts the SIRtarget based on the BER.
When PC_OLPC_SWITCH under the PcSwitch parameter is deselected, the SIRtarget is fixed and the uplink outer loop power control for all UEs is
deactivated.
The enhanced outer loop power control can identify scenarios where uplink load is wasted, and implement fast target SIR increase or decrease, so
that the average target SIR in the uplink can be reduced, reducing the uplink power load waste and improving the uplink capacity
Downlink outer loop power control is implemented by the UE. Therefore, downlink outer loop power control is determined by the UE manufacturer.
84 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Outer Loop Power Control
Diagram above show the uplink outer loop power control process.
Uplink outer-loop power control is performed in the SRNC. The SRNC measures the received BLER and compares it with the BLERtar :
• If the BLERmea is greater than the BLERtar, the SRNC increases the SIRtar.
• If the BLERmea is smaller than the BLERtar, the SRNC decreases the SIRtar.
After adjusting the SIRtar, the SRNC sends the new SIRtar to the NodeBs for uplink inner loop power control through Frame Protocol
(FP) frames.
85 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Initial SIR Setting & Adjusting the SIR Target
The initial SIR target value (Init_SIR_target) is service-dependent and is provided by the RNC to the NodeB
For the SRB and TRB, the values of SIR target, Max_SIR_target and Min_SIR_target must fullfil the following requirement:
Min_SIR_target ≤ SIR target ≤ Max_SIR_target
The initial SIR target value is transmitted to the NodeB by using NBAP signalling of each RADIO LINK SETUP or RADIO LINK
RECONFIGURATION PREPARE messages.
Where:
i is the ith transport channel
n is the nth adjustment period
86 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Initial SIR Target
Please find the above formula use to calculate the SIR target.
According to the formula above,
• SIRtar(n) is the target SIR used for the n:th adjustment period.
• MAX means the maximum value among the total i transmission channels.
• BLERmeas,i (n) is measured for the i:th transmission channel in the n:th adjustment period.
• BLERtar,i is the target BLER of the i:th transmission channel.
• Stepi is the adjustment step of the i:th transmission channel.
• Factor is the adjustment factor.
In case of multi-service:
• The maximum value of the SIR target among multiple services is used for the SIR target adjustment.
• If one of the services requires increase in the SIR target, the reconfigured SIR target cannot exceed that maximum value.
• The maximum value can be decreased only when all the services require decrease in the SIR target.
87 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
SIR Target Adjustment Limitation
The parameter Max_SIR_increase_step and Max_SIR_decrease_step limit the adjustment range of the SIRtar, and the
algorithm is:
Where
∆SIRtar is the adjustment of SIRtar, and ∆SIRtar = SIRtar(n+1) – SIRtar(n)
ABS(∆SIRtar) means absolute value of ∆SIRtar.
88 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
BLER-based Uplink Outer Loop Power Control Parameter ex.
Parameters of BLER-based outer loop power control on RAB basis
Service Target Value of Service InitSir MaxSir MinSir SirAdjust SirAdjust MaxSir MaxSir
DCH_BLER target target target Period Step StepUp StepDn
SRB 3.4 kbit/s –20 102 132 62 4 4 400 200
SRB 13.6 kbit/s –20 122 132 62 2 10 500 200
AMR 12.2 kbit/s –20 102 132 62 2 5 500 200
CSD 64 kbit/s –27 122 152 62 2 2 1000 100
PS I/B 8 kbit/s –20 102 132 62 4 4 400 200
PS I/B 16 kbit/s –20 102 132 62 2 4 400 200
PS I/B 32 kbit/s –20 102 132 62 2 4 400 200
PS I/B 64 kbit/s –20 102 132 62 2 4 400 200
PS I/B 128 kbit/s –20 102 132 62 2 4 400 200
PS I/B 144 kbit/s –20 107 137 62 2 4 400 200
PS I/B 256 kbit/s –20 122 152 62 2 4 400 200
PS I/B 384 kbit/s –20 142 172 62 2 4 400 200
For different traffic classes, the adjustment step, maximum increase, maximum decrease of SIRtarget vary. Therefore, such variables are configured
according to the traffic class. Table above lists recommended parameter settings of typical services.
All the above parameters can be configure using this MML command -> Add Typical RAB OLPC Parameters(ADD UTYPRABOLPC)
Guidance Notes :
• CSD: CS data services
• I/B: Interactive and Background
89 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Outer Loop Power Control Parameters
BLERQuality (MO : Radio-> UTYPRABBASIC-> UTYPRABSUBFLOW->UTYPRABOLPC) – Impact Area (QOS)
Parameter Name: Target value of service DCH_BLER
GUI Value Range : -63~0
Actual Value Range : 0.0000005~1(Actual Value = 10^(GUI Value/10))
Recommended value : None
Feature ID : (WRFD-020503) ; Feature Name : (Outer Loop Power Control)
Guidance Notes :
Actual value of the target BLER of DCH based on the GUI value of this parameter. The setting of the "SirAdjustStep" parameter is
associated with this parameter. Assume that this parameter is changed from BLERQualityTarget1 to BLERQualityTarget2 and
"SirAdjustStep" is changed from SirAdjustStep1 to SirAdjustStep2.
Then, these values should fulfil the following condition: (1 - BLERQualityTarget1) x SirAdjustStep1/BLERQualityTarget1 = (1 -
BLERQualityTarget2) x SirAdjustStep2/BLERQualityTarget2.
For details about this parameter, see 3GPP TS 25.331.
Guidance Notes :
The larger the value of this parameter ->The higher the BLER/ The lower the target SIR/ The worse the QoS. This will reduces the user
throughput.
The smaller the value of this parameter, the lower the BLER and the higher the target SIR. This will reduces the cell throughput or
increases the total received power of the cell.
90 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Outer Loop Power Control Parameters (Cont.)
PC_OLPC_SWITCH (MO : Radio -> UCORRMALGOSWITCH) Impact Area - Capacity
This is one switch in PcSwitch (Power control switch) parameter, when the switch is on, the RNC updates the UL SIR
TARGET of radio links on the NodeB side through IUB DCH FP in-band signalling
GUI Value range: 1, 0
Physical value range: ON, OFF
Set this parameter through SET UCORRMALGOSWITCH
91 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Uplink Outer Loop Power Control Based on BER
• The OLPC based on the BER is similar to the OLPC base on the BLER, but the BER is used as the control object.
• When the UE is in discontinuous transmission (DTX) mode, the RNC cannot receive data or update the BLER. Therefore,
the BER is used to solve this problem.
• In an optimal condition, the BER target is the average BER after filtering within the adjustment period. The BER target is
obtained before the DTX period starts during the outer-loop power control period. During soft handover, the BER
target is the minimum value among all the links. When the BLER is a constant, the BER on the DPCCH can vary within a
limited range.
• If the UE is in DTX, the NodeB measures the BER on the UL DPCCH and send it to RNC through IUB DCH FP Frame.
• Upon receiving the BER, the RNC compares it with the BER target.
If the measured BER is greater than the BER target, the OLPC increases the SIR target.
If the measured BER is smaller than the BER target, the OLPC decreases the SIR target.
Please configure BER target using this MML command -> Add Typical RAB OLPC Parameters(ADD UTYPRABOLPC)
92 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Downlink Outer Loop Power Control
• The downlink outer loop power control is implemented
inside the UE. Therefore, this algorithm is specified by
UE manufacturer.
• The information signalled to the UE by the RNC is a
quality target for each radio bearer, expressed as a
BLER target. Then, depending on the manufacturer
specific outer-loop power control algorithm, an initial
SIR target value can be deduced from this BLER value.
• Generally, the UE L3(RRC Layer) measures the received
BLER and compares it with the BLERtar :
If the BLERmea is greater than the BLERtar, the L3
increases the SIRtar and send it to UE L1(Physical Layer).
If the BLERmea is smaller than the BLERtar, the L3
decreases the SIRtar.
93 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
• Overview of Power Control
• Open Loop Power Control
• Closed Loop Power Control
• Enhancement
94 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Enhancement
95 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Contents
Enhancement
4.1 Power Control Enhancement
4.2 DPCH Maximum Power Restriction
4.3 UE Transmit Power Insufficiency
4.4 RTWP Abnormal Increase
96 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Power Control Enhancement
97 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DPCH Pilot Power Adjustment
Downlink DPCHs include downlink DPDCHs and the downlink DPCCH. As a part of the DPCCH, the pilot field is used by UEs
to estimate the signal-to-interference ratio (SIR) during the inner loop power control procedure and to determine
whether radio links are synchronized.
When the cell load is light, the pilot field can be assigned higher transmit power and a longer bit length to increase the
SIR estimation accuracy and Uu-interface synchronization probability.
When a cell serves a large number of UEs, downlink R99 services consume a large amount of downlink power. As a result,
the remaining downlink power becomes insufficient to admit potential UEs. In addition, the amount of downlink power
available for HSDPA services decreases, which reduces HSDPA throughput. To address this situation, the WRFD-150230
DPCH Pilot Power Adjustment feature is introduced. This feature saves DPCH power by configuring a shorter bit length
and a smaller power offset for the pilot field. The saved power can be used to admit more UEs or to increase HSDPA
throughput.
• This section describes the WRFD-150230 DPCH Pilot Power Adjustment feature, which correlates with Power of
Downlink DPCCH in section Downlink Open Loop Power Control on DPCH
98 © 2017 Nokia
Power Control Enhancement
This feature is controlled by PC_PILOT_PO_OPTI_SWITCH under the PcSwitch parameter.
When downlink non-HSPA power load in a cell is the same as or heavier than the LoadStateForPilotPwrAdj parameter value, this
feature configures the pilot-field bit length and power offset as follows during the initial access procedure:
• Pilot-field bit length
• Applied only for DPCHs with Spreading Factor = 256
• If no real-time services (conversational services such as emergency calls, or streaming services) are established, then
parameter DlDpchSf256OptiPilotBit sets pilot-field bit length.
• If real-time services are established, then parameter DlDpchSf256PilotBit sets pilot-field bit length.
• Pilot-field power offset
• If real-time services are established on the downlink DPCH, the pilot-field power offset is set by parameter CsOptiPilotPo .
• If no real-time services are established on the downlink DPCH, the pilot-field power offset is set by parameter
NonCsOptiPilotPo .
When DL non-HSPA power load in a cell is lighter than the LoadStateForPilotPwrAdj parameter value, the pilot-field bit length is
determined by the value of the DlDpchSf256PilotBit parameter (only for the DPCH whose spreading factor is 256) and the pilot-field
power offset is determined by the value of the PilotPO parameter.
99 © 2017 Nokia
Power Control Enhancement (Cont.)
Notes :
DPCH pilot-field power offset configuration during the initial access procedure occurs when the downlink DPCH is established in any
of the following scenarios:
1) The UE initiates an RRC connection setup procedure in the cell that the UE accesses.
2) The UE switches from the URA_PCH, CELL_PCH or CELL_FACH state to the CELL_DCH state.
3) An incoming inter-cell hard handover occurs in the cell.
4) The UE falls back from HSDPA channels to R99 channels.
For descriptions of the power load state specified by the LoadStateForPilotPwrAdj parameter, see related descriptions in "Load-
related Measurement Quantities" of Load Control Feature Parameter Description.
• PC_PILOT_PO_OPTI_SWITCH: Sets small pilot power offset and small number of bits for pilot bits in case of downlink cell non-
HSPA power congestions to decrease power congestions.
• When this switch is turned on and the downlink non-HSPA power resources of the cell are in a congestion state specified by
"LoadStateForPilotPwrAdj"("SET UFRC"/"ADD UCELLFRC") or higher, "NonCsOptiPilotPo"("SET UFRC") or "CsOptiPilotPo"("SET
UFRC") specifies the pilot power offset on the DPCH. When the spreading factor (SF) is 256, "DlDpchSf256OptiPilotBit"("SET
UFRC") specifies the number for bits of pilot bits on the DPCH.
• Regardless of the switch state, when the downlink non-HSPA power resources of the cell are in a lower congestion state than
the state specified by "LoadStateForPilotPwrAdj"("SET UFRC"/"ADD UCELLFRC"), "PilotPo"("SET UFRC") specifies the pilot power
offset on the DPCH. When the SF is 256, "DlDpchSf256PilotBit"("SET UFRC") specifies the number for bits of pilot bits on the
DPCH.
Guidance Notes:
If the parameter is set to a large value (indicating the corresponding enumerated value is closer to the right-end value), the DL DPCH pilot
power offset adjustment algorithm is difficult to be triggered. As a result, the DL DPCH power load cannot be effectively reduced.
If the parameter is set to a small value (indicating the corresponding enumerated value is closer to the left-end value), the DL DPCH pilot
power offset adjustment algorithm can be easily triggered. However, this increases the call drop rate in the case of light DL DPCH power
load.
Function: Use this command to add the Cell-Oriented Fundamental Resource Configuration (FRC) parameters. The FRC function includes
two aspects:
• Allocation of channel type and bandwidth based on service requests.
• Configuration of channel parameters based on the Quality of Service (QoS) requirements.
Guidance Notes :
A larger parameter value indicates more accurate estimated SIR and more DL DPCH power.
A smaller parameter value indicates a higher probability of estimated SIR error rate and less DL DPCH power.
Function
Use this command to set the RNC-Oriented Fundamental Resource Configuration (FRC) parameters.
The FRC function includes two aspects:
• Allocation of channel type and bandwidth based on service requests.
• Configuration of channel parameters based on the Quality of Service (QoS) requirements.
Guidance Notes:
When this parameter is set to D8, the number of downlink DPCCH pilot bits increases. In this case, UEs can obtain more accurate SIRs but the
transmit power of DPCCH pilots is high. To reduce the transmit power of these pilots, you can use a small pilot power offset for these pilots. By
doing this, the downlink cell capacity increases.
When this parameter is set to D2, the number of downlink DPCCH pilot bits decreases. In this case, UEs obtain less accurate SIRs and the transmit
power of DPCCH pilots is low. To increase the transmit power of these pilots, you can use a large pilot power offset for these pilots. By doing this,
the downlink cell capacity decreases.
Function: Use this command to set the RNC-Oriented Fundamental Resource Configuration (FRC) parameters. The FRC function includes two
aspects:
• Allocation of channel type and bandwidth based on service requests.
• Configuration of channel parameters based on the Quality of Service (QoS) requirements.
Guidance Notes:
A larger parameter value indicates more DL DPCH power and decreased cell downlink capacity.
A smaller parameter value indicates less DL DPCH power and a higher probability of estimated SIR error rate.
Feature ID : (WRFD-020503,WRFD-150230) ; Feature Name : (Outer Loop Power Control,DPCH Pilot Power Adjustment)
Function: Use this command to set the RNC-Oriented Fundamental Resource Configuration (FRC) parameters. The FRC function includes
two aspects:
• Allocation of channel type and bandwidth based on service requests.
• Configuration of channel parameters based on the Quality of Service (QoS) requirements.
Guidance Notes:
A larger parameter value indicates more DL DPCH power and decreased cell downlink capacity.
A smaller parameter value indicates less DL DPCH power and a higher probability of estimated SIR error rate.
Function: Use this command to set the RNC-Oriented Fundamental Resource Configuration (FRC) parameters. The FRC function includes two
aspects:
• Allocation of channel type and bandwidth based on service requests.
• Configuration of channel parameters based on the Quality of Service (QoS) requirements.
Guidance Notes:
The smaller the value of this parameter: the lower the transmit power of pilot bits, the less accurate of the SIR assessment on the UE side,
the greater the downlink DPCCH transmit power fluctuation, and the higher the downlink DPDCH mean power.
The small parameter value also affects downlink cell capacity.
The larger the value of this parameter, the higher the transmit power of pilot bits. The large parameter value also wastes downlink power
resources and affects downlink cell capacity.
Function: Use this command to set the RNC-Oriented Fundamental Resource Configuration (FRC) parameters. The FRC function includes
two aspects:
• Allocation of channel type and bandwidth based on service requests.
• Configuration of channel parameters based on the Quality of Service (QoS) requirements.
107 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DPCH Maximum Power Restriction
108 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
DPCH Maximum Power Restriction
The downlink A-DPCH is used to transmit signalling messages and perform power control. When HSDPA services are being
connected, the A-DPCH consumes downlink power even though there are no signalling messages to transmit. If a cell serves a large
number of HSDPA UEs, the A-DPCH will consume a large amount of power, greatly reducing the available power for channels that
transmit HSDPA data.
To address this situation, the WRFD-150235 DPCH Maximum Power Restriction feature is introduced. This feature effectively
controls the maximum transmit power of the DL A-DPCH, which increases downlink system capacity.
Guidance Notes:
When this switch is turned on, the NodeB configures the maximum transmit power of the associated DPCH based on whether data is transmitted
on the associated DPCH for HSDPA services. If no data is transmitted on the associated DPCH for HSDPA services, the NodeB reduces the
maximum transmit power of the associated DPCH to improve the HSDPA throughput.
SET ULOCELLALGPARA:
• Whether to enable the DPCH maximum transmit power restriction algorithm. When this switch is turned on, the NodeB configures the
maximum transmit power of the associated DPCH based on whether data is transmitted on the associated DPCH for HSDPA services. When this
switch is turned off, the maximum transmit power of the associated DPCH for HSDPA services is set to the default value.
SET ULOCELLALGPARA:
• Load state when the DPCH maximum power restriction algorithm takes effect. When the downlink non-HSPA power load is in the load state set
by this parameter or a heavier load state, the maximum DPCH power restriction algorithm is triggered.
• Based on load level in ascending order (from light load to heavy load), the downlink non-HSPA power load states are as follows:
• DlLightState: indicates the downlink resource light load state threshold 0%.
• DlNormalState: indicates the downlink resource normal load state threshold 30%.
• DlLoadedState: indicates the downlink resource light congestion state threshold 50%.
• DlHeavyState: indicates the downlink resource severe congestion state threshold 70%.
• DlOverloadState: indicates the downlink resource extreme congestion state threshold 90%. The following provides the method for
determining the downlink non-HSPA power load state:
Guidance Notes:
Setting this parameter to a large value increases the downlink transmit power of a single radio link, thereby reducing the downlink capacity.
Setting this parameter to a small value reduces the coverage area for services and increases the probability of call drops.
Function
Use this command to add transmit power parameters of the DL link in a cell.
• The RNC sets the maximum and minimum transmit power of the RL carrying a single service based on the values of
parameters CNDomainId and MaxBitRate.
• The RNC calculates the maximum and minimum power of an RL carrying combined services based on the used SF and the maximum and
minimum power of the involved services.
113 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
UE Transmit Power Insufficiency
114 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
UE Transmit Power Insufficiency
The RNC sends the NodeB a DEDICATED MEASUREMENT INITIATION REQUEST message containing the measurement object of the
SIRerror.
SIRerror = Smeas – SIRtarget
• The NodeB reports event F to the RNC. Event F consists of event Fa and event Fb.
• If the SIRerror is lower than the threshold (–3 dB) of event Fa for a period of time (80 ms), event Fa is triggered.
• If the SIRerror is equal to or higher than the threshold (–3 dB) of event Fb for a period of time (80 ms), event Fb is triggered.
If the RNC receives the measurement report containing the event Fa from all the radio link sets of a UE, the RNC determines that
the link quality is poor and the UE transmit power is insufficient.
Then, the RNC sets the SIRtarget to the initial SIRtarget (InitSirtarget) and disables SIRtarget adjustment.
• In this way, the transmit power insufficiency does not raise the SIRtarget excessively. After the UE transmit power becomes
sufficient, less uplink power is wasted.
If the RNC receives the measurement report containing the event Fb from any radio link set of the UE, the RNC determines that the
link quality resumes and the UE transmit power becomes sufficient. Then, the RNC enables the SIRtarget quick decrease.
The enhanced feature is enabled by PC_OLPC_FastDown_Optimize_SWITCH under the PCSwitch parameter.
117 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
RTWP Abnormal Increase
118 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
RTWP Abnormal Increase
In this scenario, the enhanced feature is controlled by RTWPSIRTGTADJSW.
When the RTWP increases abnormally due to limited cell capacity, the NodeB determines the RTWP abnormal increase scenario according to the
slight congestion threshold and severe congestion threshold, and adjusts the SIRtarget from the RNC for DTX UEs and non-DTX UEs separately.
This decreases the RTWP or increases cell uplink capacity.
Notes:
• HSUPA UEs with no data transmission for more than 200 ms are regarded as DTX UEs. When data transmission resumes, the HSUPA UEs are
regarded as non-DTX UEs.
• UEs over DCH are regarded as non-DTX UEs by default. For details about DTX, see HSPA Evolution Feature Parameter Description.
The above diagram shows the procedure for enhanced outer loop power control in the RTWP abnormal increase scenario.
The following describes the procedure for enhanced outer loop power control in the RTWP abnormal increase scenario.
1. The NodeB adjusts the SIRtarget received from the RNC for different types of UE. The SIRtarget is adjusted as follows:
For a non-DTX UE
• Non-DTX UE over DCHSIRtarget = max{SIRtarget from the RNC + min{DCHDeltaSIRtargeti, i=1,...}, min{SIRtarget from the RNC, 0 dB}}
• A UE has only one SIRtarget. When multiple radio links have been established on the UE, the radio link with the smallest adjustment
(DCHDeltaSIRtarget) is used for calculating the SIRtarget.
• Non-DTX UE over E-DCHSIRtarget = max{SIRtarget from the RNC + min{EDCHnonDTXDeltaSIRtargeti, i=1,...} + min{EDCHDTXDeltaSIRtargeti,
i=1,...}, min{SIRtarget from the RNC, 0 dB}}
• A UE has only one SIRtarget. When multiple radio links have been established on the UE, the radio link with the smallest adjustment
(EDCHDTXDeltaSIRtarget or EDCHnonDTXDeltaSIRtarget) is used for calculating the SIRtarget.
For a DTX UE over E-DCHSIRtarget = max{SIRtarget from the RNC + min{EDCHDTXDeltaSIRtargeti, i=1,...}, min{SIRtarget from the RNC, 0 dB}}
A UE has only one SIRtarget. When multiple radio links have been established on the UE, the radio link with the smallest adjustment
(EDCHDTXDeltaSIRtarget) is used for calculating the SIRtarget.
Notes: The subscript "i" indicates the radio link number in the radio link set.
• Tools that use for MML Command = U2000 or LMT ( BSC6900/6910/DBS3900) or (RNC or NodeB)
• All the details of Features and Parameters will refer to “HW2 Feature License Counter Parameters Macro v1 1” & “HW2 Huawei Recommended
Parameters v 1.1”
Please click below link for detail reference of Parameters and Features License Information.
124 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>
Copyright and confidentiality
The contents of this document are proprietary and names of their respective owners.
confidential property of Nokia. This document is Nokia operates a policy of ongoing development.
provided subject to confidentiality obligations of the Nokia reserves the right to make changes and
applicable agreement(s). improvements to any of the products and/or
services described in this document or withdraw this
This document is intended for use of Nokia’s document at any time without prior notice.
customers and collaborators only for the purpose
for which this document is submitted by Nokia. No The contents of this document are provided "as is".
part of this document may be reproduced or made Except as required by applicable law, no warranties
available to the public or to any third party in any of any kind, either express or implied, including, but
form or means without the prior written permission not limited to, the implied warranties of
of Nokia. This document is to be used by properly merchantability and fitness for a particular purpose,
trained professional personnel. Any use of the are made in relation to the accuracy, reliability or
contents in this document is limited strictly to the contents of this document. NOKIA SHALL NOT BE
use(s) specifically created in the applicable RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
agreement(s) under which the document is DOCUMENT or for any loss of data or income or any
submitted. The user of this document may special, incidental, consequential, indirect or direct
voluntarily provide suggestions, comments or other damages howsoever caused, that might arise from
feedback to Nokia in respect of the contents of this the use of this document or any contents of this
document ("Feedback"). document.
Such Feedback may be used in Nokia products and
related specifications or other documentation. This document and the product(s) it describes
Accordingly, if the user of this document gives Nokia are protected by copyright according to the
Feedback on the contents of this document, Nokia applicable laws.
may freely use, disclose, reproduce, license,
distribute and otherwise commercialize the Nokia is a registered trademark of Nokia
feedback in any Nokia product, technology, service, Corporation. Other product and company names
specification or other documentation. mentioned herein may be trademarks or trade
126 © 2017 Nokia <Document ID: change ID in footer or remove> <Change information classification in footer>