zte umts handover control feature description v3.1.pdf

Handover Control WCDMA RAN Feature Description

Handover Control Feature Description

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

Handover Control Feature Description Version Date Author Approved By Remarks

V2.5 2009-1-20 Sha Xiubin / ZhangBo Liu Min

V3.0 2009-2-27 Sha Xiubin / ZhangBo Liu Min

V3.1 2009-6-2 ZhangBo Liu Min

© 2008 ZTE Corporation. All rights reserved.

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


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

TABLE OF CONTENTS

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

2 Overview ................................................................................................................ 2 2.1 Function Introduction............................................................................................... 2 2.1.1 Soft Handover and Softer Handover ....................................................................... 2 2.1.2 Intra-Frequency Hard Handover .............................................................................. 2 2.1.3 Inter-Frequency Hard Handover .............................................................................. 2 2.1.4 Inter-RAT Mobility ................................................................................................... 2 2.1.5 Inter-RNC(with IUR) Handover ................................................................................ 2 2.1.6 Inter-RNC Handover Without lur Interface............................................................... 2 2.1.7 Compressed Mode .................................................................................................. 2 2.1.8 Adjacent Cell Priority............................................................................................... 2 2.1.9 Change of HS-DSCH Serving Cell .......................................................................... 2 2.1.10 Change of Serving Cell in E-DCH Active Set .......................................................... 2 2.1.11 Handover Based on Dedicated Downlink Transmit Power ....................................... 2 2.1.12 Handover Based on Dedicated Uplink Transmit Power (UE).................................... 2 2.1.13 QoS-based Handover.............................................................................................. 2 2.1.14 IMSI-based Handover ............................................................................................. 2 2.1.15 Associated Channel Soft/Softer Handover of HSDPA.............................................. 2 2.1.16 Associated Channel Soft/Softer Handover of HSUPA.............................................. 2 2.1.17 Different Active Sets of E-DCH and DCH................................................................ 2 2.1.18 Handover Strategy Based on Service Type............................................................. 2 2.1.19 SRNS Relocation .................................................................................................... 2

3 Compressed Mode Strategy.................................................................................. 2 3.1 Introduction to Compressed Mode........................................................................... 2 3.2 Compressed Mode Strategy .................................................................................... 2

4 Intra-Frequency Handover Strategy ..................................................................... 2 4.1 Intra-Frequency Measurement ................................................................................ 2 4.1.1 Introduction to Intra-Frequency Measurement ......................................................... 2 4.1.2 Measurement Control Method Related to Active Set and Monitored set .................. 2 4.1.3 Handling of Over 32 Adjacent Cells......................................................................... 2 4.2 Handling Mechanism for Period-based Report of Intra-Frequency Handover

Measurement .......................................................................................................... 2 4.3 Intra-Frequency Handover Decision ........................................................................ 2 4.3.1 Event 1A-Triggered Handover................................................................................. 2 4.3.2 Event 1B-Triggered Handover................................................................................. 2 4.3.3 Event 1C-Triggered Handover................................................................................. 2 4.3.4 Event 1D-Triggered Handover................................................................................. 2 4.3.5 Time-To-Trigger Mechanism Used to Control Event Report .................................... 2 4.3.6 Handling of Intra-Frequency Events ........................................................................ 2 4.3.7 Detected set Handover............................................................................................ 2 4.3.8 Detected Set Tracing .............................................................................................. 2 4.3.9 Processing of the Rx-Tx time difference of a UE in macro diversity ........................ 2 4.4 Intra-Frequency Handover Procedure...................................................................... 2 4.4.1 Intra-RNC Soft Handover (Add a Radio Link) .......................................................... 2 4.4.2 Intra-RNC Soft Handover (Delete a Radio Link) ...................................................... 2 4.4.3 Intra-RNC Soft Handover (Swap a Radio Link)........................................................ 2 4.4.4 Intra-RNC Hard handover........................................................................................ 2 4.4.5 Inter-RNC Hard Handover Through lur Interface ..................................................... 2 4.4.6 Inter-RNC Hard Handover Without lur Interface ...................................................... 2


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

5 Inter-Frequency Handover Strategy ..................................................................... 2 5.1 Inter-Frequency Measurement ................................................................................ 2 5.1.1 Introduction to Inter-Frequency Measurement ......................................................... 2 5.1.2 Inter-Frequency Measurement Control Method........................................................ 2 5.1.3 Handling of Over 32 Adjacent Cells......................................................................... 2 5.2 Handling Mechanism for Period-based Report of Inter-Frequency Handover

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

6 SRNS Relocation ................................................................................................... 2 6.1 Relocation Triggered by Soft Handover................................................................... 2 6.2 Relocation Triggered by Hard Handover.................................................................. 2

7 Inter-RAT Handover Policy ................................................................................... 2 7.1 Inter-RAT Measurement.......................................................................................... 2 7.1.1 Overview of Inter-RAT Measurement ...................................................................... 2 7.1.2 Control Methods for Inter-RAT Measurement .......................................................... 2 7.1.3 Processing in the Case of More Than 32 Inter-RAT Neighboring Cells .................... 2 7.2 Inter-RAT Handover Based on Downlink Coverage ................................................. 2 7.3 Inter-RAT Handover Based on Uplink BLER............................................................ 2 7.4 Inter-RAT Handover Based on Uplink Transmit Power ............................................ 2 7.5 Inter-RAT Handover Based on Downlink Transmit Power........................................ 2 7.6 Handover Based on Load Control............................................................................ 2 7.7 with ShareCover (Overlap or Covers)with GsmShareCover (Overlap or Covers)with

GsmShareCover (Overlap or Covers)Coupling for Different Handover Causes ....... 2 7.8 Inter-RAT Handover Process................................................................................... 2 7.8.1 CS Service Handover from 3G System to 2G System............................................. 2 7.8.2 PS Service Reselection in 3G to 2G Handover ....................................................... 2

8 IMSI-based handover............................................................................................. 2 8.1 Querying Whether a SRNC Cell Is Authorized According to IMSI ............................ 2 8.2 Querying Whether a DRNC Cell Is Authorized According to IMSI............................ 2

9 HSDPA-related special strategy............................................................................ 2 9.1 Overview ................................................................................................................ 2 9.2 Intra-frequency Handover........................................................................................ 2 9.3 Inter-frequency Handover........................................................................................ 2 9.4 Inter-RAT Handover ................................................................................................ 2

10 HSUPA-related special strategy............................................................................ 2 10.1 Overview ................................................................................................................ 2 10.2 Intra-frequency Handover........................................................................................ 2 10.3 Inter-frequency Handover........................................................................................ 2 10.4 Inter-RAT Handover ................................................................................................ 2

11 MBMS-related special strategy ............................................................................. 2 11.1 Intra-frequency Handover........................................................................................ 2 11.2 Inter-frequency Handover........................................................................................ 2


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

12 parameters and configurations ............................................................................ 2 12.1 Intra-Frequency Handover Parameters.................................................................... 2 12.1.1 Parameter List......................................................................................................... 2 12.1.2 Parameter Configuration ......................................................................................... 2 12.2 Inter-Frequency Handover Parameters.................................................................... 2 12.2.1 Parameter List......................................................................................................... 2 12.2.2 Parameter Configuration ......................................................................................... 2 12.3 SRNC Relocation Parameters................................................................................. 2 12.3.1 Parameter List......................................................................................................... 2 12.3.2 Parameter Configuration ......................................................................................... 2 12.4 Inter-RAT Handover Parameters............................................................................. 2 12.4.1 Parameter List......................................................................................................... 2 12.4.2 Parameter Configuration ......................................................................................... 2 12.5 IMSI-based Handover Parameters .......................................................................... 2 12.5.1 Parameter List......................................................................................................... 2 12.5.2 Parameter Configuration ......................................................................................... 2 12.6 HSDPA Handover Parameters ................................................................................ 2 12.6.1 Parameter List......................................................................................................... 2 12.6.2 Parameter Configuration ......................................................................................... 2 12.7 HSUPA Handover Parameters ................................................................................ 2 12.7.1 Parameter List......................................................................................................... 2 12.7.2 Parameter Configuration ......................................................................................... 2 12.8 MBMS Handover Parameters.................................................................................. 2 12.8.1 Parameter List......................................................................................................... 2 12.8.2 Parameter Configuration ......................................................................................... 2

13 Counter And Alarm................................................................................................ 2 13.1 Counter List............................................................................................................. 2 13.1.1 RNC Soft Handover Statistics ................................................................................. 2 13.1.2 RNC Hard Handover Statistics ................................................................................ 2 13.1.3 Relocation With UE Not Involed.............................................................................. 2 13.1.4 RNC Inter-RAT Handover Statistics ........................................................................ 2 13.1.5 Cell Soft Handover Statistics................................................................................... 2 13.1.6 Cell Hard Handover Statistics.................................................................................. 2 13.1.7 Transfer between HSPA and DCH due to Cell Mobility............................................ 2 13.1.8 Cell HSPA Handover to 2G Statistics...................................................................... 2 13.1.9 Cell Inter-RAT Handover Statistics.......................................................................... 2 13.1.10 Inter-cell Hard Handover Statistics .......................................................................... 2 13.1.11 Inter-cell Soft Handover Statistics ........................................................................... 2 13.1.12 Inter-RAT Cell Handover Statistics.......................................................................... 2 13.2 Alarm List................................................................................................................ 2

14 Glossary................................................................................................................. 2


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

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

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

IMSI .......................................................................................................................... 2

Table 1 Correspondence between handover and compressed modes .................................... 2 Table 2 Parameters of compressed mode.............................................................................. 2 Table 3 Table of Principle ...................................................................................................... 2 Table 4 Default Value of the UE Intra-frequency Measurement Configuration Parameters

Related to Traffic Category ....................................................................................... 2 Table 5 Service Type Related UE Inter-frequency Measurement Parameter

ConfigurationDefault Value ....................................................................................... 2 Table 6 Service Type Related UE Inter-RAT Measurement Parameter ConfigurationDefault

Value ........................................................................................................................ 2


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

1 Functional Attribute System version: [RNC V3.07.310, OMMR V3.17.310, Node B V4.00.200, OMMB V4.00.200]

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

• Different Active Sets of E-DCH and DCH

• Handover Strategy Based on Service

• SRNS Relocation

2.1.1 Soft Handover and Softer Handover

In a soft handover, a UE maintains several radio links with different NodeBs, while in a softer handover, a UE concurrently maintains radio link with several cells in a NodeB, and these several cells are also known as macro diversity.

The soft/softer handover can only occur in intra-frequency cells. Compared with the hard handover, the soft/softer handover features are as follows:

• The soft and softer handovers are seamless handovers and no service will be interrupted during handover.

• Macro diversity gain: When a UE maintains radio links with several cells, the receiver may enhance the accuracy of data receiving and link receiving quality and lower the transmit power of all links by combining the signal receiving results of several links.

• The best cell where UE is registered may establish a radio connection with the UE in time so as to lower the transmit power of UE.

In view of the above features, the soft and softer handovers will be taken in intra-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 cellbefore setting up a link (synchronization) with the new cell (that is, new and original links do not co-exist in UE). The intra-frequency hard handover is only adopted when soft/softer handover is unavailable. The scenarios where soft/softer handover is unavailable (intra-frequency hard handover must be adopted) in the case of intra-frequency handover include:

• UE uses transmit diversity in active set cell in case of intra-frequency handover, but the target cell does not support transmit diversity.



• Intra-frequency measurement report excludes the OFF and TM of the target cell.

• lur interface between RNCs is unavailable in the case of intra-frequency handover.

• UE uses multi-user detection in the active set cell, but the target cell does not support multi-user detection.

• Types of target and source cells are 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 transmission delay TimeDelay reported during intra-frequency handover for the NodeB where the neighboring cell of the current RNC resides is inconsistent with the transmission 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 (For a cell of the DRNC whose transmission delay is not configured, the transmission delay of this cell shall be the transmission delay of a cell in macro diversity).

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 non-double-receiver terminals in WCDMA, the compressed mode must be initiated for Inter-RAT measurement. Initiation of compressed mode has some impact on the performance of both system and UE.Therefore, compressed mode must be initiated only when necessary (for example, when the quality of current serving carrier frequency worsens).

2.1.5 Inter-RNC(with IUR) Handover

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

2.1.6 Inter-RNC Handover Without lur Interface

This feature provides inter-RNC handover management in the absence of lur interface. The inter-RNC handover without lur interface is implemented through inter-CN relocation.

If neighboring RNC does not support HSDPA relocation or vendor expect to adopt DSCR for inter-RNC handover, it introducts the 4th bit of parameter RncFeatSwitch to control whether DSCR will be used in inter-RNC handover . Bit4＝0 means DSCR is not used for inter-RNC handover of HSPA service, Bit4=1 means DSCR is used for inter-RNC handover of HSPA service on condition that current service use HSDSCH/DCH or HSDSCH/EDCH channel and is not include AMR.



2.1.7 Compressed Mode

For non-double-receiver terminals in WCDMA, the compressed mode must be initiated for Inter-RAT/inter-frequency measurement. The use of compressed mode means some timeslots are specially used for inter-frequency/Inter-RAT measurement instead of data transmission during transmitting and receiving.

2.1.8 Adjacent Cell Priority

The system offers two types of cell priority policies as follows:

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

Secondly, adjacent cells are set with different priorities (MeasPrio (utranRelation/ gsmRelation)) in RNC to facilitate RNC to adjust adjacent cell list when the number of adjacent cells in active set is over 32. The priority of each cell in the adjacent cell list is determined based on the network planning and optimization progress. The priority helps RNC select better monitored set for UE to facilitate the improvement of measurement and handover performance of UE.

2.1.9 Change of HS-DSCH Serving Cell

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

2.1.10 Change of Serving Cell in E-DCH Active Set

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

2.1.11 Handover Based on Dedicated Downlink Transmit Power

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



2.1.12 Handover Based on Dedicated Uplink Transmit Power (UE)

This feature enables handover based on the dedicated uplink transmit power, and applies to the following scenario: The signal of pilot frequency is acceptable, but the dedicated uplink transmit power has become very high, requiring UE handover to an inter-frequency or Inter-RAT adjacent cell to avoid large interference on other users.

2.1.13 QoS-based Handover

This feature enables the handover based on the uplink BLER and applies to the following scenario: The signal of pilot frequency is acceptable, but the uplink of UE is very unacceptable due to uplink interference or other reasons. In the event of failure of outer loop power control, the UE needs to be handed off to an inter-frequency or Inter-RAT adjacent cell as quick as possible to avoid call drop.

2.1.14 IMSI-based Handover

Configure the scope of authorized cells based on the IMSI information on the network side. The IMSI information is resolved through the CommonID on lu interface during service setup or handover, and UE is not allowed to access or handover to unauthorized cells.

2.1.15 Associated Channel Soft/Softer Handover of HSDPA

The HSDPA service supports soft/softer handover of associated DPDCH/DPCCH, with the policy identical with that of common soft/softer handover.

2.1.16 Associated Channel Soft/Softer Handover of HSUPA

The HSUPA service supports soft/softer handover of associated DPDCH/DPCCH, with the policy identical with that of common soft/softer handover.

2.1.17 Different Active Sets of E-DCH and DCH

The feature enables E-DCH and DCH to have different active sets. The maximum number of links of E-DCH active set is MaxNumOfEdchAct, and that of DCH active set is MaxNumOfAct.

2.1.18 Handover Strategy Based on Service Type

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

• Handover to GSM should be performed: RAB must be handed over to GSM immediately. If there is any GSM adjacent cell in the cell where the UE is located



and inter-frequency measurement is not activated upon service setup or handover success, the Inter-RAT measurement must be activated immediately.

• Handover to GSM should not be performed: RAB is handed over to GSM forcedly when the UMTS is unable to carry it. RNC triggers Inter-RAT blind handover or activates Inter-RAT measurement only when the quality of the UMTS is poor.

• Handover to GSM shall not be performed: Service cannot be handed over to GSM. For such a type of service, RNC neither activates the Inter-RAT measurement, nor triggers the handover to GSM.

2.1.19 SRNS Relocation

If inter-RNC handover occurs and radio link does not exist in SRNC, or hard handover occurs, the system determines the delay in performing SRNC relocation based on the timer configured in OMCR(set separately based on CS and PS services: RtReDelayTimer, and NrtReDelayTimer). The DRNC changes its role into SRNC upon relocation, and assigns new RNTI to the UE through the UTRAN MOBILITY INFORMATION of radio interface. Therefore, the SRNS relocation can be categorized into relocation involving no UE (soft handover triggered) and relocation involving UE (hard handover triggered) based on UE relevance:

• The relocation involving no UE equals to the relocation triggered by soft handover.

− The interactive message (RELOCATION COMMIT) interacts through lur interface between SRNC and DRNC. SRNC sends SN and GTP of PDCP to DRNC through interactive message.

− There is no message interaction between SRNC and UE.

− Two types of messages (UTRAN Mobility Information/UTRAN Mobility Information Confirm) interact between DRNC and UE. The DRNC sends the PDCP SN received by the UE downlink.

• The relocation involving UE equals to the relocation triggered by hard handover.

− The messages related to hard handover interact between SRNC and UE.

− The messages related to hard handover interact between DRNC and UE.

− There is no message interaction between SRNC and DRNC through lur interface.

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



3 Compressed Mode Strategy

3.1 Introduction to Compressed Mode For non-double-receiver terminals in WCDMA, the compressed mode must be initiated 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 1.

#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

Figure 1 Transmission Gap (TG) position

In the protocol, the Transmission Gap Length (TGL) can be set to 3, 4, 5, 7, 10 and 14 timeslots. The TG may start from any timeslot in a frame. When the TG spans two consecutive frames, each frame at least has 8 non-compressed timeslots.



Figure 2 shows the parameters involved in compressed mode. The Transmission Gap Pattern Sequence (TGPS) consists of consecutive TG patterns (TG pattern 1). One or two TGs are defined in TG pattern. The start timeslot No. of the first TG is determined by parameter TGSN. The number of timeslots between starting timeslots of two TGs in the TG pattern is determined by the parameter TGD. The first TGL is determined by parameter TGL1, and the second by parameter TGL2. If parameter TGD is not defined, it means there is only one TG in TG pattern. Length of a TG pattern is determined by parameter TGPL1.

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

Figure 2 Parameters of compressed mode

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 realtime rate of services. For RT services, only the first strategy can be adopted to ensure delay and transmission rate; for NRT services, both the first and second strategies can be adopted because of their low requirements for delay and rate. For NRT services on ZTE network, the first strategy is adopted for uplink and the second for downlink.

The above rules only apply to DCH/DCH. For HS-DSCH or E-DCH, only the higher layer schedule is supported, as stipulated in the protocol.



The compressed mode of all services on ZTE network adopts identical parameters as listed below:

Table 2 Parameters of compressed mode

GSM adjacent cell measurement

FDD adjacent cell measurement

TGSN 4 (Slots) 3 (Slots) TGL1 7 (Slots) 7 (Slots) 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 Description) before initiating the compressed mode. Figure 3 shows the procedure in which E-DCH falls back to DCH before the initiation of compressed mode.



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

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

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 intra-frequency measurement, the UE needs to implement layer 3 filter for the measurement results to avoid measurement fluctuation and then make event decision and report by using filtered values. The layer 3 filter formula is as follows:

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-frequency measurement refers to measurement performed for intra-frequency cells. It can adopt either period-based report or event-based report strategy, which is determined through the parameter SoftHoMth.

• The period-based report means the UE periodically reports the quality measurement result of intra-frequency cell PCPICH to the RNC and the RNC then judges whether intra-frequency events are met based on the measurement result. If so, it outputs intra-frequency events (including such information as event ID, and target cell).

• The event-based report means the UE judges whether intra-frequency events are met based on the quality measurement result of cell PCPICH.If so, it reports intra-frequency events (including such information as event ID, and target cell) to the RNC.

A series of intra-frequency measurement events are defined in 3GPP as the judgment and trigger criteria for intra-frequency handover.



Event 1A: A Primary CPICH enters the Reporting Range. It can be used for adding cell to the active set.

Event 1B: A Primary CPICH leaves the Reporting Range. It can be used for deleting cell from the active set.

Event 1C: A Non-active Primary CPICH becomes better than an active Primary CPICH. It can be used for replacing the cell with bad quality in the active set.

Event 1D: The best cell changes. It can be used for soft/softer handover, intra-frequency hard handover and inter-frequency load balance.

4.1.2 Measurement Control Method Related to Active Set and Monitored set

4.1.2.1 Measurement Setup

Configure intra-frequency measurement parameters for UE and initiate intra-frequency measurement through measurement control setup message in the following cases:

• RRC connection is set up and enters CELL_DCH state.

• CELL_FACH -> CELL_DCH.

• Relocation to current RNC from other systems or RNCs.

Set up intra-frequency measurement again after intra-system hard handover (including intra- or inter-frequency hard handover).

4.1.2.2 Measurement Modification

If the intra-frequency measurement is enabled, the intra-frequency measurement modification is triggered in the following cases:

• The change of adjacent cell list may trigger the modification of intra-frequency measurement so as to modify adjacent cell parameters after soft handover.

• After the best cell changes (Event 1D), the change of intra-frequency measurement parameters will trigger the modification of intra-frequency measurement to update handover parameters.

• 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 intra-frequency measurement report (for example, the measurement report belongs to non-existent measurement task), or making decision about the relocation triggered by soft handover, the RNC will voluntarily release corresponding intra-frequency measurement.

4.1.2.4 Parameter Configuration Strategies

• Intra-frequency event parameter configuration:

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

• Handover parameter 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)

Service bearer type (TrfCategory(CIntra))

− Single RT RAB Including Voice on DL DCH/UL DCH

− Single RT RAB Excluding Voice on DL DCH/UL DCH

− Single NRT on DL DCH/UL DCH

− Single RAB on DL HS-DSCH/UL DCH



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

− All Multi-RAB on DL DCH/UL DCH

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

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

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

To facilitate parameter modification and optimization, the intra-frequency parameters are index-organized, with the index quotations listed as follows:

Figure 4 Intra-frequency handover index quotations

Before obtaining intra-frequency handover parameters, first find the “Service Type-Related Intra-frequency Measurement Parameter Index (TrfCatIntraMIdx)”, “UTRAN Intra-frequency Radio Quality Measurement Quantity (IntraMeasQuan)”, and “Soft Handover Algorithm Selection (SoftHoMth)” from Utran Cell (utranCell) configuration items; then find the “Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)” from the UE Intra-frequence Measurement Relative to Traffic Category Configuration Information (CIntra) configuration items based on TrfCatIntraMIdx, "Traffic Category (TrfCategory)", “Measurement Purpose (PrdMeasEcNo, EvtMeasEcNo, PrdMeasEcNo, and PrdMeasRSCP)”; finally, find corresponding handover measurement parameters from UE Intra-frequency Measurement Configuration (Intra) configuration items based on the “Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)”.

Note:

Each IntraMeasCfgNo corresponds to one measurement purpose, indicated with the parameter IntraMeasCfgNote.

• The correspondence between other parameters that need to be filled in 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 intra-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(Intra) are automatically filled by the system based on IntraMeasCfgNote.

For cells of neighbor RNC， if the value of Primary CPICH Power Configuration Tag(PcpichPwrPre(externalUtranCell))is TURE,then the cell info of intra-freq measurement should include the Primary CPICH Power for this cell. Otherwise the cell info of intra-freq measurement shall not include the Primary CPICH Power for this cell.

4.1.3 Handling of Over 32 Adjacent Cells

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

4.1.3.1 Cell Priority Configuration

The OMCR configuration parameter MeasPrio(utranRelation) is used to define the priority of adjacent cells and includes three values (0: High priority; 1: Medium priority; 2: Low priority). The specific value of MeasPrio(utranRelation) must be set by the network planning engineer based on existing network situation (for example, adjacent cell quality and geographical location of adjacent cell). Figure 5 shows the cell priority configuration based on the geographical location of adjacent cells. Take the configuration of cells adjacent to the innermost gray cell as an example: there are three layers of adjacent cells surrounding the gray cell, and they are differentiated from one another with yellow (0: Top priority), blue (1: Medium priority) and red (2: Low priority).



Figure 5 Cell priority configuration

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 intra-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 periodically reported by UE. If several decision conditions are concurrently met, the RNC will handle events in the sequence of 1D, 1A, 1C and 1B.

Long interval set in the period-based report mode may result in call drop due to handover delay. Therefore, it is recommended to set the interval to a small value. But setting a short interval will increase the signaling load of radio interface and easily lead to signaling congestion, so the event-based report is generally preferred.

4.3 Intra-Frequency Handover Decision

4.3.1 Event 1A-Triggered Handover

Event 1A means the quality of certain cell outside the active set ameliorates. Upon receiving Event 1A, the RNC adds corresponding target cell into the active set to enhance the gain of macro diversity. When the cell meets the conditions in the following formula, the UE reports Event 1A to the RNC.

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

N

1iiNewNew

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

Mi: Refers to the mean measurement value of other cells except the best cell in active set.

NA: Refers to the number of other cells except the best cell in active set.

MBest: Refers to the measurement of the best cell in the active set.



W: Refers to the weight proportion (W[MAX_INTRA_MEAS_EVENT]) of the best cell to the rest cells in the active set in evaluation standards.

As can be calculated from the above formula, you can 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

1iiOldOld

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

Mi: Refers to the mean measurement value of other cells except the best cell in active set.

NA: Refers to the number of other cells except the best cell in active set.

MBest: Refers to the measurement of the best cell in the active set.

W: Refers to the weight proportion (W[MAX_INTRA_MEAS_EVENT]) of the best cell to the rest cells in the active set in evaluation standards.

As can be calculated from the above formula, you can decrease the probability of triggering Event 1B by either increasing R1b (Event 1B meets the reporting range



conditions) or decreasing H1b (Decision hysteresis range). Otherwise, you can increase the probability of triggering Event 1B.

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.

MInAS: Refers to the cell with poorest quality in the active set.

CIONew: Refers to offset of the to-be-evaluated cell outside the active set in relation to other cells (CellIndivOffset (utranRelation)).

CIOInAS: Refers to offset of cell with poorest quality in active set in relation to other cells (CellIndivOffset (utranCell)).

As can be calculated from the above formula, you can decrease the probability of 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 (EvtRptAmount[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)).

As can be calculated from the above formula, you can decrease the probability of triggering Event 1D by increasing H1d (decision hysteresis range); otherwise, you can increase the probability of triggering Event 1D.

4.3.5 Time-To-Trigger Mechanism Used to Control Event Report

If a to-be-evaluated cell meets the reporting range or threshold of certain event, the condition must be met within a period of time (TrigTime[MAX_INTRA_MEAS_EVENT] (Intra)) before the reporting of this event to avoid intra-frequency event misreport due to the fluctuation of radio quality. Take Event 1A as an example, suppose a cell meets the reporting range, the UE only reports Event 1A only if the cell quality meets this reporting range condition within TrigTime[MAX_INTRA_MEAS_EVENT] (Intra), as shown in Figure 6.

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

Figure 6 Time-To-Trigger mechanism



4.3.6 Handling of Intra-Frequency Events

Handling of Event 1A

• Add links to the active set if the number of links in the DCH active set is less than MaxNumOfAct. Do not handle Event 1A if the total number of links in the active set reaches the maximum.

• If a link to be added to the active set is rejected in Event 1A, the handover punishment timer (5s) is initiated so that the Event 1A reported by this rejected cell will not be handled until the timer times up.

• If the cell reporting Event 1A is the target cell traced by the detected set, no link will be added to the active set. For details, see Detected set Tracing.

• If the measurement report contains several target cells, the cell with best quality (Ec/N0) will be selected as the target cell to be added in the active set.

Handling of Event 1B

• Delete the link of related cell based on Event 1B reported by UE.

• If the measurement report contains several target cells, the cell with worst quality (Ec/N0) will be selected as the target cell to be deleted from the active set.

Handling of Event 1C

• Replace the cell if the radio links in active set are equal MaxNumOfAct .

• If a link to be added to the active set is rejected in Event 1C, the handover punishment timer is initiated so that the Event 1C reported by this rejected cell will not be handled until the timer times up.

Handling of Event 1D

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



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 7 Intra-frequency handover index quotations

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 Utran Cell (utranCell) configuration items; then find the “Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)” from the UE Intra-frequency Measurement Relative to Traffic Category Configuration Information (CIntra) configuration items based on TrfCatIntraMIdx, "Traffic Category (TrfCategory)", “Measurement Purpose (EvtMeasDctEcNo, and EvtMeasDctRSCP)”; finally, find corresponding handover measurement parameters from UE Intra-frequency Measurement Configuration (Intra) configuration items based on the “Intra-Frequency Measurement Configuration No. (IntraMeasCfgNo)”.

Note: Each IntraMeasCfgNo corresponds to one measurement purpose, indicated with the parameter IntraMeasCfgNote.

4.3.8.1 Measurement Procedure of Detected Set Tracing

(1)The measurement of detected set tracing is controlled through the detected set tracing task in the performance measurement of OMCR. The detected set measurement is started after the detected set tracing task is created and initiated. When configuring the measurement control, set “Triggering condition 2” to “Detected set cells”, and “Reporting cell status” to “Report cells within detected set on used frequency”.

(2)The measurement parameters of detected set are indexed to the cell, and the parameters of the best cell will be chosen in macro diversity state. If the parameters of the best cell are different from those used by the UE, the measurement information needs to be modified through the measurement control message.

(3)After the detected set tracing task stops, disable detected set tracing and release related measurement task.

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, if the 6F/6G event parameters of the best cell are different from the parameters issued to the UE, the parameter configuration of the UE will be modified through 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.4 Intra-Frequency Handover Procedure

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

UE Node B Drift RNS Drift RNC

Serving RNC

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 6. Radio Link Restore

Indication

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



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

UE Node BDrift RN S

D riftRN C

ServingR NC

R RCR R C2. D CC H : Ac tive Set Update C omplete

D ecision to deleteold RL

R NSAP R NSAP

3. R adio Link D eletionR equest

N B AP N B AP

4. R adio Link D eletionRequest

R NSAP R NSA P

6. R adio Link D eletionR esponse

NB AP NB AP

5. R adio Link Dele tionR esponse

S top R X and T X

R RCR R C1. DC CH : Active Set Update

[Radio L ink Dele tion]

ALC AP Iur B earer R elease7. ALCAP Iub B earer Release

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



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

9. U plink S ynchro nisation

RN SA P RN S AP

1. R ad io Link Setup Request

S tart TX description

R N SA P RN SA P

4. R adio L ink Setup Respo nse

NB A P N BA P

2. Radio Link Setup Request

NB A P N BA P 3 . Radio L ink S etup Response

Start RX description

D ecision to setup new RL and

re lease old RL

N BA P

12. Rad io Link D eletion Request

N BA P N BA P 13. Radio L ink Release Respo nse

S top RX and T X

14. ALCA P Iub Data T ranspo rt B earer Release

R RC R RC

11. D CC H : A ctive Set Up date Com plete

R RC R RC

10. D CC H : Active Set U p date Com m and

[Rad io Lin k Addition & Deletio n]

N BA P

U E N od e B D rift RN S

N o de B S erving RNS

D rift RN C

S erving RN C

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

D CH -FP D CH -F P

D CH -F P DC H -FP

8. Do wnlink S ynchronisation

RN SA P RN S AP

7. Radio L ink Res tore Indication

NB A P N B AP 6. Rad io Link Restore Indication

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



4.4.4 Intra-RNC Hard handover

Figure 11 Intra-RNC hard handover procedure



4.4.5 Inter-RNC Hard Handover Through lur Interface

RNSAP RNSAP

1. Radio Link Setup Reque st

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 Reconf iguration

RRC

6. ALCAP Iur Dat a Transport Bearer Setup

NBAP NBAP

2. Radi o 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 Set up

16. ALCAP Iub D ata Transpor t Bearer Release

RNSAP RNSAP

17. Radio Link Deletion Response

18. ALCAP Iur Dat a

Transport Bearer Release

RNSAP

5. RL Se tup Re sponse

RNSAP

RNSAP 13. Radio Link Dele tion Request

RNS AP

NBAP NBAP

8. Radio Link Failure Indication

RNSAP

RNSAP 9. Radio Link Failure Indication

NBAP NBAP

10. Radio Link Restore Indication

RNSAP

11. RL Restore Indication

RNSAP

Figure 12 Inter-RNC hard handover through lur interface

If the cells belong to different RNCs are adjacent and lur interface is available, the SRNC performs inter-RNC hard handoff. The SRNC relocation is triggered after hard handover.



4.4.6 Inter-RNC Hard Handover Without lur Interface

2 . R eloca tion R equired RA N A P R AN A P

R A N AP R AN A P

3. R elo cation Re quest

R A N AP R AN A P

9 . R eloca tio n R equ est A ckn ow led ge

R A N AP R AN A P 1. Relo catio n R eq uired

U E R N C S ou rce

R N C Targ et

M S C/S GS N

R A N AP RA N A P

4. R eloc atio n R eq uest

RA N A P R AN A P

10. R elo cation Re quest A ckno wledg e

R AN A P R A N AP 1 1. Re lo cation Co mm and

R A NA P 12. R elo cation Co m man d

RA N A P

R A N AP R AN A P

1 5. R elo catio n D e te ct

RR C 13 . D C C H : Ph ysica l Ch annel R eco nfig uratio n N ote 1

RR C

5 . A LC A P Iu D ata Tra nspo rt B earer S etup

N o de B So urce

N o de B Ta rget

N B AP NB A P 6. R ad io L in k Se tu p R eq uest

N B A P NB A P 7 . R ad io Link Setup R espo nse

8. A L CA P Iub D ata T ransp ort B eare r Se tup

R AN A P R A N AP

19. R elocation C om plete

R R C RR C 1 8. D CC H : P hysical C hann el Re con figura tion C om plete N o te 1

RA N A P R AN A P 16 . R eloca tio n D etect

RA N A P R AN A P 20 . R eloca tio n C om plete

R AN A P 21 . Iu R elease C om ma nd

RA N A P

N B AP N B A P 17. R adio Link F ailure Ind icatio n

R AN A P 22 . Iu Re le ase C om m and R A N AP

23. A LC AP Iu D ata T ransp ort B eare r Relea se

RA N A P 24 . Iu Re lea se C om plete

R A N AP

RA N A P 25. Iu R elease Co m plete

R A N AP

SG S N/M S C

N B A P N B A P 14 . R ad io Link Re sto re Ind icatio n

Figure 13 Inter-RNC hard handover without lur interface

If inter-frequency cells between RNCs are adjacent and lur interface is unavailable, the hard-handover-triggered SRNS relocation is performed. The procedure is as follows:

The SRNC sets up radio link at DRNC through the lu interface relocation, and then reconfig UE to the cell of DRNC through relocation. Upon receiving the reconfigureation response message from the UE, the DRNC informs the CN to complete relocation and changes into SRNC. The CN then releases the resources of UE at the original SRNC through lu interface release command.

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

1ijijjfrequencyfrequencyj LogM10)W(1MLog10WLogM10Q

jA

⋅⋅−+

⋅⋅=⋅= ∑

=

Where,

Qfrequency j: Refers to (Virtual) active set quality of carrier j, that is, the measurement result of carrier j (dB for Ec/No; dBm for RSCP).

Mfrequency j: Refers to the physical measurement value (ratio for Ec/No; mW for RSCP) of the (Virtual) active set of carrier j.

Mi j: Refers to the physical measurement value of cell i of carrier j.

NA j: Refers to the number of cells (excluding best cell) in the (Virtual) active set of carrier j.

MBest j: Refers to the measurement result of the best cell in the (Virtual) active set of carrier j.

Wj: Refers to the weight (WNoUsed[MAX_INTER_MEAS_EVENT] or Wused[MAX_INTER_MEAS_EVENT]) of the best cell in the (Virtual) active set of carrier j during carrier measurement.

5.1.1 Introduction to Inter-Frequency Measurement

The inter-frequency measurement contains radio quality measurement of both working carrier frequency and non-working carrier frequency. It can be performed based on either Ec/N0 or RSCP measurement quantity, which is based on the parameter NonIntraMeasQuan. The inter-frequency measurement can adopt either period-based report or event-based report strategy, which is based on the parameter InterHoMth. The period-based report means the UE periodically reports the quality measurement result of inter-frequency cell PCPICH to the RNC and the RNC then judges whether inter-frequency events are met based on the measurement result. If so, it outputs inter-frequency events (including such information as event ID, and target cell). The event-based report means the UE judges whether inter-frequency events are met based on the quality measurement result of non-working carrier frequency PCPICH. If so, it reports inter-frequency events (including such information as event ID, and target cell) to the RNC.

A series of inter-frequency measurement events are defined in 3GPP as the judgment and trigger criteria for inter-frequency handover.

The inter-frequency handover events are described as follows:

Event 2A: The best carrier frequency changes.

/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 (ThreshNoUsedFreq[MAX_INTER_MEAS_EVENT]) of good quality of non-working 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 (ThreshUsedFreq[MAX_INTER_MEAS_EVENT]) of poor quality of working carrier 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 (ThreshNoUsedFreq[MAX_INTER_MEAS_EVENT]) of good quality of non-working 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 (ThreshUsedFreq[MAX_INTER_MEAS_EVENT]) of poor quality of working carrier 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 transmit power does not exceed inter-frequency measurement initiation threshold (100%) or recovers below normal value (90%), and the downlink transmit power does not exceed 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 Description).

• For CS users, perform inter-frequency hard handover.

• For PS users, hard handover tends to fail due to admission failure in the event of heavy cell load because a majority of resources are occupied by PS services.So the following strategies are required:

− If current channel type is DCH and the channel assigned for target cell is also DCH after handover, first make a handover attempt according to current rate. If handover fails, then makes another handover attempt according to the GBR of current service or minimum rate grade of DRBC (for details, see ZTE UMTS DRBC Algorithm Feature Description), to improve the handover success rate.



− If current channel type is HS-DSCH/E-DCH or HS-DSCH/DCH, and DCH after handover, perform handover directly according to the GBR of current service or 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 Description); 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 ShareCover(Overlap or Covers) relation with current serving cell, and the value of “RAB assignment requestàservice handover” is “Handover to GSM should not be performed” (For values of “service handover”, see 2.1.7 Handover Strategy Based on Service Attribute), implement Inter-RAT blind handover.

• All non-working carrier frequencies report Event 2E, indicating that radio quality of all inter-frequency adjacent cells is poor and 3G system quality deteriorates. If the value of “RAB assignment requestàservice handover” is “Handover to GSM should not be performed” (For values of “service handover”, see 2.1.7 Handover Strategy Based on Service Attribute), current serving cell has Inter-RAT adjacent cells without GsmShareCover(Overlap or Covers) or Inter-RAT blind handover fails, issue the Inter-RAT measurement Event 3A/3C.

(4)Handling of Event 2F

• The compressed mode and inter-frequency measurement disabling can be triggered. For details, see Compressed Mode Enabling/Disabling and “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)

Measurement report mode

− InterHoMth (Event report or periodically report)

Service bearer type (TrfCategory (CInter))











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

To facilitate parameter modification and optimization, the inter-frequency parameters are index-organized, with the index quotations listed as follows:

Figure 14 Inter-frequency handover index quotations

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)”, and “Inter-frequency Handover Algorithm Selection (InterHoMth)” from Utran Cell (utranCell) configuration items; then find the “Inter-Frequency Measurement Configuration No. (InterMeasCfgNo)” from the UE Inter-frequency Measurement Relative to Traffic Category Configuration Information (CInter) configuration items based on TrfCatInterMIdx, "Traffic Category (TrfCategory)", “Measurement Purpose (PrdMeasEcNo, EvtMeasEcNo, PrdMeasEcNo, and EvtMeasRSCP)”; finally, find corresponding handover measurement parameters from UE Inter-frequency Measurement Configuration (Inter) configuration items based on the “Inter-Frequency Measurement Configuration No. (InterMeasCfgNo)”.

Note: Each InterMeasCfgNo corresponds to one measurement purpose, indicated with the parameter InterMeasCfgNote.

• The correspondence between other parameters that need to be filled in inter-frequency measurement control message and OMCR configuration is described as follows: Measurement report transmission mode (MeasRptTrMod) Whether to report UTRA Carrier RSSI (UTRACarrierRSSI) Whether to report carrier frequency quality evaluation value

(FreqQualEst)

Cell synchronization information report indication of inter-frequency measurement

(CellSynRptInd)

Cell identity report indication of inter-frequency measurement

(CIdRptInd)

Ec/No report indication of inter-frequency measurement cell

(EcN0RptInd)

CPICH RSCP report indication of inter-frequency measurement cell

(RscpRptInd)



Path loss report indication of inter-frequency measurement cell

(RscpRptInd)

Whether to read SFN indication of target cell (ReadSFNInd) Inter-Frequency measurement amount (MeasQuantity(Inter)) Inter-frequency measurement report mode (RptCrt(Inter))

Note: The parameters MeasQuantity(Inter) and RptCrt(Inter) are automatically filled by the system based on InterMeasCfgNote.

For cells of neighbor RNC， if the value of Primary CPICH Power Configuration Tag(PcpichPwrPre(externalUtranCell))is TURE， then the cell info of inter-freq measurement should include the Primary CPICH Power for this cell, otherwise the cell info of inter-freq measurement shall not include the Primary CPICH Power for this cell.

5.1.3 Handling of Over 32 Adjacent Cells

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

5.1.3.1 Cell priority configuration

The OMCR configuration parameter MeasPrio(utranRelation) is used to define the priority of adjacent cells and includes three values (0: High priority; 1: Medium priority; 2: Low priority). The specific value of MeasPrio(utranRelation) must be set by the network planning engineer based on existing network situation (for example, adjacent cell quality and geographical location of adjacent cell). Figure 15 shows the cell priority configuration based on the geographical location of adjacent cells. Take the configuration of cells adjacent to the innermost gray cell as an example: there are three layers of adjacent cells surrounding the gray cell, and they are differentiated from one another with yellow (0: Top priority), blue (1: Medium priority) and red (2: Low priority).



Source Cell

Priority 0

Priority 1

Priority 2

Figure 15 Cell priority configuration

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.

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 handling in “Handling of Inter-Frequency Events”.



5.5 Uplink Transmit Power Based Inter-Frequency Handover The activation of uplink transmit power based inter-frequency handover is controlled through the parameter UlPwrHoSwch.


When the value of UlPwrHoSwch is “ON”, the RNC sets up the internal measurement events 6A (Uplink power of UE exceeds the absolute threshold – 100% of maximum transmit power of UE) and 6B (Uplink power of UE is less than the absolute threshold – 90% of maximum transmit power of UE) of UE while service initially establishing. When the transmit power of UE meets the above threshold requirements, the UE will report the corresponding events. After receiving an Event 6A report or an Event 6B report, the RNC adopts the same handling strategy as that of 2D or 2F, respectively. For details, see the Events 2D and 2F handling strategies in “Handling of Inter-Frequency Events”.

5.6 Downlink Transmit Power Based Inter-Frequency Handover The activation of downlink transmit power based inter-frequency handover is controlled through the parameter DlPwrHoSwch.


NodeB periodically sends the dedicated measurement report of downlink transmit power to the RNC.

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



5.8 Moving Speed Based Handover In the Hierarchical Cell Structure (HCS), Macro cells are used to carry the fast-moving UEs and they have low HCS priority (HcsPrio). Micro cells are used to carry the 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 17).

(a) (b) Figure 16 Example of slow-moving UE judging conditions



Figure 17 Example of fast-moving UE judging condition

5.9 Coupling Handling of Different Handovers Inter-frequency handover can be triggered by the following:

• Load control

• Downlink coverage events

• Uplink transmit power

• Uplink BLER

• Downlink transmit power

• Moving speed of UE

The load control based handover aims to quickly reduce system loads and ensure system stability, and it has the top priority. The handovers based on downlink coverage 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 SRNS Relocation SRNS relocation is mainly triggered by soft handover, hard handover,.The SRNS relocation procedure involves several NEs in the system, such as the UE, NodeB, RNC and CN.

In the relocation preparation procedure initiated by the SRNC for traffic beared on HS-DSCH, the “RELOCATION REQUIRED” message carries the configuration parameters of HSDPA that has IUR MAC-d FLOW, and then the subsequent procedure is identical with the relocation procedure triggered by soft handover.

Figure 18 shows the overall procedure of SRNC relocation.

2 . Relocation Required RANAP RANAP

RANAP RAN AP

6 . Relocation Request Ack.

RANAP RAN AP 1 . Relocation Required

UE Node B

RNC Source

RNC Target

M SC/SGSN SGSN/M SC

RANAP RAN AP

4 . Relocation Request

RANAP RANAP

3. Reloca tion Request

RANAP RANAP 7 . Relocation Request Ack.

RANAP RAN AP

9. Reloca tion Command

RANAP RAN AP

8 . Relocation Command

RANAP RANAP

14 . Relocation Complete

RANAP RANAP 13. Reloca tion Complete

RN SAP RNSAP

10 . Reloca tion Commit

RAN AP 15 . Iu Release Command

RANAP

RAN AP 16. Iu Release Command

RANAP

5 . ALCAP Iu D ata Transport Bearer Setup

17. ALCAP Iu Data Transpor t Bearer Relelase

RAN AP 18. Iu Release Complete

RANAP

RAN AP 19 . Iu Release Complete

RANAP

RANAP RAN AP

12. Reloca tion Detect

RANAP RAN AP 11. Reloca tion Detect

Figure 18 SRNC relocation procedure (Span two CNs )



6.1 Relocation Triggered by Soft Handover

UE

TargetRNCSGSNSource

RNC1.Relocation Required

2.Relocation Request

3.Relocation Request Ack

4.Relocation Command

5.Relocation Commit

6.Relocation Detect7.UTRAN Mobility

Information

8.UTRAN Mobility Information Confirm

9.Relocation Complete

10.Iu Release Command

11.Iu Release Complete

Figure 19 Relocation triggered by soft handover

Procedure description:

1 Upon detecting that all links already exist in a DRNC, the SRNC initiates the relocation procedure and sends a “Relocation Required” message to the CN. If the SRNC connects with CS and PS domains, it needs to send the “Relocation Required” message to CS and PS domains.

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.

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.

Relocation failure caused by “UTRAN Mobility Information” message transmission failure

The DRNC fails to initiate the “UTRAN Mobility Information Configuration” procedure due to procedure timeout or the UE failure in returning UTRAN mobility message. In such a case, the DRNC does not send a “Relocation Complete” message to the CN, and after the CN relocation timer times out, the CN initiates a “Iu Release Command” message to release the resources on the DRNC side.

6.2 Relocation Triggered by Hard Handover

UE

TargetRNCSGSNSource

RNC1.Relocation Required

2.Relocation Request

3.Relocation Request Ack

4.Relocation Command

7.Relocation Detect8.Physical Channel

Reconfiguration Complete

9.Relocation Complete

10.Iu Release Command

11.Iu Release Complete

5.Physical Channel Reconfiguration

UE6.UE detected by target RNC

Figure 20 Relocation triggered by hard handover

Procedure description:

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

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

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.

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.

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.

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

1iiUTRANUTRAN LogM10W)(1MLog10WLogM10Q

A

⋅⋅−+

⋅⋅=⋅= ∑

=

Where:

QUTRAN indicates the measurement result of the currently used UTRAN frequency (dB for Ec/No; dBm for RSCP).

MUTRAN indicates the measured physical value of the currently used UTRAN frequency (ratio for Ec/No; mV for RSCP).

Mi indicates the measured physical value of cell I in the current active set.

NA indicates the number of the cells (excluding best cells) in an active set.

MBest indicates the measurement result of the best cells in an active set.

W indicates the weight of the best cells in an active set in the frequency quality evaluation of the currently used UTRAN.

7.1.1 Overview of Inter-RAT Measurement

Inter-RAT measurement is to measure the Inter-RAT cells. In the case of Inter-RAT measurement, the measured quantity of the UTRAN network can be triggered based on the measured quantity of Ec/N0 or RSCP. The specific parameter used is controlled by the NonIntraMeasQuan parameter. The measured quantity of Inter-RAT measurement depends on the systems to be measured. For the GERAN, the measured quantity is RSSI. At present, Inter-RAT measurement supports only the handover modes reported through events. The IntRatHoMth parameter is invalid.

3GPP defies a series of Inter-RAT measurement events. An UE reports the corresponding events when defined conditions are met.

3A: The currently used UTRAN carrier quality is lower than a threshold, and the quality of other radio systems is higher than a threshold. It is used for decision of Inter-RAT handover.

/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, if Inter-RAT measurement is not enabled or the conditions for Inter-RAT blind handover are met but blind handover fails, Inter-RAT measurement is set up.

iii Inter-frequency measurement is enabled, and all non-working carriers trigger 2E events. In this case, if the conditions for Inter-RAT blind handover are not met and Inter-RAT neighboring cells exist, or the conditions for Inter-RAT blind handover are met, but blind handover fails, inter-frequency measurement is disabled, and Inter-RAT measurement is set up.

• When the value of the service handover IE is Handover to GSM shall not be performed, it indicates that the service cannot be switched to the GSM. For such a service, the RNC does not enable Inter-RAT measurement or trigger the handover to GSM.

• For the service handover attribute of concurrent services, the highest service handover value of BasicPrio is used. When a concurrent service is added or deleted, the RNC needs to determine the service handover attribute and thus decides to adopt the measurement policy and handover policy between 2G systems.

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

perform Inter-RAT handover.

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

7.1.2.5 Policy for Setting Inter-RAT Measurement Parameters

• Policy for setting Inter-RAT event parameters

There are four Inter-RAT measurement events, namely, 3A, and 3Cevents. The EventId [MAX_RAT_MEAS_EVENT] (Rat) parameter controls the number of the events to be configured. The EventId [MAX_RAT_MEAS_EVENT] (Rat)



parameter controls the specific events to be configured. The MeaEvtId parameter is defined in array mode. The dimension of arrays equals the value of MeasEvtNum, being 4 at most.


Measurement parameters are based on cells. Therefore, in the case of macro diversity, the measurement parameters configured for the best cell are used as handover parameters. If the best cell changes, the measurement parameters must be updated.


• Setting of multiple sets of handover parameters

Inter-RAT handover parameters can be configured separately according to the measured quantity, measurement reporting mode, and service bearer type. In this way, multiple sets of measurement parameters are required for different purposes. The classification is as follows:

Measured quantity of the UTRAN

− NonIntraMeasQuan ( PCPICH RSCP or Ec/N0)

Measurement reporting mode

− IntRatHoMth (Event report or periodically report Only Event report can be supported currently. So the following parameters for periodically report is not used currently: PrdMeasEcNo(RAT), PrdMeasRSCP(RAT), PrdRptAmount(RAT), PrdRptInterval(RAT) )

Service bearer type (TrfCategory(Rat))









− Not Related to Service Type (used for detect set measurement)



For ease of parameter modification and optimization, Inter-RAT handover parameters are arranged by indexes. The index relation is as follows:

Figure 21 Indexing relation for Inter-RAT handover

The procedure for obtaining an Inter-RAT handover parameter is as follows: 1) Obtain the TrfCatRatMIdx parameter from Utran Cell (utranCell). 2) Find the InterRatCfgNo parameter in UE Inter-Rat Measurement Relative to Traffic Category (CRat) based on TrfCatRatMIdx, TrfCategory, and EvtMeasRSCP or EvtMeasEcNo. 3) Find the corresponding handover measurement parameter in UE Inter-Rat Measurement Configuration Information(Rat) based on InterRatCfgNo.

Note: Each InterRatCfgNo corresponds to an EvtMeasRSCP or EvtMeasEcNo, indicated by InterRatCfgNote.

• The relations between the other parameters to be entered in the Inter-RAT measurement control message and the OMCR parameters are as follows: Measurement report transmission mode (MeasRptTrMod) GSM BSIC acknowledgement indication for Inter-RAT measurement

(BSICVeriReq)

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

(OwnMeasQuantity)

(OwnMeasQuantity) (RptCrt(Rat)

Note: OwnMeasQuantity and RptCrt(Rat) are automatically entered based on InterRatCfgNote, and manual operations are not needed. The values of these parameters are for maintenance personnel’s reference.

7.1.3 Processing in the Case of More Than 32 Inter-RAT Neighboring Cells

When an active set has many cells, the number of the Inter-RAT neighboring cells for the cells in an active set may exceed the maximum value, 32. When the number of Inter-RAT neighboring cells exceeds 32, some must be deleted to ensure only 32 Inter-RAT neighboring cells exist in an active set.



In addition, the cells to be deleted must be the cells having the least impacts on active set users, namely, the cells having the poorest signal quality or in furthest geographic locations. For this purpose, priority is defined for each Inter-RAT neighboring cell.

7.1.3.1 Priority Settings of Cells

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

Source Cell

Priority 0

Priority 1

Priority 2

Figure 22 Priority settings of cells

7.1.3.2 Deletion policy in the case of more than 32 neighboring cells

Related standards stipulate that the maximum number of Inter-RAT neighboring cells is 32. When an UE is in macro diversity state, the number of unions of Inter-RAT neighboring cells of multiple cells in the macro diversity may exceed this limit. Therefore, a specific policy is needed to delete neighboring cells. The policy involves combination, selection, and deletion of the neighboring cells with the same priority.

• Priority combination

If a cell is a common neighboring cell of multiple cells in the active set, it may be configured with different priority levels in different cells. In this case, the multiple priority



levels of this cell must be combined, using the highest priority level as the priority of this cell.

• Neighboring cell list update and deletion in the case of more than 32 neighboring cells

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

7.7 with ShareCover (Overlap or Covers)with GsmShareCover (Overlap or Covers)with GsmShareCover (Overlap or Covers)Coupling for Different Handover Causes As described above, the causes of Inter-RAT handover include the following:

• 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.8 Inter-RAT Handover Process

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

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

Figure 23 3G to 2G CS service handover

7.8.2 PS Service Reselection in 3G to 2G Handover

The handover of PS domain from the UTRAN to the GSM can be classified into the following cases:

• The UE actively initiates the PS service reselection. The UE selects a GPRS cell to dwell through the cell reselection process, sets up a connection with the target cell, and then initiates route area update. This case applies to an UE in CELL_FACH or URA_PCH state.



U E CN

1. C ell R eselectio ntriggered

S ervingR NC

R AN A P R A N A P2 . Iu Release Co m m and

R AN A P R AN A P2. Iu Release Co m plete

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

• The RNC actively initiates PS service reselection. The RNC decides to switch the UE to another RAT cell according to handover decision results. This case applies to an UE in CELL_DCH or CELL_FACH state. The RNC sends a handover command CELL CHANGE ORDER FROM UTRAN to the UE. After receiving the command, the UE sets up a connection with the target cell, and then initiates route area update.

Figure 25 PS service reselection initiated by the RNC in the case of 3G to 2G handover

Note: Both processes are applicable to an UE in CELL_FACH state. The specific policy is as follows: The process of PS service reselection actively initiated by the UE is used for the 3G to 2G PS service handover based on radio quality. The process of PS service reselection actively initiated by the RNC is used for the 3G to 2G PS service handover based on load.

8 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 Figure 26 shows the process of querying whether a neighbor cell belonging SRNC is authorized according to the IMSI information carried in the CommonID message of lu interface and also the authorization information configured in the network side. The steps of the query are:

1 Resolve the MCC (rncPnSnac), MNC and other number information ExtInfo (10 digits at most, number of digits depending on ExtInfoDgtNum) according to the IMSI carried in the CommonID message of lu interface.

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

8.2 Querying Whether a DRNC Cell Is Authorized According to IMSI Figure 26 shows the process of querying whether a neighbor cell belonging DRNC is authorized according to the IMSI information carried in the CommonID message of lu interface and also the authorization information configured in the network side. The steps of the query are:

4 Resolve the MCC (rncPnSnac), MNC and other number information ExtInfo (10 digits at most, number of digits depending on ExtInfoDgtNum) according to the IMSI carried in the CommonID message of lu interface.

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

6 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 27 Schematic Diagram of Querying Whether a DRNC Cell Is Authorized According to IMSI

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

9.1 Overview The cells are classified in three types according to the support capability of HSDPA (HspaSptMeth) after HSDPA is introduced: (1) support HSDPA and DCH; (2) do not support HSUPA or HSDPA; (3) support HSDPA only. The services are classified in two types: HSDPA service and NHSDPA service. The HSDPA handover is similar to R99 handover in terms of measurement and handover decision, except that the decisions of cell capacity during a handover and the service type are added. For the HSDPA service, the handover is accepted through HS-DSCH to the cells that support HSDPA and DCH and cells that support HSDPA only as much as possible. If the HS-DSCH fails, accept the handover to the cells that support HSDPA and DCH and cells that do not support HSUPA or HSDPA through DCH. For the NHSDPA service, the handover can only be accepted through DCH to the cells that support HSDPA and DCH and cells that do not support HSUPA or HSDPA.



After HSDPA is introduced, the inter-RNC handover also depends on the capability of office direction RNC to support HSDPA (RncFeatSwitch) because neighbor cells feature varying support capabilities (HspaSptMeth). That is, only if both the target cell and target RNC (office direction RNC) support HSDPA, the HS-DSCHàHS-DSCH handover can be performed. Otherwise, the DCHàDCH handover flow cannot be originated until HS-DSCH falls back to DCH. The channel transfer is performed along with handover. Different channel transfer situations are described in the following based on different handover types.

9.2 Intra-frequency Handover The intra-frequency handover of HDSPA includes soft add/soft drop/soft replacement of HS-DSCH associated channel, HS-DSCH service cell change, channel type change due to different capabilities between source cell and target cell during the handover process. The strategy of soft add/soft drop/soft replacement of HS-DSCH associated channel is described in “strategy of intra-frequency handover”. The HS-DSCH service cell change and channel type change are special handover strategies that make HSDPA different from the R99 (DCH) handover. The specific principles are:

1 HS-DSCH->DCH

• If the HS-DSCH is used before the handover and the link to be deleted for 1B event triggering/radio link failure happens to be the service cell of HS-DSCH, and also the cells in the active set do not support acceptance through HS-DSCH, a decision of soft handover together with HS-DSCH transferring to DCH is made.

• If the HS-DSCH is used before the handover and the 1C event is triggered, the cell to be replaced is the HS-DSCH service cell and also the cells in the new active set do not support acceptance through HS-DSCH, a decision of soft handover together with HS-DSCH transferring to DCH is made.

• If the HS-DSCH is used before the handover and the 1D event triggers 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 Description 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 acceptance through HS-DSCH, a decision of inter-frequency hard handover 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 (measurement-based or blind handover) and also the target cell supports acceptance through HS-DSCH, a decision of inter-frequency hard 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 Description for details).

10.1 Overview HSUPA is developed on the basis of HSDPA. An HSUPA network element (UE, RNC or NodeB) that supports HSUPA will also supports HSDPA. That is, if E-DCH is adopted in uplink, HS-DSCH is adopted in downlink without doubt. Therefore, HSUPA supports five types of cells (HspaSptMeth): (1) cells that support HSUPA and HSDPA; (2) cells that support HSUPA, HSDPA and DCH; (3) cells that support HSDPA and DCH; (4) cells that support HSDPA only; (5) cells that do not support HSUPA or HSDPA. For the cells that support HSUPA and HSDPA, the E-DCH is used in uplink and the HS-DSCH is used in downlink. The DPCH is used as associated channel. For the cells that support HSUPA, HSDPA and DCH, the E-DCH or DCH is used in uplink and the HS-DSCH or DCH is used in downlink. The DPCH is used as associated channel or allocated to users who do not use HSUPA or HSDPA.

The service types supported by HSUPA are HSPA services if they can be carried by HSUPA or HSDPA (HSUPA and HSDPA are equivalent as far as the services are concerned). Otherwise they are NHSPA services. The HSPA services should be accepted first through E-DCH and HS-DSCH in cells that support HSUPA and HSDPA, cells that support HSDPA only, cells that support HSUPA, HSDPA and DCH and cells that support HSDPA and DCH (HspaSptMeth). If E-DCH and HS-DSCH fail to accept



the services, the HSPA services should be accepted through DCH in cells that support HSUPA, HSDPA and DCH, cells that support HSDPA and DCH or cells that do not support HSUPA or HSDPA. The NHSPA services can only be accepted through DCH in cells that support HSUPA, HSDPA and DCH, cells that support HSDPA and DCH or cells that do not support HSUPA or HSDPA.

The maximum number of cells allowed in the E-DCH active set in the process of HSUPA soft handover is controlled by the parameter MaxNumOfEdchAct.

After HSUPA is introduced, the inter-RNC handover also depends on the capability of office direction RNC to support HSUPA (RncFeatSwitch) because neighbor cells feature varying support capabilities (HspaSptMeth). That is, only if both the target cell and target RNC (office direction RNC) support HSUPA, the E-DCHàE-DCH handover can be performed. Otherwise, the DCHàDCH handover flow cannot be originated until E-DCH falls back to DCH. The channel transfer is performed along with handover. Different channel transfer situations are described in the following based on different handover types.

10.2 Intra-frequency Handover The intra-frequency handover of HDUPA includes soft add/soft drop/soft replacement of E-DCH associated channel, E-DCH service cell change, channel type change due to different capabilities between source cell and target cell during the handover process. The strategy of soft add/soft drop/soft replacement of E-DCH associated channel is described in “strategy of intra-frequency handover”. The E-DCH service cell change and channel type change are special handover strategies that make HSUPA different from the R99 (DCH) handover. The specific principles are:

1 HS-DSCH/E-DCH->DCH/DCH

• If the link to be deleted for 1B event triggering/radio link failure happens to be the service cell of HS-DSCH/E-DCH, and also the cells in the active set do not support acceptance through HS-DSCH/E-DCH or HS-DSCH/DCH, a decision of soft handover together with HS-DSCH/E-DCH transferring to DCH/DCH is made.

• If the 1C event is triggered, the cell to be replaced is the HS-DSCH/E-DCH service cell and also the cells in the new active set do not support acceptance through 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 Description 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.

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

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



10.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/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 (measurement-based or blind handover) and also the target cell supports 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

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 supports acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover together with HS-DSCH/E-DCH service cell change is made.

4 HS-DSCH/E-DCH->HS-DSCH/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 supports 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 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 acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover 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).

11.1 Intra-frequency Handover 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, if the best cell does not belong to MBMS service area, the best cell does not support the MBMS service, the best cell has set up the p-t-m bearer, or the best cell is not the convergence carrier of the service, then p-t-p RB is released.

• For the MBMS service has not set up p-t-p bearer but the MBMS service connection already exists, the best cell belongs to MBMS service area, the best cell supports the MBMS service, the bearer type strategy needs to set up the p-t-m bearer and the carrier can set up the bearer of the service, then p-t-p RB is set up.

3 The principle of the type change in the bearer of the MBMS service in the active set under the macro diversity.

Table 3 Table of Principle

Bearer Change Type Cell Type Principles of Change Best cell Delete the p-t-p

p-t-p->p-t-m Non best cell No change



Best cell

Set up p-t-p: If the channel of the service is DCH, then set up p-t-p for all cells in the active set; if the channel of the service is HS-DSCH, then set up p-t-p in the best cell.

p-t-m ->p-t-p

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.

11.2 Inter-frequency Handover 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(utranCell) Cell individual offset CellIndivOffset(utranRelation) 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

MeaEvtId[MAX_INTRA_MEAS_EVENT] Intra-frequency Measurement Event ID

TrfCategory Service and Bearer Type Used for Differentiating Handover Configuration

EvtMeasEcNo UE Event Report Configuration Index for CPICH Ec/No

EvtMeasDctEcNo Detected Set Measurement Configuration Index for CPICH Ec/No

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

Measurement ThreshUsedFreq[MAX_INTRA_MEAS_EVENT]

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

MaxNumOfAct Maximum Number of Cells Within DCH Active Set

StateMode UE State Indicator Used for UTRAN Neighboring Cell Configuration

ReadSFNInd Read SFN Indicator SoftHoMth Soft Handover Method IntraMeasQuan UTRAN Measurement Quantity for 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

EvtRptInterval 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

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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Detected Set Handover Switch

• Parameter Configuration

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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Cell Individual Offset(dB)


This parameter defines the individual offset of cells in the active set relative to other cells. When the value is positive, a positive value is added to the measurement result. If the value is negative, a negative value is added to the measurement result. Refer to the description of the formula for triggering event 1B/1C/1d in section 4.3 for the effect of this parameter on the measurement report.

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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Neighbouring Cell->Neighbouring Cell XXX->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.

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.12 Reporting Deactivation Threshold for Event 1A

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Intra-frequency Measurement Configuration Index Related to Traffic Category


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

12.1.2.16 Intra-frequency Measurement Configuration Index

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement Configuration-> Intra-frequency Measurement Configuration Index


Each intra-frequency measurement configuration with different measurement purpose and measurement quantity is assigned with a unique intra-frequency measurement configuration index. This parameter indicates the index of the intra-frequency measurement configuration. This configuration index is cited in the table Intra-frequency measurement configuration relationship of the service type-related UE.



That is, the parameter Intra-frequency Measurement Configuration Index Related to Traffic Category (namely TrfCatIntraMIdx) is cited in the advanced parameter of the serving cell and different Intra-frequency Measurement Configuration Indexes (namely IntraMeasCfgNo) can be selected aiming at the specific service type, measurement purpose, and measurement quantity. Hence, this parameter can be used to meet the various requirements of network planning.

12.1.2.17 Intra-frequency Measurement Event ID

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement Configuration-> Intra-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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement Relative to Traffic Category Configuration Information->UE Event Report Configuration Index for CPICH Ec/No • Parameter Configuration



This parameter indicates the index of the intra-frequency measurement configuration for event reporting judgment by the UE when the measurement quantity is CPICH Ec/No.

Table 4 Default Value of the UE Intra-frequency Measurement Configuration Parameters Related to Traffic Category

Fiel

d N

ame

Def

ault

Valu

e 1

Def

ault

Valu

e 2

Def

ault

Valu

e 3

Def

ault

Valu

e 4

Def

ault

Valu

e 5

Def

ault

Valu

e 6

Def

ault

Valu

e 7

Def

ault

Valu

e 8

Def

ault

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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement Relative to Traffic Category Configuration Information->Period Report Configuration Index for CPICH Ec/No • Parameter Configuration

This parameter indicates the index of the intra-frequency measurement configuration for 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement Relative to Traffic Category Configuration Information->Period Report Configuration Index for CPICH RSCP • Parameter Configuration

This parameter indicates the index of the intra-frequency measurement configuration for 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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement Relative to Traffic Category Configuration Information-> UE Event Report Configuration Index for CPICH RSCP • Parameter Configuration

This parameter indicates the index of the intra-frequency measurement configuration for event reporting judgment by the UE when the measurement quantity is CPICH RSCP.

12.1.2.23 Detected Set Measurement Configuration Index for CPICH Ec/No

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frequency Measurement Relative to Traffic Category Configuration Information->Detected Set Measurement Configuration Index for CPICH RSCP • Parameter Configuration

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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement Configuration-> CPICH RSCP Reporting Indicator


This parameter indicates whether the UE should report the measurement result based on the measurement quantity CPICH RSCP.

This parameter is associated with the parameter MeasQuantity. When MeasQuantity is set to 1, the parameter RscpRptInd must be set to TRUE.

12.1.2.30 Pathloss Reporting Indicator

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement Configuration-> Pathloss reporting indicator


This parameter indicates whether the UE should report the measurement result based on the measurement quantity pathloss.

12.1.2.31 Report Criteria

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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 Management-> Modify Advanced Parameter->UE Intra-frquence Measurement 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 Maximum Number of Cells Within DCH Active Set

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->RNC Radio Resource Management->Maximum Number of Cells Within DCH Active Set


This parameter indicates the maximum number of cells allowed in the DCH active set. The default value of the parameter is 3.

12.1.2.35 UE State Indicator Used for UTRAN Neighboring Cell Configuration

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Neighbouring Cell->Neighbouring Cell XXX->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.36 Read SFN Indicator

• 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->Read SFN Indicator


This parameter indicates whether to read the SFN of the neighbouring cell.In the case of the intra-frequency neighbouring cell, the recommended configuration is True (Read); in the case of the inter-frequency neighbouring cell, the recommended configuration is False (Do not read).

12.1.2.37 Soft Handover Method

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Soft Handover Method


The parameter indicates the soft handover method (periodical method or event method) that should be used in the current cell. The event method is recommended.

12.1.2.38 UTRAN Measurement Quantity for Intra-frequency Measurements

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->UTRAN Measurement Quantity for Intra-frequency Measurements


This parameter indicates the measurement quantity (Ec/No or RSCP) for the intra-frequency measurement of the cell. The measurement quantity Ec/No is recommended.

12.1.2.39 Reporting Interval for Event 1A/1B/1C/1J • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement Configuration-> Reporting Interval for Event 1A/1B/1C/1J




This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event 1A/1C meets the reporting range of quality standards, the UE will report Event 1A/1C periodically (EvtRptInterval) until this event does not meet reporting conditions or the reporting times reach the maximum allowed times (EvtRptAmount).

12.1.2.40 Amount of Reporting for Event 1A/1B/1C/1J • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Intra-frquence Measurement Configuration-> Amount of Reporting for Event 1A/1B/1C/1J • Parameter Configuration

This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event 1A/1C meets the reporting range of quality standards, the UE will report Event 1A/1C periodically (EvtRptInterval) until this event does not meet reporting conditions or the reporting times reach the maximum allowed times (EvtRptAmount).

12.1.2.41 Forbidden Cell Indicator for Event 1A/1B • 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->Forbidden Cell Indicator for Event 1A/1B • Parameter Configuration

This parameter indicates whether the cell is effect while evaluating the intra-frequency 1A/1B event

12.1.2.42 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 • Parameter Configuration

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.43 Switch for RL Reference Time Adjust During Diversity Mode • OMCR Interface

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.44 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.45 Transport Time Delay(externalUtranCell) • OMCR Interface

Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.46 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 • Parameter Configuration

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.2 Inter-Frequency Handover Parameters

12.2.1 Parameter List Field Name Name on the Interface



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 MeaEvtId[MAX_INTER_MEAS_EVENT]

Inter-frequency Event Identity

TrfCategory Service and Bearer Type Used for Differentiating Handover Configuration

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


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


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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->UL BLER Swich for Handover


This parameter indicates the handover switch based on uplink block error rate (BLER). When the switch is on, if the uplink BLER arrives at the threshold, RNC will initiate compressed mode and the inter-frequency measurement.

12.2.2.4 UL Tx Power Switch for Handover

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell-> 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Use of HCS


This parameter indicates whether the HCS function is used.

12.2.2.7 Use of 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Tfast(s)


This parameter indicates whether the UE is in the high-speed moving state in combination with the parameter Nfast. If the best cell changes Nfast times within the period specified by Tfast, the UE is judged to move in a high speed.

12.2.2.11 Nfast

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Nfast


This parameter indicates whether the UE is in the high-speed moving state in combination with the parameter Nfast. If the best cell changes Nfast times within the period specified by Tfast, the UE is judged to move in a high speed.

12.2.2.12 Tslowjudge

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Tslowjudge(s)




This parameter indicates the period of the timer to judge that the UE is moving at a low speed. If the number of times that the UE changes its cell within the time specified by Tslowjudge is less than NSlow and the difference between time when the best cell is changed for the last time and the current time is more than Tslow, the UE is judged to move in a low speed.

12.2.2.13 Tslow

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Tslow(s)


This parameter indicates the minimum time interval between the Tslowjudge expiration and the last best cell change. See the description of the Tslowjudge parameter for its functions.

12.2.2.14 Nslow

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Nslow


This parameter indicates the maximum number of best cell changes within the time specified by Tslowjudge. See the description of the Tslowjudge parameter for its functions.

12.2.2.15 Inter- frequency Handover Tactic

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell-> 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement Configuration-> Filter Coefficient


This parameter indicates the filtering factor that UE performs the L3 filtering on the 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement Configuration-> Absolute Threshold of the Quality of the Currently Used Frequency for 2B/2D/2F


This parameter indicates the absolute threshold that should be configured for event 2b/2d/2f (used when judging the quality of the currently used carrier frequency).

In the case of event 2B, the less the threshold configured, the more difficult the event 2B been triggered.

In the case of event 2D, the less the threshold configured, the more difficult the event 2D been triggered.

In the case of event 2F, the less the threshold configured, the easier the event 2B been triggered.

12.2.2.18 Weight of the Currently Used Frequency for 2A/2B/2D/2F

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement 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.

12.2.2.19 Amount of Reporting in Period Report Criteria • OMC Path

Interface Path: View-> Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement Configuration-> Amount of Reporting in Period Report Criteria • Parameter Configuration

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.2.2.20 Hysteresis(Inter)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement 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


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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement 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.

12.2.2.24 Reporting Interval in Period Report Criteria

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-frequence Mesurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> Inter-frequency event identity


This parameter indicates the identify of the event triggered by the inter-frequency measurement (2a~2f).


• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frequency Measurement 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 exclusively used in the measurement of the detected set.

Table 5 Service Type Related UE Inter-frequency Measurement Parameter ConfigurationDefault Value

Fiel

d N

ame

Def

ault

Valu

e 1

Def

ault

Valu

e 2

Def

ault

Valu

e 3

Def

ault

Valu

e 4

Def

ault

Valu

e 5

Def

ault

Valu

e 6

Def

ault

Valu

e 7

Def

ault

Valu

e 8

Def

ault

Valu

e 9

TrfCatInterMIdx

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



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frequency Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frequency Measurement 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.


Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-frequency Measurement Relative to Traffic Category Configuration Information-> Period Report Configuration Index for CPICH Ec/No • Parameter Configuration

This parameter indicates the index of the inter-frequency measurement configuration for periodic reporting by the UE when the measurement quantity is CPICH Ec/No.


Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-frequency Measurement Relative to Traffic Category Configuration Information->Period Report Configuration Index for CPICH RSCP • Parameter Configuration

This parameter indicates the index of the inter-frequency measurement configuration for periodic reporting by the UE when the measurement quantity is CPICH Ec/No.




• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> Function of Configuration Parameters


This parameter indicates the purpose and functions of the set of inter-frequency measurement configuration parameters.


• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> Measurement Report Transfer Mode



12.2.2.38 UTRA Carrier RSSI

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> CPICH Ec/No Reporting Indicator


This parameter indicates whether the UE should report the measurement results whose measurement quantity is 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.2.2.43 CPICH RSCP Reporting Indicator

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> CPICH RSCP Reporting Indicator




This parameter indicates whether the UE should report the measurement results whose measurement quantity is CPICH RSCP.

This parameter is associated with the parameter MeasQuantity. When MeasQuantity is set to 1, the parameter RscpRptInd must be set to TRUE.

12.2.2.44 Pathloss reporting indicator

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> Pathloss reporting indicator


This parameter indicates whether the UE should report the measurement results whose measurement quantity is pathloss.


• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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 measurement parameters is selected. For example, when the parameter 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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:

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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Inter-frequency Handover Method


The parameter indicates the inter-frequency handover method (periodical method or event method) that should be used in the current cell. The event method is recommended.

12.2.2.51 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements


This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for the inter-frequency and inter-RAT measurements. The measurement quantity RSCP is recommended.

12.2.2.52 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 • Parameter Configuration

This parameter indicates whether PCPICH transmission power is configured.

PCPICH transmission power is valid when this parameter is set “True”. Otherwise, PCPICH transmission power is invalid.



12.3 SRNC Relocation Parameters

12.3.1 Parameter List Parameter Field Name Name on the Interface Trelocprep SRNC Wait Time for Relocation Preparation (100ms) Trelocoverall SRNC Overall Protective Time for Relocation (100ms) RtReDelayTimer Timer of Relocation Delay for RT Service NrtReDelayTimer Timer of Relocation Delay for NRT Service


12.3.2.1 Trelocprep

• OMC Path

Interface Path: view->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->Iu Timer and Constant->Trelocprep


This parameter specifies the maximum time for Relocation Preparation procedure in the source RNC after the SRNC successfully sends the RELOCATION REQUIRED message to the CN. If the SRNC fails to receive the RELOCATION COMMAND message within the time specified by the parameter, the timer is judged as expiry and the relocation is canceled.

12.3.2.2 Trelocoverall

• OMC Path

Interface Path: view->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->Iu Timer and Constant->Trelocoverall


This parameter specifies the maximum time for the initiation of the Iu release by the CN after the SRNC receives the RELOCATION COMMAND message. If the CN fails to initate the Iu release within the time specified by the parameter, the timer is judged as expiry and the SRNC initiates the Iu release instead.

12.3.2.3 RtReDelayTimer

• OMC Path



Interface Path: view->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->RNC Radio Resource Management->RtReDelayTimer


This parameter is applicable to realtime services. It indicates the delay of initiating the relocation procedure after the link at the S side is deleted.

12.3.2.4 NrtReDelayTimer

• OMC Path

Interface Path: view->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->RNC Radio Resource Management->NrtReDelayTimer


This parameter is applicable to nonrealtime services. It indicates the delay of initiating the relocation procedure after the link at the S side is deleted.

12.4 Inter-RAT Handover Parameters

12.4.1 Parameter List Field Name Name on the Interface 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) TrfCategory Service and Bearer Type Used for Differentiating

Handover Configuration



EvtMeasRSCP UE Event Report Configuration Index for Own System CPICH RSCP

InterRatCfgNo Inter-RAT Measurement Configuration Index InterRatCfgNote Function of Configuration Parameters MeasRptTrMod Measurement Report Transfer Mode FilterCoeff(Rat) UTRAN Filter Coefficient(Rat) OwnMeasQuantity UTRAN Measurement quantity GsmFilterCoeff GSM Filter Coefficient(Rat) BSICVeriReq GSM BSIC Verification Required Indicatior UtranEstQual UTRAN Quality Estimation Reporting Indicator GsmCarrRSSIInd GSM Carrier RSSI Reporting Indicator RptCrt Report Criteria EventNum Inter-RAT Measurement Event Number EventId [MAX_RAT_MEAS_EVENT]

Inter-RAT Event Identity

CellIndivOffset(gsmRelation) Cell individual offset(gsmRelation) GsmStateMode UE State Indicator Used for GSM Neighboring Cell

Configuration 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


12.4.2.1 Measurement Priority of Neighboring GSM Cell

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Inter-RAT Handover Tactic


This parameter indicates the measurement event type (3A or 3C) that is used to trigger the inter-RAT handover.

Event 3C can be triggered when the quality of the inter-RAT carrier frequency signal is higher than a certain value. In contrast, the trigger of event 3A requires an additional condition, that is, the quality of the carrier frequency signal of the current RAT must be less than a certain value. Hence, the inter-RAT handover can be triggered more easily when the parameter is set to 3C Event Trigger.

12.4.2.3 UL BLER Switch for Handover

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->UL BLER Swich for Handover


This parameter indicates the handover switch based on uplink BLER. When the switch is on, the RNC will initiate compressed mode and inter-RAT measurement if the uplink BLER quality arrives at the threshold.

12.4.2.4 DL Tx Power Switch for handover

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell-> 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell-> 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-RAT Measurement Configuration Information->Weight of the UTRAN System for 3A


This parameter indicates the weight of the best cell in the quality judgment of event 3a. It is used in judging the quality of the UTRAN system in inter-RAT measurement.

See the description of the formula in Section 7.1 for the effect of this parameter on the inter-RAT measurement.



12.4.2.8 Absolute Threshold of the Quality of Other RAT for 3A/3B/3C

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-RAT Measurement Configuration Information-> Absolute Threshold of the Quality of Other RAT for 3A/3B/3C


This parameter indicates the absolute threshold used when judging the quality of other RAT configured for event 3a/3b/3c. The value range and unit of this parameter are related to the measurement quantity of the cells of other systems. At present, the measurement quantity can only be GSM Carrier RSSI of the GSM system, which corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit of this parameter correspond to CPICH RSCP.

The larger the value configured, the more difficult event 3a/3b/3c be reported.

12.4.2.9 Hysteresis(Rat)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-RAT Measurement Configuration Information-> Hysteresis


This parameter indicates the hysteresis used when judging whether the event meets the conditions of been triggered.

This parameter is related to the measurement quantity and the event type. If a small hysteresis is configured, the corresponding event will be reported in a high probability; and vice versa.

12.4.2.10 Time to Trigger(Rat)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-RAT Measurement Configuration Information-> 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 can be triggered and reported only when the event is detected and still meets all 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.4.2.11 Inter-RAT Measurement Configuration Index Related to Traffic Category（Crat）

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View-> Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell-> 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-Rat Measurement 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 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 6 Service Type Related UE Inter-RAT Measurement Parameter ConfigurationDefault Value

Fiel

d N

ame

Def

ault

Valu

e 1

Def

ault

Valu

e 2

Def

ault

Valu

e 3

Def

ault

Valu

e 4

Def

ault

Valu

e 5

Def

ault

Valu

e 6

Def

ault

Valu

e 7

Def

ault

Valu

e 8

Def

ault

Valu

e 9

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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-Rat Measurement Relative to 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-Rat Measurement Relative to 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration-> Inter-RAT Measurement Configuration Index


Each inter-RAT measurement configuration with different measurement purpose and measurement quantity is assigned with a unique inter-RAT measurement configuration. This parameter indicates the index of the inter-RAT measurement configuration. This configuration index is cited in the table “Inter-RAT measurement configuration relationship of the service type-related UE”.

That is, the parameter Inter-RAT Measurement Configuration Index Related to Traffic Category (namely TrfCatInterMIdx) is cited in the advanced parameter of the serving cell and different Inter-RAT Measurement Configuration Index (namely InterMeasCfgNo) can be selected aiming at the specific service type, measurement purpose, and measurement quantity. This parameter can be used to meet various requirements of network planning.


• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration-> Function of Configuration Parameters


This parameter indicates the purpose and functions of the set of inter-RAT measurement configuration parameters.


• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration-> Measurement Report Transfer Mode





12.4.2.19 UTRAN Filter Coefficient(Rat)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration->UTRAN Filter Coefficient


This parameter indicates the filtering factor that UE performs the L3 filtering on the 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration->UTRAN Measurement quantity


This parameter indicates the measurement quantity of the inter-RAT measurement that UE performs. After a new inter-RAT measurement configuration index is added, the measurement quantity is fixed when the function of the set of the inter-RAT measurement parameters is selected. For example, when the parameter 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration->GSM Filter Coefficient


This parameter indicates the filtering factor that UE performs the L3 filtering on the GSM measurement results of the inter-RAT measurement. The smaller the filtering factor, the larger the effect of the measurement on the final result.



12.4.2.22 GSM BSIC Verification Required Indicatior

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration-> 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 UTRAN Quality Estimation Reporting Indicator

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration-> UTRAN Quality Estimation Reporting Indicator


This parameter indicates whether to report the quality estimation value of the UTRAN system.

12.4.2.24 GSM Carrier RSSI Reporting Indicator

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter->UE Inter-Rat Mesurement Configuration-> GSM Carrier RSSI Reporting Indicator


This parameter indicates whether to report the received signal strength indicator (RSSI) of GSM cells.


• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration-> Report Criteria




This parameter indicates the criteria of reporting the inter-RAT measurement, including the Event Reporting and Periodical Reporting.

12.4.2.26 Inter-RAT Measurement Event Number

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-Rat Measurement Configuration-> Inter-RAT Measurement Event Number


This parameter indicates the number of events that should be configured for the inter-RAT measurement configuration index for a certain purpose.

12.4.2.27 Inter-RAT Event Identity

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->UE Inter-frquence Measurement Configuration-> Inter-RAT event identity


This parameter indicates the identity of the event triggered by the inter-RAT measurement (3a~3d).

12.4.2.28 Cell individual offset(gsmRelation)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.

Through the configuration of the individual offset of a single cell, the trigger difficulty of the cell can be adjusted to meet the actual requirements of network planning, thus avoiding the need to modify the global handover parameters.



12.4.2.29 UE State Indicator Used for GSM Neighboring Cell Configuration

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->GSM Neighbouring Cell->GSM 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 list used for reselection in nondedicated mode and the neighbouring cells 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.4.2.30 Share Cover Indication

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->GSM Neighbouring Cell->GSM 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.31 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->UTRAN Measurement Quantity for Inter-frequency and Inter-RAT Measurements




This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for inter-frequency and inter-RAT measurements. The measurement quantity RSCP is recommended.

12.4.2.32 Inter-RAT Handover Method • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Utran Cell->Inter-RAT Handover Method • Parameter Configuration

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.


Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-Rat Measurement Relative to Traffic Category Configuration Information -> Period Report Configuration Index for CPICH Ec/No • Parameter Configuration

Only event report can be supported currently. So the following parameters for periodically report is invalid: PrdMeasEcNo(RAT), PrdMeasRSCP(RAT), PrdRptAmount(RAT), PrdRptInterval(RAT)


Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter-> UE Inter-Rat Measurement Relative to Traffic Category Configuration Information ->Period Report Configuration Index for CPICH RSCP • Parameter Configuration


12.4.2.35 Amount of Reporting in Period Report Criteria • OMC Path

Interface Path: View-> Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter-> UE Inter-Rat Measurement Configuration->Amount of Reporting in Period Report Criteria • Parameter Configuration




12.4.2.36 Reporting Interval in Period Report Criteria • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Modify Advanced Parameter-> UE Inter-Rat Measurement Configuration->Reporting Interval in Period Report Criteria(ms) • Parameter Configuration


12.4.2.37 Use of HCS (gsmRelation) • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->GSM Neighbouring Cell->GSM Neighbouring Cell XXX ->Modify Advanced Parameter-> Use of HCS



12.4.2.38 HCS_PRIO(gsmRelation) • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->GSM Cell->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.5 IMSI-based Handover Parameters

12.5.1 Parameter List Field Name Name on the Interface 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) LAC(gsmRelation ) Location Area Code of Neighbouring GSM Cell


12.5.2.1 MCC(rncPnSnac)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->User Authorized PLMN+SNAC Information->MCC


This parameter indicates the mobile country code (MCC) of the IMSI card. See Figure 26 in the text for the use case.

12.5.2.2 MNC(rncPnSnac)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->User Authorized PLMN+SNAC Information->MNC




This parameter indicates the mobile network code (MNC) of the IMSI card. See Figure 26 in the text for the use case.

12.5.2.3 Extend Information Digits Num

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.4 Extend Information

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.5 MCC of Shared Network

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.6 MNC of Shared Network

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.7 Shared Network Area Code

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.8 MCC(rncLcSnac)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->LAC and SNAC Information->MCC


This parameter in combination with parameters MNC(rncLcSnac), LAC(rncLcSnac), and SNAC(rncLcSnac) specifies a target area code that the handover is allowed in. See Figure 26 in the text for the use case.

12.5.2.9 MNC(rncLcSnac)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->LAC and SNAC Information->MNC


This parameter in combination with parameters MCC(rncLcSnac), LAC(rncLcSnac), and SNAC(rncLcSnac) specifies a target area code that the handover is allowed in. See Figure 26 in the text for the use case.

12.5.2.10 Location Area Code(rncLcSnac)

• OMC Path



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->LAC and SNAC Information->Location Area Code


This parameter in combination with parameters MCC(rncLcSnac), MNC(rncLcSnac), and SNAC(rncLcSnac) specifies a target area code that the handover is allowed in. See Figure 26 in the text for the use case.

12.5.2.11 Shared Network Area Code(rncLcSnac)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->LAC and SNAC Information->Shared Network Area Code


This parameter in combination with parameters MCC(rncLcSnac), MNC(rncLcSnac), and LAC(rncLcSnac) specifies a target area code that the handover is allowed in. See Figure 26 in the text for the use case.

12.5.2.12 Mobile Country Code(UtranCell)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->UtranCell Global Info>MCC


This parameter indicates the MCC of the cells in the RNC.

12.5.2.13 Mobile Country Code(ExternalUtranCell)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.14 Mobile Country Code（externalGsmCell）

• OMC Path



Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Gsm Cell ->Gsm Cell XXX->MCC


This parameter indicates in the MCC of the GSM cells.

12.5.2.15 Mobile Network Code(UtranCell)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->UtranCell Global Info>MNC


This parameter indicates the MNC of the cells in the RNC.

12.5.2.16 Mobile Network Code(ExternalUtranCell)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.17 Mobile Network Code（externalGsmCell）

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Gsm Cell->Gsm Cell XXX ->MNC


This parameter indicates in the MNC of the GSM cells.

12.5.2.18 Location Area Code(UtranCell)

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->UtranCell Global Info>LAC




This parameter indicates the LAC of the cells in the RNC.

12.5.2.19 OMC PathOMC Path Shared Network Area Code（ExternalUtranCell） • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->External Utran Cell->External Utran Cell XXX->SNAC • Parameter Configuration

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.20 Shared Network Area Code Number（ExternalUtranCell） • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> External Utran Cell ->External Utran Cell XXX->SNACNum • Parameter Configuration

This parameter indicates the number of shared network area code that the neighboring cell belongs to.

12.5.2.21 Shared Network Area Code（externalGsmCell） • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Gsm Cell ->Gsm Cell XXX->SNAC • Parameter Configuration

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（externalGsmCell） • OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management->Gsm Cell ->Gsm Cell XXX->SNACNum • Parameter Configuration

This parameter indicates the number of shared network area code that the neighboring cell belongs to.



12.6 HSDPA Handover Parameters

12.6.1 Parameter List Field Name Name on the Interface HspaSptMeth HSPA Support Method T1d Timer for Event 1D in HSPA or MBMS RncFeatSwitch Neighbouring RNC Feather Switch HsdpaCmAssoMode HSDPA Associate CM Method


12.6.2.1 HSPA Support Method

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->Hspa Configuration Information-> Timer for Event 1D in HSPA or MBMS


For HSPA, this parameter indicates the minimum interval required for the change of the HSPA serving cell or the transition between the HS and DCH channels. A large value of this parameter helps to avoid too frequent HSPA serving cell change and channel transition.

12.6.2.3 Neighbouring RNC Feather Switch

• 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

Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->Hspa Configuration Information-> HSDPA Associate CM Method • Parameter Configuration

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

12.7.1 Parameter List Field Name Name on the Interface HspaSptMeth HSPA Support Method MaxNumOfEdchAct Maximum Number of Cells in E-DCH Active Set RncFeatSwitch Neighbouring RNC Feather Switch HsupaCmAssoMode HSUPA Associate CM Method


12.7.2.1 HSPA Support Method

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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.7.2.2 Maximum Number of Cells in E-DCH Active Set

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->Hspa Configuration Information->Maximum Number of Cells in E-DCH Active Set


This parameter indicates the maximum number of cells allowed in the E-DCH active set. The number is configured according to the actual requirements.

12.7.2.3 Neighbouring RNC Feather Switch

• 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.7.2.4 HSUPA Associate CM Method • OMCR Interface

Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->Hspa Configuration Information-> HSUPA Associate CM Method • Parameter Configuration

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

12.8.1 Parameter List Field Name Name on the Interface



MbmsSuptInd Support MBMS Indicator T1d Timer for Event 1D in HSPA or MBMS


12.8.2.1 Support MBMS Indicator

• OMC Path

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource 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

Interface Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->Hspa Configuration Information-> Timer for Event 1D in HSPA or MBMS


For HSPA, this parameter indicates the minimum interval required for the change of the HSPA serving cell or the transition between the HS and DCH channels. A large value of this parameter helps to avoid too frequent HSPA serving cell change and channel transition.

For MBMS, this parameter indicates the minimum interval required for changing the best cell of the MBMS service for two times caused by event 1d. This parameter helps to avoid too frequent change between the PTP and PTM bearer types.



13 Counter And Alarm

13.1 Counter List

13.1.1 RNC Soft Handover Statistics Counter No. Description C301100479 Number of soft handover attempt C301101040 C301101041 C301101042 C301101043

Number of soft handover attempt,by traffic class

C301100480 C301100481 C301100482 C301100483 C301100484 C301100485 C301100486 C301100487

Number of failed soft handover,by cause

C301101044 C301101045 C301101046 C301101047

Number of failed soft handover,by traffic class

C301100931 C301100932 C301100933 C301100934

Number of soft handover attempt,add Radio link

C301100935 Number of soft handover attempt,add Radio link for HSDPA C301100936 C301100937 C301100938 C301100939

Number of soft handover attempt,delete radio link

C301100940 Number of soft handover attempt,delete radio link for HSDPA C301100941 C301100942 C301100943 C301100944 C301100945

RNC Soft handover ratio



Counter No. Description C301100946 C301100947 C301100948 C301100949 C301100950 C301100951 C301100952 C301100953 RNC Soft handover ratio C301100954 C301100955 C301100956 C301100957 C301100958 C301100959 C301100960

RNC Soft handover ratio for RT Class

C301100961 C301100962 C301100963 C301100964 C301100965 C301100966 C301100967

RNC Soft handover ratio for NRT Class,but no HSPA

C301770104 Number of soft handover attempt,add Radio link,DCH Voice C301770105 Number of soft handover attempt,add Radio link,DCH Video C301770106 Number of soft handover attempt,add Radio link,DCH NRT C301770107 Number of soft handover attempt,add Radio link,HS/D C301770108 Number of soft handover attempt,add Radio link,HS/E C301770109 Number of soft handover attempt,add Radio link,M-DCH C301770110 Number of soft handover attempt,add Radio link,M-HS/D C301770111 Number of soft handover attempt,add Radio link,M-HS/E C301770112 Number of soft handover Success,add Radio link,DCH Voice C301770113 Number of soft handover Success,add Radio link,DCH Video C301770114 Number of soft handover Success,add Radio link,DCH NRT C301770115 Number of soft handover Success,add Radio link,HS/D C301770116 Number of soft handover Success,add Radio link,HS/E C301770117 Number of soft handover Success,add Radio link,M-DCH C301770118 Number of soft handover Success,add Radio link,M-HS/D C301770119 Number of soft handover Success,add Radio link,M-HS/E C301770120 Number of soft handover attempt,Del Radio link,DCH Voice



Counter No. Description C301770121 Number of soft handover attempt,Del Radio link,DCH Video C301770122 Number of soft handover attempt,Del Radio link,DCH NRT C301770123 Number of soft handover attempt,Del Radio link,HS/D C301770124 Number of soft handover attempt,Del Radio link,HS/E C301770125 Number of soft handover attempt,Del Radio link,M-DCH C301770126 Number of soft handover attempt,Del Radio link,M-HS/D C301770127 Number of soft handover attempt,Del Radio link,M-HS/E C301770128 Number of soft handover Success,del Radio link,DCH Voice C301770129 Number of soft handover Success,del Radio link,DCH Video C301770130 Number of soft handover Success,del Radio link,DCH NRT C301770131 Number of soft handover Success,del Radio link,HS/D C301770132 Number of soft handover Success,del Radio link,HS/E C301770133 Number of soft handover Success,del Radio link,M-DCH C301770134 Number of soft handover Success,del Radio link,M-HS/D

C301770135 Number of soft handover Success,del Radio link,M-HS/E

13.1.2 RNC Hard Handover Statistics Counter No. Description C301110488 Number of intra-RNC intra frequency hard handover attempt C301110489 C301110490 C301110491 C301110492 C301110493 C301110494 C301110495 C301110496

Number of intra-RNC intra frequency hard handover failure,by cause

C301110497 Number of intra-RNC inter frequency hard handover attempt C301110498 C301110499 C301110500 C301110501 C301110502 C301110503 C301110504 C301110505

Number of intra-RNC inter frequency hard handover failure,by cause

C301110506 Number of inter-RNC intra frequency hard handover via Iur attempt C301110507 Number of inter-RNC intra frequency hard handover via Iur failure,by



Counter No. Description C301110508 C301110509 C301110510 C301110511 C301110512 C301110513 C301110514

cause

C301110515 Number of inter-RNC inter frequency hard handover via Iur attempt C301110516 C301110517 C301110518 C301110519 C301110520 C301110521 C301110522 C301110523

Number of inter-RNC inter frequency hard handover via Iur failure,by cause

Counter No. Description

C301500136 Number of outgoing hard handover attempted,DCH Voice

C301500137 Number of outgoing hard handover attempted,DCH Video

C301500138 Number of outgoing hard handover attempted,DCH NRT

C301500139 Number of outgoing hard handover attempted,HS/D

C301500140 Number of outgoing hard handover attempted,HS/E

C301500141 Number of outgoing hard handover attempted,M-DCH

C301500142 Number of outgoing hard handover attempted,M-HS/D

C301500143 Number of outgoing hard handover attempted,M-HS/E

C301500144 Number of outgoing hard handover Success,DCH Voice

C301500145 Number of outgoing hard handover Success,DCH Video

C301500146 Number of outgoing hard handover Success,DCH NRT

C301500147 Number of outgoing hard handover Success,HS/D

C301500148 Number of outgoing hard handover Success,HS/E

C301500149 Number of outgoing hard handover Success,M-DCH

C301500150 Number of outgoing hard handover Success,M-HS/D

C301500151 Number of outgoing hard handover Success,M-HS/E

13.1.3 Relocation With UE Involed


C301120543 Number of attempted relocation preparation with UE involved for



C301120544 C301120545 C301120546 C301120547 C301120548 C301120549

CS domain, by cause

C301120550 C301120551 C301120552 C301120553 C301120554 C301120555 C301120556 C301120557 C301120558

Number of failed relocation preparation with UE involved for CS domain, by cause

C301120559 Number of attempted outgoing relocation with UE involved for CS domain

C301120560 C301120561 C301120562 C301120563 C301120564 C301120565 C301120566 C301120567

Number of failed outgoing relocation with UE involved for CS domain, by cause

C301120587 C301120588 C301120589 C301120590 C301120591 C301120592 C301120593

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

C301120594 C301120595 C301120596 C301120597 C301120598 C301120599 C301120600 C301120601 C301120602

Number of failed relocation preparation with UE involved for PS domain, by cause



C301120603 Number of attempted outgoing relocation with UE involved for PS domain

C301120604 C301120605 C301120606 C301120607 C301120608 C301120609 C301120610 C301120611

Number of failed outgoing relocation with UE involved for PS domain, by cause

C301120624 C301120625 C301120626 C301120627 C301120628 C301120629 C301120630 C301120631 C301120632 C301120633 C301120634 C301120635

Number of attempted incoming relocation with UE involved for CS domain, by cause

C301120648 C301120649 C301120650 C301120651 C301120652 C301120653 C301120654

Number of attempted incoming relocation with UE involved for PS domain, by cause

C301120655 C301120656 C301120657 C301120658 C301120659

Number of failed incoming relocation with UE involved for PS domain, by cause

13.1.4 Relocation With UE Not Involed


C301120524 C301120525 C301120526 C301120527

Number of attempted relocation preparation with UE not involved for CS domain, by cause



C301120528 C301120529 C301120530 C301120531 C301120532 C301120533 C301120534 C301120535 C301120536 C301120537 C301120538 C301120539

Number of failed relocation preparation with UE not involved for CS domain, by cause

C301120540 Number of attempted outgoing relocation with UE not involved for CS domain

C301120541 C301120542

Number of failed outgoing relocation with UE not involved for CS domain, by cause

C301120568 C301120569 C301120570 C301120571 C301120572 C301120573 C301120574

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

C301120575 C301120576 C301120577 C301120578 C301120579 C301120580 C301120581 C301120582 C301120583

Number of failed relocation preparation with UE not involved for PS domain， by cause

C301120584 Number of attempted outgoing relocation with UE not involved for PS domain

C301120585 C301120586

Number of failed outgoing relocation with UE not involved for PS domain, by cause

C301120612 C301120613 C301120614 C301120615

Number of attempted incoming relocation with UE not involved for CS domain, by cause



C301120616 C301120617 C301120618 C301120619 C301120620 C301120621 C301120622 C301120623 C301120636 C301120637 C301120638 C301120639 C301120640 C301120641 C301120642

Number of attempted incoming relocation with UE not involved for PS domain, by cause

C301120643 C301120644 C301120645 C301120646 C301120647

Number of failed incoming relocation with UE not involved for PS domain, by cause

13.1.5 RNC Inter-RAT Handover Statistics Counter No. Description C301130660 C301130661 C301130662 C301130663 C301130664 C301130665 C301130666

Number of attempted relocation preparation for outgoing CS inter-RAT handovers, by cause

C301130667 C301130668 C301130669 C301130670 C301130671 C301130672 C301130673 C301130674 C301130675

Number of failed relocation preparation for outgoing CS inter-RAT handovers, by cause



Counter No. Description C301130676 Number of attempted outgoing CS inter-RAT handovers C301130677 C301130678 C301130679 C301130680 C301130681 C301130682

Number of failed outgoing CS inter-RAT handovers, by cause

C301130683 C301130684 C301130685 C301130686 C301130687 C301130688 C301130689

Number of attempted incoming CS inter-RAT handovers, by cause

C301130690 C301130691 C301130692 C301130693 C301130694

Number of failed incoming CS inter-RAT handovers, by cause

C301130695 Number of attempted outgoing PS inter-RAT handovers C301130696 C301130697 C301130698 C301130699 C301130700

Number of failed outgoing PS inter-RAT handovers, by cause

C301130701 Number of attempted incoming PS inter-RAT handovers C301130702 Number of successful incoming PS inter-RAT handovers C301510029 Number of attempted outgoing inter-RAT handovers,DCH Voice C301510030 Number of attempted outgoing inter-RAT handovers,DCH Video C301510031 Number of attempted outgoing inter-RAT handovers,DCH NRT C301510032 Number of attempted outgoing inter-RAT handovers,HS/D C301510033 Number of attempted outgoing inter-RAT handovers,HS/E C301510034 Number of attempted outgoing inter-RAT handovers,M-DCH C301510035 Number of attempted outgoing inter-RAT handovers,M-HS/D C301510036 Number of attempted outgoing inter-RAT handovers,M-HS/E C301510037 Number of Failure outgoing inter-RAT handovers,DCH Voice C301510038 Number of Failure outgoing inter-RAT handovers,DCH Video C301510039 Number of Failure outgoing inter-RAT handovers,DCH NRT C301510040 Number of Failure outgoing inter-RAT handovers,HS/D



Counter No. Description C301510041 Number of Failure outgoing inter-RAT handovers,HS/E C301510042 Number of Failure outgoing inter-RAT handovers,M-DCH C301510043 Number of Failure outgoing inter-RAT handovers,M-HS/D C301510044 Number of Failure outgoing inter-RAT handovers,M-HS/E

13.1.6 Cell Soft Handover Statistics Counter No. Description C301391098 C301391099 C301391100

Number of attempted radio link addition for soft handover

C301391101 C301391102 C301391103

Number of failed radio link addition for soft handover, by procedure

C301390586 C301390587 C301390588 C301390589 C301390590 C301390591 C301390592 C301390593

Number of failed radio link addition for soft handover,by cause

C301390594 Number of attempted radio link deletion for soft handover C301390595 C301390596 C301390597 C301390598 C301390599 C301390600 C301390601 C301390602

Number of failed radio link deletion for soft handover,by cause

C301391156 C301391157 C301391158

Number of attempted radio link addition for E-DCH soft handover

C301391159 C301391160 C301391161

Number of failed radio link addition for E-DCH soft handover, by procedure

C301391162 C301391163

Number of failed radio link addition for E-DCH soft handover,by cause



Counter No. Description C301391164 C301391165 C301391166 C301391167 C301391168 C301391169 C301391250 Number of attempted radio link deletion for E-DCH soft handover C301391251 C301391252 C301391253 C301391254 C301391255 C301391256 C301391257 C301391258

Number of failed radio link deletion for E-DCH soft handover,by cause

C301390603 C301390604 C301390605 C301390606 C301390607 C301390608 C301390609 C301390610 C301390611 C301390612 C301390613 C301390614 C301390615

Soft handover ratio

C301391332 C301391333 C301391334 C301391335

Soft handover rate of E-DCH user

C301391509 C301391510 C301391511 C301391512 C301391513 C301391514 C301391515

Stat of Soft Handover for DCH RT traffic



Counter No. Description C301391516 C301391517 C301391518 C301391519 C301391520 C301391521 C301391522 C301391523 C301391524 C301391525 C301391526 C301391527 C301391528 C301391529 C301391530 C301391531 C301391532

Stat of Soft Handover for DCH NRT traffic

C301391533 C301391534 C301391536 C301391537 C301391538 C301391539 C301391540 C301391541 C301391542 C301391543 C301391544 C301391545 C301391546 C301391547 C301391548 C301391549

Stat of Soft handover for E-DCH(Traffic Class)

C301770104 C301770105 C301770106 C301770107 C301770108 C301770109

Number of soft handover attempt,add Radio link,by channel and traffic



Counter No. Description C301770110 C301770111 C301770112 C301770113 C301770114 C301770115 C301770116 C301770117 C301770118 C301770119

Number of soft handover Success,add Radio link,by channel and traffic

C301770120 C301770122 C301770123 C301770124 C301770125 C301770126 C301770127

Number of soft handover attempt,Del Radio link,by channel and traffic

C301770128 C301770129 C301770130 C301770131 C301770132 C301770133 C301770134 C301770135

Number of soft handover Success,del Radio link,by channel and traffic

13.1.7 Cell Hard Handover Statistics Counter No. Description

C301410616 Number of outgoing intra-NodeB intra frequency hard handover attempt

C301410617 C301410618 C301410619 C301410620 C301410621 C301410622 C301410623 C301410624

Number of outgoing intra-NodeB intra frequency hard handover failure




C301410625 Number of outgoing intra-NodeB inter frequency hard handover attempt

C301410626 C301410627 C301410628 C301410629 C301410630 C301410631 C301410632 C301410633

Number of outgoing intra-NodeB inter frequency hard handover failure

C301410634 Number of outgoing inter-NodeB,intra-RNC intra frequency hard handover attempt

C301410635 C301410636 C301410637 C301410638 C301410639 C301410640 C301410641 C301410642

Number of outgoing inter-NodeB,intra-RNC intra frequency hard handover failure

C301410643 Number of outgoing inter-NodeB,intra-RNC inter frequency hard handover attempt

C301410644 C301410645 C301410646 C301410647 C301410648 C301410649 C301410650 C301410651

Number of outgoing inter-NodeB,intra-RNC inter frequency hard handover failure

C301410652 Number of outgoing inter-RNC intra frequency hard handover via Iur attempt

C301410653 C301410654 C301410655 C301410656 C301410657 C301410658 C301410659 C301410660

Number of outgoing inter-RNC intra frequency hard handover via Iur failure




C301410661 Number of outgoing inter-RNC inter frequency hard handover via Iur attempt

C301410662 C301410663 C301410664 C301410665 C301410666 C301410667 C301410668 C301410669

Number of outgoing inter-RNC inter frequency hard handover via Iur failure

C301500136 C301500137 C301500138 C301500139 C301500140 C301500141 C301500142 C301500143

Number of outgoing hard handover attempted,by channel and traffic

C301500144 C301500145 C301500146 C301500147 C301500148 C301500149 C301500150 C301500151

Number of outgoing hard handover Success,by channel and traffic

13.1.8 Transfer between HSPA and DCH due to Cell Mobility Counter No. Description C301450826 Number of intra frequency HS-DSCH to DCH attempt due to moving C301450827 C301450828 C301450829 C301450830 C301450831 C301450832 C301450833 C301450834

Number of intra frequency HS-DSCH to DCH failure due to moving

C301450835 Number of inter frequency HS-DSCH to DCH attempt due to moving



Counter No. Description C301450836 C301450837 C301450838 C301450839 C301450840 C301450841 C301450842 C301450843

Number of inter frequency HS-DSCH to DCH failure due to moving

C301450844 Number of intra frequency DCH to HS-DSCH attempt due to moving C301450845 C301450846 C301450847 C301450848 C301450849 C301450850 C301450851 C301450852

Number of intra frequency DCH to HS-DSCH failure due to moving

C301450853 Number of inter frequency DCH to HS-DSCH attempt due to moving C301450854 C301450855 C301450856 C301450857 C301450858 C301450859 C301450860 C301450861

Number of inter frequency DCH to HS-DSCH failure due to moving

C301451186 Number of intra frequency E-DCH to DCH attempt due to moving C301451187 C301451188 C301451189 C301451190 C301451191 C301451192 C301451193 C301451194

Number of intra frequency E-DCH to DCH failure due to moving

C301451195 Number of inter frequency E-DCH to DCH attempt due to moving C301451196 C301451197 C301451198

Number of inter frequency E-DCH to DCH failure due to moving



Counter No. Description C301451199 C301451200 C301451201 C301451202 C301451203 C301451204 Number of intra frequency DCH to E-DCH attempt due to moving C301451205 C301451206 C301451207 C301451208 C301451209 C301451210 C301451211 C301451212

Number of intra frequency DCH to E-DCH failure due to moving

C301451213 Number of inter frequency DCH to E-DCH attempt due to moving C301451214 C301451215 C301451216 C301451217 C301451218 C301451219 C301451220 C301451221

Number of inter frequency DCH to E-DCH failure due to moving

13.1.9 Cell HSPA Handover to 2G Statistics Counter No. Description C301460862 Number of HS-DSCH to 2G handover attempt C301460863 C301460864 C301460865 C301460866 C301460867

Number of HS-DSCH to 2G handover failure

C301461173 Number of E-DCH to 2G handover attempt C301461174 C301461175 C301461176 C301461177 C301461178

Number of E-DCH to 2G handover failure



13.1.10 Cell Inter-RAT Handover Statistics Counter No. Description C301490941 C301490942 C301490943 C301490944 C301490945 C301490946 C301490947

Number of attempted incoming inter-RAT handover for CS domain

C301490948 C301490949 C301490950 C301490951 C301490952

Number of failed incoming inter-RAT handover for CS domain

C301490953 Number of attempted incoming inter-RAT handover for PS domain C301490954 Number of successful incoming inter-RAT handover for PS domain C301490955 C301490956 C301490957 C301490958 C301490959 C301490960 C301490961

Number of attempted relocation preparation for outgoing CS inter-RAT handovers

C301490962 C301490963 C301490964 C301490965 C301490966 C301490967 C301490968 C301490969 C301490970

Number of failed relocation preparation for outgoing CS inter-RAT handovers

C301490971 Number of attempted outgoing CS inter-RAT handovers C301490972 C301490973 C301490974 C301490975 C301490976 C301490977

Number of failed outgoing CS inter-RAT handovers

C301490978 Number of attempted outgoing PS inter-RAT handovers



Counter No. Description C301490979 C301490980 C301490981 C301490982 C301490983

Number of failed outgoing PS inter-RAT handovers

13.1.11 Inter-cell Hard Handover Statistics Counter No. Description

C301500000 Number of outgoing intra-NodeB intra frequency hard handover attempt

C301500001 C301500002 C301500003 C301500004 C301500005 C301500006 C301500007 C301500008

Number of outgoing intra-NodeB intra frequency hard handover failure

C301500009 Number of outgoing intra-NodeB inter frequency hard handover attempt

C301500010 C301500011 C301500012 C301500013 C301500014 C301500015 C301500016 C301500017

Number of outgoing intra-NodeB inter frequency hard handover failure

C301500018 Number of outgoing inter-NodeB,intra-RNC intra frequency hard handover attempt

C301500019 C301500020 C301500021 C301500022 C301500023 C301500024 C301500025 C301500026

Number of outgoing inter-NodeB,intra-RNC intra frequency hard handover failure




C301500027 Number of outgoing inter-NodeB,intra-RNC inter frequency hard handover attempt

C301500028 C301500029 C301500030 C301500031 C301500032 C301500033 C301500034 C301500035

Number of outgoing inter-NodeB,intra-RNC inter frequency hard handover failure

C301500036 Number of outgoing inter-RNC intra frequency hard handover via Iur attempt

C301500037 C301500038 C301500039 C301500040 C301500041 C301500042 C301500043 C301500044

Number of outgoing inter-RNC intra frequency hard handover via Iur failure

C301500045 Number of outgoing inter-RNC inter frequency hard handover via Iur attempt

C301500046 C301500047 C301500048 C301500049 C301500050 C301500051 C301500052 C301500053

Number of outgoing inter-RNC inter frequency hard handover via Iur failure

C301500054 Number of outgoing inter-RNC intra frequency hard handover switching in the CN attempt

C301500055 C301500056 C301500057 C301500058 C301500059 C301500060 C301500061 C301500062

Number of outgoing inter-RNC intra frequency hard handover switching in the CN failure




C301500063 Number of outgoing inter-RNC inter frequency hard handover switching in the CN attempt

C301500064 C301500065 C301500066 C301500067 C301500068 C301500069 C301500070 C301500071

Number of outgoing inter-RNC inter frequency hard handover switching in the CN failure

13.1.12 Inter-cell Soft Handover Statistics Counter No. Description

C301770072 Number of attempted radio link addition for soft handover between cells

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

C301770074 C301770075 C301770076 C301770077 C301770078 C301770079 C301770080 C301770081

Number of failed radio link addition for soft handover between cells,by cause

C301770082 Number of attempted radio link deletion for soft handover between cells

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

C301770084 C301770085 C301770086 C301770087 C301770088 C301770089 C301770090 C301770091

Number of failed radio link deletion for soft handover between cells,by cause

C301770092 Number of attempted soft handover between cells C301770093 Number of Successful soft handover between cells C301770094 Number of failed soft handover between cells,by cause



Counter No. Description C301770095 C301770096 C301770097 C301770098 C301770099 C301770100 C301770101 C301770103 Statistics of soft handover between cells for monitor set

13.1.13 Inter-RAT Cell Handover Statistics Counter No. Description C301510000 C301510001 C301510002 C301510003 C301510004 C301510005 C301510006

Number of attempted relocation preparation for outgoing CS inter-RAT handovers

C301510007 C301510008 C301510009 C301510010 C301510011 C301510012 C301510013 C301510014 C301510015

Number of failed relocation preparation for outgoing CS inter-RAT handovers

C301510016 Number of attempted outgoing CS inter-RAT handovers C301510017 C301510018 C301510019 C301510020 C301510021 C301510022

Number of failed outgoing CS inter-RAT handovers

C301510023 Number of attempted outgoing PS inter-RAT handovers C301510024 C301510025 C301510026

Number of failed outgoing PS inter-RAT handovers



Counter No. Description C301510027 C301510028 C301500129 C301500130 C301500131 C301500132 C301500133 C301500134 C301500135 C301500136

Number of attempted outgoing inter-RAT handovers,by Channel and traffic

C301500137 C301500138 C301500139 C301500140 C301500141 C301500142 C301500143 C301500144

Number of Failure outgoing inter-RAT handovers,by Channel and traffic

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

zte umts handover control feature description v3.1.pdf

Documents