RAN Feature Documentation RAN22.1 - 07 20221201150622

Handover
Contents
7.4.1.11 Handover
WCDMA RAN
Handover Feature Parameter

Description
Issue 01
Date 2019-06-06
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2021. 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 a 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: https:/
Email: support@huawei.com
7.4.1.11 Contents
1 About This Document
1.1 Scope
1.2 General Statements
1.3 Change History
1.4 Differences Between Base Station Types
2 Overview
2.1 Overview of Handover Types
2.2 Introduction
2.2.1 WRFD-020201 Intra NodeB Softer Handover
2.2.2 WRFD-020202 Intra RNC Soft Handover
2.2.3 WRFD-020203 Inter RNC Soft Handover
2.2.4 WRFD-020301 Intra Frequency Hard Handover
2.2.5 WRFD-020302 Inter Frequency Hard Handover Based on Coverage
2.2.6 WRFD-020303 Inter-RAT Handover Based on Coverage
2.2.7 WRFD-020304 Inter Frequency Hard Handover Based on DL QoS
2.2.8 WRFD-020309 Inter-RAT Handover Based on DL QoS
2.2.9 WRFD-020306 Inter-RAT Handover Based on Load
2.2.10 WRFD-020305 Inter-RAT Handover Based on Service
2.2.11 WRFD-01061006 HSDPA Mobility Management
2.2.12 WRFD-01061204 HSUPA Mobility Management
2.2.13 WRFD-021200 HCS (Hierarchical Cell Structure)
2.2.14 WRFD-020308 Inter-RAT Handover Phase 2
2.2.15 WRFD-02030801 NACC (Network Assisted Cell Change)
2.2.16 WRFD-02030802 PS Handover Between UMTS and GPRS
2.2.17 WRFD-020310 3G/2G Common Load Management
3 Intra-Frequency Handover
3.1 Overview
3.1.1 Intra-Frequency Soft Handover
3.1.2 Intra-Frequency Hard Handover
3.2 Signaling Procedures for Intra-Frequency Handover
3.2.1 Intra-NodeB Intra-Frequency Soft Handover
3.2.2 Intra-RNC Inter-NodeB Intra-Frequency Soft Handover
3.2.3 Inter-RNC Intra-Frequency Soft Handover
3.2.4 Intra-RNC Inter-NodeB Intra-Frequency Hard Handover
3.2.5 Inter-RNC Intra-Frequency Hard Handover
3.3 Intra-Frequency Handover Procedure
3.4 Intra-Frequency Handover Measurement
3.4.1 Intra-Frequency Handover Measurement Control
3.4.2 Measurement Quantities and Measurement Events Used for Intra-Frequency Handovers
3.4.3 Triggering of Event 1A
3.4.4 Triggering of Event 1B
3.4.5 Triggering of Event 1C
3.4.6 Triggering of Event 1D
3.4.7 Triggering of Event 1F
3.5 Intra-Frequency Handover Decision and Execution
3.6 Follow-up Procedures for Soft Handover Failures
3.6.1 Overview
3.6.2 Rate Reduction After a Soft Handover Failure
3.6.3 D2F State Transition After a Soft Handover Failure
3.6.4 E2D Reconfiguration After a Soft Handover Failure
3.7 Other Functions
3.7.1 Addition of Detected Set Cells to the Active Set
3.7.2 Uplink Active Set Expansion
3.7.2.1 Overview
3.7.2.2 Link Management
3.7.2.3 Admission Procedure
3.7.2.4 Application Scenarios
3.7.2.5 Performance Monitoring
4 Inter-Frequency and Inter-RAT Handovers

4.1 Overview
4.2 Signaling Procedures for Inter-Frequency and Inter-RAT Handovers
4.2.1 Signaling Procedures for Inter-Frequency Handover
4.2.1.1 Inter-Frequency Handover Within One RNC
4.2.1.2 Inter-Frequency Handover Between RNCs
4.2.2 Signaling Procedures for Inter-RAT Handover
4.2.2.1 UMTS-to-GSM Handover in the CS Domain
4.2.2.2 UMTS-to-GSM Handover in the PS Domain
4.2.2.3 UMTS-to-GSM Handover in Both CS and PS Domains
4.2.2.4 GSM-to-UMTS Handover in the CS Domain
4.2.2.5 GSM-to-UMTS Handover in the PS Domain
4.3 Coverage- and QoS-based Handover
4.3.1 Procedure
4.3.2 Triggering
4.3.3 Measurement
4.3.3.1 Starting Handover Measurement
4.3.3.2 Stopping Handover Measurement
4.3.3.3 Penalty for Measurement Failures
4.3.4 Decision and Execution
4.3.4.1 Inter-Frequency Handovers
4.3.4.2 Inter-RAT Handovers
4.3.5 Processing After a Handover Failure
4.4 Load-based Inter-Frequency Handover
4.4.1 Procedure
4.4.2 Triggering
4.4.3 Measurement
4.5 Load-based UMTS-to-GSM Handover
4.5.1 Procedure
4.5.2 Triggering
4.5.3 Measurement
4.6 Service-based Inter-Frequency Handover
4.7 Service-based UMTS-to-GSM Handover
4.8 Speed-based Inter-Frequency and Inter-RAT Handover
4.8.1 Overview
4.8.2 HCS Handover Procedure
4.8.3 Triggering of HCS Handover
4.8.4 HCS Handover Measurement
4.8.5 HCS Handover Decision and Execution
4.8.6 Interoperability Between HCS Handover and Other Handovers
4.9 UMTS-to-GSM Handovers When NACC Is Supported
4.10 UMTS-to-GSM PS Handover
4.11 Other Functions
4.11.1 Handover Protection
4.11.1.1 Anti-Ping-Pong
4.11.1.2 Handover Retry
4.11.1.2.1 Inter-Frequency Handover Retry
4.11.1.2.2 Inter-RAT (UMTS-to-GSM) Handover Retry
4.11.1.3 Inter-RAT Multimedia Fallback
4.11.2 Compressed Mode
4.11.2.1 Overview
4.11.2.2 Compressed Mode Switches
4.11.2.3 Compression Methods
4.11.2.3.1 SF/2 Compressed Mode
4.11.2.3.2 Higher Layer Scheduling Compressed Mode
4.11.2.4 Measurement Timer Length
4.11.2.5 Check of Compressed Mode Parameter Settings During Inter-RNC Handover
4.11.3 Inter-Frequency Measurements in Batches
4.11.4 BSIC Verification Requirements for GSM Cells
4.11.5 Rules for Inter-RAT Handovers
4.11.6 Inter-RAT Load Information Exchange
4.11.7 Handover of UEs in the Blacklist
4.11.8 UMTS-to-GSM Handover Success Rate Optimization and Enhanced UMTS-to-GSM Handover
Success Rate Optimization
4.11.8.1 UMTS-to-GSM Handover Success Rate Optimization
4.11.8.2 Enhanced UMTS-to-GSM Handover Success Rate Optimization
4.11.9 Inter-Frequency Handover Success Rate Optimization
5 HSPA Handover
5.1 HSDPA Handover
5.1.1 HSDPA Intra-Frequency Handover
5.1.2 HSDPA Inter-Frequency Handover
5.1.3 HSDPA Inter-RAT Handover
5.2 HSUPA Handover
5.2.1 HSUPA Intra-Frequency Handover
5.2.2 HSUPA Inter-Frequency Handover
5.2.3 HSUPA Inter-RAT Handover
5.3 HSPA+ Handover
5.3.1 Overview
5.3.2 Preselection Phase
5.3.3 Fallback Phase
5.3.4 Retry Phase
5.4 Anti-Frequent Serving Cell Change
5.5 HSPA Handover Retry
6 Inter-PLMN Handover
7 Neighboring Cell Combination

7.1 Overview
7.2 Neighboring Cell Combination Switches
7.3 Neighboring Cell Combination Procedure
8 Missing Neighboring Cell Detection

8.1 Overview
8.2 Missing Intra-Frequency Neighboring Cell Detection
8.3 Missing Inter-Frequency or Inter-RAT Neighboring Cell Detection
8.4 Missing Neighboring Cell Detection Activation Observation
9 Related Features
9.1 WRFD-01061006 HSDPA Mobility Management
9.2 WRFD-01061204 HSUPA Mobility Management
9.3 WRFD-020302 Inter Frequency Hard Handover Based on Coverage
9.4 WRFD-021200 HCS (Hierarchical Cell Structure)
9.5 WRFD-020304 Inter Frequency Hard Handover Based on DL QoS
9.6 WRFD-020309 Inter-RAT Handover Based on DL QoS
10 Network Impact
10.3 Inter Frequency Hard Handover Based on UL QoS
10.5 Inter-RAT Handover Based on UL QoS
11 Engineering Guidelines
11.1 WRFD-020201 Intra NodeB Softer Handover
11.1.1 Requirements
11.1.2 Activation
11.1.3 MML Command Examples (Activation)
11.1.4 Activation Observation
11.1.5 Deactivation
11.1.6 MML Command Examples (Deactivation)
11.2 WRFD-020202 Intra RNC Soft Handover
11.2.1 Requirements
11.2.2 Activation
11.2.5 Deactivation
11.3 WRFD-020203 Inter RNC Soft Handover
11.3.1 Requirements
11.3.2 Activation
11.3.5 Deactivation
11.4 WRFD-020301 Intra Frequency Hard Handover
11.4.1 Requirements
11.4.2 Activation
11.4.5 Deactivation
11.6.1 Requirements
11.6.2 Activation
11.6.5 Deactivation
11.7.1 When to Use This Feature
11.7.2 Required Information
11.7.3 Requirements
11.7.4 Activation
11.7.7 Deactivation
11.7.9 Performance Monitoring
11.8.3 Requirements
11.8.4 Activation
11.8.7 Deactivation
11.9.3 Requirements
11.9.4 Activation
11.9.7 Deactivation
11.10 WRFD-020303 Inter-RAT Handover Based on Coverage
11.10.1 Requirements
11.10.2 Activation
11.10.5 Deactivation
11.10.7 Parameter Optimization
11.11.2 Activation
11.12.2 Activation
11.13 WRFD-020308 Inter-RAT Handover Phase 2
11.13.2 Deployment
11.14 WRFD-02030801 NACC (Network Assisted Cell Change)
11.14.2 Activation
11.15 WRFD-02030802 PS Handover Between UMTS and GPRS
11.15.2 Activation
11.16 WRFD-020305 Inter-RAT Handover Based on Service
11.16.2 Activation
11.17 WRFD-020306 Inter-RAT Handover Based on Load
11.17.2 Activation
11.18 WRFD-020310 3G/2G Common Load Management
11.18.2 Activation
11.20 Compressed Mode
11.20.1 When to Use Compressed Mode
11.20.3 Activation
11.20.3.1 Using MML Commands
11.20.3.2 MML Command Examples
11.20.3.3 Using the MAE-Deployment
11.21 Inter-PLMN Handover
11.21.1 When to Use Inter-PLMN Handover
11.21.2 Deployment
11.21.2.1 Requirements
11.21.2.2 Data Preparation
11.21.2.3 Activation
11.21.2.3.1 Using MML Commands
11.21.2.3.2 MML Command Examples
11.21.2.3.3 Using the MAE-Deployment
11.21.2.4 Activation Observation
11.21.2.5 Deactivation
11.21.5 Troubleshooting
12 Parameters
13 Counters
14 Glossary
15 Reference Documents
1 About This Document
1.1 Scope
This document describes handover, including its technical principles, network impact, and
engineering guidelines.
This document covers the following features:
• WRFD-020201 Intra NodeB Softer Handover
• WRFD-020202 Intra RNC Soft Handover
• WRFD-020203 Inter RNC Soft Handover
• WRFD-020301 Intra Frequency Hard Handover
• WRFD-01061006 HSDPA Mobility Management
• WRFD-01061204 HSUPA Mobility Management
• WRFD-021200 HCS (Hierarchical Cell Structure)
• WRFD-020302 Inter Frequency Hard Handover Based on Coverage
• WRFD-020304 Inter Frequency Hard Handover Based on DL QoS
• WRFD-020303 Inter-RAT Handover Based on Coverage
• WRFD-020309 Inter-RAT Handover Based on DL QoS
• WRFD-020308 Inter-RAT Handover Phase 2
• WRFD-02030801 NACC (Network Assisted Cell Change)
• WRFD-02030802 PS Handover Between UMTS and GPRS
• WRFD-020305 Inter-RAT Handover Based on Service
• WRFD-020306 Inter-RAT Handover Based on Load
• WRFD-020310 3G/2G Common Load Management
1.2 General Statements
Purpose
Feature Parameter Description documents are intended to acquaint readers with:

• The technical principles of features and their related parameters
• The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
• Requirements of the operating environment that must be met before feature activation
• Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and feature gains
depend on the specifics of the network scenario where the feature is deployed. To achieve the desired
gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter
Description documents apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
1.3 Change History
This section provides information about the changes in different document versions. There are
two types of changes:
• Feature change
Changes in features and parameters of a specified version
• Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes and parameters of a specified version
RAN21.1 01 (2019-06-06)
This issue does not include any changes.
RAN21.1 Draft A (2018-12-30)
Compared with Issue 01 (2018-03-30) of RAN20.1, Draft A (2018-12-30) of RAN21.1 includes

the following changes.
Change Change Description Parameter Change

Type
Feature Added the function of Added the following parameters:

change enhanced UMTS-to- • U2GSuccRatioOptEnhSw (BSC6900, BSC6910)
GSM handover success • U2GSuccRateOptCSTrgtThld (BSC6900,
rate optimization. For BSC6910)
Change Change Description Parameter Change
Type
details, see the following • U2GSuccRateOptPSTrgtThld (BSC6900,

sections: BSC6910)
• 4.11.8.2 • CSCIOOffsetDelta (BSC6900, BSC6910)
Enhanced
• PSCIOOffsetDelta (BSC6900, BSC6910)
UMTS-to-GSM
Handover
Success Rate
Optimization
• 11.10 WRFD-
020303 Inter-
RAT Handover
Based on
Coverage
Added the function of Added the following values for HoSwitch2 (BSC6900,
allowing inter-RAT BSC6910):
handovers of UEs with • HO_INTER_RAT_CS_SIGNAL_LIMIT_SWITCH
SRBs only and no • HO_INTER_RAT_PS_SIGNAL_LIMIT_SWITCH
RABs. For details, see
4.1 Overview.
Editorial None None

change
1.4 Differences Between Base Station Types
Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Description Supported by Base Supported Supported Supported

Station Controllers by Macro by Micro by
Base Base LampSite
BSC6900 BSC6910 Station Station Base
Station
WRFD- Intra NodeB Yes Yes Yes No Yes

020201 Softer
Handover
WRFD- Intra RNC Yes Yes Yes Yes Yes

020202 Soft
Handover
WRFD- Inter RNC Yes Yes Yes Yes Yes

020203 Soft
Handover
WRFD- Intra Yes Yes Yes Yes Yes
020301 Frequency
Hard
Handover
WRFD- HSDPA Yes Yes Yes Yes Yes

01061006 Mobility
Management
WRFD- HSUPA Yes Yes Yes Yes Yes

01061204 Mobility
Management
WRFD- HCS Yes Yes Yes Yes Yes

021200 (Hierarchical
Cell
Structure)
WRFD- Inter Yes Yes Yes Yes Yes

020302 Frequency
Hard
Handover
Based on
Coverage
WRFD- Inter Yes Yes Yes Yes Yes

020304 Frequency
Hard
Handover
Based on DL
QoS
WRFD- Inter-RAT Yes Yes Yes Yes Yes

020303 Handover
Based on
Coverage

020309 Handover
Based on DL
QoS

020308 Handover
Phase 2
WRFD- NACC Yes Yes Yes Yes Yes

02030801 (Network
Assisted Cell
Change)
WRFD- PS Yes Yes Yes Yes Yes
02030802 Handover
Between
UMTS and
GPRS

020305 Handover
Based on
Service

020306 Handover
Based on
Load
WRFD- 3G/2G Yes Yes Yes Yes Yes

020310 Common
Load
Management
2 Overview
2.1 Overview of Handover Types
Being a basic function of the cellular mobile network, the handover ensures that UEs in the
CELL_DCH state can process services without interruptions when they move.
illustrates the handovers supported by the Universal Mobile Telecommunications
Figure 2-1
System (UMTS).
• By the frequency or RAT of the target cell, handovers can be classified into intra-
frequency, inter-frequency, and inter-RAT handovers. An intra-frequency handover
can be a soft or hard handover, while an inter-frequency or inter-RAT handover can
only be a hard handover.
• By trigger cause, handovers can be classified into coverage-, QoS-, load-, service-, and
HCS-based handovers.
• By whether measurement is required before handover execution, handovers can be
classified into measurement-based handovers and blind handovers.
• By handover user type, handovers can be classified into R99 user and HSPA user
handovers.
Figure 2-1 Handovers supported by the UMTS
Table 2-1 lists handover-related features and reference sections or documents.

Table 2-1 Handover-related features and reference sections or documents
Type Feature Name Reference
Intra- WRFD-020201 Intra NodeB Softer 3 Intra-Frequency Handover

frequency Handover
handover
WRFD-020202 Intra RNC Soft Handover
WRFD-020203 Inter RNC Soft Handover
WRFD-020301 Intra Frequency Hard

Handover
Inter- WRFD-020302 Inter Frequency Hard 4.3 Coverage- and QoS-based Handover
frequency Handover Based on Coverage
handover
WRFD-020304 Inter Frequency Hard
Handover Based on DL QoS
Type Feature Name Reference
WRFD-020103 Inter Frequency Load 4.4 Load-based Inter-Frequency

Balance Handover
WRFD-02040004 Traffic Steering and Directed Retry Decision Feature

Load Sharing During RAB Setup Parameter Description
Inter-RAT WRFD-020303 Inter-RAT Handover Based 4.3 Coverage- and QoS-based Handover
handover on Coverage
WRFD-020309 Inter-RAT Handover Based

on DL QoS
WRFD-020306 Inter-RAT Handover Based 4.5 Load-based UMTS-to-GSM Handover

on Load
WRFD-020305 Inter-RAT Handover Based 4.7 Service-based UMTS-to-GSM

on Service Handover
WRFD-020308 Inter-RAT Handover Phase 4.9 UMTS-to-GSM Handovers When

2 NACC Is Supported and 4.10 UMTS-to-
GSM PS Handover
WRFD-02030801 NACC (Network Assisted 4.9 UMTS-to-GSM Handovers When

Cell Change) NACC Is Supported
WRFD-02030802 PS Handover Between 4.10 UMTS-to-GSM PS Handover

UMTS and GPRS
WRFD-020310 3G/2G Common Load 4.11.6 Inter-RAT Load Information

Management Exchange
WRFD-150220 Coverage Based PS Interoperability Between UMTS and LTE

Handover from UMTS to LTE Feature Parameter Description
WRFD-150217 Load Based PS Handover

from UMTS to LTE
WRFD-140218 Service-Based PS
Handover from UMTS to LTE
Inter- WRFD-021200 HCS (Hierarchical Cell 4.8 Speed-based Inter-Frequency and

frequency and Structure) Inter-RAT Handover
inter-RAT
Handovers WRFD-01061006 HSDPA Mobility 5 HSPA Handover
Management
WRFD-01061204 HSUPA Mobility

Management
2.2 Introduction
2.2.1 WRFD-020201 Intra NodeB Softer Handover

This feature is concerned with intra-NodeB softer handover. The intra-NodeB softer handover
can provide a higher combination gain (maximum combination) and reduce the occupation of
transmission resources on the Iub interface. For details, see 3 Intra-Frequency Handover.
2.2.2 WRFD-020202 Intra RNC Soft Handover
This feature enables intra-RNC soft handovers. Compared with the intra-NodeB softer handover,
the intra-RNC soft handover has a wider application scope. The intra-RNC soft handover enables
macro diversity combination and each radio link (RL) has its own transport bearer on the Iub
interface. For details, see 3 Intra-Frequency Handover.
2.2.3 WRFD-020203 Inter RNC Soft Handover
This feature enables inter-RNC soft handovers. The inter-RNC soft handover function enables
the establishment of an RL on the drift radio network controller (DRNC) and the macro diversity
combination on the source radio network controller (SRNC) through the Iur interface. For
details, see 3 Intra-Frequency Handover.
2.2.4 WRFD-020301 Intra Frequency Hard Handover
This feature is concerned with intra-frequency hard handover. When the soft handover fails, the
RNC enables the UE to move between cells through hard handover. For details, see 3 Intra-
Frequency Handover.
2.2.5 WRFD-020302 Inter Frequency Hard Handover Based on Coverage
This feature introduces inter-frequency hard handover triggered by Active Set quality
measurement event 2D or by Uplink Radio Link QoS or emergency blind handover triggered by
event 1F. For details, see 4.3 Coverage- and QoS-based Handover.
2.2.6 WRFD-020303 Inter-RAT Handover Based on Coverage
This feature is related to inter-RAT handover based on coverage such as Active Set Quality
measurement 2D, UE uplink QoS or emergency blind handover triggered by event 1F. This
feature deals with the inter-RAT handover caused by coverage reason or UE mobility. For
details, see 4.3 Coverage- and QoS-based Handover.
2.2.7 WRFD-020304 Inter Frequency Hard Handover Based on DL QoS
When the load of services is high in the cell and downlink QoS drops, this feature enables the
UE to be handed over to an inter-frequency cell, guaranteeing QoS requirements. For details, see
4.3 Coverage- and QoS-based Handover.
2.2.8 WRFD-020309 Inter-RAT Handover Based on DL QoS
When the load of voice and PS BE services is high in the cell and downlink QoS drops, this
feature enables the UE to be handed over to an inter-RAT cell, guaranteeing QoS requirements.
For details, see 4.3 Coverage- and QoS-based Handover.
2.2.9 WRFD-020306 Inter-RAT Handover Based on Load
When a cell is in initial congestion state, this feature enables some UEs in the cell to be handed
over to an inter-RAT co-coverage cell, reducing the load of the cell. For details, see 4.5 Load-based
UMTS-to-GSM Handover.
2.2.10 WRFD-020305 Inter-RAT Handover Based on Service
This feature supports UMTS-to-GSM handovers based on service attributes. When 3G and 2G
coexist, this feature enables the 3G traffic to be directed to the 2G system. For details, see 4.7
Service-based UMTS-to-GSM Handover.
2.2.11 WRFD-01061006 HSDPA Mobility Management
This feature is related to HSDPA mobility management in different scenarios. This feature
ensures that the HSDPA services are continuous. For details, see 5.1 HSDPA Handover.
2.2.12 WRFD-01061204 HSUPA Mobility Management
This feature is related to HSUPA mobility management. This feature can ensure that HSUPA
services are continuous. For details, see 5.2 HSUPA Handover.
2.2.13 WRFD-021200 HCS (Hierarchical Cell Structure)
This feature complies with the hierarchical cell structure (HCS) as stipulated in 3GPP
specifications. It enables the UE to be handed over to the relevant hierarchical cell according to
its moving speed. For details, see 4.8 Speed-based Inter-Frequency and Inter-RAT Handover.
2.2.14 WRFD-020308 Inter-RAT Handover Phase 2
This feature provides the inter-RAT relocation procedure for NACC and PS services to shorten
the interruption time of PS services caused by inter-RAT handover. For details, see 4.9 UMTS-to-
GSM Handovers When NACC Is Supported and 4.10 UMTS-to-GSM PS Handover.
2.2.15 WRFD-02030801 NACC (Network Assisted Cell Change)
This feature supports the standard NACC procedure defined in 3GPP specifications. For details,
see 4.9 UMTS-to-GSM Handovers When NACC Is Supported.
2.2.16 WRFD-02030802 PS Handover Between UMTS and GPRS
This feature enables the relocation of PS services between systems. For details, see 4.10 UMTS-to-
GSM PS Handover.
2.2.17 WRFD-020310 3G/2G Common Load Management
During inter-RAT handover or inter-system direct retry, this feature supports the transfer of load
information as stipulated in 3GPP specifications to reduce inter-RAT ping-pong handover. For
details, see 4.11.6 Inter-RAT Load Information Exchange.
3 Intra-Frequency Handover
3.1 Overview
Intra-frequency handovers can be classified into the following two types:

• Intra-frequency soft handover: Multiple radio links are connected to a UE at the same
time during a handover.
• Intra-frequency hard handover: Only one radio links is connected to a UE during a
handover.
3.1.1 Intra-Frequency Soft Handover
The intra-frequency soft handover is more commonly used than the intra-frequency hard
handover. The types of intra-frequency soft handover are as follows:
• Softer handover: This type of handover occurs within a NodeB, and the NodeB
performs maximum ratio combining (MRC) for uplink signals. This type of handover
is implemented by the WRFD-020201 Intra NodeB Softer Handover feature.
Softer handovers can be performed only between cells in the same uplink resource group. For versions
earlier than RAN13.0, softer handovers cannot be performed between cells that are configured in
different downlink resource groups. For RAN13.0 and later versions, softer handovers can be
performed between cells that are configured in different downlink resource groups.
• Intra-RNC inter-NodeB soft handover: During this type of handover, the RNC
performs selective combining for uplink signals. This type of handover is
implemented by the WRFD-020202 Intra RNC Soft Handover feature.
• Inter-RNC soft handover: During this type of handover, the RNC selectively combines
uplink signals. This type of handover is implemented by the WRFD-020203 Inter
RNC Soft Handover feature.
During an intra-frequency soft handover, a UE can be connected to multiple UTRAN access
points at the same time. Addition and removal of radio links can be implemented through the
ACTIVE SET UPDATE message.
Table 3-1 describes the differences between the softer handover and soft handover.
Table 3-1 Differences between the softer handover and soft handover
Item Softer Handover Soft Handover
Scenario The UE is in the coverage The UE is in the coverage

overlap of multiple neighboring overlap of two neighboring
cells served by a NodeB. cells served by different
The UE communicates with NodeBs.
multiple cells by setting up The UE communicates with
multiple channels over the Uu multiple cells by setting up
interface. multiple channels over the Uu
interface.
Uplink signal The DivCtrlField (BSC6900, Selective combining is used.

BSC6910) parameter specifies
Item Softer Handover Soft Handover
whether to use MRC or

selective combining.
Downlink signal MRC is used. MRC is used.
Resource utilization Less Iub bandwidth is More Iub bandwidth is

occupied. occupied.
HO_INTRA_FREQ_SOFT_HO_SWITCH under the HoSwitch (BSC6900, BSC6910)

parameter specifies whether soft and softer handovers are allowed. The default value is ON,
indicating that soft and softer handovers are allowed. Upon receiving the event 1A, 1B, 1C, or
1D report from a UE, the RNC initiates a soft handover for the UE, for example, to add or
remove a link.
An inter-RNC intra-frequency soft handover is allowed if all the following conditions are met:
• An Iur interface is configured between the source RNC and the target RNC.
• The target cell served by the target RNC meets the intra-frequency soft handover
requirements.
• All the switches listed in Table 3-2 are turned on.
Table 3-2 Switches for cross-Iur intra-frequency soft handovers
Scenario Parameter Option Function
An RB has SHOTRIG CS_SHO_SWITCH Specifies whether a

been (BSC6900, cross-Iur soft
established. BSC6910) handover is allowed
for CS services.
HSPA_SHO_SWITCH Specifies whether a

cross-Iur soft
handover is allowed
for HSPA services.
NON_HSPA_SHO_SWITCH Specifies whether a

cross-Iur soft
handover is allowed
for non-HSPA PS
services.
No RB is HoSwitch HO_MC_SIGNAL_IUR_INTRA_SWITCH Specifies whether a

established. (BSC6900, cross-Iur soft
BSC6910) handover is allowed.
CMP_IUR_SHO_DIVCTRL_SWITCH must be selected under the CmpSwitch (BSC6900,

BSC6910) parameter when all the following conditions are true: During an inter-RNC soft
handover, multiple radio links of the UE are connected to the same or different NodeBs under
the target RNC; intra-frequency neighboring cells for the inter-RNC soft handover are
configured in different uplink resource groups. Under this circumstance, if the NodeB under the
target RNC carries multiple radio links, the NodeB determines whether to combine the radio
links on the NodeB based on the value of DivCtrlField (BSC6900, BSC6910).
3.1.2 Intra-Frequency Hard Handover
The WRFD-020301 Intra Frequency Hard Handover feature describes the intra-frequency hard
handover algorithm, for which the new radio link can be established only after the original radio
link is removed. The intra-frequency hard handover uses fewer transmission resources compared
with the intra-frequency soft handover.
The intra-frequency hard handover is used in the following scenario: When the intra-frequency
soft handover fails due to the target cell congestion, the RNC attempts an intra-frequency hard
handover.
If no Iur interface is configured between two RNCs, neither the soft handover nor the intra-frequency hard handover
without SRNS relocation is allowed between them. In this case, the combined hard handover and SRNS relocation is
allowed. For details, see SRNS Relocation and DSCR Feature Parameter Description.
HO_INTRA_FREQ_HARD_HO_SWITCH under the HoSwitch (BSC6900, BSC6910)

parameter specifies whether the intra-frequency hard handover is allowed. By default, this switch
is set to ON.
An inter-RNC intra-frequency hard handover is allowed if all the following conditions are met:
• An Iur interface is configured between the source RNC and the target RNC.
• The target cell served by the target RNC meets the intra-frequency hard handover
requirements.
• HHOTRIG (BSC6900, BSC6910) is set to ON.
3.2 Signaling Procedures for Intra-Frequency Handover
3.2.1 Intra-NodeB Intra-Frequency Soft Handover
This section describes the signaling procedure for the intra-frequency soft handover within a
NodeB.
Figure 3-1shows the procedure for the intra-frequency soft handover when a UE moves from one
cell to another cell within the same NodeB.
Figure 3-1 Procedure for intra-NodeB intra-frequency soft handover
The connections involved in the intra-NodeB intra-frequency softer handover change are as
follows:
1. Before the softer handover, only cell 1 is connected to the UE.
2. During the softer handover, both cell 1 and cell 2 are connected to the UE.
3. After the softer handover, only cell 2 is connected to the UE. Cell 1 is removed from
the active set.
Figure 3-2 shows the signaling procedure for the intra-NodeB intra-frequency soft handover.
Figure 3-2 Signaling procedure for the intra-NodeB intra-frequency soft handover
3.2.2 Intra-RNC Inter-NodeB Intra-Frequency Soft Handover
This section describes the signaling procedure for the intra-RNC inter-NodeB intra-frequency
soft handover.
Figure 3-3 Procedure for the intra-RNC inter-NodeB intra-frequency soft handover
1. Before the handover, only NodeB 1 is connected to the UE.
2. During the handover, both NodeBs are connected to the UE.
3. After the handover, only NodeB 2 is connected to the UE. The radio link between
NodeB 1 and the UE is removed.
Figure 3-4 Signaling procedure for the intra-RNC inter-NodeB intra-frequency soft handover
3.2.3 Inter-RNC Intra-Frequency Soft Handover
This section describes the signaling procedure for the inter-RNC intra-frequency soft handover.
Figure 3-5 Procedure for the inter-RNC intra-frequency soft handover
1. Before the handover, the UE is connected to NodeB 1 and NodeB 2.

2. After the SRNC makes a soft handover decision, it sets up a connection between
NodeB 3 under the drift RNC (DRNC) and the UE, and releases the connection
between NodeB 1 and the UE.
Figure 3-6 Signaling procedure for the inter-RNC intra-frequency soft handover
3.2.4 Intra-RNC Inter-NodeB Intra-Frequency Hard Handover
The signaling procedure for the intra-RNC inter-NodeB intra-frequency hard handover is similar
to that for the intra-NodeB intra-frequency hard handover. This section describes the signaling
procedure for only the intra-RNC inter-NodeB intra-frequency hard handover.
Figure 3-7 Procedure for the intra-RNC inter-NodeB intra-frequency hard handover
Figure 3-8 Signaling procedure for the intra-RNC inter-NodeB intra-frequency hard handover
3.2.5 Inter-RNC Intra-Frequency Hard Handover

shows the procedure for the intra-frequency hard handover when a UE moves from one
Figure 3-9
NodeB served by an SRNC to another NodeB served by a DRNC.
Figure 3-9 Procedure for the inter-RNC intra-frequency hard handover
Figure 3-10 Signaling procedure for the inter-RNC intra-frequency hard handover
3.3 Intra-Frequency Handover Procedure
Upon the reception of a measurement report from the UE, the RNC makes a handover decision
and performs the corresponding handover. Figure 3-11 uses the intra-frequency handover
procedure as an example to show the three phases in a handover process.
Figure 3-11 Intra-frequency handover procedure
3.4 Intra-Frequency Handover Measurement
After a UE in a call enters the CELL_DCH state and measurement is triggered, the RNC sends
the UE a MEASUREMENT CONTROL message. Upon receiving the message, the UE performs
measurements as required and reports measurement results to the RNC. The MEASUREMENT
CONTROL message includes the following information:
• Measurement mode, handover threshold, and hysteresis
• Neighboring cell list
If the neighboring cell combination function is disabled, the RNC selects the target
cells from the non-blacklisted neighboring cells of the best cell based on the priority
(specified by the Nprio (BSC6900, BSC6910) parameter) in a descending order. If two
or more neighboring cells have the same Nprio (BSC6900, BSC6910) setting, the RNC
randomly selects up to 32 cells (including the serving cell). If the neighboring cell
combination function is enabled, the RNC selects neighboring cells according to the
rules described in 7 Neighboring Cell Combination.
▪ If the APFlag (BSC6900, BSC6910) parameter is set to TRUE for an intra-frequency

neighboring cell under a neighboring RNC, information about the intra-frequency
neighboring cell will not be contained in the measurement control message.
▪ For blacklisted neighboring cells, BLACKLIST_FLAG under the NCellCapContainer
(BSC6900, BSC6910) parameter is selected.
• Layer 3 filter coefficient

As specified in 3GPP TS 25.331, the RNC includes the Layer 3 filter coefficient
specified by IntraFreqFilterCoef (BSC6900, BSC6910) or IntraFreqFilterCoef
(BSC6900, BSC6910) (used only when the best cell is served by the DRNC) in the
MEASUREMENT CONTROL message to ensure that UEs can obtain stable signals.
After sending a measurement control message to a UE in the CELL_DCH state, the RNC sends
another measurement control message to the UE in any of the following scenarios:
• Best cell change
• Incoming handover
• Changes in information in the original intra-frequency measurement control message
3.4.1 Intra-Frequency Handover Measurement Control
The RNC delivers algorithm-specific handover parameters in the intra-frequency handover

measurement control message to the UE. Multiple algorithms may be involved.
Algorithms Involved in Intra-Frequency Handover Measurement
Algorithms involved in intra-frequency handover measurement are as follows:

1. Algorithm 1: Coverage-based intra-frequency handover, which is depicted in this
document. This algorithm is a basic intra-frequency handover measurement control
algorithm. Specific handover parameters must be configured in the cell-level MO
UCELLINTRAFREQHO and RNC-level MO UINTRAFREQHO. If both RNC-
level and cell-level parameters are configured, the cell-level parameter settings
prevail.
2. Algorithm 2: Event 1D-triggered HSDPA serving cell change based on RSCP. For
details, see Procedure Optimization Feature Parameter Description. After this function is
activated, handover parameters listed in Table 3-3 must be configured for desired UEs.
Table 3-3 Intra-frequency handover parameters involved in event 1D-triggered HSDPA
serving cell change based on RSCP
Parameter Name Parameter ID
Hysteresis for RSCP 1D for HystFor1DRSCP (BSC6900, BSC6910)

HSPA Serve Cell Change
Time to Trigger RSCP 1D TrigTime1DRSCP (BSC6900, BSC6910)

for HSPA Serve Cell
Change
3. Algorithm 3: WRFD-020801 Cell ID+RTT Function Based LCS. For details, see LCS
Feature Parameter Description. After the forced soft handover in CELLID+RTT
positioning is activated, handover parameters listed in Table 3-4 must be configured.
Table 3-4 Handover parameters related to the forced soft handover in CELLID+RTT
positioning
1A Event Relative IntraRelThdFor1A (BSC6900, BSC6910)

Threshold
1A Event Trigger Delay TrigTime1A (BSC6900, BSC6910)

Time
1B Event Relative IntraRelThdFor1B (BSC6900, BSC6910)

Threshold
1B Event Trigger Delay TrigTime1B (BSC6900, BSC6910)

Time
4. Algorithm 4: WRFD-180107 Efficient Improvement of Call Drop-related KPIs in

Multi-Sector. For details, see Efficient Improvement of Call Drop-related KPIs in Multi-Sector
Feature Parameter Description. After this feature is activated, handover parameters listed
in Table 3-5 must be configured.
Table 3-5 Handover parameters related to the Efficient Improvement of Call Drop-related
KPIs in Multi-Sector feature
CS Non-VP Service Event IntraRelThdFor1ACSNVP (BSC6900, BSC6910)

1A Relative THD
PS Service Event 1A IntraRelThdFor1APS (BSC6900, BSC6910)

Relative Threshold
VP is short for video phone.
5. Algorithm 5: WRFD-191102 KPI Improvement for High-Speed Users. For details,

see KPI Improvement for High-Speed Users Feature Parameter Description. After this feature is
activated, handover parameters listed in Table 3-6 must be configured for high-speed
UEs.
Table 3-6 Handover parameter used for high-speed UEs
Event Parameter Name Parameter ID
Event 1A VP Service 1A Relative Threshold IntraRelThld1ACSVPForHS (BSC6900,

For HS BSC6910)
CS Non-VP Service 1A Relative IntraRelThld1ACSNVPForHS (BSC6900,

THD For HS BSC6910)
PS Service 1A Relative Threshold IntraRelThld1APSForHS (BSC6900,

For HS BSC6910)
1A Triggering Delay For HS TrigTime1AForHS (BSC6900, BSC6910)
Event 1B CS Non-VP Service 1B Relative IntraRelThld1BCSNVPForHS (BSC6900,

THD For HS BSC6910)
PS Service 1B Relative Threshold IntraRelThld1BPSForHS (BSC6900,

For HS BSC6910)
PS Service 1B Relative Threshold IntraRelThld1BPSForHS (BSC6900,

For HS BSC6910)
1B Triggering Delay For HS TrigTime1BForHS (BSC6900, BSC6910)
Event 1D 1D Hysteresis For HS HystFor1DForHS (BSC6900, BSC6910)
1D Triggering Delay For HS TrigTime1DForHS (BSC6900, BSC6910)
N/A Intra-Freq L3 Filter Coefficient For IntraFreqFilterCoefForHS (BSC6900,

HS BSC6910)
6. Algorithm 6: Soft handover performance improvement under weak coverage. For

details, see Soft Handover Performance Improvement Under Weak Coverage. After this function
is activated, handover parameters listed in Table 3-7 must be configured for UEs under
weak coverage.
Table 3-7 Intra-frequency handover parameters used for UEs under weak coverage
Event 1A Weak Cov 1A Relative Thld for CS WeakCovRelThld1ACS (BSC6900, BSC6910)
Weak Cov 1A Relative Thld for PS WeakCovRelThld1APS (BSC6900, BSC6910)
Weak Cov Delayed Time to WeakCovDelayTrigTime1A (BSC6900,

Trigger 1A Event BSC6910)
Event 1B Weak Cov 1B Relative Thld for CS WeakCovRelThld1BCS (BSC6900, BSC6910)
Weak Cov 1B Relative Thld for PS WeakCovRelThld1BPS (BSC6900, BSC6910)
Weak Cov Delayed Time to WeakCovDelayTrigTime1B (BSC6900,

Trigger 1B Event BSC6910)
N/A Weak Cov SHO Measurement WeakCovFilterCoef (BSC6900, BSC6910)

Control Filter Coef
Handover Parameter Configurations When Two or More Algorithms Take Effect Simultaneously
When two or more of the preceding algorithms take effect simultaneously, the following
principles apply to parameter configurations:
• Parameters related to events 1A and 1B are involved in the following algorithms:
algorithm 1, algorithm 3, algorithm 4, algorithm 5, algorithm 6. The parameter
configuration complies with the following principles:
1. If two or three of algorithms 1, 3, and 4 take effect simultaneously, use the
parameter configuration of the highest priority. The parameter
configuration in algorithm 3 is of the highest priority while that in
algorithm 1 is of the lowest.
2. Take the smaller or greater one between the parameter configurations
obtained in step 1 and algorithm 5 or 6. For details, see Table 3-8.
Table 3-8 Configuration principles of parameters related to events 1A and 1B
Parameter Name Configuration Principle
Relative threshold for event 1A decision when Use the maximum value.
VP services are performed
non-VP services are performed in the CS
domain
PS services are performed
Event 1A trigger delay time Use the minimum value.
Relative threshold for event 1B decision when Use the maximum value.
VP services are performed
non-VP services are performed in the CS
domain
PS services are performed
Event 1B trigger delay time Use the maximum value.
• Event 1D related parameters are involved in algorithms 1 and 2.Event 1D related

parameters are involved in algorithms 1, 2, and 5. The parameter configuration
complies with the following principles:
1. If both algorithms 1 and 2 take effect and a parameter is configured in both
algorithms, use the parameter configuration in algorithm 2.
2. Take the smaller one between the parameter value obtained in step 1 and
that in algorithm 5.
• Parameters related to intra-frequency Layer 3 filtering are involved in algorithms 1, 5,
and 6. If two or three of algorithms 1, 5, and 6 take effect simultaneously, use the
smallest parameter configuration.
Assume that algorithms 1, 2, 3, 4, 5, and 6 take effect simultaneously:
• The greatest or smallest values of parameters related to events 1A and 1B in
algorithms 3, 5, and 6 are used.
• The smaller values of parameters related to event 1D in algorithms 2 and 5 are used.
• The smallest value in algorithms 1, 5, and 6 is used as the Layer 3 filtering coefficient
for intra-frequency handover measurements.
Table 3-9 lists the parameter configuration adopted when all algorithms take effect.
Table 3-9 Parameter configuration adopted when all algorithms take effect
Event Parameter Name Configuration Principle Parameter Setting
1A Relative threshold Take the maximum one Max(IntraRelThdFor1A (BSC6900,

for event 1A from the following values: BSC6910),
decision when VP Relative threshold for IntraRelThld1ACSVPForHS
services are event 1A decision for (BSC6900, BSC6910),
performed in the CS triggering forced soft WeakCovRelThld1ACS (BSC6900,
domain handover in BSC6910))
CELLID+RTT
positioning, Relative
threshold for event 1A
decision for high-speed
moving UEs when VP
services are performed,
Relative threshold for
event 1A decision for
UEs under weak
coverage areas when VP
services are performed
Relative threshold Take the maximum one Max(IntraRelThdFor1A (BSC6900,

for event 1A from the following values: BSC6910),
decision when non- Relative threshold for IntraRelThld1ACSNVPForHS
VP services are event 1A decision for (BSC6900, BSC6910),
performed in the CS triggering forced soft WeakCovRelThld1ACS (BSC6900,
CELLID+RTT
moving UEs when non-
VP services are
performed in the CS
domain, Relative

decision for UEs under
weak coverage areas
when non-VP services
are performed in the CS
domain
Relative threshold Take the maximum one Max(IntraRelThdFor1A (BSC6900,

for event 1A from the following values: BSC6910), IntraRelThld1APSForHS
decision when PS Relative threshold for (BSC6900, BSC6910),
services are event 1A decision for WeakCovRelThld1APS (BSC6900,
performed triggering forced soft BSC6910))
handover in
CELLID+RTT
moving UEs when PS
event 1A decision for
UEs under weak
coverage areas when PS
Event 1A trigger Take the minimum one Min(TrigTime1A (BSC6900, BSC6910),

delay time from the following values: TrigTime1AForHS (BSC6900,
Event 1A trigger delay BSC6910),
time for forced soft WeakCovDelayTrigTime1A
handover in (BSC6900, BSC6910))
CELLID+RTT
positioning, Event 1A
trigger delay time for
high-speed moving UEs,
Event 1A trigger delay
time for UEs under weak
coverage areas
1B Relative threshold Take the maximum one Max(IntraRelThdFor1B (BSC6900,

for event 1B from the following values: BSC6910),
decision when VP Relative threshold for IntraRelThld1BCSVPForHS
services are event 1B decision for (BSC6900, BSC6910),
performed triggering forced soft WeakCovRelThld1BCS (BSC6900,
handover in BSC6910))
CELLID+RTT
threshold for event 1B
moving UEs when VP

event 1B decision for
UEs under weak
coverage areas when VP
Relative threshold Take the maximum one Max(IntraRelThdFor1B (BSC6900,

for event 1B from the following values: BSC6910),
decision when non- Relative threshold for IntraRelThld1BCSNVPForHS
VP services are event 1B decision for (BSC6900, BSC6910),
performed in the CS triggering forced soft WeakCovRelThld1BCS (BSC6900,
CELLID+RTT
moving UEs when non-
VP services are
performed in the CS
domain, Relative
decision for UEs under
weak coverage areas
when non-VP services
are performed in the CS
domain
Relative threshold Take the maximum one Max(IntraRelThdFor1B (BSC6900,

for event 1B from the following values: BSC6910), IntraRelThld1BPSForHS
decision when PS Relative threshold for (BSC6900, BSC6910),
services are event 1B decision for WeakCovRelThld1BPS (BSC6900,
performed triggering forced soft BSC6910))
handover in
CELLID+RTT
moving UEs when PS
event 1B decision for
UEs under weak
coverage areas when PS
Event 1B trigger Take the maximum one Max(TrigTime1B (BSC6900,

delay time from the following values: BSC6910), TrigTime1BForHS
Event 1B trigger delay (BSC6900, BSC6910),
time for forced soft WeakCovDelayTrigTime1B

handover in (BSC6900, BSC6910))
CELLID+RTT
positioning, Event 1B
trigger delay time for
high-speed moving UEs,
Event 1B trigger delay
time for UEs under weak
coverage areas
1D Hysteresis for Take the smaller one Min(HystFor1DRSCP (BSC6900,

RSCP 1D for HSPA from the following values: BSC6910), HystFor1DForHS
Serve Cell Change Hysteresis for RSCP- (BSC6900, BSC6910))
based event 1D, Event
1D hysteresis for high-
speed moving UEs
Event 1D trigger Take the smaller one Min(TrigTime1DRSCP (BSC6900,

delay time from the following values: BSC6910),TrigTime1DForHS
RSCP-based event 1D (BSC6900, BSC6910))
trigger delay time, Event
1D trigger delay time for
high-speed moving UEs
N/A Layer 3 filtering Take the minimum one • The best cell resides in the
coefficient for the from the following values: SRNC:
intra-frequency Layer 3 filtering Min(IntraFreqFilterCoef
measurement coefficient for intra- (BSC6900, BSC6910),
frequency handovers, IntraFreqFilterCoefForHS
Layer 3 filtering (BSC6900, BSC6910),
coefficient for the intra- WeakCovFilterCoef
frequency measurement (BSC6900, BSC6910))
for high-speed moving • The best cell resides in the
UEs, Layer 3 filtering DRNC:
coefficient for the intra-
frequency measurement Min(IntraFreqFilterCoef
for UEs under weak (BSC6900, BSC6910),
coverage areas IntraFreqFilterCoefForHS
(BSC6900, BSC6910),
WeakCovFilterCoef
(BSC6900, BSC6910))
Soft Handover Performance Improvement Under Weak Coverage
To enable the function of soft handover performance improvement under weak coverage, set the
CellWeakCovShoSwitch (BSC6900, BSC6910) parameter to ON in the best cell. If the best cell
of a UE is under the DRNC, this function does not take effect on this UE.
If the function of soft handover performance improvement under weak coverage is enabled,
applying the soft handover parameters specific to UEs under weak coverage helps reduce service
drops due to delayed handovers triggered under weak coverage on the condition of using
common soft handover parameters. This function provides the following two sub-functions:
• Identifying UEs under weak coverage areas
1. The RNC obtains the current Ec/N0 of a UE by using the method listed in
Table 3-10.
Table 3-10 Methods for obtaining Ec/N0 of UEs of different types
UE Type How to Obtain Ec/N0
New UE The RNC uses the Ec/N0 carried in the RRC connec
setup request.
UE with cell update The RNC uses the Ec/N0 carried in the cell update
request sent by the UE.
UE in an incoming coverage-based The RNC uses the Ec/N0 carried in the inter-frequen
inter-frequency handover handover measurement report.
UE in an F2D/P2D procedure • If the F2D/P2D procedure is triggered by e

4A and the event 4A report contains Ec/N
RNC uses the Ec/N0 contained in the rep
• If the procedure is not triggered by event
the RNC does not check whether the UE
under the weak coverage area.
UE with best cell change The RNC uses the Ec/N0 contained in the latest eve
1X-triggered intra-frequency measurement report.
Other UEs The RNC delivers periodic intra-frequency measurem

control messages to the UE. The UE periodically rep
the Ec/N0 of the current cell at an interval specified
WeakCovIntrafreqMeasPeriod (BSC6900, BSC6910)
parameter.
2. The RNC compares the obtained Ec/N0 with the

WeakCovBestCellEcN0LowThld parameter value.
• If the obtained Ec/N0 is not greater than the
WeakCovBestCellEcN0LowThld (BSC6900, BSC6910)
parameter value, the RNC considers the UE to be under a weak
coverage area.
• If the obtained Ec/N0 is greater than the
WeakCovBestCellEcN0HThld (BSC6900, BSC6910)
parameter value, the RNC considers the UE to be not under a
weak coverage area.
• Adjusting handover parameters
For UEs under weak coverage areas, the RNC determines whether to change related
intra-frequency handover parameters of the UEs in the intra-frequency soft handover
measurement control message to those specific to UEs under weak coverage areas.
▪ If the intra-frequency handover parameters after the function of soft
handover performance improvement under weak coverage are applied, the
RNC does not modify the intra-frequency soft handover measurement
control message.
For details about the intra-frequency handover parameters used after the function of soft
handover performance improvement under weak coverage, see Handover Parameter
Configurations When Two or More Algorithms Take Effect Simultaneously .
▪ If the intra-frequency handover parameters before the function of soft

RNC modifies the intra-frequency soft handover measurement control
message. First, the RNC starts a timer specified by
WeakCovShoMCProtectTimer (BSC6900, BSC6910). After the timer
expires, the RNC sends the UE a new measurement control message that
contains the parameter configurations listed in Table 3-11, instructing the UE
to use handover parameters specific to UEs under weak coverage areas.
Table 3-11 Handover parameters specific to UEs under weak coverage areas
Parameter Name Parameter ID Remarks
Weak Cov SHO WeakCovFilterCoef (BSC6900, The default value is

Measurement Control BSC6910) recommended.
Filter Coef
Weak Cov 1A Relative WeakCovRelThld1ACS The default value is

Thld for CS (BSC6900, BSC6910) recommended. This parameter
is valid for all CS services,
including VP services.
Weak Cov 1A Relative WeakCovRelThld1APS The default value is

Thld for PS (BSC6900, BSC6910) recommended.
Weak Cov 1B Relative WeakCovRelThld1BCS The default value is

Thld for CS (BSC6900, BSC6910) recommended. This parameter
is valid for all CS services,
including VP services.
Weak Cov 1B Relative WeakCovRelThld1BPS The default value is

Thld for PS (BSC6900, BSC6910) recommended.
Parameter Name Parameter ID Remarks
Weak Cov Delayed Time WeakCovDelayTrigTime1A The default value is

to Trigger 1A Event (BSC6900, BSC6910) recommended.
Weak Cov Delayed Time WeakCovDelayTrigTime1B The default value is

to Trigger 1B Event (BSC6900, BSC6910) recommended.
For UEs not under weak coverage areas, the RNC determines whether to change
related intra-frequency handover parameters of the UEs in the intra-frequency soft
handover measurement control message to those specific to UEs not under weak
coverage areas.
▪ If the intra-frequency handover parameters before the function of soft
RNC does not modify the intra-frequency soft handover measurement
control message.
▪ If the intra-frequency handover parameters after the function of soft
RNC operates as listed in Table 3-12.
Table 3-12 Processing of the intra-frequency measurement control message for
UEs not under weak coverage areas
If... Then...
The timer specified by The RNC includes handover parameters

WeakCovShoMCProtectTimer (BSC6900, specific to UEs not under weak coverage
BSC6910) expires areas in the intra-frequency soft handover
measurement control message and re-
initializes the timer.
The timer specified by No action is required.

WeakCovShoMCProtectTimer (BSC6900,
BSC6910) does not expire
During a soft handover in weak coverage areas, if the CellWeakCovShoSwitch (BSC6900,

BSC6910) parameter is reconfigured to OFF, the RNC delivers a measurement control message
including handover parameters specific to UEs not under weak coverage areas and re-initializes the
timer specified by WeakCovShoMCProtectTimer (BSC6900, BSC6910).
3.4.2 Measurement Quantities and Measurement Events Used for Intra-Frequency Handovers
Measurement Quantity
The IntraFreqMeasQuantity (BSC6900, BSC6910) parameter specifies the measurement
quantity used for a handover. For intra-frequency handovers, the Ec/N0 or RSCP value of the
CPICH can be used as the measurement quantity.
Measurement Event
In the intra-frequency handover, the UE reports measurement results to the RNC through event
reporting. Table 3-13 lists the events involved in the intra-frequency handover.
Table 3-13 Events involved in the intra-frequency handover
Event Description
1A A primary Common Pilot Channel (CPICH) enters the reporting range. This
indicates that the CPICH signal quality of a cell in the monitored set is close
to that 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.
1B A primary CPICH leaves the reporting range. This indicates that the CPICH
signal quality of a cell in the active set is lower than that of the best cell in the
active set and the difference between them is higher than a specified
threshold. The cell has to be removed from the active set.
1C The primary CPICH signal quality of a cell in the non-active set becomes
better than that of a cell in the active set. This indicates that the CPICH signal
quality of a cell exceeds that of the worst cell in the active set. The RNC
replaces the worst cell in the active set with a cell of good signal quality
indicated by the event 1C measurement report. MaxCellInActiveSet
(BSC6900, BSC6910) specifies the maximum number of cells in the active set.
1D The best cell changes. This indicates that the CPICH signal quality of a non-
best cell is higher than that of the best cell in the active set and the difference
between them exceeds a specified threshold, and the non-best cell becomes
the new best cell. The non-best cell can be a cell in the active set or in the
monitored set.
1F The signal quality of the best cell in the active set is lower than a specified
threshold.
3.4.3 Triggering of Event 1A
Event 1A is triggered under the following condition:
10 x Log(MNew) + CIONew ≥ W x 10 x Log ( ) + (1 – W) x 10 x Log(MBest) – (R1a – H1a/2)

Table 3-14 describes the variables in the preceding formula.
Table 3-14 Variables involved in triggering of event 1A
Variable Description Parameter
MNew Measurement value of the cell in N/A

the reporting range
CIONew Sum of the serving cell's CIO and CIO (BSC6900, BSC6910): CIO of the serving
the neighboring cell's CIO cell
CIOOffset (BSC6900, BSC6910): CIO of the
neighboring cell
W Weighting coefficient Weight (BSC6900, BSC6910)
Mi Measured value of a cell in the N/A

active set
NA Number of cells not forbidden to CellsForbidden1A (BSC6900, BSC6910):

affect the reporting range in the indicates whether adding the cell to the active
active set set affects the relative threshold of event 1A,
as indicated by the variable R1a.
MBest Measured value of the best cell in N/A

the active set
R1a Reporting range or the relative • IntraRelThdFor1ACSVP (BSC6900,

threshold of the soft handover BSC6910): indicates the relative
threshold for event 1A decision
when CS VP services are
performed.
• IntraRelThdFor1ACSNVP
(BSC6900, BSC6910): indicates the
relative threshold for event 1A
decision when non-VP services are
performed in the CS domain.
• IntraRelThdFor1APS (BSC6900,
BSC6910): indicates the relative
threshold for event 1A decision
when PS services are performed.
NOTE:
For the CS+PS combined services and single signaling
connection of the UE, the thresholds for CS services are
used.
H1a Event 1A hysteresis Hystfor1A (BSC6900, BSC6910)
Figure 3-12 shows how event 1A is triggered. In this procedure, both W and H1a are 0.
Figure 3-12 Triggering of event 1A when W and H1a are 0
• 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
In Figure 3-12, Th1A = (CPICH Ec/N0 of the best cell in the active set) – (Reporting range for
event 1A)
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 (BSC6900, BSC6910) (Time to trigger in Figure 3-12), the UE reports
event 1A.
If W is greater than 0 and H1a is 0, Th1A is the general signal quality of all the cells in the active
set minus the reporting range for event 1A.
After a UE reports event 1A to the RNC, the RNC may miss the measurement reports. If the
reported cell does not join the active set in a specified period of time, the UE starts to report the
event at an interval specified by ReportIntervalfor1A (BSC6900, BSC6910) to avoid missing of
measurement reports. If the actual number of reporting times exceeds the value of
PeriodMRReportNumfor1A (BSC6900, BSC6910), the UE stops periodic reporting.
For parameters related to the relative threshold for triggering event 1A and event 1A trigger delay time, see 3.4.1
Intra-Frequency Handover Measurement Control.
3.4.4 Triggering of Event 1B
Event 1B is triggered under the following condition:

10 x Log(Mold) + CIOold ≤ W x 10 x Log( ) + (1 – W) x 10 x Log(MBest) – (R1b + H1b/2)
Table 3-15 Variables involved in triggering of event 1B
Mold Measurement value of the cell that N/A

becomes worse
CIOold Sum of the serving cell's CIO and the CIO (BSC6900, BSC6910): CIO of the serving
neighboring cell's CIO cell
CIOOffset (BSC6900, BSC6910): CIO of the
neighboring cell
W Weighting coefficient Weight (BSC6900, BSC6910)
Mi Measured value of a cell in the active N/A

set
NB Number of cells not forbidden to affect CellsForbidden1B (BSC6900, BSC6910):

the reporting range in the active set indicates whether adding the cell to the
active set affects the relative threshold of
event 1B, as indicated by the variable R1b.
MBest Measured value of the best cell in the N/A

active set
R1b Reporting range or the relative • IntraRelThdFor1BCSVP

threshold of the soft handover (BSC6900, BSC6910): indicates the
relative threshold for event 1B
decision when CS VP services
are performed.
• IntraRelThdFor1BCSNVP
(BSC6900, BSC6910): indicates the
relative threshold for event 1B
decision when non-VP services
are performed in the CS domain.
• IntraRelThdFor1BPS (BSC6900,
BSC6910): indicates the relative
threshold for event 1B decision
when PS services are
performed.
NOTE:
For the CS+PS combined services and single

signaling connection of the UE, the thresholds for
CS services are used.
H1b Event 1B hysteresis Hystfor1B (BSC6900, BSC6910)
Configuration principle and restrictions: The value of H1b must be greater than that of H1a for a
service.
Figure 3-13 shows how event 1B is triggered. In this procedure, both W and H1b are 0.
Figure 3-13 Triggering of event 1B when W = 0 and H1b = 0

• B: signal quality curve of the non-best-cell in the active set
• C: curve of Th1B
In Figure 3-13, Th1B = (CPICH Ec/N0 of the best cell in the active set) – (reporting range for event
1B)
If the signal quality of a cell in the active set is higher than Th1B for a period of time specified by
TrigTime1B (BSC6900, BSC6910) (Time to trigger in Figure 3-13), the UE reports event 1B.
If W is greater than 0 and H1b is 0, then Th1B is the general signal quality of all the cells in the
active set minus the reporting range for event 1B.
For parameters related to the relative threshold for triggering event 1B and event 1B trigger delay time, see 3.4.1
3.4.5 Triggering of Event 1C
Event 1C is triggered under the following condition:

10 x Log(MNew) + CIONew ≥ 10 x Log(MInAS) + CIOInAS + H1c/2
Table 3-16 Variables involved in triggering of event 1C
MNew Measurement value of the cell in N/A

the reporting range
CIONew Sum of the values of the CIO of a Sum of CIO (BSC6900, BSC6910) and
cell where event 1C is reported CIOOffset (BSC6900, BSC6910)
and the CIO offset when the cell
acts as a neighboring cell
MInAS Measured value of the cell with N/A

weakest signals in the active set
CIOInAS Sum of the values of the CIO of Sum of CIO (BSC6900, BSC6910) and
the worst cell in the active set and CIOOffset (BSC6900, BSC6910)
the CIO offset when the cell acts
as a neighboring cell
H1c Event 1C hysteresis Hystfor1C (BSC6900, BSC6910)
Figure 3-14 shows how event 1C is triggered. In this procedure, the default parameter values are
used.
Figure 3-14 Triggering of event 1C

• B: signal quality curve of a cell in the active set
• 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/N0 of the worst cell in the active set) + (hysteresis/2)
If the signal quality of a cell that is not in the active set is higher than Th1C for a period of time
specified by TrigTime1C (BSC6900, BSC6910) (Time to trigger in Figure 3-14), the UE reports
event 1A.
The UE reports event 1C for qualified cells after the number of cells in the active set reaches the
maximum value. MaxCellInActiveSet (BSC6900, BSC6910) specifies the maximum number of
cells in the active set.
After a UE reports event 1C to the RNC, the RNC may miss the measurement reports. If the
event at an interval specified by ReportIntervalfor1C (BSC6900, BSC6910) to avoid missing of
PeriodMRReportNumfor1C (BSC6900, BSC6910), the UE stops periodic reporting.
3.4.6 Triggering of Event 1D
Event 1D is triggered under the following condition:

10 x Log(MNotBest) + CIONotBest ≥ 10 x Log(MBest) + CIOBest + H1d/2
The following table describes the variables in the preceding formula.
MNotBest Measured value of a non-best N/A

cell
MBest Measured value of the best cell N/A

in the active set
CIONotBest Sum of the serving cell's CIO Sum of CIO (BSC6900, BSC6910) and CIOOffset
and the neighboring cell's CIO (BSC6900, BSC6910)
CIOBest CIO of the best cell HoSwitch (BSC6900, BSC6910):

HO_CIO_1D_USED
• If HO_CIO_1D_USED is selected,
CIOBest equals CIO (BSC6900,
BSC6910).
• If HO_CIO_1D_USED is not
selected, CIOBes is 0.
H1d Event 1D hysteresis Hystfor1D (BSC6900, BSC6910)
Figure 3-15 shows how event 1D is triggered. In this procedure, the default parameter values are
used.
Figure 3-15 Triggering of event 1D

• B: signal quality curve of a non-best cell
• C: signal quality curve of Th1D
If the signal quality of a non-best cell is greater than Th1D for a period of time specified by
TrigTime1D (BSC6900, BSC6910) (Time to trigger in Figure 3-15), the UE reports event 1D.
For parameters related to the relative threshold for triggering event 1D and event 1D trigger delay time, see 3.4.1
3.4.7 Triggering of Event 1F
Event 1F is triggered when the following inequality is true and lasts for a period of time
specified by TrigTime1F (BSC6900, BSC6910):
10logMOld ≤ T1f – H1f/2
The following table describes the variables in the preceding formula.
MOld Measurement value of a cell N/A

whose signal deteriorates
T1f Absolute threshold IntraAblThdFor1FRSCP (BSC6900, BSC6910) or

IntraAblThdFor1FecNo (BSC6900, BSC6910)
H1f Event 1F hysteresis Hystfor1F (BSC6900, BSC6910)
When the inter-frequency or inter-RAT handover switch is turned on and there is only one cell in
the active set, the RNC performs inter-frequency blind handover after receiving event 1F. For
details, see 4.3.4.1 Inter-Frequency Handovers.
3.5 Intra-Frequency Handover Decision and Execution
Intra-Frequency Handover Decision and Execution Triggered by Event 1X
The intra-frequency handover decision and execution procedure depends on the different
measurement events that the RNC receives.
Upon receiving an event 1A, 1C, or 1D report, the RNC adds a target cell (excluding the
blacklisted neighboring cells of the best cell) to the active set only when the CPICH Ec/N0 of the
target cell is higher than the absolute threshold specified by SHOQualmin (BSC6900, BSC6910).
• To enable the UEs served by cells in the monitored set to report event 1D, you need to turn on the intra-
frequency hard handover switch, that is, select HO_INTRA_FREQ_HARD_HO_SWITCH under the
HoSwitch (BSC6900, BSC6910) parameter in the SET UCORRMALGOSWITCH command.
• For blacklisted neighboring cells, BLACKLIST_FLAG under the NCellCapContainer (BSC6900,
BSC6910) parameter is selected.
Table 3-17lists different types of intra-frequency handover decision and execution based on
different events.
Table 3-17 Intra-frequency handover decision and execution
Event Decision and Execution
1A When receiving an event 1A report, the RNC decides whether to add or replace a
cell in the active set.
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 cell quality indicated by
the 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 upper limit. If the number of
cells in the active set has reached the upper limit, the RNC determines whether to
initiate replacement of cells in the active set according to the switch for the function
of Intra-Frequency Handover Decision and Execution Triggered by Event 1A that Serves as a
Substitute for Event 1C.
1B When receiving an event 1B report, the RNC decides whether to remove a cell.
For event 1B, if there is more than one radio link in the active set, the RNC decides
whether to remove 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 cells in
the active set.
For event 1C, the UE reports a list that contains cells with good signals and the cells
to be replaced, and sequences the cells in descending order of cell quality indicated
by the measurement quantity. After receiving the list from the UE, the RNC replaces
the cells with poor signals in the active set with those with good signals 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 initiates the best cell
change and reconfigures measurement control.
• If the reported cell is in the monitored set, the RNC performs either of the
following operations and changes the best cell as the reported cell.
If the number of cells in the active set does not reach the upper limit, the
RNC adds the reported cell to the active set.
If the number of cells in the active set has reached the upper limit, the
RNC replaces the worst cell in the active set with the reported cell.
If the soft handover fails, the RNC determines whether the intra-frequency hard
handover is applicable, and if available, performs an intra-frequency hard handover.
When the only RAB of a PS service is released,

RAB_REL_SRV_CELL_CHG_CROSS_SWITCH under the OptimizationSwitch3
(BSC6900, BSC6910) parameter in the RNC MML command SET URRCTRLSWITCH specifies
whether to initiate a serving cell change procedure.
• If this option is selected, a serving cell change procedure is not allowed.
• If this option is not selected, a serving cell change procedure is allowed.
When WRFD-020203 Inter RNC Soft Handover enables cell addition or replacement in the
active set and the target cell is served by the DRNC, the DRNC will send information about the
inter-frequency neighboring cells of the target cell to the SRNC. To make the handover priority
of these inter-frequency neighboring cells more accurate, the handover priority optimization for
inter-frequency neighboring cells sent to the SRNC is introduced as follows:
• If PERFENH_DRNC_INTER_FREQ_NCELL_OPT_SWITCH under the
PerfEnhanceSwitch10 (BSC6900, BSC6910) parameter is not selected, the handover
priority optimization for inter-frequency neighboring cells sent to the SRNC is
disabled. The SRNC considers that the coverage-based handover priority of these
inter-frequency neighboring cells in the received information is 2.
• If PERFENH_DRNC_INTER_FREQ_NCELL_OPT_SWITCH under the
PerfEnhanceSwitch10 (BSC6900, BSC6910) parameter is selected, the handover
priority optimization for inter-frequency neighboring cells sent to the SRNC is
enabled. When the DRNC sends the SRNC information about inter-frequency
neighboring cells, the cells are sequenced in descending order based on the priority
specified by HOCovPrio (BSC6900, BSC6910), and cells with HOCovPrio (BSC6900,
BSC6910) set to 0 are excluded.
The handover priority optimization for inter-frequency neighboring cells sent to the SRNC has
the following impact on other features:
• WRFD-020302 Inter Frequency Hard Handover Based on Coverage and WRFD-
020304 Inter Frequency Hard Handover Based on DL QoS
After this function is enabled, the target neighboring cell selection becomes more
accurate during the coverage- or QoS-based inter-frequency handover.
• WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load
Threshold and WRFD-021200 HCS (Hierarchical Cell Structure)
After this function is enabled, the number of inter-frequency neighboring cells sent by
the DRNC to the SRNC decreases, possibly causing the activation times of the two
features to decrease.
Intra-Frequency Handover Decision and Execution Triggered by Event 1A that Serves as a

Substitute for Event 1C
With the function of substituting intra-frequency handover decision and execution triggered by
event 1A for that triggered by event 1C enabled, the RNC initiates replacement of cells in the
active set if the number of cells in the active set has reached the upper limit. This function is
controlled by HO_MC_INTRAFREQ_1A_REPLACE_1C_SWITCH under the HoSwitch1
(BSC6900, BSC6910) parameter. If this option is selected, the function is enabled. If this option is
not selected, the function is disabled.
The RNC initiates replacement of cells in the active set (same as replacement of cells in the
active set triggered by event 1C) if the function is enabled and the following inequality is true:
MNew > MInAS + H1c/2
• MNew is the measurement value of the best cell in an event 1A report.
• MInAS is the measurement value of the worst cell in an event 1A report.
• H1c is the hysteresis (decibel/dB) for event 1C, which is determined by the Hystfor1C
(BSC6900, BSC6910) parameter.
It is recommended that the function of substituting intra-frequency handover decision and
execution triggered by event 1A for that triggered by event 1C be enabled when the following
conditions are met:
The number of event 1C reports occupies more than 25% of the total number of event 1A, 1B,
and 1C reports, as indicated by the following inequality: VS.RRC.MrRpt.1C (BSC6900,
BSC6910)/(VS.RRC.MrRpt.1A (BSC6900, BSC6910) + VS.RRC.MrRpt.1B (BSC6900, BSC6910) +
VS.RRC.MrRpt.1C (BSC6900, BSC6910)) > 25%
This function is successfully enabled if the number of event 1A reports increases whereas the
number of event 1C reports decreases to 0.
If this function is enabled when the preceding conditions are met, the soft handover success rate
has an increase of 0% to 5% and has an even greater increase in top N cells where the preceding
problems are worse.
3.6 Follow-up Procedures for Soft Handover Failures
3.6.1 Overview
If a soft handover fails, the RNC performs the procedures listed in Table 3-18 according to the
service type.
Table 3-18 Follow-up procedures for soft handover failures
Service Type Procedure
R99 non-real-time (NRT) services in the The RNC reduces the service rate. If service
uplink and downlink rate reduction fails, the RNC initiates a state
transition from Cell_DCH to Cell_FACH (D2F).
R99 NRT services in the uplink The RNC initiates a D2F state transition.
HSUPA NRT services The RNC initiates a reconfiguration from E-

DCH to DCH (E2D).
The three procedures are detailed as follows:

• Rate reduction: For a UE processing R99 NRT services in uplink and downlink, if the
RNC fails to set up a radio link for the UE during the admission phase of a soft
handover, the RNC reduces the service rate of the UE and then sets up a radio link
again, increasing the soft handover success rate. For details, see 3.6.2 Rate Reduction After
a Soft Handover Failure.
• D2F state transition: If the RNC fails to set up a radio link for a UE during a soft
handover, the RNC triggers a D2F state transition for the UE in the best cell when the
target cell's signal quality is greater than the best cell's signal quality plus a preset
threshold value. This mitigates the interference to the target cell caused by UEs
processing R99 NRT services in the uplink. For details, see 3.6.3 D2F State Transition After
a Soft Handover Failure.
• E2D reconfiguration: If the RNC fails to set up a radio link for an HSUPA UE during
a soft handover or the target cell does not support E2D reconfiguration for HSUPA
UEs, the RNC triggers the E2D reconfiguration procedure for the HSUPA UE. This
mitigates the interference to the target cell caused by UEs processing HSUPA NRT
services in the uplink. For details, see 3.6.4 E2D Reconfiguration After a Soft Handover Failure.
The follow-up procedures for soft handover failures reduce the possibility of received total wideband power
(RTWP) or channel element (CE) congestion in a cell but increase the number of RB reconfigurations and the call
drop rate.
3.6.2 Rate Reduction After a Soft Handover Failure
If the radio link fails to be added for a soft handover, the rate reduction is triggered for R99 NRT
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, as shown in Figure 3-16.
Figure 3-16 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 as follows: Mnew > Mbest_cell –
RelThdForDwnGrd (BSC6900, BSC6910)
where
• Mnew is the CPICH Ec/N0 measurement value of the cell failing to be
admitted.
• Mbest_cell is the CPICH Ec/N0 measurement value of the best cell in the
active set.
2. ShoFailNumForDwnGrd (BSC6900, BSC6910) specifies the threshold for the
number of soft handover failures in a cell.
3. The soft handover failure counter of a cell is used to record the number of soft
handover failures in this cell. For each UE, the RNC records the number of soft
handover failures occurred in first three cells at most. For soft handover failures in
any other cells, the RNC does not record the number.
The ShoFailPeriod (BSC6900, BSC6910) parameter specifies a timer for rate
reduction after a soft handover failure.
Procedure of Rate Reduction Execution
Figure 3-17 shows the rate reduction process.

Figure 3-17 Procedure of rate reduction execution
1. The RNC performs a rate reduction process for the access service.
To determine the access rate after rate reduction, see sections related to WRFD-
010507 Rate Negotiation at Admission Control in Intelligent Access Control Feature
Parameter Description.
If rate reduction fails, the RNC sets the soft handover failure counter of the cell to 0
and terminates the rate reduction process.
2. If rate reduction succeeds, the RNC makes an admission decision for the UE.
• If UE admission to a cell succeeds, the RNC adds this cell to the active set
without measurement and adds the radio link for the UE.
• If UE admission fails, the RNC starts the penalty timer specified by the
DcccShoPenaltyTime (BSC6900, BSC6910) to avoid a rate increase
triggered by DCCC within the period. When the penalty timer expires, the
RNC sets the soft handover failure counter of the cell to 0 and terminates
the rate reduction process.
If the RNC fails to perform a soft handover again, it performs the estimation and execution
procedures, as previously described in this section.
3.6.3 D2F State Transition After a Soft Handover Failure
When SoftFailD2FSwitch (BSC6900, BSC6910) is set to ON, the RNC triggers a D2F state
transition in the best cell for a UE processing R99 NRT services in the uplink (R99 or HSDPA
NRT services in the downlink) if the UE experiences a soft handover failure and the following
inequality is true:
Target cell's Ec/N0 > Best cell's Ec/N0 + SoftFailD2FOffset (BSC6900, BSC6910)
If the D2F state transition succeeds, the RNC starts a penalty timer for state transitions from
Cell_FACH to Cell_DCH (F2D) upon the soft handover failures and applies the following
restrictions:
• Forbids all F2D transitions except for those triggered by CS service requests until the
penalty timer expires.
• Stops the penalty timer if the cell update procedure is triggered before the timer
expiry.
3.6.4 E2D Reconfiguration After a Soft Handover Failure
If the RNC fails to set up a radio link for a UE processing HSUPA NRT services in the uplink
during a soft handover, or the target cell does not support E2D reconfiguration for HSUPA UEs,
the RNC triggers the E2D reconfiguration procedure for the UE. This reduces the uplink
interference to the target cell caused by the UE.
If SoftFailE2DSwitch (BSC6900, BSC6910) is set to ON, the RNC triggers the E2D
reconfiguration. If the independent active set function is enabled, a DC-HSUPA UE will fall
back to the DCH when it fails to access any link on the primary carrier. If the admission of a link
on the secondary carrier fails, the UE remains on the DC-HSUPA carriers. For details about the
independent active set function, see DC-HSUPA Feature Parameter Description. If the independent
active set function is disabled, the DC-HSUPA will fall back to the DCH.
If the E2D reconfiguration succeeds, the RNC starts a penalty timer of 20s and applies the
following restrictions on the UE before the timer expires:
• Forbids periodic DRDs based on blind handovers or measurements.
For details about periodic DRD, see Directed Retry Decision Feature Parameter Description.
• Forbids D2E reconfiguration triggered by dynamic channel configuration control
(DCCC).
• Forbids D2E state transitions if the target cell does not support HSUPA.
The RNC does not trigger E2D reconfiguration for the UE if the soft handover fails due to a downlink admission
failure. This is because the uplink resources of the target cell are not congested if only a downlink admission failure
occurs.
3.7 Other Functions
3.7.1 Addition of Detected Set Cells to the Active Set

A detected set cell is not in a UE's neighboring cell list, which is contained in the measurement
control message. However, according to section 10.3.7.39 "Intra-frequency measurement
reporting criteria" in 3GPP TS 25.331 V10.0.0, like a monitored set cell, a detected set cell
(excluding blacklisted neighboring cells of the best cell) can also be contained in an intra-
frequency measurement report triggered by a 1X (1A, 1C, and 1D) event.
For blacklisted neighboring cells, BLACKLIST_FLAG under the NCellCapContainer (BSC6900, BSC6910)
parameter is selected.
Whether a detected set cell can be contained in a measurement report triggered by a 1X event is
controlled by HO_INTRA_FREQ_DETSET_RPRT_SWITCH under the HOSWITCH
(BSC6900, BSC6910) parameter in the RNC MML command SET UCORRMALGOSWITCH.
• If this option is selected, the UE reports information about both monitored set cells
and detected set cells. The detected set cells can be added to the active set only when
HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH under the HoSwitch
(BSC6900, BSC6910) parameter is selected. For details, see Procedure Optimization Feature
• If this option is not selected, the UE reports information about monitored set cells
only.
3.7.2 Uplink Active Set Expansion
3.7.2.1 Overview
The scope of the soft handover area affects soft handover overheads, especially downlink
overheads. Expanding the soft handover area increases downlink resource consumption
(reducing the power and code usage), raises downlink interference to neighboring cells, and
affects the downlink capacity.
According to the current handover policy, handovers are triggered by events 1A and 1B, which
occur when the downlink measurement results meet specific conditions. This policy
comprehensively considers the uplink and downlink resource consumption, power efficiency,
and contiguous coverage. However, the uplink soft handover area may be too small because the
uplink measurement results are not taken into account in the handover decision. As a result, the
area where link combination gains are available and cell-edge UEs can obtain gains through
handovers is decreased.
Therefore, the uplink active set expansion function is introduced to expand the soft handover
area. As shown in Figure 3-18, area C is the expanded area for the uplink active set.
Figure 3-18 Expanded area for the uplink active set
Area A: soft handover area, which is the overlapping area of two sectors belonging to different
NodeBs. When located in this area, the UE can establish uplink and downlink channels with both
NodeBs.
Area B: center of a sector belonging to a NodeB. When located in this area, the UE can establish
uplink and downlink channels only with this NodeB.
Area C: expanded area of the uplink active set, which is also the overlapping area of two sectors
belonging to different NodeBs. The UE has not reached the soft handover area when located in
this area, but the RNC has established an uplink coordinating link between the UE and the non-
serving NodeB.
This feature has the following advantages:
• Only an uplink coordinating link is established, which does not affect the downlink.
• Without this feature, signals sent by UEs at the cell edge cause interference to UEs in
neighboring cells. These signals can now be used for uplink combination as well as
interference cancellation, which is used to suppress interference caused to neighboring
cells.
3.7.2.2 Link Management
The Uplink Active Set Expansion feature consists of the following functions, which are
implemented by the RNC, NodeB, and UE:
• Management of event 1A for uplink active set expansion
An event 1A measurement control message is added on the RNC side and delivered to
the UE.
When the CPICH signal quality difference between a cell in the UE's monitored set
and the best cell in the UE's active set meets the threshold for adding uplink
coordinating links, the UE reports event 1A for uplink active set expansion, as
illustrated by the following formula:
10 x Log(MNew) + CIONew ≥ W x 10 x Log( ) + (1 – W) x 10 x Log(MBest) –

(R1aPre – H1aPre/2)
▪ The decision process of event 1A for uplink active set expansion is the same as the decision
process of event 1A. For details, see 3.4.3 Triggering of Event 1A.
▪ Most parameters related to event 1A for uplink active set expansion are the same as those
related to event 1A, which are stated in 3.4.3 Triggering of Event 1A.
R1aPre refers to the relative threshold of event 1A for uplink active set expansion. It is
specified by the cell-level parameter IntraRelThldFor1APre (BSC6900, BSC6910) or
RNC-level parameter IntraRelThldFor1APre (BSC6900, BSC6910). If both RNC-
level and cell-level parameters are configured, the cell-level parameter settings
prevail.
H1aPre is the hysteresis, which is specified by the HystFor1APre (BSC6900, BSC6910)
parameter.
Figure 3-19 shows the process of triggering an event 1A for uplink active set expansion.
Figure 3-19 Process of triggering an event 1A for uplink active set expansion
Th1APre in Figure 3-19 is calculated as follows: Th1APre = (Ec/N0 of the CPICH of the
best cell in the active set) – (Relative threshold of event 1A for uplink active set
expansion – Hysteresis of event 1A for uplink active set expansion/2).
The hysteresis of event 1A for uplink active set expansion is specified by the
HystFor1APre (BSC6900, BSC6910) parameter.
If the signal quality of the target cell keeps better than Th1APra for a duration specified
by TrigTime1APre (BSC6900, BSC6910), the UE reports event 1A for uplink active
set expansion.
After receiving event 1A for uplink active set expansion from the UE, the RNC
establishes an uplink coordinating link for the UE. Without knowing the link, the UE
periodically reports event 1A for uplink active set expansion.
The interval of UEs reporting event 1A for uplink active set expansion is specified by
the cell-level parameter ReportIntervalfor1APre (BSC6900, BSC6910) or RNC-level
parameter ReportIntervalfor1APre (BSC6900, BSC6910).
The maximum number of times that the event is reported is specified by the cell-level
parameter PeriodMRReportNumfor1APre (BSC6900, BSC6910) or RNC-level
parameter PeriodMRReportNumfor1APre (BSC6900, BSC6910). When the number
of times that the event is reported reaches the specified threshold, the reporting ends.
If both RNC-level and cell-level parameters are configured, the cell-level parameter settings prevail.
• Addition of uplink coordinating links

The RNC parses the measurement report sent by the UE. If the measurement report is
about event 1A for uplink active set expansion, the RNC sends a radio link setup or
addition request message to the NodeB.
After receiving this message, the NodeB sets up only an uplink coordinating link
rather than a downlink coordinating link if the radio link requested to be set up is an
uplink coordinating link.
• Removal of uplink coordinating links
After setting up an uplink coordinating link for the UE, the NodeB measures the
uplink quality of the coordinating link in real time and determines whether the link is
synchronized. If link synchronization fails, the NodeB instructs the RNC to remove
the uplink coordinating link.
When the UE moves to the edge of the soft handover area and reports event 1A to add
a non-serving link, the RNC first removes the uplink coordinating link of the
corresponding cell and then sets up a non-serving link for soft handovers.
3.7.2.3 Admission Procedure
Uplink coordinating link admission consumes uplink credit resources and NodeB application
part (NBAP) resources. The RNC admits uplink coordinating links when there are idle resources
and stops uplink coordinating link admission when these resources are insufficient to ensure the
admission of common users.
shows detailed uplink credit admission procedures for uplink coordinating links. The
Figure 3-20
RNC admits an uplink coordinating link only when uplink credit resources are sufficient.
Figure 3-20 Uplink credit admission procedures for uplink coordinating links
• Predict the uplink credit resource usage before activating this function for a site. You are advised to
activate this function when the uplink credit resources are sufficient (credit usage lower than 65%).
• After Uplink Active Set Expansion is enabled, the uplink credit resources consumed by uplink
coordinating links are separately calculated. That is, original RNC counters do not measure the uplink
credit resource usage of uplink coordinating links. For details about the counters, see 3.7.2.5
Performance Monitoring.
During NBAP resource admission for uplink coordinating links, the NodeB monitors real-time
NBAP load. When the NBAP load is heavy, the NodeB instructs the RNC to stop uplink
coordinating link admission.
Predict the current NBAP load of a site before function activation. You are advised to activate this function when
the average CNBAP usage of the NodeB is lower than 65%. The current CNBAP usage of the NodeB is indicated by
the VS.BTS.CnbapCap.UseRate counter.
After the admission of an uplink coordinating link succeeds, it is possible that a large number of
real radio links are set up in a short period of time and the uplink credit and NBAP resources
occupied by the uplink coordinating link cannot be released in time. To ensure the real radio link
setup of common users, resources of the uplink coordinating links can be preempted.
DC-HSUPA users do not support setup of uplink coordinating links and therefore do not support preemption of
uplink coordinating links.
An uplink coordinating link complies with the following CE consumption rules:

• When the Seamless Crystal Voice and Improved Uplink Coverage for SRB over DCH
features are enabled, an uplink coordinating link consumes CEs according to the
actually used spreading factors (SFs).
• When the Control Channel Parallel Interference Cancellation (Phase 2) feature is
enabled:
▪ If the WBBPb, WBBPd, or WBBPf board is used, an uplink coordinating
link consumes one CE in the single- or dual-antenna scenario and two CEs
in the four-antenna scenario.
▪ If the UBBP board is used, an uplink coordinating link consumes one CE in
the single-, dual-, or four-antenna scenario.
• When the Softer Handover feature is enabled:
▪ If the WBBPb, WBBPd, or WBBPf board is used, an uplink coordinating
link consumes one CE in the single- or dual-antenna scenario and two CEs
in the four-antenna scenario.
▪ If the UBBP board is used, an uplink coordinating link consumes one CE in
the single-, dual-, or four-antenna scenario.
For mapping between the SF and the CE consumption, see CE Resource Management Feature Parameter
Description.
3.7.2.4 Application Scenarios
This feature can be used together with some other features when the corresponding switches are
turned on:
• When CCPIC_PHASE2_COORDINATING_RL_SWITCH under the
UplinkActiveSetEXP (BSC6900, BSC6910) parameter is selected and the WRFD-
140202 Control Channel Parallel Interference Cancellation (Phase 2) feature is
enabled, DPCCH interference cancellation can be performed on the uplink
coordinating links that are set up by the Uplink Active Set Expansion feature, reducing
interference to neighboring cells and improving the uplink capacity. For details about
the Control Channel Parallel Interference Cancellation (Phase 2) feature, see Control
Channel Interference Cancellation Feature Parameter Description .
• When SMLESSCRSTVOICE_COORDINATING_RL_SWITCH under the

170201 Seamless Crystal Voice feature is enabled, the WRFD-170201 Seamless
Crystal Voice feature is supported in the expanded area for the uplink active set. For
details about the Seamless Crystal Voice feature, see Seamless Crystal Voice Feature
• When IMPRV_ULCOV_SRBOD_COORDINATING_RL_SWITCH under the

180201 Improved Uplink Coverage for SRB over DCH feature is enabled, the
Improved Uplink Coverage for SRB over DCH feature is supported in the expanded
area for the uplink active set. For details about the Improved Uplink Coverage for
SRB over DCH feature, see Improved Uplink Coverage for SRB over DCH Feature Parameter
Description.
3.7.2.5 Performance Monitoring
The coordinating link management process can be monitored using the following counters on the
RNC.
Counter Name Counter Description
VS.RRC.MrRpt.UplinkActiveSetEXP.1A Number of UL Active Set Extension Event 1A'

(BSC6900, BSC6910) Measurement Reports for Cell
VS.IUB.CoordinatingRL.AttSetup (BSC6900, Number of UL Coordinating Link Setup

BSC6910) Requests over the Iub Interface for Cell
VS.IUB.CoordinatingRL.SuccSetup Number of Successful UL Coordinating Link

(BSC6900, BSC6910) Setups over the Iub Interface for Cell
VS.IUB.CoordinatingRL.SetupFailNoRestore Number of UL Coordinating Link Setup

(BSC6900, BSC6910) Failures over the Iub Interface for Cell
(Synchronization Failure)
VS.IUB.CoordinatingRL.AttAdd (BSC6900, Number of UL Coordinating Link Addition

VS.IUB.CoordinatingRL.SuccAdd (BSC6900, Number of UL Coordinating Links

BSC6910) Successfully Added over the Iub Interface for
Cell
VS.IUB.CoordinatingRL.FailInd (BSC6900, Number of UL Coordinating Link Failures over

BSC6910) the Iub Interface for Cell
VS.IUB.CoordinatingRL.FailInd.SyncFail Number of UL Coordinating Link

(BSC6900, BSC6910) Synchronization Failures over the Iub
Interface for Cell
VS.IUB.CoordinatingRL.AttDel (BSC6900, Number of UL Coordinating Link Deletion

VS.IUB.CoordinatingRL.AttRecfg (BSC6900, Number of UL Coordinating Link

BSC6910) Reconfiguration Attempts over the Iub
Interface for Cell
VS.IUB.CoordinatingRL.SuccRecfg Number of UL Coordinating Links

(BSC6900, BSC6910) Successfully Reconfigured During
Synchronization over the Iub Interface for Cell
The number of uplink coordinating links and credit consumption for admission of the uplink
coordinating links can be monitored using the following counters on the RNC.
VS.CoordinatingRL.Mean (BSC6900, BSC6910) Average Number of Uplink

Coordinating RLs for Cell
VS.CoordinatingRL.Max (BSC6900, BSC6910) Maximum Number of Uplink

Coordinating RLs for Cell
VS.LCG.CoordinatingRL.ULCreditUsage.Mean Average Credit Usage of Uplink

(BSC6900, BSC6910) Coordinating RLs in LCG for Cell
VS.LCG.CoordinatingRL.ULCreditUsage.Max Maximum Credit Usage of Uplink

(BSC6900, BSC6910) Coordinating RLs in LCG for Cell
VS.NodeB.CoordinatingRL.ULCreditUsed.Max.PLMN Maximum NodeB Credit Resources

(BSC6900, BSC6910) Consumed by Uplink Coordinating
RLs of an Operator
VS.NodeB.CoordinatingRL.ULCreditUsed.Mean.PLMN Average NodeB Credit Resources

RLs of an Operator
VS.NodeB.CoordinatingRL.ULCreditUsed.Mean Average NodeB Credit Resources

RLs
VS.NodeB.CoordinatingRL.ULCreditUsed.Max Maximum NodeB Credit Resources

RLs
The consumption of uplink coordinating links can be monitored using the following counters on
the NodeB.
VS.CoordinatingRL.Handle.Max Maximum number of received uplink

coordinating links per second
VS.CoordinatingRL.Handle.Mean Average number of received uplink

coordinating links per second
After the Uplink Active Set Expansion feature is enabled, the CPU usage of the BSC6900 or
BSC6910 will increase by less than 10%, which can be monitored by the following counters.
Counter Name Counter Description NE
VS.XPU.CPULOAD.Mean AR9780: Average CPU Usage of the BSC6900

XPU
VS.SUBSYS.CPULOAD.Mean AR9725: Average Subsystem CPU BSC6910
Usage of the Board
This feature is not recommended when the CPU usage is relatively high. In order not to affect the paging function,
traffic control is performed on the uplink coordinating links only when the following condition is met: CPU usage >
Min (SMS paging recover threshold, SS and LCS paging recover threshold, Call-type paging control threshold) – 5.
The preceding thresholds can be queried by running the RNC MML command LST FCCPUTHD.
After the Uplink Active Set Expansion function is enabled, setup of uplink coordinating links
will consume some traffic resources of the RNC interface board. The increase in the traffic
resource consumption of the RNC interface board depends on the increase in the proportion of
uplink coordinating links. The increase in the traffic resource consumption of the RNC interface
board before and after the Uplink Active Set Expansion function can be obtained through the
following counters.
VS.INT.TRM.FLOW.UDP.MAX (BSC6900, Maximum Number of Occupied UDP Ports of

BSC6910) Interface Boards
VS.INT.TRM.FLOW.UDP.MEAN (BSC6900, Average Number of Occupied UDP Ports of

VS.INT.TRM.FLOW.CID.MAX (BSC6900, Maximum Number of Occupied CIDs of

VS.INT.TRM.FLOW.CID.MEAN (BSC6900, Average Number of Occupied CIDs of

4 Inter-Frequency and Inter-RAT Handovers
4.1 Overview
General Process
The inter-frequency and inter-RAT handover involves four phases: measurement triggering,
handover measurement, handover decision, and handover execution. After a UE in a call enters
the CELL_DCH state and measurement is triggered, the RNC sends the UE a measurement
control message. Upon receiving the message, the UE performs measurements as required and
reports measurement results to the RNC. The measurement control messages include the
following information:
• Measurement mode, threshold, and hysteresis
• Neighboring cell list
If the neighboring cell combination function is disabled, the list includes only
neighboring cells of the best cell. If the neighboring cell combination function is
enabled, refer to 7 Neighboring Cell Combination for included cells.
If the APFlag (BSC6900, BSC6910) parameter is set to TRUE for an inter-frequency neighboring cell under a
neighboring RNC, the inter-frequency neighboring cell will not be contained in the measurement control message.
Inter-frequency handovers fall into two categories: intra-band and inter-band inter-frequency
handovers. For these two types of handovers, the handover process is the same whereas the
dependent features are different.
• If an inter-band inter-frequency handover to UMTS 900 MHz is to be triggered, the
feature WRFD-020110 Multi Frequency Band Networking Management must be
enabled.
• If an intra-band inter-frequency handover is to be triggered, no feature is required.
Unless otherwise specified, the inter-RAT handover in this document refers to the handover
performed between GSM and UMTS networks. For details about the handover between UMTS
and LTE networks, see Interoperability Between UMTS and LTE Feature Parameter Description .
Inter-Frequency and Inter-RAT Handover Switches
The inter-frequency and inter-RAT handovers are switch-controlled by the parameters listed in
the following table.
Parameter ID Option Description
HOSWITCH HO_INTER_FREQ_HARD_HO_SWITCH Switch for inter-frequency

(BSC6900, handovers
BSC6910)
HO_INTER_RAT_PS_OUT_SWITCH Switch for inter-RAT PS
handovers
HO_INTER_RAT_CS_OUT_SWITCH Switch for inter-RAT CS

handovers
HO_MC_SIGNAL_SWITCH Time at which the signal

quality of cells in the active
set is measured (a)
HO_MC_MEAS_BEYOND_UE_CAP_SWITCH Whether the inter-

frequency measurement
control message carries a
neighboring cell, for which
the frequency is beyond
the UE's measurement
capability (b)
HHOTRIG - Switch for intra- or inter-

(BSC6900, frequency hard handovers
BSC6910) over the Iur interface
HoSwitch2 HO_INTER _FREQ_IUR_CTRL_SWITCH Whether the SRNC

(BSC6900, performs coverage-based
BSC6910) cross-Iur inter-frequency
handovers specific for a
downlink frequency
BlindHoFlag - Switch for inter-frequency

(BSC6900, blind handovers
BSC6910) Huawei devices do not
support inter-RNC inter-
frequency blind handovers.
BlindHoFlag - Switch for inter-RAT blind

(BSC6900, handovers
BSC6910) BlindHOPrio (BSC6900,
BSC6910) specifies the blind
handover priority of
neighboring cells. A smaller
value indicates a higher
priority.
HoSwitch2 HO_INTER_RAT_CS_SIGNAL_LIMIT_SWITCH Switch for inter-RAT

(BSC6900, handovers of UEs with
BSC6910)
Parameter ID Option Description
SRBs only and no RABs in

the CS domain (c)(d)
HoSwitch2 HO_INTER_RAT_PS_SIGNAL_LIMIT_SWITCH Switch for inter-RAT

(BSC6900, handovers of UEs with
BSC6910) SRBs only and no RABs in
the PS domain (d)
(a) For each switch:

• If the switch is turned on, the RNC initiates the active set quality measurement after the RRC
connection setup is completed (before the RB setup) or when the UE resides at the cell edge or emits
weak signals.
The RNC determines whether to allow handovers for UEs with single signaling connections based on
the situation of subsequent service establishment and setting of
PERFENH_HO_SIGNAL_SCENE_CTRL under the PerfEnhanceSwitch3 (BSC6900, BSC6910)
parameter in the SET UCORRMPARA command.
When PERFENH_HO_SIGNAL_SCENE_CTRL is selected, if a service is established after the RRC
connection is set up, the RNC allows handovers for UEs with single signaling connections; if no service
is established after the RRC connection is set up, the RNC prohibits handovers for UEs with single
signaling connections.
When PERFENH_HO_SIGNAL_SCENE_CTRL is deselected, the RNC always allows handovers
for UEs with single signaling connections.
• If the switch is turned off, the RNC initiates the active set quality measurement after the RB setup is
completed.
(b): Measurement quantity at some frequencies may not be reported due to the limitation of the version of UE
protocol. Therefore, the reported measurement capability of the UE is not the same as the actual measurement
quantity of the UE. The switch is used to specify whether the inter-frequency measurement control message sent by
the RNC carries the frequencies beyond the UE's reporting capability.
• ON: indicates that the inter-frequency measurement control message sent by the RNC carries the
frequencies beyond the UE's reporting capability.
• OFF: indicates that the inter-frequency measurement control message sent by the RNC does not carry
the frequencies beyond the UE's reporting capability.
• (c): This function does not control the inter-RAT handover for UEs with SRBs only and no RABs in the
CS domain for emergency calls. That is, even if this function is enabled, inter-RAT handovers for UEs
with SRBs only and no RABs in the CS domain are allowed for emergency calls.
(d): This function does not control the inter-RAT handover for UEs with SRBs only and no RABs
triggered by the DRD function. That is, even if this function is enabled, inter-RAT handovers triggered
by the DRD function are allowed for UEs with SRBs only and no RABs.
4.2 Signaling Procedures for Inter-Frequency and Inter-RAT Handovers
4.2.1 Signaling Procedures for Inter-Frequency Handover
4.2.1.1 Inter-Frequency Handover Within One RNC

shows the inter-frequency handover for a UE that moves from NodeB 1 to NodeB 2
Figure 4-1
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.
The signaling procedure of inter-frequency handover within one NodeB is similar to the
signaling procedure of the hard handover between NodeBs within one RNC.
Figure 4-1 Inter-frequency handover between NodeBs within one RNC
Figure 4-2 Signaling procedure for the inter-frequency handover between NodeBs within one RNC
4.2.1.2 Inter-Frequency Handover Between RNCs
shows the signaling procedure for inter-frequency hard handover for a UE that moves
Figure 4-3
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-3 Inter-frequency hard handover between RNCs
Figure 4-4 Signaling procedure for the inter-frequency hard handover between RNCs
4.2.2 Signaling Procedures for Inter-RAT Handover
4.2.2.1 UMTS-to-GSM Handover in the CS Domain
shows the signaling procedure for the UMTS-to-GSM handover in the CS domain. The
Figure 4-5
GSM messages shown in Figure 4-5 are for reference only.
Figure 4-5 UMTS-to-GSM handover in the CS domain
4.2.2.2 UMTS-to-GSM Handover in the PS Domain
If the serving GPRS support node (SGSN) changes as a UE in idle mode or connected mode
moves from a UMTS network to a GSM 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 UMTS-to-GSM 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 UMTS-to-GSM handover in the PS domain is triggered through the cell
reselection.
shows an example of handover for the UE in CELL_FACH, CELL_PCH, or
Figure 4-6
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 4-6.
Figure 4-6 Example of the UMTS-to-GSM handover in the PS domain
If a UE in either idle mode or connected mode performs a UMTS-to-GSM handover and the SGSN serving the UE
remains unchanged before and after the handover, all messages sent to different SGSNs in the preceding figure will
be sent to the same SGSN. In this case, signaling interaction procedures in steps 3, 5, 7, and 9 are not required.
4.2.2.3 UMTS-to-GSM Handover in Both CS and PS Domains
Inter-RAT Handover in Both CS and PS Domains
The difference of the signaling procedure for UMTS-to-GSM handover of CS+PS combined
services from that of a single CS or PS service is that the inter-RAT handover procedure is based
on the measurement reports from the UE but is initiated from the UTRAN for a UE in
CELL_DCH state using both CS and PS services.
1. 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.
2. 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 or not.
3. In case of an inter-RAT handover failure, the UE may go back to the UTRA RRC
Connected mode and re-establish the RRC 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. Figure 4-7 and Figure 4-8 show the
resume procedures.
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 4-7 Intra-SGSN service suspended and resumed
Figure 4-8 Inter-SGSN service suspended and resumed
4.2.2.4 GSM-to-UMTS Handover in the 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 then decides whether to start the
inter-RAT handover according to the measurement result. To allow GSM-to-UMTS handovers in
the CS domain, select SYSHO_CSIN_PERMIT_SWITCH under the RsvdPara1 (BSC6900,
BSC6910) parameter in the SET URRCTRLSWITCH command.
shows the signaling procedure of GSM-to-UMTS handovers in the CS domain. The
Figure 4-9
GSM system uses time division multiple access (TDMA), and the inter-RAT measurement is
performed in idle timeslots. Therefore, the GSM does not need to support the compressed mode.
Figure 4-9 GSM-to-UMTS handover in the CS domain
4.2.2.5 GSM-to-UMTS Handover in the PS Domain
Figure 4-10 shows the GSM-to-UMTS handover in the PS domain.

Figure 4-10 GSM-to-UMTS handover in the PS domain
4.3 Coverage- and QoS-based Handover
This section describes the coverage- and QoS-based UMTS-to-GSM handovers. The procedures
for these two handovers are the same except for the triggering cause.
4.3.1 Procedure
Figure 4-11 shows the procedure for the coverage- or QoS-based handover.
Figure 4-11 Coverage- or QoS-based handover procedure
4.3.2 Triggering
QoS-based Handover
If the service quality of the current cell deteriorates, the link stability control algorithm decides
whether to trigger a QoS-based handover. If a QoS-based handover is required, the RNC initiates
a QoS-based handover.
For details about the triggering conditions of QoS-based handovers for CS services, see
descriptions about AMRC based on link stability in AMR Feature Parameter Description. For details
about the triggering conditions of QoS-based handovers for PS BE services, see descriptions
about link stability control for BE services in DCCC Feature Parameter Description.
Coverage-based Handover
The coverage-based handover is triggered by event 2D. That is, event 2D is reported if the
estimated quality of the currently used frequency is below a certain threshold. After receiving
event 2D, the RNC decides to trigger a handover.
The signal quality measurement used for event 2D is specified by InterRATHO2DEventType
(BSC6900, BSC6910) or InterFreqHO2DEventType (BSC6900, BSC6910) and can be CPICH
Ec/N0 or CPICH RSCP. A UE reports event 2D measurement results if the following inequality
is true and lasts for a period of time specified by Event 2D Trigger Delay:
QUsed ≤ TUsed2d – H2d/2
Table 4-1 describes variables involved in triggering of event 2D.
Table 4-1 Variables involved in triggering of event 2D
Event 2D Trigger Time delay to trigger event 2D TimeToTrig2D (BSC6900, BSC6910)

Delay (for inter-frequency handovers)
TrigTime2D (BSC6900, BSC6910) (for
inter-RAT handovers)
QUsed Measured quality of the used N/A

frequency
TUsed2d Absolute quality threshold of the cell It is specified by the event 2D

that uses the current frequency threshold. For details, see Table 4-2.
H2d Event 2D hysteresis, used to prevent HystFor2D (BSC6900, BSC6910) (for

ping-pong triggering of event 2D. inter-frequency handovers)
Hystfor2D (BSC6900, BSC6910) (for
inter-RAT handovers)
Table 4-2 Parameters related to the event 2D threshold
Scenario Measurement Quantity Service Type Parameter
Inter- Ec/N0 R99 CS service InterFreqCSThd2DEcN0 (BSC6900,

frequency BSC6910)
handover
R99 PS service InterFreqR99PsThd2DEcN0
(BSC6900, BSC6910)
Scenario Measurement Quantity Service Type Parameter
HSPA service InterFreqHThd2DEcN0 (BSC6900,

BSC6910)
RSCP R99 CS service InterFreqCSThd2DRSCP (BSC6900,

BSC6910)
R99 PS service InterFreqR99PsThd2DRSCP

(BSC6900, BSC6910)
HSPA service InterFreqHThd2DRSCP (BSC6900,

BSC6910)
Inter-RAT Ec/N0 R99 CS service InterRATCSThd2DEcN0 (BSC6900,

handover BSC6910)
R99 PS service InterRATR99PsThd2DEcN0

(BSC6900, BSC6910)
HSPA service InterRATHThd2DEcN0 (BSC6900,

BSC6910)
RSCP R99 CS service InterRATCSThd2DRSCP (BSC6900,

BSC6910)
R99 PS service InterRATR99PsThd2DRSCP

(BSC6900, BSC6910)
HSPA service InterRATHThd2DRSCP (BSC6900,

BSC6910)
The principles for using event 2D-related parameters in hybrid networking scenarios are as
follows:
• When neighboring LTE and GSM cells are configured, event 2D-related parameters
configured for inter-RAT handover are used.
• When neighboring LTE cells and inter-frequency neighboring UMTS cells are
configured, event 2D-related parameters configured for inter-frequency handover are
used.
• When neighboring LTE cells, neighboring GSM cells, and inter-frequency
neighboring UMTS cells are configured, or when neighboring GSM cells and inter-
frequency neighboring UMTS cells are configured, the event 2D-related parameters to
be used depend on the setting of the CoexistMeasThdChoice parameter.
▪ If CoexistMeasThdChoice is set to
COEXIST_MEAS_THD_CHOICE_INTERFREQ, event 2D-related
parameters configured for inter-frequency handovers are used.
▪ If CoexistMeasThdChoice is set to
COEXIST_MEAS_THD_CHOICE_INTERRAT, event 2D-related
parameters configured for inter-RAT handovers are used.
The CoexistMeasThdChoice parameter is either an RNC-level parameter or a cell-level parameter. The RNC-level
CoexistMeasThdChoice parameter is set by running the SET UHOCOMM command. The cell-level
CoexistMeasThdChoice parameter is set by running the ADD UCELLHOCOMM command. If the cell-level
CoexistMeasThdChoice parameter has been set, the setting of the RNC-level CoexistMeasThdChoice parameter
does not take effect.
For the PS and CS combined services, when

HO_MULTIRAB_CSPS_HO_COV_PARA_SWITCH under the HoSwitch (BSC6900,
BSC6910) parameter in the SET UCORRMALGOSWITCH command is selected, the threshold
for triggering event 2D (TUsed2d) is specified by CSPSMRABThd2DEcN0 (BSC6900, BSC6910)
or CSPSMRABThd2DRSCP (BSC6900, BSC6910). Otherwise, the high threshold for CS and PS
services is used for the inter-frequency handover parameter, and the CS service threshold is used
for the inter-RAT handover parameter.
If the UE only has signaling connections, the threshold for triggering event 2D for CS services is used.
4.3.3 Measurement
The coverage- or QoS-based handover measurement starts after the compressed mode is
completed. For details about the compressed mode, see 4.11.2 Compressed Mode.
4.3.3.1 Starting Handover Measurement
Measurement Report Modes
The coverage- and QoS-based handovers use the event-triggered or periodic measurement report
mode.
• InterFreqReportMode (BSC6900, BSC6910) specifies the measurement report mode
of inter-frequency handovers.
• InterRatReportMode (BSC6900, BSC6910) specifies the measurement report mode of
inter-RAT handovers.
• PrdReportInterval (BSC6900, BSC6910) specifies the periodic measurement report
interval of inter-frequency handovers.
• InterRATPeriodReportInterval (BSC6900, BSC6910) specifies the periodic
measurement report interval of inter-RAT handovers.
The advantage of periodic measurement report is that if the handover fails, the RNC reattempts
the handover to the same cell after receiving the periodic measurement report from the UE. This
increases the probability of successful inter-frequency handovers.
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 a handover.
Measurement Quantity and Measurement Event
The coverage- and QoS-based handovers use the event-triggered or periodic measurement report
mode. In periodic measurement report mode, the CPICH Ec/N0 and CPICH RSCP can be used
as the measurement quantities. Table 4-3 lists the measurement events and measurement quantities
used in event-triggered mode.
Table 4-3 Measurement quantities and events used in coverage- and QoS-based handovers
Handover Triggering Measurement Measurement Quantity Description

Type Cause Event
Inter- Coverage 2B CPICH Ec/N0 and CPICH RSCP The estimated

frequency and QoS quality of the
handover currently used
frequency is below a
certain threshold and
the estimated quality
of a non-used
frequency is above a
certain threshold.
Inter-RAT Coverage 3A MeasQuantityOf3A (BSC6900, The estimated

handover BSC6910) (for UMTS cells) quality of the
RSSI (for GSM cells) currently used
UTRAN frequency is
QoS 3A UsedFreqMeasQuantityForQos3A below a certain
(BSC6900, BSC6910) (for UMTS cells) threshold and the
RSSI (for GSM cells) estimated quality of
the other system is
above a certain
threshold.
Triggering of Event 2B for Inter-Frequency Handovers
A UE reports event 2B measurement results if both the following inequalities are true and last for
a period of time specified by Event 2B Trigger Delay:
QNoused ≥ TNoused2b + H2b/2
QUsed ≤ TUsed2b – H2b/2
Table 4-4 describes variables involved in triggering of event 2B.
Table 4-4 Variables involved in triggering of event 2B
Event 2B Time delay to trigger event 2B TimeToTrig2B (BSC6900, BSC6910)

Trigger Delay
QNoused Measured quality of the non- N/A

used frequency
QUsed Measured quality of the used N/A

frequency
TNoused2b Quality threshold of the cells Parameters used for setting the service type
that use the target frequencies and measurement quantity
• TargetFreqCsThdEcN0 (BSC6900,
BSC6910)
• TargetFreqCsThdRscp (BSC6900,
BSC6910)
• TargetFreqR99PsThdEcN0
(BSC6900, BSC6910)
• TargetFreqR99PsThdRscp
(BSC6900, BSC6910)
• TargetFreqHThdEcN0 (BSC6900,
BSC6910)
• TargetFreqHThdRscp (BSC6900,
BSC6910)
TUsed2b Absolute quality threshold of Table 4-5describes TUsed2b configuration

the cell that uses the current details based on the measurement
frequency quantities used for events 2D and 2B.
H2b Event 2B hysteresis HystFor2B (BSC6900, BSC6910)
Table 4-5 TUsed2b configuration
Measurement Measurement Value of TUsed2b

Quantity Used for Quantity Used for
Event 2D Event 2B
RSCP RSCP UsedFreqCSThdRSCP (BSC6900, BSC6910)

UsedFreqR99PsThdRSCP (BSC6900, BSC6910)
UsedFreqHThdRSCP (BSC6900, BSC6910)
Ec/N0 Fixed at 0 dB(a)
Ec/N0 RSCP Fixed at -25 dBm(b)
Ec/N0 UsedFreqCSThdEcN0 (BSC6900, BSC6910)

UsedFreqR99PsThdEcN0 (BSC6900, BSC6910)
UsedFreqHThdEcN0 (BSC6900, BSC6910)
(a). As stipulated in section 10.3.7.39 "Intra-frequency measurement reporting criteria" of 3GPP TS 25.331 V10.0.0,
the maximum value of TUsed2b is 0 dB if the CPICH Ec/N0 is used as the measurement quantity. If the RNC receives
event 2F that uses CPICH Ec/N0 as the measurement quantity and TUsed2b is changed to a value other than 0 dB,
reset TUsed2b to 0 dB.
(b). As stipulated in section 10.3.7.39 "Intra-frequency measurement reporting criteria" of 3GPP TS 25.331 V10.0.0,
the maximum value of TUsed2b is -25 dBm if the CPICH RSCP is used as the measurement quantity. If the RNC
receives event 2F that uses CPICH Ec/N0 as the measurement quantity and TUsed2b is changed, reset TUsed2b to -25
dBm.
For CS+PS combined services, the configuration principles of event 2B-related parameters are
the same as those of event 2D-related parameters. For details, see Coverage-based Handover.
Triggering of Event 3A
This section describes triggering of event 3A used for UMTS-to-GSM handovers. For details
about triggering of event 3A used for UMTS-to-LTE handovers, see Interoperability Between UMTS
and LTE Feature Parameter Description.
A UE reports event 3A measurement results if both the following inequalities are true and last
for a period of time specified by 3A Event Trigger Delay Time:
• QUsed ≤ TUsed – H3a/2
• MOtherRAT + CIOOtherRAT ≥ TOtherRAT + H3a/2
Table 4-6 describes variables involved in triggering of event 3A.
Table 4-6 Variables involved in triggering of event 3A
3A Event Trigger Time delay to trigger event TrigTime3A (BSC6900, BSC6910)

Delay Time 3A
QUsed Measured quality of the N/A

used frequency
TUsed Absolute threshold for the Table 4-7 describes the TUsed configuration
signal quality of the serving details based on the triggering cause and
cell the measurement quantities used for
events 2D and 3A.
MOtherRAT Measurement value of the N/A

cell (in another RAT) in the
reporting range
CIOOtherRAT CIO of the cell (in another Sum of CIO (BSC6900, BSC6910) and
RAT) CIOOffset (BSC6900, BSC6910)
TOtherRAT Absolute inter-RAT It is set based on the service type.

handover threshold • TargetRatCsThd (BSC6900,
BSC6910)
• TargetRatR99PsThd (BSC6900,
BSC6910)
• TargetRatHThd (BSC6900,
BSC6910)
H3a Event 3A hysteresis Hystfor3A (BSC6900, BSC6910)
Table 4-7 TUsed configuration
Triggering Measurement Measurement Value of TUsed

Cause Quantity Used for Quantity Used for
Event 2D Event 3A
Coverage RSCP RSCP • UsedFreqCSThdRSCP

(BSC6900, BSC6910)
• UsedFreqHThdRSCP
(BSC6900, BSC6910)
• UsedFreqR99PsThdRSCP
(BSC6900, BSC6910)
Ec/N0 Fixed at 0 dB
Ec/N0 RSCP Fixed at -25 dBm
Ec/N0 • UsedFreqCSThdEcN0
(BSC6900, BSC6910)
• UsedFreqHThdEcN0 (BSC6900,
BSC6910)
• UsedFreqR99PsThdEcN0
(BSC6900, BSC6910)
Uplink QoS N/A RSCP Fixed at -25 dBm
N/A Ec/N0 Fixed at 0 dB
Downlink N/A RSCP It can be the sum of the either of the

QoS following parameter combination:
• UsedFreqCSThdRSCP
(BSC6900, BSC6910) and
DlRscpQosHyst (BSC6900,
BSC6910)
• UsedFreqR99PsThdRSCP
Triggering Measurement Measurement Value of TUsed
Cause Quantity Used for Quantity Used for
Event 2D Event 3A
BSC6910)
• UsedFreqHThdRSCP
BSC6910)
N/A Ec/N0 Fixed at 0 dB
For CS+PS combined services, the configuration principles of event 3A-related parameters are
the same as those of event 2D-related parameters. For details, see Coverage-based Handover.
Target Neighboring Cell Selection
The process of selecting the target neighboring cells for measurement is as follows:
Selecting target inter-frequency neighboring cells
• If the neighboring cell combination function is disabled, the RNC performs the
following operations:
1. From the neighboring cell list of the best cell, the RNC removes the
blacklisted neighboring cells, for which BLACKLIST_FLAG under the
NCellCapContainer (BSC6900, BSC6910) parameter is selected.
2. From the remaining neighboring cells of the best cell, the RNC selects up
to two frequencies where the neighboring cells operate as those to be
measured based on priorities (specified by the HOCovPrio (BSC6900,
BSC6910) parameter) of neighboring cells in a descending order. If two or
more neighboring cells have the same HOCovPrio (BSC6900, BSC6910)
setting, the RNC randomly selects two frequencies as the target ones for
measurements.
3. From the inter-frequency neighboring cells operating at the prioritized
target frequency, the RNC selects the target cells based on the priority
(specified by the Nprio (BSC6900, BSC6910) parameter) in descending
order. If two or more neighboring cells have the same Nprio (BSC6900,
BSC6910) setting, the RNC randomly selects up to 32 cells. If fewer than 32
neighboring cells are available, the RNC proceeds to 4.
4. From the inter-frequency neighboring cells operating at the second
prioritized target frequency, the RNC selects the target cells based on the
priority (specified by the Nprio (BSC6900, BSC6910) parameter) in
descending order. A total of 32 inter-frequency neighboring cells are
allowed. (If there are no more than 32 inter-frequency neighboring cells,
the RNC selects all neighboring cells.) If two or more neighboring cells
have the same Nprio (BSC6900, BSC6910) setting, the RNC randomly
selects the neighboring cells.
• If the neighboring cell combination function is enabled, the RNC selects neighboring
cells according to the rules described in 7 Neighboring Cell Combination.
Selecting target inter-RAT neighboring cells: If the neighboring cell combination function is
disabled, the RNC selects the target cells from the inter-RAT neighboring cells of the best cell
based on the priority (specified by the Nprio (BSC6900, BSC6910) parameter) in descending order.
If two or more neighboring cells have the same Nprio (BSC6900, BSC6910) setting, the RNC
randomly selects up to 32 cells. If the neighboring cell combination function is enabled, the RNC
selects neighboring cells according to the rules described in 7 Neighboring Cell Combination.
4.3.3.2 Stopping Handover Measurement
For the coverage-based handover, if the CPICH signal quality of the current cell resumes, the UE
reports event 2F to the RNC. Upon receiving event 2F, the RNC stops the compressed mode and
coverage-based handover. For the conditions for stopping QoS-based handovers for CS services,
see descriptions about AMRC based on link stability in AMR Feature Parameter Description. For the
conditions for stopping PS BE service handovers, see descriptions about link stability control for
BE services in DCCC Feature Parameter Description.
Triggering of Event 2F
A UE reports event 2F measurement results if the following inequality is true and lasts for a
period of time specified by 2F Event Trigger Delay Time:
QUsed ≥ TUsed2f + H2f/2
Table 4-8 describes variables involved in triggering of event 2F.
Table 4-8 Variables involved in triggering of event 2F
2F Event Time delay to trigger TimeToTrig2F (BSC6900, BSC6910) (for inter-frequency

Trigger Delay event 2F handovers)
Time TrigTime2F (BSC6900, BSC6910) (for inter-RAT
handovers)
QUsed Measured quality of N/A

the used frequency
TUsed2f Absolute quality It is specified by the event 2F threshold. For details,

threshold of the cell see Table 4-9.
that uses the current
frequency
H2f Event 2F hysteresis, HystFor2F (BSC6900, BSC6910) (for inter-frequency

used to prevent ping- handovers)
pong triggering of Hystfor2F (BSC6900, BSC6910) (for inter-RAT
event 2F. handovers)
Table 4-9 Parameters related to the event 2F threshold
Scenario Measurement Service Type Parameter

Quantity
Inter- Ec/N0 R99 CS service InterFreqCSThd2FEcN0 (BSC6900,

frequency BSC6910)
handover
R99 PS service InterFreqR99PsThd2FEcN0 (BSC6900,
BSC6910)
HSPA service InterFreqHThd2FEcN0 (BSC6900,

BSC6910)
RSCP R99 CS service InterFreqCSThd2FRSCP (BSC6900,

BSC6910)
R99 PS service InterFreqR99PsThd2FRSCP (BSC6900,

BSC6910)
HSPA service InterFreqHThd2FRSCP (BSC6900,

BSC6910)
Inter-RAT Ec/N0 R99 CS service InterRATCSThd2FEcN0 (BSC6900,

handover BSC6910)
R99 PS service InterRATR99PsThd2FEcN0 (BSC6900,

BSC6910)
HSPA service InterRATHThd2FEcN0 (BSC6900,

BSC6910)
RSCP R99 CS service InterRATCSThd2FRSCP (BSC6900,

BSC6910)
R99 PS service InterRATR99PsThd2FRSCP (BSC6900,

BSC6910)
HSPA service InterRATHThd2FRSCP (BSC6900,

BSC6910)
For hybrid networking and combined CS and PS services, the principles for event 2F-related
parameters and event 2D-related parameters are the same. For details, see Coverage-based Handover.
4.3.3.3 Penalty for Measurement Failures
For coverage-based or QoS-based handovers, including inter-frequency handovers and UMTS-

to-GSM handovers, if the UE fails to send a useful measurement report (a measurement report is
regarded as useless if it does not contain any neighboring cells or does not meet the requirement)
before the measurement timer expires, a penalty is imposed on the UE as follows:
• If an inter-frequency handover measurement in compressed mode was performed, this
measurement is stopped and the UE is prohibited from performing any inter-frequency
handover measurement in compressed mode triggered by any cause within the
duration specified by the penalty timer.
• If a UMTS-to-GSM handover measurement in compressed mode was performed, this
measurement is stopped and the UE is prohibited from performing any UMTS-to-
GSM handover measurement in compressed mode triggered by any cause within the
duration specified by the penalty timer.
The penalty timer is specified an RNC-level or cell-level parameter
PenaltyTimerForCMFailCov (BSC6900, BSC6910). If the PenaltyTimerForCMFailCov
(BSC6900, BSC6910) parameter is configured on both the cell and RNC levels, the cell-level value
takes precedence.
When a UE keeps camping on a cell, it can only initiate one QoS-based inter-frequency or inter-
RAT handover in the cell. Therefore, if a UE fails to perform a QoS-based inter-frequency or
inter-RAT handover in a cell due to the compressed mode penalty, it can no longer initiate the
same type of handover as long as it keeps camping on the cell.
4.3.4.1 Inter-Frequency Handovers
After receiving a measurement report from a UE, the RNC proceeds as follows:
Event 2B-triggered Measurement Report (for the Measurement-based Handover)
After receiving the event 2B measurement report for inter-frequency cells, the RNC starts the
following procedure:
1. Removes the blacklisted neighboring cells of the best cell from the target
neighboring cells where event 2B is triggered, adds the remaining cells to a cell set,
and prioritizes them based on the CPICH Ec/N0 value in descending order.
Blacklisted neighboring cells are those cells with BLACKLIST_FLAG is selected
under the NCellCapContainer (BSC6900, BSC6910) parameter.
2. (Optional and required when InterFreqHOConsiderRTWPSw (BSC6900,
BSC6910) is set to ON) Removes a neighboring cell from the cell set if the RTWP of
the neighboring cell minus its CPICH RSCP is greater than or equal to the value of
TargetFreqUlCoverLimitThd (BSC6900, BSC6910), specifically, if the target cell
provides poor uplink coverage.
3. Selects a cell from the cell set in sequence and instructs the UE to perform a
handover to the cell.
Event 1F-triggered Measurement Report (for the Blind Handover)
If there is only one cell in the active set, the RNC, upon receiving event 1F from an intra-
frequency cell, determines to initiate an inter-frequency blind handover. The process is as
follows:
1. The RNC obtains the best cell based on the event 1F report. If the signal quality of
the best cell meets conditions for blind handovers (specifically, the signal quality of
the best cell is not lower than the value of BlindHORSCP1FThreshold (BSC6900,
BSC6910)), the RNC obtains the neighboring cells of the best cell for blind handovers,
excluding the blacklisted neighboring cells and those at the UE-incapable bands. If
the signal quality of the best cell is lower than the value of
BlindHORSCP1FThreshold (BSC6900, BSC6910), the UE is at the edge of the
network coverage and blind handovers are not allowed.
For blacklisted neighboring cells, BLACKLIST_FLAG under the NCellCapContainer (BSC6900,

2. If there are multiple neighboring cells available for the blind handover, the RNC
chooses the cell that supports all the ongoing services of the UE. If there are multiple
such cells, the RNC randomly chooses one from them for blind handover.
If no inter-frequency cell is available, the RNC chooses an inter-RAT cell of the highest priority
in blind handovers. The priority in blind handovers for a cell can be specified by the
BlindHOPrio (BSC6900, BSC6910) parameter.
Periodic Measurement Reports
Figure 4-12shows the operations of the RNC upon reception of the periodic measurement report of
the inter-frequency cell.
Figure 4-12 Processing of the periodic measurement report of the inter-frequency cell during coverage- and QoS-
based inter-frequency handovers
Table 4-10 lists the variables and parameters involved in the process.
Table 4-10 Variables and parameters involved in processing of the periodic measurement report of the
inter-frequency cell during coverage- and QoS-based inter-frequency handovers
Variable/Parameter Description Parameter ID
Mother_Freq Measured CPICH N/A

Ec/N0 or CPICH RSCP
of the target cell
CIOother_Freq CIO of the target cell, CIO (BSC6900, BSC6910): CIO of the serving cell
which is the sum of CIO CIOOffset (BSC6900, BSC6910): CIO of the
and CIOOffset neighboring cell
Tother_Freq Quality threshold of the Parameters used for setting the service type
cells that use the target and measurement quantity:
frequencies • TargetFreqCsThdEcN0 (BSC6900,
BSC6910)
• TargetFreqCsThdRscp (BSC6900,
BSC6910)
• TargetFreqR99PsThdEcN0
(BSC6900, BSC6910)
• TargetFreqR99PsThdRscp
(BSC6900, BSC6910)
• TargetFreqHThdEcN0 (BSC6900,
BSC6910)
• TargetFreqHThdRscp (BSC6900,
BSC6910)
H Hard handover HystForPrdInterFreq (BSC6900, BSC6910)

hysteresis
Uplink RTWP N/A InterFreqHOConsiderRTWPSw (BSC6900,

switch BSC6910)
UL Coverage N/A TargetFreqUlCoverLimitThd (BSC6900,

Threshold for BSC6910)
Target Cell
HHO Period Trigger N/A TimeToTrigForPrdInterFreq (BSC6900,

Delay BSC6910)
Figure 4-13 shows the cell with the highest CPICH RSCP.
Figure 4-13 Cell with the highest CPICH RSCP
4.3.4.2 Inter-RAT Handovers
Event-triggered Measurement Reports
After receiving the event 3A measurement reports from GSM cells, the RNC starts the following
procedure:
1. Puts all the GSM cells that trigger event 3A into a cell set and arranges the cells
according to the signal quality in descending order.
2. Selects a cell from the cell set in sequence and instructs the UE to perform a
handover to the cell.
Periodic Measurement Reports
shows the operations of the RNC upon reception of the periodic measurement report of
Figure 4-14
GSM cells.
Figure 4-14 Processing of the periodic measurement report of the GSM cell during coverage- and QoS-based inter-
RAT handovers
Table 4-11 lists the variables and parameters involved in the process.
Table 4-11 Variables and parameters involved in processing of the periodic measurement report of the
GSM cell during coverage- and QoS-based inter-RAT handovers
Variable/Parameter Description Parameter ID
Mother_Freq Inter-RAT N/A

measurement result
CIOother_Freq CIO of the target cell, CIO (BSC6900, BSC6910): CIO of the serving cell
which is the sum of CIOOffset (BSC6900, BSC6910): CIO of the
CIO and CIOOffset neighboring cell
Tother_RAT Quality threshold of It is set based on the service type.

the cells that use the • TargetRatCsThd (BSC6900, BSC6910)
target frequencies • TargetRatR99PsThd (BSC6900, BSC6910)
• TargetRatHThd (BSC6900, BSC6910)
NOTE:
For CS+PS combined services, use the value for CS services.
H Inter-RAT handover HystforInterRAT (BSC6900, BSC6910) (RNC-level)

hysteresis HystforInterRAT (BSC6900, BSC6910) (cell-level)
Time-to-trigger N/A TimeToTrigForVerify (BSC6900, BSC6910) (BSIC

timer acknowledgement mode)
TimeToTrigForNonVerify (BSC6900, BSC6910)
(non-BSIC acknowledgement mode)
The reason and process for determining whether the signal quality of the best cell meets the
handover requirements are as follows:
Reason
Poor signal quality of the best cell may lead to handover failures. Before performing an inter-
RAT handover, the RNC checks the signal quality of the best cell. If the signal quality of the best
cell is poor, the RNC does not trigger an inter-RAT handover. This increases the inter-RAT
handover success rate.
Process
1. The RNC checks whether the switches for reporting the signal quality of intra-
frequency neighboring cells in periodic inter-RAT measurement for the single CS
service, single PS service, and CS+PS combined service are turned on:
• For a single CS service and CS+PS combined services, the switch can be
turned on by selecting
HO_CS_IRATHHO_WITH_INTRA_FREQ_MR_SWITCH under the
HoSwitch1 (BSC6900, BSC6910) parameter in the SET
UCORRMALGOSWITCH command.
• For a single PS service, the switch can be turned on by selecting
HO_PS_IRATHHO_WITH_INTRA_FREQ_MR_SWITCH under the
HoSwitch1 (BSC6900, BSC6910) parameter in the SET
UCORRMALGOSWITCH command.
If at least one switch is turned on, the periodic inter-RAT measurement reports sent
by the UE to the RNC contain the signal quality information about the cells in the
active set. In this case, the RNC proceeds to step 2 for the UEs with the switch set to
on. If neither switch is turned on, the RNC selects a target cell for a UMTS-to-GSM
handover. For details about target cell selection, see Target Cell Selection.
In an area where GSM and UMTS networks are deployed, you are advised to turn on both switches if
the inter-RAT handover success rate is lower than expected or if the customer is unsatisfied with the
situation where the UMTS network signal quality is good enough for UEs to camp on but UEs are
nevertheless handed over to the GSM network.
2. The RNC checks whether the Ec/N0 of the best cell in the active set meets the
following formula:
UsedIRATHOLowerThdEcNo (BSC6900, BSC6910) ≤ Ec/N0 of the best cell in the
active set ≤ UsedIRATHOUpperThdEcNo (BSC6900, BSC6910)
If the preceding formula is met, the RNC decides to perform an inter-RAT handover.
Otherwise, the RNC decides not to perform an inter-RAT handover.
The RNC needs to send an intra-frequency neighboring cell measurement control message to the UE because the
RNC decides whether to perform an inter-RAT handover based on the signal quality of intra-frequency neighboring
cells. The size of the inter-RAT measurement report increases when it contains the intra-frequency neighboring cell
measurement result, increasing the call drop rate.
Target Cell Selection
Upon receiving the first non-blank measurement report from a UE, the RNC selects a target cell
according to the following principles:
• If PERFENH_IRAT_COV_HO_NCELL_PRE_SWITCH under the
PerfEnhanceSwitch2 (BSC6900, BSC6910) parameter is not selected, the RNC
selects the neighboring cell with the best signal quality.
• If PERFENH_IRAT_COV_HO_NCELL_PRE_SWITCH under the
PerfEnhanceSwitch2 (BSC6900, BSC6910) parameter is selected, the RNC
preferentially selects the neighboring cell with the highest priority. If two or more
neighboring cells have the same priority, the RNC selects the one with the best signal
quality.
The HOPrio (BSC6900, BSC6910) parameter specifies the priorities of neighboring
GSM cells. Value 0 indicates the highest priority, and value 7 indicates the lowest
priority. If GSM 900 MHz and GSM 1800 MHz networks are deployed in the same
area and the operator expects UEs to be preferentially handed over to the GSM 1800
MHz network, set the priorities of neighboring GSM 1800 MHz cells to values within
the range of 0 to 3 and the priorities of neighboring GSM 900 MHz cells to values
within the range of 4 to 7.
4.3.5 Processing After a Handover Failure
Inter-Frequency Handover Failure
For a UE that is processing PS services, the RNC unconditionally enables the UE to continue
processing the PS services in the source cell.
For a UE that is processing CS services, the RNC enables the UE to continue processing the CS
services in the source cell only if AMR_HHO_FAIL_ROLLBACK_SWITCH under the
PROCESSSWITCH4 (BSC6900, BSC6910) parameter in the SET URRCTRLSWITCH
command is selected.
If an inter-frequency handover fails, the RNC takes the following measures:
• The RNC starts a penalty timer specified by the PenaltyTimerForIFHoFail
(BSC6900, BSC6910) parameter specific to the target cell. During the penalty period, the
RNC prohibits inter-frequency handovers to the target cell.
• The RNC starts a penalty timer specified by the UEPenaltyTimerForIFHoFail
(BSC6900, BSC6910) parameter specific to all cells.
If the number of consecutive inter-frequency handover failures for a UE reaches the
value of the IFHoFailNum (BSC6900, BSC6910) parameter, the RNC imposes a
penalty on the UE. During the penalty period, the RNC prohibits the UE from
initiating inter-frequency handovers.
Inter-RAT Handover Failure
If an inter-RAT handover to a cell triggered by event reporting fails, the RNC initiates inter-RAT
handovers to other candidate cells one by one. If an inter-RAT handover to a cell triggered by
periodic reporting fails, the RNC initiates an inter-RAT handover to other candidate cells only
when PERFENH_INTERRATHO_RETRY_SWITCH under the PerfEnhanceSwitch1
Upon receiving a message indicating inter-RAT handover failures from a UE (for example,
HANDOVER FROM UTRAN FAILURE from a UE processing CS services or CELL
CHANGE ORDER FROM UTRAN FAILURE from a UE processing PS services), the RNC
performs the following operations:
• Terminates the handover procedure and enables the UE to continue processing the CS
services in the source cell.
• Starts a penalty timer specific to the target cell. During the penalty period, the RNC
prohibits the UE from being handed over to the target cell again.
InterRATCovPenaltyTime (BSC6900, BSC6910) specifies the length of the penalty
timer. If InterRATCovPenaltyTime (BSC6900, BSC6910) is specified, the setting of
PERFENH_INTERRAT_PENALTY_50_SWITCH under the
PerfEnhanceSwitch (BSC6900, BSC6910) parameter through the SET
UCORRMPARA command does not take effect.
• Starts the penalty timer in all cells if handover attempts to all candidate cells fail. If the
number of handover failures caused by physical channel failures reaches the value of
the InterRatPhyChFailNum parameter, the RNC starts the penalty timer. During the
penalty period specified by the PenaltyTimeForPhyChFail, the UE is prohibited
from being handed over to any neighboring GSM cell.
The InterRatPhyChFailNum and PenaltyTimeForPhyChFail parameters are set by
running the cell-level command ADD UCELLINTERRATHOCOV or MOD
UCELLINTERRATHOCOV, or RNC-level command SET
UINTERRATHONCOV. If both RNC-level and cell-level parameters are
configured, the cell-level parameter settings prevail.
4.4 Load-based Inter-Frequency Handover
4.4.1 Procedure
The load-based inter-frequency handover suits cells with overlapping coverage. Figure 4-15 shows
the load-based inter-frequency handover procedure.
Figure 4-15 Load-based inter-frequency handover procedure
4.4.2 Triggering
If the load of a cell is higher than a specified threshold, the load reshuffling (LDR) algorithm
makes a handover decision. For details about LDR, see Load Reshuffling Feature Parameter Description.
4.4.3 Measurement
The load-based inter-frequency handover measurement starts after the compressed mode is
enabled. For details about the compressed mode, see 4.11.2 Compressed Mode.
For details about the target neighboring cells to be measured, see sections related to
measurement-based inter-frequency handovers in Inter Frequency Load Balance Feature Parameter
Description.
The load-based inter-frequency handover uses the periodic reporting mode.

• In a load-based inter-frequency blind handover, CPICH RSCP of the used frequency is
measured.
• In a load-based inter-frequency measurement-based handover, both CPICH RSCP and
CPICH Ec/N0 of the target frequency are measured.
The load-based inter-frequency measurement-based handover uses the event 2C-triggered
reporting mode.
A UE reports event 2C to the RNC if the following inequality is true and lasts for a period of
time specified by TrigTime2C (BSC6900, BSC6910):
QNoused ≥ TNoused2c + H2c/2
where
• QNoused is the measured quality of the inter-frequency neighboring cell.
• TNoused2c is the absolute quality threshold of the inter-frequency neighboring cell,
namely, InterFreqNCovHOThdEcN0 (BSC6900, BSC6910).
• H2c is the event 2C hysteresis value, which is specified by Hystfor2C (BSC6900,
BSC6910).
The load-based inter-frequency handover is triggered by LDR. This section describes the
procedure for load-based inter-frequency handover decision and execution triggered by LDR.
The LDR-triggered inter-frequency handover can be performed based on blind handovers or
measurement, which is specified by the InterFreqLDHOMethodSelection (BSC6900,
BSC6910) parameter.
Measurement-based Inter-Frequency Handover
The procedure is as follows:

1. The LDR algorithm learns that a cell is in basic congestion and provides target cells
and the UE with low priority for handover.
2. The RNC selects the target cell based on the measurement results and performs an
inter-frequency hard handover to the target cell. PrdReportInterval (BSC6900,
BSC6910) specifies the measurement result reporting period.
The target cell must meet all the following conditions:

• The target cell is not a blacklisted neighboring cell of the best cell.
Specifically, BLACKLIST_FLAG under the NCellCapContainer
(BSC6900, BSC6910) parameter is deselected for the target cell.
• The CPICH RSCP of the target cell is greater than the value of the
TargetFreqThdRscp (BSC6900, BSC6910) parameter.
• The CPICH Ec/N0 of the target cell is greater than the value of the
TargetFreqThdEcN0 (BSC6900, BSC6910) parameter.
• The target cell is not in the congestion state.
Blind Handover Decision and Execution
Figure 4-16 shows the procedure for the load-based inter-frequency blind handover.
Figure 4-16 Procedure for the load-based inter-frequency blind handover.
The inter-frequency cells with the same coverage area have the same CPICH RSCP values. By measuring the
CPICH RSCP of the serving cell, the RNC obtains quality of the cells with the same coverage area and determines
whether to allow a blind handover, which increases the probability of successful blind handovers.
Table 4-12 describes the parameters involved in Figure 4-16.

Table 4-12 Parameters involved in the procedure
SN Parameter ID Description
(1) HoSwitch (BSC6900, BSC6910): Switch for triggering LDR inter-frequency

HO_ALGO_LDR_ALLOW_SHO_SWITCH handovers during a soft handover
(2) BlindHOIntrafreqMRInterval (BSC6900, Intra-frequency measurement report

BSC6910) interval of blind handover
(3) BlindHOQualityCondition (BSC6900, Blind handover quality condition

BSC6910)
(4) BlindHOIntrafreqMRAmount (BSC6900, Number of intra-frequency measurement

BSC6910) reports for blind handover
4.5 Load-based UMTS-to-GSM Handover
When the load of the UMTS network is heavy and all the RABs of the UE are supported by the
GSM network, the load-based UMTS-to-GSM handover (WRFD-020306 Inter-RAT Handover
Based on Load) is triggered.
Load-based inter-RAT handovers are not allowed for CS+PS combined services.
4.5.1 Procedure
Figure 4-17 shows the load-based inter-RAT handover procedure.

Figure 4-17 Load-based inter-RAT handover procedure
4.5.2 Triggering
If the load of a cell is higher than a specified threshold, the load reshuffling (LDR) algorithm
makes a handover decision. For details about LDR, see WRFD-020106 Load Reshuffling in Load
Control Feature Parameter Description.
4.5.3 Measurement
The load-based inter-RAT handover measurement starts after the compressed mode is enabled.
For details about the compressed mode, see 4.11.2 Compressed Mode.
From the neighboring cells of the best cell, the RNC selects up to 32 cells as the target cells for
load-based inter-RAT handover measurements based on the priority (specified by the Nprio
(BSC6900, BSC6910) parameter) in descending order. If two or more neighboring cells have the
same Nprio (BSC6900, BSC6910) setting, the RNC randomly adds 32 cells to the neighboring cell
list.
The load-based inter-RAT handover measurement uses the event 3C-triggered reporting mode.
A UE reports event 3C to the RNC if the following inequality is true and lasts for a period of
time specified by TrigTime3C (BSC6900, BSC6910):
MOtherRAT + CIOOtherRAT ≥ TOtherRAT + H3c/2
Table 4-13 Variables involved in event 3C reporting
MOtherRAT Measurement value of the N/A

cell (in another RAT) in the
reporting range
CIOOtherRAT CIO of the cell (in another Sum of CIO (BSC6900, BSC6910) and CIOOffset
RAT) (BSC6900, BSC6910)
TOtherRAT Absolute inter-RAT InterRATNCovHOCSThd (BSC6900, BSC6910) (for

handover threshold CS services)
InterRATNCovHOPSThd (BSC6900, BSC6910) (for
PS services)
H3c Event 3C hysteresis HYSTFOR3C (BSC6900, BSC6910)
After receiving the event 3C measurement report of GSM cells, the RNC performs the following
decision and execution procedure:
1. Puts all the GSM cells that trigger event 3C into a cell set and arranges the cells
according to the signal quality in descending order.
2. Selects 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 InterRATHOAttempts (BSC6900, BSC6910) parameter is set to restrict the
maximum attempts of the UMTS-to-GSM load-based or service-based handover. The parameter
indicates the handover attempts made to different cells. If the number of handover attempts
exceeds the value of this parameter, the RNC does not initiate the handover.
4.6 Service-based Inter-Frequency Handover
For details about the service-based inter-frequency handover, see descriptions about the function
of inter-frequency DRD for service steering in Directed Retry Decision Feature Parameter Description.
4.7 Service-based UMTS-to-GSM Handover
The service-based inter-RAT handover supports UMTS-to-GSM handovers based on service

attributes and can balance the load between the two systems by transferring some kind of
appropriate services to GSM/GPRS. The inter-RAT handover in this section refers to the UMTS-
to-GSM handover.
Handover Switches
To perform the service-based UMTS-to-GSM 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 service-
based UMTS-to-GSM handover if CSServiceHOSwitch (BSC6900, BSC6910) is set
to ON.
• When a single PS service is initially set up by the UE, the RNC allows the service-
based UMTS-to-GSM handover if PSServiceHOSwitch (BSC6900, BSC6910) is set
to ON.
• When CS+PS combined services are initially set up by the UE, the RNC allows the
service-based UMTS-to-GSM handover if CSPSServiceHOSwitch (BSC6900,
BSC6910) is set to ON.
Handover Procedure
Figure 4-18 shows the procedure for the service-based inter-RAT handover.
Figure 4-18 Service-based inter-RAT handover procedure
Except for the triggering phase, the procedure for the service-based inter-RAT handover is the
same as that for the load-based inter-RAT handover. For details, see 4.5 Load-based UMTS-to-GSM
Handover.
When a service is established, the RNC requests the handover to GSM based on the service type
and service handover indications assigned by the CN.
shows the indications for load/service-based UMTS-to-GSM handover of a single
Figure 4-19
CS/PS service. CS+PS combined services do not support load-based UMTS-to-GSM handover
but support service-based UMTS-to-GSM handover. The indications for service-based UMTS-
to-GSM handover of +CSPS combined services are the same as those for service-based UMTS-
to-GSM handover of a single CS service.
Figure 4-19 Indications for load/service-based UMTS-to-GSM handover of a single CS/PS service
4.8 Speed-based Inter-Frequency and Inter-RAT Handover
4.8.1 Overview
The hierarchical cell structure (HCS) handover, indicated by WRFD-021200 HCS (Hierarchical
Cell Structure), is triggered based on UE speed estimation and can be implemented as an inter-
frequency or inter-RAT handover.
In a UMTS network, hot spots in radio communication may appear with the increase of
subscribers and traffic. This requires more cells to increase the network capacity. However, more
cells and smaller cell coverage areas lead to an increase in UE handovers. For a UE in fast
movement, frequent handovers reduce call quality, increase uplink interference, and increase
signaling load. HCS arranges cells at different layers and the cells at each layer are given an HCS
priority. The cells at different layers employ different frequencies and those at a layer must
provide continuous coverage.
Based on UE speed estimation, the RNC instructs a fast-moving UE to select a cell with a lower
HCS priority to decrease the frequency of handovers, and instructs a slow-moving UE to select a
cell with a higher HCS priority to increase the network capacity. The coverage area of a cell is
inversely proportional to its HCS priority.
Up to eight HCS priorities can be configured. The HCSPrio (BSC6900, BSC6910) parameter
specifies the priority of a cell. A smaller parameter value indicates a lower HCS priority and
larger coverage area.
There are three types of cells on the network: macro cell, micro cell, and Pico cell. If three HCS
priorities are configured, it is good practice to configure the highest HCS priority for the macro
cell and lowest for the Pico cell.
Figure 4-20 shows an HCS example with three layers.
Figure 4-20 HCS with three layers
Characteristics of different cells are as follows:

• Macro cell
▪ Large coverage
▪ Continuous coverage
▪ Low requirement for capacity
▪ Suitable for fast-moving UEs
• Micro cell
▪ Applicable to densely populated areas
▪ High requirement for capacity
▪ Suitable for slow-moving UEs
• Pico cell
▪ Indoor coverage
▪ Outdoor blind spot coverage
▪ Suitable for slow-moving UEs
To enable HCS handovers, select HO_ALGO_HCS_SPEED_EST_SWITCH under the
HoSwitch (BSC6900, BSC6910) parameter.
HCS is not recommended for the UMTS-to-GSM handover.

If the UseOfHcs (BSC6900, BSC6910) parameter is set to NOT_USED for a GSM cell, the cell does not use
HCS. You can refer to the LST UEXT2GCELL command output for the value of Use of HCS to check whether a
GSM cell uses HCS. For details about HCS-capable cells, see UE Behaviors in Idle Mode Feature Parameter
Description.
4.8.2 HCS Handover Procedure
The HCS handover is based on UE speed estimation. Figure 4-21 shows HCS handover procedure.
Figure 4-21 HCS handover procedure
4.8.3 Triggering of HCS Handover
Based on UE speed estimation, the RNC determines whether a UE is in the fast-moving, slow-
moving, or normal-moving state. Measurement is triggered when the UE is in the fast-moving or
slow-moving state.
When a UE enters the CELL_DCH state from the idle mode or CELL_PCH/URA_PCH state,
the RNC estimates the moving speed state of the UE according to the "UE Mobility State
Indicator" information element (IE) reported by the UE. The speed estimation principles are as
follows:
• If HO_HCS_SPD_INI_BSD_UE_SWITCH under the HoSwitch (BSC6900,
BSC6910) parameter is selected, the HCS speed estimation module obtains the "UE
Mobility State Indicator" IE from the RRC Connection Request or Cell Update
message reported by the UE. According to the "UE Mobility State Indicator" IE, the
HCS speed estimation module estimates the initial moving speed state of the UE as
follows:
▪ When the UE enters the CELL_DCH state from the idle mode and the value
of the "UE Mobility State Indicator" IE in the RRC Connection Request
message is High-mobilityDetected, the RNC considers the UE to be in the
fast-moving state.
▪ When the UE enters the CELL_DCH state from the
CELL_PCH/URA_PCH state and the value of the "UE Mobility State
Indicator" IE in the Cell Update message is High-mobilityDetected, the
RNC considers the UE to be in the fast-moving state.
▪ If neither of the preceding conditions is met, the RNC considers the UE to
be in the normal-moving state.
• If HO_HCS_SPD_INI_BSD_UE_SWITCH under the HoSwitch (BSC6900,
BSC6910) parameter is not selected, the RNC considers the UE to be in the normal-
moving state.
• A UE can report the "UE Mobility State Indicator" IE only in the networks complying with 3GPP
Release 7 or later.
• For details about speed estimation and cell reselection parameters for the UEs in idle mode or in the
CELL_PCH/URA_PCH state, see UE Behaviors in Idle Mode Feature Parameter Description.
After a UE enters the CELL_DCH state from the idle mode or CELL_PCH/URA_PCH state, the
speed estimation algorithm estimates and then decides the moving speed of the UE based on the
number of best cell changes within a specified period.
The procedure for high-speed estimation is as follows:
1. If HO_ALGO_HCS_SPEED_EST_SWITCH under the HoSwitch (BSC6900,
BSC6910) parameter is selected and the cell has an HCS priority that is not the lowest,
the RNC initiates high-speed estimation for the UE after receiving an event 1D
report.
2. A UE is considered to be in the fast-moving state if the number of its best cell
changes is greater than the value of NFastSpdEst (BSC6900, BSC6910) within the
duration specified by TFastSpdEst (BSC6900, BSC6910).
The procedure for low-speed estimation is as follows:
1. If HO_ALGO_HCS_SPEED_EST_SWITCH under the HoSwitch (BSC6900,
BSC6910) parameter is selected and the cell has an HCS priority that is not the
highest, the RNC starts the timer specified by TCycleSlow (BSC6900, BSC6910) after
the RRC connection is set up.
2. When the timer specified by TCycleSlow (BSC6900, BSC6910) expires, the RNC
initiates low-speed estimation for the UE.
3. If the number of changes of the best cell for the UE is less than the value of
NSlowSpdEst (BSC6900, BSC6910) within a time period specified by
TSlowSpdEst (BSC6900, BSC6910), 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 reported.
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 (BSC6900,
BSC6910), if multiple event 1Ds are reported for a certain cell, only the first one is recorded.
4.8.4 HCS Handover Measurement
The HCS handover measurement starts after the compressed mode is enabled. For details about
the compressed mode, see 4.11.2 Compressed Mode.
If a UE is in the fast-moving state and switches from a cell with a lower HCS priority to a cell
with a higher HCS priority, handover measurements are not required and the RNC directly
initiates a blind handover.
If the neighboring cells do not support blind handover or the UE is in the slow-moving state and
switches from a cell with a higher HCS priority to a cell with a lower HCS priority, handover
measurements are performed and the UE uses the event-triggered reporting mode.
• In the inter-frequency HCS handover, event 2C takes only the CPICH Ec/N0 as the
measurement quantity. For details about triggering of event 2C, see 4.4.3 Measurement.
• In the inter-RAT HCS handover, event 3C takes only the GSM RSSI as the
measurement quantity. For details about triggering of event 3C, see 4.5.3 Measurement.
4.8.5 HCS Handover Decision and Execution
After receiving event 2C or event 3C, the RNC determines whether to initiate a handover based
on the estimated UE speed. HCS handover execution based on UE speed estimation falls into the
following two categories:
• Inter-layer handover in fast movement: If the UE is in fast movement, the RNC
instructs the UE to select a cell with a lower HCS priority.
• Inter-layer handover in slow movement: If the UE is in slow movement, the RNC
instructs the UE to select a cell with a higher HCS 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 HCS 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 HCS priority.
• If the UE is located in the overlap between the cell with a higher HCS priority and the
cell with a lower HCS priority, a blind handover is initiated.
1. The RNC selects the neighboring cells with a lower HCS priority level to
generate a cell list. If neighboring cells on multiple candidate frequencies
are available, the RNC selects cells on one frequency.
2. From the cell list generated in 1, the RNC selects a cell whose blind
handover flag is TRUE as the target cell for blind handovers.
The blind handover flag is specified by BlindHOFlag (BSC6900, BSC6910)
for inter-frequency cells and BlindHOFlag (BSC6900, BSC6910) for inter-
RAT cells.
3. 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 priority of an inter-frequency blind handover is higher than that of an
inter-RAT blind handover.
• If the UE is not located in the overlap between the cell with a higher HCS priority and
the cell with a lower HCS priority, the measurement on the cell with a lower HCS
priority is initiated.
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 HCS priority for measurement. Based on the measurement report from the UE, the RNC
selects the cell with the best signal quality as the target cell.
4.8.6 Interoperability Between HCS Handover and Other Handovers
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
interrupted.
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.
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 IIFAntiPingpangTimerLength (BSC6900, BSC6910) expires.
• If the timer does not expire, the RNC cancels the handover.
• If the timer expires, the RNC starts the handover.
4.9 UMTS-to-GSM Handovers When NACC Is Supported
This section describes the feature WRFD-02030801 NACC (Network Assisted Cell Change).
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 Network Assisted Cell Change (NACC) enables the system
information exchange between different BSSs, or between BSS and RAN. The inter-RAT
handover delay, especially inter-RAT handover delay in PS domains, can be reduced. With
NACC, the SRNC requests and receives the SI/PSI from the target BSS and the target RNC
sends the UE a cell change order, which contains the GSM EDGE Radio Access Network
(GERAN) system information, when the UMTS-to-GSM handover in the PS domain is triggered.
The NACC process specified in TS 25.901 is shown in the following figure.
Figure 4-22 NACC process specified in the protocol
Information exchange between BSSs or between the BSS and the RAN can be implemented by
exchanging RIM messages through either the CN or Huawei proprietary eCoordinator.
RIM messages can be exchanged between the UTRAN and GERAN through the eCoordinator when the following
conditions are met: Huawei devices used in the UTRAN and GERAN are connected to the same eCoordinator. The
CN to which the UTRAN and GERAN connect does not support the RIM procedure or the RIM procedure is not
enabled for the UTRAN and GERAN. When the RIM procedure is performed through the eCoordinator, the
switches for the RIM procedure must be turned on for NEs involved in the procedure, such as BSC, eCoordinator,
and RNC. Otherwise, the RIM procedure cannot be performed through the eCoordinator and these NEs cannot send
RIM messages to or respond to RIM messages from the CN.
When HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH is deselected under the

HoSwitch (BSC6900, BSC6910) parameter, the PS inter-RAT handover from the 3G network to
the 2G network can be performed in the cell change order procedure, that is, the NACC
associated UMTS-to-GSM handover procedure can be initiated. With NACC, the RNC sends a
cell change order carrying the SI/PSI of the GERAN to the UE when a UMTS-to-GSM handover
is triggered. To enable the NACC function, do as follows:
• Run the SET UCORRMALGOSWITCH command with
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH under HoSwitch
(BSC6900, BSC6910) set to ON.
• Run the ADD UEXT2GCELL or MOD UEXT2GCELL command with the
parameter SuppRIMFlag (BSC6900, BSC6910) set to TRUE.
• Select RIM_ON_ECO_SWITCH under the PROCESSSWITCH5 (BSC6900,
BSC6910) parameter in the RNC MML command SET URRCTRLSWITCH when
the RIM procedure is performed through the eCoordinator.
4.10 UMTS-to-GSM PS Handover
This section describes the feature WRFD-02030802 PS Handover Between UMTS and GPRS.
If HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH under the HoSwitch (BSC6900,
BSC6910) parameter is selected, the PS handover from UMTS to GSM is performed in the
relocation process. Otherwise, the PS handover from UMTS to GSM is performed in the cell
change order process.
To enable the PS handover, do as follows:
• Run the SET UCORRMALGOSWITCH command with
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH under the HoSwitch
(BSC6900, BSC6910) parameter set to ON.
• Run the ADD UEXT2GCELL or MOD UEXT2GCELL command with the
SuppPSHOFlag (BSC6900, BSC6910) parameter set to TRUE.
4.11 Other Functions
4.11.1 Handover Protection
4.11.1.1 Anti-Ping-Pong
Inter-Frequency Anti-Ping-Pong
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 works as follows:
1. If a coverage-based inter-frequency handover, an inter-frequency blind handover
based on event 1F, or a QoS-based inter-frequency handover succeeds, the RNC
starts a timer specified by the IFHoPingPongTimer (BSC6900, BSC6910) parameter
for the UE.
• Before the timer expires, the RNC prohibits the UE from re-initiating
coverage-based inter-frequency handovers, inter-frequency blind
handovers based on event 1F, or QoS-based inter-frequency handovers.
• After the timer expires, the RNC allows the UE to re-initiate coverage-
based inter-frequency handovers, inter-frequency blind handovers based
on event 1F, or QoS-based inter-frequency handovers.
2. When a non-coverage-based inter-frequency handover is triggered, the RNC
determines whether the timer specified by IFAntiPingpangTimerLength
(BSC6900, BSC6910) expires.
• If the timer does not expire, the RNC cancels the handover.
• If the timer expires, the RNC performs the handover.
Inter-RAT (GSM-to-UMTS) Anti-Ping-Pong
For the GSM-to-UMTS handover, the measurement control message is delivered through the
GSM system information when the GSM cell has a neighboring UMTS cell. The dual-mode MS
performs the inter-RAT measurement in idle timeslots and reports the measurement result. Based
on the reported measurement result, the BSC decides whether to perform a handover to the
UMTS network.
To avoid the ping-pong handover between GSM and UMTS networks, the GSM-to-UMTS
handover penalty algorithm is used.
When the UE is handed over from a GSM network to a UMTS network, if any CS domain
service exists, the system increases the hysteresis of event 3A through the parameter
InterRATPingPongHyst (BSC6900, BSC6910) to prevent the UE from the ping-pong handover
between GSM and UMTS in the period specified by the parameter InterRATPingPongTimer
(BSC6900, BSC6910). During the penalty time, the previous periodic report will be changed to the
event 3A report. The value 0 indicates that the system does not take measures to avoid ping-pong
handovers between GSM and UMTS networks.
4.11.1.2 Handover Retry
4.11.1.2.1 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 the 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 number of retries exceeds the upper limit. If the handover succeeds or two new
event 2B reports are received, the periodic 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 retries:
• Retry timer: PeriodFor2B (BSC6900, BSC6910)
• Maximum number of retries: AmntOfRpt2B (BSC6900, BSC6910)
For the inter-frequency handover based on speed estimation, the following two parameters
determine the retry period and the maximum number of retries:
• Retry timer: PeriodFor2C (BSC6900, BSC6910)
• Maximum number of retries: AmntOfRpt2C (BSC6900, BSC6910)
4.11.1.2.2 Inter-RAT (UMTS-to-GSM) Handover Retry
For an inter-RAT handover failure, if the cause of the failure is neither a configuration failure
nor the retry timer expiry, the UE makes attempts to be handed over to the cell again until the
number of retries exceeds the upper limit.
The retry timer and maximum number of retries for coverage-based and QoS-based inter-RAT
handovers are:
• Retry timer: PeriodFor3A (BSC6900, BSC6910)
• Maximum number of retries: AmntOfRpt3A (BSC6900, BSC6910)
The retry timer and maximum number of retries for load-based and service-based inter-RAT
handovers are:
• Retry timer: PeriodFor3C (BSC6900, BSC6910)
• Maximum number of retries: AmntOfRpt3C (BSC6900, BSC6910)
If the penalty timer starts in the target cell after an inter-RAT handover fails, an inter-RAT
handover retry is allowed only after the retry timer following the penalty timer expiry times out.
For example, the penalty timer is set to 4s, the retry timer is set to 2s, and a maximum of four
retries are allowed. After an inter-RAT handover fails, the next inter-RAT handover retry is
allowed 6s later, specifically, after the retry timer expires for the third time. Up to two retries (the
third and fourth retries) are allowed.
The inter-RAT handover retry algorithm involves the following two signaling procedures:
• Signaling procedure for Iu relocation
• Signaling procedure for service-based handover on the Uu interface
Signaling Procedure for Iu Relocation
1. The RELOCATION REQUIRED message is initiated on the Iu interface.

2. 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 failures, the RNC
does not make a handover retry to the cell.
• Relocation failure in the target CN/RNC or target system
• Relocation not supported or not allowed in the target RNC or target system
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 number of retries exceeds
the upper limit.
3. If the RNC receives the RELOCATION COMMAND message, the handover on the
Uu interface continues.
4. If the handover succeeds or the new event 3A or 3C report is received, the periodic
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.
• For PS services 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 IE "Inter-RAT handover failure cause" in HANDOVER FROM UTRAN FAILURE
message is "Configuration unacceptable", or if the IE "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 number of retries exceeds the upper limit.
If the handover succeeds or the new event 3A or 3C report is received, the periodic retry is
stopped.
4.11.1.3 Inter-RAT Multimedia Fallback
This section describes the feature Video Telephony Fallback to Speech (AMR) for Inter-RAT
HO. This feature is an enhancement to the following features:
• WRFD-020303 Inter-RAT Handover Based on Coverage
• WRFD-020305 Inter-RAT Handover Based on Service
• WRFD-020306 Inter-RAT Handover Based on Load
• WRFD-021200 HCS (Hierarchical Cell Structure)
The GSM network does not support videophone (VP) services. Therefore, the RNC, before
performing a handover for a UE running VP services, needs to initiate multimedia fallback to
change the VP services to the AMR speech services, that is, to perform a UMTS-to-GSM
handover based on the CS AMR speech service. This operation avoids call drops.
This function has the following requirements for the CN and UE:
• The CN needs to comply with 3GPP Release 6 or a later version so that the RNC can
send an RAB modify message to trigger fallback of a UE from a VP service to an
AMR service.
• The UE needs to comply with 3GPP Release 6 or a later version. However, this
function is only optional, which may not be supported by a UE complying with 3GPP
Release 6 or a later version.
As specified in section 4.3 "Core Network procedure" in 3GPP TS 23.172 V10.0.0, 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.
• The process of changing multimedia services back to speech services during the call.
Triggering of Fallback Service
Currently, the network-initiated multimedia fallback is performed only for the UMTS-to-GSM
handover. Service changes triggered by the UEs are not supported.
Fallback is initiated when both of the following conditions are met:
• The RNC decides to send an inter-RAT handover request after receiving periodic
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 4-23 shows the service change procedure for the UMTS-to-GSM 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 4-23 Service change procedure for the UMTS-to-GSM handover in the CS domain
When the multimedia fallback ends, the RNC decides whether to perform the UMTS-to-GSM
handover according to the current measurement results reported by the UE.
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.
4.11.2 Compressed Mode
4.11.2.1 Overview
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. The UE must use
the compressed mode if the UE needs to measure the pilot signal strength of an inter-frequency
cell or inter-RAT cell and has a single-frequency receiver only.
Figure 4-24 Compressed mode
4.11.2.2 Compressed Mode Switches
General Switch
The DlSFLimitCMInd (BSC6900, BSC6910) parameter specifies whether to start the downlink
compressed mode according to the LimitCMDlSFThd (BSC6900, BSC6910) parameter setting.
• If DlSFLimitCMInd (BSC6900, BSC6910) is set to TRUE,
▪ When the downlink spreading factor is less than or equal to the value of the
LimitCMDlSFThd (BSC6900, BSC6910) parameter, the compressed mode is
disabled.
▪ When the downlink spreading factor is greater than the value of the
LimitCMDlSFThd (BSC6900, BSC6910) parameter, the compressed mode is
enabled.
• If DlSFLimitCMInd (BSC6900, BSC6910) is set to FALSE, the compressed mode is
not limited by the downlink spreading factor.
The uplink 384 kbit/s uses SF4. The method of SF/2 is not allowed for the services of SF4.
CMCF_UL_PRECFG_TOLERANCE_SWITCH under the CmcfSwitch (BSC6900, BSC6910)
parameter specifies whether to set up the uplink 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 the CmcfSwitch (BSC6900,
BSC6910) parameter specifies whether to use the frequencies beyond the range of UE reports on
the compressed mode measurement.
To initiate the high layer scheduling, set the following two switches:
• If CMCF_DL_HLS_SWITCH under the CmcfSwitch (BSC6900, BSC6910)
parameter is set to ON, the downlink high-layer scheduling for the compressed mode
is allowed.
• If CMCF_UL_HLS_SWITCH under the CmcfSwitch (BSC6900, BSC6910)
parameter is set to ON, the uplink high-layer scheduling for the compressed mode is
allowed.
Switches for State Transition of UEs in Compressed Mode
Table 4-14lists the parameters for specifying whether a UE in compressed mode is allowed to
switch to the CELL_FACH or CELL_PCH state.
Table 4-14 Switches for state transition of UEs in compressed mode
Parameter Option Handover Value

Cause
CmcfSwitch CMCF_UE_STATE_TRANS_COV_SWITCH Coverage • ON:

(BSC6900, indicates
BSC6910) the state
transition is
allowed for
UEs in
compressed
mode.
• OFF:
indicates
the state
transition is
not allowed
for UEs in
compressed
mode.
Parameter Option Handover Value
Cause
CMCF_UE_STATE_TRANS_NCOV_SWITCH Non- • ON:

coverage indicates
the state
transition is
allowed for
UEs in
compressed
mode.
• OFF:
indicates
the state
transition is
not allowed
for UEs in
compressed
mode.
Compressed Type Selection Switch
The RNC parameter InterFreqRATSwitch (BSC6900, BSC6910) specifies the compression type.
• Value INTERFREQ indicates that only the inter-frequency measurement is allowed.
• Value INTERRAT indicates that only the inter-RAT measurement is allowed.
• Value SIMINTERFREQRAT indicates that both the inter-frequency and inter-RAT
measurements are allowed.
If InterFreqRATSwitch (BSC6900, BSC6910) is set to SIMINTERFREQRAT, the
CoexistMeasThdChoice (BSC6900, BSC6910) parameter decides the event 2D/2F
threshold to be used.
▪ Value COEXIST_MEAS_THD_CHOICE_INTERFREQ indicates that
the event 2D/2F threshold for the inter-frequency measurement is used.
▪ Value COEXIST_MEAS_THD_CHOICE_INTERRAT indicates that the
event 2D/2F threshold for the inter-RAT measurement is used.
Compatibility Switch for Dual-frequency Receiver
If the UE has a dual-frequency receiver, it can perform inter-frequency or inter-RAT

measurement without starting the compressed mode when all of the following conditions are
met:
• CMP_UU_ADJACENT_FREQ_CM_SWITCH under the CmpSwitch (BSC6900,
• The IE "Adjacent frequency measurements without compressed mode" reported by the
UE is TRUE.
• For a UE that supports DC-HSDPA/DC-HSUPA:
▪ If the UE has a DC-HSDPA/DC-HSUPA service, all the cells involved in
inter-frequency measurement are at the same frequency as the secondary
carrier.
▪ If the UE does not have a DC-HSDPA/DC-HSUPA service, all the cells
involved in inter-frequency measurement are at the same frequency, with a
5 MHz spacing from the current cell, but within the same band as the
current cell.
If a UE that supports DC-HSDPA/DC-HSUPA does not meet the preceding conditions, it needs
to perform inter-frequency or inter-RAT measurement in compressed mode. In this case, the
same sequence and type of compressed mode are required by the primary and secondary carriers.
Compatibility Switches for HSPA
Some UEs do not support the compressed mode when HSPA+ or HSPA is enabled. For
compatibility reasons with these UE, compatibility switch parameters have been introduced.
Service Parameter Value Compressed Mode Service

Starting Allowed or Setup
Not Allowed
When the
Compressed
Mode Is
Enabled
HSDPA HsdpaCMPermissionInd TRUE Allowed Allowed

(BSC6900, BSC6910)
FALSE The UE must be first Not allowed
reconfigured from
the HSDPA to the
DCH and then starts
the compressed
mode to measure
neighboring cells.
HSUPA HsupaCMPermissionInd Permit Allowed Allowed

(BSC6900, BSC6910)
Limited The UE must be first Not allowed
reconfigured from
the E-DCH to the
DCH and then starts
the compressed
mode to measure
neighboring cells.
Service Parameter Value Compressed Mode Service
Starting Allowed or Setup
Not Allowed
When the
Compressed
Mode Is
Enabled
BasedOnUECap The UE capability determines

whether to start the compressed
mode and whether HSDPA
services are allowed.
HSPA+ EHSPACMPermissionInd FALSE The UE is Not allowed

(BSC6900, BSC6910) reconfigured to the
DCH first and starts
the compressed
mode.
TRUE Allowed (for UEs Allowed

supporting the
compressed mode)
Not allowed (for UEs Not allowed

not supporting the
compressed mode)
DC- McHsdpaLteCMPermissionInd TRUE Allowed Allowed

HSDPA (BSC6900, BSC6910)
FALSE The UE must be first Not allowed
reconfigured to the
HSDPA and starts
the compressed
mode to measure
neighboring cells.
Certain UEs may not support HSDPA/HSUPA/HSPA+. To ensure network performance, it is

good practice to blacklist such UEs for the function as described in Terminal Black List Feature
Parameter Description. In this situation, blacklisted UEs in compressed mode cannot initiate
HSDPA/HSUPA/HSPA+ services.
During the blacklist setting, set the TAC_FUNC (BSC6900, BSC6910) parameter to
Special_User_Enhance and select SPECUSER_NO_HSDPACM_SWITCH (for HSDPA),
SPECUSER_NO_HSUPACM_SWITCH (for HSUPA), or
SPECUSER_NO_EHSPACM_SWITCH (for HSPA+) under the
SpecUserFunctionSwitch4 (BSC6900, BSC6910) parameter.
4.11.2.3 Compression Methods
Table 4-15 describes the two methods for implementing the compressed mode.
Table 4-15 Methods for implementing the compressed mode
Method Description
SF/2 The SF is reduced by half to improve the rate on the channel. It takes less time
to transmit the same volume of data. In this way, transmit gaps are created.
The SF must be greater than 4.
The SF/2 mode consumes more system resources and therefore this mode is
recommended only for low-rate users.
High layer High layer limits the allowed Transport Format Combination (TFC) to create
scheduling gaps without data to be transmitted.
The high-layer scheduling mode 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. Therefore, this mode is
recommended only when the SF/2 approach is unavailable or there are high-
rate users.
The RNC automatically determines the type of compressed mode based on the spreading factor
used in the uplink or the downlink.
• If the downlink spreading factor is greater than or equal to the value of the
DlSFTurnPoint (BSC6900, BSC6910) parameter, the SF/2 approach is used.
Otherwise, high layer scheduling is used.
• If the uplink spreading factor is greater than or equal to the value of the
UlSFTurnPoint (BSC6900, BSC6910) parameter, the SF/2 approach is used.
Otherwise, high layer scheduling is used.
4.11.2.3.1 SF/2 Compressed Mode
Figure 4-25 shows how to implement the SF/2 compressed mode.

Figure 4-25 Implementation of the SF/2 compressed mode
1. For details about the alternative scrambling code, see section 4.3.2 "Scrambling codes" in 3GPP
TS25.213 V10.0.0.
2. DlCMAvoidChgScCodeSwitch (BSC6900, BSC6910) is set by running the ADD
UCELLALGOSWITCH or MOD UCELLALGOSWITCH command.
Replacing the Scrambling Code with an Alternative One
uses the AMR voice service with SF128 as an example to show the code resource
Figure 4-26
usage before and after the SF is halved by using an alternative scrambling code.
Figure 4-26 Halving the SF by using an alternative scrambling code
When an AMR UE starts SF/2 compressed mode, the adjacent code (SF128, 13) has been
occupied, which makes the root code word (SF64, 6) become unavailable. Meanwhile, code
resources in the cell are insufficient, so a halved SF (SF64, 6) is obtained by using an alternative
scrambling code. The original channelization code (SF128, 12) is reserved to be used when the
compressed mode ends.
Reallocating a Channelization Code
The orthogonality obtained by using an alternative scrambling code is lower than the
orthogonality obtained by reallocating a channelization code. Therefore, using an alternative
scrambling code will increase interference to a cell, which raises transmit power of the cell or
decreases throughput of the cell. For this reason, it is recommended that the function of halving
the SF based on channelization code reallocation be enabled so that an idle channelization code
of a new brother code instead of an alternative scrambling code is used when code resources are
sufficient.
uses the AMR voice service with SF128 as an example to show the code resource
Figure 4-27
usage before and after the SF is halved by reallocating the channelization code.
Figure 4-27 Halving the SF by reallocating a channelization code
When an AMR UE starts SF/2 compressed mode, the adjacent code (SF128, 13) has been
occupied, which makes the root code word (SF64, 6) become unavailable. Meanwhile, code
resources in the cell are sufficient, so the service is reconfigured to use (SF128, 14) and the idle
channelization code (SF64, 7) will be used by the service in compressed mode to obtain the
halved SF. The original channelization code (SF128, 14) is reserved to be used when the
compressed mode ends.
The DlSFdiv2CmValidCodeThd (BSC6900, BSC6910) parameter defines the effective scope of
the channelization codes to be reallocated by UEs to implement SF/2 compressed mode. This
parameter uses the SF16 code tree as a unit. The RNC allocates an idle code word with a smaller
code number to the UE. Therefore, when the code number of the channelization code reallocated
by the UE is less than the value of the preceding parameter, the channelization code resources
and available HSDPA channelization code resources of the cell are sufficient, so a new
channelization code will be allocated. If not, the channelization code resources and available
HSDPA channelization code resources of the cell are insufficient, so an alternative scrambling
code will be used to implement SF/2 compressed mode.
The recommended value of the parameter is 10. If the parameter is set to an excessively large
value, a new channelization code can be allocated even when the code resource is experiencing a
congestion, which causes negative gains to the HSDPA throughput. If the parameter is set to an
excessively small value, the channelization code cannot be allocated even when the code
resources are sufficient, making it difficult to obtain gains.
When the code words of the cell are not experiencing congestion, this function can reduce the
number of times (VS.CM.DLSF2.AltScramCode.UE.Mean (BSC6900, BSC6910)) the alternative
scrambling code is used by UEs in SF/2 compressed mode, which decreases interference to the
system and reduces the downlink DPCH power. It increases throughput of the HSDPA UEs
when data service resources are sufficient.
The more UEs using channelization code reallocation to implement SF/2 compressed mode, the
more DPCH power is saved. In medium-load cells, for example, there are 15 to 30 UEs on the
DCH and compressed mode is started over 300 times, this function can reduce the number of
UEs who use alternative scrambling codes to implement SF/2 compressed mode and it decreases
the downlink R99 DCH transmit power by 0% to 5%, compared with the same scenario when
this function is disabled. If there are always HSDPA UEs with sufficient data sources throughout
the measurement period, the downlink throughput of HSDPA UEs can be increased by 5% at
most.
In addition, this function may slightly increase the number of downlink channelization code
words used in the cell because it does not use any alternative scrambling code.
4.11.2.3.2 Higher Layer Scheduling Compressed Mode
Higher layer scheduling is implemented to control the transport format combination set (TFCSs)
that are multiplexed to a CCTrCH. It adjusts the transport format combinations (TFCs) in the
TFCSs to limit the maximum transmission rate in the TFCS. A TFCS is adjusted not to generate
the new TFC but to avoid using the TFCs with high transmission rates in the TFCS. By lower-
layer rate matching and insertion of the DTX (discontinuous transmission) indication bit, the
compression mode is achieved.
4.11.2.4 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 after the inter-frequency measurement timers listed in the following table expire.
Handover Type Timer Parameter
Inter-frequency handover based on InterFreqMeasTime (BSC6900, BSC6910)

load and HCS
Coverage-based inter-RAT InterRATMeasTime (BSC6900, BSC6910)

handover
Inter-RAT handover based on load InterRATMeasTime (BSC6900, BSC6910)

and service
Uplink QoS-based inter-RAT ULQosMcTimerLen (BSC6900, BSC6910)

handover
Downlink QoS-based inter-RAT DLQosMcTimerLen (BSC6900, BSC6910)

handover
4.11.2.5 Check of Compressed Mode Parameter Settings During Inter-RNC Handover
During an inter-RNC handover, the NodeB checks static compressed mode parameter settings to
avoid handover failures due to inconsistent compressed mode parameter settings. Figure 4-28
shows the process of checking static compressed mode parameter settings.
Figure 4-28 Checking static compressed mode parameter settings
The following table lists the parameters involved in the figure above.
SN Parameter
(1) OPTIMIZATIONSWITCH4 (BSC6900,

BSC6910):DRNC_NOTICE_NODEB_SRNC_VEST_SWITCH
(2) ProcessSwitch (BSC6900, BSC6910): NRNC_COMPATIBLE_SWITCH of the

peer RNC
4.11.3 Inter-Frequency Measurements in Batches
As stipulated in 3GPP specifications, a UE can measure only two frequencies belonging to other
frequency bands at a time. If two or more frequencies are included in the network plan, it is
recommended that Interfreqmcmode (BSC6900, BSC6910) be set to ON and
PERFENH_BATCH_FREQ_SEND_MCREL_OPT_SWITCH under the
OptimizationSwitch7 (BSC6900, BSC6910) parameter be selected to support batch
measurement of multiple frequencies. When Interfreqmcmode (BSC6900, BSC6910) is set to
ON, frequencies belonging to other frequency bands are listed. The RNC selects target
neighboring cells to be measured in the same way as that described in Target Neighboring Cell
Selection. The RNC sends the UE information about the neighboring cells operating on the first
two frequencies. If no inter-frequency neighboring cell meets the required conditions and the
timer specified by InterFreqMeasTime (BSC6900, BSC6910) expires, the RNC sends a
measurement control message to the UE, instructing the UE to stop the measurement on the
specified frequencies and start the measurement on new frequencies. If no more frequencies are
to be measured, the RNC stops the compressed mode. A maximum of three batches of inter-
frequency measurements are supported, that is, a maximum of six frequencies are measured. If
an inter-frequency or inter-RAT handover is to be triggered, the UE can also measure the
frequencies of inter-frequency neighboring cells in batches.
Batch measurement does not affect inter-RAT measurement. It is recommended that the timer
specified by InterFreqMeasTime (BSC6900, BSC6910) be set to 20s so that the measurement in
other inter-frequency neighboring cells is not postponed by a long measurement period.
4.11.4 BSIC Verification Requirements for GSM Cells
During inter-RAT measurement, the UE reports the GSM cell to the RNC after the Base
Transceiver Station Identity Code (BSIC) of the cell is verified. This greatly enhances handover
reliability.
After the compressed mode is started, if the RNC instructs a UE to measure only neighboring
GSM cells during an inter-RAT handover, the UE needs to measure the Received Signal
Strength Indication (RSSI), initial BSIC verification (Init BSIC), and BSIC re-verification (BSIC
Reconfirm). The Init BSIC and BSIC Reconfirm are collectively termed BSIC verification.
The following table lists the parameters that take effect in the RNC-level command SET
UINTERRATHOCOV or cell-level commands ADD UCELLINTERRATHOCOV and MOD
UCELLINTERRATHONCOV when BSICVerify is set to REQUIRED during an inter-RAT
handover for a single CS or PS service. The BSIC verification mode depends on the parameter
setting.
Table 4-16 BSIC verification mode
Service Parameter ID Parameter Setting Description
Type
CS CSBSICVerifyindication BSICINIT_AND_RECONFIRM Both initial BSIC verification

service (BSC6900, BSC6910) and BSIC re-verification are
required.
BSICINIT Only initial BSIC verification

is required.
PS PSBSICVerifyindication BSICINIT_AND_RECONFIRM Both initial BSIC verification

service (BSC6900, BSC6910) and BSIC re-verification are
required.
BSICINIT Only initial BSIC verification

is required.
BSICINIT_ADPT Initial BSIC verification is

dynamically performed
depending on whether the
BCCHs of any two inter-
Service Parameter ID Parameter Setting Description
Type
RAT neighboring cells use

the same ARFCN.
When both the cell- and RNC-level parameters are set, the cell-level parameters settings prevail.
4.11.5 Rules for Inter-RAT Handovers
Capability Requirements
Before deciding a UMTS-to-GSM handover, the RNC checks the UE capability and settings of
the RatCellType (BSC6900, BSC6910) and Req2GCap (BSC6900, BSC6910) parameters. Table 4-
17 describes the impacts of different types of capability on handover decision.
Table 4-17 Impacts of different types of capability on handover decision
RatCellType UE Capability Req2GCap
EDGE GPRS GSM
EDGE EDGE Allowed Allowed Allowed
GPRS Not allowed Allowed Allowed
GSM Not allowed Not allowed Allowed
Not supported by Not allowed Not allowed Not allowed

2G
GPRS EDGE Not allowed Allowed Allowed
GPRS Not allowed Allowed Allowed

2G
GSM EDGE Not allowed Not allowed Allowed
GPRS Not allowed Not allowed Allowed

2G
If the capability of all neighboring GSM cells does not meet the requirement, the inter-RAT
measurement will not be triggered.
SHIND
The RNC initiates a coverage-based or QoS-based UMTS-to-GSM handover only when Service
Handover Indicator is as follows:
• HO_TO_GSM_SHOULD_BE_PERFORM
• HO_TO_GSM_SHOULD_NOT_BE_PERFORM
The RNC triggers a service-based or load-based UMTS-to-GSM handover only when the Service
Handover Indicator is set to HO_TO_GSM_SHOULD_BE_PERFORM.
The IE Service Handover Indicator indicates the CN policy for the service handover to the GSM
network. This IE is indicated in the Radio Access Bearer (RAB) assignment signaling assigned
by the CN, or provided by the RNC side.
HO_INTER_RAT_RNC_SERVICE_HO_SWITCH under the HoSwitch (BSC6900, BSC6910)
decides whether the service attribute of inter-RAT handover is based on the RNC or the CN.
• If this option is selected, the service attribute of inter-RAT handover is based on the
parameter configured on the RNC side.
• If this option is not selected, 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 the
inter-RAT handover is based on the parameter configured on the RNC side.
Through the SHIND (BSC6900, BSC6910) parameter, the service handover indicators are set as
follows:
• HO_TO_GSM_SHOULD_BE_PERFORM: indicates that the handover to the GSM
network is performed when GSM signals are available.
• HO_TO_GSM_SHOULD_NOT_BE_PERFORM: indicates that the handover to
the GSM network is performed when UMTS signals are weak but GSM signals are
strong.
• HO_TO_GSM_SHALL_NOT_BE_PERFORM: indicates that the handover to the
GSM network is not performed even when UMTS signals are weak but GSM signals
are strong.
By default, the RNC does as follows:
• For a UE with a single signaling RAB, the RNC supports the handover to the GSM,
which 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 CS services, because CS services have 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 PS services with the highest QoS
priority.
If the service handover indicators are not configured by the CN, each indicator 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).
4.11.6 Inter-RAT Load Information Exchange
In a load-based or service-based inter-RAT handover, load information is exchanged between

GSM and UMTS networks to facilitate the inter-RAT handover (WRFD-020310 3G/2G
Common Load Management).
The load status between the source cell and the target cell can be acquired by load information
exchange between a UMTS cell and a GSM cell during the load-based or service-based
handover. Whether to further conduct the handover can be determined to avoid the GSM cell
overload and possible handovers to congested cells.
Load Information Exchange in a UMTS-to-GSM Handover
The procedure for load information exchange between the source UMTS cell and target GSM
cell is described as follows:
1. When the RNC sends a RELOCATION REQUIRED message to the UMTS CN,
• If SndLdInfo2GsmInd (BSC6900, BSC6910) is set to ON, the
RELOCATION REQUIRED message includes the "Old BSS To New
BSS Information" IE that carries the load information of the source UMTS
cell.
• If SndLdInfo2GsmInd (BSC6900, BSC6910) is set to OFF, 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 GSM
CN,
• If NcovHoOn2GldInd (BSC6900, BSC6910) is set to ON, the RNC obtains the load
information of the target GSM cell by reading the "Inter-System Information
Transparent Container" IE, which is included in the RELOCATION COMMAND
message.
▪ If the GSM cell load is lower than the value of CSHOOut2GloadThd
(BSC6900, BSC6910) (for CS service), or if the GSM cell load is lower than
the value of PSHOOut2GloadThd (BSC6900, BSC6910) (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, load information of the target
GSM cell is not considered and this inter-RAT handover is continued.
• If NcovHoOn2GldInd (BSC6900, BSC6910) is set to OFF, the RNC continues the
inter-RAT handover procedure without considering the thresholds.
Load Information Exchange in a GSM-to-UMTS Handover
In a load- or service-based GSM-to-UMTS handover, the RNC can make an admission decision
considering load information of the target UMTS cell. This can avoid worsening of the UMTS
system performance caused by the load- or service-based GSM-to-UMTS handover if the UMTS
system load is high.
The procedure is described as follows:
1. When the RNC sends a RELOCATION REQUEST ACKNOWLEDGE message to
the UMTS CN,
• If SndLdInfo2GsmInd (BSC6900, BSC6910) is set to ON, the
RELOCATION REQUEST ACKNOWLEDGE message includes the
"New BSS To Old BSS Information" IE, which includes load information
of the target UMTS cell.
• If SndLdInfo2GsmInd (BSC6900, BSC6910) is set to OFF, the
RELOCATION REQUEST ACKNOWLEDGE message does not include
the "New BSS To Old BSS Information" IE.
2. Depending on the network requirement, the GSM network decides whether to use the
load information sent to the UMTS network for decision.
3. When the RNC receives the RELOCATION REQUEST message from the UMTS
CN,
• If the UMTS cell is not in the basic congestion state, the RNC continues
the inter-RAT handover procedure.
• If the UMTS 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 Load Control Feature Parameter Description.
4.11.7 Handover of UEs in the Blacklist
Certain UEs may not support inter-frequency or inter-RAT handovers. It is good practice to
blacklist inter-frequency or inter-RAT handovers on unsupported UEs as described in Terminal
Black List Feature Parameter Description.
Handover processing for UEs in the blacklist is as follows:

• Processing of inter-frequency or inter-RAT handovers
Set TAC_FUNC (BSC6900, BSC6910) to Special_User_Enhance and select
INTERHO_DISABLED_SWITCH (for inter-frequency handovers) or
INTRATHO_DISABLED_SWITCH under the SpecUserFunctionSwitch
After the UE blacklist function is enabled, the principles for inter-frequency handovers
and inter-RAT handovers are as follows:
▪ Coverage-based handovers
If a UE has been added to both the inter-frequency blacklist and the inter-
RAT blacklist, the RNC does not send the 2D or 2F measurement control
message. If the UE has been added to either the inter-frequency blacklist or
the inter-RAT blacklist, the RNC sends 2D or 2F measurement control
message. However, after the UE reports 2D measurement result, the RNC
does not send the inter-frequency measurement control message (if the UE
is added to the inter-frequency blacklist) or inter-RAT measurement control
message (if the UE is added to the inter-RAT blacklist).
▪ Load-based handovers, service-based handovers, QoS-based handovers,
HCS-based handovers, and blind handovers
The RNC does not trigger handovers for UEs that are added to the inter-
frequency blacklist or inter-RAT blacklist even if handover conditions are
met.
• Processing of inter-frequency handovers for UEs with only PS BE services
Certain UEs performing only PS BE services may not support inter-frequency
handovers. It is good practice to blacklist inter-frequency handovers on such UEs.
During the setting, set TAC_FUNC (BSC6900, BSC6910) to Special_User_Enhance
and select PSBE_INTERHO_DISABLED_SWITCH under the
SpecUserFunctionSwitch (BSC6900, BSC6910) parameter.
4.11.8 UMTS-to-GSM Handover Success Rate Optimization and Enhanced UMTS-to-GSM Handover Success
Rate Optimization
4.11.8.1 UMTS-to-GSM Handover Success Rate Optimization
The UMTS-to-GSM handover success rate optimization function lowers the probability that the
RNC determines a UMTS-to-GSM handover to a top neighboring GSM cell with a high
handover failure rate, thereby increasing the success rate of UMTS-to-GSM handovers.
The U2GSuccRatioOptSw (BSC6900, BSC6910) parameter specifies whether to enable or
disable this function.
Execution
After the UMTS-to-GSM handover success rate optimization function is enabled, the RNC
performs the following operations to increase the success rate of UMTS-to-GSM handovers.
1. Measures counters related to the number of UMTS-to-GSM handover attempts and
the number of successful UMTS-to-GSM handover attempts.
Related counters are as follows:
• VS.IRATHO.AttOutCS.GCell (BSC6900, BSC6910): measures number of
attempts for CS outgoing inter-RAT handovers according to the neighbor
relationships.
• VS.IRATHO.SuccOutCS.GCell (BSC6900, BSC6910): measures the
number of successful CS inter-RAT outgoing handovers between
neighboring cells.
• VS.IRATHO.AttOutPSUTRAN.GCell (BSC6900, BSC6910): measures the
number of attempts for PS outgoing inter-RAT handovers initiated by the
RNC according to the neighbor relationships.
• VS.IRATHO.SuccOutPSUTRAN.GCell (BSC6900, BSC6910): measures
the number of successful PS inter-RAT outgoing handovers between
neighboring cells.
2. Determines the scenarios where the function can be performed. Specifically, the
RNC removes the items not meeting the optimization conditions after the period of
UMTS-to-GSM handover success rate optimization expires. Table 4-18 lists the
scenarios unavailable for UMTS-to-GSM handover success rate optimization.
Table 4-18 Scenarios unavailable for UMTS-to-GSM handover success rate optimization
Object Scenario (Any Condition Is Met) Description
Source The switch for UMTS-to-GSM handover All handover data on the source
UMTS cell success rate optimization is turned off. UMTS cell within the optimization
period will be cleared.
The frequency or cell ID is changed.
Cell deactivation is performed.
The cell is out of service or re-

established.
The value of the

VS.IRATHO.AttOutCS.GCell counter is
not greater than the threshold for the
number of attempts of inter-RAT CS
handover success rate optimization.
The value of the

VS.IRATHO.AttOutPSUTRAN.GCell
counter is not greater than the threshold
for the number of attempts of inter-RAT
PS handover success rate optimization.
Neighboring Neighboring cells are added within the Handover data of the new neighboring
GSM cell optimization period. cells will not be collected during the
period and the function is not
performed in these cells.
3. Calculates the UMTS-to-GSM handover success rates according to the counter

values obtained in step 2.
UMTS-to-GSM CS handover success rate =
(VS.IRATHO.SuccOutCS.GCell/VS.IRATHO.AttOutCS.GCell) x 100%
UMTS-to-GSM PS handover success rate =
(VS.IRATHO.SuccOutPSUTRAN.GCell/VS.IRATHO.AttOutPSUTRAN.GCell) x
100%
4. Determines the handover grade of each neighboring GSM cell separately for CS and
PS services according to Table 4-19.
The handover probability varies with handover grades. The handover probabilities corresponding to
handover grades are as follows:
• Handover grade 0: 100%
Table 4-19 Determining the handover grade of each neighboring GSM cell by checking the
UMTS-to-GSM handover success rate
Handover Grade Handover Success Rate
Grade 0 (Threshold for the UMTS-to-GSM handover success rate of

handover grade 0, 100%]

handover grade 1, Threshold for the UMTS-to-GSM handover
success rate of handover grade 0]

handover grade 2, Threshold for the UMTS-to-GSM handover
success rate of handover grade 1]
Grade 3 [0%, Threshold for the UMTS-to-GSM handover success rate of

handover grade 2]
After the optimization period expires, the RNC clears the timer, removes all collected
data, and restarts the timer for the next optimization period.
5. Generates optimization suggestions corresponding to the handover grade and
automatically delivers instructions to change the handover grade of the neighboring
cell.
If the RNC CPU usage is high (specifically, greater than the minimum value among SMPAGERTHD
(BSC6900, BSC6910), SLPAGERTHD, and CPAGERTHD (BSC6900, BSC6910)) when
optimization suggestions are generated, the RNC starts flow control, instead of delivering instructions
to activate the function of UMTS-to-GSM handover success rate optimization.
6. Determines whether to perform a UMTS-to-GSM handover based on the handover

grade.
Upon receiving an event 3A report or inter-RAT periodic measurement report from a
UE, the RNC determines whether all measurement quantities meet the requirements.
For details, see 4.3.4.2 Inter-RAT Handovers. If the conditions for handover decision are
met, the RNC determines whether to initiate an inter-RAT handover to a neighboring
GSM cell according to the handover probability corresponding to the handover grade
of the neighboring GSM cell.
Specifically, during the handover decision, the RNC generates a random number
between 1 and 100. The RNC decides to initiate a handover to a neighboring GSM
cell only when the number corresponding to the handover probability of the
neighboring GSM cell is less than or equal to the random number. For example, if the
handover probability of a neighboring GSM cell is 70%, the RNC initiates a
handover to the cell only when the generated random number is within the range of 1
to 70.
The handover probabilities corresponding to handover grades are as follows:
The RNC determines the handover grade of a neighboring cell in compliance with
the following principles:
• If the best cell is served by the DRNC, this function does not take effect
and the handover grade is not considered in the handover decision.
• If the determined target neighboring GSM cell is configured as the
neighboring cell of two or three cells in the active set, it uses the handover
grade of the cell with the best signal quality.
• During a compressed mode procedure, if a UE sends multiple
measurement reports where both the service type and best cell remain
unchanged, the neighboring GSM cell uses the handover grade reported in
the first measurement report.
• If the CS domain is available, the handover grade of the inter-RAT CS
handover is used. If only the PS domain is available, the handover grade of
the inter-RAT PS handover is used.
• If RNC in Pool Load Sharing is enabled on the control plane, this function only takes effect on the
master RNC by default. You can set U2GSROptSwforOverflowRNC (BSC6900, BSC6910) to ON
to make this function take effect on the overflow RNC.
• After the function of UMTS-to-GSM handover success rate optimization is disabled, handover grades
of inter-RAT neighboring cells will be saved, rather than be cleared, so that they can be directly used
next time when this function is enabled.
• After the function of UMTS-to-GSM handover success rate optimization is enabled, the inter-RAT
handovers may decrease and UEs cannot be promptly handed over to GSM. In this case, UEs may
experience service drops or shift to a UMTS cell through an inter-frequency handover. Consequently,
there is a probability that the service drop rate increases and the success rate of inter-frequency
handovers decrease.
Parameters Related to UMTS-to-GSM Handover Success Rate Optimization
describes parameters related to the function of UMTS-to-GSM handover success rate

Table 4-20
optimization.
Table 4-20 Parameters related to the function of UMTS-to-GSM handover success rate optimization
Parameter Parameter ID MML Command Description

Name
U2G U2GSuccRatioOptPrd SET UHHONCELLPAOPT Inter-RAT handover

Success (BSC6900, BSC6910) success rate
Ratio Opt optimization period.
Period
CS U2G U2GSuccRatioOptCSHoThld ADD Threshold of the

Att (BSC6900, BSC6910) UCELLHHONCELLPAOPT number of inter-RAT
Threshold CS handover attempts
for Succ from a cell to be
Ratio Opt optimized to all
configured neighboring
cells, which is used to
determine whether to
enable inter-RAT
handover success rate
optimization.
PS U2G U2GSuccRatioOptPSHoThld ADD Threshold of the

Att (BSC6900, BSC6910) UCELLHHONCELLPAOPT number of inter-RAT
Threshold PS handover attempts
Name
for Succ from a cell to be

Ratio Opt optimized to all
configured neighboring
cells, which is used to
determine whether to
enable inter-RAT
handover success rate
optimization.
U2G U2GSuccThdForHoGrade0 ADD UMTS-to-GSM

Success (BSC6900, BSC6910) UCELLHHONCELLPAOPT handover success rate
Ratio threshold for handover
Thld for grade 0 of a
HO neighboring GSM cell.
Grade 0

Grade 1

Grade 2
4.11.8.2 Enhanced UMTS-to-GSM Handover Success Rate Optimization
This function enhances the handover decision method for the UMTS-to-GSM handover success
rate optimization function. During the handover grade-based UMTS-to-GSM handover decision,
the RNC determines whether the signal quality in the current measurement report meets
requirements. If the signal quality meets requirements, the RNC determines the handover grade.
The mechanism of this function is similar to that of UMTS-to-GSM handover success rate
optimization. After the optimization period specified by U2GSuccRatioOptPrd (BSC6900,
BSC6910) expires, the RNC calculates the UMTS-to-GSM handover success rate between every
two cells, and determines the CIOOffset adjustment value and handover grade accordingly:
1. The CIOOffset adjustment value is determined through the following scheme:
• When the handover success rate in this period is greater than that of the
last period, the RNC obtains the CIOOffset adjustment value based on the
mapping relationship listed in Table 4-21 (the CIOOffset adjustment value is
determined for CS and PS services separately), and then determines
whether to allow the inter-RAT handover.
• When the handover success rate in this period is lower than that of the last
period by 1% or less, the RNC uses the CIOOffset value in the last period
to determine whether to allow the inter-RAT handover.
• When the handover success rate in this period is lower than that of the last
period by over 1%, the RNC uses the CIOOffset adjustment value in the
historical period with the highest handover success rate to determine
whether to allow the inter-RAT handover.
2. If the signals meet quality requirements after the RNC adjusts the CIOOffset value,
the RNC determines the handover grade in the next period according to Table 4-21.
Table 4-21 CIOOffset adjustment value and handover grade for every two cells
Range of Inter-RAT Handover Success CIOOffset Adjustment Value Handover Grade
Rate
[Target threshold for the inter-RAT If CIOOffset is equal to or less Grade 0

handover, 100%] than -3, the CIOOffset adjustment
value is +1 dB.
If CIOOffset is greater than -3, the
CIOOffset adjustment value is 0.
[Inter-RAT handover success rate The CIOOffset adjustment value Grade 0

threshold 1, Target threshold of the is –1 dB.
inter-RAT handover]

threshold 2, Inter-RAT handover is –1 dB.
success rate threshold 1]

threshold 3, Inter-RAT handover is –1 dB.
success rate threshold 2]
[0%, Inter-RAT handover success The CIOOffset adjustment value Grade 3

rate threshold 3] is –1 dB.
The handover probability varies with handover grades. The handover probabilities corresponding to handover grades
are as follows:
This function is controlled by U2GSuccRatioOptEnhSw (BSC6900, BSC6910).

• When this function takes effect, the UMTS-to-GSM handover success rate optimization function does
not take effect.
• This function takes effect only in the scenario where the inter-RAT handover measurement report mode
is set to periodic report mode (that is, InterRatReportMode (BSC6900, BSC6910) is set to
PERIODICAL_REPORTING).
• When the UMTS-to-GSM handover success rate is already high (for example, higher than 98%),
CIOOffset adjustment for optimizing the neighboring GSM cell selection may bring unnoticeable gains
to the handover success rate. Therefore, this function is not recommended in this scenario.
• Activation of this function may decrease the number of inter-RAT handovers. In this case, the UE may
fail to be promptly handed over to GSM, and then the UE may experience call drops or perform inter-
frequency handovers on the UMTS side, causing an increase in call drops and a decrease in the inter-
frequency handover success rate.
• When this function is enabled, the adjustment is performed after a learning period. There are several
periods of adjustment. It is estimated that stable gains can be observed after five to ten periods.
• If the handover grades of two cells and the CIOOffset incremental value are configured in the MML
configuration file, the configured values are used after this function is enabled.
Parameters Related to Enhanced UMTS-to-GSM Handover Success Rate Optimization
Table 4-22describes parameters related to the function of enhanced UMTS-to-GSM handover

success rate optimization.
Table 4-22 Parameters related to the function of enhanced UMTS-to-GSM handover success rate
optimization (a)

Name
IRAT HO U2GSuccRatioOptEnhSw ADD/MOD Whether

Success (BSC6900, BSC6910) UCELLHHONCELLPAOPT enhanced inter-
Ratio Opt RAT handover
Enhancement success rate
Switch optimization takes
effect.
U2G U2GsuccRateOptCSTrgtThld ADD/MOD Target threshold

Handover (BSC6900, BSC6910)(b) UCELLHHONCELLPAOPT for optimizing the
Target UMTS-to-GSM
Threshold for handover success
CS Domain rate in the CS
domain.
U2G U2GSuccRateOptPSTrgtThld ADD/MOD Target threshold

Handover (BSC6900, BSC6910)(b) UCELLHHONCELLPAOPT for optimizing the
Target UMTS-to-GSM
Threshold for handover success
PS Domain rate in the PS
domain.
Increment CSCIOOffsetDelta (BSC6900, ADD/MOD U2GNCELL CS cell individual
Value of BSC6910)(c) offset (CIO)
CIOOffset for increment
CS Domain oriented to
neighboring cells.
Increment PSCIOOffsetDelta (BSC6900, ADD/MOD U2GNCELL PS cell individual

Value of BSC6910)(c) offset (CIO)
CIOOffset for increment
PS Domain oriented to
neighboring cells.
(a): The parameters related to this function, such as the optimization period, threshold for the number of attempts of
enhanced UMTS-to-GSM handover success rate optimization in the CS domain, and threshold for the number of
attempts of enhanced UMTS-to-GSM handover success rate optimization in the PS domain, inherit the settings of
the UMTS-to-GSM handover success rate optimization. That is, the U2GsuccRatioOptPrd (BSC6900,
BSC6910) parameter specifies the optimization period of the enhanced UMTS-to-GSM handover success rate
optimization, the U2GSuccRatioOptCSHoThld (BSC6900, BSC6910) parameter specifies the threshold of the
number of attempts of enhanced UMTS-to-GSM handover success rate optimization in the CS domain, and the
U2GSuccRatioOptPSHoThld (BSC6900, BSC6910) parameter specifies the threshold of the number of attempts
of enhanced UMTS-to-GSM handover success rate optimization in the PS domain.
(b): When you configure this parameter, it is good practice to refer to the parameter settings of the UMTS-to-GSM
handover success rate optimization before enabling this function to avoid a too large or too small value. If this
parameter is set to a too large value, handovers between a large number of cells with high handover success rates
may be restricted, resulting in an abnormal increase of the call drop rate. If this parameter is set to a too small value,
the gains provided by this function may be insignificant.
(c): The value of this parameter is calculated by this function and manual reconfiguration is not recommended. If
this parameter must be reconfigured, contact Huawei engineers.
4.11.9 Inter-Frequency Handover Success Rate Optimization
The inter-frequency handover success rate optimization function automatically reconfigures the
CIOOFFSET (BSC6900, BSC6910) parameter to enable UEs to shift to neighboring cells with
high inter-frequency handover success rates as much as possible during the inter-frequency
handover, increasing the success rate of inter-frequency handovers. The
IFHOSuccRateOptSW (BSC6900, BSC6910) parameter specifies whether to enable this
function.
Execution
After the inter-frequency handover success rate optimization function is enabled, the RNC
performs the following operations to increase the success rate of inter-frequency handovers.
1. Measures counters related to the number of inter-frequency handover attempts and
the number of successful inter-frequency handovers.
Related counters are as follows:
Number of Measurement-based Inter-Frequency Hard Handover Attempts Between
Two Cells: VS.HHO.AttInterFreqOut.Meas.NCell (BSC6900, BSC6910)
Number of Successful Measurement-based Inter-Frequency Hard Handovers
Between Two Cells: VS.HHO.SuccInterFreqOut.Meas.NCell (BSC6900, BSC6910)
2. Determines the scenarios where the function can be performed. Specifically, the
RNC removes the items not meeting the optimization conditions after the period of
inter-frequency handover success rate optimization expires. Table 4-23 lists the
scenarios unavailable for inter-frequency handover success rate optimization.
Table 4-23 Scenarios unavailable for inter-frequency handover success rate optimization
Source The switch for inter-frequency handover All handover data on the source
UMTS cell success rate optimization is turned off. UMTS cell within the
optimization period will be
The frequency or cell ID is changed. cleared.
Cell deactivation is performed.
The cell is out of service or re-established.
The number of measurement-based inter-

frequency hard handover attempts is not
greater than the value of the IFHO Att
Threshold for Success Rate Opt parameter.
Neighboring Neighboring cells are added within the Handover data of the new
cell optimization period. neighboring cells will not be
collected during the period and
the function is not performed in
these cells.
3. Calculates the success rate of measurement-based inter-frequency handovers

according to the counter values obtained in step 1.
Success rate of measurement-based inter-frequency hard handovers =
VS.HHO.SuccInterFreqOut.Meas.NCell (BSC6900,
BSC6910)/VS.HHO.AttInterFreqOut.Meas.NCell (BSC6900, BSC6910) x 100%
4. Automatically reconfigures the CIOOFFSET (BSC6900, BSC6910) parameter

according to the obtained inter-frequency hard handover success rate. Table 4-24
describes the policy for the parameter reconfiguration.
Table 4-24 CIOOFFSET (BSC6900, BSC6910) parameter reconfiguration policy
Range of Inter-frequency Hard Handover Adjusted Value for the CIOOFFSET (BSC6900,
Success Rate BSC6910) Parameter
[IFHO Success Rate Threshold 1, 100%] Incremental value 0 of the CIO of neighboring
cells
If the value of the CIOOFFSET (BSC6900,
BSC6910) parameter is greater than or equal to
–3, the CIOOffset Delta 0 parameter setting
takes effect and the RNC adjusts the
CIOOFFSET (BSC6900, BSC6910) parameter
value by an amount indicated by CIOOffset
Delta 0. If the value is less than –3, the
CIOOffset Delta 0 parameter setting does not
take effect and the CIOOFFSET (BSC6900,
BSC6910) parameter value remains unchanged.
[IFHO Success Rate Threshold 2, IFHO Incremental value 1 of the CIO of neighboring
Success Rate Threshold 1] cells
[IFHO Success Rate Threshold 3, IFHO Incremental value 2 of the CIO of neighboring
Success Rate Threshold 2] cells
[0%, IFHO Success Rate Threshold 3] Incremental value 3 of the CIO of neighboring
cells
After the optimization period expires, the RNC clears the timer, removes all collected
data, and restarts the timer for the next optimization period.
• If RNC in Pool Load Sharing is enabled on the control plane, this function only takes effect on the
master RNC, but not on the overflow RNC.
• After this function takes effect, attempts of inter-frequency handovers may decrease and UEs may fail
to promptly perform inter-frequency handovers. In this case, UEs may experience service drops or
attempt to perform an inter-frequency handover. As a result, service drop rates may increase and inter-
RAT handover attempts may increase.
• During the CIOOFFSET (BSC6900, BSC6910) parameter reconfiguration, if the RNC CPU usage is
high (specifically, greater than the minimum value among SMPAGERTHD (BSC6900, BSC6910),
SLPAGERTHD (BSC6900, BSC6910), and CPAGERTHD (BSC6900, BSC6910)), the RNC starts
flow control, instead of activating the function of inter-frequency handover success rate optimization.
Parameters Related to Inter-Frequency Handover Success Rate Optimization
describes parameters related to the function of inter-frequency handover success rate

Table 4-25
optimization.
Table 4-25 Parameters related to the function of inter-frequency handover success rate optimization
Name
Inter-Freq IFHOSuccRateOptSW ADD Switch for inter-

Handover (BSC6900, BSC6910) UCELLHHONCELLPAOPT frequency handover
Success MOD success rate
Rate Opt UCELLHHONCELLPAOPT optimization.
Switch
IFHO IFHOSuccRateOptPrd SET UHHONCELLPAOPT Execution period for

Success (BSC6900, BSC6910) inter-frequency handover
Rate Opt success rate
Period optimization.
IFHO Att IFHOSuccRateOptAttThld ADD Threshold for the number

Threshold (BSC6900, BSC6910) UCELLHHONCELLPAOPT of handover attempts
for MOD from a cell to be
Success UCELLHHONCELLPAOPT optimized to an inter-
Rate Opt frequency neighboring
cell during inter-
frequency handover
success rate
optimization.
IFHO IFHOSuccRateThd1 ADD Threshold 1 for the

Success (BSC6900, BSC6910) UCELLHHONCELLPAOPT success rate of inter-
Rate MOD frequency handovers
Threshold UCELLHHONCELLPAOPT between two cells.
1

2

3
CIOOffset CIOOffsetDelta0 (BSC6900, ADD Incremental value 0 of

Delta 0 BSC6910) UCELLHHONCELLPAOPT CIOOffset.
MOD
UCELLHHONCELLPAOPT

MOD
UCELLHHONCELLPAOPT
Name

MOD
UCELLHHONCELLPAOPT

MOD
UCELLHHONCELLPAOPT
5 HSPA Handover
5.1 HSDPA Handover
This section describes the WRFD-01061006 HSDPA Mobility Management feature.

5.1.1 HSDPA Intra-Frequency Handover
This section describes decision and execution of intra-frequency handovers, and handovers
between a cell that supports the F-DPCH and a cell that does not support the F-DPCH after the
introduction of HSDPA.
Handling of Event 1A
After receiving an event 1A report, the RNC adds the cell to the active set if the number of cells
in the active set does not reach the upper limit.
If the function Intra-Frequency Handover Decision and Execution Triggered by Event 1A that Serves as a
Substitute for Event 1C is enabled, the RNC, upon receiving an event 1A report, determines whether
to add or replace cells in the active set according to the rules described in the following table.
If... Then...
The best cell in the active set The RNC reconfigures the best cell as the HSDPA serving cell
supports HSDPA services and then replaces the cell in the active set.
If the reconfiguration fails, the RNC reconfigures the HSDPA
service on the DPCH and replaces the cell in the active set.
If... Then...
The best cell in the active set The RNC reconfigures the HSDPA service on the DPCH and
does not support HSDPA then replaces the cell in the active set.
services
Handling of Event 1B
After receiving an event 1B report, the RNC determines whether to remove a cell.
• If the cell to be removed is not an HSDPA serving cell, the RNC directly removes the
cell.
• If the cell to be removed is an HSDPA serving cell, the RNC makes the following
decision and removes the cell from the active set.
▪ If the new best cell supports HSDPA services, the RNC reconfigures the
new best cell as an HSDPA serving cell. If the reconfiguration fails, the
RNC reconfigures the HSDPA service on the DPCH.
▪ If the new best cell does not support HSDPA services, the RNC
reconfigures the HSDPA service on the DPCH to ensure service continuity.
Handling of Event 1C
After receiving an event 1C report, the RNC determines whether to replace the worst cell.
• If the cell to be replaced is not an HSDPA serving cell, the RNC directly replaces the
cell.
• If the cell to be replaced is an HSDPA serving cell, then:
▪ If the best cell supports HSDPA services, the RNC reconfigures the best
cell as an HSDPA serving cell. If the reconfiguration fails, the RNC
reconfigures the HSDPA service on the DPCH.
▪ If the best cell does not support HSDPA services, the RNC reconfigures the
HSDPA service on the DPCH to ensure service continuity.
Handling of Event 1D
After receiving an event 1D report, the RNC proceeds as follows:

• If the downlink service is carried over HSDPA, then:
▪ If the cell, where event 1D is reported, supports HSDPA services and the
HSPA handover protection timer (specified by HspaTimerLen (BSC6900,
BSC6910)) expires, the RNC reconfigures the cell as an HSDPA serving cell.
▪ If the cell, where event 1D is reported, does not support HSDPA services,
the RNC reconfigures the downlink service on the DPCH.
shows an example of how to handle event 1D. Assume that the UE
Figure 5-1
moves from HSDPA cell 1 to HSDPA cell 2, the two cells are intra-
frequency neighboring cells, and all the cells in the active set support
HSDPA services. The RNC updates the HSDPA serving cell according to
the MR and keeps the HSDPA serving cell as the best cell.
Figure 5-1 Intra-frequency handover between HSDPA cells when the best cell changes
• If the downlink service is carried on the DCH, the UE is handed over to the target cell,
and the service is carried on the DCH. After the handover, the RNC may retry to
configure the service on the HS-DSCH. For details, see 5.5 HSPA Handover Retry.
In the execution procedure mentioned above,
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH under the CmpSwitch
(BSC6900, BSC6910) parameter determines whether the update of the active set and the
change of the serving cell are synchronized. This switch is applicable only to UEs
complying with 3GPP Release 6.
▪ If this switch is turned on, the RNC simultaneously performs active set
update and serving cell change.
▪ If this switch is turned off, the UE completes serving cell change through a
PHYSICAL CHANNEL RECONFIGURATION message after active set
update.
The NBMMachsResetAlgoSelSwitch (BSC6900, BSC6910) parameter specifies whether to
reset the UE MAC-hs during the HSDPA serving cell change.
RAN16.0 introduces the fast HSDPA serving cell change function, which is implemented during
an HSDPA intra-frequency handover. For details about the fast HSDPA serving cell change
function, see Procedure Optimization Feature Parameter Description.
RAN18.1 introduces the optimized HSDPA serving cell change function, which is controlled by
the HSDPASERCELLCHOPTSW parameter. In the scenario where internal procedures in the HSDPA
serving cell change coincide, the data transmission policy is optimized. Specifically, the time for
removing the old link is adjusted to increase the user throughput.
When there is a large amount of data exchanged on the network, this function provides the
following benefits:
• Increased HSDPA user throughput in the HSDPA serving cell change process, as
indicated by VS.HSDPA.MeanChThroughput (BSC6900, BSC6910)
• Decreased downlink HSDPA service retransmission rate at the RLC layer
HSDPA service retransmission rate = VS.AM.RLC.Rtx.HsdpaTrf.PDU (BSC6900,

BSC6910)/VS.RLC.AM.Tx.HsdpaTrf.PDU (BSC6900, BSC6910)
Handling of HSDPA Serving Cell Uplink Out-Of-Synchronization
When the HSDPA serving cell experiences uplink out-of-synchronization, serving cell change is
triggered and the serving link is removed if the link restoration timer specified by RlRstrTmr
(BSC6900, BSC6910) expires.
PERFENH_UL_RL_FAIL_SRV_CELL_CHG_SWITCH under the PerfEnhanceSwitch3
(BSC6900, BSC6910) parameter in the SET UCORRMPARA command specifies whether a
serving cell change to a target HSDPA cell that is in the uplink out-of-synchronization state is
allowed.
• When the switch is turned on, the cell change is prohibited.
• When the switch is turned off, the cell change is allowed.
5.1.2 HSDPA Inter-Frequency Handover
The inter-frequency handover can be triggered on the basis of coverage, load, service, and
hierarchical cell structure (HCS).
The following describes the three possible scenarios where an inter-frequency handover occurs.
Scenario 1: Inter-Frequency Handover from an HSDPA Cell to an R99 Cell
As shown in Figure 5-2, when the UE moves from cell 1 (an HSDPA cell) to cell 2 (an inter-
frequency R99 cell) and the inter-frequency handover conditions are met, the RNC makes a
handover decision for HSDPA services according to the neighboring cell measurement report,
and reconfigures the service on the DPCH of cell 2.
Figure 5-2 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 5-3, when the UE moves from cell 2 (an R99 cell) to cell 1 (an inter-frequency
HSDPA cell) and the inter-frequency handover conditions are met, the RNC hands over the UE
to the DPCH of cell 1 and then reconfigures the service on the HS-PDSCH.
Figure 5-3 Inter-frequency handover from an R99 cell to an HSDPA cell
Scenario 3: Inter-Frequency Handover Between HSDPA Cells
As shown in Figure 5-4, 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 RNC hands over the UE from cell
1 to cell 2. The target cell becomes the new serving cell.
If the serving or target cell is in load congestion when the UE performs a serving cell update
during an inter-frequency or inter-RAT handover, the service is reconfigured from the HS-
PDSCH to the DPCH.
Implementation in hard handovers of an HSDPA cell is the same as that of an R99 cell.
Figure 5-4 Inter-frequency handover between HSDPA cells
5.1.3 HSDPA Inter-RAT Handover
When a UE is handed over to a cell that supports the F-DPCH from another system and event 4A
is reported in the uplink or downlink, the RNC decides whether to change the bearer mode of
TRBs and SRBs.
If the TPC command is carried on the F-DPCH between the UE and the UTRAN, the SRBs and
TRBs are carried on the HS-DSCH. If a cell that does not support the F-DPCH is added to the
active set, all the F-DPCHs will be deleted. In addition, new DPCHs between the UE and all the
cells in the active set are set up to carry the SRBs and TPC commands.
5.2 HSUPA Handover
This section describes the WRFD-01061204 HSUPA Mobility Management feature.

If the handover is an inter-RNC HSUPA handover, see description about HSUPA over Iur in
HSUPA Feature Parameter Description and determine whether corresponding configuration is required.
5.2.1 HSUPA Intra-Frequency Handover
This section describes the decision and execution procedure for HSUPA intra-frequency
handovers. For details about intra-frequency handover of DC-HSUPA UEs, see DC-HSUPA Feature
Handling of Event 1A
If the number of cells in the active set does not reach the maximum value when the RNC
receives an event 1A report, the RNC adds the cell to the active set according to the following
rules.
If... Then...
The number of cells in the E-DCH active set is The RNC adds the target cell to the DCH
less than the value of active set and E-DCH active set.
MaxEdchCellInActiveSet (BSC6900, BSC6910)
If... Then...
The number of cells in the E-DCH active set is The RNC adds the target cell to the DCH
equal to the value of active set.
MaxEdchCellInActiveSet (BSC6900, BSC6910)
If the function Intra-Frequency Handover Decision and Execution Triggered by Event 1A that Serves as a
Substitute for Event 1C is enabled, the RNC, upon receiving an event 1A report, operates as follows:
• Initiates replacement of cells in the active set and adds the cell to the DCH active set
when the target cell does not support HSUPA services.
• Adds the cell to the active set according to the rules described in the following table
when the target cell supports HSUPA services.
If... Then...
The number of cells in the E-DCH active set is The RNC initiates replacement of cells in the
equal to the value of active set and adds this cell to the DCH active
MaxEdchCellInActiveSet (BSC6900, BSC6910) set and E-DCH active set.
and the cell to be replaced is in the E-DCH
active set
The number of cells in the E-DCH active set is The RNC initiates replacement of cells in the
equal to the value of active set and adds this cell to the DCH active
MaxEdchCellInActiveSet (BSC6900, BSC6910) set.
and the cell to be replaced is not in the E-DCH
active set
Handling of Event 1B
If the number of radio links in the DCH active set is greater 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 and CS services are not carried
over HSPA, 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 cell to be removed is an HSUPA serving cell and CS services are carried over
HSPA, 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
reconfigured from CS Voice over HSPA to CS Voice over DCH. 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.
The RNC-level parameter CSVoiceoverHSPASuppInd (BSC6900, BSC6910) specifies whether
the cells under the adjacent RNC support CS Voice over HSPA.
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 that 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
After receiving the event 1C measurement report, the RNC proceeds as follows:
• If the new cell supports HSUPA, then:
▪ If the number of cells in the E-DCH active set is less than the value of
MaxEdchCellInActiveSet (BSC6900, BSC6910), the RNC adds the new
cell to the E-DCH active set.
▪ If the number of cells in the E-DCH active set is equal to the value of
MaxEdchCellInActiveSet (BSC6900, BSC6910) and the cell to be replaced
is also in the E-DCH active set, the RNC adds the new cell to the E-DCH
active set to replace the cell to be replaced.
▪ If the number of cells in the E-DCH active set is equal to the value of
MaxEdchCellInActiveSet (BSC6900, BSC6910) and the cell to be replaced
is not in the E-DCH active set, the RNC adds the new cell to the DCH
active set.
• If the new cell does not support HSUPA, the cell is added to only the DCH active set.
If CS services are carried over HSPA and the cell to be removed is an E-DCH serving cell:
• 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
reconfigured from CS Voice over HSPA to CS Voice over DCH. 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. Therefore, a new
E-DCH serving cell and a new 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.
Handling of Event 1D
If the criteria for intra-frequency soft handovers are fulfilled, the RNC performs an intra-
frequency soft handover after receiving the event 1D report. If the criteria for intra-frequency
soft handovers are not fulfilled, the RNC performs an intra-frequency hard handover based on
the measurement report.
If the uplink service is carried on the E-DCH, then:
• If the new best cell in the active set supports HSUPA, and the handover penalty timer
for HSPA services expires, the RNC reconfigures the E-DCH serving cell as the best
cell. The RNC restarts this timer after an HSUPA serving cell change. The length of
the timer is specified by the HspaTimerLen (BSC6900, BSC6910) parameter.
• If the new best cell in the active set does not support HSUPA, 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 DCH.
If the uplink service is carried on the DCH, the uplink service is still carried on the DCH. After
the handover is completed, the RNC may retry to configure the service on the E-DCH. For
details, see 5.5 HSPA Handover Retry.
If CS services are carried over HSPA and the new best cell supports both HSUPA and HSDPA,
the cell is reconfigured to be an HSPA serving cell. Otherwise, the services are reconfigured
from HSPA to the DCH.
Triggering of Event 1J
Event 1J is triggered to reconfigure services from the DCH to the E-DCH if the following
inequality is true and lasts for a period of time specified by TrigTime1J (BSC6900, BSC6910):
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 for event 1J and is determined by the Hystfor1J (BSC6900,
BSC6910) parameter.
Figure 5-5 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 5-5, the hysteresis and the cell individual offsets for all cells equal 0.
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.
If the RNC does not process the reported event 1J, the UE periodically reports event 1J at an
interval specified by ReportIntervalfor1J (BSC6900, BSC6910). When the number of reported
events 1J reaches the value specified by PeriodMRReportNumfor1J (BSC6900, BSC6910), the
UE stops reporting.
HO_INTRA_FREQ_RPRT_1J_SWITCH under the HoSwitch (BSC6900, BSC6910) parameter
specifies the measurement control switch for event 1J. If this option is selected, event 1J is
included in the intra-frequency measurement control message when the UE complies with 3GPP
Release 6.
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.
After a UE reports event 1J to the RNC, the RNC may miss the measurement reports. If the
event at an interval specified by ReportIntervalfor1J (BSC6900, BSC6910) to avoid missing of
PeriodMRReportNumfor1J (BSC6900, BSC6910), the UE stops periodic reporting.
Handling of Event 1J
Event 1J provides the solution to the issue of how to add an HSUPA cell in a DCH active set to
an E-DCH active set. This event is triggered when a non-active E-DCH but active DCH primary
CPICH becomes better than an active E-DCH primary CPICH.
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 event 1J report, the RNC proceeds as follows:
• If the current number of cells in the E-DCH active set is less than the value of
MaxEdchCellInActiveSet (BSC6900, BSC6910), the RNC reconfigures the cell
where event 1J is triggered to E-DCH.
• If the current number of cells in the E-DCH active set is equal to the value of
MaxEdchCellInActiveSet (BSC6900, BSC6910), the RNC searches the measurement
report for the non-serving E-DCH cell with the lowest measured quality in the E-DCH
active set. Then, 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.
Handling of HSUPA Serving Cell Uplink Out-Of-Synchronization
If experiencing uplink out-of-synchronization, the HSUPA serving cell is changed and its
serving link is removed when the link restoration timer specified by RlRstrTmr (BSC6900,
BSC6910) expires.
PERFENH_UL_RL_FAIL_SRV_CELL_CHG_SWITCH under the PerfEnhanceSwitch3

(BSC6900, BSC6910) parameter in the SET UCORRMPARA command specifies whether a cell
change to the HSUPA target cell is allowed if the HSUPA target cell is in the uplink out-of-
synchronization state.
• When the switch is turned on, the cell change is prohibited.
• When the switch is turned off, the cell change is allowed.
5.2.2 HSUPA Inter-Frequency Handover
Inter-frequency handovers can be triggered on the basis of coverage, load, service, and HCS. The
introduction of HSUPA does not affect decision and execution of these types of inter-frequency
handover.
During the execution phase, whether to reconfigure the services from E-DCH to DCH depends
on the HSUPA capability of the target cell. There are three scenarios for inter-frequency
handovers, which are described as follows.
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.
CSVoiceOverHspaSuppInd (BSC6900, BSC6910) specifies whether the target RNC supports
CS Voice over HSPA during an inter-RNC handover.
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 5-6.
Figure 5-6 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 on 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 5-7.
Figure 5-7 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. If the request is accepted, the RB
reconfiguration is implemented, and the services on the E-DCH are reconfigured on the DCH.
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 5-8.
Figure 5-8 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. If the
request is accepted, the RB reconfiguration is implemented, and the services are reconfigured
from the DCH to the E-DCH.
5.2.3 HSUPA Inter-RAT Handover
When the CS service is carried over HSPA and the UE is handed over from a GSM cell to a
UMTS cell,
• If the UE and the target UMTS RAN support CS Voice Over HSPA, the service is
configured as CS Voice over HSPA during the handover.
• Otherwise, the service is configured as CS Voice over DCH during the handover.
5.3 HSPA+ Handover
5.3.1 Overview
The basic mechanisms of handover remain unchanged after the introduction of HSPA+. New
functions are added to handle handovers in either of the following scenarios:
• The source cell and target cell support different HSPA+ technologies.
• Admission control prevents the UE from using the preferred technologies.
CellCapContainerFdd (BSC6900, BSC6910) specifies whether the neighboring cell supports
HSPA+.
Figure 5-9 shows the procedure of HSPA+ technology configuration.
Figure 5-9 Procedure of HSPA+ technology configuration
5.3.2 Preselection Phase
HSPA+ technologies are preselected in the preselection phase (during handover decision).
During intra- and inter-frequency hard handovers, for DC-MIMO, DC-HSUPA, DC-HSDPA,
MIMO+64QAM, MIMO, 64QAM, downlink enhanced L2, HS-SCCH Less Operation, 16QAM,
uplink enhanced L2, and DTX/DRX, the RNC preselects the HSPA+ technologies that are
supported by both the source cell and target cell and have been used in the source cell.
During intra-frequency soft handovers, for uplink 16QAM, uplink enhanced L2, and DTX/DRX,
the preselection schemes are as follows:
• The RNC preselects HSPA+ if both of the following conditions are met:
▪ All the cells in the active set support the technologies.
▪ The target cell supports the technologies.
• Otherwise, the RNC does not preselect them.
5.3.3 Fallback Phase
HSPA+ technologies with lower ranking are selected in the fallback phase (during handover
execution).
In this phase, the RNC performs admission control based on the preselected technologies. If the
admission is unsuccessful, the RNC selects DCH to carry services.
5.3.4 Retry Phase
In the retry phase, if both the UE and the network meet the requirements for configuring higher-
ranked HSPA+ technologies, the RNC attempts to apply them. The RetryCapability (BSC6900,
BSC6910) parameter specifies the HSPA+ technologies that can be retried. Such technologies may
not be pre-selected in the preselection phase or fail to be applied in the fallback phase. For
example, the RNC attempts to use DC-HSDPA instead of SC-HSDPA.
The retry procedure is as follows:
1. The RNC starts the handover protection timer specified by the
ChannelRetryHoTimerLen (BSC6900, BSC6910) parameter.
2. After the timer expires, the RNC attempts to apply higher-ranked HSPA+
technologies.
3. If the retry fails, the RNC starts the retry timer specified by the
ChannelRetryTimerLen (BSC6900, BSC6910) parameter for periodic retry attempts.
5.4 Anti-Frequent Serving Cell Change
HSPA serving cell change is usually triggered by event 1D. To avoid frequent serving cell
change that may affect the system performance, a protection timer specified by the
HspaTimerLen (BSC6900, BSC6910) parameter is introduced. This timer is started when the
serving HS-DSCH cell changes or the E-DCH serving cell changes. In addition, no more 1D-
triggered serving cell change is performed until the timer expires. However, this timer does 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 cannot be started and serving cell
change must be initiated immediately.
5.5 HSPA Handover Retry
If a UE has a HSDPA/HSUPA suitable service, the RNC tries to reconfigure the service onto the
HS-DSCH/E-DCH as soon as possible.
After handover or radio bearer setup, the HSDPA/HSUPA suitable service may be set up on the
DCH or FACH in a cell. If the cell is capable of HSPA or the cell has an HSPA-capable
neighboring cell, the RNC retries to configure the service on the HS-DSCH/E-DCH in this cell
or in its neighboring cell.
To avoid frequent handovers at the boundary between an HSPA cell and an R99 cell, a
protection timer specified by the ChannelRetryTimerLen (BSC6900, BSC6910) parameter is
introduced. After a handover, the timer starts. After this timer expires, the RNC retries to
configure the service of the UE onto the HS-DSCH or E-DCH if either of the following two
conditions is met:
• The target cell supports HSDPA or HSUPA.
• The target cell does not support HSDPA or HSUPA but has a DRD neighboring cell.
If the admission fails during the reconfiguration, the timer specified by the
ChannelRetryTimerLen (BSC6900, BSC6910) parameter starts. The RNC periodically attempts
to reconfigure services to the HS-DSCH or E-DCH.
6 Inter-PLMN Handover
Generally, an operator disallows the inter-PLMN handover. The following parameter settings on
the RNC are used to determine whether to allow the inter-PLMN handover:
• Inter-PLMN handovers within the UMTS network: If
InterPlmnHoAllowedIntraRat (BSC6900, BSC6910) in the SET
UOPERATORSHARINGMODE command is set to YES, the RNC supports inter-
PLMN handovers within the UMTS network. If this parameter is set to NO, the RNC
does not support inter-PLMN handovers within the UMTS network.
• Inter-RAT inter-PLMN handovers: If InterPlmnHoAllowedInterRat (BSC6900,
BSC6910) in the SET UOPERATORSHARINGMODE command is set to YES, the
RNC supports inter-RAT inter-PLMN handovers. If this parameter is set to NO, the
RNC does not support inter-RAT inter-PLMN handovers.
When both the parameters above are set to YES:
• If the TarCnOpIndex (BSC6900, BSC6910) parameter in the ADD
UINTERPLMNHOLIST command is specified, handovers are allowed in
neighboring cells contained in the inter-PLMN handover list and in neighboring cells
of the current operator. If not specified, handovers to all configured neighboring cells
are allowed.
• UEs cannot be handed over to a blacklisted neighboring cell of the best cell through an
intra-UMTS inter-PLMN handover. For blacklisted neighboring cells,
BLACKLIST_FLAG under the NCellCapContainer (BSC6900, BSC6910) parameter
is selected.
For details about inter-PLMN handovers, see sections related to inter-PLMN handover in MOCN
Feature Parameter Description.
The function of preferentially handing over a roaming UE to its HPLMN during a cross-PLMN
handover is introduced in RAN19.1. When a roaming user attempts to perform a handover to the
UMTS (cross-RNC handover), GSM, or LTE network of another PLMN, this function enables
the SRNC to include the HPLMN of the roaming user as the target PLMN in the RELOCATION
REQUIRED message to the CN so that the user is preferentially handed over to its HPLMN.
This function takes effect only when all the following conditions are met:
• PERFENH_RELO_HPLMN_OPT_SWITCH under the PerfEnhanceSwitch9
• The target cell is a neighboring cell of the source cell and the operator indicated by the
HPLMN of the roaming user is included in the operator group configured on the target
cell.
Neighboring LTE cells are configured by using the ULTECELL MO, in which the
CnOpGrpIndex (BSC6900, BSC6910) indicates the index of the operator group that
serves the neighboring LTE cells.
Neighboring UMTS cells are configured by using the UEXT3GCELL MO, in which
the CnOpGrpIndex (BSC6900, BSC6910) indicates the index of the operator group
that serves the neighboring UMTS cells.
Neighboring GSM cells are configured by using the UEXT2GCELL MO, in which
the CnOpGrpIndex (BSC6900, BSC6910) indicates the index of the operator group
that serves the neighboring GSM cells.
Information of operators included in an operator group is configured by using the
UCNOPERGROUP MO.
• Information of the HPLMN of the roaming user has been configured on the SRNC by
using the UCNOPERATOR MO.
A PLMN ID consists of an MCC and an MNC. An MCC contains three digits, while
an MNC contains two or three digits. A PLMN ID contains five or six digits. The first
five or six digits in the IMSI delivered by the CN indicate the PLMN of the roaming
user. Due to uncertainty in the PLMN ID length, the RNC cannot correctly identify the
HPLMN of the roaming. The HPLMN of the roaming user must be configured on the
SRNC so that it can correctly identify its HPLMN. This function takes effect only
when the PLMN ID obtained in the IMSI is the same as that configured on the SRNC.
7 Neighboring Cell Combination
7.1 Overview
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 the 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.
Restrictions on the maximum number of neighboring cells configured for a cell are as follows:
• A maximum number of 64 intra-frequency neighboring cells can be configured,
including the cell itself.
If more than 32 intra-frequency neighboring cells are configured,

HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH and
HO_INTRA_FREQ_DETSET_RPRT_SWITCH under the HoSwitch (BSC6900, BSC6910)
parameter must be selected so that UEs can report information about the excessive intra-frequency
neighboring cells and add them to the active set.
• Up to 32 inter-frequency neighboring cells operating at the same frequency can be

configured. Up to 64 inter-frequency neighboring cells operating at different
frequencies can be configured.
• Up to 32 neighboring GSM cells served by the same operator can be configured. Up to
64 neighboring GSM cells served by different operators can be configured.
7.2 Neighboring Cell Combination Switches
Table 7-1 lists parameters involved in neighboring cell combination.

Table 7-1 Parameters involved in neighboring cell combination
Function Parameter Option Description
General HOSWITCH HO_MC_NCELL_COMBINE_SWITCH After this option is selected, t

switch (BSC6900, combination algorithm takes
BSC6910)
Intra- HOSWITCH HO_MC_INTRAFREQ_NCELL_COMBINE_SWITCH For any of these options:

Frequency (BSC6900, • If the option is sele
Neighboring BSC6910) cells from the neig
Cell in the active set fo
Combination • If the option is not
Algorithm the cells from the n
Switch best cell for measu
Inter- HOSWITCH HO_MC_INTERFREQ_NCELL_COMBINE_SWITCH For example, if
Frequency (BSC6900, HO_MC_INTRAFREQ_NCE
Neighboring BSC6910) is selected, the UE selects th
Cell frequency neighboring cells o
Combination set for measurement.
Algorithm
Switch
Function Parameter Option Description
Neighboring HOSWITCH HO_MC_GSM_NCELL_COMBINE_SWITCH

GSM Cell (BSC6900,
Combination BSC6910)
Algorithm
Switch
Neighboring HOSWITCH HO_MC_LTE_NCELL_COMBINE_SWITCH

LTE Cell (BSC6900,
Combination BSC6910)
Algorithm
Switch
7.3 Neighboring Cell Combination Procedure
After obtaining the intra-frequency, inter-frequency, and inter-RAT neighboring cells of each
cell in the active set, the RNC separately calculates the combined intra-frequency, inter-
frequency, and inter-RAT neighboring cell sets, which are recorded as Sall, and then adds these
neighboring cells and cells in the active set to Sall in the following order until the number reaches
the upper limit:
1. (Only applicable to intra-frequency neighboring cells) The RNC adds the best cell in
the active set to Sall.
The best cell is reported through event 1D.
2. (Only applicable to intra-frequency neighboring cells) The RNC adds other cells in
the active set to Sall in a descending order of CPICH Ec/N0.
3. The RNC adds the neighboring cells of the best cell in the active set to Sall.
• Selecting inter-RAT neighboring cells: The RNC adds neighboring cells of
the best cell to the neighboring cell list based on the priority (specified by
the Nprio (BSC6900, BSC6910) parameter) in a descending order. If two or
more neighboring cells have the same Nprio (BSC6900, BSC6910) setting,
the RNC randomly selects up to 32 cells. If fewer than 32 neighboring
cells are configured, the RNC proceeds to 4.
• Selecting inter-frequency neighboring cells
a. From the neighboring cell list of the best cell, the RNC selects
up to two frequencies where the neighboring cells operate as
those to be measured based on priorities (specified by the
HOCovPrio (BSC6900, BSC6910) parameter) of neighboring
cells in a descending order. If two or more neighboring cells
have the same HOCovPrio (BSC6900, BSC6910) setting, the
RNC randomly selects two frequencies as the target ones for
measurements.
b. From the inter-frequency neighboring cells operating at the
target frequency of the highest HOCovPrio (BSC6900,
BSC6910), the RNC selects the target cells based on the priority
(specified by the Nprio (BSC6900, BSC6910) parameter) in a
descending order. If two or more neighboring cells have the
same Nprio (BSC6900, BSC6910) setting, the RNC randomly
selects up to 32 cells. If fewer than 32 neighboring cells are
configured, the RNC proceeds to 3.c.
c. From the inter-frequency neighboring cells operating at the
target frequency of the second highest HOCovPrio (BSC6900,
BSC6910), the RNC selects the target cells based on the priority
(specified by the Nprio (BSC6900, BSC6910) parameter) in a
descending order. If two or more neighboring cells have the
same Nprio (BSC6900, BSC6910) setting, the RNC randomly
selects up to 32 cells. If fewer than 32 neighboring cells are
configured, the RNC proceeds to 4.
4. The RNC adds the neighboring cells of other cells in the active set to Sall.
The method of adding neighboring cells of the best cell in 3 also applies in this step.
In addition, the following principles apply:
• The RNC still uses the two frequencies selected in step 3 as the target
ones.
• The RNC selects intra-frequency, inter-frequency, and inter-RAT
neighboring cells by their repetition in the neighboring cell list of cells in
the active set in a descending order. If two or more neighboring cells are
configured for the same number of cells in the active set, the RNC
preferentially selects the neighboring cells of cells (excluding the best cell)
with the highest CPICH Ec/N0 in the active set.
8 Missing Neighboring Cell Detection
8.1 Overview
An RNC may fail to configure some neighboring cells in a cell's neighboring cell list. These
neighboring cells include intra-frequency, inter-frequency, and inter-RAT neighboring cells.
The causes of the failures are classified into the following:
• Predictable causes, for example, a cell is added or a cell's frequency or scrambling
code changes.
• Unpredictable causes, for example, a building is demolished, causing changes in cell
coverage.
If the neighboring cell list is not updated in time to adapt to these changes, some neighboring
cells may be missing.
Missing neighboring cells may result in call drops or deteriorated signal quality because UEs
cannot be handed over to appropriate neighboring cells in time. Missing neighboring cell
detection consists of the following:
• Missing intra-frequency neighboring cell detection
• Missing inter-frequency neighboring cell detection
• Missing inter-RAT neighboring cell detection
8.2 Missing Intra-Frequency Neighboring Cell Detection
A detected set cell is not in a UE's neighboring cell list, which is contained in the measurement
control message. However, according to section 10.3.7.39 "Intra-frequency measurement
reporting criteria" in 3GPP TS 25.331 V10.0.0, like a monitored set cell, a detected set cell can
also be contained in an intra-frequency measurement report triggered by a 1X (1A, 1C, and 1D)
event. Upon receiving the information about the detected set cell from the UE, the RNC regards
the detected set cell as a missing intra-frequency neighboring cell because the cell is not
contained in the neighboring cell list. Then, the RNC reports the detected set cell to the Nastar or
LMT.
Missing intra-frequency neighboring cell detection is controlled by the
IntraFreqNCellDetectSwitch (BSC6900, BSC6910) parameter in the RNC MML command
SET UNCELLDETECTSWITCH.
• When this switch is turned on, missing intra-frequency neighboring cell detection is
enabled. A UE can report both detected set cells and monitored set cells to the RNC,
which then reports the missing intra-frequency neighboring cells to the Nastar or
LMT.
• When this switch is turned off, missing intra-frequency neighboring cell detection is
disabled.
8.3 Missing Inter-Frequency or Inter-RAT Neighboring Cell Detection
A UE only measures cells in the inter-frequency or inter-RAT neighboring cell list contained in
the measurement control message from the RNC to the UE. Therefore, you can configure as
many inter-frequency or inter-RAT neighboring cells as possible in the neighboring cell list.
Upon receiving an inter-frequency or inter-RAT neighboring cell measurement report from the
UE, the RNC compares the reported cell with the neighboring cell list and determines whether
the reported cell is a missing neighboring cell.
First, the RNC MML command ADD UAUTOINTERNCELLGROUP or ADD
UAUTOGSMNCELLGROUP is executed to configure a group that includes the cells on which
inter-frequency or inter-RAT neighboring cell missing detection is required.
The RNC then adds these cells to the inter-frequency or inter-RAT neighboring cell list of the
UEs that require inter-frequency or inter-RAT measurement. Then, the UEs perform inter-
frequency or inter-RAT measurement.
When receiving a measurement report from a UE, the RNC determines whether the cell in the
measurement report is a missing neighboring cell.
Missing inter-frequency neighboring cell detection is controlled by the
InterFreqNCellDetectSwitch (BSC6900, BSC6910) parameter in the RNC MML command
SET UNCELLDETECTSWITCH.
• When this switch is turned on, missing inter-frequency neighboring cell detection is
enabled. The RNC reports the missing inter-frequency neighboring cells to the Nastar
or LMT.
• When this switch is turned off, missing inter-frequency neighboring cell detection is
disabled.
Missing inter-RAT neighboring cell detection is controlled by the
InterRatNCellDetectSwitch (BSC6900, BSC6910) parameter in the RNC MML command SET
UNCELLDETECTSWITCH.
• When this switch is turned on, missing inter-RAT neighboring cell detection is
enabled. The RNC reports the missing inter-RAT neighboring cells to the Nastar or
LMT.
• When this switch is turned off, missing inter-RAT neighboring cell detection is
disabled.
8.4 Missing Neighboring Cell Detection Activation Observation
After the missing neighboring cell detection function is activated, observe the activation status
using either of the following methods:
• Tracing messages
1. Click Trace on the LMT page. The Trace page is displayed.
2. In the Trace Navigation Tree pane, choose Trace > UMTS Services >
MNCDT Trace. The MNCDT Trace dialogue box is displayed. See
Figure 8-1.
Figure 8-1 Missing neighboring cell tracing
3. In the MNCDT Trace dialog box, set Detection Type to the required type
for the missing neighboring cell detection, specify other parameters as
required, and click Submit.
If the RNC reports missing neighboring cells, the missing neighboring cell
detection function has taken effect. Figure 8-2 shows an example of the
RNC reporting intra-frequency missing neighboring cells, and the intra-
frequency missing neighboring cell detection function has taken effect.
Figure 8-2 Reporting missing intra-frequency neighboring cells
• Viewing OMU logs

1. Run the RNC MML command SET UCHRCTRL with
INTRA_FREQ_NET_OPT, INTER_FREQ_NET_OPT, or
INTER_RAT_NET_OPT selected under the Flow Type parameter.
2. Check the corresponding event block of missing neighboring cells in the
OMU log file generated by the RNC.
If there are event blocks of missing neighboring cells, the missing
neighboring cell detection function has taken effect.
9 Related Features
Prerequisite Features
Feature ID Feature Name Description
WRFD-010610 HSDPA Introduction Package N/A
WRFD-020201 Intra NodeB Softer Handover The intra-frequency handover function

in the WRFD-01061006 HSDPA
WRFD-020202 Intra RNC Soft Handover Mobility Management feature depends
on at least one of these features.
WRFD-020203 Inter RNC Soft Handover
WRFD-020301 Intra Frequency Hard Handover
WRFD-020302 Inter Frequency Hard Handover The inter-frequency handover function

Based on Coverage in the WRFD-01061006 HSDPA
Mobility Management feature depends
WRFD-020304 Inter Frequency Hard Handover on at least one of these features.
Based on DL QoS
WRFD-020103 Inter Frequency Load Balance
WRFD-020303 Inter-RAT Handover Based on The inter-RAT handover function in

Coverage the WRFD-01061006 HSDPA Mobility
Management feature depends on at
WRFD-020309 Inter-RAT Handover Based on least one of these features.
DL QoS
WRFD-020305 Inter-RAT Handover Based on

Service

Load
Mutually Exclusive Features
None
Impacted Features
WRFD-160103 Terminal Black List If TAC_FUNC (BSC6900, BSC6910) is set

to Special_User_Enhance and
SpecUserFunctionSwitch4 (BSC6900,
BSC6910) is set to
SPECUSER_NO_HSDPACM_SWITCH,
UEs in the blacklist cannot process
HSDPA and HSPA+ services in
compressed mode.
WRFD-020201 Intra NodeB Softer Handover The intra-frequency handover

function in the WRFD-01061204
WRFD-020202 Intra RNC Soft Handover HSUPA Mobility Management
feature depends on at least one of
WRFD-020203 Inter RNC Soft Handover these features.
WRFD-020301 Intra Frequency Hard Handover
WRFD-020302 Inter Frequency Hard Handover The inter-frequency handover

Based on Coverage function in the WRFD-01061204
HSUPA Mobility Management
WRFD-020304 Inter Frequency Hard Handover feature depends on at least one of
Based on DL QoS these features.
WRFD-020103 Inter Frequency Load Balance
WRFD-020303 Inter-RAT Handover Based on The inter-RAT handover function in

Coverage the WRFD-01061204 HSUPA
Mobility Management feature
WRFD-020309 Inter-RAT Handover Based on depends on at least one of these
DL QoS features.
Service

Load

None
Impacted Features
WRFD-160103 Terminal Black List If TAC_FUNC (BSC6900, BSC6910) is set

to Special_User_Enhance and
SpecUserFunctionSwitch4 (BSC6900,
BSC6910) is set to
SPECUSER_NO_HSDPACM_SWITCH,
UEs in the UE blacklist cannot process
HSUPA and HSPA+ services in
compressed mode.
WRFD-020110 Multi Frequency Band The WRFD-020302 Inter Frequency

Networking Management Hard Handover Based on Coverage
feature depends on the WRFD-
020110 Multi Frequency Band
Networking Management feature if it
applies to inter-frequency handovers
from a non-U900 band to the U900
band.
None
Impacted Features
None
WRFD-020110 Multi Frequency The WRFD-021200 HCS (Hierarchical Cell

Band Networking Structure) feature depends on the WRFD-020110
Management Multi Frequency Band Networking Management
feature if it applies to inter-frequency handovers from
a non-U900 band to the U900 band.
None
Impacted Features
None
WRFD-020110 Multi Frequency Band The WRFD-020304 Inter

Networking Management Frequency Hard Handover Based
on DL QoS feature depends on
the WRFD-020110 Multi
Frequency Band Networking
Management feature if it applies
to inter-band inter-frequency
handovers from another
frequency band to the U900
frequency band.
WRFD-020302 Inter Frequency Hard Handover N/A

Based on Coverage
None
Impacted Features
None
WRFD-020302 Inter Frequency Hard Handover N/A

Based on Coverage
None
Impacted Features
None
10 Network Impact
System Capacity
No impact.
Network Performance
This feature ensures the service continuity of moving UEs and reduces service drops at the
coverage edge.
System Capacity
No impact.
Network Performance
This feature reduces service drops caused by reduced downlink quality and ensures the QoS for
users.
System Capacity
No impact.
Network Performance
This feature reduces service drops caused by reduced uplink quality and ensures the QoS for
users.
System Capacity
No impact.
Network Performance
This feature reduces the number of call drops caused by reduced downlink quality and ensures
the QoS for users.
System Capacity
No impact.
Network Performance
This feature reduces service drops caused by reduced uplink quality and ensures the QoS for
users.
System Capacity
None
Network Performance
This feature implements all types of handovers between adjacent cells. This provides continuous
coverage and better service quality for HSDPA UEs.
11 Engineering Guidelines
11.1 WRFD-020201 Intra NodeB Softer Handover
11.1.1 Requirements
• Hardware
Micro base stations do not support intra-NodeB softer handovers.
• Other features
This feature does not depend on other features.
• License
This feature is not under license control.
• Other requirements
PScrambCode (BSC6900, BSC6910) for intra-frequency cells with the same or
overlapped coverage must be set to different values.
11.1.2 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH. In this step, select
HO_INTRA_FREQ_SOFT_HO_SWITCH under HandOver Switch.
2. Run the RNC MML command SET UHOCOMM. In this step, set Softer Handover
Combination Indication Switch to MAY(NodeB chooses whether combine at
NodeB) or MUST(Must combine at NodeB).
3. Run the RNC MML command ADD UINTRAFREQNCELL to add an intra-
frequency neighboring cell.
4. Run the RNC MML command SET UINTRAFREQHO. In this step, set Intra-
frequency L3 Filter Coefficient, Intra-frequency Measurement Quantity, Event
1C to Periodical Report Number, and Event 1C to Periodical Report Period to
D3, CPICH_EC/NO, D16, and D4000, respectively.
5. (Optional) Run the RNC MML command ADD UCELLINTRAFREQHOENH. In
this step, set Cell Weak Cov SHO Switch to ON and specify the following
parameters:
• Weak Cov SHO Measurement Control Filter Coef
• Weak Cov 1A Relative Thld for CS
• Weak Cov 1A Relative Thld for PS
• Weak Cov 1B Relative Thld for CS
• Weak Cov 1B Relative Thld for PS
• Weak Cov Delayed Time to Trigger 1A Event
• Weak Cov Delayed Time to Trigger 1B Event
//Activating Intra NodeB Softer Handover
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_SOFT_HO_SWITCH-1;
SET UHOCOMM: DivCtrlField=MAY;
ADD UINTRAFREQNCELL: RNCId=202, CellId=2381, NCellRncId=202, NCellId=3291,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE;
SET UINTRAFREQHO: FilterCoef=D3, IntraFreqMeasQuantity=CPICH_EC/NO,
PeriodMRReportNumfor1C=D16, ReportIntervalfor1C=D4000;

Check the value of the RNC counter VS.SoHO.Att.RNC (BSC6900, BSC6910). If the value is not
0, this feature has been activated.
11.1.5 Deactivation
1. Deactivate Intra NodeB Softer Handover.

Run the RNC MML command SET UHOCOMM to set Softer handover
combination indicator switch to MUST_NOT.
//Deactivating Intra NodeB Softer Handover
SET UHOCOMM: DivCtrlField=MUST_NOT;
11.2 WRFD-020202 Intra RNC Soft Handover
11.2.1 Requirements
• Hardware
This feature does not have any special requirements for hardware.
• Other features
• License
11.2.2 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH to enable the soft
handover.
3. Run the RNC MML command SET UINTRAFREQHO to set the parameters
related to intra-frequency handovers.
parameters:
//Activating Intra RNC Soft Handover
1. On the RNC LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace. The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. Enable both UE 1 and UE 2 in idle mode to camp on CELL1.
4. Enable UE 1 to make a call to UE 2.
The conversation is clear.
5. Enable UE 1 to move from CELL1 to CELL2.
Through Trace Data, it can be observed that RNC 1 sends the
RRC_ACTIVE_SET_UPDATE message to UE 1, and UE 1 returns the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC 1.
11.2.5 Deactivation
1. Deactivate Inter RNC Soft Handover.

Run the RNC MML command SET UCORRMALGOSWITCH to set Softer
handover combination indicator to disable the soft handover.
//Deactivating Intra RNC Soft Handover
11.3 WRFD-020203 Inter RNC Soft Handover
11.3.1 Requirements
• Hardware
• Other features
• License
Neighboring RNCs must support this feature.
11.3.2 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH to enable the soft
handover.
2. Run the RNC MML command ADD UNRNC with the SHO cross IUR trigger
parameter specified to enable cross-Iur soft handovers for required services.
3. Run the RNC MML command ADD UEXT3GCELL to add a cell served by the
neighboring RNC.
parameters:
7. (Optional) To enable the handover priority optimization for inter-frequency
neighboring cells sent to the SRNC, run the RNC MML command SET
UCORRMPARA with
PERFENH_DRNC_INTER_FREQ_NCELL_OPT_SWITCH under
PerfEnhanceSwitch9 selected.
//Activating Inter RNC Soft Handover
ADD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-1&HSPA_SHO_SWITCH-
1&NON_HSPA_SHO_SWITCH-1, HHOTRIG=ON, ServiceInd=SUPPORT_CS_AND_PS,
IurExistInd=TRUE, RncProtclVer=R10, TnlBearerType=IP_TRANS;
ADD UEXT3GCELL: NRncId=1, CellId=2381, CellHostType=SINGLE_HOST,
CellName="2222", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1,
UARFCNUplinkInd=TRUE, UARFCNUplink=9750, UARFCNDownlink=10700,
TxDiversityInd=FALSE, LAC=2506, CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE,
QrxlevminInd=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED,
CellCapContainerFdd=EDCH_SUPPORT-0, EFachSupInd=FALSE;
1. On the RNC LMT, click Trace > UMTS Services, and then double-click Uu
Interface Trace.
The Uu Interface Trace dialog box is displayed.
2. Set parameters in the areas Cell Config, Uu Message Type, and Save File. Then,
click Submit.
3. Enable both UE 1 and UE 2 in idle mode to camp on CELL1.
4. Enable UE 1 to make a call to UE 2.
The conversation is clear.
5. Enable UE 1 to move from CELL1 to CELL2.
Through Trace Data, it can be observed that RNC 1 sends the
RRC_ACTIVE_SET_UPDATE message to UE 1, and UE 1 sends the
RRC_ACTIVE_SET_UPDATE_CMP message to RNC 1.
11.3.5 Deactivation
1. Deactivate Inter RNC Soft Handover.

Run the RNC MML command MOD UNRNC with the SHO cross IUR trigger
parameter specified to disable cross-Iur soft handovers for required services.
//Deactivating Inter RNC Soft Handover
MOD UNRNC: NRncId=1, SHOTRIG=CS_SHO_SWITCH-0&HSPA_SHO_SWITCH-
0&NON_HSPA_SHO_SWITCH-0;
11.4 WRFD-020301 Intra Frequency Hard Handover
11.4.1 Requirements
• Hardware
• Other features
• License
11.4.2 Activation
HO_INTRA_FREQ_HARD_HO_SWITCH under HandOver Switch.
2. Run the RNC MML command ADD UINTRAFREQNCELL to add a neighboring
cell served by the same RNC.
3. If the cross-Iur hard handover is required, run the following commands to add a
neighboring RNC and a cell served by the neighboring RNC.
a. Run the RNC MML command ADD UNRNC to add a neighboring
RNC.
b. Run the RNC MML command ADD UEXT3GCELL to add a cell
served by the neighboring RNC.
c. Run the RNC MML command ADD UINTRAFREQNCELL to add
neighboring relationship.
//Activating Intra Frequency Hard Handover
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_HARD_HO_SWITCH-1;
ADD UINTRAFREQNCELL: RncId=1, CellId=111, NCellRncId=1, NCellId=211,
ADD UNRNC: NRncId =2, SHOTRIG=CS_SHO_SWITCH-0&HSPA_SHO_SWITCH-
0&NON_HSPA_SHO_SWITCH-0, HHOTRIG=ON, SERVICEIND=SUPPORT_CS_AND_PS,
IurExistInd=TRUE, DPX=1, RNCPROTCLVER=R5, STATEINDTMR=20,
TnlBearerType=ATM_TRANS;
ADD UEXT3GCELL: NRncId=2, CellId=311, CellHostType=SINGLE_HOST,
CellName="311", CnOpGrpIndex=0, PScrambCode=256, BandInd=Band1,
UARFCNUplinkInd=TRUE, UARFCNUplink=http://localhost:7890/9750,
UARFCNDownlink=10700, TxDiversityInd=FALSE, LAC=H'2506,
CfgRacInd=NOT_REQUIRE, QqualminInd=FALSE, QrxlevminInd=FALSE,
MaxAllowedUlTxPowerInd=FALSE, CellCapContainerFdd=EDCH_SUPPORT-1,
EFachSupInd=FALSE;
SET UINTRAFREQHO: LogicRncId=11, FilterCoef=D4,
IntraFreqMeasQuantity=CPICH_EC/NO, PeriodMRReportNumfor1A=D16,
ReportIntervalfor1A=D4000, PeriodMRReportNumfor1C=D16,
ReportIntervalfor1C=D4000, PeriodMRReportNumfor1J=D64,
ReportIntervalfor1J=D1000, IntraRelThdFor1ACSVP=6, IntraRelThdFor1ACSNVP=6,
IntraRelThdFor1APS=6, IntraRelThdFor1BCSVP=12, IntraRelThdFor1BCSNVP=12,
IntraRelThdFor1BPS=12, IntraAblThdFor1FEcNo=-24, HystFor1A=0, HystFor1B=0,
HystFor1C=8, HystFor1D=8, HystFor1F=8, HystFor1J=8, Weight=0,
TrigTime1A=D320, TrigTime1B=D640, TrigTime1C=D640, TrigTime1D=D640,
TrigTime1F=D640, TrigTime1J=D640, ShoFailPeriod=60, ShoFailNumForDwnGrd=3,
RelThdForDwnGrd=2, DcccShoPenaltyTime=30, SHOQualmin=-20,
MaxCellInActiveSet=3, BlindHORSCP1FThreshold=-115,
BlindHOIntrafreqMRInterval=D250, BlindHOIntrafreqMRAmount=D2,
SoftFailD2FSwitch=OFF, SoftFailF2DPunishTimer=10, SoftFailD2FOffset=4,
SoftFailE2DSwitch=OFF;
Check the value of the RNC counter VS.HHO.AttIntraFreq.RNC (BSC6900, BSC6910). If the
value is not 0, this feature has been activated.
11.4.5 Deactivation
Run the RNC MML command SET UCORRMALGOSWITCH to deselect

HO_INTRA_FREQ_HARD_HO_SWITCH from the Handover switch list.
//Deactivating Intra Frequency Hard Handover
SET UCORRMALGOSWITCH: HoSwitch=HO_INTRA_FREQ_HARD_HO_SWITCH-0;
Requirements
• Hardware
None
• Other features
The prerequisite features have been configured. For details about the prerequisite
features, see 9.2 WRFD-01061204 HSUPA Mobility Management.
• License
This feature is controlled by the license for WRFD-010612 HSUPA Introduction
Package. For details about this license, see HSUPA Feature Parameter Description.
Deployment
The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers are the
same for HSUPA users and R99 users. For the activation procedures for configuring HSUPA
Mobility Management, see the following sections:
• 11.4 WRFD-020301 Intra Frequency Hard Handover
• 11.7 WRFD-020302 Inter Frequency Hard Handover Based on Coverage
• 11.9 Inter Frequency Hard Handover Based on UL QoS
• "Engineering Guidelines" in Inter Frequency Load Balance Feature Parameter Description

• 11.10 WRFD-020303 Inter-RAT Handover Based on Coverage
• 11.12 Inter-RAT Handover Based on UL QoS
• 11.16 WRFD-020305 Inter-RAT Handover Based on Service
• 11.17 WRFD-020306 Inter-RAT Handover Based on Load
After this feature is activated, UMTS-to-GSM handover is allowed after videophone services fall
back to voice services.
This feature is not recommended for new projects (such as new deployment, reconstruction, and
optimization). Contact Huawei technical support if you want to enable this feature.
11.6.1 Requirements
• Hardware
• Other features
• License
For details about how to activate the license, see License Management Feature Parameter
Description.
Feature ID Feature Name License Control NE Sales Unit

Item ID
WRFD-021200 HCS (Hierarchical LQW1HCS01 BSC6900 per Erl

Cell Structure) BSC6910 per Mbps
The license control item in the DSP LICUSAGE command output is Hierarchical
Cell Structure (per Erl) or Hierarchical Cell Structure (per Mbps).
▪ To enable videophone services to fall back to voice services, the MSC and
UE must comply with 3GPP Release 6. For details, see section 4.3 "Core
Network procedure" in 3GPP TS 23.172 V10.0.0.
11.6.2 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH.

In this step, select CMP_DL_LOAD_BALANCE_SWITCH under the
Compatibility Switch2 parameter and the following options under the HoSwitch
(BSC6900, BSC6910) parameter:
• HO_ALGO_HCS_SPEED_EST_SWITCH
• HO_INTRA_FREQ_SOFT_HO_SWITCH
• HO_INTER_FREQ_HARD_HO_SWITCH
• HO_INTER_RAT_PS_OUT_SWITCH
• HO_INTER_RAT_CS_OUT_SWITCH
2. Run the RNC MML command ADD UCELLHCS. In this step, set Use of HCS to
USED.
3. Set the HCS parameters for different types of neighboring cells as follows:
• Run the RNC MML command ADD UINTRAFREQNCELL to add an
intra-frequency neighboring cell and set the HCS parameters.
• Run the RNC MML command ADD UINTERFREQNCELL to add an
inter-frequency neighboring cell and set the HCS parameters.
• Run the RNC MML command ADD U2GNCELL to add an inter-RAT
neighboring GSM cell and set the HCS parameters.
4. For the cells whose HCS parameters have been set, run the RNC MML command
ADD UCELLHCSHO. In this step, set SpdEstSwitch to ON.
5. Run the RNC MML command SET UHCSHO to set the RNC-level HCS parameters
according to network plan.
/*Activating HCS (Hierarchical Cell Structure)*/
//Setting the handover switch
SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-
1&HO_INTRA_FREQ_SOFT_HO_SWITCH-1&HO_INTER_FREQ_HARD_HO_SWITCH-
1&HO_INTER_RAT_PS_OUT_SWITCH-1&HO_INTER_RAT_CS_OUT_SWITCH-1,
CmpSwitch2=CMP_DL_LOAD_BALANCE_SWITCH-1;
//Setting an HCS cell
ADD UCELLHCS: CellId=11, UseOfHcs=USED;
//Adding an intra-frequency neighboring cell
SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE,
TpenaltyHcsReselect=D0, NPrioFlag=FALSE;
//Adding an inter-frequency neighboring cell
ADD UINTERFREQNCELL: RncId=1, CellId=11, NCellRncId=9, NCellId=100,
CIOOffset=0, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0,
HOCovPrio=1, BlindHOFlag=FALSE, NPrioFlag=FALSE;
//Adding a GSM inter-RAT neighboring cell
ADD U2GNCELL: RncId=1, CellId=11, GSMCellIndex=0, CIOOffset=0, Qoffset1sn=0,
Qrxlevmin=-50, TpenaltyHcsReselect=D0, TempOffset1=D3, BlindHoFlag=TRUE,
BlindHOPrio=30, NPrioFlag=FALSE;
//Enabling the UE speed estimation algorithm
ADD UCELLHCSHO: CellId=11, SpdEstSwitch=ON;
//Configuring RNC-level HCS parameters
SET UHCSHO: TFastSpdEst=180, NFastSpdEst=15, TCycleSlow=60, TSlowSpdEst=240,
NSlowSpdEst=3, TRelateLength=10;

To check whether this feature has been activated, perform the following steps:
1. If the moving speed of a UE is higher than the fast-moving handover threshold (the
number of 1D events reported by the UE in the specified period reaches the preset
number), an inter-frequency or inter-RAT HCS handover is triggered.
2. If the moving speed of a UE is lower than the slow-moving handover threshold (the
number of 1D events reported by the UE in the specified period is less than the slow-
moving handover threshold), slow-moving HCS handover measurement is triggered,
and a slow-moving inter-frequency or inter-RAT HCS handover is performed.
3. If a measurement-based inter-frequency or inter-RAT handover is triggered, check
whether compressed mode is started by using a RRC_PH_CH_RECFG message on
the Uu interface on the RNC LMT. If compressed mode is started, this feature is
activated.
4. If an inter-frequency blind handover is triggered, check whether the handover is
triggered by using a RRC_PH_CH_RECFG message on the Uu interface on the
RNC LMT. If the handover is triggered by using the message, this feature is
activated.
5. If an inter-RAT blind handover is triggered, check whether UMTS-to-GSM
handovers are performed on the Uu and Iu interfaces on the RNC LMT. If UMTS-to-
GSM handovers are performed, this feature is activated.
To check whether a videophone service has fallen back to a voice service after being handed
over to the GSM network, perform the following steps:
1. Start Iu Interface Trace and Uu Interface Trace on the RNC LMT.
2. After video phone services are established, check, in the Uu Interface Trace dialog
box, that the UE sends to the RNC an RRC_MEAS_RPRT message, which contains
the 3A report.
3. In the Iu Interface Trace dialog box, check that the RNC sends an
RAB_MODIFY_REQ message to the CN. In the RAB_MODIFY_REQ message,
the value of the IE "alternativeRABConfigurationRequest" is alternative-RAB-
configuration-Requested.
11.6.5 Deactivation
1. Run the RNC MML command SET UCORRMALGOSWITCH. In this step,

deselect HO_ALGO_HCS_SPEED_EST_SWITCH from the HoSwitch
parameter.
2. Run the RNC MML command MOD UCELLHCS. In this step, set Use of HCS to
NOT_USED.
3. Run the RNC MML command MOD UCELLHCSHO. In this step, set
SpdEstSwitch to OFF.
//Deactivating HCS (Hierarchical Cell Structure)
SET UCORRMALGOSWITCH: HoSwitch=HO_ALGO_HCS_SPEED_EST_SWITCH-0;
MOD UCELLHCS: CellId=11, UseOfHcs=NOT_USED;
MOD UCELLHCSHO: CellId=11, SpdEstSwitch=OFF;
Enable WRFD-020302 Inter Frequency Hard Handover Based on Coverage in inter-frequency

networking.
• The success rate of coverage-based inter-frequency handovers in a cell has exceeded
the target set by the operator. For example, greater than 99%.
Success rate of coverage-based inter-frequency handovers =
(VS.HHO.SuccInterFreqOut.CS.Rscp (BSC6900, BSC6910) +
VS.HHO.SuccInterFreqOut.CS.EcNo (BSC6900, BSC6910) +
VS.HHO.SuccInterFreqOut.PS.Rscp (BSC6900, BSC6910) +
VS.HHO.SuccInterFreqOut.PS.EcNo (BSC6900,
BSC6910))/(VS.HHO.AttInterFreqOut.CS.TrigRscp (BSC6900, BSC6910) +
VS.HHO.AttInterFreqOut.CS.TrigEcNo (BSC6900, BSC6910) +
VS.HHO.AttInterFreqOut.PS.TrigRscp (BSC6900, BSC6910) +
VS.HHO.AttInterFreqOut.PS.TrigEcNo (BSC6900, BSC6910)) x 100%
• The inter-frequency handover measurement results are reported through event
reporting.
It is recommended that the inter-frequency handover success rate optimization
function be disabled when inter-frequency handover measurement results are reported
through event reporting, specifically, InterFreqReportMode (BSC6900, BSC6910) is
set to EVENT_TRIGGER. The reason is that the CIOOFFSET (BSC6900, BSC6910)
parameter setting does not take effect on some UEs in this situation.
None
11.7.3 Requirements
• Hardware
None
• Other features
None
• License
Description.
Feature ID Feature Name License Control Item NE Sales Unit
ID
WRFD-020302 Inter Frequency LQW1HHO01 BSC6900 per Erl

Hard Handover BSC6910 per Mbps
Based on Coverage
The license control item in the DSP LICUSAGE command output is Inter frequency
hard handover (per Erl) or Inter frequency hard handover (per Mbps).
If RAN Sharing or MOCN is enabled, the licensed resource is allocated among the
primary and secondary operators according to the following method:
Method 5: In RAN Sharing scenarios, a feature is activated for the primary and
secondary operators separately. In MOCN scenarios, a feature is activated only for the
primary operator. The licensed values can be set by running the SET LICENSE
command.
▪ The UE supports relevant measurements and the handover procedure.
▪ Certain UEs may not support this feature. To ensure network performance,
it is good practice to blacklist this feature on unsupported UEs as described
in Terminal Black List Feature Parameter Description. During the setting, set
TAC_FUNC (BSC6900, BSC6910) to Special_User_Enhance and select
INTERHO_DISABLED_SWITCH under SpecUserFunctionSwitch
(BSC6900, BSC6910).
▪ Certain UEs running only PS BE services may not support this feature. To
ensure network performance, it is good practice to blacklist this feature on
unsupported UEs as described in Terminal Black List Feature Parameter Description.
During the setting, set TAC_FUNC (BSC6900, BSC6910) to
Special_User_Enhance and select
PSBE_INTERHO_DISABLED_SWITCH under
SpecUserFunctionSwitch (BSC6900, BSC6910).
11.7.4 Activation
HO_INTER_FREQ_HARD_HO_SWITCH under HandOver Switch.
2. Run the RNC MML command ADD UINTERFREQNCELL to add an inter-
3. Run the RNC MML command ADD UCELLINTERFREQHOCOV (cell level) or
SET UINTERFREQHOCOV (RNC level) to configure parameters related to the
coverage-based inter-frequency hard handover.
//Operations on the RNC
//Activating Inter Frequency Hard Handover Based on Coverage
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1;
ADD UCELLINTERFREQHOCOV: CellId=1, InterFreqReportMode=PERIODICAL_REPORTING,
InterFreqMeasTime=60;
1. Start Uu interface trace on the RNC LMT.

2. Check that the RNC sends the UE an RRC_MEAS_CTRL message and that the
message contains thresholds for triggering events 2D and 2F and the reporting mode.
3. Attenuate signals in the current cell that the UE accesses to trigger reporting of event
2D by the UE.
4. Check that the RNC sends the UE an RRC_MEAS_RPRT message and that the
traced message contains an event 2D measurement report shown in Figure 11-1.
Figure 11-1 Event 2D measurement report
5. After the event 2D measurement result is reported, check that the RNC sends the UE
an RRC_MEAS_CTRL message and that the traced message contains the
"interFrequencyMeasurement" IE, as shown in Figure 11-2.
Figure 11-2 Inter-frequency measurement control message
6. After the inter-frequency measurement control message is reported, check that the
RNC sends the UE an RRC_PH_CH_RECFG message and that the UE sends the
RNC an RRC_PH_CH_RECFG_CMP message, as shown in Figure 11-3 and Figure 11-
4.
Figure 11-3 Physical channel reconfiguration message
Figure 11-4 Physical channel reconfiguration complete message

11.7.7 Deactivation
Run the RNC MML command SET UCORRMALGOSWITCH. In this step, deselect
HO_INTER_FREQ_HARD_HO_SWITCH under HandOver Switch.
//Operations on the RNC
//Deactivating Inter Frequency Hard Handover Based on Coverage
After the WRFD-020302 Inter Frequency Hard Handover Based on Coverage feature is
activated, collect statistics about the following counters in the live network.
Counter Name Description
VS.RRC.MrRpt.2D (BSC6900, BSC6910) Number of Event 2D Measurement Reports

for Cell
VS.HHO.AttInterFreqOut.CS.TrigRscp Number of CS Inter-Frequency Hard

(BSC6900, BSC6910) Handover Attempts Based on RSCP for Cell
VS.HHO.AttInterFreqOut.CS.TrigEcNo Number of CS Inter-Frequency Hard

(BSC6900, BSC6910) Handover Attempts Based on EcNo for Cell
VS.HHO.AttInterFreqOut.PS.TrigRscp Number of PS Inter-Frequency Hard

(BSC6900, BSC6910) Handover Attempts Based on RSCP for Cell
VS.HHO.AttInterFreqOut.PS.TrigEcNo Number of PS Inter-Frequency Hard

(BSC6900, BSC6910) Handover Attempts Based on EcNo for Cell
When a UE is located at the cell edge, it reports event 2D to trigger a coverage-based inter-
frequency or inter-RAT hard handover.
• If the value of the VS.RRC.MrRpt.2D (BSC6900, BSC6910) counter is small, the
number of coverage-based inter-frequency hard handovers triggered in a measurement
period is small, which indicates that the gains provided by this feature are not obvious.
• If the value of the counter is large and is similar to the value of the
VS.HHO.AttInterFreqOut.CS.TrigRscp (BSC6900, BSC6910),
VS.HHO.AttInterFreqOut.CS.TrigEcNo (BSC6900, BSC6910),
VS.HHO.AttInterFreqOut.PS.TrigRscp (BSC6900, BSC6910),
VS.HHO.AttInterFreqOut.PS.TrigEcNo (BSC6900, BSC6910) counter, the inter-
frequency hard handovers triggered in the measurement period are mainly coverage-
based inter-frequency hard handovers, which indicates that the gains provided by this
feature are obvious.
• If the value of the counter is large and is much greater than the value of the
VS.HHO.AttInterFreqOut.CS.TrigRscp (BSC6900, BSC6910),
VS.HHO.AttInterFreqOut.CS.TrigEcNo (BSC6900, BSC6910),
VS.HHO.AttInterFreqOut.PS.TrigRscp (BSC6900, BSC6910), or
VS.HHO.AttInterFreqOut.PS.TrigEcNo (BSC6900, BSC6910) counter, both
coverage-based inter-frequency hard handovers and coverage-based inter-RAT hard
handovers are triggered in the measurement period.
This feature is recommended when signal fading is serious and the traffic load is high in the live
network.
Collect statistics about the following counters before deploying the WRFD-020304 Inter
Frequency Hard Handover Based on DL QoS feature:
VS.AMR.DL.RateDown (BSC6900, BSC6910): indicates the number of times the downlink data
rates of narrowband AMR speech services are reduced in a cell.
VS.AMRWB.DLRateDown (BSC6900, BSC6910): indicates the number of times the downlink
data rates of wideband AMR speech services are reduced in a cell.
VS.DCCC.AttDownsizing.DL.Cov (BSC6900, BSC6910): indicates the number of downlink DCH
DCCC downsizing attempts based on different strategies (coverage or QoS) in the best cell on
which the UE camps.
During the link stability control of CS services and R99 PS BE services, rate reduction and
handover are triggered in sequence. If the number of rate reductions for CS services and R99 PS
BE services (VS.AMR.DL.RateDown (BSC6900, BSC6910), VS.AMRWB.DLRateDown
(BSC6900, BSC6910), or VS.DCCC.AttDownsizing.DL.Cov (BSC6900, BSC6910)) is small, the
downlink quality did not deteriorate. In this case, do not enable the WRFD-020304 Inter
Frequency Hard Handover Based on DL QoS feature. If the number of rate reductions for CS
services and R99 PS BE services is large, enable the WRFD-020304 Inter Frequency Hard
Handover Based on DL QoS feature.
11.8.3 Requirements
• Hardware
None
• Other features
WRFD-020302 Inter Frequency Hard Handover Based on Coverage
• License
Description.
ID
WRFD-020304 Inter Frequency LQW1IFHHO01 BSC6900 per Erl

Hard Handover BSC6910 per Mbps
Based on DL QoS
The license control item in the DSP LICUSAGE command output is Inter
Frequency Hard Handover Based on DL QoS (per Erl) or Inter Frequency Hard
Handover Based on DL QoS (per Mbps).
command.
INTERHO_DISABLED_SWITCH under SpecUserFunctionSwitch
(BSC6900, BSC6910).
11.8.4 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH to activate the

inter-frequency hard handover.
3. Run the RNC MML command ADD UCELLQOSHO (cell level) or SET
UQOSHO (RNC level) to configure parameters related to DL-QoS-based inter-
frequency hard handover.
4. Run the RNC MML command SET UQOSACT to activate inter-frequency hard
handover based on downlink QoS for BE services.
handover based on downlink QoS for AMR and AMR-WB services.
handover based on downlink QoS for VP services.
//Activating Inter Frequency Hard Handover Based on DL QoS
ADD UCELLQOSHO: CellId=111, DlRscpQosHyst=5, DLQosMcTimerLen=20,
ULQosMcTimerLen=20;
SET UQOSACT: BEQosPerform=YES, BeDlAct1=InterFreqHO;
SET UQOSACT: AMRQosPerform=YES, DlQosAmrInterFreqHoSwitch=YES,
DlQosWAmrInterFreqHoSwitch=YES;
SET UQOSACT: VPQosPerform=YES, DlQosVpInterFreqHoSwitch=YES;
1. Log in to the RNC LMT and start Iub Interface Trace.

2. Check that the RNC sends an NBAP_DEDI_MEAS_INIT_REQ message to the
NodeB and that the message contains the event E and event F parameters.
3. Check that the NodeB sends an NBAP_DEDIC_MEAS_RPRT message to the RNC
and that the message contains the event E parameters.
4. Check that the RNC sends an RRC_MEAS_CTRL message to the NodeB to start
event-triggered or periodic inter-frequency measurement. Check that the traced
messages contain the inter-frequency measurement control message sent from the
RNC to the UE.
11.8.7 Deactivation
1. Run the RNC MML command SET UQOSACT to deactivate inter-frequency hard
handover based on downlink QoS for BE services.
handover based on downlink QoS for AMR and AMR-WB services.
handover based on downlink QoS for VP services.
//Deactivating Inter Frequency Hard Handover Based on DL QoS
SET UQOSACT: BEQosPerform=NO;
SET UQOSACT: AMRQosPerform=NO;
SET UQOSACT: VPQosPerform=NO;

This feature is recommended when signal fading is serious and the traffic load is high in the live
network.
Collect statistics about the following counters before deploying the Inter Frequency Hard
Handover Based on UL QoS feature:
• VS.AMRWB.ULRateDown (BSC6900, BSC6910): indicates the number of times the
uplink data rates of narrowband AMR speech services are reduced in a cell.
• VS.AMRWB.ULRateDown (BSC6900, BSC6910): indicates the number of times the
uplink data rates of wideband AMR speech services are reduced in a cell.
• VS.DCCC.AttDownsizing.UL.Cov (BSC6900, BSC6910): indicates the number of
uplink DCH DCCC downsizing attempts based on different strategies (coverage or
QoS) in the best cell on which the UE camps.
During the link stability control of CS services and R99 PS BE services, rate reduction and
handover are triggered in sequence. If the number of rate reductions for CS services and R99 PS
BE services (VS.AMRWB.ULRateDown (BSC6900, BSC6910), VS.AMRWB.ULRateDown
(BSC6900, BSC6910), or VS.DCCC.AttDownsizing.UL.Cov (BSC6900, BSC6910)) is small, the
uplink quality did not deteriorate. In this case, do not enable the Inter Frequency Hard Handover
Based on UL QoS feature. If the number of rate reductions for CS services and R99 PS BE
services is large, enable the Inter Frequency Hard Handover Based on UL QoS feature.
11.9.3 Requirements
• Hardware
None
• Other features
None
• License
INTERHO_DISABLED_SWITCH under the SpecUserFunctionSwitch
11.9.4 Activation

inter-frequency hard handover.
3. Run the RNC MML command ADD UCELLQOSHO (cell level) or SET
UQOSHO (RNC level) to configure parameters related to UL-QoS-based inter-
frequency hard handover.
handover based on uplink QoS for BE services.
handover based on uplink QoS for AMR and AMR-WB services.
handover based on uplink QoS for VP services.
//Activating Inter Frequency Hard Handover Based on UL QoS
ADD UCELLQOSHO: CellId=111, DlRscpQosHyst=5, DLQosMcTimerLen=20,
ULQosMcTimerLen=20;
SET UQOSACT: BEQosPerform=YES, BeUlAct1=InterFreqHO;
SET UQOSACT: AMRQosPerform=YES, UlQosAmrInterFreqHoSwitch=YES,
UlQosWAmrInterFreqHoSwitch=YES;
SET UQOSACT: VPQosPerform=YES, UlQosVpInterFreqHoSwitch=YES;
1. Log in to the RNC LMT and start Uu Interface Trace.

2. Check that the RNC sends an RRC_MEAS_CTRL message to the UE and that the
message contains the event 6A parameter, as shown in Figure 11-5.
Figure 11-5 RRC_MEAS_CTRL message
3. Check that the UE sends an RRC_MEAS_RPRT message to the RNC and that the
message contains the event 6A parameter, as shown in Figure 11-6.
Figure 11-6 RRC_MEAS_RPRT message
event-triggered or periodic inter-frequency measurement.
11.9.7 Deactivation
handover based on uplink QoS for BE services.
handover based on uplink QoS for AMR and AMR-WB services.
handover based on uplink QoS for VP services.
//Deactivating Inter Frequency Hard Handover Based on UL QoS
//Deactivating the Inter Frequency Hard Handover Based on UL QoS feature for
BE services
SET UQOSACT: BEQosPerform=NO;
AMR and AMR-WB services
SET UQOSACT: AMRQosPerform=NO;
videophone services
SET UQOSACT: VPQosPerform=NO;
11.10 WRFD-020303 Inter-RAT Handover Based on Coverage
After this feature is activated, videophone services can fall back to voice services after being
handed over to the GSM network.
• Hardware
None
• Other features
None
• License
Description.

ID
WRFD-020303 Inter-RAT Handover LQW1UGHO01 BSC6900 per Erl

Based on Coverage BSC6910 per Mbps
The license control item in the DSP LICUSAGE command output is Inter-RAT
handover based on coverage (per Erl) or Inter-RAT handover based on coverage
(per Mbps).
command.
INTRATHO_DISABLED_SWITCH under SpecUserFunctionSwitch
(BSC6900, BSC6910).
11.10.2 Activation
HO_INTER_RAT_CS_OUT_SWITCH and
HO_INTER_RAT_PS_OUT_SWITCH under the HandOver Switch parameter.
2. Run the RNC MML command ADD U2GNCELL to add an inter-frequency
neighboring GSM cell.
3. Run the RNC MML command ADD UCELLINTERRATHOCOV (cell level) or
SET UINTERRATHOCOV (RNC level) to configure parameters related to
coverage-based inter-RAT handover to GSM.
If both RNC-level and cell-level parameters are configured, the cell-level parameter
settings prevail.
4. Run the RNC MML command MOD UTYPRABBASIC. In this step, select
HO_TO_GSM_SHOULD_NOT_BE_PERFORM under the Service Handover
Indicator parameter.
//Activating the Inter-RAT Handover Based on Coverage feature

SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_CS_OUT_SWITCH-
1&HO_INTER_RAT_PS_OUT_SWITCH-1;
Qrxlevmin=-50, TpenaltyHcsReselect=D0, TempOffset1=D3, BlindHoFlag=FALSE,
NPrioFlag=FALSE, InterRatAdjsQhcs=20;
ADD UCELLINTERRATHOCOV: CellId=1, FilterCoefOf2D2F=D6, TrigTime2D=D100;
MOD UTYPRABBASIC: RabIndex=0, SHInd=HO_TO_GSM_SHOULD_NOT_BE_PERFORM;

1. Attenuate signals in the current cell that the UE accesses to trigger reporting of event
2D by the UE.
2. Log in to the RNC LMT and start Uu Interface Trace. Under Uu Message Type,
select RRC_MEAS_RPRT.
3. Check whether event 2D shown in Figure 11-7 is reported in the traced messages.
Figure 11-7 Event 2D measurement report
4. Start Uu Interface Trace on the RNC LMT. Under Uu Message Type, select
RRC_MEAS_CTRL.
5. View the traced messages to check whether the RNC sends the UE an inter-RAT
measurement control message shown in Figure 11-8.
Figure 11-8 Inter-RAT measurement control message
• To verify the measurement-based inter-RAT handover triggered by uplink QoS of UEs, you need to run
the RNC MML command SET UQOSACT to turn on the QoS switches of different service types and
attenuate the signals of the current cell. Check whether UEs send the uplink QoS measurement reports
to the RNC. The verification steps are the same as those for event 2D.
• The inter-RAT blind handover triggered by event 1F is a special application. You need to measure the
pilot strength and quality scope of the best cell where the blind handover is to be triggered. Generally,
the inter-RAT blind handover is not needed and therefore does not need to be verified.
2. After videophone services are established, check, in the Uu Interface Trace dialog
box, that the UE sends the RNC an RRC_MEAS_RPRT message, which contains
the 3A report.
Run the RNC MML command SET UCORRMALGOSWITCH to deactive inter-RAT

handover based on coverage. In this step, deselect HO_INTER_RAT_CS_OUT_SWITCH and
//Deactivating Inter-RAT Handover Based on Coverage

If the handover grade of all target neighboring GSM cells is 3 and inter-RAT handovers decrease
significantly in some cells after the function of UMTS-to-GSM handover success rate
optimization is enabled, reconfigure U2GSuccThdForHoGrade0 (BSC6900, BSC6910),
U2GSuccThdForHoGrade1 (BSC6900, BSC6910), and U2GSuccThdForHoGrade2
(BSC6900, BSC6910) to smaller values.
• Hardware
• Other features
The feature WRFD-020303 Inter-RAT Handover Based on Coverage must be
configured before this feature is activated.
• License
For details about how to activate the license, see License Management Feature
Feature ID Feature Name License Control Item NE Sales

ID Unit
WRFD-020309 Inter-RAT Handover LQW1IRHO01RESE BSC6900 BSC6910 per Erl

Based on DL QoS
WRFD-020309 Inter-RAT Handover LQW1IRHO01RESM BSC6900 BSC6910 per

Based on DL QoS Mbps
The license control item in the DSP LICUSAGE command output is Inter-RAT
handover based on DL QoS (per Erl) or Inter-RAT handover based on DL QoS
(per Mbps).
primary and secondary operators according to method 1 when the sales unit is per Erl
or according to method 2 when the sales unit is per Mbps.
11.11.2 Activation
2. Run the RNC MML command ADD U2GNCELL to add an inter-RAT neighboring
cell.
3. Run the RNC MML command SET UQOSHO to set RNC-level parameters related
to Inter-RAT Handover Based on DL QoS.
4. Run the RNC MML command SET UQOSACT to turn on QoS switches for
different traffic classes.
//Activating Inter-RAT Handover Based on DL QoS
NPrioFlag=FALSE;
SET UQOSHO: LogicRncId=1, DlRscpQosHyst=10, DLQosMcTimerLen=20,
UsedFreqMeasQuantityForQos3A=CPICH_RSCP;
SET UQOSACT: BEQosPerform=YES, AMRQosPerform=YES, VPQosPerform=YES,
BeDlAct1=InterRatHO, DlQosAmrInterRatHoSwitch=YES,
DlQosWAmrInterRatHoSwitch=YES;
1. Log in to the RNC LMT and start Iub Interface Trace.

2. Check that the RNC sends an NBAP_DEDI_MEAS_INIT_REQ message to the
NodeB and that the message contains the event E and event F parameters.
3. Check that the NodeB sends an NBAP_DEDIC_MEAS_RPRT message to the RNC
and that the message contains the event E parameter.
event-triggered or periodic inter-frequency measurement.

deselect HO_INTER_RAT_CS_OUT_SWITCH and
2. Run the RNC MML command SET UQOSACT to turn off QoS switches for
//Deactivating Inter-RAT Handover Based on DL QoS
SET UQOSACT: BEQosPerform=NO, AMRQosPerform=NO, VPQosPerform=NO;
• Hardware
• Other features
• License
11.12.2 Activation
2. Run the RNC MML command ADD U2GNCELL to add an inter-RAT neighboring
cell.
3. Run the RNC MML command SET UQOSHO to set RNC-level parameters related
to Inter-RAT Handover Based on UL QoS.
4. Run the RNC MML command SET UQOSACT to turn on QoS switches for
//Activating Inter-RAT Handover Based on UL QoS
NPrioFlag=FALSE;
SET UQOSHO: LogicRncId=1, ULQosMcTimerLen=20,
UsedFreqMeasQuantityForQos3A=CPICH_RSCP;
SET UQOSACT: BEQosPerform=YES, AMRQosPerform=YES, VPQosPerform=YES,
BeUlAct1=InterRatHO, UlQosAmrInterRatHoSwitch=YES,
UlQosWAmrInterRatHoSwitch=YES;
1. Log in to the RNC LMT and start Uu Interface Trace.

2. Check that the RNC sends the UE an RRC_MEAS_CTRL message and that this
message contains event 6A measurement results. See Figure 11-9.
3. Check that the UE sends the RNC an RRC_MEAS_RPRT message and that this
message contains event 6A measurement results. See Figure 11-10.
Figure 11-10 RRC_MEAS_RPRT message
4. Check that the RNC sends the UE an RRC_MEAS_CTRL message and then starts
inter-RAT measurements in event-triggered or periodic mode. Then, check that the
corresponding traced message indicates that the RNC has sent the inter-RAT
measurement control message to the UE. See Figure 11-11.

deselect HO_INTER_RAT_CS_OUT_SWITCH and
2. Run the RNC MML command SET UQOSACT to turn off QoS switches for
//Deactivating Inter-RAT Handover Based on UL QoS
SET UQOSACT: BEQosPerform=NO, AMRQosPerform=NO, VPQosPerform=NO;
11.13 WRFD-020308 Inter-RAT Handover Phase 2
The optional feature Inter-RAT Handover Phase 2 supports NACC and inter-RAT PS handovers,
and therefore reduces the service interruption duration during inter-RAT PS handovers.
WRFD-020308 Inter-RAT Handover Phase 2 consists of:
• WRFD-02030801 NACC (Network Assisted Cell Change)
• WRFD-02030802 PS Handover Between UMTS and GPRS
• Hardware
The BSC must support the NACC RIM procedure and PS handovers.
• Other features
The configurations of the features on which this feature depends are complete. This
feature is required only when one or more of the following features are enabled:
▪ WRFD-020303 Inter-RAT Handover Based on Coverage
▪ WRFD-020305 Inter-RAT Handover Based on Service
▪ WRFD-020306 Inter-RAT Handover Based on Load
▪ WRFD-021200 HCS (Hierarchical Cell Structure)
• License
▪ The UE must support the NACC procedure and PS handover.
▪ The BSC must support the NACC RIM (RAN Information Management)
procedure and PS handover.
▪ The SGSN must support the NACC procedure and PS handover.
11.13.2 Deployment
For details about how to activate, verify, and deactivate this feature, see the following sections:
• 11.14 WRFD-02030801 NACC (Network Assisted Cell Change)
• 11.15 WRFD-02030802 PS Handover Between UMTS and GPRS
11.14 WRFD-02030801 NACC (Network Assisted Cell Change)
• Hardware
• Other features
feature depends on the feature WRFD-020308 Inter-RAT Handover Phase 2.
• License
Description.

ID
WRFD-02030801 NACC (Network LQW1NACC01 BSC6900 per Mbps

Assisted Cell BSC6910
Change)
The license control item in the DSP LICUSAGE command output is NACC
(Network Assisted Cell Change) (per Mbps).
▪ The UE must support the NACC procedure and comply with 3GPP Release
5 or later.
procedure.
11.14.2 Activation
HO_INTER_RAT_PS_OUT_SWITCH and
HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH under the
HandOver switch parameter and deselect
HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH under the HandOver
switch parameter.
When HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH is selected,

HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH does not take effect.
2. Run the RNC MML command ADD UEXT2GCELL (for new neighboring cell) or
MOD UEXT2GCELL (for the existing neighboring cell). In this step, set Inter-
RAT cell support RIM indicator to TRUE.
//Activating NACC
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH-
1&HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH-0&HO_INTER_RAT_PS_OUT_SWITCH-1;
//Setting Inter-RAT cell support RIM indicator to TRUE
MOD UEXT2GCELL: GSMCellIndex=1, SuppRIMFlag=TRUE;
To enable RIM messages to be exchanged through the CN, do as follows:

1. Trace messages over the Iu interface to check whether the RNC has sent a
RANAP_DIR_INFO_TRANSFER message to the CN to request RIM information.
2. Trace messages over the Iu interface to check whether the RNC has received a
RANAP_DIR_INFO_TRANSFER message from the CN as a response to the request
message.
3. Trace messages over the Uu interface to check whether there is an
RRC_CELL_CHANGE_ORDER_FROM_UTRAN message that carries system
information on the GSM side.
To enable RIM messages to be exchanged through Huawei proprietary eCoordinator, do as

follows:
Check the signaling messages over the Sg interface before the UMTS-to-GSM handover is
performed. If an RNC DIRECT INFORMATION TRANSFER message has been sent to the
eCoordinator and an ECO DIRECT INFORMATION TRANSFER message sent by the
eCoordinator has been received over the Sg interface, the WRFD-02030801 NACC (Network
Assisted Cell Change) feature takes effect.
To implement this feature, the UE should support NACC. Therefore, the NACC-supportive UEs are required for
activation.
1. Run the RNC MML command SET UCORRMALGOSWITCH to set

HO_INTER_RAT_PS_3G2G_CELLCHG_NACC_SWITCH in the HandOver
switch parameter to 0.
2. Run the RNC MML command MOD UEXT2GCELL to set Inter-RAT cell
support RIM indicator to FALSE.
//Deactivating NACC
MOD UEXT2GCELL: GSMCellIndex=1, SuppRIMFlag=FALSE;
11.15 WRFD-02030802 PS Handover Between UMTS and GPRS
This feature is not recommended for new projects (such as new deployment, reconstruction, and
optimization). Contact Huawei technical support if you want to enable this feature.
• Hardware
• Other features
feature depends on the feature WRFD-020308 PS Inter-RAT Handover Phase 2.
• License
Description.

ID
WRFD- PS Handover Between LQW1PSHO01 BSC6900 per Mbps

02030802 UMTS and GPRS BSC6910
The license control item in the DSP LICUSAGE command output is PS Handover
Between UMTS and GPRS (per Mbps).
procedure.
11.15.2 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH to open the

following switches in the HandOver switch parameter:
• HO_INTER_RAT_PS_OUT_SWITCH
• HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH
2. Run the RNC MML command ADD UEXT2GCELL to add a neighboring GSM
cell to the UMTS coverage and to set the Inter-RAT cell support PS HO indicator
parameter to TRUE.
3. Run the RNC MML command ADD U2GNCELL to add a neighboring GSM cell
for the UMTS cell.
4. (Optional) Run the RNC MML command SET UINTERRATHOCOV to set inter-
RAT handover measurement related parameters.
//Activating PS Handover Between UMTS and GPRS
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH-
ADD UEXT2GCELL: GSMCellIndex=1, GSMCellName="GSMCELL1", NBscIndex=1,
LdPrdRprtSwitch=ON, MCC="460", MNC="01", CnOpGrpIndex=1, LAC=1,
CfgRacInd=REQUIRE, RAC=1, CID=1, NCC=1, BCC=1, BcchArfcn=512,
RatCellType=GPRS, UseOfHcs=NOT_USED, SuppPSHOFlag=TRUE;
ADD U2GNCELL: RNCId=1, CellId=100, GSMCellIndex=1;
//(Optional) Setting inter-RAT handover measurement related parameters
SET UINTERRATHOCOV: InterRatReportMode=PERIODICAL_REPORTING,
FilterCoefOf2D2F=D4, InterRATFilterCoef=D6;
Check the value of the RNC counter VS.IRATHO.AttRelocOutPS (BSC6900, BSC6910). If the
value is not 0, this feature has been activated.
1. Run the RNC MML command SET UCORRMALGOSWITCH to set

HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH in the HandOver
switch parameter to 0.
2. Run the RNC MML command MOD UEXT2GCELL to set the SuppPSHOFlag
parameter to FALSE.
//Deactivating PS Handover Between UMTS and GPRS
SET UCORRMALGOSWITCH: HoSwitch=HO_INTER_RAT_PS_3G2G_RELOCATION_SWITCH-0;
MOD UEXT2GCELL: GSMCellIndex=1, SuppPSHOFlag=FALSE;
11.16 WRFD-020305 Inter-RAT Handover Based on Service

• Hardware
• Other features
• License
Description.

ID
WRFD-020305 Inter-RAT Handover LQW1SVHO01 BSC6900 per Erl

Based on Service BSC6910 per Mbps
The license control item in the DSP LICUSAGE command output is Inter system
Service Handover (per Erl) or Inter system Service Handover (per Mbps).
11.16.2 Activation
2. Run the RNC MML command ADD UEXT2GCELL to add a GSM cell.
3. Run the RNC MML command ADD U2GNCELL to add the GSM cell as a
neighboring cell of the UMTS cell.
4. Run the RNC MML command ADD UCELLHOCOMM. In this step, set both
Inter-RAT CS handover switch and Inter-RAT PS handover switch to ON.
5. Run the RNC MML command ADD UCELLINTERRATHONCOV (cell level) or
SET UINTERRATHONCOV (RNC level) to configure parameters related to non-
coverage-based inter-RAT handover to GSM.
settings prevail.
6. (Optional) Set the inter-RAT handover attribute as follows to facilitate feature
verification during tests. Do as the network plan during feature deployment on live
networks.
a. Run the RNC MML command SET UCORRMALGOSWITCH with
HO_INTER_RAT_RNC_SERVICE_HO_SWITCH under the
HandOver Switch parameter selected.
b. Run the RNC MML command MOD UTYPRABBASIC with the
Service Handover Indicator parameter set to
HO_TO_GSM_SHOULD_BE_PERFORM for the corresponding
service.
7. (Optional) Perform the following action to cancel the restriction on service-based
inter-RAT handovers for a certain operator: Run the RNC MML command ADD
UOPERALGOSWITCH with HO_IRAT_SERV_FORBID_SWITCH deselected
under the HandOver Switch parameter.
//Activating Inter-RAT Handover Based on Service
ADD UEXT2GCELL: GSMCellIndex=0, GSMCellName="GSMCell1", NBscIndex=1,
MCC="460", MNC="01", CnOpGrpIndex=0, LAC=H'1234, CfgRacInd=REQUIRE, RAC=0,
CID=1, NCC=1, BCC=1, BcchArfcn=512, RatCellType=GPRS, UseOfHcs=NOT_USED;
NPrioFlag=FALSE, InterRatAdjsQhcs=20;
ADD UCELLHOCOMM: CellId=1, CSServiceHOSwitch=ON, PSServiceHOSwitch=ON;
ADD UCELLINTERRATHONCOV: CellId=1, InterRATFilterCoef=D3, Hystfor3C=0,
TrigTime3C=D640, BSICVerify=REQUIRED, InterRATNCovHOCSThd=21,
InterRATNCovHOPSThd=21, InterRATHOAttempts=16, InterRATMeasTime=15;
//(Optional) Setting the inter-RAT handover attribute
SET UCORRMALGOSWITCH:HoSwitch=HO_INTER_RAT_RNC_SERVICE_HO_SWITCH-1;
MOD UTYPRABBASIC: RabIndex=1, SHInd=HO_TO_GSM_SHOULD_BE_PERFORM;
//(Optional) Canceling the restriction on service-based inter-RAT handovers
for a certain operator
ADD UOPERALGOSWITCH: CnOpIndex=0, HoSwitch=HO_IRAT_SERV_FORBID_SWITCH-0;
1. Click to display Uu Interface Trace on the RNC LMT. Under Uu Message Type,
select RRC_MEAS_CTRL.
2. After services are set up, view in the traced messages whether the RNC sends the UE
an inter-RAT measurement control message shown in Figure 11-12.
Figure 11-12 Inter-RAT measurement control message
2. After video phone services are established, check, in the Uu Interface Trace dialog
the 3C report.
the value of the "IE alternativeRABConfigurationRequest" is alternative-RAB-
1. Run the RNC MML command MOD UCELLHOCOMM. In this step, set both
Inter-RAT CS handover switch and Inter-RAT PS handover switch to OFF.
//Deactivating Inter-RAT Handover Based on Service
MOD UCELLHOCOMM: CellId=1, CSServiceHOSwitch=OFF, PSServiceHOSwitch=OFF;
11.17 WRFD-020306 Inter-RAT Handover Based on Load
• Hardware
• Other features
If this feature is used for HSDPA or HSUPA load control, the feature WRFD-010610
HSDPA Introduction Package or WRFD-010612 HSUPA Introduction Package has
been configured correspondingly before this feature is activated.
• License
Description.

ID
WRFD-020306 Inter-RAT LQW1LOHO01 BSC6900 per Erl

Handover Based on BSC6910 per Mbps
Load
The license control item in the DSP LICUSAGE command output is Inter system
Load Handover (per Erl) or Inter system Load Handover (per Mbps).
11.17.2 Activation

inter-RAT handover. In this step, select HO_INTER_RAT_CS_OUT_SWITCH
and HO_INTER_RAT_PS_OUT_SWITCH under the HandOver Switch
parameter.
2. (Optional) Set the inter-RAT handover attribute as follows to facilitate feature
verification during tests. Do as the network plan during feature deployment on live
networks.
a. Run the RNC MML command SET UCORRMALGOSWITCH with
HO_INTER_RAT_RNC_SERVICE_HO_SWITCH under the
HandOver Switch parameter selected.
b. Run the RNC MML command MOD UTYPRABBASIC with the
Service Handover Indicator parameter set to
HO_TO_GSM_SHOULD_BE_PERFORM for the corresponding
service.
3. Run the RNC MML command ADD UCELLALGOSWITCH with UL_UU_LDR
under the Switch for Cell Load Control parameter selected to enable the uplink air-
interface LDR algorithm.
4. Run the RNC MML command ADD UCELLALGOSWITCH with DL_UU_LDR
under the Switch for Cell Load Control parameter selected to enable the downlink
air-interface LDR algorithm.
5. Run the RNC MML command ADD UCELLALGOSWITCH with
CELL_CREDIT_LDR under the Switch for Cell Load Control parameter selected
to enable the cell credit LDR algorithm.
6. Run the RNC MML command SET ULDCALGOPARA with
NODEB_CREDIT_LDR_SWITCH (NodeB level) or
LCG_CREDIT_LDR_SWITCH (cell group level) under the load control
algorithm switch parameter selected to enable credit load control algorithm.
7. Run the RNC MML command ADD UNODEBALGOPARA with
NODEB_CREDIT_LDR (NodeB level) or LCG_CREDIT_LDR (cell group level)
under the NodeB LDC algorithm switch parameter selected to enable the credit load
congestion control algorithm.
Performing 3 to 7 facilitates feature verification during lab tests. On a live network, set the parameters
according to the network plan.
8. Run the RNC MML command ADD UEXT2GCELL to add a GSM cell.
9. Run the RNC MML command ADD U2GNCELL to add the GSM cell as a
neighboring cell of the UMTS cell.
10. Run the RNC MML command ADD UCELLLDR to set the inter-RAT handover
policy for the UMTS cell. In this step, set DL LDR fourth action to
CSInterRatShouldBeLDHO, DL LDR fifth action to
PSInterRatShouldBeLDHO, UL LDR fourth action to
CSInterRatShouldBeLDHO, and UL LDR fifth action to
PSInterRatShouldBeLDHO.
Setting UL/DL LDR first action to CSInterRatShouldBeLDHO and UL/DL LDR second action to
PSInterRatShouldBeLDHO facilitates feature verification during lab tests. On a live network, set the
parameters according to the network plan.
11. Run the RNC MML command MOD UCELLLDM with the following parameters
set to appropriate values: UL LDR trigger threshold, UL LDR release threshold,
DL LDR trigger threshold, DL LDR release threshold, and DL State Trans
Hysteresis threshold.
12. Run the RNC MML command MOD UNODEBLDR with the UL LDR Credit SF
reserved threshold parameter set to an appropriate value.
13. Run the RNC MML command SET ULDCPERIOD with the LDR period timer
length parameter set to an appropriate value.
14. Run the RNC MML command ADD UCELLINTERRATHONCOV (cell level) or
SET UINTERRATHONCOV (RNC level) to configure parameters related to non-
coverage-based inter-frequency handover to GSM.
settings prevail.
//Activating Inter-RAT Handover Based on Load
1&HO_INTER_RAT_PS_OUT_SWITCH-1&HO_INTER_RAT_RNC_SERVICE_HO_SWITCH-1;
MOD UTYPRABBASIC: RabIndex=1, SHInd=HO_TO_GSM_SHOULD_BE_PERFORM;
SET ULDCALGOPARA: LdcSwitch=NODEB_CREDIT_LDR_SWITCH-1&LCG_CREDIT_LDR_SWITCH-
1;
ADD UNODEBALGOPARA: IDTYPE=BYNAME, NodeBName="NodeB1",
NodeBLdcAlgoSwitch=IUB_LDR-1, NodeBHsdpaMaxUserNum=3840,
NodeBHsupaMaxUserNum=3840;
ADD UEXT2GCELL: GSMCellIndex=2, GSMCellName="2", NBscIndex=2,
LdPrdRprtSwitch=OFF, MCC="460", MNC="07", CnOpGrpIndex=1, LAC=H'0012,
CfgRacInd=REQUIRE, RAC=H'01, CID=2, NCC=2, BCC=2, BcchArfcn=1000,
RatCellType=GSM, UseOfHcs=NOT_USED;
ADD U2GNCELL: RncId=1, CellId=1, GSMCellIndex=2, BlindHoFlag=TRUE,
ADD UCELLLDR: CellId=1, DlLdrFourthAction=CSInterRatShouldBeLDHO,
DlLdrFifthAction=PSInterRatShouldBeLDHO,
UlLdrFourthAction=CSInterRatShouldBeLDHO,
UlLdrFifthAction=PSInterRatShouldBeLDHO;
MOD UCELLLDM: CellId=1, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70,
DlLdrRelThd=60, DlLdTrnsHysTime=1000;
MOD UNODEBLDR: IDTYPE=BYNAME, NodeBName="nodeb1", UlLdrCreditSfResThd=SF256;
SET ULDCPERIOD: LdrPeriodTimerLen=10;
ADD UCELLINTERRATHONCOV: CellId=1, InterRATFilterCoef=D3, Hystfor3C=0,
TrigTime3C=D640, BSICVerify=REQUIRED, InterRATNCovHOCSThd=21,
InterRATNCovHOPSThd=21, InterRATHOAttempts=16, InterRATMeasTime=15;
1. Initiate Iu interface message tracing and Uu interface message tracing on the RNC
LMT.
2. Use a UE in the UMTS cell to call another UE in the same cell.
The call is set up successfully.
3. Run the RNC MML command MOD UCELLLDM and set the UlLdrTrigThd
(BSC6900, BSC6910) and DlLdrTrigThd (BSC6900, BSC6910) parameters to reduce the
uplink and downlink LDR threshold for CELL_A11, respectively.
4. Trace the following messages on the Iu interface: the
RANAP_RELOCATION_REQUIRED message from the RNC to the CN, the
RANAP_RELOCATION_COMMAND message from the CN to the RNC, the
RANAP_IU_RELEASE_COMMAND message from the CN to the RNC, and the
RANAP_IU_RELEASE_COMPLETE message from the RNC to the CN.
5. Trace the following message on the Uu interface: the
RRC_HO_FROM_UTRAN_CMD_GSM message from the RNC to the UE.
2. After videophone services are established, check, in the Uu Interface Trace dialog
the 3A report.
1. Run the RNC MML command MOD UCELLLDR to deactivate the load-based
handover. In this step, set DL LDR fourth action, DL LDR fifth action, UL LDR
fourth action, and UL LDR fifth action to NoAct.
2. Run the RNC MML command SET UCORRMALGOSWITCH to deactivate the
inter-RAT handover. In this step, deselect the
HO_INTER_RAT_PS_OUT_SWITCH check boxes under the parameter
HandOver Switch.
//Deactivating Inter-RAT Handover Based on Load
MOD UCELLLDR: CellId=1, DlLdrFourthAction=NoAct, DlLdrFifthAction=NoAct,
UlLdrFourthAction=NoAct, UlLdrFifthAction=NoAct;
11.18 WRFD-020310 3G/2G Common Load Management
• Hardware
• Other features
This feature can be enabled when at least one of the following features is activated:
▪ WRFD-020305 Inter-RAT Handover Based on Service
▪ WRFD-020306 Inter-RAT Handover Based on Load
▪ WRFD-021200 HCS (Hierarchical Cell Structure)
▪ WRFD-020400 DRD Introduction Package
▪ WRFD-020308 Inter-RAT Handover Phase 2
• License
Description.
Feature ID Feature Name License Control Item NE Sales

ID Unit
WRFD-020310 3G/2G Common LQW1UGCLM01 BSC6900 BSC6910 per Erl

Load Management per
Mbps
The license control item in the DSP LICUSAGE command output is 3G/2G
Common Load Management (per Erl) or 3G/2G Common Load Management
(per Mbps).
The CN and BSS must support this feature.
Before deploying this feature, ensure that the Handover Request Acknowledge
messages sent from GSM to UMTS carry load information of GSM cells, because the
RNC needs to determine whether to allow a UMTS-to-GSM handover based on load
information of GSM cells.
11.18.2 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH to enable the inter-
RAT handover. In this step, select HO_INTER_RAT_CS_OUT_SWITCH and
HO_INTER_RAT_PS_OUT_SWITCH from the HandOver Switch list.
2. Run the RNC MML command SET UINTERRATHONCOV to enable the 3G/2G
common load management function. In this step, select the Send Load Info to GSM
Ind and NCOV Reloc Ind Based on GSM Cell Load.
3. Run the RNC MML command ADD UEXT2GCELL to add a GSM cell
neighboring to the UMTS coverage.
4. Run the RNC MML command ADD U2GNCELL to set a GSM cell as the UMTS
cell's neighboring cell.
//Activating 3G/2G Common Load Management
SET UINTERRATHONCOV: SndLdInfo2GsmInd=ON, NcovHoOn2GldInd=ON;
ADD UEXT2GCELL: GSMCellIndex=2, GSMCellName="2", NBscIndex=2,
LdPrdRprtSwitch=OFF, MCC="460", MNC="07", CnOpGrpIndex=1, LAC=H'0012,
CfgRacInd=REQUIRE, RAC=H'01, CID=2, NCC=2, BCC=2, BcchArfcn=1000,
RatCellType=GSM, UseOfHcs=NOT_USED;
ADD U2GNCELL: RncId=1, CellId=2, GSMCellIndex=2, BlindHoFlag=TRUE,
1. Run the RNC MML command LST UINTERRATHONCOV to check whether the
parameters Send Load Info to GSM Ind and NCOV Reloc Ind based on GSM cell
load are set to ON.
2. Run the RNC MML command LST U2GNCELL to ensure that the inter-RAT
neighboring cell for the GSM system is added correctly.
Consult Huawei engineers about the verification solution to obtain professional technical support.
Run the RNC MML command SET UINTERRATHONCOV to set the parameter Send Load
Info to GSM Ind to OFF and the parameter NCOV Reloc Ind based on GSM cell load to
OFF.
//Deactivating 3G/2G Common Load Management
SET UINTERRATHONCOV: SndLdInfo2GsmInd=OFF, NcovHoOn2GldInd=OFF;
This feature consists of the intra-frequency HSDPA handover, inter-frequency HSDPA

handover, and inter-RAT HSDPA handover.
Requirements
• Hardware
• Other features
For details, see 9.1 WRFD-01061006 HSDPA Mobility Management.
• License
This feature is controlled by the license for WRFD-010610 HSDPA Introduction
Package. For details about this license, see HSDPA Feature Parameter Description.
Deployment
The methods of activating intra-frequency, inter-frequency, and inter-RAT handovers are the
same for HSDPA users and R99 users. For the method of activating a function in the WRFD-
01061006 HSDPA Mobility Management feature, see the method of activating the same function
for R99 UEs in following sections:
• 11.1 WRFD-020201 Intra NodeB Softer Handover
• 11.2 WRFD-020202 Intra RNC Soft Handover
• 11.3 WRFD-020203 Inter RNC Soft Handover
• 11.4 WRFD-020301 Intra Frequency Hard Handover
• 11.7 WRFD-020302 Inter Frequency Hard Handover Based on Coverage
• 11.8 WRFD-020304 Inter Frequency Hard Handover Based on DL QoS
• "Engineering Guidelines" in Inter Frequency Load Balance Feature Parameter Description

• 11.10 WRFD-020303 Inter-RAT Handover Based on Coverage
• 11.11 WRFD-020309 Inter-RAT Handover Based on DL QoS
• 11.16 WRFD-020305 Inter-RAT Handover Based on Service
• 11.17 WRFD-020306 Inter-RAT Handover Based on Load
To enable the function of optimized HSDPA serving cell change, perform the following steps:
1. Collect the values of VS.HSDPA.MeanChThroughput (BSC6900, BSC6910) and
VS.AM.RLC.Rtx.HsdpaTrf.PDU (BSC6900,
BSC6910)/VS.RLC.AM.Tx.HsdpaTrf.PDU (BSC6900, BSC6910) for the purpose of
network performance comparison before and after this function is enabled.
2. Activate the function of optimized HSDPA serving cell change.
Run the NodeB MML command SET NODEBALGPARA with
HSDPASERCELLCHOPTSW set to ON.
MML command example:
SET NODEBALGPARA: HSDPASERCELLCHOPTSW=ON;
Batch modification on the MAE-Deployment is supported.

3. Check whether the function takes effect.
a. Log in to the NodeB WebLMT.
b. In the main window of the NodeB WebLMT, choose Trace.
c. In the navigation tree of the displayed Trace page, choose Trace >
UMTS Services. Double-click User Trace.
d. On the Iub page, choose the three red-framed items shown in Figure 11-13,
and click Submit.
Figure 11-13 Iub message trace
e. Check the tracing result.

During an intra-NodeB HSDPA serving cell change:
• If the RAT2TRM_RECFG_BEARER_REQ message arrives
after the ID-NEC-HSDPA-COMMIT-RESPONSE message,
this function has taken effect.
• If the RAT2TRM_RECFG_BEARER_REQ message arrives
prior to the ID-NEC-HSDPA-COMMIT-RESPONSE message,
this function does not take effect.
Figure 11-14 shows an example, in which this feature takes effect.
Figure 11-14 Example of the Iub message tracing result
4. (Optional) Deactivate the function of optimized HSDPA serving cell change.
Run the NodeB MML command SET NODEBALGPARA with
HSDPASERCELLCHOPTSW set to OFF.
MML command example:
SET NODEBALGPARA: HSDPASERCELLCHOPTSW=OFF;
11.20 Compressed Mode
11.20.1 When to Use Compressed Mode
Compressed mode must be enabled if inter-frequency and inter-RAT handovers are required. To
ensure service continuity, HLS compressed mode and SF/2 compressed mode must be enabled,
and the two compression modes can be selected by setting related threshold parameters.
Halving the SF based on channelization code reallocation is a special algorithm for
implementing SF/2 compressed mode. It is controlled by a switch. It is recommended that this
algorithm be enabled.
• Hardware
• Other features
• License
11.20.3 Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH with

CMCF_DL_HLS_SWITCH and CMCF_UL_HLS_SWITCH selected under the
CMCF Algorithm Switch parameter to enable downlink and uplink higher-layer
scheduling in compressed mode.
2. Run the RNC MML command SET UCMCF with DL SF Threshold and UL SF
Threshold set to appropriate values so that the RNC can determine whether to use
higher-layer scheduling or halved SF in compressed mode according to the SFs used
in the downlink and uplink.
3. When SF/2 compressed mode is used, it is recommended that the function of
channelization code reallocation be used to obtain the halved SF for compressed
mode. To enable this function, run the RNC MML command MOD
UCELLALGOSWITCH with DL CM Avoid Alternative Scrambling Code
Switch set to ON.
SET UCORRMALGOSWITCH: CmcfSwitch= CMCF_DL_HLS_SWITCH-1& CMCF_UL_HLS_SWITCH-
1;
SET UCMCF: DlSFTurnPoint=D64, UlSFTurnPoint=D64;
MOD UCELLALGOSWITCH: CellId=01, DlCMAvoidChgScCodeSwitch=ON;
For detailed operations, see Feature Configuration Using the MAE-Deployment.

Table 11-1 Configuring parameters on the MAE-Deployment
SN MO NE Parameter Parameter ID Remarks
Name
1 UCORRMALGOSWITCH RNC CMCF CmcfSwitch (BSC6900, Batch

Algorithm BSC6910) modification
Switch on the
MAE-
Deployment
is
supported.
2 UCMCF RNC DL SF DlSFTurnPoint (BSC6900, Batch

Threshold BSC6910) modification
on the
MAE-
Deployment
is
supported.
UL SF UlSFTurnPoint (BSC6900, Batch

Threshold BSC6910) modification
on the
MAE-
Deployment
is
supported.
4 UCELLALGOSWITCH RNC DL CM DlCMAvoidChgScCodeSwitch Batch

Avoid (BSC6900, BSC6910) modification
Alternative on the
Scrambling MAE-
Code Deployment
Switch is
supported.
Higher Layer Scheduling
Observe the values of the following counters. If any of them is not zero, the compressed mode
with higher layer scheduling has taken effect.
• The VS.CM.ULHLS.Act.Att (BSC6900, BSC6910) counter measures the number of
uplink HLS compressed mode activation requests in a cell.
• The VS.CM.DLHLS.Act.Att (BSC6900, BSC6910) counter measures the number of
downlink HLS compressed mode activation requests in a cell.
SF/2
Observe the values of the following counters. If any of them is not zero, the SF/2 compressed
mode has taken effect.
• The VS.CM.ULSF2.Act.Att (BSC6900, BSC6910) counter measures the number of
uplink SF/2 compressed mode activation requests in a cell.
• The VS.CM.DLSF2.Act.Att (BSC6900, BSC6910) counter measures the number of
downlink SF/2 compressed mode activation requests in a cell.
Reallocation of a Channelization Code
The VS.CM.DLSF2.AltScramCode.UE.Mean (BSC6900, BSC6910) counter measures the

number of UEs that use SF/2 compressed mode in the downlink and obtain the halved SFs using
alternative scrambling codes. This counter will decrease after the algorithm of reallocating
channelization codes is enabled. Reallocating a channelization code is a special SF/2
compression algorithm. It is controlled by a dedicated switch. To check this algorithm, perform
the following operations:
1. Start Uu interface trace on the RNC LMT.
2. Enable two CS voice UEs to access a cell one by one. In the RRC_RB_RECFG
message, query the configured SF for the first UE. For example, as shown in the
following figure, the UE is configured to use SF128 and the code number is 9.
3. Check whether the RNC sends a measurement control message

"RRC_MEAS_CTRL" to the UE and whether this message contains 2D
measurement information.
4. Perform attenuation on signals sent to the UE who first accesses the cell to trigger a
2D measurement report of the UE.
5. Check whether the UE has sent an RRC_MEAS_RPRT message to the RNC and
whether this message contains an event 2D measurement report, as shown in the
following figure.
6. The reallocation channelization code algorithm will take effect if the following
conditions are met: The RNC sends an RRC_PH_CH_RECFG signaling message to
the UE. The downlink channel codes are reconfigured as different channel numbers.
The scrambling code remains unchanged. As shown in the following figure, the
channelization code is reconfigured as SF128, the code number is changed to 10, and
the scrambling code remains the same.
Both high layer scheduling compressed mode and SF/2 compressed mode must be enabled. This
section describes only the methods for deactivating the channelization code reallocation
algorithm.
Run the RNC MML command MOD UCELLALGOSWITCH with DL CM Avoid

Alternative Scrambling Code Switch set to OFF.
MOD UCELLALGOSWITCH: CellId=01, DlCMAvoidChgScCodeSwitch=OFF;

Table 11-2 Configuring parameters on the MAE-Deployment
SN MO NE Parameter Parameter ID Remarks
Name
1 UCELLALGOSWITCH RNC DL CM DlCMAvoidChgScCodeSwitch Batch

Avoid (BSC6900, BSC6910) modification
Alternative on the
Scrambling MAE-
Code Switch Deployment
is
supported.
11.21 Inter-PLMN Handover
11.21.1 When to Use Inter-PLMN Handover
Enable this function when a UE needs to be handed over from a cell deployed by the serving
operator to a neighboring cell deployed by another operator.
11.21.2 Deployment
11.21.2.1 Requirements
• Hardware
• Other features
• License
11.21.2.2 Data Preparation
Parameter Parameter ID Setting Data Remarks
Name Notes Source
Intra InterPlmnHoAllowedIntraRat To Radio NE: RNC

RAT (BSC6900, BSC6910) activate network MO:
Inter this plan UOPERATORSHARINGMODE
Plmn Ho function, (internal) Batch modification on the
Allowed set the MAE-Deployment is supported.
parameter
to YES.
Inter InterPlmnHoAllowedInterRat To
RAT (BSC6900, BSC6910) activate
Inter this
Plmn Ho function,
Allowed set the
parameter
to YES.
Cn CnOpIndex (BSC6900, Set this Radio NE: RNC

Operator BSC6910) parameter network MO: UINTERPLMNHOLIST
Index based on plan Batch modification on the
the (negotiated MAE-Deployment is supported.
negotiated with the
data peer)
among
operators.
The value
of this
parameter
must be
unique.
Target TarRAT (BSC6900, BSC6910) Set this

Radio parameter
System based on
the
negotiated
data
among
operators.
Target TarCnOpIndex (BSC6900, Set this

Operator BSC6910) parameter
Index based on
the
negotiated
data
among
operators.
Parameter Parameter ID Setting Data Remarks
Name Notes Source
The value
of this
parameter
must be
unique.
11.21.2.3 Activation
1. Run the RNC MML command SET UOPERATORSHARINGMODE with both

Intra RAT Inter Plmn Ho Allowed and Inter RAT Inter Plmn Ho Allowed set to
YES.
2. (Optional) Perform this action when an inter-PLMN handover list is required for
filtering neighboring cells. Run the RNC MML command ADD
UINTERPLMNHOLIST with Cn Operator Index, Target Radio System, and
Target Operator Index specified to configure an intra-RAT and inter-RAT inter-
PLMN handover list.
//Enabling the functions of intra-RAT inter-PLMN handovers and inter-RAT
inter-PLMN handovers
SET UOPERATORSHARINGMODE: InterPlmnHoAllowedIntraRat=YES,
InterPlmnHoAllowedInterRat=YES;
//(Optional) Configuring an intra-RAT and inter-RAT inter-PLMN handover list
ADD UINTERPLMNHOLIST: CnOpIndex=0, TarRAT=U2U, TarCnOpIndex=1;
ADD UINTERPLMNHOLIST: CnOpIndex=0, TarRAT=U2G, TarCnOpIndex=1;
Based on the parameter configurations involved in 11.21.2.2 Data Preparation, perform the following
operations to activate this feature:
11.21.2.4 Activation Observation
Intra-RAT Inter-PLMN Handover
Counters contained in the CELL.Ncell function subset can be used to determine whether the
intra-RAT inter-PLMN handover function takes effect and to monitor network performance after
the intra-RAT inter-PLMN handover function is enabled.
Measurement of these counters requires selecting related measurement items on the MAE and is
not performed by default.
Inter-RAT Inter-PLMN Handover

Counters contained in the IRATHO.Gcell function subset can be used to determine whether the
inter-RAT inter-PLMN handover function takes effect and to monitor network performance after
the inter-RAT inter-PLMN handover function is enabled.
Measurement of these counters requires selecting related measurement items on the MAE and is
not performed by default.
11.21.2.5 Deactivation
The following table describes the parameters for deactivating this function.
Parameter Name Parameter ID Setting Notes Remarks
Intra RAT Inter InterPlmnHoAllowedIntraRat Set this NE: RNC

Plmn Ho (BSC6900, BSC6910) parameter to MO:
Allowed NO. UOPERATORSHARINGMODE
Inter RAT Inter InterPlmnHoAllowedInterRat Set this Batch modification on the
Plmn Ho (BSC6900, BSC6910) parameter to MAE-Deployment is supported.
Allowed NO.
Deactivation can be performed using the MAE-Deployment or MML commands.

Run the RNC MML command SET UOPERATORSHARINGMODE with both Intra RAT
Inter Plmn Ho Allowed and Inter RAT Inter Plmn Ho Allowed set to NO.
//Disabling the functions of intra-RAT inter-PLMN handovers and inter-RAT
inter-PLMN handovers
SET UOPERATORSHARINGMODE: InterPlmnHoAllowedIntraRat=NO,
InterPlmnHoAllowedInterRat=NO;

None
None
11.21.5 Troubleshooting
None
12 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version with
which this document is released.
Base station controller parameter reference
• BSC6900 UMTS Parameter Reference: contains the parameters related to the BSC6900
equipment, transport, and radio access functions.
• BSC6910 UMTS Parameter Reference: contains the parameters related to the BSC6910
equipment, transport, and radio access functions.
NodeB parameter reference
• Node Parameter Reference: contains base station equipment and transport parameters.
• NodeBFunction Parameter Reference:contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.
You can find the EXCEL files of parameter reference for the software version on the live network from the product
documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter reference?
1. Open the EXCEL file of parameter reference.
2. On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, WRFD-170201.
3. Click OK. All parameters related to the feature are displayed.
13 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
Base station controller performance counter reference
• BSC6900 UMTS Performance Counter Reference:
contains the counters related to the
BSC6900 equipment, transport, and radio access functions.
• BSC6910 UMTS Performance Counter Reference:
contains the counters related to the
BSC6910 equipment, transport, and radio access functions.
NodeB performance counter reference
• Node Performance Counter Summary: contains base station equipment and transport
counters.
• NodeBFunction Performance Counter Summary:
contains all counters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.
You can find the EXCEL files of performance counter reference for the software version used on the live network
from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
1. Open the EXCEL file of performance counter reference.
2. On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, WRFD-170201.
3. Click OK. All counters related to the feature are displayed.
14 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
15 Reference Documents
Reference documents are as follows:

1. 3GPP TS 23.122, "Non Access Stratum functions related to Mobile Station (MS) in
idle mode"
2. 3GPP TS 24.008, "Mobile radio interface layer 3 specification; Core Network
Protocols - Stage 3"
3. 3GPP TS 25.304, "UE Procedures in Idle Mode and Procedures for Cell Reselection
in Connected Mode"
4. 3GPP TS 25.331, "RRC Protocol Specification"
5. 3GPP TS 23.060, "General Packet Radio Service (GPRS); Service description"
6. 3GPP TS 25.931, "UTRAN Functions, Examples on Signaling Procedures"
7. License Management Feature Parameter Description
8. CE Resource Management Feature Parameter Description
9. Load Control Feature Parameter Description
10. Directed Retry Decision Feature Parameter Description

11. Interoperability Between UMTS and LTE Feature Parameter Description
12. AMR Feature Parameter Description
13. DCCC Feature Parameter Description
14. Inter Frequency Load Balance Feature Parameter Description
15. SRNS Relocation and DSCR Feature Parameter Description

RAN Feature Documentation RAN22.1 - 07 20221201150622

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RAN Feature Documentation RAN22.1 - 07 20221201150622

Uploaded by

Copyright:

Available Formats

Handover

Handover Feature Parameter

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved.

Huawei Technologies Co., Ltd.

4 Inter-Frequency and Inter-RAT Handovers

7 Neighboring Cell Combination

8 Missing Neighboring Cell Detection

Feature Parameter Description documents are intended to acquaint readers with:

This issue does not include any changes.

RAN21.1 Draft A (2018-12-30)

Compared with Issue 01 (2018-03-30) of RAN20.1, Draft A (2018-12-30) of RAN21.1 includes

Change Change Description Parameter Change

Feature Added the function of Added the following parameters:

details, see the following • U2GSuccRateOptPSTrgtThld (BSC6900,

Editorial None None

1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations

Feature ID Description Supported by Base Supported Supported Supported

WRFD- Intra NodeB Yes Yes Yes No Yes

WRFD- Intra RNC Yes Yes Yes Yes Yes

WRFD- Inter RNC Yes Yes Yes Yes Yes

WRFD- HSDPA Yes Yes Yes Yes Yes

WRFD- HSUPA Yes Yes Yes Yes Yes

WRFD- HCS Yes Yes Yes Yes Yes

WRFD- Inter Yes Yes Yes Yes Yes

WRFD- Inter Yes Yes Yes Yes Yes

WRFD- Inter-RAT Yes Yes Yes Yes Yes

WRFD- Inter-RAT Yes Yes Yes Yes Yes

WRFD- Inter-RAT Yes Yes Yes Yes Yes

WRFD- NACC Yes Yes Yes Yes Yes

WRFD- Inter-RAT Yes Yes Yes Yes Yes

WRFD- Inter-RAT Yes Yes Yes Yes Yes

WRFD- 3G/2G Yes Yes Yes Yes Yes

2.1 Overview of Handover Types

Table 2-1 lists handover-related features and reference sections or documents.

Type Feature Name Reference

Intra- WRFD-020201 Intra NodeB Softer 3 Intra-Frequency Handover

WRFD-020203 Inter RNC Soft Handover

WRFD-020301 Intra Frequency Hard

WRFD-020103 Inter Frequency Load 4.4 Load-based Inter-Frequency

WRFD-02040004 Traffic Steering and Directed Retry Decision Feature

WRFD-020309 Inter-RAT Handover Based

WRFD-020306 Inter-RAT Handover Based 4.5 Load-based UMTS-to-GSM Handover

WRFD-020305 Inter-RAT Handover Based 4.7 Service-based UMTS-to-GSM

WRFD-020308 Inter-RAT Handover Phase 4.9 UMTS-to-GSM Handovers When

WRFD-02030801 NACC (Network Assisted 4.9 UMTS-to-GSM Handovers When

WRFD-02030802 PS Handover Between 4.10 UMTS-to-GSM PS Handover

WRFD-020310 3G/2G Common Load 4.11.6 Inter-RAT Load Information

WRFD-150220 Coverage Based PS Interoperability Between UMTS and LTE

WRFD-150217 Load Based PS Handover

Inter- WRFD-021200 HCS (Hierarchical Cell 4.8 Speed-based Inter-Frequency and

WRFD-01061204 HSUPA Mobility

2.2.1 WRFD-020201 Intra NodeB Softer Handover

2.2.5 WRFD-020302 Inter Frequency Hard Handover Based on Coverage

2.2.8 WRFD-020309 Inter-RAT Handover Based on DL QoS

2.2.11 WRFD-01061006 HSDPA Mobility Management

2.2.15 WRFD-02030801 NACC (Network Assisted Cell Change)

2.2.17 WRFD-020310 3G/2G Common Load Management

Intra-frequency handovers can be classified into the following two types:

Item Softer Handover Soft Handover

Scenario The UE is in the coverage The UE is in the coverage

Uplink signal The DivCtrlField (BSC6900, Selective combining is used.

whether to use MRC or