CSFB Huawei

CS Fallback
Contents
3.1.2 CS Fallback
eRAN
CS Fallback Feature Parameter Description
Issue 02
Date 2015-06-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.
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of

Address:
China
Website: http://www.huawei.com/
Email: support@huawei.com
3.1.2 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 Overview
2.2 Benefits
2.3 Architecture
3 CSFB to UTRAN
3.1 Basic CSFB to UTRAN
3.1.1 Handover Measurement
3.1.2 Blind Handover
3.2 Flash CSFB to UTRAN
3.3 Ultra-Flash CSFB to UTRAN
3.4 CS Fallback with LAI to UTRAN
3.5 E-UTRAN to UTRAN CS Steering
3.6 CS Fallback Steering to UTRAN
3.7 Load-based CSFB to UTRAN
3.8 Handover Decision
3.8.1 Basic Handover Decision
3.8.2 Flash Redirection Decision
3.9 Handover Execution
3.9.1 Handover Policy Selection
3.9.2 Ultra-Flash CSFB to UTRAN
3.9.3 Redirection-based CSFB Optimization for UEs in Idle Mode
3.9.4 CSFB Admission Optimization for UEs in Idle Mode
3.10 RIM Procedure Between E-UTRAN and UTRAN
3.10.1 RIM Procedure Through the Core Network
3.10.2 RIM Procedure Through the eCoordinator
3.11 CSFB to UTRAN
3.11.1 Combined EPS/IMSI Attach Procedure
3.11.2 CSFB Based on PS Handover
3.11.3 Signaling procedure of redirection to CDMA2000 1xRTT
3.11.4 Flash CSFB
3.11.7 CSFB for SMS
3.11.8 Emergency Call
3.11.9 CSFB for LCS
4 CSFB to GERAN
4.1 Basic CSFB to GERAN
4.2 Flash CSFB to GERAN
4.3 CS Fallback with LAI to GERAN
4.4 CS Fallback Steering to GERAN
4.5 Ultra-Flash CSFB to GERAN
4.8 RIM Procedure Between E-UTRAN and GERAN
4.9 CSFB to GERAN
4.9.3 CSFB Based on CCO/NACC
4.9.4 CSFB Based on Redirection
4.9.5 Flash CSFB
4.9.6 Ultra-Flash CSFB to GERAN
4.9.7 CSFB for SMS
4.9.9 CSFB for LCS
5 Related Features
5.1 Features Related to LOFD-001033 CS Fallback to UTRAN
5.2 Features Related to LOFD-001052 Flash CS Fallback to UTRAN
5.3 Features Related to LOFD-070202 Ultra-Flash CSFB to UTRAN
5.4 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN
5.5 Features Related to LOFD-001088 CS Fallback Steering to UTRAN
5.6 Features Related to LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
5.7 Features Related to LOFD-001034 CS Fallback to GERAN
5.8 Features Related to LOFD-001053 Flash CS Fallback to GERAN
5.9 Feature Related to LOFD-081283 Ultra-Flash CSFB to GERAN
5.10 Features Related to LOFD-001069 CS Fallback with LAI to GERAN
5.11 Features Related to LOFD-001089 CS Fallback Steering to GERAN
6 Network Impact
6.1 LOFD-001033 CS Fallback to UTRAN
6.2 LOFD-001052 Flash CS Fallback to UTRAN
6.3 LOFD-070202 Ultra-Flash CSFB to UTRAN
6.4 LOFD-001068 CS Fallback with LAI to UTRAN
6.5 LOFD-001088 CS Fallback Steering to UTRAN
6.6 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
6.7 LOFD-001034 CS Fallback to GERAN
6.8 LOFD-001053 Flash CS Fallback to GERAN
6.9 LOFD-081283 Ultra-Flash CSFB to GERAN
6.10 LOFD-001069 CS Fallback with LAI to GERAN
6.11 LOFD-001089 CS Fallback Steering to GERAN
7 Engineering Guidelines
7.1.1 When to Use CS Fallback to UTRAN
7.1.2 Required Information
7.1.3 Requirements
7.1.4 Precautions
7.1.5 Data Preparation and Feature Activation
7.1.5.1 Data Preparation
7.1.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
7.1.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs
7.1.5.4 Using the CME to Perform Single Configuration
7.1.5.5 Using MML Commands
7.1.6 Activation Observation
7.1.7 Deactivation
7.1.8 Performance Monitoring
7.1.9 Parameter Optimization
7.2 RIM Procedure from E-UTRAN to UTRAN
7.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN
7.2.3 Requirements
7.2.4 Precautions
7.2.7 Deactivation
7.3.1 When to Use Flash CS Fallback to UTRAN
7.3.3 Requirements
7.3.4 Precautions
7.3.7 Deactivation
7.4.1 When to Use Ultra-Flash CSFB
7.4.3 Requirements
7.4.4 Precautions
7.4.7 Deactivation
7.5.1 When to Use CS Fallback with LAI to UTRAN
7.5.3 Requirements
7.5.4 Precautions
7.5.7 Deactivation
7.6.1 When to Use CS Fallback Steering to UTRAN
7.6.3 Requirements
7.6.4 Precautions
7.6.7 Deactivation
7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering
7.7.3 Requirements
7.7.4 Precautions
7.7.7 Deactivation
7.8.1 When to Use CS Fallback to GERAN
7.8.3 Requirements
7.8.4 Precautions
7.8.5.5 Using Feature Operation and Maintenance on the CME
7.8.7 Deactivation
7.9 RIM Procedure from E-UTRAN to GERAN
7.9.1 When to Use RIM Procedure Between E-UTRAN and GERAN
7.9.3 Requirements
7.9.4 Precautions
7.9.7 Deactivation
7.10.1 When to Use Flash CS Fallback to GERAN
7.10.3 Requirements
7.10.4 Precautions
7.10.7 Deactivation
7.11.1 When to Use This Feature
7.11.3 Requirements
7.11.4 Precautions
7.11.7 Deactivation
7.12.1 When to Use CS Fallback with LAI to GERAN
7.12.3 Requirements
7.12.4 Precautions
7.12.7 Deactivation
7.13.1 When to Use CS Fallback Steering to GERAN
7.13.3 Requirements
7.13.4 Precautions
7.13.7 Deactivation
7.14 Troubleshooting
7.14.1 CSFB Calling Procedure Failure
7.14.2 eNodeB Receiving No Measurement Report
7.14.3 CSFB Blind Handover Failure
7.14.4 CSFB Handover Failure
8 Parameters
9 Counters
10 Glossary
11 Reference Documents
1 About This Document
1.1 Scope
This document describes circuit switched fallback (CSFB), including its technical
principles, related features, network impact, and engineering guidelines.
This document covers the following features:
• LOFD-001033 CS Fallback to UTRAN
• LOFD-001052 Flash CS Fallback to UTRAN
• LOFD-070202 Ultra-Flash CSFB to UTRAN
• LOFD-001068 CS Fallback with LAI to UTRAN
• LOFD-001088 CS Fallback Steering to UTRAN
• LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
• LOFD-001034 CS Fallback to GERAN
• LOFD-001053 Flash CS Fallback to GERAN
• LOFD-001069 CS Fallback with LAI to GERAN
• LOFD-001089 CS Fallback Steering to GERAN
• LOFD-081283 Ultra-Flash CSFB to GERAN
If Huawei devices are used in the GERAN or UTRAN to which CS fallback is
performed, refer to the following documents to obtain details about CSFB
implementation in the corresponding network:
• For the GERAN, see CSFB in GBSS Feature Documentation.
• For the UTRAN, see Interoperability Between UMTS and LTE in RAN Feature
Documentation.
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
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.
eRAN8.1 02 (2015-06-30)
This issue includes the following changes.
Change Type Change Description Parameter Change Affected

Entity
Feature Added the measurement-specific None Macro,

change DRX configuration for Ultra-Flash micro, and
CSFB to GERAN. For details, see LampSite
4.5 Ultra-Flash CSFB to GERAN. eNodeBs
Added the random procedure Added the Macro,

selection optimization for CSFB. RsvdSwPara1_bit23 micro, and
For details, see 7.1.5.1 Data option in the reserved LampSite
Preparation. parameter eNodeBs
eNBRsvdPara.
RsvdSwPara1.
Editorial None None -

change
eRAN8.1 01 (2015-03-23)
This issue includes the following changes.
Change Change Description Parameter Change Affected

Type Entity
Feature Added the UE Added the Macro,

change compatibility risk UltraFlashCsfbComOptSw option micro, and
optimization for Ultra- to the LampSite
flash CSFB. For details, GlobalProcSwitch.UeCompatSwitch eNodeBs
see 7.11.5.1 Data parameter.
Preparation.
Type Entity
Editorial None None -

change
eRAN8.1 Draft A (2015-01-15)
Compared with Issue 06 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1

includes the following changes.

Type Entity
Feature Supported the cell-level blind Added the CellHoParaCfg.HoModeSwitch Macro,

change handling switch for CSFB in parameter. micro,
CS Fallback to UTRAN or and
GERAN and Flash CS LampSite
Fallback to UTRAN or eNodeBs
GERAN scenarios.
• For details about the
switch, see 3.1 Basic CSFB
to UTRAN and 3.1.2 Blind
Handover.
• For details about
handover policy
selection, see 3.9.1
Handover Policy Selection.
scenario-specific
parameter preparations,
see section "Data
Preparation" in
engineering guidelines.
scenario-specific
configurations, see
"Using the CME to
Perform Batch
Configuration for Newly
Deployed eNodeBs" and
"Using MML
Commands" in section
"Activation" in
engineering guidelines.
Type Entity
Added the feature LOFD- • Added the Macro,

081283 Ultra-Flash CSFB to GeranExternalCell.UltraFlashCsfbInd micro,
GERAN. parameter. and
• For details about the • Added the GeranUltraFlashCsfbSwitch LampSite
feature description, see option in the eNodeBs
4.5 Ultra-Flash CSFB to ENodeBAlgoSwitch.HoAlgoSwitch
GERAN. parameter.
signaling procedure, see
4.9.6 Ultra-Flash CSFB to
GERAN.
• For details about related
features and network
impact, see 5.9 Feature
Related to LOFD-081283
Ultra-Flash CSFB to GERAN
and 6.9 LOFD-081283 Ultra-
Flash CSFB to GERAN.
engineering guidelines,
see 7.11 LOFD-081283 Ultra-
Added the configuration of Added the Macro,

the round-robin function for CSFallBackBlindHoCfg.UtranCsfbBlindRedirRrSw micro,
L2U blind redirections. parameter. and
• For details about the LampSite
switch, see 3.1.2 Blind eNodeBs
Handover.
scenario-specific data
preparations, see 7.1.5.1
Data Preparation.
function activation, see
7.1.5.5 Using MML
Commands.
Added SPID-based mobility None Macro,

management. For details micro,
about the function, see 3.1.2 and
Blind Handover, 3.8.1 Basic LampSite
Handover Decision, and 3.8.2 eNodeBs
Flash Redirection Decision.
Type Entity
Ultra-flash CSFB to GERAN Added the CellDrxPara.DrxForMeasSwitch Macro,

uses the DRX-based parameter. micro,
measurement, which is and
controlled by the LampSite
CellDrxPara.DrxForMeasSwitch eNodeBs
parameter.
parameter, see 4.5 Ultra-
• For details about data
preparations and MML
configurations, see
related sections in 7.11
LOFD-081283 Ultra-Flash
CSFB to GERAN.
Editorial Changed "blind handling" to None -

change "blind handover". For details,
see descriptions of blind
handover in this document.
1.4 Differences Between eNodeB Types
The features described in this document are implemented in the same way on macro,
micro, and LampSite eNodeBs.
2 Overview
In an early phase of evolved packet system (EPS) construction, operators who own a
mature UTRAN or GERAN can protect their investments in legacy CS networks and
reduce their investments in the EPS by using legacy CS networks to provide CS services
such as the voice service, short message service (SMS), location service (LCS), and
emergency calls.
Currently, CSFB and voice over IP (VoIP) over IP multimedia subsystem (IMS) are the
two standard solutions to provide voice services for E-UTRAN UEs. After the
technological maturity, industry chain, and deployment costs of the two methods are well
weighed, CSFB is chosen to serve as an interim solution for voice service access before
mature commercial use of IMS.
2.1 Overview
With the CSFB solution, when a UE initiates a CS service, the MME instructs the UE to
fall back to the legacy CS network before the UE performs the service. CSFB is a session
setup procedure. UEs fall back to CS networks before CS sessions are set up, and they
always stay in the CS networks during the CS sessions. For details, see 3GPP TS 23.272
V8.5.0.
The eNodeB handles the CSFB for different types of CS services in a uniform way such
as the voice service, SMS, LCS, and emergency calls.
2.2 Benefits
CSFB brings the following benefits:

• Facilitates voice services for the LTE network.
• Helps operators reduce costs by reusing legacy CS networks and not deploying an
IMS network.
2.3 Architecture
CSFB is applicable to scenarios where the CS network of the UTRAN/GERAN has the
same or larger coverage area than E-UTRAN.
The network architecture for CSFB is simple. To implement CSFB, all mobile switching
centers (MSCs) that serve overlapping areas with the E-UTRAN coverage must be
upgraded to support functions involving the SGs interface. The SGs interface is between
an MSC and a mobility management entity (MME), and functions involving the SGs
interface include combined attach, combined TAU/LAU (TAU is short for tracking area
update, and LAU is short for location area update), paging, and SMS. If the live network
uses an MSC pool, only one or multiple MSCs in the MSC pool need to be upgraded to
support the SGs interface.
Figure 2-1 shows the network architecture for CSFB to UTRAN/GERAN.
Figure 2-1 Network architecture for CSFB to UTRAN/GERAN
Table 2-1 describes the elements of the network architecture in Figure 2-1.
Table 2-1 Elements of the network architecture for CSFB to UTRAN/GERAN
Element Function
SGs interface • Is an interface between the MME and the MSC server.
• Assists mobility management and paging between the EPS
and the CS network.
• Transmits mobile originated (MO) and mobile terminated (MT)
SMS messages.
• Transmits messages related to combined attach and combined
TAU/LAU.
UE • Is capable of accessing the EPS and accessing the UTRAN,

GERAN, or both.
• Supports combined EPS/IMSI (IMSI is short for international
mobile subscriber identity) attach, combined EPS/IMSI detach,
and combined TAU/LAU.
• Supports CSFB mechanisms, such as PS redirection and PS
handover.
NOTE:
CSFB-capable UEs must support SMS over SGs, but UEs that support SMS over
SGs are not necessarily CSFB-capable.
MME • Supports the SGs interface to the MSC/VLR.

Element Function
• Selects the VLR and location area identity (LAI) based on the
tracking area identity (TAI) of the serving cell.
• Forwards paging messages delivered by the MSC.
• Performs public land mobile network (PLMN) selection and
reselection.
• Supports combined EPS/IMSI attach, combined EPS/IMSI
detach, and combined TAU/LAU.
• Routes CS signaling.
• Supports SMS over SGs.
• Supports RIM, which is required when flash CSFB or CCO with
NACC is used as the CSFB mechanism. (CCO is short for cell
change order and NACC is short for network assisted cell
change.)
MSC • Supports combined EPS/IMSI attach.

• Supports SMS over SGs.
• Forwards paging messages transmitted through the SGs
interface.
E-UTRAN • Forwards paging messages related to CSFB.

• Selects target cells for CSFB for E-UTRAN UEs.
• Supports one or more of the following functions:
▪ PS redirection to UTRAN or GERAN, if PS redirection is
used as the CSFB mechanism.
▪ PS handover to UTRAN or GERAN, if PS handover is
▪ CCO without NACC to GERAN, if CCO without NACC is
used as the CSFB mechanism; RIM for acquiring the
system information of GERAN cells, if NACC is used as
the CSFB mechanism.
▪ RIM for acquiring the system information of UTRAN or
GERAN cells, in addition to PS redirection, if flash CSFB
is used as the CSFB mechanism.
UTRAN/GERAN Supports one or more of the following functions:

• Incoming handovers from the E-UTRAN, if PS handover is
• RIM for delivering the system information of GERAN cells to
eNodeBs, if CCO with NACC is used as the CSFB mechanism.
• RIM for delivering the system information of UTRAN or GERAN
cells to eNodeBs, in addition to PS redirection, if flash CSFB is
NOTE:
Element Function
The UTRAN and GERAN do not need to provide extra functions to support PS
redirection. The GERAN does not need to provide extra functions to support CCO
without NACC.
SGSN • Supports the follow-up procedures performed for the PS

handover, including data forwarding, path switching, RAU, and
encryption and authentication.
• Supports RIM, which is required when flash CSFB or CCO with
NACC is used as the CSFB mechanism.
eCoordinator Is a network element provided by Huawei, and is optional. The

eCoordinator supports the RIM procedure.
3 CSFB to UTRAN
CSFB to UTRAN can be implemented in different ways, and this section covers the
following features/functions:
• LOFD-001033 CS Fallback to UTRAN
• LOFD-001052 Flash CS Fallback to UTRAN
• LOFD-070202 Ultra-Flash CSFB to UTRAN
• LOFD-001068 CS Fallback with LAI to UTRAN
• LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
• LOFD-001088 CS Fallback Steering to UTRAN
• Load-based CSFB to UTRAN
The triggering conditions for different features are different. Basically the procedure for
CSFB to UTRAN is as follows:
1. Selecting a target cell or frequency
In a measurement-based handover, the eNodeB generates a candidate cell list based
on inter-RAT measurement results and selects a target cell from the list.
In a blind handover, the eNodeB selects a target cell based on the blind handover
priorities of neighboring cells or selects a target frequency based on the frequency
priorities.
2. Handover decision
In the handover decision phase, the eNodeB checks the target cell list.
3. Handover execution
The eNodeB controls the UE to be handed over from the serving cell to the target
cell.
3.1 Basic CSFB to UTRAN
This section describes the optional feature LOFD-001033 CS Fallback to UTRAN. For
details about the engineering guidelines for this feature, see 7.1 LOFD-001033 CS Fallback to
UTRAN. The UtranCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter
specifies whether to enable this feature.
When a UE initiates a CS service in the E-UTRAN, the MME sends an S1-AP message
containing CS Fallback Indicator to the eNodeB, instructing the eNodeB to transfer the
UE as well as the CS service to a target network.
The eNodeB determines whether to trigger UTRAN measurements or blind handling for
CSFB to UTRAN based on the status of the blind handling switch first. The blind
handover switch is controlled by the BlindHoSwitch option in the eNodeB-level
parameter ENodeBAlgoSwitch.HoModeSwitch and the BlindHoSwitch option in the cell-
level parameter CellHoParaCfg.HoModeSwitch. The blind handover function takes effect
only if the eNodeB-level BlindHoSwitch and cell-level BlindHoSwitch options are
selected.
• If this option is selected, the eNodeB triggers blind handover directly.
• If this option is cleared, the eNodeB determines whether to trigger inter-RAT
measurements or blind handover based on the UE capability:
▪ If the UE supports UTRAN measurements, the eNodeB triggers inter-RAT
measurements.
▪ If the UE does not support UTRAN measurements, the eNodeB triggers a blind
handover.
3.1.1 Handover Measurement
Measurement Triggering Reason
During CSFB, the eNodeB starts a UTRAN measurement after it receives a CS Fallback
Indicator. The measurement configuration is the same as that for coverage-based
handover from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility Management in
Connected Mode.
Figure 3-1 shows the measurement object selection procedure.

Figure 3-1 Measurement object selection procedure
The configurations involved in Figure 3-1 are as follows:

• Neighboring UTRAN frequencies are added by running the ADD UTRANNFREQ
command.
• The frequency priority is specified by the UtranNFreq.ConnFreqPriority parameter.
A larger value indicates a higher priority.
• The cell measurement priorities of neighboring UTRAN cells can be automatically
optimized by ANR. The UTRAN_SWITCH option in the
ENodeBAlgoSwitch.NCellRankingSwitch parameter is used to enable this function.
This option is recommended to be selected if ANR is enabled.
▪ If this option is selected, the eNodeB automatically optimizes the setting of the
UtranNCell.NCellMeasPriority parameter for the cell. This parameter cannot be
modified manually. For details, see ANR Management.
▪ If this option is cleared, the cell measurement priorities are specified by the
UtranNCell.CellMeasPriority parameter, which needs to be configured manually.
• The number of frequencies or cells that the eNodeB can randomly select for
measurement is always equal to the allowed maximum number.
• The maximum number of frequencies is specified by the
CellUeMeasControlCfg.MaxUtranFddMeasFreqNum parameter.
• For details about the maximum number of neighboring cells in a measurement
configuration message, see section 6.4 "RRC multiplicity and type constraint
values" in 3GPP TS 36.331 V10.1.0.
Triggering of CSFB
During the measurement procedure, CSFB is triggered by event B1. The principle of
triggering CSFB by event B1 is the same as that of triggering the coverage-based inter-
frequency handover by event B1. For details, see Inter-RAT Mobility Management in Connected
Mode.
They have different thresholds and time-to-trigger. Table 3-1 lists the thresholds and time-
to-trigger related to event B1 for CSFB to UTRAN. Other parameters are the same as
those related to event B1 for coverage-based inter-frequency handovers.
Table 3-1 Parameters related to event B1 for CSFB to UTRAN
Parameter Parameter ID Parameter Description

Name
CSFB CSFallBackHo.CsfbHoUtranB1ThdRscp The

UTRAN InterRatHoComm.InterRATHoUtranB1MeasQuan
EventB1 parameter determines which threshold is to
RSCP be used.
Trigger
Threshold
CSFB CSFallBackHo.CsfbHoUtranB1ThdEcn0
UTRAN
EventB1
ECN0
Trigger
Threshold
Parameter Parameter ID Parameter Description
Name
CSFB CSFallBackHo.CsfbHoUtranTimeToTrig N/A

Utran
EventB1
Time To
Trig
3.1.2 Blind Handover
Triggering of Blind Handover
The blind handover switch is controlled by the BlindHoSwitch option in the

ENodeBAlgoSwitch.HoModeSwitch parameter and the BlindHoSwitch option in the
CellHoParaCfg.HoModeSwitch parameter. The blind handover function takes effect only
if the eNodeB-level BlindHoSwitch and cell-level BlindHoSwitch options are selected.
When an E-UTRAN coverage area is larger than a UTRAN coverage area and E-UTRAN
and UTRAN base stations are co-sited, adaptive-blind-handover-based CSFB estimates
the signal strength of the neighboring UTRAN cell based on the signal strength of the
serving E-UTRAN cell.
• If the UE is located in the center of the E-UTRAN cell, the eNodeB performs the
blind handover.
• If the UE is located at the edge of the E-UTRAN cell, the eNodeB performs a
measurement-based handover.
When the blind handover function takes effect:
• If adaptive-blind-handover-based CSFB is disabled, the eNodeB directly enters the
blind handover procedure.
• If adaptive-blind-handover-based CSFB is enabled, the eNodeB delivers
measurement configurations for event A1.
▪ If the eNodeB receives an event A1 report and determines that the UE is
located in the center of the E-UTRAN cell, it directly enters the blind handover
procedure.
▪ If the eNodeB does not receive an event A1 report and determines that the UE
is located at the edge of the E-UTRAN cell, it enters the measurement
procedure.
The event A1 threshold is specified by the CSFallBackHo.BlindHoA1ThdRsrp
parameter, and other event-A1-related principles are the same as these in coverage-
based handover from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility
Management in Connected Mode.
Target RAT Selection

During a blind handover for CSFB, the eNodeB selects the target RAT based on the RAT
priorities specified by the following parameters:
• CSFallBackBlindHoCfg.InterRatHighestPri: specifies the RAT with the highest
priority.
• CSFallBackBlindHoCfg.InterRatSecondPri: specifies the RAT with the second
highest priority.
• CSFallBackBlindHoCfg.InterRatLowestPri: specifies the RAT with the lowest
priority.
If CSFallBackBlindHoCfg.InterRatHighestPri is set to UTRAN(UTRAN), the eNodeB
performs CSFB to UTRAN.
• When selecting target cells for blind handover, the eNodeB excludes the following
neighboring cells:
▪ Blacklisted neighboring cells
▪ Neighboring cells with a handover prohibition flag
▪ Neighboring cells that have a different PLMN from the serving cell in the
neighboring cell list. If the inter-PLMN handover switch is turned on, such
cells are not excluded.
▪ Cells in the areas indicated by the Handover Restriction List IE in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME
After the preceding exclusion, the eNodeB excludes cells from the neighboring cell
list based on SPID-based mobility management in connected mode. For details, see
LOFD-00105401 Camp and Handover Based on SPID in Flexible User Steering
Feature Parameter Description.
• When selecting target frequencies for blind redirection, the eNodeB filters
frequencies based on the RATs supported by the UE and PLMN information
corresponding to frequencies.
After the preceding exclusion, the eNodeB filters cells from the neighboring cell list
based on SPID-based mobility management in connected mode. For details, see
LOFD-00105401 Camp and Handover Based on SPID in Flexible User Steering
During blind handover, the target selection procedure is different, depending on whether
neighboring UTRAN cells are configured.
• If neighboring UTRAN cells are configured, the target selection procedure is shown
in Figure 3-2.
▪ The blind handover priority of a neighboring UTRAN cell is specified by the
UtranNCell.BlindHoPriority parameter. A larger value indicates a higher
priority.
▪ The priority of a neighboring UTRAN frequency is specified by
UtranNFreq.ConnFreqPriority parameter. A larger value indicates a higher
priority.
• If no neighboring UTRAN cell is configured, neighboring UTRAN frequencies are
configured, and the UE performs CSFB based on redirection, the target selection
procedure is shown in Figure 3-3.
▪ Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
▪ The PLMN information of the neighboring UTRAN frequencies is contained in
the configured UtranRanShare or UtranExternalCell MOs.
Figure 3-2 Target cell selection (configured with a neighboring UTRAN cell)
Figure 3-3 Target cell selection (configured with no neighboring UTRAN cell)
When a UE performs a blind redirection, the eNodeB preferentially selects the frequency
with the highest priority. If multiple frequencies are of the same priority, the eNodeB
selects the blind redirection frequency in a round-robin manner. This ensures that the UE
accesses each frequency equally. This function is specified by the
CSFallBackBlindHoCfg.UtranCsfbBlindRedirRrSw parameter.
3.2 Flash CSFB to UTRAN
This section describes the optional feature LOFD-001052 Flash CS Fallback to UTRAN.
For details about the engineering guidelines for this feature, see 7.3 LOFD-001052 Flash CS
Fallback to UTRAN. The UtranFlashCsfbSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.
This feature is an enhancement to the optional feature LOFD-001033 CS Fallback to
UTRAN. After this feature is activated. the eNodeB obtains the UTRAN cell information
through the RIM procedure and then sends the LTE-to-UMTS redirection message
including the obtained UTRAN cell information to the UE. In this case, the UE can
access a UTRAN cell without obtaining the UTRAN cell information. This reduces the
access delay. For details about how the UTRAN cell information is delivered to the
eNodeB through the RIM procedure, see Interoperability Between UMTS and LTE.
This feature requires that the eNodeB can obtain UTRAN cell information through the
RIM procedures and the networks and UEs involved must support 3GPP Release 9 or
later. For details about the RIM procedure, see 3.10 RIM Procedure Between E-UTRAN and
UTRAN.
Other procedures are the same as those in CSFB to UTRAN. For details, see 3.1 Basic
CSFB to UTRAN.
3.3 Ultra-Flash CSFB to UTRAN
This section describes the optional feature LOFD-070202 Ultra-Flash CSFB to UTRAN.
For details about the engineering guidelines for this feature, see 7.4 LOFD-070202 Ultra-Flash
CSFB to UTRAN. The UtranUltraFlashCsfbSwitch option in the
This feature is a Huawei-proprietary feature. To enable this feature, the MME, MSC, and
RNC must all provided by Huawei and support this feature.
When a UE initiates a CS service setup request in an LTE cell that does not support
VoIP, this feature enables the eNodeB to hand over the UE to the UTRAN through the
SRVCC handover procedure. This shortens the access delay for CS fallbacks by 1
second.
The measurement procedure and blind handover procedure for this feature are the same
as those in CSFB to UTRAN. For details, see 3.1 Basic CSFB to UTRAN.
NOTE:
The following table describes the parameters that must be set in the GLOBALPROCSWITCH MO to turn
on the UE compatibility switch when UEs do not support Ultra-Flash CSFB, resulting in UE compatibility
problems.
3.4 CS Fallback with LAI to UTRAN
This section describes the optional feature LOFD-001068 CS Fallback with LAI to
UTRAN. For details about the engineering guidelines for this feature, see 7.5 LOFD-001068
CS Fallback with LAI to UTRAN. This feature is under license control and is not controlled by a
switch.
This feature mainly applies to the following scenarios:
• In a multi-PLMN or national roaming scenario
An LAI consists of a PLMN ID and a LAC. In the CSFB with LAI function, the
PLMN ID identifies the CS network that the UE has registered with and will fall
back to after fallback.
If the serving E-UTRAN cell has multiple neighboring UTRAN or GERAN cells
with different PLMN IDs and the InterPlmnHoSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected, or the serving PLMN
differs from the target PLMN, the operator can use CSFB with LAI to achieve
fallback to a specified target network.
• In a tracking area (TA) that overlaps multiple location areas (LAs)
The eNodeB selects a CSFB target cell with the same LAC as that mapped to the
network to which the UE has attached. An LAU is not required after CSFB, and
therefore the CSFB delay does not include the LAU time.
UTRAN. With this feature, the eNodeB selects a target frequency or cell for
measurement or blind handover based on the LAI sent by the MME.
• In a measurement procedure, the eNodeB selects only an inter-RAT frequency on
which the PLMN ID of a neighboring cell is the same as that in the LAI received.
The follow-up measurement procedure is similar to that in CS Fallback to UTRAN.
For details, see 3.1.1 Handover Measurement.
The difference is that the eNodeB sorts neighboring cells in the following order after
receiving measurement reports from a UE:
1. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
2. Neighboring cells with PLMN IDs the same as that in the LAI but LACs
different from that in the LAI
If no frequency or neighboring cell can be selected based on the LAI, the processing
is the same as that when no LAI is received.
• In a blind handover procedure, the eNodeB first selects a target cell for blind
handover.
If no neighboring UTRAN cell is configured, the eNodeB preferentially selects the
UTRAN frequencies whose PLMN ID is the same as that in the LAI. The follow-up
procedure is the same as that described in 3.1.2 Blind Handover.
If neighboring UTRAN cells are configured, the eNodeB preferentially selects the
operating UTRAN frequencies of the neighboring UTRAN cells whose PLMN ID is
the same as that in the LAI. The eNodeB then sorts the frequencies based on the
blind handover priorities of the neighboring cells and frequency priorities for
connected mode. For details, see 3.1.2 Blind Handover.
The eNodeB selects a target cell in the following order of preference:
1. Neighboring cell whose PLMN ID and LAC are the same as those in the LAI
2. If no neighboring cells described in 1 exist, the eNodeB selects the
neighboring cells with PLMN IDs the same as that in the LAI but LACs
different from that in the LAI.
3. If no neighboring cells described in 1 and 2 exist, the eNodeB selects the
neighboring cells with PLMN IDs the same as the serving PLMN ID of the
UE.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter is selected, the eNodeB also selects cells whose PLMN IDs are in
the target PLMN list.
3.5 E-UTRAN to UTRAN CS Steering
This section describes the CS steering function in the optional feature LOFD-001078 E-
UTRAN to UTRAN CS/PS Steering. For details about the engineering guidelines for this
function, see 7.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering. For details about the PS
steering function in this feature, see Inter-RAT Mobility Management in Connected Mode.
This feature applies to a scenario where service steering is required in a UTRAN with
multiple UTRAN frequencies. By setting CS service priorities for UTRAN frequencies,
the operator can achieve CSFB from E-UTRAN only to the UTRAN frequency that has a
high CS service priority.
CS Steering in CSFB
This function is an enhancement to the CS Fallback to UTRAN feature. The

enhancements are as follows:
• During inter-RAT measurement on the UTRAN, frequencies with a high CS service
priority are preferentially measured.
The UtranFreqLayerMeasSwitch option of the
ENodeBAlgoSwitch.FreqLayerSwtich parameter specifies whether to enable this
function.
If the option is selected, the eNodeB preferentially selects frequencies with a high
CS service priority specified by the UtranNFreq.CsPriority parameter as the
measurement targets. A larger value of this parameter indicates a higher priority. If
this parameter is set to Priority_0(Priority 0) for a frequency, the eNodeB does not
select this frequency as the measurement target. The follow-up measurement
procedure is the same as that in CS Fallback to UTRAN. For details, see 3.1.1
Handover Measurement.
• During blind handover, cells working on frequencies with a high CS service priority
are preferentially selected.
The UtranFreqLayerBlindSwitch option of the
ENodeBAlgoSwitch.FreqLayerSwtich parameter specifies whether to enable this
function.
If the option is selected, the eNodeB preferentially selects cells working on
frequencies with a high CS service priority specified by the UtranNFreq.CsPriority
parameter. A larger value of this parameter indicates a higher priority. If this
parameter is set to Priority_0(Priority 0) for a frequency, the eNodeB does not
select cells working on this frequency. The follow-up blind handover procedure is
the same as that in CS Fallback to UTRAN. For details, see 3.1.2 Blind Handover.
LAI-based CS Steering in CSFB

This function is an enhancement to the CS Fallback with LAI to UTRAN feature. The
enhancements are as follows:
• Enhancement in measurement
1. The eNodeB selects inter-RAT frequencies on which the PLMN ID of a
neighboring cell is the same as the PLMN ID in the LAI.
2. Among the selected frequencies, the eNodeB selects a frequency with a high
CS service priority specified by the UtranNFreq.CsPriority parameter.
3. The follow-up measurement procedure is similar to that in CS Fallback to
UTRAN. For details, see 3.1.1 Handover Measurement.
The difference is that the eNodeB sorts neighboring cells in the following
order after receiving measurement reports from a UE:
4. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
5. Neighboring cells with PLMN IDs the same as that in the LAI but LACs
different from that in the LAI
6. Neighboring cells with PLMN IDs the same as the serving PLMN ID of the
UE
• Enhancement in blind handover
1. The eNodeB selects frequencies whose PLMN ID is the same as the PLMN ID
in the LAI.
2. Among the selected frequencies, the eNodeB selects a frequency with a high
CS service priority specified by the UtranNFreq.CsPriority parameter.
3. The eNodeB selects a neighboring cell whose PLMN ID and LAC are the
same as those in the LAI.
4. If such a neighboring cell is unavailable, the eNodeB selects a neighboring
cell whose PLMN ID is the same as that in the LAI but LAC is different from
that in the LAI.
5. The follow-up blind handover procedure is the same as that in CS Fallback to
UTRAN. For details, see 3.1.2 Blind Handover.
3.6 CS Fallback Steering to UTRAN
This chapter describes the optional feature LOFD-001088 CS Fallback Steering to

UTRAN. For details about the engineering guidelines for this feature, see 7.6 LOFD-001088
CS Fallback Steering to UTRAN. The UtranCsfbSteeringSwitch option of the
This feature is an enhancement to the optional feature LOFD-001033 CSFB to UTRAN.
In terms of the UE status at the time when the UE initiates a CS service, you can
configure the target RAT and handover policy flexibly. There are two types of UEs:
• CS-only UE
CS-only UE If the MME uses the INITIAL CONTEXT SETUP REQUEST message
to send the CSFB indicator to the eNodeB, the eNodeB determines that the UE is in
idle mode at the time when the UE initiates the CS service. This UE is called a CS-
only UE.
• CS+PS UE
If the MME uses the UE CONTEXT MODIFICATION REQUEST message to send
the CSFB indicator to the eNodeB, the eNodeB determines that the UE is
performing PS services at the time when the UE initiates the CS service. This UE is
called a CS+PS UE.
CS-only UE
If the UE is a CS-only UE, the eNodeB selects the target RAT based on the RAT
priorities for CSFB of CS-only UEs. The priorities are specified by the following
parameters:
• CSFallBackBlindHoCfg.IdleCsfbHighestPri: specifies the highest-priority RAT
for CSFB of CS-only UEs.
• CSFallBackBlindHoCfg.IdleCsfbSecondPri: specifies the second-highest-
priority RAT for CSFB of CS-only UEs.
• CSFallBackBlindHoCfg.IdleCsfbLowestPri: specifies the lowest-priority RAT
for CSFB of CS-only UEs.
The eNodeB can select a neighboring cell or frequency with a lower-priority RAT only if
no neighboring cell or frequency with higher-priority RATs is configured.
If the target system with the highest priority is UTRAN, the eNodeB selects the target
frequencies based on the setting of the UtranNFreq.CsPriority parameter. For details,
see 3.5 E-UTRAN to UTRAN CS Steering.
The eNodeB selects the handover policy for CSFB of CS-only UEs based on the setting
of the CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. PS HO and
redirection are selected in descending order.
CS+PS UE
The eNodeB selects the target RAT based on the RAT priorities specified by the
following parameters:
• CSFallBackBlindHoCfg.InterRatHighestPri: specifies the RAT with the highest
priority.
• CSFallBackBlindHoCfg.InterRatSecondPri: specifies the RAT with the second-
highest priority.
• CSFallBackBlindHoCfg.InterRatLowestPri: specifies the RAT with the lowest
priority.
The eNodeB can select a neighboring cell or frequency with a lower-priority RAT only if
no neighboring cell or frequency with higher-priority RATs is configured.
If the target system with the highest priority is UTRAN, the eNodeB selects the target
frequencies based on the setting of the UtranNFreq.CsPsMixedPriority parameter.
The UtranNFreq.CsPsMixedPriority and UtranNFreq.CsPriority parameters have
similar setting principles. For details, see 3.5 E-UTRAN to UTRAN CS Steering.
The eNodeB selects the handover policy for CSFB based on the setting of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. PS HO and redirection are
selected in descending order.
3.7 Load-based CSFB to UTRAN
This chapter describes load-based CSFB to UTRAN. This function is an enhancement to

the CS Fallback to UTRAN feature. For details about the engineering guidelines for this
feature, see 7.1 LOFD-001033 CS Fallback to UTRAN. The CSFBLoadInfoSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.
In load-based CSFB to UTRAN, the eNodeB uses the RIM procedure in Multiple Report
mode to obtain the load information about UTRAN cells. For details about the RIM
procedure, see 3.10 RIM Procedure Between E-UTRAN and UTRAN. After receiving the load
information about UTRAN cells, the eNodeB saves the information and uses the
information to determine the target UTRAN cell for the CSFB.
In load-based CSFB to UTRAN, the measurement and blind handover procedures are the
same as those in the CS Fallback to UTRAN feature. For details, see 3.1 Basic CSFB to
UTRAN.
When the eNodeB selects the target UTRAN cell for the CSFB based on the load status
of UTRAN cells, the eNodeB considers UTRAN cells in descending order as follows:
cells whose load status is normal, cells whose load status is congested, and cells whose
load status is overloaded.
Load-based CSFB to UTRAN affects the target cell selection at a later phase. If
measurement is performed, the eNodeB does not select a low-priority frequency because
all UTRAN cells on the high-priority frequency are overloaded.
3.8.1 Basic Handover Decision
When the handover policy is PS HO, SRVCC, or redirection (excluding flash

redirection), the eNodeB does not need to obtain system information of the peer and
performs the basic 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. If the eNodeB receives measurement reports
about different RATs, it processes the reports in an FIFO manner.
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 in the
neighboring cell list
If the inter-PLMN handover switch is turned on, such cells are not excluded.
• Neighboring cells in the areas indicated by the IE Handover Restriction List in the
INITIAL CONTEXT SETUP REQUEST message sent from the MME
After the preceding exclusion, the eNodeB excludes cells from the neighboring cell list
based on SPID-based mobility management in connected mode. For details, see LOFD-
00105401 Camp & Handover Based on SPID in Flexible User Steering Feature
Parameter Description.
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 3-2.
Table 3-2 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.
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.
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 attempt.
3.8.2 Flash Redirection Decision
When the handover policy requires the eNodeB to obtain system information about the
peer, for example, flash redirection, handover decision based on system information is
performed. If the handover decision is based on system information, the eNodeB includes
system information of the target cell of the corresponding RAT. Therefore, the time for
reading cell system information is not required so that the UE can quickly access the
target network.
Decision based on system information adheres to the following principles:
• In blind handover scenarios:
1. The target cell list for blind handover is selected, including other cells under
the target frequency for redirection. The UTRAN_SWITCH option of the
ENodeBAlgoSwitch.NCellRankingSwitch parameter specifies the sequence of
adding other cells.
When this option is selected, the eNodeB adds other cells in the target
frequency according to UtranNCell.NCellMeasPriority in descending order.
When this option is cleared, the eNodeB adds other cells in the target
frequency according to UtranNCell.CellMeasPriority in descending order.
2. Basic handover decision is applied. For details, see 3.8.1 Basic Handover Decision.
3. Cells whose system information is not obtained are filtered out.
4. The eNodeB excludes cells from the neighboring cell list based on SPID-
based mobility management in connected mode. For details, see LOFD-
00105401 Camp & Handover Based on SPID in Flexible User Steering
• In measurement scenarios:
1. Cells in the candidate cell list generated by measurement are selected, plus
cells that are not in measurement reports but work on the target frequency for
redirection. The UTRAN_SWITCH option of the
ENodeBAlgoSwitch.NCellRankingSwitch parameter specifies the sequence of
adding other cells.
2. Basic handover decision is applied. For details, see 3.8.1 Basic Handover Decision.
3. Cells whose system information is not obtained are filtered out.
You can specify the number of UTRAN cells contained in the redirection message by
setting the InterRatHoComm.CellInfoMaxUtranCellNum parameter. Assume that this
parameter is set to N.
• If the number of target cells after flash redirection decision is greater than N, the
eNodeB selects the first N cells.
• If the number of target cells after flash redirection decision is smaller than N, the
eNodeB selects target cells after flash redirection decision.
The eNodeB obtains system information of target cells in the RAN information
management (RIM) procedure. If a target cell does not support the RIM procedure, the
eNodeB cannot obtain system information of that cell.
3.9.1 Handover Policy Selection
When a UE in an LTE system needs to perform voice service but the LTE system does
not support VoIP, a CSFB to an inter-RAT network is triggered.
CSFB from E-UTRAN to UTRAN can be based on PS handover, redirection, or flash
redirection, as shown in Figure 3-4. This handover policy selection procedure is based on
the assumption that neighboring frequency and neighboring cell configurations are
proper.
During a CSFB based on blind PS handover, if the target cell with the highest blind
handover priority fails to prepare the handover, the eNodeB attempts another cell with the
second highest blind handover priority. The eNodeB can attempt a maximum of eight
cells. If all these cells fail in preparation, the eNodeB performs CSFB based on
redirection.
Figure 3-4 E-UTRAN-to-UTRAN CSFB policy selection procedure
The parameters mentioned in the preceding figure are described as follows:
• The timer length is specified by the CSFallBackHo.CsfbProtectionTimer parameter. If
the UE stays in the area covered by the eNodeB before the timer expires, the
eNodeB performs the CSFB based on the blind redirection,
▪ The eNodeB preferentially selects a system that the UE has not measured. For
example, if the UE has measured the UTRAN, the eNodeB preferentially
selects the GERAN for redirection.
▪ If a cell to which the eNodeB has never attempted to hand over the UE is
reported, the eNodeB preferentially selects the operating frequency of the cell
for redirection.
▪ The eNodeB selects the target cell for redirection as it does during blind
handover. For details about how the eNodeB performs target selection during
blind handover, see 3.1.2 Blind Handover.
▪ If there is not target frequency available for redirection, the eNodeB stops the
procedure.
▪ If flash CSFB is enabled in this situation, redirection-based CSFB performed
by the eNodeB is referred to as CSFB emergency redirection. In this scenario,
you need to set the InterRatHoComm.UTRANCellNumForEmcRedirect parameter
to specify the maximum number of UTRAN cell system information messages
that can be transmitted during a CSFB emergency redirection procedure.
• The blind handover switch is controlled by the BlindHoSwitch option in the
eNodeB-level parameter ENodeBAlgoSwitch.HoModeSwitch and the
BlindHoSwitch option in the cell-level parameter CellHoParaCfg.HoModeSwitch.
The blind handover function takes effect only when the eNodeB-level
BlindHoSwitch and cell-level BlindHoSwitch options are selected.
• The adaptive-blind-handover-based CSFB switch is controlled by the
CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter.
• If PS handover for CSFB is required, select the UtranPsHoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter and the PS_HO option of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. If either option is cleared, PS
handover for CSFB is invalid. The eNodeB selects the redirection policy. If the
redirection policy is invalid and the CSFB protection timer expires, the eNodeB
enters the blind redirection procedure.
• If blind redirection for CSFB is required, select the REDIRECTION option of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.
• The CSFB policy is specified by different parameters, depending on whether LOFD-
001088 CS Fallback Steering to UTRAN is enabled.
If this feature is enabled:
▪ The CSFB policy for UEs in idle mode is specified by the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.
▪ The CSFB policy for UEs in connected mode is specified by the
If this feature is not enabled, the CSFB policy is specified by the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether UEs are in
idle or connected mode.
This section describes the optional feature LOFD-070202 Ultra-Flash CSFB to UTRAN.
For details about the engineering guidelines for this feature, see 7.4 LOFD-070202 Ultra-Flash
CSFB to UTRAN. The UtranUltraFlashCsfbSwitch option in the
This feature is a Huawei-proprietary feature. To enable this feature, the MME, MSC, and
RNC must all provided by Huawei and support this feature.
When a UE initiates a CS service setup request in an LTE cell that does not support
VoIP, this feature enables the eNodeB to hand over the UE to the UTRAN through the
SRVCC handover procedure. This shortens the access delay for CS fallbacks by 1
second.
The measurement procedure and blind handover procedure for this feature are the same
as those in CSFB to UTRAN. For details, see 3.1 Basic CSFB to UTRAN.
not support VoIP, the eNodeB decides to perform ultra-flash CSFB if LOFD-070202
Ultra-Flash CSFB to UTRAN is enabled. Figure 3-5 shows ultra-flash CSFB to UTRAN by
using the SRVCC procedure after the eNodeB performs a measurement or blind handover
decision. For details about how to select other CSFB policies, see 3.9.1 Handover Policy
Selection.
Figure 3-5 Ultra-Flash CSFB to UTRAN
The preceding figure is described as follows:

• The ultra-flash CSFB to UTRAN switch is controlled by the
UtranUltraFlashCsfbSwitch option of the ENodeBAlgoSwitch. HoAlgoSwitch
parameter.
• At least one neighboring UTRAN cell's RNC support ultra-flash CSFB to UTRAN.
▪ If all neighboring UTRAN cells' RNCs support ultra-flash CSFB to UTRAN,
no configuration is required.
▪ If some neighboring UTRAN cells' RNCs do not support ultra-flash CSFB to
UTRAN, the following configurations are required:
Select the UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.
For RNCs that do not support ultra-flash CSFB to UTRAN, do not select the
corresponding UltraFlashCsfbCap option of the
UtranNetworkCapCfg.NetworkCapCfg parameter.
To speed up CSFB for UEs in idle mode by shortening end-to-end delays and to reduce
the CSFB failure rate due to initial context setup failures, redirection-based CSFB for
UEs in idle mode is optimized.
The optimization is performed after the eNodeB decides to perform blind handover, as
shown in Figure 3-6.
Figure 3-6 Redirection-based CSFB optimization for UEs in idle mode
The optimization switch is controlled by the IdleCsfbRedirectOptSwitch option of the

GlobalProcSwitch.ProtocolMsgOptSwitch parameter.
For details about how to decide between redirection and flash redirection, see 3.9.1
Handover Policy Selection.
For the signaling procedure, see 3.11.6 Redirection-based CSFB Optimization for UEs in Idle Mode.
3.9.4 CSFB Admission Optimization for UEs in Idle Mode
UEs in idle mode only have a default bearer for data service, and the allocation/retention
priority (ARP) of the default bearer is generally lower. When a UE in idle mode needs to
perform CSFB but the target cell is congested or cannot accommodate more UEs, this UE
cannot preempt resources in the target cell.
To ensure the CSFB success rate in the preceding scenario, the eNodeB can preferentially
admit CSFB UEs. This function is controlled by the
CSFallBackPolicyCfg.CsfbUserArpCfgSwitch parameter.
A larger value of the CsFallbackPolicyCfg.NormalCsfbUserArp parameter indicates a
higher probability of admission of CSFB UEs in idle mode. For details about the
admission procedure, see Admission and Congestion Control.
3.10 RIM Procedure Between E-UTRAN and UTRAN
The RIM procedure exchanges information between the E-UTRAN and UTRAN through
the core networks.
In CSFB procedures, the eNodeB obtains the load information of external UTRAN cells
from RNCs through the RIM procedure if the parameter
GlobalProcSwitch.UtranLoadTransChan is set to BASED_ON_RIM.
In flash CSFB procedures, the eNodeB obtains the system information (SI) of external
cells from RNCs through the RIM procedure. For details about related parameters, see
3.10.1 RIM Procedure Through the Core Network and 3.10.2 RIM Procedure Through the eCoordinator.
The RIM procedure includes the following two information exchange modes:
• Single Report
In Single Report mode, the source sends a request, and then the target responds with
a single report.
When flash CSFB to UTRAN is triggered, the eNodeB sends a RIM message to the
RNC and then includes the obtained SI in a redirection message to send to the UE. If
the SI fails to be obtained from the RNC, the eNodeB no longer attempts the RIM
request.
• Multiple Report
In Multiple Report mode, the target responds with a report after receiving a request
from the source, and the target also sends a report to the source each time
information about the target changes.
When flash CSFB to UTRAN is triggered, the eNodeB sends RIM messages to all
neighboring UTRAN cells every four seconds no matter whether the eNodeB has
CSFB services.
To ensure that the SI of the target cell can be obtained successfully, the eNodeB
starts a four-second timer when it sends a RIM message.
▪ If the eNodeB receives a response to the RIM message before the timer expires,
the eNodeB saves the obtained SI.
▪ If the eNodeB receives a response to the RIM message after the timer expires,
the eNodeB considers that an exception occurs and discards the SI.
▪ If the eNodeB does not receive a response to the RIM message when the timer
expires, the eNodeB sends the RIM message and starts the timer again (called a
retry) two hours later. If the eNodeB still does not receive a response after 10
retries, the RIM request fails. The interval between the nth and (n+1)th retries
is twice the interval between the (n-1)th and nth retries. For example, the first
retry occurs two hours after the first SI acquisition fails, the second retry occurs
four hours after the first retry fails, and the third retry occurs six hours after the
second retry fails. For each retry, the eNodeB sends a RIM message and
restarts the timer.
The eNodeB may obtain incorrect SI due to the abnormalities in the UTRAN, core
network, or transport network. To avoid this situation, the eNodeB selects a time
point randomly every day from 02:00 a.m. to 04:00 a.m and deletes all the obtained
SI. Then, the eNodeB requests the SI of UTRAN cells through the RIM procedure
again.
If a neighboring UTRAN cell is faulty or deactivated, the RNC sends an END
message to notify the eNodeB of stopping the RIM procedure. In this case, the
eNodeB deletes the obtained SI and requests SI again in the next RIM procedure.
Currently, the eNodeB triggers a RIM procedure in Multiple Report mode only if
MMEs comply with 3GPP Release 9 or later.
The RIM procedure can be performed through the core network or eCoordinator.
3.10.1 RIM Procedure Through the Core Network
If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is

performed through the core network As shown in Figure 3-7, the RIM procedure involves
the eNodeB, MME, SGSN, and RNC Among these NEs, the MME and the SGSN
transfer but do not resolve information. For details, see section 8c "Signalling procedures
between RIM SAPs" in 3GPP TS 48.018 V10.0.0.
Figure 3-7 Performing the RIM procedure through the core network
The preceding figure is described as follows:

• The RIM procedure between EUTRAN and UTRAN is controlled by the
UTRAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch
parameter.
If this option is selected, the eNodeB uses the RIM procedure in Multiple Report
mode to obtain the system information of external UTRAN cells.
• Whether multiple UTRAN operators can use different mobility policies is specified
by the UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.
• The RIM procedure for obtaining SI is controlled by the SiByRimCapCfg option of
the UtranNetworkCapCfg.NetworkCapCfg parameter.
Figure 3-8 Information exchange mode selection for the RIM procedure
3.10.2 RIM Procedure Through the eCoordinator
If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is

performed through the eCoordinator. As shown in Figure 3-9, the RIM procedure through
the eCoordinator involves the eNodeB, eCoordinator, and RNC. Among these NEs, the
MME and the SGSN transfer but do not resolve information.
Figure 3-9 RIM procedure through the eCoordinator
The RIM procedure through the eCoordinator requires that the corresponding switches of
all NEs involved to be switched on.
During the RIM procedure through the eCoordinator, the eNodeB does not send RIM
messages to the EPC or process RIM messages from the EPC.
The information exchange mode for the eCoordinator-based RIM procedure is controlled
by UTRAN_RIM_SWITCH under the ENodeBAlgoSwitch.RimSwitch parameter.
• If this switch is on, the eNodeB uses the RIM procedure in Multiple Report mode to
obtain the system information of external UTRAN cells.
• If this switch is off, the eNodeB uses the RIM procedure in Single Report mode.
3.11 CSFB to UTRAN
The combined EPS/IMSI attach procedure is performed by exchanging NAS messages.

Therefore, this procedure is transparent to the eNodeBs. After a CSFB-capable UE is
powered on in the E-UTRAN, the UE initiates a combined EPS/IMSI attach procedure,
as shown in Figure 3-10.
Figure 3-10 Combined EPS/IMSI attach procedure
HSS: home subscriber server VLR: visitor location register

NOTE:
The symbols that appear in signaling procedure figures throughout this document are explained as follows:
• An arrow denotes the transmission of a message.
• A plain box denotes a mandatory procedure.
• A dashed box denotes an optional procedure.
The combined EPS/IMSI attach procedure is described as follows:

1. The UE sends a Combined attach request message to the MME, requesting a
combined EPS/IMSI attach procedure. This message also indicates whether the
CSFB or SMS over SGs function is required.
2. The EPS attach procedure is performed in the same way as it is performed within
the LTE system. For details, see section 5.3.2 in 3GPP TS 23.401 V9.2.0.
3. The MME allocates an LAI to the UE, and then it finds the MSC/VLR for the UE
based on the LAI. If multiple PLMNs are available for the CS domain, the MME
selects a PLMN based on the selected PLMN information reported by the eNodeB.
Then, the MME sends the MSC/VLR a Location update request message, which
contains the new LAI, IMSI, MME name, and location update type.
4. The MSC/VLR performs the location update procedure in the CS domain.
5. The MSC/VLR responds with a Location update accept message that contains
information about the VLR and temporary mobile subscriber identity (TMSI). The
location update procedure is successful.
6. The UE is informed that the combined EPS/IMSI attach procedure is successful. If
the network supports SMS over SGs but not CSFB, the message transmitted to the
UE contains the information element (IE) SMS-only. The message indicates that
the combined EPS/IMSI attach procedure is successful but only SMS is supported.
During CSFB based on PS handover, the UE is transferred from the E-UTRAN to the
UTRAN by performing a PS handover. It then initiates a CS service in the UTRAN.
Call procedure
shows the procedure for CSFB to UTRAN based on PS handover for mobile-
Figure 3-11
originated calls.
Figure 3-11 CSFB to UTRAN based on PS handover for mobile-originated calls
1. The UE sends the MME an NAS message Extended Service Request to initiate a
CS service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB
procedure. If the MME supports the LAI-related feature, the MME also delivers the
LAI to the eNodeB.
3. If the MME supports the LAI-related feature, the MME also delivers the LAI to the
eNodeB.
4. The eNodeB initiates the preparation phase for a PS handover. If the preparation is
successful, the eNodeB instructs the UE to perform a handover.
NOTE:
For details about how the eNodeB selects a target cell and a CSFB policy, see 3.8 Handover
Decision and 3.9 Handover Execution.
5. After the handover, the UE may initiate a CS call establishment procedure with an
LAU or combined RAU/LAU procedure in the UTRAN.
6. The follow-up procedures are performed for the PS handover. These procedures
include data forwarding, path switching, and RAU. This step is performed together
with 5.
CSFB Procedure for Mobile-terminated Calls

shows the procedure for CSFB to UTRAN based on PS handover for mobile-
Figure 3-12
terminated calls.
Figure 3-12 CSFB to UTRAN based on PS handover for mobile-terminated calls
1. The MSC sends a Paging Request message from the CS domain to the MME over
the SGs interface. Then, either of the following occurs:
• If the UE is in idle mode, the MME sends a Paging message to the eNodeB.
Then the eNodeB sends a Paging message over the Uu interface to inform the
UE of an incoming call from the CS domain.
• If the UE is in active mode, the MME sends the UE an NAS message to
inform the UE of an incoming call from the CS domain.
2. The UE sends an Extended Service Request message containing a CS Fallback
Indicator after receiving the paging message from the CS domain.
3. The MME instructs the eNodeB over the S1 interface to perform CSFB.
4. The subsequent steps are similar to steps 3 through 6 in the procedure for CSFB to
UTRAN based on PS handover for mobile-originated calls. The only difference is
that the UE sends a Paging Response message from the UTRAN cell.
3.11.3 Signaling procedure of redirection to CDMA2000 1xRTT
During CSFB based on PS redirection, the eNodeB receives a CS Fallback Indicator, and
then it sends an RRC Connection Release message to release the UE. The message
contains information about a target UTRAN frequency, reducing the time for the UE to
search for a target network. After selecting the UTRAN, the UE acquires the system
information of a UTRAN cell. Then, the UE performs initial access to the cell to initiate a
CS service. For the UTRAN, the UE is an initially accessing user.
Call procedure
shows the procedure for CSFB to UTRAN based on redirection for mobile-
Figure 3-13
originated calls.
Figure 3-13 CSFB to UTRAN based on redirection for mobile-originated calls
CS service.
LAI to the eNodeB.
eNodeB.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to
perform a redirection. The message contains information about a target UTRAN
frequency. Then, the eNodeB initiates an S1 UE context release procedure.
NOTE:
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU
in the target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.

In a mobile-terminated call, the MSC sends a Paging request message from the CS
domain to the MME over the SGs interface, and then the MME or eNodeB initiates a
paging procedure for the UE. The paging procedure is similar to that for UTRAN
described in 3.11.2 CSFB Based on PS Handover. The subsequent steps are the same as the
steps in the procedure for CSFB to UTRAN based on PS handover for mobile-originated
calls.
3.11.4 Flash CSFB
During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then
it sends an RRC Connection Release message to release the UE. The message contains
information about a target UTRAN frequency, as well as one or more physical cell
identities and their associated system information. In this way, the UE can quickly access
the target UTRAN without the need to perform the procedure for acquiring system
information of the target UTRAN cell. Then, the UE can directly initiate a CS service in
the UTRAN cell.
Call procedure
shows the procedure for CSFB to UTRAN based on flash redirection for
Figure 3-14
mobile-originated calls.
Figure 3-14 CSFB to UTRAN based on flash redirection for mobile-originated calls
CS service.
LAI to the eNodeB.
eNodeB.
perform a redirection. The message contains information about a target UTRAN
frequency, as well as one or more physical cell identities and their associated
system information. Then, the eNodeB initiates an S1 UE context release
procedure.
NOTE:
Decision and 3.9 Handover Execution. The system information of the target cell is acquired during
the RIM procedure.
in the target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.
steps in the procedure for CSFB to UTRAN based on PS handover for mobile-originated
calls.
CSFB Procedure for Mobile-Originated Calls
shows the procedure of ultra-flash CSFB to UTRAN for mobile-originated

Figure 3-15
calls. Compared with the standard procedure described in chapter 6 "Mobile Originating
Call" in 3GPP TS 23.272 V10.9.0 and 3GPP TS 24.008 V11.0.0, Huawei ultra-flash
CSFB to UTRAN for mobile-originated calls:
• Excludes the authentication procedure because the UE has been authenticated in the
LTE system before CSFB to UTRAN.
• Excludes the ciphering procedure because the UE has performed ciphering as
instructed during SRVCC.
• Excludes the IMEI check procedure because the MME has sent the IMEI to the
MSC during the preparation for SRVCC.
• Excludes the CS resource setup procedure because the UTRAN system has prepared
CS resources during SRVCC and therefore the UE does not need to reestablish the
CS resource after SRVCC.
Figure 3-15 Flash CSFB to UTRAN for mobile-originated calls
CSFB Procedure for Mobile-Terminated Calls
Figure 3-16shows the procedure of ultra-flash CSFB to UTRAN for mobile-terminated

calls. Ultra-flash CSFB for mobile-terminated calls excludes the same procedures as
ultra-flash CSFB for mobile-originated calls. For details about the standard procedure,
see chapter 6 "Mobile Originating Call" in 3GPP TS 23.272 V10.9.0 and 3GPP TS
24.008 V11.0.0.
Figure 3-16 Ultra-flash CSFB to UTRAN for mobile-terminated calls
After the NodeB receives an initial context setup request with a CS Fallback Indicator
from the MME, the eNodeB does not perform the UE capability query, Uu security mode
command, or RRC connection reconfiguration procedure with dashed lines in the
following figure:
Figure 3-17 Redirection-based CSFB optimization for UEs in idle mode
3.11.7 CSFB for SMS
SMS services are unknown to the eNodeB because SMS messages are encapsulated in
NAS messages. During interworking with the UTRAN, SMS messages are exchanged
between the MME and the MSC over the SGs interface. Because a UE does not require
fallback to the UTRAN to perform an SMS service, the SMS over SGs function can be
used in a place covered only by the E-UTRAN.
As the SMS service is transparent to the eNodeB, the procedure is not described in this
document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
The CSFB procedure for an emergency call is the same as the CSFB procedure for a
normal mobile-originated voice service. The UE sends an RRC Connection Request
message over the Uu interface or the MME sends an Initial Context Setup Request or UE
Context Modification Request message, which contains an IE to inform the eNodeB of
the service type. Emergency calls take precedence over other services in the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the
cells in the handover restriction list when selecting the target cell. The eNodeB sends the
RNC a handover request with the IE CSFB high priority in the IE Source to Target
Transparent Container. This request informs the RNC that a CSFB procedure is required
for an emergency call. Upon receiving the information, the RNC preferentially processes
this call when using related algorithms such as admission control.
If redirection is used for CSFB for emergency calls, the RRC Connection Request
message that the UE sends when accessing the UTRAN contains the indication of a CS
emergency call.
The UTRAN will treat this call as a common CS emergency call. For details about
admission and preemption of emergency calls, see Emergency Call.
3.11.9 CSFB for LCS
After a UE initiates an LCS request, the MME performs an attach or combined

TAU/LAU procedure to inform the UE of the LCS capability of the EPS. If the EPS does
not support LCS, the UE falls back to the UTRAN to initiate LCS under the control of the
EPS. The CSFB procedure is the same as the procedure for CSFB to UTRAN for mobile-
originated calls.
If the UTRAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the
MSC sends an LCS indicator to the MME over the SGs interface. Then, the MME
instructs the eNodeB to perform CSFB for the UE. The CSFB procedure is the same as
the procedure for CSFB to UTRAN for mobile-terminated calls. The UE performs the
LCS service after the fallback to the UTRAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272
V10.0.0 and LCS.
4 CSFB to GERAN
CSFB to GERAN can be implemented in different ways, and this section covers the
following features/functions:
• LOFD-001034 CS Fallback to GERAN
• LOFD-001053 Flash CS Fallback to GERAN
• OFD-001069 CS Fallback with LAI to GERAN
• LOFD-001089 CS Fallback Steering to GERAN
• LOFD-081283 Ultra-Flash CSFB to GERAN
The triggering condition for different features are different. Basically the procedure is as
follows:
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
The eNodeB controls the UE to be handed over from the serving cell to the target
cell.
4.1 Basic CSFB to GERAN
This section describes the optional feature LOFD-001034 CS Fallback to GERAN. For
details about the engineering guidelines for this feature, see 7.8 LOFD-001034 CS Fallback to
GERAN. The GeranCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch
parameter specifies whether to enable this feature.
The blind handover switch is controlled by the BlindHoSwitch option in the eNodeB-
level parameter ENodeBAlgoSwitch.HoModeSwitch and the BlindHoSwitch option
in the cell-level parameter CellHoParaCfg.HoModeSwitch. The blind handover
function takes effect only when the eNodeB-level BlindHoSwitch and cell-level
BlindHoSwitch options are selected.
This feature has the same principle as CSFB to UTRAN, except the parameters
mentioned below in this section. For details about the principle of CSFB to UTRAN, see
3.1 Basic CSFB to UTRAN.
Handover Measurement
The frequency priority used during target frequency selection is specified by the
GeranNfreqGroup.ConnFreqPriority parameter. A larger value indicates a higher
priority.
During the GERAN frequency selection for measurement that is different from the
UTRAN frequency selection, if the total number of the GERAN frequencies that can be
delivered in the frequency group with the highest priority and the frequencies that have
been delivered exceeds the allowed maximum number 32, all frequencies in this
frequency group cannot be delivered. The eNodeB determines whether the GERAN
frequencies in the frequency group with the second highest priority can be delivered until
the number of delivered frequencies is less than or equal to the maximum number of
GERAN frequencies allowed for measurement or all frequency groups are determined.
In GERAN, no cell measurement priority is configured. If the number of cells working on
a frequency exceeds the specification, the eNodeB randomly measures certain cells.
Blind Handover
If CSFallBackBlindHoCfg.InterRatHighestPri is set to GERAN(GERAN), the
eNodeB performs CSFB to GERAN.
During blind handover, the target selection procedure is different, depending on whether
neighboring GERAN cells are configured.
• If neighboring GERAN cells are configured:
▪ The blind handover priority of a GERAN neighboring cell is specified by the
GeranNcell.BlindHoPriority parameter. A larger value indicates a higher
priority.
▪ The GERAN frequency group with the highest priority (specified by the
GeranNfreqGroup.ConnFreqPriority parameter) is selected for blind
handover. A larger value indicates a higher priority.
▪ If the priorities of neighboring GERAN cells or frequencies are the same, the
eNodeB randomly selects a target cell or frequency. Due to uncertainty of
random selection, to increase the probability of a successful blind handover,
you are not advised to set an identical priority for neighboring GERAN cells or
frequencies.
• If no neighboring GERAN cell is configured:
▪ Neighboring GERAN frequencies are configured in GeranNfreqGroup MOs.
▪ The PLMN information of the neighboring GERAN frequency is contained in
the configured GeranRanShare or GeranExternalCell MOs.
4.2 Flash CSFB to GERAN
This section describes the optional feature LOFD-001053 Flash CS Fallback to GERAN.
For details about the engineering guidelines for this feature, see 7.10 LOFD-001053 Flash CS
Fallback to GERAN. The GeranFlashCsfbSwitchh option of the
GERAN. After this feature is activated, the eNodeB obtains the GERAN cell information
through the RIM procedure and then sends the LTE-to-GSM redirection message
including the obtained GERAN cell information to the UE. The
InterRatHoComm.CellInfoMaxGeranCellNum parameter specifies the maximum number of
GERAN cells that can be contained in the redirection message, which is configurable.
In this case, the UE can access a GERAN cell without obtaining GERAN cell
information. This reduces the access delay. For details about how the GERAN cell
information is delivered to the eNodeB through the RIM procedure, see Interoperability
Between GSM and LTE.
This feature has the same principle as flash CSFB to UTRAN. For details, see 3.2 Flash
CSFB to UTRAN.
4.3 CS Fallback with LAI to GERAN

This section describes the optional feature LOFD-001069 CS Fallback with LAI to
GERAN. For details about the engineering guidelines for this feature, see 7.12 LOFD-
001069 CS Fallback with LAI to GERAN. This feature is under license control and is not
controlled by a switch.
This feature has the same principle as CS fallback with LAI to UTRAN. For details, see
3.4 CS Fallback with LAI to UTRAN.
4.4 CS Fallback Steering to GERAN
This chapter describes the optional feature LOFD-001089 CS Fallback Steering to

GERAN. For details about the engineering guidelines for this feature, see 7.13 LOFD-
001089 CS Fallback Steering to GERAN. The GeranCsfbSteeringSwitch option of the
The principles of this feature are similar to the principles of the CS Fallback Steering to
UTRAN feature. For details about the principles, see 3.6 CS Fallback Steering to UTRAN.
The eNodeB selects a handover policy for CSFB of a CS-only UE based on the setting of
the CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. The eNodeB selects PS
HO, CCO, and redirection in descending order.
The eNodeB selects a handover policy for CSFB of a CS+PS UE based on the setting of
the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. The eNodeB selects PS HO, CCO,
and redirection in descending order.
4.5 Ultra-Flash CSFB to GERAN
This section describes the optional feature LOFD-081283 Ultra-Flash CSFB to GERAN.
The GeranUltraFlashCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch
parameter specifies whether to enable this feature. This feature is a Huawei-proprietary
feature. To enable this feature, the MME, MSC, and eNodeB must be all provided by
Huawei and support this feature.
When a UE initiates a voice setup request in an LTE cell that does not support VoIP, this
feature enables the eNodeB to transfer the UE to the GERAN through the SRVCC
handover procedure. This shortens the access delay for CS fallbacks by 2 seconds.
• The measurement procedure and blind handover procedure for this feature are the
same as those in CSFB to GERAN. For details, see 3.1 Basic CSFB to UTRAN.
• The SRVCC handover policy for this feature is the same as that for ultra-flash CSFB
to GERAN. For details, see 3.9.2 Ultra-Flash CSFB to UTRAN.
This feature requires that external GERAN cells support ultra-flash CSFB to GERAN.
• If all external GERAN cells support ultra-flash CSFB to GERAN, no configuration
is required.
• If some external GERAN cells do not support ultra-flash CSFB to GERAN, the
following configurations are required:
▪ Set UltraFlashCsfbInd to BOOLEAN_FALSE for external GERAN cells
that do not support ultra-flash CSFB to GERAN.
▪ The ultra-flash CSFB to GERAN capability for external GERAN cells is
specified by the GeranExternalCell.UltraFlashCsfbInd parameter.
When the UE completes voice services on the E-UTRAN after the Ultra-Flash CSFB to
GERAN, you can enable the Fast Return to LTE feature on the GSM side so that the UE
quickly returns to the E-UTRAN. After the UE completes voice services on the GERAN,
the UE carries the LTE frequency information in a Channel Release message and selects
a proper LTE cell to camp on based on the frequency information to accelerate the return
to the E-UTRAN.
When IratMeasCfgTransSwitch in the GlobalProcSwitch.ProtocolMsgOptSwitch
parameter is set to ON, the eNodeB filters LTE frequencies supported by the UE based
on the UE capability to obtain a frequency set. During the SRVCC handover, the eNodeB
sends a Handover Required message containing the frequency set to the BSC of the target
cell and provides reference for the UE to accelerate the return to the E-UTRAN after the
UE completes voice services on the GERAN.
When the CellDrxPara.DrxForMeasSwitch parameter is set to ON(On), the eNodeB
delivers the DRX and gap-assisted measurement configurations if the following
conditions are met. The UE uses the DRX measurement preferentially and makes more
use of DRX sleep time continuously to accelerate the measurement and decrease the
delay.
• The UE cannot perform the gap-assisted measurement. In this case, the
AutoGapSwitch option of the ENODEBALGOSWITCH.HoModeSwitch
parameter is set to OFF(Off) or the interRAT-NeedForGaps option for the GSM
frequency of the UE capability is set to TRUE(True).
• The gap-assisted measurement is not configured for the UE.
• The UE supports DRX.
• The BlindHoSwitch option of the ENODEBALGOSWITCH.HoModeSwitch
parameter is set to OFF(Off).
After the DRX measurement is used, you need to set longer sleep time for measurements.
Therefore, the UE is easier to enter the sleep time, affecting the scheduling by decreasing
the cell throughput.
For details about how to configure measurement-specific DRX troubleshooting and
related parameters, see DRX and Signaling Control.
NOTE:
The following table describes the parameters that must be set in the GLOBALPROCSWITCH MO to turn
on the UE compatibility switch when UEs do not support Ultra-Flash CSFB, resulting in UE compatibility
problems.
The handover decision for CSFB to GERAN is the same as that for CSFB to UTRAN.
For details, see 3.8 Handover Decision.
not support VoIP, a CSFB to an inter-RAT network is triggered.
CSFB from E-UTRAN to GERAN can be based on PS handover, CCO/NACC,
redirection, or flash redirection, as shown in Figure 4-1. This handover policy selection
procedure is based on the assumption that neighboring frequency and neighboring cell
configurations are proper.
During a CSFB based on blind PS handover, if the target cell with the highest blind
handover priority fails to prepare the handover, the eNodeB attempts another cell with the
second highest blind handover priority. The eNodeB can attempt a maximum of eight
cells. If all these cells fail in preparation, the eNodeB performs CSFB based on
redirection.
Figure 4-1 E-UTRAN-to-GERAN handover policy selection procedure
The parameters mentioned in the preceding figure are described as follows:
• The timer length is specified by the CSFallBackHo.CsfbProtectionTimer parameter. If
the UE stays in the area covered by the eNodeB before the timer expires, the
eNodeB performs the CSFB based on the blind redirection,
▪ The eNodeB preferentially selects a system that the UE has not measured. For
example, if the UE has measured the UTRAN, the eNodeB preferentially
selects the GERAN for redirection.
▪ If there is not target frequency available for redirection, the eNodeB stops the
procedure.
• The BlindHoSwitch switch under the ENodeBAlgoSwitch.HoModeSwitch parameter
and the BlindHoSwitch switch under the CELLHOPARACFG.HoModeSwitch
parameter specify whether to enable blind handover. The CSFB blind handover is
triggered only when eNodeB- and cell-level blind handover switches are enabled.
• The adaptive-blind-handover-based CSFB switch is controlled by the
CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter.
• The CSFB policy switches are controlled by the options of the
ENodeBAlgoSwitch.HoModeSwitch parameter:
▪ The PS handover supporting capability is specified by GeranPsHoSwitch.
▪ The CCO supporting capability is specified by GeranCcoSwitch.
▪ The NACC supporting capability is specified by GeranNaccSwitch.
When CSFB to GERAN is based on CCO/NACC, the eNodeB obtains SI of
external cells from RNCs through the RIM procedure. For details about the
RIM procedure, see 4.8 RIM Procedure Between E-UTRAN and GERAN.
• The CSFB policy is specified by different parameters, depending on whether LOFD-
001089 CS Fallback Steering to GERAN is enabled.
If this feature is enabled:
▪ The CSFB policy for UEs in idle mode is specified by the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.
▪ The CSFB policy for UEs in connected mode is specified by the
If this feature is not enabled, the CSFB policy is specified by the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether UEs are in
idle or connected mode.
4.8 RIM Procedure Between E-UTRAN and GERAN
The principles of the RIM procedure between E-UTRAN and GERAN are the same as
those for UTRAN described in 3.10 RIM Procedure Between E-UTRAN and UTRAN.
The RIM procedure between E-UTRAN and GERAN is enabled by default because there
is no switch for selecting a load information transfer channel.
If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is
performed through the core network. If ENodeBAlgoSwitch.RimOnEcoSwitch is set to
ON(On), the RIM procedure is performed through the eCoordinator. The two RIM
procedures select information exchange modes in the same way.
shows the procedure of information exchange mode selection for the RIM
Figure 4-2
procedure.
• The preceding figure is described as follows: The RIM procedure between
EUTRAN and GERAN is controlled by the GERAN_RIM_SWITCH option of the
ENodeBAlgoSwitch.RimSwitch parameter.
If this option is selected, the eNodeB uses the RIM procedure in Multiple Report
mode to obtain the system information of external GERAN cells.
• If external GERAN cells do not support the Multiple Report mode, they do not
notify the eNodeB of any system information change after the initial request.
Figure 4-2 Information exchange mode selection for the RIM procedure
4.9 CSFB to GERAN
The combined EPS/IMSI attach procedure for CSFB to GERAN is the same as that for
CSFB to UTRAN. For details, see 3.11.1 Combined EPS/IMSI Attach Procedure.
During CSFB based on PS handover, the UE is transferred from the E-UTRAN to the
GERAN by performing a PS handover. It then initiates a CS service in the GERAN. If
the GERAN or UE does not support dual transfer mode (DTM, in which CS and PS
services run simultaneously), the ongoing PS services of the UE are suspended before a
CS service is set up.
Call procedure
shows the procedure for CSFB to GERAN based on PS handover for mobile-
Figure 4-3
originated calls.
Figure 4-3 CSFB to GERAN based on PS handover for mobile-originated calls
The procedure is described as follows:

1. The UE sends the MME a NAS message Extended service request to initiate a CS
service.
2. The MME instructs the eNodeB to initiate a CSFB procedure. If the MME supports
the LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform blind handover based on the UE
capabilities, parameters settings, and algorithm policies.
4. The eNodeB initiates the preparation phase for a PS handover. If the preparation is
successful, the eNodeB instructs the UE to perform a handover. If the GERAN or
UE does not support DTM, the ongoing PS services of the UE are suspended, and
the SGSN update bearers with the S-GW/P-GW.
NOTE:
5. After the handover, the UE may initiate a CS call establishment procedure with an
LAU or combined RAU/LAU procedure in the GERAN.
6. The follow-up procedures are performed for the PS handover. These procedures
include data forwarding, path switching, and RAU, which are performed together
with step 5.
steps in the procedure for CSFB to GERAN based on PS handover for mobile-originated
calls.
4.9.3 CSFB Based on CCO/NACC
During CSFB based on CCO/NACC, the eNodeB receives a CS Fallback Indicator from
the MME, and then it sends a Mobility From EUTRA Command message to the UE over
the Uu interface. The message contains information about the operating frequency, ID,
and system information of a target GERAN cell. The UE searches for a target cell based
on the information it received, and then it performs initial access to the cell to initiate a
CS service. It then initiates a CS service in the GERAN.
Call procedure
shows the procedure for CSFB to GERAN based on CCO/NACC for mobile-
Figure 4-4
originated calls.
Figure 4-4 CSFB to GERAN based on CCO/NACC for mobile-originated calls
CS service.
LAI to the eNodeB.
eNodeB.
4. The eNodeB sends a Mobility From EUTRA Command message over the Uu
interface to indicate the operating frequency and ID of the target GERAN cell. If
the source cell has the system information of the target cell, the system information
is also carried in the message.
NOTE:
5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in

the target cell.
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE
are suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
8. The eNodeB initiates an S1-based UE context release procedure.
steps in the procedure for CSFB to GERAN based on CCO/NACC for mobile-originated
calls.
4.9.4 CSFB Based on Redirection
During CSFB based on redirection, the eNodeB receives a CS Fallback Indicator, and
then it sends an RRC Connection Release message to release the UE. The message
contains information about a target GERAN frequency, reducing the time for the UE to
search for a target network. After selecting the GERAN, the UE acquires the system
information of a GERAN cell. Then, the UE performs initial access to the cell to initiate a
CS service. For the GERAN, the UE is an initially accessing user.
CSFB Procedure for Mobile-Originated Calls
shows the procedure for CSFB to GERAN based on redirection for mobile-
Figure 4-5
originated calls.
Figure 4-5 CSFB to GERAN based on redirection for mobile-originated calls
The procedure is described as follows:

1. The UE sends the MME a NAS message Extended service request to initiate a CS
service.
LAI to the eNodeB.
3. The eNodeB determines whether to perform blind handover based on the UE
perform a redirection. The message contains information about a target GERAN
frequency. Then, the eNodeB initiates an S1 UE context release procedure.
NOTE:
in the target cell.
6. If the GERAN or UE does not support DTM, the ongoing PS services of the UE are
suspended.
domain to the MME over the SGs interface. Then, the MME or eNodeB initiates a paging
procedure for the UE. The paging procedure is similar to that for UTRAN described in
3.11.2 CSFB Based on PS Handover. The subsequent steps are the same as the steps in the
procedure for CSFB to GERAN based on redirection for mobile-originated calls.
4.9.5 Flash CSFB
During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then
it sends an RRC Connection Release message to release the UE. The message contains
information about a target UTRAN frequency, as well as one or more physical cell
identities and their associated system information. In this way, the UE can quickly access
the target UTRAN without the need to perform the procedure for acquiring system
information of the target UTRAN cell. Then, the UE can directly initiate a CS service in
the UTRAN cell. It then initiates a CS service in the GERAN.
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved
must support 3GPP Release 9 or later.
Call procedure
shows the procedure for CSFB to GERAN based on flash redirection for
Figure 4-6
mobile-originated calls.
Figure 4-6 CSFB to GERAN based on flash redirection for mobile-originated calls
CS service.
LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind redirection based on the UE
perform a redirection. The message contains information about a target GERAN
carrier frequency group, as well as one or more physical cell identities and their
associated system information. Then, the eNodeB initiates an S1 UE context
release procedure.
NOTE:
Decision and 4.7 Handover Execution. The system information of the target cell is acquired during
the RIM procedure.
5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in

the target cell.
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE
are suspended.
domain to the MME over the SGs interface. Then, the MME or eNodeB initiates a paging
procedure for the UE. The paging procedure is similar to that for UTRAN described in
3.11.2 CSFB Based on PS Handover. The subsequent steps are the same as the steps in the
procedure for CSFB to GERAN based on CCO/NACC for mobile-originated calls.
4.9.6 Ultra-Flash CSFB to GERAN
Ultra-Flash CSFB to GERAN is a Huawei-proprietary procedure. To enable this feature,

the MSC, MME, and eNodeB must all be provided by Huawei and support this feature.
Resources are prepared in advance on the GERAN using the SRVCC, and authentication
and encryption procedures are excluded to reduce delays. The following figures show
Ultra-Flash CSFB to GERAN of mobile-originated calls and mobile-terminated calls,
respectively.
Figure 4-7 Ultra-flash CSFB to GERAN for mobile-originated calls
Figure 4-8 Ultra-flash CSFB to GERAN for mobile-terminated calls
Steps 1 to 3a: The UE initiates voice services (mobile-originated calls and mobile-
terminated calls) on the E-UTRAN. The eNodeB triggers SRVCC to GERAN. The MME
and MSC guarantees the proper procedure through special processing.
Step 3b: The BSC receives an SRVCC request and prepares CS resources.
Step 4: The eNodeB receives the handover command transferred over the core network
and sends it to the UE.
Step 5: The UE is transferred to the GERAN.
Steps 6 to 9: The UE establishes voice services on the GERAN. Signaling is carried on
the TCH, which accelerates the transfer and reduces delays.
As shown in the preceding figures, Ultra-Flash CSFB to GERAN excludes the following
procedures:
• Authentication procedure
The UE has been authenticated in the LTE system before CSFB to GERAN.
• Ciphering procedure
The UE has performed ciphering as instructed during SRVCC. Therefore, the
encryption procedure is not required after the UE is transferred to the GERAN.
• IMEI query procedure
The MME has sent the IMEI to the MSC during the preparation for SRVCC. There,
the procedure is not required in the GERAN after SRVCC.
• CS resource setup procedure
The GSM system has prepared CS resources during SRVCC and therefore the UE
does not need to reestablish the CS resource after SRVCC. There, the procedure is
not required in the GERAN after SRVCC.
When the UE completes voice services in the GERAN after the Ultra-Flash CSFB to
GERAN, you can enable the Fast Return to LTE feature on the GERAN side so that the
UE quickly returns to the E-UTRAN. After the UE completes voice services in the
GERAN, the UE carries the LTE frequency information in a Channel Release message
and selects a proper LTE cell to camp on based on the frequency information to
accelerate the return to the E-UTRAN.
When IratMeasCfgTransSwitch is set to ON, the eNodeB filters LTE frequencies
supported by the UE based on the UE capability to obtain a frequency set. During the
SRVCC, the eNodeB sends a Handover Required message containing the frequency set
to the BSC of the target cell and provides reference for the UE to accelerate the return to
the E-UTRAN after the UE completes voice services on the GERAN.
4.9.7 CSFB for SMS
SMS services are unknown to the eNodeB because SMS messages are encapsulated in
NAS messages. During interworking with the GERAN, SMS messages are exchanged
between the MME and the MSC over the SGs interface. Because a UE does not require
fallback to the GERAN to perform an SMS service, the SMS over SGs function can be
used in a place covered only by the E-UTRAN.
As the SMS service is transparent to the eNodeB, the procedure is not described in this
document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
The CSFB procedure for an emergency call is the same as the CSFB procedure for a
normal mobile-originated voice service. The UE sends an RRC Connection Request
message over the Uu interface or the MME sends an Initial Context Setup Request or UE
Context Modification Request message, which contains an IE to inform the eNodeB of
the service type. Emergency calls take precedence over other services in the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the
cells in the handover restriction list when selecting the target cell.
If redirection is used for CSFB for emergency calls, the Channel Request message that
the UE sends when accessing the GERAN contains the indication of a CS emergency
call.
The GERAN will treat this call as a common CS emergency call. For details about
admission and preemption of emergency calls, see Emergency Call.
4.9.9 CSFB for LCS
After a UE initiates an LCS request, the MME performs an attach or combined

TAU/LAU procedure to inform the UE of the LCS capability of the EPS. If the EPS does
not support LCS, the UE falls back to the GERAN to initiate LCS under the control of the
EPS. The CSFB procedure is the same as the procedure for CSFB to GERAN for mobile-
originated calls.
If the GERAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the
MSC sends an LCS indicator to the MME over the SGs interface. Then, the MME
instructs the eNodeB to perform CSFB for the UE. The CSFB procedure is the same as
the procedure for CSFB to GERAN for mobile-terminated calls. The UE performs the
LCS service after the fallback to the GERAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272
V10.0.0 and LCS.
5 Related Features
5.1 Features Related to LOFD-001033 CS Fallback to UTRAN
Prerequisite Features
This feature requires the optional feature LOFD-001019 PS Inter-RAT Mobility between
E-UTRAN and UTRAN.
Mutually Exclusive Features
None
Impacted Features
When a UE initiates a CSFB request, the eNodeB cannot determine whether the target
inter-RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN, according to
3GPP Release 9. Therefore, it is not recommended that CSFB to GERAN/UTRAN be
enabled together with CSFB to CDMA2000 1xRTT. In addition, it is not recommended
that this feature be enabled together with either of the following features:
• LOFD-001035 CS Fallback to CDMA2000 1xRTT
• LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT
If both CSFB to UTRAN and CSFB to CDMA2000 are enabled, the eNodeB attempts
CSFB to UTRAN first. If the attempt fails, the eNodeB attempts CSFB to CDMA2000.
5.2 Features Related to LOFD-001052 Flash CS Fallback to UTRAN
This feature requires LOFD-001033 CS Fallback to UTRAN.
When a UE initiates a CSFB request, the eNodeB cannot determine, according to 3GPP
Release 9 specifications, whether the target inter-RAT network is a CDMA2000 1xRTT
network or a GERAN/UTRAN. Therefore, CSFB to GERAN/UTRAN cannot be enabled
together with CSFB to CDMA2000 1xRTT. This feature does not work with the
following features:
Impacted Features
None
5.3 Features Related to LOFD-070202 Ultra-Flash CSFB to UTRAN
This feature depends on the optional feature LOFD-001033 CS Fallback to UTRAN.
None
Impacted Features
None
5.4 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN
This feature requires LOFD-001033 CS Fallback to UTRAN.

following features:
Impacted Features
None
5.5 Features Related to LOFD-001088 CS Fallback Steering to UTRAN
This feature requires LOFD-001033 CS Fallback to UTRAN and LOFD-001078 E-

UTRAN to UTRAN CS/PS Steering.
following features:
Impacted Features
This feature affects LOFD-001089 CS Fallback Steering to GERAN. In overlapping

coverage of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to
UTRAN and LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously,
achieve CSFB steering to different RATs.
5.6 Features Related to LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
Required Features
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and

UTRAN or LOFD-001033 CS Fallback to UTRAN.
None
Affected Features
None
5.7 Features Related to LOFD-001034 CS Fallback to GERAN
This feature requires LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and

GERAN.
None
Impacted Features
When a UE initiates a CSFB request, the eNodeB cannot determine whether the target
inter-RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN, according to
3GPP Release 9. Therefore, it is not recommended that CSFB to GERAN/UTRAN be
enabled together with CSFB to CDMA2000 1xRTT. In addition, it is not recommended
that this feature be enabled together with either of the following features:
If both CSFB to GERAN and CSFB to CDMA2000 are enabled, the eNodeB attempts
CSFB to GERAN first. If the attempt fails, the eNodeB attempts CSFB to CDMA2000.
5.8 Features Related to LOFD-001053 Flash CS Fallback to GERAN
This feature requires LOFD-001034 CS Fallback to GERAN.
following features:
Impacted Features
None
5.9 Feature Related to LOFD-081283 Ultra-Flash CSFB to GERAN
This feature requires the optional feature LOFD-001034 CS Fallback to GERAN.
None
Impacted Features
None
5.10 Features Related to LOFD-001069 CS Fallback with LAI to GERAN
following features:
Impacted Features
None
5.11 Features Related to LOFD-001089 CS Fallback Steering to GERAN
following features:
Impacted Features
This feature affects LOFD-001088 CS Fallback Steering to UTRAN. In overlapping
coverage of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to
UTRAN and LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously,
achieve CSFB steering to different RATs.
6 Network Impact
System Capacity
In essence, CSFB provides CS service access for E-UTRAN UEs. Considering that the
number of UEs that request CS services within an area is relatively stable and is not
affected by EPS deployment, CSFB has no impact on the total number of UEs that
request CS services within a network.
Load-based CSFB to UTRAN prevents PS handover preparation failure caused by
UTRAN cell congestion, because the eNodeB selects a target cell based on the UTRAN
cell load status. This increases system capacity.
CSFB mechanisms affect signaling overhead as follows:
• If redirection is used as the CSFB mechanism, no extra signaling message is
required for the UTRAN because each CSFB procedure is equivalent to the
initiation of a new CS service. The EPS does not need to interact with the target
network, and the corresponding signaling overhead is negligible.
• If PS handover is used as the CSFB mechanism, extra signaling messages are
required from each NE for the request, preparation, and execution of each handover.
However, from the perspective of traffic statistics, the number of UEs that initiate
CS services per second per cell during peak hours is far below cell capacity.
Therefore, signaling overhead caused by PS handovers is low.
Network Performance
Load-based CSFB to UTRAN prevents PS handover preparation failure caused by

UTRAN cell congestion, because the eNodeB selects a target cell based on the UTRAN
cell load status. This increase the CSFB delay.
CSFB affects the access success rate as follows:
• CSFB affects the access success rate as follows: If redirection is used as the CSFB
mechanism, each CSFB procedure is equivalent to the initiation of a new CS
service. Therefore, the access success rate for CSFB UEs is theoretically the same as
that for normal CS UEs in the UTRAN.
• If PS handover is used as the CSFB mechanism, the access success rate for CSFB
UEs depends on the success rate of handovers to the target RAT. Handover-
triggered CS service access has a higher requirement for signal quality compared
with normal CS service access. Therefore, the access success rate for CSFB UEs is a
little lower than that for normal CS UEs in the UTRAN.
System Capacity
Extra signaling messages are required only during eNodeB deployment.
• Afterward, signaling overhead is negligible because of infrequent system
information updates.
Network Performance
Flash CSFB to UTRAN decreases the CSFB delay by up to 1.28s because UEs obtain
information about the target UTRAN cell for redirection before RRC connections to the
LTE network are released.
Flash CSFB affects the access success rate as follows:
• Each flash CSFB procedure is equivalent to the initiation of a new CS service.
Therefore, the access success rate for CSFB UEs is theoretically the same as that for
normal CS UEs in the UTRAN.
• The RRC connection setup success rate may decrease slightly for the UTRAN. The
uplink interference information contained in SIB7 in the UTRAN updates
frequently. The RNC cannot update the uplink interference information in the
system information sent to the LTE network based on SIB7 in the UTRAN.
Therefore, the uplink interference information contained in SIB7 in the LTE
network is a default value (–105 dBm). If the actual uplink interference in the
UTRAN is greater than –105 dBm, the transmit power on UEs' physical random
access channel (PRACH) increases and the RRC connection setup success rate may
decrease.
System Capacity
Non impact.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to UTRAN by 1
second, improving user experience.
System Capacity
No impact.
Network Performance
CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has
attached. This prevents CSFB failure or long delay caused by incorrect target RAT
selection and increases the CSFB success rate.
System Capacity
No impact.
Network Performance
Using this feature, an operator that owns inter-RAT networks can specify the target RAT
and frequency for CSFB based on the network plan and network load balancing
requirements and thereby improve network operating efficiency.
If the frequency with the highest priority is inappropriately configured, for example, if
the highest-priority frequency has coverage holes, a UE may fail to measure this
frequency and therefore the CSFB delay increases.
This feature may conflict with the service-based directed retry decision (DRD) algorithm
used for UTRAN, thereby affecting user experience. For example, if a CS service is
initiated for a UE that is performing PS services, the eNodeB may select a High Speed
Packet Access (HSPA) frequency used in UTRAN for CSFB based on configured
policies. However, if the UE requests CS bearer establishment first after the fallback, the
UTRAN may transfer the UE to an R99 frequency.
System Capacity
No impact.
Network Performance
E-UTRAN to UTRAN CS/PS Steering enables an eNodeB to include only UTRAN

frequencies with a high CS service priority in measurement configurations. This prevents
redundant measurements, reduces the measurement time, and decreases end-to-end CSFB
delay.
If the CS service priorities of UTRAN frequencies configured on the eNodeB are
consistent with those configured at the UTRAN side, E-UTRAN to UTRAN CS/PS
Steering prevents further intra-UTRAN handovers for service steering.
System Capacity
CSFB mechanisms affect signaling overhead as follows:
• CSFB mechanisms affect signaling overhead as follows: If redirection or CCO
without NACC is used as the CSFB mechanism, no extra signaling message is
required for the GERAN because each CSFB procedure is equivalent to the
initiation of a new CS service. The EPS does not need to interact with the target
network. Therefore, signaling overhead is negligible.
• If CCO with NACC is used as the CSFB mechanism, extra signaling messages are
required only during eNodeB deployment.
• Afterward, signaling overhead is negligible because of infrequent system
information updates. If PS handover is used as the CSFB mechanism, extra signaling
messages are required from each NE for the request, preparation, and execution of
each handover. However, from the perspective of traffic statistics, the number of
UEs that initiate CS services per second per cell during peak hours is far below cell
capacity. Therefore, signaling overhead caused by PS handovers is low.
Network Performance
CSFB affects the access success rate as follows:

• If redirection or CCO/NACC is used as the CSFB mechanism, each CSFB
procedure is equivalent to the initiation of a new CS service. Therefore, the access
success rate for CSFB UEs is theoretically the same as that for normal CS UEs in
the GERAN.
• If PS handover is used as the CSFB mechanism, the access success rate for CSFB
UEs depends on the success rate of handovers to the target RAT. Handover-
triggered CS service access has a higher requirement for signal quality compared
with normal CS service access. Therefore, the access success rate for CSFB UEs is a
little lower than that for normal UEs in the GERAN.
System Capacity
CSFB mechanisms affect signaling overhead as follows: Flash CSFB affects signaling
overhead as follows: Extra signaling messages are required only during eNodeB
deployment. Afterward, signaling overhead is negligible because of infrequent system
information updates.
Network Performance
If flash CSFB is used as the CSFB mechanism, each CSFB procedure is equivalent to the
initiation of a new CS service. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the GERAN.
Flash CSFB to GERAN decreases the CSFB delay by up to 2s because UEs obtain
information about the target GERAN cell for redirection before RRC connections to the
LTE network are released.
System Capacity
When DRX measurements are used, there is a higher probability that the UE enters the
DTX sleep state, affecting the scheduling by decreasing the cell throughput.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to GERAN by 2
seconds, improving user experience.
System Capacity
No impact.
Network Performance
CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has
attached. This prevents CSFB failure or long delay caused by incorrect target RAT
selection and increases the CSFB success rate.
System Capacity
No impact.
Network Performance
Using this feature, an operator that owns inter-RAT networks can specify the target RAT
and frequency for CSFB based on the network plan and network load balancing
requirements and thereby improve network operating efficiency.
If the frequency with the highest priority is inappropriately configured, for example, if
the highest-priority frequency has coverage holes, a UE may fail to measure this
frequency and therefore the CSFB delay increases.
7 Engineering Guidelines
This section provides engineering guidelines for LOFD-001033 CS Fallback to UTRAN.

7.1.1 When to Use CS Fallback to UTRAN
Use LOFD-001033 CS Fallback to UTRAN in the initial phase of LTE network

deployment when both of the following conditions are met:
• The operator owns a mature UTRAN network.
• The LTE network does not provide VoIP services, or UEs in the LTE network do
not support VoIP services.
For policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT
Mobility Management in Connected Mode. If UTRAN and E-UTRAN cells cover the same area,
or the UTRAN cell provides better coverage than the E-UTRAN cell, use CSFB based on
blind handover to decrease the CSFB delay.
1. Collect the operating frequencies, coverage areas, and configurations of the E-

UTRAN and UTRAN cells. Information about coverage areas includes engineering
parameters of sites (such as latitude and longitude), TX power of cell reference
signals (RSs), and neighbor relationship configurations.
2. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and
core networks, and ensure that they all support CSFB. Table 7-1 describes the
requirements of CSFB to UTRAN for the core networks.
3. Collect the following information about the UEs that support UMTS and LTE on
the live network:
• Supported frequency bands
• Whether the UEs support redirection from E-UTRAN to UTRAN
• Whether the UEs support PS handover from E-UTRAN to UTRAN
• Whether the UEs support UTRAN measurements
This information is used to configure neighboring UTRAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Inter-
RAT Mobility Management in Connected Mode.
4. Collect information about the RNC, MME, and SGSN to check whether they all
support RIM procedures.
Table 7-1 Requirements of CSFB to UTRAN for core networks
NE Requirement
MME • Supports: SGs interface to the MSC

• LAI selection based on the TAI of the
serving cell
• MSC-initiated paging
• PLMN selection and reselection
• Combined EPS/IMSI attach, combined
EPS/IMSI detach, and combined TAU/LAU
• CS signaling message routing
• SMS over SGs
MSC • Supports: Combined EPS/IMSI attach

• SMS over SGs
• Paging message forwarding over the SGs
interface
SGSN Does not activate ISR during the combined

RAU/LAU procedure initiated by the UE.
7.1.3 Requirements
Operating Environment
For CSFB to UTRAN, the eNodeB must collaborate with core-network equipment. If the
core-network equipment is provided by Huawei, the version must be SAE1.2 or later. If
the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB to
UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-2.
Table 7-2 License control item for CSFB to UTRAN
Feature ID Feature Model License NE Sales Unit
Name Control Item
LOFD-001033 CSFB to LT1S00CFBU00 CS Fallback eNodeB per RRC

UTRAN to Connected
UTRAN(FDD) User
7.1.4 Precautions
None
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 not required): parameter values planned and set by the
operator
• Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
• User-defined: parameter values set by users
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships
with UTRAN cells. This section provides only the information about managed objects
(MOs) related to neighboring UTRAN cells. For more information about how to collect
data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected Mode
Feature Parameter Description. Collect data for the parameters in the following MOs:
1. UtranNFreq: used to configure neighboring UTRAN frequencies

2. UtranExternalCell: used to configure external UTRAN cells. The
UtranExternalCell.Rac parameter must be set.
3. UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external UTRAN cell. This MO is required only if the NodeB that provides the
external UTRAN cell works in RAN sharing with common carriers mode and
multiple operators share the external UTRAN cell.
4. The following table describes the parameters that must be set in the UtranNCell
MO to configure the neighboring relationship with a UTRAN cell. If a neighboring
UTRAN cell supports blind handovers according to the network plan, the blind-
handover priority of the cell must be specified by the UtranNCell.BlindHoPriority
parameter.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch
MO to set the eNodeB-level handover mode and handover algorithm switches for CSFB
to UTRAN.
Parameter Parameter ID Data Source Setting Notes

Name
Handover ENodeBAlgoSwitch.HoModeSwitch Network Set this parameter based on the

Mode plan network plan.
switch (negotiation To activate PS handovers, select the
not UtranPsHoSwitch(UtranPsHoSwitch)
required) check box. If this check box is not
selected, redirection will be used for
CSFB to UTRAN.
Handover ENodeBAlgoSwitch.HoAlgoSwitch Network To activate CSFB to UTRAN, select

Algo plan the
switch (negotiation UtranCsfbSwitch(UtranCsfbSwitch)
not check box.
required) To activate load-based CSFB, select
the CSFBLoadInfoSwitch check box.
and CellHoParaCfg MOs to set eNodeB- and cell-level blind handovers.

Name
Handover ENodeBAlgoSwitch.HoModeSwitch Network To activate blind handovers,

Mode plan select the
switch (negotiation BlindHoSwitch(BlindHoSwitch)
not check box under the parameter.
required) If the
BlindHoSwitch(BlindHoSwitch)
check box is deselected, blind
handovers for all cells under the
eNodeB are invalid.
Handover CellHoParaCfg.HoModeSwitch Network To activate blind handovers for a

Mode plan cell under the eNodeB, select the
required) If the
Name

handovers for the cell are invalid.
The following table describes the parameters that must be set in the
CSFallBackBlindHoCfg MO to set the blind-handover priorities of different RATs for
CSFB.

Name
CN CSFallBackBlindHoCfg.CnOperatorId Network Set this parameter

Operator plan based on the
ID (negotiation network plan. This
not parameter
required) identifies the
operator whose
RAT blind-
handover priorities
are to be set.
Highest CSFallBackBlindHoCfg.InterRatHighestPri Network Set this parameter

priority plan based on the
InterRat (negotiation network plan. This
not parameter is set to
required) UTRAN by default
and specifies the
highest-priority
RAT to be
considered in blind
handovers for
CSFB. For CSFB to
UTRAN, retain the
default value.
Second CSFallBackBlindHoCfg.InterRatSecondPri Network Set this parameter

required) GERAN by default
and specifies the
second-highest-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
Name
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatLowestPri
parameters.
Lowest CSFallBackBlindHoCfg.InterRatLowestPri Network Set this parameter

required) CDMA2000 by
default and
specifies the low-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.
UTRAN CSFallBackBlindHoCfg.UtranLcsCap Network Set this parameter

LCS plan based on the
capability (negotiation network plan. This
not parameter specifies
required) the LCS capability
of the UTRAN.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch
MO to activate load-based CSFB.

Name
Handover ENodeBAlgoSwitch.HoAlgoSwitch Network To activate load-based CSFB, select the

Algo plan CSFBLoadInfoSwitch(CSFBLoadInfoSwitch
switch (negotiation check box.
not
required)
The following table describes the parameter that must be set in the GlobalProcSwitch
MO to set load-based CSFB to UTRAN.

Name
Choose GlobalProcSwitch.UtranLoadTransChan Network Set this parameter to

UTRAN plan BASED_ON_RIM to
Cell (negotiation enable UTRAN cell
Load Info not load information
Trans required) acquisition through
Channel RIM if the RNC,
MME, and SGSN
support RIM.
The following table describes the parameter that must be set in the CSFallBackHo MO
to set the CSFB protection timer.

Name
CSFB CSFallBackHo.CsfbProtectionTimer Network Set this parameter based

Protection plan on the network plan. The
Timer (negotiation default value 4 applies to
not a GSM+UMTS+LTE
required) network. The value 2 is
recommended for a
UMTS+LTE network. If
this parameter is set too
large, the CSFB delay
increases in abnormal
CSFB scenarios. If this
parameter is set too
small, normal
measurement or
handover procedures
may be interrupted.
The following table describes the parameter that must be set in the InterRatHoComm
MO to set the maximum number of neighboring UTRAN cells whose system information
is sent to UEs for emergency redirections.

Name
Max Utran InterRatHoComm.UtranCellNumForEmcRedirect Network The default

cell num plan value is 0,
Name
in CSFB (negotiation indicating that

EMC not no system
redirection required) information of
any
neighboring
UTRAN cells
is sent to UEs
for
emergency
redirections.
Operators
can set this
parameter to
0 through 16
based on the
network plan.
After the
CSFB
protection
timer expires,
the eNodeB
performs an
emergency
redirection. If
the signal
quality of the
serving cell is
poor and this
parameter is
set to a large
value, the
eNodeB may
fail to send
the system
information of
neighboring
UTRAN cells
to UEs.
The following table describes the parameter that must be set in the
CSFallBackPolicyCfg MO to specify the CSFB policy.
Name
CSFB CSFallBackPolicyCfg.CsfbHoPolicyCfg Network Set this parameter

handover plan based on the
policy (negotiation network plan. The
Configuration not default values are
required) REDIRECTION,
CCO_HO, and
PS_HO. You are
advised to set this
parameter based
on the UE
capabilities and
network
capabilities.
NOTE:
If none of the three
options is selected and
measurement-based
mobility is enabled,
the eNodeB does not
perform CSFB for a
UE until the CSFB
protection timer
expires. Then the
eNodeB performs a
blind redirection for
the UE. If blind
handover is enabled,
the eNodeB directly
performs a blind
redirection for the
UE.
CCO_HO applies
only to CSFB to
GERAN.
CSFALLBACKBLINDHOCFG MO to set the round-robin switch when multiple
frequencies are of the same priority for CSFB-based blind redirections.

Name
CSFB to UtranCsfbBlindRedirRrSw Network Set this parameter based on

UTRAN plan the network plan. The option is
Name
Blind (negotiation cleared by default. When the

Redirection not UE needs to perform a blind
RR Switch required) redirection and multiple
frequencies are of the same
priority, the option can be
selected to ensure that the UE
accesses each frequency
equally. In addition, you are
advised to plan neighboring
cells on the frequencies and
neighboring frequencies, and
neighboring cell priorities
before selecting the option.
The following table describes the parameter that must be set in the ENBRSVDPARA
MO to set the random procedure selection optimization for CSFB.

Name
Reserved ENBRSVDPARA.RsvdSwPara1 Network Select the

Switch plan RsvdSwPara1_bit23 option
Parameter (negotiation when CSFB selects a target
1 not frequency or cell to enter the
required) random selection procedure.
This ensures that each
frequency or cell is selected
evenly.
Enter the values of the parameters listed in Table 7-3 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:
• The managed objects (MOs) in Table 7-3 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 MOs in Table 7-3 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.
When configuring neighboring cells, you are advised to use the radio data planning file.
For details about how to fill in and export the radio data planning file, see section
"Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
Table 7-3 Parameters for CSFB to UTRAN
MO Sheet in the Summary Parameter Remarks

Data File Group
UtranNFreq UtranNFreq See 7.1.5.1 The RNP template

Data sheet is
Preparation. recommended.
UtranExternalCell UtranExternalCell See 7.1.5.1 The RNP template

Data sheet is
UtranExternalCellPlmn UtranExternalCellPlmn See 7.1.5.1 The RNP template

Data sheet is
UtranNCell UtranNCell See 7.1.5.1 The RNP template

Data sheet is
ENodeBAlgoSwitch User-defined sheet. See 7.1.5.1 This parameter

ENodeBAlgoSwitch is Data must be customized
recommended. Preparation. on a list-type sheet
of the template.
CSFallBackBlindHoCfg User-defined sheet. See 7.1.5.1 This parameter

CSFallBackBlindHoCfg Data must be customized
is recommended. Preparation. on a list-type sheet
of the template.
CellHoParaCfg User-defined sheet. See 7.1.5.1 This parameter

CellHoParaCfg is Data must be customized
of the template.
CSFallBackHo User-defined sheet. See 7.1.5.1 This parameter

CSFallBackHo is Data must be customized
of the template.
Data File Group
InterRatHoComm User-defined sheet. See 7.1.5.1 None

InterRatHoComm is Data
recommended. Preparation.
Batch Activated
This feature can be batch activated using the CME. For detailed operations, see the
following section in the CME product documentation or online help: Managing the CME
> CME Guidelines > Enhanced Feature Management > Feature Operation and
Maintenance.
Batch Reconfiguration
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.
1. Customize a summary data file with the MOs and parameters listed in section
"Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs."
For online help, press F1 when a CME window is active, and select Managing the
CME > CME Guidelines > LTE Application Management > eNodeB Related
Operations > Customizing a Summary Data File for Batch eNodeB
Configuration.
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 according to the setting
notes provided in section "Data Preparation" 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. After data verification is complete, 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. For detailed operations, see Managing the CME >
CME Guidelines > Script File Management > Exporting Incremental Scripts
from a Planned Data Area in the CME online help.
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
Basic scenario 1: CSFB to UTRAN using blind redirection

CSFB to UTRAN using blind redirection works regardless of whether neighboring
UTRAN cells are configured.
• If you want to configure a neighboring UTRAN cell, you must configure the
UtranNFreq and UtranNCell MOs. For details about parameter settings, see Inter-
• If you do not want to configure a neighboring UTRAN cell, you must configure the
UtranRanShare or UtranExternalCell MO. For details about parameter settings,
see Inter-RAT Mobility Management in Connected Mode.
1. Run the MOD ENODEBALGOSWITCH command with the
UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch
parameter selected.
2. Run the following eNodeB- and cell-level commands to enable blind handovers for
CSFB to UTRAN:
a. Run the MOD ENODEBALGOSWITCH command with the
BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch
parameter selected.
b. Run the MOD CELLHOPARACFG command with the BlindHoSwitch
option of the Handover Mode switch parameter selected.
3. Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and
PS_HO options of the CSFB handover policy Configuration parameter
deselected and the REDIRECTION option of the same parameter selected.
4. (Optional) If you require setting UTRAN as having the highest priority for CSFB,
run the MOD CSFALLBACKBLINDHOCFG command with the Highest
priority InterRat parameter set to UTRAN and the Second priority InterRat
parameter set to GERAN.
5. (Optional) If a neighboring UTRAN cell is configured, run the MOD
UTRANNCELL command with the Blind handover priority parameter set to the
highest priority (32).
6. (Optional) If no neighboring UTRAN cell is configured, run the MOD
UTRANNFREQ command with the Frequency Priority for Connected Mode
parameter set to the highest priority (8).
7. (Optional) Run the MOD CSFALLBACKBLINDHOCFG command to turn on
the CSFB to UTRAN blind redirection RR switch.
Basic scenario 2: CSFB to UTRAN using blind handover
1. Add neighboring UTRAN frequencies and neighbor relationships with UTRAN
cells. For details about parameter settings, see Inter-RAT Mobility Management in
Connected Mode.
parameter selected.
3. Run the following eNodeB- and cell-level commands to enable blind handovers for
CSFB to UTRAN:
parameter selected.
b. Run the MOD CELLHOPARACFG command with the BlindHoSwitch
option of the Handover Mode switch parameter selected.
4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option
of the CSFB handover policy Configuration parameter selected.
5. Run the MOD UTRANNCELL command with the Blind handover priority
parameter set to 32.
Basic scenario 3: CSFB to UTRAN using measurement-based redirection
Connected Mode.

parameter selected.
3. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of
the Handover Mode switch parameter deselected for the cells to be measured.
PS_HO options of the CSFB handover policy Configuration parameter
deselected and the REDIRECTION option of the same parameter selected.
Basic scenario 4: CSFB to UTRAN using measurement-based handovers
Connected Mode.

UtranCsfbSwitch(UtranCsfbSwitch) check box selected under the Handover
Algo switch and the UtranPsHoSwitch(UtranPsHoSwitch) check box selected
under the Handover Mode switch parameter.
4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option
of the CSFB handover policy Configuration parameter selected.
Enhanced scenario: Load-based CSFB to UTRAN To activate load-based CSFB to
UTRAN, run the following commands after the commands in a basic scenario are
executed:
CSFBLoadInfoSwitch(CSFBLoadInfoSwitch) check box selected under the
Handover Algo switch parameter.
2. Run the MOD GLOBALPROCSWITCH command with the Choose UTRAN
Cell Load Info Trans Channel parameter set to BASED_ON_RIM.
MML Command Examples
Basic scenario 1: CSFB to UTRAN using blind redirection (configured with neighboring
UTRAN cells)
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1,
HoModeSwitch=BlindHoSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-
0;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,
InterRatSecondPri=GERAN;
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1,
CellId=123, BlindHoPriority=32;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;
Basic scenario 1: CSFB to UTRAN using blind redirection (configured with no

neighboring UTRAN cell)
0;
MOD UTRANNFEQ: LocalCellId=0, UtranDlArfcn=9700, ConnFreqPriority=8;
MOD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=9700, Mcc="460",
Mnc="20";
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;
Basic scenario 2: CSFB to UTRAN using blind handovers

HoModeSwitch=UtranPsHoSwitch-1&BlindHoSwitch-1;
1;
CellId=123, BlindHoPriority=32;
Basic scenario 3: CSFB to UTRAN using measurement-based redirection

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1;
0;
MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms,
CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13,
CsfbProtectionTimer=4;
CellId=123;
Basic scenario 4: CSFB to UTRAN using measurement-based handovers

1;
MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms,
CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13,
CsfbProtectionTimer=4;
CellId=123;
Enhanced scenario: Load-based CSFB to UTRAN To activate load-based CSFB to

UTRAN, run the following commands after the commands in a basic scenario are
executed:
MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-1;
MOD GLOBALPROCSWITCH: UtranLoadTransChan=BASED_ON_RIM;
Signaling Observation
The activation observation procedure for CSFB to UTRAN is as follows:

1. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that the UE
falls back to a UTRAN cell and completes the call.
2. Enable a UE to camp on an E-UTRAN cell and receive a voice call so that the UE
The activation observation procedure for load-based CSFB to UTRAN is as follows:
Two UTRAN cells A and B report MRs and are under overload control and in the normal
state, respectively. The RSCP of cell A is larger than that of cell B.
Enable a UE to perform a PS-handover-based CSFB when both cell A and cell B
provides services correctly.
1. If the RSCP of cell B meets the handover requirements, the eNodeB transfers the
UE to cell B.
2. If cell B is blocked and the RSCP of cell A meets the handover requirements, the
eNodeB transfers the UE to cell A and the UE can access the network through
preemption or queuing.
and Figure 7-3 show sample procedures for CSFB to UTRAN for a mobile-
Figure 7-2
originated call and CSFB to UTRAN for a mobile-terminated call, respectively. In the
examples, the UE was in idle mode before the call and is forced to fall back to the
UTRAN using a redirection.
NOTE:
The same UE is shown in the left and right sides of the figure. This applies to all figures in the rest of this
document. The messages on the UTRAN side are only for reference.
Figure 7-2 Redirection-based CSFB to UTRAN for a mobile-originated call
Figure 7-3 Redirection-based CSFB to UTRAN for a mobile-terminated call
If the UE capability is not included in the Initial Context Setup Request (Initial Context
Setup Req in the figures) message, the eNodeB initiates a UE capability transfer
procedure immediately after receiving this message from the MME. If the UE capability
is included in the Initial Context Setup Request message, the eNodeB initiates a UE
capability transfer procedure after sending an Initial Context Setup Response (Initial
Context Setup Rsp in the figures) message to the MME.
If measurement-based redirection is used for CSFB to UTRAN, the eNodeB delivers the
B1-related measurement configuration.
If blind redirection is used for CSFB to UTRAN, the eNodeB does not deliver the B1-
related measurement configuration but sends an RRC Connection Release (RRC Conn
Rel in the figures) message to the UE. As shown in the red and green boxes in Figure 7-4,
in the RRC Connection Release message, the cause value is "other" and the target RAT is
UTRAN. For an emergency call, the cause value is "CSFBhighpriority."
Figure 7-4 The RRC Connection Release message during CSFB to UTRAN
If PS handover is used for CSFB to UTRAN, the eNodeB initiates a PS handover

procedure after receiving a measurement report from the UE, instead of sending an RRC
Connection Release message to the UE. Figure 7-5 shows the PS handover procedure. As
shown in the red and green boxes in Figure 7-6, in the handover command sent over the air
interface, the cs-FallbackIndicator IE is TRUE and the target RAT is UTRAN.
Figure 7-5 PS handover procedure
Figure 7-6 The MobilityFromEUTRAN message during CSFB to UTRAN
MML Command Observation
The activation observation procedure for load-based CSFB to UTRAN is as follows: Run
the DSP UTRANRIMLOADINFO command to query neighboring UTRAN cell load
status to check whether load-based CSFB has been activated.
If the neighboring UTRAN cell load status is displayed, load-based CSFB has been
activated.
Counter Observation
lists the performance counters for observing functions related to CSFB to

Table 7-4
UTRAN.
Table 7-4 Performance counters for observing CSFB to UTRAN
Function Counter ID Counter Name Description
CSFB to 1526728323 L.CSFB.E2W Number of times CSFB to UTRAN

UTRAN is performed
CSFB to 1526728709 L.CSFB.E2W.Emergency Number of times CSFB to UTRAN

UTRAN is triggered for emergency calls
triggered for
emergency
calls
RIM during 1526728949 L.RIM.Load.E2W.Req Number of load information

load-based requests sent from an eNodeB to a
CSFB to UMTS network
UTRAN
1526728950 L.RIM.Load.E2W.Resp Number of load information
responses sent from a UMTS
network to an eNodeB
1526728951 L.RIM.Load.E2W.Update Number of load information

updates sent from a UMTS
network to an eNodeB
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 Batch Reconfiguration. In the procedure, modify
parameters according to Table 7-5.
Table 7-5 Parameters for deactivating CSFB to UTRAN
MO Sheet in the Summary Parameter Setting Notes

Data File Group
ENodeBAlgoSwitch User-defined sheet. HoAlgoSwitch To deactivate CSFB to

ENodeBAlgoSwitch UTRAN, set
is recommended. UtranCsfbSwitch under the
Data File Group
HoAlgoSwitch parameter to
0.
To deactivate only load-based
CSFB to UTRAN, set
CSFBLoadInfoSwitch under
the HoAlgoSwitch parameter
to 0.
To deactivate only adaptive-
blind-handover-based CSFB,
Set
CsfbAdaptiveBlindHoSwitch
to 0.
Using the CME to Perform Single Configuration
On the CME, set parameters according to Table 7-5. For detailed instructions, see 7.1.5.4
Using the CME to Perform Single Configuration for feature activation.
Using MML Commands
• Deactivating CSFB to UTRAN

Run the MOD ENODEBALGOSWITCH command with the
UtranCsfbSwitch(UtranCsfbSwitch) check box cleared under the Handover Algo
switch parameter.
• Deactivating only load-based CSFB to UTRAN
CSFBLoadInfoSwitch(CSFBLoadInfoSwitch) check box cleared under the
• Deactivating adaptive-blind-handover-based CSFB
Run the MOD ENODEBALGOSWITCH command to with the
CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlindHoSwitch) option of the
Handover Algo switch parameter cleared.
• Deactivating CSFB to UTRAN

• Deactivating only load-based CSFB to UTRAN

MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-0;
• Deactivating adaptive-blind-handover-based CSFB
MOD ENODEBALGOSWITCH: HoAlgoSwitch=CsfbAdaptiveBlindHoSwitch-0;
CSFB is an end end-to to-end service. The performance counters on the LTE side can
only indicate the success rate of the CSFB procedure on the LTE side, and. they cannot
indicate the success rate of the CSFB procedure on the target side. Therefore, the
performance counters on the LTE side cannot directly show user experience of the CSFB
procedure. It is recommended that you perform drive tests and use the performance
counters on the UE side to indicate the actual user experience of the CSFB procedure.
Related counters are listed in Table 7-6.
Table 7-6 Counters related to the execution of CSFB by the eNodeB
Counter ID Counter Name Description
1526728321 L.CSFB.PrepAtt Number of CSFB indicators received by

the eNodeB
1526728322 L.CSFB.PrepSucc Number of successful CSFB responses

from the eNodeB
Table 7-7 lists the counter related to CSFB to UTRAN.

Table 7-7 Counter related to CSFB to UTRAN
1526728323 L.CSFB.E2W Number of procedures for CSFB to

WCDMA network
lists the counters that indicate whether CSFB is performed through redirection or
Table 7-8
through handover.
Table 7-8 Counters related to CSFB through redirection or handover
1526728497 L.RRCRedirection.E2W.CSFB Number of CSFB-based redirections

from E-UTRANs to WCDMA network
1526728504 L.IRATHO.E2W.CSFB.PrepAttOut Number of CSFB-based inter-RAT

handover preparation attempts from
E-UTRAN to WCDMA network
After the CSFB protection timer expires, the eNodeB may perform a blind redirection to
enter the protection procedure. Table 7-9 lists the counter related to the number of times
that the eNodeB enters the protection procedure for CSFB. A larger value of this counter
indicates a longer average UE access delay during CSFB.
Table 7-9 Counter related to the number of times that the eNodeB enters the protection procedure
for CSFB
1526729515 L.RRCRedirection.E2W.CSFB.TimeOut Number of CSFB-based blind

redirections from E-UTRAN to
WCDMA network caused by CSFB
protection timer expiration
Table 7-10 lists the counters related to CSFB for emergency calls.
Table 7-10 Counters related to CSFB for emergency calls
1526729510 L.IRATHO.E2W.CSFB.ExecAttOut.Emergency Number of CSFB-based

handover execution attempts
to WCDMA network triggered
for emergency calls
1526729511 L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency Number of successful CSFB-

based handover executions
to WCDMA network triggered
for emergency calls
The formula for calculating the CSFB handover success rate for emergency calls is as
follows: CSFB handover success rate for emergency calls =
L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency/L.IRATHO.E2W.CSFB.ExecAttOut.Emergency
CSFB end-to-end delay includes the processing time at the LTE side and that at the side
after fallback. Processing at any side may affect the CSFB end-to-end delay and user
experience.
• If GSM devices are provided by Huawei, for details about processing at the GSM
side, see Interoperability Between GSM and LTE Feature Parameter Description.
• If UMTS devices are provided by Huawei, for details about processing at the UMTS
side, see Interoperability Between UMTS and LTE Feature Parameter Description.
Blind Handover for CSFB
Compared with measurement-based handovers, blind handovers reduce access delays but
affect handover success rates.
The following table describes the parameters in the CSFallBackBlindHoCfg MO used to
set the blind-handover priorities of different RATs for CSFB.
Name

not parameter
required) specifies the ID of
the operator
whose RAT blind-
handover
priorities are to be
set.

not parameter is set
required) to UTRAN by
default and
specifies the high-
priority RAT to be
considered in
blind handovers
for CSFB.

required) to GERAN by
default and
specifies the
medium-priority
RAT to be
considered in
blind handovers
for CSFB. Ensure
that this
parameter is set
to a different
value from the
InterRatHighestPri
and
InterRatLowestPri
parameters.
Name

required) to CDMA2000 by
default and
specifies the low-
priority RAT to be
considered in
blind handovers
for CSFB. Ensure
that this
parameter is set
to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.

Name

not check box. A blind handover to
required) an inter-RAT cell can be
performed only if a blind-
handover priority is specified for
the inter-RAT cell. Compared
with measurement-based
handovers, blind handovers
reduce access delays but affect
handover success rates.
To deactivate blind handovers,
clear the
check box.
Name

required) If the
Measurement-based Handovers for CSFB
An appropriate event B1 threshold for CSFB ensures that inter-RAT handovers are
triggered in a timely fashion. A high threshold results in a low probability of triggering
event B1, thereby affecting user experience. A low threshold results in a high probability
of triggering event B1, but causes a high probability of incorrect handover decisions and
a low handover success rate. Tune this parameter based on site conditions.
Event B1 for CSFB has a time-to-trigger parameter. This parameter lowers the
probability of incorrect handover decisions and raises the handover success rate.
However, if the value of this parameter is too large, CSFB delay is extended, affecting
user experience. Tune this parameter based on site conditions.
Appropriate settings of the threshold and time-to-trigger for event B1 raise the handover
success rate and lower the call drop rate. The related parameters are as follows:
Related parameters are in the CSFallBackHo MO.

Name
Local cell CSFallBackHo.LocalCellId Network Set this

ID plan parameter based
(negotiation on the network
not plan.
required)
CSFB CSFallBackHo.CsfbHoUtranTimeToTrig Network Set this

Utran plan parameter based
EventB1 (negotiation on the network
Time To not plan. This
Trig required) parameter
specifies the
time-to-trigger for
event B1 in CSFB
Name
to UTRAN. When
CSFB to UTRAN
is required, set
this parameter,
which is used by
UEs as one of the
conditions for
triggering event
B1. When a UE
detects that the
signal quality in at
least one UTRAN
cell meets the
entering
condition, it does
not immediately
send a
measurement
report to the
eNodeB. Instead,
the UE sends a
measurement
report only when
the signal quality
has been meeting
the entering
condition
throughout a
period defined by
this parameter.
This parameter
helps decrease
the number of
occasionally
triggered event
reports, the
average number
of handovers,
and the number
of incorrect
handovers,
preventing
unnecessary
handovers.
Name
CSFB CSFallBackHo.CsfbHoUtranB1ThdRscp Network Set this

UTRAN plan parameter based
EventB1 (negotiation on the network
RSCP not plan. This
Trigger required) parameter
Threshold specifies the
RSCP threshold
for event B1 in
CSFB to UTRAN.
When CSFB to
UTRAN is
required, set this
parameter, which
is used by UEs
as one of the
conditions for
triggering event
B1. This
parameter
specifies the
minimum
required RSCP of
the signal quality
provided by a
UTRAN cell when
a CSFB
procedure can be
initiated toward
this cell. Event B1
is triggered when
the RSCP
measured by the
UE is higher than
the value of this
parameter and all
other conditions
are also met.
CSFB CSFallBackHo.CsfbHoUtranB1ThdEcn0 Network Indicates the

UTRAN plan Ec/No threshold
EventB1 (negotiation for event B1,
ECN0 not which is used in
Trigger required) CS fallback to
Threshold UTRAN. When
CSFB to UTRAN
Name
is required, set
this parameter,
which is used by
UEs as one of the
conditions for
triggering event
B1. This
parameter
specifies the
minimum
required Ec/No of
the signal quality
provided by a
UTRAN cell when
a CSFB
procedure can be
initiated toward
this cell. Event B1
is triggered when
the Ec/No
measured by the
UE is higher than
the value of this
parameter and all
other conditions
are also met. Set
this parameter to
a large value for
a cell with a large
signal fading
variance in order
to reduce the
probability of
unnecessary
handovers. Set
this parameter to
a small value for
a cell with a small
signal fading
variance in order
to ensure timely
handovers.
7.2 RIM Procedure from E-UTRAN to UTRAN
7.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN

It is recommended that the RIM procedure be performed through the Huawei-proprietary
eCoordinator if the following two conditions are met: 1. Both the eNodeB and the
RNC/BSC are provided by Huawei and are connected to the same eCoordinator. 2. The
core network that the eNodeB and the RNC/BSC are connected to does not support the
RIM procedure or is not enabled with the RIM procedure. To perform the RIM procedure
through the eCoordinator, set ENodeBAlgoSwitch.RimOnEcoSwitch to ON(On).
In other conditions, it is recommended that the RIM procedure be performed through the
core network. In this case, set ENodeBAlgoSwitch.RimOnEcoSwitch to OFF(Off).
Check whether the RNC, MME, and SGSN support the RIM procedure, and whether an
eCoordinator has been deployed.
7.2.3 Requirements
If the RIM procedure is performed through the core network, the core-network equipment
must support this feature:
• If the core-network equipment is provided by Huawei, the version must be SAE1.2
or later.
• If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support the
RIM procedure from E-UTRAN to UTRAN.
If the RIM procedure is performed through the eCoordinator, the RNC/BSC, eNodeB,
and eCoordinator must all be provided by Huawei and with the switch for supporting the
RIM procedure through eCoordinator turned on.
To facilitate connection setup for RIM message exchange, you must enable RIM in the
UTRAN before you enable it in the E-UTRAN.
License
Table 7-11 License control item for CSFB to UTRAN

Name Control Item

UTRAN to Connected
UTRAN(FDD) User
7.2.4 Precautions
None
operator
Required Data
The required data is the same as that for LOFD-001033 CS Fallback to UTRAN. For
details, see 7.1.5.1 Data Preparation.
UtranExternalCell: used to configure external UTRAN cells. The
MO to configure the RIM procedure.

Name
Support RIM ENodeBAlgoSwitch.RimOnEcoSwitch Network If

by plan ENodeBAlgoSwitch.RimOnEcoSwitch
eCoordinator (negotiation is set to OFF(Off), the RIM
Switch not procedure is performed through the
required) core network.
If
ENodeBAlgoSwitch.RimOnEcoSwitch
is set to ON(On), the RIM procedure
is performed through the
eCoordinator.
and save the file.
• Some MOs in Table 7-12 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.
Table 7-12 Parameters for the RIM procedure
MO Sheet in the Summary Parameter Group Remarks

Data File
ENodeBAlgoSwitch User-defined sheet. See 7.2.5.1 Data Preparation. None

ENodeBAlgoSwitch
is recommended.
multiple eNodeBs in a single procedure. The procedure is as follows:
Configuration.
import the summary data file into the CME, and then start the data verification.
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
• Performing the RIM procedure through the core network

Run the MOD ENODEBALGOSWITCH command with the Support RIM by
eCoordinator Switch parameter set to OFF(Off).
• Performing the RIM procedure through the eCoordinator
eCoordinator Switch parameter set to ON(On).

MOD ENODEBALGOSWITCH: RimOnEcoSwitch=OFF;

MOD ENODEBALGOSWITCH: RimOnEcoSwitch=ON;
Counter Observation
No matter whether the RIM procedure is performed through the core network or the
eCoordinator, performance counters listed in Table 7-13 can be used to observe whether the
RIM procedure has taken effect.
Table 7-13 Counters related to the RIM procedure between E-UTRAN and UTRAN
1526728949 L.RIM.Load.E2W.Req Number of load information requests from

an eNodeB to WCDMA network
1526728950 L.RIM.Load.E2W.Resp Number of times the eNodeB receives load

information responses from WCDMA
network
1526728951 L.RIM.Load.E2W.Update Number of times the eNodeB receives load

information updates from WCDMA network
Signaling Tracing Result Observation
If the RIM procedure is performed through the core network, trace signaling messages as
follows:
1. Start an S1 interface tracing task on the eNodeB LMT.
Check whether the eNB DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMATION-REQUEST IE is sent over the S1 interface.
If the message is sent, you can infer that the eNodeB has sent the RIM request
successfully.
2. Start an Iu interface tracing task on the RNC LMT.
If after receiving the DIRECT INFORMATION TRANSFER message containing
the RAN-INFORMATION-REQUEST IE, the RNC sends the DIRECT
INFORMATION TRANSFER message containing the RAN-INFORMAION IE to
the SGSN, you can infer that the RNC can response to the RIM request normally.
3. Change the state of the UTRAN cell.
If the RNC sends the DIRECT INFORMATION TRANSFER message containing
the RAN-INFORMATION IE over the Iu interface, you can infer that the RNC can
notify the eNodeB with the cell state change through the RIM procedure.
If the RIM procedure is performed through the eCoordinator, trace signaling messages as
follows:
1. Start an Se interface tracing task on the eNodeB LMT.
Check whether the ENB DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMAION-REQUEST IE is sent over the Se interface. If
the message is sent, you can infer that the eNodeB has sent the RIM request
successfully.
2. Start an Sr interface tracing task on the RNC LMT.
If after receiving the ECO DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMAION-REQUEST IE, the RNC sends the RNC
DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMAION IE to the eCoordinator, you can infer that the RNC can response to
the RIM request normally.
3. Change the state of the UTRAN cell.
If the RNC sends the RNC DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMATION IE over the Sr interface, you can infer that
the RNC can notify the eNodeB with the cell state change through the RIM
procedure.
7.2.7 Deactivation
to that for feature activation described in 7.2.5.3 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to the table listed in the
scenario of E-UTRAN to UTRAN CS/PS steering.
MO Sheet in the Summary Parameter Group Setting Notes

Data File
ENodeBAlgoSwitch User-defined sheet. RimOnEcoSwitch Set this parameter to

(eNodeB-level ENodeBAlgoSwitch OFF(Off).
switch) is recommended.
Using MML Commands



The performance monitoring procedure for this feature is the same as that for CSFB to
UTRAN. For details, see 7.1.8 Performance Monitoring.
The parameter optimization procedure for this feature is the same as that for CSFB to
UTRAN. For details, see 7.1.9 Parameter Optimization.
This section provides engineering guidelines for LOFD-001052 Flash CS Fallback to

UTRAN.
7.3.1 When to Use Flash CS Fallback to UTRAN
When LOFD-001033 CS Fallback to UTRAN has been enabled, use LOFD-001052 Flash
CS Fallback to UTRAN if all the following conditions are met: The E-UTRAN and
UTRAN support the RIM with SIB procedure. 3GPP Release 9 UEs are used on the live
network. The core networks support the RIM procedure. The eCo has been deployed. For
policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT Mobility
Management in Connected Mode. If UTRAN and E-UTRAN cells cover the same area, or the
UTRAN cell provides better coverage than the E-UTRAN cell, use CSFB based on blind
handover to decrease the CSFB delay.
1. Collect information about whether LOFD-001033 CS Fallback to UTRAN has

been activated.
UTRAN and UTRAN cells. Information about coverage areas includes engineering
core networks, and ensure that they all support CSFB and the RIM procedure. Table
7-15 describes the requirements of flash CSFB to UTRAN for the core networks.
For details about the deployment guide on the UTRAN, see Interoperability
Between UMTS and LTE Feature Parameter Description.
the live network:
• Whether the UEs comply with 3GPP Release 9 specifications
Table 7-15 Requirements of flash CSFB to UTRAN for core networks
NE Requirement
MME Supports CSFB and RIM procedures in compliance with 3GPP

Release 9
SGSN Supports CSFB and RIM procedures in compliance with 3GPP

Release 9
7.3.3 Requirements
For flash CSFB to UTRAN, the eNodeB must collaborate with core-network equipment.
If the core-network equipment is provided by Huawei, the version must be PS9.1 or later.
If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support flash CSFB
to UTRAN.
License
Table 7-16 License control item for Flash CS Fallback to UTRAN

Name Control Item

UTRAN to Connected
UTRAN(FDD) User
LOFD-001052 Flash LT1S0FCFBU00 Flash CS eNodeB per RRC

CSFB to Fallback to Connected
UTRAN UTRAN User
NOTE:
If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN.
7.3.4 Precautions
None
operator
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships
with UTRAN cells. This section provides only the information about MOs related to
neighboring UTRAN cells and key parameters in these MOs. For more information about
how to collect data for the parameters in these MOs, see Inter-RAT Mobility Management in
Connected Mode Feature Parameter Description.
1. The following table describes the parameters that must be set in the UtranNFreq
MO to configure a neighboring UTRAN frequency.
2. UtranExternalCell: used to configure external UTRAN cells. The
3. UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external UTRAN cell. This MO is required only if the BTS that provides the
external GERAN cell works in RAN sharing with common carriers mode and
multiple operators share the external GERAN cell.
4. The following table describes the parameters that must be set in the UtranNCell
MO to configure the neighboring relationship with a UTRAN cell. If a neighboring
UTRAN cell supports blind handovers according to the network plan, the blind-
handover priority of the cell must be specified by the UtranNCell.BlindHoPriority
parameter.
MO to set the handover mode and handover algorithm switches for flash CSFB to
UTRAN.

Name
Handover ENodeBAlgoSwitch.HoModeSwitch Network Set this parameter based on the network plan
Mode plan
switch (negotiation
not
required)
Handover ENodeBAlgoSwitch.HoAlgoSwitch Network To activate flash CSFB to UTRAN, select the

Algo plan UtranCsfbSwitch(UtranCsfbSwitch) and
switch (negotiation UtranFlashCsfbSwitch(UtranFlashCsfbSwi
not check boxes.
required)
RIM ENodeBAlgoSwitch.RimSwitch Network UTRAN_RIM_SWITCH(UTRAN RIM Switch)

switch plan under this parameter specifies whether to ena
(negotiation or disable the RIM procedure that requests
not event-driven multiple reports from UTRAN cel
required)
Name
If this switch is turned on, the eNodeB can se

RAN-INFORMATION-REQUEST/Multiple Rep
protocol data units (PDUs) to UTRAN cells to
request event-driven multiple reports.
If this switch is turned off, the eNodeB cannot
send RAN-INFORMATION-REQUEST/Multipl
Report PDUs to UTRAN cells.
If this switch is turned off and
UtranFlashCsfbSwitch(UtranFlashCsfbSwi
under ENodeBAlgoSwitch.HoAlgoSwitch is
turned on, the eNodeB sends RAN-
INFORMATION-REQUEST/Single Report PD
to UTRAN cells to request single reports.
If the UTRAN cells support RAN-INFORMATI
REQUEST/Multiple Report PDUs, you are
advised to select the
UTRAN_RIM_SWITCH(UTRAN RIM Switch)
option.

Name

required) If the
eNodeB are invalid.

required) If the
The following table describes the parameter that must be set in the S1Interface MO to
set the compliance protocol release of the MME.
Parameter Name Parameter ID Data Source Setting Notes
MME Release S1INTERFACE.MmeRelease Network plan To activate RIM

(negotiation not procedures in
required) Multiple Report
mode, set the
parameter to
Release_R9(Release
9).
CSFB.

Name

not parameter
operator whose
RAT blind-
handover priorities
are to be set.

and specifies the
highest-priority
RAT to be
considered in blind
handovers for
CSFB. For CSFB to
UTRAN, retain the
default value.

parameter is set to
Name
not GERAN by default

required) and specifies the
second-highest-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatLowestPri
parameters.

default and
specifies the low-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.

of the UTRAN.
is sent to UEs for flash redirections.
Name
Max Utran InterRatHoComm.CellInfoMaxUtranCellNum Network Set this

cell num plan parameter based
in (negotiation on the network
redirection not plan. The default
required) value is 8. If this
parameter is set
too small, the
flash CSFB
success rate
decreases
because UEs
may not receive
valid neighboring
cell system
information. If this
parameter is set
too large, the size
of an RRC
connection
release message
increases and
CSFB may fail.
and save the file.
set the parameters.
Table 7-17 Parameters for flash CSFB to UTRAN

Data File
UtranNFreq UtranNFreq See 7.3.5.1 Data The RNP

Preparation. template sheet
is
recommended.
UtranExternalCell UtranExternalCell See 7.3.5.1 Data The RNP

is
recommended.
UtranExternalCellPlmn UtranExternalCellPlmn See 7.3.5.1 Data The RNP

is
recommended.
UtranNCell UtranNCell See 7.3.5.1 Data The RNP

is
recommended.
S1Interface S1Interface See 7.3.5.1 Data This

Preparation. parameter
must be
customized on
a list-type
sheet of the
template.
ENodeBAlgoSwitch User-defined sheet. See 7.3.5.1 Data This

ENodeBAlgoSwitch is Preparation. parameter
recommended. must be
customized on
a list-type
sheet of the
template.
CSFallBackBlindHoCfg User-defined sheet. See 7.3.5.1 Data This

CSFallBackBlindHoCfg Preparation. parameter
is recommended. must be
customized on
a list-type
sheet of the
template.
Data File
InterRatHoComm User-defined sheet. See 7.3.5.1 Data This

InterRatHoComm is Preparation. parameter
customized on
a list-type
sheet of the
template.
CSFallBackHo User-defined sheet. See 7.3.5.1 Data This

CSFallBackHo is Preparation. parameter
customized on
a list-type
sheet of the
template.
(Optional) User-defined sheet. See 7.3.5.1 Data This

GlobalProcSwitch GlobalProcSwitch is Preparation. parameter
customized on
a list-type
sheet of the
template.
CellHoParaCfg User-defined sheet. See 7.3.5.1 Data This

CellHoParaCfg is Preparation. parameter
customized on
a list-type
sheet of the
template.
Batch Activated
Maintenance.
Configuration.
Using MML Commands
The prerequisite is that CSFB to UTRAN has been activated.

1. Run the MOD GLOBALPROCSWITCH command to set the RIM Coding
Policy parameter.
If the peer device is a Huawei device, go to 2 directly.
If the peer device is not a Huawei device, you need to modify the RIM Coding
Policy feature. Run the MOD GLOBALPROCSWITCH command to set the
RIM Coding Policy parameter to StandardCoding.
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check box selected under the
Handover Algo switch parameter and with the
UTRAN_RIM_SWITCH(UTRAN RIM Switch) check box selected under the
RIM switch parameter.
3. Run the MOD S1INTERFACE command with the MME Release parameter set
to Release_R9(Release 9).
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranFlashCsfbSwitch-

1,RimSwitch=UTRAN_RIM_SWITCH-1;
MOD S1INTERFACE:
S1InterfaceId=2,S1CpBearerId=1,CnOperatorId=0,MmeRelease=Release_R9;
Enable a UE to camp on an E-UTRAN cell and make a voice call. If the call continues
and the RRC Connection Release message traced on the Uu interface carries the
information about neighboring UTRAN cells, flash CSFB to UTRAN has been activated.
The signaling procedure for flash CSFB to UTRAN is similar to that for redirection-
based CSFB to UTRAN described in 7.1.6 Activation Observation. The difference is that the
RRC Connection Release message carries the information about neighboring UTRAN
cells.
Check the status of the RIM procedure towards neighboring UTRAN cells by running the
DSP UTRANRIMINFO command. If the ID of a neighboring UTRAN cell is displayed
in the command output, the eNodeB has obtained the system information of this
neighboring UTRAN cell.
Counter Observation
Table 7-18 lists the performance counters for observing functions related to flash CSFB to
UTRAN.
Table 7-18 Performance counters for observing flash CSFB to UTRAN
Flash CSFB to 1526728705 L.FlashCSFB.E2W Number of times flash

UTRAN CSFB to UTRAN is
performed
1526728946 L.RIM.SI.E2W.Req Number of system

information requests sent
RIM during from an eNodeB to a UMTS

flash CSFB to network
UTRAN
1526728947 L.RIM.SI.E2W.Resp Number of system
information responses sent
from a UMTS network to an
eNodeB
1526728948 L.RIM.SI.E2W.Update Number of system

information updates sent
from a UMTS network to an
eNodeB
7.3.7 Deactivation
Existing eNodeBs. In the procedure, modify parameters according to Table 7-19.
Table 7-19 Parameters for deactivating flash CSFB to UTRAN

Data File Group
ENodeBAlgoSwitch User-defined sheet HoAlgoSwitch Set

UtranFlashCsfbSwitch
under the HoAlgoSwitch
parameter to 0.
Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands

UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check box cleared under the

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranFlashCsfbSwitch-0;
7.4.1 When to Use Ultra-Flash CSFB
When LOFD-001033 CS Fallback to UTRAN has been enabled, this feature is

recommended in scenarios where the eNodeB, RNC, MME, and MSC are provided by
Huawei, and a proportion of of UEs in the live network support SRVCC from E-UTRAN
to UTRAN.
Before deploying this feature, collect the following information:

• LOFD-001033 CS Fallback to UTRAN has been activated.
• The eNodeB, RNC, MME, and MSC in the network are provided by Huawei and
they all support this feature.
• A proportion of UEs in the live network support SRVCC from E-UTRAN to
UTRAN.
7.4.3 Requirements
This feature is a Huawei-proprietary feature and requires that the UTRAN, eNodeB,
RNC, MME, and MSC are provided by Huawei and support this feature. This feature is
used with MME11.0 and MSC11.0.
License
Table 7-20 License information for ultra-flash CSFB to UTRAN
Feature ID Feature Name Model License NE Sales Unit
Control
Item
LOFD- Ultra-Flash LT1SUFCSFB00 Ultra-Flash eNodeB per RRC

070202 CSFB to CSFB to Connected
UTRAN UTRAN User
7.4.4 Precautions
This feature is a Huawei-proprietary feature and is not supported by devices provided by

other vendors. In addition, this feature must first be activated on the RNC, MME, and
MSC, and then be activated on the eNodeB. This is because this feature is triggered by
the eNodeB and this avoids CSFB failures.
operator
Required Data
MO to set the handover mode and handover algorithm switches for ultra-flash CSFB to
UTRAN.

Name
Handover ENodeBAlgoSwitch.HoAlgoSwitch Network Select the

Algo plan UtranUltraFlashCsfbSwitch(UtranUltraF
switch (negotiation check box.
Name
not
required)
(Optional) ENodeBAlgoSwitch.MultiOpCtrlSwitch Network If some RNCs do not support ultra-flash CS

Multi- plan turn on the mobility switch for correspondin
Operator (negotiation
Control required)
Switch
If some RNCs do not support ultra-flash CSFB to UTRAN, the ultra-flash CSFB
supporting capability of the UTRAN must be set in the UtranNetworkCapCfg MO.

Name
Network UtranNetworkCapCfg.NetworkCapCfg Network Clear the

Capability plan UltraFlashCsfbCapCfg
Configuration (negotiation check box for RNCs
required) that do not support
ultra-flash CSFB to
UTRAN.
GLOBALPROCSWITCH MO to turn on the UE compatibility switch when UEs do not
support Ultra-Flash CSFB, resulting in UE compatibility problems.

Name
Ue GlobalProcSwitch.UeCompatSwitch Network Select the

Compatibility plan UltraFlashCsfbComOptSw
Switch (negotiation option of the parameter
required) when UEs on the network
do not support ultra-flash
CSFB.
When the MME provided by
Huawei allows IMEI
whitelist configurations for
ultra-flash CSFB and the
option is selected, the
eNodeB performs ultra-
flash CSFB on UEs in the
IMEI whitelist. Therefore,
Name
delete the UEs that do not

support ultra-flash CSFB
from the whitelist before
selecting the option.
Otherwise, keep the option
unselected.
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
and save the file.
set the parameters.
Table 7-21 Parameters for ultra-flash CSFB to UTRAN

Data File Group
UtranNFreq UtranNFreq See 7.4.5.1 The RNP template

Data sheet is
UtranExternalCell UtranExternalCell See 7.4.5.1 The RNP template

Data sheet is
UtranExternalCellPlmn UtranExternalCellPlmn See 7.4.5.1 The RNP template

Data sheet is
Data File Group
UtranNCell UtranNCell See 7.4.5.1 The RNP template

Data sheet is
ENodeBAlgoSwitch User-defined sheet. See 7.4.5.1 This parameter must

ENodeBAlgoSwitch is Data be customized on a
recommended. Preparation. list-type sheet of the
template.
CSFallBackBlindHoCfg User-defined sheet. See 7.4.5.1 This parameter must

CSFallBackBlindHoCfg Data be customized on a
is recommended. Preparation. list-type sheet of the
template.
CSFallBackHo User-defined sheet. See 7.4.5.1 This parameter must

CSFallBackHo is Data be customized on a
template.
InterRatHoComm User-defined sheet. See 7.4.5.1 This parameter must

InterRatHoComm is Data be customized on a
template.
GeranNfreqGroup User-defined sheet. See 7.4.5.1 This parameter must

GeranNfreqGroup is Data be customized on a
template.
GlobalProcSwitch User-defined sheet. See 7.4.5.1 This parameter must

GlobalProcSwitch is Data be customized on a
template.
Configuration.
Using MML Commands
• Ultra-Flash CSFB to UTRAN

1. For details about parameter settings, see Inter-RAT Mobility Management in Connected
Mode.

UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box selected
under the Handover Algo switch parameter.
• (Optional) If some RNCs do not support ultra-flash CSFB to UTRAN, perform the
following operations:
UtranSepOpMobilitySwitch(UtranSepOpMobilitySwitch) check box selected
under the Multi-Operator Control Switch parameter.
2. Run the MOD UTRANNETWORKCAPCFG command with the
UltraFlashCsfbCapCfg(UltraFlashCsfbCapCfg) check box cleared under the
Network Capability Configuration parameter for RNCs that do not support ultra-
flash CSFB to UTRAN.
• (Optional) Perform the following operation if UE compatibility risks exist after
ultra-flash CSFB is activated.
1. Run the MOD GLOBALPROCSWITCH command with the
UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw) option of the UE
Compatibility Switch parameter selected.
• Ultra-Flash CSFB to UTRAN

MOD ENODEBALGOSWITCH: HoAlgoSwitch= UtranUltraFlashCsfbSwitch-1;
• (Optional) If some RNCs do not support ultra-flash CSFB to UTRAN, perform the
following operations:
• MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch= UtranSepOpMobilitySwitch-
1;
MOD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0,
NetworkCapCfg= SrvccBasedCsfbCapCfg-0;

ultra-flash CSFB is activated.
MO GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;
The activation observation procedure for ultra-flash CSFB to UTRAN is as follows:

2. Enable a UE to camp on an E-UTRAN cell and receive a voice call so that the UE
shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-
Figure 7-10
originated call.
shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-
Figure 7-11
terminated call.
The UEs in the left and right sides of the figure are the same UE. The messages on the
UTRAN side are only for reference. The UE was in idle mode before the call.
If the UE capability is not included in the Initial Context Setup Request (Initial Context
Setup Req in the figures) message, the eNodeB initiates a UE capability transfer
procedure immediately after receiving this message from the MME. If the UE capability
is included in the Initial Context Setup Request message, the eNodeB initiates a UE
capability transfer procedure after sending an Initial Context Setup Response (Initial
Context Setup Rsp in the figures) message to the MME.
Figure 7-10 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-originated call
Figure 7-11 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-terminated call
Counter Observation
The counter listed in Table 7-22 can be viewed to check whether the feature has taken
effect.
Table 7-22 Counter related to ultra-flash CSFB to UTRAN
1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut Triggered by ultra-flash CSFB

Number of SRVCC-based
outgoing handover executions
from E-UTRAN to WCDMA
network for ultra-flash CSFB
7.4.7 Deactivation
Table 7-23 Parameter related to ultra-flash CSFB to UTRAN

Data File Group
ENodeBAlgoSwitch User-defined sheet. HoAlgoSwitch Clear the

(eNodeB-level ENodeBAlgoSwitch UtranUltraFlashCsfbSwitch(UtranUltraFlashC
switch) is recommended. check box.
Using MML Commands

UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box cleared under
the Handover Algo switch parameter.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranUltraFlashCsfbSwitch-0;

Table 7-24
1526730146 L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut Number of SRVCC-based

outgoing handover attempts from
for ultra-flash CSFB
1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut Number of SRVCC-based

outgoing handover executions
from E-UTRAN to WCDMA
network for ultra-flash CSFB
1526730148 L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut Number of successful SRVCC-

based outgoing handovers from
for ultra-flash CSFB to UTRAN
Ultra-flash CSFB to UTRAN success rate =

L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut/L.IRATHO.CSFB.SRVCC.E2W.PrepAtt
Out
This section provides engineering guidelines for LOFD-001068 CS Fallback with LAI to
UTRAN.
7.5.1 When to Use CS Fallback with LAI to UTRAN
Use LOFD-001068 CS Fallback with LAI to UTRAN when both of the following
conditions are met:LOFD-001033 CS Fallback to UTRAN has been enabled.The E-
UTRAN cell has neighboring UTRAN cells that belong to different PLMNs and supports
inter-PLMN handovers, or the E-UTRAN cell has neighboring UTRAN cells that have
different location area codes (LACs).
If both LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to
GERAN have been enabled, you are advised to enable both LOFD-001068 CS Fallback
with LAI to UTRAN and LOFD-001069 CS Fallback with LAI to GERAN.

been activated.
UTRAN and UTRAN cells.
core networks, and ensure that they all support CSFB and the MME supports LAI
delivery. Table 7-25 describes the requirements of CSFB with LAI to UTRAN for
the core networks.
the live network:
Table 7-25 Requirements of CSFB with LAI to UTRAN for core networks
NE Requirement
MME • Supports: SGs interface to the MSC

serving cell
• Combined EPS/IMSI attach, combined
EPS/IMSI detach, and combined TAU/LAU
• SMS over SGs
• LAI delivery
MSC • Supports: Combined EPS/IMSI attach

• SMS over SGs
• Paging message forwarding over the SGs
interface
SGSN Does not activate ISR during the combined

RAU/LAU procedure initiated by the UE.
7.5.3 Requirements
For CSFB with LAI to UTRAN, the eNodeB must collaborate with core-network
equipment. If the core-network equipment is provided by Huawei, the version must be
PS9.2 or later. If the core-network equipment is provided by another vendor, check with
the vendor whether the equipment supports this feature. The core network must support
CSFB with LAI to UTRAN.
License
Table 7-26 License information for CSFB with LAI to UTRAN
Feature Feature Name Model License NE Sales Unit

ID Control Item
LOFD- CS Fallback with LT1S0CSFLU00 CS Fallback eNodeB per RRC

001068 LAI to UTRAN with LAI to Connected
UTRAN User
7.5.4 Precautions
None
CSFB with LAI to UTRAN is automatically activated when two conditions are met: The
license for this feature has been purchased. CSFB to UTRAN has been activated.
Data preparation for activating CSFB with LAI to UTRAN is the same as that for
activating CSFB to UTRAN. For details, see 7.1.5.1 Data Preparation.
For details, see 7.1.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs .
For details, see 7.1.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs .
For details, see 7.1.5.4 Using the CME to Perform Single Configuration.
For details, see 7.1.5.5 Using MML Commands.

The activation observation procedure is as follows:

1. Configure two neighboring UTRAN cells with different LAIs for an E-UTRAN
cell, and enable the MME to include only one of the two LAIs in the instructions
that will be delivered to the eNodeB.
2. Ensure that the signal strengths of the two UTRAN cells both reach the threshold
for event B1. You can query the threshold by running the LST
INTERRATHOUTRANGROUP command.
falls back to the UTRAN cell with the specified LAI and completes the call.
4. Enable the UE to camp on the E-UTRAN cell and receive a voice call so that the
UE falls back to the UTRAN cell with the specified LAI and completes the call.
You can observe the signaling procedure for CSFB with LAI to UTRAN, which is
similar to that for CSFB to UTRAN described in 7.1.6 Activation Observation. The
difference is that the Initial Context Setup Request or UE Context Mod Request
message carries the LAI that the MME delivers to the eNodeB, as shown in the
following figure:
Figure 7-12 LAI signaling tracing
7.5.7 Deactivation
CSFB with LAI to UTRAN is automatically deactivated when its license or CSFB to
UTRAN is deactivated. For details about how to deactivate CSFB to UTRAN, see 7.1.7
Deactivation.
This section provides engineering guidelines for LOFD-001088 CS Fallback Steering to
UTRAN.
7.6.1 When to Use CS Fallback Steering to UTRAN
Use LOFD-001088 CS Fallback Steering to UTRAN to improve the network efficiency

when both of the following conditions are met:
• LOFD-001033 CS Fallback to UTRAN has been activated.
• An operator owns multiple UTRAN frequencies or the operator has different
handover policies for CS-only services and combined CS+PS services.
If the operator owns both UTRAN and GERAN, you can also activate LOFD-001089 CS
Fallback Steering to GERAN to improve the network efficiency.

been activated.
the live network:
3. Collect information about the frequencies and frequency policies of the UTRAN.
The frequency policies for UTRAN and E-UTRAN must be the same. For example,
if F1 is the preferred frequency for voice services on UTRAN, the same
configuration is recommended for E-UTRAN.
4. If LOFD-001089 CS Fallback Steering to GERAN is also to be activated, consider
the GERAN frequencies when making frequency policies.
7.6.3 Requirements
For CSFB steering to UTRAN, the eNodeB must collaborate with core-network
SAE1.2 or later. If the core-network equipment is provided by another vendor, check
with the vendor whether the equipment supports this feature. The core network must
support CSFB steering to UTRAN.
License
Table 7-27 License information for CSFB steering to UTRAN

ID Control Item
LOFD- CS Fallback LT1S0CFBSU00 CS Fallback eNodeB per RRC

001088 Steering to Steering to Connected
UTRAN UTRAN User
7.6.4 Precautions
None
operator
Required Data
MO to enable CSFB steering to UTRAN.

Name

Algo plan UtranCsfbSteeringSwitch(UtranCsfbSteerin
switch (negotiation check box under this parameter.
Name
not
required)
CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for
RRC_CONNECTED UEs.

Name

ID (negotiation network plan.
not
required)

and specifies the
highest-priority
RAT to be
considered in blind
handovers for
CSFB. For CSFB to
UTRAN, retain the
default value.

and specifies the
second-highest-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
Name
and
InterRatLowestPri
parameters.

default and
specifies the low-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.

of the UTRAN.
CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for RRC_IDLE
UEs.

Name
CSFB CSFallBackBlindHoCfg.IdleCsfbHighestPri Network Set this parameter

Highest plan based on the
priority (negotiation network plan. This
InterRat not parameter is set to
for Idle required) UTRAN by default
UE and specifies the
high-priority RAT to
be considered in
Name
CSFB for UEs in

idle mode. For
CSFB to UTRAN,
retain the default
value.
CSFB CSFallBackBlindHoCfg.IdleCsfbSecondPri Network Set this parameter

Second plan based on the
for Idle required) GERAN by default
second-highest-
priority RAT to be
considered in
CSFB for UEs in
idle mode. Ensure
that this parameter
is set to a different
value from the
InterRatHighestPri
and
InterRatLowestPri
parameters.
CSFB CSFallBackBlindHoCfg.IdleCsfbLowestPri Network Set this parameter

Lowest plan based on the
for Idle required) CDMA2000 by
UE default and
specifies the low-
priority RAT to be
considered in
CSFB for UEs in
idle mode. Ensure
that this parameter
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.
The following table describes the parameter that must be set in the UtranNFreq MO to
set the CS service priority of a neighboring UTRAN frequency considered for
RRC_IDLE UEs.
Name
CS UtranNFreq.CsPriority Network Set this parameter based on the

service plan network plan. If this parameter is set to
priority (negotiation Priority_0(Priority 0) for the UTRAN
not frequency, the eNodeB does not select
required) the frequency for SRVCC. The values
Priority_16(Priority 16) and
Priority_1(Priority 1) indicate the
highest and lowest SRVCC priority,
respectively. Set a high priority for a
UTRAN frequency with good coverage.
set the CS+PS combined service priority of a neighboring UTRAN frequency for
RRC_CONNECTED UEs.

Name
CS and UtranNFreq.CsPsMixedPriority Network Set this parameter based on

PS plan the network plan. If this
mixed (negotiation parameter is set to
priority not Priority_0(Priority 0) for the
required) UTRAN frequency, the eNodeB
does not select the frequency
for SRVCC. The values
Priority_16(Priority 16) and
Priority_1(Priority 1) indicate
the highest and lowest SRVCC
priority, respectively. Set a high
priority for a UTRAN frequency
with good coverage.
CSFallBackPolicyCfg MO to set the CSFB policy for RRC_CONNECTED UEs.

Name

CCO_HO, and
Name
PS_HO. You are

advised to set this
parameter based
on the UE
capabilities and
network
capabilities. For
details about how
to select a CSFB
handover policy,
see 3.9 Handover
Execution.
CSFallBackPolicyCfg MO to set the CSFB policy for RRC_IDLE UEs.

Name
CSFB CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg Network Set this

handover plan parameter
policy (negotiation based on the
Configuration not network plan.
for idle ue required) The default
values are
REDIRECTION,
CCO_HO, and
PS_HO. You
are advised to
set this
parameter
based on the
UE capabilities
and network
capabilities. For
details about
how to select a
CSFB handover
policy, see 3.9
Handover
Execution.
and save the file.
set the parameters.
Table 7-28 Parameters for CS fallback steering to UTRAN

Data File
ENodeBAlgoSwitch User-defined sheet. See 7.6.5.1 Data None

ENodeBAlgoSwitch is Preparation.
recommended.
CSFallBackBlindHoCfg User-defined sheet. See 7.6.5.1 Data None

CSFallBackBlindHoCfg Preparation.
is recommended.
UtranNFreq User-defined sheet. See 7.6.5.1 Data None

UtranNFreq is Preparation.
recommended.
CSFallBackPolicyCfg User-defined sheet. See 7.6.5.1 Data None

CSFallBackPolicyCfg Preparation.
is recommended.
Configuration.
Using MML Commands
The configurations in this section are examples, and configurations on the live network
can differ from the examples.
The prerequisite for the following operations is that E-UTRAN to UTRAN CS/PS
Steering has been activated.
Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous
coverage.
UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) check box selected under
2. Run the MOD CSFALLBACKBLINDHOCFG command with the Highest
priority InterRat, Second priority InterRat, CSFB Highest priority InterRat
for Idle UE, and CSFB Second priority InterRat for Idle UE parameters to
UTRAN, GERAN, GERAN, and UTRAN, respectively.
3. Run the MOD UTRANNFREQ command with the CS service priority or CS
and PS mixed priority parameter set to Priority_16(Priority 16) for UTRAN
frequencies.
4. Run the MOD CSFAllBACKPOLICYCFG command with the PS_HO check
box selected under the CSFB handover policy Configuration parameter and the
REDIRECTION check box selected under the CSFB handover policy
Configuration for idle ue parameter.
Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN provides
contiguous coverage but the UTRAN does not. In this scenario, the eNodeB may not
receive measurement reports after delivering UTRAN measurement configurations.
When the CSFB protection timer expires, the UE is redirected to the GERAN.
1. The feature activation procedure is as follows: Run the MOD GERANNCELL
command with the blind handover priority specified for the neighboring GERAN
cell.
2. Run the MOD ENODEBALGOSWITCH command with switches set as follows:
• Select the following options of the Handover Algo switch parameter:
UtranCsfbSwitch(UtranCsfbSwitch),
GeranCsfbSwitch(GeranCsfbSwitch),
UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch), and
GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch).
• Select the UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch)
option of the Frequency Layer Switch parameter.
• Deselect the BlindHoSwitch option of the Handover Mode switch
parameter.
3. Run the MOD CSFALLBACKBLINDHOCFG command with parameters set as
follows based on the network conditions and policies: Set the Highest priority
InterRat parameter to UTRAN. Set the Second priority InterRat parameter to
GERAN. Set the CSFB Highest priority InterRat for Idle UE parameter to
UTRAN. Set the CSFB Second priority InterRat for Idle UE parameter to
GERAN.
4. Run the MOD CSFALLBACKPOLICYCFG command with the
REDIRECTION option of the CSFB handover policy Configuration parameter
selected.
Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous
coverage.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSteeringSwitch-1;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0,
InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GE
RAN,IdleCsfbSecondPri=UTRAN;
MOD UTRANNFREQ:
LocalCellId=0,UtranDlArfcn=10800,CsPriority=Priority_16;
MOD UTRANNFREQ:
LocalCellId=1,UtranDlArfcn=9700,CsPsMixedPriority=Priority_16;
1, IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN provides
contiguous coverage but the UTRAN does not.
MOD GERANNCELL:LocalCellId=1, Mcc="460", Mnc="20", Lac=12,
GeranCellId=16,BlindHoPriority=32;
MOD ENODEBALGOSWITCH:HoModeSwitch=BlindHoSwitch-
0,HoAlgoSwitch=UtranCsfbSwitch-1&GeranCsfbSwitch-
1,HoAlgoSwitch=UtranCsfbSteeringSwitch-1&GeranCsfbSteeringSwitch-
1,FreqLayerSwtich=UtranFreqLayerMeasSwitch-1;
MOD
CSFALLBACKBLINDHOCFG:CnOperatorId=0,InterRatHighestPri=UTRAN,InterRatS
econdPri=GERAN,IdleCsfbHighestPri=UTRAN,IdleCsfbSecondPri=GERAN;
MOD CSFALLBACKPOLICYCFG:CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-
0,IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
The signaling procedure is the same as that for CSFB to UTRAN. After CS Fallback
Steering to UTRAN is used, check whether it works as expected.
The activation observation procedure for CSFB steering to UTRAN is as follows:
1. Check that the UE supports redirection-based CSFB and handover-based CSFB.
2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to
redirection and handover, respectively.
3. Enable the UE to initiate a voice call in idle mode and in connected mode.
4. Observe the counters L.CSFB.E2W, L.RRCRedirection.E2W.CSFB, and
L.IRATHO.E2W.CSFB.ExecAttOut. If the values of the counters increase by 2, 1,
and 1, respectively, CSFB steering to UTRAN has been activated.
If CSFB steering to GERAN has also been activated, the activation observation
procedure is as follows:
1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.
2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs
and UTRAN as the highest-priority RAT for CSFB triggered for
RRC_CONNECTED UEs.
4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase
by 1, both CSFB steering to UTRAN and CSFB steering to GERAN have been
activated.
7.6.7 Deactivation
Table 7-29 Parameters for deactivating CSFB steering to UTRAN

Data File Group
ENodeBAlgoSwitch User-defined sheet. HoAlgoSwitch Set

(eNodeB-level ENodeBAlgoSwitch UtranCsfbSteeringSwitch
switch) is recommended. under the HoAlgoSwitch
parameter to 0.
Using MML Commands

UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) check box cleared under the
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSteeringSwitch-0;
This section provides engineering guidelines for activation and activation observation of
LOFD-001078 E-UTRAN to UTRAN CS/PS Steering.
7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering
Use LOFD-001078 E-TURAN to UTRAN CS/PS Steering when all of the following
conditions are met: LOFD-001034 CS Fallback to UTRAN and LOFD-001019 PS Inter-
RAT Mobility between E-UTRAN and UTRAN have been activated. The operator owns
multiple UTRAN frequencies. The operator wants to divert CS or PS services to specific
UTRAN frequencies based on the network plan and loads.
1. Determine whether LOFD-001034 CS Fallback to UTRAN and LOFD-001019 PS

Inter-RAT Mobility between E-UTRAN and UTRAN have been activated.
the live network:
3. Collect the operating frequencies and frequency policies of the E-UTRAN and
UTRAN. The frequency policies for UTRAN and E-UTRAN must be the same.
For example, if F1 is the preferred frequency for voice services on UTRAN, the
same configuration is recommended for E-UTRAN.
4. Collect the configurations and versions of E-UTRAN and UTRAN equipment to
check whether CSFB is supported.
7.7.3 Requirements
None
License
Table 7-30 License information for E-UTRAN to UTRAN CS/PS Steering
Feature ID Feature Model License Control NE Sales Unit

Name Item
LOFD- E-UTRAN to LT1SEUCSPS00 E-UTRAN to eNodeB per RRC

001078 UTRAN UTRAN Connected
CS/PS CS/PS User
Steering Steering
7.7.4 Precautions
None
operator
Required Data
MO to enable E-UTRAN to UTRAN CS/PS Steering.

Name
Frequency ENodeBAlgoSwitch.FreqLayerSwtich Network When CSFB to UTRAN and PS inter-RA

Layer plan UTRAN and UTRAN have been configu
Switch (negotiation follows:
not • Select the
required) UtranFreqLayerMeasSwitch(Utra
Name
check box to enable measurement

UTRAN to UTRAN CS/PS Steering
• Select the
UtranFreqLayerBlindSwitch(Utra
check box to enable blind handove
CS/PS Steering.
The two check boxes can be simultaneo
set the CS service priority for a UTRAN frequency.

Name
CS UtranNFreq.CsPriority Network plan Set this parameter based on the

service (negotiation network plan. This parameter
priority not required) specifies the CS service priority
for the UTRAN frequency.
and save the file.
set the parameters.
Table 7-31 Parameters for E-UTRAN to UTRAN CS/PS steering
Data File
ENodeBAlgoSwitch User-defined sheet. See 7.7.5.1 Data Preparation. None

ENodeBAlgoSwitch
is recommended.
UtranNFreq User-defined sheet. See 7.7.5.1 Data Preparation. None

UtranNFreq is
recommended.
Configuration.
Using MML Commands
The prerequisite is that CSFB to UTRAN has been activated.

• Scenario 1: Blind E-UTRAN to UTRAN CS/PS steering
UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) check box selected
under the Frequency Layer Switch parameter.
2. Run the MOD UTRANNFREQ command with the CS service priority parameter
set to Priority_16(Priority 16).
• Scenario 2: Measurement-based E-UTRAN to UTRAN CS/PS steering
1. Run the MOD ENODEBALGOSWITCH command with
UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) selected under the
Frequency Layer Switch parameter.
2. Run the MOD UTRANNFREQ command with the CS service priority parameter
set to Priority_16(Priority 16).
• Scenario 1: Blind E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerBlindSwitch-1;
MOD UTRANNFREQ:
• Scenario 2: Measurement-based E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-1;
MOD UTRANNFREQ:
The signaling procedure is the same as that for CSFB to UTRAN. After E-UTRAN to
UTRAN CS/PS Steering is used, check whether it works as expected.
1. Verify that the UE supports CSFB and multiple UTRAN frequencies are available.
2. Enable measurement-based and blind handover for E-UTRAN to UTRAN CS/PS
Steering. Set a high PS service priority for UTRAN frequency F1 and a high CS
service priority for UTRAN frequency F2.
3. Have the UE camp on an LTE cell and initiate a voice call in the cell. The expected
result is that the UE falls back to the UTRAN cell operating on F2.
4. Have the UE camp on the LTE cell and initiate PS services. Move the UE to the
LTE cell edge. The expected result is that the UE is handed over to the UTRAN
cell operating on F1.
7.7.7 Deactivation
Existing eNodeBs.
In the procedure, modify parameters according to the table listed in the
Table 7-32 Parameters for deactivating E-UTRAN to UTRAN CS/PS Steering

Data File
ENodeBAlgoSwitch User-defined sheet. FreqLayerSwtich Clear the following options:

(eNodeB-level ENodeBAlgoSwitch • UtranFreqLayerMeasSwitch
switch) is recommended. • UtranFreqLayerBlindSwitch
Using MML Commands
• Deactivating blind E-UTRAN to UTRAN CS/PS steering

UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) check box cleared
• Deactivating measurement-based E-UTRAN to UTRAN CS/PS steering
UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) check box cleared
• Deactivating blind E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerBlindSwitch-0;
• Deactivating measurement-based E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-0;
This section provides engineering guidelines for LOFD-001034 CS Fallback to GERAN.
7.8.1 When to Use CS Fallback to GERAN
Use LOFD-001034 CS Fallback to GERAN in the initial phase of LTE network

deployment when both of the following conditions are met:
• The operator owns a mature GERAN network.
• The LTE network does not provide VoIP services, or UEs in the LTE network do
not support VoIP services.
For policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT
Mobility Management in Connected Mode. If GERAN and E-UTRAN cells cover the same area,
or the GERAN cell provides better coverage than the E-UTRAN cell, use CSFB based on
blind handover to decrease the CSFB delay.
• Collect the operating frequencies, coverage areas, and configurations of the E-

UTRAN and GERAN cells. Information about coverage areas includes engineering
• Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and
core networks, and ensure that they all support CSFB. Table 7-33 describes the
requirements of CSFB to GERAN for the core networks.
Table 7-33 Requirements of CSFB to GERAN for core networks
NE Requirement
MME Supports:
• SGs interface to the MSC
serving cell
• Combined EPS/IMSI attach,
combined EPS/IMSI detach, and
combined TAU/LAU
• Routing of CS signaling messages
• SMS over SGs
MSC Supports:
• Combined EPS/IMSI attach
• SMS over SGs
• Paging message forwarding over the
SGs interface
NE Requirement
SGSN Does not activate ISR during the

combined RAU/LAU procedure initiated by
the UE.
• Collect the following information about the UEs that support GSM and LTE on the
live network:
▪ Supported frequency bands
▪ Whether the UEs support redirection from E-UTRAN to GERAN
▪ Whether the UEs support PS handover from E-UTRAN to GERAN
▪ Whether the UEs support GERAN measurements
This information is used to configure neighboring GERAN cells and to
determine whether to perform CSFB based on handover or redirection. For
details, see Inter-RAT Mobility Management in Connected Mode.
7.8.3 Requirements
For CSFB to GERAN, the eNodeB must collaborate with core-network equipment. If the
core-network equipment is provided by Huawei, the version must be SAE1.2 or later. If
the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB to
GERAN.
License
Table 7-34 License information for CSFB to GERAN

Control
Item
LOFD- CS Fallback to LT1S00CFBG00 CS eNodeB per RRC

001034 GERAN Fallback to Connected
GERAN User
NOTE:
If the GERAN network uses Huawei equipment, activate the license for GBFD-511313 CSFB and turn on
the switch specified by the GCELLSOFT.SUPPORTCSFB parameter. This licence is used for scenarios
with LAU after CSFB to GERAN.
7.8.4 Precautions
None
operator
Required Data
Before configuring CSFB to GERAN, collect the data related to neighbor relationships
with GERAN cells. This section provides only the information about MOs related to
neighboring GERAN cells. For more information about how to collect data for the
parameters in these MOs, see Inter-RAT Mobility Management in Connected Mode Feature Parameter
Description.
1. GeranNfreqGroup: used to configure a group of neighboring GERAN

frequencies.
2. GeranNfreqGroupArfcn: used to configure a neighboring BCCH frequency in a
GERAN carrier frequency group.
3. GeranExternalCell: used to configure external GERAN cells. The
GeranExternalCell.Rac parameter must be set.
4. GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external GERAN cell. This MO is required only if the BTS that provides the
5. GeranNcell: used to configure the neighboring relationship with a GERAN cell. If
a neighboring GERAN cell supports blind handovers according to the network
plan, the blind-handover priority of the cell must be specified by the
GeranNcell.BlindHoPriority parameter.
MO to set the handover mode and handover algorithm switches for CSFB to GERAN.
Name
Handover ENodeBAlgoSwitch.HoModeSwitch Network Set this parameter based on the

Mode plan network plan.
switch (negotiation To activate PS handovers, select the
not GeranPsHoSwitch(GeranPsHoSwitch)
required) check box. To activate CCO, select the
GeranCcoSwitch(GeranCcoSwitch)
check box. To activate NACC, select the
GeranNaccSwitch(GeranNaccSwitch)
check box. If none of the preceding
check boxes is selected, redirection will
be used for CSFB to GERAN.
Handover ENodeBAlgoSwitch.HoAlgoSwitch Network To activate CSFB to GERAN, select the

Algo plan GeranCsfbSwitch(GeranCsfbSwitch)
switch (negotiation option.
not
required)

Name

required) If the
eNodeB are invalid.

required) If the
CSFB.

Name

required) the ID of the
operator whose
RAT blind-
handover priorities
are to be set.

and specifies the
highest-priority
RAT to be
considered in blind
handovers for
CSFB. For CSFB to
GERAN, set this
parameter to
GERAN.

and specifies the
second-highest-
priority RAT to be
considered in blind
handovers for
CSFB. If the
highest-priority
RAT has been set
to GERAN, the
second-highest-
priority RAT cannot
be set to GERAN.
Name
Ensure that this

parameter is set to
a different value
from the
InterRatHighestPri
and
InterRatLowestPri
parameters.

default and
specifies the low-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.
GERAN CSFallBackBlindHoCfg.GeranLcsCap Network Set this parameter

of the GERAN.
The following table describes the parameter that must be set in the CSFallBackHo MO
to set the CSFB protection timer.

Name
CSFB CSFallBackHo.CsfbProtectionTimer Network Set this parameter based

Protection plan on the network plan. The
Timer (negotiation default value 4 applies to
a GSM+UMTS+LTE
Name
not network. The default

required) value is also
recommended for a
GSM+LTE network. If this
large, the CSFB delay
increases in abnormal
CSFB scenarios. If this
small, normal
measurement or
handover procedures
may be interrupted.
MO to set the maximum number of neighboring GERAN cells whose system information
is sent to UEs for emergency redirections.
Parameter Parameter ID Data Source Setting

Name Notes
Max Geran InterRatHoComm.GeranCellNumForEmcRedirect Network The default

cell num in plan value is 0,
CSFB EMC (negotiation indicating
redirection not that no
required) system
information
of any
neighboring
UTRAN
cells is sent
to UEs for
emergency
redirections.
Operators
can set this
parameter
to 0 through
32 based
on the
network
plan. After
the CSFB
protection
Name Notes
timer
expires, the
eNodeB
performs an
emergency
redirection.
If the signal
quality of
the serving
cell is poor
and this
parameter
is set to a
large value,
the eNodeB
may fail to
send the
system
information
of
neighboring
UTRAN
cells to
UEs.
and save the file.
set the parameters.
Table 7-35 Parameters for CSFB to GERAN

Data File
GeranNfreqGroup GeranNfreqGroup See 7.8.5.1 Data The RNP

is
recommended.
GeranNfreqGroupArfcn GeranNfreqGroupArfcn See 7.8.5.1 Data The RNP

is
recommended.
GeranExternalCell GeranExternalCell See 7.8.5.1 Data The RNP

is
recommended.
GeranExternalCellPlmn GeranExternalCellPlmn See 7.8.5.1 Data The RNP

is
recommended.
GeranNcell GeranNcell See 7.8.5.1 Data The RNP

is
recommended.

customized on
a list-type
sheet of the
template.

customized on
a list-type
sheet of the
template.
Data File
CSFallBackHo User-defined sheet. See 7.8.5.1 Data This

CSFallBackHo is Preparation. parameter
customized on
a list-type
sheet of the
template.
InterRatHoComm User-defined sheet. See 7.8.5.1 Data None

InterRatHoComm is Preparation.
recommended.

customized on
a list-type
sheet of the
template.
Batch Activated
Maintenance.
Configuration.
7.8.5.5 Using Feature Operation and Maintenance on the CME
1. On the U2000 client, choose CME > Planned Area > Create Planned
Area.
2. In the displayed Create Planned Area dialog box, specify Planned area name,
select the eNodeB (for which CSFB to GERAN is to be activated) on the Base
Station tab page under Available NEs, and click so that it is added to
Selected NEs. Then, click OK.
3. Choose CME > Advanced > Feature Operation and Maintenance >
Export Feature Commission Data from the main menu.
4. In the displayed dialog box, click LTE in the Category drop-down list, and select
the CSFB to GERAN feature to be activated, for example, TDLOFD-001033
CSFB to GERAN. Then, click Next.
5. Under Available Base Stations in the dialog box, select the eNodeB whose data is
to be exported. Click so that the eNodeB is added to Selected Base
Stations. Then, click Next.
6. In the dialog box, set Export as to the format (.xls or .xlsm) in which the exported
data is to be saved. Click to the right of Export path to specify the save path.
Then, click Next.
7. Wait until the data is exported.
8. Click the hyperlink to the save path. Alternatively, click Finish, and locate the
exported file in the save path.
9. Set related parameters in the CSFB to UTRAN data file (for example, TDLOFD-
001033.xls).
10. After setting the parameters, choose CME > Advanced > Feature
Operation and Maintenance > Import Feature Commission Data on the
U2000 client. In the displayed dialog box, select the CSFB to GERAN data file,
and click Next.
11. Wait until the file is imported. Leave the Export incremental script check box
selected (default setting). Click Finish.
12. In the displayed dialog box, check that the eNodeB is displayed in the Selected
NEs area. Set Encrypt script and Script Executor Operation. You are advised to
set Script Executor Operation to Launch script executor and activate exported
project so that the script will be executed upon it is loaded. Then, click OK.
13. In the displayed confirmation dialog box, click Yes. Data synchronization starts for
the eNodeB. When Success is displayed in the Result column, the CSFB to
GERAN feature has been activated.
The following table describes parameters for CSFB to GERAN:
Table 7-36 Parameters for CSFB to GERAN
MO Parameter Parameter ID Setting Notes

Name
GERANNFREQGROUP Local cell ID LocalCellId Manually configured
BCCH group BcchGroupId Manually configured

ID
GERAN versi GeranVersion Manually configured

Name
Starting StartingArfcn Manually configured

ARFCN
Band BandIndicator Manually configured

indicator
Cell CellReselPriorityCfgInd Automatically

reselection configured as
priority NOT_CFG
configure
indicator
Cell CellReselPriority Automatically

reselection configured as 1
priority
PMAX PmaxGeranCfgInd Automatically

configure configured as
indicator NOT_CFG
PMAX PmaxGeran Manually configured
Minimum QRxLevMin Automatically

required RX configured as 0
level
High priority ThreshXHigh Automatically

threshold configured as 7
Lower ThreshXLow Automatically

priority configured as 7
threshold
Frequency OffsetFreq Automatically

offset configured as 0
NCC NccPermitted Automatically

monitoring configured as 255
permitted
GERANNFREQGROUPARFCN Local cell ID LocalCellId Manually configured
BCCH group BcchGroupId Manually configured

ID
GERAN GeranArfcn Manually configured

ARFCN
Name
GERANEXTERNALCELL Mobile Mcc Manually configured

country code
Mobile Mnc Manually configured

network code
GERAN cell GeranCellId Manually configured

ID
Location Lac Manually configured

area code
Routing area RacCfgInd Automatically

code configured as
configure NOT_CFG
indicator
Routing area Rac Manually configured

code
Band BandIndicator Manually configured

indicator
GERAN GeranArfcn Manually configured

ARFCN
Network NetworkColourCode Manually configured

color code
Base station BaseStationColourCode Manually configured

color code
DTM DtmInd Automatically

indication configured as
DTM_NOT_AVAILABLE
Cell name CellName Manually configured
CS and PS CsPsHOInd Automatically

handover configured as
indication BOOLEAN_FALSE
GERANEXTERNALCELLPLMN GERAN cell GeranCellId Manually configured

ID

area code
Name
Mobile Mcc Manually configured

country code

network code
Share mobile ShareMcc Manually configured

country code
Share mobile ShareMnc Manually configured

network code
GERANNCELL Local cell ID LocalCellId Manually configured
Mobile Mcc Manually configured

country code

network code

area code
GERAN cell GeranCellId Manually configured

ID
No handover NoHoFlag Automatically

indicator configured as
PERMIT_HO_ENUM
No remove NoRmvFlag Automatically

indicator configured as
PERMIT_RMV_ENUM
Blind BlindHoPriority 0
handover
priority
Local cell LocalCellName Manually configured

name
Neighboring NeighbourCellName Manually configured

cell name
ENODEBALGOSWITCH Handover HoAlgoSwitch Automatically

Algo switch configured as
GeranCsfbSwitch-1
Name
Handover HoModeSwitch Automatically

Mode switch configured as
GeranRedirectSwitch-
1&BlindHoSwitch-
0&GeranPsHoSwitch-0
CSFALLBACKPOLICYCFG CSFB CsfbHoPolicyCfg Automatically

policy REDIRECTION-
Configuration 1&CCO_HO-0&PS_HO-
0
CSFB IdleModeCsfbHoPolicyCfg Automatically

policy REDIRECTION-
Configuration 1&CCO_HO-0&PS_HO-
for idle ue 0
Csfb User CsfbUserArpCfgSwitch Automatically

Arp configured as OFF
Configuration
Switch
Normal Csfb NormalCsfbUserArp Automatically

User Arp configured as 2
CSFALLBACKBLINDHOCFG CN operator CnOperatorId Manually configured

ID
Highest InterRatHighestPri Automatically

priority configured as UTRAN
InterRat
Second InterRatSecondPri Automatically

priority configured as GERAN
InterRat
Lowest InterRatLowestPri Automatically

priority configured as
InterRat CDMA2000
GERAN LCS GeranLcsCap Automatically

capability configured as OFF
CSFALLBACKHO Local cell ID LocalCellId Manually configured

Name
CSFB Geran CsfbHoGeranTimeToTrig Automatically

EventB1 configured as 40ms
Time To Trig
CSFB CsfbHoGeranB1Thd Automatically

GERAN configured as -103
EventB1
Trigger
Threshold
CSFB CsfbProtectionTimer Automatically

Protection configured as 4
Timer
CELLHOPARACFG Handover HoModeSwitch Automatically

Mode switch configured as
BlindHoSwitch-0
INTERRATHOCOMM Max Geran GeranCellNumForEmcRedirect Automatically

cell num in configured as 0
CSFB EMC
redirection
MML-based Procedure
• Basic scenario 1: CSFB to GERAN using blind redirection

CSFB to GERAN using blind redirection works regardless of whether neighboring
GERAN cells are configured.
• If you want to configure a neighboring GERAN cell, you must configure the
GeranNFreqand GeranNCell MOs. For details about parameter settings, see Inter-
• If you do not want to configure a neighboring GERAN cell, you must configure the
GeranRanShare or GeranExternalCell MO. For details about parameter settings,
see Inter-RAT Mobility Management in Connected Mode.
1. Run the following eNodeB- and cell-level commands to enable the blind handover
function for CSFB to GERAN:
parameter selected.
b. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of
the Handover Mode switch parameter selected.
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch
parameter selected.
PS_HO option of the CSFB handover policy Configuration parameter deselected
and the REDIRECTION option of the same parameter selected.
4. (Optional) If you require setting GERAN as having the highest priority for CSFB,
priority InterRat parameter set to GERAN and the Second priority InterRat
parameter set to UTRAN.
5. (Optional) If a neighboring GERAN cell is configured, run the MOD
GERANNCELL command with the Blind handover priority parameter set to the
highest priority (32).
6. (Optional) If no neighboring GERAN cell is configured, run the ADD
GeranNfreqGroup command with the Frequency Priority for Connected Mode
parameter set to the highest priority (8).
• Basic scenario 2: CSFB to GERAN using blind CCO with NACC
1. Add neighboring GERAN frequencies and neighbor relationships with GERAN
Connected Mode.
parameter, the BlindHoSwitch(BlindHoSwitch),
GeranNaccSwitch(GeranNaccSwitch), and GeranCcoSwitch(GeranCcoSwitch)
options of the Handover Mode switch parameter, and the
GERAN_RIM_SWITCH(GERAN RIM Switch) option of the RIM switch
parameter selected.
3. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO and
CCO_HO options of the CSFB handover policy Configuration parameter
deselected and selected, respectively.
5. (Optional) If you require setting UTRAN as having the highest priority for CSFB,
6. Run the MOD GERANNCELL command with the Blind handover priority
• Basic scenario 3: CSFB to GERAN using blind handovers
Connected Mode.
parameter and the BlindHoSwitch(BlindHoSwitch) and
GeranPsHoSwitch(GeranPsHoSwitch) options of the Handover Mode switch
parameter selected.
3. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
4. (Optional) If the optional feature LOFD-001089 CS Fallback Steering to GERAN
is enabled, run the MOD CSFALLBACKPOLICYCFG command with the
PS_HO option of the CSFB handover policy Configuration parameter selected.
5. (Optional) If you require setting GERAN as having the highest priority for CSFB,
• Basic scenario 4: CSFB to GERAN using measurement-based redirections
Connected Mode.
parameter selected.
PS_HO option of the CSFB handover policy Configuration parameter deselected
and the REDIRECTION option of the same parameter selected.
• Basic scenario 5: CSFB to GERAN using measurement-based handovers
(recommended)
Connected Mode.
GeranCsfbSwitch(GeranCsfbSwitch) check box selected under the Handover
Algo switch and the GeranPsHoSwitch(GeranPsHoSwitch) check box selected
under the Handover Mode switch parameter.
4. (Optional) If the optional feature LOFD-001089 CS Fallback Steering to GERAN
is enabled, run the MOD CSFALLBACKPOLICYCFG command with the
PS_HO option of the CSFB handover policy Configuration parameter selected.
• Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC
(recommended)
Connected Mode.
parameter, the GeranNaccSwitch(GeranNaccSwitch) and
GeranCcoSwitch(GeranCcoSwitch) options of the Handover Mode switch
parameter, and the GERAN_RIM_SWITCH(GERAN RIM Switch) option of the
RIM switch parameter selected.
4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO and
CCO_HO options of the CSFB handover policy Configuration parameter
deselected and selected, respectively.
• Basic scenario 1: CSFB to GERAN using blind redirection (configured with

neighboring GERAN cells)
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1,
0;
InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;
MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12,
• Basic scenario 1: CSFB to GERAN using blind redirection (configured with no
neighboring GERAN cell)
0;
ADD GeranNfreqGroup: LocalCellId=0, BcchGroupId=0, StratingArfcn=0,
ConnFreqPriority=8;
ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0,GeranArfcn=0;
ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="20";
• Basic scenario 2: CSFB to GERAN using blind CCO with NACC

HoModeSwitch=BlindHoSwitch-1&GeranNaccSwitch-1&GeranCcoSwitch-
1,RimSwitch=GERAN_RIM_SWITCH-1;
0;
• Basic scenario 3: CSFB to GERAN using blind handovers

HoModeSwitch=GeranPsHoSwitch-1&BlindHoSwitch-1;
1;
• Basic scenario 4: CSFB to GERAN using measurement-based redirections

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1;
0;
• Basic scenario 5: CSFB to GERAN using measurement-based handovers

HoModeSwitch=GeranPsHoSwitch-1;
1;
• Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC

HoModeSwitch=GeranNaccSwitch-1&GeranCcoSwitch-
0;

1. Enable a UE to camp on an E-UTRAN cell and make a voice call.
2. Enable the UE to camp on an E-UTRAN cell and receive a voice call.
You can observe the signaling procedures for CSFB to GERAN, which is similar to that
for CSFB to UTRAN described in section Figure 7-16.
NOTE:
In the following figures, the UE on the left side and the UE on the right side are the same UE. The
signaling on the GERAN side is for reference only. The procedure for mobile-terminated calls is similar to
the procedure for mobile-originated calls except that the procedure for mobile-terminated calls includes
paging.
Figure 7-16 Redirection-based CSFB to GERAN for a mobile-originated call
The signaling procedure for PS handover-based CSFB to GERAN is different from the
signaling procedure for redirection-based CSFB to GERAN. The difference is as follows:
In PS handover-based CSFB to GERAN, the eNodeB performs a PS handover procedure
rather than an RRC connection release procedure after the UE reports measurement
results to the eNodeB. For details about the signaling procedure of PS handover-based
CSFB to GERAN, see 7.1.6 Activation Observation. In the signaling procedure of PS
handover-based CSFB to GERAN, the CSFB indication flag is true and the CSFB target
is GERAN in the MobilityFromEUTRACommand message.
In the signaling procedure for PS handover-based CSFB to GERAN, the cs-
FallbackIndicator IE is TRUE and the CSFB target is GERAN in the
MobilityFromEUTRACommand message. Figure 7-17 shows the signaling procedure for
CCO/NACC-based CFSB to GERAN for a mobile-originated call. In the CSFB,
handover preparation is absent. The MobilityFromEUTRACommand message carries the
CCO/NACC information and the CSFB target is GERAN.
Figure 7-17 CCO/NACC-based CSFB to GERAN for a mobile-originated call
Counter Observation
Table 7-37 lists the performance counters for observing functions related to CSFB to
GERAN.
Table 7-37 Performance counters for observing CSFB to GERAN
CSFB to 1526728324 L.CSFB.E2G Number of times CSFB to

GERAN GERAN is performed
CSFB to 1526728710 L.CSFB.E2G.Emergency Number of times CSFB to

GERAN GERAN is triggered for
triggered for emergency calls
emergency calls
7.8.7 Deactivation
Table 7-38 Parameters for deactivating CSFB to GERAN
MO Sheet in the Parameter Group Remarks

Summary Data File
ENodeBAlgoSwitch User-defined sheet HoAlgoSwitch To deactivate CSFB

to GERAN, set
GeranCsfbSwitch
under the
HoAlgoSwitch
parameter to 0.
Using MML Commands

GeranCsfbSwitch(GeranCsfbSwitch) check box cleared under the Handover Algo
switch parameter.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-0;

CSFB is an end end-to to-end service. The performance counters on the LTE side can
only indicate the success rate of the CSFB procedure on the LTE side, and. they cannot
indicate the success rate of the CSFB procedure on the target side. Therefore, the
performance counters on the LTE side cannot directly show user experience of the CSFB
procedure. It is recommended that you perform drive tests and use the performance
counters on the UE side to indicate the actual user experience of the CSFB procedure.
Related counters are listed in Table 7-39.
Table 7-39 Counters related to the execution of CSFB by the eNodeB
1526728321 L.CSFB.PrepAtt Number of CSFB indicators received by

the eNodeB
1526728322 L.CSFB.PrepSucc Number of successful CSFB responses

from the eNodeB
Table 7-40 lists the counter related to CSFB to GERAN.

Table 7-40 Counter related to CSFB to GERAN
1526728324 L.CSFB.E2G Number of procedures for CSFB to

GERAN
lists the counters that indicate whether CSFB is performed through redirection
Table 7-41
or through handover.
Table 7-41 Counters related to CSFB through redirection or handover
1526728498 L.RRCRedirection.E2G.CSFB Number of CSFB-based redirections

from E-UTRAN to GERAN
1526728507 L.IRATHO.E2G.CSFB.PrepAttOut Number of CSFB-based inter-RAT

E-UTRAN to GERAN
You can check whether CCO with NACC or CCO without NACC is used as the CSFB
mechanism by viewing the counters listed in Table 7-42.
Table 7-42 Counters related to using CCO with NACC or CCO without NACC
1526729505 L.CCOwithNACC.E2G.CSFB.ExecAttOut Number of CSFB-based CCO

with NACC executions from E-
UTRAN to GERAN
1526729506 L.CCOwithNACC.E2G.CSFB.ExecSuccOut Number of successful CSFB-

based CCOs with NACC from E-
UTRAN to GERAN
1526729507 L.CCOwithoutNACC.E2G.CSFB.ExecAttOut Number of CSFB-based CCO

without NACC executions from
E-UTRAN to GERAN
The CCO success rate can be calculated in the following ways:

• L.CCOwithNACC.E2G.CSFB.ExecSuccOut/ L.CCOwithNACC.E2G.CSFB.ExecAttOut
• L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut/ L.CCOwithoutNACC.E2G.CSFB.ExecAttOut
After the CSFB protection timer expires, the eNodeB may perform a blind redirection to
enter the protection procedure. Table 7-43 lists the related counter. A larger value of this
counter indicates a longer average UE access delay during CSFB.
Table 7-43 Counter related to the number of times that the eNodeB enters the protection
procedure for CSFB
1526729516 L.RRCRedirection.E2G.CSFB.TimeOut Number of CSFB-based blind

redirections from E-UTRAN to
GERAN caused by CSFB
protection timer expiration
Table 7-44 lists the counters related to CSFB for emergency calls.
Table 7-44 Counters related to CSFB for emergency calls
1526729513 L.IRATHO.E2G.CSFB.ExecAttOut.Emergency Number of CSFB-based

handover execution attempts
to GERAN triggered for
emergency calls
1526729514 L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency Number of successful CSFB-

based handover executions
to GERAN triggered for
emergency calls
CSFB handover success rate for emergency calls =
L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency/L.IRATHO.E2G.CSFB.ExecAttOut.E
mergency
The blind-handover-related parameter optimization procedure for CSFB to GERAN is the

same as that for CSFB to UTRAN. For details, see 7.1.9 Parameter Optimization.
The following table lists event-B1-related parameters for CSFB to GERAN in the
CSFallBackHo MO.

Name
Local cell CSFallBackHo.LocalCellId Network Set this parameter

ID plan based on the network
(negotiation plan.
not
required)
CSFB CSFallBackHo.CsfbHoGeranB1Thd Network Set this parameter

GERAN plan based on the network
EventB1 (negotiation plan. This parameter
Trigger not specifies the RSSI
Threshold required) threshold for event B1
in CSFB to GERAN.
Event B1 is triggered
when the measured
RSSI of a GERAN cell
reaches the value of
this parameter and all
other conditions are
also met.
CSFB CSFallBackHo.CsfbHoGeranTimeToTrig Network Set this parameter

Geran plan based on the network
EventB1 (negotiation plan. This parameter
Time To not specifies the time-to-
Trig required) trigger for event B1 in
CSFB to GERAN.
When CSFB to
GERAN is required,
set this parameter,
which is used by UEs
as one of the
conditions for
triggering event B1.
When a UE detects
that the signal quality
in at least one
Name
GERAN cell meets

the entering condition,
it does not
immediately send a
measurement report
to the eNodeB.
Instead, the UE sends
a measurement report
only when the signal
quality has been
meeting the entering
condition throughout a
period defined by this
parameter. This
parameter helps
decrease the number
of occasionally
triggered event
reports, the average
number of handovers,
and the number of
incorrect handovers,
preventing
unnecessary
handovers.
7.9 RIM Procedure from E-UTRAN to GERAN
7.9.1 When to Use RIM Procedure Between E-UTRAN and GERAN
It is recommended that the RIM procedure be performed through the Huawei-proprietary

eCoordinator if the following two conditions are met: 1. Both the eNodeB and the
RNC/BSC are provided by Huawei and are connected to the same eCoordinator. 2. The
core network that the eNodeB and the RNC/BSC are connected to does not support the
RIM procedure or is not enabled with the RIM procedure. To perform the RIM procedure
through the eCoordinator, set ENodeBAlgoSwitch.RimOnEcoSwitch to ON(On).
In other conditions, it is recommended that the RIM procedure be performed through the
core network. In this case, set ENodeBAlgoSwitch.RimOnEcoSwitch to OFF(Off).
Check whether the BSC, MME, and SGSN support the RIM procedure, and whether an
eCoordinator has been deployed.
7.9.3 Requirements
If the RIM procedure is performed through the core network, the core-network equipment
must support this feature:
• If the equipment is provided by Huawei, the version must be SAE1.2.
• If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature.
• The BSC, MME, and SGSN must support the RIM procedures. If one of the NEs
does not support, the RIM procedures fail.
NOTE:
In a multioperator core network (MOCN) scenario, the eNodeB preferentially selects the link for the
primary operator when sending an RIM request. If the RIM procedure fails, the eNodeB no longer
attempts to send the RIM request on other links.
If the RIM procedure is performed through the eCoordinator, the RNC/BSC, eNodeB,
and eCoordinator must all be provided by Huawei and with the switch for supporting the
RIM procedures through eCoordinator turned on.
License
Table 7-45 License control item for CSFB to GERAN

ID Control Item
LOFD- CSFB to LT1S00CFBG00 CS Fallback eNodeB per user in

001034 GERAN to GERAN RRC
connected
mode
7.9.4 Precautions
None
operator
Required Data
GeranExternalCell: used to configure external GERAN cells. The
MO to configure the RIM procedure.

Name
Support RIM ENodeBAlgoSwitch.RimOnEcoSwitch Network If

by plan ENodeBAlgoSwitch.RimOnEcoSw
eCoordinator (negotiation is set to OFF(Off), the RIM procedur
Switch not performed through the core network.
required) If
ENodeBAlgoSwitch.RimOnEcoSw
is set to ON(On), the RIM procedure
performed through the eCoordinator.
and save the file.
set the parameters.

Data File
ENodeBAlgoSwitch User-defined sheet. Support RIM by None

ENodeBAlgoSwitch eCoordinator Switch
is recommended.
Configuration.
Using MML Commands



Counter Observation
No matter whether the RIM procedure is performed through the core network or the
eCoordinator, performance counters listed in Table 7-47 can be used to observe whether the
RIM procedure has taken effect.
Table 7-47 Counters related to the RIM procedure between E-UTRAN and GERAN
1526729661 L.RIM.SI.E2G.Req Number of times the

eNodeB sends a system
information request to a
GERAN
1526729662 L.RIM.SI.E2G.Resp Number of times the

eNodeB receives a system
information response from
a GERAN
1526729663 L.RIM.SI.E2G.Update Number of times the

eNodeB receives a system
information update from a
GERAN
Signaling Tracing Result Observation
If the RIM procedure is performed through the core network, trace signaling messages as
follows:
1. Start an S1 interface tracing task on the eNodeB LMT.

Check whether the eNB DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMATION-REQUEST IE is sent over the S1 interface.
successfully.
2. Start a Gb interface tracing task on the BSC LMT.
If after receiving the DIRECT INFORMATION TRANSFER message containing
the RAN-INFORMATION-REQUEST IE, the BSC sends the DIRECT
INFORMATION TRANSFER message containing the RAN-INFORMATION IE
to the SGSN, you can infer that the BSC can response to the RIM request normally.
3. Change the state of the GSM cell.
If the BSC sends the DIRECT INFORMATION TRANSFER message containing
the RAN-INFORMAION IE over the Gb interface, you can infer that the BSC can
notify the eNodeB with the cell state change through the RIM procedure.
If the RIM procedure is performed through the eCoordinator, trace signaling messages as
follows:
1. Start an Se interface tracing task on the eNodeB LMT.
Check whether the ENB DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMATION-REQUEST IE is sent over the Se interface.
successfully.
2. Start an Sg interface tracing task on the BSC LMT.
If after receiving the ECO DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMATION-REQUEST IE, the BSC sends the BSC
DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMAION IE to the eCoordinator, you can infer that the BSC can response to
the RIM request normally.
3. Change the state of the GSM cell.
If the BSC sends the BSC DIRECT INFORMATION TRANSFER message
containing the RAN-INFORMATION IE over the Sg interface, you can infer that
the BSC can notify the eNodeB with the cell state change through the RIM
procedure.
7.9.7 Deactivation
Data File
ENodeBAlgoSwitch User-defined sheet. RimOnEcoSwitch Set this parameter to

ENodeBAlgoSwitch OFF(Off).
is recommended.
Using MML Commands



GERAN. For details, see 7.8.8 Performance Monitoring.
GERAN. For details, see 7.8.9 Parameter Optimization.
This section provides engineering guidelines for LOFD-001053 Flash CS Fallback to

GERAN.
7.10.1 When to Use Flash CS Fallback to GERAN
When LOFD-001034 CS Fallback to GERAN has been enabled, use LOFD-001053 Flash
CS Fallback to GERAN if all the following conditions are met:The E-UTRAN and
GERAN support the RIM with SIB procedure.3GPP Release 9 UEs are used on the live
network.The core networks support the RIM procedure. For policies on whether to use
PS handover or PS redirection for CSFB, see Inter-RAT Mobility Management in Connected Mode.
If GERAN and E-UTRAN cells cover the same area, or the GERAN cell provides better
coverage than the E-UTRAN cell, use CSFB based on blind handover to decrease the
CSFB delay.
• Collect information about whether LOFD-001034 CS Fallback to GERAN has been

activated.
core networks, and ensure that they all support CSFB and the RIM procedure. Table
7-49 describes the requirements of flash CSFB to GERAN for the core networks. For
details about processing in Huawei GSM equipment, see Interoperability Between
GSM and LTE in GBSS Feature Documentation.
live network:
▪ Whether the UEs comply with 3GPP Release 9 specifications
• This information is used to configure neighboring GERAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Inter-RAT
Mobility Management in Connected Mode.
Table 7-49 Requirements of flash CSFB to GERAN for core networks

NE Requirement
MME Supports CSFB and RIM procedures
SGSN Supports CSFB and RIM procedures
7.10.3 Requirements
For flash CSFB to GERAN, the eNodeB must collaborate with core-network equipment.
If the core-network equipment is provided by Huawei, the version must be PS9.2 or later.
If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support flash CSFB
to UTRAN.
License
Table 7-50 License information for flash CSFB to GERAN

Name Control Item
LOFD- CSFB to LT1S00CFBG00 CS Fallback eNodeB per RRC

001034 GERAN to GERAN Connected User
LOFD- Flash LT1S0FCFBG00 Flash CS eNodeB per RRC

001053 CSFB to Fallback to Connected User
GERAN GERAN
NOTE:
If the GERAN uses Huawei devices, evolved network assisted cell change (eNACC) between E-UTRAN
and GERAN for CSFB needs to be enabled on the GERAN.
7.10.4 Precautions
None
operator
Required Data
Before configuring CSFB to GERAN, collect the data related to neighbor relationships
with GERAN cells. This section provides only the information about MOs related to
neighboring GERAN cells and key parameters in these MOs. For more information about
how to collect data for the parameters in these MOs, see Inter-RAT Mobility Management
in Connected Mode Feature Parameter Description.
1. GeranNfreqGroup: used to configure a group of neighboring GERAN
frequencies.
2. GeranNfreqGroupArfcn: used to configure a neighboring BCCH frequency in a
GERAN carrier frequency group.
3. GeranExternalCell: used to configure external GERAN cells. The
4. GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external GERAN cell. This MO is required only if the BTS that provides the
5. GeranNcell: used to configure the neighboring relationship with a GERAN cell. If
a neighboring GERAN cell supports blind handovers according to the network
plan, the blind-handover priority of the cell must be specified by the
GeranNcell.BlindHoPriority parameter.
MO to set the handover mode and handover algorithm switches for flash CSFB to
GERAN.

Name
Handover ENodeBAlgoSwitch.HoModeSwitch Network Set this parameter based on the network p

Mode plan
switch (negotiation
not
required)
Handover ENodeBAlgoSwitch.HoAlgoSwitch Network To activate flash CSFB to GERAN, select t

Algo plan GeranCsfbSwitch(GeranCsfbSwitch) an
switch (negotiation GeranFlashCsfbSwitch(GeranFlashCsfb
not check boxes.
required)
RIM ENodeBAlgoSwitch.RimSwitch Network GERAN_RIM_SWITCH(GERAN RIM Swit

switch plan under this parameter specifies whether to e
(negotiation or disable the RIM procedure that requests
not driven multiple reports from GERAN cells.
required) If this switch is turned on, the eNodeB can
RAN-INFORMATION-REQUEST/Multiple R
Name
PDUs to GERAN cells to request event-dri

multiple reports.
If this switch is turned off, the eNodeB cann
RAN-INFORMATION-REQUEST/Multiple R
PDUs to GERAN cells.
If this switch is turned off and
GeranFlashCsfbSwitch(GeranFlashCsfb
under ENodeBAlgoSwitch.HoAlgoSwitch
turned on, the eNodeB sends RAN-
INFORMATION-REQUEST/Single Report
GERAN cells to request single reports.
If the GERAN cells support RAN-INFORMA
REQUEST/Multiple Report PDUs, you are
to select the GERAN_RIM_SWITCH(GERA
Switch) option.

Name

required) If the
eNodeB are invalid.

required) If the
The following table describes the parameter that must be set in the S1Interface MO to
set the compliance protocol release of the MME.
Name
MME S1INTERFACE.MmeRelease Network To activate RIM procedures in

Release plan Multiple Report mode, set the
(negotiation parameter to
not Release_R9(Release 9).
required)
CSFB.

Name

required) the ID of the
operator whose
RAT blind-
handover priorities
are to be set.

and specifies the
highest-priority
RAT to be
considered in blind
handovers for
CSFB. For flash
CSFB to GERAN,
set this parameter
to GERAN.

and specifies the
second-highest-
Name
priority RAT to be
considered in blind
handovers for
CSFB. If the
highest-priority
RAT has been set
to GERAN, the
second-highest-
priority RAT cannot
be set to GERAN.
Ensure that this
parameter is set to
a different value
from the
InterRatHighestPri
and
InterRatLowestPri
parameters.

default and
specifies the low-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.

of the GERAN.
is sent to UEs for flash redirections.

Name Notes
Max InterRatHoComm.CellInfoMaxGeranCellNum Network Set this

Geran cell plan parameter
num in (negotiation based on
redirection not the network
required) plan. The
default
value is 8. If
this
parameter
is set too
small, the
flash CSFB
success
rate
decreases
because
UEs may
not receive
valid
neighboring
cell system
information.
If this
parameter
is set too
large, the
size of an
RRC
connection
release
message
increases
and CSFB
may fail.
and save the file.
set the parameters.
Table 7-51 Parameters for flash CSFB to GERAN
Data File
GeranNfreqGroup GeranNfreqGroup See 7.10.5.1 Data The RNP

is
recommended.
GeranNfreqGroupArfcn GeranNfreqGroupArfcn See 7.10.5.1 Data The RNP

is
recommended.
GeranExternalCell GeranExternalCell See 7.10.5.1 Data The RNP

is
recommended.
GeranExternalCellPlmn GeranExternalCellPlmn See 7.10.5.1 Data The RNP

is
recommended.
GeranNcell GeranNcell See 7.10.5.1 Data The RNP

is
recommended.
S1Interface S1Interface See 7.10.5.1 Data This

Preparation. parameter
must be
customized on
a list-type
sheet of the
template.
Data File

customized on
a list-type
sheet of the
template.

customized on
a list-type
sheet of the
template.
InterRatHoComm User-defined sheet. See 7.10.5.1 Data None

InterRatHoComm is Preparation.
recommended.
CSFallBackHo User-defined sheet. See 7.10.5.1 Data None

CSFallBackHo is Preparation.
recommended.

customized on
a list-type
sheet of the
template.
Batch Activated
Maintenance.
Configuration.
Using MML Commands
The prerequisite is that CSFB to GERAN has been activated. In addition to the steps in
the CSFB to GERAN using blind redirections or CSFB to GERAN using measurement-
based redirections scenario, perform the following steps:
GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box selected under the
Handover Algo switch parameter and with the
GERAN_RIM_SWITCH(GERAN RIM Switch) check box selected under the
RIM switch parameter.
2. Run the MOD S1INTERFACE command with the MME Release parameter set
to Release_R9(Release 9).
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranFlashCsfbSwitch-

MOD S1INTERFACE:
S1InterfaceId=2,S1CpBearerId=1,CnOperatorId=0,MmeRelease=Release_R9;
Enable a UE to camp on an E-UTRAN cell and originate a voice call. If so that the UE
falls back to a GERAN cell and completes the call continues, and the RRC Connection
Release message traced in on the Uu interface tracing carries the information of the
neighboring GERAN cell. In this case, flash CSFB to GERAN has been activated
successfully.
In this case, flash CSFB to GERAN has been activated successfully. The procedure of
flash CS fallback to GERAN on the E-UTRAN side is the same as the procedure of
redirection-based CS fallback to GERAN. For details, see 7.1.6 Activation Observation. The
difference is that the RRC Connection Release message carries the system information of
the neighboring GERAN cell. For details, see Figure 7-20.
Figure 7-20 The RRC Connection Release message during flash CSFB to GERAN
Check the status of the RIM procedure towards neighboring GERAN cells by running the
DSP GERANRIMINFO command. If the ID of a neighboring GERAN cell is displayed
in the command output, the eNodeB has obtained the system information of this
neighboring GERAN cell.
Counter Observation
The counter listed in Table 7-52 can be viewed to check whether the feature has taken
effect.
Table 7-52 Performance counters for observing flash CSFB to GERAN
Functions Counter ID Counter Name Description
Flash CS Fallback 1526728706 L.FlashCSFB.E2G Number of

to GERAN procedures for flash
CSFB to GERAN
RIM during flash 1526729661 L.RIM.SI.E2G.Req Number of times the

CSFB to GERAN eNodeB sends a
system information
request to a GERAN
1526729662 L.RIM.SI.E2G.Resp Number of times the

eNodeB receives a
system information
response from a
GERAN
1526729663 L.RIM.SI.E2G.Update Number of times the

eNodeB receives a
system information
update from a
GERAN
7.10.7 Deactivation
to that for feature activation described in 7.10.5.3 Using the CME to Perform Batch Configuration
for Existing eNodeBs. In the procedure, modify parameters according to Table 7-53.
Table 7-53 Parameters for deactivating flash CSFB to GERAN
MO Sheet in the Parameter Group Remarks

Summary Data File
ENodeBAlgoSwitch User-defined HoAlgoSwitch Set

sheet GeranFlashCsfbSwitch
under the
HoAlgoSwitch
parameter to 0.
Using MML Commands

GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box cleared under the
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranFlashCsfbSwitch-0;
This section provides engineering guidelines for LOFD-081283 Ultra-Flash CSFB to

GERAN.
7.11.1 When to Use This Feature
The LOFD-001034 CS Fallback to GERAN feature is recommended in scenarios where

the eNodeB, MME, and MSC are provided by Huawei, and a proportion of UEs in the
live network support SRVCC from E-UTRAN to GERAN. It is recommended that this
feature be activated in GERAN and E-UTRAN overlapping coverage areas.
Before deploying this feature, collect the following information:

• Check whether LOFD-001034 CS Fallback to GERAN has been activated.
• Check whether the eNodeB, MME, and MSC in the network are provided by
Huawei and they all support this feature.
Check whether a proportion of UEs in the live network support SRVCC from E-UTRAN
to GERAN.
7.11.3 Requirements
This feature is a Huawei-proprietary feature and requires that the eNodeB, MME, and
MSC are provided by Huawei and support this feature. This feature is used with
MME11.0 and MSC11.0.
License
Table 7-54 License information for ultra-flash CSFB to GERAN

ID Control Item
LOFD- Ultra-Flash CSFB LT1SUFCSFB20 Ultra-Flash eNodeB per RRC

081283 to GERAN CSFB to Connected
GERAN User
7.11.4 Precautions
This feature is a Huawei-proprietary feature and is not supported by devices provided by

other vendors. In addition, this feature must first be activated on the BSC, MME, and
MSC, and then be activated on the eNodeB. This is because this feature is triggered by
the eNodeB and this avoids CSFB failures.
data is data that you must collect for all scenarios. 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: data sources:
operator
Required Data
The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For
MO to set the eNodeB-level handover mode and handover algorithm switches for ultra-
flash CSFB to GERAN.

Name

Algo plan GeranUltraFlashCsfbSwitch(GeranUltraFlas
switch (negotiation option.
not
required)
The following table describes the parameters that must be set in the CellHoParaCfg MO
to set the cell-level blind handover mode switches for ultra-flash CSFB to GERAN.

Name
Handover CellHoParaCfg.HoModeSwitch Network To activate cell-level blind

Mode plan handovers, select the
not option. To activate blind
required) handovers, you still need to
activate eNodeB-level blind
handovers.
The following table describes the parameter that must be set in the GeranExternalCell
MO to set the capability of external GERAN cells when some GERAN cells do not
support ultra-flash CSFB to GERAN.

Name
Ultra- GeranExternalCell.UltraFlashCsfbInd Network Clear the

Flash plan UltraFlashCsfbInd
CSFB (negotiation check box for external
capability required) GERAN cells that do not
indicator support ultra-flash CSFB
to GERAN.
The following table describes the parameter that must be set in the CellDrxPara MO to
set the DRX switch for measurements when UEs support DRX-based measurements.
DRX switch for CellDrxPara.DrxForMeasSwitch Network When the network

measurements plan supports
(negotiation measurements and
required) UEs support DRX
measurements well,
measurement
delays are
significantly
reduced and the
customer can
tolerate the impact
on services during
measurements.
To enable the DRX
switch for
measurements, set
DrxForMeasSwitch
to 1.
Long DRX CellDrxPara.LongDrxCycleForMeas Network This parameter

Cycle for plan specifies the length
Measurement (negotiation of the long DRX
required) cycle specific to
GERAN
measurement.
On Duration CellDrxPara.OnDurTimerForMeas Network This parameter

Timer for plan specifies the length
Measurement (negotiation of the On Duration
required) Timer specific to
GERAN
measurement.
DRX Inactivity CellDrxPara.DrxInactTimerForMeas Network This parameter

Measurement (negotiation of the DRX
required) Inactivity Timer
specific to GERAN
measurement.
DRX CellDrxPara.DrxReTxTimerForMeas Network This parameter

Retransmission plan specifies the length
Timer for (negotiation of the DRX
Measurement required) Retransmission
Timer specific to
GERAN
measurement.
Short DRX CellDrxPara.ShortDrxSwForMeas Network This parameter

Switch for plan specifies whether
Measurement (negotiation short-period DRX is
required) enabled for GERAN
measurements.
Short DRX CellDrxPara.ShortDrxCycleForMeas Network This parameter

Cycle for plan specifies the length
Measurement (negotiation of the short DRX
required) cycle specific to
GERAN
measurement.
Short Cycle CellDrxPara.ShortCycleTimerForMeas Network This parameter

Measurement (negotiation of the Short Cycle
required) Timer specific to
GERAN
measurement.
GLOBALPROCSWITCH MO to turn on the UE compatibility switch when UEs do not
support Ultra-Flash CSFB, resulting in UE compatibility problems.

Name
Ue GlobalProcSwitch.UeCompatSwitch Network Select the

Compatibility plan UltraFlashCsfbComOptSw
Switch (negotiation option of the parameter
required) when UEs on the network
do not support ultra-flash
CSFB.
When the MME provided by
Huawei allows IMEI
whitelist configurations for
ultra-flash CSFB and the
option is selected, the
eNodeB performs ultra-
flash CSFB on UEs in the
IMEI whitelist. Therefore,
delete the UEs that do not
support ultra-flash CSFB
from the whitelist before
selecting the option.
Name
Otherwise, keep the option

unselected.
and save the file.
set the parameters.
Table 7-55 Parameters for ultra-flash CSFB to UTRAN

Data File Group
GeranNfreqGroup GeranNfreqGroup See 7.11.5.1 The RNP template

Data sheet is
GeranNfreqGroupArfcn GeranNfreqGroupArfcn See 7.11.5.1 The RNP template

Data sheet is
GeranExternalCell GeranExternalCell See 7.11.5.1 The RNP template

Data sheet is
GeranExternalCellPlmn GeranExternalCellPlmn See 7.11.5.1 The RNP template

Data sheet is
GeranNcell GeranNcell See 7.11.5.1 The RNP template

Data sheet is
Data File Group
ENodeBAlgoSwitch User-defined sheet. See 7.11.5.1 This parameter

ENodeBAlgoSwitch is Data must be customized
of the template.
CellHoParaCfg User-defined sheet. See 7.11.5.1 This parameter

CellHoParaCfg is Data must be customized
of the template.
CSFallBackBlindHoCfg User-defined sheet. See 7.11.5.1 This parameter

CSFallBackBlindHoCfg Data must be customized
is recommended. Preparation. on a list-type sheet
of the template.
CSFallBackHo User-defined sheet. See 7.11.5.1 This parameter

CSFallBackHo is Data must be customized
of the template.
InterRatHoComm User-defined sheet. See 7.11.5.1 This parameter

InterRatHoComm is Data must be customized
of the template.
GlobalProcSwitch User-defined sheet. See 7.11.5.1 This parameter

GlobalProcSwitch is Data must be customized
of the template.
Batch Activation
following section in the CME product documentation or online help: Managing the
CME > CME Guidelines > Enhanced Feature Management > Feature Operation
and Maintenance.
Configuration.
Using MML Commands
• Basic scenario
Connected Mode.
GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the
Handover Algo switch parameter selected.
3. (Optional) Run the MOD GlobalProcSwitch command with the
IratMeasCfgTransSwitch option of the ProtocolMsgOptSwitch parameter
selected if you need to optimize "G2L Fast Return after Ultra-Flash CSFB to
UTRAN" based on the E-UTRA frequency capability supported by UEs. The
eNodeB transfers E-UTRA frequency information supported by UEs to the BSC
during the SRVCC.
4. (Optional) Run the MO GERANEXTERNALCELL command with the Ultra-
Flash CSFB capability indicator parameter set to BOOLEAN_FALSE if some
external GERAN cells do not support ultra-flash CSFB to UTRAN.
5. (Optional) Run the MOD CELLDRXPARA command with the DRX for
Measurement Switch parameter set to ON(On) if UEs support DRX-based
measurements.
Ultra-Flash CSFB is activated.
1. Run the MOD GLOBALPROCSWITCH command with the
UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw) option of the UE
Compatibility Switch parameter selected.
• Basic scenario
• MOD ENODEBALGOSWITCH: HoAlgoSwitch= GeranUltraFlashCsfbSwitch-1;
• MOD GlobalProcSwitch: ProtocolMsgOptSwitch=IratMeasCfgTransSwitch-
1;
• MOD GERANEXTERNALCELL: Mcc="302", Mnc="220", GeranCellId=2,
Lac=12, UltraFlashCsfbInd=BOOLEAN_TRUE;
MOD CELLDRXPARA: LocalCellId=0,
DrxForMeasSwitch=1;LongDrxCycleForMeas=SF160,
OnDurTimerForMeas=PSF2, DrxInactTimerForMeas=PSF2,
DrxReTxTimerForMeas=PSF4, ShortDrxSwForMeas=1,
ShortDrxCycleForMeas=SF20, ShortCycleTimerForMeas=1;

Ultra-Flash CSFB is activated.
MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;
To use signaling tracing to verify whether this feature has been activated, perform the
following steps:
1. As shown in the following figure, the HANDOVER REQUIRED message sent
from the eNodeB to the MME over the S1 interface contains handover request
cause values "cs-fallback-triggered" and "sRVCCHOIndication-cSonly (1)",
indicating that a ultra-flash CSFB to GERAN is triggered successfully.
2. The UE falls back to a GERAN cell and completes the call.
Figure 7-22 HANDOVER REQUIRED message
Counter Observation
The counter listed in the following table can be monitored to check whether the feature
has been activated.
Table 7-56 Performance counters for ultra-flash CSFB to GERAN
1526733006 L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut Number of SRVCC-based outgoing

handover attempts from E-UTRAN
to GERAN for ultra-flash CSFB to
GERAN
7.11.7 Deactivation

for Existing eNodeBs. In the procedure, modify parameters according to the following table.
Table 7-57 Parameter related to ultra-flash CSFB to GERAN

Data File Group
ENodeBAlgoSwitch User-defined sheet. HoAlgoSwitch To deactivate the Ultra-Flash

ENodeBAlgoSwitch CSFB to GERAN feature
is recommended. Deselect the
GeranUltraFlashCsfbSwitch
option.
Using MML Commands

GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the Handover
Algo switch parameter deselected.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranUltraFlashCsfbSwitch-0;
Table 7-58 lists the counters used to monitor the performance of ultra-flash CSFB to
GERAN
Table 7-58 Counters related to ultra-flash CSFB to GERAN
1526733006 L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut Number of SRVCC-based

outgoing handover attempts
from E-UTRAN to GERAN for
ultra-flash CSFB
1526733007 L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut Number of SRVCC-based

EUTRAN-to-GERAN outgoing
handover executions for ultra-

flash CSFB to to GERAN
1526733008 L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut Number of successful

SRVCC-based EUTRAN-to-
GERAN outgoing handovers
for ultra-flash CSFB to
GERAN
1526733009 L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp Number of abnormal

responses from the MME
during EUTRAN-to-GERAN
handovers for ultra-flash
CSFB to GERAN
Success rate of handovers for ultra-fast CSFB to GERAN =

(L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut -
L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp)/L.IRATHO.CSFB.SRVCC.E2G.Exe
cAttOut
This section provides engineering guidelines for LOFD-001069 CS Fallback with LAI to
GERAN.
7.12.1 When to Use CS Fallback with LAI to GERAN
Use LOFD-001069 CS Fallback with LAI to GERAN when both of the following
conditions are met:
• LOFD-001034 CS Fallback to GERAN has been enabled.
• The E-UTRAN cell has neighboring GERAN cells that belong to different PLMNs
and supports inter-PLMN handovers, or the E-UTRAN cell has neighboring
GERAN cells that have different LACs.
If both LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to
GERAN have been enabled, you are advised to enable both LOFD-001069 CS Fallback
with LAI to GERAN and LOFD-001068 CS Fallback with LAI to UTRAN.
• Collect information about whether LOFD-001034 CS Fallback to GERAN has been

activated.
core networks, and ensure that they all support CSFB and the MME supports LAI
delivery. Table 7-59 describes the requirements of CSFB with LAI to GERAN for the
core networks.
Table 7-59 Requirements of CSFB with LAI to GERAN for core networks
NE Requirement
MME Supports:
• SGs interface to the MSC
serving cell
• Combined EPS/IMSI attach,
combined EPS/IMSI detach, and
combined TAU/LAU
• SMS over SGs
• LAI delivery
MSC Supports:
• Combined EPS/IMSI attach
• SMS over SGs
• Paging message forwarding over the
SGs interface
SGSN Does not activate ISR during the

combined RAU/LAU procedure initiated by
the UE.
live network:
This information is used to configure neighboring GERAN cells and to
determine whether to perform CSFB based on handover or redirection. For
details, see Inter-RAT Mobility Management in Connected Mode.
7.12.3 Requirements
For this feature, the eNodeB must collaborate with core-network equipment. If the core-
network equipment is provided by Huawei, the version must be PS9.2 or later. If the
core-network equipment is provided by another vendor, check with the vendor whether
the equipment supports this feature. The core network must support CSFB with LAI to
GERAN.
License
Table 7-60 License information for CSFB with LAI to GERAN

ID Control Item
LOFD- CS Fallback LT1S0CSFLG00 CS Fallback eNodeB per RRC

001069 with LAI to with LAI to Connected
GERAN GERAN User
7.12.4 Precautions
None
This feature is automatically activated when two conditions are met: The license for this
feature has been purchased. CSFB to GERAN has been activated.
Data preparation for activating CSFB with LAI to GERAN is the same as that for
activating CSFB to GERAN. For details, see 7.8.5.1 Data Preparation.
For details, see 7.8.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs .
For details, see 7.8.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs .
For details, see 7.8.5.4 Using the CME to Perform Single Configuration.
For details, see 7.8.5.6 Using MML Commands.


1. Configure two neighboring GERAN cells with different LAIs for an E-UTRAN
cell, and enable the MME to include only one of the two LAIs in the instructions
that will be delivered to the eNodeB.
2. Ensure that the signal strengths of the two GERAN cells both reach the threshold
for event B1. You can query the threshold by running the LST
INTERRATHOGERANGROUP command.
3. Enable a UE to camp on the E-UTRAN cell and make a voice call.
4. Enable the UE to camp on the E-UTRAN cell and receive a voice call.
You can observe the signaling procedure for CSFB with LAI to GERAN, which is
similar to that for CSFB to GERAN described in 7.9.6 Activation Observation. The difference
is that the Initial Context Setup Request or UE Context Mod Request message carries the
LAI that the MME delivers to the eNodeB, as shown in the following figure:
Figure 7-23 LAI signaling tracing
7.12.7 Deactivation
CSFB with LAI to GERAN is automatically deactivated when its license or CSFB to
GERAN is deactivated. For details about how to deactivate CSFB to GERAN, see 7.8.7
Deactivation.
This section provides engineering guidelines for LOFD-001089 CS Fallback Steering to

GERAN.
7.13.1 When to Use CS Fallback Steering to GERAN
Use LOFD-001089 CS Fallback Steering to GERAN to improve the network efficiency

when both of the following conditions are met:
• LOFD-001034 CS Fallback to GERAN has been activated.
• An operator has multiple GERAN frequencies and has different handover policies
for CS-only services and combined CS+PS services.
If the operator owns both UTRAN and GERAN, you can also activate LOFD-001088 CS
Fallback Steering to UTRAN to improve the network efficiency.
1. Collect information about whether LOFD-001034 CS Fallback to GERAN has

been activated.
2. Collect the following information about the UEs that support GSM and LTE on the
live network:
• Whether the UEs support redirection from E-UTRAN to GERAN
• Whether the UEs support PS handover from E-UTRAN to GERAN
• Whether the UEs support CCO from E-UTRAN to GERAN
• Whether the UEs support GERAN measurements
This information is used to configure neighboring GERAN cells and to determine
whether to perform CSFB based on handover, redirection, or CCO. For details, see
Inter-RAT Mobility Management in Connected Mode Feature Parameter
Description.
3. Collect information about the frequencies and frequency policies of the GERAN.
Frequency policies must be the same for GERAN and E-UTRAN.
4. If LOFD-001088 CS Fallback Steering to UTRAN is also to be activated, consider
the UTRAN frequencies when making frequency policies.
7.13.3 Requirements
For CSFB steering to GERAN, the eNodeB must collaborate with core-network
SAE1.2 or later. If the core-network equipment is provided by another vendor, check
with the vendor whether the equipment supports this feature. The core network must
support CSFB steering to GERAN.
License
Table 7-61 License information for CSFB steering to GERAN

Control
Item
LOFD- CS Fallback LT1S0CFBSG00 CS eNodeB per RRC

001089 Steering to Fallback Connected
GERAN Steering to User
GERAN
7.13.4 Precautions
None
operator
Required Data
The required data is the same as that for CS Fallback to GERAN. For details, see 7.8.5.1
Data Preparation.
MO to enable CSFB steering to GERAN.
Name

Algo plan GeranCsfbSteeringSwitch(GeranCsfbSteeri
switch (negotiation check box under this parameter.
not
required)
CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for
RRC_CONNECTED UEs.

Name

not parameter
operator whose
RAT blind-
handover priorities
are to be set.

and specifies the
highest-priority
RAT to be
considered in blind
handovers for
CSFB.

and specifies the
second-highest-
priority RAT to be
considered in blind
handovers for
Name
CSFB. Ensure that

this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatLowestPri
parameters.

default and
specifies the low-
priority RAT to be
considered in blind
handovers for
CSFB. Ensure that
this parameter is
set to a different
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.

of the GERAN.
CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for RRC_IDLE
UEs.

Name
CSFB CSFallBackBlindHoCfg.IdleCsfbHighestPri Network Set this parameter

Highest plan based on the
Name

for Idle required) UTRAN by default
high-priority RAT to
be considered in
CSFB for UEs in
idle mode.
CSFB CSFallBackBlindHoCfg.IdleCsfbSecondPri Network Set this parameter

Second plan based on the
for Idle required) GERAN by default
second-highest-
priority RAT to be
considered in
CSFB for UEs in
idle mode. Ensure
that this parameter
value from the
InterRatHighestPri
and
InterRatLowestPri
parameters.
CSFB CSFallBackBlindHoCfg.IdleCsfbLowestPri Network Set this parameter

Lowest plan based on the
for Idle required) CDMA2000 by
UE default and
specifies the low-
priority RAT to be
considered in
CSFB for UEs in
idle mode. Ensure
that this parameter
value from the
InterRatHighestPri
and
InterRatSecondPri
parameters.
CSFallBackPolicyCfg MO to set the CSFB policy for RRC_CONNECTED UEs.

Name

CCO_HO, and
PS_HO. You are
advised to set this
parameter based
on the UE
capabilities and
network
capabilities. For
details about how
to select a CSFB
handover policy,
see 4.7 Handover
Execution.
CSFallBackPolicyCfg MO to set the CSFB policy for RRC_IDLE UEs.

Name
CSFB CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg Network Set this

handover plan parameter
policy (negotiation based on the
Configuration not network plan.
for idle ue required) The default
values are
REDIRECTION,
CCO_HO, and
PS_HO. You
are advised to
set this
parameter
based on the
UE capabilities
and network
capabilities. For
Name
details about
how to select a
CSFB handover
policy, see 4.7
Handover
Execution.
and save the file.
set the parameters.
Table 7-62 Parameters for CSFB steering to GERAN

Data File
ENodeBAlgoSwitch User-defined sheet. Handover Algo switch This

ENodeBAlgoSwitch is parameter
customized
on a list-
type sheet
of the
template.
CSFallBackBlindHoCfg User-defined sheet. CN Operator ID, This

CSFallBackBlindHoCfg Highest priority parameter
is recommended. InterRat, Second must be
Data File
priority InterRat, customized

Lowest priority on a list-
InterRat, CSFB type sheet
Highest priority of the
InterRat for Idle UE, template.
CSFB Second priority
InterRat for Idle UE,
CSFB Lowest priority
InterRat for Idle UE
CSFallBackPolicyCfg User-defined sheet. CSFB handover policy This

CSFallBackPolicyCfg Configuration, CSFB parameter
is recommended. handover policy must be
Configuration for idle customized
ue on a list-
type sheet
of the
template.
Configuration.
Using MML Commands
The configuration is just an example, and configurations on the live network can differ
from this example. For MML command settings in scenarios where the UTRAN and
GERAN cover the same area but only the GERAN provides contiguous coverage, see
7.6.5 Data Preparation and Feature Activation.
The prerequisite is that CSFB to GERAN has been activated.

GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) check box selected under
2. Run the MOD CSFALLBACKBLINDHOCFG command with the Highest
priority InterRat, Second priority InterRat, CSFB Highest priority InterRat
for Idle UE, and CSFB Second priority InterRat for Idle UE parameters to
UTRAN, GERAN, GERAN, and UTRAN, respectively.
3. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO check
box selected under the CSFB handover policy Configuration parameter and the
REDIRECTION check box selected under the CSFB handover policy
Configuration for idle ue parameter.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-1;

InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GE
RAN,IdleCsfbSecondPri=UTRAN;
1, IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
The signaling procedure is the same as that for CSFB to GERAN. After CS Fallback
Steering to GERAN is used, check whether it works as expected.
The activation observation procedure for CSFB steering to GERAN is as follows:
1. Check that the UE supports redirection-based CSFB and handover-based CSFB.
2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to
redirection and handover, respectively.
4. Observe the counters L.CSFB.E2G, L.RRCRedirection.E2G.CSFB, and
L.IRATHO.E2G.CSFB.ExecAttOut. If the values of the counters increase by 2, 1,
and 1, respectively, CSFB steering to GERAN has been activated.
If CSFB steering to UTRAN has also been activated, the activation observation
procedure is as follows:
1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.
2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs
and UTRAN as the highest-priority RAT for CSFB triggered for
RRC_CONNECTED UEs.
4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase
by 1, both CSFB steering to UTRAN and CSFB steering to GERAN have been
activated.
7.13.7 Deactivation
for Existing eNodeBs. In the procedure, modify parameters according to Table 7-63.
Table 7-63 Parameters for deactivating CSFB steering to GERAN

Data File Group
ENodeBAlgoSwitch User-defined sheet. HoAlgoSwitch Set

ENodeBAlgoSwitch GeranCsfbSteeringSwitch
is recommended. under the HoAlgoSwitch
parameter to 0.
Using MML Commands

GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) check box cleared under the
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-0;

7.14 Troubleshooting
7.14.1 CSFB Calling Procedure Failure
Fault Description
A UE performs cell reselection to an inter-RAT neighboring cell directly after initiating a

voice call in an E-UTRAN cell, and the S1 interface tracing result shows that CSFB is
not triggered.
Fault Handling
1. Create an S1 interface tracing task, use the UE to camp on the E-UTRAN cell
again, and check whether the value of the information element (IE) ePS-attach-
type-value is "combined-attach" in the traced Attach Request message.
• If so, go to 2.
• If not, replace the UE with one that supports combined EPS/IMSI attach, and
try again.
2. Check whether the traced Attach Accept message includes the IE cs-domain-not-
available.
• If it does, go to 3.
• If not, contact Huawei technical support.
3. Contact the vendors of core network NEs to ensure the following:
• Attach procedures to the CS domain are allowed according to the subscription
data on the HSS.
• The core network supports CSFB.
• The SGs interface is correctly configured.
7.14.2 eNodeB Receiving No Measurement Report
Fault Description
An eNodeB delivers an RRC Connection Reconfiguration message for measurement

control to a UE that has initiated a voice call in the LTE network, but the eNodeB does
not receive a measurement report.
Fault Handling
1. Check whether the RRC Connection Reconfiguration message contains B1-related
measurement configurations and whether the information about the inter-RAT
systems in the configuration is correct.
• If it is, go to 2
• If not, rectify the faults and try again.
2. Check whether the coverage of the inter-RAT neighboring cell is satisfactory. If the
coverage is unsatisfactory, adjust B1-related parameters or use CSFB based on
blind handovers.
For details about how to adjust B1-related parameters, see Inter-RAT Mobility
Management in Connected Mode.
7.14.3 CSFB Blind Handover Failure
Fault Description
Even when blind handovers are configured as the preferred choice according to the
operator policies, instead of triggering a blind handover for CSFB, an eNodeB delivers an
inter-RAT measurement configuration to a UE that has initiated a voice call.
Fault Handling
1. Run the LST ENODEBALGOSWITCH command and check the setting of

BlindHoSwitch under the Handover Mode Switch parameter. If BlindHoSwitch
is Off, run the MOD ENODEBALGOSWITCH command with the
BlindHoSwitch(BlindHoSwitch) check box under the Handover Mode Switch
parameter selected.
2. Run the LST CELLHOPARACFG command and check the setting of
BlindHoSwitch under the Handover Mode Switch parameter. If BlindHoSwitch
is Off, run the MOD CELLHOPARACFG command with the
BlindHoSwitch(BlindHoSwitch) check box under the Handover Mode Switch
parameter selected. In addition, check the CSFB mechanism and perform the
following:
• If CSFB to UTRAN is required, go to 3.
• If CSFB to GERAN is required, go to 4.
3. Run the LST UTRANNCELL command and check whether Blind handover
priority is 0 for a neighboring UTRAN cell that is supposed to accept incoming
blind handovers.
• If Blind handover priority is 0, blind handovers to this cell are not allowed.
In this case, run the MOD UTRANNCELL command with the Blind
handover priority parameter set to a value other than 0.
• If Blind handover priority is not 0, contact Huawei technical support.
4. Run the LST GERANNCELL command and check whether Blind handover
priority is 0 for a neighboring GERAN cell that is supposed to accept incoming
blind handovers.
• If Blind handover priority is 0, blind handovers to this cell are not allowed.
In this case, run the MOD GERANNCELL command with the Blind
handover priority parameter set to a value other than 0.
• If Blind handover priority is not 0, contact Huawei technical support.
7.14.4 CSFB Handover Failure
Fault Description
During CSFB to UTRAN procedures with the handover policy set to PS HO, the
handover preparation success rate is low.
Table 7-64 Counters related to the handover preparation success rate
1526728504 L.IRATHO.E2W.CSFB.PrepAttOut Number of CSFB-based inter-RAT

1526728505 L.IRATHO.E2W.CSFB.ExecAttOut Number of CSFB-based inter-RAT

handover execution attempts from
Fault Handling
Here uses the CSFB to UTRAN as an example to describe the fault handling procedure.
Similar counters are provided for CSFB to GERAN or to other systems.
1. View the counters listed in Table 7-65 to check the cause for the low handover
preparation success rate.
Table 7-65 Counters related to outgoing handover preparation failures
1526730076 L.IRATHO.E2W.CSFB.Prep.FailOut.MME Number of CSFB-based

outgoing handover
preparation failures from E-
UTRAN to WCDMA network
because of the MME side

causes
1526730077 L.IRATHO.E2W.CSFB.Prep.FailOut.PrepFailure Number of CSFB-based

outgoing handover
because of the response of
handover preparation failure
from WCDMA network
1526730078 L.IRATHO.E2W.CSFB.Prep.FailOut.NoReply Number of CSFB-based

outgoing handover
because of no response from
WCDMA network
2. Analyze the failure cause based on the values of the preceding counters for each
NE.
8 Parameters
Table 8-1 Parameters

MO Parameter ID MML Command Feature ID Feature
eNBRsvdPara RsvdSwPara1 MOD ENBRSVDPARA None None

LST ENBRSVDPARA
GlobalProcSwitch UeCompatSwitch MOD GLOBALPROCSWITCH None None

LST GLOBALPROCSWITCH
CellHoParaCfg HoModeSwitch MOD CELLHOPARACFG LOFD-001033 / CS Fallb

LST CELLHOPARACFG LOFD-001034 / UTRAN
TDLOFD-001033 Fallback
/ TDLOFD- GERAN
001034 Fallback
UTRAN
Fallback
GERAN
GeranExternalCell UltraFlashCsfbInd ADD GERANEXTERNALCELL LOFD-081283 / Ultra-Fla

MOD TDLOFD-081203 CSFB to
GERANEXTERNALCELL GERAN
LST GERANEXTERNALCELL
ENodeBAlgoSwitch HoAlgoSwitch MOD ENODEBALGOSWITCH LBFD-00201801 / Coverag

LST ENODEBALGOSWITCH TDLBFD- Based In
00201801 frequenc
LBFD-00201802 / Handove
TDLBFD- Distance
00201802 Based In
LBFD-00201804 / frequenc
TDLBFD- Handove
00201804 Service
LBFD-00201805 / Inter-
TDLBFD- frequenc
00201805 Handove
LOFD-001033 / CS Fallb
TDLOFD-001033 UTRAN
TDLOFD-001034 GERAN
TDLOFD-001035 CDMA20
LOFD-001052 / 1xRTT
TDLOFD-001052 Flash CS
LOFD-001053 / Fallback
TDLOFD-001053 UTRAN
LOFD-001088 / Flash CS
GERAN
LOFD-001089 /
TDLOFD-001089 CS Fallb
Steering
LOFD-001090 / UTRAN
TDLOFD-001090
CS Fallb
LOFD-001019 / Steering
TDLOFD-001019 GERAN
LOFD-001020 / Enhance
LOFD-001043 / CDMA20
TDLOFD-001043 1xRTT
LOFD-001046 / PS Inter
TDLOFD-001046 Mobility
LOFD-001072 / between
TDLOFD-001072 UTRAN
LOFD-001073 / UTRAN
TDLOFD-001073
TDLBFD-002018 PS Inter
TDLOFD-070228 between
UTRAN
LOFD-081283 / GERAN
TDLOFD-081203
Service
LOFD-070202 / inter-RA
TDLOFD-070202
handove
TDLOFD-081223 UTRAN
Service
inter-RA
handove
GERAN
Distance
based in
RAT han
to UTRA
Distance
based in
RAT han
to GERA
Mobility
Manage
Coverag
Based In
frequenc
Handove
SRVCC
UTRAN
Service-
Request
Based In
frequenc
Handove
Ultra-Fla
CSFB to
GERAN
Ultra-Fla
CSFB to
UTRAN
Ultra-Fla
CSFB to
UTRAN
CSFallBackBlindHoCfg UtranCsfbBlindRedirRrSw MOD LOFD- CS Fallb

CSFALLBACKBLINDHOCFG 001033/TDLOFD- UTRAN
LST 001033
CSFALLBACKBLINDHOCFG Flash CS
LOFD- Fallback
001052/TDLOFD- UTRAN
001052
CellDrxPara DrxForMeasSwitch MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

LST CELLDRXPARA TDLOFD-081203 CS Fallb
GERAN
ENodeBAlgoSwitch HoModeSwitch MOD ENODEBALGOSWITCH LOFD-001022 / SRVCC

LST ENODEBALGOSWITCH TDLOFD-001022 UTRAN
LOFD-001023 / SRVCC
TDLOFD-001023 GERAN
TDLOFD-001033 UTRAN
TDLOFD-001034 GERAN
LOFD-001019 / PS Inter
TDLOFD-001020 UTRAN
LOFD-001021 / UTRAN
TDLOFD-001021 PS Inter
between
TDLOFD-001088 UTRAN
TDLOFD-001043 GERAN
UTRAN
CDMA20
Flash CS
Fallback
UTRAN
CS Fallb
Steering
UTRAN
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
Service
Inter-RA
handove
GERAN
Distance
based In
RAT han
to GERA
UtranNFreq ConnFreqPriority ADD UTRANNFREQ LOFD-001019 / PS Inter

MOD UTRANNFREQ TDLOFD-001019 Mobility
LST UTRANNFREQ TDLBFD- between
00201803 UTRAN
TDLOFD-001022 UTRAN
TDLOFD-001033 Cell Sele
and Re-
TDLOFD-001052 selection
TDLOFD-001043
SRVCC
TDLOFD-001072 UTRAN
UTRAN
Flash CS
Fallback
UTRAN
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
E-UTRA
UTRAN
CS/PS
steering
ENodeBAlgoSwitch NCellRankingSwitch MOD ENODEBALGOSWITCH LOFD- Inter-RA

LST ENODEBALGOSWITCH 002002/TDLOFD- ANR
002002 SRVCC
LOFD- UTRAN
001022/TDLOFD- CS Fallb
001022 UTRAN
LOFD- Flash CS
001033/TDLOFD- Fallback
001033 UTRAN
LOFD- Flash CS
001052 GERAN
LOFD- PS Inter
001053/TDLOFD- Mobility
001053 between
LOFD- UTRAN
001019 Service
LOFD- inter-RA
001043/TDLOFD- handove
001043 UTRAN
LOFD- Distance
001072/TDLOFD- based in
001072 RAT han
to UTRA
UtranNCell NCellMeasPriority ADD UTRANNCELL LOFD- Inter-RA

LST UTRANNCELL 002002/TDLOFD- ANR
002002 SRVCC
LOFD- UTRAN
001022/TDLOFD- CS Fallb
001022 UTRAN
LOFD- Flash CS
001033 UTRAN
LOFD- PS Inter
001052 between
LOFD- UTRAN
001019 Service
inter-RA
LOFD- handove
001043 Distance
LOFD- based in
001072/TDLOFD- RAT han
001072 to UTRA
UtranNCell CellMeasPriority ADD UTRANNCELL LOFD-001019 PS Inter

MOD UTRANNCELL TDLOFD-001022 Mobility
LST UTRANNCELL between
TDLOFD-001033
UTRAN
TDLOFD-001052 UTRAN
TDLOFD-001019
SRVCC
TDLOFD-001043 UTRAN
TDLOFD-001078 UTRAN
Flash CS
Fallback
UTRAN
PS Inter
Mobility
between
UTRAN
UTRAN
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
E-UTRA
UTRAN
CS/PS
steering
CellUeMeasControlCfg MaxUtranFddMeasFreqNum MOD LOFD-001019 / PS Inter

CELLUEMEASCONTROLCFG TDLOFD-001019 Mobility
LST between
CELLUEMEASCONTROLCFG LOFD-001022 /
TDLOFD-001022 UTRAN
LOFD-001043 / UTRAN
TDLOFD-001043 SRVCC
LOFD-001072 / UTRAN
TDLOFD-001072 Service
Inter-RA
LOFD-001033 / handove
TDLOFD-001033 UTRAN
Distance
based In
RAT han
to UTRA
CS Fallb
UTRAN
CellUeMeasControlCfg MaxUtranTddMeasFreqNum MOD LOFD-001019 / PS Inter

CELLUEMEASCONTROLCFG TDLOFD-001019 Mobility
LST between
CELLUEMEASCONTROLCFG LOFD-001022 /
TDLOFD-001022 UTRAN
LOFD-001043 / UTRAN
TDLOFD-001043 SRVCC
LOFD-001072 / UTRAN
TDLOFD-001072 Service
LOFD-001033 / Inter-RA
TDLOFD-001033 handove
UTRAN
Distance
based In
RAT han
to UTRA
CS Fallb
UTRAN
CSFallBackHo CsfbHoUtranB1ThdRscp MOD CSFALLBACKHO LOFD-001033 / CS Fallb

LST CSFALLBACKHO TDLOFD-001033 UTRAN
InterRatHoComm InterRatHoUtranB1MeasQuan MOD INTERRATHOCOMM LOFD-001019 / PS Inter

LST INTERRATHOCOMM TDLOFD-001019 Mobility
TDLOFD-001022 UTRAN
LOFD-001033 / UTRAN
TDLOFD-001033
SRVCC
UTRAN
CS Fallb
UTRAN
CSFallBackHo CsfbHoUtranB1ThdEcn0 MOD CSFALLBACKHO LOFD-001033 / CS Fallb

CSFallBackHo CsfbHoUtranTimeToTrig MOD CSFALLBACKHO LOFD-001033 / CS Fallb

CSFallBackHo BlindHoA1ThdRsrp MOD CSFALLBACKHO LOFD-001052 / Flash CS

LST CSFALLBACKHO TDLOFD-001052 Fallback
LOFD-001053 / UTRAN
Fallback
GERAN
CSFallBackBlindHoCfg InterRatHighestPri MOD LOFD-001033 / CS Fallb

CSFALLBACKBLINDHOCFG TDLOFD-001033 UTRAN
LST
CSFALLBACKBLINDHOCFG LOFD-001034 / CS Fallb
TDLOFD-001034 GERAN
LOFD-001019 / 1xRTT
LOFD-001020 / Mobility
LOFD-001021 UTRAN
UTRAN
TDLOFD-001052
PS Inter
TDLOFD-001043 UTRAN
TDLOFD-001072 GERAN
between
UTRAN
CDMA20
Flash CS
Fallback
UTRAN
Flash CS
Fallback
GERAN
Enhance
Fallback
CDMA20
1xRTT
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
Service
Inter-RA
handove
GERAN
Distance
based In
RAT han
to GERA
CSFallBackBlindHoCfg InterRatSecondPri MOD LOFD-001033 / CS Fallb

LST
TDLOFD-001034 GERAN
LOFD-001019 / 1xRTT
LOFD-001021 UTRAN
UTRAN
TDLOFD-001052
PS Inter
TDLOFD-001043 UTRAN
TDLOFD-001072 GERAN
between
UTRAN
CDMA20
Flash CS
Fallback
UTRAN
Flash CS
Fallback
GERAN
Enhance
Fallback
CDMA20
1xRTT
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
Service
Inter-RA
handove
GERAN
Distance
based In
RAT han
to GERA
CSFallBackBlindHoCfg InterRatLowestPri MOD LOFD-001033 / CS Fallb

LST
TDLOFD-001034 GERAN
LOFD-001019 / 1xRTT
LOFD-001021 UTRAN
UTRAN
TDLOFD-001052
PS Inter
TDLOFD-001043 UTRAN
TDLOFD-001072 GERAN
Mobility
UTRAN
CDMA20
Flash CS
Fallback
UTRAN
Flash CS
Fallback
GERAN
Enhance
Fallback
CDMA20
1xRTT
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
Service
Inter-RA
handove
GERAN
Distance
based In
RAT han
to GERA
UtranNCell BlindHoPriority ADD UTRANNCELL LOFD-001019 PS Inter

MOD UTRANNCELL TDLOFD-001022 Mobility
LST UTRANNCELL between
TDLOFD-001033
UTRAN
TDLOFD-001052 UTRAN
TDLOFD-001019 SRVCC
TDLOFD-001043 UTRAN
TDLOFD-001078 UTRAN
Flash CS
Fallback
UTRAN
PS Inter
Mobility
between
UTRAN
UTRAN
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
E-UTRA
UTRAN
CS/PS
steering
ENodeBAlgoSwitch FreqLayerSwtich MOD ENODEBALGOSWITCH LOFD-001087 SRVCC

LST ENODEBALGOSWITCH LOFD-001078 / Flexible
TDLOFD-001078 Steering
TDLOFD-001022 UTRAN
TDLOFD-001033 E-UTRA
UTRAN
TDLOFD-001052 CS/PS
SRVCC
UTRAN
CS Fallb
UTRAN
Flash CS
Fallback
UTRAN
CS Fallb
Steering
UTRAN
UtranNFreq CsPriority ADD UTRANNFREQ LOFD-001078 / E-UTRA

MOD UTRANNFREQ TDLOFD-001078 UTRAN
LST UTRANNFREQ TDLOFD-001033 CS/PS
UTRAN
Flash CS
Fallback
UTRAN
CS Fallb
Steering
UTRAN
CSFallBackBlindHoCfg IdleCsfbHighestPri MOD LOFD-001035 / CS Fallb

CSFALLBACKBLINDHOCFG TDLOFD-001035 CDMA20
LST 1xRTT
CSFALLBACKBLINDHOCFG LOFD-001088 /
TDLOFD-001089 UTRAN
Steering
GERAN
Enhance
Fallback
CDMA20
1xRTT
CSFallBackBlindHoCfg IdleCsfbSecondPri MOD LOFD-001035 / CS Fallb

LST 1xRTT
TDLOFD-001089 UTRAN
Steering
GERAN
Enhance
Fallback
CDMA20
1xRTT
CSFallBackBlindHoCfg IdleCsfbLowestPri MOD LOFD-001035 / CS Fallb

LST 1xRTT
TDLOFD-001089 UTRAN
Steering
GERAN
Enhance
Fallback
CDMA20
1xRTT
CSFallBackPolicyCfg IdleModeCsfbHoPolicyCfg MOD LOFD-001088 / CS Fallb

CSFALLBACKPOLICYCFG TDLOFD-001088 Steering
LST UTRAN
CSFALLBACKPOLICYCFG LOFD-001089 /
Steering
GERAN
UtranNFreq CsPsMixedPriority ADD UTRANNFREQ LOFD-001088 / CS Fallb

MOD UTRANNFREQ TDLOFD-001088 Steering
LST UTRANNFREQ LOFD-001019 / UTRAN
UTRAN
TDLOFD-001078 UTRAN
CS Fallb
UTRAN
Flash CS
Fallback
UTRAN
E-UTRA
UTRAN
CS/PS
steering
CSFallBackPolicyCfg CsfbHoPolicyCfg MOD LOFD-001033 / CS Fallb

CSFALLBACKPOLICYCFG TDLOFD-001033 UTRAN
LST
CSFALLBACKPOLICYCFG LOFD-001034 / CS Fallb
TDLOFD-001034 GERAN
LOFD-001089 / UTRAN
Steering
GERAN
InterRatHoComm CellInfoMaxUtranCellNum MOD INTERRATHOCOMM LOFD-001019 / PS Inter

UTRAN
UTRAN
Flash CS
Fallback
UTRAN
CSFallBackHo CsfbProtectionTimer MOD CSFALLBACKHO LOFD-001033 / CS Fallb

TDLOFD-001034 GERAN
LOFD-001033 / Enhance
CDMA20
1xRTT
InterRatHoComm UtranCellNumForEmcRedirect MOD INTERRATHOCOMM LOFD-001033 / CS Fallb

LST INTERRATHOCOMM TDLOFD-001033 UTRAN
Fallback
UTRAN
ENodeBAlgoSwitch MultiOpCtrlSwitch MOD ENODEBALGOSWITCH LOFD-001022 SRVCC

LST ENODEBALGOSWITCH LOFD-001087 UTRAN
LOFD-001033 SRVCC
LOFD-001052 Flexible
LOFD-001068 Steering
LOFD-001088 UTRAN
LOFD-001019 CS Fallb
LOFD-001043 UTRAN
LOFD-001072 Flash CS
Fallback
LOFD-001078 UTRAN
CS Fallb
with LAI
UTRAN
CS Fallb
Steering
UTRAN
PS Inter
Mobility
between
UTRAN
UTRAN
Service
inter-RA
Distance
based In
RAT han
to UTRA
E-UTRA
UTRAN
CS/PS
Steering
UtranNetworkCapCfg NetworkCapCfg ADD LOFD-001022 / SRVCC

UTRANNETWORKCAPCFG TDLOFD-001022 UTRAN
MOD
UTRANNETWORKCAPCFG LOFD-001033 / CS Fallb
LST TDLOFD-001033 UTRAN
UTRANNETWORKCAPCFG LOFD-001052 / Flash CS
LOFD-001068 / UTRAN
LOFD-001088 / with LAI
TDLOFD-001088 UTRAN
LOFD-001043 / UTRAN
LOFD-081283 / UTRAN
TDLOFD-081203 UTRAN
LOFD-070202 / Service
TDLOFD-081223 inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
Ultra-Fla
CSFB to
GERAN
Ultra-Fla
CSFB to
UTRAN
CSFallBackPolicyCfg CsfbUserArpCfgSwitch MOD LBFD-002023 Admissio

CSFALLBACKPOLICYCFG /TDLBFD-002023 Control
LST
CSFALLBACKPOLICYCFG
CSFallBackPolicyCfg NormalCsfbUserArp MOD LBFD-002023 Admissio

CSFALLBACKPOLICYCFG /TDLBFD-002023 Control
LST
CSFALLBACKPOLICYCFG
GlobalProcSwitch UtranLoadTransChan MOD GLOBALPROCSWITCH None None

LST GLOBALPROCSWITCH
ENodeBAlgoSwitch RimOnEcoSwitch MOD ENODEBALGOSWITCH MRFD-090211 eCoordin

LST ENODEBALGOSWITCH LOFD- based R
001052/TDLOFD- process
001052 optimiza
LOFD- Flash CS
001019 UTRAN
LOFD- PS Inter
001044 between
LOFD- UTRAN
001033 Inter-RA
Load Sh
to
UTRAN(
on UMTS
load
informat
CS Fallb
UTRAN
(based o
UMTS c
load
informat
ENodeBAlgoSwitch RimSwitch MOD ENODEBALGOSWITCH LOFD-001034 / CS Fallb

LST ENODEBALGOSWITCH TDLOFD-001034 GERAN
LOFD-001052 / Flash CS
LOFD-001053 / UTRAN
Fallback
GERAN
GeranNfreqGroup ConnFreqPriority ADD GERANNFREQGROUP LOFD-001020 / PS Inter

MOD GERANNFREQGROUP TDLOFD-001020 Mobility
LST GERANNFREQGROUP TDLOFD-001023 between
TDLOFD-001034 UTRAN
GERAN
TDLOFD-001053
SRVCC
GERAN
CS Fallb
GERAN
Flash CS
Fallback
GERAN
GeranNcell BlindHoPriority ADD GERANNCELL LOFD-001020 / PS Inter

MOD GERANNCELL TDLOFD-001020 Mobility
LST GERANNCELL TDLOFD-001023 between
TDLOFD-001034 UTRAN
GERAN
TDLOFD-001053
SRVCC
GERAN
CS Fallb
GERAN
Flash CS
Fallback
GERAN
InterRatHoComm CellInfoMaxGeranCellNum MOD INTERRATHOCOMM LOFD-001020 / PS Inter

UTRAN
GERAN
Flash CS
Fallback
GERAN
UtranExternalCell Rac ADD UTRANEXTERNALCELL LOFD-001019 / PS Inter

MOD TDLOFD-001019 Mobility
UTRANEXTERNALCELL between
LOFD-001034 /
LST UTRANEXTERNALCELL UTRAN
TDLOFD-001034
UTRAN
TDLOFD-001052 GERAN
TDLOFD-001072 UTRAN
UTRAN
Service
Inter-RA
handove
UTRAN
Distance
based In
RAT han
to UTRA
E-UTRA
UTRAN
CS/PS
steering
CSFallBackBlindHoCfg CnOperatorId LST LOFD-001033 / CS Fallb

MOD
TDLOFD-001034 GERAN
TDLOFD-001035 UTRAN
Fallback
GERAN
CS Fallb
CDMA20
1xRTT
Enhance
Fallback
CDMA20
1xRTT
CSFallBackBlindHoCfg UtranLcsCap MOD LOFD-001033 / CS Fallb

LST
CSFALLBACKBLINDHOCFG
CSFallBackHo LocalCellId LST CSFALLBACKHO None None

MOD CSFALLBACKHO
S1Interface MmeRelease ADD S1INTERFACE LBFD-00300101 / Star Top

MOD S1INTERFACE TDLBFD- Chain
DSP S1INTERFACE 00300101 Topolog
LBFD-00300102 / Tree Top
TDLBFD- 3GPP R
00300102 Specifica
LBFD-00300103 /
TDLBFD-
00300103
LBFD-001008 /
TDLBFD-070111
GeranExternalCell Rac ADD GERANEXTERNALCELL LOFD-001034 / CS Fallb

MOD LOFD-001034 GERAN
GERANEXTERNALCELL
LOFD-001053 Flash CS
LST GERANEXTERNALCELL
LOFD-001020 / Fallback
TDLOFD-001020 GERAN
PS Inter
Mobility
between
UTRAN
GERAN
CSFallBackBlindHoCfg GeranLcsCap MOD LOFD-001034 / CS Fallb

CSFALLBACKBLINDHOCFG TDLOFD-001034 GERAN
LST
CSFALLBACKBLINDHOCFG
InterRatHoComm GeranCellNumForEmcRedirect MOD INTERRATHOCOMM LOFD-001034 / CS Fallb

LST INTERRATHOCOMM TDLOFD-001034 GERAN
CSFallBackHo CsfbHoGeranB1Thd MOD CSFALLBACKHO LOFD-001034 / CS Fall B

LST CSFALLBACKHO TDLOFD-001034 to GERA
CSFallBackHo CsfbHoGeranTimeToTrig MOD CSFALLBACKHO LOFD-001034 / CS Fall B

LST CSFALLBACKHO TDLOFD-001034 to GERA
CellDrxPara LongDrxCycleForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
CellDrxPara OnDurTimerForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
CellDrxPara DrxInactTimerForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
CellDrxPara DrxReTxTimerForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
CellDrxPara ShortDrxSwForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
CellDrxPara ShortDrxCycleForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
CellDrxPara ShortCycleTimerForMeas MOD CELLDRXPARA LOFD-081283 / Ultra-Fla

GERAN
9 Counters
Table 9-1 Counters

Counter ID Counter Name Counter Feature Feature
Description ID Name
1526726992 L.IRATHO.E2G.PrepAttOut Number of Multi- PS Inter-

inter-RAT mode: RAT
handover None Mobility
attempts between E-
Description ID Name
from E- GSM: UTRAN

UTRAN to None and
GERAN UMTS: GERAN
None SRVCC to
LTE: GERAN
LOFD- CS
001020 Fallback to
LOFD- GERAN
001023 PS Inter-
LOFD- RAT
001034 Mobility
TDLOFD- between E-
001020 UTRAN
and
TDLOFD- GERAN
001023
SRVCC to
TDLOFD- GERAN
001034
CS
Fallback to
GERAN
1526726993 L.IRATHO.E2G.ExecAttOut Number of Multi- PS Inter-

inter-RAT mode: RAT
executions GSM: between E-
from E- None UTRAN
UTRAN to UMTS: and
GERAN None GERAN
LTE: SRVCC to
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
CS
Fallback to
GERAN
Description ID Name
1526726994 L.IRATHO.E2G.ExecSuccOut Number of Multi- PS Inter-

successful mode: RAT
inter-RAT None Mobility
handovers GSM: between E-
from E- None UTRAN
UTRAN to UMTS: and
GERAN None GERAN
LTE: SRVCC to
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
CS
Fallback to
GERAN
1526728306 L.IRATHO.E2G.Prep.FailOut.MME Number of Multi- CS

inter-RAT mode: Fallback to
handover None GERAN
preparation GSM: CS
failures from None Fallback to
E-UTRAN to UMTS: GERAN
GERAN None PS Inter-
because of RAT
faults on the LTE:
LOFD- Mobility
MME side between E-
001034
TDLOFD- UTRAN
001034 and
GERAN
LOFD-
001020 PS Inter-
RAT
TDLOFD- Mobility
001020 between E-
LOFD- UTRAN
001046 and
GERAN
Description ID Name
TDLOFD- Service
001046 based
LOFD- inter-RAT
001073 handover
LOFD- to GERAN
001023 Service
TDLOFD- based
001023 Inter-RAT
handover
to GERAN
Distance
based
Inter-RAT
handover
to GERAN
SRVCC to
GERAN
SRVCC to
GERAN
1526728307 L.IRATHO.E2G.Prep.FailOut.NoReply Number of Multi- CS

handover None GERAN
preparation GSM: CS
GERAN None PS Inter-
because of RAT
LTE:
no Mobility
responses LOFD-
001034 between E-
from UTRAN
GERAN TDLOFD-
001034 and
GERAN
LOFD-
001020 PS Inter-
RAT
TDLOFD- Mobility
001020 between E-
LOFD- UTRAN
001046 and
TDLOFD- GERAN
001046 Service
LOFD- based
001073 inter-RAT
LOFD- handover
001023 to GERAN
Description ID Name
TDLOFD- Service
001023 based
Inter-RAT
handover
to GERAN
Distance
based
Inter-RAT
handover
to GERAN
SRVCC to
GERAN
SRVCC to
GERAN
1526728308 L.IRATHO.E2G.Prep.FailOut.PrepFailure Number of Multi- CS

handover None GERAN
preparation GSM: CS
GERAN due None PS Inter-
tobecause RAT
LTE:
GERAN Mobility
cells send LOFD-
001034 between E-
handover UTRAN
preparation TDLOFD-
001034 and
failure GERAN
messages LOFD-
001020 PS Inter-
RAT
TDLOFD- Mobility
001020 between E-
LOFD- UTRAN
001046 and
TDLOFD- GERAN
001046 Service
LOFD- based
001073 inter-RAT
LOFD- handover
001023 to GERAN
TDLOFD- Service
001023 based
Inter-RAT
handover
to GERAN
Description ID Name
Distance
based
Inter-RAT
handover
to GERAN
SRVCC to
GERAN
SRVCC to
GERAN
1526728309 L.IRATHO.E2T.Prep.FailOut.MME Number of Multi- CS

handover None UTRAN
preparation GSM: CS
E-UTRAN to UMTS: UTRAN
TD-SCDMA None PS Inter-
network RAT
LTE:
because of Mobility
faults on the LOFD-
001033 between E-
MME side UTRAN
TDLOFD-
001033 and
UTRAN
LOFD-
001019 PS Inter-
RAT
TDLOFD- Mobility
001019 between E-
LOFD- UTRAN
001043 and
TDLOFD- UTRAN
001043 Service
LOFD- based
001072 inter-RAT
LOFD- handover
001022 to UTRAN
TDLOFD- Service
001022 based
Inter-RAT
handover
to UTRAN
Distance
based
Inter-RAT
handover
to UTRAN
Description ID Name
SRVCC to
UTRAN
SRVCC to
UTRAN
1526728310 L.IRATHO.E2T.Prep.FailOut.NoReply Number of Multi- CS

handover None UTRAN
preparation GSM: CS
E-UTRAN to UMTS: UTRAN
network due RAT
LTE:
tobecause Mobility
of no LOFD-
001033 between E-
responses UTRAN
from TD- TDLOFD-
001033 and
SCDMA UTRAN
network LOFD-
001019 PS Inter-
RAT
TDLOFD- Mobility
001019 between E-
LOFD- UTRAN
001043 and
TDLOFD- UTRAN
001043 Service
LOFD- based
001072 inter-RAT
LOFD- handover
001022 to UTRAN
TDLOFD- Service
001022 based
Inter-RAT
handover
to UTRAN
Distance
based
Inter-RAT
handover
to UTRAN
SRVCC to
UTRAN
SRVCC to
UTRAN
Description ID Name
1526728311 L.IRATHO.E2T.Prep.FailOut.PrepFailure Number of Multi- CS

handover None UTRAN
preparation GSM: CS
failures None Fallback to
because UMTS: UTRAN
network RAT
cells send LTE:
LOFD- Mobility
handover between E-
preparation 001033
TDLOFD- UTRAN
failure and
messages 001033
UTRAN
LOFD-
001019 PS Inter-
RAT
TDLOFD- Mobility
001019 between E-
LOFD- UTRAN
001043 and
TDLOFD- UTRAN
001043 Service
LOFD- based
001072 inter-RAT
LOFD- handover
001022 to UTRAN
TDLOFD- Service
001022 based
Inter-RAT
handover
to UTRAN
Distance
based
Inter-RAT
handover
to UTRAN
SRVCC to
UTRAN
SRVCC to
UTRAN
1526728312 L.IRATHO.BlindHO.E2W.ExecAttOut Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
executions None UTRAN
Description ID Name
from E- UMTS: and

UTRAN to None UTRAN
WCDMA LTE: SRVCC to
network LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
TDLOFD- Mobility
001019 between E-
TDLOFD- UTRAN
001022 and
UTRAN
TDLOFD-
001033 SRVCC to
UTRAN
CS
Fallback to
UTRAN
1526728313 L.IRATHO.BlindHO.E2W.ExecSuccOut Number of Multi- PS Inter-

blind GSM: between E-
handovers None UTRAN
from E- UMTS: and
UTRAN to None UTRAN
WCDMA SRVCC to
LTE:
network UTRAN
LOFD-
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
Description ID Name
1526728314 L.IRATHO.BlindHO.E2G.ExecAttOut Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
from E- UMTS: and
UTRAN to None GERAN
GERAN SRVCC to
LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
CS
Fallback to
GERAN
1526728315 L.IRATHO.BlindHO.E2G.ExecSuccOut Number of Multi- PS Inter-

from E- UMTS: and
UTRAN to None GERAN
GERAN SRVCC to
LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
Description ID Name
TDLOFD- SRVCC to
001034 GERAN
CS
Fallback to
GERAN
1526728321 L.CSFB.PrepAtt Number of Multi- CS

CSFB mode: Fallback to
indicators None UTRAN
received by GSM: CS
the eNodeB None Fallback to
UMTS: UTRAN
None CS
LTE: Fallback to
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD- CS
001035 Fallback to
CDMA2000
TDLOFD- 1xRTT
001035
1526728322 L.CSFB.PrepSucc Number of Multi- CS

successful mode: Fallback to
CSFB None UTRAN
responses GSM: CS
from the None Fallback to
eNodeB UMTS: UTRAN
None CS
LTE: Fallback to
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
Description ID Name
LOFD- CS
001035 Fallback to
TDLOFD- CDMA2000
001035 1xRTT
1526728323 L.CSFB.E2W Number of Multi- CS

procedures mode: Fallback to
for CSFB to None UTRAN
WCDMA GSM: CS
network None Fallback to
UMTS: UTRAN
None Ultra-Flash
LTE: CSFB to
LOFD- UTRAN
001033 Ultra-Flash
TDLOFD- CSFB to
001033 UTRAN
LOFD-
070202
TDLOFD-
081223
1526728324 L.CSFB.E2G Number of Multi- CS

for CSFB to None GERAN
GERAN GSM: CS
None Fallback to
UMTS: GERAN
None
LTE:
LOFD-
001034
TDLOFD-
001034
1526728326 L.RRCRedirection.E2W Number of Multi- PS Inter-

redirections mode: RAT
from E- None Mobility
UTRAN to GSM: between E-
WCDMA None UTRAN
network UMTS: and
None UTRAN
CS
Fallback to
UTRAN
Description ID Name
LTE: PS Inter-
LOFD- RAT
001019 Mobility
LOFD- between E-
001033 UTRAN
TDLOFD- and
001019 UTRAN
TDLOFD- CS
001033 Fallback to
UTRAN
1526728327 L.RRCRedirection.E2G Number of Multi- PS Inter-

GERAN None UTRAN
UMTS: and
None GERAN
LTE: CS
LOFD- Fallback to
001020 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001034 GERAN
CS
Fallback to
GERAN
1526728328 L.IRATHO.BlindHO.E2W.PrepAttOut Number of Multi- CS

blind None UTRAN
handover GSM: CS
attempts None Fallback to
from E- UMTS: UTRAN
UTRAN to None PS Inter-
WCDMA RAT
network LTE:
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001033 and
UTRAN
Description ID Name
LOFD- PS Inter-
001019 RAT
TDLOFD- Mobility
001019 between E-
UTRAN
and
UTRAN
1526728329 L.IRATHO.BlindHO.E2G.PrepAttOut Number of Multi- CS

blind None GERAN
handover GSM: CS
from E- UMTS: GERAN
GERAN RAT
LTE:
LOFD- Mobility
001034 between E-
TDLOFD- UTRAN
001034 and
GERAN
LOFD-
001020 PS Inter-
RAT
TDLOFD-
Mobility
001020 between E-
UTRAN
and
GERAN
1526728330 L.RRCRedirection.E2W.PrepAtt Number of Multi- PS Inter-

redirection mode: RAT
preparations None Mobility
from E- GSM: between E-
UTRAN to None UTRAN
WCDMA UMTS: and
network None UTRAN
LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001033 UTRAN
Description ID Name
CS
Fallback to
UTRAN
1526728331 L.RRCRedirection.E2G.PrepAtt Number of Multi- PS Inter-

UTRAN to None UTRAN
GERAN UMTS: and
None GERAN
LTE: CS
LOFD- Fallback to
001020 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020
UTRAN
TDLOFD- and
001034 GERAN
CS
Fallback to
GERAN
1526728380 L.IRATHO.E2G.PrepAttOut.PLMN Number of Multi- PS Inter-

inter-RAT mode: RAT
attempts GSM: between E-
from E- None UTRAN
UTRAN to UMTS: and
GERAN for None GERAN
a specific SRVCC to
operator LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
Description ID Name
LOFD- CS
001036 Fallback to
LOFD- GERAN
001037 RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728381 L.IRATHO.E2G.ExecAttOut.PLMN Number of Multi- PS Inter-

inter-RAT mode: RAT
from E- None UTRAN
UTRAN to UMTS: and
a specific SRVCC to
operator LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD-
001023
Description ID Name
TDLOFD- and
001034 GERAN
LOFD- SRVCC to
001036 GERAN
LOFD- CS
001037 Fallback to
TDLOFD- GERAN
001036 RAN
TDLOFD- Sharing
001037 with
LOFD- Common
070206 Carrier
RAN
Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728382 L.IRATHO.E2G.ExecSuccOut.PLMN Number of Multi- PS Inter-

from E- None UTRAN
UTRAN to UMTS: and
a specific SRVCC to
operator LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Description ID Name
TDLOFD- Mobility
001020 between E-
TDLOFD- UTRAN
001023 and
TDLOFD- GERAN
001034 SRVCC to
LOFD- GERAN
001036 CS
LOFD- Fallback to
001037 GERAN
TDLOFD- RAN
001036 Sharing
with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728386 L.CSFB.PrepAtt.Idle Number of Multi- CS

received by GSM: CS
for UEs in UMTS: UTRAN
idle mode None CS
LTE: Fallback to
LOFD- GERAN
001033
Description ID Name
TDLOFD- CS
001033 Fallback to
LOFD- GERAN
001034 CS
TDLOFD- Fallback to
001034 CDMA2000
LOFD- 1xRTT
001035 CS
TDLOFD- Fallback to
001035 CDMA2000
1xRTT
1526728387 L.CSFB.PrepSucc.Idle Number of Multi- CS

CSFB None UTRAN
responses GSM: CS
from the None Fallback to
eNodeB for UMTS: UTRAN
UEs in idle None CS
mode Fallback to
LTE:
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD- CS
001035 Fallback to
CDMA2000
TDLOFD- 1xRTT
001035
1526728388 L.CSFB.E2W.Idle Number of Multi- CS

WCDMA GSM: CS
network for None Fallback to
UEs in idle UMTS: UTRAN
mode None Ultra-Flash
LTE: CSFB to
LOFD- UTRAN
001033
Description ID Name
TDLOFD- Ultra-Flash
001033 CSFB to
LOFD- UTRAN
070202
TDLOFD-
081223
1526728389 L.IRATHO.BlindHO.E2W.PrepAttOut.PLMN Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
handover GSM: between E-
attempts None UTRAN
from E- UMTS: and
UTRAN to None UTRAN
WCDMA SRVCC to
network for LTE:
LOFD- UTRAN
a specific CS
operator 001019
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019
UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
LOFD- CS
001036 Fallback to
LOFD- UTRAN
001037 RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Description ID Name
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728390 L.IRATHO.BlindHO.E2G.PrepAttOut.PLMN Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
attempts None UTRAN
from E- UMTS: and
UTRAN to None GERAN
GERAN for SRVCC to
a specific LTE:
LOFD- GERAN
operator CS
001020
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
LOFD- CS
001036 Fallback to
LOFD- GERAN
001037 RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
Description ID Name
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728391 L.IRATHO.BlindHO.E2W.ExecAttOut.PLMN Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
from E- UMTS: and
UTRAN to None UTRAN
WCDMA SRVCC to
network for LTE:
LOFD- UTRAN
a specific CS
operator 001019
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
LOFD- CS
001036 Fallback to
LOFD- UTRAN
001037 RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
Description ID Name
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728392 L.IRATHO.BlindHO.E2W.ExecSuccOut.PLMN Number of Multi- PS Inter-

handover None UTRAN
executions UMTS: and
from E- None UTRAN
UTRAN to SRVCC to
WCDMA LTE:
LOFD- UTRAN
network for CS
a specific 001019
LOFD- Fallback to
operator UTRAN
001022
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
LOFD- CS
001036 Fallback to
LOFD- UTRAN
001037 RAN
TDLOFD- Sharing
001036 with
Description ID Name
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728393 L.IRATHO.BlindHO.E2G.ExecAttOut.PLMN Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
from E- UMTS: and
UTRAN to None GERAN
GERAN for SRVCC to
a specific LTE:
LOFD- GERAN
operator CS
001020
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
LOFD- CS
001036 Fallback to
GERAN
Description ID Name
LOFD- RAN
001037 Sharing
TDLOFD- with
001036 Common
TDLOFD- Carrier
001037 RAN
LOFD- Sharing
070206 with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728394 L.IRATHO.BlindHO.E2G.ExecSuccOut.PLMN Number of Multi- PS Inter-

handover None UTRAN
executions UMTS: and
from E- None GERAN
UTRAN to SRVCC to
GERAN for LTE:
LOFD- GERAN
a specific CS
operator 001020
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
Description ID Name
LOFD- CS
001036 Fallback to
LOFD- GERAN
001037 RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526728497 L.RRCRedirection.E2W.CSFB Number of Multi- CS

CSFB- mode: Fallback to
based None UTRAN
redirections GSM: CS
from E- None Fallback to
UTRANs to UMTS: UTRAN
WCDMA None
network
LTE:
LOFD-
001033
TDLOFD-
001033
1526728498 L.RRCRedirection.E2G.CSFB Number of Multi- CS

based None GERAN
redirections GSM:
from E- None
Description ID Name
UTRAN to UMTS: CS
GERAN None Fallback to
LTE: GERAN
LOFD-
001034
TDLOFD-
001034
1526728500 L.RRCRedirection.E2T.CSFB Number of Multi- CS

based None UTRAN
UTRAN to UMTS: UTRAN
TD-SCDMA None
network
LTE:
LOFD-
001033
TDLOFD-
001033
1526728504 L.IRATHO.E2W.CSFB.PrepAttOut Number of Multi- CS

based inter- None UTRAN
RAT GSM: CS
handover None Fallback to
preparation UMTS: UTRAN
attempts None
from E-
UTRAN to LTE:
WCDMA LOFD-
network 001033
TDLOFD-
001033
1526728505 L.IRATHO.E2W.CSFB.ExecAttOut Number of Multi- CS

RAT GSM: CS
execution UMTS: UTRAN
attempts None
from E-
UTRAN to LTE:
WCDMA LOFD-
network 001033
Description ID Name
TDLOFD-
001033
1526728506 L.IRATHO.E2W.CSFB.ExecSuccOut Number of Multi- CS

CSFB- None UTRAN
based inter- GSM: CS
RAT None Fallback to
handover UMTS: UTRAN
executions None
from E-
LTE:
UTRAN to
WCDMA LOFD-
001033
network
TDLOFD-
001033
1526728507 L.IRATHO.E2G.CSFB.PrepAttOut Number of Multi- CS

based inter- None GERAN
RAT GSM: CS
preparation UMTS: GERAN
attempts None
from E-
UTRAN to LTE:
GERAN LOFD-
001034
TDLOFD-
001034
1526728508 L.IRATHO.E2G.CSFB.ExecAttOut Number of Multi- CS

based inter- None GERAN
RAT GSM: CS
execution UMTS: GERAN
attempts None
from E-
UTRAN to LTE:
GERAN LOFD-
001034
TDLOFD-
001034
1526728509 L.IRATHO.E2G.CSFB.ExecSuccOut Number of Multi- CS

CSFB- None GERAN
Description ID Name

handover UMTS: GERAN
executions None
from E- LTE:
UTRAN to LOFD-
GERAN 001034
TDLOFD-
001034
1526728510 L.IRATHO.E2T.CSFB.PrepAttOut Number of Multi- CS

RAT GSM: CS
attempts None
from E-
UTRAN to LTE:
TD-SCDMA LOFD-
network 001033
TDLOFD-
001033
1526728511 L.IRATHO.E2T.CSFB.ExecAttOut Number of Multi- CS

RAT GSM: CS
execution UMTS: UTRAN
attempts None
from E-
UTRAN to LTE:
TD-SCDMA LOFD-
001033
network
TDLOFD-
001033
1526728512 L.IRATHO.E2T.CSFB.ExecSuccOut Number of Multi- CS

CSFB- None UTRAN
handover UMTS: UTRAN
executions None
from E-
UTRAN to
Description ID Name
TD-SCDMA LTE:
network LOFD-
001033
TDLOFD-
001033
1526728513 L.CSFB.PrepFail.Conflict Number of Multi- CS

preparation None UTRAN
failures GSM: CS
because of None Fallback to
process UMTS: UTRAN
conflict None CS
LTE: Fallback to
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD-
001035
1526728560 L.IRATHO.E2W.NoData.ExecAttOut Number of Multi- PS Inter-

inter-RAT mode: RAT
from E- None UTRAN
UTRAN to UMTS: and
WCDMA None UTRAN
network SRVCC to
triggered for LTE:
LOFD- UTRAN
UEs that do CS
not transmit 001019
LOFD- Fallback to
or receive UTRAN
data 001022
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
Description ID Name
TDLOFD- SRVCC to
001033 UTRAN
LOFD- CS
001105 Fallback to
TDLOFD- UTRAN
001105 Dynamic
DRX
Dynamic
DRX
1526728561 L.IRATHO.E2W.NoData.ExecSuccOut Number of Multi- PS Inter-

from E- None UTRAN
UTRAN to UMTS: and
WCDMA None UTRAN
network SRVCC to
triggered for LTE:
LOFD- UTRAN
UEs that do CS
not transmit 001019
LOFD- Fallback to
or receive UTRAN
data 001022
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
LOFD- CS
001105 Fallback to
TDLOFD- UTRAN
001105 Dynamic
DRX
Dynamic
DRX
1526728705 L.FlashCSFB.E2W Number of Multi- Flash CS

for flash None UTRAN
CSFB to GSM: Flash CS
WCDMA None Fallback to
network UTRAN
Description ID Name
UMTS:
None
LTE:
LOFD-
001052
TDLOFD-
001052
1526728706 L.FlashCSFB.E2G Number of Multi- Flash CS

for flash None GERAN
CSFB to GSM: Flash CS
GERAN None Fallback to
UMTS: GERAN
None
LTE:
LOFD-
001053
TDLOFD-
001053
1526728707 L.CSFB.PrepAtt.Emergency Number of Multi- CS

received by GSM: CS
for UMTS: UTRAN
emergency None CS
calls Fallback to
LTE:
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD- CS
001035 Fallback to
CDMA2000
TDLOFD- 1xRTT
001035
Description ID Name
1526728708 L.CSFB.PrepSucc.Emergency Number of Multi- CS

responses mode: Fallback to
sent from None UTRAN
the eNodeB GSM: CS
for CSFB None Fallback to
triggered for UMTS: UTRAN
emergency None CS
calls Fallback to
LTE:
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD- CS
001035 Fallback to
CDMA2000
TDLOFD- 1xRTT
001035
1526728709 L.CSFB.E2W.Emergency Number of Multi- CS

WCDMA GSM: CS
network None Fallback to
triggered for UMTS: UTRAN
emergency None Ultra-Flash
calls CSFB to
LTE:
LOFD- UTRAN
001033 Ultra-Flash
TDLOFD- CSFB to
001033 UTRAN
LOFD-
070202
TDLOFD-
081223
1526728710 L.CSFB.E2G.Emergency Number of Multi- CS

GERAN GSM: CS
triggered for None Fallback to
GERAN
Description ID Name
emergency UMTS:
calls None
LTE:
LOFD-
001034
TDLOFD-
001034
1526728746 L.IRATHO.BlindHO.E2T.PrepAttOut Number of Multi- CS

blind None UTRAN
handover GSM: CS
from E- UMTS: UTRAN
TD-SCDMA RAT
network LTE:
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001033 and
UTRAN
LOFD-
001019 PS Inter-
RAT
TDLOFD-
Mobility
001019 between E-
UTRAN
and
UTRAN
1526728747 L.IRATHO.BlindHO.E2T.ExecAttOut Number of Multi- PS Inter-

inter-RAT mode: RAT
blind None Mobility
from E- UMTS: and
UTRAN to None UTRAN
TD-SCDMA SRVCC to
network LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
Description ID Name
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728748 L.IRATHO.BlindHO.E2T.ExecSuccOut Number of Multi- PS Inter-

from E- UMTS: and
UTRAN to None UTRAN
TD-SCDMA SRVCC to
network LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD-
between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728749 L.CSFB.E2T Number of Multi- CS

for SRVCC None UTRAN
to TD- GSM: CS
SCDMA None Fallback to
network UMTS: UTRAN
None
LTE:
LOFD-
001033
TDLOFD-
001033
Description ID Name
1526728750 L.CSFB.E2T.Idle Number of Multi- CS

for SRVCC None UTRAN
to TD- GSM: CS
network for UMTS: UTRAN
UEs in idle None
mode
LTE:
LOFD-
001033
TDLOFD-
001033
1526728751 L.RRCRedirection.E2T.PrepAtt Number of Multi- PS Inter-

to TD- GSM: between E-
SCDMA None UTRAN
network UMTS: and
None UTRAN
LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD-
between E-
001019 UTRAN
TDLOFD- and
001033 UTRAN
CS
Fallback to
UTRAN
1526728752 L.RRCRedirection.E2T Number of Multi- PS Inter-

to TD- None Mobility
SCDMA GSM: between E-
network None UTRAN
UMTS: and
None UTRAN
LTE: CS
LOFD- Fallback to
001019 UTRAN
Description ID Name
LOFD- PS Inter-
001033 RAT
TDLOFD- Mobility
001019 between E-
TDLOFD- UTRAN
001033 and
UTRAN
CS
Fallback to
UTRAN
1526728870 L.IRATHO.T2E.PrepAttIn Number of Multi- PS Inter-

inter-RAT mode: RAT
from TD- None UTRAN
SCDMA UMTS: and
network to None UTRAN
E-UTRAN SRVCC to
LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728871 L.IRATHO.T2E.PrepInSucc Number of Multi- PS Inter-

preparations None UTRAN
from TD- UMTS: and
SCDMA None UTRAN
network to SRVCC to
E-UTRAN UTRAN
Description ID Name
LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001022 RAT
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001019 and
UTRAN
TDLOFD-
001022 SRVCC to
UTRAN
TDLOFD-
001033 CS
Fallback to
UTRAN
1526728872 L.IRATHO.T2E.ExecSuccIn Number of Multi- PS Inter-

from TD- None UTRAN
SCDMA UMTS: and
E-UTRAN SRVCC to
LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728873 L.IRATHO.T2E.PrepInFail.TgtNotAllow Number of Multi- PS Inter-

inter-RAT mode: RAT
preparation between E-
failures from UTRAN
Description ID Name
TD-SCDMA GSM: and

network in None UTRAN
the target UMTS: SRVCC to
cell due to None UTRAN
Handover LTE: CS
Target not LOFD- Fallback to
allowed 001019 UTRAN
LOFD- PS Inter-
001022 RAT
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001019 and
UTRAN
TDLOFD-
001022 SRVCC to
UTRAN
TDLOFD-
001033 CS
Fallback to
UTRAN
1526728874 L.IRATHO.W2E.PrepAttIn Number of Multi- PS Inter-

inter-RAT mode: RAT
from None UTRAN
WCDMA UMTS: and
E-UTRAN SRVCC to
LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
Description ID Name
1526728875 L.IRATHO.W2E.PrepInSucc Number of Multi- PS Inter-

preparations None UTRAN
from UMTS: and
WCDMA None UTRAN
network to SRVCC to
E-UTRAN LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728876 L.IRATHO.W2E.ExecSuccIn Number of Multi- PS Inter-

from None UTRAN
WCDMA UMTS: and
E-UTRAN SRVCC to
LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
Description ID Name
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728877 L.IRATHO.W2E.PrepInFail.TgtNotAllow Number of Multi- PS Inter-

inter-RAT mode: RAT
preparation GSM: between E-
failures from None UTRAN
WCDMA UMTS: and
network in None UTRAN
the target SRVCC to
cell due to LTE:
LOFD- UTRAN
Handover CS
Target not 001019
LOFD- Fallback to
allowed UTRAN
001022
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526728899 L.IRATHO.E2W.CSFB.MMEAbnormRsp Number of Multi- CS

for None UTRAN
abnormal GSM: CS
causes None Fallback to
received by UMTS: UTRAN
the eNodeB None
from the
MME during LTE:
CSFB- LOFD-
based inter- 001033
RAT TDLOFD-
handover 001033
executions
from E-
Description ID Name
UTRAN to
WCDMA
network
1526728900 L.IRATHO.E2G.CSFB.MMEAbnormRsp Number of Multi- CS

for None GERAN
abnormal GSM: CS
received by UMTS: GERAN
the eNodeB None
from the
MME during LTE:
LOFD-
CSFB-
based inter- 001034
RAT TDLOFD-
handover 001034
executions
from E-
UTRAN to
GERAN
1526728901 L.IRATHO.E2T.CSFB.MMEAbnormRsp Number of Multi- CS

for None UTRAN
abnormal GSM: CS
the eNodeB None
from the
LTE:
MME during
CSFB- LOFD-
based inter- 001033
RAT TDLOFD-
handover 001033
executions
from E-
UTRAN to
TD-SCDMA
network
1526728946 L.RIM.SI.E2W.Req Number of Multi- Flash CS

times the mode: Fallback to
eNodeB None UTRAN
sends a GSM: Flash CS
system None Fallback to
information UTRAN
Description ID Name
request to a UMTS:
WCDMA None
network LTE:
LOFD-
001052
TDLOFD-
001052
1526728947 L.RIM.SI.E2W.Resp Number of Multi- Flash CS

eNodeB None UTRAN
receives a GSM: Flash CS
information UMTS: UTRAN
response None
from a
WCDMA LTE:
network LOFD-
001052
TDLOFD-
001052
1526728948 L.RIM.SI.E2W.Update Number of Multi- Flash CS

eNodeB None UTRAN
information UMTS: UTRAN
update from None
a WCDMA
network LTE:
LOFD-
001052
TDLOFD-
001052
1526728949 L.RIM.Load.E2W.Req Number of Multi- Inter-RAT

times the mode: Load
eNodeB None Sharing to
sends a GSM: UTRAN
load None Inter-RAT
information UMTS: Load
request to a None Sharing to
WCDMA UTRAN
network LTE:
LOFD-
001044
Description ID Name
TDLOFD-
001044
1526728950 L.RIM.Load.E2W.Resp Number of Multi- Inter-RAT

receives a GSM: UTRAN
load None Inter-RAT
response None Sharing to
from a UTRAN
LTE:
WCDMA
network LOFD-
001044
TDLOFD-
001044
1526728951 L.RIM.Load.E2W.Update Number of Multi- Inter-RAT

receives a GSM: UTRAN
load None Inter-RAT
update from None Sharing to
a WCDMA UTRAN
network LTE:
LOFD-
001044
TDLOFD-
001044
1526729260 L.CSFB.E2G.Idle Number of Multi- CS

GERAN GSM: CS
network for None Fallback to
UEs in idle UMTS: GERAN
mode None
LTE:
LOFD-
001034
TDLOFD-
001034
1526729432 L.IRATHO.E2W.TimeAvg Average Multi- PS Inter-

handover mode: RAT
duration None Mobility
Description ID Name

UTRAN to None UTRAN
WCDMA UMTS: and
network None UTRAN
LTE: SRVCC to
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
TDLOFD- Mobility
001019 between E-
UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526729433 L.IRATHO.E2G.TimeAvg Average Multi- PS Inter-

handover mode: RAT
UTRAN to None UTRAN
GERAN UMTS: and
None GERAN
LTE: SRVCC to
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
Description ID Name
CS
Fallback to
GERAN
1526729434 L.IRATHO.E2T.TimeAvg Average Multi- PS Inter-

handover mode: RAT
UTRAN to None UTRAN
TD-SCDMA UMTS: and
network None UTRAN
LTE: SRVCC to
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526729503 L.RRCRedirection.E2W.PLMN Number of Multi- PS Inter-

WCDMA None UTRAN
network for UMTS: and
a specific None UTRAN
operator CS
LTE:
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001033 UTRAN
Description ID Name
LOFD- CS
001036 Fallback to
LOFD- UTRAN
001037 RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526729504 L.RRCRedirection.E2G.PLMN Number of Multi- PS Inter-

GERAN for None UTRAN
a specific UMTS: and
operator None GERAN
LTE: CS
LOFD- Fallback to
001020 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001034 GERAN
LOFD-
001036
Description ID Name
LOFD- CS
001037 Fallback to
TDLOFD- GERAN
001036 RAN
TDLOFD- Sharing
001037 with
LOFD- Common
070206 Carrier
RAN
Sharing
with
Dedicated
Carrier
RAN
Sharing
with
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526729505 L.CCOwithNACC.E2G.CSFB.ExecAttOut Number of Multi- CS

based CCO None GERAN
with NACC GSM: CS
executions None Fallback to
from E- UMTS: GERAN
UTRAN to None
GERAN
LTE:
LOFD-
001034
TDLOFD-
001034
1526729506 L.CCOwithNACC.E2G.CSFB.ExecSuccOut Number of Multi- CS

CSFB- None GERAN
based GSM:
CCOs with None
Description ID Name
NACC from UMTS: CS

E-UTRAN to None Fallback to
GERAN LTE: GERAN
LOFD-
001034
TDLOFD-
001034
1526729507 L.CCOwithoutNACC.E2G.CSFB.ExecAttOut Number of Multi- CS

based CCO None GERAN
without GSM: CS
NACC None Fallback to
executions UMTS: GERAN
from E- None
UTRAN to
GERAN LTE:
LOFD-
001034
TDLOFD-
001034
1526729508 L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut Number of Multi- CS

CSFB- None GERAN
based GSM: CS
CCOs None Fallback to
without UMTS: GERAN
NACC from None
E-UTRAN to
GERAN LTE:
LOFD-
001034
TDLOFD-
001034
1526729509 L.IRATHO.E2W.CSFB.PrepAttOut.Emergency Number of Multi- CS

based None UTRAN
handover GSM: CS
preparation None Fallback to
attempts to UMTS: UTRAN
WCDMA None
network
triggered for LTE:
emergency LOFD-
calls 001033
Description ID Name
TDLOFD-
001033
1526729510 L.IRATHO.E2W.CSFB.ExecAttOut.Emergency Number of Multi- CS

based None UTRAN
handover GSM: CS
execution None Fallback to
attempts to UMTS: UTRAN
WCDMA None
network
LTE:
triggered for
emergency LOFD-
001033
calls
TDLOFD-
001033
1526729511 L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency Number of Multi- CS

CSFB- None UTRAN
based GSM: CS
executions UMTS: UTRAN
to WCDMA None
network
triggered for LTE:
emergency LOFD-
calls 001033
TDLOFD-
001033
1526729512 L.IRATHO.E2G.CSFB.PrepAttOut.Emergency Number of Multi- CS

based None GERAN
handover GSM: CS
attempts to UMTS: GERAN
GERAN None
triggered for
emergency LTE:
calls LOFD-
001034
TDLOFD-
001034
1526729513 L.IRATHO.E2G.CSFB.ExecAttOut.Emergency Number of Multi- CS

based None GERAN
Description ID Name
handover GSM: CS
attempts to UMTS: GERAN
GERAN None
triggered for LTE:
emergency LOFD-
calls 001034
TDLOFD-
001034
1526729514 L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency Number of Multi- CS

CSFB- None GERAN
based GSM: CS
to GERAN None
triggered for
emergency LTE:
calls LOFD-
001034
TDLOFD-
001034
1526729515 L.RRCRedirection.E2W.CSFB.TimeOut Number of Multi- CS

based blind None UTRAN
WCDMA None
network
caused by LTE:
CSFB LOFD-
001033
protection
timer TDLOFD-
expiration 001033
1526729516 L.RRCRedirection.E2G.CSFB.TimeOut Number of Multi- CS

based blind None GERAN
UTRAN to UMTS: GERAN
GERAN None
caused by
CSFB
Description ID Name
protection LTE:
timer LOFD-
expiration 001034
TDLOFD-
001034
1526729562 L.IRATHO.NCell.E2G.PrepAttOut Number of Multi- PS Inter-

handover mode: RAT
attempts None Mobility
from a GSM: between E-
specific E- None UTRAN
UTRAN cell UMTS: and
to a specific None GERAN
GERAN cell SRVCC to
LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
CS
Fallback to
GERAN
1526729563 L.IRATHO.NCell.E2G.ExecAttOut Number of Multi- PS Inter-

handover mode: RAT
executions None Mobility
GERAN cell SRVCC to
LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Description ID Name
TDLOFD- Mobility
001020 between E-
TDLOFD- UTRAN
001023 and
TDLOFD- GERAN
001034 SRVCC to
GERAN
CS
Fallback to
GERAN
1526729564 L.IRATHO.NCell.E2G.ExecSuccOut Number of Multi- PS Inter-

handovers None Mobility
GERAN cell SRVCC to
LTE:
LOFD- GERAN
001020 CS
LOFD- Fallback to
001023 GERAN
LOFD- PS Inter-
001034 RAT
Mobility
TDLOFD- between E-
001020 UTRAN
TDLOFD- and
001023 GERAN
TDLOFD- SRVCC to
001034 GERAN
CS
Fallback to
GERAN
1526729565 L.IRATHO.NCell.E2W.PrepAttOut Number of Multi- PS Inter-

handover mode: RAT
attempts None Mobility
to a specific None UTRAN
WCDMA SRVCC to
cell UTRAN
Description ID Name
LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001022 RAT
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001019 and
UTRAN
TDLOFD-
001022 SRVCC to
UTRAN
TDLOFD-
001033 CS
Fallback to
UTRAN
1526729566 L.IRATHO.NCell.E2W.ExecAttOut Number of Multi- PS Inter-

handover mode: RAT
executions None Mobility
WCDMA SRVCC to
cell LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526729567 L.IRATHO.NCell.E2W.ExecSuccOut Number of Multi- PS Inter-

handovers None Mobility
from a between E-
specific E- UTRAN
Description ID Name
UTRAN cell GSM: and

WCDMA UMTS: SRVCC to
cell None UTRAN
LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001022 RAT
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001019 and
UTRAN
TDLOFD-
001022 SRVCC to
UTRAN
TDLOFD-
001033 CS
Fallback to
UTRAN
1526729661 L.RIM.SI.E2G.Req Number of Multi- Flash CS

eNodeB None GERAN
sends a GSM: Flash CS
information UMTS: GERAN
request to a None
GERAN
LTE:
LOFD-
001053
TDLOFD-
001053
1526729662 L.RIM.SI.E2G.Resp Number of Multi- Flash CS

eNodeB None GERAN
response None
from a
GERAN LTE:
LOFD-
001053
Description ID Name
TDLOFD-
001053
1526729663 L.RIM.SI.E2G.Update Number of Multi- Flash CS

eNodeB None GERAN
update from None
a GERAN
LTE:
LOFD-
001053
TDLOFD-
001053
1526730044 L.CSFB.PrepAtt.PLMN Number of Multi- CS

received by GSM: CS
for a UMTS: UTRAN
specific None CS
operator Fallback to
LTE:
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD- RAN
001035 Sharing
with
LOFD-
Common
001036 Carrier
LOFD- RAN
001037 Sharing
TDLOFD- with
001036 Dedicated
TDLOFD- Carrier
001037 RAN
LOFD- Sharing
070206 with
Description ID Name
Common
Carrier
RAN
Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730045 L.CSFB.PrepSucc.PLMN Number of Multi- CS

CSFB None UTRAN
responses GSM: CS
sent from None Fallback to
the eNodeB UMTS: UTRAN
for a None CS
specific Fallback to
operator LTE:
LOFD- GERAN
001033 CS
TDLOFD- Fallback to
001033 GERAN
LOFD- CS
001034 Fallback to
TDLOFD- CDMA2000
001034 1xRTT
LOFD- RAN
001035 Sharing
with
LOFD- Common
001036 Carrier
LOFD- RAN
001037 Sharing
TDLOFD- with
001036 Dedicated
TDLOFD- Carrier
001037 RAN
LOFD- Sharing
070206 with
Common
Carrier
RAN
Sharing
with
Description ID Name
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730046 L.RRCRedirection.E2W.CSFB.PLMN Number of Multi- CS

based None UTRAN
WCDMA None RAN
network for Sharing
a specific LTE:
LOFD- with
operator Common
001033
TDLOFD- Carrier
001033 RAN
LOFD- Sharing
001036 with
Dedicated
LOFD- Carrier
001037
RAN
TDLOFD-
Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730047 L.IRATHO.E2W.CSFB.PrepAttOut.PLMN Number of Multi- CS

based None UTRAN
handover GSM: CS
attempts UMTS: UTRAN
from E- None RAN
UTRAN to Sharing
WCDMA with
network for
Description ID Name
a specific LTE: Common

operator LOFD- Carrier
001033 RAN
TDLOFD- Sharing
001033 with
LOFD- Dedicated
001036 Carrier
LOFD- RAN
001037 Sharing
TDLOFD- with
001036 Common
Carrier
TDLOFD-
001037 RAN
Sharing
LOFD- with
070206 Dedicated
Carrier
Hybrid
RAN
Sharing
1526730048 L.IRATHO.E2W.CSFB.ExecAttOut.PLMN Number of Multi- CS

based None UTRAN
handover GSM: CS
attempts UMTS: UTRAN
from E- None RAN
UTRAN to Sharing
WCDMA LTE:
LOFD- with
network for Common
a specific 001033
TDLOFD- Carrier
operator
001033 RAN
LOFD- Sharing
001036 with
Dedicated
LOFD- Carrier
001037
RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Description ID Name
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730049 L.IRATHO.E2W.CSFB.ExecSuccOut.PLMN Number of Multi- CS

CSFB- None UTRAN
based GSM: CS
executions UMTS: UTRAN
from E- None RAN
UTRAN to Sharing
WCDMA LTE:
LOFD- with
network for Common
a specific 001033
TDLOFD- Carrier
operator
001033 RAN
LOFD- Sharing
001036 with
Dedicated
LOFD- Carrier
001037
RAN
TDLOFD-
Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730050 L.RRCRedirection.E2G.CSFB.PLMN Number of Multi- CS

based None GERAN
UTRAN to UMTS: GERAN
GERAN for None RAN
a specific Sharing
operator with
Description ID Name
LTE: Common
LOFD- Carrier
001034 RAN
TDLOFD- Sharing
001034 with
LOFD- Dedicated
001036 Carrier
LOFD- RAN
001037 Sharing
TDLOFD- with
001036 Common
Carrier
TDLOFD-
001037 RAN
Sharing
LOFD- with
070206 Dedicated
Carrier
Hybrid
RAN
Sharing
1526730051 L.IRATHO.E2G.CSFB.PrepAttOut.PLMN Number of Multi- CS

based None GERAN
handover GSM: CS
attempts UMTS: GERAN
from E- None RAN
UTRAN to Sharing
GERAN for LTE:
LOFD- with
a specific Common
operator 001034
TDLOFD- Carrier
001034 RAN
LOFD- Sharing
001036 with
Dedicated
LOFD- Carrier
001037
RAN
TDLOFD- Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Description ID Name
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730052 L.IRATHO.E2G.CSFB.ExecAttOut.PLMN Number of Multi- CS

based None GERAN
handover GSM: CS
from E- None RAN
UTRAN to Sharing
GERAN for LTE:
LOFD- with
a specific Common
operator 001034
TDLOFD- Carrier
001034 RAN
LOFD- Sharing
001036 with
Dedicated
LOFD- Carrier
001037
RAN
TDLOFD-
Sharing
001036 with
TDLOFD- Common
001037 Carrier
LOFD- RAN
070206 Sharing
with
Dedicated
Carrier
Hybrid
RAN
Sharing
1526730053 L.IRATHO.E2G.CSFB.ExecSuccOut.PLMN Number of Multi- CS

CSFB- None GERAN
based GSM: CS
from E- None RAN
UTRAN to Sharing
GERAN for with
Description ID Name
a specific LTE: Common

operator LOFD- Carrier
001034 RAN
TDLOFD- Sharing
001034 with
LOFD- Dedicated
001036 Carrier
LOFD- RAN
001037 Sharing
TDLOFD- with
001036 Common
Carrier
TDLOFD-
001037 RAN
Sharing
LOFD- with
070206 Dedicated
Carrier
Hybrid
RAN
Sharing
1526730076 L.IRATHO.E2W.CSFB.Prep.FailOut.MME Number of Multi- CS

based None UTRAN
outgoing GSM: CS
failures from None
E-UTRAN to
WCDMA LTE:
network LOFD-
because of 001033
the MME TDLOFD-
side causes 001033
1526730077 L.IRATHO.E2W.CSFB.Prep.FailOut.PrepFailure Number of Multi- CS

based None UTRAN
outgoing GSM: CS
failures from None
E-UTRAN to
WCDMA LTE:
network LOFD-
because of 001033
Description ID Name
the TDLOFD-
response of 001033
handover
preparation
failure from
WCDMA
network
1526730078 L.IRATHO.E2W.CSFB.Prep.FailOut.NoReply Number of Multi- CS

based None UTRAN
outgoing GSM: CS
failures from None
E-UTRAN to
WCDMA LTE:
network LOFD-
001033
because of
no response TDLOFD-
from 001033
WCDMA
network
1526730079 L.IRATHO.E2T.CSFB.Prep.FailOut.MME Number of Multi- CS

based None UTRAN
outgoing GSM: CS
failures from None
E-UTRAN to
TD-SCDMA LTE:
network LOFD-
because of 001033
the MME TDLOFD-
side causes 001033
1526730080 L.IRATHO.E2T.CSFB.Prep.FailOut.PrepFailure Number of Multi- CS

based None UTRAN
outgoing GSM: CS
failures from None
E-UTRAN to
TD-SCDMA
Description ID Name
network LTE:
because of LOFD-
the 001033
response of TDLOFD-
handover 001033
preparation
failure from
TD-SCDMA
network
1526730081 L.IRATHO.E2T.CSFB.Prep.FailOut.NoReply Number of Multi- CS

based None UTRAN
outgoing GSM: CS
failures from None
E-UTRAN to
LTE:
TD-SCDMA
network LOFD-
because of 001033
no response TDLOFD-
from TD- 001033
SCDMA
network
1526730146 L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut Number of Multi- Ultra-Flash

SRVCC- mode: CSFB to
based None UTRAN
outgoing GSM:
handover None
attempts UMTS:
from E- None
UTRAN to
WCDMA LTE:
network for LOFD-
ultra-flash 070202
CSFB
1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut Number of Multi- Ultra-Flash

based None UTRAN
outgoing GSM:
handover None
executions UMTS:
from E- None
UTRAN to
Description ID Name
WCDMA LTE:
network for LOFD-
ultra-flash 070202
CSFB
1526730148 L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut Number of Multi- Ultra-Flash

successful mode: CSFB to
SRVCC- None UTRAN
based GSM:
outgoing None
handovers UMTS:
from E- None
UTRAN to
LTE:
WCDMA
network for LOFD-
ultra-flash 070202
CSFB
1526733006 L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut Number of Multi- Ultra-Flash

based None GERAN
outgoing GSM: Ultra-Flash
handover None CSFB to
from E- None
UTRAN to
GERAN for LTE:
ultra-flash LOFD-
CSFB 081283
TDLOFD-
081203
1526733007 L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut Number of Multi- Ultra-Flash

based None GERAN
handover None CSFB to
from E- None
UTRAN to
GERAN for LTE:
ultra-flash LOFD-
CSFB 081283
TDLOFD-
081203
Description ID Name
1526733008 L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut Number of Multi- Ultra-Flash

successful mode: CSFB to
SRVCC- None GERAN
based GSM: Ultra-Flash
outgoing None CSFB to
handovers UMTS: GERAN
from E- None
UTRAN to
GERAN for LTE:
LOFD-
ultra-flash
CSFB 081283
TDLOFD-
081203
1526733009 L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp Number of Multi- Ultra-Flash

abnormal mode: CSFB to
responses None GERAN
from the GSM: Ultra-Flash
MME during None CSFB to
outgoing UMTS: GERAN
handovers None
from E-
UTRAN to LTE:
GERAN for LOFD-
ultra-flash 081283
CSFB TDLOFD-
081203
1526736728 L.IRATHO.CSFB.SRVCC.E2W.MMEAbnormRsp Number of Multi- Ultra-Flash

responses mode: CSFB to
for None UTRAN
abnormal GSM: Ultra-Flash
causes None CSFB to
the eNodeB None
from the
MME during LTE:
handovers LOFD-
from the E- 070202
UTRAN to TDLOFD-
WCDMA 081223
networks for
ultra-flash
CSFB
Description ID Name
1526736729 L.IRATHO.E2W.CSFB.SRVCC.Prep.FailOut.MME Number of Multi- Ultra-Flash

MME- mode: CSFB to
caused None UTRAN
preparation GSM:
failures of None
outgoing UMTS:
handovers None
to WCDMA
networks for LTE:
LOFD-
ultra-flash
CSFB 070202
1526736730 L.IRATHO.E2W.CSFB.SRVCC.Prep.FailOut.PrepFailure Number of Multi- Ultra-Flash

preparation mode: CSFB to
failures of None UTRAN
outgoing GSM:
handovers None
to WCDMA UMTS:
networks for None
ultra-flash
CSFB LTE:
LOFD-
because of
the 070202
response of
handover
preparation
failure sent
by the
WCDMA
networks
1526736731 L.IRATHO.E2W.CSFB.SRVCC.Prep.FailOut.NoReply Number of Multi- Ultra-Flash

failures of None UTRAN
outgoing GSM:
handovers None
to WCDMA UMTS:
networks for None
ultra-flash
CSFB LTE:
because of LOFD-
no response 070202
from the
WCDMA
networks
Description ID Name
1526736732 L.IRATHO.E2G.CSFB.SRVCC.Prep.FailOut.MME Number of Multi- Ultra-Flash

MME- mode: CSFB to
caused None GERAN
preparation GSM: Ultra-Flash
failures of None CSFB to
outgoing UMTS: GERAN
handovers None
to GERANs
for ultra- LTE:
LOFD-
flash CSFB
081283
TDLOFD-
081203
1526736733 L.IRATHO.E2G.CSFB.SRVCC.Prep.FailOut.PrepFailure Number of Multi- Ultra-Flash

failures of None GERAN
handovers None CSFB to
to GERANs UMTS: GERAN
for ultra- None
flash CSFB
because of LTE:
the LOFD-
response of 081283
handover TDLOFD-
preparation 081203
failure sent
by the
GERANs
1526736734 L.IRATHO.E2G.CSFB.SRVCC.Prep.FailOut.NoReply Number of Multi- Ultra-Flash

failures of None GERAN
handovers None CSFB to
to GERANs UMTS: GERAN
for ultra- None
flash CSFB
LTE:
because of
no response LOFD-
from the 081283
GERANs TDLOFD-
081203
Description ID Name
1526736745 L.IRATHO.T2E.PrepInFail.AdmitFail Number of Multi- PS Inter-

TDSCDMA- mode: RAT
to-EUTRAN None Mobility
failures UMTS: and
because of None UTRAN
admission SRVCC to
failure LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736746 L.IRATHO.T2E.PrepInFail.FlowCtrl Number of Multi- PS Inter-

TDSCDMA- mode: RAT
failures UMTS: and
flow control SRVCC to
LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
Description ID Name
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736747 L.IRATHO.T2E.PrepInFail.HOCancel Number of Multi- PS Inter-

TDSCDMA- mode: RAT
failures UMTS: and
because the None UTRAN
target cell SRVCC to
receives LTE:
LOFD- UTRAN
handover CS
cancelation 001019
LOFD- Fallback to
messages UTRAN
001022
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736748 L.IRATHO.T2E.PrepInFail.disc.FlowCtrl Number of Multi- PS Inter-

times mode: RAT
TDSCDMA- None Mobility
to-EUTRAN GSM: between E-
handover None UTRAN
messages UMTS: and
are None UTRAN
discarded SRVCC to
because of LTE:
LOFD- UTRAN
flow control CS
001019
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Description ID Name
TDLOFD- Mobility
001019 between E-
TDLOFD- UTRAN
001022 and
TDLOFD- UTRAN
001033 SRVCC to
UTRAN
CS
Fallback to
UTRAN
1526736749 L.IRATHO.W2E.PrepInFail.AdmitFail Number of Multi- PS Inter-

WCDMA-to- mode: RAT
EUTRAN None Mobility
failures UMTS: and
admission SRVCC to
failure LTE:
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736750 L.IRATHO.W2E.PrepInFail.FlowCtrl Number of Multi- PS Inter-

WCDMA-to- mode: RAT
failures UMTS: and
flow control SRVCC to
UTRAN
Description ID Name
LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001022 RAT
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001019 and
UTRAN
TDLOFD-
001022 SRVCC to
UTRAN
TDLOFD-
001033 CS
Fallback to
UTRAN
1526736751 L.IRATHO.W2E.PrepInFail.HOCancel Number of Multi- PS Inter-

WCDMA-to- mode: RAT
failures UMTS: and
because the None UTRAN
target cell SRVCC to
receives LTE:
LOFD- UTRAN
handover CS
cancelation 001019
LOFD- Fallback to
messages UTRAN
001022
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736752 L.IRATHO.W2E.PrepInFail.disc.FlowCtrl Number of Multi- PS Inter-

times mode: RAT
WCDMA-to- None Mobility
EUTRAN between E-
handover UTRAN
Description ID Name
messages GSM: and

are None UTRAN
discarded UMTS: SRVCC to
flow control LTE: CS
LOFD- Fallback to
001019 UTRAN
LOFD- PS Inter-
001022 RAT
LOFD- Mobility
001033 between E-
TDLOFD- UTRAN
001019 and
UTRAN
TDLOFD-
001022 SRVCC to
UTRAN
TDLOFD-
001033 CS
Fallback to
UTRAN
1526736753 L.IRATHO.G2E.PrepInFail Number of Multi- PS Inter-

GERAN-to- mode: RAT
failures UMTS: and
None UTRAN
LTE: SRVCC to
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
Description ID Name
1526736754 L.IRATHO.T2E.PrepInFail Number of Multi- PS Inter-

TDSCDMA- mode: RAT
failures UMTS: and
None UTRAN
LTE: SRVCC to
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736755 L.IRATHO.W2E.PrepInFail Number of Multi- PS Inter-

WCDMA-to- mode: RAT
failures UMTS: and
None UTRAN
LTE: SRVCC to
LOFD- UTRAN
001019 CS
LOFD- Fallback to
001022 UTRAN
LOFD- PS Inter-
001033 RAT
Mobility
TDLOFD- between E-
001019 UTRAN
TDLOFD- and
001022 UTRAN
Description ID Name
TDLOFD- SRVCC to
001033 UTRAN
CS
Fallback to
UTRAN
1526736760 L.IRATHO.E2W.CSFB.MMEAbnormRsp.PLMN Number of Multi- CS

for None UTRAN
abnormal GSM: CS
the eNodeB None
from the
MME during LTE:
CSFB- LOFD-
based inter- 001033
RAT TDLOFD-
handover 001033
executions
from E-
UTRAN to
WCDMA
network for
a specific
operator
1526737720 L.RRCRedirection.E2T.CSFB.TimeOut Number of Multi- CS

based blind None UTRAN
LTE-to-TD- GSM: CS
redirections UMTS: UTRAN
triggered None
due to timer
expiration LTE:
LOFD-
001033
TDLOFD-
001033
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
11 Reference Documents
1. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System

(EPS)"
2. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC); Stage 2"
3. VoLGA Forum Specifications
4. 3GPP TS 36.300, "E-UTRAN Overall description"
5. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access "
6. 3GPP TS 48.018, "General Packet Radio Service (GPRS); Base Station System
(BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP) "
7. VoLGA Forum Specifications Inter-RAT Mobility Management in Connected Mode
8. Emergency Call
9. LCS
10. Interoperability Between GSM and LTE

11. Interoperability Between UMTS and LTE

CSFB Huawei

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CSFB Huawei

Uploaded by

Copyright:

Available Formats

CS Fallback

HUAWEI TECHNOLOGIES CO., LTD.

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

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of

1 About This Document

eNodeB Type Model

Macro 3900 series eNodeB

1.2 Intended Audience

This document is intended for personnel who:

This issue includes the following changes.

Change Type Change Description Parameter Change Affected

Feature Added the measurement-specific None Macro,

Added the random procedure Added the Macro,

Editorial None None -

This issue includes the following changes.

Change Change Description Parameter Change Affected

Feature Added the UE Added the Macro,

Editorial None None -

eRAN8.1 Draft A (2015-01-15)

Compared with Issue 06 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1

Change Change Description Parameter Change Affected

Feature Supported the cell-level blind Added the CellHoParaCfg.HoModeSwitch Macro,

Added the feature LOFD- • Added the Macro,

Added the configuration of Added the Macro,

Added SPID-based mobility None Macro,

Ultra-flash CSFB to GERAN Added the CellDrxPara.DrxForMeasSwitch Macro,

Editorial Changed "blind handling" to None -

1.4 Differences Between eNodeB Types

CSFB brings the following benefits:

UE • Is capable of accessing the EPS and accessing the UTRAN,

MME • Supports the SGs interface to the MSC/VLR.

MSC • Supports combined EPS/IMSI attach.

E-UTRAN • Forwards paging messages related to CSFB.

UTRAN/GERAN Supports one or more of the following functions:

SGSN • Supports the follow-up procedures performed for the PS

eCoordinator Is a network element provided by Huawei, and is optional. The

Measurement Triggering Reason

Figure 3-1 shows the measurement object selection procedure.

The configurations involved in Figure 3-1 are as follows:

Parameter Parameter ID Parameter Description

CSFB CSFallBackHo.CsfbHoUtranB1ThdRscp The

CSFB CSFallBackHo.CsfbHoUtranTimeToTrig N/A

3.1.2 Blind Handover

Triggering of Blind Handover

The blind handover switch is controlled by the BlindHoSwitch option in the

Target RAT Selection

3.3 Ultra-Flash CSFB to UTRAN

3.4 CS Fallback with LAI to UTRAN

This function is an enhancement to the CS Fallback to UTRAN feature. The

LAI-based CS Steering in CSFB

This chapter describes the optional feature LOFD-001088 CS Fallback Steering to

This chapter describes load-based CSFB to UTRAN. This function is an enhancement to

3.8.1 Basic Handover Decision

When the handover policy is PS HO, SRVCC, or redirection (excluding flash

Candidate Cell List Sequence of Handover Requests

If the handover request fails in all candidate cells:

3.9.1 Handover Policy Selection

The preceding figure is described as follows:

The optimization switch is controlled by the IdleCsfbRedirectOptSwitch option of the

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is

The preceding figure is described as follows:

3.10.2 RIM Procedure Through the eCoordinator

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is