Mobility Management in Connected Mode (ERAN3.0 - 07)
Mobility Management in Connected Mode (ERAN3.0 - 07)
eRAN3.0
Feature Parameter Description
Issue 07
Date 2013-05-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
eRAN
Mobility Management in Connected Mode Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
4 Intra-Frequency Handover......................................................................................................4-1
4.1 Cause of an Intra-Frequency Handover ........................................................................................ 4-1
4.1.1 Coverage-based Handover .................................................................................................. 4-1
4.1.2 Load-based Handover .......................................................................................................... 4-1
4.2 Measurement Phase of an Intra-Frequency Handover ................................................................. 4-1
4.2.1 Intra-Frequency Measurement Configuration....................................................................... 4-2
4.2.2 Event A3 Triggering .............................................................................................................. 4-3
4.3 Decision Phase of an Intra-Frequency Handover ......................................................................... 4-4
4.4 Execution Phase of an Intra-Frequency Handover ....................................................................... 4-5
4.4.1 Execution Policy ................................................................................................................... 4-5
4.4.2 Retry and Penalty ................................................................................................................. 4-5
4.5 Signaling Procedure of a Typical Intra-Frequency Handover ....................................................... 4-6
5 Inter-Frequency Handover......................................................................................................5-1
5.1 Measurement Triggering/Stopping Phase of an Inter-Frequency Handover ................................ 5-1
5.1.1 Coverage-based Handover .................................................................................................. 5-1
5.1.2 Load-based Handover .......................................................................................................... 5-4
5.1.3 Frequency-Priority-based Handover .................................................................................... 5-4
5.1.4 Distance-based Handover .................................................................................................... 5-6
5.1.5 Service-based Handover ...................................................................................................... 5-7
5.1.6 UL-Quality-based Handover ................................................................................................. 5-8
5.2 Measurement Phase of an Inter-Frequency Handover ................................................................. 5-9
5.2.1 Inter-Frequency Measurement Configuration....................................................................... 5-9
5.2.2 Setup of Measurement Gaps.............................................................................................. 5-10
5.2.3 Inter-Frequency Handover Triggering ................................................................................ 5-10
5.3 Decision Phase of an Inter-Frequency Handover ....................................................................... 5-13
5.4 Execution Phase of an Inter-Frequency Handover ..................................................................... 5-13
5.5 Signaling Procedure of a Typical Inter-Frequency Handover ..................................................... 5-13
5.5.1 Signaling Procedure of a Successful Handover ................................................................. 5-13
5.5.2 RRC Connection Re-Establishment After a Handover Failure ........................................... 5-14
10 Parameters .............................................................................................................................10-1
11 Counters ..................................................................................................................................11-1
12 Glossary ..................................................................................................................................12-1
13 Reference Documents .........................................................................................................13-1
1 Introduction
1.1 Scope
Mobility management is performed to support mobility of user equipment (UEs). It informs the network of
the UEs' current locations, provides the network with UE identities, and maintains physical channels. In
an evolved UTRAN (E-UTRAN), mobility management can be performed in connected mode or idle
mode, depending on Radio Resource Control (RRC) states.
This document describes mobility management in connected mode. In this mode, the mobile network
ensures continuity of physical channels and provides uninterrupted communication service for UEs in
connected mode through handovers when the UEs are moving in the network. A handover is a
procedure where the serving cell of a UE in connected mode is changed. Handovers can be classified as
follows: intra-frequency, inter-frequency, and inter-RAT.
Unless otherwise specified, "handover" in this document is a generic term including the handover, cell
change order (CCO), and redirection procedures.
In idle mode a UE is powered on but does not have an RRC connection to the radio network. When idle,
UEs report their locations to the network, and the E-UTRAN NodeB (eNodeB) broadcasts system
information, which can be used by UEs to select suitable cells. For details about mobility management in
idle mode, see Idle Mode Management Feature Parameter Description.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
Document Issues
The document issues are as follows:
07 (2013-05-20)
06 (2013-02-27)
05 (2012-12-29)
04 (2012-09-20)
03 (2012-06-30)
02 (2012-05-11)
07 (2013-05-20)
Compared with issue 06 (2013-02-27) of eRAN3.0, issue 07 (2013-05-20) of eRAN3.0 includes the
following changes.
06 (2013-02-27)
Compared with issue 05 (2012-12-29) of eRAN3.0, issue 06 (2013-02-27) of eRAN3.0 includes the
following changes.
05 (2012-12-29)
Compared with issue 04 (2012-09-20) of eRAN3.0, issue 05 (2012-12-29) of eRAN3.0 includes the
following changes.
04 (2012-09-20)
Compared with issue 03 (2012-06-30) of eRAN3.0, issue 04 (2012-09-20) of eRAN3.0 includes the
following changes.
03 (2012-06-30)
Compared with issue 02 (2012-05-11) of eRAN3.0, issue 03 (2012-06-30) of eRAN3.0 includes the
following changes.
02 (2012-05-11)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-05-11) of eRAN3.0 includes the
following changes.
01 (2012-03-30)
This is the first official release.
Draft A (2012-01-10)
This is a draft.
Compared with issue 02 (2011-12-24) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.
2.1 Introduction
Handover Types By Handover Target
Handovers are classified by handover target into the following types: intra-frequency, inter-frequency,
and inter-RAT.
Intra-frequency handover
An intra-frequency handover is performed between cells on the same frequency in the LTE system. A
network may use one frequency in different geographical areas, and therefore the eNodeB needs to
support handovers within one frequency in the system.
Inter-frequency handover
An inter-frequency handover is performed between cells on different frequencies in the LTE system. A
network may use different frequencies, and therefore the eNodeB needs to support handovers
between different frequencies within the system.
Handovers between LTE FDD cells and LTE TDD cells are inter-mode handovers and follow the
common inter-frequency handover procedure.
Inter-RAT handover
An inter-RAT handover is performed from LTE to any of the following RATs:
− Global System for Mobile communications (GSM)
− Wideband Code Division Multiple Access (WCDMA)
− Time Division-Synchronous Code Division Multiple Access (TD-SCDMA)
− Code Division Multiple Access 2000 (CDMA2000)
Different areas may be covered by different systems, and therefore LTE supports handovers between
different RATs to ensure uninterrupted service provision.
2.2 Benefits
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
Figure 2-2 shows the network architecture for mobility management in connected mode. Standardized
interfaces are used in the communication between eNodeBs, eNodeB and mobility management entity
(MME), and eNodeB and UEs.
S1 interface
The eNodeB and MME/serving gateway (S-GW) communicate through the S1 interface. In an
inter-eNodeB handover for which an X2 interface is unavailable between the source and target
eNodeBs, or in an inter-RAT handover to UTRAN or GREAN, handover signaling is exchanged
through the S1 interface. For details about the S1 interface, see 3GPP TS 36.413 V10.1.0 (2011-03).
3GPP is short for 3rd Generation Partnership Project.
X2 interface
eNodeBs communicate with each other through the X2 interface. In an inter-eNodeB handover
for which an X2 interface is available between the source and target eNodeBs, handover signaling is
exchanged through the X2 interface. For details about the X2 interface, see 3GPP TS 36.423 V10.1.0
(2011-03).
Uu interface
The eNodeB and UEs communicate through the Uu interface. The Uu interface is also called the radio
interface. For details about the Uu interface, see 3GPP TS 36.331 V10.1.0 (2011-03).
NOTE
Redirection control shown in Figure 3-1 is irrelevant to handovers. This type of redirection and the cell reselection priority
are not described in this document. For details about these entities, see Idle Mode Management Feature
Parameter Description, Admission and Congestion Control Feature Parameter Description, and S1-Flex Feature
Parameter Description.
Target System
For measurement of the serving cell or an intra-frequency neighboring cell, the target system is
E-UTRAN.
For an inter-frequency measurement, the eNodeB determines the target system based on the UE
measurement capability. If the UE supports inter-frequency measurement in connected mode, the
target system is E-UTRAN.
For an inter-RAT measurement, the eNodeB determines the target system based on the UE
measurement capability as follows:
− If the UE supports measurement of UTRAN frequencies, the target system can be UTRAN.
− If the UE supports measurement of GERAN frequencies, the target system can be GERAN.
− If the UE supports measurement of CDMA2000 frequencies, the target system can be CDMA2000.
Target Frequency
The eNodeB determines target frequencies based on a list of neighboring cells in the selected target
system. If the service is an emergency call, the eNodeB determines the target frequencies based on the
complete neighboring cell list. If the service is not an emergency call, the eNodeB determines the target
frequencies based on the neighboring cell list that excludes the following cells:
Blacklisted neighboring cells
Neighboring cells that have a different PLMN from the serving cell, if the inter-PLMN handover switch
is turned off
For details about inter-PLMN handovers, see section 3.9 "Inter-PLMN Handovers."
Neighboring cells with a handover prohibition flag
Neighboring cells in the areas indicated by the information element (IE) Handover Restriction List in
the INITIAL CONTEXT SETUP REQUEST message sent from the MME
NOTE
If ANR is enabled, the eNodeB does not determine target frequencies based on the neighboring cell list. For details, see
ANR Management Feature Parameter Description.
The number of inter-frequency and inter-RAT frequencies configured on an eNodeB should not exceed the number
specified in 3GPP TS 36.133 (see section 8.1.2.1 in 3GPP TS 36.133 Release 10 issued in December, 2010). If the
number of configured inter-frequency and inter-RAT frequencies exceeds the limit, certain frequencies cannot be
measured by UEs.
Measurement Gap
A measurement gap is a time period during which the UE performs measurements on a neighboring
frequency of the serving frequency. Measurement gaps are applicable to inter-frequency and inter-RAT
measurements. The UE performs inter-frequency or inter-RAT measurements only within the
measurement gaps. In most cases, one UE has only one receiver, and consequently one UE can receive
the signals on only one frequency at a time. For details about measurement gaps, see section 10.1.3 in
3GPP TS 36.300 Release 10 issued in March 2011.
When inter-frequency or inter-RAT measurements are required, the eNodeB delivers the measurement
gap configuration, and then the UE starts gap-assisted measurements accordingly. As shown in Figure
3-3, Tperiod denotes the repetition period of measurement gaps, and TGAP denotes the
gap width, within which the UE performs measurements.
When gap-assisted measurements for various handover types co-exist, the eNodeB records the
measurements based on these types. Different gap-assisted measurements can share the same
measurement gap configuration. A UE releases measurement gaps only after all gap-assisted
measurements are stopped.
Two measurement gap patterns are available: pattern 1 and pattern 2. In pattern 1, TGAP is 6 ms and
Tperiod is 40 ms. In pattern 2, TGAP is 6 ms and Tperiod is 80 ms. The pattern to use is specified by the
HoMeasComm.GapPatternType parameter.
In the case of an intra-MME inter-eNodeB handover (handover between eNodeB 1 and eNodeB 2 shown
in Figure 3-4), the source eNodeB checks whether the X2 interface is available between the source and
target eNodeBs or not and then automatically selects a path for the handover as follows:
If the X2 interface is available, the handover request is sent over the X2 interface. Data forwarding is
also performed over the X2 interface.
If the X2 interface is unavailable, the handover request is sent over the S1 interface. Data forwarding
is also performed over the S1 interface.
In the case of an inter-MME inter-eNodeB handover (handover between eNodeB 1 and eNodeB 3 shown
in Figure 3-4), the handover request is sent over the S1 interface. In addition, the source eNodeB
checks whether the X2 interface is available between the source and target eNodeBs or not and then
automatically selects a path for data forwarding as follows:
If the X2 interface is available, data forwarding is performed over the X2 interface.
If the X2 interface is unavailable, data forwarding is performed over the S1 interface.
In the case of an inter-RAT handover to the UTRAN or GERAN, the eNodeB sends a handover request
and forwards data over the S1 interface.
In the case of an inter-RAT handover to CDMA2000 High Rate Packet Data (HRPD), either an optimized
handover or a non-optimized handover is applicable, depending on whether the pre-registration of the
UE to the target CDMA2000 HRPD system has succeeded or not. If the pre-registration to the target
CDMA2000 HRPD system has succeeded, an optimized handover is executed, in which the eNodeB
sends the handover request over the S1 interface. If the pre-registration has failed, a non-optimized
handover is executed, in which the UE sends the handover request.
NOTE
A prepared cell can be one of the following cells: the source cell, a cell towards which handover preparation has been
performed, and a cell under the same eNodeB as either of the preceding cell.
To reduce delay, the eNodeB may select a target cell for handover in the absence of the measurement
information. This type of handover is called a blind handover. The candidate cells for a blind handover
must be the neighboring cells with blind-handover priorities other than priority 0. For details about the
parameters for blind-handover priorities, see section 3.7 "Blind Handovers."
In the configuration of inter-frequency neighboring cells, the EutranInterFreqNCell.BlindHoPriority
parameter is also used to differentiate between inter-frequency neighboring cells for
frequency-priority-based handovers and those for handovers triggered by other causes. Values 17 to 32
of this parameter are dedicated to frequency-priority-based inter-frequency handovers. A
frequency-priority-based inter-frequency handover can be triggered only if the target inter-frequency
neighboring cell is configured with a blind-handover priority in the range of 17 to 32. Blind-handover
priorities 0 to 16 apply to inter-frequency handovers triggered by causes other than frequency priorities.
NOTE
Ensure that neighboring cells are correctly configured. Otherwise, a handover (a generic term including the handover,
CCO, and redirection procedures) cannot be triggered.
3.6 Redirection
Redirection is a method of transferring UEs between cells and is a type of handover when "handover" is
used as a generic term. When a handover cannot be performed in an emergency or due to equipment
limitations, the eNodeB sends the UE an RRC Connection Release message, which contains
information about a neighboring frequency in the LTE system or in another RAT system. Using this
message, the eNodeB instructs the UE to initiate a random access procedure towards an inter-frequency
or inter-RAT neighboring cell so that the UE can resume its services.
− CSFallBackBlindHoCfg.InterRatSecondPri
− CSFallBackBlindHoCfg.InterRatLowestPri
2. If UTRAN is selected as the target system that supports E-UTRAN to UTRAN CS/PS steering, the
eNodeB determines the target frequency based on whether the UE is performing PS or CS services:
− If
a coverage-based inter-RAT blind handover to UTRAN is triggered for a UE that is performing PS
services, the eNodeB hands over the UE preferentially to a frequency with a high PS service priority.
The UtranNFreq.PsPriority parameter specifies the PS service priorities.
− If
a blind handover is triggered for CSFB to UTRAN, the eNodeB hands over the UE preferentially to
a frequency with a high CS service priority. The UtranNFreq.CsPriority parameter specifies the CS
service priorities.
4 Intra-Frequency Handover
An intra-frequency handover consists of the following phases:
Measurement phase
The UE performs measurements according to the measurement configuration delivered from the
eNodeB. When the signal quality in at least one intra-frequency neighboring cell meets the configured
triggering condition of event A3, the UE sends the measurement result to the eNodeB.
Decision phase
The eNodeB generates a list of candidate cells and makes a handover decision based on the
measurement result.
Execution phase
The handover from the serving cell to the target cell is executed.
The coverage- and load-based intra-frequency handovers use the same procedures. The major
difference between them is the cause of the handover.
If the RRC connection re-establishment fails, the UE enters the idle mode. A failed re-establishment
procedure, according to Figure 4-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 re-establishment of the RRC connection.
2. The eNodeB responds with an RRC Connection Reestablishment Reject message to indicate that it
rejects the request.
Figure 4-4 Failed RRC connection re-establishment procedure
5 Inter-Frequency Handover
An inter-frequency handover consists of the following phases:
Measurement triggering/stopping phase
The measurement triggering/stopping phase varies according to the cause of the inter-frequency
handover.
Measurement phase
The eNodeB delivers the inter-frequency measurement configuration to the UE, and the UE performs
inter-frequency measurements accordingly. When the signal quality in at least one inter-frequency
neighboring cell meets the configured triggering condition of event A4, the UE reports the
measurement results.
Decision phase
The eNodeB checks the measurement results and generates a list of candidate cells.
Execution phase
The handover from the serving cell to the target cell is executed.
After event A2 is reported, the eNodeB delivers the measurement configuration related to event A3, A4,
or A5 to the UE. For details about the triggering of inter-frequency handovers, see section 5.2.3
"Inter-Frequency Handover Triggering."
As shown in Figure 5-4, F1 and F2 indicate two frequencies: Cell 1 uses F1, and Cells 2, 3, and 4 all use
F2. The gray area in the figure (Cell 1) is covered by F1, while the light yellow area (Cells 2, 3, and 4) is
covered by F2. It is obvious that cell 1 exerts cross-cell coverage to the other three cells.
Assume that the UE moves along the direction indicated by the arrow. As the UE moves, F1 provides
sustained signal quality and therefore inter-frequency measurements are not triggered for the UE
even when the UE has been in the coverage of F2 for a long time. Gradually, the UE enters the overlap
coverage between Cell 1 and Cell 4. Considering the long distance between the two cells, it is unlikely
that Cell 4 is configured as a neighboring cell of Cell 1. As a result, as soon as the UE leaves the
coverage of Cell 1, it experiences a call drop. To prevent such a call drop and ensure service continuity,
the UE should have been handed over to F2 earlier.
Before delivering the measurement configuration related to event A4 and the measurement gap
configuration, the eNodeB checks whether the measurement gap has been activated for use in other
types of handovers. If the measurement gap has been activated, the eNodeB delivers only the
measurement configuration related to event A4. If not, the eNodeB delivers both.
If a UE has performed gap-assisted measurements for a service-based inter-frequency handover for a
long time but fails to trigger such a handover, the eNodeB releases the measurement gaps for
service-based inter-frequency handovers to stop the measurements.
Event A3 Triggering
For details about how event A3 is triggered, see section 4.2.2 "Event A3 Triggering" about
intra-frequency handovers.
Event A3 in inter-frequency handovers uses the same set of parameters with that in intra-frequency
handovers, except the offset and frequency-specific offset. Specifically, the offset for this event A3 is
specified by the InterFreqHoGroup.InterFreqHoA3Offset parameter and applies to all inter-frequency
handovers triggered by this event A3, and the frequency-specific offset is specified by the
EutranInterNFreq.QoffsetFreq parameter for each neighboring E-UTRAN frequency.
The measurement quantities for events A1 and A2 are both RSRP. The RSRP thresholds for triggering
events A1 and A2 are specified by the InterFreqHoGroup.A3InterFreqHoA1ThdRsrp and
InterFreqHoGroup.A3InterFreqHoA2ThdRsrp parameters, respectively.
Event A4 Triggering
The triggering of event A4 indicates that the signal quality is higher than a specified threshold in at least
one neighboring cell. Section 5.5.4.5 in 3GPP TS 36.331 Release 10 issued in March 2011 defines the
entering and leaving conditions of event A4 as follows:
Entering condition: Mn + Ofn + Ocn - Hys > Thresh
Leaving condition: Mn + Ofn + Ocn + Hys < Thresh
The variables in the preceding formulas are described as follows:
NOTE
If the IntraRatHoComm.InterFreqHoA4TrigQuan parameter is set to BOTH, both the RSRP- and RSRQ-based
measurement configurations are delivered. If the IntraRatHoComm.InterFreqHoA4RprtQuan parameter is set to BOTH,
an inter-frequency handover can be triggered only when neither of the RSRP- and RSRQ-based measurement results of a
neighboring cell meets the leaving condition of event A4.
Figure 5-5 shows the event A4 triggering mechanism. When the RSRP- or RSRQ-based measurement
result meets the triggering condition of event A4, the UE reports the information about the cell where the
event is triggered, to ensure that the inter-frequency handover is triggered in a timely fashion.
Figure 5-5 Event A4 triggering mechanism
According to section 5.5.4.3 in 3GPP TS 36.331 Release 10 issued in March 2011, the following
A4-related parameters are provided in the reporting configuration of the measurement configuration:
IntraRatHoComm.InterFreqHoA4RprtQuan: specifies the reporting quantity for inter-frequency
handover event A4. This refers to the quantity to be included in the measurement reports.
IntraRatHoComm.InterFreqHoRprtInterval: specifies the interval between the reports that are
triggered by event A4. This parameter controls the frequency of the periodical measurement reports
sent by the UE. This reduces the signaling load on the radio interface.
IntraRatHoComm.IntraRATHoMaxRprtCell: specifies the maximum number of cells to be included in
the measurement report for an intra-RAT handover. In the case of event A4 for an inter-frequency
handover within the E-UTRAN, this parameter specifies the maximum number of cells to be included
in the measurement report of event A4. The limitation on the number of cells to be reported can save
resources on the radio interface.
IntraRatHoComm.IntraRATHoRprtAmount: specifies the number of event-triggered periodical
reports for an intra-RAT handover. The number of event-triggered periodical reports is set to restrict
handover retries.
6 Inter-RAT Handover
An inter-RAT handover consists of the following phases:
Measurement triggering/stopping phase
The measurement triggering/stopping phase varies according to the cause of the inter-RAT handover.
Measurement phase
The eNodeB delivers the inter-RAT measurement configuration, and the UE performs inter-RAT
measurements accordingly. When the signal quality in at least one inter-RAT neighboring cell meets
the configured triggering condition of event B1, the UE reports the measurement results.
Decision phase
The eNodeB checks the measurement results and generates a list of candidate cells.
Execution phase
The handover from the serving cell to the target cell is executed.
The coverage-, load-, service-, UL-quality-based, and distance-based inter-RAT handovers use the
same procedure except for the measurement triggering/stopping phase.
This chapter describes the following optional features:
LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN
LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000
LOFD-001022 SRVCC to UTRAN
LOFD-001023 SRVCC to GERAN
After receiving an event A2 report that triggers inter-RAT measurements, the eNodeB delivers the
measurement configuration related to event B1 to the UE. For details, see section 6.2.4 "Inter-RAT
Handover Triggering."
After receiving an event A2 report that triggers a blind handover, the eNodeB starts a blind handover.
This blind handover is achieved only by performing a CCO or redirection procedure, because an event
A2-triggered blind handover indicates an urgent situation where the serving cell cannot provide the
required service quality.
When the measurement gaps for coverage-based inter-RAT handovers are released, the gap-assisted
measurements for other types of handovers are not affected. The measurement gap configuration stops
only when all gap-assisted measurements are stopped.
Event B1 Triggering
The triggering of event B1 indicates that the signal quality is higher than a specified threshold in at least
one neighboring cell. Section 5.5.4.7 in 3GPP TS 36.331 Release 10 issued in March 2011 defines the
entering and leaving conditions of event B1 as follows:
Entering condition: Mn + Ofn - Hys > Thresh
Leaving condition: Mn + Ofn + Hys < Thresh
The variables in the preceding formulas are described as follows:
Mn is the measurement result of the neighboring cell.
Ofn is the frequency-specific offset for the frequency of the neighboring cell. It is specified by the
UtranNFreq.OffsetFreq parameter, which is contained in the associated measurement object IE in
the measurement configuration.
Hys is the hysteresis for event B1. The hysteresis values for inter-RAT handovers to UTRAN, GERAN,
and CDMA2000 (specified by the InterRatHoUtranGroup.InterRATHoUtranB1Hyst,
InterRatHoGeranGroup.InterRATHoGeranB1Hyst, and
InterRatHoCdmaHrpdGroup.InterRATHoCDMAB1Hyst parameters respectively) are included in the
delivered measurement configuration.
Thresh is the threshold for event B1. The values of Thresh are set on the basis of the measurement
quantities for each RAT.
Figure 6-3 shows the event B1 triggering mechanism. Triggering of event A2 is based on the E-UTRAN
quantity (RSRP or RSRQ). Triggering of event B1 is based on the measurement quantities and
thresholds listed in Table 6-1. The measurement quantity for UTRAN can be RSCP, Ec/No, or both as
specified by the InterRatHoComm.InterRATHoUtranB1MeasQuan parameter. When
InterRatHoComm.InterRATHoUtranB1MeasQuan is set to UTRAN_BOTH, the eNodeB delivers both
RSCP and Ec/No measurement quantities to the UE.
NOTE
Section 5.5.5 in 3GPP TS 36.331 Release 10 issued in March 2011 specifies that UEs can report RSCP and Ec/No
quantities of the UTRAN at the same time. For UEs that are compliant with earlier releases, the eNodeB sends only the
RSCP-related measurement configuration to the UEs even if the InterRatHoComm.InterRATHoUtranB1MeasQuan
parameter is set to UTRAN_BOTH.
When the quantity-based measurement result meets the triggering condition of event B1, the UE reports
the information about the cell where the event is triggered to ensure that the inter-RAT handover is
triggered in a timely fashion. The time-to-trigger for event B1 related to handovers to UTRAN, GERAN,
and CDMA2000 is specified by the InterRatHoUtranGroup.InterRATHoUtranB1TimeToTrig,
According to section 5.5.4.7 in 3GPP TS 36.331 Release 10 issued in March 2011, the following
B1-related parameters are provided in the reporting configuration of the measurement configuration:
InterRatHoComm.InterRATHoUtranRprtInterval,
InterRatHoComm.InterRATHoGeranRprtInterval, and
InterRatHoComm.InterRATCDMAHRPDRprtInterval: specify the interval between the reports that
are triggered by event B1. This parameter controls the frequency of the periodical measurement
reports sent by the UE. This reduces the signaling load on the radio interface.
InterRatHoComm.InterRATHoMaxRprtCell: specifies the maximum number of cells to be included in
the measurement report of event B1 for an inter-RAT handover. The limitation on the number of cells to
be reported can save resources on the radio interface.
InterRatHoComm.InterRATHoRprtAmount: specifies the number of periodical reports to be sent
after event B1 is triggered. The number of event-triggered periodical reports is set to restrict handover
retries.
Event B2 Triggering
The triggering of event B2 indicates that the signal quality in the serving cell is lower than a specified
threshold and the signal quality in at least one neighboring cell is higher than another specified threshold.
Section 5.5.4.8 in 3GPP TS 36.331 Release 10 issued in March 2011 defines the entering and leaving
conditions of event B2 as follows:
Entering condition: Ms + Hys < Thresh 1 and Mn + Ofn - Hys > Thresh 2
Leaving condition: Ms - Hys > Thresh 1 or Mn + Ofn + Hys < Thresh 2
Event B2 uses the same set of parameters as event B1 except four parameters: the triggering quantity
related to Thresh 1, the measurement quantity related to Thresh 2, Thresh 1, and Thresh 2. For details
about the four parameters, see Table 6-2 and Table 6-3.
Table 6-2 Thresh 1 for event B2
Triggering Quantity Thresh 1
Same as the triggering RSRP InterRatHoCommGroup.InterRatHoA2ThdRSRP
quantity for event A2
RSRQ InterRatHoCommGroup.InterRatHoA2ThdRSRQ
NOTE
Do not change the inter-RAT handover policy for each QCI unless necessary.
A bearer with a QCI of 1 carries VoIP services. Redirection for QCI 1 will affect user experience with VoIP services. If the
target system does not support VoIP services, you are advised not to enable redirection for VoIP services.
The eNodeB determines the handover policy to use based on the following factors: enabled handover
policies under the ENodeBAlgoSwitch.HoModeSwitch parameter, QCI of the radio bearer of the UE,
UE capabilities, and target RAT. The eNodeB selects from the enabled handover policies in descending
order: PS handover, SRVCC, CCO/NACC, and redirection. SRVCC can be triggered only if the UE is
using VoIP services and supports SRVCC. Figure 6-4 shows the flowchart for handover policy selection.
7 Related Features
7.1 Intra-Frequency Handover
7.1.1 Required Features
Load-based intra-frequency handovers are triggered by the intra-frequency mobility load balancing (MLB)
function. For details about the triggering causes, see MLB Feature Parameter Description.
During an intra-frequency handover, the UE needs to initiate a random access procedure to the target
E-UTRAN cell. For details about random access procedures, see Connection Management Feature
Parameter Description.
9 Engineering Guidelines
This chapter provides engineering guidelines for mobility management in connection mode.
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.
(Optional, required only if the home eNodeB of the external E-UTRAN cell works in eRAN 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.
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.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
configure coverage-based intra-frequency handover.
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.
The following table describes the parameter that must be set in the CellExtendedQci MO to configure
parameter groups for services with extended QCIs.
For details about the index of the intra-frequency parameter group and the corresponding thresholds,
see section 9.1.7 "Reconfiguration".
Transmission Networking
Coverage-based intra-frequency handovers have no requirements for transmission networking.
License
Coverage-based intra-frequency handovers have no requirements for licenses.
9.1.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.1.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-1 Coverage-based Intra-Frequency Handover
MO Parameter Group Parameter
Name
ENODEBALG ENodeBAlgoSwitch Handover Algo switch
OSWITCH
EUTRANEXT EutranInterFreqNCell Mobile country code, Mobile network code, eNodeB identity,
ERNALCELL Cell identity, Downlink EARFCN, Uplink EARFCN indicator,
Uplink EARFCN, Physical cell identity, Tracking area code,
Cell name
EUTRANEXT EutranExternalCellPl Mobile country code, Mobile network code, eNodeB identity,
ERNALCELL mn Cell identity, Share mobile country code, Share mobile
PLMN network code
EUTRANINT EutranIntraFreqNCell Local cell identity, Mobile country code, Mobile network
RAFREQNCE code, eNodeB identity, Cell identity, Cell individual
LL offset(dB), Cell offset(dB), No handover indicator, No
remove indicator, ANR flag, Local cell name, Neighbour cell
name
For detailed parameter configuration for intra-frequency neighboring cells, see the "Required Data" part
in 9.1.3 Data Preparation.
9.1.8 Deactivation
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.
Hysteresis
The hysteresis in event A3 for coverage-based intra-frequency handovers is specified by the
IntraFreqHoGroup.IntraFreqHoA3Hyst parameter. This parameter determines the strictness of the
conditions for entering or leaving event A3. Tune this parameter to minimize the probability of frequently
entering and leaving event A3.
A larger value for the IntraFreqHoGroup.IntraFreqHoA3Hyst parameter makes it more difficult to
meet the conditions for entering and leaving event A3. As a result, it is less probable for UEs to
frequently enter and leave event A3.
CIO
The CIO for an intra-frequency neighboring cell is included in event A3 measurement reports, and it is
specified by the EutranInterFreqNCell.CellIndividualOffset parameter in the configuration data for this
neighbor relationship. This cell-level parameter varies according to the serving cell and its neighboring
cells. Each UE adds the CIO to the measurement results of the serving cell and neighboring cells. The
UE considers this sum when making handover decisions. This measure is equivalent to relocating cell
borders. EutranInterFreqNCell.CellIndividualOffset also determines the handover threshold. Tune
this parameter for handovers between a serving cell and its neighboring cells without affecting the
handover thresholds for other cells.
Adding the CIO to the measurement result of the serving cell raises the probability of handovers from
the serving cell.
Adding the CIO to the measurement result of a neighboring cell raises the probability of handovers to
this cell.
If signal quality fluctuates, tune the EutranInterFreqNCell.CellIndividualOffset parameter as follows:
To increase the probability of handovers from a serving cell, decrease the value of this parameter.
To increase the probability of handovers to a neighboring cell, increase the value of this parameter.
This measure improves handover performance and reduces the risk of call drops.
Time-to-Trigger
The IntraFreqHoGroup.IntraFreqHoA3TimeToTrig parameter specifies whether to allow UEs to
promptly report measurement results. If measurement reporting is always delayed, decrease the value
of this parameter to ensure prompt measurement reporting. If the RSRP fluctuates greatly and ping-pong
handovers occur as a result, increase the value of this parameter to reduce the impact of signal
fluctuations.
9.1.11 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:
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.
(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 section 9.1.3 "Data Preparation".
(Optional, required only if the home eNodeB of the external E-UTRAN cell works in eRAN 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 section 9.1.3 "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.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
configure coverage-based inter-frequency handover.
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.
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.
Transmission Networking
None.
License
None.
9.2.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.2.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-2 Coverage-based Inter-Frequency Handover
MO Parameter Group Name Parameter
ENODEBALGOS ENodeBAlgoSwitch Handover Algo switch
WITCH
EUTRANEXTER EutranInterFreqNCell Mobile country code, Mobile network code, eNodeB
NALCELL identity, Cell identity, Downlink EARFCN, Uplink
EARFCN indicator, Uplink EARFCN, Physical cell
identity, Tracking area code, Cell name
EUTRANEXTER EutranExternalCellPlmn Mobile country code, Mobile network code, eNodeB
NALCELLPLMN identity, Cell identity, Share mobile country code,
Share mobile network code
EUTRANINTER EutranInterNFreq Local cell identity, Downlink EARFCN, Uplink
NFREQ EARFCN configure 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 antenna port1, Inter-Freq HO
trigger Event Type
EUTRANINTER EutranInterFreqNCell Local cell identity, Mobile country code, Mobile
network code, eNodeB identity, Cell identity, Cell
9.2.7 Reconfiguration
Inter-Frequency Handover Parameters
Inter-frequency handover parameters are contained in the InterFreqHoGroup MO. The following table
provides suggestions on how to reconfigure these parameters.
For detailed parameter configuration for inter-frequency neighboring cells, see the "Required Data" part
in 9.2.3 Data Preparation.
9.2.8 Deactivation
To deactivate coverage-based inter-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.
In this situation, set the event A2 threshold to –96 dBm and the event A4 threshold to –94 dBm, and set
hysteresis for event A2 and that for event A4 to 4, which means 2 dB. With this configuration, a UE can
be smoothly handed over between cell A and cell B. During the handover, the RSRP difference between
the two cells is 4 dB, which means a ping-pong handover will not occur. If the signal fluctuates greatly in
the handover area, increase the difference between the event A2 threshold and the event A4 threshold.
However, if the difference is too large, handovers may not be performed in time.
Hysteresis
In inter-frequency handovers, the hysteresis for events A1 and A2 is specified by the
InterFreqHoGroup.InterFreqHoA1A2Hystparameter and that for event A4 by the
InterFreqHoGroup.InterFreqHoA4Hystparameter. These parameters are QCI-specific and are used in
decisions for events A1, A2, and A4, effectively reducing frequent event reporting caused by radio signal
fluctuations. The default values for these parameters are recommended.
A greater hysteresis makes it more difficult for events to be reported, and therefore handovers may not
be triggered in time. This affects user experience.
A smaller hysteresis makes it easier for events to be reported. This may result in incorrect handover
decisions and ping-pong handovers.
CIO
The CIO for an inter-frequency neighboring cell is included in event A4 measurement reports, and it is
specified by the EutranInterFreqNCell.CellIndividualOffsetparameter in the configuration data for this
neighbor relationship. This cell-level parameter varies according to the neighboring cells. Each UE adds
the CIO to the measurement results of neighboring cells. The UE considers this sum when making
decisions for handovers. This measure is equivalent to relocating cell borders.
A larger value for this parameter makes it easier for the UE to be handed over to an inter-frequency
neighboring cell.
A smaller value for this parameter makes it more difficult for the UE to be handed over to an
inter-frequency neighboring cell.
9.2.11 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:
Step 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 Step 2.
If the value of this IE is not radioNetwork:radio-connection-with-ue-lost, the handover parameters are
set correctly. Contact Huawei engineers.
Required Data
For details about the required data, see 9.2.3 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 9.2.3 Data Preparation.
The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure
frequency-priority-based inter-frequency handover.
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.
Transmission Networking
None.
License
None.
9.3.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.3.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-3 Frequency-Priority-based Inter-Frequency Handover
MO Parameter Group Name Parameter
CELLALGOSWIT CellAlgoSwitch Based on Frequency Priority HO Switch
CH
EUTRANINTERN EutranInterNFreq Local cell identity, Downlink EARFCN, Uplink
FREQ EARFCN configure 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 antenna port1, Inter-Freq HO trigger
Event Type
EUTRANINTERF EutranInterFreqNCell Local cell identity, Mobile country code, Mobile
REQNCELL network code, eNodeB 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
9.3.7 Reconfiguration
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 9.2.7 Reconfiguration.
9.3.8 Deactivation
To deactivate frequency-priority-based inter-frequency handover, disable its algorithm by running the
MOD CELLALGOSWITCH command.
9.3.11 Troubleshooting
Fault description
An eNodeB may not initiate a handover procedure upon receipt of an event A1 measurement report.
Required Data
For details about the required data, see 9.2.3 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
The following table describes the parameters that must be set in the DistBasedHo MO to set the
measurement object type.
Transmission Networking
None.
9.4.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.4.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-4 Distance-based Inter-Frequency Handover
MO Parameter Group Name Parameter
CELLALGOSWIT CellAlgoSwitch Distance-based Handover Switch
CH
DISTBASEDHO DistBaseDHO Local cell identity, Distance-based Measurement
Object Type, Distance-based Handover Threshold
EUTRANEXTERN EutranInterFreqNCell Mobile country code, Mobile network code, eNodeB
ALCELL identity, Cell identity, Downlink EARFCN, Uplink
EARFCN indicator, Uplink EARFCN, Physical cell
identity, Tracking area code, Cell name
EUTRANEXTERN EutranExternalCellPlmn Mobile country code, Mobile network code, eNodeB
ALCELLPLMN identity, Cell identity, Share mobile country code,
Share mobile network code
9.4.7 Reconfiguration
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 9.2.7 Reconfiguration.
9.4.8 Deactivation
To deactivate distance-based inter-frequency handover, disable its algorithm by running the
MOD DISTBASEDHO command.
9.4.11 Troubleshooting
None
Required Data
For details about the required data, see 9.2.3 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 9.2.3 Data Preparation.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
configure service-based inter-frequency handover.
The following table describes the parameter that must be set in the ServiceIfHoCfgGroup MO to
configure a service-based inter-frequency handover policy.
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 tables describe the parameter that must be set in the CnOperatorStandardQci MO to
configure inter-frequency handover policy groups for services with standard QCIs.
The following tables describe the parameter that must be set in the CnOperatorExtendedQci MO to
configure inter-frequency handover policy groups for services with extended QCIs.
Transmission Networking
None.
License
None.
9.5.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.5.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
9.5.7 Reconfiguration
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 9.2.7 Reconfiguration.
9.5.8 Deactivation
To deactivate service-based inter-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.
9.5.11 Troubleshooting
None
Required Data
For details about the required data, see 9.2.3 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 9.2.3 Data Preparation.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
configure UL-quality-based inter-frequency handover.
Transmission Networking
None.
License
None.
9.6.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.6.3 "Data Preparation."
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-6 UL-Quality-based Inter-Frequency Handover
MO Parameter Group Parameter
Name
ENODEBALGO ENodeBAlgoSwitch Handover Algo switch
SWITCH
EUTRANEXTER EutranInterFreqNCell Mobile country code, Mobile network code, eNodeB
NALCELL identity, Cell identity, Downlink EARFCN, Uplink EARFCN
indicator, Uplink EARFCN, Physical cell identity, Tracking
area code, Cell name
EUTRANEXTER EutranExternalCellPl Mobile country code, Mobile network code, eNodeB
NALCELLPLMN mn identity, Cell identity, Share mobile country code, Share
mobile network code
9.6.7 Reconfiguration
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 9.2.7 Reconfiguration.
9.6.8 Deactivation
To deactivate UL-quality-based inter-frequency handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.
9.6.11 Troubleshooting
Table 9-7 shows the alarms related to the feature.
Table 9-7 Alarm list
Alarm ID Alarm Name NE Feature ID Feature Name
29219 Inter-Frequency eNodeB LBFD-00201802 Coverage Based
Outgoing Cell LBFD-00201804 Inter-frequency
Handover Handover
Success Rate Distance Based
Too Low Inter-frequency
Handover
Required Data
This section describes the data required for configuring neighbor relationships with UTRAN and GERAN
cells.
During coverage-based inter-RAT handovers, the eNodeB can perform a blind handover when there is no neighboring
cells.To enable this function, you can configure only UTRAN neighboring frequencies, GERAN neighboring frequency
groups, or GERAN BCCH neighboring frequencies.
To enable other inter-RAT handover features, you must configure required data described in this section.
The following table describes the parameters that must be set in the UtranExternalCell MO to configure
an external UTRAN cell.
The following table describes the parameters that must be set in the UtranExternalCellPlmn MO to
configure an additional PLMN ID (representing a secondary operator) for an external UTRAN cell. This
MO is required only if the home NodeB of the external UTRAN cell works in RAN sharing with common
carrier mode and multiple operators share the same external UTRAN cell.
The following table describes the parameters that must be set in the UtranNCell MO to configure the
neighbor relationship with a UTRAN cell.
GERAN version GeranNfre Network This parameter specifies the RAT supported
qGroup.G plan by the GERAN carrier frequency group.
eranVersi (negotiation This parameter references the
on required) corresponding parameter on the peer BTS.
Band indicator GeranNfre Network This parameter specifies the GSM band
qGroup.B plan containing the GERAN carrier frequency
andIndicat (negotiation group.
or required) This parameter references the
corresponding parameter on the peer BTS.
The following table describes the parameters that must be set in the GeranNfreqGroupArfcn MO to
configure a neighboring frequency in a GERAN carrier frequency group.
The following table describes the parameters that must be set in the GeranExternalCell MO to
configure an external GERAN cell.
The following table describes the parameters that must be set in the GeranExternalCellPlmn MO to
configure an additional PLMN ID (representing a secondary operator) for an external GERAN cell. This
MO is required only if the home BTS of the external GERAN cell works in RAN sharing with common
carrier mode and multiple operators share the same external GERAN cell.
The following table describes the parameters that must be set in the GERANNCELL MO to configure the
neighbor relationship with a GERAN cell.
Collecting Data for Neighbor Relationships with CDMA2000 HRPD or CDMA2000 1xRTT Cells
The following table describes the parameters that must be set in the Cdma2000BandClass MO to
configure a neighboring CDMA2000 band class. This MO applies to the configuration of neighbor
relationships with CDMA2000 HRPD and those with CDMA2000 1xRTT cells.
The following table describes the parameters that must be set in the Cdma2000Nfreq MO to configure a
neighboring CDMA2000 frequency. This MO applies to the configuration of neighbor relationships with
CDMA2000 HRPD and those with CDMA2000 1xRTT cells.
The following table describes the parameters that must be set in the Cdma2000ExternalCell MO to
configure an external CDMA2000 cell. This MO applies to the configuration of neighbor
relationships with CDMA2000 HRPD and those with CDMA2000 1xRTT cells.
The following table describes the parameters that must be set in the Cdma2000ExternalCellPlmn MO
to configure an additional PLMN ID (representing a secondary operator) for an external CDMA2000 cell.
This MO applies to the configuration of neighbor relationships with CDMA2000 HRPD and those with
CDMA2000 1xRTT cells. This MO is required only if the home BTS of the external CDMA2000 cell works
in RAN sharing with common carrier mode and multiple operators share the external CDMA2000 cell.
The following table describes the parameters that must be set in the Cdma20001XRTTNcell MO to
configure the neighbor relationship with a CDMA2000 1xRTT cell.
The following table describes the parameters that must be set in the InterRatPolicyCfgGroup MO to
configure an inter-RAT handover policy group.
The following table describes the parameters that must be set in the StandardQci MO to configure the
inter-RAT handover policy group for a standardized QCI.
The following table describes the parameters that must be set in the ExtendedQci MO to configure the
inter-RAT handover policy group for an extended QCI.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to
configure the mode for coverage-based inter-RAT handovers.
By default, the inter-RAT handover parameter group Group0 is used for services with all QCIs. To apply
different inter-RAT 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.
The following table describes the parameter that must be set in the CellExtendedQci MO to configure
parameter groups for services with extended QCIs.
For details about inter-RAT handover parameter group ID and corresponding thresholds, see 9.7.7
Reconfiguration.
The following table describes the parameter that must be set in the GeranNcell MO to configure blind
handover priorities and measurement priorities for GERAN neighboring cells.
The following table describes the parameters must be set in a CSFallBackBlindHoCfg MO to configure
RAT priorities for blind handovers. The CSFallBackBlindHoCfg MO takes effect for all inter-RAT
handovers, rather than for only CSFB.
Transmission Networking
None
9.7.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.7.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
After the eNodeB receives an event B1 or B2 measurement report from the UE, the eNodeB sends an
RRC_MOBIL_FROM_EUTRA_CMD message or an RRC_CONN_REL message containing an
inter-RAT frequency to the UE.
After the eNodeB receives an event A2 measurement report for a blind handover, the UE does not
support measurement of a specified RAT and the eNodeB sends an RRC_CONN_REL message
containing an inter-RAT frequency to the UE.
9.7.8 Deactivation
To deactivate coverage-based inter-RAT handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.
Hysteresis
The hysteresis in events A1 and A2 for inter-RAT handovers is specified by the
InterRatHoCommGroup.InterRatHoA1A2Hystparameter. The hysteresis in event B1 for inter-RAT
handovers is specified by:
the InterRatHoUtranGroup.InterRATHoUtranB1Hyst parameter in WCDMA and TD-SCDMA
systems
the InterRatHoGeranGroup.InterRATHoGeranB1Hyst parameter in GSM systems
9.7.11 Troubleshooting
Fault 1: No Delivery of A1/A2-related Inter-RAT Measurement Configuration
Fault description
The eNodeB does not deliver the A1/A2-related inter-RAT measurement configuration to some UEs that
have accessed the network.
Fault handling
Step 1 Trace messages over the Uu interface on the M2000 client. Check for the target system and
frequency band in the IE interRAT-Parameters of the RRC_UE_CAP_INFO message.
If the interRAT-Parameters IE does not contain information about the target system and frequency band,
the UE does not support inter-RAT measurement of the specified target system and frequency. Figure
9-3 shows a sample RRC_UE_CAP_INFO message.
Figure 9-3 RRC_UE_CAP_INFO message
Step 2 Run an MML command to check for the neighboring cell configurations. For example, if the
target system is UTRAN, run the LST UTRANNCELL command to check whether the
neighboring UTRAN cells are configured.
If the neighboring UTRAN cells are not configured, configure the cells.
If the neighboring UTRAN cells are configured, go to Step 3.
Step 3 Run the LST ENODEBALGOSWITCH command to check whether the corresponding handover
mode is enabled.
If the corresponding handover mode is disabled, enable it.
If the corresponding handover mode is enabled, contact Huawei technical support.
Step 2 Run an MML command to check for the neighboring cell configurations. For example, if the
target system is UTRAN, run the LST UTRANNCELL command to check whether the
neighboring UTRAN cells are configured.
If the neighboring UTRAN cells are not configured, configure the cells.
If the neighboring UTRAN cells are configured, go to Step 3.
Step 3 Run the LST ENODEBALGOSWITCH command to check whether the corresponding handover
mode is enabled.
----End
Alarm
Table 9-12 shows the alarms related to the feature.
Table 9-12 Alarm list
Alarm ID Alarm Name NE Feature ID Feature Name
29221 LTE-WCDMA eNodeB LOFD-001072 Distance based
Inter-System Inter-RAT
Outgoing Cell handover to
Handover UTRAN
Success Rate
Too Low
29222 LTE-GERAN eNodeB LOFD-001073 Distance based
Inter-System Inter-RAT
Outgoing Cell handover to
Handover GERAN
Success Rate
Too Low
Required Data
For details about the required data, see 9.7.3 Data Preparation.
Scenario-specific Data
UL-Quality-based inter-RAT handover can be enabled only after coverage-based inter-RAT handover is
enabled. This section describes the required parameters except those for coverage-based inter-RAT
handover. For details on the required parameters for coverage-based inter-RAT handover, see the
"Scenario-specific Data" part in 9.7.3 Data Preparation.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to
configure the mode for inter-RAT handover based on UL quality.
Transmission Networking
None
9.8.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.8.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
9.8.7 Reconfiguration
The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-RAT handovers. For details, see 9.7.7 Reconfiguration.
9.8.8 Deactivation
To deactivate UL-quality-based inter-RAT handover, disable its algorithm by running the MOD
ENODEBALGOSWITCH command.
9.8.11 Troubleshooting
For details about troubleshooting, see 9.7.11 Troubleshooting.
Required Data
For details about the required data, see 9.7.3 Data Preparation.
Scenario-specific Data
Distance-based inter-RAT handover can be enabled only after coverage-based inter-RAT handover is
enabled. This section describes the required parameters except those for coverage-based inter-RAT
handover. For details on the required parameters for coverage-based inter-RAT handover, see the
"Scenario-specific Data" part in 9.7.3 Data Preparation.
To enable distance-based inter-RAT handovers, the corresponding switch must be turned on and the
measurement object type must be set to UTRAN or GERAN.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to enable
distance-based inter-RAT handovers.
The following table describes the parameters that must be set in the DistBasedHo MO to set the
measurement object type.
License
To use distance-based inter-RAT handovers, an operator must purchase and activate the licenses for the
features listed in the following table.
9.9.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.9.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-17 Distance-based inter-RAT handover to UTRAN
MO Parameter Group Parameter
Name
CELLALGOSWITCH CELLALGOSWITCH Distance-based Handover Switch
DISTBASEDHO DISTBASEDHO Distance-based Measurement Object
Type, Distance-based Handover Threshold
9.9.7 Reconfiguration
The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-RAT handovers. For details, see 9.7.7 Reconfiguration.
9.9.8 Deactivation
Step 1 Run the MOD CELLALGOSWITCH command to turn off the switch for distance-based
handover.
Step 2 Run the MOD DISTBASEDHO command, and clear the corresponding check box under
the Distance-based Measurement Object Type parameter to disable distance-based
handovers to the corresponding RAT.
----End
9.9.11 Troubleshooting
For details about troubleshooting, see 9.7.11 Troubleshooting.
Required Data
For details about the required data, see 9.7.3 Data Preparation.
Scenario-specific Data
Service-based inter-RAT handover can be enabled only after coverage-based inter-RAT handover is
enabled. This section describes the required parameters except those for coverage-based inter-RAT
handover. For details on the required parameters for coverage-based inter-RAT handover, see the
"Scenario-specific Data" part in 9.7.3 Data Preparation.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable
service-based inter-RAT handovers.
The following table describes the parameters that must be set in the ServiceIrHoCfgGroup MO to
configure a service-based inter-RAT handover policy.
The following tables describe the parameter that must be set to configure inter-RAT handover policy
groups for services with standard or extended QCIs.
The following table describes the parameter that must be set in the CnOperatorStandardQci MO to
configure parameter groups for services with standard QCIs.
Transmission Networking
None
License
To use service-based inter-RAT handovers, an operator must purchase and activate the licenses for the
features listed in the following table.
9.10.5 Activation
Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MO and parameters as described in section 9.10.3 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-19 Service-based inter-RAT handover to UTRAN
MO Parameter Group Parameter
Name
ENODEBAL ENodeBAlgoSwitch Handover Algo switch, Handover Mode switch
GOSWITCH
SERVICEIR ServiceIrHoCfgGroup CN Operator ID, Service-based inter-RAT handover policy
HOCFGGR group ID, Inter-RAT handover state
OUP
9.10.7 Reconfiguration
The reconfiguration of parameters that are not involved in this section is the same as the reconfiguration
of parameters for coverage-based inter-RAT handovers. For details, see 9.7.7 Reconfiguration.
9.10.8 Deactivation
To deactivate service-based inter-RAT handover, disable the algorithms for service-based UTRAN
handovers and service-based GERAN handovers by running the MOD ENODEBALGOSWITCH
command.
9.10.11 Troubleshooting
For details about troubleshooting, see 9.7.11 Troubleshooting.
Required Data
For details about required data for coverage-based inter-RAT handover to UTRAN, see 9.7.3 Data
Preparation.
For details about required data for CSFB to UTRAN, see CS Fallback Feature Parameter Description.
Scenario-specific Data
E-URTAN to UTRAN CS/PS steering can be enabled only after coverage-based inter-RAT handover is
enabled. This section describes the required parameters except those for coverage-based inter-RAT
handover. For details on the required parameters for coverage-based inter-RAT handover, see the
"Scenario-specific Data" part in 9.7.3 Data Preparation.
For details about scenario-specific data for CSFB to UTRAN, see CS Fallback Feature
Parameter Description.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
configure E-UTRAN to UTRAN CS/PS steering.
The following table describes the parameters that must be set in a UtranNFreq MO to set CS and PS
service priorities of a UTRAN frequency.
Transmission Networking
None.
License
The operator has purchased and activated the license for the feature listed in the following table.
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN and
LOFD-001033 CS Fallback to UTRAN. For the corresponding license requirement, see License part in
9.7.4 Deployment Requirements and CS Fallback Feature Parameter Description.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Table 9-21 E-UTRAN to UTRAN CS/PS Steering
MO Parameter Group Parameter
Name
ENODEBALGOSWITCH ENodeBAlgoSwitch Frequency Layer Switch
UTRANNFREQ UtranNFreq PS service priority, CS service priority
For details about activation observations for CS service priority configuration, see CS Fallback Feature
Parameter Description.
----End
9.11.7 Reconfiguration
None.
9.11.8 Deactivation
Run the MOD ENODEBALGOSWITCH command and clear the check boxes
UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) and
UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) under Frequency Layer Switch.
9.11.11 Troubleshooting
For details about troubleshooting, see 9.7.11 Troubleshooting.
10 Parameters
Table 10-1 Parameter description
MO Parameter ID MML Command Feature Feature Description
ID Name
LOFD-00 PS
1022 / Inter-RAT
TDLOFD Mobility
-001022 between
E-UTRAN
and UTRAN
SRVCC to
UTRAN
RMV
CDMA2000NFR
EQ
RMV
INTERRATHOG
ERANGROUP
LBFD-00
201805
11 Counters
Table 11-1 Counter description
Counter Counter Name Counter Descrip Feature ID Feature Name
ID tion
in a cell
in a cell
in a cell
in a cell
rejection
messages
received by the
target cell<?Pub
Caret?>
12 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
13 Reference Documents
This chapter lists the reference documents related to mobility management in connected mode:
[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] eNodeB Performance Counter Reference
[9] eNodeB MO Reference
[10] Idle Mode Management Feature Parameter Description
[11] ANR Management Feature Parameter Description
[12] MLB Feature Parameter Description
[13] ICIC Feature Parameter Description
[14] S1/X2/OM Channel Management Feature Parameter Description
[15] eNodeB Initial Configuration Guide
[16] eNodeB Reconfiguration Guide