102907285-11

Handover Control WCDMA RAN

Feature Guide

Operator Logo

Handover Control Feature Description

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I

Handover Feature Guide

Version Date Author Approved By Remarks

V4.5 2010-10-15 ZhangBo Liu Min

© 2010 ZTE Corporation. All rights reserved.

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

disclosed or used without the prior written permission of ZTE.

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

is subjected to change without notice.


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I

TABLE OF CONTENTS

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

2 Overview .............................................................................................................. 1

2.1 Function Introduction ............................................................................................ 1 2.1.1 Soft/Softer Handover ............................................................................................ 3 2.1.2 Intra-Frequency Hard Handover ........................................................................... 3 2.1.3 Inter-Frequency Hard Handover ........................................................................... 4 2.1.4 Inter-RAT Mobility ................................................................................................. 4 2.1.5 Inter-RNC Handover with Iur Support .................................................................. 6 2.1.6 Directed Signalling Connection Re-establishment ............................................... 6 2.1.7 Coverage Based Handover .................................................................................. 6 2.1.8 Compressed Mode................................................................................................ 6 2.1.9 Neighboring Cells Priorities .................................................................................. 7 2.1.10 Handover Based on Dedicated Downlink Transmit Power .................................. 7 2.1.11 Handover Based on Dedicated Uplink Transmit Power (UE) .............................. 7 2.1.12 Quality Based Handover ....................................................................................... 7 2.1.13 SRNS Relocation .................................................................................................. 7 2.1.14 IMSI-based Handover ........................................................................................... 7 2.1.15 Inter-RAT PS Handover ........................................................................................ 8 2.1.16 DTM Handover ...................................................................................................... 8 2.1.17 NACC .................................................................................................................... 8 2.1.18 Target Cell Load Based Inter-RAT Handover ...................................................... 8 2.1.19 Handover Strategy Based on Service Type ......................................................... 8 2.1.20 Enhanced Iur-g...................................................................................................... 8 2.1.21 HS-DSCH Serving Cell Change ........................................................................... 8 2.1.22 HS-DSCH Inter-RAT Reselection ......................................................................... 9 2.1.23 HSDPA Soft/Softer Handover of A-DPCH............................................................ 9 2.1.24 HSDPA over Iur..................................................................................................... 9 2.1.25 HSUPA Soft/Softer Handover of A-DPCH............................................................ 9 2.1.26 E-DCH Serving Cell Change Inside Active Set .................................................... 9 2.1.27 E-DCH Intra-frequency Hard Handover ............................................................... 9 2.1.28 E-DCH Inter-frequency Hard Handover ............................................................. 10 2.1.29 HSUPA over Iur................................................................................................... 10 2.1.30 HSUPA Inter-RAT Reselection ........................................................................... 10

3 Compressed Mode Strategy ............................................................................ 10

3.1 Introduction to Compressed Mode ..................................................................... 10 3.2 Compressed Mode Strategy ............................................................................... 12 3.3 Compressed Mode Configuration Strategy via RNC ......................................... 14

4 Intra-Frequency Handover Strategy ............................................................... 15

4.1 Intra-Frequency Measurement ........................................................................... 15 4.1.1 Introduction to Intra-Frequency Measurement ................................................... 15 4.1.2 Measurement Control Method Related to Active Set and Monitored set .......... 16 4.1.3 Neighboring Cells Configuration ......................................................................... 19 4.2 Handling Mechanism for Period-based Report of Intra-Frequency Handover

Measurement...................................................................................................... 21


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. II

4.3 Intra-Frequency Handover Decision................................................................... 21 4.3.1 Event 1A-Triggered Handover ............................................................................ 21 4.3.2 Event 1B-Triggered Handover ............................................................................ 22 4.3.3 Event 1C-Triggered Handover............................................................................ 23 4.3.4 Event 1D-Triggered Handover............................................................................ 24 4.3.5 Time-To-Trigger Mechanism Used to Control Event Report ............................. 25 4.3.6 Handling of Intra-Frequency Events ................................................................... 25 4.3.7 Detected set Handover ....................................................................................... 26 4.3.8 Detected Set Tracing .......................................................................................... 27 4.3.9 Processing of the Rx-Tx time difference of a UE in macro diversity.................. 28 4.3.10 IUB transmission bandwidth limitation strategy.................................................. 29 4.3.11 Decision on support-CS64k traffic of target cell ................................................. 30 4.3.12 Scenarios of Intra-Frequency hard handover..................................................... 30 4.3.13 The disposal strategy of intra-frquency events in buffer .................................... 31 4.4 Intra-Frequency Handover Procedure ................................................................ 33 4.4.1 Inter-RNC Soft Handover (Add a Radio Link) .................................................... 33 4.4.2 Inter-RNC Soft Handover (Delete a Radio Link) ................................................ 34 4.4.3 Inter-RNC Soft Handover (Swap a Radio Link).................................................. 35 4.4.4 Intra-RNC Hard handover ................................................................................... 36 4.4.5 Inter-RNC Hard Handover Through lur Interface ............................................... 37 4.4.6 Inter-RNC Hard Handover Without lur Interface ................................................ 38

5 Inter-Frequency Handover Strategy ............................................................... 39

5.1 Inter-Frequency Measurement ........................................................................... 40 5.1.1 Introduction to Inter-Frequency Measurement ................................................... 40 5.1.2 Inter-Frequency Measurement Control Method ................................................. 43 5.1.3 Neighboring Cells Configuration ......................................................................... 50 5.2 Handling Mechanism for Period-based Report of Inter-Frequency Handover

Measurement...................................................................................................... 52 5.3 Downlink Coverage Based Inter-Frequency Handover...................................... 52 5.4 Uplink BLER Based Inter-Frequency Handover................................................. 52 5.5 Uplink Transmit Power Based Inter-Frequency Handover ................................ 53 5.6 Downlink Transmit Power Based Inter-Frequency Handover ............................ 53 5.7 Load Control Based Handover ........................................................................... 53 5.8 Moving Speed Based Handover ......................................................................... 54 5.9 Coupling Handling of Different Handovers ......................................................... 55 5.10 Inter-Frequency Handover Procedure ................................................................ 56

6 Inter-RNC Mobility............................................................................................. 56

6.1 SRNS Relocation ................................................................................................ 56 6.1.1 Relocation Triggered by Soft Handover ............................................................. 57 6.1.2 Relocation Triggered by Hard Handover ............................................................ 59 6.2 DSCR .................................................................................................................. 60 6.3 Coupling between relocation and DSCR ............................................................ 61

7 Inter-RAT Handover Policy .............................................................................. 61

7.1 Inter-RAT Measurement ..................................................................................... 61 7.1.1 Overview of Inter-RAT Measurement ................................................................. 62 7.1.2 Control Methods for Inter-RAT Measurement .................................................... 63 7.1.3 Neighboring Cells Configuration ......................................................................... 69 7.2 Inter-RAT Handover Based on Downlink Coverage .......................................... 71


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. III

7.3 Inter-RAT Handover Based on Uplink BLER ..................................................... 71 7.4 Inter-RAT Handover Based on Uplink Transmit Power ..................................... 72 7.5 Inter-RAT Handover Based on Downlink Transmit Power................................. 72 7.6 Handover Based on Load Control ...................................................................... 72 7.7 Inter-RAT Handover based on GSM Load ......................................................... 73 7.7.1 Acquirement and Update of GSM Load Condition .......................................... 73 7.7.2 Inter-RAT Handover based on GSM Load Process ........................................... 73 7.8 Coupling for Different Handover Causes............................................................ 74 7.9 Inter-RAT Handover Process.............................................................................. 75 7.9.1 CS Service Handover from 3G System to 2G System....................................... 75 7.9.2 PS Service Reselection in 3G to 2G Handover.................................................. 75

8 IMSI-based handover........................................................................................ 78

8.1 Querying Whether a SRNC Cell Is Authorized According to IMSI..................... 79 8.2 Querying Whether a DRNC Cell Is Authorized According to IMSI .................... 80

9 HSDPA-related special strategy ...................................................................... 81

9.1 Overview ............................................................................................................. 81 9.2 Intra-frequency Handover ................................................................................... 82 9.3 Inter-frequency Handover ................................................................................... 83 9.4 Inter-RAT Handover ............................................................................................ 84

10 HSUPA-related special strategy ...................................................................... 84

10.1 Overview ............................................................................................................. 84 10.2 Intra-frequency Handover ................................................................................... 85 10.3 Inter-frequency Handover ................................................................................... 87 10.4 Inter-RAT Handover ............................................................................................ 88

11 MBMS-related special strategy ....................................................................... 88

11.1 Intra-frequency Handover ................................................................................... 89 11.2 Inter-frequency Handover ................................................................................... 89

12 Parameters and Configurations ...................................................................... 90

12.1 Intra-Frequency Handover Parameters .............................................................. 90 12.1.1 Parameter List ..................................................................................................... 90 12.1.2 Parameter Configuration..................................................................................... 92 12.2 Inter-Frequency Handover Parameters ............................................................ 111 12.2.1 Parameter List ................................................................................................... 111 12.2.2 Parameter Configuration................................................................................... 113 12.3 SRNC Relocation Parameters .......................................................................... 133 12.3.1 Parameter List ................................................................................................... 133 12.3.2 Parameter Configuration................................................................................... 133 12.4 Inter-RAT Handover Parameters ...................................................................... 135 12.4.1 Parameter List ................................................................................................... 135 12.4.2 Parameter Configuration................................................................................... 137 12.5 IMSI-based Handover Parameters ................................................................... 158 12.5.1 Parameter List ................................................................................................... 158 12.5.2 Parameter Configuration................................................................................... 159 12.6 HSDPA Handover Parameters ......................................................................... 166 12.6.1 Parameter List ................................................................................................... 166 12.6.2 Parameter Configuration................................................................................... 166


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. IV

12.7 HSUPA Handover Parameters ......................................................................... 167 12.7.1 Parameter List ................................................................................................... 167 12.7.2 Parameter Configuration................................................................................... 168 12.8 MBMS Handover Parameters........................................................................... 169 12.8.1 Parameter List ................................................................................................... 169 12.8.2 Parameter Configuration................................................................................... 169

13 Counter And Alarm ......................................................................................... 170

13.1 Counter List ....................................................................................................... 170 13.1.1 RNC Soft Handover Statistics........................................................................... 170 13.1.2 RNC Hard Handover Statistics ......................................................................... 175 13.1.3 Cell Relocation Statistics .................................................................................. 181 13.1.4 Inter-RAT Cell Handover Statistics ................................................................... 186 13.1.5 HSPA Serving Cell Change Statistics .............................................................. 194 13.1.6 Inter-cell Hard Handover Statistics ................................................................... 196 13.1.7 Inter-cell Soft Handover Statistics .................................................................... 199 13.1.8 Inter-cell Detected Set Statistics....................................................................... 201 13.1.9 Inter-RAT Inter-cell Handover Statistics ........................................................... 201 13.2 Alarm List .......................................................................................................... 203

14 Glossary ........................................................................................................... 204


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. V

FIGURES

Figure 3-1 Transmission Gap (TG) position .......................................................................... 11

Figure 3-2 Parameters of compressed mode ........................................................................ 12

Figure 3-3 Procedure for E-DCH fallback to DCH prior to initiation of compressed mode .. 13

Figure 4-1 Intra-frequency handover index quotations ......................................................... 18

Figure 4-2 Cell priority configuration...................................................................................... 20

Figure 4-3 Time-To-Trigger mechanism................................................................................ 25

Figure 4-4 Intra-frequency handover index quotations ......................................................... 27

Figure 4-5 Intra-RNC soft handover (Add a radio link) ......................................................... 33

Figure 4-6 Intra-RNC soft handover (Delete a radio link) ..................................................... 34

Figure 4-7 Intra-RNC soft handover (Swap a radio link) ....................................................... 35

Figure 4-8 Intra-RNC hard handover procedure ................................................................... 36

Figure 4-9 Inter-RNC hard handover through lur interface ................................................... 37

Figure 4-10 Inter-RNC hard handover without lur interface .................................................. 38

Figure 5-1 Inter-frequency handover index quotations ......................................................... 48

Figure 5-2 Cell priority configuration...................................................................................... 51

Figure 5-3 Example of slow-moving UE judging conditions .................................................. 55

Figure 5-4 Example of fast-moving UE judging condition ..................................................... 55

Figure 6-1 Relocation triggered by soft handover ................................................................. 57

Figure 6-2 Relocation triggered by hard handover................................................................ 59

Figure 7-1 Indexing relation for Inter-RAT handover............................................................. 68

Figure 7-2 Priority settings of cells ........................................................................................ 70

Figure 7-3 3G to 2G CS service handover ............................................................................ 75

Figure 7-4 PS service reselection initiated by an UE in the case of 3G to 2G handover ..... 76

Figure 7-5 PS service reselection initiated by the RNC in the case of 3G to 2G handover . 77

Figure 8-1 Schematic Diagram of Querying Whether a SRNC Cell Is Authorized According to IMSI ....................................................................................................................................... 80

Figure 8-2 Schematic Diagram of Querying Whether a DRNC Cell Is Authorized According to IMSI ....................................................................................................................................... 81

TABLES


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. VI

Table 2-1 Correspondence between handover and compressed modes............................... 2

Table 3-1 Parameters of compressed mode ......................................................................... 12

Table 11-1 Table of Principle ................................................................................................. 89

Table 12-1 Default Value of the UE Intra-frequency Measurement Configuration Parameters Related to Traffic Category....................................................................................................... 99

Table 12-2 Service Type Related UE Inter-frequency Measurement Parameter ConfigurationDefault Value..................................................................................................... 124

Table 12-3 Service Type Related UE Inter-RAT Measurement Parameter Configuration Default Value .......................................................................................................................... 142


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 1

1 Functional Attribute

System version: [RNC V3.09, OMMR V3.09, Node B V4.09, OMMB V4.09]

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].

2 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, inter-

frequency 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 inter-

frequency/Inter-RAT measurement. The following table lists the correspondence

between handover and compressed modes.

Table 2-1 Correspondence between handover and compressed modes

Softer handover

Soft handover

Hard handover

Require compression or not

Intra-frequency Y Y Y N

Inter-frequency N N Y Y

Inter-RAT N N Y Y

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-RNC(with IUR)Handover

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)



QoS-based Handover

IMSI-based Handover

Associated Channel Soft/Softer Handover of HSDPA

Associated Channel Soft/Softer Handover of HS UPA

Different Active Sets of E-DCH and DCH

Handover Strategy Based on Service

SRNS Relocation

2.1.1 Soft/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 int ra-

frequency 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 cell before 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.



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 Handover with Iur Support

The feature supports maintaining communication continuity in the case of a UE in

CELL_DCH state moving among inter-RNC cells. Iur interface is configured between

different RNCs to support that a UE maintains the original connection with the CN when

handing over in the coverage areas of different RNCs. There is no need to trigger the

SRNS relocation, so as to reduce the effects of SRNS relocation on service quality.

2.1.6 Directed Signalling Connection Re-establishment

The feature enables RNC to support that UE with ongoing PS service can trigger DSCR

procedure in order to interoperate with the RNC which cannot support SRNS relocation

procedure.

2.1.7 Coverage Based Handover

The feature supports utilizing the measurement report to judge the quality of radio l ink

and thus to perform handover to guarantee the service quality of the user in the case of

changing network coverage condition.

RNC supports controlling the UE to perform the intra-frequency, the inter-frequency and

the inter-RAT measurement and judges the radio link quality according to the

measurement resultof event triggerred report to trigger various handovers: soft/softer

handover, intra-frquency hard handover, inter-frequency hard handover and inter-RAT

handover. RNC also supports configuating diffe rent handover parameters for different

services.

2.1.8 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.9 Neighboring Cells Priorities

The feature supports configuring different priorities for different cells in adjacent cell list.

It makes a UE hand over to an adjacent cell of high priority at a higher success rate to

improve the handover performance of the system.

2.1.10 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.11 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.12 Quality 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 Inter-

RAT adjacent cell as quick as possible to avoid call drop.

2.1.13 SRNS Relocation

This feature supports that a UE in the CELL_DCH state transfers service to a new RNC

when moving among adjacent RNC cells. When there is not Iur interface between RNCs,

SRNS relocation can maintain continuous service. When there is Iur interface between

RNCs, SRNS relocation triggered timely can reduce the transmission resource

consumption at the Iur interface.

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 Inter-RAT PS Handover

The feature shortens the PS service interruption when there is a handover between

inter-RAT adjacent cells. With this feature, PS service continuityis enhanced, especially

for real-time packet service with higher QoS requirements. And user experience get

improved.

2.1.16 DTM Handover

The feature guarantees the CS service continuity combined with PS service during inter-

RAT moving. It improves user experience.

When UE with CS and PS service simultaneously moves between inter -RAT adjacent

cells, CS and PS service are handed over to inter-RAT cell in parallel via DTM

mechanism.

2.1.17 NACC

PS service will be interrupted when it is handed over to GERAN via cell reselection

procedure, which leads to bad user experience. Network Assisted Cell Change (NACC)

reduces the duration of UE inter-RAT cell reselection procedure by system information is

sended in advance.

2.1.18 Target Cell Load Based Inter-RAT Handover

The feature enables RNC to get load of 2G adjacent cells. RNC will select a GSM

adjacent cell with lower load as target cell when UE is handed over to GSM from UMTS.

2.1.19 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.

2.1.20 Enhanced Iur-g

The feature supports the enhaced Iur-g interface between GERAN BSC and 3G RNC. It

enables RNC to get capability and load of 2G cell. By employing the interface, inter-RAT

load balance can be achieved, inter-RAT handover success ratio is improved and

handover delay is decreased.

2.1.21 HS-DSCH Serving Cell Change

The HS-PDSCH has only one serving cell. During intra-system soft handover, if HS-

PDSCH exists before and after handover when the best cell changes(1D event



triggering), HS-PDSCH serving cell change will be t riggered. If there exists an HS-

PDSCH before and after hard handover, the HS-PDSCH serving cell must change.

2.1.22 HS-DSCH Inter-RAT Reselection

The feature ensures service continuity when HSDPA users moving from UMTS cell to

GSM cell. When HSDPA user with service carried on HS -DSCH channel is needed to

handover from UTMS cell to GSM cell, RNC can hand over UE to connect GSM cell

directly without falling HS-DSCH back to DCH before inter-RAT handover.

2.1.23 HSDPA Soft/Softer Handover of A-DPCH

The HSDPA service supports soft/softer handover of associated DPDCH/DPCCH, with

the policy identical with that of common soft/softer handover.

2.1.24 HSDPA over Iur

The feature enables that data transmission on HS-DSCH is retaining without HS-DSCH

falling back to DCH when HSDPA subscriber is handed over between different RNCs

over Iur.

2.1.25 HSUPA Soft/Softer Handover of A-DPCH

The HSUPA service supports soft/softer handover of associated DPDCH/DPCCH, with

the policy identical with that of common soft/softer handover.

2.1.26 E-DCH Serving Cell Change Inside 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 intra-

system soft handover. If there exists an E-DCH before and after hard handover, the E-

DCH serving cell must change.

2.1.27 E-DCH Intra-frequency Hard Handover

The procedure of E-DCH intra-frequency hard handover is similar with DCH int ra-

frequency hard handover. If target cell supports HSUPA, intra-frequency hard handover

will accompany with E-DCH serving cell change, otherwise E-DCH will fall back to DCH.



2.1.28 E-DCH Inter-frequency Hard Handover

The procedure of E-DCH inter-frequency hard handover is similar with DCH inter-

frequency hard handover. If target cell supports HSUPA, inter-frequency hard handover

will accompany with E-DCH serving cell change, otherwise E-DCH will fall back to DCH.

2.1.29 HSUPA over Iur

The feature enables that data transmission on E-DCH is retaining without E-DCH falling

back to DCH when HSUPA subscriber is handed over between different RNCs over Iur.

2.1.30 HSUPA Inter-RAT Reselection

The feature ensures service continuity when HSUPA users moving from UMTS cell to

GSM cell. When HSUPA user with service carried on E-DCH channel is needed to

handover from UTMS cell to GSM cell, RNC can hand over UE to connect GSM cell

directly without falling E-DCH back to DCH before inter-RAT handover.

3 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.

2 Higher Layer Scheduling

The higher layer scheduling is in nature a strategy in which the higher layer adjusts

and controls the data transmission rate. Some 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 3-1.

Figure 3-1 Transmission Gap (TG) position

#14#Nfirst-1

(1) Single-frame method

(2) Double-frame method

First radio frame Second radio frame

Radio frameTransmission gap

Transmission gap

#0

#14

#Nlast+1

#Nfirst-1 #Nlast+1#0

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 3-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.



Figure 3-2 Parameters of compressed mode

Transmission

gap 2

TGSN

TGL2

TG pattern 1

#TGPRC

gap 1

Transmission

TGD

TGPL1

TG pattern 1

TGL1

#1 #2 #3 #4 #5

TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1

3.2 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 real time 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.

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 3-1 Parameters of compressed mode

GSM adjacent cell measurement FDD adjacent cell measurement

TGSN 4 (Slots) 3 (Slots)



GSM adjacent cell measurement FDD adjacent cell measurement

TGL1 7 (Slots) 7 (Slots)

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

DCH.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 E-

DCH 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

Guide) before initiating the compressed mode. Figure 3-3 shows the procedure in which

E-DCH falls back to DCH before the initiation of compressed mode.

Figure 3-3 Procedure for E-DCH fallback to DCH prior to initiation of compressed mode

NodeBRNC

Radio Link Reconfiguration Prepare

UE

Measurement Report (Event 2d)

Radio Link Reconfiguration Commit

Radio Bearer Reconfiguration Complete

Radio Bearer Reconfiguration(E-DCH to DCH)

Radio Link Reconfiguration Ready

HS-DSCH/E-DCH

Radio Link Reconfiguration Prepare

Radio Link Reconfiguration Commit

Physical Channel Reconfiguration Complete

Physical Channel Reconfiguration (Activate Compressed Mode)

Radio Link Reconfiguration Ready

Compressed Mode Command

Measurement Control

E-DCH downgrade

to DCH

parameters setting

Compressed mode

Activation

(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.).



For all commercial terminals in current market, the compressed mode can be initiated

directly when services are carried on HS-DSCH.

(whether HS-DSCH falls back to DCH before initiation of compressed mode is controlled

through the parameter HsdpaCmAssoMode. If the parameter value is “Serial”, HS-DSCH

needs to fall back to DCH before the initiation of compressed mode.If the parameter

value is “Parallel”, the compressed mode is initiated directly.).

In the procedure of service setup, state transition, call re-establishment and relocation

from other RNC/system to local RNC, RNC will configure accompanying compressed

mode through RADIO BEARER SETUP/RADIO BEARER RECONFIGURATION to UE

and RADIO LINK SETUP REQUEST/RADIO LINK RECONFIGURATION to NodeB.

After service setups up successfully, since the neighboring cell relation changes or the

value of IfOrRatHoSwch or ServHoSwch changes duing to the best cell change(for example,

the best cell change from the cell with only supporting inter-frequency handover to the

cell with only supporting inter-RAT handover), RNC will configure dedicated compressed

mode through PHYSICAL CHANNEL RECONFIGURATION to UE and RADIO LINK

RECONFIGURATION REQUEST to NodeB.

3.3 Compressed Mode Configuration Strategy via

RNC

For inter-RNC handover, some vendors don’t support accompanying compressed mode.

To guarantee the normal procedure via IUR, ZTE performs the special strategy as

follows:

DRNC doesn’t support accompanying compressed mode

RncFeatSwitch Bit9 indicates whether neighboring RNC supports accompany configure

compressed mode parameters. If compressed mode is not activated in SRNC side, then

the method of configuration compressed mode is decided by RncFeatSwitch Bit9.

Otherwise RncFeatSwitch Bit9 is invalid, and SRNC configures compressed mode

parameters accompany and activates compressed mode.

DRNC partly supports accompanying compressed mode

Some vendors only support one type of accompanying compressed mode (inter-

frequency or inter-RAT). CompMdCfgStra is used to indicate strategy of accompanying

compressed mode configuration. When inter-frequency and inter-RAT neighboring cells

exist, if the value of CompMdCfgStra is “0”, RNC will configure two types of accompanying

compressed mode(inter-frequency and inter-RAT) ,else if the value of CompMdCfgStra is “1”,

RNC will configure only one type of accompanying compressed mode(inter-frequency or

inter-RAT) based on the specific value of IfOrRatHoSwch.



4 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 int ra-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:

nnn MaFaF 1)1(

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-frquency measurement means to perform measurement on intra-frequency cells.

Only event-based method of reporting measurement result is supported, and parameter

SofthoMthd is invalid. The event-based report method means the UE judges whether

intra-frequency events are met based on the quality measurement result of cell

PCPICH.If so, it reports intra-frequency events (including such information as event ID,

and target cell) to the RNC.



A series of int ra-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.



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.

4.1.2.3 Measurement Deletion

Upon receiving exceptional int ra-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 configuration strategy 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.

For handover in inter-RNC, if there has SRNC cell in active set, the measurement

parameters of the best cell in SRNC will be used as handover parameters, and if

there is no SRNC cell in activeset, the measurement parameters of the last SRNC

cell in active set will be used as handover parameters.

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



SoftHoMth (Period- or event-based report, only event-based

report method is supported, and the following parameters related to period

report method are invalid: PrdMeasEcNo(Intra), PrdMeasRSCP(Intra),

PrdRptAmount(Intra) and PrdRptInterval(Intra))

Service bearer type (TrfCategory(CIntra))

RT RAB Including Voice

RT RAB Excluding Voice

Single NRT on DL DCH/UL DCH

Single NRT RAB on DL HS-DSCH/UL DCH

Single NRT RAB on DL HS-DSCH/UL E-DCH

All Multi-NRT RAB on DL DCH/UL DCH

Multi-NRT RAB, HSPA is Involved and only DCHs are Used in UL

Multi-NRT RAB, HSPA is Involved and E-DCH is Used in UL

Not Related to Service Type (Used for detected set measurement)

Remark:

(1) When concurrent service exists and includes AMR service, index to RT RAB

Including Voice configuration.

(2) When concurrent service exists and includes non-AMR service, index to RT

RAB Excluding Voice configuration.

(3) When the above principles are met simultaneously, comply with the first one.

To facilitate parameter modification and optimization, the intra-frequency parameters are

index-organized, with the index quotations listed as follows:

Figure 4-1 Intra-frequency handover index quotations

Utran Cell (utranCell)UE Intra-frequence Measurement

Configuration (Intra)

UE Intra-frequence Measurement

Relative to Traffic Category

Configuration Information (CIntra)

TrfCatIntraMIdx

IntraMeasQuan

TrfCategory:







Multi-NRTRAB, HSPA is Involved and only DCHs are Used in UL


Not Related to Service Type

IntraMeasCfgNo



Before obtaining intra-frequency handover parameters, first find the “Service Type-

Related Intra-frequency Measurement Parameter Index (TrfCatIntraMIdx)”, “UTRAN

Intra-frequency Radio Quality Measurement Quantity (IntraMeasQuan)” 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

(EvtMeasEcNo, EvtMeasRSCP)”; finally, find corresponding handover measurement

parameters from UE Int ra-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 intra-

frequency 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 int ra-frequency measurement cell

(RscpRptInd)

Whether to read SFN indication of target cell (ReadSFNInd)

Forbidden Cell Indicator for Event 1A/1B (FbdCellInd)

Measurement quantity. (MeasQuantity(Intra))

Measurement report mode (RptCrt(Intra))

Note: The parameters MeasQuantity(Intra) and RptCrt(Int ra) 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 Neighboring Cells Configuration

In neighboring cells configuration, adjacent cell list used for reselection in non-

CELL_DCH state and that used for handover in CELL_DCH state can be configured

separately. In handover, target cells are chosed by neighboring cells configuration state

(StateMode). When UE in macro diversity state, the neighboring cell list is the union of

neighboring cell list of each cell active set, then the number of intra -frequency



neighboring cells may exceed 32 which is the maximum number regulated by protocol. If

the number of intra-frequency neighboring cells exceeds 32, it needs to delete some

cells to ensure that there are only 32 intra-frequency neighboring cells. With minimal

impact on UE in active set, these dropped cells are those with poorer signal quality or

remoter geographical location. So each intra-frequency neighboring cell is configured

with a priority.

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 4-2 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 4-2 Cell priority configuration

Source Cell

Priority 0

Priority 1

Priority 2

4.1.3.2 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 intra-

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 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 which can buffer at most 64 truncated intra-frequency cells.

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 int ra-frequency adjacent

cell list, Number of cells in reserve list).

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 periodical ly reported by UE. If

several decision conditions are concurrently met, the RNC will handle events in the

sequence of 1D, 1A, 1C and 1B. Period report method is not supported.

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.

/2)H(RLogM10W)(1MLog10WCIOLogM10 1a1aBest

N

1i

iNewNew

A



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)).

M i: 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 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.

/2)H(RLogM10W)(1MLog10WCIOLogM10 1b1bBest

N

1i

iOldOld

A



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)).

M i: 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.

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.

/2HCIOLogM10CIOLogM10 1cInASInASNewNew

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.

M InAS: 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

(EvtRptAmount[MAX_INTRA_MEAS_EVENT]).

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

(RplcActThr[MAX_INTRA_MEAS_EVENT]).

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).

When the cell meets the conditions in the following formula, the UE reports Event 1D to

the RNC.

/2HCIOLogM10CIOLogM10 1dBestBestNotBestNotBest

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 E vent 1A only if the cell quality meets this reporting

range condition within TrigTime[MAX_INTRA_MEAS_EVENT] (Int ra), as shown in

Figure 4-3.

Figure 4-3 Time-To-Trigger mechanism

Reporting event 1A

Measurement quantity

Time

TrigTime[MAX_INTRA_MEAS_EVENT]

P CPICH 1 RptRange

[MAX_INTRA_MEAS_EVENT]

P CPICH 2

P CPICH 3

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 3.

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 3 .

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

The cell triggering Event 1D is an intra-frequency adjacent cell outside the active

set. if the criterion mentioned in “2.1.2 Intra-Frequency Hard Handover” is fulfilled,

RNC will perform intra-frequency hard handover.

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. And if event 1A or 1C is failure due to admission

control failure, RNC will perforem intra-frequency hard handover.

If the cell triggering Event 1D is within the active set, change the best cell in the

active set.

After Active Set Update is sent from RNC to UE, if Acti ve Set Update Complete is not

received in a period of time, RNC will consider active set update to fail.

4.3.7 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

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 or 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 (The parameters of detected set tracing is irrelevant to service type, which

means all sorts of service will be indexed by “Not Related to Service Type “ in service

type(TrfCategory)), with parameter index as follows:

Figure 4-4 Intra-frequency handover index quotations

Utran Cell (utranCell)UE Intra-frequence Measurement

Configuration (Intra)

UE Intra-frequence Measurement

Relative to Traffic Category

Configuration Information (CIntra)

TrfCatIntraMIdx

IntraMeasQuan

TrfCategory:


IntraMeasCfgNo

Before obtaining intra-frequency handover parameters, first find the “Service Type-

Related Intra-frequency Measurement Parameter Index (TrfCatIntraMIdx)”, “UTRAN

Intra-frequency Radio Quality Measurement Quantity (IntraMeasQuan)”, and “Soft

Handover Algorithm Selection (SoftHoMth)” from Ut ran Cell (utranCell) configuration

items; then find the “Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)”



from the UE Int ra-frequency Measurement Relative to Traffic Category Configuration

Information (CIntra) configuration items based on Tr fCatInt raMIdx, "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 “Int ra-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 if the parameter

NbrCellMonSupInd is 1. 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.

4.3.9 Processing of the Rx-Tx time difference of a UE in macro diversity

When a UE is in macro diversity, the uplink transmitting time of the UE is not adjusted.

The initial downlink channels can be correctly demodulated, but the downlink receiving

time will change along with the moving of the UE or with the drifting of the clock between

Node Bs. Therefore, the downlink receiving time may fall outside the time window of the

UE transmitting time T0 ± 148 chips, and consequently the UE cannot correctly

demodulate one or multiple downlink channels, causing the degradation of the UE

downlink quality or even call drop. For this reason, the 3GPP protocols have defined the

UE internal measurement events 6F and 6G for UE Rx-Tx time difference measurement:

6F event: The UE Rx-Tx time difference for a link in the active set is greater than an

absolute threshold.

6G event: The UE Rx-Tx time difference for a link in the active set is less than an

absolute threshold.

The RlRefTimeAjtSwit parameter controls the policy of the UE Rx-Tx time difference in

macro diversity. If the switch is on, the RNC removes the corresponding link from macro



diversity when the UE reports the 6F or 6G event (indicating that the downlink receiving

time already falls outside the UE transmitting time window). If the switch is off, the

function is disabled.

4.3.9.1 Related Measurement Procedure

(1)When the radiolink reference time adjust switch of the best cell (RlRefTimeAjtSwit ) is

on and the number of links in macro diversity changes from one to multiple, 6F/6G

measurement parameters will be issued to the UE.

(2)The internal measurement parameters (6F/6G) of the UE are configured per cell

according to the index. The measurement parameters configured for the UE are subject

to the parameters of the best cell. For a UE in macro diversity and on which the internal

measurement (6F/6F) function is enabled, i f the 6F/6G event parameters of the best cell

are different from the parameters issued to the UE, the parameter configuration of the

UE will be modified through measurement control.

(3)When the number of links in macro diversity changes from multiple to one and the

internal measurement function (6F/6G) is enabled on the UE, the release of internal

measurement will be triggered on the UE.

4.3.10 IUB transmission bandwidth limitation strategy

When constructing a network, there may be lack of Iub transmission resource. An

access of a high-rate UE may lead to numbers of other users inaccessibility to the

network. In order to avoid the case that some individual high-rate UE affect the

communication quality in large scale, it is necessary to limit the maximum rate of these

UE in the cell.

In the case of intra-RNC, for DCH users, parameters RtMaxUlRateDch /

RtMaxDlRateDch (for RT service) and NrtMaxUlRateDch / NrtMaxDlRateDch (for NRT

service) are used to limited the DCH maximum rate of uplink and downlink respectively.

For EDCH users, the E-DCH users’ maximum rates are limited by the parameters

RtMaxrateEdch (for RT service) and NrtMaxRateEdch (for NRT service).

In the case of inter-RNC, for DCH users, parameters RtMaxUlRateDchD /

RtMaxDlRateDchD (for RT service) and NrtMaxUlRateDchD / NrtMaxDlRateDchD (for

NRT service) are used to limited the DCH maximum rate of uplink and downlink

respectively. For EDCH users, the E-DCH users’ maximum rates are limited by

parameters RtMaxRateEdchD (for RT service) and NrtMaxRateEdchD (for NRT service).

If the related parameters are not configured in the neighboring cells, the restriction

decision does not effect.

Handling of adding a radio link in active set



1) For DCH users, if the GBR of DCH users is higher than the rate limitation

RtMaxUlRateDch / RtMaxDlRateDch of new neighboring cell, it doesn’t perform

adding a radio link, otherwise performs adding a radio link.

2) For EDCH users, if the rate of E-DCH users is higher than the EDCH rate limitation

RtMaxRateEdch / NrtMaxRateEdch of new neighboring cell, it will reduce E-DCH

Maximum Bitrate by radio link reconfiguration, and then add the corresponding

neighboring cell into macro diversity.

Handling of deleting a radio link in active set

1) For DCH users, perform deleting a radio link in macro diversity. If the UE rate is less

than the DCH rate limitation of cells in macro diversity, RNC will perform RB

reconfiguration.

2) For EDCH users, perform deleting a radio link in macro diversity. If the UE rate is

less than EDCH rate limitation of cells in macro diversity, RNC will perform RL

reconfiguration to enhance E-DCH Maximum Bitrate.

4.3.11 Decision on support-CS64k traffic of target cell

According to some special scenarios where CS64K traffic is not expected to

access/handover in a cell, parameters Cs64kSwitch and AdjCs64Switch are used to

control whether cells support CS64k traffic in SRNC and DRNC, respectively. When

CS64k traffic is restricted in a cell, ingoging, outgoing and handover of CS64k traffic

are forbidded.

When handover happens in intra-RNC cells and CS64k traffic is covered, if

Cs64kSwitch in target cell is closed and UE supports CS64k falling back to

AMR12.2k, then CS64k falls back to AMR12.2k and UE performs the related

disposal about handover, otherwise UE doesn’t perform any disposal.

When handover happens in inter-RNC cells and CS64k traffic is covered, if

AdjCs64kSwitch in target cell is closed and UE supports CS64k falling back to

AMR12.2k, then CS64k falls back to AMR12.2k and UE performs the related

disposal about handover, otherwise UE doesn’t perform any disposal. If the

configuration in DRNC cell and SRNC cell is not given, the cell is defaulted to

support CS64k.

4.3.12 Scenarios of Intra-Frequency hard handover

When soft handover cannot be realized in adjacent cells of intra-frequency for some

reasons, intra-frequency hard handover can guarantee the service continuity. The

scenarios where soft/softer handover is unavailable (intra-frequency hard handover must

be adopted) in the case of intra-frequency handover include:

Adding new link fails in soft handover when 1A or 1C event is triggered.



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.

Types of target and source cells are different(define 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.

The signal RB is carried on HS -DSCH in active cell, while F-DPCH is not supported

in soft add cell.

The capability of target cell is not consistent with that of source cell. Such as UE

uses transmit diversity in active set cell, but the target cell does not support

transmit diversity; UE uses multi-user detection in the active set cell, but the target

cell does not support multi-user detection; UE uses DTX-DRX in the active set cell,

but the target cell does not support the capability; uplink 16QAM is configurated but

the target cell does not support; TTI 2ms service is setup in source cell but the

target cell does not support; the transmission delay TimeDelay reported during

intra-frequency handover for the NodeB where the neighboring cell of the current

RNC resides is inconsistent with the t ransmission delay of the cells in the current

active set, or the transmission delay ATimeDelay reported during intra-frequency

handover for the neighboring cell that is a DRNC cell is inconsistent with the

transmission delay of the cells in the current active set

4.3.13 The disposal strategy of intra-frquency events in buffer

If RNC receives measurement events and discards them in unsteady state, it may miss

handover opportunity, and radio links with good signal may be not added in active set

while radio links with poor signal be still in active set. So it needs to cache measurement

reports in buffer in unsteady state and then perform the related disposal to such

measurement reports while RNC enters steady state. In unsteady state, RNC should

combine the received measurement reports, the strategy is as follows:

Events exist in buffer

1A 1B 1C 1D

New

measurement report

1A

If the

scramble

code in new 1A event is identical with

that in old 1A event, then old 1A event

is replaced by new one. Otherwise

new 1A event is cached.

1A event is cached

× 1A event is cached



1B 1B event is cached

The old 1B

event is

replaced by new one

1B event is cached

If the

scramble

code in 1B event is identical with

existedone, then 1D event is

replaced by 1B. Otherwise

1B is cached.

1C × 1C event is cached

The old 1C is

replaced by the new one

If the

replaced scramble code in 1C

event is identical with the existed

one in 1D event, then 1D event is

replaced by 1C. Otherwise

1C event is cached.

1D 1D event is cached

If scramble

code in 1D is identical with the one in

1B, then 1B event is replace by

1D. Otherwise 1D event is cached.

If scramble

code in 1D event is identical with

the replaced scramble code in 1C,

then 1C event is replaced by

1D. otherwise 1D event is cached

The old 1D

event is

replaced by the new one.



4.4 Intra-Frequency Handover Procedure

4.4.1 Inter-RNC Soft Handover (Add a Radio Link)

Figure 4-5 Intra-RNC soft handover (Add a radio link)

UE Node B

Drift RNS

Drift

RNC

Serving

RNC

DCH - FP DCH - FP

8. Downlink Synchronisation

RNSAP RNSAP

1. Radio Li nk Setup

Request

Start TX description

NBAP NBAP

2. Radio Link Setup

Request

RNSAP RN SAP

4. Radio Link Setup

Response

NBAP NBAP

3. Radio Link Setup Response

Start RX description

Decision to setup new RL

RRC RRC

11. DCCH : Active Set Update Complete

RRC RRC

10. DCCH : Active Set Update

[Radio Link Addition]

ALCAP Iur Bearer Setup 5. ALCAP Iub Bearer Setup

DCH - FP DCH - FP

9. Uplink Synchronisation

RNSAP RNSAP

7. Radio Link Restore Indication

NBAP NBAP




4.4.2 Inter-RNC Soft Handover (Delete a Radio Link)

Figure 4-6 Intra-RNC soft handover (Delete a radio link)

UE Node B

Drift RNS

Drift

RNC

Serving

RNC

RRCRRC2. DCCH : Active Set Update Complete

Decision to delete

old RL

RNSAP RNSAP

3. Radio Link Deletion

Request

NBAP NBAP


Request

RNSAP RNSAP


Response

NBAP NBAP


Response

Stop RX and TX

RRCRRC

1. DCCH : Active Set Update

[Radio Link Deletion]

ALCAP Iur Bearer Release7. ALCAP Iub Bearer Release



4.4.3 Inter-RNC Soft Handover (Swap a Radio Link)

Figure 4-7 Intra-RNC soft handover (Swap a radio link)

9 . U plink Synchronisation

R N SA P R N SA P

1 . R adio Link Setup

R equest

S tart T X

descrip tion

R N SA P R N SA P

4 . R adio Link Setup

R esponse

N B A P N B A P

2 . R adio Link Setup R equest

N B A P N B A P 3 . R adio Link Setup R esponse

S tart R X

descrip tion

D ecision to setup

new R L and

release o ld R L

N B A P

12 . R adio Link D eletion R equest

N B A P N B A P 13. R adio Link R elease R esponse

S top R X and T X

14 . A LC A P Iub D ata T ransport B earer R eleas e

R R C R R C

11 . D C C H : A ctive Set U pdate C om plete

R R C R R C

10 . D C C H : A ctive Set U pdate C om m and

[R adio L ink A ddition & D eletion]

N B A P

U E N ode B

D rift R N S

N ode B

Serving R N S

D rift

R N C

Serving

R N C

A LC A P Iur B earer Setup 5 . A LC A P Iub D ata T ransport B earer Setup

D C H -FP D C H -FP

D C H -FP D C H -FP

8 . D ownlink Synchronisation

R N SA P R N SA P

7 . R adio Link R estore

Indication

N B A P N B A P 6 . R adio Link R estore Indication



4.4.4 Intra-RNC Hard handover

Figure 4-8 Intra-RNC hard handover procedure

RADIO LINK SETUP REQUEST

RADIO LINK SETUP RESPONSE

PHYSICAL CHANNEL RECONFIGURATION

PHYSICAL CHANNEL RECONFIGURATION COMPLETE

RADIO LINK DELETION REQUEST

RADIO LINK DELETION RESPONSE

UE NODEB2 NODEB1 RNC



4.4.5 Inter-RNC Hard Handover Through lur Interface

Figure 4-9 Inter-RNC hard handover through lur interface

RNSAP RNSAP

1. Radio Link Setup Request

UE Node B

Source

Node B Target

RNC Source

RNC target

SRNC

RRC

RRC

12. DCCH : Physical Channel Reconfiguration Complete

RRC

7. DCCH : Physical Channel Reconfiguration

RRC

6. ALCAP Iur Data Transport Bearer Setup

NBAP NBAP

2. Radio Link Setup Request

NBAP NBAP

3. Radio Link Setup Response

NBAP

NBAP

14. Radio Link Deletion Request

NBAP

NBAP

15. Radio Link Deletion Response

4. ALCAP Iub Data Transport Bearer Setup

16. ALCAP Iub Data Transport Bearer Release

RNSAP

RNSAP

17. Radio Link Deletion Response

18. ALCAP Iur Data Transport Bearer Release

RNSAP

5. RL Setup Response

RNSAP

RNSAP 13. Radio Link Deletion Request

RNS AP

NBAP

NBAP

8. Radio Link Failure Indication

RNSAP RNSAP

9. Radio Link Failure Indication

NBAP

NBAP


RNSAP

11. RL Restore Indication

RNSAP

If the cells belong to different RNCs are adjacent and lur interface is available, the SRNC

performs inter-RNC hard handoff. The SRNC relocation is triggered after hard handover.



4.4.6 Inter-RNC Hard Handover Without lur Interface

Figure 4-10 Inter-RNC hard handover without lur interface

2 . R elocation R equired R A N A P R A N A P

R A N A P R A N A P

3 . R elocation R equest

R A N A P R A N A P


A cknow ledge

R A N A P R A N A P 1 . R elocation R equired

U E R N C

Source

R N C

Target

M SC /SG SN

R A N A P R A N A P


R A N A P R A N A P


A cknow ledge

R A N A P R A N A P 11 . R elocation C om m and

R A N A P 12 . R elocation C om m and

R A N A P

R A N A P R A N A P

15 . R elocation

D etect

R R C 13 . D C C H : P hysical C hannel R econfiguration N ote 1

R R C

5 . A LC A P Iu D ata

T ransport B earer Setup

N ode B

Source

N ode B

Target

N B A P N B A P 6 . R adio L ink Setup R equest

N B A P N B A P 7 . R adio L ink Setup R esponse

8 . A LC A P Iub D ata T ransport B earer Setup

R A N A P R A N A P

19 . R elocation

C om plete

R R C R R C 18 . D C C H : P hysical C hannel R econfiguration C om plete N ote 1

R A N A P R A N A P 16 . R elocation D etect

R A N A P R A N A P 20 . R elocation C om plete

R A N A P 21 . Iu R elease C om m and

R A N A P

N B A P N B A P 17 . R adio L ink Failure Ind ication

R A N A P 22 . Iu R elease C om m and

R A N A P

23 . A LC A P Iu D ata T ransport B earer

R elease

R A N A P 24 . Iu R elease C om plete

R A N A P

R A N A P 25 . Iu R elease C om plete

R A N A P

SG SN /M SC

N B A P N B A P 14 . R adio L ink R estore Ind ication

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.



5 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

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.

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.



5.1 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:

jBestj

N

1i

jijjfrequencyfrequencyj LogM10)W(1MLog10WLogM10QjA

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).

M frequency j: Refers to the physical measurement value (ratio for Ec/No; mW for RSCP) of

the (Virtual) active set of carrier j.

M i 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 or both of them measurement quantity, which is based on the

parameter NonIntraMeasQuan. Only event-based method of reporting measurement

result is supported, and parameter InterHoMth is invalid.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.

/2HQQ 2aBestNotBest

Where,

QNotBest: Refers to the measurement result of current non-best carrier frequency.

QBest : Refers to the measurement result of current best carrier frequency.

H2a : Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2A.

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.

/2HTQ 2b2busedNonusedNon /2HTQ 2b2bUsedUsed

Where,

QNon used: Refers to the measurement result of current non-working carrier frequency.

TNon used 2b: Refers to the absolute threshold

(ThreshNoUsedFreq[MAX_INTER_MEAS_EVENT]) of good quality of non-working

carrier frequency in Event 2B decision.

H2b : Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2B.

QUsed: Refers to the measurement result of current working carrier frequency.

TUsed 2b: Refers to the absolute threshold

(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.

/2HTQ 2c2cusedNonusedNon

Where,


TNon used 2c: Refers to the absolute threshold


carrier frequency in Event 2C decision.



H2c: Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2C.

Event 2D: The quality of working carrier frequency is lower than a threshold.

/2HTQ 2d2dUsedUsed

Where,


TUsed 2d: Refers to the absolute threshold


frequency in Event 2D decision.

H2d: Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2D.

Event 2E: The quality of non-working carrier frequency is lower than a threshold.

/2HTQ 2e2eusedNonusedNon

Where,


TNon used 2e: Refers to the absolute threshold


carrier frequency in Event 2E decision.

H2e: Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] ) of Event 2E.

Event 2F: The quality of working carrier frequency is higher than a threshold.

/2HTQ 2f2fUsedUsed

Where,


TUsed 2f: Refers to the absolute threshold


frequency in Event 2F decision.

H2f: Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2F.



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.

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

frequency adjacent cell that has no ShareCover(Overlap or Covers) relation (judged

through ShareCover) with current serving cell and UE supports the radio frequency band

of these neighboring cells.

(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:

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.

5.1.2.2 Measurement Modification

If the inter-frequency measurement is enabled, the inter -frequency measurement

modification is triggered in the following cases:

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.

5.1.2.3 Measurement Deletion

When inter-frequency measurement setup conditions are no longer met, the inter-

frequency measurement will be deleted (released).

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 t ransmit power does not

exceed inter-frequency measurement initiation threshold (100%) or recovers below

normal value (90%), and the downlink transmit power does not exceed inter -

frequency measurement initiation threshold (90%) or recovers below normal value

(80%).

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).



5.1.2.4 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 inter-

frequency load balancing based on the cells’s load . (For details, see ZTE UMTS

Load Balance Feature Guide).

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 Guide), 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 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 HS-

DSCH/DCH after, then access by HS-DSCH/E-DCH or HS-DSCH/DCH (for

details, see ZTE UMTS DRBC Algorithm Feature Guide); if HS-DSCH/E-DCH

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 cover relation(GsmShareCover value is “2

GSM neighboring cell covers the serving cell” ) with current serving cell, 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

serving celll doesn’t have any inter-RAT neighboring cell with cover

relation(GsmShareCover value is not “2 GSM neighboring cell covers the serving

cell”), 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 “Inter-

Frequency Measurement Control Method Measurement Deletion”.

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.


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:

Measurement quantity.

NonIntraMeasQuan ( PCPICH RSCP or Ec/N0 or both of them)

Remark:

(1) When NonIntraMeasQuan is configured as “Ec/No” or “RSCP ”, only issue

corresponding measurement quality.

(2) When NonIntraMeasQuan is configured as “Ec/No and RSCP”, two

categories of 2D/2F measurement event about CPICH Ec/No and CPICH

RSCP are configured and one of 2D measurement events can trigger

compressed mode. After compressed mode is triggered, inter frequency

event of corresponding measurement quantity will be issued according to

that of 2D event. For example, if the measurement quanitty of triggering 2D

event is Cpich Ec/No, only inter frequency event of Cpich Ec/No will be

issued.

Measurement report mode

InterHoMth (Event report or periodical report, only event

report method is supported and the following parameters related to periodical

report are invalid: PrdmeasEcNo(Inter), PrdMeasRSCP(Inter),

PrdRptAmount(Inter) and PrdRptInterval(Inter))

Service bearer type (TrfCategory (CInter))









Not Related to Service Type (Used for detected set measurement)

Remark:



(1) When concurrent service exists and includes AMR serivce, index to RT

RAB Including Voice configuration.

(2) When concurrent service exists and includes non-AMR service, index to RT

RAB Excluding Voice configuration.

To facilitate parameter modification and optimization, the inter-frequency

parameters are index-organized, with the index quotations listed as follows:

Figure 5-1 Inter-frequency handover index quotations

Utran Cell (utranCell)UE Inter-frequence Measurement

Configuration (Inter)

UE Inter-frequence Measurement

Relative to Traffic Category (CInter)

TrfCatInterMIdx

NonIntraMeasQuan

TrfCategory:










InterMeasCfgNo

Before obtaining inter-frequency handover parameters, first find the “Service Type-

Related Inter-frequency Measurement Parameter Index (TrfCatIntraMIdx)”, “UTRAN

Inter-frequency Radio Quality Measurement Quantity (NonIntraMeasQuan)”,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

TrfCat InterMIdx, "Traffic Category (TrfCategory)", “Measurement Purpose

(EvtMeasEcNo, 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 inter-

frequency measurement control message and OMCR configuration is described as

follows:


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

(CIdRpt Ind)



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)

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.

Switch of inter-frequency handover based on measurement for different services

There are several switches for different services to control whether inter -frequency

based on measurment could be performed. When the switch is open, it is allowed to

perform inter-frequency handover for the corresponding service. Otherwise RNC forbids

performing inter-frequency handover for the serivce by not activating inter-frequency

measurement. The switches for different services are as followed:

Service Switch

AMR AmrIfHoSwch

R99 RT R99RtIfHoSwch

R99 NRT R99NrtIfHoSwch

HSDPA HsdpaIfHoSwch

HSUPA HsupaIfHoSwch

Inter-frequency and inter-RAT measurement choice

When a cell has both inter-frequency and inter-RAT cells as its neighbors,

IfOrRatHoSwch is used to indicate the priority of inter-frquency and inter-RAT

handover.

If IfOrRatHoSwch indicates “Turn off Inter-frequency and Inter-RAT Handover”,

neither inter-frequency measurement nor inter-RAT measurement will be

issued by RNC.

If IfOrRatHoSwch indicates “Only Inter Frequency” and inter-frequency

neighboring cells exist, only measurement on inter-frequency is issued by

RNC

If IfOrRatHoSwch indicates “Only Inter RAT” and inter-RAT neighboring cells

exist, only measurement on inter-RAT is issued by RNC



If IfOrRatHoSwch indicates “Inter Frequency Is Prior to Inter RAT”, and only inter-

frequency or inter-RAT neighboring cells exist, measurement on inter-

frequency or inter-RAT is issued by RNC, else if both inter-frequency and

inter-RAT neighboring cells exist, RNC will configure inter-frequency

measurement in priority and start a timer T4StpIfMeaActRat, when 2E event is

reported or T4StpIfMeaActRat is expired, RNC will reconfigure inter-frequency

measurement to inter-RAT measurement.


In neighboring cells configuration, adjacent cell list used for reselection in non-



(StateMode). When UE in macro diversity state, the neighboring cell list is the union of

neighboring cell list of each cell active set, then the number of inter -frequency

neighboring cells may exceed 32 which is the maximum number regulated by protocol. If

the number of inter-frequency neighboring cells exceeds 32, it needs to delete some

cells to ensure that there are only 32 inter-frequency neighboring cells. With minimal

impact on UE in active set, these dropped cells are those with poorer signal quality or

remoter geographical location. So each inter-frequency neighboring cell is configured

with a priority.

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). 0 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 5-2 Cell priority configuration

Source Cell

Priority 0

Priority 1

Priority 2

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 which can buffer at most 8 truncated inter-

frequency cells.

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

frequency 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. Period report method is not supported.

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

handover, and moving speed based handover. For details on enabling/disabling of

compressed mode and inter-frequency measurement setup/release, see “Inter-

Frequency 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 handli ng 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.

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 cell’s load and ensure system stability.



For details on load handover, see ZTE UMTS Overload Control Feature Guide.

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

moving 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 slow-

speed 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:

(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 5-3).



Figure 5-3 Example of slow-moving UE judging conditions

TimeTslowjudge

N = 0

Time of serving cell change is 0 during Tslowjudge

TimeTslowjudge

NSlow

Time difference between the time of last serving

cell change and current time is larger than Tslow

TSlow

（one red line means one time of serving cell change

or

(a) (b)

Figure 5-4 Example of fast-moving UE judging condition

TimeTfast

NFast

Time of serving cell change is larger than Nfast

before Tfast timeout

（one red line means one time of serving cell change

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

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.

6 Inter-RNC Mobility

6.1 SRNS Relocation

SRNS relocation can be categorized into relocation UE not involved (soft handover

triggered) and relocation UE involved (hard handover triggered) according that whether

UE is involved.

Relocation UE not involved

It is soft handover relocation namely, and UE can use radio resource in DRNC and

connect with CN through SRNC. The trigger condition is :

There is an Iur interface between RNCs

The switch of relocation UE not involved is open. It is differentiated by CS

service and PS service, RncFeatSwitch bit10 is for CS service and

RncFeatSwitch bit11 for PS service.

When all radio links are handed over to DRNC, timer is activated

(CsReDelayTimer and PsReDelayTImer are configured according to CS

service and PS service respectively, the timer of CS service is considered for

multi-RAB service) and relocation is performed when the corresponding timer

is overtime.

Relocation UE involved

Namely it is hard handover relocation. The trigger condition is :

The switch of relocation UE involved RncFeatSwitch bit0 is open



6.1.1 Relocation Triggered by Soft Handover

Figure 6-1 Relocation triggered by soft handover

UE

Target

RNCSGSN

Source

RNC

1.Relocation Required

2.Relocation Request

3.Relocation Request Ack

4.Relocation Command

5.Relocation Commit

6.Relocation Detect

7.UTRAN Mobility

Information

8.UTRAN Mobility

Information Confirm

9.Relocation Complete

10.Iu Release Command

11.Iu Release Complete

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. When SRNC sends the Relocation

Required message, it shall start the timer Trelocprep. Upon reception of the

Relocation Command message, SRNC shall stop the timer and terminate the

Relocation Preparation procedure. If there is no response from the CN to the

Relocation Required message before expiry of timer Trelocprep, SRNC shall cancel

the Relocation Preparation procedure by initiating the Relocation Cancel procedure

with the Cause “Trelocprep expiry”.

2 The CN sends a “Relocation Request” message to the DRNC, carrying “RAB

SETUP” message.

3 After the RAB of DRNC is established successfully, the DRNC sends “Relocation

Request Ack” message to the CN.

4 The CN sends “Relocation Command” message to the SRNC requiring the SRNC

to start relocation. Upon reception of the Relocation Command message, SRNC

shall stop the timer Trelocprep, start the timer Trelocoverall and terminate the

Relocation Preparation procedure. If the Iu Release procedure is not initiated



towards SRNC from CN before expirty of Trelocoverall, SRNC shall initiate the Iu

Release Request procedure towards CN with cause “Trelocoverall expiry”.

5 The SRNC sends “Relocation Commit” message to the DRNC through the lur

interface.

6 The DRNC sends “Relocation Detect” message to the CN and is converted into a

new SRNC through role exchange.

7 The new SRNC sends “UTRAN Mobility Information” message to UE to relocate U-

RNTI.

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

message to the new SRNC.

9 The new SRNC sends “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.

12 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.1.2 Relocation Triggered by Hard Handover

Figure 6-2 Relocation triggered by hard handover

UE

Target

RNCSGSN

Source

RNC

1.Relocation Required

2.Relocation Request

3.Relocation Request Ack

4.Relocation Command

7.Relocation Detect

8.Physical Channel

Reconfiguration Complete

9.Relocation Complete

10.Iu Release Command

11.Iu Release Complete

5.Physical Channel

ReconfigurationUE

6.UE detected by target RNC


The SRNC initiates a “Relocation Required” message to the CN.

1 Upon receiving the message, the CN sends “Relocation Request” message to the

DRNC. When SRNC sends the Relocation Required message, it shall start the

timer Trelocprep. Upon reception of the Relocation Command message, SRNC

shall stop the timer and terminate the Relocation Preparation procedure. If there is

no response from the CN to the Relocation Required message before expiry of

timer Trelocprep, SRNC shall cancel the Relocation Preparation procedure by

initiating the Relocation Cancel procedure with the Cause “Trelocprep expiry ”.

2 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.

3 The CN sends “Relocation Command” message to the SRNC requiring the SRNC

to start relocation.

4 The SRNC sends “Physical Channel Reconfiguration” message to the UE, requiring

UE to perform hard handover. Upon reception of the Relocation Command

message, SRNC shall stop the timer Trelocprep, start the timer Trelocoverall and

terminate the Relocation Preparation procedure. If the Iu Release procedure is not

initiated towards SRNC from CN before expirty of Trelocoverall, SRNC shall initiate

the Iu Release Request procedure towards CN with cause “Trelocoverall expiry ”.

5 The DRNC initiates “UE Detect” message to imply that the DRNC already detects

UE.



6 Upon detecting the UE, the DRNC sends “Relocation Detect” message to CN, and

then DRNC is converted into a new SRNC through role exchange.

7 The UE returns “Physical Channel Reconfiguration Complete ” message to inform

the new SRNC of successful hard handover.

8 Upon receiving the message, the new SRNC sends “Relocation Complete”

message to CN.

9 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.

11 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.

6.2 DSCR

Like relocation, DSCR is categorized into hard handover DSCR and soft handover

DSCR. The trigger condition of DSCR is:

Soft handover DSCR

It means that all radio links are handed over to DRNC and relocation is not

performed. DSCR will be triggered when all the following conditions are met:

The switch of soft handover DSCR RncFeatSwitch bit7 is open.

All radio links are in DRNC side.

CS service is not included.

Hard handover DSCR

DSCR will be trigger if all the following conditions are met when relocation is output

in hard handover.

The switch of hard handover DSCR RncFeatSwitch bit4 is open.

Hard handover is needed to perform according to decision.



CS service is not included.

6.3 Coupling between relocation and DSCR

DSCR is performed in priority when conditions of relocation and DSCR are met

simultaneously.

If there is only PS service, DSCR is performed when conditions of relocation

and DSCR are met simultaneously.

If there is only CS service, relocation is performed.

For multi-RAB service, if DSCR condition of PS service is met, then DSCR is

performed after CS service is released.

7 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

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.



Best

N

1i

iUTRANUTRAN LogM10W)(1MLog10WLogM10QA

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).

M i 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 GERA N, 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.

/2HTQ 3aUsedUsed and /2HTCIOM 3aRATOtherRATOtherRATOther

Where:

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).

TOther RAT is the absolute threshold of other systems

(ThreshSys[MAX_RAT_MEAS_EVENT]).l

3C: The quality of other radio systems is higher than a threshold. It can be used for

Inter-RAT handover decision.

/2HTCIOM 3cRATOtherRATOtherRATOther

Where:

MOther RAT is the quality measurement result of other systems.

CIOOther RAT is the quality offset of other system cells (CellIndivOffset(gsmRelation).

TOther RAT is the absolute threshold of other systems

(ThreshSys[MAX_RAT_MEAS_EVENT]).

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

RAT 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-RAT measurement immediately. (Note: For simplification, the startup policy of

service-based Inter-RAT measurement is not checked in the following scenarios:

i 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 inter-frequency neighboring cell is not configured) or for inter -frequency blind

handover are not met. In this case, i f 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 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.

Parameter ServBasedHoInd indicates whether RNC supports handover based on

service and ServHoSwch is used to control whether a cell open such function. For

UE in macro diversity state, ServHoSwch in the best cell is taken. If the best cell is

changed, parameter configuration needs update.

Service handover strategy controlled by RNC

When IE “service handover” is not include in RAB Assignment Request, RNC can

perform service handover strategy by parameter ServHoInd:

If the parameter sets as “Ignore service handover IE”，RNC will ignore

"service handover" IE in requested RAB, and perform strategy according to

the value of

AmrServHoStra/CS64ServHoStra/PsRtServHoStra/PsNrtServHoStra; If the

parameter sets as “Apply service handover IE” and "service handover" is

not included in requested RAB, RNC will also perform corresponding service

handover strategy according to the value of



AmrServHoStra/CS64ServHoStra/PsRtServHoStra/PsNrtServHoStra,

otherwise RNC will perform strategy based on the value of "service handover"

IE in requested RAB.

Four service types （AMR/CS64/PS RT/PS NRT） are classified in this

strategy and RNC performs service handover according to the parameter

AmrServHoStra/CS64ServHoStra/PsRtServHoStra/PsNrtServHoStra.

For multi-RAB service, ServHoComStra is used to control the combination of

service handover values. For example, if service handover value of AMR is

Handover to GSM should be performed, and the value of PS RT service is

Handover to GSM should not be performed, the priority of Handover to GSM should

not be performed can be set to at a higher level than Handover to GSM should be

perform, then when AMR and PS RT service are setup simultaneously, WCDMA is

used to carry the services, only after PS RT service is released can CS voice

service is allowed to hand over to GSM based on service handover value.

7.1.2.2 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 Inter-

RAT 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.

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 int ra-frequency neighboring cells of the

cells in the current active set are neighboring cells with GsmShareCover(Overlap or

Covers)



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.

7.1.2.4 Processing of Inter-RAT Events

Processing of 3A/3C events

1) In a cell, inter-RAT handover can only be triggered by 3A or 3C event, which is

controlled by Inter-RAT handover tactic RatHoTactic.

2) Penalty timer set by HoToGsmPenTimer is introduced to avoid inter -RAT

handover failure repeatedly because of 2G target cell. It means that only the

timer is overtime can inter-RAT handover be attempted again when inter-RAT

handover fails.

3) When only PS service exists, if UE supports inter-RAT PS service handover

and parameters PsInterSysHoSupp and BscFeatSwitch in OMCR indicates

that RNC andadjacent BSC supports PS service handover respectively, then

adopt HANDOVER FROM COMMAND process (See “CS Service Handover

from 3G System to 2G System” process). Otherwise, adopt cell reselection

process of PS service handover (See “PS Service Reselection in 3G to 2G

Handover” process). In cell reselection of PS service handover process, inter-

RAT cell reselection time can be decreased by NACC, which means that

system information of target GERAN cell is carried in CELL CHANGE

ORDER FROM UTRAN message sent from RNC to UE, assisting UE in inter-

RAT cell reselection process. NaccSuppInd parameter indicates that whether

RNC supports NACC function or not. GeranCellInd indicates whether a GSM

cell is a GERAN cell.

4) When CS service and PS service exist simultaneity, if UE supports inter-RAT

DTM handover and parameters DtmSuppInd and BscFeatSwitch in OMCR

indicates that RNC and adjacent BSC supports DTM handover, then adopt

HANDOVER FROM COMMAND process to handover concurrent service to 2G

system. Otherwise suspend PS service firstly, then handover CS service to 2G

system and handover PS service to 2G system in sequence.

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.


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 p arameters 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 or both of them)

Remark:

(1) When NonIntraMeasQuan is configured as “Ec/No” or “RSCP ”, only issue

corresponding measurement quality.

(2) When NonIntraMeasQuan is configured as “Ec/No and RSCP”, two

categories of 2D/2F measurement event about CPICH Ec/No and CPICH

RSCP are configured and one of 2D measurement events can trigger

compressed mode. After compressed mode is triggered, inter-RAT event of

corresponding measurement quantity will be issued according to that of 2D

event. For example, if the measurement quantity of triggering 2D event is

Cpich Ec/No, only inter-RAT event of Cpich Ec/No will be issued.

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:

Figure 7-1 Indexing relation for Inter-RAT handover

Utran Cell (utranCell)UE Inter-Rat Measurement

Configuration Information(Rat)

UE Inter-Rat Measurement Relative to

Traffic Category (CRat)

TrfCatRatMIdx

NonIntraMeasQuan

TrfCategory:










InterRatCfgNo

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:


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 personnel’s reference.

Switch of inter-RAT handover based on measurement for different services

There are several switches for different services to control whether inter-RAT based on

measurment could be performed. When the switch is open, it is allowed to perform inter-

RAT handover for the corresponding service. Otherwise RNC forbids performing inter-

RAT handover for the serivce by not activating inter-RAT measurement. The switches

for different services are as followed:

Service Switch

AMR AmrRatHoSwch

R99 RT R99RtRatHoSwch

R99 NRT R99NrtRatHoSwch

HSDPA HsdpaIfHoSwch

HSUPA HsupaRatHoSwch


In neighboring cells configuration, neighboring cell list used for reselection in non-



(GsmStateMode). When UE in macro diversity state, the neighboring cell list is the union

of neighboring cell list of each cell active set, then the number of inter -RAT neighboring

cells may exceed 32 which is the maximum number regulated by protocol. If the number

of inter-RAT neighboring cells exceeds 32, it needs to delete some cells to ensure that

there are only 32 inter-RAT neighboring cells. With minimal impact on UE in active set,

these dropped cells are those with poorer signal quality or remoter geographical location.

So each inter-RAT neighboring cell is configured with a priority.



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. 0 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 7-2 Priority settings of cells

Source Cell

Priority 0

Priority 1

Priority 2

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 priori ty

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

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 which can

buffer at most 8 truncated inter-RAT cells.

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,

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 Guide.

7.7 Inter-RAT Handover based on GSM Load

As UMTS can acquire the load condition in GSM after IUR-G is introduced, inter-RAT

handover based on GSM load is taken into consideration in order to avoid admission

failure in GSM because of overload in GSM system. This function is controlled by

parameter LdBsIntSysHOInd.

7.7.1 Acquirement and Update of GSM Load Condition

3GPP defines three catogories of GSM load in IUR-G: Load Value, RT Load, and NRT

load. Load Value is about total load condition in cell, while RT Load for RT service load

and NRT Load for NRT service load.

GSM overload cell save and update strategy

Define RT overload cell list and GSM overload cell list. RNC saves and updates the

two lists in time, and sets up an overload valid timer CellLdInfoVldTim. When duration of

a cell’s overload information before updating exceeds CellLdInfoVldTim, the cell will be

deleted from corresponding overload cell list.

When reported downlink RT load in GSM cell is not less than GsmDlRTLdThrd or

reported uplink RT load in GSM cell is not less than GsmUlRtLdThrd, it means that the

load in GSM cell is heavy and RT service can not be accessed, then the cell will be kept

in RT overload cell list. If reported uplink/downlink RT load is smaller than the according

threshold in a cell and the cell exists in RT overload cell list, then the cell will be deleted

from RT overload cell list.

When reported downlink load in GSM cell is not less than GsmDlLdThrd or reported

uplink load in GSM cell is not less than GsmUlLdThrd, it means that any service can not

be accessed, and then the cell will be kept in GSM overload cell list. If reported

uplink/downlink load is smaller than the according threshold in a cell and the cell exists

in GSM overload cell list, then the cell will be deleted from GSM overload cell list.

For RT service, i f RT load is reported, then it is used to decide the load condition of

GSM cell, otherwise Load Value is used to decide. For NRT service, Load Value is used

to decide the load condition of GSM cell.

7.7.2 Inter-RAT Handover based on GSM Load Process

Under following scenarios, firstly select target cell list which will be handovered to. If a

target cell is included in overload cell list, it is considered that the GSM cell is overload

and handover to the cell is not triggered, then try another cell in the candidate cells list. If



all cells in candidate cells list don’t satisfy handover condition, the corresponding

handover is not performed.

Inter-RAT handover based on quality of downlink coverage, uplink BLER, and

uplink/downlink transmit power.

Inter-RAT handover based on load control

Inter_RAT handover based on load balance

Remark: For RT service, i f GSM reports RT info rmation, overload-cell list stands for RT

overload-cell list. Otherwise, i f GSM doesn’t report RT information, overload cell list

stands for GSM overload-cell list. For NRT service, overload-cell list means GSM

overload-cell list.

7.8 Coupling for Different Handover Causes

As described above, the causes of Inter-RAT handover include the following:

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.



7.9 Inter-RAT Handover Process

7.9.1 CS Service Handover from 3G System to 2G System

Figure 7-3 3G to 2G CS service handover

RNCNODE BUE

HANDOVER FROM UTRAN COMMAND

HANDOVER COMPLETE

CN

RELOCATION REQUIRED

RELOCATION COMMAND

BSC

HANDOVER REQUEST

HANDOVER DETECT

HANDOVER COMPLETE

IU RELEASE COMMAND

IU RELEASE COMPLETE

HANDOVER REQUEST ACK

RADIO LINK DELETION REQUEST

RADIO LINK DELETION RESPONSE

7.9.2 PS Service Reselection in 3G to 2G Handover

If UE doesn’t support inter-RAT PS service handover or adjacent BSC doesn’t support

PS service handover, 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.



Figure 7-4 PS service reselection initiated by an UE in the case of 3G to 2G handover

UE CN

1. Cell Reselection

triggered

Serving

RNC

RANAP RANAP2. Iu Release Command

RANAP RANAP2. Iu Release Complete

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 7-5 PS service reselection initiated by the RNC in the case of 3G to 2G handover

1. Cell Change Order from UTRAN

UE

RRC RRC

2. Reselection to the target GPRS cell; radio link establishment in GSM/BSS

GMM GMM 3. Routing Area Update Request

4. SRNS Context

Request RANAP RANAP

RANAP 5. SRNS Context

Response RANAP

6. SRNS Data Forward

Command RANAP RANAP

7. Forwarding of PDUs

RANAP RANAP 8. Iu Release Command

10. Routing Area Update Accept

Node B BTS

BSC CN

(SGSN)

RNC

Serving

GMM

GMM GMM

GMM 11. Routing Area Update Complete

RANAP 9. Iu Release Complete

RANAP


1 Upon detection of a trigger, SRNC initiates the handover to GSM/BSS by sending

the RRC message Cell Change Order from UTRAN to the UE, and starts the timer

TWaitContextReq. Upon reception of the SRNS Context Request message, SRNC

shall stop the timer. If TWaitContextReq expires, SRNC starts the timer

TWaitDataFwd.

2 The UE reselects to the target GPRS cell and establishes the radio connection to

the GSM/BSS.

3 The UE initiates the GPRS Routing Area Update procedure by sending the GMM

message Routing Area Update Request to the SGSN.

4 The SGSN sends the RANAP message SRNS Context Request to the SRNC listing

the PS RABs for which context transfer shall be performed.



5 SRNC responds to the SGNS with the RANAP message SRNS Context Response

containing the context information of all referenced PS RABs whose transfer is

successful and starts the timer TWaitDataFwd. Upon reception of the SRNS Data

Forward Command message, SRNC shall stop the timer. If TWaitDataFwd expires,

SRNC starts the timer TWaitRelCmd.

6 The SGSN asks the SRNC to forward its buffered data back to the SGSN by

sending the RANAP message SRNS Data Forward Command, and starts the timer

TWaitRelCmd. Upon reception of the IU RELEASE COMMAND message, SRNC

shall stop the timer. If TWaitDataFwd expires, SRNC releases IU conncetion.

7 For each PS RAB indicated by the SRNS Data Forward Command, the SRNC

starts duplicating and tunnelling the buffered data back to the SGSN.

8 The SGSN sends the RANAP message Iu Release Command to initiate the release

of the Iu connection with UTRAN.

9 At the expiration of the RNC data forwarding timer (i.e. TDATAfwd), the SRNC

sends the RANP message Iu Release Complete message to the SGSN.

10 The SGSN validates the UE’s presence in the new RA by sending the GMM

message Routing Area Update Accept to the UE. The message may contain a new

P-TMSI that the network assigns to the UE.

11 The UE acknowledges the assignment of a new P -TMSI by sending the GMM

message Routing Area Update Complete to the UE.

8 IMSI-based handover

Parameter BasedImsiHoInd indicates whether RNC supports 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.

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

0 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.

2 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.



3 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 8-1 Schematic Diagram of Querying Whether a SRNC Cell Is Authorized According to IMSI

CommonID:MCC

MNC

ExtInfo

rncPnSnac:MCC

MNC

ExtInfo

SNAC

Granted:MCC

MNC

SNAC

rncLcSnac：MCC

MNC

SNAC

LAC

Granted：MCC

MNC

LAC

utranCell、externalUtranCell、gsmRelation：MCC

MNC

LAC

Neighbor cell is

granted or not

8.2 Querying Whether a DRNC Cell Is Authorized According to IMSI

0 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:

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.

2 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.

3 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.

Notes:In step 3, how many SNAC is configured for DRNC neighbor cells is controlled by

SNACNum (externalUtranCell, gsmRelation).

Figure 8-2 Schematic Diagram of Querying Whether a DRNC Cell Is Authorized

According to IMSI

CommonID:MCC

MNC

ExtInfo

rncPnSnac:MCC

MNC

ExtInfo

SNAC

Granted:MCC

MNC

SNAC

rncLcSnac：MCC

MNC

SNAC

LAC

Granted：MCC

MNC

LAC

utranCell：MCC

MNC

LAC

Neighbor cell is

granted or not

9 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 Guide 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 HS-

DSCH falls back to DCH. The channel transfer is performed along with handover.

Different channel t ransfer 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 int ra-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 intra-

frequency 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.

2 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

Guide for details), a decision of handover from DCH to HS -DSCH is made.



3 HS->DSCH->HS-DSCH

If the HS-DSCH is used before the handover and 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 HS-DSCH service

cell change is made.

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.

2 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.

3 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.

4 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.

9.4 Inter-RAT Handover

Two strategies are available for handovers between HSDPA systems: UTRAN-

>GSM/GERAN strategy and GSM/GERAN -> UTRAN strategy.

1 UTRAN->GSM/GERAN

The HSDPA service is included and then the same handover flow as that for

between R99 systems is performed.

2 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.

10 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 Guide for details).

10.1 Overview

HSUPA is developed on the basis of HSDPA. An HSUPA net work 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.

The maximum number of cells allowed in the E-DCH active set in the process of HSUPA

soft handover is 3.

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 diffe rent handover

types.


The intra-frequency handover of HSUPA 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 HS-



DSCH/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.

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 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 HSPA, the current channel type is DCH/DCH,

and also the best cell in the active set supports HSDPA. If the downlink or uplink

traffic increases to trigger the 4A event (refer to ZTE UMTS DRBC Algorithm

Feature Guide for details), a decision of handover from DCH/DCH to HS-DSCH/E-

DCH is made.

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

frequency 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.

4 HS-DSCH/E-DCH->HS-DSCH/DCH


service cell of HS-DSCH/E-DCH, and also the cells in the active set supports HS-

DSCH/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 HS-

DSCH/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.

5 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 HS-

DSCH/E-DCH is made.


The conditions for triggering the inter-frequency handover of HSPA 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

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.

3 HS-DSCH/E-DCH->HS-DSCH/E-DCH





together with HS-DSCH/E-DCH service cell change is made.

4 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 HS-

DSCH/DCH is made.

5 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.

6 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, and then the same handover flow as that for

between R99 systems is performed.

2 GSM/GERAN -> UTRAN

Similar to the handover between R99 systems, if the target cell support HS-

DSCH/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:

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.

2 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, i f 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.

3 The principle of the type change in the bearer of the MBMS service in the active set

under the macro diversity.

Table 11-1 Table of Principle

Bearer Change Type Cell Type Principles of Change

p-t-p->p-t-m Best cell Delete the p-t-p

Non best cell No change

p-t-m ->p-t-p 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.


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.



2 If the target carrier does not come with a cell with the same coverage (included), the

neighbor cell of the current cell in the UE’s 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

TrigTime[MAX_INTRA_MEAS_EVENT]

Time to Trigger

PrdRptAmount Amount of reporting

PrdRptInterval Reporting Interval in Period Report Criteria

CellIndivOffset(ut ranCell) Cell individual offset

CellIndivOffset(ut ranRelation) Cell individual offset

RptDeactThr Reporting Deactivation Threshold for 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 Intra-frequency Measurement Configuration Index

MeaEvt Id[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_EVENT]

Threshold of the Quality of the Used Frequency for Event 1E/1F

StateMode UE State Indicator Used for UTRAN Neighboring Cell Configuration

ReadSFNInd Read SFN Indicator

SoftHoMth Soft Handover Method

IntraMeasQuan UTRAN Measurement Quantity for Intra-frequency 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

EvtRpt Interval Reporting Interval for Event 1A/1B/1C/1J

EvtRptAmount Amount of Reporting for Event 1A/1B/1C/1J

FbdCellInd Forbidden Cell Indicator for Event 1A/1B

PcpichPwrPre Primary CPICH Power Configuration Tag

RlRefTimeAjtSwit Switch for RL Reference Time Adjust During Diversity Mode

TimeDelay Transport Time Delay(NodeB)

ATimeDelay Transport Time Delay(externalUtranCell)

RncFeatSwitch Neighbouring RNC Feather Switch

NrtMaxUlRateDch Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell

NrtMaxDlRateDch Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell



RtMaxUlRateDch Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell

RtMaxDlRateDch Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell

RtMaxRateEdch Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell

NrtMaxRateEdch Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell

NrtMaxUlRateDchD Maximum Bit Rate on UL DCH for NRT PS RAB in DRNC Cell

NrtMaxDlRateDchD Maximum Bit Rate on DL DCH for NRT PS RAB in DRNC Cell

RtMaxUlRateDchD Maximum Bit Rate on UL DCH for RT PS RAB in DRNC Cell

RtMaxDlRateDchD Maximum Bit Rate on DL DCH for RT PS RAB in DRNC Cell

NrtMaxRateEdchD Maximum Bit Rate on E-DCH for NRT PS RAB in DRNC Cell

RtMaxRateEdchD Maximum Bit Rate on E-DCH for RT PS RAB in DRNC Cell

Cs64Switch Switch of CS 64kbps Establishment

AdjCs64Switch Switch of CS 64kbps Establishment for External UTRAN Cell

Pcpichpwr Primary CPICH Power

NbrCellMonSupInd Neighboruing Cell Monitoring Support Indicator

12.1.2 Parameter Configuration

12.1.2.1 Measurement Priority of Neighboring Cell

OMC Path

Interface Path: View->Configuration Management ->RNC NE->RNC Radio Resource

Management->Utran Cell->Utran Cell XXX->Neighbouring Cell ->Neighbouring Cell XXX-

> Measurement Priority of Neighboring Cell

Parameter Configuration

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 Detected Set Handover Switch

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

OMC Path


Management-> Modify Advanced Parameter->UE Intra-frquence Measurement

Configuration->Reporting Range Constant Event 1A/1B(dB)


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 Weight for Event 1A/1B

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.

12.1.2.5 Hysteresis(Intra)

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)

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).

12.1.2.7 Time to Trigger(Intra)

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.

12.1.2.8 Amount of Reporting in Period Report Criteria

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

measurement results.

12.1.2.9 Reporting Interval in Period Report Criteria

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)

OMC Path



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

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)

OMC Path



>Modify Advanced 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

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

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 Intra-frequency Measurement Configuration Index Related to Traffic

Category(CIntra)

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


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 Intra-frequency Measurement Configuration Index Related to Traffic

Category(UtranCell)

OMC Path



>Intra-frequency Measurement Configuration Index Related to Traffic Catego ry


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

OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource


Configuration-> Int ra-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 Intra-frequency Measurement Event ID

OMC Path



Configuration-> Int ra-frequency event identity


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

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.

12.1.2.19 UE Event Report Configuration Index for CPICH Ec/No

OMC Path



Relative to Traffic Category Configuration Information->UE Event Report Configuration

Index for CPICH Ec/No


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.

Table 12-1 Default Value of the UE Int ra-frequency Measurement Configuration Parameters Related to Traffic Category

Fie

ld N

am

e

Defa

ult

Valu

e 1

Defa

ult

Valu

e 2

Defa

ult

Valu

e 3

Defa

ult

Valu

e 4

Defa

ult

Valu

e 5

Defa

ult

Valu

e 6

Defa

ult

Valu

e 7

Defa

ult

Valu

e 8

Defa

ult

Valu

e 9

TrfCatIntraMIdx 1 1 1 1 1 1 1 1 1

TrfCategory 0 1 2 3 4 5 6 7 0xff

PrdMeasEcNo 0 0 0 0 0 0 0 0 0

EvtMeasEcNo 2 2 2 2 2 2 2 2 2

PrdMeasRSCP 5 5 5 5 5 5 5 5 5

EvtMeasRSCP 7 7 7 7 7 7 7 7 7

EVTMEASDCTECNO 10 10 10 10 10 10 10 10 10

EVTMEASDCTRSCP 11 11 11 11 11 11 11 11 11



12.1.2.20 Period Report Configuration Index for CPICH Ec/No

OMC Path



Relative to Traffic Category Configuration Information->Period Report Configuration

Index for CPICH Ec/No



periodic reporting by the UE when the measurement quantity is CPICH Ec/No.

12.1.2.21 Period Report Configuration Index for CPICH RSCP

OMC Path



Relative to Traffic Category Configuration Information->Period Report Configuration

Index for CPICH RSCP



periodic reporting by the UE when the measurement quantity is CPICH RSCP.

12.1.2.22 UE Event Report Configuration Index for CPICH RSCP

OMC Path



Relative to Traffic Category Configuration Information-> UE Event Report Configuration

Index for CPICH RSCP



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

OMC Path



Relative to Traffic Category Configuration Information ->Detected Set Measurement

Configuration Index for CPICH Ec/No




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

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 Function of Configuration Parameters

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 Measurement Report Transfer Mode

OMC Path



Configuration-> Measurement Report Transfer Mode


This parameter indicates the transfer mode of the measurement quantity: acknowledge

mode or unacknowledged mode.



12.1.2.27 Measurement quantity

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 CPICH Ec/No Reporting Indicator

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 CPICH RSCP Reporting Indicator

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

OMC Path



Configuration-> Pathloss reporting indicator



on the measurement quantity pathloss.

12.1.2.31 Report 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

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

OMC Path

Interface Path:View->Configuration Management ->RNC NE->RNC Radio Resource


Configuration->Threshold of the Quality of the Used Frequency for Event 1E/1F


This parameter indicates the absolute threshold used for judging event 1e/1f by using

carrier frequency.

12.1.2.34 UE State Indicator Used for UTRAN Neighboring Cell Configuration

OMC Path



>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 (Non-

Cell_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.35 Read SFN Indicator

OMC Path


Management->Utran Cell ->Utran Cell XXX->Neighbouring Cell ->Neighbouring Cell XXX

-> Modify Advanced 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.36 Soft Handover Method

OMC Path



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

12.1.2.37 UTRAN Measurement Quantity for Intra-frequency Measurements

OMC Path



>UTRAN Measurement Quantity for Int ra-frequency Measurements


This parameter indicates the measurement quantity (Ec/No or RSCP) for the intra-

frequency measurement of the cell. The measurement quantity Ec/No is recommended.

12.1.2.38 Reporting Interval for Event 1A/1B/1C/1J

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.39 Amount of Reporting for Event 1A/1B/1C/1J

OMC Path



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.40 Forbidden Cell Indicator for Event 1A/1B

OMC Path


Management->Utran Cell->Utran Cell XXX->Neighbouring Cell-> Neighbouring Cell XXX

->Modify Advanced 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.41 Primary CPICH Power Configuration Tag

OMC Path

Interface Path: View-> View->Configuration Management ->RNC ME->RNC Radio

Resource Management->External Utran Cell-> External Utran CellXXX->Global Else-

>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.1.2.42 Switch for RL Reference Time Adjust During Diversity Mode

OMCR Interface


Management-> Modify Advanced Parameter->RNC Radio Resource Management ->

Switch for RL Reference Time Adjust During Diversity Mode




When the switch is closed, RNC will not send measurement control of 6F/6G to UE;

when it is open, RNC may send measurement control of 6F/6G.

12.1.2.43 Transport Time Delay(NodeB)

OMCR Interface

Path: View->Configuration Management->RNC NE->RNC Radio Resource

Management-> NodeB Configureation Informationxxx-> Modify Advanced Parameter->

Transport Time Delay


This parameter indicates the Iub transport time delay, it could be 20ms/100ms/250ms.

12.1.2.44 Transport Time Delay(externalUtranCell)

OMCR Interface


Management->External UTRAN Cell -> External UTRAN Cell XXX->-> Modify Advanced

Parameter-> Transport Time Delay


This parameter indicates the iub transport time delay of external utran cell, it could be

20ms/100ms/250ms.

12.1.2.45 Neighbouring RNC Feather Switch

OMCR Interface

Path: View->Configuration Management ->RNC NE->RNC Ground Resource

Management->Transmission Configuration->NE Information Configuration->RNC:xx -

>Adjacent RNC Office-> Rnc Config


This parameter indicates the feature of neighbouring RNC.

Bit4=0 means DSCR is not used for inter-RNC handover of HSPA service;

Bit4=1 means DSCR may be used for inter-RNC handover of HSPA service.

12.1.2.46 Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell

OMCR Interface





>Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell


This parameter indicates the maximum bit rate on UL DCH allowed in serving cell for an

NRT PS domain RAB.

12.1.2.47 Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell

OMCR Interface


Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell ->

Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell


This parameter indicates the maximum bit rate on DL DCH allowed in serving cell for an

NRT PS domain RAB.

12.1.2.48 Maximum Bit Rate on UL DCH for RT PS RAB in Serving Cell

OMCR Interface



Maximum Bit Rate on UL DCH for RT PS RAB in Serving Cell


This parameter indicates the maximum bit rate on UL DCH allowed in serving cell for an

RT PS domain RAB.

12.1.2.49 Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell

OMCR Interface



Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell


This parameter indicates the maximum bit rate on DL DCH allowed in serving cell for an

RT PS domain RAB.

12.1.2.50 Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell

OMCR Interface





Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell


This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an

RT PS domain RAB.

12.1.2.51 Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell

OMCR Interface



Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell


This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an

RT PS domain RAB.

12.1.2.52 Maximum Bit Rate on UL DCH for NRT PS RAB in DRNC Cell

OMCR Interface


Management->External UTRAN Cell-> External UTRAN Cell XXX->Modify Advanced

Parameter-> Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell


This parameter indicates the maximum bit rate on UL DCH allowed in DRNC cell for an

NRT PS domain RAB.

12.1.2.53 Maximum Bit Rate on DL DCH for NRT PS RAB in DRNC Cell

OMCR Interface


Management-> External UTRAN Cell-> External UTRAN Cell XXX ->Modify Advanced

Parameter-> Maximum Bit Rate on DL DCH for NRT PS RAB in External UTRAN Cell


This parameter indicates the maximum bit rate on DL DCH allowed in DRNC cell for an

NRT PS domain RAB.

12.1.2.54 Maximum Bit Rate on UL DCH for RT PS RAB in DRNC Cell

OMCR Interface




Management-> External UTRAN Cell -> External UTRAN Cell XXX ->Modify Advanced

Parameter-> Maximum Bit Rate on UL DCH for RT PS RAB in External UTRAN Cell


This parameter indicates the maximum bit rate on UL DCH allowed in DRNC cell for an

RT PS domain RAB.

12.1.2.55 Maximum Bit Rate on DL DCH for RT PS RAB in DRNC Cell

OMCR Interface



Parameter-> Maximum Bit Rate on DL DCH for RT PS RAB in External UTRAN Cell


This parameter indicates the maximum bit rate on DL DCH allowed in DRNC cell for an

RT PS domain RAB.

12.1.2.56 Maximum Bit Rate on E-DCH for NRT PS RAB in DRNC Cell

OMCR Interface



Parameter-> Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell


This parameter indicates the maximum bit rate on UL E-DCH allowed in DRNC cell for

an NRT PS domain RAB.

12.1.2.57 Maximum Bit Rate on E-DCH for RT PS RAB in DRNC Cell

OMCR Interface


Management-> External UTRAN Cell -> External UTRAN Cell XXX ->Modify Advanced

Parameter-> Maximum Bit Rate on E-DCH for RT PS RAB in External UTRAN Cell


This parameter indicates the maximum bit rate on UL E-DCH allowed in DRNC cell for

an RT PS domain RAB.

12.1.2.58 Switch of CS 64kbps Establishment

OMCR Interface




This parameter indicates whether establishing traffic CS 64kbps in serving cell is

allowed or not.

12.1.2.59 Swithc of CS 64kbps Establishment for External UTRAN Cell

OMCR Interface


This parameter indicates whether establishing traffic CS 64kbps in external UTRAN cell

is allowed or not.

12.1.2.60 Primary CPICH Power Configuration

OMC Path


Resource Management->External Utran Cell-> External Utran CellXXX->Global Else->

Primary CPICH Power


This parameter indicates the value of PCPICH transmission power.

12.1.2.61 Neighbouring Cell Monitoring Support Indicator

OMC Path


Management-> RNC Configuration Supplement Information -> Neighbouring Cell

Monitoring Support Indicator


This parameter indicates whether RNC supports neighbouring cell monitoring.

0 means not supported, 1 means supported,

12.2 Inter-Frequency Handover Parameters



MeasPrio Measurement Priority of Neighboring Cell

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_INTER_MEAS_EVENT]

Absolute Threshold of the Quality of the Currently Used Frequency for 2B/2D/2F

Wused[MAX_INTER_MEAS_EVENT]

Weight of the Currently Used Frequency for 2A/2B/2D/2F

Hysteresis[MAX_INTER_MEAS_EVENT]

Hysteresis

TrigTime[MAX_INTER_MEAS_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 Reporting Interval in Period Report Criteria

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

MeaEvt Id[MAX_INTER_MEAS_EVENT]

Inter-frequency Event Identity


EvtMeasEcNo UE Inter-frequency Event Measurement Configuration Index for CPICH Ec/No

EvtMeasRSCP UE Inter-frequency Event Measurement Configuration Index for CPICH RSCP

InterMeasCfgNote Function of Configuration Parameters


UTRACarrierRSSI UTRA Carrier RSSI

FreqQualEst Carrier Frequency Quality Estimation Reporting Indicator



CellSynRptInd Cell Synchronization Information Reporting Indicator

CIdRptInd Cell ID Reporting Indicator

EcN0RptInd CPICH Ec/No Reporting Indicator

RscpRptInd CPICH RSCP Reporting Indicator

PathlossRptInd Pathloss reporting indicator


MeasQuantity Measurement quantity

MeasEvtNum Event Number of Inter-frequency Measurement

StateMode UE State Indicator Used for UTRAN Neighboring Cell 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

PrdRptAmount Amount of Reporting in Period Report Criteria

UseOfHCS(UtranRelation) Use of HCS

PcpichPwrPre Primary CPICH Power Configuration Tag

PcpichPwr Primary CPICH Power

AmrIfHoSwch AMR Inter Frequency Handover Switch

R99RtIfHoSwch R99 RT Inter Frequency Handover Switch

R99NrtIfHoSwch R99 NRT Inter Frequency Handover Switch

HsdpaIfHoSwch HSDPA Inter Frequency Handover Switch

HsupaIfHoSwch HSUPA Inter Frequency Handover Switch

CompMdCfgStra Compressed Mode Configuration Strategy

IfOrRatHoSwch Inter Frequency or Inter RAT Handover Switch


12.2.2.1 Measurement Priority of Neighboring Cell

OMC Path



> 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

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.

12.2.2.3 UL BLER Switch for Handover

OMC Path



>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

OMC Path



>UE Tx Power Switch for Handover




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

OMC Path



DL Tx Power Switch for Handover


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 HCS(UtranCell)

OMC Path



>Use of HCS


This parameter indicates whether the HCS function is used.

12.2.2.7 Use of HCS(UtranRelation)

OMC Path

Interface Path: View-> Configuration Management->RNC NE->RNC Radio Resource

Management-> Utran Cell->Utran Cell XXX->Neighbouring Cell->Neighbouring Cell

XXX->Modify Advanced Parameter->Use of HCS



12.2.2.8 HCS_PRIO(utranCell)

OMC Path





>HCS_PRIO


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)

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

OMC Path



>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

OMC Path



>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

OMC Path



>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

OMC Path



>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

OMC Path



>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 Inter- frequency Handover Tactic

OMC Path



Inter- frequency Handover Tactic


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)

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

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 eve nt 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 Weight of the Currently Used Frequency for 2A/2B/2D/2F

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)

and is related to the measurement quantity and the event type.


OMC Path



Configuration-> Amount of Reporting in Period Report Criteria


This parameter indicates the times of the periodical reports to be repo rted. 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

measurement results.

12.2.2.20 Hysteresis(Inter)

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)

OMC Path

Path:View->Configuration Management->RNC NE->RNC Radio Resource Management-

>Modify Advanced Parameter->UE Inter-frequence Mesurement Configuration-> Time to

Trigger



is detected and the time that the event is reported. The event is triggered a nd the

measurement report is reported only when the event generation is detected and still

meets the requirements of event triggering after Time to trigger.


parameter should be set according to the actual requirements.

12.2.2.22 Absolute Threshold of the Quality of the Non-used Frequency for 2B/2C/2E

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 Weight of the Non-used Frequency for 2A/2B/2C/2E

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)

and is related to the measurement quantity and the event type.


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 report, the UE reports the inter-frequency

measurement results in the period indicated by the parameter.

12.2.2.25 Share Cover Indication

OMC Path


Management->Utran Cell->Utran Cell XXX->Neighbouring Cell ->Neighbouring Cell XXX

-> 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 DPCH Maximum DL Power

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

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)

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 Inter-frequency Measurement Configuration Index Related to Traffic

Category(UtranCell)

OMC Path


Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->

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.29 Inter-frequency Measurement Configuration Index

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

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 Inter-frequency Event Identity

OMC Path



Configuration-> Inter-frequency event identity


This parameter indicates the identify of the event triggered by the inter -frequency

measurement (2a~2f).




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.

Table 12-2 Service Type Related UE Inter-frequency Measurement Parameter ConfigurationDefault Value

Fie

ld N

am

e

Defa

ult

Valu

e 1

Defa

ult

Valu

e 2

Defa

ult

Valu

e 3

Defa

ult

Valu

e 4

Defa

ult

Valu

e 5

Defa

ult

Valu

e 6

Defa

ult

Valu

e 7

Defa

ult

Valu

e 8

Defa

ult

Valu

e 9

TrfCatInterMIdx 1 1 1 1 1 1 1 1 1


PrdMeasEcNo 0 0 0 0 0 0 0 0 0

EvtMeasEcNo 3 3 3 3 3 3 3 3 3

PrdMeasRSCP 4 4 4 4 4 4 4 4 4

EvtMeasRSCP 7 7 7 7 7 7 7 7 7

12.2.2.32 UE Inter-frequency Event Measurement Configuration Index for CPICH

Ec/No

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

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.


OMC Path



Relative to Traffic Category -> UE Period Report Configuration Index for CPICH Ec/No





OMC Path



Relative to Traffic Category->UE Period Measurement Report Configuration Index for

CPICH RSCP





OMC Path





Configuration-> Function of Configuration Parameters


This parameter indicates the purpose and functions of the set of inter -frequency

measurement configuration parameters.


OMC Path



Configuration-> Measurement Report Transfer Mode




12.2.2.38 UTRA Carrier RSSI

OMC Path



Configuration-> UTRA Carrier RSSI


This parameter indicates whether to report the UTRA Carrier RSSI.

12.2.2.39 Carrier Frequency Quality Estimation Reporting Indicator

OMC Path



Configuration-> Carrier Frequency Quality Estimation Reporting Indicator


This parameter indicates whether to report the carrier frequency quality estimation value.



12.2.2.40 Cell Synchronization Information Reporting Indicator

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 Cell ID Reporting Indicator

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 CPICH Ec/No Reporting Indicator

OMC Path



Configuration-> CPICH Ec/No Reporting Indicator


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 CPICH RSCP Reporting Indicator

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 Pathloss reporting indicator

OMC Path



Configuration-> Pathloss reporting indicator



measurement quantity is pathloss.


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 Measurement quantity

OMC Path



Configuration-> Measurement quantity




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 Event Number of Inter-frequency Measurement

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

OMC Path


Management->Utran Cell->Utran Cell XXX->Neighbouring Cell ->Neighouring Cell XXX -

>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

OMC Path


Management-> Utran Cell->Utran Cell XXX->Neighbouring Cell->Neighbouring Cell

XXX->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 Inter-frequency Handover Method

OMC Path



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

12.2.2.51 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT

Measurements

OMC Path



>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 Primary CPICH Power Configuration Tag

OMC Path



Interface Path: View-> View->Configuration Management->RNC ME->RNC Radio


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.2.53 Primary CPICH Power Configuration

OMC Path



Primary CPICH Power


This parameter indicates the value of PCPICH transmission power.

12.2.2.54 AMR Inter Frequency Handover Switch

OMC Path


Management-> Modify Advanced Parameter->RNC Configuration Supplement

Information ->AMR Inter Frequency Handover Switch


This parameter indicates whether AMR inter-frequency handover allowed or not.

12.2.2.55 R99 RT Inter Frequency Handover Switch

OMC Path



Information ->R99 RT Inter Frequency Handover Switch


This parameter indicates whether R99 RT inter-frequency handover allowed or not.

12.2.2.56 R99 NRT Inter Frequency Handover Switch

OMC Path





Information ->R99 NRT Inter Frequency Handover Switch


This parameter indicates whether R99 NRT inter-frequency handover allowed or not.

12.2.2.57 HSDPA Inter Frequency Handover Switch

OMC Path


Management-> RNC Configuration Supplement Information ->HSDPA Inter Frequency

Handover Switch


This parameter indicates whether HSDPA inter-frequency handover allowed or not.

12.2.2.58 HSUPA Inter Frequency Handover Switch

OMC Path


Management-> RNC Configuration Supplement Information ->HSUPA Inter Frequency

Handover Switch


This parameter indicates whether HSUPA inter-frequency handover allowed or not.

12.2.2.59 Compressed Mode Configuration Strategy

OMCR Interface


Management-> Modify Advanced Parameter->RNC Radio Resource Management-

>Compressed Mode Configuration Strategy


This parameter indicates whether inter-frequency and inter-rat compressed mode will be

configured to UE simultaneously or not, when inter-frequency cells and inter-rat

neighboring cells exist.

0: Configure Inter-Frequency and Inter-Rat Compressed Mode Simultaneously

1: Configure Inter-Frequency and Inter-Rat Compressed Mode Individually



12.2.2.60 Inter Frequency or Inter RAT Handover Switch

OMCR Interface


Management->Utran Cell ->Utran Cell XXX->Modify Advanced Parameter->Utran Cell-

>Inter Frequency or Inter RAT Handover Switch


This parameter indicates how to perform neighbor measurement if a cell has both inter -

frequency and inter-RAT cells as its neighbors.

0: Turn off Inter-frequency and Inter-RAT Handover

1: Only Inter Frequency

2: Only Inter Rat

3: Inter Frequency is Prior to Inter Rat

12.3 SRNC Relocation Parameters


Parameter Field Name Name on the Interface

Trelocprep SRNC Wait Time for Relocation Preparation (100ms)

Trelocoverall SRNC Overall Protective Time for Relocation (100ms)

CsReDelayTimer Timer of Relocation Delay for CS Service

PsReDelayTimer Timer of Relocation Delay for PS Service

Tdatafwd Maximum Time for Forwarding GTP -PDU Data in SRNC


12.3.2.1 SRNC Wait Time for Relocation Preparation

OMC Path

Interface Path: view->Configuration Management->RNC NE->RNC Radio Resource

Management->Modify Advanced Parameter->Iu Interface Timers and Constants->SRNC

Wait Time for Relocation Preparation(100ms)


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 SRNC Overall Protective Time for Relocation

OMC Path


Management->Modify Advanced Parameter->Iu Interface Timers and Constants->SRNC

Overall Protective Time for Relocation(100ms)


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 Timer of Relocation Delay for CS Service

OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Ground Resource


>Adjacent RNC Office-> RNC Config ->Timer of Relocation Delay for CS Service


This parameter is applicable to CS services. It indicates the delay of initiating the

relocation procedure after the link at the S side is deleted.

12.3.2.4 Timer of Relocation Delay for PS Service

OMC Path



>Adjacent RNC Office-> RNC Config -> Timer of Relocation Delay for PS Service


This parameter is applicable to PS services. It indicates the delay of initiating the

relocation procedure after the link at the S side is deleted.



12.3.2.5 Maximum Time for Forwarding GTP-PDU Data in SRNC

OMC Path


Management->Modify Advanced Parameter->Iu Interface Timers and Constants-

>Maximum Time for Forwarding GTP-PDU Data in SRNC(100ms)


This parameter specifies the maximum time for GTP -PDU forwarding at the source RNC

during relocation of SRNS.

12.4 Inter-RAT Handover Parameters



MeasPrio Measurement Priority of Neighboring GSM Cell

RatHoTactic Inter-Rat Handover Tactic

UlBlerHoSwch UL BLER Switch for handover

DlPwrHoSwch DL Tx Power Switch for handover

UlPwrHoSwch UE Tx Power Switch for handover

Thresh[MAX_RAT_MEAS_EVENT]

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_EVENT]

Absolute Threshold of the Quality of Other RAT for 3A/3B/3C

Hysteresis[MAX_RAT_MEAS_EVENT]

Hysteresis

TrigTime[MAX_RAT_MEAS_EVENT]

Time to Trigger

TrfCatRatMIdx(CRat) Inter-RAT Measurement Configuration Index Related to Traffic Category

TrfCatRatMIdx(utranCell)


EvtMeasRSCP UE Event Report Configuration Index for Own System CPICH RSCP

InterRatCfgNo Inter-RAT Measurement Configuration Index

InterRatCfgNote Function of Configuration Parameters


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

GeranCellInd GERAN Cell Indicator


EventNum Inter-RAT Measurement Event Number

Event Id [MAX_RAT_MEAS_EVENT]

Inter-RAT Event Identity

CellIndivOffset(gsmRelation) Cell individual offset(gsmRelation)

GsmStateMode UE State Indicator Used for GSM Neighboring Cell Configuration

GsmShareCover Share Cover Indication

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 Amount of Reporting in Period Report Criteria

PrdMeasRSCP Reporting Interval in Period Report Criteria

UseOfHCS(gsmRelation) Use of HCS

HcsPrio (gsmRelation) HCS_PRIO

PsInterSysHoSupp PS Inter-System Handover Indicator

DtmSuppInd Inter-System DTM Support Indicator

BscFeatSwitch Neighbouring BSC Feather Switch

LdBsdIntSysHOInd Loading based InterSys HO Support Indicator

CellLdInfoVldTim Duration of Valid Cell Load Infor

GsmUlRtLdThrd GSM Uplink RT Load Threshold

GsmUlLdThrd GSM Uplink Load Threshold

GsmDlLdThrd GSM Downlink Load Threshold

NaccSuppInd Nacc Support Indicator

HoToGsmPenTimer Handover to GSM Penalty Timer

ServBasedHoInd Service-Based Handover Support Indicator

ServHoSwch Service Handover Switch

ServHoComStra Service Handover Combination Strategy

AmrRatHoSwch AMR Inter Rat Handover Switch

R99RtRatHoSwch R99 RT Inter Rat Handover Switch

R99NrtRatHoSwch R99 NRT Inter Rat Handover Switch



HsdpaRatHoSwch HSDPA Inter Rat Handover Switch

HsupaRatHoSwch HSUPA Inter Rat Handover Switch

T4StpIfMeaActRat Timer for Stopping Inter-frequency Measurement and Activating Inter-RAT Measurement

ServHoInd Service Handover Strategy Indicator

AmrServHoStra Service Handover Strategy of RNC for AMR

CS64ServHoStra Service Handover Strategy of RNC for CS64

PsRtServHoStra Service Handover Strategy of RNC for PS RT service

PsNrtServHoStra Service Handover Strategy of RNC for PS NRT service

TWaitContextReq Waiting Timer for SRNS Context Request

TWaitDataFwd Waiting Timer for SRNS DATA FORWARD COMMAND

TWaitRelCmd Waiting Timer for IU RELEASE COMMAND


12.4.2.1 Measurement Priority of Neighboring GSM Cell

OMC Path


Management->Utran Cell->Utran Cell XXX->GSM Neighbouring Cell->GSM

Neighbouring Cell XXX-> 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.

12.4.2.2 Inter-Rat Handover Tactic

OMC Path



>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 UL BLER Switch for Handover

OMC Path



>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 i f the uplink

BLER quality arrives at the threshold.

12.4.2.4 DL Tx Power Switch for handover

OMC Path



DL Tx Power Switch for Handover


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 UE Tx Power Switch for handover

OMC Path



UE Tx Power Switch for Handover




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

OMC Path


Management-> Modify Advanced Parameter->UE Inter-RAT Measurement Configuration

Information->Absolute Threshold of the Quality of UTRAN Cell for 3A


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 Weight of the UTRAN System for 3A

OMC Path



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

OMC Path



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)

OMC Path



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)

OMC Path



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)

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

should use a different index. Hence, the inter-RAT handover parameters may be

different from each other.

12.4.2.12 Inter-RAT Measurement Configuration Index Related to Traffic

Category(UtranCell)

OMC Path



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

should use a different index. Hence, the inter-RAT handover parameters may be

different from each other.


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.

Table 12-3 Service Type Related UE Inter-RAT Measurement Parameter Configuration

Default Value

Fie

ld N

am

e

Defa

ult

Valu

e 1

Defa

ult

Valu

e 2

Defa

ult

Valu

e 3

Defa

ult

Valu

e 4

Defa

ult

Valu

e 5

Defa

ult

Valu

e 6

Defa

ult

Valu

e 7

Defa

ult

Valu

e 8

Defa

ult

Valu

e 9

TrfCatRatMIdx 1 1 1 1 1 1 1 1 1


PrdMeasEcNo 0 0 0 0 0 0 0 0 0

EvtMeasEcNo 2 2 2 2 2 2 2 2 2

PrdMeasRSCP 3 3 3 3 3 3 3 3 3

EvtMeasRSCP 5 5 5 5 5 5 5 5 5

12.4.2.14 UE Event Report Configuration Index for Own System CPICH RSCP

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

OMC Path





Traffic Category Configuration Information ->UE Event Report Configuration Index for

Own System CPICH Ec/No


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 Inter-RAT Measurement Configuration Index

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 TrfCat InterMIdx) 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.


OMC Path


Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration

Information-> Function of Configuration Parameters


This parameter indicates the purpose and functions of the set of inter-RAT measurement

configuration parameters.




OMC Path



Information-> Measurement Report Transfer Mode




12.4.2.19 UTRAN Filter Coefficient(Rat)

OMC Path


Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration

Information->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 UTRAN Measurement quantity

OMC Path



Information->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.



12.4.2.21 GSM Filter Coefficient(Rat)

OMC Path



Information->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 GSM BSIC Verification Required Indicatior

OMC Path



Information-> GSM BSIC Verification Required Indicatior


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 GERAN Cell Indicator

OMC Path


Management->External GSM Cell->GSM Cell XXX->GERAN Cell Indicator


This parameter indicates whether the cell is a GERAn cell.

12.4.2.24 UTRAN Quality Estimation Reporting Indicator

OMC Path



Information-> UTRAN Quality Estimation Reporting Indicator




This parameter indicates whether to report the quality estimation value of the UTRAN

system.

12.4.2.25 GSM Carrier RSSI Reporting Indicator

OMC Path



Information-> GSM Carrier RSSI Reporting Indicator


This parameter indicates whether to report the received signal strength indicator (RSSI)

of GSM cells.


OMC Path



Information-> Report Criteria


This parameter indicates the criteria of reporting the inter-RAT measurement, including

the Event Reporting and Periodical Reporting.

12.4.2.27 Inter-RAT Measurement Event Number

OMC Path



Information-> Inter-RAT Measurement Event Number


This parameter indicates the number of events that should be configured for the inter-

RAT measurement configuration index for a certain purpose.



12.4.2.28 Inter-RAT Event Identity

OMC Path



Configuration Information-> Inter-RAT event identity


This parameter indicates the identity of the event triggered by the inter -RAT

measurement (3a~3d).

12.4.2.29 Cell individual offset(gsmRelation)

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.30 UE State Indicator Used for GSM Neighboring Cell Configuration

OMC Path



Neighbouring Cell XXX ->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 lis t 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 (Non-

Cell_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.31 Share Cover Indication

OMC Path



Neighbouring Cell XXX ->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.32 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT

Measurements

OMC Path



>UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements


This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for inter-

frequency and inter-RAT measurements. The measurement quantity RSCP is

recommended.

12.4.2.33 Inter-RAT Handover Method

OMC Path



>Inter-RAT Handover Method




This parameter indicates the handover method of Inter-RAT Handover.At present, Inter-

RAT measurement supports only the handover modes reported through events. The

IntRatHoMth parameter is invalid.


OMC Path



Traffic Category Configuration Information -> Period Report Configuration Index for Own

System CPICH Ec/No


Only event report can be supported currently. So the following parameters for

periodically report is invalid: PrdMeasEcNo(RAT), PrdMeasRSCP(RAT),

PrdRptAmount(RAT), PrdRptInterval(RAT)


OMC Path



Traffic Category Configuration Information ->Period Report Configuration Index for Own

System CPICH RSCP






OMC Path


Management->Modify Advanced Parameter-> UE Inter-Rat Measurement Configuration

Information->Amount of Reporting in Period Report Criteria








OMC Path


Management->Modify Advanced Parameter-> UE Inter-Rat Measurement Configuration

Information->Reporting Interval in Period Report Criteria(ms)





12.4.2.38 Use of HCS (gsmRelation)

OMC Path



Neighbouring Cell XXX ->Modify Advanced Parameter-> Use of HCS



12.4.2.39 HCS_PRIO(gsmRelation)

OMC Path


Management->External GSM Cell->External GSM Cell XXX->Modify Advanced

Parameter-> HCS_PRIO


This parameter indicates the HCS priority level of the gsm 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.2.40 PS Inter-System Handover Indicator

OMC Path


Management-> RNC Configuration Supplement Information ->PS Inter-System

Handover Indicator




This parameter indicates whether RNC supports PS inter-RAT handover. 0 indicates not

support, 1 indicates support.

12.4.2.41 Inter-System DTM Support Indicator

OMC Path


Management-> RNC Configuration Supplement Information ->Inter-System DTM

Support Indicator


This parameter indicates whether RNC supports DTM mode, that is whether supports

inter-RAT handover both for CS domain services and PS domain services at the same

time. 0 indicates not support, 1 indicates support.

12.4.2.42 Neighbouring BSC Feather Switch

OMC Path


Management->Transmission Configuration->NE Information Configuration->BSC:xx -

>BSC Office->BSC Config


This parameter indicates neighbouring BSC feather switch.

12.4.2.43 Loading Based InterSys HO Support Indicator

OMC Path


Management-> RNC Configuration Supplement Information ->Loading Based InterSys HO

Support Indicator


This parameter indicates whether the target cell load information is taken into

consideration during the inter system handover procedure.

12.4.2.44 Duration of Valid Cell Load Info

OMC Path


Management-> Modify Advanced Parameter->RNC Configuration Supplement Informat ion -

>Duration of Valid Cell Load Info




This parameter indicates the duration of inter-sys cell’s load information which is valid to

use before updating.

12.4.2.45 GSM Uplink RT Load Threshold

OMC Path


Management->External GSM Cell->GSM Cell XXX->Modify Advanced Parameter-

>GSM Uplink RT Load Threshold


This parameter indicates the uplink overload threshold for RT service in GSM system.

12.4.2.46 GSM Downlink RT Load Threshold

OMC Path



>GSM Downlink RT Load Threshold


This parameter indicates the downlink overload threshold for RT service in GSM system.

12.4.2.47 GSM Uplink Load Threshold

OMC Path



>GSM Uplink Load Threshold


This parameter indicates the uplink overload threshold in GSM system.

12.4.2.48 GSM Downlink Load Threshold

OMC Path


Management->External GSM Cell->GSM Cell XXX->Modify Advanced Parameter->GSM

Downlink Load Threshold




This parameter indicates the downlink overload threshold in GSM system.

12.4.2.49 Nacc Support Indicator

OMC Path


Management-> RNC Configuration Supplement Information ->Nacc Support Indicator


This parameter indicates whether RNC supports NACC function or not.

12.4.2.50 Handover to GSM Penalty Timer

OMC Path


Management-> Modify Advanced Parameter-> RNC Radio Resource Management-

>Handover to GSM Penalty Timer


When handover from UMTS to GSM is failed, the timer initiates, and RNC will not handle

inter-RAT measurement report until the timer is expiry.

12.4.2.51 Service-Based Handover Support Indicator

OMC Path



Information ->AMR Inter Rat Handover Switch


This parameter indicates whether RNC supports handover based on service.

12.4.2.52 Service Handover Switch

OMC Path



Service Handover Switch




This parameter indicates whether sevice handover is allowed or not. When the “Service

Handover” IE is included in RAB assignment request, if the switch is open, RNC will

perform related process according to the value of “Service Handover” IE, otherwise RNC

will ignore the “Service Handover” IE.

12.4.2.53 Service Handover Combination Strategy

OMC Path



>Service Handover Combination Strategy


This parameter indicates the service handover combination strategy in multi-RAB, and

RNC will perform related process according to the highest priority value of IE “service

handover”.

12.4.2.54 AMR Inter Rat Handover Switch

OMC Path



Information ->AMR Inter Rat Handover Switch


This parameter indicates whether AMR inter-Rat handover is allowed or not.

12.4.2.55 R99 RT Inter Rat Handover Switch

OMC Path



Information ->R99 RT Inter Rat Handover Switch


This parameter indicates whether R99 RT inter-Rat handover is allowed or not.

12.4.2.56 R99 NRT Inter Rat Handover Switch

OMC Path





Information ->R99 NRT Inter Rat Handover Switch


This parameter indicates whether R99 NRT inter-Rat handover is allowed or not.

12.4.2.57 HSDPA Inter Rat Handover Switch

OMC Path


Management-> RNC Configuration Supplement Information ->HSDPA Inter Rat

Handover Switch


This parameter indicates whether HSDPA inter-Rat handover is allowed or not.

12.4.2.58 HSUPA Inter Rat Handover Switch

OMC Path


Management-> RNC Configuration Supplement Information ->HSUPA Inter Rat

Handover Switch


This parameter indicates whether HSUPA inter-Rat handover is allowed or not.

12.4.2.59 Timer for Stopping Inter-frequency Measurement and Activating Inter-RAT

Measurement

OMCR Interface



>Timer for Stopping Inter-frequency Measurement and Activating Inter-RAT

Measurement


This parameter indicates the time interval of issuing inter-frequency measurement and

inter-RAT measurement. When RNC issues inter-frequency measurement, the timer is

start. If the quality of non-used frequency is bad during the time length indicated by this

parameter, RNC will issue inter-RAT measurement if there is an inter-RAT neighboring

cell.



The larger the value is, the slower the inter-RAT measurement is initialized, and vice

versa.

12.4.2.60 Service Handover Strategy Indicator

OMCR Interface



>Service Handover Strategy Indicator


This parameter indicates the service handover strategy controlled by RNC.

Bit0=0/1: Ignore Service Handover IE for AMR Service/Apply Service handover IE

for AMR Service

Bit1=0/1: Ignore Service handover IE for CS64 service/(Apply Service Handover IE

for CS64 Service

Bit2=0/1: Ignore Service Handover IE for PS RT Service/Apply Service Handover IE

for PS RT Service

Bit3=0/1: Ignore Service Handover IE for PS NRT Service/Apply Service Handover

for PS NRT Service

Bit4~Bit7 reserved, fixed to 0

12.4.2.61 Service Handover Strategy of RNC for AMR

OMCR Interface



>Service Handover Strategy of RNC for AMR


This parameter indicates the service handover strategy for AMR.

0:should be performed（should be performed）

1:should not be performed（should not be performed）

2: shall not be performed（shall not be performed）



12.4.2.62 Service Handover Strategy of RNC for CS64

OMCR Interface



>Service Handover Strategy of RNC for CS64


This parameter indicates the service handover strategy for CS64.




12.4.2.63 Service Handover Strategy of RNC for PS RT service

OMCR Interface



>Service Handover Strategy of RNC for PS RT service


This parameter indicates the service handover strategy for PS RT service.




12.4.2.64 Service Handover Strategy of RNC for PS NRT service

OMCR Interface



>Service Handover Strategy of RNC for PS NRT service


This parameter indicates the service handover strategy for PS NRT service.






12.4.2.65 Waiting Timer for SRNS Context Request

OMCR Interface


Management-> Modify Advanced Parameter-> Iu Interface Timers and Constants

Information-> Waiting Timer for SRNS Context Request


This parameter indicates timer length waiting for SRNS CONTEXT REQUEST.

12.4.2.66 Waiting Timer for SRNS DATA FORWARD COMMAND

OMCR Interface



Information-> Waiting Timer for SRNS Data Forward Command


This parameter indicates timer length waiting for SRNS DATA FORWARD COMMAND.

12.4.2.67 Waiting Timer for IU RELEASE COMMAND

OMCR Interface



Information-> Waiting Timer for Iu Release Command


This parameter indicates timer length that waiting for IU RELEASE COMMAND.

12.5 IMSI-based Handover Parameters



BasedImsiHoInd Handover Based on IMSI Support



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)

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)

SNAC[MAX_NUM_SNAC_PE

R_UTRANCEL](externalUtranCell)

Shared Network Area Code(ExternalUtranCell )

SNACNum(externalUtranCell) Shared Network Area Code Number(ExternalUtranCell )

SNAC[MAX_NUM_SNAC_PE

R_GSMCEL](externalGsmCell)

Shared Network Area Code(externalGsmCell )

SNACNum(externalGsmCell ) Shared Network Area Code Number (externalGsmCell)


12.5.2.1 Handover Based on IMSI Support

OMC Path


Management-> RNC Configuration Supplement Information ->Handover Based on IMSI

Support Indicator




This parameter indicates whether RNC supports handover based IMSI or not.

12.5.2.2 MCC(rncPnSnac)

OMC Path


Management->User Authorized PLMN+SNAC Information->MCC


This parameter indicates the mobile country code (MCC) of the IMSI card. See 0 in the

text for the use case.

12.5.2.3 MNC(rncPnSnac)

OMC Path


Management->User Authorized PLMN+SNAC Information->MNC


This parameter indicates the mobile network code (MNC) of the IMSI card. See 0 in the

text for the use case.

12.5.2.4 Extend Information Digits Num

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.

12.5.2.5 Extend Information

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.5.2.6 MCC of Shared Network

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.

12.5.2.7 MNC of Shared Network

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.5.2.8 Shared Network Area Code

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.



12.5.2.9 MCC(rncLcSnac)

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 0 in the text for the use case.

12.5.2.10 MNC(rncLcSnac)

OMC Path


Management->LAC and SNAC Information->MNC


This parameter in combination with parameters MCC(rncLcSnac), LAC(rncLcSnac),



12.5.2.11 Location Area Code(rncLcSnac)

OMC Path


Management->LAC and SNAC Information->Location Area Code


This parameter in combination with parameters MCC(rncLcSnac), MNC(rncLcSnac),



12.5.2.12 Shared Network Area Code(rncLcSnac)

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

0 in the text for the use case.

12.5.2.13 Mobile Country Code(UtranCell)

OMC Path


Management->Utran Cell->Utran Cell XXX->UtranCell Global Info>MCC


This parameter indicates the MCC of the cells in the RNC.

12.5.2.14 Mobile Country Code(ExternalUtranCell)

OMC Path


Management->External Utran Cell->External Utran Cell XXX->MCC


This parameter indicates the MCC of UTRAN cells that do not belong to the RNC.

12.5.2.15 Mobile Country Code(externalGsmCell)

OMC Path


Management-> Gsm Cell ->Gsm Cell XXX->MCC


This parameter indicates in the MCC of the GSM cells.

12.5.2.16 Mobile Network Code(UtranCell)

OMC Path


Management->Utran Cell->Utran Cell XXX->UtranCell Global Info>MNC




This parameter indicates the MNC of the cells in the RNC.

12.5.2.17 Mobile Network Code(ExternalUtranCell)

OMC Path


Management->External Utran Cell->External Utran Cell XXX->MNC


This parameter indicates the MNC of the cells that do not belong to the RNC.

12.5.2.18 Mobile Network Code(externalGsmCell)

OMC Path


Management->Gsm Cell->Gsm Cell XXX ->MNC


This parameter indicates in the MNC of the GSM cells.

12.5.2.19 Location Area Code(UtranCell)

OMC Path


Management->Utran Cell ->Utran Cell XXX->UtranCell Global Info>LAC


This parameter indicates the LAC of the cells in the RNC.

12.5.2.20 Location Area Code(externalUtranCell)

OMCR Interface


Management->External Utran Cell->External Utran Cell XXX->Location Area Code




This parameter indicates the LAC of UTRAN cells that do not belong to the RNC.

12.5.2.21 Shared Network Area Code(ExternalUtranCell)

OMC Path


Management->External Utran Cell->External Utran Cell XXX->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.5.2.22 Shared Network Area Code Number(ExternalUtranCell)

OMC Path


Management-> External Utran Cell ->External Utran Cell XXX->SNACNum


This parameter indicates the number of shared network area code that the neighboring

cell belongs to.

12.5.2.23 Shared Network Area Code(externalGsmCell)

OMC Path


Management->Gsm Cell ->Gsm Cell XXX->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.5.2.24 Shared Network Area Code Number(externalGsmCell)

OMC Path


Management->Gsm Cell ->Gsm Cell XXX->SNACNum




This parameter indicates the number of shared network area code that the neighboring

cell belongs to.

12.6 HSDPA Handover Parameters



HspaSptMeth HSPA Support Method

T1d Timer for Event 1D in HSPA or MBMS


HsdpaCmAssoMode HSDPA Associate CM Method


12.6.2.1 HSPA Support Method

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 Timer for Event 1D in HSPA or MBMS

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 t ransition between the HS and DCH channels. A large value of

this parameter helps to avoid too frequent HSPA serving cell change and channel

transition.




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.

12.6.2.4 HSDPA Associate CM Method

OMCR Interface


Management-> Modify Advanced Parameter->Hspa Configuration Information-> HSDPA

Associate CM Method


This parameter indicates the association between HSDPA and CM method.

The value “Serial” means HSDPA service will be reconfigured to DCH cannel before the

compress mode is activated.;

The default value is parallel.

12.7 HSUPA Handover Parameters



HspaSptMeth HSPA Support Method


HsupaCmAssoMode HSUPA Associate CM Method




12.7.2.1 HSPA Support Method

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.


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

inter-frequency hard handover between RNSs or whether the Iur interface supports the

HSDPA/UPA feature.

12.7.2.3 HSUPA Associate CM Method

OMCR Interface


Management-> Modify Advanced Parameter->Hspa Configuration Information-> HSUPA

Associate CM Method


This parameter indicates the association between HSUPA and CM method.

The value “Serial” means HSUPA service will be reconfigured to DCH cannel before the

compress mode is activated.;

The default value is serial.



12.8 MBMS Handover Parameters



MbmsSuptInd Support MBMS Indicator

T1d Timer for Event 1D in HSPA or MBMS


12.8.2.1 Support MBMS Indicator

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.

12.8.2.2 Timer for Event 1D in HSPA or MBMS

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 t ransition 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

C310322211

Statistics of soft handover prepare

C310322212

C310322213

C310322214

C310322215

C310322216

Number of active set update attempted to add cell, by procedure C310322217

C310322218

C310322219

Number of active set update failed to add cell, by procedure C310322220

C310322221

C310322222

Number of active set update failed to add cell, by cause

C310322223

C310322224

C310322225

C310322226

C310322227

C310322228

C310322229

C310322230

C310322231

C310322232

Number of active set update attempted to delete cell, by procedure C310322233

C310322234



C310322235

Number of active set update failed to delete cell, by cause

C310322236

C310322237

C310322238

C310322239

C310322240

C310322241

C310322242

C310322243

C310322244

C310322245

Number of active set update attempted to add cell, by traffic class C310322246

C310322247

C310322248

C310322249

Number of active set update failed to add cell, by traffic class C310322250

C310322251

C310322252

C310322253

Number of active set update attempted to delete cell, by traffic class C310322254

C310322255

C310322256

C310322257

Number of active set update failed to delete cell, by traffic class C310322258

C310322259

C310322260

C310322261

Number of active set update attempted to add cell, by traffic class

C310322262

C310322263

C310322264

C310322265

C310322266

C310322267

C310322268

C310322269

Number of active set update failed to add cell, by traffic class

C310322270

C310322271

C310322272

C310322273

C310322274



C310322275

C310322276

C310322277

Number of active set update attempted to delete cell, by traffic class

C310322278

C310322279

C310322280

C310322281

C310322282

C310322283

C310322284

C310322285

Number of active set update failed to delete cell, by traffic class

C310322286

C310322287

C310322288

C310322289

C310322290

C310322291

C310322292

C310322293

Statistics of active set update for HS-DSCH C310322294

C310322295

C310322296

C310322297 Number of active set update attempted to add cell for E-DCH, by procedure

C310322298

C310322299

C310322300 Number of active set update failed to add cell for E-DCH, by procedure

C310322301

C310322302

C310322303

Number of active set update failed to add cell for E-DCH, by cause

C310322304

C310322305

C310322306

C310322307

C310322308

C310322309

C310322310

C310322311

C310322312

C310322313 Number of active set update attempted to delete cell for E-DCH, by procedure C310322314



C310322315

C310322316

Number of active set update failed to delete cell for E-DCH, by cause

C310322317

C310322318

C310322319

C310322320

C310322321

C310322322

C310322323

C310322324

C310322325

C310322326

Number of active set update attempted to add cell for E-DCH, by traffic class

C310322327

C310322328

C310322329

C310322330

Number of active set update failed to delete cell for E-DCH, by traffic class

C310322331

C310322332

C310322333

C310322334

Number of active set update attempted to delete cell for E-DCH, by traffic class

C310322335

C310322336

C310322337

C310322338

Number of active set update failed to delete cell for E-DCH, by traffic class

C310322339

C310322340

C310322341

C310322342

Number of active set update for attempted add cell with multi -traffic C310322343

C310322344

C310322345

Number of active set update for failed add cell with multi-t raffic C310322346

C310322347

C310322348

Soft handover ratio

C310322349

C310322350

C310322351

C310322352

C310322353

C310322354



C310322355

C310322356

C310322357

C310322358

C310322359

C310322360

C310322361

Soft handover rate of E-DCH user C310322362

C310322363

C310322364

C310322379

Number of UE having DCH active set cell in cell

Number of UE having DCH active set cell in cell

C310322380

C310322381

C310322382

C310322383

C310322384

C310322385

C310322386

C310322387

C310322388

C310322389

C310322390

C310322391

C310322392

C310322393

C310322394

C310322395

C310322396

C310322397

C310322398

C310322399

C310322400

C310322401

C310322402

C310322403

C310322404

C310322405

C310322406

C310322407

C310322408



C310322409

C310322410

C310322475

Number of UE having E-DCH active set cell in cell

C310322476

C310322477

C310322478

C310322479

C310322480

C310322481

C310322482

C310322483

C310322484

C310322485

C310322486

C310322487

Statistics of active set update, by traffic

C310322488

C310322489

C310322490

C310322491

C310322492

C310322493

C310322494

C310322495

Statistics of active set update, by domain

C310322496

C310322497

C310322498

C310322499

C310322500

C310322501

C310322502

13.1.2 RNC Hard Handover Statistics


C310332503

Number of int ra-Node B hard handover statistics

C310332504

C310332505

C310332506

C310332507

C310332508

C310332509



C310332510

C310332511

C310332512

C310332513

C310332514

C310332515

C310332516

C310332517

C310332518

C310332519

C310332520

C310332521

C310332522

C310332523

C310332524

C310332525

Number of inter-Node B hard handover statistics

C310332526

C310332527

C310332528

C310332529

C310332530

C310332531

C310332532

C310332533

C310332534

Number of inter-Node B hard handover statistics

C310332535

C310332536

C310332537

C310332538

C310332539

C310332540

C310332541

C310332542

C310332543

C310332544

C310332545

C310332546

C310332547

Number of SRNC Iur hard handover statistics C310332548

C310332549



C310332550

C310332551

C310332552

C310332553

C310332554

C310332555

C310332556

C310332557

C310332558

C310332559

C310332560

C310332561

C310332562

C310332563

C310332564

C310332565

C310332566

C310332567

C310332568

C310332569

Number of SRNC Iur hard handover statistics, by channel type

C310332570

C310332571

C310332572

C310332573

C310332574

Number of SRNC Iur hard handover statistics, by channel type

C310332575

C310332576

C310332577

C310332578

C310332579

C310332580

C310332581

C310332582

C310332583

C310332584

C310332585

C310332586

C310332587

C310332588

C310332589



C310332590

C310332591

C310332592

C310332593

C310332594

C310332595

C310332596

C310332597

Number of hard handover statistics, by source cause

C310332598

C310332599

C310332600

C310332601

C310332602

C310332603

C310332604

C310335701

Number of hard handover statistics,by inner source cause

C310335702

C310335703

C310335704

C310335705

C310335706

C310335707

C310335708

C310335738

C310332605

Number of CS hard handover statistics, by measurement quality

C310332606

C310332607

C310332608

C310332609

C310332610

C310332611

C310332612

C310332613

C310332614

C310332615

C310332616

C310332617

C310332618

C310332619

C310332620



C310332621

C310332622

C310332623

C310332624

C310332625

C310332626

C310332627

Number of PS hard handover statistics, by measurement quality

C310332628

C310332629

C310332630

C310332631

C310332632

C310332633

C310332634

C310332635

C310332636

C310332637

C310332638

C310332639

C310332640

C310332641

C310332642

C310332643

C310332644

C310332645

C310332646

C310332647

C310332648

C310332649

Number of hard handover statistics, by traffic class

C310332650

C310332651

C310332652

C310332653

C310332654

C310332655

C310332656

C310332657

C310332658

C310332659

C310332660



C310332661

C310332662

C310332663

C310332664

C310332665

Number of hard handover statistics, by domain

C310332666

C310332667

C310332668

C310332669

C310332670

C310332671

C310332672

C310332673

Number of int ra-RNC hard handover statistics, by channel type

C310332674

C310332675

C310332676

C310332677

C310332678

C310332679

C310332680

C310332681

C310332682

C310332683

C310332684

C310332685

C310332686

C310332687

C310332688

C310332689

C310332690

C310332691

C310332692

C310332693

C310332694

C310332695

C310332696

C310332697

C310332698

C310332699

C310332700



C310336076

Statistics of hard handover outgoing by siganlling

C310336077

C310336078

C310336079

C310336080

C310336081

C310336082

C310336083

C310336084

C310336085

C310336086 Statistics of hard handover outgoing by siganlling

13.1.3 Cell Relocation Statistics


C310342701

Statistics of attempted relocation preparation, by channel type

C310342702

C310342703

C310342704

C310342705

C310342706

C310342707

C310342708

C310342709

C310342710

C310342711

C310342712

C310342713

C310342714

C310342715

Statistics of attempted outgoing relocation, by channel type

C310342716

C310342717

C310342718

C310342719

C310342720

C310342721

C310342722

C310342723

C310342724

C310342725

C310342726



C310342727

C310342728

C310342729

Number of attempted relocation preparation, by traffic class

C310342730

C310342731

C310342732

C310342733

C310342734

C310342735

C310342736

C310342737

Number of attempted outgoing relocation, by traffic class

C310342738

C310342739

C310342740

C310342741

C310342742

C310342743

C310342744

C310342745

Number of attempted relocation preparation with UE not involved for CS domain, by cause

C310342746

C310342747

C310342748

C310342749

C310342750

C310342751

C310342752

Number of failed relocation preparation with UE not involved for CS domain, by cause

C310342753

C310342754

C310342755

C310342756

C310342757

C310342758

C310342759

C310342760

C310342761 Number of attempted outgoing relocation with UE not involved for CS domain

C310342762 Number of failed outgoing relocation with UE not involved for CS domain, by cause C310342763

C310342764 Number of attempted relocation preparation with UE involved for CS domain, by cause

C310342765

C310342766



C310342767

C310342768

C310342769

C310342770

C310342771

Number of failed relocation preparation with UE involved for CS domain, by cause

C310342772

C310342773

C310342774

C310342775

C310342776

C310342777

C310342778

C310342779

C310342780 Number of attempted outgoing relocation with UE involved for CS domain

C310342781

Number of failed outgoing relocation with UE involved for CS domain, by cause

C310342782

C310342783

C310342784

C310342785

C310342786

C310342787

C310342788

C310342789

C310342790

C310342791

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

C310342792

C310342793

C310342794

C310342795

C310342796

C310342797

C310342798

Number of failed relocation preparation with UE not involved for PS domain, by cause

C310342799

C310342800

C310342801

C310342802

C310342803

C310342804

C310342805

C310342806



C310342807 Number of attempted outgoin relocation with UE not involved for PS domain

C310342808 Number of failed outgoing relocation with UE not involved for PS domain, by cause C310342809

C310342810

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

C310342811

C310342812

C310342813

C310342814

C310342815

C310342816

C310342817

Number of failed relocation preparation with UE involved for PS domain, by cause

C310342818

C310342819

C310342820

C310342821

C310342822

C310342823

C310342824

C310342825

C310342826 Number of attempted outgoing relocation with UE involved for PS domain

C310342827

Number of failed outgoing relocation with UE involved for PS domain, by cause

C310342828

C310342829

C310342830

C310342831

C310342832

C310342833

C310342834

C310342835

C310342836

C310342837

Number of attempted incoming relocation with UE not involved for CS domain, by cause

Number of attempted incoming relocation with UE not involved for CS domain, by cause

C310342838

C310342839

C310342840

C310342841

C310342842

C310342843

C310342844 Number of failed incoming relocation with UE not involved for CS domain, by cause C310342845



C310342846

C310342847

C310342848

C310342849 Number of attempted incoming relocation with UE involved for CS domain, by cause C310342850

C310342851

Number of attempted incoming relocation with UE involved for CS domain, by cause

C310342852

C310342853

C310342854

C310342855

C310342856

Number of failed incoming relocation with UE involved for CS domain, by cause

C310342857

C310342858

C310342859

C310342860

C310342861

Number of attempted incoming relocation with UE not involved for PS domain, by cause

C310342862

C310342863

C310342864

C310342865

C310342866

C310342867

C310342868

Number of failed incoming relocation with UE not involved for PS domain, by cause

C310342869

C310342870

C310342871

C310342872

C310342873

Number of attempted incoming relocation with UE involved for PS domain, by cause

C310342874

C310342875

C310342876

C310342877

C310342878

C310342879

C310342880

Number of failed incoming relocation with UE involved for PS domain, by cause

C310342881

C310342882

C310342883

C310342884



13.1.4 Inter-RAT Cell Handover Statistics


C310352885

Number of attempted incoming inter-RAT handover for CS domain

C310352886

C310352887

C310352888

C310352889

C310352890

C310352891

C310352892

Number of failed incoming inter-RAT handover for CS domain

C310352893

C310352894

C310352895

C310352896

C310352897

Number of attempted incoming inter-RAT handover for PS domain

C310352898

C310352899

C310352900

C310352901

C310352902

C310352903

C310352904

Number of failed incoming inter-RAT handover for PS domain

C310352905

C310352906

C310352907

C310352908

C310352909 Number of attempted incoming inter-RAT handover for PS domain(Cell Re-selection)

C310352910 Number of successful incoming inter-RAT handover for PS domain(Cell Re-selection)

C310352911

Number of attempted relocation preparation for outgoing CS inter-RAT handovers

C310352912

C310352913

C310352914

C310352915

C310352916

C310352917

C310352918

Number of failed relocation preparation for outgoing CS inter-RAT handovers

C310352919

C310352920

C310352921



C310352922

C310352923

C310352924

C310352925

C310352926

C310352927

Number of attempted relocation preparation for outgoing PS inter -RAT handovers

C310352928

C310352929

C310352930

C310352931

C310352932

C310352933

C310352934

Number of failed relocation preparation for outgoing PS inter-RAT handovers

C310352935

C310352936

C310352937

C310352938

C310352939

C310352940

C310352941

C310352942

C310352943 Statistics of outgoing CS and PS inter-RAT handovers(DTM)

C310352944

C310352945 Number of attempted outgoing CS inter-RAT handovers

C310352946

Number of failed outgoing CS inter-RAT handovers

C310352947

C310352948

C310352949

C310352950

C310352951

C310352952 Number of attempted outgoing PS inter-RAT handovers

C310352953

Number of failed outgoing PS inter-RAT handovers

Number of failed outgoing PS inter-RAT handovers

C310352954

C310352955

C310352956

C310352957

C310352958

C310352959 Number of attempted outgoing PS inter-RAT handovers(Cell Change Order)

C310352960 Number of failed outgoing PS inter-RAT handovers(Cell Change Order) C310352961



C310352962

C310352963

C310352964

C310352965 Statistics of relocation preparation for outgoing inter-RAT handovers, by channel type C310352966

C310352967

Statistics of relocation preparation for outgoing inter-RAT handovers, by channel type

C310352968

C310352969

C310352970

C310352971

C310352972

C310352973

C310352974

C310352975

C310352976

C310352977

C310352978

C310352979

C310352980

C310352981

C310352982

C310352983

C310352984

C310352985 Number of attempted outgoing inter-RAT handoverrs, by channel type

C310352986


C310352987

C310352988

C310352989

C310352990

C310352991

C310352992

C310352993

C310352994

C310352995 Number of attempted outgoing inter-RAT handovers, by channel type

C310352996


C310352997

C310352998

C310352999

C310353000

C310353001



C310353002

C310353003

C310353004


C310353006 Statistics of relocation preparation for outgoing inter-RAT handovers, by channel type

C310353007


C310353008

C310353009

C310353010

C310353011

C310353012

C310353013

C310353014


C310353016


C310353017

C310353018

C310353019

C310353020

C310353021

C310353022

C310353023

C310353024


C310353026


C310353027

C310353028

C310353029

C310353030

C310353031

C310353032

C310353033

C310353034


C310353036



C310353037

C310353038

C310353039

C310353040

C310353041



C310353042

C310353043

C310353044


C310353046 Statistics of relocation preparation for outgoing inter-RAT handovers, by channel type

C310353047


C310353048

C310353049

C310353050

C310353051

C310353052

C310353053

C310353054

C310353055

Statistics of outgoing inter-RAT handovers, by channel type

C310353056

C310353057

C310353058

C310353059

C310353060

C310353061

C310353062

C310353063

C310353064

C310353065

C310353066

C310353067

C310353068

C310353069

C310353070

C310353071

C310353072

C310353073

C310353074

C310353075

C310353076

C310353077

C310353078

C310353079

C310353080

C310353081



C310353082

C310353083

C310353084

C310353085

C310353086

C310353087

C310353088

C310353089

C310353090

C310353091

C310353092

C310353093

C310353094

C310353095

C310353096

C310353097

C310353098

C310353099

C310353100

C310353101

C310353102

C310353103

C310353104

C310353105

C310353106

C310353107

C310353108

C310353109

C310353110

C310353111

C310353112

C310353113

C310353114

C310353115

Statistics of outgoing inter-RAT handovers, by channel type C310353116

C310353117

C310353118

Number of speech outgoing inter-RAT handovers, by measurement quality

C310353119

C310353120

C310353121



C310353122

C310353123

C310353124

C310353125

C310353126

C310353127

C310353128

C310353129

C310353130

C310353131

C310353132

C310353133

C310353134

Statistics of outgoing R99 data inter-RAT handovers(CCO), by measurement quality

C310353135

C310353136

C310353137

C310353138

C310353139

C310353140

C310353141

C310353142

Number of DCH NRT outgoing inter-RAT handovers, by measurement quality

C310353143

C310353144

C310353145

C310353146

C310353147

C310353148

C310353149

C310353150

Number of DCH video outgoing inter-RAT handover,by measurement Quality

C310353151

C310353152

C310353153

C310353154

C310353155

C310353156

C310353157

C310353158

Number of DCH other RT outgoing inter-RAT handover,by measurement Quality

C310353159

C310353160

C310353161



C310353162

C310353163

C310353164

C310353165

C310353166

Number of HS-DSCH outgoing inter-RAT handover,by measurement Quality

C310353167

C310353168

C310353169

C310353170

C310353171

C310353172

C310353173

C310353174

Number of E-DCH outgoing inter-RAT handover,by measurement Quality

C310353175

C310353176

C310353177

C310353178

C310353179

C310353180

C310353181

C310353182

Number of VoIP outgoing inter-RAT handover,by measurement Quality

C310353183

C310353184

C310353185

C310353186

C310353187

C310353188

C310353189

C310353190

C310353191

C310353192

C310353193

C310353194

C310353195

C310353196

C310353197

C310353198

Statistics of outgoing inter-RAT handover,by start cause C310353199

C310353200

C310353201



C310353202

C310353203

C310353204

C310353205

C310353206

C310353207

C310353208

C310353209

C310353210

C310353211

C310353212

C310353213

C310353214

C310353215

C310353216

C310353217

C310353218

C310353219

C310353220

C310353221

C310353222

C310353223

C310353224

C310353225

C310353226

C310353227

C310353228

C310353229

13.1.5 HSPA Serving Cell Change Statistics


C310363230

Statistics of HS-DSCH serving cell change

C310363231

C310363232

C310363233

C310363234

C310363235

C310363236

C310363237

C310363238



C310363239

C310363240

C310363241

C310363242

C310363243

C310363244

C310363245

C310363246

C310363247

C310363248

C310363249

C310363250

C310363251

C310363252

C310363253

C310363254

C310363255

C310363256

C310363257

C310363258

C310363259

C310363260

C310363261

C310363262

C310363263

Statistics of E-DCH serving cell change

C310363264

C310363265

C310363266

C310363267

C310363268

C310363269

C310363270

C310363271

C310363272

C310363273

C310363274

C310363275

C310363276

C310363277

C310363278



C310363279

C310363280

C310363281

C310363282

C310363283

Statistics of E-DCH serving cell change

C310363284

C310363285

C310363286

C310363287

C310363288

C310363289

C310363290

C310363291

C310363292

C310363293

C310363294

C310363295

13.1.6 Inter-cell Hard Handover Statistics


C310890001

Statistics of outgoing int ra-NodeB hard handover

C310890002

C310890003

C310890004

C310890005

C310890006

C310890007

C310890008

C310890009

C310890010

C310890011

C310890012

C310890013

Statistics of outgoing int ra-NodeB hard handover

C310890014

C310890015

C310890016

C310890017

C310890018

C310890019 Stattistics of outgoing inter-NodeB,intra-RNC hard handover

C310890020



C310890021

C310890022

C310890023

C310890024

C310890025

C310890026

C310890027

C310890028

C310890029

C310890030

C310890031

C310890032

C310890033

C310890034

C310890035

C310890036

C310890037

Stattistics of outgoing inter-RNC hard handover via Iur

C310890038

C310890039

C310890040

C310890041

C310890042

C310890043

C310890044

C310890045

C310890046

C310890047

C310890048

C310890049

C310890050

C310890051

C310890052

C310890053

C310890054

C310890055

Stattistics of outgoing inter-RNC hard handover switching in the CN

C310890056

C310890057

C310890058

C310890059

C310890060



C310890061

C310890062

C310890063

C310890064

C310890065

C310890066

C310890067

C310890068

C310890069

C310890070

C310890071

C310890072

C310890073

Stattistics of outgoing hard handover,by channel and traffic

C310890074

C310890075

C310890076

C310890077

C310890078

C310890079

C310890080

C310890081

C310890082

C310890083

C310890084

C310890085

C310890086

C310890087

C310890088

C310890089

Statistics of outgoing hard handover,by domain

C310890090

C310890091

C310890092

C310890093

C310890094

C310890095

C310890096

C310890097

C310890098

C310890099

C310890100



C310890101

C310890102

C310890103

C310890104

C310890105

C310890106

C310890107

C310890108

C310890109

C310890110

C310890111

C310890112

C310890113

C310890114

C310890115

C310890116

C310890117

C310890118

C310890119

C310890120

C310890121

C310890122

C310890123

C310890124

C310890125

C310890126

C310890127

C310890128

C310890129

C310890130

C310890131

C310890132

C310890133

Statistics of outgoing hard handover,by domain C310890134

C310890135

C310890136

13.1.7 Inter-cell Soft Handover Statistics


C310880137 Stattistics of radio link addition for soft handover between cells



C310880138

C310880139

Number of failed radio link addition for soft handover between cells,by cause

C310880140

C310880141

C310880142

C310880143

C310880144

C310880145

C310880146

C310880147 Stattistics of radio link deletion for soft handover between cells

C310880148

C310880149

Number of failed radio link deletion for soft handover between cells,by cause

C310880150

C310880151

C310880152

C310880153

C310880154

C310880155

C310880156

C310880157 Stattistics of soft handover between cells

C310880158

C310880159

Number of failed soft handover between cells,by cause

C310880160

C310880161

C310880162

C310880163

C310880164

C310880165

C310880166

C310880167 Statistics of soft handover between cells for monitor set

C310880168 Statistics of soft handover,add Radio link,by channel and traffic

C310880169

C310880170

Statistics of soft handover,add Radio link,by channel and traffic

C310880171

C310880172

C310880173

C310880174

C310880175

C310880176

C310880177



C310880178

C310880179

C310880180

C310880181

C310880182

C310880183

C310880184

Statistics of soft handover,delete Radio link,by channel and traffic

C310880185

C310880186

C310880187

C310880188

C310880189

C310880190

C310880191

C310880192

C310880193

C310880194

C310880195

C310880196

C310880197

C310880198

C310880199

13.1.8 Inter-cell Detected Set Statistics


C310910200 Statistics of detected set

13.1.9 Inter-RAT Inter-cell Handover Statistics


C301460862 Number of HS-DSCH to 2G handover attempt

C310900001 Stattistics of attempted relocation preparation for outgoing CS inter-RAT handovers C310900002

C310900003

Stattistics of attempted relocation preparation for outgoing CS inter-RAT handovers

C310900004

C310900005

C310900006

C310900007

C310900008 Stattistics of failed relocation preparation for outgoing CS inter -RAT handovers C310900009



C310900010

C310900011

C310900012

C310900013

C310900014

C310900015

C310900016

C310900017 Stattistics of attempted outgoing CS inter-RAT handovers

C310900018

Stattistics of failed outgoing CS inter-RAT handovers

C310900019

C310900020

C310900021

C310900022

C310900023

C310900024

Stattistics of attempted relocation preparation for outgoing PS inter-RAT handovers(Handover from UTRAN)

C310900025

C310900026

C310900027

C310900028

C310900029

C310900030

C310900031

Stattistics of failed relocation preparation for outgoing PS inter-RAT handovers(Handover From UTRAN)

C310900032

C310900033

C310900034

C310900035

C310900036

C310900037

C310900038

C310900039

C310900040 Stattistics of attempted outgoing PS inter-RAT handovers(Handover From UTRAN)

C310900041 Stattistics of failed outgoing PS inter-RAT handovers(Handover From UTRAN) C310900042

C310900043

Stattistics of failed outgoing PS inter-RAT handovers(Handover From UTRAN)

C310900044

C310900045

C310900046

C310900047 Stattistics of attempted outgoing PS inter-RAT handovers

C310900048 Stattistics of failed outgoing PS inter-RAT handovers

C310900049



C310900050

C310900051

C310900052

C310900053

Stattistics of outgoing inter-RAT handovers,by Channel and traffic

C310900054

C310900055

C310900056

C310900057

C310900058

C310900059

C310900060

C310900061

C310900062

C310900063

C310900064

C310900065

C310900066

C310900067

C310900068

C310900069

C310900070

C310900071

C310900072

C310900073

C310900074

C310900075

C310900076

C310900077

C310900078

C310900079

C310900080

C310900081

C310900082

13.2 Alarm List

This feature has no related alarm.



14 Glossary

B

BLER Block error ratio

C

CIO Cell individual offset

CPICH Common Pilot Channel

CS Circuit switched

CTCP Common transmitted carrier power

D

DTCP Dedicated transmitted code power

E

Ec/No Received energy per chip divided by the power density in the

band

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

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

102907285-11

Documents

confi guration item

macro di versity

macro di versity

arget area code

mobile country code

traffic cat egory

maximum bit rate

maximum bit rate