Handover Control

Handover Control
Feature Guide
Handover Control
Handover Control
Version Date Author Reviewer Notes
Update the features introduced in version

UR14, including:
1. Add "3.2.7.4 Soft Handover between Cells
with Different Transport Time Delay
Grades over Iub".
2. Add "3.2.1.1.1 Optimization of
Measurement Setup Occasion".
3. Add "3.7.4 Optimization of Relocation
Process of Dual Domain".
4. Modify "3.5.5.1 Event 3A/3C Processing":
add the description that "inter-RAT
handover is not permitted when either of
domains is in the RRC stage".
5. Add the parameter
URncFunction.sHOforMIubTimeSpt,
Feng Hong
V1.0 2015/06/10 UExtCelInfoFDD.rptforDCHinSIB.
Chen Yanli
6. Delete parameter
UCompressMode.dlCMMethod.
7. URncFunction.GResPara48 bit11 is
replaced by URncInfo.sendDetetOcca;
URncFunction.GResPara47 bit14 is
replaced by
URncInfo.modeOfIntraHardHO.
8. Delete the parameter
URncFunction.GResPara14.
9. Add the chapter “Macro Diversity
Combining Strategy” and the relative
parameters and counters.
10. Add the parameters:
URncFunction.GResPara56 bit3,
URncFunction.GResPara56 bit4
ZTE Confidential Proprietary 1

Handover Control
Version Date Author Reviewer Notes
© 2015 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.

Handover Control
TABLE OF CONTENTS
1 Feature Attribute ............................................................................................. 11
2 Overview .......................................................................................................... 11
2.1 Feature Introduction ........................................................................................... 11
2.1.1 ZWF21-03-001 Soft/Softer Handover ................................................................. 11
2.1.2 ZWF21-03-002 Intra-Frequency Hard Handover ................................................ 12
2.1.3 ZWF21-03-003 Inter-Frequency Hard Handover ................................................ 13
2.1.4 ZWF21-03-004 Inter-RAT Mobility ..................................................................... 13
2.1.5 ZWF21-03-006 Inter-RNC Handover with Iur Support ........................................ 14
2.1.6 ZWF21-03-008 Directed Signaling Connection Re-establishment ...................... 14
2.1.7 ZWF21-03-009 Coverage Based Handover ....................................................... 15
2.1.8 ZWF21-03-010 Compressed Mode .................................................................... 16
2.1.9 ZWF21-03-011 Neighboring Cells Priorities ....................................................... 17
2.1.10 ZWF21-03-020 SRNS Relocation ...................................................................... 18
2.2 License Control .................................................................................................. 19
2.3 Correlation with Other Features ......................................................................... 20
3 Technical Description ..................................................................................... 21

3.1 ZWF21-03-009 Coverage Based Handover ....................................................... 21
3.2 ZWF21-03-001 Soft/Softer Handover ................................................................. 21
3.2.1 Intra-Frequency Measurement ........................................................................... 22
3.2.2 The Number of Configured Intra-frequency Neighboring Cells is Up to 40 ......... 31
3.2.3 Intra-frequency Event Triggering ........................................................................ 32
3.2.4 Intra-frequency Handover Decision and Execution............................................. 39
3.2.5 Intra-frequency Event Buffering.......................................................................... 40
3.2.6 Detected Set Handover and Detected Set Tracing ............................................. 43
3.2.7 Strategy for Special Scenarios in Intra-frequency Handover .............................. 45
3.2.8 Intra-Frequency Handover Procedure ................................................................ 50
3.3 ZWF21-03-002 Intra-Frequency Hard Handover ................................................ 50
3.3.1 Intra-Frequency Hard Handover Scenarios ........................................................ 50
3.3.2 Intra-Frequency Hard Handover Procedure ....................................................... 52
3.4 ZWF21-03-003 Inter-Frequency Hard Handover ................................................ 54
3.4.1 Selection Strategy of Inter-Frequency and Inter-RAT Handover......................... 54
3.4.2 Switch Control Strategy of Measurement-based Inter-frequency Handover for
Services ............................................................................................................. 57
3.4.3 Inter-frequency Measurement ............................................................................ 57
3.4.4 Inter-frequency Event Triggering ........................................................................ 67
3.4.5 Inter-frequency Handover Decision and Execution............................................. 72
3.4.6 Inter-frequency Event Buffering.......................................................................... 74

Handover Control
3.4.7 Coupling Processing of Different Handovers ...................................................... 75

3.4.8 Strategy of Coupling Between Intelligent Carrier Power Off/On and
Inter-Frequency Handover ................................................................................. 76
3.4.9 Periodic Inter-frequency Measurement Reporting .............................................. 76
3.4.10 Control Strategy for Blind Handover Triggered by Second-Try ........................... 79
3.4.11 Inter-Frequency Handover Procedure ................................................................ 80
3.5 ZWF21-03-004 Inter-RAT Mobility ..................................................................... 80
3.5.1 Selection Strategy of Inter-Frequency and Inter-RAT Handover......................... 81
3.5.2 Switch Control Strategy of Measurement-based Inter-RAT Handover for
Services ............................................................................................................. 81
3.5.3 Inter-RAT Measurements ................................................................................... 82
3.5.4 Inter-RAT Event Triggering ................................................................................ 92
3.5.5 Inter-RAT Handover Decision and Execution ..................................................... 95
3.5.6 Inter-RAT Event Buffering .................................................................................. 97
3.5.7 Coupling Processing of Different Handovers ...................................................... 97
3.5.8 UMTS->GSM Handover Based on Board Power Off .......................................... 98
3.5.9 Special UMTS->GSM Handover Strategy based on the Indoor Neighboring cell 99
3.5.10 Strategy of Coupling Between Intelligent Carrier Power Off/On and Inter-RAT
Handover ........................................................................................................... 99
3.5.11 Periodic Inter-RAT Measurement Reporting..................................................... 100
3.5.12 Inter-RAT Handover Process ........................................................................... 103
3.6 ZWF21-03-006 Inter-RNC Handover with Iur Support ...................................... 108
3.6.1 Parameter Configuration via Iur ....................................................................... 108
3.6.2 Strategy for Soft Handover OD Switch Configuration in the Signaling Stage .... 108
3.6.3 Special Events Processing via Iur for CS+PS .................................................. 109
3.6.4 Special Events Processing via Iur for Only PS ................................................. 109
3.6.5 Special Events Processing via Iur for Only CS ................................................. 110
3.6.6 Special Events Processing via Iur for PS0/0 .................................................... 110
3.6.7 Inter-RNC Handover Through the lur Interface................................................. 111
3.7 ZWF21-03-020 SRNS Relocation .................................................................... 115
3.7.1 Relocation Triggered by Soft Handover ........................................................... 115
3.7.2 Relocation Triggered by Hard Handover .......................................................... 118
3.7.3 Special Relocation Processing of CS+PS Services .......................................... 121
3.7.4 Optimization of Dual-Domain Relocation.......................................................... 121
3.8 ZWF21-03-008 Directed Signaling Connection Re-establishment .................... 122
3.8.1 DSCR in Dedicated Status ............................................................................... 122
3.8.2 DSCR in Common Status ................................................................................ 122
3.8.3 Coupling between Relocation and DSCR......................................................... 123
3.9 ZWF21-03-011 Neighboring Cells Priorities ..................................................... 123
3.9.1 Cell Priority Configuration ................................................................................ 124
3.9.2 Strategy for Neighboring Cells Exceeding 32 ................................................... 125
3.10 ZWF21-03-010 Compressed Mode .................................................................. 126

Handover Control
3.10.1 Introduction to Compressed Mode ................................................................... 126

3.10.2 Compressed Mode Strategy ............................................................................ 129
3.10.3 Compressed Mode Configuration Strategy via RNC ........................................ 133
4 Parameters..................................................................................................... 135
4.1 ZWF21-03-001 Soft/Softer Handover ............................................................... 135
4.2 ZWF21-03-002 Intra-Frequency Hard Handover .............................................. 171
4.3 ZWF21-03-003 Inter-Frequency Hard Handover .............................................. 173
4.4 ZWF21-03-004 Inter-RAT Mobility ................................................................... 198
4.5 ZWF21-03-006 Inter-RNC Handover with Iur Support ...................................... 237
4.6 ZWF21-03-008 Directed Signaling Connection Re-establishment .................... 239
4.7 ZWF21-03-009 Coverage Based Handover ..................................................... 240
4.8 ZWF21-03-010 Compressed Mode .................................................................. 241
4.8.1 UCompressMode ............................................................................................. 246
4.9 ZWF21-03-011 Neighboring Cells Priorities ..................................................... 247
4.10 ZWF21-03-020 SRNS Relocation .................................................................... 249
5 Related Counters and Alarms ...................................................................... 253

5.1 Related Counters ............................................................................................. 253
5.1.1 ZWF21-03-001 Soft/Softer Handover ............................................................... 253
5.1.2 ZWF21-03-002 Intra-Frequency Hard Handover .............................................. 255
5.1.3 ZWF21-03-003 Inter-Frequency Hard Handover .............................................. 257
5.1.4 ZWF21-03-004 Inter-RAT Mobility ................................................................... 258
5.1.5 ZWF21-03-006 Inter-RNC Handover with Iur Support ...................................... 261
5.1.6 ZWF21-03-020 SRNS Relocation .................................................................... 263
5.1.7 ZWF21-03-008 Directed Signaling Connection Re-establishment .................... 269
5.1.8 ZWF21-03-011 Neighboring Cells Priorities ..................................................... 269
5.1.9 ZWF21-03-010 Compressed Mode .................................................................. 269
5.2 Related Alarms ................................................................................................ 270
6 Engineering Guide ........................................................................................ 271

6.1 Application Scenario ........................................................................................ 271
6.2 Feature Activation Procedure ........................................................................... 271
6.2.6 ZWF21-03-008 Directed Signaling Connection Re-establish............................ 313
6.2.7 ZWF21-03-009 Coverage Based Handover ..................................................... 315

Handover Control

6.3 Feature Validation Procedure .......................................................................... 323
6.4 Feature Deactivation Procedure....................................................................... 330
6.4.2 ZWF21-03-002 Intra-Frequency Handover ...................................................... 330
6.5 Impact on the Network ..................................................................................... 332
7 Abbreviation .................................................................................................. 333
8 Reference Document..................................................................................... 335

Handover Control
FIGURES
Figure 3-1 Parameter Indexing Principle of Intra-frequency Handover ...............................28

Figure 3-2 Time-To-Trigger mechanism .............................................................................34
Figure 3-3 Intra-RNC Hard Handover ................................................................................52
Figure 3-4 Inter-RNC Hard Handover Without an lur Interface ...........................................53
Figure 3-5 Parameter Indexing Principle of Inter-frequency Handover ...............................63
Figure 3-6 Parameter Indexing Principle of Event 2D/2F during GSM Inter-RAT Handover
.............................................................................................................................................87
Figure 3-7 Parameter Indexing Principle of Inter-RAT handover events .............................89
Figure 3-8 3G to 2G CS Service Handover ......................................................................103
Figure 3-9 PS service reselection initiated by an UE in the case of 3G to 2G handover ...105
Figure 3-10 PS service reselection initiated by the RNC in the case of 3G to 2G handover
...........................................................................................................................................106
Figure 3-11 Intra-RNC Soft Handover (Adding a Radio Link) ...........................................111
Figure 3-12 Intra-RNC Soft Handover (Deleting a Radio Link) .........................................112
Figure 3-13 Intra-RNC Soft Handover (Swapping a Radio Link) ......................................113
Figure 3-14 Inter-RNC Hard Handover Through lur Interface ...........................................114
Figure 3-15 Relocation Triggered by Soft Handover ........................................................116
Figure 3-16 Relocation Triggered by Hard Handover .......................................................119
Figure 3-17 Cell Priority Configuration .............................................................................125
Figure 3-18 Downlink Compressed Mode Frame Type ....................................................127
Figure 3-19 Compressed Mode Parameters ....................................................................128
Figure 3-20 Transmission Gap (TG) Position ...................................................................129
Figure 3-21 Procedure for Configuring Parameters for Compressed Mode in Associated
Mode ..................................................................................................................................132
Figure 3-22 Procedure for Configuring Parameters for Compressed Mode in Dedicated
Mode ..................................................................................................................................133
Figure 6-1 Parameter Configuration Interface-1 ...............................................................287
Figure 6-3 Parameters configuration interface-3 ..............................................................288

Handover Control

Figure 6-10 Parameter Configuration Interface-10 ...........................................................293
Figure 6-33 Parameter Configuration Interface53 ............................................................322

Handover Control
TABLES
Table 2-1 License Control List ...........................................................................................19
Table 3-1 Compressed Mode Parameters List ...................................................................41
Table 3-2 Relationships between Services and IfHoSw .....................................................57
Table 3-3 Relationships between Services and RatHoSw ..................................................81
Table 4-1 Soft/Softer Handover Parameters List ..............................................................135
Table 4-2 Intra-Frequency Hard Handover Parameters List .............................................171
Table 4-3 Inter-Frequency Hard Handover Parameters List .............................................173
Table 4-4 Inter-RAT Mobility Parameters List ..................................................................198
Table 4-5 Inter-RNC Handover with Iur Support Parameters List .....................................237
Table 4-6 Directed Signaling Connection Re-establishment Parameters List ...................239
Table 4-7 Compressed Mode Parameters List .................................................................241
Table 4-8 Neighboring Cells Priorities Parameters List ....................................................247
Table 4-9 SRNS Relocation Parameters List ...................................................................249
Table 5-1 Soft/Softer Handover Counter List ...................................................................253
Table 5-2 Intra-Frequency Hard Handover Counter List ...................................................255
Table 5-3 Inter-Frequency Hard Handover Counter List ...................................................257
Table 5-4 Inter-RAT Mobility Counter List ........................................................................258
Table 5-5 Inter-RNC Handover with Iur Support Counter List...........................................261
Table 5-6 SRNS Relocation Counter List .........................................................................263
Table 5-7 Directed Signaling Connection Re-establishment Counter List.........................269
Table 5-8 Compressed Mode Counter List.......................................................................269
Table 6-1 Feature Validation Procedure...........................................................................325

Handover Control

Table 6-8 RNC Parameter List .........................................................................................330
Table 6-9 RNC Parameter List .........................................................................................331
Table 6-10 RNC Parameter List .......................................................................................332

Handover Control
1 Feature Attribute
RNC version: [ZXWR RNC V3.14.10.14/ZXUR 9000 V4.14.10.14]
Node B version: [ZXSDR V4.14.10]
Attribute: [Mandatory]
Involved NEs:
NE Name Related or Not Special Requirement
UE √ None
Node B √ None
RNC √ None
MSC - None
MGW - None
SGSN - None
GGSN - None
HLR - None
“√”: involved
“-”: not involved
2 Overview
2.1 Feature Introduction
2.1.1 ZWF21-03-001 Soft/Softer Handover
In a soft handover, a UE concurrently maintains several radio links with different Node Bs.
And while in a softer handover, a UE concurrently maintains radio links with several cells
in one Node B. The soft/softer handover only occurs in intra-frequency cells. Compared
with hard handover, the advantages of soft/softer handover are as follows:

Handover Control
 Soft and softer handovers are seamless handovers and service will not be
interrupted during the handover process. The soft and softer handover have
higher success rate and lower call drop rate.
 Macro diversity gain: When a UE maintains radio links with several cells, the
receiving side may enhance the accuracy of data reception by combining the
signal reception of several links, which helps to improve communication quality
as well.
 The best cell where the UE is located may establish a radio connection with
UE in time. Hence, it will reduce the transmitting power of UE, and eliminate
the near-far effect and reduce power consumption of UE.
ZTE RAN equipment supports the signaling process of the soft/softer handover that
complies with the 3GPP protocol, macro diversity convergence (soft handover mode) in
the RNC’s FP layer and the Rake convergence (softer handover mode) in the Node B’s
physical layer.
ZTE RAN equipment supports the implementation of 'RL addition' and the
implementation of RRC message “Active Set update” simultaneously at the soft hander
over procedure to improve the efficiency. This procedure will be available when the
hander over is intra-RNC and inter-NodeB handover.
2.1.2 ZWF21-03-002 Intra-Frequency Hard Handover
This feature is the supplement of soft handover. When soft handover cannot be realized
in neighboring cell s of intra-frequency for some reasons, intra-frequency hard handover
can guarantee service continuity.
Hard handover is a typical handover mechanism in which a UE has to disconnect the link
with the original cell (that is, new and original links do not co-exist in UE) before setting
up a link (synchronization) with the new cell. Soft/softer handover has more advantages
than hard handover. Hence, soft/softer handover has the higher priority than the hard
handover in the intra-frequency. The hard handover will not be chosen unless the
soft/softer handover doesn’t work

Handover Control
2.1.3 ZWF21-03-003 Inter-Frequency Hard Handover
This feature supports the handover of UE in inter-frequency cells. It is applied to maintain

communication continuity when moving in inter-frequency cells and properly allocate the
load in different frequency layers for the UTRAN.
The inter-frequency hard handover means a UE in dedicated connecting state is handed

over from a cell on one frequency point of UTRAN to another cell on another frequency
point. The factors triggering inter-frequency hard handover include radio quality, load,
and moving speed of the UE.
ZTE RAN equipment supports the signaling procedures of the inter-frequency hard
handover that complies with the 3GPP protocol. Handover may occur in inter-frequency
cells of the same Node B and also in inter-frequency cells of different Node Bs.
2.1.4 ZWF21-03-004 Inter-RAT Mobility
This feature supports inter-RAT handover of a UE in the Cell_DCH state, and it is applied
to maintain communication continuity when moving in inter-RAT cells and properly
allocate load between 3G and 2G for UTRAN.
Inter-RAT handover means a UE in Cell_DCH state changes the current access mode
and continues service in another RAN because of moving or load balance (networks here
only refer to WCDMA and GSM). This function requires UE to support both WCDMA and
GSM, and moreover, the GSM also needs to offer related functions to support the
inter-RAT handover.
The inter-RAT handover, supported by ZTE RAN equipment, works as follows:
 Support inter-RAT handover of CS voice service from RAN to GSM
 Support inter-RAT handover of CS voice service from GSM to RAN
 Support cell change of PS data service from RAN to GSM
 Support re-access of PS data service from GSM to RAN
The inter-RAT handover in connected mode accompanies the inter-RAT relocation. In

the case of the handover of concurrent CS voice and PS data service from WCDMA to

Handover Control
GSM, it first hands over the CS service to GSM, and the RNC releases the lu interface
connection in the PS domain upon receiving the context request message from the CN.
2.1.5 ZWF21-03-006 Inter-RNC Handover with Iur Support
This feature supports maintaining communication continuity in the case of a UE in

Cell_DCH state moving among inter-RNC cells.
ZTE RAN equipment supports the 3GPP standard Iur interface and can configure the Iur
interface between different RNCs to support that a UE maintains the original connection
of the Iu interface with the CN when handing over in the coverage areas of different
RNCs. And there is no need to trigger the SRNS relocation to build a new Iu connection,
to reduce the effects of SRNS relocation on service quality.
ZTE RAN equipment supports the soft handover and the hard handover of the cross-Iur
interface. The Soft handover of the cross-Iur interface is beneficial to realize the
seamless handover in the cross area of RNC coverage, and utilize macro diversity gain
to provide better communication quality. The cross-Iur interface hard handover is
beneficial to reduce sudden interruption of service caused by a Iu connection changing
during the SRNS relocation. After the success of the handover, if the UE is totally in the
coverage of the DRNC and no other radio link is in the SRNC, SRNC will trigger the
relocation process after the delay time related to the service is configured in background.
2.1.6 ZWF21-03-008 Directed Signaling Connection Re-establishment
This feature supports maintaining communication continuity in the case of a UE in

Cell_FACH or URA_PCH/CELL_PCH state moving among inter-RNC cells.
Directed Signaling Connection Re-establishment (DSCR) means when receiving the Cell
Update or URA Update request from the UE, the DRNC/SRNC will release the UE's RRC
connection directly due to Directed Signaling Connection Re-establishment (DSCR).
According to the 3GPP protocol, when receiving the message of RRC connection
release with the reason of Directed Signaling Connection Re-establishment, UE will redo
the connection setup with SGSN immediately while going back to Idle status to recover
data service rapidly.

Handover Control
In the case of a UE moving among different RNCs, for the Cell_FACH or the
URA_PCH/CELL_PCH state, the 3GPP protocol defines DSCR, SRNS relocation and
inter-Iur interface, and among them, the process of DSCR is the simplest and it doesn’t
affect user experience. When different vendors configure the Iur interface, DSCR is
beneficial to avoid interconnection problems.
ZTE RAN equipment also supports the DSCR procedure initiated by UE in Cell_DCH
state and with ongoing service to support the interoperation with the RNC which cannot
support the SRNS relocation procedure.
2.1.7 ZWF21-03-009 Coverage Based Handover
This feature supports utilizing the measurement report to determine the quality of the
radio link and thus to perform the handover to guarantee the service quality of the user in
the case of changing network coverage conditions.
When a UE moves or the coverage condition changes, it is necessary to pay more

attention to the triggering time of the handover. A too early or too late handover will
cause call drop and even service interruption. ZTE RAN equipment supports controlling
the UE to perform the intra-frequency, the inter-frequency and the inter-RAT
measurement. 3GPP protocol defines and judges the radio link quality of the UE
according to the measurement result of the UE periodic or event triggered report to
trigger various handovers which are as follows:
 ZWF21-03-001 Soft/Softer Handover

According to the neighboring cell list of intra-frequency configured in background,
the RNC initiates intra-frequency measurement control for the UE and decides
whether to set up connection in new cells with high radio quality or deletes
connection in cells with low radio quality according to the intra-frequency
measurement result reported by the UE.
The RNC also can control the UE so that UE can actively detect and report the radio
quality of intra-frequency cells besides intra-frequency cells configured by the RNC,
and initiates the handover when handover conditions are satisfied.
 ZWF21-03-002 Intra-Frequency Hard Handover

When soft and softer handover cannot be initiated, the RNC can initiate an

Handover Control
intra-frequency hard handover according to the intra-frequency measurement result

reported by the UE.
 ZWF21-03-003 Inter-Frequency Hard Handover

According to the neighboring cell list of inter-frequency configured in background,
the RNC initiates the inter-frequency measurement control for the UE and decides
whether to handover the UE to cells with high radio quality according to the
inter-frequency measurement result reported by the UE.
 ZWF21-03-004 Inter-RAT Handover

According to the neighboring cell list of inter-RAT configured in background, the
RNC initiates the inter-RAT measurement control for the UE and decides whether to
handover the UE to other system with high radio quality according to the
measurement result reported by the UE.
ZTE RAN equipment supports configuring different handover parameters for CS and PS
service. Inter-system and inter-frequency handover based on coverage is allowed to be
disabled separately for traffic.
2.1.8 ZWF21-03-010 Compressed Mode
This feature supports that non-double-receiver WCDMA terminals can initiate the
inter-frequency or the inter-RAT measurement in the process of service, hence triggering
inter-frequency or inter-RAT handover is supported.
For non-double-receiver WCDMA terminals, it is impossible to receive radio signals of

different frequencies at the same time. So it is necessary for the inter-frequency and the
inter-RAT measurement to adopt compressed mode. In the process of sending and
receiving, part of timeslots are used not for the data transmission but for the quality
measurement of other UMTS or GSM frequency signals.
Two types of compressed mode policies supported by ZTE RAN equipment are as
follows:
 Halving of Spreading Factor

By halving the SF, the air interface bandwidth can be increased so that some
timeslots in one radio frame can be specially assigned for the

Handover Control
inter-frequency/inter-RAT measurement and others for the data transmission. This

transmission strategy is generally used in services which raise high requirements
for the delay and the guarantee of the minimum data rate.
 Higher Layer Scheduling

The higher layer adjusts and controls the data transmission rate. Some timeslots in
a radio frame can be specially assigned for the inter-frequency/inter-RAT
measurement and others for the data transmission while the air interface bandwidth
remains unchanged. This strategy is generally used for non-realtime services with
low requirements for delay, for example, I/B-type PS data services.
When the RRM handover algorithm decides that it is necessary to initiate the
inter-frequency or the inter-RAT measurement, ZTE RAN equipment will decide whether
to initiate compressed mode according to the UE ability and configure different
parameters of the compressed mode according to the inter-frequency or the inter-RAT
measurement.
2.1.9 ZWF21-03-011 Neighboring Cells Priorities
This feature can support configuring different priorities for different cells in neighboring
cell list according to the network coverage condition or operators’ requirements. It
makes a UE hand over to an neighboring cell of high priority at a higher success rate to
improve the handover performance of the system.
ZTE RAN equipment offers two types of cell priority policies.
Firstly, neighboring cell s can be configured based on UE state. So the neighboring cell
list used for reselection in the non-dedicated state and that used for handover in the
dedicated state can be separately configured. A UE in the non-dedicated state only
receives the neighboring cell information of one cell, while a UE in the dedicated state
receives the union of neighboring cell list of multiple cells in macro diversity. But a UE
can only receive a maximum of 32 intra-frequency neighboring cell s, 32 inter-frequency
neighboring cell s and 32 inter-RAT neighboring cell s respectively.
Secondly, neighboring cell s are set with different priorities in the RNC to facilitate the
RNC to adjust the neighboring cell list when the number of neighboring cell s in active
set exceeds 32. The priority of each cell in the neighboring cell list is determined on the

Handover Control
basis of network planning and optimization. The priority helps the RNC to select better
monitored set for UE to facilitate the improvement of measurement and the handover
performance of the UE.
2.1.10 ZWF21-03-020 SRNS Relocation
This feature supports that a UE in the Cell_DCH state transfers service to a new RNC
when moving among adjacent RNC cells:
 An RNC without Iur interface: maintain continuous service through SRNS

relocation
 An RNC with Iur interface: after the handover of inter-Iur interface, timely
trigger the SRNS relocation to reduce the transmission resource consumption
at the Iur interface
The SRNS relocation transfers the Iu connection for a UE from one RNC to another. ZTE
RAN equipment supports the SRNS relocation with UE involved or not involved:
 SRNS Relocation with UE involved

In the process of the SRNS relocation, the handover in air interface is a hard
handover and the target RNC at the same time needs to set up a new radio link.
This relocation does not need Iur interface.
 SRNS Relocation with UE not involved

There must be Iur interface in RNCs. Firstly a UE is handed over to DRNC through
the Iur interface, and builds a new radio link in the DRNC. SRNC, DRNC and CN
exchange information and achieve the Iu connection migration with UE not involved.
Therefore the connection continuity of the air interface is maintained so as to reduce
the service interruption during the handover and make the user experience better.
According to the service types established by the UE, the SRNC relocation can occur in
the CS domain, the PS domain or in both domains. Relocation with UE involved
generally accompanies hard handover, and the triggering condition is controlled by the
RRM handover algorithm. A deferred relocation with UE not involved occurs under the
condition that the inter-Iur handover is completed and there's no radio connection

Handover Control
between the SRNC and the UE. ZTE RAN equipment supports configuring different time
delay for the CS and PS service:
 For CS services, the delay can be configured longer in order to reduce the
sudden call interruption caused by the Iu connection migration during the
SRNS relocation, which provides better service quality.
 For PS services, the delay can be configured shorter to initiate the relocation
as soon as possible, avoiding the Iur bandwidth consumption.
2.2 License Control
Table 2-1 License Control List
License Configured Sales

Feature ID Feature Name
Control Item NE Unit
ZWF21-03-001 Soft/Softer Handover None None None
Intra-Frequency Hard
ZWF21-03-002 None None None
Handover
Inter-Frequency Hard
Handover
ZWF21-03-004 Inter-RAT Mobility None None None
Inter-RNC Handover
with Iur Support
Directed Signaling
ZWF21-03-008 Connection None None None
Re-establishment
Coverage Based
Handover
ZWF21-03-010 Compressed Mode None None None
Neighboring Cells
Priorities
ZWF21-03-020 SRNS Relocation None None None

Handover Control
2.3 Correlation with Other Features
1. Required Features
None
2. Mutually Exclusive Features
None
3. Affected Features
ZWF21-03-012 Transmitted Power Based Handover
ZWF21-03-013 Quality Based Handover
ZWF21-03-021 Hierarchical Cell Structures
ZWF21-03-022 IMSI based Handover
ZWF21-03-023 PS handover with GSM
ZWF21-03-024 DTM Handover with GSM
ZWF21-03-025 NACC
ZWF21-03-026 Target cell Load based inter-RAT HO
ZWF21-03-050 Handover Optimization in Weak Coverage
ZWF21-03-110 Handover with LTE
ZWF21-05-022 Service-Based Handover

Handover Control
3 Technical Description
3.1 ZWF21-03-009 Coverage Based Handover
Coverage Based Handover in the ZTE network includes intra-frequency handover,

inter-frequency handover, and inter-RAT handover. To ensure communication continuity,
the RNC hands over a UE to the most appropriate serving cell based on the
measurement results of the signaling quality of the P-CPICH channel.
For details about the handover strategy, refer to the following chapters respectively:
3.2 ZWF21-03-001 Soft/Softer Handover;
3.3 ZWF21-03-002 Intra-Frequency Hard Handover;
3.4 ZWF21-03-003 Inter-Frequency Hard Handover;
3.5 ZWF21-03-004 Inter-RAT Mobility.
3.2 ZWF21-03-001 Soft/Softer Handover
The soft and softer handover are both a handover performed among the cells of the
same frequency in UTRAN, which are all referred to as the intra-frequency handover in
this chapter if there is no special description.
The intra-frequency handover is a measurement-based handover. The intra-frequency

measurement contains the measurement for the cells in the active set, the measurement
for the cells in a monitored set and the measurement for the cells in a detected set.
Where,
The active set means a set of cells that have been established a radio connection with
the UE.

Handover Control
The monitored set means a set of cells which are not included in the active set, but are
sent to the UE in the measurement control message and need to be measured by the
UE.
The detected set means a set of cells which are neither in the active set nor in the
monitored set, but need to be detected by the UE.
3.2.1 Intra-Frequency Measurement
Intra-frequency measurements are applicable to the measurements to the signal quality

of intra-frequency cells. ZTE RAN only supports event-triggered reporting. The
event-triggered reporting is that the UE checks whether the intra-frequency triggering
events are fulfilled in accordance with the measurement results of the P-CPICH quality of
intra-frequency neighboring cells. If yes, the UE reports the intra-frequency events
(including event ID and target cell) to the RNC.
3GPP has defined a group of intra-frequency measurement events as follows. If the

defined condition is fulfilled, the UE will report the corresponding event to the RNC.
Event 1A: The quality of a cell outside the active set ameliorates and enters the reporting
range. It can be used for adding cells to the active set.
Event 1B: The quality of a cell in the active set deteriorates and leaves the reporting
range. It can be used for deleting cells from the active set.
Event 1C: The quality of a cell in the non-active set is better than that of a cell in the
active set. It can be used for replacing the cell with bad quality in the active set.
Event 1D: The best cell changes. It can be used for adding cells to the active set,
replacing the cell with bad quality in the active set, intra-frequency hard handover and
inter-frequency load balance.
Event 1E: A Primary CPICH becomes better than an absolute threshold. It can be used
for switching channel type.
Event 1F: A Primary CPICH becomes worse than an absolute threshold. It can be used
for switching channel type.

Handover Control
Where, event 1A~1D is the basis of triggering an intra-frequency handover, described in

this text. For the details about the usage of events 1E and 1F, refer to ZTE UMTS
HSDPA Introduction Feature Guide.
3.2.1.1 Measurement Setup
Intra-frequency measurement parameters are configured for the UE and intra-frequency

measurements are initiated through the measurement control message if either of the
following conditions is met:
 The UE enters CELL_DCH state after an RRC connection is set up.
 State transition from CELL_FACH to CELL_DCH.
 Relocation to the current RNC from other systems or RNCs.
An intra-frequency measurement is set up again after an intra-system hard handover

(including intra- or inter-frequency hard handover).
3.2.1.1.1 Optimization of Measurement Setup Occasion
To start intra-frequency measurements in a timely manner for a UE newly entering

CELL_DCH state, and reduce the number of intra-frequency Measurement Control
messages sent in the RRC stage, this feature is introduced. The occasion of sending an
intra-frequency Measurement Control message is delayed from the time when RRC
connection setup is completed to the time when RAB setup is completed through the
intra-frequency measurement reporting criteria for a UE in CELL_DCH state broadcasted
in SIB11.
The intra-frequency measurement reporting criteria for CELL_DCH state include events
1A and 1D only, and is sent through the optional element “Reporting information for state
CELL_DCH” broadcasted in SIB11. Whether to send the criteria is controlled by the
parameter UExtCelInfoFDD.rptforDCHinSIB.
Assume that UExtCelInfoFDD.rptforDCHinSIB is set to “1: Yes”,
 No intra-frequency handover occurs after RRC connection setup is completed

Handover Control
If balancing occurs in the RRC stage or both the RNC and UE support Deferred
SIB11/12, and UE defers reading SIB11/12 when an RRC connection is established,
the RNC sends an intra-frequency Measurement Control message after RRC
connection setup is completed.
Otherwise, the RNC sends an intra-frequency Measurement Control message after

RAB setup is completed.
 An Intra-frequency handover occurs after RRC connection setup is completed
Before an intra-frequency Measurement Control message is sent, if the UE reports

event 1A or 1D, and the StateMode of the target cell is “1: handover only” or “2: cell
selection/reselection and handover”, a soft handover is performed, and the RNC
sends an intra-frequency Measurement Control message after active-set update is
completed.
3.2.1.2 Measurement Modification
After an intra-frequency measurement is set up, the measurement can be modified if

either of the following conditions is met:
 If neighboring cells are changed after the soft handover, the neighboring cell list
needs to be updated by modifying the measurement control message.
 If the intra-frequency measurement parameters are changed after changing the
best cell (triggered by event 1D), the intra-frequency measurement parameters
need to be updated by modifying the measurement control message.
 In the case of adding or deleting a service, if the handover parameters of a single
service and concurrent services are different, the intra-frequency measurement
parameters need to be updated by modifying the measurement control message.
3.2.1.3 Measurement Deletion
An intra-frequency measurement should be deleted if any of the following conditions is

met:
 If an abnormal intra-frequency measurement report (for example, a nonexistent

Handover Control
measurement task in the RNC) is received, the corresponding intra-frequency
measurement should be released.
 If a relocation triggered by a soft handover decision is made, the corresponding
intra-frequency measurement should be released.
The RNC records the timestamp when the measurement of a certain ID is deleted and
the measurement information is released. If the RNC receives the measurement report
with the measurement ID that has been deleted afterwards, it directly discards the
measurement report, and checks the time difference between the current time and the
time to release the measurement. If the time difference exceeds a threshold (indicated by
the parameter URncFunction.TResndMeaCtrlRel), the RNC performs measurement
deletion again.
3.2.1.4 Parameter Configuration
 Neighboring cell configuration
During the neighboring cells configuration, the neighboring cell list used for
reselection in non-CELL_DCH state and that is used for handover in CELL_DCH
state can be configured separately, which can be indicated by the neighboring cell
configuration state for neighboring cells. For intra-frequency neighboring cells, it is
indicated by UUtranRelation.StateMode.
The neighboring cells, which would be sent to the UE in the measurement

information of the system broadcast and the measurement control message used in
handovers, are chosen according to the configuration state.
 Handover parameter configuration under macro diversity
All measurement parameters are obtained based on cells. In the case of macro
diversity, the measurement parameters configured in the best cell are used as
handover parameters. If the best cell is changed, the measurement parameters
should be updated simultaneously.
 Multiple sets of handover parameter configurations

Handover Control
Intra-frequency handover parameters can be independently configured in

accordance with the application scenarios, measurement quantities, measurement
reporting criteria and service bearer types. Multiple sets of measurement
parameters are needed for different purposes. The details are described as follows:
Factor Application Scenario Parameter
Application Outdoor Scene UIntraMeasProfile.intialHoCelSelSc
Scenario High-Mobility Outdoor ene
Scene
UUtranCellFDD.HoCelSelScene
Indoor Scene
(Note: These two parameters are
Subway/ tunnel Scene
only used for displaying the
scenario, not for indexing handover
parameters, which refers to the
following “Handover parameter
indexing principle”.)
Measuremen PCPICH Ec/No UUtranCellFDD.IntraMeasQuan

t quantity PCPICH RSCP
Measuremen Event-triggered reporting None

t reporting Periodic reporting (Event-triggered reporting is used
criterion (nonsupport) by default. Whether to apply
Detected set tracing detected set tracing, refer to 3.2.6.2
Detected Set Tracing.)
Service RT RAB Including Voice UIntraMeasSrvSpec.srvCategory

bearer type RT RAB Excluding Voice
on
Single NRT on DL
DCH/UL DCH
Single NRT RAB on DL
HS-DSCH/UL DCH
HS-DSCH/UL E-DCH
All Multi-NRT RAB on DL
DCH/UL DCH
Multi-NRT RAB, HSPA is
Involved and only DCHs
are Used in UL
Involved and E-DCH is
Used in UL

Handover Control

Multi RAB Including CS
and PS
Not Related to Service
Type (used for detected
set measurement)
Note:
i. If the concurrent services contain CS and PS services, the handover

parameters are indexed to “Multi RAB including CS and PS”.
ii. If the concurrent services only contain non-CS RT services, the handover
parameters are indexed to “RT RAB Excluding Voice”.
iii. If both of the above two conditions are fulfilled, the handover parameters are
indexed to “Multi RAB including CS and PS”.
 Handover parameter indexing principle
To modify and optimize parameters more easily, intra-frequency handover

parameters are used based on profile and index. For the detailed parameter
indexing principle, see Figure 3-1:

Handover Control
Figure 3-1 Parameter Indexing Principle of Intra-frequency Handover
UUtranCellFDD
ref1UIntraMeasProfile
UIntraMeasProfile
UIntraMeasSrvSpec UIntraMeasNoSrvSpec
intraMeasQuan intraMeasQuan
UIntraEcNoEvMeas UIntraRscpEvMeas
UIntraEcNoEvMeasForD UIntraRscpEvMeasForD
srvCategory srvCategory
intraMeasCfgNo intraMeasCfgNo intraMeasCfgNo intraMeasCfgNo
1. First, you can obtain an intra-frequency configuration set UIntraMeasProfile by

matching UIntraMeasProfile.profileId with UUtranCellFDD.ref1UintraMeasProfile.
Then you can obtain the measurement object in the next level in accordance with
the reporting criterion currently used by the UE in this configuration set. If the
measurement reporting criterion is event-triggered reporting, you can obtain the
next-level measurement object from the UIntraMeasSrvSpec object. If the
measurement reporting criterion is detected set tracing, you can obtain the
next-level measurement object from the UIntraMeasNoSrvSpec object.
2. If the measurement object obtained in Step 1 is UIntraMeasSrvSpec, you can

obtain the current measurement object (UIntraEcNoEvMeas or UIntraRscpEvMeas)
in accordance with the measurement quantity UUtranCellFDD.IntraMeasQuan.
Then, you can obtain IntraMeasCfgNo (intra-frequency measurement configuration
number) in accordance with the service type UIntraMeasSrvSpec.srvCategory. If
the measurement object obtained in Step 1 is UIntraMeasNoSrvSpec, you can
obtain the current measurement object and IntraMeasCfgNo (intra-frequency
measurement configuration number) in accordance with the measurement quantity
UUtranCellFDD.IntraMeasQuan. Finally, you can obtain the intra-frequency

Handover Control
handover measurement parameters of the current application scenario and service

through the indexing to IntraMeasCfgNo. The details are described as follows:
i. If the event-triggered reporting is used, and the measurement quantity is

P-CPICH Ec/No, you can refer to the following table to obtain the parameters
that are matched with IntraMeasCfgNo and associated with
UIntraEcNoEvMeas.IntraMeasCfgNo from the UIntraEcNoEvMeas object.
GUI Name Parameter
Intra-frequency Event Identity UIntraEcNoEvMeas.MeaEvtId
Event Number of Intra-frequency UIntraEcNoEvMeas.MeasEvtNum

Measurement
Filter Coefficient UIntraEcNoEvMeas.FilterCoeff
Weight for Event 1A/1B UIntraEcNoEvMeas.W
Hysteresis UIntraEcNoEvMeas.Hysteresis
Reporting Range Constant for Event UIntraEcNoEvMeas.RptRange

1A/1B
Time To Trigger UIntraEcNoEvMeas.TrigTime
Amount of Reporting for Event UIntraEcNoEvMeas.EvtRptAmount

1A/1B/1C/1J
Reporting Interval for Event UIntraEcNoEvMeas.EvtRptInterval

1A/1B/1C/1J
Replacement Activation Threshold for UIntraEcNoEvMeas.RplcActThr

Event 1C and 1J
Reporting Deactivation Threshold for UIntraEcNoEvMeas.RptDeactThr

Event 1A
ii. If the event-triggered reporting is used, and the measurement quantity is

P-CPICH RSCP, you can refer to the following table to obtain the parameters
that are matched with IntraMeasCfgNo and associated with
UIntraRscpEvMeas.IntraMeasCfgNo from the UIntraRscpEvMeas object.
GUI Name Parameter
Intra-frequency Event Identity UIntraRscpEvMeas.MeaEvtId
Event Number of Intra-frequency UIntraRscpEvMeas.MeasEvtNum

Measurement
Filter Coefficient UIntraRscpEvMeas.FilterCoeff

Handover Control
GUI Name Parameter

Weight for Event 1A/1B UIntraRscpEvMeas.W
Hysteresis UIntraRscpEvMeas.Hysteresis
Reporting Range Constant for Event UIntraRscpEvMeas.RptRange

1A/1B
Time To Trigger UIntraRscpEvMeas.TrigTime
Amount of Reporting for Event UIntraRscpEvMeas.EvtRptAmount

1A/1B/1C/1J
Reporting Interval for Event UIntraRscpEvMeas.EvtRptInterval

1A/1B/1C/1J
Replacement Activation Threshold for UIntraRscpEvMeas.RplcActThr

Event 1C and 1J
Reporting Deactivation Threshold for UIntraRscpEvMeas.RptDeactThr

Event 1A
iii. If the detected set tracing is used, and the measurement quantity is P-CPICH
Ec/No, you can refer to the following table to obtain the parameters that are
matched with IntraMeasCfgNo and associated with
UIntraEcNoEvMeasForD.IntraMeasCfgNo from the UIntraEcNoEvMeasForD
object.
GUI Name Parameter
Filter Coefficient UIntraEcNoEvMeasForD.FilterCoeff
Weight for Event 1A/1B UIntraEcNoEvMeasForD.W
Hysteresis UIntraEcNoEvMeasForD.Hysteresis
Reporting Range Constant for UIntraEcNoEvMeasForD.RptRange

Event 1A/1B
Time To Trigger UIntraEcNoEvMeasForD.TrigTime
Amount of Reporting for Event UIntraEcNoEvMeasForD.EvtRptAmount

1A/1B/1C/1J
Reporting Interval for Event UIntraEcNoEvMeasForD.EvtRptInterval

1A/1B/1C/1J
Reporting Deactivation UIntraEcNoEvMeasForD.RptDeactThr

Threshold for Event 1A
iv. If the detected set tracing is used, and the measurement quantity is P-CPICH
RSCP, you can refer to the following table to obtain the parameters that are

Handover Control
matched with IntraMeasCfgNo and associated with

UIntraRscpEvMeasForD.IntraMeasCfgNo from the UIntraRscpEvMeasForD
object.
GUI Name Parameter
Filter Coefficient UIntraRscpEvMeasForD.FilterCoeff
Weight for Event 1A/1B UIntraRscpEvMeasForD.W
Hysteresis UIntraRscpEvMeasForD.Hysteresis
Reporting Range Constant for UIntraRscpEvMeasForD.RptRange

Event 1A/1B
Time To Trigger UIntraRscpEvMeasForD.TrigTime
Amount of Reporting for Event UIntraRscpEvMeasForD.EvtRptAmount

1A/1B/1C/1J
Reporting Interval for Event UIntraRscpEvMeasForD.EvtRptInterval

1A/1B/1C/1J
Reporting Deactivation UIntraRscpEvMeasForD.RptDeactThr

Threshold for Event 1A
Where,
MeasEvtNum
(UIntraEcNoEvMeas.MeasEvtNum/UIntraRscpEvMeas.MeasEvtNum) and
MeaEvtId (UIntraEcNoEvMeas.MeaEvtId/UIntraRscpEvMeas.MeaEvtId) control
how many events can be configured during the intra-frequency measurement, and
which events should be configured. MeaEvtId is defined as an array whose
dimension number is MeasEvtNum. The MeasEvtNum is configured up to seven
because there are a total of seven events (1A, 1B, 1C, 1D, 1E, 1F, 1J) in the
intra-frequency measurement.
3.2.2 The Number of Configured Intra-frequency Neighboring Cells is Up

to 40
In the current network, 31 intra-frequency neighboring cells cannot meet the need any
more for network deployment and network planning, so this function is introduced to
extend the configuration for intra-frequency neighboring cells. At most 40 intra-frequency
neighboring cells for a serving cell can be configured, and all of these configured

Handover Control
neighboring cells can be performed the detected set handover. It increases the success
rate of intra-frequency handover.
3.2.3 Intra-frequency Event Triggering
3.2.3.1 Measurement Result Filtering
To avoid measurement fluctuation during intra-frequency measurements, the UE needs

to perform layer-3 filtering to the measurement results. Then, the UE determines whether
an event is triggered in accordance with the filtered measurement value, and reports the
measurement results to the RNC. The filtering formula is as follows:
Fn  (1  a)  Fn 1  a  M n
Where,
Fn-1 is the filtered result last time.
Fn is the filtered result this time.
Mn is the current measurement result.
(k/2)
a = 1/2 is the filter coefficient calculated based on the filter factor k, k is obtained from
the parameter filterCoeff in the record associated with a certain configuration number
based on the principles described in 3.2.1.4 Parameter Configuration.
3.2.3.2 CIO Configuration Strategy
The Cell Individual Offset (CIO) defined by 3GPP is used to control the difficulty level of
event triggering. The tendency of handover can also be controlled by the CIO in actual
scenarios.
 If the target cell is not the best cell in the active set, the principles for obtaining the
CIO are as follows:
 If the target cell is a neighboring cell of the best cell, the CIO is obtained from
the CellIndivOffset in the adjacent relationship configuration of the best cell.

Handover Control
 If the target cell is a neighboring cell of the cells other than the best cell in the
active set, each CellIndivOffseti in the adjacent relationship configuration of
those cells in the active set is obtained first, and the CIO is the minimum
absolute value among CellIndivOffseti, i=1 ... N. Where, N is the number of
cells in the active set that have the neighbor relation with the target cell.
 If the target cell is not a neighboring cell of any cell in the active set, CIO is
zero.
Where, CellIndivOffset is obtained from the parameter

UUtranRelation.CellIndivOffset.
 If the target cell is the best cell in the active set, then
CIO is obtained from the parameter UUtranCellFDD.CellIndividualOffset.
If the best cell and the output CIO value change, the RNC informs UEs to update the
CIO.
3.2.3.3 Time-To-Trigger Mechanism Used to Control Event Report
For the intra-frequency events judgment, to avoid the intra-frequency event misreport
due to the fluctuation of radio quality, if an evaluated cell meets the reporting range or
threshold of a certain event and the condition must be met for a time (Timetotrigger), the
event can be really triggered. Where, Timetotrigger is obtained from the parameter
TrigTime in the record associated with a certain configuration number based on the
principles described in 3.2.1.4 Parameter Configuration.
For example, if a cell meets the reporting range of event 1A, the UE only reports event
1A only if the cell quality meets this reporting range condition for a Timetotrigger time ,
see Figure 3-2.

Handover Control
Figure 3-2 Time-To-Trigger mechanism
Measurement
quantity
RptRange
P CPICH 1 [MAX_INTRA_
MEAS_EVENT]
P CPICH 2
P CPICH 3 TrigTime[MAX_INTRA_MEAS_EVENT]
Reporting Time
event 1A
3.2.3.4 Event 1A Triggering
Event 1A means the quality of a certain cell outside the active set ameliorates. Upon
receiving event 1A, the RNC adds the corresponding target cell into the active set to
enhance the gain of macro diversity.
When the cell meets the conditions in the following formula, the UE reports event 1A to
the RNC:
 NA 
10  LogM New  CIONew  W  10  Log Mi   (1 W)  10  LogM B est  (R1a  H1a /2)
 i1 
Where,
R1a is the reporting range of event 1A, used to control the extent of difficulty in adding a
cell into the active set. It is obtained from the parameter RptRange in the record
associated with a certain configuration number based on the principles described in
3.2.1.4 Parameter Configuration.
H1a is the reporting hysteresis of event 1A, used to control the extent of difficulty in
adding a cell into the active set. It is obtained from the parameter Hysteresis in the record

Handover Control

MNew is the measurement value of the to-be-evaluated cell outside the active set.
CIONew is the offset of the to-be-evaluated cell outside the active set.
Mi is the mean measurement value of the cells other than the best cell in the active set.
NA is the number of cells other than the best cell in the active set.
MBest is the measurement value of the best cell in the active set.
W is the weight of the best cell to the rest cells in the active set in evaluation standards. It
is obtained from the parameter W in the record associated with a certain configuration
number based on the principles described in 3.2.1.4 Parameter Configuration.
From the formula, it can be concluded that the probability of triggering event 1A can be
increased by either increasing R1a or decreasing H1a. Otherwise, probability of triggering
event 1A can be reduced.
Moreover, event 1A supports event-triggered periodic reporting, that is, once the
reporting range of quality standards of event 1A is met, the UE reports event 1A
periodically (EvtRptInterval) until reporting conditions are not met or the reporting times
reach the maximum allowed times (EvtRptAmount). Where, EvtRptInterval and
EvtRptAmount are obtained from the record associated with a certain configuration
There is a restriction on the number of radio links in active set, so event 1A will not be
reported once the number of cells in the active set reaches the threshold (RptDeactThr).
RptDeactThr is obtained from the record associated with a certain configuration number
3.2.3.5 Event 1B Triggering
Event 1B indicates the quality deterioration of a certain cell in the active set. Upon
receiving event 1B, the RNC may delete the cell from the active set.

Handover Control
When the cell meets the conditions in the following formula, the UE reports event 1B to
the RNC:
 NA 
10  LogM Old  CIOOld  W  10  Log Mi   (1 W)  10  LogM B est  (R1b  H1b /2)
 i1 
R1b is the reporting range of event 1B, used to control the extent of difficulty in dropping a
cell from the active set. It is obtained from the parameter RptRange in the record
H1b is the reporting hysteresis of event 1B, used to control the extent of difficulty in
dropping a cell from the active set. It is obtained from the parameter Hysteresis in the
record associated with a certain configuration number based on the principles described
in 3.2.1.4 Parameter Configuration.
MOld is the measurement value of the to-be-evaluated cell in the active set.
CIOOld is the offset of the to-be-evaluated cell in active set.
Mi is the mean measurement value of the cells other than the best cell in the active set.
NA is the number of cells other than the best cell in the active set.
MBest is the measurement value of the best cell in the active set.
W is the weight of the best cell to the rest of the cells in the active set in the evaluation
standards. It is obtained from the parameter W in the record associated with a certain
configuration number based on the principles described in 3.2.1.4 Parameter
Configuration.
From the formula, it can be concluded that the probability of triggering event 1B can be
decreased by either increasing R1b or decreasing H1b. Otherwise the probability of
triggering event 1B can be increased.

Handover Control
3.2.3.6 Event 1C Triggering
Event 1C indicates that the quality of a cell outside the active set is better than that of a
cell in the active set. Upon receiving event 1C, the RNC may replace the cell in the active
set with a cell outside the active set to obtain better gain of macro diversity.
When the cell meets the conditions in the following formula, the UE reports event 1C to
the RNC:
10  LogM New  CIONew  10  LogM InA S  CIOInA S  H1c /2
H1c is the reporting hysteresis of event 1C, used to control the extent of difficulty in
replacing a cell in the active set. It is obtained from the parameter Hysteresis in the
MNew is the measurement value of the to-be-evaluated cell outside the active set.
MInAS is the cell with poorest quality in the active set.
CIONew is the offset of the to-be-evaluated cell outside the active set.
CIOInAS is the offset of cell with poorest quality in the active set.
From the formula, it can be concluded that the probability of triggering event 1C can be
decreased by increasing H1c. Otherwise the probability of triggering event 1C can be
increased.
Moreover, event 1C supports event-triggered periodic reporting, that is, once the
reporting range of quality standards of event 1C is met, the UE reports event 1C
periodically (EvtRptInterval) until reporting conditions are not met or the reporting times
reach the maximum allowed times (EvtRptAmount). Where, EvtRptInterval and
EvtRptAmount are obtained from the record associated with a certain configuration
To ensure the gain of macro diversity, the reporting of event 1C is only allowed when the
number of cells in the active set reaches a certain threshold (RplcActThr). RplcActThr is

Handover Control
obtained from the record associated with a certain configuration number based on the
3.2.3.7 Event 1D Triggering
Event 1D indicates that the quality of a cell inside or outside the current active set is
better than the best cell in the current active set, that is, the best cell changes in the
active set. The following operations can be triggered upon the reception of event 1D:
 A cell is added into the active set (The cell outside the active set reports event 1D
and the number of links in the active set does not reach the maximum limit).
 The cell with poor quality in the active set is replaced (The cell outside the active set
reports event 1D but the number of links in the active set reaches the maximum
limit).
 The serving cell changes.
When the cell meets the conditions in the following formula, the UE reports event 1D to
the RNC:
10 LogMNotBest  CIONotBest  10 LogMBest  CIOBest  H1d/2
MNotBest is the measurement value of the to-be-evaluated cell inside or outside the active
set.
CIONotBest is the offset of the to-be-evaluated cell inside the active set or outside the
active set.
CIOBest is the offset of the to-be-evaluated cell in the active set.
MBest is the measurement value of the to-be-evaluated cell in the active set.
H1d is event 1D reporting hysteresis. It is obtained from the parameter Hysteresis in the

Handover Control
From the formula, it can be concluded that the probability of triggering event 1D can be
decreased by increasing H1d. Otherwise, the probability of triggering event 1D can be
increased.
Note: In the above formula, whether CIONotBest and CIOBest are used is controlled by the
parameter UExtCelInfoFDD.e1DUseCIOInd. This parameter is introduced for optimizing
the performance of the macro cell and the micro cell networking, the details about it refer
to ZTE UMTS Small Cell Package Feature Guide.
3.2.4 Intra-frequency Handover Decision and Execution
3.2.4.1 Event 1A Processing
 Links are added into the active set if the number of links in the DCH active set is
less than 3. Event 1A will not be processed if the total number of links in the active
set reaches the maximum limit.
 If a link to be added into the active set is rejected in event 1A, the handover
punishment timer (indicated by URncInfo.HoToIntraPenTimer) is initiated, so that
event 1A reported by this rejected cell will not be processed until the timer has
expired.
 If the cell reporting event 1A is the target cell of detected set tracing, no link will be
added into the active set. For details, refer to 3.2.6.2 Detected Set Tracing.
 If the measurement report contains several target cells, the cell with best quality
(EcNo) will be selected as the target cell to be added in the active set.
For adding links into the active set triggered by event 1A, ZTE RAN supports the strategy
of processing the procedures of the Iub interface and Uu interface in parallel, to
accelerate the soft handover and improve user experience.
If the switch URncFunction.ParallelSoftHO is set to “On”, and the cell reporting event 1A
is the cell in SRNC, the Radio Link Setup message of the Iub interface and the Active Set
Update message of the Uu interface are processed in parallel.

Handover Control
3.2.4.2 Event 1B Processing
 The link of the related cell is deleted based on event 1B reported by the UE.
 If the measurement report contains several target cells, the cell with the worst
quality (EcNo) will be selected as the target cell to be deleted from the active set.
3.2.4.3 Event 1C Processing
 A cell in the active set is replaced with a cell outside the active set.
 If a link to be added into the active set is rejected in event 1C, the handover
punishment timer (indicated by URncInfo.HoToIntraPenTimer) is initiated, so that
event 1C reported by this rejected cell will not be processed until the timer has
expired.
 The parallel processing of the Iub and Uu interfaces when adding a radio link in soft
handover is the same as that of event 1A.
3.2.4.4 Event 1D Processing
 If the cell triggering event 1D is an intra-frequency neighboring cell outside the

active set, and if the criterion described in “3.3.1 Intra-Frequency Hard Handover
Scenarios” is fulfilled, the RNC will perform an intra-frequency hard handover.
Otherwise, if the DCH active set is full, event 1D will be processed as event 1C. If
the DCH active set is not full, event 1D will be processed as event 1A. If event 1A or
1C fails due to the admission failure, the RNC will perform an intra-frequency hard
handover.
 If the cell triggering event 1D is in the active set, the best cell in the active set is
changed.
3.2.5 Intra-frequency Event Buffering
If the RNC receives measurement events and discards them in unsteady state, it may
miss handover opportunities, and radio links with good signal quality may be not added

Handover Control
into the active set while radio links with poor signal quality may be still in the active set.
So it needs to cache measurement reports in the buffer in unsteady state and then
dispose of such measurement reports while the UE enters steady state. In unsteady
state, the RNC needs to combine the received measurement reports. The strategy is
described as follows:
Table 3-1 Compressed Mode Parameters List
Events Existing in Buffer
1A 1B 1C 1D
If the
scrambling
code in the
new 1A event
is identical
with that in
the old 1A
event, then The 1A event The 1A event
1A ×
the old 1A is cached. is cached.
event is
replaced by
the new one.
Otherwise,
New the new 1A
measurement event is
report cached.
If the
scrambling
code in the
1B event is
identical with
The old 1B
the existing
The 1B event event is 1B event is
1B one, then the
is cached. replaced by cached
1D event is
the new one.
replaced by
the 1B event.
Otherwise,
the 1B event
is cached.

Handover Control
Events Existing in Buffer
1A 1B 1C 1D
If the
replaced
scrambling
code in the
1C event is
identical with
The old 1C the existing
The 1C event event is one in the 1D
1C ×
is cached. replaced by event, then
the new one. the 1D event
is replaced
by the 1C
event.
Otherwise,
the 1C event
is cached.
If the
scrambling
If scrambling
code in the
code in the
1D event is
1D event is
identical with
identical with
the replaced
the one in
scrambling The old 1D
the 1B event,
The 1D event code in the event is
1D then the 1B
is cached. 1C event, replaced by
event is
then the 1C the new one.
replaced by
event is
the 1D event.
replaced by
Otherwise,
the 1D event.
the 1D event
Otherwise,
is cached.
the 1D event
is cached.

Handover Control
3.2.6 Detected Set Handover and Detected Set Tracing
This chapter only briefly introduces the detected set handover and detected set tracing,
focuses on the measurement procedure. For the details about the events triggering and
execution, refer to ZTE UMTS Neighboring Cell Monitoring Feature Guide.
3.2.6.1 Detected Set Handover
The detected set handover is controlled by the switch UUtranCellFDD.DetSetHoSwch.

This function is introduced for allowing the UE to report the P-CPICH signal quality of the
cells, which are cut off because the number of neighboring cells exceeds 32. This
function prevents calls from being dropped due to the unable soft handover after the
neighboring cells are cut off.
If UUtranCellFDD.DetSetHoSwch is set to “On”, and the number of neighboring cells

exceeds 32, the RNC must send a measurement control message to instruct the UE to
submit the measurement report of the detected set.
If the target cell in the detected set event reported by the UE is a cell in the neighboring
cell reserve list described in 3.9.2 Strategy for Neighboring Cells Exceeding 32, the RNC
processes the cell in the detected set as that in the monitored set. That is, the RNC
determines a handover.
3.2.6.1.1 Related Measurement Procedure of Detected Set Handover
 The strategy of initiating a detected set measurement
If the switch of detected set handover of the best cell

(UUtranCellFDD.DetSetHoSwch) is enabled and there are over 32 neighboring
cells, a detected set measurement is initiated.
The initiation strategy is to set “1A Triggering condition 2” to “Detected set cells and
monitored set cells”, and set “Reporting cell status” to “Report all active set cells +
cells within monitored set and/or detected set on used frequency”, that is,
performing measurement reporting of the active set, monitored set and detected set
concurrently by sharing the same set of handover measurement parameters.

Handover Control
 The strategy of disabling a detected set measurement
If the switch of detected set handover of the best cell

(UUtranCellFDD.DetSetHoSwch) is disabled or there are less than 32 neighboring
cells, the detected set measurement is released.
The disable strategy is to set “1A Triggering condition” to “Monitored set cells” and
set “Reporting cell status” to “Report cells within active set and/or monitored set
cells on used frequency”, that is, only reporting the monitored set instead of the
detected set.
3.2.6.1.2 Related Parameter Configurations
The RNC only performs handovers for the detected set measurement reported by the
neighboring cells exceeding 32. The processing of the measurement report triggered by
these cells is actually consistent with that triggered by the monitored set. Therefore, the
detected set and monitored set share the same set of measurement configurations.
3.2.6.2 Detected Set Tracing
The detected set tracing is used in network planning and optimization to judge whether
there is any neighboring cell that is not configured based on the statistical report. The
purpose of detected set tracing measurement differs from that of handover measurement,
so the measurement parameters used for detected set tracing are separately configured
in the OMCR. The parameters of detected set tracing is irrelevant to service type, which
means all sorts of services will be indexed by “Not Related to Service Type “in service
type (UIntraMeasSrvSpec.srvCategory). For the details about obtaining the parameters,
refer to 3.2.1.4 Parameter Configuration.
3.2.6.2.1 Measurement Procedure of Detected Set Tracing
The measurement of detected set tracing is controlled through the detected set tracing
task in the performance measurement of the OMCR. A detected set measurement is
started after a detected set tracing task is created and initiated if the parameter
ULogicalRnc.NbrCellMonSupInd is set to “1: Supported”.

Handover Control
During the configuration of the measurement control message, “Triggering condition 2” is

set to “Detected set cells”, and “Reporting cell status” is set to “Report cells within
detected set on used frequency”.
The measurement parameters of the detected set are indexed to the cell, and the
parameters of the best cell will be selected in macro diversity state. If the parameters of
the best cell are different from those used by the UE, the measurement information is
modified through the measurement control message.
After the detected set tracing task stops, the detected set tracing is disabled and the
related measurement task is released.
3.2.7 Strategy for Special Scenarios in Intra-frequency Handover
3.2.7.1 Processing of the Rx-Tx Time Difference of a UE in Macro Diversity
When a UE is in macro diversity, the uplink transmitting time of the UE is not adjusted.
The initial downlink channels can be correctly demodulated, but the downlink receiving
time changes along with the movement of the UE or with the drifting of the clock between
Node Bs. Therefore, the downlink receiving time may fall out of the time window of the
UE transmitting time T0 ± 148 chips, and consequently the UE cannot correctly
demodulate one or multiple downlink channels, causing the degradation of UE downlink
quality or even call drop.
For this reason, the 3GPP protocols have defined the UE internal measurement events
6F and 6G for UE Rx-Tx time difference measurement:
 Event 6F: The UE Rx-Tx time difference for a link in the active set is greater than an
absolute threshold.
 Event 6G: The UE Rx-Tx time difference for a link in the active set is less than an
absolute threshold.
The parameter ULogicalRnc.rlRefTimeAjtSw controls the policy of the UE Rx-Tx time

difference in macro diversity.

Handover Control
 If the switch is set to “1:On”, the RNC removes the corresponding link in the active
set when the UE reports a 6F or 6G event (indicating that the downlink receiving
time falls out of the UE transmitting time window).
 If the switch is set to “0: Off”, the function is disabled.
Measurement of the Rx-Tx time difference of a UE in macro diversity:
1. The initiated conditions: When the radio link reference time adjustment switch of the
best cell (ULogicalRnc.rlRefTimeAjtSw) is set to “1: On” and the number of links in
macro diversity changes from one to multiple, the 6F/6G measurement parameters
will be issued to the UE. Where, the UE Rx-Tx time difference reporting threshold in
event 6F/6G is indicated by URlEvtRttUeInt.TxRxTDThres. The period of time is
indicated by URlEvtRttUeInt.TrigTime, during which the event conditions have to be
satisfied before a measurement report is sent.
2. The internal measurement parameters (6F/6G) of the UE are configured per cell
according to the index, and are subject to the parameters of the best cell. First, an
UE internal measurement configuration set UUeIntMeasProfile is obtained by
matching UUeIntMeasProfile.profileId with UUtranCellFDD.refUUeIntMeasProfile.
Then you can obtain the measurement object URlEvtRttUeInt in accordance with
the measurement purpose “UE Rx-Tx Time Difference Event Measurement for RL
Timing Adjustment” currently in this configuration set. Finally, the internal
measurement parameters are obtained from URlEvtRttUeInt. For a UE on which the
internal measurement (6F/6F) function is enabled in macro diversity, if the 6F/6G
event parameters of the best cell are different from the parameters issued to the UE,
the parameter configuration of the UE will be modified through the measurement
control message.
The correspondence between other parameters that need to be filled in the UE

internal measurement control message and OMCR configuration is described as
follows:
GUI Name Parameter
UE internal measurement configuration index URlEvtRttUeInt.ueIntMCfgNo
Measurement report transmission mode URlEvtRttUeInt.MeasRptTrMod
Filter coefficient URlEvtRttUeInt.FilterCoeff

Handover Control
UE internal event identity URlEvtRttUeInt.MeaEvtId
URlEvtRttUeInt.MeasEvtNum
3. When the number of links in macro diversity changes from multiple to one and the
internal measurement function (6F/6G) is enabled on the UE, a release of the
internal measurement will be triggered on the UE.
3.2.7.2 Iub Transmission Bandwidth Limitation Strategy
When a network is constructed, there may be a shortage of Iub transmission resources.

A large number of users cannot access the network because of the access of a small
number of high-speed users. To prevent some individual high-speed users from affecting
the communication quality of a great number of users in the cell, it is necessary to limit
the maximum rate of these high-speed users in the cell.
For the definition of the maximum rates of uplink and downlink DCHs, refer to ZTE UMTS
Dynamic Radio Bearer Control Feature Guide.
In the case of macro diversity, the rate threshold is the minimum of DCH rate threshold of
all cells in the active set and is updated along with the change of the cells in the active
set.
The handover strategy is processed as follows:
For a radio link addition to the active set, the rate limitation is determined when the link is
added. For a radio link deletion from the active set, the rate limitation is determined after
the link is deleted.
 Radio link addition to the active set
If the GBR of a DCH user is higher than the rate limitation of the newly-added
neighboring cell, the RNC does not add the link into the active set. Otherwise, the
RNC adds the link into the active set.
Where, for the concurrent RT services and NRT services, the rate threshold is the
bigger of the two.
 Radio link deletion from the active set

Handover Control
For a DCH user, a radio link is deleted from the macro diversity. After that, if the rate
threshold is changed and the bit rate of the UE is less than the new rate threshold,
the RNC triggers rate is adjusted based on traffic volume.
3.2.7.3 IP Reallocation with LAC/RAC Change
Based on the operator’s requirement on IP restriction in some specific areas, when the
LAC/RAC changes for a UE in connected state, the RNC needs to inform the UE of the
new LAC/RAC, and the UE requests the CN to reallocate an IP address (a restricted one)
for it by initiating an LAU/RAU process. Where, whether to inform the UE of the new
LAC/RAC is controlled by the parameter URncFunction.notifyUeRacChg..
The strategy is as follows:
When the best cell of a UE changes, if either of the LAC and RAC is different between
the new and old best cells, and URncFunction.notifyUeRacChg is set to “1: On”, the RNC
fills CN INFORMATION IE of the Active Set Update or RB Reconfiguration/Transport
Channel Reconfiguration/Physical Channel Reconfiguration message with the latest
LAC/RAC, and sends it to the UE.
Note: This feature is only valid for the scenario that the best cell belongs to the SRNC.
3.2.7.4 Soft Handover between Cells with Different Transport Time Delay Grades
over Iub
3.2.7.4.1 Configuration of Soft Handover between Cells with Different Transport Time Delay
Grades over Iub
For different Iub transport link properties, ZTE networks support different time delay
grade settings. To decrease the probability of an intra-frequency hard handover triggered
by the different transport time delay grades among cells, and improve the user
experience, this feature is introduced. Soft handovers among the intra-RNC cells with
different Iub transport time delay grades (20 ms and 100 ms) are supported.
When the UE reports event 1A, 1C or 1D (triggered by a cell outside of the active set),
and the transport time delay grade of the Node B that the target cell belongs to is

Handover Control
different from that of a cell in the current active set, if all the following conditions are met,
the RNC performs a soft handover to the target cell. Otherwise, an intra-frequency hard
handover is performed.
1. The target cell belongs to the SRNC.
2. No cell in the current active set belongs to the DRNC,
3. URncFunction.sHOforMIubTimeSpt is set to “1: Supported”.
4. The transport time delay grades of the target cell and the cells in the current active
set are 20 ms or 100 ms,
Note: If the transport time delay grades of cells in the active set are different, the relative
parameters are determined in accordance with the highest transport time delay grade to
ensure the combined effect of the active set.
3.2.7.4.2 Macro Diversity Combining Strategy
For better QoS, the RNC considers the strategy of soft handover macro diversity
combining as follows:
1. When the Iub transmission quality between the RNC and connected Node Bs is
similar: For example, if the macro diversity combining time of different UEs is
similar, It is suggested to configure a fixed macro diversity combining time to get
better QoS. The parameters refer to URnluCfg.UlMcrWaitTimeSwi,
URnluCfg.UlEdchMcrWaitTimeSwi and URnluCfg.UlStaticMcrWaitTime.
2. When the Iub transmission quality between the RNC and connected Node Bs differs:
For example, some macro Node Bs are connected to the RNC by dedicated IP
network, which leads to better transmission quality due to smaller transmission
delay and jitter; at the same time, some pico Node Bs are connected to the RNC by
common IP network, which results in unstable transmission quality since the
transmission delay and jitter is larger. In this case, macro diversity combining time of
UEs differs a lot. It is suggested to configure a dynamic macro diversity combining
time to get better QoS. The parameters refer to URnluCfg.UlMcrWaitTimeSwi,
URnluCfg.UlEdchMcrWaitTimeSwi and URnluCfg.UlMaxMcrWaitTime. The macro
diversity combining time can be set to maximum 120ms in an RNC.

Handover Control
3.2.8 Intra-Frequency Handover Procedure
For inter-RNC soft handover procedures, refer to 3.6.7.1 Inter-RNC Soft Handover
(Adding a Radio Link), 3.6.7.2 Inter-RNC Soft Handover (Deleting a Radio Link) and
3.6.7.3 Inter-RNC Soft Handover (Swapping a Radio Link).
3.3 ZWF21-03-002 Intra-Frequency Hard Handover
The function of intra-frequency hard handover is controlled by the switch

UCelInfoFDD.IntraHardHoSw in the cell level. When UCelInfoFDD.IntraHardHoSw is set
to “1: On”, intra-frequency hard handover is permitted. Otherwise, it is not permitted.
3.3.1 Intra-Frequency Hard Handover Scenarios
Soft or softer handover has requirements on time and cell capability. If a soft or softer
handover is unavailable in any of the following scenarios, an intra-frequency hard
handover is performed to guarantee service continuity.
 The intra-frequency measurement report excludes the OFF and TM of the target
cell.
 The lur interface between RNCs is unavailable in the case of intra-frequency

handover.
 The signal RB is carried on HS-DSCH in the active cell, while F-DPCH is not
supported by the target cell of the soft handover.
 The capability of the target cell does not match that of the source cell, including:
 The UE uses multi-user detection in active set cells, but the target cell does not
support multi-user detection.
 The UE uses DTX-DRX in active set cells, but the target cell does not support
DTX-DRX.
 Uplink 16QAM is configured but the target cell does not support it.

Handover Control
 UL flexible RLC is used by the current service, but the target cell does not
support it.
 E-DPCCH Power Boosting is configured but the target cell does not support it.
 The transmission delay UIubLink.TimeDelay of the cell that has triggered the
intra-frequency event and is the neighboring cell of the current RNC side does
not match the transmission delay of the cells in the current active set, and the
soft handover conditions in “3.2.7.4.1 Configuration of Soft Handover between
Cells with Different Transport Time Delay Grades over Iub” are not met. Or the
transmission delay UExternalUtranCellFDD.timeDelay of the cell that has
triggered the intra-frequency event and is the neighboring cell of the D-RNC
side does not match the transmission delay of the cells in the current active
set.
3GPP has defined two synchronization modes for intra-frequency hard handover: timing
re-initialized and timing-maintained. The difference between them is whether CFN and
UL transmission timing of the UE are changed after intra-frequency hard handover.
Compared with timing re-initialized mode, re-executing the physical layer synchronization
on the UE side is not required in timing-maintained mode, thus shortening the time delay
and increasing the handover success rate.
The selection of a synchronization mode is controlled by

URncInfo.modeOfIntraHardHO.
If URncInfo.modeOfIntraHardHO is set to “0”, timing re-initialized mode is used.
If URncInfo.modeOfIntraHardHO is set to “1”, timing-maintained mode is used.

Handover Control
3.3.2 Intra-Frequency Hard Handover Procedure
3.3.2.1 Intra-RNC Hard Handover
Figure 3-3 Intra-RNC Hard Handover
UE NODEB2 NODEB1 RNC
RADIO LINK SETUP REQUEST
RADIO LINK SETUP RESPONSE
PHYSICAL CHANNEL RECONFIGURATION
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
RADIO LINK DELETION REQUEST
RADIO LINK DELETION RESPONSE

Handover Control
3.3.2.2 Inter-RNC Hard Handover Without an lur Interface
Figure 3-4 Inter-RNC Hard Handover Without an lur Interface
UE N ode B N ode B RNC RNC M S C /S G S N S G S N /M S C

S o u rce T a rg et S o u rce T a rg et
1 . R elo catio n R eq uired

RANAP RANAP
2 . R elo catio n R eq uired

RANAP RANAP
3 . R elo catio n R eq uest

RANAP RANAP

RANAP RANAP
5 . A L C A P Iu D ata
T ransp o rt B earer S etup
6 . R ad io L ink S etup R eq uest

NBAP NBAP
7 . R ad io L ink S etup R esp o nse

NBAP NBAP
8 . A L C A P Iub D ata T ransp o rt B earer S etup

RANAP A ckno w led ge RANAP
1 0 . R elo catio n R eq uest

A ckno w led ge
RANAP RANAP
1 1 . R elo catio n C o m m and

RANAP RANAP
1 2 . R elo catio n C o m m and

RANAP RANAP
1 3 . D C C H : P hysical C hannel R eco nfiguratio n N o te 1

RRC RRC
1 4 . R ad io L ink R esto re Ind icatio n

NBAP NBAP 1 5 . R elo catio n
D etect
RANAP RANAP
1 6 . R elo catio n D etect RANAP
RANAP
1 7 . R ad io L ink F ailure Ind icatio n
NBAP NBAP
1 8 . D C C H : P hysical C hannel R eco nfiguratio n C o m p lete N o te 1

RRC RRC
1 9 . R elo catio n
C o m p lete
RANAP RANAP
2 0 . R elo catio n C o m p lete

RANAP RANAP
2 1 . Iu R elease C o m m and
RANAP RANAP
2 2 . Iu R elease C o m m and
RANAP RANAP
2 3 . A L C A P Iu D ata T ransp o rt B earer

R elease
2 4 . Iu R elease C o m p lete
RANAP RANAP
2 5 . Iu R elease C o m p lete
RANAP RANAP
If inter-frequency cells between RNCs are adjacent and the lur interface is unavailable,
the hard-handover-triggered SRNS relocation is performed. The procedure refers to
3.7.2 Relocation Triggered by Hard Handover.
For the procedure of inter-RNC hard handover via Iur interface, refer to 3.6.7.4 Inter-RNC
Hard Handover Through lur Interface.

Handover Control
3.4 ZWF21-03-003 Inter-Frequency Hard Handover
The inter-frequency handover is the procedure which a UE is handed over from one
frequency of a UTRAN to another one. It can be a measurement-based handover
between frequencies or a blind handover based on the “Overlap or Covers” relationship.
The blind handover between cells with the overlap relationship can only be triggered by
the function of overload control or load balancing. For the details about overload control,
refer to ZTE UMTS Overload Control Feature Guide. For the details about load balancing,
refer to ZTE UMTS Load Balance Feature Guide.
The prerequisite for measurement-based inter-frequency handovers is that the UE

measures the quality of non-used frequencies. In a WCDMA system, for an
inter-frequency measurement in CELL_DCH state, the UE must enable compressed
mode for inter-frequency measurements unless it has dual receivers (for the details
about compressed mode, refer to 3.10 ZWF21-03-010 Compressed Mode). In addition,
regarding the influence of compressed mode on the system resource utilization (for
example, downlink power and uplink interference) and UE (for example, transmitted
power and battery consumption), an inter-frequency measurement is enabled only when
the current serving carrier has poor radio quality. The radio quality of the current serving
carrier can be measured by four indicators, namely, uplink BLER, uplink transmitted
power of the UE, downlink transmitted power, and the pilot signal quality of the current
frequency. When receiving the inter-frequency measurement result reported by the UE,
the RNC determines an inter-frequency handover and handovers the UE to the target
frequency and cell specified in the measurement result.
This text only describes the inter-frequency handover based on inter-frequency

measurement (the UE measures the quality of P-CPICH). The inter-frequency handover
based on uplink BLER refers to ZTE UMTS Quality Based Handover Feature Guide. The
inter-frequency handover based on uplink or downlink transmitted power refers to ZTE
UMTS Transmitted Power Based Handover Feature Guide.
3.4.1 Selection Strategy of Inter-Frequency and Inter-RAT Handover
When the compressed mode and handover are initiated, there is a priority between
inter-frequency and inter-RAT, which is controlled by the configured parameter

Handover Control
IfOrRatHoSwch (UCelInfoFDD.IfOrRatHoSwch). So the selection strategy is described

firstly.
 IfOrRatHoSwch is set to “Only Inter Frequency”.
 If inter-frequency neighboring cells exist, the measurement of event 2D and 2F

for inter-frequency handover are initially issued. When compressed mode is
activated, only inter-frequency measurements are issued by the RNC.
 If no inter-frequency neighboring cells exist, no inter-frequency measurements

are issued by the RNC.
 IfOrRatHoSwch is set to “Only Inter RAT”.
 If inter-RAT neighboring cells exist, the measurement of event 2D and 2F for

inter-RAT handover are initially issued. When compressed mode is activated,
only inter-RAT measurements are issued by the RNC.
 If only inter-RAT neighboring cells exist, no inter-RAT measurements are

issued by the RNC.
 IfOrRatHoSwch is set to “Inter Frequency Is Prior to Inter RAT”.
 If only inter-frequency neighboring cells exist, the measurement of event 2D

and 2F for inter-frequency handover are initially issued. When compressed
mode is activated, only inter-frequency measurements are issued by the RNC.
 If only inter-RAT neighboring cells exist, the measurement of event 2D and 2F

for inter-RAT handover are initially issued. When compressed mode is
activated, only inter-RAT measurements are issued by the RNC.
 If both inter-frequency and inter-RAT neighboring cells exist, the RNC initially
issues the measurement of event 2D and 2F for inter-frequency handover.
When compressed mode is activated, the RNC only issues the inter-frequency
measurements and starts the timer Timer_Wait (controlled by
URncFunction.T4ShifIfLteGsmMea). If all non-used frequencies trigger event
2E or the timer Timer_Wait has expired, the RNC stops the inter-frequency
measurement and starts an inter-RAT measurement.

Handover Control
 IfOrRatHoSwch is set to “EUTRAN Firstly, Inter-frequency Secondly, GSM Finally”.
i. For the service including a CS service, or only PS services and the conditions
of E-UTRAN inter-RAT handover are not met.
 If only inter-frequency neighboring cells exist, the measurement of event 2D

and 2F for inter-frequency handover are initially issued. When compressed
mode is activated, only the inter-frequency measurement is issued by the
RNC.
 If only GSM inter-RAT neighboring cells exist, the measurement of event 2D

and 2F for GSM inter-RAT handover are initially issued. When compressed
mode is activated, only the GSM inter-RAT measurement is issued by the
RNC.
 If both inter-frequency and GSM inter-RAT neighboring cells exist, the RNC
initially issues the measurement of event 2D and 2F for inter-frequency
handover. When compressed mode is activated, the RNC only issues the
inter-frequency measurement and starts the timer Timer_Wait (controlled by
URncFunction.T4ShifIfLteGsmMea). If all non-used frequencies trigger event
2E or the timer Timer_Wait has expired, the RNC stops the inter-frequency
measurement and starts a GSM inter-RAT measurement.
ii. For only PS services and the conditions of E-UTRAN inter-RAT handover are
met.
 If inter-frequency neighboring cells exist, the RNC initially issues the

measurement of event 2D and 2F for E-UTRAN inter-RAT handover. When
compressed mode is activated, the RNC only issues the E-UTRAN inter-RAT
measurement and starts the timer Timer_Wait (controlled by
URncFunction.T4ShifIfLteGsmMea). If the timer Timer_Wait has expired, the
RNC stops the E-UTRAN inter-RAT measurement and starts an
inter-frequency measurement.
 If inter-frequency neighboring cells do not exist, the measurement of event 2D

and 2F for E-UTRAN inter-RAT handover are initially issued. When

Handover Control
compressed mode is activated, only the E-UTRAN inter-RAT measurement is

issued by the RNC.
For the details about the E-UTRAN inter-RAT handover, refer to ZTE UMTS
Handover with LTE Feature Guide.
Note: When the best cell changes or service changes, if the compressed mode is
activated, the compressed mode remains unchanged as far as possible. Only if the
compressed mode can’t be maintained, the RNC will reconfigure compressed mode.
3.4.2 Switch Control Strategy of Measurement-based Inter-frequency

Handover for Services
As the operators have different handover requirements for different services, ZTE RAN
sets the switch of inter-frequency handover based on measurement respectively for
services, which is convenient for operators to configure the network flexibly.
Inter-frequency handover is permitted only when the inter-frequency switch (IfHoSw)

corresponding to the current UE service is enabled. Otherwise, the RNC prohibits
performing an inter-frequency handover for the current service by not starting the
inter-frequency measurement. For the relationships between the IfHoSw and the service
configuration parameters, refer to Table 3-2.
Table 3-2 Relationships between Services and IfHoSw
Service IfHoSw
AMR ULogicalRnc.amrIfHoSw
R99 RT ULogicalRnc.r99RtIfHoSw
R99 NRT ULogicalRnc.r99NrtIfHoSw
HSDPA ULogicalRnc.hsdpaIfHoSw
HSUPA ULogicalRnc.hsupaIfHoSw
3.4.3 Inter-frequency Measurement
Inter-frequency measurements contain radio quality measurement on both used carrier

frequency and non-used carrier frequency. ZTE RAN supports two reporting criteria for

Handover Control
the inter-frequency measurements: periodic reporting and event-triggered reporting. The

URncFunction.InterHoMth parameter determines which reporting criterion is selected.
The event-triggered reporting criterion indicates that the UE checks whether the
inter-frequency triggering events are fulfilled in accordance with the P-CPICH quality
measurement results of inter-frequency neighboring cells. If yes, the UE reports the
inter-frequency events (including event ID and target cell) to the RNC.
The periodic reporting criterion indicates that the UE regularly reports the P-CPICH
quality measurement results of inter-frequency neighboring cells to the RNC, and the
RNC checks whether the inter-frequency triggering events are fulfilled in accordance with
the measurement reporting results. If yes, the RNC outputs the inter-frequency events
(including event ID and target cell).
The measurement reporting criteria in this section are all based on the event-triggered
reporting if there is no special description. For the periodic reporting criteria, refer to 3.4.9
Periodic Inter-frequency Measurement Reporting.
3GPP has defined of the following inter-frequency measurement events. If the defined
condition is fulfilled, the UE will report the corresponding event to the RNC.
Event 2A: Change of best frequency.
Event 2B: 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 2C: The estimated quality of a non-used frequency is above a certain threshold.
Event 2D: The estimated quality of the currently used frequency is below a certain
threshold.
Event 2E: The estimated quality of a non-used frequency is below a certain threshold.
Event 2F: The estimated quality of the currently used frequency is above a certain
threshold.
Among all inter-frequency measurement events, event 2D and event 2F only involve the
measurements of the currently used carrier frequency, so compressed mode is not
required during measurement and no extra overhead will be brought to both the UE and

Handover Control
the system. Compressed mode can be enabled and disabled based on the definition of
2D and 2F. If inter-frequency or inter-RAT handover is permitted (the relative service
switches are all “On” and the corresponding conditions of issuing event 2D and 2F in
3.4.1 Selection Strategy of Inter-Frequency and Inter-RAT Handover are met), the RNC
delivers event 2D, event 2F, and intra-frequency events to the UE. The following
principles for the measurement setup, modification and deletion are applied to
inter-frequency measurement events other than event 2D and event 2F.
An inter-frequency measurement can be triggered in either of the following scenarios:
 The radio quality of the current serving carrier frequency deteriorates, and there are
inter-frequency neighboring cells, and the UE supports the radio frequency band of
these neighboring cells.
Where, the “Radio Quality Deterioration of Current Serving Carrier Frequency” can
be judged through any of the following four indexes: the UE reports event 2D, the
uplink BLER exceeds a certain threshold, the transmitted power of the UE exceeds
a certain threshold, or the downlink transmitted power exceeds a certain threshold.
 The UE meets the slow moving conditions and there is a micro cell with a higher
HCS level in the coverage of the current cell (for the details about the handover
based on moving speed, refer to ZTE UMTS Hierarchical Cell Structures Feature
Guide.).
After an inter-frequency measurement is set up, the measurement can be modified under
either of the following conditions:
 If the inter-frequency measurement parameters and neighboring cells are changed
after the soft handover, the inter-frequency measurement parameters and
neighboring cell list need to be updated by modifying the measurement.
service and concurrent services are different, the inter-frequency measurement

Handover Control
Measurement deletion corresponds to the measurement setup, so the inter-frequency

measurement will be released when the conditions of setting up an inter-frequency
measurement are not met.
 If the active set cells do not have an inter-frequency neighboring cell after a
handover is performed and the inter-frequency measurement is started, then this
 If there are inter-frequency neighboring cells, but these cells have a contained
relationship with active set cells or intra-frequency neighboring cells of active set
cells, and the inter-frequency measurement is started, then this measurement
should be released.
 If the inter-frequency measurement is started, and the used frequency quality is

improving, then this measurement should be released.
An inter-frequency measurement should be also deleted if any of the following conditions

is met:
 After an inter-frequency handover is performed, the inter-frequency measurement
should be released.
 If an abnormal inter-frequency measurement report (for example, a nonexistent
measurement task in the RNC) is received, the corresponding inter-frequency
time to release the measurement. If the time difference exceeds a threshold (set by the
parameter URncFunction.TResndMeaCtrlRel), the RNC performs measurement deletion
again.

Handover Control
reselection in non-CELL_DCH state and that used for handover in CELL_DCH state
can be configured separately, which can be indicated by neighboring cell
configuration state. For inter-frequency neighboring cells, it is indicated by
UUtranRelation.StateMode.

 Handover parameter configuration under micro diversity
All measurement parameters are generated based on cells. In the case of macro
Inter-frequency handover parameters can be independently configured in

accordance with the application scenarios, measurement quantities, measurement
reporting criteria and service bearer types. Multiple sets of measurement
parameters are needed for different purpose. The details are described as follows:
UInterMeasProfile.intialHoCelSelScen
e
Outdoor Scene UUtranCellFDD.HoCelSelScene
High-Mobility Outdoor (Note: These two parameters are only
Application
Scene used for displaying the scenario, not
Scenario
Indoor Scene for indexing handover parameters,
Subway/ tunnel Scene which refers to the following
“Handover parameter indexing
principle”.)
Measurement PCPICH Ec/No UUtranCellFDD.NonIntraMeasQuan

Handover Control

quantity PCPICH RSCP
PCPICH Ec/No and RSCP
Measurement
Event-triggered reporting
reporting URncFunction.InterHoMth
Periodic reporting
criterion
RT RAB Including Voice

RT RAB Excluding Voice on
Single NRT on DL DCH/UL
DCH
HS-DSCH/UL DCH
HS-DSCH/UL E-DCH
DCH/UL DCH
Service
Multi-NRT RAB, HSPA is UInterMeaSrvSpec.srvCategory
bearer type
Involved and only DCHs are
Used in UL
Used in UL
Multi RAB Including CS and
PS
Not Related to Service Type
(used for detected set
measurement)
Note:

ii. If the concurrent services contain non-CS RT services, the handover


Handover Control
To modify and optimize parameters more easily, inter-frequency handover

parameters are used based on indexing. For the detailed parameter indexing
principle, see Figure 3-5:
Figure 3-5 Parameter Indexing Principle of Inter-frequency Handover
UUtranCellFDD
refUInterMeasProfile
UInterMeasProfile
UInterMeaSrvSpec UInterMeasNoSrvSpec
NonIntraMeasQuan NonIntraMeasQuan
UInterEcNoEvMeasforU UInterRscpEvMeasforU UInterEcNoPrdMeas UInterRscpPrdMeas
InterMeasCfgNo InterMeasCfgNo interMeasCfgNo interMeasCfgNo
1. First, you can obtain an inter-frequency configuration set UInterMeasProfile by

matching UInterMeasProfile.profileId with UUtranCellFDD.refUinterMeasProfile.
Then you can obtain the measurement object in the next level in accordance with
the reporting criterion currently used by the UE in this configuration set. If the
measurement reporting criterion is event-triggered reporting, you can obtain the
next-level measurement object from the UInterMeaSrvSpec object. If the
measurement reporting criterion is periodic reporting, you can obtain the next-level
measurement object from the UInterMeasNoSrvSpec object.
2. If the measurement object obtained in Step 1 is UInterMeaSrvSpec, you can obtain

the current measurement object (UInterEcNoEvMeasforU or
UInterRscpEvMeasforU) in accordance with the measurement quantity
UUtranCellFDD.NonIntraMeasQuan. Then, you can obtain InterMeasCfgNo

Handover Control
(inter-frequency measurement configuration number) in accordance with the

service type UInterMeaSrvSpec.srvCategory. If the measurement object obtained in
Step 1 is UInterMeasNoSrvSpec, you can obtain the current measurement object
and InterMeasCfgNo (inter-frequency measurement configuration number) in
accordance with the measurement quantity UUtranCellFDD.NonIntraMeasQuan.
Finally, you can obtain the inter-frequency handover measurement parameters of
the current application scenario and service through the indexing to
InterMeasCfgNo. The details are described as follows:
i. If the event-triggered reporting is used, and the measurement quantity is

P-CPICH Ec/No, you can refer to the following table to obtain the parameters
that are matched with InterMeasCfgNo and associated with
UInterEcNoEvMeasforU.InterMeasCfgNo from the UInterEcNoEvMeasforU
object.
GUI Name Parameter
Inter-frequency Event Identity UInterEcNoEvMeasforU.meaEvtId
Event Number of Inter-frequency UInterEcNoEvMeasforU.measEvtNum

Measurement
Filter Coefficient UInterEcNoEvMeasforU.filterCoeff
Hysteresis UInterEcNoEvMeasforU.hysteresis
Time To Trigger UInterEcNoEvMeasforU.TrigTime
Weight of the Non-used Frequency for UInterEcNoEvMeasforU.WNoUsed

2A/2B/2C/2E
Weight of the Currently Used Frequency UInterEcNoEvMeasforU.Wused

for 2A/2B/2D/2F
Absolute Threshold of the Quality of the UInterEcNoEvMeasforU.ThreshNoUsedFreq

Non-used Frequency for 2B/2C/2E
Absolute Threshold of the Quality of the UInterEcNoEvMeasforU.ThreshUsedFreq

Currently Used Frequency for 2B/2D/2F
ii. If the event-triggered reporting is used, and the measurement quantity is

P-CPICH RSCP, you can refer to the following table to obtain the parameters
that are matched with InterMeasCfgNo and associated with
UInterRscpEvMeasforU.InterMeasCfgNo from the UInterEcNoEvMeasforU
object.

Handover Control
GUI Name Parameter

Inter-frequency Event Identity UInterRscpEvMeasforU.meaEvtId
Event Number of Inter-frequency UInterRscpEvMeasforU.measEvtNum

Measurement
Filter Coefficient UInterRscpEvMeasforU.filterCoeff
Hysteresis UInterRscpEvMeasforU.hysteresis
Time To Trigger UInterRscpEvMeasforU.TrigTime
Weight of the Non-used Frequency for UInterRscpEvMeasforU.WNoUsed

2A/2B/2C/2E
Weight of the Currently Used Frequency UInterRscpEvMeasforU.Wused

for 2A/2B/2D/2F
Absolute Threshold of the Quality of the UInterRscpEvMeasforU.ThreshNoUsedFreq

Non-used Frequency for 2B/2C/2E
Absolute Threshold of the Quality of the UInterRscpEvMeasforU.ThreshUsedFreq

Currently Used Frequency for 2B/2D/2F
iii. If the periodic reporting is used, and the measurement quantity is P-CPICH
Ec/No, you can refer to the following table to obtain the parameters that are
matched with InterMeasCfgNo and associated with
UInterEcNoPrdMeas.InterMeasCfgNo from the UInterEcNoPrdMeas object.
GUI Name Parameter
Filter Coefficient UInterEcNoPrdMeas.filterCoeff
Amount of Reporting in Period Report UInterEcNoPrdMeas.PrdRptAmount

Criteria
Reporting Interval in Period Report UInterEcNoPrdMeas.PrdRptInterval

Criteria
iv. If the periodic reporting is used, and the measurement quantity is RSCP, you
can refer to the following table to obtain the parameters that are matched with
InterMeasCfgNo and associated with UInterRscpPrdMeas.InterMeasCfgNo
from the UInterEcNoPrdMeas object.
GUI Name Parameter
Filter Coefficient UInterRscpPrdMeas.filterCoeff
Amount of Reporting in Period Report UInterRscpPrdMeas.PrdRptAmount

Criteria

Handover Control
GUI Name Parameter

Reporting Interval in Period Report UInterRscpPrdMeass.PrdRptInterval
Criteria
Where,
The MeasEvtNum
(UInterEcNoEvMeasforU.measEvtNum/UInterRscpEvMeasforU.measEvtNum) and
MeaEvtId (UInterEcNoEvMeasforU.meaEvtId/UInterRscpEvMeasforU.meaEvtId)
control how many events can be configured during the inter-frequency
measurement, and which events should be configured. MeaEvtId is defined as an
array whose dimension number is MeasEvtNum. The MeasEvtNum is configured
up to six because there are a total of six events (2A, 2B, 2C, 2D, 2E, 2F) in the
3.4.3.5 Selection Strategy of Inter-frequency Neighboring Cells Sent in

Measurement Control
In an inter-frequency measurement, a UE can measure two non-used frequencies at

most. Therefore, when the number of frequencies of inter-frequency neighboring cells
sent in a Measurement Control message is greater than two, which frequency the UE will
be handed over to is unpredictable.
To ensure that a UE is handed over to the expected frequency and that users are
reasonably distributed among frequencies, this feature is introduced, and the non-used
frequencies are filtered in accordance with the cell measurement priority. The strategy is
as follows:
1. If a cell is an adjacent cell to several cells in the active set, that is, the priority levels
configured for this cell may vary, the highest priority level is used.
2. The inter-frequency neighboring cells are sorted in a descending order of

measurement priority, and two non-used frequencies are selected in order.
3. The inter-frequency neighboring cells, whose frequencies are selected in step 2, are
filtered and sent in a Measurement Control message. If the number of filtered

Handover Control
neighboring cells exceeds 32, the neighboring cells are sorted in a descending
order of measurement priority, and the cells in excess of 32 are discarded.
The measurement priority levels of inter-frequency neighboring cells are updated

whenever event 1A, 1B, 1C or 1D is triggered, and the non-used frequencies are
selected in accordance with the new cell measurement priorities.
3.4.4 Inter-frequency Event Triggering
To avoid measurement fluctuation during inter-frequency measurements, the UE needs

to perform layer-3 filtering to the measurement results. Then, the UE determines whether
measurement results to the RNC. For the filtering principle and formula, refer to 3.2.3.1
Measurement Result Filtering. The layer-3 filtering coefficient k is obtained from the
parameter filterCoeff in the record associated with a certain configuration number based
on the principles described in 3.4.3.4 Parameter Configuration.
3.4.4.2 Carrier Quality Estimation Criteria for Inter-frequency Measurement
The quality of a carrier is reflected by estimating the signal quality of the P-CPICH
channel of all cells in the active set in inter-frequency measurement, so a special quality
estimation criteria for inter-frequency measurement is needed, the estimation formula is
as follows:
 NA j 
Qfrequencyj  10  LogMfrequency j  Wj  10  Log  Mi j   (1  Wj )  10  LogMBest j
 i 1 
Where,
Qfrequency j is the measurement result of the carrier j (dB for Ec/No; dBm for RSCP);
Mfrequency j is the physical measurement value of the carrier j;
Mi j is the physical measurement value of cell i in the carrier j;

Handover Control
NA j is the number of cells in the active set of the carrier j (excluding the best ell);
MBest j is the measurement result of the best cell in the active set of the carrier j;
Wj is the weight that the best cell in the active set occupies in the quality estimation for
the carrier j. It is obtained from the parameters WNoUsed or Wused in the record
For the inter-frequency events judgment, to avoid the inter-frequency event misreport
due to the fluctuation of radio quality, if a to-be-evaluated cell meets the reporting range
or threshold of a certain event, the condition must be met for a time (Timetotrigger)
before the reporting of this event. Where, Timetotrigger is obtained from the parameter
TrigTime in the record associated with a certain configuration number based on the
Event 2A: Change of best frequency.
QNotBest  QBest  H2a/2
Where,
QNotBest is the measurement result of the currently non-best carrier frequency.
QBest is the measurement result of the currently best carrier frequency.
H2a is the handover decision hysteresis parameter of event 2A. It can be obtained from
the parameter hysteresis in the record associated with a certain configuration number

Handover Control
3.4.4.5 Event 2B Triggering
Event 2B: 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.
QNon used  TNon used 2b  H2b /2 QUsed  TUsed 2b  H2b /2
Where,
QNon used is the measurement result of the currently used carrier frequency.
TNon used 2b is the absolute threshold of good-quality non-used carrier frequency in an

event 2B decision. It can be obtained from the parameter ThreshNoUsedFreq in the
H2b is the handover decision hysteresis parameter of event 2B. It can be obtained from
QUsed is the measurement result of the currently used carrier frequency.
TUsed 2b is the absolute threshold of poor-quality used carrier frequency in an event 2B

decision. It can be obtained from the parameter ThreshUsedFreq in the record
Event 2C: The estimated quality of a non-used frequency is above a certain threshold.
QNon used  TNon used 2c  H2c /2
Where,
QNon used is the measurement result of the currently non-used carrier frequency.

Handover Control
TNon used 2c is the absolute threshold of good-quality non-used carrier frequency in an

event 2C decision. It can be obtained from the parameter ThreshNoUsedFreq in the
H2c is the handover decision hysteresis parameter of event 2C. It can be obtained from
3.4.4.7 Event 2D Triggering
Event 2D: The estimated quality of the currently used frequency is below a certain
threshold.
QUsed  TUsed 2d  H2d /2
Where,
TUsed 2d is the absolute threshold of poor-quality used carrier frequency in an event 2D

H2d is the handover decision hysteresis parameter of event 2D. It can be obtained from
3.4.4.8 Event 2E Triggering
Event 2E: The estimated quality of a non-used frequency is below a certain threshold.
QNon used  TNon used 2e  H2e /2
Where,

Handover Control
QNon used is the measurement result of the currently non-used carrier frequency.
TNon used 2e is the absolute threshold of good-quality non-used carrier frequency in an

event 2E decision. It can be obtained from the parameter ThreshNoUsedFreq in the
H2e is the handover decision hysteresis parameter of event 2E. It can be obtained from
3.4.4.9 Event 2F Triggering
Event 2F: The estimated quality of the currently used frequency is above a certain
threshold.
QUsed  TUsed 2f  H2f /2
Where,
TUsed 2f is the absolute threshold of poor-quality used carrier frequency in an event 2F

H2f is the handover decision hysteresis parameter of event 2F. It can be obtained from

Handover Control
3.4.5 Inter-frequency Handover Decision and Execution
3.4.5.1 Event 2A/2B/2C Processing
During an inter-frequency handover, only one of events 2A, 2B and 2C can be triggered
in the same cell. Specifically, which event is used to make an inter-frequency handover
decision is controlled by the inter-frequency handover policy parameter
UUtranCellFDD.InterHoTactic.
When the quality of the target carrier frequency meets the handover requirements, the
ZTE RNC performs a handover in accordance with the following principles:
 If a measurement report contains several target cells, one with the best quality is
preferentially selected as the target cell. If there is any inter-frequency neighboring
cell which covers or overlaps the target cell, inter-frequency load balancing is
performed based on the cell’s load. (For the details about load balancing, refer to
ZTE UMTS Load Balance Feature Guide).
 For CS users, an inter-frequency hard handover is performed.
 For PS users, a hard handover tends to fail due to admission failure in the event of
heavy cell load because a majority of resources are occupied by PS services. The
following strategies are required:
 If the current channel type is DCH/DCH and the channel assigned for the
target cell is also DCH/DCH after a handover, a handover attempt is made first
according to the current rate. If the admission fails, another handover attempt
is made according to the GBR of the current services or the minimum rate
grade of DRBC (for the details about DRBC, refer to ZTE UMTS Dynamic
Radio Bearer Control Feature Guide), to improve the handover success rate.
 If the current channel type is HS-DSCH/E-DCH or HS-DSCH/DCH, and

DCH/DCH is used after a handover, the handover is performed directly
according to the GBR of the current services or the minimum rate grade of
DRBC (for the details about DRBC, refer to ZTE UMTS Dynamic Radio Bearer
Control Feature Guide).

Handover Control
 If the current channel type is DCH/DCH, and HS-DSCH/E-DCH or

HS-DSCH/DCH is used after a handover, the handover is admitted by the
HS-DSCH/E-DCH or HS-DSCH/DCH (for the details about the HSDPA or
HSUPA admission, refer to ZTE UMTS HSDPA Introduction Feature Guide or
ZTE UMTS HSUPA Introduction Feature Guide). If the HS-DSCH/E-DCH or
HS-DSCH/DCH admission fails, another handover attempt is made according
to the minimum rate (GBR of services or minimum rate grade of DRBC) of
DCH/DCH.
To prevent the UE from being repeatedly handed over to inter-frequency cells within a
short time, which affects the system performance, the failure punishment mechanism of
inter-frequency handover as follows is introduced.
If an inter-frequency handover of a UE fails, the RNC starts a penalty timer
(URncInfo.HoToInterPenTimer) for the UE handover failures. At the expiry of this timer,
the inter-frequency measurement whose measurement report has not been processed
by the RNC will be initiated again.
3.4.5.2 Event 2D Processing
The RNC processes event 2D reported by a UE according to the following principles:
 A blind handover attempt is performed if there are inter-frequency neighboring cells

which cover the source cell.
 Compressed mode is initiated and an inter-frequency measurement (includes

events 2A, 2E and 2F, or 2B, 2E and 2F, or 2C, 2E and 2F) is initiated if there is no
inter-frequency neighboring cell which covers the source cell or a blind handover
fails.
3.4.5.3 Event 2E Processing
If all non-used carrier frequencies report event 2E, which indicates that the radio quality
of all inter-frequency neighboring cells is poor and the 3G system quality deteriorates, the
RNC deals with this case according to the following principles:

Handover Control
 If there are inter-RAT neighboring cells which cover the current serving cell
(indicated by the parameter UGsmRelation.GsmShareCover), an inter-RAT blind
handover attempt is performed.
 Inter-RAT compressed mode is initiated and an inter-RAT measurement (includes

event 3A or 3C) is initiated if there is no inter-RAT neighboring cell which covers the
current serving cell or a blind handover fails.
3.4.5.4 Event 2F Processing
When event 2F of the currently used carrier frequency is reported, which means the
quality of the currently used carrier frequency is good, the RNC deactivates the
compressed mode and releases the inter-frequency or inter-RAT measurement
3.4.5.5 Minimum Quality Judgment Strategy of Inter-frequency Handover
The inter-frequency handover success rate is low when the quality of the target cell is
poor. Therefore ZTE RAN introduces the following strategy to increase the
inter-frequency handover success rate and decrease the call-drop rate. That is to
determine an inter-frequency handover according to the result of the quality judgment of
the target cell whose signal quality meets the conditions of event 2A, 2B or 2C.
For event 2A, 2B or 2C, if the following conditions are met, the RNC does not process the
inter-frequency event, which means that inter-frequency handover is not performed.
1. UCelInfoFDD.InterHoMinThrdSw is set to “1: On”.
2. The UE reports event 2A, 2B or 2C or the quality of the target cell reported
periodically by the UE meets the conditions of event 2C.
3. The link quality of the target cell: CPICH EcNo<=URncFunction.InterHoEcNoThrd or

CPICH RSCP<=URncFunction.InterHoRscpThrd.
3.4.6 Inter-frequency Event Buffering
If the RNC receives an inter-frequency measurement report but discards it without any
processing because the RNC is busy on other events (for example, Radio Bearer

Handover Control
Reconfiguration) of the UE, the handover opportunity is lost easily and call drops may
occur. Therefore, the measurement report needs to be buffered, and waits for processing
by the RNC after the RNC completes the current event of the UE.
The inter-frequency buffering strategies are described as follows:
 Inter-frequency event buffering supports up to six events.
 For event 2D or 2F used for an inter-frequency handover, if the measurement
quantity is “CPICH Ec/No” or “CPICH RSCP”, only the measurement report that has
the same measurement quantity with UUtranCellFDD.NonIntraMeasQuan can be
buffered. If the measurement quantity is “CPICH Ec/No and CPICH RSCP”, the
event 2D or 2F of the latest Ec/No and RSCP are buffered.
 If event 2A, 2B, 2C or 2E exists in the buffer and event 2F is triggered, and if the
measurement quantity of event 2F is the same as the current event, the buffered
event is deleted and event 2F is buffered. Otherwise, event 2F is discarded.
 When event 2A, 2B, 2C or 2E is reported, if event 2F exists in the buffer and its
measurement quantity is the same with the current measurement, event 2A, 2B, 2C
or 2E is discarded; otherwise, event 2A, 2B, 2C or 2E is buffered.
 After the handover is successfully performed, all the measurement reports in the
buffer should be cleared.
3.4.7 Coupling Processing of Different Handovers
Inter-frequency handover can be triggered by the following:
 Load control
 Downlink coverage events
 Uplink transmitted power
 Uplink BLER
 Downlink transmitted power

Handover Control
 Moving speed of the UE
The load control-based handover aims to quickly reduce system loads and ensure
system stability, and it has the highest priority.
The handovers based on downlink coverage events, uplink transmitted power, uplink
BLER or downlink transmitted power aims to guarantee the call QoS and user
experience, and they have lower priority.
The moving speed-based handover in the HCS is used to appropriately allocate traffic for
different cells, make full use of system resources and enhance system performance. The
moving speed-based handover is a system optimization function and has the lowest
priority.
The handover with highest priority will shield the handovers with comparatively lower
priority. For example, if a load control-based handover occurs in a cell, the RNC can no
longer hand over or access new services into the cell. In the case of a poor carrier quality,
the RNC needs to hand over the UE into the cell with good quality through radio quality
measurement, without taking account of the moving speed of the UE.

Inter-Frequency Handover
In the scenarios of the service setup procedure, relocation from other RNCs to the local
RNC, state transition (CELL_FACH to CELL_DCH) and best cell change, when the cell
meets the conditions of turning off carrier power, if the best cell has inter-frequency
neighboring cells, the RNC performs the inter-frequency measurement and activates the
corresponding inter-frequency compressed mode no matter what
UCelInfoFDD.IfOrRatHoSwch and the relative inter-frequency service switches are. For
details about “Intelligent Carrier Power Off/On”, refer to the ZTE UMTS Intelligent Carrier
Power off/on Feature Guide.
3.4.9 Periodic Inter-frequency Measurement Reporting
In some scenarios, inter-frequency handover may not be performed timely due to long
delay of reporting events. ZTE RAN introduces an inter-frequency handover algorithm for

Handover Control
periodic inter-frequency measurement reporting, to accelerate the inter-frequency

handover.
Whether event-triggered reporting or periodic reporting is used in inter-frequency

measurement is determined by the RNC-level parameter InterHoMth
(URncFunction.InterHoMth) .
If InterHoMth is set to “0: Periodic Reporting”, and if the conditions for setting up an
inter-frequency measurement are fulfilled, ZTE RNC starts an inter-frequency
measurement in periodic reporting mode, and creates the inter-frequency handover
events in accordance with the conditions of the event-2c-triggering decision based on the
inter-frequency neighboring cell signal quality periodically reported by the UE. Then, a
handover procedure is executed based on the created event.
The subsequent handover processing performed by the RNC is the same as the
event-triggered reporting performed by the UE. For the detailed description, refer to
3.4.5.1 Event 2A/2B/2C Processing. This section only describes how to enable/disable
the periodic reporting measurement and create handover events by the RNC.
3.4.9.1 Periodic Reporting Measurement
For the parameters of periodic reporting measurement, refer to 3.4.3.4 Parameter

Configuration.
The periodic reporting measurement setup, modification and deletion procedures are the
same as the event-triggered reporting measurement, refer to the corresponding
procedures in 3.4.3 Inter-frequency Measurement.
3.4.9.2 Principle for Creating Event 2C
After the UE periodically reports the signal quality of the inter-frequency neighboring cell,
the ZTE RNC makes a decision in accordance with the conditions of the event 2C
triggering decision.
If the conditions of the event 2C triggering are satisfied continuously for the duration of
TriggerTime_2c, event 2C is created. Where, TriggerTime_2c is the triggering hysteresis
duration and controlled by the UCelInfoFDD.PeriodTriggerTime parameter.

Handover Control
 The condition of the event 2C triggering decision:
QTarget_Freq_Cell+ CIOTarget_Freq_Cell>= TTarget_Freq_Cell+H/2
Where,
QTarget_Freq_Cell is the quality of the target carrier frequency.
CIOTarget_Freq_Cell is the quality offset of the target carrier frequency

(UUtranRelation.CellIndivOffset), which is specially defined for periodic reporting.
TTarget_Freq_Cell is the decision threshold of quality of the target carrier frequency. It can be
obtained from the parameter ThreshNoUsedFreq in the record associated with a certain
Configuration.
H is the hysteresis of event 2C. It can be obtained from the parameter hysteresis in the
Note: when the measurement quantity is CPICH Ec/No and CPICH RSCP, CPICH Ec/No
and CPICH RSCP are both needed to meet the conditions of event 2C.
3.4.9.3 Combination of Inter-frequency Periodic Reporting and Inter-RAT

Measurement
If the inter-frequency and inter-RAT handover are both allowed, the combination of
inter-frequency periodic reporting measurement and inter-RAT measurement should be
considered.
The detailed strategies are described as follows:
 If the inter-frequency measurement criterion is periodic reporting and the inter-RAT

measurement criterion is event-triggered reporting,
The RNC performs the inter-frequency measurement in periodic reporting and

activates the corresponding inter-frequency compressed mode. After the UE
reports event 2E, or the timer Timer_Wait (controlled by
URncFunction.T4ShifIfLteGsmMea) which is used for stopping the inter-frequency

Handover Control
measurement and starting an inter-RAT measurement expires, the RNC

reconfigures the measurement to the inter-RAT event-triggered reporting
measurement and activates inter-RAT compressed mode.
Where, Timer_Wait is started when the RNC initiates the inter-frequency

measurement in periodic reporting.

measurement criterion is periodic reporting,
The RNC starts inter-frequency and inter-RAT measurement in the periodic

reporting criterion at the same time, and simultaneously activates the
inter-frequency and inter-RAT compressed mode.
Where, the mode of the inter-RAT measurement is controlled by

URncFunction.IntRatHoMth.
3.4.10 Control Strategy for Blind Handover Triggered by Second-Try
As the inter-frequency blind handover is much blind sometimes, the success rate is not
high, which affects the overall system performance. In addition, there is no control switch
in some scenarios, which is bad for performance tuning. Therefore, it is necessary to add
control switches appropriately. In view of the trigger frequency and the necessity for
controlling, first, the cell-level control switch UCelInfoFDD.SecTryBlidHoSw is introduced
for the inter-frequency blind handover triggered by second-try.
UCelInfoFDD.SecTryBlidHoSw is set to “1: On”: When an admission failure occurs, if

there is an intra-RNC inter-frequency neighboring cell that covers or overlaps the current
cell and supports the current channel type, the UE is blindly handed over to that cell.
Otherwise, the UE attempts to access the current cell on anther channel.
UCelInfoFDD.SecTryBlidHoSw is set to “0: Off”: When an admission failure occurs, the

inter-frequency blind handover is not permitted. The UE directly attempts to access the
current cell on anther channel.

Handover Control
Note: To reduce the coupling with the current features, UCelInfoFDD.SecTryBlidHoSw is

invalid and the inter-frequency blind handover triggered by second-try is permitted by
default if the balancing function is enabled.
3.4.11 Inter-Frequency Handover Procedure
Inter-frequency handovers are all hard handovers, and their procedures are identical with
intra-frequency hard handovers, refer to 3.3.2.1 Intra-RNC Hard Handover and 3.3.2.2
Inter-RNC Hard Handover Without an lur Interface.
3.5 ZWF21-03-004 Inter-RAT Mobility
Inter-RAT handover is the procedure which a UE is handed over from one radio access
system to another, and specifically in this chapter, from the UTRAN system to the GSM
system. Inter-RAT handover may be a measurement-based handover between systems
or a blind handover based on the “Overlap or Covers” relationship. The blind handover
between the cells with an overlap relationship can only be triggered by the function of
overload control or load balancing. For the details about overload control, refer to ZTE
UMTS Overload Control Feature Guide. For the details about load balancing, refer to
ZTE UMTS Load Balance Feature Guide.
The prerequisite of measurement-based inter-RAT handover is that the UE measures the

quality of the inter-RAT neighboring cells. In the WCDMA system, for Inter-RAT
measurements in CELL_DCH state, the UE must enable compressed mode for
inter-RAT measurements unless it has dual receivers (for the details about compressed
mode, refer to 3.10 ZWF21-03-010 Compressed Mode). In addition, regarding the
influence of compressed mode on the system and UE, an inter-RAT measurement is
enabled only when the current UTRAN system has poor radio quality. The radio quality of
the current UTRAN system can be measured by four indicators, namely, uplink BLER,
uplink transmitted power of the UE, downlink transmitted power, and the P-CPICH quality
of the current frequency. When receiving the inter-RAT measurement result reported by
the UE, the RNC determines an inter-RAT handover and hands over the UE to the target
cell specified in the measurement result.

Handover Control
This text only describes the inter-RAT handover from UTRAN to GSM based on the
inter-RAT measurement (using Cell Change Order way for PS service). For the
inter-RAT handover based on uplink BLER, refer to ZTE UMTS Quality Based Handover
Feature Guide. For the inter-RAT handover based on uplink or downlink transmitted
power, refer to ZTE UMTS Transmitted Power Based Handover Feature Guide. For the
inter-RAT PS handover from UTRAN to GSM (in the way of HANDOVER FROM UTRAN
COMMAND), refer to ZTE UMTS PS Handover with GSM Feature Guide. For the
inter-RAT handover from UTRAN to LTE, refer to ZTE UMTS Handover with LTE Feature
Guide.
3.5.1 Selection Strategy of Inter-Frequency and Inter-RAT Handover
Please refer to 3.4.1 Selection Strategy of Inter-Frequency and Inter-RAT Handover.
3.5.2 Switch Control Strategy of Measurement-based Inter-RAT Handover

for Services
As the operators have different handover requirements for different services, ZTE RAN
sets the switch of inter-RAT handover based on measurement respectively for services,
which is convenient for operators to configure the network flexibly.
The inter-RAT handover is permitted only when the inter-RAT switch (RatHoSw)
corresponding to the current UE service is enabled. Otherwise, the RNC prohibits
performing an inter-RAT handover for the current service by not starting the inter-RAT
measurement. For the relationships between the RatHoSw and the service configuration
parameters, refer to Table 3-3.
Table 3-3 Relationships between Services and RatHoSw
Service RatHoSw
AMR ULogicalRnc.amrRatHoSw
R99 RT ULogicalRnc.r99RtRatHoSw
R99 NRT ULogicalRnc.r99NrtRatHoSw
HSDPA ULogicalRnc.hsdpaRatHoSw
HSUPA ULogicalRnc.hsupaRatHoSw

Handover Control
3.5.3 Inter-RAT Measurements
Inter-RAT measurements indicate the measurements to the signal quality of an inter-RAT

neighboring cell. ZTE RAN supports two reporting criteria for the inter-RAT
measurements: periodic or event-triggered reporting, and which reporting criterion is
used controlled by URncFunction.IntRatHoMth.
The event-triggered reporting indicates that the UE checks whether the inter-RAT
triggering events of the inter-RAT cells are fulfilled. If yes, the UE reports the inter-RAT
events (including event ID and target cell) to the RNC.
The periodic reporting indicates that the UE regularly reports the quality measurement
results of the inter-RAT cell to the RNC, and the RNC checks whether the inter-RAT
triggering events are fulfilled in accordance with the measurement reporting results. If
yes, the RNC gives the inter-RAT events (including event ID and target cell).
The measurement reporting criteria in this chapter are all event-triggered reporting if
there is no special description. For the periodic reporting criteria, refer to 3.5.11 Periodic
Inter-RAT Measurement Reporting.
The 3GPP has defined a group of inter-RAT measurement events as follows. If the
defined condition is fulfilled, the UE will report the corresponding event to the RNC.
Event 3A: 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, which is used for an inter-RAT handover decision.
Event 3B: The estimated quality of the other system is below a certain threshold, which is
a reserved event.
Event 3C: The estimated quality of the other system is above a certain threshold, which
is used for an inter-RAT handover decision.
Event 3D: Change of the best cell in the other system, which is a reserved event.
An inter-RAT measurement can be triggered in either of the following scenarios:

Handover Control
 The radio quality of the current serving carrier frequency deteriorates, and there are
inter-RAT neighboring cells, and the UE supports the radio frequency band of these
neighboring cells.
Where, “Radio Quality Deterioration of Current Serving Carrier Frequency” can be

determined through any of the following four measurement quantities: the UE
reports event 2D, the uplink BLER exceeds a certain threshold, the transmit power
of the UE exceeds a certain threshold, or the downlink transmit power exceeds a
certain threshold.
 The UE meets the slow moving conditions and there is a micro cell with higher HCS
level in the coverage of the current cell. For details about the handover based on
moving speed, refer to the ZTE UMTS Hierarchical Cell Structures Feature Guide.
 The service-based handover function is enabled, and the service handover value is
set to “Handover to GSM should be performed” or “Handover to GSM should not be
performed” and the radio quality of the current serving carrier frequency is poor
enough to set up an inter-RAT measurement. For details about the service-based
handover, refer to the ZTE UMTS Service-Based Handover Feature Guide.
 The inter-frequency measurement has already been initiated, all non-used

frequencies have triggered event 2E or the URncFunction.T4ShifIfLteGsmMea
timer expires, and inter-RAT neighboring cells exist.
After an inter-RAT measurement is set up, the measurement can be modified if either of
the following conditions is met:
 If the inter-RAT measurement parameters and neighboring cells are changed after
the soft handover, the inter-RAT measurement parameters and neighboring cell list
need to be updated by modifying the measurement control message.
service and concurrent services are different, the inter-RAT measurement

Handover Control
An inter-RAT measurement should be deleted if any of the following conditions is met:
 If the inter-RAT measurement is started before the hard handover, it should be
stopped.
 If either of the following two conditions is fulfilled after a soft handover is performed,
the inter-RAT measurement should be deleted.
 The active set cells do not have an inter-RAT neighboring cell.
 The RNC or cell switch does not allow the UE to be handed over to the
inter-RAT neighboring cell.
 The used frequency quality is improving.
 The value of service handover is changed to “Handover to GSM shall not be
performed”.
 If an abnormal inter-RAT measurement report (for example, a nonexistent
measurement task in the RNC) is received, the corresponding inter-RAT
measurement should be deleted.
time to release the measurement. If the time difference exceeds a threshold (set by the
parameter URncFunction.TResndMeaCtrlRel), the RNC performs measurement deletion
again.
reselection in non-CELL_DCH state and that is used for handover in CELL_DCH

Handover Control
state can be configured separately, which can be indicated by neighboring cell

configuration state. For inter-RAT neighboring cells, it is indicated by
UGsmRelation.GsmStateMode.

 Handover parameter configuration under macro diversity
All measurement parameters are generated based on cells. In the case of macro
Inter-RAT handover parameters can be independently configured in accordance

with the application scenarios, measurement quantities, measurement reporting
criteria and service bearer types. Multiple sets of measurement parameters are
needed for different purposes. The details are described as follows:
Application Outdoor Scene URatMeasProfile.intialHoCelSelSce

Scenario High-Mobility Outdoor ne
Scene
UUtranCellFDD.HoCelSelScene
Indoor Scene
(Note: These two parameters are
Subway/ tunnel Scene
only used for displaying the
scenario, not for indexing handover
parameters, which refers to the
following “Handover parameter
indexing principle”.)
Measuremen UTRAN: UTRAN:

t quantity PCPICH Ec/No UUtranCellFDD.NonIntraMeasQua
PCPICH RSCP n
PCPICH Ec/No and GERAN: RSSI, not controlled by
RSCP any parameter.
GERAN: RSSI

Handover Control
Measuremen Event-triggered reporting URncFunction.IntRatHoMth

t reporting Periodic reporting
criterion
Service RT RAB Including Voice URatMeasSrvSpec.srvCategory

bearer type RT RAB Excluding Voice
on
Single NRT on DL
DCH/UL DCH
HS-DSCH/UL DCH
HS-DSCH/UL E-DCH
DCH/UL DCH
Involved and only DCHs
are Used in UL
Used in UL
Multi RAB Including CS
and PS
Not Related to Service
Type (used for detected
set measurement)
Note:

ii. If the concurrent services contain non-CS RT services, the handover


Handover Control
To modify and optimize parameters more easily, inter-RAT handover parameters

are used based on indexing.
1. For the detailed parameter indexing principle of Event 2D/2F during GSM inter-RAT
handover, see Figure 3-6:
Figure 3-6 Parameter Indexing Principle of Event 2D/2F during GSM Inter-RAT
Handover
UUtranCellFDD
refUInterMeasProfile
UInterMeasProfile
UInterMeaSrvSpec
NonIntraMeasQuan
UInterEcNoEvMeasforG UInterRscpEvMeasforG
InterMeasCfgNo InterMeasCfgNo
i. First, you can obtain an inter-frequency configuration set UInterMeasProfile by

matching UInterMeasProfile.profileId with
UUtranCellFDD.refUinterMeasProfile. Then you can obtain the measurement
object UInterMeaSrvSpec of the corresponding service in the configuration
set.
ii. In the measurement object UInterMeaSrvSpec, you can obtain the current
measurement object (UInterEcNoEvMeasforG or UInterRscpEvMeasforG) in
accordance with the measurement quantity
UUtranCellFDD.NonIntraMeasQuan. Then, you can obtain the
InterMeasCfgNo (inter-frequency measurement configuration number) in
accordance with the service type UInterMeaSrvSpec.srvCategory. Finally, you

Handover Control
can obtain the event 2D/2F parameters of the GSM inter-RAT handover
through the indexing to InterMeasCfgNo. The details are described as follows:
a) If the current frequency measurement quantity is P-CPICH Ec/No, you

can refer to the following table to obtain the parameters that are matched
with InterMeasCfgNo and associated with
UInterEcNoEvMeasforG.InterMeasCfgNo from the
UInterEcNoEvMeasforG object.
GUI Name Parameter
Inter-frequency Event Identity UInterEcNoEvMeasforG.meaEvtId
Event Number of Inter-frequency UInterEcNoEvMeasforG.measEvtNum

Measurement
Filter Coefficient UInterEcNoEvMeasforG.filterCoeff
Hysteresis UInterEcNoEvMeasforG.hysteresis
Time To Trigger UInterEcNoEvMeasforG.TrigTime
Weight of the Currently Used UInterEcNoEvMeasforG.Wused

Frequency for 2D/2F
Absolute Threshold of the Quality UInterEcNoEvMeasforG.ThreshUsedFreq

of the Currently Used Frequency
for 2D/2F
b) If the current frequency measurement quantity is P-CPICH RSCP, you

can refer to the following table to obtain the parameters that are matched
with InterMeasCfgNo and associated with
UInterRscpEvMeasforG.InterMeasCfgNo from the
UInterRscpEvMeasforG object.
GUI Name Parameter
Inter-frequency Event Identity UInterRscpEvMeasforG.meaEvtId
Event Number of Inter-frequency UInterRscpEvMeasforG.measEvtNum

Measurement
Filter Coefficient UInterRscpEvMeasforG.filterCoeff
Hysteresis UInterRscpEvMeasforG.hysteresis
Time To Trigger UInterRscpEvMeasforG.TrigTime
Weight of the Currently Used UInterRscpEvMeasforG.Wused

Frequency for 2D/2F

Handover Control
GUI Name Parameter

Absolute Threshold of the Quality UInterRscpEvMeasforG.ThreshUsedFreq
of the Currently Used Frequency
for 2D/2F
2. For the indexing principle of the Inter-RAT handover event, see Figure 3-7.
Figure 3-7 Parameter Indexing Principle of Inter-RAT handover events
UUtranCellFDD
refURatMeasProfile
URatMeasProfile
URatMeasSrvSpec URatMeasNoSrvSpec
NonIntraMeasQuan NonIntraMeasQuan
URatEcNoEvMeasforG URatRscpEvMeasforG URatEcNoPrdMeas URatEcNoPrdMeas
InterRatCfgNo InterRatCfgNo InterRatCfgNo InterRatCfgNo
i. To obtain the inter-RAT handover parameters, first, you need to obtain the
inter-RAT measurement configuration set URatMeasProfile by matching
URatMeasProfile.profileId with UUtranCellFDD.refURatMeasProfile. Then you
can obtain the measurement object in the next level in accordance with the
reporting criterion currently used by the UE in this configuration set. If the
measurement reporting criterion is event-triggered reporting, you can obtain
the next-level measurement object from the URatMeasSrvSpec object. If the
measurement reporting criterion is periodic reporting, you can obtain the
next-level measurement object from the URatMeasNoSrvSpec object.

Handover Control
ii. If the measurement object obtained in Step i is URatMeasSrvSpec, you can

obtain the current measurement object (URatEcNoEvMeasforG or
URatRscpEvMeasforG) in accordance with the measurement quantity
UUtranCellFDD.NonIntraMeasQuan. Then, you can obtain InterRatCfgNo
(inter-RAT measurement configuration number) in accordance with the service
type URatMeasSrvSpec.srvCategory. If the measurement object obtained in
Step i is URatMeasNoSrvSpec, you can obtain the current measurement
object and InterRatCfgNo (inter-RAT measurement configuration number) in
accordance with the measurement quantity
UUtranCellFDD.NonIntraMeasQuan. Finally, you can obtain the inter-RAT
handover measurement parameters of the current application scenario and
service through the indexing to InterRatCfgNo. The details are described as
follows:
a) If the event-triggered reporting is used, and the UMTS measurement

quantity is P-CPICH Ec/No, you can refer to the following table to obtain
the parameters that are matched with InterRatCfgNo and associated with
URatEcNoEvMeasforG.InterRatCfgNo from the URatEcNoEvMeasforG
object.
GUI Name Parameter
Inter-RAT Event Identity URatEcNoEvMeasforG.EventId
Inter-RAT Measurement Event URatEcNoEvMeasforG.EventNum

Number
UTRAN Filter Coefficient URatEcNoEvMeasforG.FilterCoeff
GSM Filter Coefficient URatEcNoEvMeasforG.GsmFilterCoeff
Hysteresis URatEcNoEvMeasforG.Hysteresis
Time To Trigger URatEcNoEvMeasforG.TrigTime
Weight of the UTRAN System for 3A URatEcNoEvMeasforG.W
Absolute Threshold of the Quality of URatEcNoEvMeasforG.Thresh

UTRAN Cell for 3A
Absolute Threshold of the Quality of URatEcNoEvMeasforG.ThreshSys

Other RAT for 3A/3B/3C
b) If the event-triggered reporting is used, and the UMTS measurement

quantity is P-CPICH RSCP, you can refer to the following table to obtain

Handover Control
the parameters that are matched with InterRatCfgNo and associated with
URatRscpEvMeasforG.InterRatCfgNo from the URatRscpEvMeasforG
object.
GUI Name Parameter
Inter-RAT Event Identity URatRscpEvMeasforG.EventId
Inter-RAT Measurement Event URatRscpEvMeasforG.EventNum

Number
UTRAN Filter Coefficient URatRscpEvMeasforG.FilterCoeff
GSM Filter Coefficient URatRscpEvMeasforG.GsmFilterCoeff
Hysteresis URatRscpEvMeasforG.Hysteresis
Time To Trigger URatRscpEvMeasforG.TrigTime
Weight of the UTRAN System for 3A URatRscpEvMeasforG.W
Absolute Threshold of the Quality of URatRscpEvMeasforG.Thresh

UTRAN Cell for 3A
Absolute Threshold of the Quality of URatRscpEvMeasforG.ThreshSys

Other RAT for 3A/3B/3C
c) If the periodic reporting is used, and the UMTS measurement quantity is

P-CPICH Ec/No, you can refer to the following table to obtain the
parameters that are matched with InterRatCfgNo and associated with
URatEcNoPrdMeas.InterRatCfgNo from the URatEcNoPrdMeas object.
GUI Name Parameter
UTRAN Filter Coefficient URatEcNoPrdMeas.FilterCoeff
GSM Filter Coefficient URatEcNoPrdMeas.GsmFilterCoeff
Amount of Reporting in Period URatEcNoPrdMeas.PrdRptAmount

Report Criteria
Reporting Interval in Period Report URatEcNoPrdMeas.PrdRptInterval

Criteria
d) If the periodic reporting is used, and the UMTS measurement quantity is

P-CPICH RSCP, you can refer to the following table to obtain the
parameters that are matched with InterRatCfgNo and associated with
URatRscpPrdMeas.InterRatCfgNo from the URatRscpPrdMeas object.
GUI Name Parameter
UTRAN Filter Coefficient URatRscpPrdMeas.FilterCoeff

Handover Control
GSM Filter Coefficient URatRscpPrdMeas.GsmFilterCoeff
Amount of Reporting in Period URatRscpPrdMeas.PrdRptAmount

Report Criteria
Reporting Interval in Period Report URatRscpPrdMeas.PrdRptInterval

Criteria
Where,
EventNum
(URatEcNoEvMeasforG.EventNum/URatRscpEvMeasforG.EventNum) and
EventId (URatEcNoEvMeasforG.EventId/URatRscpEvMeasforG.EventId)
control how many events can be configured during the inter-RAT
measurement, and which events should be configured. EventId is defined as
an array whose dimension number is EventNum. The EventNum is configured
up to four because there are a total of four events (3A, 3B, 3C, 3D) in the
inter-RAT measurement. ZTE RAN only supports event 3A and event 3C.
3.5.4 Inter-RAT Event Triggering
To avoid measurement fluctuation during inter-RAT measurements, the UE needs to

perform layer-3 filtering to the measurement results. Then, the UE determines whether
measurement results to the RNC. For the filtering principle and formula, refer to 3.2.3.1
Measurement Result Filtering.
The layer-3 filtering coefficient k during a UTRAN measurement is obtained from the
parameter filterCoeff in the record associated with a certain configuration number based
on the principles described in 3.5.3.4 Parameter Configuration.
The layer-3 filtering coefficient k during a GSM measurement is obtained from the
parameter GsmFilterCoeff in the record associated with a certain configuration number

Handover Control
3.5.4.2 CIO Configuration Strategy
The Cell Individual Offset (CIO) defined by 3GPP is used to control the difficulty level of
event triggering. The tendency of handover can also be controlled by the CIO in actual
scenarios.
 If the target cell is a neighboring cell of the best cell, the CIO is obtained from the
CellIndivOffset in the adjacent relationship configuration of the best cell.
 If the target cell is a neighboring cell of the cells other than the best cell in the active
set, all the CellIndivOffseti in the adjacent relationship configuration of those cells in
the active set are obtained first, and the CIO is the minimum absolute value of
CellIndivOffseti, i=1 ... N. Where, N is the number of cells in the active set that have
the neighbor relation with the target cell.
 If the target cell is not a neighboring cell of any cell in the active set, CIO is zero.
Where, for a GSM neighboring cell, CellIndivOffset is obtained from the parameter
UExternalGsmCell.CellIndivOffset.
If the best cell and the output CIO value change, the RNC informs UEs to update the
CIO.
For the inter-RAT events judgment, to avoid the inter-RAT event misreport due to the
fluctuation of radio quality, if a to-be-evaluated cell meets the reporting range or
threshold of a certain event, the condition must be met for a time (Timetotrigger) before
the reporting of this event. Where, Timetotrigger is obtained from the parameter TrigTime
in the record associated with a certain configuration number based on the principles
described in 3.5.3.4 Parameter Configuration.
Event 3A: 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, which is used for inter-RAT handover decision.

Handover Control
QUsed  TUsed  H3a /2
MOther RAT  CIOOther RAT  TOther RAT  H3a /2

And
Where,
QUsed is the value of the estimated quality of the currently used UTRAN frequency.
TUsed is an absolute threshold of the currently used frequency, which can be obtained
from the parameter TrigTime in the record associated with a certain configuration
H3a is the hysteresis for an event 3A decision. It can be obtained from the parameter
Hysteresis in the record associated with a certain configuration number based on the
MOther RAT is the measurement result of the other system quality;
CIOOther RAT is the quality offset of the other RAT cell (UExternalGsmCell.CellIndivOffset).
TOther RAT is an absolute threshold of the other RAT cell with good quality. It can be
obtained from the parameter ThreshSys in the record associated with a certain
Configuration.
Event 3C: The estimated quality of other system is above a certain threshold, which is
used for inter-RAT handover decision.
MOther RAT  CIOOther RAT  TOther RAT  H3c /2
Where,
MOther RAT is the quality measurement result of the other system.

Handover Control
CIOOther RAT is the quality offset of the other system cell

(UExternalGsmCell.CellIndivOffset).
TOther RAT is an absolute threshold of the other RAT cell with a good quality. It can be
obtained from the parameter Thresh in the record associated with a certain configuration
H3c is the hysteresis for an event 3C decision. It can be obtained from the parameter
Hysteresis in the record associated with a certain configuration number based on the
3.5.5 Inter-RAT Handover Decision and Execution
3.5.5.1 Event 3A/3C Processing
Only event 3A or 3C can trigger an inter-RAT handover in the same cell. Specifically,
which event is used to determine an inter-RAT handover is controlled by the inter-RAT
handover policy parameter UUtranCellFDD.RatHoTactic.
When the quality of the target system meets the handover requirements, the ZTE RNC
performs a handover in accordance with the following principles:
 If only CS service exists, an inter-RAT handover is performed. The handover

procedure is described in 3.5.12.1 CS Service Handover from 3G System to 2G
System.
 If only PS service exists, an inter-RAT handover is performed. The handover

procedure is described in 3.5.12.2 PS Service Reselection in 3G to 2G Handover. In
addition, the cell reselection time for inter-RAT handover can be decreased by
using the NACC function. For details about NACC, refer to the ZTE UMTS NACC
Feature Guide. Moreover, the HANDOVER FROM UTRAN COMMAND message is
used to perform the handover if inter-RAT PS service handover for GSM is
supported. For details, refer to the ZTE UMTS PS Handover with GSM Feature
Guide.
 If a CS service and a PS service exist simultaneously, the PS service is suspended

firstly, and then CS service is handed over to the 2G system and the PS service is

Handover Control
handed over to the 2G system in sequence. However, the concurrent services can
be handed over to the 2G system simultaneously if the inter-RAT DTM handover for
GSM is supported. For details about DTM, refer to the ZTE UMTS DTM Handover
with GSM Feature Guide.
 If the CS domain and PS domain exist simultaneously, and either of them is still in
the RRC stage, the inter-RAT handover is not permitted, which ensures that the
RAB assignment can be completed in the domain in the RRC stage, and increases
the success rate of RAB establishment.
To prevent a UE from being repeatedly handed over to GSM within a short time, which
affects the system performance, the following failure punishment mechanism of
inter-RAT handover is introduced.
If an inter-RAT handover of a UE fails, the RNC starts a penalty timer

(ULogicalRnc.HoToGsmPenTimer) for the UE handover failure. The inter-RAT
measurement report from the UE is not processed before the expiration of the timer, that
is, the inter-RAT handover procedure is not allowed to be executed again within the
duration of the timer. At the expiration of this timer, the inter-RAT measurement will be
initiated again.
In addition, the protocol introduces a function to compare the consistency between

inter-RAT neighboring cells measured by UE and inter-RAT neighboring cells sent by
RNC. The ZTE RAN also provides a selection strategy that indicates whether to perform
the inter-RAT handover when the inter-RAT cell information is inconsistent between the
UE side and the RNC side. The function is controlled by the switch
URncFunction.RatCelInfoSwch.
When the IE “inter-rat cell info indication” is filled into the measurement control message,
if the value of the IE “inter-rat cell info indication” in the inter-RAT measurement report
submitted by the UE is different from that filled in the measurement control message,
follow the following principles:
If URncFunction.RatCelInfoSwch is set to “0: Off”, the measurement report will not be

processed;

Handover Control
If URncFunction.RatCelInfoSwch is set to “1: On”, the measurement report is processed

based on the above handover criteria.
3.5.6 Inter-RAT Event Buffering
If the RNC receives an inter-RAT measurement report but discards it without any
processing because the RNC is busy on other events (for example, Radio Bearer
Reconfiguration) of the UE, the handover opportunity is lost easily and call drops may
occur. Therefore, the measurement report needs to be buffered, and waits for processing
by the RNC after the RNC completes the current event of the UE.
The inter-RAT buffering strategies are described as follows:
 Inter-RAT event buffering supports up to six events.
 For event 2D or 2F for an inter-RAT handover, if the measurement quantity is
“P-CPICH Ec/No” or “P-CPICH RSCP”, only the measurement report that has the
same measurement quantity with UUtranCellFDD.NonIntraMeasQuan can be
buffered. If the measurement quantity is “P-CPICH Ec/No and P-CPICH RSCP”, the
event 2D or 2F of the latest Ec/No and RSCP are buffered.
 If event 3A or 3C exists in the buffer and event 2F is triggered, and if the
measurement quantity of event 2F is the same as the current event, the buffered
event is deleted and event 2F is buffered. Otherwise, event 2F is discarded.
 When event 3A or 3C is reported, if event 2F exists in the buffer and its
measurement quantity is the same with the current measurement, event 3A or 3C is
discarded; otherwise, event 3A or 3C is buffered.
 After the handover is successfully performed, all the measurement reports in the
buffer should be cleared.
3.5.7 Coupling Processing of Different Handovers
Inter-RAT handover can be triggered by the following:
 Load control

Handover Control
 Downlink coverage events
 Uplink transmitted power
 Uplink BLER
 Downlink transmitted power
The load control-based handover aims to quickly reduce system loads and ensure
system stability, and it has the highest priority.
The handovers based on downlink coverage events, uplink transmitted power, uplink
BLER or downlink transmitted power aims to guarantee the call QoS and user
experience, and they have lower priority.
The handover with highest priority will shield the handovers with comparatively lower
priority. For example, if a load control-based handover occurs in a cell, the RNC can no
longer hand over or access new services in the cell.
3.5.8 UMTS->GSM Handover Based on Board Power Off
No matter whether the board power is off or board property is changed, the users
belonging to the corresponding board will be all dropped off, which will influence user
experience. Therefore, the waiting timer is set to control the time of turning off power.
During the waiting timer period, the users in the board can be handed over to the other
system to be served, which improves user experience.
The length of waiting timer is controlled by the parameter

URncFunction.BoardPwrOffHoTmr. When the board power is off, the timer is started.
For the user with a CS service, if there are 2G neighboring cells and all the relative
inter-RAT switches are open, Event 3C will be used in inter-RAT measurements to force
the service to be handed over to the 2G system as soon as possible. For the user with a
CS service that does not meet the conditions of inter-RAT handover, the RRC connection
of the user is released immediately. For the user with only PS services, a DSCR is
directly performed.

Handover Control
When the timer expires, all the services of the users belong to the corresponding board
will be released.
3.5.9 Special UMTS->GSM Handover Strategy based on the Indoor

Neighboring cell
For a 3G cell within the network, when the indoor neighboring cells exist, if the process
strategy for ordinary 2G neighboring cells is still used, a call drop may occur before a
handover can be performed. Therefore, for different 2G neighboring cells of the one 3G
cell, different thresholds for triggering event 2D are configured and different inter-RAT
measurement events are issued. In this way, handovers can be performed timely in
response to the signal changes of indoor cells.
If the following conditions are met, the special UMTS->GSM handover strategy is
performed. That is to issue two sets of measurement (event 3A and 3C) simultaneously,
and only event 3A is processed for ordinary 2G neighboring cells, event 3A or 3C is
processed for indoor 2G neighboring cells.
1. UUtranCellFDD.RatHoTactic is “0: determined by algorithm”.
2. There is at least one GSM neighboring cell whose UExternalGsmCell.IndoorCellInd

is “1: indoor cell”.
3. The value of “service handover” is not “handover to GSM should be performed”.

Inter-RAT Handover
In the procedure of service setup, the relocation from other RNCs to the local RNC, state
transition (FACH to DCH), and best cell change, when the cell meets the conditions of
turning off the carrier power, if the current best cell has only the inter-RAT neighboring
cells, the RNC activates the corresponding inter-RAT compressed mode and performs
an inter-RAT measurement. If inter-frequency and inter-RAT neighboring cells coexist,
the RNC performs the inter-frequency measurement and activates the inter-frequency
compressed mode. After the UE reports event 2E, or the timer Timer_Wait (controlled by
URncFunction.T4ShifIfLteGsmMea) for stopping the inter-frequency measurement and
starting an inter-RAT measurement expires, the RNC reconfigures the measurement to

Handover Control
the inter-RAT measurement and activates compressed mode for the UE. This process is
performed no matter what UCelInfoFDD.IfOrRatHoSwch and the relative inter-RAT
service switches are. For details about “Intelligent Carrier Power Off/On”, refer to the ZTE
UMTS Intelligent Carrier Power off/on Feature Guide.
3.5.11 Periodic Inter-RAT Measurement Reporting
In some scenarios, the inter-RAT handover may not be performed timely due to the long
delay of reporting events. ZTE RAN introduces an inter-RAT handover algorithm for
periodic inter-RAT measurement reporting, to accelerate the inter-RAT handover.
Whether event-triggered reporting or periodic reporting is used in inter-RAT

measurement is determined by the RNC-level parameter IntRatHoMth
(URncFunction.IntRatHoMth).
If IntRatHoMth is set to “0: Periodic Reporting”, and if the conditions for setting up an
inter-RAT measurement are fulfilled, ZTE RNC starts an inter-RAT measurement in
periodic reporting mode, and creates the inter-RAT handover events in accordance with
the conditions of the event-3c-triggering decision based on the inter-RAT neighboring
cell signal quality periodically reported by the UE. Then, a handover procedure is
executed based on the created event.
The subsequent handover processing performed by the RNC is the same as the
event-triggered reporting performed by the UE. For the detailed description, refer to
3.5.5.1 Event 3A/3C Processing. This section only describes how to enable/disable the
periodic reporting measurement and create handover events by the RNC.
3.5.11.1 Periodic Reporting Measurement
For the parameters of periodic reporting measurement, refer to 3.5.3.4 Parameter

Configuration.
The periodic reporting measurement setup, modification and deletion procedures are the
same as the event-triggered reporting measurement, refer to the corresponding
procedures in 3.5.3 Inter-RAT Measurements.

Handover Control
3.5.11.2 Principle for Creating Event 3C
After the UE periodically reports the signal quality of the inter-RAT neighboring cell, the
ZTE RNC makes a decision in accordance with the conditions of the event 3C triggering
decision.
If the conditions of event 3C triggering are satisfied continuously for the duration of
TriggerTime_3c, event 3C is created. Where, TriggerTime_3c is the triggering hysteresis
duration and controlled by the UCelInfoFDD.PeriodTriggerTime parameter.
 Event 3C triggering decision condition:
QTarget_Rat_Cell+ CIOTarget_Rat_Cell>= TTarget_Rat_Cell+H/2
Where,
QTarget_Rat_Cell is the quality of the target system cell.
CIOTarget_Rat_Cell is the quality offset of the target system cell

(UExternalGsmCell.CellIndivOffset).
TTarget_Rat_Cell is the decision threshold of quality of the target system cell. It can be
obtained from the parameter ThreshSys in the record associated with a certain
Configuration.
H is the hysteresis of event 3C, and can be obtained from the parameter hysteresis in the
3.5.11.3 Combination of Inter-RAT Periodic Reporting and Inter-Frequency

Measurement
If the inter-frequency and inter-RAT handover are both allowed, the combination of
inter-RAT periodic reporting measurement and inter-frequency measurement should be
considered.
The detailed strategies are described as follows:

Handover Control
 If the inter-frequency measurement criterion is event-triggered reporting and the

inter-RAT measurement criterion is periodic reporting,
The RNC performs the inter-frequency measurement in event-triggered reporting

and activates the corresponding inter-frequency compressed mode. After the UE
reports event 2E, or the timer Timer_Wait (controlled by
URncFunction.T4ShifIfLteGsmMea) for stopping the inter-frequency measurement
and starting an inter-RAT measurement expires, the RNC reconfigures the
measurement to the inter-RAT periodic reporting measurement and activates
inter-RAT compressed mode.
Where, Timer_Wait is started when the RNC initiates the inter-frequency

measurement in event-triggered reporting.

measurement criterion is periodic reporting,
The RNC starts inter-frequency and inter-RAT measurement in the periodic

reporting criterion at the same time, and simultaneously activates the
inter-frequency and inter-RAT compressed mode.
Where,
The mode of inter-frequency measurement is controlled by URncFunction.InterHoMth.
When the inter-RAT measurement criterion is periodic reporting, only two sets of
compressed modes can be configured for GSM, whose measurement purpose is “GSM
carrier RSSI Measurement” and “GSM Initial BSIC Identification”.

Handover Control
3.5.12 Inter-RAT Handover Process
3.5.12.1 CS Service Handover from 3G System to 2G System
Figure 3-8 3G to 2G CS Service Handover
UE NODE B RNC CN BSC
1. RELOCATION REQUIRED
2. HANDOVER REQUEST
3. HANDOVER REQUEST ACK
4. RELOCATION COMMAND
5. HANDOVER FROM UTRAN COMMAND
6. HANDOVER DETECT
7. HANDOVER COMPLETE
8. HANDOVER COMPLETE
9. IU RELEASE COMMAND
10. RADIO LINK DELETION REQUEST
11. RADIO LINK DELETION RESPONSE
12. IU RELEASE COMPLETE
Procedure description:
1. The RNC sends a RELOCATION REQUIRED message to the CN, requiring the
handover.
2. Upon receiving the message RELOCATION REQUIRED, the CN sends a

HANDOVER REQUEST message to the BSC, requiring the resources.
3. After the resources are established, the BSC sends a HANDOVER REQUEST ACK
message to the CN.
4. Upon receiving the message HANDOVER REQUEST ACK, the CN sends a

RELOCATION COMMAND message to the RNC.

Handover Control
5. Upon receiving the message RELOCATION COMMAND, the RNC sends a

HANDOVER FROM UTRAN COMMAND message to the UE, requiring the UE to
perform a hard handover.
6. If the BSC has already detected the UE, the BSC will send a HANDOVER DETECT
to the CN.
7. The UE returns “HANDOVER COMPLETE” to the BSC to inform the BSC that the
handover is finished.
8. After receiving HANDOVER COMPLETE from the UE, the BSC sends a
HANDOVER COMPLETE message to the CN.
9. Upon receiving the message HANDOVER COMPLETE, the CN sends an IU

RELEASE COMMAND message to the RNC to release all the Iu resources.
10. The RNC sends a RADIO LINK DELETION REQUEST message to the Node B to
release the Iub resources.
11. Upon releasing the Iub resources, the Node B returns a RADIO LINK DELETION
RESPONSE to the RNC.
12. Upon releasing the lu resources, the RNC returns IU RELEASE COMPLETE to the
CN.
Note:
In the process of a CS service handover from UTRAN to GSM, the parameter

URncInfo.rxlevNecellInd is used to control whether to fill the IE “RXLEV-NECELL” in
oldBSS_ToNewBSS of the RELOCATION REQUIRED message. When
URncInfo.rxlevNecellInd is “1:On”, the IE is filled to allow the GSM to select a suitable
frequency.
3.5.12.2 PS Service Reselection in 3G to 2G Handover
If the UE doesn’t support inter-RAT handover for a PS service or the adjacent BSC
doesn’t support the PS service handover, the PS service handover to the GSM is
performed only through cell reselection or the CELL CHANGE ORDER way.

Handover Control
The handover of the PS domain from UTRAN to GSM can be classified into the following
cases:
 The UE actively initiates the PS service reselection.
The UE selects a GPRS cell to dwell through the cell reselection process, sets up a
connection with the target cell, and then initiates a route area update procedure. This
case applies to a UE in CELL_FACH or URA_PCH state.
Figure 3-9 PS service reselection initiated by an UE in the case of 3G to 2G handover
UE Serving
CN
RNC
1. Cell Reselection
triggered
2. Iu Release Command
RANAP RANAP
2. Iu Release Complete
RANAP RANAP
 The RNC actively initiates PS service reselection.
The RNC decides to switch the UE to another RAT cell according to handover decision
results. This case applies to a UE in CELL_DCH state. The RNC sends a handover
command CELL CHANGE ORDER FROM UTRAN to the UE. After receiving the
command, the UE sets up a connection with the target cell, and initiates a route area
update procedure.

Handover Control
Figure 3-10 PS service reselection initiated by the RNC in the case of 3G to 2G

handover
UE BTS BSC CN RNC Node B

(SGSN) Serving
RRC 1. Cell Change Order from UTRAN RRC
2. Reselection to the target GPRS cell; radio link establishment in GSM/BSS
GMM 3. Routing Area Update Request GMM
4. SRNS Context
RANAP Request RANAP
5. SRNS Context
RANAP Response RANAP
6. SRNS Data Forward

RANAP Command RANAP
7. Forwarding of PDUs
8. Iu Release Command
RANAP RANAP
9. Iu Release Complete
RANAP RANAP
GMM 10. Routing Area Update Accept GMM
GMM 11. Routing Area Update Complete GMM
1. Upon detection of a trigger, the SRNC initiates the handover to GSM by sending the
Cell Change Order message to the UE, and starts the timer Timer_waitContextReq
(controlled by URncFunction.TwaitContextReq). Upon reception of the SRNS
Context Request message, the SRNC shall stop the timer. If the
Timer_waitContextReq expires, the SRNC starts the timer Timer_WaitDataFwd
(controlled by URncFunction.TWaitDataFwd).
2. The UE reselects to the target GSM cell and establishes the radio connection to the
GSM.
3. The UE initiates the GPRS Routing Area Update procedure by sending the GMM
message Routing Area Update Request to the SGSN.

Handover Control
4. The SGSN sends the RANAP message SRNS Context Request to the SRNC listing
the PS RABs for which a context transfer shall be performed.
5. The SRNC responds to the SGNS with the RANAP message SRNS Context
Response containing the context information of all referenced PS RABs whose
transfers are successful and starts the timer Timer_WaitDataFwd. Upon reception
of the SRNS Data Forward Command message, the SRNC shall stop the timer. If
Timer_WaitDataFwd expires, the SRNC starts the timer Timer_WaitRelCmd
(controlled by URncFunction.TWaitRelCmd).
6. The SGSN asks the SRNC to forward its buffered data back to the SGSN by
sending the RANAP message SRNS Data Forward Command, and starts the timer
Timer_datafwd (controlled by UIuCnst.Tdatafwd) and Timer_WaitRelCmd. If the
Timer_datafwd expires, the SRNC releases the resource used to forward buffered
data. Upon reception of the IU RELEASE COMMAND message, the SRNC shall
stop the timer Timer_WaitRelCmd. If the Timer_WaitRelCmd expires, the SRNC
releases IU connection.
7. For each PS RAB indicated by the SRNS Data Forward Command, the SRNC
starts duplicating and tunneling the buffered data back to the SGSN.
8. The SGSN sends the RANAP message Iu Release Command to initiate the release
of the Iu connection with UTRAN.
9. At the expiration of the RNC data forwarding timer, the SRNC sends the RANP
message Iu Release Complete message to the SGSN.
10. The SGSN validates the UE’s presence in the new RA by sending the GMM
message Routing Area Update Accept to the UE. The message may contain a new
P-TMSI that the network assigns to the UE.
11. The UE acknowledges the assignment of a new P-TMSI by sending the GMM
message Routing Area Update Complete to the SGSN.

Handover Control
3.6 ZWF21-03-006 Inter-RNC Handover with Iur Support
This chapter mainly describes some special processing for handovers via Iur interface.
For the strategy of the unmentioned part, refer to other chapters of the text.
3.6.1 Parameter Configuration via Iur
 For inter-RNC handovers, if there is a cell belonging to SRNC in the active set, the
measurement parameters of the best cell belonging to SRNC are used as handover
parameters, and if there is no cell belonging to SRNC in the active set, the
measurement parameters of the last cell belong to SRNC that leaves the active set
are used as handover parameters.
 For the cells belonging to a neighboring RNC, if "Primary CPICH Power

Configuration Tag" (UExternalUtranCellFDD.PcpichPwrPre) is “1: True”, the IE "Cell
info" of the intra-frequency measurement should include "Primary CPICH Power"
(UExternalUtranCellFDD.primaryCpichPower) for this neighboring cell. Otherwise,
the IE "Cell info" of the intra-frequency measurement should not include "Primary
CPICH Power" for this neighboring cell.
 If the neighboring RNC is the SRNC, the cell diversity combination criterion is
indicated by UExternalRncFunction.divCtrlInd. If the neighboring RNC is the DRNC,
the cell diversity combination criterion is indicated by
UExternalRncFunction.dIurCmbInd. Where, the “Combined” mode can reduce
transmission resource consumption on the IUR interface, but the support of DRNC
is needed.
3.6.2 Strategy for Soft Handover OD Switch Configuration in the Signaling

Stage
In response to the incompatibility that may occur when the RNCs from different vendors
are connected through the Iur interface, ZTERNC adds a special strategy in the signaling
stage, which is controlled by UIurLink.RncFeatSwitchBit16.
If the SRNC receives event 1A, 1B, 1C or 1D from the DRNC’s cells in the signaling
stage, the event is processed according to the following principles:

Handover Control
 If UIurLink.RncFeatSwitchBit16 is set to “0: Not Process Intra-Frequency Events of

DRNC’s Cell in RRC Procedure”, the RNC does not process the reported event,
that is, the soft handover in the signaling stage is not performed.
 If UIurLink.RncFeatSwitchBit16 is set to “1: Process Intra-Frequency Events of

DRNC’s Cell in RRC Procedure”, the RNC processes the reported event as usual.
3.6.3 Special Events Processing via Iur for CS+PS
For the concurrent service of the CS service and PS service of a UE through the Iur
interface, a call drop may occur due to the incompatibility of different vendors’ equipment.
In response, the ZTE RNC executes the special strategy of handover via Iur interface for
the concurrent service.
If the following conditions are both met, the RNC does not process event 1A, 1C or 1D
reported by the cell of the DRNC, that is, not add the link into the active set.
(1). UIurLink.RncFeatSwitchBit15 is set to “0: Not handle Event 1A/1C/1D reported by

DRNC”.
(2). The concurrent service of a CS service and PS service for a UE exist.
3.6.4 Special Events Processing via Iur for Only PS
For the PS-only services of a UE through the Iur interface, dropped calls may occur due
to the incompatibility of different vendors’ devices. In response, the RNC executes the
special strategy for handover through the Iur interface for the PS-only services.
If the following conditions are met, the RNC does not process event 1A or 1C reported by
the cell of DRNC, that is, not add the link into the active set. If event 1D is reported
subsequently, the RNC performs relocation triggered by hard handover or DSCR.

DRNC”.
(2). The UE has only PS services.

Handover Control
3.6.5 Special Events Processing via Iur for Only CS
For a CS only service of a UE through the Iur interface, a call drop may occur due to the
incompatibility of different vendors’ equipment. In response, the RNC executes the
special strategy of handover through the Iur interface for the CS only service.
If the following conditions are met, the RNC does not process event 1A, 1C or 1D
reported by the cell of DRNC, that is, not add the link into the active set.

DRNC”.
(2). UCelInfoFDD.CsIntraEvtSwch is set to “1: On”.
(3). The UE has only CS service.
3.6.6 Special Events Processing via Iur for PS0/0
For the PS0/0 kbps service via Iur interface, the call drop may occur due to the
incompatibility of different vendors’ equipment. In response, the RNC executes the
special strategy of handover via Iur interface for the PS0/0 service.
If the following conditions are met, the RNC does not process the events 1A/1C/1D or
2A/2B/2C reported by the cell of DRNC, and releases the PS0/0 service while receiving
those events, which is convenient for processing the follow-up reported events and
performing the handover.
(1). UIurLink.RncFeatSwitchBit18 is set to “0: Not Support PS(0 kbps /0 kbps)”.
(2). The PS 0/0 kbps service exists currently.

Handover Control
3.6.7 Inter-RNC Handover Through the lur Interface
3.6.7.1 Inter-RNC Soft Handover (Adding a Radio Link)
Figure 3-11 Intra-RNC Soft Handover (Adding a Radio Link)
UE Node B Drift Serving

Drift RNS RNC RNC
Decision to setup
new RL
1. Radio Li nk Setup
RNSAP Request RNSAP
2. Radio Link Setup

NBAP Request NBAP
Start RX
description
3. Radio Link Setup
Response
NBAP NBAP
4. Radio Link Setup
Response
RNSAP RN SAP
5. ALCAP Iub Bearer Setup ALCAP Iur Bearer Setup
6. Radio Link Restore

Indication
NBAP NBAP
7. Radio Link Restore
Indication
RNSAP RNSAP
8. Downlink Synchronisation
DCH - FP DCH - FP
9. Uplink Synchronisation
DCH - FP DCH - FP
Start TX
description
10. DCCH : Active Set Update
RRC RRC
[Radio Link Addition]
11. DCCH : Active Set Update Complete

RRC RRC

Handover Control
3.6.7.2 Inter-RNC Soft Handover (Deleting a Radio Link)
Figure 3-12 Intra-RNC Soft Handover (Deleting a Radio Link)
UE Node B Drift Serving

Drift RNS RNC RNC
Decision to delete
old RL
1. DCCH : Active Set Update

RRC RRC
[Radio Link Deletion]
2. DCCH : Active Set Update Complete

RRC RRC
3. Radio Link Deletion

Request
RNSAP RNSAP
Request
NBAP NBAP
Stop RX and TX

Response
NBAP NBAP
Response
RNSAP RNSAP
7. ALCAP Iub Bearer Release ALCAP Iur Bearer Release

Handover Control
3.6.7.3 Inter-RNC Soft Handover (Swapping a Radio Link)
Figure 3-13 Intra-RNC Soft Handover (Swapping a Radio Link)
UE N ode B N ode B D rift S erv in g

D rift R N S S ervin g R N S RNC RNC
D ecisio n to setu p
n ew R L an d
release o ld R L
1 . R ad io L in k S etu p
R eq u est
RN SAP RN SAP
2 . R ad io L in k S etu p R eq u est
NBAP NBAP
S tart R X
d escrip tio n
NBAP 3 . R ad io L in k S etu p R esp o n se NBAP
4 . R ad io L in k S etu p
R esp o n se
RN SAP RN SAP
5 . A L C A P Iu b D ata T ran sp o rt B earer S etu p A L C A P Iu r B earer S etu p
NBAP 6 . R ad io L in k R esto re In d icatio n NBAP

7 . R ad io L in k R esto re
In d icatio n
RN SAP RN SAP
D C H -F P 8 . D o w n lin k S yn ch ro n isatio n
D C H -F P
9 . U p lin k S yn ch ro n isatio n
D C H -F P D C H -F P
S tart T X
d escrip tio n
1 0 . D C C H : A ctiv e S et U p d ate C o m m an d
RRC RRC
[R a d io L in k A d d itio n & D eletio n ]
1 1 . D C C H : A ctiv e S et U p d ate C o m p lete

RRC RRC
1 2 . R ad io L in k D eletio n R eq u est
NBAP NBAP
S to p R X an d T X
1 3 . R ad io L in k R elease R esp o n se
NBAP NBAP
1 4 . A L C A P Iu b D ata T ran sp o rt B earer R elease

Handover Control
3.6.7.4 Inter-RNC Hard Handover Through lur Interface
Figure 3-14 Inter-RNC Hard Handover Through lur Interface
UE Node B Node B RNC RNC SRNC

Source Target Source target
1. Radio Link
RNSAP Setup Request RNSAP
2. Radio Link Setup Request

NBAP NBAP
NBAP 3. Radio Link Setup Response NBAP
4. ALCAP Iub Data Transport Bearer Setup
5. RL Setup
RNSAP Response RNSAP
6. ALCAP Iur Data

Transport Bearer Setup
7. DCCH : Physical Channel Reconfiguration
RRC RRC
8. Radio Link Failure Indication

NBAP NBAP
RNSAP 9. Radio Link Failure Indication RNSAP
NBAP 10. Radio Link Restore Indication NBAP
11. RL Restore
RNSAP Indication RNSAP
12. DCCH : Physical Channel Reconfiguration Complete
RRC RRC
RNS AP 13. Radio Link Deletion Request RNSAP
14. Radio Link Deletion Request

NBAP NBAP
15. Radio Link Deletion Response

NBAP NBAP
16. ALCAP Iub Data Transport Bearer Release
RNSAP 17. Radio Link Deletion Response RNSAP
18. ALCAP Iur Data

Transport Bearer Release
If the cells belonging to different RNCs are adjacent and the lur interface is available, the
SRNC performs an inter-RNC hard handover. SRNC relocation is triggered after the hard
handover.

Handover Control
3.7 ZWF21-03-020 SRNS Relocation
SRNS relocation can be categorized into the relocation of a UE not involved (soft
handover-triggering) and the relocation of a UE involved (hard handover-triggering).
They are described respectively as follows.
3.7.1 Relocation Triggered by Soft Handover
In the relocation triggered by soft handover, the UE can use radio resources in the DRNC
and connect with the CN through the SRNC.
If the following conditions are all met, a relocation triggered by soft handover is triggered.
 There is an Iur interface between RNCs.
 The switch for relocation of the UE not involved is on. It is differentiated by the CS
service and PS service, UIurLink.RncFeatSwitchBit10 is for CS service and
UIurLink.RncFeatSwitchBit11 is for PS service.
 When all radio links are handed over to the DRNC and the relocation waiting timer
expires.
Where,
The relocation waiting timer is differentiated by the CS service and PS service,

UIurLink.CsReDelayTimer is for CS service and UIurLink.PsReDelayTimer is for PS
service. For the concurrent service of CS service and PS service, the timer is
obtained from UIurLink.CsReDelayTimer.
After all radio links are handed over to the DRNC, the relocation waiting timer is
started.

Handover Control
Figure 3-15 Relocation Triggered by Soft Handover
Source Target
SGSN
RNC RNC
1.Relocation Required
2.Relocation Request
3.Relocation Request Ack
4.Relocation Command
5.Relocation Commit
6.Relocation Detect
7.UTRAN Mobility
Information
8.UTRAN Mobility UE
Information Confirm
9.Relocation Complete
10.Iu Release Command
11.Iu Release Complete
1. Upon detecting that all links already exist in a DRNC, the SRNC initiates the
relocation procedure and sends a “Relocation Required” message to the CN. If the
SRNC connects with the CS and PS domains, it needs to send the “Relocation
Required” message to the CS and PS domains. When the SRNC sends the
“Relocation Required” message, it starts the timer TRELOCprep (indicated by
UIuCnst.Trelocprep). Upon receiving the “Relocation Command” message, the
SRNC stops the timer and terminates the Relocation Preparation procedure. If there
is no response from the CN to the “Relocation Required” message before the timer
TRELOCprep expires, the SRNC cancels the Relocation Preparation procedure by
initiating the Relocation Cancel procedure with the cause “TRELOCprep expiry”.
2. The CN sends a “Relocation Request” message to the DRNC, carrying the “RAB
SETUP” IE.
3. After the RAB of DRNC is established successfully, the DRNC sends a “Relocation
Request ACK” message to the CN.

Handover Control
4. The CN sends a “Relocation Command” message to the SRNC, requiring the

SRNC to start the relocation. Upon receiving the Relocation Command message,
the SRNC stops the timer TRELOCprep, starts the timer TRELOCoverall (indicated by
UIuCnst.Trelocoverall) and terminates the Relocation Preparation procedure. If the
Iu Release procedure is not initiated towards the SRNC from the CN before the
expiry of TRELOCoverall, the SRNC initiates the Iu Release Request procedure towards
the CN with cause “TRELOCoverall expiry”.
5. The SRNC sends a “Relocation Commit” message to the DRNC through the lur
interface.
6. The DRNC sends a “Relocation Detect” message to the CN and is converted into a
new SRNC through role exchange.
7. The new SRNC sends a “UTRAN Mobility Information” message to the UE to

reallocate U-RNTI.
8. Upon relocating U-RNTI, the UE sends a “UTRAN Mobility Information Confirm”

message to the new SRNC.
9. The new SRNC sends a “Relocation Complete” message to inform the CN of the
successful relocation.
10. Upon receiving the message from the new SRNC, the CN sends an “Iu Release
Command” message to the original SRNC to release all the resources in the original
SRNC.
11. Upon releasing the lu resource, the original SRNC sends an “Iu Release Complete”
message to the CN.
Note:
 The timing of sending Relocation Detect mentioned above in step 6, also the timing
of converting the DRNC into a new SRNC, can also be triggered when the DRNC
receives the UTRAN Mobility Information Confirm message from UE. The function
is controlled by URncInfo.sendDetetOcca. If URncInfo.sendDetetOcca is set to “0”,
the DRNC sends Relocation Detect until UTRAN Mobility Information Confirm is
received from the UE.

Handover Control
 Initializing the RNC data forwarding function during the relocation can reduce the
data loss in the process of sending UMI. The function is controlled by the parameter
UIurLink.RncFeatSwitchBit25. If UIurLink.RncFeatSwitchBit25 is set to “1: On”, the
SRNC forwards the data of the CN to user plane of the DRNC, the DRNC buffers
the data, and sends the data to the UE after being converted into a new SRNC.
There may be some exceptional procedures during the relocation.
 Relocation failure caused by “UTRAN Mobility Information” message transmission

failure
The DRNC fails to initiate the “UTRAN Mobility Information Configuration” procedure
because the procedure times out or the UE return a UTRAN mobility failure
message. In such a case, the DRNC does not send a “Relocation Complete”
message to the CN, but sends an “Iu Release Request” message to the CN to
release the resources on the DRNC side.
What “procedure timeout” means: The DRNC initiates the timer (400ms) after
sending a “UTRAN Mobility Information” (UMI) message to the UE. If the DRNC
cannot receive the UMI confirm message from the UE until the timer expires, the
DRNC resends the UMI message, and repeats the process up to four times. When
the DRNC sends the UMI message for the fourth time, and the UMI confirm
message is not received when the timer expires, this case is regarded as
“procedure timeout”.
3.7.2 Relocation Triggered by Hard Handover
In the relocation triggered by hard handover, the relocation is performed along with the
handover.
If the following conditions are both met, a relocation triggered by hard handover is
triggered.
 The conditions of hard handover are met and the target cell does not belong to the
SRNC.

Handover Control
 The switch of relocation triggered by hard handover corresponding to the current

service is set to “1: On”.
 For CS service, the switch of relocation UIurLink.RncFeatSwitchBit0 is set to

“1: On”.
 For PS service, the switch of relocation UIurLink.RncFeatSwitchBit19 is set to

“1: On”.
 For the concurrent service of the CS service and PS service, the switch of
relocation UIurLink.RncFeatSwitchBit0 is set to “1: On”.
Figure 3-16 Relocation Triggered by Hard Handover
Source Target
SGSN
RNC RNC
1.Relocation Required
2.Relocation Request
3.Relocation Request Ack
4.Relocation Command
5.Physical Channel
Reconfiguration
UE
6.UE detected by target RNC
7.Relocation Detect
8.Physical Channel
Reconfiguration Complete
UE
9.Relocation Complete
10.Iu Release Command

11.Iu Release Complete
1. The SRNC initiates a “Relocation Required” message to the CN and starts the timer
TRELOCprep (indicated by UIuCnst.Trelocprep). Upon receiving the “Relocation
Command” message, the SRNC stops the timer and terminates the Relocation
Preparation procedure. If the timer TRELOCprep expires, the SRNC cancels the
Relocation Preparation procedure by initiating the Relocation Cancel procedure
with the cause “TRELOCprep expiry”.
2. Upon receiving the message, the CN sends a “Relocation Request” message to the
DRNC.

Handover Control
3. After the bearer on the lu interface and the radio link are established, the DRNC
returns a “Relocation Request ACK” message to inform the CN that the DRNC is
ready.
4. The CN sends a “Relocation Command” message to the SRNC, requiring the

SRNC to start the relocation. Upon receiving the Relocation Command message,
the SRNC stops the timer TRELOCprep, starts the timer TRELOCoverall (indicated by
UIuCnst.Trelocoverall). If the Iu Release procedure is not initiated towards the
SRNC from the CN before the expiry of TRELOCoverall, the SRNC initiates the Iu
Release Request procedure towards the CN with cause “TRELOCoverall expiry”.
5. The SRNC sends a “Physical Channel Reconfiguration” message to the UE,

requiring the UE to perform a hard handover.
6. The DRNC initiates a “UE Detect” message to imply that the DRNC already detects
the UE.
7. Upon detecting the UE, the DRNC sends a “Relocation Detect” message to the CN,
and then the DRNC is converted into a new SRNC through role exchange.
8. The UE returns a “Physical Channel Reconfiguration Complete” message to inform

the new SRNC of successful hard handover.
9. Upon receiving the message, the new SRNC sends a “Relocation Complete”
message to the CN.
10. Upon receiving the message from the new SRNC, the CN sends an “Iu Release
Command” message to the original SRNC to release all the resources in the original
SRNC.
11. Upon releasing the lu resource, the original SRNC sends an “Iu Release Complete”
message to the CN.
Note:
 Initializing the RNC data forwarding function during the relocation can reduce the
data loss in the process of sending UMI. The function is controlled by the parameter
UIurLink.RncFeatSwitchBit25. If UIurLink.RncFeatSwitchBit25 is set to “1: On”, the

Handover Control
SRNC forwards the data of the CN to user plane of the DRNC, the DRNC buffers
the data, and sends the data to the UE after being converted into a new SRNC.
There may be some exceptional procedures during the relocation.
 Relocation failure caused by radio bearer (RB) reconfiguration failure
Upon receiving the RB reconfiguration failure message, the SRNC sends a

relocation cancellation message to the CN and the CN releases the resources on
the DRNC side through the lu release procedure.
3.7.3 Special Relocation Processing of CS+PS Services
If the UE has CS and PS services simultaneously and the DRNC does not support PS
relocation, the PS services will be released before an SRNC relocation triggered by hard
handover is performed, to ensure the CS service performance.
The control strategy:
When UE has the concurrent service of CS service and PS service and the conditions of
hard handover are met, if UIurLink.RncFeatSwitchBit4 is set to “1: Support Hard
Handover DSCR”, the RNC releases PS services, and then performs the relocation for
CS service.
3.7.4 Optimization of Dual-Domain Relocation
Before a relocation process, if either of the domains is still in the RRC stage, the
relocation is not permitted, which ensures that the RAB assignment can be completed in
the domain, the success rate of RAB establishment is increased, and the system
performance is improved.

Handover Control
3.8 ZWF21-03-008 Directed Signaling Connection

Re-establishment
3.8.1 DSCR in Dedicated Status
As the SRNC relocation, DSCR is categorized into hard handover DSCR and soft
handover DSCR.
The triggering conditions of DSCR are described as follows.
 Soft handover DSCR
When all radio links are handed over to the DRNC and the relocation is not
performed, the DSCR is triggered if the following conditions are all met:
 The switch of soft handover DSCR UIurLink.RncFeatSwitchBit77 is set to “1:

On”.
 No CS service is included.
 Hard handover DSCR
When the conditions of hard handover are met and the target cell does not belong to
the SRNC, the DSCR will be triggered if the following conditions are all met:
 The switch of hard handover DSCR UIurLink.RncFeatSwitchBit4 is set to “1:

On”.
 No CS service is included.
3.8.2 DSCR in Common Status
To avoid the UE from staying in common status continuously without any chance for
transferring a large amount of data due to the failure to switch to CELL_DCH, the
following strategy is introduced:

Handover Control
When the UE fails to transfer from common status to Cell_DCH status with the cause of
invalid configuration, if URncFunction.dscrInCmnToDedSwch is set to “1: On”, the RNC
executes the DSCR procedure, making the UE enter IDLE status and reestablish an
RRC connection.
3.8.3 Coupling between Relocation and DSCR
The DSCR is performed first when the conditions of relocation and DSCR are met
simultaneously.
 DSCR and hard handover relocation
 If there are only PS services, a DSCR is performed when the conditions of

relocation and DSCR are met simultaneously.
 If CS service exists, the relocation is performed.
 DSCR and soft handover relocation
 If there are only PS services, when the conditions of DSCR are met, DSCR is
performed.
 If there is only CS service, the relocation is performed.
 For the concurrent service of CS service and PS services, if the conditions of

DSCR for PS services are met, then DSCR is performed after CS service is
released.
3.9 ZWF21-03-011 Neighboring Cells Priorities
When the UE is in macro diversity state, the neighboring cell list is a combination of
neighboring cell lists of each cell in the active set, so the number of intra-frequency,
inter-frequency or inter-RAT neighboring cells may exceed 32, which is the maximum
number specified by the protocol. If the number of intra-frequency, inter-frequency or
inter-RAT neighboring cells exceeds 32, some cells must be deleted to ensure that there
are only 32 neighboring cells to be sent to UEs. With minimal impact on the UEs in the
active set, these dropped cells are those with poorer signal quality or remoter

Handover Control
geographical location. Therefore, each of the intra-frequency, inter-frequency or

inter-RAT neighboring cells is configured with a priority, that is, the neighboring cells are
sorted according to the configured measurement priority.
3.9.1 Cell Priority Configuration
The measurement priority of neighboring cells is configured for intra-frequency or

inter-frequency neighboring cells and inter-RAT neighboring cells respectively.
If the neighboring cells are intra-frequency or inter-frequency neighboring cells, the

measurement priority is indicated by UUtranRelation.MeasPrio. If the neighboring cells
are inter-RAT neighboring cells, the measurement priority is indicated by
UGsmRelation.MeasPrio. Where, the measurement priority has three values: 0: High
priority; 1: Medium priority; 2: Low priority. The neighboring cells with lower priority are
prior deleted.
The value of measurement priority is configured by the network planning engineer based
on the existing network conditions (for example, neighboring cell quality and
geographical location of neighboring cell).
Figure 3-17 is the schematic diagram of configuring the cell priority based on
geographical location. For example, for the configuration of cells adjacent to the
innermost gray cell, there are three layers of neighboring cells surrounding the gray cell,
and they are differentiated from one another with yellow (0: Top priority), blue (1: Medium
priority) and red (2: Low priority).

Handover Control
Figure 3-17 Cell Priority Configuration
Source Cell
Priority 0
Priority 1
Priority 2
3.9.2 Strategy for Neighboring Cells Exceeding 32
As specified in the protocol, the maximum number of intra-frequency, inter-frequency or

inter-RAT neighboring cells is 32 (the source cell is included in intra-frequency). When
the UE is in macro diversity state, the total number of intra-frequency, inter-frequency or
inter-RAT neighboring cells in the macro diversity may exceed 32, so some strategies
are required to control the number within 32, including:
 Priority combination strategy
If a cell is adjacent to several cells in the active set, that is, the priority levels configured
for this cell may vary, the priority levels of this cell are combined and the highest priority
level prevails.
 Sorting strategy
If the total number of intra-frequency, inter-frequency or inter-RAT neighboring cells in

the active set is 32, the system prioritizes them in descending order and places the cells
in excess of 32 into the intra-frequency, inter-frequency or inter-RAT neighboring cell

Handover Control
reserve list. The intra-frequency neighboring cell reserve list can buffer at most 64
truncated cells, and the inter-frequency or inter-RAT neighboring cell reserve list can
buffer at most 8 truncated cells.
The priority levels of neighboring cells in the intra-frequency, inter-frequency or inter-RAT

neighboring cell list will be updated whenever event 1A, 1B, 1C or 1D is triggered. If
event 1B is triggered and the number of neighboring cells is less than 32, the system
selects cells from the reserve list in descending order of priority and places them into the
neighboring cell list. The number of cells that can be selected: min (32 – Number of
existing cells in the neighboring cell list, Number of cells in the reserve list).
3.10 ZWF21-03-010 Compressed Mode
3.10.1 Introduction to Compressed Mode
For non-double-receiver terminals in WCDMA, compressed mode must be initiated for

inter-frequency or inter-RAT measurement. When compressed mode is used, some slots
are specially used for inter-frequency or inter-RAT measurement instead of data
transmission during transmission and reception.
A UE supports to configure several sets of compressed mode parameters for different

measurement purposes (indicated by UCompressMode.MeasPurpose). The meanings
of each measurement purpose are as follows:
 FDD measurement
 GSM carrier RSSI measurement
 GSM Initial BSIC identification
 GSM BSIC re-confirmation
 E-UTRA measurement.
In the following part, the compressed mode configuration is introduced in detail, which is
applied to all measurement purposes if there is no special description.
The following two ways can generate compressed mode frames:

Handover Control
1 Halving of Spreading Factor (SF)
By halving the SF, the bandwidth can be increased so that some slots in one radio
frame can be specially assigned for inter-frequency or inter-RAT measurement and
some can be specially assigned for data transmission. This transmission strategy is
generally used in services that have high requirements for delay and minimum data
rate, for example, CS- and S-type PS data services.
2 Higher Layer Scheduling
The higher layer scheduling is in nature a strategy in which the higher layer adjusts
and controls the data transmission rate. Some slots in a radio frame can be specially
assigned for inter-frequency or inter-RAT measurement and some can be specially
assigned for data transmission while the bandwidth remains unchanged. This
strategy is generally used for non-real-time services that have low requirements for
delay, for example, I/B-type PS data services.
Different methods are used for the uplink and downlink. For the uplink, the method is
determined by UCompressMode.UlCMMethod, while for the downlink, the method is
fixed at “Halving of Spreading Factor”. Moreover, whether the compressed mode is
applied in uplink, downlink or both is controlled by UCompressMode.UlDlMode.
For a downlink compressed mode frame, the protocol defines two frame types: type A
and type B, as shown in Figure 3-18. Type A indicates that the TPC command is not
transmitted in the transmission gap, which maximizes the transmission gap length. Type
B indicates that the TPC command is transmitted in the transmission gap, which is
optimized for power control. The selection of a frame type is controlled by
UCompressMode.DlFrameType. In general, type A is used, because the transmit power
adjustment can be achieved by the strategy applied in the slots after the transmission
gap.
Figure 3-18 Downlink Compressed Mode Frame Type
Slot # (Nfirst - 1) transmission gap Slot # (Nlast + 1)
T TF T TF
Data1 P CI Data2 PL PL Data1 P CI Data2 PL
C C

Handover Control
(a) Frame type A
Slot # (Nfirst - 1) transmission gap Slot # (Nlast + 1)
T TF T T TF
Data1 P CI Data2 PL P PL Data1 P CI Data2 PL
C C C
(b) Frame type B
Figure 3-19 shows the parameters involved in compressed mode.
Figure 3-19 Compressed Mode Parameters
#1 #2 #3 #4 #5 #TGPRC
TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1
TG pattern 1
Transmission Transmission
gap 1 gap 2
TGSN
TGL1 TGL2
TGD
TGPL1
Where,
The Transmission Gap Pattern Sequence (TGPS) consists of consecutive TG

patterns (TG pattern 1). The length of a TG pattern is indicated by the parameter
UCompressMode.TGPL1, and the repeated times of which is indicated by the
parameter UCompressMode.TGPRC.
One or two TGs are defined in a TG pattern. The starting slot number of the first TG
is determined by the parameter UCompressMode.TGSN. The number of slots
between starting slots of two TGs in the TG pattern is determined by the parameter
UCompressMode.TGD. The first Transmission Gap Length (TGL) is determined by

Handover Control
the parameter UCompressMode.TGL1, and the second by the parameter

UCompressMode.TGL2. In TS 25.212, the TGL can be set to 3, 4, 5, 7, 10 and 14
slots. If UCompressMode.TGD is not configured, it means that there is only one TG
in the TG pattern, and the value of UCompressMode.TGL2 is invalid.
The TG may start from any slot in a frame and can be placed either within one radio
frame or between two radio frames, as shown in Figure 3-20. When the TG spans two
consecutive frames, each frame at least has eight non-compressed slots.
Figure 3-20 Transmission Gap (TG) Position
Transmission gap Radio frame
#0 #Nfirst-1 #Nlast+1 #14

(1) Single-frame method
Transmission gap
First radio frame Second radio frame
#0 #Nfirst-1 #Nlast+1 #14

(2) Double-frame method
For compressed mode used for GSM inter-RAT measurement, if the measurement
purpose is “GSM Initial BSIC identification”, the TG patten maximum repetition number
(N_Identify_abort) of TG patterns that the UE shall use to attempt to decode the
unknown BSIC of the GSM cell is indicated by the parameter UCompressMode.NIdAbort.
When the measurement purpose is “GSM BSIC re-confirmation”, the longest time length
(T_Reconfirm_abort) allowed for BSIC re-confirmation of one GSM cell is indicated by
the parameter UCompressMode.TrecfgAbort.
3.10.2 Compressed Mode Strategy
 Activate compressed mode
If UE capability information indicates that compressed mode is required during an

FDD inter-frequency or inter-RAT measurement procedure, compressed mode is
initiated upon the initiation of an inter-frequency or inter-RAT measurement.

Handover Control
 Deactivate compressed mode
Compressed mode must be disabled in either of the following scenarios:
i. Deleting the inter-frequency measurement while keeping the inter-RAT

measurement disabled.
ii. Deleting the inter-RAT measurement while keeping the inter-frequency

measurement disabled.
 Compressed mode parameters
In the ZTE network, compressed mode parameters are configured for different
measurement purposes instead of different services.
The compressed mode parameters associated with

UCompressMode.MeasPurpose that matches the actual measurement purpose
can be obtained from the UCompressMode object. In addition to those parameters
defined by the protocol, which are described in 3.10.1 Introduction to Compressed
Mode, there are some parameters as follows defined specially based on the
problems in actual application.
TGCFN Hysteresis Coefficient (UCompressMode.K): The parameter is used for

correcting the time of the starting of the transmission gap pattern, introduced by
considering the Node B interleaving, UE de-interleaving and transmission delay.
TGCFN Offset (UCompressMode.TGCFNOffset): Typically, TGCFN for the first

TGPS is set to 0, indicating that compressed mode must be started as soon as
possible. The other TGPSs must have an offset to the first TGPS so that it is
ensured that there is only one transmission gap in a frame. Otherwise, an error will
occur when the transmission gaps collide. Therefore, the parameter is introduced to
indicate the offset of the position of TGPS relative to the first frame for which
compressed mode is enabled.
Special processing: If uplink compressed mode method SF/2 is configured but has
not been activated, and currently the services are using the minimum SF4 and
compressed mode needs to be activated, the RNC can modify it to higher layer
scheduling method.

Handover Control
 Compressed mode parameter configuration
The ZTE RAN supports two ways to configure the compressed mode parameters:
associated mode and dedicated mode, which is selected according to the scenario,
and is controlled by parameters for some scenarios
 For state transitions from common state to dedicated state, the RNC does not
configure the parameters for compressed mode in associated mode, so that
the signaling message length of the radio interface can be decreased, and the
parameters for compressed mode are configured in dedicated mode when
compressed mode needs to be activated.
 For hard handovers, the configuration mode of compressed mode parameters

is controlled by the bit3 of URncFunction.GResPara56. If the bit3 of
URncFunction.GResPara56 is set to 0, the associated mode is used. If it is set
to 1, the dedicated mode is used.
 For other procedures, such as service setup, state transition (excluding the
transition from common state to dedicated state), call re-establishment,
relocation from other RNCs to the local RNC, and soft handover, the
configuration mode of compressed mode parameters is controlled by the bit4
of URncFunction.GResPara56. If the bit4 of URncFunction.GResPara56 is set
to 0, the associated mode is used. If it is set to 1, the dedicated mode is used.
If the associated mode is selected, the RNC configures the parameters for
compressed mode in associated mode through the RADIO BEARER SETUP or
RADIO BEARER RECONFIGURATION or PHYSICAL CHANNEL
RECONFIGURATION message to UE and the RADIO LINK SETUP REQUEST or
RADIO LINK RECONFIGURATION message to NodeB while the procedure occurs.
Figure 3-21 shows the procedure for configuring the parameters for compressed
mode in associated mode.
If the dedicated mode is selected, when the compressed mode needs to be

initialized (for example, event 2D is reported), the RNC configures the parameters
for compressed mode in dedicated mode through the PHYSICAL CHANNEL
RECONFIGURATION or RADIO BEARER RECONFIGURATION message to the
UE and the RADIO LINK RECONFIGURATION message to the Node B. Figure

Handover Control
3-22 shows the procedure for configuring the parameters for compressed mode in
dedicated mode.
Note: TGCFN in the following figure indicates the time when compressed mode is
activated.
Figure 3-21 Procedure for Configuring Parameters for Compressed Mode in

Associated Mode
UE NodeB RNC CN
RAB Assignment Request

Radio Link Reconfiguration Prepare
(Transmission Gap Pattern Sequence Information
->TGSN, TGL1, TGPL1…)
Service setup, Radio Link Reconfiguration Ready
configure
accompanying Radio Bearer Setup
compressed mode (DPCH compressed mode info-> TGPRC,TGSN,TGL1…)
Radio Link Reconfiguration Commit

Radio Bearer Setup Complete
RAB Assignment Response
……
Measurement Control
(DPCH compressed mode status info->TGCFN)
Active
Compressed Mode Command
compressed mode (Active Pattern Sequence Information
->TGCFN)

Handover Control
Figure 3-22 Procedure for Configuring Parameters for Compressed Mode in Dedicated
Mode
UE NodeB RNC CN
RAB Assignment Request

Radio Link Reconfiguration Ready
Radio Bearer Setup
Service setup
Radio Bearer Setup Complete

RAB Assignment Response
……
Need to initialize the
compressed mode(such as event
2D is reported)

(Transmission Gap Pattern Sequence Information
->TGSN, TGL1, TGPL1…)
Radio Link Reconfiguration Ready

Configure Dedicated
compressed mode Physical Channel Reconfiguration
(DPCH compressed mode info-> TGPRC,TGSN,TGL1…)

Physical Channel Reconfiguration Complete
……
Measurement Control
(DPCH compressed mode status info->TGCFN)
Active compressed
mode Compressed Mode Command
(Active Pattern Sequence Information
->TGCFN)
3.10.3 Compressed Mode Configuration Strategy via RNC
In response to an incompatibility that may occur when the RNCs from different vendors
are connected through the Iur interface, the following strategies are introduced to
guarantee the normal procedure via Iur interface.
 The strategy for the case that other vendors do not support configuring the
parameters for compressed mode by accompanying mode.
Whether a neighbor RNC supports configuring the parameters for compressed

mode by accompanying mode is indicated by the switch
UIurLink.RncFeatSwitchBit9.
If compressed mode has not been activated on the SRNC side, the way of
configuring compressed mode is decided by UIurLink.RncFeatSwitchBit9.

Handover Control
If compressed mode has been activated already on the SRNC side,

UIurLink.RncFeatSwitchBit9 is invalid, and the SRNC configures the parameters for
compressed mode by accompanying mode and activates compressed mode for the
DRNC.
 The strategy for the case that other vendors conditionally support configuring the
parameters for compressed mode by accompanying mode.
Some vendors do not support configuring the parameters for compressed mode by
accompanying mode for inter-frequency and inter-RAT simultaneously, but ZTE
RAN does. ULogicalRnc.CompMdCfgStra is introduced to control how to configure
the parameters for compressed mode by accompanying mode. If
ULogicalRnc.CompMdCfgStra is set to “0: Configure Inter-Frequency and Inter-Rat
compressed mode simultaneously”, and inter-frequency and inter-RAT neighboring
cells exist, the RNC configures two types of parameters for compressed mode
(inter-frequency and inter-RAT) by accompanying mode.
If ULogicalRnc.CompMdCfgStra is set to “1 Configure Inter-Frequency and

Inter-Rat compressed mode individually”, the RNC configures only one type of
parameters for compressed mode (inter-frequency or inter-RAT) by accompanying
mode based on the strategy in 3.4.1 Selection Strategy of Inter-Frequency and
Inter-RAT Handover.
 The strategy for the case that other vendors do not allow the use of compressed
mode by the compressed mode command through the Iur interface
Some vendors do not allow the use of compressed mode by the compressed mode
command via Iur interface, so UIurLink.RncFeatSwitchBit17 is introduced for this
situation.
If UIurLink.RncFeatSwitchBit17 is set to “0: Not Activate Compressed Mode for CS

service When Radio Link via IUR exists”, only the CS service exists for the UE and
the UE has the Iur links, and the compressed mode of the UE is not activated, the
SRNC does not activate compressed mode for the UE even when needed.
If UIurLink.RncFeatSwitchBit17 is set to “1: Activate Compressed Mode for CS

service When Radio Link via IUR exists”, for the case that only the CS service

Handover Control
exists for the UE and the UE has the Iur links, the SRNC can activate compressed
mode when needed.
4 Parameters
4.1 ZWF21-03-001 Soft/Softer Handover
Table 4-1 Soft/Softer Handover Parameters List
Recom
Parameter Value Default
GUI Name Parameter Description Unit mended
Name Range Value
Value
1. This parameter indicates the

threshold of the time when an
RNC resends the
MEASUREMENT CONTROL
RELEASE message.
When the RNC sends the
MEASUREMENT CONGROL
RELEASE message for a
measurement ID, the time
stamp is recorded. If the RNC
The Time
receives the report with the
Threshold that
measurement ID, it compares
URncFuncti the RNC May
the current time with the (1..255)s,
on.TResnd Resend the s 30s 30s
recorded time. If the step 1s
MeaCtrlRel MEASUREME
difference between the
NT CONTROL
current time and the recorded
RELEASE
time exceeds the threshold
configured, the
MEASUREMENT CONTROL
RELEASE message is resent;
otherwise, this measurement
report is discarded and the
MEASUREMENT CONTROL
RELEASE message is not
resent.
This parameter is used to

Handover Control
Recom
Name Range Value
Value
control the sending frequency
for the MEASUREMENT
CONTROL RELEASE
message.

scenario of the neighboring
cell.
When SIB11 is to be sent, the 0: cell
cells that support "cell selection/r
selection/reselection" are eselection
2: cell 2: cell
UE State selected from the neighboring only
selectio selectio
Indicator Used cell list and written to SIB11; 1:
UUtranRelat n/resele n/resele
for UTRAN When SIB12 is to be sent, the handover
ion.StateMo N/A ction ction
Neighboring method is the same as that for only
de and and
Cell SIB11; 2:cell
handove handove
Configuration When the measurement selection/r
r r
control message is to be sent, eselection
the cells that support and
"handover" are selected from handover
the neighboring cell list and
written to the measurement
control message.
3. 0: Outdoor
Scene
1:
This parameter indicates High-Mobil
UIntraMeas typical handovers and cell ity Outdoor
Mobility 0: 0:
Profile.intial reselection scenarios. For Scene
Configuration N/A Outdoor Outdoor
HoCelSelSc each scenario, the 2: Indoor
Scene Scene Scene
ene corresponding parameter can Scene
be set to different values. 3:
Subway/
tunnel
Scene
4. UUtranCellF Mobility This parameter indicates 0: Outdoor 0: 0:

DD.HoCelS Configuration typical handovers and cell Scene N/A Outdoor Outdoor
elScene Scene reselection scenarios. For 1: Scene Scene

Handover Control
Recom
Name Range Value
Value
each scenario, the High-Mobil
corresponding parameter can ity Outdoor
be set to different values. Scene
2: Indoor
Scene
3:
Subway/
tunnel
Scene

measurement quantity for
UTRAN intra-frequency
measurement. For
intra-frequency scenarios,
Cpich Ec/No is generally used
because the main factor that
UTRAN
affects signal quality is 0: Ec/No
UUtranCellF Measurement
intra-frequency interference. 1: RSCP
DD.IntraMe Quantity for N/A 0: Ec/No 0: Ec/No
But if the cell is located at the 2: Ec/No
asQuan Intra-frequency
edge of the coverage area, and RSCP
Measurements
where the main factor that
affects signal quality is the
distance between the cell and
the base station, Cpich RSCP
is used. "Cpich EcNo and
RSCP" is not used in the
current version.
6. This parameter distinguishes 0: RT RAB 0: RT 0: RT

handover parameter Including RAB RAB
configurations based on Voice Includin Includin
Service and
services and bearer types. 1: RT RAB g Voice g Voice
Bearer Type
UIntraMeas Handover-related parameter Excluding 1: RT 1: RT
Used for
SrvSpec.srv configurations, for example, Voice N/A RAB RAB
Differentiating
Category handover triggering threshold, 2: Single Excludin Excludin
Handover
hysteresis, vary based on NRT on g Voice g Voice
Configuration
different service DL 2: Single 2: Single
characteristics. Based on the DCH/UL NRT on NRT on
real-time feature, channel DCH DL DL

Handover Control
Recom
Name Range Value
Value
types and the number of 3: Single DCH/UL DCH/UL
RABs, services are divided NRT RAB DCH DCH
into nine types for different on DL 3: Single 3: Single
parameter configurations. The HS-DSCH/ NRT NRT
value 0xff corresponds to the UL DCH RAB on RAB on
periodic measurement or 4: Single DL DL
detected set measurement, NRT RAB HS-DSC HS-DSC
which must be used in all on DL H/UL H/UL
services. HS-DSCH/ DCH DCH
UL E-DCH 4: Single 4: Single
5: All NRT NRT
Multi-NRT RAB on RAB on
RAB on DL DL
DL HS-DSC HS-DSC
DCH/UL H/UL H/UL
DCH E-DCH E-DCH
6: 5: All 5: All
Multi-NRT Multi-NR Multi-NR
RAB, T RAB T RAB
HSPA is on DL on DL
Involved DCH/UL DCH/UL
and only DCH DCH
DCHs are 6: 6:
Used in UL Multi-NR Multi-NR
7: T RAB, T RAB,
Multi-NRT HSPA is HSPA is
RAB, Involved Involved
HSPA is and only and only
Involved DCHs DCHs
and are are
E-DCH is Used in Used in
Used in UL UL UL
8:Multi 7: 7:
Rab Multi-NR Multi-NR
Including T RAB, T RAB,
CS and PS HSPA is HSPA is
0xff: Not Involved Involved
Related to and and

Handover Control
Recom
Name Range Value
Value
Service E-DCH E-DCH
Type is Used is Used
in UL in UL
8: Multi 8: Multi
Rab Rab
Includin Includin
g CS g CS
and PS and PS
0xff: Not 0xff: Not
Related Related
to to
Service Service
Type Type

ID of the intra-frequency
measurement profile object. A
UUtranCellF Used
profile corresponds to a set of
DD.ref1Uintr Intra-frequency
intra-frequency measurement N/A N/A 0 0
aMeasProfil Measurement
configurations. Each cell
e Profile
obtains the intra-frequency
measurement parameters
based on the profile ID.

profile ID of a set of
intra-frequency measurement
UIntraMeas Intra-frequency
parameters. Each cell obtains Set by Set by
Profile.profil Measurement 0~99 N/A
the intra-frequency system system
eId Profile Identity
measurement parameters in
accordance with the profile
ID.

configuration index of the
UIntraEcNo Intra-frequency
EvMeas.Intr Measurement Set by Set by
parameters, which is used to 0..65535 N/A
aMeasCfgN Configuration system system
index different parameter
o Index
configuration sets for
intra-frequency

Handover Control
Recom
Name Range Value
Value
measurement. There are
several different sets of
measurement values for the
same set of parameters
according to specific
measurement purpose,
measurement quantity and so
on.

event ID triggered by the
1a[0],
intra-frequency
1b[1],
UIntraEcNo measurement. 1a,1b,1c 1a,1b,1c
Intra-frequency 1c[2],
EvMeas.Me MAX_INTRA_MEAS_EVENT N/A ,1d,1e,1f ,1d,1e,1f
Event Identity 1d[3],
aEvtId indicates the maximum ,1j ,1j
1e[4],
number of intra-frequency
1f[5], 1j[6]
measurement event, which is
7.
11. This parameter indicates

number of events required to
be configured for the set of
the intra-frequency
1..MAX_IN
measurement parameters for
TRA_MEA
a certain purpose. The
Event Number S_EVENT
UIntraEcNo number of the events is
of Where
EvMeas.Me related to the purpose of the N/A 7 7
Intra-frequency MAX_INT
asEvtNum measurement and the
Measurement RA_MEAS
judgment method of the soft
_EVENT
handover. The measurement
=7.
parameter of the soft
handover is related to the
number of the events in the
soft handover algorithm.
12. This parameter indicates the (0[0],

UIntraEcNo filtering factor that UE 1[1], 2[2],
Filter
EvMeas.Filt performs the L3 filtering on 3[3], 4[4], N/A 2 2
Coefficient
erCoeff the measurement results of 5[5], 6[6],
the intra-frequency 7[7], 8[8],

Handover Control
Recom
Name Range Value
Value
measurement. 9[9],
UE executes intra-frequency 11[10],
measurement on L1 in the 13[11],
fixed cycle (measure several 15[12],
points in one measurement 17[13],
cycle and L1 filters the 19[14])
measurement results. This
method can be decided by UE
freely). Then L1 reports to L3
at intervals and L3 filters the
latest measurement results
and the measurement results
saved previously. The filtering
shall be performed according
to the following formula
described in 3GPP TS
25.331: "RRC Protocol
Specification": Fn=
(1-a)*Fn-1+a*Mn , a = 1/2^
(k/2) .
Fn is the updated filtered
measurement result
Fn-1 is the previous filtered
measurement result
Mn is the latest received
measurement result
a = 1/2^ (k/2), where the value
of k is the Filter Coefficient.
NOTE: if k is set to 0 that will
mean no layer 3 filtering.
This formula indicates that the
smaller the value of the
filtering factor is, the larger
effect the current
measurement result will have
on the measurement result
reported to RNC (periodic
report) or the judgment (event

Handover Control
Recom
Name Range Value
Value
report).
13. This parameter is used for

quality judgment of event 1a
and 1b,which indicates the
weight of the best cell in the
quality judgment and is
0.0,0.0,0 0.0,0.0,0
UIntraEcNo Weight for related to the measurement (0.0..2.0),
N/A .0,0.0,0. .0,0.0,0.
EvMeas.W Event 1A/1B quantity and the event type. step 0.1
0,0.0,0.0 0,0.0,0.0
MAX_INTRA_MEAS_EVENT
indicates the maximum
7.

hysteresis used when judging
whether to trigger the event.
This parameter makes it
different between the status to
trigger an event and the
status to leave the event, so
as to avoid the trigger status
change due to very small
change.
The larger the value is, the
UIntraEcNo larger the difference between
0,0,4,4,2 0,0,4,4,2
EvMeas.Hys Hysteresis the status to trigger the event (0..7.5)dB, dB
,2,4 ,2,4
teresis and the status to leave the step 0.5dB
event will be.
This parameter is related to
the measurement quantity
and the event type.
Different events are
configured separately and
can be configured with
different hysteresis

Handover Control
Recom
Name Range Value
Value
7.

reporting range for event
1a/1b, used to control the
extent of difficulty in adding a
cell into the active set or
dropping a cell from the active
Reporting
UIntraEcNo set. 1a is easier but 1b is
Range (0..14.5)d 3,5,0,0,0 3,5,0,0,0
EvMeas.Rpt harder to trigger when this dB
Constant for B, step ,0,0 ,0,0
Range value increases; and vice
Event 1A/1B 0.5dB
versa.
measurement events, which
is 7.

time difference between
having detected the event (0[0],
generation and reporting the 10[1],
event. Only when the event 20[2],
generation is detected and 40[3],
still meets all requirements of 60[4],
event triggering after Time to 80[5],
trigger, the event can be 100[6],
200,640, 200,640,
UIntraEcNo triggered and reported. The 120[7],
320, 320,
EvMeas.Trig Time To Trigger larger the value is, the stricter 160[8], ms
320,200, 320,200,
Time the judgment is for the event 200[9],
200,320 200,320
to be The 240[9],
triggered.
parameter should be set 320[10],
according to the actual 640[11],
requirements. Sometimes, if it 1280[12],
is set too large, the quality of 2560[13],
calls may decrease. 5000[14])
MAX_INTRA_MEAS_EVENT ms

Handover Control
Recom
Name Range Value
Value
7.

maximum number of times
that a measurement report is
sent after event 1a/1b/1c/1j is
triggered (because they are
reported periodically). After
event 1a/1b/1c/1j is triggered,
the UE reports the
measurement results
according to the report
intervals. If the number of
(1[0],
times that an event is
Amount of 2[1], 4[2], 4,4,4,Infi 4,4,4,Infi
UIntraEcNo reported exceeds the value of
Reporting for 8[3], 16[4], nity,Infin nity,Infin
EvMeas.Evt this parameter, the UE stops N/A
Event 32[5], ity,Infinit ity,Infinit
RptAmount reporting the measurement
1A/1B/1C/1J 64[6], y,4 y,4
results. If the result of
Infinity[7])
judgment indicates that event
1a/1b/1c/1j finishes, stop
reporting the measurement
results even the number of
report do not reach the value
of this parameter.
is 7.

(0[0],
time interval to report the
250[1],
measurement results after 2000,20 2000,20
Reporting 500[2],
UIntraEcNo event 1a/1b/1c/1j is triggered 00,2000, 00,2000,
Interval for 1000[3],
EvMeas.Evt (because they are reported ms 500,500, 500,500,
Event 2000[4],
RptInterval periodically). After event 500,200 500,200
1A/1B/1C/1J 4000[5],
1a/1b/1c/1j is triggered, the 0 0
8000[6],
UE reports the measurement
16000[7])
results according to the report

Handover Control
Recom
Name Range Value
Value
intervals. ms
is 7.

minimum number of the cells
that can exist in the DCH
active set when event 1c is
triggered, or in the E-DCH
active set when event 1j is
triggered. When UE detects
that one cell satisfies the
trigger threshold of event
Replacement
1c/1j, it first checks whether
UIntraEcNo Activation (0, 1, 2,
the number of the cells in the 0,0,3,0,0 0,0,3,0,0
EvMeas.Rpl Threshold for 3, 4, 5, 6, N/A
current active set is smaller ,0,3 ,0,3
cActThr Event 1C and 7)
than the value indicated by
1J
this parameter. If so, event
1c/1j is not triggered. If the
value is 0, the parameter is
invalid.
7

maximum number of the cells
that can exist in active set.
Reporting When the UE detects that one
UIntraEcNo (0, 1, 2,
Deactivation cell in the monitoring set 2,0,0,0,0 2,0,0,0,0
EvMeas.Rpt 3, 4, 5, 6, N/A
Threshold for satisfies the threshold of ,0,0 ,0,0
DeactThr 7)
Event 1A event 1a, it first judges
whether the number of the
cells in the current active set
is not bigger than the value

Handover Control
Recom
Name Range Value
Value
indicated by this parameter. If
so, event 1a is triggered. If
not, event 1a is not triggered.
7.

parameters, which is used to
UIntraRscp Intra-frequency
intra-frequency
EvMeas.Intr Measurement Set by Set by
measurement. There are 0..65535 N/A
aMeasCfgN Configuration system system
o Index
on.

event ID triggered by the
1a[0],
intra-frequency
1b[1],
UIntraRscp measurement. 1a,1b,1c 1a,1b,1c
Intra-frequency 1c[2],
EvMeas.Me MAX_INTRA_MEAS_EVENT N/A ,1d,1e,1f ,1d,1e,1f
Event Identity 1d[3],
aEvtId indicates the maximum ,1j ,1j
1e[4],
1f[5], 1j[6]
7.
23. This parameter indicates 1..MAX_IN

Event Number
UIntraRscp number of events required to TRA_MEA
of
EvMeas.Me be configured for the set of S_EVENT N/A 7 7
Intra-frequency
asEvtNum the intra-frequency Where
Measurement
measurement parameters for MAX_INT

Handover Control
Recom
Name Range Value
Value
a certain purpose. The RA_MEAS
number of the events is _EVENT
related to the purpose of the =7.
measurement and the
judgment method of the soft
handover. The measurement
parameter of the soft
handover is related to the
number of the events in the
soft handover algorithm.

filtering factor that UE
performs the L3 filtering on
the measurement results of
the intra-frequency
measurement.
UE executes intra-frequency
measurement on L1 in the
fixed cycle (measure several
(0[0],
points in one measurement
1[1], 2[2],
cycle and L1 filters the
3[3], 4[4],
5[5], 6[6],
UIntraRscp 7[7], 8[8],
Filter freely). Then L1 reports to L3
EvMeas.Filt 9[9], N/A 3 3
Coefficient at intervals and L3 filters the
erCoeff 11[10],
latest measurement results
13[11],
and the measurement results
15[12],
saved previously. The filtering
17[13],
shall be performed according
19[14])
to the following formula
described in 3GPP TS
Specification": Fn=
(1-a)*Fn-1+a*Mn , a = 1/2^
(k/2) .
measurement result

Handover Control
Recom
Name Range Value
Value
measurement result
measurement result
effect the current
report).

0.0,0.0,0 0.0,0.0,0
UIntraRscp Weight for related to the measurement (0.0..2.0),
N/A .0,0.0,0. .0,0.0,0.
EvMeas.W Event 1A/1B quantity and the event type. step 0.1
0,0.0,0.0 0,0.0,0.0
7.

UIntraRscp
different between the status to 4,4,6,6,4 4,4,6,6,4
EvMeas.Hys Hysteresis (0..7.5)dB, dB
trigger an event and the ,4,6 ,4,6
teresis step 0.5dB
change.

Handover Control
Recom
Name Range Value
Value
larger the difference between
the status to trigger the event
and the status to leave the
event will be.
and the event type.
7.

Reporting
UIntraRscp set. 1a is easier but 1b is
Range (0..14.5)d 6,8,0,0,0 6,8,0,0,0
EvMeas.Rpt harder to trigger when this dB
Constant for B, step ,0,0 ,0,0
Range value increases; and vice
Event 1A/1B 0.5dB
versa.
is 7.

time difference between 10[1], 200,200, 200,200,
UIntraRscp
having detected the event 20[2], 200,200, 200,200,
EvMeas.Trig Time To Trigger ms
generation and reporting the 40[3], 200,200, 200,200,
Time
event. Only when the event 60[4], 200 200

Handover Control
Recom
Name Range Value
Value
triggered and reported. The 200[9],
larger the value is, the stricter 240[9],
the judgment is for the event 320[10],
to be triggered. The 640[11],
requirements. Sometimes, if it 5000[14])
is set too large, the quality of ms
calls may decrease.
7.

the UE reports the
(1[0],
measurement results
Amount of 2[1], 4[2], 4,4,4,Infi 4,4,4,Infi
UIntraRscp according to the report
Reporting for 8[3], 16[4], nity,Infin nity,Infin
EvMeas.Evt intervals. If the number of N/A
Event 32[5], ity,Infinit ity,Infinit
RptAmount times that an event is
1A/1B/1C/1J 64[6], y,4 y,4
reported exceeds the value of
Infinity[7])
this parameter, the UE stops

Handover Control
Recom
Name Range Value
Value
of this parameter.
is 7.

measurement results after
event 1a/1b/1c/1j is triggered (0[0],
(because they are reported 250[1],
periodically). After event 500[2], 2000,20 2000,20
Reporting
UIntraRscp 1a/1b/1c/1j is triggered, the 1000[3], 00,2000, 00,2000,
Interval for
EvMeas.Evt UE reports the measurement 2000[4], ms 500,500, 500,500,
Event
RptInterval results according to the report 4000[5], 500,200 500,200
1A/1B/1C/1J
intervals. 8000[6], 0 0
MAX_INTRA_MEAS_EVENT 16000[7])
indicates the maximum ms
is 7.

minimum number of the cells
that can exist in the DCH
active set when event 1c is
triggered, or in the E-DCH
active set when event 1j is
Replacement triggered. When UE detects
UIntraRscp Activation that one cell satisfies the (0, 1, 2,
0,0,3,0,0 0,0,3,0,0
EvMeas.Rpl Threshold for trigger threshold of event 3, 4, 5, 6, N/A
,0,3 ,0,3
cActThr Event 1C and 1c/1j, it first checks whether 7)
1J the number of the cells in the
current active set is smaller
than the value indicated by
this parameter. If so, event
1c/1j is not triggered. If the
value is 0, the parameter is
invalid.

Handover Control
Recom
Name Range Value
Value
7

When the UE detects that one
cell in the monitoring set
satisfies the threshold of
event 1a, it first judges
Reporting whether the number of the
UIntraRscp (0, 1, 2,
Deactivation cells in the current active set 2,0,0,0,0 2,0,0,0,0
EvMeas.Rpt 3, 4, 5, 6, N/A
Threshold for is not bigger than the value ,0,0 ,0,0
DeactThr 7)
Event 1A indicated by this parameter. If
7.

parameters, which is used to
UIntraEcNo Intra-frequency configuration sets for
EvMeasFor Measurement intra-frequency Set by Set by
0..65535 N/A
D.IntraMeas Configuration measurement. There are system system
CfgNo Index several different sets of

Handover Control
Recom
Name Range Value
Value
on.

the intra-frequency
measurement.
cycle and L1 filters the
freely). Then L1 reports to L3 (0[0],
at intervals and L3 filters the 1[1], 2[2],
latest measurement results 3[3], 4[4],
and the measurement results 5[5], 6[6],
UIntraEcNo saved previously. The filtering 7[7], 8[8],
Filter
EvMeasFor shall be performed according 9[9], N/A 3 3
Coefficient
D.FilterCoeff to the following formula 11[10],
described in 3GPP TS 13[11],
25.331: "RRC Protocol 15[12],
Specification": Fn= 17[13],
(1-a)*Fn-1+a*Mn , a = 1/2^ 19[14])
(k/2) .
measurement result
measurement result
measurement result

Handover Control
Recom
Name Range Value
Value
effect the current
report).

UIntraEcNo
Weight for related to the measurement (0.0..2.0),
EvMeasFor N/A 0 0
Event 1A/1B quantity and the event type. step 0.1
D.W
7.

UIntraEcNo
EvMeasFor
Hysteresis change. (0..7.5)dB, dB 2 2
D.Hysteresi
The larger the value is, the step 0.5dB
s
event will be.
and the event type.

Handover Control
Recom
Name Range Value
Value
7.

Reporting
UIntraEcNo set. 1a is easier but 1b is
Range (0..14.5)d
EvMeasFor harder to trigger when this dB 4 4
Constant for B, step
D.RptRange value increases; and vice
Event 1A/1B 0.5dB
versa.
is 7.

time difference between 10[1],
having detected the event 20[2],
generation and reporting the 40[3],
event. Only when the event 60[4],
UIntraEcNo still meets all requirements of 100[6],
EvMeasFor Time To Trigger event triggering after Time to 120[7], ms 200 200
D.TrigTime trigger, the event can be 160[8],

Handover Control
Recom
Name Range Value
Value
calls may decrease.
7.

the UE reports the
measurement results
according to the report
intervals. If the number of
(1[0],
times that an event is
UIntraEcNo Amount of 2[1], 4[2],
reported exceeds the value of
EvMeasFor Reporting for 8[3], 16[4],
this parameter, the UE stops N/A 1 1
D.EvtRptAm Event 32[5],
ount 1A/1B/1C/1J 64[6],
Infinity[7])
of this parameter.
is 7.
40. UIntraEcNo Reporting This parameter indicates the (0[0],

EvMeasFor Interval for time interval to report the 250[1], ms 2000 2000
D.EvtRptInt Event measurement results after 500[2],

Handover Control
Recom
Name Range Value
Value
erval 1A/1B/1C/1J event 1a/1b/1c/1j is triggered 1000[3],
periodically). After event 4000[5],
1a/1b/1c/1j is triggered, the 8000[6],
UE reports the measurement 16000[7])
results according to the report ms
intervals.
is 7.

UIntraEcNo Reporting whether the number of the
(0, 1, 2,
EvMeasFor Deactivation cells in the current active set
3, 4, 5, 6, N/A 6 6
D.RptDeact Threshold for is not bigger than the value
7)
Thr Event 1A indicated by this parameter. If
7.

UIntraRscp Intra-frequency intra-frequency measurement
EvMeasFor Measurement parameters, which is used to Set by Set by
0..65535 N/A
D.IntraMeas Configuration index different parameter system system
CfgNo Index configuration sets for
intra-frequency

Handover Control
Recom
Name Range Value
Value
on.

the intra-frequency
measurement.
cycle and L1 filters the (0[0],
measurement results. This 1[1], 2[2],
method can be decided by UE 3[3], 4[4],
freely). Then L1 reports to L3 5[5], 6[6],
UIntraRscp at intervals and L3 filters the 7[7], 8[8],
Filter
EvMeasFor latest measurement results 9[9], N/A 3 3
Coefficient
D.FilterCoeff and the measurement results 11[10],
saved previously. The filtering 13[11],
shall be performed according 15[12],
to the following formula 17[13],
described in 3GPP TS 19[14])
Specification": Fn=
(1-a)*Fn-1+a*Mn , a = 1/2^
(k/2) .
measurement result
measurement result
measurement result

Handover Control
Recom
Name Range Value
Value
effect the current
report).

UIntraRscp
Weight for related to the measurement (0.0..2.0),
EvMeasFor N/A 0 0
Event 1A/1B quantity and the event type. step 0.1
D.W
7.

UIntraRscp
EvMeasFor
Hysteresis status to leave the event, so (0..7.5)dB, dB 6 6
D.Hysteresi
as to avoid the trigger status step 0.5dB
s
change.

Handover Control
Recom
Name Range Value
Value
event will be.
and the event type.
7.

Reporting
UIntraRscp set. 1a is easier but 1b is
Range (0..14.5)d
EvMeasFor harder to trigger when this dB 7 7
Constant for B, step
D.RptRange value increases; and vice
Event 1A/1B 0.5dB
versa.
is 7.

time difference between 10[1],
having detected the event 20[2],
UIntraRscp generation and reporting the 40[3],
EvMeasFor Time To Trigger event. Only when the event 60[4], ms 200 200
D.TrigTime generation is detected and 80[5],

Handover Control
Recom
Name Range Value
Value
calls may decrease.
7.

the UE reports the
measurement results
according to report (1[0],
the
UIntraRscp Amount of intervals. If the number of 2[1], 4[2],
EvMeasFor Reporting for times that an event is 8[3], 16[4],
N/A 1 1
D.EvtRptAm Event reported exceeds the value of 32[5],
ount 1A/1B/1C/1J this parameter, the UE stops 64[6],
reporting the measurement Infinity[7])
of this parameter.

Handover Control
Recom
Name Range Value
Value
is 7.

measurement results after
event 1a/1b/1c/1j is triggered (0[0],
periodically). After event 500[2],
UIntraRscp Reporting
1a/1b/1c/1j is triggered, the 1000[3],
EvMeasFor Interval for
UE reports the measurement 2000[4], ms 2000 2000
D.EvtRptInt Event
results according to the report 4000[5],
erval 1A/1B/1C/1J
intervals. 8000[6],
MAX_INTRA_MEAS_EVENT 16000[7])
indicates the maximum ms
is 7.

UIntraRscp Reporting whether the number of the
(0, 1, 2,
EvMeasFor Deactivation cells in the current active set
3, 4, 5, 6, N/A 6 6
D.RptDeact Threshold for is not bigger than the value
7)
Thr Event 1A indicated by this parameter. If
7.
51. UUtranRelat Cell Individual Cell individual offset. An offset (-50..50) dB 0dB 0dB

Handover Control
Recom
Name Range Value
Value
ion.CellIndiv Offset is allocated to each cell that is dB step 1
Offset monitored. The offset can be Db
positive or negative. Before
the UE determines whether
an event occurs, the offset
should be added to the
measurement result. If the
PCPICH uses a positive
offset, the UE sends the
measurement report just like
PCPICH is x dB better than
the actual case. Or, if the
PCPICH uses a negative
offset, the PCPICH report is
limited. When the cell
individual offset is used, the
corresponding cell may be (at
least temporarily) the target
cell for handovers or removed
from the active set.
52. Cell individual offset. An offset

is allocated to each cell that is
monitored. The offset can be
the UE determines whether
an event occurs, the offset
UUtranCellF (-50..50)
Cell Individual PCPICH uses a positive
DD.CellIndiv dB step 1 dB 0dB 0dB
Offset offset, the UE sends the
idualOffset Db

Handover Control
Recom
Name Range Value
Value

penalty duration of
intra-frequency handover
failure. When a link to be
added into the active set is
URncInfo.H Intra-frequency
rejected in Event 1A/1C, the (0..255)s,
oToIntraPen Handover s 5s 5s
timer is initiated, and the RNC step 1s
Timer Penalty Timer
will not handle the
event 1A/1C reported by this
rejected cell until the timer
expires.
54. This parameter is a switch

that determines whether the
RNC supports parallel
transmission of messages
over the Iub and Uu interfaces
during soft handover.
Switch of RNC When the switch is turned on,
Send RL the RNC sends an active set
SETUP and update message over the Uu
URncFuncti
ACTIVE SET interface and an RL SETUP 0: Off
on.ParallelS N/A 1: On 1: On
UPDATE message over the Iub 1: On
oftHO
parallelly when interface in parallel during the
Soft Add soft handover procedure.
Handover When the switch is turned off,
the RNC completes the RL
SETUP procedure on the Iub
interface first, and then starts
the active set update
procedure on the Uu
interface.
55. UUtranCellF Detected Set This parameter the 0: Off

starts
N/A 1: On 1: On
DD.DetSetH Handover detected set switch for cells. If 1: On

Handover Control
Recom
Name Range Value
Value
oSwch Switch the switch is "On", when the
number of neighboring cells
exceeds 32 and the cells are
reduced, the RNC needs to
indicate UE to report the
measurement of the detected
set in measurement control.
When the target cell in the
detected set report submitted
by the UE belongs to the cell
list that is cut because it
contains more than 32 cells,
the RNC can perform a
handover.

Neighbouring whether an RNC should 0:Not
ULogicalRn 0: Not 0: Not
Cell Monitoring monitor neighboring cells. supported
c.NbrCellMo N/A Support Support
Support When the parameter is set to 1:Supporte
nSupInd ed ed
Indicator 1, the RNC starts to monitor d
the neighboring cells.

whether to adjust the radio
link reference time in macro
diversity mode. It is used to
prevent the radio link
sending/receiving time in
macro diversity mode from
Switch for RL locating outside the receiving
ULogicalRn
Reference Time time window. When this 0: Off
c.rlRefTime N/A 0: Off 0: Off
Adjust During parameter is set to Off, the 1: On
AjtSw
Diversity Mode UE internal measurement
(Event 6G/6F) used to trigger
the radio link reference time
adjustment is not performed.
When this parameter is set to
On, the UE internal
measurement (Event 6G/6F)
used to trigger the radio link

Handover Control
Recom
Name Range Value
Value
reference time adjustment is
performed. Note: The UE
internal measurement and UE
quality measurement (DL
BLER) share the same
measurement ID (4). When
both measurements are
performed, the UE internal
measurement (Event 6G/6F)
takes precedence.

URlEvtRttU UE Rx-Tx Time
UE Rx-Tx time difference (768..1280 [1200, [1200,
eInt.TxRxTD Difference chips
reporting threshold in chips in )chips, 800] 800]
Thres Threshold
event 6f/6g. step 1chip
59. (0, 10,

20, 40, 60,
This parameter indicates the 80, 100,
URlEvtRttU period of time during which 120, 160,
[240, [240,
eInt.TrigTim Time to Trigger the event criteria is satisfied 200, 240, ms
240] 240]
e before sending a 320, 640,
measurement report. 1280,
2560,
5000)ms
60. UUtranCellF Used UE

This parameter is the DN
DD.refUUeI Internal 0..65535,
(Distinguish Name) of N/A 0 0
ntMeasProfil Measurement step 1
UUeIntMeasProfile.
e Profile
61. UUeIntMeas
ID of UE internal Set by Set by
Profile.profil Profile Id 0..9, step 1 N/A
measurement Profile system system
eId

UE Internal indexing the configuration of
URlEvtRttU
Measurement the set of parameters of UE 0..65535, Set by Set by
eInt.ueIntM N/A
Configuration Rx-Tx time difference event step 1 system system
CfgNo
Index report for radio link timing
adjustment.

Handover Control
Recom
Name Range Value
Value

RLC mode of the UE internal
measurement report. If the
value is AM RLC, RNC can
request UE for retransmission
after receiving the error SDU 0:
label (not continuous). If the Acknowled
0: 0:
value is UM RLC, the ged Mode
URlEvtRttU Measurement Acknowl Acknowl
retransmission is not RLC
eInt.MeasR Report Transfer N/A edged edged
required. Usually, report the 1:
ptTrMod Mode Mode Mode
results of the important Unacknowl
RLC RLC
measurements in AM mode edged
and those less important in Mode RLC
UM mode (to reduce the
traffic volume of the
measurement report and
increase the system
capacity).

the results of the internal
measurement.
For the UE, L1 performs
measurement based on the
fixed measurement period
(0, 1, 2,
(Multiple points might be
URlEvtRttU 3, 4, 5, 6,
Filter measured in a measurement
eInt.FilterCo 7, 8, 9, 11, N/A 3 3
Coefficient period. L1 uses the filtering
eff 13, 15, 17,
method that is freely decided
19)
by UE to filter measurement
results). Then, L1 reports the
filtered measurement results
to L3 periodically and L3
filters the reported
measurement storage
measurement results and
storage measurement results

Handover Control
Recom
Name Range Value
Value
based on the following
method defined by the
protocol:
Fn= (1-a)*Fn-1+a*Mn,
measurement result.
Fn-1 is the old filtered
measurement result.
measurement result.
a = 1/2(k/2), where k is the
filtering factor.
NOTE: If k is set to 0, it
indicates that there is no L3
filtering.

UE internal measurement
event identity including 6A,
6B, 6F, and 6G.
6A: The UE Tx power
becomes larger than an
absolute threshold;
6B: The UE Tx power
URlEvtRttU UE Internal
becomes less than an [6a, 6b, 6f,
eInt.MeaEvtI Measurement N/A [6f, 6g] [6f, 6g]
absolute threshold; 6g]
d Event Identity
6F: The UE Rx-Tx time
difference for a RL included in
the active set becomes larger
than an absolute threshold
6G: The UE Rx-Tx time
difference for a RL included in
the active set becomes less
than an absolute threshold
66. Maximum Event

URlEvtRttU This parameter indicates the
Number of UE
eInt.MeasEv number of UE internal 1..7, step 1 N/A 2 2
Internal
tNum measurement events.
Measurement

Handover Control
Recom
Name Range Value
Value
67. When RRC connected UE

moved and the LAC/RAC
Switch for notify
URncFuncti changed, RNC should notify
UE when 0: Off
on.notifyUe UE through RRC message. N/A 0: Off 0: Off
LAC/RAC 1: On
RacChg This parameter indicates
changed
whether RNC notify UE or not
when LAC/RAC changed.
whether the soft handover
can be performed between
the macro cells with different
transport time delay of 20 ms
Whether Soft and 100 ms over Iub.
Handover Is If it is set to “Supported”, the
Supported soft handover can be
0: Not
URncFuncti between Macro performed between the macro 0: Not 1:
Supported;
on.sHOforM Cells with cells with transport time delay NA Support Support
1:
IubTimeSpt Different of 20 ms and 100ms over Iub. ed ed
Supported
Transport Time Otherwise, the soft handover
Delay Grades cannot be performed between
over Iub these macro cells.
In this version, the soft
handover is not performed for
the cells with different
transport time delay if the Iur
is involved.
whether the Intra-frequency
measurement reporting
Whether
criteria of event 1a and 1d for
Reporting
state CELL_DCH is broadcast
UExtCelInfo Information for
in SIB 11. If the threshold for 0: False
FDD.rptforD State NA 0: False 1: True
event 1a and 1d is broadcast 1: True
CHinSIB CELL_DCH is
in SIB 11, the event 1a or 1d
Broadcast in
can be reported in time
SIB
between the RRC connection
setup complete and the setup
of Intra-frequency

Handover Control
Recom
Name Range Value
Value
measurement control, thus
the service quality is
guaranteed.
70. dynamic
adjustment
dynamic adjustment switch of
URnluCfg.Ul switch of DCH
DCH service's uplink macro 0:0ff
McrWaitTim service's uplink N/A 0:off 1:on
diversity combining waiting 1:on
eSwi macro diversity
time
combining
waiting time
71. dynamic
adjustment
switch of dynamic adjustment switch of
URnluCfg.Ul
E-DCH E-DCH service's uplink macro 0:0ff
EdchMcrWa N/A 0:off 1:on
service's uplink diversity combining waiting 1:on
itTimeSwi
macro diversity time
combining
waiting time
72. The parameter relates the
static waiting time from
transmission QoS differential
of macro diversity combining
service. It is valid while
static waiting either DCH's or E-DCH's
time from uplink macro diversity
transmission combining wait time is off.
URnluCfg.Ul
QoS differential For a service over UL DCH, 0-120,step
StaticMcrW ms 20 20
of macro the parameter indicates static 1
aitTime
diversity waiting time of macro diversity
combining combining service.
service For a service over E-DCH,
both the value of the
parameter and maximum
E-DCH HARQ retransmission
number control static waiting
time of macro diversity
combining service.

Handover Control
Recom
Name Range Value
Value
73. The parameter relates the

waiting time' upper limit from
transmission QoS differential
of macro diversity combining
service. It is valid while
either DCH's or E-DCH's
maximum
uplink macro diversity
waiting time
combining wait time is
from
configured on.
URnluCfg.Ul transmission
For a service over UL DCH, 0-120,step
MaxMcrWait QoS differential ms 100 100
the parameter indicates 1
Time of macro
waiting time' upper limit of
diversity
macro diversity combining
combining
service.
service
For a service over E-DCH,
both the value of the
parameter and maximum
E-DCH HARQ retransmission
number control waiting time'
upper limit of macro diversity
combining service.
4.2 ZWF21-03-002 Intra-Frequency Hard Handover
Table 4-2 Intra-Frequency Hard Handover Parameters List
Recom
Name Range Value
Value
1. UCelInfoFD Intra-frequency This parameter indicates

0: Off
D.IntraHard Hard Handover whether an intra-frequency N/A 1: On 1: On
1: On
HoSw Switch hard handover is allowed.
2. The transport network delay OMCR:

UIubLink.Ti Transport Time
between the RNC and the 20ms, ms 20ms 20ms
meDelay Delay
related NodeB influences the 100ms,

Handover Control
Recom
Name Range Value
Value
quality of service, such as the 400ms;
downlink throughput. RNC: 0..2
This parameter indicates the
transport network delay
between the RNC and the
related NodeB.
3. The transport network delay

between the SRNC and the
related DRNS NodeB
including the external
neighboring cell influences
UExternalUt the quality of service, such as (20[0],
Transport Time
ranCellFDD. the downlink throughput. 100[1], ms 20ms 20ms
Delay
timeDelay This parameter indicates the 400[2])ms
transport network delay
between the SRNC and the
related DRNS NodeB
including the external
neighboring cell .
4. The parameter controls the

mode of intra-frequency hard
0:Timing
handover.
re-initialise
URncInfo.m Mode of 0: Timing re-initialised 0:Timing 0:Timing
d
odeOfIntraH Intra-Frequency intra-frequency hard NA re-initiali re-initiali
1:
ardHO Hard Handover handover sed sed
Timing-ma
1: Timing-maintained
intained
intra-frequency hard
handover
This feature is the supplement of soft handover. Therefore, besides the above ones,
other parameters (such as parameters relative to measurement), please refer to 4.1
ZWF21-03-001 Soft/Softer Handover.

Handover Control
4.3 ZWF21-03-003 Inter-Frequency Hard Handover
Table 4-3 Inter-Frequency Hard Handover Parameters List
Recom
Name Range Value
Value
1. 0: Turn off
This parameter indicates how Inter-freque
to perform neighbor ncy and
measurement if the Inter-RAT
both
inter-frequency and inter-RAT Handover
neighboring cells exist. 1: Only Inter
4:EUTR 4:EUTR
For inter-RAT, when GSM Frequency
AN AN
Inter neighbor cells and EUTRAN 2: Only Inter
Firstly, Firstly,
UCelInfoFD Frequency or neighbor cells are both exist, RAT
Inter-freq Inter-freq
D.IfOrRatHo Inter RAT only the measurement of the 3: Inter N/A
uency uency
Swch Handover higher priority is Frequency
system
Secondly Secondly
Switch issued. When the value is not Is Prior to
, GSM , GSM
4, the priority of GSM and Inter RAT
Finally Finally
EUTRAN is indicated by 4:EUTRAN
ChoStraMulRatHo. When the Firstly,
value is 4, EUTRAN is prior to Inter-freque
GSM by default. ncy
Secondly,
GSM Finally
interval between the events
that the RNC performs
inter-frequency measurement,
Timer for
GSM inter-RAT measurement
Shifting
and EUTRAN inter-RAT
URncFuncti Inter-frequenc
measurement.
on.T4ShifIfL y 1..20, step 1 s 5 5
When inter-frequency is prior
teGsmMea Measurement
to inter-RAT, the timer is
and Inter-RAT
initialized after the RNC
Measurement
performs inter-frequency
measurement. If the quality of
non-used frequency is poor
within the timer duration, the

Handover Control
Recom
Name Range Value
Value
RNC will perform inter-RAT
measurement.
When EUTRAN inter-RAT is
prior to inter-frequency, the
timer is initialized after the
RNC performs EUTRAN
inter-RAT measurement. If the
timer is expiry, the RNC will
perform inter-frequency
measurement.
3. AMR Inter This parameter indicates

ULogicalRn
Frequency whether an inter-frequency 0: Off
c.amrIfHoS N/A 1: On 1: On
Handover AMR handover is allowed or 1: On
w
Switch not.
4. R99 RT Inter This parameter indicates

ULogicalRn
c.r99RtIfHo N/A 1: On 1: On
Handover R99 RT handover is allowed 1: On
Sw
Switch or not.
5. R99 NRT Inter This parameter indicates

ULogicalRn
c.r99NrtIfHo N/A 1: On 1: On
Handover R99 NRT handover is allowed 1: On
Sw
Switch or not.
6. HSDPA Inter This parameter indicates

ULogicalRn
c.hsdpaIfHo N/A 1: On 1: On
Handover HSDPA handover is allowed 1: On
Sw
Switch or not.
7. HSUPA Inter This parameter indicates

ULogicalRn
c.hsupaIfHo N/A 1: On 1: On
Handover HSUPA handover is allowed 1: On
Sw
Switch or not.

whether the inter-frequency 0: Periodic
URncFuncti Inter-frequenc
handover uses the periodic Method 1: Event 1: Event
on.InterHoM y Handover N/A
method or event method. If 1: Event Method Method
th Method
this parameter is set to Method
periodic method,

Handover Control
Recom
Name Range Value
Value
inter-frequency measurement
reports are periodically
reported. If this parameter is
set to event method,
reports are reported by
triggering the event.

neighboring relationship
between a serving cell and its
GSM neighboring cell. It is
used in load balancing and
handover policies. Load 0: Neighbor
UUtranRelat balancing policies can be 1: Overlap
Share Cover 0: 0:
ion.ShareCo applied to a neighboring cell 2: Covers N/A
Indication Neighbor Neighbor
ver that has an overlap or 3:
containment relationship with Contained in
the serving cell. Handover
policies can be applied to a
neighboring cell regardless of
its relationship with the
serving cell.

threshold of the time when an
RNC resends the
MEASUREMENT CONTROL
The Time RELEASE message.
Threshold that When the RNC sends the
the RNC May MEASUREMENT CONGROL
URncFuncti
Resend the RELEASE message for a (1..255)s,
on.TResnd s 30s 30s
MEASUREM measurement ID, the time step 1s
MeaCtrlRel
ENT stamp is recorded. If the RNC
CONTROL receives the report with the
RELEASE measurement ID, it compares
the current time with the
recorded time. If the

Handover Control
Recom
Name Range Value
Value
configured, the
MEASUREMENT CONTROL
MEASUREMENT CONTROL
resent.
for the MEASUREMENT
CONTROL RELEASE
message.

scenario of the neighboring
cell.
When SIB11 is to be sent, the
cells that support "cell
0: cell
selection/reselection" are
selection/res
UE State selected from the neighboring
election only 2: cell 2: cell
Indicator Used cell list and written to SIB11;
UUtranRelat 1: handover selection selection
for UTRAN When SIB12 is to be sent, the
ion.StateMo only N/A /reselecti /reselecti
Neighboring method is the same as that for
de 2:cell on and on and
Cell SIB11;
selection/res handover handover
Configuration When the measurement
election and
control message is to be sent,
handover
the cells that support
"handover" are selected from
control message.
12. 0: Outdoor
This parameter indicates
UInterMeas Scene
Mobility typical handovers and cell 0: 0:
Profile.intial 1:
Configuration reselection scenarios. For N/A Outdoor Outdoor
HoCelSelSc High-Mobilit
Scene each scenario, the Scene Scene
ene y Outdoor
corresponding parameter can
Scene

Handover Control
Recom
Name Range Value
Value
be set to different values. 2: Indoor
Scene
3: Subway/
tunnel
Scene
13. 0: Outdoor
Scene
1:
High-Mobilit
typical handovers and cell
UUtranCellF Mobility y Outdoor 0: 0:
reselection scenarios. For
DD.HoCelS Configuration Scene N/A Outdoor Outdoor
each scenario, the
elScene Scene 2: Indoor Scene Scene
corresponding parameter can
Scene
be set to different values.
3: Subway/
tunnel
Scene

UTRAN measurement
quantity for inter-frequency
UTRAN and inter-RAT measurements.
Measurement For inter-frequency/inter-RAT
Quantity for handover,the main factor that 0: Ec/No
UUtranCellF
Inter-frequenc affects signal quality is the 1: RSCP
DD.NonIntra N/A 1: RSCP 1: RSCP
y and distance between the cell and 2: Ec/No
MeasQuan
Inter-RAT the base station, Cpich RSCP and RSCP
Measurement is adopted. But for some
s specical scenario(such as
interference is very serious),
Cpich EcNo and RSCP is
more suitable.

Service and
Bearer Type
UInterMeaS configurations based on Voice Including Including
Used for
rvSpec.srvC services and bearer types. 1: RT RAB N/A Voice Voice
Differentiating
ategory Handover-related parameter Excluding 1: RT 1: RT
Handover
configurations, for example, Voice RAB RAB
Configuration
handover triggering threshold, 2: Single Excludin Excludin

Handover Control
Recom
Name Range Value
Value
hysteresis, vary based on NRT on DL g Voice g Voice
different service DCH/UL 2: Single 2: Single
characteristics. Based on the DCH NRT on NRT on
real-time feature, channel 3: Single DL DL
types and the number of NRT RAB DCH/UL DCH/UL
RABs, services are divided on DL DCH DCH
into nine types for different HS-DSCH/U 3: Single 3: Single
parameter configurations. The L DCH NRT NRT
value 0xff corresponds to the 4: Single RAB on RAB on
periodic measurement, which NRT RAB DL DL
must be used in all services. on DL HS-DSC HS-DSC
HS-DSCH/U H/UL H/UL
L E-DCH DCH DCH
5: All 4: Single 4: Single
Multi-NRT NRT NRT
RAB on DL RAB on RAB on
DCH/UL DL DL
DCH HS-DSC HS-DSC
6: Multi-NRT H/UL H/UL
RAB, HSPA E-DCH E-DCH
is Involved 5: All 5: All
and only Multi-NR Multi-NR
DCHs are T RAB T RAB
Used in UL on DL on DL
7: Multi-NRT DCH/UL DCH/UL
RAB, HSPA DCH DCH
is Involved 6: 6:
and E-DCH Multi-NR Multi-NR
is Used in T RAB, T RAB,
UL HSPA is HSPA is
8:Multi Rab Involved Involved
Including and only and only
CS and PS DCHs DCHs
0xff: Not are Used are Used
Related to in UL in UL
Service 7: 7:
Type Multi-NR Multi-NR
T RAB, T RAB,

Handover Control
Recom
Name Range Value
Value
HSPA is HSPA is
Involved Involved
and and
E-DCH is E-DCH is
Used in Used in
UL UL
8:Multi 8:Multi
Rab Rab
Including Including
CS and CS and
PS PS
0xff: Not 0xff: Not
Related Related
to to
Service Service
Type Type

ID of the inter-frequency
Used UE measurement profile object. A
UUtranCellF Inter-frequenc profile corresponds to a set of
DD.refUinter y inter-frequency measurement N/A N/A 0 0
MeasProfile Measurement configurations. Each cell
Profile obtains the inter-frequency

Inter-frequenc
UInterMeas inter-frequency measurement
y Set by Set by
Profile.profil parameters. Each cell obtains 0~99 N/A
Measurement system system
eId the inter-frequency
Profile Identity
accordance with the profile ID.
18. Inter-frequenc This parameter indicates the

UInterEcNo
y index number of
EvMeasforU Set by Set by
Measurement inter-frequency measurement 0..65535 N/A
.InterMeasC system system
Configuration parameter configurations. It is
fgNo
Index used to index parameter

Handover Control
Recom
Name Range Value
Value
There are several sets of
measurement configurations
for the same set of
parameters based on
measurement purposes.
19. MAX_INTER_MEAS_EVENT
UInterEcNo Inter-frequenc indicates the maximum
2a, 2b, 2c, 2a,2b,2c, 2a,2b,2c,
EvMeasforU y Event number of inter-frequency N/A
2d, 2e, 2f 2d,2e,2f 2d,2e,2f
.meaEvtId Identity measurement events, and its
value is 6.

number of events required to 1..MAX_INT
Event Number be configured for an ER_MEAS_
UInterEcNo
of inter-frequency measurement EVENT
EvMeasforU
Inter-frequenc configuration number for a Where N/A 6 6
.measEvtNu
y certain purpose. This MAX_INTE
m
Measurement parameter is related to the R_MEAS_E
method of determining VENT =6.
inter-frequency handover.

filtering factor that is used by a
UE to perform L3 filtering on
results.
On the UE side, a UE
performs L1 inter-frequency (0, 1, 2, 3,
UInterEcNo
Filter measurement at a fixed 4, 5, 6, 7, 8,
EvMeasforU N/A 3 3
Coefficient measurement cycle (during 9, 11, 13,
.filterCoeff
which several points are 15, 17, 19)
measured. How L1 filters the
measurement result depends
on UEs.). After that, L1
reports the result to L3 at
certain time intervals and L3
performs filtering on the latest

Handover Control
Recom
Name Range Value
Value
measurement result and the
previous measurement result.
The filtering shall be
performed based on the
following formula specified in
3GPP TS 25.331: Fn =
(1-a)*Fn-1 +a*Mn, in which:
Fn indicates the currently
filtered measurement result;
Fn-1 indicates the previously
Mn indicates the latest
measurement result;
a = 1/2^ (k/2), in which k is the
filtering factor;
Note: If k is set to 0, no L3
filtering is performed.
From the above formula, the
filtering factor is, the greater
impact the latest
measurement result has on
the measurement result that is
finally reported to an RNC (in
the periodic report) or that is
used for determination (in the
event report).

hysteresis used to determine
whether to trigger an event.
This parameter is used as a
UInterEcNo reference to distinguish the (0,
4,4,4,4,4, 4,4,4,4,4,
EvMeasforU Hysteresis status to trigger an event from 0.5..14.5)dB dB
4 4
.hysteresis the status to end the event to step 0.5dB
avoid the transition of statuses
due to a small change. Events
are configured separately and

Handover Control
Recom
Name Range Value
Value
different values.
MAX_INTER_MEAS_EVENT
number of inter-frequency
measurement events, and its
value is 6.

time interval from the time an
event is detected to the time it
is reported. An event is
triggered and the
measurement report is
reported only when the event
occurrence is detected and
event triggering conditions
can still be met after the (0, 10, 20,
period of time indicated by 40, 60, 80,
Time to trigger. The greater 100, 120,
UInterEcNo 100,100, 100,100,
Time To the value of Time to trigger is, 160, 200,
EvMeasforU ms 100,640, 100,640,
Trigger the stricter the determination 240, 320,
.TrigTime 100,640 100,640
for event triggering will be. But 640, 1280,
this parameter should be set 2560,
based on actual needs, 5000)ms
because excessively great
value may decrease the
communication quality of
users.
value is 6.

Weight of the weight of the cell with best
UInterEcNo 0.0,0.0,0. 0.0,0.0,0.
Non-used signal in the quality evaluation (0.0..2.0),
EvMeasforU N/A 0,0.0,0.0, 0,0.0,0.0,
Frequency for of the non-used carrier step 0.1
.WNoUsed 0.0 0.0
2A/2B/2C/2E frequency (for the 2a/2b/2c/2e
events only). It is related to

Handover Control
Recom
Name Range Value
Value
and event types.
value is 6.

weight of the cell with best
signal in the quality evaluation
of the currently used carrier
Weight of the frequency (for the 2a/2b/2d/2f
UInterEcNo Currently events only). It is related to 0.0,0.0,0. 0.0,0.0,0.
(0.0..2.0),
EvMeasforU Used the measurement quantity N/A 0,0.0,0.0, 0,0.0,0.0,
step 0.1
.Wused Frequency for and event types. 0.0 0.0
2A/2B/2D/2F MAX_INTER_MEAS_EVENT
value is 6.

absolute threshold required to
be configured for the 2b/2c/2e
events (to determine the
quality of the unused carrier
CPICH
frequency). If the quality of the
RSCP:
Absolute unused carrier frequency is
(-115..-25 )d
UInterEcNo Threshold of higher than "the value of this
Bm step -24,-10,- -24,-10,-
EvMeasforU the Quality of parameter + the value of the
1dBm dB 10,-24,-1 10,-24,-1
.ThreshNoU the Non-used corresponding hysteresis/2"
CPICH 3,-24 3,-24
sedFreq Frequency for for a period of time, this carrier
Ec/No:
2B/2C/2E frequency is considered as in
(-24..0) dB
good quality and can be
step 1dB
treated as the target carrier
frequency for handover. If the
frequency is lower than "the
value of this parameter - the

Handover Control
Recom
Name Range Value
Value
value of the corresponding
hysteresis/2" for a period of
time, this carrier frequency is
considered as in poor quality.
If all the carrier frequencies in
the system are in poor quality,
inter-RAT measurement may
be triggered.
value is 6.

be configured for the 2b/2d/2f
quality of the currently used
carrier frequency). If the
carrier frequency is lower than
"the value of this parameter - CPICH
Absolute the value of the corresponding RSCP:
Threshold of hysteresis/2" for a period of (-115..-25 )d
UInterEcNo
the Quality of time, this carrier frequency is Bm step -24,-13,- -24,-13,-
EvMeasforU
the Currently considered as in poor quality, 1dBm dB 24,-13,-2 24,-13,-2
.ThreshUse
Used and inter-frequency and CPICH 4,-8 4,-8
dFreq
Frequency for inter-RAT measurements Ec/No:
2B/2D/2F should be performed. If the (-24..0) dB
quality of the currently used step 1dB
carrier frequency is higher
than "the value of this
parameter + the value of the
corresponding hysteresis/2"
for a period of time, this carrier
frequency is considered as in
good quality, and
inter-frequency and inter-RAT

Handover Control
Recom
Name Range Value
Value
measurements do not need to
be performed.
value is 6.

index number of
parameter configurations. It is
Inter-frequenc
UInterRscp used to index parameter
y
EvMeasforU configuration sets for Set by Set by
Measurement 0..65535 N/A
.InterMeasC inter-frequency measurement. system system
Configuration
fgNo There are several sets of
Index
for the same set of
parameters based on

UInterRscp Inter-frequenc ID of the event triggered by
2a, 2b, 2c, 2a,2b,2c, 2a,2b,2c,
EvMeasforU y Event inter-frequency measurement. N/A
2d, 2e, 2f 2d,2e,2f 2d,2e,2f
.meaEvtId Identity It is related to the
measurement quantity.

number of events required to 1..MAX_INT
Event Number be configured for an ER_MEAS_
UInterRscp
of inter-frequency measurement EVENT
EvMeasforU
Inter-frequenc configuration number for a Where N/A 6 6
.measEvtNu
y certain purpose. This MAX_INTE
m
Measurement parameter is related to the R_MEAS_E
31. This parameter indicates the (0, 1, 2, 3,

UInterRscp
Filter filtering factor that is used by a 4, 5, 6, 7, 8,
EvMeasforU N/A 3 3
Coefficient UE to perform L3 filtering on 9, 11, 13,
.filterCoeff
inter-frequency measurement 15, 17, 19)

Handover Control
Recom
Name Range Value
Value
results.
performs L1 inter-frequency
measurement at a fixed
measurement cycle (during
which several points are
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest

Handover Control
Recom
Name Range Value
Value
event report).

reference to distinguish the
status to trigger an event from
the status to end the event to
UInterRscp avoid the transition of statuses (0,
4,4,4,4,4, 4,4,4,4,4,
EvMeasforU Hysteresis due to a small change. Events 0.5..14.5)dB dB
4 4
.hysteresis are configured separately and step 0.5dB
different values.
value is 6.

event is detected to the time it
is reported. An event is
triggered and the
measurement report is
reported only when the event (0, 10, 20,
occurrence is detected and 40, 60, 80,
event triggeringconditions 100, 120,
UInterRscp 100,100, 100,100,
Time To can still be met after the 160, 200,
EvMeasforU ms 100,640, 100,640,
Trigger period of time indicated by 240, 320,
.TrigTime 100,640 100,640
Time to trigger. The greater 640, 1280,
the value of Time to trigger is, 2560,
the stricter the determination 5000)ms
for event triggering will be. But
this parameter should be set
based on actual needs,

Handover Control
Recom
Name Range Value
Value
users.
value is 6.

of the non-used carrier
frequency (for the 2a/2b/2c/2e
Weight of the
UInterRscp events only). It is related to 0.0,0.0,0. 0.0,0.0,0.
Non-used (0.0..2.0),
EvMeasforU the measurement quantity N/A 0,0.0,0.0, 0,0.0,0.0,
Frequency for step 0.1
.WNoUsed and event types. 0.0 0.0
2A/2B/2C/2E
value is 6.

Weight of the frequency (for the 2a/2b/2d/2f
UInterRscp Currently events only). It is related to 0.0,0.0,0. 0.0,0.0,0.
(0.0..2.0),
EvMeasforU Used the measurement quantity N/A 0,0.0,0.0, 0,0.0,0.0,
step 0.1
.Wused Frequency for and event types. 0.0 0.0
2A/2B/2D/2F MAX_INTER_MEAS_EVENT
value is 6.
36. Absolute This parameter indicates the CPICH

UInterRscp
Threshold of absolute threshold required to RSCP: -115,-90, -115,-90,
EvMeasforU
the Quality of be configured for the 2b/2c/2e (-115..-25 )d dBm -90,-115, -90,-115,
.ThreshNoU
the Non-used events (to determine the Bm step -95,-115 -95,-115
sedFreq
Frequency for quality of the unused carrier 1dBm

Handover Control
Recom
Name Range Value
Value
2B/2C/2E frequency). If the quality of the CPICH
unused carrier frequency is Ec/No:
higher than "the value of this (-24..0) dB
parameter + the value of the step 1dB
good quality and can be
treated as the target carrier
frequency for handover. If the
frequency is lower than "the
value of this parameter - the
value of the corresponding
considered as in poor quality.
If all the carrier frequencies in
the system are in poor quality,
inter-RAT measurement may
be triggered.
value is 6.

CPICH
be configured for the 2b/2d/2f
Absolute RSCP:
Threshold of (-115..-25 )d
UInterRscp quality of the currently used
the Quality of Bm step -115,-95, -115,-95,
EvMeasforU carrier frequency). If the
the Currently 1dBm dBm -115,-95, -115,-95,
.ThreshUse quality of the currently used
Used CPICH -115,-80 -115,-80
dFreq carrier frequency is lower than
Frequency for Ec/No:
"the value of this parameter -
2B/2D/2F (-24..0) dB
the value of the corresponding
step 1dB

Handover Control
Recom
Name Range Value
Value
considered as in poor quality,
and inter-frequency and
inter-RAT measurements
should be performed. If the
good quality, and
inter-frequency and inter-RAT
measurements do not need to
be performed.
value is 6.

index number of
Inter-frequenc
UInterEcNo used to index parameter
y
PrdMeas.Int configuration sets for Set by Set by
Measurement 0..65535 N/A
erMeasCfgN inter-frequency measurement. system system
Configuration
o There are several sets of
Index
for the same set of
parameters based on

filtering factor that is used by a (0, 1, 2, 3,
UInterEcNo
Filter UE to perform L3 filtering on 4, 5, 6, 7, 8,
PrdMeas.filt N/A 3 3
Coefficient inter-frequency measurement 9, 11, 13,
erCoeff
results. 15, 17, 19)

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
event report).
40. UInterEcNo Amount of This parameter indicates the 1, 2, 4, 8, N/A Infinity Infinity

Handover Control
Recom
Name Range Value
Value
PrdMeas.Pr Reporting in number of times that periodic 16, 32, 64,
dRptAmount Period Report reports are reported. A UE Infinity
Criteria uses the parameter Amount of
reporting to determine
whether measurement reports
are also needed. If the UE
detects that the number of
times of event reporting
exceeds the value of the
parameter, it stops reporting
measurement reports.
41. (250, 500,

1000, 2000,
time interval at which a UE 6000, 8000,
Reporting
UInterEcNo reports periodic reports. For 12000,
Interval in
PrdMeas.Pr periodic reports, the UE 16000, ms 1000 1000
Period Report
dRptInterval periodically reports 20000,
Criteria
measurement results based 24000,
on this parameter. 28000,
32000,
64000)ms
42. Inter-frequenc This parameter indicates the

UInterRscp
y ID of the event triggered by
PrdMeas.Int Set by Set by
Measurement inter-frequency measurement. 0..65535 N/A
erMeasCfgN system system
Configuration It is related to the
o
Index measurement quantity.

filtering factor that is used by a
UE to perform L3 filtering on
inter-frequency measurement (0, 1, 2, 3,
UInterRscp
Filter results. 4, 5, 6, 7, 8,
PrdMeas.filt N/A 3 3
Coefficient On the UE UE 9, 11, 13,
side, a
erCoeff
performs L1 inter-frequency 15, 17, 19)

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
event report).

Amount of
UInterRscp number of times that periodic 1, 2, 4, 8,
Reporting in
PrdMeas.Pr reports are reported. A UE 16, 32, 64, N/A Infinity Infinity
Period Report
dRptAmount uses the parameter Amount of Infinity
Criteria
reporting to determine

Handover Control
Recom
Name Range Value
Value
whether measurement reports
are also needed. If the UE
45. (250, 500,

1000, 2000,
time interval at which a UE 6000, 8000,
UInterRscp Reporting
reports periodic reports. For 12000,
PrdMeass.P Interval in
periodic reports, the UE 16000, ms 500 500
rdRptInterva Period Report
periodically reports 20000,
l Criteria
measurement results based 24000,
on this parameter. 28000,
32000,
64000)ms

inter-frequency handover
policy.
In most scenarios, this
parameter is set to 2A Event
Trigger, and precise
0: Algorithm
inter-frequency handovers
Deciding
can be ensured as long as the
1: 2A Event
UUtranCellF Inter-frequenc target cell is better than the 1: 2A 1: 2A
Trigger
DD.InterHoT y Handover serving cell. In some N/A Event Event
2: 2B Event
actic Tactic scenarios where handover Trigger Trigger
Trigger
quality needs to be better
3: 2C Event
controlled, this parameter is
Trigger
set to Algorithm Deciding or
2B Event Trigger. In some
scenarios where it is required
to hand over to the target cell
as soon as possible, this
parameter is set to 2C Event

Handover Control
Recom
Name Range Value
Value
Trigger.
47. This parameter indicates that

this timer is enabled upon an
URncInfo.H Inter-frequenc intra-frequency handover
oToInterPen y Handover failure. The RNC does not (0..65535)s, s 20s 20s
Timer Penalty Timer handle intra-frequency step 1s
measurement reports until the
timer expires.

neighboring relationship
between a serving cell and its
GSM neighboring cell. It is
used in load balancing and
handover policies. Load 0: Neighbor
UGsmRelati balancing policies can be 1: Overlap
Share Cover 0: 0:
on.GsmShar applied to an neighboring cell 2: Covers N/A
Indication Neighbor Neighbor
eCover that has an overlap or 3:
containment relationship with Contained in
the serving cell. Handover
policies can be applied to an
neighboring cell regardless
of its relationship with the
serving cell.

whether RNC judge the
Switch of minimu quality threshold of
Judging Targt target cells in inter-frequency
UCelInfoFD Cell's handover. If the switch is On,
0: Off
D.InterHoMi Minimum when the signal quality of N/A 0: Off 0: Off
1: On
nThrdSw Quality in target cells' quality is lower
Inter-frequenc than InterHoEcNoThrd or
y Handover InterHoRscpThrd, RNC will
not perform the inter
frequency handover.
50. URncFuncti Cpich Ec/No This parameter indicates the

(-24..0)dB,
on.InterHoE Minimum Cpich EcNo minimum dB -13dB -13dB
step 1dB
cNoThrd Threshold for threshold for inter frequency

Handover Control
Recom
Name Range Value
Value
Inter-Frequen handover. If reported Cpich
cy Handover EcNo is less than
InterHoEcNoThrd or Cpich
RSCP is less than
InterHoRscpThrd, inter
frequency handover will not
be triggered.

minimum Cpich EcNo
threshold for intra-frequency
Cpich Rscp
handovers. If the reported
URncFuncti Minimum
Cpich EcNo is lower than (-120..-25)d
on.InterHoR Threshold for dBm -108dBm -108dBm
InterHoEcNoThrd or Cpich Bm, step
scpThrd Inter-Frequen
RSCP is lower than 1dBm
cy Handover
InterHoRscpThrd, no
intra-frequency handover is
triggered.

interval between reception of
periodic reports and triggering
of the inter-frequency or
inter-RAT handover. Only the
neighboring cell in which the
Time To signal quality is above a
Trigger for certain threshold in all periodic
UCelInfoFD Inter-frequenc reports during a time equal to
(0..255)s,
D.PeriodTrig y and this parameter can be s 0s 0s
step 1s
gerTime Inter-Rat selected as the target cell for
Period the inter-frequency or inter-rat
Measurement handover. If this parameter is
set to a large value, the
probability of incorrect
decision is low. However, the
handover algorithm becomes
slow in responding to signal
change.
53. UUtranRelat Cell Individual Cell individual offset. An offset (-50..50) dB dB 0dB 0dB

Handover Control
Recom
Name Range Value
Value
ion.CellIndiv Offset is allocated to each cell that is step 1 Db
Offset monitored. The offset can be
the UE determines whether an
event occurs, the offset
PCPICH uses a positive

whether the second attempt is
allowed to trigger a blind
handover. If this switch is
enabled, the UE is allowed to
attempt to access another
Switch of candidate cell through a blind
UCelInfoFD Blind handover in case of admission
0: Off
D.SecTryBli Handover failure. If this switch is N/A 1: On 1: On
1: On
dHoSw triggered by disabled, the blind handover is
Second-Try not allowed. This parameter is
effective only when the load
balancing feature is disabled.
If the load balancing feature is
enabled, the second attempt
to trigger a blind handover is
allowed by default.

Handover Control
4.4 ZWF21-03-004 Inter-RAT Mobility
Table 4-4 Inter-RAT Mobility Parameters List
Recom
Name Range Value
Value
1. ULogicalRn AMR Inter Rat This parameter indicates

0: Off
c.amrRatHo Handover whether an inter-RAT AMR N/A 1: On 1: On
1: On
Sw Switch handover is allowed or not.
2. ULogicalRn R99 RT Inter This parameter indicates

0: Off
c.r99RtRatH Rat Handover whether an inter-RAT R99 RT N/A 1: On 1: On
1: On
oSw Switch handover is allowed or not.

ULogicalRn R99 NRT Inter
whether an inter-RAT R99 0: Off
c.r99NrtRat Rat Handover N/A 1: On 1: On
NRT handover is allowed or 1: On
HoSw Switch
not.
4. ULogicalRn HSDPA Inter This parameter indicates

0: Off
c.hsdpaRat Rat Handover whether an inter-RAT HSDPA N/A 1: On 1: On
1: On
HoSw Switch handover is allowed or not.
5. ULogicalRn HSUPA Inter This parameter indicates

0: Off
c.hsupaRat Rat Handover whether an inter-RAT HSUPA N/A 1: On 1: On
1: On
HoSw Switch handover is allowed or not.

whether the inter-RAT
handover uses the periodic
method or event method. If
this parameter is set to
0: Periodic
URncFuncti Inter-RAT periodic method, inter-RAT
Method 1: Event 1: Event
on.IntRatHo Handover measurement reports are N/A
1: Event Method Method
Mth Method periodically reported. If this
Method
parameter is set to event
method, inter-RAT
measurement reports are
reported by triggering the
event.
7. URncFuncti The Time This parameter indicates the (1..255)s,

s 30s 30s
on.TResnd Threshold that threshold of the time when an step 1s

Handover Control
Recom
Name Range Value
Value
MeaCtrlRel the RNC May RNC resends the
Resend the MEASUREMENT CONTROL
MEASUREME RELEASE message.
NT CONTROL When the RNC sends the
RELEASE MEASUREMENT CONGROL
RELEASE message for a
measurement ID, the time
stamp is recorded. If the RNC
receives the report with the
measurement ID, it compares
the current time with the
recorded time. If the
configured, the
MEASUREMENT CONTROL
MEASUREMENT CONTROL
resent.
for the MEASUREMENT
CONTROL RELEASE
message.
8. This parameter indicates UE 0: cell

status for GSM neighboring selection/r
2:cell 2:cell
UE State cell configuration. eselection
selectio selectio
Indicator Used When SIB11 is to be sent, the only
UGsmRelati n/resele n/resele
for GSM cells that support "cell 1:
on.GsmStat N/A ction ction
Neighboring selection/reselection" are handover
eMode and and
Cell selected from the neighboring only
handove handove
Configuration cell list and written to SIB11; 2:cell
r r
When SIB12 is to be sent, the selection/r
method is the same as that for eselection

Handover Control
Recom
Name Range Value
Value
SIB11; and
When the measurement handover
control message is to be sent,
the cells that support
"handover" are selected from
control message.
9. 0: Outdoor
Scene
1:
URatMeasP typical handovers and cell ity Outdoor
Mobility 0: 0:
rofile.intialH reselection scenarios. For Scene
Configuration N/A Outdoor Outdoor
oCelSelSce each scenario, the 2: Indoor
Scene Scene Scene
ne corresponding parameter can Scene
Subway/
tunnel
Scene
10. 0: Outdoor
Scene
1:
typical handovers and cell ity Outdoor
UUtranCellF Mobility 0: 0:
reselection scenarios. For Scene
DD.HoCelS Configuration N/A Outdoor Outdoor
each scenario, the 2: Indoor
elScene Scene Scene Scene
corresponding parameter can Scene
Subway/
tunnel
Scene
11. UTRAN This parameter indicates

0: Ec/No
UUtranCellF Measurement UTRAN measurement
1: RSCP
DD.NonIntra Quantity for quantity for inter-frequency N/A 1:RSCP 1:RSCP
2: Ec/No
MeasQuan Inter-frequency and inter-RAT
and RSCP
and Inter-RAT measurements. For

Handover Control
Recom
Name Range Value
Value
Measurements inter-frequency/inter-RAT
handover,the main factor that
affects signal quality is the
distance between the cell and
the base station, Cpich RSCP
is adopted. But for some
specical scenario(such as
interference is very serious),
Cpich EcNo and RSCP is
more suitable.
12. 0: RT RAB 0: RT 0: RT
Including RAB RAB
Voice Includin Includin
1: RT RAB g Voice g Voice
Excluding 1: RT 1: RT
This parameter distinguishes Voice RAB RAB
handover parameter 2: Single Excludin Excludin
configurations based on NRT on g Voice g Voice
services and bearer types. DL 2: Single 2: Single
Handover-related parameter DCH/UL NRT on NRT on
configurations, for example, DCH DL DL
Service and handover triggering threshold, 3: Single DCH/UL DCH/UL
Bearer Type hysteresis, vary based on NRT RAB DCH DCH
UInterMeaS
Used for different service on
DL 3: Single 3: Single
rvSpec.srvC N/A
Differentiating characteristics. Based on the HS-DSCH/ NRT NRT
ategory
Handover real-time feature, channel UL DCH RAB on RAB on
Configuration types and the number of 4: Single DL DL
RABs, services are divided NRT RAB HS-DSC HS-DSC
into nine types for different on DL H/UL H/UL
parameter configurations. The HS-DSCH/ DCH DCH
value 0xff corresponds to the UL E-DCH 4: Single 4: Single
periodic measurement, which 5: All NRT NRT
must be used in all services. Multi-NRT RAB on RAB on
RAB on DL DL
DL HS-DSC HS-DSC
DCH/UL H/UL H/UL
DCH E-DCH E-DCH
6: 5: All 5: All

Handover Control
Recom
Name Range Value
Value
RAB, T RAB T RAB
HSPA is on DL on DL
and only DCH DCH
DCHs are 6: 6:
7: T RAB, T RAB,
Involved DCHs DCHs
and are are
Used in UL UL UL
8:Multi 7: 7:
Related to and and
Service E-DCH E-DCH
in UL in UL
8: Multi 8: Multi
Rab Rab
Includin Includin
g CS g CS
and PS and PS
0xff: Not 0xff: Not
Related Related
to to
Service Service
Type Type
13. Used UE This parameter indicates the

UUtranCellF
Inter-frequency ID of the inter-frequency
DD.refUinter N/A N/A 0 0
Measurement measurement profile object. A
MeasProfile
Profile profile corresponds to a set of

Handover Control
Recom
Name Range Value
Value
configurations. Each cell
obtains the inter-frequency

UInterMeas Inter-frequency
parameters. Each cell obtains Set by Set by
Profile.profil Measurement 0~99 N/A
the inter-frequency system system
eId Profile Identity
accordance with the profile
ID.

index number of
UInterEcNo Inter-frequency used to index parameter
EvMeasforG Measurement configuration sets for Set by Set by
0..65535 N/A
.InterMeasC Configuration inter-frequency system system
fgNo Index measurement. There are
several sets of measurement
configurations for the same
set of parameters based on
16. MAX_INTER_MEAS_EVENT
UInterEcNo indicates the maximum
Inter-frequency 2a, 2b, 2c,
EvMeasforG number of inter-frequency N/A 2d,2f 2d,2f
Event Identity 2d, 2e, 2f
.meaEvtId measurement events, and its
value is 6.
17. This parameter indicates the 1..MAX_IN

number of events required to TER_MEA
UInterEcNo Event Number
be configured for an S_EVENT
EvMeasforG of
inter-frequency measurement Where N/A 2 2
.measEvtNu Inter-frequency
configuration number for a MAX_INT
m Measurement
certain purpose. This ER_MEAS
parameter is related to the _EVENT

Handover Control
Recom
Name Range Value
Value
method of determining =6.

filtering factor that is used by
a UE to perform L3 filtering on
results.
(0, 1, 2,
UInterEcNo 3, 4, 5, 6,
Filter previous measurement result.
EvMeasforG 7, 8, 9, 11, N/A 3 3
Coefficient The filtering shall be
.filterCoeff 13, 15, 17,
19)
3GPP TS 25.331: Fn =
measurement result;
filtering factor;

Handover Control
Recom
Name Range Value
Value
impact the latest
the measurement result that
is finally reported to an RNC
(in the periodic report) or that
is used for determination (in
the event report).

avoid the transition of (0,
UInterEcNo
statuses due to a small 0.5..14.5)d
EvMeasforG Hysteresis dB 4,4 4,4
change. Events are B step
.hysteresis
configured separately and 0.5dB
different values.
value is 6.

event is detected to the time it (0, 10,
is reported. An event is 20, 40, 60,
triggered and the 80, 100,
UInterEcNo measurement report is 120, 160,
EvMeasforG Time To Trigger reported only when the event 200, 240, ms 640,640 640,640
.TrigTime occurrence is detected and 320, 640,
event conditions 1280,
triggering
can still be met after the 2560,
period of time indicated by 5000)ms
Time to trigger. The greater
the value of Time to trigger is,

Handover Control
Recom
Name Range Value
Value
the stricter the determination
for event triggering will be.
But this parameter should be
set based on actual needs,
users.
value is 6.

frequency (for the 2d/2f
Weight of the
UInterEcNo events only). It is related to
Currently Used (0.0..2.0),
EvMeasforG the measurement quantity N/A 0.0,0.0 0.0,0.0
.Wused and event types.
2D/2F
value is 6.

CPICH
be configured for the 2d/2f
Absolute RSCP:
Threshold of (-115..-25
UInterEcNo quality of the currently used
the Quality of )dBm step
EvMeasforG carrier frequency). If the
the Currently 1dBm dB -13,-8 -13,-8
.ThreshUse quality of the currently used
Used CPICH
dFreq carrier frequency is lower than
Frequency for Ec/No:
"the value of this parameter -
2D/2F (-24..0) dB
the value of the
step 1dB
for a period of time, this

Handover Control
Recom
Name Range Value
Value
carrier frequency is
considered as in good quality,
inter-RAT measurements do
not need to be performed.
value is 6.

index number of
UInterRscp Inter-frequency used to index parameter
EvMeasforG Measurement configuration sets for Set by Set by
0..65535 N/A
.InterMeasC Configuration inter-frequency system system
fgNo Index measurement. There are

UInterRscp
Inter-frequency ID of the event triggered by 2a, 2b, 2c,
EvMeasforG N/A 2d,2f 2d,2f
Event Identity inter-frequency 2d, 2e, 2f
.meaEvtId
measurement. It is related to

Handover Control
Recom
Name Range Value
Value
the measurement quantity.

1..MAX_IN
number of events required to
TER_MEA
be configured for an
UInterRscp Event Number S_EVENT
EvMeasforG of Where
configuration number for a N/A 2 2
.measEvtNu Inter-frequency MAX_INT
certain purpose. This
m Measurement ER_MEAS
parameter is related to the
_EVENT
method of determining
=6.

results.
(0, 1, 2,
UInterRscp 3, 4, 5, 6,
Filter reports the result to L3 at
EvMeasforG 7, 8, 9, 11, N/A 3 3
Coefficient certain time intervals and L3
.filterCoeff 13, 15, 17,
19)
3GPP TS 25.331: Fn =

Handover Control
Recom
Name Range Value
Value
measurement result;
filtering factor;
impact the latest
the event report).

avoid the transition of (0,
UInterRscp
statuses due to a small 0.5..14.5)d
EvMeasforG Hysteresis dB 4,4 4,4
change. Events are B step
.hysteresis
configured separately and 0.5dB
different values.
value is 6.
28. This parameter indicates the (0, 10,

UInterRscp time interval from the time an 20, 40, 60,
EvMeasforG Time To Trigger event is detected to the time it 80, 100, ms 640,640 640,640
.TrigTime is reported. An event is 120, 160,
triggered and the 200, 240,

Handover Control
Recom
Name Range Value
Value
measurement report is 320, 640,
reported only when the event 1280,
occurrence is detected and 2560,
event triggering conditions 5000)ms
can still be met after the
period of time indicated by
Time to trigger. The greater
the value of Time to trigger is,
the stricter the determination
for event triggering will be.
But this parameter should be
set based on actual needs,
users.
value is 6.

frequency (for the 2d/2f
Weight of the
UInterRscp events only). It is related to
Currently Used (0.0..2.0),
EvMeasforG the measurement quantity N/A 0.0,0.0 0.0,0.0
.Wused and event types.
2D/2F
value is 6.
30. Absolute This parameter indicates the CPICH

UInterRscp
Threshold of absolute threshold required to RSCP:
EvMeasforG dBm -95,-80 -95,-80
the Quality of be configured for the 2d/2f (-115..-25
.ThreshUse
the Currently events (to determine the )dBm step

Handover Control
Recom
Name Range Value
Value
dFreq Used quality of the currently used 1dBm
Frequency for carrier frequency). If the CPICH
2D/2F quality of the currently used Ec/No:
carrier frequency is lower than (-24..0) dB
"the value of this parameter - step 1dB
the value of the
considered as in good quality,
inter-RAT measurements do
not need to be performed.
value is 6.

Service and
configurations based on Voice Includin Includin
Bearer Type
URatMeasS services and bearer types. 1: RT RAB g Voice g Voice
Used for
rvSpec.srvC Handover-related parameter Excluding N/A 1: RT 1: RT
Differentiating
ategory configurations, for example, Voice RAB RAB
Handover
handover triggering threshold, 2: Single Excludin Excludin
Configuration
hysteresis, vary based on NRT on g Voice g Voice
different service DL 2: Single 2: Single

Handover Control
Recom
Name Range Value
Value
characteristics. Based on the DCH/UL NRT on NRT on
real-time feature, channel DCH DL DL
types and the number of 3: Single DCH/UL DCH/UL
RABs, services are divided NRT RAB DCH DCH
into nine types for different on DL 3: Single 3: Single
parameter configurations. The HS-DSCH/ NRT NRT
value 0xff corresponds to the UL DCH RAB on RAB on
periodic measurement, which 4: Single DL DL
must be used in all services. NRT RAB HS-DSC HS-DSC
on DL H/UL H/UL
HS-DSCH/ DCH DCH
UL E-DCH 4: Single 4: Single
5: All NRT NRT
Multi-NRT RAB on RAB on
RAB on DL DL
DL HS-DSC HS-DSC
DCH/UL H/UL H/UL
DCH E-DCH E-DCH
6: 5: All 5: All
RAB, T RAB T RAB
HSPA is on DL on DL
and only DCH DCH
DCHs are 6: 6:
7: T RAB, T RAB,
Involved DCHs DCHs
and are are
Used in UL UL UL
8:Multi 7: 7:

Handover Control
Recom
Name Range Value
Value
Related to and and
Service E-DCH E-DCH
in UL in UL
8: Multi 8: Multi
Rab Rab
Includin Includin
g CS g CS
and PS and PS
0xff: Not 0xff: Not
Related Related
to to
Service Service
Type Type

ID of the inter-RAT
measurement profile object. A
UUtranCellF Used Inter-RAT profile corresponds to a set of
DD.refURat Measurement intra-RAT measurement N/A N/A 0 0
MeasProfile Profile configurations. Each cell
obtains the intra-RAT

profile ID of a set of inter-RAT
URatMeasP Inter-Rat measurement parameters.
Set by Set by
rofile.profileI Measurement Each cell obtains the 0~99 N/A
system system
d Profile Identity inter-RAT measurement
parameters in accordance
with the profile ID.

URatEcNoE Inter-RAT index number of inter-RAT
vMeasforG.I Measurement measurement parameter Set by Set by
0..65535 N/A
nterRatCfgN Configuration configurations. It is used to system system
o Index index parameter configuration
sets for inter-RAT

Handover Control
Recom
Name Range Value
Value

ID of the event triggered by
inter-RAT measurement. It is
related to the measurement
URatEcNoE
Inter-RAT Event quantity. 3a, 3b, 3c, 3a,3b,3c 3a,3b,3c
vMeasforG. N/A
Identity MAX_RAT_MEAS_EVENT 3d ,3d ,3d
EventId
number of inter-RAT
value is 4.

number of events required to 1..MAX_R
be configured for an AT_MEAS
URatEcNoE Inter-RAT inter-RAT measurement _EVENT T
vMeasforG. Measurement configuration number for a Where N/A 4 4
EventNum Event Number certain purpose.This MAX_RAT
parameter is related to the _MEAS_E
inter-RAT handover.

results. 0, 1, 2, 3,
URatEcNoE On the UE UE 4, 5, 6, 7,
side, a
UTRAN Filter
vMeasforG. performs L1 intra-frequency 8, 9, 11, N/A 3 3
Coefficient
FilterCoeff measurement at a fixed 13, 15, 17,
measurement cycle (during 19

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
the event report).

0, 1, 2, 3,
URatEcNoE a UE to perform L3 filtering on
4, 5, 6, 7,
vMeasforG. GSM Filter GSMRNC measurement
8, 9, 11, N/A 3 3
GsmFilterCo Coefficient results in inter-RAT
13, 15, 17,
eff measurement.
19
performs L1 inter-RAT

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
the event report).
39. URatEcNoE This parameter indicates the (0,

Hysteresis dB 4,4,2,4 4,4,2,4
vMeasforG. hysteresis used to determine 0.5..7.5)dB

Handover Control
Recom
Name Range Value
Value
Hysteresis whether to trigger an event. step 0.5dB
avoid the transition of
statuses due to a small
change.
The greater the value of
Hysteresis is, the greater the
threshold to trigger an event
and the threshold to end the
event is.
It is related to the
measurement quantity and
event types.
MAX_RAT_MEAS_EVENT is
the maximum number of
inter-RAT measurement
events, and its value is 4.

difference in time when an
event is detected and when it
(0, 10,
is reported. The event will be
20, 40, 60,
triggered and reported only
80, 100,
when it meets all the
URatEcNoE 120, 160,
triggering conditions within 100,100, 100,100,
vMeasforG. Time To Trigger 200, 240, ms
the triggering duration 100,100 100,100
TrigTime 320, 640,
indicated by this parameter
1280,
after being detected.
2560,
5000)ms

URatEcNoE Weight of the (0.0..2.0),
weight of the cell with the best N/A 0,0,0,0 0,0,0,0
vMeasforG. UTRAN System step 0.1
quality in the calculation of the

Handover Control
Recom
Name Range Value
Value
W for 3A UTRAN system quality (for
the 3a event only). It is used
to determine the quality of the
UTRAN system in inter-RAT
measurement.

absolute threshold of the
UTRAN cell quality that the
UE uses for determination of
event 3a. If the quality of the
current system is lower than
this threshold minus
hysteresis/2 for a period of
time, then the system is
considered to be of poor
quality, and it is necessary to CPICH
perform an inter-RAT RSCP:
Absolute handover quickly. If the (-115..-25
URatEcNoE Threshold of quality of the current system )dBm step
-9,-24,-2 -9,-24,-2
vMeasforG. the Quality of is higher than this threshold 1dB dB
4,-24 4,-24
Thresh UTRAN Cell for plus hysteresis/2 for a period CPICH
3A of time, then the system is Ec/No:
considered to be of good (-24..0) dB
quality, and there is no need step 1dB
to perform an inter-RAT
handover.
The range and unit of this
measurement quantity of the
UTRAN cell.

Handover Control
Recom
Name Range Value
Value

absolute threshold configured
for event 3a/3b/3c, used for
determining the quality of
other RATs. If the quality of a
system plus the cell individual
offset is higher than this
threshold plus hysteresis/2 for
a period of time, then the
system is considered to be of
good quality, and can serve
as a target system for (-140..0)
handovers. If the quality of a CPICH
system plus the cell individual RSCP:
offset is lower than this (-115..-25
threshold minus hysteresis/2 )dBm step
Absolute
for a period of time, then the 1dB
URatEcNoE Threshold of
system is considered to be of CPICH -90,-95,- -90,-95,-
vMeasforG. the Quality of dBm
poor quality, and cannot serve Ec/No: 95,-115 95,-115
ThreshSys Other RAT for
as a target system for (-24..0) dB
3A/3B/3C
handovers. step 1dB
The range and unit of this RSRP:
parameter is related to the (-140..-44)
measurement quantity of dBm step
other RATs. The 1dB
measurement quantity GSM
Carrier RSSI of the GSM
system corresponds to
CPICH RSCP of the UTRAN
system, so the value range
and unit of this parameter
corresponds to CPICH RSCP.
44. URatRscpE Inter-RAT This parameter indicates the Set by Set by

0..65535 N/A
vMeasforG.I Measurement index number of inter-RAT system system

Handover Control
Recom
Name Range Value
Value
nterRatCfgN Configuration measurement parameter
o Index configurations. It is used to
index parameter configuration
sets for inter-RAT

ID of the event triggered by
inter-RAT measurement. It is
related to the measurement
URatRscpE
Inter-RAT Event quantity. 3a, 3b, 3c, 3a,3b,3c 3a,3b,3c
vMeasforG. N/A
Identity MAX_RAT_MEAS_EVENT 3d ,3d ,3d
EventId
number of inter-RAT
value is 4.

number of events required to 1..MAX_R
be configured for an AT_MEAS
URatRscpE Inter-RAT inter-RAT measurement _EVENT T
vMeasforG. Measurement configuration number for a Where N/A 4 4
EventNum Event Number certain purpose.This MAX_RAT
parameter is related to the _MEAS_E
inter-RAT handover.

a UE to perform L3 filtering on 0, 1, 2, 3,
URatRscpE intra-frequency measurement 4, 5, 6, 7,
UTRAN Filter
vMeasforG. results. 8, 9, 11, N/A 3 3
Coefficient
FilterCoeff On the UE side, a UE 13, 15, 17,
performs L1 intra-frequency 19

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
the event report).
48. URatRscpE This parameter indicates the 0, 1, 2, 3,

vMeasforG. GSM Filter filtering factor that is used by 4, 5, 6, 7,
N/A 3 3
GsmFilterCo Coefficient a UE to perform L3 filtering on 8, 9, 11,
eff GSMRNC measurement 13, 15, 17,

Handover Control
Recom
Name Range Value
Value
results in inter-RAT 19
measurement.
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest

Handover Control
Recom
Name Range Value
Value
the event report).

avoid the transition of
statuses due to a small
change.
URatRscpE The greater the value of (0,
vMeasforG. Hysteresis Hysteresis is, the greater the 0.5..7.5)dB dB 4,4,4,4 4,4,4,4
Hysteresis difference between the step 0.5dB
threshold to trigger an event
and the threshold to end the
event is.
It is related to the
measurement quantity and
event types.

difference in time when an
event is detected and when it (0, 10,
is reported. The event will be 20, 40, 60,
triggered and reported only 80, 100,
URatRscpE when it meets all the 120, 160,
100,100, 100,100,
vMeasforG. Time To Trigger triggering conditions within 200, 240, ms
100,100 100,100
TrigTime the triggering duration 320, 640,
indicated by this parameter 1280,
after being detected. 2560,
MAX_RAT_MEAS_EVENT is 5000)ms

Handover Control
Recom
Name Range Value
Value

weight of the cell with the best
quality in the calculation of the
UTRAN system quality (for
the 3a event only). It is used
URatRscpE Weight of the
to determine the quality of the (0.0..2.0),
vMeasforG. UTRAN System N/A 0,0,0,0 0,0,0,0
UTRAN system in inter-RAT step 0.1
W for 3A
measurement.

absolute threshold of the
UTRAN cell quality that the
UE uses for determination of
event 3a. If the quality of the
current system is lower than
this threshold minus
hysteresis/2 for a period of
time, then the system is CPICH
considered to be of poor RSCP:
Absolute quality, and it is necessary to (-115..-25
URatRscpE Threshold of perform an inter-RAT )dBm step -95,-115 -95,-115
vMeasforG. the Quality of handover quickly. the 1dB
If dBm ,-115,-1 ,-115,-1
Thresh UTRAN Cell for quality of the current system CPICH 15 15
3A is higher than this threshold Ec/No:
plus hysteresis/2 for a period (-24..0) dB
of time, then the system is step 1dB
considered to be of good
quality, and there is no need
to perform an inter-RAT
handover.
The range and unit of this
measurement quantity of the
UTRAN cell.

Handover Control
Recom
Name Range Value
Value

absolute threshold configured
for event 3a/3b/3c, used for
determining the quality of
other RATs. If the quality of a
system plus the cell individual
offset is higher than this
threshold plus hysteresis/2 for
a period of time, then the
system is considered to be of
good quality, and can serve (-140..0)
as a target system for CPICH
handovers. If the quality of a RSCP:
system plus the cell individual (-115..-25
offset is lower this )dBm step
than
Absolute
threshold minus hysteresis/2 1dB
URatRscpE Threshold of
for a period of time, then the CPICH -90,-95,- -90,-95,-
vMeasforG. the Quality of dBm
system is considered to be of Ec/No: 95,-115 95,-115
ThreshSys Other RAT for
poor quality, and cannot serve (-24..0) dB
3A/3B/3C
as a target system for step 1dB
handovers. RSRP:
The range and unit of this (-140..-44)
parameter is related to the dBm step
measurement quantity of 1dB
other RATs. The
measurement quantity GSM
Carrier RSSI of the GSM
system corresponds to
CPICH RSCP of the UTRAN
system, so the value range
and unit of this parameter
corresponds to CPICH RSCP.

Handover Control
Recom
Name Range Value
Value

index number of inter-RAT
measurement parameter
configurations. It is used to
Inter-RAT
URatEcNoP index parameter configuration
Measurement Set by Set by
rdMeas.Inter sets for inter-RAT 0..65535 N/A
Configuration system system
RatCfgNo measurement. There are
Index

results.
performs L1 intra-frequency
measured. How L1 filters the 0, 1, 2, 3,
URatEcNoP measurement result depends 4, 5, 6, 7,
UTRAN Filter
rdMeas.Filte on UEs.). After L1 8, 9, 11, N/A
that, 3 3
Coefficient
rCoeff reports the result to L3 at 13, 15, 17,
certain time intervals and L3 19
3GPP TS 25.331: Fn =

Handover Control
Recom
Name Range Value
Value
measurement result;
filtering factor;
impact the latest
the event report).

GSMRNC measurement
results in inter-RAT
measurement.
0, 1, 2, 3,
URatEcNoP 4, 5, 6, 7,
GSM Filter measurement cycle (during
rdMeas.Gs 8, 9, 11, N/A 3 3
Coefficient which several points are
mFilterCoeff 13, 15, 17,
19

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
the event report).

number of times that periodic
reports are reported. A UE
uses the parameter Amount
Amount of of reporting to determine
URatEcNoP 1, 2, 4, 8,
Reporting in whether measurement reports
rdMeas.Prd 16, 32, 64, N/A Infinity Infinity
Period Report are also needed. If the UE
RptAmount Infinity
Criteria detects that the number of
58. URatEcNoP Reporting This parameter indicates the (250,

ms 1000 1000
rdMeas.Prd Interval in interval at which periodic 500, 1000,

Handover Control
Recom
Name Range Value
Value
RptInterval Period Report reports are reported. 2000,
Criteria 3000,
4000,
6000,
8000,
12000,
16000,
20000,
24000,
28000,
32000,
64000)ms

index number of inter-RAT
measurement parameter
configurations. It is used to
Inter-RAT
URatRscpPr index parameter configuration
Measurement Set by Set by
dMeas.Inter sets for inter-RAT 0..65535 N/A
Configuration system system
RatCfgNo measurement. There are
Index

results.
On the UE side, UE 0, 1, 2, 3,
a
URatRscpPr performs L1 intra-frequency 4, 5, 6, 7,
UTRAN Filter
dMeas.Filter measurement at a fixed 8, 9, 11, N/A 3 3
Coefficient
Coeff measurement cycle (during 13, 15, 17,
which several points are 19

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
the event report).

0, 1, 2, 3,
GSMRNC measurement
URatRscpPr 4, 5, 6, 7,
GSM Filter results in inter-RAT
dMeas.Gsm 8, 9, 11, N/A 3 3
Coefficient measurement.
FilterCoeff 13, 15, 17,
19

Handover Control
Recom
Name Range Value
Value
3GPP TS 25.331: Fn =
measurement result;
filtering factor;
impact the latest
the event report).
62. Amount of This parameter indicates the

URatRscpPr 1, 2, 4, 8,
Reporting in number of times that periodic
dMeas.PrdR 16, 32, 64, N/A Infinity Infinity
Period Report reports are reported. A UE
ptAmount Infinity
Criteria uses the parameter Amount

Handover Control
Recom
Name Range Value
Value
of reporting to determine
whether to report. If the UE
times of event reports
exceeds the parameter value,
it stops reporting
63. (250,
500, 1000,
2000,
3000,
4000,
Reporting 6000,
URatRscpPr This parameter indicates the
Interval in 8000,
dMeas.PrdR interval at which periodic ms 500 500
Period Report 12000,
ptInterval reports are reported.
Criteria 16000,
20000,
24000,
28000,
32000,
64000)ms
64. This parameter indicates a

cell individual offset. An offset
is allocated to each cell that is
monitored. The offset can be
positive or negative. Before a
UE determines whether an
event occurs, the offset
UExternalG should be added the (-50..50)
to
Cell Individual
smCell.CellI measurement quantity. If the dB step 1 dB 0dB 0dB
Offset
ndivOffset PCPICH uses a positive Db
the PCPICH is x dB better
than the actual case. If the
offset, The PCPICH report is
limited. When a cell individual

Handover Control
Recom
Name Range Value
Value
offset is used, the
cell for handover or removed

inter-RAT handover policy.
0:
In most scenarios, this
Algorithm
parameter is set to 3A Event
Deciding
Trigger to ensure precise
UUtranCellF Inter-RAT 1: 3A 1: 3A 1: 3A
inter-frequency handovers. In
DD.RatHoT Handover Event N/A Event Event
some scenarios where it is
actic Tactic Trigger Trigger Trigger
required to hand over to the
2: 3C
target cell as soon as
Event
possible, this parameter is set
Trigger
to Algorithm Deciding or 3C
Event Trigger.
66. If the inter-RAT measurement

is initialized, and an
intra-frequency handover is
triggered, the inter-RAT
measurement will be
updated/modified. The RNC
may receive UE reports
Inter-rat Cell based on original inter-RAT
URncFuncti
Information measurement configuration 0: False; 1:
on.RatCelInf N/A 0: False 0: False
indication due to the transmission delay True
oSwch
Strategy of radio interface.
RatCelInfoSwch is used to
control the policy. If it is set to
1, the measurement report
based on original inter-RAT
measurement configuration
will be handled to improve
handover timeliness.
67. ULogicalRn Handover to This parameter indicates that 0..65535s

s 20s 20s
c.HoToGsm GSM Penalty this timer is initialized upon step 1s

Handover Control
Recom
Name Range Value
Value
PenTimer Timer handover failure from UMTS
to GSM. The RNC will not
handle inter-RAT
measurement reports until the
timer expires.

timer for waiting UEs hand
The waiting
over to 2G or DSCR when a
URncFuncti timer for UE
board is powered off. When
on.BoardPw Handover (0~65535) s 10s 10s
the timer expires, the CS
rOffHoTmr When Board's s, step 1s
service releases the RRC,
power is Off
and the PS service releases
the DSCR.
69. The parameter indicates

whether the cell is an indoor
cell. If the cell is an indoor
UExternalG
Indoor Cell cell, because signals change 0: False; 1:
smCell.Indo N/A 0: False 0: False
Indicator quickly, the handover True
orCellInd
parameter should be set a
more sensitive value to
ensure timely handovers.
70. 0: Turn off

Inter-frequ
ency and
Inter-RAT
Handover 3: Inter 3: Inter
This parameter indicates how
Inter Frequency 1: Only Frequen Frequen
UCelInfoFD to perform neighbor
or Inter RAT Inter cy Is cy Is
D.IfOrRatHo measurement if both the N/A
Handover Frequency Prior to Prior to
Swch inter-frequency and inter-RAT
Switch 2: Only Inter Inter
neighboring cells exist.
Inter RAT RAT RAT
3: Inter
Frequency
Is Prior to
Inter RAT
71. UCelInfoFD Time To Trigger This parameter indicates the (0..255)s,

s 0s 0s
D.PeriodTrig for interval between reception of step 1s

Handover Control
Recom
Name Range Value
Value
gerTime Inter-frequency periodic reports and triggering
and Inter-Rat of the inter-frequency or
Period inter-RAT handover. Only the
Measurement neighboring cell in which the
signal quality is above a
certain threshold in all
periodic reports during a time
equal to this parameter can
be selected as the target cell
for the inter-frequency or
inter-rat handover. If this
parameter is set to a large
value, the probability of
incorrect decision is low.
However, the handover
algorithm becomes slow in
responding to signal change.
72. This parameter is a switch

Switch of
that determines whether to fill
RXLEV-NECEL
URncInfo.rxl the oldBSS_ToNewBSS 0:Off
L indication in N/A 1:On 1:On
evNecellInd information with the 1:On
oldBSS_ToNew
RXLEV-NECELL indication
BSS
during a 3G-to-2G handover.

duration for waiting for the
SRNS CONTEXT REQUEST
message.
Enabled: This timer is
enabled when the cell is
Waiting Timer 1..500,
URncFuncti relocated to another RAT.
for SRNS step 1;
on.TwaitCon Expiration: When an IU 100ms 200 200
Context Unit:
textReq RELEASE REQ message is
Request 100ms
transmitted, another timer for
waiting for IU RELEASE
COMMAND from CN is
enabled.
Disabled: The timer is
disabled when the SRNS

Handover Control
Recom
Name Range Value
Value
receives an SRNS CONTEXT
REQUEST message.

duration for waiting for the
SRNS DATA FORWARD
COMMAND message.
Enabled: This timer is
enabled after the SRNS
transmits the CONTEXT
RESPONSE message to the
Waiting Timer CN. 1..500,
URncFuncti
for SRNS DATA Expiration: When an IU step 1;
on.TWaitDat 100ms 50 50
FORWARD RELEASE REQ message is Unit:
aFwd
COMMAND transmitted, the timer for 100ms
waiting for the IU RELEASE
COMMAND message from
CN is enabled.
Disabled: The timer is
receives the SRNS DATA
FORWARD COMMAND
message.

duration for waiting for the IU
RELEASE COMMAND
message. Enabled: This timer
Waiting Timer is enabled after the SRNS
of SRNS for IU receives the DATA
RELEASE FORWARD COMMAND 1..500,
URncFuncti
COMMAND message or the timer that step 1;
on.TWaitRel 100ms 50 50
while PS waits for the DATA Unit:
Cmd
service FORWARD COMMAND 100ms
handover from message expires. Expiration:
3G to 2G This timer expires when the Iu
resource is released.
Disabled: This timer is
receives the IU RELEASE

Handover Control
Recom
Name Range Value
Value
COMMAND message.
76. This parameter specifies the

time to start sending the
forwarded PDCP SDUs in the
target RNC during the
relocation of SRNS.
start time to During the relocation of the
send the SRNS, the target RNC starts
forwarded the timer that equals to the
UIuCnst.Tda PDCP SDUs in value of the parameter after
(1..300)ms ms 80ms 80ms
tafwd the target RNC the target RNC receives the
, step 1ms
during UE's response, for example,
relocation of the
SRNS RadioBearReconfigComplete
message. After the timer
expires, the Target RNC
begins to send the forwarded
PDCP-SDUs to UE including
the Iu DL PDCP-SDUs.
4.5 ZWF21-03-006 Inter-RNC Handover with Iur Support
Table 4-5 Inter-RNC Handover with Iur Support Parameters List
Recom
Name Range Value
Value
1. UExternalUt Primary CPICH

ranCellFDD. Power 0: False; 1:
whether PCPICH transmitted N/A 0: False 0: False
PcpichPwrP Configuration True
power is configured.
re Tag
2. UExternalUt This parameter indicates the OMCR:

ranCellFDD. Primary CPICH PCPICH transmitted power of (-10..50)d 33.0dB 33.0dB
dBm
primaryCpic Power a neighboring cell. It is an Bm step m m
hPower absolute value. 0.1dBm;

Handover Control
Recom
Name Range Value
Value
RNC: D=
(P+10)*10,
0..600
3. This parameter is the 0:

UExternalR DRNC Diversity 0: 0:
neighboring cell's diversity Combined
ncFunction. Combination N/A Combin Combin
combination indicator when 1: Not
dIurCmbInd Indicator ed ed
the current RNC is a DRNC. Combined
4. This parameter is the

UExternalR SRNC Diversity 0: May
neighboring cell's diversity
ncFunction. Combination 1: Must N/A 0: May 0: May
combination indicator when
divCtrlInd Indicator 2: Must not
the current RNC is an SRNC.
5. 0: Not
handle
1: 1:
Event
Handle Handle
1A/1C/1D
Whether Event Event
UIurLink.Rn This parameter indicates reported
Process 1A/1C/1 1A/1C/1
cFeatSwitch whether SRNC handles Event by DRNC N/A
1A/1C/1D Event D D
Bit15 1A/1C/1D reported by DRNC. 1: Handle
of DRNC's Cell reported reported
Event
by by
1A/1C/1D
DRNC DRNC
reported
by DRNC
6. 0:Not
Process
Intra-Freq 1:Proce 1:Proce
uency ss ss
Events of Intra-Fre Intra-Fre
Whether
DRNC’s quency quency
Process This parameter indicates
UIurLink.Rn Cell in Events Events
Intra-Frequency whether the neighboring RNC
cFeatSwitch RRC N/A of of
Events of supports the soft handover
Bit16 Procedure DRNC’s DRNC’s
DRNC's Cell in based on DRNC during RRC.
1:Process Cell in Cell in
RRC Procedure
Intra-Freq RRC RRC
uency Procedu Procedu
Events of re re
DRNC’s
Cell in

Handover Control
Recom
Name Range Value
Value
RRC
Procedure

whether the 1a/1c/1d events
for CS services are handled
Event 1A/1C/1D
UCelInfoFD on the IUR interface. When
of DRNC's Cells 0:Off
D.CsIntraEv this parameter is set to On, N/A 0:Off 0:Off
for CS Service 1:On
tSwch 1a/1c/1d events for CS
Strategy Switch
services are not handled to
avoid IUR compatibility
problems.
8. 0:Not
This parameter indicates the Support
1:Suppo 1:Suppo
UIurLink.Rn Whether adjacent RNC feature PS(0 kbps
rt PS(0 rt PS(0
cFeatSwitch Support PS switch,0 means not support /0 kbps) N/A
kbps /0 kbps /0
Bit18 (0kbps/0kbps) PS(0 kbps /0 kbps) and 1 1:Support
kbps) kbps)
means support. PS(0 kbps
/0 kbps)
4.6 ZWF21-03-008 Directed Signaling Connection

Re-establishment
Table 4-6 Directed Signaling Connection Re-establishment Parameters List
Recom
Name Range Value
Value
1. 0: Not Use 0: Not 1: Use

Whether Use
DSCR for Use DSCR
DSCR for PS This parameter indicates
UIurLink.Rn PS DSCR for PS
Service When whether DSCR is performed
cFeatSwitch Service N/A for PS Service
UE all RLs on the PS service when all
Bit7 When UE Service When
Have Moved to RLs migrate to the DRNC.
all RLs When UE all
DRNC
Have UE all RLs

Handover Control
Recom
Name Range Value
Value
Moved to RLs Have
DRNC; Have Moved
1: Use Moved to
DSCR for to DRNC
PS DRNC
Service
When UE
all RLs
Have
Moved to
DRNC
2. 0: Not
Support
0: Not 1:
Hard
Whether Support Support
UIurLink.Rn This parameter indicates Handover
Support Hard Hard Hard
cFeatSwitch whether a hard handover DSCR N/A
Handover Handov Handov
Bit4 DSCR is supported. 1: Support
DSCR er er
Hard
DSCR DSCR
Handover
DSCR

Switch of DSCR function switch for an RNC to
in Transferring execute a DSCR procedure
URncFuncti
Unsuccessfully when a UE fails to transfer
on.dscrInC 0: Off
from Common from common connected N/A 0: Off 1: On
mnToDedS 1: On
Status to RRC status to dedicated
wch
CELL_DCH connected RRC status and
status returns a configuration-related
failure cause.
4.7 ZWF21-03-009 Coverage Based Handover
Coverage Based Handover includes intra-frequency handover, inter-frequency handover,

and inter-RAT handover. Therefore, the parameters relative to this feature, please refer
to 4.1 ZWF21-03-001 Soft/Softer Handover, 4.2 ZWF21-03-002 Intra-Frequency Hard

Handover Control
Handover, 4.3 ZWF21-03-003 Inter-Frequency Hard Handover, 4.4 ZWF21-03-004

Inter-RAT Mobility.
4.8 ZWF21-03-010 Compressed Mode
Table 4-7 Compressed Mode Parameters List
Recom
Name Range Value
Value
1. 2:FDD
Measurem
ent
3:GSM
carrier
RSSI
Measurem
ent
4:GSM
Initial
BSIC
This parameter indicates the Identificati
UCompress purpose of measurement on UCompr UCompr
Measurement
Mode.Meas performed by the UE during 5:GSM N/A essMod essMod
Purpose
Purpose the transmission gaps of each BSIC e e
of the TGPSs. Re-confirm
ation
6:
EUTRAN
Measurem
ent
these
values
must be
configured
fully and
uniquely.
2. UCompress Downlink This parameter indicates the 0: Frame UCompr UCompr

N/A
Mode.DlFra Frame Type downlink frame type used in Type A essMod essMod

Handover Control
Recom
Name Range Value
Value
meType downlink compressed mode, 1: Frame e e
which can be type A or B. Type B

TGCFN TGCFN hysteresis coefficient UCompr UCompr
UCompress
Hysteresis used for correcting the time of 1..100 N/A essMod essMod
Mode.K
Coefficient the starting of the e e
transmission gap pattern.

maximum number of
repetition of patterns that the
UE shall use to attempt to
decode the unknown BSIC of
the GSM cell in the initial
UCompress BSIC identification procedure. UCompr UCompr
Mode.NIdAb N Identify Abort If the UE has not successfully 1..128 N/A essMod essMod
ort decoded the BSIC of the e e
GSM BCCH carrier within
Nidentify_abort successive
patterns, the UE shall
continue to try to perform
BSIC identification of the next
GSM BCCH.

offset of the position of TGPS
relative to the first frame for
which compressed mode is
enabled. TGCFN is specified
in number of frames.
UCompress Typically, TGCFN for the first UCompr UCompr
Mode.TGCF TGCFN Offset TGPS is set to 0, to start 0..255 N/A essMod essMod
NOffset compressed mode as soon as e e
possible. The other TGPSs
must have an offset to the first
TGPS so that there is never
more than one transmission
gap in a frame. Otherwise, an
error will occur when the

Handover Control
Recom
Name Range Value
Value
transmission gaps collide.

number of slots between the
starting slots of TGL1 and
TGL2 in the transmission gap
Transmission pattern. This setting is only (15..269, UCompr UCompr
UCompress
Gap Start applicable when TGL2 is Undefined) slots essMod essMod
Mode.TGD
Distance non-zero. If there is only one slots e e
transmission gap in the
transmission gap pattern, this
parameter should be set as
‘Undefined’.

length (in slots) of the first
Enumerate
transmission gap in the UCompr UCompr
UCompress Transmission d
transmission gap pattern. slots essMod essMod
Mode.TGL1 Gap Length 1 (3,4,5,7,10
Note that there cannot be e e
,14) slots
more than 7 transmission gap
slots within one frame.

Enumerate
length (in slots) of the second
d
transmission gap in the
(0,3,4,5,7,
transmission gap pattern.
10,14)slots
Note that there cannot be
,where 0
more than 7 transmission gap UCompr UCompr
UCompress Transmission means
slots within one frame. If this slots essMod essMod
Mode.TGL2 Gap Length 2 invalid, is a
parameter is not explicitly set e e
custom
by higher layers, then TGL2 =
value, not
TGL1.
defined by
Also, if TGL2 is non-zero, a
the
valid TG Start Distance (TGD)
protocol.
must be specified.
9. This parameter indicates the (2..144)

UCompress Transmission UCompr UCompr
length of the transmission gap frames
Mode.TGPL Gap Pattern 1 frames essMod essMod
pattern 1, expressed in step 2
1 Length e e
number of frames. frames
10. UCompress Transmission This parameter indicates how Infinity, N/A UCompr UCompr

Handover Control
Recom
Name Range Value
Value
Mode.TGPR Gap Pattern many times the transmission 1..511 essMod essMod
C Repetition gap pattern is repeated in a e e
Count transmission gap pattern
sequence.

slot number of the first
transmission gap slot within
the first radio frame of the
transmission gap pattern;
which specifies the placement
(slot 0 through slot 14) of
Transmission UCompr UCompr
UCompress TGL1. A transmission gap (0..14)slot
Gap Starting slots essMod essMod
Mode.TGSN begins in a radio frame, which s
Slot Number e e
is called the first radio frame
of the transmission gap
pattern and contains at least
one transmission gap slot.
Refer to "Transmission Gap
Pattern Repetition Count" for
figure and table explanation.

longest time length allowed
UCompress (0.5..10.0) UCompr UCompr
T Reconfirm for the re-confirmation of the
Mode.TRecf s step 0.5 s essMod essMod
Abort BSIC of one GSM cell in the
gAbort s e e
BSIC re-confirmation
procedure.

uplink compressed mode 0: SF/2
UCompress Uplink method. The supported 1: Higher UCompr UCompr
Mode.UlCM Compressed methods are spreading factor Layer N/A essMod essMod
Method Mode Method division by two and higher Schedulin e e
layer scheduling. For details, g
refer to 3GPP TS 25.212.

UCompress UL/DL 0:UL only UCompr UCompr
UL/DL compressed mode
Mode.UlDlM Compressed 1:DL only N/A essMod essMod
selection, which specifies
ode Mode Selection 2:UL/DL e e
whether compressed mode is

Handover Control
Recom
Name Range Value
Value
used in UL only, DL only, or
both UL and DL.
15. 0:
Support Accompan
Accompanying ying 0: 0:
UIurLink.Rn Compressed Compress Accomp Accomp
whether accompanying
cFeatSwitch Mode or ed N/A anying anying
compressed mode is
Bit9 Dedicated 1: Compre Compre
supported.
Compressed Dedicated ssed ssed
Mode Compress
ed Mode
16. 0:
Configure
Inter-Freq
0: 0:
uency and
Configur Configur
Inter-Rat
e e
This parameter indicates compresse
Inter-Fre Inter-Fre
whether inter-frequency and d mode
Compressed quency quency
ULogicalRn inter-RAT compressed modes simultaneo
Mode and and
c.CompMdC are configured to UE usly N/A
Configuration Inter-Rat Inter-Rat
fgStra simultaneously or not when 1:
Strategy compres compres
inter-frequency and inter-RAT Configure
sed sed
neighboring cells exist. Inter-Freq
mode mode
uency and
simultan simultan
Inter-Rat
eously eously
compresse
d mode
individually
17. 0: Not 1: 1:
Whether Activate Activate Activate
Activate Compress Compre Compre
whether the neighboring RNC
UIurLink.Rn Compressed ed Mode ssed ssed
supports the CS service and
cFeatSwitch Mode for CS for CS N/A Mode Mode
activates the compressed
Bit17 Service When service for CS for CS
mode when IUR radio links
Radio Link via When service service
exist.
IUR Exists Radio Link When When
via IUR Radio Radio

Handover Control
Recom
Name Range Value
Value
exsits Link via Link via
1: Activate IUR IUR
Compress exists exists
ed Mode
for CS
service
When
Radio Link
via IUR
exists
18. bit3: This parameter indicates

bit3:
the configuration mode of
0:
compressed mode bit3: bit3:
URncFuncti Global associated
parameters in the hard 0: 0:
on.GResPar Reserved mode N/A
handover process. 0: associat associat
a56 Parameter 56 1:
associated mode, 1: ed mode ed mode
dedicated
dedicated mode. The default
mode
value is 0.
19. bit4: This parameter indicates
the configuration mode of
compressed mode bit4:
parameters in other 0:
bit4: bit4:
URncFuncti Global processes other than the associated
0: 0:
on.GResPar Reserved state transition from common mode N/A
associat associat
a56 Parameter 56 state to dedicated state and 1:
ed mode ed mode
hard handover processes. 0: dedicated
associated mode, 1: mode
dedicated mode. The default
value is 0.
4.8.1 UCompressMode
3: GSM
2: FDD 4: GSM Initial 5: GSM BSIC 6: EUTRAN
UCompressMode. carrier RSSI
Measuremen BSIC Re-confirmati Measureme
MeasPurpose Measuremen
t Identification on nt
t
UCompressMode. 0: Frame 0: Frame 0: Frame 0: Frame 0: Frame

DlFrameType Type A Type A Type A Type A Type A

Handover Control
UCompressMode.
1 1 1 1 1
K
UCompressMode.
66 66 66 66 66
NIdAbort
UCompressMode.
9 0 3 6 9
TGCFNOffset
UCompressMode.
Undefined Undefined Undefined Undefined Undefined
TGD
UCompressMode.
7 7 7 7 10
TGL1
UCompressMode.
0 0 0 0 0
TGL2
UCompressMode.
8 8 8 8 8
TGPL1
UCompressMode.
Infinity Infinity Infinity Infinity Infinity
TGPRC
UCompressMode.
3 4 4 4 9
TGSN
UCompressMode.
10 10 10 10 10
TRecfgAbort
UCompressMode.
0: SF/2 0: SF/2 0: SF/2 0: SF/2 0: SF/2
UlCMMethod
UCompressMode.
2:UL/DL 2:UL/DL 2:UL/DL 2:UL/DL 2:UL/DL
UlDlMode
4.9 ZWF21-03-011 Neighboring Cells Priorities
Table 4-8 Neighboring Cells Priorities Parameters List
Recom
Name Range Value
Value
1. Measurement This parameter indicates the
UUtranRelat
Priority of measurement priority of the
ion.MeasPri 0..2 N/A 0 0
Neighboring neighboring cell. The highest
o
Cell priority is 0, and the lowest

Handover Control
Recom
Name Range Value
Value
priority is 2.
The larger the parameter
value is, the lower the priority
is. When the number of
neighboring cells in a macro
diversity exceeds 32, there is
a high probability that cells
are removed (that is, the
probability of handover to this
cell is low).
The smaller the parameter
value is, the higher the priority
neighboring cells in a macro
diversity exceeds 32, there is
a low probability that cells are
removed (that is, the
cell is high).

measurement priority of a
neighboring cell. The highest
priority is 0, and the lowest
priority is 2.
The greater the parameter
value is, the lower the priority
Measurement
neighboring cells in macro
UGsmRelati Priority of
diversity mode exceeds 32, 0..2 N/A 0 0
on.MeasPrio Neighboring
there is a high probability that
GSM Cell
cells are removed (that is, the
cell is low).
The smaller the parameter
value is, the higher the priority
neighboring cells in macro
diversity mode exceeds 32,

Handover Control
Recom
Name Range Value
Value
there is a low probability that
cells are removed (that is, the
cell is high).
4.10 ZWF21-03-020 SRNS Relocation
Table 4-9 SRNS Relocation Parameters List
Recom
Name Range Value
Value
1. 0: Not
Support
UE not
1: 1:
Involved
Support Support
Whether Relocation
This parameter indicates UE not UE not
UIurLink.Rn Support UE not for CS
whether UE-unrelated Involved Involved
cFeatSwitch Involved service N/A
relocation of the CS service is Relocati Relocati
Bit10 Relocation for 1: Support
supported. on for on for
CS Service UE not
CS CS
Involved
service service
Relocation
for CS
service
2. 0: Not
Support
1: 1:
UE not
Support Support
Whether Involved
This parameter indicates UE not UE not
UIurLink.Rn Support UE not Relocation
whether UE-unrelated Involved Involved
cFeatSwitch Involved for PS N/A
relocation of the PS service is Relocati Relocati
Bit11 Relocation for service
supported. on for on for
PS Service 1: Support
PS PS
UE not
service service
Involved
Relocation

Handover Control
Recom
Name Range Value
Value
for PS
service
3. 0..65535,
step 1,
Timer of
UIurLink.Cs This parameter indicates the where 0
Relocation
ReDelayTim length of the relocation delay meas no 100ms 300 300
Delay for CS
er timer for CS services. delay;
Service
Unit:
100ms
4. 0..65535,
step 1,
Timer of
UIurLink.Ps This parameter indicates the where 0
Relocation
ReDelayTim length of the relocation delay meas no 100ms 0 0
Delay for PS
er timer for PS services. delay;
Service
Unit:
100ms

maximum time of the
Relocation Preparation
procedure in the source
RNC..When the SRNC
transmits a RELOCATION
REQUIRED message to the
CN, timer Trelocprep is
enabled. When receiving the
SRNC Wait 1..300,
RELOCATION COMMAND
UIuCnst.Trel Time for step 1;
message, the source RNC 100ms 60 60
ocprep Relocation Unit:
stops timer Trelocprep, and
Preparation 100ms
terminates the Relocation
Preparation procedure. If
there is no response from the
CN to the RELOCATION
REQUIRED message before
timer Trelocprep expires in
the source RNC, the source
RNC cancels the Relocation
Preparation procedure by

Handover Control
Recom
Name Range Value
Value
initiating the Relocation
Cancel procedure with the
appropriate value for the
Cause IE, e.g. "Trelocprep
expiry".

maximum time for protecting
the entire relocation
procedure in the SRNC.
When receiving the
RELOCATION COMMAND
message the source RNC
stops timer Trelocprep, starts 1..300,
SRNC Overall
UIuCnst.Trel timer Trelocoverall and step 1;
Protective Time 100ms 80 80
ocoverall terminates the Relocation Unit:
for Relocation
Preparation procedure. If the 100ms
CN fails to start the Iu
Release process after timer
Trelocoverall expires, the
source RNC initiates the Iu
Release Request procedure
with TRELOCoverall expiry as
the cause.
7. 0: when 0: when 0: when

This switch control what
DRNC DRNC DRNC
moment should send
received received received
Relocation Detect message to
UtranMobil UtranMo UtranMo
CN in soft handover
ityInformati bilityInfo bilityInfo
The occasion of relocation procedure: when
onConfirm rmation rmation
send Relocation DRNC received
URncInfo.se message Confirm Confirm
Detect UtranMobilityInformationConfi
ndDetetOcc from UE, NA messag messag
message to CN rm message from UE, then
a then send e from e from
in soft handover send Relocation Detect
Relocation UE, then UE, then
relocation message to CN / When
Detect send send
DRNC received Relocation
message Relocati Relocati
Commit message from
to CN; on on
SRNC, then send Relocation
1: When Detect Detect
Detect message to CN.
DRNC messag messag

Handover Control
Recom
Name Range Value
Value
received e to CN; e to CN;
Relocation
Commit
message
from
SRNC,
then send
Relocation
Detect
message
to CN.
8. Whether This parameter is the

UIurLink.Rn Support RNC functional switch that enables
0: Off
cFeatSwitch forward PDCP or disables the Iur interface to N/A 0: Off 0: Off
1: On
Bit25 data when support the data forwarding
Relocation function during relocation.
9. 0:
Hard-hand
over
1: 1:
Without
Hard-ha Hard-ha
Whether Relocation
This parameter indicates ndover ndover
UIurLink.Rn Support for CS
whether a CS hard handover With With
cFeatSwitch Hard-handover Service N/A
is accompanied with Relocati Relocati
Bit0 With Relocation 1:
relocation. on for on for
for CS Service Hard-hand
CS CS
over With
Service Service
Relocation
for CS
Service
10. 0: PS
Hard-hand 1: PS 1: PS
Whether
This parameter indicates over Hard-ha Hard-ha
UIurLink.Rn Support
whether a PS hard handover Without ndover ndover
cFeatSwitch Hard-handover N/A
is accompanied with Relocation With With
Bit19 With Relocation
relocation. 1: PS Relocati Relocati
for PS Service
Hard-hand on on
over With

Handover Control
Recom
Name Range Value
Value
Relocation
11. 0: Not
Support
0: Not 0: Not
Hard
Whether Support Support
UIurLink.Rn This parameter indicates Handover
Support Hard Hard Hard
cFeatSwitch whether a hard handover DSCR N/A
Handover Handov Handov
Bit4 DSCR is supported. 1: Support
DSCR er er
Hard
DSCR DSCR
Handover
DSCR
5 Related Counters and Alarms
5.1 Related Counters
Table 5-1 Soft/Softer Handover Counter List
Counter ID Name
1. Number of attempted prepare to setup radio link
C310322211
for soft handover
2. Number of failed prepare to setup radio link for soft
C310322212
handover ,TNL fail
C310322213
handover ,UP fail
C310322214
handover ,NodeB fail
C310322215
handover ,access control refuse
6. Number of attempted active set update to add cell,
C310322216
softer handover
C310322217
soft handover

Handover Control
8. Number of failed active set update to add cell,

C310322219
softer handover
9. Number of failed active set update to add cell, soft
C310322220
handover
10. Number of attempted active set update to del cell,
C310322232
softer handover
C310322233
soft handover
12. Number of failed active set update to del cell,
C310326690
softer handover
13. Number of failed active set update to del cell, soft
C310326691
handover
14. C310322409 Number of UE with softer handover state in cell
15. Average number of UE with softer handover state

C310322410
in cell
16. C310322487 Number of active set update, Conversational class
17. C310322488 Number of active set update ,Streaming class
18. C310322489 Number of active set update, Interactive class
19. C310322490 Number of active set update ,Background class
20. Number of failed active set update for

C310322491
Conversational class
21. Number of failed active set update for Streaming
C310322492
class
22. Number of failed active set update for Interactive
C310322493
class
23. Number of failed active set update for Background
C310322494
class
24. Number of attempted active set update add cell
C310322495
include CS domain traffic
25. Number of attempted active set update add cell
C310322496
include PS domain traffic
26. Number of failed active set update add cell include
C310322497
CS domain traffic
27. Number of failed active set update add cell include
C310322498
PS domain traffic
28. Number of attempted active set update del cell
C310322499
include CS domain traffic
29. Number of attempted active set update del cell
C310322500
include PS domain traffic

Handover Control
30. Number of failed active set update del cell include

C310322501
CS domain traffic
31. Number of failed active set update del cell include
C310322502
PS domain traffic
32. Number of detected set cell can be added in active
C310910200
set
33. 300451 Soft Handover Success Rate
34. 300865 UL Bler for DCH
35. 300867 UL Bler for RT
36. 300868 UL Bler for NRT
Table 5-2 Intra-Frequency Hard Handover Counter List
Counter ID Name
1. Number of outgoing intra frequency hard handover

C310332597
attempt, Radio quality required
C310332601
failed, Radio quality required
C310335701
attempt, Admission failed
C310335702
attempt, No Report Adjacency Cell Information
C310335703
attempt, No Iur
C310335704 attempt, Capability of Adjacency Cell And Source
Cell Unlikeness
C310335706
failed, Admission failed
C310335707
failed, No Report Adjacency Cell Information
9. Number of failed outgoing intra frequency hard
C310335708
handover failed ,No Iur
C310336596 failed, Capability of Adjacency Cell And Source
Cell Unlikeness

Handover Control

C310332649
attempt, Conversational class
C310332650
attempt, Streaming class
C310332651
attempt, Interactive class
C310332652
attempt, Background class
C310332657
failed, Conversational class
C310332658
failed, Streaming class
C310332659
failed, Interactive class
C310332660
failed, Background class
C310332665
attempt, CS domain
C310332666
attempt, PS domain
C310332669
failed, CS domain
C310332670
failed, PS domain
23. Number of attempted intra-RNC intra-frequency
C310336605
hard handover, CS domain traffic
24. Number of attempted intra-RNC intra-frequency
C310336606
hard handover, PS domain traffic
25. Number of successful intra-RNC intra-frequency
C310336607
26. Number of successful intra-RNC intra-frequency
C310336608
27. Number of attempted inter-RNC intra-frequency
C310336613
28. Number of attempted inter-RNC intra-frequency
C310336614
29. Number of successful inter-RNC intra-frequency
C310336615
30. Number of successful inter-RNC intra-frequency
C310336616
31. 300981 Intra-Freq Hard Handover Success Rate

Handover Control
Table 5-3 Inter-Frequency Hard Handover Counter List
Counter ID Name
1. Number of Inter-Frequency Handover Attempts for

C310332608
CS services due to RSCP
C310332609
CS services due to EcNo
3. Number of successful Inter-Frequency Handover
C310332619
for CS services due to RSCP
C310332620
for CS services due to EcNo
C310332630
PS services due to RSCP
C310332631
PS services due to EcNo
C310332641
for PS services due to RSCP
C310332642
for PS services due to EcNo
9. Number of outgoing inter frequency hard handover
C310332653
attempt, Conversational class
C310332654
attempt, Streaming class
C310332655
attempt, Interactive class
C310332656
attempt, Background class
C310332661
failed, Conversational class
C310332662
failed, Streaming class
C310332663
failed, Interactive class
C310332664
failed, Background class
C310332667
attempt, CS domain
C310332668
attempt, PS domain

Handover Control

C310332671
failed, CS domain
C310332672
failed, PS domain
21. Number of attempted intra-RNC inter-frequency
C310336609
22. Number of attempted intra-RNC inter-frequency
C310336610
23. Number of successful intra-RNC inter-frequency
C310336611
24. Number of successful intra-RNC inter-frequency
C310336612
25. Number of attempted inter-RNC inter-frequency
C310336617
26. Number of attempted inter-RNC inter-frequency
C310336618
27. Number of successful inter-RNC inter-frequency
C310336619
28. Number of successful inter-RNC inter-frequency
C310336620
29. Success Rate of RNC Inter-Frequency Outgoing
300955
Hard Handover
Table 5-4 Inter-RAT Mobility Counter List
Counter ID Name
1. Number of attempted relocation preparation for
C310352913 outgoing CS inter-RAT handovers, Relocation
desirable for radio reasons
2. Number of failed relocation preparation for
C310352918 outgoing CS inter-RAT handovers, TRELOCalloc
Expiry
failed In Target CN/RNC Or Target System
C310352920 outgoing CS inter-RAT handovers, Relocation Not
Supported In Target RNC Or Target System

Handover Control

Target not allowed
C310352922 outgoing CS inter-RAT handovers, No Radio
Resources Available in Target Cell
C310352923 outgoing CS inter-RAT handovers, Traffic Load In
The Target Cell Higher Than In The Source Cell
C310352924 outgoing CS inter-RAT handovers, Unknown
Target RNC
C310352926
outgoing CS inter-RAT handovers, No Reply
10. Number of attempted relocation preparation for
C310352929 outgoing PS inter-RAT handovers, Relocation
C310352934 outgoing PS inter-RAT handovers, TRELOCalloc
Expiry
failed In Target CN/RNC Or Target System
C310352936 outgoing PS inter-RAT handovers, Relocation Not
Target not allowed
C310352938 outgoing PS inter-RAT handovers, No Radio
Resources Available in Target Cell
C310352939 outgoing PS inter-RAT handovers, Traffic Load In
The Target Cell Higher Than In The Source Cell
C310352940 outgoing PS inter-RAT handovers, Unknown
Target RNC
C310352942
outgoing PS inter-RAT handovers, No Reply

Handover Control

C310352941
outgoing PS inter-RAT handovers, Other Causes
20. Number of attempted outgoing CS inter-RAT
C310352945
handovers
21. Number of failed outgoing CS inter-RAT
C310352946
handovers, Configuration unacceptable
C310352947
handovers, Physical Channel failed
C310352948
handovers, Protocol Error
C310352949
handovers, Inter-RAT Protocol Error
C310352950
handovers, Unspecified failed
C310352951
handovers, No Reply
27. Number of attempted outgoing PS inter-RAT
C310352952
handovers
28. Number of failed outgoing PS inter-RAT
C310352953
handovers, Configuration unacceptable
C310352954
handovers, Physical Channel failed
C310352955
handovers, Protocol Error
C310352956
handovers, Inter-RAT Protocol Error
C310352957
handovers, Unspecified failed
C310352958
handovers, No Reply
34. Number of attempted outgoing PS inter-RAT
C310352959
handovers(Cell Change Order)
C310352960 handovers, Configuration unacceptable(Cell
Change Order)
C310352961 handovers, Physical Channel failed(Cell Change
Order)
C310352962
handovers, Protocol Error(Cell Change Order)

Handover Control

C310352963
handovers, Unspecified failed(Cell Change Order)
C310352964
handovers, No Reply(Cell Change Order)
40. Cell Inter-RAT CS Outgoing Handover Success
300476
Rate(WCDMA->GSM)
41. Cell Inter-RAT PS Outgoing Handover Success
300478
Rate(WCDMA->GPRS)
Table 5-5 Inter-RNC Handover with Iur Support Counter List
Counter ID Name
C310322218
Iur soft handover
2. Number of failed active set update to add cell, Iur
C310322221
soft handover
C310322234
Iur soft handover
4. Number of failed active set update to del cell, Iur
C310326692
soft handover
5. Number of outgoing inter-Rnc intra frequency hard
C310336856
handover preparation attempt
C310336857
handover preparation failed, TNL fail
C310336858
handover preparation failed, UP fail
C310336859
handover preparation failed, NodeB fail
C310336860
handover preparation failed, access control refuse
10. Number of outgoing inter-Rnc inter frequency hard
C310336861
handover preparation attempt
C310336862
handover preparation failed, TNL fail
C310336863
handover preparation failed, UP fail
C310336864
handover preparation failed, NodeB fail

Handover Control

C310336865
handover preparation failed, access control refuse
15. Number of outgoing inter-RNC intra frequency
C310332547
hard handover via Iur attempt
C310332548 hard handover via Iur failed, configuration
unsupported
C310332549 hard handover via Iur failed, Physical Channel
failed
C310332550 hard handover via Iur failed, Incompatible
Simultaneous Reconfiguration
C310332551 hard handover via Iur failed, Compress Mode
Error
C310332552
hard handover via Iur failed, Protocol Error
C310332553
hard handover via Iur failed, Cell Update Occurred
C310332554
hard handover via Iur failed, invalid configuration
incomplete
C310332556
hard handover via Iur failed, No Reply
C310332557
hard handover via Iur failed, Other Causes
26. Number of outgoing inter-RNC inter frequency
C310332558
hard handover via Iur attempt
unsupported
C310332560 hard handover via Iur failed, Physical Channel
failed
C310332561 hard handover via Iur failed, Incompatible

Handover Control

C310332562 hard handover via Iur failed, Compress Mode
Error
C310332563
hard handover via Iur failed, Protocol Error
C310332564
hard handover via Iur failed, Cell Update Occurred
C310332565
hard handover via Iur failed, invalid configuration
incomplete
C310332567
hard handover via Iur failed, No Reply
C310332568
hard handover via Iur failed, Other Causes
37. 301013 Soft Handover Success Rate for Iur
Table 5-6 SRNS Relocation Counter List
Counter ID Name
1. Number of attempted relocation preparation with

C310342745 UE not involved for CS domain, Time Critical
Relocation
C310342746 UE not involved for CS domain, Resource
Optimization Relocation
C310342747 UE not involved for CS domain, Relocation
C310342748
UE not involved for CS domain, Directed Retry
C310342749 UE not involved for CS domain, Reduce Load in
Serving Cell
C310342750 UE not involved for CS domain, Access Restricted
Due to Shared Networks

Handover Control

C310342751
UE not involved for CS domain, Other Causes
8. Number of failed relocation preparation with UE
C310342752
not involved for CS domain, TRELOCalloc Expiry
C310342753 not involved for CS domain, Relocation failed In
Target CN/RNC Or Target System
C310342754 not involved for CS domain, Relocation Not
C310342755 not involved for CS domain, Relocation Target not
allowed
C310342756 not involved for CS domain, No Radio Resources
Available in Target Cell
C310342757 not involved for CS domain, Traffic Load In The
Target Cell Higher Than In The Source Cell
C310342758
not involved for CS domain, Unknown Target RNC
C310342760
not involved for CS domain, No Reply
C310342759
not involved for CS domain, Other Causes
17. Number of attempted outgoing relocation with UE
C310342761
not involved for CS domain
18. Number of failed outgoing relocation with UE not
C310342762
involved for CS domain, No Reply
C310342763
involved for CS domain, Other Causes
C310342764 UE involved for CS domain, Time Critical
Relocation
C310342765 UE involved for CS domain, Resource
C310342766 UE involved for CS domain, Relocation desirable
for radio reasons

Handover Control

C310342767
UE involved for CS domain, Directed Retry
C310342768 UE involved for CS domain, Reduce Load in
Serving Cell
C310342769 UE involved for CS domain, Access Restricted
C310342770
UE involved for CS domain, Other Causes
C310342771
involved for CS domain, TRELOCalloc Expiry
C310342772 involved for CS domain, Relocation failed In Target
CN/RNC Or Target System
C310342773 involved for CS domain, Relocation Not Supported
In Target RNC Or Target System
C310342774 involved for CS domain, Relocation Target not
allowed
C310342775 involved for CS domain, No Radio Resources
C310342776 involved for CS domain, Traffic Load In The Target
Cell Higher Than In The Source Cell
C310342777
involved for CS domain, Unknown Target RNC
C310342779
C310342780
involved for CS domain
36. Number of failed outgoing relocation with UE
C310342781 involved for CS domain, configuration
unsupported
C310342782
involved for CS domain, Physical Channel failed
C310342783 involved for CS domain, Incompatible

Handover Control

C310342784
involved for CS domain, Compress Mode Error
C310342785
involved for CS domain, Protocol Error
C310342786
involved for CS domain, Cell Update Occurred
C310342787
involved for CS domain, invalid configuration
C310342788
involved for CS domain, configuration incomplete
C310342789
C310342790
involved for CS domain, Other failed
C310342791 UE not involved for PS domain, Time Critical
Relocation
C310342792 UE not involved for PS domain, Resource
C310342793 UE not involved for PS domain, Relocation
C310342794
UE not involved for PS domain, Directed Retry
C310342795 UE not involved for PS domain, Reduce Load in
Serving Cell
C310342796 UE not involved for PS domain, Access Restricted
C310342797
UE not involved for PS domain, Other Causes
C310342798
not involved for PS domain, TRELOCalloc Expiry
C310342799 not involved for PS domain, Relocation failed In
Target CN/RNC Or Target System
C310342800 not involved for PS domain, Relocation Not

Handover Control

C310342801 not involved for PS domain, Relocation Target not
allowed
C310342802 not involved for PS domain, No Radio Resources
C310342803 not involved for PS domain, Traffic Load In The
Target Cell Higher Than In The Source Cell
C310342804
not involved for PS domain, Unknown Target RNC
C310342806
not involved for PS domain, No Reply
C310342805
not involved for PS domain, Other Causes
C310342807
not involved for PS domain
C310342808
involved for PS domain, No Reply
C310342809
involved for PS domain, Other Causes
C310342810 UE involved for PS domain, Time Critical
Relocation
C310342811 UE involved for PS domain, Resource
C310342812 UE involved for PS domain, Relocation desirable
for radio reasons
C310342813
UE involved for PS domain, Directed Retry
C310342814 UE involved for PS domain, Reduce Load in
Serving Cell
C310342815 UE involved for PS domain, Access Restricted
C310342816
UE involved for PS domain, Other Causes

Handover Control

C310342817
involved for PS domain, TRELOCalloc Expiry
C310342818 involved for PS domain, Relocation failed In Target
CN/RNC Or Target System
C310342819 involved for PS domain, Relocation Not Supported
In Target RNC Or Target System
C310342820 involved for PS domain, Relocation Target not
allowed
C310342821 involved for PS domain, No Radio Resources
C310342822 involved for PS domain, Traffic Load In The Target
Cell Higher Than In The Source Cell
C310342823
involved for PS domain, Unknown Target RNC
C310342825
C310342824
involved for PS domain, Other Causes
C310342826
involved for PS domain
C310342827
involved for PS domain, configuration unsupported
C310342828
involved for PS domain, Physical Channel failed
C310342829 involved for PS domain, Incompatible
C310342830
involved for PS domain, Compress Mode Error
C310342831
involved for PS domain, Protocol Error
C310342832
involved for PS domain, Cell Update Occurred
C310342833
involved for PS domain, invalid configuration

Handover Control

C310342834
involved for PS domain, configuration incomplete
C310342835
C310342836
involved for PS domain, Other failed
5.1.7 ZWF21-03-008 Directed Signaling Connection Re-establishment
Table 5-7 Directed Signaling Connection Re-establishment Counter List
Counter ID Name
1. Number of RRC connection Release on DCCH

C310555142 due to Directed Signaling Connection
Re-establishment
2. Number of RRC connection Release on CCCH,
C310555149
directed signaling connection re-establishment
None
Table 5-8 Compressed Mode Counter List
Counter ID Name
1. Total number of Compressed Mode Command in

C310605484
Cell
2. C310585292 Total Number of Measurement Control Send
3. Number of Measurement Control to Activate

C310585293 Compressed Mode for Inter-frequency
Measurement

C310585294
Compressed Mode for Inter-RAT Measurement

C310585295
Compressed Mode for CS Service

Handover Control

C310585296
Compressed Mode for PS Service

C310585297
Compressed Mode for CS+PS Service

C310585298
Compressed Mode for Ec/No Measurement
C310585299
Compressed Mode for RSCP Measurement
10. Total Number of Measurement Control Failure
C310585300
Received
11. Number of Measurement Control Failure due to

C310585301
Compressed Mode Runtime Error
12. Number of Measurement Control Failure to

C310585308 Activate Compressed Mode for Inter-frequency
Measurement

C310585309 Activate Compressed Mode for Inter-RAT
Measurement

C310585310
Activate Compressed Mode for CS Service

C310585311
Activate Compressed Mode for PS Service

C310585312
Activate Compressed Mode for CS+PS Service

C310585313 Activate Compressed Mode for Ec/No
Measurement

C310585314 Activate Compressed Mode for RSCP
Measurement
5.2 Related Alarms
This feature has no related alarms.

Handover Control
6 Engineering Guide
6.1 Application Scenario
The intra-frequency handover indicates that UEs are handed over among the
intra-frequency neighboring cells, the inter-frequency handover indicates that UEs are
handed over to another frequency cell, and the inter-RAT handover indicates that UEs
are handed over to the neighboring cell of another system. As the basic and essential
functions, these handover functions are prerequisite for guaranteeing the normal
communication and maintaining communication continuity when UEs are moving among
neighboring cells.
Periodic reporting measurement in inter-frequency and inter-RAT handovers: In some

scenarios, the UE does not report the event or reports the event after a long delay, which
leads to handover execution not being in time and dropped calls. In this case, enabling
the periodic reporting measurement is recommended.
6.2 Feature Activation Procedure
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
The purpose of this chapter is just to guide the reader how to find the GUI location of the
parameters which are related to the deployment of this feature. The values indicated by
the captures possibly are not the real value to configure. Please refer to the last column
of table in chapter 4 for the practical configuration value.
In the configuration resource tree window, open the [Modify Area->Managed

Element->UMTS Logical Function Configuration->UTRAN Cell] interface and set the
parameter “Used UE Internal Measurement Profile”, “Used Intra-frequency Measurement
Profile”, “Cell Individual Offset”, “Detected Set Handover Switch”, “UTRAN Measurement

Handover Control
Quantity for Intra-frequency Measurements”, “Mobility Configuration Scene” and “Switch

of CS 64kbps Establishment”, as shown in Figure 6-1.
Figure 6-1 Parameters configuration interface 1

Handover Control

Handover Control
In the configuration resource tree window, open the [Modify Area->Managed Element->
UMTS Logical Function Configuration->UTRAN Cell->Adjacent Relation Configuration]
interface and set the parameter “Cell Individual Offset”, “UE State Indicator Used for
UTRAN Neighboring Cell Configuration” and “Share Cover Indication”, as shown in
below

Handover Control
UMTS Logical Function Configuration] interface and set the parameter “The Time
Threshold that the RNC May Resend the MEASUREMENT CONTROL RELEASE”,
“Switch of RNC Send RL SETUP and ACTIVE SET UPDATE parallelly when Soft Add
Handover” and “Global Reserved Parameter 47”, as shown in Figure 6-3.

Handover Control
UMTS Logical Function Configuration->PLMN Relating Configuration->Logic RNC
Configuration] interface and set the parameter “Switch for RL Reference Time Adjust
During Diversity Mode” and “Neighbouring Cell Monitoring Support Indicator”, as shown
in Figure 6-4.

Handover Control
UMTS Logical Function Configuration->Extended info of RNC] interface and set the
parameter “Intra-frequency Handover Penalty Timer”, as shown in Figure 6-5.

Handover Control
UMTS Logical Function Configuration->Service Configuration->Measurement
Configuration->UE Internal Measurement Profile] interface and set the parameter “Profile
Id”, as shown in Figure 6-6.

Handover Control
Configuration->UE Internal Measurement Profile->UE Rx-Tx Time Difference Event
Measurement Configuration for RL Timing Adjustment] interface and set the parameter
“UE Internal Measurement Configuration Index”, “Measurement Report Transfer Mode”,
“Filter Coefficient”, “Maximum Event Number of UE Internal Measurement”, “UE Internal
Measurement Event Identity”, “Time to Trigger” and “UE Rx-Tx Time Difference
Threshold” as shown in Figure 6-7.
Configuration->Intra-frequency Measurement Profile-> Intra-frequency Measurement
Configuration Related to Traffic Category] interface and set the parameter “Service and
Bearer Type Used for Differentiating Handover Configuration”, as shown in Figure 6-8.

Handover Control
Configuration->Intra-frequency Measurement Profile] interface and set the parameter
“Intra-frequency Measurement Profile Identity” and “Mobility Configuration Scene”, as
shown in Figure 6-9.

Handover Control
Configuration->Intra-frequency Measurement Profile> Intra-frequency Measurement
Configuration Related to Traffic Category->UE Intra-frequency Event Measurement
Configuration for CPICH Ec/No] interface and set the parameter “Amount of Reporting
for Event 1A/1B/1C/1J” , “Reporting Interval for Event 1A/1B/1C/1J”, “Filter Coefficient”,
“Hysteresis”, “Intra-frequency Measurement Configuration Index”, “Intra-frequency Event
Identity”, “Event Number of Intra-frequency Measurement”, “Replacement Activation
Threshold for Event 1C and 1J”, “Reporting Deactivation Threshold for Event 1A”,
“Reporting Range Constant for Event 1A/1B”, “Time To Trigger” and “Weight for Event
1A/1B”, as shown in Figure 6-10.

Handover Control
Configuration Related to Traffic Category->UE Intra-frequency Event Measurement
Configuration for CPICH RSCP] interface and set the parameter “Amount of Reporting
for Event 1A/1B/1C/1J” , “Reporting Interval for Event 1A/1B/1C/1J”, “Filter Coefficient”,
“Hysteresis”, “Intra-frequency Measurement Configuration Index”, “Intra-frequency Event
Identity”, “Event Number of Intra-frequency Measurement”, “Replacement Activation
Threshold for Event 1C and 1J”, “Reporting Deactivation Threshold for Event 1A”,
“Reporting Range Constant for Event 1A/1B”, “Time To Trigger” and “Weight for Event
1A/1B”, as shown in Figure 6-11.

Handover Control
Configuration Unrelated to Traffic Category->Detected Set Measurement Configuration
for CPICH Ec/No] interface and set the parameter “Amount of Reporting for Event
1A/1B/1C/1J”, “Reporting Interval for Event 1A/1B/1C/1J”, “Filter Coefficient”,
“Hysteresis”, “Intra-frequency Measurement Configuration Index”, “Reporting
Deactivation Threshold for Event 1A”, “Reporting Range Constant for Event 1A/1B”,
“Time To Trigger” and “Weight for Event 1A/1B”, as shown in Figure 6-12.

Handover Control
Configuration Unrelated to Traffic Category->Detected Set Measurement Configuration
for CPICH RSCP] interface and set the parameter “Amount of Reporting for Event

Handover Control
1A/1B/1C/1J”, “Reporting Interval for Event 1A/1B/1C/1J”, “Filter Coefficient”,

“Hysteresis”, “Intra-frequency Measurement Configuration Index”, “Reporting
Deactivation Threshold for Event 1A”, “Reporting Range Constant for Event 1A/1B”,
“Time To Trigger” and “Weight for Event 1A/1B”, as shown in Figure 6-13.
UMTS Logical Function Configuration] interface and set the parameter “Switch for notify
UE when LAC/RAC changed”, as shown in Figure 6-14

Handover Control
Please refer to ZWF21-03-001
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell and set
Inter Frequency or Inter RAT handover Switch, see the following figure.

Handover Control
Figure 6-1 Parameter Configuration Interface-1
Logical Function Configuration and set Timer for Stopping Inter-frequency
Measurement and Activating Inter-RAT Measurement (s), see the following figure.
In the configuration resource tree, select Modify Area->Managed Element->UMTS

Logical Function Configuration] interface and set the parameter “Inter-frequency
Handover Method” see the following figure.

Handover Control
Figure 6-3 Parameters configuration interface-3
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration and set AMR Inter Frequency Handover Switch, R99 RT Inter
Frequency Handover Switch, R99 NRT Inter Frequency Handover Switch, HSDPA
Inter Frequency Handover Switch, and HSUPA Inter Frequency Handover Switch,
see the following figure.

Handover Control
Logical Function Configuration > Service Configuration > Measurement
Configuration > UE Inter-frequency Measurement Profile and set Mobility
Configuration Scene and Inter-frequency Measurement Profile Identity, see the
following figure.
Logical Function Configuration > UTRAN Cell and set Inter-frequency Handover
Tactic and UTRAN Measurement Quantity for Inter-frequency and Inter-RAT
Measurements, see the following figure.

Handover Control
Configuration > UE Inter-frequency Measurement Profile > Inter-frequency
Measurement Configuration Related to Traffic Category and set Service and Bearer
Type Used for Differentiating Handover Configuration, see the following figure.

Handover Control
Logical Function Configuration > UTRAN Cell and set Used UE Inter-frequency
Measurement Profile, see the following figure.
Measurement Configuration Related to Traffic Category > UE Inter-frequency
Event Measurement Configuration for CPICH Ec/No(UTRAN) and set the following
parameters:
 Filter Coefficient
 Event Number of Inter-frequency Measurement
 Inter-frequency Event Identity
 Absolute Threshold of the Quality of the Currently Used Frequency for

2B/2D/2F
 Weight of the Currently Used Frequency for 2A/2B/2D/2F
 Hysteresis

Handover Control
 Time to Trigger
 Absolute Threshold of the Quality of the Non-used Frequency for 2B/2C/2E
 Weight of the Non-used Frequency for 2A/2B/2C/2E
See the following figure.
Measurement Configuration Related to Traffic Category > UE Inter-frequency
Event Measurement Configuration for CPICH RSCP (UTRAN) and set the following
parameters:
 Absolute Threshold of the Quality of the Currently Used Frequency for

2B/2D/2F

Handover Control
 Weight of the Currently Used Frequency for 2A/2B/2D/2F
 Hysteresis
 Time to Trigger
 Absolute Threshold of the Quality of the Non-used Frequency for 2B/2C/2E
 Weight of the Non-used Frequency for 2A/2B/2C/2E
Measurement Configuration Unrelated to Traffic Category > UE Inter-frequency
Period Measurement Configuration for CPICH Ec/No and set Filter Coefficient,
Amount of Reporting in Period Report Criteria, and Reporting Interval in Period
Report Criteria, see the following figure.

Handover Control
Measurement Configuration Unrelated to Traffic Category > UE Inter-frequency
Period Measurement Configuration for CPICH RSCP and set the parameter Filter
Coefficient, Amount of Reporting in Period Report Criteria, and Reporting Interval
in Period Report Criteria, see the following figure.

Handover Control
Logical Function Configuration > Extended Info of RNC and set Cpich Ec/No
Minimum Threshold for Inter-Frequency Handover, Cpich Rscp Minimum
Threshold for Inter-Frequency Handover, and Inter-frequency Handover Penalty
Timer, see the following figure.
Logical Function Configuration > UTRAN Cell > Extended Info of UTRAN Cell and
set Time to Trigger for Inter-frequency and Inter-Rat Period Measurement, see the
following figure.

Handover Control
set Switch of Judging Targt Cell's Minimum Quality in Inter-frequency Handover,
Logical Function Configuration > UTRAN Cell > Adjacent relation Configuration >

Handover Control
Neighbouring Cell and set Share Cover Indication and Cell Individual Offset, see the
following figure.
Logical Function Configuration and set The Time Threshold that the RNC May
Resend the MEASUREMENT CONTROL RELEASE, see the following figure.

Handover Control
Logical Function Configuration > UTRAN Cell > Adjacent relation Configuration >
GSM Neighbouring Cell and set Share Cover Indication, see the following figure.
set Switch of Blind Handover triggered by Second-Try, see the following figure.

Handover Control
Configuration and set the following parameters:
 AMR Inter Rat Handover Switch
 R99 RT Inter Rat Handover Switch
 R99 NRT Inter Rat Handover Switch
 HSDPA Inter Rat Handover Switch
 HSUPA Inter Rat Handover Switch
 Handover to GSM Penalty Timer
See the following figures.

Handover Control
Figure 6-15 Parameter Configuration Interfaces-20 and 21
Logical Function Configuration and keep the following parameters with their default
values:
 Inter-RAT Handover Method
 Inter-rat Cell Information indication Strategy
 The Time Threshold that the RNC May Resend the MEASUREMENT CONTROL
RELEASE
 The waiting timer for UE Handover When Board's power is Off

Handover Control
 Waiting Timer for SRNS Context Request
 Waiting Timer for SRNS DATA FORWARD COMMAND
 Waiting Timer of SRNS for IU RELEASE COMMAND while PS service

handover from 3G to 2G
Figure 6-16 Parameter Configuration Interfaces-22, 23, 24, and 25

Handover Control
Logical Function Configuration > UTRAN Cell > GSM Neighbouring Cell and keep
UE State Indicator Used for GSM Neighboring Cell Configuration with its default
value, see the following figure.
Logical Function Configuration > Service Configuration > Inter-RAT Measurement
Profile and set Inter-frequency Measurement Profile Identity and Mobility
Configuration Scene, see the following figure.

Handover Control
Logical Function Configuration > UTRAN Cell and set the following parameters:
 Mobility Configuration Scene
 Inter-RAT Handover Tactic
 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT

Measurements
 Used UE Inter-frequency Measurement Profile
 Used Inter-RAT Measurement Profile

Handover Control
Figure 6-19 Parameter Configuration Interfaces-28, 29, and 30
Configuration > Inter-RAT Measurement Profile > Inter-RAT Measurement
Configuration Related to Traffic Category and set Service and Bearer Type Used
for Differentiating Handover Configuration, see the following figure.

Handover Control
Configuration > UE Inter-frequency Measurement Profile and keep Inter-frequency
Measurement Profile Identity and Mobility Configuration Scene with their default
values, see the following figure.
Configuration > UE Inter-frequency Measurement Profile > UE Inter-frequency

Handover Control
Event Measurement Configuration for CPICH EcNo (GSM) and keep the following
parameters with their default values:
 Hysteresis
 Time to Trigger
 Weight of the Currently Used Frequency for 2D/2F
 Absolute Threshold of the Quality of the Currently Used Frequency for 2D/2F
Configuration > UE Inter-frequency Measurement Profile > UE Inter-frequency
Event Measurement Configuration for CPICH RSCP (GSM) and keep the following
parameters with their default values:
 Inter-frequency Measurement Configuration Index

Handover Control
 Hysteresis
 Time to Trigger
 Weight of the Currently Used Frequency for 2D/2F
Configuration Related to Traffic Category > UE inter-RAT Event Measurement
Configuration for CPICH RSCP (GSM) and keep the following parameters with their
default values:
 Inter-RAT Measurement Configuration Index
 Inter-RAT Event Identity

Handover Control
 Inter-RAT Measurement Event Number
 UTRAN Filter Coefficient
 GSM Filter Coefficient
 Hysteresis
 Time to Trigger
 Weight of the UTRAN System for 3A
 Absolute Threshold of the Quality of UTRAN Cell for 3A
 Absolute Threshold of the Quality of Other RAT for 3A/3B/3C
Configuration Related to Traffic Category > UE inter-RAT Event Measurement
Configuration for CPICH RSCP (GSM) and keep the following parameters with their
default values:
 Inter-RAT Measurement Configuration Index

Handover Control
 Inter-RAT Event Identity
 Inter-RAT Measurement Event Number
 UTRAN Filter Coefficient
 GSM Filter Coefficient
 Hysteresis
 Time to Trigger
 Weight of the UTRAN System for 3A
 Absolute Threshold of the Quality of UTRAN Cell for 3A
 Absolute Threshold of the Quality of Other RAT for 3A/3B/3C
In the configuration resource tree, Select Modify Area > Managed Element > UMTS
Logical Function Configuration > External Resource Configuration > External GSM
Cell and keep Cell Individual Offset and Indoor Cell Indicator with their default values,

Handover Control
Logical Function Configuration > Extended Info of RNC and keep Switch of
RXLEV-NECELL indication in oldBSS_ToNewBSS with its default value, see the
following figure.
Logical Function Configuration > PLMN Relating Configuration > Iu Interface
Timers AND Constants Information and set Start time to send the forwarded PDCP
SDUs in the target RNC during relocation of SRNS (ms), see the following figure.

Handover Control
Logical Function Configuration > External Resource Configuration > External RNC
Function > External UTRAN Cell and set Primary CPICH Power Configuration Tag, see
the following figure.
Logical Function Configuration > Link Configuration > Iur Link and set Whether

Handover Control
Process 1A/1C/1D Event of DRNC’s Cell, Whether Process Intra-Frequency Events

of DRNC’s Cell in RRC Procedure, and Whether Support PS (0Kbps/0Kbps), see the
following figure.
set Event 1A/1C/1D of DRNC’s Cells for CS Service Strategy Switch, see the
following figure.

Handover Control
6.2.6 ZWF21-03-008 Directed Signaling Connection Re-establish

Element->UMTS Logical Function Configuration->Link Configuration->Iur Link] and
make sure that the configuration of RNCFEATSWITCHBit4 as shown in Figure 6-29.
Figure 6-29 Parameters configuration interface 1 - DSCR

Handover Control

Element->UMTS Logical Function Configuration->Link Configuration->Iur Link] and
make sure that the configuration of RNCFEATSWITCHBit7 as shown in Figure 6-30.

Element->UMTS Logical Function Configuration] and make sure that the configuration of
dscrInCmnToDedSwch as shown in Figure 6-31.

Handover Control
Refer to ZWF21-03-001 Soft/Softer Handover.
Logical Function Configuration > Service Configuration > Basic Compress Mode
Configuration and set the following parameters:
 Measurement Purpose
 Transmission Gap Patten Repetition Count
 Transmission Gap Starting Slot Number (slots)
 Transmission Gap Length 1 (slots)
 Transmission Gap Length 2 (slots)
 Transmission Gap Start Distance (slots)
 Transmission Gap Patten 1 Length (frames)
 UL/DL Compressed Mode Selection
 Downlink Compressed Mode Method
 Uplink Compressed Mode Method

Handover Control
Logical Function Configuration > Service Configuration > Basic Compress Mode
Configuration and set TGCFN Offset, TGCFN Hysteresis Coefficient, N Identify
Abort, and T Reconfirm Abort (s), see the following figure.

Handover Control
Logical Function Configuration and set Global Reserved Parameter 14, see the following
figure.
Configuration and set Compressed Mode Configuration Strategy, see the following
figure.

Handover Control
Logical Function Configuration > Link Configuration > Iur Link and set Support
Accompanying Compressed Mode or Dedicated Compressed Mode and Whether
Activate Compressed Mode for CS Service When Radio Link via IUR Exists, see the
following figure.

Handover Control
Logical Function Configuration > UTRAN Cell > Adjacent Relation Configuration >
Neighboring Cell and set Measurement Priority of Neighboring Cell and UE State
Indicator Used for UTRAN Neighboring Cell Configuration, see the following figure.
Logical Function Configuration > UTRAN Cell > Adjacent Relation Configuration >
Neighbouring Cell and set Measurement Priority of Neighboring GSM Cell and UE
State Indicator Used for GSM Neighboring Cell Configuration, see the following
figure.

Handover Control
Logical Function Configuration > Link Configuration > Iur Link and set the following
parameters:
 Timer of Relocation Delay for CS Service
 Timer of Relocation Delay for PS Service
 Whether Support Hard-handover With Relocation for CS Service
 Whether Support Hard Handover DSCR

Handover Control
Support UE not Involved Relocation for CS Service and Whether Support UE not
Involved Relocation for PS Service, see the following figure.

Handover Control
Support Hard-handover With Relocation for PS Service and Whether Support RNC
forward PDCP data when Relocation, see the following figure.
Logical Function Configuration and set Global Reserved Parameter 48, see the
following figure.
Figure 6-33 Parameter Configuration Interface53

Handover Control
Logical Function Configuration > PLMN Relating Configuration > Iu Interface Timer
and Constants Information and set SRNC Wait Time for Relocation Preparation and
SRNC Overall Protective Time for Relocation, see the following figure.
6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure
Test Item Soft/Softer Handover
1. WCDMA system is ready.

2. Cell1 and Cell2 support HSUPA, HSDPA and DCH. Cell1 and Cell2
Preconditio belong to RNC1/NodeB1.

ns 3. Cell1 and Cell2 have the same frequency. Configures Cell1 and
Cell2 adjacent cells with different coverage.
4. UE1 camps on Cell1 in Idle mode.

Handover Control
Test Item Soft/Softer Handover
1. UE1 makes an AMR 12.2kbps voice call to another UE or PSTN in

Cell1. Hold the call.
2. UE1 moves from Cell1 to Cell2 to trigger event 1A. Cell2 is added
Test Steps into the active set.
3. UE1 continues moving to Cell2 until trigger event 1B and Cell1 is
removed from the active set.
4. Release the voice call.
Anticipative
UE1 performs the softer handover successfully.
Result
Test Item Intra-Frequency Hard Handover
1. WCDMA system ready.

2. Cell1 and Cell2 support HSUPA, HSDPA and DCH. Cell1 belongs
to RNC1/NodeB1. Cell2 belongs to RNC2/NodeB2.
Preconditio
3. Cell1 and Cell2 have the same frequency. Configures Cell1 and
ns
Cell2 adjacent cells with different coverage.
4. The Iur connection is not available between RNC1 and RNC2.
1. UE1 makes an AMR 12.2kbps voice call to another UE or PSTN in

Cell1. Hold the call.
Test Steps 2. UE1 moves from Cell1 to Cell2 to trigger event 1D. Then UE1
performs hard handover to Cell2.
Anticipative
UE1 performs the hard handover successfully.
Result

Handover Control
Test Item Inter-Frequency Hard Handover
1. The WCDMA system is ready.

2. Cell 1 and Cell 2 support HSUPA, HSDPA, and DCH. Cell 1
belongs to RNC1/NodeB1. Cell 2 belongs to RNC1/NodeB2.
3. Cell 1 and Cell 2 have different frequencies and coverage
Prerequisite
areas.
4. UE 1 camps on Cell 1 in Idle mode.
5. The Inter-frequency measurement parameter is set to CPICH
RSCP.
1. Use UE 1 to make an AMR 12.2kbps voice call to another UE

or PSTN in Cell 1. Hold the call.
2. Move UE 1 from Cell 1 to Cell 2 to trigger event 2D by CPICH
Steps RSCP and activate compressed mode.
3. Continue moving UE 1 to Cell 2 to trigger event 2A. Use UE 1
to perform a hard handover to Cell 2.
Expected Result UE 1 performs the hard handover successfully.
Test Item AMR Rate Controlling based on UE TxPower

2. Cell1 supports HSUPA, HSDPA and DCH. WCDMA Cell 1
belongs to RNC1/NodeB1, and GSM Cell 2 belongs to
BSC1/BTS1.
Prerequisite
3. Cell 1 and Cell 2 have different coverage areas.
4. Rel99 dual-mode UE 1 camps on Cell1 in Idle mode.
5. The Inter-frequency measurement parameter is set to
CPICH RSCP.

Handover Control
Test Item AMR Rate Controlling based on UE TxPower
1. Use UE 1 to make an AMR 12.2kbps voice call to another

UE or PSTN in Cell 1. Hold the call.
2. Move UE 1 from Cell 1 to Cell 2 to trigger event 2D by
Steps CPICH RSCP and activate compressed mode.
3. Continue moving UE 1 to Cell 2 to trigger event 3A/3C. Use
UE 1 to perform an inter-RAT handover to Cell 2.
Expected Result UE 1 performs the inter-RAT handover successfully.
Test Item Inter-RNC Soft Handover with Iur Support

2. Cell 1 and Cell 2 support HSUPA, HSDPA and DCH. Cell 1
belongs to RNC1/NodeB1. Cell2 belongs to RNC2/NodeB2.
3. Cell1 and Cell2 have the same frequency but different
Prerequisite coverage areas.
4. The Iur connection is available between RNC 1 and RNC 2.
5. The duration of the delay timer of relocation for the RT
service is set to 500 seconds.
1. Use UE 1 to makes an AMR 12.2kbps voice call to another

UE or PSTN in Cell1. Hold the call.
2. Move UE 1 from Cell 1 to Cell 2 to trigger event 1A. Cell 2 is
Steps added into the active set.
3. Continue moving UE 1 to Cell 2 until event 1B is triggered
and Cell 1 is removed from the active set.
Expected Result UE1 performs the inter-RNC soft handover successfully.

Handover Control
Table 6-3 Feature Validation Procedure -DSCR
Test Item Mobility Management
1. WCDMA system ready.

2. Cell1 and Cell4 support HSUPA, HSDPA and DCH. Cell1 belongs
to RNC1/NodeB1. Cell4 belongs to RNC2/NodeB2.
3. Cell1 and Cell4 have the same frequency. Configures Cell1 and
Precondition
Cell4 as adjacent cells with different coverage.
s
4. Configures DSCR function for Iur interface.
6. UE1 subscribes interactive or background service, MBR=
UL2Mbps/ DL2Mbps.
1. UE1 activates a PS service in Cell1 and starts FTP downloading.

2. UE1 moves from Cell1 to Cell4 to trigger event 1A/1D. Cell4 is
added into the active set.
Test Steps
3. UE1 moves further into Cell4 until triggers event 1B and DSCR
from RNC1 to RNC2.
4. Deactivate the PDP.
Anticipative
1. UE1 performs the DSCR procedure successfully.
Result
Test Item Coverage based handover

2. Cell1 and Cell2 support HSUPA, HSDPA and DCH. Cell 1
belongs to RNC1/NodeB1. Cell 2 belongs to RNC1/NodeB2.
Prerequisite
3. Cell1 and Cell2 have the same frequency but different
coverage areas.

Handover Control
Test Item Coverage based handover

or PSTN in Cell1. Hold the call.
2. Move UE 1 from Cell1 to Cell2 to trigger event 1A. Cell 2 is
3. Continue moving UE 1 to Cell 2 until event 1B is triggered
Expected Result UE1 performs the soft handover successfully
Test Item Compressed Mode

2. Cell 1 and Cell 2 support HSUPA, HSDPA and DCH, and
belong to RNC1/NodeB1.
Prerequisite
3. Cell 1 and Cell 2 have different frequencies and coverage
areas.

2. Move UE1 from Cell 1 to Cell 2 to trigger event 2D and
Steps activate compressed mode.
3. Continue moving UE 1 to Cell 2 to trigger event 2A. Use UE 1
to perform a hard handover to Cell2.
UE1 activates compressed mode and performs the hard

Expected Result
handover successfully.
Test Item Neighboring Cells Priorities

Handover Control

belongs to RNC1/NodeB1. Cell 2 belongs to
RNC1/NodeB2.
3. Cell 1 and Cell 2 have the same frequency.
4. Cell 2 and Cells 3 through 22 are intra-frequency
Prerequisite
neighboring cells of Cell 1. The priority of Cells 3 through
12 is 0. The priority of Cells 13 through 22 and Cell 2 is 1.
5. Cells 23 through 42 are intra-frequency neighboring cells of
Cell 2. The priority of Cells 23 through 32 is 1. The priority
of Cells 33 through Cell 42 is 2.
1. Use UE 1 to make an AMR 12.2kbps voice call to another

UE or PSTN in Cell 1. Hold the call.
2. Move UE1 from Cell 1 to Cell 2 to trigger event 1A. Cell 2 is
added into the active set, and a new measurement control
Steps message of the intra-frequency cells for the active set will
be sent to UE 1.
3. Continue moving UE1 to Cell 2 until event 1B is triggered
1. In the measurement control message in step 2, the

combined neighboring cell list contains Cells 1 through 32.
Expected Result 2. In the measurement control message in step 3, the
combined neighboring cell list contains Cell 2, and Cells 23
through 42.
Test Item SRNS Relocation––UE not involved for CS domain

Handover Control
Test Item SRNS Relocation––UE not involved for CS domain

belongs to RNC1/NodeB1, and Cell 2 belongs to
RNC2/NodeB2.
3. Cell 1 and Cell 2 have the same frequency but different
Prerequisite
coverage areas.
4. The Iur interface between the two RNCs is available.
5. The duration of the delay timer of relocation for the RT service
is set to 0 second.

2. Move UE 1 from Cell 1 to Cell 2 to trigger event 1A. Cell2 is
3. Continue moving UE 1 to Cell 2 until event 1B and relocation
from RNC1 to RNC2 are triggered.
Expected Result UE 1 performs the relocation procedure successfully.
6.4 Feature Deactivation Procedure
None
6.4.2 ZWF21-03-002 Intra-Frequency Handover
None
Table 6-8 RNC Parameter List
No. Parameter Name Default Value Deactivation Value

Handover Control
No. Parameter Name Default Value Deactivation Value
0: Turn off Inter-frequency

Inter Frequency or Inter 3: Inter Frequency Is
1 and Inter-RAT Handover/2:
RAT Handover Switch Prior to Inter RAT
Only Inter RAT
For the description and configuration of the above parameter, refer to chapter 6.2.

Managed Object. logic Default Value Deactivation
GUI Name
name Value
AMR Inter Rat

ULogicalRnc.amrRatHoSw 0:Off 0:Off
Handover Switch
None.
Table 6-4 Feature Deactivation Procedure -DSCR
Managed Object. Default Value Deactivation

GUI Name
logic name Value
Whether Support 0: Not Support

UIurLink.RNCFEA 0: Not Support Hard
Hard Handover Hard Handover
TSWITCHBit4 Handover DSCR
DSCR DSCR
0: Not Use
0: Not Use DSCR
Whether Use DSCR DSCR for PS
for PS Service
UIurLink.RNCFEA for PS Service When Service When
When UE all RLs
TSWITCHBit7 UE all RLs Have UE all RLs Have
Have Moved to
Moved to DRNC Moved to
DRNC;
DRNC;

Handover Control
Switch of DSCR in
URncFunction.ds Transferring
crInCmnToDedS Unsuccessfully from 0: Off 0: Off
wch Common Status to
CELL_DCH status
None.
None.
None.
Default Deactivation
Managed Object. logic name GUI Name
Value Value
Whether 1: Support
Support UE UE not 0: Not Support UE
not Involved Involved not Involved
UIurLink.RncFeatSwitchBit10
Relocation Relocation Relocation for CS
for CS for CS service
Service service
For the description and configuration of the above parameter, refer to chapter 6.2.
6.5 Impact on the Network
The advantages of this feature:

Handover Control
1. Intra-frequency handover
An intra-frequency handover can guarantee communication continuity when UEs

are moving among intra-frequency neighboring cells.
Because soft and softer handovers are seamless handovers, services are not
interrupted during the handover procedure, and have higher success rates and
lower dropped-call rates.
Moreover, in the case of macro diversity, the receiving side may enhance the
accuracy of data reception by combining the signal reception of several links, and
the communication quality can be improved as well.
2. Inter-frequency handover
A UE is handed over to an inter-frequency neighboring cell with better quality when

moving between inter-frequency neighboring cells, which can guarantee
communication continuity and reduce the dropped-call rate.
3. Inter-RAT handover
A UE is handed over to an inter-RAT neighboring cell with better quality when

moving between systems, which can guarantee communication continuity and
reduce the dropped-call rate.
4. Periodic reporting measurement
The periodic reporting measurement can accelerate the triggering of an

inter-frequency or inter-RAT handover, and prevent calls from being dropped
because of handover execution not in time due to that the UE does not report the
event or reports the event with a long delay.
7 Abbreviation
Abbreviation Full Name
BLER Block Error Ratio
BSC Base Station Controller

Handover Control
CIO Cell Individual Offset
CN Core Network
CPICH Common Pilot Channel
CS Circuit Switched
DCH Dedicated Channel
DL Downlink (Forward Link)
DPCCH Dedicated Physical Control Channel
DPDCH Dedicated Physical Data Channel
DRBC Dynamic Radio Bearer Control
DRNC Drift Radio Network Controller
DSCR Directed Signaling Connection Re-establishment
DTM Dual Transfer Mode
Ec/No Received energy per chip divided by the power density in the band
E-DCH Enhanced Dedicated Channel
E-UTRA Evolved Universal Terrestrial Radio Access
FDD Frequency Division Duplex
GBR Guaranteed Bit Rate
GERAN GSM/EDGE Radio Access Network
GPRS General Packet Radio Service
GSM Global System for Mobile communication
HSDPA High Speed Downlink Packet Access
HS-DSCH High Speed Downlink Shared Channel
HSPA High Speed Packet Access
HSUPA High Speed Uplink Packet Access
LTE Long Term Evolution
NACC Network Assisted Cell Change
NRT Non-Real Time
P-CPICH Primary Common Pilot Channel
PS Packet Switched
QoS Quality of Service
RAB Radio Access Bearer
RL Radio Link

Handover Control
RNC Radio Network Controller
RNS Radio Network Subsystem
RRC Radio Resource Control
RSCP Received Signal Code Power
RSSI Received Signal Strength Indicator
RT Real Time
RTWP Received Total Wideband Power
SF Spreading Factor
SIR Signal to Interference Ratio
SRNC Serving Radio Network Controller
SRNS Serving RNS
TCP Transmitted Code Power
TDD Time Division Duplex
TFCS Transport Format Combination Set
TG Transmission Gap
TGD Transmission Gap start Distance
TGL Transmission Gap Length
TGSN Transmission Gap Starting Slot Number
TGPL Transmission Gap Pattern Length
TTI Transmission Time Interval
UE User Equipment
UL Uplink
UMTS Universal Mobile Telecommunications System
UTRA UMTS Terrestrial Radio Access
UTRAN UMTS Terrestrial radio access network
WCDMA Wideband CDMA, Code division multiple access
8 Reference Document
[1] ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Radio Parameter
Reference

Handover Control
[2] ZXWR RNC (V3.14.10.14) Radio Network Controller Radio Parameter Reference
[3] ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Performance Counter
Reference
[4] ZXWR RNC (V3.14.10.14) Radio Network Controller Performance Counter

Reference
[5] ZTE UMTS Neighboring Cell Monitoring Feature Guide
[6] ZTE UMTS Dynamic Radio Bearer Control Feature Guide
[7] ZTE UMTS Power Control Feature Guide
[8] ZTE UMTS Load Balance Feature Guide
[9] ZTE UMTS Quality Based Handover Feature Guide
[10] ZTE UMTS Transmitted Power Based Handover Feature Guide
[11] ZTE UMTS Hierarchical Cell Structures Feature Guide
[12] ZTE UMTS HSDPA Introduction Feature Guide
[13] ZTE UMTS HSUPA Introduction Feature Guide
[14] ZTE UMTS Service-Based Handover Feature Guide
[15] ZTE UMTS NACC Feature Guide
[16] ZTE UMTS PS Handover with GSM Feature Guide
[17] ZTE UMTS DTM Handover with GSM Feature Guide
[18] ZTE UMTS Intelligent Carrier Power off/on Feature Guide
[19] ZTE UMTS Handover with LTE Feature Guide

Handover Control

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Handover Control

Caricato da

Copyright:

Formati disponibili

Handover Control

Update the features introduced in version

ZTE Confidential Proprietary 1

Version Date Author Reviewer Notes

© 2015 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 2

3 Technical Description ..................................................................................... 21

ZTE Confidential Proprietary 3

3.4.7 Coupling Processing of Different Handovers ...................................................... 75

ZTE Confidential Proprietary 4

3.10.1 Introduction to Compressed Mode ................................................................... 126

5 Related Counters and Alarms ...................................................................... 253

6 Engineering Guide ........................................................................................ 271

ZTE Confidential Proprietary 5

6.2.10 ZWF21-03-020 SRNS Relocation .................................................................... 320

7 Abbreviation .................................................................................................. 333

8 Reference Document..................................................................................... 335

ZTE Confidential Proprietary 6

Figure 3-1 Parameter Indexing Principle of Intra-frequency Handover ...............................28

ZTE Confidential Proprietary 7

Figure 6-4 Parameter Configuration Interface-4 ...............................................................288

ZTE Confidential Proprietary 8

Figure 6-34 Parameter Configuration Interface-54 ...........................................................323

ZTE Confidential Proprietary 9

Table 6-7 Feature Validation Procedure...........................................................................329

ZTE Confidential Proprietary 10

Node B version: [ZXSDR V4.14.10]

2.1 Feature Introduction

2.1.1 ZWF21-03-001 Soft/Softer Handover

ZTE Confidential Proprietary 11

2.1.2 ZWF21-03-002 Intra-Frequency Hard Handover

ZTE Confidential Proprietary 12

2.1.3 ZWF21-03-003 Inter-Frequency Hard Handover

This feature supports the handover of UE in inter-frequency cells. It is applied to maintain

The inter-frequency hard handover means a UE in dedicated connecting state is handed

2.1.4 ZWF21-03-004 Inter-RAT Mobility

The inter-RAT handover, supported by ZTE RAN equipment, works as follows:

 Support inter-RAT handover of CS voice service from RAN to GSM

 Support inter-RAT handover of CS voice service from GSM to RAN

 Support cell change of PS data service from RAN to GSM

 Support re-access of PS data service from GSM to RAN

The inter-RAT handover in connected mode accompanies the inter-RAT relocation. In

ZTE Confidential Proprietary 13

2.1.5 ZWF21-03-006 Inter-RNC Handover with Iur Support

This feature supports maintaining communication continuity in the case of a UE in

2.1.6 ZWF21-03-008 Directed Signaling Connection Re-establishment

This feature supports maintaining communication continuity in the case of a UE in

ZTE Confidential Proprietary 14

2.1.7 ZWF21-03-009 Coverage Based Handover

When a UE moves or the coverage condition changes, it is necessary to pay more

 ZWF21-03-001 Soft/Softer Handover

 ZWF21-03-002 Intra-Frequency Hard Handover

ZTE Confidential Proprietary 15

intra-frequency hard handover according to the intra-frequency measurement result

 ZWF21-03-003 Inter-Frequency Hard Handover

 ZWF21-03-004 Inter-RAT Handover

2.1.8 ZWF21-03-010 Compressed Mode

For non-double-receiver WCDMA terminals, it is impossible to receive radio signals of

 Halving of Spreading Factor

ZTE Confidential Proprietary 16

inter-frequency/inter-RAT measurement and others for the data transmission. This

 Higher Layer Scheduling

2.1.9 ZWF21-03-011 Neighboring Cells Priorities

ZTE RAN equipment offers two types of cell priority policies.