Documente Academic
Documente Profesional
Documente Cultură
Feature Guide
Power Control
Power Control
Version Date Author Reviewer Notes
TABLE OF CONTENTS
FIGURES 4
TABLES 5
2 Overview ............................................................................................................ 6
2.1 Feature Introduction ............................................................................................. 6
2.1.1 ZWF21-04-009 Power Control ............................................................................. 6
2.1.2 ZWF21-04-008 Downlink Power Balancing .......................................................... 8
2.2 License Control .................................................................................................... 8
2.3 Correlation With Other Features .......................................................................... 9
4 Parameters....................................................................................................... 47
4.1 ZWF21-04-009 Power Control ........................................................................... 47
4.1.1 Uplink Open Loop Power Control Parameters.................................................... 47
4.1.2 Downlink Open Loop Power Control Parameters ............................................... 51
4.1.3 Uplink Inner Loop Power Control Parameters .................................................... 56
4.1.4 Downlink Inner Loop Power Control Parameters ................................................ 64
4.1.5 Uplink Outer Loop Power Control Parameters ................................................... 64
4.1.6 Downlink Outer Loop Power Control Parameters ............................................... 71
4.2 ZWF21-04-008 Downlink Power Balancing ........................................................ 75
4.2.1 Downlink Power Balancing Parameters ............................................................. 75
4.2.2 Node B Dedicated Measurement Parameters .................................................... 76
FIGURES
Figure 3-1 Service Related Power Control Parameter Configuration Flowchart .................20
Figure 6-1 Parameter Configuration Interface 1 .................................................................85
Figure 6-2 Parameter Configuration Interface 2 .................................................................86
Figure 6-3 Parameter Configuration Interface 3 .................................................................87
Figure 6-4 Parameter Configuration Interface 4 .................................................................89
Figure 6-5 Parameter Configuration Interface 5 .................................................................90
Figure 6-6 Parameter Configuration Interface 6 .................................................................92
Figure 6-7 Parameter Configuration Interface 7 .................................................................94
Figure 6-8 Parameter Configuration Interface 8 .................................................................95
Figure 6-9 Parameter Configuration Interface 9 .................................................................96
Figure 6-10 Parameter Configuration Interface 10 .............................................................97
Figure 6-11 Parameter Configuration Interface 11 .............................................................98
Figure 6-12 Parameter Configuration Interface 12 .............................................................98
Figure 6-13 Parameter Configuration Interface13 ..............................................................99
Figure 6-14 Parameter Configuration Interface 14 ...........................................................100
Figure 6-15 Parameter Configuration Interface 15 ...........................................................101
Figure 6-16 Parameter Configuration Interface 16 ...........................................................102
Figure 6-17 Parameter Configuration Interface 17 ...........................................................104
Figure 6-18 Parameter Configuration Interface 18 ...........................................................105
Figure 6-19 Parameter Configuration Interface 19 ...........................................................107
Figure 6-20 Parameter Configuration Interface 20 ...........................................................109
Figure 6-21 Parameter Configuration Interface 21 ...........................................................110
Figure 6-22 Parameter Configuration Interface 22 ...........................................................111
Figure 6-23 Parameter Configuration Interface 23 ...........................................................112
Figure 6-24 Parameter Configuration Interface 24 ...........................................................113
Figure 6-25 Parameter Configuration Interface 25 ...........................................................113
Figure 6-26 Parameter Configuration Interface 26 ...........................................................114
TABLES
1 Feature Attribute
RNC version: [ZXWR RNC V3.14.10.14 / ZXUR 9000 V4.14.10.14]
Attribute: [Basic]
Involved NEs:
NE Name Related or Not Special Requirement
UE √ None
Node B √ None
RNC √ None
iTC - None
MSC - None
MGW - None
SGSN - None
GGSN - None
HLR - None
“√”: involved
“-”: not involved
2 Overview
This feature is only for R99 power control. For the power control algorithms for HSDPA,
HSUPA and DC-HSUPA, refer to the ZTE UMTS HSDPA Introduction Feature Guide,
ZTE UMTS HSUPA Introduction Feature Guide, and ZTE UMTS DC-HSUPA Feature
Guide.
Power control includes uplink power control and downlink power control. Uplink power
control is used to eliminate near-far effect and ensure the system capacity and QoS.
Downlink power control is used to increase the system capacity on the condition that the
QoS is guaranteed. The ZTE RAN system supports power control on both downlink and
uplink connections.
In the uplink OLPC, the uplink reception quality is estimated by the RNC based on
the uplink service quality or DPCCH BER (namely, Quality Estimate (QE)) reported
by the Node B. Here the uplink service quality is evaluated through the CRC code
carried in the Frame Protocol (FP). The ZTE RAN performs uplink OLPC based on
the uplink service quality and DPCCH BER (QE). When only the uplink service
quality is considered, it takes a long time to adjust SIRtarget to a proper value after
the channel condition gets better suddenly. Moreover, at the beginning of
transmission, SIRtarget is usually set to a large value to ensure secure
communication. It also takes a long time to make SIRtarget reach an ideal value at the
initial convergence. The DPCCH BER evaluates and reacts to radio conditions
more quickly and accurately, so both DPCCH BER and service quality are taken
into account in the uplink OLPC. Additionally, the step of downgrading SIRtarget is
adjustable, which facilitates speeding up SIRtarget convergence when the radio
condition gets better suddenly.
compares the received uplink SIR with the SIRtarget specified by OLPC, and then
sends the power control command to a UE to adjust the transmit power, so that the
SIR value changes quickly to reach the SIRtarget. If the measured SIR is lower
(higher) than the SIRtarget, the Node B uses the power control command to notify the
UE to increase (decrease) its transmit power. The downlink power control is the
same as uplink power control, except that the power control command is sent by the
UE and executed in the Node B.
Both outer loop power control and inner loop power control are closed loop power
control.
In the macro diversity status of a soft handover, a UE can communicate with all cells in
the active set. In this situation, the UE sends the same TPC commands to the cells in the
active set. The links have different transmission paths, so error codes will be produced in
the TPC commands, and some Node Bs receive wrong TPC commands. As a result,
some Node Bs increase their transmit power and some Node Bs decrease their transmit
power. Therefore, power drifting occurs. If the received power of different links differs a
lot, a high block error rate is caused after the combination of macro diversities on the UE,
and the gain of soft handover is decreased.
The ZTE RAN system uses downlink power balancing to eliminate power drifting. The
RNC allocates a reference or common reference power benchmark for each radio link in
the active set. The Node B calculates the power of each link adjusted as a result of power
balancing and adds the value to the power value used for downlink inner loop power
control. In this way, the power drifting is solved on the radio link.
1. Required Features
None
None
3. Affected Features
None
3 Technical Description
The uplink open loop power control of a common channel is to determine the PRACH
transmit power.
In FDD mode, when a UE transmits the first preamble of PRACH, it calculates the initial
Where,
Primary CPICH DL TX power is the transmit power of the primary CPICH channel,
and its value is obtained from the UUtranCellFDD.primaryCpichPower parameter.
The UE obtains the primary CPICH DL TX power from System Information Block
type 6 (SIB 6) (or SIB 5 if SIB 6 is not broadcast).
Constant Value is a value related to the cell environment and tower mounted
amplifier (TMA) configuration. It is calculated by the following formula:
Where,
ulRxGain_TMA is the uplink Rx gain provided by the TMA, and its value is
obtained from the UCelInfoFDD.ulRxGainTMA parameter. When the TMA is
installed, the gain of the antenna feeder is produced, and the parameter is set
to the gain value. When the TMA is not installed, this parameter is set to 0.
The UE obtains the constant value from SIB 6 (or SIB 5 if SIB 6 is not broadcast).
If the parameters in the system broadcast information change, the UE calculates the
initial transmit power again and submits the result to the physical layer.
When the physical random access process is started, the UE sets the preamble transmit
power as Preamble_Initial_Power. If the value of Preamble_Initial_Power exceeds the
maximum power UUtranCellFDD.maxRachTxPwr, the UE sets the preamble transmit
power to the maximum power. If no response (+1 or -1) is received through the AICH
after the preamble consisting of the selected signature and scramble is sent out, the UE
selects a new signature in the next timeslot, and uses it to form a preamble together with
the scramble, and then sends the preamble again. Next, the UE increases the preamble
transmit power by the Power Ramp Step [dB]. If the number of preamble transmissions
reaches the maximum number of retransmissions, the UE will exit the physical random
access procedure. If the response (+1) is received through the AICH, the UE transmits a
random access message. The power of the control part of the random access message
is the last transmit power of the preamble plus the offset P p-m [dB].
From the above description we get the formula for calculating the transmit power of the
control part of the PRACH message:
er PowerRampStep P p - m
wer Preamble_Initial_Pow
PRACH_C_Po
(3.1-2)
Where,
Power Ramp Step is the power offset between two continuous preambles. It is
obtained from the UPrach.pRStep parameter.
Pp_m is the power offset between the control part of the PRACH message part and
the last preamble, and its value is 2dB.
In addition, PRACH is similar to the uplink DPCH. That is, its data field and control field
are sent out after being multiplexed with I and Q channels and then added by scramble
c d
on the physical layer. Therefore, the parameters and (gain factor of the control
c
channel and data channel of the message part) also need to be determined. Here,
d
is 11, and is 15.
The UL interference can be updated in SIB 7 in two ways, which is configured by the
UUtranCellFDD.sIB7Originator parameter.
3.1.1.2 Uplink Open Loop Power Control of the R99 Dedicated Channel
Uplink open loop power control of the dedicated channel is to determine the initial
c d
transmit power of DPCCH, and the gain factors and of the uplink control
As required by the related standard, a UE should start uplink inner loop power
control according to the following power level when the first DPCCH is being set up:
Where,
(3.1-4)
Where,
Eb/N0 is the quality factor of the DPCCH PILOT field. It is related to the service
type, and obtained from the USrvDivPc.dpcchPilotEbN0 parameter.
NT+IT is the uplink interference, namely, RTWP, which is reported by the Node
B through the common measurement report (RTWP) and updated in real time
in SIB 7.
ULRxGain_TMA is the uplink Rx gain provided by the TMA, and its value is
obtained from the UCelInfoFDD.ulRxGainTMA parameter. When the TMA is
installed, the gain of antenna feeder is produced, and the parameter is set to
the gain value. When the TMA is not installed, the parameter is set to 0.
Note: The quality factor of the DPCCH PILOT field is related to the cell load
scenario, diversity mode, and service type.
Different strategies are used according to the features of a single service and
multi-service:
TFC Format c d
TFC Format c d
TFC Format c d
TFC Format c d
TFC Format c d
0×336, 0×144 15 1
1×336, 0×144 15 14
2×336, 0×144 11 15
4×336, 0×144 8 15
0×336, 1×144 15 8
1×336, 1×144 14 15
2×336, 1×144 10 15
4×336, 1×144 8 15
TFC Format c d
0×336, 0×144 15 1
1×336, 0×144 15 14
2×336, 0×144 11 15
4×336, 0×144 8 15
8×336, 0×144 6 15
TFC Format c d
0×336, 1×144 15 9
1×336, 1×144 14 15
2×336, 1×144 10 15
4×336, 1×144 8 15
8×336, 1×144 6 15
Table 3-5 c and d Values for the UL PS384kbps and Services With Higher Rates
Streaming/Interactive/Background Service
TFC Format c d
0×336, 0×144 15 1
1×336, 0×144 11 15
2×336, 0×144 8 15
4×336, 0×144 8 15
8×336, 0×144 6 15
12×336, 0×144 5 15
0×336, 1×144 15 8
1×336, 1×144 10 15
2×336, 1×144 8 15
4×336, 1×144 8 15
8×336, 1×144 6 15
12×336, 1×144 5 15
ii. For multi-service, the c and d values are calculated by the RNC and
configured for the UE.
(1) For the transmission combination (TFCmulti) when services A and B are
combined, the number of bits per frame mapped to the transport channel by each
(2) The service with more bits transmitted in a frame is selected as the reference
service, and the service corresponding to the TFI that corresponds to TFCmulti is
selected as the reference service.
(4) The following formula is used to calculate and obtain the c and d
corresponding to this TFCmulti.
d ,r ef Lr ef Kj
Aj
c ,r ef Lj K r ef
(3.1-5)
c, j
If Aj > 1, then d , j 1.0 and is the maximum quantified value that
c, j 1 / 15 .
d, j
If Aj <= 1, then is the minimum quantified value that satisfies the
Where,
c,ref and d,ref are the gain factors corresponding to the above mentioned
TFCsingle. c,j and d,j are the gain factors corresponding to the j
th
type of
TFCmulti.
Lref is the number of dedicated physical channels needed by the number of bits
to be sent out in the case of TFCsingle.
L,j is the number of dedicated physical channels needed by the number of bits
to be sent out in the case of TFCmulti.
K r ef RM i N i
i
Where: RMi is the semi-static rate matching factor of transport channel i in the
TFCsingle combination; Ni is the number of bits mapped from transport channel i to a
radio frame before rate matching is performed. ∑ refers to summing up all transport
channels in the TFC.
K j RM i N i
i
The parameters in this formula have the same meanings as those in the previous
formulas. But ∑ refers to summing up all transport channels in the TFCj (TFCmulti).
4. To ensure that the power of the data channel reaches the required value before
data is transmitted, the power control preamble is sent before data transmission on
the uplink dedicated channel. In addition, closed loop power control is already
performed while the power control preamble is sent out. The length of the preamble
depends on the UCelInfoFDD.dpcchPcpLen parameter. At the same time, when
uplink DPDCH data is sent, no RB0–RB4 signaling is included in the first several
frames. The number of delayed signaling frames depends on the
UCelInfoFDD.srbDelay parameter.
3.1.1.3 Uplink Open Loop Power Control of the R99 in Compressed Mode
The gain factors c,C,j and d,C,j corresponding to a certain TFC used by the compressed
frame in compressed mode are obtained from c and d used by radio frames in normal
mode. The formula is as follows:
15 N pilot ,C
AC , j Aj
Nslots,C N pilot , N
(3.1-6)
Where,
Npilot,C is the number of pilot bits per timeslot in the compressed frame in
compressed mode
Nslots,C is the number of timeslots used for data sending in the compressed
frame in compressed mode.
AC,j is obtained by the above formula when the current frame is compressed. The
following rules are then used to obtain the values of d,c,j and c,C,j.
c,C, j
If AC,j > 1, then d ,C , j 1.0 and is the maximum quantified value that
c,C, j
satisfies the condition that <= 1 / Aj . Note: If c ,C , j 0 is obtained,
then c ,C , j 1 / 15 .
d, j
If AC,j <= 1, then is the minimum quantified value that satisfies the
d, j
condition that >= Aj, and c, j 1.0 .
2. The configuration profile (USrvPcProfile) that includes the power control parameters
for all service types is obtained through UUtranCellFDD.refUSrvPcProfile matching
with USrvPcProfile.profileId. These parameters are related to the load scenario
indicated by USrvPcProfile.intialloadscene. Then the power control parameters
used for a service type matching with USrvPc.srvType are obtained from the child
object (USrvPc) of the configuration profile (USrvPcProfile).
3. Because some parameters for power control are related with transmit diversity
mode and the parameters are in the child object (USrvDivPc) of the object (USrvPc),
we need to match the actual transmit diversity mode of the user to
USrvDivPc.txDivMod and get the transmit diversity mode related the parameters for
power control for the service type.
UUtranCellFDD.refUSrvPcProfile USubSrv.srvType
USrvFunction::
USrvPcProfile::USrvPc USrvPc::USrvDivPc
USrvPcProfile
In the downlink direction, the initial transmit power of P-CPICH, S-CPICH, P-CCPCH,
SCH, AICH, PICH and S-CCPCH should be configured. These channels are downlink
common physical channels.
The power of P-CCPCH, P-SCH, S-SCH, AICH, and PICH depend on the offset to the
power of P-CPICH. BCH is mapped to the P-CCPCH physical channel. P-CCPCH power
is the same as that of BCH. In a non MIMO cell (cell portion), the S-CPICH power is
indicated by UScpich.scpichPwr.
Where,
Because the physical channel S-CCPCH bears the transport channels PCH and FACH,
and the number of FACH channels is not fixed, the transmit power of each PCH indicated
by UUtranCellFDD.pchPower and the maximum transmit power allowed for each FACH
indicated by USccpch.maxFachPwr borne by a certain S-CCPCH are specified in the
related protocol. Because the data rate of PCH is invariable, the transmit power of PCH
is determined by a fixed rate. The transmit power of FACH is determined by the
maximum data rate borne by this FACH. For different rates, the transmit power can be
measured in the actual environment. The transmit power of the data field of S-CCPCH
depends on the PCH transmit power and the maximum value of the maximum transmit
power of FACH borne on S-CCPCH. The transmit power of the TFCI field and Pilot field
of S-CCPCH are indicated respectively by the offsets PO1(USccpch.pO1) and
PO3(USccpch.pO3) relative to the transmit power of the data field.
3.1.2.2 Downlink Open Loop Power Control of the R99 Dedicated Channel
The transmit power of the downlink dedicated physical channel is related to the load of
the cell, interference, path losses, and rate of the bearer service. In the related protocol,
the initial transmit power of a specific dedicated channel is for the physical channel.
Therefore, the initial transmit power should be calculated separately for a single service
and multi-service. The estimation power algorithm based on CPICH Ec/N0 is used for
Ptx ,CPICH
min
Ptx ,init min max L k1 Ptx ,total PowerOffset
PG E c cpich
1 k 10 k2
N0
(3.1-7)
Where,
Ptx,CPICH
is transmit power of the P-CPICH (dBm), obtained from
UUtranCellFDD.primaryCpichPower.
Eccpich
N0 is CPICH Ec/No(dB) reported by the UE. For details refer to the
ZTE UMTS Admission Control Feature Guide. Note: The CPICH Ec/No in the
Iur interface is calculated by the CPICH Ec/No of the UE measurement result
minus URncFunction.iurEcNoDelta.
min is the lower limit of the downlink orthogonal factor. For details, refer to
the ZTE UMTS Admission Control Feature Guide.
max is the upper limit of the downlink orthogonal factor. For details, refer to
the ZTE UMTS Admission Control Feature Guide.
The rule for obtaining L from the measurement result reported from the UE is
as follows:
k1 and k2 are scenario parameters. The values of k1 and k2 vary with specific
scenarios, including a densely-populated urban area, suburban area, and rural
area.
Dense Urban Urban Suburb Rural
K1=–32.9116 K1=–53.5116 K1=–51.1716 K1=–48.8116
Ptx,total is the total transmit power of a cell before a UE accesses the cell. It is
obtained from the common measurement report (TCP- Transmitted Carrier
Power). Note: For an HS cell, Ptx,total is the valid load of TCP, and obtained
through the Node B's common measurement report HS-DSCH Required
Power and Transmitted carrier power of all codes not used for HS. Ptx,total =
MaxSpi
NOHSDSCHPower
Spi 0
HSDSCHRequiredPowerSpi
( ).
UCelInfoFDD.pOReEstab
Call Re-Establishment
lish
iii. For radio link reconfiguration, if the initial power needs to be calculated
again, the PowerOffset is 0.
To avoid excessive power usage of the dedicated channel, the maximum power
offset indicated by USrvDivPc.maxDlDpchPwr and minimum power offset indicated
by USrvDivPc.minDlDpchPwr of DPCH are specified in the 3GPP protocol.
N
DPCH _ Initial_ Power j DPCH _ Power
j 1 (3.1-8)
On the DPCH, the bits of TFCI, TPC and PILOT are also multiplexed besides the
data bits because the information carried by these bits is important. Therefore, the
needed power is also a little higher than that of the data field. The power value
depends on the offset relative to the power of the data field and is indicated by PO1
(USrvDivPc.dpchPO1), PO2 (USrvDivPc.dpchPO2) and PO3 (USrvDivPc.dpchPO3)
respectively.
ZTE supports the dynamic update PO2 function. When the dynamic update PO2
switch (ULogicalRnc.dynaUpdtPO2Sw) is turned on, the PO2 is dynamically
updated as follows:
The PO2 (USrvDivPc.dpchPO2) value is obtained based on the DPCH data rate
and traffic class. If DPCH bears multi-service, USrvDivPc.dpchPO2 values are
obtained respectively according to the service type, and then the minimum value is
obtained and sent to the Node B through the FP. If the DPCH data rate is changed,
then the new PO2 is obtained and sent to the Node B in the same way. Therefore,
PO2 dynamic update is completed.
2. Related measurement
TCP: Transmitted Carrier Power. The internal measurement value of the Node
B is obtained from the common measurement report and reported to the RNC.
The measurement is started after the cell is set up and the common transport
channel of the cell is set up, and ended after the cell is deleted.
CPICH Ec/N0: the SNR for reception of CPICH. When a service is set up, the
measurement result carried in the RRC connection request is used. In the
case of handover, the measurement result of the intra-frequency or
inter-frequency measurement report is used.
3.1.2.3 Downlink Open Loop Power Control of the R99 in Compressed Mode
Because the adjustment proportion of DPDCH transmit power is the same as that of the
control field for the downlink compressed mode, it is unnecessary to change the values
of PO1, PO2 and PO3. That means the power offset between the control part and data
part in the compressed mode is the same as that in normal mode.
3GPP TS 25.214 specifies the following methods for calculating inner loop power control.
At the receiving end, the SIR measurement (SIR=Eb/No) is performed for each
received radio link, and then the measurement result is compared with the
target SIR (SIRtarget) required by the service.
If SIR < SIRtarget, a TPC command whose bit value is 1 is returned through the
downlink control channel to the sender.
This section discusses how to select the proper inner loop power control algorithm. The
principles of inner loop power control for the uplink and downlink are the same.
Note about TPC: When the first radio link is set up between the UTRAN and UE, the
UTRAN cannot calculate the TPC by using the normal process before uplink
synchronization. Therefore, the UTRAN sends a fixed TPC pattern in the TPC bit of the
downlink DPCH. The TPC pattern should consist of UUtranCellFDD.dlTpcN instances of
the pair of TPC commands (0, 1), followed by one instance of TPC command 1. The TPC
pattern continuously repeats but should be forcibly restarted at the beginning of each
frame where CFN mod 4 = 0. The TPC pattern should be terminated once the uplink
synchronization is achieved.
3.1.3.1 Uplink Inner Loop Power Control of the R99 in Normal Mode
There are two uplink inner loop power control algorithms, which are described as follows:
For Algorithm 1, the transmit power of the sender can be adjusted in every timeslot.
The UE determines whether to increase or decrease the transmit power according
to the TPC command received in each timeslot.
Suppose the TPCs of all radio link sets are 1, then TPC_cmd = 1 (to increase
transmit power).
Suppose one TPC coming from any radio link set is 0, then TPC_cmd = –1
(TPC = 0 indicates the transmit power should be decreased).
For Algorithm 2, the transmit power of the sender is adjusted every five timeslots.
Rules for the UE to combine the TPC commands are different in the following two
cases.
When a single TPC is received in one timeslot: The transmit power is not adjusted
th
during the first four timeslots (TPC_cmd = 0). When the TPC command of the 5
timeslot is received, a soft decision is made: TPC_cmd = 1 if all the five TPC
commands are 1; TPC_cmd =–1 if all the five TPC commands are 0; TPC_cmd = 0
in other cases.
When several TPCs are received in one timeslot: The transmit power is not
adjusted during the first four timeslots of the five continuous timeslots
th
(TPC_cmd=0). At the 5 timeslot, the TPCi (i=1,2,…,N, N is the number of radio link
TPC commands from different radio link sets) is determined first. Next, the TPCs
are respectively combined according to the TPC command rule used for the case
where a single TPC is received to obtain N temporary TPC commands (TPC_temp).
Finally, the TPC_cmds are combined using the following rule:
N
1
N
TPC _ temp i 0.5
If i 1 , then TPC_cmd = 1.
TPC _ tempi
If any of is –1, then TPC_cmd = –1.
For Algorithm 1, inner loop power control is performed every timeslot, while for
Algorithm 2, inner loop power control is performed every five timeslots. That means
the frequency of inner loop power control for Algorithm 1 is higher. When the mobile
communication environment is quite unfavorable and the channel fades very quickly,
Algorithm 1 helps to converge the transmit power quickly to meet the service quality
requirement.
For Algorithm 2, the inner loop power control is performed every five timeslots, so
the frequency of inner loop power control is lower compared with Algorithm 1. So
Algorithm 2 is applicable to favorable radio communication environments (the MS is
or will be in static state, for instance) and scenarios where the channel fades lowly
or hardly fades.
Algorithm 1 either increases or decreases the transmit power when the TPC
command is received. Algorithm 2 increases, decreases or does not change the
transmit power after making a soft decision based on the TPC commands at five
different timeslots. Therefore, Algorithm 1 is more applicable to scenarios where the
channel fades fast, because the channel needs to increase or decrease the transmit
power quickly.
Note:
When uplink inner loop power control is performed, the transmit power calculated
by the UE can exceed the maximum transmit power of the uplink DPCH indicated
by USrvDivPc.maxUlDpchPwr. In this case, the UE can only transmit with the
configured maximum transmit power.
3.1.3.2 Uplink Inner Loop Power Control of the R99 in Compressed Mode
The principle of inner loop power control in compressed mode is the same as that in
normal mode. That means the serving cell (a cell in the active set) estimates the received
SIRest of uplink DPCH, and one TPC command is produced and sent in each timeslot
except the downlink transmission gap according to the following rules.
If SIRest > SIRcm_target, then the TPC command is set to 0; if SIRest < SIRcm_target, then the
TPC command is set to 1. SIRcm_target is the target SIR value during the period when the
compressed mode is used.
Where,
Npilot,curr_frame is the number of pilot bits per timeslot in the current uplink link
frame.
Npilot,N is the number of pilot bits per timeslot in normal mode without
transmission gap.
If the current uplink link frame contains the start of the first transmission gap of
the transmission gap pattern, then ΔSIR1_coding = DeltaSIR1. DeltaSIR1 is
obtained from UCompressMode.DeltaSIR1.
If the current uplink link frame contains the frame next to the start of the first
transmission gap of the transmission gap pattern, then ΔSIR1_coding =
DeltaSIRafter1. DeltaSIRafter1 is obtained from
UCompressMode.DeltaSIRafter1.
If the current uplink link frame contains the start of the second transmission
gap of the transmission gap pattern, then ΔSIR2_coding = DeltaSIR2.
DeltaSIR2 is obtained from UCompressMode.DeltaSIR2.
If the current uplink link frame contains the frame next to the start of the
second transmission gap of the transmission gap pattern, then ΔSIR2_coding
= DeltaSIRafter2. DeltaSIRafter2 is obtained from
UCompressMode.DeltaSIRafter2.
One TGPS (Transmission Gap Pattern Sequence) has only one measurement value, but
the UE can measure several values at the same time, so multiple compressed modes
can be activated at the same time in one radio frame. In this case, the SIR1_coding and
SIR2_coding corresponding to each compressed mode can be calculated, and then they
are summed up to obtain the available ΔSIR1_coding and ΔSIR2_coding.
N
SIR1 _ coding SIR1 _ coding, i
i 1
N
SIR2 _ coding SIR2 _ coding, i
i 1
Where, N is the number of types of compressed modes activated at the same time in one
radio frame.
Because no TPC command is sent in the timeslot of the transmission gap in the downlink
compressed frame, the UE sets TPC_cmd to 0 in the corresponding receiving timeslot.
Transmission gaps of compressed frames in compressed mode make the format of the
timeslot used in compressed mode different from that in normal mode, so the number of
pilots for each timeslot of the uplink DPCCH may differ between compressed mode and
non-compressed mode. To offset the changes in the total power of the pilot signals, the
transmit power of the uplink DPCCH should be changed. Therefore, at the start of each
timeslot, the UE calculates the power adjustment volume ΔPILOT.
If the number of pilots per timeslot of the uplink DPCCH is different from that sent in the
previous timeslot, then ΔPILOT (dB) is obtained by the following formula:
Where,
Unless otherwise specified, in compressed mode, the UE adjusts the transmit power of
the uplink DPCCH with a step of ΔDPCCH (in dB) in every slot, which is given by:
At the start of the first slot after an uplink or downlink transmission gap, the UE should
use a change in the transmit power of the uplink DPCCH by an amount ΔDPCCH (in dB),
with respect to the uplink DPCCH power in the most recently transmitted uplink slot.
The value of ΔRESUME (in dB) should be determined by the UE according to the Initial
Transmit Power mode (ITP) indicated by UCompressMode.Itp. The ITP is a UE specific
parameter, which is signaled by the network with other compressed mode parameters.
The different modes are summarized in the following table.
ITP Description
TPC_cmdgap should be the value of TPC_cmd derived in the first slot of the uplink
transmission gap, if a downlink TPC_command is transmitted in that slot. Otherwise
TPC_cmdgap should be zero if no downlink TPC_command is transmitted in that slot.
last should be equal to the most recently computed value of i. i should be updated
according to the following recursive relations, which should be executed in all slots in
which both the uplink DPCCH and a downlink TPC command are transmitted, and in the
first slot of an uplink transmission gap if a downlink TPC command is transmitted in that
slot:
Where,
ksc = 0 if additional scaling is used in the current slot and the previous slot.
Otherwise, ksc = 1.
i-1 is the value of i computed for the previous slot. When the uplink DPCCH is activated,
the value of i-1 should be initialized to zero at the end of the first slot after each uplink
transmission gap, and at the end of the first slot after each downlink transmission gap.
The value of i should be set to zero at the end of the first slot after each uplink
transmission gap.
After a transmission gap in either the uplink or the downlink, the period following
resumption of simultaneous uplink and downlink DPCCH transmission is called a
recovery period. RPL is the recovery period length and expressed as a number of slots.
RPL is equal to the minimum value out of the transmission gap length and 7 slots. If a
transmission gap or an Uplink DPCCH burst pattern gap is scheduled to start before RPL
slots have elapsed, then the recovery period should end at the start of the gap, and the
value of RPL should be reduced accordingly.
During the recovery period, there are two modes for the power control algorithm. The
Recovery Period Power (RPP) control mode indicated by UCompressMode.Rpp is
signaled with other compressed mode parameters. The different modes are summarized
in the following table.
Table 3-7 Recovery Period Power control modes during compressed mode
RPP Description
The power control algorithm 1 is used during RPL slots after each
1
transmission gap. The step size is ΔRP-TPC.
For RPP mode 0, the step size is not changed during the recovery period, and ordinary
transmit power control is used. The algorithm for processing TPC commands is
determined by the value of PCA.
For RPP mode 1, during RPL slots after each transmission gap, power control algorithm
1 is used with a step size ΔRP-TPC instead of ΔTPC, regardless of the value of PCA.
Therefore, the change in uplink DPCCH transmit power at the start of each of the RPL+1
slots immediately following the transmission gap (except for the first slot after the
transmission gap) is given by:
ΔRP-TPC is called the recovery power control step size and expressed in dB.
After the recovery period, ordinary transmit power control resumes. The power control
algorithm is determined by the value of PCA, and the step size is ΔTPC.
If PCA is 2, the sets of slots over which the TPC commands are processed should
remain aligned to the frame boundaries in the compressed frame. For both RPP mode 0
and RPP mode 1, if the transmission gap or the recovery period results in any incomplete
sets of TPC commands, TPC_cmd should be zero for those sets of slots which are
incomplete.
3.1.4.1 Downlink Inner Loop Power Control of the R99 in Normal Mode
In the case of downlink inner loop power control, the UTRAN adjusts the current downlink
power P(k-1) to the new transmit power level P(k) according to the following formula
th
when it estimates the k number of the TPC command.
Where,
th
PTPC(k) is the k number of power adjustment volume in the process of inner loop
power control.
PTPC(k) is determined with the following method. The UE sends a TPC command at each
timeslot. The UTRAN adjusts the transmit power at each timeslot according to the TPC
command.
If the limitation on power increase needs to be considered for downlink inner loop power
control, the value of PTPC(k) is determined by the following formula:
The inner loop power control in compressed mode works in the same way as that in
normal mode, except that both downlink DPDCH and DPCCH stop transmission during
the transmission gap of compressed frames.
The transmit power of the first timeslot after the transmission gap of DPCCH is the same
as that of the timeslot prior to the transmission gap.
When the compressed mode is used, the UTRAN adjusts the current downlink transmit
power P(k-1) [dB] of each timeslot except the downlink transmission gap to a new power
th
value P(k) [dB] based on the TPC command received at the k-1 timeslot and the
following formula.
Where,
th
PTPC(k) is the k power adjustment value according to inner loop power control.
th
PSIR(k) is the k power adjustment value because the downlink SIRTarget changes in
compressed mode as opposed to normal mode (this change is reflected in inner
loop instead of outer loop).
Pbal(k) [dB] is a correction value obtained according to the downlink power control
process. It is used to balance the power of the radio link so that the value can reach
a common reference power level.
The uplink TPC command may fail to be received due to transmission gaps in uplink
compressed frames. In this case, the Node B sets PTPC(k) to 0. Otherwise, PTPC(k) is
calculated in the same way as that in normal mode except that ΔTPC is replaced with
ΔSTEP in the formula.
During the recovery period (RPL number of timeslots) of the transmission gap, the
common power transmission control algorithm is used, but ΔSTEP = ΔRP-TPC. In a
non-recovery period, ΔSTEP = ΔTPC.
Where,
RPL is the length of the recovery period that is expressed in the number of timeslots.
RPL=minimum (out of the transmission gap length, 7). If the next transmission gap
starts again before the recovery period ends, then the recovery period ends at the
start of the next transmission gap. RPL depends on the length of the new
transmission gap. RPL = 7.
ΔRP-TPC is the step (dB) of power control during the recovery period. ΔRP-TPC
=minimum (3dB, 2ΔTPC).
Power offset PSIR(k) = δPcurr – δPprev, δPcurr and δPprev respectively indicate the δP value
of the current timeslot and the latest transmission timeslot. The formula for calculating δP
is as follows:
Where, n is the type of TTI length of all TrCHs multiplexed to a CCTrCH. ΔP1_coding
and ΔP2_coding are obtained from the following relations and the uplink parameters,
including DeltaSIR1, DeltaSIR2, DeltaSIRafter1 and DeltaSIRafter2, which are informed
by the upper level.
If the current frame contains the start of the first transmission gap, then ΔP1_coding
= DeltaSIR1. DeltaSIR1 is obtained from UCompressMode.DeltaSIR1.
If the current frame is next to the frame that contains the start of the first
transmission gap, then ΔP1_coding = DeltaSIRafter1. DeltaSIRafter1 is obtained
from UCompressMode.DeltaSIRafter1.
If the current frame contains the start of the second transmission gap, then
ΔP2_coding = DeltaSIR2. DeltaSIR2 is obtained from UCompressMode.DeltaSIR2.
If the current frame is next to the frame that contains the start of the second
transmission gap, then ΔP2_coding = DeltaSIRafter2. DeltaSIRafter2 is obtained
from UCompressMode.DeltaSIRafter2.
If the compressed mode with half spectrum spread factor is used, ΔPi_compression
= 3 dB.
When several compressed modes are used at the same time, the δP of each
compressed mode is calculated separately. The δP used for the current frame is the
summation of all δP values.
No transmit power of any timeslot in compressed mode can be higher than the maximum
transmit power or lower than the minimum transmit power.
ΔPi_compression is used to offset the influence of the high SIR needed for increasing
transmission bits in compressed mode.
Outer loop power control includes uplink OLPC and downlink OLPC. The downlink OLPC
is performed by UEs and unrelated to the RNC. This section describes the uplink OLPC
algorithm on the UTRAN side only. The initial SIRTarget value (USrvDivPc.uLInitSIR) is
determined at the service access stage, and the quality information (such as CRCI, BER
and BLER) is obtained from the measurement report, the SIR Target adjustment decision
command is produced based on the service quality. If adjustment is necessary, SIR Target
is adjusted slowly and the signaling OUTER LOOP PC is used to notify the Node B. The
Node B compares the SIR in the dedicated measurement report with the latest SIRTarget
and makes the single link SIR reach SIRTarget through inner loop power control. In this
way, the service quality will not fluctuate drastically due to changes in the radio
environment.
There are two uplink OLPC algorithms: BLER Target Algorithm and Threshold Algorithm.
The algorithm to be activated is controlled by the URncInfo.olPcAlg parameter.
When URncInfo.olPcAlg is set to BLER Target Algorithm, the BLER Target Algorithm is
used. For details, refer to the ZTE UMTS Power Control Algorithm Enhancement Feature
Guide.
The CRC based OLPC adjusts the SIRTarget based on the total TB number and CRC error
TB number. When the CRC based OLPC is used, some improvement algorithms are
used to improve the SIRTarget adjustment result. The DPCCH BER based OLPC is used,
mainly because the CRC based OLPC adjusts the SIRTarget too slowly, and it is necessary
to speed up the SIRTarget convergence. The DPCCH BER based OLPC is also called QE
based OLPC.
The principle of the CRC-based outer loop power control algorithm is as follows:
The number of error blocks is counted according to the CRC result of the transport
channel. In addition, the total number of transmitted data blocks is also counted (called
error block tolerance counter). Then SIRtarget is updated based on the number of error
blocks and the total number of transmitted data blocks.
When the tolerance BLER period (USrvPc.blerAccpPeriod) (the unit is number of data
blocks instead of a time measurement unit) does not expire, but the number of error
blocks exceeds the error transport block number threshold (USrvPc.errorThresh),
SIRTarget needs to be increased (meanwhile, the error block counter and error block
tolerance counter are cleared to 0).
As the loop delay is at least 4–5 frames, the effect of any increase will be shown after
4–5 frames. Therefore, if a CRC indication error occurs again in 4–5 frames after the
increase, no error block is counted (a shield period (UCelInfoFDD.coverPrd) is used here
to shield out the adjustment function). If the CRCI indication error occurs again after the
shield period expires, the error blocks are counted again.
The step size for increasing SIRTarget is determined by the following formula:
Where,
deltaStep1 is an additional increase step size when the SIRTarget increase is caused
by consecutive error TBs. If there are at least two consecutive error TBs which
cause the SIRTarget increase, the deltaStep1 is obtained from
URncFunction.sirUpAddStep. Otherwise, the deltaStep1 is 0.
deltaStep2 is another additional increase step size when the SIRTarget will be
increased continuously. If the last SIRTarget adjustment command is "increase" and
the SIRTarget is increased again during the period (indicated by
URncFunction.validTimTbCovPrd) after the shield period, then the deltaStep2 for
the following SIRTarget increase should be calculated with the following formula:
Where,
ErrTbNumInCovPrd is the number of error TBs in the shield period after the
last SIRTarget increase.
When the error block tolerance counter is not less than the tolerance BLER period
(USrvPc.blerAccpPeriod), the RNC will: (1) decrease SIRTarget if the received number of
error blocks is less than the error transport block number threshold (USrvPc.errorThresh),
(2) keep the SIRTarget unchanged if the received number of error blocks equals to the error
For the decreasing of SIRTarget, ZTE uses the SIR target adaptive down step size function
to speed up the SIRTarget decreasing.
When the switch of SIR target adaptive down step size is off (USrvPc.swchAdaptiveStep
= 0), the step for decreasing SIRTarget is USrvPc.ulSirTargDnStep.
When the switch of SIR target adaptive down step size is on (USrvPc.swchAdaptiveStep
= 1), the step for decreasing SIRTarget is determined as follows:
When the last SIR target adjustment command is "decrease", the following SIR
target adjustment command also is down, and there is no error TB, the current step
for decreasing SIRTarget will be the result that the last step for decreasing SIRTarget
plus 0.1dB. If the last step for decreasing SIR Target is the biggest value
(USrvPc.maxSirTargDnStep), the current step for decreasing SIRTarget is reset to the
initial value (USrvPc.ulSirTargDnStep).
When the last SIR target adjustment command is "increase" or "keep", or the last
and current SIR target adjustment command are both "decrease", but there are
error TBs during the current SIR target adjustment period, then the current step for
decreasing SIRTarget is reset to the initial value (USrvPc.ulSirTargDnStep).
To prevent the SIRTarget from being increased or decreased too much, MaxSIRtarget and
MinSIRtarget are used. MaxSIRtarget is obtained from the USrvDivPc.uLMaxSIR
parameter, and MinSIRtarget is obtained from the USrvDivPc.uLMinSIR parameter.
In the CRC-based OLPC, SIRTarget can be decreased only when the TB number is no less
than the tolerance BLER period, so the SIRTarget is decreased slowly, which affects the
system capacity. To increase the system capacity, the DPCCH BER-based OLPC
(namely, Quality Estimate (QE) based OLPC) is used. Here, DPCCH BER is the QE in
UL DATA FRAME FOR DCH.
When the QE based OLPC switch (USrvPc.ulOlPcQESwchSil) is on, the OLPC of the
ZTE RNC can be based on the physical channel BER (QE), but it only can decrease the
SIRTarget. Here, the silent mode for the transmission of the uplink data frame that contains
the BER measurement result is used. In silent mode, the uplink data frame can be sent to
the RNC only when the number of DCH TB is not zero.
The principle of QE based OLPC is as follows:
In the valid time window (8 seconds), if the condition that the physical channel BER is
smaller than or equal to physical channel BERtarget (SrvPc.qePhyBerTarSil) is fulfilled for
N (USrvPc.qeCntThres) times continuously, then the SIRTarget should be decreased.
For the SIRTarget decreasing step, refer to “CRC based OLPC”. After SIRTarget is
decreased, it is also necessary to clear all the OLPC counters to 0.
The common outer loop power control algorithm described above is designed for one
transport channel. For multi-service (that is, several transport channels that are
multiplexed to one CCtrCH), special treatment is needed for the outer loop power control
algorithm.
Firstly, QE-based OLPC can be activated only when all the QE based OLPC switches
(USrvPc.ulOlPcQESwchSil) of all services are on. The BER target value should be the
minimum value of USrvPc.qePhyBerTarSil of all the services.
The downlink outer loop power control is performed by UEs. The RNC provides the
corresponding BLER target values (USrvPc.blerTarget) to UEs.
In the case of soft handover or macro diversity, a UE can communicate with all cells in
the active set. With downlink inner loop power control, the UE sends the same TPC
commands to the cells in the active set. The links have different transmission paths, so
error codes will be produced in the TPC commands, and some cells receive wrong TPC
commands. As a result, some cells increase their downlink transmission power and
some cells decrease their downlink transmission power. Therefore, power drifting occurs.
The downlink power balancing feature is used to eliminate power drifting.
The downlink power balancing is to balance the downlink transmit power of one or more
radio links used by the Node Bs related to a UE. In the case where a single link is
involved, the downlink average power will be insensitive to the central value of a power
control range if the downlink power control balancing is used. In the case where several
links are involved, power balancing can help overcome power drifting.
Where,
PP-CPICH is the transmit power of the primary CPICH, obtained from the
UUtranCellFDD.primaryCpichPower parameter.
Pinit is the code power of the last timeslot in the previous adjustment period. If the
last timeslot in the previous adjustment period is included in the transmission gap
(in compressed mode), then Pinit equals to the code power of the timeslot prior to the
transmit gap.
The downlink transmit power of each radio link, needed for calculating DL Reference
Power, can be obtained indirectly from the Transmitted code power (TCP: transmit power
of PILOT field of DPCH) periodically reported by the Node B by the following formula:
j
PDPDCH (dBm) j TCP j PO3 (3.2-2)
Where,
j th
PDPDCH is the downlink transmit power of the j radio link, unit: dBm;
j
PO3 is the power offset between the DL DPCH PILOT field and the DPCH data
th
field (USrvDivPc.dpchPO3) of the j radio link;
j th
TCP is transmitted code power periodically reported by the Node B of the j radio
link.
th
The downlink reference power of the j radio link is:
j
DL _ Re fer _ Power (dB) j PDPDCH j P _ CPICH _ Power (3.2-3)
j th
Where, P_CPICH_POWER is P-CPICH power of the j radio link.
Next, RNC takes the average value of the reference power for each radio link as the
required DL Reference Power.
j 1
j
DL _ Re fer _ Power
DL _ Re fer _ Power
N (3.2-4)
The method for power balancing between the RNC and Node B is as follows:
The dedicated TCP values of all links are obtained from the dedicated
measurement report. The DL Reference Power is obtained by computing the
reported values.
When the absolute value of the difference between the DL Reference Power
obtained in the new adjustment period and that obtained in the previous period
exceeds the downlink reference power adjustment threshold (2dB), the signaling of
the DL Power Control Request message that contains the information of DL
Reference Power is sent to the Node B.
The Node B uses this value to implement link balancing through the inner loop
power control algorithm.
Other parameters in the Iub interface related to power balancing are as follows:
1. Adjustment Type:
2. Adjustment Period:
This parameter indicates the adjustment period for power balancing, and its value is
50 frames.
Max adjustment step defines a time period in slots. It is set to 8 slots, during which
the accumulative adjustment for power balancing does not exceed 1dB.
Note:
When the ZTE RNC serves as a DRNC, whether to use DL POWER CONTROL
REQUEST message from the Iur interface to control power balancing is determined by
URncFunction.iurPwrCtlReqSwch.
The strategy for starting and terminating the Node B TCP dedicated measurement is as
follows:
The measurement of TCP is started after the UE changes from non-macro diversity
to macro diversity status.
The measurement of TCP is terminated after the UE changes from macro diversity
to non-macro diversity status.
The Node B TCP dedicated measurement for power balancing is reported periodically.
The Node B dedicated measurement parameters are obtained in the following way. A
unique record is obtained by matching 0: Period Report Parameters for TCP in Power
balancing with UNbDedMeas.nbDMCfgNote in the management object UNbDedMeas,
and then the following Node B dedicated measurement parameters are obtained.
4 Parameters
Note: In this section, the default value and recommended value of the service related
parameters are the values for typical services only. For the values for the other service,
refer to the ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Radio Parameter
Reference, ZXWR RNC (V3.14.10.14) Radio Network Controller Radio Parameter
Reference.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Power calculating the initial transmit dB, step
Constant power of the PRACH 1dB
Value preamble. For details, refer
to 3GPP 25.331.
Maximum
UUtranCellF This parameter indicates the
Allowed UL (-50..33)d
DD.maxRac maximum UL transmit power dBm 24 24
TX Power of Bm, step
hTxPwr used by the RACH.
RACH 1dBm
UL UL
This parameter indicates the
13.6kb 13.6kb
quality factor of the uplink
ps ps
USrvDivPc. DPCCH DPCCH pilot field, which is
(-30..+30) Signali Signali
dpcchPilotE Pilot Field used for calculating the dB
dB, step ng: ng:
bN0 Eb/N0 uplink DPCCH power offset
0.1dB 3,3,3,3, 3,3,3,3,
upon new call access.
3,3,3,3, 3,3,3,3,
[Note1]
3 3
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
0:Normal
UUtranCellF This parameter indicates 0:Norm 0:Norm
Cell Load Load Cell
DD.loadSce whether the cell is highly N/A al Load al Load
Scene 1:High
ne loaded. Cell Cell
Load Cell
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
control parameters. Each
cell obtains service-related
power control parameters
according to this parameter.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Note1: The parameter is a 9-tuple. The elements are used in different load conditions
and for different user priorities. For details, refer to the ZTE UMTS Load Adaptive Power
Control Feature Guide. The relationships between the elements and load levels/user
priorities are as follows:
Element 1: low load, golden-level user.
Element 2: low load, silver-level user
Element 3: low load, bronze-level user
Element 4: medium load, golden-level user
Element 5: medium load, silver-level user
Element 6: medium load, bronze-level user
Element 7: high load, golden-level user
Element 8: high load, silver-level user
Element 9: high load, bronze-level user.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
DD.aichPow AICH transmit power. It is an (-22..5)d
er offset relative to the primary B, step
CPICH power. 1dB
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Offset the data field on the 0.25dB
SCCPCH (relative value).
Power
Offset for
Downlink This parameter indicates the
UCelInfoFD DPCH Initial power offset for calculating (-50, …5
D.pORabHa Power the downlink DPCH initial 0)dB, dB 1 1
rdHO Calculation power during the RAB hard step
when RAB handover. 0.1dB
Hard
Handover
Power
Offset for
Downlink This parameter indicates the
UCelInfoFD DPCH Initial power offset for calculating
(-50..50)d
D.pOReEsta Power the downlink DPCH initial dB 2 2
B, step
blish Calculation power during the RAB
0.1dB
when RAB reestablishment.
Re-Establish
ment
UCelInfoFD Power This parameter indicates the
dB 0 0
D.pOSetup Offset for power offset for calculating (-50..50)d
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Downlink the downlink DPCH initial B, step
DPCH Initial power during the RAB/SRB 0.1dB
Power establishment.
Calculation
when Call
Setup
Power
Offset for
Downlink This parameter indicates the
DPCH Initial power offset for calculating
UCelInfoFD (-50..50)d
Power the downlink DPCH initial dB 0 0
D.pOSoftHO B, step
Calculation power during the soft or
0.1dB
when Soft or softer handover.
Softer
Handover
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
set it to DPCH Maximum DL
Power.
[Note1]
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
PO2Sw Switch adjust the PO2.PO2 is the Need Need Need
power offset of the DPCH Dynamic Dynami Dynami
TPC field relative to the data Update) c c
field. 1: On Update Update
(Need ) )
Dynamic
Update)
Note1: The parameter is a 9-tuple. The elements are used in different load conditions
and for different user priorities. For details, refer to the ZTE UMTS Load Adaptive Power
Control Feature Guide. The relationships between the elements and load levels/user
priorities are as follows:
Element 1: low load, golden-level user.
Element 2: low load, silver-level user
Element 3: low load, bronze-level user
Element 4: medium load, golden-level user
Element 5: medium load, silver-level user
Element 6: medium load, bronze-level user
Element 7: high load, golden-level user
Element 8: high load, silver-level user
Element 9: high load, bronze-level user.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
when algorithm 1 is selected
for uplink inner loop power
control. Because the default
step in algorithm 2 is 1, this
parameter is not needed.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Algorithm used. In the case of 2: m1 m1
algorithm 1, inner loop Algorithm
power control is performed 2
every time slot. In the case
of algorithm 2, inner loop
power control is performed
every 5 time slots.
UL UL
This parameter indicates the signalin signalin
maximum DPCH uplink g: g:
transmit power allowed for a 24,24,2 24,24,2
Maximum UE. When uplink inner loop 4,24,24 4,24,24
Allowed power control is performed, ,24,24, ,24,24,
USrvDivPc
Uplink the transmit power newly (-50..33)d 24,24; 24,24;
.maxUlDpc dBm
DPCH calculated by a UE may be Bm, step UL UL
hPwr
Transmissio larger than this parameter. 1dBm service service
n Power In this case, the UE can only s: s:
use this parameter for 33,33,3 33,33,3
transmitting signals. 3,33,33 3,33,33
[Note1] ,33,33, ,33,33,
33,33 33,33
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
recover as rapidly as
possible a
signal-to-interference ratio
(SIR) close to the target SIR
after each transmission gap.
The serving cells (cells in the
active set) should estimate
signal-to-interference ratio
SIRest of the received uplink
DPCH. The serving cells
should then generate TPC
commands and transmit the
commands once per slot,
except during downlink
transmission gaps,
according to the following
rule: if SIRest > SIRcm_target
then the TPC command to
transmit is "0", while if SIRest
< SIRcm_target then the TPC
command to transmit is "1".
SIRcm_target is the target SIR
during compressed mode
and fulfils
SIRcm_target = SIRtarget +
△SIRPILOT +
△SIR1_coding +
△SIR2_coding,
where △SIR1_coding and
△SIR2_coding are
computed from uplink
parameters DeltaSIR1,
DeltaSIR2, DeltaSIRafter1,
DeltaSIRafter2 signaled by
higher layers as:
△SIR1_coding = DeltaSIR1
if the start of the first
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
transmission gap in the
transmission gap pattern is
within the current uplink
frame.
△SIR1_coding =
DeltaSIRafter1 if the current
uplink frame just follows a
frame containing the start of
the first transmission gap in
the transmission gap
pattern.
△SIR2_coding = DeltaSIR2
if the start of the second
transmission gap in the
transmission gap pattern is
within the current uplink
frame.
△SIR2_coding =
DeltaSIRafter2 if the current
uplink frame just follows a
frame containing the start of
the second transmission gap
in the transmission gap
pattern.
△SIR1_coding = 0 dB and
△SIR2_coding = 0 dB in all
other cases.
DSIRPILOT is defined as:
△SIRPILOT = 10Log10
(Npilot, N/Npilot,
curr_frame), where Npilot,
curr_frame is the number of
pilot bits per slot in the
current uplink frame, and
Npilot, N is the number of
pilot bits per slot in a normal
uplink frame without a
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
transmission gap.
In the case of several
compressed mode pattern
sequences being used
simultaneously,
DSIR1_coding and
DSIR2_coding offsets are
computed for each
compressed mode pattern
and all DSIR1_coding and
DSIR2_coding offsets are
summed together.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
the start of the second
transmission gap in the
transmission gap pattern.
When not configured, UE
regards DeltaSIRafter2 =
DeltaSIRafter1.
Please refer to DeltaSIR1.
In downlink compressed
mode, no TPC commands
are transmitted during the
transmission gap in the
compressed frame. This
means that the transmit
powers of the uplink DPDCH
(s) and DPCCH are not
changed during the
transmission gaps.
0: Initial
After a transmission gap, the
Transmit
closed loop power control 0: Initial 0: Initial
Power
Initial has to converge on the SIR Transm Transm
UCompres Mode 0
Transmit target as quickly as possible. N/A it it
sMode.Itp 1: Initial
Power Mode Power Power
Transmit
At the start of the first slot Mode 0 Mode 0
Power
after an uplink or downlink
Mode 1
transmission gap the UE
should apply a change in the
transmit power of the uplink
DPCCH by an amount
△DPCCH (in dB), with
respect to the uplink DPCCH
power in the most recently
transmitted uplink slot,
where:
△DPCCH = △RESUME +
△PILOT
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
The value of △RESUME (in
dB) should be determined by
the UE according to the
Initial Transmit Power mode
(ITP). The ITP is a UE
specific parameter, which is
signaled by the network with
the other compressed mode
parameters.
Note1: The parameter is a 9-tuple. The elements are used in different load conditions
and for different user priorities. For details, refer to the ZTE UMTS Load Adaptive Power
Control Feature Guide. The relationships between the elements and load levels/user
priorities are as follows:
Element 1: low load, golden-level user.
Element 2: low load, silver-level user
Element 3: low load, bronze-level user
Element 4: medium load, golden-level user
Element 5: medium load, silver-level user
Element 6: medium load, bronze-level user
Element 7: high load, golden-level user
Element 8: high load, silver-level user
Element 9: high load, bronze-level user.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
cannot be shown before a
period of time. When the
shielded period is set, it
indicates that during this
shielded period, the received
error transport blocks will not
be handled.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
quality of uplink data frames.
If mixed services are used,
the minimum value in
qePhyBerTarSil of each
service is combined, and
signaling is excluded.
[Note1]
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
steps are set asymmetrically
and separately.
[Note1]
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Target of the R99 service, which is 3)dB, .75~12. .75~12.
used to restrict the range of step 2kbps: 2kbps:
the SIR target in outer loop 0.1dB 0,0,0,0, 0,0,0,0,
power control. 0,0,0,0, 0,0,0,0,
[Note1] 0 0
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
addition step size is added
to the SIR target increase
step size. This additional
step size is calculated
according to the error TB
number in and beyond the
shielding period.
UL UL
NAMR4 NAMR4
Uplink SIR This parameter indicates the .75~12. .75~12.
USrvPc.m Target maximum step size of 2kbps: 2kbps:
(0.1..1)dB
axSirTarg Maximum increasing the uplink SIR dB 0.6,0.6, 0.6,0.6,
, step
UpStep Up Step target. 0.6,0.6, 0.6,0.6,
0.1dB
Size [Note1] 0.6,0.6, 0.6,0.6,
0.6,0.6, 0.6,0.6,
0.6 0.6
Note1: The parameter is a 9-tuple. The elements are used in different load conditions
and for different user priorities. For details, refer to the ZTE UMTS Load Adaptive Power
Control Feature Guide. The relationships between the elements and load levels/user
priorities are as follows:
Element 1: low load, golden-level user.
Element 2: low load, silver-level user
Element 3: low load, bronze-level user
Element 4: medium load, golden-level user
Element 5: medium load, silver-level user
Element 6: medium load, bronze-level user
Element 7: high load, golden-level user
Element 8: high load, silver-level user
Element 9: high load, bronze-level user.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
DL DL
NAMR4 NAMR4
This parameter indicates the .75~12. .75~12.
Block Error Ratio (BLER) 2kbps: 2kbps:
target of a transport channel, 1.0000 1.0000
and is the benchmark for 000000 000000
outer loop power control. In 00000e 00000e
the case of a service with -002,1. -002,1.
multiple sub-flows, this 000000 000000
parameter is applicable to 000000 000000
the first sub-flow. 000e-0 000e-0
The signaling value is Log10 02,1.00 02,1.00
(transport channel BLER 000000 000000
quality target). That is, the 000000 000000
physical value P in TS 0e-002, 0e-002,
25.331 is Log10 (actual 1.0000 1.0000
USrvPc.ble BLER
rTarget Target value); the scalar value D in Note2 N/A 000000 000000
TS 25.331 is P*10; the value 00000e 00000e
configured in the database is -002,1. -002,1.
D+63; the actual value 000000 000000
configured on the OMCR is 000000 000000
10^P, and is listed in 000e-0 000e-0
exponential form, refer to the 02,1.00 02,1.00
table in value range. 000000 000000
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
02,1.25 02,1.25
892541 892541
179416 179416
8e-002 8e-002
Note1: The parameter is a 9-tuple. The elements are used in different load conditions
and for different user priorities. For details, refer to the ZTE UMTS Load Adaptive Power
Control Feature Guide. The relationships between the elements and load levels/user
priorities are as follows:
Element 1: low load, golden-level user.
Element 2: low load, silver-level user
Element 3: low load, bronze-level user
Element 4: medium load, golden-level user
Element 5: medium load, silver-level user
Element 6: medium load, bronze-level user
Element 7: high load, golden-level user
Element 8: high load, silver-level user
Element 9: high load, bronze-level user.
Note2: The mapping relations between the quantized values and the physical values of
USrvPc.blerTarget are as follows:
Physical Value Quantized Value
0 0
6.309573444801915e-007 1
7.943282347242824e-007 2
1.000000000000000e-006 3
1.258925411794166e-006 4
1.584893192461114e-006 5
1.995262314968879e-006 6
2.511886431509582e-006 7
3.162277660168379e-006 8
3.981071705534968e-006 9
5.011872336272724e-006 10
6.309573444801928e-006 11
7.943282347242820e-006 12
1.000000000000000e-005 13
1.258925411794166e-005 14
1.584893192461114e-005 15
1.995262314968880e-005 16
2.511886431509581e-005 17
3.162277660168382e-005 18
3.981071705534966e-005 19
5.011872336272722e-005 20
6.309573444801933e-005 21
7.943282347242817e-005 22
1.000000000000000e-004 23
1.258925411794168e-004 24
1.584893192461115e-004 25
1.995262314968877e-004 26
2.511886431509580e-004 27
3.162277660168380e-004 28
3.981071705534974e-004 29
5.011872336272726e-004 30
6.309573444801930e-004 31
7.943282347242803e-004 32
1.000000000000000e-003 33
1.258925411794168e-003 34
1.584893192461114e-003 35
1.995262314968878e-003 36
2.511886431509579e-003 37
3.162277660168379e-003 38
3.981071705534972e-003 39
5.011872336272724e-003 40
6.309573444801928e-003 41
7.943282347242816e-003 42
1.000000000000000e-002 43
1.258925411794168e-002 44
1.584893192461114e-002 45
1.995262314968880e-002 46
2.511886431509580e-002 47
3.162277660168379e-002 48
3.981071705534974e-002 49
5.011872336272722e-002 50
6.309573444801933e-002 51
7.943282347242812e-002 52
1.000000000000000e-001 53
1.258925411794167e-001 54
1.584893192461114e-001 55
1.995262314968880e-001 56
2.511886431509580e-001 57
3.162277660168380e-001 58
3.981071705534972e-001 59
5.011872336272722e-001 60
6.309573444801932e-001 61
7.943282347242815e-001 62
1.000000000000000e+000 63
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
CtlReqSwc Power the downlink power
h Control balancing function through
Request the Power Control Request
Information message on the Iur
in Iur interface. When this function
Interface is enabled, the DRNC can
send the DL POWER
CONTROL REQUEST
message received from the
Iur interface to the Node B.
When this function is
disabled, the DRNC will
discard the DL POWER
CONTROL REQUEST
message received from the
Iur interface.
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
NbDed
UNbDedMe This parameter indicates the
Measure
as.nbDMCfg Node B Dedicated Measure 0..65535 N/A N/A N/A
Configuratio
No Configuration No.
n No
0: Period 0: 0:
This parameter indicates the Report Period Period
Function of
UNbDedMe function, purpose etc. of the Paramete Report Report
Configuratio
as.nbDMCfg dedicated measurement rs for N/A Parame Parame
n
Note parameters indicated by the TCP in ters for ters for
Parameters
configuration index. Power TCP in TCP in
balancing Power Power
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
1: Period balanci balanci
Report ng ng
Paramete 1: 1:
rs for Period Period
TCP in Report Report
AMR or Parame Parame
DASF-PS ters for ters for
or TCP in TCP in
Handover AMR or AMR or
Control DASF- DASF-
2: Event PS or PS or
A Report Handov Handov
Paramete er er
rs for Control Control
TCP in 2: 2:
DASF-PS Event A Event A
3: Event Report Report
B Report Parame Parame
Paramete ters for ters for
rs for TCP in TCP in
TCP in DASF- DASF-
DASF-PS PS PS
4: Period 3: 3:
Report Event B Event B
Paramete Report Report
rs for Parame Parame
RTT in ters for ters for
LCS TCP in TCP in
5: Event DASF- DASF-
E Report PS PS
Paramete 4: 4:
rs for SIR Period Period
Error in Report Report
Outer Parame Parame
Loop ters for ters for
Power RTT in RTT in
Control LCS LCS
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
6: Event 5: 5:
F Report Event E Event E
Paramete Report Report
rs for SIR Parame Parame
Error in ters for ters for
Outer SIR SIR
Loop Error in Error in
Power Outer Outer
Control Loop Loop
7: Event Power Power
A Report Control Control
Paramete 6: 6:
rs for Event F Event F
TCP in Report Report
AMR Parame Parame
8: Event ters for ters for
B Report SIR SIR
Paramete Error in Error in
rs for Outer Outer
TCP in Loop Loop
AMR Power Power
9: Event Control Control
A Report 7: 7:
Paramete Event A Event A
rs for Report Report
TCP in Parame Parame
Handover ters 2 ters 2
Control for TCP for TCP
10: Event in AMR in AMR
B Report 8: 8:
Paramete Event B Event B
rs for Report Report
TCP in Parame Parame
Handover ters 2 ters 2
Control for TCP for TCP
in AMR in AMR
9: 9:
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Event A Event A
Report Report
Parame Parame
ters for ters for
TCP in TCP in
Handov Handov
er er
Control Control
10: 10:
Event B Event B
Report Report
Parame Parame
ters for ters for
TCP in TCP in
Handov Handov
er er
Control Control
Period Period
Report Report
1: SIR Parame Parame
Error ters for ters for
This parameter indicates the 2: TCP in TCP in
UNbDedMe Dedicated
type of dedicated Transmitt Power Power
as.dedMeas Measureme N/A
measurement to be ed Code balanci balanci
Type nt Type
executed by Node B Power ng: ng:
5: Round Transm Transm
Trip Time itted itted
Code Code
Power Power
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
following formula.
F(n) = (1-a)* F(n-1) +
a*M(n)
The variables in the formula
are defined as follows:
F(n) is the updated filtered
measurement result
F(n-1) is the old filtered
measurement result
M(n) is the latest received
measurement result from
physical layer
measurements
a = (1/2)^ (k/2) , where k is
the Measurement Filter
Coefficient. If k is 0 there’s
no filtering)
During the initialization, F(0)
is set to M(1) when the first
measurement result from the
physical layer measurement
is received.
1: On
Demand
2:
Period Period
Periodic
Report Report
3: Event
This parameter indicates the Parame Parame
A
report characteristics of ters for ters for
Report 4: Event
UNbDedMe measurement results, which TCP in TCP in
Characteristi B N/A
as.rptType can be on demand, periodic Power Power
cs 5: Event
or by triggering all kinds of balanci balanci
C
events. ng: ng:
6: Event
Periodi Periodi
D
c c
7: Event
E
8: Event
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
F
rptPrdUnit
=1:
(10..6000
0)ms,
This parameter indicates the
step
UNbDedMe Report frequency of measurement
10ms ms 4000 4000
as.rptPrd Period report transmitted by Node
rptPrdUnit
B.
=2:
(1..60)mi
n step
min
Counter ID Name
6 Engineering Guide
1. Power control is a basic feature. It should be used in all scenarios to ensure the
service quality and system capacity.
Whether the QE based OLPC in the uplink outer loop power control is activated or
not is based on the cell load. When the system capacity is limited due to high uplink
load, this function can be activated to improve the system capacity.
2. Power balancing is also a basic feature. It also should be used in all scenarios to
avoid power drifting when a soft handover occurs.
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Channel Configuration > AICH
Configuration > PRACH Configuration, and set PRACH Preamble Power Ramp Step,
and PRACH Initiation Tx Power Constant Value, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function >
Power Control Profile Related to Service, and set Service Related Power Control
Profile ID, and Initial Load Scene, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function >
Power Control Profile Related to Service > Power Control Related to Service, and
set Sub-service Type, Uplink Inner Loop Power Control Algorithm, Step Size of
Downlink Inner Loop Power Control, Step Size of Uplink Inner Loop Power Control,
Uplink SIR Target Down Step Size, Uplink SIR Target Up Step Size, Uplink SIR
Target Maximum Down Step Size, Uplink SIR Target Maximum Up Step Size, BLER
Target, Error Transport Block Number Threshold, Tolerance BLER Period,
Physical Channel BER Target For Silent Mode, The Number Threshold of Physical
Channel BER Less Than or Equal BER Target, Uplink Outer Loop PC SIR Target
Adaptive Down Step Size Switch, and Uplink Outer Loop PC QE Switch For Silent
Mode, see the following figure. Figure 6-16
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function >
Power Control Profile Related to Service > Power Control Related to Service >
Power Control Related to Service and Diversity Mode, and set Transmit Diversity
Mode, DPCH Maximum DL Power, DPCH Minimum DL Power, DPCH PO1, DPCH
PO2, DPCH PO3, DPCCH Pilot Field Eb/N0, Maximum Allowed Uplink DPCH
Transmission Power, Uplink Initial SIR Target, and Maximum Uplink SIR Target,
Minimum Uplink SIR Target, see the following figure.Figure 6-17
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell, and
set Uplink Rx Gain Provided by Tower Mounted Amplifier, DPCH PC Preamble
Length, SRB Delay, Shield Period for Increasing SIR Target in Threshold Algorithm,
Power Offset for Downlink DPCH Initial Power Calculation when RAB Hard
Handover, Power Offset for Downlink DPCH Initial Power Calculation when RAB
Re-Establishment, Power Offset for Downlink DPCH Initial Power Calculation when
Call Setup, Power Offset for Downlink DPCH Initial Power Calculation when Soft or
Softer Handover, and Power Offset for Downlink DPCH Initial Power Calculation
when SRB Hard Handover, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell, and
set PICH Power, P-CPICH Power, BCH Power, PCH Power, Primary SCH Power,
Secondary SCH Power, AICH Power, Cell Load Scene, Used Power Control Profile
Related to Service, SIB7 Originator, DL TPC Pattern 01 Count, and Maximum
Allowed UL TX Power of RACH, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration, and set Dynamic Update PO2 Switch, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration, and set The Offset of CPICH Ec/No in Iur Interface
Relative to the UE Measurement Result, Additional Size for Uplink SIR Target
Increasing When Consecutive Error TB Occurs, Valid Time Window for the TB in
Shield Period, and Switch of Using DL Power Control Request Information in Iur
Interface, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Extended Info of RNC, and set Normal OLPC
Algorithm Method, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > SCCPCH Configuration, and set
Maximum FACH Power, S-CCPCH TFCI Field Power Offset, and S-CCPCH Pilot
Field Power Offset, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Basic Compress Mode
Configuration, and set Recovery Period Power Control Mode, Initial Transmit
Power Mode, DeltaSIR1, DeltaSIR2, DeltaSIRafter1, and DeltaSIRafter2, see the
following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > Iub Link, and set
Adjustment Type for DL Power balancing, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > NodeB Dedicated Measurement Profile > NodeB Dedicated
Measurement Configuration, and set Function of Configuration Parameters,
Dedicated Measurement Type, Measurement Filter Coefficient, Report
Characteristics, and Choice Report Periodicity Scale, and Report Period, see the
following figure.
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Channel Configuration > AICH
Configuration > PRACH Configuration, and set PRACH Preamble Power Ramp Step,
and PRACH Initiation Tx Power Constant Value, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function >
Power Control Profile Related to Service, and set Service Related Power Control
Profile ID, and Initial Load Scene see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function >
Power Control Profile Related to Service > Power Control Related to Service, and
set Sub-service Type, Uplink Inner Loop Power Control Algorithm, Step Size of
Downlink Inner Loop Power Control, Step Size of Uplink Inner Loop Power Control,
Uplink SIR Target Down Step Size, Uplink SIR Target Up Step Size, Uplink SIR
Target Maximum Down Step Size, Uplink SIR Target Maximum Up Step Size, BLER
Target, Error Transport Block Number Threshold, Tolerance BLER Period,
Physical Channel BER Target For Silent Mode, The Number Threshold of Physical
Channel BER Less Than or Equal BER Target, Uplink Outer Loop PC SIR Target
Adaptive Down Step Size Switch, and Uplink Outer Loop PC QE Switch For Silent
Mode, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Service Function >
Power Control Profile Related to Service > Power Control Related to Service >
Power Control Related to Service and Diversity Mode, and set Transmit Diversity
Mode, DPCH Maximum DL Power, DPCH Minimum DL Power, DPCH PO1, DPCH
PO2, DPCH PO3, DPCCH Pilot Field Eb/N0, Maximum Allowed Uplink DPCH
Transmission Power, Uplink Initial SIR Target, Maximum Uplink SIR Target, and
Minimum Uplink SIR Target, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell, and
set Uplink Rx Gain Provided by Tower Mounted Amplifier, DPCH PC Preamble
Length, SRB Delay, Shield Period for Increasing SIR Target in Threshold Algorithm,
Power Offset for Downlink DPCH Initial Power Calculation when RAB Hard
Handover, Power Offset for Downlink DPCH Initial Power Calculation when RAB
Re-Establishment, Power Offset for Downlink DPCH Initial Power Calculation when
Call Setup, Power Offset for Downlink DPCH Initial Power Calculation when Soft or
Softer Handover, and Power Offset for Downlink DPCH Initial Power Calculation
when SRB Hard Handover, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell, and
set PICH Power, P-CPICH Power, BCH Power, PCH Power, Primary SCH Power,
Secondary SCH Power, AICH Power, Cell Load Scene, Used Power Control Profile
Related to Service, SIB7 Originator, DL TPC Pattern 01 Count, and Maximum
Allowed UL TX Power of RACH, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration, and set Dynamic Update PO2 Switch, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration, and set The Offset of CPICH Ec/No in Iur Interface
Relative to the UE Measurement Result, Additional Size for Uplink SIR Target
Increasing When Consecutive Error TB Occurs, Valid Time Window for the TB in
Shield Period, and Switch of Using DL Power Control Request Information in Iur
Interface, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Extended Info of RNC, and set Normal OLPC
Algorithm Method, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > SCCPCH Configuration, and set
Maximum FACH Power, S-CCPCH TFCI Field Power Offset, and S-CCPCH Pilot
Field Power Offset, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Basic Compress Mode
Configuration, and set Recovery Period Power Control Mode, Initial Transmit
Power Mode, DeltaSIR1, DeltaSIR2, DeltaSIRafter1, and DeltaSIRafter2, see the
following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > Iub Link, and set
Adjustment Type for DL Power balancing, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > NodeB Dedicated Measurement Profile > NodeB Dedicated
Measurement Configuration, and set Function of Configuration Parameters,
Dedicated Measurement Type, Measurement Filter Coefficient, Report
Characteristics, Choice Report Periodicity Scale, and Report Period, see the
following figure.
Steps 2. Move UE1 away from Cell1. RNC will adjust the SIR Target.
Expected
1. SIR Target is adjusted with the bler for the whole time.
Result
3. Cell1 and Cell2 have the same frequency. Configure Cell1 and Cell2
Prerequisite
adjacent cells with different coverage.
2. UE1 moves from Cell1 to Cell2 to trigger event 1A. Cell2 is added into
Steps
the active set. Maintain the call in 2-way SHO state for 60s.
None.
None.
When the QE based OLPC algorithm in the uplink outer loop power control is
activated, the system capacity can be increased.
When the QE based OLPC algorithm in the uplink outer loop power control is
activated, the service quality will be reduced.
ii. Power balancing is a basic feature, and it is activated all the time.
None.
7 Abbreviation
Abbreviation Full Name
ACK Acknowledgement
DL Downlink
FP Frame Protocol
PL Puncture Limitation
QE Quality Estimate
TB Transport Block
TF Transport Format
TX Transmission
UE User Equipment
8 Reference Document
[1] ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Radio Parameter
Reference
[2] ZXWR RNC (V3.14.10.14) Radio Network Controller Radio Parameter Reference
[3] ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Performance Counter
Reference
[4] ZXWR RNC (V3.14.10.14) Radio Network Controller Performance Counter Reference