ZTE UMTS Handover Control Feature Description PDF

Handover Control
WCDMA RAN
Feature Description
Handover Control Feature Description

Version
Date
Author
Approved By
V2.5
2009-1-20
Sha Xiubin /
ZhangBo
Liu Min
V3.0
2009-2-27
Sha Xiubin /
ZhangBo
Liu Min
Remarks
2008 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 of the document is
subjected to change without notice.
ZTE Confidential Proprietary
TABLE OF CONTENTS
1
Functional Attribute ................................................................................................... 1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.1.10
2.1.11
2.1.12
2.1.13
2.1.14
2.1.15
2.1.16
2.1.17
2.1.18
2.1.19
Overview ..................................................................................................................... 1
Function Introduction ................................................................................................... 1
Soft Handover and Softer Handover ........................................................................... 3
Intra-Frequency Hard Handover.................................................................................. 3
Inter-Frequency Hard Handover.................................................................................. 4
Inter-RAT Mobility ........................................................................................................ 5
Inter-RNC(with IUR) Handover.................................................................................... 6
Inter-RNC Handover Without lur Interface .................................................................. 6
Compressed Mode ...................................................................................................... 6
Adjacent Cell Priority ................................................................................................... 6
Change of HS-DSCH Serving Cell .............................................................................. 7
Change of Serving Cell in E-DCH Active Set .............................................................. 7
Handover Based on Dedicated Downlink Transmit Power ......................................... 7
Handover Based on Dedicated Uplink Transmit Power (UE)...................................... 7
QoS-based Handover .................................................................................................. 7
IMSI-based Handover.................................................................................................. 8
Associated Channel Soft/Softer Handover of HSDPA ................................................ 8
Associated Channel Soft/Softer Handover of HSUPA ................................................ 8
Different Active Sets of E-DCH and DCH.................................................................... 8
Handover Strategy Based on Service Type ................................................................ 8
SRNS Relocation......................................................................................................... 8
3
3.1
3.2
Compressed Mode Strategy...................................................................................... 9

Introduction to Compressed Mode .............................................................................. 9
Compressed Mode Strategy...................................................................................... 11
4
4.1
4.1.1
4.1.2
4.1.3
4.2
Intra-Frequency Handover Strategy ....................................................................... 13

Intra-Frequency Measurement .................................................................................. 13
Introduction to Intra-Frequency Measurement .......................................................... 13
Measurement Control Method Related to Active Set and Monitored set .................. 14
Handling of Over 32 Adjacent Cells........................................................................... 17
Handling Mechanism for Period-based Report of Intra-Frequency Handover
Measurement............................................................................................................. 19
Intra-Frequency Handover Decision.......................................................................... 19
Event 1A-Triggered Handover................................................................................... 19
Event 1B-Triggered Handover................................................................................... 20
Event 1C-Triggered Handover................................................................................... 21
Event 1D-Triggered Handover................................................................................... 21
Time-To-Trigger Mechanism Used to Control Event Report..................................... 22
Handling of Intra-Frequency Events .......................................................................... 23
Detected set Handover .............................................................................................. 23
Detected Set Tracing ................................................................................................. 24
Intra-Frequency Handover Procedure....................................................................... 26
Intra-RNC Soft Handover (Add a Radio Link) ........................................................... 26
Intra-RNC Soft Handover (Delete a Radio Link) ....................................................... 27
Intra-RNC Soft Handover (Swap a Radio Link)......................................................... 28
Intra-RNC Hard handover.......................................................................................... 29
Inter-RNC Hard Handover Through lur Interface ...................................................... 30
Inter-RNC Hard Handover Without lur Interface........................................................ 31
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
II
5
5.1
5.1.1
5.1.2
5.1.3
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
Inter-Frequency Handover Strategy ....................................................................... 31

Inter-Frequency Measurement .................................................................................. 32
Introduction to Inter-Frequency Measurement .......................................................... 33
Inter-Frequency Measurement Control Method ........................................................ 35
Handling of Over 32 Adjacent Cells........................................................................... 41
Handling Mechanism for Period-based Report of Inter-Frequency Handover
Measurement............................................................................................................. 42
Downlink Coverage Based Inter-Frequency Handover............................................. 42
Uplink BLER Based Inter-Frequency Handover........................................................ 43
Uplink Transmit Power Based Inter-Frequency Handover........................................ 43
Downlink Transmit Power Based Inter-Frequency Handover ................................... 43
Load Control Based Handover .................................................................................. 44
Moving Speed Based Handover................................................................................ 44
Coupling Handling of Different Handovers ................................................................ 45
Inter-Frequency Handover Procedure....................................................................... 46
6
6.1
6.2
SRNS Relocation ...................................................................................................... 46

Relocation Triggered by Soft Handover .................................................................... 48
Relocation Triggered by Hard Handover................................................................... 49
7
7.1
7.1.1
7.1.2
7.1.3
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.8.1
7.8.2
Inter-RAT Handover Policy...................................................................................... 50

Inter-RAT Measurement ............................................................................................ 51
Overview of Inter-RAT Measurement ........................................................................ 51
Control Methods for Inter-RAT Measurement ........................................................... 52
Processing in the Case of More Than 32 Inter-RAT Neighboring Cells.................... 56
Inter-RAT Handover Based on Downlink Coverage.................................................. 58
Inter-RAT Handover Based on Uplink BLER............................................................. 58
Inter-RAT Handover Based on Uplink Transmit Power............................................. 58
Inter-RAT Handover Based on Downlink Transmit Power ........................................ 59
Handover Based on Load Control ............................................................................. 59
with ShareCover (Overlap or Covers)with GsmShareCover (Overlap or Covers)with
GsmShareCover (Overlap or Covers)Coupling for Different Handover Causes....... 59
Inter-RAT Handover Process .................................................................................... 61
CS Service Handover from 3G System to 2G System .............................................. 61
PS Service Reselection in 3G to 2G Handover......................................................... 61
8
8.1
8.2
IMSI-based handover ............................................................................................... 62

Querying Whether a SRNC Cell Is Authorized According to IMSI ............................ 63
Querying Whether a DRNC Cell Is Authorized According to IMSI ............................ 64
9
9.1
9.2
9.3
9.4
HSDPA-related special strategy ............................................................................. 65

Overview .................................................................................................................... 65
Intra-frequency Handover.......................................................................................... 66
Inter-frequency Handover.......................................................................................... 67
Inter-RAT Handover................................................................................................... 68
10
10.1
10.2
10.3
10.4
HSUPA-related special strategy ............................................................................. 68

Overview .................................................................................................................... 68
Inter-RAT Handover................................................................................................... 71
11
11.1
11.2
MBMS-related special strategy............................................................................... 72

III
12
12.1
12.1.1
12.1.2
parameters and configurations .............................................................................. 73

Intra-Frequency Handover Parameters..................................................................... 73
Parameter List ........................................................................................................... 73
Parameter Configuration ........................................................................................... 75
This parameter indicates whether PCPICH transmission power is configured.................. 105

12.2
Inter-Frequency Handover Parameters................................................................... 105
12.2.1
Parameter List ......................................................................................................... 105
12.2.2
Parameter Configuration ......................................................................................... 107
This parameter indicates whether the HCS function is used................................................ 111
This parameter indicates whether PCPICH transmission power is configured.................. 143
12.3
SRNC Relocation Parameters................................................................................. 143
12.3.1
Parameter List ......................................................................................................... 143
12.3.2
12.4
Inter-RAT Handover Parameters............................................................................. 146
12.4.1
Parameter List ......................................................................................................... 146
12.4.2
This parameter indicates whether the HCS function is used................................................ 173
12.4.3
Parameter List ......................................................................................................... 173
12.4.4
12.5
HSDPA Handover Parameters ................................................................................ 185
12.5.1
Parameter List ......................................................................................................... 185
12.5.2
12.6
HSUPA Handover Parameters ................................................................................ 187
12.6.1
Parameter List ......................................................................................................... 187
12.6.2
12.7
MBMS Handover Parameters.................................................................................. 189
12.7.1
Parameter List ......................................................................................................... 189
12.7.2
13
13.1
13.1.1
13.1.2
13.1.3
13.1.4
13.1.5
13.1.6
13.1.7
13.1.8
13.1.9
13.1.10
13.1.11
13.1.12
13.1.13
13.2
Counter And Alarm ................................................................................................ 190

Counter List ............................................................................................................. 190
RNC Soft Handover Statistics ................................................................................. 190
RNC Hard Handover Statistics ................................................................................ 192
193
Relocation With UE Not Involed .............................................................................. 195
RNC Inter-RAT Handover Statistics ........................................................................ 197
Cell Soft Handover Statistics ................................................................................... 198
Cell Hard Handover Statistics.................................................................................. 200
Transfer between HSPA and DCH due to Cell Mobility .......................................... 202
Cell HSPA Handover to 2G Statistics...................................................................... 204
Cell Inter-RAT Handover Statistics.......................................................................... 204
Inter-cell Hard Handover Statistics .......................................................................... 206
Inter-cell Soft Handover Statistics ........................................................................... 208
Inter-RAT Cell Handover Statistics.......................................................................... 209
Alarm List ................................................................................................................. 210
14
Glossary .................................................................................................................. 210
IV
Figures and Tables

Figure 1
Transmission Gap (TG) position.................................................................................. 10
Figure 2
Parameters of compressed mode ............................................................................... 11
Figure 3
Procedure for E-DCH fallback to DCH prior to initiation of compressed mode........... 12
Figure 4
Intra-frequency handover index quotations ................................................................. 16
Figure 5
Cell priority configuration ............................................................................................. 18
Figure 6
Time-To-Trigger mechanism ....................................................................................... 22
Figure 7
Intra-frequency handover index quotations ................................................................. 24
Figure 8
Intra-RNC soft handover (Add a radio link) ................................................................. 26
Figure 9
Intra-RNC soft handover (Delete a radio link) ............................................................. 27
Figure 10
Intra-RNC soft handover (Swap a radio link)............................................................... 28
Figure 11
Intra-RNC hard handover procedure ........................................................................... 29
Figure 12
Inter-RNC hard handover through lur interface ........................................................... 30
Figure 13
Inter-RNC hard handover without lur interface............................................................ 31
Figure 14
Inter-frequency handover index quotations ................................................................. 40
Figure 15
Cell priority configuration ............................................................................................. 41
Figure 16
Example of slow-moving UE judging conditions.......................................................... 45
Figure 17
Example of fast-moving UE judging condition ............................................................. 45
Figure 18
SRNC relocation procedure (Span two CNs ) ............................................................. 47
Figure 19
Relocation triggered by soft handover......................................................................... 48
Figure 20
Relocation triggered by hard handover ....................................................................... 49
Figure 21
Indexing relation for Inter-RAT handover .................................................................... 56
Figure 22
Priority settings of cells ................................................................................................ 57
Figure 23
3G to 2G CS service handover.................................................................................... 61
Figure 24
PS service reselection initiated by an UE in the case of 3G to 2G handover ............. 62
Figure 25
PS service reselection initiated by the RNC in the case of 3G to 2G handover ......... 62
Figure 26
Schematic Diagram of Querying Whether a SRNC Cell Is Authorized According to

IMSI.............................................................................................................................. 64
Figure 27
Schematic Diagram of Querying Whether a DRNC Cell Is Authorized According to

IMSI.............................................................................................................................. 65
Table 1
Correspondence between handover and compressed modes...................................... 2
Table 2
Parameters of compressed mode ............................................................................... 11
Table 3
Table of Principle ......................................................................................................... 72
Table 4
Parameter Description ................................................................................................. 76
Table 5
Table 6
Default Value of the UE Intra-frequency Measurement Configuration Parameters

Related to Traffic Category.......................................................................................... 89
Table 7
Table 8
Service
Type
Related
UE
Inter-frequency
Measurement
Parameter
ConfigurationDefault Value........................................................................................ 128
Table 9
Parameter Description ............................................................................................... 129
Table 10
Service Type Related UE Inter-RAT Measurement Parameter ConfigurationDefault

Value.......................................................................................................................... 156
VI
Functional Attribute
System version: [RNC V3.07.300, Node B V4.00.100, OMMR V3.17.300, OMMB
V4.00.100]
Attribute: [Mandatory function]
Involved NEs:
UE
NodeB
RNC
MSCS
MGW
SGSN
GGSN
HLR
Note:
*-: Not involved.
*: Involved.
Dependent function: [None].
Mutually exclusive function: [None].
Remarks: [None].
Overview
2.1
Function Introduction
The cell handover strategy is required in WCDMA to implement the mobility
management of RRC connection due to the mobility of UE. It is also required to balance
traffic among cells to lower traffic in heavily-loaded cell. The service connection must not
be interrupted and QoS must be met during handover.
In the process of handover:
The handover in which a UE retains radio connection with the original cell while
establishing radio connection in a new cell is referred to as soft handover.
During soft handover, if the new and original cells are located under the same
NodeB, this type of handover is referred to as softer handover.
If UE needs to disconnect link with the original cell before setting up a link
(synchronization) with the new cell(that is, new and original links do not co-exist in
UE), this type of handover is referred to as hard handover.
A interruption will occur to UE transmitting and receiving at the time of hard handover.
Therefore, the hard handover may affect the QoS.
The handover may also be further classified into intra-frequency handover, interfrequency handover and Inter-RAT handover based on different cell frequency
features/access technologies before and after handover. A UE in a connection mode
can only receive the service data of single frequency, but the soft handover/softer
handover requires the UE to retain radio link with several cells concurrently, so
soft/softer handover must be intra-frequency handover. But the handover between cells
in the same frequency may not necessarily be soft/softer handover, and it may be hard
handover. The inter-frequency/Inter-RAT handover is hard handover without fail
because of the change of carrier frequency/frequency band. Generally a UE has only
one set of receiver/transmitter, so the compressed mode is necessary for interfrequency/Inter-RAT measurement. The following table lists the correspondence
between handover and compressed modes.
Table 1
Correspondence between handover and compressed modes
Softer
handover
Soft
handover
Hard
handover
Require compression
or not
Intra-frequency
Inter-frequency
Inter-RAT
The handover generally involves three steps: measurement, handover decision and
handover implementation. The measurement is the prerequisite for handover, the
handover decision is the core of handover and the handover implementation is the
process of implementing the handover decision. This document primarily centers on
these three steps to illustrate the algorithm, and contains the following contents.
.Soft Handover and Softer Handover
Intra-Frequency Hard Handover
Inter-Frequency Hard Handover
Inter-RAT Mobility
Inter-RNCwith IURHandover
Inter-RNC Handover Without lur Interface
Compressed Mode
Adjacent Cell Priority
Change of HS-DSCH Serving Cell
Change of Serving Cell in E-DCH Active Set:
Handover Based on Dedicated Downlink Transmit Power
Handover Based on Dedicated Uplink Transmit Power (UE)
2.1.1
QoS-based Handover
IMSI-based Handover
Associated Channel Soft/Softer Handover of HSDPA
Associated Channel Soft/Softer Handover of HSUPA
Different Active Sets of E-DCH and DCH
Handover Strategy Based on Service
SRNS Relocation
Soft Handover and Softer Handover

In a soft handover, a UE maintains several radio links with different NodeBs, while in a
softer handover, a UE concurrently maintains radio link with several cells in a NodeB,
and these several cells are also known as macro diversity.
The soft/softer handover can only occur in intra-frequency cells. Compared with the hard
handover, the soft/softer handover features are as follows:
The soft and softer handovers are seamless handovers and no service will be
interrupted during handover.
Macro diversity gain: When a UE maintains radio links with several cells, the
receiver may enhance the accuracy of data receiving and link receiving quality and
lower the transmit power of all links by combining the signal receiving results of
several links.
The best cell where UE is registered may establish a radio connection with the UE
in time so as to lower the transmit power of UE.
In view of the above features, the soft and softer handovers will be taken in intrafrequency handover in general.
2.1.2
Intra-Frequency Hard Handover

Hard handover is a typical handover mechanism in which a UE needs to disconnect the
link with the original cellbefore setting up a link (synchronization) with the new cell (that
is, new and original links do not co-exist in UE). The intra-frequency hard handover is
only adopted when soft/softer handover is unavailable. The scenarios where soft/softer
handover is unavailable (intra-frequency hard handover must be adopted) in the case of
intra-frequency handover include:
UE uses transmit diversity in active set cell in case of intra-frequency handover, but
the target cell does not support transmit diversity.
Intra-frequency measurement report excludes the OFF and TM of the target cell.
lur interface between RNCs is unavailable in the case of intra-frequency handover.
UE uses multi-user detection in the active set cell, but the target cell does not
support multi-user detection.
Types of target and source cells are differentdefine R99,R5+R99, R6+R5+R99

belong to the same cell type and R5,R6+R5 belong to another cell type, for
example, the UE hands over from a DCH-capable cell to an HSPA-capable cell.
2.1.3
Inter-Frequency Hard Handover

Inter-frequency hard handover means a UE in connecting state hands over from a cell
on a frequency of UTRAN to another cell on another frequency.
The factors triggering inter-frequency hard handover include radio quality, load, and
moving speed of UE.
Inter-frequency hard handover triggered by radio quality: Initiate inter-frequency
measurement when the quality of frequency where UE is currently located worsens, and
handover UE to the frequency with better quality based on inter-frequency measurement
results. The quality of the carrier frequency where the UE is currently located is
measured through the following four standards (For details, see Inter-Frequency
Handover Strategy):
PCPICH quality of cell in current serving carrier frequency.
Uplink Block Error Rate (BLER) of the Dedicated CHannel (DCH).
Uplink transmit power of DCH.
Downlink transmit power of DCH.
Inter-frequency hard handover triggered by cell load: When the load of cell on current
frequency is too heavy, the system switches partial services of this cell to an adjacent
cell on another frequency.
Inter-frequency hard handover triggered by moving speed of UE: It is mainly used on the
HCS network. UEs with quick moving speed are carried in macro cells and those with
slow moving speed in micro cells so as to realize appropriate traffic distribution in cells,
make full use of system resources and enhance system performance.
For non-double-receiver terminals in WCDMA, the compressed mode must be initiated
for inter-frequency measurement. The initiation of compressed mode has some impact
on the performance of both system and UE,.Therefore, compressed mode must be
initiated only when necessary (for example, when the quality of current serving carrier
frequency worsens).
2.1.4
Inter-RAT Mobility
Inter-RAT mobility refers to the mobility management conducted when a UE switches
from one UMTS to another one. Here it only applies to the mobility management for UE
to switch from UTRAN to GERAN (the mobility management from GERAN to UTRAN
belongs to the strategy of GERAN).
This function requires UE to support both WCDMA and GSM, Moreover, the GSM also
needs to offer related functions to support Inter-RAT handover. The functions required
by WCDMA are described below.
WCDMA-to-GSM handover supports the following services:
Conversational services
Videophone service fallback to ordinary voice service. (3GPP R6)
PS transferred to GPRS/GERAN
For WCDMA-to-GSM handover involving CS and PS RAB combination, the system first
switches CS service to GERAN first, and then RNC releases the PS on lu interface upon
receiving the context request message from CN.The UE activates the PS service on
GERAN upon the release of CS service.
In WCDMA:
UTRAN-to-GERAN mobility of CS service in connected mode is implemented

through CS service handover procedure
UTRAN-to-GERAN mobility of PS service in CELL_DCH state is implemented

through cell reselection procedure (PS service handover) triggered on the network
side
UTRAN-to-GERAN mobility of PS service in CELL_FACH /URA_PCH state is

implemented through cell reselection procedure triggered by UE
Load-based UTRAN-to-GERAN handover of PS service in CELL_FACH state is

implemented through cell reselection procedure triggered on the network side
Inter-system mobility in connected mode must be accompanied by inter-system

relocation
The factors triggering Inter-RAT handover include radio quality and cell load.
Inter-RAT handover triggered by radio quality: Initiate Inter-RAT measurement when
quality of the frequency where the UE is currently located worsens and inter-frequency
measurement initiation conditions cannot be met or the quality of other frequencys is
also poor, and then handovers UE to the cell of GERAN based on Inter-RAT
measurement results. The quality of frequency where UE is currently located is
measured through the following four standards (For details, see Inter-RAT Handover
Strategy):
PCPICH quality of cell in current serving carrier frequency.
Uplink Block Error Rate (BLER) of the Dedicated CHannel (DCH).
Uplink transmit power of DCH.
Downlink transmit power of DCH.
Inter-RAT handover triggered by cell load: When the load of cell in current UTRAN
system is too heavy, the system switches partial services of this cell to an adjacent cell
in GERAN.
for Inter-RAT measurement. Initiation of compressed mode has some impact on the
performance of both system and UE.Therefore, compressed mode must be initiated only
when necessary (for example, when the quality of current serving carrier frequency
worsens).
2.1.5
Inter-RNC(with IUR) Handover

This feature provides inter-RNC handover management in the presence of lur interface.
The inter-RNC(with iur) handover is basically identical with intra-RNC handover strategy
except that the handover may involve SRNC relocation. For hard handover(with iur), the
lur interface relocation must be involved; for soft handover(with iur), the SRNC
relocation is only triggered when there is no link on SRNC side.
2.1.6
Inter-RNC Handover Without lur Interface

This feature provides inter-RNC handover management in the absence of lur interface.
The inter-RNC handover without lur interface is implemented through inter-CN relocation.
2.1.7
Compressed Mode
for Inter-RAT/inter-frequency measurement. The use of compressed mode means some
timeslots are specially used for inter-frequency/Inter-RAT measurement instead of data
transmission during transmitting and receiving.
2.1.8
Adjacent Cell Priority

The system offers two types of cell priority policies as follows:
Firstly, adjacent cells can be configured based on their states (StateMode, and
GsmStateMode).Therefore, adjacent cell list used for reselection in non-dedicated mode
and that used for handover in dedicated mode can be separately configured. A UE in
non-dedicated mode only receives the adjacent cell information of one cell, while a UE
in dedicated mode receives the union of adjacent cell list of multiple cells in macro
diversity. But a UE can only receive a maximum of 32 intra-frequency adjacent cells,
inter-frequency adjacent cells and Inter-RAT adjacent cells respectively. Therefore,

more adjacent cells may be configured for UE in non-dedicated mode.
Secondly, adjacent cells are set with different priorities (MeasPrio (utranRelation/
gsmRelation)) in RNC to facilitate RNC to adjust adjacent cell list when the number of
adjacent cells in active set is over 32. The priority of each cell in the adjacent cell list is
determined based on the network planning and optimization progress. The priority helps
RNC select better monitored set for UE to facilitate the improvement of measurement
and handover performance of UE.
2.1.9
Change of HS-DSCH Serving Cell

The HS-PDSCH has only one serving cell. If the best cell changes (1D event triggering)
in the presence of HS-PDSCH, the change of HS-PDSCH serving cell is triggered during
intra-system soft handover. If there exists an HS-PDSCH before and after hard
handover, the HS-PDSCH serving cell must change.
2.1.10
Change of Serving Cell in E-DCH Active Set

The E-DCH has only one serving cell, so if the best cell changes (1D event triggering) in
the presence of E-DCH, the change of E-DCH serving cell is triggered during intrasystem soft handover. If there exists an E-DCH before and after hard handover, the EDCH serving cell must change.
2.1.11
Handover Based on Dedicated Downlink Transmit Power

This feature enables handover based on the dedicated downlink transmit power, and
applies to the following scenario: The signal of pilot frequency is acceptable, but the
dedicated downlink transmit power has become very high, requiring UE handover to an
inter-frequency or Inter-RAT adjacent cell.
2.1.12
Handover Based on Dedicated Uplink Transmit Power (UE)

This feature enables handover based on the dedicated uplink transmit power, and
applies to the following scenario: The signal of pilot frequency is acceptable, but the
dedicated uplink transmit power has become very high, requiring UE handover to an
inter-frequency or Inter-RAT adjacent cell to avoid large interference on other users.
2.1.13
QoS-based Handover
This feature enables the handover based on the uplink BLER and applies to the
following scenario: The signal of pilot frequency is acceptable, but the uplink of UE is
very unacceptable due to uplink interference or other reasons. In the event of failure of
outer loop power control, the UE needs to be handed off to an inter-frequency or InterRAT adjacent cell as quick as possible to avoid call drop.
2.1.14
IMSI-based Handover
Configure the scope of authorized cells based on the IMSI information on the network
side. The IMSI information is resolved through the CommonID on lu interface during
service setup or handover, and UE is not allowed to access or handover to unauthorized
cells.
2.1.15
Associated Channel Soft/Softer Handover of HSDPA

The HSDPA service supports soft/softer handover of associated DPDCH/DPCCH, with
the policy identical with that of common soft/softer handover.
2.1.16
Associated Channel Soft/Softer Handover of HSUPA

The HSUPA service supports soft/softer handover of associated DPDCH/DPCCH, with
the policy identical with that of common soft/softer handover.
2.1.17
Different Active Sets of E-DCH and DCH

The feature enables E-DCH and DCH to have different active sets. The maximum
number of links of E-DCH active set is MaxNumOfEdchAct, and that of DCH active set is
MaxNumOfAct.
2.1.18
Handover Strategy Based on Service Type

This feature determines whether and when service can be handed over to GSM based
on the service handover attribute in RAB assignment request message, and includes the
following values:
2.1.19
Handover to GSM should be performed: RAB must be handed over to GSM

immediately. If there is any GSM adjacent cell in the cell where the UE is located
and inter-frequency measurement is not activated upon service setup or handover
success, the Inter-RAT measurement must be activated immediately.
Handover to GSM should not be performed: RAB is handed over to GSM forcedly
when the UMTS is unable to carry it. RNC triggers Inter-RAT blind handover or
activates Inter-RAT measurement only when the quality of the UMTS is poor.
Handover to GSM shall not be performed: Service cannot be handed over to GSM.
For such a type of service, RNC neither activates the Inter-RAT measurement, nor
triggers the handover to GSM.
SRNS Relocation
If inter-RNC handover occurs and radio link does not exist in SRNC, or hard handover
occurs, the system determines the delay in performing SRNC relocation based on the
timer
configured in OMCR(set separately based on CS and PS services:
RtReDelayTimer, and NrtReDelayTimer). The DRNC changes its role into SRNC upon
relocation, and assigns new RNTI to the UE through the UTRAN MOBILITY
INFORMATION of radio interface. Therefore, the SRNS relocation can be categorized
into relocation involving no UE (soft handover triggered) and relocation involving UE
(hard handover triggered) based on UE relevance:
The relocation involving no UE equals to the relocation triggered by soft handover.
The interactive message (RELOCATION COMMIT) interacts through lur

interface between SRNC and DRNC. SRNC sends SN and GTP of PDCP to
DRNC through interactive message.
There is no message interaction between SRNC and UE.
Two types of messages (UTRAN Mobility Information/UTRAN Mobility

Information Confirm) interact between DRNC and UE. The DRNC sends the
PDCP SN received by the UE downlink.
The relocation involving UE equals to the relocation triggered by hard handover.
The messages related to hard handover interact between SRNC and UE.
The messages related to hard handover interact between DRNC and UE.
There is no message interaction between SRNC and DRNC through lur

interface.
When the CS and PS services coexist, the relocation is performed based on different
domains. If handover conditions of either domain are met, different handovers will be
performed in CS domain and PS domain respectly.
Compressed Mode Strategy
3.1
Introduction to Compressed Mode

for Inter-RAT/inter-frequency measurement. The use of compressed mode means some
timeslots are specially used for inter-frequency/Inter-RAT measurement instead of data
transmission during transmitting and receiving. There are the following two ways to
generate compressed mode frames:
1
Halving of Spreading Factor (SF)

By halving the SF, the bandwidth can be increased so that some timeslots in one
radio frame can be specially assigned for inter-frequency/Inter-RAT measurement
and some can be specially assigned for data transmission. This transmission
strategy is generally used in services which raise high requirements for delay and
assurance of minimum data rate, for example, CS- and S-type PS data services.
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 timeslots in a radio frame can be
specially assigned for inter-frequency/Inter-RAT measurement and some can be
specially assigned for data transmission while the 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.
After the compressed mode is initiated, the GAP used for transmitting/receiving
(measurement) can be placed either within one radio frame or between two radio frames,
as shown in Figure 1.
Transmission gap
#0
#Nfirst-1
Radio frame
#Nlast+1
#14
(1) Single-frame method
First radio frame
#0
Figure 1
Transmission gap
Second radio frame
#Nfirst-1
#Nlast+1
(2) Double-frame method
#14
Transmission Gap (TG) position
In the protocol, the Transmission Gap Length (TGL) can be set to 3, 4, 5, 7, 10 and 14
timeslots. The TG may start from any timeslot in a frame. When the TG spans two
consecutive frames, each frame at least has 8 non-compressed timeslots.
Figure 2 shows the parameters involved in compressed mode. The Transmission Gap
Pattern Sequence (TGPS) consists of consecutive TG patterns (TG pattern 1). One or
two TGs are defined in TG pattern. The start timeslot No. of the first TG is determined by
parameter TGSN. The number of timeslots between starting timeslots of two TGs in the
TG pattern is determined by the parameter TGD. The first TGL is determined by
parameter TGL1, and the second by parameter TGL2. If parameter TGD is not defined,
it means there is only one TG in TG pattern. Length of a TG pattern is determined by
parameter TGPL1.
10
#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
TGL1
TGL2
TGSN
TGD
TGPL1
Figure 2
3.2
Parameters of compressed mode
Compressed Mode Strategy

If the compressed mode is required when the UE capability message indicates the FDD
inter-frequency or Inter-RAT measurement, then the compressed mode is initiated upon
the initiation of inter-frequency or Inter-RAT measurement. The compressed mode must
be disabled in either of the following scenarios: 1) Delete inter-frequency measurement
while keeping Inter-RAT measurement disabled. 2) Delete Inter-RAT measurement
while keeping inter-frequency measurement disabled.
As is described in the above section, the strategy of halving of SF does not affect the
realtime rate of services, while that of higher layer scheduling reduces the realtime rate
of services. For RT services, only the first strategy can be adopted to ensure delay and
transmission rate; for NRT services, both the first and second strategies can be adopted
because of their low requirements for delay and rate. For NRT services on ZTE network,
the first strategy is adopted for uplink and the second for downlink.
The above rules only apply to DCH/DCH. For HS-DSCH or E-DCH, only the higher layer
schedule is supported, as stipulated in the protocol.
The compressed mode of all services on ZTE network adopts identical parameters as
listed below:
Table 2
Parameters of compressed mode
GSM adjacent cell measurement
FDD adjacent cell measurement
TGSN
4 (Slots)
3 (Slots)
TGL1
7 (Slots)
7 (Slots)
11
TGD
Not configured
Not configured
TGPL1
8 (Frames)
8 (Frames)
It can be seen from above parameters: When TGSN is 4 (GSM) or 3 (FDD), TGL1=7, all
GAPs of compressed mode on ZTE network fall under the same radio frame (one radio
frame in FDD has 15 slots), that is, the single frame mode is uniformly adopted.
Note: For a great majority of commercial terminals (Qualcomm-chip terminals) in current
market, the compressed mode cannot be initiated when services are carried on EDCH.Moreover, the capability of whether UE should supports Initiate compressed mode
for services carried on E-DCH is not specified in 3GPP. Therefore, when services are
carried on E-DCH and compressed mode needs to be initiated, RNC first configure EDCH to DCH (the reconfigured target rate is min( max(DRBC lowest of rate grades,
GBR), MaxBR)) (For DRBC rate grades, see ZTE UMTS DRBC Algorithm Feature
Description) before initiating the compressed mode. Figure 3 shows the procedure in
which E-DCH falls back to DCH before the initiation of compressed mode.
Figure 3
Procedure for E-DCH fallback to DCH prior to initiation of compressed mode
(In 300i version, whether E-DCH falls back to DCH before initiation of compressed mode
is controlled through the parameter HsupaCmAssoMode. If the parameter value is Serial,
E-DCH needs to fall back to DCH before the initiation of compressed mode.If the
parameter value is Parallel, the compressed mode is initiated directly. Detailed
strategies and control parameters are provided in 300i version).
For all commercial terminals in current market, the compressed mode can be initiated
directly when services are carried on HS-DSCH.
12
Intra-Frequency Handover Strategy

Intra-frequency handover refers to the handover performed between cells under the
same frequency of UTRAN. The intra-frequency handover can be triggered based on
Ec/N0 or RSCP measurement through the parameter IntraMeasQuan.Intra-frequency
handover is measurement-based handover. Intra-frequency measurement contains
active set measurement, monitored set measurement and detected set measurement.
The active set refers to the collection of cells retaining radio connection with UE.
The monitored set refers to the collection of cells retaining no radio connection with UE
but requiring measurement by sending the intra-frequency measurement control
message to UE.
The detected set refers to the collection of intra-frequency cells except cells in the active
set and monitored set.
4.1
Intra-Frequency Measurement
When conducting intra-frequency measurement, the UE needs to implement layer 3 filter
for the measurement results to avoid measurement fluctuation and then make event
decision and report by using filtered values. The layer 3 filter formula is as follows:
Fn = (1 a) Fn 1 + a M n
Where,
Fn-1 refers to the result of last filter.
Fn refers to the result of current measurement filter.
Mn refers to current measurement result.
a = 1/2(k/2) refers to the filter coefficient calculated based on the filter factor K (FilterCoeff
(Intra)).
4.1.1
Introduction to Intra-Frequency Measurement

Intra-frequency measurement refers to measurement performed for intra-frequency cells.
It can adopt either period-based report or event-based report strategy, which is
determined through the parameter SoftHoMth.
The period-based report means the UE periodically reports the quality

measurement result of intra-frequency cell PCPICH to the RNC and the RNC then
judges whether intra-frequency events are met based on the measurement result. If
so, it outputs intra-frequency events (including such information as event ID, and
target cell).
The event-based report means the UE judges whether intra-frequency events are
met based on the quality measurement result of cell PCPICH.If so, it reports intra-
13
frequency events (including such information as event ID, and target cell) to the
RNC.
A series of intra-frequency measurement events are defined in 3GPP as the judgment
and trigger criteria for intra-frequency handover.
Event 1A: A Primary CPICH enters the Reporting Range. It can be used for adding cell
to the active set.
Event 1B: A Primary CPICH leaves the Reporting Range. It can be used for deleting cell
from the active set.
Event 1C: A Non-active Primary CPICH becomes better than an active Primary CPICH.
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 soft/softer handover, intra-frequency
hard handover and inter-frequency load balance.
4.1.2
Measurement Control Method Related to Active Set and Monitored

set
4.1.2.1
Measurement Setup
Configure intra-frequency measurement parameters for UE and initiate intra-frequency
measurement through measurement control setup message in the following cases:
RRC connection is set up and enters CELL_DCH state.
CELL_FACH -> CELL_DCH.
Relocation to current RNC from other systems or RNCs.
Set up intra-frequency measurement again after intra-system hard handover (including

intra- or inter-frequency hard handover).
4.1.2.2
Measurement Modification
If the intra-frequency measurement is enabled, the intra-frequency measurement
modification is triggered in the following cases:
The change of adjacent cell list may trigger the modification of intra-frequency
measurement so as to modify adjacent cell parameters after soft handover.
After the best cell changes (Event 1D), the change of intra-frequency measurement
parameters will trigger the modification of intra-frequency measurement to update
handover parameters.
14
4.1.2.3
If a service is added or deleted, the change of intra-frequency measurement

parameters will trigger the modification of intra-frequency measurement to update
handover parameters.
Measurement Deletion
Upon receiving exceptional intra-frequency measurement report (for example, the
measurement report belongs to non-existent measurement task), or making decision
about the relocation triggered by soft handover, the RNC will voluntarily release
corresponding intra-frequency measurement.
4.1.2.4
Parameter Configuration Strategies
Intra-frequency event parameter configuration:

There are 7 intra-frequency measurement events (1A, 1B, 1C, 1D, 1E, 1F and 1J)
in total. The specific number of events configured is based on the parameter
MeasEvtNum (Intra), and the specific intra-frequency events configured are based
on the parameter MeaEvtId (Intra). MeaEvtId is defined through array, and the
dimensions of array equal to MeasEvtNum, which is 7 at most.
Handover parameter combination in macro diversity:

All measurement parameters are cell-based. In macro diversity, the measurement
parameters configured in the best cell will be used as handover parameters. If the
best cell changes, the measurement parameters need to be updated at the same
time.
Configuration of several sets of handover parameters:

The intra-frequency handover parameters can be separately configured based on
measurement quantity, measurement report mode and service bearer type. In this
way, several sets of measurement parameters are necessitated for different
purposes: The specific categories are as follows:
Measurement quantity.
IntraMeasQuan
(PCPICH Ec/N0 or RSCP)
Measurement report mode
(Period- or event-based report)
SoftHoMth
Service bearer type
(TrfCategory(CIntra))
Single RT RAB Including Voice on DL DCH/UL DCH
Single RT RAB Excluding Voice on DL DCH/UL DCH
Single NRT on DL DCH/UL DCH
15
Single RAB on DL HS-DSCH/UL DCH
Single RAB on DL HS-DSCH/UL E-DCH
All Multi-RAB on DL DCH/UL DCH
Multi-RAB, HSPA is Involved and only DCHs are Used in UL
Multi-RAB, HSPA is Involved and E-DCH is Used in UL
Not Related to Service Type (Used for detected set measurement)
To facilitate parameter modification and optimization, the intra-frequency parameters are

index-organized, with the index quotations listed as follows:
Figure 4
Intra-frequency handover index quotations
Before obtaining intra-frequency handover parameters, first find the Service TypeRelated Intra-frequency Measurement Parameter Index (TrfCatIntraMIdx), UTRAN
Intra-frequency Radio Quality Measurement Quantity (IntraMeasQuan), and Soft
Handover Algorithm Selection (SoftHoMth) from Utran Cell (utranCell) configuration
items; then find the Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)
from the UE Intra-frequence Measurement Relative to Traffic Category Configuration
Information (CIntra) configuration items based on TrfCatIntraMIdx, "Traffic Category
(TrfCategory)", Measurement Purpose (PrdMeasEcNo, EvtMeasEcNo, PrdMeasEcNo,
and PrdMeasRSCP); finally, find corresponding handover measurement parameters
from UE Intra-frequency Measurement Configuration (Intra) configuration items based
on the Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo).
Note: Each IntraMeasCfgNo corresponds to one measurement purpose, indicated with
the parameter IntraMeasCfgNote.
The correspondence between other parameters that need to be filled in intrafrequency measurement control message and OMCR configuration is described as
follows:
Measurement report transmission mode
(MeasRptTrMod)
CPICH Ec/No report indication of intra-frequency

measurement cell
(EcN0RptInd)
CPICH RSCP report indication of intra-frequency

measurement cell
(RscpRptInd)
Path loss report indication of intra-frequency measurement
(RscpRptInd)
16
cell
Whether to read SFN indication of target cell
(ReadSFNInd)
Forbidden Cell Indicator for Event 1A/1B
(FbdCellInd)
(MeasQuantity(Intra)
)
(RptCrt(Intra))
Note: The parameters MeasQuantity(Intra) and RptCrt(Intra) are automatically filled by

the system based on IntraMeasCfgNote.
For cells of neighbor RNC if the value of Primary CPICH Power Configuration
Tag(PcpichPwrPre(externalUtranCell))is TURE,then the cell info of intra-freq
measurement should include the Primary CPICH Power for this cell. Otherwise the cell
info of intra-freq measurement shall not include the Primary CPICH Power for this cell.
4.1.3
Handling of Over 32 Adjacent Cells

When there are many cells in an active set, the number of intra-frequency adjacent cells
in the active set may exceed 32, the maximum number of adjacent cells as stipulated in
the protocol. In that case, some intra-frequency adjacent cells must be deleted to ensure
there are only 32 adjacent cells in the active set. Having minimal impact on users in the
active set, these dropped cells are those with poorest signal quality or remotest
geographical location. Therefore, each intra-frequency adjacent cell is configured with a
priority level.
4.1.3.1
Cell Priority Configuration

The OMCR configuration parameter MeasPrio(utranRelation) is used to define the
priority of adjacent cells and includes three values (0: High priority; 1: Medium priority; 2:
Low priority). The specific value of MeasPrio(utranRelation) must be set by the network
planning engineer based on existing network situation (for example, adjacent cell quality
and geographical location of adjacent cell). Figure 5 shows the cell priority configuration
based on the geographical location of adjacent cells. Take the configuration of cells
adjacent to the innermost gray cell as an example: there are three layers of adjacent
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).
17
Figure 5
4.1.3.2
Cell priority configuration
Strategy for adjacent cells exceeding 32

As stipulated in the protocol, the maximum number of adjacent cells is 32 (including
source cell). When the UE is in the macro diversity state, the total number of intrafrequency adjacent cells in the macro diversity may be in excess of 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, then combine the priority levels of this cell and taking the highest
priority as the priority of the cell.
Sorting strategy
If the total number of adjacent cells in the active set is 32, the system prioritizes them in
descending order of priority and places the cells in excess of 32 in adjacent cell reserve
list.
The priority levels of adjacent cells in intra-frequency adjacent cell list will be updated
whenever Event 1A/1B/1C/1D is triggered. If Event 1B is triggered and the number of
adjacent cells is less than 32, the system selects cells from reserve list in descending
order of priority and places them in the intra-frequency adjacent cell list. The number of
cells that can be selected: min (32 Number of existing cells in intra-frequency adjacent
cell list, Number of cells in reserve list).
18
4.2
Handling Mechanism for Period-based Report of

Intra-Frequency Handover Measurement
The period-based report means the UE periodically reports the intra-frequency
measurement result based on the periodical report interval (PrdRptInterval (R7Intra) and
the amount of periodical reports (PrdRptAmount (R7Intra)) configured by RNC. The RNC
judges intra-frequency handover events in accordance with the intra-frequency event
rule defined in protocol by referring to the cell quality periodically reported by UE. If
several decision conditions are concurrently met, the RNC will handle events in the
sequence of 1D, 1A, 1C and 1B.
Long interval set in the period-based report mode may result in call drop due to
handover delay. Therefore, it is recommended to set the interval to a small value. But
setting a short interval will increase the signaling load of radio interface and easily lead
to signaling congestion, so the event-based report is generally preferred.
4.3
Intra-Frequency Handover Decision
4.3.1
Event 1A-Triggered Handover

Event 1A means the quality of certain cell outside the active set ameliorates. Upon
receiving Event 1A, the RNC adds 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 + CIO New W 10 Log M i + (1 W) 10 LogM Best (R 1a H1a /2)
i=1
The meanings of all parameters are described as follows:

R1a: Refers to the reporting range of Event 1A. It is used to control the extent of difficulty
in adding a cell into the active set (RptRange [MAX_INTRA_MEAS_EVENT]).
H1a: Refers to the reporting hysteresis of Event 1A. It is used to control the extent of
difficulty in adding a cell into the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]
(Intra)).
MNew: Refers to measurement of the to-be-evaluated cell outside the active set.
CIONew: Refers to offset of cell outside active set in relation to other cells (CellIndivOffset
(utranRelation)).
Mi: Refers to the mean measurement value of other cells except the best cell in active
set.
NA: Refers to the number of other cells except the best cell in active set.
MBest: Refers to the measurement of the best cell in the active set.
19
W: Refers to the weight proportion (W[MAX_INTRA_MEAS_EVENT]) of the best cell to

the rest cells in the active set in evaluation standards.
As can be calculated from the above formula, you can increase the probability of
triggering Event 1A by either increasing R1a (Event 1A meets the reporting range
conditions) or decreasing H1a (Decision hysteresis range.Otherwise, you can reduce the
probability of triggering Event 1A.
Event 1A supports period-based report, that is, once Event 1A meets the reporting
range of quality standards, the UE will report Event 1A periodically
(EvtRptInterval[MAX_INTRA_MEAS_EVENT]) until this event does not meet reporting
conditions or the reporting times reach the maximum allowed times
(EvtRptAmount[MAX_INTRA_MEAS_EVENT]).
There is 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 certain threshold
(RptDeactThr[MAX_INTRA_MEAS_EVENT]).
4.3.2
Event 1B-Triggered Handover

Event 1B indicates the quality deterioration of certain cell in the active set. Upon
receiving the Event 1B, the RNC may delete the cell from the active set. When the cell
meets the conditions in the following formula, the UE reports Event 1B to the RNC.
NA
10 LogM Old + CIO Old W 10 Log M i + (1 W) 10 LogM Best (R 1b + H1b /2)
i=1
R1b: Refers to the reporting range of Event 1B. It is used to control the extent of difficulty
in dropping a cell from the active set (RptRange [MAX_INTRA_MEAS_EVENT]).
H1b Refers to the reporting hysteresis of Event 1B. It is used to control the extent of
difficulty in dropping a cell from the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]
(Intra)).
MOld: Refers to measurement of the to-be-evaluated cell in the active set.
CIOOld: Refers to offset of cell in active set in relation to other cells (CellIndivOffset
(utranCell)).
Mi: Refers to the mean measurement value of other cells except the best cell in active
set.
NA: Refers to the number of other cells except the best cell in active set.
MBest: Refers to the measurement of the best cell in the active set.
W: Refers to the weight proportion (W[MAX_INTRA_MEAS_EVENT]) of the best cell to
the rest cells in the active set in evaluation standards.
As can be calculated from the above formula, you can decrease the probability of
triggering Event 1B by either increasing R1b (Event 1B meets the reporting range
conditions) or decreasing H1b (Decision hysteresis range). Otherwise, you can increase
the probability of triggering Event 1B.
20
4.3.3
Event 1C-Triggered Handover

Event 1C indicates the quality of a cell in non-active set is better than that of a cell in
certain active set. Upon receiving Event 1C, the RNC may replace the cell in the active
set with a cell in non-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 + CIO New 10 LogM InAS + CIO InAS + H1c /2

H1c Refers to the reporting hysteresis of Event 1C. It is used to control the extent of
difficulty in replacing a cell in the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]
(Intra)).
MNew: Refers to measurement of the to-be-evaluated cell outside the active set.
MInAS: Refers to the cell with poorest quality in the active set.
CIONew: Refers to offset of the to-be-evaluated cell outside the active set in relation to
other cells (CellIndivOffset (utranRelation)).
CIOInAS: Refers to offset of cell with poorest quality in active set in relation to other cells
(CellIndivOffset (utranCell)).
triggering Event 1C by increasing H1c (decision hysteresis range); otherwise, you can
increase the probability of triggering Event 1C.
Event 1C supports period-based report, that is, once Event 1C meets the reporting
range of quality standards, the UE will report Event 1C periodically
(EvtRptInterval[MAX_INTRA_MEAS_EVENT]) until this event does not meet reporting
conditions or the reporting times reach the maximum allowed times
To ensure the gain of macro diversity, the report of Event 1C is only allowed when the
number
of
cells
in
the
active
set
reaches
certain
threshold
4.3.4
Event 1D-Triggered Handover

Event 1D indicates the quality of certain cell within or outside current active set is better
than the best cell in current active set, that is, the best cell changes in the active set. The
following can be triggered upon the receipt of Event 1D:
Add a cell 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).
Replace the cell with bad quality in active set (the cell outside the active set reports
Event 1D but the number of links in the active set reaches the maximum).
The serving cell changes (for HS-DSCH/E-DCH).
21
When the cell meets the conditions in the following formula, the UE reports Event 1D to
the RNC.
10 LogM NotBest + CIO NotBest 10 LogM Best + CIO Best + H1d /2

MNotBest: Refers to the measurement of the to-be-evaluated cell within or outside the
active set.
CIONotBest: Refers to the offset of the to-be-evaluated cell within the active set
(CellIndivOffset (utranCell)) or outside the active set (CellIndivOffset (utranRelation)) in
relation to other cells.
CIOBest: Refers to offset of the to-be-evaluated cell in the active set in relation to other
cells (CellIndivOffset (utranCell)).
MBest: Refers to the measurement of the to-be-evaluated cell in the active set.
H1d: Refers to Event 1D report hysteresis (Hysteresis[MAX_INTRA_MEAS_EVENT]
(Intra)).
triggering Event 1D by increasing H1d (decision hysteresis range); otherwise, you can
increase the probability of triggering Event 1D.
4.3.5
Time-To-Trigger Mechanism Used to Control Event Report

If a to-be-evaluated cell meets the reporting range or threshold of certain event, the
condition must be met within a period of time (TrigTime[MAX_INTRA_MEAS_EVENT]
(Intra)) before the reporting of this event to avoid intra-frequency event misreport due to
the fluctuation of radio quality. Take Event 1A as an example, suppose a cell meets the
reporting range, the UE only reports Event 1A only if the cell quality meets this reporting
range condition within TrigTime[MAX_INTRA_MEAS_EVENT] (Intra), as shown in
Figure 6.
Measurement
quantity
P CPICH 1
RptRange
[MAX_INTRA_
MEAS_EVENT]
P CPICH 2
P CPICH 3
TrigTime[MAX_INTRA_MEAS_EVENT]
Reporting
event 1A
Figure 6
Time
Time-To-Trigger mechanism
22
4.3.6
Handling of Intra-Frequency Events

Handling of Event 1A
Add links to the active set if the number of links in the DCH active set is less than
MaxNumOfAct. Do not handle Event 1A if the total number of links in the active set
reaches the maximum.
If a link to be added to the active set is rejected in Event 1A, the handover
punishment timer (5s) is initiated so that the Event 1A reported by this rejected cell
will not be handled until the timer times up.
If the cell reporting Event 1A is the target cell traced by the detected set, no link will
be added to the active set. For details, see Detected set Tracing.
If the measurement report contains several target cells, the cell with best quality
(Ec/N0) will be selected as the target cell to be added in the active set.
Handling of Event 1B
Delete the link of related cell based on Event 1B reported by UE.
If the measurement report contains several target cells, the cell with worst quality
(Ec/N0) will be selected as the target cell to be deleted from the active set.
Handling of Event 1C
Replace the cell if the radio links in active set are equal MaxNumOfAct .
If a link to be added to the active set is rejected in Event 1C, the handover
punishment timer is initiated so that the Event 1C reported by this rejected cell will
not be handled until the timer times up.
Handling of Event 1D
4.3.7
The cell triggering Event 1D is an intra-frequency adjacent cell outside the active
set. If the DCH active set is full, turn to Event 1C handling. If the DCH active set is
not full, turn to Event 1A handling.
If the cell triggering Event 1D is within the active set, change the best cell in the
active set.
Detected set Handover

The detected set handover is controlled through the parameter DetSetHoSwch. If the
detected set handover is enabled, and the number of adjacent cells are exceeding 32 ,
the RNC needs to instruct the UE to report the measurement report of detected set in
the measurement control. If the target cell in the detected set event reported by UE is a
cell in the adjacent cell reserve list as described in 4.1.3.2 Cell Dropping Strategy for
23
Over 32 Adjacent Cells, then the RNC handles the cell in the detected set in the same
way as it does in the monitored set, that is, to make decision about handover.
4.3.7.1
Related Measurement Procedure of Detected set Handover

(1) If the detected set handover (DetSetHoSwch) of the best cell is enabled and there
are over 32 adjacent cells, the detected set measurement will be initiated. Initiation
strategy: Change 1A Triggering condition 2 into Detected set cells and monitored set
cells, and Reporting cell status into Report all active set cells + cells within monitored
set and/or detected set on used frequency. That is, perform measurement report of
active set, monitored set and detected set concurrently by sharing the same set of
handover measurement parameters.
(2) If the detected set handover (DetSetHoSwch) of the best cell is disabled and there
are less 32 adjacent cells, then change 1A Triggering condition into Monitored set
cells and Reporting cell status into Report cells within active set and/or monitored set
cells on used frequency. That is, to only report the monitored set instead of detected set.
4.3.7.2
Related Parameter Configurations

The RNC only performs handover for the detected set measurement reported by the
adjacent cells exceeding 32. The handling 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.
4.3.8
Detected Set Tracing

The detected set tracing is used in network planning and optimization to judge whether
there is any adjacent cell 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
OMCR (take parameters under the measurement configuration No. in relation to Not
Related to Service Type), with parameter index as follows:
Figure 7
Intra-frequency handover index quotations
Before obtaining intra-frequency handover parameters, first find the Service TypeRelated Intra-frequency Measurement Parameter Index (TrfCatIntraMIdx), UTRAN
Intra-frequency Radio Quality Measurement Quantity (IntraMeasQuan), and Soft
Handover Algorithm Selection (SoftHoMth) from Utran Cell (utranCell) configuration
items; then find the Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)
from the UE Intra-frequency Measurement Relative to Traffic Category Configuration
24
Information (CIntra) configuration items based on TrfCatIntraMIdx, "Traffic Category

(TrfCategory)", Measurement Purpose (EvtMeasDctEcNo, and EvtMeasDctRSCP);
finally, find corresponding handover measurement parameters from UE Intra-frequency
Measurement Configuration (Intra) configuration items based on the Intra-Frequency
Measurement Configuration No. (IntraMeasCfgNo).
Note: Each IntraMeasCfgNo corresponds to one measurement purpose, indicated with
the parameter IntraMeasCfgNote.
4.3.8.1
Measurement Procedure of Detected Set Tracing

(1)The measurement of detected set tracing is controlled through the detected set
tracing task in the performance measurement of OMCR. The detected set measurement
is started after the detected set tracing task is created and initiated. When configuring
the measurement control, set Triggering condition 2 to Detected set cells, and
Reporting cell status to Report cells within detected set on used frequency.
(2)The measurement parameters of detected set are indexed to the cell, and the
parameters of the best cell will be chosen in macro diversity state. If the parameters of
the best cell are different from those used by the UE, the measurement information
needs to be modified through the measurement control message.
(3)After the detected set tracing task stops, disable detected set tracing and release
related measurement task.
25
4.4
Intra-Frequency Handover Procedure
4.4.1
Intra-RNC Soft Handover (Add a Radio Link)

UE
Node B
Drift RNS
Drift
RNC
Serving
RNC
Decision to setup
new RL
RNSAP
NBAP
2. Radio Link Setup

Request
1. Radio Li nk Setup
Request
RNSAP
NBAP
Start RX
description
NBAP
3. Radio Link Setup

Response
NBAP
4. Radio Link Setup
Response
RNSAP
5. ALCAP Iub Bearer Setup
NBAP
6. Radio Link Restore

Indication
RN SAP
ALCAP Iur Bearer Setup
NBAP
RNSAP
7. Radio Link Restore

Indication
RNSAP
8. Downlink Synchronisation
DCH -FP
DCH -FP
DCH - FP
9. Uplink Synchronisation
DCH - FP
Start TX
description
10. DCCH : Active Set Update
RRC
RRC
[Radio Link Addition]
11. DCCH : Active Set Update Complete
RRC
Figure 8
RRC
Intra-RNC soft handover (Add a radio link)
26
4.4.2
Intra-RNC Soft Handover (Delete a Radio Link)

UE
N ode B
D rift R N S
D rift
RNC
S erv ing
RNC
D ecisio n to d elete
o ld R L
1 . D C C H : A ctiv e S et U p d ate
RRC
RRC
[R a d io L in k D eletio n ]
2 . D C C H : A ctive S et U p d ate C o m p lete
RRC
RRC
RN SAP
NBAP
4 . R ad io L ink D eletio n
R eq u est
3 . R ad io L in k D eletio n
R eq uest
RN SAP
NBAP
S to p R X an d T X
NBAP
5 . R ad io L ink D eletio n
R esp o nse
NBAP
RN SAP
7 . A L C A P Iub B earer R elease
Figure 9
6 . R ad io L in k D eletio n
R esp o nse
RN SAP
A L C A P Iur B earer R elease
Intra-RNC soft handover (Delete a radio link)
27
4.4.3
Intra-RNC Soft Handover (Swap a Radio Link)

UE
Node B
D rift R N S
N ode B
S erv in g R N S
D rift
RNC
S erv ing
RNC
D ec isio n to se tup
ne w R L an d
rele ase o ld R L
RNSAP
NBAP
2 . R ad io L ink S e tup R eq ue st
1 . R ad io L in k S e tup
R e q u est
RN SAP
NBAP
S tart R X
NBAP
3 . R a d io L in k S etu p R e sp o n se
NBAP
RNSAP
5 . A L C A P Iub D a ta T ra nsp o rt B ea re r S etu p

NBAP
6 . R a d io L ink R e sto re Ind ic atio n
4 . R a d io L ink S etu p
R e sp o n se
A L C A P Iur B e arer S etu p

NBAP
RN SA P
7 . R a d io L in k R esto re
Ind ica tio n
8 . D o w n lin k S ync h ro nisa tio n
D C H -F P
RNSAP
D C H -F P
9 . U p link S yn ch ro n isatio n
D C H -F P
RNSAP
D C H -F P
S ta rt T X
1 0 . D C C H : A ctiv e S et U p d a te C o m m a nd
RRC
RRC
[R a d io L in k A d d itio n & D e letio n ]
RRC
1 1 . D C C H : A ctive S e t U p d a te C o m p le te
RRC
1 2 . R a d io L in k D e letio n R e q ue st
NBAP
NBAP
S to p R X an d T X
1 3 . R ad io L ink R elea se R e sp o nse
NBAP
NBAP
1 4 . A L C A P Iub D ata T ran sp o rt B e arer R ele ase
Figure 10 Intra-RNC soft handover (Swap a radio link)
28
4.4.4
Intra-RNC Hard handover
Figure 11 Intra-RNC hard handover procedure
29
4.4.5
Inter-RNC Hard Handover Through lur Interface

UE
Node B
Source
Node B
Target
RNC
Source
RNC
target
SRNC
1. Radio Link
Setup Reque st
RNSAP
2. Radi o Link Setup Reque st
NBAP
NBAP
3. Radio Link Setup Response
NBAP
RNSAP
NBAP
4. ALCAP Iub Data Transport Bearer Set up

5. RL Se tup
Re sponse
RNSAP
RNSAP
6. ALCAP Iur Dat a

Transport Bearer Setup
7. DCCH : Physical Channel Re configuration
RRC
RRC
NBAP
8. Radio Link Failure Indication
NBAP
RNSAP
NBAP
9. Radio Link Failure Indic ation
10. Radio Link Re store Indication
RNSAP
NBAP
RNSAP
11. RL Restore
Indication
RNSAP
12. DCCH : Physical Channel Reconfiguration Complete

RRC
RRC
RNSAP
NBAP
NBAP
14. Radio Link Deletion Re quest
15. Radio Link Deletion Response
13. Radio Link De le tion Request
RNSAP
17. Radio Link Deletion Response
RNSAP
NBAP
NBAP
16. ALCAP Iub D ata Transport Bearer Release
RNSAP
18. ALCAP Iur Dat a

Transport Bearer Release
Figure 12 Inter-RNC hard handover through lur interface
If the cells belong to different RNCs are adjacent and lur interface is available, the
SRNC performs cross-lur hard handoff. The SRNC relocation is triggered after hard
handover.
30
4.4.6
Inter-RNC Hard Handover Without lur Interface

N ode B
S o u rce
UE
N ode B
T a rg e t
RNC
S o u rc e
RANAP
RNC
T a rg e t
S G S N /M S C
M S C /S G S N
1 . R elo c a tio n R e q uire d
RANAP
2 . R e lo c a tio n R e q u ired
RANAP
RANAP
RANAP
3 . R e lo c atio n R eq u e st
RANAP
4 . R elo c a tio n R e q u est
RANAP
RANAP
5 . A L C A P Iu D ata
T ra nsp o rt B e a re r S e tu p
NBAP
NBAP
6 . R a d io L in k S e tu p R e q u e st
NBAP
7 . R a d io L in k S e tu p R e sp o n se
NBAP
8 . A L C A P Iu b D a ta T ra n sp o rt B e a re r S e tup
9 . R e lo c a tio n R e q u e st
A c k n o w le d g e
RANAP
RANAP
1 0 . R elo c a tio n R e q ue st
A c k n o w le d g e
RANAP
1 1 . R e lo c a tio n C o m m a n d
RANAP
1 2 . R e lo c atio n C o m m a n d
RANAP
RRC
1 3 . D C C H : P h ysica l C h a nn e l R ec o n fig ura tio n N o te 1
NBAP
RANAP
RRC
1 4 . R a d io L in k R e sto re In d ic a tio n
NBAP
1 5 . R elo c a tio n
D ete c t
RANAP
RANAP
1 6 . R elo c a tio n D e te ct
NBAP
RRC
1 7 . R a d io L in k F ailu re Ind ic a tio n
RANAP
RANAP
RANAP
RANAP
NBAP
1 8 . D C C H : P h ysic al C h a n ne l R e co n fig u ra tio n C o m p lete N o te 1
RRC
RANAP
1 9 . R elo c a tio n
C o m p le te
RANAP
2 1 . Iu R e le a se C o m m a n d
RANAP
RANAP
RANAP
2 0 . R e lo c a tio n C o m p le te
2 2 . Iu R e le a se C o m m an d
RANAP
RANAP
RANAP
2 3 . A L C A P Iu D ata T ra nsp o rt B e a re r
R e le a se
2 4 . Iu R e le a se C o m p lete
RANAP
RANAP
2 5 . Iu R ele a se C o m p lete
RANAP
RANAP
Figure 13 Inter-RNC hard handover without lur interface
If inter-frequency cells between RNCs are adjacent and lur interface is unavailable, the
hard-handover-triggered SRNS relocation is performed. The procedure is as follows:
The SRNC sets up radio link at DRNC through the lu interface relocation, and then
reconfig UE to the cell of DRNC through relocation. Upon receiving the reconfigureation
response message from the UE, the DRNC informs the CN to complete relocation and
changes into SRNC. The CN then releases the resources of UE at the original SRNC
through lu interface release command.
Inter-Frequency Handover Strategy

The inter-frequency handover is a feature in which the UE hands over from one
frequency of UTRAN to another one. It can either be handover based on inter-frequency
31
measurement, or blind handover based on ShareCover(Overlap or Covers). The

measurement-based handover cannot trigger the blind handover based on shared
coverage. The blind handover between cells with shared coverage can only be triggered
by such functions as load control and load balance.
The prerequisite for measurement-based inter-frequency handover is that UE performs
quality measurement of non-used frequency. For inter-frequency measurement in
CELL_DCH state, UE needs to initiate compressed mode unless it has double-receiver.
The compressed mode has a great impact on both the resource utilization (for example,
downlink power and uplink interference) and UE (for example, the transmit power and
battery consumption), so inter-frequency measurement is only initiated when the radio
quality of current serving carrier is poor, which can be evaluated through four
measurement quantities: Uplink BLER, UE uplink transmit power, transmit power of
downlink and inter-frequency measurement (quality measurement performed by UE for
PCPICH). Upon receiving the inter-frequency measurement results from UE, the RNC
makes a decision about inter-frequency handover, and hands over UE to the target
frequency and cell carried in the measurement results.
The blind handover based on ShareCover(Overlap or Covers) is controlled through the
coverage indication (ShareCover) in the adjacent cell configuration relation. If the radio
quality of a cell is good, then that of another cell with ShareCover(Overlap or Covers)
relation with this cell must also be good, that is, to forecast the radio quality of another
cell with ShareCover(Overlap or Covers) relation with a cell based on the radio quality of
this cell. Whether ShareCover(Overlap or Covers) relation exists among cells is
determined by the network planner based on cell coverage (Only cells with completely
the same coverage can be called cells with shared coverage, and inter-frequency cells
with shared coverage generally share a site and antenna feeder. If a cell completely
contains the coverage of another cell, the relation between them is called Covers). The
blind handover based on ShareCover(Overlap or Covers) is primarily used in load
control, load balancing and handover based on moving speed.
5.1
In the load balancing mechanism, if the load of the target cell for access or
handover is too heavy, you can access or handover the service into another less
loaded cell that has ShareCover(Overlap or Covers) relation with the target cell.
In the load control mechanism, if the load of current cell is too heavy, you can
forcedly handover partial services into another less loaded cell that has
ShareCover(Overlap or Covers) relation with the target cell.
In the handover based on moving speed, when the UE changes from low to high
moving speed, you can directly handover the UE from micro cell into a macro cell
that contains this micro cell.
Inter-Frequency Measurement
When conducting inter-frequency measurement, the UE needs to implement layer 3 filter
for the measurement results to avoid measurement fluctuation and then make event
decision and report by using filtered values. The layer 3 filter factor is FilterCoeff (Inter).
For inter-frequency measurement formula, see Intra-frequency Measurement.
Carrier evaluation standards for inter-frequency measurement:
32
NA j
Q frequencyj = 10 LogM frequency j = W j 10 Log Mi j + (1 W j ) 10 LogM Best j
i =1
Where,
Qfrequency j: Refers to (Virtual) active set quality of carrier j, that is, the measurement
result of carrier j (dB for Ec/No; dBm for RSCP).
Mfrequency j: Refers to the physical measurement value (ratio for Ec/No; mW for RSCP) of
the (Virtual) active set of carrier j.
Mi j: Refers to the physical measurement value of cell i of carrier j.
NA j: Refers to the number of cells (excluding best cell) in the (Virtual) active set of
carrier j.
MBest j: Refers to the measurement result of the best cell in the (Virtual) active set of
carrier j.
Wj:
Refers
to
the
weight
(WNoUsed[MAX_INTER_MEAS_EVENT]
or
Wused[MAX_INTER_MEAS_EVENT]) of the best cell in the (Virtual) active set of carrier j
during carrier measurement.
5.1.1
Introduction to Inter-Frequency Measurement

The inter-frequency measurement contains radio quality measurement of both working
carrier frequency and non-working carrier frequency. It can be performed based on
either Ec/N0 or RSCP measurement quantity, which is based on the parameter
NonIntraMeasQuan. The inter-frequency measurement can adopt either period-based
report or event-based report strategy, which is based on the parameter InterHoMth.
The period-based report means the UE periodically reports the quality measurement
result of inter-frequency cell PCPICH to the RNC and the RNC then judges whether
inter-frequency events are met based on the measurement result. If so, it outputs interfrequency events (including such information as event ID, and target cell).
The event-based report means the UE judges whether inter-frequency events are met
based on the quality measurement result of non-working carrier frequency PCPICH. If
so, it reports inter-frequency events (including such information as event ID, and target
cell) to the RNC.
A series of inter-frequency measurement events are defined in 3GPP as the judgment
and trigger criteria for inter-frequency handover.
The inter-frequency handover events are described as follows:
Event 2A: The best carrier frequency changes.
Q NotBest Q Best + H 2a /2
Where,
QNotBest: Refers to the measurement result of current non-best carrier frequency.
33
QBest : Refers to the measurement result of current best carrier frequency.

:
Refers
to
handover
decision
hysteresis
H2a
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2A.
parameter
Event 2B: The quality of working carrier frequency is lower than a threshold and that of
non-working carrier frequency is higher than a threshold.
QNon used TNon used 2b + H2b /2 Q Used TUsed 2b H 2b /2

Where,
QNon used: Refers to the measurement result of current non-working carrier frequency.
Refers
to
the
absolute
threshold
TNon
used
2b:
(ThreshNoUsedFreq[MAX_INTER_MEAS_EVENT]) of good quality of non-working
carrier frequency in Event 2B decision.
:
Refers
to
handover
decision
hysteresis
H2b
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2B.
parameter
QUsed: Refers to the measurement result of current working carrier frequency.

Refers
to
the
absolute
threshold
TUsed
2b:
(ThreshUsedFreq[MAX_INTER_MEAS_EVENT]) of poor quality of working carrier
frequency in Event 2B decision.
Event 2C: The quality of non-working carrier frequency is higher than a threshold.
Q Non used TNon used 2c + H 2c /2

Where,
Refers
to
the
absolute
threshold
TNon
used
2c:
carrier frequency in Event 2C decision.
Refers
to
handover
decision
hysteresis
H2c:
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2C.
parameter
Event 2D: The quality of working carrier frequency is lower than a threshold.
Q Used TUsed 2d H 2d /2
Where,
Refers
to
the
absolute
threshold
TUsed
2d:
frequency in Event 2D decision.
34
H2d:
Refers
to
handover
decision
hysteresis
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2D.
parameter
Event 2E: The quality of non-working carrier frequency is lower than a threshold.
Q Non used TNon used 2e H2e /2

Where,
Refers
to
the
absolute
threshold
TNon
used
2e:
carrier frequency in Event 2E decision.
Refers
to
handover
decision
H2e:
(Hysteresis[MAX_INTER_MEAS_EVENT] ) of Event 2E.
hysteresis
parameter
Event 2F: The quality of working carrier frequency is higher than a threshold.
QUsed TUsed 2f + H2f /2

Where,
Refers
to
the
absolute
threshold
TUsed
2f:
frequency in Event 2F decision.
Refers
to
handover
decision
hysteresis
H2f:
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2F.
parameter
If a carrier frequency meets the reporting range or threshold of certain event, the
condition must be met within a period of time (TrigTime(Iner)) before the reporting of this
event to avoid inter-frequency event misreport due to the fluctuation of radio quality.
5.1.2
Inter-Frequency Measurement Control Method

Among all inter-frequency measurement events, Event 2D and Event 2F only involve
measurement of working carrier frequencies, so the compressed mode is not required
during measurement and extra overhead will not be brought about to both UE and RNC.
The compressed mode can be enabled and disabled based on the definition of 2D/2F. If
there is any inter-frequency/Inter-RAT adjacent cell that has no ShareCover(Overlap or
Covers) relation with current cell during service setup, the RNC will configure Event 2D,
Event 2F and intra-frequency events to the UE. The following measurement setup,
modification and deletion apply to other inter-frequency measurement events except
Event 2D and Event 2F.
35
5.1.2.1
Measurement Setup
The inter-frequency measurement is only set up only when Inter-RAT measurement is
not initiated, and it can be triggered in either of the following scenarios:
(1)The radio quality of current serving carrier frequency deteriorates and there is interfrequency adjacent cell that has no ShareCover(Overlap or Covers) relation (judged
through ShareCover) with current serving cell.
(2)The UE meets the slow moving condition and there exists micro cell with higher HCS
level in the coverage of current cell (based on moving speed).
The Radio Quality Deterioration of Current Serving Carrier Frequency can be judged
through any of the following four indexes:
5.1.2.2
Uplink BLER: The uplink BLER value exceeds certain threshold (1.25%) and
meantime the Sirtarget value (realtime measurement result) reaches the maximum
configuration Sir (ULMaxSIR) in OMCR. The BLER is measured and judged by the
RNC.
Uplink transmit power of UE: The transmit power of UE exceeds certain threshold
(100%, in relation to the maximum transmit power of UE). The uplink transmit power
is measured by the UE and reported to the RNC through internal measurement
report 6A/6B.
Downlink transmit power: The downlink transmit power exceeds certain threshold
(90%, in relation to MaxDlDpchPwr of services). The downlink transmit power is
measured by NodeB and reported to the RNC through dedicated NodeB
measurement report.
The UE reports Event 2D.
Measurement Modification
If the inter-frequency measurement is enabled, the inter-frequency measurement
modification is triggered in the following cases:
5.1.2.3
If inter-frequency measurement parameters and adjacent cells change after soft

handover, the changed parameters and adjacent cells must be updated through
measurement modification.
If handover parameters change when a service is added or deleted, the changed

parameters must be updated through measurement modification.
Measurement Deletion
When inter-frequency measurement setup conditions are no longer met, the interfrequency measurement will be deleted (released).
36
Release inter-frequency measurement if there is no inter-frequency adjacent cell in

active set after handover and inter-frequency measurement is initiated.
Release inter-frequency measurement if there exists inter-frequency adjacent cell

but it has a ShareCover(Overlap or Covers) relation with a cell or an intra-frequency
adjacent cell in current active set, and inter-frequency measurement is initiated.
Release inter-frequency measurement if it is initiated but the radio quality of working

carrier frequency changes better. The standards for judging The Radio Quality of
Working Carrier Frequency Changes Better are described as follows:
The UE does not report Event 2D or reports Event 2F, the uplink BLER does not
exceed poor quality threshold (1.25%) or the BLER recovers below normal quality
threshold (CS64K: 0.1%; other services: 1%), the UE transmit power does not
exceed inter-frequency measurement initiation threshold (100%) or recovers below
normal value (90%), and the downlink transmit power does not exceed interfrequency measurement initiation threshold (90%) or recovers below normal value
(80%).
5.1.2.4
Release inter-frequency measurement after inter-frequency handover.
Release inter-frequency measurement in the case of exceptions, for example,

receiving exceptional inter-frequency measurement report (for example, the
measurement report belongs to non-existent measurement task on the network
side).
Handling of Inter-Frequency Events

(1)Handling of Event 2A/2B/2C:
If the measurement report contains several target cells, preferentially select those
with good quality (RSCP) as target cells. If there is any inter-frequency adjacent cell
that has ShareCover(Overlap or Covers) relation with the target cell, perform interfrequency load balancing based on the cellss load . (For details, see ZTE UMTS
Load Balance Feature Description).
For CS users, perform inter-frequency hard handover.
For PS users, 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.So
the following strategies are required:
If current channel type is DCH and the channel assigned for target cell is also
DCH after handover, first make a handover attempt according to current rate. If
handover fails, then makes another handover attempt according to the GBR of
current service or minimum rate grade of DRBC (for details, see ZTE UMTS
DRBC Algorithm Feature Description), to improve the handover success rate.
If current channel type is HS-DSCH/E-DCH or HS-DSCH/DCH, and DCH after

handover, perform handover directly according to the GBR of current service or
37
minimum rate grade of DRBC (for details, see ZTE UMTS DRBC Algorithm
Feature Description).
If the channel type is DCH before handover and HS-DSCH/E-DCH or HSDSCH/DCH after, then access by HS-DSCH/E-DCH or HS-DSCH/DCH (for
details, see ZTE UMTS DRBC Algorithm Feature Description); if HS-DSCH/EDCH or HS-DSCH/DCH admission fails, the handover can also be
implemented according to the minimum rate (GBR of service or minimum rate
grade of DRBC) of DCH.
The same cell can only use one of Event 2A, Event 2B and Event 2C to trigger
inter-frequency handover. Which of the three events will be used is based on the
inter-frequency handover recommendation strategy parameter InterHoTactic.
(2)Handling of Event 2D
Attempt blind handover if there exists ShareCover(Overlap or Covers) relationship

in the inter-frequency adjacent cells.
Initiate compressed mode and issue inter-frequency measurement 2A/2B/2C/2E if

there exists no ShareCover(Overlap or Covers) relation in inter-frequency adjacent
cells or blind handover fails. For initiation decision of compressed mode, see
Compressed Mode Enabling/Disabling.
(3)Handling of Event 2E
All non-working carrier frequencies report Event 2E, indicating that radio quality of
all inter-frequency adjacent cells is poor and 3G system quality deteriorates. If there
is any Inter-RAT adjacent cell that has ShareCover(Overlap or Covers) relation with
current serving cell, and the value of RAB assignment requestservice handover
is Handover to GSM should not be performed (For values of service handover,
see 2.1.7 Handover Strategy Based on Service Attribute), implement Inter-RAT
blind handover.
All non-working carrier frequencies report Event 2E, indicating that radio quality of
all inter-frequency adjacent cells is poor and 3G system quality deteriorates. If the
value of RAB assignment requestservice handover is Handover to GSM should
not be performed (For values of service handover, see 2.1.7 Handover Strategy
Based on Service Attribute), current serving cell has Inter-RAT adjacent cells
without GsmShareCover(Overlap or Covers) or Inter-RAT blind handover fails,
issue the Inter-RAT measurement Event 3A/3C.
(4)Handling of Event 2F
The compressed mode and inter-frequency measurement disabling can be

triggered. For details, see Compressed Mode Enabling/Disabling and InterFrequency Measurement Control Method Measurement Deletion.
38
5.1.2.5
Parameter Configuration Strategies
Inter-frequency event parameter configuration:

There are 6 inter-frequency measurement events (2a, 2B, 2C, 2D, 2E, and 2F) in
total. The specific number of events configured is based on the parameter
MeasEvtNum (Inter), and the specific inter-frequency events configured are based
on
the
parameter
MeaEvtId[MAX_INTER_MEAS_EVENT]
(Inter).
MeaEvtId[MAX_INTER_MEAS_EVENT] is defined through array, and the
dimensions of array equal to MeasEvtNum, which is 6 at most.
Handover parameter combination in macro diversity:

All measurement parameters are cell-based. In macro diversity, the measurement
parameters configured in the best cell will be used as handover parameters. If the
best cell changes, the measurement parameters need to be updated at the same
time.
Configuration of several sets of handover parameters:

The inter-frequency handover parameters can be separately configured based on
measurement quantity, measurement report mode and service bearer type. In this
way, several sets of measurement parameters are necessary for different purposes:
The specific categories are as follows:
NonIntraMeasQuan
( PCPICH RSCP or Ec/N0)
(Event report or periodically report)
InterHoMth
Service bearer type
(TrfCategory (CInter))
Not Related to Service Type (Used for detected set measurement)
39
To facilitate parameter modification and optimization, the inter-frequency

parameters are index-organized, with the index quotations listed as follows:
TrfCategory:
Not Related to Service Type
TrfCatInterMIdx
Utran Cell (utranCell)
NonIntraMeasQuan
InterHoMth
UE Inter-frequence Measurement
Relative to Traffic Category (CInter)
InterMeasCfgNo
UE Inter-frequence Measurement
Configuration (Inter)
Figure 14 Inter-frequency handover index quotations
Before obtaining inter-frequency handover parameters, first find the Service TypeRelated Inter-frequency Measurement Parameter Index (TrfCatIntraMIdx), UTRAN
Inter-frequency Radio Quality Measurement Quantity (NonIntraMeasQuan), and Interfrequency Handover Algorithm Selection (InterHoMth) from Utran Cell (utranCell)
configuration items; then find the Inter-Frequency Measurement Configuration No.
(InterMeasCfgNo) from the UE Inter-frequency Measurement Relative to Traffic
Category Configuration Information (CInter) configuration items based on
TrfCatInterMIdx, "Traffic Category (TrfCategory)", Measurement Purpose (PrdMeasEcNo,
EvtMeasEcNo, PrdMeasEcNo, and EvtMeasRSCP); finally, find corresponding
handover measurement parameters from UE Inter-frequency Measurement
Configuration (Inter) configuration items based on the Inter-Frequency Measurement
Configuration No. (InterMeasCfgNo).
Note: Each InterMeasCfgNo corresponds to one measurement purpose, indicated with
the parameter InterMeasCfgNote.
The correspondence between other parameters that need to be filled in interfrequency measurement control message and OMCR configuration is described as
follows:
(MeasRptTrMod)
Whether to report UTRA Carrier RSSI
(UTRACarrierRSSI)
Whether to report carrier frequency quality evaluation

value
(FreqQualEst)
Cell synchronization information report indication of

inter-frequency measurement
(CellSynRptInd)
Cell identity report indication of inter-frequency

measurement
(CIdRptInd)
Ec/No report indication of inter-frequency

measurement cell
(EcN0RptInd)
CPICH RSCP report indication of inter-frequency

measurement cell
(RscpRptInd)
Path loss report indication of inter-frequency

measurement cell
(RscpRptInd)
Whether to read SFN indication of target cell
(ReadSFNInd)
40
Inter-Frequency measurement amount
(MeasQuantity(Inter))
Inter-frequency measurement report mode
(RptCrt(Inter))
Note: The parameters MeasQuantity(Inter) and RptCrt(Inter) are automatically filled by

the system based on InterMeasCfgNote.
For cells of neighbor RNC if the value of Primary CPICH Power Configuration
Tag(PcpichPwrPre(externalUtranCell))is TURE then the cell info of inter-freq
measurement should include the Primary CPICH Power for this cell, otherwise the cell
info of inter-freq measurement shall not include the Primary CPICH Power for this cell.
5.1.3
Handling of Over 32 Adjacent Cells

When there are many cells in an active set, the number of inter-frequency adjacent cells
in the active set may exceed 32, the maximum number of adjacent cells as stipulated in
the protocol. In that case, some inter-frequency adjacent cells must be dropped to
ensure there are only 32 adjacent cells in the active set. Having minimal impact on users
in the active set, these dropped cells are those with poorest signal quality or remotest
geographical location. Therefore, each inter-frequency adjacent cell is configured with a
priority level.
5.1.3.1
Cell priority configuration

The OMCR configuration parameter MeasPrio(utranRelation) is used to define the
priority of adjacent cells and includes three values (0: High priority; 1: Medium priority; 2:
Low priority). The specific value of MeasPrio(utranRelation) must be set by the network
planning engineer based on existing network situation (for example, adjacent cell quality
and geographical location of adjacent cell). Figure 15 shows the cell priority
configuration based on the geographical location of adjacent cells. Take the
configuration of cells adjacent to the innermost gray cell as an example: there are three
layers of adjacent 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).
Figure 15 Cell priority configuration
41
5.1.3.2
Strategy for adjacent cells exceeding 32

As specified in the protocol, the maximum number of inter-frequency adjacent cells is 32.
When the UE is in the macro diversity state, the total number of inter-frequency adjacent
cells in the macro diversity may be in excess of 32, so some strategies are required to
control the number within 32, including:
Priority combination strategy
If a cell is adjacent to several inter-frequency cells in the active set, that is, the priority
levels configured for this cell may vary, then combine the priority levels of this cell, and
the highest priority level prevails.
Sorting strategy
If the total number of inter-frequency adjacent cells in the active set is 32, the system
prioritizes them in descending order of priority and places the cells in excess of 32 in
inter-frequency adjacent cell reserve list.
The priority levels of adjacent cells in inter-frequency adjacent cell list will be updated
whenever Event 1A/1B/1C/1D is triggered. If Event 1B is triggered and the number of
inter-frequency adjacent cells is less than 32, the system selects cells from reserve list
in descending order of priority and places them in the inter-frequency adjacent cell list.
The number of cells that can be selected: min (32 Number of existing cells in interfrequency adjacent cell list, Number of cells in reserve list).
5.2
Handling Mechanism for Period-based Report of

Inter-Frequency Handover Measurement
The period-based report means the UE periodically reports the inter-frequency
measurement result based on the periodical report interval (PrdRptInterval (R7Inter))
and the amount of periodical reports (PrdRptAmount (R7Inter)) configured by RNC. The
RNC judges inter-frequency handover events in accordance with the inter-frequency
event rule defined in protocol by referring to the inter-frequency cell quality periodically
reported by UE.
Long interval set in the period-based report mode may result in call drop due to
handover delay. Therefore, it is recommended to set the interval to a small value. But
setting a short interval will increase the signaling load of radio interface and easily lead
to signaling congestion, so the event-based report is generally preferred.
5.3
Downlink Coverage Based Inter-Frequency

Handover
Downlink coverage adopts Events 2D and 2F as a criterion to evaluate the quality of
current working carrier frequency signals. For details on handling strategies of Events
2D and 2F, see Handling of Inter-Frequency Events.
A coupling relationship exists among the coverage based handover, uplink BLER based
handover, uplink transmit power based handover, downlink transmit power based
42
handover, and moving speed based handover. For details on enabling/disabling of

compressed mode and inter-frequency measurement setup/release, see InterFrequency Handover Strategy--> Coupling Handling of Different Handovers.
5.4
Uplink BLER Based Inter-Frequency Handover

The activation of uplink BLER based inter-frequency handover is controlled through the
parameter UlBlerHoSwch.
This strategy only applies to the DCH.
When the value of UlBlerHoSwch is ON, the RNC periodically collects the statistics of
uplink BLER. If the uplink BLER value exceeds certain threshold (1.25%) and meantime
the Sirtarget value (realtime measurement result) reaches the maximum configuration
(ULMaxSIR) in OMCR, then the outer loop power control is already invalid and the
uplink quality gets worse. In such a case, handover the UE into its inter-frequency
adjacent cell that has ShareCover(Overlap or Covers)relation with current cell, or initiate
the inter-frequency measurement. The specific handling strategy is same to that of
Event 2D. For details, see Event 2D handling in Handling of Inter-Frequency Events.
5.5
Uplink Transmit Power Based Inter-Frequency

Handover
The activation of uplink transmit power based inter-frequency handover is controlled
through the parameter UlPwrHoSwch.
When the value of UlPwrHoSwch is ON, the RNC sets up the internal measurement
events 6A (Uplink power of UE exceeds the absolute threshold 100% of maximum
transmit power of UE) and 6B (Uplink power of UE is less than the absolute threshold
90% of maximum transmit power of UE) of UE while service initially establishing. When
the transmit power of UE meets the above threshold requirements, the UE will report the
corresponding events. After receiving an Event 6A report or an Event 6B report, the
RNC adopts the same handling strategy as that of 2D or 2F, respectively. For details,
see the Events 2D and 2F handling strategies in Handling of Inter-Frequency Events.
5.6
Downlink Transmit Power Based Inter-Frequency

Handover
The activation of downlink transmit power based inter-frequency handover is controlled
through the parameter DlPwrHoSwch.
NodeB periodically sends the dedicated measurement report of downlink transmit power
to the RNC.
43
When the value of DlPwrHoSwch is ON, the RNC judges the downlink code power
(DTCP) mentioned in the dedicated measurement report sent by NodeB. When the
DTCP value reaches certain threshold (90% of the maximum downlink transmit power
MaxDlDpchPwr), it indicates that the downlink power is very high. In such a case,
handover the UE to its inter-frequency adjacent cell that has ShareCover(Overlap or
Covers) relation with current cell, or initiate the inter-frequency measurement. The
specific handling strategy is same to that of Event 2D. For details, see Event 2D
handling in Handling of Inter-Frequency Events
5.7
Load Control Based Handover

When the load (downlink carrier power (TCP) or total uplink receive wideband power
(RTWP)) of a cell reaches a high level, if the cell has some less-loaded inter-frequency
adjacent cells that have ShareCover(Overlap or Covers) relation with this cell (judge
through ShareCover), the RNC will handover some UEs with low priority from this cell
into its adjacent cells, so as to reduce this cells load and ensure system stability.
For details on load handover, see ZTE UMTS Overload Control Feature Description.
5.8
Moving Speed Based Handover

In the Hierarchical Cell Structure (HCS), Macro cells are used to carry the fast-moving
UEs and they have low HCS priority (HcsPrio). Micro cells are used to carry the slowmoving UEs and they have high HCS priority (HcsPrio).
The moving speed based handover is to handover the fast-moving and slow-moving
UEs into Macro and Micro cells, respectively. The handover between Macro and Micro
cells requires an algorithm for judging the moving speeds of UEs. As long as there is
one HCS cell (UseOfHCS (utrancell) is TRUE) in active set, the moving speed
measurement needs to be activated.
The number of best cell changes per unit time is taken as a criterion for judging the
moving speed of UE. The more times the best cell changes per unit time, the faster the
moving speed. The number of best cell changes is based on the number of Event 1D
reports. The following parameters are used during the activation of moving speed judge:
Tslowjudge: Refers to the timing length of the timer set for judging slow-moving UEs.
NFast: Refers to the number of best cell changes for judging fast-moving UEs.
TFast: Refers to the maximum time required when the best cell changes Nfast times
during fast moving of UEs.
NSlow: Refers to the maximum number of best cell changes in the timing length of slowspeed timer.
TSlow: Refers to the minimum threshold of system time difference during best cell
change.
Within the Tslowjudge of the timer, the moving speed of a UE is considered slow if any
of the following conditions is met:
44
(1)The number of best cell changes is 0.

(2)The number of best cell changes is less than NSlow, and the time difference between
the system time at the last best cell change and the current system time is larger than
the time threshold Tslow.
If the time used for Nfast times of best cell changes is less than the time threshold Tfast,
the UE moving speed is considered fast (as shown in Figure 17).
(a)
(b)
Figure 16 Example of slow-moving UE judging conditions
Figure 17 Example of fast-moving UE judging condition
5.9
Coupling Handling of Different Handovers

Inter-frequency handover can be triggered by the following:
Load control
Downlink coverage events
Uplink transmit power
Uplink BLER
Downlink transmit power
Moving speed of UE
The load control based handover aims to quickly reduce system loads and ensure
system stability, and it has the top priority. The handovers based on downlink coverage
45
events, uplink transmit power, uplink BLER or downlink transmit power all aim to
guarantee the call QoS and user experience, and they have lower priority. The moving
speed based handover in the HSC 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 top priority will shield the handovers with comparatively lower priority.
For example, if the load control based handover occurs in a cell, the RNC shall no
longer hand over or access new services into the cell. In the case of a poor carrier
quality, the RNC needs to handover the UE into the cell with good quality through radio
quality measurement, without taking account of the moving speed of UE.
5.10
Inter-Frequency Handover Procedure

Inter-frequency handovers are all hard handovers, and their procedures are identical
with intra-frequency hard handover.
SRNS Relocation
SRNS relocation is mainly triggered by soft handover, hard handover,.The SRNS
relocation procedure involves several NEs in the system, such as the UE, NodeB, RNC
and CN.
In the relocation preparation procedure initiated by the SRNC for traffic beared on HSDSCH, the RELOCATION REQUIRED message carries the configuration parameters
of HSDPA that has IUR MAC-d FLOW, and then the subsequent procedure is identical
with the relocation procedure triggered by soft handover.
Figure 18 shows the overall procedure of SRNC relocation.
46
UE
N od e B
RNC
So u rce
RNC
T a rg et
1 . R elo catio n R eq uired
RANAP
RANAP
M S C /S G S N
S G S N /M SC
RANAP
2 . R elo catio n R eq uired
RANAP
RANAP
3. R elocatio n R eq uest
RANAP
4. R elocatio n R eq uest
RANAP
RANAP
5. A L C A P Iu D ata
T ranspo rt B earer S etup
6 . R elo catio n
R equest A ck.
RANAP
RANAP
7. R elocatio n R equest A ck.
RANAP
8 . R elocatio n C om m and
RANAP
9. R elocatio n C o m m and
RANAP
RANAP
RANAP
RANAP
1 0 . R elo cation
C om m it
R N SA P
RNSAP
1 1 . R elo cation D etect
RANAP
RANAP
1 2 . R elo cation D etect

RANAP
RANAP
1 3. R elo catio n C o m plete
RANAP
RANAP
14 . R elocatio n
C o m plete
RANAP
RANAP
RANAP
RANAP
1 5. Iu R elease C om m and
16 . Iu R elease C om m and
RANAP
RANAP
1 7. A L C A P Iu D ata T ransp ort B earer R elelase
RANAP
RANAP
1 8. Iu R elease C o m plete
1 9. Iu R elease C om p lete
RANAP
RANAP
Figure 18 SRNC relocation procedure (Span two CNs )
47
6.1
Relocation Triggered by Soft Handover

Source
RNC
Target
RNC
SGSN
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
Information Confirm
UE
9.Relocation Complete
10.Iu Release Command
11.Iu Release Complete
Figure 19 Relocation triggered by soft handover
Procedure description:
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 CS and PS domains, it needs to send the Relocation
Required message to CS and PS domains.
The CN sends a Relocation Request message to the DRNC, carrying RAB

SETUP message.
After the RAB of DRNC is established successfully, the DRNC sends Relocation
Request Ack message to the CN.
The CN sends Relocation Command message to the SRNC requiring the SRNC
to start relocation.
The SRNC sends Relocation Commit message to the DRNC through the lur
interface.
The DRNC sends Relocation Detect message to the CN and is converted into a
new SRNC through role exchange.
The new SRNC sends UTRAN Mobility Information message to UE to relocate URNTI.
Upon relocating U-RNTI, the UE sends a UTRAN Mobility Information Confirm

message to the new SRNC.
48
The new SRNC sends Relocation Complete message to inform the CN of the
successful relocation.
10 Upon receiving the message from the new SRNC, CN sends Iu Release
Command message to the original SRNC to release all the resources in the
original SRNC.
11 Upon releasing the lu resource, original SRNC sends Iu Release Complete
message to the CN.
There may exist some exceptional procedures during relocation.
Relocation failure caused by UTRAN Mobility Information message transmission failure
The DRNC fails to initiate the UTRAN Mobility Information Configuration
procedure due to procedure timeout or the UE failure in returning UTRAN mobility
message. In such a case, the DRNC does not send a Relocation Complete
message to the CN, and after the CN relocation timer times out, the CN initiates a
Iu Release Command message to release the resources on the DRNC side.
6.2
Relocation Triggered by Hard Handover

Source
RNC
Target
RNC
SGSN
1.Relocation Required
2.Relocation Request
3.Relocation Request Ack
UE
4.Relocation Command
5.Physical Channel
Reconfiguration
6.UE detected by target RNC

7.Relocation Detect
8.Physical Channel
Reconfiguration Complete
9.Relocation Complete
UE
10.Iu Release Command

11.Iu Release Complete
Figure 20 Relocation triggered by hard handover
Procedure description:
The SRNC initiates a Relocation Required message to the CN.
1
Upon receiving the message, the CN sends Relocation Request message to the
DRNC.
After the bearer on lu interface and the radio link are established, the DRNC returns
Relocation Request Ack message to inform the CN that the DRNC is ready.
49
The CN sends Relocation Command message to the SRNC requiring the SRNC
to start relocation.
The SRNC sends Physical Channel Reconfiguration message to the UE, requiring
UE to perform hard handover.
The DRNC initiates UE Detect message to imply that the DRNC already detects
UE.
Upon detecting the UE, the DRNC sends Relocation Detect message to CN, and
then DRNC is converted into a new SRNC through role exchange.
The UE returns Physical Channel Reconfiguration Complete message to inform

the new SRNC of successful hard handover.
Upon receiving the message, the new SRNC sends Relocation Complete
message to CN.
Upon receiving the message from the new SRNC, the CN sends Iu Release
Command message to the original SRNC to release all the resources in the
original SRNC.
10 Upon releasing the lu resource, the original SRNC sends Iu Release Complete
message to the CN.
There may exist some exceptional procedures during relocation.
Relocation failure caused by radio bearer (RB) reconfiguration failure
Upon receiving the RB reconfiguration failure message, the SRNC will send a
relocation cancellation message to the CN and the CN release the resources on the
DRNC side through the lu release procedure.
Inter-RAT Handover Policy

Inter-RAT handover means that an UE switches from one radio access system to
another, and specifically, from a UTRAN access system to a GERAN system. (If an UE
switches from a GERAN system to a UTRAN system, the GERAN system policy is used.)
Inter-RAT handover can be measurement-based handover between systems or blind
handover based on GsmShareCover(Overlap or Covers).
The prerequisite of measured-based Inter-RAT handover is that the UE measures the
quality of the Inter-RAT neighboring cells. In WCDMA system, for Inter-RAT
measurement in CELL_DCH state, the UE must enable compressed mode for Inter-RAT
measurement unless it has dual receivers. In addition, regarding the influences of the
compressed mode on the system and UE, 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
transmit power of the UE, downlink transmit power, and inter-frequency measurement
(quality measurement on the PCPICH by the UE). When receiving Inter-RAT
measurement result reported by the UE, the RNC makes Inter-RAT handover decision
50
and switches the UE to the target cell of the GERAN system specified in the
measurement result.
7.1
Inter-RAT Measurement
To avoid measurement fluctuation, the UE must perform layer 3 filter on the
measurement result, and then use the filtered value for event decision and reporting.
The FilterCoeff (Rat) is used as the layer 3 filter factor for intra-system measurement,
and the GsmFilterCoef is used for GSM system measurement. The principles are the
same as the formula for co-frequency measurement.
NA
Q UTRAN = 10 LogM UTRAN = W 10 Log Mi + (1 W) 10 LogM Best

i=1
Where:
QUTRAN indicates the measurement result of the currently used UTRAN frequency (dB for
Ec/No; dBm for RSCP).
MUTRAN indicates the measured physical value of the currently used UTRAN frequency
(ratio for Ec/No; mV for RSCP).
Mi indicates the measured physical value of cell I in the current active set.
NA indicates the number of the cells (excluding best cells) in an active set.
MBest indicates the measurement result of the best cells in an active set.
W indicates the weight of the best cells in an active set in the frequency quality
evaluation of the currently used UTRAN.
7.1.1
Overview of Inter-RAT Measurement

Inter-RAT measurement is to measure the Inter-RAT cells. In the case of Inter-RAT
measurement, the measured quantity of the UTRAN network can be triggered based on
the measured quantity of Ec/N0 or RSCP. The specific parameter used is controlled by
the NonIntraMeasQuan parameter. The measured quantity of Inter-RAT measurement
depends on the systems to be measured. For the GERAN, the measured quantity is
RSSI. At present, Inter-RAT measurement supports only the handover modes reported
through events. The IntRatHoMth parameter is invalid.
3GPP defies a series of Inter-RAT measurement events. An UE reports the
corresponding events when defined conditions are met.
3A: The currently used UTRAN carrier quality is lower than a threshold, and the quality
of other radio systems is higher than a threshold. It is used for decision of Inter-RAT
handover.
Q Used TUsed H 3a /2 and MOther
RAT
+ CIOOther RAT TOther
RAT
+ H3a /2
Where:
51
QUsed indicates the estimated quality of the used frequency of the UTRAN.
TUsed indicates the absolute threshold (Thresh[MAX_RAT_MEAS_EVENT]) of the
currently used frequency difference.
H3a is the hysteresis parameter (Hysteresis[MAX_RAT_MEAS_EVENT] (Rat)) for 3A
event decision.
MOther RAT is the quality measurement result of other systems.
CIOOther RAT is the quality offset of other system cells (CellIndivOffset(gsmRelation).
is
the
absolute
TOther
RAT
(ThreshSys[MAX_RAT_MEAS_EVENT]).l
threshold
of
other
systems
3C: The quality of other radio systems is higher than a threshold. It can be used for
Inter-RAT handover decision.
MOther
RAT
+ CIOOther
RAT
TOther
RAT
+ H3c /2
Where:
MOther RAT is the quality measurement result of other systems.
CIOOther RAT is the quality offset of other system cells (CellIndivOffset(gsmRelation).
is
the
absolute
TOther
RAT
(ThreshSys[MAX_RAT_MEAS_EVENT]).
threshold
of
other
systems
H3c is the hysteresis parameter (Hysteresis[MAX_RAT_MEAS_EVENT] (Rat)) for 3C

event decision.
During Inter-RAT event decision, the carrier must keep meeting the reporting scope or
threshold of an event for a certain period of time (TrigTime[MAX_RAT_MEAS_EVENT]
(Rat)) before it can be reported as this event. In this way, improper reporting of InterRAT events resulted from carrier quality fluctuation can be avoided.
7.1.2
Control Methods for Inter-RAT Measurement
7.1.2.1
Setting up a measurement
The principles for setting up an Inter-RAT measurement (service-based Inter-RAT
handover) depend on the value of the service handover IE in the RAB assignment
request message.
When the value of the service handover IE is Handover to GSM should be

performed, it indicates that the RAB should switch to the GSM system as soon as
possible. During the service setup or intra-system handover of such a service, if the
current dwell cell has a GSM neighboring cell ad the inter-frequency measurement
is not enabled after service setup or handover is successful, the RNC enables Inter-
52
RAT measurement immediately. (Note: For simplification, the startup policy of

service-based Inter-RAT measurement is not checked in the following scenarios:
Soft handover succeeds.
ii
Incoming compressed mode relocation of soft handover is enabled.)
When the value of the service handover IE is Handover to GSM should not be
performed, it indicates that the RAB can switch to the GSM only when it exceeds
the bearing capability of the UMTS. For such a service, the RNC enables Inter-RAT
measurement only when the quality of the UMTS system is poor. The specific
scenarios are as follows:
The current working carrier is in poor quality (the measurement method is described
in ), but the conditions for enabling inter-frequency measurement (that is, the interfrequency neighboring cell is not configured) or for inter-frequency blind handover
are not met. In this case, if Inter-RAT measurement is not enabled or the conditions
for Inter-RAT blind handover are met but blind handover fails, Inter-RAT
measurement is set up.
iii
7.1.2.2
Inter-frequency measurement is enabled, and all non-working carriers trigger

2E events. In this case, if the conditions for Inter-RAT blind handover are not
met and Inter-RAT neighboring cells exist, or the conditions for Inter-RAT blind
handover are met, but blind handover fails, inter-frequency measurement is
disabled, and Inter-RAT measurement is set up.
When the value of the service handover IE is Handover to GSM shall not be
performed, it indicates that the service cannot be switched to the GSM. For such a
service, the RNC does not enable Inter-RAT measurement or trigger the handover
to GSM.
For the service handover attribute of concurrent services, the highest service
handover value of BasicPrio is used. When a concurrent service is added or
deleted, the RNC needs to determine the service handover attribute and thus
decides to adopt the measurement policy and handover policy between 2G systems.
Modifying a measurement
After Inter-RAT measurement is enabled, the measurement is changed in the following
cases:
After soft handover, if Inter-RAT measurement parameters and Inter-RAT

neighboring cells are changed, the Inter-RAT measurement parameters and InterRAT neighboring cell list are updated by means of measurement modification.
When a service is added or deleted, if the handover parameters for a single service
or concurrent services are different, Inter-RAT measurement parameters must be
updated by means of measurement and modification.
53
7.1.2.3
Deleting a measurement
Before hard handover, Inter-RAT measurement is enabled. Terminate the Inter-RAT

measurement.
After soft handover, Inter-RAT measurement is terminated in any of the following

cases:
The cell in an active set does not have Inter-RAT neighboring cell.
Inter-RAT neighboring cells are neighboring cells with GsmShareCover(Overlap or
Covers)
The Inter-RAT neighboring cells and the intra-frequency neighboring cells of the
cells in the current active set are neighboring cells with GsmShareCover(Overlap
or Covers)
7.1.2.4
When the service handover value of the service is Handover to GSM should not be
performed, and the quality of the working carries turns for better (the measurement
method is the same as that described in ), the compressed mode is closed, and
Inter-RAT measurement is terminated.
In the case of exceptions, such as the exceptional report of the Inter-RAT

measurement task (for example, an unavailable measurement task is received from
the network side), the corresponding Inter-RAT measurement is released.
Processing of Inter-RAT Events
Processing of 3A/3C events
perform Inter-RAT handover.

During Inter-RAT handover, the same cell can be triggered by any of the 3A, and 3C
events. The recommended policy parameter for Inter-RAT handover, namely,
RatHoTactic, controls the specific event that is used as the basis for Inter-RAT handover
decision.
7.1.2.5
Policy for Setting Inter-RAT Measurement Parameters
Policy for setting Inter-RAT event parameters

There are four Inter-RAT measurement events, namely, 3A, and 3Cevents. The
EventId [MAX_RAT_MEAS_EVENT] (Rat) parameter controls the number of the
events to be configured. The EventId [MAX_RAT_MEAS_EVENT] (Rat)
parameter controls the specific events to be configured. The MeaEvtId parameter is
defined in array mode. The dimension of arrays equals the value of MeasEvtNum,
being 4 at most.
Policy for combining handover parameters in macro diversity
54
Measurement parameters are based on cells. Therefore, in the case of macro

diversity, the measurement parameters configured for the best cell are used as
handover parameters. If the best cell changes, the measurement parameters must
be updated.
Setting of multiple sets of handover parameters

Inter-RAT handover parameters can be configured separately according to the
measured quantity, measurement reporting mode, and service bearer type. In this
way, multiple sets of measurement parameters are required for different purposes.
The classification is as follows:
Measured quantity of the UTRAN
NonIntraMeasQuan
( PCPICH RSCP or Ec/N0)
Measurement reporting mode
IntRatHoMth
(Event report or periodically report
Only Event report can be supported currently. So the following parameters for
periodically
report
is
not
used
currently:
PrdMeasEcNo(RAT),
PrdMeasRSCP(RAT), PrdRptAmount(RAT), PrdRptInterval(RAT) )
Service bearer type
(TrfCategory(Rat))
Not Related to Service Type (used for detect set measurement)
For ease of parameter modification and optimization, Inter-RAT handover parameters

are arranged by indexes. The index relation is as follows:
55
Figure 21 Indexing relation for Inter-RAT handover
The procedure for obtaining an Inter-RAT handover parameter is as follows: 1) Obtain

the TrfCatRatMIdx parameter from Utran Cell (utranCell). 2) Find the InterRatCfgNo
parameter in UE Inter-Rat Measurement Relative to Traffic Category (CRat) based on
TrfCatRatMIdx, TrfCategory, and EvtMeasRSCP or EvtMeasEcNo. 3) Find the
corresponding handover measurement parameter in UE Inter-Rat Measurement
Configuration Information(Rat) based on InterRatCfgNo.
Note: Each InterRatCfgNo corresponds to an EvtMeasRSCP or EvtMeasEcNo,
indicated by InterRatCfgNote.
The relations between the other parameters to be entered in the Inter-RAT

measurement control message and the OMCR parameters are as follows:
(MeasRptTrMod)
GSM BSIC acknowledgement indication for Inter-RAT

measurement
(BSICVeriReq)
UTRAN quality estimation reporting indication
(UtranEstQual)
GSM cell RSSI reporting indication
(GsmCarrRSSIInd)
Measured quantity for UTRAN quality estimation in

Inter-RAT measurement
(OwnMeasQuantity)
(OwnMeasQuantity)
(RptCrt(Rat)
Note: OwnMeasQuantity and RptCrt(Rat) are automatically entered based on

InterRatCfgNote, and manual operations are not needed. The values of these
parameters are for maintenance personnels reference.
7.1.3
Processing in the Case of More Than 32 Inter-RAT Neighboring Cells

When an active set has many cells, the number of the Inter-RAT neighboring cells for
the cells in an active set may exceed the maximum value, 32.
When the number of Inter-RAT neighboring cells exceeds 32, some must be deleted to
ensure only 32 Inter-RAT neighboring cells exist in an active set.
In addition, the cells to be deleted must be the cells having the least impacts on active
set users, namely, the cells having the poorest signal quality or in furthest geographic
locations. For this purpose, priority is defined for each Inter-RAT neighboring cell.
56
7.1.3.1
Priority Settings of Cells

The MeasPrio(gsmRelation) parameter is used to define the priority of an Inter-RAT
neighboring cell. The value can be 0 (high), 1 (medium), or 2 (low). The value can be
determined by network planning engineers according to existing network situations,
such as the quality and geographic location of the Inter-RAT neighboring cell. Figure 22
shows the priority settings of Inter-RAT neighboring cells based on geographic locations.
Assume that the gray cell in the center is the source cell. It has three layers of Inter-RAT
neighboring cells, marked respectively in yellow, blue, and red. The Inter-RAT
neighboring cells in yellow have the highest priority level, namely, 0. Those in blue have
the secondary highest priority level, namely, 1. Those in red have the lowest priority
level, namely, 2.
Figure 22 Priority settings of cells
7.1.3.2
Deletion policy in the case of more than 32 neighboring cells

Related standards stipulate that the maximum number of Inter-RAT neighboring cells is
32. When an UE is in macro diversity state, the number of unions of Inter-RAT
neighboring cells of multiple cells in the macro diversity may exceed this limit. Therefore,
a specific policy is needed to delete neighboring cells. The policy involves combination,
selection, and deletion of the neighboring cells with the same priority.
Priority combination
If a cell is a common neighboring cell of multiple cells in the active set, it may be
configured with different priority levels in different cells. In this case, the multiple priority
levels of this cell must be combined, using the highest priority level as the priority of this
cell.
Neighboring cell list update and deletion in the case of more than 32 neighboring
cells
57
If the Inter-RAT neighboring cell list of an active list contains more than 32 cells, the
cells are sorted in descending order based on priority. The first 32 cells remain
unchanged, and all other cells are put into the reserved Inter-RAT neighboring cell list.
Each time when the 1A, 1B, 1C, or 1D event is triggered, the priority levels of the
neighboring cells in the Inter-RAT neighboring cell list are updated. If there are less than
32 cells in the Inter-RAT neighboring cell list after the 1B event is triggered, the cells
with the highest priority in the reserved Inter-RAT neighboring cell list are put into the
Inter-RAT neighboring cell list. The number of the cells from the reserved Inter-RAT
neighboring cell list equals: min(32 number of existing cells in the Inter-RAT
neighboring cell list).
7.2
Inter-RAT Handover Based on Downlink Coverage

Downlink coverage uses 2D and 2F events as the criterions for evaluating the signal
quality of the current frequency. The RNC transmits the 2D ad 2F event configuration
to the UE when the service is set up. If the UE reports a 2D event, that is, the current
carrier is in poor signal quality, and no inter-frequency neighboring cells exist, or the UE
reports a 2E event after inter-frequency measurement is started (that is, the signal
quality of the measured inter-frequency neighboring cell is also poor), the RNC tries to
initiate Inter-RAT blind handover first if Inter-RAT neighboring cells withGsmShareCover
(Overlap or Covers) exist. If Inter-RAT neighboring cells exist but have no
GsmShareCover (Overlap or Covers) relation, or blind handover fails, the RNC needs to
configure and start Inter-RAT measurement 3A or 3C event to the UE, and then
performs the corresponding decision process for Inter-RAT handover according to the
3A, or 3C event subsequently reported by the UE.
7.3
Inter-RAT Handover Based on Uplink BLER

The UlBlerHoSwch parameter controls the enabling of uplink BLER based handover.
This policy is specific to DCHs.
When the value of UlBlerHoSwch is On, the RNC periodically measures the uplink
BLER. If the measured uplink BLER is higher than a certain threshold (1.25%), and the
real-time measured value (Sirtarget) reaches the maximum value of the BAM
(ULMaxSIR), the RNC triggers the Inter-RAT measurement or handover policy. The
process is the same as that for Inter-RAT handover based on downlink coverage.
7.4
Inter-RAT Handover Based on Uplink Transmit

Power
The UlPwrHoSwch parameter controls the enabling of inter-frequency handover based
on uplink transmit power.
Notes: Handover Based on Uplink Transmit Power is used only for traffic carried on
DCHs.
When the value of UlPwrHoSwch is On, the RNC starts the internal measurement for
the UE that reports a 6A (the uplink power of the UE exceeds the absolute threshold,
58
namely, 100% of the maximum transmit power of the UE) or 6B (the uplink power of the
UE is lower than the absolute threshold, namely, 90% of the maximum transmit power of
the UE) measurement event when the initial service is set up. When the transmit power
of the UE meets the event threshold, the UE reports the corresponding event. After
receiving a 6A event, the RNC performs processing according to the same process as
that for Inter-RAT handover based on downlink coverage.
7.5
Inter-RAT Handover Based on Downlink Transmit

Power
The DlPwrHoSwch parameter controls the enabling of inter-frequency handover based
on downlink transmit power.
This policy is specific to DCHs.
When the value of DlPwrHoSwch is On, the RNC checks the DTCP in the NodeB
dedicated measurement report. If the DTCP reaches a certain threshold (90% of the
maximum downlink transmit power MaxDlDpchPwr), it indicates the downlink power is
very high. In this case, the process is the same as that for Inter-RAT handover based on
downlink coverage.
7.6
Handover Based on Load Control

RNC selects some users with lower priority levels in the cell and switches them to the
neighboring cells with GsmShareCover (Overlap or Covers) blindly in case of the
following conditions:
When the load (transmitted carrier power (TCP) or received total wideband power
(RTWP)) of a cell is rather high,
If the current neighboring cell does not have any inter-frequency neighboring cell
with ShareCover (Overlap or Covers), but has inter-RAT neighboring cells with
GsmShareCover (Overlap or Covers), the RNC selects some users with lower
priority levels in the cell and switches them to the neighboring cells with
GsmShareCover (Overlap or Covers) blindly.
In this way, the system load can be reduced quickly and the system reliability can be
guaranteed. For details about the inter-system handover based on load, refer to the ZTE
UMTS Load Balance Feature Description.
7.7
with ShareCover (Overlap or Covers)with

GsmShareCover (Overlap or Covers)with
GsmShareCover (Overlap or Covers)Coupling for
Different Handover Causes
As described above, the causes of Inter-RAT handover include the following:
59
Handover based on load control
Based on downlink coverage/quality event
Based on uplink transmit power
Based on uplink BLER
Based on downlink transmit power
Handover based on load control aims to reduce the system load quickly to ensure the
system stability. Therefore, handover based on load control has the highest priority. The
handover triggered by radio quality causes such as downlink coverage event, uplink
transmit power, uplink BLER, ad downlink transmit power aims to ensure the QoS and
impressibility of users. The handover of this kind has second highest priority.
The handover of higher priority filters the handover of lower priority, for example, a cell
handed over based on load control cannot access new services.
60
7.8
Inter-RAT Handover Process
7.8.1
CS Service Handover from 3G System to 2G System
Figure 23 3G to 2G CS service handover
7.8.2
PS Service Reselection in 3G to 2G Handover

The handover of PS domain from the UTRAN to the 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 route area update. This case applies to an UE in CELL_FACH or
URA_PCH state.
61
UE
S erving
RNC
CN
1 . C ell R eselectio n
trig g ered
RANAP
RANAP
2 . Iu R elease C o m m and
2 . Iu R elease C o m p lete
RANAP
RANAP
Figure 24 PS service reselection initiated by an UE in the case of 3G to 2G handover
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
an UE in CELL_DCH or CELL_FACH 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 then initiates route area update.
Figure 25 PS service reselection initiated by the RNC in the case of 3G to 2G handover
Note: Both processes are applicable to an UE in CELL_FACH state. The specific policy
is as follows: The process of PS service reselection actively initiated by the UE is used
for the 3G to 2G PS service handover based on radio quality. The process of PS service
reselection actively initiated by the RNC is used for the 3G to 2G PS service handover
based on load.
IMSI-based handover
The IMSI-based handover can limit the range of cells for allowed for handover according
to IMSI of UE with the following principle:
While the measurement control message is not delivered before CommonID message is
received in the signaling stage, RNC does not yet know the cells authorized to the user.
Therefore RNC delivers the measurement control message regardless of the
authorization status of the cells.
62
While delivering measurement control message after receiving CommonID message,

RNC queries whether the cells are authorized according to the IMSI information carried
in the CommonID message of lu interface and also the authorization information
configured in the network side. Only the authorized neighbor cells will be included in the
neighbor cell list of measurement control message.
In the process of RAB assignment of service, a decision of whether the current service
cell is authorized is made according to the IMSI information carried in the CommonID
message and the authorization information configured in the network side.
If none of the cells in the active set is authorized
If the best cells in the active set are like the coverage neighbor cells (ShareCover)
and are also authorized cells,
then the inter-frequency handover is performed along with service establishment
Otherwise,
If the best cells in the active set are like the coverage GSM neighbor cells
(GsmShareCover) and are authorized cells, and also the current service is AMR,
then Inter-RAT directional retry is performed
Otherwise,
return, treated as assignment failure
Otherwise,
establish service normally. If some of the cells in the active set are unauthorized
cells, delete the unauthorized cells from the active set through the active set update flow.
8.1
Querying Whether a SRNC Cell Is Authorized

According to IMSI
Figure 26 shows the process of querying whether a neighbor cell belonging SRNC is
authorized according to the IMSI information carried in the CommonID message of lu
interface and also the authorization information configured in the network side. The
steps of the query are:
1
Resolve the MCC (rncPnSnac), MNC and other number information ExtInfo (10
digits at most, number of digits depending on ExtInfoDgtNum) according to the IMSI
carried in the CommonID message of lu interface.
Use the information (MCC, MNC and ExtInfo) resolved and also the authorized
network information MCC (rncPnSnac), MNC (rncPnSnac) and ExtInfo (rncPnSnac)
configured in the network side to query whether the IMSI of UE is authorized or not.
If MCC, MNC and ExtInfo of UE does not have a configuration item in rncPnSnac,
no neighbor cell authorized is returned. Otherwise the MCC (SMCC), MNC
(SMNC) and SNAC that are authorized are obtained.
63
According to the relation between MCC (rncLcSnac), MNC (rncLcSnac), SNAC

(rncLcSnac) and LAC (rncLcSnac) and also the cell information including MCC
(utranCell), MNC (utranCell), LAC (utranCell), query whether the cell belongs to the
MCC (rncLcSnac), MNC (rncLcSnac), and LAC (rncLcSnac) that are already
authorized.
Figure 26 Schematic Diagram of Querying Whether a SRNC Cell Is Authorized According to IMSI
8.2
Querying Whether a DRNC Cell Is Authorized

According to IMSI
Figure 26 shows the process of querying whether a neighbor cell belonging DRNC is
authorized according to the IMSI information carried in the CommonID message of lu
interface and also the authorization information configured in the network side. The
steps of the query are:
4
Resolve the MCC (rncPnSnac), MNC and other number information ExtInfo (10
digits at most, number of digits depending on ExtInfoDgtNum) according to the IMSI
carried in the CommonID message of lu interface.
Use the information (MCC, MNC and ExtInfo) resolved and also the authorized
network information MCC (rncPnSnac), MNC (rncPnSnac) and ExtInfo (rncPnSnac)
configured in the network side to query whether the IMSI of UE is authorized or not.
If MCC, MNC and ExtInfo of UE does not have a configuration item in rncPnSnac,
no neighbor cell authorized is returned. Otherwise the MCC (SMCC), MNC
(SMNC) and SNAC that are authorized are obtained.
According to the granted MCC SMCC MNC SMNC SNAC and the
DRNC neighbor cell information including: MCC externalUtranCell
gsmRelation MNC externalUtranCell gsmRelation SNAC
externalUtranCell gsmRelation , query whether the DRNC neighbor cell
belongs to the MCC SMCC MNC SMNC and SNAC that are already
authorized.
64
NotesIn step 3how many SNAC is configured for DRNC neighbor cells is controlled
by SNACNum (externalUtranCellgsmRelation)
CommonID:
MCC
MNC
ExtInfo
rncPnSnac:
MCC
MNC
ExtInfo
SNAC
Granted:
MCC
MNC
SNAC
rncLcSnac
Granted
MCC
MNC
LAC
MCC
MNC
SNAC
LAC
Neighbor cell is
granted or not
utranCell
MCC
MNC
LAC
Figure 27 Schematic Diagram of Querying Whether a DRNC Cell Is Authorized According to IMSI
HSDPA-related special strategy

For channel changes from non-DCH to DCH in the HSDPA handover process, the target
data rate of DCH is the guaranteed bit rate of GBR traffic or the minimum rate of DRBC
for no GBR traffic(refer to ZTE UMTS DRBC Algorithm Feature Description for details).
9.1
Overview
The cells are classified in three types according to the support capability of HSDPA
(HspaSptMeth) after HSDPA is introduced: (1) support HSDPA and DCH; (2) do not
support HSUPA or HSDPA; (3) support HSDPA only. The services are classified in two
types: HSDPA service and NHSDPA service. The HSDPA handover is similar to R99
handover in terms of measurement and handover decision, except that the decisions of
cell capacity during a handover and the service type are added. For the HSDPA service,
the handover is accepted through HS-DSCH to the cells that support HSDPA and DCH
and cells that support HSDPA only as much as possible. If the HS-DSCH fails, accept
the handover to the cells that support HSDPA and DCH and cells that do not support
HSUPA or HSDPA through DCH. For the NHSDPA service, the handover can only be
accepted through DCH to the cells that support HSDPA and DCH and cells that do not
support HSUPA or HSDPA.
After HSDPA is introduced, the inter-RNC handover also depends on the capability of
office direction RNC to support HSDPA (RncFeatSwitch) because neighbor cells feature
varying support capabilities (HspaSptMeth). That is, only if both the target cell and target
RNC (office direction RNC) support HSDPA, the HS-DSCHHS-DSCH handover can
be performed. Otherwise, the DCHDCH handover flow cannot be originated until HSDSCH falls back to DCH. The channel transfer is performed along with handover.
65
Different channel transfer situations are described in the following based on different
handover types.
9.2
Intra-frequency Handover
The intra-frequency handover of HDSPA includes soft add/soft drop/soft replacement of
HS-DSCH associated channel, HS-DSCH service cell change, channel type change due
to different capabilities between source cell and target cell during the handover process.
The strategy of soft add/soft drop/soft replacement of HS-DSCH associated channel is
described in strategy of intra-frequency handover. The HS-DSCH service cell change
and channel type change are special handover strategies that make HSDPA different
from the R99 (DCH) handover. The specific principles are:
1
HS-DSCH->DCH
If the HS-DSCH is used before the handover and the link to be deleted for 1B event
triggering/radio link failure happens to be the service cell of HS-DSCH, and also the
cells in the active set do not support acceptance through HS-DSCH, a decision of
soft handover together with HS-DSCH transferring to DCH is made.
If the HS-DSCH is used before the handover and the 1C event is triggered, the cell
to be replaced is the HS-DSCH service cell and also the cells in the new active set
do not support acceptance through HS-DSCH, a decision of soft handover together
with HS-DSCH transferring to DCH is made.
If the HS-DSCH is used before the handover and the 1D event triggers intrafrequency hard handover and the target cell does not support acceptance through
HS-DSCH, a decision of intra-frequency hard handover together with HS-DSCH
transferring to DCH is made.
DCH->HS-DSCH
The current service of UE includes HSDPA and also the DCH is used before the
handover. If the 1D event triggers intra-frequency hard handover and the target cell
supports acceptance through HS-DSCH, a decision of intra-frequency hard
handover together with DCH transferring to HS-DSCH is made.
The current service of UE includes HSDPA, the DCH is used before the handover
and also the best cell in the active set supports HSDPA. If the downlink traffic
increases to trigger the 4A event (refer to ZTE UMTS DRBC Algorithm Feature
Description for details), a decision of handover from DCH to HS-DSCH is made.
HS->DSCH->HS-DSCH
If the HS-DSCH is used before the handover and the 1D event triggers intrafrequency hard handover and the target cell supports acceptance through HSDSCH, a decision of intra-frequency hard handover together with HS-DSCH service
cell change is made.
66
If the HS-DSCH is used before the handover and the link to be deleted for 1B event
triggering/radio link failure happens to be the service cell of HS-DSCH, and also
there are cells in the active set that support acceptance through HS-DSCH, a
decision of soft handover together with HS-DSCH change is made. If the 1C/1D
event triggers soft handover, the cell to be replaced is the HS-DSCH service cell
and also the cells in the new active set support acceptance through HS-DSCH, a
decision of soft handover together with HS-DSCH change is made.
In the above described processes, the 1D event may trigger ping-pong handover that
leads to frequent change of service cell. To avoid this,
a time threshold (T1d) is configured and changes of service cell should occur at an
interval longer than this threshold.
9.3
Inter-frequency Handover
The conditions for triggering the inter-frequency handover of HDSPA are described in
inter-frequency handover strategy. The HS-DSCH service cell change or channel type
change always happens in the handover process. The principles are as follow:
1
HS-DSCH->DCH
The current service of UE includes HSDPA and also the HS-DSCH is used before
the handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell does not support
acceptance through HS-DSCH, a decision of inter-frequency hard handover
together with HS-DSCH transferring to DCH is made.
DCH->HS-DSCH
The current service of UE includes HSDPA and also the DCH is used before the
handover. If the original decision is to trigger an inter-frequency handover
(measurement-based or blind handover) and also the target cell supports
together with DCH transferring to HS-DSCH is made.
HS-DSCH->HS-DSCH
The current service of UE includes HSDPA and also the HS-DSCH is used before
the handover. If the original decision is to trigger an inter-frequency handover
together with HS-DSCH service cell change is made.
Handover of HS-DSCH between Iur interfaces

For the hard handover of HS-DSCH between Iur interfaces, the handover strategy
is the same as the handover inside the RNC if the target cell supports HS-DSCH.
But if the target cell does not support HS-DSCH, the HS-DSCH/DCH should fall
back to DCH/DCH first, and then the hard handover between lur interfaces and
redirection flow can be performed.
67
9.4
Inter-RAT Handover
Two strategies are available for handovers between HSDPA systems: UTRAN>GSM/GERAN strategy and GSM/GERAN -> UTRAN strategy.
10
UTRAN->GSM/GERAN
The HSDPA service is included. The channel transfers to DCH/DCH first, and then
the same handover flow as that for between R99 systems is performed.
GSM/GERAN -> UTRAN
The strategy is similar to that when a service accesses the system for the first time.
If both service and target cell support HS-DSCH/DCH, the service is established
directly on HS-DSCH/DCH, otherwise try DCH/DCH.
HSUPA-related special strategy

If in the handover process, the channel type changes from non-DCH to DCH, the
handover is accepted according to the target rate of DCH, that is, the guaranteed bit rate
of the current service while the handover occurs or the minimum rate of DRBC (refer to
ZTE UMTS DRBC Algorithm Feature Description for details).
10.1
Overview
HSUPA is developed on the basis of HSDPA. An HSUPA network element (UE, RNC or
NodeB) that supports HSUPA will also supports HSDPA. That is, if E-DCH is adopted in
uplink, HS-DSCH is adopted in downlink without doubt. Therefore, HSUPA supports five
types of cells (HspaSptMeth): (1) cells that support HSUPA and HSDPA; (2) cells that
support HSUPA, HSDPA and DCH; (3) cells that support HSDPA and DCH; (4) cells
that support HSDPA only; (5) cells that do not support HSUPA or HSDPA. For the cells
that support HSUPA and HSDPA, the E-DCH is used in uplink and the HS-DSCH is
used in downlink. The DPCH is used as associated channel. For the cells that support
HSUPA, HSDPA and DCH, the E-DCH or DCH is used in uplink and the HS-DSCH or
DCH is used in downlink. The DPCH is used as associated channel or allocated to users
who do not use HSUPA or HSDPA.
The service types supported by HSUPA are HSPA services if they can be carried by
HSUPA or HSDPA (HSUPA and HSDPA are equivalent as far as the services are
concerned). Otherwise they are NHSPA services. The HSPA services should be
accepted first through E-DCH and HS-DSCH in cells that support HSUPA and HSDPA,
cells that support HSDPA only, cells that support HSUPA, HSDPA and DCH and cells
that support HSDPA and DCH (HspaSptMeth). If E-DCH and HS-DSCH fail to accept the
services, the HSPA services should be accepted through DCH in cells that support
HSUPA, HSDPA and DCH, cells that support HSDPA and DCH or cells that do not
support HSUPA or HSDPA. The NHSPA services can only be accepted through DCH in
cells that support HSUPA, HSDPA and DCH, cells that support HSDPA and DCH or
cells that do not support HSUPA or HSDPA.
68
The maximum number of cells allowed in the E-DCH active set in the process of HSUPA
soft handover is controlled by the parameter MaxNumOfEdchAct.
After HSUPA is introduced, the inter-RNC handover also depends on the capability of
office direction RNC to support HSUPA (RncFeatSwitch) because neighbor cells feature
varying support capabilities (HspaSptMeth). That is, only if both the target cell and target
RNC (office direction RNC) support HSUPA, the E-DCHE-DCH handover can be
performed. Otherwise, the DCHDCH handover flow cannot be originated until E-DCH
falls back to DCH. The channel transfer is performed along with handover. Different
channel transfer situations are described in the following based on different handover
types.
10.2
The intra-frequency handover of HDUPA includes soft add/soft drop/soft replacement of
E-DCH associated channel, E-DCH service cell change, channel type change due to
different capabilities between source cell and target cell during the handover process.
The strategy of soft add/soft drop/soft replacement of E-DCH associated channel is
described in strategy of intra-frequency handover. The E-DCH service cell change and
channel type change are special handover strategies that make HSUPA different from
the R99 (DCH) handover. The specific principles are:
1
HS-DSCH/E-DCH->DCH/DCH
If the link to be deleted for 1B event triggering/radio link failure happens to be the
service cell of HS-DSCH/E-DCH, and also the cells in the active set do not support
acceptance through HS-DSCH/E-DCH or HS-DSCH/DCH, a decision of soft
handover together with HS-DSCH/E-DCH transferring to DCH/DCH is made.
If the 1C event is triggered, the cell to be replaced is the HS-DSCH/E-DCH service

cell and also the cells in the new active set do not support acceptance through HSDSCH/E-DCH, a decision of soft handover together with HS-DSCH/E-DCH
transferring to DCH/DCH is made.
If the 1D event is triggered, the best cell changes from HS-DSCH/E-DCH service
cell to a cell that does not support HS-DSCH/E-DCH, a decision of intra-frequency
hard handover together with HS-DSCH/E-DCH transferring to DCH/DCH is made.
DCH/DCH->HS-DSCH/E-DCH
The current service of UE includes HSPA and also the DCH/DCH is used before the
handover. If the 1D event triggers intra-frequency hard handover and the target cell
supports acceptance through HS-DSCH/E-DCH, a decision of intra-frequency hard
handover together with DCH/DCH transferring to HS-DSCH/E-DCH is made.
The current service of UE includes

and also the best cell in the active
traffic increases to trigger the 4A
Feature Description for details), a
DSCH/E-DCH is made.
HSPA, the current channel type is DCH/DCH,

set supports HSDPA. If the downlink or uplink
event (refer to ZTE UMTS DRBC Algorithm
decision of handover from DCH/DCH to HS-
69
10.3
HS-DSCH/E-DCH->HS-DSCH/E-DCH
If the 1D event triggers intra-frequency hard handover and the target cell supports
acceptance through HS-DSCH/E-DCH, a decision of intra-frequency hard handover
together with HS-DSCH/E-DCH service cell change is made.Refer to 2.1.2 Intrafrequency Hard Handover for the scenario where the intra-frequency hard handover
is triggered.
service cell of HS-DSCH/E-DCH, and also there are cells in the active set that
support acceptance through HS-DSCH/E-DCH, a decision of soft handover together
with HS-DSCH/E-DCH service cell change is made. If the 1C/1D event triggers soft
handover, the cell to be replaced is the HS-DSCH/E-DCH service cell and also the
cells in the new active set support acceptance through HS-DSCH/E-DCH, a
decision of soft handover together with HS-DSCH/E-DCH change is made.
HS-DSCH/E-DCH->HS-DSCH/DCH
service cell of HS-DSCH/E-DCH, and also the cells in the active set supports HSDSCH/DCH instead of HS-DSCH/E-DCH, a decision of soft handover together with
HS-DSCH/E-DCH transferring to HS-DSCH/DCH is made.
If the 1C event is triggered, the cell to be replaced is the HS-DSCH/E-DCH service

cell and also the cells in the new active set supports HS-DSCH/DCH instead of HSDSCH/E-DCH, a decision of soft handover together with HS-DSCH/E-DCH
transferring to HS-DSCH/DCH is made.
If the 1D event is triggered, the best cell changes from HS-DSCH/E-DCH service
cell to a cell that supports HS-DSCH/DCH instead of HS-DSCH/E-DCH, a decision
of intra-frequency hard handover together with HS-DSCH/E-DCH transferring to
HS-DSCH/DCH is made.
HS-DSCH/DCH->HS-DSCH/E-DCH
The current service of UE includes HSPA service and also the HS-DSCH/DCH is
used before the handover. If the 1D event is triggered, the best cell changes from
HS-DSCH/DCH service cell to a cell that supports HS-DSCH/E-DCH, a decision of
intra-frequency hard handover together with HS-DSCH/DCH transferring to HSDSCH/E-DCH is made.
The conditions for triggering the inter-frequency handover of HDSPA are described in
inter-frequency handover strategy. The HS-DSCH service cell change or channel type
change always happens in the handover process. The principles are as follow:
1
HS-DSCH/E-DCH->DCH/DCH
70
The current service of UE includes HSPA and also the HS-DSCH/E-DCH is used
before the handover. If the original decision is to trigger an inter-frequency
handover (measurement-based or blind handover) and also the target cell does not
support acceptance through HS-DSCH/E-DCH or HS-DSCH/DCH, a decision of
inter-frequency hard handover together with HS-DSCH/E-DCH transferring to
DCH/DCH is made.
2
DCH/DCH->HS-DSCH/E-DCH
The current service of UE includes HSPA and also the DCH/DCH is used before the
handover. If the original decision is to trigger an inter-frequency handover
acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover
together with DCH/DCH transferring to HS-DSCH/E-DCH is made.
HS-DSCH/E-DCH->HS-DSCH/E-DCH
handover (measurement-based or blind handover) and also the target cell supports
together with HS-DSCH/E-DCH service cell change is made.
HS-DSCH/E-DCH->HS-DSCH/DCH
acceptance through HS-DSCH/DCH instead of HS-DSCH/E-DCH, a decision of
inter-frequency hard handover together with HS-DSCH/E-DCH transferring to HSDSCH/DCH is made.
HS-DSCH/DCH->HS-DSCH/E-DCH
The current service of UE includes HSPA and also theHS-DSCH/DCH is used
together with HS-DSCH/DCH transferring to HS-DSCH/E-DCH is made.
Handover of HS-DSCH between Iur interfaces

For the hard handover of E-DCH between Iur interfaces, the handover strategy is
the same as the handover inside the RNC if the target cell supports E-DCH. But if
the target cell does not support E-DCH, the E-DCH should fall back to DCH first,
and then the hard handover between lur interfaces and redirection flow can be
performed.
10.4
Inter-RAT Handover
1
UTRAN->GSM/GERAN
The HSPA service is included. The channel transfers to DCH/DCH first, and then
the same handover flow as that for between R99 systems is performed.
71
GSM/GERAN -> UTRAN

Similar to the handover between R99 systems, if the target cell support HSDSCH/E-DCH, the service is established directly on HS-DSCH/E-DCH.
11
MBMS-related special strategy

After the MBMS is introduced, the cell type (MbmsSuptInd) can be defined as follows:
11.1
Cells that do not support MBMS (Not Support).
Cells that support both MBMS and non-MBMS (Support MBMS and not MBMS).
Cells that support MBMS only (Only Support MBMS).
1
The soft add strategy does not consider whether the soft add cell belongs to the
service area or whether it supports the MBMS in the case of 1A/1C soft add. That is,
the strategy is similar to that for the non-MBMS case.
1B/1C or the link is deleted due to radio link failure:
For the MBMS service has set up p-t-p bearer but the link is deleted, if the best cell
does not belong to MBMS service area, the best cell does not support the MBMS
service, the best cell has set up the p-t-m bearer, or the best cell is not the
convergence carrier of the service, then p-t-p RB is released.
For the MBMS service has not set up p-t-p bearer but the MBMS service connection
already exists, the best cell belongs to MBMS service area, the best cell supports
the MBMS service, the bearer type strategy needs to set up the p-t-m bearer and
the carrier can set up the bearer of the service, then p-t-p RB is set up.
The principle of the type change in the bearer of the MBMS service in the active set
under the macro diversity.
Table 3
Table of Principle
Bearer Change Type

p-t-p->p-t-m
p-t-m ->p-t-p
Cell Type
Principles of Change
Best cell
Delete the p-t-p
Non best cell
No change
Best cell
Set up p-t-p: If the channel of the service is DCH,

then set up p-t-p for all cells in the active set; if
the channel of the service is HS-DSCH, then set
up p-t-p in the best cell.
Non best cell
No change
To avoid ping-pong switchover between p-t-p and p-t-m, a time threshold (T1d) is
configured and any swichover should occur at an interval longer than this threshold.
72
11.2
When UE reports MBMS MODIFIED REQUEST and the information of MBMS preferred
frequency request is carried,
1
If the target carrier comes with a cell with the same coverage (included: the
expected frequency layer cell includes the current working frequency cell) and the
cell belongs to the service area and supports the MBMS, and also the target cell is
able to allocate the resource of currently established dedicated bearer, then the cell
with the same coverage at the frequency layer can be taken as the target cell to
perform the hard handover.
If the target carrier does not come with a cell with the same coverage (included), the
neighbor cell of the current cell in the UEs active set includes the neighbor cell
(neighboring or being included) that is at the MBMS preferred frequency layer
corresponding to the MBMS service expected to be received and the neighbor cell
belongs to the service area and supports MBMS, then inter-frequency
measurement 2A/2B/2C is started for UE. When the 2A/2B/2C event reported by
UE is received, the cells that do not support MBMS are screened out and a proper
cell is taken for the hard handover.
No treatment is performed if UE does not carry the information of MBMS preferred

frequency request in the MBMS MODIFIED REQUEST.
12
parameters and configurations
12.1
Intra-Frequency Handover Parameters
12.1.1
Parameter List
Field Name
Name on the Interface
MeasPrio
Measurement Priority of Neighboring Cell
DetSetHoSwch
Detected Set Handover Switch
RptRange [MAX_INTRA_MEAS_EVENT]
Reporting Range Constant for Event

1A/1B
W[MAX_INTRA_MEAS_EVENT]
Weight for Event 1A/1B
Hysteresis[MAX_INTRA_MEAS_EVENT]
Hysteresis
FilterCoeff(Intra)
Filter Coefficient
Time to Trigger
PrdRptAmount
Amount of reporting
PrdRptInterval
Reporting Interval in Period Report

Criteria
CellIndivOffset(utranCell)
Cell individual offset
CellIndivOffset(utranRelation)
RptDeactThr
Reporting Deactivation Threshold for
73
Event 1A
RplcActThr
Replacement Activation Threshold for

Event 1C and 1J
TrfCatIntraMIdx(CIntra)
Intra-frequency Measurement
Configuration Index Related to Traffic
Category
TrfCatIntraMIdx(utranCell)
IntraMeasCfgNo
Configuration Index
MeaEvtId[MAX_INTRA_MEAS_EVENT]
Intra-frequency Measurement Event ID
TrfCategory
Service and Bearer Type Used for

Differentiating Handover Configuration
EvtMeasEcNo
UE Event Report Configuration Index for

CPICH Ec/No
EvtMeasDctEcNo
Detected Set Measurement

Configuration Index for CPICH Ec/No
IntraMeasCfgNote
Function of Configuration Parameters
MeasRptTrMod
Measurement Report Transfer Mode
MeasQuantity
Measurement quantity
EcN0RptInd
CPICH Ec/No Reporting Indicator
RscpRptInd
CPICH RSCP Reporting Indicator
PathlossRptInd
Pathloss reporting indicator
RptCrt
Report Criteria
MeasEvtNum
Event Number of Intra-frequency

Measurement
ThreshUsedFreq[MAX_INTRA_MEAS_E
VENT]
Threshold of the Quality of the Used

Frequency for Event 1E/1F
MaxNumOfAct
Maximum Number of Cells Within DCH

Active Set
StateMode
UE State Indicator Used for UTRAN

Neighboring Cell Configuration
ReadSFNInd
Read SFN Indicator
SoftHoMth
Soft Handover Method
IntraMeasQuan
UTRAN Measurement Quantity for Intrafrequency Measurements
EvtMeasDctRSCP
Detected Set Measurement

Configuration Index for CPICH RSCP
PrdMeasEcNo
UE Periodic Measurement Configuration

Index for CPICH Ec/No
PrdMeasRSCP
UE Periodic Measurement Configuration

Index for CPICH RSCP
EvtMeasRSCP
UE Event Report Configuration Index for

CPICH RSCP
74
EvtRptInterval
Reporting Interval for Event 1A/1B/1C/1J
EvtRptAmount
Amount of Reporting for Event

1A/1B/1C/1J
FbdCellInd
PcpichPwrPre
Primary CPICH Power Configuration Tag
12.1.2
Parameter Configuration
12.1.2.1
Parameter Description
Parameter name
Abbreviated name
MeasPrio
Description
This parameter indicates the measurement priority of the

neighboring cell. The highest priority is 0, the lowest
priority is 2.
Range and Step
[0, 1, 2]
Unit
N/A
Default Value (note)
OMC Path
Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource

Management->Utran Cell->Utran Cell XXX->Neighbouring Cell->Modify Advanced
Parameter-> Measurement Priority of Neighboring Cell
This parameter indicates the measurement priority of the neighbouring cell. The priority
of the neighbouring cell can be set to 0, 1, or 2, of which, 0 represents the highest
priority and 2 represents the lowest priority. The priority of the neighbouring is set by the
configuration personnel according to the signal strength and distance of the neighboring
cell.
The neighbouring cells with the priority ranked the 33rd or after are placed in the
neighboring cell reservation list. When the number of cells in the neighbouring cell list is
less than 32, the cell(s) with higher priority in the neighbouring cell reservation list are
placed to the neighbouring cell list.
12.1.2.2
Parameter name
75
Abbreviated name
DetSetHoSwch
Description
This parameter is the detected set handover control switch.
Range and Step
0: Closed
1: Open
Unit
N/A
1: Open
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Detected Set Handover Switch
The measurement control message that contains the detected set information is sent
only when the DetSetHO switch of the best cell in the current active set is set to 1 and
the current number of intra-frequency neighbouring cells is less than 32.
12.1.2.3
Reporting Range Constant for Event 1A/1B

Table 4
Parameter name
Reporting Range Constant for Event 1A/1B(dB)
Abbreviated name
RptRange [MAX_INTRA_MEAS_EVENT]
Description
This parameter controls the triggering of event 1a/1b. 1a is

easier but 1b is harder to trigger when this value increases;
and vice verse.
MAX_INTRA_MEAS_EVENT indicates the maximum number
of intra-frequency measurement event, which is 7.
Range and Step
[0, 14.5]dB step 0.5dB
Unit
dB
Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No:
[3,5,0,0,0,0,0]
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP:
[6,8,0,0,0,0,0]
Detected Set Measurement Parameters for CPICH Ec/No: [4]
Detected Set Measurement Parameters for CPICH RSCP: [7]
OMC Path

Management-> Modify Advanced Parameter->UE Intra-frquence Measurement
Configuration->Reporting Range Constant Event 1A/1B(dB)
76
Event 1A is easier to be triggered when the reporting range constant for event 1A is set
to a larger value; and vice verse.
Event 1B is easier to be triggered when the reporting range constant for event 1B is set
to a smaller value; and vice verse.
12.1.2.4
Parameter name
Abbreviated
name
W[MAX_INTRA_MEAS_EVENT]
Description
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 related to the measurement quantity and the event type.
MAX_INTRA_MEAS_EVENT indicates the maximum number of
intra-frequency measurement event, which is 7.
Range and Step
[0.0, 2.0] step 0.1
Unit
N/A
Default Value
(note)
Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: [0. 0 0. 0 0. 0 0. 0
0. 0 0. 0 0. 0]
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [0. 0 0. 0 0. 0 0. 0
0. 0 0. 0 0. 0]
Detected Set Measurement Parameters for CPICH Ec/No: [0. 0]
Detected Set Measurement Parameters for CPICH RSCP: [0. 0]
OMC Path

Configuration-> Weight for Event 1A/1B
This parameter is used for the quality judgment of event 1A and 1B. This parameter
indicates the weight of the best cell in the quality judgment and is related to the
measurement quantity and the event type.
See the description of the formula for triggering event 1A/1B in section 4.3 for the effects
of this parameter on the quality judgment.
77
12.1.2.5
Hysteresis(Intra)
Table 5
Parameter name
Hysteresis(dB)
Abbreviated name
Hysteresis[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the 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 larger the difference between the
status to trigger the event and the status to leave the 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
of intra-frequency measurement event, which is 7
Range and Step
[0, 7.5]dB step 0.5dB
Unit
dB
Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: [0,0,4,4,2,2,4]
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [4,4,6,6,4,4,6]
OMC Path

Configuration-> Hysteresis
This parameter indicates the hysteresis when judging whether to trigger the event. This
parameter avoids the change of the trigger status due to very small change. This
parameter is related to the measurement quantity and the event type.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
12.1.2.6
Filter Coefficient(Intra)
78
Parameter name
Filter Coefficient
Abbreviated
name
FilterCoeff
Description
This parameter indicates the 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 points in one measurement cycle and L1 filters
the 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 TS25. 331:
F = (1 a) F + a M , a = 1/2(k/2).
n
n 1
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 (periodical report) or
the judgment (event report).
Range and Step
(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19)
Unit
N/A
Default Value
(note)
Period Report Parameters for CPICH Ec/No: 2

UE Event Report Parameters for CPICH Ec/No: 2
Period Report Parameters for CPICH RSCP: 3
UE Event Report Parameters for CPICH RSCP: 3
Detected Set Measurement Parameters for CPICH Ec/No: 3
Detected Set Measurement Parameters for CPICH RSCP: 3
OMC Path

Configuration-> Filter Coefficient
This parameter indicates the filtering factor that UE performs the L3 filtering on the
measurement results of the intra-frequency measurement. 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 (periodical report) or the judgment (event report).
79
12.1.2.7
Time to Trigger(Intra)
Parameter name
Time To Trigger(ms)
Abbreviated name
Description
This parameter indicates the time difference between having

detected the event generation and reporting the event. Only
when the event generation is detected and still meets all
requirements of event triggering after Time to trigger, the event
can be triggered and reported. The larger the value is, the
stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements.
Sometimes, if it is set too large, the quality of calls may
decrease.
Range and Step
(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320,
640, 1280, 2560, 5000)ms
Unit
N/A
Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No:
[200,640,320,320,200,200, 320]ms
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [200,200,200,
200,200,200,200]ms
Detected Set Measurement Parameters for CPICH Ec/No:
[200]ms
Detected Set Measurement Parameters for CPICH RSCP:
[200]ms
OMC Path

Configuration-> Time to Trigger
This parameter indicates the time difference between the time that the event generation
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be configured according to the actual requirements.
80
12.1.2.8
Amount of Reporting in Period Report Criteria
Parameter name
Abbreviated
name
PrdRptAmount
Description
This parameter indicates the times of the periodical reports to be

reported. If the UE detects that the times of event reports exceeds
the value of Amount of reporting, UE stops reporting the
measurement results.
Range and Step
[1, 2, 4, 8, 16, 32, 64, Infinity]
Unit
N/A
Default Value
(note)
Period Report Parameters for CPICH Ec/No: Infinity

UE Event Report Parameters for CPICH Ec/No: Period Report Parameters for CPICH RSCP: Infinity
UE Event Report Parameters for CPICH RSCP: Detected Set Measurement Parameters for CPICH Ec/No: Detected Set Measurement Parameters for CPICH RSCP: -
OMC Path

Configuration-> Amount of Reporting in Period Report Criteria
This parameter indicates the times of the periodical reports to be reported. In the case of
the UE side, the value is used for the determination of whether to report the
measurement report in reporting the periodical report. If the UE detects that the times of
event reporting exceeds the value of Amount of reporting, UE stops reporting the
12.1.2.9
Reporting Interval in Period Report Criteria
Parameter name
Reporting Interval in Period Report Criteria(ms)
Abbreviated
name
PrdRptInterval
Description
This parameter indicates the interval of periodical reporting when

such reporting is triggered periodically.
Range and Step
[250, 500, 1000, 2000, 3000, 4000, 6000, 8000, 12000,

16000, 20000, 24000, 28000, 32000, 64000]ms
Unit
Ms
Default Value
(note)
Period Report Parameters for CPICH Ec/No: 1s
UE Event Report Parameters for CPICH Ec/No: -
81
Period Report Parameters for CPICH RSCP: 1s

UE Event Report Parameters for CPICH RSCP: Detected Set Measurement Parameters for CPICH Ec/No: Detected Set Measurement Parameters for CPICH RSCP:
OMC Path

Configuration-> Reporting Interval in Period Report Criteria(ms)
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria. In the case of the periodical reporting, the UE reports the
measurement reports in the period indicated by the parameter.
12.1.2.10
Cell individual offset(utranCell)
Parameter name
Cell Individual Offset (dB)
Abbreviated name
CellIndivOffset
Description
An offset is allocated for each cell being monitored. The offset

can be positive or negative. Before the UE judges whether an
event occurs, adds the offset 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 is possibly (at least temporarily)
the target cell of the handover or removed from the active set.
Range and Step
OMCR:[ -10, 10 ] dB step 0.5 dB

RNC:D = ( P+10 ) * 2, [ 0, 40 ]
Unit
dB
0dB
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Cell Individual Offset(dB)
This parameter defines the individual offset of cells in the active set relative to other cells.
When the value is positive, a positive value is added to the measurement result. If the
value is negative, a negative value is added to the measurement result. Refer to the
description of the formula for triggering event 1B/1C/1d in section 4.3 for the effect of
this parameter on the measurement report.
82
Through the configuration of the individual offset of a single cell, the trigger difficulty of
the cell can be adjusted to meet the practical requirements of network planning without
the need to modify the global handover parameters.
12.1.2.11
Cell individual offset(utranRelation)
Parameter name
Cell Individual Offset (dB)
Abbreviated name
CellIndivOffset
Description

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 is possibly (at least temporarily) the target
cell of the handover or removed from the active set.
Range and Step
OMCR: [-10, 10]dB; Step 0.5

RNC: D=(P+10)*2, [0, 40]
Unit
dB
0 dB
OMC Path

Parameter->Cell Individual Offset(dB)
This parameter defines the individual offset of cells outside the active set relative to
other cells. When the value is positive, a positive value is added to the measurement
result. If the value is negative, a negative value is added to the measurement result.
Refer to the description of the formula for triggering event 1A/1C/1d in section 4.3 for the
effect of this parameter on the measurement report.
the cell can be adjusted to meet the practical requirements of network planning without
the need to modify the global handover parameters.
12.1.2.12
Reporting Deactivation Threshold for Event 1A
Parameter name
Reporting Deactivation Threshold for Event 1A
Abbreviated name
RptDeactThr[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the maximum number of the cells that

can exist in the active set. When the UE detects that one cell in
83
the monitoring set satisfies the threshold of event 1a, it first

judges whether the number of the cells in the current active set
is not greater than the value indicated by this parameter. If so,
triggers event 1a. If not, does not trigger event
1a.MAX_INTRA_MEAS_EVENT indicates the maximum
number of intra-frequency measurement event, which is 7.
Range and Step
(0, 1, 2, 3, 4, 5, 6, 7)
Unit
N/A
Only configured for event 1A.

Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: [2, -, -, -, -, -, -]
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [2, -, -, -, -, -, -]
OMC Path

Configuration-> Reporting Deactivation Threshold for Event 1A
This parameter indicates the maximum number of the cells allowed in the active set.
When the UE detects that one cell in the monitoring set satisfies the trigger threshold of
event 1A, it determines whether the number of the cells in the current active set greater
than the value indicated by this parameter at first. If yes, the event 1A is not triggered.
12.1.2.13
Replacement Activation Threshold for Event 1C and 1J
Parameter name
Replacement Activation Threshold for Event 1C and 1J
Abbreviated name
RplcActThr[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the minimum number of the cell that

can exist in the DCH active set when triggering event 1c or in
the E-DCH active set when triggering event 1j. When UE
detects that one cell satisfies the trigger threshold of event
1c/1j, it first judges whether the number of the cells in the
current active set is smaller than the value indicated by this
parameter. If so, do not trigger event 1c/1j. If the value is 0,
the parameter is invalid.
Range and Step
(0, 1, 2, 3, 4, 5, 6, 7)
Unit
N/A
Only configured for event 1c and 1j.
84
Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: [-, -, 3, -, -, -,
3]
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [-, -, 3, -, -, -,
3]
Detected Set Measurement Parameters for CPICH Ec/No: [-]
Detected Set Measurement Parameters for CPICH RSCP: [-]
OMC Path

Configuration-> Replacement Activation Threshold for Event 1C and 1J
This parameter indicates the minimum number of the cell allowed in the DCH active set
when triggering event 1C or in the E-DCH active set when triggering event 1j. When UE
detects that the measurement result of a cell satisfies the trigger threshold of event 1c/1j,
it first judges whether the number of cells in the current active set is smaller than the
value indicated by this parameter. If yes, event 1C/1j is not triggered.
12.1.2.14
Category(CIntra)
Configuration
Index
Related
to
Traffic
Parameter name
Intra-frequency Measurement Configuration Index Related to

Traffic Category
Abbreviated name
TrfCatIntraMIdx
Description
This parameter indicates the configuration index of the intrafrequency measurement parameters based on traffic type.
There are several different sets of measurement values
according to different traffic types.
Range and Step
0..65535
Unit
N/A
OMC Path

Management-> Modify Advanced Parameter->UE Intra-frequency Measurement
Relative to Traffic Category Configuration Information->Intra-frequency Measurement
Configuration Index Related to Traffic Category
85
This parameter indicates the index of the intra-frequency measurement configuration

based on traffic type. Each traffic type corresponds to a unique intra-frequency
measurement configuration index. If multiple sets of handover parameters are
configured, each cell may use different index. Hence, the intra-frequency handover
parameters of the cells may be different from each other.
12.1.2.15
Category(UtranCell)
Configuration
Index
Related
to
Traffic
Parameter name
Intra-frequency Measurement Configuration Index Related to

Traffic Category
Abbreviated name
TrfCatIntraMIdx
Description
This parameter indicates the configuration index of the intrafrequency measurement parameters based on traffic type.
Range and Step
0..65535
Unit
N/A
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Intra-frequency Measurement Configuration Index Related to Traffic Category
This parameter indicates the index of the intra-frequency measurement configuration

based on traffic type. Each traffic type corresponds to a unique intra-frequency
measurement configuration index. If multiple sets of handover parameters are
configured, each cell may use different index. Hence, the intra-frequency handover
parameters of the cells may be different from each other.
12.1.2.16
Intra-frequency Measurement Configuration Index
Parameter name
Intra-frequency Measurement Configuration Index
Abbreviated name
IntraMeasCfgNo
Description
This parameter indicates the configuration index of the intrafrequency measurement parameters, which is used to index
different parameter configuration sets for intra-frequency
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.
Range and Step
0..65535
86
Unit
N/A
2: UE Event Report Parameters for CPICH Ec/No

10: Detected Set Measurement Parameters for CPICH Ec/No
OMC Path

Configuration-> Intra-frequency Measurement Configuration Index
Each intra-frequency measurement configuration with different measurement purpose

and measurement quantity is assigned with a unique intra-frequency measurement
configuration index. This parameter indicates the index of the intra-frequency
measurement configuration. This configuration index is cited in the table Intra-frequency
measurement configuration relationship of the service type-related UE.
That is, the parameter Intra-frequency Measurement Configuration Index Related to
Traffic Category (namely TrfCatIntraMIdx) is cited in the advanced parameter of the
serving cell and different Intra-frequency Measurement Configuration Indexes (namely
IntraMeasCfgNo) can be selected aiming at the specific service type, measurement
purpose, and measurement quantity. Hence, this parameter can be used to meet the
various requirements of network planning.
12.1.2.17
Parameter name
Abbreviated name
MeaEvtId[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the event triggered by the intrafrequency measurement, which is related to the measurement
quantity.
Range and Step
1a,1b,1c,1d,1e,1f,1j
Unit
N/A
Default Value
(note)
[1a,1b,1c,1d]
OMC Path

Configuration-> Intra-frequency event identity
87
This parameter indicates the identity of the event triggered by the intra-frequency
measurement (1A~1D).
12.1.2.18
Service and Bearer Type Used for Differentiating Handover Configuration
Parameter name
Service and Bearer Type Used for Differentiating Handover

Configuration
Abbreviated
name
TrfCategory
Description
This parameter differentiates different sets of handover parameter

according to different traffic type. Taking account of various
characteristic of service, it should have various handover
parameters such as hysteresis, absolute threshold for 3a/3c etc.
Altogether there are 8 sets of configuration for different scenario
based on service type, transport channel type, single/multi RAB.
Range and Step
0: Single RT RAB Including Voice on DL DCH/UL DCH

1: Single RT RAB Excluding Voice on DL DCH/UL DCH
2: Single NRT on DL DCH/UL DCH
3: Single RAB on DL HS-DSCH/UL DCH
4: Single RAB on DL HS-DSCH/UL E-DCH
5: All Multi-RAB on DL DCH/UL DCH
6: Multi-RAB, HSPA is Involved and only DCHs are Used in UL
7: Multi-RAB, HSPA is Involved and E-DCH is Used in UL
0xff: Not Related to Service Type
Unit
N/A
Default Value
(note)
OMC Path

Relative to Traffic Category Configuration Information->Service and Bearer Type Used
for Differentiating Handover Configuration
All the services are classified into eight categories according to the real-time attribute of
services, channel type, and service quantity. This parameter indicates the service and
bearer type. The handover parameters can be configured flexibly for different scenarios
and the parameters may have different handover trigger thresholds and hysteresis.
The value 0xff (Not Related to Service Type) is exclusive used in the measurement of
the detected set.
88
12.1.2.19
UE Event Report Configuration Index for CPICH Ec/No
Parameter name
UE Event Report Configuration Index for CPICH Ec/No
Abbreviated name
EvtMeasEcNo
Description
This parameter indicates the UE event report configuration

index for CPICH Ec/No, used for indexing the configuration of
the set of intra-frequency measurement parameters for event
reporting decided by UE when measurement quantity is CPICH
Ec/No.
Range and Step
0..65535
Unit
N/A
See Table 4
OMC Path

Relative to Traffic Category Configuration Information->UE Event Report Configuration
This parameter indicates the index of the intra-frequency measurement configuration for
event reporting judgment by the UE when the measurement quantity is CPICH Ec/No.
12.1.2.20
TrfCatIntraMIdx
TrfCategory
0xff
PrdMeasEcNo
EvtMeasEcNo
PrdMeasRSCP
EvtMeasRSCP
EVTMEASDCTECN
O
10
10
10
10
10
10
10
10
10
EVTMEASDCTRSCP
11
11
11
11
11
11
11
11
11
Period Report Configuration Index for CPICH Ec/No
Default Value 9
Default Value 8
Default Value 7
Default Value 6
Default Value 5
Default Value 4
Default Value 3
Default Value 2
Field Name
Default Value 1
Table 6
Default Value of the UE Intra-frequency Measurement Configuration Parameters
Related to Traffic Category
Parameter name
89
Abbreviated
name
PrdMeasEcNo
Description
This parameter indicates the period report configuration index for

CPICH Ec/No, used for indexing the configuration of the set of
intra-frequency measurement parameters for periodical reporting
when measurement quantity is CPICH Ec/No.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 4
OMC Path

Relative to Traffic Category Configuration Information->Period Report Configuration
periodic reporting by the UE when the measurement quantity is CPICH Ec/No.
12.1.2.21
Period Report Configuration Index for CPICH RSCP
Parameter name
Abbreviated
name
PrdMeasRSCP
Description

CPICH RSCP, used for indexing the configuration of the set of
intra-frequency measurement parameters for periodical reporting
when measurement quantity is CPICH RSCP.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 4
OMC Path

periodic reporting by the UE when the measurement quantity is CPICH RSCP.
12.1.2.22
UE Event Report Configuration Index for CPICH RSCP
90
Parameter name
UE Event Report Configuration Index for CPICH RSCP
Abbreviated
name
EvtMeasRSCP
Description
This parameter indicates the UE event report configuration index

for CPICH RSCP, used for indexing the configuration of the set of
intra-frequency measurement parameters for event reporting
decided by UE when measurement quantity is CPICH RSCP.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 4
OMC Path

Relative to Traffic Category Configuration Information-> UE Event Report Configuration
event reporting judgment by the UE when the measurement quantity is CPICH RSCP.
12.1.2.23
Detected Set Measurement Configuration Index for CPICH Ec/No

Table 7
Parameter name
Detected Set Measurement Configuration Index for CPICH

Ec/No
Abbreviated name
EvtMeasDctEcNo
Description
This parameter indicates the detected set measurement

configuration index for CPICH Ec/No, used for indexing the
configuration of the set of intra-frequency measurement
parameters for detected set when measurement quantity is
CPICH Ec/No.
Range and Step
0..65535
Unit
N/A
Default Value
(note)
See Table 4
OMC Path

Relative to Traffic Category Configuration Information->Detected Set Measurement
Configuration Index for CPICH Ec/No
91
This parameter indicates the configuration index of the set of intra-frequency

measurement parameters when measurement quantity of the detected set cell is CPICH
Ec/No.
12.1.2.24
Detected Set Measurement Configuration Index for CPICH RSCP
Parameter name
Detected Set Measurement Configuration Index for CPICH RSCP
Abbreviated
name
EvtMeasDctRSCP
Description
This parameter indicates the detected set measurement

configuration index for CPICH RSCP, used for indexing the
configuration of the set of intra-frequency measurement
parameters for detected set when measurement quantity is CPICH
RSCP.
Range and Step
0..65535
Unit
N/A
Default Value
(note)
See Table 4
OMC Path

Relative to Traffic Category Configuration Information->Detected Set Measurement
Configuration Index for CPICH RSCP
This parameter indicates the configuration index of the set of intra-frequency

measurement parameters when measurement quantity of the detected set cell is CPICH
RSCP.
12.1.2.25
Parameter name
Abbreviated name
IntraMeasCfgNote
Description
This parameter indicates the purpose and functions of the set of

intra-frequency measurement configuration parameters.
Range and Step
Period Report Parameters for CPICH Ec/No

UE Event Report Parameters for CPICH Ec/No
Period Report Parameters for CPICH RSCP
UE Event Report Parameters for CPICH RSCP
Detected Set Measurement Parameters for CPICH Ec/No
Detected Set Measurement Parameters for CPICH RSCP
Unit
N/A
Default Value
There are 6 sets of measurement parameter are configured for

different measurement purpose, theDefault Values of this
92
(note)
parameter are as the following:

0: Period Report Parameters for CPICH Ec/No
5: Period Report Parameters for CPICH RSCP
7: UE Event Report Parameters for CPICH RSCP
11: Detected Set Measurement Parameters for CPICH RSCP
OMC Path

Configuration-> Function of Configuration Parameters
This parameter indicates the purpose and functions of the set of intra-frequency
measurement configuration parameters.
12.1.2.26
Parameter name
Abbreviated name
MeasRptTrMod
Description
This parameter indicates the RLC mode of the inter-frequency

measurement report. If the value is AM RLC, RNC can request
UE for retransmission after receiving the error SDU label (not
continuous). If the value is UM RLC, the retransmission is not
required. Usually, report the results of the important
measurements in AM mode and those less important in UM
mode (to reduce the traffic of the measurement report and
increase the system capacity).
Range and Step
0: Acknowledged Mode RLC

1: Unacknowledged Mode RLC
Unit
N/A
Default Value
(note)
UE Period Report Parameters for CPICH Ec/No: Acknowledged

Mode RLC
UE Inter-frequency Event Report Parameters for CPICH Ec/No:
Acknowledged Mode RLC
UE Period Report Parameters for CPICH RSCP: Acknowledged
Mode RLC
UE Inter-frequency Event Report Parameters for CPICH RSCP:
OMC Path
93

Configuration-> Measurement Report Transfer Mode
This parameter indicates the transfer mode of the measurement quantity: acknowledge
mode or unacknowledged mode.
12.1.2.27
Parameter name
Abbreviated name
MeasQuantity
Description
This parameter indicates the measurement quantity of the intrafrequency measurement that UE performs.
Range and Step
0: CPICH Ec/No
1: CPICH RSCP
2: Pathloss
Unit
N/A
Default Value
(note)
Period Report Parameters for CPICH Ec/No: CPICH Ec/No

UE Event Report Parameters for CPICH Ec/No: CPICH Ec/No
Period Report Parameters for CPICH RSCP: CPICH RSCP
UE Event Report Parameters for CPICH RSCP: CPICH RSCP
CPICH Ec/No
CPICH RSCP
OMC Path

Configuration-> Measurement quantity
This parameter indicates the measurement quantity of the intra-frequency measurement

that UE performs. If a new intra-frequency measurement configuration index is added,
the measurement quantity is fixed when the functions of the set of the intra-frequency
measurement parameters is selected. For example, when the parameter
IntraMeasCfgNote is set to UE Event Report Parameters for CPICH Ec/No, the value
of MeasQuantity is set to the corresponding CPICH Ec/No.
12.1.2.28
94
Parameter name
Abbreviated name
EcN0RptInd
Description
This parameter indicates whether UE should report the

measurement result based on the measurement quantity
CPICH Ec/No.
Range and Step
0: False (No Report)

1: True (Report)
Unit
N/A
Period Report Parameters for CPICH Ec/No: True

UE Event Report Parameters for CPICH Ec/No: True
Period Report Parameters for CPICH RSCP: True
UE Event Report Parameters for CPICH RSCP: True
Detected Set Measurement Parameters for CPICH Ec/No: True
True
OMC Path

Configuration-> CPICH Ec/No Reporting Indicator
This parameter indicates whether the UE should report the measurement result based
on the measurement quantity CPICH Ec/No.
This parameter is associated with the parameter MeasQuantity. When MeasQuantity is
set to 0, the parameter EcN0RptInd must be set to TRUE.
12.1.2.29
Parameter name
Abbreviated name
RscpRptInd
Description

CPICH RSCP.
Range and Step
0: False (No Report)

1: True (Report)
Unit
N/A
Period Report Parameters for CPICH Ec/No: True

UE Event Report Parameters for CPICH Ec/No: True
Period Report Parameters for CPICH RSCP: True
UE Event Report Parameters for CPICH RSCP: True
95

True
True
OMC Path

Configuration-> CPICH RSCP Reporting Indicator
on the measurement quantity CPICH RSCP.
set to 1, the parameter RscpRptInd must be set to TRUE.
12.1.2.30
Pathloss Reporting Indicator
Parameter name
Abbreviated name
PathlossRptInd
Description

pathloss.
Range and Step
0..65535
Unit
N/A
Default Value
(note)
Period Report Parameters for CPICH Ec/No: False

UE Event Report Parameters for CPICH Ec/No: False
Period Report Parameters for CPICH RSCP: False
UE Event Report Parameters for CPICH RSCP: False
False
False
OMC Path

Configuration-> Pathloss reporting indicator
on the measurement quantity pathloss.
96
12.1.2.31
Report Criteria
Parameter name
Report Criteria
Abbreviated name
RptCrt
Description
This parameter indicates the report rules of the intra-frequency

measurement. When the value is Periodical Reporting Criteria
, two sets of the measurement parameters are required to be
configured. One set of the periodical parameters are
configured to UE and the other set of event parameters are
configured to SRNC for event judgment. When receiving the
periodical measurement reports from UE, SRNC judges which
event is triggered according to the event criteria parameters,
and then decides whether to perform the software handover
according to the triggered event. When the value is Event
Reporting Criteria, only one set of the measurement
parameters is required to be configured to UE. SRNC decides
whether to perform the software handover according to the
measurement results reported by UE.
Range and Step
1: Event Reporting Criteria

2: Periodical Reporting Criteria
Unit
N/A
Period Report Parameters for CPICH Ec/No: Periodical

Reporting Criteria
UE Event Report Parameters for CPICH Ec/No: Event
Reporting Criteria
Period Report Parameters for CPICH RSCP: Periodical
Reporting Criteria
UE Event Report Parameters for CPICH RSCP: Event
Reporting Criteria
Event Reporting Criteria
Event Reporting Criteria
OMC Path

Configuration-> Report Criteria
This parameter indicates the reporting criteria of the intra-frequency measurement,

including the event reporting criteria and the periodical reporting criteria.
12.1.2.32
Event Number of Intra-frequency Measurement
97
Parameter name
Event Number of Intra-frequency Measurement
Abbreviated name
MeasEvtNum
Description
This parameter indicates how many events are required to be

configured for the set of the intra-frequency measurement
parameters for a certain purpose. The number of the events is
related to the purpose of the 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.
Range and Step
[1,MAX_INTRA_MEAS_EVENT]
in which,MAX_INTRA_MEAS_EVENT =7.
Unit
N/A
Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: 7
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: 7
Detected Set Measurement Parameters for CPICH Ec/No: 7
Detected Set Measurement Parameters for CPICH RSCP: 7
OMC Path

Configuration-> Event Number of Intra-frequency Measurement
This parameter indicates the number of events that should be configured for the set of
the intra-frequency measurement parameters for a certain purpose. The value is related
to the purpose of the measurement and the judgment method and the algorithm of the
soft handover.
12.1.2.33
Threshold of the Quality of the Used Frequency for Event 1E/1F
Parameter name
Threshold of the Quality of the Used Frequency for Event 1E/1F
Abbreviated name
ThreshUsedFreq[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the absolute threshold value used for

judging event 1e/1f.
Range and Step
CPICH RSCP: (-115..-25) dBm

CPICH Ec/No: (-24..0) dB
Pathloss: (30..165) dB
Unit
CPICH RSCP: dBm
98
CPICH Ec/No: dB
Pathloss: dB
Period Report Parameters for CPICH Ec/No: -
Default Value
(note)
UE Event Report Parameters for CPICH Ec/No: [-24,-24,-24,-24,12,-20,-24]

Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [-115, -115, -115, 115,-80,-97,-115]
Detected Set Measurement Parameters for CPICH Ec/No: Detected Set Measurement Parameters for CPICH RSCP: -
OMC Path
Interface Path:
This parameter indicates the absolute threshold used for judging event 1e/1f by using
carrier frequency.
12.1.2.34
Maximum Number of Cells Within DCH Active Set
Parameter name
Maximum Number of Cells Within DCH Active Set
Abbreviated name
MaxNumOfAct
Description
This parameter indicates the maximum number of cells within

DCH active set.
Range and Step
[1, 6]
Unit
N/A
OMC Path

Management->Modify Advanced Parameter->RNC Radio Resource Management>Maximum Number of Cells Within DCH Active Set
This parameter indicates the maximum number of cells allowed in the DCH active set.
The default value of the parameter is 3.
12.1.2.35
UE State Indicator Used for UTRAN Neighboring Cell Configuration
99
Parameter name
UE State Indicator Used for UTRAN Neighboring Cell

Configuration
Abbreviated name
StateMode
Description
This parameter indicates the status of the neighboring cell.

When SIB11 is to be sent, the cells that support idle mode are
selected from the neighboring cells list and are filled in SIB11;
When the measurement control message is to be sent, the
cells that support DCH status are selected from the neighboring
cells list and are filled in the measurement control message.
0: Idle State Only
Range and Step
1: Cell_DCH State Only

2: Connected State, Non-Cell_DCH
3: Idle State + Cell_DCH State
4: Idle State + Connected State, Non-Cell_DCH
5: Cell_DCH State + Connected State, Non-Cell_DCH
6: Idle State + Cell_DCH State+ Connected State, NonCell_DCH
Unit
N/A
OMC Path

Parameter->UE State Indicator Used for UTRAN Neighboring Cell Configuration
This parameter indicates the UE status used for the neighboring cell. When the
neighbouring cell is configured by the status, the neighbouring cell list used for
reselection in nondedicated mode and the neighbouring cell list used for handover in
dedicated mode are differentiated as follows:
When SIB11 is to be sent, the UE selects the cell that supports the idle state or the
connected (Non-Cell_DCH) state from the neighboring cells list and fills in SIB11;
When SIB12 is to be sent, the UE selects the cell that supports the connected (NonCell_DCH) state from the neighboring cells list and fills in SIB12;
When the measurement control message is to be sent, the UE selects the cell that
supports the Cell_DCH state from the neighboring cells list.
12.1.2.36
Read SFN Indicator
100
Parameter name
Read SFN Indicator
Abbreviated name
ReadSFNInd
Description
This parameter indicates whether to read the SFN of the

target cell.
Range and Step
0: False
1: True
Unit
N/A
1: True
OMC Path

Parameter->Read SFN Indicator
This parameter indicates whether to read the SFN of the neighbouring cell.In the case of
the intra-frequency neighbouring cell, the recommended configuration is True (Read); in
the case of the inter-frequency neighbouring cell, the recommended configuration is
False (Do not read).
12.1.2.37
Parameter name
Abbreviated name
SoftHoMth
Description
The paramerer indicates the soft handover method is

periodical method or event method.
Range and Step
0: Periodical method
1: Event method
Unit
N/A
1: Event method
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Soft Handover Method
The parameter indicates the soft handover method (periodical method or event method)
that should be used in the current cell. The event method is recommended.
101
12.1.2.38
UTRAN Measurement Quantity for Intra-frequency Measurements
Parameter name
UTRAN Measurement Quantity for Intra-frequency

Measurements
Abbreviated name
IntraMeasQuan
Description
This parameter indicates UTRAN measurement quantity for

intra-frequency measurements.
Range and Step
0: Ec/No
1: RSCP
2: Ec/No and RSCP
Unit
N/A
0: Ec/No
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>UTRAN Measurement Quantity for Intra-frequency Measurements
This parameter indicates the measurement quantity (Ec/No or RSCP) for the intrafrequency measurement of the cell. The measurement quantity Ec/No is recommended.
12.1.2.39
Reporting Interval for Event 1A/1B/1C/1J
Parameter name
Reporting Interval for Event 1A/1B/1C/1J(ms)
Abbreviated
name
EvtRptInterval[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the time interval to report the

measurement results after triggering event 1a/1b/1c/1j (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 times of event reports exceeds Amount of
Reporting for Event 1A/1B/1C/1J, UE stops reporting the
measurement results. If the result of judgment indicates that event
1a/1b/1c/1j finishes, stop reporting the measurement results even
the times of report do not reach Amount of Reporting for Event
1A/1B/1C/1J. MAX_INTRA_MEAS_EVENT indicates the
maximum number of intra-frequency measurement event, which is
7.
Range and Step
[0, 250, 500, 1000, 2000, 4000, 8000, 16000]ms
Unit
ms
Default Value
(note)
Only configured for event 1a, 1c, 1j.

Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: [2000, -, 2000, -, , -, 2000]ms
102
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [2000, -, 2000, -, , -, 2000]ms
[2000]ms
[2000]ms
OMC Path

Configuration-> Reporting Interval for Event 1A/1B/1C/1J
This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event
1A/1C meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
12.1.2.40
Amount of Reporting for Event 1A/1B/1C/1J
Parameter name
Amount of Reporting for Event 1A/1B/1C/1J
Abbreviated
name
EvtRptAmount[MAX_INTRA_MEAS_EVENT]
Description
This parameter indicates the maximum times to report the

measurement report after triggering event 1a/1b/1c/1j (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 times of event reports exceeds the value indicated
by this parameter, UE stops reporting the measurement results. If
the result of judgment indicates that event 1a/1b/1c/1j finishes,
stop reporting the measurement results even the times of report
do not reach the value indicated by this parameter.
Range and Step
[1, 2, 4, 8, 16, 32, 64, Infinity]
Unit
N/A
Default Value
(note)
Only configured for event 1a, 1c, 1j.

Period Report Parameters for CPICH Ec/No: UE Event Report Parameters for CPICH Ec/No: [4, -, 4, -, -, -, 4]
Period Report Parameters for CPICH RSCP: UE Event Report Parameters for CPICH RSCP: [4, -, 4, -, -, -, 4]
OMC Path
103

Configuration-> Amount of Reporting for Event 1A/1B/1C/1J
This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event
1A/1C meets the reporting range of quality standards, the UE will report Event 1A/1C
periodically (EvtRptInterval) until this event does not meet reporting conditions or the
reporting times reach the maximum allowed times (EvtRptAmount).
12.1.2.41
Parameter name
Abbreviated
name
FbdCellInd
Description
This parameter indicates whether the cell affects the intrafrequency event 1A/1B judgment. If the cell belongs to the active
set of the UE, this parameter indicates whether the measurement
results of the cell will affect the reporting of event 1A/1B. That is to
say whether the measurement quantity of the cell is used when
judging whether 1A/1B criteria are satisfied.
Range and Step
0: False
1: True
Unit
N/A
Default Value
(note)
0: False
OMC Path

Parameter->Forbidden Cell Indicator for Event 1A/1B
This parameter indicates whether the cell is effect while evaluating the intra-frequency
1A/1B event
12.1.2.42
Parameter name
Abbreviated
name
PcpichPwrPre
Description
This parameter indicates whether PCPICH transmission power is

configured.
PCPICH transmission power is valid when this parameter is set
True. Otherwise, PCPICH transmission power is invalid.
Range and Step
0: False
1: True
104
Unit
N/A
Default Value
(note)
1: True
OMC Path
Interface Path: View-> View->Configuration Management->RNC ME->RNC Radio

Resource Management->External Utran Cell-> External Utran CellXX-> Modify
Advanced Parameter-> Primary CPICH Power Configuration Tag
This parameter indicates whether PCPICH transmission power is configured.

PCPICH transmission power is valid when this parameter is set True. Otherwise,
PCPICH transmission power is invalid.
12.2
Inter-Frequency Handover Parameters
12.2.1
Parameter List
Field Name
MeasPrio
ULMaxSIR
Maximum Uplink SIR Target
UlBlerHoSwch
UL BLER Switch for handover
UlPwrHoSwch
UE Tx Power Switch for handover
DlPwrHoSwch
DL Tx Power Switch for handover
UseOfHCS
Use of HCS
HcsPrio(utranCell)
HCS_PRIO
HcsPrio(externalUtranCell
)
HCS_PRIO
Tfast
Tfast
Nfast
Nfast
Tslowjudge
Tslowjudge
Tslow
Tslow
Nslow
Nslow
InterHoTactic
Inter- frequency Handover Tactic
FilterCoeff(Inter)
Filter Coefficient
ThreshUsedFreq[MAX_IN
TER_MEAS_EVENT]
Absolute Threshold of the Quality of the Currently Used

Frequency for 2B/2D/2F
Wused[MAX_INTER_MEA
S_EVENT]
Weight of the Currently Used Frequency for 2A/2B/2D/2F
Hysteresis[MAX_INTER_
MEAS_EVENT]
Hysteresis
105
TrigTime[MAX_INTER_M
EAS_EVENT]
Time to Trigger
ThreshNoUsedFreq[MAX_
INTER_MEAS_EVENT]
Absolute Threshold of the Quality of the Non-used

Frequency for 2A/2B/2C/2E
WNoUsed[MAX_INTER_
MEAS_EVENT]
Weight of the Non-used Frequency for 2A/2B/2C/2E
PrdRptInterval
ShareCover
Share Cover Indication
MaxDlDpchPwr
DPCH Maximum DL Power
TrfCatInterMIdx(CInter)
Inter-frequency Measurement Configuration Index Related

to Traffic Category
TrfCatInterMIdx(utranCell)
InterMeasCfgNo
Inter-frequency Measurement Configuration Index
MeaEvtId[MAX_INTER_M
EAS_EVENT]
Inter-frequency Event Identity
TrfCategory
Service and Bearer Type Used for Differentiating

Handover Configuration
EvtMeasEcNo
UE Inter-frequency Event Measurement Configuration

EvtMeasRSCP
UE Inter-frequency Event Measurement Configuration

InterMeasCfgNote
MeasRptTrMod
UTRACarrierRSSI
UTRA Carrier RSSI
FreqQualEst
Carrier Frequency Quality Estimation Reporting Indicator
CellSynRptInd
Cell Synchronization Information Reporting Indicator
CIdRptInd
Cell ID Reporting Indicator
EcN0RptInd
RscpRptInd
PathlossRptInd
RptCrt
Report Criteria
MeasQuantity
MeasEvtNum
Event Number of Inter-frequency Measurement
StateMode

Configuration
ReadSFNInd
Read SFN Indicator
InterHoMth
Inter-frequency Handover Method
NonIntraMeasQuan
UTRAN Measurement Quantity for Inter-frequency and

Inter-RAT measurements
PrdMeasEcNo
UE Periodic Measurement Configuration Index for CPICH

Ec/No
PrdMeasRSCP
UE Periodic Measurement Configuration Index for CPICH

RSCP
106
PrdRptAmount
UseOfHCS(UtranRelation)
Use of HCS
PcpichPwrPre
12.2.2
12.2.2.1
Parameter name
Abbreviated name
MeasPrio
Description

neighboring cell. The highest priority is 0, the lowest priority is
2.
Range and Step
[0, 1, 2]
Unit
N/A
OMC Path

Parameter-> Measurement Priority of Neighboring Cell
The priority of a neighbouring cell can be set to 0, 1, and 2, of which, 0 represents the
highest priority and 2 represents the lowest priority. The priority of the neighbouring is
set by the configuration personnel according to the signal strength and the distance of
the neighboring cell.
12.2.2.2
Maximum Uplink SIR Target
Parameter name
Maximum Uplink SIR Target(dB)
Abbreviated name
ULMaxSIR
Description
This parameter indicates the maximum uplink target SIR, which

is used to give the range for the target SIR of the outer loop
power control.
Range and Step
[-8.2, 17.3]dB step 0.1
Unit
dB

Conversational
UL 3.4k Signaling(AM):15dB
107
Conversational
UL AMR6.60k~23.85k:15dB
Conversational
UL 64K(PS Conversational Video) 15dB
Conversational
UL NAMR4.75k~12.2k15dB
Streaming
PS64k15dB
Streaming
PS384k15dB
Streaming
PS128k15dB
Interactive
PS64k15dB
Interactive
PS384k15dB
Interactive
PS128k15dB
Background
PS64k15dB
Background
PS384k15dB
Background
PS128k15dB
Streaming
CS64k15dB
Interactive
UL PS 1024kbps:15dB
Interactive
UL PS 2.048Mbps:15dB
Interactive
UL PS 3. 072Mbps:15dB
Interactive
Interactive
UL PS 5.76Mbps:15dB
Background
UL PS 1024kbps:15dB
Background
Background
Background
Background
UL PS 5.76Mbps:15dB
Streaming
UL PS 1024kbps:15dB
Streaming
Streaming
Streaming
Streaming
UL PS 5.76Mbps:15dB
OMC Path

Management-> Modify Advanced Parameter->Power Control Related to Service and
Diversity Mode->Maximum Uplink SIR Target(dB)
This parameter indicates the maximum target signal-to-interference ratio (SIR) of the
uplink.
When the uplink SIR is already in the maximum threshold, if certain error packets are
still detected, the power control will become invalid because the SIR cannot be further
adjusted upwards. If the UL BLER switch for handover has been opened, the RNC will
initiate the compressed mode and the inter-frequency measurement.
108
12.2.2.3
UL BLER Switch for Handover
Parameter name
Abbreviated name
UlBlerHoSwch
Description
This parameter indicates the handover switch based on uplink

transmit power. When the switch is on, if uplink BLER quality
arrives at the threshold configured by OMCR, RNC will initiate
compressed mode and inter-frequency measurement.
Range and Step
0: Closed
1: Open
Unit
N/A
0: Closed
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>UL BLER Swich for Handover
This parameter indicates the handover switch based on uplink block error rate (BLER).
When the switch is on, if the uplink BLER arrives at the threshold, RNC will initiate
compressed mode and the inter-frequency measurement.
12.2.2.4
UL Tx Power Switch for Handover
Parameter name
UE Tx Power Switch for Handover
Abbreviated name
UlPwrHoSwch
Description

transmit power. When the switch is on, if uplink transmit power
compressed mode and inter-frequency or inter-RAT
measurement.
Range and Step
0: Closed
1: Open
Unit
N/A
0: Closed
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>UE Tx Power Switch for Handover
109
This parameter indicates the handover switch based on uplink transmit power. When the
switch is on, if the uplink transmit power arrives at the threshold, RNC will initiate the
compressed mode and the inter-frequency measurement.
12.2.2.5
DL Tx Power Switch for Handover
Parameter name
Abbreviated name
DlPwrHoSwch
Description
This parameter indicates the handover switch based on

downlink transmit power. When the switch is on, if downlink
transmit power arrives at the threshold configured by OMCR,
RNC will initiate compressed mode and inter-frequency
measurement.
Range and Step
0: Closed
1: Open
Unit
N/A
0: Closed
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->
This parameter indicates the handover switch based on downlink transmit power. When
the switch is on, if the downlink transmit power arrives at the threshold, RNC will initiate
the compressed mode and the inter-frequency measurement.
12.2.2.6
Use of HCSUtranCell
Parameter name
Use of HCS
Abbreviated name
UseOfHCS
Description
This parameter indicates whether the HCS is used or not.
Range and Step
1: Not Used
2: Used
Unit
N/A
1: Not Used
OMC Path
110

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Use of HCS
This parameter indicates whether the HCS function is used.
12.2.2.7
Use of HCSUtranRelation
Parameter name
Use of HCS
Abbreviated name
UseOfHCS
Description
Range and Step
1: Not Used
2: Used
Unit
N/A
1: Not Used
OMC Path
Interface Path: View-> Configuration Management->RNC NE->RNC Radio Resource

Management-> Utran Cell->Utran Cell XXX->Neighbouring Cell->Modify Advanced
Parameter->Use of HCS
12.2.2.8
HCS_PRIO(utranCell)
Parameter name
HCS_PRIO
Abbreviated name
HcsPrio
Description
This parameter indicates the HCS priority level (0-7) for the
utran cell. 7 is the highest priority, 0 is the lowest priority.
Range and Step
[0, 7]
Unit
N/A
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>HCS_PRIO
111
This parameter indicates the HCS priority level of the utran cell. 7 represents the highest
priority and 0 represents the lowest priority. A cell with a higher priority often provides a
smaller coverage and a cell with a lower priority offers a larger coverage.
12.2.2.9
HCS_PRIO(externalUtranCell)
Parameter name
HCS_PRIO
Abbreviated name
HcsPrio
Description
neighboring cells. 7 is the highest priority, 0 is the lowest
priority.
Range and Step
[0, 7]
Unit
N/A
OMC Path

Management->External Utran Cell->External Utran Cell XXX->Modify Advanced
Parameter->Utran Cell->HCS_PRIO
This parameter indicates the HCS priority level of the neighbouring cell. 7 represents the
highest priority and 0 represents the lowest priority. A cell with a higher priority often
provides a smaller coverage and a cell with a lower priority often offers a larger
coverage.
12.2.2.10
Tfast
Parameter name
Tfast(s)
Abbreviated name
Tfast
Description
If within the period of Tfast, the best cell has changed Nfast
times, the UE is juged to be in high speed state.
Range and Step
[0, 65535]s
Unit
300s
OMC Path
112

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Tfast(s)
This parameter indicates whether the UE is in the high-speed moving state in

combination with the parameter Nfast. If the best cell changes Nfast times within the
period specified by Tfast, the UE is judged to move in a high speed.
12.2.2.11
Nfast
Parameter name
Nfast
Abbreviated name
Nfast
Description
If within the period of Tfast, the best cell has changed Nfast
times, the UE is juged to be in high speed state.
Range and Step
[1, 255]
Unit
N/A
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Nfast
This parameter indicates whether the UE is in the high-speed moving state in

combination with the parameter Nfast. If the best cell changes Nfast times within the
period specified by Tfast, the UE is judged to move in a high speed.
12.2.2.12
Tslowjudge
Parameter name
Tslowjudge(s)
Abbreviated name
Tslowjudge
Description
This parameter indicates the period of the timer to judge that the
UE is moving at a low speed.
Range and Step
[0, 255]s
Unit
Default Value
(note)
100s
OMC Path
113

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Tslowjudge(s)
This parameter indicates the period of the timer to judge that the UE is moving at a low
speed. If the number of times that the UE changes its cell within the time specified by
Tslowjudge is less than NSlow and the difference between time when the best cell is
changed for the last time and the current time is more than Tslow, the UE is judged to
move in a low speed.
12.2.2.13
Tslow
Parameter name
Tslow(s)
Abbreviated name
Tslow
Description
This parameter indicates the minimum time interval between

Tslowjudge expiration and latest best cell changes.
Range and Step
[0, 65535]s
Unit
10s
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Tslow(s)
This parameter indicates the minimum time interval between the Tslowjudge expiration
and the last best cell change. See the description of the Tslowjudge parameter for its
functions.
12.2.2.14
Nslow
Parameter name
Nslow
Abbreviated name
Nslow
Description
This parameter indicates the maximum number of the best cell

changes within Tslowjudge.
Range and Step
[1, 255]
Unit
N/A
114
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Nslow
This parameter indicates the maximum number of best cell changes within the time
specified by Tslowjudge. See the description of the Tslowjudge parameter for its
functions.
12.2.2.15
Parameter name
Inter-frequence Handover Tactic
Abbreviated name
InterHoTactic
Description
This parameter indicates the inter-frequency handover tactic.
Range and Step
0: Algorithm Deciding
1: 2A Event Trigger
2: 2B Event Trigger
3: 2C Event Trigger
Unit
N/A
1: 2A Event Trigger
OMC Path

This parameter indicates the event that is used to trigger the inter-frequency handover.
The default value of the parameter is 2A, that is, the handover can be triggered when
the conditions for best carrier frequency change are satisfied.
12.2.2.16
Filter Coefficient(Inter)
Parameter name
Filter Coefficient
Abbreviated name
FilterCoeff
Description
This parameter indicates the filtering factor that UE performs

the L3 filtering on the measurement results of the interfrequency measurement.
UE executes inter-frequency measurement on L1 in the fixed
115
cycle (measure several points in one measurement cycle and

L1 filters the 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 TS25.
331: F = (1 a ) F + a M , a = 1/2(k/2) .
n
n 1

factor is, the larger effect the current measurement result will
have on the measurement result reported to RNC (periodical
report) or the judgment (event report).
Range and Step
(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19)
Unit
N/A
UE Period Report Parameters for CPICH Ec/No: 3

3
UE Period Report Parameters for CPICH RSCP: 3
3
OMC Path

Management->Modify Advanced Parameter->UE Inter-frequence Mesurement
Configuration-> Filter Coefficient
measurement results of the inter-frequency measurement. 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 (periodical report) or the judgment (event report).
12.2.2.17
Absolute Threshold of the Quality of the Currently Used Frequency for 2B/2D/2F
Parameter name
Absolute Threshold of the Quality of the Currently Used

Frequency for 2B/2D/2F
Abbreviated name
ThreshUsedFreq[MAX_INTER_MEAS_EVENT]
Description
This parameter indicates the absolute threshold that is required

to be configured for event 2b/2d/2f (used when judging the
quality of the currently used frequency.
116
MAX_INTEREAS_EVENT is the maximum number of interfrequecy measument event which is 6.

CPICH RSCP: [-115, -25] dBm
Range and Step
CPICH Ec/No: [-24, 0] dB

Pathloss: [30, 165] dB
Unit
dBm /dB
For CPICH Ec/No, UE periodic measurement report parameter:

For CPICH Ec/No, UE inter frequency event report parameter:
[-24,-13, -24,-13,-24,-5]dB
For CPICH RSCP, UE periodic measurement report parameter:
For CPICH RSCP, UE inter frequency event report parameter:
[-115,-95, -115,-95,-115,-70]dB
OMC Path

Configuration-> Absolute Threshold of the Quality of the Currently Used Frequency for 2B/2D/2F
This parameter indicates the absolute threshold that should be configured for event
2b/2d/2f (used when judging the quality of the currently used carrier frequency).
In the case of event 2B, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2D, the less the threshold configured, the more difficult the event 2D
been triggered.
In the case of event 2F, the less the threshold configured, the easier the event 2B been
triggered.
12.2.2.18
Parameter name
Abbreviated name
Wused[MAX_INTER_MEAS_EVENT]
Description
This parameter is used for quality judgment for the carrier of

currently used frequency, which indicates the weight of the
best cell in the quality judgment and is related to the
measurement quantity and the event type (only for event
2a/2b/2d/2f).
Range and Step
[0.0, 2.0]step 0.1
117
Unit
N/A
For CPICH Ec/No, UE periodic measurement report

parameter: For CPICH Ec/No, UE inter frequency event report parameter:
[0. 0, 0. 0, 0. 0,0. 0,0. 0,0. 0]
For CPICH RSCP, UE periodic measurement report
parameter: For CPICH RSCP, UE inter frequency event report parameter:
[0. 0, 0. 0, 0. 0,0. 0,0. 0,0. 0]
OMC Path

Configuration-> Weight of the Currently Used Frequency for 2A/2B/2D/2F
This parameter is used for quality judgment of the currently used carrier frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)
12.2.2.19
Parameter name
Abbreviated
name
PrdRptAmount
Description

Range and Step
[1, 2, 4, 8, 16, 32, 64, Infinity]
Unit
N/A
Default Value
(note)

Infinity
For CPICH Ec/No, UE inter frequency event report parameter: For CPICH RSCP, UE periodic measurement report parameter:
Infinity
For CPICH RSCP, UE inter frequency event report parameter: -
OMC Path

Configuration-> Amount of Reporting in Period Report Criteria
This parameter indicates the times of the periodical reports to be reported. In the case of
the UE side, the value is used for the determination of whether to report the
118
measurement report in reporting the periodical report. If the UE detects that the times of
event reporting exceeds the value of Amount of reporting, UE stops reporting the
12.2.2.20
Hysteresis(Inter)
Parameter name
Hysteresis(dB)
Abbreviated name
Hysteresis[MAX_INTER_MEAS_EVENT]
Description

small change. Different events are configured separately and
can be configured with different values.
Range and Step
(0, ,14.5)dB step 0.5dB
Unit
dB

[4,4,4,4,4,4]dB
[4,4,4,4,4,4]dB
OMC Path

Configuration-> Hysteresis
This parameter indicates the hysteresis used when judging whether to trigger the event.
This parameter avoids the trigger status change due to very small change. Different
events are configured separately and the events can be configured with different values.
If a small hysteresis is configured, the corresponding event will be reported in a higher
probability; and vice versa.
12.2.2.21
Time to Trigger(Inter)
Parameter name
Time To Trigger(ms)
119
Abbreviated name
TrigTime[MAX_INTER_MEAS_EVENT]
Description

requirements of event triggering after Time to trigger, the
event can be triggered and reported. The larger the value is,
the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual
requirements. Sometimes, if it is set too large, the quality of
calls may decrease.
Range and Step
(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320,
640, 1280, 2560, 5000)ms
Unit
Ms

parameter: For CPICH Ec/No, UE inter frequency event report
parameter: [100,100,100,640,100,640]
[100,100,100,640,100,640]
OMC Path
Path:View->Configuration
Management->RNC
NE->RNC
Radio
Resource
Configuration-> Time to Trigger
is detected and the time that the event is reported. The event is triggered and the
measurement report is reported only when the event generation is detected and still
meets the requirements of event triggering after Time to trigger.
12.2.2.22
Absolute Threshold of the Quality of the Non-used Frequency for 2B/2C/2E
Parameter name
Absolute Threshold of the Quality of the Non-used Frequency

for 2B/2C/2E
Abbreviated name
ThreshNoUsedFreq[MAX_INTER_MEAS_EVENT]
Description
This parameter indicates the absolute threshold that is

required to be configured for event 2a/2b/2c/2e (used when
judging the quality of the noT used frequency).
120

CPICH RSCP: [-115, 25]dBm step 1dBm
Range and Step
CPICH Ec/No: [-24, 0]dB step 1dB

Unit
dBm /dB

[-24,-5,-5,-24,-13,-24]dB
[-115,-50,-50,-115,-95,-115]dBm
OMC Path

Configuration->Absolute Threshold of the Quality of the Non-used Frequency for
2B/2C/2E
This parameter indicates the absolute threshold that should be configured for event
2b/2c/2e (used when judging the quality of the non-used frequency).
In the case of event 2b, the less the threshold configured, the more difficult the event 2B
been triggered.
In the case of event 2c, the larger the threshold configured, the more difficult the event
2c been triggered.
In the case of event 2E, the larger the threshold configured, the easier the event 2E
been triggered.
12.2.2.23
Parameter name
Abbreviated name
WNoUsed[MAX_INTER_MEAS_EVENT]
Description
This parameter is used when judging the quality of the cells of

not used frequencies. This parameter indicates the weight of
the best cell in the quality judgment (only for event
2a/2b/2c/2e).
Range and Step
[0.0, 2.0] step 0.1
Unit
N/A
121

[0. 0, 0. 0, 0. 0,0. 0,0. 0,0. 0]
For CPICH RSCP, UE inter frequency event report parameter:
[0. 0, 0. 0, 0. 0,0. 0,0. 0,0. 0]
OMC Path

Configuration->Weight of the Non-used Frequency for 2A/2B/2C/2E
This parameter is used for quality judgment of the currently non-used frequency. It
indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2c/2e)
12.2.2.24
Parameter name
Abbreviated name
PrdRptInterval
Description
This parameter indicates the interval of periodical reporting

when such reporting is triggered periodically. For periodic
report, UE report measurement result according to this
parameter indicated periodic.
Range and Step
(250, 500, 1000, 2000, 3000, 4000, 6000, 8000, 12000,

16000, 20000, 24000, 28000, 32000, 64000)ms
Unit
Ms

parameter: 1s
500ms
For CPICH RSCP, UE inter frequency event report parameter: -
OMC Path

Configuration->Reporting Interval in Period Report Criteria(ms)
122
This parameter indicates the interval of periodical reporting specified in the periodical
reporting criteria. In the case of the periodical report, the UE reports the inter-frequency
measurement results in the period indicated by the parameter.
12.2.2.25
Parameter name
Abbreviated name
ShareCover
Description
This parameter describes the neighboring relationship of the

serving cell and neighboring cell.
Range and Step
0: Neighbor
1: Overlap
2: Covers
3: Contained in
Unit
N/A
0: Neighbor
OMC Path

Parameter->Share Cover Indication
This parameter describes the neighboring relationship of the current cell and the
neighboring cell. The relationship between the neighbouring cell and the current cell
may be Neighbor, Overlap, Covers, or Contained in.
12.2.2.26
Parameter name
Abbreviated name
MaxDlDpchPwr
Description
This parameter indicates the maximum downlink DPCH

transmission power. When performing the downlink inner loop
power control, the new transmission power must be smaller than
or equal to the configured DPCH Maximum DL Power. If the newly
computed transmission power is larger than the configured DPCH
Maximum DL Power, make it equal to the configured DPCH
Maximum DL Power.
Range and Step
(-35..15 ) dB step 0.1 dB
Unit
dB
Default Value
(note)
Conversational DL 3.4k Signaling(AM)::0 dB
123
Conversational DL WAMR6.60k~23.85k :0dB

Conversational DL 64K(PS Conversational Video):3dB
Conversational DL NAMR4.75k~12.2k:0dB
Streaming
PS64k:1dB
Streaming
PS384k:4dB
Streaming
PS128k:2dB
Interactive
PS64k:1dB
Interactive
PS384k:4dB
Interactive
PS128k:2dB
Background
PS64k:1dB
Background
PS384k:4dB
Background
PS128k:2dB
Streaming
CS64k:3dB
Interactive
DL PS 1.2Mbps:4dB
Interactive
DL PS 3.65Mbps:4dB
Interactive
DL PS 7.2Mbps:4dB
Interactive
DL PS 10.1Mbps:4dB
Interactive
DL PS 14.0Mbps:4dB
Background
DL PS 1.2Mbps:4dB
Background
DL PS 3.65Mbps:4dB
Background
DL PS 7.2Mbps:4dB
Background
DL PS 10.1Mbps:4dB
Background
DL PS 14.0Mbps:4dB
Streaming
DL PS 1.2Mbps:4dB
Streaming
DL PS 3.65Mbps:4dB
Streaming
DL PS 7.2Mbps:4dB
Streaming
DL PS 10.1Mbps:4dB
Streaming
DL PS 14.0Mbps:4dB
OMC Path

Management-> Modify Advanced Parameter->Power Control Related to Service and
Diversity Mode->DPCH Maximum DL Power
This parameter indicates the maximum downlink transmit power of DPCH.

When the downlink inner loop power control is performed, the new transmit power must
be smaller than or equal to the configured DPCH Maximum DL Power.
If the DL Tx Power Switch for Handover (DlPwrHoSwch) is open, the RNC judges the
downlink code power (DTCP) in the dedicated measurement report of the NodeB. That
124
is, when the DTCP arrives at a certain threshold, the inter-frequency handover is
triggered.
12.2.2.27
Inter-frequency Measurement Configuration Index Related to Traffic Category

CInter
Parameter name
Inter-frequency Measurement Configuration Index Related to

Traffic Category
Abbreviated name
TrfCatInterMIdx
Description
This parameter indicates the configuration index of the interfrequency measurement parameters based on traffic type.
Range and Step
0..65535
Unit
N/A
OMC Path

Management-> Modify Advanced Parameter-> UE Inter-frequency Measurement
Relative to Traffic Category Configuration Information -> Inter-frequency Measurement
Configuration Index Related to Traffic Category
This parameter indicates the index of the inter-frequency measurement configuration

based on traffic type. Each traffic type corresponds to a unique inter-frequency
configuration. If multiple sets of handover parameters are configured, each cell should
use a different index. Hence, the inter-frequency handover parameters of the cells may
be different.
12.2.2.28

UtranCell
Parameter name
Inter-frequency Measurement Configuration Index Related to

Traffic Category
Abbreviated name
TrfCatInterMIdx
Description
This parameter indicates the configuration index of the interfrequency measurement parameters based on traffic type.
Range and Step
0..65535
Unit
N/A
125
OMC Path

This parameter indicates the index of the inter-frequency measurement configuration

based on traffic type. Each traffic type corresponds to a unique inter-frequency
configuration. If multiple sets of handover parameters are configured, each cell should
use a different index. Hence, the inter-frequency handover parameters of the cells may
be different.
12.2.2.29
Parameter name
Abbreviated name
InterMeasCfgNo
Description
This parameter indicates the configuration index of the interfrequency measurement parameters, which is used to index
different parameter configuration sets for inter-frequency
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.
Range and Step
0..65535
Unit
N/A
There are 4 sets of measurement parameter are configured for

different measurement purpose, theDefault Values of intrafrequency measurement configuration index are 0, 3, 4, 7
respectively:
0: UE Period Report Parameters for CPICH Ec/No
3: UE Inter-frequency Event Report Parameters for CPICH
Ec/No
4: UE Period Report Parameters for CPICH RSCP
RSCP
OMC Path

Management-> Modify Advanced Parameter->UE Inter-frquence Measurement
Configuration-> Inter-frequency Measurement Configuration Index
Each inter-frequency measurement configuration with different measurement purpose

and measurement quantity is assigned with a unique inter-frequency measurement
126
configuration index. This parameter indicates the index of the inter-frequency

measurement configuration. This configuration index is cited in the table Inter-frequency
measurement configuration relationship of the service type-related UE.
That is, the parameter Inter-frequency Measurement Configuration Index Related to
Traffic Category (namely TrfCatIntraMIdx) is cited in the advanced parameters of the
serving cell and different Inter-frequency Measurement Configuration Indexes
(namely IntraMeasCfgNo) can be selected aiming at the specific service type,
measurement objective, and measurement quantity. This parameter can be used to
meet various requirements of network planning.
12.2.2.30
Parameter name
Abbreviated name
MeaEvtId[MAX_INTER_MEAS_EVENT]
Description
This parameter indicates the event triggered by the interfrequency measurement, which is related to the measurement
quantity.
MAX_INTER_MEAS_EVENT indicates the maximum number
of inter-frequency measurement event, which is 6.
Range and Step
[2a,2b,2c,2d,2e,2f]
Unit
N/A

[2a,2b,2c,2d,2e,2f]
[2a,2b,2c,2d,2e,2f]
OMC Path

Configuration-> Inter-frequency event identity
This parameter indicates the identify of the event triggered by the inter-frequency
measurement (2a~2f).
12.2.2.31
Parameter name

Configuration
127
Abbreviated name
TrfCategory
Description
This parameter differentiates different sets of handover

parameter according to different service and bearer type. For
different services, there are different parameters such as
handover trigger threshold, hysteresis, etc. Altogether there are
8 sets of configuration for different scenario based on service
type, transport channel type, service quantity, etc.
Range and Step
0:Single RT RAB Including Voice on DL DCH/UL DCH

1:Single RT RAB Excluding Voice on DL DCH/UL DCH
2:Single NRT on DL DCH/UL DCH
3:Single RAB on DL HS-DSCH/UL DCH
4:Single RAB on DL HS-DSCH/UL E-DCH
5:All Multi-RAB on DL DCH/UL DCH
6:Multi-RAB, HSPA is Involved and only DCHs are Used in UL
7:Multi-RAB, HSPA is Involved and E-DCH is Used in UL
Unit
N/A
Default Value
(note)
See Table 4
OMC Path

Management-> Modify Advanced Parameter->UE Inter-frequency Measurement
Relative to Traffic Category Configuration Information->Service and Bearer Type Used
for Differentiating Handover Configuration
services, channel type, and service quantity. This parameter indicates the service and
bearer type. The handover parameters can be configured flexibly for different scenarios
and the parameters may have different handover trigger thresholds and hysteresis.
The value 0xff (Not Related to Service Type) is exclusively used in the measurement of
the detected set.
TrfCatInterMId
x
128
Default Value 9
Default Value 8
Default Value 7
Default Value 6
Default Value 5
Default Value 4
Default Value 3
Default Value 2
Default Value 1
Field Name
Table 8
Service Type Related UE Inter-frequency Measurement Parameter
ConfigurationDefault Value
12.2.2.32
TrfCategory
0xff
PrdMeasEcNo
EvtMeasEcNo
PrdMeasRSCP
EvtMeasRSCP
UE Inter-frequency Event Measurement Configuration Index for CPICH Ec/No

Table 9
Parameter name
UE Inter-frequency Event Measurement Configuration Index

for CPICH Ec/No
Abbreviated name
EvtMeasEcNo
Description
This parameter indicates the UE event report configuration

index for CPICH Ec/No, used for indexing the configuration of
the set of intra-frequency measurement parameters for event
reporting decided by UE when measurement quantity is
CPICH Ec/No.
Range and Step
0.65535
Unit
N/A
See Table 4
OMC Path

Relative to Traffic Category Configuration Information->UE Inter-frequency Event
Measurement Configuration Index for CPICH Ec/No
This parameter indicates the index of the inter-frequency measurement configuration for
event reporting judgment by the UE when the measurement quantity is CPICH Ec/No.
12.2.2.33
UE Inter-frequency Event Measurement Configuration Index for CPICH RSCP
Parameter name
UE Inter-frequency Event Measurement Configuration Index

for CPICH RSCP
Abbreviated name
EvtMeasRSCP
Description
This parameter indicates the Inter-frequency report

configuration index for CPICH RSCP, used for indexing the
configuration of the set of inter-frequency measurement
parameters for event reporting when measurement quantity is
CPICH RSCP.
Range and Step
[0,65535]
129
Unit
N/A
See Table 4
OMC Path

Relative to Traffic Category Configuration Information->UE Inter-frequency Event
Measurement Configuration Index for CPICH RSCP
This parameter indicates the index of the inter-frequency measurement configuration in

event reporting judgment by the UE when the measurement quantity is CPICH RSCP.
12.2.2.34
Parameter name
Abbreviated
name
PrdMeasEcNo
Description
This parameter indicates the UE period report inter-frequency

measurement configuration index for CPICH Ec/No, used for
indexing the configuration of the set of inter-frequency
measurement parameters for UE periodical reporting when
measurement quantity is CPICH Ec/No.
Range and Step
0.65535
Unit
N/A
Default Value
(note)
See Table 5
OMC Path

Relative to Traffic Category Configuration Information-> Period Report Configuration
12.2.2.35
Parameter name
Abbreviated
name
PrdMeasRSCP
Description

CPICH RSCP, used for indexing the configuration of the set of
inter-frequency measurement parameters for periodical reporting
130
when measurement quantity is CPICH RSCP

Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 5
OMC Path

12.2.2.36
Parameter name
Abbreviated name
InterMeasCfgNote
Description
This parameter indicates the purpose and functions of the set

of inter-frequency measurement configuration parameters.
Range and Step

Ec/No
RSCP
Unit
N/A
There are 4 sets of measurement parameter are configured

for different measurement purpose, theDefault Values of intrafrequency measurement configuration index are 0, 3, 4, 7
respectively.
Ec/No
RSCP
OMC Path

Configuration-> Function of Configuration Parameters
131
This parameter indicates the purpose and functions of the set of inter-frequency
12.2.2.37
Parameter name
Abbreviated name
MeasRptTrMod
Description

Range and Step
0: Acknowledged mode RLC

1: Unacknowledged mode RLC
Unit
N/A
Default Value
(note)

Mode RLC
Mode RLC
OMC Path

Configuration-> Measurement Report Transfer Mode
12.2.2.38
UTRA Carrier RSSI
Parameter name
UTRA Carrier RSSI
Abbreviated name
UTRACarrierRSSI
Description
This parameter indicates whether the report of the UTRA
132
Carrier RSSI is requested or not. This parameter is valid to the

cells no matter of currently used frequency or of non-used
frequencies.
0: Not Report (False)
Range and Step
1: Report (True)
Unit
N/A
UE Period Report Parameters for CPICH Ec/No: False

False
UE Period Report Parameters for CPICH RSCP: False
False
OMC Path

Configuration-> UTRA Carrier RSSI
This parameter indicates whether to report the UTRA Carrier RSSI.
12.2.2.39
Parameter name
Abbreviated name
FreqQualEst
Description
This parameter indicates whether the report of carrier quality

estimation value is requested. This parameter is valid to the
cells no matter of currently used frequency or of non-used
frequencies.
Range and Step

1: Report (True)
Unit
N/A

False
False
OMC Path
133

Configuration-> Carrier Frequency Quality Estimation Reporting Indicator
This parameter indicates whether to report the carrier frequency quality estimation value.
12.2.2.40
Parameter name
Abbreviated name
CellSynRptInd
Description
This parameter indicates whether the report of the

synchronization information of the neighboring cells is
requested or not. This parameter is only valid to the cells of
non-used frequencies.
Range and Step

1: Report (True)
Unit
N/A
Default Value
(note)

False
False
OMC Path

Configuration->Cell Synchronization Information Reporting Indicator
This parameter indicates whether to report the cell synchronization information in the
inter-frequency measurement.
12.2.2.41
Parameter name
Abbreviated name
CIdRptInd
Description
This parameter indicates the inter-frequency cell identity when

reporting the measurement results. This parameter is only valid
to the cells of non-used frequencies.
134
Range and Step
1: Report (True)
Unit
N/A

False
False
OMC Path

Configuration->Cell ID Reporting Indicator
This parameter indicates whether to report the cell identity in the inter-frequency
measurement.
12.2.2.42
Parameter name
Abbreviated name
EcN0RptInd
Description
This parameter indicates whether the report of the CPICH

Ec/No is requested or not. This parameter is only valid to the
cells of non-used frequencies.
Range and Step

1: Report (True)
Unit
N/A
UE Period Report Parameters for CPICH Ec/No: True

UE Inter-frequency Event Report Parameters for CPICH
Ec/No: True
UE Period Report Parameters for CPICH RSCP: True
RSCP: True
OMC Path

Configuration-> CPICH Ec/No Reporting Indicator
135
This parameter indicates whether the UE should report the measurement results whose
measurement quantity is CPICH Ec/No.
set to 0, the parameter EcN0RptInd must be set to TRUE.
12.2.2.43
Parameter name
Abbreviated name
RscpRptInd
Description

RSCP is requested or not. This parameter is only valid to the
Range and Step

1: Report (True)
Unit
N/A
Default Value
(note)
UE Period Report Parameters for CPICH Ec/No: True

True
UE Period Report Parameters for CPICH RSCP: True
True
OMC Path

Configuration-> CPICH RSCP Reporting Indicator
measurement quantity is CPICH RSCP.
set to 1, the parameter RscpRptInd must be set to TRUE.
12.2.2.44
Parameter name
Abbreviated name
PathlossRptInd
Description

Ec/No is requested or not. This parameter is only valid to the
136
Range and Step
1: Report (True)
Unit
N/A

Ec/No: False
RSCP: False
OMC Path

Configuration-> Pathloss reporting indicator
measurement quantity is pathloss.
12.2.2.45
Report Criteria
Parameter name
Report Criteria
Abbreviated name
RptCrt
Description
This parameter indicates the report criteria of the interfrequency measurement.

When a different report criteria is selected, parameters for this
measurement purpose is configured differently.
When Periodical Reporting Criteria is selected, two sets of the
measurement parameters are required to be configured. One
set of the periodical parameters are configured to UE and the
other set of inter-frequency event parameters are configured to
SRNC for event judgment. Having received the periodical
measurement reports from UE, SRNC judges which event is
triggered according to the event criteria parameters and then
decides whether to perform the inter-frequency handover
according to the event.
When Intra-frequency Event Reporting Criteria is selected, a
set of parameters of the corresponding intra-frequency
measurement configuration ID are configured to UE.
When the value is Inter-frequency Event Reporting Criteria ,
the set of parameters of the corresponding inter-frequency
measurement configuration ID are configured to UE.
Range and Step
1: Intra-frequency Event Reporting Criteria

2: Inter-frequency Event Reporting Criteria
137
3: Periodical Reporting Criteria

Unit
N/A
UE Period Report Parameters for CPICH Ec/No: Periodical

Reporting Criteria
Inter-frequency Event Reporting Criteria
UE Period Report Parameters for CPICH RSCP: Periodical
Reporting Criteria
Inter-frequency Event Reporting Criteria
OMC Path

Configuration-> Report Criteria
This parameter indicates the criteria of reporting the inter-frequency measurement,

including the Event Reporting and periodical reporting.
12.2.2.46
Parameter name
Abbreviated name
MeasQuantity
Description
This parameter indicates the measurement quantity of the

intra-frequency measurement that UE performs.
Range and Step
0: CPICH Ec/No
1: CPICH RSCP
Unit
N/A
Period Report Parameters for CPICH Ec/No: CPICH Ec/No

UE Event Report Parameters for CPICH Ec/No: CPICH Ec/No
Period Report Parameters for CPICH RSCP : CPICH RSCP
UE Event Report Parameters for CPICH RSCP: CPICH RSCP
CPICH Ec/No
CPICH RSCP
OMC Path

Configuration-> Measurement quantity
138
This parameter indicates the measurement quantity of the inter-frequency measurement

that UE performs. After a new inter-frequency measurement configuration index is
added, the measurement quantity is fixed if the function of the set of the inter-frequency
InterMeasCfgNote is set to UE Inter-frequency Event Report Parameters for CPICH
RSCP, the value of MeasQuantity is automatically set to the corresponding CPICH
RSCP.
12.2.2.47
Parameter name
Abbreviated name
MeasEvtNum
Description
This parameter indicates number of event to be configured in

intra frequency measurement configuration code for certain
function. It defines event quantity is related to the function or
soft handover judgment.
Range and Step
[1,MAX_INTER_MEAS_EVENT]
in which,MAX_INTER_MEAS_EVENT =6.
Unit
N/A
Default Value
(note)

For CPICH Ec/No, UE inter frequency event report parameter: 6
For CPICH RSCP, UE inter frequency event report parameter: 6
OMC Path

Configuration-> Event Number of Inter-frequency Measurement
This parameter indicates the number of events that should be configured for the index of
the inter-frequency measurement configuration for a certain purpose.
12.2.2.48
UE State Indicator Used for UTRAN Neighboring Cell Configuration
Parameter name

Configuration
Abbreviated name
StateMode
Description
This parameter indicates the status of the neighboring cell.
139
When the measurement control message is to be sent, the
cells that support DCH status are selected from the
neighboring cells list and are filled in the measurement control
message.
0: Idle State Only
Range and Step

Unit
N/A
OMC Path

Parameter->UE State Indicator Used for UTRAN Neighboring Cell Configuration
This parameter indicates the UE status applied to the neighboring cell. When the
neighbouring cell is configured by status, the neighbouring cells list used for reselection
in nondedicated mode and the neighbouring cells list for handover in dedicated mode
are differentiated as follows:
connected Non-Cell_DCH state from the neighboring cells list and fills in SIB11.
When SIB12 is to be sent, the cells that support the connected Non-Cell_DCH state
are selected from the neighboring cells list and are filled in SIB12;
When the measurement control message is to be sent, the cells that support the
Cell_DCH state are selected from the neighboring cells list.
12.2.2.49
Read SFN Indicator
Parameter name
Read SFN Indicator
Abbreviated name
ReadSFNInd
140
Description
This parameter indicates whether to read the SFN of the target

cell.
Range and Step
0: False
1: True
Unit
N/A
Default Value
(note)
1: True
OMC Path

Management-> Utran Cell->Utran Cell XXX->Neighbouring Cell->Modify Advanced
Parameter->Read SFN Indicator
This parameter indicates whether to read the SFN of the neighbouring cell.
Generally, the parameter is set to True for intra-frequency neighbouring cells and False
for inter-frequency neighbouring cells.
12.2.2.50
Parameter name
Abbreviated name
InterHoMth
Description
This paramerer indicates the inter handover method is

Range and Step
0: Periodical method
1: Event method
Unit
N/A
1: Event method
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Inter-frequency Handover Method
The parameter indicates the inter-frequency handover method (periodical method or

event method) that should be used in the current cell. The event method is
recommended.
141
12.2.2.51
UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements
Parameter name
UTRAN Measurement Quantity for Inter-frequency and InterRAT measurements
Abbreviated name
NonIntraMeasQuan
Description

inter-frequency and inter-RAT measurements.
Range and Step
0: Ec/No
1: RSCP
2: Ec/No and RSCP
Unit
N/A
1: RSCP
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements
This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for the
inter-frequency and inter-RAT measurements. The measurement quantity RSCP is
recommended.
12.2.2.52
Parameter name
Abbreviated
name
PcpichPwrPre
Description
This parameter indicates whether PCPICH transmission power is

configured.
PCPICH transmission power is valid when this parameter is set
True. Otherwise, PCPICH transmission power is invalid.
Range and Step
0: False
Unit
N/A
Default Value
(note)
1: True
1: True
OMC Path
Interface Path: View-> View->Configuration Management->RNC ME->RNC Radio

Resource Management->External Utran Cell-> External Utran CellXX-> Modify
Advanced Parameter-> Primary CPICH Power Configuration Tag
142
This parameter indicates whether PCPICH transmission power is configured.

PCPICH transmission power is valid when this parameter is set True. Otherwise,
PCPICH transmission power is invalid.
12.3
SRNC Relocation Parameters
12.3.1
Parameter List
Parameter Field Name
Trelocprep
SRNC Wait Time for Relocation Preparation (100ms)
Trelocoverall
SRNC Overall Protective Time for Relocation (100ms)
RtReDelayTimer
Timer of Relocation Delay for RT Service
NrtReDelayTimer
Timer of Relocation Delay for NRT Service
12.3.2
12.3.2.1
Trelocprep
Parameter name
SRNC Wait Time for Relocation Preparation (100ms)
Abbreviated name
Trelocprep
Specifies the maximum time for Relocation Preparation
procedure in the source RNC.
When the source RNC sends the RELOCATION REQUIRED
message, it shall start the timer Trelocprep.
Description
Upon reception of the RELOCATION COMMAND message the

source RNC shall stop the timer Trelocprep, and terminate 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 shall cancel the Relocation
Preparation procedure by initiating the Relocation Cancel
procedure with the appropriate value for the Cause IE, e. g.
"Trelocprep expiry".
Range and Step
[1, 300]
Unit
100ms
Default Value
(note)
50
OMC Path
143
Interface Path: view->Configuration Management->RNC NE->RNC Radio Resource

Management->Modify Advanced Parameter->Iu Timer and Constant->Trelocprep
This parameter specifies the maximum time for Relocation Preparation procedure in the
source RNC after the SRNC successfully sends the RELOCATION REQUIRED
message to the CN. If the SRNC fails to receive the RELOCATION COMMAND
message within the time specified by the parameter, the timer is judged as expiry and
the relocation is canceled.
12.3.2.2
Trelocoverall
Parameter name
SRNC Overall Protective Time for Relocation (100ms)
Abbreviated name
Trelocoverall
Specifies the maximum time for the protection of overall
Relocation procedure in the source RNC.
Description
Upon reception of the RELOCATION COMMAND message the

source RNC shall stop the timer Trelocprep, start the timer
Trelocoverall and terminate the Relocation Preparation
procedure.
If the Iu Release procedure is not initiated towards the source
RNC from the CN before the expiry of timer Trelocoverall, the
source RNC should initiate the Iu Release Request procedure
towards the CN with a cause value "Trelocoverall expiry".
Range and Step
[1, 300] step: 1
Unit
100ms
Default Value
(note)
50
OMC Path

Management->Modify Advanced Parameter->Iu Timer and Constant->Trelocoverall
This parameter specifies the maximum time for the initiation of the Iu release by the CN
after the SRNC receives the RELOCATION COMMAND message. If the CN fails to
initate the Iu release within the time specified by the parameter, the timer is judged as
expiry and the SRNC initiates the Iu release instead.
12.3.2.3
RtReDelayTimer
Parameter name
Timer of Relocation Delay for RT Service
144
Abbreviated name
RtReDelayTimer
Description
This parameter indicates the timer length of relocation delay for

realtime service.
Range and Step
0. 65535, where 0 meas no delay.
Unit
100ms
300
OMC Path

Management->Modify Advanced Parameter->RNC Radio Resource Management>RtReDelayTimer
This parameter is applicable to realtime services. It indicates the delay of initiating the
relocation procedure after the link at the S side is deleted.
12.3.2.4
NrtReDelayTimer
Parameter name
Timer of Relocation Delay for NRT Service
Abbreviated name
NrtReDelayTimer
Description
This parameter indicates the timer length of relocation delay for

nonrealtime service.
0. 65535, where 0 meas no delay.
Range and Step
Unit: 100ms
Unit
Ms
OMC Path

Management->Modify Advanced Parameter->RNC Radio Resource Management>NrtReDelayTimer
This parameter is applicable to nonrealtime services. It indicates the delay of initiating

the relocation procedure after the link at the S side is deleted.
145
12.4
Inter-RAT Handover Parameters
12.4.1
Parameter List
Field Name
MeasPrio
Measurement Priority of Neighboring GSM Cell
RatHoTactic
Inter-Rat Handover Tactic
UlBlerHoSwch
UL BLER Switch for handover
DlPwrHoSwch
UlPwrHoSwch
Thresh[MAX_RAT_MEAS_EVE
NT]
Absolute Threshold of the Quality of UTRAN Cell

for 3A
W[MAX_RAT_MEAS_EVENT]
Weight of the UTRAN System for 3A
ThreshSys[MAX_RAT_MEAS_E
VENT]
Absolute Threshold of the Quality of Other RAT for

3A/3B/3C
Hysteresis[MAX_RAT_MEAS_E
VENT]
Hysteresis
TrigTime[MAX_RAT_MEAS_EV
ENT]
Time to Trigger
TrfCatRatMIdx(CRat)
Inter-RAT Measurement Configuration Index

Related to Traffic Category
TrfCatRatMIdx(utranCell)
TrfCategory
Service and Bearer Type Used for Differentiating

Handover Configuration
EvtMeasRSCP
UE Event Report Configuration Index for Own

System CPICH RSCP
InterRatCfgNo
InterRatCfgNote
MeasRptTrMod
FilterCoeff(Rat)
UTRAN Filter Coefficient(Rat)
OwnMeasQuantity
UTRAN Measurement quantity
GsmFilterCoeff
GSM Filter Coefficient(Rat)
BSICVeriReq
GSM BSIC Verification Required Indicatior
UtranEstQual
UTRAN Quality Estimation Reporting Indicator
GsmCarrRSSIInd
GSM Carrier RSSI Reporting Indicator
RptCrt
Report Criteria
EventNum
Inter-RAT Measurement Event Number
EventId
[MAX_RAT_MEAS_EVENT]
Inter-RAT Event Identity
CellIndivOffset(gsmRelation)
Cell individual offset(gsmRelation)
GsmStateMode
UE State Indicator Used for GSM Neighboring Cell

Configuration
146
GsmShareCover
NonIntraMeasQuan
UTRAN Measurement Quantity for Inter-frequency

and Inter-RAT Measurements
EvtMeasEcNo
UE Event Report Configuration Index for Own

System CPICH Ec/No
IntRatHoMth
Inter-RAT Handover Method
PrdRptInterval
Periodical Report Configuration Index for Own

System CPICH Ec/No
PrdRptAmount
Periodical Report Configuration Index for Own

System CPICH RSCP
PrdMeasEcNo
PrdMeasRSCP
UseOfHCS(gsmRelation)
Use of HCS
HcsPrio (gsmRelation)
HCS_PRIO
12.4.2
12.4.2.1
Parameter name
Abbreviated name
MeasPrio
Description

neighboring cell. The highest priority is 0, the lowest priority is
2.
Range and Step
[0, 2]
Unit
N/A
OMC Path

Management->Utran Cell->Utran Cell XXX->GSM Neighbouring Cell->Modify Advanced
Parameter-> Measurement Priority of Neighboring GSMCell
This parameter indicates the measurement priority of the neighboring cell. 0 presents
the highest priority and 2 presents the lowest priority. This parameter should be
configured by the network planning engineer according to the actual conditions of the
current network, including the quality and geographic position of the inter-RAT
neighbouring cell.
147
12.4.2.2
Parameter name
Abbreviated name
RatHoTactic
Description
This parameter indicates the inter-RAT handover tactic.
Range and Step
0: Algorithm Deciding
1: 3A Event Trigger
2: 3C Event Trigger
Unit
N/A
1: 3A Event Trigger
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Inter-RAT Handover Tactic
This parameter indicates the measurement event type (3A or 3C) that is used to trigger
the inter-RAT handover.
Event 3C can be triggered when the quality of the inter-RAT carrier frequency signal is
higher than a certain value. In contrast, the trigger of event 3A requires an additional
condition, that is, the quality of the carrier frequency signal of the current RAT must be
less than a certain value. Hence, the inter-RAT handover can be triggered more easily
when the parameter is set to 3C Event Trigger.
12.4.2.3
Parameter name
Abbreviated name
UlBlerHoSwch
Description

transmit power. When the switch is on, if uplink BLER quality
compressed mode and inter-frequency measurement.
Range and Step
0: Closed
1: Open
Unit
N/A
0: Closed
OMC Path
148

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>UL BLER Swich for Handover
This parameter indicates the handover switch based on uplink BLER. When the switch
is on, the RNC will initiate compressed mode and inter-RAT measurement if the uplink
BLER quality arrives at the threshold.
12.4.2.4
Parameter name
Abbreviated name
DlPwrHoSwch
Description
This parameter indicates the handover switch based on

downlink transmit power. When the switch is on, if downlink
transmit power arrives at the threshold configured by OMCR,
RNC will initiate compressed mode and inter-frequency
measurement.
Range and Step
0: Closed
1: Open
Unit
N/A
0: Closed
OMC Path

This parameter indicates the handover switch based on downlink transmit power. When
the switch is on, the RNC will initiate compressed mode and inter-RAT measurement if
the downlink transmit power arrives at the threshold.
12.4.2.5
Parameter name
Abbreviated name
UlPwrHoSwch
Description

transmit power. When the switch is on, if uplink transmit power
compressed mode and inter-frequency or inter-RAT
measurement.
149
0: Closed
Range and Step
1: Open
Unit
N/A
0: Closed
OMC Path

This parameter indicates the handover switch based on uplink transmit power. When the
switch is on, the RNC will initiate compressed mode and inter-RAT measurement if the
uplink transmit power arrives at the threshold.
12.4.2.6
Absolute Threshold of the Quality of UTRAN Cell for 3A
Parameter name
Absolute Threshold of the Quality of UTRAN Cell for 3A
Abbreviated name
Thresh[MAX_RAT_MEAS_EVENT]
Description
This parameter indicates the absolute threshold of the UTRAN

cell quality that UE uses to judge event 3a. The range and Unit
of the parameter relate to the measurement quantity of UTRAN
system.
MAX_RAT_MEAS_EVENT is the maximum number of inter-RAT
measurement events which takes the value of 4.
Range and Step
CPICH RSCP:[-115, -25] dBm step 1dBm

CPICH Ec/No: [-24, 0] dB step 1dB
Unit
dBm/ dB
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: For own system CPICH Ec/No, UE event report parameter: [-6, 24,-24,-24]
For own system CPICH RSCP, periodic report parameter: For own system CPICH RSCP, UE event report parameter: [-95,
-115,-115,-115]
OMC Path

Management->
Modify
Advanced
Parameter->UE
Inter-RAT
Measurement
Configuration Information->Absolute Threshold of the Quality of UTRAN Cell for 3A
150
This parameter indicates the absolute threshold of the UTRAN cell quality that is used
by UE to judge event 3a. The range and unit of the parameter are related to the
measurement quantity of the cells of the UTRAN system.
The smaller the value configured, the more difficult the event 3a been reported.
12.4.2.7
Parameter name
Abbreviated name
W[MAX_RAT_MEAS_EVENT]
Description
This parameter is used when judging the quality of the UTRAN

system in inter-RAT measurement, which indicates the weight of
the best cell in the quality judgment (only for event 3a).
Range and Step
[0.0, 2.0] step 0.1
Unit
N/A
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: For own system CPICH Ec/No, UE event report parameter: [0, -,
-, -]
For own system CPICH RSCP, periodic report parameter: For own system CPICH RSCP, UE event report parameter: [0, -,
-, -]
OMC Path

Management->
Modify
Advanced
Parameter->UE
Inter-RAT
Measurement
Configuration Information->Weight of the UTRAN System for 3A
This parameter indicates the weight of the best cell in the quality judgment of event 3a. It
is used in judging the quality of the UTRAN system in inter-RAT measurement.
See the description of the formula in Section 7.1 for the effect of this parameter on the
inter-RAT measurement.
12.4.2.8
Absolute Threshold of the Quality of Other RAT for 3A/3B/3C
Parameter name
Absolute Threshold of the Quality of Other RAT for 3A/3B/3C
Abbreviated name
ThreshSys[MAX_RAT_MEAS_EVENT]
Description
This parameter indicates the absolute threshold used when

judging the quality of other RAT configured for event 3a/3b/3c.
The value range and Unit of this parameter are related to the
151
measurement quantity of other system, at present the

measurement quantity can only be GSM Carrier RSSI of the
GSM system, which corresponds to the CPICH RSCP of
UTRAN system, so the value range and Unit of this parameter
correspond to the CPICH RSCP.
MAX_RAT_MEAS_EVENT is the maximum number of interRAT measurement events which takes the value of 4.
Range and Step
CPICH RSCP: [-115, -25]dBm step 1dBm

CPICH Ec/No: [-24, 0] dB step 1dB
Unit
dBm/ dB
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: For own system CPICH Ec/No, UE event report parameter: [90, -95, -95, -115]dBm
For own system CPICH RSCP, periodic report parameter: -
OMC Path

Management->
Modify
Advanced
Parameter->UE
Inter-RAT
Measurement
Configuration Information-> Absolute Threshold of the Quality of Other RAT for 3A/3B/3C
This parameter indicates the absolute threshold used when judging the quality of other
RAT configured for event 3a/3b/3c. The value range and unit of this parameter are
related to the measurement quantity of the cells of other systems. At present, the
measurement quantity can only be GSM Carrier RSSI of the GSM system, which
corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit
of this parameter correspond to CPICH RSCP.
The larger the value configured, the more difficult event 3a/3b/3c be reported.
12.4.2.9
Hysteresis(Rat)
Parameter name
Hystersis(dB)
Abbreviated name
Hysteresis[MAX_RAT_MEAS_EVENT]
Description

small change.
The larger the value is, the larger the difference between the
status to trigger the event and the status to leave the event will
be.
This parameter is related to the measurement quantity and the
event type.
Different events are configured separately and can be
152
configured with different hysteresis

MAX_RAT_MEAS_EVENT is the maximum number of interRAT measurement events which takes the value of 4.
Range and Step
(0, , 7.5)dB step 0.5dB
Unit
dB
For own system CPICH Ec/No, periodic report parameter: For own system CPICH Ec/No, UE event report parameter:
[4,4,2,4]dB
For own system CPICH RSCP, periodic report parameter: For own system CPICH RSCP, UE event report parameter:
[4,4,4,4]dB
OMC Path

Management->
Modify
Advanced
Parameter->UE
Inter-RAT
Measurement
Configuration Information-> Hysteresis
This parameter indicates the hysteresis used when judging whether the event meets the
conditions of been triggered.
This parameter is related to the measurement quantity and the event type. If a small
hysteresis is configured, the corresponding event will be reported in a high probability;
and vice versa.
12.4.2.10
Time to Trigger(Rat)
Parameter name
Time To Trigger(ms)
Abbreviated name
TrigTime[MAX_RAT_MEAS_EVENT]
Description

requirements of event triggering after Time to trigger, the event
can be triggered and reported. The larger the value is, the
stricter the judgment is for the event to be triggered. The
Sometimes, if it is set too large, the quality of calls may
decrease.
Range and Step
(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640,
1280, 2560, 5000)ms
Unit
Ms
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: -
For own system CPICH Ec/No, UE event report parameter:
153
[100,100,100,100]ms
[100,100,100,100]ms
OMC Path

Management->
Modify
Advanced
Parameter->UE
Inter-RAT
Measurement
Configuration Information-> Time to Trigger
is detected and the time that the event is reported. The event can be triggered and
reported only when the event is detected and still meets all requirements of event
triggering after Time to trigger.
parameter should be configured according to the actual requirements.
12.4.2.11
Inter-RAT Measurement Configuration Index Related to Traffic Category

Crat
Parameter name
Inter-RAT Measurement Configuration Index Related to Traffic

Category
Abbreviated name
TrfCatRatMIdx
Description
This parameter indicates the configuration index of the interRAT measurement parameters based on traffic type. There are
several different sets of measurement values according to
different traffic types.
Range and Step
[0, 65535]
Unit
N/A
Default Value
(note)
OMC Path

Management-> Modify Advanced Parameter-> UE Inter-Rat Measurement Relative to
Traffic Category Configuration Information -> Inter-RAT Measurement Configuration
Index Related to Traffic Category
This parameter indicates the index of the inter-RAT measurement configuration based
on traffic type. Each traffic type corresponds to a unique inter-RAT measurement
configuration index. If multiple sets of handover parameters are configured, each cell
154
should use a different index. Hence, the inter-RAT handover parameters may be
different from each other.
12.4.2.12

UtranCell
Parameter name
Inter-RAT Measurement Configuration Index Related to Traffic

Category
Abbreviated name
TrfCatRatMIdx
Description
This parameter indicates the configuration index of the interRAT measurement parameters based on traffic type. There are
several different sets of measurement values according to
different traffic types.
Range and Step
[0, 65535]
Unit
N/A
Default Value
(note)
OMC Path

This parameter indicates the index of the inter-RAT measurement configuration based
on traffic type. Each traffic type corresponds to a unique inter-RAT measurement
configuration index. If multiple sets of handover parameters are configured, each cell
should use a different index. Hence, the inter-RAT handover parameters may be
different from each other.
12.4.2.13
Parameter name

Configuration
Abbreviated name
TrfCategory
Description
This parameter differentiates different sets of handover

parameter according to different service and bearer type. For
different services, there are different parameters such as
handover trigger threshold, hysteresis, etc. Altogether there are
8 sets of configuration for different scenario based on service
type, transport channel type, service quantity, etc.
Range and Step
0:Single RT RAB Including Voice on DL DCH/UL DCH

1:Single RT RAB Excluding Voice on DL DCH/UL DCH
155
2:Single NRT on DL DCH/UL DCH

3:Single RAB on DL HS-DSCH/UL DCH
4:Single RAB on DL HS-DSCH/UL E-DCH
5:All Multi-RAB on DL DCH/UL DCH
6:Multi-RAB, HSPA is Involved and only DCHs are Used in UL
7:Multi-RAB, HSPA is Involved and E-DCH is Used in UL
Unit
N/A
See Table 5
OMC Path

Traffic Category Configuration Information -> Service and Bearer Type Used for
Differentiating Handover Configuration
the services, channel type, and service quantity. This parameter indicates the service
and bearer type. The handover parameters can be configured flexibly for different
scenarios and the parameters may have different handover trigger thresholds and
hysteresis.
The value 0xff (Not Related to Service Type) is exclusively used in the measurement of
the detected set.
Default Value 9
Default Value 8
Default Value 7
Default Value 6
Default Value 5
Default Value 4
Default Value 3
Default Value 2
Default Value 1
Service Type Related UE Inter-RAT Measurement Parameter ConfigurationDefault
Field Name
Table 10
Value
TrfCatRatMIdx
TrfCategory
0xff
PrdMeasEcNo
EvtMeasEcNo
PrdMeasRSC
P
EvtMeasRSCP
156
12.4.2.14
UE Event Report Configuration Index for Own System CPICH RSCP
Parameter name
UE Inter-frequency Event Measurement Configuration Index for

CPICH RSCP
Abbreviated name
EvtMeasRSCP
Description
This parameter indicates the Inter-frequency report configuration

index for CPICH RSCP, used for indexing the configuration of
the set of inter-frequency measurement parameters for event
reporting when measurement quantity is CPICH RSCP.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 5
OMC Path

Traffic Category Configuration Information ->UE Event Report Configuration Index for
Own System CPICH RSCP
This parameter indicates the index of the inter-RAT measurement configuration for
event reporting judgment by the UE when the UMTS measurement quantity is CPICH
RSCP.
12.4.2.15
UE Event Report Configuration Index for Own System CPICH Ec/No
Parameter name
UE Event Report Configuration Index for Own System CPICH

Ec/No
Abbreviated
name
EvtMeasEcNo
Description
This parameter is the UE event report configuration index for

CPICH Ec/No, used for indexing the configuration of the set of
inter-RAT measurement parameters for event reporting decided by
UE when measurement quantity is CPICH Ec/No.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 5
OMC Path

Traffic Category Configuration Information ->UE Event Report Configuration Index for
Own System CPICH Ec/No
157
This parameter indicates the index of the inter-RAT measurement configuration for
event reporting judgment by the UE when the UMTS measurement quantity is CPICH
Ec/No
12.4.2.16
Parameter name
Abbreviated name
InterRatCfgNo
Description
This parameter indicates the configuration index of the inter-RAT

measurement parameters, which is used to index different
parameter configuration sets for inter-RAT 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.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
0: Period Report Parameters for Own System CPICH Ec/No

2: UE Event Report Parameters for Own System CPICH Ec/No
3: Period Report Parameters for Own System CPICH RSCP
5: UE Event Report Parameters for Own System CPICH RSCP
OMC Path

Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration> Inter-RAT Measurement Configuration Index
Each inter-RAT measurement configuration with different measurement purpose and

measurement quantity is assigned with a unique inter-RAT measurement configuration.
This parameter indicates the index of the inter-RAT measurement configuration. This
configuration index is cited in the table Inter-RAT measurement configuration
relationship of the service type-related UE.
That is, the parameter Inter-RAT Measurement Configuration Index Related to
Traffic Category (namely TrfCatInterMIdx) is cited in the advanced parameter of the
serving cell and different Inter-RAT Measurement Configuration Index (namely
InterMeasCfgNo) can be selected aiming at the specific service type, measurement
purpose, and measurement quantity. This parameter can be used to meet various
requirements of network planning.
12.4.2.17
158
Parameter name
Abbreviated name
InterRatCfgNote
Description
This parameter indicates the purpose and functions of the set of

inter-RAT measurement configuration parameters.
Range and Step

Unit
N/A
Default Value
(note)

OMC Path

Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration> Function of Configuration Parameters
This parameter indicates the purpose and functions of the set of inter-RAT
12.4.2.18
Parameter name
Abbreviated name
MeasRptTrMod
Description

Range and Step
0: Acknowledged Mode RLC

1: Unacknowledged Mode RLC
Unit
N/A
Default Value
(note)

Mode RLC
159
Mode RLC
OMC Path

Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration> Measurement Report Transfer Mode
12.4.2.19
Parameter name
Abbreviated name
FilterCoeff(Rat)
Description
This parameter indicates the filtering factor that UE performs

the L3 filtering on the measurement results of the inter-RAT
measurement.
UE executes inter-RAT measurement on L1 in the fixed cycle
(measure several points in one measurement cycle and L1
filters the 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 TS25. 331:
F = (1 a ) F + a M , a = 1/2(k/2) .
n
n 1

Range and Step
(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19)
Unit
N/A
Period Report Parameters for Own System CPICH Ec/No: 3

UE Event Report Parameters for Own System CPICH Ec/No: 3
Period Report Parameters for Own System CPICH RSCP: 3
UE Event Report Parameters for Own System CPICH RSCP: 3
160
OMC Path

Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration>UTRAN Filter Coefficient
UTRAN measurement results of the inter-RAT measurement. The smaller the filtering
factor, the larger the effect of the measurement on the final result.
12.4.2.20
Parameter name
Abbreviated name
OwnMeasQuantity
Description
This parameter indicates the measurement quantity of the interRAT measurement that UE performs.
Range and Step
0: CPICH Ec/No
1: CPICH RSCP
Unit
N/A
For own system CPICH Ec/No, periodic report parameter:

CPICH Ec/No
CPICH Ec/No
For own system CPICH RSCP, periodic report parameter:
CPICH RSCP
For own system CPICH RSCP, UE event report parameter:
CPICH RSCP
OMC Path

Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration>UTRAN Measurement quantity
This parameter indicates the measurement quantity of the inter-RAT measurement that
UE performs. After a new inter-RAT measurement configuration index is added, the
measurement quantity is fixed when the function of the set of the inter-RAT
InterRatCfgNote is set to UE Event Report Parameters for Own System CPICH
RSCP, the value of UTRAN MeasQuantity is automatically set to the corresponding
CPICH RSCP.
161
12.4.2.21
Parameter name
Abbreviated name
GsmFilterCoeff
Description
UE executes inter-RAT measurement on L1 in the fixed cycle

(measure several points in one measurement cycle and L1
filters the 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 TS25. 331:
F = (1 a ) F + a M , a = 1/2(k/2) .
n
n 1

Range and Step
(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19)
Unit
N/A
For own system CPICH Ec/No, periodic report parameter: 3

For own system CPICH Ec/No, UE event report parameter: 3
For own system CPICH RSCP, periodic report parameter: 3
For own system CPICH RSCP, UE event report parameter: 3
OMC Path

Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration>GSM Filter Coefficient
This parameter indicates the filtering factor that UE performs the L3 filtering on the GSM
measurement results of the inter-RAT measurement. The smaller the filtering factor, the
larger the effect of the measurement on the final result.
12.4.2.22
Parameter name
Abbreviated name
BSICVeriReq
162
Description
This parameter indicates whether to confirm the BSIC of GSM

cells when performing the Inter-RAT measurement. BSIC =
NCC (Network Color Code) + BCC (Base Color Code). BSIC
can be used to identify the GSM cells. If the value is Not
Required , UE does not confirm the BSIC when measuring the
GSM cells. If the value is Required , UE confirms the BSIC
when measuring the GSM cells, and then queue the confirmed
BSIC cells according to the measurement results. In each
measurement period, re-confirm and measure the BSIC in the
order of the measurement results, from good to bad.
Range and Step
0: Require Confirm
1: Not Required Confirm
Unit
N/A
Period Report Parameters for Own System CPICH Ec/No:

Required
UE Event Report Parameters for Own System CPICH Ec/No:
Required
Period Report Parameters for Own System CPICH RSCP:
Required
UE Event Report Parameters for Own System CPICH RSCP:
Required
OMC Path

Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration->
This parameter indicates whether to confirm the base station identification code (BSIC)
of GSM cells when performing the inter-RAT measurement.
12.4.2.23
Parameter name
Abbreviated name
UtranEstQual
Description
This parameter indicates whether the report of the estimation

quality of UTRAN system is requested or not.
Range and Step

1: Report (True)
Unit
N/A
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: Not

Report
For own system CPICH Ec/No, UE event report parameter: Not
Report
163
For own system CPICH RSCP, periodic report parameter: Not

Report
For own system CPICH RSCP, UE event report parameter: Not
Report
OMC Path

This parameter indicates whether to report the quality estimation value of the UTRAN
system.
12.4.2.24
Parameter name
Abbreviated name
GsmCarrRSSIInd
Description
This parameter indicates whether the report of RSSI of the

GSM cells is requested or not. Since the measurement quantity
of the GSM cell is only GSM Carrier RSSI, in inter-RAT
measurement Event Reporting Criteria, there is no need to
report this parameter when measuring the GSM cell and
performing the Inter-RAT handover. In the periodical reporting
criteria, GSM carrier RSSI report is required.
Range and Step

1: Report (True)
Unit
N/A

Report
Report
Report
Report
OMC Path

164
This parameter indicates whether to report the received signal strength indicator (RSSI)
of GSM cells.
12.4.2.25
Report Criteria
Parameter name
Report Criteria
Abbreviated name
RptCrt
Description
This parameter indicates the report rules of the inter-RAT

measurement. When the value is Periodical Reporting Criteria,
two sets of the measurement parameters are required to be
configured. One set of the periodical parameters are configured
to UE and the other set of event parameters are configured to
SRNC for event judgment. When receiving the periodical
measurement reports from UE, SRNC judges which event is
triggered according to the event criteria parameters, and then
decides whether to perform the software handover according to
the triggered event. When the value is Event Reporting Criteria,
only one set of the measurement parameters is required to be
configured to UE. SRNC decides whether to perform the interRAT handover according to the measurement results reported
by UE.
Range and Step
1: Event Report (Inter-RAT Event Reporting Criteria)

2: Periodic Report (Periodical Reporting Criteria)
Unit
N/A
Default Value
(note)

Periodic Report
Event Report
Periodic Report
Event Reporting
OMC Path

Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration> Report Criteria
This parameter indicates the criteria of reporting the inter-RAT measurement, including
the Event Reporting and Periodical Reporting.
12.4.2.26
165
Parameter name
Abbreviated name
EventNum
Description
This parameter indicates how many events are required to be

configured for the set of the measurement parameters for a
certain purpose. The defined event number is related to the
judgment method of inter-RAT handover.
Range and Step
[1,MAX_RAT_MEAS_EVENT]
in which,MAX_RAT_MEAS_EVENT =4.
Unit
N/A
For own system CPICH Ec/No, periodic report parameter: For own system CPICH Ec/No, UE event report parameter: 4
For own system CPICH RSCP, periodic report parameter: For own system CPICH RSCP, UE event report parameter: 4
OMC Path

Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration> Inter-RAT Measurement Event Number
This parameter indicates the number of events that should be configured for the interRAT measurement configuration index for a certain purpose.
12.4.2.27
Parameter name
Abbreviated name
EventId [MAX_RAT_MEAS_EVENT]
Description
This parameter indicates the event triggered by the inter-RAT

measurement, which is related to the measurement quantity.
MAX_RAT_MEAS_EVENT indicates the maximum number of
inter-RAT measurement event, which is 4.
Range and Step
[3a,3b,3c,3d]
Unit
N/A
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: For own system CPICH Ec/No, UE event report parameter:
[3a,3b,3c,3d]
[3a,3b,3c,3d]
OMC Path
166

Configuration-> Inter-RAT event identity
This parameter indicates the identity of the event triggered by the inter-RAT
measurement (3a~3d).
12.4.2.28
Parameter name
Abbreviated name
CellIndivOffset(gsmRelation)
Description

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 is possibly (at least temporarily) the target
cell of the handover or removed from the active set.
Range and Step
OMCR: [-10, 10]dB step 0. 5

RNC: D= (P+10) *2, [0, 40]
Unit
dB
0dB
OMC Path

Management->GSM Cell->GSM Cell XXX->Modify Advanced Parameter->Cell
Individual Offset(dB)
This parameter indicates the individual offset of GSM cells. When the value is positive, a
positive value is added to the measurement result to be judged. If the value is negative,
a negative value is added to the measurement result to be judged. See the introduction
to inter-RAT measurement in section 7.1.1 for the effect of this parameter on the
measurement report.
the cell can be adjusted to meet the actual requirements of network planning, thus
avoiding the need to modify the global handover parameters.
12.4.2.29
UE State Indicator Used for GSM Neighboring Cell Configuration
167
Parameter name
UE State Indicator Used for GSM Neighboring Cell Configuration
Abbreviated name
GsmStateMode
Description
This parameter indicates the status of the GSM neighboring cell.

When the measurement control message is to be sent, the cells
that support DCH status are selected from the neighboring cells
list and are filled in the measurement control message.
Range and Step
0: Idle State Only

6: Idle State + Cell_DCH State+ Connected State, Non-Cell_DCH
Unit
N/A
Default Value
(note)
6: Idle State + Cell_DCH State+ Connected State, Non-Cell_DCH
OMC Path

Parameter->UE State Indicator Used for GSM Neighboring Cell Configuration
This parameter indicates the UE status applied to the GSM neighboring cell. When the
neighbouring cell is configured by status, the neighbouring cells list used for reselection
in nondedicated mode and the neighbouring cells list used for handover in dedicated
mode are differentiated as follows:
connected Non-Cell_DCH state from the neighboring cells list and fills in SIB11.
When SIB12 is to be sent, the UE selects the cell that supports the connected NonCell_DCH state from the neighboring cells list and fills in SIB12;
When the measurement control message is to be sent, the UE selects the cell that
supports the Cell_DCH state from the neighboring cells list.
12.4.2.30
Parameter name
168
Abbreviated name
GsmShareCover
Description
This parameter describes the neighboring relationship of the

serving cell and Gsm neighboring cell.
Range and Step
0: Neighbor
1: Overlap
2: Covers
3: Contained in
Unit
N/A
0: Neighbor
OMC Path

Parameter->Share Cover Indication
This parameter indicates the neighboring relationship of the current cell and GSM
neighboring cell, including Neighbor, Overlap, Covers, and Contained in.
12.4.2.31
UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements
Parameter name
UTRAN Measurement Quantity for Inter-frequency and InterRAT Measurements
Abbreviated name
NonIntraMeasQuan
Description

inter-frequency and inter-RAT measurements.
Range and Step
0: Ec/No
1: RSCP
2: Ec/No and RSCP
Unit
N/A
1: RSCP
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements
This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for interfrequency and inter-RAT measurements. The measurement quantity RSCP is
recommended.
169
12.4.2.32
Parameter name
Abbreviated
name
IntRatHoMth
Description
The paramerer indicates the inter-RAT handover method is

Range and Step
0: Periodical Method
1: Event Method
Unit
N/A
Default Value
(note)
1: Event Method
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell>Inter-RAT Handover Method
This parameter indicates the handover method of Inter-RAT Handover.At present, InterRAT measurement supports only the handover modes reported through events. The
IntRatHoMth parameter is invalid.
12.4.2.33
Parameter name
Abbreviated
name
PrdMeasEcNo
Description
This parameter is period report configuration index for CPICH

Ec/No, used for indexing the configuration of the set of inter-RAT
measurement parameters for periodical reporting when
measurement quantity of own system is CPICH Ec/No.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 5
OMC Path

Traffic Category Configuration Information -> Period Report Configuration Index for
CPICH Ec/No
170
Only event report can be supported currently. So the following parameters for
periodically
report
is
invalid:
PrdMeasEcNo(RAT),
PrdMeasRSCP(RAT),
PrdRptAmount(RAT), PrdRptInterval(RAT)
12.4.2.34
Parameter name
PrdMeasRSCP
Abbreviated
name
Description
This parameter is period report configuration index for CPICH

RSCP, used for indexing the configuration of the set of inter-RAT
measurement parameters for periodical reporting when
measurement quantity of own system is CPICH RSCP.
Range and Step
[0,65535]
Unit
N/A
Default Value
(note)
See Table 5
OMC Path

Traffic Category Configuration Information ->Period Report Configuration Index for
CPICH RSCP
periodically
report
is
invalid:
PrdMeasEcNo(RAT),
PrdMeasRSCP(RAT),
12.4.2.35
Parameter name
Abbreviated
name
PrdRptAmount
Description

Range and Step
(1, 2, 4, 8, 16, 32, 64, Infinity)
Unit
N/A
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: Infinity

For own system CPICH Ec/No, UE event report parameter: For own system CPICH RSCP, periodic report parameter: Infinity
For own system CPICH RSCP, UE event report parameter: -
OMC Path
171

Management->Modify Advanced Parameter-> UE Inter-Rat Measurement Configuration>Amount of Reporting in Period Report Criteria
periodically
report
is
invalid:
PrdMeasEcNo(RAT),
PrdMeasRSCP(RAT),
12.4.2.36
Parameter name
Abbreviated
name
PrdRptInterval
Description
This parameter indicates the reporting interval in periodical

reporting.
Range and Step
(250, 500, 1000, 2000, 3000, 4000, 6000, 8000, 12000, 16000,
20000, 24000, 28000, 32000, 64000)ms
Unit
ms
Default Value
(note)
For own system CPICH Ec/No, periodic report parameter: 1s

For own system CPICH Ec/No, UE event report parameter: For own system CPICH RSCP, periodic report parameter: 500ms
For own system CPICH RSCP, UE event report parameter: -
OMC Path

Management->Modify Advanced Parameter-> UE Inter-Rat Measurement Configuration>Reporting Interval in Period Report Criteria(ms)
periodically
report
is
invalid:
PrdMeasEcNo(RAT),
PrdMeasRSCP(RAT),
12.4.2.37
Use of HCS (gsmRelation)
Parameter name
Use of HCS
Abbreviated
name
UseOfHCS
Description
Range and Step
1: Not Used
2: Used
Unit
N/A
Default Value
(note)
1: Not Used
172
OMC Path

Parameter-> Use of HCS
12.4.2.38
HCS_PRIO(gsmRelation)
Parameter name
HCS_PRIO
Abbreviated
name
HcsPrio
Description
neighboring cells. 7 is the highest priority, 0 is the lowest priority.
Range and Step
[07]
Unit
N/A
Default Value
(note)
OMC Path

Management->GSM Cell->GSM Cell XXX->Modify Advanced Parameter-> HCS_PRIO
This parameter indicates the HCS priority level of the neighbouring cell. 7 represents the
highest priority and 0 represents the lowest priority. A cell with a higher priority often
provides a smaller coverage and a cell with a lower priority often offers a larger
coverageIMSI-Based Handover Parameters
12.4.3
Parameter List
Field Name
MCC(rncPnSnac)
MCC(rncPnSnac)
MNC(rncPnSnac)
MNC(rncPnSnac)
ExtInfoDgtNum
Extend Information Digits Num
ExtInfo[10]
Extend Information
SMCC
MCC of Shared Network
SMNC
MNC of Shared Network
SNAC
Shared Network Area Code
MCC(rncLcSnac)
MCC(rncLcSnac)
173
MNC(rncLcSnac)
MNC(rncLcSnac)
LAC(rncLcSnac)
Location Area Code(rncLcSnac)
SNAC(rncLcSnac)
Shared Network Area Code(rncLcSnac)
MCC(utranCell)
Mobile Country Code(UtranCell)
MCC(externalUtranCell)
Mobile Country Code(ExternalUtranCell)
MCC(gsmRelation)
Mobile Country Code of Neighbouring GSM

Cell(gsmRelation)
MNC(utranCell)
Mobile Network Code(UtranCell)
MCC(externalUtranCell)
Mobile Network Code(ExternalUtranCell)
MCC(gsmRelation)
Mobile Network Code of Neighbouring GSM Cell
LAC(utranCell)
Location Area Code(UtranCell)
LAC(externalUtranCell)
Location Area Code(ExternalUtranCell)
LAC(gsmRelation )
Location Area Code of Neighbouring GSM Cell
12.4.4
12.4.4.1
MCC(rncPnSnac)
Parameter name
MCC(rncPnSnac)
Abbreviated name
MCC
Description
This parameter indicates MCC included in IMSI. MCC uniquely

identifies the country that the mobile users (or system) belong
to. MCC is allocated uniformly and internationally.
Range and Step
[0, 999]
Unit
N/A
Default Value
(note)
460
OMC Path

Management->User Authorized PLMN+SNAC Information->MCC
This parameter indicates the mobile country code (MCC) of the IMSI card. See Figure
26 in the text for the use case.
12.4.4.2
MNC(rncPnSnac)
Parameter name
MNC(rncPnSnac)
174
Abbreviated name
MNC
Description
This parameter indicates MNC included in IMSI. MNC identifies a

specific PLMN inside one country (decided by MCC).
Range and Step
[0, 999]
Unit
N/A
Default Value
(note)
N/A
OMC Path

Management->User Authorized PLMN+SNAC Information->MNC
This parameter indicates the mobile network code (MNC) of the IMSI card. See Figure
26 in the text for the use case.
12.4.4.3
Parameter name
Abbreviated name
ExtInfoDgtNum
Description
This parameter indicates the number of the extend information

digits included in MSIN of IMSI. The extend information means
several high-bit digits of MSIN, includes the number of digits and
values of these digits. UEs with same MCC and MNC can be
have different authorization. The digits number of extend
information must be same for each MCC+MNC.
Range and Step
0..10, 0 means no extend information
Unit
N/A
N/A
OMC Path

Management->User Authorized PLMN+SNAC Information->Extend Information Digits
Num
This parameter indicates the number of extend information digits included in the mobile
station identity number (MSIN) of IMSI. If the parameter is set to n, the first n digits of the
corresponding MSIN are extend information digits. The maximum value of this
parameter is 10.
175
12.4.4.4
Extend Information
Parameter name
Extend Information
Abbreviated name
ExtInfo[10]
Description
This parameter indicates values of the extend information digits

included in MSIN of IMSI. The extend information means
several high-bit digits of MSIN, includes the number of digits
and values of these digits. UEs with same MCC and MNC can
be have different authorization. The digits number of extend
information must be same for each MCC+MNC.
Range and Step
[0, 9]
Unit
N/A
N/A
OMC Path

Management->User Authorized PLMN+SNAC Information->Extend Information
This parameter indicates the MSIN of IMSI, namely the last 10 digits of the 15-digit IMSI.
This parameter in combination with the parameter Extend Information Digits Num
specifies an IMSI segment.
12.4.4.5
MCC of Shared
Network
Parameter name
MCC of Shared Network
Abbreviated name
SMCC
Description
The parameter indicates MCC of network that is shared by UEs

having same MCC+MNC+ Extend Information Digits Num+
Extend Information.
Range and Step
[0, 999]
Unit
N/A
460
OMC Path

Management->User Authorized PLMN+SNAC Information->MCC of Shared Network
The parameter indicates the MCC of the shared network, namely the MCC of the target
location area code (LAC) that the handover is allowed in.
176
12.4.4.6
MNC of Shared
Network
Parameter name
MNC of Shared Network
Abbreviated name
SMNC
Description
The parameter indicates MNC of network that is shared by UEs

having same MCC+MNC+ Extend Information Digits Num+
Extend Information.
Range and Step
[0, 999]
Unit
N/A
N/A
OMC Path

Management->User Authorized PLMN+SNAC Information->MNC of Shared Network
The parameter indicates the MNC of the shared network, namely the MNC of the target
LAC that the handover is allowed in.
12.4.4.7
Parameter name
Abbreviated name
SNAC
Description
The parameter indicates shared network area code of network

that is shared by UEs having same MCC+MNC+Extend
Information Digits Num+ Extend Information.
Range and Step
[0, 65535]
Unit
N/A
N/A
OMC Path

Management->User Authorized PLMN+SNAC Information->Shared Network Area Code
This parameter indicates the shared network area code (SNAC). It is defined by the
customer.
177
12.4.4.8
MCC(rncLcSnac)
Parameter name
MCC(rncLcSnac)
Abbreviated name
MCC
Description
MCC uniquely identifies the country that the mobile users (or
system) belong to. MCC is allocated uniformly and
internationally.
Range and Step
[0, 999]
Unit
N/A
460
OMC Path

Management->LAC and SNAC Information->MCC
This parameter in combination with parameters MNC(rncLcSnac), LAC(rncLcSnac),

and SNAC(rncLcSnac) specifies a target area code that the handover is allowed in.
See Figure 26 in the text for the use case.
12.4.4.9
MNC(rncLcSnac)
Parameter name
MNC(rncLcSnac)
Abbreviated name
MNC
Description
MNC identifies a specific PLMN inside one country (decided by

MCC).
Range and Step
[0, 999]
Unit
N/A
Default Value
(note)
N/A
OMC Path

Management->LAC and SNAC Information->MNC
This parameter in combination with parameters MCC(rncLcSnac), LAC(rncLcSnac),

178
12.4.4.10
Parameter name
Abbreviated name
LAC
Description
This parameter identifies different location area. LAC belongs

to LAI (LAI= MCC+MNC+LAC).
Range and Step
[1, 0xfffd], 0xffff
Unit
N/A
N/A
OMC Path

Management->LAC and SNAC Information->Location Area Code
This parameter in combination with parameters MCC(rncLcSnac), MNC(rncLcSnac),

12.4.4.11
Parameter name
Abbreviated name
SNAC
Description
This parameter indicates the shared network area code that the
location area belongs to. One LAC can belong to at most four
SNAC (shared network area code).
Range and Step
[0, 65535]
Unit
N/A
N/A
OMC Path

Management->LAC and SNAC Information->Shared Network Area Code
This parameter in combination with parameters MCC(rncLcSnac), MNC(rncLcSnac),

and LAC(rncLcSnac) specifies a target area code that the handover is allowed in. See
Figure 26 in the text for the use case.
179
12.4.4.12
Parameter name
Abbreviated name
MCC
Description
MCC uniquely identifies the country that the mobile users (or
internationally.
Range and Step
[0, 999]
Unit
N/A
460
OMC Path

Management->Utran Cell->UtranCell Global Info>MCC
This parameter indicates the MCC of the cells in the RNC.
12.4.4.13
Parameter name
Abbreviated name
MCC
Description
MCC uniquely identifies the country that the UE users (or

internationally.
Range and Step
[0, 999]
Unit
N/A
460
OMC Path

Management->External Utran Cell->MCC
This parameter indicates the MCC of UTRAN cells that do not belong to the RNC.
12.4.4.14
Mobile Country CodeexternalGsmCell
180
Parameter name
Mobile Country CodeexternalGsmCell
Abbreviated name
MCC
Description
MCC uniquely identifiesthe country that the UE users (or system)

belong to. MCC is allocated uniformly and internationally.
Range and Step
[0, 999]
Unit
N/A
Default Value
(note)
460
OMC Path

Management-> External Gsm Cell ->MCC
This parameter indicates in the MCC of the GSM cells.
12.4.4.15
Parameter name
Abbreviated name
MNC
Description
MNC identifies a specific PLMN inside one country (decided

by MCC).
Range and Step
[0, 999]
Unit
N/A
Default value
N/A
OMC Path

Management->Utran Cell->UtranCell Global Info>MNC
This parameter indicates the MNC of the cells in the RNC.
12.4.4.16
Parameter name
Abbreviated name
MNC
Description

MCC).
181
Range and Step
[0, 999]
Unit
N/A
N/A
OMC Path

Management->External Utran Cell->MNC
This parameter indicates the MNC of the cells that do not belong to the RNC.
12.4.4.17
Mobile Network CodeexternalGsmCell
Parameter name
Mobile Network CodeexternalGsmCell
Abbreviated name
MNC
Description

MCC).
Range and Step
[0, 999]
Unit
N/A
N/A
OMC Path

Management-> External Gsm Cell->MNC
This parameter indicates in the MNC of the GSM cells.
12.4.4.18
Parameter name
Abbreviated name
LAC
Description
This parameter indicates the LAC of the cell. It is used to

determine the location of the MS. The coverage area of each
PLMN is divided into many location areas. LAC is used to identify
different location area. LAC belongs to LAI (LAI = MCC + MNC +
LAC). One location area includes many cells.
Range and Step
[1, 0xfffd], 0xffff
Unit
N/A
182
Default Value
(note)
N/A
OMC Path

Management->Utran Cell->UtranCell Global Info>LAC
This parameter indicates the LAC of the cells in the RNC.
12.4.4.19
OMC PathOMC Path Shared Network Area CodeExternalUtranCell
Parameter name
Shared Network Area CodeExternalUtranCell
Abbreviated
name
SNAC
Description
neighboring cell belongs to. One cell can belong to at most four
SNACs (shared network area code).
Range and Step
0..65535
Unit
N/A
Default Value
(note)
N/A
OMC Path

Management->External Utran Cell->SNAC
This parameter indicates the shared network area code that the neighboring cell belongs
to. One cell can belong to at most four SNACs (shared network area code).
12.4.4.20
Shared Network Area Code NumberExternalUtranCell
Parameter name
Shared Network Area Code NumberExternalUtranCell
Abbreviated
name
SNACNum
Description
This parameter indicates the number of shared network area code

that the neighboring cell belongs to.
Range and Step
0..4
Unit
N/A
Default Value
(note)
N/A
OMC Path
183

Management-> External Utran Cell ->SNAC
This parameter indicates the number of shared network area code that the neighboring
cell belongs to.
12.4.4.21
Shared Network Area CodeexternalGsmCell
Parameter name
Shared Network Area CodeexternalGsmCell
Abbreviated
name
SNAC
Description
neighboring cell belongs to. One cell can belong to at most four
SNACs (shared network area code).
Range and Step
0..65535
Unit
N/A
Default Value
(note)
N/A
OMC Path

Management-> External Gsm Cell ->SNAC
This parameter indicates the shared network area code that the neighboring cell belongs
to. One cell can belong to at most four SNACs (shared network area code).
12.4.4.22
Shared Network Area Code NumberexternalGsmCell
Parameter name
Shared Network Area Code NumberexternalGsmCell
Abbreviated
name
SNACNum
Description
This parameter indicates the number of shared network area code

that the neighboring cell belongs to.
Range and Step
0..4
Unit
N/A
Default Value
(note)
N/A
OMC Path

Management-> External Gsm Cell -> SNACNum
184
This parameter indicates the number of shared network area code that the neighboring
cell belongs to.
12.5
12.5.1
HSDPA Handover Parameters

Parameter List
Field Name
HspaSptMeth
HSPA Support Method
T1d
Timer for Event 1D in HSPA or MBMS
RncFeatSwitch
Neighbouring RNC Feather Switch
12.5.2
12.5.2.1
HSPA Support Method
Parameter name
HSPA Support Method
Abbreviated name
HspaSptMeth
Description
This parameter indicates the supporting type of DCH, HSDPA and

HSUPA of the neighboring cell.
Range and Step
0: Not Support HSUPA and HSDPA

1: Support HSDPA and DCH
3: Support HSUPA , HSDPA and DCH
Unit
N/A
OMC Path

Management->Utran Cell->Utran Cell XXX->Cell Ability and Cell Reselection->HSPA
Support Method
This parameter indicates the support for various types of cells.
12.5.2.2
Parameter name
Timer for Event 1D in HSPA or MBMS(s)
Abbreviated name
T1d
185
Description
For HSPA, this parameter indicates the minimum interval

between two HSPA serving cell changes or channel, which
helps to avoid too frequent HSPA serving cell changes and
channel transition.
For MBMS, this parameter indicates the minimum interval
between two best cell changes due to event 1d which helps to
avoid too frequent change between PTP and PTM bearer types.
Range and Step
[0, 65535]s step: 1 s
Unit
Default Value
(note)
4s
OMC Path

Management-> Modify Advanced Parameter->Hspa Configuration Information-> Timer
for Event 1D in HSPA or MBMS
For HSPA, this parameter indicates the minimum interval required for the change of the
HSPA serving cell or the transition between the HS and DCH channels. A large value of
this parameter helps to avoid too frequent HSPA serving cell change and channel
transition.
12.5.2.3
Parameter name
Abbreviated name
RncFeatSwitch
Description
The parameter indicates the feather switch of neighboring RNC.
Range and Step
Bit0 = 0/1:Hard-handover With Relocation / Hard-handover

Without Relocation)
Unit
Bit1 = 0/1:Not Support HSDPA Iur Interface Process / Support

HSDPA Iur Interface Process
Default Value
(note)
Bit2 = 0/1:Not Support HSUPA Iur Interface Process / Support

HSUPA Iur Interface Process
OMC Path
View->Configuration Management->RNC NE->RNC Ground Resource Management>Transmission Configuration->NE Information Configuration->RNC:xx ->Adjacent RNC
Office-> Rnc Config
186
The parameter indicates whether the relocation procedure is performed together with
the inter-frequency hard handover between RNSs or whether the Iur interface supports
the HSDPA/UPA feature.
12.6
HSUPA Handover Parameters
12.6.1
Parameter List
Field Name
HspaSptMeth
HSPA Support Method
MaxNumOfEdchAct
Maximum Number of Cells in E-DCH Active Set
RncFeatSwitch
12.6.2
12.6.2.1
HSPA Support Method
Parameter name
HSPA Support Method
Abbreviated name
HspaSptMeth
Description
This parameter indicates the supporting type of DCH, HSDPA

and HSUPA of the neighboring cell.
Range and Step
0: Not Support HSUPA and HSDPA

1: Support HSDPA and DCH
Unit
N/A
OMC Path

Management->Utran Cell->Utran Cell XXX->Cell Ability and Cell Reselection->HSPA
Support Method
This parameter indicates the support for various types of cells.
12.6.2.2
Parameter name
Abbreviated name
MaxNumOfEdchAct
187
Description
This parameter indicates the maximum number of cells

allowed in E-DCH active set.
Range and Step
[1, 4]
Unit
N/A
OMC Path

Management-> Modify Advanced Parameter->Hspa Configuration Information>Maximum Number of Cells in E-DCH Active Set
This parameter indicates the maximum number of cells allowed in the E-DCH active set.
The number is configured according to the actual requirements.
12.6.2.3
Parameter name
Abbreviated name
RncFeatSwitch
Description
The parameter indicates the feather switch of neighboring

RNC.
Range and Step
Bit0 = 0/1:Hard-handover With Relocation / Hard-handover

Without Relocation)
Unit
Bit1 = 0/1:Not Support HSDPA Iur Interface Process / Support

HSDPA Iur Interface Process
Bit2 = 0/1:Not Support HSUPA Iur Interface Process / Support

HSUPA Iur Interface Process
OMC Path
View->Configuration Management->RNC NE->RNC Ground Resource Management>Transmission Configuration->NE Information Configuration->RNC:xx ->Adjacent RNC
Office-> Rnc Config
The parameter indicates whether the relocation procedure is performed together with
the inter-frequency hard handover between RNSs or whether the Iur interface supports
the HSDPA/UPA feature.
188
12.7
MBMS Handover Parameters
12.7.1
Parameter List
Field Name
MbmsSuptInd
Support MBMS Indicator
T1d
12.7.2
12.7.2.1
Parameter name
Abbreviated name
MbmsSuptInd
Description
This parameter indicates whether MBMS is supported in the

cell.
Range and Step
0: Not Support
1: Support MBMS and not MBMS
2: Only Support MBMS
Unit
N/A
0: Not Support
OMC Path

Management->Utran Cell->Utran Cell XXX->Cell Ability and Cell Reselection->MBMS
Support Indicator
This parameter indicates whether to support the MBMS. When the parameter is set to 0
(Not Support), the cell does not support the MBMS service.
When the parameter is set to 1 (Support MBMS and not MBMS), the cell supports both
the MBMS service and the mixed R99, R5, and R6 service. In this case, the cell can
either use a separate carrier frequency for establishing the co-coverage relationship or
HSC structure with other cells, or use the same carrier frequency as the neighbouring
cell.
When the parameter is set to 2 (Only Support MBMS), the cell supports only the MBMS
service. In this case, non-S-CCPCHs can neither be allocated separately for users nor
exist as the DCH channel of the concurrent service. The purpose of such a cell is to
share the load of the MBMS service.
189
12.7.2.2
Parameter name
Timer for Event 1D in HSPA or MBMS(s)
Abbreviated name
T1d
Description
For HSPA, this parameter indicates the minimum interval

between two HSPA serving cell changes or channel , which
helps to avoid too frequent HSPA serving cell changes and
channel transition.
For MBMS, this parameter indicates the minimum interval
between two best cell changes due to event 1d which helps to
avoid too frequent change between PTP and PTM bearer
types.
Range and Step
[0, 65535]s step: 1 s
Unit
4s
OMC Path

Management-> Modify Advanced Parameter->Hspa Configuration Information-> Timer
for Event 1D in HSPA or MBMS
For HSPA, this parameter indicates the minimum interval required for the change of the
HSPA serving cell or the transition between the HS and DCH channels. A large value of
this parameter helps to avoid too frequent HSPA serving cell change and channel
transition.
For MBMS, this parameter indicates the minimum interval required for changing the best
cell of the MBMS service for two times caused by event 1d. This parameter helps to
avoid too frequent change between the PTP and PTM bearer types.
13
Counter And Alarm
13.1
Counter List
13.1.1
RNC Soft Handover Statistics

Counter No.
Description
C301100479
Number of soft handover attempt
C301101040
Number of soft handover attempt,by traffic class
C301101041
C301101042
190
Counter No.
Description
C301101043
C301100480
C301100481
C301100482
C301100483
C301100484
Number of failed soft handover,by cause
C301100485
C301100486
C301100487
C301101044
C301101045
C301101046
Number of failed soft handover,by traffic class
C301101047
C301100931
C301100932
C301100933
Number of soft handover attempt,add Radio link
C301100934
C301100935
Number of soft handover attempt,add Radio link for HSDPA
C301100936
C301100937
C301100938
Number of soft handover attempt,delete radio link
C301100939
C301100940
Number of soft handover attempt,delete radio link for HSDPA
C301100941
C301100942
C301100943
C301100944
C301100945
C301100946
C301100947
RNC Soft handover ratio
C301100948
C301100949
C301100950
C301100951
C301100952
C301100953
RNC Soft handover ratio
C301100954
RNC Soft handover ratio for RT Class
C301100955
191
Counter No.
Description
C301100956
C301100957
C301100958
C301100959
C301100960
C301100961
C301100962
C301100963
C301100964
RNC Soft handover ratio for NRT Class,but no HSPA
C301100965
C301100966
C301100967
13.1.2
RNC Hard Handover Statistics

Counter No.
Description
C301110488
Number of intra-RNC intra frequency hard handover attempt
C301110489
C301110490
C301110491
C301110492
C301110493
Number of intra-RNC intra frequency hard handover failure,by cause
C301110494
C301110495
C301110496
C301110497
Number of intra-RNC inter frequency hard handover attempt
C301110498
C301110499
C301110500
C301110501
C301110502
Number of intra-RNC inter frequency hard handover failure,by cause
C301110503
C301110504
C301110505
C301110506
Number of inter-RNC intra frequency hard handover via Iur attempt
C301110507
Number of inter-RNC intra frequency hard handover via Iur failure,by

cause
C301110508
C301110509
C301110510
192
Counter No.
Description
C301110511
C301110512
C301110513
C301110514
C301110515
Number of inter-RNC inter frequency hard handover via Iur attempt
C301110516
C301110517
C301110518
C301110519
C301110520
Number of inter-RNC inter frequency hard handover via Iur failure,by

cause
C301110521
C301110522
C301110523
13.1.3
Counter No.
C301120543
C301120544
C301120545
C301120546
C301120547
Description
Number of attempted relocation preparation with UE involved for

CS domain, by cause
C301120548
C301120549
C301120550
C301120551
C301120552
C301120553
C301120554
Number of failed relocation preparation with UE involved for CS

domain, by cause
C301120555
C301120556
C301120557
C301120558
C301120559
C301120560
C301120561
Number of attempted outgoing relocation with UE involved for CS

domain
Number of failed outgoing relocation with UE involved for CS
domain, by cause
C301120562
C301120563
C301120564
193
C301120565
C301120566
C301120567
C301120587
C301120588
C301120589
C301120590
C301120591
Number of attempted relocation preparation with UE involved for PS domain,

by cause
C301120592
C301120593
C301120594
C301120595
C301120596
C301120597
C301120598
Number of failed relocation preparation with UE involved for PS domain, by

cause
C301120599
C301120600
C301120601
C301120602
C301120603
Number of attempted outgoing relocation with UE involved for PS domain
C301120604
C301120605
C301120606
C301120607
C301120608
Number of failed outgoing relocation with UE involved for PS domain, by

cause
C301120609
C301120610
C301120611
C301120624
C301120625
C301120626
C301120627
C301120628
C301120629
C301120630
Number of attempted incoming relocation with UE involved for CS domain, by

cause
C301120631
C301120632
C301120633
C301120634
C301120635
194
C301120648
C301120649
C301120650
C301120651
Number of attempted incoming relocation with UE involved for PS domain, by

cause
C301120652
C301120653
C301120654
C301120655
C301120656
C301120657
Number of failed incoming relocation with UE involved for PS domain, by

cause
C301120658
C301120659
13.1.4
Relocation With UE Not Involed

Counter No.
C301120524
C301120525
C301120526
C301120527
C301120528
Description
Number of attempted relocation preparation with UE not involved

for CS domain, by cause
C301120529
C301120530
C301120531
C301120532
C301120533
C301120534
C301120535
Number of failed relocation preparation with UE not involved for CS domain,

by cause
C301120536
C301120537
C301120538
C301120539
C301120540
C301120541
Number of attempted outgoing relocation with UE not involved for

CS domain
C301120542
Number of failed outgoing relocation with UE not involved for CS

domain, by cause
C301120568
C301120569
Number of attempted relocation preparation with UE not involved for PS

domain, by cause
C301120570
C301120571
C301120572
195
C301120573
C301120574
C301120575
C301120576
C301120577
C301120578
C301120579
Number of failed relocation preparation with UE not involved for PS domain

by cause
C301120580
C301120581
C301120582
C301120583
C301120584
C301120585
C301120586
Number of attempted outgoing relocation with UE not involved for PS

domain
Number of failed outgoing relocation with UE not involved for PS domain, by
cause
C301120612
C301120613
C301120614
C301120615
Number of attempted incoming relocation with UE not involved for CS

domain, by cause
C301120616
C301120617
C301120618
C301120619
C301120620
C301120621
C301120622
C301120623
C301120636
C301120637
Number of attempted incoming relocation with UE not involved for PS

domain, by cause
C301120638
C301120639
C301120640
C301120641
C301120642
C301120643
C301120644
C301120645
Number of failed incoming relocation with UE not involved for PS domain, by

cause
C301120646
C301120647
196
13.1.5
RNC Inter-RAT Handover Statistics

Counter No.
Description
C301130660
C301130661
C301130662
C301130663
C301130664
Number of attempted relocation preparation for outgoing CS interRAT handovers, by cause
C301130665
C301130666
C301130667
C301130668
C301130669
C301130670
C301130671
C301130672
Number of failed relocation preparation for outgoing CS inter-RAT

handovers, by cause
C301130673
C301130674
C301130675
C301130676
Number of attempted outgoing CS inter-RAT handovers
C301130677
C301130678
C301130679
C301130680
Number of failed outgoing CS inter-RAT handovers, by cause
C301130681
C301130682
C301130683
C301130684
C301130685
C301130686
Number of attempted incoming CS inter-RAT handovers, by cause
C301130687
C301130688
C301130689
C301130690
C301130691
C301130692
Number of failed incoming CS inter-RAT handovers, by cause
C301130693
C301130694
C301130695
Number of attempted outgoing PS inter-RAT handovers
C301130696
Number of failed outgoing PS inter-RAT handovers, by cause
C301130697
197
Counter No.
Description
C301130698
C301130699
C301130700
13.1.6
C301130701
Number of attempted incoming PS inter-RAT handovers
C301130702
Number of successful incoming PS inter-RAT handovers
Cell Soft Handover Statistics

Counter No.
Description
C301391098
C301391099
Number of attempted radio link addition for soft handover
C301391100
C301391101
C301391102
Number of failed radio link addition for soft handover, by procedure
C301391103
C301390586
C301390587
C301390588
C301390589
C301390590
Number of failed radio link addition for soft handover,by cause
C301390591
C301390592
C301390593
C301390594
Number of attempted radio link deletion for soft handover
C301390595
C301390596
C301390597
C301390598
C301390599
Number of failed radio link deletion for soft handover,by cause
C301390600
C301390601
C301390602
C301391156
C301391157
Number of attempted radio link addition for E-DCH soft handover
C301391158
C301391159
C301391160
C301391161
C301391162
Number of failed radio link addition for E-DCH soft handover, by

procedure
Number of failed radio link addition for E-DCH soft handover,by
198
Counter No.
C301391163
Description
cause
C301391164
C301391165
C301391166
C301391167
C301391168
C301391169
C301391250
Number of attempted radio link deletion for E-DCH soft handover
C301391251
C301391252
C301391253
C301391254
C301391255
Number of failed radio link deletion for E-DCH soft handover,by

cause
C301391256
C301391257
C301391258
C301390603
C301390604
C301390605
C301390606
C301390607
C301390608
C301390609
Soft handover ratio
C301390610
C301390611
C301390612
C301390613
C301390614
C301390615
C301391332
C301391333
C301391334
Soft handover rate of E-DCH user
C301391335
C301391509
Stat of Soft Handover for DCH RT traffic
C301391510
C301391511
C301391512
C301391513
199
Counter No.
Description
C301391514
C301391515
C301391516
C301391517
C301391518
C301391519
C301391520
C301391521
C301391522
C301391523
C301391524
C301391525
C301391526
C301391527
C301391528
C301391529
Stat of Soft Handover for DCH NRT traffic
C301391530
C301391531
C301391532
C301391533
C301391534
C301391536
C301391537
C301391538
C301391539
C301391540
C301391541
C301391542
Stat of Soft handover for E-DCH(Traffic Class)
C301391543
C301391544
C301391545
C301391546
C301391547
C301391548
C301391549
13.1.7
Cell Hard Handover Statistics

Counter No.
Description
200
Counter No.
Description
C301410616
Number of outgoing intra-NodeB intra frequency hard handover

attempt
C301410617
C301410618
C301410619
C301410620
C301410621

failure
C301410622
C301410623
C301410624
C301410625
Number of outgoing intra-NodeB inter frequency hard handover

attempt
C301410626
C301410627
C301410628
C301410629
C301410630

failure
C301410631
C301410632
C301410633
C301410634
Number of outgoing inter-NodeB,intra-RNC intra frequency hard

handover attempt
C301410635
C301410636
C301410637
C301410638
C301410639

handover failure
C301410640
C301410641
C301410642
C301410643
Number of outgoing inter-NodeB,intra-RNC inter frequency hard

handover attempt
C301410644
C301410645
C301410646
C301410647
C301410648

handover failure
C301410649
C301410650
C301410651
201
Counter No.
Description
C301410652
Number of outgoing inter-RNC intra frequency hard handover via Iur

attempt
C301410653
C301410654
C301410655
C301410656
C301410657

failure
C301410658
C301410659
C301410660
C301410661
Number of outgoing inter-RNC inter frequency hard handover via Iur

attempt
C301410662
C301410663
C301410664
C301410665
C301410666

failure
C301410667
C301410668
C301410669
13.1.8
Transfer between HSPA and DCH due to Cell Mobility

Counter No.
Description
C301450826
Number of intra frequency HS-DSCH to DCH attempt due to moving
C301450827
C301450828
C301450829
C301450830
C301450831
Number of intra frequency HS-DSCH to DCH failure due to moving
C301450832
C301450833
C301450834
C301450835
Number of inter frequency HS-DSCH to DCH attempt due to moving
C301450836
Number of inter frequency HS-DSCH to DCH failure due to moving
C301450837
C301450838
C301450839
C301450840
C301450841
202
Counter No.
Description
C301450842
C301450843
C301450844
Number of intra frequency DCH to HS-DSCH attempt due to moving
C301450845
C301450846
C301450847
C301450848
C301450849
Number of intra frequency DCH to HS-DSCH failure due to moving
C301450850
C301450851
C301450852
C301450853
Number of inter frequency DCH to HS-DSCH attempt due to moving
C301450854
C301450855
C301450856
C301450857
C301450858
Number of inter frequency DCH to HS-DSCH failure due to moving
C301450859
C301450860
C301450861
C301451186
Number of intra frequency E-DCH to DCH attempt due to moving
C301451187
C301451188
C301451189
C301451190
C301451191
Number of intra frequency E-DCH to DCH failure due to moving
C301451192
C301451193
C301451194
C301451195
Number of inter frequency E-DCH to DCH attempt due to moving
C301451196
C301451197
C301451198
C301451199
C301451200
Number of inter frequency E-DCH to DCH failure due to moving
C301451201
C301451202
C301451203
203
Counter No.
Description
C301451204
Number of intra frequency DCH to E-DCH attempt due to moving
C301451205
C301451206
C301451207
C301451208
C301451209
Number of intra frequency DCH to E-DCH failure due to moving
C301451210
C301451211
C301451212
C301451213
Number of inter frequency DCH to E-DCH attempt due to moving
C301451214
C301451215
C301451216
C301451217
C301451218
Number of inter frequency DCH to E-DCH failure due to moving
C301451219
C301451220
C301451221
13.1.9
Cell HSPA Handover to 2G Statistics

Counter No.
Description
C301460862
Number of HS-DSCH to 2G handover attempt
C301460863
C301460864
C301460865
Number of HS-DSCH to 2G handover failure
C301460866
C301460867
C301461173
Number of E-DCH to 2G handover attempt
C301461174
C301461175
C301461176
Number of E-DCH to 2G handover failure
C301461177
C301461178
13.1.10
Cell Inter-RAT Handover Statistics

Counter No.
Description
C301490941
Number of attempted incoming inter-RAT handover for CS domain
204
Counter No.
Description
C301490942
C301490943
C301490944
C301490945
C301490946
C301490947
C301490948
C301490949
C301490950
Number of failed incoming inter-RAT handover for CS domain
C301490951
C301490952
C301490953
Number of attempted incoming inter-RAT handover for PS domain
C301490954
Number of successful incoming inter-RAT handover for PS domain
C301490955
C301490956
C301490957
C301490958
C301490959
Number of attempted relocation preparation for outgoing CS interRAT handovers
C301490960
C301490961
C301490962
C301490963
C301490964
C301490965
C301490966
C301490967

handovers
C301490968
C301490969
C301490970
C301490971
C301490972
C301490973
C301490974
C301490975
Number of failed outgoing CS inter-RAT handovers
C301490976
C301490977
C301490978
C301490979
Number of failed outgoing PS inter-RAT handovers
205
Counter No.
Description
C301490980
C301490981
C301490982
C301490983
13.1.11
Inter-cell Hard Handover Statistics

Counter No.
Description
C301500000

attempt
C301500001
C301500002
C301500003
C301500004
C301500005

failure
C301500006
C301500007
C301500008
C301500009

attempt
C301500010
C301500011
C301500012
C301500013
C301500014

failure
C301500015
C301500016
C301500017
C301500018

handover attempt
C301500019
C301500020
C301500021
C301500022
C301500023

handover failure
C301500024
C301500025
C301500026
C301500027

handover attempt
206
Counter No.
Description
C301500028
C301500029
C301500030
C301500031
C301500032

handover failure
C301500033
C301500034
C301500035
C301500036

attempt
C301500037
C301500038
C301500039
C301500040
C301500041

failure
C301500042
C301500043
C301500044
C301500045

attempt
C301500046
C301500047
C301500048
C301500049
C301500050

failure
C301500051
C301500052
C301500053
C301500054
Number of outgoing inter-RNC intra frequency hard handover

switching in the CN attempt
C301500055
C301500056
C301500057
C301500058
C301500059
Number of outgoing inter-RNC intra frequency hard handover

switching in the CN failure
C301500060
C301500061
C301500062
C301500063
Number of outgoing inter-RNC inter frequency hard handover

switching in the CN attempt
207
Counter No.
Description
C301500064
C301500065
C301500066
C301500067
C301500068
Number of outgoing inter-RNC inter frequency hard handover

switching in the CN failure
C301500069
C301500070
C301500071
13.1.12
Inter-cell Soft Handover Statistics

Counter No.
Description
C301770072
Number of attempted radio link addition for soft handover between

cells
C301770073
Number of Successful radio link addition for soft handover between

cells
C301770074
C301770075
C301770076
C301770077
C301770078
Number of failed radio link addition for soft handover between

cells,by cause
C301770079
C301770080
C301770081
C301770082
Number of attempted radio link deletion for soft handover between

cells
C301770083
Number of Successful radio link deletion for soft handover between

cells
C301770084
C301770085
C301770086
C301770087
C301770088
Number of failed radio link deletion for soft handover between

cells,by cause
C301770089
C301770090
C301770091
C301770092
Number of attempted soft handover between cells
C301770093
Number of Successful soft handover between cells
C301770094
Number of failed soft handover between cells,by cause
C301770095
208
Counter No.
Description
C301770096
C301770097
C301770098
C301770099
C301770100
C301770101
C301770103
13.1.13
Statistics of soft handover between cells for monitor set
Inter-RAT Cell Handover Statistics

Counter No.
Description
C301510000
C301510001
C301510002
C301510003
C301510004
Number of attempted relocation preparation for outgoing CS interRAT handovers
C301510005
C301510006
C301510007
C301510008
C301510009
C301510010
C301510011
C301510012

handovers
C301510013
C301510014
C301510015
C301510016
C301510017
C301510018
C301510019
C301510020
Number of failed outgoing CS inter-RAT handovers
C301510021
C301510022
C301510023
C301510024
Number of failed outgoing PS inter-RAT handovers
C301510025
C301510026
C301510027
209
Counter No.
Description
C301510028
13.2
Alarm List
This feature has no related alarm.
14
Glossary
B
BLER
Block error ratio
C
CIO
CPICH
Common Pilot Channel
CS
Circuit switched
CTCP
Common transmitted carrier power
D
DTCP
Dedicated transmitted code power
E
Ec/No
band
Received energy per chip divided by the power density in the
G
GSM
Global system for mobile communciations
GERAN
GSM/EDGE Radio Access Network
H
HSDPA
High speed downlink packet access
HSUPA
High speed uplink packet access
I
IMS
IP Multimedia Sub-system
IMSI
International Mobile Subscriber Identity
210
M
MBMS
Multimedia Broadcast Multicast Service
O
OLPC
Outer loop power control
P
PS
Packet switched
R
RAB
Radio access bearer
RNC
Radio network controller
RRC
Radio resource control
RSCP
Received Signal Code Power
S
SF
Spreading Factor
SIR
Signal to interference ratio
T
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
U
UE
User equipment
UTRAN
UMTS Terrestrial radio access network
W
WCDMA
Wideband CDMA, Code division multiple access
211

ZTE UMTS Handover Control Feature Description PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE UMTS Handover Control Feature Description PDF

Uploaded by

Copyright:

Available Formats

Handover Control

Handover Control Feature Description

Handover Control Feature Description

2008 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Handover Control Feature Description

Functional Attribute ................................................................................................... 1

Compressed Mode Strategy...................................................................................... 9

Intra-Frequency Handover Strategy ....................................................................... 13

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Handover Control Feature Description

Inter-Frequency Handover Strategy ....................................................................... 31

SRNS Relocation ...................................................................................................... 46

Inter-RAT Handover Policy...................................................................................... 50

IMSI-based handover ............................................................................................... 62

HSDPA-related special strategy ............................................................................. 65

HSUPA-related special strategy ............................................................................. 68

MBMS-related special strategy............................................................................... 72

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Handover Control Feature Description

parameters and configurations .............................................................................. 73

This parameter indicates whether PCPICH transmission power is configured.................. 105

Counter And Alarm ................................................................................................ 190

Glossary .................................................................................................................. 210

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Handover Control Feature Description

Figures and Tables

Transmission Gap (TG) position.................................................................................. 10

Parameters of compressed mode ............................................................................... 11

Procedure for E-DCH fallback to DCH prior to initiation of compressed mode........... 12

Intra-frequency handover index quotations ................................................................. 16

Cell priority configuration ............................................................................................. 18

Time-To-Trigger mechanism ....................................................................................... 22

Intra-frequency handover index quotations ................................................................. 24

Intra-RNC soft handover (Add a radio link) ................................................................. 26

Intra-RNC soft handover (Delete a radio link) ............................................................. 27

Intra-RNC soft handover (Swap a radio link)............................................................... 28

Intra-RNC hard handover procedure ........................................................................... 29

Inter-RNC hard handover through lur interface ........................................................... 30

Inter-RNC hard handover without lur interface............................................................ 31

Inter-frequency handover index quotations ................................................................. 40

Cell priority configuration ............................................................................................. 41

Example of slow-moving UE judging conditions.......................................................... 45

Example of fast-moving UE judging condition ............................................................. 45

SRNC relocation procedure (Span two CNs ) ............................................................. 47

Relocation triggered by soft handover......................................................................... 48

Relocation triggered by hard handover ....................................................................... 49

Indexing relation for Inter-RAT handover .................................................................... 56

Priority settings of cells ................................................................................................ 57

PS service reselection initiated by an UE in the case of 3G to 2G handover ............. 62

PS service reselection initiated by the RNC in the case of 3G to 2G handover ......... 62

Schematic Diagram of Querying Whether a SRNC Cell Is Authorized According to

Schematic Diagram of Querying Whether a DRNC Cell Is Authorized According to

Correspondence between handover and compressed modes...................................... 2

Parameters of compressed mode ............................................................................... 11

Table of Principle ......................................................................................................... 72

Parameter Description ................................................................................................. 76

Parameter Description ................................................................................................. 78

Default Value of the UE Intra-frequency Measurement Configuration Parameters