Mobility Management in Connected Mode Feature Parameter Description PDF

11/27/2019 Mobility Management in Connected Mode Feature Parameter Description
eRAN
eRAN13.1
Mobility Management in Connected
Mode Feature Parameter Description
Issue 05
Date 2019-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2019. 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 the property 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: http://www.huawei.com
https://support.huawei.com/hedex/pages/DOC110051112531189937/10/DOC110051112531189937/10/resources/hert/ref-ne/pdf/Mobility_Connecte… 1/120
Email: support@huawei.com
Contents
1 Change History
1.1 eRAN13.1 05 (2019-04-30)
1.2 eRAN13.1 04 (2019-01-21)
1.3 eRAN13.1 03 (2018-11-12)
1.4 eRAN13.1 02 (2018-06-30)
1.5 eRAN13.1 01 (2018-04-10)
1.6 eRAN13.1 Draft B (2018-03-30)
1.7 eRAN13.1 Draft A (2018-01-15) (FDD)
1.8 eRAN13.1 Draft A (2018-01-15) (TDD)
2 About This Document

2.1 Applicable RAT
2.2 Features in This Document
2.3 Feature Differences Between FDD and TDD
3 Overview of Mobility Management in Connected Mode
4 Basic Functions of Mobility Management in Connected Mode

4.1 Principles
4.1.1 Overall Process
4.1.2 Handover Function Initiation Decision
4.1.3 Processing Mode Selection
4.1.4 Measurement Configuration Delivery
4.1.4.1 Measurement Object
4.1.4.1.1 RAT Selection for Measurement
4.1.4.1.2 Frequency Selection for Measurement
4.1.4.1.3 Cell Selection for Measurement
4.1.4.2 Reporting Configurations
4.1.4.2.1 Measurement Events
4.1.4.2.2 Triggering Quantity and Reporting Quantity
4.1.4.2.3 Other Parameters
4.1.4.3 Other Configurations
4.1.5 Measurement Reporting
4.1.6 Target Cell or Frequency Decision
4.1.6.1 Processing Measurement Reports
4.1.6.2 Determining a Handover Policy
4.1.6.2.1 Handover Policies
4.1.6.2.2 Intra-RAT Handover Policy
4.1.6.2.3 Inter-RAT Handover Policy
4.1.6.3 Generating a Target Cell or Target Frequency List
4.1.7 Handover Execution
4.1.8 Retry and Penalty for Handover Failures
4.1.9 Compatibility Procedure Optimization
4.1.9.1 Handover Optimization Between UTRAN and E-UTRAN
4.1.9.2 Special Signaling Retransmission Optimization
4.1.9.3 E-UTRAN to GERAN PLMN Selection Optimization
4.1.9.4 Optimization of the Interaction Between Handover and E-RAB Management Procedures
4.1.9.5 Intra-E-UTRAN Handover Optimization
4.1.9.6 Signaling Optimization for UE's UTRAN Capability Query
4.2 Network Analysis
4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Others
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the CME
4.4.2 Activation Verification
4.4.3 Network Monitoring
5 Coverage-based Handover
5.1 Overview
5.1.1 Introduction to Handover Functions
5.1.2 Measurement-based Handover Functions
5.1.3 Blind Handover Functions
5.1.4 Event A2 Involved in Coverage-based Handover
5.1.5 Principles for Selecting UTRAN or GERAN for Inter-RAT Handovers
5.2 Coverage-based Intra-frequency Handover
5.2.1 Principles
5.2.2 Network Analysis
5.2.2.1 Benefits
5.2.2.2 Impacts
5.2.3 Requirements
5.2.3.1 Licenses
5.2.3.2 Software
5.2.3.3 Hardware
5.2.3.4 Others
5.2.4 Operation and Maintenance
5.2.4.1 Data Configuration
5.2.4.1.1 Data Preparation
5.2.4.1.2 Using MML Commands
5.2.4.1.3 Using the CME
5.2.4.2 Activation Verification
5.2.4.3 Network Monitoring
5.3 Coverage-based Inter-frequency Handover
5.3.1 Principles
5.3.1.1 Initiation Decision of Measurement-based Handover
5.3.1.1.1 Event A2
5.3.1.1.2 Event A1
5.3.1.2 Measurement Configuration Delivery
5.3.1.3 Target Cell Decision for Measurement-based Handover
5.3.1.3.1 Event A3
5.3.1.3.2 Event A4
5.3.1.3.3 Event A5
5.3.1.4 Principles of Blind Handover Functions
5.3.1.4.1 Preferential Blind Handover
5.3.1.4.2 Emergency Blind Handover
5.3.2.1 Benefits
5.3.2.2 Impacts
5.3.3 Requirements
5.3.3.1 Licenses
5.3.3.2 Software
5.3.3.3 Hardware
5.3.3.4 Others
5.4 Coverage-based Inter-RAT Handover to UTRAN
5.4.1 Principles
5.4.1.1.1 Event A2
5.4.1.1.2 Event A1
5.4.1.3 Target Cell Decision for Measurement-based Mode
5.4.1.3.1 Event B1
5.4.1.3.2 Event B2
5.4.1.4 Principles of Blind Handover
5.4.2.1 Benefits
5.4.2.2 Impacts
5.4.3 Requirements
5.4.3.1 Licenses
5.4.3.2 Software
5.4.3.3 Hardware
5.4.3.4 Others
5.5 Coverage-based Inter-RAT Handover to GERAN
5.5.1 Principles
5.5.2.1 Benefits
5.5.2.2 Impacts
5.5.3 Requirements
5.5.3.1 Licenses
5.5.3.2 Software
5.5.3.3 Hardware
5.5.3.4 Others
5.6 Coverage-based E-UTRAN to UTRAN CS/PS Steering
5.6.1 Principles
5.6.2.1 Benefits
5.6.2.2 Impacts
5.6.3 Requirements
5.6.3.1 Licenses
5.6.3.2 Software
5.6.3.3 Hardware
5.6.3.4 Others
6 Service-based Handover
6.1 Overview
6.2 Service-based Inter-frequency Handover
6.2.1 Principles
6.2.1.1 Handover Function Initiation Decision
6.2.1.3 Target Cell Determination
6.2.2.1 Benefits
6.2.2.2 Impacts
6.2.3 Requirements
6.2.3.1 Licenses
6.2.3.2 Software
6.2.3.3 Hardware
6.2.3.4 Others
6.3 Service-based Inter-RAT Handover to UTRAN
6.3.1 Principles
6.3.1.1 Handover Function Initiation Determination
6.3.2.1 Benefits
6.3.2.2 Impacts
6.3.3 Requirements
6.3.3.1 Licenses
6.3.3.2 Software
6.3.3.3 Hardware
6.3.3.4 Others
6.4 Service-based Inter-RAT Handover to GERAN
6.4.1 Principles
6.4.2.1 Benefits
6.4.2.2 Impacts
6.4.3 Requirements
6.4.3.1 Licenses
6.4.3.2 Software
6.4.3.3 Hardware
6.4.3.4 Others
7 Distance-based Handover
7.1 Overview
7.2 Distance-based Inter-frequency Handover
7.2.1 Principles
7.2.2.1 Benefits
7.2.2.2 Impacts
7.2.3 Requirements
7.2.3.1 Licenses
7.2.3.2 Software
7.2.3.3 Hardware
7.2.3.4 Others
7.3 Distance-based Inter-RAT Handover to UTRAN
7.3.1 Principles
7.3.2.1 Benefits
7.3.2.2 Impacts
7.3.3 Requirements
7.3.3.1 Licenses
7.3.3.2 Software
7.3.3.3 Hardware
7.3.3.4 Others
7.4 Distance-based Inter-RAT Handover to GERAN
7.4.1 Principles
7.4.2.1 Benefits
7.4.2.2 Impacts
7.4.3 Requirements
7.4.3.1 Licenses
7.4.3.2 Software
7.4.3.3 Hardware
7.4.3.4 Others
8 UL-quality-based Handover
8.1 Overview
8.2 UL-quality-based Inter-frequency Handover
8.2.1 Principles
8.2.1.1 Initiation Determination of Measurement-based Handover
8.2.1.2 Target Cell Determination for Measurement-based Mode
8.2.2.1 Benefits
8.2.2.2 Impacts
8.2.3 Requirements
8.2.3.1 Licenses
8.2.3.2 Software
8.2.3.3 Hardware
8.2.3.4 Others
8.3 UL-quality-based Inter-RAT Handover to UTRAN or GERAN
8.3.1 Principles
8.3.2.1 Benefits
8.3.2.2 Impacts
8.3.3 Requirements
8.3.3.1 Licenses
8.3.3.2 Software
8.3.3.3 Hardware
8.3.3.4 Others
9 Service-request-based Inter-frequency Handover

9.1 Principles
9.1.3 Target Cell Determination
9.2.1 Benefits
9.2.2 Impacts
9.3 Requirements
9.3.1 Licenses
9.3.2 Software
9.3.3 Hardware
9.3.4 Others
10 Frequency-priority-based Inter-frequency Handover

10.1 Principles
10.1.1 Initiation Determination of Measurement-based Handover
10.1.3 Target Cell Determination for Measurement-based Mode
10.1.4 Principles of Blind Handover
10.2.1 Benefits
10.2.2 Impacts
10.3 Requirements
10.3.1 Licenses
10.3.2 Software
10.3.3 Hardware
10.3.4 Others
11 Separate Mobility Policies to UTRAN for Multi PLMN (FDD)

11.1 Principles
11.2.1 Benefits
11.2.2 Impacts
11.3 Requirements
11.3.1 Licenses
11.3.2 Software
11.3.3 Hardware
11.3.4 Others
12 Separate Mobility Policies to GERAN for Multi PLMN

12.1 Principles
12.2.1 Benefits
12.2.2 Impacts
12.3 Requirements
12.3.1 Licenses
12.3.2 Software
12.3.3 Hardware
12.3.4 Others
13 Glossary
14 Reference Documents
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and "Reference Documents" chapters. These changes include:
Technical changes
Changes in functions and their corresponding parameters
Editorial changes
Improvements or revisions to the documentation
1.1 eRAN13.1 05 (2019-04-30)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Changed the QCI values in the MML command examples. For details, see 4.4.1.2 Using MML Commands, 6.3.4.1.2 Using MML Commands, and 6.4.4.1.2
Using MML Commands.
Added descriptions about not recommending service-based inter-RAT handovers for QCI 1 services. For details, see 6.3.1.1 Handover Function Initiation
Determination.
Added Carrier Aggregation as the reference for the frequency-priority-based handover in CA scenarios. For details, see 10.1 Principles.
Added configuration constraints on the target frequencies for the QCI with the highest priority in service-based inter-frequency handovers. For details,
see 6.2.1.2 Measurement Configuration Delivery.
1.2 eRAN13.1 04 (2019-01-21)

Technical Changes
None
Editorial Changes
Added the description about the UTRAN frequency to be contained in the delivered measurement configurations. For details, see 5.4.1.2 Measurement
Configuration Delivery.
Added the description about how the eNodeB determines whether to enable service-based inter-RAT handover to UTRAN for a UE. For details, see
6.3.1.1 Handover Function Initiation Determination.
Added other parameters related to event A5. For details, see 4.1.4.2.3 Other Parameters.
Changed the value of the GERAN version parameter in the MML command for adding the neighbor relationship with a GERAN cell. For details, see
4.4.1.2 Using MML Commands.
Revised the descriptions of capabilities of handovers to the UTRAN and GERAN. For details, see 4.1.6.2.3 Inter-RAT Handover Policy.
1.3 eRAN13.1 03 (2018-11-12)

Technical Changes
None
Editorial Changes
Modified the description about how eNodeB acts when another gap pattern needs to be set up during the gap-assisted measurement. For details, see
4.1.4.3 Other Configurations.
Added descriptions about intra-RAT handovers. For details, see 4.1.7 Handover Execution.
1.4 eRAN13.1 02 (2018-06-30)

Technical Changes
Change Description Parameter Change RAT Base Station Model
Change Description Parameter Change RAT Base Station Model
Supported QCI-specific inter-frequency event A2 Added the following parameter: FDD 3900 and 5900 series base
RSRP thresholds for different operators. For eNBCnOpQciRsvdPara.RsvdPara14 TDD stations
details, see 5.3.1.1.1 Event A2.
DBS3900 LampSite and DBS5900
LampSite
BTS3912E
BTS3911E
Editorial Changes
Revised descriptions in this document.
1.5 eRAN13.1 01 (2018-04-10)

Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.6 eRAN13.1 Draft B (2018-03-30)

Technical Changes
None
Editorial Changes
Deleted descriptions of the speed-based inter-frequency handover (FDD).

Added deactivation command examples. For details, see the respective "Using MML Commands" sections.
1.7 eRAN13.1 Draft A (2018-01-15) (FDD)

This issue introduces the following changes to eRAN12.1 02 (2017-05-30).
Technical Changes
Change Description Parameter Change Base Station Model
Added support for preferential handover to the Added parameters: 3900 and 5900 series base stations
highest-priority frequency during frequency-priority- IntraRatHoComm.FreqPriIFHoWaitingTimer
based inter-frequency handovers. For details, see 10 EutranInterNFreq.MeasPriorityForFreqPriHo LampSite
Frequency-priority-based Inter-frequency Handover.
BTS3912E
BTS3911E
BTS3203E
BTS3202E
Supported the signal quality type (RSRP or RSRQ) Added parameters: 3900 and 5900 series base stations
used to trigger coverage-based inter-RAT handovers InterRatHoCommGroup.A2BasedInterRatHoTrigQuan
to be dependent on the QCI of highest-priority
LampSite
services on individual UEs. For details, see:
BTS3912E
5.4.1.1 Initiation Decision of Measurement-based
BTS3911E
Handover
BTS3203E
BTS3202E
https://support.huawei.com/hedex/pages/DOC110051112531189937/10/DOC110051112531189937/10/resources/hert/ref-ne/pdf/Mobility_Connect… 10/120
Changed the number of handover retries for an inter- Supported the 3900 and 5900 series base stations
RAT handover failure from a fixed value of 10 to a CellHoParaCfg.InterRatUuHoFailRetryTimes
configurable value. For details, see 4.1.8 Retry and parameter in FDD.
LampSite
Penalty for Handover Failures.
BTS3912E
BTS3911E
BTS3203E
BTS3202E
Supported QCI-specific inter-RAT event A2 RSRP Added parameters: 3900 and 5900 series base stations
thresholds for different operators. CnOperatorQciPara.InterRatA2RsrpThldOffset
LampSite
BTS3912E
BTS3911E
Added service-request-based inter-frequency None 3900 and 5900 series base stations
handover. For details, see 9 Service-request-based
Inter-frequency Handover.
LampSite
BTS3912E
BTS3911E
BTS3203E
BTS3202E
Added LBFD-131111 Mobility between LTE TDD and None 3900 and 5900 series base stations
LTE FDD.
LampSite
BTS3912E
BTS3911E
BTS3203E
BTS3202E
Editorial Changes
Combined Overview of Mobility Management in Connected Mode, Intra-RAT Mobility Management in Connected Mode, and Inter-RAT Mobility
Management in Connected Mode.
Incorporated both FDD and TDD descriptions into this document.
Reorganized this document using a new template.
1.8 eRAN13.1 Draft A (2018-01-15) (TDD)

This issue introduces the following changes to eRAN12.1 03 (2017-07-29).
Technical Changes
Added support for preferential handover to the Added parameters: 3900 and 5900 series base stations
highest-priority frequency during frequency-priority- IntraRatHoComm.FreqPriIFHoWaitingTimer
based inter-frequency handovers. For details, see 10 EutranInterNFreq.MeasPriorityForFreqPriHo LampSite
Frequency-priority-based Inter-frequency Handover.
BTS3205E
Supported the signal quality type (RSRP or RSRQ) Added parameters: 3900 and 5900 series base stations
used to trigger coverage-based inter-RAT handovers InterRatHoCommGroup.A2BasedInterRatHoTrigQuan
to be dependent on the QCI of highest-priority
LampSite
services on individual UEs. For details, see:
BTS3205E
5.4.1.1 Initiation Decision of Measurement-based
Handover
Supported QCI-specific inter-RAT event A2 RSRP Added parameters: 3900 and 5900 series base stations
thresholds for different operators. CnOperatorQciPara.InterRatA2RsrpThldOffset
LampSite
Added TDLOFD-131210 Separate Mobility Policies to None 3900 and 5900 series base stations
GERAN for Multi PLMN.
LampSite
BTS3205E
Changed the optional feature TDLOFD-001050 None 3900 and 5900 series base stations
Mobility between LTE TDD and LTE FDD to a basic
feature TDLBFD-001050 Mobility between LTE TDD
LampSite
and LTE FDD.
BTS3205E
Added support for services with QCIs of 75 and 79 None Macro/Micro/LampSite

and adjusted the priority of services with each QCI.
For details, see 4.1.4.2.1 Measurement Events.
Editorial Changes
Combined Overview of Mobility Management in Connected Mode, Intra-RAT Mobility Management in Connected Mode, and Inter-RAT Mobility
Management in Connected Mode.
Incorporated both FDD and TDD descriptions into this document.
Reorganized this document using a new template.
2 About This Document
2.1 Applicable RAT

This document applies to FDD/TDD.
2.2 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LBFD-002018 Mobility Management 4 Basic Functions of Mobility Management in

Connected Mode
LBFD-00201801 Coverage Based Intra-frequency Handover 5.2 Coverage-based Intra-frequency Handover
LBFD-00201802 Coverage Based Inter-frequency Handover 5.3 Coverage-based Inter-frequency Handover
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and 5.4 Coverage-based Inter-RAT Handover to
UTRAN UTRAN
LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and 5.5 Coverage-based Inter-RAT Handover to
GERAN GERAN
LOFD-001078 E-UTRAN to UTRAN CS/PS Steering 5.6 Coverage-based E-UTRAN to UTRAN CS/PS
Steering
LBFD-00201805 Service Based Inter-frequency Handover 6.2 Service-based Inter-frequency Handover
LOFD-001043 Service based Inter-RAT handover to UTRAN 6.3 Service-based Inter-RAT Handover to UTRAN
LOFD-001046 Service based Inter-RAT handover to GERAN 6.4 Service-based Inter-RAT Handover to GERAN
LBFD-00201804 Distance Based Inter-frequency Handover 7.2 Distance-based Inter-frequency Handover
LOFD-001072 Distance based Inter-RAT handover to UTRAN 7.3 Distance-based Inter-RAT Handover to
UTRAN
LOFD-001073 Distance based Inter-RAT handover to GERAN 7.4 Distance-based Inter-RAT Handover to
GERAN
LBFD-131111 Mobility between LTE TDD and LTE FDD 5.3 Coverage-based Inter-frequency Handover
LOFD-070216 Separate Mobility Policies to UTRAN for Multi 11 Separate Mobility Policies to UTRAN for Multi
PLMN PLMN (FDD)
LOFD-111204 Separate Mobility Policies to GERAN for Multi 12 Separate Mobility Policies to GERAN for Multi
PLMN PLMN
This document describes the following TDD features.
TDLBFD-002018 Mobility Management 4 Basic Functions of Mobility Management in

Connected Mode
TDLBFD-00201801 Coverage Based Intra-frequency Handover 5.2 Coverage-based Intra-frequency Handover
TDLBFD-00201802 Coverage Based Inter-frequency Handover 5.3 Coverage-based Inter-frequency Handover
TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and 5.4 Coverage-based Inter-RAT Handover to
UTRAN UTRAN
TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and 5.5 Coverage-based Inter-RAT Handover to
GERAN GERAN
TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering 5.6 Coverage-based E-UTRAN to UTRAN CS/PS
Steering
TDLBFD-00201805 Service Based Inter-frequency Handover 6.2 Service-based Inter-frequency Handover
TDLOFD-001043 Service based Inter-RAT handover to UTRAN 6.3 Service-based Inter-RAT Handover to UTRAN
TDLOFD-001046 Service based Inter-RAT handover to GERAN 6.4 Service-based Inter-RAT Handover to GERAN
TDLBFD-00201804 Distance Based Inter-frequency Handover 7.2 Distance-based Inter-frequency Handover
TDLOFD-001072 Distance based Inter-RAT handover to UTRAN 7.3 Distance-based Inter-RAT Handover to
UTRAN
TDLOFD-001073 Distance based Inter-RAT handover to GERAN 7.4 Distance-based Inter-RAT Handover to
GERAN
TDLOFD-070228 Service-Request Based Inter-frequency Handover 9 Service-request-based Inter-frequency

Handover
TDLBFD-001050 Mobility between LTE TDD and LTE FDD 5.3 Coverage-based Inter-frequency Handover
TDLOFD-131210 Separate Mobility Policies to GERAN for Multi 12 Separate Mobility Policies to GERAN for Multi
PLMN PLMN
2.3 Feature Differences Between FDD and TDD
FDD Feature TDD Feature Difference Section
LBFD-002018 Mobility TDLBFD-002018 Mobility None 4 Basic Functions of Mobility

Management Management Management in Connected
Mode
LBFD-00201801 Coverage TDLBFD-00201801 Coverage None 5.2 Coverage-based Intra-

Based Intra-frequency Based Intra-frequency frequency Handover
Handover Handover
LBFD-00201802 Coverage TDLBFD-00201802 Coverage None 5.3 Coverage-based Inter-

Based Inter-frequency Based Inter-frequency frequency Handover
Handover Handover
LOFD-001019 PS Inter-RAT TDLOFD-001019 PS Inter-RAT None 5.4 Coverage-based Inter-RAT

Mobility between E-UTRAN and Mobility between E-UTRAN and Handover to UTRAN
UTRAN UTRAN
LOFD-001020 PS Inter-RAT TDLOFD-001020 PS Inter-RAT None 5.5 Coverage-based Inter-RAT

Mobility between E-UTRAN and Mobility between E-UTRAN and Handover to GERAN
GERAN GERAN
LOFD-001078 E-UTRAN to TDLOFD-001078 E-UTRAN to None 5.6 Coverage-based E-UTRAN

UTRAN CS/PS Steering UTRAN CS/PS Steering to UTRAN CS/PS Steering
LBFD-00201805 Service Based TDLBFD-00201805 Service In FDD, the 6.2 Service-based Inter-
Inter-frequency Handover Based Inter-frequency ENodeBAlgoSwitch.ServiceHoMultiTargetFreqSw frequency Handover
Handover parameter specifies whether services can be
transferred to different target frequencies or a
specified frequency by service-based handovers.
In TDD, services of a certain QCI can only be
transferred to all frequencies.
Other mechanisms work the same way in FDD
and TDD.
LOFD-001043 Service based TDLOFD-001043 Service based None 6.3 Service-based Inter-RAT
Inter-RAT handover to UTRAN inter-RAT handover to UTRAN Handover to UTRAN
LOFD-001046 Service based TDLOFD-001046 Service based None 6.4 Service-based Inter-RAT
Inter-RAT handover to GERAN inter-RAT handover to GERAN Handover to GERAN
LBFD-00201804 Distance Based TDLBFD-00201804 Distance None 7.2 Distance-based Inter-

Inter-frequency Handover Based Inter-frequency frequency Handover
Handover
LOFD-001072 Distance based TDLOFD-001072 Distance None 7.3 Distance-based Inter-RAT

Inter-RAT handover to UTRAN based Inter-RAT handover to Handover to UTRAN
UTRAN
LOFD-001073 Distance based TDLOFD-001073 Distance None 7.4 Distance-based Inter-RAT

Inter-RAT handover to GERAN based Inter-RAT handover to Handover to GERAN
GERAN
LOFD-070216 Separate Mobility N/A This feature is supported only by FDD. 11 Separate Mobility Policies to
Policies to UTRAN for Multi UTRAN for Multi PLMN (FDD)
PLMN
LOFD-111204 Separate Mobility TDLOFD-131210 Separate None 12 Separate Mobility Policies to

Policies to GERAN for Multi Mobility Policies to GERAN for GERAN for Multi PLMN
PLMN Multi PLMN
LBFD-131111 Mobility between TDLBFD-001050 Mobility None 5.3 Coverage-based Inter-

LTE TDD and LTE FDD between LTE TDD and LTE FDD frequency Handover
6.2 Service-based Inter-

frequency Handover
7.2 Distance-based Inter-

frequency Handover
N/A TDLOFD-070228 Service- This feature works the same way in FDD and TDD. 9 Service-request-based Inter-
Request Based Inter-frequency frequency Handover
Handover
3 Overview of Mobility Management in Connected Mode
Mobility management in connected mode, which is also termed as handover, is a basic function in mobile networks. With this function, an eNodeB keeps
monitoring the air interface status of user equipment (UEs) in the synchronization state of radio resource control (RRC) connected mode and determines
whether to switch the serving cell of UEs. Handover ensures uninterrupted network services during UE mobility.
NOTE:
Handover in this document is a generic term that covers procedures related to mobility management in connected mode.
In the case of handover policy, handover is a specific term in contrast to redirection. In this case, handover refers to a procedure in which the
serving cell of a UE changes. For details, see 4.1.6.2.1 Handover Policies.
This document focuses on the common process of mobility management in connected mode for data services. For details about intra-RAT mobility
management in connected mode for voice over Long Term Evolution (VoLTE) services, see VoLTE. For details about inter-RAT mobility management in
connected mode to UTRAN or GERAN for VoLTE services, see SRVCC. For details about inter-RAT mobility management in connected mode to UTRAN or
GERAN for non-VoLTE voice services, see CS Fallback. The mobility management mechanism of combined services varies depending on the service with
the highest-priority QCI.
Handover Functions in Different Scenarios
The eNodeB provides various handover functions to accommodate UE mobility requirements in different scenarios. Table 3-1 describes these functions.
Table 3-1 Handover functions
Handover Function Application Scenario
Coverage-based handover When a UE moves to the cell edge on a network with contiguous coverage, the eNodeB initiates a coverage-based
handover if the UE receives better signal quality from neighboring cells than from the serving cell. This function
prevents service drops caused by signal quality deterioration.
Load-based handover When a cell is heavily loaded but its neighboring cells are lightly loaded, the eNodeB initiates load-based
handovers from the overloaded cell to maximize system resource usage.
For details about load-based handovers, including intra-RAT and inter-RAT handovers, see Intra-RAT Mobility Load
Balancing and Inter-RAT Mobility Load Balancing, respectively.
Service-based handover When operators require that services with different QCIs be carried by different frequencies, service-based
handovers can be used to preferentially set up services with specified QCIs on specified frequencies for service
steering.
Distance-based handover When a UE moves out of the planned coverage area of a neighboring cell in overshoot coverage scenarios, the
eNodeB initiates a distance-based handover to prevent handover failures or service drops caused by a delayed
handover.
UL-quality-based handover When the uplink signal quality is poor but the downlink signal quality is normal, the eNodeB promptly initiates a
UL-quality-based handover to prevent service drops caused by poor uplink signal quality.
Service-request-based handover In service steering scenarios or when a service is not allowed on the serving frequency of a UE (for example, VoLTE
is not licensed on the frequency), the eNodeB initiates a service-request-based handover to transfer the UE to
another permissible frequency for service continuity.
Frequency-priority-based When a network has both low and high bands, the eNodeB initiates frequency-priority-based handovers so that UE
handover services can be preferentially carried on the high band and the low band is spared for contiguous coverage.
Handover Function Application Scenario
Other handoversa The following lists mobility management policies for other services or scenarios and their reference documents:
VoLTE-specific handovers. For details, see VoLTE.
Video-specific handovers, such as QoE-based handovers from E-UTRAN to UTRAN. For details, see UL Unified
Video Steering.
Inter-frequency handovers for primary component carrier (PCC) anchoring. For details, see Carrier Aggregation.
Inter-frequency handovers based on evolved multimedia broadcast/multicast service (eMBMS) service interest
indications. For details, see eMBMS.
Handover enhancement at high speed mobility. For details, see High Speed Mobility.
UE-specific handovers, such as SPID-based handovers back to home public land mobile network (HPLMN). For
details, see Flexible User Steering.
Inter-RAT handovers of CS services and handovers of PS services to CDMA2000 networks. For details about CS
service handovers to UTRAN and GERAN, see VoLTE, SRVCC, and CS Fallback. For details about handovers to
CDMA2000 networks, see LTE-CDMA2000 CS Service Interworking (FDD), LTE-CDMA2000 CS Service
Interworking (TDD), and LTE-CDMA2000 PS Service Interworking.
a: These handovers are not described in this document.
The basic procedures for handover functions are the same. For details, see 4 Basic Functions of Mobility Management in Connected Mode. The
differences between handover functions are described in their respective sections. Users can read 4 Basic Functions of Mobility Management in
Connected Mode and the corresponding handover function section to acquire complete information about a handover function.
Table 3-2 briefs the differences among handover functions.

Table 3-2 Handover function differences
Handover Function Handover Function Starting Handover Function Stopping Condition Handover Execution Initiation Conditionc
Condition
Coverage-based For intra-frequency handovers: For intra-frequency handovers: N/A For intra-frequency handovers: event A3
handovera Started unconditionally when For inter-frequency handovers: event A1 For inter-frequency handovers: event A3, A4, or
UEs are running services. Intra- For inter-RAT handovers: event A1 A5
frequency mobility management For inter-RAT handovers: event B1 or B2
involves only coverage-based
handovers.
For inter-frequency handovers:
event A2b
For inter-RAT handovers: event
A2
Service-based Inter-frequency handover is Measurement for an inter-frequency or For intra-frequency handovers: N/A
handover allowed for the highest-priority inter-RAT handover has been performed For inter-frequency handovers: event A4
QCI of services running on the for 3s, but no measurement report is For inter-RAT handovers: event B1 or B2
UE. received.
Distance-based The distance between the UE The distance between the UE and the For intra-frequency handovers: N/A
handover and the eNodeB exceeds a eNodeB falls below the specified For inter-frequency handovers: event A4
configured value. threshold. For inter-RAT handovers: event B1 or B2
UL-quality-based Uplink quality becomes worse. Uplink quality becomes better. For intra-frequency handovers: N/A
handovera For inter-frequency handovers: event A4
For inter-RAT handovers: event B1 or B2
Service-request- The eNodeB receives a UE's Measurement has been performed for a Event A4 (This handover function involves only
based handover service setup or modification time specified by inter-frequency handovers.)
request. ServiceIfHoCfgGroup.A4RptWaitingTimer,
but no measurement report is received.
Frequency-priority- Event A1 Event A2 Event A4 (This handover function involves only

based handovera inter-frequency handovers.)
Event A2 Measurement has been performed for 3s, Event A4 (This handover function involves only
but no measurement report is received. inter-frequency handovers.)
Handover Function Handover Function Starting Handover Function Stopping Condition Handover Execution Initiation Conditionc
Condition
a: These handovers can be processed in measurement-based mode or blind mode. Handovers not marked with a can be processed only in
measurement-based mode. For details about handover processing modes, see 4.1.3 Processing Mode Selection.
b: For details about the events in this table, see 4.1.4.2.1 Measurement Events.
c: Handover execution initiation conditions are involved only in measurement-based mode, not in blind mode.
Handover Function Classification
Handover functions are classified as follows based on the necessity of initiating a handover:
Necessary handover: When the serving cell of a UE is not able to provide services for the UE and a handover must be initiated to avoid service drops,
such a handover is termed as necessary handover. Necessary handovers are indicated by the cause value "Handover desirable for radio reasons" (for
intra-RAT handovers) or "Time Critical Handover" (inter-RAT handovers), in accordance with 3GPP specifications. Necessary handovers include:
Coverage-based handover
Distance-based handover
UL-quality-based handover
Unnecessary handover: Such handovers are generally performed depending on network deployment policies. UEs can still perform services in their
serving cells if the UEs are not successfully handed over. Unnecessary handovers are further categorized into offload-oriented handover and
optimization-oriented handover:
Offload-oriented handover is cell-triggered and is used to balance cell loads. This type of handover is indicated by the cause value "Reduce Load
in Serving Cell" in accordance with 3GPP specifications. For details, see Intra-RAT Mobility Load Balancing and Inter-RAT Mobility Load Balancing.
Optimization-oriented handover is UE-triggered and is performed to achieve better network performance. This type of handover is indicated by
the cause value "Handover Optimisation" (X2-based networking) or "Resource Optimisation Handover" (S1-based networking) in accordance
with 3GPP specifications. Optimization-oriented handovers include:
Service-based handover
Service-request-based handover
Frequency-priority-based handover
4 Basic Functions of Mobility Management in Connected Mode
4.1 Principles
4.1.1 Overall Process

Figure 4-1 shows the overall handover process.
Figure 4-1 Overall handover process
The following sections describe procedures in the process:
4.1.2 Handover Function Initiation Decision describes the conditions for starting handover functions.
Handover functions consist of:
Coverage-based handover
Service-based handover
UL-quality-based handover
Service-request-based inter-frequency handover
Frequency-priority-based inter-frequency handover
The conditions for determining whether a UE in its serving cell requires a handover vary depending on handover functions. The conditions are
described in follow-up chapters and sections related to handover functions.
4.1.3 Processing Mode Selection describes blind mode and measurement-based mode, which differ in whether to measure cells.
4.1.4 Measurement Configuration Delivery describes delivery of measurement configurations to the UE. This procedure applies only to measurement-
based mode.
4.1.5 Measurement Reporting describes reporting of measurement results to the eNodeB. This procedure applies only to measurement-based mode.
4.1.6 Target Cell or Frequency Decision describes how the eNodeB selects a target cell or target frequency after a handover function is initiated. In
this procedure, the eNodeB determines whether there is a suitable new serving cell for the handover. If there is, the eNodeB starts executing the
handover.
4.1.7 Handover Execution describes handover preparation and execution.
4.1.8 Retry and Penalty for Handover Failures describes penalty and retry after the handover fails.

The conditions for determining whether a UE in its serving cell requires a handover vary depending on handover functions. The conditions are described
in follow-up chapters and sections related to handover functions.
4.1.3 Processing Mode Selection

According to whether measurement on neighboring cells is performed before a handover, handover processing mode is classified into measurement-
based mode and blind mode.
Measurement-based mode
In this mode, UEs measure signal quality of candidate cells and the eNodeB generates a candidate cell list based on measurement reports.
The measurement-based mode applies to all handover policies. For details about handover policies, see 4.1.6.2.1 Handover Policies.
Blind mode
In this mode, UEs do not measure signal quality of candidate cells. The eNodeB generates a target cell or frequency list based on priority parameter
configurations. UEs are likely to experience access failures in neighboring cells in this mode. Therefore, this mode is used only when a handover
needs to be initiated immediately.
The blind mode is used only when the handover policy is handover or redirection. For details about handover policies, see 4.1.6.2.1 Handover
Policies.
Figure 4-2 shows how measurement-based and blind modes work during a handover.
Figure 4-2 Measurement-based and blind modes

During a measurement, a UE evaluates the signal quality of a measurement object at the frequency level and, based on measurement configurations, the
UE determines whether event conditions are met.
Measurement objects can be the serving cell or neighboring cells. The procedures for measuring the serving cell and neighboring cells are the same. This
section uses neighboring cell measurement as an example to describe measurement configuration delivery.
After a radio bearer is established for the UE, the eNodeB includes measurement configurations in an RRC Connection Reconfiguration message and
delivers the message to the UE based on handover function configurations.
The eNodeB also checks whether the measurement configurations for the UE need to be updated after the UE enters the RRC_CONNECTED mode or a
handover is completed. If it does, the eNodeB delivers updated measurement configurations to the UE in an RRC Connection Reconfiguration message.
The ReduceMeasCtrlMesNumSwitch option of the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter can be selected to reduce the number of RRC
Connection Reconfiguration messages sent to the UE. If this option is selected, measurement configuration update and E-RAB modifications are
combined in a single RRC Connection Reconfiguration message. Considering UE compatibility issues, this option can be deselected so that measurement
configuration update and E-RAB modifications are sent through two separate messages.
Measurement configurations are mainly determined on the eNodeB side and are delivered to UEs, which include the following information about
measurement tasks:
Measurement objects
Measurement objects include the RATs, frequencies, and cells whose signal quality needs to be measured.
Reporting configurations
Reporting configurations include measurement event information, triggering quantity and reporting quantity (only for intra-RAT handovers), and
other information about measurement reports. Reporting configurations specify the criteria for measurement reporting.
Other configurations
Other configurations include measurement quantity, measurement gap, and measurement filtering coefficient.
4.1.4.1 Measurement Object

The eNodeB selects an RAT for measurement and then obtains the frequencies or cells to be measured from the neighboring cell list of the selected RAT.
Table 4-1 lists the key attributes of measurement objects for different RATs.
Table 4-1 Measurement object configurations
RAT Configuration
RAT Configuration
E-UTRAN The key attributes are as follows:
E-UTRA absolute radio frequency channel number (EARFCN), which is specified by the EutranInterNFreq.DlEarfcn
parameter
Measurement bandwidth, which is specified by the EutranInterNFreq.MeasBandWidth parameter
Connected-mode frequency-specific offset, which is specified by the EutranInterNFreq.QoffsetFreqConn parameter
Cell individual offset (CIO), which is the cell-specific offset for the neighboring cell. For details about CIOs, see CIO-
related descriptions in MRO.
Blacklisted cells. For details, see descriptions of blacklisted neighboring cells for handovers in ANR Management.
UTRAN The key attributes are as follows:
UTRA absolute radio frequency channel number (UARFCN), which is specified by the UtranNFreq.UtranDlArfcn parameter
Frequency-specific offset, which is specified by the UtranNFreq.OffsetFreq parameter
GERAN The key attributes are as follows:
ARFCN-related configurations:
Starting ARFCN, which is specified by the GeranNfreqGroup.StartingArfcn parameter
Band indicator, which is specified by the GeranNfreqGroup.BandIndicator parameter
ARFCN of the GERAN BCCH, which is specified by the GeranNfreqGroupArfcn.GeranArfcn parameter
Frequency-specific offset, which is specified by the GeranNfreqGroup.OffsetFreq parameter
4.1.4.1.1 RAT Selection for Measurement

If the RAT can be determined, the eNodeB selects E-UTRAN, UTRAN, or GERAN based on handover function initiation conditions. If the RAT cannot be
determined, the eNodeB preferentially selects E-UTRAN. If the RAT for inter-RAT handovers cannot be determined, the eNodeB selects both UTRAN and
GERAN.
4.1.4.1.2 Frequency Selection for Measurement
Filtering of Frequencies to Be Measured
The eNodeB filters out the following cells from the neighboring cell list before obtaining the frequencies to measure. If no cell is working on a frequency
after cell filtering, the frequency will not be selected for measurement.
Blacklisted neighboring cells
Neighboring cells with a handover prohibition flag
Neighboring cells that do not belong to any PLMN in the PLMN list
A PLMN list consists of three parts:
PLMN that the serving cell belongs to
Target PLMNs defined in InterPlmnHoList MOs when the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is
selected
Equivalent PLMNs obtained by the eNodeB from the Handover Restriction List IE sent from the MME when both the InterPlmnHoSwitch and
EPlmnSwitch options of the ENodeBAlgoSwitch.HoAlgoSwitch parameter are selected
Cells in the TAs and LAs indicated by the Forbidden TACs and Forbidden LACs in the Handover Restriction List IE in the INITIAL CONTEXT SETUP
REQUEST message sent from the MME
An exception is that the eNodeB does not filter out the preceding cells in the following cases:
The UE is performing an emergency call.
Automatic neighbor relation (ANR) is enabled and the cells can be maintained by ANR.
The frequencies to measure must be neighboring E-UTRA frequencies or inter-RAT neighboring frequencies configured on the eNodeB. The eNodeB
selects the frequencies for measurement in descending order of frequency priority. If the highest priority maps to multiple frequencies, the eNodeB
randomly selects frequencies with the highest priority. Table 4-2 lists frequency priority parameters.
Table 4-2 Frequency priority parameters
Handover Type Priority Parameter
Handover Type Priority Parameter
Measurement-based inter-frequency Frequency priorities are determined based on the setting of the FixedMeasObjIDSwitch option of the
handover CellAlgoSwitch.MultiFreqPriControlSwitch parameter:
When this option is deselected, frequency priorities are determined by the

EutranInterNFreq.ConnFreqPriority parameter.
When this option is selected, frequency priorities are determined by the

EutranInterNFreq.MeasFreqPriority parameter.
When the CellAlgoSwitch.MultiCnConnFreqPriSw parameter is set to ON, operator-specific frequency priority

settings are supported. Frequency priorities are generated based on the following parameter settings in the
RAN sharing with common carrier scenario:
CellOp.RatFreqPriorityGroupId configured for different operators
RatFreqPriorityGroup.ConnFreqPriority configured for different operators
Measurement-based handover from UtranNFreq.ConnFreqPriority

E-UTRAN to UTRAN
Measurement-based handover from GeranNfreqGroup.ConnFreqPriority

E-UTRAN to GERAN
Maximum Number of Frequencies to Be Measured
The number of frequencies to be included in measurement configurations of each RAT is controlled by parameters, as listed in Table 4-3.
The total number of target frequencies included in measurement configurations of all RATs must not exceed the total number of inter-frequency and
inter-RAT measurement objects, which is specified by the CellUeMeasControlCfg.MaxNonIntraMeasObjNum parameter. In GERAN, a frequency group is
delivered as one measurement object. A frequency group contains a maximum of 32 frequencies.
Neighboring E-UTRAN FDD and TDD frequency configurations are set in the EUTRANINTERNFREQ MO. When the main control board is UMPT, a
maximum of 16 neighboring FDD and TDD frequencies can be configured. When another main control board is used, a maximum of eight neighboring
FDD and TDD frequencies can be configured.
For E-UTRAN FDD, the maximum number of frequencies that can be delivered in measurement configurations is the smaller value between the
CellUeMeasControlCfg.MaxEutranFddMeasFreqNum parameter value and the number of configured neighboring FDD frequencies.
For E-UTRAN TDD, the maximum number of frequencies that can be delivered in measurement configurations is the smaller value between the
CellUeMeasControlCfg.MaxEutranTddMeasFreqNum parameter value and the number of configured neighboring TDD frequencies.
Table 4-3 Parameters that specify the maximum number of frequencies of each RAT
RAT Parameter Specifying the Maximum Number of Frequencies that Can Be Delivered in Measurement Configurations
E-UTRAN FDD CellUeMeasControlCfg.MaxEutranFddMeasFreqNum
E-UTRAN TDD CellUeMeasControlCfg.MaxEutranTddMeasFreqNum
UTRAN FDD CellUeMeasControlCfg.MaxUtranFddMeasFreqNum
UTRAN TDD CellUeMeasControlCfg.MaxUtranTddMeasFreqNum
GERAN CellUeMeasControlCfg.MaxGeranMeasFreqNum
NOTE:
If the sum of the number of to-be-delivered GERAN frequencies in the highest-priority GERAN frequency group and the number of delivered
GERAN frequencies exceeds the maximum number of GERAN frequencies allowed for measurement, all the GERAN frequencies in this GERAN
frequency group are not delivered in measurement configurations. The eNodeB evaluates the frequency group with the next highest priority till
the number of delivered frequencies equals the maximum number of GERAN frequencies allowed for measurement or all frequency groups are
evaluated.
Measurement Preemption
According to 3GPP TS 36.133, UE capability in gap-assisted inter-frequency or inter-RAT measurements is limited. Measurement preemption allows a UE
with such a limited capability to measure higher-priority frequencies when possible.
The MEAS_OBJ_PREEMPT_SW option of the CellAlgoSwitch.MeasOptAlgoSwitch parameter specifies whether to enable this function. If this option is
selected and the UE frequency measurement capability is limited, the eNodeB checks whether the priority of the algorithm to be started is higher than
the highest priority of earlier started algorithms. If the priority of the algorithm to be started is higher, the eNodeB enables this algorithm to preempt
measurement resources, which means that the UE measures the frequency involved in the algorithm to be started. Table 4-4 lists the algorithm priorities
for frequency measurement.
Table 4-4 Algorithm priorities
Category Description Example
First priority Algorithms for voice services CS fallback
Second priority Handover algorithms directly affecting user experience, such Necessary handovers such as coverage-based inter-frequency
as service drop and interruption or inter-RAT handovers
Third priority Handover algorithms related to the measurement of a single Unnecessary handovers such as service-based inter-frequency
UE (without affecting key performance indicators) or inter-RAT handovers
Fourth priority Algorithms not for specific UEs Sampling measurement such as ANR
4.1.4.1.3 Cell Selection for Measurement
Filtering of Cells to Be Measured
If the RAT for measurement is E-UTRAN, the eNodeB delivers cell information in addition to frequency information when the CIO (specified by
EutranInterFreqNCell.CellIndividualOffset) is not 0. In addition, the eNodeB preferentially delivers information about neighboring cells with
EutranInterFreqNCell.CellMeasPriority set to HIGH_PRIORITY.
If the RAT for measurement is UTRAN, the eNodeB delivers cell information, in addition to frequency information, based on the UTRAN neighbor
relationship configuration. The delivered cell and frequency information determines the cells to measure. The cells to be delivered are sorted by certain
priority, depending on the settings listed in Table 4-5.
Table 4-5 Cell measurement priorities
Setting Priority Parameter
The UTRAN_SWITCH option of the ENodeBAlgoSwitch.NCellRankingSwitch UtranNCell.NCellMeasPriority, which can be optimized by

parameter is selected. ANR. For details, see ANR Management.
The UTRAN_SWITCH option of the ENodeBAlgoSwitch.NCellRankingSwitch UtranNCell.CellMeasPriority

parameter is deselected.
For details, see section 6.3.5 "Measurement information elements" in 3GPP TS 36.331 V10.1.0.
Maximum Number of Cells to Be Measured
Table 4-6 lists the maximum number of neighboring cells that can be delivered for each measurement object. For details, see section 6.4 "RRC multiplicity
and type constraint values" in 3GPP TS 36.331 V10.1.0.
Table 4-6 Maximum number of neighboring cells indicated in a measurement configuration message
Neighboring Cell Type Maximum Number of Neighboring Cells Description
Intra-frequency neighboring 32 Maximum number of neighboring cells that can be

cell
configured for a cell: 256a
Maximum number of neighboring cells that can be

Inter-frequency neighboring 32 configured for an eNodeB: Total number of cells
cell supported by the eNodeB x 256. The maximum number
must not exceed 72 x 256.
Neighboring UTRAN cell 32 Maximum number of neighboring cells that can be

configured for a cell: 128
Maximum number of neighboring cells that can be

configured for an eNodeB: Total number of cells
supported by the eNodeB x 128
a: This number increases to 384 when the UMPT board is used as the active main control board.
4.1.4.2 Reporting Configurations

Reporting configurations include:
Information about measurement events, including events A1 to A5, event B1, and event B2
Triggering quantity and reporting quantity (involved only in intra-RAT handovers)
Other parameters, including the maximum number of cells to be included in each measurement report, number of periodic measurement reports,
and interval between periodic measurement reports
4.1.4.2.1 Measurement Events
Overview of Mobility Events
An event is an indication of signal quality. Table 4-7 lists the definition of each event.
Table 4-7 Event definitions
Event Type Event Definition
Event A1 The signal quality of the serving cell exceeds a specific threshold.
Event A2 The signal quality of the serving cell drops below a specific threshold.
Event A3 The signal quality of a neighboring cell exceeds that of the serving cell.
Event A4 The signal quality of a neighboring cell exceeds a specific threshold.
Event A5 The signal quality of the serving cell drops below threshold 1 (Thresh1) and the signal quality of a neighboring cell exceeds
threshold 2 (Thresh2).
Event B1 The signal quality of an inter-RAT neighboring cell exceeds a specific threshold.
Event B2 The signal quality of the serving cell drops below threshold 1 (Thresh1) and the signal quality of an inter-RAT neighboring cell
exceeds threshold 2 (Thresh2).
The entering and leaving conditions of these events are described as follows. For details, see section 5.5.4 "Measurement report triggering" in 3GPP TS
36.331 V10.1.0.
Event A1
Entering conditions: (Ms – Hys > Thresh) is true throughout a duration specified by TimeToTrig.
Leaving conditions: (Ms + Hys < Thresh) is true throughout a duration specified by TimeToTrig.
Figure 4-3 shows the details.
Figure 4-3 Entering and leaving of event A1
Event A2
Entering conditions: (Ms + Hys < Thresh) is true throughout a duration specified by TimeToTrig.
Leaving conditions: (Ms – Hys > Thresh) is true throughout a duration specified by TimeToTrig.
Event A3
Entering conditions: (Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off) is true throughout a duration specified by TimeToTrig.
Leaving conditions: (Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off) is true throughout a duration specified by TimeToTrig.
Event A4
Entering conditions: (Mn + Ofn + Ocn – Hys > Thresh) is true throughout a duration specified by TimeToTrig.
Leaving conditions: (Mn + Ofn + Ocn + Hys < Thresh) is true throughout a duration specified by TimeToTrig.
Event A5
Entering conditions: (Ms + Hys < Thresh1) and (Mn + Ofn + Ocn – Hys > Thresh2) are true throughout a duration specified by TimeToTrig.
Leaving conditions: (Ms – Hys > Thresh1) or (Mn + Ofn + Ocn + Hys < Thresh2) is true throughout a duration specified by TimeToTrig.
Event B1
Entering conditions: (Mn + Ofn – Hys > Thresh) is true throughout a duration specified by TimeToTrig.
Leaving conditions: (Mn + Ofn + Hys < Thresh) is true throughout a duration specified by TimeToTrig.
Figure 4-8 Entering and leaving of event B1
Event B2
Entering conditions: (Ms + Hys < Thresh1) and (Mn + Ofn – Hys > Thresh2) are true throughout a duration specified by TimeToTrig.
Leaving conditions: (Ms – Hys > Thresh1) or (Mn + Ofn + Hys < Thresh2) is true throughout a duration specified by TimeToTrig.
Figure 4-9 Entering and leaving of event B2
The meanings of variables in the preceding formulas are as follows:
Ms and Mn are the measurement results of the serving cell and a neighboring cell, respectively.
Hys is the hysteresis for an event.
TimeToTrig indicates the duration throughout which a condition is met before the event can be triggered.
Thresh, Thresh1, and Thresh2 indicate thresholds.
Ofs and Ofn indicate the frequency-specific offsets for the serving cell and the neighboring cell, respectively.
Ocs and Ocn indicate the CIOs set for the serving cell and the neighboring E-UTRAN cell, respectively.
Off indicates the offset for the event.
NOTE:
Events A2 and A1 are used to evaluate the signal quality of the serving cell in the handover function initiation determination phase. Other events
are used to evaluate the signal quality of neighboring cells in the target cell or frequency determination phase.
Measurement configuration delivery and measurement reporting mechanisms of these events (A1 to A5, B1, and B2) are the same.
Configurations of Intra-RAT Events
Intra-RAT events include events A1, A2, A3, A4, and A5.
The following variables in the formulas are user-configurable:
Hys and TimeToTrig, which can be set for each QCI. The variables for different events are specified by different parameters. For details, see Table 4-8.
Thresh, Thresh1, and Thresh2, which can be set for each eNodeB. The thresholds for different events or handover types are specified by different
parameters. For details, see the sections that describe the specific handover functions.
NOTE:
The signal quality types of Ms, Mn, Thresh, Thresh1, and Thresh2 are determined by their triggering quantities.
Ofs and Ofn, which are considered during inter-frequency handovers

The Cell.QoffsetFreq parameter specifies Ofs.
The EutranInterNFreq.QoffsetFreqConn parameter specifies Ofn.
Ocs and Ocn

The Cell.CellSpecificOffset parameter specifies Ocs.
The EutranIntraFreqNCell.CellIndividualOffset parameter specifies Ocn for intra-frequency neighboring cells.
The EutranInterFreqNCell.CellIndividualOffset parameter specifies Ocn for inter-frequency neighboring cells.
Off, which applies only to event A3

The IntraFreqHoGroup.IntraFreqHoA3Offset parameter specifies Off for intra-frequency event A3.
The InterFreqHoGroup.InterFreqHoA3Offset parameter specifies Off for inter-frequency event A3.
Table 4-8 Variable values used in intra-RAT handover events
Event Type Variable Value
A1 InterFreqHoGroup.InterFreqHoA1A2Hyst specifies Hys.
InterFreqHoGroup.InterFreqHoA1A2TimeToTrig specifies TimeToTrig.
A2
A3 IntraFreqHoGroup.IntraFreqHoA3Hysta specifies Hys.
IntraFreqHoGroup.IntraFreqHoA3TimeToTriga specifies TimeToTrig.
A4 InterFreqHoGroup.InterFreqHoA4Hyst specifies Hys.

InterFreqHoGroup.InterFreqHoA4TimeToTrig specifies TimeToTrig.
A5
a: Both intra-frequency event A3 and inter-frequency event A3 use these parameters.
Configurations of Inter-RAT Events
Inter-RAT events include events A1, A2, B1, and B2.
The following variables in the formulas are user-configurable:
Hys and TimeToTrig, which can be set for each QCI. The variables for different events are specified by different parameters. For details, see Table 4-9.
Thresh, Thresh1, and Thresh2, which can be set for each eNodeB. The thresholds for different events or handover types are specified by different
parameters. For details, see the sections that describe the specific handover functions.
NOTE:
The signal quality types of Ms, Mn, Thresh, Thresh1, and Thresh2 are determined by their triggering quantities.
Ofs and Ofn

The Cell.QoffsetFreq parameter specifies Ofs.
The UtranNFreq.OffsetFreq parameter specifies Ofn for neighboring UTRAN cells.
The GeranNfreqGroup.OffsetFreq parameter specifies Ofn for neighboring GERAN cells.
Table 4-9 Variable values related to inter-RAT handover events
A1 InterRatHoCommGroup.InterRatHoA1A2Hyst specifies Hys.

InterRatHoCommGroup.InterRatHoA1A2TimeToTrig specifies TimeToTrig.
A2
B1 E-UTRAN to UTRAN
InterRatHoUtranGroup.InterRATHoUtranB1Hyst specifies Hys.
InterRatHoUtranGroup.InterRATHoUtranB1TimeToTrig specifies TimeToTrig.
B2 E-UTRAN to GERAN
InterRatHoGeranGroup.InterRatHoGeranB1Hyst specifies Hys.
InterRatHoGeranGroup.InterRatHoGeranB1TimeToTrig specifies TimeToTrig.
For TimeToTrig used for E-UTRAN to UTRAN handovers, the measurement duration of offload-oriented and optimization-oriented handovers is
controlled by a 3s timer. If TimeToTrig is longer than 3s, UEs will not send measurement reports to the eNodeB because the measurements are stopped
before the time-to-trigger elapses. In this case, offload-oriented and optimization-oriented handovers will not be triggered.
The TimeToTrig variable differs depending on UTRAN and GERAN. Operators can set TimeToTrig to control the event B1 reporting probability. For
example, if the TimeToTrig value for handovers from E-UTRAN to UTRAN is smaller than that for handovers from E-UTRAN to GERAN, a UE reports event
B1 for neighboring UTRAN cells more probably than event B1 for neighboring GERAN cells, given the same network conditions. Therefore, the eNodeB
sends a handover request more probably to a neighboring UTRAN cell.
Differentiated Parameter Delivery Depending on QCI Settings
Event-related parameters can be delivered depending on QCI settings, flexibly controlling handovers of services with different QCIs.
The eNodeB delivers parameters for combined services (services with multiple QCIs) as follows:
If a necessary handover is triggered for a UE running combined services, the eNodeB delivers the parameters defined for the highest-priority QCI to
the UE.
Table 4-10 lists the default mapping between QCIs and priorities for FDD. Table 4-11 lists the default mapping between QCIs and priorities for TDD.
If different QCIs are mapped to the same priority value in the table, the eNodeB delivers parameters according to the priority levels recommended in
3GPP specifications. A smaller priority value indicates a higher priority level. For details, see section 6.1.7 "Standardized QoS characteristics" in 3GPP
TS 23.203 V15.0.0.
Operators can also customize the QCI priorities by setting the CellQciPara.QciPriorityForHo parameter.
If an unnecessary handover is triggered for a UE running combined services, the eNodeB performs differentiated handling to guarantee the QoS of
these services: If the thresholds are different for the QCIs, the eNodeB delivers the most restrictive handover parameters (meeting all QCI
requirements) to the UE. If the thresholds are the same but other parameters are different, the eNodeB delivers the parameters defined for the
highest-priority QCI to the UE.
Table 4-10 Mapping between QCIs and priorities for FDD
QCI 1 2 3 4 5 6 7
Priority 2 4 3 5 1 6 7
QCI 8 9 65 66 69 70 -
Priority 8 9 2 4 1 8 -
Table 4-11 Mapping between QCIs and priorities for TDD
QCI 1 2 3 4 5 6 7 8
Priority 2 4 3 5 1 6 7 8
QCI 9 65 66 69 70 75 79 -
Priority 9 2 4 1 8 3 3 -
4.1.4.2.2 Triggering Quantity and Reporting Quantity

Triggering quantity and reporting quantity are involved only in intra-RAT measurement configurations. Triggering quantity and reporting quantity for
each intra-RAT event or handover are specified by user-configured parameters. For details, see the sections that describe the handover functions.
Triggering quantity refers to the policy that triggers event reporting, which can be set to RSRP, RSRQ, or BOTH.
When the triggering quantity is RSRP, the UE sends measurement reports to the eNodeB if the reference signal received power (RSRP) meets the
entering condition of the corresponding event.
When the triggering quantity is RSRQ, the UE sends measurement reports to the eNodeB if the reference signal received quality (RSRQ) meets
the entering condition of the corresponding event.
When the triggering quantity is BOTH, the eNodeB delivers two measurement configurations, with one being RSRP-based and the other being
RSRQ-based. The UE reports the corresponding event if either RSRP or RSRQ meets the entering condition for the event.
Reporting quantity refers to the signal quality information contained in measurement reports, which serves as a criterion for handover evaluation.
The reporting quantity can be set to SAME_AS_TRIG_QUAN or BOTH.
The value SAME_AS_TRIG_QUAN indicates that the reporting quantity is the same as the triggering quantity.
The value BOTH indicates that both RSRP and RSRQ values are included in measurement reports when either triggering quantity meets the
triggering condition.
4.1.4.2.3 Other Parameters

The other parameters listed in Table 4-12 apply only to events A3, A4, A5, B1, and B2.
Table 4-12 Other parameters for a measurement report
Event Type Maximum Number of Cells to Be Maximum Number of Periodic Reporting Interval
Included Measurement Reports
Event A3 IntraRatHoComm.IntraRATHoMaxRprtCell IntraRatHoComm.IntraRATHoRprtAmount IntraRatHoComm.IntraFreqHoRprtInterval
Event A4/A5 IntraRatHoComm.IntraRATHoMaxRprtCell IntraRatHoComm.IntraRATHoRprtAmount IntraRatHoComm.InterFreqHoRprtInterval
E-UTRAN to InterRatHoComm.InterRATHoMaxRprtCell InterRatHoComm.InterRATHoRprtAmount InterRatHoComm.InterRATHoUtranRprtInterval

UTRAN
event B1
E-UTRAN to InterRatHoComm.InterRATHoMaxRprtCell nterRatHoComm.InterRATHoRprtAmount InterRatHoComm.InterRATHoUtranRprtInterval

UTRAN
event B2
E-UTRAN to InterRatHoComm.InterRATHoMaxRprtCell nterRatHoComm.InterRATHoRprtAmount InterRatHoComm.InterRatHoGeranRprtInterval

GERAN
event B1
E-UTRAN to InterRatHoComm.InterRATHoMaxRprtCell nterRatHoComm.InterRATHoRprtAmount InterRatHoComm.InterRatHoGeranRprtInterval

GERAN
event B2
4.1.4.3 Other Configurations

Measurement Quantity Configurations of UTRAN and GERAN Cells
Measurement quantities are the types of signal quality to be evaluated for events B1 and B2 for E-UTRAN to UTRAN or GERAN handovers.
Measurement quantities for E-UTRAN to UTRAN events B1 and B2:
The InterRatHoComm.InterRATHoUtranB1MeasQuan parameter specifies whether received signal code power (RSCP) or Ec/N0 is used as the
measurement quantity for event B1.
The InterRatHoComm.InterRatHoA1A2TrigQuan parameter specifies whether RSRP or RSRQ is used to express Thresh1 for event B2. Thresh2 for
event B2 is the same as the threshold for event B1.
Measurement quantities for E-UTRAN to GERAN events B1 and B2:
Generally, the measurement quantity for event B1 is received signal strength indicator (RSSI).
The InterRatHoComm.InterRatHoA1A2TrigQuan parameter specifies whether RSRP or RSRQ is used to express Thresh1 for event B2. Thresh2 for
event B2 is the same as the threshold for event B1.
Measurement Gap Configurations
A measurement gap is a time period during which the UE performs measurements on a neighboring frequency of the serving frequency. The
measurements can be either inter-frequency or inter-RAT measurements. For details, see Figure 4-10. Before delivering a measurement configuration, the
eNodeB checks whether measurement gaps have been set up. If they have been set up for other purposes, the eNodeB does not reconfigure the
measurement gaps. Otherwise, the eNodeB sets up measurement gaps. For details about measurement gaps, see section 10.1.3 "Measurements" in 3GPP
TS 36.300 V10.3.0.
Figure 4-10 GAP-assisted measurement
Typically, measurement gap configurations are delivered by eNodeBs to UEs. If the AutoGapSwitch option of the ENodeBAlgoSwitch.HoModeSwitch
parameter is selected, the eNodeB does not deliver measurement gap configurations to UEs that support autonomous gaps.
Two measurement gap patterns are available: pattern 0 and pattern 1. Measurement duration and measurement period differ in the two patterns. The
HoMeasComm.GapPatternType or HoMeasComm.DedicatedGapPatternType parameter determines the pattern to be used. Table 4-13 describes the
measurement gap parameters.
Table 4-13 Measurement gap configurations
Parameter Name Parameter ID Description
GAP measurement pattern HoMeasComm.GapPatternType Non-CSFB measurement gap pattern
Dedicated Gap Pattern Type HoMeasComm.DedicatedGapPatternType CSFB measurement gap pattern
If another gap pattern needs to be set up during the gap-assisted measurement, the eNodeB acts as follows:
If the current pattern is 0 and the requested new pattern is 1, the eNodeB does not deliver the new pattern to the UE.
If the current pattern is 1 and the requested new pattern is 0, the eNodeB delivers the new pattern to the UE only when the triggering cause of the
ongoing gap-assisted measurement is an unnecessary handover.
Measurement Filtering Configurations
Before evaluating the reporting criteria and sending measurement reports, the UE filters measurement results.
The filtering mechanism for different networks is specified by different parameters, as listed in Table 4-14.
Table 4-14 Parameters that specify Layer 3 (L3) filtering for different networks
Network L3 Filtering Coefficient k
E-UTRAN HoMeasComm.EutranFilterCoeffRSRP
Network L3 Filtering Coefficient k
HoMeasComm.EutranFilterCoeffRSRQ
UTRAN HoMeasComm.UtranFilterCoeffRSCP
HoMeasComm.UtranFilterCoeffECN0
GERAN HoMeasComm.GeranFilterCoeff
UE Capabilities
UE capabilities include the supported protocol version, RATs, frequencies, reception and transmission capabilities (for example, simplex/duplex or double
receivers), measurement capabilities, and handover capabilities. For details, see 3GPP TS 36.331 V10.1.0. The information to be included in measurement
configurations is dependent on UE capabilities.
4.1.5 Measurement Reporting

A UE performs measurements based on the received measurement configurations. When determining that event conditions are met, the UE sends
measurement reports to the eNodeB.
Events A2 and A1, which indicate the signal quality of the serving cell, are used in the handover function initiation decision phase. Events A2 and A1
are involved only in frequency-priority-based inter-frequency and coverage-based handovers.
Events A3, A4, A5, B1, and B2, which indicate the signal quality of neighboring cells, are used in the target cell or target frequency decision phase.
NOTE:
Measurement-based handover in this document refers to a process in which UEs measure signal quality of neighboring cells and the eNodeB
generates target cells based on measurement reports. The measurement objects of events A2 and A1 are serving cells. Therefore, measurements
for events A2 and A1 are not discussed within the range of measurement-based handover.
According to section 5.5.3 "Performing measurements" in 3GPP 36.331 V10.1.0, UEs do not need to perform intra-frequency, inter-frequency, or inter-
RAT measurements when the RSRP of their serving cells is greater than the HoMeasComm.SMeasure parameter value. That is, UEs do not send
measurement reports to the eNodeB in this situation.
4.1.6 Target Cell or Frequency Decision

The eNodeB determines a target cell or target frequency for each UE based on the handover processing mode, measurement report, and handover policy
of a handover function.
This decision process includes:
Processing measurement reports (applied only to measurement-based handover)
Determining a handover policy
Generating a target cell or target frequency list
4.1.6.1 Processing Measurement Reports

The eNodeB processes measurement reports in a first in first out (FIFO) manner. That is, the cells included in a measurement report that arrives first are
evaluated first. The eNodeB processes measurement reports as follows:
When receiving intra-frequency or inter-frequency event A3 reports, the eNodeB generates a candidate cell list based on the measurement reports.
When receiving inter-frequency event A4 or A5 reports, the eNodeB generates a candidate cell list based on the measurement reports when the
conditions listed in Table 4-15 are met.
Table 4-15 Handover determination for event A4 or A5
Triggering Quantity Reporting Quantity Handover Initiation Condition Description

Setting
RSRP SAME_AS_TRIG_QUAN RSRP meets the event entering condition. RSRP is relatively stable and RSRQ
is related to load and fluctuates
RSRQ SAME_AS_TRIG_QUAN RSRQ meets the event entering condition.
greatly with different loads.
Therefore, it is recommended that
BOTH SAME_AS_TRIG_QUAN RSRP or RSRQ meets the event entering
the following configurations be
condition.
used as the reference signal quality
RSRP BOTH RSRP meets the event entering condition but type:
RSRQ does not meet the event leaving condition. Triggering quantity: RSRP
RSRQ BOTH RSRQ meets the event entering condition but Reporting quantity:
RSRP does not meet the event leaving condition. SAME_AS_TRIG_QUAN
Triggering Quantity Reporting Quantity Handover Initiation Condition Description

Setting
BOTH BOTH RSRP meets the event entering condition but

RSRQ does not meet the event leaving condition.
Alternatively, RSRQ meets the event entering
condition but RSRP does not meet the event
leaving condition.
When receiving event B1 or B2 reports indicating a handover to UTRAN, the eNodeB generates a candidate cell list based on the measurement
reports. An exception is that, if InterRatHoComm.InterRATHoUtranB1MeasQuan is set to BOTH, the eNodeB takes the following actions when
receiving event B1 reports:
The eNodeB delivers RSCP-based event B1 measurement configurations. When RSCP meets the event B1 triggering condition, UEs complying with
3GPP Release 10 or later also report Ec/N0. In this situation, the handover is triggered only when both RSCP and Ec/N0 meet the handover
conditions. For UEs complying with versions earlier than 3GPP Release 10, the value BOTH is equivalent to the value RSCP.
When receiving event B1 or B2 reports indicating a handover to GERAN, the eNodeB generates a candidate cell list based on the measurement
reports.
The eNodeB does not perform inter-frequency handover evaluation on a UE whose behavior does not comply with its reported frequency capabilities.
Instead, the eNodeB performs only intra-frequency or inter-RAT handover evaluation for the UE. The UECapRprtAbnormalCtrlSwitch option of the
ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter specifies whether to enable this function.
4.1.6.2 Determining a Handover Policy

A handover policy is a method that an eNodeB uses to instruct a UE to change its serving cell. The eNodeB selects a handover policy for each UE based
on the following factors:
Target frequency or target RAT
The current service type of the UE
UE capabilities
4.1.6.2.1 Handover Policies

The following defines each handover policy:
Handover: In a handover, services of a UE are transferred from the PS domain of the source cell to the PS domain of a target cell to ensure
continuous service provision. Handovers are classified into intra-RAT handover and inter-RAT handover.
NOTE:
Handover in this document is a generic term that covers procedures related to mobility management in connected mode. In the case of
handover policy, handover is a specific term that refers to service transfer between PS domains.
Single radio voice call continuity (SRVCC): It applies to VoLTE services. This policy allows the transfer of VoLTE services from an LTE system to the CS
domain of an inter-RAT network. For details about SRVCC and its activation, see SRVCC.
Cell change order (CCO) without network assisted cell change (NACC) and CCO with NACC: These policies apply only to cell changes from a source E-
UTRAN cell towards a target GERAN cell.
During CCO without NACC (CCO for short), the UE is instructed to switch to the GERAN idle mode to access a GERAN cell. The procedure is
simple but causes an extended delay.
CCO with NACC (NACC for short) is an enhancement to CCO. CCO must be enabled before NACC can be used. During NACC, the eNodeB
acquires the system information of GERAN and then sends the information to the UE through a handover command. Therefore, NACC
accelerates the UE access to the target GERAN cell.
Redirection: With this policy, the eNodeB releases a UE and instructs the UE to camp on a certain frequency.
Fast redirection: It is an enhanced redirection that enables the eNodeB to instruct a Release 9-compliant UE to directly access a target cell if the
eNodeB has stored system information about the target cell.
4.1.6.2.2 Intra-RAT Handover Policy

The policy for intra-frequency handovers can only be handover.
The policy for inter-frequency handovers can be handover or redirection.
4.1.6.2.3 Inter-RAT Handover Policy

This section describes only inter-RAT data service handover policies. Policies involved in inter-RAT voice service handovers include handover, SRVCC,
CCO, and NACC. For details about handover, SRVCC, and CCO/NACC, see VoLTE, SRVCC, and CS Fallback, respectively.
E-UTRAN to UTRAN or GERAN Handover Policies
Three policies are available for E-UTRAN to UTRAN or GERAN handovers: handover, redirection, and fast redirection. Figure 4-11 shows the handover
policy selection procedure.
Figure 4-11 E-UTRAN to UTRAN or GERAN handover procedures
Parameters Related to E-UTRAN to UTRAN Handover Policies
To set the E-UTRAN to UTRAN handover policies of data services with a specific QCI, perform the following steps:
1. Set InterRatPolicyCfgGroup.UtranHoCfg to PS_HO or REDIRECTION.
2. Map the index of the handover policy configuration (identified by InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId) to the QCI by setting
QciPara.InterRatPolicyCfgGroupId to that index.
The following options specify E-UTRAN to UTRAN handover policies:
UtranPsHoSwitch option of the CellHoParaCfg.HoModeSwitch parameter: specifies the handover policy.
UtranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter: specifies the redirection policy.
UtranFlashRedirectSwitch option of the ENodeBAlgoSwitch.RedirectSwitch parameter: specifies the fast redirection policy.
During fast redirection, it is recommended that the eNodeB obtain UTRAN cell information through the RIM procedure in Multiple Reports mode to
reduce delay. For details about the RIM procedure, see RIM.
Parameters Related to E-UTRAN to GERAN Handover Policies
To set the E-UTRAN to GERAN handover policies of data services with a specific QCI, perform the following steps:
1. Set InterRatPolicyCfgGroup.GeranGprsEdgeHoCfg to PS_HO or REDIRECTION.
2. Map the index of the handover policy configuration (identified by InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId) to the QCI by setting
QciPara.InterRatPolicyCfgGroupId to that index.
The following options specify E-UTRAN to GERAN handover policies:
GeranPsHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch parameter: specifies the handover policy.
GeranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter: specifies the redirection policy.
GeranFlashRedirectSwitch option of the ENodeBAlgoSwitch.RedirectSwitch parameter: specifies the fast redirection policy.
During fast redirection, it is recommended that the eNodeB obtain GERAN cell information through the RIM procedure in Multiple Reports mode to
reduce delay. For details about the RIM procedure, see RIM.
4.1.6.3 Generating a Target Cell or Target Frequency List

The eNodeB generates a target cell or target frequency list based on the handover processing mode, measurement report, and handover policy.
The eNodeB generates a candidate cell list or frequency list in measurement-based mode and blind mode as follows:
In measurement-based mode
The eNodeB generates a candidate cell list based on measurement reports. For details, see 4.1.6.1 Processing Measurement Reports.
In blind mode
Only coverage-based, UL-quality-based, and frequency-priority-based handovers are involved in this mode. The following briefs the basic procedure.
For details, see descriptions of each handover function.
1. The eNodeB selects the RAT that has not been measured.
2. The eNodeB generates a candidate cell or target frequency list according to the sequences of RAT priority, neighboring cell priority, and
frequency priority.
For inter-RAT handovers with the policy being fast redirection, the eNodeB adds cells to or filters out cells from the candidate cell list.
In measurement-based mode, the eNodeB adds cells that are not in measurement reports but working on the target frequency for redirection.
In blind mode, the eNodeB adds other cells on the target frequency for redirection.
The cells to be delivered are sorted by certain priority, depending on the UTRAN_SWITCH option of the ENodeBAlgoSwitch.NCellRankingSwitch
parameter:
If this option is selected, the eNodeB adds cells on the target frequency according to UtranNCell.NCellMeasPriority in descending order.
If this option is deselected, the eNodeB adds high-priority cells on the target frequency according to UtranNCell.CellMeasPriority.
The eNodeB filters out neighboring cells whose system information has not been obtained.
The eNodeB filters out neighboring UTRAN cells ranked lower than the value of InterRatHoComm.CellInfoMaxUtranCellNum when the total number
of neighboring UTRAN cells exceeds this value.
The eNodeB filters out blacklisted neighboring cells.
The eNodeB filters out neighboring cells to which handovers are prohibited.
The eNodeB filters out neighboring cells that do not belong to any PLMN in the PLMN list.
A PLMN list consists of three parts:
PLMN that the serving cell belongs to
Target PLMNs defined in InterPlmnHoList MOs when the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is
selected
Equivalent PLMNs obtained by the eNodeB from the Handover Restriction List IE from the MME when both the InterPlmnHoSwitch and
EPlmnSwitch options of the ENodeBAlgoSwitch.HoAlgoSwitch parameter are selected
The eNodeB filters out cells to which handovers are forbidden according to the Handover Restriction List IE in the INITIAL CONTEXT SETUP REQUEST
message sent from the MME.
The eNodeB filters out heavy-traffic cells.

When MRFD-101402 UL Unified Overload Control is enabled, cells with heavy traffic are filtered out from candidate cell lists for service-based inter-
RAT handovers. For necessary handovers, cells with heavy traffic are filtered out, unless no non-heavy-traffic neighboring cells meet the handover
condition.
4.1.7 Handover Execution

After determining target cells or frequencies, the eNodeB executes a handover based on the selected handover policy. This section focuses on handover
and redirection policies on the eNodeB side.
If the handover policy is handover, the eNodeB sends a handover request to the best cell in the filtered candidate cell list.
The eNodeB sends the handover request and forwards data through the X2 or S1 interface adaptively.
For intra-RAT handovers, the eNodeB sends handover requests and forwards data through the X2 or S1 interface adaptively. After X2 interfaces
are set up, data forwarding is performed preferentially over the X2 interface.
For intra-MME inter-eNodeB handovers, handover requests are sent preferentially over the X2 interface.
NOTE:
If the value of the freqBandPriorityAdjustment-r12 IE in the UECapabilityInformation message sent by the UE is Supported, the handover
type used by the eNodeB is determined by the setting of the MFBIX2HoSwitch option of the CellAlgoSwitch.MFBIAlgoSwitch
parameter. For details, see Multi-Band Compatibility Enhancement.
For inter-MME inter-eNodeB handovers, handover requests are always sent over the S1 interface.
For inter-RAT handovers, the eNodeB sends handover requests and forwards data through the S1 interface.
After sending a handover request to the target cell, the eNodeB delivers a handover command to a UE only when the admission evaluation is passed
in the target cell. Table 4-16 lists the admission determination policies.
Table 4-16 Admission conditions
Handover Type Admission Condition for Handovers (Including Intra- and Inter-RAT Handovers)
Necessary handover Admission success of any QCI
Unnecessary offload- Admission success of all QCIs

oriented handover
Handover Type Admission Condition for Handovers (Including Intra- and Inter-RAT Handovers)
Unnecessary optimization- For SPID-based handovers to HPLMN and frequency-priority-based handovers: The MultiQciHoExecOptSwitch
oriented handover option of the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter determines whether to deliver a handover
command based on the admission result of all QCIs:
If this option is selected, the eNodeB delivers a handover command only when all QCIs of the services running
on the UE are successfully admitted.
If this option is deselected, the eNodeB delivers a handover command when any QCI of the services running on
the UE is successfully admitted.
For other handovers: admission success of all QCIs
After the handover to the target cell succeeds, the eNodeB performs data forwarding. If the handover to the target cell fails, the eNodeB performs
retries and penalty.
If a UE experiences service drops during the handover, the UE re-accesses the E-UTRAN through an RRC connection reestablishment. For details, see
Connection Management.
If the handover policy is redirection, the eNodeB selects the highest-priority frequency from qualified frequencies, includes the frequency in the RRC
Connection Release message, and delivers the message to the UE.
4.1.8 Retry and Penalty for Handover Failures

If a handover to the target cell fails, the eNodeB performs different operations depending on handover admission failures or follow-up handover
execution failures.
Handover Admission Failures
If handover admission fails, the eNodeB handles the handover admission failure depending on the handover cause:
During necessary handovers or intra-eNodeB inter-cell unnecessary handovers, if the handover admission fails, the eNodeB tries the next best cell
among the candidate cells for the handover. If the eNodeB has tried all cells in the candidate cell list but handover admission still fails, the eNodeB
waits for another measurement report from the UE.
During inter-eNodeB or inter-RAT unnecessary handovers, if the handover admission fails, the eNodeB does not try the next best cell among the
candidate cells for the handover. Instead, the eNodeB waits for another measurement report from the UE after the handover failure.
During blind handovers, the eNodeB finishes the handover procedure.
If the cells in the candidate cell list experience admission failures, the retry and penalty procedure is performed on the cells.
Figure 4-12 shows the retry and penalty procedure. This figure uses the handover attempt procedure of cell A in the candidate cell list as an example.
Figure 4-12 Handover attempt procedure of cell A
Retry and penalty policies differ depending on handover admission failure causes. Therefore, different parameter settings are used to accommodate
handover type and handover admission failure causes. Table 4-17 lists the parameter settings in different scenarios.
For resource-related handover admission failures, a penalty timer can be set to impose penalty on the cell. A retry can be initiated to the cell only
after the penalty timer expires.
For non-resource-related handover admission failures, the number of penalty times can be set to impose penalty on the cell. A retry can be initiated
to the cell only when the number of penalty times has been reached.
NOTE:
After entering the penalty state, the number of penalty times is incremented by one each time the measurement result indicates that cell
A meets the handover condition.
If cell A meets the handover condition after a specified number of penalties have been imposed, the eNodeB sends a handover request to
cell A again. This process is termed as retry.
Resource-related handover admission failures are only those whose failure causes are as follows:
No radio resources available in target cell
Transport resource unavailable
Not enough User Plane Processing Resources
Radio resources not available
Control Processing Overload
Table 4-17 Penalty and retry settings for handover admission failures
Procedure Resource-related Handover Non-Resource-related Handover
Penalty for necessary Set the HoMeasComm.ResHoPreFailPunishTimer parameter Set the HoMeasComm.NonResHoPreFailPunishTimes
handovers to specify the penalty timer. parameter to specify the number of penalty times.
Penalty for unnecessary Set the HoMeasComm.OptHoPreFailPunishTimer parameter Set the HoMeasComm.NonResHoPreFailPunishTimes
handovers to specify the penalty timer. parameter to specify the number of penalty times.
Retry after the penalty N/A Set the HoMeasComm.NonResHoPreFailRetryTimes

parameter to specify the number of retry times.
During retry and penalty, the eNodeB may identify whether the penalty is caused by handover or SRVCC, depending on the
L2UBasedHoPolicyPenaltySwitch option setting of the ENodeBAlgoSwitch.HoCommOptSwitch parameter.
When this option is deselected, the eNodeB collects the number of penalties and retries without identifying the penalty causes for measurement
reports sent by UEs.
When this option is selected, the eNodeB identifies the penalty causes for measurement reports sent by UEs and collects the number of penalties
and retries on a per cause basis. For example, when the eNodeB receives a measurement report for SRVCC:
If the penalty and retry procedure performed last time was caused by handover, penalty is not imposed for the measurement report of this time.
The SRVCC procedure is executed when the handover policy fails.
If the penalty and retry procedure performed last time was caused by SRVCC, penalty is imposed for the measurement report of this time. In this
case, the eNodeB collects the number of penalties and retries caused by SRVCC.
Handover Admission Success
If admission to cell A is successful during a handover, the source eNodeB delivers a handover command to the UE. The UE has its RRC connection
reestablished with the source cell if the air interface transmission fails during the handover execution. When a handover attempt is initiated on cell A
again and handover admission succeeds, the eNodeB initiates a handover retry to cell A. The eNodeB allows consecutive handover retries to cell A. If the
target cell is an inter-frequency cell, the maximum number of retries is 10. If the target cell is an inter-RAT cell, the maximum number of retries is
specified by the CellHoParaCfg.InterRatUuHoFailRetryTimes parameter. If all the retries fail during the handover execution, the eNodeB no longer
initiates a handover retry to cell A for this UE, to prevent service drops caused by exceptions.
4.1.9 Compatibility Procedure Optimization
4.1.9.1 Handover Optimization Between UTRAN and E-UTRAN

When the GlobalProcSwitch.S1HoInDataFwdSwitch parameter is set to ON, the RNC can forward data to the eNodeB through the transport-layer
channel during UTRAN to E-UTRAN handovers.
4.1.9.2 Special Signaling Retransmission Optimization

Certain UEs do not send Radio Link Control (RLC) status reports after outgoing handovers from E-UTRAN. This causes the RLC layer to repeatedly issue
unnecessary handover commands. In large traffic volume scenarios such as important sports events, turning on the special signaling retransmission
optimization switch reduces the number of unnecessary handover commands sent by the RLC layer, which reduces resource consumption over the air
interface.
The SPECSIGRETRANSOPTSWITCH option of the ENodeBAlgoSwitch.HighLoadNetOptSwitch parameter controls special signaling retransmission
optimization.
4.1.9.3 E-UTRAN to GERAN PLMN Selection Optimization
Assume that an E-UTRAN cell and a GERAN cell are both working in RAN sharing with common carrier mode. However, the GERAN cell complies with
3GPP Release 10 or earlier, which means that this cell is not working in standard RAN sharing with common carrier mode and broadcasts only the
configured primary PLMN ID. In this case, the target PLMN ID in each request message, such as handover request or RIM request messages, sent from
the E-UTRAN cell to the GERAN cell must be the primary PLMN ID configured for the GERAN cell. Otherwise, the request fails. The
L2GPLMNChooseOptSwitch option of the GlobalProcSwitch.ProtocolMsgOptSwitch parameter has been introduced to avoid this failure. When this
option is selected, the eNodeB takes the NCL-defined PLMN IDs and includes them in the E-UTRAN to GERAN handover request messages or RIM
request messages.
4.1.9.4 Optimization of the Interaction Between Handover and E-RAB Management Procedures
When a handover procedure conflicts with an E-RAB management procedure, the eNodeB preferentially processes the handover procedure. Meanwhile,
the eNodeB replies to the EPC with an E-RAB failure response, which carries the cause value of "S1 intra system Handover Triggered", "S1 inter system
Handover Triggered", or "X2 Handover triggered". When the handover is complete, the EPC initiates the E-RAB management procedure again. If the EPC
receiving the E-RAB failure response with a preceding cause value is not capable of reinitiating the E-RAB management procedure, this procedure will
fail.
In this situation, the ErabFlowFirstSwitch option of the GlobalProcSwitch.HoProcCtrlSwitch parameter must be selected so that the eNodeB
preferentially handles the E-RAB management procedure for intra-RAT inter-eNodeB handovers or inter-RAT handovers in the handover preparation
phase. That is, if the eNodeB has received procedures such as E-RAB establishment, deletion, or modification before delivering a handover command
over the air interface, the eNodeB sends a HANDOVER CANCEL message to cancel the handover so that the E-RAB management procedure can be
performed.
4.1.9.5 Intra-E-UTRAN Handover Optimization

When the Huawei eNodeB is interconnected to a third-party eNodeB to perform intra-E-UTRAN handover, the CaHoReqWithR9ConfigSwitch option of
the GlobalProcSwitch.ProtocolCompatibilitySw parameter must be selected. This reduces handover failures caused by the lack of sourceOtherConfig-r9
and ue-ConfigRelease-r9 IEs.
4.1.9.6 Signaling Optimization for UE's UTRAN Capability Query

The eNodeB does not query UE's UTRAN capability to reduce signaling overhead when the following conditions are met:
The UeUtranCapEnquiryOptSwitch option of the GlobalProcSwitch.ProtocolMsgOptSwitch parameter is selected.
ANR is disabled.
Neighboring UTRAN cells are not configured for the serving cell.
4.2.1 Benefits
Ensures service continuity and network performance when UEs move in co-coverage networks.
Provides a means to transfer UEs and allows flexible networking to meet the service steering and load balancing requirements of operators.
4.2.2 Impacts
Network Impacts
None
Function Impacts
None
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and mutually exclusive functions have been deactivated. For
detailed operations, see the relevant feature documents.
Prerequisite Functions
None
Mutually Exclusive Functions
None
4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.3.4 Others
None

Live networks may be E-UTRAN only or a combination of E-UTRAN, UTRAN, and GERAN in any form. This document uses a network where E-UTRAN,
UTRAN, and GERAN coexist as an example to describe network operation and maintenance. Before setting parameters to activate each handover
function, refer to this section to set parameters related to common configurations.
Common configurations involve a large number of parameters. This section describes only key parameters. For details about the parameters that are not
listed, see principles in other sections and eNodeB parameter reference.
Mobility is a basic feature to maintain service continuity. Before activating basic functions of mobility, obtain information about network plan and
neighboring cell plan for neighbor relationship configuration. Table 4-18 lists the MOs related to neighbor relationship configuration. This helps check
whether the configuration is complete. The parameters related to cell setup are not described in this section.
Table 4-18 MOs related to neighbor relationship configuration
Configuration Task Attributes to Be Configured Attribute Name MOs Involved
Configuring intra-frequency External cell relationships Inter-eNodeB intra-frequency or EutranExternalCell if required

neighbor relationships inter-frequency cells within E-
UTRAN
Neighbor relationships Intra-frequency handovers EutranIntraFreqNCell
Configuring inter-frequency Neighboring frequency relationships Inter-frequency handover parameter EutranInterNFreq

neighbor relationships group
External cell relationships Inter-eNodeB intra-frequency or EutranExternalCell if required

inter-frequency cells within E-
UTRAN
Neighbor relationships Inter-frequency handovers EutranInterFreqNCell
Configuring neighbor relationships Neighboring frequency relationships Common parameter groups of UtranNFreq
with UTRAN cells UTRAN
External cell relationships UTRAN cells UtranExternalCell
Neighbor relationships Handover to UTRAN UtranNCell
Configuring neighbor relationships Neighboring frequency relationships Common parameter groups of GeranNfreqGroupArfcn
with GERAN cells GERAN
External cell relationships GERAN cells GeranExternalCell
Neighbor relationships Handover to GERAN GeranNCell
In addition, the following optional configurations are also involved:
Maximum number of neighboring frequencies, which is set in the CellUeMeasControlCfg MO.
PLMN list for an external E-UTRAN cell, which is set in the EutranExternalCellPlmn MO, if this neighboring E-UTRAN cell is working in RAN sharing
mode.
PLMN list for an external UTRAN cell, which is set in the UtranExternalCellPlmn MO if a neighboring UTRAN cell works in RAN sharing mode.
Secondary band of an external UTRAN cell if this UTRAN cell is a multi-band cell, which is set by running the ADD EUTRANEXTERNALCELLBAND
command.
PLMN list for an external GERAN cell, which is set in the GeranExternalCellPlmn MO, if a neighboring GERAN cell works in RAN sharing mode.
Table 4-19 lists the parameters for activation.

Table 4-19 Parameters used for activation of mobility management
Parameter Name Parameter ID Option Setting Notes
Handover Mode ENodeBAlgoSwitch.HoModeSwitch UtranVoipCapSwitch Set this parameter based on the VoIP capability
switch of UTRAN.
Redirection switch ENodeBAlgoSwitch.RedirectSwitch UtranFlashRedirectSwitch Set this parameter based on the fast redirection
capability of UTRAN.
Handover Mode CellHoParaCfg.HoModeSwitch UtranPsHoSwitch and Set this parameter based on the handover and
switch UtranRedirectSwitch redirection capabilities of UTRAN.
Handover Mode ENodeBAlgoSwitch.HoModeSwitch GeranPsHoSwitch, Set this parameter based on the handover, CCO,
switch GeranCcoSwitch, and and NACC capabilities of GERAN.
GeranNaccSwitch
Redirection switch ENodeBAlgoSwitch.RedirectSwitch GeranFlashRedirectSwitch Set this parameter based on the fast redirection
capability of GERAN.
Handover Mode CellHoParaCfg.HoModeSwitch GeranRedirectSwitch Set this parameter based on the redirection
switch capability of GERAN.
Handover Algo ENodeBAlgoSwitch.HoAlgoSwitch InterPlmnHoSwitch It is recommended that the options be selected

switch if inter-PLMN handovers or handovers to
neighboring cells under equivalent PLMNs
EPlmnSwitch
(EPLMNs) are allowed.
Handover Mode ENodeBAlgoSwitch.HoModeSwitch AutoGapSwitch Select this option.

switch
Compatibility ENodeBAlgoSwitch.CompatibilityCtrlSwitch UECapRprtAbnormalCtrlSwitch It is recommended that this option be selected if

Control Switch the eNodeB needs to handle compatibility issues
of UEs during measurement.
Handover Signaling ENodeBAlgoSwitch.HoSignalingOptSwitch ReduceMeasCtrlMesNumSwitch It is recommended that this option be selected

Optimized Switch to reduce the number of Uu interface
measurement configuration messages and be
deselected if UE compatibility issues need to be
considered.
S1 handover in data GlobalProcSwitch.S1HoInDataFwdSwitch N/A Turn on this switch.

forwarding switch
High Load Network ENodeBAlgoSwitch.HighLoadNetOptSwitch SPECSIGRETRANSOPTSWITCH Select this option.

Optimized Switch
Protocol Message GlobalProcSwitch.ProtocolMsgOptSwitch L2GPLMNChooseOptSwitch Select this option.

Optimization Switch
Handover Process GlobalProcSwitch.HoProcCtrlSwitch ErabFlowFirstSwitch Select this option.

Control Switch
Protocol GlobalProcSwitch.ProtocolCompatibilitySw CaHoReqWithR9ConfigSwitch Select this option.

Compatibility Switch
Measurement CellAlgoSwitch.MeasOptAlgoSwitch MEAS_OBJ_PREEMPT_SW Select this option.

Optimization
Algorithm Switch
Handover Signaling ENodeBAlgoSwitch.HoSignalingOptSwitch MultiQciHoExecOptSwitch Select this option.

Optimized Switch
Parameters used for optimization include:
Parameters that allow different handover policies to be configured for services with different QCIs. For example, parameters in the MOs in Table 4-
20.
Other parameters such as common handover parameters, common intra-RAT handover parameters, and common inter-RAT handover parameters,
which are set in HoMeasComm, IntraRatHoComm, and InterRatHoComm MOs, respectively.
Table 4-20 QCI-level parameters used for optimization of mobility management
QCI Parameter Level QCI Parameter Group MO to Which QCI Parameters QCI Parameter Group ID
Belong
Cell-level QCI parameters Intra-frequency handover IntraFreqHoGroup CellQciPara.IntraFreqHoGroupId

parameter group
Inter-frequency handover InterFreqHoGroup CellQciPara.InterFreqHoGroupId

parameter group
Common parameter group related InterRatHoCommGroup CellQciPara.InterRatHoCommGroupId

to inter-RAT handover
Common parameter group related InterRatHoUtranGroup CellQciPara.InterRatHoUtranGroupId

to inter-RAT handover to UTRAN
Common parameter group related InterRatHoGeranGroup CellQciPara.InterRatHoGeranGroupId

to inter-RAT handover to GERAN
eNodeB-level QCI parameters Inter-RAT handover policy group InterRatPolicyCfgGroup QciPara.InterRatPolicyCfgGroupId
NOTE:
The configurations apply to services with QCIs specified by CellQciPara.Qci. By default, the configurations of each parameter group in the
preceding table are the same for all QCIs. That is, the configurations with group ID being 0 are used. Customized configurations are supported to
apply different handover parameter groups to services with different QCIs.

This section uses a network where E-UTRAN, UTRAN, and GERAN coexist as an example.
Use the command examples based on live-network requirements, for example, intra-frequency, inter-frequency, E-UTRAN to UTRAN, or E-UTRAN to
GERAN handovers.
Neighbor Relationship Configuration Examples
Configurations related to intra-frequency handovers
Adding intra-frequency neighbor relationships
//Optional, required only when there are inter-eNodeB intra-frequency E-UTRAN cells
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=0, DlEarfcn=2350, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1;
//Optional, required only when neighboring E-UTRAN cells work in RAN sharing mode
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=0, ShareMcc="460", ShareMnc="22";
//Adding an intra-frequency neighboring cell
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=123, CellId=0;
Configurations related to inter-frequency handovers
Adding inter-frequency neighbor relationships
//Adding a neighboring E-UTRA frequency

ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2860, UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG, SpeedDependSPCfgInd=NOT_CFG,
//Optional, required only when there are inter-eNodeB inter-frequency E-UTRAN cells
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=1, DlEarfcn=2860, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1;
//Optional, required only when neighboring E-UTRAN cells work in RAN sharing mode
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=1, ShareMcc="460", ShareMnc="22";
//Adding an inter-frequency neighboring cell
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=123, CellId=1;
Configurations related to E-UTRAN to UTRAN handovers
Adding neighbor relationships with UTRAN cells
//Adding a neighboring UTRAN frequency

ADD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10650, UtranFddTddType=UTRAN_FDD, UtranUlArfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG
//Adding an external UTRAN cell
ADD UTRANEXTERNALCELL: Mcc="460", Mnc="00", RncId=123, CellId=2, UtranDlArfcn=10650, UtranUlArfcnCfgInd=NOT_CFG, UtranFddTddType=UTRAN_F
//Optional, required only when neighboring UTRAN cells work in RAN sharing mode
ADD UTRANEXTERNALCELLPLMN: Mcc="460", Mnc="00", RncId=123, CellId=2, ShareMcc="460", ShareMnc="20";
//Adding a neighboring UTRAN cell
ADD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="00", RncId=123, CellId=2;
Configurations related to E-UTRAN to GERAN handovers
Adding neighbor relationships with GERAN cells
//Adding a neighboring GERAN frequency

ADD GERANNFREQGROUP: LocalCellId=0, BcchGroupId=0, GeranVersion=EDGE, StartingArfcn=600, BandIndicator=GSM_dcs1800, CellReselPriorityCfgInd=N
ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0, GeranArfcn=601;
//Adding an external GERAN cell
ADD GERANEXTERNALCELL: Mcc="460", Mnc="00", GeranCellId=1, Lac=5, RacCfgInd=CFG, Rac=0, BandIndicator=GSM_dcs1800, GeranArfcn=601, Network
//Optional, required only when neighboring GERAN cells work in RAN sharing mode
ADD GERANEXTERNALCELLPLMN: GeranCellId=1, Lac=1, Mcc="460", Mnc="00", ShareMcc="460", ShareMnc="20";
//Adding a neighboring GERAN cell
ADD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="00", Lac=1, GeranCellId=1;
Activation Command Examples
//Setting policy switches of E-UTRAN to UTRAN or GERAN handovers

MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=UtranPsHoSwitch-1&UtranRedirectSwitch-1&GeranRedirectSwitch-1;
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranPsHoSwitch-1;
//Setting switches for mobility-related optimization functions

MOD ENODEBALGOSWITCH: HoAlgoSwitch=InterPlmnHoSwitch-0&EPlmnSwitch-0, HoModeSwitch=AutoGapSwitch-0, CompatibilityCtrlSwitch=UECapRprtAbno
MOD GLOBALPROCSWITCH: S1HoInDataFwdSwitch=ON, ProtocolMsgOptSwitch=L2GPLMNChooseOptSwitch-0, HoProcCtrlSwitch=ErabFlowFirstSwitch-0, Proto
MOD CELLALGOSWITCH: LocalCellId=0, MeasOptAlgoSwitch=MEAS_OBJ_PREEMPT_SW-0;
Optimization Command Examples
Configurations related to intra-frequency handovers
The following commands are required only when QCI-level parameters need to be set to different values for services with different QCIs.
//Modifying intra-frequency handover parameter groups

MOD INTRAFREQHOGROUP: LocalCellId=0, IntraFreqHoGroupId=9, IntraFreqHoA3TimeToTrig=640ms;
MOD INTRAFREQHOGROUP: LocalCellId=0, IntraFreqHoGroupId=1, IntraFreqHoA3TimeToTrig=640ms;
MOD CELLQCIPARA: LocalCellId=0, Qci=9, IntraFreqHoGroupId=9, InterFreqHoGroupId=9, InterRatHoCommGroupId=9, InterRatHoUtranGroupId=0, InterRa

Configurations related to inter-frequency handovers
//Modifying inter-frequency handover parameter groups

MOD INTERFREQHOGROUP: LocalCellId=0, InterFreqHoGroupId=9, InterFreqHoA1A2TimeToTrig=640ms;
MOD INTERFREQHOGROUP: LocalCellId=0, InterFreqHoGroupId=1, InterFreqHoA1A2TimeToTrig=640ms;

Configurations related to E-UTRAN to UTRAN handovers
//Modifying common parameter groups related to inter-RAT handover

MOD INTERRATHOCOMMGROUP: LocalCellId=0, InterRatHoCommGroupId=9, InterRatHoA1A2TimeToTrig=640ms;
//Modifying common parameter groups related to inter-RAT handover to UTRAN
MOD INTERRATHOUTRANGROUP: LocalCellId=0, InterRatHoUtranGroupId=0, InterRatHoUtranB1ThdEcn0=-20;
MOD INTERRATHOUTRANGROUP: LocalCellId=0, InterRatHoUtranGroupId=1, InterRatHoUtranB1ThdEcn0=-20;

The following commands are required only when different inter-RAT handover policies need to be configured for services with different QCIs.
//Modifying inter-RAT handover policy groups

MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, UtranHoCfg=PS_HO-1;
MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=1, UtranHoCfg=REDIRECTION-1;
MOD QCIPARA: Qci=9, InterRatPolicyCfgGroupId=0;

Configurations related to E-UTRAN to GERAN handovers
//Modifying common parameter groups related to inter-RAT handover

//Modifying common parameter groups related to inter-RAT handover to GERAN
MOD INTERRATHOGERANGROUP: LocalCellId=0, InterRatHoGeranGroupId=0, InterRatHoGeranB1TimeToTrig=64ms;
MOD INTERRATHOGERANGROUP: LocalCellId=0, InterRatHoGeranGroupId=1, InterRatHoGeranB1TimeToTrig=64ms;

The following commands are required only when different inter-RAT handover policies need to be configured for services with different QCIs.
//Modifying inter-RAT handover policy groups

MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, GeranGprsEdgeHoCfg=PS_HO-1&REDIRECTION-1;

Deactivation Command Examples
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=UtranPsHoSwitch-0&UtranRedirectSwitch-0&GeranRedirectSwitch-0;


For detailed operations, see CME-based Feature Configuration.

Use either of the following methods for activation verification:
Using counters
Observe the counters in outgoing intra-RAT handover and inter-RAT handover measurement function subsets to check whether handover functions
have taken effect.
Using signaling tracing
Observe signaling to check each phase of handover functions. Figure 4-13 is an example of signaling procedures for a successful X2-based intra-
MME inter-eNodeB handover.
Figure 4-13 Signaling procedures for a successful intra-MME inter-eNodeB handover

Operators can monitor network performance using mobility and retainability KPIs.
5 Coverage-based Handover
5.1 Overview
5.1.1 Introduction to Handover Functions
A coverage-based handover is triggered when a UE moves to the cell edge. Handovers are classified by handover target into the following types:
Intra-frequency handover, which involves only measurement-based handover
Inter-frequency handover, which involves measurement-based and blind handovers
E-UTRAN to UTRAN handover, which involves measurement-based and blind handovers
E-UTRAN to GERAN handover, which involves measurement-based and blind handovers
5.1.2 Measurement-based Handover Functions

The following functions and options are involved in measurement- and coverage-based handover functions:
Intra-frequency handover, which is specified by the IntraFreqCoverHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
Inter-frequency handover, which is specified by the InterFreqCoverHoSwitch option of the CellHoParaCfg.CellHoAlgoSwitch parameter
E-UTRAN to UTRAN handover, which is specified by the UtranRedirectSwitch or UtranPsHoSwitch option of the CellHoParaCfg.HoModeSwitch
parameter
E-UTRAN to GERAN handover, which is specified by the GeranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter
Table 5-1 lists the conditions for starting and stopping each function.
Table 5-1 Conditions for starting and stopping each measurement-based coverage-based handover
Handover Function Starting Condition Stopping Condition
Measurement- and coverage-based intra-frequency This function starts unconditionally when a UE N/A
handover is running services.
Measurement- and coverage-based inter-frequency The signal quality of the serving cell drops The signal quality of the serving cell becomes
handover below the threshold for inter-frequency higher than or equal to the threshold for inter-
measurement. That is, the eNodeB receives frequency measurement. That is, the eNodeB
the corresponding inter-frequency event A2 receives the corresponding event A1 report.
report. For details, see 5.1.4 Event A2 Involved
in Coverage-based Handover.
Measurement- and coverage-based handover from The signal quality of the serving cell drops The signal quality of the serving cell becomes
E-UTRAN to UTRAN below the threshold for inter-RAT higher than or equal to the threshold for inter-
measurement. That is, the eNodeB receives RAT measurement. That is, the eNodeB receives
the corresponding inter-RAT event A2 report. the corresponding event A1 report.
Measurement- and coverage-based handover from
For details, see 5.1.4 Event A2 Involved in
E-UTRAN to GERAN
Coverage-based Handover.
5.1.3 Blind Handover Functions

The following functions and options are involved in blind coverage-based handover functions:
Inter-frequency handover, which is specified by the EmcInterFreqBlindHoSwitch and IfCoverPreBlindHoSwitch options of the
CellHoParaCfg.CellHoAlgoSwitch parameter
E-UTRAN to UTRAN handover, which is specified by the UtranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter
E-UTRAN to GERAN handover, which is specified by the GeranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter
Table 5-2 lists the conditions for starting and stopping each function.
Table 5-2 Conditions for starting and stopping each blind coverage-based handover
Handover Function Starting Condition Stopping Condition
Blind coverage-based The signal quality of the serving cell drops below the The signal quality of the serving cell becomes higher than or
inter-frequency threshold for inter-RAT or inter-frequency blind mode. That equal to the threshold for inter-RAT or inter-frequency blind
handover is, the eNodeB receives an inter-frequency or inter-RAT blind handling. That is, the eNodeB receives the corresponding
event A2 report. For details, see 5.1.4 Event A2 Involved in event A1 report.
Blind coverage-based Coverage-based Handover.
handover from E-
UTRAN to UTRAN
Blind coverage-based
handover from E-
UTRAN to GERAN
Blind coverage-based inter-frequency handover consists of preferential blind handover and emergency blind handover. Preferential blind handover is
specific to inter-frequency handover. The IfCoverPreBlindHoSwitch option of the CellHoParaCfg.CellHoAlgoSwitch parameter specifies whether to
enable this function. If this option is selected, the conditions for initiating preferential blind handover and measurement-based inter-frequency handover
are the same. When receiving an inter-frequency event A2 report, the eNodeB initiates a preferential blind handover instead of performing a
measurement-based inter-frequency handover. For details about inter-frequency event A2 reports, see 5.1.4 Event A2 Involved in Coverage-based
Handover.
5.1.4 Event A2 Involved in Coverage-based Handover

Different event A2 threshold parameters are used to flexibly initiate functions listed in Table 5-1 and Table 5-2. Table 5-3 lists event A2 types classified in
this document.
Table 5-3 Event A2 types
Event A2 Type Event A2 Triggering Quantity Parameter Event A2 Threshold Parameter
Inter-frequency event A2 IntraRatHoComm.A3InterFreqHoA1A2TrigQuana InterFreqHoGroup.A3InterFreqHoA2ThdRsrp

or
InterFreqHoGroup.A3InterFreqHoA2ThdRsrqa
IntraRatHoComm.InterFreqHoA1A2TrigQuanb InterFreqHoGroup.InterFreqHoA2ThdRSRP or
InterFreqHoGroup.InterFreqHoA2ThdRSRQb
Inter-RAT event A2c InterRatHoComm.InterRatHoA1A2TrigQuan InterRatHoCommGroup.InterRatHoA2ThdRsrp

or
InterRatHoCommGroup.InterRatHoA2ThdRsrq
Inter-frequency or inter-RAT blind InterRatHoComm.InterRatHoA1A2TrigQuan CellHoParaCfg.BlindHoA1A2ThdRsrp or

event A2 CellHoParaCfg.BlindHoA1A2ThdRsrq
a: These parameters are used when the EutranInterNFreq.InterFreqHoEventType parameter is set to EventA3.
b: These parameters are used when the EutranInterNFreq.InterFreqHoEventType parameter is set to EventA4 or EventA5.
c: When an event A2 threshold offset is set for UTRAN and GERAN, inter-RAT event A2 is further classified into UTRAN event A2 and GERAN event A2.
Event A1 and event A2 usually work in pairs. Therefore, the classifications of event A1 are the same as those of event A2. That is, event A1 is also
classified into inter-frequency event A1, inter-RAT event A1, and inter-frequency or inter-RAT blind event A1.
NOTE:
In the following scenarios, the eNodeB delivers measurement configurations only for blind event A2 but not for measurement event A2:
The UE does not support inter-RAT measurements.

The configured measurement event A2 threshold is lower than or equal to the blind event A2 threshold.
5.1.5 Principles for Selecting UTRAN or GERAN for Inter-RAT Handovers

This section describes the principles for selecting UTRAN or GERAN for measurement-based or blind inter-RAT handovers.
Measurement-based Handover
Upon receiving an inter-RAT event A2 report, the eNodeB starts UTRAN measurement and GERAN measurement simultaneously by default. This is
because the measurement configuration for inter-RAT event A2 delivered by the eNodeB is not RAT-specific. In subsequent operations, the eNodeB
determines whether to execute the handover to UTRAN or GERAN based on the decided target cell or target frequency.
If service-type-based RAT steering is enabled, the eNodeB selects only the highest-priority RAT for measurement after receiving an inter-RAT event A2
report. This is equivalent to enabling only inter-RAT handover to UTRAN or GERAN. Service-type-based RAT steering is controlled by parameters in Table
5-4.
Table 5-4 RAT priority parameters for measurement-based handover
Service Type Option RAT Priority Parameter Setting Notes
QCI-1 services SrvccRatSteeringSwitch option of CSFallBackBlindHoCfg.InterRatHighestPri It is recommended that

included the this option be selected
CSFallBackBlindHoCfg.InterRatSecondPri
ENodeBAlgoSwitch.HoAlgoSwitch when SRVCC to UTRAN or
parameter CSFallBackBlindHoCfg.InterRatLowestPri GERAN is enabled.
QCI-1 services PsRatSteeringSwitch option of the CnOperatorHoCfg.PsInterRatHighestPri It is recommended that

excluded ENodeBAlgoSwitch.HoAlgoSwitch this option be selected
CnOperatorHoCfg.PsInterRatSecondPri
parameter when the handover policy
CnOperatorHoCfg.PsInterRatLowestPri to UTRAN or GERAN is
handover or redirection.
NOTE:
The RatLayerSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter also controls service-type-based RAT steering. This option will
not be used in later versions and therefore is not recommended. When this option is selected, service-type-based RAT steering takes effect on
both voice and data services. When this option is deselected, the SrvccRatSteeringSwitch and PsRatSteeringSwitch options of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter control the service-type-based RAT steering functions for voice and data services, respectively.
Blind Handover
Inter-RAT blind handover applies only to services excluding QCI-1 services. The eNodeB selects highest-priority frequencies based on RAT priority
parameters listed in Table 5-5.
Table 5-5 RAT priority parameters for blind handover
Mode eNodeB-level RAT Priority Parameters for Data Services Cell-level RAT Priority Parameters for Data Services
RAT steering is disabled CSFallBackBlindHoCfg.InterRatHighestPri CellOpHoCfg.InterRatHighestPri
CSFallBackBlindHoCfg.InterRatSecondPri CellOpHoCfg.InterRatSecondPri
CSFallBackBlindHoCfg.InterRatLowestPri CellOpHoCfg.InterRatLowestPri
RAT steering is enabled CnOperatorHoCfg.PsInterRatHighestPri N/A
CnOperatorHoCfg.PsInterRatSecondPri
CnOperatorHoCfg.PsInterRatLowestPri
NOTE:
The PsRatSteeringSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable RAT steering for data services.
The RatLayerSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter also controls the RAT steering function. This option will not be
used in later versions and therefore is not recommended. When this option is selected, RAT steering takes effect on both voice and data services.
When this option is deselected, the PsRatSteeringSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter controls the RAT steering
function for data services.
5.2 Coverage-based Intra-frequency Handover
5.2.1 Principles
The IntraFreqCoverHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.
Intra-frequency handover involves only coverage-based handover. The eNodeB delivers measurement configurations after RRC connections are set up.
Intra-frequency handover does not include the handover function initiation decision phase because the eNodeB executes the handover when any target
cell meeting the handover requirement is available.
This function does not involve the blind mode. Figure 5-1 shows the differences between this function and the basic handover process. This section
describes only the differences.
Figure 5-1 Process of coverage-based intra-frequency handover
The eNodeB acquires target cells for coverage-based intra-frequency handover from event A3 reports. The IntraRatHoComm.IntraFreqHoA3TrigQuan
and IntraRatHoComm.IntraFreqHoA3RprtQuan parameters specify the triggering quantity and reporting quantity of event A3, respectively.
5.2.2.1 Benefits
Coverage-based intra-frequency handovers reduce interference from intra-frequency neighboring cells on an intra-frequency network, decreasing the
service drop rate.
5.2.2.2 Impacts
Network Impacts
None
Function Impacts
RAT Function Name Function Switch Reference Description
FDD None N/A N/A N/A
TDD DL flexible 3D beamforming BfSwitch option of the Massive MIMO (TDD) When certain UEs work in beamforming
CellAlgoSwitch.BfAlgoSwitch mode in massive MIMO cells, the RSRP of
parameter intra-frequency neighboring cells measured
by the UEs may be greater than the actual
value. In this case, premature handovers
possibly occur, increasing the number of
intra-frequency handovers. In addition,
handovers to the neighboring cells will
decrease the intra-frequency handover
success rate due to actual low RSRP values.
5.2.3 Requirements
5.2.3.1 Licenses
None
5.2.3.2 Software
None
None
5.2.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
5.2.3.4 Others
None

Before activating this function, refer to 4.4.1.1 Data Preparation and set basic mobility function parameters based on onsite requirements.
Table 5-6 and Table 5-7 describe the parameters used for function activation and optimization, respectively.
Table 5-6 Parameters used for activation of coverage-based intra-frequency handover
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch IntraFreqCoverHoSwitch Select this option.
Table 5-7 Parameters used for optimization of coverage-based intra-frequency handover
Parameter Name Parameter ID Setting Notes
A3 measurement trigger IntraRatHoComm.IntraFreqHoA3TrigQuan Set this parameter to its default value.

quantity
//Activating the function

MOD ENODEBALGOSWITCH: HoAlgoSwitch=IntraFreqCoverHoSwitch-1;
//Setting the triggering quantity of event A3

MOD INTRARATHOCOMM: IntraFreqHoA3TrigQuan=RSRP;
MOD ENODEBALGOSWITCH: HoAlgoSwitch=IntraFreqCoverHoSwitch-0;


Using counters
Observe the values of the counters listed in Table 5-8. If they have non-zero values, this function has taken effect.
Table 5-8 Counters related to intra-frequency handover
Counter ID Counter Name
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut
1. The eNodeB receives an intra-frequency A3 report.
2. The eNodeB delivers an RRC Connection Reconfiguration message carrying a Handover Command.
For FDD, this feature supports quick configuration of counter collection by feature using the U2000. The measurement for the counters related to this
feature can be set in a single operation. These counters are determined by the counter-feature relationships listed in the performance counter reference.
For details about the operations, see iManager U2000 MBB Network Management System Product Documentation.

Monitor the following KPIs to observe network performance:
Intra-Frequency Handover Out Success Rate
Call Drop Rate (VoIP) and Service Drop Rate
Monitor the counters in Table 5-9 to check the running status of this function.
Table 5-9 Counters related to intra-frequency handover
1526726995 L.HHO.IntraeNB.IntraFreq.PrepAttOut
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccOut
5.3 Coverage-based Inter-frequency Handover
5.3.1 Principles
The InterFreqCoverHoSwitch option of the CellHoParaCfg.CellHoAlgoSwitch parameter specifies whether to enable this function.
Inter-duplex-mode handover between FDD and TDD is also a type of inter-frequency handover.
Figure 5-2 shows the differences between this function and the basic handover process. This section describes only the differences.
Figure 5-2 Process of coverage-based inter-frequency handover
This function involves measurement-based handover, preferential blind handover, and emergency blind handover. Figure 5-3 shows the detailed
procedures for the subfunctions.
For details about starting and stopping, measurement, and target cell decision for measurement-based handover, see 5.3.1.1 Initiation Decision of
Measurement-based Handover, 5.3.1.2 Measurement Configuration Delivery, and 5.3.1.3 Target Cell Decision for Measurement-based Handover,
respectively.
For details about preferential blind handover, see 5.3.1.4.1 Preferential Blind Handover.
For details about emergency blind handover, see 5.3.1.4.2 Emergency Blind Handover.
Figure 5-3 Subfunctions of coverage-based inter-frequency handover

The eNodeB starts measurement- and coverage-based handover and follow-up inter-frequency measurement when receiving an inter-frequency event
A2 report. If an inter-frequency event A1 report is received during the procedure, the eNodeB stops this function.
During a coverage-based inter-frequency handover, the sequence that the A1/A2 measurement configurations are delivered is controlled by the
ReduceInvalidA1A2RptSigSwitch option of the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter.
If the option is selected, the eNodeB delivers measurement configuration for event A2 first when setting up an RRC connection for a UE. Then, the
eNodeB delivers measurement configuration for event A1 after receiving an event A2 report from the UE. This reduces unnecessary signaling
exchanges. Figure 5-4 shows inter-frequency measurement based on event A4/A5. Figure 5-6 shows inter-frequency measurement based on event
A3.
If the option is deselected, the eNodeB delivers both A2 and A1 measurement configurations when setting up an RRC connection for a UE. Figure 5-5
shows inter-frequency measurement based on event A4/A5. Figure 5-7 shows inter-frequency measurement based on event A3.
When the IntraRatHoComm.InterFreqHoA1A2TrigQuan parameter is set to BOTH and the TrigQuanBothMeasOptSw option of the
ENodeBAlgoSwitch.HoCommOptSwitch parameter is selected, RSRP- and RSRQ-based measurement triggering and stopping procedures are mutually
independent. When an RSRP-triggered event A2 report is received, RSRP-based measurement is triggered irrespective of whether there is RSRQ-based
measurement. When RSRP-triggered event A1 report is received, RSRP-based measurement is stopped.
Figure 5-4 Triggering and stopping of measurement when event A2 configuration is delivered earlier than event A1 configuration (inter-frequency
measurement based on event A4/A5)
Figure 5-5 Triggering and stopping of measurement when event A2 and A1 configurations are delivered simultaneously (inter-frequency measurement
based on event A4/A5)
Figure 5-6 Triggering and stopping of measurement when event A2 configuration is delivered earlier than event A1 configuration (inter-frequency
measurement based on event A3)
Figure 5-7 Triggering and stopping of measurement when event A2 and A1 configurations are delivered simultaneously (inter-frequency measurement
based on event A3)
5.3.1.1.1 Event A2
Table 5-10 describes thresholds related to event A2.
Table 5-10 Thresholds related to event A2 for coverage-based inter-frequency handover
Threshold Parameter Value Description

Name
A3 based Interfreq A2 InterFreqHoGroup.A3InterFreqHoA2ThdRsrpa + The IntraRatHoComm.A3InterFreqHoA1A2TrigQuan

RSRP threshold parameter specifies the triggering quantity for events A1 and
eNBCnOpQciRsvdPara.RsvdPara14b
A2 related to A3-based inter-frequency handovers.
For wireless broadband (WBB) UEs, the following thresholds

are used to flexibly control the probabilities of inter-
frequency handovers:
A3InterFreqHoA2ThdRsrp = max(-140, min(-43,

A3 Based Interfreq A2 InterFreqHoGroup.A3InterFreqHoA2ThdRsrq InterFreqHoGroup.A3InterFreqHoA2ThdRsrp +
RSRQ Threshold SpidCfg.InterFreqHoA2RsrpThdFactor))
A3InterFreqHoA2ThdRsrq = max(-40, min(-6,

InterFreqHoGroup.A3InterFreqHoA2ThdRsrq +
SpidCfg.InterFreqHoA2RsrqThdFactor))
A4A5 Based Interfreq InterFreqHoGroup.InterFreqHoA2ThdRSRPa + The IntraRatHoComm.InterFreqHoA1A2TrigQuan parameter

A2 RSRP Threshold specifies the measurement quantity for events A1 and A2
eNBCnOpQciRsvdPara.RsvdPara14 b
related to A4- or A5-based inter-frequency handovers.
A4A5 Based Interfreq InterFreqHoGroup.InterFreqHoA2ThdRSRQ For WBB UEs, the following thresholds are used to flexibly
A2 RSRQ Threshold control the probabilities of inter-frequency handovers:
InterFreqHoA2ThdRsrp = max(-140, min(-43,

InterFreqHoGroup.InterFreqHoA2ThdRsrp +
SpidCfg.InterFreqHoA2RsrpThdFactor))
InterFreqHoA2ThdRsrq = max(-40, min(-6,

InterFreqHoGroup.InterFreqHoA2ThdRsrq +
SpidCfg.InterFreqHoA2RsrqThdFactor))
a: The RSRP threshold for event A2 for inter-duplex-mode handovers between FDD and TDD can be set separately. For details, see Table 5-11.
b: In RAN sharing scenarios, different eNBCnOpQciRsvdPara.RsvdPara14 parameter values need to be set only when the event A2 RSRP thresholds
d b fi d fl ibl f diff d QCI
need to be configured flexibly for different operators and QCIs.
Name
For inter-duplex-mode handover between FDD and TDD, Huawei eNodeBs allow different RSRP thresholds for event A2 to be set for FDD and TDD
frequencies for events A3/A4/A5. The different settings enable UEs to be preferentially handed over to FDD or TDD frequencies during a coverage-based
handover. For details, see Table 5-11. This separate setting is used when FDD and TDD cells are co-sited but FDD cells use different policies from TDD
cells.
Table 5-11 Thresholds related to event A2 in inter-duplex-mode cases
Duplex Mode Parameter ID of the A2 Threshold Offset Parameter ID of the Threshold Description
FDD for CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset InterFreqHoGroup.A3InterFreqHoA2ThdRsrp When the threshold offset is not 0, the
A3/A4/A5 (eNodeB level) or or threshold for event A2 delivered by
CellOpHoCfg.FddIfHoA2ThdRsrpOffset (cell InterFreqHoGroup.InterFreqHoA2ThdRSRP the eNodeB is the sum of the
level) threshold and offset parameter values.
The RSRP threshold for event A2 is
TDD for CnOperatorHoCfg.TddIfHoA2ThdRsrpOffset
accompanied by an offset, while the
A3/A4/A5 (eNodeB level) or RSRQ threshold for event A2 is not.
CellOpHoCfg.TddIfHoA2ThdRsrpOffset (cell
level)
When the FDD and TDD threshold offsets are set to different valid values, the eNodeB delivers the two inter-frequency event A2 thresholds using
different measurement IDs. After receiving event A2 reports from the UE, the eNodeB delivers A3/A4/A5 inter-frequency measurement configurations
based on the following principles:
When the event A2 threshold offset is specified by CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset or CellOpHoCfg.FddIfHoA2ThdRsrpOffset, the

eNodeB delivers A3/A4/A5 inter-frequency measurement configurations related to FDD frequencies.
When the event A2 threshold offset is specified by CnOperatorHoCfg.TddIfHoA2ThdRsrpOffset or CellOpHoCfg.TddIfHoA2ThdRsrpOffset, the

eNodeB delivers A3/A4/A5 inter-frequency measurement configurations related to TDD frequencies.
When the FDD and TDD threshold offsets are set to the same valid values, the eNodeB delivers one measurement configuration for event A2. After
receiving event A2 reports from the UE, the eNodeB delivers A3/A4/A5 inter-frequency measurement configurations related to FDD and TDD frequencies.
When any cell-level threshold offset parameter is valid, the cell-level instead of the eNodeB-level threshold offsets take effect. This policy applies to the
FDD and TDD co-sited scenarios where FDD cell policies differ from TDD cell policies.
5.3.1.1.2 Event A1

Name
A3 based interfreq A1 InterFreqHoGroup.A3InterFreqHoA1ThdRsrp The IntraRatHoComm.A3InterFreqHoA1A2TrigQuan

RSRP threshold parameter specifies the triggering quantity for events A1 and
A2 related to A3-based inter-frequency handovers.
A3 Based Interfreq A1 InterFreqHoGroup.A3InterFreqHoA1ThdRsrq
RSRQ Threshold
A4A5 Based Interfreq InterFreqHoGroup.InterFreqHoA1ThdRSRP The IntraRatHoComm.InterFreqHoA1A2TrigQuan parameter

A1 RSRP Threshold specifies the triggering quantity for events A1 and A2 related
to A4- or A5-based inter-frequency handovers.
A4A5 Based Interfreq InterFreqHoGroup.InterFreqHoA1ThdRSRQ
A1 RSRQ Threshold

When the CellAlgoSwitch.CovBasedInterFreqHoMode parameter is set to HandoverImmediately, the eNodeB selects frequencies and delivers
measurement configurations as follows:
1. When the conditions in the first two columns of Table 5-13 are met, the eNodeB selects the highest-priority frequency according to the frequency
priority parameters listed in this table and delivers the measurement configuration to a UE. If the priorities are the same, the eNodeB proceeds with
the next step.
Table 5-13 Frequency priority parameters when the directional handover function takes effect
Directional Handover Activation Condition UE Condition Frequency Priority Parameter
Both of the following options are selected: UEs with voice bearers EutranInterNFreq.VoipPriority
VoipMeasFreqPriSwitch option of the CellAlgoSwitch.MultiFreqPriControlSwitch

parameter
HO_USE_VOIP_FREQ_ALLOWED option of the CellQciPara.QciAlgoSwitch

parameter
Directional Handover Activation Condition UE Condition Frequency Priority Parameter
The PsMeasFreqPriSwitch option of the CellAlgoSwitch.MultiFreqPriControlSwitch UEs without voice EutranInterNFreq.PsPriority

parameter is selected. bearers
2. When the conditions in the first column of Table 5-14 are met, the eNodeB selects a high-priority frequency according to the frequency priority
parameters listed in this table and delivers the measurement configuration. If the priorities are the same, the eNodeB proceeds with the next step.
Table 5-14 Frequency priority parameters when the directional handover function does not take effect
Frequency Priority Configuration Policy Frequency Priority Parameter
Both of the following conditions are met: EutranInterNFreq.ConnFreqPriority
The CellAlgoSwitch.MultiCnConnFreqPriSw parameter is set to OFF.
The FixedMeasObjIDSwitch option of the

CellAlgoSwitch.MultiFreqPriControlSwitch parameter is deselected.
Both of the following conditions are met: EutranInterNFreq.MeasFreqPriority
The CellAlgoSwitch.MultiCnConnFreqPriSw parameter is set to OFF.
The FixedMeasObjIDSwitch option of the

CellAlgoSwitch.MultiFreqPriControlSwitch parameter is selected.
The CellAlgoSwitch.MultiCnConnFreqPriSw parameter is set to ON. RatFreqPriorityGroup.ConnFreqPriority and

CellOp.RatFreqPriorityGroupId configured for different operators
3. If the priorities are still the same, the eNodeB randomly selects a high-priority frequency and delivers the measurement configuration.
When the CellAlgoSwitch.CovBasedInterFreqHoMode parameter is set to BasedOnSignalStrength or BasedOnFreqPriority, the eNodeB selects
frequencies and delivers measurement configurations as follows:
1. When the conditions in the first two columns of Table 5-13 are met, the eNodeB selects the highest-priority frequency according to the frequency
priority parameters listed in this table and delivers the measurement configuration to a UE. If the priorities are the same, the eNodeB proceeds with
the next step.
2. The eNodeB selects a frequency based on the priority specified by the EutranInterNFreq.MeasFreqPriority parameter and delivers the measurement
configuration to the UE.
5.3.1.3 Target Cell Decision for Measurement-based Handover

When a macro eNodeB communicates with a pico eNodeB through an S1 interface and the pico eNodeB connects to the MME through S1-AG
aggregation, a macro-to-pico handover can be initiated only if the tracking area code (TAC) of the pico eNodeB in a measurement report is within the
range from HeNbTacRangeGroup.TacStart to HeNbTacRangeGroup.TacEnd. For details about S1-AG, see S1-C Aggregation in the SVA3200AG product
documentation.
The eNodeB acquires target cells from event A3, A4, and A5 reports. The EutranInterNFreq.InterFreqHoEventType parameter specifies the event to be
used by the eNodeB.
NOTE:
When Thresh1 for event A5 is less than or equal to the threshold for blind event A2, the eNodeB does not deliver measurement configurations
related to event A5.
After receiving event A3, A4, or A5 reports, the eNodeB initiates coverage-based inter-frequency handover based on the value of the
CellAlgoSwitch.CovBasedInterFreqHoMode parameter:
If the parameter value is HANDOVERIMMEDIATELY, the eNodeB immediately determines whether to perform the handover when receiving a
measurement report.
If the parameter value is BASEDONSIGNALSTRENGTH, the eNodeB waits a period specified by IntraRatHoComm.CovBasedIfHoWaitingTimer and
then determines whether to perform the handover to the strongest neighboring cell in the target cell list.
If the parameter value is BASEDONFREQPRIORITY, the eNodeB preferentially considers the frequency measurement priority specified by the
EutranInterNFreq.MeasFreqPriority parameter. In addition, the eNodeB considers signal strength and then determines whether to perform the
handover.
The first mode is always adopted for emergency call services. That is, the eNodeB immediately selects a cell and initiates the handover when receiving a
measurement report.
5.3.1.3.1 Event A3
The IntraRatHoComm.A3InterFreqHoA1A2TrigQuan and IntraRatHoComm.IntraFreqHoA3RprtQuan parameters specify the triggering quantity and
reporting quantity of event A3, respectively.
5.3.1.3.2 Event A4
Value Description
InterFreqHoGroup.InterFreqHoA4ThdRSRP + The IntraRatHoComm.InterFreqHoA1A2TrigQuan parameter specifies the

EutranInterNFreq.IfHoThdRsrpOffset triggering quantity.
The IntraRatHoComm.InterFreqHoA4RprtQuan parameter specifies the
InterFreqHoGroup.InterFreqHoA4ThdRSRQ reporting quantity.
5.3.1.3.3 Event A5
Table 5-16 and Table 5-17 describe Thresh1 and Thresh2 for event A5, respectively.
Table 5-16 Thresh1 for event A5 for coverage-based inter-frequency handover
Value Description
InterFreqHoGroup.InterFreqHoA5Thd1Rsrp The IntraRatHoComm.InterFreqHoA1A2TrigQuan and

IntraRatHoComm.InterFreqHoA4RprtQuan parameters determine the
triggering quantity and reporting quantity of Thresh1 for event A5,
InterFreqHoGroup.InterFreqHoA5Thd1Rsrq respectively. The triggering quantity and reporting quantity for event A5
are the same as those for event A4.
Table 5-17 Thresh2 for event A5 for coverage-based inter-frequency handover
Value Description
InterFreqHoGroup.InterFreqHoA4ThdRSRP + The IntraRatHoComm.InterFreqHoA1A2TrigQuan and

EutranInterNFreq.IfHoThdRsrpOffset IntraRatHoComm.InterFreqHoA4RprtQuan parameters determine the
triggering quantity and reporting quantity of Thresh2 for event A5,
respectively. The triggering quantity and reporting quantity for event A5
InterFreqHoGroup.InterFreqHoA4ThdRSRQ
are the same as those for event A4.
5.3.1.4 Principles of Blind Handover Functions

This section describes starting and stopping of and target cell or target frequency decision for coverage-based blind handover.
Coverage-based blind handover consists of preferential blind handover and emergency blind handover.
E-UTRAN TDD and E-UTRAN FDD can be considered as two independent RATs in inter-duplex-mode handovers between FDD and TDD. The priorities of
TDD and FDD are determined as follows:
If the CnOperatorHoCfg.FirstRatPri parameter is set to EUTRAN, E-UTRAN TDD and E-UTRAN FDD are not prioritized.
If the CnOperatorHoCfg.SecondRatPri parameter is set to NULL, handover is performed only to frequencies of the RAT specified by the
CnOperatorHoCfg.FirstRatPri parameter.
NOTE:
If both the CnOperatorHoCfg.FirstRatPri parameter and the cell-level parameter CellOpHoCfg.FirstRatPri are set, the cell-level parameter is
used as the actual value. This policy applies to the FDD and TDD co-sited scenarios where FDD cell policies differ from TDD cell policies.
5.3.1.4.1 Preferential Blind Handover

The IfCoverPreBlindHoSwitch option of the CellHoParaCfg.CellHoAlgoSwitch parameter specifies whether to enable preferential blind handover.
The handover policy for preferential blind handover is handover. That is, the eNodeB initiates a handover to a qualified inter-frequency cell.
Function Initiation Decision
When a UE sends an inter-frequency event A2 report, the eNodeB triggers a preferential blind handover instead of a measurement-based inter-frequency
handover. If the eNodeB receives an inter-frequency event A1 report before the preferential blind handover is completed, the eNodeB stops the
preferential blind handover.
The same parameters are used by preferential blind handover and measurement-based handover for inter-frequency event A2 and A1 reports, as listed
in Table 5-10 and Table 5-12. Therefore, the two functions are always triggered simultaneously.
Compared with measurement-based handovers, target cell selection for preferential blind handovers is faster because the latter adopts blind mode. This
means that a preferential blind handover is preferentially performed even if the two functions are triggered simultaneously.
Target Cell Decision
The EutranInterFreqNCell.BlindHoPriority parameter specifies the target selection priority. A neighboring cell with a high priority is preferentially
selected. If none of the neighboring cells are configured with the priority (EutranInterFreqNCell.BlindHoPriority is set to 0), the eNodeB performs a
measurement-based handover instead of a preferential blind handover.
5.3.1.4.2 Emergency Blind Handover

The EmcInterFreqBlindHoSwitch option of the CellHoParaCfg.CellHoAlgoSwitch parameter specifies whether to enable emergency blind handover.
The handover policy for emergency blind handover is redirection. That is, the eNodeB initiates a redirection to a qualified target frequency.
Function Initiation Determination
An emergency blind handover is triggered when a UE sends an inter-frequency or inter-RAT blind event A2 report. Non-serving E-UTRA frequencies are
preferentially selected.
If the eNodeB receives the event while processing the handover, the eNodeB records the event. If the handover preparation fails, the eNodeB performs
emergency blind handover. If the eNodeB receives an inter-frequency or inter-RAT blind event A1 report before the emergency blind handover is
completed, the eNodeB stops the emergency blind handover.
When the CellAlgoSwitch.VolteRedirectSwitch parameter is set to ON, emergency blind handover can be triggered for services with QCI of 1. In this
case, the cause value in the release message sent from the eNodeB to the MME is always User Inactivity.
Table 5-18 lists the thresholds for inter-frequency or inter-RAT blind events A1 and A2.
Table 5-18 Thresholds for inter-frequency or inter-RAT blind events A1 and A2
Value Description
CellHoParaCfg.BlindHoA1A2ThdRsrp The InterRatHoComm.InterRatHoA1A2TrigQuan parameter determines

the threshold to be used.
Other event-related parameters except threshold parameters are the same
CellHoParaCfg.BlindHoA1A2ThdRsrq as those for inter-RAT events A2 and A1. The parameters include
InterRatHoCommGroup.InterRatHoA1A2Hyst and
InterRatHoCommGroup.InterRatHoA1A2TimeToTrig.
Target Frequency Determination
A scenario is regarded as a fast fading scenario if the interval between measurement configuration delivering and blind event A2 reporting is less than
the CellHoParaCfg.CovBasedIntraRatMeasTime parameter value. In fast fading scenarios, the eNodeB determines that measurement has not been
performed on frequencies whose information has been delivered to UEs. In other scenarios, the eNodeB determines that measurement has been
performed on such frequencies.
The eNodeB selects the RAT that has not been measured.
If E-UTRAN is selected, the eNodeB then selects the frequency with the highest priority as follows:
1. The eNodeB selects the frequency of the neighboring cells with the highest priority based on the values of EutranInterFreqNCell.BlindHoPriority. If
the priorities are the same, the eNodeB randomly selects a frequency of these cells.
2. If the EutranInterFreqNCell.BlindHoPriority parameter is not configured for any of the cells, the eNodeB selects the frequency with the highest
priority based on the values of the EutranInterNFreq.ConnFreqPriority parameter.
5.3.2.1 Benefits
With coverage-based inter-frequency handovers, the coverage in areas with weak LTE coverage or coverage holes can be supplemented by inter-
frequency neighboring cells, decreasing the service drop rate.
5.3.2.2 Impacts
Network Impacts
None
Function Impacts
FDD Service-based inter- SrvBasedInterFreqHoSw option Mobility Management in When inter-frequency measurement
TDD frequency handover of the Connected Mode frequency priority control in the
CellAlgoSwitch.HoAllowedSwitch coverage-based inter-frequency handover
parameter function is enabled for VoLTE UEs, the
VoLTE settings must be the same among
frequencies if the service-based inter-
frequency handover switch is turned on.
Meanwhile, inter-frequency measurement
frequency priority control does not take
effect on VoLTE UEs.
FDD MOCN cell reselection None RAN Sharing MOCN cell reselection priority
TDD priority configuration configuration is incompatible with the
RAN sharing information of the inter-
frequency blind redirection frequencies in
coverage-based inter-frequency
handover.
5.3.3 Requirements
5.3.3.1 Licenses
None
5.3.3.2 Software
None
None
5.3.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
5.3.3.4 Others
None

Table 5-19 Parameters used for activation of coverage-based inter-frequency handover
Handover Algo CellHoParaCfg.CellHoAlgoSwitch InterFreqCoverHoSwitch, Select the InterFreqCoverHoSwitch and

Switch EmcInterFreqBlindHoSwitch, and EmcInterFreqBlindHoSwitch options when
IfCoverPreBlindHoSwitch you need to enable this function. If a target
neighboring cell completely includes the
source cell in coverage, it is recommended
that the IfCoverPreBlindHoSwitch option be
selected.
Downlink EARFCN EutranInterNFreq.DlEarfcn N/A These parameters need to be configured

when inter-frequency blind redirection is
Mobile country code EutranInterFreqNCell.Mcc triggered when there are no neighboring
cells.
The frequencies meeting all the following
conditions are selected:
Frequencies other than those of

neighboring cells
Frequencies requiring blind redirection
Frequencies that have been configured

Mobile network EutranInterFreqNCell.Mnc
in the EutranInterNFreq MO
code
Multi Frequency CellAlgoSwitch.MultiFreqPriControlSwitch VoipMeasFreqPriSwitch and Select the options when a directional
Priority Control PsMeasFreqPriSwitch handover is required.
Switch
QCI Algorithm CellQciPara.QciAlgoSwitch HO_USE_VOIP_FREQ_ALLOWED

Switch
HeNB TAC Range HeNbTacRangeGroup.HeNbTacRaGId N/A Set these parameters based on the network
Group ID plan.
Set TAC information about a pico eNodeB
only when a macro eNodeB communicates
with the pico eNodeB through an S1
TAC Start Mark HeNbTacRangeGroup.TacStart interface and the pico eNodeB connects to
the MME through S1-AG aggregation.
The values of TACs of pico eNodeBs
connected through S1-AG aggregation must
TAC End Mark HeNbTacRangeGroup.TacEnd
be different from those of other pico
eNodeBs or macro eNodeBs.
Multi Op Freq CellAlgoSwitch.MultiCnConnFreqPriSw N/A It is recommended that the switch be turned

Priority For on and operator-specific frequency priorities
Connected Mode Sw be set when you need to reduce inter-
operator handovers in RAN sharing with
RAT Frequency CellOp.RatFreqPriorityGroupId common carrier mode.
Priority Group ID
Frequency Priority RatFreqPriorityGroup.ConnFreqPriority

for Connected Mode
Table 5-20 Parameters used for optimization of coverage-based inter-frequency handover
Blind handover Priority EutranInterFreqNCell.BlindHoPriority It is recommended that this parameter be set to a value ranging from
1 to 16 for neighboring cells whose coverage includes that of the
serving cell.
Cell Measure Priority EutranInterFreqNCell.CellMeasPriority It is recommended that a high priority be set for neighboring cells with
favorable coverage.
Frequency Priority for EutranInterNFreq.ConnFreqPriority It is recommended that this parameter be set to a non-zero value for
Connected Mode frequencies providing continuous coverage to specify their priorities.
Set this parameter to a larger value for a frequency in a lower
frequency band. Set this parameter to 0 for frequencies providing non-
continuous coverage, which means that this frequency is not selected
as the target frequency.
Inter-Freq HO trigger EutranInterNFreq.InterFreqHoEventType It is recommended that this parameter be set to EventA3 when
Event Type there is overlapping coverage, the bandwidth of the inter-
frequency target cell is the same as that of the serving cell, or the
frequency band of the inter-frequency target cell is the same as
that of the serving cell. This allows that UEs are handed over to
cells with better signal quality. In this case:
The IntraRatHoComm.A3InterFreqHoA1A2TrigQuan
parameter specifies the triggering quantity for events A1 and
A2. The value RSRP is recommended.
The InterFreqHoGroup.A3InterFreqHoA2ThdRsrp or
InterFreqHoGroup.A3InterFreqHoA2ThdRsrq parameter
specifies the threshold for event A2.
The InterFreqHoGroup.A3InterFreqHoA1ThdRsrp or
InterFreqHoGroup.A3InterFreqHoA1ThdRsrq parameter
When the interference of two cells is irrelevant, the absolute

threshold for signal quality is used as the handover criterion. It is
recommended that this parameter be set to EventA4 in such
scenarios. In this case:
The IntraRatHoComm.InterFreqHoA1A2TrigQuan parameter

specifies the triggering quantity for events A1 and A2. The
value RSRP is recommended.
The InterFreqHoGroup.InterFreqHoA2ThdRsrp or
InterFreqHoGroup.InterFreqHoA2ThdRsrq parameter
The InterFreqHoGroup.InterFreqHoA1ThdRsrp or
InterFreqHoGroup.InterFreqHoA1ThdRsrq parameter
There is no recommended scenario for event A5.
CoverageBased InterFreqHoGroup.InterFreqHoA4ThdRsrp These parameters need to be configured when

Interfreq RSRP EutranInterNFreq.InterFreqHoEventType is set to EventA4. During
threshold reconfiguration based on the live network coverage, the threshold for
coverage-based event A4 (specified by
InterFreqHoGroup.InterFreqHoA4ThdRsrp or
CoverageBased InterFreqHoGroup.InterFreqHoA4ThdRsrq
InterFreqHoGroup.InterFreqHoA4ThdRsrq) must be greater than that
Interfreq RSRQ
threshold for event A2 of all neighboring cells to reduce the risk of ping-pong
handovers.
Measurement A4 report IntraRatHoComm.InterFreqHoA4RprtQuan Set this parameter to its default value.

quantity
BlindHO A1A2 RSRP CellHoParaCfg.BlindHOA1A2ThdRsrp Set this parameter based on the actual coverage conditions to ensure
trigger threshold that service drops do not occur within corresponding areas.
BlindHO A1A2 RSRQ CellHoParaCfg.BlindHoA1A2ThdRsrq

trigger threshold
First RAT Priority CnOperatorHoCfg.FirstRatPri These parameters need to be set for inter-duplex-mode handovers
between FDD and TDD. Set these parameters based on the FDD and
Second RAT Priority CnOperatorHoCfg.SecondRatPri TDD priorities.
LTE TDD inter-freq A2 CnOperatorHoCfg.TddIfHoA2ThdRsrpOffset NOTE:

Threshold RSRP Offset
In the FDD and TDD co-sited scenarios where FDD cell policies
differ from TDD cell policies, set the following cell-level
parameters. When eNodeB- and cell-level parameters coexist,
the cell-level parameters take effect.
CellOpHoCfg.FirstRatPri
CellOpHoCfg.TddIfHoA2ThdRsrpOffset
CellOpHoCfg.FddIfHoA2ThdRsrpOffset
LTE FDD inter-freq A2 CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset

Threshold RSRP Offset
Reserved Parameter 14 eNBCnOpQciRsvdPara.RsvdPara14 In RAN sharing scenarios, different

eNBCnOpQciRsvdPara.RsvdPara14 parameter values need to be set
only when the inter-frequency event A2 RSRP thresholds need to be
configured flexibly for different operators and QCIs.

MOD CELLHOPARACFG: LocalCellId=0,CellHoAlgoSwitch=InterFreqCoverHoSwitch-1;
Certain UEs report to support inter-duplex-mode measurement but actually they do not support such measurement. When such UEs exist on the live
network, the L.RRC.ReEst.ReconfFail.Att counter indicates a large number of RRC connection reestablishments. This affects the service drop rate on the
live network. In this case, you are advised to enable LTE inter-duplex-mode measurement optimization. This function is controlled by the
InterFddTddMeasComOptSw option of the GlobalProcSwitch.UeCompatSwitch parameter.
NOTE:
After this function is enabled, UEs supporting inter-duplex-mode measurement but not supporting inter-duplex-mode handover cannot be
transferred to an inter-duplex-mode network through measurement-based redirection. Enabling this function does not affect UEs supporting
both inter-duplex-mode measurement and inter-duplex-mode handover.
//Enabling LTE inter-duplex-mode measurement optimization

MOD GLOBALPROCSWITCH: UeCompatSwitch=InterFddTddMeasComOptSw-1;
MOD CELLHOPARACFG: LocalCellId=0,CellHoAlgoSwitch=InterFreqCoverHoSwitch-0;


Using counters
Table 5-21 Counters related to inter-frequency handover
1526728935 L.HHO.InterFreq.Coverage.ExecSuccOut
1. The eNodeB receives an inter-frequency A3, A4, or A5 report.
In FDD: This feature supports quick configuration of counter collection by feature using the U2000. The measurement for the counters related to this
For details about the operations, see "Quickly Setting Performance Measurement by Feature" in iManager U2000 MBB Network Management System
Product Documentation.

Inter-Frequency Handover Out Success Rate
Table 5-22 Counters related to inter-frequency handover
1526728933 L.HHO.InterFreq.Coverage.PrepAttOut
1526728934 L.HHO.InterFreq.Coverage.ExecAttOut
1526728935 L.HHO.InterFreq.Coverage.ExecSuccOut
1526729612 L.HHO.InterFddTdd.Coverage.PrepAttOut
1526729613 L.HHO.InterFddTdd.Coverage.ExecAttOut
1526729614 L.HHO.InterFddTdd.Coverage.ExecSuccOut
5.4 Coverage-based Inter-RAT Handover to UTRAN
5.4.1 Principles
This function works only when the UtranRedirectSwitch or UtranPsHoSwitch option of the CellHoParaCfg.HoModeSwitch parameter is selected.
Figure 5-8 Process of coverage-based inter-RAT handover to UTRAN
This function involves measurement-based handover and emergency blind handover. Figure 5-9 shows the detailed procedures for the subfunctions.
For details about starting and stopping, measurement, and target cell decision for measurement-based handover, see 5.4.1.1 Initiation Decision of
Measurement-based Handover, 5.4.1.2 Measurement Configuration Delivery, and 5.4.1.3 Target Cell Decision for Measurement-based Mode,
respectively.
For details about emergency blind handover, see 5.4.1.4 Principles of Blind Handover.
Figure 5-9 Subfunctions of coverage-based inter-RAT handover to UTRAN

The eNodeB starts measurement- and coverage-based handover when receiving an inter-RAT event A2 report. If an inter-RAT event A1 report is received
during the procedure, the eNodeB stops this function.
During coverage-based inter-RAT handovers, the ReduceInvalidA1A2RptSigSwitch option of the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter
specifies the sequence of delivering event A1 and A2 measurement configurations.
If this option is selected, the eNodeB delivers event A2 measurement configurations when setting up an RRC connection for a UE, and delivers event
A1 measurement configurations after receiving an event A2 report from the UE. This reduces the reporting of unnecessary event A1, as shown in
Figure 5-10.
If this option is deselected, the eNodeB delivers both event A1 and A2 measurement configurations when setting up an RRC connection for a UE, as
shown in Figure 5-11.
Figure 5-10 uses an example to describe the procedures for triggering and stopping inter-RAT measurement. In this example:
InterRatHoComm.InterRatHoA1A2TrigQuan is set to BOTH.
InterRatHoComm.InterRatHoEventType is set to EventB2.
The TrigQuanBothMeasOptSw option of the ENodeBAlgoSwitch.HoCommOptSwitch parameter is selected.
During the triggering and stopping of inter-RAT measurement, RSRP- and RSRQ-based procedures are mutually independent. This helps reduce
unnecessary signaling exchanges. When an RSRP-triggered event A2 report is received, RSRP-based measurement is triggered irrespective of whether
there is RSRQ-based measurement. When RSRP-triggered event A1 report is received, RSRP-based measurement is stopped.
Figure 5-10 Triggering and stopping of inter-RAT measurement when event A2 measurement configurations are delivered earlier than event A1
measurement configurations
Figure 5-11 Triggering and stopping of inter-RAT measurement when event A2 and A1 measurement configurations are delivered simultaneously
If the InterRatHoComm.InterRatHoA1A2TrigQuan parameter is set to BOTH, the eNodeB checks the

InterRatHoCommGroup.A2BasedInterRatHoTrigQuan parameter value for the highest-priority service among all services running on the UE when the
eNodeB receives an inter-RAT event A2 report:
If this parameter is set to RSRP, the eNodeB delivers inter-RAT measurement configurations only when receiving an RSRP-based event A2 report.
If this parameter is set to RSRQ, the eNodeB delivers inter-RAT measurement configurations only when receiving an RSRQ-based event A2 report.
If this parameter is set to BOTH, the eNodeB delivers inter-RAT measurement configurations when receiving an RSRP- or RSRQ-based event A2
report.
5.4.1.1.1 Event A2
The eNodeB allows different RSRP threshold offsets for event A2 to be set for UTRAN and GERAN. The different settings enable UEs to be preferentially
handed over to UTRAN or GERAN during a coverage-based handover. For details, see Table 5-24. The actual event A2 threshold is the sum of an RSRP
threshold and an RSRP offset.
Table 5-23 Thresholds related to event A2

Name
InterRAT A2 RSRP InterRatHoCommGroup.InterRatHoA2ThdRsrp The InterRatHoComm.InterRatHoA1A2TrigQuan parameter specifies the

trigger threshold triggering quantity of inter-RAT events A1 and A2.
InterRAT A2 RSRQ InterRatHoCommGroup.InterRatHoA2ThdRsrq

trigger threshold
Table 5-24 Threshold offsets related to event A2 for RAT-based measurement
RAT Threshold Offset Description
UTRAN CnOperatorHoCfg.UtranA2ThdRsrpOffset + The RSRP threshold for event A2 is accompanied by an offset, while the RSRQ
CnOperatorQciPara.InterRatA2RsrpThldOffset threshold for event A2 is not.
In RAN sharing scenarios, different
CnOperatorQciPara.InterRatA2RsrpThldOffset parameter values need to be
RAT Threshold Offset Description
set only when the QCI-specific event A2 RSRP thresholds need to be

GERAN CnOperatorHoCfg.GeranA2ThdRsrpOffset +
configured for different operators.
CnOperatorQciPara.InterRatA2RsrpThldOffset
The eNodeB delivers A2 measurement configurations for RAT-based measurement as follows:
If the two offset parameters are set to different values, the eNodeB delivers two A2 measurement configurations, with one for UTRAN and the other
for GERAN. After a UE sends an event A2 report related to a RAT, the eNodeB delivers the measurement configuration for this RAT.
If the two offset parameters are set to the same value, the eNodeB delivers one A2 measurement configuration, without distinguishing between
UTRAN and GERAN. After a UE sends an event A2 report, the eNodeB delivers two measurement configurations simultaneously, with one for UTRAN
and the other for GERAN.
Note the following related to event A2 for RAT-based measurement:
If one of the threshold offsets is set to -100, the eNodeB does not trigger the corresponding inter-RAT measurement to UTRAN or GERAN.
If both threshold offsets are set to -100, the effect is the same as those set to 0. In this case, the eNodeB delivers one A2 measurement configuration,
with the threshold value being the event A2 threshold.
If the calculated RSRP threshold is lower than the protocol-specified minimum value (-140 dBm), the protocol-specified minimum value is used as
the RSRP threshold.
If the calculated RSRP threshold exceeds the protocol-specified maximum value (-43 dBm), the protocol-specified maximum value is used as the
RSRP threshold.
5.4.1.1.2 Event A1
Table 5-25 Thresholds related to event A1
Value Description
InterRatHoCommGroup.InterRatHoA1ThdRSRP The InterRatHoComm.InterRatHoA1A2TrigQuan parameter specifies the triggering

quantity of inter-RAT events A1 and A2.
InterRatHoCommGroup.InterRatHoA1ThdRSRQ
To ensure that coverage-based inter-RAT measurements can be stopped based on event A1 report, the event A1 threshold must be greater than the
event A2 threshold.

The eNodeB delivers both UTRAN and GERAN measurement configurations when receiving an inter-RAT event A2 report. If service-type-based RAT
steering is enabled, the eNodeB selects only the highest-priority RAT for measurement. For details, see 5.1.5 Principles for Selecting UTRAN or GERAN for
Inter-RAT Handovers.
The eNodeB delivers a UTRAN or GERAN measurement configuration when receiving the corresponding event A2 report.
The eNodeB contains the UTRAN frequency with the highest priority (specified by the UtranNFreq.ConnFreqPriority parameter) in the UTRAN
measurement configuration. If the priorities of frequencies are the same, the eNodeB randomly selects a target frequency.
5.4.1.3 Target Cell Decision for Measurement-based Mode

The eNodeB acquires target cells from event B1 and B2 reports. The principles are as follows:
If the UE supports both events B1 and B2, the InterRatHoComm.InterRatHoEventType parameter specifies the type of the inter-RAT handover event.
If the UE supports only event B2, the inter-RAT handover event is event B2.
5.4.1.3.1 Event B1
Table 5-26 describes thresholds related to event B1.
Table 5-26 Thresholds related to event B1 for UTRAN
Value Description
InterRatHoUtranGroup.InterRATHoUtranB1ThdRSCP The InterRatHoComm.InterRATHoUtranB1MeasQuan parameter specifies the

measurement quantity.
InterRatHoUtranGroup.InterRATHoUtranB1ThdEcN0
5.4.1.3.2 Event B2
Table 5-27 describes Thresh1 and Thresh2 for event B2.
Table 5-27 Thresholds related to event B2 for UTRAN
Value Description
InterRatHoCommGroup.UtranB2Thd1Rsrp Thresh1 for event B2. The InterRatHoComm.InterRatHoA1A2TrigQuan parameter

specifies the triggering quantity of Thresh1 for event B2.
Value Description
When Thresh1 for event B2 is smaller than or equal to the threshold for blind event
InterRatHoCommGroup.UtranB2Thd1Rsrq
A2, the eNodeB does not deliver B2 measurement configurations.
InterRatHoUtranGroup.InterRATHoUtranB1ThdRSCP Thresh2 for event B2 is the same as the event B1 threshold. The
InterRatHoComm.InterRATHoUtranB1MeasQuan parameter specifies the
InterRatHoUtranGroup.InterRATHoUtranB1ThdEcN0 measurement quantity of Thresh2 for event B2.

This function applies only to data services. The handover policy is redirection, and target frequency decision is performed during target selection.
This function takes effect only when the UtranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter is selected.
Starting and Stopping
This function is started when a UE sends an inter-frequency or inter-RAT blind event A2 report.
If the EmcInterFreqBlindHoSwitch option of the CellHoParaCfg.CellHoAlgoSwitch parameter is deselected, the eNodeB only performs a coverage-
based inter-RAT emergency blind handover. If this option is selected, the eNodeB preferentially performs a coverage-based inter-frequency emergency
blind handover. The eNodeB performs a coverage-based inter-RAT emergency blind handover only when non-serving E-UTRA frequencies are not
available for target frequency selection.
If the InterRatHoComm.InterRatHoA1A2TrigQuan parameter is set to BOTH for a coverage-based inter-RAT emergency blind handover, the eNodeB
checks the InterRatHoCommGroup.A2BasedInterRatHoTrigQuan parameter value for the highest-priority service among all services running on the UE
when the eNodeB receives an inter-frequency or inter-RAT blind event A2 report:
If this parameter is set to RSRP, the eNodeB performs follow-up target frequency selection only when receiving an RSRP-based event A2 report.
If this parameter is set to RSRQ, the eNodeB performs follow-up target frequency selection only when receiving an RSRQ-based event A2 report.
If this parameter is set to BOTH, the eNodeB performs follow-up target frequency selection when receiving an RSRP- or RSRQ-based event A2
report.
Target Frequency Selection
The eNodeB selects the frequency with the highest priority according to the following sequence:
1. The eNodeB selects the frequency of the neighboring cell with the highest priority (specified by UtranNCell.BlindHoPriority) for measurement. If the
priorities are the same, the eNodeB proceeds with the next step.
2. The eNodeB selects the frequency with the highest priority (specified by UtranNFreq.ConnFreqPriority) for measurement. If the priorities are the
same, the eNodeB randomly selects a target frequency.
5.4.2.1 Benefits
With coverage-based inter-RAT handovers, the coverage in areas with weak LTE coverage or coverage holes can be supplemented by inter-RAT
neighboring cells, decreasing the service drop rate.
5.4.2.2 Impacts
Network Impacts
None
Function Impacts
TDD priority configuration configuration is incompatible with the RAN
sharing information of the blind redirection
frequencies in coverage-based inter-RAT
handover to UTRAN.
5.4.3 Requirements
5.4.3.1 Licenses
The operator has purchased and activated the licenses for the features listed in the following table.
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-001019 PS Inter-RAT Mobility LT1SPIRHLU00 per RRC Connected User

between E-UTRAN and
UTRAN
TDD TDLOFD-001019 PS Inter-RAT Mobility LT1STIRHLU00 per RRC Connected User

between E-UTRAN and
UTRAN
5.4.3.2 Software
None
None
5.4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
5.4.3.4 Others
The eNodeB must collaborate with EPC equipment for this function to take effect. If the EPC equipment is provided by Huawei, its version must be
SAE1.2 or later. If the EPC equipment is provided by another vendor, check whether the vendor's equipment supports this function.

Table 5-28 Parameters used for activation of coverage-based inter-RAT handover to UTRAN
Handover Mode CellHoParaCfg.HoModeSwitch UtranPsHoSwitch and At least one option must be selected for inter-RAT handover to
switch UtranRedirectSwitch UTRAN.
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch RatLayerSwitch It is recommended that this option be selected when inter-RAT
handover priorities need to be considered for E-UTRAN to
UTRAN or GERAN handovers.
Handover Algo Switch ENodeBAlgoSwitch.HoAlgoSwitch SrvccRatSteeringSwitch It is recommended that this option be selected when inter-RAT
handover priorities need to be considered for voice service UEs if
UTRAN or GERAN supports SRVCC. In addition,
CSFallBackBlindHoCfg.InterRatHighestPri,
CSFallBackBlindHoCfg.InterRatSecondPri, and
CSFallBackBlindHoCfg.InterRatLowestPri need to be set.
Handover Algo Switch ENodeBAlgoSwitch.HoAlgoSwitch PsRatSteeringSwitch It is recommended that this option be selected when inter-RAT
handover priorities need to be considered for data service UEs if
UTRAN or GERAN supports the handover policy of handover or
redirection. In addition, CnOperatorHoCfg.PsInterRatHighestPri,
CnOperatorHoCfg.PsInterRatSecondPri, and
CnOperatorHoCfg.PsInterRatLowestPri need to be set.
Downlink UARFCN UtranRanShare.UtranDlArfcn N/A These parameters need to be set only when E-UTRAN to UTRAN
blind redirection needs to be triggered. Select the frequencies
meeting all the following conditions:
Mobile country code UtranRanShare.Mcc N/A
Frequencies other than those of neighboring cells
Mobile network code UtranRanShare.Mnc N/A Frequencies that have been configured in the UtranNFreq
MO
Table 5-29 Parameters used for optimization of coverage-based inter-RAT handover to UTRAN
Blind handover priority UtranNCell.BlindHoPriority It is recommended that this parameter be set to a value ranging from 1
to 32 for neighboring UTRAN cells whose coverage includes that of the
serving cell. Set this parameter to a larger value for a neighboring cell
that has wider coverage or a lower frequency.
Cell Measure Priority UtranNCell.CellMeasPriority It is recommended that a high priority be set for neighboring cells with
favorable coverage.
Frequency Priority for UtranNFreq.ConnFreqPriority It is recommended that this parameter be set to 1 to 8 for UTRAN
Connected Mode frequencies providing continuous coverage to specify their priorities.
Set this parameter to a larger value for a lower frequency. Set this
parameter to 0 for UTRAN frequencies providing non-continuous
coverage, which means that this frequency is not selected as the target
frequency.
InterRat A1A2 InterRatHoComm.InterRatHoA1A2TrigQuan Set this parameter to its recommended value. If this parameter is set to
measurement trigger BOTH and different signal quality types (RSRP or RSRQ) are used to
quantity trigger a handover for a UE with services of different QCIs, it is
recommended that the
InterRatHoCommGroup.A2BasedInterRatHoTrigQuan parameter be
set for each QCI.
InterRAT A1 RSRP trigger InterRatHoCommGroup.InterRatHoA1ThdRsrp It is recommended that the value of this parameter be greater than
threshold (usually 4 dB greater than) the sum of
InterRatHoCommGroup.InterRatHoA2ThdRsrp,
CnOperatorHoCfg.UtranA2ThdRsrpOffset, and
CnOperatorQciPara.InterRatA2RsrpThldOffset parameter values.
InterRAT A1 RSRQ trigger InterRatHoCommGroup.InterRatHoA1ThdRsrq It is recommended that the value of this parameter be greater than
threshold (usually 2 dB greater than) the
InterRatHoCommGroup.InterRatHoA2ThdRsrq parameter value.
InterRAT A2 RSRP trigger InterRatHoCommGroup.InterRatHoA2ThdRsrp Set this parameter based on the onsite conditions. Usually, set this
threshold parameter to the RSRP in the area where the UE throughput in the
serving cell and that in the neighboring cell are similar.
InterRAT A2 RSRQ trigger InterRatHoCommGroup.InterRatHoA2ThdRsrq Set this parameter based on the onsite conditions. Usually, set this
threshold parameter to the RSRQ in the area where the UE throughput in the
UTRAN A2 Threshold CnOperatorHoCfg.UtranA2ThdRsrpOffseta This parameter needs to be set when the UTRAN and GERAN handover
RSRP Offset priorities need to be differentiated.
Set this parameter based on the onsite conditions.
InterRAT A2 RSRP CnOperatorQciPara.InterRatA2RsrpThldOffset In RAN sharing scenarios, different

Threshold Offset CnOperatorQciPara.InterRatA2RsrpThldOffset parameter values need
to be set only when the QCI-specific event A2 RSRP thresholds need to
be configured for different operators.
UTRAN B2 RSRP InterRatHoCommGroup.UtranB2Thd1Rsrp It is recommended that you adjust the parameter value based on onsite
Threshold 1 conditions. Increase the parameter value if delayed inter-RAT
handovers occur.
UTRAN B2 RSRQ InterRatHoCommGroup.UtranB2Thd1Rsrq It is recommended that you adjust the parameter value based on onsite
Threshold 1 conditions. Increase the parameter value if delayed inter-RAT
handovers occur.
a: When service-type-based RAT steering is enabled, it is recommended that this parameter and the CnOperatorHoCfg.GeranA2ThdRsrpOffset
parameter be set to the same value.
//Activating coverage-based inter-RAT handover to UTRAN by setting the E-UTRAN to UTRAN handover policies
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=UtranPsHoSwitch-1&UtranRedirectSwitch-1;
//Setting inter-RAT handover policies
MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, UtranHoCfg=PS_HO-1&REDIRECTION-1;
None
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=UtranPsHoSwitch-0&UtranRedirectSwitch-0;
Fast batch activation

This function can be batch activated using the Feature Operation and Maintenance function of the CME. For detailed operations, see the following
section in the CME product documentation or online help: CME Management > CME Guidelines > Enhanced Feature Management > Feature
Operation and Maintenance.
Single/batch configuration
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME. For detailed operations, see CME-based Feature
Configuration.

Using counters
Observe the values of the counters listed in Table 5-30. If either of the counters has a non-zero value, this function has taken effect.
Table 5-30 Counters related to coverage-based inter-RAT handover to UTRAN
1526729486 L.IRATHO.E2W.Coverage.ExecAttOut
1526729491 L.RRCRedirection.E2W.Coverage
1. The eNodeB receives a UTRAN B1 or B2 report.
2. The eNodeB delivers an RRC_MOBIL_FROM_EUTRA_CMD message.

Inter-RAT Handover Out Success Rate (LTE to WCDMA)
Service Drop Rate
1526729485 L.IRATHO.E2W.Coverage.PrepAttOut
1526729487 L.IRATHO.E2W.Coverage.ExecSuccOut
5.5 Coverage-based Inter-RAT Handover to GERAN
5.5.1 Principles
This function is available when the GeranPsHoSwitch option of the eNodeB-level parameter ENodeBAlgoSwitch.HoModeSwitch or the
GeranRedirectSwitch option of the cell-level parameter CellHoParaCfg.HoModeSwitch is selected.
This function is similar to coverage-based inter-RAT handover to UTRAN. For details, see 5.4 Coverage-based Inter-RAT Handover to UTRAN. The
following describes the differences between the two functions.
When coverage-based E-UTRAN to GERAN measurement is enabled and the measurement-specific DRX switch (specified by
CellDrxPara.CovGsmMeasDrxCfgSwitch) is turned on, the measurement-specific DRX parameters are used for GERAN measurement during gap-assisted
measurement activation. For details about measurement-specific DRX parameters, see DRX and Signaling Control.
Table 5-32 lists the thresholds for events B1 and B2 for coverage-based inter-RAT handover to GERAN.
Table 5-32 Thresholds for events B1 and B2 for coverage-based inter-RAT handover to GERAN
Value Description
InterRatHoGeranGroup.InterRatHoGeranB1Thd The measurement quantity for GERAN event B1 is received signal strength
indicator (RSSI).
InterRatHoCommGroup.GeranB2Thd1Rsrp The InterRatHoComm.InterRatHoA1A2TrigQuan parameter specifies the

triggering quantity of Thresh1 for GERAN event B2.
InterRatHoCommGroup.GeranB2Thd1Rsrq
Blind handover takes effect only when the GeranRedirectSwitch option of the CellHoParaCfg.HoModeSwitch parameter is selected.
The eNodeB selects target frequency groups with the highest priority and delivers them to the UE according to the following sequence:
1. The eNodeB selects neighboring cells with the highest priority (specified by GeranNcell.BlindHoPriority) for redirection. In addition, the eNodeB
uses the frequency group including the frequency corresponding to the highest-priority cell as the target frequency group. If the priorities are the
same, the eNodeB randomly selects a blind neighboring GERAN cell. If such a cell is unavailable, the eNodeB proceeds with the next step.
2. The eNodeB selects the GERAN frequency group with the highest priority as the target frequency group based on the setting of
GeranNfreqGroup.ConnFreqPriority. If the priorities are the same, the eNodeB randomly selects a target frequency group.
5.5.2.1 Benefits
With coverage-based inter-RAT handovers, the coverage in areas with weak LTE coverage or coverage holes can be supplemented by inter-RAT
neighboring cells, decreasing the service drop rate.
5.5.2.2 Impacts
Network Impacts
None
Function Impacts
TDD priority configuration configuration is incompatible with the RAN
sharing information of the blind redirection
frequencies in coverage-based inter-RAT
handover to GERAN.
5.5.3 Requirements
5.5.3.1 Licenses
FDD LOFD-001020 PS Inter-RAT Mobility LT1SPIRHLG00 per RRC Connected User

between E-UTRAN and
GERAN
TDD TDLOFD-001020 PS Inter-RAT Mobility LT1STIRHLG00 per RRC Connected User

between E-UTRAN and
GERAN
5.5.3.2 Software
None
None
5.5.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
5.5.3.4 Others
UEs support inter-RAT handover to GERAN. That is, the S1 interface message UECapabilityInfoIndication includes the "interRAT-PS-HO-ToGERAN" IE with
the value True.
The eNodeB must collaborate with EPC equipment for this function to take effect. If the EPC equipment is provided by Huawei, its version must be PS11.0
or later. If the EPC equipment is provided by another vendor, check whether the vendor's equipment supports this function.

Table 5-33 Parameters used for activation of coverage-based inter-RAT handover to GERAN
Handover Mode switch CellHoParaCfg.HoModeSwitch GeranRedirectSwitch Select this option.
Handover Mode switch ENodeBAlgoSwitch.HoModeSwitch GeranPsHoSwitch, Select the options depending on network support capabilities.
GeranNaccSwitch, and
GeranCcoSwitch
BCCH group ID GeranRanShare.BcchGroupId N/A These parameters need to be configured if inter-RAT blind
redirection to GERAN is triggered when there are no
neighboring cells.
Mobile country code GeranRanShare.Mcc N/A Select the frequencies meeting all the following conditions:
Frequency groups other than those of neighboring cells

Mobile network code GeranRanShare.Mnc N/A
Frequency groups that have been configured in the
GeranNfreqGroup MO
Table 5-34 Parameters used for optimization of coverage-based inter-RAT handover to GERAN
InterRat A1A2 InterRatHoComm.InterRatHoA1A2TrigQuan The default value is recommended. If this parameter is set to BOTH
measurement trigger and different signal quality types (RSRP or RSRQ) are used to trigger a
quantity handover for a UE with services of different QCIs, it is recommended
that the InterRatHoCommGroup.A2BasedInterRatHoTrigQuan
parameter be set for each QCI.
InterRAT A1 RSRP trigger InterRatHoCommGroup.InterRatHoA1ThdRsrp It is recommended that the value of this parameter be greater than
threshold (usually 4 dB greater than) the sum of
InterRatHoCommGroup.InterRatHoA2ThdRsrp,
CnOperatorHoCfg.GeranA2ThdRsrpOffset, and
CnOperatorQciPara.InterRatA2RsrpThldOffset parameter values.
InterRAT A1 RSRQ trigger InterRatHoCommGroup.InterRatHoA1ThdRsrq It is recommended that the value of this parameter be greater than
threshold (usually 2 dB greater than) the
InterRatHoCommGroup.InterRatHoA2ThdRsrq parameter value.
InterRAT A2 RSRP trigger InterRatHoCommGroup.InterRatHoA2ThdRsrp Set this parameter based on the onsite conditions. Usually, set this
threshold parameter to the RSRP in the area where the UE throughput in the
InterRAT A2 RSRQ trigger InterRatHoCommGroup.InterRatHoA2ThdRsrq Set this parameter based on the onsite conditions. Usually, set this
threshold parameter to the RSRQ in the area where the UE throughput in the
GERAN A2 Threshold CnOperatorHoCfg.GeranA2ThdRsrpOffseta This parameter needs to be set when the UTRAN and GERAN handover
RSRP Offset priorities need to be differentiated. Set this parameter based on the
onsite conditions.
InterRAT A2 RSRP CnOperatorQciPara.InterRatA2RsrpThldOffset In RAN sharing scenarios, different

Threshold Offset CnOperatorQciPara.InterRatA2RsrpThldOffset parameter values need
to be set only when the QCI-specific event A2 RSRP thresholds need to
be configured for different operators.
Inter RAT HO Trigger InterRatHoComm.InterRatHoEventType The default value is recommended.

Event Type
GERAN B2 RSRP InterRatHoCommGroup.GeranB2Thd1Rsrp It is recommended that the parameter value be adjusted based on
Threshold 1 onsite conditions.
GERAN B2 RSRQ InterRatHoCommGroup.GeranB2Thd1Rsrq It is recommended that the parameter value be adjusted based on
Threshold 1 onsite conditions.
CoverageBased GERAN InterRatHoGeranGroup.InterRatHoGeranB1Thd It is recommended that the parameter value be adjusted based on
trigger threshold onsite conditions.
a: When service-type-based RAT steering is enabled, it is recommended that this parameter and the CnOperatorHoCfg.UtranA2ThdRsrpOffset
parameter be set to the same value.
//Activating coverage-based inter-RAT handover to GERAN by setting the E-UTRAN to GERAN handover policy
//Enabling inter-RAT handover to GERAN with the handover policy being redirection
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=GeranRedirectSwitch-1;
//Enabling inter-RAT handover to GERAN with the handover policy being handover
//Setting inter-RAT policy configurations
None
//Deactivating coverage-based inter-RAT handover to GERAN by setting the E-UTRAN to GERAN handover policy
//Disabling inter-RAT handover to GERAN with the handover policy being redirection
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=GeranRedirectSwitch-0;
//Disabling inter-RAT handover to GERAN with the handover policy being handover

Configuration.

Using counters
Table 5-35 Counters related to coverage-based inter-RAT handover to GERAN
1526729489 L.IRATHO.E2G.Coverage.ExecAttOut
1526729492 L.RRCRedirection.E2G.Coverage
1. The eNodeB receives a GERAN B1 or B2 report.

Inter-RAT Handover Out Success Rate (LTE to GSM)
Service Drop Rate
Table 5-36 Counters related to coverage-based inter-RAT handover to GERAN
1526729488 L.IRATHO.E2G.Coverage.PrepAttOut
1526729489 L.IRATHO.E2G.Coverage.ExecAttOut
1526729490 L.IRATHO.E2G.Coverage.ExecSuccOut
1526729492 L.RRCRedirection.E2G.Coverage
5.6 Coverage-based E-UTRAN to UTRAN CS/PS Steering
5.6.1 Principles
This section describes PS steering in coverage-based E-UTRAN to UTRAN CS/PS steering. For details about CS steering, see CS Fallback.
Service steering is an enhancement of coverage-based inter-RAT handover to UTRAN. In the measurement configuration delivery phase, the eNodeB
determines the frequencies to measure with the help of service steering. Figure 5-12 shows the differences between service steering and the basic
handover process.
Figure 5-12 Process of E-UTRAN to UTRAN CS/PS steering
PS steering has the following enhancements over coverage-based inter-RAT handover to UTRAN:
When the UtranFreqLayerMeasSwitch option of the CellAlgoSwitch.FreqLayerSwitch parameter is selected, the eNodeB selects the frequencies
with the highest priority for measurement-based inter-RAT handover to UTRAN as follows:
1. The eNodeB selects the frequency with the highest priority (specified by the UtranNFreq.PsPriority parameter) for measurement. If the
2. The eNodeB selects a frequency for measurement according to the UtranNFreq.ConnFreqPriority setting. If the priorities are the same, the
eNodeB randomly selects a frequency for measurement.
When the UtranFreqLayerBlindSwitch option of the CellAlgoSwitch.FreqLayerSwitch parameter is selected, the eNodeB selects a frequency with
the highest priority for emergency blind inter-RAT handover to UTRAN as follows:
1. The eNodeB preferentially selects a frequency with the highest priority (specified by UtranNFreq.PsPriority) for measurement. If the priorities
are the same, the eNodeB proceeds with the next step.
2. The eNodeB selects the frequency of the neighboring cell with the highest priority (specified by UtranNCell.BlindHoPriority) for measurement. If
the priorities are the same, the eNodeB proceeds with the next step.
3. The eNodeB selects the frequency with the highest priority (specified by UtranNFreq.ConnFreqPriority) for measurement. If the priorities are
the same, the eNodeB randomly selects a target frequency.
If emergency blind handover is triggered after inter-RAT measurement configurations for PS service steering are delivered, PS service steering for blind
redirection does not take effect.
5.6.2.1 Benefits
With coverage-based E-UTRAN to UTRAN CS/PS steering, the eNodeB selects different target frequencies for CS and PS services during inter-RAT
handover to UTRAN. This ensures service continuity and reduces the service drop rate.
5.6.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.6.3 Requirements
5.6.3.1 Licenses
FDD LOFD-001078 E-UTRAN to UTRAN CS/PS LT1SEUCSPS00 per RRC connected user
Steering
TDD TDLOFD-001078 E-UTRAN to UTRAN CS/PS LT1SEUCSPS01 per RRC connected user
Steering
5.6.3.2 Software
FDD Coverage-based inter-RAT UtranPsHoSwitch or Mobility Management in Coverage-based E-UTRAN to UTRAN

TDD handover to UTRAN UtranRedirectSwitch option of Connected Mode CS/PS service steering takes effect when
the either of the functions is enabled.
CellHoParaCfg.HoModeSwitch
parameter
FDD CS Fallback to UTRAN UtranCsfbSwitch option of the CS Fallback

TDD CellAlgoSwitch.HoAllowedSwitch
parameter
None
5.6.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
5.6.3.4 Others
None

Table 5-37 Parameters used for activation of CS/PS steering
Frequency Layer Switch CellAlgoSwitch.FreqLayerSwitch UtranFreqLayerMeasSwitch Select either or both the options based on onsite network
and deployment.
UtranFreqLayerBlindSwitch
Table 5-38 Parameters used for optimization of CS/PS steering
PS service priority UtranNFreq.PsPriority Set this parameter based on the plan of the priority for the neighboring
UTRAN frequency to carry PS services. Set this parameter to Priority_0
for a frequency that carries CS services so that this frequency is not
involved in frequency priority sorting for PS services.
CS service priority UtranNFreq.CsPriority Set this parameter based on the plan of the priority for the neighboring
UTRAN frequency to carry CS services. Set this parameter to Priority_0
for a frequency that carries PS services so that this frequency is not
involved in frequency priority sorting for CS services.
Configuring measurement-based handover for E-UTRAN to UTRAN CS/PS steering
//Enabling measurement-based handover for E-UTRAN to UTRAN CS/PS steering

MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerMeasSwitch-1;
//Setting CS or PS service priorities
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10650, CsPriority= Priority_16, PsPriority= Priority_16;
Configuring blind handover for E-UTRAN to UTRAN CS/PS steering
//Enabling blind handover for E-UTRAN to UTRAN CS/PS steering

MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerBlindSwitch-1;
//Setting CS or PS service priorities
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10650, CsPriority= Priority_16, PsPriority= Priority_16;
None
Configuring measurement-based handover for E-UTRAN to UTRAN CS/PS steering
//Disabling measurement-based handover for E-UTRAN to UTRAN CS/PS steering

MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerMeasSwitch-0;
Configuring blind handover for E-UTRAN to UTRAN CS/PS steering
//Disabling blind handover for E-UTRAN to UTRAN CS/PS steering

MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerBlindSwitch-0;


Check the activation status through signaling tracing. This function has taken effect if the following conditions are met:
1. The RRC_CONN_RECFG message sent from the eNodeB to a UE running PS services includes only the UTRAN frequency with the highest PS service
priority.
2. The eNodeB receives a UTRAN B1 or B2 report.
3. The RRC_MOBIL_FROM_EUTRA_CMD message delivered by the eNodeB includes the cell under the UTRAN frequency with the highest PS service
priority.

Service Drop Rate
1526729485 L.IRATHO.E2W.Coverage.PrepAttOut
1526729487 L.IRATHO.E2W.Coverage.ExecSuccOut
6 Service-based Handover
6.1 Overview
This function allows services with different QCIs to be carried by different frequencies. This function supports measurement-based handovers.
This function is classified by handover target into the following types:
Inter-frequency handover, including inter-duplex-mode handover between FDD and TDD
E-UTRAN to UTRAN handover
E-UTRAN to GERAN handover
Table 6-1 lists the conditions for starting and stopping the preceding functions.
Table 6-1 Conditions for starting and stopping service-based handover
Function Starting Condition Stopping Condition
Service-based inter- The UE running the highest-priority-QCI service can be Measurement for an inter-frequency or inter-RAT handover
frequency handover handed over to a non-serving E-UTRA frequency. has been performed for 3s, but no measurement report is
received.
Service-based inter- The UE running the service of a certain QCI can be handed
RAT handover to over to a UTRAN frequency.
UTRAN
Service-based inter- The UE running the service of a certain QCI can be handed
RAT handover to over to a GERAN frequency.
GERAN
6.2.1 Principles
This function is available only when both of the following options are selected:
ServiceBasedInterFreqHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
SrvBasedInterFreqHoSw option of the CellAlgoSwitch.HoAllowedSwitch parameter
Figure 6-1 Process of service-based handover
6.2.1.1 Handover Function Initiation Decision

If a service with a certain QCI, which has the highest priority, is initiated for a UE, this function is initiated when both of the following conditions are met:
The UE running the service of this QCI supports service-based handover. For example:
The configuration of CnOperatorQciPara.ServiceIfHoCfgGroupId set to 0 is used for service-based inter-frequency handovers of the UE.
ServiceIfHoCfgGroup.ServiceIfHoCfgGroupId is set to 0 and ServiceIfHoCfgGroup.InterFreqHoState is set to PERMIT_HO for service-based

inter-frequency handovers.
The serving frequency of the UE is not within the target frequency range expected to carry the service of this QCI.
The serving frequency of the UE is not included in the frequency group with ServiceIfDlEarfcnGrp.ServiceIfHoCfgGroupId being 0.

In FDD, if the ENodeBAlgoSwitch.ServiceHoMultiTargetFreqSw parameter is set to ON, services with a certain QCI can be transferred to any associated
frequencies specified in the ServiceIfDlEarfcnGrp MO. In this case, the eNodeB selects the frequencies for measurement in descending order of
frequency priority specified by ServiceIfDlEarfcnGrp.ServiceHoFreqPriority until the number of selected frequencies reaches the maximum. If the
ENodeBAlgoSwitch.ServiceHoMultiTargetFreqSw parameter is set to OFF, services with this QCI can be transferred only to the frequency with an index
(specified by ServiceIfDlEarfcnGrp.DlEarfcnIndex) of 0 in the ServiceIfDlEarfcnGrp MO. If any target frequency configured for the QCI with the highest
priority is the same as the frequency of the serving cell of a UE, a service-based inter-frequency handover is not performed for the UE.
In TDD, the eNodeB selects the frequencies for measurement in descending order of frequency priority specified by
ServiceIfDlEarfcnGrp.ServiceHoFreqPriority until the number of selected frequencies reaches the maximum.

The eNodeB acquires target cells from event A4 reports. Table 6-2 describes thresholds related to event A4. For details about other parameters, see 4.1.4
Measurement Configuration Delivery.
Table 6-2 Thresholds related to event A4 for service-based inter-frequency handover
Value Description
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRSRP + The IntraRatHoComm.InterFreqHoA4TrigQuan parameter specifies the

EutranInterNFreq.IfSrvHoThdRsrpOffset triggering quantity.
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRSRQ +
reporting quantity.
EutranInterNFreq.IfSrvHoThdRsrqOffset
After receiving a service-based event A4 report, the eNodeB considers the load status and bandwidth of cells for CA-incapable UEs when the
ServiceBasedMultiFreqHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected. The eNodeB preferentially selects high-
frequency-priority, high-bandwidth, and light-load cells as target cells for such UEs.
When the ServiceBasedMultiFreqHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected, service-based handovers will not be
triggered for CA-capable UEs.
NOTE:
Only the inter-frequency neighboring cells with the EutranInterFreqNCell.OverlapInd parameter set to YES send load information over the X2
interface. A neighboring cell is regarded as lightly loaded if either of the following conditions is met:
The number of UL-sync UEs in the neighboring cell is less than the sum of the CellMLB.InterFreqMlbUeNumThd and
CellMLB.InterFrqUeNumOffloadOffset parameter values of the serving cell.
The neighboring cell load information is unavailable.
For CA-capable UEs, the eNodeB does not preferentially select target cells. In this case, it is recommended that the CaSmartSelectionSwitch
option of the ENodeBAlgoSwitch.CaAlgoSwitch parameter be selected so that the eNodeB selects more suitable carrier combination for each
CA-capable UE. For details, see Carrier Aggregation.
Assume that a UE is handed over from frequency A to a cell on frequency B and a service-based inter-frequency handover is then triggered for the UE in
the cell on frequency B. In this situation:
In FDD, the eNodeB can select the source frequency (frequency A) as the target frequency for this UE if the ServBasedHoBackSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter is selected.
In TDD, the eNodeB can select the source frequency (frequency A) as the target frequency for this UE if the ServBasedHoBackSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter is selected and the service-based handover bearer policy (CnOperatorQciPara.ServiceHoBearerPolicy) of
the bearer that triggers the handover is set to SERVICE_HO_QCI_ALLOWED.
In TDD, when a UE that triggers service-based inter-frequency handover fails the outgoing handover and continues to camp in the source eNodeB, the
eNodeB adopts different policies depending on the bearer policy for service-based handovers. In FDD, the eNodeB always retains the bearers with the
corresponding QCI.
If CnOperatorQciPara.ServiceHoBearerPolicy is set to SERVICE_HO_QCI_NOT_ALLOWED, the eNodeB removes the bearers with this QCI.
If CnOperatorQciPara.ServiceHoBearerPolicy is set to SERVICE_HO_QCI_ALLOWED, the eNodeB does not remove the bearers with this QCI.
NOTE:
To prevent the default bearer of the UE from being removed, the CnOperatorQciPara.ServiceHoBearerPolicy parameter can be set to
SERVICE_HO_QCI_NOT_ALLOWED only for QCI 1 and QCI 2.
When the NCellSelectSwitch option of the CellMlbHo.MlbMatchOtherFeatureMode parameter is selected, an intra-eNodeB neighboring cell for which
MLB is triggered can act as a target cell. When this option is deselected, this neighboring cell cannot act as the target cell.
6.2.2.1 Benefits
This function provides a means to transfer UEs and allows flexible networking to meet the service steering requirements of operators.
6.2.2.2 Impacts
Network Impacts
None
Function Impacts
FDD PRB-usage-based The InterFreqMlbSwitch Intra-RAT Mobility Load When either of the MLB functions is
TDD connected mode load option of the Balancing enabled and the HoAdmitSwitch option of
equalization CellAlgoSwitch.MlbAlgoSwitch the CellMlbHo.MlbMatchOtherFeatureMode
parameter and the parameter is selected, handovers to a cell
CellMLB.MlbTriggerMode will not be admitted if an MLB procedure is
parameter with the value of triggered in the cell. This decreases the
PRB_ONLY handover preparation success rate.
Therefore, it is recommended that the
FDD User-number-based The InterFreqMlbSwitch Intra-RAT Mobility Load HoAdmitSwitch option of the
TDD connected mode load option of the Balancing CellMlbHo.MlbMatchOtherFeatureMode
equalization CellAlgoSwitch.MlbAlgoSwitch parameter be deselected.
parameter and the
CellMLB.MlbTriggerMode
parameter with the value of
UE_NUMBER_ONLY
6.2.3 Requirements
6.2.3.1 Licenses
None
6.2.3.2 Software
None
RAT Function Name Function Switch Reference
FDD None N/A N/A
TDD Service-request-based inter- ServiceReqInterFreqHoSwitch Mobility Management in Connected

frequency handover option of the Mode
ENodeBAlgoSwitch.HoAlgoSwitch
parameter
6.2.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
6.2.3.4 Others
None

Table 6-3 Parameters used for activation of service-based inter-frequency handover
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch ServiceBasedInterFreqHoSwitch Select this option.
Handover Allowed CellAlgoSwitch.HoAllowedSwitch SrvBasedInterFreqHoSw Select this option.

Switch
Table 6-4 Parameters used for optimization of service-based inter-frequency handover
QCI Priority For CellQciPara.QciPriorityForHo Set this parameter to the priority of the corresponding QCI.
Handover
MLB Match Other CellMlbHo.MlbMatchOtherFeatureMode When any MLB function is enabled and the HoAdmitSwitch option
Feature Mode of the CellMlbHo.MlbMatchOtherFeatureMode parameter is selected,
handovers to a cell will not be admitted if an MLB procedure is
triggered in the cell. This decreases the handover preparation
success rate. Therefore, it is recommended that the HoAdmitSwitch
option of the CellMlbHo.MlbMatchOtherFeatureMode parameter be
deselected.
Load Based Interfreq InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp The event A4 threshold for each type of inter-frequency handover
RSRP threshold must be higher than the event A2 threshold for coverage-based
inter-frequency handover to ensure that a coverage-based inter-

Load Based Interfreq InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrq
frequency measurement is not triggered immediately after a UE is
RSRQ threshold
handed over to the target frequency. This helps decrease the
probability of ping-pong handovers.
A4 Measurement IntraRatHoComm.InterFreqHoA4TrigQuan Set this parameter to its default value.

Trigger Quantity
Service HO Multiple ENodeBAlgoSwitch.ServiceHoMultiTargetFreqSw It is recommended that this switch be turned on if different E-

Target Frequency Switch UTRAN frequencies need to be considered during service-based
handovers.
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch It is recommended that the ServiceBasedMultiFreqHoSwitch

option of this parameter be selected if the load of the target cell
needs to be considered during service-based handovers.

MOD ENODEBALGOSWITCH: HoAlgoSwitch=ServiceBasedInterFreqHoSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch=SrvBasedInterFreqHoSw-1;
MOD SERVICEIFHOCFGGROUP: CnOperatorId=0, ServiceIfHoCfgGroupId=0, InterFreqHoState=PERMIT_HO;
//Configuring services and the corresponding target frequencies
MOD CNOPERATORQCIPARA: CnOperatorId=0, Qci=9, ServiceIfHoCfgGroupId=0;
ADD SERVICEIFDLEARFCNGRP: CnOperatorId=0, ServiceIfHoCfgGroupId=0, DlEarfcnIndex=0, DlEarfcn=38100;
Certain UEs report to support inter-duplex-mode measurement but actually they do not support such measurement. When such UEs exist on the live
network, the L.RRC.ReEst.ReconfFail.Att counter indicates a large number of RRC connection reestablishments. This affects the service drop rate on the
live network. In this case, you are advised to enable LTE inter-duplex-mode measurement optimization. This function is controlled by the
InterFddTddMeasComOptSw option of the GlobalProcSwitch.UeCompatSwitch parameter.
NOTE:
After this function is enabled, UEs supporting inter-duplex-mode measurement but not supporting inter-duplex-mode handover cannot be
transferred to an inter-duplex-mode network through measurement-based redirection. Enabling this function does not affect UEs supporting
both inter-duplex-mode measurement and inter-duplex-mode handover.
//Enabling LTE inter-duplex-mode measurement optimization

MOD GLOBALPROCSWITCH: UeCompatSwitch=InterFddTddMeasComOptSw-1;



Using counters
Table 6-5 Counters related to service-based inter-frequency handover
1526729481 L.HHO.InterFreq.Service.ExecSuccOut
1. The eNodeB receives an inter-frequency A4 report.

Table 6-6 Counters related to service-based inter-frequency handover
1526729479 L.HHO.InterFreq.Service.PrepAttOut
1526729480 L.HHO.InterFreq.Service.ExecAttOut
1526730002 L.HHO.InterFddTdd.Service.PrepAttOut
1526730003 L.HHO.InterFddTdd.Service.ExecAttOut
1526730004 L.HHO.InterFddTdd.Service.ExecSuccOut
1526737785 L.HHO.InterFddTdd.Service.Meas.Timeout
1526737872 L.HHO.InterFddTdd.Service.AttFail.NoNRT
6.3 Service-based Inter-RAT Handover to UTRAN
6.3.1 Principles
The UtranServiceHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.
Figure 6-2 Process of service-based handover

With this function, the eNodeB determines whether to hand over a UE to an inter-RAT network according to the handover policies for QCIs of UE
services. This function is enabled when both of the following conditions are met:
The value of the CnOperatorQciPara.ServiceIrHoCfgGroupId parameter is set to 0 for services with different QCIs.
The value of the ServiceIrHoCfgGroup.ServiceIrHoCfgGroupId parameter is set to 0 and the value of the ServiceIrHoCfgGroup.InterRatHoState
parameter is set to MUST_HO or PERMIT_HO for services with different QCIs. In addition, among all services with different QCIs set up for a UE, the
value of the ServiceIrHoCfgGroup.InterRatHoState parameter for at least one service is MUST_HO, and the parameter value for all the other services
is PERMIT_HO.
NOTE:
Service-based inter-RAT handovers for QCI 1 services is not recommended. This is because VoLTE services may fail on live networks due to
single radio voice call continuity before ringing (bSRVCC). Service-based inter-RAT handovers for QCI 1 services will increase the bSRVCC
probability. The CellHoParaCfg.SrvccMrDelayTimer parameter is mainly used to solve the coverage-based bSRVCC problem.

The eNodeB acquires target cells from event B1 reports. Table 6-7 describes thresholds related to event B1.
Table 6-7 Thresholds related to event B1 for service-based inter-RAT handover to UTRAN
Value Description
InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRSCP The InterRatHoComm.InterRATHoUtranB1MeasQuan parameter specifies

the measurement quantity of event B1.
InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdECN0
6.3.2.1 Benefits
6.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
6.3.3 Requirements
6.3.3.1 Licenses
FDD LOFD-001043 Service based Inter-RAT LT1S0SBIRU00 per RRC connected user
handover to UTRAN
TDD TDLOFD-001043 Service based Inter-RAT LT1STSBIRU00 per RRC connected user
handover to UTRAN
6.3.3.2 Software
FDD Coverage-based inter-RAT UtranPsHoSwitch or Mobility Management in Service-based inter-RAT handover to

TDD handover to UTRAN UtranRedirectSwitch option Connected Mode UTRAN takes effect only when either of the
of the preceding functions is enabled.
parameter
FDD SRVCC to UTRAN UtranSrvccSwitch option of CS Fallback

TDD the
parameter
FDD None N/A N/A
TDD Service-request-based ServiceReqInterFreqHoSwitch Mobility Management in Connected Mode

inter-frequency handover option of the
parameter
6.3.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
6.3.3.4 Others
The eNodeB must collaborate with EPC equipment for this function to take effect. If the EPC equipment is provided by Huawei, its version must be
SAE1.2 or later. If the EPC equipment is provided by another vendor, check whether the vendor's equipment supports this function.

Table 6-8 Parameters used for activation of service-based inter-RAT handover to UTRAN
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch Select the UtranServiceHoSwitch option.
Table 6-9 Parameters used for optimization of service-based inter-RAT handover to UTRAN
Load Service Based InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdEcn0 The default value is recommended.

UTRANB1 ECN0
threshold
Load Service Based InterRatHoUtranGroup.LdSvBasedHoUtranB1ThdRscp The default value is recommended.

UTRAN EventB1 RSCP
trigger threshold

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranServiceHoSwitch-1;
//Setting the handover parameters for services with a specified QCI
MOD SERVICEIRHOCFGGROUP: CnOperatorId=0, ServiceIrHoCfgGroupId=0, InterRatHoState=MUST_HO;
MOD CNOPERATORQCIPARA: CnOperatorId=0, Qci=1, ServiceIrHoCfgGroupId=0;
None
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranServiceHoSwitch-0;
Configuration.

Using counters
Table 6-10 Counters related to service-based inter-RAT handover to UTRAN
1526730019 L.IRATHO.E2W.Service.ExecAttOut
1526730024 L.RRCRedirection.E2W.Service
1. The eNodeB receives a UTRAN B1 report.

Service Drop Rate
Table 6-11 Counters related to service-based inter-RAT handover to UTRAN
1526730018 L.IRATHO.E2W.Service.PrepAttOut
1526730019 L.IRATHO.E2W.Service.ExecAttOut
1526730020 L.IRATHO.E2W.Service.ExecSuccOut
1526730024 L.RRCRedirection.E2W.Service
6.4 Service-based Inter-RAT Handover to GERAN
6.4.1 Principles
The GeranServiceHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.
The principles for this function are similar to those for service-based inter-RAT handover to UTRAN. The differences lie in the parameters listed in Table
6-12.
Table 6-12 Thresholds related to event B1 for service-based inter-RAT handover to GERAN
Value Description
InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd The reference signal quality type is RSSI.
6.4.2.1 Benefits
6.4.2.2 Impacts
Network Impacts
None
Function Impacts
None
6.4.3 Requirements
6.4.3.1 Licenses
FDD LOFD-001046 Service based Inter-RAT LT1S0SBIRG00 per RRC connected user
handover to GERAN
TDD TDLOFD-001046 Service based Inter-RAT LT1STSBIRG00 per RRC connected user
handover to GERAN
6.4.3.2 Software
FDD Coverage-based inter-RAT GeranPsHoSwitch option of the Mobility Management in Service-based inter-RAT handover to
TDD handover to GERAN ENodeBAlgoSwitch.HoModeSwitch Connected Mode GERAN takes effect only when either of
parameter or GeranRedirectSwitch the preceding functions is enabled.
option of the
parameter
FDD SRVCC to GERAN GeranSrvccSwitch option of the SRVCC

TDD CellHoParaCfg.HoModeSwitch
parameter
FDD None N/A N/A
TDD Service-request-based ServiceReqInterFreqHoSwitch Mobility Management in Connected Mode

inter-frequency handover option of the
parameter
6.4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
6.4.3.4 Others
UEs support inter-RAT handover to GERAN. That is, the S1 interface message UECapabilityInfoIndication includes the "interRAT-PS-HO-ToGERAN" IE with
the value True.
The eNodeB must collaborate with EPC equipment for this function to take effect. If the EPC equipment is provided by Huawei, its version must be PS11.0
or later. If the EPC equipment is provided by another vendor, check whether the vendor's equipment supports this function.

Table 6-13 Parameters used for activation of service-based inter-RAT handover to GERAN
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch GeranServiceHoSwitch Select this option.
Table 6-14 Parameters used for optimization of service-based inter-RAT handover to GERAN
Load Service Based InterRatHoGeranGroup.LdSvBasedHoGeranB1Thd Set this parameter to its default value.
Geran EventB1 trigger
threshold

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranServiceHoSwitch-1;
//Setting the handover parameters for services with a specified QCI
MOD SERVICEIRHOCFGGROUP: CnOperatorId=0, ServiceIrHoCfgGroupId=0, InterRatHoState=MUST_HO;
MOD CNOPERATORQCIPARA: CnOperatorId=0, Qci=1, ServiceIrHoCfgGroupId=0;
None
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranServiceHoSwitch-0;

Configuration.

Using counters
Table 6-15 Counters related to service-based inter-RAT handover to GERAN
1526730022 L.IRATHO.E2G.Service.ExecAttOut
1526730025 L.RRCRedirection.E2G.Service
1. The eNodeB receives a GERAN B1 report.

Service Drop Rate
Table 6-16 Counters related to service-based inter-RAT handover to GERAN
1526730021 L.IRATHO.E2G.Service.PrepAttOut
1526730022 L.IRATHO.E2G.Service.ExecAttOut
1526730023 L.IRATHO.E2G.Service.ExecSuccOut
1526730025 L.RRCRedirection.E2G.Service
7 Distance-based Handover
7.1 Overview
The CellAlgoSwitch.DistBasedHoSwitch parameter specifies whether to enable distance-based handover. This function supports only measurement-
based handover.
As shown in Figure 7-1, band F1 is used to cover urban areas and band F2 is used to cover suburban areas. If there are few obstacles in the overlapping
area between urban and suburban areas, the RF signals from an F1 cell may be able to travel a long distance (typically three times the distance between
sites), causing overshoot coverage to an F2 cell. The triangle area in the UE moving direction indicates overshoot coverage. In this figure, cell 4 is not a
neighboring cell of cell 1.
As a result of overshoot coverage effect of cell 1, a UE cannot trigger a coverage-based inter-frequency handover in cell 2 and cell 3. When the UE
reaches cell 4 and moves out of the overshoot coverage area, service drops will occur due to lack of neighbor relationships.
When distance-based handover is enabled, the eNodeB monitors its distance to the UE so that the UE can be handed over to cell 2 or cell 3 in time to
avoid service drops.
NOTE:
The eNodeB acquires its distance to the UE using the uplink timing advance (TA) mechanism. The precision in the estimated distance is about 100
to 150 meters.
Figure 7-1 Distance-based inter-frequency handover
Table 7-1 describes the conditions for triggering and stopping each distance-based handover function. If all distance-based handover functions are
enabled and triggering conditions are met, the eNodeB delivers inter-frequency, UTRAN, and GERAN measurement. Then, the eNodeB determines
whether to execute an inter-frequency handover or inter-RAT handover to UTRAN or GERAN after determining target cells or frequencies.
Table 7-1 Conditions for triggering and stopping distance-based handover
Function Name Triggering Condition Stopping Condition
Distance-based inter- Distance between the UE and eNodeB exceeds the The distance between the UE and the eNodeB falls below the specified
frequency handover specified threshold. threshold.
Distance-based inter-
RAT handover to
UTRAN
Distance-based inter-
RAT handover to
GERAN
7.2.1 Principles
This function takes effect when the DistBasedHO.DistBasedMeasObjType parameter is set to EUTRAN.
Figure 7-2 Process of distance-based handover

Distance-based inter-frequency handover is triggered by the eNodeB based on the distance between the eNodeB and the UE.
The eNodeB keeps monitoring the distance to all UEs. Table 7-2 lists the triggering and stopping conditions.
Table 7-2 Conditions for triggering and stopping distance-based handover
Distance-based inter- The measured distance to a UE exceeds the The measured distance to a UE becomes less than or equal to the
frequency handover threshold specified by the threshold specified by the DistBasedHO.DistBasedHOThd parameter
DistBasedHO.DistBasedHOThd parameter for 10 for 10 seconds.
seconds.

The eNodeB acquires target cells from event A4 reports. The thresholds related to event A4 for this function are the same as those for coverage-based
handover. For details, see Table 7-3.
Table 7-3 Thresholds related to event A4 for distance-based inter-frequency handover
Value Description
InterFreqHoGroup.InterFreqHoA4ThdRSRP The IntraRatHoComm.InterFreqHoA4TrigQuan parameter specifies the

triggering quantity.
InterFreqHoGroup.InterFreqHoA4ThdRSRQ The IntraRatHoComm.InterFreqHoA4RprtQuan parameter specifies

the reporting quantity.
7.2.2.1 Benefits
This function ensures the continuity of radio network coverage and provides uninterrupted communication services for UEs.
7.2.2.2 Impacts
Network Impacts
None
Function Impacts
None
7.2.3 Requirements
7.2.3.1 Licenses
None
7.2.3.2 Software
None
None
7.2.3.3 Hardware
Base Station Models
3900 and 5900 series base stations
Boards
No requirements
RF Modules
No requirements
7.2.3.4 Others
None

Table 7-4 Parameters used for activation of distance-based inter-frequency handover
Distance-based Handover Switch CellAlgoSwitch.DistBasedHoSwitch Turn on this switch.
Distance-based Measurement Object Type DistBasedHO.DistBasedMeasObjType Set this parameter to EUTRAN.
Table 7-5 Parameters used for optimization of distance-based inter-frequency handover
Distance-based Handover Threshold DistBasedHO.DistBasedHOThd Set this parameter to its default value.
CoverageBased Interfreq RSRP threshold InterFreqHoGroup.InterFreqHoA4ThdRsrp The event A4 threshold for each type of inter-frequency
handover must be higher than the event A2 threshold for
coverage-based inter-frequency handover to ensure that a
coverage-based inter-frequency measurement is not triggered
CoverageBased Interfreq RSRQ threshold InterFreqHoGroup.InterFreqHoA4ThdRsrq
immediately after a UE is handed over to the target frequency.
This helps decrease the probability of ping-pong handovers.
A4 Measurement Trigger Quantity IntraRatHoComm.InterFreqHoA4TrigQuan Set this parameter to its default value.

MOD CELLALGOSWITCH: LocalCellId=0, DistBasedHoSwitch=ON;
MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=EUTRAN-1;
None
MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=EUTRAN-0;


Using counters
Table 7-6 Counters related to distance-based inter-frequency handover
1526730014 L.HHO.InterFreq.Distance.ExecSuccOut

Table 7-7 Counters related to distance-based inter-frequency handover
1526730010 L.HHO.InterFreq.Distance.PrepAttOut
1526730012 L.HHO.InterFreq.Distance.ExecAttOut
1526730014 L.HHO.InterFreq.Distance.ExecSuccOut
1526730011 L.HHO.InterFddTdd.Distance.PrepAttOut
1526730013 L.HHO.InterFddTdd.Distance.ExecAttOut
1526730015 L.HHO.InterFddTdd.Distance.ExecSuccOut
7.3 Distance-based Inter-RAT Handover to UTRAN
7.3.1 Principles
This function takes effect when the DistBasedHO.DistBasedMeasObjType parameter is set to UTRAN.
The initiation determination mechanism of this function is the same as that of distance-based inter-frequency handover. The eNodeB acquires target
cells from event B1 reports. The thresholds related to event B1 for this function are the same as those for coverage-based handover. For details, see Table
7-8.
Table 7-8 Thresholds related to event B1 for distance-based inter-RAT handover to UTRAN
Value Description
InterRatHoUtranGroup.InterRATHoUtranB1ThdRSCP The InterRatHoComm.InterRATHoUtranB1MeasQuan parameter specifies

the measurement quantity.
7.3.2.1 Benefits
7.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
7.3.3 Requirements
7.3.3.1 Licenses
FDD LOFD-001072 Distance based Inter-RAT handover LT1S0DBIHU00 per RRC connected user
to UTRAN
TDD TDLOFD-001072 Distance based Inter-RAT handover LT1SUDIRAT00 per RRC connected user
to UTRAN
7.3.3.2 Software
FDD Coverage-based inter-RAT handover UtranPsHoSwitch or Mobility Management in Connected Mode

TDD to UTRAN UtranRedirectSwitch option of the
parameter
None
7.3.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
7.3.3.4 Others
None

Table 7-9 Parameters used for activation of distance-based inter-RAT handover to UTRAN
Distance-based Measurement Object Type DistBasedHO.DistBasedMeasObjType Set this parameter to UTRAN.
Table 7-10 Parameters used for optimization of distance-based inter-RAT handover to UTRAN
CoverageBased UTRAN ECN0 trigger InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0 Set this parameter to its default value.
threshold
CoverageBased UTRAN RSCP trigger InterRatHoUtranGroup.InterRatHoUtranB1ThdRscp Set this parameter to its default value.
threshold

MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=UTRAN-1;
None
MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=UTRAN-0;

Using counters
Table 7-11 Counters related to distance-based inter-RAT handover to UTRAN
1526730035 L.IRATHO.E2W.Distance.ExecAttOut
1526730040 L.RRCRedirection.E2W.Distance
1. The eNodeB receives a UTRAN B1 report.

Service Drop Rate
Table 7-12 Counters related to distance-based inter-RAT handover to UTRAN
1526730034 L.IRATHO.E2W.Distance.PrepAttOut
1526730035 L.IRATHO.E2W.Distance.ExecAttOut
1526730036 L.IRATHO.E2W.Distance.ExecSuccOut
1526730040 L.RRCRedirection.E2W.Distance
7.4 Distance-based Inter-RAT Handover to GERAN
7.4.1 Principles
This function takes effect when the DistBasedHO.DistBasedMeasObjType parameter is set to GERAN.
The initiation determination mechanism of this function is the same as that of distance-based inter-frequency handover. The eNodeB acquires target
cells from event B1 reports. The thresholds related to event B1 for this function are the same as those for coverage-based handover. For details, see Table
7-13.
Table 7-13 Thresholds related to event B1 for distance-based inter-RAT handover to GERAN
Value Description
InterRatHoGeranGroup.InterRatHoGeranB1Thd The reference signal quality type is RSSI.
7.4.2.1 Benefits
7.4.2.2 Impacts
Network Impacts
None
Function Impacts
None
7.4.3 Requirements
7.4.3.1 Licenses
FDD LOFD-001073 Distance based Inter-RAT handover LT1S0DBIHG00 per RRC connected user
to GERAN
TDD TDLOFD-001073 Distance based Inter-RAT handover LT1SGDIRAT00 per RRC connected user
to GERAN
7.4.3.2 Software
FDD Coverage-based inter-RAT handover GeranPsHoSwitch option of the Mobility Management in Connected Mode
TDD to GERAN ENodeBAlgoSwitch.HoModeSwitch
parameter or GeranRedirectSwitch
option of the
parameter
None
7.4.3.3 Hardware
Base Station Models
Boards
No requirements
RF Modules
No requirements
7.4.3.4 Others
None

Table 7-14 Parameters used for activation of distance-based inter-RAT handover to GERAN
Distance-based Measurement Object Type DistBasedHO.DistBasedMeasObjType Set this parameter to GERAN.
Table 7-15 Parameters used for optimization of distance-based inter-RAT handover to GERAN
CoverageBased GERAN trigger InterRatHoGeranGroup.InterRatHoGeranB1Thd Set this parameter to its default value.
threshold

MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=GERAN-1;
None
MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=GERAN-0;


Using counters
Table 7-16 Counters related to distance-based inter-RAT handover to GERAN
1526730038 L.IRATHO.E2G.Distance.ExecAttOut
1526730041 L.RRCRedirection.E2G.Distance
1. The eNodeB receives a GERAN B1 report.

Service Drop Rate
Table 7-17 Counters related to distance-based inter-RAT handover to GERAN
1526730037 L.IRATHO.E2G.Distance.PrepAttOut
1526730038 L.IRATHO.E2G.Distance.ExecAttOut
1526730039 L.IRATHO.E2G.Distance.ExecSuccOut
1526730041 L.RRCRedirection.E2G.Distance
8 UL-quality-based Handover
8.1 Overview
UL-quality-based handover decreases the number of service drops caused by deteriorated uplink quality. The eNodeB determines whether to execute an
inter-frequency handover or inter-RAT handover to UTRAN or GERAN after determining target cells or frequencies.
UL-quality-based handover involves measurement-based and blind handovers. Table 8-1 lists the conditions for triggering and stopping UL-quality-
based handover.
Table 8-1 Conditions for triggering and stopping UL-quality-based handover
Mode Triggering Condition Stopping Condition
Measurement-based handover Uplink quality becomes worse. Uplink quality becomes better.
Blind handover Uplink quality becomes further worse, but the None
eNodeB fails to receive any event A4 reports.
8.2 UL-quality-based Inter-frequency Handover
8.2.1 Principles
The UlQualityInterFreqHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.
Figure 8-1 Process of UL-quality-based handover
8.2.1.1 Initiation Determination of Measurement-based Handover

UL-quality-based inter-frequency handover is triggered based on uplink signal quality. This ensures timely handover and avoids service drops when the
uplink signal quality is poor.
Table 8-2 lists the conditions for starting and stopping measurement.
Table 8-2 Conditions for triggering and stopping measurement
UL-quality-based inter- The eNodeB starts inter-frequency measurement when both The eNodeB stops inter-frequency measurement when either
frequency handover the following conditions are met: of the following conditions is met:
Uplink MCS index < CellHoParaCfg.UlBadQualHoMcsThd Uplink MCS index >=

parameter value CellHoParaCfg.UlBadQualHoMcsThd parameter value
Actual IBLER of uplink data transmission – Target IBLER Actual IBLER of uplink data transmission – Target IBLER
value > CellHoParaCfg.UlBadQualHoIblerThd parameter value <= CellHoParaCfg.UlBadQualHoIblerThd
value parameter value
8.2.1.2 Target Cell Determination for Measurement-based Mode

The eNodeB acquires target cells from event A4 reports. Table 8-3 describes thresholds related to event A4.
Table 8-3 Thresholds of event A4 for UL-quality-based inter-frequency handovers
Value Description
InterFreqHoGroup.InterFreqHoA4ThdRSRP + The IntraRatHoComm.InterFreqHoA4TrigQuan parameter

InterFreqHoGroup.UlBadQualHoA4Offset specifies the triggering quantity.
The IntraRatHoComm.InterFreqHoA4RprtQuan parameter
InterFreqHoGroup.InterFreqHoA4ThdRSRQ +
specifies the reporting quantity.
InterFreqHoGroup.UlBadQualHoA4Offset
Initiation Decision
If the UL quality for the UE further deteriorates, the eNodeB considers that a service drop may occur due to the poor UL quality and performs blind
redirection for the UE when the following conditions are met:
Uplink MCS index < CellHoParaCfg.UlBadQualHoMcsThd parameter value
Actual IBLER of uplink data transmission – Target IBLER value – 10% > CellHoParaCfg.UlBadQualHoIblerThd parameter value
The eNodeB fails to receive any event A4 reports.

When CellAlgoSwitch.VolteRedirectSwitch is turned on, blind redirection can be executed for QCI-1 services during UL-quality-based inter-
frequency handovers. In this case, the cause value in the release message sent from the eNodeB to the MME is always User Inactivity.
Target Frequency Selection
The mechanism of UL-quality-based inter-frequency blind handover is the same as that of coverage-based inter-frequency emergency blind handover.
For details, see 5.3.1.4.2 Emergency Blind Handover.
8.2.2.1 Benefits
8.2.2.2 Impacts
Network Impacts
None
Function Impacts
None
8.2.3 Requirements
8.2.3.1 Licenses
None
8.2.3.2 Software
None
None
8.2.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
8.2.3.4 Others
None

Table 8-4 Parameters used for activation of UL-quality-based inter-frequency handover
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch UlQualityInterFreqHoSwitch Select this option.
Table 8-5 Parameters used for optimization of UL-quality-based inter-frequency handover
A4 Measurement Trigger IntraRatHoComm.InterFreqHoA4TrigQuan Set this parameter to its default value.

Quantity
CoverageBased Interfreq RSRP InterFreqHoGroup.InterFreqHoA4ThdRsrp The event A4 threshold for each type of inter-frequency handover
threshold must be higher than the event A2 threshold for coverage-based
inter-frequency handover to ensure that a coverage-based inter-
frequency measurement is not triggered immediately after a UE is
CoverageBased Interfreq RSRQ InterFreqHoGroup.InterFreqHoA4ThdRsrq
threshold

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UlQualityInterFreqHoSwitch-1;
None
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UlQualityInterFreqHoSwitch-0;


Using counters
Observe the value of the counter listed in Table 8-6. If it has a non-zero value, this function has taken effect.
Table 8-6 Counter related to UL-quality-based inter-frequency handover
1526729998 L.HHO.InterFreq.ULquality.ExecSuccOut

Table 8-7 Counters related to UL-quality-based inter-frequency handover
1526729994 L.HHO.InterFreq.ULquality.PrepAttOut
1526729996 L.HHO.InterFreq.ULquality.ExecAttOut
1526729998 L.HHO.InterFreq.ULquality.ExecSuccOut
1526729995 L.HHO.InterFddTdd.ULquality.PrepAttOut
1526729997 L.HHO.InterFddTdd.ULquality.ExecAttOut
1526729999 L.HHO.InterFddTdd.ULquality.ExecSuccOut
8.3 UL-quality-based Inter-RAT Handover to UTRAN or GERAN
8.3.1 Principles
The UlQualityInterRATHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function. If this option is
selected, UEs can be handed over to UTRAN or GERAN cells.
Figure 8-2 Process of UL-quality-based handover
The initiation determination mechanism of this function is the same as that of UL-quality-based inter-frequency handover.
In measurement-based handover, the eNodeB acquires target cells from event B1 reports. The thresholds related to event B1 for this function are the
same as those for coverage-based handover.
Table 8-8 lists the thresholds related to event B1 for UTRAN cells.
Table 8-9 lists the thresholds related to event B1 for GERAN cells.
Table 8-8 Thresholds related to event B1 for UL-quality-based inter-RAT handover to UTRAN
Value Description
InterRatHoUtranGroup.InterRATHoUtranB1ThdRSCP The InterRatHoComm.InterRATHoUtranB1MeasQuan parameter specifies

the measurement quantity.
Table 8-9 Thresholds related to event B1 for UL-quality-based inter-RAT handover to GERAN
Value Description
InterRatHoGeranGroup.InterRatHoGeranB1Thd The reference signal quality type is RSSI.
In UL-quality-based inter-RAT blind handover to UTRAN, the eNodeB selects the frequency with the highest priority as follows:
1. The eNodeB selects the frequency of the neighboring cell with the highest priority (specified by UtranNCell.BlindHoPriority) for measurement. If the
2. The eNodeB selects the frequency with the highest priority (specified by UtranNFreq.ConnFreqPriority) for measurement. If the priorities are the
same, the eNodeB randomly selects a target frequency.
In UL-quality-based inter-RAT blind handover to GERAN, the eNodeB selects the frequency group with the highest priority as follows:
1. The eNodeB selects the frequency of the neighboring cell with the highest priority (specified by GeranNcell.BlindHoPriority) for measurement. If the
2. The eNodeB selects the frequency group with the highest priority (specified by GeranNfreqGroup.ConnFreqPriority) for measurement. If the
priorities are the same, the eNodeB randomly selects a target frequency group.
8.3.2.1 Benefits
8.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
8.3.3 Requirements
8.3.3.1 Licenses
The operator has purchased and activated the licenses for the features listed in the following table to use UL-quality-based inter-RAT handover to
UTRAN.
FDD LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and LT1SPIRHLU00 per RRC Connected User
UTRAN
TDD TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and LT1STIRHLU00 per RRC Connected User
UTRAN
The operator has purchased and activated the licenses for the features listed in the following table to use UL-quality-based inter-RAT handover to
GERAN.
FDD LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and LT1SPIRHLG00 per RRC Connected User
GERAN
TDD TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and LT1STIRHLG00 per RRC Connected User
GERAN
https://support.huawei.com/hedex/pages/DOC110051112531189937/10/DOC110051112531189937/10/resources/hert/ref-ne/pdf/Mobility_Connec… 100/120
8.3.3.2 Software
FDD Coverage-based inter-RAT UtranPsHoSwitch or Mobility Management in Connected UL-quality-based inter-RAT

TDD handover to UTRAN UtranRedirectSwitch option of the Mode handover to UTRAN/GERAN
CellHoParaCfg.HoModeSwitch takes effect only when either
parameter of the preceding functions is
enabled.
FDD Coverage-based inter-RAT GeranPsHoSwitch option of the Mobility Management in Connected
TDD handover to GERAN ENodeBAlgoSwitch.HoModeSwitch Mode
parameter or GeranRedirectSwitch
option of the
parameter
None
8.3.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
8.3.3.4 Others
None

Table 8-10 Parameters used for activation of UL-quality-based inter-RAT handover to UTRAN or GERAN
Handover Algo switch ENodeBAlgoSwitch.HoAlgoSwitch UlQualityInterRATHoSwitch Select this option.
Table 8-11 Parameters used for optimization of UL-quality-based inter-RAT handover to UTRAN or GERAN
CoverageBased UTRAN InterRatHoUtranGroup.InterRatHoUtranB1ThdEcn0 Set this parameter to its default value.

ECN0 trigger threshold
CoverageBased UTRAN InterRatHoUtranGroup.InterRatHoUtranB1ThdRscp Set this parameter to its default value.

RSCP trigger threshold
CoverageBased GERAN InterRatHoGeranGroup.InterRatHoGeranB1Thd Set this parameter to its default value.

trigger threshold

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UlQualityInterRATHoSwitch-1;
None
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UlQualityInterRATHoSwitch-0;


Using counters
Observe the values of the counters listed in Table 8-12. If either of the counters has a non-zero value, UL-quality-based inter-RAT handover to
UTRAN has taken effect.
Table 8-12 Counters related to UL-quality-based inter-RAT handover to UTRAN
1526730027 L.IRATHO.E2W.ULquality.ExecAttOut
1526730032 L.RRCRedirection.E2W.Ulquality
Observe the values of the counters listed in Table 8-13. If either of the counters has a non-zero value, UL-quality-based inter-RAT handover to
GERAN has taken effect.
Table 8-13 Counters related to UL-quality-based inter-RAT handover to GERAN
1526730030 L.IRATHO.E2G.ULquality.ExecAttOut
1526730033 L.RRCRedirection.E2G.Ulquality
1. The eNodeB receives a UTRAN or GERAN B1 report.

Inter-RAT Handover Out Success Rate (LTE to WCDMA) and Inter-RAT Handover Out Success Rate (LTE to GSM)
Service Drop Rate
Table 8-14 Counters related to UL-quality-based inter-RAT handover to UTRAN or GERAN
1526730026 L.IRATHO.E2W.ULquality.PrepAttOut
1526730027 L.IRATHO.E2W.ULquality.ExecAttOut
1526730028 L.IRATHO.E2W.ULquality.ExecSuccOut
1526730032 L.RRCRedirection.E2W.Ulquality
1526730029 L.IRATHO.E2G.ULquality.PrepAttOut
1526730030 L.IRATHO.E2G.ULquality.ExecAttOut
1526730031 L.IRATHO.E2G.ULquality.ExecSuccOut
1526730033 L.RRCRedirection.E2G.Ulquality
9 Service-request-based Inter-frequency Handover
9.1 Principles
The ServiceReqInterFreqHoSwitch option of the CellAlgoSwitch.HoAllowedSwitch parameter specifies whether to enable this function. This function
supports only measurement-based handover.
NOTE:
For cells on TDD frequencies, this function can also be enabled or disabled by the ServiceReqInterFreqHoSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter. This means that either the cell- or eNodeB-level parameter can control this feature. This option will
not be used in later versions and therefore is not recommended.
For cells on FDD frequencies, this function is not controlled by the eNodeB-level parameter.
Figure 9-1 Process of service-request-based handover

With this function, the eNodeB determines the QCI priority of a service after receiving a setup or modification request of a UE running the service. If the
QCI priority is the highest among configured QCIs, the eNodeB determines whether to hand over the UE to another cell. This function is initiated when
both of the following conditions are met:
The configuration of CnOperatorQciPara.ServiceIfHoCfgGroupId set to 0 is used for service-request-based inter-frequency handovers of the UE.
ServiceIfHoCfgGroup.ServiceIfHoCfgGroupId is set to 0 and ServiceIfHoCfgGroup.InterFreqHoState is set to PERMIT_HO for service-request-based

inter-frequency handovers.
The eNodeB hands over a UE to the target frequency. Then, the EPC triggers service bearer setup.
The VoipExProtSwitch option of the ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter specifies whether to enable service-request-based inter-
frequency handover protection when a VoLTE exception occurs.
When this option is selected, the eNodeB sets up bearers for QCI-1 services if the ServiceIfHoCfgGroup.InterFreqHoState parameter value is
PERMIT_HO in the UE initial context. Then, the eNodeB initiates inter-frequency measurement after the UE accesses the network.

For UEs on TDD frequencies, services in a service group can be transferred to any E-UTRAN frequencies specified in the ServiceIfDlEarfcnGrp MO for a
certain QCI.
For UEs on FDD frequencies, if the ENodeBAlgoSwitch.ServiceHoMultiTargetFreqSw parameter is set to ON, services in a service group can be
transferred to different E-UTRAN frequencies specified in the ServiceIfDlEarfcnGrp MO for the certain QCI. When this parameter is set to OFF, services in
a service group can be transferred only to the frequency with an index (specified by ServiceIfDlEarfcnGrp.DlEarfcnIndex) of 0 for the certain QCI.
Frequency priorities are determined based on the setting of the FixedMeasObjIDSwitch option of the CellAlgoSwitch.MultiFreqPriControlSwitch
parameter.
If this option is deselected, the eNodeB selects the frequencies for measurement in descending order of frequency priority specified by
ServiceIfDlEarfcnGrp.ServiceHoFreqPriority.
If this option is selected, the eNodeB selects the frequencies for measurement in descending order of frequency priority specified by
EutranInterNFreq.MeasFreqPriority.
The duration of gap-assisted inter-frequency measurements triggered for service-request-based inter-frequency handovers must be restricted. This
prevents persistent measurements performed due to failures to receive measurement reports from affecting data transmission. The duration is specified
by the ServiceIfHoCfgGroup.A4RptWaitingTimer parameter.
9.1.3 Target Cell Determination

The eNodeB acquires target cells from event A4 reports. Table 9-1 describes thresholds related to event A4.
Table 9-1 Thresholds related to event A4 for service-request-based inter-frequency handover
Value Description
InterFreqHoGroup.SrvReqHoA4ThdRsrp + The IntraRatHoComm.InterFreqHoA4TrigQuan parameter specifies the

EutranInterNFreq.IfSrvHoThdRsrpOffset triggering quantity.
InterFreqHoGroup.SrvReqHoA4ThdRsrq +
reporting quantity.
EutranInterNFreq.IfSrvHoThdRsrqOffset
Assume that a UE is handed over from frequency A to a cell on frequency B and a service-request-based inter-frequency handover is then triggered for
the UE in the cell on frequency B. In this situation:
In FDD, the eNodeB can select the source frequency (frequency A) as the target frequency for this UE if the ServBasedHoBackSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter is selected.
In TDD, the eNodeB can select the source frequency (frequency A) as the target frequency for this UE if the ServBasedHoBackSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter is selected and the service-based handover bearer policy (CnOperatorQciPara.ServiceHoBearerPolicy) of
the bearer that triggers the handover is set to SERVICE_HO_QCI_ALLOWED.
The eNodeB adopts different policies for TDD depending on the value of the CnOperatorQciPara.ServiceHoBearerPolicy parameter:
If this parameter is set to SERVICE_HO_QCI_NOT_ALLOWED:
During an incoming handover of the UE, the target eNodeB reads the parameter value, responds to the source eNodeB with a handover
preparation failure, and rejects the handover request of the UE.
If the handover of the UE fails and the UE continues to camp on the source eNodeB, the eNodeB removes the bearers with this QCI.
NOTE:
To prevent the default bearer of the UE from being removed, the CnOperatorQciPara.ServiceHoBearerPolicy parameter can be set to
SERVICE_HO_QCI_NOT_ALLOWED only for QCI 1 and QCI 2.
If this parameter is set to SERVICE_HO_QCI_ALLOWED:
During an incoming handover of the UE, the target eNodeB allows the handover.
If the handover of the UE fails and the UE continues to camp on the source eNodeB, the eNodeB does not remove the bearers with this QCI.
The eNodeB always adopts the following policies for FDD:
During an incoming handover of the UE, the target eNodeB allows the handover.
If the handover of the UE fails and the UE continues to camp on the source eNodeB, the eNodeB does not remove the bearers with this QCI.
In TDD, when the NCellSelectSwitch option of the CellMlbHo.MlbMatchOtherFeatureMode parameter is selected, an intra-eNodeB neighboring cell for
which MLB is triggered can act as a target cell. When this option is deselected, this neighboring cell cannot act as the target cell.
9.2.1 Benefits
9.2.2 Impacts
Network Impacts
None
Function Impacts
FDD PRB-usage-based The InterFreqMlbSwitch Intra-RAT Mobility Load When either of the MLB functions is
TDD connected mode load option of the Balancing enabled and the HoAdmitSwitch option of
equalization CellAlgoSwitch.MlbAlgoSwitch the CellMlbHo.MlbMatchOtherFeatureMode
parameter and the parameter is selected, handovers to a cell
CellMLB.MlbTriggerMode will not be admitted if an MLB procedure is
parameter with the value of triggered in the cell. This decreases the
PRB_ONLY handover preparation success rate.
Therefore, it is recommended that the
FDD User-number-based The InterFreqMlbSwitch Intra-RAT Mobility Load HoAdmitSwitch option of the
TDD connected mode load option of the Balancing CellMlbHo.MlbMatchOtherFeatureMode
equalization CellAlgoSwitch.MlbAlgoSwitch parameter be deselected.
parameter and the
CellMLB.MlbTriggerMode
parameter with the value of
UE_NUMBER_ONLY
9.3 Requirements
9.3.1 Licenses
The following are TDD license requirements.
TDD TDLOFD-070228 Service-Request Based Inter- LT1SSRBIFH00 per Active User

frequency Handover
There are no FDD license requirements.
9.3.2 Software
None
FDD Service-based inter-frequency ServiceBasedInterFreqHoSwitch Mobility Management in Connected

TDD handover option of the Mode
parameter and
SrvBasedInterFreqHoSw option of
the
CellAlgoSwitch.HoAllowedSwitch
parameter
FDD Service-based inter-RAT handover UtranServiceHoSwitch option of

TDD to UTRAN the
parameter
FDD Service-based inter-RAT handover GeranServiceHoSwitch option of

TDD to GERAN the
parameter
9.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
9.3.4 Others
None

Table 9-2 Parameters used for activation of service-request-based inter-frequency handover
Handover Algo switch CellAlgoSwitch.HoAllowedSwitch ServiceReqInterFreqHoSwitch Select this option.
Table 9-3 Parameters used for optimization of service-request-based inter-frequency handover
A4 Measurement Trigger IntraRatHoComm.InterFreqHoA4TrigQuan Set this parameter to its default value.

Quantity
Service-Request based InterFreqHoGroup.SrvReqHoA4ThdRsrp The event A4 threshold for each type of inter-frequency handover must
handover A4 RSRP be higher than the event A2 threshold for coverage-based inter-
threshold frequency handover to ensure that a coverage-based inter-frequency
measurement is not triggered immediately after a UE is handed over to
Service-Request based InterFreqHoGroup.SrvReqHoA4ThdRsrq the target frequency. This helps decrease the probability of ping-pong
handover A4 RSRQ handovers.
threshold
//Increasing the QCI-1 priority (QCI1-triggered handovers as an example)

MOD CELLQCIPARA: LocalCellId=0, QCI=1, QciPriorityForHo=1;
MOD CELLQCIPARA: LocalCellId=0, QCI=5, QciPriorityForHo=2;
//Disabling service-based inter-frequency handover
//Activating service-request-based inter-frequency handover
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=ServiceReqInterFreqHoSwitch-1;
None
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=ServiceReqInterFreqHoSwitch-0;


Using counters
Observe the value of the counter listed in Table 9-4. If it has a non-zero value, this function has taken effect.
Table 9-4 Counters related to service-request-based inter-frequency handover

Table 9-5 Counters related to service-request-based inter-frequency handover
1526729479 L.HHO.InterFreq.Service.PrepAttOut
1526729480 L.HHO.InterFreq.Service.ExecAttOut
1526730002 L.HHO.InterFddTdd.Service.PrepAttOut
1526730003 L.HHO.InterFddTdd.Service.ExecAttOut
1526730004 L.HHO.InterFddTdd.Service.ExecSuccOut
1526737785 L.HHO.InterFddTdd.Service.Meas.Timeout
1526737872 L.HHO.InterFddTdd.Service.AttFail.NoNRT
10 Frequency-priority-based Inter-frequency Handover
10.1 Principles
The FreqPriorIFHOSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter specifies whether to enable this function. This function involves
measurement-based and blind handovers.
This function works in the following scenarios:
Multi-band different-coverage scenarios. In these scenarios, a frequency-priority-based inter-frequency handover can be performed so that a higher
band with a larger bandwidth carries services when the network load is light. Figure 10-1 shows an example where a low band (900 MHz) with a small
bandwidth and a high band (1800 MHz) with a larger bandwidth coexist.
Figure 10-1 Frequency-priority-based inter-frequency handover in multi-band different-coverage scenarios
Multi-band same-coverage scenarios. In these scenarios, a frequency-priority-based inter-frequency handover can be performed so that the high
band preferentially carries services and the low band is spared for continuous coverage. Figure 10-2 shows an example of such scenarios, where 900
MHz is the low band and 1800 MHz is the high band.
Figure 10-2 Frequency-priority-based inter-frequency handover in multi-band same-coverage scenarios
NOTE:
For details about frequency-priority-based handovers in CA scenarios, see Carrier Aggregation.
Figure 10-3 Process of frequency-priority-based inter-frequency handover
When a UE accesses a cell (including entering RRC connected mode from idle mode, incoming handover, and incoming RRC connection reestablishment),
this function takes effect if all the following conditions are met:
The HO_USE_VOIP_FREQ_ALLOWED option of the CellQciPara.QciAlgoSwitch parameter is deselected for all QCIs of the services running on the UE
when the VoipMeasFreqPriSwitch option of the CellAlgoSwitch.MultiFreqPriControlSwitch parameter is selected.
NOTE:
During bearer setup and release, this condition can be used to determine whether to stop or re-deliver event A1/A2 measurement for
triggering frequency-priority-based inter-frequency handovers.
MLB from the serving cell has not been triggered when the MlbBasedFreqPriHoSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch
parameter is selected.
The eNodeB detects cells that meet the following conditions when the LoadTriggerFreqPriHoSwitch option of the
CellAlgoSwitch.FreqPriorityHoSwitch parameter is selected:
EutranInterFreqNCell.OverlapInd is set to YES for neighboring cells.
The load of neighboring cells can be obtained.
UE-number-based MLB from the neighboring cells has not been triggered.
There are no PCI conflicts between the neighboring cells and any other cell.
If frequency-priority-based inter-frequency handover has been enabled for an intra-eNodeB neighboring cell, the PRB usage of the candidate
neighboring cell is lower than the CellMLB.InterFreqMlbThd parameter value of this neighboring cell.
Table 10-1 lists the conditions for starting and stopping this function.
Table 10-1 Conditions for starting and stopping frequency-priority-based inter-frequency handover
A2-based Frequency- Frequency-priority-based Starting Condition Stopping Condition Application Scenario

priority-based Handover Inter-frequency Blind
Switchb Handover Switchc

Switchb Handover Switchc
Selected N/A Event A2 Event A4 measurement has Multi-band different-

been performed for 3s, but coverage
no event A4 report is sent.a
Deselected Deselected Event A1 Event A2 Measurement-based

handover in multi-band
same-coverage scenarios
Deselected Selected Event A1 N/A Blind handover in multi-

band same-coverage
scenarios
a: In multi-band different-coverage scenarios, event A1 is not used as the function stopping condition so that UEs are preferentially handed over to a
high-band cell.
b: This switch is controlled by the A2BasedFreqPriHoSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter.
c: This switch is controlled by the FreqPriorIFBlindHOSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter.
10.1.1 Initiation Determination of Measurement-based Handover

Table 10-2 lists the conditions for starting and stopping frequency-priority-based measurement-based inter-frequency handover.
Table 10-2 Conditions for starting and stopping frequency-priority-based measurement-based handover

Switcha Handover Switchb
Selected N/A Event A2 Event A4 measurement has Multi-band different-

been performed for 3s, but coverage
no event A4 report is sent.
Deselected Deselected Event A1 Event A2 Multi-band same-coverage
a: This switch is controlled by the A2BasedFreqPriHoSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter.

b: This switch is controlled by the FreqPriorIFBlindHOSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter.
The conditions for starting and stopping this function vary in different scenarios, but the thresholds related to events A1 and A2 are the same.
Table 10-3 and Table 10-4 describe thresholds related to events A1 and A2, respectively.
The settings of the ReduceInvalidA1A2RptSigSwitch option of the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter determine the sequence in
delivering A1/A2 measurement configurations in multi-band same-coverage scenarios.
If this option is selected, the eNodeB delivers A1 measurement configurations when setting up an RRC connection for a UE, and delivers A2
measurement configurations after it has received an event A1 report from the UE. This reduces the reporting of unnecessary event A2.
If the option is deselected, the eNodeB delivers both A2 and A1 measurement configurations when setting up an RRC connection for a UE.
Table 10-3 Thresholds related to event A1 for frequency-priority-based inter-frequency handover
Value Description
InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrp It is recommended that the IntraRatHoComm.FreqPriInterFreqHoA1TrigQuan parameter

be set to RSRP.
InterFreqHoGroup.FreqPriInterFreqHoA1ThdRsrq
Table 10-4 Thresholds related to event A2 for frequency-priority-based inter-frequency handover
Value Description
InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrp It is recommended that the IntraRatHoComm.FreqPriInterFreqHoA1TrigQuan parameter

be set to RSRP.
InterFreqHoGroup.FreqPriInterFreqHoA2ThdRsrq

If the initiation of this function is triggered by event A1 (usually in multi-band same-coverage scenarios) and the
IntraRatHoComm.FreqPriHoCandidateUeSelPer parameter is set to a non-zero value, an optimization is started. That is, if the eNodeB has not received
the corresponding measurement report three seconds after delivering event A4 measurement configurations, the eNodeB stops inter-frequency event A4
measurement. Then, the eNodeB delivers event A4 measurement configurations again at intervals specified by
IntraRatHoComm.FreqPriHoCandidateUeSelPer to UEs experiencing measurement failures. This allows UEs to retry handovers to high-band cells and
avoids impact on UE throughput due to long time measurement.
If a UE is performing gap-assisted measurement for a frequency-priority-based handover and the VoipMeasFreqPriSwitch option of the
CellAlgoSwitch.MultiFreqPriControlSwitch parameter is selected, the eNodeB stops frequency-priority-based inter-frequency measurement when a voice
bearer is set up for the UE.
The EutranInterNFreq.FreqPriBasedHoMeasFlag parameter specifies the measurement flag for a frequency for frequency-priority-based inter-frequency
measurement.
The frequencies with this parameter set to ENABLE can be selected as target frequencies. The eNodeB delivers these frequencies for measurement in
descending order of frequency priority specified by EutranInterNFreq.MeasPriorityForFreqPriHo. A larger value of this parameter indicates a higher
priority level.
If this parameter is set to DISABLE for all frequencies, target inter-frequency neighboring cells must have a blind-handover priority (specified by
EutranInterFreqNCell.BlindHoPriority) ranging from 17 to 32. The eNodeB delivers these frequencies for measurement in descending order of
frequency priority. A larger value of this parameter indicates a higher priority level.
10.1.3 Target Cell Determination for Measurement-based Mode

The eNodeB acquires target cells for frequency-priority-based inter-frequency handover from event A4 reports. The thresholds related to event A4 for
this function are the same as those for load-based handover. For details, see Table 10-5.
Table 10-5 Thresholds related to event A4 for frequency-priority-based measurement-based handover
Value Description
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp Frequency-priority-based inter-frequency handover is mainly applicable to same-

coverage scenarios. It is recommended that RSRP be used as the reference signal quality
because RSRP is an indication of relationship between signal quality and distance.
Therefore, it is recommended that the IntraRatHoComm.FreqPriInterFreqHoA1TrigQuan
InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrq
parameter be set to RSRP and the IntraRatHoComm.InterFreqHoA4RprtQuan parameter
be set to SAME_AS_TRIG_QUAN.
If the IntraRatHoComm.FreqPriIFHoWaitingTimer parameter is set to 0, the eNodeB selects target cells upon receiving an event A4 report.
If the IntraRatHoComm.FreqPriIFHoWaitingTimer parameter is set to a value greater than 0, the eNodeB checks whether the highest-priority frequency
is included in an event A4 report:
If it is, the eNodeB performs a handover immediately.
If it is not, the eNodeB waits for the next measurement report. After the timer specified by IntraRatHoComm.FreqPriIFHoWaitingTimer expires, the
eNodeB executes a handover based on the measurement report containing the relatively highest-priority frequency among all reports received
within the timer-defined period.
10.1.4 Principles of Blind Handover

Only multi-band same-coverage scenarios involve measurement-based and blind handovers. Frequency-priority-based inter-frequency handover can be
performed in a blind manner only when the FreqPriorIFBlindHOSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter is selected. Table
10-6 lists the conditions for starting and stopping frequency-priority-based blind handover.
Table 10-6 Conditions for starting and stopping frequency-priority-based blind handover

Switcha Handover Switchb
Deselected Selected Event A1 N/A Multi-band same-coverage
a: This switch is controlled by the A2BasedFreqPriHoSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter.

b: This switch is controlled by the FreqPriorIFBlindHOSwitch option of the CellAlgoSwitch.FreqPriorityHoSwitch parameter.
The handover policy for frequency-priority-based blind handover is handover.

Same as measurement-based handover, blind handover is initiated when the eNodeB receives an event A1 report.
In frequency-priority-based blind handover, target inter-frequency neighboring cells must have a blind-handover priority (specified by the
EutranInterFreqNCell.BlindHoPriority parameter) ranging from 17 to 32. If such neighboring cells are unavailable, the eNodeB performs measurement-
based handover.
10.2.1 Benefits
10.2.2 Impacts
Network Impacts
None
Function Impacts
None
10.3 Requirements
10.3.1 Licenses
For FDD, the operator has purchased and activated the license for event A2-based frequency-priority-based handovers (applying to multi-band different-
coverage scenarios). There are no license requirements for event A1-based frequency-priority-based handovers (applying to multi-band same-coverage
scenarios)
FDD LOFD-081227 Intra-LTE Load Balancing for Non- LT1SILBNCC00 per cell
cosited Cells
There are no TDD license requirements.
10.3.2 Software
None
None
10.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
10.3.4 Others
None

Table 10-7 Parameters used for activation of frequency-priority-based inter-frequency handover
Based on Frequency CellAlgoSwitch.FreqPriorityHoSwitch FreqPriorIFHOSwitch Select this option.

Priority HO Switch
MlbBasedFreqPriHoSwitch When the MLB function is enabled in a cell, it is
recommended that this option be selected to enable load
management to be fully controlled by MLB in heavy load
scenarios. This improves resource utilization in these
scenarios.
A2BasedFreqPriHoSwitch Deselect this option in multi-band same-coverage

scenarios and select this option in multi-band different-
coverage scenarios.
FreqPriorIFBlindHOSwitch Select this option if blind handover needs to be enabled in

multi-band same-coverage scenarios.
Table 10-8 Parameters used for optimization of frequency-priority-based inter-frequency handover
Freq-Pri-based Inter- IntraRatHoComm.FreqPriIFHoWaitingTimer For networks with rich spectrum resources, it is recommended that
Freq HO Waiting Timer this parameter be set to 3s if operators expect that high-priority
frequencies be preferentially selected.
Frequency Priority EutranInterNFreq.FreqPriBasedHoMeasFlag It is recommended that the

Based Ho Measure Flag EutranInterNFreq.FreqPriBasedHoMeasFlag parameter be set to
ENABLE to enable preferential handover to a neighboring
frequency. The frequency priority can be set in the
EutranInterNFreq.MeasPriorityForFreqPriHo parameter. A larger
Meas Priority for Freq- EutranInterNFreq.MeasPriorityForFreqPriHo value indicates a higher priority level.
Priority-based HO
It is recommended that the
EutranInterNFreq.FreqPriBasedHoMeasFlag parameter be set to
DISABLE to enable preferential handover to a neighboring cell.
In addition, it is recommended that the value range of the
Blind handover Priority EutranInterFreqNCell.BlindHoPriority
EutranInterFreqNCell.BlindHoPriority parameter be 17 to 32. A
larger value indicates a higher priority level.
MLB Match Other CellMlbHo.MlbMatchOtherFeatureMode When any MLB function is enabled and the HoAdmitSwitch option
Feature Mode of the CellMlbHo.MlbMatchOtherFeatureMode parameter is selected,
handovers to a cell will not be admitted if an MLB procedure is
triggered in the cell. This decreases the handover preparation success
rate. Therefore, it is recommended that the HoAdmitSwitch option
of the CellMlbHo.MlbMatchOtherFeatureMode parameter be
deselected.
Load Based Interfreq InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp The IntraRatHoComm.FreqPriInterFreqHoA1TrigQuan parameter

RSRP threshold determines the threshold to be used.
The event A4 threshold for each type of inter-frequency handover
must be higher than the event A2 threshold for coverage-based
Load Based Interfreq InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrq inter-frequency handover to ensure that a coverage-based inter-
RSRQ threshold frequency measurement is not triggered immediately after a UE is

MOD CELLALGOSWITCH: LOCALCELLID=0, FREQPRIORITYHOSWITCH=FreqPriorIFHOSwitch-1&FreqPriorIFBlindHOSwitch-0&MlbBasedFreqPriHoSwitch-0&A2Ba
Configuring the measurement-based handover function
//Setting the time within which the eNodeB waits for measurement reports for frequency-priority-based inter-frequency handovers
MOD INTRARATHOCOMM: FreqPriIFHoWaitingTimer = 1;
//(Optional) Enabling preferential handover to a neighboring frequency

MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, FreqPriBasedHoMeasFlag=ENABLE, MeasPriorityForFreqPriHo=1;
//(Optional) Enabling preferential handover to a neighboring cell
MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, FreqPriBasedHoMeasFlag=DISABLE;
MOD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=123, CellId=1, BlindHoPriority=17;
Configuring the blind handover function
MOD CELLALGOSWITCH: LOCALCELLID=0, FREQPRIORITYHOSWITCH=FreqPriorIFBlindHOSwitch-1;

Configuring the event A1–based handover function
MOD CELLALGOSWITCH: LocalCellId=0, FreqPriorityHoSwitch=FreqPriorIFHOSwitch-1&A2BasedFreqPriHoSwitch-0;

MOD INTERFREQHOGROUP: LocalCellId=0, InterFreqHoGroupId=0,FreqPriInterFreqHoA2ThdRsrp=-105,FreqPriInterFreqHoA1ThdRsrp=-100;
//In measurement-based mode
MOD EUTRANINTERNFREQ: LocalCellId=0,DlEarfcn=3600,FreqPriBasedHoMeasFlag=ENABLE;
MOD INTERFREQHOGROUP: LocalCellId=0, InterFreqHoGroupId=0,InterFreqLoadBasedHoA4ThdRsrp=-110;
//In blind mode
MOD CELLALGOSWITCH: LocalCellId=0, FreqPriorityHoSwitch=FreqPriorIFBlindHOSwitch-1;
MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3600, FreqPriBasedHoMeasFlag=DISABLE;
Configuring the event A2–based handover function
MOD CELLALGOSWITCH: LocalCellId=1, FreqPriorityHoSwitch=FreqPriorIFHOSwitch-1&A2BasedFreqPriHoSwitch-1;

MOD INTERFREQHOGROUP: LocalCellId=1, InterFreqHoGroupId=0, FreqPriInterFreqHoA2ThdRsrp=-110, FreqPriInterFreqHoA1ThdRsrp=-105;
//In measurement-based mode
MOD EUTRANINTERNFREQ: LOCALCELLID=1,DlEarfcn=3600, FreqPriBasedHoMeasFlag=ENABLE;
MOD INTERFREQHOGROUP: LocalCellId=1, InterFreqHoGroupId=0, InterFreqLoadBasedHoA4ThdRsrp=-120;
MOD CELLALGOSWITCH: LOCALCELLID=0, FREQPRIORITYHOSWITCH=FreqPriorIFHOSwitch-0&FreqPriorIFBlindHOSwitch-0&MlbBasedFreqPriHoSwitch-0&A2Ba


Using counters
Observe the value of the counter listed in Table 10-9. If it has non-zero values, this function has taken effect.
Table 10-9 Counters related to frequency-priority-based inter-frequency handover
1526729484 L.HHO.InterFreq.FreqPri.ExecSuccOut

Table 10-10 Counters related to frequency-priority-based inter-frequency handover
1526729482 L.HHO.InterFreq.FreqPri.PrepAttOut
1526729483 L.HHO.InterFreq.FreqPri.ExecAttOut
1526729484 L.HHO.InterFreq.FreqPri.ExecSuccOut
1526730006 L.HHO.InterFddTdd.FreqPri.PrepAttOut
1526730007 L.HHO.InterFddTdd.FreqPri.ExecAttOut
1526730008 L.HHO.InterFddTdd.FreqPri.ExecSuccOut
11 Separate Mobility Policies to UTRAN for Multi PLMN (FDD)
11.1 Principles
The UtranSepOpMobilitySwitch option of the ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter specifies whether to enable this function.
This function is an enhancement of the handover policy selection. In the target cell or target frequency decision phase, the eNodeB determines a
handover policy with the help of this function. Figure 11-1 shows the differences between the process of this function and the basic handover process.
Figure 11-1 Process of Separate Mobility Policies to UTRAN for Multi PLMN
The enhancements in this function are as follows:
Multi-PLMN mobility policy for handover: When the PsHoCapCfg option of the UtranNetworkCapCfg.NetworkCapCfg parameter is selected, the
eNodeB can obtain handover capabilities of UTRAN cells based on PLMN and RNC configurations. Based on the obtained handover capability, the
eNodeB determines whether to use handover as the handover policy. For details, see 4.1.6.2.3 Inter-RAT Handover Policy.
Multi-PLMN mobility policy for VoIP: When the VoipCapCfg option of the UtranNetworkCapCfg.NetworkCapCfg parameter is selected, the eNodeB
can obtain VoIP capabilities (whether VoIP services can be handed over) of UTRAN cells based on PLMN and RNC configurations. For details, see
SRVCC.
Multi-PLMN mobility policy for SRVCC: When the SrvccCapCfg option of the UtranNetworkCapCfg.NetworkCapCfg parameter is selected, the
eNodeB can obtain SRVCC capabilities of UTRAN cells based on PLMN and RNC configurations. Based on the obtained SRVCC capabilities, the
eNodeB determines whether to use SRVCC for E-UTRAN to UTRAN voice service handovers. For details, see SRVCC.
Multi-PLMN mobility policy for SI acquisition through CN-based RIM: When the SiByRimCapCfg option of the
UtranNetworkCapCfg.NetworkCapCfg parameter is selected, the eNodeB can obtain RIM capabilities of UTRAN cells based on PLMN and RNC
configurations. For voice services, the eNodeB determines a CSFB method for CSFB to UTRAN. For data services, the eNodeB determines a
redirection method for redirection to UTRAN. For details, see CS Fallback.
Multi-PLMN mobility policy for ultra-flash CSFB: When the UltraFlashCsfbCapCfg option of the UtranNetworkCapCfg.NetworkCapCfg parameter is
selected, the eNodeB can obtain ultra-flash CSFB capabilities of UTRAN cells based on PLMN and RNC configurations. Based on the obtained ultra-
flash CSFB capabilities, the eNodeB determines whether to use ultra-flash CSFB for E-UTRAN to UTRAN CSFB. For details, see CS Fallback.
11.2.1 Benefits
This function provides a means to transfer UEs and allows flexible networking to meet the service requirements of different operators.
11.2.2 Impacts
Network Impacts
This function enables the eNodeB to determine the handover, RIM supporting, VoIP, ultra-flash CSFB, and SRVCC capabilities of the UTRAN. This reduces
unnecessary signaling exchanges, and therefore reduces the number of handover attempts and failures.
Function Impacts
None
11.3 Requirements
11.3.1 Licenses
The operator has purchased and activated the license for the feature listed in the following table.
Feature ID Feature Name Model Sales Unit
LOFD-070216 Separate Mobility Policies to UTRAN for LT1SEUPLMN00 per cell

Multi PLMN
11.3.2 Software
Function Name Function Switch Reference Description
Coverage-based inter-RAT UtranPsHoSwitch or Mobility Management in The handover policy requires this function.
handover to UTRAN UtranRedirectSwitch option of Connected Mode
the CellHoParaCfg.HoModeSwitch
parameter
Flash CSFB to UTRAN UtranFlashCsfbSwitch option of CS Fallback RIM requires this function.
the
parameter
Ultra-flash CSFB to UTRAN UtranUltraFlashCsfbSwitch CS Fallback Ultra-flash CSFB requires this function.
option of the
parameter
SRVCC to UTRAN UtranSrvccSwitch option of the SRVCC SRVCC requires this function.
parameter
None
11.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
11.3.4 Others
None

Table 11-1 Parameters used for activation of Separate Mobility Policies to UTRAN for Multi PLMN
Multi-Operator ENodeBAlgoSwitch.MultiOpCtrlSwitch UtranSepOpMobilitySwitch Select this option.

Control Switch
Mobile country code UtranNetworkCapCfg.Mcc N/A If neighboring RNCs or the MME, SGSN, and MSC
corresponding to the RNCs have different handover, RIM,
Mobile network code UtranNetworkCapCfg.Mnc N/A
VoIP, ultra-flash CSFB, or SRVCC capabilities, set different

RNC ID UtranNetworkCapCfg.RncId N/A
UTRAN capabilities for the RNCs.
Network Capability UtranNetworkCapCfg.NetworkCapCfg N/A Set this parameter based on RNC capabilities. a
Configuration
a: The SiByRimCapCfg option of this parameter affects the CN-based RIM procedure. The eCoordinator-based RIM procedure is not affected by this
option.

//Turning on the UTRAN multi-operator control switch
MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch=UtranSepOpMobilitySwitch-1;
//Configuring UTRAN capabilities
ADD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0, NetworkCapCfg=PsHoCapCfg-1&SiByRimCapCfg-0&VoipCapCfg-0&UltraFlashCsfbCapCfg-0&S
None
MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch=UtranSepOpMobilitySwitch-0;

The activation verification procedure for handover and RIM functions for multi-PLMN mobility policy from E-UTRAN to UTRAN is as follows:
Trace Uu interface messages to check the data service processing procedure in areas where E-UTRAN and UTRAN overlap:
If the measured UTRAN cells do not support handover but support RIM, UEs are transferred to the UTRAN through fast redirection. That is, the
network side sends the UEs the RRC_CONN_REL message, containing the frequencies and system information of the UTRAN cells.
If the measured UTRAN cells do not support handover or RIM, UEs are transferred to the UTRAN through common redirection. That is, the
network side sends the UEs the RRC_CONN_REL message, containing the frequencies but without the system information of the UTRAN cells.
The activation verification procedure for ultra-flash CSFB, VoIP, and SRVCC is as follows:
Trace UE messages to check the voice service processing procedure in areas where E-UTRAN and UTRAN overlap:
If the measured UTRAN cells do not support ultra-flash CSFB, the UEs fall back to UTRAN for voice services through common CSFB or flash CSFB
procedures. For details, see CS Fallback.
If the measured UTRAN cells do not support VoIP, the UEs fall back to UTRAN for voice services through SRVCC procedures (if supported). For
details, see SRVCC.
If the measured UTRAN cells do not support SRVCC, the UEs fall back to UTRAN for voice services through VoIP procedures (if supported). For
details, see SRVCC.

None
12 Separate Mobility Policies to GERAN for Multi PLMN
12.1 Principles
The GeranSepOpMobilitySwitch option of the CellAlgoSwitch.HoAllowedSwitch parameter specifies whether to enable this function.
This function is an enhancement of the handover policy selection. In the target cell or target frequency decision phase, the eNodeB determines a
handover policy with the help of this function. Figure 12-1 shows the differences between the process of this function and the basic handover process.
Figure 12-1 Process of Separate Mobility Policies to GERAN for Multi PLMN
The enhancements in this function are as follows:
Multi-PLMN mobility policy for SI acquisition through CN-based RIM: When the SiByRimCapCfg option of the
GeranNetworkCapCfg.NetworkCapCfg parameter is selected, the eNodeB can obtain RIM capabilities of GERAN cells based on PLMN and LAC
configurations. Based on the obtained RIM capabilities, the eNodeB determines whether to use flash CSFB for E-UTRAN to GERAN CSFB or use fast
redirection for E-UTRAN to GERAN redirection. For details, see CS Fallback.
Multi-PLMN mobility policy for ultra-flash CSFB: When the UltraFlashCsfbCapCfg option of the GeranNetworkCapCfg.NetworkCapCfg parameter is
selected, the eNodeB can obtain ultra-flash CSFB capabilities of GERAN cells based on PLMN and LAC configurations. Based on the obtained ultra-
flash CSFB capabilities, the eNodeB determines whether to use ultra-flash CSFB for E-UTRAN to GERAN CSFB. For details, see CS Fallback.
Multi-PLMN mobility policy for SRVCC: When the SrvccCapCfg option of the GeranNetworkCapCfg.NetworkCapCfg parameter is selected, the
eNodeB can obtain SRVCC capabilities of GERAN cells based on PLMN and LAC configurations. Based on the obtained SRVCC capabilities, the
eNodeB determines whether to use SRVCC for E-UTRAN to GERAN voice service handovers. For details, see SRVCC.
12.2.1 Benefits
This function provides a means to transfer UEs and allows flexible networking to meet the service requirements of different operators.
12.2.2 Impacts
Network Impacts
This function enables the eNodeB to determine the RIM supporting, ultra-flash CSFB, and SRVCC capabilities of the GERAN. This reduces unnecessary
signaling exchanges, and therefore reduces the number of handover attempts and failures.
Function Impacts
None
12.3 Requirements
12.3.1 Licenses
FDD LOFD-111204 Separate Mobility Policies to GERAN LT1SSMPPLMN0 per cell

for Multi PLMN
TDD TDLOFD-131210 Separate Mobility Policies to GERAN LT4SSMPGMP00 per cell

for Multi PLMN
12.3.2 Software
FDD Flash CSFB to GERAN GeranFlashCsfbSwitch option of CS Fallback RIM requires this function.
TDD the
parameter
FDD Ultra-flash CSFB to GERAN GeranUltraFlashCsfbSwitch CS Fallback Ultra-flash CSFB requires this function.
TDD option of the
parameter
FDD SRVCC to GERAN GeranSrvccSwitch option of the SRVCC SRVCC requires this function.
TDD CellHoParaCfg.HoModeSwitch
parameter
None
12.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
12.3.4 Others
None

Table 12-1 Parameters used for activation of Separate Mobility Policies to GERAN for Multi PLMN
Handover Allowed CellAlgoSwitch.HoAllowedSwitch GeranSepOpMobilitySwitch Select this option.

Switch
Mobile country code GeranNetworkCapCfg.Mcc N/A If neighboring GERAN cells or the MME, SGSN, and MSC
corresponding to the neighboring GERAN cells have
Mobile network code GeranNetworkCapCfg.Mnc N/A different RIM, ultra-flash CSFB, or SRVCC capabilities, set
different GERAN capabilities for different GERAN LACs.
Location Area Code GeranNetworkCapCfg.Lac N/A
Network Capability GeranNetworkCapCfg.NetworkCapCfg N/A Set this parameter based on the network capabilities of
Configuration the cells under the LAC of GERAN. a
a: The SiByRimCapCfg option of this parameter affects the CN-based RIM procedure. The eCoordinator-based RIM procedure is not affected by this
option.

//Turning on the GERAN multi-operator control switch
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=GeranSepOpMobilitySwitch-1;
//Configuring GERAN capabilities
ADD GERANNETWORKCAPCFG: Mcc="460", Mnc="32", Lac=1, NetworkCapCfg=SiByRimCapCfg-1&UltraFlashCsfbCapCfg-0&SrvccCapCfg-0;
None
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=GeranSepOpMobilitySwitch-0;

The activation verification procedure for the RIM function for multi-PLMN mobility policy from E-UTRAN to GERAN is as follows:
Trace Uu interface messages to check the data service processing procedure in areas where E-UTRAN and GERAN overlap. If the measured GERAN
cells do not support RIM, UEs are transferred to the GERAN through common redirection. That is, the network side sends the RRC_CONN_REL
message to UEs, containing the frequencies but without the system information of the GERAN cells.
The activation verification procedure for the ultra-flash CSFB and SRVCC functions for multi-PLMN mobility policy from E-UTRAN to GERAN is as
follows:
Trace UE messages to check the voice service processing procedure in areas where E-UTRAN and GERAN overlap:
If the measured GERAN cells do not support ultra-flash CSFB, the UEs fall back to GERAN for voice services through common CSFB or flash CSFB
procedures. For details, see CS Fallback.
If the measured GERAN cells do not support SRVCC, voice services are not handed over to the GERAN cells. For details, see SRVCC.

None
13 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
14 Reference Documents
1. 3GPP TS 23.203, "Policy and charging control architecture"
2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.104, "Base Station (BS) radio transmission and reception"
4. 3GPP TS 36.133,"Requirements for support of radio resource management"
5. 3GPP TS 36.300, "E-UTRAN Overall description"
6. 3GPP TS 36.331, "RRC Protocol Specification"
7. 3GPP TS 36.413, "S1 Application Protocol"
8. 3GPP TS 36.423, "X2 Application Protocol"
9. ANR Management
10. LTE-CDMA2000 CS Service Interworking (FDD)
11. LTE-CDMA2000 CS Service Interworking (TDD)
12. LTE-CDMA2000 PS Service Interworking
13. CS Fallback
14. eMBMS
15. MRO
16. SRVCC
17. UL Unified Video Steering
18. VoLTE
19. High Speed Mobility
20. Connection Management
21. Flexible User Steering
22. Intra-RAT Mobility Load Balancing
23. Inter-RAT Mobility Load Balancing
24. Carrier Aggregation
25. Massive MIMO (TDD)
26. RAN Sharing
27. DRX and Signaling Control
28. RIM
29. iManager U2000 MBB Network Management System Product Documentation
30. S1-C Aggregation
Average rating: 0 Points 0 ratings Average problem solving rate: 0%
Your Feedback Is Appreciated
*Please rate this document: very poor excellent
Did you find what you were looking for? Yes No Just Browsing
Feedback:
Attachments (Max 4 pictures)
Huawei may contact you to help you resolve the problem as soon as possible. Please enter your contact information:
Name: OSCAR GIL OSCAR GIL *Email: gil.o****@huawei.com Tel: +58****350

Modify (http://w3.huawei.com/account/usermng.do?c_it_id=null) / Refresh Contact Information
Submit

Mobility Management in Connected Mode Feature Parameter Description PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Mobility Management in Connected Mode Feature Parameter Description PDF

Caricato da

Copyright:

Formati disponibili

11/27/2019 Mobility Management in Connected Mode Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

2 About This Document

3 Overview of Mobility Management in Connected Mode

4 Basic Functions of Mobility Management in Connected Mode

9 Service-request-based Inter-frequency Handover

10 Frequency-priority-based Inter-frequency Handover

11 Separate Mobility Policies to UTRAN for Multi PLMN (FDD)

12 Separate Mobility Policies to GERAN for Multi PLMN

1.1 eRAN13.1 05 (2019-04-30)

1.2 eRAN13.1 04 (2019-01-21)

1.3 eRAN13.1 03 (2018-11-12)

1.4 eRAN13.1 02 (2018-06-30)

Change Description Parameter Change RAT Base Station Model

Change Description Parameter Change RAT Base Station Model

Revised descriptions in this document.

1.5 eRAN13.1 01 (2018-04-10)

Revised descriptions in this document.

1.6 eRAN13.1 Draft B (2018-03-30)

Deleted descriptions of the speed-based inter-frequency handover (FDD).

1.7 eRAN13.1 Draft A (2018-01-15) (FDD)

Change Description Parameter Change Base Station Model

Change Description Parameter Change Base Station Model

Reorganized this document using a new template.

1.8 eRAN13.1 Draft A (2018-01-15) (TDD)

Change Description Parameter Change Base Station Model

Change Description Parameter Change Base Station Model

5.4.1.4 Principles of Blind Handover

Added support for services with QCIs of 75 and 79 None Macro/Micro/LampSite

Reorganized this document using a new template.

2 About This Document

2.1 Applicable RAT

2.2 Features in This Document

Feature ID Feature Name Section

LBFD-002018 Mobility Management 4 Basic Functions of Mobility Management in

LBFD-00201801 Coverage Based Intra-frequency Handover 5.2 Coverage-based Intra-frequency Handover

LBFD-00201802 Coverage Based Inter-frequency Handover 5.3 Coverage-based Inter-frequency Handover

LBFD-00201805 Service Based Inter-frequency Handover 6.2 Service-based Inter-frequency Handover

Feature ID Feature Name Section

LBFD-00201804 Distance Based Inter-frequency Handover 7.2 Distance-based Inter-frequency Handover

6.2 Service-based Inter-frequency Handover

7.2 Distance-based Inter-frequency Handover

This document describes the following TDD features.

Feature ID Feature Name Section

TDLBFD-002018 Mobility Management 4 Basic Functions of Mobility Management in

TDLBFD-00201801 Coverage Based Intra-frequency Handover 5.2 Coverage-based Intra-frequency Handover

TDLBFD-00201802 Coverage Based Inter-frequency Handover 5.3 Coverage-based Inter-frequency Handover

TDLBFD-00201805 Service Based Inter-frequency Handover 6.2 Service-based Inter-frequency Handover

TDLBFD-00201804 Distance Based Inter-frequency Handover 7.2 Distance-based Inter-frequency Handover

TDLOFD-070228 Service-Request Based Inter-frequency Handover 9 Service-request-based Inter-frequency

6.2 Service-based Inter-frequency Handover

7.2 Distance-based Inter-frequency Handover

2.3 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Section

FDD Feature TDD Feature Difference Section

LBFD-002018 Mobility TDLBFD-002018 Mobility None 4 Basic Functions of Mobility

LBFD-00201801 Coverage TDLBFD-00201801 Coverage None 5.2 Coverage-based Intra-

LBFD-00201802 Coverage TDLBFD-00201802 Coverage None 5.3 Coverage-based Inter-

LOFD-001019 PS Inter-RAT TDLOFD-001019 PS Inter-RAT None 5.4 Coverage-based Inter-RAT

LOFD-001020 PS Inter-RAT TDLOFD-001020 PS Inter-RAT None 5.5 Coverage-based Inter-RAT