Sie sind auf Seite 1von 138

eRAN

eRAN7.0
Intra-RAT Mobility Management in Connected
Mode Feature Parameter Description
Issue 03
Date 2014-09-30

HUAWEI TECHNOLOGIES CO., LTD.

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


No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees or representations of
any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: http://www.huawei.com

Email: support@huawei.com

Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types
2 Overview
2.1 Definition
2.2 Benefits
2.3 Architecture
3 Intra-Frequency Mobility Management
3.1 Intra-Frequency Measurement
3.2 Triggering of an Intra-Frequency Handover
3.3 Handover Decision
3.4 Handover Execution
3.5 Signaling Procedures
3.5.1 Procedure of a Successful Handover
3.5.2 Procedure of RRC Connection Reestablishment After a Handover Failure
4 Inter-Frequency Mobility Management
4.1 Coverage-based Inter-Frequency Handover
4.1.1 Triggering and Stopping of Inter-Frequency Measurement
4.1.1.1 Event A2
4.1.1.2 Event A1
4.1.2 Inter-Frequency Measurement
4.1.3 Inter-Frequency Handover Triggering
4.1.3.1 Event A3
4.1.3.2 Event A4
4.1.3.3 Event A5
4.1.4 Blind Handover
4.2 Service-based Inter-Frequency Handover
4.2.1 Triggering and Stopping of Inter-Frequency Measurement
4.2.2 Inter-Frequency Measurement
4.2.3 Inter-Frequency Handover Triggering
4.3 Distance-based Inter-Frequency Handover
4.3.1 Triggering and Stopping of Inter-Frequency Measurement
4.3.2 Inter-Frequency Measurement
4.3.3 Inter-Frequency Handover Triggering
4.4 UL-Quality-based Inter-Frequency Handover
4.4.1 Triggering and Stopping of Inter-Frequency Measurement
4.4.2 Inter-Frequency Measurement
4.4.3 Inter-Frequency Handover Triggering
4.4.4 Blind Handover
4.5 Frequency-Priority-based Inter-Frequency Handover
4.5.1 Triggering and Stopping of Inter-Frequency Measurement
4.5.2 Inter-Frequency Measurement
4.5.3 Inter-Frequency Handover Triggering
4.5.4 Blind Handover
4.6 Handover Decision
4.6.1 Target Decision
4.6.2 Admission Decision
4.7 Handover Execution
4.8 Signaling Procedures

5 Related Features
5.1 Coverage-based Intra-Frequency Handover
5.2 Coverage-based Inter-Frequency Handover
5.3 Service-based Inter-Frequency Handover
5.4 Distance-based Inter-Frequency Handover
6 Network Impact
6.1 Coverage-based Intra-Frequency Handover
6.2 Coverage-based Inter-Frequency Handover
6.3 Service-based Inter-Frequency Handover
6.4 Distance-based Inter-Frequency Handover

7 Engineering Guidelines
7.1 Coverage-based Intra-Frequency Handover
7.1.1 When to Use Coverage-based Intra-Frequency Handover
7.1.2 Required Information
7.1.3 Requirements
7.1.4 Data Preparation
7.1.5 Activation
7.1.6 Activation Observation
7.1.7 Deactivation
7.1.8 Performance Monitoring
7.1.9 Parameter Optimization
7.1.10 Troubleshooting
7.2 Coverage-based Inter-Frequency Handover
7.2.1 When to Use Coverage-based Inter-Frequency Handover
7.2.2 Required Information
7.2.3 Requirements
7.2.4 Data Preparation
7.2.5 Activation
7.2.6 Activation Observation
7.2.7 Deactivation
7.2.8 Performance Monitoring
7.2.9 Parameter Optimization
7.2.10 Troubleshooting
7.3 Service-based Inter-Frequency Handover
7.3.1 When to Use Service-based Inter-Frequency Handover
7.3.2 Required Information
7.3.3 Requirements
7.3.4 Data Preparation
7.3.5 Activation
7.3.6 Activation Observation
7.3.7 Deactivation
7.3.8 Performance Monitoring
7.3.9 Parameter Optimization
7.3.10 Troubleshooting
7.4 Distance-based Inter-Frequency Handover
7.4.1 When to Use Distance-based Inter-Frequency Handover
7.4.2 Required Information
7.4.3 Requirements
7.4.4 Data Preparation
7.4.5 Activation
7.4.6 Activation Observation
7.4.7 Deactivation
7.4.8 Performance Monitoring
7.4.9 Parameter Optimization
7.4.10 Troubleshooting
7.5 UL-quality-based Inter-Frequency Handover
7.5.1 When to Use UL-quality-based Inter-Frequency Handover
7.5.2 Required Information
7.5.3 Requirements
7.5.4 Data Preparation
7.5.5 Activation
7.5.6 Activation Observation
7.5.7 Deactivation
7.5.8 Performance Monitoring
7.5.9 Parameter Optimization
7.5.10 Troubleshooting
7.6 Frequency-Priority-based Inter-Frequency Handover
7.6.1 When to Use Frequency-Priority-based Inter-Frequency Handover
7.6.2 Required Information
7.6.3 Requirements
7.6.4 Data Preparation
7.6.5 Activation
7.6.6 Activation Observation
7.6.7 Deactivation
7.6.8 Performance Monitoring
7.6.9 Parameter Optimization
7.6.10 Troubleshooting

8 Reference Documents
1 About This Document
1.1 Scope
This document describes intra-RAT mobility management in connected mode, including its technical
principles, related features, network impact, and engineering guidelines.
This document covers the following features:
 LBFD-00201801 Coverage Based Intra-frequency Handover
 LBFD-00201802 Coverage Based Inter-frequency Handover
 LBFD-00201804 Distance Based Inter-frequency Handover
 LBFD-00201805 Service Based Inter-frequency Handover
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the
software release delivered with this document. Any future updates will be described in the product
documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB"
refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E and BTS3203E

LampSite DBS3900

1.2 Intended Audience


This document is intended for personnel who:
 Need to understand the features described herein
 Work with Huawei products

1.3 Change History


This section provides information about the changes in different document versions. There are two types
of changes:
 Feature change
Changes in features and parameters of a specified version as well as the affected entities.
 Editorial change
Changes in wording or addition of information and any related parameters affected by editorial
changes. Editorial change does not specify the affected entities.
eRAN7.0 03 (2014-09-30)

This issue includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Changed blind handling to blind handover. For None


details, see descriptions about blind handover in
this document.
eRAN7.0 02 (2014-07-25)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

Editorial change Revised descriptions about inter- None N/A


frequency measurement object
Change Type Change Description Parameter Change Affected Entity

selection in inter-frequency
handovers. For details, see 4.1.2
Inter-Frequency Measurement.
eRAN7.0 01 (2014-04-26)

This issue does not include any changes.


eRAN7.0 Draft B (2014-03-07)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

Editorial change Added 1.4 Differences Between None N/A


eNodeB Types, which describes
differences in feature support
between eNodeB types.
eRAN7.0 Draft A (2014-01-20)

This is a draft for eRAN7.0.

1.4 Differences Between eNodeB Types


Features Support by Macro, Micro, and LampSite eNodeBs

Feature ID Feature Name Supported by Supported by Supported by


Macro Micro eNodeBs LampSite eNodeBs
eNodeBs

LBFD-00201801 Coverage Based Yes Yes Yes


Intra-frequency
Handover

LBFD-00201802 Coverage Based Yes Yes Yes


Inter-frequency
Handover

LBFD-00201804 Distance Based Yes No No


Inter-frequency
Handover

LBFD-00201805 Service Based Inter- Yes Yes Yes


frequency Handover
Function Implementation in Macro, Micro, and LampSite eNodeBs

Each feature or function is implemented in the same way on micro, macro, and LampSite sites.

2 Overview
Based on the frequency of the target cell, intra-RAT mobility management can be classified into intra-
frequency mobility management and inter-frequency mobility management.

2.1 Definition
Intra-Frequency Mobility Management

Intra-frequency mobility management is implemented by handovers between E-UTRAN cells using the
same frequency. A network may use the same frequency in different cells, and therefore the eNodeB
needs to support intra-frequency handovers within the network.
Inter-Frequency Mobility Management

Intra-frequency mobility management is implemented by handovers between E-UTRAN cells using the
different frequencies. A network may use different frequencies in different geographical areas, and
therefore the eNodeB needs to support inter-frequency handovers within the network.

2.2 Benefits
Intra-RAT mobility management in connected mode provides the following benefits:
 Ensures the continuity of radio network coverage and provides uninterrupted communication
services for UEs.
 Provides means to transfer UEs and supports flexible networking to meet operators' service
steering and load balancing requirements.

2.3 Architecture
For the network architecture for intra-RAT mobility management in connected mode, see Overview of
Mobility Management in Connected Mode.

3 Intra-Frequency Mobility Management


Intra-frequency mobility management is implemented through coverage-based intra-frequency
handovers. This chapter describes the basic feature LBFD-00201801 Coverage Based Intra-frequency
Handover. For details about the engineering guidelines for this feature, see 7.1 Coverage-based Intra-
Frequency Handover. The coverage-based intra-frequency handover is enabled or disabled by the switch
IntraFreqCoverHoSwitch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter.
Blind handover is not supported during intra-frequency mobility management, and the coverage-based
intra-frequency handover process can be divided into the following phases:
1. Intra-frequency measurement
When a UE establishes a radio bearer, the eNodeB sends the UE the intra-frequency
measurement configuration, based on which the UE performs measurements. Then, the UE
generates a candidate cell list based on measurement results.
2. Triggering intra-frequency handovers
Intra-frequency handovers are triggered by event A3. For details, see 3.2 Triggering of an
Intra-Frequency Handover.
3. Handover decision
In the handover decision phase, the eNodeB checks the cells in the candidate cell list and
determines whether a handover needs to be initiated and, if so, to which cell the UE is to be
handed over.
4. Handover execution
In the handover execution phase, the eNodeB controls the procedure of UE handover to the
target cell.

3.1 Intra-Frequency Measurement


If the switch for the coverage-based intra-frequency handover is turned on, the eNodeB sends the UE the
intra-frequency measurement configuration in a Measurement Configuration message when the UE
establishes a radio bearer.
Based on the measurement configuration, the UE measures all cells on the associated frequency within
the measurement scope.
After the UE enters the RRC connected mode or a handover is complete, the eNodeB checks whether
the measurement configuration for the UE needs to be updated. If yes, the eNodeB delivers the entirely
or partially updated measurement configuration to the UE through an RRC Connection Reconfiguration
message. If no, the eNodeB does not deliver updated measurement configuration. In this case, the UE
uses the original measurement configuration.
The Measurement Configuration message used for intra-frequency measurements contains the basic
information listed in Table 3-1. For details about the measurement report configuration, see 3.2 Triggering
of an Intra-Frequency Handover.
Table 3-1 Parameters in the measurement configuration

Measurement Parameter Parameter ID Parameter Description


Configuration Name

Measurement Downlink Cell.DlEarfcn It is a cell-level parameter.


objects EARFCN

Frequency Cell.QoffsetFreq It is a frequency-level


offset parameter.

Measurement CellResel.MeasBandWidth It is a cell-level parameter.


bandwidth

EUTRAN EUTRAN HoMeasComm.EutranFilterCoeffRSRP They are eNodeB-level


RSRP filter RSRP filter common parameters.
coefficient coefficient

EUTRAN HoMeasComm.EutranFilterCoeffRSRQ
RSRQ filter
coefficient

3.2 Triggering of an Intra-Frequency Handover


Event A3 indicates that the signal quality in a neighboring cell is better than that in the serving cell. When
coverage-based intra-frequency handover is enabled, the eNodeB sends measurement configurations
related to event A3 to the UE during UE radio bearer setup.
The entering and leaving conditions of event A3 are shown in Figure 3-1 and Figure 3-2. For details about
event A3, see section 5.5.4.4 "Event A3 (Neighbour becomes offset better than PCell)" in 3GPP TS
36.331 V10.1.0.
 Entering condition: Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off
After receiving an event A3 from a UE, the eNodeB makes handover decision based on the
reported candidate cell list.
 Leaving condition: Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off
If the leaving condition of event A3 is met, the UE no longer reports event A3.
Figure 3-1 Event A3 triggering condition

Figure 3-2 Event A3 leaving condition

The variables in the preceding formulas are described in Table 3-2.


Assume that both Hys and Off are set to 2 dB. The eNodeB detects that the signal quality in the source
cell always drops rapidly and the signal quality in the target cell always rises quickly in a handover.
To facilitate intra-frequency handovers, you can set Ocs to -1 dB for the serving cell and set Ocn to 1 dB
for the target cell.
Ofs and Ofn use the same value for an intra-frequency handover. Assume that they are set to 0 dB, then
the entering condition of event A3 is as follows: Mn + 0 + 1 - 2 > Ms + 0 - 1 + 2. That is, event A3 can be
triggered when the signal quality of the target cell is 2 dB higher than that of the serving cell.
Table 3-2 Parameters related to event A3

Variable Paramet Parameter ID Parameter Description


s in the er Name
Formula

Ms - - Ms is the measurement result of the


serving cell and Mn is the measurement
Mn - - result of the neighboring cell. The
measurement result type is specified by
the
IntraRatHoComm.IntraFreqHoA3Trig
Quan parameter.

Ofs/Ofn Frequenc Cell.QoffsetFreq This is a frequency-level parameter.


y offset This parameter is contained in the
measurement configuration.

Ocs Cell Cell.CellSpecificOffset This is a cell-level parameter. This


specific parameter is contained in the
offset measurement configuration.

Ocn Cell EutranIntraFreqNCell.CellIndividualO This is a cell-level parameter.


individual ffset  If the value is not 0, the parameter
offset is contained in the measurement
configuration.
 If the value is 0, the parameter is
not contained in the measurement
configuration and the default value
0 is used for calculation.

Hys Intrafreq IntraFreqHoGroup.IntraFreqHoA3Hy This parameter is set for each QCI.


handover st
hysteresi
s

Off Intrafreq IntraFreqHoGroup.IntraFreqHoA3Off


handover set
offset

Table 3-3 lists other parameters related to the reporting of event A3.
Table 3-3 Other parameters related to the reporting of event A3
Parameter Parameter ID Parameter Description
Name

Intrafreq IntraFreqHoGroup.IntraFreqHoA3TimeToTrig This parameter is set for each QCI.


handover time
to trigger

Max report cell IntraRatHoComm.IntraRATHoMaxRprtCell Cells included in These are


number the measurement common
report are eNodeB-level
sequenced based parameters
on the value of Mn used for intra-
for triggering event RAT
A3. handovers.

Measurement IntraRatHoComm.IntraRATHoRprtAmount This parameter is


report amount used to limit the
number of
measurement
reports, reducing
the number of
handover retries.

A3 IntraRatHoComm.IntraFreqHoA3TrigQuan This parameter


measurement specifies the Mn
trigger quantity and Ms type and
triggering quantity
for event A3.

A3 IntraRatHoComm.IntraFreqHoA3RprtQuan This parameter


measurement specifies the
report quantity reporting quantity
to be included in
the measurement
reports after event
A3 is triggered.

A3 IntraRatHoComm.IntraFreqHoRprtInterval This parameter


measurement specifies the
report interval interval between
two event A3
measurement
reports from the
UE. Setting this
parameter to a
proper value
reduces signaling
traffic on the air
interface.

3.3 Handover Decision


In the handover decision phase, the eNodeB checks the cells in the candidate cell list and determines
whether a handover needs to be initiated and, if so, to which cell the UE is to be handed over.
The eNodeB first filters out following cells from the candidate cell list:
 Blacklisted neighboring cells
 Neighboring cells with a handover prohibition flag
 Neighboring cells that have a different PLMN from the serving cell
These cells will not be filtered out if the inter-PLMN handover switch is turned on.
InterPlmnHoSwitch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter controls the
inter-PLMN handover switch.
 Neighboring cells in the areas indicated by the IE Handover Restriction List in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME
When a UE is performing VoIP services, cells that forbid VoIP handovers are also filtered.
VoipHoControlSwitch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to
enable this function.
 When this switch is turned on, cells specified by EutranVoipHoBlkList are filtered when a UE is
performing VoIP services.
 When this switch is turned off, cells specified by EutranVoipHoBlkList are not filtered when a
UE is performing VoIP services.
The ENodeBAlgoSwitch.EutranVoipSupportSwitch parameter indicates whether the VoIP services are
allowed in the E-UTRAN cell.
 When this switch is turned on, VoIP services are allowed in the E-UTRAN cell, which means that
the establishment, handover in, admission, and reestablishment of VoIP services are allowed.
 When this switch is turned off, VoIP services are not allowed in the E-UTRAN cell, which means
that the establishment, handover in, admission, and reestablishment of VoIP services are not
allowed.
Assume that eNodeB1 cells are neighboring cells of eNodeB2. It is recommended that eNodeB1 cells be
added to the EutranVoipHoBlkList parameter of eNodeB2 if eNodeB1 forbids VoIP service handover in.
Otherwise, the handover attempt fails.
The eNodeB then sends a handover request to the target cell at the top of the candidate cell list. If the
handover request fails, the eNodeB sends the handover request to the next target cell.
A cell with the best signal quality (as indicated in the measurement result) has the highest priority. If the
measurement result of an intra-eNodeB cell is the same as that of an inter-eNodeB cell, the eNodeB
assigns the intra-eNodeB cell a higher priority to avoid signaling and data forwarding required in an inter-
eNodeB handover.
If the eNodeB has tried all cells indicated in the measurement report but failed to perform a handover, the
eNodeB waits for the next measurement report from the UE.

3.4 Handover Execution


After making a handover decision, the eNodeB initiates a handover towards the best cell in the filtered
candidate cell list.
During an intra-frequency handover, the eNodeB sends handover requests and forwards data through the
X2 or S1 interface adaptively.
 If the handover succeeds, the target eNodeB (in an X2-based handover) or the MME (in an S1-
based handover) sends a Release Resource message to the source eNodeB after data
forwarding is complete. The source eNodeB then release related resources.
 If the handover fails, the UE performs a cell selection procedure and then initiates an RRC
connection reestablishment procedure towards the selected cell.
If the handover admission fails, the eNodeB initiates a handover attempt to the next best cell in the
candidate cell list. For details about the retry and penalty mechanism, see Overview of Mobility
Management in Connected Mode.

3.5 Signaling Procedures

3.5.1 Procedure of a Successful Handover


This section describes the signaling procedure of a successful intra-MME inter-eNodeB handover, as
shown in Figure 3-3.
Figure 3-3 Signaling procedure of a successful intra-MME inter-eNodeB handover

1. When the UE establishes a radio bearer, the source eNodeB sends the UE an RRC
Connection Reconfiguration message that contains the measurement configuration, which
controls the measurements of the UE in RRC connected mode.
2. The UE sends measurement reports to the source eNodeB based on the measurement results.
3. The source eNodeB makes a handover decision based on the measurement reports.
4. After deciding that a handover is to be performed, the source eNodeB sends a Handover
Request message to the target eNodeB, requesting the target eNodeB to prepare for the
handover.
5. The target eNodeB makes admission decisions. If resources can be granted by the target
eNodeB, the target eNodeB performs admission control depending on the QoS information
about the Evolved Packet System (EPS) bearer.
6. The target eNodeB prepares layer 1 and layer 2 resources for the handover and then sends a
Handover Request Acknowledge message to the source eNodeB.
7. The source eNodeB sends the UE an RRC Connection Reconfiguration message that contains
the MobilityControlInfo IE, indicating that the handover should start.

NOTE:
Data forwarding starts when the source eNodeB sends the UE an RRC Connection
Reconfiguration message that contains the MobilityControlInfo IE.
8. The UE performs a random access procedure towards the target eNodeB for uplink
synchronization with the target eNodeB.
9. After successfully accessing the target cell, the UE sends the target eNodeB an RRC
Connection Reconfiguration Complete message, indicating that the handover procedure is
complete. Subsequently, the target eNodeB can start sending data to the UE.
10. The downlink data path switching is performed.
11. The target eNodeB sends the source eNodeB a UE Context Release message to inform the
source eNodeB of a handover success and to trigger the resource release at the source
eNodeB.
12. After receiving the UE Context Release message, the source eNodeB releases the radio and
control-plane resources associated with the UE context.
Intra-frequency mobility management is applicable to intra-eNodeB handovers, intra-MME inter-eNodeB
handovers, and inter-MME inter-eNodeB handovers. For either of the latter two handover types, the
signaling procedure varies depending on whether the X2 interface is available between the eNodeBs.
 In the case of an intra-MME handover between eNodeBs where the X2 interface is unavailable,
the signaling and the data forwarding between the two eNodeBs as shown in Figure 3-3 are
implemented over the S1 interface.
 In the case of an inter-MME handover between eNodeBs where the X2 interface is unavailable,
the signaling and the data forwarding between the two eNodeBs as shown in Figure 3-3 are
implemented over the S1 interface and Evolved Packet Core network (EPC), which is an indirect
route compared with the route over the X2 interface.
 In the case of an inter-MME handover between eNodeBs where the X2 interface is available, the
signaling between the two eNodeBs as shown in Figure 3-3 is implemented through the S1
interface and EPC, which is an indirect route compared with the route over the X2 interface. In
addition, the data forwarding between them is implemented over the X2 interface.

3.5.2 Procedure of RRC Connection Reestablishment After a Handover Failure


After a handover fails, the UE performs a cell selection procedure and then initiates a procedure of RRC
connection reestablishment towards the selected cell. The RRC connection can be reestablished
successfully only when the selected cell is a prepared cell.
The RRC connection reestablishment procedure is different in successful RRC reestablishment and failed
RRC reestablishment.
 A successful reestablishment procedure, as shown in Figure 3-4, consists of the following steps:
1. The UE sends an RRC Connection Reestablishment Request message to the eNodeB to
which the prepared cell belongs, to request the reestablishment of the RRC connection.
2. The eNodeB responds with an RRC Connection Reestablishment message, indicating that it
has accepted the request.
3. The UE performs the RRC connection reestablishment and sends an RRC Connection
Reestablishment Complete message.
Figure 3-4 Successful RRC connection reestablishment procedure

 If the RRC connection reestablishment fails, the UE enters the idle mode. A failed
reestablishment procedure, as shown in Figure 3-5, consists of the following steps:
1. The UE sends an RRC Connection Reestablishment Request message to the eNodeB to
which the prepared cell belongs, to request the reestablishment of the RRC connection.
2. The eNodeB responds with an RRC Connection Reestablishment Reject message, indicating
that it rejects the request.
Figure 3-5 Failed RRC connection reestablishment procedure

4 Inter-Frequency Mobility Management


Inter-frequency mobility management can be implemented in different manners. This section describes
the following features/functions:
 LBFD-00201802 Coverage Based Inter-frequency Handover
 LBFD-00201805 Service Based Inter-frequency Handover
 LBFD-00201804 Distance Based Inter-frequency Handover
 UL-quality-based inter-frequency handover
 Frequency-priority-based inter-frequency handover
The triggering condition for each feature or function is different, and the mobility management can mainly
be divided into the following phases:
1. Target cell/frequency selection
For a measurement, the eNodeB generates a candidate cell list based on inter-RAT
measurement results.
For a blind handover, the eNodeB selects a blind handover target based on the blind handover
priority or frequency priority of neighboring cells.
2. Handover decision
In the handover decision phase, the eNodeB checks the candidate cell list. Based on the check
result, the eNodeB determines whether a handover needs to be initiated and, if so, to which
cell the UE is to be handed over.
3. Handover execution
In the handover execution phase, the eNodeB controls the procedure of UE handover to the
target cell.

4.1 Coverage-based Inter-Frequency Handover


This section describes the basic feature LBFD-00201802 Coverage Based Inter-frequency Handover. For
details about the engineering guidelines for this feature, see 7.2 Coverage-based Inter-Frequency
Handover. The coverage-based inter-frequency handover is enabled or disabled by the switch
InterFreqCoverHoSwitch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter.
During a coverage-based inter-frequency handover, measurements or blind handover can be triggered
and stopped by different events, as shown in Table 4-1.
Table 4-1 Events for triggering/stopping measurements or blind handover during a coverage-based inter-
frequency handover

Procedure Subprocedure Triggering Events Stopping Events

Measurement Inter-frequency Event A2 Event A1


measurement

Inter-frequency Event A3, event A4, or event -


handover A5

Blind - Event A2 Event A1


handover

The eNodeB delivers measurement configuration for event A2 for inter-frequency measurement or event
A2 for blind handover as follows:
 If the UE is in RRC-connected mode, the eNodeB delivers measurement configuration for both
event A2 for inter-frequency measurement and event A2 for blind handover.
 If the signal quality in the serving cell is lower than the specified threshold, the UE reports
event A2 for inter-frequency measurement. After receiving the report, the eNodeB delivers
an inter-frequency measurement configuration.
 If the signal quality in the serving cell further deteriorates and the eNodeB does not
perform a handover for the UE, the UE reports event A2 for blind handover. After receiving
the report, the eNodeB considers that the serving cell can no longer provide services for
the UE and performs a blind handover.
 In the following scenarios, the eNodeB delivers measurement configuration for event A2 only for
blind handover:
 The UE does not support inter-frequency measurements.
 The configured event A2 threshold for inter-frequency measurements is less than or equal
to that for blind handover.

4.1.1 Triggering and Stopping of Inter-Frequency Measurement


Inter-frequency measurements are triggered by event A2 and stopped by event A1.
During a coverage-based inter-frequency handover, the sequence that the measurement configuration for
events A1 and A2 is sent is controlled by the ReduceInvalidA1A2RptSigSwitch switch under the
ENodeBAlgoSwitch.HoSignalingOptSwitch parameter.
 If the switch is turned on, the eNodeB sends measurement configuration for event A2 when the
UE sets up an RRC connection, and sends measurement configuration for event A1 after it
receives an event A2 from the UE. This reduces the reporting of invalid event A1.
 If the switch is turned off, the eNodeB sends measurement configuration for both event A2 and
event A1 when the UE sets up an RRC connection.

4.1.1.1 Event A2
Event A2 indicates that the signal quality of the serving cell is lower than a threshold.
Event A2 for Inter-Frequency Measurement

The entering and leaving conditions of event A2 are shown in Figure 4-1. For details about event A2, see
section 5.5.4.3 "Event A2 (Serving becomes worse than threshold)" in 3GPP TS 36.331 V10.1.0.
 Entering condition: Ms + Hys < Thresh
If the entering condition is met, the UE reports an event A2. After receiving the event A2 report,
the eNodeB delivers a measurement configuration to start inter-frequency measurement.
 Leaving condition: Ms - Hys > Thresh
If the leaving condition of event A2 is met, the UE no longer reports event A2.
Figure 4-1 Entering and leaving conditions of event A2

The variables in the preceding formulas are described in Table 4-2 and Table 4-3. Thresholds related to
event A2 vary according to events that are used to trigger inter-frequency handovers.
Table 4-2 Parameters related to event A2

Variable Paramet Parameter ID Parameter Description


s in the er Name
Formul
a

Ms - - Ms is the measurement result of the


serving cell. The measurement result type
is specified by the
IntraRatHoComm.InterFreqHoA1A2Tri
gQuan parameter.

Hys Interfreq InterFreqHoGroup.InterFreqHoA1A This parameter is set for each QCI.


A1A2 2Hyst
hysteresi
s
Table 4-3 Thresholds related to event A2 according to events that are used to trigger inter-frequency
handovers
Events Parame Parameter ID of the Threshold Parameter Description
That ter
Trigger Name
Inter- of the
Frequen Thresh
cy old
Handov
er

Event A3 InterFreqHoGroup.A3InterFreqHoA This parameter is set for each QCI.


A3 based 2ThdRsrp If event A3 is used to trigger inter-
Interfreq frequency handover, the threshold for
A2 event A2 can only be the RSRP threshold.
RSRP
threshol
d

Events Interfreq InterFreqHoGroup.InterFreqHoA2T This parameter is set for each QCI.


A4 and A2 hdRSRP The
A5 RSRP IntraRatHoComm.InterFreqHoA1A2Trig
threshol Quan parameter determines which
d threshold is to be used.
 If
Interfreq InterFreqHoGroup.InterFreqHoA2T IntraRatHoComm.InterFreqHoA1A
A2 hdRSRQ 2TrigQuan is set to BOTH, two A2
RSRQ events are reported, with one being
threshol RSRP-based and the other RSRQ-
d based. When the entering condition
for either of the A2 events is met, the
UE reports the A2 event.
 If
IntraRatHoComm.InterFreqHoA1A
2TrigQuan is set to RSRP or RSRQ,
the UE reports an A2 event only
when the entering condition for the
related A2 event is met.

Table 4-4 lists other parameters related to the event A2 report.


Table 4-4 Other parameters related to the event A2 report

Parameter Name Parameter ID Parameter Description

Interfreq A1A2 time InterFreqHoGroup.InterFreqHoA1A2TimeToTrig This parameter is set for


to trigger each QCI.

InterFreq A1A2 IntraRatHoComm.InterFreqHoA1A2TrigQuan This is a common


Measurement trigger parameter for intra-RAT
quantity handover and is set for
each eNodeB.
This parameter specifies
the Ms type and triggering
Parameter Name Parameter ID Parameter Description

quantity for events A1 and


A2.
Event A2 for Target-based Measurement

Huawei eNodeBs allow different event A2 parameters to be set for target FDD and TDD frequencies so
that coverage-based handovers can be preferentially triggered for FDD or TDD frequencies.
The variables Ms and Hys for event A2 for target-based measurement are the same as those for event
A2 for inter-frequency measurement. Table 4-5 lists the thresholds related to event A2 for target-based
measurement.
Table 4-5 Thresholds related to event A2 for target-based measurement

Frequ Parameter ID of the Parameter ID of the Threshold Param


ency Threshold Offset eter
Type Descri
ption

FDD CnOperatorHoCfg.FddIfH InterFreqHoGroup.A3InterFreqHoA2ThdRsrp/InterFr The


oA2ThdRsrpOffset eqHoGroup.InterFreqHoA2ThdRSRP thresho
ld for
TDD CnOperatorHoCfg.TddIfH event
oA2ThdRsrpOffset A2 is
the
sum of
the
RSRP
thresho
ld.
Only
the
RSRP
thresho
ld for
event
A2 is
accomp
anied
by an
offset,
while
the
RSRQ
thresho
ld for
event
A2 is
not.

The eNodeB delivers measurement configurations for event A2 for target-based measurement as follows:
 If CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset and
CnOperatorHoCfg.TddIfHoA2ThdRsrpOffset are set to different values, the eNodeB delivers
two measurement configurations for events A2, with one corresponding to an FDD frequency
and the other corresponding to a TDD frequency. After a UE reports an event A2 related to a
frequency, the eNodeB delivers the measurement configuration of the related frequency.
 If CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset and
CnOperatorHoCfg.TddIfHoA2ThdRsrpOffset are set to the same value, the eNodeB delivers
one measurement configuration for event A2, without distinguishing between the FDD and TDD
frequencies. After a UE reports an event A2, the eNodeB delivers two measurement
configurations, one for the FDD frequency and the other for the TDD frequency.
Pay attention to the following points related to event A2 for target-based measurement:
 If only either of the offset is set to -100, the inter-frequency measurement of an FDD or TDD
frequency is not triggered.
 If both offset values are set to -100, the effect is the same as those set to 0. In this case, the
eNodeB sends an inter-frequency event A2, with the threshold set to the event A2 threshold
value.
 If the calculated RSRP threshold is lower than the protocol-specified minimum value, the
protocol-specified minimum value is used as the RSRP threshold.
 If the calculated RSRP threshold is higher than the protocol-specified maximum value, the
protocol-specified maximum value is used as the RSRP threshold.

4.1.1.2 Event A1
Event A1 indicates that the signal quality of the serving cell is higher than a threshold.
The entering and leaving conditions of event A1 are shown in Figure 4-2. For details about event A1, see
section 5.5.4.2 "Event A1 (Serving becomes better than threshold)" in 3GPP TS 36.331 V10.1.0.
 Entering condition: Ms - Hys > Thresh
When event A1 is triggered, the eNodeB receives an event A1 from the UE.
 Leaving condition: Ms + Hys < Thresh
When the leaving condition of event A1 is met, the eNodeB no longer reports event A1.
Figure 4-2 Entering and leaving conditions of event A1

The variables in the formulas for event A1 are the same as those in the formulas for event A2. Thresholds
related to event A1 also vary according to events that are used to trigger inter-frequency handovers, as
described in Table 4-6.
Table 4-6 Thresholds related to event A1 according to events that are used to trigger inter-frequency
handovers

Events Parame Parameter ID of the Threshold Parameter Description


That ter
Trigger Name
Inter- of the
Frequen Thresh
cy old
Handov
er

Event A3 InterFreqHoGroup.A3InterFreqHoA This parameter is set for each QCI.


A3 based 1ThdRsrp If event A3 is used to trigger inter-
Interfreq frequency handover, the threshold for
A1 event A1 can only be the RSRP threshold.
RSRP
threshol
d
Events Parame Parameter ID of the Threshold Parameter Description
That ter
Trigger Name
Inter- of the
Frequen Thresh
cy old
Handov
er

Events Interfreq InterFreqHoGroup.InterFreqHoA1T This parameter is set for each QCI.


A4 and A1 hdRSRP The
A5 RSRP IntraRatHoComm.InterFreqHoA1A2Trig
threshol Quan parameter determines which
d threshold is to be used.
 If
Interfreq InterFreqHoGroup.InterFreqHoA1T IntraRatHoComm.InterFreqHoA1A
A1 hdRSRQ 2TrigQuan is set to BOTH, two A1
RSRQ events are reported, with one being
threshol RSRP-based and the other RSRQ-
d based. The eNodeB stops coverage-
based inter-frequency measurement
only when both RSRP-based and
RSRQ-based measurement results
meet the entering condition.
 If
IntraRatHoComm.InterFreqHoA1A
2TrigQuan is set to RSRP or RSRQ,
the UE reports an A1 event only
when the entering condition for the
related A1 event is met.

Other parameters related to the event A1 report are the same as those related to event A2 report. For
details, see Table 4-4.
You must set the thresholds related to event A1 to be higher than those related to event A2. If the RSRP
threshold offset for FDD or TDD frequencies are set, the thresholds related to event A1 must be greater
than or equal to the sum of the thresholds related to event A2 and the offset.

4.1.2 Inter-Frequency Measurement


The Measurement Configuration message used for inter-frequency measurements contains the basic
information listed in Table 4-7. 4.1.3 Inter-Frequency Handover Triggering lists information contained in
the reporting configuration.
Table 4-7 Parameters in the measurement configuration

Measurement Parameter Parameter ID Parameter Description


Configuration Name

Measurement Downlink EutranInterNFreq.DlEarfcn This is a cell-level


objects EARFCN parameter.
If an inter-frequency
neighboring cell is a
multi-band cell, the
eNodeB calculates and
Measurement Parameter Parameter ID Parameter Description
Configuration Name

delivers an EARFCN
based on the band
supporting capability of
the UE.
For details about the
relationship between the
band and EARFCN, see
section 5.7.3 "Carrier
frequency and EARFCN"
in 3GPP TS 36.101
V10.2.1.
For details about multi-
band cells, see Cell
Management.

Frequency EutranInterNFreq.QoffsetFreqConn This is a frequency-level


offset parameter.

Measurement EutranInterNFreq.MeasBandWidth This is a frequency-level


bandwidth parameter.

Cell EutranInterFreqNCell.CellIndividualOffset This is a parameter for a


individual neighboring cell.
offset

Filter EUTRAN HoMeasComm.EutranFilterCoeffRSRP This is an eNodeB-level


coefficients RSRP filter common parameter.
coefficient

EUTRAN HoMeasComm.EutranFilterCoeffRSRQ
RSRQ filter
coefficient

Measurement GAP HoMeasComm.GAPPatternType


gap measurement
configuration pattern

 The FixedMeasObjIDSwitch option of the CellAlgoSwitch.MultiFreqPriControlSwitch


parameter specifies the frequency priority for UEs. The eNodeB selects the frequencies for
measurement in descending order of frequency priority till the number of selected frequencies
reaches the maximum. If all frequencies with the same priority are selected and the number of
frequencies for measurement exceeds the maximum, the eNodeB randomly selects frequencies
with this priority till the number of selected priorities reaches the maximum.
 When this option is deselected, the frequency priority is determined by the
EutranInterNFreq.ConnFreqPriority parameter. A larger value indicates a higher priority.
The eNodeB selects the frequencies for measurement in descending order of frequency
priority till the number of selected frequencies reaches the maximum.
 When this option is selected, the frequency priority is determined by the
EutranInterNFreq.MeasFreqPriority parameter. A larger value indicates a higher priority.
The eNodeB sets measurement object IDs based on frequency priorities to control the
UE's actual measurement priorities. This ensures that the UE preferentially reports the
measurement reports on high-priority frequencies.
 The eNodeB delivers information about a cell for measurement only if the cell individual offset
(CIO) of the cell is not set to the default value (0 dB). The measurement priority of an inter-
frequency neighboring cell is determined by the combination of the high bit and low bit specified
by the EutranInterFreqNCell.CellMeasPriority and
EutranInterFreqNCell.CellIndividualOffset parameters, respectively.
 For details about the specifications of the number of frequencies and neighboring cells in a
measurement configuration message, see Overview of Mobility Management in Connected
Mode.

4.1.3 Inter-Frequency Handover Triggering


Coverage-based inter-frequency handovers can be triggered by event A3, A4, or A5. The
EutranInterNFreq.InterFreqHoEventType parameter specifies which event triggers coverage-based
inter-frequency handovers.
 When receiving event A2 that triggers inter-frequency measurement, the eNodeB sends related
inter-frequency handover event according to parameter configurations.
 If carrier aggregation (CA) is enabled and the EutranInterNFreq.InterFreqHoEventType
parameter is set to EventA4(EventA4), the eNodeB will send a measurement configuration for
event A5 to trigger an inter-frequency measurement when a CA UE reports an event A2 in the
primary serving cell (PCell). For details, see Carrier Aggregation.

4.1.3.1 Event A3
Event A3 triggers inter-frequency handovers the same way as it triggers intra-frequency handovers. For
details, see 3.2 Triggering of an Intra-Frequency Handover.
All parameters (other than Ofn and Off) for event A3 that triggers inter-frequency handovers are the same
as those for event A3 that triggers intra-frequency handovers. Table 4-8 lists the parameters related to
event A3.
Table 4-8 Parameters related to event A3

Variable Paramet Parameter ID Parameter Description


s in the er Name
Formula

Ms - - Ms is the measurement result of the


serving cell and Mn is the measurement
Mn - - result of the neighboring cell. The
measurement result type is specified by
the
IntraRatHoComm.IntraFreqHoA3Trig
Quan parameter.

Ofs Frequenc Cell.QoffsetFreq This is a frequency-level parameter.


y offset This parameter is contained in the
measurement configuration.
Ofn Frequenc EutranInterNFreq.QoffsetFreqConn
y offset
Variable Paramet Parameter ID Parameter Description
s in the er Name
Formula

Ocs Cell Cell.CellSpecificOffset This parameter is contained in the


specific measurement configuration.
offset

Ocn Cell EutranInterFreqNCell.CellIndividualO  If the value is not 0, the parameter


individual ffset is contained in the measurement
offset configuration.
 If the value is 0, the parameter is
not contained in the measurement
configuration and the default value
0 is used for calculation.

Hys Intrafreq IntraFreqHoGroup.IntraFreqHoA3Hy This parameter is set for each QCI.


handover st
hysteresi
s

Off Interfreq InterFreqHoGroup.InterFreqHoA3Off


A3 offset set

Table 4-9 lists other parameters related to the event A3 report.


Table 4-9 Other parameters related to the event A3 report

Parameter Parameter ID Parameter Description


Name

Intrafreq IntraFreqHoGroup.IntraFreqHoA3TimeToTrig This parameter is set for each QCI.


handover time
to trigger

Max report cell IntraRatHoComm.IntraRATHoMaxRprtCell The reported cells These are


number are sequenced common
according to the eNodeB-level
value of Mn that parameters
triggers event A3. used for intra-
RAT
Measurement IntraRatHoComm.IntraRATHoRprtAmount This parameter is handovers.
report amount used to limit the
number of
measurement
reports, reducing
the number of
handover retries.

A3 IntraRatHoComm.IntraFreqHoA3TrigQuan This parameter


measurement specifies the Mn
trigger quantity and Ms type and
triggering quantity
for event A3.
Parameter Parameter ID Parameter Description
Name

A3 IntraRatHoComm.IntraFreqHoA3RprtQuan This parameter


measurement specifies the
report quantity reporting quantity
to be included in
the measurement
reports after event
A3 is triggered.

A3 IntraRatHoComm.IntraFreqHoRprtInterval This parameter


measurement specifies the
report interval interval between
two event A3
measurement
reports from the
UE. Setting this
parameter to a
proper value
reduces signaling
traffic on the air
interface.

4.1.3.2 Event A4
Event A4 indicates that the signal quality of a neighboring cell is higher than a threshold.
The entering and leaving conditions of event A4 are shown in Figure 4-3. For details about event A4, see
section 5.5.4.5 "Event A4 (Neighbour becomes better than threshold)" in 3GPP TS 36.331 V10.1.0.
 Entering condition: Mn + Ofn + Ocn - Hys > Thresh
If the entering condition is met, the UE reports an event A4.
 Leaving condition: Mn + Ofn + Ocn + Hys < Thresh
If the leaving condition of event A4 is met, the UE no longer reports event A4.
Figure 4-3 Entering condition of event A4

The variables in the preceding formulas are described in Table 4-10.


Table 4-10 Parameters related to event A4

Variabl Paramet Parameter ID Parameter Description


es in er Name
the
Formul
a

Mn - - Mn is the measurement result of the


neighboring cell. The measurement result
type is specified by the
IntraRatHoComm.InterFreqHoA1A2Tri
gQuan parameter.

Ofn Frequenc EutranInterNFreq.QoffsetFreqConn This is a frequency-level parameter.


y offset This parameter is contained in the
measurement configuration.
This parameter adjusts the UE to
preferentially hands over to a specific
frequency. This parameter adjusts the
handover difficulty between cells of
different frequencies.
Variabl Paramet Parameter ID Parameter Description
es in er Name
the
Formul
a

Ocn Cell EutranInterFreqNCell.CellIndividual This parameter is contained in the


individual Offset associated measurement object in the
offset delivered measurement configuration.

Hys Interfreq InterFreqHoGroup.InterFreqHoA4Hy This parameter is set for each QCI.


handover st
hysteresi
s

Table 4-11 lists the threshold parameters related to event A4.


Table 4-11 Threshold parameters related to event A4

Threshold Threshold Value Parameter Description


Parameter

CoverageBas When the triggering threshold is RSRP, The threshold parameter is set for each QCI.
ed Interfreq the threshold value equals The threshold offset parameter is set for each
RSRP InterFreqHoGroup.InterFreqHoA4Thd inter-frequency neighboring frequency.
threshold RSRP plus The threshold parameter is set for each QCI.
EutranInterNFreq.IfHoThdRsrpOffset.
The threshold offset parameter is set for each
inter-frequency neighboring frequency.
CoverageBas When the triggering threshold is RSRQ,
ed Interfrq the threshold value equals The
RSRQ InterFreqHoGroup.InterFreqHoA4Thd IntraRatHoComm.InterFreqHoA1A2TrigQu
threshold RSRQ. an parameter determines which triggering
threshold is to be used.
 When
IntraRatHoComm.InterFreqHoA1A2Tr
igQuan is set to BOTH, the eNodeB
delivers a measurement configuration
related to event A4 according to the
triggering quantity of the reported event
A2.
 When
IntraRatHoComm.InterFreqHoA1A2Tr
igQuan is set to RSRP or RSRQ, the
eNodeB delivers a measurement
configuration related to event A4 for
which the triggering quantity is RSRP or
RSRQ, respectively.
The
IntraRatHoComm.InterFreqHoA4RprtQuan
parameter determines the reporting quantity
to be included in the measurement reports
after event A4 is triggered.
 When
IntraRatHoComm.InterFreqHoA4Rprt
Threshold Threshold Value Parameter Description
Parameter

Quan is set to BOTH, two A4 events


are reported, with one being RSRP-
based and the other RSRQ-based. An
inter-frequency handover is triggered
only when both measurement quantities
meet the condition that the sum of the
Mn, Ofn, Ocn, and Hys values is greater
than or equal to the threshold value.
 When
IntraRatHoComm.InterFreqHoA4Rprt
Quan is set to
SAME_AS_TRIG_QUAN(Same as Trig
Quan), coverage-based measurement
report type for event A4 is the same as
the measurement triggering quantity.

Table 4-12 lists other parameters related to the event A4 report.


Table 4-12 Other parameters related to the event A4 report

Parameter Parameter ID Parameter Description


Name

Interfreq InterFreqHoGroup.InterFreqHoA4TimeToTrig This parameter is set for each QCI.


HandOver
Time to Trigger

Max report cell IntraRatHoComm.IntraRATHoMaxRprtCell The reported cells This is a


number are sequenced common
according to the parameter for
value of Mn that intra-RAT
triggers event A3. handover and
is set for each
Measurement IntraRatHoComm.IntraRATHoRprtAmount This parameter eNodeB.
report amount specifies the
number of events
to be reported.
Setting this
parameter to a
proper value
reduces the
number of
handover retries.

InterFreq A1A2 IntraRatHoComm.InterFreqHoA1A2TrigQuan This parameter


Measurement specifies the Mn
trigger quantity type.

Measurement IntraRatHoComm.InterFreqHoA4RprtQuan This parameter


A4 report specifies the
quantity reporting quantity
Parameter Parameter ID Parameter Description
Name

to be included in
the measurement
reports after event
A4 is triggered.

Interfreq IntraRatHoComm.InterFreqHoRprtInterval This parameter


measurement specifies the
report interval interval at which
periodical
measurement
reports are sent
after event A4 is
triggered.

4.1.3.3 Event A5
Event A5 indicates that the signal quality of the serving cell is lower than threshold 1 (Thresh1) and the
signal quality of a neighboring cell is higher than threshold 2 (Thresh 2).
The entering and leaving conditions of event A5 are shown in Figure 4-4. For details about event A5, see
section 5.5.4.6 "Event A5 (PCell becomes worse than threshold1 and neighbour becomes better than
threshold2)" in 3GPP TS 36.331 V10.1.0.
 Entering condition: Ms + Hys < Thresh1 and Mn + Ofn + Ocn - Hys > Thresh2
If the entering condition is met, the UE reports an event A5. After receiving the event A5 report,
the eNodeB delivers a measurement configuration to start inter-frequency handover.
 Leaving condition: Ms - Hys > Thresh1 or Mn + Ofn + Ocn + Hys < Thresh2
If the leaving condition of event A5 is met, the UE no longer reports event A5.
Figure 4-4 Entering condition of event A5

All parameters (other than thresholds) for event A5 are the same as those for event A4. For details, see
Table 4-10 and Table 4-12.
For event A5 that triggers inter-frequency handover, Thresh1 is the same as the event A2 threshold for
coverage-based inter-frequency handover and Thresh2 is the same as the event A4 threshold for
coverage-based inter-frequency handover. Table 4-13 describes threshold parameters.
Table 4-13 Thresh1 for event A5

Threshol Parameter ID Parameter Description


d
Paramete
r

Interfreq InterFreqHoGroup.InterFreqHoA2ThdRS This parameter is set for each QCI.


A2 RSRP RP The
threshold IntraRatHoComm.InterFreqHoA1A2TrigQu
an parameter determines which threshold is
Interfreq InterFreqHoGroup.InterFreqHoA2ThdRS to be used.
A2 RSRQ RQ
threshold
Table 4-14 Thresh2 for event A5
Threshol Parameter ID Threshold Value Parameter Description
d
Paramete
r

Coverage InterFreqHoGroup.InterFre When the triggering threshold The threshold parameter is


Based qHoA4ThdRSRP is RSRP, Thresh2 equals set for each QCI.
Interfreq InterFreqHoGroup.InterFreq The threshold offset
RSRP HoA4ThdRSRP plus parameter is set for each
threshold EutranInterNFreq.IfHoThdR inter-frequency neighboring
srpOffset. frequency.
The
Coverage InterFreqHoGroup.InterFre When the triggering threshold IntraRatHoComm.InterFre
Based qHoA4ThdRSRQ is RSRQ, Thresh2 equals qHoA4RprtQuan parameter
Interfrq InterFreqHoGroup.InterFreq determines which threshold
RSRQ HoA4ThdRSRQ. is to be used.
threshold

4.1.4 Blind Handover


Triggering and Stopping of Blind Handover

The eNodeB can deliver a measurement configuration related to event A2 for blind handover if the signal
quality of the serving cell deteriorates to a specified level but the UE has not yet been handed over. The
eNodeB also delivers the measurement configuration related to event A1 to stop blind handover when the
signal quality in the serving cell does not further deteriorate.
 The eNodeB records the reports of event A2 for blind handover during handover preparation and
handles them if the handover preparation fails.
 If the eNodeB receives a report of event A1 used to stop a blind handover from the UE before
blind handover is completed, the eNodeB stops performing blind handover.
If the EmcInterFreqBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is
selected, the eNodeB performs a blind handover procedure for coverage-based inter-frequency
handover. The eNodeB selects an inter-frequency target cell when the UE sends a report of event A2 for
blind handover.
Table 4-15 lists parameters related to events A1 and A2 for blind handover.
Table 4-15 Parameters related to events A1 and A2

Variabl Paramet Parameter ID Parameter Description


es in er Name
the
Formul
a

Ms - - Ms is the measurement result of the


serving cell. The measurement result type
is specified by the
InterRatHoComm.InterRatHoA1A2Trig
Quan parameter.

Hys InterRA InterRatHoCommGroup.InterRatHoA This parameter is set for each QCI.


T A1A2 1A2Hyst
Variabl Paramet Parameter ID Parameter Description
es in er Name
the
Formul
a

hysteres
is

Thresh BlindHO CellHoParaCfg.BlindHoA1A2ThdRsr This is a cell-level parameter.


A1A2 p The
RSRP InterRatHoComm.InterRatHoA1A2Trig
trigger Quan parameter determines which
threshol threshold is to be used.
d
 If
InterRatHoComm.InterRatHoA1A2
BlindHO CellHoParaCfg.BlindHoA1A2ThdRsr TrigQuan is set to BOTH, two A2
A1A2 q events are reported, with one being
RSRQ RSRP-based and the other RSRQ-
trigger based. When the entering condition
threshol for either of the A2 events is met,
d the UE reports the A2 event.
 If
InterRatHoComm.InterRatHoA1A2
TrigQuan is set to RSRP or RSRQ,
the UE reports an A2 event only
when the entering condition for the
related A2 event is met.

Table 4-16 lists other parameters related to the event A1/A2 report for blind handover.
Table 4-16 Other parameters related to the event A1/A2 report

Parameter Name Parameter ID Parameter Description

InterRAT A1A2 InterRatHoCommGroup.InterRatHoA1A2TimeToTrig This parameter is set for


time to trigger each QCI.

InterRat A1A2 InterRatHoComm.InterRatHoA1A2TrigQuan This is a common


measurement parameter for inter-RAT
trigger quantity handover and is set for
each eNodeB.
This parameter specifies
the Ms type and
triggering quantity for
events A1 and A2.

Event A2 for blind handover can be used to trigger both coverage-based inter-frequency blind redirection
and inter-RAT blind handover. Coverage-based inter-frequency blind redirection and inter-RAT blind
handover share the same thresholds related to event A2. The working principles for event A2 for
coverage-based inter-frequency blind redirection and inter-RAT blind handover are similar. For details
about event A2 for inter-RAT blind handover, see Inter-RAT Mobility Management in Connected Mode.
For details about event A2 for inter-RAT blind handover, see Inter-RAT Mobility Management in
Connected Mode.
Target Selection

Figure 4-5 shows the target selection process for blind handover. The related parameters are described
as follows:
 In coverage-based inter-frequency blind handover, target cells must be the neighboring cells
whose EutranInterFreqNCell.BlindHoPriority is set to a value within the range of 1 to 16. A
larger value indicates a higher priority.
 The eNodeB preferentially selects a frequency with the highest priority for the redirection. The
frequency priority is specified by the EutranInterNFreq.ConnFreqPriority parameter. A larger
value indicates a higher priority. When this parameter is set to 0, the frequency is not selected
for redirection.
Figure 4-5 Target selection process for blind handover

For a coverage-based blind handover, E-UTRAN TDD and E-UTRAN FDD are considered as two
independent systems, and the CnOperatorHoCfg.FirstRatPri and CnOperatorHoCfg.SecondRatPri
parameters specify the priorities of E-UTRAN TDD and E-UTRAN FDD.
 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, blind handover are performed
only to frequencies of the network specified the CnOperatorHoCfg.FirstRatPri parameter.

4.2 Service-based Inter-Frequency Handover


This section describes the basic feature LBFD-00201805 Service Based Inter-frequency Handover. For
details about the engineering guidelines for this feature, see 7.3 Service-based Inter-Frequency
Handover. Service-based inter-frequency handover can be enabled by the
ServiceBasedInterFreqHoSwitch switch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter.
Service-based inter-frequency handovers are applicable to two neighboring E-UTRAN frequencies that
cover the same area. Based on the QCIs of the services that are running on a UE, the eNodeB can divert
the UE to an appropriate co-coverage E-UTRAN frequency by means of a service-based inter-frequency
handover to implement service steering.
Table 4-17 describes events for triggering/stopping measurement and handover during a service-based
inter-frequency handover. Blind handover is not applied to service-based inter-frequency handover.
Table 4-17 Events for triggering/stopping measurement and handover during a service-based inter-
frequency handover

Procedure Triggering Events Stopping Events

Inter-frequency UE service with the highest-priority The UE service is terminated.


measurement QCI is allowed to be handed over to
a frequency on a different band.

Inter-frequency Event A4 -
handover

4.2.1 Triggering and Stopping of Inter-Frequency Measurement


To implement service-based inter-frequency handovers, operators need to configure service-based inter-
frequency handover policies. Since the services of each operator are classified by QCIs, each QCI can be
associated with a service-based inter-frequency handover policy so that the frequency specified by the
policy preferentially carries the services with this QCI. There must be at least one neighboring cell
working on this frequency. The eNodeB triggers a service-based inter-frequency handover for a UE
based on the highest-priority QCI of the services running on the UE.
1. Set the service-based inter-frequency handover policy (specified by the
ServiceIfHoCfgGroup.InterFreqHoState parameter) for a frequency (specified by the
ServiceIfDlEarfcnGrp.DlEarfcn parameter) to PERMIT_HO.
2. Associate a QCI (specified by CnOperatorStandardQci.Qci or ExtendedQci.ExtendedQci)
with the service-based inter-frequency handover policy.
3. If the UE performs services with this QCI and the QCI is with the highest priority, the eNodeB
delivers a measurement configuration for event A4. Then the UE measures the frequency
(specified by the ServiceIfDlEarfcnGrp.DlEarfcn parameter).
4. The UE stops service-based inter-frequency measurement when the UE stops services with
this QCI.
The QCI priority is specified by the CellStandardQci.QciPriorityForHo parameter. A smaller value
indicates a higher priority.
If the configurations for QCI priorities are the same, handover parameter selection is based on the QCI
priority specified in 3GPP. For details, see section 6.1.7 "Standardized QoS characteristics" in 3GPP TS
23.203 V10.3.0.

4.2.2 Inter-Frequency Measurement


Before delivering the measurement configuration related to event A4, the eNodeB checks whether the
measurement gap has been activated. If the measurement gap has been activated and includes other
measurement gap, the eNodeB does not perform any handling. Otherwise, the eNodeB activates the
measurement gap.
If a UE has performed gap-assisted measurements for a service-based inter-frequency handover for a
period of time (internally set to 3s) but fails to trigger such a handover, the eNodeB will stop the service-
based inter-frequency measurements.
Parameters in the measurement configuration for service-based inter-frequency measurement are the
same as those for coverage-based inter-RAT measurement. For details, see 4.1.2 Inter-Frequency
Measurement.

4.2.3 Inter-Frequency Handover Triggering


Service-based inter-frequency handovers can be triggered by event A4. Working principles of event A4
for triggering service-based inter-frequency handovers are the same as those of event A4 for triggering
coverage-based inter-frequency handovers. For details, see 4.1.3.2 Event A4.
All parameters (other than thresholds) for event A4 that triggers service-based inter-frequency handovers
are the same as those for event A4 that triggers coverage-based inter-frequency handovers. Table 4-18
lists the thresholds related to event A4.
Table 4-18 Thresholds related to event A4 that triggers service-based inter-frequency handovers

Paramet Parameter ID Parameter Description


er Name

Load InterFreqHoGroup.InterFreqLoadBasedHoA4 This parameter is set for each QCI.


Based ThdRSRP The
Interfreq IntraRatHoComm.InterFreqHoA4TrigQ
RSRP uan parameter determines which
threshol threshold is to be used.
d
 If
IntraRatHoComm.InterFreqHoA4T
Load InterFreqHoGroup.InterFreqLoadBasedHoA4 rigQuan is set to BOTH, two A4
Based ThdRSRQ events are delivered, with one being
Interfreq RSRP-based and the other RSRQ-
RSRQ based. When the entering condition
threshol for either of the A4 events is met,
d the UE reports the A4 event. An
inter-frequency handover is
triggered only when the triggering
conditions for both of the A4 events
are met.
 When
IntraRatHoComm.InterFreqHoA4T
rigQuan is set to RSRP or RSRQ,
the eNodeB delivers a measurement
configuration related to event A4 for
which the triggering quantity is
RSRP or RSRQ, respectively.
The
IntraRatHoComm.InterFreqHoA4RprtQ
uan parameter determines the reporting
quantity to be included in the
measurement reports after event A4 is
triggered.
 When
IntraRatHoComm.InterFreqHoA4R
prtQuan is set to BOTH, two A4
events are reported, with one being
RSRP-based and the other RSRQ-
based.
 When
IntraRatHoComm.InterFreqHoA4R
prtQuan is set to
SAME_AS_TRIG_QUAN(Same as
Trig Quan), service-based
measurement report type for event
Paramet Parameter ID Parameter Description
er Name

A4 is the same as the measurement


triggering quantity.

The event A4 triggering quantity for service-based inter-frequency handovers is determined by the
IntraRatHoComm.InterFreqHoA4TrigQuan parameter. Other parameters related to the event A4 report
for service-based inter-frequency measurement are the same as the parameters related to the event A4
report for coverage-based inter-frequency measurement. For details, see 4.1.3.2 Event A4.
When a service-based inter-frequency handover is triggered, the eNodeB checks the handover history
information of the UE. If the target frequency for the handover is the same as the frequency of the cell
where the UE is previously located, the handover is not performed to prevent ping-pong handovers.

4.3 Distance-based Inter-Frequency Handover


This section describes the basic feature LBFD-00201804 Distance Based Inter-frequency Handover. For
details about the engineering guidelines for this feature, see 7.4 Distance-based Inter-Frequency
Handover. The CellAlgoSwitch.DistBasedHoSwitch parameter specifies whether to enable distance-
based inter-frequency handover.
Distance-based inter-frequency handover can be triggered only when the
DistBasedHO.DistBasedMeasObjType parameter is set to EUTRAN.
Distance-based inter-frequency handover applies in high- and low-band hybrid networks where cells on
the low band cover a larger area than cells on the high band and overshoot coverage occurs on the high
band while neighbor relations are missing on the low band.
As shown in Figure 4-6, the 1800 MHz band F1 is used to cover the urban area and the 800 MHz band
F2 is used to cover the suburban area. If there are only a few buildings along the border between the
urban area and the suburban area, 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.
As there are restrictions on number of cells between two neighboring cells, Cell D cannot be configured
as a neighboring cell of Cell A. However, because of overshoot coverage of Cell A, the UE cannot trigger
coverage-based inter-frequency handover in Cell B and Cell C. When the UE reaches Cell D and moves
out of the overshoot coverage area, service drops will occur because of the missing neighbor relationship.
The deviation in the estimated distance between the UE and eNodeB is about 100 to 150 meters.

NOTE:
Obtaining the distance between the UE and the eNodeB is dependent on the uplink timing advance (TA).
The eNodeB measures the TA of a UE and sends the TA value to the UE through a timing advance
command. The TA accuracy is 16 Ts.
Ts is the minimum time unit at the physical layer in LTE. The formula for calculating Ts is as follows: Ts =
1/(15000 x 2048)s = 32.55 ns.
The formula for calculating the distance in a distance-based inter-frequency handover is as follows: 16
Ts/2 x Radio transmitting speed. That is, 16 x 32.55 ns /2 x 3 x 10^8 m/s = 78.12 m.
Figure 4-6 Distance-based inter-frequency handover

Table 4-19 lists the triggering and stopping conditions for triggering/stopping measurement and handover
during a distance-based inter-frequency handover. Blind handover is not applied to distance-based inter-
frequency handover.
Table 4-19 Events for triggering/stopping measurement and handover during a distance-based inter-
frequency handover

Procedure Triggering Events Stopping Events

Inter-frequency Distance between the UE and Distance between the UE and eNodeB
measurement eNodeB exceeds the specified falls below the specified threshold.
threshold.

Inter-frequency Event A4 -
handover

4.3.1 Triggering and Stopping of Inter-Frequency Measurement


Distance-based inter-frequency handovers are triggered by the eNodeB based on the distance between
the eNodeB and the UE.
The eNodeB keeps monitoring the distance to all UEs. Upon detecting that the measured distance to a
UE exceeds the threshold specified by the DistBasedHO.DistBasedHOThd parameter for 10 seconds
(which is a fixed value), the eNodeB delivers the measurement configuration for event A4 to the UE.
While the measurements for a distance-based inter-frequency handover are being taken, if the eNodeB
detects that the reported TA value does not meet DistBasedHO.DistBasedHOThd for 10 seconds, the
measurements are immediately stopped.

4.3.2 Inter-Frequency Measurement


Before delivering the measurement configuration related to event A4, the eNodeB checks whether the
measurement gap has been activated. If the measurement gap has been activated and includes other
measurement gap, the eNodeB does not perform any handling. Otherwise, the eNodeB activates the
measurement gap.
If a UE has performed gap-assisted measurements for a distance-based inter-frequency handover for a
period of time (internally set to 3s) but fails to trigger such a handover, the eNodeB releases the
measurement gaps for distance-based inter-frequency handovers to stop the measurements.
Parameters in the measurement configuration for distance-based inter-frequency measurement are the
same as those for coverage-based inter-frequency measurement. For details, see 4.1.2 Inter-Frequency
Measurement.
4.3.3 Inter-Frequency Handover Triggering
Distance-based inter-frequency handovers can be triggered by event A4. Working principles of event A4
for triggering distance-based inter-frequency handovers are the same as those of event A4 for triggering
coverage-based inter-frequency handovers. For details, see 4.1.3.2 Event A4.
All parameters (other than thresholds) for event A4 that triggers distance-based inter-frequency
handovers are the same as those for event A4 that triggers coverage-based inter-frequency handovers.
Table 4-20 lists the thresholds related to event A4.
Table 4-20 Thresholds related to event A4 that triggers distance-based inter-frequency handovers

Parameter Parameter ID Parameter Description


Name

CoverageBas InterFreqHoGroup.InterFreqHoA4Thd This parameter is set for each QCI.


ed Interfreq RSRP The
RSRP IntraRatHoComm.InterFreqHoA4TrigQua
threshold n parameter determines which threshold is
to be used.
CoverageBas InterFreqHoGroup.InterFreqHoA4Thd  If
ed Interfreq RSRQ IntraRatHoComm.InterFreqHoA4Trig
RSRQ Quan is set to BOTH, two A4 events
threshold are delivered, with one being RSRP-
based and the other RSRQ-based.
When the entering condition for either
of the A4 events is met, the UE reports
the A4 event. An inter-frequency
handover is triggered only when the
triggering conditions for both of the A4
events are met.
 When
IntraRatHoComm.InterFreqHoA4Trig
Quan is set to RSRP or RSRQ, the
eNodeB delivers a measurement
configuration related to event A4 for
which the triggering quantity is RSRP
or RSRQ, respectively.
The
IntraRatHoComm.InterFreqHoA4RprtQua
n parameter determines the reporting
quantity to be included in the measurement
reports after event A4 is triggered.
 When
IntraRatHoComm.InterFreqHoA4Rpr
tQuan is set to BOTH, two A4 events
are reported, with one being RSRP-
based and the other RSRQ-based.
 When
IntraRatHoComm.InterFreqHoA4Rpr
tQuan is set to
SAME_AS_TRIG_QUAN(Same as
Trig Quan), distance-based
measurement report type for event A4
Parameter Parameter ID Parameter Description
Name

is the same as the measurement


triggering quantity.

The event A4 triggering quantity for distance-based inter-frequency handovers is determined by the
IntraRatHoComm.InterFreqHoA4TrigQuan parameters. Other parameters related to the event A4
report for distance-based inter-frequency measurement are the same as the parameters related to the
event A4 report for coverage-based inter-frequency measurement. For details, see 4.1.3.2 Event A4.

4.4 UL-Quality-based Inter-Frequency Handover


This section describes UL-quality-based inter-frequency handover. For details about the engineering
guidelines for this feature, see 7.5 UL-quality-based Inter-Frequency Handover. UL-quality-based inter-
frequency handover can be enabled by the UlQualityInterFreqHoSwitch switch under the
ENodeBAlgoSwitch.HoAlgoSwitch parameter.
A UL-quality-based inter-frequency handover prevents service drops caused by deteriorated UL quality.
Table 4-21 describes events for triggering and stopping measurement and blind handover during an UL-
quality-based inter-frequency handover.
Table 4-21 Events for triggering/stopping measurement and blind handover during an UL-quality-based
inter-frequency handover

Procedure Subprocedure Triggering Events Stopping Events

Measurement Inter-frequency UL quality becomes worse. UL quality becomes better.


measurement

Inter-frequency Event A4 -
handover

Blind - UL quality becomes further -


Handover worse, but the eNodeB does
not receive any event A4
reports.

4.4.1 Triggering and Stopping of Inter-Frequency Measurement


UL-quality-based inter-frequency handovers are triggered based on the UL signal quality. When the UL
signal quality is unsatisfactory, call drops may occur if handovers are not performed in time. The eNodeB
checks the uplink signal quality. If the eNodeB finds that the uplink signal quality is poor, it delivers the
measurement configuration for event A4.
When a UE detects that the uplink quality becomes better, the eNodeB stops UL-quality-based inter-
frequency measurements.

4.4.2 Inter-Frequency Measurement


Before delivering the measurement configuration related to event A4, the eNodeB checks whether the
measurement gap has been activated. If the measurement gap has been activated and includes other
measurement gap, the eNodeB does not perform any handling. Otherwise, the eNodeB activates the
measurement gap.
If a UE has performed gap-assisted measurements for a UL-quality-based inter-frequency handover for a
period of time (internally set to 3s) but fails to trigger such a handover, the eNodeB releases the
measurement gaps for UL-quality-based inter-frequency handovers to stop the measurements.
Parameters in the measurement configuration for UL-quality-based inter-frequency measurement are the
same as those for coverage-based inter-frequency measurement. For details, see 4.1.2 Inter-Frequency
Measurement.

4.4.3 Inter-Frequency Handover Triggering


UL-quality-based inter-frequency handovers can be triggered by event A4. Working principles of event A4
for triggering UL-quality-based inter-frequency handovers are the same as those of event A4 for triggering
coverage-based inter-frequency handovers. For details, see 4.1.3.2 Event A4.
Parameters related to event A4 that triggers UL-quality-based inter-frequency handovers are the same as
those related to event A4 that triggers distance-based inter-frequency handovers. For details, see 4.3.3
Inter-Frequency Handover Triggering.

4.4.4 Blind Handover


Triggering of Blind Handover

If the UL quality for the UE further deteriorates but the eNodeB does not receive an event A4
measurement report, the eNodeB considers that service drops may occur due to the poor UL quality. In
this situation, the eNodeB performs blind handover for the UE.
Target Selection

The target selection process of UL-quality-based inter-frequency blind handover is the same as that of
coverage-based inter-frequency blind handover. For details, see 4.1.4 Blind Handover.

4.5 Frequency-Priority-based Inter-Frequency Handover


This section describes frequency-priority-based inter-frequency handover. For details about the
engineering guidelines for this function, see 7.6 Frequency-Priority-based Inter-Frequency Handover.
Frequency-priority-based inter-frequency handover can be enabled by the FreqPriorIFHOSwitch switch
under the CellAlgoSwitch.FreqPriorityHoSwitch parameter.
When cells on a low band (for example, 900 MHz) and a high band (for example, 1800 MHz) have the
same coverage, a frequency-priority-based inter-frequency handover can be performed to preferentially
carry services in the high band while sparing the low band for continuous coverage. Figure 4-7 shows
frequency-priority-based inter-frequency handover.
Figure 4-7 Frequency-Priority-based Inter-Frequency Handover

Table 4-22 lists the triggering and stopping conditions for triggering/stopping measurement and handover
during a distance-based inter-frequency handover.
Table 4-22 Events for triggering/stopping measurement and blind handover during a frequency-priority-
based inter-frequency handover

Procedure Subprocedure Triggering Events Stopping Events

Measurement Inter-frequency Event A1 Event A2


measurement

Inter-frequency Event A4 -
handover

Blind - Event A1 Event A2


handover

Events A1 and A2 are respectively used for triggering and stopping measurement and blind handover.
When the eNodeB receives an event A1 report, blind handover or inter-frequency measurement is
triggered as follows:
 Blind handover is triggered if it has been enabled by turning on the FreqPriorIFBlindHOSwitch
switch under the CellAlgoSwitch.FreqPriorityHoSwitch.
 If blind handover is not enabled, the eNodeB delivers a measurement configuration for event A4
to trigger inter-frequency measurement.

4.5.1 Triggering and Stopping of Inter-Frequency Measurement


During frequency-priority-based inter-frequency measurement, the sequence that the measurement
configuration of events A1 and A2 for triggering and stopping inter-frequency measurements is sent is
controlled by the ReduceInvalidA1A2EventRptSigSwitch switch under the
ENodeBAlgoSwitch.HoSignalingOptSwitch parameter.
 If the switch is turned on, the eNodeB sends measurement configuration for event A1 when the
UE sets up an RRC connection, and sends measurement configuration for event A2 after it
receives an event A1 from the UE. This reduces the reporting of invalid event A2.
 If the switch is turned off, the eNodeB sends measurement configuration for both event A2 and
event A1 when the UE sets up an RRC connection.
Triggering of Inter-Frequency Measurement

When frequency-priority-based inter-frequency handover is enabled, the eNodeB delivers event A1 for
frequency-priority-based inter-frequency measurement.
Working principles of event A1 for triggering frequency-priority-based inter-frequency measurement is the
same as those of event A1 for triggering coverage-based inter-frequency measurement. Parameters
(other than those for thresholds and triggering quantity) in the measurement configuration for frequency-
priority-based inter-frequency measurement are the same as those for coverage-based inter-frequency
measurement. For details, see 4.1.1.2 Event A1. Parameters for thresholds and triggering quantity are
listed in Table 4-23.
Table 4-23 Parameters for event A1 for triggering frequency-priority-based inter-frequency measurement

Parameter Parameter ID of the Threshold Parameter Description


Name of
the
Threshold

Freq InterFreqHoGroup.FreqPriInterFreqHoA This parameter is set for each QCI.


Priority 1ThdRsrp The
Based IntraRatHoComm.FreqPriInterFreqHoA1Tri
Interfreq gQuan parameter determines which threshold
A1 RSRP is to be used.
threshold
 If
IntraRatHoComm.FreqPriInterFreqHo
Freq InterFreqHoGroup.FreqPriInterFreqHoA A1TrigQuan is set to BOTH, two A1
Priority 1ThdRsrq events are reported, with one being
Based RSRP-based and the other RSRQ-
Interfreq based. When the entering condition for
A1 RSRQ either of the A1 events is met, the UE
threshold reports the A1 event.
 If
IntraRatHoComm.FreqPriInterFreqHo
A1TrigQuan is set to RSRP or RSRQ,
the UE reports an A1 event only when
the entering condition for the related A1
event is met.

A1A2 IntraRatHoComm.FreqPriInterFreqHoA This is a common eNodeB-level parameter


Measurem 1TrigQuan used for intra-RAT handovers.
ent trigger This parameter specifies the Ms type and
quantity of triggering quantity for events A1 and A2.
Freq
Priority
Stopping of Inter-Frequency Measurement

Inter-frequency measurement stops when the eNodeB receives an event A2 report for frequency-priority-
based inter-frequency measurement.
Working principles of event A2 for stopping frequency-priority-based inter-frequency measurement is the
same as those of event A2 for stopping coverage-based inter-frequency measurement. Parameters (other
than those for thresholds and triggering quantity) in the measurement configuration for frequency-priority-
based inter-frequency measurement are the same as those for coverage-based inter-frequency
measurement. For details, see 4.1.1.1 Event A2. Parameters for thresholds and triggering quantity are
listed in Table 4-24.
Table 4-24 Parameters for event A2 for stopping frequency-priority-based inter-frequency measurement

Parameter Parameter ID of the Threshold Parameter Description


Name of
the
Threshold

Freq InterFreqHoGroup.FreqPriInterFreqHoA This parameter is set for each QCI.


Priority 2ThdRsrp The
Based IntraRatHoComm.FreqPriInterFreqHoA1Tri
Interfreq gQuan parameter determines which threshold
A2 RSRP is to be used.
threshold
 If
IntraRatHoComm.FreqPriInterFreqHo
Freq InterFreqHoGroup.FreqPriInterFreqHoA A1TrigQuan is set to BOTH, two A2
Priority 2ThdRsrq events are reported, with one being
Based RSRP-based and the other RSRQ-
Interfreq based. When the entering condition for
A2 RSRQ either of the A2 events is met, the UE
threshold reports the A2 event.
 If
IntraRatHoComm.FreqPriInterFreqHo
A1TrigQuan is set to RSRP or RSRQ,
the UE reports an A2 event only when
the entering condition for the related A2
event is met.

A1A2 IntraRatHoComm.FreqPriInterFreqHoA This is a common eNodeB-level parameter


Measurem 1TrigQuan used for intra-RAT handovers.
ent trigger This parameter specifies the Ms type and
quantity of triggering quantity for events A1 and A2.
Freq The triggering quantity for event A2 for
Priority frequency-priority-based inter-frequency
measurement is the same as that for event A1
for frequency-priority-based inter-frequency
measurement.

4.5.2 Inter-Frequency Measurement


Before delivering the measurement configuration related to event A4, the eNodeB checks whether the
measurement gap has been activated. If the measurement gap has been activated and includes other
measurement gap, the eNodeB does not perform any handling. Otherwise, the eNodeB activates the
measurement gap.
If a UE has performed gap-assisted measurements for a frequency-priority-based inter-frequency
handover for a period of time (internally set to 3s) but fails to trigger such a handover, the eNodeB will
stop the frequency-priority-based inter-frequency measurements.
Parameters (other than parameter for frequency selection) in the measurement configuration for
frequency-priority-based inter-frequency measurement are the same as those for coverage-based inter-
frequency measurement. For details, see 4.1.2 Inter-Frequency Measurement.
The EutranInterNFreq.FreqPriBasedHoMeasFlag parameter specifies the measurement flag for a
frequency for frequency-priority-based inter-frequency measurement.
 If EutranInterNFreq.FreqPriBasedHoMeasFlag is set to ENABLE(Enable), the frequency is a
target frequency for frequency-priority-based inter-frequency measurement. If the number of
target frequencies to be measured exceeds the maximum number allowed by 3GPP
specifications, the eNodeB contains random frequencies in the measurement configuration.
 If EutranInterNFreq.FreqPriBasedHoMeasFlag is set to DISABLE(Disable), the selected inter-
frequency neighboring cells must have a frequency priority ranging from 17 to 32. Only the
frequencies of these cells are measured. The frequency priority is set by the
EutranInterFreqNCell.BlindHoPriority parameter. If the number of target frequencies to be
measured exceeds the maximum number allowed by 3GPP specifications, the eNodeB sorts the
frequencies according to the value of the EutranInterFreqNCell.BlindHoPriority parameter
and selects the frequencies of the neighboring cells with high priorities.

4.5.3 Inter-Frequency Handover Triggering


Frequency-priority-based inter-frequency handovers can be triggered by event A4. Working principles of
event A4 for triggering frequency-priority-based inter-frequency handovers are the same as those of
event A4 for triggering coverage-based inter-frequency handovers. For details, see 4.1.3.2 Event A4.
Parameters related to event A4 that triggers frequency-priority-based inter-frequency handovers are the
same as those related to event A4 that triggers service-based inter-frequency handovers. For details, see
4.2.3 Inter-Frequency Handover Triggering.

4.5.4 Blind Handover


Triggering and Stopping of Blind Handover

Blind handover is triggered when the eNodeB receives an event A1 report from a UE and blind handover
is enabled. Blind handover is enabled when the FreqPriorIFBlindHOSwitch switch under the
CellAlgoSwitch.FreqPriorityHoSwitch parameter is turned on.

Target Selection

The target selection process of frequency-priority-based inter-frequency blind handover is the same as
that of coverage-based inter-frequency blind handover. For details, see 4.1.4 Blind Handover.
In frequency-priority-based blind handover, the target inter-frequency neighboring cell must have a blind-
handover priority ranging from 17 to 32. The frequency priority is set by the
EutranInterFreqNCell.BlindHoPriority parameter.
If an inter-frequency neighboring cell is not configured with a blind-handover priority, the subsequent
processing depends on the setting of the EutranInterNFreq.FreqPriBasedHoMeasFlag parameter.
 If EutranInterNFreq.FreqPriBasedHoMeasFlag is set to ENABLE(Enable), measurement is
performed. The frequency of the neighboring cell is a target frequency. If the number of target
frequencies to be measured exceeds the maximum number allowed by 3GPP specifications, the
eNodeB contains random frequencies in the measurement configuration.
 If EutranInterNFreq.FreqPriBasedHoMeasFlag is set to DISABLE(Disable), measurement is
not performed.

4.6 Handover Decision


In the handover decision phase, the eNodeB checks the cells in the candidate cell list and determines
whether a handover needs to be initiated and, if so, to which cell the UE is to be handed over.
The candidate cell list varies according to handover type.
 The candidate cell list generated for coverage-based inter-frequency handovers is controlled by
the CellAlgoSwitch.CovBasedInterFreqHoMode parameter.
 When this parameter is set to HANDOVERIMMEDIATELY, the candidate cell list is
generated based on measurement report.
 When this parameter is set to BASEDONSIGNALSTRENGTH or
BASEDONFREQPRIORITY, the candidate cell list is generated as shown in Figure 4-8.
 For other inter-frequency handovers, the candidate cell list is generated based on the
measurement report.
Figure 4-8 Candidate cell list generation procedure
As shown in Figure 4-8, the IntraRatHoComm.CovBasedIfHoWaitingTimer parameter specifies the
timer for candidate cell list generation during coverage-based inter-frequency handovers.
 When the timer is set to 0, handover decision is started after candidate cell list is generated
according to measurement report.
 After the timer expires, handover decision based on frequency priority performs handover attempt
according to the frequency priority sequence specified in the measurement report. If there are
frequencies with the same priority, a random frequency is selected for handover attempt.
If all the cells fail after the handover attempt is complete, the eNodeB waits until the UE sends the next
measurement report. After receiving the measurement report, the eNodeB no longer starts the timer to
wait but performs handover decision immediately.

4.6.1 Target Decision


In the handover decision phase, the eNodeB filters cells in the candidate cell list based on cell load
status. Then, the eNodeB determines whether a handover needs to be initiated and, if so, the handover
sequence.
Basic Handover Decision

The eNodeB excludes the following cells from the neighboring cell list:
 Blacklisted neighboring cells
 Neighboring cells with a handover prohibition flag
 Neighboring cells that have a different PLMN from the serving cell
 These cells will not be filtered out if the inter-PLMN handover switch is turned on. Inter-
PLMN handover is controlled by the InterPlmnHoSwitch switch under the
ENodeBAlgoSwitch.HoAlgoSwitch parameter.
 If the equivalent PLMN switch is turned on, the inter-PLMN list can include the EPLMN list.
EPlmnSwitch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies the
equivalent PLMN switch.
 Neighboring cells in the areas indicated by the IE Handover Restriction List in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME
When a UE is performing VoIP services, cells that forbid VoIP handovers are also filtered.
VoipHoControlSwitch under the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to
enable this function.
 When this switch is turned on, cells specified by EutranVoipHoBlkList are filtered when a UE is
performing VoIP services.
 When this switch is turned off, cells specified by EutranVoipHoBlkList are not filtered when a
UE is performing VoIP services.

Load Decision

If the handover target cell is an intra-site cell, the source cell checks the load status of the target cells. If
the load of any operator's target cell is high, the cell is not selected as the candidate cell. For details
about the load status of the target cell, see MLB.
When InterFreqMlbSwitch under the CellAlgoSwitch.MlbAlgoSwitch parameter is turned on, whether
inter-frequency handover based on frequency priority is triggered is determined by cell load status.
ReduceInvalidFreqPriHoSwitch under the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter
specifies whether to enable this function.
 When this switch is turned on, inter-frequency handover based on frequency priority is not
triggered if the load of the target cell is high.
 When this switch is turned off, whether to trigger inter-frequency handover based on frequency
priority is not related to the load of the target cell.
The source eNodeB applies a penalty mechanism on UEs that performs unnecessary handovers when its
handover admission fails. This prevents a large number of initiated handover attempts from affecting the
target eNodeB, especially when the eNodeB has insufficient resources. Unnecessary handovers include:
 Service-based inter-frequency handover
 Frequency-Priority-based Inter-Frequency Handover
 SPID-based inter-frequency handover back to the HPLMN. For details, see Flexible User
Steering

Sequence Decision

The eNodeB then sends a handover request to the target cell at the top of the filtered candidate cell list. If
the handover request fails, the eNodeB sends the handover request to the next target cell, as described
in Table 4-25.
Table 4-25 Sequence of handover requests to be sent by the eNodeB

Candidate Cell List Sequence of Handover Requests


Generated by

Measurement A handover request is sent to the cell with the best signal quality.
If the measurement results are the same, the eNodeB assigns the intra-
eNodeB cell a higher priority to avoid signaling and data forwarding
required in an inter-eNodeB handover.
In handover based on frequency priority, a random cell is selected as the
target cell when the cell measurement results are the same.

Blind Handover A handover request is sent to a cell or frequency that has the highest
priority. If multiple cells have the highest priority, the eNodeB randomly
selects a cell for blind handover.
In handover based on frequency priority, a random cell is selected as the
target cell when the priorities are the same.

If the handover request fails in all candidate cells:


 For a measurement procedure, the eNodeB waits until the UE sends the next measurement
report.
 For a blind handover procedure, the eNodeB finishes the handover procedure.

4.6.2 Admission Decision


MultiQciHoExecOptSwitch under the ENodeBAlgoSwitch.HoSignalingOptSwitch parameter indicates
whether the handover decision is triggered based on the admission result of all QCIs in SPID-based
handovers to HPLMN and frequency-priority-based handovers.
 If this switch is turned on, the handover decision is triggered only when all QCIs are successfully
admitted.
 If this switch is turned off, the handover decision is triggered when any of the QCIs is successfully
admitted.
The eNodeB provides the ENodeBAlgoSwitch.EutranVoipSupportSwitch parameter, which prevents
UEs performing VoIP services from being handed over to an eNodeB that does not support VoIP.
 When this switch is turned on, VoIP services are allowed in the E-UTRAN cell, which means that
the establishment, handover in, admission, and reestablishment of VoIP services are allowed.
 When this switch is turned off, VoIP services are not allowed in the E-UTRAN cell, which means
that the establishment, handover in, admission, and reestablishment of VoIP services are not
allowed.
Assume that eNodeB1 cells are neighboring cells of eNodeB2. It is recommended that eNodeB1 cells be
added to the EutranVoipHoBlkList parameter of eNodeB2 if eNodeB1 forbids VoIP service handover in.
Otherwise, the handover will fail due to handover penalty.

4.7 Handover Execution


The eNodeB selects either a handover procedure or a redirection procedure.
 The eNodeB selects the handover procedure for all measurement-based handovers.
 The procedure selection for blind handover is as follows:
 The eNodeB selects the redirection procedure for coverage-based and UL-quality-based
blind handover. Redirections are performed only on non-VoIP UEs, not on VoIP UEs.
 The eNodeB selects the handover procedure for frequency-priority-based blind handover.
 When the FDD and TDD cells of the same eNodeB are served by different MMEs, only the
redirection procedure can be selected for coverage-based inter-frequency handover between
FDD and TDD cells.
This is because there is a possibility that the MME cannot be changed during a handover in
such a case. For details about such MME configurations, see S1-Flex.
Other execution mechanisms for inter-frequency handover are the same as those for intra-frequency
handover. For details, see 3.4 Handover Execution.

4.8 Signaling Procedures


Signaling procedures for inter-frequency handovers are the same as those for intra-frequency handovers.
For details, see 3.5 Signaling Procedures.

5 Related Features
5.1 Coverage-based Intra-Frequency Handover
Prerequisite Features

None
Mutually Exclusive Features

None

Impacted Features

None

5.2 Coverage-based Inter-Frequency Handover


Prerequisite Features
None

Mutually Exclusive Features

Coverage-based inter-frequency handovers support inter-frequency blind redirection in the


absence of neighbor relationship configurations. To use inter-frequency blind redirection in the
absence of neighbor relationship configurations, ensure that RAN sharing information about
inter-frequency frequencies is configured.

The parameters for RAN sharing and LOFD-001112 MOCN Flexible Priority Based Camping
are mutually exclusive. Therefore, if inter-frequency blind redirection in the absence of neighbor
relationship configurations is used, LOFD-001112 MOCN Flexible Priority Based Camping
cannot be used.

Impacted Features

If LBFD-00201802 Coverage Based Inter-frequency Handover is used, you are advised not to
use other inter-frequency handover features for multiple different frequencies. Otherwise, ping-
pong handovers between frequencies may occur due to differences in triggering conditions for
different types of inter-frequency handovers.

If other inter-frequency handover features need to be used for multiple frequencies with LBFD-
00201802 Coverage Based Inter-frequency Handover enabled, event A4 thresholds for those
inter-frequency handover features must be properly set. 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 immediately after a UE is handed over to the target frequency.

5.3 Service-based Inter-Frequency Handover


Prerequisite Features

None
Mutually Exclusive Features

None
Impacted Features

Good practice is to avoid enabling multiple inter-frequency handover types (excluding coverage-based
inter-frequency handovers) on multiple E-UTRAN frequencies. If multiple inter-frequency handover types
are enabled on multiple E-UTRAN frequencies, ping-pong handovers may occur due to the diverse
triggering conditions of different inter-frequency handover types.
If coverage-based inter-frequency handovers are enabled on multiple E-UTRAN frequencies and another
inter-frequency handover type is to be enabled on one frequency (for example, F1), ensure that the
threshold for event A4 for this inter-frequency handover type is greater than the threshold for inter-
frequency measurement event A2. To further elaborate on the two thresholds mentioned here, the
threshold for event A4 is configured on the eNodeB providing F1, while the threshold for inter-frequency
measurement event A2 is configured on the eNodeB providing a neighboring E-UTRAN frequency of F1.
5.4 Distance-based Inter-Frequency Handover
Prerequisite Features

None

Mutually Exclusive Features

None

Impacted Features

If LBFD-00201804 Distance Based Inter-frequency Handover is used, you are advised not to use
other inter-frequency handover features for multiple different frequencies. Otherwise, ping-pong
handovers between frequencies may occur due to differences in triggering conditions for
different types of inter-frequency handovers.

If other inter-frequency handover features need to be used for multiple frequencies with LBFD-
00201804 Distance Based Inter-frequency Handover enabled, event A4 thresholds for those
inter-frequency handover features must be properly set. 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 immediately after a UE is handed over to the target frequency.

6 Network Impact
6.1 Coverage-based Intra-Frequency Handover
System Capacity

No impact.

Network Performance

Coverage-based intra-frequency handovers reduce interference from intra-frequency neighboring cells on


an intra-frequency network, decreasing the call drop rate.

6.2 Coverage-based Inter-Frequency Handover


System Capacity

No impact.

Network Performance

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 call drop rate.

6.3 Service-based Inter-Frequency Handover


System Capacity
No impact.

Network Performance

No impact.

6.4 Distance-based Inter-Frequency Handover


System Capacity

No impact.

Network Performance

No impact.

7 Engineering Guidelines
This chapter provides engineering guidelines for mobility management in connection mode.

7.1 Coverage-based Intra-Frequency Handover

7.1.1 When to Use Coverage-based Intra-Frequency Handover

Mobility management is fundamental to service continuity. Coverage-based intra-frequency


handovers are used by default. You are advised to keep this type of handover enabled.

7.1.2 Required Information

Coverage-based intra-frequency handover is a basic feature and has no special requirements for
the network and UE.

To ensure the performance of coverage-based intra-frequency handover, verify that the E-


UTRAN provides effective and continuous coverage. If there are coverage holes in the E-
UTRAN, coverage-based intra-frequency handover may not achieve satisfactory performance.

In addition, collect information about intra-frequency neighbor relationships to ensure the


integrity of such relationships.

7.1.3 Requirements
Operating Environment

Coverage-based intra-frequency handovers have no requirements for operating environment.

Transmission Networking

Coverage-based intra-frequency handovers have no requirements for transmission networking.


License

Coverage-based intra-frequency handovers have no requirements for licenses.

7.1.4 Data Preparation


This section describes the data that you need to collect for setting parameters. Required data is data that
you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature
deployment scenario.
There are three types of data sources:

 Network plan (negotiation required): parameter values planned by the operator and negotiated
with the EPC or peer transmission equipment
 Network plan (negotiation not required): parameter values planned and set by the operator
 User-defined: parameter values set by users

Required Data

This section describes the data required for configuring neighbor relationships with intra-frequency E-
UTRAN cells.
The following table describes the parameters that must be set in the EutranExternalCell managed object
(MO) to configure an external E-UTRAN cell. This MO is required only if an intra-frequency neighboring
cell is under a different eNodeB from the local cell.

Parameter Parameter ID Data Setting Notes


Name Source
Mobile EutranExternalCell.Mcc Network This parameter specifies the mobile country
country plan code (MCC) of the home eNodeB of the
code (negotiation external E-UTRAN cell. If this external cell
required) works in RAN sharing mode, set this
parameter to the MCC of the primary
operator.

This parameter references the


corresponding parameter defined in the
CnOperator MO on the peer eNodeB.
Mobile EutranExternalCell.Mnc Network This parameter specifies the mobile network
network plan code (MNC) of the home eNodeB of the
code (negotiation external E-UTRAN cell. If this external cell
required) works in RAN sharing mode, set this
parameter to the MNC of the primary
operator.

This parameter references the


corresponding parameter defined in the
CnOperator MO on the peer eNodeB.
eNodeB ID EutranExternalCell.eNodeBId Network This parameter specifies the ID of the home
plan eNodeB of the external E-UTRAN cell. It
(negotiation uniquely identifies the eNodeB within the
required) entire network.
Parameter Parameter ID Data Setting Notes
Name Source
This parameter references the
corresponding parameter defined in the
eNodeBFunction MO on the peer eNodeB.
Cell ID EutranExternalCell.CellId Network This parameter specifies the ID of the
plan external E-UTRAN cell. It uniquely identifies
(negotiation a cell within an eNodeB.
required)
This parameter references the
corresponding parameter defined in the Cell
MO on the peer eNodeB.
Downlink EutranExternalCell.DlEarfcn Network This parameter specifies the DL EARFCN of
EARFCN plan the external E-UTRAN cell.
(negotiation
required)
Physical EutranExternalCell.PhyCellId Network This parameter references the
cell ID plan corresponding parameter defined in the Cell
(negotiation MO on the peer eNodeB.
required)
Tracking EutranExternalCell.Tac Network This parameter references the
area code plan corresponding parameter defined in the
(negotiation CnOperatorTa MO on the peer eNodeB.
required)

(Optional, required only if the home eNodeB of the external E-UTRAN cell works in RAN sharing with
common carrier mode) The following table describes the parameters that must be set in the
EutranExternalCellPlmn MO to configure an additional PLMN ID (representing a secondary operator) for
an external E-UTRAN cell.

Parameter Parameter ID Data Setting Notes


Name Source
Mobile EutranExternalCellPlmn.Mcc Network This parameter specifies the MCC of
country plan the primary operator.
code (negotiation
required) This parameter references the
corresponding parameter defined in
the CnOperator MO on the peer
eNodeB.
Mobile EutranExternalCellPlmn.Mnc Network This parameter specifies the MNC of
network plan the primary operator.
code (negotiation
required) This parameter references the
corresponding parameter defined in
the CnOperator MO on the peer
eNodeB.
eNodeB ID EutranExternalCellPlmn.eNodeBId Network This parameter specifies the ID of the
plan home eNodeB of the external E-
Parameter Parameter ID Data Setting Notes
Name Source
(negotiation UTRAN cell. It uniquely identifies the
required) eNodeB within the entire network.

This parameter references the


corresponding parameter defined in
the eNodeBFunction MO on the peer
eNodeB.
Cell ID EutranExternalCellPlmn.CellId Network This parameter specifies the ID of the
plan external E-UTRAN cell. It uniquely
(negotiation identifies a cell within an eNodeB.
required)
This parameter references the
corresponding parameter defined in
the Cell MO on the peer eNodeB.
Share EutranExternalCellPlmn.ShareMcc Network This parameter specifies the MCC of
mobile plan the secondary operator for the
country (negotiation external E-UTRAN cell.
code required)
This parameter references the
corresponding parameter defined in
the CnOperator MO on the peer
eNodeB.
Share EutranExternalCellPlmn.ShareMnc Network This parameter specifies the MNC of
mobile plan the secondary operator for the
network (negotiation external E-UTRAN cell.
code required)
This parameter references the
corresponding parameter defined in
the CnOperator MO on the peer
eNodeB.

(Optional, required only if the neighboring E-UTRAN cell is a multi-band cell) The following table
describes the parameters that must be set in the EutranExternalCellBand MO to configure the
secondary band for an external E-UTRAN cell.

Parameter Parameter ID Data Source Setting Notes


Name
Mobile EutranExternalCellBand.Mcc Network plan This parameter specifies the MCC of
country (negotiation the home eNodeB of the neighboring
code required) cell. If this neighboring cell works in
RAN sharing mode, set this
parameter to the MCC of the primary
operator.

This parameter references the


corresponding parameter defined in
the eNodeB MO on the peer
eNodeB.
Parameter Parameter ID Data Source Setting Notes
Name
Mobile EutranExternalCellBand.Mnc Network plan This parameter specifies the MNC of
network (negotiation the home eNodeB of the neighboring
code required) cell. If this neighboring cell works in
RAN sharing mode, set this
parameter to the MNC of the primary
operator.

This parameter references the


corresponding parameter defined in
the eNodeB MO on the peer
eNodeB.
eNodeB ID EutranExternalCellBand.eNodeBId Network plan This parameter specifies the ID of
(negotiation the eNodeB of the neighboring cell. It
required) uniquely identifies the eNodeB within
the entire network.

This parameter references the


corresponding parameter defined in
the eNodeB MO on the peer
eNodeB.
Cell ID EutranExternalCellBand.CellId Network plan This parameter specifies the ID of
(negotiation the neighboring E-UTRAN cell. It
required) uniquely identifies a cell within an
eNodeB.

This parameter references the


corresponding parameter defined in
the Cell MO on the peer eNodeB.
Frequency EutranExternalCellBand.FreqBand Network plan This parameter specifies other
band (negotiation frequency band in which the cell
required) operates.

Set this parameter to the


primary/secondary band identifier of
the multi-band inter-frequency
neighboring cell.

The following table describes the parameters that must be set in the EutranIntraFreqNCell MO to
configure the neighbor relationship with an intra-frequency E-UTRAN cell.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell EutranIntraFreqNCell.LocalCellId Network Ensure that this parameter has been set
ID plan in a Cell MO.
(negotiation
not
required)
Parameter Parameter ID Data Setting Notes
Name Source
Mobile EutranIntraFreqNCell.Mcc Network This parameter specifies the MCC of the
country plan home eNodeB of the intra-frequency
code (negotiation neighboring E-UTRAN cell. If this
required) neighboring E-UTRAN cell works in
RAN sharing mode, set this parameter
to the MCC of the primary operator.

This parameter references the


corresponding parameter defined in the
CnOperator MO on the peer eNodeB.
Mobile EutranIntraFreqNCell.Mnc Network This parameter specifies the MNC of the
network plan home eNodeB of the neighboring E-
code (negotiation UTRAN cell. If this neighboring E-
required) UTRAN cell works in RAN sharing
mode, set this parameter to the MNC of
the primary operator.

This parameter references the


corresponding parameter defined in the
CnOperator MO on the peer eNodeB.
eNodeB ID EutranIntraFreqNCell.eNodeBId Network This parameter specifies the ID of the
plan home eNodeB of the neighboring E-
(negotiation UTRAN cell. It uniquely identifies the
required) eNodeB within the entire network.

This parameter references the


corresponding parameter defined in the
eNodeBFunction MO on the peer
eNodeB.
Cell ID EutranIntraFreqNCell.CellId Network This parameter specifies the ID of the
plan neighboring E-UTRAN cell. It uniquely
(negotiation identifies a cell within an eNodeB.
required)
This parameter references the
corresponding parameter defined in the
Cell MO on the peer eNodeB.
Scenario-specific Data

The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to configure
coverage-based intra-frequency handover.

Paramet Parameter ID Data Setting Notes


er Name Source
Handove ENodeBAlgoSwitch.HoAlgoS Network To enable coverage-based intra-frequency
r Algo witch plan handover, select the
switch (negotiati IntraFreqCoverHoSwitch(IntraFreqCoverHo
on not Switch) check box under this parameter.
required)
By default, the intra-frequency handover parameter group Group0 is used for services with all QCIs. To
apply different intra-frequency handover parameter groups to services based on the QCI, the
corresponding parameter group ID must be changed.
The following table describes the parameter that must be set in the CellStandardQci MO to configure
parameter groups for services with standard QCIs.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell CellStandardQci.LocalCellId Network Ensure that this parameter has
ID plan been set in a Cell MO based on
(negotiation the network plan.
not
required)
QoS Class CellStandardQci.Qci Network This parameter specifies the index
Indication plan of the standard QCI for which the
(negotiation parameter group is configured.
not
required)
Intrafreq CellStandardQci.IntraFreqHoGroupId Network This parameter specifies the index
handover plan of the intra-frequency handover
group ID (negotiation parameter group.
not
required)
QCI CellStandardQci.QciPriorityForHo Network This parameter specifies priority
Priority For plan mapping the QCI.
Handover (negotiation
not
required)

The following table describes the parameter that must be set in the CellExtendedQci MO to configure
parameter groups for services with extended QCIs.

Parameter Parameter ID Data Setting Notes


Name Source
Extended CellExtendedQci.ExtendedQci Network Set this parameter to the index of
QCI plan the extended QCI for which the
(negotiation parameter group is configured.
not
required)
Local cell CellExtendedQci.LocalCellId Network Ensure that this parameter has
ID plan been set in a Cell MO based on the
(negotiation network plan.
not
required)
Intrafreq CellExtendedQci.IntraFreqHoGroupId Network Set this parameter to the index of
handover plan the corresponding parameter
group ID (negotiation group.
not
required)
The following table describes the parameter that must be set in the EutranIntraFreqNCell MO to
configure measurement priorities for intra-frequency neighboring cells.

Parameter Parameter ID Data Setting Notes


Name Source
Cell EutranIntraFreqNCell.CellMeasPriority Network Neighboring cells with optimal
Measure plan network coverage are easy to be
Priority (negotiation measured and quickly meet
not handover conditions. You are
required) advised to set this parameter to
HIGH_PRIORITY(High Priority)
for such neighboring cells and set
this parameter to
LOW_PRIORITY(Low Priority)
for other neighboring cells.

7.1.5 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of related parameters in a summary data file, which also contains other data for the new
eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file,
depending on the following conditions:

 Related managed objects (MOs) are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
 Some related MOs are not contained in a scenario-specific summary data file. In this situation,
customize a summary data file to include the MOs before you can set the parameters.

Related MOs and parameters in each scenario are listed as follows:

Table 7-1 Parameters related to coverage-based intra-frequency handovers

MO Sheet in the Summary Parameter Group Remarks


Data File
ENodeBAlgoSwitch User-defined sheet Handover Algo switch A list-type
sheet is
ENodeBAlgoSwitch is recommended.
recommended.
EutranExternalCell User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCell is Cell identity, Downlink EARFCN, recommended.
recommended. Uplink EARFCN indicator, Uplink
EARFCN, Physical cell identity,
Tracking area code, Cell name
EutranExternalCellPlmn User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
Cell identity, Share mobile recommended.
MO Sheet in the Summary Parameter Group Remarks
Data File
EutranExternalCellPlmn country code, Share mobile
is recommended. network code
EutranIntraFreqNCell User-defined sheet Local cell identity, Mobile A list-type
country code, Mobile network sheet is
EutranIntraFreqNCell is code, eNodeB identity, Cell recommended.
recommended. identity, Cell individual
offset(dB), Cell offset(dB), No
handover indicator, No remove
indicator, ANR flag, Local cell
name, Neighbour cell name
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a
single procedure. The procedure is as follows:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary
data file for batch reconfiguration.

NOTE:

For context-sensitive help on a current task in the client, press F1.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
3. In the summary data file, set the parameters in the MOs listed in Table 7-1 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The
procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration
window.
2. In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using MML Commands

1. Run the MOD ENODEBALGOSWITCH command, and select the IntraFreqCoverHoSwitch


option under the Handover Algo switch parameter.
2. Run the following commands to add neighbor relationships with intra-frequency E-UTRAN
cells:
a. (Optional) ADD EUTRANEXTERNALCELL, which is required when the intra-frequency
neighboring cell is under a different eNodeB from the local cell.
b. (Optional) ADD EUTRANEXTERNALCELLPLMN, which is used to configure the PLMN
list for an external E-UTRAN cell when the neighboring E-UTRAN cell works in RAN
sharing mode.
c. ADD EUTRANINTRAFREQNCELL

MML Command Examples

//Activating coverage-based intra-frequency handover


MOD ENODEBALGOSWITCH: HoAlgoSwitch=IntraFreqCoverHoSwitch-1;
//Adding intra-frequency E-UTRAN neighboring cells
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=0,
DlEarfcn=2350, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1; ADD
EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=0,
ShareMcc="460", ShareMnc="22"; ADD EUTRANINTRAFREQNCELL: LocalCellId=0,
Mcc="460", Mnc="20", eNodeBId=123, CellId=0;

7.1.6 Activation Observation


The observation procedure is as follows:

1. Trace messages over the Uu interface on the U2000 client after UEs access the network.
Check the RRC_CONN_RECFG message. If the message contains measurement
configuration of event A3 for a coverage-based intra-frequency handover, you can infer that
coverage-based intra-frequency handover has been activated.
2. Trace messages over the Uu interface while the UE is moving towards an intra-frequency
neighboring cell. Check the RRC_CONN_RECFG message, which is a handover command. If
the message contains target cell access information, you can infer that coverage-based intra-
frequency handover has been triggered.

7.1.7 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs.
This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single
procedure. The procedure for feature deactivation is similar to that for feature activation described in
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify related
parameters described below.

Table 7-2 Parameters related to coverage-based intra-frequency handovers

MO Sheet in the Parameter Group Setting Notes


Summary Data File
ENodeBAlgoSwitch ENodeBAlgoSwitch Handover Algo Clear the
switch IntraFreqCoverHoSwitch
check box.
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in each scenario for a single eNodeB. For detailed instructions,
see Using the CME to Perform Single Configuration for feature activation.
Using MML Commands

To deactivate coverage-based intra-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command and clear the IntraFreqCoverHoSwitch option under the Handover
Algo switch parameter.

MML Command Examples

//Deactivating coverage-based intra-frequency handover


MOD ENODEBALGOSWITCH: HoAlgoSwitch=IntraFreqCoverHoSwitch-0;
7.1.8 Performance Monitoring
Coverage-based intra-frequency handovers ensure service continuity when users move around. How well
these handovers serve this purpose reflects their performance. After activating coverage-based intra-
frequency handover, check the following counters to monitor and evaluate handover performance:

 Success rate of X2 and S1 handovers. The interface-specific statistics helps locating the
handover failure cause. The related counters are:
 Intra-eNB Intra-frequency Handover Out Success Rate
 Inter-eNB Intra-frequency Handover Out Success Rate
 Abnormal Release Rate indicating the service drop rate

If the handover success rate is low and the service drop rate is high, the performance of coverage-based
intra-frequency handover is poor. In this situation, check the related parameter settings and network
coverage.

7.1.9 Parameter Optimization


Intra-Frequency Handover Parameters

Intra-frequency handover parameters are contained in the IntraFreqHoGroup MO.

Paramet Parameter ID Data Setting Notes


er Name Source
Local cell IntraFreqHoGroup.LocalCellId Network Ensure that this parameter has been
ID plan set in a Cell MO based on the
(negotiati network plan.
on not
required)
Intrafreq IntraFreqHoGroup.IntraFreqHoGroupId Network This parameter specifies the ID of
handover plan the parameter group related to intra-
group ID (negotiati frequency handovers.
on not
required) If you want to set different intra-
frequency handover parameters for
services with a specific QCI, you
must create a parameter group, and
reference the parameter group ID to
the corresponding QCI.
Intrafreq IntraFreqHoGroup.IntraFreqHoA3Hyst Network This parameter specifies the
handover plan hysteresis for event A3 associated
hysteresi (negotiati with intra-frequency handover. A
s on not larger hysteresis value causes a
required) lower probability of triggering event
A3, affecting user experience. A
smaller hysteresis value causes a
higher probability of triggering event
A3 but also a higher probability of
incorrect handover decisions and
ping-pong handovers.

It is recommended that the default


value be used. You can suitably
Paramet Parameter ID Data Setting Notes
er Name Source
decrease the value in areas with
slight signal fluctuation.
Intrafreq IntraFreqHoGroup.IntraFreqHoA3Offse Network This parameter specifies the offset
handover t plan for event A3 associated with intra-
offset (negotiati frequency handover. A larger value
on not causes a lower probability of
required) triggering event A3. A smaller value
causes a higher probability.

It is recommended that you adjust


the parameter value based on the
application scenario. Increase the
parameter value if premature intra-
frequency handovers occur.
Decrease the parameter value if
delayed intra-frequency handovers
occur.
Intrafreq IntraFreqHoGroup.IntraFreqHoA3Time Network This parameter specifies the time-to-
handover ToTrig plan trigger for event A3 associated with
time to (negotiati intra-frequency handover. Setting an
trigger on not appropriate triggering delay
required) effectively reduces the average
number of handovers and the
number of wrong handovers,
preventing unnecessary handovers.
The average number of handovers
has a negative correlation with the
time-to-trigger. At the same time, an
excessively large value of the time-
to-trigger results in a high risk of
service drops.

It is recommended that you adjust


the parameter value with
IntraFreqHoGroup.IntraFreqHoA3
Offset based on the application
scenario. Increase the parameter
value if premature intra-frequency
handovers occur. Decrease the
parameter value if delayed intra-
frequency handovers occur.
Cell Individual Offset for Intra-Frequency Neighboring Cells

The following table provides the parameter that must be set in the EutranIntraFreqNCell MO to adjust
cell individual offset for the intra-frequency neighboring cells.
Parameter Parameter ID Data Setting Notes
Name Source
Cell EutranIntraFreqNCell.CellIndividualOffset Network This parameter affects the
individual plan probability of reporting intra-
offset (negotiation frequency measurement
not events. A larger parameter
required) value indicates a higher
probability.

If there are multiple target cells


for the intra-frequency
handover and related
handover parameters need to
be optimized, you can
decrease this parameter value
for a neighboring cell to reduce
the possibility of the handover
to the neighboring cell, or you
can increase this parameter
value for a neighboring cell to
raise the possibility of the
handover to the neighboring
cell.
Intra-RAT Intra-Frequency Handover Parameters

Intra-RAT intra-frequency handover parameters are contained in the IntraRatHoComm MO.

Parameter Parameter ID Data Setting Notes


Name Source
Max report IntraRatHoComm.IntraRatHoMaxRprtCell Network This parameter specifies
cell number plan the maximum number of
(negotiation cells to be included in each
not intra-frequency or inter-
required) frequency measurement
report after the
corresponding event is
triggered. Set this
parameter to a larger value
if the eNodeB requires
more candidate cells to
make a handover decision.
An excessively large value,
however, causes a waste
of air interface resources.

It is recommended that the


default value be used.
Measurement IntraRatHoComm.IntraRatHoRprtAmount Network This parameter specifies
report plan the number of intra-
amount (negotiation frequency or inter-
not frequency periodical
required) measurement reports to be
Parameter Parameter ID Data Setting Notes
Name Source
sent after the
corresponding event is
triggered. Set this
parameter to a larger value
if the eNodeB requires
more measurement reports
to make a handover
decision. An excessively
large parameter value,
however, causes a waste
of air interface resources.

It is recommended that the


default value be used.
A3 IntraRatHoComm.IntraFreqHoA3TrigQuan Network This parameter specifies
measurement plan the triggering quantity for
trigger (negotiation event A3 associated with
quantity not intra-frequency handover.
required) The parameter can be
either RSRP or RSRQ.
RSRQ-based
measurement results
reflect signal quality in real
time, whereas RSRP-
based measurement
results are stable with little
signal fluctuation.

It is recommended that the


default value be used.
A3 IntraRatHoComm.IntraFreqHoA3RprtQuan Network This parameter specifies
measurement plan the reporting quantity to be
report (negotiation included in the
quantity not measurement reports after
required) event A3 associated with
intra-frequency handover is
triggered. The parameter
can be either the same as
the triggering quantity for
this event A3 or both RSRP
and RSRQ. That is, the
measurement results of the
serving cell and
neighboring cells can be
RSRP-based, RSRQ-
based, or both in A3-
related measurement
reports.
Parameter Parameter ID Data Setting Notes
Name Source
It is recommended that the
default value be used.
Intrafreq IntraRatHoComm.IntraFreqHoRprtInterval Network This parameter specifies
measurement plan the interval between the
report interval (negotiation reports that are triggered
not by event A3 associated
required) with intra-frequency
handover. A smaller value
causes more measurement
reports and greater
consumption of air interface
resources, but a higher
probability of triggering
handovers. An excessively
large parameter value,
however, causes a long
delay in retries and a low
handover success rate.

It is recommended that the


default value be used.

7.1.10 Troubleshooting
Fault description

An eNodeB may not initiate a handover procedure upon receipt of an event A3 measurement report.
Fault handling

When this problem occurs, perform the following steps to determine whether it has occurred because the
target cell has not been configured as a neighboring cell:

1. Check the messages over the Uu interface and locate the PCI of the neighboring cell in the
measurement report.
2. Run the LST EUTRANEXTERNALCELL command to list all external E-UTRAN cells of the
eNodeB, run the LST CELL command to list all local cells of the eNodeB, and check these lists
for the cell whose PCI equals the PCI found in the previous step.
 If this cell can be found, go to 4.
 If this cell cannot be found, the target cell has not been configured as an external cell. To
solve this problem, go to 3.
3. Find out the CGI of the cell whose PCI equals the PCI found in 1 in the command output in 2.
Then, run the ADD EUTRANINTRAFREQNCELL command to add the CGI to the
EutranIntraFreqNCell MO.
4. Find out the CGI of the cell whose PCI equals the PCI found in 1 in the command output in 2.
Then, run the ADD EUTRANEXTERNALCELL and ADD EUTRANINTRAFREQNCELL
commands to add the CGI to the EutranExternalCell and EutranIntraFreqNCell MOs,
respectively.

7.2 Coverage-based Inter-Frequency Handover


7.2.1 When to Use Coverage-based Inter-Frequency Handover
Mobility management is fundamental to service continuity. Coverage-based inter-frequency handovers
are used by default. You are advised to keep this type of handover enabled.
If the live network does not require inter-frequency networking, you can disable coverage-based inter-
frequency handover.

7.2.2 Required Information


If blind handovers or redirections are required to implement inter-frequency handovers, collect the
information about the neighboring cells to which blind handovers or redirections will be allowed as well as
their blind-handover priorities.
The information to be collected before deploying coverage-based inter-frequency handover includes the
information to be collected before deploying coverage-based intra-frequency handover.
Collect UE information to determine whether the eNodeB needs to handle UEs that report an abnormal
frequency-supporting capability.
In addition to the information described in 7.1.2 Required Information, collect the information about the
coverage at the inter-frequency handover area. This information serves as a basis for setting the
thresholds used to trigger events A1, A2, and A4.
The event A2 threshold for coverage-based inter-frequency handover and the event A2 threshold for
coverage-based inter-RAT handover can be separately set. If users expect coverage-based inter-
frequency handover to be triggered earlier than coverage-based inter-RAT handover, the event A2
threshold for coverage-based inter-frequency handover must be set to a value greater than the event A2
threshold for coverage-based inter-RAT handover.

7.2.3 Requirements
Operating Environment

None
Transmission Networking

None

License

None

7.2.4 Data Preparation


This section describes the data that you need to collect for setting parameters. Required data is data that
you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature
deployment scenario.
There are three types of data sources:

 Network plan (negotiation required): parameter values planned by the operator and negotiated
with the EPC or peer transmission equipment
 Network plan (negotiation not required): parameter values planned and set by the operator
 User-defined: parameter values set by users

Required Data
This section describes the data required for configuring neighbor relationships with inter-frequency E-
UTRAN cells.
The following table describes the parameters that must be set in the EutranInterNFreq MO to configure a
neighboring E-UTRAN frequency.

Parameter Parameter ID Data Source Setting Notes


Name
Local cell ID EutranInterNFreq.LocalCellId Network plan Ensure that this parameter
(negotiation not has been set in a Cell MO.
required)
Downlink EutranInterNFreq.DlEarfcn Network plan This parameter specifies the
EARFCN (negotiation not DL EARFCN of the cells on
required) the neighboring E-UTRAN
frequency.

This parameter references


the corresponding parameter
defined in the Cell MO on the
peer eNodeB.
Measurement EutranInterNFreq.MeasBandWidth Network plan This parameter references
bandwidth (negotiation not the corresponding parameter
required) defined in the Cell MO on the
peer eNodeB.

NOTE:

If an inter-frequency neighboring cell is a multi-band cell, the EARFCN in the secondary band also needs
to be added in the EutranInterNFreq MO. For details about the relationship between the band and
EARFCN, see section 5.7.3 in 3GPP TS 36.101 V10.2.1 (2011-04).

For details about multi-band cells, see Cell Management.

(Optional, required only if an inter-frequency neighboring cell is under a different eNodeB from the local
cell) Collect the parameters in the EutranExternalCell MO used to configure an external E-UTRAN cell.
For details about the key parameters in this MO, see 7.1.4 Data Preparation.
(Optional, required only if a neighboring E-UTRAN cell is a multi-band cell) Collect the parameters in the
EutranExternalCellBand MO used to configure the secondary band for an external E-UTRAN cell. For
details about the key parameters in this MO, see 7.1.4 Data Preparation.
(Optional, required only if the home eNodeB of the external E-UTRAN cell works in RAN sharing with
common carrier mode and multiple operators share the same external E-UTRAN cell) Collect the
parameters in the EutranExternalCellPlmn MO used to configure an additional PLMN ID for an external
E-UTRAN cell. For details about the key parameters in this MO, see 7.1.4 Data Preparation.
The following table describes the parameters that must be set in the EutranInterFreqNCell MO to
configure the neighbor relationship with an inter-frequency E-UTRAN cell.
Parameter Parameter ID Data Setting Notes
Name Source
Local cell EutranInterFreqNCell.LocalCellId Network Ensure that this parameter has been
ID plan set in a Cell MO.
(negotiation
not
required)
Mobile EutranInterFreqNCell.Mcc Network This parameter specifies the MCC of
country plan the home eNodeB of the inter-
code (negotiation frequency neighboring E-UTRAN cell. If
required) this neighboring E-UTRAN cell works in
RAN sharing mode, set this parameter
to the MCC of the primary operator.

This parameter references the


corresponding parameter defined in the
eNodeB MO on the peer eNodeB.
Mobile EutranInterFreqNCell.Mnc Network This parameter specifies the MNC of
network plan the home eNodeB of the neighboring E-
code (negotiation UTRAN cell. If this neighboring E-
required) UTRAN cell works in RAN sharing
mode, set this parameter to the MNC of
the primary operator.

This parameter references the


corresponding parameter defined in the
eNodeB MO on the peer eNodeB.
eNodeB ID EutranInterFreqNCell.eNodeBId Network This parameter specifies the ID of the
plan home eNodeB of the neighboring E-
(negotiation UTRAN cell. It uniquely identifies the
required) eNodeB within the entire network.

This parameter references the


corresponding parameter defined in the
eNodeB MO on the peer eNodeB.
Cell ID EutranInterFreqNCell.CellId Network This parameter specifies the ID of the
plan neighboring E-UTRAN cell. It uniquely
(negotiation identifies a cell within an eNodeB.
required)
This parameter references the
corresponding parameter defined in the
Cell MO on the peer eNodeB.
Scenario-specific Data

The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to configure
coverage-based inter-frequency handover.
Paramet Parameter ID Data Setting Notes
er Name Source
Handove ENodeBAlgoSwitch.HoAlgoSwit Network To enable coverage-based inter-frequency
r Algo ch plan handover, select the
switch (negotia InterFreqCoverHoSwitch(InterFreqCoverH
tion not oSwitch) check box under this parameter.
required
) To reduce the number of signaling messages
over the air interface, clear the
EmcBlindHoA1Switch(EmcBlindHoA1Swit
ch) check box under this parameter.

To reduce the call drop rate, select the


EmcInterFreqBlindHoSwitch(EmcInterFreq
BlindHoSwitch) check box under this
parameter.
Compati ENodeBAlgoSwitch.Compatibili Network It is recommended that the
bility tyCtrlSwitch plan UECapRprtAbnormalCtrlSwitch option of
Control (negotia this parameter be selected when the UE
Switch tion not reporting capability is abnormal.
required
)

By default, the inter-frequency handover parameter group Group0 is used for services with all QCIs. To
apply different inter-frequency handover parameter groups to services based on the QCI, the
corresponding parameter group ID must be changed.
The following table describes the parameters that must be set in the CellStandardQci MO to configure
inter-frequency handover parameter groups for services with standard QCIs.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell CellStandardQci.LocalCellId Network Ensure that this parameter has
ID plan been set in a Cell MO based on the
(negotiation network plan.
not
required)
QoS Class CellStandardQci.Qci Network This parameter specifies the
Indication plan standard QCI for which the
(negotiation parameter group is configured.
not
required)
Interfreq CellStandardQci.InterFreqHoGroupId Network This parameter specifies the index
handover plan of the inter-frequency handover
group ID (negotiation parameter group.
not
required)
QCI CellStandardQci.QciPriorityForHo Network This parameter specifies priority
Priority For plan mapping the QCI.
Handover (negotiation
Parameter Parameter ID Data Setting Notes
Name Source
not
required)

The following table describes the parameters that must be set in the CellExtendedQci MO to configure
inter-frequency handover parameter groups for services with extended QCIs.

Parameter Parameter ID Data Source Setting Notes


Name
Extended CellExtendedQci.ExtendedQci Network plan Set this parameter to the index of
QCI (negotiation the extended QCI for which the
not required) parameter group is configured.
Local cell CellExtendedQci.LocalCellId Network plan Ensure that this parameter has
ID (negotiation been set in a Cell MO based on
not required) the network plan.
Interfreq CellExtendedQci.InterFreqHoGroupId Network plan Set this parameter to the index of
handover (negotiation the corresponding parameter
group ID not required) group.

The following table describes the parameters that must be set in the EutranInterFreqNCell MO to
configure blind handover priorities and measurement priorities for inter-frequency neighboring cells.

Parameter Parameter ID Data Setting Notes


Name Source
Blind EutranInterFreqNCell.BlindHoPriority Network If this parameter value is set to 0,
handover plan blind handovers and frequency-
Priority (negotiation priority-based handovers cannot
not be performed. The values 1 to 16
required) indicate blind-handover priorities.
Multiple neighboring cells can be
configured with the same blind-
handover priority. If multiple
neighboring cells have the highest
blind-handover priority, the
eNodeB randomly selects one
from them.

The values 17 to 32 indicate the


priorities for frequency-priority-
based handovers. Set this
parameter (with a value ranging
from 1 to 16) only for those inter-
frequency neighboring cells that
have overlapped coverage with
the serving cell. Set this parameter
to a larger value for a neighboring
cell that has wider overlapped
coverage or a lower frequency.
Parameter Parameter ID Data Setting Notes
Name Source
Set this parameter to 0 for all inter-
frequency neighboring cells if no
inter-frequency neighboring cells
have overlapped coverage with
the serving cell.
Cell EutranInterFreqNCell.CellMeasPriority Network Neighboring cells with optimal
Measure plan network coverage are easy to be
Priority (negotiation measured and quickly meet
not handover conditions. You are
required) advised to set this parameter to
HIGH_PRIORITY(High Priority)
for such neighboring cells and set
this parameter to
LOW_PRIORITY(Low Priority)
for other neighboring cells.

The following table describes the parameters that must be set in the EutranInterNFreq MO to configure
the event for triggering a coverage-based inter-frequency handover and to configure the frequency priority
used during the selection of a target frequency for blind redirection.

Parameter Parameter ID Data Setting Notes


Name Source
Inter-Freq EutranInterNFreq.InterFreqHoEventType Network This parameter specifies the
HO trigger plan event for triggering a coverage-
Event (negotiation based inter-frequency
Type not handover. It can be set to event
required) A3, event A4, or event A5.

 Interference may be strong


in the following scenarios:
overlapping scenario,
inter-frequency with the
same bandwidth, and
inter-frequency in the
same frequency band.
Event A3 is recommended
for coverage-based inter-
frequency handovers in
such scenarios as it
provides better handover
performance.
 When the interference of
two cells is irrelevant, the
absolute threshold of
signal quality is used as
the handover criterion.
Event A4 is recommended
for coverage-based inter-
frequency handovers in
such scenario.
Parameter Parameter ID Data Setting Notes
Name Source

 There is no recommended
scenario for event A5.

Connect EutranInterNFreq.ConnFreqPriority Network Based on the frequency priority


frequency plan specified by this parameter, the
priority (negotiation eNodeB selects a target
not frequency for blind redirection or
required) contains a frequency in a
measurement configuration. A
larger value indicates a higher
priority. If this priority is set to 0
for a frequency, this frequency
is not selected as the target
frequency for a blind redirection.
Multiple frequencies can be
configured with the same
priority. If multiple frequencies
have the highest priority, the
eNodeB randomly selects one
from them.

You are advised to set this


parameter for frequencies with
continuous coverage. If there
are multiple frequencies with
continuous coverage, set this
parameter to a larger value for a
frequency in a lower frequency
band. Set this parameter to 0 for
a frequency with non-
continuous coverage.

(Optional, required for only coverage-based inter-frequency handovers) The following table describes the
parameters that must be set in the CnOperatorHoCfg MO to configure the RSRP threshold offset and
priorities for TDD/FDD frequencies during the selection of the target cells for coverage-based inter-
frequency handovers.

Paramet Parameter ID Data Setting Notes


er Name Source
CN CnOperatorHoCfg.CnOperatorId Network This parameter specifies the ID of an
Operator plan operator and is defined in the
ID (negotiati CnOperator MO.
on not
required) Set this parameter to the ID of the
operator that needs to be configured
with a priority.
First CnOperatorHoCfg.FirstRatPri Network This parameter specifies the priorities of
RAT plan E-UTRAN TDD and E-UTRAN FDD. To
Priority (negotiati prioritize E-UTRAN TDD or E-UTRAN
FDD, set this parameter to
Paramet Parameter ID Data Setting Notes
er Name Source
on not EUTRAN_TDD or EUTRAN_FDD. To
required) give E-UTRAN TDD and E-UTRAN
FDD the same priority, set this
parameter to EUTRAN.

Set this parameter based on the actual


conditions.
Second CnOperatorHoCfg.SecondRatPri Network This parameter specifies the priorities of
RAT plan E-UTRAN TDD and E-UTRAN FDD. To
Priority (negotiati prioritize E-UTRAN TDD or E-UTRAN
on not FDD, set this parameter to
required) EUTRAN_TDD or EUTRAN_FDD. If
FirstRatPri is set to EUTRAN, set
SecondRatPri to NULL, indicating that
E-UTRAN TDD and E-UTRAN FDD are
not prioritized.

Set this parameter based on the actual


conditions.
LTE CnOperatorHoCfg.TddIfHoA2ThdRsr Network This parameter value plus the value of
TDD pOffset plan InterFreqHoGroup.InterFreqHoA2Thd
inter-freq (negotiati Rsrp or
A2 on not InterFreqHoGroup.A3InterFreqHoA2T
Threshol required) hdRsrp is the offset of the RSRP
d RSRP threshold for LTE TDD inter-frequency
Offset measurement event A2.

Set this parameter based on the actual


conditions.
LTE CnOperatorHoCfg.FddIfHoA2ThdRsr Network This parameter value plus the value of
FDD pOffset plan InterFreqHoGroup.InterFreqHoA2Thd
inter-freq (negotiati Rsrp or
A2 on not InterFreqHoGroup.A3InterFreqHoA2T
Threshol required) hdRsrp is the offset of the RSRP
d RSRP threshold for LTE FDD inter-frequency
Offset measurement event A2.

Set this parameter based on the actual


conditions.

(Optional, required for only coverage-based inter-frequency handovers) The following table describes the
parameters that must be set in the EutranNFreqRanShare MO to configure the PLMN information in the
RAN sharing configuration of the neighboring frequencies for enabling inter-frequency blind handovers
when there is no neighboring cells.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell EutranNFreqRanShare.LocalCellId Network Ensure that this parameter has been
ID plan set in a Cell MO.
Parameter Parameter ID Data Setting Notes
Name Source
(negotiation
not
required)
Downlink EutranNFreqRanShare.DlEarfcn Network This parameter specifies the DL
EARFCN plan EARFCN of the cells on the
(negotiation neighboring E-UTRAN frequency. This
not parameter references the
required) corresponding parameter in the Cell
MO on the peer eNodeB.

Add only the frequencies for blind


handovers triggered when there is no
neighboring cells, and ensure that
EARFCN has been set in an
EutranInterNFreq MO.
Mobile EutranNFreqRanShare.Mcc Network This parameter specifies the MCC of
country plan the frequency for blind handovers
code (negotiation triggered when there is no neighboring
required) cells.

This parameter references the


corresponding parameter in the
eNodeB MO on the peer eNodeB.
Mobile EutranNFreqRanShare.Mnc Network This parameter specifies the MNC of
network plan the frequency for blind handovers
code (negotiation triggered when there is no neighboring
required) cells.

This parameter references the


corresponding parameter in the
eNodeB MO on the peer eNodeB.

7.2.5 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of related parameters in a summary data file, which also contains other data for the new
eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file,
depending on the following conditions:

 Related managed objects (MOs) are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
 Some related MOs are not contained in a scenario-specific summary data file. In this situation,
customize a summary data file to include the MOs before you can set the parameters.

Related MOs and parameters in each scenario are listed as follows:


Table 7-3 Coverage-based Inter-Frequency Handover

MO Sheet in the Summary Parameter Group Remarks


Data File
ENodeBAlgoSwitch User-defined sheet Handover Algo switch A list-type sheet is
recommended.
ENodeBAlgoSwitch is
recommended.
EutranExternalCell User-defined sheet Mobile country code, A list-type sheet is
Mobile network code, recommended.
EutranExternalCell is eNodeB identity, Cell
recommended. identity, Downlink
EARFCN, Uplink
EARFCN indicator, Uplink
EARFCN, Physical cell
identity, Tracking area
code, Cell name
EutranExternalCellPlmn User-defined sheet Mobile country code, A list-type sheet is
Mobile network code, recommended.
EutranExternalCellPlmn eNodeB identity, Cell
is recommended. identity, Share mobile
country code, Share
mobile network code
EutranInterNFreq User-defined sheet Local cell identity, A list-type sheet is
Downlink EARFCN, recommended.
EutranInterNFreq is Uplink EARFCN configure
recommended. indicator, Uplink
EARFCN, Inter frequency
cell resel priority
configure indicator, Inter
frequency cell resel
priority, EUTRAN
reselection time(s),
Speed dependent resel
parameter configuring
indicator, Scaling factor of
treseleutra in medium
mobility state, Scaling
factor of treseleutra in
high mobility state,
Measurement
bandwidth(MHz),
Frequency offset(dB),
Inter frequency high
priority threshold(2dB),
Inter frequency lower
priority threshold(2dB),
Minimum required RX
level(2dBm), PMAX
configure indicator,
PMAX(dBm), Neighbor
cell config, Presence
MO Sheet in the Summary Parameter Group Remarks
Data File
antenna port1, Inter-Freq
HO trigger Event Type
EutranInterFreqNCell User-defined sheet Local cell identity, Mobile A list-type sheet is
country code, Mobile recommended.
EutranInterFreqNCell is network code, eNodeB
recommended. identity, Cell identity, Cell
individual offset(dB), Cell
offset(dB), No handover
indicator, No remove
indicator, Blind handover
Priority, ANR flag, Local
cell name, Neighbour cell
name
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a
single procedure. The procedure is as follows:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary
data file for batch reconfiguration.

NOTE:

For context-sensitive help on a current task in the client, press F1.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
3. In the summary data file, set the parameters in the MOs listed in Table 7-3 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The
procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration
window.
2. In area 1 shown in Figure 7-2, select the eNodeB to which the MOs belong.
Figure 7-2 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using MML Commands

1. Run the MOD ENODEBALGOSWITCH command to enable coverage-based inter-frequency


handover.
2. Run the following commands to add neighbor relationships with inter-frequency E-UTRAN
cells:
a. ADD EUTRANINTERNFREQ
b. (Optional) ADD EUTRANEXTERNALCELL, which is required when the inter-frequency
neighboring cell is under a different eNodeB from the local cell.
c. (Optional) ADD EUTRANEXTERNALCELLPLMN, which is used to configure the PLMN
list for an external E-UTRAN cell when the neighboring E-UTRAN cell works in RAN
sharing mode.
d. ADD EUTRANINTERFREQNCELL

MML Command Examples


//Activating coverage-based inter-frequency handover
MOD ENODEBALGOSWITCH: HoAlgoSwitch=InterFreqCoverHoSwitch-1;
//Adding inter-frequency neighboring E-UTRAN cells
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2860,
UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG,
SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG,
QqualMinCfgInd=NOT_CFG;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
DlEarfcn=2860, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1;
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
ShareMcc="460", ShareMnc="22";
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20",
eNodeBId=123, CellId=1;

7.2.6 Activation Observation


This section uses A4-triggered inter-frequency handover as an example. The observation procedure is as
follows:

1. Trace messages over the Uu interface on the U2000 client after UEs access the network.
Check the RRC_CONN_RECFG message. If the message contains measurement
configuration of events A1 and A2 for a coverage-based inter-frequency handover, you can
infer that coverage-based inter-frequency handover has been activated.
2. Trace messages over the Uu interface while the UE is moving towards the cell edge. After the
eNodeB receives an A2-related measurement report from the UE, check the
RRC_CONN_RECFG message that contains the inter-frequency measurement configuration
and A4-related measurement report information.
3. Trace messages over the Uu interface after the UE moves to the cell edge. Check the
RRC_CONN_RECFG message, which is a handover command, after the eNodeB receives an
A4-related measurement report from the UE. If the message contains target cell access
information, you can infer that coverage-based inter-frequency handover has been triggered.

7.2.7 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs.
This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single
procedure. The procedure for feature deactivation is similar to that for feature activation described in
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify related
parameters described below.

Table 7-4 Parameters related to coverage-based inter-frequency handovers

MO Sheet in the Parameter Group Setting Notes


Summary Data File
ENodeBAlgoSwitch ENodeBAlgoSwitch Handover Algo Clear the InterFreqCoverHoSwitch
switch check box.
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in each scenario for a single eNodeB. For detailed instructions,
see Using the CME to Perform Single Configuration for feature activation.
Using MML Commands

To deactivate coverage-based inter-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.

MML Command Examples

//Deactivating coverage-based inter-frequency handover


MOD ENODEBALGOSWITCH: HoAlgoSwitch=InterFreqCoverHoSwitch-0;

7.2.8 Performance Monitoring


Inter-frequency handovers are intended to ensure service continuity when users move around. How well
these handovers serve this purpose reflects their performance. After activating coverage-based inter-
frequency handover, check the following counters to monitor and evaluate handover performance:

 Success rate of X2 and S1 handovers. The interface-specific statistics helps locating the
handover failure cause. The related counters are:
 Intra-eNB Inter-frequency Handover Out Success Rate
 Inter-eNB Inter-frequency Handover Out Success Rate
 Blind Handover Out Success Rate
 Abnormal Release Rate indicating the service drop rate

If the handover success rate is low and the service drop rate is high, the performance of coverage-based
inter-frequency handover is poor. In this situation, check the related parameter settings and network
coverage.
Table 7-5 lists the counters related to coverage-based inter-frequency and inter-mode handover.

Table 7-5 Counters related to coverage-based inter-frequency and inter-mode handover

Counter ID Counter Name Counter Description


1526728933 L.HHO.InterFreq.Coverage.PrepAttOut Number of coverage-based
inter-frequency handover
preparation attempts
1526728934 L.HHO.InterFreq.Coverage.ExecAttOut Number of Coverage-based
Inter-Frequency Handover
Execution Attempts
1526728935 L.HHO.InterFreq.Coverage.ExecSuccOut Number of Successful
Coverage-based Inter-
Frequency Handovers
1526729612 L.HHO.InterFddTdd.Coverage.PrepAttOut Number of coverage-based
inter-duplex-mode
handover preparation
attempts
1526729613 L.HHO.InterFddTdd.Coverage.ExecAttOut Number of coverage-based
inter-duplex-mode
handover execution
attempts
1526729614 L.HHO.InterFddTdd.Coverage.ExecSuccOut Number of successful
coverage-based inter-
Counter ID Counter Name Counter Description
duplex-mode handover
executions

7.2.9 Parameter Optimization


Inter-Frequency Handover Parameters

Inter-frequency handover parameters are contained in the InterFreqHoGroup MO.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell ID InterFreqHoGroup.LocalCellId Network Ensure that this parameter has been
plan set in a Cell MO based on the
(negotiat network plan.
ion not
required)
Interfreq InterFreqHoGroup.InterFreqHoGrou Network This parameter specifies the ID of
handover pId plan the parameter group related to inter-
group ID (negotiat frequency handovers.
ion not
required) If you want to set different inter-
frequency handover parameters for
services with a specific QCI, you
must create a parameter group, and
reference the parameter group ID to
the corresponding QCI.
Interfreq InterFreqHoGroup.InterFreqHoA1A2 Network This parameter specifies the
A1A2 Hyst plan hysteresis for events A1 and A2 for
hysteresis (negotiat inter-frequency measurement. A
ion not larger value causes a lower
required) probability of triggering event A1 or
A2 for inter-frequency measurement.
A smaller value causes a higher
probability.

It is recommended that the default


value be used.
Interfreq InterFreqHoGroup.InterFreqHoA1A2 Network This parameter specifies the time-to-
A1A2 time TimeToTrig plan trigger for events A1 and A2 for inter-
to trigger (negotiat frequency measurement. This time-
ion not to-trigger effectively reduces the
required) number of inter-frequency
measurements to be started,
preventing unnecessary inter-
frequency measurement. The
average number of inter-frequency
measurements to be started has a
negative correlation with the time-to-
trigger. At the same time, an
excessively large value of the time-
Parameter Parameter ID Data Setting Notes
Name Source
to-trigger results in a high risk of
service drops.

It is recommended that the default


value be used.
Interfreq A1 InterFreqHoGroup.InterFreqHoA1Th Network This parameter specifies the RSRP
RSRP dRsrp plan threshold for event A1 associated
threshold (negotiat with inter-frequency measurement. A
ion not larger value causes a lower
required) probability of triggering event A1. A
smaller value causes a higher
probability.

The value of this parameter must be


(usually 4 dB) greater than or equal
to the sum of the value of
InterFreqHoGroup.InterFreqHoA2T
hdRsrp and RSRP threshold offset
for event A2 for inter-frequency
measurement (set in the
CnOperatorHoCfg MO).
Interfreq A1 InterFreqHoGroup.InterFreqHoA1Th Network This parameter specifies the RSRQ
RSRQ dRsrq plan threshold for event A1 for inter-
threshold (negotiat frequency measurement. A larger
ion not value causes a lower probability of
required) triggering event A1. A smaller value
causes a higher probability.

The value of this parameter must be


(usually 2 dB) greater than or equal
to the sum of the value of
InterFreqHoGroup.InterFreqHoA2T
hdRsrq .
Interfreq A2 InterFreqHoGroup.InterFreqHoA2Th Network This parameter specifies the RSRP
RSRP dRsrp plan threshold for event A2 for inter-
threshold (negotiat frequency measurement. A larger
ion not value causes a lower probability of
required) triggering event A2. A smaller value
causes a higher probability.

Set this parameter based on the


actual conditions. Usually, set this
parameter to the RSRP in the area
where the UE throughput in the
serving cell is similar to that in the
neighboring cell.
Interfreq A2 InterFreqHoGroup.InterFreqHoA2Th Network This parameter specifies the RSRQ
RSRQ dRsrq plan threshold for event A2 for inter-
threshold (negotiat frequency measurement. A larger
Parameter Parameter ID Data Setting Notes
Name Source
ion not value causes a lower probability of
required) triggering event A2. A smaller value
causes a higher probability.

Set this parameter based on the


actual conditions. Usually, set this
parameter to the RSRQ in the area
where the UE throughput in the
serving cell is similar to that in the
neighboring cell.
Interfreq InterFreqHoGroup.InterFreqHoA4Hy Network This parameter specifies the
handover st plan hysteresis for event A4. A larger
hysteresis (negotiat value causes a lower probability of
ion not triggering event A4. A smaller value
required) causes a higher probability.

It is recommended that the default


value be used.
CoverageBa InterFreqHoGroup.InterFreqHoA4Th Network This parameter specifies the RSRP
sed dRsrp plan threshold for event A4 in a coverage-
Interfreq (negotiat based, UL-quality-based, or
RSRP ion not distance-based handover, or in a
threshold required) SPID-based handover to the
HPLMN. A larger value causes a
lower probability of triggering event
A4. A smaller value causes a higher
probability.

The value of this parameter must be


greater than the sum of the peer-end
RSRP threshold for event A2 for
inter-frequency measurement (set in
the InterFreqHoGroup MO at the
peer eNodeB) and the RSRP
threshold offset for event A2 for inter-
frequency measurement for the
higher-priority RAT(set in the
CnOperatorHoCfg MO at the peer
eNodeB).
CoverageBa InterFreqHoGroup.InterFreqHoA4Th Network This parameter specifies the RSRQ
sed Interfrq dRsrq plan threshold for event A4 in a coverage-
RSRQ (negotiat based, UL-quality-based, or
threshold ion not distance-based handover, or in a
required) SPID-based handover to the
HPLMN. A larger value causes a
lower probability of triggering event
A4. A smaller value causes a higher
probability.
Parameter Parameter ID Data Setting Notes
Name Source
The value of this parameter must be
greater than or equal to the peer-end
RSRQ threshold for event A2 for
inter-frequency measurement set at
the peer eNodeB (set in the
InterFreqHoGroup MO at the peer
eNodeB).
Interfreq InterFreqHoGroup.InterFreqHoA4Ti Network This parameter specifies the time-to-
HandOver meToTrig plan trigger for event A4. A larger value
Time to (negotiat causes a lower probability of
Trigger ion not handover to inter-frequency
required) neighboring E-UTRAN cells and a
smaller average number of
handovers, but a higher risk of
service drops. A smaller value
causes the opposite effect.

If both coverage-based inter-


frequency handovers and coverage-
based inter-RAT handovers are
enabled, you are advised to set the
time-to-trigger for the inter-frequency
handover event to be smaller than
that for the inter-RAT handover event
so that intra-RAT is preferentially
performed. This helps increase the
possibility of inter-frequency
handovers.
Interfreq A3 InterFreqHoGroup.InterFreqHoA3Off Network This parameter specifies the offset
offset set plan for event A3 associated with inter-
(negotiat frequency handover. It determines
ion not the border between the serving cell
required) and the neighboring cell. If the
parameter is set to a large value, an
inter-frequency handover is
performed only when the signal
quality of the neighboring cell is
significantly better than that of the
serving cell and other triggering
conditions are met.

It is recommended that you adjust


the parameter value based on the
application scenario. Increase the
parameter value if premature inter-
frequency handovers occur.
Decrease the parameter value if
delayed inter-frequency handovers
occur.
Parameter Parameter ID Data Setting Notes
Name Source
A3 based InterFreqHoGroup.A3InterFreqHoA1 Network This parameter specifies the RSRP
interfreq A1 ThdRsrp plan threshold for event A1 associated
RSRP (negotiat with event-A3-triggered inter-
threshold ion not frequency handover. A relatively
required) large value results in a low
probability of stopping inter-
frequency measurements, whereas a
relatively small value results in a high
probability.

It is recommended that the value of


this parameter be 4 dB greater than
or equal to the sum of the value of
InterFreqHoGroup.A3InterFreqHo
A2ThdRsrp and RSRP threshold
offset for event A2 for inter-frequency
measurement (set in the
CnOperatorHoCfg MO).
A3 based InterFreqHoGroup.A3InterFreqHoA2 Network This parameter specifies the RSRP
Interfreq A2 ThdRsrp plan threshold for event A2 associated
RSRP (negotiat with event-A3-triggered inter-
threshold ion not frequency handover. A relatively
required) small value results in a low
probability of starting inter-frequency
measurements, whereas a relatively
large value results in a high
probability.

Set this parameter based on actual


conditions to ensure that event-A3-
triggered inter-frequency handovers
can occur timely.
Cell Individual Offset for Inter-Frequency Neighboring Cells

The following table provides the parameter that must be set in the EutranInterFreqNCell MO to adjust
cell individual offset for the inter-frequency neighboring cells

Parameter Parameter ID Data Setting Notes


Name Source
Cell EutranInterFreqNCell.CellIndividualOffset Network This parameter affects the
individual plan probability of reporting inter-
offset (negotiation frequency measurement
not events. A larger value
required) indicates a higher probability.

If there are multiple target cells


for the inter-frequency
handover and related
handover parameters need to
be optimized, you can
Parameter Parameter ID Data Setting Notes
Name Source
decrease this parameter value
for a neighboring cell to reduce
the possibility of the handover
to the neighboring cell, or you
can increase this parameter
value for a neighboring cell to
raise the possibility of the
handover to the neighboring
cell.
Intra-RAT Inter-Frequency Handover Parameters

Intra-RAT handover parameters are contained in the IntraRatHoComm MO.

Parameter Parameter ID Data Setting Notes


Name Source
Max report IntraRatHoComm.IntraRatHoMaxRprtCell Network This parameter specifies
cell number plan the maximum number of
(negotiation cells to be included in
not each intra-frequency or
required) inter-frequency
measurement report
after the corresponding
event is triggered. Set
this parameter to a larger
value if the eNodeB
requires more candidate
cells to make a handover
decision. An excessively
large value, however,
causes a waste of air
interface resources.

It is recommended that
the default value be
used.
Measurement IntraRatHoComm.IntraRatHoRprtAmount Network This parameter specifies
report plan the number of intra-
amount (negotiation frequency or inter-
not frequency periodical
required) measurement reports to
be sent after the
corresponding event is
triggered. Set this
parameter to a larger
value if the eNodeB
requires more
measurement reports to
make a handover
decision. An excessively
large parameter value,
Parameter Parameter ID Data Setting Notes
Name Source
however, causes a
waste of air interface
resources.

It is recommended that
the default value be
used.
Measurement IntraRatHoComm.InterFreqHoA4RprtQuan Network This parameter specifies
A4 report plan the reporting quantity to
quantity (negotiation be included in the
not measurement reports
required) after event A4 is
triggered. It can be either
the same as the
triggering quantity for
event A4 for inter-
frequency measurement
or both RSRP and
RSRQ. That is, the
measurement results
can be RSRP-based,
RSRQ-based, or both in
A4-related measurement
reports.

It is recommended that
the default value be used
if the traffic load of LTE
cells is not stable.
Interfreq IntraRatHoComm.InterFreqHoRprtInterval Network This parameter specifies
measurement plan the interval between
report interval (negotiation every two reports that
not are triggered by event
required) A4. A smaller value
causes more
measurement reports
and greater consumption
of air interface
resources, but a higher
probability of triggering
handovers. An
excessively large
parameter value,
however, causes a long
delay in retries and a low
handover success rate.

It is recommended that
the default value be
used.
Parameter Parameter ID Data Setting Notes
Name Source
A1A2 IntraRatHoComm.InterFreqHoA1A2TrigQuan Network This parameter specifies
Measurement plan the triggering quantity for
trig quantity (negotiation inter-frequency
not measurement events A1
required) and A2. The parameter
can be either RSRP or
RSRQ. RSRQ-based
measurement results
reflect signal quality in
real time, whereas
RSRP-based
measurement results are
stable with little signal
fluctuation.

It is recommended that
the default value be used
if the traffic load of LTE
cells is not stable.

When event A3 is used to trigger coverage-based inter-frequency handovers, the reconfiguration of other
parameters is the same as those in coverage-based intra-frequency handovers. For details, see 7.1.9
Parameter Optimization.
Threshold Parameters Related to Coverage-based Handovers

Coverage-based inter-frequency blind handover thresholds are contained in the CellHoParaCfg MO.

Parameter Name Parameter ID Data Setting Notes


Source
BlindHOA1A2ThdRsrp CellHoParaCfg.BlindHOA1A2ThdRsrp Network This parameter
plan specifies the RSRP
(negotiation threshold for events A1
not and A2 that are used
required) for coverage-based
inter-frequency and
inter-RAT blind
handovers.

Set this parameter


based on the actual
coverage conditions to
ensure that service
drops do not occur
within corresponding
areas.
BlindHOA1A2ThdRsrq CellHoParaCfg.BlindHoA1A2ThdRsrq Network This parameter
plan specifies the RSRQ
(negotiation threshold for events A1
not and A2 that are used
required) for coverage-based
Parameter Name Parameter ID Data Setting Notes
Source
inter-frequency and
inter-RAT blind
handovers.

Set this parameter


based on the actual
coverage conditions to
ensure that service
drops do not occur
within corresponding
areas.

7.2.10 Troubleshooting
Fault description:

An event A4 measurement report may not be submitted when a UE moving toward the cell edge
experiences a call drop.

Fault handling

Perform the following steps to determine whether the handover parameters are set correctly:

1. Check the messages over the S1 interface and locate the IE Cause in the
S1AP_UE_CONTEXT_REL_REQ message.
 If the value of this IE is radioNetwork:radio-connection-with-ue-lost, go to 2.
 If the value of this IE is not radioNetwork:radio-connection-with-ue-lost, the handover
parameters are set correctly. Contact Huawei technical support engineers.
2. Check the messages over the Uu interface for A4 measurement reports in RRC_MEAS_RPRT
messages prior to RRC_CONN_REL messages.
 If such reports cannot be found, this problem is due to inappropriate settings of handover
parameters. Go to 3.
 If such reports can be found, contact Huawei engineers.
3. Run the MOD INTERFREQHOGROUP command to reconfigure the following parameters:
 Interfreq A2 RSRP threshold
 Interfreq A2 RSRQ threshold
 Interfreq handover hysteresis
 CoverageBased Interfreq RSRP threshold
 CoverageBased Interfreq RSRQ threshold

7.3 Service-based Inter-Frequency Handover

7.3.1 When to Use Service-based Inter-Frequency Handover

You can enable service-based inter-frequency handover if service differentiation is required by


assigning services of different priorities to different frequencies. For example, services with a
QCI of 1 can be assigned to a narrow-bandwidth frequency and services with other QCIs be
assigned to other wide-bandwidth frequencies. Note that service-based inter-frequency handover
can be enabled on multiple E-UTRAN frequencies, but their QCI-based policy configurations
must be the same.
7.3.2 Required Information

Before deploying service-based inter-frequency handover, collect information about the normal
inter-site spacing and the service that the RF signals of the cell exerting overshoot coverage can
travel to properly set the TA threshold.

7.3.3 Requirements
Operating Environment

None
Transmission Networking

None
License

None

7.3.4 Data Preparation


This section describes the data that you need to collect for setting parameters. Required data is data that
you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature
deployment scenario.
There are three types of data sources:

 Network plan (negotiation required): parameter values planned by the operator and negotiated
with the EPC or peer transmission equipment
 Network plan (negotiation not required): parameter values planned and set by the operator
 User-defined: parameter values set by users

Required Data

For details about the required data, see 7.2.4 Data Preparation.
Scenario-specific Data

Service-based inter-frequency handover can be enabled only after coverage-based inter-frequency


handover is enabled. This section describes the required parameters except those for coverage-based
inter-frequency handover. For details on the required parameters for coverage-based inter-frequency
handover, see the "Scenario-specific Data" part in 7.2.4 Data Preparation.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to configure
service-based inter-frequency handover.

Parame Parameter ID Data Setting Notes


ter Source
Name
Handov ENodeBAlgoSwitch.HoAl Network To enable service-based inter-frequency handover,
er Algo goSwitch plan select the
switch (negotiat ServiceBasedInterFreqHoSwitch(ServiceBasedInt
ion not erFreqHoSwitch) check box under this parameter.
Parame Parameter ID Data Setting Notes
ter Source
Name

required
)

The following table describes the parameters that must be set in the ServiceIfHoCfgGroup MO to
configure a service-based inter-frequency handover policy.

Parameter Parameter ID Data Setting Notes


Name Source
CN ServiceIfHoCfgGroup.CnOperatorId Network This parameter specifies
Operator plan the index of the operator.
ID (negotiation Ensure that this parameter
not has been set in a
required) CnOperator MO.
Service- ServiceIfHoCfgGroup.ServiceIfHoCfgGroupId Network This parameter specifies
based plan the ID of the service-based
inter-Freq (negotiation inter-frequency handover
handover not policy group.
policy required)
group ID This parameter can be
referenced by services
with a specific QCI.
Inter-Freq ServiceIfHoCfgGroup.InterFreqHoState Network This parameter specifies
handover plan whether to allow service-
state (negotiation based inter-frequency
not handovers to a specific
required) frequency.

The following table describes the parameters that must be set in the ServiceIfDlEarfcnGrp MO to
configure a group of downlink EARFCNs to service-based inter-frequency handover policy group.

Parameter Parameter ID Data Source Setting Notes


Name
CN ServiceIfDlEarfcnGrp. Network plan This parameter indicates the ID of the
Operator CnOperatorId (negotiation not operator.
ID required)
This parameter references the
corresponding parameter defined in
the CnOperator MO.
Service ServiceIfDlEarfcnGrp. Network plan This parameter specifies the ID of the
Interfreq ServiceIfHoCfgGroupId (negotiation not service-based inter-frequency
Ho Policy required) handover policy group.
Group Id
This parameter configured the index
for QCI.
Downlink ServiceIfDlEarfcnGrp. Network plan This parameter indicates the index of
EARFCN DlEarfcnIndex (negotiation not a downlink EARFCN in a downlink
Index required)
Parameter Parameter ID Data Source Setting Notes
Name
EARFCN group for service-based
inter-frequency handover.

Only the value with DlEarfcnIndex


set to 0 in the downlink EARFCN
group is valid for LTE FDD cells. All
values of this parameter are valid and
have the same priority for LTE TDD
cells.
Downlink ServiceIfDlEarfcnGrp. Network plan This parameter indicates a downlink
EARFCN DlEarfcn (negotiation not EARFCN for service-based inter-
required) frequency handover.

Only the value with DlEarfcn set to 0


in the downlink EARFCN group is
valid for LTE FDD cells. All values of
this parameter are valid and have the
same priority for LTE TDD cells.

The following tables describe the parameter that must be set to configure inter-frequency handover policy
groups for services with standard or extended QCIs.
The following table describes the parameters that must be set in the CnOperatorStandardQci MO to
configure inter-frequency handover policy groups for services with standard QCIs.

Parame Parameter ID Data Setting Notes


ter Source
Name
CN CnOperatorStandardQci.CnOperatorId Network This parameter specifies the index of
Operato plan the operator. Ensure that this
r ID (negotiati parameter has been set in a
on not CnOperator MO.
required)
QoS CnOperatorStandardQci.Qci Network This parameter specifies the index of
Class plan the standard QCI for which the
Indicatio (negotiati parameter group is configured.
n on not
required)
Service- CnOperatorStandardQci.ServiceIfHoC Network This parameter specifies the ID of the
based fgGroupId plan service-based inter-frequency
inter- (negotiati handover policy group.
Freq on not
handove required) Set this parameter to an ID that is
r policy configured in
group ID ServiceIfHoCfgGroup.ServiceIfHoCf
gGroupId.

The following table describes the parameters that must be set in the CnOperatorExtendedQci MO to
configure inter-frequency handover policy groups for services with extended QCIs.
Parame Parameter ID Data Setting Notes
ter Source
Name
CN CnOperatorExtendedQci.CnOperatorI Network This parameter specifies the index of
Operato d plan the operator. Ensure that this
r ID (negotiati parameter has been set in a
on not CnOperator MO.
required)
CN CnOperatorExtendedQci.ExtendedQci Network This parameter specifies the index of
Operato plan the extended QCI for which the
r (negotiati parameter group is configured.
extende on not
d QCI required)
Service- CnOperatorExtendedQci.ServiceIfHoC Network This parameter specifies the ID of the
based fgGroupId plan service-based inter-frequency
inter- (negotiati handover policy group.
Freq on not
handove required) Set this parameter to an ID that is
r policy configured in
group ID ServiceIfHoCfgGroup.ServiceIfHoCf
gGroupId.

The following table describes the parameters that must be set in the CellStandardQci MO to configure
priority for standard cell QCI.

Parameter Parameter ID Data Source Setting Notes


Name
QCI Priority CellStandardQci.QciPriorityForHo Network plan This parameter specifies
For (negotiation not priority mapping the QCI.
Handover required)

7.3.5 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of related parameters in a summary data file, which also contains other data for the new
eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file,
depending on the following conditions:

 Related managed objects (MOs) are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
 Some related MOs are not contained in a scenario-specific summary data file. In this situation,
customize a summary data file to include the MOs before you can set the parameters.

Related MOs and parameters in each scenario are listed as follows:

Table 7-6 Service-based Inter-Frequency Handover


MO Sheet in the Summary Parameter Group Remarks
Data File
ENodeBAlgoSwitch User-defined sheet Handover Algo switch A list-type
sheet is
ENodeBAlgoSwitch is recommended.
recommended.
ServiceIfHoCfgGroup User-defined sheet CN Operator ID, Service-based A list-type
inter-Freq handover policy group sheet is
ServiceIfHoCfgGroup is ID, Inter-Freq handover state, recommended.
recommended. Downlink EARFCN

EutranExternalCell User-defined sheet Mobile country code, Mobile A list-type


network code, eNodeB identity, sheet is
EutranExternalCell is Cell identity, Downlink EARFCN, recommended.
recommended. Uplink EARFCN indicator, Uplink
EARFCN, Physical cell identity,
Tracking area code, Cell name
EutranExternalCellPlmn User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCellPlmn Cell identity, Share mobile recommended.
is recommended. country code, Share mobile
network code
EutranInterNFreq User-defined sheet Local cell identity, Downlink A list-type
EARFCN, Uplink EARFCN sheet is
EutranInterNFreq is configure indicator, Uplink recommended.
recommended. EARFCN, Inter frequency cell
resel priority configure indicator,
Inter frequency cell resel priority,
EUTRAN reselection time(s),
Speed dependent resel
parameter configuring indicator,
Scaling factor of treseleutra in
medium mobility state, Scaling
factor of treseleutra in high
mobility state, Measurement
bandwidth(MHz), Frequency
offset(dB), Inter frequency high
priority threshold(2dB), Inter
frequency lower priority
threshold(2dB), Minimum
required RX level(2dBm), PMAX
configure indicator, PMAX(dBm),
Neighbor cell config, Presence
antenna port1, Inter-Freq HO
trigger Event Type
EutranInterFreqNCell User-defined sheet Local cell identity, Mobile country A list-type
code, Mobile network code, sheet is
EutranInterFreqNCell is eNodeB identity, Cell identity, recommended.
recommended. Cell individual offset(dB), Cell
offset(dB), No handover indicator,
No remove indicator, Blind
handover Priority, ANR flag,
MO Sheet in the Summary Parameter Group Remarks
Data File
Local cell name, Neighbour cell
name
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a
single procedure. The procedure is as follows:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary
data file for batch reconfiguration.

NOTE:

For context-sensitive help on a current task in the client, press F1.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
3. In the summary data file, set the parameters in the MOs listed in Table 7-6 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The
procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration
window.
2. In area 1 shown in Figure 7-3, select the eNodeB to which the MOs belong.
Figure 7-3 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using MML Commands

1. Run the MOD ENODEBALGOSWITCH command to enable service-based inter-frequency


handover.
2. Run the MOD SERVICEIFHOCFGGROUP command to configure a service-based inter-
frequency handover policy group.
3. Run the following commands to add neighbor relationships with inter-frequency E-UTRAN
cells:
a. ADD EUTRANINTERNFREQ
b. (Optional) ADD EUTRANEXTERNALCELL, which is required when the inter-frequency
neighboring cell is under a different eNodeB from the local cell.
c. (Optional) ADD EUTRANEXTERNALCELLPLMN, which is used to configure the PLMN
list for an external E-UTRAN cell when the neighboring E-UTRAN cell works in RAN
sharing mode.
d. ADD EUTRANINTERFREQNCELL
4. Run the following command to modify service settings:
a. To modify the settings of a standardized QCI for an operator, run the MOD
CNOPERATORSTANDARDQCI command.
b. To add a Huawei-defined extended QCI for an operator, run the ADD
CNOPERATOREXTENDEDQCI command.
5. Run the ADD SERVICEIFDLEARFCNGRP command to add target EARFCNs for specified
services.

MML Command Examples

//Activating service-based inter-frequency handover


MOD ENODEBALGOSWITCH: HoAlgoSwitch=ServiceBasedInterFreqHoSwitch-1;
MOD SERVICEIFHOCFGGROUP: CnOperatorId=0, ServiceIfHoCfgGroupId=0,
InterFreqHoState=PERMIT_HO, DlEarfcn=2860;
//Adding inter-frequency neighboring E-UTRAN cells
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2860,
UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG,
SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG,
QqualMinCfgInd=NOT_CFG;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
DlEarfcn=2860, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1;
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
ShareMcc="460", ShareMnc="22";
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20",
eNodeBId=123, CellId=1;
//Configuring services with standard QCI and target EARFCNs
MOD CNOPERATORSTANDARDQCI: CnOperatorId=0, Qci=QCI9,
ServiceIrHoCfgGroupId=0;
ADD SERVICEIFDLEARFCNGRP: CnOperatorId=0, ServiceIfHoCfgGroupId=9,
DlEarfcnIndex=0, DlEarfcn=38100;

7.3.6 Activation Observation


The observation procedure is as follows:

1. Trace messages over the S1 interface after a UE accesses the network at the center of a cell
in the 2600 MHz band and sets up a handover-enabled dedicated bearer with a QCI of 2.
Check the S1AP_ERAB_SETUP_REQ message. If the message contains dedicated-bearer
configuration, you can infer that service-based inter-frequency handover has been activated.
2. Trace messages over the Uu interface on the U2000 client. Check the RRC_CONN_RECFG
message that contains the A4-related inter-frequency measurement configuration for service-
based handover.
3. Trace messages over the Uu interface on the U2000 client again. Check the
RRC_CONN_RECFG message, which is the handover command sent from the eNodeB after
the eNodeB receives an A4-related inter-frequency measurement report from the UE for a
service-based handover. If the message contains target cell access information, you can infer
that service-based inter-frequency handover has been triggered.

7.3.7 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs.
This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single
procedure. The procedure for feature deactivation is similar to that for feature activation described in
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify related
parameters described below.

Table 7-7 Parameters related to service-based inter-frequency handover

MO Sheet in the Parameter Group Setting Notes


Summary Data File
ENodeBAlgoSwitch ENodeBAlgoSwitch Handover Algo Clear the
switch ServiceBasedInterFreqHoSwitch
check box.
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in each scenario for a single eNodeB. For detailed instructions,
see Using the CME to Perform Single Configuration for feature activation.
Using MML Commands

To deactivate service-based inter-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.

MML Command Examples

//Deactivating service-based inter-frequency handover


MOD ENODEBALGOSWITCH: HoAlgoSwitch=ServiceBasedInterFreqHoSwitch-0;

7.3.8 Performance Monitoring


The handover success rate and service drop rate used for monitoring the performance of service-based
inter-frequency handover are the same as those for monitoring the performance of coverage-based inter-
frequency handover. For details, see 7.2.8 Performance Monitoring.
Table 7-8 lists the counters related to service-based inter-frequency and inter-mode handover.

Table 7-8 Counters related to service-based inter-frequency and inter-mode handover

Counter ID Counter Name Counter Description


1526729479 L.HHO.InterFreq.Service.PrepAttOut Number of service-based inter-
frequency handover preparation
attempts
1526729480 L.HHO.InterFreq.Service.ExecAttOut Number of Service-based Inter-
Frequency Handover Execution
Attempts
1526729481 L.HHO.InterFreq.Service.ExecSuccOut Number of Successful Service-based
Inter-Frequency Handover Executions
1526730002 L.HHO.InterFddTdd.Service.PrepAttOut Number of service-based inter-duplex-
mode handover preparation attempts
1526730003 L.HHO.InterFddTdd.Service.ExecAttOut Number of service-based inter-duplex-
mode handover execution attempts
Counter ID Counter Name Counter Description
1526730004 L.HHO.InterFddTdd.Service.ExecSuccOut Number of successful service-based
inter-duplex-mode handover
executions

7.3.9 Parameter Optimization


The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-frequency handovers. For details, see 7.2.9 Parameter
Optimization.
Inter-Frequency Handover Parameters

Inter-frequency handover parameters are contained in the InterFreqHoGroup MO.

Paramete Parameter ID Data Setting Notes


r Name Source
Local cell InterFreqHoGroup.LocalCellId Network Ensure that this
ID plan parameter has
(negotiatio been set in a Cell
n not MO based on the
required) network plan.
Load InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsr Network This parameter
Based p plan specifies the
Interfreq (negotiatio RSRP threshold
RSRP n not for event A4 for
threshold required) load-based,
frequency-priority-
based, and
service-based
inter-frequency
handovers. A
larger value
causes a lower
probability of
triggering event
A4. A smaller
value causes a
higher probability.

The value of this


parameter must be
greater than the
sum of the peer-
end RSRP
threshold for event
A2 for inter-
frequency
measurement (set
in the
InterFreqHoGrou
p MO at the peer
eNodeB) and the
Paramete Parameter ID Data Setting Notes
r Name Source
RSRP threshold
offset for event A2
for inter-frequency
measurement (set
in the
CnOperatorHoCfg
MO at the peer
eNodeB).
Load InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsr Network This parameter
Based q plan specifies the
Interfrq (negotiatio RSRQ threshold
RSRQ n not for event A4 for
threshold required) load-based,
frequency-priority-
based, and
service-based
inter-frequency
handovers. A
larger value
causes a lower
probability of
triggering event
A4. A smaller
value causes a
higher probability.

The value of this


parameter must be
greater than or
equal to the peer-
end RSRQ
threshold for event
A2 for inter-
frequency
measurement set
at the peer
eNodeB (set in the
InterFreqHoGrou
p MO at the peer
eNodeB).
Intra-RAT Inter-Frequency Handover Parameters

Intra-RAT handover parameters are contained in the IntraRatHoComm MO.

Parameter Parameter ID Data Setting Notes


Name Source
FreqPrior IntraRatHoComm.InterFreqHoA4TrigQuan Network This parameter specifies
loadBased plan the event A4 triggering
A4 (negotiation quantity for inter-frequency
Measurement handovers other than
Parameter Parameter ID Data Setting Notes
Name Source
trigger not coverage-based inter-
quantity required) frequency handovers. The
quantity can be either
RSRP or RSRQ, or both.
The measured RSRP
values are stable, slightly
varying with the load, and
therefore there is little
signal fluctuation. The
measured RSRQ values
vary with the load and are
likely to reflect the signal
quality of the cell in real
time.

It is recommended that the


default value be used if the
traffic load of LTE cells is
not stable.

7.3.10 Troubleshooting
Fault description

A UE with a service of QCIx may not be handed over to a cell working at frequency F1 after the handover
policy has been set to enable services with QCIx to be handed over to a cell working at frequency F1.
Fault handling

Perform the following steps to determine whether the handover parameters are set correctly:

1. Check the messages over the S1 interface and locate the e-RABlevelQoSParameters IE in the
S1AP_INITIAL_CONTEXT_SETUP_REQ message and the S1AP_ERAB_SETUP_REQ
message (which may not exist).
 If QCIx is not contained in the e-RABlevelQoSParameters IE, ignore this fault and
perform the test again after verifying that the UE has set up a service with QCIx.
 If QCIx is contained in the e-RABlevelQoSParameters IE, check whether the UE has set
up a service which is not allowed to be handed over to a cell working at F1 because of its
QCI.
 If yes, perform the test again after the UE has stopped this service.
 If no, go to step 2.
2. Check the messages over the Uu interface for A4 measurement reports in RRC_MEAS_RPRT
messages.
 If such reports cannot be found, this problem is due to inappropriate settings of handover
parameters. Go to 3.
 If such reports can be found, contact Huawei technical support engineers.
3. Run the MOD INTERFREQHOGROUP command to reconfigure the following parameters:
 Interfreq handover hysteresis
 CoverageBased Interfreq RSRP threshold
 CoverageBased Interfreq RSRQ threshold

7.4 Distance-based Inter-Frequency Handover


7.4.1 When to Use Distance-based Inter-Frequency Handover

If high bands and low bands are used to cover separate areas that border each other, RF signals
from a high-band cell may be able to travel a long distance (for example, three times the inter-
site spacing) and cause severe overshoot coverage to low-band cells. If the low-band cells are not
configured as neighboring cells of the high-band cell, inter-frequency measurements cannot be
triggered in time and call drops will occur. To reduce the probability of such call drops, you can
enable distance-based inter-frequency handover.

7.4.2 Required Information


Before deploying distance-based inter-frequency handover, collect information about the distance that the
RF signals of the cell exerting overshoot coverage based on the inter-eNodeB distance on the live
network. This distance is the criterion for the distance-based inter-frequency handover threshold.

7.4.3 Requirements
Operating Environment

None

Transmission Networking

None
License

None

7.4.4 Data Preparation


This section describes the data that you need to collect for setting parameters. Required data is data that
you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature
deployment scenario.
There are three types of data sources:

 Network plan (negotiation required): parameter values planned by the operator and negotiated
with the EPC or peer transmission equipment
 Network plan (negotiation not required): parameter values planned and set by the operator
 User-defined: parameter values set by users

Required Data

For details about the required data, see 7.2.4 Data Preparation.
Scenario-specific Data

Distance-based inter-frequency handover can be enabled only after coverage-based inter-frequency


handover is enabled. This section describes the required parameters except those for coverage-based
inter-frequency handover. For details on the required parameters for coverage-based inter-frequency
handover, see the "Scenario-specific Data" part in 7.2.4 Data Preparation.
To enable distance-based inter-frequency handovers, the corresponding switch must be turned on and
the measurement object type must be set to EUTRAN.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to enable
distance-based inter-frequency handovers.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell ID CellAlgoSwitch.LocalCellId Network Ensure that this parameter has
plan been set in a Cell MO.
(negotiation
not
required)
Distance- CellAlgoSwitch.DistBasedHoSwitch Network This parameter specifies whether
based plan to enable distance-based
Handover (negotiation handovers. If this switch is turned
Switch not on, distance-based handovers are
required) allowed. If this switch is turned
off, distance-based handovers to
any cells are prohibited.

The following table describes the parameters that must be set in the DistBasedHO MO to set the
measurement object type.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell ID DistBasedHO.LocalCellId Network Ensure that this parameter has
plan been set in a Cell MO.
(negotiation
not
required)
Distance- DistBasedHO.DistBasedMeasObjType Network This parameter specifies the
based plan measurement object type for
Measurement (negotiation distance-based handovers.
Object Type not
required) If this parameter is set to
EUTRAN, distanced-based
handovers to inter-frequency
neighboring cells are allowed.

7.4.5 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of related parameters in a summary data file, which also contains other data for the new
eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file,
depending on the following conditions:

 Related managed objects (MOs) are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
 Some related MOs are not contained in a scenario-specific summary data file. In this situation,
customize a summary data file to include the MOs before you can set the parameters.
Related MOs and parameters in each scenario are listed as follows:

Table 7-9 Distance-based Inter-Frequency Handover

MO Sheet in the Summary Parameter Group Remarks


Data File
CellAlgoSwitch User-defined sheet Distance-based Handover Switch A list-type
sheet is
CellAlgoSwitch is recommended.
recommended.
DistBaseDHO User-defined sheet Local cell identity, Distance- A list-type
based Measurement Object sheet is
DistBasedHO is Type, Distance-based Handover recommended.
recommended. Threshold

EutranExternalCell User-defined sheet Mobile country code, Mobile A list-type


network code, eNodeB identity, sheet is
EutranExternalCell is Cell identity, Downlink EARFCN, recommended.
recommended. Uplink EARFCN indicator, Uplink
EARFCN, Physical cell identity,
Tracking area code, Cell name
EutranExternalCellPlmn User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCellPlmn Cell identity, Share mobile recommended.
is recommended. country code, Share mobile
network code
EutranInterNFreq User-defined sheet Local cell identity, Downlink A list-type
EARFCN, Uplink EARFCN sheet is
EutranInterNFreq is configure indicator, Uplink recommended.
recommended. EARFCN, Inter frequency cell
resel priority configure indicator,
Inter frequency cell resel priority,
EUTRAN reselection time(s),
Speed dependent resel
parameter configuring indicator,
Scaling factor of treseleutra in
medium mobility state, Scaling
factor of treseleutra in high
mobility state, Measurement
bandwidth(MHz), Frequency
offset(dB), Inter frequency high
priority threshold(2dB), Inter
frequency lower priority
threshold(2dB), Minimum
required RX level(2dBm), PMAX
configure indicator, PMAX(dBm),
Neighbor cell config, Presence
antenna port1, Inter-Freq HO
trigger Event Type
MO Sheet in the Summary Parameter Group Remarks
Data File
EutranInterFreqNCell User-defined sheet Local cell identity, Mobile country A list-type
code, Mobile network code, sheet is
EutranInterFreqNCell is eNodeB identity, Cell identity, recommended.
recommended. Cell individual offset(dB), Cell
offset(dB), No handover indicator,
No remove indicator, Blind
handover Priority, ANR flag,
Local cell name, Neighbour cell
name
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a
single procedure. The procedure is as follows:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary
data file for batch reconfiguration.

NOTE:

For context-sensitive help on a current task in the client, press F1.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
3. In the summary data file, set the parameters in the MOs listed in Table 7-9 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The
procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration
window.
2. In area 1 shown in Figure 7-4, select the eNodeB to which the MOs belong.
Figure 7-4 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using MML Commands

1. Run the MOD CELLALGOSWITCH command to turn on the switch for distance-based
handover.
2. Run the MOD DISTBASEDHO command to enable the measurement for distance-based inter-
frequency handover.
3. Run the following commands to add neighbor relationships with inter-frequency E-UTRAN
cells:
a. ADD EUTRANINTERNFREQ
b. (Optional) ADD EUTRANEXTERNALCELL, which is required when the inter-frequency
neighboring cell is under a different eNodeB from the local cell.
c. (Optional) ADD EUTRANEXTERNALCELLPLMN, which is used to configure the PLMN
list for an external E-UTRAN cell when the neighboring E-UTRAN cell works in RAN
sharing mode.
d. ADD EUTRANINTERFREQNCELL
MML Command Examples

//Activating distance-based handover


MOD CELLALGOSWITCH: LocalCellId=0, DistBasedHoSwitch=ON;
MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=EUTRAN-1;
//Adding inter-frequency neighboring E-UTRAN cells
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2860,
UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG,
SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG,
QqualMinCfgInd=NOT_CFG;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
DlEarfcn=2860, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1;
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
ShareMcc="460", ShareMnc="22";
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20",
eNodeBId=123, CellId=1;

7.4.6 Activation Observation


The observation procedure is as follows:

1. Trace messages over the Uu interface on the U2000 client after a UE accesses the network at
the center of a cell in the 2600 MHz band. Move the UE toward the cell edge. During the
movement, inter-frequency measurements are not triggered for a coverage-based handover
due to overshoot coverage, but the threshold for distance-based inter-frequency handover is
reached. Check the RRC_CONN_RECFG message. If the message contains measurement
configuration for a distance-based inter-frequency handover, you can infer that distance-based
inter-frequency handover has been activated.
2. Trace messages over the Uu interface on the U2000 client again. Check the
RRC_CONN_RECFG message, which is the handover command sent from the eNodeB after
the eNodeB receives an A4-related inter-frequency measurement report from the UE for a
distance-based handover. If the message contains target cell access information, you can infer
that distance-based inter-frequency handover has been triggered.

7.4.7 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs.
This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single
procedure. The procedure for feature deactivation is similar to that for feature activation described in
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify related
parameters described below.

Table 7-10 Parameters related to distance-based inter-frequency handover

MO Sheet in the Summary Parameter Group Setting Notes


Data File
CellAlgoSwitch CellAlgoSwitch Distance-based Handover Set the switch to OFF(Off).
Switch
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in each scenario for a single eNodeB. For detailed instructions,
see Using the CME to Perform Single Configuration for feature activation.
Using MML Commands

To deactivate the measurement for distance-based inter-frequency handover, disable its algorithm by
running the MOD DISTBASEDHO command.

MML Command Examples

//Deactivating the measurement for distance-based inter-frequency handover


MOD DISTBASEDHO: LocalCellId=0, DistBasedMeasObjType=EUTRAN-0;

7.4.8 Performance Monitoring


The handover success rate and service drop rate used for monitoring the performance of distance-based
inter-frequency handover are the same as those for monitoring the performance of coverage-based inter-
frequency handover. For details, see 7.2.8 Performance Monitoring.
Table 7-11 lists the counters related to distance-based inter-frequency and inter-mode handover.

Table 7-11 Counters related to distance-based inter-frequency and inter-mode handover

Counter ID Counter Name Counter Description


1526730010 L.HHO.InterFreq.Distance.PrepAttOut Number of distance-based inter-
frequency handover preparation
attempts
1526730012 L.HHO.InterFreq.Distance.ExecAttOut Number of distance-based inter-
frequency handover execution
attempts
1526730014 L.HHO.InterFreq.Distance.ExecSuccOut Number of distance-based inter-
frequency handover execution
attempts
1526730011 L.HHO.InterFddTdd.Distance.PrepAttOut Number of distance-based inter-
duplex-mode handover preparation
attempts
1526730013 L.HHO.InterFddTdd.Distance.ExecAttOut Number of distance-based inter-
duplex-mode handover execution
attempts
1526730015 L.HHO.InterFddTdd.Distance.ExecSuccOut Number of successful distance-based
inter-duplex-mode handover
executions

7.4.9 Parameter Optimization


The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-frequency handovers. For details, see 7.2.9 Parameter
Optimization.
Distance-Based Handover Threshold

Distance-based handover threshold is contained in the DistBasedHO MO.


Parameter Parameter ID Data Source Setting Notes
Name
Distance- DistBasedHO.DistBasedHOThd Network plan This parameter specifies the
based (negotiation not threshold for distance-based
Handover required) handovers.
Threshold
It is recommended that you set
this parameter based on the
planned distance between sites.
Inter-Frequency Handover Parameters

Inter-frequency handover parameters are contained in the InterFreqHoGroup MO.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell ID InterFreqHoGroup.LocalCellId Network Ensure that this
plan parameter has been
(negotiation set in a Cell MO
not based on the network
required) plan.
CoverageBased InterFreqHoGroup.InterFreqHoA4ThdRsrp Network This parameter
Interfreq RSRP plan specifies the RSRP
threshold (negotiation threshold for event A4
not in a coverage-based,
required) UL-quality-based, or
distance-based
handover, or in a
SPID-based handover
to the HPLMN. A
larger value causes a
lower probability of
triggering event A4. A
smaller value causes
a higher probability.

The value of this


parameter must be
greater than the sum
of the peer-end RSRP
threshold for event A2
for inter-frequency
measurement (set in
the
InterFreqHoGroup
MO at the peer
eNodeB) and the
RSRP threshold offset
for event A2 for inter-
frequency
measurement (set in
the
CnOperatorHoCfg
Parameter Parameter ID Data Setting Notes
Name Source
MO at the peer
eNodeB).
CoverageBased InterFreqHoGroup.InterFreqHoA4ThdRsrq Network This parameter
Interfrq RSRQ plan specifies the RSRQ
threshold (negotiation threshold for event A4
not in a coverage-based,
required) UL-quality-based, or
distance-based
handover, or in a
SPID-based handover
to the HPLMN. A
larger value causes a
lower probability of
triggering event A4. A
smaller value causes
a higher probability.

The value of this


parameter must be
greater than or equal
to the peer-end RSRQ
threshold for event A2
for inter-frequency
measurement set at
the peer eNodeB (set
in the
InterFreqHoGroup
MO at the peer
eNodeB).
Interfreq InterFreqHoGroup.InterFreqHoA4TimeToTrig Network This parameter
HandOver Time plan specifies the time-to-
to Trigger (negotiation trigger for event A4. A
not larger value causes a
required) lower probability of
handover to inter-
frequency neighboring
E-UTRAN cells and a
smaller average
number of handovers,
but a higher risk of
service drops. A
smaller value causes
the opposite effect.

If both distance-based
inter-frequency
handovers and
distance-based inter-
RAT handovers are
enabled, you are
advised to set the
Parameter Parameter ID Data Setting Notes
Name Source
time-to-trigger for the
inter-frequency
handover event to be
smaller than that for
the inter-RAT
handover event. This
helps increase the
possibility of inter-
frequency handovers.
Intra-RAT Inter-Frequency Handover Parameters

Intra-RAT handover parameters are contained in the IntraRatHoComm MO.

Parameter Parameter ID Data Setting Notes


Name Source
FreqPrior IntraRatHoComm.InterFreqHoA4TrigQuan Network This parameter specifies
loadBased plan the event A4 triggering
A4 (negotiation quantity for inter-frequency
Measurement not handovers other than
trigger required) coverage-based inter-
quantity frequency handovers. The
quantity can be either
RSRP or RSRQ, or both.
The measured RSRP
values are stable, slightly
varying with the load, and
therefore there is little
signal fluctuation. The
measured RSRQ values
vary with the load and are
likely to reflect the signal
quality of the cell in real
time.

It is recommended that the


default value be used if the
traffic load of LTE cells is
not stable.

7.4.10 Troubleshooting
Fault Description

An event A4 measurement report may not be submitted when a UE moving toward the edge of a
cell that has overshoot coverage experiences a call drop.

Fault handling

Perform the following steps to determine whether the handover parameters are set correctly:
1. Check the messages over the S1 interface and locate the IE Cause in the
S1AP_UE_CONTEXT_REL_REQ message.
 If the value of this IE is radioNetwork:radio-connection-with-ue-lost, go to 2.
 If the value of this IE is not radioNetwork:radio-connection-with-ue-lost, the handover
parameters are set correctly. Contact Huawei technical support engineers.
2. Check the messages over the Uu interface for A4 measurement reports in RRC_MEAS_RPRT
messages prior to RRC_CONN_REL messages.
 If such reports cannot be found, this problem is due to inappropriate settings of handover
parameters. Go to 3.
 If such reports can be found, contact Huawei technical support engineers.
3. Run the MOD INTERFREQHOGROUP command to reconfigure the following parameters:
 Interfreq handover hysteresis
 CoverageBased Interfreq RSRP threshold
 CoverageBased Interfreq RSRQ threshold

7.5 UL-quality-based Inter-Frequency Handover

7.5.1 When to Use UL-quality-based Inter-Frequency Handover

Coverage-based inter-frequency handovers are triggered based on DL signal quality. However,


there may be a huge imbalance between the DL and UL signal quality: The UL signal quality
may be relatively poor while the DL signal quality is fairly satisfactory. If this occurs, inter-
frequency handovers cannot be promptly triggered. To handle this problem, you can enable UL-
quality-based inter-frequency handover.

7.5.2 Required Information

Before deploying UL-quality-based inter-frequency handover, collect the causes of the


imbalance between the UL and DL signal quality as well as the possible magnitudes of the
imbalance. In addition, you need to collect the requirements of the local network plan for the UL
data rate at the cell edge.

7.5.3 Requirements
Operating Environment

None
Transmission Networking

None
License

None

7.5.4 Data Preparation


This section describes the data that you need to collect for setting parameters. Required data is data that
you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature
deployment scenario.
There are three types of data sources:
 Network plan (negotiation required): parameter values planned by the operator and negotiated
with the EPC or peer transmission equipment
 Network plan (negotiation not required): parameter values planned and set by the operator
 User-defined: parameter values set by users

Required Data

For details about the required data, see 7.2.4 Data Preparation.
Scenario-specific Data

UL-quality-based inter-frequency handover can be enabled only after coverage-based inter-frequency


handover is enabled. This section describes the required parameters except those for coverage-based
inter-frequency handover. For details on the required parameters for coverage-based inter-frequency
handover, see the "Scenario-specific Data" part in 7.2.4 Data Preparation.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to configure
UL-quality-based inter-frequency handover.

Paramet Parameter ID Data Setting Notes


er Name Source
Handov ENodeBAlgoSwitch.HoAlgo Network To enable UL-quality-based inter-frequency
er Algo Switch plan handover, select the
switch (negotiati UlQualityInterFreqHoSwitch(UlQualityInterFre
on not qHoSwitch) check box under this parameter.
required)

7.5.5 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of related parameters in a summary data file, which also contains other data for the new
eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file,
depending on the following conditions:

 Related managed objects (MOs) are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
 Some related MOs are not contained in a scenario-specific summary data file. In this situation,
customize a summary data file to include the MOs before you can set the parameters.

Related MOs and parameters in each scenario are listed as follows:

Table 7-12 UL-Quality-based Inter-Frequency Handover

MO Sheet in the Summary Parameter Group Remarks


Data File
ENodeBAlgoSwitch User-defined sheet Handover Algo switch A list-type
sheet is
recommended.
MO Sheet in the Summary Parameter Group Remarks
Data File
ENodeBAlgoSwitch is
recommended.
EutranExternalCell User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCell is Cell identity, Downlink recommended.
recommended. EARFCN, Uplink EARFCN
indicator, Uplink EARFCN,
Physical cell identity, Tracking
area code, Cell name
EutranExternalCellPlmn User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCellPlmn Cell identity, Share mobile recommended.
is recommended. country code, Share mobile
network code
EutranInterNFreq User-defined sheet Local cell identity, Downlink A list-type
EARFCN, Uplink EARFCN sheet is
EutranInterNFreq is configure indicator, Uplink recommended.
recommended. EARFCN, Inter frequency cell
resel priority configure indicator,
Inter frequency cell resel
priority, EUTRAN reselection
time(s), Speed dependent resel
parameter configuring indicator,
Scaling factor of treseleutra in
medium mobility state, Scaling
factor of treseleutra in high
mobility state, Measurement
bandwidth(MHz), Frequency
offset(dB), Inter frequency high
priority threshold(2dB), Inter
frequency lower priority
threshold(2dB), Minimum
required RX level(2dBm),
PMAX configure indicator,
PMAX(dBm), Neighbor cell
config, Presence antenna port1,
Inter-Freq HO trigger Event
Type
EutranInterFreqNCell User-defined sheet Local cell identity, Mobile A list-type
country code, Mobile network sheet is
EutranInterFreqNCell is code, eNodeB identity, Cell recommended.
recommended. identity, Cell individual
offset(dB), Cell offset(dB), No
handover indicator, No remove
indicator, Blind handover
Priority, ANR flag, Local cell
name, Neighbour cell name
Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on existing
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a
single procedure. The procedure is as follows:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary
data file for batch reconfiguration.

NOTE:

For context-sensitive help on a current task in the client, press F1.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
3. In the summary data file, set the parameters in the MOs listed in Table 7-12 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The
procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration
window.
2. In area 1 shown in Figure 7-5, select the eNodeB to which the MOs belong.
Figure 7-5 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using MML Commands

1. Run the MOD ENODEBALGOSWITCH command to enable UL-quality-based inter-frequency


handover.
2. Run the following commands to add neighbor relationships with inter-frequency E-UTRAN
cells:
a. ADD EUTRANINTERNFREQ
b. (Optional) ADD EUTRANEXTERNALCELL, which is required when the inter-frequency
neighboring cell is under a different eNodeB from the local cell.
c. (Optional) ADD EUTRANEXTERNALCELLPLMN, which is used to configure the PLMN
list for an external E-UTRAN cell when the neighboring E-UTRAN cell works in RAN
sharing mode.
d. ADD EUTRANINTERFREQNCELL

MML Command Examples


//Activating UL-quality-based inter-frequency handover
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UlQualityInterFreqHoSwitch-1;
//Adding inter-frequency neighboring E-UTRAN cells
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2860,
UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG,
SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG,
QqualMinCfgInd=NOT_CFG;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
DlEarfcn=2860, UlEarfcnCfgInd=NOT_CFG, PhyCellId=101, Tac=1;
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=123, CellId=1,
ShareMcc="460", ShareMnc="22";
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20",
eNodeBId=123, CellId=1;

7.5.6 Activation Observation


The observation procedure is as follows:

1. Use a UE to access the network at the cell center in the 2600 MHz band. Then, move the UE
from the cell center to the cell edge. During this process, the uplink quality of the UE becomes
poor.
2. Observe the user-level measurement result on the U2000 (choose Monitor > Signaling Trace
> Signaling Trace Management, and observe the value of BLER Monitoring in User
Performance Monitoring.)
 When the user uplink IBLER increases gradually, observe the messages traced over the
Uu interface. If the RRC_CONN_RECFG message from the eNodeB contains
measurement control information for the inter-frequency handover and the
RRC_CONN_RECFG message received by the eNodeB contains information of the
target cell for an inter-frequency handover, you can infer that UL-quality-based inter-
frequency handover has been activated.
 When the user uplink IBLER increases suddenly but has not reached 99%, observe the
messages traced over the Uu interface. If the RRC_CONN_REL message from the
eNodeB contains target frequency information, you can infer that UL-quality-based inter-
frequency handover has been activated.
3. Observe the messages traced over the Uu interface again.

As the uplink IBLER of the UE increases, if the RRC_CONN_RECFG message, which is a


handover command, contains the target cell access information, you can infer that UL-quality-
based inter-frequency handover has been triggered.

7.5.7 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs.
This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single
procedure. The procedure for feature deactivation is similar to that for feature activation described in
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify related
parameters described below.

Table 7-13 Parameters related to UL-quality-based inter-frequency handover


MO Sheet in the Parameter Group Setting Notes
Summary Data File
ENodeBAlgoSwitch ENodeBAlgoSwitch Handover Algo switch Clear the
UlQualityInterFreqHoSwitch
check box.
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in each scenario for a single eNodeB. For detailed instructions,
see Using the CME to Perform Single Configuration for feature activation.

Using MML Commands

To deactivate UL-quality-based inter-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.

MML Command Examples

//Deactivating UL-quality-based inter-frequency handover


MOD ENODEBALGOSWITCH: HoAlgoSwitch=UlQualityInterFreqHoSwitch-0;

7.5.8 Performance Monitoring


The handover success rate and service drop rate used for monitoring the performance of UL-quality-
based inter-frequency handover are the same as those for monitoring the performance of coverage-
based inter-frequency handover. For details, see 7.2.8 Performance Monitoring.
Table 7-14 lists the counters related to UL-quality-based inter-frequency and inter-mode handover.

Table 7-14 Counters related to UL-quality-based inter-frequency and inter-mode handover

Counter ID Counter Name Counter Description


1526729994 L.HHO.InterFreq.ULquality.PrepAttOut Number of UL-quality-based inter-
frequency handover preparation
attempts
1526729996 L.HHO.InterFreq.ULquality.ExecAttOut Number of UL-quality-based inter-
frequency handover execution
attempts
1526729998 L.HHO.InterFreq.ULquality.ExecSuccOut Number of successful UL-quality-
based inter-frequency handover
executions
1526729995 L.HHO.InterFddTdd.ULquality.PrepAttOut Number of UL-quality-based inter-
duplex-mode handover preparation
attempts
1526729997 L.HHO.InterFddTdd.ULquality.ExecAttOut Number of UL-quality-based inter-
duplex-mode handover execution
attempts
1526729999 L.HHO.InterFddTdd.ULquality.ExecSuccOut Number of successful UL-quality-
based inter-duplex-mode handover
executions
7.5.9 Parameter Optimization
The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-frequency handovers. For details, see 7.2.9 Parameter
Optimization.
Inter-Frequency Handover Parameters

Inter-frequency handover parameters are contained in the InterFreqHoGroup MO.

Parameter Parameter ID Data Setting Notes


Name Source
Local cell ID InterFreqHoGroup.LocalCellId Network Ensure that this
plan parameter has been
(negotiation set in a Cell MO
not based on the network
required) plan.
CoverageBased InterFreqHoGroup.InterFreqHoA4ThdRsrp Network This parameter
Interfreq RSRP plan specifies the RSRP
threshold (negotiation threshold for event A4
not in a coverage-based,
required) UL-quality-based, or
distance-based
handover, or in a
SPID-based handover
to the HPLMN. A
larger value causes a
lower probability of
triggering event A4. A
smaller value causes
a higher probability.

The value of this


parameter must be
greater than the sum
of the peer-end RSRP
threshold for event A2
for inter-frequency
measurement (set in
the
InterFreqHoGroup
MO at the peer
eNodeB) and the
RSRP threshold offset
for event A2 for inter-
frequency
measurement (set in
the
CnOperatorHoCfg
MO at the peer
eNodeB).
CoverageBased InterFreqHoGroup.InterFreqHoA4ThdRsrq Network This parameter
Interfrq RSRQ plan specifies the RSRQ
threshold (negotiation threshold for event A4
Parameter Parameter ID Data Setting Notes
Name Source
not in a coverage-based,
required) UL-quality-based, or
distance-based
handover, or in a
SPID-based handover
to the HPLMN. A
larger value causes a
lower probability of
triggering event A4. A
smaller value causes
a higher probability.

The value of this


parameter must be
greater than or equal
to the peer-end RSRQ
threshold for event A2
for inter-frequency
measurement set at
the peer eNodeB (set
in the
InterFreqHoGroup
MO at the peer
eNodeB).
Interfreq InterFreqHoGroup.InterFreqHoA4TimeToTrig Network This parameter
HandOver Time plan specifies the time-to-
to Trigger (negotiation trigger for event A4. A
not larger value causes a
required) lower probability of
handover to inter-
frequency neighboring
E-UTRAN cells and a
smaller average
number of handovers,
but a higher risk of
service drops. A
smaller value causes
the opposite effect.

If both UL-quality-
based inter-frequency
handovers and UL-
quality-based inter-
RAT handovers are
enabled, you are
advised to set the
time-to-trigger for the
inter-frequency
handover event to be
smaller than that for
the inter-RAT
Parameter Parameter ID Data Setting Notes
Name Source
handover event,
increasing the
possibility of inter-
frequency handovers.
Intra-RAT Inter-Frequency Handover Parameters

Intra-RAT handover parameters are contained in the IntraRatHoComm MO.

Parameter Parameter ID Data Setting Notes


Name Source
FreqPrior IntraRatHoComm.InterFreqHoA4TrigQuan Network This parameter specifies
loadBased plan the event A4 triggering
A4 (negotiation quantity for inter-frequency
Measurement not handovers other than
trigger required) coverage-based inter-
quantity frequency handovers. The
quantity can be either
RSRP or RSRQ, or both.
The measured RSRP
values are stable, slightly
varying with the load, and
therefore there is little
signal fluctuation. The
measured RSRQ values
vary with the load and are
likely to reflect the signal
quality of the cell in real
time.

It is recommended that the


default value be used if the
traffic load of LTE cells is
not stable.

7.5.10 Troubleshooting
Fault description

An event A4 measurement report may not be submitted when a UE moving toward the cell edge
experiences a call drop.

Fault handling

Perform the following steps to determine whether the handover parameters are set correctly:

1. Check the messages over the S1 interface and locate the IE Cause in the
S1AP_UE_CONTEXT_REL_REQ message.
 If the value of this IE is radioNetwork:radio-connection-with-ue-lost, go to 2.
 If the value of this IE is not radioNetwork:radio-connection-with-ue-lost, the handover
parameters are set correctly. Contact Huawei technical support engineers.
2. Check the messages over the Uu interface for A4 measurement reports in RRC_MEAS_RPRT
messages prior to RRC_CONN_REL messages.
 If such reports cannot be found, this problem is due to inappropriate settings of handover
parameters. Go to 3.
 If such reports can be found, contact Huawei technical support engineers.
3. Run the MOD INTERFREQHOGROUP command to reconfigure the following parameters:
 Interfreq handover hysteresis
 CoverageBased Interfreq RSRP threshold
 CoverageBased Interfreq RSRQ threshold

7.6 Frequency-Priority-based Inter-Frequency Handover

7.6.1 When to Use Frequency-Priority-based Inter-Frequency Handover

Frequency-priority-based inter-frequency handover applies to the following scenario:

Some eNodeB sites use a high frequency band (for example, 2600 MHz) and a low band (for example,
900 MHz) as co-coverage bands. The high band is preferentially used to provide services, and the low
band is used to ensure continuous coverage.

In this scenario, frequency-priority-based inter-frequency handover can be used to hand over


UEs from the low to high band.

Note that frequency-priority-based inter-frequency handovers are performed to transfer UEs only
from the low band to the high band. If a UE needs to be handed over from the high band to the
low band, a coverage-based inter-frequency handover can be performed.

7.6.2 Required Information


To prevent failures in frequency-priority-based inter-frequency handovers, verify that blind handover is
disabled and the high and low bands have the same coverage.
Collect information about the coverage of the high and low bands. This information serves as a basis for
setting the thresholds used to trigger events A1, A2, and A4.
If blind handover is used in frequency-priority-based inter-frequency handover scenarios, collect
information about the neighboring cells to configure them with blind handover priorities in the range of 17
to 32.

7.6.3 Requirements
Operating Environment

None

Transmission Networking

None

License

None

7.6.4 Data Preparation


This section describes the data that you need to collect for setting parameters. Required data is data that
you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature
deployment scenario.
There are three types of data sources:

 Network plan (negotiation required): parameter values planned by the operator and negotiated
with the EPC or peer transmission equipment
 Network plan (negotiation not required): parameter values planned and set by the operator
 User-defined: parameter values set by users

Required Data

For details about the required data, see 7.2.4 Data Preparation.
Scenario-specific Data

Frequency-priority-based inter-frequency handover can be enabled only after coverage-based inter-


frequency handover is enabled. This section describes the required parameters except those for
coverage-based inter-frequency handover. For details on the required parameters for coverage-based
inter-frequency handover, see the "Scenario-specific Data" part in 7.2.4 Data Preparation.
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure
frequency-priority-based inter-frequency handover.

Parameter Parameter ID Data Setting Notes


Name Source
FreqPriorityHo CellAlgoSwitch.FreqPriority Network To enable frequency-priority-based inter-
Switch HoSwitch plan frequency handover in scenarios where the
(negotiat high and low bands have the same
ion not coverage under the same eNodeB and the
required low band has a smaller bandwidth, select
) the
FreqPriorIFHOSwitch(FreqPriorIFHOSwit
ch) check box. You are advised not to
select this check box for other scenarios.

To enable frequency-priority-based blind


handover, select the
FreqPriorIFBlindHOSwitch(FreqPriorIFBl
indHOSwitch) check box.

The following table describes the parameter that must be set in the EutranInterFreqNCell MO to
configure the blind handover priorities for inter-frequency neighboring cells.

Parameter Parameter ID Data Setting Notes


Name Source
Blind EutranInterFreqNCell.BlindHoPriority Network If this parameter value is set to 0,
handover plan blind handovers and frequency-
Priority (negotiation priority-based handovers cannot be
not performed. The values 1 to 16
required) indicate blind-handover priorities.
Multiple neighboring cells can be
configured with the same blind-
Parameter Parameter ID Data Setting Notes
Name Source
handover priority. If multiple
neighboring cells have the highest
blind-handover priority, the eNodeB
randomly selects one from them.
The values 17 to 32 indicate the
priorities for frequency-priority-
based handovers. Set this
parameter to a value ranging from 1
to 16 only for those inter-frequency
neighboring cells that have
overlapped coverage with the
serving cell. Set this parameter to a
larger value for a neighboring cell
that has wider overlapped coverage
or a lower frequency. Set this
parameter to 0 for all inter-
frequency neighboring cells if no
inter-frequency neighboring cells
have overlapped coverage with the
serving cell.

7.6.5 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of related parameters in a summary data file, which also contains other data for the new
eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file,
depending on the following conditions:

 Related managed objects (MOs) are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
 Some related MOs are not contained in a scenario-specific summary data file. In this situation,
customize a summary data file to include the MOs before you can set the parameters.

Related MOs and parameters in each scenario are listed as follows:

Table 7-15 Frequency-Priority-based Inter-Frequency Handover

MO Sheet in the Summary Parameter Group Remarks


Data File
CellAlgoSwitch User-defined sheet Based on Frequency Priority HO A list-type
Switch sheet is
CellAlgoSwitch is recommended.
recommended.
MO Sheet in the Summary Parameter Group Remarks
Data File
EutranExternalCell User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCell is Cell identity, Downlink EARFCN, recommended.
recommended. Uplink EARFCN indicator, Uplink
EARFCN, Physical cell identity,
Tracking area code, Cell name
EutranInterNFreq User-defined sheet Local cell identity, Downlink A list-type
EARFCN, Uplink EARFCN sheet is
EutranInterNFreq is configure indicator, Uplink recommended.
recommended. EARFCN, Inter frequency cell
resel priority configure indicator,
Inter frequency cell resel priority,
EUTRAN reselection time(s),
Speed dependent resel
parameter configuring indicator,
Scaling factor of treseleutra in
medium mobility state, Scaling
factor of treseleutra in high
mobility state, Measurement
bandwidth(MHz), Frequency
offset(dB), Inter frequency high
priority threshold(2dB), Inter
frequency lower priority
threshold(2dB), Minimum
required RX level(2dBm), PMAX
configure indicator, PMAX(dBm),
Neighbor cell config, Presence
antenna port1, Inter-Freq HO
trigger Event Type
EutranInterFreqNCell User-defined sheet Local cell identity, Mobile country A list-type
code, Mobile network code, sheet is
EutranInterFreqNCell is eNodeB identity, Cell identity, recommended.
recommended. Cell individual offset(dB), Cell
offset(dB), No handover indicator,
No remove indicator, Blind
handover Priority, ANR flag,
Local cell name, Neighbour cell
name
EutranExternalCellPlmn User-defined sheet Mobile country code, Mobile A list-type
network code, eNodeB identity, sheet is
EutranExternalCellPlmn Cell identity, Share mobile recommended.
is recommended. country code, Share mobile
network code
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a
single procedure. The procedure is as follows:
1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary
data file for batch reconfiguration.

NOTE:

For context-sensitive help on a current task in the client, press F1.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME
into the customized summary data file.
3. In the summary data file, set the parameters in the MOs listed in Table 7-15 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The
procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration
window.
2. In area 1 shown in Figure 7-6, select the eNodeB to which the MOs belong.
Figure 7-6 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.

Using MML Commands

1. Run the MOD CELLALGOSWITCH command to enable frequency-priority-based inter-


frequency handover.
2. Run the following commands to add neighbor relationships with inter-frequency E-UTRAN
cells:
a. ADD EUTRANINTERNFREQ
b. ADD EUTRANINTERFREQNCELL

NOTE:

Set EutranInterFreqNCell.BlindHOPriority to a value ranging from 17 to 32.

MML Command Examples


//Activating frequency-priority-based inter-frequency handover
MOD
CELLALGOSWITCH:LOCALCELLID=0,FREQPRIORITYHOSWITCH=FreqPriorIFHOSwitch-1;
//Adding inter-frequency neighboring E-UTRAN cells
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2860,
UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG,
SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG,
QqualMinCfgInd=NOT_CFG;
ADD EUTRANINTERFREQNCELL: LOCALCELLID=0, MCC="460", MNC="20",
ENODEBID=123, CELLID=1, BLINDHOPRIORITY=32;

7.6.6 Activation Observation


The observation procedure is as follows:

1. Trace messages over the Uu interface on the U2000 client after UEs access the network at the
center of a 900 MHz cell. Check the RRC_CONN_RECFG message. If the message contains
measurement configuration for a frequency-priority-based inter-frequency handover, you can
infer that frequency-priority-based inter-frequency handover has been activated.
2. After receiving a measurement report for event A1 from the UE, the eNodeB sends a
measurement configuration for event A4 to start the gap-assisted inter-frequency
measurement.
3. Trace messages over the Uu interface on the U2000 client. After receiving a measurement
report for event A4 from the UE, the eNodeB sends an RRC_CONN_RECFG message to the
UE for a frequency-priority-based inter-frequency handover. Check the RRC_CONN_RECFG
message. If the message contains target cell access information, you can infer that frequency-
priority-based inter-frequency handover has been triggered.

7.6.7 Deactivation
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs.
This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single
procedure. The procedure for feature deactivation is similar to that for feature activation described in
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify related
parameters described below.

Table 7-16 Parameters related to frequency-priority-based inter-frequency handover

MO Sheet in the Summary Parameter Group Setting Notes


Data File
CELLALGOSWITCH CELLALGOSWITCH Based on Frequency Clear the
Priority HO Switch FreqPriorIFHOSwitch
check box.
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in each scenario for a single eNodeB. For detailed instructions,
see Using the CME to Perform Single Configuration for feature activation.
Using MML Commands
To deactivate frequency-priority-based inter-frequency handover, disable its algorithm by running the
MOD CELLALGOSWITCH command.
MML Command Examples

//Deactivating frequency-priority-based inter-frequency handover


MOD CELLALGOSWITCH: LocalCellId=0,
FreqPriorityHoSwitch=FreqPriorIFHOSwitch-0;

7.6.8 Performance Monitoring


The handover success rate and service drop rate used for monitoring the performance of frequency-
priority-based inter-frequency handover are the same as those for monitoring the performance of
coverage-based inter-frequency handover. For details, see 7.2.8 Performance Monitoring.
Table 7-17 lists the counters related to frequency-priority-based inter-frequency and inter-mode handover.

Table 7-17 Counters related to frequency-priority-based inter-frequency and inter-mode handover

Counter ID Counter Name Counter Description


1526729482 L.HHO.InterFreq.FreqPri.PrepAttOut Number of frequency-priority-based
inter-frequency handover preparation
attempts
1526729483 L.HHO.InterFreq.FreqPri.ExecAttOut Number of frequency-priority-based
inter-frequency handover execution
attempts
1526729484 L.HHO.InterFreq.FreqPri.ExecSuccOut Number of successful frequency-
priority-based inter-frequency
handover executions
1526730006 L.HHO.InterFddTdd.FreqPri.PrepAttOut Number of frequency-priority-based
inter-duplex-mode handover
preparation attempts
1526730007 L.HHO.InterFddTdd.FreqPri.ExecAttOut Number of frequency-priority-based
inter-duplex-mode handover execution
attempts
1526730008 L.HHO.InterFddTdd.FreqPri.ExecSuccOut Number of successful frequency-
priority-based inter-duplex-mode
handover executions

7.6.9 Parameter Optimization


The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-frequency handovers. For details, see 7.2.9 Parameter
Optimization.
Inter-Frequency Handover Parameters

Inter-frequency handover parameters are contained in the InterFreqHoGroup MO.


Param Parameter ID Data Setting Notes
eter Source
Name
Local InterFreqHoGroup.LocalCellId Network Ensure that this parameter has been
cell ID plan set in a Cell MO based on the network
(negotia plan.
tion not
required
)
Load InterFreqHoGroup.InterFreqLoadBased Network This parameter specifies the RSRP
Based HoA4ThdRsrp plan threshold for event A4 for load-based,
Interfre (negotia frequency-priority-based, and service-
q tion not based inter-frequency handovers. A
RSRP required larger value causes a lower probability
threshol ) of triggering event A4. A smaller value
d causes a higher probability.

The value of this parameter must be


greater than the sum of the peer-end
RSRP threshold for event A2 for inter-
frequency measurement (set in the
InterFreqHoGroup MO at the peer
eNodeB) and the RSRP threshold
offset for event A2 for inter-frequency
measurement (set in the
CnOperatorHoCfg MO at the peer
eNodeB).
Load InterFreqHoGroup.InterFreqLoadBased Network This parameter specifies the RSRQ
Based HoA4ThdRsrq plan threshold for event A4 for load-based,
Interfrq (negotia frequency-priority-based, and service-
RSRQ tion not based inter-frequency handovers. A
threshol required larger value causes a lower probability
d ) of triggering event A4. A smaller value
causes a higher probability.

The value of this parameter must be


greater than the sum of the peer-end
RSRQ threshold for event A2 for inter-
frequency measurement (set in the
InterFreqHoGroup MO at the peer
eNodeB) and the RSRQ threshold
offset for event A2 for inter-frequency
measurement (set in the
CnOperatorHoCfg MO at the peer
eNodeB).
Freq InterFreqHoGroup.FreqPriInterFreqHo Network This parameter specifies the RSRP
Priority A1ThdRsrp plan threshold for event A1 for frequency-
Based (negotia priority-based inter-frequency
Interfre tion not handovers. A larger value causes a
q A1 required lower probability of triggering event A1.
RSRP )
Param Parameter ID Data Setting Notes
eter Source
Name

threshol A smaller value causes a higher


d probability.

Set this parameter based on the actual


conditions. You are advised to set this
parameter to the sum of peer-end
RSRP threshold for event A2 for inter-
frequency measurement (set in the
InterFreqHoGroup MO at the peer
eNodeB), the RSRP threshold offset for
event A2 for inter-frequency
measurement (set in the
CnOperatorHoCfg MO at the peer
eNodeB), RSRP difference between
frequency bands, and compensation (6
dB is recommended).
Freq InterFreqHoGroup.FreqPriInterFreqHo Network This parameter specifies the RSRQ
Priority A1ThdRsrq plan threshold for event A1 for frequency-
Based (negotia priority-based inter-frequency
Interfre tion not handovers. A larger value causes a
q A1 required lower probability of triggering event A1.
RSRQ ) A smaller value causes a higher
threshol probability.
d
Set this parameter based on the actual
conditions. You are advised to set this
parameter to the sum of the peer-end
RSRQ threshold for event A2 for inter-
frequency measurement (set in the
InterFreqHoGroup MO at the peer
eNodeB), RSRQ difference between
frequency bands, and compensation (3
dB is recommended).
Freq InterFreqHoGroup.FreqPriInterFreqHo Network This parameter specifies the RSRP
Priority A2ThdRsrp plan threshold for event A2 for frequency-
Based (negotia priority-based inter-frequency
Interfre tion not handovers. It is used in determining
q A2 required when to exit the gap-assisted
RSRP ) measurement triggered by frequency-
threshol priority-based inter-frequency
d handover.

The value of this parameter must be


(usually 4 dB) less than or equal to the
value of
InterFreqHoGroup.FreqPriInterFreqH
oA1ThdRsrp.
Freq InterFreqHoGroup.FreqPriInterFreqHo Network This parameter specifies the RSRQ
Priority A2ThdRsrq plan threshold for event A2 for frequency-
Param Parameter ID Data Setting Notes
eter Source
Name

Based (negotia priority-based inter-frequency


Interfre tion not handovers. It is used in determining
q A2 required when to exit the gap-assisted
RSRQ ) measurement triggered by frequency-
threshol priority-based inter-frequency
d handover.

The value of this parameter must be


(usually 2 dB) less than or equal to the
value of
InterFreqHoGroup.FreqPriInterFreqH
oA1ThdRsrq.
Intra-RAT Handover

Intra-RAT handover parameters are contained in the IntraRatHoComm MO.

Parameter Parameter ID Data Setting Notes


Name Source
A1 IntraRatHoComm.FreqPriInterFreqHoA1TrigQuan Network This parameter
Measurement plan specifies the
trigger (negotiation triggering quantity
quantity of not for events A1 and
Freq Priority required) A2 for frequency-
priority-based inter-
frequency
measurement. The
quantity can be
either RSRP or
RSRQ. The
measured RSRP
values are stable,
slightly varying with
the load, and
therefore there is
little signal
fluctuation. The
measured RSRQ
values vary with the
load and are likely
to reflect the signal
quality of the cell in
real time.

It is recommended
that the default
value be used if the
traffic load of LTE
cells is not stable.
Parameter Parameter ID Data Setting Notes
Name Source
FreqPrior IntraRatHoComm.InterFreqHoA4TrigQuan Network This parameter
loadBased plan specifies the event
A4 (negotiation A4 triggering
Measurement not quantity for inter-
trigger required) frequency
quantity handovers other
than coverage-
based inter-
frequency
handovers. The
quantity can be
either RSRP or
RSRQ, or both. The
measured RSRP
values are stable,
slightly varying with
the load, and
therefore there is
little signal
fluctuation. The
measured RSRQ
values vary with the
load and are likely
to reflect the signal
quality of the cell in
real time.

It is recommended
that the default
value be used if the
traffic load of LTE
cells is not stable.

7.6.10 Troubleshooting
Fault description

An eNodeB may not initiate a handover procedure upon receipt of an event A1 measurement
report.

Fault handling

Perform the following steps to determine whether the blind handover priorities for neighboring
cells are accurate:

1. Run the LST EUTRANINTERFREQNCELL command to list the inter-frequency neighboring


cells. Check the list for cells whose blind handover priorities range from 17 to 32.
 If such cells cannot be found, go to 2.
 If such cells can be found, contact Huawei technical support engineers.
2. Run the MOD EUTRANINTERFREQNCELL command to change the blind handover priorities
of neighboring cells for frequency-priority-based blind handovers to a value in the range from
17 to 32.

8 Reference Documents
1. 3GPP TS 36.331, "RRC Protocol Specification"
2. 3GPP TS 36.300, "E-UTRAN Overall description"
3. 3GPP TS 36.423, "X2 Application Protocol"
4. 3GPP TS 36.413, "S1 Application Protocol"
5. 3GPP TS 23.203, "Policy and charging control architecture"
6. 3GPP TS 36.104, "Base Station (BS) radio transmission and reception"
7. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
8. Idle Mode Management
9. ANR Management
10. MLB
11. ICIC
12. SRVCC