WCDMA BSC6900 R11 Features and Algorithms

WCDMA Radio Network Features &
Algorithms
Southern Eastern Africa Learning

Services
BSC6900 V9-R11
WCDMA UE BEHAVIORS IN IDLE MODE ........................................................................................................ 3

PLMN Selection .................................................................................................................................................. 5
System Information Reception ........................................................................................................................... 9
Cell Selection and Reselection .......................................................................................................................... 12
Location Registration........................................................................................................................................ 31
Paging Procedure ............................................................................................................................................. 34
Access Procedure ............................................................................................................................................. 43
WCDMA POWER CONTROL ALGORITHM AND PARAMETERS ................................................................................. 55
Power Control Overview .................................................................................................................................. 57
Open Loop Power Control ................................................................................................................................ 66
Open Loop Power Control Overview............................................................................................................. 66
PRACH Open Loop Power Control................................................................................................................. 67
Downlink Dedicated Channel Open Loop Power Control ............................................................................... 76
Uplink Dedicated Channel Open Loop Power Control ................................................................................... 81
Closed Loop Power Control .............................................................................................................................. 85
Closed Loop Power Control Overview........................................................................................................... 85
Uplink Inner Loop Power Control.................................................................................................................. 86
Downlink Inner Loop Power Control ............................................................................................................. 93
Outer Loop Power Control ......................................................................................................................... 100
WCDMA HANDOVER ALGORITHM AND PARAMETERS......................................................................................... 107
Intra-Frequency Handover.............................................................................................................................. 111
Intra-Frequency Handover Procedure......................................................................................................... 115
Intra-Frequency Handover Measurement............................................................................................... 116
Intra-Frequency Handover Decision and Execution................................................................................. 142
Neighboring Cell Combination Algorithm ............................................................................................... 150
Signaling Procedures for Intra-Frequency Handover ................................................................................... 153
Inter-Frequency Handover ............................................................................................................................. 159
Inter-Frequency Handover Overview .......................................................................................................... 159

Coverage-based Inter-Frequency Handover............................................................................................ 160
QoS-based Inter-Frequency Handover.................................................................................................... 183
Load-based Inter-Frequency Handover................................................................................................... 188
Speed-based Inter-Frequency Handover ................................................................................................ 195
Blind Handover based on Event 1F ......................................................................................................... 200
Inter-Frequency anti-Ping-Pong.............................................................................................................. 204
Inter-Frequency Handover Retry ............................................................................................................ 206
Signaling Procedures for Inter-Frequency Handover ................................................................................... 209
Inter-RAT Handover ....................................................................................................................................... 211
Coverage-based Inter-RAT Handover...................................................................................................... 218
QoS-based Inter-RAT Handover.............................................................................................................. 238
Load-based Inter-RAT Handover............................................................................................................. 242
Service-based Inter-RAT Handover ......................................................................................................... 252
UMTS to GSM Multimedia Fallback ........................................................................................................ 254
NACC and PS Handover .......................................................................................................................... 256
UMTS to GSM Handover Retry ............................................................................................................... 261
Signaling Procedures for Inter-RAT Handover ................................................................................................. 265
WCDMA LOAD CONTROL ALGORITHM AND PARAMETERS .................................................................................. 270
Load Control Overview ................................................................................................................................... 272
Load Measurement .................................................................................................................................... 275
Priorities Involved in Load Control .............................................................................................................. 280
PUC (Potential User Control ........................................................................................................................... 286
LDB (Intra-Frequency Load Balancing.............................................................................................................. 297
CAC (Call Admission Control) .......................................................................................................................... 302
IAC (Intelligent Access Control) ....................................................................................................................... 342
LDR (Load Reshuffling) ................................................................................................................................... 393
OLC (Overload Control) .................................................................................................................................. 423
Abbreviations................................................................................................................................................. 444
WCDMA UE BEHAVIORS IN IDLE MODE
Foreword
UE behaviors in idle mode include:

PLMN selection
System information reception
Cell selection and reselection
Location registration
Paging procedure
Access procedure
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.
PLMN selection
Used to ensure that the PLMN selected by the UE provides services properly.
System information reception
The network broadcasts the network information to the UE that camps on the cell. Upon reception of broadcast
information, the UE obtains the network information and takes actions accordingly.
Cell selection and reselection
Used to ensure that the UE finds a suitable cell to camp on.
Location registration
This procedure is used by the UE to report its status to the network. This procedure is of two types: periodical
location registration and the location registration necessitated by changes in the location area.
Paging procedure
Used for the network to send paging messages to a UE which is in idle mode, CELL_PCH state, or URA_PCH
state.
Access procedure
From the view of access stratum, access is the procedure the UE shift from idle mode to connected mode.
References
3GPP TS 22.011: Service Accessibility
3GPP TS 23.122: NAS Functions Related to Mobile Station

(MS) in Idle Mode
3GPP TS 24.008: Mobile Radio Interface Layer 3 Specification;

Core Network Protocols - Stage 3
3GPP TS 25.304: UE Procedures in Idle Mode and Procedures

for Cell Reselection in Connected Mode
3GPP TS 25.331: Radio Resource Control (RRC)
3GPP TS 31.102: Characteristics of The USIM Application
Objectives
Upon completion of this course, you will be able to:

Describe the working principles of the UE Behaviors in Idle

Mode feature
Perform parameters modification of the UE Behaviors in Idle

Mode feature
PLMN Selection
Cell Search
UE does not have UTRAN carrier information:

In order to find a suitable cell to stay, UE will scan all the

frequencies in UTRAN. In each carrier, UE just need to find a
cell with best signal
UE has UTRAN carrier information:

UE will try whether the original cell is suitable to stay. If not,

UE still need to scan all the frequencies in UTRAN to find a
suitable cell in PLMN

Typical scenario of first occasion is the first time a new UE is put into use.
The second occasion is very common.
Cell Search (Cont.)

Slot synchronization
Frame synchronization and

code-group identification
Primary scrambling code

identification
Step 1: Slot synchronization

During the first step of the cell search procedure, the UE uses the primary synchronisation
code (PSC) to acquire slot synchronisation to a cell.
Step 2: Frame synchronization and code-group identification
During the second step of the cell search procedure, the UE uses the secondary
synchronisation code (SSC) to find frame synchronisation and identify the code group of the
cell found in the first step.
Step 3: Primary scrambling code identification
During the last step of the cell search procedure, the UE determines the exact primary
scrambling code used by the found cell. The primary scrambling code is typically identified
through symbol-by-symbol correlation over the CPICH with all codes within the code group
identified in the second step.
If the UE has received information about which scrambling codes to search for, steps 2 and 3
above can be simplified.
PLMN Selection
When the UE is switched on, or the coverage is restored, or the

UE selects a cell that belongs to another PLMN, then the UE
selects the registered PLMN or its equivalent PLMN
If no registered PLMN or equivalent PLMN is available, or if

registration fails, the UE performs one of the following two
procedures, depending on its operating mode:
Automatic PLMN selection: the UE automatically selects a PLMN

according to the priority order
Manual PLMN selection: the UE shows all available PLMNs to the

subscriber. The subscriber then selects a PLMN
The UE can get system information from PCCPCH, and the PLMN information is transmitted
in MIB of PCCPCH.
After getting the MIB, the UE can judge whether the current PLMN is right one. If so, the UE
will get SIB scheduling information from the MIB; if not, the UE will search another carrier,
do this procedure again.
The priority order of automatic PLMN selection mode:
PLMN Selection (Cont.)

Automatic PLMN selection: UE can select a PLMN from the

Home PLMNs (HPLMNs) and roam in the Visited PLMN (VPLMN)
Selecting from the HPLMNs: UE maintains a list of allowed and

available PLMNs in priority order. When selecting a PLMN, the UE
searches for the PLMNs from the highest priority to the lowest
Roaming in the VPLMN: UE periodically searches for the HPLMN
and higher priority PLMNs for better services
Manual PLMN selection: UE maintains a list of allowed and

available PLMNs in priority order. When selecting a PLMN, the
UE indicates the list to the subscriber who will select a PLMN,
and then camps on the selected PLMN

The MCC and MNC, which are in the PLMN identity of the HPLMN, match the MCC and
MNC in the IMSI of the UE.
Except the HPLMNs, the PLMNs that the UE camps on are defined as VPLMNs.
For the PLMN selection in the VPLMN, a value of T minutes may be stored in the SIM.
Either T is in the range 6 minutes to 8 hours with a step of 6 minutes or T indicates that no
periodic attempts shall be made. If no value is stored in the SIM, a default value of 60 minutes
is used.
When the UE attempts to access the HPLMN or the PLMN with higher priority, the UE must
adhere to the following rules:

After the UE is switched on, a period of at least two minutes and at most T minutes
shall elapse before the first attempt is made.

Periodic attempts shall be performed only by the UE in idle mode.

Only the priority levels of equivalent PLMNs of the same country (which serve as the
current serving VPLMN) can be compared with the priority level of a selected PLMN.
System Information Reception
Structure of System Information

System information is organized as a tree, including:

MIB (Master Information Block)
SB (Scheduling Block)
SIB (System Information Block)

System information is used for the network to broadcast network information to UEs camping
on a cell so as to control the behavior of UEs.
MIB

When selecting a new cell, the UE reads the MIB. The UE may locate the MIB by
predefined scheduling information. The IEs in the MIB includes MIB value tag,
PLMN type, PLMN identity, reference and scheduling information for a number of
SIBs in a cell or one or two SBs in a cell.
SB

Scheduling Block (SB) gives reference and scheduling information to other SIBs.
SIB

System Information Block (SIB) contains actual system information. It consists of
system information elements (IEs) with the same purpose.
Scheduling information for an SIB may only be included in either the MIB or one of the SB.
UE may use the scheduling information in the MIB and SB to locate each SIB to be acquired.
If UE received an SIB in a position according to the scheduling information and considers the
contents as valid, UE will read and store the SIB.
9
System Information

SIB1: contains the system information for NAS and the

timer/counter for UE
SIB2: contains the URA information
SIB3: contains the parameters for cell selection and cell reselection
SIB5: contains parameters for the common physical channels of
the cell
SIB7: contains the uplink interference level and the refreshing
timer for SIB7
SIB11: contains measurement controlling information

SIB4: contains parameters for cell selection and cell re-selection while UE is in connected
mode.
SIB6: contains parameters for the common physical channels of the cell while UE is in
connected mode.
SIB8: contains the CPCH static information.
SIB9: contains the CPCH dynamic information.
SIB10: contains information to be used by UEs having their DCH controlled by a DRAC
procedure. Used in FDD mode only. To be used in CELL_DCH state only. Changes so often,
its decoding is controlled by a timer.
SIB12: contains measurement controlling information in connecting mode.
SIB13: contains ANSI-41 system information.
SIB14: contains the information in TDD mode.
SIB15: contains the position service information.
SIB16: contains the needed pre-configuration information for handover from other RAT to
UTRAN.
SIB17: contains the configuration information for TDD.
SIB18: contains the PLMN identities of the neighboring cells.

To be used in shared networks to help with the cell reselection process.
10
Reception of System Information

The UE shall read system information broadcast on a BCH

transport channel when the UE is in idle mode or in
connected mode, that is, in CELL_FACH, CELL_PCH, or
URA_PCH state
11
Cell Selection and Reselection
Cell Selection
When the PLMN is selected and the UE is in idle mode,

the UE starts to select a cell to camp on and to obtain
services
There are four states involved in cell selection:

Camped normally
Any cell selection
Camped on any cell
Connected mode
Camped normally: The cell that UE camps on is called the suitable cell. In this state, the UE
obtains normal services.
Any cell selection: In this state, the UE shall attempt to find an acceptable cell of any PLMN
to camp on, trying all RATs that are supported by the UE and searching first for a high quality
cell.
Camped on any cell: The cell that UE camps on is called the acceptable cell. In this state the
UE obtains limited services. For example, UE may originate emergency call. The UE shall
regularly attempt to find a suitable cell of the selected PLMN, trying all RATs that are
supported by the UE.
Connected mode: After RRC connection setup, the UE changes from the idle mode to the
connected mode (CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH state).
Cell selection of the UE leaving the connected mode:

When returning to the idle mode from the connected mode, the UE shall select a
suitable cell to camp on. Candidate cells for this selection are the cells used
immediately before the UE leaves the connected mode.

When returning to the idle mode after an emergency call on any PLMN, the UE shall
select an acceptable cell to camp on. Candidate cells for this selection are the cells
used immediately before the UE leaves the connected mode.

If no acceptable cell is found, the UE shall continue to search for an acceptable cell on
any PLMN in the state "Any cell selection".
12
13
Cell Selection (Cont.)

Two types of cell selection:

Initial cell selection

If no cell information is stored for the PLMN, the UE starts this

procedure
Stored information of cell selection

If cell information is stored for the PLMN, the UE starts this

procedure
Initial cell selection: If no cell information is stored for the PLMN, the UE starts the initial
cell selection. For this procedure, the UE need not know in advance which Radio Frequency
(RF) channels are UTRA bearers. The UE scans all RF channels in the UTRA band according
to its capabilities to find a suitable cell of the selected PLMN. On each carrier, the UE need
only search for the strongest cell. Once a suitable cell is found, this cell shall be selected.
Stored information of cell selection: For this procedure, the UE has to know the central
frequency information and other optional cell parameters that are obtained from the
measurement control information received before, such as scrambling codes. After this
procedure is started, the UE selects a suitable cell if any. Otherwise, the "Initial cell selection"
procedure is triggered.
14
Cell Selection Criteria

Criterion S is used by the UE to judge whether the cell is

suitable to camped on
Criterion S: Srxlev > 0 & Squal > 0, where:
S qual = Qqualmeas Qqual min
S rxlev = Qrxlevmeas Qrxlev min Pcompensation
If the pilot strength and quality of one cell meet S criteria, UE will stay in this cell and get other system
information. Then, UE will initiate a location update registration process.
If the cell doesnt satisfy S criteria, UE will get adjacent cells information from SIB11. Then, UE will judge
weather these cells satisfy S criteria. If the adjacent cell is suitable, UE will stay in the adjacent cell.
If no cell satisfies S criteria, UE will take the area as dead zone and continue the PLMN selection and reselection
procedure.
15
Parameters of S Criterion
Qqualmin
Parameter name: Min quality level
Recommended value: -18, namely -18dB
Qrxlevmin
Parameter name: Min Rx level
Recommended value: -58, namely -115dBm
Qqualmin

Content: The minimum required quality level corresponding to CPICH Ec/No. The UE
can camp on the cell only when the measured CPICH Ec/No is greater than the value
of this parameter.

Value range: -24~0

Physical value range: -24~0; step: 1

Physical unit: dB

Set this parameter through ADD UCELLSELRESEL, query it through LST
UCELLSELRESEL, and modify it through MOD UCELLSELRESEL.
Qrelevmin

Content: The minimum required RX level corresponding to CPICH RSCP. The UE
can camp on the cell only when the measured CPICH RSCP is greater than the value
of this parameter.

Value range: -58~-13

Physical value range: -115~-25; step: 2 (-58: -115, -57: -113, ..., -13 :-25)

Physical unit: dBm

16
Parameters of S Criterion (Cont.)

MaxAllowedUlTxPower
Parameter name: Max allowed UE UL TX power
Recommended value: 24, namely 24dBm
MaxAllowedUlTxPower

Content: The maximum allowed uplink transmit power of a UE in the cell, which is
related to the network planning.

Value range: -50~33


Physical unit: dBm

17
Cell Reselection
The signal strength of both serving cell and neighboring

cells varies with the movement of a UE and so the UE
needs to select the most suitable cell to camp on. This
process is called cell reselection
Cell reselection process:

Measurement start criteria
Cell reselection criteria
Measurement Start Criteria

Intra-frequency measurement:
Squal Sintrasearch
Qqualmeas Qqualmin Sintrasearch
Qqualmeas Qqualmin + Sintrasearch
18

If Squal > Sintrasearch, the UE need not start the intra-frequency measurement.
If Squal Sintrasearch, the UE need to start the intra-frequency measurement.
If system messages do not contain Sintrasearch, the UE always need to start the intra-frequency
measurement.
Parameters of the measurement start criteria:
Measurement Start Criteria (Cont.)

Inter-frequency measurement:
Squal Sintersearch
Qqualmeas Qqualmin Sintersearch
Qqualmeas Qqualmin + Sintersearch

If Squal > Sintersearch, the UE need not start the inter-frequency measurement.
If Squal Sintersearch, the UE need to start the inter-frequency measurement.
If system messages do not contain Sintersearch, the UE always need to start the inter-frequency
measurement.
19
Measurement Start Criteria (Cont.)

Inter-RAT measurement:
Squal SsearchRATm
Qqualmeas Qqualmin SsearchRATm
Qqualmeas Qqualmin + SsearchRATm

If Squal > SsearchRATm, the UE need not start the inter-RAT measurement.
If Squal SsearchRATm, the UE need to start the inter-RAT measurement.
If system messages do not contain SsearchRATm, the UE always need to start the inter-RAT
measurement.
Parameters of Measurement Start Criteria

IdleSintrasearch
Parameter name: Intra-freq cell reselection threshold for

idle mode
Recommended value: 127, namely none
ConnSintrasearch
Parameter name: Intra-freq cell reselection threshold for

connected mode
IdleSintrasearch
20
Content: A threshold for intra-frequency cell reselection in idle mode. When the quality (CPICH Ec/No
measured by UE) of the serving cell is lower than this threshold plus the [Qqualmin] of the cell, the
intra-frequency cell reselection procedure will be started. This parameter is not configured when its
value is 127.

Value range: {{-16~10}, {127}}


Physical unit: dB

Set this parameter through ADD UCELLSELRESEL, query it through LST UCELLSELRESEL, and
modify it through MOD UCELLSELRESEL.
ConnSintrasearch

Content: A threshold for intra-frequency cell reselection in connect mode. When the quality (CPICH
Ec/No measured by UE) of the serving cell is lower than this threshold plus the [Qqualmin] of the cell,
the intra-frequency cell reselection procedure will be started. This parameter is not configured when its
value is 127.

Value range: {{-16~10}, {127}}


Physical unit: dB


(Cont.)
IdleSintersearch
Parameter name: Inter-freq cell reselection threshold for

idle mode
ConnSintersearch
Parameter name: Inter-freq cell reselection threshold for

connected mode
IdleSintersearch

Content: A threshold for inter-frequency cell reselection in idle mode. When the quality (CPICH Ec/No
measured by UE) of the serving cell is lower than this threshold plus the [Qqualmin] of the cell, the
inter-frequency cell reselection procedure will be started. This parameter is not configured when its
value is 127.

Value range: {{-16~10}, {127}}


Physical unit: dB
21
ConnSintersearch

Content: A threshold for inter-frequency cell reselection in connect mode. When the quality (CPICH
Ec/No measured by UE) of the serving cell is lower than this threshold plus the [Qqualmin] of the cell,
the inter-frequency cell reselection procedure will be started. This parameter is not configured when its
value is 127.

Value range: {{-16~10}, {127}}


Physical unit: dB


(Cont.)
SsearchRat
Parameter name: Inter-RAT cell reselection threshold
SearchRat

Content: A threshold for inter-RAT cell reselection. When the quality (CPICH Ec/No measured by UE)
of the serving cell is lower than this threshold plus the [Qqualmin] of the cell, the inter-RAT cell
reselection procedure will be started. This parameter is not configured when its value is 127.

Value range: {{-16~10}, {127}}


Physical unit: dB

22
Measurement Start Criteria Description
The intra-frequency, inter-frequency, and inter-RAT measurement criteria are as shown in the above
figure.
The intra-frequency cell reselection has a priority higher than the inter-frequency cell reselection and
inter-RAT cell reselection, the intra-frequency cell reselection start threshold should be higher than the
inter-frequency cell reselection start threshold and inter-RAT cell reselection start threshold.
If the cell reselection threshold is set to a comparatively high value, the UE may frequently start cell
reselections, and the battery of the UE may be largely consumed. If the cell reselection threshold is set
to a comparatively low value, it is difficult for cell reselections to be started, and the UE may not
timely reside in the cells with good quality, affecting the quality of communication between the
UTRAN and the UE. For detailed information, refer to 3GPP TS 25.304.
23
Cell Reselection Criteria

Criterion R is used for intra-frequency, inter-frequency

and inter-RAT cell reselection
The cell-ranking criterion R is defined by:
Rs = Qmeas, s + Qhysts
Rn = Qmeas,n Qoffsets ,n

In Rs, s means serving cell. In Rn, n means neighbor cell.

The offset Qoffset1s,n is used for Qoffsets,n to calculate Rn. The hysteresis Qhyst1s is used
for Qhysts to calculate Rs.
The UE shall rank the cells according to the R criterion, derive Qmeas,n and Qmeas,s and
calculate the R values, as described in the following cases:

If a TDD or GSM cell is ranked as the best cell, the UE shall reselect that TDD or
GSM cell.

If an FDD cell is ranked as the best cell and the quality measure for cell selection and
reselection is set to CPICH RSCP (QualMeas = CPICH_RSCP), the UE shall reselect
that FDD cell.

If an FDD cell is ranked as the best cell and the quality measure for cell selection and
reselection is set to CPICH Ec/N0 (QualMeas = CPICH_ECNO), the UE shall
perform a second ranking of the FDD cells according to the R criteria specified above.
In this case, however, the UE uses the measurement quantity CPICH Ec/N0 for
deriving the Qmeas,n and Qmeas,s and then calculating the R values of the FDD cells.
The offset Qoffset2s,n is used for Qoffsets,n to calculate Rn, the hysteresis Qhyst2s is
used for Qhysts to calculate Rs.
24
Hysteresis and Time Interval

Quality
Qhyst,s
Qmeas,n
Rn
Rs
Qoffsets,n
Qmeas,s
Time
Treselection
In all the previous cases, the UE can reselect a new cell only when the following conditions
are met:

The new cell is better ranked than the serving cell during a time interval Treselections.

More than one second has elapsed since the UE camped on the current serving cell.
25
Parameters of R Criteria
QualMeas
Parameter name: Cell Sel-reselection quality measure
Recommended value: CPICH_ECNO
Treselections
Parameter name: Reselection delay time
Recommended value: 1, namely 1s
QualMeas

Content: Measurement quantity of cell selection and reselection. It can be set to CPICH Ec/N0 or
CPICH RSCP.

Value range: CPICH_ECNO(CPICH Ec/N0), CPICH_RSCP(CPICH RSCP)

Physical value range: CPICH_ECNO, CPICH_RSCP

Physical unit: None

Treselections

Content: If the signal quality of a neighboring cell is better than that of the serving cell during the
specified time of this parameter, the UE reselects the neighboring cell. It is used to avoid ping-pong
reselection between different cells.

Value range: 0~31

Physical value range: 0~31; step: 1

Physical unit: s

26
Parameters of R Criteria (Cont.)

IdleQhyst1s
Parameter name: Hysteresis 1 for idle mode
Recommended value: 2, namely 4dB
ConnQhyst1s
Parameter name: Hysteresis 1 for connected mode
IdleQhyst1s

Content: The hysteresis value of the serving FDD cells in idle mode in case the quality measurement for
cell selection and reselection is set to CPICH RSCP. It is related to the slow fading feature of the area
where the cell is located. The greater the slow fading variance is, the greater this parameter.

Value range: 0~20


Physical unit: dB

ConnQhyst1s

Content: The hysteresis value of the serving FDD cells in connected mode in case the quality
measurement for cell selection and reselection is set to CPICH RSCP. It is related to the slow fading
feature of the area where the cell is located. The greater the slow fading variance is, the greater this
parameter .

Value range: 0~20


Physical unit: dB

27

IdleQhyst2s
Parameter name: Hysteresis 2 for idle mode
ConnQhyst2s
Parameter name: Hysteresis 2 for connected mode
IdleQhyst2s

Content: The hysteresis value of the serving FDD cells in idle mode in case the quality measurement for
cell selection and reselection is set to CPICH Ec/No. It is related to the slow fading feature of the area
where the cell is located. The greater the slow fading variance is, the greater this parameter.

Value range: {{0~20}, {255}}


Physical unit: dB

ConnQhyst2s

Content: The hysteresis value of the serving FDD cells in connected mode in case the quality
measurement for cell selection and reselection is set to CPICH Ec/No. It is related to the slow fading
feature of the area where the cell is located. The greater the slow fading variance is, the greater this
parameter.

Value range: {{0~20}, {255}}


Physical unit: dB

28

IdleQoffset1sn
Parameter name: IdleQoffset1sn
ConnQoffset1sn
Parameter name: ConnQoffset1sn
IdleQoffset1sn

Content: Offset of cell CPICH RSCP measurement value in cell selection or reselection when the UE is
in idle mode.

Value range: -50~+50

Physical value range: -50~+50; step: 1

Physical unit: dB

Set this parameter through ADD UINTRAFREQNCELL / ADD UINTERFREQNCELL, query it
through LST UINTRAFREQNCELL / LST UINTERFREQNCELL, and modify it through MOD
UINTRAFREQNCELL / MOD UINTERFREQNCELL.
ConnQoffset1sn

Content: Offset of cell CPICH RSCP measurement value in cell selection or reselection when the UE is
in connected mode.



Physical unit: dB

29

IdleQoffset2sn
Parameter name: IdleQoffset2sn
ConnQoffset2sn
Parameter name: ConnQoffset2sn
IdleQoffset2sn

Content: Offset of cell CPICH Ec/No measurement value in cell selection or reselection when the UE is
in idle mode.



Physical unit: dB

ConnQoffset2sn

Content: Offset of cell CPICH Ec/No measurement value in cell selection or reselection when the UE is
in connected mode.



Physical unit: dB

30
Location Registration
Location Registration
The location registration includes:

Location update (for non-GPRS)
Route update (for GPRS)
The types of location registration:

Normal location registration
Periodic location registration
IMSI attach/detach
Location registration is used for the PLMN to trace the current status of the UE. Location
registration ensures that the UE is connected to the network when the UE does not perform
any operation for a long period.
The UE performs normal location registration in the following conditions:

After being switched on, the UE selects a suitable cell that belongs to a new LA or RA.
That is, the LA or RA is different from that recorded in the USIM before the switchoff of the UE.

The UE in idle mode enters the cell of a new LA or RA.
31
Periodic Location Registration

Periodic location registration is controlled by a Periodic

Location Update timer (T3212, for non-GPRS operation)
or a Periodic Routing Area Update timer (T3312, for
GPRS operation)
T3212 is set through T3212 on the RNC side
T3312 is set on the CN side
Periodic location registration may be used to periodically notify the network of the availability of the
UE.
The value of T3212 is sent by the network to the UE in SIB1. The value of T3312 is sent by the
network to the UE in the messages ATTACH ACCEPT and ROUTING AREA UPDATE ACCEPT.
The value of T3312 shall be unique within an RA.
IMSI Attach/Detach
The IMSI attach/detach process facilitates the fast

location registration of the UE in specific conditions
IMSI attach/detach is set through ATT on the RNC side
If the UE still stays in the same LA or RA after being switched on again, the UE shall perform an LR
request indicating IMSI attach. Otherwise, the UE shall perform an LR request indicating normal
location update.
32
When the IMSI attach/detach operation applies, the UE shall send the IMSI detach message to the
network when the UE is switched off or the SIM is removed while being in the UPDATED state. This
IMSI detach message will not be acknowledged by the network.
The system information contains an indicator indicating whether the IMSI attach/detach operation is
mandatory in the cell. The UE shall operate in accordance with the received value of the indicator.
Parameters of Location Registration

T3212
Parameter name: Periodical location update timer [6min]
Recommended value: 10, namely 60min
ATT
Parameter name: Attach/detach indication
Recommended value: ALLOWED
T3212

Content: This parameter indicates the time length of the periodical location update. Periodical location
update is implemented by MS through the location update procedure. 0: The periodical update
procedure is not used. This parameter is valid only when [CN domain ID] is set as CS_DOMAIN.
Value range: 0~255
Physical unit: min
Set this parameter through ADD UCNDOMAIN, query it through LST UCNDOMAIN, modify it
through MOD UCNDOMAIN.
ATT

Content: Indicating whether attach/detach is allowed. NOT_ALLOWED indicates that MS cannot apply
the IMSI attach/detach procedure. ALLOWED indicates that MS can apply the IMSI attach/detach
procedure. This parameter is valid only when [CN domain ID] is set as CS_DOMAIN.
Value range: NOT_ALLOWED, ALLOWED
Physical value range: NOT_ALLOWED, ALLOWED
Physical unit: None
Set this parameter through ADD UCNDOMAIN, query it through LST UCNDOMAIN, modify it
33
Paging Procedure
Paging Initiation
CN initiated paging:
Establish a signaling connection
UTRAN initiated paging:

Trigger the cell update procedure
Trigger reading of updated system information
For CN originated paging:

In order to request UTRAN connect to UE, CN initiates the paging procedure, transmits
paging message to the UTRAN through Iu interface, and UTRAN transmits the paging
message from CN to UE through the paging procedure on Uu interface, which will make the
UE initiate a signaling connection setup process with the CN.
For UTRAN originated paging:

UE state transition: In order to trigger UE in the CELL_PCH or URA_PCH state to carry out
state transition (for example, transition to the CELL_FACH state), the UTRAN will perform a
paging process. Meanwhile, the UE will initiate a cell update or URA update process, as a
reply to the paging.

When the cell system message is updated: When system messages change, the UTRAN will
trigger paging process in order to inform UE in the idle, CELL_PCH or URA_PCH state to
carry out the system message update, so that the UE can read the updated system message.
34
Paging Type 1
If UE is in the idle or CELL/URA_PCH state, the paging

message will be transmitted on PCCH with paging type 1
CN
RNC1
RNC2
NODEB1.1
NODEB2.1
UE
PAGING
RANAP
RANAP
RANAP
PAGING
RANAP
PCCH: PAGING TYPE 1
PCCH: PAGING TYPE 1
Paging type 1:

The message is transmitted in one LA or RA for idle state, or in one cell for
CELL_PCH state, or in one URA for URA_PCH state.

After calculating the paging time, the paging message will be transmitted at that time.

If UE is in CELL_PCH or URA_PCH state, the UTRAN transmits the paging
information in PAGING TYPE 1 message to UE. After received paging message, UE
performs a cell update or URA update procedure to transit state to CELL_FACH.
As shown in the above figure, the CN initiates paging in a location area (LA), which is
covered by two RNCs. After receiving a paging message, the RNC searches all the cells
corresponding to the LAI, and then calculates the paging time, at which it will send the
PAGING TYPE 1 message to these cells through the PCCH.
35
Paging Type 2
If UE is in CELL_DCH or CELL_FACH state, the paging

message will be transmitted on DCCH with paging type 2
CN
SRNC
UE
PAGING
RANAP
RANAP
DCCH: PAGING TYPE 2

RRC
RRC
Paging type 2:

If UE is in CELL_DCH or CELL_FACH statethe paging message will be transmitted on
DCCH with paging type 2.

The message will be only transmitted in a cell.
As shown in the above figure, if the UE is in the CELL_DCH or CELL_FACH state, the UTRAN will
immediately transmit PAGING TYPE 2 message to the paged UE on DCCH channel.
36
Typical Call Flow of UE

NSS
UE AS
UE N AS
pa ging
R R _ P A IN G _ IN D
RA NA P
M SC
pa ging
R AN AP
R R _ E S T _ R E Q (P A G IN G R E S P O N S E )
R R C se tu p pro ces s
IN ITIA L_ D IR E C T _T R A N S FE R
A U T H E N T IC A T IO N
R EQ U ES T
A U T H E N T IC A T IO N
R ES PO N SE
(P A G IN G R E S P O N S E )
R R _ S E C U R IT Y _C O N T R O L _R E Q
( IK C K )
S ecu rity m o d e c on trol

S ETUP
C A L L C O N F IR M
R A B se tup p ro ce ss
ALER T
C O NN E CT
C O N NE CT AC KN O W LED G E
Many problems will cause the target UE cannot receive the paging message properly:

Power setting of paging channel is unreasonable

Unreasonable paging strategies will result in paging channel congestion, which can
cause paging message loss

Paging parameter is unreasonable

Equipment fault
37
DRX Procedure
To reduce power consumption, the UE can read the

information from the PICH only at a particular time. This
is known as the Discontinuous Reception (DRX)
technology. The interval between two consecutive
periods of time is called DRX cycle
The value for the DRX paging cycle length is determined

as follows:
DRX Cycle Length MAX (2k, PBP) frames
The DRX paging period formula:

DRX Cycle Length MAX(2k, PBP) frames

K is the CN domain specific DRX cycle length coefficient, which is broadcasted in SIB1.
The typical value is 6.

PBP is Paging Block Periodicity , which is 1 for FDD mode.

The paging period should be 640ms if K is 6.
38
DRX Procedure (Cont.)

The value of the Paging Occasion is determined as

follows:
Paging Occasion (CELL SFN) =

{(IMSI div K) mod (DRX cycle length div PBP)} * PBP
+ n * DRX cycle length + Frame Offset
Paging SFN formula:

Paging Occasion (CELL SFN) = {(IMSI div K) mod (DRX cycle length div PBP)}
*PBP + n *DRX cycle length + Frame Offset

n =0, 1, 2and the requirement is the calculated CELL SFN must be below its
maximum value 4095.

Frame Offset is 0 for FDD mode.

K is the number of SCCPCH which carries PCH, and the typical value is 1.

The formula cloud be simplified as: SFN = IMSI mod (2^K) + n * (2^K).
39

In FDD the UE shall monitor its paging indicator in the

PICH frame with SFN given by the Paging Occasion
The Paging Indicator to use is calculated by using the

following formula:
PI = (IMSI div 8192) mod NP
As shown in the below figure, the UE needs to monitor the frames (paging occasions) indicated by the
red dots, and then decodes the qth PI of this frame. (The qth PI is obtained based on the above
formula).
If the UE has no IMSI, for instance when making an emergency call without USIM, the UE shall use
as default numbers, IMSI = 0 and DRX cycle length = 256 (2.56 s), in the formulas above.
40

Through DRX, UE only listens to PICH at certain

predefined time. And UE will read the paging information
on SCCPCH if the paging indicator is 1
Time offset between PICH and SCCPCH:
PICH frame containing paging indicator
Associated S-CCPCH frame

PICH
The timing relationship between PICH and SCCPCH is defined by the above figure, and the interval is
3 slots duration (2ms, 7680 chips).
Parameters of DRX
DRXCyclelenCoef
Parameter name: DRX cycle length coefficient
Recommended value: 6
PICHMode
Parameter name: PICH mode
Recommend value: V36
41
DRXCyclelenCoef

Content: This parameter is broadcasted on SIB1. This parameter is used when a UE is in idle mode.

Value range: 6~9

Physical value range: 6~9

Physical unit: None

Set this parameter through ADD UCNDOMAIN, query it through LST UCNDOMAIN, and modify it
PICHMode

Content: Indicating the number of PIs contained in each frame on the PICH.

Value range: V18, V36, V72, V144

Physical value range: 18, 36, 72, 144

Physical unit: None

Set this parameter through ADD UPICH, query it through LST UPICH.
Parameters of DRX (Cont.)

MaccPageRepeatTimes
Parameter name: Repeat Times of Macc Paging
MaccPageRepeatTimes

Content: This parameter defines the times of retransmission of paging messages. If the times of
retransmission exceeds the value of this parameter, retransmission stops. For details, refer to the 3GPP
TS 25.331 protocol.

Value range: 0~2


Physical unit: None

Set this parameter through SET UDPUCFGDATA, query it through LST UDPUCFGDATA.
42
Access Procedure
Two Working Modes of UE

Idle mode:
After turning on, UE will stay in idle mode
Connected mode:
UE will switch to connected mode which could be

CELL_FACH state or CELL_DCH state from the idle mode
After releasing RRC connection, UE will switch to the idle

mode from the connected mode
The most important difference between idle mode and connected mode is whether UE has RRC connection with
UTRAN or not.
In idle mode, UE will be identified by IMSI, TMSI or PTMSI and so on.
In connected mode, UE will be identified by URNTI (UTRAN Radio Network Temporary Identity), which is the ID
of one RRC connection.
43
Random Access Procedure

Definition:
Random access procedure is initiated by UE in order to get

service from the system. Meanwhile, the access channels
are allocated to the UE by system
This process may happen in the following typical scenarios:

Attach and detach

LA update and RA update

Signaling connection for services
Random Access Channel
AICH access
slots
SFN mod 2 = 0
p-a
#0
PRACH
access slots
#0
#1
#2
#1
#3
#2
#4
#3
#5
#4
#6
SFN mod 2 = 1
#5
#6
#7
#8
#7
#9
Access slot set 1
#8
#9
#10
#11
#10
#11
#12
Access slot set 2
10 ms
10 ms
44
#13
#12
#14
#13
#14

UE will transmit the preamble at the access time slot.

Access frame is composed of two 10ms radio frames, which is divided into 15 access time slot, and 5120 chips
for each slot.
The PRACH access slots, AICH access slots and their time offset are showed in the above figure.
RACH Sub-Channels
The access slots of different RACH sub-channels are illustrated

by the following table:
SFN
mod 8
Random access sub-channels number

0
12 13 14
10 11
5
6
12 13
14
10
10 11
10 11
7
8
0
8
11 12 13 14
8
10 11 12 13 14
A RACH sub-channel defines a sub-set of the total set of uplink access slots. There are a total of 12 RACH subchannels.
Set Preamble signatures and RACH sub-channel no. through ADD UPRACHBASIC, query them through LST
UPRACH.
45
Access Service Class

The PRACH resources can be classified into several ASCs,

so as to provide RACH applications with different
priorities
For Frequency Division Duplex (FDD) mode, the PRACH resources include access timeslots
and preamble signatures, which can be classified into several ASCs, so as to provide RACH
applications with different priorities.
The ASCs range from 0 to 7, and the quantity of ASCs is 8. "0" indicates the highest priority
and "7" indicates the lowest priority.
Set ASC of PRACH through ADD UPRACHASC, modify it through MOD UPRACHASC,
and remove it through RMV UPRACHASC.
Access Control
Access Control is used by network operators to prevent

overload of radio access channels under critical
conditions
Access class 0 ~ Access Class 9
Access class 11 ~ Access Class 15
Access class 10

The access class number is stored in the SIM/USIM.

Access class 0~9 are allocated to all the users. And these 10 classes show the same priority.
Access class 11~15 are allocated to specific high priority users as follows. (The enumeration
is not meant as a priority sequence):

Access class 15: PLMN staff
46
Access class 14: users subscribing to emergency services

Access class 13: public organizations

Access class 12: users subscribing to security services

Access class 11: users responsible for PLMN management
Access Class 10 indicates whether or not network access for Emergency Calls is allowed for
UEs with access classes 0 to 9 or without an IMSI. For UEs with access classes 11 to 15,
Emergency Calls are not allowed if both "Access class 10" and the relevant Access Class (11
to 15) are barred. Otherwise, Emergency Calls are allowed.
Mapping between AC and ASC

The AC-ASC mapping information is optional and used

for the System Information Block 5 (SIB5) only
Set the mapping between AC and ASC through ADD UPRACHACTOASCMAP, modify it through MOD
UPRACHACTOASCMAP, and remove it through RMV UPRACHACTOASCMAP.
47
Random Access Procedure

START
Choose a RACH sub channel from
available ones
Get available signatures
Set Preamble Retrans Max
Set Preamble_Initial_Power
Send a preamble
Choose a access slot again
Choose a signature and

increase preamble transmit power
The counter of preamble retransmit
Subtract by 1, Commanded preamble power
increased by Power Ramp Step
Y
Counter > 0 & Commanded Preamble

power-maximum allowed power < 6
dB
N
Set physical status to be Nack
on AICH received
No AI
Check the corresponding AI
Get positive AI
Get negative AI
Change message part power by p

-m based on preamble power
Send the corresponding message part
Set physical status to be RACH

message transmitted
Set physical status to be Nack

on AICH received
Report the physical status to MAC
END
Random access procedure

1. Derive the available uplink access slots, in the next full access slot set, for the set of
available RACH sub-channels within the given ASC. Randomly select one access slot among
the ones previously determined. If there is no access slot available in the selected set,
randomly select one uplink access slot corresponding to the set of available RACH subchannels within the given ASC from the next access slot set. The random function shall be
such that each of the allowed selections is chosen with equal probability.

2. Randomly select a signature from the set of available signatures within the given ASC.

3. Set the Preamble Retransmission Counter to Preamble_ Retrans_ Max.

4. Set the preamble transmission power and Commanded Preamble Power to
Preamble_Initial_Power.
48
5. Transmit a preamble using the selected uplink access slot, signature, and preamble
transmission power.
6. If no positive or negative acquisition indicator (AI +1 nor 1) corresponding to the
selected signature is detected in the downlink access slot corresponding to the selected uplink
access slot:

A: select the next available access slot in the set of available RACH sub-channels
within the given ASC;

B: select a signature;

C: increase the preamble transmission power and Commanded Preamble Power by
Power Ramp Step, whereas the maximum value of preamble transmission power is
equal to MaxallowedUlTxPower.

D: Decrease the Preamble Retransmission Counter by one. If the Preamble
Retransmission Counter > 0 and Commanded Preamble Power maximum allowed
power < 6dB, then repeat from step 5. Otherwise exit the physical random access
procedure.
7. If a negative acquisition indicator corresponding to the selected signature is detected in the
downlink access slot corresponding to the selected uplink access slot, exit the physical random
access procedure.
8. If a positive acquisition indicator corresponding to the selected signature is detected, UE
transmits the random access message three or four uplink access slots after the uplink access
slot of the last transmitted preamble. After that, exit the physical random access procedure.
RRC Connection Message

Typical RRC connection messages:

RRC_CONNECTION_REQUEST
RRC_CONNECTION_SETUP
RRC_CONNECTION_SETUP_COMPLETE
RRC_CONNECTION_RELEASE
49
When a UE needs network service, it first sets up RRC connection as follows:

The UE sends a RRC CONNECTION REQUEST message from the cell where it camps to the RNC.

The RNC allocates related resources for the UE and sends an RRC CONNECTION SETUP message
to the UE.

The UE sends a RRC CONNECTION SETUP COMPLETE message to the RNC. The RRC
connection setup ends.
UE Timers and Constants in Idle Mode

T300
Parameter name: Timer 300 [ms]
Recommended value: D2000, namely 2s
N300
Parameter name: Constant 300
T300

Content: T300 is started when UE sends the RRC CONNECTION REQUEST message. It is stopped
when UE receives the RRC CONNECTION SETUP message. RRC CONNECTION REQUEST
will be resent upon the expiry of the timer if V300 is lower than or equal to N300, else enter idle mode.
Value range: D100, D200, D400, D600, D800, D1000, D1200, D1400, D1600, D1800, D2000, D3000,
D4000, D6000, D8000
Physical value range: 100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000,
8000
Physical unit: ms
Set this parameter through SET UIDLEMODETIMER, query it through LST UIDLEMODETIMER.
N300

Content: Maximum number of retransmissions of the RRC CONNECTION REQUEST message.

Value range: 0~7
Physical unit: None
50
UE Timers and Constants in Idle Mode

(Cont.)
T312
Parameter name: Timer 312 [s]
N312
Parameter name: Constant 312
Recommended value: D1, namely 1
T312

Content: T312 is started when UE starts to establish a DCH, and stopped when UE detects consecutive
N312 "in sync" indications from L1. It indicates physical channel setup failure upon the expiry of the
timer.
Value range: 1~15
Physical value range: 1~15s
Physical unit: s
N312

Content: Maximum number of successive "in sync" indications received from L1.
Value range: D1, D2, D4, D10, D20, D50, D100, D200, D400, D600, D800, D1000
Physical value range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000
Physical unit: None
51
RRC Connection Establish Channel

Type and Bit Rate
RrcCause
Parameter name: Cause of RRC connection establishment
Recommended value: refer to next page
SigChType
Parameter name: Channel type for RRC establishment
RrcCause

Content: This parameter specifies the cause of RRC connection establishment, that is, the value of the
Establishment cause IE in the RRC CONNECTION REQUEST message.

Value range: ORIGCONVCALLEST, ORIGSTREAMCALLEST, ORIGINTERCALLEST,
ORIGBKGCALLEST, ORIGSUBSTRAFFCALLEST, TERMCONVCALLEST,
TERMSTREAMCALLEST, TERMINTERCALLEST, TERMBKGCALLEST, EMERGCALLEST,
INTERRATCELLRESELEST, INTERRATCELLCHGORDEREST, REGISTEST, DETACHEST,
ORIGHIGHPRIORSIGEST, ORIGLOWPRIORSIGEST, CALLREEST, TERMHIGHPRIORSIGEST,
TERMLOWPRIORSIGEST, TERMCAUSEUNKNOWN, MBMSCALLEST, DEFAULTEST

Set this parameter through SET URRCESTCAUSE, query it through LST URRCESTCAUSE.
SigChType

Content: This parameter specifies the channel type and bit rate for RRC connection establishment.

Value range: FACH, DCH_3.4K_SIGNALLING, DCH_6.8K_SIGNALLING,
DCH_13.6K_SIGNALLING, DCH_27.2K_SIGNALLING

FACH: The RRC connection is set up on the common channel.

DCH_3.4K_SIGNALLING: The RRC connection is set up on the 3.4 kbit/s dedicated channel.

DCH_6.8K_SIGNALLING: The RRC connection is set up on the 6.8 kbit/s dedicated channel.

DCH_13.6K_SIGNALLING: The RRC connection is set up on the 13.6 kbit/s dedicated
channel.

DCH_27.2K_SIGNALLING: The RRC connection is set up on the 27.2 kbit/s dedicated
channel.

Set this parameter through SET URRCESTCAUSE, query it through LST URRCESTCAUSE.
52
RRC Connection Establish Channel

Type and Bit Rate
EFachSwitch
Parameter name: switch for RRC established on E_FACH
EFachSwitch
Content: This parameter specifies whether the RRC connection is established preferentially on the E-
FACH. If this parameter is set to ON and both the UE and the serving cell support E-FACH, then the
RRC connection is established preferentially on the E-FACH, regardless of the setting of SigChType.
According to the related protocols, the UE cannot transmit signals over the FACH if both the UE and
the cell support E-FACH. Thus, if this parameter is set to OFF and both the UE and the serving cell
support E-FACH, then the RRC connection can only be established on the non-FACH, even if the
SigChType is set to FACH. Otherwise, the RRC connection is established on the corresponding channel
according to the setting of SigChType
Value range: OFF, ON
Set this parameter through SET URRCESTCAUSE, query it through LST

URRCESTCAUSE.
53
54
WCDMA POWER CONTROL ALGORITHM AND PARAMETERS
Foreword
Power control categories:

Uplink power control
Downlink power control
Power control types:

Open loop power control
Closed loop power control

Inner loop power control
Outer loop power control
The WCDMA system is an interference-limited system, and the most important way to restrain
system interference is power control. The core purpose of power control is to minimized the
power of transmitting signals while ensuring Quality of Service (QoS).
In the uplink, a UE emitting too high power will cause unacceptable competing interference on
the NodeB in comparison to signals coming from UEs at the cell edge. This is called near-far
effect. To avoid near-far effect, uplink power control is required.
In the downlink, the system capacity is determined by the total code power. Therefore, it is
necessary to keep the transmit power at the lowest possible level while still ensuring signal
quality at the UE.
At open loop power control, the initial transmit power is calculated. This method is rather
inaccurate and it is only applied at the beginning of a connection setup.
At closed loop power control, the transmitter dynamically adjusts its transmit power according
to the feedback from the receiver of the other side. Closed loop power control is further
classified into the following types:
Inner loop power control directly adjusts the transmit power of the transmitter by using power
control commands.
Outer loop power control indirectly controls the transmit power of the transmitter.
55
References
3GPP TS 25.211: Physical Channels and Mapping of

Transport Channels onto Physical Channels (FDD)
3GPP TS 25.214: Physical Layer Procedures (FDD)
3GPP TS 25.331: RRC Protocol Specification
3GPP TS 25.433: UTRAN Iub Interface NodeB

Application Part (NBAP) Signaling
Objectives

Describe the purpose and function of power control
Perform parameters modification of open loop power

control
Perform parameters modification of inner loop power

control
Perform parameters modification of outer loop power

control
56
Power Control Overview
Purpose of Uplink Power Control

Uplink transmission character:

Self-interference system
Uplink capacity is limited by interference level
Near-far effect
Fading
Uplink power control function:

Ensure uplink quality with minimum transmission power
Decrease interference to other UE, and increase capacity
Solve the near-far effect
Save UE transmission power
CDMA system have the embedded characteristics of self-interference, for uplink one users
transmission power become interference to others.
The more connected users, the higher interference. Generally the capacity is limited by
interference level.
WCDMA suffer from Near-far effect, which means if all UE use the same transmission power,
the one close to the NodeB may block the entire cell.
Uplink power control can guarantee the service quality and minimize the required transmission
power. It will resolve the near-far effect and resist fading of signal propagation. By lowering the
uplink interference level, the system capacity will be increased.
57
Purpose of Downlink Power Control

Downlink transmission character:

Interference among different subscribers
Interference from other adjacent cells
Downlink capacity is limited by NodeB transmission power
Fading
Downlink power control function:

Ensure downlink quality with minimum transmission power
Decrease interference to other cells, and increase capacity
Save NodeB transmission power
The downlink has different characteristics from the uplink, for downlink interference is caused
by multi-path, part of one users power also become interference to others.
Downlink power from adjacent cells also is one part of interference to the own cell.
Transmission power of NodeB is shared by all users channels, so downlink capacity usually is
considered to be limited by transmission power.
Downlink power control also can guarantee the service quality and minimize the required
transmission power, so the capacity is maximized in case that interference is lowered.
58
Effect of Power Control

20
Channel Fading
15
Transmitting power
Receiving power
Relative power (dB)
10
0
-5
-10
-15
-20
0
200
400
600
800
Time (ms)
Because of channel fading in mobile communication system, the radio signal is deteriorated and
fluctuated, the fast power control become one key technology to resist this phenomenon.
In this figure, the channel fading is compensated by the transmitting power, which is adjusted
by the fast power control, so the receiving power is almost constant and the radio propagation
condition is improved.
59
Power Control Classification

Open loop power control:

Uplink/Downlink open loop power control
Closed loop power control:

Uplink/Downlink inner loop power control
Uplink/Downlink outer loop power control
In WCDMA system, power control includes open loop and closed loop power control.
Open loop power control is used to determine the initial transmission power, and the closed
loop power control adjusts the transmission power dynamically and continuously during the
connection.
For uplink, the UEs transmission power is adjusted; and for downlink, the NodeBs
transmission power is adjusted.
60
Power Control for Physical Channels

Power control methods are adopted for these physical

channels:
" : can be applied; : canClosed

not be
applied
Loop
Power Control
Physical
Channel
Open Loop
Power
Control
Inner Loop Power

Control
Outer Loop
Power Control
DPDCH
DPCCH
SCH
PCCPCH
SCCPCH
PRACH
AICH
PICH
Open loop power control is used in two cases:

1. to decide the initial transmission power of PRACH;
2. to decide the initial transmission power of DPCCH / DPDCH.
Closed loop power control is only applied on DPCCH and DPDCH.
For other common channels, power control is not applied, they will use fixed transmission
power:
The PCPICH power is defined by the PCPICHPower parameter as an absolute value in dBm.
All other common channels power is defined in relation with the PCPICHPower parameter,
and measured in dB.
61
Common Physical Channel Power

Parameters
MaxTxPower
Parameter name: Max transmit power of cell [0.1dBm]
PCPICHPower
Parameter name: PCPICH transmit power [0.1dBm]
MaxTxPower
Content: The sum of the maximum transmit power of all DL channels in a cell.
Value range: 0 to 500
Physical value range: 0 to 50; step: 0.1
Physical unit: dBm
Set this parameter through ADD UCELLSETUP and modify it through MOD UCELL.
PCPICHPower
Content: This parameter should be set based on the actual environment and the downlink coverage should be
guaranteed firstly. If PCPICH transmit power is configured too great, the cell capacity will be decreased, for power
resources is occupied by common channel and the interference to traffic channels is also increased.
Value range: -100 to 500
Physical value range: -10 to 50; step: 0.1
Physical unit: dBm
Set this parameter through ADD UPCPICH, query it through LST UPCPICH and modify it through MOD UCELL.
62

Parameters (Cont.)
PSCHPower and SSCHPower

Parameter name: PSCH / SSCH transmit power [0.1dB]
BCHPower
Parameter name: BCH transmit power [0.1dB]
PSCHPower and SSCHPower

Content: The offset of the PSCH/SSCH transmit power from the PCPICH transmit power in a cell .
Physical unit: dB
For PSCH Power, set it through ADD UPSCH, and query it through LST UPSCH; for SSCH Power, set it through
ADD USSCH, and query it through LST USSCH. And modify them through MOD UCELL.
BCHPower
Content: The offset of the BCH transmit power from the PCPICH transmit power in a cell.
Physical unit: dB
Set this parameter through ADD UBCH, query it through LST UBCH, and modify it through MOD UCELL.
63

Parameters (Cont.)
MaxFachPower
Parameter name: Max transmit power of FACH [0.1dB]
PCHPower
Parameter name: PCH transmit power [0.1dB]
MaxFachPower
Content: The offset between the FACH transmit power and PCPICH transmit power in a cell.
Physical unit: dB
Set this parameter through ADD UFACH, query it through LST UFACH.
PCHPower
Content: The Offset of the PCH transmit power from the PCPICH transmit power in a cell.
Physical unit: dB
Set this parameter through ADD UPCH, query it through LST UPCH, and modify it through MOD USCCPCH.
64

Parameters (Cont.)
AICHPowerOffset
Parameter name: AICH power offset
PICHPowerOffset
Parameter name: PICH power offset
AICHPowerOffset
Content: The difference between the transmit power of AICH and that of PCPICH.
Physical value range: -22 to 5; step: 1
Physical unit: dB
Set this parameter through ADD UCHPWROFFSET, query it through LST UCHPWROFFSET, and modify it
through MOD UAICHPWROFFSET.
PICHPowerOffset
Content: The difference between the transmit power of PICH and that of PCPICH.
Physical unit: dB
Set this parameter through ADD UCHPWROFFSET, query it through LST UCHPWROFFSET, and modify it
through MOD UPICHPWROFFSET.
65
Open Loop Power Control
Open Loop Power Control Overview
Open Loop Power Control Overview

Purpose
Calculate the initial transmission power of uplink / downlink

channels
Principle
Estimates the downlink signal power loss on propagation path
Path loss of the uplink channel is related to the downlink channel
Application
Open loop power control is applied only at the beginning of

connection setup to set the initial power value
In downlink open loop power control, the initial transmission power is calculated according to the downlink path
loss between NodeB and UE.
In uplink, since the uplink and downlink frequencies of WCDMA are in the same frequency band, a significant
correlation exists between the average path loss of the two links. This make it possible for each UE to calculate the
initial transmission power required in the uplink based on the downlink path loss.
However, there is 90MHz frequency interval between uplink and downlink frequencies, the fading between the
uplink and downlink is uncorrelated, so the open loop power control is not absolutely accurate.
66
PRACH Open Loop Power Control

NodeB
UE
SRNC
1. CCCH: RRC Connection Request
RRC
RRC
Open loop power

control of PRACH
Allocate RNTI
Select L1 and L2
parameters
2. Radio Link Setup Request
NBAP
NBAP
Start RX
description
3. Radio Link Setup Response
NBAP
NBAP
4. ALCAP Iub Data Transport Bearer Setup
DCH - FP
DCH - FP
5. Downlink Synchronization
6. Uplink Synchronization
DCH - FP
DCH - FP
Start TX
description
RRC
7. CCCH: RRC Connection Setup
RRC
8. Radio Link Restore Indication

NBAP
RRC
NBAP
9. DCCH: RRC Connection Setup Complete
RRC
In access procedure, the first signaling RRC CONNECTION REQUEST is transmitted in message part on
PRACH.
Before PRACH message part transmission, UE will transmit PRACH preamble, and the transmission power of first
preamble is calculated by this PRACH open loop power control.
67

When UE needs to set up a RRC connection, the initial
power of uplink PRACH preamble can be calculated

according to the following formula:
Preamble_I nitial_Pow er = PCPICHPowe r - CPICH_RSCP

+ UL interferen ce + Constantva lue
In this formula, where

PCPICHPower defines the PCPICH transmit power in a cell. It is broadcast in SIB5.
CPICH_RSCP means received signal code power, the received power measured on the PCPICH. The measurement
is performed by the UE.
UL interference is the UL RTWP measured by the NodeB. It is broadcast in SIB7.
Constantvalue compensates for the RACH processing gain. It is broadcast in SIB5.
The initial value of PRACH power is set through open loop power control. UE operation steps are as follows:
1. Read Primary CPICH DL TX power, UL interference and Constant value from system information;
2. Measure the value of CPICH_RSCP;
3. Calculate the Preamble_Initial_Power of PRACH.

Parameters
Constantvalue
Parameter name: Constant value for calculating initial TX

power
68
Constantvalue
Content: It is used to calculate the transmit power of the first preamble in the random access process.
Value range: -35 to -10
Physical value range: -35 to -10; step: 1
Physical unit: dB
Set this parameter through ADD UPRACHBASIC, query it through LST UPRACH, and modify it through MOD
UPRACHUUPARAS.
PRACH Open Loop Power Control (Cont.)

Timing relationship of PRACH and AICH:
1 access slot
Acq.
Ind.
AICH
p-a
PRACH
Preamble
Preamble
p-p
Message
part
p-m
After UE transmit the first Preamble on PRACH, it will wait for the corresponding AI (Acquisition Indicator) on
the AICH. The timing relationship of PRACH and AICH is shown in above figure.
There will be 3 parameters used to define the timing relationship:
p-p: time interval between two PRACH preambles. p-p is not a fixed value, it is decided by selecting access slot of
PRACH preambles.
Here p-p has one restriction, it must be longer than a minimum value p-p min, namely p-p p-p min.
p-a: time interval between PRACH preamble and AICH Acquisition Indicator. If UE sends the PRACH preamble,
it will detect the responding AI after p-a time.
p-m: time interval between PRACH preamble and PRACH message part. If UE sends the PRACH preamble and
receives positive AI from the AICH, it will send the message part after p-m time.
69

Parameters (Cont.)
AICHTxTiming
Parameter name: AICH transmission timing
Content:
When AICHTXTIMING = 0,
p-p,min = 15360 chips, p-a = 7680 chips, p-m = 15360 chips

When AICHTXTIMING = 1,
p-p,min = 20480 chips, p-a = 12800 chips, p-m = 20480 chips

AICHTxTiming
Content: Transmission timing information of an AICH. "0" indicates that there are 7680 chips offset between the
access preamble of the PRACH and AICH. "1" indicates that there are 12800 chips offset between them.
Value range: 0 to 1
Physical value range: 0 to 1; step: 1
Set this parameter through ADD UAICH, query it through LST UAICH, and modify it needs de-activated the cell
through DEA UCELL. After the old configuration of AICH is deleted through RMV UAICH , a new AICH can be
established through ADD UAICH.
70
PRACH Open Loop Power Control (Cont.)

Power ramping for preamble retransmission:
Power Offset P p-m

Power Ramp Step
Preamble_Initial
_Power
Preamble
Preamble
Preamble
Preamble
Message
part
After UE transmit the first preamble,

If no positive or negative AI on AICH is received after p-a time,
UE shall increase the preamble power by PowerRampStep, and retransmit the preamble.
A preamble ramping procedure consists of several preamble ramping cycles, which cannot exceed Mmax.
In each cycle, the UE retransmits the preamble until the UE receives the acquisition indicator or the
number of retransmissions has reached PreambleRetransMax.
If a negative AI on AICH is received by the UE after p-a time,
which indicates rejection of the preamble, the UE shall wait for a certain Back-off Delay and re-initiate
a new random access process. The parameters NB01min and NB01max define the lower and upper limits
of the back-off delay. If the value of NB01min is equal to that of NB01max, it means that the
retransmission period of the preamble part is fixed.
When a positive AI on AICH is received by UE after p-a time,
it will transmit the random access message after the uplink access slot of the last preamble.
The message part consists of two parts: the control part and the data part. The power of the control part is
the same as the power of the last transmitted preamble plus a value defined by the PowerOffsetPpm
parameter. PowerOffsetPpm must be set for each instance of PRACH TFC.
71

Parameters (Cont.)
PowerRampStep
Parameter name: Power increase step
PreambleRetransMax
Parameter name: Max preamble retransmission
PowerRampStep
Content: The power increase step of the random access preambles transmitted before the UE receives the
acquisition indicator in the random access process.
Value range: 1 to 8
Physical unit: dB
UPRACHUUPARAS.
PreambleRetransMax
Content: The maximum number of preambles transmitted in a preamble ramping cycle.
UPRACHUUPARAS.
72

Parameters (Cont.)
Mmax
Parameter name: Max preamble loop
NB01min / NB01max
Parameter name: Random back-off lower / upper limit
Recommended value: 0 for both NB01min / NB01max
Mmax
Content: Maximum number of random access preamble loops.
Set this parameter through ADD URACH, query it through LST URACH, and modify it first de-activated the cell
through DEA UCELL, then MOD URACH, finally ACT UCELL.
NB01min / NB01max
Content: Lower/Upper limit of random access back-off delay.
Physical unit: frame
Set this parameter through ADD URACH, query it through LST URACH, and modify it first de-activated the cell
through DEA UCELL, then MOD URACH, finally ACT UCELL.
73

Parameters (Cont.)
PowerOffsetPpm
Parameter name: Power offset
Recommended value:
PRACH
PowerOffwetPpm
GainFactorBetaC
GainFactorBetaD
Signaling
-3
13
15
Service
-2
10
15
PowerOffsetPpm
Content: The power offset between the last access preamble and the message control part. The power of
the message control part can be obtained by adding the offset to the access preamble power.
Physical unit: dB
Set this parameter through ADD UPRACHTFC, query it through LST UPRACH, and modify it deactivated the cell through DEA UCELL . After the old configuration of PRACH is deleted through RMV
UPRACHTFC , a new parameters can be established through ADD UPRACHTFC.
The power of the data part is calculated with the following formula:
, where Pcontrol is the power for the control part.

d is the power gain factor for the data part. The value is defined by the GainFactorBetaD parameter.
c is the power gain factor for the control part. The value is defined by the GainFactorBetaC parameter.

74

Parameters (Cont.)
The transmit power on the PRACH cannot be greater

than the maximum allowed uplink transmit power:
MaxAllowedUlTxPower
Parameter name: Max allowed UE UL TX power
MaxAllowedUlTxPower
Content: The maximum allowed uplink transmit power of a UE in the cell, which is related to the network planning.
Physical unit: dBm
Set this parameter through ADD UCELLSELRESEL, query it through LST UCELLSELRESEL, and modify it
through MOD UCELLSELRESEL.
75
Downlink Dedicated Channel Open Loop Power Control
DL DPCH Open Loop Power Control

NodeB
UE
SRNC

RRC
RRC
Allocate RNTI
Select L1 and L2
parameters
NBAP
NBAP
Start RX
description
NBAP
NBAP
DL DPCH open loop

power control
DCH - FP
DCH - FP
DCH - FP
DCH - FP
Start TX
description
RRC
RRC

NBAP
RRC
NBAP
RRC
According to the RRC connection establishment procedure, after RNC received the RRC
CONNECTION REQUEST message, and NodeB set up the radio link for UE, then Iub interface
resources is established between NodeB and RNC.
When DCH-FP of Iub interface finished downlink and uplink synchronization, the downlink DPCH
starts to transmit, and DPCH initial transmission power is calculated through open loop power control.
76
DL DPDCH Open Loop Power Control

When a dedicated channel is set up, the initial power of

downlink DPDCH can be calculated according to the
following formula:
Pinit =
R
Eb
PCPICH
( ) DL
PTotal
W
No
( Ec / No ) CPICH
In this formula, where:

Pinit is the initial power of the DPDCH.
PCPICH is the PCPICH power in a cell. The value is configured by the PCPICHPower parameter on the
RNC.
R is the traffic rate requested by the UE and W is the chip rate (3.84 Mcps).
(Eb/No)DL is the Eb/No target of the downlink DPDCH used to ensure the service quality. Eb is the
energy of a signal information bit and No is the noise spectral density. The RNC estimates a value of
Eb/No target dynamically based on cell environment type and BLER target.
(Ec/No)CPICH is the ratio of received energy per chip to noise spectral density of the CPICH received
by the UE.
is the orthogonal factor in the downlink. The value is fixed to 0.
Ptotal is the downlink transmitted carrier power measured on the NodeB and reported to the RNC.
77
DL DPCCH Open Loop Power Control

1 timeslot
Downlink
Transmit
Power
PO2
PO1
PO3
Data1
DPDCH
TPC
TFCI
DPCCH
Data2
Pilot
DPDCH
DPCCH
The downlink DPCCH consists of three fields: TFCI, TPC, and pilot. Their power is set as the offset
reference to the power of the downlink DPDCHs.
The downlink power on the DPCCH and its associated DPDCHs is simultaneously regulated. Thus,
power control adjusts the power of the DPCCH and DPDCHs with the same step, and the power offset
between the DPCCH and the DPDCH keeps constant.
Power offsets between the DPCCH and the DPDCH in the downlink are identical for all TFCs in the
TFCS, whereas in the uplink the power offsets are TFC-dependent.
The power offsets of TFCI, TPC and pilot fields of the DPCCH reference to the power of DPDCHs are
fixed to 0dB, 3dB, and 3dB respectively.
78
Downlink Power Control Restriction

The power of downlink dedicated channel is limited by

an upper and lower limit for each radio link
RlMaxDlPwr/RlMinDlPwr
Parameter name: RL Max/Min DL TX power
Recommended value is shown in the next page
RlMaxDlPwr
Content: This parameter should fulfill the coverage requirement of the network planning, and the value is relative
to PCPICH transmit power.
Physical unit: dB
Set this parameter through ADD UCELLRLPWR , query it through LST UCELLRLPWR, and modify it through
MOD UCELLRLPWR.
RlMinDlPwr
Content: This parameter should consider the maximum downlink transmit power and the dynamic range of power
control, and the value is relative to PCPICH transmit power.
Physical unit: dB
Set this parameter through ADD UCELLRLPWR, query it through LST UCELLRLPWR, and modify it through
MOD UCELLRLPWR.
79
Downlink Power Restriction Parameters

Recommended configurations for typical services:

Service
RL Max Downlink
Transmit Power (dB)
RL Min Downlink
Transmit Power
(dB)
Downlink SF
CS Domain
12.2 kbps AMR
-3
-18
128
28 kbps
-2
-17
64
32 kbps
-2
-17
64
56 kbps
-15
32
64 kbps
-15
32
PS Domain
8 kbps
-8
-23
128
32 kbps
-4
-19
64
64 kbps
-2
-17
32
144 kbps
-15
16
256 kbps
-13
384 kbps
-11
Both downlink open loop and close loop power control will be limited by these parameters.
80
Uplink Dedicated Channel Open Loop Power Control
UL DPCH Open Loop Power Control

NodeB
UE
SRNC

RRC
RRC
Allocate RNTI
Select L1 and L2
parameters
NBAP
NBAP
Start RX
description
NBAP
NBAP
DCH - FP
DCH - FP
DCH - FP
DCH - FP
Start TX
description
RRC
UL DPCH open loop

power control
RRC
RRC

NBAP
NBAP
RRC
According to the RRC connection establishment procedure, after RNC sent the RRC CONNECTION
SETUP message, UE will try to synchronize with NodeB, and the uplink DPCCH starts to transmit, here
DPCCH initial transmission power is calculated through open loop power control.
The power of the uplink DPDCH is set as a power offset (d/c) reference to the uplink DPCCH. The
uplink DPCCH and DPDCHs are transmitted through different channel codes. To meet a given QoS
requirement on the transport channels, different TFCs use different power offsets.
The RNC has a set of reference values (c,ref and d,ref) that are stored for each predefined Radio
Access Bearer (RAB) or Signaling Radio Bearer (SRB). c,ref and d,ref can be configured by BETAC
and BETAD on the RNC.
The RNC calculates a new power offset for each TFC based on the reference values dynamically and
sends the power offset to the UE.
81
UL DPCCH Open Loop Power Control

The initial power of the uplink DPCCH can be calculated

according to the following formula:
DPCCH _ Initial_ Power = DPCCH _ Power _ Offset CPICH _ RSCP

Where:
DPCCH_Power_Offset is provided by the RNC to the UE via

RRC signaling
CPICH_RSCP is the received signal code power of the

PCPICH
For Huawei, DPCCH_Power_Offset is calculated with the following formula:
Where:
The PCPICHPower parameter defines the PCPICH transmit power in a cell. This value is
broadcast in SIB5.
Uplink interference is the uplink RTWP measured by the NodeB and sent to the UE through the
SIB7.
The DefaultConstantValue parameter reflects the target Ec/No of the uplink DPCCH.
82
UL DPCCH Open Loop Power Control

Parameter
DefaultConstantValue
Parameter name: Constant value configured by default
DefaultConstantValue
Content: This parameter specifies the constant that is used by the RNC to compute the DPCCH_Power_Offset
which is further used by the UE to calculate the UL DPCCH_Initial_Power during the open-loop power control.
Value range: -35 to -10
Physical value range: -35 to -10; step: 1
Physical unit: dB
Set this parameter through SET UFRC, query it through LST UFRC, and modify it through SET UFRC.
83
Uplink Power Control Restriction

There are four parameters which correspond to the

maximum allowed transmit power of four classes of
services:
MaxUlTxPowerforConv
MaxUlTxPowerforStr
MaxUlTxPowerforInt
MaxUlTxPowerforBac
Parameter name: Max UL TX power of

conversational/streaming/interactive/background service
MaxUlTxPowerforConv
MaxUlTxPowerforStr
MaxUlTxPowerforInt
MaxUlTxPowerforBac
Content: The maximum UL transmit power for specific services in a cell. It is based on the UL coverage
requirement of the specific services designed by the network planning.
Physical unit: dBm
Set this parameter through ADD UCELLCAC, query it through LST UCELLCAC, and modify it through MOD
UCELLCAC.

84
Closed Loop Power Control

Closed Loop Power Control Overview
Closed Loop Power Control Overview

Why closed loop power control is needed?

Open loop power control is not accurate enough, it can only

estimate the initial transmission power
Closed loop power control can guarantee the QoS with
minimum power. By decreasing the interference, the system
capacity will be increased
Outer Loop
Inner Loop
SIRmea>SIRtar TPC=0
BLERmea>BLERtarSIRtar
SIRtar
BLERtar BLERmea<BLERtarSIRtar
Until
BLERmea=BLERtar
TPC
SIRmea SIRtar TPC=1
TPC=1
TPC=0
Power
Power
Until
SIRmea=SIRtar
Inner Loop Power Control:

The receiver compares SIRmea (measured SIR) with SIRtar (target SIR), and decide the TPC to send:
If SIRmea is greater than SIRtar, the TPC is set as 0 to decrease transmission power;
If SIRmea is less than SIRtar, the TPC is set as 1 to increase transmission power.
TPC is sent to the transmitter in DPCCH, the transmitter will adjust the power according to the value of
received TPC.
Through inner loop power control, the SIRmea can be ensured to approach SIRtar.
Outer Loop Power Control:
The receiver compares BLER mea (measured BLER) with BLERtar (target BLER), and decide how to set
the SIRtar:
If BLERmea is greater than BLERtar, the SIRtar is increased;
If BLERmea is less than BLERtar, the SIRtar is decreased.
The adjusted SIRtar is sent for the inner loop power control, then it will be used in previous process to
guide the transmitter power adjustment.
Through outer loop power control, the BLERmea can be ensured to approach BLERtar.
85
Uplink Inner Loop Power Control

NodeB compares the measured SIR to the target SIR,

then derives TPC and sends the TPC Decision to UE
TPC Decision
( 0, 1 )
Compare SIRmea with SIRtar

SIRmea > SIRtar TPC = 0
SIRmea SIRtar TPC = 1
Single RL / Soft HO
PCA1 / PCA2
Generate TPC_cmd
( -1, 0, 1 )
Inner Loop
Adjust DPCCH Tx
Set SIRtar
NodeB
Transmit TPC
UE
DPCCH =TPC TPC_cmd
Adjust DPDCH Tx
( c , d )
RNC sends SIRtar (target SIR) to NodeB and then NodeB compares SIRmea (measured SIR) with
SIRtar:
If the estimated SIR is greater than the target SIR, NodeB sends TPC 0 to UE on downlink
DPCCH TPC field;
Otherwise, NodeB sends TPC 1 to UE.
After reception of one or more TPC, UE shall derive a single TPC_cmd (TPC command, with
value among -1, 0, 1):
Two algorithms could be used by the UE for deriving the TPC_cmd, those are PCA1 and PCA2
(PCA means Power Control Algorithm).
For UE is in soft handover state, more than one TPC is received, so firstly multiple TPC_cmd is
combined.
When deriving the combined TPC_cmd, UE shall adjust the transmit power of uplink DPCCH
with a step UL Closed Loop Power Control Step Size, as following:
DPCCH =TPCTPC_cmd
This adjustment is executed on the DPCCH, then associated DPDCH transmit power is
calculated according to DPDCH / DPCCH power ratio d / c.
86
Uplink Inner Loop PCA1 with Single

Radio Link
For single radio link and PCA1, UE derives one TPC_cmd

in each time slot as follows:
TPC
TPC_cmd
-1
-1
-1
-1
This control is performed in each time slot, so

the power control frequency is 1500Hz
When UE has single radio link, only one TPC will be received in each slot. In this case, the value of TPC_cmd
shall be derived by PCA1 as follows:
If the received TPC is equal to 0, then TPC_cmd for that slot is -1;
If the received TPC is equal to 1, then TPC_cmd for that slot is 1.
According to DPCCH channel structure, there are 15 time slots in a 10ms radio frame, and the control is performed
once in each time slot, so the frequency of uplink inner loop PCA1 is 1500Hz.
87
Uplink Inner Loop PCA2 with Single

Radio Link
For single radio link and PCA2, UE derives one TPC_cmd

in each 5-slot group as follows:
10ms radio frame
TPC
Group 2
Group 1
Group 3
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS8
TS9
TS10
TS11
TS12
TS13
TS14
-1
TPC_cmd
This control is performed in each 5-slot group,

so the power control frequency is 300Hz
When UE has single radio link, only one TPC will be received in each slot. In this case, the value of
TPC_cmd shall be derived by PCA2 as follows:
For the first 4 slots of a set, TPC_cmd = 0.
For the fifth slot of a set, UE make the decisions on as follows:
If all 5 TPCs within a group are 1, then TPC_cmd = 1 in the 5th slot;
If all 5 TPCs within a group are 0, then TPC_cmd = -1 in the 5th slot;
Otherwise, TPC_cmd = 0 in the 5th slot.
According to DPCCH channel structure, there are 15 time slots in a 10ms radio frame, and the control is
performed once in each 5-slot group, so the frequency of uplink inner loop PCA2 is 300Hz.
88
Uplink Inner Loop with Soft Handover

When UE enters soft handover state, on the NodeB side,

there are two phases :
Uplink synchronization phase
Multi-radio link phase
On UE side, UE will receive different TPCs from different

RLS in one time slot. Therefore, the UE should combine
all the TPCs to get a unique TPC_CMD
On the NodeB side, there are two phases during the soft handover state:
Uplink synchronization phase
The NodeB should send durative TPC = 1 to the newly-added RL before successful synchronization.
Multi-radio link phase
Each NodeB and each cell will estimate the SIR individually and the general TPC individually. Therefore,
the UE may receive different TPC from different RLS.
Especially, when UE is in softer handover state, it means UE has radio links to the same NodeB, in this case, these
RLs (Radio Link) belong to the same RLS (Radio Link Set), and the all TPCs are the same from each RL.
89
Uplink Inner Loop PCA1 with Soft

Handover
CELL1
For each slot, combine TPC from

the same RLS, then get Wi
CELL2
RL1-1
RL1-2
RLS1
Get TPC_cmd based on

TPC_cmd = (W1, W2, WN)
RLS3
RLS2
CELL3
CELL4
RLS1-TPC (W1)
RLS2-TPC (W2)
RLS3-TPC (W3)
TPC_cmd
-1
-1
-1
-1
-1
-1
-1
-1
When UE is in soft handover state, multiple TPC will be received in each slot from different cells in the active set.
UE will generate the TPC_cmd by PCA1 as follows:
1. Combine the TPC from the same RLS and derive the Wi
When the RLs (Radio Link) are in the same RLS (Radio Link Set), they will transmit the same TPC in a slot. In
this case, the TPCs from the same RLS shall be combined into one.
After combination, UE will obtain a soft symbol decision Wi for each RLSi.
2. Combine the TPC from different RLSs and derive the TPC_cmd
UE derives TPC_cmd, it is based on a function and all the N soft symbol decisions Wi:
TPC_cmd = (W1, W2, WN),
Where TPC_cmd can only take the values 1 or -1.
In Huawei implementation, the function shall fulfil the following criteria:
If the TPCs from all RLSs are 1, the output of shall be equal to 1;
If one TPC from any RLS is 0, the output of shall be equal to -1.
90

Handover
Combine TPC from same RLS
in each time slot
CELL1
CELL2
RL1-1
Calculate TPC_cmd
If any TPC_tempi = -1, TPC_cmd = -1
If
1
N
RLS2
CELL3
TPC _ temp
RL1-2
RLS1
Calculate TPC_tempi for each RLSi
RLS3
CELL4
> 0 .5 , TPC_cmd = 1
i =1
Otherwise, TPC_cmd = 0
When UE is in soft handover state, multiple TPC will be received in each slot from different cells in the active set.
UE will generate the TPC_cmd by PCA2 as follows:
1. Combine the TPC from the same RLS
When the RLs are in the same RLS, they will transmit the same TPC in a slot. In this case, the TPCs from the same
RLS shall be combined into one.
2. Calculate the TPC_tempi for each RLS
UE derives TPC_tempi through the same way in the last slide, as follows:
For the first 4 slots of a group, TPC_tempi = 0.
For the 5th slot of a group:
If all 5 TPCs within a group are 1, then TPC_tempi = 1 in the 5th slot;
If all 5 TPCs within a group are 0, then TPC_tempi = -1 in the 5th slot;
Otherwise, TPC_tempi = 0 in the 5th slot.
3. Calculate the TPC_cmd
UE derives TPC_cmd through the following criteria:
If any TPC_tempi is equal to -1, TPC_cmd is set to -1;
If
, TPC_cmd = 1;
Otherwise, TPC_cmd = 0.
91

Handover (Cont.)
10ms/frame
Group 1
Group 2
Group 3
TPC
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS8
TS9
TS10
TS11
TS12
TS13
RLS1
TS14
1
RLS2
RLS3
TS14
TPC_tempi
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS8
TS9
TS10
TS11
TS12
TS13
RLS1
-1
RLS2
-1
RLS3
-1
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS8
TS9
TS10
TS11
TS12
TS13
TS14
-1
TPC_cmd
The example of the uplink inner loop PCA2 in soft handover state.

Parameters
PwrCtrlAlg
Parameter name: Power control algorithm selection
Recommended value: ALGORITHM1
UlTpcStepSize
Parameter name: UL closed loop power control step size
92
PwrCtrlAlg
Content: This parameter is used to inform the UE of the method for translating the received Transmit Power
Control (TPC) commands. In other words, it is used to select UL power control algorithm.
Value range: ALGORITHM1, ALGORITHM2
Physical value range: ALGORITHM1, ALGORITHM2
UlTpcStepSize
Content: The step size of the closed loop power control performed on UL DPDCH. This parameter is mandatory
when the parameter PwrCtrlAlg is set as ALGORITHM1.
Value range: 1 to 2
Physical unit: dB
For PCA2, the step is fixed to 1 dB.
Downlink Inner Loop Power Control

UE L1 compares the measured SIR to the target SIR, then

derives TPC and sends the TPC Decision to NodeB
Derive TPCest(k)
(0, 1)
L3 set SIRtar
DPC_MODE
Inner Loop
Generate PTPC(k)
L1 compare
SIRmea with
SIRtar
Calculate P(k)
NodeB
Derive and transmit

TPC based on
DPC_MODE
UE
Adjust DPCH Tx Power
Basically the downlink inner loop power control process is similar with uplink, UE L3 sends SIRtar to
UE L1 and then UE L1 compares SIRmea with SIRtar:
If the SIRmea is greater than the SIRtar, UE sends TPC 0 to NodeB on uplink DPCCH TPC field;
Otherwise, UE sends TPC 1 to NodeB.
93
The UE shall check the downlink power control mode before generating the TPC, two algorithm
DPC_MODE1 and DPC_MODE2 could be used by UE to derive the TPC. Upon receiving the TPC,
NodeB shall estimate the transmitted TPC and adjust its downlink DPCCH/DPDCH power accordingly.
After reception of one or more TPC in a slot, NodeB shall derive the estimated TPC TPCest(k) and
calculate a PTPC(k), the power adjustment of k:th slot.
Then NodeB shall adjust the current downlink power P(k-1) to a new power P(k), and adjust the power
of the DPCCH and DPDCH with the same amount, since power difference between them is fixed.
Downlink Inner Loop Power Control Mode

Two DPC_MODE (Downlink Power Control Mode) could

be used:
If DPC_MODE = 0, UE sends a unique TPC in each slot,

UTRAN shall derive TPCest to be 0 or 1, and update the
power every slot
If DPC_MODE = 1, UE repeats the same TPC over 3 slots,

UTRAN shall derive TPCest over three slots to be 0 or 1, and
update the power every three slots
The DPC_MODE parameter is a UE specific parameter and controlled by the UTRAN.

The UE shall check the DPC_MODE (Downlink Power Control Mode) before generating the TPC, and upon
receiving the TPC, the UTRAN shall adjust its downlink power accordingly.
94
Downlink Inner Loop Power Control Mode

Parameters
DpcMode
Parameter name: Downlink power control mode
Recommended value: SINGLE_TPC, namely DPC_MODE = 0
DpcMode
Content: This parameter specifies the DL power control mode.
- SINGLE_TPC, a fast power control mode, indicates that a unique TPC command is sent in each timeslot on the
DPCCH.
- TPC_TRIPLET_IN_SOFT, a slow power control mode, indicates that the same TPC command is sent over three
timeslots. It is applicable to soft handover, and it can decrease the power deviation.
- TPC_AUTO_ADJUST, an automatic adjustment mode, indicates that the value of DPC_MODE can be modified
by sending the ACTIVE SET UPDATE message to the UE.
Value range: SINGLE_TPC (DPC_MODE=0), TPC_TRIPLET_IN_SOFT (DPC_MODE=1),
TPC_AUTO_ADJUST
Physical recommended value: SINGLE_TPC
95
Downlink Inner Loop Power Control (Cont.)

After estimating the TPC, the UTRAN shall set the downlink
power to P(k) for k:th slot according to the following formula:
P ( k ) = P ( k 1 ) + PTPC ( k ) + Pbal ( k )
Where:
P(k-1) is downlink transmission power in (k-1):th slot
PTPC(k) is the adjustment of downlink power in k:th slot
Pbal (k) is correction value according to the downlink power balance

procedure. For a single radio link, Pbal (k) equals 0
If PC_DOWNLINK_POWER_BALANCE_SWITCH is OFF, then Pbal(k) equals 0.

PTPC(k) is calculated according to the following:

If the value of Limited Power Increase Used parameter is

Not Used, then:
+
PTPC ( k ) = TPC
TPC
if TPC est ( k ) = 1
if TPC est ( k ) = 0
Where:
TPCest (k) is uplink received TPC of the k:th slot

TPC is downlink power adjustment step size
96

If the value of Limited Power Increase Used parameter is

Used, then:
+ TPC
PTPC ( k ) = 0

TPC
if TPCest ( k ) = 1 and sum ( k ) + TPC < Power _ Raise _ Limit

if TPCest ( k ) = 1 and sum ( k ) + TPC Power _ Raise _ Limit
if TPCest ( k ) = 0
Where:
k 1
sum ( k ) =
PTPC ( i )
i = k DL _ Power _ Average _ Window _ Size
From the definition above, sum(k) indicates the sum of downlink power adjustment in the latest
DL_Power_Average_Window_Size time slots.
Power_Raise_Limit is set to 10dB.
DL_Power_Averaging_Window_Size is set to 20 slots.

Parameters
PC_INNER_LOOP_LMTED_PWR_INC_SWITCH
This is one switch in PcSwitch (Power control switch)

parameter
Recommended value: 0, namely OFF
FddTpcDlStepSize
Parameter name: FDD DL power control step size
Recommended value: STEPSIZE_1DB, namely 1dB
97
PC_INNER_LOOP_LMTED_PWR_INC_SWITCH
This is one switch in PcSwitch (Power control switch) parameter.
Content: When the switch is on, the limited power increase function is used for DL inner loop power control.
Value range: 1, 0
Physical value range: ON, OFF
Set this parameter through SET UCORRMALGOSWITCH, query it through LST UCORRMALGOSWITCH, and
modify it through SET UCORRMALGOSWITCH.
FddTpcDlStepSize
Content: This parameter specifies the step size of the closed-loop power control performed on DL DPCH in
Frequency Division Duplex (FDD) mode.
Value range: STEPSIZE_0.5DB, STEPSIZE_1DB, STEPSIZE_1.5DB, STEPSIZE_2DB
Physical value range: 0.5, 1, 1.5, 2; step: 1
Physical unit: dB
Downlink Power Balance

Purpose
Monitor the
Tx power of
NodeBs and
start the DPB
process
The purpose of this procedure is to

balance the DL transmission powers
of more than one Radio Links
The start and stop of DPB

The power offset of two RLs is

greater than the DPB start threshold,
NodeB
the DPB process is started

NodeB
The power offset of two RLs is less

than the DPB stop threshold, the
DPB process is stopped
DPB process
During soft handover, the UL TPC is demodulated in each RLS, then due to demodulation errors, the DL transmit
power of the each branch in soft handover will drift separately, which causes loss to the macro-diversity gain.

The DL Power Balance (DPB) algorithm is introduced to reduce the power drift between links during the soft
handover.
98
Downlink Power Balance Parameters

PC_DOWNLINK_POWER_BALANCE_SWITCH

parameter
Recommended value: 1, namely ON
PC_DOWNLINK_POWER_BALANCE_SWITCH
Content: When the switch is on, the RNC supports DL power balancing. During soft handover, TPC bit errors may
cause DL power drift. DL power balancing is enabled to balance the DL power between links, thus achieving the
optimal gain of soft handover.
Value range: 1, 0
99
Outer Loop Power Control
Outer Loop Power Control

Why we need outer loop power control?
Different curves
correspond to
different multi-path
environment
BLER
SIR
The main reason of outer loop power control:

The QoS which NAS provides to CN is BLER, not SIR.
The relationship between inner loop power control and outer loop power control:
SIRtar should be satisfied with the requirement of decoding correctly. But different multi-path
radio environments request different SIRtar. Therefore, the outer loop power control can adjust
the SIRtar to get a stable BLER in the changeable radio environment.
100
Uplink Outer Loop Power Control
Measure BLER of received

data and compare with the
BLERtar
Measure SIR and

compare with SIRtar
Out loop
Set BLERtar
Inner loop
Transmit TPC
Set SIRtar
RNC
NodeB
UE
Uplink outer-loop power control is performed in the SRNC. The SRNC measures the received BLER and compares
it with the BLERtar. If the BLERmea is greater than the BLERtar, the SRNC increases the SIRtar; otherwise, the SRNC
decreases the SIRtar.
Initial SIR Setting

The initial SIR target value (Init_SIR_target) is servicedependent and is provided by the RNC to the NodeB
For the SRB and TRB, the values of SIR target,
Max_SIR_target, and Min_SIR_target must fulfill the

following requirement: Min_SIR_target SIR target
Max_SIR_target
The initial SIR target value is transmitted to the NodeB by using NBAP signaling of each RADIO LINK SETUP or
RADIO LINK RECONFIGURATION PREPARE messages.
101
Adjusting the SIR Target

SIRtar adjustment formula:
BLER meas ,i ( n 1 ) BLER tar ,i

SIR tar ( n ) = MAX SIRtar ( n 1 ) +
Step i Factor
BLER tar ,i
Where:
i is the i:th transport channel
n is the n:th adjustment period
According to the formula above,

SIRtar(n) is the target SIR used for the n:th adjustment period.
MAX means the maximum value among the total i transmission channels.
BLERmeas,i (n) is measured for the i:th transmission channel in the n:th adjustment period.
BLERtar,i is the target BLER of the i:th transmission channel.
Stepi is the adjustment step of the i:th transmission channel.
Factor is the adjustment factor.
In case of multi-service:
The maximum value of the SIR target among multiple services is used for the SIR target adjustment.
If one of the services requires increase in the SIR target, the reconfigured SIR target cannot exceed that
maximum value.
The maximum value can be decreased only when all the services require decrease in the SIR target.
102
SIR Target Adjustment Limitation

The parameters Max_SIR_increase_step and

Max_SIR_decrease_step limit the adjustment range of the
SIRtar, and the algorithm is:
If SIRtar > 0 and SIRtar > Max_SIR_increase_step,

then SIRtar (n+1) = SIRtar (n) + Max_SIR_increase_step
If SIRtar < 0 and ABS (SIRtar) > Max_SIR_decrease_step,

then SIRtar (n+1) = SIRtar (n) - Max_SIR_decrease_step
Where,
SIRtar is the adjustment of SIRtar, and SIRtar = SIRtar (n+1) - SIRtar (n).
ABS (SIRtar) means absolute value of SIRtar.
103
Parameters of BLER-based Outer Loop

Power Control on the RAB Basis
Service
BLER
target
Init_SIR
_target
Max_SIR
_target
Min_SIR
_target
OLPC
period
SIR_adjust
ment_step
Max_SIR_inc
rease_step
Max_SIR_dec
rease_step
SRB 3.4K
0.01
2 dB
5 dB
2 dB
40 ms
0.004 dB
0.4 dB
0.2 dB
SRB 13.6K
0.01
4 dB
5 dB
2 dB
20 ms
0.01 dB
0.5 dB
0.2 dB
AMR 12.2K
0.01
2 dB
5 dB
2 dB
20 ms
0.005 dB
0.5 dB
0.2 dB
CSD 64K
0.002
4 dB
7 dB
2 dB
20 ms
0.002 dB
1 dB
0.1 dB
PS I/B 8K
0.01
2 dB
5 dB
2 dB
40 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 16K
0.01
2 dB
5 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 32K
0.01
2 dB
5 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 64K
0.01
2 dB
5 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 128K
0.01
2 dB
5 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 144K
0.01
2.5 dB
5.5 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 256K
0.01
4 dB
7 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
PS I/B 384K
0.01
6 dB
9 dB
2 dB
20 ms
0.004 dB
0.4 dB
0.2 dB
Where,
CSD: CS domain Data service.
I/B: Interactive and Background.
Set these parameter through ADD UTYPRABOLPC, query it through LST UTYPRABOLPC, and modify it
through MOD UTYPRABOLPC.
104
Uplink Outer Loop Power Control

Parameters
PC_OLPC_SWITCH

parameter
Recommended value: 1, namely ON
PC_OLPC_SWITCH
Comments: When the switch is on, the RNC updates the UL SIR TARGET of radio links on the NodeB side
through IUB DCH FP in-band signaling.
Value range: 1, 0
Uplink Outer-Loop Power Control Based on

BER
The OLPC based on the BER is similar to the OLPC based

on the BLER, but the BER is used as the control object.
When the UE is in discontinuous transmission (DTX) mode,

the RNC cannot receive data or update the BLER.
Therefore, the BER is used to solve this problem.
105
In an optimal condition, the BER target is the average BER after filtering within the adjustment period. The BER
target is obtained before the DTX period starts during the outer-loop power control period. During soft handover, the
BER target is the minimum value among all the links. When the BLER is a constant, the BER on the DPCCH can
vary within a limited range.
During the DTX, the MAC measures the BER on the DPCCH, and the RNC compares it with the BER target. If the
measured BER is smaller than the BER target, the OLPC decreases the SIR target. Otherwise, the OLPC increases
the SIR target.
Downlink Outer Loop Power Control

Measure BLER of
received data and
compare with the
BLERtar
L3
Outer loop
Set
SIRtar
Inner loop
L1
NodeB
Transmit TPC
Measure SIR and

compare with SIRtar
UE
The downlink outer loop power control is implemented inside the UE. Therefore, this algorithm is
specified by UE manufacturer.
The information signaled to the UE by the RNC is a quality target for each radio bearer, expressed as a
BLER target. Then, depending on the manufacturer specific outer-loop power control algorithm, an initial
SIR target value can be deduced from this BLER value.

Generally, the UE L3 measures the received BLER and compares it with the BLERtar. If the BLERmea
is greater than the BLERtar, the L3 increases the SIRtar and send it to UE L1; otherwise, the L3
decreases the SIRtar.
106
WCDMA HANDOVER ALGORITHM AND PARAMETERS
Foreword
Why mobile system need handover?

The mobility of UE
Load Balance
Any others?
Page1
Handover is a basic function of the cellular mobile network. The purpose of

handover is to ensure that a UE in CELL_DCH state is served continuously
when it moves.
With the development of WCDMA network, more and more users join in the
system. Using Handover can achieve load balance between carriers and fully
utilizes system resources.
HCS: Hierarchical Cell Structure.
107
Handover types supported by UMTS:
108
References

3GPP TS 23.122: Non Access Stratum functions related to Mobile

Station (MS) in idle mode
3GPP TS 24.008: Mobile radio interface layer 3 specification; Core
Network Protocols - Stage 3
3GPP TS 25.304: UE Procedures in Idle Mode and Procedures for Cell
Reselection in Connected Mode
3GPP TS 25.331: RRC Protocol Specification
3GPP TS 23.060: General Packet Radio Service (GPRS); Service
description
3GPP TS 25.931: UTRAN Functions, Examples on Signalling
Procedures
Page3
Objectives

Explain the features of each handover
Describe the procedures of each handover
Perform the parameters setting of each handover
109
Page4
The Basic Concepts of Handover

Active set
Monitored set
Detected set
Selective combination
Radio link (RL)
Soft handover gain
Radio link set (RLS)
PCPICH
Maximum ratio
combination

Page5
Active set: A set of cells simultaneously involved in a specific communication

service between the UE and the UTRAN.
Monitored set: A set of cells included in the CELL_INFO_LIST, but do not
belong to the active set.
Detected set: A set of cells detected by the UE, and do not included in the
CELL_INFO_LIST.
RL: Radio link between NodeB and UE.
RLS: All radio links from the same NodeB consist of a radio link set.
Combination way: For soft handover, the uplink signals are combined in RNC.
The RNC will select one best signal to process. We call this selective
combination. For softer handover, the uplink signals are combined in the RAKE
receiver of NodeB. It is maximum ratio combination.
Soft handover gain: Please refer to the WCDMA Coverage Planning course.
PCPICH: Primary Common Pilot Channel. UE measures the signal strength of
PCPICH for handover decision.
110
Intra-Frequency Handover
Intra-Frequency Handover Types

The carrier frequencies of the current cell and target cell are
the same:
Intra-frequency soft handover
Intra-frequency hard handover
Page8
Intra-frequency handover is of the following two types:

Intra-frequency soft handover: means that multiple radio links are
connected to the UE at the same time.
Intra-frequency hard handover: means that only one radio link is
connected to the UE at the same time.
111
Intra-Frequency Handover Types

(Cont.)
Comparison between soft handover and hard handover:

Item
Soft Handover
Hard Handover
The number of RLs in

active set during
Several
One
No
Yes
Only happened
Can be happened in Intra-
between Intra-
frequency cells or Inter-
frequency cells
frequency cells
handover
Interruption during
handover
The frequencies of cells
Page9
The maximum number of RL in the active set is 3 by default. And This

parameter can be changed in the RNC. But this function need the UE to support.
Normally, the active set supported by UE is fixed 3 and can not be changed.
Intra-Frequency Soft Handover

The types of intra-frequency soft handover are as follows:

Intra-NodeB soft handover (also known as softer handover)
Intra-RNC inter-NodeB soft handover
Inter-RNC soft handover
112
Page10
Intra-frequency soft handover is characterized by the function that the UE can be

connected to multiple Universal Terrestrial Radio Access Network (UTRAN)
access points at the same time. Addition and/or release of radio links are
controlled by the ACTIVE SET UPDATE procedure.
The HO_INTRA_FREQ_SOFT_HO_SWITCH parameter in the SET
UCORRMALGOSWITCH command is used to determine whether to enable
both soft handover and softer handover. When the switch is on, the cells on the
RNC can active the soft handover. When the RNC receives reports on the events
1A, 1B, 1C, or 1D, associated addition, removal, and replacement of handover
cell of the soft handover are initiated. By default, this switch is set to ON.
Intra-Frequency Soft Handover (cont.)

Comparison between soft handover and softer handover:

Item
Softer Handover
Soft Handover
When the UE is in the overlapped When the UE is in the

Scenario
Uplink signal
coverage area of two
overlapped coverage area of
neighboring cells of a NodeB
two neighboring cells of
with combined RLs
different NodeBs
Using maximum-ratio
Using selection combination
combination
Downlink
Using maximum-ratio
Using maximum-ratio
signal
combination
combination
Resource use
Occupying less Iub bandwidth
Occupying more Iub bandwidth
Page11
During softer handover, the uplink signaling are combined in NodeB by

maximum ratio combination, but during soft handover they are combined in
RNC by selective combination.
Compare to later one, the maximum ratio combination can get more gain. So the
performance of maximum ratio combination is better.
113
Since softer handover is completed in NodeB, it do not consume more transport

resource of Iub.
Intra-Frequency Hard Handover

Intra-frequency hard handover:

No Iur interface
Iur interface is congested
High-speed Best Effort (BE) service Handover
Soft handover fails
Page12
Compared with soft handover, intra-frequency hard handover uses fewer resources. The
scenarios of intra-frequency hard handover are as follows:

No Iur interface is present between RNCs. In this scenario, intra-frequency hard
handover instead of soft handover can be performed between two RNCs.

The Iur interface is congested between RNCs. In this scenario, also intra-frequency
hard handover instead of soft handover can be performed between two RNCs.

There is a high-speed Best Effort (BE) service. Compared with soft handover, intrafrequency hard handover is used to save downlink bandwidth for a high-speed BE
service.

The intra-frequency soft handover fails and intra-frequency hard handover is allowed.
When intra-frequency soft handover fails because of a congestion problem of the
target cell, the RNC tries an intra-frequency hard handover with a lower service bit
rate.
The HO_INTRA_FREQ_HARD_HO_SWITCH parameter in the SET
UCORRMALGOSWITCH command is used to determine whether to enable intra-frequency
hard handover. When the switch is on (default configuration), the RNC is allowed to initiate
the intra-frequency hard handover. The RNC initiates the intra-frequency hard handover in the
following cases:
114
When the BE service is set up in the DCH, the bit rate of the BE service or combined
services exceeds the rate threshold of DL soft handover.
SOFT_HANDOVER_SWITCH is turned off, the UE reports event 1D.
Intra-Frequency Handover Procedure
Intra-Frequency Handover Procedure
Measurement
Decision
Execution
Page14
The intra-frequency handover procedure is divided into three phases: handover

measurement, handover decision, and handover execution.
After the UE transits to the CELL_DCH state in connected mode during a call,
the RNC sends a MEASUREMENT CONTROL message to instruct the UE to
take measurements and report the measurement event results. Upon the
reception of an event report from the UE, the RNC makes a handover decision
and performs the corresponding handover.
115
Intra-Frequency Handover Measurement
Measurement
Measurement control:
UE
UTRAN
MEASUREMENT CONTROL
Page16
The MEASUREMENT CONTROL message carries the following information:

Event trigger threshold
Hysteresis value
Event trigger delay time
Neighboring cell list

116
Measurement (Cont.)
Measurement report:
UTRAN
UE
MEASUREMENT REPORT
Page17
Measurement (Cont.)
Measurement model in the WCDMA system:
L3 filtering formula:
Fn = (1 ) Fn 1 + M n
117
Page18
Measurement model in the WCDMA system:

A: measurement value of the physical layer
B: measurement value obtained after layer-1 filtering. The value is
weighted by the layer 3 filtering coefficient.
C: measurement value obtained after layer 3 filtering. This value is
controlled by the higher layer. Filtering coefficient C is applicable to
event reports and periodic reports.
C': another measurement value. C' and C are measured in the same way.
D: measurement report message of Uu.
Parameters (a) include the layer 3 filtering system and Parameters (b)
include the measurement report configuration.
L3 filtering formula:
Fn: measurement value obtained after the nth filtering
Fn-1: measurement value obtained after the (n-1)th filtering
Mn: measurement value of the nth physical layer
= 1/2(k/2): k is determined by the parameter which is the layer 3
filtering coefficient of intra-frequency handover measurement
When is set to 1, k = 0 and layer 3 filtering is not performed.

Parameters of Intra-Frequency
Measurement
IntraFreqMeasQuantity
Parameter name: Intra-freq Measure Quantity
Recommended value: CPICH_EC/NO
FilterCoef
Parameter name: Intra-freq meas L3 filter coeff
Recommended value: D3, namely K=3
118
Page19
IntraFreqMeasQuantity
Content: This parameter specifies the intra-frequency measurement
quantity. It defines the reference measurement quantity for the UE to
report event 1x.
Value range: CPICH_EC/NO, CPICH_RSCP
Physical value range: CPICH_EC/NO, CPICH_RSCP
FilterCoef
Content: This parameter specifies the intra-frequency measurement L3
filter coefficient. The larger the value of this parameter, the stronger the
smoothing effect and the higher the anti-fast-fading capability, but the
lower the signal tracing capability and the greater the possibility of call
drops. If the value of this parameter is too small, unnecessary soft
handover or the ping-pong handover may occur.
Value range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13, D15,
D17, D19
Physical value range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19
Set these parameters through SET UINTRAFREQHO/ADD
UCELLINTRAFREQHO/MOD UCELLINTRAFREQHO.

Measurement Events
Event
Description
1A
A primary CPICH enters the reporting range. This indicates that the
quality of a cell is close to the quality of the best cell in the active set. A
relatively high combined gain can be achieved when the cell is added to
the active set.
1B
A primary CPICH leaves the reporting range. This indicates that a cell has
a lower quality than the best cell in the active set. The cell has to be
deleted from the active set.
1C
A non-active primary CPICH becomes better than an active primary CPICH.

This indicates that the quality of a cell is better than the quality of the
worst cell in the active set. The RNC replaces a cell in the active set with
a cell in the monitored set.
1D
The best cell changes.
1J
RAN10.0 provides the solution to the issue of how to add an HSUPA cell
in a DCH active set to an E-DCH active set. Event 1J is added to the 3GPP
protocol. This event is triggered when a non-active E-DCH but active DCH
primary CPICH becomes better than an active E-DCH primary CPICH.
119
Page20
Measurement Events (Cont.)
1A event
Event 1A is triggered on the basis of the following formula:
NA
M New + CIONew W ( M i ) + (1 W ) M Best ( R1a H1a / 2)

i =1

Page21
MNew is the measurement value of the cell in the reporting range.

CIONew is equal to the sum of CIO and CIOOffset, which adjusts the cell boundary in the
handover algorithms. To facilitate handover in neighboring cell configuration, the parameter
is set as a positive value; otherwise, the parameter is set as a negative value.
W represents Weighted factor, which is determined by the parameter Weight. The total quality
of the best cell and the active set is specified by W.
Mi is the measurement value of a cell in the active set.
NA is the number of cells not forbidden to affect the reporting range in the active set. The
parameter CellsForbidden1A indicates whether adding the cell to the active set affects the
relative threshold of event 1A.
MBest is the measurement value of the best cell in the active set.
R1a is the reporting range or the relative threshold of soft handover. The threshold parameters
of the CS non-VP service, VP service, and PS service are as follows:

IntraRelThdFor1ACSVP

IntraRelThdFor1ACSNVP

IntraRelThdFor1APS
H1a represents 1A hysteresis, the hysteresis value of event 1A.
120
A: signal quality curve of the best cell in the active set
B: signal quality curve of a cell in the monitored set
C: curve of Th1A
Page22
The above figure shows the triggering of event 1A. In this procedure, the default
parameter values are used.
If the signal quality of a cell that is not in the active set is higher than Th1A for a
period of time specified by TrigTime1A (that is, Time to trigger in the figure),
the UE reports event 1A.
Th1A = (CPICH Ec/No of the best cell in the active set) - (reporting range for
event 1A)
If Weighted factor > 0, then Th1A = (general signal quality of all the cells in the
active set) - (reporting range for event 1A).
Reporting range for event 1A is equal to the value of IntraRelThdFor1ACSVP,
IntraRelThdFor1ACSNVP, or IntraRelThdFor1APS.
121
Handover (Cont.)
CIO
Parameter name: Cell oriented Cell Individual Offset
CIOOffset
Parameter name: Neighboring cell oriented CIO
CIO
Content: This parameter works with the Neighboring cell oriented CIO. It is used for
intra- or inter-frequency handover decisions. The larger the sum, the higher the
handover priority of the neighboring cell. The smaller the sum, the lower the handover
priority of the neighboring cell. Usually it is configured to 0.

Value range: -20~20

Physical value range: -10~10; step: 0.5

Physical unit: dB

Set this parameter through ADD UCELLSETUP/MOD UCELLSETUP.
CIOOffset

Content: This parameter defines the neighboring cell oriented cell individual offset.
The set value functions in combination of the cell oriented CIO. Their sum is added to
the measurement quantity before the UE evaluates whether an event has occurred. In
handover algorithms, this parameter is used for moving the border of a cell.

Value range: -20~20


Physical unit: dB

Set this parameter through ADD UINTRAFREQNCELL/MOD
UINTRAFREQNCELL.
Page23
122
Handover (Cont.)
IntraRelThdFor1ACSNVP
Parameter name: CS non VP service 1A event relative THD
IntraRelThdFor1ACSVP
Parameter name: VP service 1A event relative THD
IntraRelThdFor1APS
Parameter name: PS service 1A event relative threshold
Page24
IntraRelThdFor1ACSNVP/IntraRelThdFor1ACSVP/IntraRelThdFor1APS

Content: These parameters specify the CS non-VP/VP and PS services relative
threshold of event 1A. The higher the threshold is, the more easily the target cell joins
the active set, the harder the call drops, the larger the ratio of the UE involved in soft
handover is, but the more the use of forward resources is. The lower the threshold is,
the more difficult the target cell joins the active set. Thus the communication quality
and the smooth handover cannot be guaranteed.

Value range: 0~29

Physical value range: 0~14.5; step: 0.5

Physical unit: dB
Set these parameters through SET UINTRAFREQHO/ADD UCELLINTRAFREQHO/MOD
UCELLINTRAFREQHO.
123
Handover (Cont.)
Hystfor1A
Parameter name: 1A hysteresis
TrigTime1A
Parameter name: 1A event trigger delay time
Recommended value: D320, namely 320ms
Weight
Parameter name: Weighted factor
Page25
Hystfor1A

Content: This parameter specifies the hysteresis value for event 1A. The value of this
parameter correlates with slow fading. The larger the value of this parameter, the less
possibility of ping-pong effect or wrong decision. But the event might not be triggered in time.

Value range: 0~15


Physical unit: dB
TrigTime1A

Content: This parameter specifies the time delay to trigger event 1A. The value of this
parameter correlates with slow fading. The larger the value of this parameter, the lower the
incorrect decision probability, but the slower the response of the event to measurement signal
change.

Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640,
D1280, D2560, D5000

Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560,
5000

Physical unit: ms
Weight

Content: This parameter is used to define the soft handover relative threshold based on the
measured value of each cell in the active set. The greater the parameter value, the higher the
soft handover relative threshold. When this value is set to 0, the soft handover relative
threshold is determined only by the best cell in the active set.

Value range: 0~20

Physical value range: 0~2; step: 0.1
UCELLINTRAFREQHO.
124
1A event report mode:

Event trigger report
Event to periodical report

Page26
The report mode of 1A is event trigger report.

Generally the event 1A is reported only once. However, to avoid measurement
report loss, the event 1A reporting can be turned to periodical reporting.
Handover (Cont.)
ReportIntervalfor1A
Parameter name: 1A event to periodical rpt period
PeriodMRReportNumfor1A
Parameter name: 1A event to periodical rpt number
Recommended value: D16
125
Page27
ReportIntervalfor1A

Content: This parameter specifies the reporting period of event 1A. That is, event 1A
is reported at each reporting interval. Usually, event 1A is reported only once.
Nevertheless, if the cell, where event 1A is reported, does not join the active set in a
specified period of time, the UE can change the reporting of event 1A into periodical
mode to avoid missing of measurement reports. The event 1A of this cell is reported
for PeriodMRReportNumfor1A times with the reporting interval as the set value.

Value range: NON_PERIODIC_REPORT, D250, D500, D1000, D2000, D4000,
D8000, D16000

Physical value range: NON_PERIODIC_REPORT, 250, 500, 1000, 2000, 4000, 8000,
16000

Physical unit: ms
PeriodMRReportNumfor1A

Content: This parameter specifies the number of reporting times of event 1A for
periodical reporting. When the actual reporting times exceeds the set value, the
periodical reporting ends.

Value range: D1, D2, D4, D8, D16, D32, D64, INFINITY

Physical value range: 1, 2, 4, 8, 16, 32, 64, INFINITY
UCELLINTRAFREQHO.
1B event
Event 1B is triggered on the basis of the following formula:
NA
M Old + CIO Old W ( M i ) + (1 W ) M Best ( R1b + H 1b / 2 )

i =1

Page28
MOld is the measurement value of the cell that becomes worse.

CIOOld is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the
reporting range and the best cell in the active set.
126

W represents Weighted factor, used to weight the quality of the active set. The total quality of
the best cell and the active set is specified by the parameter Weight.
Mi is the measurement value of a cell in the active set.
NB is the number of cells not forbidden to affect the reporting range in the active set. The
parameter CellsForbidden1B indicates whether adding the cell to the active set affects the
relative threshold of event 1B.
R1b is the reporting range or the relative threshold of soft handover. The threshold parameters
of the CS non-VP service, VP service, and PS services are as follows:

IntraRelThdFor1BCSVP

IntraRelThdFor1BCSNVP

IntraRelThdFor1BPS
H1b is the hysteresis value of event 1B, which is determined by the parameter Hystfor1B.
B: signal quality curve of the worst cell in the active set
C: curve of Th1B

Page29
The above figure shows the triggering of event 1B. In this procedure, the default parameter
values are used.
If the signal quality of a cell in the active set is lower than Th1B for a period of time specified
by TrigTime1B (Time to trigger in the figure), the UE reports event 1B.
Th1B = (CPICH Ec/No of the best cell in the active set) - (reporting range for event 1B)
If Weight > 0, then Th1B = (general signal quality of all the cells in the active set) - (reporting
range for event 1B).
127
Reporting range for event 1B is equal to the value of IntraRelThdFor1BCSVP,

IntraRelThdFor1BCSNVP, or IntraRelThdFor1BPS.
Configuration rule and restriction:

The value of IntraRelThdFor1BCSNVP has to be larger than that of
IntraRelThdFor1ACSNVP.

The value of IntraRelThdFor1BCSVP has to be larger than that of
IntraRelThdFor1ACSVP.

The value of IntraRelThdFor1BPS has to be larger than that of IntraRelThdFor1APS.
Handover (Cont.)
IntraRelThdFor1BCSNVP
Parameter name: CS non VP service 1B event relative THD
IntraRelThdFor1BCSVP
Parameter name: VP service 1B event relative THD
IntraRelThdFor1BPS
Parameter name: PS service 1B event relative threshold
Page30
IntraRelThdFor1BCSNVP/IntraRelThdFor1BCSVP/IntraRelThdFor1BPS

Content: These parameters specify the CS non-VP/VP and PS services relative
threshold of event 1B. The lower the threshold is, the more easily the event 1B is
triggered. The higher the threshold is, the harder the event 1B is triggered.

Value range: 0~29


Physical unit: dB
UCELLINTRAFREQHO.
128
Handover (Cont.)
Hystfor1B
Parameter name: 1B hysteresis
TrigTime1B
Parameter name: 1B event trigger delay time
Page31
Hystfor1B

Content: This parameter specifies the hysteresis value for event 1B. The value of this
possibility of ping-pong effect or wrong decision. But the event might not be triggered
in time.

Value range: 0~15


Physical unit: dB
TrigTime1B

Content: This parameter specifies the time delay to trigger event 1B. The value of this
parameter correlates with slow fading. The larger the value of this parameter, the
lower the incorrect decision probability, but the slower the response of the event to
measurement signal change.

D640, D1280, D2560, D5000

2560, 5000

Physical unit: ms
UCELLINTRAFREQHO.
129
1C event
Event 1C is triggered on the basis of the following formula:
New
+ CIO New M InAS + CIO InAS + H 1c / 2

Page32
MNew is the measurement value of the cell in the reporting range.

CIONew is the cell individual offset value of the cell in the reporting range. It is equal to the
sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the
best cell in the active set.
MInAS is the measurement value of the worst cell in the active set.
H1c is the hysteresis value of event 1C, which is determined by the parameter Hystfor1C.
130
B: signal quality curve of a cell in the active set
C: signal quality curve of the worst cell in the active set
D: signal quality curve of a cell in the monitored set
E: curve of Th1C

Page33
The above figure shows the triggering of event 1C. In this procedure, the default
parameter values are used.
If the signal quality of a cell not in the active set is higher than Th1C for a
period of time specified by TrigTime1C (Time to trigger in the figure), the UE
reports event 1C, as shown in the figure.
Th1C = (CPICH Ec/No of the worst cell in the active set) + (Hystfor1C/2)
The UE reports event 1C for qualified cells after the number of cells in the
active set reaches the maximum value. The maximum number of cells in the
active set can be set by the MaxCellInActiveSet parameter.
131
Handover (Cont.)
Hystfor1C
Parameter name: 1C hysteresis
TrigTime1C
Parameter name: 1C event trigger delay time
Page34
Hystfor1C
Content: This parameter specifies the hysteresis value for event 1C. The value of this

in time.

Value range: 0~15


Physical unit: dB
TrigTime1C

Content: This parameter specifies the time delay to trigger event 1C. The value of this

D640, D1280, D2560, D5000

2560, 5000

Physical unit: ms
UCELLINTRAFREQHO.
132
1C event report mode:


Page35
The report mode of 1C is event trigger report.

Generally the event 1C is reported only once. However, to avoid measurement
report loss, the event 1C reporting can be turned to periodical reporting.
Handover (Cont.)
ReportIntervalfor1C
Parameter name: 1C event to periodical rpt period
PeriodMRReportNumfor1C
Parameter name: 1C event to periodical rpt number
133
Page36
ReportIntervalfor1C

Content: This parameter specifies the number of reporting times of event 1C for
periodical reporting. That is, event 1C is reported at each reporting interval. Usually,
event 1C is reported only once. Nevertheless, if the cell, where event 1C is reported,
does not join the active set in a specified period of time, the UE can change the
reporting of event 1C into periodical mode to avoid missing of measurement reports.
The event 1C of this cell is reported for PeriodMRReportNumfor1C times with the
reporting interval as the set value.

D8000, D16000

16000

Physical unit: ms
PeriodMRReportNumfor1C

Content: This parameter specifies the number of reporting times of event 1C for


UCELLINTRAFREQHO.
1D event
Event 1D is triggered on the basis of the following formula:
NotBest
+ CIO
NotBest
Best
+ CIO

Best
+ H 1d / 2
Page37
MNotBest is the measurement value of a cell that is not the best cell.
CIONotBest is equal to the sum of CIO and CIOOffset, which is the offset between the cell in
the reporting range and the best cell in the active set.
134
CIOBest is the cell individual offset value of the best cell. This parameter is not used for
event 1D.
H1d is the hysteresis value of event 1D, which is determined by the parameter Hystfor1D.
B: signal quality curve of a cell in the active set or the monitored set
C: curve of Th1D
Page38
The above figure shows the triggering of event 1D. In this procedure, the default parameter
values are used.
If the signal quality of a cell not in the active set is higher than Th1D for a period of time
specified by TrigTime1D (Time to trigger in the figure), the UE reports event 1D.
Th1D = (CPICH Ec/No of the best cell in the active set) + (Hystfor1D/2)
135
Handover (Cont.)
Hystfor1D
Parameter name: 1D hysteresis
TrigTime1D
Parameter name: 1D event trigger delay time
Page39
Hystfor1D

Content: This parameter specifies the hysteresis value for event 1D. The value of this
in time.

Value range: 0~15


Physical unit: dB
TrigTime1D

Content: This parameter specifies the time delay to trigger event 1D. The value of this

D640, D1280, D2560, D5000

2560, 5000

Physical unit: ms
UCELLINTRAFREQHO.
136
1J event
Event 1J is triggered on the basis of the following formula:
New
+ CIO
New
InAS
+ CIO

InAS
+ H 1J / 2
Page40
MNew is the measurement result of the cell not in the E-DCH active set but in the DCH
active set.
CIONew and CIOInAS refer to the offset of each cell.
MInAS is the measurement result of the cell in the E-DCH active set with the lowest
measurement result.
H1J is the hysteresis parameter for event 1J and is determined by Hystfor1J.
137
A: signal quality curve of a cell in the E-DCH active set
B: signal quality curve of the worst cell in the E-DCH active set
C: signal quality curve of a cell not in the E-DCH active set but included in DCH active
set
D: signal quality curve of a cell not in the E-DCH active set but included in DCH active
Copyright
set 2009 Huawei Technologies Co., Ltd. All rights reserved.

Page41
The above figure shows the triggering of event 1J. In this procedure, the hysteresis and the
cell individual offsets for all cells equal 0.
If the signal quality of a cell not in the E-DCH active set is higher than Th1J for a period of
time specified by TrigTime1J (Time to trigger in the figure), the UE reports event 1J.
Th1J = (CPICH Ec/No of the worst cell in the active set) + (Hystfor1J/2)
The first measurement report is sent when primary CPICH D becomes better than primary
CPICH B. The "cell measurement event result" of the measurement report contains the
information of primary CPICH D and CPICH B.
On the assumption that the E-DCH active set has been updated after the first measurement
report (E-DCH active set is now primary CPICH A and primary CPICH D), the second report
is sent when primary CPICH C becomes better than primary CPICH A. The "cell
measurement event result" of the second measurement report contains the information of
primary CPICH C and primary CPICH A.
The characteristics of 1J event:

3GPP define the maximum DCH active set size is 6 and the maximum E-DCH active set size
is 4.
The DCH active set covers the E-DCH active set or they are the same.
The best cell in E-DCH active set should be the same as that in DCH active set.
Uplink channel type of UE is decided by the best cell in DCH active set:
138
Uplink channel is E-DCH if the best cell in DCH active set supports HSUPA.

Uplink channel is DCH if the best cell in DCH active set can NOT support HSUPA.
Processing procedure of 1J event:
The UE reports 1J event if it find a non-active E-DCH but active DCH cell PCICH becomes
better than an active E-DCH PCIPCH.
RNC will add the target cell into E-DCH active set if the E-DCH active set is NOT full.
RNC will perform replace procedure if the E-DCH active set is full.
Handover (Cont.)
Hystfor1J
Parameter name: 1J hysteresis
TrigTime1J
Parameter name: 1J event trigger delay time
MaxEdchCellInActiveSet
Parameter name: Max number of cell in EDCH active set
Hystfor1J
Content: This parameter specifies the hysteresis value for event 1J. The value of this
in time.
Value range: 0~15
Physical unit: dB
Set this parameter through SET UINTRAFREQHO/ADD
TrigTime1J
Content: This parameter specifies the time delay to trigger event 1J. The value of this
lower probability of incorrect decision, but the slower the response of event to the
change of measured signals.

Page43
139
D640, D1280, D2560, D5000
2560, 5000
Physical unit: ms
Set this parameter through SET UINTRAFREQHO/ADD
MaxEdchCellInActiveSet
Content: This parameter determines the maximum number of links in the EDCH active
set. When the RNC acts as the SRNC, the number of links in the EDCH active set for
all the UEs under the RNC cannot exceed the parameter value. If the parameter value
is too large, a lot of resources on the RAN side will be occupied as the same data is
transferred over multiple EDCH links in macro diversity, thus affecting the system
performance. If this parameter value is too small, insufficient combination gain can be
achieved in macro diversity by the EDCH, which causes excessive retransmissions and
affects the UE speed.
Value range: 1~4
Set this parameter through SET UHOCOMM.

1J event report mode:


Page44
The report mode of 1J is event trigger report.

Generally the event 1J is reported only once. However, to avoid measurement
report loss, the event 1J reporting can be turned to periodical reporting.
140
Handover (Cont.)
ReportIntervalfor1J
Parameter name: 1J event to periodical rpt period
PeriodMRReportNumfor1J
Parameter name: 1J event to periodical rpt number
Page45
ReportIntervalfor1J

Content: This parameter specifies the number of reporting times of event 1J for
periodical reporting. That is, event 1J is reported at each reporting interval. Usually,
event 1J is reported only once. Nevertheless, if the cell, where event 1J is reported,
does not join the EDCH active set in a specified period of time, the UE can change the
reporting of event 1J into periodical mode to avoid missing of measurement reports.
The event 1J of this cell is reported for PeriodMRReportNumfor1J times with the
reporting period as the set value.

D8000, D16000

16000

Physical unit: ms
PeriodMRReportNumfor1J

Content: This parameter specifies the number of reporting times of event 1J for


UCELLINTRAFREQHO.
141
Intra-Frequency Handover Decision and Execution
Intra-Frequency Handover Decision

and Execution
The intra-frequency handover decision and execution

procedure depends on the different measurement events
that the RNC receives:
1A Event
1B Event
1C Event
1D Event
1J Event
142
Page47
143
Handover (Cont.)
MaxCellInActiveSet
Parameter name: Max number of cell in active set
SHOQualmin
Parameter name: Min quality THD for SHO
Page49
MaxCellInActiveSet

Content: This parameter specifies the maximum number of cells in the active set. This
parameter can achieve the balance between the signal quality in the SHO area and the
performance of the system. The more cells the active set contains, the larger macro
diversity gain the user obtains in the SHO area, and the smaller the intra-frequency
interference is. But in this case, the user occupies resources of several cells, which
increases the amount of data to be processed by the system and lowers the system
performance.

Value range: 1~6

SHOQualmin

Content: When the RNC receives events 1A, 1C and 1D, the target cell can be added
to the active set only when CPICH Ec/No of the target cell is higher than this absolute
threshold.

Value range: -24~0


Physical unit: dB
UCELLINTRAFREQHO.
144
Rate Reduction After an SHO Failure

If the radio link addition for a soft handover fails, the rate
reduction is triggered for R99 NRT (Non Real Time) services to
increase the probability of a successful soft handover
1A,1C,1D is received by RNC
Execute admission control in target cell
Admission succeed?
Yes
No
Estimation
Rate Reduction
Execution
Execute Handover
Page50
Estimation Procedure for Rate

Reduction
145
Page51
If the RNC receives a 1A, 1C, or 1D measurement report, the RNC tries to add the
corresponding cell to the active set. If the addition fails, the RNC performs the estimation
procedure for rate reduction.
Estimation procedure for rate reduction:

Step 1:

The RNC evaluates whether the measurement quantity of the cell failing to be
admitted meets the condition of rate reduction.

If the condition is met, the RNC performs a rate reduction process for the
access service immediately, as described in the next page Procedure of Rate
Reduction Execution.

If the condition is not met, the RNC performs the step 2.

The condition of rate reduction is as follows: Mnew > Mbest_cell RelThdForDwnGrd

Mnew is the CPICH Ec/No measurement value of the cell failing to be
admitted.

Mbest_cell is the CPICH Ec/No measurement value of the best cell in the
active set.

RelThdForDwnGrd is configured through the parameter Relative threshold of
SHO failure.
Step 2:

The RNC evaluates whether the number of SHO failures in the cell exceeds the
Threshold number of SHO failure.

If the number of SHO failures in the cell is smaller than the ShoFailNumForDwnGrd:

If the timer has not been started, the RNC starts it.

If the timer has been started, the RNC increments the SHO failure counter by
one.

The timer length is set through the parameter ShoFailPeriod.

The SHO failure counter of a cell is used to record the number of SHO failures in this
cell. For each UE, the RNC records the number of SHO failures in three cells at most.
For SHO failures in any other cells, the RNC does not record the number.

Before the SHO failure evaluation timer expires, no action is taken and the RNC waits
for the next measurement report period.

When the SHO failure evaluation timer expires, the RNC sets the SHO failure counter
of the corresponding cell to 0 and ends the evaluation.

If the number of SHO failures in the cell is larger than or equal to the parameter
ShoFailNumForDwnGrd, the RNC performs a rate reduction process for the access
service.
146
Handover (Cont.)
RelThdForDwnGrd
Parameter name: Relative threshold of SHO failure
ShoFailPeriod
Parameter name: Max evaluation period of SHO failure
ShoFailNumForDwnGrd
Parameter name: Threshold number of SHO failure
Page53
RelThdForDwnGrd

Content: This parameter specifies the threshold of immediate rate reduction after the
soft handover failure.

Value range: -29~29

Physical value range: -14.5~14.5; step: 0.5

Physical unit: dB
ShoFailPeriod

Content: This parameter specifies the maximum evaluation period of the soft handover
failure. When the rate reduction evaluation is performed on a cell that fails to join the
active set, the evaluation timer is started. If the cell cannot fulfill the condition of rate
reduction before the timer expires, the evaluation and rate reduction retry on the cell
will not be performed.

Value range: 0~120


Physical unit: s
ShoFailNumForDwnGrd

Content: This parameter specifies the threshold number of the soft handover failures.
This parameter determines the reporting times of the events from the cell that fails to
join the active set in soft handover, to trigger the rate reduction of the active set and
the attempt to join the active set.

Value range: 0~63
147

Set these parameters through SET UINTRAFREQHO.
Procedure of Rate Reduction Execution
Page54
The RNC performs a rate reduction process for the access service. The method
of determining the access rate after the rate reduction is the same as that
described in rate negotiation of load control course.
After the rate reduction succeeds, the RNC immediately attempts to add this cell
to the active set without measurement:
If the cell succeeds in admitting the UE, the RNC adds the radio link and
sets the SHO failure counter of the cell to 0 and ends the execution.
If the cell fails to admit the UE, the RNC starts the Period of penalty timer
for SHO failure after down rate to avoid an increase in the rate triggered
by DCCC within the period. Also in this period, the RNC sets the SHO
failure counter of the cell to 0 and ends the execution.
148
Handover (Cont.)
DcccShoPenaltyTime
Parameter name: Period of penalty timer for SHO failure

after down rate
Page55
DcccShoPenaltyTime
Content: This parameter defines the length of penalty timer for SHO
failure after rate reduction in the active set. When the rate reduction in the
active set is performed which triggers the increase of SHOs in the target
cell, if the target cell fails to join the active again, the RNC starts the
penalty timer for SHO failure. This parameter defines the length of the
penalty timer. Before the timer expires, the rate increasing in the active set
is prohibited, but rate reduction is not prohibited.
Value range: 0~255
Physical unit: s
Set this parameter through SET UINTRAFREQHO.

149
Neighboring Cell Combination Algorithm
Neighboring Cell Combination

Algorithm
Cell A
Cell B
Cell C
Cell A, Cell B and Cell C

are in active set. Cell A is
the best cell. Cell B
Ec/No is greater than
Cell C.
Cell A
Cell B
Firstly, the cells in

the active set are
added.
Cell C
Secondly,
the
neighboring cells
of cell A are
added.
After that, the

neighboring cells
of cell B are
added.
Finally,
the
neighboring cells
of cell C are
added.
Page57
After the active set is updated, the RNC updates the neighboring cell list by using the
neighboring cell combination algorithm according to the status of the active set. This list
includes the new intra-frequency, inter-frequency, and inter-RAT neighboring cells. The
combination methods of intra-frequency handover, inter-frequency handover, and inter-RAT
handover are the same.
The neighboring cell combination result is contained in the MEASUREMENT CONTROL
message and sent to the UE, which instructs the UE to perform intra-frequency, interfrequency, and inter-RAT measurement and handover procedures.
The number of inter-frequency neighboring cells is configured as follows:

A maximum of 32 intra-frequency neighboring cells are configured.

A maximum of 32 single-carrier inter-frequency neighboring cells are configured.

A maximum of 64 multi-carrier inter-frequency neighboring cells are configured.
A maximum of 32 inter-RAT neighboring cells are configured.
Neighboring cell combination switch:

HO_MC_NCELL_COMBINE_SWITCH is the neighboring cell combination switch.

If the switch is set to ON, measurement objects are chosen from the neighboring cells
of all the cells in the active set.
150
If the switch is set to OFF, measurement objects are chosen from the neighboring cells
of the best cell.
Neighboring cell combination procedure:
After obtaining the intra-frequency neighboring cells of each cell in the active set, the RNC
calculates the union neighboring cell set of the intra-frequency cells, which is referred as Sall,
by using the following method. This method can also be used to generate the Sall of interfrequency or inter-RAT cells.

The intra-frequency, inter-frequency, and inter-RAT neighboring cells of each cell in
the current active set are obtained.

The RNC sequences the cells in the active set in descending order of CPICH Ec/No
according to the latest measurement report (event 1A, 1B, 1C, or 1D) from the UE.
The best cell is based on event 1D, whereas other cells are based on the latest
measurement report.

The cells in the active set are added to Sall.

The neighboring cells of the best cell in the active set are added to Sall. NprioFlag (the
flag of the priority) and Nprio (the priority of the neighboring cell), which are set for
each neighboring cell, are used to change the order of adding the neighboring cells to
Sall.

The neighboring cells of other cells in the active set are added to Sall in descending
order by CPICH Ec/No values of these cells in the active set. The neighboring cells of
the same cell in the active set are added according to Nprio and the number of repeated
neighboring cell is recorded.

If there are more than 32 intra-frequency neighboring cells in Sall, delete the repeated
neighboring cells whose number in Sall is less. The top 32 neighboring cells are
grouped into the final Sall.
151
Parameters of Neighboring Cell

Combination Algorithm
HO_MC_NCELL_COMBINE_SWITCH
Parameter name: Neighboring Cell Combination Switch
Recommended value: ON
NprioFlag
Parameter name: The flag of the priority
Recommended value: FALSE
Nprio
Parameter name: the priority of the neighboring cell
Recommended value: None
Page59
HO_MC_NCELL_COMBINE_SWITCH
Content: When the switch is on, the neighboring cell combined algorithm is used

during the delivery of the objects to be measured. When the switch is off, the best cell
algorithm is used.

Value range: ON, OFF

Physical value range: 1, 0

Set this parameter through SET UCORRMALGOSWITCH.
NprioFlag

Content: Priority identifier of neighboring cells. TRUE indicates that the neighboring
cell priority is valid in the algorithm of neighboring cell combination. FALSE
indicates that the neighboring cell priority is invalid, and, in the algorithm of
neighboring cell combination, the cell with invalid priority is the last one to be
considered as the measurement object.

Value range: FALSE, TRUE

Physical value range: FALSE, TRUE

Set the upper two parameters through ADD UINTRAFREQNCELL/MOD
UINTRAFREQNCELL / ADD UINTERFREQNCELL/MOD UINTERFREQNCELL
/ ADD U2GNCELL/MOD U2GNCELL.
Nprio

Content: Priority of neighboring cells. The lower the priority, the easier it is for the
neighboring cell to be delivered as the measurement object. For example, it is more
152

possible for a neighboring cell of priority 1 than a cell of priority 2 to be delivered as

the measurement object.
Value range: 0~31
Set the upper two parameters through ADD UINTRAFREQNCELL/MOD
UINTRAFREQNCELL / ADD UINTERFREQNCELL/MOD UINTERFREQNCELL
/ ADD U2GNCELL/MOD U2GNCELL.
Signaling Procedures for Intra-Frequency Handover
Signaling Procedures for IntraFrequency Handover

There are five types of signaling procedures for intrafrequency handover:

Intra-NodeB Intra-Frequency Soft Handover
Intra-RNC Inter-NodeB Intra-Frequency Soft Handover
Inter-RNC Intra-Frequency Soft Handover
Intra-RNC Inter-NodeB Intra-Frequency Hard Handover
Inter-RNC Intra-Frequency Hard Handover
153
Page61
Intra-NodeB Intra-Frequency Soft

Handover
154
Page62
Intra-RNC Inter-NodeB Intra-Frequency

Soft Handover
155
Page63
Inter-RNC Intra-Frequency Soft

Handover
156
Page64
Intra-RNC Inter-NodeB Intra-Frequency

Hard Handover
157
Page65
Inter-RNC Intra-Frequency Hard

Handover
158
Page66
Inter-Frequency Handover
Inter-Frequency Handover Overview
Inter-Frequency Handover Types

The carrier frequency of the current cell and target cell

are different
Based on the triggering causes of handover, interfrequency handover can be categorized into four types:
Coverage-based inter-frequency handover
QoS-based inter-frequency handover
Load-based inter-frequency handover
Speed-based inter-frequency handover
Page69
Coverage-based inter-frequency handover:

If a moving UE leaves the coverage of the current frequency, the RNC needs to trigger
the coverage-based inter-frequency handover to avoid call drops.
QoS-based inter-frequency handover:

According to the Link Stability Control Algorithm, the RNC needs to trigger the QoSbased inter-frequency handover to avoid call drops.
Load-based inter-frequency blind handover:

To balance the load between inter-frequency con-coverage cells, the RNC chooses
some UEs and performs the inter-frequency blind handover according to user priorities
and service priorities.
Speed-based inter-frequency handover:

When the Hierarchical Cell Structure (HCS) applies, the cells are divided into different
layers according to coverage. The macro cell has a larger coverage and a lower priority,
whereas the micro cell has a smaller coverage and a higher priority.
159
Inter-frequency handover can be triggered by the UE speed estimation algorithm of the

HCS. To reduce frequent handovers, the UE at a higher speed is handed over to a cell
under a larger coverage, whereas the UE at a lower speed is handed over to a cell
under a smaller coverage.
The InterFreqHOSwitch parameter in the ADD UCELLHOCOMM command is used to
chooses the inter-frequency measurement control parameters to implement handover
measurement based on coverage, QoS and speed.
The HO_INTER_FREQ_HARD_HO_SWITCH parameter in the SET
UCORRMALGOSWITCH command is used to determine whether to allow load-based interfrequency handover.
Coverage-based Inter-Frequency Handover
Coverage-based Inter-Frequency
Handover
Page71
In the triggering phase:

The RNC requests the UE to measure through an inter-frequency measurement control
message. If the CPICH Ec/No or CPICH RSCP of the current cell is lower than the
corresponding threshold, the UE reports event 2D.
In the measurement phase:

The RNC sends an inter-frequency measurement control message to the UE,
requesting the NodeB and UE to start the compressed mode. The RNC also requests
the UE to perform the inter-frequency measurement.
160
In this phase, the method of either periodical measurement report or event-triggered

measurement report can be used.
In the decision phase:

After the UE reports event 2B, the RNC performs the handover. Otherwise, the UE
periodically generates measurement reports, and the RNC makes a decision after
evaluation.
In the execution phase:

The RNC executes the handover procedure.
Handover - Triggering Phase
Triggering event:
2D event:
The estimated quality of the currently used frequency is below

a certain threshold
2F event:
The estimated quality of the currently used frequency is above a

certain threshold
Page72
When the estimated quality or strength of the currently used frequency is below
a certain threshold, 2D event will be triggered. Then RNC will initiate the
compressed mode to start inter-frequency measurement.
During compressed mode, if the estimated quality of the currently used
frequency is above a certain threshold, 2F event will be triggered. Then RNC
will stop the compressed mode.
161
Compressed Mode
Purpose
Measure the inter-frequency cell or inter-RAT cell under FDD

mode
Categories
Downlink compressed mode
Uplink compressed mode
Realization Methods
SF/2
Higher layer scheduling
Page73
Compressed mode control is a mechanism whereby certain idle periods are

created in radio frames during which the UE can perform measurements on
other frequencies. The UE can carry out measurements in the neighboring cell,
such as GSM cell and FDD cell on other frequency. If the UE needs to measure
the pilot signal strength of an inter-frequency WCDMA or GSM cell and has
one frequency receiver only, the UE must use the compressed mode.
Each physical frame can provide 3 to 7 timeslots for the inter-frequency or interRAT cell measurement, which enhances the transmit capability of physical
channels but reduces the volume of data traffic.
In DL, during compressed mode, UE receiver can test signal from other
frequency. In order to avoid the effect cause by UE transmitter, compressed
mode is also used in UL.
The compressed mode includes two types, spreading factor reduction (SF/2) and
high layer approaches. The usage of type of compressed mode is decided by the
RNC, according to spreading factor used in uplink or downlink.
162
Handover Events
2D event:

QUsed TUsed2d - H2d/2

QUsed is the measured quality of the used frequency.

TUsed2d is the absolute quality threshold of the cell that uses the current
frequency. Based on the service type and measurement quantity, this threshold
can be configured through one of the following parameters:
InterFreqCSThd2DEcN0
InterFreqR99PsThd2DEcN0
InterFreqHThd2DEcN0
InterFreqCSThd2DRSCP
InterFreqR99PsThd2DRSCP
InterFreqHThd2DRSCP
H2d is the event 2D hysteresis value set through the parameter HystFor2D.
After the conditions of event 2D are fulfilled and maintained until the
TimeToTrig2D is reached, the UE sends the event 2D measurement report
message.
Any of the Ec/No and RSCP measurement result can trigger the 2D event.

Page74
163
Parameters of Inter-Frequency
Handover
Parameter name: Inter-freq CS measure start Ec/No THD
Parameter name: Inter-freq R99 PS measure start Ec/No

THD
InterFreqHThd2DEcN0
Parameter name: Inter-freq H measure start Ec/No THD
Page75

Content: Threshold to trigger inter-frequency measurement with measurement quantity
of Ec/No for CS domain services.

Value range: -24~0


Physical unit: dB

of Ec/No for PS domain non-HSPA services.

Value range: -24~0


Physical unit: dB
InterFreqHThd2DEcN0

of Ec/No for PS domain HSPA services.

Value range: -24~0

Physical value range: -24~0; step : 1

Physical unit: dB
Set these parameters through ADD UCELLINTERFREQHOCOV/ MOD
UCELLINTERFREQHOCOV/ SET UINTERFREQHOCOV.
164
Handover (Cont.)
Parameter name: Inter-freq CS measure start RSCP THD
Parameter name: Inter-freq R99 PS measure start RSCP THD
InterFreqHThd2DRSCP
Parameter name: Inter-freq H measure start RSCP THD
Page76

of RSCP for CS domain services.


Physical value range: -115~-25; step: 1

Physical unit: dBm

of RSCP for PS domain non-HSPA services.



Physical unit: dBm
InterFreqHThd2DRSCP

of RSCP for PS domain HSPA services.



Physical unit: dBm
Set these parameters through ADD UCELLINTERFREQHOCOV/MOD
UCELLINTERFREQHOCOV/SET UINTERFREQHOCOV.
165
Handover (Cont.)
HystFor2D
Parameter name: 2D hysteresis
TimeToTrig2D
Parameter name: 2D event trigger delay time
HystFor2D
Content: Hysteresis value for the event 2D. The value of this parameter
correlates with slow fading. The larger the value of this parameter, the
smaller probability of ping-pong effect or wrong decision, but event 2D
might not be triggered in time.
Value range: 0~29
Physical unit: dB
TimeToTrig2D
Content: Time delay to trigger event 2D. The value of this parameter
correlates with slow fading. The larger the value of this parameter, the
lower probability of incorrect decision, but the slower the response of
event 2D to the change of measured signals.
Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200,
D240, D320, D640, D1280, D2560, D5000
Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320,
640, 1280, 2560, 5000
Physical unit: ms

Page77
166
Handover Events (Cont.)
2F event
Event 2F is triggered on the basis of the following formula:

QUsed TUsed2f + H2f/2

Page78

TUsed2f is the absolute quality threshold of the cell that uses the current frequency. Based on
the service type and measurement quantity, this threshold can be configured through one of
the following parameters:

InterFreqCSThd2FEcN0

InterFreqR99PsThd2FEcN0

InterFreqHThd2FEcN0

InterFreqCSThd2FRSCP

InterFreqR99PsThd2FRSCP

InterFreqHThd2FRSCP
H2f is the event 2F hysteresis value set through the parameter HystFor2F.
After the conditions of event 2F are fulfilled and maintained until the parameter
TimeToTrig2F is reached, the UE reports the event 2F measurement report message.
Any of Ec/No and RSCP measurement result can trigger the 2F event.
Conditions of event 2F are as follows: TUsed2d - H2d/2 < TUsed2f + H2f/2, for example,
(InterFreqCSThd2DEcN0HystFor2D/2) < (InterFreqCSThd2FEcN0+ HystFor2F/2).
167
Handover (Cont.)
Parameter name: Inter-freq CS measure stop Ec/No THD
Parameter name: Inter-freq R99 PS measure stop Ec/No THD
InterFreqHThd2FEcN0
Parameter name: Inter-freq H measure stop Ec/No THD
Page79

Content: Threshold to stop inter-frequency measurement with measurement quantity
of Ec/No for CS domain services.

Value range: -24~0


Physical unit: dB

of Ec/No for PS domain non-HSPA services.

Value range: -24~0


Physical unit: dB
InterFreqHThd2FEcN0

of Ec/No for PS domain HSPA services.

Value range: -24~0


Physical unit: dB
168
Handover (Cont.)
Parameter name: Inter-freq CS measure stop RSCP THD
Parameter name: Inter-freq R99 PS measure stop RSCP THD
InterFreqHThd2FRSCP
Parameter name: Inter-freq H measure stop RSCP THD
Page80

of RSCP for CS domain services.



Physical unit: dBm

of RSCP for PS domain non-HSPA services.



Physical unit: dBm
InterFreqHThd2FRSCP

of RSCP for PS domain HSPA services.



Physical unit: dBm
169
Handover (Cont.)
HystFor2F
Parameter name: 2F hysteresis
TimeToTrig2F
Parameter name: 2F event trigger delay time
Page81
HystFor2F

Content: Hysteresis value for the event 2F. The value of this parameter correlates with
slow fading. The larger the value of this parameter, the smaller probability of pingpong effect or wrong decision, but event 2F might not be triggered in time.

Value range: 0~29


Physical unit: dB
TimeToTrig2F

Content: Time delay to trigger the event 2F. The value of this parameter correlates
with slow fading. The larger the value of this parameter, the lower probability of
incorrect decision, but the slower the response of event 2F to the change of measured
signals.

D640, D1280, D2560, D5000

2560, 5000

Physical unit: ms
170
Handover - Measurement Phase
RNC
UE
Measurement report (2D)
Physical Channel Recfg (CM)
Physical Channel Recfg Complet (CM)
Measurement control (RSCP)
Measurement control (Ec/No)
Page82
When the UE enters the compress mode, RNC will trigger the inter-frequency handover
measurement by two additional measurement control signaling, so as to request UE test interfrequency neighbor cell.
In this Measurement control message, RNC should inform the UE inter-frequency
measurement parameter, including neighbor list and reporting mode as well.
171
Handover - Measurement Phase (Cont.)
Measurement report:
RNC
UE
UE
RNC
Measurement report
Measurement report (2B)
Measurement report
Measurement report
Handover
Handover
Periodical Reporting
Event Reporting
Page83
The measurement report mode of inter-frequency handover is configured

through the parameter InterFreqReportMode. By default, periodically reporting
is recommended.
The advantage of periodical measurement report is that if the handover fails, the
RNC reattempts the handover to the same cell after receiving the periodical
measurement report from the UE. This increases the probability of the success of
inter-frequency handover.
Based on the measurement control message received from the RNC, the UE
periodically reports the measurement quality of the target cell. Then, based on
the measurement report, the RNC makes the handover decision and performs
handover.
If the reporting mode is periodically reporting: UE test the Inter-frequency
neighbor RSCP and Ec/No.
If the reporting mode is event trigger reporting: UE test the Inter-frequency
neighbor RSCP and Ec/No, and current cell Ec/No or RSCP.
172
Handover (Cont.)
InterFreqReportMode
Parameter name: Inter-frequency measure report mode
Recommended value: Periodical reporting
PrdReportInterval
Parameter name: Inter-frequency measure periodical rpt

period
InterFreqMeasTime
Parameter name: Inter-freq measure timer length
Page84
InterFreqReportMode

Content: This parameter specifies the inter-frequency measurement report mode.

Value range: PERIODICAL_REPORTING(Periodical reporting), EVENT_TRIGGER(Event
trigger)

Physical value range: Periodical reporting, Event trigger
PrdReportInterval

Content: This parameter specifies the interval of the inter-frequency measurement report.

Value range: NON_PERIODIC_REPORT(Non periodical reporting), D250, D500, D1000,
D2000, D3000, D4000, D6000, D8000, D12000, D16000, D20000, D24000, D28000, D32000,
D64000

Physical value range: NON_PERIODIC_REPORT, 250, 500, 1000, 2000, 3000, 4000, 6000,
8000, 12000, 16000, 20000, 24000, 28000, 32000, 64000

Physical unit: ms
InterFreqMeasTime

Content: Timer length for inter-frequency measurement. After inter-frequency measurement
starts, if no inter-frequency handover is performed when this timer expires, the inter-frequency
measurement and the compressed mode (if started) are stopped. The value 0 indicates the
timer is not to be enabled.

Value range: 0~512


Physical unit: s
173
Handover - Decision Phase
The coverage-based inter-frequency handovers are

categorized into two types according to the following
two measurement report modes:
periodical measurement report mode
event-triggered measurement report mode
Each mode corresponds to a different decision and

execution procedure
Page85
Handover - Decision Phase (Cont.)
Periodical measurement report mode:

RNC decide whether both the CPICH Ec/No value and CPICH RSCP
value of the pilot signal of the target cell meet the requirement of
inter-frequency handover. The evaluation formula is listed below:
Mother_Freq + CIOother_Freq Tother_Freq + H/2
Start the hard handover time-to-trigger timer, which is configured

through the parameter TimeToTrigForPrdInterFreq
If Mother_Freq + CIOother_Freq < Tother_Freq - H/2, stop the

timer
Select the cells in sequence, that is, from high quality cells to low
quality ones, to initiate inter-frequency handover in the cells where
the hard handover time-to-trigger timer expires
174
Page86
Mother_Freq is the CPICH Ec/No or CPICH RSCP measurement value of the target cell reported by
the UE. Both of the two measurement values of the inter-frequency cell must satisfy the formula.
CIOother_Freq is the cell individual offset value of the target cell. It is equal to the sum of CIO and
CIOOffset.
Tother_Freq is the decision threshold of inter-frequency hard handover. Based on the service type and
measurement quantity, this threshold can be configured through one of the following parameters:

TargetFreqCsThdEcN0

TargetFreqR99PsThdEcN0

TargetFreqHThdEcN0

TargetFreqCsThdRscp

TargetFreqR99PsThdRscp

TargetFreqHThdRscp

These thresholds are the same as the quality threshold of event 2B.
H is the inter-frequency hard handover hysteresis value set through the parameter
HystForPrdInterFreq.
Page87
Each cell in the measurement report shall be evaluated as mentioned previously. When the hard
handover time-to-trigger timers of more than one cell expire at the same time, the latest measurement
report is used for selecting the best inter-frequency neighboring cell for handover. For example, the
cell with the highest CPICH RSCP in the latest measurement report is selected, as shown in the above
figure.
175
Handover (Cont.)
CIO
CIOOffset
Page88
CIO
Content: This parameter works with the Neighboring cell oriented CIO. It is used for intra- or
inter-frequency handover decisions. The larger the sum, the higher the handover priority of the
neighboring cell. The smaller the sum, the lower the handover priority of the neighboring cell.
Usually it is configured to 0.

Value range: -20~20


Physical unit: dB

Set this parameter through ADD UCELLSETUP/MOD UCELLSETUP.
CIOOffset

Content: This parameter defines the neighboring cell oriented cell individual offset. The set
value functions in combination of the cell oriented CIO. Their sum is added to the
measurement quantity before the UE evaluates whether an event has occurred. In handover
algorithms, this parameter is used for moving the border of a cell.

Value range: -20~20


Physical unit: dB

Set this parameter through ADD UINTERFREQNCELL/MOD UINTERFREQNCELL.
176
Handover (Cont.)
HystForPrdInterFreq
Parameter name: HHO hysteresis
TimeToTrigForPrdInterFreq
Parameter name: HHO period trigger delay time
Recommended value: 0, namely 0ms
Page89
HystForPrdInterFreq

Content: Hysteresis for inter-frequency hard handover in periodical report mode. This
parameter is used to estimate the inter-frequency handover at the RNC. The larger the value of
this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong
effect can be resisted, but the speed of the handover algorithm to respond to signal change
becomes lower, and therefore event 2B might not be triggered in time.

Value range: 0~29


Physical unit: dB
TimeToTrigForPrdInterFreq

Content: Hysteresis for inter-frequency hard handover in periodical report mode. This
parameter is used to estimate the inter-frequency handover at the RNC. The larger the value of
this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong
effect can be resisted, but the speed of the handover algorithm to respond to signal change
becomes lower, and therefore event 2B might not be triggered in time.

Value range: 0~64000


Physical unit: ms
177
Event-triggered measurement report mode:

After receiving the event 2B measurement report, the RNC

starts the following procedure:
Add all the pilot cells that trigger event 2B to a cell set and arrange
the cells according to the measurement quality of CPICH_Ec/No in
descending order
Select the cells in turn from the cell set to perform inter-frequency
handover
Page90
2B event:
The estimated quality of the currently used frequency is

below a certain threshold and the estimated quality of a
non-used frequency is above a certain threshold
Event 2B is triggered on the basis of the following formula:

QNoused TNoused2b + H2b/2
QUsed TUsed2b - H2b/2
Page91
QNoused is the measured quality of the cell that uses the other frequencies.
178


H2b is the event 2B hysteresis value set through the parameter HystFor2B.
TNoused2b is the absolute quality threshold of the cell that uses the other frequencies. Based
on the service type and measurement quantity, this threshold can be configured through one of

TargetFreqCsThdEcN0

TargetFreqR99PsThdEcN0

TargetFreqHThdEcN0

TargetFreqCsThdRscp

TargetFreqR99PsThdRscp

TargetFreqHThdRscp
TUsed2b is the absolute quality threshold of the cell that uses the current frequency.
After the conditions of event 2B are fulfilled and maintained until the parameter
TimeToTrig2B is reached, the UE reports the event 2B measurement report message.
TUsed2b is set in the following way:

Based on the service type and measurement quantity, this threshold can be configured through
one of the following parameters:

If event 2D with the CPICH RSCP value is received by the RNC:

TUsed2b of event 2B with the CPICH RSCP value can be:
UsedFreqCSThdRSCP
UsedFreqR99PsThdRSCP
UsedFreqHThdRSCP

TUsed2b of event 2B with the CPICH Ec/No value is configured as the
maximum value 0dB.

According to 3GPP specifications, TUsed2b of event 2B with the CPICH
Ec/No value should be configured as the maximum value 0dB. If the event 2F
with the CPICH Ec/No value is received by the RNC and TUsed2b of event 2B
with the CPICH Ec/No value is modified, TUsed2b is reset to 0dB.

If event 2D with the CPICH Ec/No value is received by the RNC:

TUsed2b of event 2B with the CPICH Ec/No value can be:
UsedFreqCSThdEcN0
UsedFreqR99PsThdEcN0
UsedFreqHThdEcN0

TUsed2b of event 2B with the CPICH RSCP value is configured as the
maximum value 25 dBm.

According to 3GPP specification, TUsed2b of event 2B with the CPICH RSCP
value should be configured as the maximum value -25dBm. If event 2F with
the CPICH RSCP value is received by the RNC and TUsed2b of event 2B with
the CPICH RSCP value is modified, TUsed2b is reset to -25 dBm.
179
Handover (Cont.)
TargetFreqCsThdEcN0
Parameter name: Inter-freq CS target frequency trigger

Ec/No THD
UsedFreqCSThdEcN0
Parameter name: Inter-freq CS Used frequency trigger Ec/No

THD
Page93
TargetFreqCsThdEcN0

Content: Threshold of the target frequency for triggering inter-frequency measurement with
measurement quantity of Ec/No for CS domain services. For CS domain services, if the value
of inter-frequency measure report mode is set to EVENT_TRIGGER, this parameter is used to
set the measurement control of event 2B. One of the necessary conditions for triggering event
2B can be met only when the quality of the target frequency is higher than this threshold. If the
value of inter-frequency measure report mode is set to PERIODICAL_REPORTING, this
parameter is used to evaluate inter-frequency handovers at the RNC. .

Value range: -24~0


Physical unit: dB
UsedFreqCSThdEcN0

Content: Threshold of used frequency quality for triggering inter-frequency measurement with
measurement quantity of Ec/No for CS domain services. For CS domain services, if the value
of inter-frequency measure report mode is set to EVENT_TRIGGER, this parameter is used to
set the measurement control of event 2B. One of the necessary conditions can be met only
when the quality of the used frequency is lower than this threshold.

Value range: -24~0


Physical unit: dB
180
Handover (Cont.)
Recommended values of 2B event:

Objective
Target Cell
CS Ec/No threshold
-12, namely -12dB
-12, namely -12dB
PS Ec/No threshold
-12, namely -12dB
-12, namely -12dB
H Ec/No threshold
-12, namely -12dB
-12, namely -12dB
CS RSCP threshold
-92, namely -92dBm
-92, namely -92dBm
PS RSCP threshold
-92, namely -92dBm
-92, namely -92dBm
H RSCP threshold
-92, namely -92dBm
-92, namely -92dBm
Used Cell
Page94

Handover (Cont.)
HystFor2B
Parameter name: 2B hysteresis
TimeToTrig2B
Parameter name: 2B event trigger delay time
181
Page95
HystFor2B

Content: Hysteresis value for the event 2B. The value of this parameter correlates with
slow fading. The larger the value of this parameter, the stronger the capability of
resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the speed of
the handover algorithm to respond to signal change becomes lower, and therefore
event 2B might not be triggered in time.

Value range: 0~29


Physical unit: dB
TimeToTrig2B

Content: Time delay to trigger event 2B. The value of this parameter correlates with
slow fading. The larger the value of this parameter, the lower probability of incorrect
decision, but the slower the response of event 2B to the change of measured signals.

D640, D1280, D2560, D5000

2560, 5000

Physical unit: ms
182
QoS-based Inter-Frequency Handover
QoS-based Inter-Frequency Handover

If the service quality of the current cell deteriorates, the link stability
control algorithm makes a handover measurement decision.
Besides the triggering step, the rest 3 steps are the same with coverage-based
inter-frequency handover.
Link stability control algorithm:
When the uplink transmit power of the UE or downlink transmitted code
power of the NodeB exceeds the associated threshold:
for AMR, a fixed sequence of rate downsizing, inter-frequency
handover, and then inter-RAT handover are performed;
for VP, Inter-handover handover are performed;
for BE service, rate downsizing, inter-frequency handover, and then
inter-RAT handover are performed according to the configured
sequence.
Page97

183
Handover (Cont.)
UlQosAmrInterFreqHoSwitch
Parameter name: InterFreq HO For Switch For Uplink AMR
Recommended value: NO
DlQosAmrInterFreqHoSwitch
Parameter name: InterFreq HO For Switch For Downlink

AMR
UlQosAmrInterFreqHoSwitch
Content: Inter-frequency handover switch of link stability control for UL
QoS of AMR services. When the parameter is set to YES, inter-frequency
handover can be performed for AMR services to ensure the QoS.
Value range: NO, YES
Physical value range: No, Yes
DlQosAmrInterFreqHoSwitch
Content: Inter-frequency handover switch of link stability control for DL
QoS of AMR services. When the parameter is set to YES, inter-frequency
handover can be performed for AMR services to ensure the QoS.
Set these parameters through SET UQOSACT.

Page98
184
Handover (Cont.)
UlQosVpInterFreqHoSwitch
Parameter name: InterFreq HO Switch For Uplink VP
DlQosVpInterFreqHoSwitch
Parameter name: InterFreq HO Switch For Downlink VP
UlQosVpInterFreqHoSwitch
Content: Inter-frequency handover switch of link stability control for UL
QoS of VP services. When the parameter is set to YES, inter-frequency
handover can be performed for VP services to ensure the QoS.
DlQosVpInterFreqHoSwitch
Content: Inter-frequency handover switch of link stability control for DL
QoS of VP services. When the parameter is set to YES, inter-frequency
handover can be performed for VP services to ensure the QoS.

Page99
185
Handover (Cont.)
BeUlAct1/BeUlAct2/BeUlAct3
Parameter name: First/Second/Third Action For BE Uplink

QOS
Recommended value: RateDegrade/InterFreqHO/InterRatHO
BeDlAct1/BeDlAct2/BeDlAct3
Parameter name: First/Second/Third Action For BE Downlink

QOS
Content: The first/second/third action selected by the QoS control
algorithm when the UL QoS of BE service deteriorates. If QoS action is
RateDegrade, then the rate will be downsized to the full coverage rate
according to 3-rates rule.
Value range: None, RateDegrade, InterFreqHO, InterRatHO
Physical value range: None, RateDegrade, InterFreqHO, InterRatHO
algorithm when the DL QoS of BE service deteriorates. If QoS action is

Page100
186
Handover (Cont.)
DLQosMcTimerLen
Parameter name: Down Link Qos Measure timer length
ULQosMcTimerLen
Parameter name: Up Link Qos Measure timer length
Page101
DLQosMcTimerLen

Content: Timer length for downlink QOS measurement. This parameter controls the
time lengths for the inter-frequency and inter-RAT measurement based on QOS.
After inter-frequency or inter-RAT measurement starts, if no inter-frequency handover
is performed when this timer expires, the measurement is stopped, and the compressed
mode is deactivated, if any. If this parameter is set to 0, this indicates that the timer
will not be started.

Value range:0~512


Physical unit: s
ULQosMcTimerLen

Content: Timer length for uplink QOS measurement. This parameter controls the time
lengths for the inter-frequency and inter-RAT measurement based on QOS.
After inter-frequency or inter-RAT measurement starts, if no inter-frequency handover
is performed when this timer expires, the measurement is stopped, and the compressed
mode is deactivated, if any. If this parameter is set to 0, this indicates that the timer
will not be started.

Value range:0~512


Physical unit: s
Set these parameters through ADD UCELLQOSHO/ MOD UCELLQOSHO/ SET UQOSHO.
187
Load-based Inter-Frequency Handover
Page103
The load-based inter-frequency handover suits best in the case of the co-sited cells covering
the same area.

The Load Reshuffling (LDR) module directly determines whether the current cell is
overloaded and whether an inter-frequency handover needs to be performed. The LDR
module provides the target cell information for the current cell, and the RNC performs
the handover procedure.
188
The RNC decides to trigger an inter-frequency blind handover if the conditions are
met.

If the inter-frequency blind handover can be triggered, the RNC enters the
decision phase.

If the inter-frequency blind handover cannot be triggered, the RNC does not
perform the handover.

After the inter-frequency handover is triggered, the RNC chooses a decision algorithm
according to whether the conditions of direct blind handover are met.

If the conditions of direct blind handover are met, the RNC performs an interfrequency blind handover.

If the conditions of direct blind handover are not met, the RNC initiates a
measurement, and then, if all the conditions are met, the RNC performs the
handover.

The RNC performs the blind handover according to the decision result.

- Triggering Phase
Current cell
Heavy load
Target cell
Light load
Blind handover flag is true
Target user
User with lower integrated priority
Page104
Based on the service ARP, traffic class, channel type (R99 or HSPA), RNC will choose the
users with lower priority to execute handover.
The target cell of this inter-frequency handover is only the blind handover neighbor with light
load, which is indicated by the BlindHOFlag.
189
Handover (Cont.)
BlindHOFlag
Parameter name: Blind handover flag
Recommended value: False
Page105
BlindHOFlag

Content: Flag of target cell for blind handovers. This parameter indicates whether the
neighboring cell is the target cell for blind handovers. If the value is TRUE, blind
handovers can be performed to the neighboring cell.



Set this parameter through ADD UINTERFREQNCELL/ MOD
UINTERFREQNCELL.
190

- Decision Phase
Step 1: Based on the handover state, the RNC determines how to

trigger an inter-frequency blind handover:
Perform direct blind handover, go to step 2
Perform conditional blind handover, go to step 3
Do not perform blind handover
Step 2: The RNC check whether the conditions of direct blind

handover are met or not. If yes, UE perform direct blind handover.
Otherwise, go to step 3
Step 3: The RNC check whether the conditions of conditional blind

handover are met or not. If yes, UE perform conditional blind
handover. Otherwise, not perform blind handover
Step 1:
Page106
If the UE is not in soft handover state, the UE directly performs inter-frequency blind
handover based on load.
If the UE is in soft handover state, the UE operates based on the following conditions:

If the HO_ALGO_LDR_ALLOW_SHO_SWITCH is set to ON, the RNC determines
whether the cell that triggers LDR is the best cell.
If this cell is the best cell, the RNC initiates an intra-frequency measurement for
inter-frequency blind handover based on load.
If this cell is not the best cell, the RNC does not initiate an inter-frequency blind
handover based on load.

If the HO_ALGO_LDR_ALLOW_SHO_SWITCH is set to OFF, the RNC does not
initiate an inter-frequency blind handover based on load.
Step 2:
According to the parameter BlindHOQualityCondition, the RNC executes:

If the value of the parameter of a cell is -115dBm, the RNC performs direct blind
handover to this cell.

If there is no such cell with the parameter value -115dBm, the RNC initiates an intrafrequency measurement for conditional blind handover.

If the neighboring cells have the same BlindHOQualityCondition value, the RNC
chooses any one of them.
191
Step 3:
The inter-frequency cells with the same coverage area have the same
CPICH RSCP values. By measuring the CPICH RSCP of the cell, the
quality of the cells with the same coverage area can be determined, which
increases the probability of successful blind handover.
1. The RNC initializes the timer of intra-frequency measurement for blind
handover. The timer is specified by internal algorithm and need not be
configured.
2. The RNC initiates a periodical intra-frequency measurement. The
measurement report mode is set to periodical report.
The reporting period is BlindHOIntrafreqMRInterval.
The number of measurement reports is
BlindHOIntrafreqMRAmount.
The intra-frequency handover measurement quantity is CPICH
RSCP.
The list of measured cells contains only the cells that trigger LDR.
3. After receiving from the UE the intra-frequency measurement reports
for conditional blind handover, the RNC checks whether the following
condition is met: CPICH RSCP of the cell in the measurement report
BlindHOQualityCondition
If the condition is met, the RNC increments the counter of the
number of intra-frequency measurement reports for blind handover
by 1.
If the condition is not met, the RNC does not perform a blind
handover to the cell that triggers LDR and stops intra-frequency
measurement for blind handover.
4. When the counter reaches the value of BlindHOIntrafreqMRAmount,
the RNC initiates a blind handover to the cell that triggers LDR.
5. If the counter does not reach this value, the RNC waits for the next
intra-frequency measurement report from the UE.
6. If the timer of intra-frequency measurement for blind handover expires,
the RNC does not perform a blind handover to the cell that triggers LDR
and stops intra-frequency handover measurement for blind handover.
192
Handover (Cont.)
HO_ALGO_LDR_ALLOW_SHO_SWITCH
Parameter name: HandOver switch
Parameter name: Blind handover condition
Page108
HO_ALGO_LDR_ALLOW_SHO_SWITCH
Content: When the switch is on, the LDR inter-frequency handover is allowed during

soft handover.




Content: Blind handover condition. If the value is not -115, the handover is defined as
Conditional Blind HO, which is used for the inter-frequency neighboring cells of the
same coverage. If the value is -115, the handover is defined as Direct Blind HO, which
is used for the inter-frequency neighboring cells of larger coverage.



Physical unit: dBm

Set this parameter through ADD UINTERFREQNCELL/ MOD
UINTERFREQNCELL.
193
Handover (Cont.)
BlindHOIntrafreqMRInterval
Parameter name: Intrafrequency measurement report

interval of blind HO
BlindHOIntrafreqMRAmount
Parameter name: Intrafrequency measurement report

amount of blind handover
Recommended value: D2, namely 2 times
Page109
BlindHOIntrafreqMRInterval

Content: This parameter specifies the intra-frequency measurement report interval of blind
handover. It determines the intra-frequency measurement reporting interval of Load
Reshuffling (LDR) blind handover. The smaller the value of this parameter, the smaller the
intra-frequency measurement reporting interval, and the smaller the time for intra-frequency
measurement. But the greater the influence of signal fluctuation, which can result in wrong
handover. On the contrary, the larger the value of this parameter, the longer the intrafrequency measurement reporting interval, and the less the influence of signal fluctuation,
which can improve the possibility of successful blind handover. But if the time for intrafrequency measurement becomes long, the handover may not be performed timely.

Value range: D250, D500


Physical unit: ms
BlindHOIntrafreqMRAmount

Content: This parameter is used in the algorithm of the load reshuffling (LDR) intra-frequency
blind handover. This parameter defines how many measurement reports are needed for making
the blind handover decision. The RNC starts blind handover only if the UE continuously
reports adequate intra-frequency measurement reports that meet the quality requirements of
blind handover. During the measurement process, if the UE reports an unqualified
measurement report, the process ends. And the RNC does not start blind handover on the
target cell.

Value range: D1, D2, D4, D8

Physical value range: 1, 2, 4, 8
Set these parameters through SET UINTRAFREQHO.
194
Speed-based Inter-Frequency Handover
Speed-based Inter-Frequency
Handover
Page111

The RNC receives the handover request according to the HCS speed estimation. The
handover based on HCS speed estimation is of two types: handover from the macro
cell to the micro cell and handover from the micro cell to the macro cell. For different
types of handover, the RNC acts differently.
In the measurement and decision phases:

If the handover is performed from a macro cell to a micro cell, the RNC sends an
inter-frequency measurement control message. After the UE reports event 2C, the
RNC performs the handover decision. For inter-RAT handover, the UE reports event
3C.

If the handover is performed from a micro cell to a macro cell, the RNC directly
performs blind handover, ignoring the measurement procedure.

The RNC initiates a handover procedure.
195
If the handover is performed from a micro cell to a macro cell and the target cell of
blind handover is configured (through the parameter BlindHOFlag), the RNC
performs blind handover to the target cell.
If the blind handover fails or the handover is performed from a macro cell to a micro
cell, the RNC starts the inter-frequency (or inter-RAT) measurement procedure. If the
inter-frequency measurement mode is employed, the RNC performs the interfrequency handover procedure to the cell with the best quality after receiving event 2C
from the UE.
Decision of Micro Cell to Macro Cell

Handover
The RNC selects the neighboring cells with a lower HCSPrio to

generate a cell set. If there are neighboring cells with several
candidate frequencies, then the RNC selects one of the frequencies
randomly
The RNC searches for neighboring cells for blind handover according
to BlindHOFlag
The RNC chooses a neighboring cell whose BlindHOQualityCondition

value is the smallest for blind handover
The RNC determines whether the target cell supports the current
service. If the target cell does not support the current service, the RNC
does not perform the blind handover
196
Page112
Decision of Macro Cell to Micro Cell

Handover
Add all the pilot cells that trigger event 2C to a cell set
and arrange the cells according to the measurement

quality in descending order
Select the cells in turn from the cell set to perform inter-
frequency handover

Page113
Event 2C is only used in Speed-based inter-frequency handover.

After RNC believe the UE is in low-speed state, RNC will start handover from
the macro cell to the micro cell. The RNC triggers compressed mode firstly, then
sends an inter-frequency measurement control message for 2C event to start the
inter-frequency measurement procedure.
Decision of Macro Cell to Micro Cell

Handover (Cont.)
2C event:
The estimated quality of a non-used frequency is above a

certain threshold

QNoused TNoused2c + H2c/2
197
Page114

QNoused is the measured quality of the cell that uses the other frequencies.
TNoused2c is the absolute quality threshold of the cell that uses the other
frequencies, namely, InterFreqNCovHOThdEcN0.
H2c is the event 2C hysteresis value Hystfor2C.
After the conditions of event 2C are fulfilled and maintained until the parameter
TrigTime2C is reached, the UE reports the event 2C measurement report
message.
2C Event only takes the CPICH Ec/No as the measurement quantity.
Handover (Cont.)
InterFreqNCovHOThdEcN0
Parameter name: Inter-freq measure target frequency

trigger Ec/No THD
Hystfor2C
TrigTime2C
Page115
InterFreqNCovHOThdEcN0
Content: Threshold of signal quality of the target frequency for triggering interfrequency measurement. This parameter is used to set measurement control on the
event 2C. The event 2C is triggered when the signal quality of the target frequency is
above this threshold.
Value range: -24~0
Physical unit: dB

198
2C hysteresis
Content: Hysteresis value for the event 2C. The value of this parameter correlates with
resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the speed of
the handover algorithm to respond to signal change becomes lower, and therefore
event 2C might not be triggered in time.
Value range: 0~29
Physical unit: dB
TrigTime2C
Content: Time delay to trigger the event 2C. The value of this parameter correlates
with slow fading. The larger the value of this parameter, the lower probability of
incorrect decision, but the slower the response of event 2C to the change of measured
signals. .
Value range D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,
D640, D1280, D2560, D5000
2560, 5000
Physical unit: ms
Set these parameters through ADD UCELLINTERFREQHONCOV/ MOD
UCELLINTERFREQHONCOV/ SET UINTERFREQHONCOV.

199
Blind Handover based on Event 1F
Blind Handover based on Event

1F
Blind handover in inter-frequency handover:

Load-based handover
Speed-based handover from micro cell to macro cell
1F event triggered inter-frequency handover

Page117
1F event is a intra-frequency measurement event, like as 1A,1B,1C,1D.

Events 1A,1B,1C,1D are used to trigger intra-frequency handover, however event 1F only
trigger inter-frequency or Inter-RAT blind handover.
When there is only one cell in the active set, the RNC performs inter-frequency blind
handover after receiving event 1F.
When the UE is in soft handover state, the procedure of blind handover decision and
execution based on event 1F is as follows:

The RNC determines whether the cell that reports event 1F is the best cell. If the cell is
not the best cell, the RNC does not initiate a blind handover.

If the cell is the best cell, and the CPICH_RSCP of the cell is smaller than or equal to
BlindHORSCP1FThreshold, the RNC searches for neighboring cells for blind
handover according to BlindHOFlag.

If there are many neighboring cells, the RNC chooses a neighboring cell whose
BlindHOQualityCondition value is smallest for blind handover.

If the neighboring cells have the same BlindHOQualityCondition value, the RNC
chooses any one of them.
200
Blind Handover based on Event 1F

(Cont.)
1F event:
A PCPICH becomes worse than an absolute threshold

MOld T1f - H1f/2

Page118
MOld is the measurement value of the cell that becomes worse.

T1f is an absolute threshold. It is set through the parameter
IntraAblThdFor1FRSCP or IntraAblThdFor1FecNo.
H1f is the event 1F hysteresis value set through the parameter Hystfor1F.
After the conditions of event 1F are fulfilled and maintained until the parameter
TrigTime1F is reached, the UE reports the event 1F measurement report
message.
201
Handover (Cont.)
IntraAblThdFor1FecNo
Parameter name: 1F event absolute EcNo threshold
IntraAblThdFor1FRSCP
Parameter name: 1F event absolute RSCP threshold
Page119
IntraAblThdFor1FecNo
Content: This parameter specifies the Ec/No absolute threshold of event 1F in the SHO
algorithm, corresponding to the guarantee signal strength with QoS of basic service. The
emergency blind handover is a special occasion that requires on-site measurements on the
scope of the pilot strength of the best cell at the location where the blind handover is triggered.
Generally, this function need not be started, so the parameter is set to the lowest value by
default, indicating that the blind handover is not triggered. The larger the set value is, the more
easily the event 1F can be triggered. The smaller the set value is, the more difficultly the event
1F can be triggered.

Value range: -24~0


Physical unit: dB

IntraAblThdFor1FRSCP

Content: This parameter specifies the RSCP absolute threshold of event 1F in the SHO
algorithm, corresponding to the guarantee signal strength with the QoS of basic service. The
emergency blind handover is a special occasion that requires on-site measurements on the
scope of the pilot strength of the best cell at the location where the blind handover is triggered.
Generally, this function need not be started, so the parameter is set to the lowest value by
default, indicating that the blind handover is not triggered. The larger the set value is, the more
easily the event 1F can be triggered. The smaller the set value is, the more difficultly the event
1F can be triggered.


Physical value range: -115~-25 ; step: 1

Physical unit: dBm
UCELLINTRAFREQHO.
202
Handover (Cont.)
Hystfor1F
Parameter name: 1F hysteresis
TrigTime1F
Parameter name: 1F event trigger delay time
BlindHORSCP1FThreshold
Parameter name: 1F event blind handover trigger condition
Hystfor1F
Content: This parameter specifies the hysteresis value for event 1F. The value of this
in time.
Value range: 0~15
Physical unit: dB
TrigTime1F
Content: This parameter specifies the time delay to trigger 1F. The value of this
D640, D1280, D2560, D5000
Physical value range: 0,10,20,40,60,80,100,120,160,200,240,320,640,1280,2560,5000
Physical unit: ms
BlindHORSCP1FThreshold
Content: This parameter specifies the quality threshold for the event 1F reported cell to
trigger blind handover. This parameter defines the lowest quality threshold of the
emergency blind handover. The blind handover is implemented only if the signal
quality in the cell, which reports event 1F, exceeds the specified threshold. Otherwise,
the report will be discarded. This parameter is set to raise the possibility of successful

Page120
203
blind handover. If the signal quality in the cells that report event 1F are all very poor,
this indicates that the user is located at the edge of coverage area. Under this condition,
if the blind handover is initiated rashly, the possibility of call drop increases.
Physical unit: dBm
UCELLINTRAFREQHO.

Inter-Frequency anti-Ping-Pong
Inter-Frequency anti-Ping-Pong
When a coverage-based inter-frequency handover or an

inter-frequency blind handover based on event 1F occurs,
the RNC starts the timer specified by
IFAntiPingpangTimerLength for the UE

When a non-coverage-based inter-frequency handover is

triggered, first, the RNC determines whether the timer
specified by IFAntiPingpangTimerLength expires
If the timer does not expire, the RNC cancels the handover
If the timer expires, the RNC performs the handover
Page122
After an inter-frequency handover based on coverage or an inter-frequency blind

handover based on event 1F occurs, the RNC starts the anti-ping-pong algorithm
to prevent frequent switching between inter-frequency handovers triggered by
different causes.
204
Handover (Cont.)
IFAntiPingpangTimerLength
Parameter name: The timer length of anti pingpong NCOV

interfreq handover
Page123
IFAntiPingpangTimerLength
Content: After the coverage based handover succeeds, to avoid the
handover of the UE to another frequency due to the following factors:
overload, speed estimation, MBMS channel reselection, and QoS,
frequent handovers occur. The RNC will start the inter-frequency noncoverage based anti-ping-pong timer and prohibit the handover or
measurement caused by the previous factors before the timeout of the
timer. The larger this parameter, the better effect the anti-frequent
handover. This, however, will affect the management policy of the cell or
the quality of service felt by the users; the smaller this parameter, the
more frequent the inter-frequency handover.
Value range: 0~120
Physical unit: s
Set this parameter through SET UHOCOMM.

205
Inter-Frequency Handover Retry
Inter-Frequency Handover Retry

If an inter-frequency handover based on event-triggered

measurement report mode fails, the RNC initiates the
inter-frequency handover attempt according to an interfrequency retry algorithm:
After the inter-frequency handover fails, the retry timer for

the cell is started
After the retry timer expires, the UE makes a handover
attempt to the cell again until the retry number exceeds the
maximum allowed retry number. If the handover succeeds
or two new event 2B/2C reports are received, the periodical
retry is stopped
For the inter-frequency handover based on coverage or QoS, the following two
parameters determine the retry period and the maximum number of retry times:
Retry timer: PeriodFor2B
Maximum number of retry times: AmntOfRpt2B
For the inter-frequency handover based on speed, the following two parameters
determine the retry period and the maximum number of retry times:
Retry timer: PeriodFor2C
Maximum number of retry times: AmntOfRpt2C

Page125

206
Handover (Cont.)
PeriodFor2B
Parameter name: 2B event retry period
AmntOfRpt2B
Parameter name: 2B event retry max times
Recommended value: 4, namely 4 times
Page126
PeriodFor2B

Content: 2B event retry period. This parameter defines the length of the event 2B retry period.
The smaller the value of this parameter, the more frequent the handover retry due to interfrequency handover failure, and the faster the UE to be successfully handed over to the target
cell whose load is restored, thus lowering the probability of call drops. In this case, however,
frequent handover retry brings more load to the RNC system.

Value range: 1~64


Physical unit: ms
AmntOfRpt2B

Content: Maximum number of times for event 2B retry. This parameter defines the number of
times for event 2B retry when the measurement control is valid. The larger the value of this
parameter, the larger the number of times for inter-frequency handover retry, and the higher
probability for the UE to be successfully handed over to the target cell whose load is restored.
After the maximum number of times for event 2B retry, the RNC sends the inter-frequency
measurement control message again to hand over the UEs to the other cells of this frequency.
If the measurement control message is released, the retry will be immediately stopped.

Value range: 0~63

Physical value range: 0~62, 63: Infinity; step: 1
Set these parameters through SET UINTRERFREQHOCOV/ ADD UCELLINTERFREQHOCOV/
MOD UCELLINTERFREQHOCOV.
207
Handover (Cont.)
PeriodFor2C
Parameter name: 2C event retry period
AmntOfRpt2C
Parameter name: 2C event retry max times
Page127
PeriodFor2C

Content: Retry period for the event 2C. This parameter defines the length of the event 2C retry
period. The smaller the value of this parameter, the more frequent the handover retry due to
inter-frequency handover failure, and the faster the UE to be successfully handed over to the
target cell whose load is restored. In this case, however, frequent handover retry brings more
load to the RNC system.

Value range: 1~64


Physical unit: ms
AmntOfRpt2C

Content: Maximum retry times of the event 2C. This parameter defines the number of times
for event 2C retry when the measurement control is valid. The larger the value of this
parameter, the larger the number of times for inter-frequency handover retry, and the higher
probability for the UE to be successfully handed over to the target cell whose load is restored.
When the retry times reaches the maximum value, the RNC stops the retry process. Or if the
measurement control message is released, the retry will be immediately stopped.

Value range: 0~63

Set these parameters through SET UINTRERFREQHONCOV/ ADD UCELLINTERFREQHONCOV/
MOD UCELLINTERFREQHONCOV.
208
Signaling Procedures for Inter-Frequency Handover
Signaling Procedures for InterFrequency Handover

Intra-RNC inter-frequency handover:
209
Page129
Signaling Procedures for InterFrequency Handover (Cont.)

Inter-RNC inter-frequency handover:
210
Page130
Inter-RAT Handover
Inter-RAT Handover Scenarios
Page133
Inter-RAT handover refers to the handover performed between 3G network and

2G network. Inter-RAT handover provides continuous coverage, load sharing,
and HCS services, which fully utilizes the existing 2G network resources and
thus reduces operator's cost.
In this handover, however, GSM and UMTS dual-mode UEs (MSs) are required,
and both the GSM MSC and the GSM BSS must be upgraded.
211
Inter-RAT Handover Types

Based on the triggering causes of handover, interfrequency handover can be categorized into five types:
Coverage-based 3G to 2G handover
QoS-based 3G to 2G handover
Load-based 3G to 2G handover
Service-based 3G to 2G handover
Speed-based 3G to 2G handover
Page134
Coverage-based 3G to 2G handover:

The coverage of the 3G network is incontinuous at the initial stage. On the border of
the coverage, the poor signal quality of the 3G network triggers the 3G-to-2G
measurement. If the signal quality of the 2G network is good enough and all the
services of the UE are supported by the 2G network, the coverage-based 3G to 2G
handover is triggered.
QoS-based 3G to 2G handover:

According to the Link Stability Control Algorithm, the RNC needs to trigger the QoSbased 3G to 2G handover to avoid call drops.
Load-based 3G to 2G handover:

If the load of the 3G network is heavy and all the RABs of the UE are supported by the
2G network, the load-based 3G to 2G handover is triggered.
Service-based 3G to 2G handover:

Based on layered services, the traffic of different classes is handed over to different
systems. For example, when an Adaptive Multi Rate (AMR) speech service is
requested, this service can be handed over to the 2G network.
Speed-based 3G to 2G handover:

The principles of the 3G-to-2G handover based on HCS speed estimation are similar to
those of inter-frequency handover.
212
Inter-RAT Handover Preconditions

Before handover, the RNC checks whether all the

following preconditions for the 3G to 2G handover are
met:
2G cell capability
Service capability
UE capability
Service handover indicator
Page135
2G cell capability:

2G cell capability is configured through the parameter RATCELLTYPE. This
parameter indicates whether the cell supports the GSM, GPRS, or EDGE.

For more detailed information, please refer to the ADD UEXT2GCELL command.
Service capability:

The required 2G capability (Req2GCap) specifies the capability of 2G cells required
by inter-RAT handover. This indicates whether the service is supported by the GSM,
GPRS, or EDGE.

For more detailed information, please refer to the ADD UTYPRABBASIC command.
UE capability:

Upon the reception of the UE capability information message, the RNC decides
whether to start the inter-RAT measurement. The information indicates whether the
UE supports the GSM, GPRS, or EDGE.
213
Service handover indicator:

The IE service handover indicator indicates the CN policy for the service handover to the 2G
network. This IE is indicated in the Radio Access Bearer (RAB) assignment signaling
assigned by the CN, or in the following table configured in the RNC by default.

The algorithm switch HoSwitch: HO_INTER_RAT_RNC_SERVICE_HO_SWITCH decides
whether the service attribute of inter-RAT handover is based on the RNC or the CN.

If the switch is set to on, the service attribute of inter-RAT handover is based on the
parameter configured on the RNC side.

If the switch is set to off, the service attribute of inter-RAT handover is first based on
the CN when the indicator is contained in the RAB assignment signaling assigned by
the CN. If the CN does not allocate a service indicator, the service attribute of interRAT handover is based on the RNC side.

For more detailed information, please refer to the SET UCORRMALGOSWITCH
command.

Through the SHIND parameter, the service handover indicators are set as follows:

HO_TO_GSM_SHOULD_BE_PERFORM: means that the handover to the 2G
network is performed when 2G signals are available.

HO_TO_GSM_SHOULD_NOT_BE_PERFORM: means that the handover to the 2G
network is performed when 3G signals are weak but 2G signals are strong.

HO_TO_GSM_SHALL_NOT_BE_PERFORM: means that the handover to the 2G
network is not performed even when 3G signals are weak but 2G signals are strong.

For more detailed information, please refer to the ADD UTYPRABBASIC command.
214
Inter-RAT Handover Rules

Rules for coverage-based and QoS-based 3G to 2G

Handover:

HO_TO_GSM_SHOULD_BE_PERFORM
HO_TO_GSM_SHOULD_NOT_BE_PERFORM
Three types of capability:

Refer to the following table
215
Page137
Inter-RAT Handover Rules (Cont.)

Rules for Load-based 3G to 2G Handover:



Refer to the following table
216
Page138
Inter-RAT Handover Rules (Cont.)

Rules for service-based 3G to 2G Handover

Service Handover Indicator


Refer to the table of load-based handover
Service switch
Page139
To perform the service-based 3G to 2G handover, the RNC must turn on the

related switches for services in the CS and PS domains.
When a single CS service is initially set up by the UE, the RNC allows the
3G to 2G service-based handover if CSServiceHOSwitch is set to on.
When a single PS service is initially set up by the UE, the RNC allows the
service-based 3G-to-2G handover if PSServiceHOSwitch is set to on.
For the CS and PS combined services, no service-based handover is
triggered.
For more detailed information, please refer to the ADD
UCELLHOCOMM command.
217
Coverage-based Inter-RAT Handover
Page141

The RNC requests the UE to measure through an inter-RAT measurement control
message. If the CPICH Ec/No or CPICH RSCP of the current cell is lower than the
corresponding threshold, the UE reports event 2D.

The RNC sends an inter-RAT measurement control message to the UE, requesting the
NodeB and UE to start the compressed mode. The RNC also requests the UE to
perform the inter-RAT measurement.

In this phase, the method of either periodical measurement report or event-triggered
measurement report can be used.

After the UE reports event 3A, the RNC performs the handover. Otherwise, the UE
periodically generates measurement reports, and the RNC makes a decision after
evaluation.
218
The RNC executes the handover procedure.
Coverage-based Inter-RAT Handover Triggering Phase

Triggering event:
2D event:
The estimated quality of the currently used frequency is below a

certain threshold
2F event:
The estimated quality of the currently used frequency is above a

certain threshold
Page142
When the estimated quality or strength of the currently used frequency is below
a certain threshold,2D event will be triggered. Then RNC will initiate the
compressed mode to start inter-RAT handover measurement.
During compressed mode, if the estimated quality or strength of the currently
used frequency is above a certain threshold, 2F event will be triggered. Then
RNC will stop the compressed mode.
219

Events
2D event:

QUsed TUsed2d - H2d/2

QUsed is the measurement value of the cell at the currently used frequency.
TUsed2d is the absolute quality threshold of the cell at the currently used
can be configured through the following parameters:
InterRATCSThd2DEcN0
InterRATR99PsThd2DEcN0
InterRATHThd2DEcN0
InterRATCSThd2DRSCP
InterRATR99PsThd2DRSCP
InterRATHThd2DRSCP
H2d is the event 2D hysteresis value set through the parameter HystFor2D.
When the conditions for event 2D are met and maintained in time-to-trigger
specified by the parameter TimeToTrig2D, the UE sends the measurement report
of event 2D.
Any of the Ec/No and RSCP measurement result can trigger the 2D event.

Page143
220
Parameters of Inter-RAT Handover

Recommended values of 2D event:

Parameter
Recommended Value
InterRATCSThd2DEcN0
-14, namely -14dB
InterRATR99PsThd2DEcN0
-15, namely -15dB
InterRATHThd2DEcN0
-15, namely-15dB
InterRATCSThd2DRSCP
-100, namely -100dBm
InterRATR99PsThd2DRSCP
InterRATHThd2DRSCP
HystFor2D
4, namely 2dB
TimeToTrig2D
D320, namely 320ms
Page144
The parameters for inter-RAT handover 2D are similar with inter-frequency

handover.
Set above parameters through ADD UCELLINTERRATHOCOV/ MOD
UCELLINTERRATHOCOV/ SET UINTERRATHOCOV.
221

Events (Cont.)
2F event:

QUsed TUsed2f + H2f/2

TUsed2f is the absolute quality threshold of the cell at the currently used
can be configured through the following parameters:
InterRATCSThd2FEcN0
InterRATR99PsThd2FEcN0
InterRATHThd2FEcN0
InterRATCSThd2FRSCP
InterRATR99PsThd2FRSCP
InterRATHThd2FRSCP
H2f is the event 2F hysteresis value set through the parameter HystFor2F.
When the conditions for event 2F are met and maintained in time-to-trigger
specified by TrigTime2F, the UE sends the measurement report of event 2F.
Any of Ec/No and RSCP measurement result can trigger the 2F event.
Conditions of event 2F are as follows: TUsed2d - H2d/2 < TUsed2f + H2f/2, for
example, (InterRATCSThd2DEcN0HystFor2D/2) < (InterRATCSThd2FEcN0+
HystFor2F/2).

Page145
222

(Cont.)
Recommended values of 2F event:

Parameter
Recommended Value
InterRATCSThd2FEcN0
-12, namely -12dB
InterRATR99PsThd2FEcN0
-13, namely -13dB
InterRATHThd2FEcN0
-13, namely-13dB
InterRATCSThd2FRSCP
-97, namely -97dBm
InterRATR99PsThd2FRSCP
InterRATHThd2FRSCP
HystFor2F
4, namely 2dB
TimeToTrig2F
D1280, namely 1280ms
Page146
The parameters for inter-RAT handover 2F are similar with inter-frequency

handover.
Set above parameters through ADD UCELLINTERRATHOCOV/ MOD
223
Interoperability between Inter-RAT and

Inter-Frequency Handover
Inter-frequency measurement:
2D, 2F event
Inter-frequency neighboring cell
Inter-RAT measurement:
2D, 2F event
Inter-RAT neighboring cell
Measure
inter-frequency
neighbor?
Measure interRAT neighbor?
Page147
During the coverage-based and QoS-based 3G to 2G handover, the measurements on both

inter-frequency and inter-RAT neighboring cells can be made, which enables the cells to
provide continuous coverage and high quality.
The preconditions for the measurements are as follows:

Both inter-frequency and inter-RAT neighboring cells are available.

InterFreqRATSwitch is set to SIMINTERFREQRAT.
If InterFreqRATSwitch is set to:

Inter-frequency measurement (INTERFREQ), the RNC allows the UE to perform only
this type of measurement.

Inter-RAT measurement (INTERRAT), the RNC allows the UE to perform only this
type of measurement.

Concurrent inter-frequency and inter-RAT measurement (SIMINTERFREQRAT), the
RNC allows the UE to perform both types of measurement at the same time.
During the concurrent inter-frequency and inter-RAT measurement, the values of the
parameter CoexistMeasThdChoice for event 2D are chosen as follows:

When the value COEXIST_MEAS_THD_CHOICE_INTERFREQ is chosen, the
inter-frequency measurement threshold for event 2D is used.

When the value COEXIST_MEAS_THD_CHOICE_INTERRAT is chosen, the interRAT measurement threshold for event 2D is used.
224

(Cont.)
InterFreqRATSwitch
Parameter name: Inter-freq and Inter-RAT coexist switch
Recommended value: SIMINTERFREQRAT
CoexistMeasThdChoice
Parameter name: InterFreq and InterRat coexist measure

threshold choice
Recommended value:
COEXIST_MEAS_THD_CHOICE_INTERFREQ
Page148
InterFreqRATSwitch

Content: Cell-level switch for inter-frequency and inter-RAT handover.
INTERFREQ: only measuring inter-frequency cells and performing inter-frequency handover.
INTERRAT: only measuring GSM cells and performing inter-RAT handover .
SIMINTERFREQRAT: measuring both inter-frequency and inter-RAT cells, performing interfrequency or inter-RAT handover according to the type of the cell that first meets the handover
decision condition.

Value range: INTERFREQ, INTERRAT, SIMINTERFREQRAT

Physical value range: Inter-frequency handover only, Inter-RAT handover only, Interfrequency and Inter-RAT handover
CoexistMeasThdChoice

Content: Type of event 2D/2F measurement thresholds when inter-frequency and inter-RAT
measurements coexist.
COEXIST_MEAS_THD_CHOICE_INTERFREQ: choosing the inter-frequency oriented
parameters as event 2D/2F measurement thresholds for inter-frequency measurement.
COEXIST_MEAS_THD_CHOICE_INTERRAT: choosing the inter-RAT oriented parameters
as event 2D/2F measurement thresholds for inter-RAT measurement.

Value range: COEXIST_MEAS_THD_CHOICE_INTERFREQ,
COEXIST_MEAS_THD_CHOICE_INTERRAT

Physical value range: Choosing the inter-frequency oriented parameters, Choosing the interRAT oriented parameters
Set these parameters through SET UHOCOMM/ ADD UCELLHOCOMM/ MOD UCELLHOCOMM.
225
Coverage-based Inter-RAT Handover Measurement Phase

RNC
UE
Measurement report (2D)

Physical Channel Recfg (CM)
Physical Channel Recfg Complet (CM)
Measurement control (RSCP or Ec/No)
Page149
When the UE enters the compressed mode, RNC will trigger the inter-RAT handover measurement by
one measurement control signaling, so as to request UE test inter-RAT neighbor cell.
In this Measurement control message, RNC should inform the UE inter-RAT measurement parameters,
including neighbor list and reporting mode as well.
Coverage-based Inter-RAT Handover Measurement Phase (Cont.)

Measurement report:
UE
RNC
UE
RNC
Measurement report
Measurement report (3A)
Measurement report
Measurement report
Handover
Handover
Event Reporting
Periodical Reporting
Page150
The measurement report mode of inter-RAT handover is configured through the parameter
InterRatReportMode. By default, periodically reporting is recommended.
226

Based on the measurement control message received from the RNC, the UE periodically reports the
measurement quality of the target cell. Then, based on the measurement report, the RNC makes the
handover decision and performs handover.
If the reporting mode is periodically reporting: UE only test the Inter-RAT neighbor RSSI only.
If the reporting mode is event trigger reporting: UE test the Inter-RAT neighbor RSSI and current cell
Ec/No or RSCP:

In coverage-based 3G to 2G handover, the event 3A measurement quantity is set through the
parameter MeasQuantityOf3A.

In QoS-based 3G to 2G handover, the event 3A measurement quantity is set through the
parameter UsedFreqMeasQuantityForQos3A.

(Cont.)
InterRatReportMode
Parameter name: Inter-RAT report mode
Recommended value: PERIODICAL_REPORTING
InterRATPeriodReportInterval
Parameter name: Inter-RAT period report interval
Page151
InterRatReportMode

Content: Inter-RAT measurement report mode.
When PERIODICAL_REPORTING is selected, you can infer that periodical inter-RAT
measurement report is adopted; when EVENT_TRIGGER is selected, you can infer that eventtriggered inter-RAT measurement report is adopted.

Value range: PERIODICAL_REPORTING, EVENT_TRIGGER

Physical value range: Periodical reporting, Event trigger
InterRATPeriodReportInterval

Content: Interval that the UE reports inter-RAT measurement results to the RNC. In periodical
report mode, the interval between two reports is the configured value. That is, the UE submits
reports at intervals of the configured time.

Value range: NON_PERIODIC_REPORT, D250, D500, D1000, D2000, D3000, D4000,
D6000, D8000, D12000, D16000, D20000, D24000, D28000, D32000, D64000
227
Physical value range: Non periodical reporting, 250, 500, 1000, 2000, 3000, 4000, 6000, 8000,
12000, 16000, 20000, 24000, 28000, 32000, 64000

Physical unit: ms
Set these parameters through ADD UCELLINTERRATHOCOV/ MOD UCELLINTERRATHOCOV/
SET UINTERRATHOCOV.

(Cont.)
InterRATMeasTime
Parameter name: Inter-RAT measure timer length
MeasQuantityOf3A
Parameter name: 3A Measure Quantity
Recommended value: Auto, namely based on the 2D
Page152
InterRATMeasTime

Content: Timer length for inter-RAT measurement. After inter-RAT measurement
starts, if no inter-RAT handover is performed when this timer times out, the inter-RAT
measurement is stopped. In addition, the compressed mode is deactivated, if any; If the
value is 0, you can infer that the inter-RAT measurement timer is not started.

Value range: 0~512


Physical unit: s
MeasQuantityOf3A

Content: Measurement quantity used in coverage-based inter-RAT measurement in
event 3A-triggered reporting mode.
CPICH_Ec/No indicates that the Ec/No measurement quantity is used for event 3A
measurement. The physical unit is dB.
CPICH_RSCP indicates that the RSCP measurement quantity is used for event 3A
measurement. The physical unit is dBm.
AUTO indicates that the Ec/N0 measurement quantity is used for event 3A
measurement if RNC receives the Ec/No 2D firstly; the RSCP measurement quantity
is used for event 3A measurement if RNC receives the RSCP 2D firstly.
228
This parameter can be configured only when InterRatReportMode is set to

EVENT_TRIGGER.

Value range: CPICH_EC/NO, CPICH_RSCP, AUTO

Physical value range: CPICH_EC/NO, CPICH_RSCP, AUTO
Set these parameters through ADD UCELLINTERRATHOCOV/ MOD
Coverage-based Inter-RAT Handover Decision Phase

The coverage-based and QoS-based 3G to 2G handover is

categorized into two types according to the following
two measurement report modes:
Periodical measurement report mode
Event-triggered measurement report mode
Each mode corresponds to a different decision and

execution procedure
229
Page153
Coverage-based Inter-RAT Handover Decision Phase (Cont.)


RNC decide whether the quality of 2G cells meets the conditions of

inter-RAT handover. The evaluation formula is listed below:
Start the evaluation of the cells that meet the quality requirement
and start the time-to-trigger timer. If the measurement report
meet the following formula and time-to-trigger timer does not
expire, stop the time-to-trigger timer
Mother_RAT + CIOother_RAT Tother_RAT + H/2
Mother_RAT + CIOother_RAT < Tother_RAT - H/2
Select the cells in sequence, that is, from high quality cells to low
quality ones, to initiate 3G to 2G handover in the cells where the
handover time-to-trigger timer expires

Page154
Mother_RAT is the measurement result of inter-RAT handover (RSSI) received by the RNC.
CIOother_RAT is the cell individual offset value of the target cell. It is equal to the sum of
CIO and CIOOffset.
Tother_RAT is the decision threshold of inter-RAT hard handover.Based on the service type
and measurement quantity, this threshold can be configured through the following parameters:

TargetRatCsThd

TargetRatR99PsThd

TargetRatHThd
These thresholds are the same as the quality threshold of event 3A.
H is the inter-RAT handover hysteresis value set through HystforInterRAT.
The length of the time-to-trigger timer is configured through the parameter
TimeToTrigForVerify (with BSIC acknowledged, and it is the default setting) or the parameter
TimeToTrigForNonVerify (with BSIC unacknowledged).
230

(Cont.)
CIO
CIOOffset
Page155
CIO
Content: This parameter is used for the inter-RAT handover decision in combination
with the neighboring cell oriented CIO. The larger the sum, the higher the handover
priority of the GSM cell. The smaller the sum, the lower the handover priority of the
GSM cell. The parameter is generally set to 0.

Value range: -50~50


Physical unit: dB

Set this parameter through ADD UEXT2GCELL/ MOD UEXT2GCELL.
CIOOffset

Content: This parameter is used for decision making for the inter-RAT handover. The
larger the value of the parameter, the higher the handover priority of the GSM cell.
The smaller the value of the parameter, the lower the handover priority of the GSM
cell.

Value range: -50~50


Physical unit: dB

Set this parameter through ADD U2GNCELL/ MOD U2GNCELL.
231

(Cont.)
HystforInterRAT
Parameter name: Inter-RAT hysteresis
TimeToTrigForVerify
Parameter name: Time to trigger for verified GSM cell
TimeToTrigForNonVerify
Parameter name: Time to trigger for non-verified GSM cell
Page156
HystforInterRAT
Content: Hysteresis value for inter-RAT measurement periodical reports. This
parameter aims to prevent the mis-decision caused by unexpected jitters of signals
during inter-RAT handover decisions. The HystforInterRAT and the inter-RAT
handover decision threshold determine whether to trigger inter-RAT handovers.
Value range: 0~15
Physical unit: dB

TimeToTrigForVerify
Content: Time delay for triggering handovers to GSM cells with verified BSIC.
During the period of time specified by this parameter, if the signal quality in a
neighboring GSM cell satisfies inter-RAT handover conditions and the neighboring
GSM cell is verified, an inter-RAT handover is triggered.
Physical unit: ms
TimeToTrigForNonVerify
Content: Time delay for triggering handovers to GSM cells with non-verified BSIC.
During the period of time specified by this parameter, if the signal quality in a
neighboring GSM cell satisfies inter-RAT handover conditions and the neighboring
GSM cell is not verified, an inter-RAT handover is triggered. When the value of this

232
parameter is 65535, the RNC does not perform inter-RAT handovers to non-verified
GSM cells.
Value range: 0~64000, 65535
Physical value range: 0~64000, 65535; step: 1
Physical unit: ms
Set this parameter through ADD UCELLINTERRATHOCOV/ MOD


Event-triggered measurement report mode:

After receiving the event 3A measurement report of 2G cells,

the RNC performs the following decision and execution
procedures:
Put all the 2G cells that trigger event 3A into a cell set and arrange
the cells according to the measurement quality in descending
order
Select the cells in sequence from the cell set to perform inter-RAT
handover
233
Page157

3A event:
The estimated quality of the currently used UTRAN

frequency is below a certain threshold and the estimated
quality of the other system is above a certain threshold
Event 3A is triggered on the basis of the following formula:

QOtherRAT + CIOOtherRAT TOtherRAT + H3a/2
QUsed TUsed - H3a/2

Page158
TUsed is the absolute quality threshold of the cell that uses the current frequency.
MOtherRAT is the measurement value of the cell (in another RAT) in the reporting range.
CIOOtherRAT is the cell individual offset value of the cell (in another RAT) in the reporting
range which is equal to the sum of CIO and CIOOffset.
TOtherRAT is the absolute inter-RAT handover threshold. Based on different service types
(CS , PS domain R99 service, or PS domain HSPA service), this threshold can be configured
through the following parameters:

TargetRatCsThd

TargetRatR99PsThd

TargetRatHThd
H3a is 3A hysteresis, the hysteresis value of event 3A.
When the conditions for event 3A are met and maintained in time-to-trigger specified by
TrigTime3A the UE sends the measurement report of event 3A.
234

(Cont.)
UsedFreqCSThdEcN0
Parameter name: Inter-RAT CS Used frequency trigger Ec/No

THD
TargetRatCsThd
Parameter name: Inter-RAT CS handover decision THD
Recommended value: 16, namely -95dBm
Page159
UsedFreqCSThdEcN0

Content: Threshold of used frequency quality for triggering inter-RAT measurement with
measurement quantity of Ec/No for CS domain services. For CS domain services, when Ec/No
is used as the measurement quantity for inter-RAT measurement, this parameter is used to set
measurement control on the event 3A. The event 3A is triggered, when the quality of the
currently used UTRAN frequency is below this threshold and the TargetRatCsThd is reached.

Value range: -24~0


Physical unit: dB
TargetRatCsThd

Content: Quality requirement for the inter-RAT cell during an inter-RAT handover with CS
domain services. For CS domain services, if the value of InterRatReportMode is set to
EVENT_TRIGGER, this parameter is used to set the measurement control of event 3A. One of
the necessary conditions for triggering event 3A can be met only when the quality of the target
frequency is higher than this threshold; if the value of InterRatReportMode is set to
PERIODICAL_REPORTING, this parameter is used to evaluate inter-RAT coverage
handovers at the RNC. Note that the value 0 means the physical value is smaller than -110
dBm.

Value range: 0~63

Physical value range: Lower than -110, -110~-48 (1: -110; 2: -109; ...; 63: -48 )

Physical unit: dBm
Set these parameters through ADD UCELLINTERRATHOCOV/ MOD UCELLINTERRATHOCOV/
SET UINTERRATHOCOV.
235

(Cont.)
Recommended values of 3A event:

Used cell
Target cell
CS Ec/No threshold: -12, namely -12dB

CS threshold: 16, namely -95dBm
PS Ec/No threshold: -13, namely -13dB
H Ec/No threshold: -13, namely -13dB
PS threshold: 16, namely -95dBm
CS RSCP threshold: -97, namely -97dBm

PS RSCP threshold: -107, namely -107dBm
H threshold: 16, namely -95dBm
H RSCP threshold: -107, namely -107dBm
Page160
Set these parameters through ADD UCELLINTERRATHOCOV/MOD

UCELLINTERRATHOCOV/SET UINTERRATHOCOV.
236

(Cont.)
Hystfor3A
Parameter name: 3A hysteresis
TrigTime3A
Parameter name: 3A event trigger delay time
Page161
Hystfor3A

Content: Hysteresis value for the event 3A. The value of this parameter correlates with
resisting signal fluctuation. Thus, the ping-pong effect can be avoided, but the speed of
the handover algorithm to respond to signal change becomes lower. If the inter-RAT
handover hysteresis is set to an excessively high value, the GSM cell to which the UE
is handed over must be of good quality. Therefore, the conditions for triggering the
inter-RAT handover decision are hard to be satisfied, and the call drop rate increases.

Value range: 0~15


Physical unit: dB
TrigTime3A

Content: Time delay to trigger the event 3A. The value of this parameter correlates
with slow fading. The larger the value of this parameter, the lower the incorrect
decision probability, but the slower the response of the event 3A to measurement
signal change.

D640, D1280, D2560, D5000

2560, 5000

Physical unit: s
Set these parameters through ADD UCELLINTERRATHOCOV/ MOD

237
QoS-based Inter-RAT Handover
QoS-based Inter-RAT Handover

If the service quality of the current cell deteriorates, the link stability
control algorithm makes a handover measurement decision.
Besides the triggering step, the rest 3 steps are similar with coverage-based
inter-RAT handover.
In QoS-based 3G to 2G handover, the event 3A measurement quantity is set
through the parameter UsedFreqMeasQuantityForQos3A.
Page163
238

(Cont.)
UlQosAmrInterRATHoSwitch
Parameter name: InterRAT HO For Switch For Uplink AMR
DlQosAmrInterRATHoSwitch
Parameter name: InterRAT HO For Switch For Downlink

AMR
UlQosAmrInterRATHoSwitch
Content: Inter-RAT handover switch of link stability control for UL QoS
of AMR services. When the parameter is set to YES, inter-RAT handover
can be performed for AMR services to ensure the QoS.
DlQosAmrInterRATHoSwitch
Content: Inter-RAT handover switch of link stability control for DL QoS
of AMR services. When the parameter is set to YES, inter-RAT handover
can be performed for AMR services to ensure the QoS.

Page164
239

(Cont.)
Parameter name: First/Second/Third Action For BE Uplink

QOS
Parameter name: First/Second/Third Action For BE Downlink

QOS
algorithm when the UL QoS of BE service deteriorates. If QoS action is
algorithm when the DL QoS of BE service deteriorates. If QoS action is

Page165
240

(Cont.)
DLQosMcTimerLen/ULQosMcTimerLen
Parameter name: Down/UP Link Qos Measure timer length
UsedFreqMeasQuantityForQos3A
Parameter name: 3A Used-Freq Measure Quantity for Qos
Recommended value: CPICH_RSCP
Page166
DLQosMcTimerLen/ULQosMcTimerLen
Content: Timer length for downlink/uplink QOS measurement. This parameter

controls the time lengths for the inter-frequency and inter-RAT measurement based on
QOS. After inter-frequency or inter-RAT measurement starts, if no inter-frequency
handover is performed when this timer expires, the measurement is stopped, and the
compressed mode is deactivated, if any. If this parameter is set to 0, this indicates that
the timer will not be started.

Value range:0~512


Physical unit: s
UsedFreqMeasQuantityForQos3A

Content: This parameter configures the used frequency measurement quantity to
trigger the inter-RAT measurement for the purpose of Qos-based handover. The
parameter is valid when the event reporting mode is selected for inter-RAT.
CPICH_Ec/NO: the measurement quantity used for event 2D and 2F, with unit of dB
CPICH_RSCP: the measurement quantity used for event 2D and 2F, with unit of dBm .

Value range: CPICH_EC/NO, CPICH_RSCP

Physical value range: CPICH_EC/NO, CPICH_RSCP
Set these parameters through ADD UCELLQOSHO/ MOD UCELLQOSHO/ SET UQOSHO.
241
Load-based Inter-RAT Handover
Load-based Inter-RAT Handover

When the load of the 3G cell that the UE accesses is higher than the
related threshold, the Load Reshuffling (LDR) algorithm makes a
handover decision.
The RNC enables the compressed mode and starts the inter-RAT
handover measurement.
After the UE reports event 3C, the RNC makes a handover decision.
The RNC initiates a handover procedure.
Page168
242

(Cont.)
InterRATMeasTime
Parameter name: Inter-RAT measure timer length
Page169
InterRATMeasTime
Content: Timer length for inter-RAT measurement. After inter-RAT
measurement starts, if no inter-RAT handover is performed when this
timer times out, the inter-RAT measurement is stopped. In addition, the
compressed mode is deactivated, if any; If the value is 0, you can infer
that the inter-RAT measurement timer is not started.
Value range: 0~512
Physical unit: s
Set this parameter through ADD UCELLINTERRATHONCOV/ MOD
UCELLINTERRATHONCOV/ SET UINTERRATHONCOV.

243
Load-based Inter-RAT Handover Decision Phase

3C event:
The estimated quality of other system is above a certain

threshold

MOtherRAT + CIOOtherRAT TOtherRAT + H3c/2
Event 3C is used for load-based/service-based/speed-based inter-frequency

handover.
MOtherRAT is the measurement value of the cell (in another RAT) in the
reporting range, namely GSM RSSI.
CIOOtherRAT is the cell individual offset value of the cell (in another RAT) in
the reporting range, which is equal to the sum of CIO and CIOOffset.
TOtherRAT is the absolute inter-RAT handover threshold. Based on different
service types (CS , PS domain service), this threshold can be configured through
InterRATNCovHOCSThd
InterRATNCovHOPSThd
H3c is 3C hysteresis, the hysteresis value of event 3C.
When the conditions for event 3C are met and the delay requirement specified
by the TrigTime3C parameter can be satisfied, the UE sends the measurement
report of event 3C.

Page170
244

(Cont.)
InterRATNCovHOCSThd
Parameter name: Inter-RAT CS handover decision THD
InterRATNCovHOPSThd
Parameter name: Inter-RAT PS handover decision THD
Page171
InterRATNCovHOCSThd

Content: Quality requirement for the inter-RAT cell during an inter-RAT handover
with CS domain services. This parameter is used to set measurement control on the
above this threshold. Note that the value 0 indicates that the physical value is smaller
than -110 dBm.

Value range: 0~63


Physical unit: dB
InterRATNCovHOPSThd

Content: Quality requirement for the inter-RAT cell during an inter-RAT handover
with PS domain services. This parameter is used to set measurement control on the
above this threshold. Note that the value 0 indicates that the physical value is smaller
than -110 dBm.

Value range: 0~63


Physical unit: dB
Set these parameters through ADD UCELLINTERRATHONCOV/ MOD
245

(Cont.)
Hystfor3C
TrigTime3C
Page172
Hystfor3C

Content: Hysteresis value for the event 3C. The value of this parameter correlates with
resisting signal fluctuation. Thus, the ping-pong effect can be avoided, but the speed of
the handover algorithm to respond to signal change becomes lower. If the inter-RAT
handover hysteresis is set to an excessively high value, the GSM cell to which the UE
hands over must be of good quality. Therefore, the conditions for triggering the interRAT handover decision are hard to be satisfied, and the call drop rate increases. .

Value range: 0~15


Physical unit: dB
TrigTime3C

Content: Time delay to trigger the event 3C. The value of this parameter correlates
with slow fading. The larger the value of this parameter, the lower the incorrect
decision probability, but the slower the response of the event 3C to measurement
signal change.

Value range D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,
D640, D1280, D2560, D5000

2560, 5000

Physical unit: ms
246
Set these parameters through ADD UCELLINTERRATHONCOV/ MOD

Load-based Inter-RAT Handover Execution Phase

After receiving the event 3C measurement report of 2G

cells, the RNC performs the following handover decision
and execution procedure:
Put all the 2G cells that trigger event 3C into a cell set and
arrange the cells according to the measurement quality in
descending order
Select the cells in sequence from the cell set
Page173
To avoid the impact of the UE (in long-term measurement of compressed mode)

on the radio network, the parameter InterRATHOAttempts is set to restrict the
maximum attempts of the 3G to 2G load-based or service-based handover. The
parameter indicates the handover attempts made to the same cell or different
cells. If the number of attempts exceeds the parameter value, the RNC does not
initiate the handover.
247
The load status between the source cell and the target cell can be acquired by
interchanging load information between a 3G cell and a 2G cell during the loadbased and service-based 3G-to-2G handover. Thus, whether to further conduct
the handover can be determined to avoid the 2G cell overload and possible
handover to the congested cell.
The procedure for load information interchanging between the 3G source cell
and 2G target cell is described as follows:
1. When the RNC sends a RELOCATION REQUIRED message to the 3G
CN, If the switch SndLdInfo2GsmInd is set to on, the RELOCATION
REQUIRED message includes the Old BSS To New BSS Information IE
that includes the load information of the 3G source cell.
If the switch SndLdInfo2GsmInd is set to off, then the RELOCATION
REQUIRED message does not include the Old BSS To New BSS
Information IE.
2. When the RNC receives the RELOCATION COMMAND message
from the 2G CN, If the switch NcovHoOn2GldInd is set to on, the RNC
obtains the load information of the 2G target cell by reading the InterSystem Information Transparent Container IE, which is included in the
RELOCATION COMMAND message.
If the 2G load is lower than CSHOOut2GloadThd (for CS service),
or if the 2G load is lower than PSHOOut2GloadThd (for PS
service), the RNC continues the inter-RAT handover procedure;
otherwise, the RNC returns the Relocation Cancel message to the
CN to cancel this inter-RAT handover and makes another handover
attempt to the next candidate cell generated in the cell list based on
inter-RAT measurement.
If the Inter-System Information Transparent Container IE, is not
included in the RELOCATION COMMAND message, the load
information of the 2G target cell is not considered and this interRAT handover is continued.
If the switch NcovHoOn2GldInd is set to off, the RNC continues the interRAT handover procedure without considering the thresholds.
248

(Cont.)
SndLdInfo2GsmInd
Parameter name: Send Load Info to GSM Ind
NcovHoOn2GldInd
Parameter name: NCOV Reloc Ind based on GSM cell load
Page175
SndLdInfo2GsmInd

Content: When it is set to on, the RNC sends UMTS cell load information to the GSM during
the non-coverage based system relocation in or out process. When it is set to off, the RNC
does not send UMTS cell load information to the GSM during the system relocation in or out
process. This parameter is designed for the UMTS network to cooperate with the GSM
network. When the UE is handed over from the UMTS network to the GSM network, the RNC
normalizes the load information of the best cell and sends it to the GSM network. Then, the
GSM network determines whether to accept or reject the handover request. This switch is only
effective in CS domain, the RNC does not send UMTS cell load information to the GSM in PS
domain.


NcovHoOn2GldInd

Content: When this parameter is set to on, and when the load of the GSM cell exceeds the
related threshold, the RNC will stop the non-coverage based inter-RAT handover; when this
parameter is set to off, the RNC will do reversely. This parameter determines whether to stop
the non-coverage based handover from the UMTS network to the GSM network according to
the load information of the GSM cell. When the GSM network can provide its load
information to the UMTS network, the RNC determines whether to send the non-coverage
based handover to the GSM cell according to the load information of the GSM cell and the
load threshold of the GSM cell set in the UMTS cell. This parameter is invalid for the GSM
network that cannot provide its load information to the UMTS network.

249

Set these parameter through SET UINTERRATHONCOV.

(Cont.)
CSHOOut2GloadThd
Parameter name: CS domain Reloc GSM load THD
Recommended value: 80, namely 80%
PSHOOut2GloadThd
Parameter name: PS domain Reloc GSM load THD
Page176
CSHOOut2GloadThd

Content: CS domain Relocation GSM load THD. This parameter specifies the CS
domain relocation GSM load threshold. When the GSM load policy is used, that is,
when NcovHoOn2GldInd is set to on, the CS domain inter-system relocation out
process will be stopped if the GSM system send its cell load to the RNC and the cell
load exceeds the CS domain Reloc GSM load THD. Otherwise, the RNC does not stop
the CS domain inter-system relocation out process.

Value range: 0~100

Physical value range: 0~100%; step: 1

Physical unit: %
PSHOOut2GloadThd

Content: PS domain Relocation GSM load THD. This parameter specifies the PS
domain relocation GSM load threshold. When the GSM load policy is used, that is,
when NcovHoOn2GldInd is set to on, the PS domain inter-system relocation out
process will be stopped if the GSM system send its cell load to the RNC and the cell
load exceeds the PS domain Reloc GSM load THD. Otherwise, the RNC does not stop
the PS domain inter-system relocation out process.

Value range: 0~100

Physical value range: 0~100%; step: 1
250
Physical unit: %
Set these parameter through SET UINTERRATHONCOV.

(Cont.)
InterRATHOAttempts
Parameter name: Inter-RAT handover max attempt times
Page177
InterRATHOAttempts
Content: The maximum number of attempts to perform non-coveragebased inter-RAT handovers. This parameter specifies the maximum
number of attempts for the RNC to perform inter-RAT handovers after a
non-coverage-based inter-RAT handover failure. The handover attempts
should involve the target cells that have not been tried but satisfy the
handover conditions.
Value range: 1~16
Set this parameter through ADD UCELLINTERRATHONCOV/ MOD

251
Service-based Inter-RAT Handover
Service-based Inter-RAT Handover

When a service is established, the RNC requests the handover to the GSM
based on the service type and service handover indicator assigned by the
CN.
The rest 3 phases are similar with the load-based inter-RAT handover.
Page179
252

(Cont.)
CSServiceHOSwitch
Parameter name: Inter-RAT CS handover switch
Recommended value: OFF
PSServiceHOSwitch
Parameter name: Inter-RAT PS handover switch
Page180
CSServiceHOSwitch/PSServiceHOSwitch
Content: Indicating whether the cell allows CS/PS service inter-RAT
handover. Service handover refers to the handover attribute and related
parameter configuration on the network side for each service. When a
service is established, the related measurements and inter-RAT handover
are immediately triggered. These two switches are enabled only for
service handover; generally, they are disabled by default. Note that the
service handover is enabled only when the handover attribute is set to
HO_TO_GSM_SHOULD_BE_PERFORM and CS/PS service inter-RAT
handover is set to ON. Both conditions are mandatory. For hybrid services,
the service handover is not triggered.
Set these parameters through ADD UCELLHOCOMM/ MOD
UCELLHOCOMM.

253
UMTS to GSM Multimedia Fallback

VP service:
Speech
Video
Speech
GSM
WCDMA
VP
AMR service:
AMR
AMR
Page182
Compared with the traditional speech service of the GSM, the VP service of the
UMTS can transmit not only speech services between the calling party and the
called party, but also the images and videos captured by both parties. Since the
actual implementation is limited by terminals and networks, the VP service
sometimes carries only speech and may fail to transmit images or videos. In this
scenario, the Service Change and Unrestricted Digital Information Fallback
(SCUDIF) provides the fallback mechanism that changes a video call to a
common speech call.
Fallback is initiated when both of the following occasions are met:
The RNC decides to send an inter-RAT handover request after receiving
periodical measurement reports of event 1F, 3A, or 3C.
254
The service is combined with a VP, and the "Alternative RAB

Parameters" in the RAB ASSIGNMENT message is a valid AMR speech
format.

(Cont.)
Procedure of multimedia fallback:
Procedure of service change:

The CN sends the SRNC a RANAP RAB ASSIGNMENT REQUEST
message to set up the VP service.
During 3G to 2G handover, the SRNC sends a RANAP RAB MODIFY
REQUEST message to change the VP service to the AMR speech service.
In the 3GPP R6 protocol, the information element (IE) Alternative RAB
Configuration Request is also added to the RAB MODIFY REQUEST
message, which enables the RNC to request the CN to change the VP
service to the AMR speech service.
The MSC initiates the Bearer Capability (BC) negotiation with the UE.
After the negotiation, the RNC is requested to perform service change.
When the multimedia fallback ends, the RNC decides whether to perform the 3G
to 2G handover according to the current measurements reported by the UE.
The CN initiates the RAB reconfiguration to request both parties to perform the
multimedia fallback. The single VP service falls back to the single AMR speech

Page183
255
service. The multi-RAB service combined with VP falls back to the multi-RAB
service combined with AMR. If the multimedia fallback succeeds, that is, the
video phone in the service falls back to speech successfully, the inter-RAT
handover is initiated. Otherwise, the inter-RAT handover fails.
NACC and PS Handover
NACC
NACC: Network Assisted Cell Change
Cell reselect
to 2G
Reduce inter-RAT
handover delay
3G coverage
2G coverage
Page185
The Network Assisted Cell Change (NACC) function can efficiently reduce the
delay of UMTS-to-GSM handover.
Some services have requirements for the delay. If the handover takes too long,
TCP may start slowly or data transmission of the service stream may be
interrupted due to the overflow of the UE buffer. The introduction of NACC
enables the system information exchange between different BSSs, or between
BSS and RAN. Thus the inter-system delay, especially inter-system delay in PS
domains, can be reduced. With NACC, the RNC sends the UE a cell change
256
order, which contains the GSM EDGE Radio Access Network (GERAN) system information,
when the 3G-to-2G handover in the PS domain is triggered.
RAN Information Management (RIM)

UE
SRNC
RRC
MEASUREMENT
WITH GERAN BEST CELL
SGSN
BSC
REPORT
DIRECT INFORMATION TRANSFER
(RAN IFORMATION REQUEST)
RAN
INFORMATION
REQUEST
RAN INFORMATION
DIRECT
INFORMATION
TRANSFER
(RAN
INFORMATION REPORT)
CELL CHANGE
UTRAN ( (P)SI )
ORDER
FROM
Page186
RNC acquires GERAN (P)SI information by RIM procedure:

After the SRNC receives a measurement report from the UE, the UE is reselected to
the GERAN cell according to the decision.

The SRNC sends a RAN INFORMATION REQUEST message to the SGSN.

The SGSN forwards the message to the corresponding BSS.

The BSS sends a GERAN SI/PSI message to the SRNC via the SGSN. RAN
INFORMATION message can either be On-demand (single report) or Onmodification (multiple reports).

The SGSN forwards the report message to the SRNC through Iu interface.

RNC sends cell change order message with GERAN (P)SI information to UE.
257

(Cont.)
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH
Parameter name: PS 3G to 2G Cell change order NACC

Switch
SuppRIMFlag
Parameter name: Inter-RAT cell support RIM indicator
Page187
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH

Content: When the switch is ON, the NACC function is supported during the PS interRAT handover from the 3G network to the 2G network in the cell change order
process. When the switch is OFF, the NACC function is not supported. When
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH is ON, this switch is useless.
When the NACC function is supported, the UE skips the reading procedure as the
SI/PSI of the target cell is provided after the UE accesses the 2G cell. Thus, the delay
of inter-cell handover is reduced.


Physical value range: OFF, ON

SuppRIMFlag

Content: Identifying whether the inter-RAT cell supports RIM. (RIM is used to obtain
the SI/PSI information of the inter-RAT cell.) For the details of RIM process, refer to
the 3GPP TS 25.901 protocol.



Set this parameter through ADD UEXT2GCELL/ MOD UEXT2GCELL .
258
PS Handover
PS handover introduced in 3GPP R6 and like the CS interRAT handover

Reduce inter-RAT
handover delay
PS HO
to 2G
3G coverage
PS HO
to 3G
2G coverage
Page188
PS Handover (Cont.)
UE
s-RNC
CN
25.413 RELOCATION REQUIRED
<48.018 Source BSS to Target BSS

Transparent Container: 25.331 INTER
RAT HANDOVER INFO>
t-BSS
48.018 PS-HANDOVER-REQUEST
< 48.018 Source BSS to target BSS
transparent Container: 25.331 INTER
RAT HANDOVER INFO>
48.018 PS-HANDOVER-REQUEST-ACK
25.331 HANDOVER FROMUTRAN
COMMAND
< 25.331 GERANA/Gb mode message
list/ Single GERANA/Gb mode
message : 44.060 PS Handover
Command >
25.413 RELOCATION COMMAND

<48.018 Target BSS to Source BSS
Transparent Container: 44.060 PS
Handover Command >
259
<48.018 Target BSS to Source BSS

Transparent Container: 44.060 PS
Handover Command>
Page189
PS handover is different from NACC or normal cell change function, with which the
relocation procedure between 3G and 2G is applied, just like the CS inter-system handover.
The difference between PS handover and CS handover is that some new IE are added in the
corresponding messages to support PS handover. For example, GERAN System
Information is added in the Handover From UTRAN Command to support UE accessing to
GERAN cell.

(Cont.)
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH
Parameter name: PS 3G to 2G HO Switch
SuppPSHOFlag
Parameter name: Inter-RAT cell support PS HO indicator
Page190
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH

Content: When the switch is on, the PS inter-RAT handover from the 3G network to
the 2G network is performed in the relocation process. When the switch is not on, the
PS inter-RAT handover from the 3G network to the 2G network is performed in the
cell change order process.


Physical value range: OFF, ON

SuppPSHOFlag

Content: Identifying whether the inter-RAT cell supports PS HO. TRUE indicates that
the inter-RAT cell is able to perform the handover procedure with relocation. FALSE
indicates that the cell is unable to do so.



Set this parameter through ADD UEXT2GCELL/ MOD UEXT2GCELL .
260
UMTS to GSM Handover Retry
UMTS to GSM Handover Retry

In case of inter-RAT handover failure, if the cause of the failure

is not a configuration failure and the retry timer expires, the
UE makes handover attempts to the cell again until the retry
number exceeds the maximum retry number
The inter-RAT handover retry algorithm works in the following

two signaling procedures:
Signaling procedure for Iu relocation
Signaling procedure for service-based handover on the Uu

interface
The retry timer and maximum retry number for coverage-based and QoS-based
inter-RAT handover are:
PeriodFor3A
AmntOfRpt3A
The retry timer and maximum retry number for load-based and service-based
inter-RAT handover are:
PeriodFor3C
AmntOfRpt3C

Page192

261
Signaling procedure for Iu relocation:

The RELOCATION REQUIRED message is initiated on the Iu interface.
If the RNC receives the RELOCATION PREPARATION FAILURE message,
the inter-RAT handover fails.
If the cause of the failure is one of the following configuration failure, the
RNC does not make a handover retry to the cell.
Relocation Failure in Target CN/RNC or Target System, or
Relocation not supported in Target RNC or Target System, or
Relocation Target not allowed
Otherwise, the related retry timer for the cell is started. After the retry
timer expires, the UE makes handover attempts to the cell again until the
retry number exceeds the maximum retry number.
If the RNC receives the RELOCATION COMMAND message, the handover on
the Uu interface continues.
If the handover succeeds or the new event 3A or 3C report is received, the
periodical retry is stopped.
Signaling procedure for Service-based handover on the Uu interface:
For CS services or CS and PS combined services, the HANDOVER FROM
UTRAN signaling procedure on the Uu interface is performed only when the
handover based on CS services is made.
For a PS service or combined PS services, the CELL CHANGE ORDER FROM
UTRAN or HANDOVER FROM UTRAN signaling procedure on the Uu
interface is performed.
If the HANDOVER FROM UTRAN FAILURE or CELL CHANGE ORDER
FROM UTRAN FAILURE message is received, the handover on the Uu
interface fails.
If the "Inter-RAT handover failure cause" in HANDOVER FROM UTRAN
FAILURE message is "Configuration unacceptable", or if the "Inter-RAT
change failure cause" in CELL CHANGE ORDER FROM UTRAN FAILURE
message is "Configuration unacceptable", the RNC does not make a handover
retry to the cell.
Otherwise, the related retry timer for the cell is started. After the retry timer
expires, the UE makes a handover attempt to the cell again until the retry
number exceeds the maximum number.
If the handover succeeds or the new event 3A or 3C report is received, the
periodical retry is stopped.
262

(Cont.)
PeriodFor3A
Parameter name: 3A event retry period
AmntOfRpt3A
Parameter name: 3A event retry max times
Page194
PeriodFor3A

Content: Retry period for the event 3A. This parameter defines the length of the event
3A retry period. The smaller the value of this parameter, the more frequent the
handover retry due to inter-RAT handover failure, and the faster the UE to be
successfully handed over to the target cell whose load is restored, thus lowering the
probability of call drops. In this case, however, frequent handover retry brings more
load to the RNC system.

Value range: 1~64


Physical unit: ms
AmntOfRpt3A

Content: Maximum retry times of the event 3A. This parameter defines the number of
times for event 3A retry when the measurement control is valid. The larger the value
of this parameter, the larger the number of times for inter-RAT handover retry, and the
higher probability the UE is successfully handed over to the target cell whose load is
restored. When the retry times reaches the maximum value, the RNC stops the retry
process. Or if the measurement control message is released, the retry will be
immediately stopped.

Value range: 0~63

Set these parameters through ADD UCELLINTERRATHOCOV / MOD
UCELLINTERRATHOCOV / SET UINTERRATHOCOV.
263

(Cont.)
PeriodFor3C
Parameter name: 3C event retry period
AmntOfRpt3C
Parameter name: 3C event retry max times
Page195
PeriodFor3C

Content: Retry period for the event 3C. This parameter defines the length of the event 3C retry
period. The smaller the value of this parameter, the more frequent the handover retry due to
inter-RAT handover failure, and the faster the UE to be successfully handed over to the target
cell whose load is restored, thus lowering the probability of call drops. In this case, however,
frequent handover retry brings more load to the RNC system.

Value range: 1~64


Physical unit: ms
AmntOfRpt3C

Content: Maximum retry times of the event 3C. This parameter defines the number of times
for event 3C retry when the measurement control is valid. The larger the value of this
parameter, the larger the number of times for inter-RAT handover retry, and the higher
probability the UE is successfully handed over to the target cell whose load is restored. When
the retry times reaches the maximum value, the RNC stops the retry process. Or if the
measurement control message is released, the retry will be immediately stopped.

Value range: 0~63

Set these parameters through ADD UCELLINTERRATHOCOV / MOD UCELLINTERRATHOCOV
/ SET UINTERRATHOCOV.
264
Signaling Procedures for Inter-RAT Handover
Signaling Procedures for CS Inter-RAT

Handover
Page197
The above figure shows the signaling procedures for the 3G-to-2G handover in
the CS domain. The 2G messages shown in the figure are for your reference
only.
265
Signaling procedures for CS inter-RAT handover:

1. The SRNC sends the 3G MSC a RANAP message RELOCATION
REQUIRED if the condition of Inter-RAT outgoing handover is met.
2. As indicated in the received message, the 3G MSC forwards this request to
the 2G MSC on the MAP/E interface through a MAP message PREPARE
HANDOVER.
3. The 2G MSC forwards the request to the BSC. The message shown in the
figure is for reference only and is subject to the actual condition of the GSM.
4. The BSC responds to this request. The message shown in the figure is for
reference only and is subject to the actual condition of the GSM.
5. Once the initial procedures are completed in the 2G MSC/BSS, the 2G MSC
returns a MAP/E message PREPARE HANDOVER RESPONSE.
6. The 3G MSC sends the SRNC a RANAP message RELOCATION
COMMAND.
7. The SRNC sends the UE an RRC message HANDOVER FROM UTRAN
through the existing RRC connection. This message may include information
from one or several other systems.
8. The BSC performs handover detection. The figure does not show such
procedures as GSM BSS synchronization. The message shown in the figure is
for reference only and is subject to the actual condition of the GSM.
9. The UE sends the BSC a HANDOVER COMPLETE message.
10. The BSC sends the MSC a HANDOVER COMPLETE message. The
message shown in the figure is for reference only and is subject to the actual
condition of the GSM.
11. After detecting the UE in the coverage area of the GSM, the MSC sends the
CN a MAP/E message SEND END SIGNAL REQUEST.
12. The CN sends the former SRNC an IU RELEASE COMMAND message,
requesting the former SRNC to release the allocated resource.
13. After the bearer resource is released in the UMTS, the former SRNC sends
the CN an IU RELEASE COMPLETE message.
14. After the call ends, the CN sends the MSC a MAP/E message SEND END
SIGNAL RESPONSE.
266
Signaling Procedures for PS Inter-RAT

Handover
Page199
For a UE in idle mode or connected mode, if the SGSN changes with the shift of the system
that the UE accesses from 3G network to 2G network, the inter-SGSN handover will be
performed.
The handover procedures are different in the following two cases:

When the UE is in CELL_DCH state:

The 3G to 2G handover in the PS domain is triggered after the UTRAN sends a CELL
CHANGE ORDER FROM UTRAN message.

When the UE is in CELL_FACH, CELL_PCH, or URA_PCH state:

The 3G to 2G handover in the PS domain is triggered through the cell reselection.
The above figure shows an example of handover for the UE in CELL_FACH, CELL_PCH, or
URA_PCH state. When the UE is in idle mode, the cell reselection procedure does not include
the elementary procedures marked "UE CONNECTED" in figure.
267
Signaling procedures for PS inter-RAT handover:

1. The UE in CELL_DCH state or the UTRAN (when the UE is in CELL_FACH state)
decides to initiate an Inter-RAT handover in the PS domain to hand over the UE to a new
GSM cell and stop the data transmission between the UE and the network.

2. The UE sends a ROUTING AREA UPDATE REQUEST message to the 2G SGSN. The
Update Type in the message indicates RA update, combined RA/LA update, or combined
RA/LA update with IMSI attach. The BSS adds the CGI including the RAC and LAC of the
cell to the received message before forwarding the message to a new 2G SGSN.

3. The new 2G SGSN sends an SGSN CONTEXT REQUEST message to the old 3G SGSN
to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI Signature.
If the old P-TMSI Signature is valid, the old 3G SGSN starts a timer. Otherwise, the old 3G
SGSN responds with an error cause.

4. If the UE stays in connected mode before handover, the old 3G SGSN sends an SRNS
CONTEXT REQUEST message. After receiving this message, the SRNS buffers the DPUs,
stops sending the PDUs to the UE, and sends an SRNS CONTEXT RESPONSE message to
the old 3G SGSN.

5. The old 3G SGSN sends an SGSN CONTEXT RESPONSE message to the 2G SGSN,
including the MM and PDP contexts.

6. The security functions can be executed.

7. The new 2G SGSN sends an SGSN CONTEXT ACKNOWLEDGE message to the old 3G
SGSN. This informs the old 3G SGSN that the new 2G SGSN is ready to receive the PDUs
belonging to the activated PDP contexts.

8. The old 3G SGSN sends a DATA FORWARD COMMAND message to the SRNS. The
SRNS starts a data-forwarding timer and sends the buffered PDUs to the old 3G SGSN.

9. The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDUs, the sequence
numbers in the GTP header remain unchanged.

10. The new 2G SGSN sends an UPDATE PDP CONTEXT REQUEST message to each
related GGSN. Each GGSN sends an UPDATE PDP CONTEXT RESPONSE message after
updating its PDP context fields.

11. The new 2G SGSN sends an UPDATE GPRS LOCATION message, requesting the HLR
to modify the SGSN number.

12. The HLR sends a CANCEL LOCATION message to the old 3G SGSN. The old 3G
SGSN responds with a CANCEL LOCATION ACK message. After the timer expires, the old
3G SGSN removes the MM and PDP contexts.

13. The old 3G SGSN sends an IU RELEASE COMMAND message to the SRNS. After the
data-forwarding timer expires, the SRNS responds with an IU RELEASE COMPLETE
message.

14. The HLR sends an INSERT SUBSCRIBER DATA message to the new 2G SGSN. The
2G SGSN constructs an MM context and PDP contexts for the UE and returns an INSERT
SUBSCRIBER DATA ACK message to the HLR.

15. The HLR sends an UPDATE GPRS LOCATION ACK message to the new 2G SGSN.
268
16. If the association has to be established, the new 2G SGSN sends a LOCATION UPDATE
REQUEST message to the VLR. The VLR stores the SGSN number for creating or updating the
association.
17. If the subscriber data in the VLR is marked as not confirmed by the HLR, the new VLR
informs the HLR. The HLR cancels the old VLR and inserts subscriber data in the new VLR.

1. The new VLR sends an UPDATE LOCATION message to the HLR.

2. The HLR cancels the data in the old VLR by sending a CANCEL LOCATION
message to the old VLR.

3. The old VLR acknowledges the message by responding with a CANCEL
LOCATION ACK message.

4. The HLR sends an INSERT SUBSCRIBER DATA message to the new VLR.

5. The new VLR acknowledges the message by responding with an INSERT
SUBSCRIBER DATA ACK message.

6. The HLR responds with a UPDATE LOCATION ACK message to the new VLR.
17. The new VLR allocates a new TMSI and responds with a LOCATION UPDATE
ACCEPT message to the 2G SGSN.
18. The new 2G SGSN checks the presence of the MS in the new RA. If all checks are
successful, the new 2G SGSN constructs the MM and PDP contexts for the MS. A logical
link is established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE
with a ROUTING AREA UPDATE ACCEPT message.
19. The UE acknowledges the new P-TMSI by returning a ROUTING AREA UPDATE
COMPLETE message, including all PDUs successfully sent to the UE before the routing area
update procedure.
20. The new 2G SGSN sends a TMSI REALLOCATION COMPLETE message to the new
VLR if the UE confirms the VLR TMSI.
21. The 2G SGSN and the BSS perform the BSS PACKET FLOW CONTEXT procedure.
269
WCDMA LOAD CONTROL ALGORITHM AND PARAMETERS
Foreword
The WCDMA system is a self-interfering system, so the

capacity, coverage, and QoS are mutually affected
The target of load control is to maximize the system

capacity while ensuring coverage and QoS, and provide
differentiated services for users
Page1
The WCDMA system is a self-interfering system. As the load of the system increases, the
interference rises. A relatively high interference can affect the coverage and QoS of
established services. Therefore, the capacity, coverage, and QoS of the WCDMA system
are mutually affected.
Through the control of key resources, such as power, downlink channelization codes,
channel elements (CEs), Iub transmission resources, which directly affect user experience,
load control aims to maximize the system capacity while ensuring coverage and QoS.
In addition, load control provides differentiated services for users with different
priorities. For example, when the system resources are insufficient, procedures such as
direct admission, preemption, redirection can be performed to ensure the successful
access of emergency calls to the network.
Load control is implemented in the RNC through measurement reports from the NodeBs.
270
References
3GPP TS 25.133: Requirements for Support of Radio Resource

Management (FDD)
3GPP TS 25.215: Physical Layer - Measurements (FDD)
3GPP TS 25.304: UE Procedures in Idle Mode and Procedures

for Cell Reselection in Connected Mode
3GPP TS 25.321: Medium Access Control (MAC) Protocol

Specification
3GPP TS 25.331: Radio Resource Control (RRC)
3GPP TS 25.413: UTRAN Iu Interface RANAP Signaling
Page2
Objectives

Outline the principle of load control
Describe the realization method of load control
Perform the parameter adjustment of load control
271
Page3
Load Control Overview
Load Definition
Load: the occupancy of capacity
Two kinds of capacity in WCDMA system:

Hard capacity:
Cell DL OVSF code
Iub transport resource
NodeB processing capability (NodeB credit)
Soft capacity:
Cell power (UL and DL)
Page6
WCDMA network load can be defined by four factors:

Power, includes DL transmitting power of cell and increased UL interference
(RTWP)

DL OVSF code of a cell.

DL and UL NodeB processing capability which is defined by NodeB credit.

Iub transmission bandwidth of a NodeB.
The power resource is related to the mobility, distribution of the UE and also effected by
the radio conditions. Therefore, for a fixed power resource, the numbers of service can
be supported is not a fix result. We believe the UL and DL power resources are soft.
272
Load Control Algorithms

The load control algorithms are applied to the different

UE access phases as follows:
PUC: Potential User Control
CAC: Call Admission Control
IAC: Intelligent Access Control LDB : Intra-frequency Load Balancing

LDR: Load Reshuffling
OLC: Overload Control
Page7
In addition, functional load control algorithms vary depending on the load levels of the
cell, as shown in the following figure:
273
Load Control Algorithms (Cont.)

Resources considered by different load control algorithms:
Load Control Algorithm
Resources
Power
Code
NodeB Credits
Iub Bandwidth
PUC
IAC
CAC
LDB
LDR
OLC
: not considered; : considered
274
Page8
Load Measurement
Load Measurement
Load control function in the WCDMA system:
Page10
The load control functions, such as OLC and CAC, use load measurement values in the
uplink and the downlink. A common Load Measurement (LDM) function is used to
control load measurement in the uplink and the downlink separately.
Load measurement is implemented by the NodeB. The filtering of measurement
quantities is implemented by the NodeB and the RNC.
275
Load Measurement Quantities

The major load-related measurement quantities are as follows:

Uplink Received Total Wideband Power (RTWP)
Downlink Transmitted Carrier Power (TCP)
Non-HSPA power: TCP excluding the power used for transmission

on HSPA channels
Provided Bit Rate (PBR) on HS-DSCH
PBR on E-DCH
Power Requirement for GBR (GBP) on HS-DSCH: minimum power

required to ensure the GBR on HS-DSCH
Received Scheduled E-DCH Power Share (RSEPS): power of the EDCH scheduling service
Page11
Load Measurement Procedure
276
Page12
The NodeB measures the major quantities related to load control. After layer 3 filtering,
the measurement values are reported to the RNC.
The RNC performs smooth filtering on the measurement values reported from the NodeB
and then obtains the measurement values, which further serve as data input for the load
control algorithms.
Load Measurement Procedure (Cont.)

Layer 3 filtering on the NodeB side:
A is the sampling value of the measurement
B is the measurement value after layer 1 filtering
C is the measurement value after layer 3 filtering
C' is another measurement value (if any) for measurement evaluation
D is the reported measurement value after measurement evaluation on

the conditions of periodic measurement and event-triggered
measurement
Page13
Layer 1 filtering is not standardized by protocols and it depends on vendor equipment.

Layer 3 filtering is standardized. The filtering effect is controlled by a higher layer. The
alpha filtering that applies to layer 3 filtering is calculated according to the following
formula:
Here:

Fn is the new post-filtering measurement value.

Fn-1 is the last post-filtering measurement value.
Mn is the new measurement value from the physical layer.
= (1/2)k/2, where k is specified by the UlBasicCommMeasFilterCoeff or
DlBasicCommMeasFilterCoeff parameter.
Set the above parameters through SET ULDM.
277
PBR measurement does not use alpha filtering on the NodeB side.
The NodeB periodically reports each measurement quantity to the RNC. The following
table lists the reporting period parameters for setting different measurement quantities.
The Provided Bit Rate (PBR) measurement quantity is also reported by the NodeB to the
RNC. Different from other power measurement quantities, PBR does not undergo alpha
filtering on the NodeB side.
278
Load Measurement Procedure (Cont.)

Smooth filtering on the RNC side:

After the RNC receives the measurement report, it filters the

measurement value with the smooth window
Assuming that the reported measurement value is Qn and

that the size of the smooth window is N, the filtered
measurement value is:
Page15
LDM must apply different smooth filter coefficients and measurement periods to PUC,
CAC, LDR, and OLC so as to obtain appropriate filtered values.
The following table lists the smooth window length parameters for setting different
functions:
GBP measurements have the same smooth window length in all related functions. The
filter length for GBP measurement is specified by the HsdpaNeedPwrFilterLen parameter.
On the RNC side, the length of the PBR smooth filter window is specified by the
HsdpaPrvidBitRateFilterLen/HsupaPrvidBitRateFilterLen parameter.
279
Priorities Involved in Load Control
Priority
The QoS of the services or users with low priority will be

affected by the load control algorithms first
Three kinds of priorities involved in load control:

User priority
RAB integrated priority
User integrated priority
Page17
User priority: mainly applying to provide different QoS for different users. Eg., setting
different GBR according to the user priority for BE service. No consideration about the
service.
RAB integrated priority: priority of a service, related to the service type, and the user
priority of the user.
User integrated priority: only used for multi-RAB user, it is a temporary priority of an
ongoing-service user.
280
User Priority
There are three levels of user priority:

gold (high priority), silver (middle priority) and copper (low

priority) users
User priority
Gold
Silver
Copper
Uplink
384kbps
128kbps
64kbps
Downlink
384kbps
128kbps
64kbps
gold
user
Page18
In CN HLR, operator can set ARP (Allocation Retention Priority ). During service setup, CN
sends ARP to RNC. Based on the mapping relation (configured in RNC), RNC can identify
the users priority, namely gold, silver or copper one.
The levels of user priority are mainly used to provide different QoS for different users,
for example, setting different Guaranteed Bit Rate (GBR) values for BE services according
to different priority levels.
The GBR of BE services are configurable. According to the traffic class, priority level, and
carrier type (DCH or HSPA), the different values of GBR are configured through the SET
UUSERGBR command.
281
User Priority (Cont.)

The mapping relation between user priority and ARP is

configured in RNC by SET UUSERPRIORITY
Typical relation between user priority and ARP:
ARP
User
Priority
Gold
10 11 12 13
Silver
14
15
Copper
Page19
ARP 15 is always the lowest priority and is not configurable. It corresponds to lowest
user priority (copper user).
If ARP is not received in messages from the Iu interface, the user priority is regarded as
copper.
282
RAB Integrated Priority

RAB integrated priority is mainly used in load control

algorithms
RAB integrated priority are set according to :

ARP
Traffic Class
Traffic Handling Priority (THP, only for interactive services)
Carrier types: HSPA or DCH
Page20
During load control, the RABs need to be ranked by priority so that they can be chosen
by different load control actions. The priority of a RAB is determined by its traffic class,
ARP, and carrier type. Such a priority is called RAB integrated priority. RAB integrated
priority is mainly used in load control functions.
The values of RAB integrated priority are set according to the integrated priority
configuration reference parameter (PriorityReference):

If the integrated priority configuration reference parameter is set to Traffic Class,
the integrated priority abides by the following rules:

Traffic classes: conversational > streaming > interactive > background

Services of the same class: priority based on Allocation/Retention Priority
(ARP) values, that is, ARP1 > ARP2 > ARP3 > ... > ARP14 > ARP15

Only for the interactive service of the same ARP value: priority based on
Traffic Handling Priority (THP), that is, THP1 > THP2 > THP3 > ... >
THP14 > THP15

Services of the same ARP, traffic class and THP (only for interactive
services): High Speed Packet Access (HSPA) or Dedicated Channel (DCH)
service preferred depending on the carrier type priority indicator
parameter (CarrierTypePriorInd).

If the integrated priority configuration reference parameter is set to ARP, the
integrated priority abides by the following rules:

ARP: ARP1 > ARP2 > ARP3 > ... > ARP14 > ARP15
283
Services of the same ARP: priority based on traffic classes, that is,
conversational > streaming > interactive > background

Only for the interactive service of the same ARP value: priority based on
Traffic Handling Priority (THP), that is, THP1 > THP2 > THP3 > ... >
THP14 > THP15

Services of the same ARP, traffic class and THP (only for interactive
services): HSPA or DCH service preferred depending on the carrier type
priority indicator parameter.
ARP and THP are carried in the RAB ASSIGNMENT REQUEST message, and they
are not configurable on the RNC LMT.
An Example for RAB Integrated Priority

Based on ARP, HSPA priority is higher
Service
ARP
ID
B
Services attribution in the cell

Service
ARP
ID
Traffic Class
Bear
type
Interactive
DCH
Interactive
HSDPA
Conversational
DCH
Background
DCH
Bear
type
Interactive
HSDPA
Interactive
DCH
Conversational
DCH
Background
DCH
Based on Traffic Class, HSPA priority is higher

Service
ID
Traffic Class
ARP
Bear
type
Conversational
DCH
Interactive
HSDPA
Interactive
DCH
Background
DCH
Traffic Class
Page22
This example shows the RAB integrated priority calculation in 2 different conditions.
284
User Integrated Priority

For single-RAB user, the user integrated priority is the

same as the RAB integrated priority
For multiple-RAB user, the user integrated priority is

based on the highest priority of RAB
Page23
A user may have multiple RABs, and the RABs may have different priorities. In this case,
the highest priority is taken as the priority of this user. Such a priority is called user
integrated priority. User integrated priority is used in user-specific load control. For
example, the selection of R99 users during preemption, the selection of users during
inter-frequency load handover for LDR, and the selection of users during switching of BE
services to common channels are performed according to the user integrated priority.
285
Parameters of Priority
PriorityReference
Parameter name: Integrate Priority Configured Reference
Recommended value: ARP
CarrierTypePriorInd
Parameter name: Indicator of Carrier Type Priority
Recommended value: NONE
Page24
PriorityReference

Content: Reference used to determine which priority is arranged first in the

priority sequence. If the ARP is preferably used, the priority sequence is gold >
silver > copper. If the ARPs are all the same, the TrafficClass is used and the
priority sequence is conversational > streaming > interactive > background.
If the TrafficClass is preferably used, the priority sequence is conversational >
streaming > interactive > background. If the TrafficClass factors are all the same,
the ARP factor is used and the priority sequence is gold > silver > copper.
Value range: ARP, TrafficClass
Physical value range: ARP, TrafficClass
CarrierTypePriorInd
Content: Decide which carrier is prior when ARP and TrafficClass are both
identical.

Value range: NONE, DCH, HSPA

Physical value range: NONE, DCH, HSPA
Set these parameters through SET UUSERPRIORITY.
PUC (Potential User Control
286
PUC Principle
The Potential User Control (PUC) algorithm only controls

the Inter-frequency cell reselection of the potential UE,
and prevents UE from camping on a heavily loaded cell
Potential UE:
UE in idle mode
UE in Cell-FACH, Cell-PCH and URA-PCH
Page26
In the WCDMA system, the mobility management of the UE in idle or connected mode is
implemented by cell selection and reselection. The Potential User Control (PUC) function
controls the cell selection and cell reselection of the potential UE and prevents an idle UE
from camping on a heavily loaded cell.
PUC procedure:
287
PUC Load Judgment
Page27
The RNC periodically monitors the downlink load of the cell:

If the cell load is higher than the upper threshold (SpucHeavy) plus the load level
division hysteresis (SpucHyst), the cell load is considered heavy.

If the cell load is lower than the lower threshold (SpucLight) minus SpucHyst, the
cell load is considered light.
Based on the cell load, the PUC works as follows:

If the cell load becomes heavy, the PUC modifies cell selection and reselection
parameters and broadcasts them through system information. In this way, the
PUC leads UEs to the neighboring cells with light load.

If the cell load becomes normal, the PUC uses the cell selection and reselection
parameters configured on the RNC LMT.

If the cell load becomes light, the PUC modifies cell selection and reselection
parameters and broadcasts them through system information. In this way, the
PUC leads UEs to this cell.
288
PUC Procedure
Threshold
Cell TCP
Heavy?
Light?
Normal?
RNC
cell reselection
parameters
System
information
NodeB
PUC-related variables and their impacts on UEs:
289
UE
Page28
PUC Procedure (Cont.)

Normal load
Light load
Freq1
Modify
System Info
SIB3,11
1. Sintersearch
2. Qoffset
Stay
System Info
SIB3,11
Heavy load
Freq2
1. Sintersearch
2. Qoffset
Modify
System Info
SIB3,11
Idle state
CCH state
Page29
Depending on the load status of the serving cell, the cell reselection parameters are
adjusted up or down or kept unchanged. The setting of Sintersearch is related to the
serving cell:
290
The configurations of Qoffset1 and Qoffset are related to the load of the current cell and
the load of the neighboring cells:
291
Parameters of PUC
NBMLdcAlgoSwitch-PUC
Parameter name: Cell LDC algorithm switch for PUC
SpucHeavy
Parameter name: Load level division threshold 1
SpucLight
Parameter name: Load level division threshold 2
NBMLdcAlgoSwitch-PUC

Page31
Content: Potential user control algorithm. Based on the cell load, this algorithm
changes the selection/reselection parameters of a cell to lead the UE to a lighter
loaded cell.
Set this parameter through ADD UCELLALGOSWITCH/ MOD UCELLALGOSWITCH.
SpucHeavy/SpucLight

Content: It is used to decide whether the cell load level is Heavy or Light. It is
denoted by the ratio of NodeB TX power to the maximum TX power.
Value range: 0~100
Physical unit: %
Set this parameter through ADD UCELLPUC/ MOD UCELLPUC.
292
Parameters of PUC (Cont.)

SpucHyst
Parameter name: Load level division hysteresis
PucPeriodTimerLen
Parameter name: PUC period timer length
SpucHyst

Page32
Content: Hysteresis used to determine the cell load level. It is denoted by the ratio
of NodeB TX power to the maximum TX power. It is used to avoid the
unnecessary ping-pong effect of a cell between two load levels due to tiny load
change.
Value range: 0~100
Physical unit: %
Set this parameter through ADD UCELLPUC/ MOD UCELLPUC.
PucPeriodTimerLen

Content: Identifying the potential user control period. When the cell load is high,
the cell selection and reselection can be periodically modified in order to enable
users in unconnected mode to select other cells more easily, thus reducing the
local cell load.
Physical unit: s
Set this parameter through SET ULDCPERIOD.
293

OffSinterLight
Parameter name: Sintersearch offset 1
OffSinterHeavy
Parameter name: Sintersearch offset 2
Page33
OffSinteright

Content: Offset of Sintersearch when center cell load level is "Light.

Value range: -10~10
Physical unit: dB
OffSinterHeavy
Content: Offset of Sintersearch when center cell load level is Heavy.

Value range: -10~10


Physical unit: dB
Set these parameters through ADD UCELLPUC/ MOD UCELLPUC.
294

OffQoffset1Light (for RSCP)

Parameter name: Qoffset1 offset 1
OffQoffset1Heavy (for RSCP)

Page34
OffQoffset1Light

Content: Offset of Qoffset1 when neighboring cell load is lighter than that of the
center cell.
Value range: -20~20
Physical unit: dB
OffSinterHeavy
Content: Offset of Qoffset1 when neighboring cell load is heavier than that of the
center cell.

Value range: -20~20


Physical unit: dB
295

OffQoffset2Light (for Ec/No)

OffQoffset2Heavy (for Ec/No)

Recommended value: 4 namely 4dB
Page35
OffQoffset2Light

Content: Offset of Qoffset2 when neighboring cell load is lighter than that of the
center cell.
Value range: -20~20
Physical unit: dB
OffQoffset2Heavy
Content: Offset of Qoffset2 when neighboring cell load is heavier than that of the
center cell.

Value range: -20~20


Physical unit: dB
296
LDB (Intra-Frequency Load Balancing
LDB Principle
Intra-frequency Load Balancing (LDB) is performed to

adjust the coverage areas of cells by modifying PCPICH
power
LDB affect UEs in all states
Page37
Intra-frequency Load Balancing (LDB) is performed to adjust the coverage areas of cells
according to the measured values of cell load. Currently, the intra-frequency LDB
function is applicable only to the downlink.
LDB between intra-frequency cells is implemented by adjusting the transmit power of
the Primary Common Pilot Channel (PCPICH) according to the downlink load of the
associated cells. When the load of a cell increases, the cell reduces its coverage to
lighten its load. When the load of a cell decreases, the cell extends its coverage so that
some traffic is off-loaded from its neighboring cells to it.
297
LDB Procedure
Page38
The intra-frequency LDB is described as follows:

If the downlink load of a cell is higher than the cell overload threshold
(CellOverrunThd), it is an indication that the cell is heavily overloaded. In this case,
the transmit power of the P-CPICH needs to be reduced step by step. The step is
specified by the PCPICHPowerPace parameter.

If the current transmit power is equal to the minimum transmit power of P-CPICH
(MinPCPICHPower), the current transmit power is not adjusted.

If the downlink load of a cell is lower than the cell underload threshold
(CellUnderrunThd), it is an indication that the cell has sufficient remaining
capacity for more load. In this case, the transmit power of the P-CPICH can be
increased step by step to help lighten the load of neighboring cells. The step is
specified by the PCPICHPowerPace parameter.

If the current transmit power is equal to the maximum transmit power of P-CPICH
(MaxPCPICHPower), the current transmit power is not adjusted.
298
Parameters of LDB
NBMLdcAlgoSwitch-INTRA_FREQUENCY_LDB
Parameter name: Cell LDC algorithm switch for LDB
IntraFreqLdbPeriodTimerLen
Parameter name: Intra-frequency LDB period timer length
NBMLdcAlgoSwitch-INTRA_FREQUENCY_LDB

Page39
Content: Intra-frequency load balance algorithm. It is also named cell breathing

algorithm. Based on the cell load, this algorithm changes the pilot power of the
cell to control the load between intra-frequency cells.
IntraFreqLdbPeriodTimerLen

Content: Identifying the period of the Intra-frequency load balance algorithm.

When the cell load is high, the cell PCPICH TX power can be periodically reduced
in order to enable users in connected mode to be switched over to other cells
more easily, thus reducing the local cell load.
Physical unit: s
299
Parameters of LDB (Cont.)

CellOverrunThd
Parameter name: Cell overload threshold
CellUnderrunThd
Parameter name: Cell underload threshold
PCPICHPowerPace
Parameter name: Pilot power adjustment step
Recommended value: 2, namely 0.2dB
CellOverrunThd

Page40
Content: If the cell downlink load exceeds this threshold, the algorithm will decrease the pilot
transmit power of the cell so as to increase the whole system's capacity. This parameter is based on
network planning. When the cell breathing algorithm is activated, if the value is too small, the
physical coverage of the cell is limited so as to avoid cell capacity waste. If the value is too great,
the physical coverage is expanded and interference over other cells is increased.
Value range: 0~100
Physical unit: %
CellUnderrunThd

Content: If the cell downlink load is lower than this threshold, the algorithm will increase the pilot
transmit power of the cell so as to share load of other cells. This parameter is based on network
planning. When the cell breathing algorithm is activated, if the value is too small, the physical
coverage of the cell is limited so as to avoid cell capacity waste. If the value is too great, the
physical coverage is expanded and interference over other cells is increased.
Value range: 0~100
Physical unit: %
PCPICHPowerPace
Content: Pilot power adjustment step increased or decreased in each increase of the cell breathing
algorithm or decrease of cell pilot. If the value is too great, the cell pilot may change fiercely, which
is easy to lead to user call drops. If the value is too small, the cell pilot may change smoothly.
However, the response speed of the cell breathing algorithm is decreased, impacting the algorithm
performance.

Value range: 0~100


Physical unit: dB
Set these parameters through ADD UCELLLDB/ MOD UCELLLDB.
300
Parameters of LDB (Cont.)

PCPICHPower
Parameter name: PCPICH transmit power
MaxPCPICHPower
Parameter name: Max transmit power of PCPICH
Recommended value: 346, namely 34.6dBm
MinPCPICHPower
Parameter name: Min transmit power of PCPICH
Recommended value: 313, namely 31.3dBm
PCPICHPower

Page41
Content: TX power of the PCPICH in a cell.

Value range: -100~500
Physical unit: dBm
MaxPCPICHPower

Content: Maximum TX power of the PCPICH in a cell.

Physical unit: dBm
MinPCPICHPower
Content: Minimum TX power of the PCPICH in a cell.



Physical unit: dBm
Set these parameters through ADD UPCPICH/ MOD UPCPICHPWR.
301
CAC (Call Admission Control)
Why We Need CAC?

WCDMA is an interference limited system, after a new

service is admitted, the system load will be increased
If a cell is high loaded, a new service will affect the QoS

of ongoing user, even result in call drop
CAC is used to determine whether the system resources

are sufficient to accept a new user's access request or
not
CAC is needed under such scenarios:

RRC connection setup request

RAB admission decision

Handover

Rate reconfiguration
302
Page43
CAC Procedure
Page44
The admission decision is based on:

Available cell code resource

Available cell power resource

NodeB resource state, that is, NodeB credits, which are used to measure the
channel demodulation capability of NodeBs

Available Iub transport layer resource, that is, Iub transmission bandwidth

Number of HSDPA users (only for HSDPA services)

Number of HSUPA users (only for HSUPA services)
A call can be admitted only when all of these resources are available.
303
CAC Algorithm Switches

Power CAC
Uplink CAC algorithm switch: ALGORITHM_SECOND
Downlink CAC algorithm switch: ALGORITHM_FIRST
NodeB credit CAC

CAC algorithm switch: ON
Cell CAC algorithm switch-CRD_ADCTRL: ON
HSDPA user number CAC

Cell CAC algorithm switch-HSDPA_UU_ADCTRL: OFF
HSUPA user number CAC

Cell CAC algorithm switch-HSUPA_UU_ADCTRL: OFF
Page45
Code and Iub resource-based admission control are mandatory and can not be disabled. Other
admission control strategies may be enabled/disabled through the RNC command:

The switch of power CAC can be set by ADD UCELLALGOSWITCH/ MOD
UCELLALGOSWITCH:

Uplink CAC algorithm switch (NBMUlCacAlgoSelSwitch) selects the algorithm used
for power admission in the uplink.

Downlink CAC algorithm switch (NBMDlCacAlgoSelSwitch) selects the algorithm
used for power admission in the downlink.

The switch of NodeB credit CAC can be set by SET UCACALGOSWITCH and ADD
UCELLALGOSWITCH/ MOD UCELLALGOSWITCH:

CAC algorithm switch (CacSwitch) specifies whether to enable or disable the
NodeB level credit CAC algorithm.

Cell CAC algorithm switch (CRD_ADCTRL) specifies whether to enable or disable
the cell level credit CAC algorithm.

The switch of HSDPA user number CAC can be set by ADD UCELLALGOSWITCH/ MOD
UCELLALGOSWITCH:

Cell CAC algorithm switch (HSDPA_UU_ADCTRL) specifies whether to enable or
disable the HSDPA user number admission control algorithm.

The switch of HSUPA user number CAC can be set by ADD UCELLALGOSWITCH/ MOD
UCELLALGOSWITCH:

Cell CAC algorithm switch (HSUPA_UU_ADCTRL) specifies whether to enable or
disable the HSUPA user number admission control algorithm.
304
Code CAC
Code resource CAC is involved in:

RRC connection setup
Handover
R99 services setup
RRC connection setup and handover have higher priority
Page46
When a new service attempts to access the network, code resource-based admission is
mandatory.
Code resourcebased admission is implemented as follows:

For RRC connection setup requests, the code resource-based admission is
successful if the current remaining code resource is sufficient for RRC connection
setup.

For handover services, the code resource-based admission is successful if the
current remaining code resource is sufficient for the service.

For other R99 services, the RNC has to ensure that the remaining code does not
exceed the DlHoCeCodeResvSf parameter after admission of the new service.

For HSDPA services, the reserved codes are shared by all HSDPA services.
Therefore, the code resourcebased admission is not required.
305
Parameter of Code CAC

DlHoCeCodeResvSf
Parameter name: DL handover credit and code reserved SF
Recommended value: SF32
Page47
DlHoCeCodeResvSf

Content: Some cell resources can be reserved for handover UEs to guarantee
handover success rate and improve access priority of handover services. This
parameter defines the quantity of downlink code and CE resources reserved for
handover. SFOFF refers to that no resources is reserved. SF32 refers to that a
code resource with SF = 32 and its corresponding credit resource are reserved.
The backer position the value is in {SF4, SF8, SF16, SF32, SF64, SF128, SF256,
SFOFF}, the less code and credit resources reserved for handover UEs. The
possibility of rejecting handover UE admissions increases and performance of UEs
cannot be guaranteed. The more frontal position the value is, the more the
possibility of rejecting new UEs is and some idle resources are wasted.
Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFF
Physical value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFF
Set this parameter through ADD UCELLCAC/ MOD UCELLCAC.
306
Power CAC
Power resource CAC is involved in:

Handover
Services setup
Page48
The power CAC involves uplink admission control and downlink admission control. The
corresponding admission control switches NBMUlCacAlgoSelSwitch or
NBMDlCacAlgoSelSwitch are independent of each other.
To enable the power-based admission control for HSDPA/HSUPA, the
HSDPA_UU_ADCTRL or HSUPA_UU_ADCTRL must also be set to on.
307
Power CAC Procedure

Page49
The basic principles of power-based admission decision are as follows:

Four basic load thresholds are used for power-based admission decision. They are:

UL/DL access threshold for handover (UlNonCtrlThdForHo or DlHOThd)

UL/DL threshold of conversational AMR service (UlNonCtrlThdForAMR or
DlConvAMRThd)

UL/DL threshold of conversational non-AMR service
(UlNonCtrlThdForNonAMR or DlConvNonAMRThd)

UL/DL threshold of other services (UlNonCtrlThdForOther or DlOtherThd)

With these thresholds, the RNC defines the proportion of speech service to other
services while ensuring handover preference.
For an intra-frequency handover request, only downlink admission decision is needed.
For a non-intra-frequency handover request, both uplink and downlink decisions are
needed if both uplink CAC and downlink CAC are enabled.
If there is a rate downsizing request, the RNC accepts it directly. For a rate upsizing
request, the RNC makes the power CAC decision.
For a rejected RRC connection setup request, the RNC performs DRD or redirection. For a
rejected service request, the RNC performs preemption or queuing according to the
actual situation.
308
Power CAC Algorithms

Algorithm 1: based on UL/DL load measurement and

load prediction (RTWP and TCP)
Algorithm 2: based on Equivalent Number of User (ENU)
Algorithm 3: loose call admission control algorithm
Page50
Algorithm 1 (ALGORITHM_FIRST): admission decision based on predicted load increment

upon admission of a new service

Based on the current cell load (indicated by the uplink load factor and downlink
TCP) and the predicted load increment due to admission of the new service, the
RNC determines whether the cell load will exceed the threshold upon admitting
the new service. If yes, the RNC rejects the access request. If not, the RNC accepts
the access request.
Algorithm 2 (ALGORITHM_SECOND): admission decision based on the ENU

Depending on the current ENU and the access request, the RNC determines
whether the ENU will exceed the threshold upon admitting a new service. If yes,
the RNC rejects the request. If not, the RNC accepts the request.
Algorithm 3 (ALGORITHM_THIRD): admission decision based on no load increment upon
admission of a new service

This algorithm assumes that load increment upon admission of a new service is 0.
Based on the current cell load (indicated by the uplink load factor and downlink
TCP), the RNC determines whether the cell load will exceed the threshold upon
admitting the new service. If yes, the RNC rejects the access request. If not, the
RNC accepts the access request.
309
Power CAC for RRC Connection Setup

For the RRC connection request is, tolerance principles

are applied :
Emergency call, detach, registration:

Direct admission
RRC connection request for other reasons:

Based on UL/DL OLC switches and trigger threshold
Page51
To ensure that the RRC connection setup request is not denied by mistake, tolerance
principles are applied.
The admission decision for RRC connection setup request is as follows:

When power-based admission is based on power or interference (algorithm 1 and
algorithm 3):

For the RRC connection setup request for the reason of emergency call,
detach or registration, direct admission is used.

For the RRC connection setup request for other reasons, the UL or DL OLC
trigger threshold (UlOlcTrigThd or DlOlcTrigThd) is used for admission.

When power-based admission is based on the ENU (algorithm 2):

For the RRC connection setup request for the reason of emergency call,
detach or registration, direct admission is used.

For the RRC connection setup request for other reasons, the admission
decision is made as follows:
a. When UL_UU_OLC or DL_UU_OLC is set to on, RRC connection setup
request is rejected when the cell is in the overload congestion state. If
the cell is not in the overload state, the UL or DL OLC trigger threshold
is used for power-based admission.
b. When UL_UU_OLC or DL_UU_OLC is set to off, the UL or DL OLC
trigger threshold is used for power-based admission.
310
Power CAC Algorithm 1

Power-based admission decision based on algorithm 1

consists of uplink power-based admission decision and
downlink power-based admission decision procedures:
Uplink admission decision:

R99 cell
HSPA cell
Downlink admission decision:

R99 cell
HSPA cell
Page52
Algorithm 1 - Uplink for R99 Cell
311
Page53
The procedure of uplink power-based admission decision for R99 cells is as follows:

The RNC obtains the uplink RTWP of the cell and calculate the current uplink
load factor UL, where PN is the received uplink background noise.

The RNC calculates the uplink load increment UL based on the service request.

The RNC predicts the uplink load factor UL,predicted, where ULcch is specified by
UlCCHLoadFactor.

By comparing the predicted uplink load factor UL,predicted with the
corresponding threshold (UlNonCtrlThdForHo, UlNonCtrlThdForAMR,
UlNonCtrlThdForNonAMR, or UlNonCtrlThdForOther), the RNC decides whether
to accept the access request. If the access request is accepted, the RNC processes
the access request. Otherwise, the RNC rejects the access request.
Parameters of Power CAC

UlCCHLoadFactor
Parameter name: UL common channel load reserved

coefficient
UlNonCtrlThdForHo/UlNonCtrlThdForAMR/UlNonCtrlThdF
orNonAMR/UlNonCtrlThdForOther
Parameter name: UL threshold of handover/Conv AMR/Conv

non_AMR/other service
Recommended value: 80%, 75%, 75%, 60%
Page54
UlCCHLoadFactor
Content: The admission control decision is only for dedicated channels. For
common channels, some resources instead of a special admission procedure are
reserved.
312

Value range: 0~100

Physical unit: %
UlNonCtrlThdForHo/ UlNonCtrlThdForAMR/ UlNonCtrlThdForNonAMR/

UlNonCtrlThdForOther
Content: The percentage of the handover/conversational AMR/conversational
non-AMR/other service thresholds to the 100% uplink load. It is applicable to
algorithm 1 and algorithm 2. If the value is too high the system load after
admission may be over large, which impacts system stability and leads to system
congestion. If the value is too low, the possibility of user rejects may increase,
resulting in waste in idle resources.

Value range: 0~100


Physical unit: %
Set these parameters through ADD UCELLCAC/ MOD UCELLCAC.
Algorithm 1 - Uplink for HSPA Cell

After the RSEPS

measurement is introduced,
the UL RTWP is divided into
two parts: controllable part
and uncontrollable part
The controllable part is

generated by the E-DCH
scheduling service, and
others belong to the
uncontrollable part
Page55
The E-DCH scheduling service involves the following types of UEs:

Type A: UEs of this type are in the serving E-DCH cell.

Type B: UEs of this type are not in the serving E-DCH cell.
The methods of calculating the uplink load vary according to user type:

For type A, the uplink load generated by the E-DCH scheduling service is
calculated as follows:
313
For type B, the uplink load generated by the E-DCH scheduling service is
calculated through UL,EDCH,f, which is set to 0.
The uplink uncontrollable load is calculated as follows:

(Cont.)
Admission of DCH service is based on the following

formulas:
If formulas 1 and 2 are fulfilled, the RNC admits DCH

service. Otherwise, the RNC rejects the access request

Page56
HS-DPCCH is the UlHsDpcchRsvdFactor parameter.

thd is the cell UL admission threshold of a specific type of service. The threshold may
be UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, UlNonCtrlThdForOther, or
UlNonCtrlThdForHo.
thd-total is the UL total power threshold of the current cell (UlCellTotalThd).
314
Parameters of Power CAC (Cont.)

UlHsDpcchRsvdFactor
Parameter name: UL HS-DPCCH reserve factor
UlCellTotalThd
Parameter name: UL total power threshold
UlHsDpcchRsvdFactor

Page57
Content: If the HS-DPCCH carries ACK/NACK, the system will not perform CAC. If
the HS-DPCCH carries CQI, the system will perform CAC. This parameter refers to
the resources reserved for the uplink HS-DPCCH carrying ACK/NACK. The
corresponding threshold is the uplink limit capacity multiplied by this parameter.
If the value is too high, the possibility of wrong rejection to uplink admissions
increases, leading to waste in uplink resources. If the value is too low, the uplink
resources is insufficient. However, because the possibility of burst load by
ACK/NACK and its impact are relatively low, the value can be set to a low level,
representing the loose admission rule.
Value range: 0~100
Physical unit: %
UlCellTotalThd

Content: Admission threshold of total cell uplink power. This parameter is related
to the target load of the uplink schedule. The total uplink load fluctuates closing
to the target load due to the schedule mechanism of the HSUPA. Therefore, the
target load is added with margin, acting as the basis of this parameter. If the
value is too high, the system load after admission may be over large, which
impacts system stability and leads to system congestion. If the value is too low,
the possibility of user rejects may increase, resulting in waste in idle resources. If
the value is lower than the target load threshold of the uplink schedule, the
possibility of user rejects is great.
Value range: 0~100
Physical unit: %
315

(Cont.)
PBR-based application in HSUPA cell

Page58
Since the HSUPA scheduling algorithm consumes additional uplink power resources, the
power load of the HSUPA cell is always relatively high. Therefore, the CAC algorithm
combines the PBR-based decision with the load-based decision to reduce the number of
potential erroneous rejections.
PBR-based decision is used to check whether the QoS requirement of existing users is
fulfilled. The QoS is measured on the basis of the Provided Bit Rate (PBR) of the users. If
the QoS requirement is fulfilled, new users are allowed to access the network.
As shown in the previous figure, the Scheduling Priority Indicator (SPI) of a new HSUPA
user is SPINew user.
ThdL is the low priority HSUPA user PBR threshold (HsupaLowPriorityUserPBRThd).
ThdE is the equal priority HSUPA user PBR threshold (HsupaEqualPriorityUserPBRThd).
ThdGE is the high priority HSUPA user PBR threshold (HsupaHighPriorityUserPBRThd).
316

(Cont.)
The RNC admits the HSUPA scheduling services in either

of the following cases:
Formula 3, 4, or 5 is fulfilled
Formula 2 is fulfilled
For HSUPA non-scheduling services, the RNC admits the

HSUPA non-scheduling services in either of the following
cases:
Formula 3, 4, or 5 is fulfilled
Formulas 1 and 2 are fulfilled
Page59
For the first HSUPA service accessing the cell, the decision formulas that involve PBR are
regarded as unsatisfied.
If the PBR measurement is deactivated, the decision formulas that involve PBR are
If the RSEPS measurement is deactivated, the admission algorithm automatically changes
into algorithm 2.
317

HsupaLowPriorityUserPBRThd/HsupaEqualPriorityUserPB
RThdHsupaHighPriorityUserPBRThd
Parameter name: Low/Equal/High priority HSUPA user PBR

threshold
Recommended value: 100%, 100%, 100%
HsupaLowPriorityUserPBRThd/ HsupaEqualPriorityUserPBRThd/
HsupaHighPriorityUserPBRThd
Content: Threshold of all the HSUPA user PBR whose schedule priority is
lower/equal/higher than that of users to be admitted. If this value is too high, the
possibility of rejecting HSUPA schedule services increases, which impacts access
success rate. If the value is too low, too many HSUPA schedule users may be
admitted, which impacts the admitted users and results in overload and system
congestion.

Value range: 0~100


Physical unit: %
Page60
318
Algorithm 1 - Downlink for R99 Cell
Page61
The procedure of downlink power-based admission decision for R99 cells is as follows:

The RNC obtains the cell downlink TCP and calculates the downlink load factor
DL by dividing the maximum downlink transmit power Pmax by this TCP.

The RNC calculates the downlink load increment DL based on the service
request and the current load.

The RNC predicts the downlink load factor DL,predicted, where DLcch is the
percentage of reserved DL common channel load (DlCCHLoadRsrvCoeff).

By comparing the downlink load factor DL,predicted with the corresponding
threshold (DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, and DlHOThd), the
RNC decides whether to accept the access request.
319

DlCCHLoadRsrvCoeff
Parameter name: DL common channel load reserved

coefficient
DlHOThd/DlConvAMRThd/DlConvNonAMRThd/DlOtherTh
d
Parameter name: DL threshold of handover/Conv AMR/Conv

non_AMR/other service
Recommended value: 85%, 80%, 80%, 75%
Page62
DlCCHLoadRsrvCoeff

Content: Different admission policies are used for dedicated channel and common
channel users. For common channel users, resources instead of separate power
admission decision are reserved.
Value range: 0~100
Physical unit: %
DlHOThd/ DlConvAMRThd/ DlConvNonAMRThd/ DlOtherThd
Content: The percentage of the handover/conversational AMR/conversational

non-AMR/other service thresholds to the 100% downlink load. It is applicable to
algorithm 1 and algorithm 2. If the value is too high the system load after
admission may be over large, which impacts system stability and leads to system
congestion. If the value is too low, the possibility of user rejects may increase,
resulting in waste in idle resources and the failure to achieving network planning
target.

Value range: 0~100


Physical unit: %
320
Algorithm 1 - Downlink for HSPA Cell

Admission of DCH service is based on the following

formulas:
The RNC admits the DCH RAB in either of the following

situations:

Page63
Pnon-hspa is the current non-HSDPA power.

Pcch-res is the power reserved for the common channel.
Pmax is the cell maximum transmit power of the cell.
Thdnon-hspa-cac is the cell DL admission threshold for a specific type of service. The threshold
may be DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, and DlHOThd.
Ptotal is the current downlink transmitted carrier power.
Thdtotal-cac is the threshold of the total DL power of the cell (DlCellTotalThd).
GBP is the minimum power required to ensure the GBR.
Phsupa-res is the power reserved (DlHSUPARsvdFactor) for HSUPA downlink control
channels, that is, E-AGCH/E-RGCH/E-HICH channels.
Pmax-hspa is the maximum available power for HSPA. Its value is associated with the
HSDPA power allocation mode.
If the GBP measurement is deactivated, the GBP involved in the decision formulas is set
to 0.
321

DlCellTotalThd
Parameter name: DL total power threshold
DlHSUPARsvdFactor
Parameter name: DL HSUPA reserved factor
Page64
DlCellTotalThd

Content: Admission threshold of the total cell downlink power. If the value is too
high, too many users will be admitted. However, the throughput of a single user
is easy to be limited. If the value is too low, cell capacity will be wasted.
Value range: 0~100
Physical unit: %
DlHSUPARsvdFactor
Content: Reserved DL power factor for HSUPA user. The higher the value is, the
more resources reserved for the HSUPA control channel, which leads to resource
waste. If the value is too low, HSUPA user quality may be impacted.

Value range: 0~100


Physical unit: %
322

(Cont.)
When the admission of the HSDPA RAB is implemented,

the following formulas apply:

Page65
PBRstrm is the provided bit rate of all existing streaming services.

Thdhsdap-str is the admission threshold for streaming PBR decision (HsdpaStrmPBRThd).
PBRbe is the provided bit rate of all existing BE services.
Thdhsdap-be is the admission threshold for BE PBR decision (HsdpaBePBRThd).
323

(Cont.)
The RNC admits the HSDPA streaming RAB in any of the

following situations:
The RNC admits the HSDPA BE RAB in any of the following

situations:
Page66
If PS conversational services are carried on HSPA, the services can be treated as

streaming services during admission control.
If the GBP measurement is deactivated, the GBP involved in the decision formulas is set
to 0.
If the PBR measurement is deactivated, the decision formulas that involve PBR are
regarded as dissatisfied.
For the first HSDPA service accessing the cell, the decision formulas that involve PBR are
324

HsdpaStrmPBRThd
Parameter name: HSDPA streaming PBR threshold
HsdpaBePBRThd
Parameter name: HSDPA best effort PBR threshold
Page67
HsdpaStrmPBRThd

Content: Average throughput admission threshold of the HSDPA streaming service. If the
sum of PBR of all the accessed streaming users is lower than the average throughput
admission threshold of the HSDPA streaming service multiplied by the sum of GBR of all
the accessed streaming users, it indicates that the QoS of the accessed users cannot be
satisfied and new HSDPA streaming services are not allowed. Otherwise, the QoS can be
satisfied and new HSDPA streaming services are allowed. If the value is too high,
admission requirement of the HSDPA streaming service is strict, which improves the
service quality of the HSDPA streaming service but also may lead to HSDPA capacity
waste. If the value is too low, admission requirement of the HSDPA streaming service is
loose, which allows more HSDPA streaming services but QoS of the HSDPA streaming
service cannot be guaranteed.
Value range: 0~100
Physical unit: %
HsdpaBePBRThd
Content: Average throughput admission threshold of the HSDPA best effort traffic. If the
sum of PBR of all the accessed HSDPA BE users is lower than the average throughput
admission threshold of the HSDPA BE service multiplied by the sum of GBR of all the
accessed HSDPA BE users, it indicates that the QoS of the accessed users cannot be
satisfied and new HSDPA BE services are not allowed. Otherwise, the QoS can be satisfied
and new HSDPA BE services are allowed. If the value is too high, admission requirement
of the HSDPA BE service is strict, which improves the service quality of the HSDPA BE
service but also may lead to HSDPA capacity waste. If the value is too low, admission
requirement of the HSDPA BE service is loose, which allows more BE services but QoS of
the HSDPA BE service cannot be guaranteed.

Value range: 0~100


Physical unit: %
325

When the CAC function uses algorithm 2, the admission

of uplink/downlink power resources uses the algorithm
depending on the Equivalent Number of Users (ENU)
The 12.2 kbit/s AMR traffic is defined as one ENU. Thus,

the 12.2 kbit/s AMR traffic can be used to calculate the
ENU of all other services
Page68
The following table describes the typical ENU of some services (with activity factor to be
100%):
326
Power CAC Algorithm 2 Procedure

Admission request
N
ENU
Get current total ENU
total
(N ) =
ENU
i =1
Get the traffic characteristic, and

estimate the increment of ENU
ENU new
ENU total ( N + 1) = ENU total ( N ) + ENU new
Calculate the predicted ENU
Smaller than
the threshold?
admitted
ENULoad = ENU total ( N + 1) / ENU max
rejected
End of UL/DL CAC

Page69
The procedure of ENU resource decision for uplink/downlink is as follows:

The RNC obtains the total ENU of all existing users.

The RNC gets the ENU of the new incoming user.

The RNC uses the formula (ENUtotal + ENUnew)/ENUmax to forecast the ENU
load, where ENUmax is the configured maximum ENU (UlTotalEqUserNum or
DlTotalEqUserNum).

By comparing the forecasted ENU load with the corresponding threshold, the RNC
decides whether to accept the access request.
The admission thresholds for different types of service are different. The following table
lists the parameters used to set admission thresholds for different types of service:
327

UlTotalEqUserNum
Parameter name: UL total equivalent user number
DlTotalEqUserNum
Parameter name: DL total equivalent user number
Page70
UlTotalEqUserNum

Content: When the algorithm 2 is used, this parameter defines the total
equivalent user numbers corresponding to the 100% uplink load. The parameter
should be related to the admission threshold and actual condition of the network.
If the value is too high, the system load after admission may be over large, which
the possibility of user rejects may increase, resulting in waste in idle resources.
Value range: 1~200
Physical value range:1~200; step: 1
DlTotalEqUserNum
Content: When the algorithm 2 is used, this parameter defines the total
equivalent user number corresponding to the 100% downlink load. he parameter
should be related to the admission threshold and actual condition of the network.
If the value is too high, the system load after admission may be over large, which
the possibility of user rejects may increase, resulting in waste in idle resources.

Value range: 1~200

328

Algorithm 3 is similar to algorithm 1. The difference is

that the estimated load increment in algorithm 3 is
always set to 0
In accordance with the current cell load (uplink load

factor and downlink TCP), the RNC determines whether
the cell load will exceed the threshold, with the
estimated load increment set to 0. If yes, the RNC rejects
the request. If not, the RNC accepts the request
Page71
NodeB Credit CAC

CE is used to measure the channel demodulation

capability of the NodeBs. On the RNC side, it is referred
to the NodeB credit. On the NodeB side, it is the channel
element
The resource of one equivalent 12.2 kbit/s AMR voice

service, including 3.4 kbit/s signaling, is defined as one
CE
There are two kinds of CE, that is, uplink CE supporting

uplink services and downlink CE supporting downlink
services. Therefore, one 12.2 kbit/s AMR voice service
consumes one uplink CE and one downlink CE
329
Page72
The principles of NodeB credit-admission control are similar to those of power-based

admission control, that is, to check in the local cell, local cell group (if any), and NodeB
whether the remaining credit can support the requesting services.
The CE capabilities at the levels of local cell, local cell group, and NodeB are reported to
the RNC through the NBAP_AUDIT_RSP message over the Iub interface.

The CE capability of local cell level indicates the maximum capability in terms of
hardware that can be used in the local cell.

The CE capability of local cell group level indicates the capability obtained after
the license and hardware are taken into consideration.

The CE capability of NodeB level indicates the number of CEs allowed to use as
specified in the license.

For details about local cell, local cell group, and capacity consumption law, refer
to the 3GPP TS 25.433.
According to the capacity consumption laws of common and dedicated channels, the
Controlling RNC (CRNC) debits the amount of the credit resource consumed from or
credits the amount to the Capacity Credit (CC) of the local cell (or local cell group, if any)
based on the SF. The specific scenarios are the addition, removal, and reconfiguration of
the common and dedicated channels.

If the UL CC and the DL CC are separate, they are maintained separately in the
local cell or local cell group.

If the UL CC and DL CC are not separate, only the total CC is maintained in the
local cell or local cell group.
For the DCH service, the RNC uses the MBR to calculate the SF and searches the
following table for the number of consumed CEs.
330
For the HSUPA service, if the NodeB reports through its private interface that the
dynamic CE function of the cell is enabled, the RNC uses the GBR to calculate the
spreading factor. If the NodeB reports that the dynamic CE function is disabled, the RNC
uses the MBR to calculate the spreading factor. If the NodeB does not report whether
the dynamic CE function is enabled, the RNC determines whether to use the GBR or MBR
to calculate the spreading factor, based on the value of HsupaCeConsumeSelectio. Then,
the RNC searches the following table for the number of consumed CEs.
NodeB Credit CAC (Cont.)

NodeB credit CAC is involved in:

Handover
Services setup
331
Page74
When a new service tries to access the network, the admission decision based on NodeB
credit is implemented as follows:

For an RRC connection setup request, the credit resource-based admission is
successful if the current remaining credit resources of the local cell, local cell
group (if any), and NodeB are sufficient for RRC connection setup.

For a handover service, the credit resource-based admission is successful if the
current remaining credit resources of the local cell, local cell group (if any), and
NodeB are sufficient for the service.

For other services, the RNC has to ensure that the remaining credit of the local
cell, local cell group (if any), and NodeB does not exceed the value of
UlHoCeResvSf (for the uplink) or DlHoCeCodeResvSf (for the downlink) after
admission of the new services.
Parameter of NodeB Credit CAC

UlHoCeResvSf
Parameter name: UL handover credit reserved SF
DlHoCeCodeResvSf
Parameter name: DL handover credit and code reserved SF
HsupaCeConsumeSelection
Parameter name: HSUPA Credit Consume Type
Recommended value: MBR
UlHoCeResvSf

Page75
Content: Uplink Credit Reserved by Spread Factor for HandOver. SFOFF means that none of them
are reserved for handover. If the UL spare resource cant satisfy the reserved resource after the
access of a new service, the service will be rejected. If the value is too high, the credit resource
reserved for handover UEs will be less, leading to the increased possibility of rejecting handover UE
admissions, and performance of handover UEs cannot be guaranteed. If the value is too low, the
possibility of rejecting new UEs may increase and some idle resources are wasted.
DlHoCeCodeResvSf
332

Content: Some cell resources can be reserved for handover UEs to guarantee handover success rate
and improve access priority of handover services. This parameter defines the quantity of downlink
code and CE resources reserved for handover. SFOFF refers to that no resources is reserved. SF32
refers to that a code resource with SF = 32 and its corresponding credit resource are reserved. The
backer position the value is in {SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFF}, the less code and
credit resources reserved for handover UEs. The possibility of rejecting handover UE admissions
increases and performance of UEs cannot be guaranteed. The more frontal position the value is, the
more the possibility of rejecting new UEs is and some idle resources are wasted.
HsupaCeConsumeSelection

Content: When the dynamic CE algorithm on NodeB is applied, the CE consumption of HSUPA UE is
based on the GBR. When the dynamic CE algorithm on NodeB is not applied, the CE consumption of
HSUPA UE is based on the MBR. If the CE consumption of HSUPA UE is based on the GBR, the CE
LDR will not select HSUPA users to do data rate reduction. If the CE consumption of HSUPA UE is
based on the MBR,the CE LDR will select HSUPA users to do data rate reduction on condition that
the HSUPA DCCC switch is ON.
Value range: MBR, GBR
Physical value range: MBR, GBR
Set this parameter through ADD UNODEBALGOPARA/ MOD UNODEBALGOPARA.
Iub Resource CAC

Iub overbooking
The Iub overbooking feature considers the statistic

multiplexing of service activities and multiple users
Through the admission of more users, Iub overbooking

increases the resource utilization on the Iub interface
Page76
The Universal Mobile Telecommunications System (UMTS) supports four traffic classes:
conversational, streaming, interactive, and background. The transmission rate varies
with the traffic class as follows:
333
For Circuit Switched (CS) conversational services, the channel transmits voice
signals at a certain rate (for example, 12.2 kbit/s) during a conversation and only
transmits Silence Descriptors (SIDs) at intervals when there is no conversation.

For Packet Switched (PS) interactive and background services, such as web
browsing, there is data transmitted during data downloading. After a web page
has been downloaded, and when the user is reading the page, however, there is
very little data to transfer.
If the Radio Network Controller (RNC) allocates the maximum bandwidth to the
subscriber when a service is established, a large proportion of the Iub transmission
bandwidth is unused. For example, downloading a 50 KB page takes only about one
second, but reading this page needs dozens of seconds. Thus, over 90% of the Iub
transmission bandwidth is not used.
To save the Iub transmission bandwidth for operator use, Huawei provides the Iub
overbooking function, which applies an admission control mechanism to access the
service. Services are admitted according to the different activity factors. PS interactive
and background services can be admitted according to the Guaranteed Bit Rate (GBR). In
this way, the maximum number of users with the minimum number of activity request
to use voice and PS Best Effort (BE) services can access the network, thus achieving a
better utilization of transmission bandwidth.
Iub Resource CAC (Cont.)

Activity factor
RT services, including conversational and streaming services,

are admitted at the Maximum Bit Rate (MBR):
Admission bandwidth = MBR x activity factor
NRT services, including interactive and background services,

are admitted at the GBR:
Admission bandwidth = GBR x activity factor
Page77
For BE services, the GBR can be set by running the SET UUSERGBR command.
334
Activity factors can be configured for different types of service by running the ADD
TRMFACTOR/ MOD TRMFACTOR command.
Default settings of activity factors for typical types of service:
335
Iub Resource CAC Procedure

For handover of a user, the following requirements apply:

Load of the path + Bandwidth required by the user < Total

configured bandwidth of the path
For a new user, the following requirements apply:


configured bandwidth of the path - Bandwidth reserved for
handover
For rate upsizing of a user, the following requirements

apply:

configured bandwidth of the path - Congestion threshold
The parameters of threshold should satisfy with: Bandwidth reserved for handover
Congestion threshold Congestion resolving threshold.
The congestion threshold and the congestion resolving threshold are used to prevent the
ping-pong effect.
Based on the preceding requirement, the user priorities are as follows:

User requesting handover > New user > User requesting rate upsizing
The congestion thresholds are FWDCONGBW and BWDCONGBW, and the congestion
resolving thresholds are FWDCONGCLRBW and BWDCONGCLRBW.
The parameters that are used to reserve bandwidth for handover are as follows:

Page78
FWDHORSVBW
BWDHORSVBW
The admission procedure is as follows:

The new user attempts to be admitted to available bandwidth 1 on the primary path.

If the user succeeds in applying for the resources on the primary path, the user is
admitted to the primary path.

If the user fails to apply for the resources on the primary path, the user then attempts to
be admitted to available bandwidth 2 on the secondary path.

If the user succeeds in applying for the resources on the secondary path, the user is
admitted to the secondary path. If the user fails, the bandwidth admission request of the
user is rejected.
Admission procedure for handover of a user:
336
337
Parameters of Iub Resource CAC

FWDHORSVBW/BWDHORSVBW
Parameter name: Forward/Backward handover reserved bandwidth
Recommended value: 0, namely 0Kbit/s
FWDCONGBW/BWDCONGBW
Parameter name: Forward/Backward congestion threshold
FWDCONGCLRBW/BWDCONGCLRBW
Parameter name: Forward/Backward congestion clear threshold
FWDHORSVBW/BWDHORSVBW

Content: Reserved forward/backward bandwidth for handover user .

Physical unit: Kbit/s
FWDCONGBW/BWDCONGBW

Content: If the available forward/backward bandwidth is less than or equal to this

value, the forward/backward congestion alarm is emitted.
FWDCONGCLRBW/BWDCONGCLRBW
Content: If the available forward/backward bandwidth is greater than this value,
the forward/backward congestion alarm is cleared.



Set these parameters through ADD AAL2PATH/ MOD AAL2PATH (for ATM networking)
and ADD IPPATH/ MOD IPPATH (for IP networking).
Page80
338
HSPA User Number CAC

HSPA user number CAC is involved in:

Cell level
Maximum number of HSPA users in a cell
NodeB level
Maximum number of HSPA users in all the cells configured in one

NodeB
Page81
HSDPA user number CAC:

When HSDPA_UU_ADCTRL is set to on, the HSDPA services have to undergo admission
decision based on the number of HSDPA users.
When a new HSDPA service attempts to access the network, the algorithm admits the
service if the following conditions are met:

The number of HSDPA users in the cell does not exceed the maximum value
specified by MaxHsdpaUserNum.

The number of HSDPA users in the NodeB does not exceed the maximum value
specified by NodeBHsdpaMaxUserNum.
Otherwise, the algorithm rejects the service request.
HSUPA user number CAC:
When HSUPA_UU_ADCTRL is set to on, the HSUPA services have to undergo admission
decision based on the number of HSUPA users.
When a new HSUPA service attempts to access the network, the algorithm admits the
service if the following conditions are met:

The number of the HSUPA users in the cell does not exceed the maximum value
specified by MaxHsupaUserNum.

The number of the HSUPA users in the NodeB does not exceed the maximum
value specified by NodeBHsupaMaxUserNum.
Otherwise, the algorithm rejects the service request.
339
Parameters of HSPA User Number

CAC
MaxHsdpaUserNum
Parameter name: Maximum HSDPA user number
NodeBHsdpaMaxUserNum
Parameter name: NodeB Max HSDPA User Number
MaxHsdpaUserNum

Page82
Content: Maximum number of users supported by the HSDPA channel. The user in
this parameter refers to the user with services on the HSDPA channel, regardless
of the number of RABs carried on the HSDPA channel. Maximum HSDPA user
number cannot exceed the HSDPA capability of the NodeB product, In practice,
the value can be set based on the cell type and the richness of the available
HSDPA power and code resources. If the value is too low, the cell HSDPA capacity
may be reduces, leading to waste in HSDPA resources. If the value is too high,
HSDPA services may be congested.
Value range: 0~100
NodeBHsdpaMaxUserNum

Content: Maximum number of HSDPA users of the NodeB.

Value range: 0~3840
340
Parameters of HSPA User Number

CAC (Cont.)
MaxHsupaUserNum
Parameter name: Maximum HSUPA user number
NodeBHsupaMaxUserNum
Parameter name: NodeB Max HSUPA User Number
MaxHsupaUserNum

Page83
Content: Maximum number of users supported by the HSUPA channel. The user in
this parameter refers to the user with services on the HSUPA channel, regardless
of the number of RABs carried on the HSUPA channel. Maximum HSUPA user
number cannot exceed the HSUPA capability of the NodeB product, In practice,
the value can be set based on the cell type and the richness of the available
HSUPA power and code resources. If the value is too low, the cell HSDPA capacity
may be reduces, leading to waste in HSUPA resources. If the value is too high,
HSUPA services may be congested.
Value range: 0~100
NodeBHsupaMaxUserNum

Content: Maximum number of HSUPA users of the NodeB.

Value range: 0~3840
341
IAC (Intelligent Access Control)
Why we need IAC?

The disadvantages of CAC:

For PS NRT (Non-Real Time) services, CAC is not flexible
No consideration about the priority of different users
No consideration about Directed Retry after CAC rejection
Intelligent means the algorithm can increase admission

successful rate
Page85
The purpose of Intelligent Access Control (IAC) is to increase the access success rate, that
is, RRC connection success rate and RAB setup success rate.
342
IAC Procedure
IAC procedure supported by services:
343
Page86
As shown in the previous figure, the procedure of service access includes the procedures
for RRC connection setup and RAB setup. The successful setup of the RRC connection is
one of the prerequisites for the RAB setup.
During the RRC connection processing, the RNC first performs RRC redirection for
service steering:

If the RNC decides UE access from the current cell, it then makes a resourcebased admission decision through the CAC algorithm. If the resource-based
admission fails, the RNC performs DRD and redirection. Here, the resources
include power resource, code resource, Iub resource, credit resource, and number
of HSPA users.

If the RNC decides UE access from another cell, it then sends an RRC connection
reject message to the UE. The message carries the information about the cell and
instructs the UE to set up an RRC connection to the cell.
During the RAB processing, the RNC performs the following steps:
Performs inter-frequency DRD to select a suitable cell for service steering or load
balancing.
Performs rate negotiation according to the service requested by the UE.
Makes cell resource-based admission decision. If the admission is successful, UE
access is granted. Otherwise, the RNC performs the next step.
Selects a suitable cell, according to the inter-frequency DRD algorithm, from the
cells where no admission attempt has been made, and then goes to 2. If the
attempt fails, the RNC performs the next step.
Selects a suitable cell, according to the inter-RAT DRD algorithm. If the inter-RAT
admission is successful, UE access is granted in the inter-RAT cell. If the inter-RAT
DRD fails or is not supported, the RNC performs the next step.
Makes a preemption attempt. If the preemption is successful, UE access is
granted. If the preemption fails or is not supported, the RNC performs the next
step.
Makes a queuing attempt. If the queuing is successful, UE access is granted. If
the queuing fails or is not supported, the RNC performs the next step.
Performs low-rate access. If the low-rate access is admitted, UE access is granted.
If the low-rate access is unsuccessful, the RNC performs the next step.
Rejects UE access.
344
IAC - RRC Connection Setup

Page88
Before a new service is admitted to the network, an RRC connection must be set up.
During the RRC connection setup, the RRC redirection for service steering function is
used for service steering and load sharing between inter-frequency or inter-RAT cells.
When the resources of a cell for UE access are insufficient, the RNC instructs the UE to
an inter-frequency or inter-RAT cell through DRD or redirection to increase the access
rate.
After receiving an RRC CONNECTION REQUEST message from the UE, the RNC uses the
RRC redirection algorithm for service steering to decide whether the UE may access the
network from the current cell:

If the UE needs to access the network from another cell according to the decision,
the RNC sends an RRC CONNECTION REJECT message to the UE. The message
carries the information about this cell.

If the UE attempts to access the network from the current cell according to the
decision, the RNC uses the CAC algorithm to decide whether an RRC connection
can be set up between the UE and the current cell.

If the RRC connection can be set up between the UE and the current cell,
the RNC sends an RRC CONNECTION SETUP message to the UE.

If no RRC connection can be set up between the UE and the current cell,
the RNC attempts to set up an RRC connection through RRC DRD or RRC
redirection.
345
RRC Redirection for Service Steering

During the RRC connection setup, the RNC implements

service steering between inter-frequency or inter-RAT
cells according to the cause of RRC connection setup. In
addition, the RNC considers the load of the cell for access
and the redirection factors to control the degree of load
balancing
Algorithm switch: DrSwitch-DR_ RRC_DRD_SWITCH
Triggering factor: RedirFactorOfNorm or RedirFactorOfLDR
Target cell: RedirSwitch
Page89
The procedure of RRC redirection for service steering is as follows:

The RNC obtains the information about the service requested by the UE and the capability of the
UE.
If the switch of RRC redirection for service steering is on, the RNC determines the service type
requested by the UE. If the switch is off or the RNC fails to determine the service type, the RNC
handles the RRC connection setup request of the UE in the current cell.
If the RNC succeeds in determining the service type requested by the UE and the switch of RRC
direction for service steering (RedirSwitch) is set to ONLY_TO_INTER_FREQUENCY or
ONLY_TO_INTER_RAT, the RNC performs the next step. Otherwise, the RNC handles the RRC
connection setup request of the UE in the current cell.
Based on the cell load and the redirection factors, the RNC decides whether to perform RRC
redirection for service steering.

If the cell is normal, the RNC generates a random number between 0 and 1 and compares
it with the corresponding unconditional redirection factor (RedirFactorOfNorm). If the
random number is smaller than this factor, the RNC performs the next step. Otherwise,
the RNC handles the RRC connection setup request of the UE in the current cell.

If the cell is in the basic congestion or overload state, the RNC generates a random
number between 0 and 1 and compares it with the value of RedirFactorOfLDR. If the
random number is smaller than this factor, the RNC performs the next step. Otherwise,
the RNC handles the RRC connection setup request of the UE in the current cell.
Based on the setting of RedirSwitch, the RNC takes the corresponding actions:

If RedirSwitch is set to ONLY_TO_INTER_FREQUENCY, the RNC sends an RRC
CONNECTION REJECT message to the UE, redirecting the UE to the destination frequency
carried in the message.

If RedirSwitch is set to ONLY_TO_INTER_RAT, the RNC sends an RRC CONNECTION
REJECT message to the UE. The message carries the information about inter-RAT
neighboring cells.
346
Parameters of IAC
DrSwitch-DR_ RRC_DRD_SWITCH
Parameter name: DRD switch for RRC connection
RedirSwitch
Parameter name: Redirection Switch
RedirFactorOfNorm/RedirFactorOfLDR
Parameter name: Redirection Factor Of Normal/LDR
Recommended value: 0, 100

Content: When the switch is on, DRD and redirection is performed for RRC connection if retry is
required.
RedirSwitch

Page90
Content: This parameter specifies whether the RRC redirection algorithm is valid for the specified
traffic type. The algorithm is valid only when the RRC redirection switch is enabled and when this
parameter is set to ONLY_TO_INTER_FREQUENCY or ONLY_TO_INTER_FREQUENCY. Value OFF
indicates that RRC redirection is not allowed. Value ONLY_TO_INTER_FREQUENCY indicates that
only the RRC redirection to an inter-frequency neighboring cell is allowed. Value
ONLY_TO_INTER_RAT indicates that only the RRC redirection to an inter-RAT neighboring cell is
allowed.
Value range: OFF, ONLY_TO_INTER_FREQUENCY, ONLY_TO_INTER_RAT
Set this parameter through SET UREDIRECTION/ ADD UCELLREDIRECTION.
RedirFactorOfNorm/RedirFactorOfLDR

Content: When the load of the serving cell is within the normal range, a UE may be redirected to
another cell according to the traffic type. This parameter specifies the possibility of redirecting the
UE to another cell. When this parameter is set to 0, the RRC redirection is not performed if the load
of the serving cell is within the normal range. When the UL load state or DL load state of the
serving cell is LDR or OLC, a UE may be redirected to another cell according to the traffic type. This
parameter specifies the possibility of redirecting the UE to another cell. When this parameter is set
to 0, the RRC redirection is not performed if the load state on the serving cell is LDR or OLC. LDR
indicates basic congestion. OLC indicates overload congestion.
Value range: 0~100
Physical unit: %
Set these parameters through SET UREDIRECTION/ ADD UCELLREDIRECTION.
347
RRC DRD
Algorithm switch: DrSwitch-DR_ RRC_DRD_SWITCH
Target cell: intra-band inter-frequency neighboring cells,

which quality is large than threshold:
Page91
The RNC selects intra-band inter-frequency neighboring cells of the current cell. These
neighboring cells are suitable for blind handovers.
The RNC generates a list of candidate DRD-supportive inter-frequency cells. The quality
of the candidate cell meets the above formula. Here:

(CPICH_EcNo)RACH is the cached CPICH Ec/N0 value included in the RACH
measurement report.

DRD_EcNOnbcell is the DRD threshold (DRDEcN0Threshhold).
The RNC selects a target cell from the candidate cells for UE access. If the candidate cell
list contains more than one cell, the UE tries a cell randomly.

If the admission is successful, the RNC initiates an RRC DRD procedure.

If the admission to a cell fails, the UE tries admission to another cell in the
candidate cell list. If all the admission attempts fail, the RNC makes an RRC
redirection decision.
If the candidate cell list does not contain any cell, the RRC DRD fails. The RNC performs
the next step, that is, RRC redirection.
348
Parameters of IAC (Cont.)

DRDEcN0Threshhold
Parameter name: Drd Ec/N0 threshold
Page92
DRDEcN0Threshhold

Content: This parameter is used as the DRD Ec/No threshold of whether to

perform the blind handover. If the Ec/No measured value of the current cell is
greater than this parameter of the inter-frequency neighboring cell, this
neighboring cell can be selected to be the candidate DRD cell.
Value range: -24~0
Physical unit: dB
Set this parameter through ADD UINTERFREQNCELL/ MOD UINTERFREQNCELL.
349
RRC Redirection after DRD Failure

Algorithm switch:
ConnectFailRrcRedirSwitch
Target cell: intra-band inter-frequency neighboring cells

or inter-RAT neighboring cells
Page93
When the RRC DRD fails, the associated RRC connection fails to be set up if the DR_
RRC_DRD_SWITCH subparameter of the DrSwitch parameter is set to OFF or if the
switch of RRC redirection after DRD failure (ConnectFailRrcRedirSwitch) is set to OFF.
Otherwise, the RNC performs the following steps when the RRC DRD fails:

The RNC selects all intra-band inter-frequency cells of the local cell.

The RNC selects candidate cells. The candidate cells are the cells selected in step
1 but exclude the cells that have carried out inter-frequency RRC DRD attempts.

If more than one candidate cell is available, the RNC selects a cell randomly and
redirects the UE to the cell.

If no candidate cell is available,

If the switch of RRC redirection after DRD failure is set to
Only_To_Inter_Frequency, the RRC connection setup fails.

If the switch of RRC redirection after DRD failure is set to
Allowed_To_Inter_RAT, then:
a. If a neighboring GSM cell is configured, the RNC redirects the UE to
that GSM cell.
b. If no neighboring GSM cell is configured, the RRC connection setup fails.
350

ConnectFailRrcRedirSwitch
Parameter name: RRC redirect switch
Recommended value: Only_To_Inter_Frequency
Page94
DRDEcN0Threshhold

Content: This parameter specifies the RRC redirection strategy. OFF: RRC
redirection is not allowed. Only_To_Inter_Frequency: Only RRC redirection to
inter-frequency cells is allowed. Allowed_To_Inter_RAT: RRC redirection to interfrequency cells and redirection to inter-RAT cells are both allowed.
Value range: OFF, Only_To_Inter_Frequency, Allowed_To_Inter_RAT
Physical value range: OFF, Only_To_Inter_Frequency, Allowed_To_Inter_RAT
Set this parameter through SET UDRD.
351
IAC - RAB DRD

The basic procedure of RAB DRD is as follows:

The RNC performs inter-frequency DRD. According to the

purposes of directed retry, Inter-frequency DRD is of the
following types:
Inter-frequency DRD for service steering
Inter-frequency DRD for load balancing
If all admission attempts of inter-frequency DRD fail, the

RNC performs an inter-RAT DRD
If all admission attempts of inter-RAT DRD fail, the RNC

selects a suitable cell to perform preemption and queuing
Page95
Through the RAB DRD procedure, the RNC selects a suitable cell for RAB processing
during access control. RAB DRD is of two types: inter-frequency DRD and inter-RAT DRD.
Inter-frequency DRD is further classified into inter-frequency DRD for service steering
and inter-frequency DRD for load balancing.
After receiving a Radio Access Network Application Part (RANAP) message RAB
ASSIGNMENT REQUEST, the RNC initiates a RAB DRD procedure to select a suitable cell
for RAB processing during access control.
352
Inter-Frequency DRD for Service

Steering
Page96
The procedure of DRD for service steering is as follows:

The RNC determines the candidate cells to which blind handovers can be performed and sorts the
candidate cells in descending order according to service priority.
A candidate cell must meet the following conditions:

The frequency of the candidate cell is within the band supported by the UE.

The quality of the candidate cell meets the requirements of inter-frequency DRD. For
details, refer to RRC DRD.

The candidate cell supports the requested service.
The RNC selects a target cell from the candidate cells in order of service priority for UE access.
If there is more than one cell with the same service priority,

When the cell, in which the UE requests the service, is one of the candidate cells with the
same service priority, preferably, the RNC selects this cell for admission decision.

Otherwise, the RNC randomly selects a cell as the target cell.
The CAC algorithm makes an admission decision based on the status of the target cell.

If the admission attempt is successful, the RNC accepts the service request.

If the admission attempt fails, the RNC removes the cell from the candidate cells and then
checks whether all candidate cells are tried.

If there are any cells where no admission decision has been made, the algorithm
goes back to step 2.

If admission decisions have been made in all the candidate cells, then:
If the service request is an HSPA one, the HSPA request falls back to a
DCH one. Then, the algorithm goes back to step 1 to make an admission
decision based on R99 service priorities.
If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
353
Inter-Frequency DRD for Service

Steering (Cont.)
Cell service priorities refer to the priorities of cells under

the same coverage accepting specific service types. These
priorities help achieve traffic absorption in a hierarchical
way
Cell
Service
Priority
Group
Identity
Service
Priority of
R99 RT
Service
Service
Priority of
R99 NRT
Service
Service
Priority of
HSPA
Service
Service
Priority of
Other
Service
Page97
Service priority groups are configured on the LMT. In each group, priorities of R99 RT
services, R99 NRT services, HSPA services, and other services are defined.
The priorities of specific service types in cells are configurable. If a cell does not support
a service type, the priority of this service type is set to 0 in this cell. The group of service
priorities in each cell is specified by the service priority group identity (SpgId) parameter.
When selecting a target cell for RAB processing, the RNC selects a cell with a high
priority, that is, a cell that has a small value of service priority.
354

ServiceDiffDrdSwitch
Parameter name: Service differential drd switch
SpgId
Parameter name: Service priority group Identity
PriorityServiceForR99RT/R99NRT/HSPA/ExtRab
Parameter name: Service priority of R99 RT/R99

NRT/HSPA/Other service
Recommended value: 1, 1, 1, 1
ServiceDiffDrdSwitch

Content: This parameter specifies whether the service differential DRD algorithm
will be applied.
Set this parameter through ADD UCELLDRD/ SET UDRD.
SpgId

Page98
Content: This parameter identifies a group of cells that have specific capabilities
for four service types: R99 real-time services, R99 non-real-time services, HSPA
services, and other services.
Value range: 1~8
Set this parameter through ADD USPG/ MOD USPG.
PriorityServiceForR99RT/R99NRT/HSPA/ExtRab

Content: These parameters specifie the capability of the cells with a specific SpgId
for R99 real-time/R99 non-real-time/HSPA/extension services. The value 0 means
that these cells do not support these kinds of services. The value 1 indicates the
highest priority whereas the value 7 indicates the lowest.
Value range: 0~7
Set these parameters through ADD USPG/ MOD USPG.
355
Inter-Frequency DRD for Load

Balancing
Load balancing considers two resources, power and code:

The availability of power-based DRD for load balancing for

DCH service is specified by the LdbDRDSwitchDCH
parameter
The availability of power-based DRD for load balancing for

HSDPA service is specified by the LdbDRDSwitchHSDPA
parameter
The availability of code-based DRD for load balancing is

specified by the CodeBalancingDrdSwitch parameter
Page99
If the UE requests a service setup or channel reconfiguration in an area covered by

multiple frequencies, the RNC sets up the service on a carrier with a light load to achieve
load balancing among the cells on the different frequencies.
In practice, it is recommended that only either a power-based DRD for load balancing or
a code-based DRD for load balancing be activated. If both are activated, power-based
DRD for load balancing takes precedence over code-based DRD for load balancing.
Code-based DRD for load balancing is applicable to only R99 services because HSDPA
services use reserved codes.
356

LdbDRDSwitchDCH
Parameter name: Load balance DRD switch for DCH
LdbDRDSwitchHSDPA
Parameter name: Load balance DRD switch for HSDPA
CodeBalancingDrdSwitch
Parameter name: Code balance drd switch
LdbDRDSwitchDCH

Page100
Content: This parameter specifies whether the load balancing DRD algorithm will
be applied for services carried on DCH.
LdbDRDSwitchHSDPA

Content: This parameter specifies whether the load balancing DRD algorithm will
be applied for services carried on HS-DSCH.
CodeBalancingDrdSwitch
Content: This parameter specifies whether the code balancing DRD algorithm will
be applied.


Set these parameters through ADD UCELLDRD/ SET UDRD.
357
Power-Based DRD for Load Balancing

Two algorithms are available for power-based load balancing:
Algorithm 1: DL non-HSDPA power and DL HS-DSCH GBP
Algorithm 2: DCH ENU and HSDPA ENU
Cell B has a lighter load of non-HSDPA power than cell A. If the UE requests a DCH
service in cell A, preferably, the RNC selects cell B for the UE to access
Cell A has a lighter load of HS-DSCH GBP than cell B. If the UE requests an HSDPA
service in cell B, preferably, the RNC selects cell A for the UE to access
Page101
Algorithm 1: DRD for load balancing is performed according to the cell measurement
values about the DL non-HSDPA power and DL HS-DSCH GBP.

For DCH service, the RNC sets up the service on a carrier with a light load of nonHSPA power to achieve load balancing among the cells at the different
frequencies.

For HSDPA service, the RNC sets up the service on a carrier with a light load of
HS-DSCH GPB to achieve load balancing among the cells at different frequencies.
Algorithm 2: DRD for load balancing is performed according to the DCH ENU and HSDPA
user number.

For DCH service, the RNC sets up the service on a carrier with a light load of DCH
ENU to achieve load balancing among the cells on different frequencies.

For HSDPA service, the RNC sets up the service on a carrier with a light load of
HSDPA user to achieve load balancing among the cells on different frequencies.
358

LdbDRDchoice
Parameter name: Load balance DRD choice
Recommended value: UserNumber, namely Alogrithm 2
Page102
LdbDRDchoice

Content: This parameter specifies which choice the load balancing DRD algorithm
will be applied. Power: Power (Downlink none-HSDPA power is used for services
carried on DCH, and downlink HSDPA guarantee power is used for services
carried on HS-DSCH) will be applied to the load balancing DRD algorithm.
UserNumber: User number (Downlink R99 equivalent user number is used for
services carried on DCH, and downlink HSDPA user number is used for services
carried on HS-DSCH) will be applied to the load balancing DRD algorithm.
Value range: Power, UserNumber
Physical value range: Algorithm 1, Algorithm 2
Set these parameters through ADD UCELLDRD/ SET UDRD.
359

(Cont.)
Page103
The procedure of power-based DRD for load balancing is as follows:

The RNC determines the candidate cells to which blind handovers can be performed.
A candidate cell must meet the following conditions:

The frequency of the candidate cell is within the band supported by the UE.

The quality of the candidate cell meets the requirements of inter-frequency DRD.

If the current cell is such a candidate cell, the RNC goes to step 3. Otherwise, the RNC
selects a cell with the lightest load from the candidate cells as the target cell and then
goes to step 4.
The RNC determines whether the DL radio load of the current cell is lower than the
threshold of power-based DRD for load balancing (condition 1). Based on the bearer
type (DCH or HSDPA) of the requested service, the RNC selects an appropriate condition.

If the condition 1 is met, the service tries admission to the current cell. And go to
step 5.

Otherwise, go to step 4.
360
The RNC selects a target cell for UE access.

The RNC determines whether any inter-frequency neighboring cell meets the
condition 2. Based on the bearer type (DCH or HSDPA) of the requested service,
the RNC selects an appropriate condition.

Then, the RNC selects the target cell as follows:

If there is only one inter-frequency neighboring cell that meets the
conditions of DRD for load balancing, the RNC selects this cell as the
target cell. If there are multiple such cells:
For a DCH service:
a. If algorithm 1 is used, the RNC selects the cell with the lightest nonHSDPA load as the target cell.
b. If algorithm 2 is used, the RNC selects the cell with the lightest load
of DCH ENU as the target cell.
For an HSDPA service:
a. If algorithm 1 is used, the RNC selects the cell with the lightest load
of HS-DSCH required power as the target cell.
b. If algorithm 2 is used, the RNC selects the cell with the lightest load
of HSDPA user as the target cell.

If there is no such cell, the RNC selects the current cell as the target cell.
The CAC algorithm makes an admission decision based on the status of the target cell.

If the admission attempt is successful, the RNC admits the service request.

If the admission attempt fails, the RNC checks whether admission decisions have
been made in all candidate inter-frequency neighboring cells.

If there is any cell where no admission decision is made, the algorithm
goes back to step 2.

If admission decisions have been made in all the candidate cells:
When the service request is an HSPA one, the HSPA request falls
back to a DCH one. Then, the algorithm goes back to step 1 to
make an admission decision based on R99 service priorities.
When the service request is a DCH one, the RNC initiates an interRAT DRD.
361

(Cont.)
DRD condition 1:
For algorithm 1:
For DCH bearer:
(Thd
AMR , cutcell
For HSDPA bearer:
(Thd
Pnon H , cutcell ) > Thd non H
total , cutcell
PGBP , cutcell ) > Thd H
For algorithm 2:
For DCH bearer:
(Thd
AMR ,cutcell
PD ENU , cutcell ) > Thd non H
For HSDPA bearer:
(Thd
H ue , cutcell
PH ue ,cutcell ) / Thd H ue ,cutcell > Thd H
362
Page105

Recommended values for power-based DRD condition 1:

Parameter
DL threshold of Conv AMR

service
80%
LdbDRDLoadRemainT
hdDCH
DlCellTotalThd
Dl load balance DRD power

remain threshold for DCH
35%
DL total power threshold
90%
LdbDRDLoadRemainT
hdHSDPA
Dl load balance DRD power

remain threshold for HSDPA
100%
MaxHsdpaUserNum
Maximum HSDPA user

number
64
DlConvAMRThd
Content: Admission threshold of the total cell downlink power.

LdbDRDLoadRemainThdHSDPA
Content: This parameter specifies the downlink load threshold to trigger load
balancing DRD for services carried on DCH. The load balancing DRD will probably
be triggered only when the downlink cell remanent non H power or remanent
R99 equivalent user number is less than this threshold.
DlCellTotalThd
Content: The percentage of the conversational AMR service threshold to the

100% downlink load. It is applicable to algorithm 1 and algorithm 2.
LdbDRDLoadRemainThdDCH
Page106
DlConvAMRThd
Recommended
value
Parameter name
Content: This parameter specifies the downlink load threshold to trigger load
balancing DRD for services carried on HS-DSCH. The load balancing DRD will
probably be triggered only when the downlink cell remanent HSDPA guarantee
power or remanent HSDPA user number is less than this threshold.
MaxHsdpaUserNum
Content: Maximum number of users supported by the HSDPA channel. The user in
this parameter refers to the user with services on the HSDPA channel, regardless
of the number of RABs carried on the HSDPA channel.
363

(Cont.)
DRD condition 2:
Algorithm
Bearer
DCH
Algorithm
1
HSDPA
DCH
Algorithm
2
HSDPA
Formula
(Thd
(Thd
(Thd
(Thd
AMR,nbcell
PnonH ,nbcell ) (ThdAMR,cutcell PnonH ,cutcell ) > ThdD,loadoffset
total ,cutcell
Pload ,cutcell ) (Thdtotal ,nbcell Pload ,nbcell ) < Thdtotal ,loadoffset
total ,nbcell
PGBP ,nbcell ) (Thdtotal ,cutcell PGBP,cutcell ) > Thd H ,loadoffset
total , cutcell
Pload ,cutcell ) (Thdtotal ,nbcell Pload ,nbcell ) < Thdtotal ,loadoffset
(Thd
PDenu,nbcell ) (ThdAMR,cutcell PDenu,cutcell ) >ThdD,loadoffset
(Thd
PHue,nbcell ) /ThdHue,nbcell (ThdHue,cutcell PHue,cutcell ) /ThdHue,cutcell
AMR,nbcell
Hue,nbcell
> ThdH,loadoffset
364
Page107

Recommended values for power-based DRD condition 2:

Parameter
LdbDRDOffsetDCH
Load balance DRD offset

for DCH
10%
LdbDRDOffsetHSDPA
Load balance DRD offset

for HSDPA
10%
LdbDRDTotalPwrProThd
Load balance DRD total

power protect threshold
30%
Page108
LdbDRDOffsetDCH
Recommended
value
Parameter name
Content: This parameter specifies the threshold of remanent load offset between
the current cell and the target cell when load balancing DRD is applied for DCH
users. Only when the remanent load offset reaches this threshold can a
neighboring cell be selected as a candidate DRD cell for DCH users. (If Load
balance DRD choice is Power, additional condition should also be statisfied, that
is total power remain difference between the current cell and target cell should
be less than Load Balance DRD Total Power Protect Threshold; if Load balance
DRD choice is UserNumber, additional condition is not needed.)
LdbDRDOffsetHSDPA
Content: This parameter specifies the threshold of remanent load offset between
the current cell and the target cell when load balancing DRD is applied for HSDPA
users. Only when the remanent load offset reaches this threshold can a
neighboring cell be selected as a candidate DRD cell for HSDPA users. (If Load
balance DRD choice is Power, additional condition should also be statisfied, that
is total power remain difference between the current cell and target cell should
be less than Load Balance DRD Total Power Protect Threshold; if Load balance
DRD choice is UserNumber, additional condition is not needed.)
LdbDRDTotalPwrProThd
Content: This parameter specifies the threshold of the downlink remanent total
power difference between the current cell and the target cell when load
balancing DRD is applied and the load balancing DRD choice is Power. Only when
the downlink remanent total power difference is less than this threshold can a
neighboring cell be selected as a candidate DRD cell.
Set these parameters through SET UDRD.
365
Code-Based DRD for Load Balancing
Page109
The procedure of code-based DRD for load balancing is as follows:

The RNC determines whether the minimum remaining SF of the current cell is smaller
than the minimum SF threshold of DRD for code balancing (CodeBalancingDrdMinSFThd).

If the minimum SF is smaller than this threshold, the RNC tries the admission of
the service request to the current cell.

If the minimum SF is not smaller than this threshold, the RNC goes to the next
step.
The RNC determines whether the code load of the current cell is lower than the code
occupation rate threshold of DRD for code balancing (CodeBalancingDrdCodeRateThd).

If the code load is lower than this threshold, the service tries the admission to the
current cell.

If the code load is higher than or equal to this threshold, the RNC selects the cell
with the lightest load or the current cell as the target cell. The RNC selects the
cell as follows:

If the minimum SF supported by the cell with the lightest code load is the
same as that supported by the current cell, and the difference between
the code resource occupancies of the two is larger than or equal to the
value of DeltaCodeOccupiedRate, the RNC selects the cell with the lightest
code load as the target cell. Otherwise, the RNC selects the current cell as
the target cell.

If the minimum SF supported by the cell with the lightest code load is
smaller than the minimum SF supported by the current cell, the RNC
selects the cell with the lightest code load as the target cell.
366

Recommended values for code-based DRD:

Parameter
Recommended
value
Parameter name
CodeBalancingDrdMinSFT Minimum SF threshold for

hd
code balance drd
CodeBalancingDrdCodeR
ateThd
Code occupied rate

threshold for code
balancing drd
13%
DeltaCodeOccupiedRate
Delta code occupied rate
7%
Content: This parameter specifies one of the triggering conditions of code

balancing DRD. (The other condition is the code occupancy.) This condition refers
to that the minimum spreading factor of the best cell is not smaller than the value
of this parameter.
CodeBalancingDrdCodeRateThd
Page110
CodeBalancingDrdMinSFThd
SF8
Content: This parameter specifies one of the triggering conditions of code

balancing DRD. (The other condition is the minimum spreading factor.) This
condition refers to that the code occupancy in the best cell is not lower than the
value of this parameter.
DeltaCodeOccupiedRate
Content: This parameter specifies the threshold of code occupancy offset between
the current cell and the target cell when code balancing DRD is applied. Only
when the cell code occupancy offset reaches this threshold can a neighboring cell
be selected to be a candidate cell for DRD.
Set this parameter through SET UDRD.
367
Inter-Frequency DRD
Relation Between DRD for Service Steering and DRD for

Load Balancing:
When both DRD for service steering and DRD for load
balancing are enabled, the general principles of interfrequency DRD are as follows:
DRD for service steering takes precedence over DRD for load
balancing, that is, preferably considers service priorities
To services of the same service priority, load balancing applies
Page111
For example, Universal Terrestrial Radio Access Network (UTRAN) f1, UTRAN f2, UTRAN f3, and
UTRAN f4 are inter-frequency cells with the same coverage. The service priorities of real-time R99
services in these cells are listed in the following table.
According to the principles of inter-frequency DRD, the RAB DRD of a real-time R99 service will
select UTRAN f3 to make a CAC decision, as shown in the following figure.
368
Inter-Frequency DRD Procedure
Page112
The procedure of inter-frequency DRD is as follows:

If DRD for service steering is enabled but DRD for load balancing is disabled, as shown
in A in the previous figure, the inter-frequency DRD procedure is the procedure of DRD
for service steering.

If DRD for load balancing is enabled but DRD for service steering is disabled, as shown
in B in the previous figure, the inter-frequency DRD procedure is the procedure of DRD
for load balancing.

If both DRD for load balancing and DRD for service steering are disabled:
The UE attempts to access the current cell when its service priority is not 0. If the
service priority of the current cell is 0, the UE attempts to access another
candidate cell whose service priority is not 0.
The CAC algorithm makes an admission decision based on the cell status.

If the admission attempt is successful, the RNC admits the service request.

If the admission attempt fails, the UE attempts to access another
candidate cell randomly.
If any request for access to a candidate cell is rejected, then:

If the service request is an HSPA one, the HSPA request falls back to a
DCH one. Then, the algorithm goes back to step 1 to retry admission
based on R99 service priorities.

If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
369
If both DRD for load balancing and DRD for service steering are enabled:
The RNC determines the candidate cells to which blind handovers can be
performed. A candidate cell must meet the following conditions:


The frequency of the candidate cell is within the band supported by the
UE.

The quality of the candidate cell meets the requirements of interfrequency DRD.
The RNC selects a target cell from the candidate cells for UE access.
Based on the relation between DRD for service steering and DRD for load
balancing:

The RNC preferably selects the cell with the highest service priority.

If there are multiple cells with the highest service priority, load balancing
applies to these cells.
The CAC algorithm makes an admission decision based on the resource status of
the cell.

If the admission attempt is successful, the RNC initiates an inter-frequency
blind handover to the cell.

If the admission attempt fails, the RNC removes the cell from the
candidate cells and then checks whether all candidate cells are tried.
a. If there is any candidate cell not tried, the algorithm goes back to step
2 to try this cell.
b. If all candidate cells haven been tried, then:
-If the service request is an HSPA one, the HSPA request falls back to a
DCH one. Then, the algorithm goes back to step 1 to retry admission
based on R99 service priorities.
-If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
370
Inter-RAT DRD
Page114
The inter-RAT DRD procedure is as follows:

If the current cell is configured with any neighboring GSM cell suitable for blind
handover, and if the "service handover" IE that is contained in the RAB assignment
signaling assigned by the CN is set to "handover to GSM should be performed", then the
RNC performs step 2. Otherwise, the service request undergoes preemption and queuing.
The RNC generates a list of candidate DRD-supportive inter-RAT cells that fulfill the
following requirement:
Here:
(CPICH_EcNO)RACH is the cached CPICH Ec/N0 value included in the RACH
measurement report.

DRD_EcNOnbcell is the DRD threshold (DRDEcN0Threshhold).

If the candidate cell list does not include any cell, the service request undergoes
preemption and queuing.
The RNC selects target GSM cells for the service request according to the blind handover
priority.
If all admission attempts fail or the number of inter-RAT handover retries exceeds the
value of DRMaxGSMNum, the service request undergoes preemption and queuing.

371

DRDEcN0Threshhold
Parameter name: Drd Ec/N0 threshold
DRMaxGSMNum
Parameter name: Max inter-RAT direct retry number
DRDEcN0Threshhold

Page115
Content: This parameter is used as the DRD Ec/No threshold of whether to

perform the blind handover. This parameter is used as the DRD Ec/No threshold of
whether to perform the blind handover. When choosing a DRD candidate cell, if
the Ec/No value of the current cell is greater than the threshold of inter-RAT/interfrequency neighboring cell, the DRD is permitted.
Value range: -24~0
Physical unit: dB
Set this parameter through ADD U2GNCELL/ MOD U2GNCELL.
DRMaxGSMNum

Content: This parameter specifies the maximum number of inter-RAT RAB

directed retries. It decides the size of the candidate set for inter-RAT DRD. The
value 0 indicates that inter-RAT RAB DRD is not applicable.
Value range: 0~5
372
IAC - Rate Negotiation

Rate negotiation includes:

MBR negotiation
GBR negotiation
Initial rate negotiation
Target rate negotiation
Page116
MBR Negotiation
If the IE "Alternative RAB Parameter Values" is present in

the RANAP RAB ASSIGNMENT REQUEST or the
RELOCATION REQUEST message when a PS service is set
up, reconfigured, or admitted, then the RNC and the CN
negotiate the rate according to the UE capability to
obtain the MBR while ensuring a proper QoS
373
Page117
For the PS streaming service, when PS_STREAM_IU_QOS_NEG_SWITCH is set to 1, the Iu

QoS negotiation function is enabled for MBR negotiation.
For the PS BE service:

When both PS_BE_IU_QOS_NEG_SWITCH and
PS_BE_STRICT_IU_QOS_NEG_SWITCH are set to 1, the Iu QoS negotiation function
is enabled, and the RNC determines the MBR of Iu QoS negotiation based on the
information about UE capability, cell capability and other settings.

When PS_BE_IU_QOS_NEG_SWITCH is set to 1 and
PS_BE_STRICT_IU_QOS_NEG_SWITCH is set to 0, the Iu QoS negotiation function
is enabled, and the RNC determines the MBR of Iu QoS negotiation based on the
maximum rate supported by the UE rather than the cell capability and other
settings.

PsSwitch-PS_STREAM_IU_QOS_NEG_SWITCH
Parameter name: PS rate negotiation switch for Streaming service
PsSwitch-PS_ BE_IU_QOS_NEG_SWITCH
Parameter name: PS rate negotiation switch for BE service
PsSwitch-PS_BE_STRICT_IU_QOS_NEG_SWITCH
Parameter name: PS rate negotiation switch for strict BE service

Page118
Content: When the switch is on, the Iu QoS Negotiation function is applied to the PS
STREAM service if Alternative RAB Parameter Values IE is present in the RANAP RAB
ASSIGNMENT REQUEST or RELOCATION REQUEST message.
PsSwitch-PS_ BE_IU_QOS_NEG_SWITCH
374

Content: When the switch is on, the Iu QoS Negotiation function is applied to the PS BE
service if Alternative RAB Parameter Values IE is present in the RANAP RAB ASSIGNMENT
REQUEST or RELOCATION REQUEST message.
PsSwitch-PS_BE_STRICT_IU_QOS_NEG_SWITCH
Content: When the switch is on, the strict Iu QoS Negotiation function is applied to the PS
BE service, RNC select Iu max bit rate based on UE capacity, cell capacity, max bitrate and
alternative RAB parameter values in RANAP RAB ASSIGNMENT REQUEST or RELOCATION
REQUEST message. When the switch is off, the loose Iu QoS Negotiation function is
applied to the PS BE service, RNC select Iu max bit rate based on UE capacity, max bitrate
and alternative RAB parameter values in RANAP RAB ASSIGNMENT REQUEST or
RELOCATION REQUEST message, not consider cell capacity, this can avoid Iu QoS
Renegotiation between different cell. The switch is valid when
PS_BE_IU_QOS_NEG_SWITCH is set to ON.


Set these parameters through SET UCORRMALGOSWITCH.
GBR Negotiation
During the setup, reconfiguration, or handover of a realtime PS service, if the RAB assignment message carries
multiple alternative GBRs and
PS_STREAM_IU_QOS_NEG_SWITCH is set to 1, the RNC

selects the minimum rate as the GBR of this RAB and
sends it to the CN. If the IE "Type of Alternative
Guaranteed Bit Rate Information" in the message is set to
unspecified, the GBR is set to 8 kbit/s
375
Page119
Initial Rate Negotiation

For a non-real-time service in the PS domain, the RNC selects

an initial rate to allocate bandwidth for the service before the
admission request based on cell resources in the following
cases:
A service is set up
The UE state changes from CELL_FACH to CELL_DCH
The negotiation is based on the cell load information, which

includes:
Uplink and downlink radio bearer status of the cell
Minimum spreading factor (SF) supported
HSPA capability
Page120
Initial Rate Negotiation (Cont.)

Initial rate definition for DCH services:
DCCC
Switch
PS BE Initial Rate Dynamic

Configuration Switch
Actual Initial Rate
ON
In the uplink, the initial rate is the smaller one

of the MBR and 384 kbit/s.
In the downlink, the initial rate is dynamically
set on the basis of Ec/No. For the specific
method, see the following description.
ON
OFF
In the uplink, the initial rate is the smaller one

of the MBR and the initial rate of the uplink
BE service.
In the downlink, the initial rate is the smaller
one of the MBR and the initial rate of the
downlink BE service.
OFF
MBR
ON
376
Page121
As described in the table, when the two switches are ON, the initial rate is dynamically
set on the basis of Ec/No in the downlink. The specific method is as follows:

When receiving an RRC connection setup request, the RNC starts the timer
EcN0EffectTime.

Before the timer expires, the RNC dynamically sets the initial rate based on the PCPICH Ec/No carried in the RRC CONNECTION REQUEST message:

If the cell Ec/No is above the Ec/No threshold (EcN0Ths), the RNC sets the
actual initial rate to the smaller one of the MBR and 384 kbit/s.

If the cell Ec/No is below or at the Ec/No threshold (EcN0Ths) or the RRC
CONNECTION REQUEST message does not carry the information about
Ec/No, the RNC sets the actual initial rate to the smaller one of the MBR
and the initial rate of the downlink BE service (DlBeTraffInitBitrate).

DraSwitch-DRA_DCCC_SWITCH
Parameter name: Dynamic resource allocation switch for

DCCC
PsSwitch-PS_BE_INIT_RATE_DYNAMIC_CFG_SWITCH
Parameter name: PS rate negotiation switch for initial rate

reconfiguration

Page122
Content: When the switch is on, the dynamic channel reconfiguration control
algorithm is used for the RNC.
PsSwitch-PS_BE_INIT_RATE_DYNAMIC_CFG_SWITCH
377
Content: When the switch is on, the initial rate of the service should be
dynamically configured according to the value of Ec/No reported by the UE when
the PS BE service is established.


Set these parameters through SET UCORRMALGOSWITCH.

EcN0EffectTime
Parameter name: Ec/N0 effective time
EcN0Ths
Parameter name: Ec/N0 threshold
Recommended value: 41, namely -4dB
DlBeTraffInitBitrate
Parameter name: DL BE traffic Initial bit rate
Recommended value: D64, namely 64kbit/s
EcN0EffectTime

Page123
Content: This parameter specifies the time duration when the reported Ec/No is
valid. The reported Ec/No is valid for the period (starting from the time when the
RRC connection request is initiated) specified by this parameter.
Physical unit: ms
Set this parameter through ADD UCELLFRC/ SET UFRC.
EcN0Ths
Content: This parameter specifies the threshold for determining the signal quality
in a cell. If the reported Ec/No exceeds the value of this parameter, you can infer
that the signal quality in the cell is good and a high code rate can be set for initial
access.
Value range: 0~49
378

Physical value range: -24.5~0 (0: -24.5, 1: -24 49: 0)

Physical unit: dB
Set this parameter through ADD UCELLFRC/ SET UFRC.
DlBeTraffInitBitrate

Content: DL BE traffic Initial bit rate. When DCCC function is enabled, the
downlink initial bit rate will be set to this value if the downlink max bit rate is
higher than the initial bit rate.
Value range: D8, D16, D32, D64, D128, D144, D256, D384
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384
Physical unit: kbit/s
Set this parameter through SET UFRC.
Initial Rate Negotiation (Cont.)

Initial rate definition for HSUPA services:

If HSUPA_DCCC_SWITCH is set to 1, the actual initial rate is

the initial rate of the HSUPA BE service (HsupaInitialRate)
If the HSUPA DCCC function is disabled, the actual initial

rate is the MBR
379
Page124

DraSwitch-DRA_HSUPA_DCCC_SWITCH
Parameter name: Dynamic resource allocation switch for

HSUPA DCCC
HsupaInitialRate
Parameter name: Initial rate of HSUPA BE traffic
Recommended value: D256, namely 256kbit/s
DraSwitch-DRA_HSUPA_DCCC_SWITCH

Page125
Content: When the switch is on, the DCCC algorithm is used for HSUPA. The DCCC
switch must be also on before this switch takes effect.
HsupaInitialRate

Content: HSUPA BE traffic Initial bit rate. When DCCC algorithm switch and
HSUPA DCCC algorithm switch are enabled, the uplink initial bit rate will be set to
this value if the uplink max bit rate is higher than the initial bit rate.
Value range: D8, D16, D32, D64, D128, D144, D256, D384, D608, D1440, D2048,
D2880, D5740
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384, 608, 1440, 2048, 2880,
5740
Physical unit: kbit/s
Set this parameter through SET UFRC.
380
Target Rate Negotiation

For a non-real-time service in the PS domain, if cell

resource-based admission fails, the RNC selects a target
rate to allocate bandwidth for the service based on cell
resource in following cases:
Service setup
Soft handover
DCCC rate upsizing
Page126
If the cell has sufficient code and CE resources, the RNC sets the candidate target rate to
the one that matches the cell resource surplus. Then, the RNC sets the target rate to the
greater one of the candidate target rate and the GBR.
In the case of soft handover, the actual target rate is the candidate target rate set by the
RNC.
In the case of DCCC rate upsizing, if the rate upsizing fails, the target rate is the greater
one of the candidate target rate and the pre-upsizing DCCC rate.
381
IAC - Preemption
After CAC fails, the RNC performs preemption firstly
Precondition of preemption and queuing:

According to RAB ASSIGNMENT REQUEST message,

preemption and queuing are supported
The related algorithm switches are set to ON
Page127
Preemption and queuing guarantee the success in the access of a higher-priority user by
forcibly releasing the resources of a lower-priority user.
Preemption and queuing are applicable to the following scenarios:

Setup or modification of a service

Hard handover or SRNS relocation

UE state transition from CELL_FACH to CELL_DCH
382
The following table describes the selection of the target cell for preemption or queuing.
The following table describes the preemption for different types of service on different resources.
383
Preemption Procedure
Sorts the preemptable users by user integrated priority, or sorts the

preemptable RABs by RAB integrated priority
Only the users or RABs with priorities lower than the RAB to be
established are selected
Selects as many users or RABs as necessary in order to match the

resource needed by the RAB to be established
When the priorities of two users or RABs are the same, the algorithm
selects the user or RAB that can release the most resources
The RNC releases the resources occupied by the candidate users or

RABs
The requested service directly uses the released resources to access

the network without admission decision
Page129

PreemptAlgoSwitch
Parameter name: Preempt algorithm switch
384
Page130
PreemptAlgoSwitch

Content: Indicating whether preemption is supported.

Set this parameter through SET UQUEUEPREEMPT.
IAC - Queuing
After preemption fails, UE can be put into the queue,

then admission attempts are made periodically till
maximum queuing time
The queuing function is triggered by the heartbeat timer

that equals 500 ms. Each time the timer expires, the RNC
selects the service that meets the requirement to make
an admission attempt
385
Page131
The queuing function takes the following actions:

The queuing algorithm checks whether the queue is full, that is, whether the number of
service requests in the queue exceeds the queue length, which equals 5.
The queuing algorithm decides whether to put the request into the queue, as described
in the following table.
After the heartbeat timer expires, the queuing algorithm performs resource-based
admission attempts as follows:

Rejects the request if the queuing time of the request, Telapsed, is longer than
the maximum queuing time (MaxQueueTimeLen). Here, Telapsed is equal to the
current time minus the request time (T_request).

Selects the request with the highest integrated priority for a resource-based
admission attempt.

If more than one service has the highest integrated priority, the RNC selects the
request with the longest queuing time for a power-based admission attempt.

If the attempt is successful, the heartbeat timer is restarted for the next
processing.

If the attempt fails, the queuing algorithm proceeds as follows:

Puts the service request back into the queue with the request time
(T_request) unchanged for the next attempt.

Selects the request with the longest queuing time from the rest and makes
another attempt until a request is accepted or all requests are rejected.
386

QueueAlgoSwitch
Parameter name: Queue algorithm switch
MaxQueueTimeLen
Parameter name: Max queuing time length
Page133
QueueAlgoSwitch

Content: Indicating whether queue is supported. When a user initiates a call, if

cell resources are insufficient and the user is queue supportive, the RNC tries to
arrange this user to join the queue to increase access success ratio.
MaxQueueTimeLen
Content: Maximum queue time of users. When a user initiates a call, it joins the
queue due to cell resource insufficiency. This parameter defines the maximum
length of time required for queuing of a user. If cell resources are still insufficient
after expiration, access fails.

Value range: 1~60


Physical unit: s
Set these parameters through SET UQUEUEPREEMPT.
387
IAC - Low-Rate Access of the PS BE

Service
Low-rate access means access from the DCH at 0 kbit/s,

FACH, or enhanced FACH (E-FACH)
Low-rate access is used in the following scenarios:

RAB setup
Hard handover or relocation
Page134
If the PS_BE_EXTRA_LOW_RATE_ACCESS_SWITCH subparameter of the PsSwitch

parameter is set to 1, the PS BE service can access the target cell at a low rate in the
case of a preemption or queuing failure to increase the access success rate.
After an appropriate access action is determined, the service attempts to access the
network.

If the action of access from the DCH at 0 kbit/s is determined, the service
attempts to access the network at 0 kbit/s for traffic and at the normal rate for
signaling.

If the action of access from the FACH/E-FACH is determined, the service attempts
to access the network from the FACH/E-FACH.

If the attempt fails, this service is rejected.
For the service that accesses the network at 0 kbit/s, the ZeroRateUpFailToRelTimerLen
timer is started after the service rate fails to increase for the first time. If the rate fails to
increase even when the timer expires, the service is released, and the connection is also
released for a single service.
388

PsSwitch-PS_BE_EXTRA_LOW_RATE_ACCESS_SWITCH
Parameter name: PS rate negotiation switch for low rate

access
ZeroRateUpFailToRelTimerLen
Parameter name: Release 0 kbit/s Timer length for failed to

rate up
PsSwitch-PS_BE_EXTRA_LOW_RATE_ACCESS_SWITCH

Page135
Content: When the switch is on, access at a rate of 0 kbit/s or on the FACH is
determined according to the current connection state of the RRC if the PS BE
admission and the later preemption and queuing fail.
ZeroRateUpFailToRelTimerLen

Content: For the PS BE service at a rate of 0 kbit/s, this parameter is used for the
rate upsizing for DCCC triggered by event 4A. Unsuccessful rate upsizing indicates
that the resources are insufficient in the cell. The service may run at a rate of 0
kbit/s for a long time. If the timer is started, the 0 kbit/s service of the UE is
released after the timer expires. If the length is set to 0, the timer is not started.
Physical unit: s
Set this parameter through SET UCOIFTIMER.
389
IAC for Emergency Calls

RRC connection setup process of emergency calls:

No admission on power resource
Admission is successful if the current remaining hard

resources are sufficient
If the hard resource admission fails preemption is

performed regardless of the preemption switch
Page136
Compared with the RRC connection setup process of ordinary services, the RRC
connection setup process of emergency calls incorporates the preemption due to hard
resource-based admission failure. Hard resources include code, Iub, and CE resources.
To guarantee a successful admission of an emergency call, the RNC does not perform
RRC redirection for service steering.
In the case of power-based admission, the emergency call is admitted regardless of
whether the CAC function is enabled or not.
In the case of hard resource-based admission, the emergency call is admitted if the
current remaining resources are sufficient for RRC connection setup. If the admission
fails, preemption is performed regardless of whether the preemption is enabled or not.
The emergency call that triggers preemption has the highest priority. The range of users
that can be preempted is specified by the EmcPreeRefVulnSwitch parameter.

If EmcPreeRefVulnSwitch is set to ON, all non-emergency users that have
accessed the network can be preempted, regardless of the preemption-prohibited
attribute of the users.

If EmcPreeRefVulnSwitch is set to OFF, only the non-emergency users with
preemption-allowed attribute can be preempted.

The principles for selection of specific users to be preempted are the same as
those for ordinary services.
390
IAC for Emergency Calls (Cont.)

RAB process of emergency calls:

For power resource admission:

When EMC_UU_ADCTRL is on, power admission fails if the

system is in overload. Otherwise, the admission succeeds
If the CAC algorithm switch is off, the emergency calls are directly
admitted
Admission is successful if the current remaining hard

resources are sufficient
If the hard resource admission fails preemption is

performed regardless of the preemption switch
Page137
Compared with the RAB process of ordinary services, the RAB process of emergency
calls incorporates special processing of resource-based admission and preemption.
RAB admission of emergency calls:

In case of power resources:

If the CAC function is enabled, regardless of which algorithm is selected,
the admission decision-making is as follows:
When the EMC_UU_ADCTRL subparameter of the
NBMCacAlgoSwitch parameter is set to 1, power-based admission
fails if the system is in the overload congestion state. Otherwise,
the admission succeeds.
When this subparameter is set to 0, the emergency calls are
directly admitted.

If the CAC function switch is off, the emergency calls are directly admitted.

For hard resources (that is, code, Iub, and CE), the resource-based admission is
successful if the current remaining resources are sufficient for the request.
Preemption of emergency calls:

If cell resource-based admission fails, preemption is performed regardless of
whether the preempt function is enabled or not. The emergency calls that trigger
preemption have the highest priority. The range of users that can be preempted
is specified by the EmcPreeRefVulnSwitch parameter.
391

EmcPreeRefVulnSwitch
Parameter name: Preemptvulnerability for Emergency call

switch
NBMCacAlgoSwitch-EMC_UU_ADCTRL
Parameter name: Cell CAC algorithm switch for UU resource

of emergency call
EmcPreeRefVulnSwitch

Page138
Content: When the switch is enabled, users of emergency call can preempt all the
users of non emergency call. When the switch is disabled, users of emergency call
can only preempt users of non emergency call with the preempted attributes.
Set this parameter through SET UQUEUEPREEMPT.
NBMCacAlgoSwitch-EMC_UU_ADCTRL

Content: Control power admission for emergency user.

392
LDR (Load Reshuffling)
Load
LCC (Load Congestion Control)

100%
Overload state: OLC
section A
THOLC
section B
THLDR
Basic congestion state: LDR
section C
Normal state
Page140
LCC (Load Congestion Control) consist of LDR (Load Reshuffling) and OLC (Over Load
Control).
In basic congestion state, LDR will be used to optimize resource distribution, the main
rules is not to affect the feeling of users as possible as we can.
In overload state, OLC will be used to release overload state quickly, keep system
stability and the service of high priority users.
393
LDR Principle
Reason:
When the cell is in basic congestion state, new coming calls

could be easily rejected by system
Purpose:
Optimizing cell resource distribution
Decreasing load level, increasing admission successful rate
Triggering:
Power, code, Iub or NodeB credit
Page141
When the usage of cell resource exceeds the basic congestion triggering threshold, the
cell enters the basic congestion state. In this case, Load Reshuffling (LDR) is required to
reduce the cell load and increase the access success rate.
The basic congestion of a cell can be caused by power resource, code resource, Iub
resource, or NodeB credit resource. For power resource, the RNC performs periodic
measurement and checks whether the cells are congested. For code, Iub, and NodeB
credit resources, the RNC checks whether the cells are congested when resource usage
changes.
394
LDR Triggering - Power Resource
Page142
Congestion control based on power resource can be enabled through the DL_UU_LDR
and UL_UU_LDR subparameters of the NBMLdcAlgoSwitch parameter.
The above figure shows the triggering and relieving of basic congestion:

For an R99 cell:

If the current UL/DL load of the R99 cell is higher than or equal to the
UL/DL LDR trigger threshold (UlLdrTrigThd or DlLdrTrigThd) for 1,000 ms,
the cell is in the basic congestion state, and the related load reshuffling
actions are taken.

If the current UL/DL load of the R99 cell is lower than the UL/DL LDR relief
threshold (UlLdrRelThd or DlLdrRelThd) for 1,000 ms, the cell enters the
normal state again.

For an HSPA cell:

In the uplink, the basic congestion decision is based on the comparison
between the UL LDR trigger threshold (UlLdrTrigThd) and the
uncontrollable load of the cell.

In the downlink, the basic congestion decision is based on the comparison
between the DL LDR trigger threshold (DlLdrTrigThd) and the sum of the
non-HSPA power and the GBP.
395
Parameters of LDR
NBMLdcAlgoSwitch-UL_UU_LDR/DL_UU_LDR
Parameter name: Cell LDC algorithm switch for LDR
Recommended value: OFF, OFF
UlLdrTrigThd/DlLdrTrigThd
Parameter name: UL/DL LDR trigger threshold
Recommended value: 55%, 70%
UlLdrRelThd/DlLdrRelThd
Parameter name: UL/DL LDR release threshold
NBMLdcAlgoSwitch-UL_UU_LDR/DL_UU_LDR

Content: UL/DL UU load reshuffling algorithm. When the cell is heavily loaded in UL/DL, this
algorithm reduces the cell load in UL/DL by using inter-frequency load handover, BE service rate
reduction, uncontrollable real-time service QoS renegotiation and inter-RAT handover as well.
UlLdrTrigThd/DlLdrTrigThd

Page143
Content: If the ratio of UL/DL load of the cell to the uplink/downlink capacity is not lower than this
threshold, the UL/DL load reshuffling function of the cell is triggered. After the basic congestion
state of the cell load is released, the system no longer implements the LDR action. Because the load
fluctuates, the difference between the LDR release threshold and trigger threshold should be higher
than 10%. The lower the LDR trigger and release thresholds are, the easier the system enters the
preliminary congestion status, the harder it is released from this status, the easier the LDR action is
triggered, and the more likely the users are affected. But, the admission success rate becomes
higher since the resources are preserved.
Value range: 0~100
Physical unit: %
Set these parameters through ADD UCELLLDM/ MOD UCELLLDM.
UlLdrRelThd/DlLdrRelThd

Content: If the ratio of UL/DL load of the cell to the uplink capacity is lower than this threshold, the
UL/DL load reshuffling function of the cell is stopped.
Value range: 0~100
Physical unit: %
396
LDR Triggering - Code Resource

Congestion control based on code resource can be

enabled through the CELL_CODE_LDR subparameter of
the NBMLdcAlgoSwitch parameter
If the SF corresponding to the current remaining code of

the cell is larger than the value of CellLdrSfResThd, code
congestion is triggered and the related load reshuffling
actions are taken
Page144
Parameters of LDR (Cont.)

NBMLdcAlgoSwitch-CELL_CODE_LDR
Parameter name: Cell LDC algorithm switch for LDR
CellLdrSfResThd
Parameter name: Cell LDR SF reserved threshold
397
Page145
NBMLdcAlgoSwitch-CELL_CODE_LDR

Content: Code reshuffling algorithm. When the cell CODE is heavily loaded, this
algorithm reduces the cell CODE load by using BE service rate reduction and code
tree reshuffling.
CellLdrSfResThd

Content: Cell SF reserved threshold. The code load reshuffling could be triggered
only when the minimum available SF of a cell is higher than this threshold. The
lower the code resource LDR trigger threshold is, the easier the downlink code
resource enters the initial congestion status, the easier the LDR action is triggered,
and the easier the subscriber perception is affected. But a lower code resource
LDR trigger threshold causes a higher admission success rate because the
resource is reserved.
Value range: SF4(SF4), SF8(SF8), SF16(SF16), SF32(SF32), SF64(SF64),
SF128(SF128), SF256(SF256)
Physical value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256
Set this parameter through ADD UCELLLDR/ MOD UCELLLDR.
LDR Triggering - Iub Resource

Congestion control based on Iub resource can be enabled

through the IUB_LDR subparameter of the
NodeBLdcAlgoSwitch parameter
Iub congestion control in both the uplink and downlink is

NodeB-oriented. So for the basic congestion caused by
Iub resource, all UEs under the NodeB are the objects of
related LDR actions
Page146
For a path, the following congestion-related parameters are applicable:

Congestion detection parameters:
FWDCONGBW
398

BWDCONGBW
The default values of the two parameters are 0, which indicates that no
congestion detection will be performed. If the parameters are set to values other
than 0, TRM performs congestion detection according to the settings.
Congestion resolving parameters:
FWDCONGCLRBW
BWDCONGCLRBW

These two parameters are used to determine whether the congestion is resolved.
Assume that the forward parameters of a port for congestion detection are defined as
follows:

Configured bandwidth: AVE

Forward congestion threshold: CON

Forward congestion resolving threshold: CLEAR (Note that CLEAR is greater than
CON.)

Used bandwidth: USED
Then, the mechanism of congestion detection for the port is as follows:

Congestion occurs on the port when CON + USED AVE.

Congestion disappears from the port when CLEAR + USED < AVE.

NodeBLdcAlgoSwitch-IUB_LDR
Parameter name: NodeB LDC algorithm switch for LDR
Page147
NodeBLdcAlgoSwitch-IUB_LDR

Content: When the NodeB Iub load is heavy, users are assembled in priority order
among all the NodeBs and some users are selected for LDR action (such as BE
service rate reduction) in order to reduce the NodeB Iub load.
399
LDR Triggering NodeB Credit

Resource
The basic congestion caused by NodeB credit resource is

of the following types:
Type A: Basic congestion at local cell level
Type B: Basic congestion at local cell group level (if any)
Type C: Basic congestion at NodeB level
Page148
The switches of NodeB credit LDR:
The threshold of NodeB credit LDR:

Type A: If the cell UL/DL current remaining SF (mapped to credit resource) is
higher than UlLdrCreditSfResThd or DlLdrCreditSfResThd (set through the ADD
UCELLLDR command), credit congestion at cell level is triggered and related load
reshuffling actions are taken in the current cell.

Type B and C: If the cell group or NodeB UL/DL current remaining SF (mapped to
credit resource ) is higher than UlLdrCreditSfResThd or DlLdrCreditSfResThd (set
through the ADD UNODEBLDR command), credit congestion at cell group or
NodeB level is triggered and related load reshuffling actions are taken. The range
of LDR actions is the same as the first type, but the range of UEs to be sorted by
priority is different. All the UEs in the normal cells that belong to the cell group or
NodeB will be sorted.
400

Parameter
Type A:
CELL_CREDIT_LDR
Type A:
UlLdrCreditSfResThd
Type A:
DlLdrCreditSfResThd
Parameter name
Cell LDC algorithm switch for LDR
OFF
UL LDR credit SF reserved threshold
SF8
DL LDR credit SF reserved threshold
SF8
Type B:
NodeB LDC algorithm switch for
LCG_CREDIT_LDR
LDR
Type C:
NodeB LDC algorithm switch for
NODEB_CREDIT_LDR
LDR
Type B/C:
UlLdrCreditSfResThd
Type B/C:
DlLdrCreditSfResThd
OFF
OFF
UL LDR credit SF reserved threshold
SF8
DL LDR credit SF reserved threshold
SF8
Recommended value
Page149
Type A: CELL_CREDIT_LDR

Type A: UlLdrCreditSfResThd/DlLdrCreditSfResThd

Set these parameters through ADD UCELLLDR/ MOD UCELLLDR.
Type B/C: LCG_CREDIT_LDR/NODEB_CREDIT_LDR

Set these parameters through ADD UNODEBALGOPARA/ MOD
UNODEBALGOPARA.
Type B/C: UlLdrCreditSfResThd/DlLdrCreditSfResThd

Set these parameters through ADD UNODEBLDR/ MOD UNODEBLDR.
401

If the congestion of all resources is triggered in a cell, the

congestion is relieved in order of resource priority for load
reshuffling as configured through the SET ULDCALGOPARA
command
Recommended setting is as follows:
The first priority for load reshuffling (LdrFirstPri) is set to IUBLDR

The second priority for load reshuffling (LdrSecondPri) is set to
CREDITLDR
The third priority for load reshuffling (LdrThirdPri) is set to
CODELDR
The fourth priority for load reshuffling (LdrFourthPri) is set to
UULDR
Page150
LdrFirstPri/LdrSecondPri/LdrThirdPri/LdrFourthPri

Content: If congestion is triggered by multiple resources such as credit and code

at the same time, the congestion of resources specified in this parameter is
processed with the first priority. IUBLDR refers to processing of LDR action
trigged by Iub bandwidth. CREDITLDR refers to processing of LDR action trigged
by credit. CODELDR refers to processing of LDR action trigged by code. UULDR
refers to processing of LDR action trigged by Uu.
Value range: IUBLDR(Iub load reshuffling), CODELDR(Code load reshuffling),
UULDR(Uu load reshuffling), CREDITLDR(Credit load reshuffling)
Physical value range: IUBLDR, CODELDR, UULDR, CREDITLDR
Set these parameters through SET ULDCALGOPARA.
402
LDR Procedure
The RNC periodically takes actions if the basic congestion is

detected:
Inter-frequency load handover
Code reshuffling
BE service rate reduction
AMR rate reduction
Inter-RAT load handover in the CS domain
Inter-RAT load handover in the PS domain
Iu QoS renegotiation
MBMS power reduction
Page151
The sequence of LDR actions can be changed through the ADD UCELLLDR command, and
the waiting timer for LDR period is specified by the LdrPeriodTimerLen parameter
through the SET ULDCPERIOD command.
Whether the users of gold priority are selected by LDR actions is specified by the
GoldUserLoadControlSwitch parameter.
403
LDR procedure:
404
As shown in the previous figure, when the system is congested, the inter-frequency load
handover is initiated first.

If the handover succeeds, the algorithm continues to check whether the system is
congested. If the system is still congested, the inter-frequency load handover is initiated
again.

If the handover fails, code reshuffling is performed.

If the code reshuffling succeeds, the algorithm continues to check whether the system is
congested. If the system is still congested, the code reshuffling is initiated again.

If the code reshuffling fails, the next action, that is, BE rate reduction, is taken.

The rest may be deduced by analogy.
LDR actions intended for different resources:
405
If the downlink power-based admission uses the ENU algorithm, the basic congestion
can also be caused by the ENU. In this situation, LDR actions do not involve AMR rate
reduction or MBMS power reduction, as indicated by the symbol "*" in the previous
table.
For HSUPA services, the CE consumption, which is calculated on the basis of the
Maximum Bit Rate (MBR), can be reduced through rate downsizing. Therefore, the BE
service rate downsizing for HSUPA is applicable only to the relief of CE resource
congestion.
If the basic congestion of uplink power in an HSPA cell occurs, scheduled HSUPA users
cannot be selected by LDR actions.
The parameter CodeCongSelInterFreqHoInd can be set so that the inter-frequency
handover can relieve the basic congestion caused by code resource.

LdrPeriodTimerLen
Parameter name: LDR period timer length
GoldUserLoadControlSwitch
Parameter name: Gold user load control switch
Page154
LdrPeriodTimerLen
Content: Identifying the period of the LDR execution. When basic congestion
occurs, execution of LDR can dynamically reduce the cell load. The lower the
parameter value is, the more frequently the LDR action is executed, which
406

decreases the load quickly. If the parameter value is excessively low, an LDR
action may overlap the previous one before the previous result is displayed in
LDM. The higher the parameter value is, the more likely this problem can be
prevented. If the parameter value is excessively high, the LDR action may be
executed rarely, failing to lower the load timely.
Physical unit: s
GoldUserLoadControlSwitch

Content: Indicates whether gold users involve in the switch of congestion control.
According to the policy set for gold users by operators, if service quality of gold
users should be guaranteed even in resource congestion, the switch should be
disabled. If the switch is enabled, LDR such as rate reduction and handover also
occurs on gold users even in cell resource congestion, which impacts user service
quality. If the switch is disabled, no action is performed on gold users.

DlLdrFirstAction to DlLdrTenthAction
Parameter name: DL LDR first action to DL LDR tenth action
Recommended value: CodeAdj, InterFreqLDHO, BERateRed
UlLdrFirstAction to UlLdrEighthAction
Parameter name: UL LDR first action to UL LDR eighth

action
Recommended value: InterFreqLDHO, BERateRed
Page155
DlLdrFirstAction to DlLdrTenthAction

Content: Downlink LDR actions.

Value range: NoAct(no action), InterFreqLDHO(inter-freq load handover),
BERateRed(BE traff rate reduction), QoSRenego(uncontrolled real-time traff Qos
re-negotiation), CSInterRatShouldBeLDHO(CS domain inter-rat should be load
407
handover), PSInterRatShouldBeLDHO(PS domain inter-rat should be load

handover), AMRRateRed(AMR traff rate reduction), MBMSDecPower(MBMS
descend power), CodeAdj(Code adjust), CSInterRatShouldNotLDHO(CS domain
inter-rat should not be load handover), PSInterRatShouldNotLDHO(PS domain
inter-rat should not be load handover)
UlLdrFirstAction to UlLdrEighthAction

Content: Uplink LDR actions.

Value range: NoAct(no action), InterFreqLDHO(inter-freq load handover),
BERateRed(BE traff rate reduction), QoSRenego(uncontrolled real-time traff Qos
re-negotiation), CSInterRatShouldBeLDHO(CS domain inter-rat should be load
handover), PSInterRatShouldBeLDHO(PS domain inter-rat should be load
handover), AMRRateRed(AMR traff rate reduction), CSInterRatShouldNotLDHO(CS
domain inter-rat should not be load handover), PSInterRatShouldNotLDHO(PS
domain inter-rat should not be load handover)
LDR Actions - Inter-Frequency Load

Handover
Target cell:
Supporting inter-frequency blind handover
The current load is normal:

Power reason:
UlInterFreqHoCellLoadSpaceThd/DlInterFreqHoCellLoadSpaceThd
Code reason: LdrCodeUsedSpaceThd
Target user:
The UE with the lowest integrated priority
User selection algorithm switch:

NbmLdcBHOUeSelSwitch
Page156
The inter-frequency LDRalgorithm performs the following steps:

The algorithm checks whether cells for inter-frequency blind handover are available. If
available, the algorithm goes to the next step. Otherwise, the action fails, and the
algorithm takes the next action.
The algorithm selects the target cell according to the type of resource that causes the
basic congestion:

If the basic congestion is caused by power resource:
408
The algorithm checks whether the load margin of the target cell is higher than
both UlInterFreqHoCellLoadSpaceThd and DlInterFreqHoCellLoadSpaceThd and
whether the load of the target cell is normal.
If the margin is not higher than the threshold, the action fails, and the algorithm
takes the next action. If there is more than one cell meeting the requirements,
the first one is selected as the blind handover target cell.
The load margin refers to the difference between the load of the target cell and
the basic congestion triggering threshold of the target cell, but not the difference
between the load of the target cell and the load of the current cell.
If the basic congestion is caused by code resource:
Whether there are blind handover target cells meeting the requirements is
decided by the following conditions:
a. The minimum SF of the target cell is not greater than that of the current cell.
b. The difference of code usage between the current cell and the target cell is
greater than LdrCodeUsedSpaceThd.
c. The state of target cell is normal.
If there is no such cell, this action fails and the algorithm takes the next action. If
there is more than one cell meeting the requirements, the first cell is selected as
the blind handover target cell.
The algorithm selects the UEs to be handed over according to the setting of
NbmLdcBHOUeSelSwitch:

If NbmLdcBHOUeSelSwitch is set to NBM_LDC_MATCH_UE_ONLY, the algorithm
performs the following steps:
a. Selects the UEs whose service types are supported by the target cell as
candidate UEs.
b. Sorts the candidate UEs whose rates are not higher than the handover
bandwidth thresholds, based on the integrated priority.
c. Selects the UE with the lowest integrated priority for handover.

If NbmLdcBHOUeSelSwitch is set to NBM_LDC_MATCH_UE_FIRST, the algorithm
performs the following steps:
a. Selects the UEs whose service types are supported by the target cell as
candidate UEs.
b. Sorts the candidate UEs whose rates are not higher than the handover
bandwidth thresholds, based on the integrated priority.
If the rates of all the candidate UEs are higher than the handover bandwidth
thresholds, the algorithm performs the following steps:
a. Selects the UEs whose service types are not supported by the target cells as
candidate UEs.
b. Sorts the UEs whose rates are not higher than the handover bandwidth
threshold, based on the integrated priority.

If NbmLdcBHOUeSelSwitch is set to NBM_LDC_ALL_UE, the algorithm performs
the following steps:
a. From the current cell, selects the UEs whose rates are not higher than the
handover bandwidth thresholds, and then sorts them by integrated priority.
409
b. Selects the UE with the lowest integrated priority for handover.

If multiple UEs have the same lowest integrated priority, the algorithm selects
the one with the lowest rate for handover.

The UL and DL handover bandwidth thresholds are specified by
UlInterFreqHoBWThd and DlInterFreqHoBWThd respectively. Both the thresholds
are considered in the selection of the target UE.
After selecting the target cell and the UE, the algorithm takes handover actions
according to the status of the UE and the measurement of the signal quality.

UlInterFreqHoCellLoadSpaceThd/DlInterFreqHoCellLoadS
paceThd
Parameter name: UL/DL HO load space threshold
LdrCodeUsedSpaceThd
Parameter name: InterFreq HO code used ratio space

threshold
UlInterFreqHoCellLoadSpaceThd/DlInterFreqHoCellLoadSpaceThd

Page158
Content: The inter-frequency neighboring cell could be selected as the destination

of load handover only when its load remaining space is larger than this threshold.
The lower the parameter is, the easier it is to find a qualified target cell for the
blind handover. Excessively small value of the parameter, however makes the
target cell easily enter the congestion status. The higher the parameter is, the
more difficult it is for the inter-frequency blind handover occurs.
Value range: 0~100
Physical unit: %
LdrCodeUsedSpaceThd
Content: Code resource usage difference threshold. Inter-frequency handover is

triggered when the difference of the resource usage of the current cell and that
of the target cell is greater than this threshold. The smaller this parameter value,
410
the easier it is to find the qualified target cell for blind handover. Excessively
small values of the parameter, however makes the target cell easily enters the
congestion status. The higher the parameter value, the more difficult it is for the
inter-frequency blind handover occurs, and the easier it is to guarantee the
stability of the target cell.

Value range: 0~100


Physical unit: %

Parameter name: BHO Select User algorithm switch
Recommended value: NBM_LDC_MATCH_UE_ONLY
UlInterFreqHoBWThd/DlInterFreqHoBWThd
Parameter name: UL/DL HO maximum bandwidth
Recommended value: 200000bit/s, 200000bit/s
Page159
Content: NBM_LDC_ALL_UE: When inter-frequency blind handover select user occurs, no

need to consider whether target cell support users. NBM_LDC_MATCH_UE_ONLY: When
inter-frequency blind handover select user occurs, only consider users supported by target
cell. NBM_LDC_MATCH_UE_FIRST: When inter-frequency blind handover select user
occurs, first consider users supported by target cell.
Value range: NBM_LDC_ALL_UE(Select all users), NBM_LDC_MATCH_UE_ONLY(Select
users match target cell support only), NBM_LDC_MATCH_UE_FIRST(Select users match
target cell support first)
Physical value range: NBM_LDC_ALL_UE, NBM_LDC_MATCH_UE_ONLY,
NBM_LDC_MATCH_UE_FIRST
UlInterFreqHoBWThd/DlInterFreqHoBWThd
Content: The UE can be selected to process load handover only when its bandwidth is less
than this threshold. The higher the parameter is, the higher the service rate of the user in
handover is, and the more obviously the cell load is decreased. However, high value of the
411

parameter gives rise to the fluctuation and congestion of the target cell load. The lower
the parameter is, the smaller amplitude of the load decreases as a result of the interfrequency load handover, and the easier it is to maintain the stability of the target cell
load.
Physical unit: bit/s
LDR Actions - BE Rate Reduction

Target RAB:
The RAB with the lowest integrated priority
The current rate is higher than GBR
Number:
UlLdrBERateReductionRabNum/DlLdrBERateReductionRabNum
The RNC sends a RADIO BEARER RECONFIGURATION

message to the UE
Page160
The BE rate reduction function is controlled by the DCCC algorithm switch. BE rate
reduction can only be performed when the DCCC algorithm is enabled.
Different from the TF restriction to the OLC function, the BE rate reduction is
implemented by bandwidth reconfiguration. The bandwidth reconfiguration requires
signaling interaction on the Uu interface. This procedure is relatively long.
In the same environment, different rates have different downlink transmit powers. The
higher the rate, the greater the downlink transmit power. Therefore, the load can be
reduced by bandwidth reconfiguration.
For HSUPA services, the consumption of CEs is based on the bit rate. The higher the rate,
the more the consumption of CEs. Therefore, the consumption of CEs can be reduced by
bandwidth reconfiguration.
The LDR algorithm operates as follows:

Based on the integrated priority, the algorithm sorts the RABs in descending
order.
412
The algorithm selects the RABs with the lowest integrated priorities and with the
current rate higher than the GBR specified through the SET UUSERGBR command
for related to the BE services. If the integrated priorities of some RABs are
identical, the RAB with the highest rate is selected. The number of selected RABs
is specified by the UlLdrBERateReductionRabNum or
DlLdrBERateReductionRabNum parameter.
If services can be selected, the action is successful. If services cannot be selected,
the action fails. The algorithm takes the next action.
The reconfiguration is completed as indicated by the RADIO BEARER
RECONFIGURATION message on the Uu interface and through the synchronized
radio link reconfiguration procedure on the Iub interface.

UlLdrBERateReductionRabNum/DlLdrBERateReductionRa
bNum
Parameter name: UL/DL LDR-BE rate reduction RAB number
Page161
UlLdrBERateReductionRabNum/DlLdrBERateReductionRabNum

Content: Number of RABs selected in a UL/DL LDR BE traffic rate reduction. In the
actual system, this parameter can be set on the basis of the actual circumstances.
If the high-rate subscribers occupy a high proportion, set the parameter to a
comparatively low value. If the high-rate subscribers occupy a low proportion, set
the parameter to a comparatively high value. Because the basic congestion
control algorithm is designed to slowly decrease cell load, you need to set this
parameter to a comparatively low value.
Value range: 1~10
413
LDR Actions - QoS Renegotiation

QoS renegotiation function switch:

DRA_IU_QOS_RENEG_SWITCH
Target RAB:
Number:
UlLdrPsRTQosRenegRabNum/DlLdrPsRTQosRenegRabNum
The RNC sends a RAB MODIFY REQUEST message to the

CN

Page162
Uncontrollable real-time services refer to PS streaming services.

The QoS renegotiation function for uncontrollable real-time services is set by the
DRA_IU_QOS_RENEG_SWITCH subparameter of the DraSwitch parameter.
The load can be reduced by adjusting the rates of real-time services through QoS
renegotiation. In 3GPP R5, the RNC initiates the RAB renegotiation procedure through
the RAB MODIFY REQUEST message on the Iu interface. Upon reception of the RAB
MODIFY REQUEST message, the Core Network (CN) sends the RAB ASSIGNMENT
REQUEST message to the RNC for RAB parameter reconfiguration. Based on this function,
the RNC can adjust the rate of real-time services to reduce the load of the current cell.
The LDR algorithm operates as follows:

Based on the integrated priority, the algorithm sorts the RABs for real-time
services in the PS domain in descending order.

The algorithm selects the RABs with the lowest integrated priorities for QoS
renegotiation. The number of selected RABs is specified by the
UlLdrPsRTQosRenegRabNum or DlLdrPsRTQosRenegRabNum parameter.

The algorithm performs QoS renegotiation for the selected services. The GBR
during the service setup is the minimum rate of the service after the QoS
renegotiation.

The RNC initiates the RAB MODIFY REQUEST message to the CN for the QoS
renegotiation.

If the RNC cannot find an appropriate service for the QoS renegotiation, the
action fails. The algorithm takes the next action.
414

DraSwitch-DRA_IU_QOS_RENEG_SWITCH
Parameter name: Dynamic resource allocation switch for IU

QoS RENEQ
UlLdrPsRTQosRenegRabNum/DlLdrPsRTQosRenegRabNu
m
Parameter name: UL/DL LDR un-ctrl RT Qos re-nego RAB

num
DraSwitch-DRA_IU_QOS_RENEG_SWITCH

Page163
Content: When the switch is on and the Iu QoS RENEQ license is activated, the
RNC supports renegotiation of the maximum rate if the QoS of real-time services
is not ensured according to the cell status.
UlLdrPsRTQosRenegRabNum/DlLdrPsRTQosRenegRabNum

Content: Number of RABs selected in a UL/DL LDR uncontrolled real-time traffic

QoS renegotiation. The target subscribers of this parameter are the PS domain
real-time subscribers. The setting of this parameter is analogous to the setting of
BE service rate reduction subscriber number. Because the number of subscribers
performing QoS renegotiation may be smaller than the value of this parameter,
for example, the candidate subscribers selected for downlink LDR do not meet
the QoS renegotiation conditions, you must leave some margin when setting this
parameter to ensure the success of load reshuffling.
Value range: 1~10
415
LDR Actions - Inter-RAT Handover

Target user:
The user with the lowest integrated priority

GSM cell
WCDMA cell
Page164
Inter-RAT handover in the CS/PS domain involves the following actions:

Inter-RAT Should Be Load Handover in the CS/PS domain:

Based on the integrated priority, the algorithm sorts the UEs with the "service
handover" IE set to "handover to GSM should be performed" in the CS/PS domain
in descending order.

The algorithm selects the UEs with the lowest integrated priorities. The number
of selected UEs is specified by the UlCSInterRatShouldBeHOUeNum or
DlCSInterRatShouldBeHOUeNum parameter for CS domain, and
UlPSInterRatShouldBeHOUeNum or DlPSInterRatShouldBeHOUeNum parameter
for PS domain.

For the selected UEs, the LDR module sends the load handover command to the
inter-RAT handover module to ask the UEs to be handed over to the 2G system.

The handover module decides to trigger the inter-RAT handover, depending on
the capability of the UE to support the compressed mode.

If a UE that satisfies the handover criteria is not found, the algorithm takes the
next action.
Inter-RAT Should Not Be Load Handover in the CS/PS domain:

The algorithm for this action is the same as that for the action "Inter-RAT Should
Be Load Handover in the CS/PS Domain". The difference is that this action only
involves CS/PS users with the "service handover" IE set to "handover to GSM
should not be performed".

The number of selected UEs is specified by the UlCSInterRatShouldNotHOUeNum
or DlCSInterRatShouldNotHOUeNum parameter for CS domain, and
UlPSInterRatShouldNotHOUeNum or DlPSInterRatShouldNotHOUeNum parameter
for PS domain.
416

Parameter
Parameter name
UlCSInterRatShouldBeHOUeNum
UL CS should be HO user number
DlCSInterRatShouldBeHOUeNum
DL CS should be HO user number
UlCSInterRatShouldNotHOUeNum
UL CS should not be HO user

number
DlCSInterRatShouldNotHOUeNum
DL CS should not be HO user

number
UlPSInterRatShouldBeHOUeNum
UL PS should be HO user number
DlPSInterRatShouldBeHOUeNum
DL PS should be HO user number
UlPSInterRatShouldNotHOUeNum
UL PS should not be HO user

number
DlPSInterRatShouldNotHOUeNum
DL PS should not be HO user

number
Recommended
value
Page165
LDR Actions - AMR Rate Reduction

Target RAB:
Number:
In uplink:
UlLdrAMRRateReductionRabNum/DlLdrAMRRateReductionRabNum
The RNC sends the TFC CONTROL command to the UE
In downlink:
The RNC sends the Rate Control Request message through the Iu
interface to the CN
417
Page166
The action is restricted by the AMRC algorithm switch. This action can only be
performed when the AMRC algorithm is enabled.
The LDR algorithm operates in the uplink as follows:

order.

rates higher than the GBR for AMR services (conversational). The number of
selected RABs is determined by the UlLdrAMRRateReductionRabNum parameter.

The RNC sends the TFC CONTROL command to the UE to adjust the AMR rate to
the GBR.

If the RNC cannot find an appropriate RAB for the AMR rate reduction, the action
fails. The algorithm takes the next action.
The LDR algorithm operates in the downlink as follows:

order.

rates higher than the GBR for AMR services (conversational). The number of
selected RABs is specified by the DlLdrAMRRateReductionRabNum parameter.

The RNC sends the Rate Control Request message through the Iu interface to the
CN to adjust the AMR rate to the GBR.

If the RNC cannot find an appropriate RAB for the AMR rate reduction, the action
fails. The algorithm takes the next action.

UlLdrAMRRateReductionRabNum/DlLdrAMRRateReductio
nRabNum
Parameter name: UL/DL LDR-AMR rate reduction RAB

number
418
Page167
UlLdrAMRRateReductionRabNum/DlLdrAMRRateReductionRabNum

Content: This parameter defines the maximum number of RABs selected in

executing uplink/downlink LDR-AMR voice service rate reduction. If the parameter
value is too high, the LDR action may fluctuate greatly and over control may
occur (the state of basic congestion turns into another extreme--underload). If the
parameter value is too low, the LDR action has a slow response and the effect is
not apparent, affecting the LDR performance.
Value range: 1~10
LDR Actions - Code Reshuffling
Page168
The code reshuffling algorithm operates as follows:

Initializes SF_Cur to CellLdrSfResThd.

Traverses all the subtrees with this SF_Cur at the root node except the subtrees
occupied by common channels and HSDPA channels, and takes the subtrees in
which the number of users is not larger than the value of MaxUserNumCodeAdj
as candidates for code reshuffling.
If such candidates are available, the algorithm goes to step 3.
If no such candidate is available, subtree selection fails. This procedure ends.

Selects a subtree from the candidates according to the setting of
LdrCodePriUseInd.
419
If this parameter is set to TRUE, the algorithm selects the subtree with the largest
code number from the candidates.
If this parameter is set to FALSE, the algorithm selects the subtree with the
smallest number of users from the candidates. In the case that multiple subtrees
have the same number of users, the algorithm selects the subtree with the largest
code number.

Treats each user in the subtree as a new user and allocates code resources to
each user.

Initiates the reconfiguration procedure for each user in the subtree and
reconfigures the channelization codes of the users to the newly allocated code
resources. The reconfiguration procedure on the UU interface is implemented
through the PHYSICAL CHANNEL RECONFIGURATION message and that on the
Iub interface through the RL RECONFIGURATION message.
The above figure shows an example of code reshuffling. In this example,
CellLdrSfResThd is set to SF8, and MaxUserNumCodeAdj is set to 1.

CellLdrSfResThd
Parameter name: Cell LDR SF reserved threshold
MaxUserNumCodeAdj
Parameter name: Max user number of code adjust
LdrCodePriUseInd
Parameter name: LDR code priority indicator
Page169
CellLdrSfResThd
Content: Cell SF reserved threshold. The code load reshuffling could be triggered only
when the minimum available SF of a cell is higher than this threshold. The lower the code
resource LDR trigger threshold is, the easier the downlink code resource enters the initial
congestion status, the easier the LDR action is triggered, and the easier the subscriber
perception is affected. But a lower code resource LDR trigger threshold causes a higher
admission success rate because the resource is reserved.
Value range: SF4(SF4), SF8(SF8), SF16(SF16), SF32(SF32), SF64(SF64), SF128(SF128),
SF256(SF256)
420
Physical value range:SF4, SF8, SF16, SF32, SF64, SF128, SF256
MaxUserNumCodeAdj

Content: This parameter specifies the number of users selected in code reshuffling. Code
reshuffling can be triggered only when the number of users on a code is no greater than
the threshold. Code reshuffling has a big impact on the QoS. In addition, the reshuffled
subscribers occupy two code resources during code reshuffling. Thus, the parameter
should be set to a comparatively low value.
Value range: 1~3
LdrCodePriUseInd
Content: FALSE means not considering the code priority during the code reshuffling. TRUE
means considering the code priority during the code reshuffling. If the parameter is TRUE,
the codes with high priority are reserved during the code reshuffling.


LDR Actions - MBMS Power Reduction

Target RAB:
The ARP is higher than MbmsDecPowerRabThd
The RNC sends a COMMON TRANSPORT CHANNEL

RECONFIGURATION REQUEST message to NodeB

Page170
The downlink power load can be reduced by lowering power on MBMS traffic channels.
The algorithm operates as follows:

order.

The algorithm selects a RAB with the lowest integrated priority and with the
current power higher than the minimum transmit power of the corresponding
421
MTCH. That is, it selects a RAB of which the ARP value is higher than
MbmsDecPowerRabThd.
The algorithm triggers a reconfiguration procedure to set the power to the
minimum transmit power of the FACH onto which the MTCH is mapped.
The reconfiguration procedure on the Iub interface is implemented through the
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message.

MbmsDecPowerRabThd
Parameter name: MBMS descend power rab threshold
Page171
MbmsDecPowerRabThd

Content: When the priority of the RAB of MBMS services exceeds this threshold,
reconfigure the MBMS power to the minimum power. The lower the parameter
value is, the bigger the scope for selecting the MBMS services is, the more cell
load is decreased, the more effect there is on the MBMS service. At the same time,
the cell overload is significantly decreased while the impact on the MBMS services
becomes bigger. The higher the parameter value is, the smaller the scope for
selecting the MBMS services is, the less cell load is decreased, the more effect
there is on the MBMS services, and the quality of services with high priority,
however, can be guaranteed. The MBMS service at each rate is set on the basis of
two power levels. The power set for an MBMS service is determined according to
cell load during the service access. In addition, the FACH power of the MBMS
service must be decreased as required in the duration of cell congestion. Some
services with high priority, for example the disaster pre-alert, however, do not
need the coverage shrink caused by cell load. In such a case, you can adjust the
service priority threshold to protect the services with high priority against the
impact of the service access failure and the load control algorithm.
Value range: 1~15
422
OLC (Overload Control)
OLC Principle
Reason:
In overload congestion state, the system is not stable
Purpose:
Ensuring the system stability and making the system back to

the normal state as soon as possible
Triggering:
Power resource and interference
Page173
After the UE access is allowed, the power consumed by a single link is adjusted by the
single link power control function. The power varies with all kinds of factors such as the
mobility of the UE and the changes in the environment. In some situations, the total
power load of the cell can be higher than the target load. To ensure the system stability,
Overload Control (OLC) must be performed.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC subparameters of the
NBMLdcAlgoSwitch parameter.
423
OLC Load Judgment
Page174
The above figure shows the triggering and release of cell power overload:

If the current UL/DL load of an R99 cell is higher than or equal to the
UlOlcTrigThd or DlOlcTrigThd for 1,000 ms, the cell is in the overload state and
the related overload handling action is taken. If the current UL/DL load of the R99
cell is lower than the UlOlcRelThd or DlOlcRelThd for 1,000 ms, the cell comes
back to the normal state.

The overload triggering and release mechanisms for UL HSPA cells are the same
as those for R99 cells.

Whether a DL HSPA cell is overloaded is estimated according to the sum of the
non-HSPA power and the GBP.
424
Parameters of OLC
NBMLdcAlgoSwitch-UL_UU_OLC/DL_UU_OLC
Parameter name: Cell LDC algorithm switch for OLC
Recommended value: OFF, OFF
UlOlcTrigThd/DlOlcTrigThd
Parameter name: UL/DL OLC trigger threshold
UlOlcRelThd/DlOlcRelThd
Parameter name: UL/DL OLC release threshold
NBMLdcAlgoSwitch-UL_UU_OLC/DL_UU_OLC

Content: UL/DL UU overload congestion control algorithm. When the cell is overloaded in UL/DL,
this algorithm reduces the cell load in UL/DL by quick TF restriction or UE release.
UlOlcTrigThd/DlOlcTrigThd

Page175
Content: If the ratio of UL/DL load of the cell to the uplink/downlink capacity is not lower than this
threshold, the UL/DL overload and congestion control function of the cell is triggered. The lower the
OLC trigger threshold is, the easier the system is in the overload status. An excessively low value of
the OLC trigger threshold is very detrimental to the system performance. The lower the OLC release
threshold is, the harder the system releases the overload. The value of the OLC release threshold
should not be much lower than or close to the OLC trigger threshold, or the system state may have
a ping-pong effect. The recommended difference between the OLC release threshold and the OLC
trigger threshold is higher than 10%. It is desirable to set the two parameters a bit higher given
that the difference between OLC trigger threshold and OLC release threshold is fixed.
Value range: 0~100
Physical unit: %
UlOlcRelThd/DlOlcRelThd

Content: If the ratio of UL/DL load of the cell to the uplink/downlink capacity is lower than this
threshold, the UL/DL overload and congestion control function of the cell is stopped.
Value range: 0~100
Physical unit: %
425
OLC Procedure
Page176
When the cell is overloaded, the RNC takes one of the following actions in each period
specified by the OlcPeriodTimerLen parameter until the congestion is relieved:

Performing TF control of BE services

Switching BE services to common channels

Adjusting the maximum FACH TX power

Releasing some RABs
As shown in the previous figure, the OLC procedure is as follows:

When the system is overloaded, the OLC takes the first action to perform TF
control. If the TF control succeeds, the OLC checks whether the system is
overloaded. If yes, the OLC performs TF control again.
If the number of times that TF control is performed exceeds DlOlcFTFRstrctTimes
and the system is still overloaded, the OLC takes the next action to switch BE
services to common channels.

If the TF control fails, the OLC takes the second action to switch BE services to
common channels. If the switching succeeds, the OLC checks whether the system
is overloaded. If yes, the OLC switches BE services to common channels again.

If the switching fails, the OLC takes the third action to adjust the maximum FACH
transmit power. If the adjustment succeeds, the OLC checks whether the system
is overloaded. If yes, the OLC adjusts the power again.

If the adjustment fails, the OLC takes the fourth action to release some RABs.
426
Parameters of OLC (Cont.)

OlcPeriodTimerLen
Parameter name: OLC period timer length
Page177
OlcPeriodTimerLen

Content: :Identifying the period of the OLC execution. When overload occurs,
execution of OLC can dynamically reduce the cell load. When setting the
parameter, consider the hysteresis for which the load monitoring responds to the
load change. If the OLC period is excessively long, the system may respond very
slowly to overload. If the OLC period is excessively short, unnecessary adjustment
may occur before the previous OLC action has taken effect, and therefore the
system performance is affected.
Value range:100~86400000
Physical unit: ms
427
OLC Actions - Performing TF Control of

BE Services
OLC algorithm for TF control in the downlink:

Select RABs with the lowest integrated priority
The RNC sends the TF control indication message to the MAC
The MAC restricts the TFC selection: TFmax(N+1) = TFmax(N) x
Ratelimitcoeff
OLC algorithm for TF control in the uplink:

the RNC sends a TRANSPORT FORMAT COMBINATION CONTROL

message to the UE
The UE restricts the TFC selection
Page178
For the TF control in the downlink, the OLC algorithm operates as follows:
Based on the integrated priority, the algorithm sorts the RABs in descending order.
The algorithm selects the following RABs:

DCH RABs with the bit rates higher than DlDcccRateThd for BE services.

RABs with the lowest integrated priorities.
The number of RABs selected is smaller than or equal to DlOlcFTFRstrctRabNum.
The RNC sends the TF control indication message to the MAC. Each MAC of the selected
RABs will receive one TF control indication message and will restrict the TFC selection of
the BE services to reduce the data rate step by step.
The MAC restricts the TFC selection according to the following formula:

TFmax(N+1) = TFmax(N) x Ratelimitcoeff
Here:

TFmax(0) is the maximum TB number of the BE service before the service is
selected for TF control.

TFmax(N+1) is the maximum TB number during the period from (T0 +
RateRstrctTimerLen x N) to (T0 + RateRstrctTimerLen x (N + 1)), where T0 is the
time when the MAC receives the TF control indication message.

Ratelimitcoeff is specified by the RateRstrctCoef parameter.
If the RNC cannot find an appropriate service for the TF control or the number of times
that TF control is performed exceeds DlOlcFTFRstrctTimes, the action fails. The OLC
takes the next action.
428
If the congestion is relieved, the RNC sends the congestion relief indication to the MAC.
At the same time, the rate recovery timer (RateRecoverTimerLen) is started. When this
timer expires, the MAC increases the data rate step by step.
MAC recovers the TFC selection by calculating the maximum TB number with the
formula:

TFmax(N+1) = TFmax(N) x RateRecoverCoeff
Here:

TFmax(0) is the maximum TB number of the BE service before congestion relief
indication is received.

TFmax(N+1) is the maximum TB number during the period from (T1 +
RateRecoverTimerLen x N) to (T1 + (RateRecoverTimerLen x (N + 1)), where T1 is
the time when the MAC receives the congestion relief indication message.

RateRecoverCoeff is specified by the RecoverCoef parameter.
For the TF control in the uplink, the OLC algorithm operates as follows:
Based on the integrated priority, the algorithm sorts the DCH RABs in descending order.
The algorithm selects the RABs with the lowest integrated priorities and with the rates
higher than UlDcccRateThd. The number of selected RABs is specified by the
UlOlcFTFRstrctRabNum parameter.
The RNC sends the TRANSPORT FORMAT COMBINATION CONTROL message to the UE
that accesses the specified service. This message contains the following IEs:

Transport Format Combination Set Identity: defines the available TFC that the UE
can select, that is, the restricted TFC sub-set. It is always the two TFCs
corresponding to the lowest data rate.

TFC Control Duration: defines the period in multiples of 10 ms frames for which
the restricted TFC sub-set is to be applied. It is set to a random value from the
range of 10 ms to 5120 ms, so as to avoid data rate upsizing at the same time.

After the TFC control duration is due, the UE can apply any TFC of TFCS before
the TF control.
Each time, the RNC selects a certain number of RABs, which is specified by
UlOlcFTFRstrctRabNum, for TF control. The UE of each selected RAB will receive the
TRANSPORT FORMAT COMBINATION CONTROL message. The number of times that TF
control is performed is specified by UlOlcFTFRstrctTimes.
If the RNC cannot find an appropriate service, the OLC performs the next action.
429
Example of TF Control
Page180
The above figure shows an example of TF control. In this example, the MAC performs TF
control of a downlink 384 kbit/s service, and RateRstrctCoef is set to 0.68. And the time
between point A and point B is specified by the RateRstrctTimerLen parameter.

Before point A, the cell is not in OLC state. The downlink data transfer rate is 384
kbit/s, the corresponding TF is 12 x 336, and TFS is {12 x 336, 8 x 336, 4 x 336, 2
x 336, 1 x 336, 0 x 336}.

At point A, the cell enters OLC state. The RNC selects this RAB for fast TF
restriction. MAC restricts the TFC selection during the period between point A
and point B by calculating the maximum TB number as follows:

TFmax(1) = TFmax(0) x Ratelimitcoeff = 12 x 0.68 = 8.16
Compare 8.16 with the TFS. Then, the maximum TB number is 8.

At point B, the MAC performs further TFC restriction by calculating maximum TB
number as follows:

TFmax(2) = TFmax(1) x Ratelimitcoeff = 8 x 0.68 = 5.44
Compare 5.44 with the TFS. Then, the maximum TB number is 4.

At point C and point D, similar process is followed.
430

DlDcccRateThd
Parameter name: Downlink Bit Rate Threshold For DCCC
Recommended value: D64, namely 64Kbit/s
DlOlcFTFRstrctRabNum
Parameter name: DL OLC fast TF restrict RAB number
DlOlcFTFRstrctTimes
Parameter name: DL OLC fast TF restrict times
DlDcccRateThd

Content: For a BE service that has a low maximum rate, the DCCC algorithm is not obviously
effective yet it increases algorithm processing. Thus, the traffic-based DCCC algorithm is applied to
BE services whose maximum DL rate is greater than the threshold.
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384; step: 1
Set this parameter through SET UDCCC.
DlOlcFTFRstrctRabNum

Page181
Content: Selection of RABs of the OLC is based on the service priorities and ARP values and bearing
priority indication. The RAB of low priority is under control. The higher the parameters are, the
more users are involved in fast TF restriction under the same conditions, the quicker the cell load
decreases, and the more user QoS is affected.
Value range: 1~10
Set this parameter through ADD UCELLOLC/ MOD UCELLOLC.
DlOlcFTFRstrctTimes

Content: After the overload is triggered, the RNC immediately executes OLC by first executing fast
TF restriction. The internal counter is incremented by 1 with each execution. If the number of
overloads does not exceed the OLC action threshold, the system lowers the BE service rate by
lowering TF to relieve the overload. If the number of overloads exceeds the OLC action threshold,
the previous operation has no obvious effect on alleviating the overload and the system has to
release users to solve the overload problem.
Value range: 0~100
431

RateRstrctTimerLen/RateRecoverTimerLen
Parameter name: DL TF rate restrict/recover timer length
Recommended value: 3000ms, 5000ms
RateRstrctCoef/RecoverCoef
Parameter name: DL TF rate restrict/recover coefficient
Page182
RateRstrctTimerLen/RateRecoverTimerLen

Content: These parameters define the downlink data rate restrict/recover timer
length in fast TF restriction. Both of them are effective only to the downlink. The
uplink fast TF restriction is performed by the UE. For the uplink fast TF restriction,
the RNC only delivers a new TFCS and randomly selects a comparatively bigger
time length in the signaling value scope. The UE automatically release the TF
restriction once the time expires.
Physical unit: ms
RateRstrctCoef/RecoverCoef
Content: These parameters define the downlink OLC fast TF rate restrict/recovery
coefficient. Both of them are effective only to the downlink.

Value range: 1~99/100~200

Physical value range: 0.01~0.99/1~2; step:0.01

Physical unit: %
Set these parameters through ADD UCELLOLC/ MOD UCELLOLC.
432

UlDcccRateThd
Parameter name: Uplink Bit Rate Threshold For DCCC
Recommended value: D64, namely 64Kbit/s
UlOlcFTFRstrctRabNum
Parameter name: UL OLC fast TF restrict RAB number
UlOlcFTFRstrctTimes
Parameter name: UL OLC fast TF restrict times
UlDcccRateThd

Content: For a BE service that has a low maximum rate, the DCCC algorithm is not obviously
effective yet it increases algorithm processing. Thus, the traffic-based DCCC algorithm is applied to
BE services whose maximum UL rate is greater than the threshold.
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384; step: 1
Set this parameter through SET UDCCC.
UlOlcFTFRstrctRabNum

Page183
Content: Selection of RABs of the OLC is based on the service priorities and ARP values and bearing
priority indication. The RAB of low priority is under control. The higher the parameters are, the
more users are involved in fast TF restriction under the same conditions, the quicker the cell load
decreases, and the more user QoS is affected.
Value range: 1~10
UlOlcFTFRstrctTimes

Content: After the overload is triggered, the RNC immediately executes OLC by first executing fast
TF restriction. The internal counter is incremented by 1 with each execution. If the number of
overloads does not exceed the OLC action threshold, the system lowers the BE service rate by
lowering TF to relieve the overload. If the number of overloads exceeds the OLC action threshold,
the previous operation has no obvious effect on alleviating the overload and the system has to
release users to solve the overload problem.
Value range: 0~100
433
OLC Actions - Switching BE Services

to Common Channels
Target user:
Select users with the lowest integrated priority
The users with the DCH or HSPA BE services in PS domain
Execution:
The RNC sends RB Reconfiguration message to UE
The UE makes a response by RB Reconfiguration Complete
Page184
For switching BE services to common channels, the OLC algorithm operates as follows:

Based on the integrated priority, the algorithm sorts all the UEs in the PS domain
in descending order.

The algorithm selects the UEs with the lowest integrated priorities. The number
of selected UEs is specified by TransCchUserNum. If the selection fails, the OLC
takes the next action.

The OLC switches the selected UEs to common channels.
This function is disabled when the TransCchUserNum parameter is set to 0.
434

TransCchUserNum
Parameter name: Transfer Common Channel User number
Page185
TransCchUserNum

Content: When the system is overloaded and congested, users on the DCH or
HSPA can be reconfigured to the CCH in order to reduce the cell load and recover
the system. This parameter defines the maximum number of users selected in
executing reconfiguration to the CCH. If the parameter value is too high, the OLC
action may fluctuate greatly and over control may occur (the state of overload
and congestion turns into another extreme--underload). If the parameter value is
too low, the OLC action has a slow response and the effect is not apparent,
affecting the OLC performance.
Value range: 0~10
Set this parameters through ADD UCELLOLC/ MOD UCELLOLC.
435
OLC Actions - Adjusting the Maximum

FACH TX Power
Target FACH channel:

During an OLC period, the OLC can adjust the power of only
one FACH. If multiple FACHs meet the conditions, the OLC
adjusts them one by one in different OLC periods
Execution:
The cell adjusts the maximum FACH TX power:
Pt arg et = Pmax Delta
Page186
The procedure for adjusting the maximum FACH transmit power is as follows:

Set the maximum FACH transmit power to the target maximum transmit power.
The target maximum transmit power is calculated according to the above
formula.

Ptarget is the target maximum transmit power.

Pmax is the maximum FACH transmit power (MaxFachPower).

Delta is the FACH power reduction step (FACHPwrReduceValue).

If the congestion is relieved after the power adjustment, the system starts the
FACH power recovery timer, which is set to 5s. When the timer expires, the
maximum FACH transmit power is increased to the original maximum FACH
transmit power if the system is always in the normal state before the timer
expires.
436

MaxFachPower
Parameter name: Max transmit power of FACH
FACHPwrReduceValue
Parameter name: FACH power reduce value
MaxFachPower

Page187
Content: The offset between the FACH transmit power and PCPICH transmit
power in a cell. If MaxFachPower is excessively low, the UE at the cell verge fails
to receive correctly the services and signaling borne over the FACH, resulting in
the influence on the downlink common channel coverage and the cell coverage. If
MaxFachPower is excessively high, other channels are interfered, the downlink
power resources are occupied, and consequently the cell capacity is influenced.
Physical unit: dB
Set this parameter through ADD UFACH.
FACHPwrReduceValue

Content: This parameter defines the reduce value in reducing FACH power Action.
Value range: 0~30
Physical unit: dB
437
OLC Actions - Releasing Some RABs

Target user:
Select RABs with high bit rate, when the integrated priority
of some RABs are identical
Execution:
The RNC sends IU RELEASE REQUEST or RAB RELEASE

REQUEST message to CN, and sample call drop counter
Page188
For the release of some RABs in the uplink, the OLC algorithm operates as follows:

Based on the integrated priority, the algorithm sorts all RABs including HSUPA and DCH
services in descending order.

The algorithm selects the RABs with the lowest integrated priorities. If the integrated
priorities of some RABs are identical, it selects the RAB with a higher rate (that is, the
current rate for DCH RAB or the GBR for HSUPA RAB) in the uplink. The number of
selected RABs is specified by UlOlcTraffRelRabNum.

The selected RABs are released directly.
For the release of some RABs in the downlink, the OLC algorithm operates as follows:

If the SeqOfUserRel parameter is set to USER_REL, then:

Based on the integrated priority, the algorithm sorts all non-MBMS RABs in
descending order.

The algorithm selects the RABs with the lowest integrated priorities. If the
integrated priorities of some RABs are identical, it selects the RAB with a higher
rate (that is, the current rate for DCH RAB or the GBR for HSDPA RAB) in the
downlink. The number of selected RABs is specified by DlOlcTraffRelRabNum.

The selected RABs are directly released.

If all non-MBMS RABs are released but congestion persists in the downlink, MBMS
RABs are selected.

If the SeqOfUserRel parameter is set to MBMS_REL, then:

Based on the ARP, the algorithm sorts all MBMS RABs in descending order.

The algorithm selects the RABs with the lowest integrated priorities. The number
of selected RABs is specified by MbmsOlcRelNum.

The selected RABs are directly released.

If all MBMS RABs are released but congestion persists in the downlink, non-MBMS
RABs are selected.
438

UlOlcTraffRelRabNum/DlOlcTraffRelRabNum
Parameter name: UL OLC traff release RAB number
SeqOfUserRel
Parameter name: Sequence of user release
Recommended value: MBMS_REL
MbmsOlcRelNum
Parameter name: MBMS services number released
UlOlcTraffRelRabNum/DlOlcTraffRelRabNum

Page189
Content: These parameters define the maximum number of RABs released in

executing uplink/downlink OLC service release.
Value range: 0~10
SeqOfUserRel

Content: This parameter indicates whether the MBMS service is released first or
user first when the overload occurs.
Value range: MBMS_REL(MBMS service), USER_REL(UE)
Physical value range: MBMS_REL, USER_REL
MbmsOlcRelNum
Content: This parameter defines the maximum number of MBMS services released
in executing downlink OLC service release.

Value range: 0~8

Set these parameters through ADD UCELLOLC/ MOD UCELLOLC.
439
Abbreviations
AAL2 ATM Adaptation Layer type 2
Abis GSM Interface BTSBSC
ACI Adjacent Channel Interference
ACK ACKnowledgement
ACLR Adjacent Channel Leakage power Ratio
AMC Adaptive Modulation and Coding
AMPS Advance Mobile Phone Service
AMR Adaptive Multi Rate
AS Access Slot; Access Stratum
ASC Access Service Class
ASU Active Set Update
AWGN Additive White Gaussian Noise
B(T)S Base (Transceiver) Station
BA BCCH Allocation
BB BaseBand
BCC Base station Colour Code
BCCH Broadcast Control CHannel
BCH Broadcast CHannel
BCS Binary Coded Signalling
BEP Bit Error Probability
BER Bit Error Rate
BFN Node B Frame Number
BLER BLock Error Rate
BPSK Binary Phase Shift Keying
BSC Base Station Controller
BSIC Base Station Identity Code
BSS Base Station Subsystem
BSSMAP Base Station System Management Application Part
C/I Carrier-to-Interference ratio
CB Cell Broadcast
CBR Call Block Ratio
CC Call Control; Convolutional Coding; Cumulative Counter
CCCH Common Control CHannel
CCH Control CHannel
CCPCH Common Control Physical CHannel
CCTrCH Coded Composite Transport CHannel
CD Collision Detection
CDF Cumulative Distribution/Density Function
CDMA Code Division Multiple Access
CFN Connection Frame Number
CGI Cell Global Identification
CI Cell Identity
CIO Cell Individual Offset
CM Compressed Mode; Configuration Management
C-plane Control plane
CPCH Common Packet CHannel
CPICH Common PIlot CHannel
CQI Channel Quality Indicator
440
CRNC Controlling RNC

CS Coding Scheme; Circuit Switched
CSSR Call Setup Success Ratio
CTCH Common Traffic CHannel
DCCH Dedicated Control CHannel
DCH Dedicated CHannel
DCR Drop Call Ratio
DCS1800 Digital Cellular System (GSM) at 1800MHz band
DHO Diversity HandOver
DiffServ Differentiated Services
DPCCH Dedicated Physical Control CHannel
DPCH Dedicated Physical CHannel
DPDCH Dedicated Physical Data CHannel
DQPSK Differential QPSK
DRNC Drifting RNC
DRX Discontinuous Reception
DS Direct Sequence
DSCH Downlink Shared CHannel
DTCH Dedicated Traffic CHannel
DTX Discontinuous Transmission
EDGE Enhanced Data rates for GSM Evolution
EFR Enhanced Full Rate
EGPRS Enhanced GPRS
EIRP Equivalent Isotropic Radiated Power
ETSI European Telecommunications Standards Institute
FACH Forward Access CHannel
FBI FeedBack Information
FDD Frequency Division Duplex
FDMA Frequency Division Multiple Access
FEC Forward Error Correction; Forwarding Equivalence Class
FER Frame Erasure Rate
FH Frequency Hopping
FIFO First In First Out
FM Fault Management
FN Frame Number
FP Frame Protocol
FTP File Transfer Protocol
G Geometry factor
GMM GPRS MM
GMSK Gaussian Minimum Shift Keying
GP Guard Period
GPIB General Purpose Interface Bus
GPRS General Packet Radio Service
GPS Global Positioning System
GSM Global System for Mobile communication
GSM1900 GSM at 1900MHz band
GTP GPRS Tunnel Protocol
GUI Graphical User Interface
H-ARQ Hybrid ARQ
HCS Hierarchical Cell Structure
HD Harmonic Distortion
441
HHO Hard HO
HLR Home Location Register
HLS Higher Layer Scheduling
HO HandOver
HSCSD High-speed Circuit Switched Data
HSDPA High-speed Downlink Packet Access
HS-DPCCH High-speed Dedicated Physical Control CHannel (UL)
HS-DSCH High-speed DSCH
HS-PDSCH High-speed Physical DSCH
HS-SCCH High-speed Shared Control CHannel (DL)
HSUPA High-speed Uplink Packet Access
ID IDentifier
IE Information Element
IMAP Internet Message Access Protocol
IMD Inter-Modulation Distortion
IMEI International Mobile station Equipment Identity
IMS IP Multimedia Sub-system
IMSI International Mobile Subscriber Identity
IMT International Mobile Telecommunications
IR Incremental Redundancy
IS Interim Standard (US)
IS-136 North American TDMA
IS-54 North American TDMA Digital Cellular
IS-95 North American Version of the CDMA Standard
ISCP Interference Signal Code Power
IS-HO Inter-system HO
ITU-T International Telecommunication Union, Telecommunication Standardisation Sector
Iu Interconnection point between an RNC and a core network
Iub Interface between an RNC and a Node B
Iur Logical interface between two RNCs
KPI Key Performance Indicator
KQI Key Quality Indicator
ksps Kilo symbols per second
L1 OSI Layer 1: Physical Layer
L2 OSI Layer 2: Radio Data Link Layer
L3 OSI Layer 3: Radio Network Layer
LA Link Adaptation; Location Area
LAC Location Area Code
LAN Local Area Network
LC Load Control
LCS LoCation-based Services
LDAP Lightweight Directory Access Protocol
LF Load Factor
LLC Logical Link Control
LNA Low-Noise Amplifier
LoCH Logical CHannel
LOS Line Of Sight
LSA Localised Service Area
MAB Minimum Allowed Bitrate
MAC Medium Access Control
Mbps Mega bits per second
442
MCC Mobile Country Code

MCL Minimum Coupling Loss
Mcps Mega chips per second
MCS Modulation and Coding Scheme
MDC Macro Diversity Combining
MHA Mast Head Amplifier
MIB Management Information Base
MIMO Multiple Input Multiple Output
MISO Multiple Input Single Output
MM Mobility Management
MMS Multimedia Message Service
MMUSIC Multiparty MUltimedia SessIon Control
MNC Mobile Network Code
MOC Managed Object Class
MRC Maximal Ratio Combining
MS Mobile Station
MSC Mobile Switching Centre
MT Mobile Terminal
MTU Maximum Transfer Unit
NACK Negative ACK
NAS Non-Access Stratum
NB NarrowBand
NBAP Node B Application Part
NCC Network Colour Code
NCx Network Control (NC0, NC1, NC2)
NE Network Element
NEHO Network Evaluated HO
NF Noise Figure
NGB Non-GB
NLOS Non-LOS
Node B WCDMA BS
NRT Non-Real Time
NSS Networking Sub-System
OCNS Other Cell Noise Source
OFDM Orthogonal Frequency Division Multiplexing
OH OkumuraHata
OMC Operations and Maintenance Centre
OMG Object Management Group
OSI Open Systems Interconnection
OSS Operations Support System
OVSF Orthogonal Variable Spreading Factor
PACCH Packet Associate Control CHannel
PAGCH Packet Access Grant CHannel
PARC Per-Antenna Rate Control
PBCCH Packet Broadcast Control CHannel
PC Power Control
PCCCH Packet Common Control CHannel
PCCH Paging Control CHannel
P-CCPCH Primary CCPCH
PCH Paging CHannel
PCMCIA PC Modular Computer Interface Adapter card
PCPCH Physical CPCH
P-CPICH Primary CPICH
443
PCS Personal Communications Systems

P-CSCF Proxy Call State Control Function
PCU Packet Control Unit
PDCH Packet Data Channel
PDCP Packet Data Convergence Protocol
PDF Probability Density Function
PDP Packet Data Protocol
PDSCH Physical DSCH
PDTCH Packet Data Traffic CHannel
PDU Protocol Data Unit
PG Processing Gain
PHY PHYsical layer
PI Paging Indicator; Performance Indicator
PICH Paging Indicator CHannel
PLMN Public Land Mobile Network
PM Performance Management
PN PseudoNoise
PO Power Offset
PoC Push (to talk) over Cellular
PPCH Packet Paging CHannel
PPP Point-to-Point Protocol
PQ Packet Queuing
PRACH Physical RACH
PS Packet Switched; Packet Scheduler
PSC Primary Synchronisation Code
P-SCH Primary Synchronisation CHannel
PSK Phase Shift Keying
PSTN Public Switched Telephone Network
PTT Push To Talk
QM Quality Manager; Quality Management
QoS Quality of Service
QPSK Quadrature/Quaternary Phase Shift Keying
RA Routing Area
RAB Radio Access Bearer
RAC Routing Area Code
RACH Random Access CHannel
RAI Routing Area Identifier
RAKE special receiver type used in CDMA
RAM Radio Access Mode
RAN Radio Access Network
RANAP Radio Access Network Application Part
RAT Radio Access Technique
RAU Routing Area Update
RB Radio Bearer
RF Radio Frequency
RFC (IETF) Request For Comments
RFN RNC Frame Number
RL Radio Link
RLC Radio Link Control
RLCP Radio Link Control Protocol
RM Resource Manager
RMSS Receiver Maximum Segment Size
RN Radio Network
444
RNC Radio Network Controller

RNP Radio Network Planning
Abbreviations xxvii
RNS Radio Network Subsystem

RNSAP Radio Network Subsystem Application Part
RNTI Radio Network Temporary Identity
RR Radio Resource; Receiver Report; Resource Request
RRC Radio Resource Control; Route Raised Cosine
RRI Radio Resource Indicator
RRM Radio Resource Management
RRP Radio Resource Priority
RRU Radio Resource Utilisation
RSCP Received Signal Code Power
RSSI Received Signal Strength Indicator
RSVP Resource ReSerVation Protocol
RT Real-Time
RTCP Real-Time Control Protocol
RTO Roundtrip Time Out
RTP Real-time Transport Protocol
RTT Round-Trip Time
RTTVAR Round-Trip Time VARiation
RTVS Real Time Video Streaming
RU Resource Unit
Rx Receive
RxD Receive Diversity
SA Spectrum Analyser; Service Area
SACK Selective ACK
SAI Service Area Identifier
SAP Service Access Point
S-CCPCH Secondary CCPCH
SCH Synchronisation CHannel
S-CPICH Secondary CPICH
SCTP Stream Control Transmission Protocol
SDCCH Standalone Dedicated Control CHannel
SDP Session Description Protocol
SDU Service Data Unit
SF Spreading Factor
SFN System Frame Number
SGSN Serving GPRS Support Node
SHO Soft HO
SI Status Inspection
SIGTRAN SIGnalling TRANsport
SIM Subscriber Identity Module
SIMO Single Input Multiple Output
SINR Signal-to-Interference and Noise Ratio
SIP Session Initiation Protocol
SIR Signal to Interference Ratio
SLA Service Level Agreement
SLP Service Logic Program
SM Session Management; Service Management
SMS Short Message Services
SMTP Simple Message Transfer Protocol
SNR Signal-to-Noise Ratio
SR Sender Report
445
SRB Signalling RB
SRNC Serving RNC
SRNS Serving RNS
SS Spread Spectrum; Supplementary Services
SSC Secondary Synchronisation Code
S-SCH Secondary SCH
SSDT Site Selection Diversity Technique
STm-1 Synchronous Transport Module-1: An ITU-T-defined SDH physical interface for digital transmission in
ATM at the rate of 155.52 Mbps
STTD Space Time Transmit Diversity
T1 1.544Mbps Transmission Link
TACS Total Access Communication System
TB Transport Block
TBF Temporary Block Flow
TBS Transport Block Set
TC Transmission Convergence
TCH Traffic CHannel
TCP Transmission Control Protocol
TDD Time Division Duplex
TDM Time Division Multiplex
TDMA Time Division Multiple Access
TE Terminal Equipment
TF Transport Format
TFC Combination
TFCI Transport Format Combination Indicator
TFCS Transport Format Combination Set
TFI Transport Format Indicator
TFS Transport Format Set
THP Traffic Handling Priority
TIA Telecommunications Industry Association
TM Transparent Mode; Telecom Management
TMN Telecommunications Management Network
TMSI Temporary Mobile Subscriber Identity
TN Termination Node
TOM Telecom Operations Map
TPC Transmit Power Control
TPRC for CD-SIC Tx Power Ratio Control for Code Domain Successive Interference Cancellation
TR Technical Recommendation
TrCH Transport CHannel
TRX Transmit and Receive Unit; Transceiver
TS Technical Specification
TSG Technical Specification Group
TSL Time SLot
TSTD Time Switched Transmit Diversity
TTI Transmission Time Interval
UMTS Universal Mobile Telecommunications System
U-plane User plane
URA UTRAN Registration Area
USIM UMTS SIM
UTRA(N) Universal Terrestrial Radio Access (Network)
Uu Radio interface between UTRAN and UE
446

WCDMA BSC6900 R11 Features and Algorithms

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

WCDMA BSC6900 R11 Features and Algorithms

Diunggah oleh

Hak Cipta:

Format Tersedia

WCDMA Radio Network Features &

Southern Eastern Africa Learning

WCDMA UE BEHAVIORS IN IDLE MODE ........................................................................................................ 3

Inter-Frequency Handover Overview .......................................................................................................... 159

WCDMA UE BEHAVIORS IN IDLE MODE

UE behaviors in idle mode include:

System information reception

Cell selection and reselection

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

3GPP TS 22.011: Service Accessibility

3GPP TS 23.122: NAS Functions Related to Mobile Station

3GPP TS 24.008: Mobile Radio Interface Layer 3 Specification;

3GPP TS 25.304: UE Procedures in Idle Mode and Procedures

3GPP TS 25.331: Radio Resource Control (RRC)

3GPP TS 31.102: Characteristics of The USIM Application

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

Describe the working principles of the UE Behaviors in Idle

Perform parameters modification of the UE Behaviors in Idle

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

UE does not have UTRAN carrier information:

In order to find a suitable cell to stay, UE will scan all the

UE has UTRAN carrier information:

UE will try whether the original cell is suitable to stay. If not,

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Cell Search (Cont.)

Frame synchronization and

Primary scrambling code

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Step 1: Slot synchronization

When the UE is switched on, or the coverage is restored, or the

If no registered PLMN or equivalent PLMN is available, or if

Automatic PLMN selection: the UE automatically selects a PLMN

Manual PLMN selection: the UE shows all available PLMNs to the

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

PLMN Selection (Cont.)

Automatic PLMN selection: UE can select a PLMN from the

Selecting from the HPLMNs: UE maintains a list of allowed and

Manual PLMN selection: UE maintains a list of allowed and

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

System Information Reception

Structure of System Information

System information is organized as a tree, including:

MIB (Master Information Block)

SIB (System Information Block)

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

SIB1: contains the system information for NAS and the

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Reception of System Information

The UE shall read system information broadcast on a BCH

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Cell Selection and Reselection

When the PLMN is selected and the UE is in idle mode,

There are four states involved in cell selection:

Any cell selection

Camped on any cell

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Cell Selection (Cont.)

Two types of cell selection:

Initial cell selection

If no cell information is stored for the PLMN, the UE starts this

Stored information of cell selection

If cell information is stored for the PLMN, the UE starts this

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.