zte umts power control feature guide_v8.5_201312_548040

Power Control Feature Guide

WCDMA RAN


ZTE Confidential Proprietary 1


Version Date Author Reviewer Revision History

V7.0 2012-4-12 Wang

Shaojiang Chen Qi

1. Deleted “RNC static assigning mode” of

the HSDPA total power, and modified the

description about the “RNC dynamic

assigning mode”.

2. Modified the description of some

parameters and the path of all

parameters.

3. Added the Qchat used

dpcchPcpLenQChat and

srbDelayQChat.

4. Indicated the DL initial power offset for

balancing.

V8.0 2012-12-6 Wang

Shaojiang Chen Qi

1. Added Section 2.7 “Power Control

Algorithm Enhancement” the following

related algorithms:

1) Section 3.1.5.2 “BLER Target based

OLPC”.

2) Section 3.3.5.2 “NHR Target based

HSUPA OLPC”.

3) Section 3.3.5.4 “Coupling of HSUPA

and R99 outer loop power control”.

4) Section 3.7 “Period BER based

OLPC”.

5) Section 3.8 “SIR Target Rapid

Convergence”.

6) Section 3.9 “High Priority OLPC”.

2. Added Section 2.8 “Load Adaptive

Power Control”, and made the following

modifications:

1) Added Section 3.10 “Load and ARP

based Power Control Parameters

Configuration”.

2) Deleted the feature “R99 CS AMR



Service BLER Target Adjustment” and

the related parameters, and modified the

“HSUPA adaptive transmission” in

Section 2.6 and Section 3.1.5 “HSUPA

Uplink Outer Loop Power Control” and

the related parameters.

3. Added Section 2.9 “HSDPA CQI

Adjustment”. Added section 3.11 “Load

based CQI Feedback Cycle and CQI

Repetition Factor”, and added the related

parameters.

4. Added Section 3.1.9 “IMEI Based Power

Control” and the related parameters.

5. Added Section 2.10 “Common Channel

Power Optimization”. Added Section

3.12 “Common Channel Power

Optimization” and the related

parameters.

V8.5 2013-11-14 Wang

Shaojiang Chen Qi

1. Deleted Section 2.8 "ZWF21-04-013

Load Adaptive Power Control" and 3.10

"Load and ARP based Power Control

Parameters", both of which are

described in another separate manual.

© 2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used

without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document is subjected to

change without notice.



TABLE OF CONTENTS

1 Feature Attributes .............................................................................................. 7

2 Overview ............................................................................................................ 7

2.1 ZWF21-04-008 Downlink Power Balance ............................................................. 8

2.2 ZWF21-04-009 Power Control ............................................................................. 8

2.3 ZWF21-04-024 User Differentiated Power Control ............................................... 9

2.4 ZWF23-04-005 Power Allocation for HSDPA ..................................................... 10

2.5 ZWF25-04-006 Power Allocation for HSUPA ..................................................... 11

2.6 ZWF25-04-009 HSUPA Adaptive Transmission ................................................. 12

2.7 ZWF21-04-015 Power Control Algorithm Enhancement ..................................... 12

2.8 ZWF23-01-015 HSDPA CQI Adjustment ............................................................ 12

2.9 ZWF21-41-010 Common Channel Power Optimization ...................................... 13

3 Technical Descriptions ................................................................................... 13

3.1 R99 Power Control ............................................................................................. 13

3.1.1 Uplink Open Loop Power Control of R99 ........................................................... 13

3.1.2 Downlink Open Loop Power Control of R99 ....................................................... 23

3.1.3 Uplink inner loop power control of R99 ............................................................... 29

3.1.4 Downlink Inner Loop Power Control Of R99 ....................................................... 34

3.1.5 Uplink Outer Loop Power Control of R99 ........................................................... 38

3.1.6 Downlink Outer Loop Power Control of R99 ....................................................... 43

3.1.7 Downlink Power Balancing ................................................................................. 43

3.1.8 User Differentiated Power Control ...................................................................... 47

3.1.9 IMEI based Power Control ................................................................................. 48

3.2 HSDPA Power Control ....................................................................................... 49

3.2.1 Methods to Determine the Power Offsets of HS-DPCCH-related Domains ........ 50

3.2.2 Method to Determine HS-PDSCH Measurement Power Offset .......................... 52

3.2.3 HSDPA Power Control in Compressed Mode .................................................... 53

3.2.4 Total Power Allocation of HSPA ......................................................................... 54

3.3 HSUPA Power Control ....................................................................................... 58

3.3.1 Method to Determine Uplink E-DPCCH/DPCCH Power Offset ........................... 58

3.3.2 Method to Determine Power Offset of Uplink E-DPDCH/DPCCH ....................... 59

3.3.3 Method to determine Downlink E-AGCH/RGCH/HICH Power ............................ 63

3.3.4 HSUPA Power Control in Compressed Mode .................................................... 67

3.3.5 HSUPA Uplink Outer Loop Power Control ......................................................... 68

3.4 MBMS Power Control ........................................................................................ 77

3.5 Downlink Enhanced CELL_FACH Power Control .............................................. 77

3.6 Uplink Enhanced CELL_FACH Power Control ................................................... 77

3.7 Period BER based OLPC ................................................................................... 79



3.8 SIR Target Rapid Convergence ......................................................................... 80

3.9 High Priority OLPC ............................................................................................. 81

3.9.1 Algorithm Description ......................................................................................... 81

3.9.2 Related measurement ........................................................................................ 83

3.10 Load based CQI Feedback Cycle and CQI Repetition Factor ............................ 84

3.10.1 Algorithm Description ......................................................................................... 84

3.11 Common Channel Power Optimization .............................................................. 86

4 Parameters and Configurations ..................................................................... 86

4.1 Common Parameters ......................................................................................... 86

4.1.1 List of Common Parameters .............................................................................. 86

4.1.2 Configuration of Common Parameters ............................................................... 87

4.2 Related Parameters of R99 downlink Power Balancing ..................................... 99

4.2.1 List of Related Parameters of R99 Downlink Power Balancing .......................... 99

4.2.2 Configuration Related Parameters of R99 Downlink Power Balancing ............... 99

4.3 Related Parameters of R99 Power Control ...................................................... 104

4.3.1 List of Related Parameters of R99 Power Control ............................................ 104

4.3.2 Configuration of Related Parameters of R99 Power Control ............................ 106

4.4 Related Parameters of HSDPA Power Control ................................................. 129

4.4.1 List of Related Parameters of HSDPA Power Control ...................................... 129

4.4.2 Configuration of Related Parameters of HSDPA Power Control ....................... 130

4.5 Related Parameters of HSUPA Power Control ................................................. 139

4.5.1 List of Related Parameters of HSUPA Power Control ...................................... 139

4.5.2 Configuration of Related Parameters of HSUPA Power Control ....................... 141

4.6 Related Parameters of MBMS Power Control .................................................. 158

4.7 Related Parameters of Downlink Enhanced CELL_FACH Power Control ........ 158

4.7.1 List of Related Parameters of Downlink Enhanced CELL_FACH Power Control158

4.7.2 Configuration of Related Parameters of Downlink Enhanced CELL_FACH

Power Control .................................................................................................. 159

4.8 Related Parameters of Uplink Enhanced CELL_FACH Power Control ............. 160

4.8.1 List of Related Parameters of Uplink Enhanced CELL_FACH Power Control .. 160

4.8.2 Configuration of Related Parameters of Uplink Enhanced CELL_FACH Power

Control ............................................................................................................. 161

4.9 Related Parameters of Period BER based OLPC ............................................ 166

4.9.1 List of Related Parameters of Period BER based OLPC .................................. 166

4.9.2 Configuration of Related Parameters of Period BER based OLPC ................... 166

4.10 Related Parameters of SIR Target Rapid Convergence ................................... 169

4.10.1 List of Related Parameters of SIR Target Rapid Convergence ........................ 169

4.10.2 Configuration of Related Parameters of SIR Target Rapid Convergence ......... 170

4.11 Related Parameters of High Priority OLPC ...................................................... 172

4.11.1 List of Related Parameters of High Priority OLPC ............................................ 172



4.12 Related Parameters of Load based CQI Feedback Cycle and CQI Repetition

Factor .............................................................................................................. 175

4.12.1 List of Related Parameters of Load based CQI Feedback Cycle and CQI

Repetition Factor ............................................................................................. 175

4.12.2 Configuration of Related Parameters of Load based CQI Feedback Cycle and

CQI Repetition Factor ...................................................................................... 175

4.13 Related Parameters of Common Channel Power Optimization ........................ 177

4.13.1 List of Related Parameters of Common Channel Power Optimization .............. 177

4.13.2 Configuration of Related Parameters of Common Channel Power Optimization177

5 Counter and Alarm ........................................................................................ 178

5.1 Counter List ..................................................................................................... 178

5.1.1 Statistic of Cell TCP ......................................................................................... 178

5.1.2 Distribution of TCP ........................................................................................... 178

5.1.3 Statistic of HS Cell DL Configured TCP ........................................................... 179

5.1.4 Statistic of Cell NonHsTcp ............................................................................... 179

5.1.5 Distribution of Cell NonHsTcp .......................................................................... 180

5.1.6 Statistic of Cell HsTcp ...................................................................................... 180

5.2 Alarm List ......................................................................................................... 181

6 Glossary ......................................................................................................... 181



FIGURES

Figure 3-1 The frame of HSPA power allocated .................................................................55

Figure 3-2 Dynamic Power Adjustment for HSPA and DPCH ............................................55

Figure 3-3 Schematic Diagram of “SIRtarget increase”, “SIRtarget decrease”, “SIRtarget keep” and

“NHR invalid” based on NHR statistical ................................................................................71

Figure 3-4 Schematic Diagram of Slide Window Statistics .................................................72

Figure 3-5 Coupling OLPC for HSUPA and R99 ................................................................76

TABLES

Table 3-1 c and d Values for the UL WAMR6.60k~23.85k Service ..................................17

Table 3-2 c and d Values for the UL NAMR4.75k~12.2k Service .....................................18

Table 3- c and d Values for the UL PS64k streaming/interactive/background Service ..19

Table 3-4 c and d Values for the UL PS128k streaming/interactive/background Service .19

Table 3-5 c and d Values for the UL PS384k and services with higher rates streaming/

interactive/background Service .............................................................................................20

Table 3-6 Quantified Amplitude Relation between ∆ACK, ∆NACK, ∆CQI and Ahs .......................51

Table 3-7 Quantified Amplitude Relation between Aec and ∆E-DPCCH....................................59

Table 3-8 Quantified Amplitude Relation between ∆E-DPDCH and Aed ...................................60

Table 3-9 Combination of Outer Loop Adjustment of DCH and E-DCH ..............................75



1 Feature Attributes

System version: [RNC V3.12.10/V4.12.10, the Node B V4.12.10, OMMR V12.12.41,

OMMB V12.12.40]

Attribute: [Mandatory + Optional]

Involved NEs:

UE Node B RNC MSCS MGW SGSN GGSN HLR

√ √ √ - - - - -

Note:

*-: Not involved.

*√: Involved.

Dependency: [None]

Mutual exclusion: [None]

Note: [None]

2 Overview

The uplink of the WCDMA system is interference limited, the transmit power of all other

user equipment (UE) acts as interference for a mobile station (MS). This is because the

MSs are distributed randomly in a cell, some being far and some being near to the Node

B. If all MSs transmit with the same power, the high-power signals received closer to the

Node B will cover up the low-power signals received far from the Node B, and many

errors occur affecting the subscribers far from the Node B, hence the far-near effect. In

addition, the radio channel used for mobile communication has a wide-band dynamic

frequency, which is usually affected by various Doppler fast fading effects along the radio

link. Therefore, a fast and accurate power control mechanism is necessary to ensure the

quality of service for all subscribers.

There are many power control algorithms: uplink open loop power control, downlink open

loop power control, uplink inner loop power control, downlink inner loop power control,

uplink outer loop power control, downlink outer loop power control, and downlink power



balancing. Through the functional evolution of WCDMA, power control can be classified

into R99, HSDPA, HSUPA and MBMS types.

2.1 ZWF21-04-008 Downlink Power Balance

During the soft handover or macro diversity status, UE can communicate with all cells in

the active set. The UE sends the same TPC command to the cells in the active set. But

as each link travels through different transmission paths, errors are produced in the TPC

command and some Node Bs receive the wrong TPC command. As a result, some Node

Bs increases transmit power and some Node Bs decreases transmit power, hence power

drifting. Power drifting is usually eliminated through the power balancing approach.

Downlink power balancing is originated by the RNC. It allocates a power benchmark for

reference or common reference for each radio link in the active set. The Node B

calculates the power value of each link adjusted as a result of power balancing and adds

the value into the current power value used for downlink inner loop power control. By

using this method, power drifting is prevented on the radio link.

This feature is implemented by the RNC and Node B and used together with the inner

loop power control.

2.2 ZWF21-04-009 Power Control

Power control comprises uplink power control and downlink power control. Uplink power

control is used to eliminate far-near effect to ensure system capacity and user QoS.

Downlink power control is used to improve system capacity on the condition that the user

QoS is guaranteed. Power control comes in three types in two directions: open loop

power control, outer loop power control and inner loop power control.

Open loop power control sets the initial transmit power of the physical channel. Inner

loop power control is the major part of power control and is used to overcome the fast

fading along the radio path. Both open and inner loop power control are realized on the

physical layer of the Node B and UE. The parameters of inner loop power control are

configured through the RNC. Outer loop power control is used to ensure the quality of the

radio link by setting the SIRtarget value as needed by the inner loop power control. Uplink



outer loop power control is realized through the RNC and downlink outer loop power

control is realized through the UE.

Different types of power control are described as follows:

Inner loop power control is usually used on the dedicated physical channel. It adjusts the

transmit power to make the SIR of RX power reach a target value so that the problem of

channel fading is solved. The principle of uplink inner loop power control is: The Node B

compares the received uplink SIR against the target SIR (SIRtarget) and then sends the

power control command to the UE to adjust the transmit power, so that the SIR value

changes quickly to approach the target SIR value. If the measured SIR is lower (higher)

than the target SIR, 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. Inner loop power control has a higher precision than open loop power control

and is the most fundamental power control.

Open loop power control is used to determine the initial transmit power level of various

physical channels.

The purpose of outer loop power control is to adjust the SIRtarget used by inner loop power

control based on the quality of service, thus adjusting the subscriber’s transmission

power. Here the quality of service is evaluated through the check code of the CRC

carried in the frame protocol (FP). If the quality of the radio channel deteriorates when a

subscriber is making a call, outer loop power control can trace the quality status quickly

and ensure the subscriber’s call quality. If the quality of the radio channel becomes very

good, that is, even better than the BLERtarget required by the service, outer loop power

control can decrease SIRtarget so that the subscriber’s transmit power is decreased and

system capacity is enhanced. With outer loop power control, the transmission power of a

subscriber in the process of ongoing communication is adjusted to be as much as the

BLERtarget required by the service, no radio resource is wasted while the quality of service

is guaranteed.

2.3 ZWF21-04-024 User Differentiated Power Control

When the UEs are using the same service, user differentiated power control can grant



different basic priority level UEs different maximum uplink or downlink DPCH

transmission power levels. This is achieved by using a method that adds the maximum

allowed uplink or downlink DPCH transmission power based on service and a power

offset based on the basic priority. The higher the basic priority of the UE, the larger the

power offset, so that a larger actual maximum allowed uplink or downlink DPCH

transmission power level of the higher priority UE when all UEs are using the same

service is ensured.

2.4 ZWF23-04-005 Power Allocation for HSDPA

The power control of HSDPA includes the total power allocation of HSDPA and

configuration of the HS-PDSCH measurement power offset.

The allocation of HSDPA total power is performed in two modes: dynamic allocation by

the RNC and free allocation by the Node B.

Dynamic allocation by the RNC means that the RNC dynamically adjusts the maximum

transmission power usable by HSDPA. In the following three cases, the RNC is triggered

to re-allocate the total power of the HSDPA.

If congestion is caused by limited HSDPA power, the total HSDPA power

quota can be increased.

HSDPA total power is dynamically adjusted in light of the actual power

occupied by an R99 subscriber.

HSDPA power is dynamically adjusted as a result of cell overload.

Free allocation by the Node B: The Node B allocates power to HSDPA service

dynamically and quickly depending on the power occupied by the R99 service.

The HS-PDSCH measurement power offset is used for the UE to calculate the CQI value

for feedback. The RNC can be configured with a reasonable HS-PDSCH measurement

power offset based on the total power of a cell.



2.5 ZWF25-04-006 Power Allocation for HSUPA

HSUPA power control includes uplink open loop power control, uplink outer loop power

control and downlink open loop power control.

The uplink open loop power control of HSUPA refers to determining the E-DCH MAC-d

flow power offset and the power offset (PO) corresponding to the reference E-TFC and

reference E-TFC.

The E-DCH MAC-d flow power offset is used to reflect the quality differences among

varying services. For example, the power offset of a higher-priority service can be

configured to be higher than that of a lower-priority service, so that the quality of the

higher-priority service is better. Therefore, different E-DCH MAC-d flow power offsets are

configured for different services to reflect differentiated services for configuration of the

E-DCH MAC-d Flow Power Offset.

PO corresponding to the reference E-TFC and reference E-TFC: Once UE selects an

E-TFC, it calculates the power needed by the E-TFC on the basis of the reference E-TFC

and reference PO.

The principle of uplink outer loop power control of HSUPA is similar to that of outer loop

power control of R99, that is, the SIRtarget used by inner loop power control is adjusted in

light of service quality to adjust a subscriber’s transmit power. The difference being that

the service quality here is evaluated by the retransmission attempts of FP frames. That is,

the more times the FP frame is retransmitted, the worse the channel quality is. In this

case, a higher SIRtarget is needed to increase the transmit power; otherwise, a lower

SIRtarget is needed to decrease the transmit power.

Downlink open loop power control of HSUPA

In the downlink of HSUPA, the information of E-DCH AG, RG and ACK/NACK is sent to

the UE. To make sure that the UE receives such control information correctly, a

reasonable E-AGCH/E-RGCH/E-HICH power offset should be configured for these

physical channels.



2.6 ZWF25-04-009 HSUPA Adaptive Transmission

For HSUPA service, lower HARQ retransmission is good for service quality, but for the

system, HARQ retransmission of the HSUPA service has retransmission gain,

appropriate HARQ retransmission can improve system capacity. This algorithm can

configure OLPC parameters adaptively based on the cell load. In this way, when the cell

load is low, the number of HARQ retransmissions will be decreased, and the service

quality will be increased. When the cell load is high, the number of HARQ

retransmissions will be increased, and the system capacity will be increased.

2.7 ZWF21-04-015 Power Control Algorithm

Enhancement

ZTE RAN improves the OLPC algorithm continuously. In order to improve the initial SIR

target convergence speed, the algorithm “SIR target rapid convergence” is introduced, it

makes the initial SIR target convergence to the target SIR based on the BLER target

rapidly, and this avoids the problem of system capacity being reduced by slow

convergence. In order to make the power control response to radio conditions change

rapidly, and set the BLER of the R99 service closer to the BLER target and the NHR of

the HSUPA service closer to the NHR target, the algorithms “BLER target based OLPC”

for R99 and “NHR target based OLPC” for HSUPA are introduced, the new algorithms

are excellent for controlling service quality. In addition, for the traditional OLPC which can

only suit the condition when there are a lot of TBs, the “period BER based OLPC” is

introduced for improving the performance under the condition where no TBs or few TBs

exist.

2.8 ZWF23-01-015 HSDPA CQI Adjustment

The HSDPA CQI information is reported over a period, so when the cell uplink load is

heavy and there are a lot of HSDPA users, the periodic CQI report will result in an uplink

load increase, and it will affect the uplink coverage, so ZTE introduced the HSDPA CQI

adjustment algorithm. When the load is low, the short CQI feedback cycle is used to suit

the radio condition change and improve the efficiency of HSDPA scheduling. Also, when



the load is heavy, the long CQI feedback cycle is used to reduce the load and improve

the capacity. For the CS and PS multi-services user, in order to reduce the effect to the

CS service, the long CQI feedback cycle is used. In order to adjust the CQI feedback

cycle, the CQI repetition factor also needs to be adjusted accordingly.

2.9 ZWF21-41-010 Common Channel Power

Optimization

In order to reduce the power consumption to support more R99 and HSDPA users, the

Node B optimizes the PICH and SCCPCH power transmission. When there is no PI(PI =

0) or no data, the Node B reduces or closes the transmission power of the channel and

while there is PI(PI = 1) or any data, the Node B resumes the transmission power

configured by the RNC.

3 Technical Descriptions

3.1 R99 Power Control

3.1.1 Uplink Open Loop Power Control of R99

3.1.1.1 Uplink open loop power control of the R99 common channel

Algorithm

The uplink open loop power control of a common channel mainly refers to determining

the PRACH transmit power level.

In the FDD mode, the UE performs the following operations before it transmits signals to

PRACH.

1 The UE obtains “Primary CPICH DL TX Power” and “Constant Value” from System

information Block type 6 (or System information Block type 5 if type 6 is not

broadcast). The UE obtains “UL Interference” from System information Block type 7.



2 The UE measures and obtains CPICH_RSCP, the channel code power of CPICH.

3 The UE calculates the transmit power of the first preamble using the following

formula:

Preamble_Initial_Power = Primary CPICH DL TX power – CPICH_RSCP +UL

interference + Constant Value (3.1-1)

Where,

Primary CPICH DL TX power (UUtranCellFDD.primaryCpichPower) is the

transmit power of the Primary CPICH channel.

UL interference is the uplink interference, which is measured and obtained by

the Node B and updated in real time in SIB7.

Constant Value (ConstVal) is a value related with the cell environment. It is a

value that depends on the service rate and quality carried by PRACH.

If the parameters in the system’s 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 gets started, the UE sets the preamble

transmit power as Preamble_Initial_Power. If the value of Preamble_Initial_Power

exceeds the allowed maximum power MaxRACHTxPwr, the UE sets the preamble

transmit power as the allowed maximum power. If no response (+1 or -1) of AICH is

received after the preamble composed of the selected signature and scramble is sent out,

PRACH selects a new signature in the next timeslot, uses it to form a preamble together

with the scramble and sends the preamble again. Next, PRACH increases the preamble

transmit power by the Power Ramp Step [dB]. If the transmission counter is 0, the access

process exists. If a positive response is received from AICH, the random access

message is transmitted. 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 preceding description we get to the formula for calculating the transmit power

of the control part of the PRACH message:

m-p PStep RampPower ernitial_PowPreamble_IwerPRACH_C_Po (3.1-2)



Where,

Power Ramp Step (PRStep) is the power offset between two continuous

preambles.

Pp_m is the power offset between the control channel and the last preamble of

the message part, its value is 2dB.

In addition, RACH is similar to the uplink DPCH. That is, its data domain and control

domain are sent out after being multiplexed with I and Q channels and then added by

scramble on the physical layer. Therefore, parameters c and d (gain factor of the

control channel and data channel of the message part) also need to be determined. Here,

c is 11, and d is 15.

UL interference can be updated in SIB 7 in two ways, which can be selected with the

parameter SIB7Originator.

If SIB7Originator takes the value of the RNC, the Node B reports the common

measurement report of RTWP to RNC. When RNC detects that the change of

RTWP is no less than the uplink interference update threshold (1dB), it

broadcasts it to the UE through the broadcast channel.

If SIB7Originator takes the Node B, the Node B updates the UL interference

directly in the system message based on the change of RTWP.

3.1.1.2 Uplink open loop power control of R99 dedicated channel

Uplink open loop power control of the dedicated channel refers to determining the initial

transmit power of DPCCH, and determining the gain factor and d of the uplink

control physical channel and uplink data physical channel.

1 Power configuration of DPCCH:

As required by the related standard, the UE should start uplink inner loop power control

according to the following power level when the first DPCCH is being set up:

c



DPCCH_Initial_power = DPCCH_Power_offset - CPICH_RSCP (3.1-3)

Where,

The value of DPCCH_Power_offset is determined by the DPCCH open loop

power control method.

The value of CPICH_RSCP is the CPICH channel code power obtained by the

UE through measurement.

DPCCH_Power_offset is calculated using the following formula:

PowerTXCPICHdBPGdBmINdBNEOffsetPowerDPCCH TTb __)())(()(/__ 0

(3.1-4)

Where,

Eb/No is the quality factor of the DPCCH PILOT domain

(USrvDivPc.dpcchPilotEbN0).

NT+IT is the uplink interference, which is obtained by the Node B through

measurements and updated in real time in SIB7.

PG is the spectrum spread gain, 256.

CPICH_TX_Power(UUtranCellFDD.primaryCpichPower) is the transmit power

of the P-CPICH.

Description: The quality factor (USrvDivPc.dpcchPilotEbN0) of the DPCCH PILOT

domain is related with the cell load scenario (UUtranCellFDD.loadScene), the diversity

mode (TxDivMod) and sub-types of service. These service related power control

parameters are obtained in the following ways: First, obtain the used service related

power control profile (refUSrvPcProfile) from the configuration items of UUtranCellFDD.

Next, obtain the instance of the object USrvPcProfile in the used service related power

control profile object USrvPcProfile (the parameters of this object are suited for the load

scenario indicated by USrvPcProfile.intialloadscene), which is the sub-object of the

object USrvFunction. Next, obtain the instance of the sub-object USrvPc of the



USrvPcProfile object instance. In these instances of the sub-object USrvPc, sub-service

type (USrvPc.srvType) the related power control parameter can be obtained. Finally, the

service and diversity mode related power control parameters can be obtained in the

instances of the sub-object USrvDivPc of these USrvPc object instances.

2 How c and d (gain factor of uplink control / data physical channel) are determined

and configured:

Different strategies are adopted depending on the features of a single service and

mixed services:

i. For a single service, c and d are configured directly according to different

service rates and different TFCs. It is usually required that either c or d must

be 15. Table 3-1 to Table 3-5 list the c and d values configured in the ZTE

RNC for several common services in the case of different TFC formats. In the

tables, 1×144 is the format of signaling transmission.

Table 3-1 c and d Values for the UL WAMR6.60k~23.85k Service

TFC Format c d

0×40, 0×405, 0×0, 0×144 15 1

1×40, 0×405, 0×0, 0×144 15 8

1×54, 1×78, 0×0, 0×144 15 11

1×64, 1×113, 0×0, 0×144 15 13

1×72, 1×181, 0×0, 0×144 15 15

1×72, 1×213, 0×0, 0×144 14 15

1×72, 1×245, 0×0, 0×144 14 15

1×72, 1×293, 0×0, 0×144 13 15

1×72, 1×325, 0×0, 0×144 12 15

1×72, 1×389, 0×0, 0×144 12 15

1×72, 1×405, 0×0, 0×144 11 15

0×40, 0×405, 0×0, 1×144 15 8

1×40, 0×405, 0×0, 1×144 15 11

1×54, 1×78, 0×0, 1×144 15 14



TFC Format c d

1×64, 1×113, 0×0, 1×144 15 15

1×72, 1×181, 0×0, 1×144 13 15

1×72, 1×213, 0×0, 1×144 13 15

1×72, 1×245, 0×0, 1×144 12 15

1×72, 1×293, 0×0, 1×144 12 15

1×72, 1×325, 0×0, 1×144 11 15

1×72, 1×389, 0×0, 1×144 11 15

1×72, 1×405, 0×0, 1×144 11 15

Table 3-2 c and d Values for the UL NAMR4.75k~12.2k Service

TFC Format c d

0×39, 0×103, 0×60, 0×144 15 1

1×39, 0×103, 0×60, 0×144 15 9

1×42, 1×53, 0×60, 0×144 15 12

1×49, 1×54, 0×60, 0×144 15 12

1×55, 1×63, 0×60, 0×144 15 13

1×58, 1×76, 0×60, 0×144 15 14

1×61, 1×87, 0×60, 0×144 15 14

1×75, 1×84, 0×60, 0×144 15 15

1×65, 1×99, 1×40, 0×144 14 15

1×81, 1×103, 1×60, 0×144 13 15

0×39, 0×103, 0×60, 1×144 15 12

1×39, 0×103, 0×60, 1×144 15 14

1×42, 1×53, 0×60, 1×144 14 15

1×49, 1×54, 0×60, 1×144 13 15

1×55, 1×63, 0×60, 1×144 13 15

1×58, 1×76, 0×60, 1×144 12 15

1×61, 1×87, 0×60, 1×144 12 15

1×75, 1×84, 0×60, 1×144 12 15



TFC Format c d

1×65, 1×99, 1×40, 1×144 11 15

1×81, 1×103, 1×60, 1×144 11 15

Table 3-3 c and d Values for the UL PS64k streaming/interactive/background Service

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

Table 3-4 c and d Values for the UL PS128k streaming/interactive/background

Service

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

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 PS384k 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

For mixed service, the c and d values are calculated by the RNC and configured for

UE.

3 Calculation of c and d for mixed services

If service A and service B are mixed (including signaling): (1) For the transmission

combination (TFCmulti) when service A and B are being combined, the number of bits per

frame mapped to the transport channel by each service is calculated according to the

transmission format indication (TFI_i) of each service corresponding to TFCmulti. (2) The

service with the most 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. (3) c and d corresponding to TFCsingle (formed by TFI_i of the

selected reference service) are taken as the reference c and d. (4) The following

formula is used to calculate and obtain the c and d corresponding to this TFCmulti.

ref

j

j

ref

refc

refd

jK

K

L

LA

,

,

(3.1-5)



If Aj > 1, make 0.1, jd , jc,

is the maximum quantified value that satisfies the

condition of jc,<= 1 / Aj.

Note: If jc, =0 is obtained, then jc,

=1/15.

If Aj <= 1, then jd , is the minimum quantified value that satisfies the condition of

jd ,>= Aj, while

0.1, jc .

Where,

- c,ref and d,ref are the gain factors corresponding to the above mentioned

TFCsingle; c,j and d,j are the gain factor corresponding to the jth 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.

-

i

iiref NRMK

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.

i

iij NRMK

Parameters in this formula take the same meanings as those in the previous

formula. 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 being



performed while the power control preamble is sent out. Length of the preamble

depends on DpcchPcpLen (or dpcchPcpLenQChat for Qchat users). At the same

time, while starting to send uplink DPDCH data, no signaling ranging RB0~RB4 is

included in the first several frames. The number of delayed signaling frames

depends on SrbDelay (or srbDelayQChat for Qchat users).

3.1.1.3 Uplink Open Loop Power Control of R99 in Compressed Mode

The gain factors c,C,j and d,C,j corresponding to a certain TFC used by the compressed

frame while in the compressed mode are obtained from c and d used by radio frames in

normal mode. The formula for the calculation is as follows:

Npilo tCslo ts

Cp ilo t

jjCNN

NAA

,,

,

,

15

(3.1-6)

Where,

Aj is the ratio of d and c in normal mode.

AC,j is the ratio of d,C and c,C in compressed mode.

Npilot,C is the number of pilot bits per timeslot in the compressed frame in

compressed mode

Npilot,N is the number of pilot bits per timeslot in normal mode.

Nslots,C is the number of timeslots used for data sending in the compressed

frame in compressed mode.

AC,j is obtained with the previous 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.

If AC,j > 1, then 0.1,, jCd , jCc ,,

is of the maximum quantified value

that satisfies the condition jCc ,,<= 1 / Aj . Note: If jCc ,,

= 0 is obtained,

then make jCc ,, = 1/15.



If AC,j <= 1, then jd , is of the minimum quantified value that satisfies the

condition jd ,>= Aj, while

0.1, jc .

3.1.2 Downlink Open Loop Power Control of R99

3.1.2.1 Configuration of R99 downlink common channel initial power

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 transmit power (UUtranCellFDD.primaryCpichPower) of P-CPICH depends on the

proportion of maximum transmit power of a cell. The power of P-CCPCH, P-SCH

(PrimarySchPower), S-SCH (SecondarySchPower), AICH (AichPower), and PICH

(PichPower) depend on the offset to the power of P-CPICH

(UUtranCellFDD.primaryCpichPower). BCH is mapped one-to-one to the P-CCPCH

physical channel. P-CCPCH power is the same as the power of BCH (BchPower).

Presently, in a non MIMO cell (cell portion), the S-CPICH power is scpichPwr, and in a

MIMO cell, the S-CPICH power is mimoScpichPwr.

As the physical channel S-CCPCH bears the transport channel of PCH and FACH, and

the number of FACH channels is variable, the transmit power (PchPower) of each PCH

and the maximum transmit power (MaxFachPwr) allowed for each FACH borne by a

certain S-CCPCH is specified in the related protocol. As 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 domain 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 domain and Pilot domain of S-CCPCH are indicated respectively by the

offsets (PO1 and PO3) as opposed to the transmit power of the data domain.



3.1.2.2 Downlink open loop power control of 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 single services

and mixed services. At present, the estimation power algorithm based on CPICH Ec/N0

is adopted for calculating the initial transmit power.

1 Initial power of downlink dedicated channel

When a subscriber is accessing or being handover, and a downlink dedicated physical

channel should be set up for this subscriber. The RNC should configure the downlink

initial transmit power for the Node B. The strategy for configuring the initial transmit

power of the downlink dedicated channel affects the performance of the links and

capacity of the system.

The following formula is used to calculate the initial transmit power:

t PowerOffse

101

,

k 2

1k

minmax

min

0

,

,

to ta ltxLcp ichc

CPICHtx

in ittx P

kN

E

P

PGP

(3.1-7)

Where,

PG is the service processing gain, that is, W/R, W being 3.84M while R being

the bit rate of the service.

CPICHtxP , is transmission power of the CPICH (dBm).

0N

E cp ichc

is CPICH Ec/No(dB) reported by the UE (for blind handover based

on “Overlap” or “Covers” (ShareCover refers to <ZTE UMTS Load Balance Feature

Guide.doc >), the CPICH RSCP/ CPICH Ec/N0/PATHLOSS value of the target

cell is the same as that of the source cell) reported from the UE. UE-reported

CPICH Ec/No is stored in RNC and valid within 65535s; if a valid CPICH Ec/No



is unavailable, the default value of CpichEcN0 (refer to <ZTE UMTS Admission

Control Feature Guide.doc >) is used. Note: The CPICH Ec/No in the Iur interface

is calculated by the CPICH Ec/No of the UE measurement result minus

IurEcNoDelta.

min is the lower limit of the downlink orthogonal factor (MinOrthogFactor). Its

description and value can be found in the ZTE UMTS Admission Control

Feature Guide.

max is the upper limit of the downlink orthogonal factor (MaxOrthogFactor).

Its description and value can be found in the ZTE UMTS Admission Control

Feature Guide.

k is the coefficient factor. Its fixed value is 0.01.

L represents path loss. L is obtained from the measurement result reported by

the UE. If L cannot be obtained from the measurement result, its value is

130dB.

The rule for obtaining L from the measurement result reported from the UE as

following.

If the measurement quantity of the UE is Pathloss, L=Valuepathloss.

If the measurement quantity of the UE is RSCP, L= PPCPICH - ValueRSCP. The

PPCPICH refers to the transmit power of the PCPICH.

k1 and k2 are scenario parameters. The values of parameters k1 and k2 vary

with the 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

K2=-33.5849 K2=-25.8549 K2=-22.8249 K2=-21.5249

Ptx,total is the total transmit power of a cell before a subscriber 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 common measurement report of the HS-DSCH Required

Power and Transmitted carrier power of all codes not used for HS

( ).

β=10^((Eb/N0)/10), where Eb/N0 is the Eb/N0 of the sub-service configured

corresponding to the current rate of the access service. Typical values of

Eb/N0 are:

Traffic Class Data Rate Downlink Traffic Eb/N0 (dB)

Conversational DL WAMR6.60k~23.85k 5.1

Conversational DL 64K(PS Conversational

Video) 5.2

Conversational DL NAMR4.75k~12.2k 5.1

Streaming PS64k 1.7

Streaming PS384k 0.9

Streaming PS128k 0.9

Interactive PS64k 4.8



Background PS64k 1.7



Streaming CS64k 1.7


Background PS8k 6.9

PowerOffset is different for a different situation as the following:

i. Add RL in SRNC.

Situation of Adding RL in SRNC PowerOffset

Call Setup POSetup

Soft or Softer Handover POSoftHO

RAB Hard Handover (RAB on DCH) PORabHardHO

Incoming Relocation (RAB on DCH)

MaxSpi

Spi

Spi 0

NOHSDSCHPower HSDSCHRequiredPower



Situation of Adding RL in SRNC PowerOffset

CELL_FACH or CELL_PCH Transfer to CELL_DCH state

(RAB on DCH)

Balancing in RAB assignment and call holding procedure

(RAB on DCH)

Hard Handover for only SRB on DPDCH

POSrbHardHO

Hard Handover for F-DPCH

CELL_FACH or CELL_PCH Transfer to CELL_DCH state

(RAB on HS-DSCH)

Balancing in RAB assignment and call holding procedure

(RAB on HS-DSCH)

Balancing in initial RRC procedure

Call Re-Establishment POReEstablish

ii. Add RL in DRNC.

Situation of Adding RL in DRNC PowerOffset

Add RL with RAB on DPDCH

POSoftHO Add RL for F-DPCH transmission and without service on

this RL

Add RL with SRB on DPDCH

POSrbHardHO Add RL for F-DPCH transmission and with service on this

RL

iii. For radio link reconfiguration, if need to calculate the initial power again, the

PowerOffset is 0.

To avoid excessive power occupation of the dedicated channel, the maximum

(USrvDivPc.maxDlDpchPwr) and minimum (USrvDivPc.minDlDpchPwr) values of DPCH

are specified in the 3GPP protocol. In order to show the differentiation of different basic

priority users, the actual maximum allowed downlink DPCH transmission power is

configured distinctively for different users with different basic priority levels, refers to

section “3.1.9 User Differentiated Power Control”.

To calculate the transmit power of a downlink dedicated physical channel for mixed

services, first obtain the transmit power (data part) jDPCH_POWER needed to transmit

each service with the calculation method used for a single service. Next calculate the



initial transmit power of DPCH for mixed services based on the transmit power needed

for each service. The formula is given as follows:

N

j

j PowerDPCHPowerInitialDPCH1

___

(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 domain. The power value depends on

the offset as opposed to the power of the data domain and is indicated with PO1

(DpchPO1), PO2 (DpchPO2) and PO3(DpchPO3) respectively.

Under the condition that the dynamic update PO2 switch (DynaUpdtPO2Sw) is turned on,

dynamically update the PO2 as the following: Get the PO2(DpchPO2)value based on the

DPCH data rate and traffic class, if DPCH bears multi-services, get the DpchPO2 value

respectively for each service, and then get the minimum value. The DpchPO2 value is

then sent to the Node B through the control frame. If the DPCH data rate is changed,

then get the new PO2, and send the new PO2 to the Node B. In this way, PO2 dynamic

update is completed.

The parameters involved in this section, such as USrvDivPc.maxDlDpchPwr,

USrvDivPc.minDlDpchPwr, DpchPO1, DpchPO2 and DpchPO3, are related with the cell

load scenario, the diversity mode and sub-service types. The method to obtain these

parameters is related to section 3.1.1.2.

2 Related Measurement

TCP: Transmitted Carrier Power. The internal measurement value of the Node B is

obtained from the public measurement report and reported to the RNC. The

measurement is started after the cell is set up and the public transport channel of the cell

is set up, and ended after the cell is deleted.

CPICH Ec/N0 is 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 R99 in compressed mode

As the adjustment proportion of DPDCH transmit power is the same as that of the control

domain for the downlink compressed mode, it is unnecessary to change the values of PO1,

PO2 and PO3. That is, the power offset between the control part and data part in the

compressed mode is the same as that in normal mode.

3.1.3 Uplink inner loop power control of R99

3GPP TS 25.214 specifies the following methods for calculating inner loop power control.

At the receiving end, first, the SIR measurement (SIR=Eb/No) is done for each

received radio link. Next, the measurement result is compared with the target

SIR (SIRtarget) required by the service.

If SIR ≥ SIRtarget, control information is returned to the sender with a transmit

power command (Transmitted Power Control-TPC) whose bit value is 0.

If SIR < SIRtarget, a TPC command whose bit value being 1 is returned through

the downlink control channel to the sender.

The sender determines whether to increase or decrease the transmit power

depending on the received TPC command and specified power control

algorithm. The adjustment extent = TPC_cmd×TPC_STEP_SIZE

(TpcStepSize).

This section discusses how to select the proper inner loop power control algorithm, as

the principles of inner loop power control between uplink and downlink are the same.

Description of TPC: When the UTRAN and UE setup the first radio link, before uplink

synchronization, UTRAN could not work out the TPC using the normal process. So

UTRAN sent a fixed TPC pattern in the TPC bit of the downlink DPCH. The TPC pattern

shall consist of DlTpcN instances of the pair of TPC commands ("0", "1"), followed by one

instance of TPC command "1". The TPC pattern continuously repeats but shall be forcibly

re-started at the beginning of each frame where CFN mod 4 = 0. And the TPC pattern shall

terminate once uplink synchronization is achieved.



3.1.3.1 Uplink inner loop power control of R99 in normal mode

There are two uplink inner loop power control algorithms (UlIlPcAlg), which are described

as follows.

Algorithm 1 (UlIlPcAlg =1):

With algorithm 1, the transmit power of the sender can be adjusted in every timeslot.

Each timeslot, the UE judges whether to increase or decrease the transmit power of

the UE depending on the received TPC command.

Rules for the UE to combine the TPC command are as follows:

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

being 0 indicates the transmit power should be decreased).

Algorithm 2 (UlIlPcAlg =2):

With algorithm 2, the transmit power of the sender is adjusted once every five

timeslots. Rules for the UE to combine TPC commands are (when single TPC or

several TPCs are received in one timeslot):

When a single TPC is received: Transmit power is not adjusted during the first four

timeslots (TPC_cmd=0). When the TPC command of the 5th timeslot is received, a

soft decision is made: TPC_cmd=1 if all five received TPC commands are 1;

TPC_cmd=-1 if all five received TPC commands are 0; TPC_cmd=0 in other cases.

When several TPCs are received: Transmit power is not adjusted during the first

four timeslots of the five continuous timeslots (TPC_cmd=0). At the 5th timeslot, first

determine TPCi (i=1,2,…,N, N is the number of radio link TPC commands from

different radio link sets). Next, combine the TPC command respectively as when a

single TPC is received to obtain N number of temporary TPC commands

(TPC_temp). Finally, combine TPC_cmd using the following rule:

If

5.0_1

1

N

i

itempTPCN , then TPC_cmd =1.



If any of is -1, then TPC_cmd = -1.

In other cases, TPC_cmd =0.

Description: TPC_cmd =1 indicates to increase the transmit power; TPC_cmd =-1

indicates to decrease the transmit power; TPC_cmd =0 indicates not to adjust the

transmit power.

Principle for selecting the inner loop power control algorithm:

Algorithm 1 performs inner loop power control at each timeslot, while algorithm 2

performs inner loop power control only once every five timeslots. That is, the

frequency is higher to perform inner loop power control in algorithm 1. 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.

With algorithm 2, the inner loop power control is performed every five timeslots, that

reduces the frequency required to perform inner loop power control. So algorithm 2

is applicable when the mobile communication environment is quite favorable (the

MS is or will be in static state, for instance) and the channel fades slowly or hardly

fades.

With algorithm 1, when the TPC command is received, the transmit power is either

increased or decreased. With algorithm 2, the transmit power is increased,

decreased or not changed after a soft decision is made for the TPC command at

five different timeslots. In this respect, algorithm 1 is more applicable in the case

when the channel needs the transmit power to be increased or decreased quickly

since it is fading fast.

In cases when the channel fades rather slowly, algorithm 2 is more applicable

because the BLER is good enough over an extended period even if the transmit

power is not changed during this period and the measured SIR changes very little

as opposed to the target SIR.

Description:

_ iTPC temp



When uplink inner loop power control is being performed, the transmit power

calculated by the UE can exceed the maximum transmit power of the uplink DPCH

(USrvDivPc.maxUlDpchPwr). In this case, the UE can only transmit with this

configured maximum transmit power. In order to show the differentiation of different

basic priority users, the actual maximum allowed uplink DPCH transmission power

is configured specifically for different users with different basic priority levels, refers

to section “3.1.8 User Differentiated Power Control”.

3.1.3.2 Uplink inner loop power control of R99 in compressed mode

The principle of inner loop power control in compressed mode is the same as that in

normal mode. That is, 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. The rules are: If

SIRest > SIRcm_target, then the TPC command is 0; if SIRest < SIRcm_target, then the TPC

command is 1. SIRcm_target is the target SIR value during the period when the compressed

mode is adopted.

Method to determine SIRcm_target:

SIRcm_target = SIRtarget + ΔSIRPILOT + ΔSIR1_coding + ΔSIR2_coding (3.1-9)

Where,

SIRtarget is the target SIR in normal mode.

ΔSIRPILOT = 10Log10 (Npilot,N/Npilot,curr_frame):

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.

ΔSIR1_coding and ΔSIR2_coding are obtained from the parameters of the

high-level signal configuration, that is, DeltaSIR1, DeltaSIR2, DeltaSIRafter1 and

DeltaSIRafter2 can be calculated using the following methods.



If the current uplink link frame contains the start of the first transmission gap of

the “transmission gap pattern”, then: ΔSIR1_coding = DeltaSIR1 (2.3dB).

If the current uplink link frame contains the next frame to the start of the first

transmission gap of the ”transmission gap pattern”, then: ΔSIR1_coding =

DeltaSIRafter1 (0.3dB).

If the current uplink link frame contains the start of the second transmission

gap of the ”transmission gap pattern”, then: ΔSIR2_coding = DeltaSIR2 (0dB).

If the current uplink link frame contains the next frame to the start of the

second transmission gap of the ”transmission gap pattern”, then:

ΔSIR2_coding = DeltaSIRafter2 (0dB).

In other cases, ΔSIR1_coding = 0 dB and ΔSIR2_coding = 0 dB.

As one TGPS (transmission gap pattern sequence) can have only one measurement

value but the UE can measure several values at the same time, multi 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 first and then

summed up to obtain the final available ΔSIR1_coding and ΔSIR2_coding.

N

i

icodingSIRcodingSIR1

,_1_1

N

i

icodingSIRcodingSIR1

,_2_2

Where: N is the type 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.

Because of the existence of a transmission gap of the compressed frame in compressed

mode, the format of the timeslot used in compressed mode is different from that in normal

mode. As a result, 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 already sent

in the previous timeslot, then PILOT (dB) is obtained using the following formula:

PILOT = 10Log10 (Npilot,prev/Npilot,curr);

Where,

Npilot,prev is the number of pilot bits of the previous timeslot.

Npilot,curr is the number of pilot bits of the current timeslot.

Otherwise, PILOT =0.

3.1.4 Downlink Inner Loop Power Control Of R99

3.1.4.1 Downlink inner loop power control of 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

when it estimates the kth number of the TPC command.

P(k) = P(k - 1) + PTPC(k) + Pbal(k) (3.1-10)

Where,

PTPC(k) is the kth number of power adjustment volume in the process of inner

loop power control.

Pbal(k) 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

approach a common reference power level.

Two power control modes are also available to determine PTPC(k):

Mode 1: The UE sends a TPC command at each timeslot. The UTRAN adjusts the



transmit power at each timeslot according to the TPC command.

Mode 2: The UE sends the same TPC command for three timeslots. The UTRAN

adjusts the transmit power once every three timeslots according to the TPC

command.

If there is a need to consider the requirement of power increase limits at the same time

for downlink inner loop power control. The value of PTPC(k) is determined according to

the following principle:

0)(TPC if

e_LimitPower_Rais)( and 1)(TPC if

e_LimitPower_Rais)( and 1)(TPC if

0)(

est

est

est

k

kk

kk

kP TPCsu m

TPCsu m

TPC

TPC

TPC

1

indow_Sizeveraging_WDL_Power_A

)()(k

ki

TPCsum iPk

(3.1-11)

Where, is the power adjustment step (TpcDlStep), and Power_Raise_Limit is 8dB,

and DL_power_averaging_window_size is 30 times the power adjustment. At present,

ZTE inner loop power control does not consider limit power increases.

For the algorithm of downlink inner loop power control, the transmit power is also

adjusted once for one or three timeslots, and the selection of this algorithm also depends

on the channel fading status. That is, algorithm 1 is for fast channel fading and algorithm

2 for slow channel fading. The reason for such a selection principle is similar to that of

uplink inner loop power control. At present, the ZTE RNC only supports the UE sending a

TPC command at each timeslot.

3.1.4.2 Downlink inner loop power control in compressed mode

The inner loop power control of the UE 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.

TPC



During the period when the compressed mode is adopted, the UTRAN adjusts the current

downlink transmit power P(k-1) [dB] of each timeslot except the downlink transmission

gap to a new power value P(k) [dB] based on the TPC command received at the number

k-1th timeslot and the following formula.

P(k) = P(k - 1) + PTPC(k) + PSIR(k) + Pbal(k) (3.1-12)

Where,

PTPC(k) is the kth time of the power adjustment value according to inner loop

power control.

PSIR(k) is the kth time of the power adjustment value used for the reason that in

compressed mode, the downlink SIRTarget changes as opposed to that in 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 approach a common reference power level.

Because of the existence of a transmission gap in uplink compressed frames, the uplink

TPC command may fail to be received. In this case, the Node B sets PTPC(k) as 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 adopted 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:

δP=max (ΔP1_compression,…, ΔPn_compression) + ΔP1_coding + ΔP2_coding

Where: n is the type of TTI length of all TrCHs multiplexed to a CCTrCH. ΔP1_coding

and ΔP2_coding are obtained from the uplink parameters, including DeltaSIR1,

DeltaSIR2, DeltaSIRafter1 and DeltaSIRafter2, which are informed by the upper level

and also according to the following relations:

If the current frame contains the start of the first transmission gap, then

ΔP1_coding = DeltaSIR1 (2.3dB).

If the current frame is next to the frame that contains the start of the first

transmission gap, then ΔP1_coding = DeltaSIRafter1 (0.3dB).

If the current frame contains the start of the second transmission gap, then

ΔP2_coding = DeltaSIR2 (0dB).

If the current frame is next to the frame that contains the start of the second

transmission gap, then ΔP2_coding = DeltaSIRafter2 (0dB).

In other cases, ΔP1_coding = 0 dB, ΔP2_coding = 0 dB.

ΔPi_compression is defined as follows:

If the compressed mode with half spectrum spread factor is adopted,

ΔPi_compression = 3 dB.

In other cases, ΔPi_compression = 0.

When several compressed modes are used at the same time, the δP of each compressed

mode is calculated separately. The δP adopted 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 allowed

maximum transmit power or lower than the allowed minimum transmit power.

ΔPi_compression is used to offset the influence of the high SIR needed by the rate

increase of the transmission bit in compressed mode.

3.1.5 Uplink Outer Loop Power Control of R99

Outer loop power control differs between the uplink and downlink directions. The

downlink outer loop power control is performed in the UE and it is unrelated to the RNC.

This section describes the uplink outer loop power control algorithm in the UTRAN only.

The principle is: The initial SIRTarget value (USrvDivPc.uLInitSIR) is determined upon

service access, and the quality information (such as CRCI, BER and BLER) is obtained

from the measurement report, the SIRTarget adjustment decision command is produced

based on the service quality. If adjustment is necessary, SIRTarget 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 approach to SIRTarget through inner loop power control. In this way, the service

quality will not fluctuate drastically in a changing radio environment.

There are two uplink OLPC algorithms for R99 named “CRC based OLPC algorithm” and

“BLER target based algorithm”. When the parameter OlPcAlg=0, the BLER target

algorithm is used, and when OlPcAlg=1, the CRC-based outer loop power control

algorithm is used.

3.1.5.1 CRC based OLPC

The CRC based OLPC algorithm adjusts the SIR target based on the number of errors

and total TBs. Some sub-algorithms are introduced in order to optimize the CRC-based

OLPC algorithm.

1 CRC-based outer loop power control algorithm

The principle of the CRC-based outer loop power control algorithm is: 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 (referred to as error block



tolerance counter).

Principle for SIRTarget increase: When the tolerance BLER period (USrvPc.blerAccpPeriod)

(with its unit being number of data blocks, instead of a time measurement unit) has not

expired yet, but the number of error blocks has already exceeded the error transport block

number threshold (USrvPc.errorThresh), increase SIRTarget (meanwhile, clear the error

block counter and error block tolerance counter 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 (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 as following formula:

SIRtargetUpStepSize= Minimum (USrvPc.ulSirTargUpStep + deltaStep1 + deltaStep2,

USrvPc.maxSirTargUpStep)

Where,

USrvPc.ulSirTargUpStep is configured in the OMMR, it is a basic step size for

increasing SIRTarget.

deltaStep1 is an additional increase step size when the SIRTarget increases are

caused by consecutive error TBs. If there are at least two consecutive error TBs

which cause SIRTarget increase, the deltaStep1 is SirUpAddStep. Else, 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

following SIRTarget increase has happened during the period indicated by

ValidTimTbCovPrd which is after the shield period, then the deltaStep2 for the

following SIRTarget increase should be calculated with the following formula:

deltaStep2=ErrTbNu mInCovPrd

ErrTbNumOutCovPrd* USrvPc.ulSirTargUpStep;

where,



i. ErrTbNumInCovPrd is the error TB number in the shield period after the last

SIRTarget increase.

ii. ErrTbNumOutCovPrd is the error TB number out the shield period after the last

SIRTarget increase.

Other conditions, the deltaStep2 is 0.

USrvPc.maxSirTargUpStep is the maximum SIRTarget increase step size.

Principle for SIRTarget decrease: When the error block tolerance counter is no less than

the tolerance BLER period (USrvPc.blerAccpPeriod), (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 the same if the received number of error

blocks equals the error transport block number threshold (USrvPc.errorThresh). After

SIRTarget is decreased, it is necessary to clear the error block counter and error block

tolerance counter to 0.

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

following.

i The initial step for decreasing SIRTarget is USrvPc.ulSirTargDnStep.

ii 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 would be the result of the last step for decreasing

SIRTarget adding 0.1dB. If the last step for decreasing SIRTarget had been the

biggest value (USrvPc.maxSirTargDnStep), the current step for decreasing

SIRTarget would come back to the initial value (USrvPc.ulSirTargDnStep).

iii When the last SIR target adjustment command is increase or keep, or the last

and current SIR target adjustment command both are decrease, but there is

error TB during the current SIR target adjustment period, then the current step

for decreasing SIRTarget would come back to the initial value

(USrvPc.ulSirTargDnStep).



To prevent that SIRTarget is increased or decreased too much, the maximum value

(USrvDivPc.uLMaxSIR) and minimum value (USrvDivPc.uLMinSIR) of SIRTarget is

configured in the OMMR. If the calculated SIRTarget is bigger than USrvDivPc.uLMaxSIR,

USrvDivPc.uLMaxSIR will be taken as a result. And if the calculated SIRTarget is smaller

than USrvDivPc.uLMinSIR, USrvDivPc.uLMinSIR will be taken as a result.

Note: The configuration of USrvPc.errorThresh, USrvPc.blerAccpPeriod,

USrvDivPc.uLInitSIR, USrvDivPc.uLMaxSIR and USrvDivPc.uLMinSIR is related to the

cell load scene (UUtranCellFDD.loadScene).

2 BER-based outer loop power control algorithm

In the CRC-based OLPC, SIRTarget can be decreased only when the TB number is no less

than USrvPc.blerAccpPeriod, so the SIRTarget is decreased slowly, it will affect the system

capacity. In order to increase the system capacity, the BER-based OLPC is introduced.

When the BER-based OLPC switch is on (USrvPc.ulOlPcQESwchSil =1), the OLPC of

the ZTE RNC can be based on the physical channel BER, but it only can decrease the

SIRTarget. Here, the uplink data frame contains the BER measurement result is in silent

mode. In silent mode, the uplink data frame can be send to the RNC only when the

number of DCH TB is not zero.

The principle of physical channel BER-based OLPC is as the following: in the valid time

window of the data block statistic (8s), if the consecutive physical channel BER are all

smaller than the physical channel BERtarget (USrvPc.qePhyBerTarSil), and the number of

the consecutive physical channel BER reaches the threshold USrvPc.qeCntThres, then

the SIR should be decreased. After SIRTarget is decreased, it is also necessary to clear all

the OLPC counters to 0.

Note: USrvPc.ulOlPcQESwchSil can be configured differently for different cells, when

soft handover happens, only if the BER-based OLPC switch of the macro diversity

related cells are all on (USrvPc.ulOlPcQESwchSil=1), the BER-based OLPC can be run.

3 Outer loop power control combination strategy for mixed services

The common outer loop power control algorithm described above is designed for one

transport channel. For mixed services (that is, several transport channels that are

multiplexed to one CCtrCH), some special treatment is needed for the outer loop power



control algorithm.

First, for BER-based OLPC, BER-based OLPC can be run only when all the BER-based

OLPC switches (USrvPc.ulOlPcQESwchSil) of the mixed services are on. The BER

target should be the minimum value of USrvPc.qePhyBerTarSil of all the services.

Second, the SIRTarget adjustment actions of different services should be combined

together. For mixed services (that is, several transport channels are multiplexed to one

CCtrCH), if any one service type fails to satisfy the service quality requirement, SIRTarget

is increased. SIRTarget is not decreased unless all services valid for statistics indicate to

decrease SIRTarget. Services invalid for statistics are excluded from the combination of

power control. Services invalid for statistics are those services that cannot serve as the

reference for SIRTarget adjustment because their data volume is not enough. If a service

does not have enough data volume, it means the total number of packets received in the

valid time window (8s) is smaller than the error block tolerance period for the service.

3.1.5.2 BLER Target based OLPC

RNC calculates single step adjustment quantity for every scheduling cycle based on

USrvPc.blerTarget and the number of total TBs and error TBs:

(1) USrvPc.blerTarget≤50%:

BLERtarget1Z

YZ1SirStepΔSIRtarget

(2) USrvPc.blerTarget>50%:

1

BLERtargetZ

YSirStepΔSIRtarget

Z and Y indicate the number of total TBs and error TBs in a scheduling cycle, SirStep is

the SIRTarget adjustment step indicated by USrvPc.ulSirStep.

The RNC will only update the SIRtarget when the single step adjustment quantity is equal

to or greater than 0.1dB,

For the sudden strong interference scenario, the SIRTarget is easy to be overregulated

according to the algorithm mentioned above. In view of this situation, a shield period is

introduced. Under the condition that the switch (ShieldPeriodSwch) is turned on, RNC

preserves the output adjustment quantity in a slide window, the length of which is



indicated by OutSirTimWinSize. When the adjustment quantity is equal to or greater than

OutSirThresh, the subsequent SIRTarget increase is shielded.

Combination strategy for mixed services:

For multi-services users, when more than one service meets the output conditions

simultaneously, the maximum adjustment quantity is used.

3.1.6 Downlink Outer Loop Power Control of R99

The downlink outer loop power control is performed in the UE. RNC provides

USrvPc.blerTarget to the UE.

USrvPc.blerTarget corresponding to the different downlink traffic is listed in the following

table.

Traffic USrvPc.blerTarget

DL CS 64kbps Conversational 0.1%

DL PS Conversational Video 0.1%

Other downlink services 1%

For F-DPCH, the TPC command error rate target (TpcErrTarget) should be provided,

which is used for adjusting the SIR target of F-DPCH.

3.1.7 Downlink Power Balancing

3.1.7.1 Algorithm Description

In the soft handover or macro diversity status, a UE can communicate with all cells in the

active set. With downlink inner loop power control, the UE sends the same TPC

command to the cells in the active set. But because each link is available with a different

transmission path, errors will be produced in the TPC command and some cells will

receive the wrong TPC command. As a result, some cells increase downlink

transmission power and some cells decrease downlink transmit power, hence the drifting

power effect. Power drifting is usually eliminated through the downlink power balancing

approach.



The purpose of downlink power balancing is to balance the downlink transmit power of

one or more radio links used by the Node B of the related RRC connection. 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 that several links are involved, power balancing can help overcome power

drifting.

A simple formula for calculating Pbal is as follows:

))(1( in itCPICHPrefbal PPPrP precision±0.5 dB (3.1-13)

Where,

Pref is a reference power, which is equal to DL Reference Power.

PP-CPICH is the transmit power of the primary CPICH

(UUtranCellFDD.primaryCpichPower).

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.

r is the adjustment convergence coefficient that ranges 0~1.

A simple method for calculating DL Reference Power is as follows:

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 domain of DPCH) periodically reported by the Node B using the following

formula:

3)( POTCPdBmPDPDCH

j (3.1-14)

Where,

jPDPDCH is the downlink transmit power of the j

th radio link;



PO3 is the power offset between the DL DPCH PILOT domain and the DPCH

data domain (DpchPO3);

The downlink reference power of the ith radio link is:

PowerCPICHPPdBPowerferDL DPDCH

jj __)(_Re_ (3.1-15)

Where, P_CPICH_POWER is P-CPICH power (UUtranCellFDD.primaryCpichPower).

Next, RNC takes the average value of the reference power for each radio link as the DL

Reference Power needed:

N

PowerferDL

PowerferDL

N

j

j

1

_Re_

_Re_ (3.1-16)

Where: N is the number of radio links used by the Node B.

Method to perform power balancing:

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 which contains the information of DL

Reference Power sent to the Node B.

The Node B uses this value to implement link balancing through the inner loop

power control algorithm.

Adjustment Type (AdjType):

AdjType is used to select whether to perform the downlink power balancing adjustment

and the adjustment type. Power Adjustment Type can take the value of “None” or “Common”.



When the value of AdjType is “None”, it means that the Node B does not need to balance

the DL power.

When the value of AdjType is “Common”, it means the Node B balances the DL power

but the balanced radio links use common reference power.

Adjustment Period:

The value of the adjustment period is 50 frames. It is a value determined through actual

tests.

Adjustment Ratio r (0.96):

Adjustment ratio is 0.96 by default. The smaller the value of the adjustment ratio is, the

quicker the offsets of transmit power of base stations are converged to be as the power

offset as opposed to the common pilot channel of cells. However, as the adjustment

volume of power balancing is limited by the maximum adjustment step, the value of

convergence is also limited.

Max Adjustment Step (1~10 slots):

Max adjustment step defines a time period, in terms of the number of slots; its value is 8

slots, in which the Node B can make power adjustment for balancing purpose by no more

than 1dB.

Note: When the ZTE RNC is DRNC, whether to use DL POWER CONTROL REQUEST

information in the Iur interface to control power balancing is determined by the switch

IurPwrCtlReqSwch. When IurPwrCtlReqSwch = 1, DRNC sends the DL POWER

CONTROL REQUEST information to the Node B which is the same as the DL POWER

CONTROL REQUEST information send by SRNC through the Iur interface. When

IurPwrCtlReqSwch = 0, DRNC would discard the DL POWER CONTROL REQUEST

information sent by SRNC through the Iur interface.

3.1.7.2 Related measurement

The type of the Node B dedicated measurement is indicated by the parameter

dedMeasType, and the report type of the measurement result is indicated by the

parameter UNbDedMeas.rptType. Each set of the Node Bs dedicated measurement



parameters configuration has a number indicated by the parameter nbDMCfgNo, and

nbDMCfgNote and indicates the configuration is used in which function. The Node B

dedicated measurement for DL power balancing has the following features.

The measurement of TCP (transmit code power) is reported periodically. The “report

periodicity value” is UNbDedMeas.rptPrd, and the “choice report periodicity scale”

is UNbDedMeas.rptPrdUnit.

The measurement of TCP gets started after the UE changes status from macro

diversity to non-macro diversity, and is terminated after the UE changes status from

non-macro diversity to macro diversity.

The Node B dedicated measurement filter coefficient is

UNbDedMeas.measFilterCoeff.

3.1.8 User Differentiated Power Control

When the UEs are using the same service, user differentiated power control can grant

different basic priority UEs different maximum allowed uplink or downlink DPCH

transmission power levels. This is achieved by using a method that adds the maximum

allowed uplink or downlink DPCH transmission power based on service and a power

offset based on basic priority.

The actual maximum allowed downlink DPCH transmission power is:

MaxDlDpchPwrBP = USrvDivPc.maxDlDpchPwr + DL_Power_offset;

Where, DL_Power_offset is the power offset of the maximum downlink DPCH

transmission power level, it is determined by the basic priority of the service. For a

service, after the basic priority is established, the DL_Power_offset can be obtained

from the array of MaxDlDpchPO[MAX_BP]. The element of the

MaxDlDpchPO[MAX_BP] array is configured based on the basic priority. The higher

the basic priority of the user, the bigger the power offset of the maximum downlink

DPCH transmission power.

The actual maximum allowed uplink DPCH transmission power is:

MaxUlDpchPwrBP = USrvDivPc.maxUlDpchPwr + UL_Power_offset;



Where, UL_Power_offset is the power offset of the maximum uplink DPCH

transmission power level, it is determined by the basic priority of the service. For a

service, after the basic priority is established, the UL_Power_offset can be obtained

from the array of MaxUlDpchPO[MAX_BP]. The element of the

MaxUlDpchPO[MAX_BP] array is configured based on the basic priority. The higher

the basic priority of the user, the bigger the power offset of the maximum uplink

DPCH transmission power.

3.1.9 IMEI based Power Control

A well-known brand mobile phone’s antenna receiving capability degrades greatly under

a certain scenario due to an antenna design defect, resulting in a higher call drop rate.

The ZTE RAN is able to identify this kind of UE and compensate on power to reduce the

call drop rate. For some UEs whose antenna receiving sensitivity is high due to the

delicate design, the ZTE RAN can also reduce their power to save the radio resources.

The UE is identified based on IMEI, refers to “ZTE UMTS User Equipment Fault Aversion

Feature Guide”.

3.1.9.1 Algorithm Description

When the function switch is on (ImeiPcFunSwitch = 1), for the UE whose IMEI is

identified, and the IMEI based power control switch of this IMEI is on (ImeiPcSwitch = 1),

the related power control parameters are determined as the following:

1. The maximum SIR target and the minimum SIR target will add an offset

(ImeiULMaxSirOffset, ImeiULMinSirOffset) respectively. At the same time the

restriction between the maximum SIR target, the minimum SIR target and the initial

SIR target will be ensured, which is the minimum SIR target <= initial SIR target <=

the maximum SIR target. The result is as the following:

i. The initial SIR target is USrvDivPc.uLInitSIR. (Note: when the switch of the

SIR target rapid convergence is on, refer to the section 3.7 “SIR Target

Rapid Convergence”, the initial SIR target is USrvDivPc.initSirAdd +

USrvDivPc.initBlerSIR.)

ii. The maximum SIR target is maximum (Initial SIR target,



USrvDivPc.uLMaxSIR + ImeiULMaxSirOffset).

iii. The minimum SIR target is minimum (Initial SIR target,

USrvDivPc.uLMinSIR + ImeiULMinSirOffset).

Notes: When the IMEI utility switch for considering load when configuring power

control parameters is on (ImeiUtilityExt:bit0 = 1) , if the cell uplink load is at a high

level, and the value of ImeiULMaxSirOffset (or ImeiULMinSirOffset) is positive, then

the maximum SIR target (or the minimum SIR target ) will not add this offset.

2. The maximum DL power and the minimum DL power will add an offset

(ImeiMaxDlDpchPO, ImeiMinDlDpchPO) respectively. After adding this offset (and

the maximum DL power needs to add the basic priority based power offset), the

restriction between the maximum DL power and the minimum DL power will be

ensured, which is the minimum DL power <= maximum DL power. The result is as

the following:

i. The minimum DL power is USrvDivPc.minDlDpchPwr +ImeiMinDlDpchPO.

ii. The maximum DL power is maximum (USrvDivPc.maxDlDpchPwr +

MaxDlDpchPO+ ImeiMaxDlDpchPO, the minimum DL power). Where,

MaxDlDpchPO is related to the basic priority of the user, refer to the section

3.1.8 “User Differentiated Power Control”.

Notes: When the IMEI utility switch for considering load when configuring power

control parameters is on (ImeiUtilityExt:bit0 = 1) , if the cell downlink load is at a high

level, and the value of ImeiMinDlDpchPO (or ImeiMaxDlDpchPO) is positive, then

the minimum DL power (or the maximum DL power ) will not add this offset.

The uplink and downlink load state of the cell is referred to “ZTE UMTS Load Adaptive

Power Control Feature Guide”. Note: When the load based BLER switch is on

(BlerLoadSwitch=1), the load is the real load, otherwise, the default load level

(DefaultLoadLevel) is used.

3.2 HSDPA Power Control

The HSDPA-related power control involves two aspects: (1) RNC performs total power



allocation for HSDPA; and (2) power calculation of physical channels, including

HS-PDSCH, HS-SCCH and HS-DPCCH. These physical channels are useful only when

subscribers are allocated with HS-DSCH resources and data transmission occurs.

The power of HS-SCCH can be determined using either of the following two methods:

The power of HS-SCCH is determined with the HS-SCCH power offset provided by

the RNC.

The Node B calculates the power of HS-SCCH.

The second method is used by ZTE, and in this way, HS-SCCH power is calculated by

the Node B, the Method to determine the HS-SCCH power is not described in this article.

3.2.1 Methods to Determine the Power Offsets of HS-DPCCH-related

Domains

HS-DPCCH carries the ACK, NACK and CQI information, its power control works in the

way as that of UL DPCCH except that the power gain factor βhs is different.

In normal mode, βhs is inferred by the UE according to ∆ACK, ∆NACK and ∆CQI using the

following formula:

2010DPCCHHS

chs (3.2-1)

Where: βc is the power gain factor of UL DPCCH.

When HS-DPCCH is activated, each slot of the HS-DPCCH, ∆HS-DPCCH is set with the

following methods:

When HS-DPCCH carries the HARQ ACK information: If ACK = 1, then

∆HS-DPCCH = ∆ACK; if ACK = 0, then ∆HS-DPCCH = ∆NACK.

When HS-DPCCH carries the CQI information: ∆HS-DPCCH = ∆CQI.

The value range of ∆ACK, ∆NACK and ∆CQI is from 0 to 9. If Ahs =

2010DPCCHHS

, then the relation

between ∆ACK, ∆NACK, ∆CQI and Ahs is shown in Table 3-6.



Table 3-6 Quantified Amplitude Relation between ∆ACK, ∆NACK, ∆CQI and Ahs

Signaled values for ∆ ACK, ∆ACK and

∆CQI

Quantized amplitude ratios

Ahs βhs/βc

9 38/15

8 30/15

7 24/15

6 19/15

5 15/15

4 12/15

3 9/15

2 8/15

1 6/15

0 5/15

Meanwhile, as the power offset of HS-DPCCH is based on DPCCH, DPCCH has soft

handover gain in the macro diversity status and HS-DPCCH exists only in the serving cell.

When DPCCH decreases the transmit power due to the soft handover gain, the single

link configuration will affect the correct reception probability of HS-DPCCH. That is,

configurations should be set differently between the cases of macro diversity and

non-macro diversity. ∆ACK takes the values of UHspa.ackPwrOffset and InterAckPwrOfst

respectively in non-macro diversity and macro-diversity cases. ∆NACK takes the values of

UHspa.nackPwrOffset and InterNackPwrOfst respectively in non-macro diversity and

macro-diversity cases. ∆CQI takes the values of UHspa.cqiPwrOffset and InterCqiPwrOfst

respectively in non-macro diversity and macro-diversity cases.

In addition, RNC needs to configure the CQI feedback cycle (UHspa.cqiCycle) and times

of repeated CQI transmission, that is, the CQI repetition factor (UHspa.cqiRepFactor) so

that CQI feedback can be performed. RNC should also configure the ACK-NACK

repetition factor (UHspa.anackRepFactor) so that ACK-NACK feedback can be

performed.

The parameters described above are obtained and optimized through tests according to

the performance indexes for certain reception success probability.



3.2.2 Method to Determine HS-PDSCH Measurement Power Offset

HS-PDSCH uses the adaptive modulation coding (AMC) scheme and HARQ, instead of

closed loop power control, to improve link performance. For the physical channel of the

HS-PDSCH, RNC should configure the measurement power offset for the Node B and

the UE.

When measuring CQI, the UE supposes the power of the HS-PDSCH is:

CPICHHSPDSCH PP in dB (3.2--2)

Where,

Γ is the measurement power offset (MeasPwrOffset) of the RRC signaling

configuration.

Δ is obtained by the UE through querying the table depending on the UE

category. The UE category and the relationship between the UE category and Δ

is described in table 7a, 7A, 7B, 7C, 7D, 7E, 7F, 7G, 7H, 7I and 7J of 3GPP TS

25.214 protocol.

PCPICH is the receiving power of the pilot channel.

PHSPDSCH is the total receiving power evenly distributed on the HS-PDSCHs that

perform CQI measurement and evaluation.

Based on the above mentioned receivable power and the benchmark of BLER =10% of

the quality of received data, the UE determines the CQI and reports it to the Node B.

Based on the relation between the UE-reported CQI and the measurement power offset,

the Node B determines the power that can be allocated to the UE and transmittable

number of bits.

The measurement power offset (MeasPwrOffset) is configured and updated as the

following:

After the UE is admitted in the HS-DSCH channel, the measurement power

offset is configured according to the UE’s actual use of 64QAM, MIMO and



DC-HSDPA in the cell. The value of the measurement power offset is obtained

in the following ways: First, obtain the used HS-PDSCH measurement power

offset profile (refUMPOProfile) from the configuration item UUtranCellFDD.

Next, obtain the instance of the object UMPOProfile in the used HS-PDSCH

measurement power offset profile UMPOProfile, and then obtain the

sub-object UMPO. Finally, obtain the measurement power offset indexed by

app64QamInd, appMimoInd, and appDcHsdpaInd in the sub-object UMPO.

When the serving cell is changed, the measurement power offset should be

determined according to the new serving cell. If the value of the measurement

power offset is changed, the measurement power offset should be

reconfigured.

When the serving cell is not changed but the actual use of 64QAM, MIMO and

DC-HSDPA is changed, the measurement power offset should be determined

according to the UE’s actual use of 64QAM, MIMO and DC-HSDPA in the cell.

If the value of the measurement power offset is changed, the measurement

power offset should be reconfigured.

3.2.3 HSDPA Power Control in Compressed Mode

In compressed βhs used by uplink HS-DPCCH and the

formula is as follows:

Npilot

Cpilot

jCchsN

NDPCCHHS

,

,20

,, 10

Where,

Npilot,C is the number of bits occupied by the pilot domain of UL DPCCH in

compressed mode.

Npilot,N is the number of bits occupied by the pilot domain of UL DPCCH in

normal mode.



Frame format in compressed mode is corresponding to that in normal mode.

Once the frame format in normal mode is determined, the frame format once

the compressed mode has started is also determined.

When at least one DPDCH is configured, jCc ,, is the gain factor of the uplink

dedicated control physical channel of R99 for a specific TFC in compressed

mode. For calculation of jCc ,,, refer to the uplink open loop power control of

R99 in compressed mode as described in Section 3.1.1.3. If no DPDCH is

configured, jCc ,, can be configured as described in Section 5.1.2.5C of

3GPP TS 25.214, that is, jCc ,,=1.

3.2.4 Total Power Allocation of HSPA

The total power occupied by HSPA can be assigned by the RNC, and the Node B is

notified of the value with the HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH

Total Power message of PHYSICAL SHARED CHANNEL RECONFIGURATION

REQUEST. Hence when power is being allocated, the Node B will ensure that the power

used by HSPA (HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power)

will not exceed the configured value of the signal cell. The RNC can configure this power

value in a dynamic way. The RNC may also leave the HSPA power not specified so that

the Node B will allocate the power freely according to the actual availability status of the

resource.

The system determines which allocation method applies according to the parameter

HsdschTotPwrMeth configured in OMMR. The two methods, dynamic allocation by the

RNC and dynamic allocation by the Node B, are described in the following.



Figure 3-1 The frame of HSPA power allocated

The allocated

power for cell

Based on the OMC

configured ,select the next step

Node B allocate the

power freely

RNC allocate the

power dynamically

3.2.4.1 Dynamic allocation by the RNC

Dynamic power allocation by the RNC refers to the process: (1) Initial HS-PDSCH,

HS-SCCH, E-AGCH, E-RGCH and E-HICH total power (HspaPwrRatio) are configured

in the OMMR according to the number of the HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH

and E-HICH physical channels configured for the cell. (2) During the system operation,

the software algorithm has the HSPA total power dynamically adjusted according to the

following triggering condition and principle. Figure 3-2 shows the strategy of the

adjustment:

Figure 3-2 Dynamic Power Adjustment for HSPA and DPCH

Power adjustment is described as follows (Note: The variables used in this section are

measured in percentages).

1 HSPA total power is adjusted dynamically along with the system’s all non-HSPA



power and power occupation ratio by HSPA users.

Because DPCH and HSPA users use the allocated power independently, rather

than the non-HSPA physical channel taking priority to use the power resource, the

condition for making a HSPA total power decrease decision can be set to:

i. The power occupied by non-HSPA power has reached a threshold as

compared to the power resource allocated to it.

When all non-HSPAPower ≥ NodeBSafeThr - HSPATotalPower, and the

HSPA total power is allowed to be decreased (HSPATotalPower > max

(MinHspaPwrRto,

io rityPr HS-DSCH Required Power)), some power allocated

to the HSPA physical channel can be given to be used by the non-HSPA

physical channel. (The NodeBSafeThr is equivalent to CellMaxPower -

NoHsHysA in the preceding diagram).

ii. If there are HSPA users, the minimum total power of HSPA is subject to Max

(MinHspaPwrRto,

io rityPr HS-DSCH Required Power); otherwise the minimum

total power of HSPA is not subject to Max (MinHspaPwrRto,

io rityPr HS-DSCH

Required Power).

When (NodeBSafeThr-3%) - allnonHSPAPower > Max (MinHspaPwrRto,

io rityPr HS-DSCH Required Power), the adjustment quota is: AdjustP =

HSPATotalPower - ((NodeBSafeThr-3%) - allnonHSPAPower).

(Where, (NodeBSafeThr-3%) is equivalent to CellMaxPower - NoHsHysB is

the preceding diagram.)

Otherwise, HSPATotalPower = Max (MinHspaPwrRto,

io rityPr HS-DSCH

Required Power).

Another important purpose for HSPA is to make full use of cell power, that is, when

the non-HSPA physical channel needs little power, the power of HSPA can be

increased as much as possible to improve the system’s throughput. Method to



increase HSPA total power: when allnon-HSPAPower < (NodeBSafeThr-3%) -

HSPATotalPower.

If there are HSPA users, some power of the non-HSPA physical channel can

be given to the HSPA physical channel as the non-HSPA physical channel

does not need all the power allocated to it. The quota of adjustment is: AdjustP

= (NodeBSafeThr-3%) - allnon-HSPAPower - HSPATotalPower. If AdjustP < 0,

no adjustment is performed. After any adjustment, it should be guaranteed that

HSPATotalPower ≤ MaxHspaPwrRto.

If there is no HSPA user, no adjustment is necessary.

2 HSPA total power is dynamically adjusted according to a software algorithm when

HSPA resource congestion occurs. The probability of congestion-driven adjustment

can be decreased as much as possible if the first strategy is implemented (HSPA

total power is adjusted dynamically along with the system’s all non-HSPA power and

power occupation ratio by HSPA users).

When the power resources of HSPA users are limited, the dynamic adjustment of

HSPA power is triggered.

Now the HSPA total power is increased with the principle that the available

maximum power of a cell reaches the overload recovery threshold. The

adjustment quota AdjustP = (NodeBSafeThr-3%) - allnon-HSPAPower -

HSPATotalPower, but after the adjustment, it should be guaranteed that

HSPATotalPower ≤ MaxHspaPwrRto.

If the power occupation of the current non-HSPA physical channel no longer

allows the increase of HSPA total power and also HSPATotalPower <

MinHspaPwrRto, then make HSPATotalPower = MinHspaPwrRto. Otherwise

no more increase is allowed.

When the total HS-DSCH required power reported by the Node B is detected to

exceed HSPA total power configured by the RNC to the Node B, the HSPA total

power can be adjusted dynamically to guarantee the QoS of real-time services.

The adjustment principle is also that the available maximum power of a cell

reaches (NodeBSafeThr-3%). The adjustment quota AdjustP =



(NodeBSafeThr-3%) - allnon-HSPAPower - HSPATotalPower, but after the

adjustment, it should be guaranteed that HSPATotalPower ≤ MaxHspaPwrRto.

If the power occupation of the current non-HSPA physical channel no longer

allows the increase of HSPA total power, HSPA total power cannot be

increased. That is, no increase is allowed when AdjustP ≤ 0. However, it

should be guaranteed that HSPATotalPower ≥ MinHspaPwrRto.

3 When there is no HSPA user, HSPA total power can only be decreased (not

increased) along with the power change of non-HSPA.

3.2.4.2 Free allocation of the Node B

Free power allocation is determined by an algorithm of the Node B based on available

power, service priority and QoS. RNC should have the allowed available power of the

HSPA configured as 100%.

3.3 HSUPA Power Control

3.3.1 Method to Determine Uplink E-DPCCH/DPCCH Power Offset

The uplink E-DPCCH open loop power control of HSUPA is provided by setting a

reasonable E-DPCCH power offset relative to that of DPCCH.

The E-DPCCH power offset relative to that of DPCCH should satisfy the BER

requirement of E-DPCCH control signaling. The power offset value is obtained through

emulation or test and configured in OMMR (UHspa.edpcchPOTti2 or

UHspa.edpcchPOTti10, depending on different TTIs). According to 25.214, the gain

factor βec of E-DPCCH is calculated using the following formula in non-compressed mode:

eccec A (3.3-1)

Where,

βc is the gain factor of the uplink dedicated control physical channel of R99.

For the configuration details of βc, refer to Section 3.1.1.2.



Aec is obtained from the E-DPCCH power offset (∆E-DPCCH) that is configured at

the high level and then mapped in 0.

∆E-DPCCH can be configured for the UE through the radio bearer establishment message,

or configured again through the radio bearer re-configuration message. It is generally not

dynamically updated after being configured for the first time. Table 3-7 lists the relation

between Aec and ∆E-DPCCH.

Table 3-7 Quantified Amplitude Relation between Aec and ∆E-DPCCH

Signaled values for

∆E-DPCCH

Quantified amplitude ratios

Aec =βec/βc

8 30/15

7 24/15

6 19/15

5 15/15

4 12/15

3 9/15

2 8/15

1 6/15

0 5/15

The power of E-DPCCH is configured once and for all and does not need dynamic

adjustment, so it is relative simple. E-DPCCH can use different TTIs (2ms, 10ms) for

transmission. If the 10ms TTI is used, the content of the first 2ms timeslots is repeatedly

transmitted for four times to improve uplink reception performance. The power

configuration of this channel is similar to that of the downlink physical channel except

that different TTI applications should be differentiated.

3.3.2 Method to Determine Power Offset of Uplink E-DPDCH/DPCCH

3.3.2.1 Method to determine reference E-TFC and βed,ref

As many types of E-TFC exist in the TB SIZE of E-DCH, and RNC cannot notify the Node

B and the UE of the βed corresponding to each type of E-TFC, 3GPP specifies that RNC



notifies the UE and the Node B of a group of reference E-TFC and the corresponding

E-DPDCH power offset relative to DPCCH, to be used by the UE and the Node B to

calculate the power needed by other non-reference E-TFC.

RNC needs to determine which group of E-TFCs as the reference for other E-TFCs.

Principle for determining the reference E-TFC is as follows:

The E-TFC types that have the same combination feature of SF and number of code

channels are taken as a group before the position where both the physical channel and

SF turns transient is. The largest E-TFC is selected as the reference. The E-DPDCH

power offset at the reference E-TFC point can be obtained and optimized through tests

while other values can be obtained through formula-based calculation. This is a practical

approach to the selection of reference E-TFC.

βed,ref is the reference gain factor of the reference E-TFC, and for each reference E-TFC,

the βed,ref can be calculated using the following formula.

edcrefed A , (3.3-2)

Where,

βc is the gain factor of the uplink dedicated control physical channel of R99.

For the configuration details of βc, refer to Section 3.1.1.2.

Aed is obtained from the E-DPCCH power offset (∆E-DPCCH) that is configured at

the high level and then mapped in Table 3-8.

Table 3-8 Quantified Amplitude Relation between ∆E-DPDCH and Aed

Signaled values for

∆E-DPDCH


Aed

29 168/15

28 150/15

27 134/15

26 119/15

25 106/15



Signaled values for

∆E-DPDCH


Aed

24 95/15

23 84/15

22 75/15

21 67/15

20 60/15

19 53/15

18 47/15

17 42/15

16 38/15

15 34/15

14 30/15

13 27/15

12 24/15

11 21/15

10 19/15

9 17/15

8 15/15

7 13/15

6 12/15

5 11/15

4 9/15

3 8/15

2 7/15

1 6/15

0 5/15

Note:

The selection of reference E-TFC and corresponding PO values vary with different

TTIs and TB SIZE tables.



For 2ms E-TTI and Table0, E-DPDCH puncturing limit is 56%, set of reference

E-TFCIs is [1, 26, 39, 45, 51, 70, 79, 122], and the power offset of reference

E-TFCIs is [9, 12, 13, 13, 13, 12, 13, 16].

For 2ms E-TTI and Table1, E-DPDCH puncturing limit is 56%, set of reference

E-TFCIs is [1, 3, 16, 36, 62], and the power offset of reference E-TFCIs is [7,

10, 12, 12, 13].

For 10ms E-TTI and Table0, E-DPDCH puncturing limit is 64%, set of

reference E-TFCIs is [1, 12, 48, 60, 77, 88], and the power offset of reference

E-TFCIs is [3, 6, 12, 13, 15, 16].

For 10ms E-TTI and Table1, E-DPDCH puncturing limit is 64%, set of

reference E-TFCIs is [1, 5, 19, 41, 55, 71, 98], and the power offset of

reference E-TFCIs is [3, 6, 11, 13, 15, 13, 14].

Ways for other E-TFCs to select reference E-TFCs are:

Make E-TFCIref,m indicate the E-TFCI of the number mth reference E-TFC. Here

m=1,2,…,M, where M is the number of reference E-TFCs for signaling notification

and E-TFCIref,1 < E-TFCIref,2 < … < E-TFCIref,M. Make E-TFCIj indicate the E-TFCI of

number jth E-TFC. For the number j

th E-TFC:

If E-TFCIj >= E-TFCIref,M, then the reference E-TFC is the mth reference E-TFC.

If E-TFCIj < E-TFCIref,1, then the reference E-TFC is the first reference E-TFC.

If E-TFCIref,1 <= E-TFCIj < E-TFCIref,M, then the reference E-TFC is the mth

reference E-TFC that satisfies E-TFCIref,m <= E-TFCIj < E-TFCIref,m+1.

3.3.2.2 Method to determine βed

The gain factor of E-DPDCH is defined as βed, which can have a different value for each

E-TFC and HARQ offset. With the reference E-TFC and corresponding power offset sent

by the RNC and the information related to the HARQ offset, the UE and the Node B can

calculate βed of other non-reference E-TFCs, and in turn the power of related E-DPDCHs.



Make Le,ref indicate the number of E-DPDCHs used by the reference E-TFC. Make Le,j

indicate the number of E-DPDCHs used by the number jth E-TFC. If SF2 is used, Le,ref

and Le,j are the equivalent numbers of physical channels of the supposed SF4. Make

Ke,ref indicate the number of data bits of the reference E-TFC. Make Ke,j indicate the

number of data bits of the number jth E-TFC. For the number j

th E-TFC, the gain factor

βed,j,harq of the related E-DPDCH can be calculated using the following formula.

(3.3-3)

Where: HARQ power offset ∆harq has the value configured by cell E-DCH HARQ power

offset FDD (USrvPc.edchHarqPOFdd). ∆harq is configured through the radio link

establishment request or radio link increase request, and re-configured through the radio

link re-configuration request.

The power of E-DPCCH is configured once and for all and does not need dynamic

adjustment. E-DPCCH can use different TTIs (2ms, 10ms) for transmission. If the 10ms

TTI is used, the reception performance is different and in cases where different TB SIZE

tables are used, the number of E-TFCIs and TB SIZE tables are also different. To

improve uplink reception performance, different TTI and TABLE applications should be

differentiated.

Note:

When MAC-e PDU does not include MAC-d PDU, the UE uses the configured

scheduling information power offset (UHspa.scheInfoPOTti2 or

UHspa.scheInfoPOTti10, depending on different TTIs) as the HARQ power offset to

calculate E-DPDCH transmit power.

In the case that MAC-e PDU is not decoded, the Node B uses the quantified value

(UHspa.edchRefPO) of the E-DCH reference power offset configured by the RNC to

estimate the E-DPDCH power of E-TFCI.

3.3.3 Method to determine Downlink E-AGCH/RGCH/HICH Power

Downlink open loop power control is to configure or re-configure the power offset of

physical channels such as E-AGCH, E-RGCH and E-HICH. The power offset is relative

20, ,

, , ,

, ,

10

harq

e ref e j

ed j harq ed ref

e j e ref

L K

L K



to the DL DPCH pilot domain. The Node B uses the offset and the inner loop power

control of DPCCH to dynamically adjust the transmit power of these physical channels.

The following factors should be considered when the power offset is being configured.

In the event of soft handover, the reception performance of E-RGCH and E-HICH is

better by a gain of about 7~14 dB than the E-AGCH without soft handover.

The required decoding error probability of the information carried by these channels

is usually 0.1~0.01. The power should be configured to a suitable value to meet the

error probability requirement so power configuration should never be too large or

too small.

E-AGCH transmission only in the serving cell, the E-AGCH performance requirement in

single RL condition and DCH macro diversity condition is the same, so when

EagchPOUptSwch = 0, E-AGCH power offset is EagchPOTti2 (2ms TTI) or

EagchPOTti10 (10ms TTI) for both single RL condition and DCH macro diversity

condition. But E-AGCH power offset is relative to the DPCH pilot domain, and DPCH

have macro diversity gain in the DCH macro diversity condition, so when

EagchPOUptSwch = 1, different E-AGCH power offset is configured for different

scenarios as the following:

Scenario TTI Single RL DCH Macro Diversity Status

2ms TTI EagchPOTti2 EagchPOTti2 + MacroDivGain

10ms TTI EagchPOTti10 EagchPOTti10 + MacroDivGain

Where, MacroDivGain is the macro diversity gain of downlink dedicated channel, its

value is 0dB.

E-HICH and E-RGCH can be transmitted in both the serving RL and non-serving RL.

According to the simulation result described in 3GPP 25.101, the performance

requirement of E-HICH and E-RGCH is different under different conditions, so the

E-HICH power offset and E-RGCH power offset should be configured respectively under

different conditions.

E-HICH power offset should be configured to distinguish E-DCH single RL status,

E-DCH serving RLS and E-DCH non-serving RLS in the E-DCH macro diversity status.

In each status, E-HICH can be transmitted using 3 consecutive slots (2ms TTI) or 12



consecutive slots (10ms TTI). So the E-HICH power offset is configured for different

scenarios as the following:

Scenario

TTI

E-DCH Single

RL

E-DCH Serving RLS E-DCH Non-serving

RLS

2ms TTI

(3 consecutive slots)

EhichPOTti2 EhichPOTti2 +

POEhichSerRls2

EhichPOTti2 +

POEhichNoSerRl2

10ms TTI

(12 consecutive slots)

EhichPOTti10 EhichPOTti10 +

POEhichSerRls10

EhichPOTti10 +

POEhichNoSerRl10

E-RGCH power offset should be configured for E-DCH single RL status, E-DCH serving

RLS, and E-DCH non-serving RLS in E-DCH macro diversity status respectively. Only in

E-DCH single RL status or E-DCH serving RLS in E-DCH macro diversity status,

E-RGCH can transmit relative scheduling grant using 3 consecutive slots (2ms TTI) or

12 consecutive slots (10ms TTI). For E-DCH non-serving RLS in E-DCH macro diversity

status, E-RGCH can only transmit relative scheduling grant using 15 consecutive slots

(10ms TTI). Therefore, E-RGCH power offset is configured according to the following

different scenarios:

Scenario

TTI

E-DCH Single

RL

E-DCH Serving RLS E-DCH Non-serving

RLS

2ms TTI ErgchPOTti2 ErgchPOTti2 +

POErgchSerRls2

ErgchPOTti10 +

POErgchNonSerRls 10ms TTI ErgchPOTti10 ErgchPOTti10 +

POErgchSerRls10

The principles for configuring E-AGCH power offset, E-RGCH power offset and E-HICH

power offset are described as follows.

The configuration of the power offsets in OMMR are related to different services.

When the control plane detects changes (establishment, addition, deletion and

modification) in the sub-services carried by DPCH, the new power offset is obtained

from the database according to the number of sub-services and then configured

again.

When TTIs change, the power offsets are configured again.

In the DCH macro diversity status, the E-AGCH power offset update is controlled by

the switch EagchPOUptSwch. When EagchPOUptSwch = 1, in order to save power



and guarantee the channel quality of E-AGCH at the same time, the E-AGCH power

offset is adjusted when changes of UE status (macro diversity and non-macro

diversity) is detected. For single RL condition, the E-AGCH Power Offset takes the

value as configured in OMMR, it is EagchPOTti2 (2ms TTI) or EagchPOTti10 (10ms

TTI). For the DCH macro diversity condition, it is EagchPOTti2 (2ms TTI) +

MacroDivGain or EagchPOTti2 (2ms TTI) + MacroDivGain, where, MacroDivGain is

the macro diversity gain of the downlink dedicated channel, its value is 0dB. When

EagchPOUptSwch = 0, in order to reduce the reconfiguration in the Iub interface,

E-AGCH Power Offset in single radio link condition or in DCH macro diversity

condition is the same, and it is EagchPOTti2 (2ms TTI) or EagchPOTti10 (10ms

TTI).

In the E-DCH macro diversity status, the E-HICH power offset and E-RGCH power

offset are updated. When the conversion between E-DCH macro diversity status

and E-DCH single RL status happened, or serving RLS changed, the E-HICH power

offset and E-RGCH power offset should be updated according to the RL situation

whether it is in E-DCH single RL status, or E-DCH serving RLS or E-DCH

non-serving RLS in E-DCH macro diversity status.

With DPCH carrier mixed services, the TTI used by the E-DCH should be

determined first. Then, the E-AGCH power offset, E-RGCH power offset and

E-HICH power offset (each power comes with several offsets) corresponding to the

TTI are obtained respectively according to the different services carried on the

DPCH. Finally, from several corresponding offsets, the minimum offset values Min

(E-AGCH Power Offset), Min (E-RGCH Power Offset) and Min (E-HICH Power

Offset) are selected as the power offsets of the E-AGCH, E-RGCH and E-HICH

respectively. (If both UE and serving cell supports 2ms TTI, the 10ms TTI is used as

long as one service uses 10ms TTI, otherwise the 2ms TTI is used )

Note:

i. The above description is based on downlink F-DPCH not being configured. This

time the E-AGCH power offset, E-RGCH power offset and E-HICH power offset are

relative to the power of the downlink DPCH pilot domain, and determine the value

based on the service over DPCH. However, if downlink F-DPCH is configured, the

E-AGCH power offset, E-RGCH power offset and E-HICH power offset are relative



to the power of the downlink F-DPCH TPC domain, and determine the value based

on the service type of F-DPCH (USrvPc.srvType=7).

ii. The configuration of EagchPOTti2, EagchPOTti10, ErgchPOTti2, ErgchPOTti10,

EhichPOTti2 and EhichPOTti10is related with the cell load scenario

(UUtranCellFDD.loadScene).

3.3.4 HSUPA Power Control in Compressed Mode

During the compressed frame period, the gain factor βec of the E-DPCCH when E-DCH

TTI is 2ms can be calculated using the following formula.

Npilo t

Cp ilo t

jCcecN

NDPCCHE

,

,2 0

,, 10

Where,

When at least one DPDCH is configured, jCc ,, is the gain factor of the uplink

dedicated control physical channel of R99 for a specific TFC in compressed mode. For the

calculation of jCc ,,, refer to the uplink open loop power control of R99 in compressed

mode as described in Section 3.1.1.3. If no DPDCH is configured, jCc ,, can be

configured as described in Section 5.1.2.5C of 3GPP TS 25.214, that is, jCc ,,=1.

Npilot,C is the number of pilot bits per slot on the DPCCH in the compressed

frame.

Npilot,N is the number of pilot bits per slot on the DPCCH in the non-compressed

frame.

Nslots,C is the number of non DTX slots in the compressed frame.

During the compressed frame period, the gain factor βec of E-DPCCH when E-DCH TTI is

10ms can be calculated using the following formula.



Npilo tCslo ts

Cp ilo t

jCcecNN

NDPCCHE

,,

,2 0

,,

1510

Where, Nslots,C is the number of non DTX slots in the compressed frame.

3.3.5 HSUPA Uplink Outer Loop Power Control

After the introduction of E-DCH, uplink outer loop power control is still needed in some

cases although RNC has configured the power offset for the E-DPDCH. For example,

although the current outer loop power control is stable, and the SIR is basically

converged to SIRtarget through inner loop power control, but the user plane of the Node B

still sends a HARQ failure indication to the RNC through data frames because of the

unreasonable PO or unreasonable maximum retransmission times. In this case, the

failure indication and the number of HARQ retransmissions (NHR) can be used to trigger

uplink outer loop power control to guarantee the QoS of E-DCH. The outer loop power

control algorithm after the introduction of E-DCH will affect the current outer loop power

control algorithm to some extent and hence coupling treatment is necessary.

There are two uplink OLPC algorithms for HSUPA named “NHR-based outer loop power

control algorithm” and “NHR target based outer loop power control algorithm”. When the

parameter OlPcAlg=0, NHR based outer loop power control algorithm is used, and when

OlPcAlg=1, the NHR target based outer loop power control algorithm is used.

3.3.5.1 NHR based HSUPA OLPC

1 In the ZTE RNC, HSUPA OLPC is based on NHR and HARQ failure indication.

When the number of HARQ failure indications is larger than the threshold

(USrvPc.thrHarqFailTti2 or USrvPc.thrHarqFailTti10), the SIRtarget should be increased.

At the same time, the SIRtarget can be increased or decreased based on NHR.

The principle of SIRtarget adjustment based on NHR is as the following: The service

quality is evaluated on the basis of the NHR carried by the FP frame transferred by the

Node B to RNC. The greater the NHR is, the poorer the quality of the channel is and

hence it is required to increase SIRtarget for higher transmit power, otherwise decrease

SIRtarget for lower transmit power. Steps for making the decision are:



Set as the retransmission times carried by each FP. is the number ith FP

frame ( =1… , is the maximum number of FPs). When the HARQ failure indication

is received, the NHR of the data block transmission is converted to an approximate value.

The formula for converting the HARQ failure indication to an NHR is as follows.

NHR= 3 * MaxRetransEdch;

Where, MaxRetransEdch is the maximum number of retransmissions for E-DCH.

To better reflect the channel quality, the average NHR value during a statistical period is

usually taken as the basis for the decision. The average NHR (average retransmission

times of each FP frame) during a statistical period is defined as NumReTransDiffAve=

.

Once outer loop power control is started for a service, the number of received FP frames

and NHR are counted within the valid statistical time window of the NHR (1s for 2ms TTI,

and 8s for 10ms TTI). The threshold of the sample number to adjust SIRtarget upward

(USrvPc.upThrSampNumTti10 for 10ms TTI, or USrvPc.upThrSampNumTti2 and the

threshold of sample number to adjust SIRtarget downward (USrvPc.dwThrSampNumTti10

for 10ms TTI, or USrvPc.dwThrSampNumTti2 for 2ms TTI) are respectively configured.

When the received number of FP frames reaches the minimum number of FP frames that

allows SIRtarget adjustment, compare the average NHR (NumReTransDiffAve) within the

statistical period with the NHR threshold for SIRtarget increase(USrvPc.nhrThrUpTti10 for

10ms TTI, or USrvPc.nhrThrUpTti2 for 2ms TTI), and the NHR threshold for SIRtarget

decrease(USrvPc.nhrThrDownTti10 for 10ms TTI, or USrvPc.nhrThrDownTti2 for 2ms

TTI) respectively, and then judge whether to adjust SIRtarget, and how to adjust it.

2 The following describes the details of HSUPA OLPC for a single service:

When: statistical time ≤ NHR valid statistical time window,

SIRtarget increase :

If the number of HARQ failures ≥ the threshold of the HARQ failure number

to increase the SIRtarget (USrvPc.thrHarqFailTti2 or USrvPc.thrHarqFailTti10),

iNHR ii I I

1

/I

i

i

NHR I



increase SIRtarget by one adjustment step. The increase step = basic step (that

is, USrvPc.ulSirTargUpStep of R99);

If the counted number of FP frames ≥ the threshold of the FP number to adjust

SIRtarget upward (USrvPc.upThrSampNumTti10 for 10ms TTI, or

USrvPc.upThrSampNumTti2, and NumReTransDiffAve > the NHR threshold

for SIRtarget increase (USrvPc.nhrThrUpTti10 for 10ms TTI, or

USrvPc.nhrThrUpTti2 for 2ms TTI), increase SIRtarget by one adjustment step.

The increase step = basic step (that is, USrvPc.ulSirTargUpStep of R99);

SIRtarget decrease :

If the counted number of FP frames ≥ the threshold of the FP number to adjust

SIRtarget downward (USrvPc.dwThrSampNumTti10 for 10ms TTI, or

USrvPc.dwThrSampNumTti2 for 2ms TTI), and NumReTransDiffAve < the

NHR threshold for SIRtarget decrease (USrvPc.nhrThrDownTti10 for 10ms TTI,

or USrvPc.nhrThrDownTti2 for 2ms TTI), decrease SIRtarget by one adjustment

step. The decrease step is determined in the same way as described in the

section 3.1.5.1 “CRC based OLPC Algorithm”, and the difference is the error

TB does not need to be considered when USrvPc.swchAdaptiveStep=1.

In other case, SIRtarget remains unchanged.

When: statistical time ≥ NHR valid statistical time window,

Increase or decrease SIRtarget according to the principles described above.

If the counted number of FP frames < the threshold of the FP number to adjust

SIRtarget, which is Minimum (USrvPc.upThrSampNumTti10,

USrvPc.dwThrSampNumTti10) for 10ms TTI or Minimum

(USrvPc.upThrSampNumTti2, USrvPc.dwThrSampNumTti2) for 2ms TTI, this

indicates the data volume of the service is quite small and the counted NHR is

not enough to serve as the basis for making a SIRtarget adjustment decision.

Now the channel is in a status of invalid NHR count.

For 10ms TTI, If Minimum (USrvPc.upThrSampNumTti10,

USrvPc.dwThrSampNumTti10) < the counted number of FP frames <

Minimum (USrvPc.upThrSampNumTti10, USrvPc.dwThrSampNumTti10), and



NumReTransDiffAve < Minimum (USrvPc.nhrThrUpTti10,

USrvPc.nhrThrDownTti10), this indicates the data volume of the service is

relatively small and NHR is also small, so this time, the channel is also in a

status of invalid NHR count.

For 2ms TTI, If Minimum (USrvPc.upThrSampNumTti2,

USrvPc.dwThrSampNumTti2) < the counted number of FP frames < Minimum

(USrvPc.upThrSampNumTti2, USrvPc.dwThrSampNumTti2), and

NumReTransDiffAve < Minimum (USrvPc.nhrThrUpTti2,

USrvPc.nhrThrDownTti2), this indicates the data volume of the service is

relatively small and NHR is also small, so this time, the channel is also in a

status of invalid NHR count.

In other case, SIRtarget remains unchanged.

When the time is more than the NHR valid statistical time window after service setup, the

schematic diagram of “SIRtarget increase”, “SIRtarget decrease”, “SIRtarget keep” and “NHR

invalid” states as the following:

Figure 3-3 Schematic Diagram of “SIRtarget increase”, “SIRtarget decrease”, “SIRtarget keep”

and “NHR invalid” based on NHR statistical

Threshold of Sample

Number to Adjust SIR

Target Downward

Threshold of Sample

Number to Adjust SIR

Target Upward

NHR Threshold to

Adjust SIR Target

Downward

NHR Threshold to

Adjust SIR Target

Upward

SIRtarget keep SIRtarget keep

SIRtarget decrease

NHR invalid

FP number

SIRtarget increase

Average NHR

SIRtarget increase

NHR invalid

NHR invalid NHR invalid

Note:

When the statistical time reaches the NHR valid statistical time window, and if

SIRtarget is not adjusted, then the slide window statistics are started. That is, an



outer loop power control decision is made whenever the slide window slides

for one step. To reflect the channel quality in due time, the slide step is usually

short. It is 20ms by ZTE RNC. Figure 3-4 shows a schematic diagram of the

slide window statistics:

Figure 3-4 Schematic Diagram of Slide Window Statistics

The (i)th valid time window

The (i+1)th valid time window

The (i+2)th valid time window

Every time after making a decision to adjust SIRtarget, the number of FP frames,

NHR statistics and the number of HARQ failure should be cleared to 0 and

new statistics are generated again.

If the counted number of FP frames ≥ Maximum

(USrvPc.dwThrSampNumTti10, USrvPc.upThrSampNumTti10) for 10ms TTI,

or the counted number of FP frames ≥ Maximum (USrvPc.upThrSampNumTti2,

USrvPc.dwThrSampNumTti2) for 2ms TTI, the number of FP frames, NHR

statistics and the number of HARQ failure also need to be cleared to 0 and

generate new statistics again.

3 SIRtarget adjustment in the case of concurrent services:

SIRtarget is increased as long as one service triggers it to be increased.

SIRtarget is not decreased unless all services with valid NHR statistics indicate

to decrease SIRtarget. Services with invalid NHR statistics are excluded from

the combination of power control.

Some services need to decrease SIRtarget while some others need SIRtarget to

remain the same, in this way SIRtarget is not adjusted to guarantee QoS of all

services.



3.3.5.2 NHR Target based HSUPA OLPC

RNC calculates the single step adjustment quantity for every scheduling cycle:

(1) fpTargError≤50%:

NHR>USrvPc.targetRetranNum,or HarqFail is detected:

SirStepΔSIRtarget

NHR≤USrvPc.targetRetranNum:

1rfpTargErro

1

1SirStepΔSIRtarget

(2) fpTargError>50%:

NHR>USrvPc.targetRetranNum,or HarqFail is detected:

1

rfpTargErro

1SirStepΔSIRtarget

NHR≤USrvPc.targetRetranNum:

SirStepΔSIRtarget

NHR indicates the number of HARQ retransmissions. USrvPc.targetRetranNum

indicates the target number of HARQ retransmissions. SirStep means the adjustment

step indicated by USrvPc.ulSirStepTti10 for 10ms ETTI and USrvPc.ulSirStepTti2 for

2ms ETTI. fpTargError means the target percentage of frames that have a number of

HARQ retransmissions larger than USrvPc.targetRetranNum. fpTargError is indicated by

USrvPc.fpTargErrorTti2 for 2ms ETTI and USrvPc.fpTargErrorTti10 for 10ms ETTI.

The RNC will only update the SIRtarget when the single step adjustment quantity is equal

or greater than 0.1dB.

Combination strategy for mixed services:



For the multi-services user, when more than one service meets the output condition

simultaneously, the maximum adjustment quantity is adopted.

3.3.5.3 Adjust HSUPA OLPC parameters adaptively according to the cell uplink

load.

Most of the HSUPA OLPC parameters and E-DCH HARQ Power Offset are cell load and

user priority related, including USrvPc.thrHarqFailTti2, USrvPc.thrHarqFailTti10,

USrvPc.nhrThrUpTti10, USrvPc.nhrThrDownTti10, USrvPc.nhrThrUpTti2,

USrvPc.nhrThrDownTti2, USrvPc.upThrSampNumTti10, USrvPc.dwThrSampNumTti10,

USrvPc.upThrSampNumTti2, USrvPc.dwThrSampNumTti2, USrvPc.targetRetranNum,

USrvPc.ulSirStepTti2, USrvPc.ulSirStepTti10, USrvPc.fpTargErrorTti2,

USrvPc.fpTargErrorTti10, USrvPc.edchHarqPOFdd, these parameters are designed as

9-element arrays, each element corresponding to a cell load and user priority condition.

When the E-DCH service is setup or E-DCH MAC-d flow reconfiguration, the parameter

value is obtained based on the cell load and the user priority (ARP), details refer to

“ZTE UMTS Load Adaptive Power Control Feature Guide”. And when the cell load level

is changed, these HSUPA OLPC parameters would be adjusted adaptively, in this way

the average HARQ retransmission number will be adjusted adaptively, it can improve the

system capacity.

3.3.5.4 Coupling of HSUPA and R99 outer loop power control

3.3.5.4.1 Coupling of the NHR based HSUPA algorithm and CRC based R99 algorithm

As the outer loop power control event algorithm of E-DCH introduced, it may affect the

current outer loop power control algorithm in some cases. For example, at some TTI, the

decisions of outer loop power control between the HSUPA and R99 are different. In this

case, a final decision should be made by the RNC.

The following table shows the coupling result of outer loop adjustment of the DCH and

E-DCH.



Table 3-9 Combination of Outer Loop Adjustment of DCH and E-DCH

E-DCH DCH State Combination Result

↑ ↑ 1 ↑

↑ ↓ 2 ↑

↓ ↑ 3 ↑

↑ - 4 ↑

- ↑ 5 ↑

↓ - 6 -

- ↓ 7 -

- - 8 -

↓ ↓ 9 ↓

↑ × 10 ↑

↓ × 11 ↓

× ↑ 12 ↑

× ↓ 13 ↓

- × 14 -

× - 15 -

× × 16 × (invalid statistics, no adjustment)

In the above table, ↑ indicates increase, ↓ for decrease, - for no adjustment (remain

unchanged), × for invalid statistics.

The coupling function is implemented using the following principle:

Increase the SIRtarget as long as either DCH or E-DCH meets the condition for

triggering increase SIRtarget.

Decrease the SIRtarget immediately if both DCH and E-DCH meet the condition

for triggering decrease SIRtarget.

Services with invalid statistics are excluded from the combination.

With this principle:

In status 1, 2, 3, 4, 5, 10, 12, SIRtarget is increased.



In status 6, 7, 8, 14, 15, 16, SIRtarget remains unchanged.

In status 9, 11, 13, SIRtarget is decreased.

Figure 3-5 Coupling OLPC for HSUPA and R99

When the traffic

setup on E-DCH,

start the OLPC

Shield the R99

OLPC, only start

the HSUPA OLPC

Start the R99 and HSUPA’s

OLPC together, and based on the

table 3-9,decide the result

Send the new

SIRtarget to Node B

Configure the up link DPDCH

channel?

NO

YES

Need to adjust the SIRtarget?

YES

NOBased on the new

statistic date,

restart the decision

Until the traffic’s end, then

release the coupling judge

3.3.5.4.2 Coupling of the NHR target based HSUPA OLPC and BLER target based R99

algorithm

For the situation that R99 and HSUPA algorithms meet the output condition

simultaneously, the maximum adjustment quantity is used.



3.4 MBMS Power Control

The technical description of MBMS power control is given in the ZTE UMTS MBMS

Feature Guide.

3.5 Downlink Enhanced CELL_FACH Power Control

When downlink enhanced CELL_FACH is supported, downlink service can be bear on

HS-DSCH channel in CELL_FACH state, so the power of HS-SCCH and HS-PDSCH in

downlink enhanced CELL_FACH state should be set. The power of HS-SCCH and

HS-PDSCH in downlink enhanced CELL_FACH state is now be configured in OMMR,

where, the HS-SCCH power is EFACHHSSCCHPwr, and the HS-PDSCH power is

EFACHHSPDSCHPwr.

3.6 Uplink Enhanced CELL_FACH Power Control

When downlink enhanced CELL_FACH is supported, in CELL_FACH state, uplink

service can be bear on common E-DCH channel, downlink service can be bear on

HS-DSCH channel, and downlink associated-channel is F-DPCH. In uplink enhanced

CELL_FACH state, the channel power related parameters are determined as in the

following:

i. The initial power of F-DPCH is FdpchPwrEFach. Note: when FdpchPwrEFach

reaches the value 15.1dB, it means the initial power of F-DPCH is determined by

the Node B.

ii. When the IE “ACK-NACK and CQI Capable” in the Node B audit response, and the

ACK/NACK/CQI Support on HS-DPCCH Indicator in UL Enhanced CELL_FACH

State AckNackCqiSupInd has the value “True”, the RNC needs to configure the

Measurement Power Offset (MPOEFach) for HS-DSCH in uplink enhanced

CELL_FACH state.

iii. For uplink channel power control, the SIR target is SIRtargetCEdch. The uplink

inner loop power control algorithm in the uplink enhanced CELL_FACH state is



determined by the parameter UlIlPcAlgEFach, and the step size of uplink inner loop

power control in uplink enhanced CELL_FACH state is TpcStepSizeEFach.

iv. The power calculating formula for the first preamble of the Common E-DCH is the

same with that of PRACH, it is as the following:

Preamble_Initial_Power = Primary CPICH TX power – CPICH_RSCP + UL

interference + Constant Value

Where,

Primary CPICH DL TX power (UUtranCellFDD.primaryCpichPower) is the

transmit power of the Primary CPICH channel.

CPICH_RSCP is measured by the UE.

UL interference is the uplink interference, which is measured and obtained by

the Node B and updated in real time in SIB 5 or 5bis.

Constant Value is the IE “Constant Value” in SIB 5 or 5bis, it is determined by

the parameter ConstVal in OMMR.

The initial power of DPCCH channel in common E-DCH transmission is determined

as the following:

DPCCH_Initial_power = Preamble_Initial_Power + Step RampPower + Power

offset Pp-e

(The formula is the same with the PRACH control part initial power calculation.)

Where,

Power Ramp Step (PRStep) is the power offset between two continuous

preambles.

Power offset Pp-e (POPpe) is the power offset between the last preamble and

the initial power of the DPCCH in uplink enhanced CELL_FACH state.

v. For common E-DCH transmission, a different E-DCH MAC-d flow identity is



configured for CCCH, DCCH and DTCH respectively. For CCCH, the E-DCH

MAC-d flow identity is 7, which is described in 3Gpp. Considering the QoS quality

requirement of the DCCH and DTCH is different, different E-DCH MAC-d flow

identity is configured for DCCH and DTCH individually, they are as fixed as 6 and 0.

For each MAC-d flow, the E-DCH MAC-d flow power offset (E-DCH HARQ Power

Offset FDD) can be set respectively, and it also can be set differently for different

TTI conditions. When TTI is 2ms, for CCCH, DCCH and DTCH, the E-DCH MAC-d

flow power offset (E-DCH HARQ Power Offset FDD) is CEdchHarqPOTti2[1],

CEdchHarqPOTti2[2] and CEdchHarqPOTti2[3] respectively. When TTI is 10ms, for

CCCH, DCCH and DTCH, the E-DCH MAC-d flow power offset (E-DCH HARQ

Power Offset FDD) is CEdchHarqPOTti10[1], CEdchHarqPOTti10[2] and

CEdchHarqPOTti10[3] respectively.

3.7 Period BER based OLPC

In the situation that data quantity of the traffic is very low, SIRtarget adjustment may be not

timely according to the existing OLPC algorithm. In this case the period BER based

OLPC algorithm is introduced:

Node B reports DPCCH BER periodically to the RNC. Under the condition that the switch

(OlpcBerSwitch) is turned on, RNC preserves the number of TTI with data in a slide

window, the length of which is indicated by TimWinSize. The uplink BER algorithm is

opened when the number of TTI with data for all services is less than

TtiNumThreshOpen.

RNC will do a first-order filter processing of the BER reported by the Node B. The filter

coefficient is BerFilterCoeff. When BER is continuously greater than the threshold

USrvPc.berTargetUpThres for USrvPc.berCntThres times, the SIRtarget adjustment

quantity is USrvPc.ulSirTargUpStep; When BER is continuously less than the threshold

USrvPc.berTargetDnThres for USrvPc.berCntThres times, the SIRtarget adjustment

quantity is -USrvPc.ulSirTargDnStep.

The period BER based algorithm is closed when the number of TTI with data of at least

one service is greater than TtiNumThreshCls.



Note: The period BER based algorithm can be opened only when all RLs for a UE

support a BER report. The capability of the Node B under SRNC is indicated in AUDIT

RESPONSE message. The capability of the Node B under DRNC is indicated by the

parameter RncFeatSwitchBit26.

Combination strategy for period BER based algorithm and other OLPC algorithms:

The period BER based algorithm can be used together with CRC-based algorithm and

BLER target algorithm. And the maximum adjustment quantity is adopted.

3.8 SIR Target Rapid Convergence

In the condition without this algorithm, in order to ensure better performance in the

beginning, the service setup success rate for example, a big value of the initial SIR target

will be configured. It will need more time for the SIR target convergence to the needed

SIR target based on the target BLER, and it affect the system capacity. So the SIR target

rapid convergence algorithm is introduced.

The SIR target rapid convergence algorithm is controlled by the switch SirRapidConvSwi.

When SirRapidConvSwi = 1, the SIR target will be divided into two parts:

SIRTarget= SIRtargetBLER + SIRtargetAdd.

Where,

1. SIRtargetBLER is the SIR target that satisfies the service requirement of the BLER

target. This part is the result of the quality information based OLPC, for R99 service,

it can be determined by the CRC based OLPC or BLER target based OLPC, for

HSUPA service, it can be determined by NHR based OLPC or NHR target based

OLPC, and the algorithm is determined by the parameter OlPcAlg, For details refer

to the section 3.1.5 “Uplink Outer Loop Power Control of R99” and the section 3.3.5

“HSUPA Uplink Outer Loop Power Control”.

Notes:

i. Here, all algorithms in the section 3.1.5 “Uplink Outer Loop Power Control of

R99” and section 3.3.5 “HSUPA Uplink Outer Loop Power Control” can be used.



The period BER based OLPC described in the section 3.7 also can be used.

ii. The following restriction must be ensured all the time:

USrvDivPc.uLMinSIR- SIRtargetAdd <= SIRtargetBLER <= USrvDivPc.uLMaxSIR-

SIRtargetAdd.

2. SIRtargetAdd is the part to meet the need of better performance in the beginning. In

this way, SIRtargetBLER does not need to be configured with a larger value than the

BLER requirement, and configuring SIRtargetAdd with a value larger than zero can

meet the need, To make the SIR target convergence to the needed SIR target

based on the BLER target, it is only required to make the SIRtargetAdd decrease to

zero rapidly. Here, the SIRtargetAdd is decreased over a period, the period is 100ms,

and the step of decreasing is USrvPc.addiSIRDownStep.

3. The initial value of SIRtargetAdd is USrvDivPc.initSirAdd, and the initial value of

SIRtargetBLER is USrvDivPc.initBlerSIR.

3.9 High Priority OLPC

The service quality or channel quality based OLPC is named normal OLPC in the ZTE

RAN, which is described in the section 3.1.5 “Uplink Outer Loop Power Control of R99”,

section 3.3.5 “HSUPA Uplink Outer Loop Power Control” , section 3.7 “Period BER based

OLPC ” and section 3.8 “SIR Target Rapid Convergence”.

There is some condition that SIR cannot converge to SIRTarget, it means the absolute

value of the SIR error is larger than a threshold. If it continues to do the normal OLPC

based on the service quality under this condition, the absolute value of the SIR error will

be larger, after the radio condition recovers to the normal level, a too big absolute value

of SIR error will require a long time to complete SIR convergence to SIRTarget, this will

affect the service quality or the system capacity. So, the ZTE RNC introduces an OLPC

based on SIR error, which is named “high priority OLPC”.

3.9.1 Algorithm Description

The function switch of the high priority OLPC is OlPCPrioSwitch.



The high priority OLPC is based on the SIR error measurement event. The SIR error

measurement event includes event E1, E2, F1, F2. When the event E1 or F1 is reported,

it means the absolute value of the SIR error is larger than the related threshold, and it is

required to trigger the higher priority OLPC and stop the normal OLPC. When the event

E2 or F2 is reported, it means the absolute value of the SIR error is smaller than the

related threshold, and it is required to recover to the normal OLPC.

The thresholds for each SIR error measurement event as the following:

0

SIRerror

Event E1 Threshold

（evtEfSirEThrd1）

Event F1 Threshold


Event E2 Threshold


Event F2 Threshold


When the event E1 or F1 reported, it triggers the higher priority OLPC and stops the

normal OLPC, while at the same time, it determines whether to adjust the SIRTarget

according to the compared results between BLER and USrvPc.blerTarget of the service.

1. When high priority OLPC is triggered by event E1, SIR is larger than SIRTarget.

If USrvPc.blerTarget / BLER < 3, it indicates the SIR is not too big, and the SIRTarget is

small, so SIRTarget can be increased by a step of |0.5*SIRerror|.

If USrvPc.blerTarget / BLER >= 3, it indicates the SIR is too big, and the SIRTarget does

not need to be adjusted.



2. When high priority OLPC is triggered by event F1, SIR is smaller than SIRTarget.

If BLER / USrvPc.blerTarget >1.2, it indicates the SIR is too small, and the SIRTarget does

not need to be adjusted.

If BLER / USrvPc.blerTarget <=1.2, it indicates the SIR is not too big, and the SIRTarget is

big, so the SIRTarget can be decreased by a step of |0.5*SIRerror|.

Notes:

i. For HSUPA services, if high priority OLPC is triggered, the SIRTarget will be fixed.

ii. When SIR Target Rapid Convergence algorithm is switched on (sirRapidConvSwi=1),

SIRTarget is divided into two parts (SIRTarget = SIRtargetBLER + SIRtargetAdd, details refer to

the section 3.8 “SIR Target Rapid Convergence”), and when high priority OLPC is

triggered, the two parts of SIRTarget, SIRtargetBLER and SIRtargetAdd will be recover to the

initial value: USrvDivPc.initSirAdd and USrvDivPc.initBlerSIR.

3.9.2 Related measurement

OLPC Related measurement parameters as the following:

1. DEDICATED MEASUREMENT INITIATION REQUEST-> Dedicated Measurement

Type (dedMeasType) = SIR Error;

2. DEDICATED MEASUREMENT INITIATION REQUEST-> Measurement Filter

Coefficient (UNbDedMeas.measFilterCoeff).

3. DEDICATED MEASUREMENT INITIATION REQUEST->Report Characteristics

(UNbDedMeas.rptType)->>Event E

->>> Measurement Threshold 1 (evtEfSirEThrd1).

->>> Measurement Threshold 2 (evtEfSirEThrd2)

->>> Measurement Hysteresis Time (evtAbcdefTime)

->>> Report Periodicity->>>>CHOICE Report Periodicity Scale

(UNbDedMeas.rptPrdUnit)



->>> Report Periodicity->>>> Report Periodicity Value (UNbDedMeas.rptPrd)

4. DEDICATED MEASUREMENT INITIATION REQUEST->Report Characteristics

(UNbDedMeas.rptType)->>Event F



->>> Measurement Hysteresis Time (evtAbcdefTime)

->>> Report Periodicity->>>>CHOICE Report Periodicity Scale

(UNbDedMeas.rptPrdUnit)

->>> Report Periodicity->>>> Report Periodicity Value (UNbDedMeas.rptPrd).

3.10 Load based CQI Feedback Cycle and CQI

Repetition Factor

The uplink load can be decreased effectively by using long CQI feedback cycle when

there are a lot of HSDPA users in the cell. And when the cell uplink load is low, the short

CQI feedback cycle still can be used for the better service quality purpose.

3.10.1 Algorithm Description

When the switch of CQI Feedback Cycle and CQI Repetition Factor adjustment based on

load is on (cqiFeedbaLoadSwi = 1), the IE CQI Feedback Cycle (UHspa.cqiCycle) and

CQI Repetition Factor (UHspa.cqiRepFactor) are configured based on the actual

synthesize uplink and downlink cell load level as the following:

The Synthesize Uplink and

Downlink Cell Load Level

CQI Feedback Cycle k CQI Repetition Factor

Level 1: Low load level UHspa.cqiCycle[0] UHspa.cqiRepFactor[0]

Level 2: Medium load level UHspa.cqiCycle[1] UHspa.cqiRepFactor[1]

Level 3: High load level UHspa.cqiCycle[2] UHspa.cqiRepFactor[2]



The synthesize uplink and downlink cell load level is the lower level of uplink load level

and HSDPA user number level.

Where,

1. The uplink load level is based on the uplink RoT and the number of uplink equivalent

AMR user. The details refer to the uplink load level described in “ZTE UMTS Load

Adaptive Power Control Feature Guide”. Note: there is no relationship between the

load level here and the switch of load based BLER function (BlerLoadSwitch).

2. The HSDPA user number level is determined as the following:

The sample of the HSDPA user number is HsdpaNumSample, and the filter

formula is:

HsdpaNum (i) = β* HsdpaNumSample + (1-β)*HsdpaNum(i-1)

Where, β is the filter factor (UserNumFilterCoeff).

The HSDPA user number level is determined according to the compare between the

filter result HsdpaNum(i) and the threshold as following table:

HSDPA User Number Level HsdpaNum

Level 1: Low HSDPA user number

level

HsdpaNum < HsdpaNumLow

Level 2: Medium HSDPA user

number level

HsdpaNumLow <= HsdpaNum <

HsdpaNumHigh

Level 3: High HSDPA user number

level

HsdpaNum >= HsdpaNumHigh

Notes:

i. When cqiFeedbaLoadSwi = 1, for the user with CS + PS multi-services, the

high load level configuration UHspa.cqiCycle[2] and UHspa.cqiRepFactor[2]

always are used.

ii. When cqiFeedbaLoadSwi = 0, all users use the low load level configuration

UHspa.cqiCycle[0] and UHspa.cqiRepFactor[0] as default.



iii. For uplink enhanced CELL_FACH users, the low load level configuration

UCommEdch.cqiCycle[0] and UCommEdch.cqiRepFactor[0] always are used.

The uplink enhanced CELL_FACH refers to “HSPA evolution - enhanced

FACH&RACH Feature Guide”.

3.11 Common Channel Power Optimization

Because the idle time is longer than busy time for the PICH and SCCPCH, the Node B

will modify the transmission power of the PICH and SCCPCH according to whether there

is data on the channels.

For PICH, the Node B decides on each PICH frame, when there is a paging (PI=1) then

transmits the symbols with normal power, when there is no paging (PI=0) then reduces

transmission power by the pichDtxPO.

For SCCPCH, the Node B decides on each SCCPCH frame, when there is no data and

basicPwrOptSwitch is ON then performs DTX on the channel including all control fields.

When basicPwrOptSwitch is OFF, the Node B transmits the symbols with normal power,

4 Parameters and Configurations

4.1 Common Parameters

4.1.1 List of Common Parameters

Abbreviated Name Parameter Name

SIB7Originator SIB7 Originator

ConstVal PRACH Initiation Tx Power Constant Value

PRStep PRACH Preamble Power Ramp Step

MaxRACHTxPwr Maximum Allowed UL TX Power of RACH

UUtranCellFDD.primaryCpic

hPower P-CPICH Power

ScpichPwr S-CPICH Power




MimoScpichPwr MIMO S-CPICH Power

PichPower PICH Power

AichPower AICH Power

MaxFachPwr Maximum FACH Power

BchPower BCH Power

PrimarySchPower Primary SCH Power

SecondarySchPower Secondary SCH Power

PchPower PCH Power

PO1 S-CCPCH TFCI Field Power Offset

PO3 S-CCPCH Pilot Field Power Offset

DpcchPcpLen DPCH PC Preamble Length

dpcchPcpLenQChat DPCH PC Preamble Length for QChat Service

SrbDelay SRB Delay

srbDelayQChat SRB Delay for QChat Service

MaxDlDpchPO[MAX_BP] Power Offset of the Maximum Downlink DPCH

Showing Different Basic Priority

MaxUlDpchPO[MAX_BP] Power Offset of the Maximum Uplink DPCH Showing

Different Basic Priority

CoverPrd Shield Period for Increasing SIR Target in Threshold

Algorithm

DlTpcN DL TPC Pattern 01 Count

USrvPc.blerTarget BLER Target

UUtranCellFDD.loadScene Cell Load Scenario

4.1.2 Configuration of Common Parameters

4.1.2.1 SIB7 Originator

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN

Cell->UTRAN Cell



Parameter configuration

RNC originate SIB7 is based on the common measurement reported by the Node B,

so it is not in time and exactly. When the Node B originates SIB7, the RTWP

updating is more in time and exactly.

4.1.2.2 PRACH Initiation Tx Power Constant Value

OMC path


Cell->Channel Configuration->AICH Configuration->PRACH Configuration


It is required to consider the system demand on the timeliness of accessing system

and cell capacity. The receive power of single antenna receiver should be twice as

the receive power of dual antenna receiver.

If the parameter value is too big, the initial PRACH transmission power might be too

big, it would generate unnecessary power waste and affect the cell capacity, but the

access process would be short.

If the parameter value is too small, the initial PRACH transmission power would be

more reasonable, but it would have more preambles for power ramp, it would make

the access process longer.

4.1.2.3 PRACH Preamble Power Ramp Step

OMC path


Cell->Channel Configuration->AICH Configuration->PRACH Configuration


It is required to consider the system demand on the timeliness of accessing system

and cell capacity.



If the parameter value is too big, the initial PRACH transmission power might be too

big, it would generate unnecessary power waste and affect the cell capacity, but the

access process would be short.

If the parameter value is too small, the initial PRACH transmission power would be

more reasonable, but it would have more preambles for power ramp, it would make

the access process longer.

4.1.2.4 Maximum Allowed UL TX Power of RACH

OMC path


Cell->UTRAN Cell


It is required to consider the uplink PRACH coverage and interference to the

neighboring cell. The parameter should be set according to the coverage of the cell

to ensure that the UE at the cell border can be acknowledged by the Node B and

reduce the interference to the neighboring cell at the same time.

The Larger this parameter is, the larger the uplink PRACH coverage is.

Smaller this parameter is, smaller the uplink PRACH coverage is.

4.1.2.5 P-CPICH Power

OMC path


Cell->UTRAN Cell


The parameter value is configured to satisfy the requirement of probability of right

receive, coverage and system capacity.



If the parameter value is too small, the PCPICH coverage would be so small that

the UE's probability of right receiving would be bad when UE is in the edge of the

cell.

If the parameter value is too large, it would increase the unnecessary interference,

and waste the downlink power and decrease the downlink capacity.

4.1.2.6 S-CPICH Power

OMC path


Cell->Channel Configuration->SCPICH Configuration


This parameter indicates the SCPICH transmission power in non MIMO cell (cell

portion).

The value of this parameter is based on the requirement of cell portion coverage.

The larger this parameter is, the bigger coverage is, but a too much larger S-CPICH

power will generate unnecessary interference, and reduce the capacity. The

smaller this parameter is, the smaller coverage.

Note: Cell portion is not support now.

4.1.2.7 MIMO S-CPICH Power

OMC path


Cell->Channel Configuration->SCPICH Configuration


This parameter indicates the SCPICH transmission power offset for MIMO. This

parameter is the offset relative to the PCPICH power.

The value of this parameter is based on the requirement of MIMO cell coverage.



The larger this parameter is, the bigger coverage is, but a too much larger S-CPICH

power will generate unnecessary interference, and reduce the capacity. The

smaller this parameter is, the smaller coverage.

4.1.2.8 PICH Power

OMC path


Cell->UTRAN Cell


The parameter value is configured to make sure the UE in cell edge receive the

PICH rightly and avoid generating unnecessary power waste.

If the parameter value is too small, the paging information cannot be correctly

received when a UE is at the edge of the cell, it might make the UE read the PCH

channel by mistake, and it would reduce the downlink coverage.

If the parameter value is too big, it would increase the unnecessary interference to

other common channel, and waste the downlink power, it would reduce the cell

capacity.

4.1.2.9 AICH Power

OMC path


Cell->UTRAN Cell



AICH rightly and avoid generating unnecessary power waste.

If the parameter value is too small, the AI information might cannot be rightly

received when UE in the edge of the cell, it would reduce the downlink coverage.



If the parameter value is too big, it would increase the unnecessary interference to

other common channel, and waste the downlink power, it would reduce the cell

capacity.

4.1.2.10 Maximum FACH Power

OMC path


Cell->Channel Configuration->SCCPCH Configuration



FACH with the biggest data rate rightly and avoid generating unnecessary power

waste.

If the parameter value is too small, the FACH channel coverage will be so small that

the UE's receiving quality will be bad when it is in the edge of the cell.

If the parameter value is too large, it will increase the interference unnecessary,

waste the downlink power and decrease the downlink capacity.

4.1.2.11 BCH Power

OMC path


Cell->UTRAN Cell


It is required to consider the downlink coverage and system capacity. The

parameter value is configured to ensure the UE in cell edge receive the system

information rightly and avoid generating unnecessary power waste.

If the parameter value is too small, the BCH coverage will be so small that the UE's

probability of right receiving will be bad when it is in the edge of the cell.



If the parameter value is too big, it will increase the unnecessary interference, waste

the downlink power and decrease the downlink capacity.

4.1.2.12 Primary SCH Power

OMC path


Cell->UTRAN Cell


The parameter value is configured based on the requirement on coverage and

capacity of system.

If the parameter value is too small, the PSCH coverage will be so small that the UE

cannot search the cell when it is in the edge of the cell.



4.1.2.13 Secondary SCH Power

OMC path


Cell->UTRAN Cell



capacity of system.

If the parameter value is too small, the SSCH coverage will be so small that the UE

cannot search the cell when it is in the edge of the cell.





4.1.2.14 PCH Power

OMC path


Cell->UTRAN Cell


For PCH channel, the date rate is fixed, so the power should ensure the PCH date

rate at the cell margin. Too big PCH power is waste power, and too small PCH

power cannot ensure the UE be paged at the cell margin.

4.1.2.15 S-CCPCH TFCI Field Power Offset

OMC path





capacity of system. If the parameter value is too small, the SCCPCH TFCI domain

power will be so small that the UE's probability of right receiving will be bad when it

is in the edge of the cell. If the parameter value is too large, it will increase the

interference unnecessary, waste the downlink power and decrease the downlink

capacity.

4.1.2.16 S-CCPCH Pilot Field Power Offset

OMC path







capacity of system. If the parameter value is too small, the SCCPCH Pilot domain

power will be so small that the UE's probability of right receiving will be bad when it

is in the edge of the cell. If the parameter value is too large, it will increase the

interference unnecessary, waste the downlink power and decrease the downlink

capacity.

4.1.2.17 DPCH PC Preamble Length

OMC path


Cell->Extended Info of UTRAN Cell


The value of this parameter should ensure the DPDCH power is suitable at the

beginning of the DPDCH transmission. If this parameter is too big, the DPDCH

transmission is not start while the DPCCH power is already in a suitable level, it

waste power. If this parameter is too small, it might begin DPDCH transmission at a

low power, and it might make the BLER high in the beginning of DPDCH

transmission. But ZTE RNC has configured the parameter of SrbDelay, it can run

power control to several RFs before transmitting signaling, that improve the radio

link quality and increase the successful receive rate of signaling.

4.1.2.18 DPCH PC Preamble Length for QChat Service

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->QChat Service Configuration


The value of this parameter should ensure the DPDCH power is suitable at the

beginning of the DPDCH transmission for Qchat users. If this parameter is too big,

the DPDCH transmission is not start while the DPCCH power is already in a



suitable level, it waste power. If this parameter is too small, it might begin DPDCH

transmission at a low power, and it might make the BLER high in the beginning of

DPDCH transmission.

4.1.2.19 SRB Delay

OMC path




The value of this parameter should ensure the DPDCH power is change to a

suitable level before sending RB0~RB4 message. If this parameter is too small, it

might begin to send RB0~RB4 message at a low power, and it might make

message be decode mistakenly.

4.1.2.20 SRB Delay for QChat Service

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->QChat Service

Configuration


The value of this parameter should ensure the DPDCH power is change to a

suitable level before Qchat users sending RB0~RB4 message. If this parameter is

too small, it might begin to send RB0~RB4 message at a low power, and it might

make message be decode mistakenly.

4.1.2.21 Power Offset of the Maximum Downlink DPCH Showing Different Basic

Priority

OMC path




Configuration->QOS Function->QoS Basic Configuration


The parameter value is configured based on the system demand on whether

different basic priority users need have different maximum downlink power. The

larger this parameter is the bigger the actual maximum downlink power. The

smaller this parameter is, the smaller the actual maximum downlink power.

4.1.2.22 Power Offset of the Maximum Uplink DPCH Showing Different Basic

Priority

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration-> Service

Configuration->QOS Function->QoS Basic Configuration


The parameter value is configured based on the system demand on whether

different basic priority users need have different maximum uplink power. The larger

this parameter is the bigger the actual maximum uplink power. The smaller this

parameter is, the smaller the actual maximum uplink power.

4.1.2.23 Shield Period for Increasing SIR Target in Threshold Algorithm

OMC path




It is relative to the parameter TimeDelay, The value of CoverPrd must larger than

the round-trip time. It means that the value of CoverPrd must larger than double of

the TimeDelay. If parameter is too big, it will waste the time of SIR target adjustment,

and make SIR target adjust too slowly. And if parameter is too small, it might be



smaller than the double of TimeDelay, the result of SIR target adjustment last time

had not been reflected in.

4.1.2.24 DL TPC Pattern 01 Count

OMC path


Cell->UTRAN Cell


This parameter is used to ensure the TPC command is "0" and "1" by turns before

the uplink is synchronized when first radio link is setup, it avoid the power be

adjusted by mistake. The larger this parameter is, the longer initial power be kept.

The smaller this parameter is, the shorter initial power be kept, and higher

probability of the power be affect by error TPC.

4.1.2.25 BLER Target

OMC path


Configuration->Service Function->Power Control Profile Related to

Service->Power Control Related to Service


It is configured based on the requirement of service quality. The parameter is larger,

the service needed quality is higher. The parameter is smaller, the service needed

quality is lower.

4.1.2.26 Cell Load Scenario

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell




This parameter indicates whether the cell is high load cell or not. The parameter

should be set according to the load condition of the cell.

If the cell always in high load condition, set this parameter with the value "1: High

Load Cell", else the value of this parameter should be "0: Normal Load Cell".

4.2 Related Parameters of R99 downlink Power

Balancing

4.2.1 List of Related Parameters of R99 Downlink Power Balancing


AdjType Adjustment Type for DL Power Balance

IurPwrCtlReqSwch Switch of Using DL Power Control Request Information in Iur

Interface

dedMeasType Dedicated Measurement Type

nbDMCfgNote Function of Configuration Parameters

UNbDedMeas.rptTyp

e Report Characteristics

nbDMCfgNo NbDed Measure Configuration No

UNbDedMeas.rptPrd Report Periodicity Value

UNbDedMeas.rptPrd

Unit Choice Report Periodicity Scale

UNbDedMeas.measF

ilterCoeff Measurement Filter Coefficient

4.2.2 Configuration Related Parameters of R99 Downlink Power Balancing

4.2.2.1 Adjustment Type for DL Power Balance

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Link



Configuration->Iub Link


The value of this parameter is based on whether need to balance power, and the

purpose of power balancing.

"None" indicates there is no need to balance the DL power.

"Common" indicates to balance the DL power but the balanced radio links use the

same reference power. It can resolve the "power drifting" problem when the UE in

macro diversity status.

4.2.2.2 Switch of Using DL Power Control Request Information in Iur Interface

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UMTS Logical

Function Configuration


This parameter indicates the switch of using DL POWER CONTROL REQUEST

information in Iur Interface to control power balancing.

When the switch is on, DRNC send the DL POWER CONTROL REQUEST

information to the Node B which is the same with the DL POWER CONTROL

REQUEST information sent by SRNC through Iur interface.

When the switch is off, DRNC would discard the DL POWER CONTROL REQUEST

information sent by SRNC through Iur interface.

If the quality of the radio link in DRNC is bad for using the downlink power balancing

parameters from SRNC, even make call drop rate rise, then this switch can be

turned off.



4.2.2.3 Dedicated Measurement Type

OMC path


Configuration->Measurement Configuration->NodeB Dedicated Measurement

Profile->NodeB Dedicated Measurement Configuration


This parameter indicates the type of dedicated measurement to be executed by the

Node B.

Configuration Rule: Dedicated measurement type should be chose according to the

usage of the dedicated measurement.

4.2.2.4 Function of Configuration Parameters

OMC path





This parameter indicates the function, purpose etc. of the dedicated measurement

parameters indicated by the configuration index.

Configuration Rule: According to the corresponding function of the dedicated

measurement.

4.2.2.5 Report Characteristics

OMC path







This parameter indicates the report characteristics of measurement results, which

can be on demand, periodic or by triggering all kinds of events.

Configuration rule: according to the measurement type and event of the dedicated

measurement.

4.2.2.6 NbDed Measure Configuration No

OMC path





This parameter indicates the NbDed Measure Configuration Number.

4.2.2.7 Report Periodicity Value

OMC path





This parameter indicates the frequency of measurement report transmitted by the

Node B.



Configuration Rule: According to the contribution to the system load and the

timeliness of the measurement report.

The larger the value, the more contribution to the system load but the less timely of

the measurement report; the smaller the value, the less contribution to the system

load but the more timely of the measurement report.

4.2.2.8 Choice Report Periodicity Scale

OMC path





This parameter indicates the time unit of measurement report transmitted by the

Node B.

Configuration Rule: According to the measurement period which is determined

according to the contribution to the system load and the timeliness of the

measurement report.

4.2.2.9 Measurement Filter Coefficient

OMC path





This parameter indicates the L3 filter coefficient.

The involved factor for setting this parameter: the smoothness and real-time of

measurement report value.



Influence of this parameter: the less of the value, the less fluctuate of the

measurement report value; the larger of the value, the more real-time of the

measurement report value.

Suggestion for setting this parameter: Do not adjust.

4.3 Related Parameters of R99 Power Control

4.3.1 List of Related Parameters of R99 Power Control


refUSrvPcProfile Used Power Control Profile Related to Service

UlIlPcAlg Uplink Inner Loop Power Control Algorithm

TpcStepSize Step Size of Uplink Inner Loop Power Control

USrvPc.ulSirTargUpSt

ep Uplink SIR Target Up Step Size

USrvPc.ulSirTargDnSt

ep Uplink SIR Target Down Step Size

TpcDlStep Step Size of Downlink Inner Loop Power Control

TxDivMod Transmit Diversity Mode

USrvDivPc.maxDlDpch

Pwr DPCH Maximum DL Power

USrvDivPc.minDlDpch

Pwr DPCH Minimum DL Power

DpchPO1 DPCH PO1

DpchPO2 DPCH PO2

DpchPO3 DPCH PO3

USrvDivPc.dpcchPilotE

bN0 DPCCH Pilot Field Eb/N0

USrvDivPc.maxUlDpch

Pwr Maximum Allowed Uplink DPCH Transmission Power

USrvDivPc.uLInitSIR Uplink Initial SIR Target

USrvDivPc.uLMaxSIR Maximum Uplink SIR Target

USrvDivPc.uLMinSIR Minimum Uplink SIR Target




USrvPc.errorThresh Error Transport Block Number Threshold

USrvPc.blerAccpPerio

d Tolerance BLER Period

DynaUpdtPO2Sw Dynamic Update PO2 Switch

TpcErrTarget TPC Command Error Rate Target

POSetup Power Offset for Downlink DPCH Initial Power Calculation

when Call Setup

POSoftHO Power Offset for Downlink DPCH Initial Power Calculation

when Soft or Softer Handover

PORabHardHO Power Offset for Downlink DPCH Initial Power Calculation

when RAB Hard Handover

POSrbHardHO Power Offset for Downlink DPCH Initial Power Calculation

when SRB Hard Handover

POReEstablish Power Offset for Downlink DPCH Initial Power Calculation

when RAB Re-Establishment

USrvPc.maxSirTargDn

Step Uplink SIR Target Maximum Down Step Size

USrvPc.swchAdaptive

Step

Uplink Outer Loop PC SIR Target Adaptive Down Step Size

Switch

USrvPc.ulOlPcQESwc

hSil Uplink Outer Loop PC QE Switch For Silent Mode

USrvPc.qeCntThres The Number Threshold of Physical Channel BER Less Than

or Equal BER Target

USrvPc.qePhyBerTarS

il Physical Channel BER Target For Silent Mode

IurEcNoDelta The Offset of CPICH Ec/No in Iur Interface Relative to the

UE Measurement Result

SirUpAddStep Additional Size for Uplink SIR Target Increasing When

Consecutive Error TB Occurs

USrvPc.maxSirTargUp

Step Uplink SIR Target Maximum Up Step Size

ValidTimTbCovPrd Valid Time Window for the TB in Shield Period

USrvPcProfile.intialloa

dscene Initial Load Scenario




USrvPc.srvType Sub-service Type

imeiPcFunSwitch IMEI Based Power Control Function Switch

imeiPcSwitch IMEI Utility Switch for Power Control

imeiULMaxSirOffset IMEI Related Offset of Uplink Maximum SIR Target

imeiULMinSirOffset IMEI Related Offset of Uplink Minimum SIR Target

imeiMaxDlDpchPO IMEI Related Offset of Downlink Maximum DPCH Power

imeiMinDlDpchPO IMEI Related Offset of Downlink Minimum DPCH Power

ImeiUtilityExt IMEI Utility Extension

OlPcAlg Normal Algorithm Method

USrvPc.ulSirStep Uplink SIR Target Up Step Size for R99

ShieldPeriodSwch Shield Period Switch

OutSirTimWinSize Time Window Size of Opening Shield Period

OutSirThresh Threshold of Opening Shield Period

ShieldPeriod Shield Period

4.3.2 Configuration of Related Parameters of R99 Power Control

4.3.2.1 Used Power Control Profile Related to Service

OMC path



This parameter indicated the used USrvPcProfile (Service Related Power

Control Profile).

4.3.2.2 Uplink Inner Loop Power Control Algorithm

OMC path


Configuration->Service Function->Power Control Profile Related to Service->Power



Control Related to Service


The "algorithm 1" suit for the quick channel fading wireless scenario.

The "algorithm 2" suit for the slow channel fading wireless scenario.

4.3.2.3 Step Size of Uplink Inner Loop Power Control

OMC path





The value is meaningful only if 1 is selected for the uplink inner loop power control

algorithm. The greater the adjustment step is, the SIR is calculated to converge

faster to approach SIR target and the adjustment is done faster.

4.3.2.4 Uplink SIR Target Up Step Size

OMC path





The greater the parameter is, the larger the increase step will be when the increase

decision is output and SIR target is increased faster. This parameter can be queried

by the current uplink sub-service type.



4.3.2.5 Uplink SIR Target Down Step Size

OMC path





The smaller the parameter is, SIR target is decreased more slowly when the

decrease decision is output. This parameter can be queried by the current uplink

sub-service type

4.3.2.6 Step Size of Downlink Inner Loop Power Control

OMC path





This parameter is usually configured as a small value for stable channel conditions,

or as a large value for bad radio environment.

4.3.2.7 Transmit Diversity Mode

OMC path



Control Related to Service -> Power Control Related to Service and Diversity Mode


The configuration of this parameter is based on whether the transmit diversity mode



is used, and which mode is in use.

4.3.2.8 DPCH Maximum DL Power

OMC path





It is required to consider the service quality and cell capacity.

The configure principle is to ensure the power satisfy the minimum requirement for

the UE in the margin of the cell, it means that it can conquer the maximum path

loss.

If the maximum power of the service is too big, the power of this service can get a

very high power when the radio condition is bad, and it will reduce the capacity of

the cell.

If the maximum power of the service is too small, the power of the service might not

satisfy the requirement in different condition.

4.3.2.9 DPCH Minimum DL Power

OMC path





It is required to consider the call drop rate and cell capacity.

If the value of the parameter is too big, it will make the power cannot be decrease to



a suitable level, and it will reduce the capacity of the cell.

If the value of the parameter is too small, it will increase the call drop rate. Decrease

the power too much may make the power cannot return to normal level, so the call

drop happened.

4.3.2.10 DPCH PO1

OMC path



Control Related to Service-> Power Control Related to Service and Diversity Mode


It is required to consider the service quality and cell capacity. The control domain is

the foundation to demodulate the data domain, so the power of control domain is

usually relatively higher than data domain.

If the power of TFCI domain is too small, TFCI cannot be demodulated correctly, it

would affect the service quality.

If the power of TFCI domain is too large, it will waste power, and affect the cell

capacity.

4.3.2.11 DPCH PO2

OMC path



Control Related to Service->Power Control Related to Service and Diversity Mode







If the power of TPC domain is too small, TPC cannot be demodulated correctly, it

would affect the service quality.

If the power of TPC domain is too large, it will waste power, and affect the cell

capacity.

4.3.2.12 DPCH PO3

OMC path








If the power of PILOT domain is too small, PILOT cannot be demodulated correctly,

it would affect the service quality.

If the power of PILOT domain is too large, it will waste power, and affect the cell

capacity.

4.3.2.13 DPCCH Pilot Field Eb/N0

OMC path



Control Related to Service ->Power Control Related to Service and Diversity Mode




Eb/N0 of DPCCH PILOT domain is different in different radio environment, it is

required to consider the service quality and cell capacity.

The larger this parameter is, the larger the power of the service, it will reduce the

capacity of the cell.

The smaller this parameter is, the smaller the power of the service, it will affect the

quality of the service.

4.3.2.14 Maximum Allowed Uplink DPCH Transmission Power

OMC path





It is required to consider the service quality and cell capacity. The value of this

parameter should ensure the uplink coverage.

If too small of this parameter, it will reduce the quality of uplink services.

If too bigger of this parameter, it might increase the uplink interference and reduce

the capacity.

The real maximum transmission power is the minimum value of

USrvDivPc.maxUlDpchPwr and the UE transmission power ability.

4.3.2.15 Uplink Initial SIR Target

OMC path







It is required to consider the uplink synchronization and cell uplink capacity. Initial

SIR target of the service should near the normal level of the SIR target, this can

make the initial convergence of the SIR target rapidly.

If the value of this parameter is too big, it would make the power be increased too

much in the initial period after service setup, and it would reduce the capacity of the

cell.

If the value of this parameter is too small, it would make the power too low in the

initial period after service setup, and it would cost long time to complete uplink

synchronization, even make uplink synchronization failure.

4.3.2.16 Maximum Uplink SIR Target

OMC path





It is required to consider the service quality and cell uplink capacity.

If this parameter is too big, it might make the SIR target too big, and make the uplink

power too big, it would affect the cell capacity.

If this parameter is too small, it might make the power too small to satisfy the

requirement of uplink receiver demodulation, and it would affect the service quality

and uplink coverage.

4.3.2.17 Minimum Uplink SIR Target

OMC path







It is required to consider the service quality and cell uplink capacity.

If this parameter is too big, it might make the SIR target cannot be decreased to a

suitable value, and make the power cannot be decrease to a suitable level, it would

affect the cell capacity.

If this parameter is too small, it might need long time to increase the SIR target from

the minimum value to normal working level, and affect the service quality.

4.3.2.18 Error Transport Block Number Threshold

OMC path





Bigger value of this parameter, the harder to increase SIR target. And if this

parameter is too big, it will reduce the service quality. Smaller value of this

parameter, the easier to increase SIR target. And if this parameter is too small, it will

waste power.

4.3.2.19 Tolerance BLER Period

OMC path







The parameter is bigger, it is more difficult for the UE to decrease the SIR target and

accordingly easier to waste power resource. The parameter is smaller, it is easier

for the UE to decrease the SIR target and accordingly easier to affect service

quality.

4.3.2.20 Dynamic Update PO2 Switch

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->PLMN Relating

Configuration->Logic RNC Configuration


Turn on this switch, system capacity can be optimized, but it is required to add an

additional Iub control FP (RADIO INTERFACE PARAMETER UPDATE).

Turn on this switch, DPCH TPC domain might waste power, but it doesn't need to

add an additional Iub control FP (RADIO INTERFACE PARAMETER UPDATE).

This function can be turned on when the capacity of the cell is limited by downlink

power.

4.3.2.21 TPC Command Error Rate Target

OMC path


Configuration->Hspa Configuration


This parameter is TPC error rate used for F-DPCH OLPC. If the parameter value is

too large, the performance requirement of the control channel might not be meet. If

the parameter value is too small, it would be very difficult to meet this TPC error

target, and generate unnecessary waste power.



4.3.2.22 Power Offset for Downlink DPCH Initial Power Calculation when Call Setup

OMC path




Bigger this parameter is, bigger the initial power when call setup.

If this parameter is too big, the initial power when RAB or SRB setup would be too

big, it could have high rate of success RAB or SRB setup, but it would reduce the

system capacity.

If this parameter is too small, the initial power when RAB or SRB setup would be too

small, it would reduce the rate of success RAB or SRB setup.

4.3.2.23 Power Offset for Downlink DPCH Initial Power Calculation when Soft or

Softer Handover

OMC path




Bigger this parameter is, bigger the initial power when soft or softer handover.

If the parameter is too big, the initial power when soft or softer handover would be

too big, it would make high rate of new radio link downlink successful

synchronization, but it also make the power waste and reduce the cell capacity.

If the parameter is too small, the initial power when soft or softer handover would be

too small, it would make low rate of new radio link downlink successful

synchronization.



4.3.2.24 Power Offset for Downlink DPCH Initial Power Calculation when RAB Hard

Handover

OMC path




Bigger this parameter is, bigger the initial power when RAB hard handover.

If this parameter is too big, the initial power when RAB hard handover would be too

big, it could have high rate of RAB success hard handover, but it would reduce the

system capacity.

If this parameter is too small, the initial power when RAB hard handover would be

too small, it would reduce the rate of RAB success hard handover.

4.3.2.25 Power Offset for Downlink DPCH Initial Power Calculation when SRB Hard

Handover

OMC path




Bigger this parameter is, bigger the initial power when SRB or F-DPCH hard

handover.

If this parameter is too big, the initial power when SRB or F-DPCH hard handover

would be too big, it could have high rate of SRB or F-DPCH success hard handover,

but it would reduce the system capacity.

If this parameter is too small, the initial power when SRB or F-DPCH hard handover

would be too small, it would reduce the rate of SRB or F-DPCH success hard

handover.



4.3.2.26 Power Offset for Downlink DPCH Initial Power Calculation when RAB

Re-Establishment

OMC path




Bigger this parameter is, bigger the initial power when RAB re-establishment.

If this parameter is too big, the initial power when RAB re-establishment would be

too big, it could have high rate of success RAB re-establishment, but it would

reduce the system capacity.

If this parameter is too small, the initial power when RAB re-establishment would be

too small, it would reduce the rate of success RAB re-establishment.

4.3.2.27 Uplink SIR Target Maximum Down Step Size

OMC path





If the parameter value is too large, the uplink SIR target decreasing accuracy will be

too low. Accordingly it will affect the demodulation performance, and it will affect the

service quality.

If the parameter value is too small, the uplink SIR target decreasing rate will be too

slow. Accordingly it will affect the system capacity.

When USrvPc.swchAdaptiveStep = 0, this parameter is invalid.



4.3.2.28 Uplink Outer Loop PC SIR Target Adaptive Down Step Size Switch

OMC path





If the switch is on, SIR target decrease would be rapidly when service quality is

good, and system capacity would be increased.

If the switch is off, SIR target decrease step is fixed, and service quality is relative

good.

4.3.2.29 Uplink Outer Loop PC QE Switch For Silent Mode

OMC path





The value of this parameter should consider the service quality and system

capacity.

Turn on this switch, when TB number is less then USrvPc.blerAccpPeriod, the SIR

target can be decreased based on the physical channel BER, so the SIR target can

be decreased rapidly, and the system capacity can be increased, but the service

quality will be affected.

Turn off this switch, he SIR target can be decreased only when TB number is reach

USrvPc.blerAccpPeriod and error TB number is less then USrvPc.errorThresh, so

the SIR target can be decreased slowly, and the system capacity will be less, but

the service quality will be better.



Adjustment suggestion: When system uplink capacity is limit, this function can be

open.

4.3.2.30 The Number Threshold of Physical Channel BER Less Than or Equal BER Target

OMC path






capacity.

If the parameter value is larger, it is more difficult to decrease the SIR target.

Accordingly, it will improve the service quality but affect the system capacity.

If the parameter value is smaller, it is easier to decrease the SIR target. Accordingly,

it will improve the system capacity but affect the service quality.

4.3.2.31 Physical Channel BER Target for Silent Mode

OMC path






capacity.

If the parameter value is larger, it is easier to decrease the SIR target. Accordingly,

it will improve the system capacity but affect the service quality.



If the parameter value is smaller, it is more difficult to decrease the SIR target.


4.3.2.32 The Offset of CPICH Ec/No in Iur Interface Relative to the UE Measurement

Result

OMC path




This parameter indicates the offset of CPICH Ec/No in Iur interface relative to the

CPICH Ec/No of measurement result. The CPICH Ec/No in Iur interface is

calculated by the CPICH Ec/No of UE measurement result minus this offset.

If this parameter is too small, the initial power of the radio link in DRNC will be too

big, it is a power wasting.

If this parameter is too big, the initial power of the radio link in DRNC will be small, it

might affect the service quality.

Adjustment suggestion: If there are some problems, such as call drop, which

are because the initial power of radio link in DRNC is too small, then this

parameter can be configured with a bigger value.

4.3.2.33 Additional Size for Uplink SIR Target Increasing When Consecutive Error

TB Occurs

OMC path




This parameter indicates the additional size for uplink SIR target increasing when



consecutive error TB occurs.

If the parameter value is larger, the SIR target will be increased more rapidly when

consecutive error TB occurs. Accordingly, it will improve the service quality but

affect the system capacity.

If the parameter value is smaller, the SIR target will be increased more slowly when

consecutive error TB occurs. Accordingly, it will improve the system capacity but

affect the service quality.

Adjustment Suggestion:

If there is no need to increase the SIR target increasing step size when consecutive

error TB occurs, this parameter can be set to 0.

If there is need to increase the SIR target increasing step size when consecutive

error TB occurs, this parameter can be set to 0.1dB (or else value).

4.3.2.34 Uplink SIR Target Maximum Up Step Size

OMC path





This parameter indicates the maximum step size of increasing the uplink SIR target.

If the parameter value is too large, the SIR target increasing step size will be too big

when consecutive error TB or consecutive SIR target increasing occurs. Accordingly,

it will improve the service quality but affect the system capacity.

If the parameter value is too small, the SIR target increasing step size will be not big

enough when consecutive error TB or consecutive SIR target increasing occurs.

Accordingly, it will improve the system capacity but affect the service quality.



4.3.2.35 Valid Time Window for the TB in Shield Period

OMC path




This parameter indicates the valid time window for TB in the shield period.

If the parameter is too big, even if the time between two SIR target increasing is too

long, the SIR target increasing step size in the second time will be increased, it will


If the parameter is too big, only when the time between two SIR target increasing is

very short, the SIR target increasing step size in the second time could be increase,

it will affect the service quality.

Adjustment Suggestion:

If there is no need to increase the SIR target increasing step size when consecutive

SIR target increasing occurs, this parameter can be set to 0.

If there is need to increase the SIR target increasing step size when consecutive

SIR target increasing occurs, this parameter can be set to 40 (it means 400ms) or

else value.

4.3.2.36 Initial Load Scenario

OMC path


Configuration ->Service Function->Power Control Profile Related to Service


This parameter indicates the initial load scenario for the parameters in

USrvPcProfile, and this parameter cannot be modified.



4.3.2.37 Sub-service Type

OMC path


Configuration ->Service Function->Power Control Profile Related to



This parameter indicates the sub service type, used for numbering for each sub

service. 0...5 are used for signaling, 6...250 are used for service. Odd number is

configured for downlink service; even number is configured for uplink service.

This parameter cannot be modified.

4.3.2.38 IMEI Based Power Control Function Switch

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration


This parameter indicates the IMEI based power control function switch. When

this switch is on, some power control parameters can be configured based on

IMEI.

Configuration Rule: Based on the requirement.

4.3.2.39 IMEI Utility Switch for Power Control

OMC path


Configuration->Imei for Black List




This parameter indicates the IMEI utility switch for power control.

Configuration Rule: Based on the requirement.

When this switch is on, the power offset parameters related to the IMEI is

effective.

When this switch is off, the power offset parameters related to the IMEI is not

effective.

4.3.2.40 IMEI Related Offset of Uplink Maximum SIR Target

OMC path




This parameter indicates the IMEI related offset of uplink maximum SIR target.

For the UE, whose IMEI is indicated in UImeiBlkLis and with imeiPcSwitch = 1,

the uplink maximum SIR target need to add this offset.

If this parameter is too big, it might make the SIR target too big, and make the

uplink power too big, it would affect the cell capacity.

If this parameter is too small, it might make the power too small to satisfy the

requirement of uplink receiver demodulation, and it would affect the service

quality and uplink coverage.

4.3.2.41 IMEI Related Offset of Uplink Minimum SIR Target

OMC path






This parameter indicates the IMEI related offset of uplink minimum SIR target.

For the UE, whose IMEI is indicated in UImeiBlkLis and with imeiPcSwitch = 1,

the uplink minimum SIR target need to add this offset.

If this parameter is too big, it might make the SIR target cannot be decreased to

a suitable value, and make the power cannot be decrease to a suitable level, it

would affect the cell capacity.

If this parameter is too small, it might need long time to increase the SIR target

from the minimum value to normal working level, and affect the service quality.

4.3.2.42 IMEI Related Offset of Downlink Maximum DPCH Power

OMC path




This parameter indicates the IMEI related offset of downlink maximum DPCH

power. For the UE, whose IMEI is indicated in UImeiBlkLis and with

imeiPcSwitch = 1, the downlink maximum DPCH power need to add this offset.

If the parameter is too big, the power of this service can get a very high power

when the radio condition is bad, and it will reduce the capacity of the cell.

If the parameter is too small, the power of the service might not satisfy the

requirement in different condition.

4.3.2.43 IMEI Related Offset of Downlink Minimum DPCH Power

OMC path






This parameter indicates the IMEI related offset of downlink minimum DPCH

power. For the UE, whose IMEI is indicated in UImeiBlkLis and with

imeiPcSwitch = 1, the downlink minimum DPCH power need to add this offset.

If the value of the parameter is too big, it will make the power cannot be

decrease to a suitable level, and it will reduce the capacity of the cell.

If the value of the parameter is too small, it will increase the call drop rate.

Decrease the power too much may make the power cannot return to normal

level, so the call drop happened.

4.3.2.44 IMEI Utility Extension

OMC path




This parameter used for IMEI Utility Extension. The bit0 of this parameter

indicates the IMEI utility switch for considering load when configure power

control parameters, bit0=0 means switch off, and bit0=1 means switch on.

If bit0=1, the power offset parameter related to the IMEI should not be used

when the cell load is high and the power offset parameter is positive.

If bit0=0, the power offset parameters related to the IMEI should be used and

not considering the cell load.

4.3.2.45 Normal Algorithm Method

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Extended Info of

RNC




This parameter indicates which outer loop power control algorithm is used. 0:

BLER Target Algorithm; 1: CRC-based OLPC algorithm

4.3.2.46 Uplink SIR Target Up Step Size for R99

OMC path





This parameter indicates the SIR target up step size for R99(2ms E-TTI). This

parameter can be queried by the current uplink sub-service type.

4.3.2.47 Shield Period Switch

OMC path


RNC


This parameter indicates the shield period switch. The shield period algorithm is

used to control the speed of SIRtarget increase, so the system capacity is

improved, but the service quality might be affected.

4.3.2.48 Time Window Size of Opening Shield Period

OMC path


RNC




This parameter indicates the time window size of opening shield period. The

greater this parameter is, the easier shield action is triggered.

4.3.2.49 Threshold of Opening Shield Period

OMC path


RNC


This parameter indicates the threshold of opening shield period. The smaller

this parameter is, the easier shield action is triggered.

4.3.2.50 Shield Period

OMC path


RNC


This parameter indicates the shield period. The greater this parameter is the

longer shield action is continued.

4.4 Related Parameters of HSDPA Power Control

4.4.1 List of Related Parameters of HSDPA Power Control


UHspa.ackPwrOffset HS-DPCCH ACK Power Offset for Single Radio Link or

Intra-NodeB Handover

UHspa.nackPwrOffset HS-DPCCH NACK Power Offset for Single Radio Link or


UHspa.cqiPwrOffset HS-DPCCH CQI Power Offset for Single Radio Link or





InterAckPwrOfst HS-DPCCH ACK Power Offset for Inter-NodeB Handover

InterNackPwrOfst HS-DPCCH NACK Power Offset for Inter-NodeB Handover

InterCqiPwrOfst HS-DPCCH CQI Power Offset for Inter-NodeB Handover

UHspa.cqiCycle CQI Feedback Cycle

UHspa.cqiRepFactor CQI Repetition Factor

UHspa.anackRepFact

or ACK-NACK Repetition Factor

HsdschTotPwrMeth HSPA Total Downlink Power Allocation Method

HspaPwrRatio HSPA Total Downlink Power

MinHspaPwrRto Minimum HSPA Total Downlink Power

MaxHspaPwrRto Maximum HSPA Total Downlink Power

refUMPOProfile Used HS-PDSCH Measurement Power Offset profile

UMPOProfile HS-PDSCH Measurement Power Offset Profile Object ID

profileId

(UMPOProfile) HS-PDSCH Measurement Power Offset Configuration Index

UMPO HS-PDSCH Measurement Power Offset Configuration

Object ID

measPwrOffset HS-PDSCH Measurement Power Offset

app64QamInd Actual Configuration of the HSDPA Evolution Function of UE

in the Cell (64QAM)

appMimoInd Actual Configuration of the HSDPA Evolution Function of UE

in the Cell (MIMO)

appDcHsdpaInd Actual Configuration of the HSDPA Evolution Function of UE

in the Cell (DC-HSDPA)

nodeBSafeThr Safe Threshold for NodeB(%)

4.4.2 Configuration of Related Parameters of HSDPA Power Control

4.4.2.1 HS-DPCCH ACK Power Offset for Single Radio Link or Intra-NodeB

Handover

OMC path






This parameter indicates the power offset of HS-DPCCH ACK domain relative to

DPCCH when UE has a single link or is in the intra-the Node B handover.


receive and system capacity.

If the parameter value is too large, it would waste the uplink power, increase the UL

interference and reduce the UL capacity of cell.

If the parameter value is too small, it would affect the receiving quality of the

HS-DPCCH ACK domain.

4.4.2.2 HS-DPCCH NACK Power Offset for Single Radio Link or Intra-NodeB

Handover

OMC path




This parameter indicates the power offset of HS-DPCCH NACK domain relative to






If the parameter value is too small, it would affect the receiving quality of

HS-DPCCH NACK domain.



4.4.2.3 HS-DPCCH CQI Power Offset for Single Radio Link or Intra-NodeB

Handover

OMC path




This parameter indicates the power offset of HS-DPCCH CQI domain relative to




If the parameter is configured too large, more interference will be generated and the

capacity will be reduced.

If the parameter is configured too small, the quality of the receiving will be bad.

4.4.2.4 HS-DPCCH ACK Power Offset for Inter-NodeB Handover

OMC path




This parameter indicates the power offset of HS-DPCCH ACK domain relative to

DPCCH when UE is in inter-the Node B handover.







If the parameter value is too small, it would affect the receiving quality of the

HS-DPCCH ACK domain.

4.4.2.5 HS-DPCCH NACK Power Offset for Inter-NodeB Handover

OMC path




This parameter indicates the power offset of HS-DPCCH NACK domain relative to






If the parameter value is too small, it would affect the receiving quality of

HS-DPCCH NACK domain.

4.4.2.6 HS-DPCCH CQI Power Offset for Inter-NodeB Handover

OMC path




This parameter indicates the power offset of HS-DPCCH CQI domain relative to






If the parameter is configured too large, more interference will be generated and the

capacity will be reduced.

If the parameter is configured too small, the quality of the receiving will be bad.

4.4.2.7 CQI Feedback Cycle

OMC path




This parameter indicates the CQI feedback cycle.

Configure CQI Feedback Cycle according to the impact to downlink throughput and

uplink interference because of different CQI Feedback Cycle. CQI Feedback Cycle

and CQI Repetition Factor determine the time of same CQI to be feedback.

If the CQI Feedback Cycle is too big, UE would wait long time to send the new CQI,

the HSDPA scheduling would be not exact, and it would affect the downlink

throughput.

If the CQI Feedback Cycle is too small, the CQI would more likely to reflect the

actual quality of the channel, and the HSDPA scheduling would be more exact, but it

would generate more uplink interference.

4.4.2.8 CQI Repetition Factor

OMC path




CQI Feedback Cycle and CQI Repetition Factor determine the time of same CQI to



be feedback. The bigger the CQI Repetition Factor is, the longer time to wait to

send the new CQI, the less exact of the scheduling, and less system capacity. But

the smaller the CQI Repetition Factor is, the less probability of CQI been decoded

rightly.

4.4.2.9 ACK-NACK Repetition Factor

OMC path




The bigger the ACK-NACK Repetition Factor is, the less ACK or NACK of new data

would be feed back to network, the less system capacity. The smaller the

ACK-NACK Repetition Factor is, the less probability of ACK or NACK been

decoded rightly.

4.4.2.10 HSPA Total Downlink Power Allocation Method

OMC path




This parameter indicates the allocation method for HSPA total power.

RNC dynamic assigning mode is a method of assigning HSPA total power by the

RNC, and the Node B does not need to allocate the power itself.

the Node B assigning mode can make full use of power resource with best effort.

4.4.2.11 HSPA Total Downlink Power

OMC path




Cell->Hspa Configuration In A Cell


When the HSPA total downlink power is allocated used the method of "RNC

dynamic assigning mode", if this parameter is too small, the HSPA total power

would be too small, and it might reduce the quality and capacity of HSPA service. If

this parameter is too big, the HSPA total power would be too big, and it might

reduce the quality and capacity of R99 service.

When the HSPA total downlink power is allocated used the method of "the Node B

Assigning Mode", this parameter is invalid.

4.4.2.12 Minimum HSPA Total Downlink Power

OMC path





Dynamic Assigning Mode". Larger value of this parameter, more power can be used

by HS subscriber, easier to trigger the rate decrease of R99 subscriber, so the KPI

of DCH subscriber is bad. But if the value of this parameter is set too small, the

power allocated to HSPA subscriber is less, it will affect the throughput of HSPA

subscriber when the resource is little.



4.4.2.13 Maximum HSPA Total Downlink Power

OMC path







Dynamic Assigning Mode", if this parameter is too small, the HSPA total power

would be too small, and it might reduce the quality and capacity of HSPA service. If

this parameter is too big, the HSPA total power would be too big, and it might

reduce the quality and capacity of R99 service.



4.4.2.14 Used HS-PDSCH Measurement Power Offset profile

OMC path



This parameter indicated the used HS-PDSCH measurement power offset

profile (UMPOProfile).

4.4.2.15 HS-PDSCH Measurement Power Offset

OMC path


Configuration->HS-PDSCH Measurement Power Offset Profile->HS-PDSCH

Measurement Power Offset Configuration


The principle is to control the CQI in the range from 1 to 30. If this parameter is

configured too big, the service might get big CQI, and get big power, but it will

reduce the cell capacity. But if this parameter is configured too small, it might not

satisfy the requirement of CQI.



4.4.2.16 Actual Configuration of the HSDPA Evolution Function of the UE in the Cell

(64QAM)

OMC path





This parameter indicates whether 64QAM is used in the configuration of MPO,

which is just for showing in screen and cannot be reconfigured.

4.4.2.17 Actual Configuration of the HSDPA Evolution Function of the UE in the Cell

(MIMO)

OMC path





This parameter indicates whether MIMO is used in the configuration of MPO, which

is just for showing in screen and cannot be reconfigured.

4.4.2.18 Actual Configuration of the HSDPA Evolution Function of UE in the Cell

(DC-HSDPA)

OMC path







This parameter indicates whether DC-HSDPA is used in the configuration of MPO,

which is just for showing in screen and cannot be reconfigured.

4.4.2.19 Safe Threshold for the Node B

OMC path




This parameter indicates the safe threshold of the HSDPA power, that is, the

maximum HSDPA power when the Node B is in free mode. In any case, HSDPA

power must not exceed this threshold.

If this parameter is too small, the total HSDPA power would be too small, and it

would affect the throughput of the HSDPA service.

If this parameter is too big, the total power of the Node B would be too big, and it

would affect the system stability.

4.5 Related Parameters of HSUPA Power Control

4.5.1 List of Related Parameters of HSUPA Power Control


UHspa.edpcchPOTti2 Quantified E-DPCCH/DPCCH Power Offset (2ms TTI)

UHspa.edpcchPOTti10 Quantified E-DPCCH/DPCCH Power Offset (10ms

TTI)

UHspa.scheInfoPOTti2 Power Offset for Scheduling Info (2ms TTI)

UHspa.scheInfoPOTti10 Power Offset for Scheduling Info (10ms TTI)

USrvPc.nhrThrUpTti10 NHR Threshold to Adjust SIR Target Upward(10ms

E-TTI)

USrvPc.nhrThrDownTti10 NHR Threshold to Adjust SIR Target Downward(10ms

E-TTI)




USrvPc.nhrThrUpTti2 NHR Threshold to Adjust SIR Target Upward(2ms

E-TTI)

USrvPc.nhrThrDownTti2 NHR Threshold to Adjust SIR Target Downward(2ms

E-TTI)

USrvPc.edchHarqPOFdd E-DCH HARQ Power Offset FDD

EagchPOTti2 E-AGCH Power Offset for TTI 2ms

EagchPOTti10 E-AGCH Power Offset for TTI 10ms

ErgchPOTti2 E-RGCH Power Offset for TTI 2ms in Single Link

Condition

ErgchPOTti10 E-RGCH Power Offset for TTI 10ms in Single Link

Condition

EhichPOTti2 E-HICH Power Offset for TTI 2ms in Single Link

Condition

EhichPOTti10 E-HICH Power Offset for TTI 10ms in Single Link

Condition

UHspa.edchRefPO E-DCH Reference Power Offset

MaxRetransEdch Maximum Number of Retransmissions for E-DCH

USrvPc.dwThrSampNumTti

10

Threshold of Sample Number to Adjust SIR Target

Downward(10ms E-TTI)

USrvPc.upThrSampNumTti1

0


Upward(10ms E-TTI)

USrvPc.dwThrSampNumTti

2


Downward(2ms E-TTI)

USrvPc.upThrSampNumTti2 Threshold of Sample Number to Adjust SIR Target

Upward(2ms E-TTI)

USrvPc.thrHarqFailTti2 Threshold of HARQ Failure Indication Number to

Adjust SIR Target Upward (2ms E-TTI)

USrvPc.thrHarqFailTti10 Threshold of HARQ Failure Indication Number to

Adjust SIR Target Upward (10ms E-TTI)

POEhichSerRls2

Power Offset Relative to E-HICH in Single Link

Condition for E-HICH of Serving RLS in Macro

Diversity Condition (2ms TTI)

POEhichSerRls10


Condition for E-HICH of Serving RLS in Macro





POEhichNoSerRl2


Condition for E-HICH of Non-serving RLS in Macro


POEhichNoSerRl10


Condition for E-HICH of Non-serving RLS in Macro


POErgchSerRls2

Power Offset Relative to E-RGCH in Single Link

Condition for E-RGCH of Serving RLS in Macro


POErgchSerRls10

Power Offset Relative to E-RGCH in Single Link

Condition for E-RGCH of Serving RLS in Macro


POErgchNonSerRls

Power Offset Relative to 10ms TTI E-RGCH in Single

Link Condition for E-RGCH of Non-serving RLS in

Macro Diversity Condition

EagchPOUptSwch Dynamic Updating Switch of E-AGCH Power Offset

USrvPc.ulSirStepTti2 Uplink SIR Target Up Step Size for HSUPA(2ms

E-TTI)

USrvPc.ulSirStepTti10 Uplink SIR Target Up Step Size for HSUPA(10ms

E-TTI)

USrvPc.targetRetranNum Target Number of HARQ Retransmission

USrvPc.fpTargErrorTti2 Target Rate of Error Frame(2ms E-TTI)

USrvPc.fpTargErrorTti10 Target Rate of Error Frame(10ms E-TTI)

4.5.2 Configuration of Related Parameters of HSUPA Power Control

4.5.2.1 Quantified E-DPCCH/DPCCH Power Offset(2ms TTI)

OMC path




This parameter indicates the quantified E-DPCCH/DPCCH power offset configured



for 2ms E-TTI.

If this parameter is too big, E-DPCCH power would be too big, miss detect rate

would be small, but it would generating unnecessary interference, and reduce the

system capacity.

If the parameter is too small, E-DPCCH power would be too small, the miss detect

rate will be too big, service quality requirement cannot be satisfied.

4.5.2.2 Quantified E-DPCCH/DPCCH Power Offset(10ms TTI)

OMC path




This parameter indicates the quantified E-DPCCH/DPCCH power offset configured

for 10ms E-TTI.

If this parameter is too big, E-DPCCH power would be too big, miss detect rate

would be small, but it would generating unnecessary interference, and reduce the

system capacity.

If the parameter is too small, E-DPCCH power would be too small, the miss detect

rate will be too big, service quality requirement cannot be satisfied.

4.5.2.3 Power Offset for Scheduling Info (2ms TTI)

OMC path




The value of this parameter is used to ensure the 2ms TTI scheduling information

be demodulated rightly, and avoiding unnecessary power waste. If this parameter is



too big, it will waste power, and reduce the system capacity. If this parameter is too

small, the scheduling information will not be demodulated, and affect the service

quality.

4.5.2.4 Power Offset for Scheduling Info (10ms TTI)

OMC path




The value of this parameter is used to ensure the 10ms TTI scheduling information

be demodulated rightly, and avoiding unnecessary power waste. If this parameter is

too big, it will waste power, and reduce the system capacity. If this parameter is too

small, the scheduling information will not be demodulated, and affect the service

quality.

4.5.2.5 NHR Threshold to Adjust SIR Target Upward(10ms E-TTI)

OMC path





This parameter indicates the number of HARQ retransmission (NHR) threshold to

increase SIR target when E-TTI=10ms.

If the parameter value is larger, it is more difficult to increase the SIR target.


If the parameter value is smaller, it is easier to increase the SIR target. Accordingly,




4.5.2.6 NHR Threshold to Adjust SIR Target Downward(10ms E-TTI)

OMC path






decrease SIR target when E-TTI=10ms.

If the parameter value is larger, it is easier to decrease the SIR target. Accordingly, it

will improve the system capacity but affect the service quality.



4.5.2.7 NHR Threshold to Adjust SIR Target Upward(2ms E-TTI)

OMC path






increase SIR target when E-TTI=2ms.

If the parameter value is larger, it is more difficult to increase the SIR target.


If the parameter value is smaller, it is easier to increase the SIR target. Accordingly,




4.5.2.8 NHR Threshold to Adjust SIR Target Downward(2ms E-TTI)

OMC path






decrease SIR target when E-TTI=2ms.

If the parameter value is larger, it is easier to decrease the SIR target. Accordingly, it

will improve the system capacity but affect the service quality.



4.5.2.9 E-DCH HARQ Power Offset FDD

OMC path





This parameter indicates the E-DCH HARQ power offset FDD, which is used to

compute the quantized gain factor βed of E-DPDCH.

If the parameter value is larger, the E-DPDCH transmission power will be larger.


If the parameter value is smaller, the E-DPDCH transmission power will be smaller.




4.5.2.10 E-AGCH Power Offset for TTI 2ms

OMC path





This parameter should ensure the E-AGCH power (for 2ms TTI) large enough to

satisfy the minimum requirement for E-AGCH detection (BLER equal or below 1%

in 3GPP 25.101 protocol). It is also required to consider the system capacity.

If this parameter is too small, the minimum requirement for E-AGCH performance

could not be satisfied.

If this parameter is too big, it would waste the power, and affect the system capacity.

4.5.2.11 E-AGCH Power Offset for TTI 10ms

OMC path





This parameter should ensure the E-AGCH power (for 10ms TTI) large enough to

satisfy the minimum requirement for E-AGCH detection (BLER equal or below 1%

in 3GPP 25.101 protocol). It is also required to consider the system capacity.

If this parameter is too small, the minimum requirement for E-AGCH performance





4.5.2.12 E-RGCH Power Offset for TTI 2ms in Single Link Condition

OMC path





This parameter should ensure the E-HICH power (for 10ms TTI) large enough to

satisfy the minimum requirement for E-HICH (MISS ACK equal or below 1% in

3GPP 25.101 protocol). It is also required to consider the system capacity.

If this parameter is too small, the minimum requirement for E-HICH performance



4.5.2.13 E-RGCH Power Offset for TTI 10ms in Single Link Condition

OMC path













4.5.2.14 E-HICH Power Offset for TTI 2ms in Single Link Condition

OMC path











4.5.2.15 E-HICH Power Offset for TTI 10ms in Single Link Condition

OMC path













4.5.2.16 E-DCH Reference Power Offset

OMC path




This parameter is used to estimate the uplink load increase caused by the MAC-e

PDUs which is not decoded. The bigger this parameter is, the bigger E-DPDCH

power, and less system capacity. The smaller this parameter is, the smaller

E-DPDCH power, and lower quality of the service.

4.5.2.17 Maximum Number of Retransmissions for E-DCH

OMC path


Configuration->Service Function->Service Basic Configuration


This parameter is used to incarnate the gain of retransmission. Usually this

parameter is configured with a larger value. The parameter is bigger, there is more

times of retransmission. The parameter is smaller, there is less times of

retransmission.

4.5.2.18 Threshold of Sample Number to Adjust SIR Target Downward(10ms E-TTI)

OMC path







Outer loop power control run in the principle of rapidly increase and slowly decrease

the uplink SIR target. So usually USrvPc.dwThrSampNumTti10 is bigger than

USrvPc.upThrSampNumTti10. The parameter is bigger, it is more difficult to

decrease the SIR target and easier to waste power. The parameter is smaller, it is

easier to decrease the SIR target and to affect the service quality.

4.5.2.19 Threshold of Sample Number to Adjust SIR Target Upward(10ms E-TTI)

OMC path







USrvPc.upThrSampNumTti10.

4.5.2.20 Threshold of Sample Number to Adjust SIR Target Downward(2ms E-TTI)

OMC path








The parameter is bigger, it is more difficult to decrease the SIR target and easier to

waste power.

The parameter is smaller, it is easier to decrease the SIR target and to affect the



service quality.

4.5.2.21 Threshold of Sample Number to Adjust SIR Target Upward(2ms E-TTI)

OMC path








The parameter is bigger, it is more difficult to increase the SIR target and affect the

service quality, easier to waste power.

The parameter is smaller, it is easier to increase the SIR target and easier to waste

power.

4.5.2.22 Threshold of HARQ Failure Indication Number to Adjust SIR Target Upward

(2ms E-TTI)

OMC path





Bigger the number of HARQ failure threshold for increasing SIR target, harder to

increase SIR target. And if this parameter is too big, it will reduce the service quality.

Smaller the number of HARQ fail threshold for increasing SIR target, more easy to

increase SIR target. And if this parameter is too small, it will waste power.



4.5.2.23 Threshold of HARQ Failure Indication Number to Adjust SIR Target Upward

(10ms E-TTI)

OMC path





Bigger the number of HARQ failure threshold for increasing SIR target, harder to

increase SIR target. And if this parameter is too big, it will reduce the service quality.

Smaller the number of HARQ fail threshold for increasing SIR target, easier to

increase SIR target. And if this parameter is too small, it will waste power.

4.5.2.24 Power Offset Relative to E-HICH in Single Link Condition for E-HICH of

Serving RLS in Macro Diversity Condition (2ms TTI)

OMC path




This parameter should ensure the power of serving E-DCH RLS E-HICH (for 2ms

TTI) large enough to satisfy the minimum requirement for E-HICH (MISS ACK equal

or below 5% in 3GPP 25.101 protocol). It is also required to consider the system

capacity.








OMC path




This parameter should ensure the power of serving E-DCH RLS E-HICH (for 10ms

TTI) large enough to satisfy the minimum requirement for E-HICH (MISS ACK equal


capacity.





Non-serving RLS in Macro Diversity Condition (2ms TTI)

OMC path




This parameter should ensure the power of non-serving E-DCH RLS E-HICH (for

2ms TTI) large enough to satisfy the minimum requirement for E-HICH (MISS ACK

equal or below 5% in 3GPP 25.101 protocol). It is also required to consider the

system capacity.







Non-serving RLS in Macro Diversity Condition (10ms TTI)

OMC path




This parameter should ensure the power of non-serving E-DCH RLS E-HICH (for

10ms TTI) large enough to satisfy the minimum requirement for E-HICH (MISS ACK

equal or below 5% in 3GPP 25.101 protocol). It is also required to consider the

system capacity.




4.5.2.28 Power Offset Relative to E-RGCH in Single Link Condition for E-RGCH of


OMC path




This parameter should ensure the power of serving E-DCH RLS E-RGCH (for 2ms

TTI) large enough to satisfy the minimum requirement for E-RGCH (MISS UP equal


capacity.

If this parameter is too small, the minimum requirement for E-RGCH performance





4.5.2.29 Power Offset Relative to E-RGCH in Single Link Condition for E-RGCH of


OMC path




This parameter should ensure the power of serving E-DCH RLS E-RGCH (for 10ms

TTI) large enough to satisfy the minimum requirement for E-RGCH (MISS UP equal


capacity.




4.5.2.30 Power Offset Relative to 10ms TTI E-RGCH in Single Link Condition for

E-RGCH of Non-serving RLS in Macro Diversity Condition

OMC path




This parameter should ensure the power of non-serving E-DCH RLS E-RGCH (for

10ms TTI) large enough to satisfy the minimum requirement for E-RGCH (MISS

DOWN equal or below 5% in 3GPP 25.101 protocol). It is also required to consider

the system capacity.






4.5.2.31 Dynamic Updating Switch of E-AGCH Power Offset

OMC path




If the switch is on, E-AGCH Power Offset is EagchPOTti2 (2ms TTI) or

EagchPOTti10 (10ms TTI) in single radio link condition, and EagchPOTti2 (2ms TTI)

+ MacroDivGain or EagchPOTti10 (10ms TTI) + MacroDivGain in DCH macro

diversity condition. In this way, the HSUPA service quality and system capacity all

are good. Where, MacroDivGain is the macro diversity gain of downlink dedicated

channel, its value is 0dB.

If the switch is off, E-AGCH Power Offset is EagchPOTti2 (2ms TTI) or

EagchPOTti10 (10ms TTI) in single radio link condition or in DCH macro diversity

condition. In this way, Iub reconfiguration is reduced.

4.5.2.32 Uplink SIR Target Up Step Size for HSUPA(2ms E-TTI)

OMC path





This parameter indicates the SIR target up step size for HSUPA (2ms E-TTI). This


4.5.2.33 Uplink SIR Target Up Step Size for HSUPA(10ms E-TTI)

OMC path







This parameter indicates the SIR target up step size for HSUPA (10ms E-TTI). This


4.5.2.34 Target Number of HARQ Retransmission

OMC path





This parameter indicates the target number of HARQ Retransmission. This

parameter is configured according to service quality requirement. If the parameter is

too big, the SIR target will be adjusted too rapidly, it might affect the system capacity.

If the parameter is too small, the SIR target will be adjusted too slowly, it might affect

the service quality.

4.5.2.35 Target Rate of Error Frame(2ms E-TTI)

OMC path





This parameter indicates the target percentage of frames that have a number of

HARQ retransmissions great than USrvPc.targetRetranNum. If the parameter is too

big, it might affect the service quality. If the parameter is too small, it might affect the

system capacity.



4.5.2.36 Target Rate of Error Frame(10ms E-TTI)

OMC path





If the

This parameter indicates the target percentage of frames that have a number of

HARQ retransmissions great than USrvPc.targetRetranNum. If the parameter is too

big, it might affect the service quality. If the parameter is too small, it might affect the

system capacity.

4.6 Related Parameters of MBMS Power Control

Refer to MBMS Feature Guide for details of related parameters of MBMS power control.

4.7 Related Parameters of Downlink Enhanced

CELL_FACH Power Control

4.7.1 List of Related Parameters of Downlink Enhanced CELL_FACH

Power Control


EFACHHSSCCHPwr Enhanced CELL_FACH HS-SCCH Power(dB)

EFACHHSPDSCHPwr Enhanced CELL_FACH HS-PDSCH Power(dB)



4.7.2 Configuration of Related Parameters of Downlink Enhanced


4.7.2.1 Enhanced CELL_FACH HS-SCCH Power(dB)

OMC path


Cell->EFACH Configuration


This parameter indicates the power of HS-SCCH in downlink enhanced

CELL_FACH state, it is a power offset relative to the P-CPICH power in the cell.

The larger of this parameter, the better QoS of the traffic in downlink enhanced

CELL_FACH state, and the lower of cell capacity in downlink enhanced

CELL_FACH state.

The smaller of this parameter, the worse QoS of the traffic in downlink enhanced

CELL_FACH state, and the larger of cell capacity in downlink enhanced

CELL_FACH state.

Adjustment suggestion: this parameter is a power level relative to the configured

P-CPICH power in a cell. A little value can be set in good radio environment to

provide maximum cell capacity in the advance of good traffic performance, and a

large value can be set in bad radio environment to provide good traffic performance.

4.7.2.2 Enhanced CELL_FACH HS-PDSCH Power(dB)

OMC path




This parameter indicates the power of the HS-PDSCH in downlink enhanced



CELL_FACH state, it is a power offset relative to the P-CPICH power in the cell.

The larger of this parameter, the better QoS of the traffic in downlink enhanced

CELL_FACH state, and the lower of cell capacity in downlink enhanced

CELL_FACH state.

The smaller of this parameter, the worse QoS of the traffic in downlink enhanced

CELL_FACH state, and the larger of cell capacity in downlink enhanced

CELL_FACH state.

Adjustment suggestion: this parameter is a power level relative to the configured

P-CPICH power in a cell. A little value can be set in good radio environment to

provide maximum cell capacity in the advance of good traffic performance, and a

large value can be set in bad radio environment to provide good traffic performance.

4.8 Related Parameters of Uplink Enhanced


4.8.1 List of Related Parameters of Uplink Enhanced CELL_FACH Power

Control


FdpchPwrEFach Initial F-DPCH Power in Uplink Enhanced

CELL_FACH State

AckNackCqiSupInd ACK/NACK/CQI Support on HS-DPCCH Indicator

in UL Enhanced CELL_FACH State

MPOEFach HS-PDSCH Measurement Power Offset (UL

Enhanced CELL_FACH)

SIRtargetCEdch SIR Target for Common E-DCH

UlIlPcAlgEFach Uplink Inner Loop Power Control Algorithm in

Uplink Enhanced CELL_FACH State

TpcStepSizeEFach Step Size of Uplink Inner Loop Power Control in

Uplink Enhanced CELL_FACH State

POPpe

Power Offset between the Last Preamble and the

Initial Power of the DPCCH in Enhanced Uplink

CELL_FACH Sate




CEdchHarqPOTti2 HARQ Power Offset for Common E-DCH MAC-d

Flow (2ms TTI)

CEdchHarqPOTti10 HARQ Power Offset for Common E-DCH MAC-d

Flow (10ms TTI)

4.8.2 Configuration of Related Parameters of Uplink Enhanced


4.8.2.1 Initial F-DPCH Power in Uplink Enhanced CELL_FACH State

OMC path




This parameter indicates the initial F-DPCH power in uplink enhanced CELL_FACH

state. The largest value in the value range is used to indicate that the RNC do not

need to configure it in PHYSICAL SHARED CHANNEL RECONFIGURATION

REQUEST, and the power of F-DPCH is decided by the Node B.

Bigger this parameter is, bigger initial power of F-DPCH for common E-DCH

transmission, and too big initial power will affect the system capacity. But the

biggest value 15.1dB means the initial power of F-DPCH is determined by the Node

B. The initial power of F-DPCH determined by the Node B will be more accurately.

Smaller this parameter is, smaller initial power of F-DPCH for common E-DCH

transmission, and too small initial power will affect the service quality.

4.8.2.2 ACK/NACK/CQI Support on HS-DPCCH Indicator in UL Enhanced

CELL_FACH State

OMC path






This parameter indicates whether ACK/NACK and CQI are supported on

HS-DPCCH in uplink enhanced CELL_FACH state.

"0: Not Supported" means ACK/NACK and CQI are not supported on HS-DPCCH in

uplink enhanced CELL_FACH state, it reduce the HS-DPCCH information in the Iub

and Uu interface.

"1: Supported" means ACK/NACK and CQI are supported on HS-DPCCH in uplink

enhanced CELL_FACH state, the Node B schedule HS-PDSCH power based on

ACK/NACK and CQI will be more accurately.

4.8.2.3 HS-PDSCH Measurement Power Offset (UL Enhanced CELL_FACH)

OMC path




This parameter indicates the assumed HS-PDSCH power offset relative to

P-CPICH/S-CPICH power used for CQI measurement in uplink enhanced

CELL_FACH state.

If this parameter is configured too big, the service in enhanced CELL_FACH state

might get big CQI, and get big power, but it will reduce the cell capacity.

If this parameter is configured too small, it might not satisfy the requirement of CQI.

4.8.2.4 SIR Target for Common E-DCH

OMC path






This parameter indicates the SIR target of the common E-DCH in uplink enhanced

CELL_FACH state.

Bigger this parameter is, higher power of the UE in CELL_FACH state, but too big

this parameter will waste power.

Smaller this parameter is, lower power of the UE in CELL_FACH state, but too small

this parameter will not satisfy the QoS need.

4.8.2.5 Uplink Inner Loop Power Control Algorithm in Uplink Enhanced

CELL_FACH State

OMC path




This parameter indicates which uplink inner loop power control algorithm is used in

uplink enhanced CELL_FACH state.

For algorithm 1 inner loop power control is done every time slot, so it can response

to radio condition change rapidly.

For algorithm 2 inner loop power control is done every 5 time slots, it is suit for radio

condition change smoothly.

4.8.2.6 Step Size of Uplink Inner Loop Power Control in Uplink Enhanced

CELL_FACH State

OMC path






This parameter indicates the TPC step size for uplink inner loop power control in

uplink enhanced CELL_FACH state.

If this parameter is 1dB, the transmit power will be adjust more smoothly. The power

will be decreased too slowly to waste the power resource affecting the system

capacity and the power will be increased too slowly to affect the service quality.

And if this parameter is 2dB, the transmit power will be adjust more rapidly. The

power will be decreased too lower to affect the service quality and the power will be

increased too higher to waste the power resource affecting the system capacity.

4.8.2.7 Power Offset between the Last Preamble and the Initial Power of the

DPCCH in Enhanced Uplink CELL_FACH Sate

OMC path




This parameter indicates the power offset between the last transmitted preamble

and the initial power of the DPCCH transmission in the Enhanced Uplink in

CELL_FACH state.

Bigger this parameter, bigger initial power of DPCCH in enhanced CELL_FACH

status, and higher demodulation quality.

Smaller this parameter, smaller initial power of DPCCH in enhanced CELL_FACH

status, and lower demodulation quality.

4.8.2.8 HARQ Power Offset for Common E-DCH MAC-d Flow (2ms TTI)

OMC path




Configuration->Common EDCH Configuration


This parameter indicates the HARQ power offset for common E-DCH MAC-d flow

when 2ms TTI is used.

If the parameter value is too large, the E-DPDCH transmission power will be too

large to increase the uplink interference unnecessary and decrease the system

capacity.

If the parameter value is too small, the E-DPDCH transmission power will be too

small to affect the probability of right receive.

4.8.2.9 HARQ Power Offset for Common E-DCH MAC-d Flow (10ms TTI)

OMC path


Configuration->Common EDCH Configuration


This parameter indicates the HARQ power offset for common E-DCH MAC-d flow

when 10ms TTI is used.

If the parameter value is too large, the E-DPDCH transmission power will be too

large to increase the uplink interference unnecessary and decrease the system

capacity.

If the parameter value is too small, the E-DPDCH transmission power will be too

small to affect the probability of right receive.



4.9 Related Parameters of Period BER based OLPC

4.9.1 List of Related Parameters of Period BER based OLPC


OlpcBerSwitch Uplink BER OLPC Algorithm Switch

USrvPc.berTargetUpThres BER Target Up Threshold

USrvPc.berTargetDnThres BER Target Down Threshold

TimWinSize Time Window Size

TtiNumThreshOpen TTI threshold of Opening BER Algorithm

TtiNumThreshCls TTI threshold of Closing BER Algorithm

BerFilterCoeff BER Filter Coefficient

USrvPc.berCntThres The Number Threshold of Trigging SIRtarget

Adjustment

RncFeatSwitchBit26 Whether Support DPCCH BER Report at DRNC

4.9.2 Configuration of Related Parameters of Period BER based OLPC

4.9.2.1 Uplink BER OLPC Algorithm Switch

OMC path


RNC


This parameter indicates the switch of period BER based OLPC algorithm. This

algorithm is applied in the situation that traffic data quantity is low.

4.9.2.2 BER Target Up Threshold

OMC path







This parameter indicates the BER target up threshold in period BER based OLPC

algorithm. This parameter can be queried by the current uplink sub-service type.

4.9.2.3 BER Target Down Threshold

OMC path





This parameter indicates the BER target down threshold in period BER based

OLPC algorithm. This parameter can be queried by the current uplink sub-service

type.

4.9.2.4 Time Window Size

OMC path





This parameter indicates the length of slide window in period BER based OLPC

algorithm. The less of this parameter, the easier this algorithm is opened.

4.9.2.5 TTI threshold of Opening BER Algorithm

OMC path







This parameter indicates the TTI threshold of opening period BER based Algorithm.

The greater of this parameter, the easier this algorithm is opened.

4.9.2.6 TTI threshold of Closing BER Algorithm

OMC path





This parameter indicates the TTI threshold of closing period BER based Algorithm.

The less of this parameter, the easier this algorithm is closed.

4.9.2.7 BER Filter Coefficient

OMC path


RNC


This parameter indicates the BER first-order filter coefficient. It is used to prevent

excessive BER fluctuation.

4.9.2.8 The Number Threshold of Trigging SIRtarget Adjustment

OMC path







This parameter indicates the number threshold of triggering SIR target adjustment

in period BER based algorithm. It is used to prevent the frequent adjustment

because of BER fluctuation.

4.9.2.9 Whether Support DPCCH BER Report at DRNC

OMC path

GUI: Managed Element->UMTS Logical Function Configuration->Link

Configuration->Iur Link


This parameter indicates whether the Node B under DRNC support BER report. 0:

Not Support; 1: Support.

Configuration Rule: This parameter is configured "support" when all the Node Bs

under DRNC support DPCCH BER report and the parameter OlpcBerSwitch is

configured "support".

4.10 Related Parameters of SIR Target Rapid

Convergence

4.10.1 List of Related Parameters of SIR Target Rapid Convergence


sirRapidConvSwi SIR Target Rapid Convergence Switch

USrvPc.addiSIRDownStep Additional SIR Target Down Step Size

USrvDivPc.initBlerSIR Initial Value for BLER Based SIR Target

USrvDivPc.initSirAdd Initial Value for Additional SIR Target



4.10.2 Configuration of Related Parameters of SIR Target Rapid

Convergence

4.10.2.1 SIR Target Rapid Convergence Switch

OMC path


RNC


This parameter indicates the SIR target rapid convergence switch.

When the switch is on, the SIR target can be decreased rapidly to the SIR target

based on the service BLER, so the system capacity is improved, but the service

quality in the beginning might be affected.

Adjustment Suggestion: When system uplink capacity is limit, this function can be

open.

4.10.2.2 Additional SIR Target Down Step Size

OMC path





This parameter indicates the additional SIR target down step size of the SIR target

rapid convergence function.

If the parameter is too big, the SIR target will be decreased too rapidly, it might

affect the service quality.

If the parameter is too small, the SIR target will be decreased too slowly, it might




4.10.2.3 Initial Value for BLER Based SIR Target

OMC path





This parameter indicates the initial value for BLER based SIR target in the SIR

target rapid convergence function.



cell.




Adjustment Suggestion: Initial SIR target based on BLER of the service should near

the normal level of the SIR target which meet the need of service BLER target.

4.10.2.4 Initial Value for Additional SIR Target

OMC path





This parameter indicates the initial value for additional SIR target in the SIR target

rapid convergence function.





cell.




Adjustment Suggestion: Initial value for additional SIR target of the service can be a

little big when the call setup success rate is low.

4.11 Related Parameters of High Priority OLPC

4.11.1 List of Related Parameters of High Priority OLPC


OlpcPrioSwitch Priority Outer Loop PC Switch

evtEfSirEThrd1 Measurement Threshold 1 of Event E/F for SIR Error

evtEfSirEThrd2 Measurement Threshold 2 of Event E/F for SIR Error

evtAbcdefTime Measurement Change Time /Measurement Hysteresis

Time

4.11.1.1 Priority Outer Loop PC Switch

OMC path





This parameter indicates the switch for priority outer loop power control.

When the switch is on, if the windup happen, which indicated that the SIR

cannot reach the SIR target, the priority outer loop power control can be

triggered based on the SIR error event F, it avoid the SIR target being increased

too much, so it can reduce the time for SIR target decreasing after the radio

condition become good. In this way, the system capacity can be improved.



Adjustment Suggestion: If the windup always happens, this function can be

switch on.

4.11.1.2 Measurement Threshold 1 of Event E/F for SIR Error

OMC path





This parameter indicates the threshold 1 used for triggering event E, F for SIR

Error measurement.

Configuration Rule: Considering whether it can correctly and timely reflects the

condition when SIR cannot converge to the SIR target because of deterioration

of radio condition.

The smaller of the absolute value of the parameter is, the easier for event E and

F of SIR error to report. But if it is too small, it will influence the normal OLPC so

as to influence service quality or system capability finally.

The bigger of the absolute value of the parameter is, the harder for event E and

F of SIR error to report. But if it is too large, it will influence the SIR convergence

speed when radio condition recovers SIR has converges to SIR error so as to

influence service quality or system capability finally.

4.11.1.3 Measurement Threshold 2 of Event E/F for SIR Error

OMC path







This parameter indicates the threshold 2 used for triggering event E, F for SIR

Error measurement.

Configuration Rule: Considering whether it can correctly and timely reflects the

condition when SIR cannot converge to the SIR target because of deterioration

of radio condition.

The smaller of the absolute value of the parameter is, the harder for event E

and F of SIR error to report. But if it is too small, when SIR can converge to the

SIR target normally, SIR target keeps fixedly so as influencing service quality or

system capability finally.

The bigger of the absolute value of the parameter is, the more easily for event E

and F of SIR error to report. But if it is too large, when SIR can converge to the

SIR target normally, SIR target keeps rising so as to influence service quality or

system capability finally.

4.11.1.4 Measurement Change Time /Measurement Hysteresis Time

OMC path





This parameter is measurement hysteresis time /change time.

Configuration Rule: according to the measurement type and event of the

dedicated measurement.

The larger this parameter is, the more difficult to trigger the measurement

event.



4.12 Related Parameters of Load based CQI Feedback

Cycle and CQI Repetition Factor

4.12.1 List of Related Parameters of Load based CQI Feedback Cycle and

CQI Repetition Factor


cqiFeedbaLoadSwi The Switch of CQI Feedback Cycle and CQI

Repetition Factor Adjustment Based on Load

hsdpaNumLow Low HSDPA User Number Level Threshold

hsdpaNumHigh High HSDPA User Number Level Threshold

4.12.2 Configuration of Related Parameters of Load based CQI Feedback

Cycle and CQI Repetition Factor

4.12.2.1 The Switch of CQI Feedback Cycle and CQI Repetition Factor Adjustment

Based on Load

OMC path


RNC


This parameter indicates the switch of CQI feedback cycle and CQI repetition factor

adjustment based on load.

If the switch is on, the CQI feedback cycle and CQI repetition factor is configured

based on uplink load and HSDPA user number, and it can improve the uplink

capacity.

If the switch is off, the CQI feedback cycle and CQI repetition factor is fixed, it might

affect the uplink capacity.



4.12.2.2 Low HSDPA User Number Level Threshold

OMC path




This parameter indicates the threshold of low HSDPA user number level. When the

HSDPA user number is smaller than this threshold, it is in low HSDPA user number

level.

Bigger this parameter is, easier the CQI feedback cycle and CQI repetition factor for

low load is used.

Smaller this parameter is, harder the CQI feedback cycle and CQI repetition factor

for low load is used.

Usually the CQI feedback cycle and CQI repetition factor for low load is configured

to improve the HSDPA service quality, but it might affect the uplink capacity.

4.12.2.3 High HSDPA User Number Level Threshold

OMC path




This parameter indicates the threshold of high HSDPA user number level. When the

HSDPA user number is no smaller than this threshold, it is in high HSDPA user

number level.

Smaller this parameter is, easier the CQI feedback cycle and CQI repetition factor

for high load is used.

Bigger this parameter is, harder the CQI feedback cycle and CQI repetition factor



for high load is used.

Usually the CQI feedback cycle and CQI repetition factor for high load is configured

to improve the uplink capacity, but it might affect the HSDPA service quality.

4.13 Related Parameters of Common Channel Power

Optimization

4.13.1 List of Related Parameters of Common Channel Power Optimization


pichDtxPO PICH Power Shifting

basicPwrOptSwitch SCCPCH Power Optimization Switch

4.13.2 Configuration of Related Parameters of Common Channel Power

Optimization

4.13.2.1 PICH Power Shifting

OMC path

GUI: Managed Element -> Radio Parameter -> UMTS


The parameter indicates the power shifting when PICH is without radio frame of

paging.

The bigger this value is, the less power is consumption when PICH is without

paging

4.13.2.2 SCCPCH Power Optimization Switch

OMC path

GUI: Managed Element -> Radio Parameter -> UMTS




The parameter decides whether to disable the SCCPCH transmission when there is

no data in channel.

When the switch is on, SCCPCH transmission power consumption is less when

there is no data.

5 Counter and Alarm

5.1 Counter List

5.1.1 Statistic of Cell TCP

Counter No. Description

C310444435 Configured Maximum DL Power

C310444436 Current utilizing rate of TCP

C310444437 Maximum utilizing rate of TCP

C310446508 Minimum utilizing rate of TCP

C310444439 Sum of utilizing rate of TCP

C310444440 Current TCP

C310444441 Maximum TCP

C310446510 Minimum TCP

C310444443 Sum of TCP

C310444444 Reported times of TCP

5.1.2 Distribution of TCP


C310444445 Times of TCP less than 30.0dBm

C310444446 Times of TCP between[30.0,31.0)dBm



















C310444462 Times of TCP more than 46.0dBm

5.1.3 Statistic of HS Cell DL Configured TCP


C310454484 Configured Maximum DL R99 Power

C310454485 Configured Maximum DL HSDPA Power

5.1.4 Statistic of Cell NonHsTcp


C310454486 Current utilizing rate of nonhsTCP

C310454487 Maximum utilizing rate of nonhsTCP

C310456516 Minimum utilizing rate of nonhsTCP

C310454489 Sum of utilizing rate of nonhsTCP

C310454490 Current nonhsTCP

C310454491 Maximum nonhsTCP

C310456517 Reported times of nonhsTCP

C310456518 Minimum nonhsTCP

C310454493 Sum of nonhsTCP



5.1.5 Distribution of Cell NonHsTcp


C310454495 Times of NONHSDPA TCP less than 30.0dBm

C310454496 Times of NONHSDPA TCP between[30.0,31.0)dBm
















C310454512 Times of NONHSDPA TCP more than 46.0dBm

5.1.6 Statistic of Cell HsTcp


C310454513 Current utilizing rate of Hsdpa TCP

C310454514 Maximum utilizing rate of Hsdpa TCP

C310456520 Minimum utilizing rate of Hsdpa TCP

C310454516 Sum of utilizing rate of Hsdpa TCP

C310454517 Current Hsdpa TCP

C310454518 Maximum Hsdpa TCP

C310456522 Minimum Hsdpa TCP

C310454520 Sum of Hsdpa TCP



5.2 Alarm List

This feature has no related alarm.

6 Glossary

A

ACK Acknowledge

AMC Adaptive Modulation and Coding

B

BER Bit Error Rate

BLER Block Error Rate

C

CPICH Common Pilot Channel

CQI Channel Quality Indicator

D

DCH Dedicated Channel

DL Downlink (Forward link)

DPCCH Dedicated Physical Control Channel

DPCH Dedicated Physical Channel

DPDCH Dedicated Physical Data Channel

E

E-AGCH E-DCH Absolute Grant Channel



E-RGCH E-DCH Relative Grant Channel

E-HICH E-DCH Hybrid ARQ Indicator Channel

E-TFC Enhanced Transport Format Combination

E-TFCI Enhanced Transport Format Combination Indicator

H

HARQ Hybrid Automatic Retransmission Request

HS-DPCCH High Speed Dedicated Physical Control Channel

HS-DSCH High Speed Downlink Shared Channel

HS-PDSCH High Speed Physical Downlink Shared Channel

HS-SCCH High Speed Shared Control Channel

HSDPA High Speed Downlink Packet Access

HSPA High Speed Packet Access

HSUPA High Speed Uplink Packet Access

M

MBMS Multimedia Broadcast Multicast Service

N

NACK No Acknowledge

R

RNC Radio Network Controller

RSCP Received Signal Code Power

RTWP Received Total Wide Band Power



S

SIR Signal to Interference Ratio

T

TB Transmission Block

Tcp Transmit Code Power D-TCP)

TCP Transmitted Carrier Power (C-TCP)

TFC Transport Format Combination

TFCI Transport Format Combination Indicator

TPC Transmit Power Control

TTI Transmission Time Interval

U

UE User Equipment

W

WCDMA Wideband Code Division Multiple Access

zte umts power control feature guide_v8.5_201312_548040

Documents

added section

power allocation

load adaptive power

deleted section

hsdpa total power

r99 outer loop power

initial power offset

downlink power balance