WCDMA R11 Feature Parameter Description - Handover

RAN
Handover
Parameter Description
Issue Date 02 2009-06-30
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided AS IS without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com
RAN Handover
About This Document
About This Document

2009-06-30
RAN Handover
Contents
Contents
1 Introduction to This Document ...............................................................................................1-1
1.1 Scope ............................................................................................................................................................. 1-1 1.2 Intended Audience ......................................................................................................................................... 1-1 1.3 Change History.............................................................................................................................................. 1-1
2 Overview of Handover..............................................................................................................2-1
2.1 Handover Types............................................................................................................................................. 2-1 2.2 Intra-Frequency Handover ............................................................................................................................ 2-2 2.3 Inter-Frequency Handover ............................................................................................................................ 2-4 2.4 Inter-RAT Handover (3G to 2G) ................................................................................................................... 2-5 2.4.1 Inter-RAT Handover Introduction ........................................................................................................ 2-5 2.4.2 Rules for Enabling 3G-to-2G Handover .............................................................................................. 2-6
3 Intra-Frequency Handover Algorithms .................................................................................3-1

3.1 Intra-Frequency Handover Procedure ........................................................................................................... 3-1 3.2 Intra-Frequency Handover Measurement ...................................................................................................... 3-1 3.2.1 Intra-Frequency Handover Measurement Quantities ........................................................................... 3-2 3.2.2 Intra-Frequency Handover Measurement Events ................................................................................. 3-2 3.2.3 Intra-Frequency Handover Neighboring Cell Combination Algorithm ............................................... 3-9 3.3 Intra-Frequency Handover Decision and Execution ................................................................................... 3-10 3.3.1 Decision and Execution ..................................................................................................................... 3-10 3.3.2 Rate Reduction After an SHO Failure ................................................................................................ 3-12 3.4 Intra-Frequency Handover of HSDPA ........................................................................................................ 3-15 3.4.1 Decision and Execution of Intra-Frequency Handover ...................................................................... 3-15 3.4.2 F-DPCH Handover Protection ........................................................................................................... 3-16 3.5 Intra-Frequency Handover of HSUPA ........................................................................................................ 3-17 3.5.1 Decision and Execution of Intra-Frequency Handover ...................................................................... 3-17 3.5.2 Handover Between E-DCHs of 10 ms TTI and 2 ms TTI .................................................................. 3-20 3.6 Signaling Procedures for Intra-Frequency Handover .................................................................................. 3-20 3.6.1 Intra-NodeB Intra-Frequency Soft Handover Signaling Procedure ................................................... 3-20 3.6.2 Intra-RNC Inter-NodeB Intra-Frequency Soft Handover Signaling Procedure ................................. 3-22 3.6.3 Inter-RNC Intra-Frequency Soft Handover Signaling Procedure ...................................................... 3-24 3.6.4 Intra-RNC Inter-NodeB Intra-Frequency Hard Handover Signaling Procedure ................................ 3-26 3.6.5 Inter-RNC Intra-Frequency Hard Handover Signaling Procedure ..................................................... 3-27
4 Inter-Frequency Handover Algorithms .................................................................................4-1

4.1 Inter-Frequency Handover Procedure ........................................................................................................... 4-1 Issue 02 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd iii
4.1.1 Coverage- or QoS-based Inter-Frequency and Inter-RAT Handover Procedure .................................. 4-1 4.1.2 Load-based Inter-Frequency Handover Procedure ............................................................................... 4-3 4.1.3 Speed-based Inter-Frequency Handover Procedure ............................................................................. 4-3 4.2 Inter-Frequency Handover Measurement ...................................................................................................... 4-5 4.2.1 Inter-Frequency Handover Measurement Switches ............................................................................. 4-5 4.2.2 Inter-Frequency Handover Measurement Report Modes ..................................................................... 4-6 4.2.3 Inter-Frequency Handover Measurement Quantity .............................................................................. 4-6 4.2.4 Inter-Frequency Handover Measurement Events ................................................................................. 4-7 4.2.5 Inter-Frequency Handover Neighboring Cell Combination Algorithm .............................................. 4-10 4.2.6 Inter-Frequency Handover Compressed Mode .................................................................................. 4-10 4.3 Inter-Frequency Handover Decision and Execution.................................................................................... 4-12 4.3.1 Coverage- and QoS-based Inter-Frequency Handover Decision and Execution ................................ 4-12 4.3.2 Load-based Inter-Frequency Handover Decision and Execution ....................................................... 4-14 4.3.3 Speed-based Inter-Frequency Handover Decision and Execution ..................................................... 4-15 4.3.4 Blind Handover Decision and Execution Based on Event 1F ............................................................ 4-15 4.3.5 Inter-Frequency Anti-Ping-Pong Algorithm ....................................................................................... 4-16 4.3.6 Inter-Frequency Handover Retry ....................................................................................................... 4-16 4.4 Inter-Frequency Handover of HSDPA ........................................................................................................ 4-16 4.5 Inter-Frequency Handover of HSUPA ........................................................................................................ 4-19 4.6 Signaling Procedures for Inter-Frequency Handover .................................................................................. 4-21 4.6.1 Inter-Frequency Handover Within One RNC ..................................................................................... 4-21 4.6.2 Inter-Frequency Handover Between RNCs ........................................................................................ 4-23
5 Inter-RAT Handover Algorithms ............................................................................................5-1

5.1 3G-to-2G Handover Procedure ..................................................................................................................... 5-1 5.1.1 Coverage-based 3G-to-2G Handover Procedure .................................................................................. 5-1 5.1.2 Load-based 3G-to-2G Handover Procedure ......................................................................................... 5-1 5.1.3 Service-based 3G-to-2G Handover Procedure ..................................................................................... 5-2 5.1.4 Speed-based 3G-to-2G Handover Procedure ....................................................................................... 5-2 5.2 3G-to-2G Handover Measurement ................................................................................................................ 5-3 5.2.1 3G-to-2G Handover Measurement Switches ....................................................................................... 5-3 5.2.2 3G-to-2G Handover Measurement Report Modes ............................................................................... 5-3 5.2.3 3G-to-2G Handover Measurement Quantity ........................................................................................ 5-3 5.2.4 3G-to-2G Handover Measurement Events ........................................................................................... 5-4 5.2.5 3G-to-2G Handover Neighboring Cell Combination Algorithms ........................................................ 5-7 5.2.6 3G-to-2G Handover Compressed Mode .............................................................................................. 5-7 5.2.7 BSIC Verification Requirements for 2G Cells ..................................................................................... 5-7 5.3 3G-to-2G Handover Decision and Execution ................................................................................................ 5-7 5.3.1 Coverage and QoS-based UMTS-to-GSM Handover Decision and Execution ................................... 5-7 5.3.2 Load- and Service-based 3G-to-2G Handover Decision and Execution .............................................. 5-8 5.3.3 3G-to-2G Handover Retry ................................................................................................................... 5-9 5.3.4 3G-to-2G Multimedia Fallback .......................................................................................................... 5-10
iv
02 (2009-06-30)
RAN Handover
Contents 5.3.5 3G-to-2G Handover in the PS Domain with NACC .......................................................................... 5-12
5.4 Inter-RAT Handover of HSDPA .................................................................................................................. 5-12 5.5 Inter-RAT Handover of HSUPA .................................................................................................................. 5-12 5.6 2G-to-3G Handover..................................................................................................................................... 5-13 5.7 Interoperability Between Inter-RAT Handover and Inter-Frequency Handover ......................................... 5-14 5.8 Signaling Procedures for Inter-RAT Handover ........................................................................................... 5-14 5.8.1 3G-to-2G Handover in CS Domain .................................................................................................... 5-14 5.8.2 3G-to-2G Handover in PS Domain .................................................................................................... 5-15 5.8.3 3G-to-2G Handover in Both CS Domain and PS Domain ................................................................. 5-16 5.8.4 2G-to-3G Handover in CS Domain .................................................................................................... 5-18 5.8.5 2G-to-3G Handover in PS Domain .................................................................................................... 5-19
6 HCS Handover Algorithms ......................................................................................................6-1

6.1 HCS Handover Overview.............................................................................................................................. 6-1 6.2 HCS Handover Phases .................................................................................................................................. 6-2 6.2.1 UE Speed Estimation ........................................................................................................................... 6-2 6.2.2 HCS Handover Execution .................................................................................................................... 6-3 6.3 Signaling Procedure of HCS Handover ......................................................................................................... 6-4 6.4 Interoperability Between HCS Handover and Other Handovers ................................................................... 6-4
7 Parameters ...................................................................................................................................7-1 8 Counters .......................................................................................................................................8-1 9 Glossary .......................................................................................................................................9-1 10 Reference Documents............................................................................................................10-1
Issue 02 (2009-06-30)
RAN Handover
1 Introduction to This Document
1
1.1 Scope

Introduction to This Document
The document describes the handover functional area. It provides an overview of the main functions and goes into details regarding handover.
1.2 Intended Audience

It is assumed that users of this document are familiar with WCDMA basics and have a working knowledge of 3G telecommunication. Personnel working on Huawei products or systems. System operators who need a general understanding of handover.
1.3 Change History

This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows:

Feature change: refers to the change in the handover feature. Editorial change: refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows:

02 (2009-06-30) 01 (2009-03-30) Draft (2009-03-10) Draft (2009-01-15)
02 (2009-06-30)
This is the document for the second commercial release of RAN11.0.
Issue 02 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-1
RAN Handover
Compared with 01 (2009-03-30) of RAN11.0, this issue adjusts the structure of the document
01 (2009-03-30)
This is the document for the first commercial issue. Compared with draft (2009-03-10), this issue optimizes the description.
Draft (2009-03-10)
This is the second draft of the document for RAN11.0. Compared with draft (2009-01-15), draft (2009-03-10) optimizes the description.
Draft (2009-01-15)
This is the first draft of the document for RAN11.0. Compared with issue 02 (2008-07-30) of RAN10.0, draft (2009-01-15) incorporates the following changes: Change Type Feature change Change Description None. Parameter Change The name of SIGNAL_HO_SWITCH is changed to HO_MC_SIGNAL_SWITCH. The name of ACT_SET_QUAL_SWITCH is changed to HO_INTER_FREQ_RPRT_2D2F_SWITCH. The name of INTER_FREQ_HHO_SWITCH is changed to HO_INTER_FREQ_HARD_HO_SWITCH. The name of HO_BEYOND_UE_CAP_ADD_TO_MC_SWITC H is changed to HO_MC_MEAS_BEYOND_UE_CAP_SWITCH. The function CS Voice over HSPA is added. The added parameter is as follows:
CSVoiceoverHSPASuppInd
1-2
02 (2009-06-30)
RAN Handover
Change Type Editorial change
Change Description The Handover Parameter Description combines the contents of the following documents:
Parameter Change None.
Intra-frequency Handover Description Inter-frequency Handover Description Inter-RAT Handover Description HCS Handover Description
Issue 02 (2009-06-30)
1-3
RAN Handover
2 Overview of Handover
Overview of Handover
Handover is a basic function of the cellular mobile network. The purpose of handover is to ensure that a UE in CELL_DCH state is served continuously when it moves. The handover functions are classified into the following types: Intra-frequency handover Inter-frequency handover Inter-RAT handover
2.1 Handover Types

Figure 2-1 shows the handovers supported by the Universal Mobile Telecommunications System (UMTS), which include intra-frequency handover, inter-frequency handover, and inter-RAT handover.
Issue 02 (2009-06-30)
2-1
RAN Handover
Figure 2-1 Handovers supported by the UMTS
2.2 Intra-Frequency Handover

Intra-frequency handover is of the following two types:

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

Intra-frequency soft handover is more commonly used than intra-frequency hard handover. The types of intra-frequency soft handover are as follows:

Intra-NodeB soft handover (also known as softer handover) Intra-RNC inter-NodeB soft handover Inter-RNC soft handover
Intra-frequency soft handover is characterized by the function that the UE can be connected to multiple Universal Terrestrial Radio Access Network (UTRAN) access points at the same
2-2
02 (2009-06-30)
RAN Handover
time. Addition and/or release of radio links are controlled by the ACTIVE SET UPDATE procedure. Table 2-1 Differences between soft handover and softer handover Item Scenario Softer Handover When the UE is in the overlapped coverage area of multiple neighboring cells of a NodeB with combined RLs When the UE communicates with multiple cells by setting up multiple channels over the Uu interface Uplink signal Downlink signal Resource use Using maximum-ratio combination Using maximum-ratio combination Occupying less Iub bandwidth Soft Handover When the UE is in the overlapped coverage area of two neighboring cells of different NodeBs When the UE communicates with different cells by setting up multiple channels over the Uu interface
Using selection combination Using maximum-ratio combination Occupying more Iub bandwidth
The HO_INTRA_FREQ_SOFT_HO_SWITCH parameter is used to determine whether to enable both soft handover and softer handover. By default, this switch is set to ON, indicating that both soft handover and softer handover are enabled. After the RNC receives the event 1A, 1B, 1C, or 1D report, it initiates the corresponding soft handover procedure for the UE. For example, the RNC can add or delete links. The DivCtrlField parameter indicates whether maximum-ratio combination is enabled in the uplink during softer handover.
Intra-Frequency Hard Handover

Intra-frequency hard handover refers to a handover where all the old radio links are released before the new radio links are established. Compared with soft handover, intra-frequency hard handover uses fewer resources. The scenarios of intra-frequency hard handover are as follows:

No Iur interface is present between RNCs. In this scenario, intra-frequency hard handover instead of soft handover can be performed between two RNCs. The Iur interface is congested between RNCs. In this scenario, also intra-frequency hard handover instead of soft handover can be performed between two RNCs. There is a high-speed Best Effort (BE) service. Compared with soft handover, intra-frequency hard handover is used to save downlink bandwidth for a high-speed BE service.
The intra-frequency soft handover fails and intra-frequency hard handover is allowed. When intra-frequency soft handover fails because of a congestion problem of the target cell, the RNC tries an intra-frequency hard handover with a lower service bit rate.
The HO_INTRA_FREQ_HARD_HO_SWITCH parameter is used to determine whether to enable intra-frequency hard handover. By default, this switch is set to ON.
Issue 02 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-3
RAN Handover
2.3 Inter-Frequency Handover

Inter-frequency handover provides supplementary coverage for inter-frequency cells to share load with each other and to ensure service continuity. From the UE point of view, inter-frequency handover is the same as intra-frequency hard handover, because for both cases, the old connection is released before a new connection is set up. The types of inter-frequency handover are as follows: Table 2-2 Types of inter-frequency handover Type Coverage-based inter-frequency handover QoS-based inter-frequency handover Load-based inter-frequency blind handover Description If a moving UE leaves the coverage of the current frequency, the RNC needs to trigger the coverage-based inter-frequency handover to avoid call drops. According to the Link Stability Control Algorithm, the RNC needs to trigger the QoS-based inter-frequency handover to avoid call drops. To balance the load between inter-frequency con-coverage cells, the RNC chooses some UEs and performs the inter-frequency blind handover according to user priorities and service priorities. When the Hierarchical Cell Structure (HCS) applies, the cells are divided into different layers according to coverage. The macro cell has a larger coverage and a lower priority, whereas the micro cell has a smaller coverage and a higher priority. Inter-frequency handover can be triggered by the UE speed estimation algorithm of the HCS. To reduce frequent handovers, the UE at a higher speed is handed over to a cell under a larger coverage, whereas the UE at a lower speed is handed over to a cell under a smaller coverage. For detailed information, see 6 HCS Handover Algorithms.
Speed-based inter-frequency handover
The coverage-based inter-frequency measurement and the QoS-based inter-frequency measurement can coexist. The InterFreqHOSwitch parameter is used to determine the type of inter-frequency handover. According to the switch, the RNC chooses the inter-frequency measurement control parameters to implement handover measurement based on coverage, QoS, speed, and other types.

INTER_FREQ_COV: The cell supports coverage-based inter-frequency handover. INTER_FREQ_COV_NCOV: The cell supports coverage-based and speed-estimation-triggered inter-frequency handover. INTER_FREQ_TA: The inter-frequency handover is triggered by HCS traffic absorption. This function itself contains the coverage-based function.
2-4
02 (2009-06-30)
RAN Handover
The HO_INTER_FREQ_HARD_HO_SWITCH parameter is used to determine whether to allow load-based inter-frequency handover. For detailed description of QoS-based inter-frequency blind handover switches, see the Rate Control Parameter Description.
2.4 Inter-RAT Handover (3G to 2G)

2.4.1 Inter-RAT Handover Introduction
Inter-RAT handover refers to the handover performed between 3G network and 2G network. The handover causes can be coverage limitation, link stability, or load limitation of the UMTS network. This document mainly describes the 3G-to-2G handover. Inter-RAT handover provides continuous coverage, load sharing, and HCS services, which fully utilizes the existing 2G network resources and thus reduces operator's cost. Based on the handover triggering causes, the 3G-to-2G handover can be categorized as five types, as described in Table 2-3. Table 2-3 3G-to-2G handover types Type Coverage-based 3G-to-2G handover Description The coverage of the 3G network is incontinuous at the initial stage. On the border of the coverage, the poor signal quality of the 3G network triggers the 3G-to-2G measurement. If the signal quality of the 2G network is good enough and all the services of the UE are supported by the 2G network, the coverage-based 3G-to-2G handover is triggered. According to the Link Stability Control Algorithm, the RNC needs to trigger the QoS-based 3G-to-2G handover to avoid call drops. If the load of the 3G network is heavy and all the RABs of the UE are supported by the 2G network, the load-based 3G-to-2G handover is triggered. Based on layered services, the traffic of different classes is handed over to different systems. For example, when an Adaptive Multi Rate (AMR) speech service is requested, this service can be handed over to the 2G network.
QoS-based 3G-to-2G handover Load-based 3G-to-2G handover Service-based 3G-to-2G handover
Issue 02 (2009-06-30)
2-5
RAN Handover
Type Speed-based 3G-to-2G handover
Description When the Hierarchical Cell Structure (HCS) applies, the cells are divided into different layers according to coverage. The macro cell has a larger coverage and a lower priority, whereas the micro cell has a smaller coverage and a higher priority. The 3G-to-2G handover can be triggered by the UE speed estimation algorithm of the HCS. To reduce the frequencies of handover, the UE at a higher speed is handed over to a cell under a larger coverage, whereas the UE at a lower speed is handed over to a cell under a smaller coverage. For detailed information, see 6 HCS Handover Algorithms.
Note:
The principles of the 3G-to-2G handover based on HCS speed estimation are similar to those of inter-frequency handover.
2.4.2 Rules for Enabling 3G-to-2G Handover

Before handover, the RNC checks whether all the preconditions for the 3G-to-2G handover are met. The preconditions include service handover indicators, service requirements, and handover rules. Before deciding the 3G-to-2G handover, the RNC considers 2G cell capability, service capability and UE capability.
2G cell capability 2G cell capability is configured through the parameter RATCELLTYPE. This parameter indicates whether the cell supports the GSM, GPRS, or EDGE.
Service capability The Required 2G Capability (Req2GCap) specifies the capability of 2G cells required by inter-RAT handover. This indicates whether the service is supported by the GSM, GPRS, or EDGE. For the default value provided by the RNC, see Table 2-6.
UE capability Upon the reception of the UE capability information message, the RNC decides whether to start the inter-RAT measurement. The information indicates whether the UE supports the GSM, GPRS, or EDGE. The rules for enabling the 3G-to-2G handover are based on the Service Handover Indicator and the three types of capability. The rules vary according to the types of inter-RAT handover.
Rules for Enabling Coverage- and QoS-based 3G-to-2G Handover

The RNC initiates the coverage- or QoS-based UMTS-to-GSM handover only when Service Handover Indicator is set as follows:

HO_TO_GSM_SHOULD_BE_PERFORM HO_TO_GSM_SHOULD_NOT_BE_PERFORM
The following tables describe the impacts of different types of capability on handover decision. If the capability of all 2G neighboring cells does not meet the requirement, the inter-RAT measurement will not be triggered.
2-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 02 (2009-06-30)
RAN Handover
Table 2-4 Impacts of different types of capability on handover decision Cell Capability EDGE UE Capability Service Capability (Required by 2G) EDGE EDGE GPRS GSM Not supported by 2G GPRS EDGE GPRS GSM Not supported by 2G GSM EDGE GPRS GSM Not supported by 2G Allowed Allowed Not allowed Not allowed Allowed Allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed GPRS Allowed Allowed Not allowed Not allowed Allowed Allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed Allowed Allowed Allowed Not allowed Allowed Allowed Allowed Not allowed
Rules for Enabling Load- and Service-based 3G-to-2G Handover

The RNC initiates the load-based 3G-to-2G handover only when Service Handover Indicator is set as follows:

HO_TO_GSM_SHOULD_BE_PERFORM HO_TO_GSM_SHOULD_NOT_BE_PERFORM
The RNC initiates the service-based 3G-to-2G handover only when the Service Handover Indicator is set to HO_TO_GSM_SHOULD_BE_PERFORM. The following three tables describe the impacts of different types of capability on handover decision. Table 2-5 Impacts of different types of capability on handover decision Cell Capability EDGE UE Capability Service Capability (Required by 2G) EDGE EDGE GPRS GSM Allowed Not allowed Not allowed GPRS Allowed Allowed Not allowed GSM Allowed Allowed Allowed
Issue 02 (2009-06-30)
2-7
RAN Handover
Cell Capability
UE Capability
Service Capability (Required by 2G) EDGE GPRS Not allowed Allowed Allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed GSM Not allowed Allowed Allowed Allowed Not allowed Allowed Allowed Allowed Not allowed
Not supported by 2G GPRS EDGE GPRS GSM Not supported by 2G GSM EDGE GPRS GSM Not supported by 2G
Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed
If the capability of all neighboring 2G cells does not meet the requirement, the inter-RAT measurement will not be triggered.
Switches for Service-based 3G-to-2G Handover

To perform the service-based 3G-to-2G handover, the RNC must turn on the related switches for services in the CS and PS domains.

When a single CS service is initially set up by the UE, the RNC allows the 3G-to-2G service-based handover if CSServiceHOSwitch is set to ON. When a single PS service is initially set up by the UE, the RNC allows the service-based 3G-to-2G handover if PSServiceHOSwitch is set to ON. For the CS and PS combined services, no service-based handover is triggered.
Service Handover Indicator

The IE Service Handover Indicator indicates the CN policy for the service handover to the 2G network. This IE is indicated in the Radio Access Bearer (RAB) assignment signaling assigned by the CN, or in Table 2-6 provided by the RNC side. The algorithm switch HoSwitch: HO_INTER_RAT_RNC_SERVICE_HO_SWITCH decides whether the service attribute of inter-RAT handover is based on the RNC or the CN.

If the switch is set to ON, the service attribute of inter-RAT handover is based on the parameter configured on the RNC side. If the switch is set to OFF, the service attribute of inter-RAT handover is first based on the CN when the indicator is contained in the RAB assignment signaling assigned by the CN. If the CN does not allocate a service indicator, the service attribute of inter-RAT handover is based on the RNC side.
Through the SHIND parameter, the service handover indicators are set as follows:
HO_TO_GSM_SHOULD_BE_PERFORM: means that the handover to the 2G network is performed when 2G signals are available.
2-8
02 (2009-06-30)
RAN Handover

HO_TO_GSM_SHOULD_NOT_BE_PERFORM: means that the handover to the 2G network is performed when 3G signals are weak but 2G signals are strong. HO_TO_GSM_SHALL_NOT_BE_PERFORM: means that the handover to the 2G network is not performed even when 3G signals are weak but 2G signals are strong.
Figure 2-2 shows an example of rules for the indicator of the 3G-to-2G handover based on load and service. Figure 2-2 Example of rules for indicator of 3G-to-2G handover based on load and service
By default, the RNC does as follows:

For a UE with a single signaling RAB, the RNC supports the handover to the GSM. But it is not recommended. For the UE accessing combined services (with CS services), the RNC sets the service handover indicator of the UE to that of the CS service, because the CS service has the highest QoS priority. For the UE accessing combined services (with only PS services), the RNC sets the service handover indicator of the UE to that of the PS service, because the PS service has the highest QoS priority
If the service handover indicators are not configured by the CN, each indictor can be set to the service parameter index of a service on the RNC. Each service parameter index is the index of one typical service RAB, which involves a set of service type, source description, CN domain ID, and maximum rate (bit/s). Table 2-6 describes the service handover indicators recommended by Huawei.
Issue 02 (2009-06-30)
2-9
RAN Handover
Table 2-6 Service handover indicators (default values) CN Domain ID Max Rate (bit/s) Source Descripti on Requi red 2G Capab ility GSM
RAB Index
Traffic Direction
Traffic Class
Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink
CS_DOM AIN CS_DOM AIN CS_DOM AIN CS_DOM AIN CS_DOM AIN CS_DOM AIN CS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN
CONVER SATION AL CONVER SATION AL CONVER SATION AL CONVER SATION AL CONVER SATION AL CONVER SATION AL STREAM ING CONVER SATION AL CONVER SATION AL CONVER SATION AL CONVER SATION AL CONVER SATION AL CONVER SATION AL
12200
SPEECH
HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM
23850
SPEECH
GSM
28800
UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN
GSM
32000
GSM
56000
GSM
64000
GSM
57600
GSM
11
8000
GSM
12
16000
EDGE
13
32000
EDGE
15
64000
EDGE
16
38800
EDGE
17
39200
EDGE
2-10
02 (2009-06-30)
RAN Handover
RAB Index
Traffic Direction
CN Domain ID
Traffic Class
Max Rate (bit/s)
Source Descripti on
Requi red 2G Capab ility EDGE
18
Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink
PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN
CONVER SATION AL CONVER SATION AL STREAM ING STREAM ING STREAM ING STREAM ING STREAM ING STREAM ING STREAM ING STREAM ING INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE
40000
UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN
HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM
19
42800
EDGE
21 22 23 24 25 26 27 28 40 41 42 43 44 45 46
8000 16000 32000 64000 128000 144000 256000 384000 0 8000 16000 32000 64000 128000 144000
EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE GPRS GPRS GPRS GPRS GPRS EDGE EDGE
Issue 02 (2009-06-30)
2-11
RAN Handover
RAB Index
Traffic Direction
CN Domain ID PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN
Traffic Class
Max Rate (bit/s)
Source Descripti on UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN
Requi red 2G Capab ility EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE GPRS
47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 70
Uplink and downlink Uplink and downlink Uplink Downlink Downlink Uplink Downlink Downlink Uplink and downlink Uplink Downlink Uplink Downlink Downlink Downlink Downlink Downlink Uplink and downlink
INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE INTERAC TIVE BACKGR OUND
256000 384000 608000 768000 1024000 1440000 1536000 1800000 2048000 2880000 3600000 5740000 7200000 10100000 13900000 21000000 27900000 0
HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM
2-12
02 (2009-06-30)
RAN Handover
RAB Index
Traffic Direction
CN Domain ID PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN
Traffic Class
Max Rate (bit/s)
Source Descripti on UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN
Requi red 2G Capab ility GPRS GPRS GPRS GPRS EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE EDGE
71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88
Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink and downlink Uplink Downlink Downlink Uplink Downlink Downlink Uplink and downlink Uplink Downlink Uplink
BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND
8000 16000 32000 64000 128000 144000 256000 384000 608000 768000 1024000 1440000 1536000 1800000 2048000 2880000 3600000 5740000
HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHOUL D_NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM
Issue 02 (2009-06-30)
2-13
RAN Handover
RAB Index
Traffic Direction
CN Domain ID PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN PS_DOM AIN
Traffic Class
Max Rate (bit/s)
Source Descripti on UNKNO WN UNKNO WN UNKNO WN UNKNO WN UNKNO WN
Requi red 2G Capab ility EDGE EDGE EDGE EDGE EDGE
89 90 91 92 93
Downlink Downlink Downlink Downlink Downlink
BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND BACKGR OUND
7200000 10100000 13900000 21000000 27900000
HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM HO_TO_GSM_SHALL_ NOT_BE_PERFORM
Note: Rows without RAB index are all NA.
2-14
02 (2009-06-30)
RAN Handover
3 Intra-Frequency Handover Algorithms
Intra-Frequency Handover Algorithms
3.1 Intra-Frequency Handover Procedure

The intra-frequency handover procedure is divided into three phases: handover measurement, handover decision, and handover execution. After the UE transits to the CELL_DCH state in connected mode during a call, the RNC sends a MEASUREMENT CONTROL message to instruct the UE to take measurements and report the measurement event results. The MEASUREMENT CONTROL message carries the following information: Event trigger threshold Hysteresis value Event trigger delay time Neighboring cell list
Upon the reception of an event report from the UE, the RNC makes a handover decision and performs the corresponding handover, as shown in Figure 3-1. Figure 3-1 Intra-frequency handover procedure
3.2 Intra-Frequency Handover Measurement

In the measurement phase, the UE takes measurements according to the MEASUREMENT CONTROL message received from the RNC. When the event triggering conditions are met, the UE sends measurement reports to the RNC according to the rules defined in the MEASUREMENT CONTROL message.
Issue 02 (2009-06-30)
3-1
RAN Handover
3.2.1 Intra-Frequency Handover Measurement Quantities

Intra-frequency handover uses Ec/No or RSCP of the CPICH as the measurement value. Intra-frequency handover measurement events can be configured through the parameter IntraFreqMeasQuantity. The UE performs layer 3 filtering on measurement values before it decides measurement events and sends measurement reports. The measurement model, as shown in Figure 3-2, is defined in 3GPP25.302. Figure 3-2 shows the position of layer 3 filtering in the measurement procedure. Figure 3-2 Measurement model in the WCDMA system
Figure 3-2 also shows the measurement points of the model, where

A: measurement value of the physical layer B: measurement value obtained after layer-1 filtering. The value is weighted by the layer 3 filtering coefficient. C: measurement value obtained after layer 3 filtering. This value is controlled by the higher layer. Filtering coefficient C is applicable to event reports and periodic reports. C': another measurement value. C' and C are measured in the same way. D: measurement report information (message) of Uu or Iub transmission. Parameters (a) include the layer 3 filtering system and Parameters (b) include the measurement report configuration.
The calculation is based on the following formula: Fn = (1 - ) x Fn-1 + x Mn

Fn: measurement value obtained after the nth filtering Fn-1: measurement value obtained after the (n-1)th filtering Mn: measurement value of the nth physical layer = 1/2(k/2): k is determined by the parameter which is the layer 3 filtering coefficient of intra-frequency handover measurement.
When is set to 1, k = 0 and layer 3 filtering is not performed.
3.2.2 Intra-Frequency Handover Measurement Events

In intra-frequency handover, the UE reports measurement results to the RNC through event reporting.
3-2
02 (2009-06-30)
RAN Handover
Event 1A
Description A primary CPICH enters the reporting range. This indicates that the quality of a cell is close to the quality of the best cell in the active set. A relatively high combined gain can be achieved when the cell is added to the active set. A primary CPICH leaves the reporting range. This indicates that a cell has a lower quality than the best cell in the active set. The cell has to be deleted from the active set. A non-active primary CPICH becomes better than an active primary CPICH. This indicates that the quality of a cell is better than the quality of the worst cell in the active set. The RNC replaces a cell in the active set with a cell in the monitored set. The best cell changes. RAN10.0 provides the solution to the issue of how to add an HSUPA cell in a DCH active set to an E-DCH active set. Event 1J is added to the 3GPP protocol. This event is triggered when a non-active E-DCH but active DCH primary CPICH becomes better than an active E-DCH primary CPICH.
1B
1C
1D 1J
Triggering of Event 1A
Event 1A is triggered under the following condition: 10 x Log(MNew) + CIONew W x 10 x Log( H1a/2)

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

IntraRelThdFor1ACSVP IntraRelThdFor1ACSNVP IntraRelThdFor1APS
Issue 02 (2009-06-30)
3-3
RAN Handover
For the PS and CS combined services, the threshold for CS services is used. For the single signaling connection of the UE, the threshold for CS services is used.
H1a represents 1A hysteresis, the hysteresis value of event 1A
Figure 3-3 shows the triggering of event 1A. In this procedure, the default parameter values are used. If the signal quality of a cell that is not in the active set is higher than Th1A for a period of time specified by TrigTime1A (that is, Time to trigger in Figure 3-3), the UE reports event 1A. Th1A = (CPICH Ec/No of the best cell in the active set) - (reporting range for event 1A)

If Weighted factor > 0, then Th1A = (general signal quality of all the cells in the active set) - (reporting range for event 1A). Reporting range for event 1A is equal to the value of IntraRelThdFor1ACSVP, IntraRelThdFor1ACSNVP, or IntraRelThdFor1APS.
Figure 3-3 Triggering of event 1A
A: signal quality curve of the best cell in the active set B: signal quality curve of a cell in the monitored set C: curve of Th1A
Triggering of Event 1B
Event 1B is triggered under the following condition: 10 x Log(Mold) + CIOold W x 10 x Log(

NB
M
i 1
) + (1-W) x 10 x Log(MBest) - (R1b+H1b/2)
MOld is the measurement value of the cell that becomes worse. CIOOld is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the best cell in the active set.
3-4
02 (2009-06-30)
RAN Handover

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

IntraRelThdFor1BCSVP IntraRelThdFor1BCSNVP IntraRelThdFor1BPS

For the PS and CS combined services, the threshold for CS services is used. If the UE currently has only signaling connections, the threshold for CS services is used.
H1b is the hysteresis value of event 1B, which is determined by the parameter Hystfor1B.
Configuration rule and restriction

The value of IntraRelThdFor1BCSNVP has to be larger than that of IntraRelThdFor1ACSNVP. The value of IntraRelThdFor1BCSVP has to be larger than that of IntraRelThdFor1ACSVP. The value of IntraRelThdFor1BPS has to be larger than that of IntraRelThdFor1APS.
Figure 3-4 shows the triggering of event 1B. In this procedure, the default parameter values are used. Figure 3-4 Triggering of event 1B
Issue 02 (2009-06-30)
3-5

RAN Handover
A: signal quality curve of the best cell in the active set B: signal quality curve of the best cell in the monitored set C: curve of Th1B
Th1B = (CPICH Ec/No of the best cell in the active set) - (reporting range for event 1B) where

Reporting range for event 1B is equal to the value of IntraRelThdFor1BCSVP, IntraRelThdFor1BCSNVP, or IntraRelThdFor1BPS. If Weight > 0, then Th1B = (general signal quality of all the cells in the active set) (reporting range for event 1B).
If the signal quality of a cell in the active set is lower than Th1B for a period of time specified by TrigTime1B (Time to trigger in the figure), the UE reports event 1B.
Triggering of Event 1C
Event 1C is triggered under the following condition: 10 x Log(MNew) + CIONew 10 x Log(MInAS) + CIOInAS + H1c/2

MNew is the measurement value of the cell in the reporting range. CIONew is the cell individual offset value of the cell in the reporting range. It is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the best cell in the active set. MInAS is the measurement value of the worst cell in the active set. H1c is the hysteresis value of event 1C, which is determined by the parameter Hystfor1C.
Figure 3-5 shows the triggering of event 1C. In this procedure, the default parameter values are used. Figure 3-5 Triggering of event 1C
A: signal quality curve of the best cell in the active set B: signal quality curve of a cell in the active set
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 02 (2009-06-30)
3-6
RAN Handover

C: signal quality curve of the worst cell in the active set D: signal quality curve of a cell in the monitored set E: curve of Th1C
Th1C = (CPICH Ec/No of the worst cell in the active set) + (hysteresis/2) where
Hysteresis is equal to the value of Hystfor1C.
If the signal quality of a cell not in the active set is higher than Th1C for a period of time specified by TrigTime1C (Time to trigger in the figure), the UE reports event 1C, as shown in the figure. The UE reports event 1C for qualified cells after the number of cells in the active set reaches the maximum value. The maximum number of cells in the active set can be set by the MaxCellInActiveSet parameter.
Triggering of Event 1D
Event 1D is triggered under the following condition: 10 x Log(MNotBest) + CIONotBest 10 x Log(MBest) + CIOBest + H1d/2

MNotBest is the measurement value of a cell that is not the best cell. CIONotBest is equal to the sum of CIO and CIOOffset, which is the offset between the cell in the reporting range and the best cell in the active set. MBest is the measurement value of the best cell in the active set. CIOBest is the cell individual offset value of the best cell. This parameter is not used for event 1D. H1d is the hysteresis value of event 1D, which is determined by the parameter Hystfor1D.
Figure 3-6 shows the triggering of event 1D. In this procedure, the default parameter values are used. Figure 3-6 Triggering of event 1D
Issue 02 (2009-06-30)
3-7

RAN Handover
A: signal quality curve of the best cell in the active set B: signal quality curve of a cell in the active set or the monitored set C: curve of Th1D Hysteresis is equal to the value of Hystfor1D.
If the signal quality of a cell not in the active set is higher than Th1D for a period of time specified by TrigTime1D (Time to trigger in the figure), the UE reports event 1D.
Triggering of Event 1J
Event 1J is triggered under the following condition: 10 x Log(MNew) + CIONew 10 x Log(MInAS) + CIOInAS + H1j/2

MNew is the measurement result of the cell not in the E-DCH active set but in the DCH active set. CIONew and CIOInAS refer to the offset of each cell. MInAS is the measurement result of the cell in the E-DCH active set with the lowest measurement result. H1J is the hysteresis parameter for event 1J and is determined by Hystfor1J. If the measurement result is CPICH-Ec/No, MNew and MInAS are expressed as ratios. If the measurement result is CPICH-RSCP, MNew and MInAS are expressed in mW.
Figure 3-7 Triggering of event 1J
A: signal quality curve of a cell in the E-DCH active set B: signal quality curve of the worst cell in the E-DCH active set C: signal quality curve of a cell not in the E-DCH active set but included in DCH active set D: signal quality curve of a cell not in the E-DCH active set but included in DCH active set
In Figure 3-7, the hysteresis and the cell individual offsets for all cells equal 0.
3-8
02 (2009-06-30)
RAN Handover
The first measurement report is sent when primary CPICH D becomes better than primary CPICH B. The "cell measurement event result" of the measurement report contains the information of primary CPICH D and CPICH B. On the assumption that the E-DCH active set has been updated after the first measurement report (E-DCH active set is now primary CPICH A and primary CPICH D), the second report is sent when primary CPICH C becomes better than primary CPICH A. The "cell measurement event result" of the second measurement report shows that primary CPICH C is better than primary CPICH A in quality. The following parameters need to be set on the RNC LMT:

Hystfor1J: hysteresis of event 1F TrigTime1J: time to trigger event 1J PeriodMRReportNumfor1J: number of periodic reports for event 1J ReportIntervalfor1J: report interval for event 1J after change to the periodic report HO_INTRA_FREQ_RPRT_1J_SWITCH: measurement control switch for event 1J. When the switch is ON, the UE version is R6 and event 1J is included in the intra-frequency measurement control message.
After receiving the intra-frequency measurement report from the UE, the RNC decides whether to go to the execution phase, depending on the information in the report.
3.2.3 Intra-Frequency Handover Neighboring Cell Combination Algorithm

After the active set is updated, the RNC updates the neighboring cell list by using the neighboring cell combination algorithm according to the status of the active set. This list includes the new intra-frequency, inter-frequency, and inter-RAT neighboring cells. The combination methods of intra-frequency handover, inter-frequency handover, and inter-RAT handover are the same. If the radio link of the Drift RNC (DRNC) is added to the active set, the Source RNC (SRNC) buffers the intra-frequency, inter-frequency, and inter-RAT neighboring cell lists of the DRNC until the radio link of the DRNC is released. The neighboring cell combination result is contained in the MEASUREMENT CONTROL message and sent to the UE, which instructs the UE to perform intra-frequency, inter-frequency, and inter-RAT measurement and handover procedures. The number of inter-frequency neighboring cells is configured as follows:

A maximum of 32 intra-frequency neighboring cells are configured. A maximum of 32 single-carrier inter-frequency neighboring cells are configured. A maximum of 64 multi-carrier inter-frequency neighboring cells are configured. A maximum of 32 inter-RAT neighboring cells are configured.
Neighboring Cell Combination Switch

HO_MC_NCELL_COMBINE_SWITCH is the neighboring cell combination switch.
If the switch is set to ON, measurement objects are chosen from the neighboring cells of all the cells in the active set.
Issue 02 (2009-06-30)
3-9
RAN Handover
If the switch is set to OFF, measurement objects are chosen from the neighboring cells of the best cell.
HO_MC_NCELL_COMBINE_SWITCH is set to ON by default.
Description of the Neighboring Cell Combination Algorithm

After obtaining the intra-frequency neighboring cells of each cell in the active set, the RNC calculates the union neighboring cell set of the intra-frequency cells, which is referred as Sall, by using the following method. This method can also be used to generate the Sall of inter-frequency or inter-RAT cells.

The intra-frequency, inter-frequency, and inter-RAT neighboring cells of each cell in the current active set are obtained. The RNC sequences the cells in the active set in descending order of CPICH Ec/No according to the latest measurement report (event 1A, 1B, 1C, or 1D) from the UE. The best cell is based on event 1D, whereas other cells are based on the latest measurement report. The cells in the active set are added to Sall. The neighboring cells of the best cell in the active set are added to Sall. NprioFlag (the flag of the priority) and Nprio (the priority of the neighboring cell), which are set for each neighboring cell, are used to change the order of adding the neighboring cells to Sall.

When NprioFlag is switched to FALSE, NPrio is cleared. When NprioFlag is switched to TRUE, NPrio is set simultaneously.
The neighboring cells of other cells in the active set are added to Sall in descending order by CPICH Ec/No values of these cells in the active set. The neighboring cells of the same cell in the active set are added according to Nprio and the number of repeated neighboring cell is recorded.
If there are more than 32 intra-frequency neighboring cells in Sall, delete the repeated neighboring cells whose number in Sall is less. The top 32 neighboring cells are grouped into the final Sall. If there are more than 64 (multi-carrier) or 32 (single-carrier) inter-frequency neighboring cells in Sall, the top 64 or 32 neighboring cells are grouped into the final Sall.
3.3 Intra-Frequency Handover Decision and Execution

The intra-frequency handover decision and execution procedure depends on the different measurement events that the RNC receives.
3.3.1 Decision and Execution

Table 3-1 lists different types of intra-frequency handover decision and execution based on different events.
3-10
02 (2009-06-30)
RAN Handover
Table 3-1 Intra-frequency handover decision and execution Event 1A Decision and Execution When receiving an event 1A report, the RNC decides whether to add a cell. For event 1A, the UE can report more than one cell in the event list in one measurement report. These cells are in the list of the MEASUREMENT CONTROL message, and they are sequenced in descending order of measurement quantity. For the cells in the list, the RNC adds the radio link to the active set only if the number of cells in the active set does not reach the maximum value. This operation is not required if the number of cells in the active set reaches a specified value. 1B When receiving an event 1B report, the RNC decides whether to delete a cell. For event 1B, if there is more than one radio link in the active set, the RNC decides whether to delete a radio link. This operation is not required if there is only one radio link in the active set. 1C When receiving an event 1C report, the RNC decides whether to change the worst cell. For event 1C, the UE reports a list that contains good cells and the cells to be replaced, and sequences the cells in descending order by measurement quantity. After receiving the list from the UE, the RNC replaces the bad cells in the active set with the good cells in the list. 1D As stipulated in related protocols, an event 1D report includes information about only one cell. This cell can be listed in an active set or a monitored set. The RNC learns that the quality of this cell is better than that of the serving cell and takes one of the following actions: If the reported cell is in the active set, the RNC decides whether to change the best cell or reconfigure measurement control. If the reported cell is in the monitored set, then:
If the number of cells in the active set has not reached the maximum value, the RNC adds the cell to the active set. If the number of cells in the active set has reached the maximum value, the RNC replaces the worst cell in the active set with the reported cell. The best cell is changed to the reported cell.
The RNC determines whether the intra-frequency hard handover scenarios are applicable. For detailed information, see 2.1 Handover Types. If any scenario is applicable, the RNC performs an intra-frequency hard handover. 1J When receiving an event 1J report with information about the good cells and the cells to be replaced, the RNC proceeds as follows: If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the uplink of the cell where event 1J is triggered is reconfigured to E-DCH. If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet, the RNC searches the measurement report for the non-serving E-DCH with the lowest measured quality in the E-DCH active set. Then, the uplink of the cell where event 1J is triggered is reconfigured from DCH to E-DCH.
Issue 02 (2009-06-30)
3-11
RAN Handover
Minimum Quality Threshold for Soft Handover

When receiving an event 1A, 1C, or 1D report, the RNC adds a target cell to the active set only when the CPICH Ec/No of the target cell is higher than the absolute threshold SHOQualmin.
SHO: soft handover
Switch for Cross-Iur Intra-Frequency Handover

If the RRC connection has been set up but the Radio Bearers (RBs) have not, whether a cross-Iur soft handover can be executed is determined by HO_MC_SIGNAL_IUR_INTRA_SWITCH of the SET CORRMALGOSWITCH parameter. Only if the switch is set to ON, can the cross-Iur soft handover be executed.
3.3.2 Rate Reduction After an SHO Failure

If the radio link addition for a soft handover fails, the rate reduction is triggered for R99 NRT (Non Real Time) services to increase the probability of a successful soft handover.
Estimation Procedure for Rate Reduction

If the RNC receives a 1A, 1C, or 1D measurement report, the RNC tries to add the corresponding cell to the active set. If the addition fails, the RNC performs the estimation procedure for rate reduction.
3-12
02 (2009-06-30)
RAN Handover
Figure 3-8 Estimation procedure for rate reduction
1.
The RNC evaluates whether the measurement quantity of the cell failing to be admitted meets the condition of rate reduction.
If the condition is met, the RNC performs a rate reduction process for the access service immediately, as described in the next section Procedure of Rate Reduction Execution. If the condition is not met, the RNC performs the next step (Step 2). Mnew is the CPICH Ec/No measurement value of the cell failing to be admitted. Mbest_cell is the CPICH Ec/No measurement value of the best cell in the active set. RelThdForDwnGrd is configured through the parameter Relative threshold of SHO failure.
The condition of rate reduction is as follows: Mnew > Mbest_cell - RelThdForDwnGrd

2.
The RNC evaluates whether the number of SHO failures in the cell exceeds the Threshold number of SHO failure. If the number of SHO failures in the cell is smaller than the ShoFailNumForDwnGrd:

If the timer has not been started, the RNC starts it. If the timer has been started, the RNC increments the SHO failure counter by one.
The timer length is set through the parameter ShoFailPeriod. The SHO failure counter of a cell is used to record the number of SHO failures in this cell. For each UE, the RNC records the number of SHO failures in three cells at most. For SHO failures in any other cells, the RNC does not record the number. Before the SHO failure evaluation timer expires, no action is taken and the RNC waits for the next measurement report period. When the SHO failure evaluation timer expires, the RNC sets the SHO failure counter of the corresponding cell to 0 and ends the evaluation.
Issue 02 (2009-06-30)
3-13
RAN Handover
If the number of SHO failures in the cell is larger than or equal to the parameter ShoFailNumForDwnGrd, the RNC performs a rate reduction process for the access service,
Procedure of Rate Reduction Execution

Figure 3-9 Procedure of rate reduction execution
2.
The RNC performs a rate reduction process for the access service. The method of determining the access rate after the rate reduction is the same as that described in Rate Negotiation of Load Control Parameter Description. After the rate reduction succeeds, the RNC immediately attempts to add this cell to the active set without measurement: If the cell succeeds in admitting the UE, the RNC adds the radio link and sets the SHO failure counter of the cell to 0 and ends the execution. If the cell fails to admit the UE, the RNC starts the Period of penalty timer for SHO failure after down rate to avoid an increase in the rate triggered by DCCC within the period. Also in this period, the RNC sets the SHO failure counter of the cell to 0 and ends the execution.
3.

If the RNC fails to perform a soft handover again, it performs the estimation procedure and the execution procedure, as previously described.
3-14
02 (2009-06-30)
RAN Handover
3.4 Intra-Frequency Handover of HSDPA

This section describes the decision and execution of intra-frequency handover, and the handover between a cell supporting the F-DPCH and a cell not supporting the F-DPCH after the introduction of HSDPA.
3.4.1 Decision and Execution of Intra-Frequency Handover

Handling of Event 1A
After receiving an event 1A report, the RNC proceeds as follows:

If the number of cells in the active set does not reach the maximum value, the RNC adds the cell to the active set. If the number of cells in the active set reaches the maximum value, the RNC does not add the radio link to the active set.
Handling of Event 1B
After receiving an event 1B report, the RNC determines whether to delete a cell.

If the cell to be deleted is not an HSDPA serving cell, the cell is directly removed. If the cell to be deleted is an HSDPA serving cell, then:
If the new best cell supports HSDPA, the new best cell is reconfigured to be an HSDPA serving cell. If the reconfiguration fails, the service is reconfigured onto DPCH. If the new best cell does not support HSDPA, the service is reconfigured onto DPCH to ensure the continuity of the service.
Handling of Event 1C
After receiving an event 1C report, the RNC decides whether to change the worst cell.

If the cell to be replaced is not an HSDPA serving cell, the cell is directly removed. If the cell to be replaced is an HSDPA serving cell, then:

If the best cell supports HSDPA, the best cell is reconfigured to be an HSDPA serving cell. If the reconfiguration fails, the service is reconfigured onto DPCH. If the best cell does not support HSDPA, the service is reconfigured onto DPCH to ensure the continuity of the service.
Handling of Event 1D
After receiving an event 1D report, the RNC proceeds as follows:
If the downlink service is carried on the HSDPA, then:
If the new best cell in the active set supports HSDPA and the HSPA hysteresis timer expires, the new best cell is reconfigured to be an HSDPA serving cell. The HSPA hysteresis timer is restarted after the serving cell change and is to avoid frequent updates at the boundary between two HSDPA cells. The timer length is specified by the parameter HspaTimerLen. Figure 3-10 shows an example of how to handle event 1D in this situation. Assume that the UE moves from HSDPA cell 1 to HSDPA cell 2, that the two cells are
Issue 02 (2009-06-30)
3-15
RAN Handover
intra-frequency neighboring cells, and that all the cells in the active set support HSDPA. The RNC updates the HSDPA serving cell according to the reported event and keeps the HSDPA serving cell consistent with the best cell.
If the new best cell in the active set does not support HSDPA, the downlink service is directed to the DCH through the reconfiguration.
Figure 3-10 Intra-frequency handover between HSDPA cells when the best cell changes
If the downlink service is carried on the DCH, then: To avoid frequent handovers at the boundary between an HSDPA cell and an R99 cell, a protection timer is used. After an intra-frequency handover, the timer starts. After this timer expires, the RNC reconfigures the service of the UE onto the HS-PDSCH of the HSDPA cell if either of the following two conditions is met:

The target cell supports HSDPA. The target cell does not support HSDPA but has a DRD neighboring cell.
The timer length is specified by the parameter ChannelRetryHoTimerLen. In the execution procedure mentioned above, CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH of the CmpSwitch parameter is used to determine whether the update of the active set and the change of the serving cell are synchronized. This switch is applicable to only R6 UEs.

If the switch is ON, the UE supports the synchronization of the update of the active set and the change of the serving cell. If the switch is OFF, the UE reconfigures the change of the serving cell by allocating physical channels after updating the active set.
During the update of the HSDPA serving cell, set the NBMMachsResetAlgoSelSwitch parameter to determine whether to reset the UE MAC-hs.
3.4.2 F-DPCH Handover Protection

If all the cells in the active set support the F-DPCH after the active set is updated and the Signaling Radio Bearer (SRB) is carried on the DCH, the timer ChannelRetryHoTimerLen starts. After this timer expires, the RNC decides whether to switch the SRB to the HS-DSCH.
3-16
02 (2009-06-30)
RAN Handover
After the UE is handed over to an HSDPA cell from an R99 cell, the D2HRetryTimer starts. After this timer expires, the RNC decides whether to switch the SRB to the HS-DSCH and whether to set up the F-DPCH.D2HRetryTimer is set through ChannelRetryHoTimerLen.
3.5 Intra-Frequency Handover of HSUPA

This section describes the decision and execution of intra-frequency handover, and the handover between E-DCHs of 10 ms TTI and 2 ms TTI after the introduction of HSUPA.
3.5.1 Decision and Execution of Intra-Frequency Handover

Handling of Event 1A
After receiving the measurement report, the RNC proceeds as follows: If the target cell supports HSUPA and the uplink service is carried on the E-DCH, then:
If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the target cell is added to both the DCH and E-DCH active sets. Otherwise, the target cell is added to only the DCH active set.
After deciding that a cell can be added to the E-DCH active set,

If the admission in the downlink fails, the cell is added to neither the E-DCH active set nor the DCH active set. It waits for the next event 1A report for retry. Otherwise, if the admission in the downlink succeeds, the RNC perform the HSUPA admission in the uplink.

If HSUPA admission in the uplink succeeds, the cell is added to the E-DCH active set and the DCH active set. If HSUPA admission in the uplink fails, the cell is added only to the DCH active set. If the DCH admission in the uplink still fails, the cell is added to neither the E-DCH active set nor the DCH active set. It waits for the next event 1A report for retry.
Handling of Event 1B
If the number of radio links in the DCH active set is larger than one, then:

If the cell to be removed is not an HSUPA serving cell, the cell is directly removed. If the cell to be removed is an HSUPA serving cell, then:

If the new best cell supports HSUPA, the new best cell is reconfigured to be an E-DCH serving cell. If the new best cell does not support HSUPA, the uplink service is redirected to the DCH through the RB reconfiguration.
If the current service is CS Voice over HSPA and the cell to be removed is an E-DCH serving cell, then:

If the new best cell supports both HSDPA and HSUPA, the cell is reconfigured to be an HS-DSCH serving cell or an E-DCH serving cell. If the new best cell supports HSDPA but not HSUPA, the current service is changed from CS Voice over HSPA to CS Voice over DCH. If there remain other HSDPA
Issue 02 (2009-06-30)
3-17
RAN Handover
services, the serving cell should be updated and the new best cell should be the HS-PDSCH serving cell.
If the new best cell supports neither HSUPA nor HSDPA, the current service is reconfigured to be CS Voice over DCH.
Whether the cells under the adjacent RNC support CS Voice over HSPA is determined by the RNC-level parameter CSVoiceoverHSPASuppInd. After the best cell of a UE changes, if the size of the DCH or E-DCH active set of the new best cell is different from those of the old best cell, the RNC removes or reconfigures radio links to adapt to the size and configuration of the new best cell.
Handling of Event 1C
When event 1C is triggered, the UE reports the event-triggered list that contains good cells and the cells to be replaced, and sequences the cells from the highest to the lowest quality according to measurement quantity. After receiving the measurement report, the RNC proceeds as follows:
If the new cell supports HSUPA, then:

If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the new cell is added to the E-DCH active set. If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet and the cell to be replaced is also included in the E-DCH active set, the new cell joins the E-DCH active set through replacement. If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet and the cell to be replaced is not included in the E-DCH active set, the new cell is added only to the DCH active set.
If the current service is CS Voice over HSPA and the cell to be removed is an E-DCH serving cell, then:

If the new best cell supports both HSDPA and HSUPA, the cell is reconfigured to be an HS-DSCH serving cell or an E-DCH serving cell. If the new best cell supports HSDPA but not HSUPA, the current service is changed from CS Voice over HSPA to CS Voice over DCH through the reconfiguration. If there remain other HSDPA services, the serving cell should be updated and the new best cell should be the HS-PDSCH serving cell. If the new best cell supports neither HSUPA nor HSDPA, the current service is reconfigured to be CS Voice over DCH. If the cell to be removed is an E-DCH serving cell, the HS-DSCH serving cell must be removed at the same time. Thus, a new E-DCH serving cell or HS-DSCH serving cell must be determined. The method is the same as that of removing the serving cell, as described in the previous section of Handling of Event 1B.
If the new cell does not support HSUPA, the cell is added to only the DCH active set.
Handling of Event 1D
If the criteria for intra-frequency hard handover are fulfilled, the RNC performs intra-frequency hard handover after receiving the event 1D report. If the criteria for intra-frequency hard handover are not fulfilled, the RNC performs intra-frequency soft handover based on the measurement report. If the uplink service is carried on the E-DCH, then:
3-18
02 (2009-06-30)
RAN Handover
If the new best cell in the active set supports HSUPA and the HSPA hysteresis timer expires, the E-DCH serving cell becomes the best cell. The HSPA hysteresis timer is restarted after the cell change. The length of the HSPA hysteresis timer is defined by the HspaTimerLen parameter.
The HSPA hysteresis timer is defined to reduce the probability of the frequent change of the serving cell, which is caused by the frequent change of the best cell. Thus, the serving cell cannot change before the timer expires. The ping-pong effect has been considered in the triggering conditions of event 1D; and therefore, the timer is set to 0 by default. This means that the serving E-DCH cell is updated immediately when the best cell changes. The uplink service is directed to the DCH through the reconfiguration. If the reconfiguration fails, the service is still carried on the E-DCH. The UE is connected to the new best cell only on the DPCH.
If the new best cell in the active set does not support HSUPA,
If the uplink service is carried on the DCH, then:
If the new best cell in the active set supports HSUPA or the new best cell has an HSUPA-capable and DRD-applicable neighboring cell, and if the uplink service is suitable to be mapped to HSUPA, the RNC starts a timer whose length is defined by the ChannelRetryHoTimerLen parameter.
After this timer expires, the service is directed to the E-DCH through the reconfiguration. If the admission fails during the reconfiguration, the timer whose length is defined by the ChannelRetryTimerLen parameter is started. Periodic retries of DCH to E-DCH are performed.
If the new best cell in the active set does not support HSUPA, the uplink service is still carried on the DCH.
If the current service is CS Voice over HSPA, then:

If the new best cell supports both HSUPA and HSDPA, the cell is reconfigured to be an HSPA serving cell. Otherwise, the service is changed from CS Voice over HSPA to CS Voice over DCH through the reconfiguration.
Handling of Event 1J
When event 1J is triggered, the UE reports the event-triggered list that contains good cells and the cells to be replaced, and sequences the cells from the highest to the lowest quality according to measurement quantity. After receiving the measurement report, the RNC proceeds as follows:
If the current number of cells in the E-DCH active set is smaller than the value of MaxEdchCellInActiveSet, the cell where event 1J is triggered is reconfigured to E-DCH. If the current number of cells in the E-DCH active set is equal to the value of MaxEdchCellInActiveSet, the RNC searches the measurement report for the non-serving Cell_EDCH with the lowest measured quality in the E-DCH active set. Then, the uplink of the cell where event 1J is triggered is reconfigured from DCH to E-DCH, and the uplink of CELL-EDCH is reconfigured from E-DCH to DCH.
In addition, for BE services, if the current bit rate is higher than HsupaBeShoRateThd, the bandwidth on the E-DCH is reduced to this parameter value.
Issue 02 (2009-06-30)
3-19
RAN Handover
3.5.2 Handover Between E-DCHs of 10 ms TTI and 2 ms TTI

For HSUPA, 2 ms TTI and 10 ms TTI are applicable but not all the cells support 2 ms TTI. When both 2ms-TTI-capable and 2ms-TTI-incapable cells exist in a network, a UE may undergo handovers between E-DCHs of 10 ms TTI and 2 ms TTI. Only when all the cells in the E-DCH active set support 2 ms TTI can the services be configured to the E-DCH with 2 ms TTI. If any cell in the E-DCH active set does not support 2 ms TTI, the services are configured on the E-DCH with 10 ms TTI. The detailed principles are as follows:
When the uplink service is carried on the E-DCH with 2 ms TTI, if a cell that supports only 10 ms TTI is to be added to the E-DCH active set, the source cell undergoes a radio bearer reconfiguration to 10 ms TTI. A soft handover to the target cell is performed. Upon each handover, if a radio link needs to be added, removed, or replaced, the RNC judges whether all the cells in the E-DCH active set and the UE support 2 ms TTI.
If they all support 2 ms TTI and the uplink service is currently carried on the E-DCH with 10 ms TTI, the RNC reconfigures the service to the E-DCH with 2 ms TTI.

If the reconfiguration fails, a timer is started for periodic retries to the E-DCH with 2 ms TTI. If the handover is performed before the timer expires, the timer is stopped. After the handover, the RNC decides whether to start the timer, based on the handover result.
3.6 Signaling Procedures for Intra-Frequency Handover

3.6.1 Intra-NodeB Intra-Frequency Soft Handover Signaling Procedure
This section describes the signaling procedure for intra-frequency soft handover within a NodeB. Figure 3-11 shows the procedure for intra-frequency soft handover when the UE moves from one cell to another cell within the same NodeB. Figure 3-11 Procedure for intra-NodeB intra-frequency soft handover
3-20
02 (2009-06-30)
RAN Handover
The connections involved in the intra-NodeB intra-frequency softer handover change are as follows:

Before the softer handover, only cell 1 is connected to the UE. During the softer handover, both cell 1 and cell 2 are connected to the UE. Before the softer handover, only cell 2 is connected to the UE. Cell 1 is removed from the active set.
Figure 3-12 Signaling procedure for intra-NodeB intra-frequency soft handover
Issue 02 (2009-06-30)
3-21
RAN Handover
3.6.2 Intra-RNC Inter-NodeB Intra-Frequency Soft Handover Signaling Procedure

Figure 3-13 Procedure for intra-RNC inter-NodeB intra-frequency soft handover
Before the soft handover, only NodeB 1 is connected to the UE. During the soft handover, both NodeBs are connected to the UE. After the soft handover, only NodeB 2 is connected to the UE. The active set of NodeB 1 is removed.
3-22
02 (2009-06-30)
RAN Handover
Figure 3-14 Signaling procedure for intra-RNC inter-NodeB intra-frequency soft handover
Issue 02 (2009-06-30)
3-23
RAN Handover
3.6.3 Inter-RNC Intra-Frequency Soft Handover Signaling Procedure

Figure 3-15 Procedure for inter-RNC intra-frequency soft handover
Before the soft handover, the UE is connected to NodeB 1 and NodeB 2. After the SRNC makes a soft handover decision, it sets up a connection between NodeB 3 under another RNC and the UE, and releases the connection between NodeB 1 and the UE.
3-24
02 (2009-06-30)
RAN Handover
Figure 3-16 Signaling procedure for inter-RNC intra-frequency soft handover
Issue 02 (2009-06-30)
3-25
RAN Handover
3.6.4 Intra-RNC Inter-NodeB Intra-Frequency Hard Handover Signaling Procedure

Figure 3-17 Procedure for intra-RNC inter-NodeB intra-frequency hard handover
3-26
02 (2009-06-30)
RAN Handover
Figure 3-18 Signaling procedure for intra-RNC inter-NodeB intra-frequency hard handover
In Figure 3-18, NodeB 1 is the source NodeB, and NodeB 2 is the target NodeB.
3.6.5 Inter-RNC Intra-Frequency Hard Handover Signaling Procedure

Figure 3-19 shows the procedure for intra-frequency hard handover when a UE moves from one NodeB in an SRNC to another NodeB in a DRNC.
Issue 02 (2009-06-30)
3-27
RAN Handover
Figure 3-19 Procedure for inter-RNC intra-frequency hard handover
3-28
02 (2009-06-30)
RAN Handover
Figure 3-20 Signaling procedure for inter-RNC intra-frequency hard handover
As shown in Figure 3-20, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
Issue 02 (2009-06-30)
3-29
RAN Handover
4 Inter-Frequency Handover Algorithms
Inter-Frequency Handover Algorithms
4.1 Inter-Frequency Handover Procedure

The inter-frequency handover procedure is divided into four phases: handover triggering, handover measurement, handover decision, and handover execution. The procedure varies according to handover types.
4.1.1 Coverage- or QoS-based Inter-Frequency and Inter-RAT Handover Procedure

The procedure for the coverage- or QoS-based inter-frequency handover is the same as that for the coverage- or QoS-based inter-RAT handover, as shown in Figure 4-1.
Issue 02 (2009-06-30)
4-1
RAN Handover
Figure 4-1 Coverage- or QoS-based inter-frequency and inter-RAT handover procedure
In the triggering phase For the coverage-based handover, the RNC requests the UE to measure through an inter-frequency measurement control message. If the CPICH Ec/No or CPICH RSCP of the current cell is lower than the corresponding threshold, the UE reports event 2D. For the QoS-based handover, if the service quality of the current cell deteriorates, the Link Stability Control Algorithm makes a handover measurement decision.
In the measurement phase The RNC sends an inter-frequency measurement control message to the UE, requesting the NodeB and UE to start the compressed mode. The RNC also requests the UE to perform the inter-frequency or inter-RAT handover measurement . In this phase, the method of either periodical measurement report or event-triggered measurement report can be used.
In the decision phase After the UE reports event 2B, the RNC performs the handover. Otherwise, the UE periodically generates measurement reports, and the RNC makes a decision after evaluation.
In the execution phase The RNC executes the handover procedure.
4-2
02 (2009-06-30)
RAN Handover
4.1.2 Load-based Inter-Frequency Handover Procedure

The load-based inter-frequency handover suits best in the case of the co-sited cells covering the same area.
In the triggering phase The Load Reshuffling (LDR) module directly determines whether the current cell is overloaded and whether an inter-frequency handover needs to be performed. The LDR module provides the target cell information for the current cell, and the RNC performs the handover procedure.
In the decision phase The RNC decides to trigger an inter-frequency blind handover if the conditions are met.

If the inter-frequency blind handover can be triggered, the RNC enters the decision phase. If the inter-frequency blind handover cannot be triggered, the RNC does not perform the handover.
After the inter-frequency handover is triggered, the RNC chooses a decision algorithm according to whether the conditions of direct blind handover are met.
In the execution phase The RNC performs the blind handover according to the decision result.
4.1.3 Speed-based Inter-Frequency Handover Procedure

Figure 4-2 shows speed-based inter-frequency handover procedure. For HCS speed estimation, see HCS Handover Algorithms.
Issue 02 (2009-06-30)
4-3
RAN Handover
Figure 4-2 Speed-based inter-frequency handover procedure
In the triggering phase The RNC receives the handover request according to the HCS speed estimation. The handover based on HCS speed estimation is of two types: handover from the macro cell to the micro cell and handover from the micro cell to the macro cell. For different types of handover, the RNC acts differently.
In the measurement and decision phases
If the handover is performed from a macro cell to a micro cell, the RNC sends an inter-frequency measurement control message. After the UE reports event 2C, the RNC performs the handover decision. For inter-RAT handover, the UE reports event 3C. If the handover is performed from a micro cell to a macro cell, the RNC directly performs blind handover, ignoring the measurement procedure.
In the execution phase The RNC initiates a handover procedure.
If the handover is performed from a micro cell to a macro cell and the target cell of blind handover is configured (through the parameter BlindHOFlag), the RNC performs blind handover to the target cell. If the blind handover fails or the handover is performed from a macro cell to a micro cell, the RNC starts the inter-frequency (or inter-RAT) measurement procedure. If the inter-frequency measurement mode is employed, the RNC performs the
4-4
02 (2009-06-30)
RAN Handover
inter-frequency handover procedure to the cell with the best quality after receiving event 2C from the UE.
4.2 Inter-Frequency Handover Measurement

In the measurement phase of inter-frequency handover, the UE takes measurement according to the MEASUREMENT CONTROL message received from the RNC. When the measurement report conditions are met, the UE sends measurement reports to the RNC according to the rules defined in the MEASUREMENT CONTROL message.
4.2.1 Inter-Frequency Handover Measurement Switches

Some switches are important for inter-frequency handover because they decide whether the handover can be performed successfully. These switches are the parameter values of Handover algorithm switch in the command SET CORRMALGOSWITCH, as described below. HO_INTER_FREQ_RPRT_2D2F_SWITCH: The switch decides whether the RNC enables the active set quality measurement.

If the switch is set to ON, the RNC allows the UE to perform the active set quality measurement. If the switch is set to OFF, the RNC forbids the UE to perform the active set quality measurement. The switch is set to ON by default.
HO_MC_SIGNAL_SWITCH: The switch decides when the RNC performs the active set signal quality measurement.

If the switch is set to ON, the RNC initiates the active set quality measurement after the RRC connection setup is completed (before the RB setup). If the switch is set to OFF, the RNC initiates the active set quality measurement after the RB setup is completed. The switch is set to OFF by default.
HO_INTER_FREQ_HARD_HO_SWITCH: The switch decides whether to enable the inter-frequency handover measurement.

If the switch is set to ON, the RNC enables the inter-frequency handover measurement and the load-based inter-frequency handover. If the switch is set to OFF, the RNC disables the inter-frequency handover measurement. The switch is set to ON by default.
HO_MC_MEAS_BEYOND_UE_CAP_SWITCH: The switch decides whether the neighboring cell will be sent in the inter-frequency measurement control message when the frequency of the neighboring cell is not included in the measurement capability of the UE. The reported measurement capability of the UE is not the same as the actual measurement capability of the UE. Measurement capability at some frequencies may not be reported due to the limitation of the version of UE protocol.
If the switch is set to ON, the RNC sends the inter-frequency measurement control message with the neighboring cell, whose frequency is not included in the measurement capability of the UE.
Issue 02 (2009-06-30)
4-5
RAN Handover
If the switch is set to OFF, the RNC sends the inter-frequency measurement control message without the neighboring cell, whose frequency is not included in the measurement capability of the UE. The switch is set to OFF by default.
4.2.2 Inter-Frequency Handover Measurement Report Modes

The event-triggered measurement report mode applies to various handovers. The periodical measurement report mode applies to only load-based and speed-based inter-frequency handovers.

The measurement report mode of inter-frequency handover is configured through the parameter InterFreqReportMode. The interval of the measurement reports is configured through the parameter PrdReportInterval.
The advantage of periodical measurement report is that if the handover fails, the RNC reattempts the handover to the same cell after receiving the periodical measurement report from the UE. This increases the probability of the success of inter-frequency handover. Based on the measurement control message received from the RNC, the UE periodically reports the measurement quality of the target cell. Then, based on the measurement report, the RNC makes the handover decision and performs handover.
4.2.3 Inter-Frequency Handover Measurement Quantity

Measurement quantities vary according to the types of inter-frequency handover.
In inter-frequency handover based on coverage, event 2B/2D/2F or periodical measurement takes both CPICH Ec/No and RSCP as measurement quantities.

In the triggering phase, events 2D and 2F that correspond to CPICH_Ec/No and CPICH_RSCP are sent from the UE. In the measurement phase, event 2B or periodical measurement that correspond to CPICH_Ec/No and CPICH_RSCP are sent from the UE. In inter-frequency handover based on coverage, the system delivers both CPICH Ec/No and RSCP as measurement quantities to perform 2D/2F measurement. To restrict the types of reported measurement quantities, set the measurement triggering threshold to the minimum value. For example, if the reporting of event 2D of CS service Ec/No is allowed but that of RSCP is restricted, you can set InterFreqCSThd2DRSCP to the minimum value, that is, 115.
In inter-frequency handover based on QoS, event 2B or periodical measurement takes both CPICH Ec/No and RSCP as measurement quantities. In inter-frequency handover based on speed, event 2C takes only CPICH Ec/No as measurement quantity. In inter-frequency handover based on load, CPICH RSCP is measured.
The UE performs the layer 3 (L3) filtering of measurement values before it judges the measurement event and sends the measurement report. The inter-frequency measurement model is similar to the intra-frequency measurement model. For detailed information, see3.2.1 Intra-Frequency Handover Measurement Quantities for Intra-Frequency Handover. The parameter InterFreqFilterCoef is the filtering coefficient of the inter-frequency measurement value, which is configured on the basis of inter-frequency handover types.
4-6
02 (2009-06-30)
RAN Handover
4.2.4 Inter-Frequency Handover Measurement Events

When the measurement thresholds are reached, the UE reports the events to the RNC to trigger related handover procedures. Table 4-1 describes the measurement events involved in inter-frequency handover. Table 4-1 Measurement events involved in inter-frequency handover Event 2D 2F 2B 2C 1F Description The estimated quality of the currently used frequency is below a certain threshold. The estimated quality of the currently used frequency is above a certain threshold. The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold. The estimated quality of a non-used frequency is above a certain threshold. A Primary CPICH becomes worse than an absolute threshold.
Frequency Quality Estimation for Inter-Frequency Handover

In inter-frequency handover, the reporting criteria of measurement events are based on the frequency quality estimation. The parameter Weight for used frequency specifies the frequency weighing factor that is used to measure the quality of the current frequency. This parameter is used for all event-triggered inter-frequency measurements but not for periodical inter-frequency measurements. The event-triggered measurement events include events 2D, 2F, 2B, and 2C. For detailed information on the quality estimation formula, see section "Frequency Quality Estimate" in 3GPP TS 25.331.
After the conditions of event 2D are fulfilled and maintained until the TimeToTrig2D is reached, the UE sends the event 2D measurement report message. Event 2D is triggered on the basis of the following formula: QUsed TUsed2d - H2d/2

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

InterFreqCSThd2DEcN0 InterFreqR99PsThd2DEcN0 InterFreqHThd2DEcN0 InterFreqCSThd2DRSCP InterFreqR99PsThd2DRSCP InterFreqHThd2DRSCP
Issue 02 (2009-06-30)
4-7
RAN Handover
The parameters InterFreqHThd2DRSCP and InterFreqHThd2DEcN0 are valid only when the switch HO_ALGO_OVERLAY_SWITCH is set to ON. Otherwise, the PS domain services will take InterFreqR99PsThd2DEcN0 or InterFreqR99PsThd2DRSCP as a measurement event threshold.

For the PS and CS combined services, the threshold is set to the higher one of CS or PS services. If the UE has only signaling connections currently, the thresholds for CS services are used.
H2d is the event 2D hysteresis value set through the parameter HystFor2D.
Triggering of Event 2F
After the conditions of event 2F are fulfilled and maintained until the parameter TimeToTrig2F is reached, the UE reports the event 2F measurement report message. Event 2F is triggered on the basis of the following formula: QUsed TUsed2f + H2f/2 where

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

InterFreqCSThd2FEcN0 InterFreqCSThd2FRSCP InterFreqR99PsThd2FEcN0 InterFreqR99PsThd2FRSCP InterFreqHThd2FEcN0 InterFreqHThd2FRSCP The parameters InterFreqHThd2FEcN0 and InterFreqHThd2FRSCP are valid only when the switch HO_ALGO_OVERLAY_SWITCH is set to ON. Otherwise, the PS domain services will take InterFreqR99PsThd2FEcN0 or InterFreqR99PsThd2FRSCP as a measurement event threshold. For the PS and CS combined services, the threshold is set to the higher one of CS or PS services. If the UE has only signaling connections currently, the thresholds for CS services are used.
H2f is the event 2F hysteresis value set through the parameter HystFor2F.
Conditions of event 2F are as follows: TUsed2d - H2d/2 < TUsed2f + H2f/2, for example, (InterFreqCSThd2DEcN0HystFor2D/ 2) < (InterFreqCSThd2FEcN0+ HystFor2F / 2).
Triggering of Event 2B
After the conditions of event 2B are fulfilled and maintained until the parameter TimeToTrig2B is reached, the UE reports the event 2B measurement report message. Event 2B is triggered on the basis of the following formula: QNoused TNoused2b + H2b/2
4-8
02 (2009-06-30)
RAN Handover
QUsed TUsed2b - H2b/2 where

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

TargetFreqCsThdEcN0 TargetFreqCsThdRscp TargetFreqR99PsThdEcN0 TargetFreqR99PsThdRscp TargetFreqHThdEcN0 TargetFreqHThdRscp
TUsed2b is the absolute quality threshold of the cell that uses the current frequency.
TUsed2b is set in the following way:
Based on the service type and measurement quantity, this threshold can be configured through one of the following parameters: If event 2D with the CPICH RSCP value is received by the RNC:
TUsed2b of event 2B with the CPICH RSCP value can be: UsedFreqCSThdRSCP UsedFreqR99PsThdRSCP UsedFreqHThdRSCP
TUsed2b of event 2B with the CPICH Ec/No value is configured as the maximum value 0 dB. According to 3GPP specifications, TUsed2b of event 2B with the CPICH Ec/No value should be configured as the maximum value 0 dB. If the event 2F with the CPICH Ec/No value is received by the RNC and TUsed2b of event 2B with the CPICH Ec/No value is modified, TUsed2b is reset to 0 dB.
If event 2D with the CPICH Ec/No value is received by the RNC:
TUsed2b of event 2B with the CPICH Ec/No value can be: UsedFreqCSThdEcN0 UsedFreqR99PsThdEcN0 UsedFreqHThdEcN0 TUsed2b of event 2B with the CPICH RSCP value is configured as the maximum value 25 dBm. According to 3GPP specification, TUsed2b of event 2B with the CPICH RSCP value should be configured as the maximum value 25 dBm. If event 2F with the CPICH RSCP value is received by the RNC and TUsed2b of event 2B with the CPICH RSCP value is modified, TUsed2b is reset to 25 dBm.
Issue 02 (2009-06-30)
4-9
RAN Handover
For the PS and CS combined services, the threshold is set to the higher one of CS or PS services. If the UE has only signaling connections currently, the thresholds for CS services are used. The parameters TargetFreqHThdEcN0, TargetFreqHThdRscp, UsedFreqHThdRSCP, and UsedFreqHThdEcN0 are valid only when the switch HO_ALGO_OVERLAY_SWITCH is set to ON. Otherwise, the PS domain R99 services take UsedFreqR99PsThdEcN0, UsedFreqR99PsThdRSCP, TargetFreqR99PsThdEcN0, or TargetFreqR99PsThdRscp as a measurement event threshold.
After the conditions of event 2C are fulfilled and maintained until the parameter TrigTime2C is reached, the UE reports the event 2C measurement report message.. Event 2C is triggered on the basis of the following formula: QNoused TNoused2c + H2c/2 where

QNoused is the measured quality of the cell that uses the other frequencies. TNoused2c is the absolute quality threshold of the cell that uses the other frequencies, namely, InterFreqNCovHOThdEcN0. H2c is the event 2C hysteresis value Hystfor2C.
After the conditions of event 1F are fulfilled and maintained until the parameter TrigTime1F is reached, the UE reports the event 1F measurement report message. Event 1F is triggered on the basis of the following formula: 10LogMOld T1f - H1f/2 where

MOld is the measurement value of the cell that becomes worse. T1f is an absolute threshold. It is set through the parameter IntraAblThdFor1FRSCP or IntraAblThdFor1FecNo. H1f is the event 1F hysteresis value set through the parameter Hystfor1F.
4.2.5 Inter-Frequency Handover Neighboring Cell Combination Algorithm

See section 3.2.3 Intra-Frequency Handover Neighboring Cell Combination Algorithm.
4.2.6 Inter-Frequency Handover Compressed Mode

Compressed Mode control is a mechanism whereby certain idle periods are created in radio frames during which the UE can perform measurements on other frequencies. If the UE needs to measure the pilot signal strength of an inter-frequency 3G or 2G cell and has one frequency receiver only, the UE must use the compressed mode.
4-10
02 (2009-06-30)
RAN Handover
Each physical frame can provide three to seven timeslots for the inter-frequency or inter-RAT cell measurement.
Compressed Mode Switches

The parameter DlSFLimitCMInd decides whether to start the DL compressed mode according to the parameter LimitCMDlSFThd.
If DlSFLimitCMInd = True,

When the downlink spreading factor is smaller than or equal to the parameter LimitCMDlSFThd, the compressed mode is disabled. When the downlink spreading factor is greater than the parameter LimitCMDlSFThd, the compressed mode is enabled.
If DlSFLimitCMInd = False and the compressed mode is not limited,
CMCF_UL_PRECFG_TOLERANCE_SWITCH under CmcfSwitch determines whether to set up the RB of SF4 during the preparation for SF/2 compressed mode.
If CMCF_UL_PRECFG_TOLERANCE_SWITCH is set to ON, the RB of SF4 can be set up during the preparation for SF/2 compressed mode. The inter-frequency or inter-RAT handover measurement, however, cannot be triggered, because SF4 cannot be compressed to SF2. If CMCF_UL_PRECFG_TOLERANCE_SWITCH is set to OFF, the RB of SF4 cannot be set up during the preparation for SF/2 compressed mode. The system can trigger the SF/2 compressed mode measurement.
CMCF_WITHOUT_UE_CAP_REPORT_SWITCH under CmcfSwitch determines whether to use the frequencies beyond the range of UE reports on the compressed mode measurement. The compressed mode is of the following types:

Spreading factor reduction (SF/2) High layer scheduling
Which type of compressed mode to use is automatically decided by the RNC on the basis of the spreading factor used in the uplink or the downlink.
When the downlink spreading factor is greater than or equal to the parameter DlSFTurnPoint, the SF/2 approach is preferred. Otherwise, the high layer scheduling is used. When the uplink spreading factor is greater than or equal to the parameter UlSFTurnPoint, the SF/2 approach is preferred. Otherwise, the high layer scheduling is used.
To initiate the high layer scheduling, set the following two switches:
If the algorithm switch CMCF_DL_HLS_SWITCH in the command SET CORRMALGOSWITCH is set to ON, the DL high-layer scheduling for the compressed mode is allowed. If the algorithm switch CMCF_UL_HLS_SWITCH in the command SET CORRMALGOSWITCH is set to ON, the UL high-layer scheduling for the compressed mode is allowed.
Issue 02 (2009-06-30)
4-11
RAN Handover
Measurement Timer Length

When the UE takes a long time to perform the inter-frequency measurement in compressed mode, the radio network will be affected. To avoid the influence, the RNC stops the inter-frequency measurement and disables the compressed mode if no inter-frequency handover occurs upon expiry of the inter-frequency measurement timer.

The timer is specified by InterFreqMeasTime in inter-frequency handover based on coverage or HCS. The timer is specified by InterRATMeasTime in inter-RAT handover based on coverage, load, or service. The timer is specified by DLQosMcTimerLen or ULQosMcTimerLen in inter-RAT handover based on downlink or uplink QoS respectively.
4.3 Inter-Frequency Handover Decision and Execution

This section describes the procedure for decision and execution of different types of inter-frequency handover.
4.3.1 Coverage- and QoS-based Inter-Frequency Handover Decision and Execution

The coverage- and QoS-based inter-frequency handovers are categorized into two types according to the following two measurement report modes: periodical measurement report mode and event-triggered measurement report mode. Each mode corresponds to a different decision and execution procedure.
Coverage- and QoS-based Inter-Frequency Handover in Periodical Measurement Report Mode

After receiving the periodical measurement report of the inter-frequency cell, the RNC starts the following decision procedures: 1. Decide whether both the CPICH Ec/No value and CPICH RSCP value of the pilot signal of the target cell meet the requirement of inter-frequency handover. The evaluation formula is listed below: Mother_Freq + CIOother_Freq Tother_Freq + H/2 where
Mother_Freq is the CPICH Ec/No or CPICH RSCP measurement value of the target cell reported by the UE. Both of the two measurement values of the inter-frequency cell must satisfy the formula. CIOother_Freq is the cell individual offset value of the target cell. It is equal to the sum of CIO and CIOOffset. Tother_Freq is the decision threshold of inter-frequency hard handover. Based on the service type and measurement quantity, this threshold can be configured through one of the following parameters: TargetFreqCsThdEcN0 TargetFreqCsThdRscp TargetFreqR99PsThdEcN0
4-12
02 (2009-06-30)
RAN Handover
TargetFreqR99PsThdRscp TargetFreqHThdEcN0 TargetFreqHThdRscp These thresholds are the same as the quality threshold of event 2B..
H is the inter-frequency hard handover hysteresis value set through the parameter HystForPrdInterFreq.
2. 3. 4.
Start the hard handover time-to-trigger timer, which is configured through the parameter TimeToTrigForPrdInterFreq. If Mother_Freq + CIOother_Freq < Tother_Freq - H/2, stop the timer. Select the cells in sequence, that is, from high quality cells to low quality ones, to initiate inter-frequency handover in the cells where the hard handover time-to-trigger timer expires.
Each cell in the measurement report shall be evaluated as mentioned previously. When the hard handover time-to-trigger timers of more than one cell expire at the same time, the latest measurement report is used for selecting the best inter-frequency neighboring cell for handover. For example, the cell with the highest CPICH RSCP in the latest measurement report is selected, as shown in Figure 4-3. Figure 4-3 Selecting the cell with the highest CPICH RSCP
Coverage- and QoS-based Inter-Frequency Handover in Event-Triggered Measurement Report Mode

After receiving the event 2B measurement reports of CPICH RSCP and CPICH Ec/No of the inter-frequency cell, the RNC starts the following procedure: 1. 2. Add all the pilot cells that trigger event 2B to a cell set and arrange the cells according to the measurement quality of CPICH_Ec/No in descending order. Select the cells in turn from the cell set to perform inter-frequency handover.
Issue 02 (2009-06-30)
4-13
RAN Handover
4.3.2 Load-based Inter-Frequency Handover Decision and Execution

The LDR algorithm may trigger an inter-frequency blind handover based on load. The following describes the procedure for handover decision and execution.
Load-based Inter-Frequency Handover Decision

1. 2. The LDR algorithm learns that a cell is overloaded and provides target cells and the UE with low priority for handover. The RNC determines to trigger an inter-frequency blind handover.
If the UE is not in soft handover state, the UE directly performs inter-frequency blind handover based on load. If the UE is in soft handover state, the UE operates based on the following conditions:
If the HO_ALGO_LDR_ALLOW_SHO_SWITCH is set to ON, the RNC determines whether the cell that triggers LDR is the best cell.

If this cell is the best cell, the RNC initiates an intra-frequency measurement for inter-frequency blind handover based on load. If this cell is not the best cell, the RNC does not initiate an inter-frequency blind handover based on load.
If the HO_ALGO_LDR_ALLOW_SHO_SWITCH is set to OFF, the RNC does not initiate an inter-frequency blind handover based on load.
Load-based Inter-Frequency Handover Execution

The inter-frequency cells with the same coverage area have the same CPICH RSCP values. By measuring the CPICH RSCP of the cell, the quality of the cells with the same coverage area can be determined, which increases the probability of successful blind handover. 1. 2. The RNC initializes the timer of intra-frequency measurement for blind handover. The timer is specified by internal algorithm and need not be configured. The RNC initiates a periodical intra-frequency measurement. The measurement report mode is set to periodical report.

The reporting period is BlindHOIntrafreqMRInterval. The number of measurement reports is BlindHOIntrafreqMRAmount. The intra-frequency handover measurement quantity is CPICH RSCP. The list of measured cells contains only the cells that trigger LDR.
3.
After receiving from the UE the intra-frequency measurement reports for conditional blind handover, the RNC checks whether the following condition is met: CPICH RSCP of the cell in the measurement report >= BlindHOQualityCondition

If the condition is met, the RNC increments the counter of the number of intra-frequency measurement reports for blind handover by 1. If the condition is not met, the RNC does not perform a blind handover to the cell that triggers LDR and stops intra-frequency measurement for blind handover.
4.
When the counter reaches the value of BlindHOIntrafreqMRAmount, the RNC initiates a blind handover to the cell that triggers LDR.
4-14
02 (2009-06-30)
RAN Handover
If the counter does not reach this value, the RNC waits for the next intra-frequency measurement report from the UE. 5. If the timer of intra-frequency measurement for blind handover expires, the RNC does not perform a blind handover to the cell that triggers LDR and stops intra-frequency handover measurement for blind handover.
If the inter-frequency handover based on coverage or QoS is triggered, the RNC stops the intra-frequency measurement for conditional blind handover.
4.3.3 Speed-based Inter-Frequency Handover Decision and Execution

This section covers the decision and execution of micro cell to macro cell, as well as that of macro cell to micro cell.
Decision and Execution of Micro Cell to Macro Cell Handover

If the handover is performed from a micro cell to a macro cell and a target cell for blind handover is configured, the RNC performs a blind handover to the target cell. If the blind handover fails, the RNC continues to perform a blind handover. The blind handover procedure is as follows: 1. The RNC selects the neighboring cells with a lower HCSPrio to generate a cell set. The neighboring cells whose frequency band is not supported by the UE are not taken into account. If there are neighboring cells with several candidate frequencies, then the RNC selects one of the frequencies randomly. The RNC searches for neighboring cells for blind handover according to BlindHOFlag. The RNC chooses a neighboring cell whose BlindHOQualityCondition value is the smallest for blind handover. The RNC determines whether the target cell supports the current service. If the target cell does not support the current service, the RNC does not perform the blind handover.
2. 3. 4.
Decision and Execution of Macro Cell to Micro Cell Handover

If the blind handover fails or the handover is performed from a macro cell to a micro cell, the RNC starts the inter-frequency (or inter-RAT) measurement procedure. If the inter-frequency measurement mode is employed, the RNC starts the following procedure: 1. 2. Add all the pilot cells that trigger event 2C to a cell set and arrange the cells according to the measurement quality in descending order. Select the cells in turn from the cell set to perform inter-frequency handover.
4.3.4 Blind Handover Decision and Execution Based on Event 1F

When there is only one cell in the active set, the RNC performs inter-frequencey blind handover after receiving event 1F. 1. The RNC gets the actual best cell from event 1F. If the quality of the best cell meets the Blind handover condition (BlindHOQualityCondition), the RNC gets neighboring cells for blind handover of the best cell, and filtrate the cells which belong to the frequency bands that UEs don't support. If there are multiple neighboring cells for blind handover, the RNC chooses the cell with the lowest value of BlindHOQualityCondition and the cell must support all the current
2.
Issue 02 (2009-06-30)
4-15
RAN Handover
services of UE. When there are multiple such cells, the RNC choose the neighboring cell for blind handover randomly.
4.3.5 Inter-Frequency Anti-Ping-Pong Algorithm

After an inter-frequency handover based on coverage or an inter-frequency blind handover based on event 1F occurs, the RNC starts the anti-ping-pong algorithm to prevent frequent switching between inter-frequency handovers triggered by different causes. The inter-frequency anti-ping-pong algorithm is as follows: 1. When a coverage-based inter-frequency handover or an inter-frequency blind handover based on event 1F occurs, the RNC starts the timer specified by IFAntiPingpangTimerLength for the UE. When a non-coverage-based inter-frequency handover is triggered, first, the RNC determines whether the timer specified by IFAntiPingpangTimerLength expires.

2.
If the timer does not expire, the RNC cancels the handover. If the timer expires, the RNC performs the handover.
4.3.6 Inter-Frequency Handover Retry

If an inter-frequency handover based on event-triggered measurement report mode fails, the RNC initiates the inter-frequency handover attempt according to an inter-frequency retry algorithm.

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

Retry timer:PeriodFor2B Maximum number of retry times:AmntOfRpt2B
For the inter-frequency handover based on speed, the following two parameters determine the retry period and the maximum number of retry times:

Retry timer:PeriodFor2C Maximum number of retry times:AmntOfRpt2C
4.4 Inter-Frequency Handover of HSDPA

Inter-frequency handover can be triggered on the basis of coverage, load, and Hierarchical Cell Structure (HCS). Some types of data cards of HSDPA terminals cannot support compressed mode (CM). Therefore, the parameter HsdpaCMPermissionInd is used to enable or disable CM for HSDPA users. The following describes the three possible scenarios for inter-frequency handover.
4-16
02 (2009-06-30)
RAN Handover
Scenario 1: Inter-Frequency Handover from an HSDPA Cell to an R99 Cell

As shown in Figure 4-4, when the UE moves from cell 1 (an HSDPA cell) to cell 2 (an R99 cell), the inter-frequency handover conditions are met and event 2B is triggered. The RNC makes a handover decision for HSDPA services according to the neighboring cell measurement report, and reconfigures the service onto the DPCH of cell 2. Figure 4-4 Inter-frequency handover from an HSDPA cell to an R99 cell
Scenario 2: Inter-Frequency Handover from an R99 Cell to an HSDPA Cell

As shown in Figure 4-5, when the UE moves from cell 2 (an R99 cell) to cell 1 (an HSDPA cell), the inter-frequency handover conditions are met and event 2B is triggered. The RNC hands over the UE to the DPCH first, and then to the HS-PDSCH if the service can be carried on the HS-PDSCH. Figure 4-5 Inter-frequency handover from an R99 cell to an HSDPA cell
Issue 02 (2009-06-30)
4-17
RAN Handover
Scenario 3: Inter-Frequency Handover Between HSDPA Cells

As shown in Figure 4-6, when the UE moves from cell 1 (an HSDPA cell) to cell 2 (an HSDPA cell) and the inter-frequency handover conditions are met, the UE is handed over from cell 1 to cell 2. The target cell becomes the new serving HS-PDSCH cell. If the serving or target cell is in load congestion when the UE performs a serving cell update for inter-frequency or inter-RAT handover, the service is reconfigured from the HS-PDSCH to the DPCH. The hard handovers of an HSDPA cell is the same as those of an R99 cell. Figure 4-6 Inter-frequency handover between HSDPA cells
D2H Penalty Timer for Inter-Frequency Handover of HSDPA

To avoid frequent handovers in a multi-carrier area with an HSDPA cell and an R99 cell, a protection timer is used. The timer length is specified by the parameter HspaTimerLen. After an inter-frequency handover, the timer starts. If the target cell supports HSDPA, or if it does not support HSDPA but has a DRD neighboring cell, the RNC can reconfigure the service of the UE onto the HS-PDSCH of the HSDPA cell only after this timer expires.
F-DPCH Handover Protection

After the UE is handed over to an HSDPA cell from an R99 cell, the D2HRetryTimer starts. After this timer expires, the RNC decides whether to switch the SRB to the HS-DSCH and whether to set up the F-DPCH.D2HRetryTimer is set through the parameter ChannelRetryHoTimerLen.
4-18
02 (2009-06-30)
RAN Handover
4.5 Inter-Frequency Handover of HSUPA

Inter-frequency handover can be triggered on the basis of coverage, load, and Hierarchical Cell Structure (HCS). The introduction of HSUPA does not affect the triggering conditions and decisions of these types of inter-frequency handover. The parameter HsupaCMPermissionInd decides whether the compressed mode (CM) can be used on HSUPA.

If the parameter is set to Permit, the UE in E-DCH state performs measurement. If the parameter is set to Limited, the reconfiguration from E-DCH to DCH is required before CM is activated because HSUPA does not support CM. If the parameter is set to BasedOnUECap, the RNC determines whether to perform E2D procedure before CM activated based on the UE capability.
During the execution phase, whether to reconfigure the services from E-DCH to DCH depends on the HSUPA capability of the target cell. After the handover, a decision must be made about whether to reconfigure the services from DCH to E-DCH. Table 4-2 describes the three possible scenarios for inter-frequency handover. Table 4-2 Scenarios for inter-frequency handover Scenario Scenario 1 Description Inter-frequency handover from an HSUPA cell to another HSUPA cell

The UE moves from one HSUPA cell to another HSUPA cell. Event 2B is triggered.
Scenario 2
Inter-frequency handover from an HSUPA cell to a non-HSUPA cell

The UE moves from an HSUPA cell to a non-HSUPA cell. Event 2B is triggered.
Scenario 3
Inter-frequency handover from a non-HSUPA cell to an HSUPA cell

The UE moves from a non-HSUPA cell to an HSUPA cell. Event 2B is triggered.
If the current service is CS Voice over HSPA and the target cell supports both HSDPA and HSUPA, the target cell is reconfigured as an HSPA serving cell. Otherwise, the service of CS Voice over HSPA must first be reconfigured as CS Voice over DCH. Whether the target RNC supports CS Voice over HSPA is determined by the parameter CSVoiceOverHspaSuppInd.
Scenario 1: Inter-Frequency Handover from an HSUPA Cell to Another HSUPA Cell

Assume that the UE moves from HSUPA cell 1 to HSUPA cell 2 and that the two cells are inter-frequency neighboring cells, as shown in Figure 4-7.
Issue 02 (2009-06-30)
4-19
RAN Handover
Figure 4-7 Inter-frequency handover from an HSUPA cell to another HSUPA cell
During this procedure, event 2B is triggered. The HSUPA admission request is made for the target cell by the RNC.

If the request is accepted, the handover is performed through the physical channel reconfiguration message. If the request is rejected, the RB reconfiguration is implemented, and the services on the E-DCH are reconfigured for the DCH.
Scenario 2: Inter-Frequency Handover from an HSUPA Cell to a Non-HSUPA Cell

Assume that the UE moves from HSUPA cell 1 to non-HSUPA cell 2 and that the two cells are inter-frequency neighboring cells, as shown in Figure 4-8. Figure 4-8 Inter-frequency handover from an HSUPA cell to a non-HSUPA cell
During this procedure, event 2B is triggered, and the target cell does not support HSUPA. The DCH admission request is made for the target cell. After the request is accepted, the RB reconfiguration is implemented, and the services on the E-DCH are reconfigured for the DCH.
4-20
02 (2009-06-30)
RAN Handover
Scenario 3: Inter-Frequency Handover from a Non-HSUPA Cell to an HSUPA Cell

Assume that the UE moves from non-HSUPA cell 1 to HSUPA cell 2 and that the two cells are inter-frequency neighboring cells, as shown in Figure 4-9. Figure 4-9 Inter-frequency handover from a non-HSUPA cell to an HSUPA cell
During this procedure, event 2B is triggered. The inter-frequency handover on DCH is performed, and the HSUPA admission request is made for the target cell by the RNC. After the request is accepted, the RB reconfiguration is implemented, and the services on the DCH are reconfigured for the E-DCH.
D2H Penalty Timer for Inter-Frequency Handover of HSUPA

If the UE moves from a non-HSUPA or HSUPA cell to a target cell after the inter-frequency handover, and the target cell does not support HSUPA but has a neighboring cell that supports HSUPA DRD, the RNC starts a timer defined by the ChannelRetryHoTimerLen parameter. After the timer expires, the services are reconfigured on the E-DCH. If the reconfiguration fails, periodical retry from DCH to E-DCH is triggered.
4.6 Signaling Procedures for Inter-Frequency Handover

4.6.1 Inter-Frequency Handover Within One RNC
Figure 4-10 shows the inter-frequency handover for a UE that moves from NodeB 1 to NodeB 2 within one RNC. Before the handover, the UE sets up a connection to NodeB 1.After the handover, the UE sets up a connection to NodeB 2.
Issue 02 (2009-06-30)
4-21
RAN Handover
Figure 4-10 Inter-frequency handover between NodeBs within one RNC
Figure 4-11 Signaling procedure for inter-frequency handover between NodeBs within one RNC
4-22
02 (2009-06-30)
RAN Handover
As shown in Figure 4-11, NodeB 1 is the source NodeB, whereas NodeB 2 is the target NodeB. From step 1 through step 6, a new connection is set up. From step 7 through step 9, the old connection is released.
4.6.2 Inter-Frequency Handover Between RNCs

Figure 4-12 shows the signaling procedure for inter-frequency hard handover for a UE that moves from a NodeB to another NodeB between the RNCs. Before the handover, the UE sets up a connection to NodeB 1.After the handover, the UE sets up a connection to NodeB 2. Figure 4-12 Inter-frequency hard handover between the RNCs
Issue 02 (2009-06-30)
4-23
RAN Handover
Figure 4-13 Signaling procedure for inter-frequency hard handover between the RNCs
NodeB 1 is the source NodeB, whereas NodeB 2 is the target NodeB. From step 1 through step 10, a new connection is set up. From step 11 through step 13, the old connection is released.
4-24
02 (2009-06-30)
RAN Handover
5 Inter-RAT Handover Algorithms
Inter-RAT Handover Algorithms
5.1 3G-to-2G Handover Procedure

The 3G-to-2G handover procedure is divided into four phases: handover triggering, handover measurement, handover decision, and handover execution. The procedure varies according to handover types.
5.1.1 Coverage-based 3G-to-2G Handover Procedure

For details, see 4.1.1 Coverage- or QoS-based Inter-Frequency and Inter-RAT Handover Procedure.
5.1.2 Load-based 3G-to-2G Handover Procedure

Figure 5-1 Load-based 3G-to-2G handover procedure
In the triggering phase
Issue 02 (2009-06-30)
5-1
RAN Handover
When the load of the 3G cell that the UE accesses is higher than the related threshold, the Load Reshuffling (LDR) algorithm makes a handover decision. For detailed information of the LDR, see Load Reshuffling in the Load Control Parameter Description.
In the measurement phase The RNC enables the compressed mode and starts the inter-RAT handover measurement. In the decision phase After the UE reports event 3C, the RNC makes a handover decision. In the execution phase The RNC initiates a handover procedure.
5.1.3 Service-based 3G-to-2G Handover Procedure

Figure 5-2 Service-based 3G-to-2G handover procedure
In the triggering phase When a service is established, the RNC requests the handover to the GSM based on the service type and service handover indicator assigned by the CN.
In the measurement phase The RNC enables the compressed mode and starts the inter-RAT handover measurement. In the decision phase After the UE reports event 3C, the RNC makes a handover decision. In the execution phase The RNC initiates a handover procedure.
5.1.4 Speed-based 3G-to-2G Handover Procedure

For details, see 4.1.3 Speed-based Inter-Frequency Handover Procedure.
5-2
02 (2009-06-30)
RAN Handover
5.2 3G-to-2G Handover Measurement

5.2.1 3G-to-2G Handover Measurement Switches
The 3G-to-2G handover measurement switches are specified by the sub-parameters of HoSwitch.

HO_MC_SIGNAL_SWITCH and HO_INTER_FREQ_RPRT_2D2F_SWITCH
HO_INTER_RAT_PS_OUT_SWITCH: The switch decides whether the RNC will initiate inter-RAT measurement to trigger inter-RAT handover of the PS domain from the UTRAN.ON HO_INTER_RAT_CS_OUT_SWITCH: The switch decides whether the RNC will initiate inter-RAT measurement to trigger inter-RAT handover of the CS domain from the UTRAN.
5.2.2 3G-to-2G Handover Measurement Report Modes

For coverage or QoS based UMTS-to-GSM handover, there are two measurement report modes: event-triggered measurement report mode and periodical measurement report mode. For load or service-based 3G-to-2G handover, the measurement report is event-triggered only.

The measurement report mode is configured through the parameter InterRatReportMode. In periodical measurement report mode, the UE sends measurement reports periodically to the RNC according to the values of the report interval. The report interval needs to be configured through the parameter InterRATPeriodReportInterval.
5.2.3 3G-to-2G Handover Measurement Quantity

There is a choice of multiple measurement quantities used to measure the CPICH quality.
In coverage-based UMTS-to-GSM handover,
Event 2D/2F or periodical measurement takes both CPICH Ec/No and RSCP as measurement quantities. In coverage-based inter-RAT handover, the system delivers both CPICH Ec/N0 and CPICH RSCP for 2D/2F measurement. To deliberately limit the types of measurement quantity, you can set the corresponding threshold of the limited measurement quantity to the minimum value. For example, if event 2D of CS service Ec/No can be reported but the RSCP cannot, the parameter InterRATCSThd2DRSCP is set to the minimum value, that is, -115.
The event 3A measurement quantity is set through the parameter MeasQuantityOf3A.
In QoS-based 3G-to-2G handover, the event 3A measurement quantity is set through the parameter UsedFreqMeasQuantityForQos3A.
The unused frequencies refer to GSM frequency signals, and the unused frequency measurement quantity refers to GSM RSSI. The UE performs the layer 3 (L3) filtering of measurement values before it judges the measurement event and sends the measurement report. The inter-RAT measurement model is similar to the intra-frequency measurement model. For detailed information, see 3.2.1 Intra-Frequency Handover Measurement Quantities for Intra-Frequency Handover. The
Issue 02 (2009-06-30)
5-3
RAN Handover
smoothed filter coefficient for layer 3 inter-RAT measurement is InterFreqFilterCoef, and the smoothed filter coefficient for events 2D and 2F is FilterCoefOf2D2F.
5.2.4 3G-to-2G Handover Measurement Events

When the measurement thresholds are reached, the UE reports the events to the RNC to trigger the related handover procedures. Table 5-1 Events in inter-RAT handover Event Event 2D Event 2F Event 3A Description The estimated quality of the currently used frequency is below a certain threshold. The estimated quality of the currently used frequency is above a certain threshold. The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold. The estimated quality of other system is above a certain threshold.
Event 3C
3G-to-2G Handover Frequency Quality Estimation

In 3G-to-2G handover, the report criteria of event 3A are based on the quality estimation of the frequency. The parameter WeightForUsedFreq is the frequency weighting factor used to calculate the quality of the current frequency. This parameter is used for event 3A only. For detailed information about the quality estimation formula, see section "Frequency Quality Estimate" in 3GPP TS 25.331.
When the conditions for event 2D are met and maintained in time-to-trigger specified by the parameter TimeToTrig2D, the UE sends the measurement report of event 2D. Event 2D is triggered on the basis of the following formula: QUsed TUsed2d - H2d/2 where

QUsed is the measurement value of the cell at the currently used frequency. TUsed2d is the absolute quality threshold of the cell at the currently used frequency. Based on the service type and measurement quantity, this threshold can be configured through the following parameters:

InterRATCSThd2DEcN0 InterRATR99PsThd2DEcN0 InterRATHThd2DEcN0 InterRATCSThd2DRSCP InterRATR99PsThd2DRSCP
5-4
02 (2009-06-30)
RAN Handover

InterRATHThd2DRSCP
H2d is the event 2D hysteresis value set through the parameter HystFor2D. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
When the conditions for event 2F are met and maintained in time-to-trigger specified by TrigTime2F, the UE sends the measurement report of event 2F. Event 2F is triggered on the basis of the following formula: QUsed TUsed2f + H2f/2 where

QUsed is the measurement value of the cell at the currently used frequency. TUsed2f is the absolute quality threshold of the cell at the currently used frequency. Based on the service type and measurement quantity, this threshold can be configured through the following parameters:

InterRATCSThd2FEcN0 InterRATR99PsThd2FEcN0 InterRATHThd2FEcN0 InterRATCSThd2FRSCP InterRATR99PsThd2FRSCP
InterRATHThd2FRSCP H2f is the event 2F hysteresis value set through the parameter HystFor2F. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
Triggering of Event 3A
When the conditions for event 3A are met and maintained in time-to-trigger specified by TrigTime3A the UE sends the measurement report of event 3A. Event 3A is triggered on the basis of the following formula: QUsed TUsed - H3a/2 and MOtherRAT + CIOOtherRAT TOtherRAT + H3a/2 where
QUsed is the measurement value of the cell at the currently used frequency. TUsed is the absolute quality threshold of the cell that uses the current frequency. Based on the service type and measurement quantity in the coverage-based handover, TUsed can be configured through the following parameters

UsedFreqCSThdEcN0 UsedFreqCSThdRSCP UsedFreqHThdEcN0 UsedFreqHThdRSCP UsedFreqR99PsThdEcN0 UsedFreqR99PsThdRSCP
Issue 02 (2009-06-30)
5-5
RAN Handover
In the uplink QoS-based handover, based on the measurement quantity (CPICH Ec/No or RSCP), TUsed is configured as the maximum value according to 3GPP specifications, as described below:

If the measurement quantity is CPICH Ec/No, TUsed is configured as the maximum value 0 dB. If the measurement quantity is CPICH RSCP, TUsed is configured as the maximum value 25 dBm. If the measurement quantity is CPICH Ec/No, TUsed is configured as the maximum value 0 dB. If the measurement quantity is CPICH RSCP, based on the service type , TUsed can be configured as one of the following sums:
In the downlink QoS-based handover:

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

TargetRatCsThd TargetRatR99PsThd TargetRatHThd
H3a is 3A hysteresis, the hysteresis value of event 3A. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
When the conditions for event 3C are met and the delay requirement specified by the TrigTime3C parameter can be satisfied, the UE sends the measurement report of event 3C. Event 3C is triggered on the basis of the following formula: MOtherRAT + CIOOtherRAT TOtherRAT + H3c/2 where

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

TargetRatCsThd
InterRATNCovHOPSThd H3c is 3C hysteresis, the hysteresis value of event 3C. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
5-6
02 (2009-06-30)
RAN Handover
5.2.5 3G-to-2G Handover Neighboring Cell Combination Algorithms

For details, see 3.2.3 Intra-Frequency Handover Neighboring Cell Combination Algorithm.
5.2.6 3G-to-2G Handover Compressed Mode

For details, see 4.2.6 Inter-Frequency Handover Compressed Mode.
5.2.7 BSIC Verification Requirements for 2G Cells

During inter-RAT measurement, it is recommended that the UE report the 2G cell after the Base Transceiver Station Identity Code (BSIC) of the cell is verified. This greatly enhances the reliability of handover. The related parameter is BSICVerify.
5.3 3G-to-2G Handover Decision and Execution

5.3.1 Coverage and QoS-based UMTS-to-GSM Handover Decision and Execution
The coverage-based and QoS-based 3G-to-2G handover is categorized into two types according to the following two measurement report modes: periodical measurement report mode and event-triggered measurement report mode. Each mode corresponds to a different decision and execution procedure.
Coverage- and QoS-based 3G-to-2G Handover in Periodical Measurement Report Mode

After receiving the periodical measurement report of GSM cells, the RNC performs the following decision and execution procedures: 1. Decide whether the quality of 2G cells meets the conditions of inter-RAT handover. The evaluation formula is listed below: Mother_RAT + CIOother_RAT Tother_RAT + H/2 where

Mother_RAT is the measurement result of inter-RAT handover received by the RNC. CIOother_RAT is the cell individual offset value of the target cell. It is equal to the sum of CIO and CIOOffset. Tother_RAT is the decision threshold of inter-RAT hard handover. Based on the service type and measurement quantity, this threshold can be configured through the following parameters: TargetRatCsThd TargetRatR99PsThd TargetRatHThd H is the inter-RAT handover hysteresis value set through HystforInterRAT. For the PS and CS combined services, one or more handover thresholds for CS services are used.
Issue 02 (2009-06-30)
5-7
RAN Handover
2.
Start the evaluation of the cells that meet the quality requirement and start the time-to-trigger timer. If the measurement report meet the following formula and time-to-trigger timer does not expire, stop the time-to-trigger timer. Mother_RAT + CIOother_RAT < Tother_RAT - H/2 The length of the time-to-trigger timer is configured through the parameter TimeToTrigForVerify (with BSIC acknowledged) or the parameter TimeToTrigForNonVerify (with BSIC unacknowledged).
3.
Select the cells in sequence, that is, from high quality cells to low quality ones, to initiate 3G-to-2G handover in the cells where the handover time-to-trigger timer expires.
Coverage- and QoS-based 3G-to-2G Handover in Event-Triggered Measurement Report Mode

After receiving the event 3A measurement report of 2G cells, the RNC performs the following decision and execution procedures: 1. 2. Put all the 2G cells that trigger event 3A into a cell set and arrange the cells according to the measurement quality in descending order. Select the cells in sequence from the cell set to perform inter-RAT handover.
5.3.2 Load- and Service-based 3G-to-2G Handover Decision and Execution

The load status between the source cell and the target cell can be acquired by interchanging load information between a 3G cell and a 2G cell during the load-based and service-based 3G-to-2G handover. Thus, whether to further conduct the handover can be determined to avoid the 2G cell overload and possible handover to the congested cell.
Decision and Execution Procedure of Load- or Service-Based 3G-to-2G Handover

After receiving the event 3C measurement report of 2G cells, the RNC performs the following handover decision and execution procedure: 1. 2. Put all the 2G cells that trigger event 3C into a cell set and arrange the cells according to the measurement quality in descending order. Select the cells in sequence from the cell set.
To avoid the impact of the UE (in long-term measurement of compressed mode) on the radio network, the parameter InterRATHOAttempts is set to restrict the maximum attempts of the 3G-to-2G load-based or service-based handover. The parameter indicates the handover attempts made to the same cell or different cells. If the number of attempts exceeds the parameter value, the RNC does not initiate the handover.
Interchanging Load Information in Load- or Service-based 3G-to-2G Handover

The procedure for load information interchanging between the 3G source cell and 2G target cell is described as follows: 1. When the RNC sends a RELOCATION REQUIRED message to the 3G CN, If the switch SndLdInfo2GsmInd is set to ON, the RELOCATION REQUIRED message includes the Old BSS To New BSS Information IE that includes the load information of the 3G source cell.
5-8
02 (2009-06-30)
RAN Handover
If the switch SndLdInfo2GsmInd is set to OFF, then the RELOCATION REQUIRED message does not include the Old BSS To New BSS Information IE. 2. When the RNC receives the RELOCATION COMMAND message from the 2G CN, If the switch NcovHoOn2GldInd is set to ON, the RNC obtains the load information of the 2G target cell by reading the Inter-System Information Transparent Container IE, which is included in the RELOCATION COMMAND message.
If the 2G load is lower than CSHOOut2GloadThd (for CS service), or if the 2G load is lower than PSHOOut2GloadThd (for PS service), the RNC continues the inter-RAT handover procedure; otherwise, the RNC returns the Relocation Cancel message to the CN to cancel this inter-RAT handover and makes another handover attempt to the next candidate cell generated in the cell list based on inter-RAT measurement. If the Inter-System Information Transparent Container IE, is not included in the RELOCATION COMMAND message, the load information of the 2G target cell is not considered and this inter-RAT handover is continued.
If the switch NcovHoOn2GldInd is set to OFF, the RNC continues the inter-RAT handover procedure without considering the thresholds.
5.3.3 3G-to-2G Handover Retry

In case of inter-RAT handover failure, if the cause of the failure is not a configuration failure and the retry timer expires, the UE makes handover attempts to the cell again until the retry number exceeds the maximum retry number. The inter-RAT handover retry algorithm works in the following two signaling procedures:
Signaling Procedure for Iu Relocation

1. 2. The RELOCATION REQUIRED message is initiated on the Iu interface. If the RNC receives the RELOCATION PREPARATION FAILURE message, the inter-RAT handover fails. If the cause of the failure is one of the following configuration failure, the RNC does not make a handover retry to the cell.

Relocation Failure in Target CN/RNC or Target System, or Relocation not supported in Target RNC or Target System, or Relocation Target not allowed
Otherwise, the related retry timer for the cell is started. After the retry timer expires, the UE makes handover attempts to the cell again until the retry number exceeds the maximum retry number. 3. 4. If the RNC receives the RELOCATION COMMAND message, the handover on the Uu interface continues. If the handover succeeds or the new event 3A or 3C report is received, the periodical retry is stopped.
Signaling Procedure for Service-based Handover on the Uu Interface
For CS services or CS and PS combined services, the HANDOVER FROM UTRAN signaling procedure on the Uu interface is performed only when the handover based on CS services is made.
Issue 02 (2009-06-30)
5-9
RAN Handover
For a PS service or combined PS services, the CELL CHANGE ORDER FROM UTRAN or HANDOVER FROM UTRAN signaling procedure on the Uu interface is performed. If the HANDOVER FROM UTRAN FAILURE or CELL CHANGE ORDER FROM UTRAN FAILURE message is received, the handover on the Uu interface fails.
If the "Inter-RAT handover failure cause" in HANDOVER FROM UTRAN FAILURE message is "Configuration unacceptable", or if the "Inter-RAT change failure cause" in CELL CHANGE ORDER FROM UTRAN FAILURE message is "Configuration unacceptable", the RNC does not make a handover retry to the cell. Otherwise, the related retry timer for the cell is started. After the retry timer expires, the UE makes a handover attempt to the cell again until the retry number exceeds the maximum number. If the handover succeeds or the new event 3A or 3C report is received, the periodical retry is stopped. The retry timer and maximum retry number for coverage-based and QoS-based inter-RAT handover are:

PeriodFor3A AmntOfRpt3A
The retry timer and maximum retry number for load-based and service-based inter-RAT handover are:

PeriodFor3C AmntOfRpt3C
5.3.4 3G-to-2G Multimedia Fallback

Before the RNC performs handover for the UE that is enjoying the video phone (VP) service, the RNC initiates multimedia fallback to change the VP service to the Adaptive Multi Rate (AMR) speech service, that is, to perform the 3G-to-2G handover based on the CS AMR speech service.
Overview of Fallback Service

Compared with the traditional speech service of the GSM, the VP service of the UMTS can transmit not only speech services between the calling party and the called party, but also the images and videos captured by both parties. Since the actual implementation is limited by terminals and networks, the VP service sometimes carries only speech and may fail to transmit images or videos. In this scenario, the Service Change and Unrestricted Digital Information Fallback (SCUDIF) provides the fallback mechanism that changes a video call to a common speech call. As specified in 3GPP TS 23.172, the fallback service of the VP is categorized into the following two types:
The process of changing multimedia services back to speech services during call setup. The RNC does not take part in the process. Therefore, the detailed description of fallback process is not given hereinafter. The process of changing multimedia services back to speech services during the call.
5-10
02 (2009-06-30)
RAN Handover
Triggering of Fallback Service

Currently, the network-initiated multimedia fallback is performed only for the 3G-to-2G handover. Service changes triggered by the UEs are not supported. Fallback is initiated when both of the following occasions are met:

The RNC decides to send an inter-RAT handover request after receiving periodical measurement reports of event 1A, 3A, or 3C. The service is combined with a VP, and the "Alternative RAB Parameters" in the RAB ASSIGNMENT message is a valid AMR speech format.
Procedure of Service Change

Figure 5-3 shows the service change procedure for the 3G-to-2G handover. The network initiates the service change, that is, the RNC initiates the change from the VP service to the speech service during the call. Figure 5-3 Service change procedure for the 3G-to-2G handover in the CS domain
2. 3.
The CN sends the SRNC a RANAP RAB ASSIGNMENT REQUEST message to set up the VP service. During 3G-to-2G handover, the SRNC sends a RANAP RAB MODIFY REQUEST message to change the VP service to the AMR speech service. In the 3GPP R6 protocol, the information element (IE) Alternative RAB Configuration Request is also added to the RAB MODIFY REQUEST message, which enables the RNC to request the CN to change the VP service to the AMR speech service. The MSC initiates the Bearer Capability (BC) negotiation with the UE. After the negotiation, the RNC is requested to perform service change.
4. 5.
When the multimedia fallback ends, the RNC decides whether to perform the 3G-to-2G handover according to the current measurements reported by the UE. At the beginning of the service setup, the RNC saves the RAB parameters.
Issue 02 (2009-06-30)
5-11
RAN Handover
The CN initiates the RAB reconfiguration to request both parties to perform the multimedia fallback. The single VP service falls back to the single AMR speech service. The multi-RAB service combined with VP falls back to the multi-RAB service combined with AMR. If the multimedia fallback succeeds, that is, the video phone in the service falls back to speech successfully, the inter-RAT handover is initiated. Otherwise, the inter-RAT handover fails.
5.3.5 3G-to-2G Handover in the PS Domain with NACC

The Network Assisted Cell Change (NACC) function can efficiently reduce the delay of UMTS-to-GSM handover. PS handover is similar to the inter-RAT handover in the CS domain. Some services have requirements for the delay. If the handover takes too long, TCP may start slowly or data transmission of the service stream may be interrupted due to the overflow of the UE buffer. The introduction of NACC enables the system information exchange between different BSSs, or between BSS and RAN. Thus the inter-system delay, especially inter-system delay in PS domains, can be reduced. With NACC, the RNC sends the UE a cell change order, which contains the GSM EDGE Radio Access Network (GERAN) system information, when the 3G-to-2G handover in the PS domain is triggered. To enable the NACC function, do as follows:

Run the SET CORRMALGOSWITCH command to set HoSwitch: HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH to ON. Run the ADD GSMCELL/MOD GSMCELL command to set SuppRIMFlag to TRUE.
To enable the PS HO function, do as follows:

Run the SET CORRMALGOSWITCH command to set HoSwitch: HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH parameter to ON. Run the ADD GSMCELL/MOD GSMCELL command to set SuppPSHOFlag to TRUE.
5.4 Inter-RAT Handover of HSDPA

The switch HsdpaCMPermissionInd decides whether the compressed mode (CM) can be used on HSDPA. When the UE is handed over to a cell supporting the F-DPCH from another system and a UL or DL event 4A is reported, the RNC decides whether to change the bearing mode of TRB and SRB. If the TPC command is carried on the F-DPCH between the UE and the UTRAN, the SRB and the TRB are carried on the HS-DSCH. If a cell not supporting the F-DPCH is added to the active set, all the F-DPCHs are deleted. In addition, new DPCHs between the UE and all the cells in the active set are set up to carry the SRB and TPC commands.
5.5 Inter-RAT Handover of HSUPA

The switch HsupaCMPermissionInd decides whether the Compressed Mode (CM) can be used on HSUPA. If the current service is CS Voice Over HSPA and is handed over from a 2G cell to a 3G cell,
5-12
02 (2009-06-30)
RAN Handover
If the UE supports CS Voice Over HSPA and the target 3G RAN supports CS Voice Over HSPA, the service is configured as CS Voice over HSPA when the UE is handed over to the 3G system. Otherwise, the service is configured as CS Voice Over DCH when the UE is handed over to the 3G system.
5.6 2G-to-3G Handover

The 2G-to-3G handover is initiated by the 2G network, where the dual-mode (GSM and WCDMA) MSs are required. Both the GSM MSC and the GSM BSS must support the GSM-to-UMTS handover.
2G-to-3G Handover Penalty Algorithm

For the 2G-to-3G handover, the measurement control message is delivered through a system information broadcast of 2G when the 2G cell has a neighboring 3G cell. The dual-mode MS performs the inter-RAT measurement in idle timeslots and reports the measurement results. Based on the reported measurement values, the BSC decides whether to perform the handover to the 3G network. To avoid the ping-pong handover between 2G and 3G, the 2G-to-3G handover penalty algorithm is used. When the UE is handed over from 2G to 3G and if any CS domain service exists, the system increases the hysteresis of event 3A through the parameter InterRATPingPongHyst to prevent the UE from the ping-pong handover between 2G and 3G in the period specified by the parameter InterRATPingPongTimer.
Interchange of Load Information in 2G-to-3G Load or Service-based Handover

In 2G-to-3G handover based on load or service, the RNC can make a decision about admission considering the load information of the 3G target cell. This can avoid the worsening of the 3G system performance caused by 2G-to-3G handover based on load or service if the 3G system load is high. The procedure is described as follows: 1. When the RNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the 3G CN,
If the switch SndLdInfo2GsmInd is set to ON, the RELOCATION REQUEST ACKNOWLEDGE message includes the New BSS To Old BSS Information IE, which includes the load information of the 3G target cell. If the switch SndLdInfo2GsmInd is set to OFF, the RELOCATION REQUEST ACKNOWLEDGE message does not include the New BSS To Old BSS Information IE.
Depending on the network requirement, the 2G network decides whether to use the load information sent to the 3G network for judgment. 2. When the RNC receives the RELOCATION REQUEST message from the 3G CN,
If the 3G cell is not in the basic congestion state, the RNC continues the inter-RAT handover procedure.
Issue 02 (2009-06-30)
5-13
RAN Handover
If the 3G cell is in the basic congestion state, the RNC returns RELOCATION FAILURE message to the CN to cancel the inter-RAT handover.
For the concept of "basic congestion", see the Load Control Parameter Description.
5.7 Interoperability Between Inter-RAT Handover and Inter-Frequency Handover

During the coverage-based and QoS-based 3G-to-2G handover, the measurements on both inter-frequency and inter-RAT neighboring cells can be made, which enables the cells to provide continuous coverage and high quality. The preconditions for the measurements are as follows:

Both inter-frequency and inter-RAT neighboring cells are available. InterFreqRATSwitch is set to SIMINTERFREQRAT.
If InterFreqRATSwitch is set to:

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

When the value COEXIST_MEAS_THD_CHOICE_INTERFREQ is chosen, the inter-frequency measurement threshold for event 2D is used. When the value COEXIST_MEAS_THD_CHOICE_INTERRAT is chosen, the inter-RAT measurement threshold for event 2D is used.
5.8 Signaling Procedures for Inter-RAT Handover

5.8.1 3G-to-2G Handover in CS Domain
Figure 5-4 shows the signaling procedures for the 3G-to-2G handover in the CS domain. The 2G messages shown in Figure 5-4 are for your reference only.
5-14
02 (2009-06-30)
RAN Handover
Figure 5-4 3G-to-2G handover in the CS domain
5.8.2 3G-to-2G Handover in PS Domain

For a UE in idle mode or connected mode, if the SGSN changes with the shift of the system that the UE accesses from 3G network to 2G network, the inter-SGSN handover will be performed. The handover procedures are different in the following two cases:
When the UE is in CELL_DCH state The 3G-to-2G handover in the PS domain is triggered after the UTRAN sends a CELL CHANGE ORDER FROM UTRAN message.
When the UE is in CELL_FACH, CELL_PCH, or URA_PCH state The 3G-to-2G handover in the PS domain is triggered through the cell reselection.
The following figure shows an example of handover for the UE in CELL_FACH, CELL_PCH, or URA_PCH state. When the UE is in idle mode, the cell reselection procedure does not include the elementary procedures marked "UE CONNECTED" in Figure 5-5.
Issue 02 (2009-06-30)
5-15
RAN Handover
Figure 5-5 Example of the 3G-to-2G handover in the PS domain
5.8.3 3G-to-2G Handover in Both CS Domain and PS Domain

This section describes the 3G-to-2G handover in both CS domain and PS domain in detail.
Inter-RAT Handover in Both CS Domain and PS Domain

For a UE in CELL_DCH state using both CS and PS domain services, the inter-RAT handover procedure is based on the measurement reports from the UE but is initiated from the UTRAN.
5-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 02 (2009-06-30)
RAN Handover
The UE performs the inter-RAT handover from UTRA RRC connected mode to GSM connected mode first. After the UE sends a handover complete message to the GSM/BSS, the UE initiates a temporary block procedure towards the GPRS to suspend the GPRS services. After the CS domain services are released on the GSM side, the inter-RAT handover in the PS domain is initiated and then completed. If the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode succeeds, the handover is regarded as successful, no matter whether the UE initiates a temporary block procedure towards the GPRS. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode and re-establish the connection in the original state.
SGSN Service Suspend and Resume

When the CS connection is terminated, the BSS may send a RESUME message to the SGSN. However, resume is impossible since the radio access system has changed. Therefore, the SGSN acknowledges the resume through a RESUME NACK message. The UE sends a ROUTING AREA UPDATE REQUEST message to the SGSN to resume the GPRS service. The update mode depends on the network operation mode in use. Figure 5-6 Intra-SGSN service suspend and resume
Issue 02 (2009-06-30)
5-17
RAN Handover
Figure 5-7 Inter-SGSN service suspend and resume
5.8.4 2G-to-3G Handover in CS Domain

When a GSM cell has a neighboring UMTS cell, the measurement control information is contained in the system information. The dual-mode MS performs the inter-RAT measurement in idle timeslots and reports the measurement result. The BSC decides whether to start the inter-RAT handover according to the measurement result. The GSM system uses time division multiple access technology, and the inter-RAT measurement is performed in idle timeslots. Therefore, the GSM need not support the compressed mode.
5-18
02 (2009-06-30)
RAN Handover
Figure 5-8 2G-to-3G handover in CS domain
5.8.5 2G-to-3G Handover in PS Domain

Figure 5-9 shows the 2G-to-3G handover in the PS domain.
Issue 02 (2009-06-30)
5-19
RAN Handover
Figure 5-9 2G-to-3G handover in PS domain
5-20
02 (2009-06-30)
RAN Handover
6 HCS Handover Algorithms
HCS Handover Algorithms
HCS handover is one type of inter-frequency handover and inter-RAT handover.
6.1 HCS Handover Overview

In a 3G network, hot spots in radio communication may appear with the increase of subscribers and traffic. This requires more cells to increase the network capacity. More cells and smaller cell radius lead to more frequent handovers of UEs. For a UE in fast movement, frequent handovers reduce call quality, increase uplink interference, and increase signaling load. Here, Hierarchical Cell Structure (HCS) is a mechanism that arranges different cells at different layers. HCS handover instructs UEs to be at different layers based on speed estimation, thus increasing the network capacity. Figure 6-1 shows an HCS with three layers. Figure 6-1 HCS with three layers
The features of different cells are as follows:
Macro cell

Large coverage Continuous coverage Low requirement for capacity Fast-moving environment Densely populated areas High requirement for capacity
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 6-1
Micro cell

Issue 02 (2009-06-30)

RAN Handover
Slow-moving environment Indoor coverage Outdoor blind spot coverage
Pico cell

The pico cell has the highest priority and the macro cell has the lowest priority. Based on speed estimation, the RNC instructs a fast-moving UE to select a cell with a lower priority to decrease the frequency of handovers, and instructs a slow-moving UE to select a cell with a higher priority to increase the network capacity. The cell with a lower priority has larger coverage, and the cell with a higher priority has smaller coverage. Huawei RNC supports the HCS with eight layers. The priority level of a cell is set by the HCSPrio parameter. To allow HCS handover, the RNC must enable the function through the HoSwitch:HO_ALGO_HCS_SPEED_EST_SWITCH parameter.
6.2 HCS Handover Phases

HCS handover has two phases: UE speed estimation and HCS handover execution.
6.2.1 UE Speed Estimation

This section describes high-speed estimation, low-speed estimation, and anti-ping-pong event 1D recording. Based on the number of changes of the best cell within a specified period, the speed estimation algorithm estimates the moving speed of the UE. Then, the RNC decides the UE speed. The procedure for high-speed estimation is as follows:
If HO_ALGO_HCS_SPEED_EST_SWITCH is set to ON and the cell is layered with a not lowest priority, the RNC initiates a high-speed estimation for the UE after receiving an event 1D report. If the number of changes of the best cell for the UE is higher than the NFastSpdEst within the TFastSpdEst, the RNC decides that the UE is in fast movement.
The procedure for low-speed estimation is as follows:
If the HO_ALGO_HCS_SPEED_EST_SWITCH is set to ON and the cell is layered with a not highest priority, the RNC starts the timer TCycleSlow after the RRC connection is set up. When the timer TCycleSlow expires, the RNC initiates a low-speed estimation for the UE. If the number of changes of the best cell for the UE is lower than the NSlowSpdEst within the TSlowSpdEst, the RNC decides that the UE is in slow movement.
If frequent changes of the best cell occur, several events 1D for the same cell may be recorded. This may lead to inaccurate UE speed estimation. Therefore, a mechanism is used for anti-ping-pong event 1D recording.
During the recent period specified by TRelateLength, if multiple event 1Ds are reported for a certain cell, only the first one is recorded.
6-2
02 (2009-06-30)
RAN Handover
6.2.2 HCS Handover Execution

HCS handover execution based on UE speed estimation has two types: inter-layer handover in fast movement and inter-layer handover in slow movement. The inter-layer handover algorithm initiates the corresponding handover based on speed estimation:

If the UE is in fast movement, the RNC instructs the UE to select a cell with a lower priority. If the UE is in slow movement, the RNC instructs the UE to select a cell with a higher priority. If the UE is in normal movement, no inter-layer handover occurs.
When the RNC instructs the UE to select a cell with a lower or higher priority, the neighboring cells whose frequency band is not supported by the UE are not taken into account. If there are neighboring cells with several candidate frequencies, the RNC selects one of the frequencies randomly.
Inter-Layer Handover in Fast Movement

When deciding that the UE is in fast movement, the RNC instructs the UE to select a cell with a lower priority.
If the UE is located in the overlap between the cell with a higher priority and the cell with a lower priority, a blind handover is initiated. The RNC selects the neighboring cells with a lower HCS priority level to generate a cell list. The neighboring cells whose frequency band is not supported by the UE are not taken into account. If there are neighboring cells with several candidate frequencies, the RNC selects one of the frequencies randomly. The RNC searches for neighboring cells for blind handover according to BlindHOFlag from the cell list generated in step 1. The RNC chooses a neighboring cell whose BlindHOQualityCondition value is the smallest for blind handover. The RNC determines whether the target cell supports the current service. If the target cell does not support the current service, the RNC does not perform the blind handover. The target cell can be a UMTS cell or a GSM cell. The priority of an intra-RAT inter-frequency blind handover is higher than that of an inter-RAT blind handover.
1.
2. 3.
If the neighboring cell for blind handover is not configured or the blind handover fails, a measurement is initiated for cells with a lower priority.
The target cell is decided on the basis of the measurement report from the UE.
Inter-Layer Handover in Slow Movement

When deciding that the UE is in slow movement, the RNC instructs the UE to select a cell with a higher priority. The inter-layer handover algorithm initiates a measurement for cells with a higher priority and then decides the target cell based on the measurement report from the UE.
Issue 02 (2009-06-30)
6-3
RAN Handover
6.3 Signaling Procedure of HCS Handover

The signaling procedure for HCS handover is the same as that of inter-frequency handover and inter-RAT handover. For details, see 4.6 Signaling Procedures for Inter-Frequency Handover and 5.8 Signaling Procedures for Inter-RAT Handover.
6.4 Interoperability Between HCS Handover and Other Handovers

This section describes the following aspects:

Interoperability between HCS handover and intra-frequency handover Interoperability between HCS handover and inter-frequency handover Interoperability between HCS handover and inter-RAT handover
Interoperability Between HCS Handover and Intra-Frequency Handover

If an intra-frequency handover is requested when an HCS handover measurement is initiated and an intra-frequency cell measurement is ongoing, the HCS handover measurement is not disrupted. After the intra-frequency handover is finished,

If the best cell remains unchanged, the HCS measurement continues. If the best cell changes, the high-speed estimation for the UE is triggered. Intra-Frequency Handover.
For more information about intra-frequency handover, see 2.2
Interoperability Between HCS Handover and Inter-Frequency Handover

An inter-frequency handover is triggered by one of the following factors:

Reporting of event 2D QoS problem caused by the quality imbalance between uplink and downlink Imbalance of load between inter-frequency cells UE speed decision in HCS
Reporting of event 2D indicates that the inter-frequency handover based on coverage is triggered, which is of high priority to be processed.
If the HCS handover algorithm is performing inter-frequency measurement when event 2D is reported, the measurement control is modified according to the algorithm of inter-frequency handover based on coverage. If the RNC is performing inter-frequency measurement after event 2D is reported, HCS handover will not be executed. If the measurement due to other causes stops, then HCS handover measurement is restarted. Other causes may be reception of event 2F, expiration of measurement control, or others.
When a speed-based inter-frequency handover is triggered, the RNC determines first whether the timer specified by IFAntiPingpangTimerLength expires.
6-4
02 (2009-06-30)
RAN Handover

If the timer does not expire, the RNC cancels this handover. If the timer expires, the RNC performs the handover.
Run the SET HONCOVALGPRIO command to set RNC-oriented non-coverage-based handover algorithm priorities.
Interoperability Between HCS Handover and Inter-RAT Handover

It is strongly recommended that the inter-RAT handover to 2G not be used in HCS handover. Set the UseOfHcs parameter to NOT_USED to disable HCS priority setting for neighboring GSM cells.
Issue 02 (2009-06-30)
6-5
RAN Handover
7 Parameters
7
The following describes the parameters related to handover. Table 7-1 Parameter description (1) Parameter id CIO Description
Parameters
For the meaning of each parameter, see Table 7-1. For the default value, value ranges, and MML commands of each parameter, see Table 7-2.
This parameter works with the offset of neighboring cell-oriented Cell Individual Offset (CIO). It is used for intra- or inter-frequency handover decisions. The larger the sum, the higher the handover priority of the neighboring cell. The smaller the sum, the lower the handover priority of the neighboring cell. Usually it is configured to 0. The larger the parameter, the easier of the handover to the neighboring cell. The smaller the parameter, the harder the handover to the neighboring cell. For details, refer to 3GPP TS 25.331. Cell individual offset for the GSM cell, which is set according to the topographic feature. This parameter is used for decision making for the inter-RAT handover. The larger the value of the parameter, the higher the handover priority of the GSM cell. The smaller the value of the parameter, the lower the handover priority of the GSM cell. Hysteresis value for the event 2C. The value of this parameter correlates with slow fading. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the speed of the handover algorithm to respond to signal change becomes lower, and therefore event 2B might not be triggered in time.
CIOOffset
Hystfor2C
Issue 02 (2009-06-30)
7-1
7 Parameters
RAN Handover
Parameter id Hystfor3C
Description Hysteresis value for the event 3C. The value of this parameter correlates with slow fading. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be avoided, but the speed of the handover algorithm to respond to signal change becomes lower. If the inter-RAT handover hysteresis is set to an excessively high value, the GSM cell to which the UE hands over must be of good quality. Therefore, the conditions for triggering the inter-RAT handover decision are hard to be satisfied, and the call drop rate increases. The emulation result shows that in a cell where the average moving speed of UEs is high, for example a cell that covers highways, HystforInterRAT can be set to 1.5 dB, because in the cell the terrain is flat and there are few barriers , which causes a small shadow fading variation. In a cell where the average moving speed of UEs is low, there are usually many tall buildings, so the shadow fading variation is comparatively big, and HystforInterRAT can be set to 3.0 dB. Hysteresis for inter-frequency hard handover in periodical report mode. This parameter is used to estimate the inter-frequency handover at the RNC. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the speed of the handover algorithm to respond to signal change becomes lower, and therefore event 2B might not be triggered in time. L3 filtering coefficient for the inter-frequency measurement. The physical meaning of this parameter is the same as the measurement model and intra-frequency measurement. The difference is that the report period for the inter-frequency measurement is 480 ms, whereas the report period for the intra-frequency measurement is 200 ms. In practice, it can be adjusted according to traffic performance measurement. The larger the value of this parameter, the stronger the smoothing effect and the higher the anti-fast-fading capability, but the lower the signal change tracing capability. If the value of this parameter is set too small, unnecessary hard handover or frequently changed handover may occur. Timer length for inter-frequency measurement. After inter-frequency measurement starts, if no inter-frequency handover is performed when this timer expires, the inter-frequency measurement and the compressed mode (if started) are stopped. The value 0 indicates the timer is not to be enabled. This parameter is used to prevent the long inter-frequency measurement state (compressed mode) due to unavailable measurement of the target cells that meet the handover requirements. Setting the value of this parameter smaller can reduce the long-time impact of the compressed mode on the serving cell. In this case, however, the compressed mode might be stopped earlier and as a result the UE cannot trigger inter-frequency handover. For the coverage-based inter-frequency handover, call drops may occur.
HystForPrdInterFreq
InterFreqFilterCoef
InterFreqMeasTime
7-2
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqReportMode
Description Inter-frequency measurement report mode. PERIODICAL_REPORTING: periodical inter-frequency measurement report EVENT_TRIGGER: event-triggered inter-frequency measurement report There are two inter-frequency handover report modes in the RNC, namely, event-triggered measurement report and periodical measurement report. The report mode is selected by setting the inter-frequency report mode switch that is RNC-oriented. - Event-triggered measurement report Use event 2B to decide whether to trigger inter-frequency handover. This prevents the ping-pong effect from occurring before and after inter-frequency handover (The quality of the currently used frequency is lower than the absolute threshold "used frequency quality threshold", and the quality of the unused frequency is higher than another absolute threshold "target frequency trigger threshold". ) The reason is that event 2B cannot change from event-triggered mode to periodical mode and cannot reattempt if the non-handover attempt fails, unless this cell can trigger event 2B again. The advantage of event-triggered report mode is that the signaling transmission and processing load are saved. Comparing the signal quality between intra-frequency and inter-frequency handovers, the ping-pong effect in handover is prevented to some extent. The disadvantage of event-triggered report mode is that the event is reported only once and cannot be changed to periodical mode. If the handover fails, the periodical report is triggered only by the internal timer. For the cell-oriented algorithm parameters, each time when the best cell is updated, the inter-frequency measurement parameters should be updated accordingly. - Periodical report mode Use event 2D/2F to start and stop the compressed mode, and to report the inter-frequency cell measurement result during the compressed mode period. When the cell quality reported by the UE is higher than the absolute threshold plus hysteresis, start the trigger delay timer. If the conditions are always met before the timer expires, start the inter-frequency handover after the timer expires. If the handover fails, perform the handover decision according to the inter-frequency measurement period report. The advantage of the periodical report mode is that it can repeatedly perform direct retry on the same cell when the handover fails, and that the following algorithms can be flexibly developed. In addition, for the cell-oriented algorithm parameters, the UE need not be informed through signaling but the cell need be updated only when the handover decision is performed in the RNC. The disadvantage of the periodical report mode is that it requires large amount of signaling and increases the load on the air interface and for signaling processing. As for the impact on network performance,the two report modes have both advantages and disadvantages. Currently, the traditional periodical report mode is used.
Issue 02 (2009-06-30)
7-3
7 Parameters
RAN Handover
Parameter id InterRATMeasTime
Description Timer length for inter-RAT measurement. After inter-RAT measurement starts, if no inter-RAT handover is performed when this timer times out, the inter-RAT measurement is stopped. In addition, the compressed mode is deactivated, if any; If the value is 0, you can infer that the inter-RAT measurement timer is not started. To set this parameter, you need to consider the following factors: This parameter aims to prevent that the handover conditions are not met and the compressed mode is kept for a long time when the UE does not move or is moving in a low speed. The service quality is adversely affected and the total available capacity decreases if the compressed mode is kept for a long time. Most inter-RAT handovers can be finished within 60 s. As for the impact on network performance, If the InterRATMeasTime is excessively low, the UE cannot finish inter-RAT handovers. If InterRATMeasTime is excessively high, it cannot help improve the service quality. In actual networks, statistics can be made to obtain the delay for a successful inter-RAT handover so as to get a proper value of InterRATMeasTime that satisfies most UEs. Interval that the UE reports inter-RAT measurement results to the RNC. In periodical report mode, the interval between two reports is the configured value. That is, the UE submits reports at intervals of the configured time. The value "NON_PERIODIC_REPORT" is, however, not recommended. In this setting, the UE behavior is not defined. Because the GSM RSSI measurement period is 480 ms, the inter-RAT periodical report interval should be longer than 480 ms. If InterPeriodReportInterval is excessively high, the handover judging time will be long, and handovers will be slower. The InterPeriodReportInterval is adjusted according to the configured GSM RSSI measurement compressed mode sequence. According to the current configured GSM RSSI measurement compressed mode sequence, the RSSI measurement of eight GSM cells can be finished in 480 ms, so the RSSI measurement of 16 GSM cells can be finished in 1000 ms. According to the protocol, not more than 32 inter-RAT neighboring cells exist, so the InterPeriodReportInterval can be set to 2000 ms if neighboring GSM cells exceeds 16. This parameter has impact on the Uu signaling flow. If the interval is too short and the frequency is too high, the RNC may have burden in processing signaling. If the interval is too long, the network cannot detect the signal change in time, which may delay the inter-RAT handover and thus cause call drops.
InterRATPeriodRepor tInterval
7-4
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterRatReportMode
Description Inter-RAT measurement report mode. When PERIODICAL_REPORTING is selected, you can infer that periodical inter-RAT measurement report is adopted; when EVENT_TRIGGER is selected, you can infer that event-triggered inter-RAT measurement report is adopted. The RNC includes two modes of the inter-RAT measurement report. The event triggered report and the periodical report are selected according to the inter-RAT measurement report mode switch. -Event-triggered measurement report To avoid the ping-pong effect before and after the inter-RAT handover, event 3A where the currently used frequency quality is lower than the absolute threshold and the signal level of the GSM cell is higher than another absolute threshold is the triggering event that determines the inter-RAT handover. To improve the handover success rate, the BSIC of the GSM cell where the event 3A is triggered must be decoded correctly by the UE. The reason is that event 3A cannot change from event-triggered mode to periodical mode and cannot reattempt if the handover attempt fails, unless this cell can trigger event 3A again. The advantage of event-triggered report mode is that signaling transmission is reduced and the load is shared. By comparing the signal quality between the current frequency and inter-RAT frequency, the ping-pong effect in the handover is prevented to some extent. The disadvantage of event-triggered report mode is that the event is reported only once and cannot be changed to periodical mode. If the handover fails, the periodical report is triggered only by the internal timer. For the cell-oriented algorithm parameters, each time the best cell is updated, the inter-frequency measurement parameters should be updated accordingly. -Periodical report mode When the quality of the GSM cell reported by the UE is higher than the inter-RAT event 2D absolute threshold + hysteresis, it starts the delay trigger timer. If the quality of the GSM cell satisfies the requirement throughout the duration of the timer, the system starts the inter-RAT handover after the time-out. The GSM cells of which the BSIC can be decoded use comparatively shorter delay trigger time to achieve a higher priority. The GSM cells of which the BSIC is not verified use comparatively longer delay trigger time to achieve a lower priority and decode the BSIC. If the handover fails, reattempt according to the inter-RAT measurement period report. The advantage of the periodical report mode is that it can repeatedly perform the handover retry on the same cell when the handover fails, and that the following algorithms can be flexibly developed. In addition, for the cell-oriented algorithm parameters, the RNC updates the parameters when performing internal handover decision and the system needs not to inform the UEs of the parameter change through signaling messages after the handovers. The disadvantage of the periodical mode is that it requires large amount of signaling and increases the load on the air interface and for signaling processing. Both modes (the periodical mode and the event report mode) have advantages and disadvantages. Currently, the traditional periodical report mode is most commonly used.
NPrio
Priority of neighboring cells. The priority that corresponds to the neighboring cell is valid only when the this parameter is set to TRUE. The lower the priority, the easier it is for the neighboring cell to be delivered as the measurement object. For example, it is more possible for a neighboring cell of priority 1 than a cell of priority 2 to be delivered as the measurement object.
Issue 02 (2009-06-30)
7-5
7 Parameters
RAN Handover
Parameter id PrdReportInterval
Description Inter-frequency measurement reporting interval. In periodical report mode, the interval between two reports is the configured value. However, it is not recommended that the value "NON_PERIODIC_REPORT" be set, upon which the UE behaviour is not defined. This parameter has impact on the Uu signaling flow. If the interval is too short and the frequency is too high, the RNC may have burden in processing signaling. If the interval is too long, the network cannot detect the signal change in time, which may delay the inter-frequency handover and thus cause call drops. Time delay for triggering handovers to GSM cells with non-verified BSIC. During the period of time specified by this parameter, if the signal quality in a neighboring GSM cell satisfies inter-RAT handover conditions and the neighboring GSM cell is not verified, an inter-RAT handover is triggered. When the value of this parameter is 65535, the RNC does not perform inter-RAT handovers to non-verified GSM cells. The higher the time-to-trigger parameters are, the smaller the average number of handovers is, and the possibility of call drops increases. Time delay for hard handover triggered by periodical reports. Only the inter-frequency cell in which the signal quality meets the requirement in all periodical reports during the period of time specified by this parameter can be selected as the target cell in the inter-frequency handover. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of the handover to the change of measured signals. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. The value of this parameter can be adjusted according to the actual network statistics.
TimeToTrigForNonV erify
TimeToTrigForPrdInt erFreq
7-6
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TimeToTrigForVerify
Description Time delay for triggering handovers to GSM cells with verified BSIC. During the period of time specified by this parameter, if the signal quality in a neighboring GSM cell satisfies inter-RAT handover conditions and the neighboring GSM cell is verified, an inter-RAT handover is triggered. The inter-RAT handover conditions are as follows: Mother_RAT + CIO >= Tother_RAT + H/2 If the quality of the GSM neighboring cell meets the preceding condition, the system starts the trigger timer. The system then implements the handover decision after timeout if the quality of the GSM neighboring cell always meets the preceding condition throughout the time length of the timer. The time length of the trigger timer is called the delay trigger time. The delay trigger time and hysteresis are used to prevent mis-decisions caused by signal jitters during inter-RAT handover decisions. Considering that the UE is on the edge of the system, the parameter TimeToTrigForVerify should be set to a comparatively low value. Because the GSM cells of which the BSIC is already verified usually have good performance, the parameter TimeToTrigForVerify should be set to 0, which indicates that the handover is implemented immediately. The higher the time-to-trigger parameters are, the smaller the average number of handovers is, and the possibility of call drops increases. Time delay to trigger the event 2C. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of event 2F to the change of measured signals. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell where fast-moving UEs are dominant, this parameter can be set smaller, whereas for the cell where slow-moving UEs are dominant, this parameter can be set larger. The value of this parameter can be adjusted according to the actual network statistics.
TrigTime2C
Issue 02 (2009-06-30)
7-7
7 Parameters
RAN Handover
Parameter id TrigTime3C
Description Time delay to trigger the event 3C. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event 3C to measurement signal change. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Thus, set the value smaller for cells where fast-moving UEs are dominant, whereas set the value bigger for cells where slow-moving UEs are dominant. The value of this parameter can be adjusted according to the actual network statistics. Because the report period of inter-frequency measurement is 480 ms, the trigger time period shorter than 480 ms is invalid. The bigger the time-to-trigger values are, the lower the average handover frequency is; but the increase of the time-to-trigger values increases the risk of call drops. Maximum number of times for event 2B retry. This parameter defines the number of times for event 2B retry when the measurement control is valid. The larger the value of this parameter, the larger the number of times for inter-frequency handover retry, and the higher probability for the UE to be successfully handed over to the target cell whose load is restored. After the maximum number of times for event 2B retry, the RNC sends the inter-frequency measurement control message again to hand over the UEs to the other cells of this frequency. If the measurement control message is released, the retry will be immediately stopped. Maximum retry times of the event 2C. This parameter defines the number of times for event 2C retry when the measurement control is valid. The larger the value of this parameter, the larger the number of times for inter-frequency handover retry, and the higher probability for the UE to be successfully handed over to the target cell whose load is restored. When the retry times reaches the maximum value, the RNC stops the retry process. Or if the measurement control message is released, the retry will be immediately stopped. Indicating whether to perform blind handover. FALSE: The cell is not in the alternative cells for blind handover, so blind handover to this cell cannot be triggered. TRUE: The cell is in the alternative cells for blind handover, so blind handover to this cell might be triggered. This parameter is used in the algorithm of the load reshuffling (LDR) intra-frequency blind handover. This parameter defines how many measurement reports are needed for making the blind handover decision. The RNC starts blind handover only if the UE continuously reports adequate intra-frequency measurement reports that meet the quality requirements of blind handover. During the measurement process, if the UE reports an unqualified measurement report, the process ends. And the RNC does not start blind handover on the target cell.
AmntOfRpt2B
AmntOfRpt2C
BlindHOFlag
BlindHOIntrafreqMR Amount
7-8
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id BlindHOIntrafreqMR Interval
Description This parameter specifies the intra-frequency measurement report interval of blind handover. It determines the intra-frequency measurement reporting interval of Load Reshuffling (LDR) blind handover. The smaller the value of this parameter, the smaller the intra-frequency measurement reporting interval, and the smaller the time for intra-frequency measurement. But the greater the influence of signal fluctuation, which can result in wrong handover. On the contrary, the larger the value of this parameter, the longer the intra-frequency measurement reporting interval, and the less the influence of signal fluctuation, which can improve the possibility of successful blind handover. But if the time for intra-frequency measurement becomes long, the handover may not be performed timely. Blind handover condition. If the value is not -115, the handover is defined as Conditional Blind HO, which is used for the inter-frequency neighboring cells of the same coverage. If the value is -115, the handover is defined as Direct Blind HO, which is used for the inter-frequency neighboring cells of larger coverage. Flag of whether adding a cell into the active set will affect the relative threshold of the event 1A. This parameter is a flag of whether adding the cell into the active set will affect the relative threshold of the event 1A NOT_AFFECT: Adding the cell into the active set does not affect the relative threshold of the event 1A. AFFECT: Adding the cell into the active set affects the relative threshold of the event 1A. Flag of whether adding a cell into the active set will affect the relative threshold of the event 1B. This parameter is a flag of whether adding the cell into the active set will affect the relative threshold of the event 1B NOT_AFFECT: Adding the cell into the active set does not affect the relative threshold of the event 1B. AFFECT: Adding the cell into the active set affects the relative threshold of the event 1B. This parameter specifies the value of the handover protection timer. If services can be set up on channels based on a higher technique after channel handover is completed, the handover protection timer will be started. When the timer expires, the RNC will try to carry services on channels based on a higher technique. Channel retry cannot be performed before this timer expires. CMCF algorithm switch. 1) CMCF_DL_HLS_SWITCH: When the switch is on, the compressed mode supports DL higher-layer scheduling. 2) CMCF_UL_HLS_SWITCH: When the switch is on, the compressed mode supports UL higher-layer scheduling. 3) CMCF_UL_PRECFG_TOLERANCE_SWITCH: When the switch is on, the compressed mode of the UE in the compressed mode pre-configuration state can be different from that required by current traffic. 4) CMCF_WITHOUT_UE_CAP_REPORT_SWITCH: When the RNC starts inter-frequency or inter-RAT measurement, the RNC checks the information of whether the compressed mode is required for measurement on the frequency band of the cells in measurement list. The information should be reported by the UE in RRC connect setup complete message. When the switch is on and no such information has been reported, the RNC starts the compressed mode and then delivers the measurement.
BlindHOQualityCond ition
CellsForbidden1A
CellsForbidden1B
ChannelRetryHoTime rLen
CmcfSwitch
Issue 02 (2009-06-30)
7-9
7 Parameters
RAN Handover
Parameter id CmpSwitch
Description Compatibility switch. 1) CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH: When the switch is on, the IMS signaling assigned by the CN undergoes compatibility processing as an ordinary PS service. When the switch is not on, no special processing is performed. 2) CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH: When the switch is on, the IUUP version can be rolled back to R99 when complete configurations are applied during inter-RAT handover. 3) CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH: When the switch is on, H2D is performed before a neighboring RNC cell whose version is earlier than R5 is added to the active set; E2D is performed before a neighboring RNC cell whose version is earlier than R6 is added to the active set. If the DRNC is of a version earlier than R5, DL services cannot be mapped on the HS-DSCH. If the DRNC is of a version earlier than R6, DL services cannot be mapped on the HS-EDCH. 4) CMP_IUR_SHO_DIVCTRL_SWITCH: When the switch is on, the diversity combination over the Iur interface is configured on the basis of that of the local RNC. When the switch is not on, the diversity combination over the Iur interface is configured on the basis of services. The flag of diversity combination over the Iur interface can be set to MUST (for BE services) or MAY (for other services). 5) CMP_UU_AMR_SID_MUST_CFG_SWITCH: For narrowband AMR services, when the switch is on, the SID frame is always configured; when the switch is not on, the SID frame is configured on the basis of CN assignment. 6) CMP_UU_DST_SERV_CELL_D2E_SWITCH: This switch is set for compatibility with the UE that does not support the change of the serving cell accompanied with the reconfiguration of the target service link D2E. When the switch is enabled, the change of the serving cell accompanies the reconfiguration of the target service link D2E. When the switch is disabled, the serving cell is changed after the UE completes the reconfiguration of the target service link D2E. The switch is used in only R6 and later versions. 7) CMP_UU_IGNORE_UE_RLC_CAP_SWITCH: When the switch is on, the RAB assignment request and the subsequent RB setup procedure proceed if the RLC AM capabilities of the UE fail to meet the minimum RLC TX/RX window buffer requirement of the RAB to be setup. When the switch is not on, the RAB assignment request is rejected. 8) CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH: When the switch is on, the active set update is in the same procedure as the change of the serving cell. When the switch is not on, the serving cell is changed after the UE updates the active set and delivers reconfiguration of physical channels. This switch is applicable only to R6 UEs. 9) CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH: When the switch is on, channel transition is in the same procedure as the change of the serving cell. When the switch is not on, the serving cell is changed after the UE performs channel transition and delivers reconfiguration of physical channels. 10) CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH: By default, the switch is on. In this case, the Alternative E-bit is not configured for L2. 11) CMP_UU_FDPCH_COMPAT_SWITCH: When the switch is OFF, the UE can support F-DPCH capability only when the message "RRC_CONNECT_REQ" or "RRC_CONNECT_SETUP_CMP" carries the information element that indicates the UE supports F-DPCH capability. 12) CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH: When the switch is on, When SRB is set up on DCH, and RNC decides to setup the AMR through DRD procedure, RNC will execute blind handover to the target cell, and then setup the AMR RBs on the target cell. 13) CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH: When the Iu QoS Negotiation function is active and the switch is on, IE RAB Asymmetry Indicator is Symmetric bidirectional, The uplink and downlink RNC negotiation rate is asymmetric, RNC select the bigger rete as Iu QoS negotiation rate. When the switch is OFF, RNC select the less rate as Iu QoS negotiation rate. Huawei Proprietary and Confidential 02 (2009-06-30)
Copyright Huawei Technologies Co., Ltd
7-10
RAN Handover
7 Parameters
Parameter id CoexistMeasThdChoi ce
Description Type of event 2D/2F measurement thresholds when inter-frequency and inter-RAT measurements coexist. COEXIST_MEAS_THD_CHOICE_INTERFREQ: choosing the inter-frequency oriented parameters as event 2D/2F measurement thresholds for inter-frequency measurement. COEXIST_MEAS_THD_CHOICE_INTERRAT: choosing the inter-RAT oriented parameters as event 2D/2F measurement thresholds for inter-RAT measurement. When you set the previous parameters, consider the following factors: event 2D/2F measurement thresholds for inter-frequency measurement, inter-frequency and inter-RAT handover decision thresholds, and current handover policy. For example, if the event 2D threshold for inter-RAT measurement is higher than that for inter-frequency measurement, and inter-frequency cells are preferred when inter-RAT and inter-frequency cells coexist, then you can choose COEXIST_MEAS_THD_CHOICE_INTERFREQ. CS domain Relocation GSM load THD. This parameter specifies the CS domain relocation GSM load threshold. When the GSM load policy is used, that is, when [NcovHoOn2GldInd] in SET INTERRATHONCOV is set to ON, the CS domain inter-system relocation out process will be stopped if the GSM system send its cell load to the RNC and the cell load exceeds the CS domain Reloc GSM load THD. Otherwise, the RNC does not stop the CS domain inter-system relocation out process. Indicating whether the cell allows CS service inter-RAT handover. ON: CS service inter-RAT handover is enabled. OFF: CS service inter-RAT handover is disabled. Service handover refers to the handover attribute and related parameter configuration on the network side for each service. When a service is established, the related measurements and inter-RAT handover are immediately triggered. These two switches are enabled only for service handover; generally, they are disabled by default. Note that the service handover is enabled only when the handover attribute is set to HO_TO_GSM_SHOULD_BE_PERFORM and CS service inter-RAT handover is set to ON. Both conditions are mandatory. For hybrid services, the service handover is not triggered. Indicating whether to support CS over HSPA of the neighboring RNC. This parameter defines the length of penalty timer for SHO failure after rate reduction in the active set. When the rate reduction in the active set is performed which triggers the increase of SHOs in the target cell, if the target cell fails to join the active again, the RNC starts the penalty timer for SHO failure. This parameter defines the length of the penalty timer. Before the timer expires, the rate increasing in the active set is prohibited, but rate reduction is not prohibited. Such penalty strategy is applied in the following scenario: If there is a cell, for some reason, it has high signal strength but heavy load, and cannot join the active set throughout by then. This cell may enter the SHO rate reduction evaluation process repeatedly, which results in rate reduction in the active set. If the cell fails to join the active set, the rate in the active set may increase during the evaluation process because of the DCCC algorithm. To avoid such rate fluctuation, the RNC uses a strategy of rate increase penalty after the SHO failure again.
CSHOOut2GloadThd
CSServiceHOSwitch
CSVoiceOverHspaSu ppInd DcccShoPenaltyTime
Issue 02 (2009-06-30)
7-11
7 Parameters
RAN Handover
Parameter id DivCtrlField
Description There are two combination methods for uplink combination of soft handover: one is maximum ratio combination at the NodeB Rake receiver, which gives the highest combination gain; the other is selective combination at the RNC, which gives a relatively smaller combination gain. The default value of the indication switch is MAY, which means the NodeB decides whether to implement maximum ratio combination according to its own physical conditions; when MUST is selected, the NodeB is forced to carry out maximum ratio combination which is usually used in tests; when MUST_NOT is selected, the NodeB is forbidden to carry out maximum ratio combination. Consider the working status (test/normal operation) and the propagation environment when deciding whether to implement softer combination and to adopt which kind of softer combination. Timer length for downlink Qos measurement. This parameter controls the time lengths for the inter-frequency and inter-RAT measurement based on Qos. After inter-frequency or inter-RAT measurement starts, if no inter-frequency handover is performed when this timer expires, the measurement is stopped, and the compressed mode is deactivated, if any. If this parameter is set to 0, this indicates that the timer will not be started. For the inter-frequency or inter-RAT measurement based on coverage, the compressed mode can be stopped through reporting event 2F. For measurement that is not based on coverage, event 2F is not reported, and the timer must be set but should not be set to 0. As for the impact on network performance: It reduces the influence of long time compressed mode to the serving cell. The compressed mode may be stopped ahead of time, which can cause the result that the UE fails to initiate inter-frequency or inter-RAT handover, and thus can lead to call drops. This parameter determines whether the compressed mode is limited to the downlink SF. Starting the compressed mode is resource consuming for the fast-moving UEs. Whether the spreading factors of the current DCH channels should be considered when the switch controlling the start compressed mode is set. When the switch is set to FALSE, you can infer that the start compressed mode does not consider the spreading factors of the DCH channels; when the switch is set to TRUE, you can infer that the start compressed mode considers the spreading factors of the DCH channels. CM implementation approach selection basis. When the downlink spreading factor is greater than or equal to this parameter value, the SF/2 approach will be preferred. Otherwise, the high-layer scheduling will be preferred. The SF/2 approach consumes more system resources and therefore this approach is recommended only for low-rate users. The high-layer scheduling requires variable multiplexing positions of transport channels and is applicable to a relatively narrow range. In addition, this approach affects the transmission rate of users and therefore is recommended only when the SF/2 approach is unavailable or there are high-rate users.
DLQosMcTimerLen
DlSFLimitCMInd
DlSFTurnPoint
7-12
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id FilterCoef
Description According to the 3GPP TS 25.331, the filtering of the measurement value is calculated using the following formula, where k represents this parameter: Fn = (1 - a) * Fn - 1 + a * Mn Here, Fn: the updated filtered measurement result Fn - 1: the old filtered measurement result Mn: the latest received measurement result from physical layer measurements a = (1/2)(k/2). When a is set to 1, this means L3 filtering will not be applied. L3 filtering should be able to filter as much random impulse as possible. Thus the filtered measurement value can reflect the varying of the actual measurement value. The input measurement value to L3 filter has been filtered by L1 filter, where the impact of fast fading is almost eliminated. So the L3 filtering should apply smooth filtering to shadow fading and small amount of remaining fast fading, thus providing more reliable measurement value for event judgement. As for the impact on network performance: the larger the value of this parameter, the stronger the smoothing effect and the higher the anti-fast-fading capability, but the lower the signal tracing capability, the greater the possibility of call drops. If the value of this parameter is too small, unnecessary soft handover or the ping-pong handover may occur. Note that this parameter has great impact on the overall performance of the handover, so you should be cautious when adjusting this parameter. L3 filtering coefficient for event 2D or event 2F measurement. The larger the value of this parameter, the stronger the smoothing effect and the higher the anti-fast-fading capability, but the lower the signal change tracing capability. If the value of this parameter is set too small, unnecessary inter-system handovers may occur. The parameter has the same physical meaning and measurement model as the inter-frequency measurement L3 filter coefficient. The report period is 480 ms. For specific analysis, refer to the intra-frequency measurement layer 3 filter coefficients and inter-frequency measurement layer 3 filter coefficients. The recommended values of the inter-RAT measurement layer 3 filter coefficients in different cells are as follows: -In cells where the average moving speed of UEs is low, there is a comparatively big shadow fading square error, so the recommended value of inter-RAT measurement layer 3 filter coefficients is 4. The value can be increased in a certain degree; -In cells where the average moving speed of UEs is medium, there is a comparatively big shadow fading square error, so the recommended value of inter-RAT measurement layer 3 filter coefficients is 3; -In cells where the average moving speed of UEs is high, there is a comparatively small shadow fading square error, so the recommended value of inter-RAT measurement layer 3 filter coefficients is 2. HCS priority of the cell belongs to. The parameter depends on HCS rules. For details, refer to 3GPP TS 25.304.
FilterCoefOf2D2F
HCSPrio
Issue 02 (2009-06-30)
7-13
7 Parameters
RAN Handover
Parameter id HoSwitch
Description HandOver switch. 1) HO_ALGO_HCS_SPEED_EST_SWITCH: When the switch is on, the RNC evaluates the UE's moving speed in the HCS and initiates fast intra-layer or slow inter-layer handover. 2) HO_ALGO_LDR_ALLOW_SHO_SWITCH: When the switch is on, the LDR inter-frequency handover is allowed during soft handover. 3) HO_ALGO_MBMS_FLC_SWITCH: When the switch is on, the UE requires that the redirection strategy be used for frequency layer convergence. 4) HO_ALGO_OVERLAY_SWITCH: When the switch is on, the associated receiving and mobility algorithms of the overlay network are used. When the switch is not on, the associated algorithms are not used. Overlay network is an UTRAN network covering present network, it supports HSPA, MBMS and other new features. To satisfy new requirements of operator and restrictions of present network, overlay network realizes operation distribution and load sharing between new network and present network, also gives special handling for mobility management of network verge. 5) HO_INTER_FREQ_HARD_HO_SWITCH: When the switch is on, the RNC is allowed to initiate inter-frequency measure control or the load-based inter-frequency hard handover upon the handover decision on inter-frequency load. 6) HO_INTER_FREQ_RPRT_2D2F_SWITCH: When the switch is on, quality measurement of the active set is allowed. After service setup is complete, the RNC initiates signal quality measurement on all the cells in the active set. If SIGNAL_HO_SWITCH is ON, this action is performed after RRC setup is complete. If the comprehensive quality of all the cells in the active set is below a preset threshold, the UE reports the event 2D. Then, the RNC starts the compressed mode, delivers inter-frequency or inter-RAT measurement control based on the settings of the associated switches and the UE's capabilities, and triggers inter-frequency or inter-RAT handover. 7) HO_INTER_RAT_CS_OUT_SWITCH: When the switch is on, the RNC is allowed to initiate inter-frequency measure control and the CS inter-RAT hard handover from the 3G network to the 2G network. 8) HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH: When the switch is on, the NACC function is supported during the PS inter-RAT handover from the 3G network to the 2G network in the cell change order process. When the switch is not on, the NACC function is not supported. When PS_3G2G_RELOCATION_SWITCH is ON, this switch is useless. When the NACC function is supported, the UE skips the reading procedure as the SI/PSI of the target cell is provided after the UE accesses the 2G cell. Thus, the delay of inter-cell handover is reduced. 9) HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH: When the switch is on, the PS inter-RAT handover from the 3G network to the 2G network is performed in the relocation process. When the switch is not on, the PS inter-RAT handover from the 3G network to the 2G network is performed in the cell change order process. 10) HO_INTER_RAT_PS_OUT_SWITCH: When the switch is on, the RNC is allowed to initiate inter-frequency measure control and the PS inter-RAT hard handover from the 3G network to the 2G network. 11) HO_INTER_RAT_RNC_SERVICE_HO_SWITCH: When the switch is on, the attributes of inter-RAT handover of the services are based on the configuration of RNC parameters. When the switch is not on, the attributes are set on the basis of the CN. If no information is provided by the CN, the attributes are then based on the RNC parameters. 12) HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH: When the switch is on, the cells in the detected set from which the RNC receives their valid event reports can be added to the active set. The cells allowed to be added to the active set must be the neighboring cells of the cells in the active set. 13) HO_INTRA_FREQ_DETSET_RPRT_SWITCH: When the switch is on, statistics on the intra-frequency measurement reports of the detected set are taken. 14) HO_INTRA_FREQ_HARD_HO_SWITCH: When the switch is on, the RNC is Huawei Proprietary and Confidential 02 (2009-06-30) allowed to initiate theHuawei Technologies Co., Ltd The RNC initiates the Copyright intra-frequency hard handover. intra-frequency hard handover in the following cases. 15) HO_INTRA_FREQ_RPRT_1J_SWITCH: When the switch is on, the event 1J is included in the delivery of intra-frequency measurement control if the UE version is R6.
7-14
RAN Handover
7 Parameters
Parameter id HsdpaCMPermissionI nd
Description This parameter determines whether the compressed mode (CM) is permitted for the UE when the HSDPA services exist. If the parameter value is set to TRUE, compressed mode is permitted on HSDPA, and HSDPA services can be set up when the compressed mode is activated. If the parameter value is set to FALSE, channel switch on H2D (from HS-DSCH to DCH) should be performed before compressed mode is started, and no HSDPA services should exist when compressed mode is activated. This switch is used for the compatibility of the HSDPA terminals existing in the network because these HSDPA terminals do not support the activated compressed mode on HSDPA services existence. HSPA serving cell change is usually triggered by event 1D. To avoid frequent serving cell change which may affect the system performance, a protection timer TimerHSPA is needed. This timer shall be started upon HSPA handover completed, i.e. the serving HSDSCH cell changed or the EDCH serving cell changed. And no more 1D-triggered serving cell change shall be performed until the timer expires. However, this timer shall not restrict HSPA serving cell change to another cell in the active set if current serving cell is to be removed from the active set. The value 0 means this timer shall not be started and serving cell change be initiated immediately. This parameter determines whether the compressed mode (CM) is permitted for the UE when HSUPA services exist. If the parameter value is set to Permit, compressed mode is permitted on HSUPA, and HSUPA services can be set up when the compressed mode activated. If the parameter value is set to Limited, channel switch on E2D (from E-DCH to DCH) should be performed before the compressed mode is started and no HSUPA services should exist when the compressed mode is activated. If the parameter value is set to BasedonUECap, the RNC determines whether to activate the compressed mode on E-DCH based on the UE capability, and whether to establish an E-DCH when the compressed mode is activated. This switch is used for the compatibility of the HSUPA terminals existing in the network because these HSUPA terminals do not support the compressed mode activated on the E-DCH. This parameter specifies the hysteresis value for event 1A. The value of this parameter correlates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effect or wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS 25.331. The value of this parameter is ranged from 2 dB to 5 dB. Event 1A is a key event that adds a cell to the active set. To ensure timely handover, the hysteresis of event 1A should be set a little smaller than those of events 1B, 1F, 1C, and 1D. But the difference should not be too large, otherwise the soft handover ratio can be affected. In addition, this parameter is related to filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters the SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leaves the SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and the number of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the varying of the signal in response to the handover algorithm becomes slower.
HspaTimerLen
HsupaCMPermissionI nd
Hystfor1A
Issue 02 (2009-06-30)
7-15
7 Parameters
RAN Handover
Parameter id Hystfor1B
Description This parameter specifies the hysteresis value for event 1B. The value of this parameter correlates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effect or wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS 25.331. The value of this parameter is ranged from 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters the SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leaves the SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and the number of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the varying of the signal in response to the handover algorithm becomes slower. This parameter specifies the hysteresis value for event 1C. The value of this parameter correlates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effect or wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS 25.331. The value of this parameter is ranged from 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters the SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leaves the SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and the number of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the varying of the signal in response to the handover algorithm becomes slower. This parameter specifies the hysteresis value for event 1D. The value of this parameter correlates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effect or wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS 25.331. The value of this parameter is ranged from 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters the SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leaves the SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and the number of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the varying of the signal in response to the handover algorithm becomes slower.
Hystfor1C
Hystfor1D
7-16
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id Hystfor1F
Description This parameter specifies the hysteresis value for event 1F. The value of this parameter correlates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effect or wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS 25.331. The value of this parameter is ranged from 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters the SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leaves the SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and the number of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the varying of the signal in response to the handover algorithm becomes slower. This parameter specifies the hysteresis value for event 1J. The value of this parameter correlates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effect or wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS 25.331. The value of this parameter is ranged from 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters the SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leaves the SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and the number of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be resisted, but the varying of the signal in response to the handover algorithm becomes slower. Hysteresis value for the event 2D. The value of this parameter correlates with slow fading. The larger the value of this parameter, the smaller probability of ping-pong effect or wrong decision, but event 2D might not be triggered in time. In periodical report mode, this parameter is used to resist the ping-pong effect of event 2D (the quality of the currently used frequency is lower than the threshold) and event 2F (the estimated quality of the currently used frequency is higher than the threshold). Event 2D is used to enable the compressed mode and event 2F is used to disable the compressed mode. Therefore, Hystfor2D can be increased on the basis of recommended value and inter-frequency handover ping-pong effect statistics. Hystfor2F can also be increased to reduce frequent enabling or disabling of compressed mode and to avoid unnecessary updates of the active set. To set the values of the parameters, you should consider the following factors: radio environment (with slow fading characteristic), actual handover distance, and moving speed of the UE. The value range of this parameter can be 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay.
Hystfor1J
HystFor2D
Issue 02 (2009-06-30)
7-17
7 Parameters
RAN Handover
Parameter id HystFor2F
Description Hysteresis value for the event 2F. The value of this parameter correlates with slow fading. The larger the value of this parameter, the smaller probability of ping-pong effect or wrong decision, but event 2F might not be triggered in time. In periodical report mode, this parameter is used to resist the ping-pong effect of event 2D (the quality of the currently used frequency is lower than the threshold) and event 2F (the estimated quality of the currently used frequency is higher than the threshold). Event 2D is used to enable the compressed mode and event 2F is used to disable the compressed mode. Therefore, Hystfor2D can be increased on the basis of recommended value and inter-frequency handover ping-pong effect statistics. Hystfor2F can also be increased to reduce frequent enabling or disabling of compressed mode and to avoid unnecessary updates of the active set. To set the values of the parameters, you should consider the following factors: radio environment (with slow fading characteristic), actual handover distance, and moving speed of the UE. The value range of this parameter can be 2 dB to 5 dB. In addition, this parameter is related to filter coefficient and trigger delay. Hysteresis value for the event 3A. The value of this parameter correlates with slow fading. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be avoided, but the speed of the handover algorithm to respond to signal change becomes lower. If the inter-RAT handover hysteresis is set to an excessively high value, the GSM cell to which the UE is handed over must be of good quality. Therefore, the conditions for triggering the inter-RAT handover decision are hard to be satisfied, and the call drop rate increases. The emulation result shows that in a cell where the average moving speed of UEs is high, for example a cell that covers highways, HystforInterRAT can be set to 1.5 dB, because in the cell the terrain is flat and there are few barriers , which causes small shadow fading variation. In a cell where the average moving speed of UEs is low, there are usually many tall buildings, so the shadow fading variation is comparatively big, and HystforInterRAT can be set to 3.0 dB. Hysteresis value for inter-RAT measurement periodical reports. This parameter aims to prevent the mis-decision caused by unexpected jitters of signals during inter-RAT handover decisions. The HystforInterRAT and the inter-RAT handover decision threshold determine whether to trigger inter-RAT handovers. The larger the value of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effect can be avoided, but the speed of the handover algorithm to respond to signal change becomes lower. If the inter-RAT handover hysteresis is set to an excessively high value, the GSM cell to which the UE is handed over must be of good quality. Therefore, the conditions for triggering the inter-RAT handover decision are hard to be satisfied, and the call drop rate increases. The emulation result shows that in a cell where the average moving speed of UEs is high, for example a cell that covers highways, HystforInterRAT can be set to 1.5 dB, because in the cell the terrain is flat and there are few barriers , which causes small shadow fading variation. In a cell where the average moving speed of UEs is low, there are usually many tall buildings, so the shadow fading variation is comparatively big, and HystforInterRAT can be set to 3.0 dB.
Hystfor3A
HystforInterRAT
7-18
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id IFAntiPingpangTimer Length
Description After the coverage based handover succeeds, to avoid the handover of the UE to another frequency due to the following factors: overload, speed estimation, MBMS channel reselection, and QoS, frequent handovers occur. The RNC will start the inter-frequency non-coverage based anti-ping-pong timer and prohibit the handover or measurement caused by the previous factors before the timeout of the timer. The larger this parameter, the better effect the anti-frequent handover. This, however, will affect the management policy of the cell or the quality of service felt by the users; the smaller this parameter, the more frequent the inter-frequency handover. Threshold to trigger inter-frequency measurement with measurement quantity of Ec/No for CS domain services. The inter-frequency measurement start Ec/No threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: moving speed of the UE and the cell radius. For CS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to activate compressed mode and start inter-frequency measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -17 dB; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -14 dB; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -12 dB. For the cell in which the UEs are moving at various speeds, this parameter should be set to -14 dB. Through emulation, the call drop rate remains low for the UEs moving at the speed of 120 km/h when this parameter is set to -14 dB. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger.
InterFreqCSThd2DEc N0
Issue 02 (2009-06-30)
7-19
7 Parameters
RAN Handover
Parameter id InterFreqCSThd2DR SCP
Description Threshold to trigger inter-frequency measurement with measurement quantity of RSCP for CS domain services. The inter-frequency measurement start RSCP threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the moving speed of the UE and the cell radius. For CS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to activate compressed mode and start inter-frequency measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -100 dBm; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -97 dBm; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -93 dBm. For the cell in which the UEs are moving at various speeds, this parameter should be set to -95 dBm. Through emulation, the call drop rate remains low for the UEs moving at the speed of 120 km/h when this parameter is set to -95 dBm. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. When the signals at the entrance to an elevator or a subway change too fast to perform handover, you should start the compressed mode earlier and set this parameter optimally to -90 dBm.
7-20
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqCSThd2FEc N0
Description Threshold to stop inter-frequency measurement with measurement quantity of Ec/No for CS domain services. The inter-frequency measurement stop Ec/No threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: moving speed of the UE and the cell radius. For CS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Threshold to stop inter-frequency measurement with measurement quantity of RSCP for CS domain services. The inter-frequency measurement stop RSCP threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the moving speed of the UE and the cell radius. For CS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. When the signals at the entrance to an elevator or a subway change too fast to perform handover, you should start the compressed mode earlier and set this parameter optimally to -85 dBm.
InterFreqCSThd2FRS CP
Issue 02 (2009-06-30)
7-21
7 Parameters
RAN Handover
Parameter id InterFreqHOSwitch
Description According to the cell inter-frequency hierarchical selection, the RNC chooses the proper inter-frequency measurement control parameters to implement coverage, speed estimation, and traffic absorption. INTER_FREQ_COV: coverage-based inter-frequency handover. INTER_FREQ_COV_NCOV: coverage-based inter-frequency handover, and non-coverage-based inter-frequency handover triggered by speed estimation. INTER_FREQ_TA: traffic-based inter-frequency handover, which includes the function similar to coverage-based inter-frequency handover. Threshold to trigger inter-frequency measurement with measurement quantity of Ec/No for PS domain HSPA services. The inter-frequency measurement start Ec/No threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: moving speed of the UE and the cell radius. For HSPA services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to activate the compressed mode and start inter-frequency measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -17 dB; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -14 dB; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -12 dB. For the cell in which the UEs are moving at various speeds, this parameter should be set to -14 dB. Through emulation, the call drop rate remains low for the UEs moving at the speed of 120 km/h when this parameter is set to -14 dB. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger.
InterFreqHThd2DEc N0
7-22
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqHThd2DRS CP
Description Threshold to trigger inter-frequency measurement with measurement quantity of RSCP for PS domain HSPA services. The inter-frequency measurement start RSCP threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the moving speed of the UE and the cell radius. For HSPA services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to activate the compressed mode and start inter-frequency measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -100 dBm; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -97 dBm; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -93 dBm. For the cell in which the UEs are moving at various speeds, this parameter should be set to -95 dBm. Through emulation, the call drop rate remains low for the UEs moving at the speed of 120 km/h when this parameter is set to -95 dBm. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. When the signals at the entrance to an elevator or a subway change too fast to perform handover, you should start the compressed mode earlier and set this parameter optimally to -90 dBm.
Issue 02 (2009-06-30)
7-23
7 Parameters
RAN Handover
Parameter id InterFreqHThd2FEcN 0
Description Threshold to stop inter-frequency measurement with measurement quantity of Ec/No for PS domain HSPA services. The inter-frequency measurement stop Ec/No threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: moving speed of the UE and the cell radius. For HSPA services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Threshold to stop inter-frequency measurement with measurement quantity of RSCP for PS domain HSPA services. The inter-frequency measurement stop RSCP threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the moving speed of the UE and the cell radius. For HSPA services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. When the signals at the entrance to an elevator or a subway change too fast to perform handover, you should start the compressed mode earlier and set this parameter optimally to -85 dBm.
InterFreqHThd2FRS CP
7-24
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqNCovHOTh dEcN0
Description Threshold of signal quality of the target frequency for triggering inter-frequency measurement. This parameter is used to set measurement control on the event 2C. The event 2C is triggered when the signal quality of the target frequency is above this threshold. Threshold to trigger inter-frequency measurement with measurement quantity of Ec/No for PS domain non-HSPA services. The inter-frequency measurement start Ec/No threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: moving speed of the UE and the cell radius. For PS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to activate the compressed mode and start inter-frequency measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -17 dB; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -14 dB; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -12 dB. For the cell in which the UEs are moving at various speeds, this parameter should be set to -14 dB. Through emulation, the call drop rate remains low for the UEs moving at the speed of 120 km/h when this parameter is set to -14 dB. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger.
InterFreqR99PsThd2 DEcN0
Issue 02 (2009-06-30)
7-25
7 Parameters
RAN Handover
Parameter id InterFreqR99PsThd2 DRSCP
Description Threshold to trigger inter-frequency measurement with measurement quantity of RSCP for PS domain non-HSPA services. The inter-frequency measurement start RSCP threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the moving speed of the UE and the cell radius. For PS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to activate the compressed mode and start inter-frequency measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -100 dBm; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -97 dBm; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -93 dBm. For the cell in which the UEs are moving at various speeds, this parameter should be set to -95 dBm. Through emulation, the call drop rate remains low for the UEs moving at the speed of 120 km/h when this parameter is set to -95 dBm. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. When the signals at the entrance to an elevator or a subway change too fast to perform handover, you should start the compressed mode earlier and set this parameter optimally to -90 dBm.
7-26
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqR99PsThd2 FEcN0
Description Threshold to stop inter-frequency measurement with measurement quantity of Ec/No for PS domain non-HSPA services. The inter-frequency measurement stop Ec/No threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: moving speed of the UE and the cell radius. For PS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Threshold to stop inter-frequency measurement with measurement quantity of RSCP for PS domain non-HSPA services. The inter-frequency measurement stop RSCP threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-frequency handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the moving speed of the UE and the cell radius. For PS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it means that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it means that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. When the signals at the entrance to an elevator or a subway change too fast to perform handover, you should start the compressed mode earlier and set this parameter optimally to -85 dBm.
InterFreqR99PsThd2 FRSCP
Issue 02 (2009-06-30)
7-27
7 Parameters
RAN Handover
Parameter id InterFreqRATSwitch
Description Cell-level switch for inter-frequency and inter-RAT handover. INTERFREQ: only measuring inter-frequency cells and performing inter-frequency handover. INTERRAT: only measuring GSM cells and performing inter-RAT handover . SIMINTERFREQRAT: measuring both inter-frequency and inter-RAT cells, performing inter-frequency or inter-RAT handover according to the type of the cell that first meets the handover decision condition. The parameter decides the handover for each cell when the inter-frequency and inter-RAT cells coexist. Threshold to trigger inter-RAT measurement with measurement quantity of Ec/No for CS domain services. The inter-RAT measurement start RSCP threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-RAT handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the speed of the UE and the cell radius. For CS domain services, when Ec/No is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to activate compressed mode and start inter-RAT measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -17 dB; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -14 dB; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -12 dB. For the cell in which the UEs are moving at various speeds, this parameter should be set to -14 dB. Through emulation, the call drop rate remains lower for the UEs moving at the speed of 120 km/h when this parameter is set to -14 dB. If the cell is a macro cell, it indicates that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it indicates that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Events 2D and 2F are the inter-RAT measurement start and stop switches, that is, the inter-RAT compressed mode start and stop switches. Because different service types may have different requirements on the signal quality and different inter-RAT handover policies to be used, the inter-RAT measurement start or stop thresholds are distinguished by CS, PS, and signaling services. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger.
InterRATCSThd2DE cN0
7-28
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterRATCSThd2DR SCP
Description Threshold to trigger inter-RAT measurement with measurement quantity of RSCP for CS domain services. For CS domain services, when RSCP is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to activate compressed mode and start inter-RAT measurement, if the UE reports the event 2D when the measured value is smaller than the value of this parameter. If you want to start the compressed mode earlier, set the threshold for event 2D larger. Otherwise, set the threshold for event 2D smaller; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. In most cases, UEs want to be maintained within a 3G network. Thus, the start threshold of the inter-RAT measurement is set smaller than that of the inter-frequency measurement. This facilitates the triggering of the inter-frequency handover. For scenarios where no inter-frequency neighboring cells or where inter-frequency coverage is not ample, the inter-RAT measurement start threshold should be set relatively larger so as to facilitate the triggering of inter-RAT measurement. Thus, call drops reduce. Threshold to stop inter-RAT measurement with measurement quantity of Ec/No for CS domain services. The inter-RAT measurement stop RSCP threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-RAT handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the speed of the UE and the cell radius. For CS domain services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it indicates that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it indicates that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Threshold to stop inter-RAT measurement with measurement quantity of RSCP for CS domain services. For CS domain services, when RSCP is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to deactivate compressed mode and stop inter-RAT measurement, if the UE reports the event 2F when the measured value is larger than the value of this parameter.
InterRATCSThd2FEc N0
InterRATCSThd2FR SCP
Issue 02 (2009-06-30)
7-29
7 Parameters
RAN Handover
Parameter id InterRATHOAttempt s
Description The maximum number of attempts to perform non-coverage-based inter-RAT handovers. This parameter specifies the maximum number of attempts for the RNC to perform inter-RAT handovers after a non-coverage-based inter-RAT handover failure. The handover attempts should involve the target cells that have not been tried but satisfy the handover conditions. Threshold to trigger inter-RAT measurement with measurement quantity of Ec/No for HSDPA services. The inter-frequency measurement start RSCP threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-RAT handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the speed of the UE and the cell radius. For HSDPA services, when Ec/No is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to activate compressed mode and start inter-RAT measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -17 dB; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -14 dB; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -12 dB. For the cell in which the UEs are moving at various speeds, this parameter should be set to -14 dB. Through emulation, the call drop rate remains lower for the UEs moving at the speed of 120 km/h when this parameter is set to -14 dB. If the cell is a macro cell, it indicates that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it indicates that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Events 2D and 2F are the inter-RAT measurement start and stop switches, that is, the inter-RAT compressed mode start and stop switches. Because different service types may have different requirements on the signal quality and different inter-RAT handover policies to be used, the inter-RAT measurement start or stop thresholds are distinguished by CS, PS, and signaling services. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger.
InterRATHThd2DEc N0
7-30
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterRATHThd2DRS CP
Description Threshold to trigger inter-RAT measurement with measurement quantity of RSCP for HSDPA services. For non-HSDPA services, when RSCP is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to activate compressed mode and start inter-RAT measurement, if the UE reports the event 2D when the measured value is smaller than the value of this parameter. If you want to start the compressed mode earlier, set the threshold for event 2D larger. Otherwise, set the threshold for event 2D smaller; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. In most cases, UEs want to be maintained within a 3G network. Thus, the start threshold of the inter-RAT measurement is set smaller than that of the inter-frequency measurement. This facilitates the triggering of the inter-frequency handover. For scenarios where no inter-frequency neighboring cells or where inter-frequency coverage is not ample, the inter-RAT measurement start threshold should be set relatively larger so as to facilitate the triggering of inter-RAT measurement. Thus, call drops reduce. Threshold to stop inter-RAT measurement with measurement quantity of Ec/No for HSDPA services. The inter-RAT measurement stop RSCP threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-RAT handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the speed of the UE and the cell radius. For HSPA services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it indicates that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it indicates that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Threshold to stop inter-RAT measurement with measurement quantity of RSCP for HSDPA services. For HSDPA services, when RSCP is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to deactivate compressed mode and stop inter-RAT measurement, if the UE reports the event 2F when the measured value is larger than the value of this parameter.
InterRATHThd2FEc N0
InterRATHThd2FRS CP
Issue 02 (2009-06-30)
7-31
7 Parameters
RAN Handover
Parameter id InterRATNCovHOPS Thd
Description Quality requirement for the inter-RAT cell during an inter-RAT handover with PS domain services. This parameter is used to set measurement control on the event 3C. The event 3C is triggered when the signal quality of the target frequency is above this threshold. Note that the value 0 indicates that the physical value is smaller than -110 dBm. If the periodical report mode is used, the inter-RAT handover decision thresholds are used for the assessment of inter-RAT coverage handover, namely as Tother_RAT in the following formulas. The inter-RAT handover decision thresholds are the absolute thresholds (RSSI) of inter-RAT cell quality for the inter-RAT handover decision. If the quality of another RAT in the inter-RAT measurement report meets the following condition: Mother_RAT + CIO >= Tother_RAT + H/2 the system starts the trigger timer and implements the handover decision after timeout. If the quality of the preceding RAT meets the following condition before timeout: Mother_RAT + CIO < Tother_RAT - H/2 The system stops the timer, and the RNC waits for another inter-RAT measurement report. In which, Mother_RAT indicates the measurement result of the GSM RSSI; Tother_RAT indicates the inter-RAT handover decision threshold; Cell Individual Offset (CIO) indicates the offset of the inter-RAT cell; H represents the hysteresis. Hysteresis can reduce wrong decisions caused by signal jitters. The sensitivity of a GSM mobile phone is -102 dBm, so the outdoor reception level should not be lower than -90 dBm, considering a margin of 3 dB for compensation of fast fading, 5 dB for compensation of slow fading, 2 dB for compensation of interference noise, and 2 dB for compensation of ambient noise. The values of inter-RAT handover decision thresholds vary with the handover policy. To have UEs hand over only to the GSM cells with high quality, you can set the inter-RAT handover decision threshold to a comparatively high value, for example -85 dBm. Inter-RAT ping-pong hysteresis. When a UE in the CS domain is handed over from a 2G network to a 3G network, the system increase 3A Hysteresis to prevent UE ping-pong handover between the 2G network and the 3G network in the period specified by this parameter. During the penalty time, the previous periodical report will be changed to the event 3A report. If this parameter is 0,the system will not start the ping-pong handover punish timer. Inter-RAT ping-pong timer. When a UE in the CS domain is handed over from a 2G network to a 3G network, the system increase 3A Hysteresis to prevent UE ping-pong handover between the 2G network and the 3G network in the period specified by this parameter. During the penalty time, the previous periodical report will be changed to the event 3A report. If this parameter is 0,the system will not start the ping-pong handover punish timer.
InterRATPingPongH yst
InterRATPingPongTi mer
7-32
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterRATR99PsThd2 DEcN0
Description Threshold to trigger inter-RAT measurement with measurement quantity of Ec/No for PS domain non-HSDPA services. The inter-frequency measurement start RSCP threshold (namely, compressed mode start threshold) is one of the key parameters in the inter-RAT handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the speed of the UE and the cell radius. For PS domain non-HSDPA services, when Ec/No is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to activate compressed mode and start inter-RAT measurement, if the UE reports event 2D when the measured value is smaller than the value of this parameter. For the UE moving at the speed of 5 km/h, it is recommended that this parameter be set to -17 dB; for the UE moving at the speed of 50 km/h, it is recommended that this parameter be set to -14 dB; for the UE moving at the speed of 120 km/h, it is recommended that this parameter be set to -12 dB. For the cell in which the UEs are moving at various speeds, this parameter should be set to -14 dB. Through emulation, the call drop rate remains lower for the UEs moving at the speed of 120 km/h when this parameter is set to -14 dB. If the cell is a macro cell, it indicates that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it indicates that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Events 2D and 2F are the inter-RAT measurement start and stop switches, that is, the inter-RAT compressed mode start and stop switches. Because different service types may have different requirements on the signal quality and different inter-RAT handover policies to be used, the inter-RAT measurement start or stop thresholds are distinguished by CS, PS, and signaling services. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger.
Issue 02 (2009-06-30)
7-33
7 Parameters
RAN Handover
Parameter id InterRATR99PsThd2 DRSCP
Description Threshold to trigger inter-RAT measurement with measurement quantity of RSCP for PS domain non-HSDPA services. For PS domain HSDPA services, when RSCP is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to activate compressed mode and start inter-RAT measurement, if the UE reports the event 2D when the measured value is smaller than the value of this parameter. If you want to start the compressed mode earlier, set the threshold for event 2D larger. Otherwise, set the threshold for event 2D smaller; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. In most cases, UEs want to be maintained within a 3G network. Thus, the start threshold of the inter-RAT measurement is set smaller than that of the inter-frequency measurement. This facilitates the triggering of the inter-frequency handover. For scenarios where no inter-frequency neighboring cells or where inter-frequency coverage is not ample, the inter-RAT measurement start threshold should be set relatively larger so as to facilitate the triggering of inter-RAT measurement. Thus, call drops reduce. Threshold to stop inter-RAT measurement with measurement quantity of Ec/No for PS domain non-HSDPA services. The inter-RAT measurement stop RSCP threshold (namely, compressed mode stop threshold) is one of the key parameters in the inter-RAT handover policy. This parameter affects the proportion of the UEs in compressed mode active status of a cell and the success rate of the hard handover. To set this parameter, you need to consider the following factors: the speed of the UE and the cell radius. For PS domain HSPA services, when Ec/No is used as the measurement quantity for inter-frequency measurement, the RNC sends the signaling to stop the compressed mode and the inter-frequency measurement, if the UE reports event 2F when the measured value is larger than the value of this parameter. If the cell is a macro cell, it indicates that micro cells exist in this cell. To enable the traffic absorption function of the micro cells, the compressed mode start threshold should be set higher and the stop threshold be set lower, that is, the threshold for event 2D/2F be set higher by using CPICH RSCP. If the cell is a micro cell, it indicates that the default value should be modified according to the link estimate result. Events 2D and 2F are the compressed mode start and stop switches. When the cell is located in the center of the frequency coverage or the inter-frequency measurement quantity is set to BOTH, Ec/No serves as the decision standard for events 2D and 2F. If you want to start the compressed mode earlier, set the threshold for event 2D larger; if you want to reduce the ping-pong effect of starting and stopping the compressed mode, set the difference between events 2D and 2F larger. Threshold to stop inter-RAT measurement with measurement quantity of RSCP for PS domain non-HSDPA services. For PS domain non-HSDPA services, when RSCP is used as the measurement quantity for inter-RAT measurement, the RNC sends the signaling to deactivate compressed mode and stop inter-RAT measurement, if the UE reports the event 2F when the measured value is larger than the value of this parameter.
InterRATR99PsThd2 FEcN0
InterRATR99PsThd2 FRSCP
7-34
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id IntraAblThdFor1FEc No
Description This parameter specifies the Ec/No absolute threshold of event 1F in the SHO algorithm, corresponding to the guarantee signal strength with QoS of basic service. The parameter affects the triggering of event 1F. Event 1F is used to trigger the emergency blind handover. If the best cell of the active set reports event 1F, which means that the active cell is very poor quality, then the blind handover is triggered as the last attempt before call drop. The emergency blind handover is a special occasion that requires on-site measurements on the scope of the pilot strength of the best cell at the location where the blind handover is triggered. Generally, this function need not be started, so the parameter is set to the lowest value by default, indicating that the blind handover is not triggered. The larger the set value is, the more easily the event 1F can be triggered. The smaller the set value is, the more difficultly the event 1F can be triggered. For the definition of event 1F, refer to 3GPP TS 25.331. As for the impact on network performance: The higher the threshold is, the more easily the event 1F can be triggered. The lower the threshold is, the more difficult the event 1F can be triggered. In real situations, the threshold can be adjusted according to the handover strategy and network coverage. This parameter specifies the RSCP absolute threshold of event 1F in the SHO algorithm, corresponding to the guarantee signal strength with the QoS of basic service. The parameter affects the triggering of event 1F. Event 1F is used to trigger the emergency blind handover. If the best cell of the active set reports event 1F, which means that the active cell is very poor quality, then the blind handover is triggered as the last attempt before call drop. The emergency blind handover is a special occasion that requires on-site measurements on the scope of the pilot strength of the best cell at the location where the blind handover is triggered. Generally, this function need not be started, so the parameter is set to the lowest value by default, indicating that the blind handover is not triggered. The larger the set value is, the more easily the event 1F can be triggered. The smaller the set value is, the more difficultly the event 1F can be triggered. For the definition of event 1F, refer to 3GPP TS 25.331. As for the impact on network performance: The higher the threshold is, the more easily the event 1F can be triggered. The lower the threshold is, the more difficult the event 1F can be triggered. In real situations, the threshold can be adjusted according to the handover strategy and network coverage. This parameter specifies the intra-frequency measurement quantity. It defines the reference measurement quantity for the UE to report event 1x. For events 1A, 1B, 1C, and 1D which adopt relative thresholds, the measurement quantity does not have great impact on the threshold values. For event 1F which adopts absolute threshold, the measurement quantity should be set based on the reality of the cell. If the cell is located in the center of the coverage area, the main factor that affects signal quality is intra-frequency interference. In this case, CPICH_EC/NO is recommended. If the cell is located at the border of the coverage area, the main factor that affects signal quality is the distance between the cell and the base station. In this case, CPICH_RSCP is recommended.
IntraAblThdFor1FRS CP
IntraFreqMeasQuantit y
Issue 02 (2009-06-30)
7-35
7 Parameters
RAN Handover
Parameter id IntraRelThdFor1ACS NVP
Description This parameter specifies the CS non-VP service relative threshold of event 1A. The higher the threshold is, the more easily the event 1A is triggered. The lower the threshold is, the harder the event 1A is triggered. For the definition of event 1A, refer to 3GPP TS 25.331. The relative threshold can directly affect the ratio of the UE involved in soft handover (SHO ratio). So the threshold should be wisely chosen to achieve smooth SHOs. The value of this parameter determines the SHO area and SHO ratio. For the CDMA system, the ratio of the UE involved in soft handover should reach 30% to 40% to ensure smooth handover. Based on simulation results, when the relative threshold is set to 5 dB, the ratio of the UE involved in soft handover (the number of cells in the active set is at least 2) is approximately 35%. It is recommended to set the relative threshold a little higher (5 dB to 7 dB) during site deployment, and to reduce the threshold when the users increase. But the threshold must be higher than 3 dB to avoid the ping-pong handover. In some specific applications, you can set different relative thresholds for event 1A and event 1B to reduce the ping-pong effect and the soft handover ratio. For example, if the ping-pong effect cannot be curbed by adjusting the hysteresis values for event 1A and event 1B, you can curb it by setting a higher relative threshold for event 1B than that for event 1A. In general applications, however, the relative thresholds for event 1A and 1B should be equal, and you can curb the ping-pong effect through the time-to-trigger, L3 filtering coefficient, and hysteresis. As for the impact on network performance: The value of this parameter determines the SHO area and the SHO ratio. The higher the threshold is, the more easily the target cell joins the active set, the harder the call drops, the larger the ratio of the UE involved in soft handover is, but the more the use of forward resources is. The lower the threshold is, the more difficult the target cell joins the active set. Thus the communication quality and the smooth handover cannot be guaranteed.
7-36
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id IntraRelThdFor1ACS VP
Description This parameter specifies the VP service relative threshold of event 1A. The higher the threshold is, the more easily the event 1A is triggered. The lower the threshold is, the harder the event 1A is triggered. For the definition of event 1A, refer to 3GPP TS 25.331. The relative threshold can directly affect the ratio of the UE involved in soft handover (SHO ratio). So the threshold should be wisely chosen to achieve smooth SHOs. The value of this parameter determines the SHO area and SHO ratio. For the CDMA system, the ratio of the UE involved in soft handover should reach 30% to 40% to ensure smooth handover. Based on simulation results, when the relative threshold is set to 5 dB, the ratio of the UE involved in soft handover (the number of cells in the active set is at least 2) is approximately 35%. It is recommended to set the relative threshold a little higher (5 dB to 7 dB) during site deployment, and to reduce the threshold when the users increase. But the threshold must be higher than 3 dB to avoid the ping-pong handover. In some specific applications, you can set different relative thresholds for event 1A and event 1B to reduce the ping-pong effect and the soft handover ratio. For example, if the ping-pong effect cannot be curbed by adjusting the hysteresis values for event 1A and event 1B, you can curb it by setting a higher relative threshold for event 1B than that for event 1A. In general applications, however, the relative thresholds for event 1A and 1B should be equal, and you can curb the ping-pong effect through the time-to-trigger, L3 filtering coefficient, and hysteresis. As for the impact on network performance: The value of this parameter determines the SHO area and the SHO ratio. The higher the threshold is, the more easily the target cell joins the active set, the harder the call drops, the larger the ratio of the UE involved in soft handover is, but the more the use of forward resources is. The lower the threshold is, the more difficult the target cell joins the active set. Thus the communication quality and the smooth handover cannot be guaranteed.
Issue 02 (2009-06-30)
7-37
7 Parameters
RAN Handover
Parameter id IntraRelThdFor1APS
Description This parameter specifies the PS service relative threshold of event 1A. The higher the threshold is, the more easily the event 1A is triggered. The lower the threshold is, the harder the event 1A is triggered. For the definition of event 1A, refer to 3GPP TS 25.331. The relative threshold can directly affect the ratio of the UE involved in soft handover (SHO ratio). So the threshold should be wisely chosen to achieve smooth SHOs. The value of this parameter determines the SHO area and SHO ratio. For the CDMA system, the ratio of the UE involved in soft handover should reach 30% to 40% to ensure smooth handover. Based on simulation results, when the relative threshold is set to 5 dB, the ratio of the UE involved in soft handover (the number of cells in the active set is at least 2) is approximately 35%. It is recommended to set the relative threshold a little higher (5 dB to 7 dB) during site deployment, and to reduce the threshold when the users increase. But the threshold must be higher than 3 dB to avoid the ping-pong handover. In some specific applications, you can set different relative thresholds for event 1A and event 1B to reduce the ping-pong effect and the soft handover ratio. For example, if the ping-pong effect cannot be curbed by adjusting the hysteresis values for event 1A and event 1B, you can curb it by setting a higher relative threshold for event 1B than that for event 1A. In general applications, however, the relative thresholds for event 1A and 1B should be equal, and you can curb the ping-pong effect through the time-to-trigger, L3 filtering coefficient, and hysteresis. As for the impact on network performance: The value of this parameter determines the SHO area and the SHO ratio. The higher the threshold is, the more easily the target cell joins the active set, the harder the call drops, the larger the ratio of the UE involved in soft handover is, but the more the use of forward resources is. The lower the threshold is, the more difficult the target cell joins the active set. Thus the communication quality and the smooth handover cannot be guaranteed.
7-38
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id IntraRelThdFor1BCS NVP
Description This parameter specifies the CS non-VP service relative threshold of event 1B. The lower the threshold is, the more easily the event 1B is triggered. The higher the threshold is, the harder the event 1B is triggered. For the definition of event 1B, refer to 3GPP TS 25.331. The relative threshold can directly affect the ratio of the UE involved in soft handover (SHO ratio). So the threshold should be wisely chosen to achieve smooth SHOs. The value of this parameter determines the SHO area and SHO ratio. For the CDMA system, the ratio of the UE involved in soft handover should reach 30% to 40% to ensure smooth handover. Based on simulation results, when the relative threshold is set to 5 dB, the ratio of the UE involved in soft handover (the number of cells in the active set is at least 2) is approximately 35%. It is recommended to set the relative threshold a little higher (5 dB to 7 dB) during site deployment, and to reduce the threshold when the users increase. But the threshold must be higher than 3 dB to avoid the ping-pong handover. In some specific applications, you can set different relative thresholds for event 1A and event 1B to reduce the ping-pong effect and the soft handover ratio. For example, if the ping-pong effect cannot be curbed by adjusting the hysteresis values for event 1A and event 1B, you can curb it by setting a higher relative threshold for event 1B than that for event 1A. In general applications, however, the relative thresholds for event 1A and 1B should be equal, and you can curb the ping-pong effect through the time-to-trigger, L3 filtering coefficient, and hysteresis. As for the impact on network performance: The value of this parameter determines the SHO area and the SHO ratio. The higher the threshold is, the more easily the target cell joins the active set, the harder the call drops, the larger the ratio of the UE involved in soft handover is, but the more the use of forward resources is. The lower the threshold is, the more difficult the target cell joins the active set. Thus the communication quality and the smooth handover cannot be guaranteed.
Issue 02 (2009-06-30)
7-39
7 Parameters
RAN Handover
Parameter id IntraRelThdFor1BCS VP
Description This parameter specifies the PS service relative threshold of event 1B. The lower the threshold is, the more easily the event 1B is triggered. The higher the threshold is, the harder the event 1B is triggered. For the definition of event 1B, refer to 3GPP TS 25.331. The relative threshold can directly affect the ratio of the UE involved in soft handover (SHO ratio). So the threshold should be wisely chosen to achieve smooth SHOs. The value of this parameter determines the SHO area and SHO ratio. For the CDMA system, the ratio of the UE involved in soft handover should reach 30% to 40% to ensure smooth handover. Based on simulation results, when the relative threshold is set to 5 dB, the ratio of the UE involved in soft handover (the number of cells in the active set is at least 2) is approximately 35%. It is recommended to set the relative threshold a little higher (5 dB to 7 dB) during site deployment, and to reduce the threshold when the users increase. But the threshold must be higher than 3 dB to avoid the ping-pong handover. In some specific applications, you can set different relative thresholds for event 1A and event 1B to reduce the ping-pong effect and the soft handover ratio. For example, if the ping-pong effect cannot be curbed by adjusting the hysteresis values for event 1A and event 1B, you can curb it by setting a higher relative threshold for event 1B than that for event 1A. In general applications, however, the relative thresholds for event 1A and 1B should be equal, and you can curb the ping-pong effect through the time-to-trigger, L3 filtering coefficient, and hysteresis. As for the impact on network performance: The value of this parameter determines the SHO area and the SHO ratio. The higher the threshold is, the more easily the target cell joins the active set, the harder the call drops, the larger the ratio of the UE involved in soft handover is, but the more the use of forward resources is. The lower the threshold is, the more difficult the target cell joins the active set. Thus the communication quality and the smooth handover cannot be guaranteed.
7-40
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id IntraRelThdFor1BPS
Description This parameter specifies the PS service relative threshold of event 1B. The lower the threshold is, the more easily the event 1B is triggered. The higher the threshold is, the harder the event 1B is triggered. For the definition of event 1B, refer to 3GPP TS 25.331. The relative threshold can directly affect the ratio of the UE involved in soft handover (SHO ratio). So the threshold should be wisely chosen to achieve smooth SHOs. The value of this parameter determines the SHO area and SHO ratio. For the CDMA system, the ratio of the UE involved in soft handover should reach 30% to 40% to ensure smooth handover. Based on simulation results, when the relative threshold is set to 5 dB, the ratio of the UE involved in soft handover (the number of cells in the active set is at least 2) is approximately 35%. It is recommended to set the relative threshold a little higher (5 dB to 7 dB) during site deployment, and to reduce the threshold when the users increase. But the threshold must be higher than 3 dB to avoid the ping-pong handover. In some specific applications, you can set different relative thresholds for event 1A and event 1B to reduce the ping-pong effect and the soft handover ratio. For example, if the ping-pong effect cannot be curbed by adjusting the hysteresis values for event 1A and event 1B, you can curb it by setting a higher relative threshold for event 1B than that for event 1A. In general applications, however, the relative thresholds for event 1A and 1B should be equal, and you can curb the ping-pong effect through the time-to-trigger, L3 filtering coefficient, and hysteresis. As for the impact on network performance: The value of this parameter determines the SHO area and the SHO ratio. The higher the threshold is, the more easily the target cell joins the active set, the harder the call drops, the larger the ratio of the UE involved in soft handover is, but the more the use of forward resources is. The lower the threshold is, the more difficult the target cell joins the active set. Thus the communication quality and the smooth handover cannot be guaranteed. DL SF threshold to limit CM. When DL SF limit CM indicator is TRUE, if the downlink spreading factor is less than or equal to this parameter value, the active set quality measurement is not allowed and CM function should be deactivated.When DL SF limit CM ind is TRUE, if CM is activated, the downlink spreading factor should be greater than this parameter value. This parameter specifies the maximum number of cells in the active set. This parameter can achieve the balance between the signal quality in the SHO area and the performance of the system. The more cells the active set contains, the larger macro diversity gain the user obtains in the SHO area, and the smaller the intra-frequency interference is. But in this case, the user occupies resources of several cells, which increases the amount of data to be processed by the system and lowers the system performance. To reduce intra-frequency interference, it is recommended to suitably increase the number of cells in the active sets for the hot-spot and micro cells, which have highly complex signals. For the cell that provides high speed services, suitably decreasing the number of cells in the active set can reduce the consumption of system resources.
LimitCMDlSFThd
MaxCellInActiveSet
Issue 02 (2009-06-30)
7-41
7 Parameters
RAN Handover
Parameter id MaxEdchCellInActiv eSet
Description This parameter determines the maximum number of links in the EDCH active set. When the RNC acts as the SRNC, the number of links in the EDCH active set for all the UEs under the RNC cannot exceed the parameter value. If the parameter value is too large, a lot of resources on the RAN side will be occupied as the same data is transferred over multiple EDCH links in macro diversity, thus affecting the system performance. If this parameter value is too small, insufficient combination gain can be achieved in macro diversity by the EDCH, which causes excessive retransmissions and affects the UE speed. Measurement quantity used in coverage-based inter-RAT measurement in event-3A-triggered reporting mode. - Ec/No: signal-to-noise ratio - RSCP: indicates the received signal code power CPICH_Ec/No indicates that the Ec/No measurement quantity is used for event 3A measurement. The physical unit is dB; CPICH_RSCP indicates that the RSCP measurement quantity is used for event 3A measurement. The physical unit is dBm. AUTO indicates that the EcN0 measurement quantity is used for event 3A measurement if RNC receives the Ec/No 2D firstly. The RSCP measurement quantity is used for event 3A measurement if RNC receives the RSCP 2D firstly. The algorithms with the above values represent are as follow: ALGORITHM_REQUIRED: Always reset the mac-hs no matter the cells in question are in the same NodeB or not. ALGORITHM_DEPEND_ON_LCG: Reset the mac-hs only when the cells in question are in the different local cell group. When this parameter is set to ON, and when the load of the GSM cell exceeds the related threshold, the RNC will stop the non-coverage based inter-RAT handover; when this parameter is set to OFF, the RNC will do reversely. This parameter determines whether to stop the non-coverage based handover from the UMTS network to the GSM network according to the load information of the GSM cell. When the GSM network can provide its load information to the UMTS network, the RNC determines whether to send the non-coverage based handover to the GSM cell according to the load information of the GSM cell and the load threshold of the GSM cell set in the UMTS cell. This parameter is invalid for the GSM network that cannot provide its load information to the UMTS network. Threshold for deciding that the UE is in high-mobility state. This parameter specifies a threshold for high-speed decision. After the UE reports event 1D, the UE is considered in high-mobility state if the number of changes of the best cell during [TFASTSPDEST] is larger than [NFASTSPDEST]. The smaller the value is, the more possibly the UE is decided in high-mobility state. Priority identifier of neighboring cells. TRUE indicates that the neighboring cell priority is valid in the algorithm of neighboring cell combination. FALSE indicates that the neighboring cell priority is invalid, and, in the algorithm of neighboring cell combination, the cell with invalid priority is the last one to be considered as the measurement object. Threshold for deciding whether the UE in low-mobility state. After the slow speed timer times out, the UE is considered in low-mobility state if the number of changes of the best cell caused by the UE reporting of event 1D during [TSLOWSPDEST] is smaller than [NSLOWSPDEST]. The larger the value is, the more possibly the UE is decided in low-mobility state.
MeasQuantityOf3A
NBMMachsResetAlg oSelSwitch
NcovHoOn2GldInd
NFastSpdEst
NprioFlag
NSlowSpdEst
7-42
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id PeriodFor2B
Description 2B event retry period. This parameter defines the length of the event 2B retry period. The smaller the value of this parameter, the more frequent the handover retry due to inter-frequency handover failure, and the faster the UE to be successfully handed over to the target cell whose load is restored, thus lowering the probability of call drops. In this case, however, frequent handover retry brings more load to the RNC system. Retry period for the event 2C. This parameter defines the length of the event 2C retry period. The smaller the value of this parameter, the more frequent the handover retry due to inter-frequency handover failure, and the faster the UE to be successfully handed over to the target cell whose load is restored. In this case, however, frequent handover retry brings more load to the RNC system. This parameter specifies the number of reporting times of event 1A for periodical reporting. When the actual reporting times exceeds the set value, the periodical reporting ends. This parameter specifies the number of reporting times of event 1C for periodical reporting. When the actual reporting times exceeds the set value, the periodical reporting ends. This parameter specifies the number of reporting times of event 1J for periodical reporting. When the actual reporting times exceeds the set value, the periodical reporting ends. PS domain Relocation GSM load THD. This parameter specifies the PS domain relocation GSM load threshold. When the GSM load policy is used, that is, when [NcovHoOn2GldInd] in SET INTERRATHONCOV is set to ON, the PS domain inter-system relocation out process will be stopped if the GSM system send its cell load to the RNC and the cell load exceeds the PS domain Reloc GSM load THD. Otherwise, the RNC does not stop the PS domain inter-system relocation out process. Indicating whether the cell allows PS service inter-RAT handover. ON: PS service inter-RAT handover is enabled. OFF: PS service inter-RAT handover is disabled. Service handover refers to the handover attribute and related parameter configuration on the network side for each service. When a service is established, the related measurements and inter-RAT handover are immediately triggered. These two switches are enabled only for service handover; generally, they are disabled by default. Note that the service handover is enabled only when the handover attribute is set to HO_TO_GSM_SHOULD_BE_PERFORM and PS service inter-RAT handover is set to ON. Both conditions are mandatory. For hybrid services, the service handover is not triggered. Identifying the type of the inter-RAT cell NO_CAPABILITY indicates that the capacity of the GSM cell remains unknown. It is not recommended to set the cell type to NO_CAPABILITY. If the cell type is NO_CAPABILITY, the inter-RAT handover cannot be triggered.
PeriodFor2C
PeriodMRReportNum for1A PeriodMRReportNum for1C PeriodMRReportNum for1J PSHOOut2GloadThd
PSServiceHOSwitch
RATCELLTYPE
Issue 02 (2009-06-30)
7-43
7 Parameters
RAN Handover
Parameter id RelThdForDwnGrd
Description This parameter specifies the threshold of immediate rate reduction after the soft handover failure. The rate reduction of the active set and the SHO retry procedure can be triggered without the intra-frequency reporting event reported, when the quality of the cell in the active set fulfills the following conditions. The formula of direct SHO rate reduction is new > Mbest_cell - RelThdForDwnGrd where Mnew: the CPICH Ec/No measurement value of the failed cell1 Mbest_cell: the CPICH Ec/No measurement value in the latest measurement report of the best cell identified by the RNC according to 1D RelThdForDwnGrd: the relative threshold for direct rate reduction. It can be configured on the BAM server. Note: The smaller the value of this parameter, the harder it is to trigger SHO rate reduction, but the greater intra-frequency interference caused by the cell that does not join the active set, the greater possibility of call drops. On the contrary, the larger the value of this parameter, the easier it is to trigger SHO rate reduction which ensures the signal quality. But, frequent triggering of SHO rate reduction may affect the use of the services. This parameter specifies the reporting period of event 1A. That is, event 1A is reported at each reporting interval. Usually, event 1A is reported only once. Nevertheless, if the cell, where event 1A is reported, does not join the active set in a specified period of time, the UE can change the reporting of event 1A into periodical mode.to avoid missing of measurement reports. The event 1A of this cell is reported for [PeriodMRReportNumfor1A] times with the reporting interval as the set value. This parameter specifies the number of reporting times of event 1C for periodical reporting. That is, event 1C is reported at each reporting interval. Usually, event 1C is reported only once. Nevertheless, if the cell, where event 1C is reported, does not join the active set in a specified period of time, the UE can change the reporting of event 1C into periodical mode.to avoid missing of measurement reports. The event 1C of this cell is reported for [PeriodMRReportNumfor1C] times with the reporting interval as the set value. This parameter specifies the number of reporting times of event 1J for periodical reporting. That is, event 1J is reported at each reporting interval. Usually, event 1J is reported only once. Nevertheless, if the cell, where event 1J is reported, does not join the EDCH active set in a specified period of time, the UE can change the reporting of event 1J into periodical mode.to avoid missing of measurement reports. The event 1J of this cell is reported for [PeriodMRReportNumfor1J] times with the reporting period as the set value. This parameter specifies the 2G cell capability required by inter-RAT handovers from 3G networks to 2G networks. If the 2G cell capability does not meet the requirement, the handover is not performed. In terms of the ability to support PS services, EDGE cells rank first, GPRS cells second, and GSM cells third. When the PS service is handed over to a 2G network, the service is set up at the closest rate that the 2G network supports.
ReportIntervalfor1A
ReportIntervalfor1C
ReportIntervalfor1J
Req2GCap
7-44
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id SHIND
Description This parameter specifies the handover attribute. If the SERVICE_HO_BASED_ON_RNC_SWITCH is on, the handover setting of this parameter is applied. Otherwise, the handover setting assigned by the CN is applied. - HO_TO_GSM_SHOULD_BE_PERFORM: Handover to the 2G network is performed so long as 2G signals are available. - HO_TO_GSM_SHOULD_NOT_BE_PERFORM: Handover to the 2G network is performed when 3G signals are weak but 2G signals are strong. - HO_TO_GSM_SHALL_NOT_BE_PERFORM: Handover to the 2G network is not performed even if 3G signals are weak but 2G signals are strong. This parameter specifies the threshold number of the soft handover failures. This parameter determines the reporting times of the events from the cell that fails to join the active set in soft handover, to trigger the rate reduction of the active set and the attempt to join the active set. The smaller the value of this parameter, the easier it is for the cell that fails to join the active set in the load based soft handover to join the active set through the soft handover rate reduction strategy, but the easier it is to trigger the rate reduction of the active set and thus to affect the use of services. Note that this parameter need be considered in combination with the rate reduction evaluation period, and the reporting intervals of event 1A and 1C. Otherwise, the reports cannot reach the required times to trigger rate reduction during the rate reduction evaluation period. This parameter specifies the maximum evaluation period of the soft handover failure. When the rate reduction evaluation is performed on a cell that fails to join the active set, the evaluation timer is started. If the cell cannot fulfill the condition of rate reduction before the timer expires, the evaluation and rate reduction retry on the cell will not be performed. The larger the value of the parameter, the greater the possibility that the target cell joins the active set. But only three parallel soft handover rate reduction evaluation processes are allowed on the RNC. The larger the value of this parameter, the less the failure cells that the RNC can handle. When it is set to ON, the RNC sends UMTS cell load information to the GSM during the non-coverage based system relocation in or out process. When it is set to OFF, the RNC does not send UMTS cell load information to the GSM during the system relocation in or out process. This parameter is designed for the UMTS network to cooperate with the GSM network. When the UE is handed over from the UMTS network to the GSM network, the RNC normalizes the load information of the best cell and sends it to the GSM network. Then, the GSM network determines whether to accept or reject the handover request.This switch is only effective in CS domain,the RNC does not send UMTS cell load information to the GSM in PS domain. Identifying whether the inter-RAT cell supports PS HO. TRUE indicates that the inter-RAT cell is able to perform the handover procedure with relocation. FALSE indicates that the cell is unable to do so. Identifying whether the inter-RAT cell supports RIM. (RIM is used to obtain the SI/PSI information of the inter-RAT cell.) For the details of RIM process, refer to the 3GPP TS 25.901 protocol.
ShoFailNumForDwn Grd
ShoFailPeriod
SndLdInfo2GsmInd
SuppPSHOFlag
SuppRIMFlag
Issue 02 (2009-06-30)
7-45
7 Parameters
RAN Handover
Parameter id TargetFreqCsThdEcN 0
Description Threshold of the target frequency for triggering inter-frequency measurement with measurement quantity of Ec/No for CS domain services. For CS domain services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions for triggering event 2B can be met only when the quality of the target frequency is higher than this threshold. If the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-frequency handovers at the RNC. To set this parameter, you need to consider the following factors: The cell signal quality of the target frequency is better and can meet the coverage requirements of the current services. After handover, to prevent ping-pong handover, the inter-frequency measurement should not be started again. That is, this parameter is usually set higher than the start threshold for event 2D or equal to the threshold of event 2F. Threshold of the target frequency for triggering inter-frequency measurement with measurement quantity of RSCP for CS domain services. For CS domain services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions for triggering event 2B can be met only when the quality of the target frequency is higher than this threshold. If the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-frequency handovers at the RNC. To set this parameter, you need to consider the following factors: The cell signal quality of the target frequency is better and can meet the coverage requirements of the current services. After handover, to prevent ping-pong handover, the inter-frequency measurement should not be started again. That is, this parameter is usually set higher than the trigger threshold for event 2D or equal to the threshold of event 2F. Threshold of the target frequency for triggering inter-frequency measurement with measurement quantity of Ec/No for PS domain HSPA services. For HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions for triggering event 2B can be met only when the quality of the target frequency is higher than this threshold. If the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-frequency handovers at the RNC. To set this parameter, you need to consider the following factors: The cell signal quality of the target frequency is better and can meet the coverage requirements of the current services. After handover, to prevent ping-pong handover, the inter-frequency measurement should not be started again. That is, this parameter is usually set higher than the start threshold for event 2D or equal to the threshold of event 2F.
TargetFreqCsThdRsc p
TargetFreqHThdEcN 0
7-46
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TargetFreqHThdRscp
Description Threshold of the target frequency for triggering inter-frequency measurement with measurement quantity of RSCP for PS domain HSPA services. For HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions for triggering event 2B can be met only when the quality of the target frequency is higher than this threshold. If the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-frequency handovers at the RNC. To set this parameter, you need to consider the following factors: The cell signal quality of the target frequency is better and can meet the coverage requirements of the current services. After handover, to prevent ping-pong handover, the inter-frequency measurement should not be started again. That is, this parameter is usually set higher than the trigger threshold for event 2D or equal to the threshold of event 2F. Threshold of the target frequency for triggering inter-frequency measurement with measurement quantity of Ec/No for PS domain non-HSPA services. For PS domain non-HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions for triggering event 2B can be met only when the quality of the target frequency is higher than this threshold. If the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-frequency handovers at the RNC. To set this parameter, you need to consider the following factors: The cell signal quality of the target frequency is better and can meet the coverage requirements of the current services. After handover, to prevent ping-pong handover, the inter-frequency measurement should not be started again. That is, this parameter is usually set higher than the trigger threshold for event 2D or equal to the threshold of event 2F. Threshold of the target frequency for triggering inter-frequency measurement with measurement quantity of RSCP for PS domain non-HSPA services. For PS domain non-HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions for triggering event 2B can be met only when the quality of the target frequency is higher than this threshold. If the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-frequency handovers at the RNC. To set this parameter, you need to consider the following factors: The cell signal quality of the target frequency is better and can meet the coverage requirements of the current services. After handover, to prevent ping-pong handover, the inter-frequency measurement should not be started again. That is, this parameter is usually set higher than the trigger threshold for event 2D or equal to the threshold of event 2F.
TargetFreqR99PsThd EcN0
TargetFreqR99PsThd Rscp
Issue 02 (2009-06-30)
7-47
7 Parameters
RAN Handover
Parameter id TargetRatCsThd
Description Quality requirement for the inter-RAT cell during an inter-RAT handover with CS domain services. For CS domain services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 3A. One of the necessary conditions for triggering event 3A can be met only when the quality of the target frequency is higher than this threshold. The event 3A can be triggered only when the requirements of frequency quality threshold of relevant measurement quantity of the CS domain services are met; if the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-RAT coverage handovers at the RNC. Note that the value 0 means the physical value is smaller than -110 dBm. If the periodical report mode is used, the inter-RAT handover decision thresholds are used for the assessment of inter-RAT coverage handover, namely as Tother_RAT in the following formulas. The inter-RAT handover decision thresholds are the absolute thresholds (RSSI) of inter-RAT cell quality for the inter-RAT handover decision. If the quality of another RAT in the inter-RAT measurement report meets the following condition: Mother_RAT + CIO >= Tother_RAT + H/2 the system starts the trigger timer and implements the handover decision after timeout. If the quality of the preceding RAT meets the following condition before timeout: Mother_RAT + CIO < Tother_RAT - H/2 The system stops the timer, and the RNC waits for another inter-RAT measurement report. In which, Mother_RAT indicates the measurement result of the GSM RSSI; Tother_RAT indicates the inter-RAT handover decision threshold; Cell Individual Offset (CIO) indicates the offset of the inter-RAT cell; H represents the hysteresis. Hysteresis can reduce wrong decisions caused by signal jitters. The sensitivity of a GSM mobile phone is -102 dBm, so the outdoor reception level should not be lower than -90 dBm, considering a margin of 3 dB for compensation of fast fading, 5 dB for compensation of slow fading, 2 dB for compensation of interference noise, and 2 dB for compensation of ambient noise. The values of inter-RAT handover decision thresholds vary with the handover policy. To have UEs hand over only to the GSM cells with high quality, you can set the inter-RAT handover decision threshold to a comparatively high value, for example -85 dBm.
7-48
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TargetRatHThd
Description Quality requirement for the inter-RAT cell during an inter-RAT handover with HSDPA services. For PS domain services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 3A. One of the necessary conditions for triggering event 3A can be met only when the quality of the target frequency is higher than this threshold. The event 3A can be triggered only when the requirements of frequency quality threshold of relevant measurement quantity of the PS domain services are met; if the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-RAT coverage handovers at the RNC. Note that the value 0 means the physical value is smaller than -110 dBm. If the periodical report mode is used, the inter-RAT handover decision thresholds are used for the assessment of inter-RAT coverage handover, namely as Tother_RAT in the following formulas. The inter-RAT handover decision thresholds are the absolute thresholds (RSSI) of inter-RAT cell quality for the inter-RAT handover decision. If the quality of another RAT in the inter-RAT measurement report meets the following condition: Mother_RAT + CIO >= Tother_RAT + H/2 the system starts the trigger timer and implements the handover decision after timeout. If the quality of the preceding RAT meets the following condition before timeout: Mother_RAT + CIO < Tother_RAT - H/2 The system stops the timer, and the RNC waits for another inter-RAT measurement report. In which, Mother_RAT indicates the measurement result of the GSM RSSI; Tother_RAT indicates the inter-RAT handover decision threshold; Cell Individual Offset (CIO) indicates the offset of the inter-RAT cell; H represents the hysteresis. Hysteresis can reduce wrong decisions caused by signal jitters. The sensitivity of a GSM mobile phone is -102 dBm, so the outdoor reception level should not be lower than -90 dBm, considering a margin of 3 dB for compensation of fast fading, 5 dB for compensation of slow fading, 2 dB for compensation of interference noise, and 2 dB for compensation of ambient noise. The values of inter-RAT handover decision thresholds vary with the handover policy. To have UEs hand over only to the GSM cells with high quality, you can set the inter-RAT handover decision threshold to a comparatively high value, for example -85 dBm.
Issue 02 (2009-06-30)
7-49
7 Parameters
RAN Handover
Parameter id TargetRatR99PsThd
Description Quality requirement for the inter-RAT cell during an inter-RAT handover with PS domain non-HSDPA services. For PS domain non-HSDPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 3A. One of the necessary conditions for triggering event 3A can be met only when the quality of the target frequency is higher than this threshold. The event 3A can be triggered only when the requirements of frequency quality threshold of relevant measurement quantity of the PS domain services are met; if the value of [Inter-frequency measure report mode] is set to PERIODICAL_REPORTING, this parameter is used to evaluate inter-RAT coverage handovers at the RNC. Note that the value 0 means the physical value is smaller than -110 dBm. If the periodical report mode is used, the inter-RAT handover decision thresholds are used for the assessment of inter-RAT coverage handover, namely as Tother_RAT in the following formulas. The inter-RAT handover decision thresholds are the absolute thresholds (RSSI) of inter-RAT cell quality for the inter-RAT handover decision. If the quality of another RAT in the inter-RAT measurement report meets the following condition: Mother_RAT + CIO >= Tother_RAT + H/2 the system starts the trigger timer and implements the handover decision after timeout. If the quality of the preceding RAT meets the following condition before timeout: Mother_RAT + CIO < Tother_RAT - H/2 The system stops the timer, and the RNC waits for another inter-RAT measurement report. In which, Mother_RAT indicates the measurement result of the GSM RSSI; Tother_RAT indicates the inter-RAT handover decision threshold; Cell Individual Offset (CIO) indicates the offset of the inter-RAT cell; H represents the hysteresis. Hysteresis can reduce wrong decisions caused by signal jitters. The sensitivity of a GSM mobile phone is -102 dBm, so the outdoor reception level should not be lower than -90 dBm, considering a margin of 3 dB for compensation of fast fading, 5 dB for compensation of slow fading, 2 dB for compensation of interference noise, and 2 dB for compensation of ambient noise. The values of inter-RAT handover decision thresholds vary with the handover policy. To have UEs hand over only to the GSM cells with high quality, you can set the inter-RAT handover decision threshold to a comparatively high value, for example -85 dBm. Cycle timer for deciding whether the UE is in low-mobility state. This timer provides the time for the RNC to decide whether the UE is in low-mobility state. The smaller the value is, the more frequently the state estimation is triggered. If the parameter is set to 0, it is an indication that the state estimation is not triggered. Time window for estimating whether the UE is in high-mobility state. The start point of the estimation is the moment of the last reporting of event 1D, and the backdated time length is determined by this parameter. If the parameter is set to 0, the RNC does not decide whether the UE is in high-mobility state.
TCycleSlow
TFastSpdEst
7-50
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TimeToTrig2B
Description Time delay to trigger event 2B. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of event 2B to the change of measured signals. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. The value of this parameter can be adjusted according to the actual network statistics. Time delay to trigger event 2D. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of event 2D to the change of measured signals. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. The value of this parameter can be adjusted according to the actual network statistics. Time delay to trigger the event 2F. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of event 2F to the change of measured signals. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. The value of this parameter can be adjusted according to the actual network statistics.
TimeToTrig2D
TimeToTrig2F
Issue 02 (2009-06-30)
7-51
7 Parameters
RAN Handover
Parameter id TRelateLength
Description Related length for 1D records in the best cells. In the speed estimation algorithm, an algorithm is adopted to avoid inaccurate estimation caused by frequent handovers of best cells. That is, during the latest [TRELATELENGTH], if more than one event 1D of a certain cell occurs, the event 1D record is restored to the state when the 1st event 1D occurs during the latest [TRELATELENGTH]. The given time length is set by this parameter. If the value is set too large, the RNC judges a non-frequently changing best cell change as a frequently changing one by mistake. If the value is set too small, the speed estimation algorithm may be invalid. It is recommended that this value be set according to the cell radius.
7-52
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TrigTime1A
Description This parameter specifies the time delay to trigger event 1A. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event to measurement signal change. The purposes of the time-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burst signals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading on event decisions. The hysteresis can effectively reduce the average number of handovers and wrong decisions, and avoid unnecessary handovers. As for the impact on network performance: The larger the value of this parameter, the smaller the average number of handovers, and the greater the possibility of call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physical layer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 ms is invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. Different events require different values of the time-to-trigger parameter: the event (1A) of adding cells to the active set requires a comparatively short delay; the events of replacing cells in the active set (1C and 1D) require relatively fewer ping-pong and wrong handovers and have no big impact on the call drop rate, and therefore TrigTime1C and TrigTime1D can be set to comparatively high values; the events of deleting cells in the active set (1B and 1F) require fewer ping-pong handovers, so the initial settings of TrigTime1B can be the same as TrigTime1A and can be adjusted according to the actual network statistics. For the macro cell, the recommended adjustment range is as follows: Table 1. Typical time-to-trigger of 1B or 1F of various channels At the speed of 5 (km/h): the range is 640~1280 (ms), the recommended value is 1280 (ms). At the speed of 50 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). At the speed of 120 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). For typical configuration: the range is 640~1280 (ms), the recommended value is 640 (ms). For the micro cell, the time-to-trigger should be shortened correspondingly. If the handover is not triggered in time, set TrigTime1A to 200 ms or 100 ms, and set TrigTime1B to 1280 ms or 2560 ms. Reducing the value of TrigTime1A can decrease the call drops when there is not enough time for performing handover. Increasing the value of TrigTime1B results in decreasing of the average number of handovers, thus part of the call drops resulted from the ping-pong handover can be eliminated. But, these adjustments may cause the growth of the SHO ratio, and the over use of the forward resources.
Issue 02 (2009-06-30)
7-53
7 Parameters
RAN Handover
Parameter id TrigTime1B
Description This parameter specifies the time delay to trigger event 1B. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event to measurement signal change. The purposes of the time-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burst signals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading on event decisions. The hysteresis can effectively reduce the average number of handovers and wrong decisions, and avoid unnecessary handovers. As for the impact on network performance: The larger the value of this parameter, the smaller the average number of handovers, and the greater the possibility of call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physical layer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 ms is invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. Different events require different values of the time-to-trigger parameter: the event (1A) of adding cells to the active set requires a comparatively short delay; the events of replacing cells in the active set (1C and 1D) require relatively fewer ping-pong and wrong handovers and have no big impact on the call drop rate, and therefore TrigTime1C and TrigTime1D can be set to comparatively high values; the events of deleting cells in the active set (1B and 1F) require fewer ping-pong handovers, so the initial settings of TrigTime1B can be the same as TrigTime1A and can be adjusted according to the actual network statistics. For the macro cell, the recommended adjustment range is as follows: Table 1. Typical time-to-trigger of 1B or 1F of various channels At the speed of 5 (km/h): the range is 640~1280 (ms), the recommended value is 1280 (ms). At the speed of 50 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). At the speed of 120 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). For typical configuration: the range is 640~1280 (ms), the recommended value is 640 (ms). For the micro cell, the time-to-trigger should be shortened correspondingly. If the handover is not triggered in time, set TrigTime1A to 200 ms or 100 ms, and set TrigTime1B to 1280 ms or 2560 ms. Reducing the value of TrigTime1A can decrease the call drops when there is not enough time for performing handover. Increasing the value of TrigTime1B results in decreasing of the average number of handovers, thus part of the call drops resulted from the ping-pong handover can be eliminated. But, these adjustments may cause the growth of the SHO ratio, and the over use of the forward resources.
7-54
02 (2009-06-30)
RAN Handover
7 Parameters
Description This parameter specifies the time delay to trigger event 1C. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event to measurement signal change. The purposes of the time-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burst signals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading on event decisions. The hysteresis can effectively reduce the average number of handovers and wrong decisions, and avoid unnecessary handovers. As for the impact on network performance: The larger the value of this parameter, the smaller the average number of handovers, and the greater the possibility of call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physical layer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 ms is invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. Different events require different values of the time-to-trigger parameter: the event (1A) of adding cells to the active set requires a comparatively short delay; the events of replacing cells in the active set (1C and 1D) require relatively fewer ping-pong and wrong handovers and have no big impact on the call drop rate, and therefore TrigTime1C and TrigTime1D can be set to comparatively high values; the events of deleting cells in the active set (1B and 1F) require fewer ping-pong handovers, so the initial settings of TrigTime1B can be the same as TrigTime1A and can be adjusted according to the actual network statistics. For the macro cell, the recommended adjustment range is as follows: Table 1. Typical time-to-trigger of 1B or 1F of various channels At the speed of 5 (km/h): the range is 640~1280 (ms), the recommended value is 1280 (ms). At the speed of 50 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). At the speed of 120 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). For typical configuration: the range is 640~1280 (ms), the recommended value is 640 (ms). For the micro cell, the time-to-trigger should be shortened correspondingly. If the handover is not triggered in time, set TrigTime1A to 200 ms or 100 ms, and set TrigTime1B to 1280 ms or 2560 ms. Reducing the value of TrigTime1A can decrease the call drops when there is not enough time for performing handover. Increasing the value of TrigTime1B results in decreasing of the average number of handovers, thus part of the call drops resulted from the ping-pong handover can be eliminated. But, these adjustments may cause the growth of the SHO ratio, and the over use of the forward resources.
Issue 02 (2009-06-30)
7-55
7 Parameters
RAN Handover
Parameter id TrigTime1D
Description This parameter specifies the time delay to trigger event 1D. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event to measurement signal change. The purposes of the time-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burst signals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading on event decisions. The hysteresis can effectively reduce the average number of handovers and wrong decisions, and avoid unnecessary handovers. As for the impact on network performance: The larger the value of this parameter, the smaller the average number of handovers, and the greater the possibility of call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physical layer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 ms is invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. Different events require different values of the time-to-trigger parameter: the event (1A) of adding cells to the active set requires a comparatively short delay; the events of replacing cells in the active set (1C and 1D) require relatively fewer ping-pong and wrong handovers and have no big impact on the call drop rate, and therefore TrigTime1C and TrigTime1D can be set to comparatively high values; the events of deleting cells in the active set (1B and 1F) require fewer ping-pong handovers, so the initial settings of TrigTime1B can be the same as TrigTime1A and can be adjusted according to the actual network statistics. For the macro cell, the recommended adjustment range is as follows: Table 1. Typical time-to-trigger of 1B or 1F of various channels At the speed of 5 (km/h): the range is 640~1280 (ms), the recommended value is 1280 (ms). At the speed of 50 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). At the speed of 120 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). For typical configuration: the range is 640~1280 (ms), the recommended value is 640 (ms). For the micro cell, the time-to-trigger should be shortened correspondingly. If the handover is not triggered in time, set TrigTime1A to 200 ms or 100 ms, and set TrigTime1B to 1280 ms or 2560 ms. Reducing the value of TrigTime1A can decrease the call drops when there is not enough time for performing handover. Increasing the value of TrigTime1B results in decreasing of the average number of handovers, thus part of the call drops resulted from the ping-pong handover can be eliminated. But, these adjustments may cause the growth of the SHO ratio, and the over use of the forward resources.
7-56
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TrigTime1F
Description This parameter specifies the time delay to trigger 1F. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event to measurement signal change. The purposes of the time-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burst signals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading on event decisions. The hysteresis can effectively reduce the average number of handovers and wrong decisions, and avoid unnecessary handovers. As for the impact on network performance: The larger the value of this parameter, the smaller the average number of handovers, and the greater the possibility of call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physical layer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 ms is invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. Different events require different values of the time-to-trigger parameter: the event (1A) of adding cells to the active set requires a comparatively short delay; the events of replacing cells in the active set (1C and 1D) require relatively fewer ping-pong and wrong handovers and have no big impact on the call drop rate, and therefore TrigTime1C and TrigTime1D can be set to comparatively high values; the events of deleting cells in the active set (1B and 1F) require fewer ping-pong handovers, so the initial settings of TrigTime1B can be the same as TrigTime1A and can be adjusted according to the actual network statistics. For the macro cell, the recommended adjustment range is as follows: Table 1. Typical time-to-trigger of 1B or 1F of various channels At the speed of 5 (km/h): the range is 640~1280 (ms), the recommended value is 1280 (ms). At the speed of 50 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). At the speed of 120 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). For typical configuration: the range is 640~1280 (ms), the recommended value is 640 (ms). For the micro cell, the time-to-trigger should be shortened correspondingly. If the handover is not triggered in time, set TrigTime1A to 200 ms or 100 ms, and set TrigTime1B to 1280 ms or 2560 ms. Reducing the value of TrigTime1A can decrease the call drops when there is not enough time for performing handover. Increasing the value of TrigTime1B results in decreasing of the average number of handovers, thus part of the call drops resulted from the ping-pong handover can be eliminated. But, these adjustments may cause the growth of the SHO ratio, and the over use of the forward resources.
Issue 02 (2009-06-30)
7-57
7 Parameters
RAN Handover
Parameter id TrigTime1J
Description This parameter specifies the time delay to trigger event 1J. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of event to the change of measured signals. The purposes of the time-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burst signals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading on event decisions. The hysteresis can effectively reduce the average number of handovers and wrong decisions, and avoid unnecessary handovers. As for the impact on network performance: The larger the value of this parameter, the smaller the average number of handovers, and the greater the possibility of call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physical layer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 ms is invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. Different events require different values of the time-to-trigger parameter: the event (1A) of adding cells to the active set requires a comparatively short delay; the events of replacing cells in the active set (1C and 1D) require relatively fewer ping-pong and wrong handovers and have no big impact on the call drop rate, and therefore TrigTime1C and TrigTime1D can be set to comparatively high values; the events of deleting cells in the active set (1B and 1F) require fewer ping-pong handovers, so the initial settings of TrigTime1B can be the same as TrigTime1A and can be adjusted according to the actual network statistics. For the macro cell, the recommended adjustment range is as follows: Table 1. Typical time-to-trigger of 1B or 1F of various channels At the speed of 5 (km/h): the range is 640~1280 (ms), the recommended value is 1280 (ms). At the speed of 50 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). At the speed of 120 (km/h): the range is 240~640 (ms), the recommended value is 640 (ms). For typical configuration: the range is 640~1280 (ms), the recommended value is 640 (ms). For the micro cell, the time-to-trigger should be shortened correspondingly. If the handover is not triggered in time, set TrigTime1A to 200 ms or 100 ms, and set TrigTime1B to 1280 ms or 2560 ms. Reducing the value of TrigTime1A can decrease the call drops when there is not enough time for performing handover. Increasing the value of TrigTime1B results in decreasing of the average number of handovers, thus part of the call drops resulted from the ping-pong handover can be eliminated. But, these adjustments may cause the growth of the SHO ratio, and the over use of the forward resources.
7-58
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TrigTime2F
Description Time delay to trigger the event 2F. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower probability of incorrect decision, but the slower the response of event 2F to the change of measured signals. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas for the cell with most of the slow-moving UEs, this parameter can be set larger. The value of this parameter can be adjusted according to the actual network statistics. Time delay to trigger the event 3A. The value of this parameter correlates with slow fading. The larger the value of this parameter, the lower the incorrect decision probability, but the slower the response of the event 3A to measurement signal change. Based on the existing emulation result, the hysteresis value is set to effectively reduce the average number of handovers and the number of wrong handovers, thus preventing unnecessary handovers. In addition, from the emulation perspective, the UE at different rates may react differently to the hysteresis value for the event. For the fast-moving UE, the call drop rate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate is less sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers. Thus, set the value smaller for cells where fast-moving UEs are dominant, whereas set the value bigger for cells where slow-moving UEs are dominant. The value of this parameter can be adjusted according to the actual network statistics. Because the report period of inter-frequency measurement is 480 ms, the trigger time period shorter than 480 ms is invalid. The bigger the time-to-trigger values are, the lower the average handover frequency is; but the increase of the time-to-trigger values increases the risk of call drops. Time window for deciding whether the UE is in low-mobility state. Every time the slow speed cycle timer times out, the RNC estimates whether the UE is in low-mobility state. The backdated time length is set by this parameter. Timer length for uplink Qos measurement. This parameter controls the time lengths for the inter-frequency and inter-RAT measurement based on Qos. After inter-frequency or inter-RAT measurement starts, if no inter-frequency handover is performed when this timer expires, the measurement is stopped, and the compressed mode is deactivated, if any. If this parameter is set to 0, this indicates that the timer will not be started. For the inter-frequency or inter-RAT measurement based on coverage, the compressed mode can be stopped through reporting event 2F. For measurement that is not based on coverage, event 2F is not reported, and the timer must be set but should not be set to 0. As for the impact on network performance: It reduces the influence of long time compressed mode to the serving cell. The compressed mode may be stopped ahead of time, which can cause the result that the UE fails to initiate inter-frequency or inter-RAT handover, and thus can lead to call drops.
TrigTime3A
TSlowSpdEst
ULQosMcTimerLen
Issue 02 (2009-06-30)
7-59
7 Parameters
RAN Handover
Parameter id UlSFTurnPoint
Description CM implementation approach selection basis. When the uplink spreading factor is greater than or equal to this parameter value, the SF/2 approach will be preferred. Otherwise, the high layer scheduling will be preferred. The SF/2 approach consumes more system resources and therefore this approach is recommended only for low-rate users. The high-layer scheduling requires variable multiplexing positions of transport channels and is applicable to a relatively narrow range. In addition, this approach affects the transmission rate of users and therefore is recommended only when the SF/2 approach is unavailable or there are high-rate users. Threshold of used frequency quality for triggering inter-frequency measurement with measurement quantity of Ec/No for CS domain services. For CS domain services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions can be met only when the quality of the used frequency is lower than this threshold (Event 2B can be triggered only when both conditions are met.) To set this parameter, you need to consider the following factors: The cell signal quality of the used frequency is better and can meet the coverage requirements of the current services. After handover, even if the inter-frequency measurement is triggered again, it is very difficult to hand over the UE again to the cell of currently used frequency. That is, this parameter is usually set lower than the start threshold for event 2F or equal to the threshold of event 2D. Threshold of used frequency quality for triggering inter-frequency measurement with measurement quantity of RSCP for CS domain services. For CS domain services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions can be met only when the quality of the used frequency is lower than this threshold (Event 2B can be triggered only when both conditions are met.) To set this parameter, you need to consider the following factors: The cell signal quality of the used frequency is better and can meet the coverage requirements of the current services. After handover, even if the inter-frequency measurement is triggered again, it is very difficult to hand over the UE again to the cell of currently used frequency. That is, this parameter is usually set lower than the start threshold for event 2F or equal to the threshold of event 2D. Threshold of used frequency quality for triggering inter-frequency measurement with measurement quantity of Ec/No for PS domain HSPA services. For HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions can be met only when the quality of the used frequency is lower than this threshold (Event 2B can be triggered only when both conditions are met.) To set this parameter, you need to consider the following factors: The cell signal quality of the used frequency is better and can meet the coverage requirements of the current services. After handover, even if the inter-frequency measurement is triggered again, it is very difficult to hand over the UE again to the cell of currently used frequency. That is, this parameter is usually set lower than the start threshold for event 2F or equal to the threshold of event 2D.
UsedFreqCSThdEcN 0
UsedFreqCSThdRSC P
UsedFreqHThdEcN0
7-60
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id UsedFreqHThdRSCP
Description Threshold of used frequency quality for triggering inter-frequency measurement with measurement quantity of RSCP for PS domain HSPA services. For HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions can be met only when the quality of the used frequency is lower than this threshold (Event 2B can be triggered only when both conditions are met.) To set this parameter, you need to consider the following factors: The cell signal quality of the used frequency is better and can meet the coverage requirements of the current services. After handover, even if the inter-frequency measurement is triggered again, it is very difficult to hand over the UE again to the cell of currently used frequency. That is, this parameter is usually set lower than the start threshold for event 2F or equal to the threshold of event 2D. This parameter configures the used frequency measurement quantity to trigger the inter-RAT measurement for the purpose of Qos-based handover. The parameter is valid when the event reporting mode is selected for inter-RAT. Ec/No: signal-to-noise ratio RSCP: received signal code power CPICH_Ec/NO: the measurement quantity used for event 2D and 2F, with unit of dB CPICH_RSCP: the measurement quantity used for event 2D and 2F, with unit of dBm The RNC, in the coverage-based inter-RAT measurement, may configure that the inter-RAT measurement quantity are delivered according to event 2D that triggers the measurement, which causes the result that the Qos-based inter-RAT measurement cannot refer to the coverage-based configurations. Under this condition, it is necessary for the Qos-based inter-RAT measurement to set the used frequency separately. When both the Qos-based and the coverage-based inter-RAT measurements exist, refer to this parameter. As for the impact on network performance: When the UE moves to the cell border, and there is a intra-frequency neighboring cell in the moving direction, CPCICH Ec/No varies faster than RSCP and the quality of the current cell should be evaluated according to CPCICH Ec/No. When there is no intra-frequency neighboring cell in the direction, CPCICH RSCP varies faster than Ec/No and the quality should be evaluated according to CPCICH RSCP. If the measurement quantity is not properly selected, the handover may not be performed timely, thus resulting in call drops. Threshold of used frequency quality for triggering inter-frequency measurement with measurement quantity of Ec/No for PS domain non-HSPA services. For PS domain non-HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions can be met only when the quality of the used frequency is lower than this threshold (Event 2B can be triggered only when both conditions are met.) To set this parameter, you need to consider the following factors: The cell signal quality of the used frequency is better and can meet the coverage requirements of the current services. After handover, even if the inter-frequency measurement is triggered again, it is very difficult to hand over the UE again to the cell of currently used frequency. That is, this parameter is usually set lower than the start threshold for event 2F or equal to the threshold of event 2D.
UsedFreqMeasQuanti tyForQos3A
UsedFreqR99PsThdE cN0
Issue 02 (2009-06-30)
7-61
7 Parameters
RAN Handover
Parameter id UsedFreqR99PsThdR SCP
Description Threshold of used frequency quality for triggering inter-frequency measurement with measurement quantity of RSCP for PS domain non-HSPA services. For PS domain non-HSPA services, if the value of [Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set the measurement control of event 2B. One of the necessary conditions can be met only when the quality of the used frequency is lower than this threshold (Event 2B can be triggered only when both conditions are met.) To set this parameter, you need to consider the following factors: The cell signal quality of the used frequency is better and can meet the coverage requirements of the current services. After handover, even if the inter-frequency measurement is triggered again, it is very difficult to hand over the UE again to the cell of currently used frequency. That is, this parameter is usually set lower than the start threshold for event 2F or equal to the threshold of event 2D. Indicating whether HCS is used. For details, refer to 3GPP TS 25.304. This parameter is used to determine the relative threshold of the soft handover based on the measurement of each cell in the active set. The larger the value of the parameter is, the higher the relative threshold is under the same conditions. When Weight is set to 0, the SHO relative threshold depends on only the best cell of the active set. For the definition, refer to 3GPP TS 25.331. When the parameter equals 0, the general quality of the active set is the measurement of the best cell and the SHO relative threshold depends on only the best cell in the active set. When the parameter equals 1, it can be regarded as the equivalent signal strength when maximum ratio combination of down links of all cells in the active set is implemented. As for the impact on network performance: The larger the value of the parameter is, the higher thresholds for triggering events 1A and 1B are obtained under the same condition, and the more difficult it is for the cell to join the active set, and the easier it is for the cell to leave the active set. The smaller the value of the parameter is, the easier it is for the cell to join the active set, and the more difficult it is for the cell to leave the active set. Weight used for computing frequency general quality. The larger the value of this parameter, the higher the calculated general quality of the active set. When this parameter is set to 0, the general quality of the active set is the quality of the best cell in the active set. For details about this parameter, refer to the subsection of frequency quality estimation in the section of inter-frequency measurement in 3GPP TS 25.331. This parameter is used for all event-triggered inter-frequency measurements, including those triggered by events 2D, 2F, 2B and 2C. The parameter, however, is not used for periodical inter-frequency measurements. The larger the value of this parameter, the higher the estimated quality of the current frequency in the same condition, and the more difficult to trigger inter-frequency handover. The smaller the value of this parameter, the lower the estimated quality of the current frequency, and the easier to trigger inter-frequency handover. Generally, this parameter is set to 0 or 1. Whether the handover is easy or difficult to trigger is not decided by the way of setting this parameter.
UseOfHcs Weight
WeightForUsedFreq
7-62
02 (2009-06-30)
RAN Handover
7 Parameters
Table 7-2 Parameter description (2) Parameter id CIO Default Value 0 GUI Value Range -20~20 Actual Value Range -10~10, step: 0.5 Unit dB MML Command ADD CELLSETUP( Optional) ADD NRNCCELL(O ptional) ADD GSMNCELL( Optional) ADD CELLINTERF REQHONCOV (Optional) SET INTERFREQH ONCOV(Optio nal) ADD CELLMBDRI NTERFREQ(O ptional) ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLMBDRI NTERRAT(Op tional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLMBDRI NTERFREQ(O ptional) NE RNC
CIOOffset
-50~50
-50~50
dB
RNC
Hystfor2C
6(ADD CELLMBDRI NTERFREQ,A DD CELLINTERF REQHONCOV ) -(SET INTERFREQH ONCOV)
0~29
0~14.5,Step:0.5
dB
RNC
Hystfor3C
0(ADD CELLMBDRI NTERRAT,AD D CELLINTERR ATHONCOV) -(SET INTERRATH ONCOV)
0~15
0~7.5,Step:0.5
dB
RNC
HystForPrdInte rFreq
0(ADD CELLMBDRI NTERFREQ,A DD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
0~29
0~14.5,Step:0.5
dB/ dBm
RNC
Issue 02 (2009-06-30)
7-63
7 Parameters
RAN Handover
Parameter id InterFreqFilter Coef
Default Value D3(ADD CELLMBDRI NTERFREQ,A DD CELLINTERF REQHONCOV ,ADD CELLINTERF REQHOCOV) -(SET INTERFREQH ONCOV,SET INTERFREQH OCOV)
GUI Value Range D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13, D15, D17, D19
Actual Value Range 0,1,2,3,4,5,6,7, 8,9,11,13,15,17 ,19
Unit None
MML Command ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHONCOV (Optional) SET INTERFREQH ONCOV(Optio nal) ADD CELLMBDRI NTERFREQ(O ptional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHONCOV (Optional) SET INTERFREQH ONCOV(Optio nal) ADD CELLMBDRI NTERFREQ(O ptional)
NE RNC
InterFreqMeas Time
60(ADD CELLINTERF REQHONCOV ,ADD CELLINTERF REQHOCOV) -(SET INTERFREQH ONCOV,SET INTERFREQH OCOV) 3(ADD CELLMBDRI NTERFREQ)
0~512
0~512
RNC
7-64
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqRepor tMode
Default Value PERIODICAL _REPORTING (ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV) EVENT_TRIG GER(ADD CELLMBDRI NTERFREQ)
GUI Value Range PERIODICAL _REPORTING (Periodical reporting), EVENT_TRIG GER(Event trigger)
Actual Value Range PERIODICAL _REPORTING, EVENT_TRIG GER
Unit None
MML Command ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLMBDRI NTERFREQ(O ptional) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLMBDRI NTERRAT(Op tional)
NE RNC
InterRATMeas Time
60(ADD CELLINTERR ATHONCOV, ADD CELLINTERR ATHOCOV) -(SET INTERRATH ONCOV,SET INTERRATH OCOV) 3(ADD CELLMBDRI NTERRAT)
0~512
0~512
RNC
Issue 02 (2009-06-30)
7-65
7 Parameters
RAN Handover
Parameter id InterRATPerio dReportInterval
Default Value D1000(ADD CELLMBDRI NTERRAT,AD D CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
GUI Value Range NON_PERIOD IC_REPORT( Non periodical reporting), D250~1 D500~2 D1000~3 D2000~4 D3000~5 D4000~6 D6000~7 D8000~8 D12000~9 D16000~10 D20000~11 D24000~12 D28000~13 D32000~14 D64000 PERIODICAL _REPORTING (Periodical reporting), EVENT_TRIG GER(Event trigger)
Actual Value Range NON_PERIOD IC_REPORT,2 50,500,1000,20 00,3000,4000,6 000,8000,1200 0,16000,20000, 24000,28000,3 2000,64000
Unit ms
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLMBDRI NTERRAT(Op tional)
NE RNC
InterRatReport Mode
PERIODICAL _REPORTING (ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV) EVENT_TRIG GER(ADD CELLMBDRI NTERRAT)
PERIODICAL _REPORTING, EVENT_TRIG GER
None
ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLMBDRI NTERRAT(Op tional) ADD INTERFREQN CELL(Mandat ory) ADD GSMNCELL( Mandatory)
RNC
NPrio
0~63
0~63
None
RNC
7-66
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id PrdReportInter val
Default Value D500(ADD CELLMBDRI NTERFREQ,A DD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
GUI Value Range NON_PERIOD IC_REPORT( Non periodical reporting), D250~1 D500~2 D1000~3 D2000~4 D3000~5 D4000~6 D6000~7 D8000~8 D12000~9 D16000~10 D20000~11 D24000~12 D28000~13 D32000~14 D64000 0~64000,65535
Actual Value Range NON_PERIOD IC_REPORT,2 50,500,1000,20 00,3000,4000,6 000,8000,1200 0,16000,20000, 24000,28000,3 2000,64000
Unit ms
MML Command ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLMBDRI NTERFREQ(O ptional)
NE RNC
TimeToTrigFor NonVerify
0(ADD CELLMBDRI NTERRAT,AD D CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
0~64000,65535
ms
ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLMBDRI NTERRAT(Op tional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLMBDRI NTERFREQ(O ptional)
RNC
TimeToTrigFor PrdInterFreq
0(ADD CELLMBDRI NTERFREQ,A DD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
0~64000
0~64000
ms
RNC
Issue 02 (2009-06-30)
7-67
7 Parameters
RAN Handover
Parameter id TimeToTrigFor Verify
Default Value 0(ADD CELLMBDRI NTERRAT,AD D CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
GUI Value Range 0~64000
Actual Value Range 0~64000
Unit ms
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLMBDRI NTERRAT(Op tional) ADD CELLINTERF REQHONCOV (Optional) SET INTERFREQH ONCOV(Optio nal) ADD CELLMBDRI NTERFREQ(O ptional) ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLMBDRI NTERRAT(Op tional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al)
NE RNC
TrigTime2C
D640(ADD CELLMBDRI NTERFREQ,A DD CELLINTERF REQHONCOV ) -(SET INTERFREQH ONCOV)
D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000
0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000
ms
RNC
TrigTime3C
D640(ADD CELLMBDRI NTERRAT,AD D CELLINTERR ATHONCOV) -(SET INTERRATH ONCOV)
0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000
ms
RNC
AmntOfRpt2B
4(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
0~63
0~62, 63: Infinity
None
RNC
7-68
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id AmntOfRpt2C
Default Value 1(ADD CELLINTERF REQHONCOV ) -(SET INTERFREQH ONCOV) FALSE
Actual Value Range 0~62, 63: Infinity
Unit None
MML Command ADD CELLINTERF REQHONCOV (Optional) SET INTERFREQH ONCOV(Optio nal) ADD GSMNCELL( Optional) ADD INTERFREQN CELL(Optional ) SET INTRAFREQH O(Optional) SET INTRAFREQH O(Optional) ADD INTERFREQN CELL(Optional ) ADD INTRAFREQN CELL(Optional ) ADD INTRAFREQN CELL(Optional ) SET COIFTIMER( Optional)
NE RNC
BlindHOFlag
FALSE, TRUE
FALSE,TRUE
None
RNC
BlindHOIntrafr eqMRAmount BlindHOIntrafr eqMRInterval BlindHOQualit yCondition
D1, D2, D4, D8 D250, D500
1,2,4,8
None
RNC
250,500
ms
RNC
-92
-115~-25
-115~-25
dBm
RNC
CellsForbidden 1A
AFFECT
AFFECT, NOT_AFFECT
AFFECT,NOT _AFFECT
None
RNC
CellsForbidden 1B
AFFECT
AFFECT, NOT_AFFECT
AFFECT,NOT _AFFECT
None
RNC
ChannelRetryH oTimerLen
0~999
0~999
RNC
Issue 02 (2009-06-30)
7-69
7 Parameters
RAN Handover
Parameter id CmcfSwitch
Default Value -
GUI Value Range CMCF_DL_H LS_SWITCH, CMCF_UL_H LS_SWITCH, CMCF_UL_PR ECFG_TOLER ANCE_SWITC H, CMCF_WITH OUT_UE_CAP _REPORT_SW ITCH
Actual Value Range CMCF_DL_H LS_SWITCH, CMCF_UL_H LS_SWITCH, CMCF_UL_PR ECFG_TOLER ANCE_SWITC H, CMCF_WITH OUT_UE_CAP _REPORT_SW ITCH
Unit None
MML Command SET CORRMALG OSWITCH(Op tional)
NE RNC
7-70
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id CmpSwitch
Default Value -
GUI Value Range CMP_IU_IMS _PROC_AS_N ORMAL_PS_S WITCH, CMP_IU_SYS HOIN_CMP_I UUP_FIXTO1 _SWITCH, CMP_IUR_H2 D_FOR_LOW R5_NRNCCEL L_SWITCH, CMP_IUR_SH O_DIVCTRL_ SWITCH, CMP_UU_AM R_SID_MUST _CFG_SWITC H, CMP_UU_DS T_SERV_CEL L_D2E_SWIT CH, CMP_UU_IGN ORE_UE_RLC _CAP_SWITC H, CMP_UU_SE RV_CELL_CH G_WITH_ASU _SWITCH, CMP_UU_SE RV_CELL_CH G_WITH_RB_ MOD_SWITC H, CMP_UU_VOI P_UP_PROC_ AS_NORMAL _PS_SWITCH, CMP_UU_FD PCH_COMPA T_SWITCH, CMP_UU_AM R_DRD_HHO _COMPAT_S WITCH, CMP_IU_QOS _ASYMMETR Y_IND_COMP AT_SWITCH
Actual Value Range CMP_IU_IMS _PROC_AS_N ORMAL_PS_S WITCH, CMP_IU_SYS HOIN_CMP_I UUP_FIXTO1 _SWITCH, CMP_IUR_H2 D_FOR_LOW R5_NRNCCEL L_SWITCH, CMP_IUR_SH O_DIVCTRL_ SWITCH, CMP_UU_AM R_SID_MUST _CFG_SWITC H, CMP_UU_DS T_SERV_CEL L_D2E_SWIT CH, CMP_UU_IGN ORE_UE_RLC _CAP_SWITC H, CMP_UU_SE RV_CELL_CH G_WITH_ASU _SWITCH, CMP_UU_SE RV_CELL_CH G_WITH_RB_ MOD_SWITC H, CMP_UU_VOI P_UP_PROC_ AS_NORMAL _PS_SWITCH, CMP_UU_FD PCH_COMPA T_SWITCH, CMP_UU_AM R_DRD_HHO _COMPAT_S WITCH, CMP_IU_QOS _ASYMMETR Y_IND_COMP AT_SWITCH
Unit None
NE RNC
Issue 02 (2009-06-30)
7-71
7 Parameters
RAN Handover
Parameter id CoexistMeasTh dChoice
Default Value COEXIST_ME AS_THD_CH OICE_INTERF REQ(ADD CELLHOCOM M) -(SET HOCOMM)
GUI Value Range COEXIST_ME AS_THD_CH OICE_INTERF REQ(Choosing the inter-frequency oriented parameters), COEXIST_ME AS_THD_CH OICE_INTER RAT(Choosing the inter-RAT oriented parameters) 0~100
Actual Value Range COEXIST_ME AS_THD_CH OICE_INTERF REQ,COEXIS T_MEAS_TH D_CHOICE_I NTERRAT
Unit None
MML Command ADD CELLHOCOM M(Optional) SET HOCOMM(Op tional)
NE RNC
CSHOOut2Glo adThd
80(ADD CELLINTERR ATHONCOV) -(SET INTERRATH ONCOV)
0~100%
per cent
ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLHOCOM M(Optional) ADD NRNC(Optiona l) SET INTRAFREQH O(Optional) SET HOCOMM(Op tional)
RNC
CSServiceHOS witch CSVoiceOverH spaSuppInd DcccShoPenalt yTime DivCtrlField
OFF
ON, OFF
ON,OFF
None
RNC
OFF
OFF, ON
OFF, ON
None
RNC
0~255
0~255
None
RNC
MAY(NodeB chooses whether combine at NodeB), MUST(Must combine at NodeB), MUST_NOT( Must combine at RNC)
MAY, MUST, MUST_NOT
None
RNC
7-72
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id DLQosMcTim erLen
Default Value 20(ADD CELLQOSHO) -(SET QOSHO)
Unit s
MML Command ADD CELLQOSHO( Optional) SET QOSHO(Optio nal) SET CMCF(Optiona l) ADD CELLCMCF(O ptional) SET CMCF(Optiona l) SET INTRAFREQH O(Optional)
NE RNC
DlSFLimitCMI nd
FALSE(Not Limited), TRUE(Limited ) D8, D16, D32, D64, D128, D256
FALSE,TRUE
None
RNC
DlSFTurnPoint
D64(ADD CELLCMCF) -(SET CMCF)
8,16,32,64,128, 256
None
RNC
FilterCoef
D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13, D15, D17, D19 D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13, D15, D17, D19
0,1,2,3,4,5,6,7, 8,9,11,13,15,17 ,19
None
RNC
FilterCoefOf2 D2F
D3(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
0,1,2,3,4,5,6,7, 8,9,11,13,15,17 ,19
None
ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLHCS(Opt ional) ADD GSMCELL(Op tional) ADD NRNCCELL(O ptional)
RNC
HCSPrio
0~7
0~7
None
RNC
Issue 02 (2009-06-30)
7-73
7 Parameters
RAN Handover
Parameter id HoSwitch
Default Value -
GUI Value Range
Actual Value Range
Unit
NE RNC
7-74
HO_ALGO_H HO_ALGO_H None CS_SPEED_E CS_SPEED_E ST_SWITCH, ST_SWITCH, HO_ALGO_L HO_ALGO_L DR_ALLOW_ DR_ALLOW_ SHO_SWITCH SHO_SWITCH , , HO_ALGO_M HO_ALGO_M BMS_FLC_S BMS_FLC_S WITCH, WITCH, HO_ALGO_O HO_ALGO_O VERLAY_SW VERLAY_SW ITCH, ITCH, HO_INTER_F HO_INTER_F REQ_HARD_ REQ_HARD_ HO_SWITCH, HO_SWITCH, HO_INTER_F HO_INTER_F REQ_RPRT_2 REQ_RPRT_2 D2F_SWITCH, D2F_SWITCH, HO_INTER_R HO_INTER_R AT_CS_OUT_ AT_CS_OUT_ SWITCH, SWITCH, HO_INTER_R HO_INTER_R AT_PS_3G2G AT_PS_3G2G _CELLCHG_N _CELLCHG_N ACC_SWITC ACC_SWITC H, H, HO_INTER_R HO_INTER_R AT_PS_3G2G AT_PS_3G2G _RELOCATIO _RELOCATIO N_SWITCH, N_SWITCH, HO_INTER_R HO_INTER_R AT_PS_OUT_ AT_PS_OUT_ SWITCH, SWITCH, HO_INTER_R HO_INTER_R AT_RNC_SER AT_RNC_SER VICE_HO_SW VICE_HO_SW ITCH, ITCH, HO_INTRA_F HO_INTRA_F REQ_DETSET REQ_DETSET _INTO_ACTS _INTO_ACTS ET_SWITCH, ET_SWITCH, HO_INTRA_F HO_INTRA_F REQ_DETSET REQ_DETSET _RPRT_SWIT _RPRT_SWIT CH, CH, HO_INTRA_F HO_INTRA_F REQ_HARD_ REQ_HARD_ HO_SWITCH, HO_SWITCH, HO_INTRA_F HO_INTRA_F REQ_RPRT_1 REQ_RPRT_1 J_SWITCH, J_SWITCH, HO_INTRA_F HO_INTRA_F REQ_RPRT_6 REQ_RPRT_6 F6G_SWITCH, F6G_SWITCH, Huawei Proprietary and Confidential HO_INTRA_F HO_INTRA_F Copyright Huawei Technologies Co., Ltd REQ_SOFT_H REQ_SOFT_H O_SWITCH, O_SWITCH, HO_MC_MEA HO_MC_MEA
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id HsdpaCMPerm issionInd HspaTimerLen
Default Value -
GUI Value Range FALSE(Forbid den), TRUE(Permit) 0~1024
Actual Value Range FALSE,TRUE
Unit None
MML Command SET CMCF(Optiona l) SET HOCOMM(Op tional) SET CMCF(Optiona l)
NE RNC
0~1024
RNC
HsupaCMPerm issionInd
Limited, Permit, BasedOnUECa p(Based On UE Capability) 0~15
For each switch of this parameter, the value can be ON, OFF. 0~7.5,Step:0.5
None
RNC
Hystfor1A
0(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 0(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 8(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 8(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 8(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
dB
ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
RNC
Hystfor1B
0~15
0~7.5,Step:0.5
dB
RNC
Hystfor1C
0~15
0~7.5,Step:0.5
dB
RNC
Hystfor1D
0~15
0~7.5,Step:0.5
dB
RNC
Hystfor1F
0~15
0~7.5,Step:0.5
dB
RNC
Issue 02 (2009-06-30)
7-75
7 Parameters
RAN Handover
Parameter id Hystfor1J
Default Value 8(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 4(ADD CELLINTERR ATHOCOV,A DD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV)
Actual Value Range 0~7.5,Step:0.5
Unit dB
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
HystFor2D
0~29
0~14.5,Step:0.5
dB/ dBm
RNC
HystFor2F
4(ADD CELLINTERR ATHOCOV,A DD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV)
0~29
0~14.5,Step:0.5
dB/ dBm
RNC
Hystfor3A
4(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
0~15
0~7.5,Step:0.5
dB
RNC
7-76
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id HystforInterRA T
Default Value 0(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
Unit dB
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) SET HOCOMM(Op tional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al)
NE RNC
IFAntiPingpan gTimerLength InterFreqCSTh d2DEcN0
0~120
0~120
RNC
-14(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
-24~0
-24~0
dB
RNC
InterFreqCSTh d2DRSCP
-115~-25
-115~-25
dBm
RNC
InterFreqCSTh d2FEcN0
-24~0
-24~0
dB
RNC
InterFreqCSTh d2FRSCP
-115~-25
-115~-25
dBm
RNC
Issue 02 (2009-06-30)
7-77
7 Parameters
RAN Handover
Parameter id InterFreqHOS witch
Default Value INTER_FREQ _COV
GUI Value Range INTER_FREQ _COV(Coverag e-based inter-frequency handover), INTER_FREQ _COV_NCOV( Coverage-base d and non-coverage-b ased inter-RAT handover), INTER_FREQ _TA(Traffic-ba sed inter-frequency handover) -24~0
Actual Value Range INTER_FREQ _COV,INTER_ FREQ_COV_ NCOV,INTER _FREQ_TA
Unit None
MML Command ADD CELLHOCOM M(Optional)
NE RNC
InterFreqHThd 2DEcN0
-24~0
dB
ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al)
RNC
InterFreqHThd 2DRSCP
-115~-25
-115~-25
dBm
RNC
InterFreqHThd 2FEcN0
-24~0
-24~0
dB
RNC
InterFreqHThd 2FRSCP
-115~-25
-115~-25
dBm
RNC
7-78
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterFreqNCov HOThdEcN0
Default Value -
GUI Value Range -24~0
Actual Value Range -24~0
Unit dB
MML Command SET INTERFREQH ONCOV(Optio nal) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLHOCOM M(Optional)
NE RNC
InterFreqR99Ps Thd2DEcN0
-24~0
-24~0
dB
RNC
InterFreqR99Ps Thd2DRSCP
-115~-25
-115~-25
dBm
RNC
InterFreqR99Ps Thd2FEcN0
-24~0
-24~0
dB
RNC
InterFreqR99Ps Thd2FRSCP
-115~-25
-115~-25
dBm
RNC
InterFreqRATS witch
SIMINTERFR EQRAT
INTERFREQ(i nter-frequency handover only), INTERRAT(int er-RAT handover only), SIMINTERFR EQRAT(inter-f requency and inter-RAT handover)
INTERFREQ,I NTERRAT,SI MINTERFRE QRAT
None
RNC
Issue 02 (2009-06-30)
7-79
7 Parameters
RAN Handover
Parameter id InterRATCSTh d2DEcN0
Default Value -14(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
Unit dB
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
InterRATCSTh d2DRSCP
-100(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
-115~-25
-115~-25
dBm
RNC
InterRATCSTh d2FEcN0
-24~0
-24~0
dB
RNC
InterRATCSTh d2FRSCP
-115~-25
-115~-25
dBm
RNC
InterRATHOAt tempts
1~16
1~16
None
RNC
InterRATHThd 2DEcN0
-24~0
-24~0
dB
RNC
7-80
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id InterRATHThd 2DRSCP
GUI Value Range -115~-25
Actual Value Range -115~-25
Unit dBm
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
InterRATHThd 2FEcN0
-24~0
-24~0
dB
RNC
InterRATHThd 2FRSCP
-115~-25
-115~-25
dBm
RNC
InterRATNCov HOPSThd
0~63
lower than -110, -110~-48(1:-11 0; 2:-109; ...; 63:-48 )
dBm
RNC
InterRATPingP ongHyst
0~15
0~7.5,Step:0.5
dBm
RNC
InterRATPingP ongTimer
0~65535
0~65535
RNC
Issue 02 (2009-06-30)
7-81
7 Parameters
RAN Handover
Parameter id InterRATR99P sThd2DEcN0
Unit dB
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
NE RNC
InterRATR99P sThd2DRSCP
-115~-25
-115~-25
dBm
RNC
InterRATR99P sThd2FEcN0
-24~0
-24~0
dB
RNC
InterRATR99P sThd2FRSCP
-115~-25
-115~-25
dBm
RNC
IntraAblThdFo r1FEcNo
-24(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) -115(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
-24~0
-24~0
dB
RNC
IntraAblThdFo r1FRSCP
-115~-25
-115~-25
dBm
RNC
7-82
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id IntraFreqMeas Quantity
Default Value CPICH_EC/N O(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 6(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 6(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 6(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 12(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 12(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
GUI Value Range CPICH_EC/N O, CPICH_RSCP
Actual Value Range CPICH_EC/N O, CPICH_RSCP
Unit None
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
NE RNC
IntraRelThdFor 1ACSNVP
0~29
0~14.5,Step:0.5
dB
RNC
IntraRelThdFor 1ACSVP
0~29
0~14.5,Step:0.5
dB
RNC
IntraRelThdFor 1APS
0~29
0~14.5,Step:0.5
dB
RNC
IntraRelThdFor 1BCSNVP
0~29
0~14.5,Step:0.5
dB
RNC
IntraRelThdFor 1BCSVP
0~29
0~14.5,Step:0.5
dB
RNC
Issue 02 (2009-06-30)
7-83
7 Parameters
RAN Handover
Parameter id IntraRelThdFor 1BPS
Default Value 12(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) -
Unit dB
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) SET CMCF(Mandat ory) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) SET HOCOMM(Op tional) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLALGOS WITCH(Optio nal) SET INTERRATH ONCOV(Optio nal) ADD CELLHCSHO( Optional) SET HCSHO(Optio nal)
NE RNC
LimitCMDlSF Thd MaxCellInActi veSet
D8, D16, D32, D64, D128, D256 1~6
8,16,32,64,128, 256 1~6
None
RNC
3(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) -
None
RNC
MaxEdchCellI nActiveSet MeasQuantity Of3A
1~4
1~4
None
RNC
AUTO(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
CPICH_EC/N O~0 CPICH_RSCP ~1 AUTO
CPICH_EC/N O,CPICH_RSC P,AUTO
None
RNC
NBMMachsRe setAlgoSelSwit ch
ALGORITHM _DEPEND_O N_LCG
ALGORITHM _REQUIRED, ALGORITHM _DEPEND_O N_LCG OFF, ON
ALGORITHM _REQUIRED, ALGORITHM _DEPEND_O N_LCG OFF, ON
None
RNC
NcovHoOn2Gl dInd
None
RNC
NFastSpdEst
15(ADD CELLHCSHO) -(SET HCSHO)
1~16
1~16
None
RNC
7-84
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id NprioFlag
Default Value FALSE
GUI Value Range FALSE, TRUE
Actual Value Range FALSE,TRUE
Unit None
MML Command ADD INTERFREQN CELL(Optional ) ADD INTRAFREQN CELL(Optional ) ADD GSMNCELL( Optional) ADD CELLHCSHO( Optional) SET HCSHO(Optio nal) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHONCOV (Optional) SET INTERFREQH ONCOV(Optio nal) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
NE RNC
NSlowSpdEst
1~16
1~16
None
RNC
PeriodFor2B
1(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
1~64
500~32000,Ste p:500
ms
RNC
PeriodFor2C
4(ADD CELLINTERF REQHONCOV ) -(SET INTERFREQH ONCOV) D16(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) D16(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
1~64
500~32000,Ste p:500
ms
RNC
PeriodMRRepo rtNumfor1A
D1, D2, D4, D8, D16, D32, D64, INFINITY
1, 2, 4, 8, 16, 32, 64, INFINITY
None
RNC
PeriodMRRepo rtNumfor1C
D1, D2, D4, D8, D16, D32, D64, INFINITY
1, 2, 4, 8, 16, 32, 64, INFINITY
None
RNC
Issue 02 (2009-06-30)
7-85
7 Parameters
RAN Handover
Parameter id PeriodMRRepo rtNumfor1J
Default Value D64(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 60(ADD CELLINTERR ATHONCOV) -(SET INTERRATH ONCOV)
GUI Value Range D1, D2, D4, D8, D16, D32, D64, INFINITY
Actual Value Range 1, 2, 4, 8, 16, 32, 64, INFINITY
Unit None
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTERR ATHONCOV( Optional) SET INTERRATH ONCOV(Optio nal) ADD CELLHOCOM M(Optional) ADD GSMCELL(Ma ndatory)
NE RNC
PSHOOut2Glo adThd
0~100
0~100%
per cent
RNC
PSServiceHOS witch RATCELLTY PE
OFF
ON, OFF
ON,OFF
None
RNC
NO_CAPABIL ITY(Cell capability unknown), GSM~1 GPRS~2 EDGE -29~29
NO_CAPABIL ITY,GSM,GPR S,EDGE
None
RNC
RelThdForDwn Grd ReportIntervalf or1A
-14.5~14.5,Ste p:0.5 NON_PERIOD IC_REPORT, 250, 500, 1000, 2000, 4000, 8000, 16000
dB
SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
RNC
D4000(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
NON_PERIOD IC_REPORT, D250~1 D500~2 D1000~3 D2000~4 D4000~5 D8000~6 D16000 NON_PERIOD IC_REPORT, D250~1 D500~2 D1000~3 D2000~4 D4000~5 D8000~6 D16000
ms
RNC
ReportIntervalf or1C
NON_PERIOD IC_REPORT, 250, 500, 1000, 2000, 4000, 8000, 16000
ms
ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
RNC
7-86
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id ReportIntervalf or1J
Default Value D1000(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
GUI Value Range NON_PERIOD IC_REPORT, D250~1 D500~2 D1000~3 D2000~4 D4000~5 D8000~6 D16000 GSM, GPRS, EDGE HO_TO_GSM _SHOULD_BE _PERFORM, HO_TO_GSM _SHOULD_N OT_BE_PERF ORM, HO_TO_GSM _SHALL_NOT _BE_PERFOR M 0~63
Actual Value Range NON_PERIOD IC_REPORT, 250, 500, 1000, 2000, 4000, 8000, 16000
Unit ms
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional)
NE RNC
Req2GCap
GSM, GPRS, EDGE HO_TO_GSM _SHOULD_BE _PERFORM, HO_TO_GSM _SHOULD_N OT_BE_PERF ORM, HO_TO_GSM _SHALL_NOT _BE_PERFOR M 0~63
None
ADD TYPRABBASI C(Mandatory) ADD TYPRABBASI C(Mandatory)
RNC
SHIND
None
RNC
ShoFailNumFo rDwnGrd ShoFailPeriod
None
SET INTRAFREQH O(Optional) SET INTRAFREQH O(Optional) SET INTERRATH ONCOV(Optio nal) ADD GSMCELL(Op tional) ADD GSMCELL(Op tional)
RNC
0~120
0~120
RNC
SndLdInfo2Gs mInd
OFF, ON
OFF, ON
None
RNC
SuppPSHOFla g SuppRIMFlag
FALSE
FALSE, TRUE
FALSE,TRUE
None
RNC
FALSE
FALSE, TRUE
FALSE,TRUE
None
RNC
Issue 02 (2009-06-30)
7-87
7 Parameters
RAN Handover
Parameter id TargetFreqCsT hdEcN0
Default Value -12(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
Unit dB
MML Command ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al)
NE RNC
TargetFreqCsT hdRscp
-115~-25
-115~-25
dBm
RNC
TargetFreqHTh dEcN0
-24~0
-24~0
dB
RNC
TargetFreqHTh dRscp
-115~-25
-115~-25
dBm
RNC
TargetFreqR99 PsThdEcN0
-24~0
-24~0
dB
RNC
TargetFreqR99 PsThdRscp
-115~-25
-115~-25
dBm
RNC
7-88
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id TargetRatCsTh d
Default Value 16(ADD CELLINTERR ATHOCOV) -(SET INTERRATH OCOV)
Actual Value Range lower than -110,-110~-48( 1:-110; 2:-109; ...; 63:-48 )
Unit dBm
MML Command ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLHCSHO( Optional) SET HCSHO(Optio nal) ADD CELLHCSHO( Optional) SET HCSHO(Optio nal) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al)
NE RNC
TargetRatHThd
0~63
lower than -110,-110~-48( 1:-110; 2:-109; ...; 63:-48 )
dBm
RNC
TargetRatR99P sThd
0~63
lower than -110,-110~-48( 1:-110; 2:-109; ...; 63:-48 )
dBm
RNC
TCycleSlow
0~255
0~255
RNC
TFastSpdEst
0~511
0~511
RNC
TimeToTrig2B
D0(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
Issue 02 (2009-06-30)
7-89
7 Parameters
RAN Handover
Parameter id TimeToTrig2D
Default Value D320(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
GUI Value Range D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 0~120
Actual Value Range 0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
Unit ms
MML Command ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLHCSHO( Optional) SET HCSHO(Optio nal) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) SET SMLC(Mandat ory) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) SET SMLC(Mandat ory)
NE RNC
TimeToTrig2F
D1280(ADD CELLINTERF REQHOCOV) -(SET INTERFREQH OCOV)
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
TRelateLength
0~120
RNC
TrigTime1A
D320(ADD CELLINTRAF REQHO) -(SET SMLC,SET INTRAFREQH O)
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
TrigTime1B
D640(ADD CELLINTRAF REQHO) -(SET SMLC,SET INTRAFREQH O)
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
7-90
02 (2009-06-30)
RAN Handover
7 Parameters
Default Value D640(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O)
GUI Value Range D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000 D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320, D640, D1280, D2560, D5000
Actual Value Range 0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
Unit ms
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
TrigTime1D
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
TrigTime1F
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
TrigTime1J
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
TrigTime2F
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
TrigTime3A
0,10,20,40,60,8 0,100,120,160, 200,240,320,64 0,1280,2560,50 00
ms
RNC
Issue 02 (2009-06-30)
7-91
7 Parameters
RAN Handover
Parameter id TSlowSpdEst
Default Value 240(ADD CELLHCSHO) -(SET HCSHO)
Unit s
MML Command ADD CELLHCSHO( Optional) SET HCSHO(Optio nal) ADD CELLQOSHO( Optional) SET QOSHO(Optio nal) ADD CELLCMCF(O ptional) SET CMCF(Optiona l) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
ULQosMcTim erLen
20(ADD CELLQOSHO) -(SET QOSHO)
0~512
0~512
RNC
UlSFTurnPoint
D64(ADD CELLCMCF) -(SET CMCF)
D8, D16, D32, D64, D128, D256
8,16,32,64,128, 256
None
RNC
UsedFreqCSTh dEcN0
-12(ADD CELLINTERR ATHOCOV,A DD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV)
-24~0
-24~0
dB
RNC
7-92
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id UsedFreqCSTh dRSCP
Default Value -92(ADD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV) -97(ADD CELLINTERR ATHOCOV)
GUI Value Range -115~-25
Actual Value Range -115~-25
Unit dBm
MML Command ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
UsedFreqHThd EcN0
-12(ADD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV) -13(ADD CELLINTERR ATHOCOV)
-24~0
-24~0
dB
RNC
UsedFreqHThd RSCP
-115~-25
-115~-25
dBm
RNC
Issue 02 (2009-06-30)
7-93
7 Parameters
RAN Handover
Parameter id UsedFreqMeas QuantityForQo s3A
Default Value CPICH_RSCP( ADD CELLQOSHO) -(SET QOSHO) -12(ADD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV) -13(ADD CELLINTERR ATHOCOV)
GUI Value Range CPICH_EC/N O, CPICH_RSCP
Actual Value Range CPICH_EC/N O,CPICH_RSC P
Unit None
MML Command ADD CELLQOSHO( Optional) SET QOSHO(Optio nal) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al) ADD CELLHCS(Opt ional) ADD GSMCELL(Op tional) ADD NRNCCELL(O ptional)
NE RNC
UsedFreqR99P sThdEcN0
-24~0
-24~0
dB
RNC
UsedFreqR99P sThdRSCP
-115~-25
-115~-25
dBm
RNC
UseOfHcs
NOT_USED
USED, NOT_USED
USED, NOT_USED
None
RNC
7-94
02 (2009-06-30)
RAN Handover
7 Parameters
Parameter id Weight
Default Value 0(ADD CELLINTRAF REQHO) -(SET INTRAFREQH O) 0(ADD CELLINTERR ATHOCOV,A DD CELLINTERF REQHOCOV) -(SET INTERRATH OCOV,SET INTERFREQH OCOV)
Actual Value Range 0~2,Step:0.1
Unit None
MML Command ADD CELLINTRAF REQHO(Optio nal) SET INTRAFREQH O(Optional) ADD CELLINTERF REQHOCOV( Optional) SET INTERFREQH OCOV(Option al) ADD CELLINTERR ATHOCOV(O ptional) SET INTERRATH OCOV(Option al)
NE RNC
WeightForUse dFreq
0~20
0~2,Step:0.1
None
RNC
The Default Value column is valid for only the optional parameters. The "-" symbol indicates no default value.
Issue 02 (2009-06-30)
7-95
RAN Handover
8 Counters
8
The following describes the counters related to handover.
Counters
For details, see the RNC Performance Counter Reference and NodeB Performance Counter Reference.
Issue 02 (2009-06-30)
8-1
RAN Handover
9 Glossary
Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 02 (2009-06-30)
9-1
RAN Handover
10 Reference Documents
10
1. 2. 3. 4. 5. 6. 7. 8. 9.
Reference Documents
The following lists the reference documents related to the feature: 3GPP TS 23.122: Non Access Stratum functions related to Mobile Station (MS) in idle mode 3GPP TS 24.008: Mobile radio interface layer 3 specification; Core Network Protocols Stage 3 3GPP TS 25.304: UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode 3GPP TS 25.331: RRC Protocol Specification 3GPP TS 23.060: General Packet Radio Service (GPRS); Service description 3GPP TS 25.931: UTRAN Functions, Examples on Signalling Procedures Basic Feature Description of Huawei UMTS RAN11.0 V1.5 Optional Feature Description of Huawei UMTS RAN11.0 V1.5 RNC Performance Counter Reference
10. NodeB Performance Counter Reference 11. Glossary
Issue 02 (2009-06-30)
10-1

WCDMA R11 Feature Parameter Description - Handover

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

WCDMA R11 Feature Parameter Description - Handover

Hochgeladen von

Copyright:

Verfügbare Formate

RAN

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

3 Intra-Frequency Handover Algorithms .................................................................................3-1

4 Inter-Frequency Handover Algorithms .................................................................................4-1

5 Inter-RAT Handover Algorithms ............................................................................................5-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

6 HCS Handover Algorithms ......................................................................................................6-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1 Introduction to This Document

Introduction to This Document

1.2 Intended Audience

1.3 Change History

02 (2009-06-30) 01 (2009-03-30) Draft (2009-03-10) Draft (2009-01-15)

1 Introduction to This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1 Introduction to This Document

Change Type Editorial change

Parameter Change None.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

2.1 Handover Types

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Figure 2-1 Handovers supported by the UMTS

2.2 Intra-Frequency Handover

Intra-Frequency Soft Handover

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Intra-Frequency Hard Handover

2.3 Inter-Frequency Handover

Speed-based inter-frequency handover

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

2.4 Inter-RAT Handover (3G to 2G)

QoS-based 3G-to-2G handover Load-based 3G-to-2G handover Service-based 3G-to-2G handover

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Type Speed-based 3G-to-2G handover

2.4.2 Rules for Enabling 3G-to-2G Handover

Rules for Enabling Coverage- and QoS-based 3G-to-2G Handover

Rules for Enabling Load- and Service-based 3G-to-2G Handover

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Switches for Service-based 3G-to-2G Handover

Service Handover Indicator

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

By default, the RNC does as follows:

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Service Handover Indicator

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Max Rate (bit/s)

Service Handover Indicator

Requi red 2G Capab ility EDGE

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Max Rate (bit/s)

Service Handover Indicator

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Max Rate (bit/s)

Service Handover Indicator

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Max Rate (bit/s)