Documente Academic
Documente Profesional
Documente Cultură
Issue 02
Date 2016-04-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 6
2.1 Introduction.................................................................................................................................................................... 7
2.2 Benefits........................................................................................................................................................................... 7
2.3 Application Scenarios.....................................................................................................................................................7
2.4 CSFB Mechanisms......................................................................................................................................................... 9
2.4.1 CSFB to UTRAN.......................................................................................................................................................10
2.4.2 CSFB to GERAN.......................................................................................................................................................11
3 CSFB to UTRAN.......................................................................................................................... 14
3.1 Overview...................................................................................................................................................................... 15
3.2 Feature Description.......................................................................................................................................................16
3.2.1 TDLOFD-001033 CS FallBack to UTRAN.............................................................................................................. 16
3.2.2 TDLOFD-001052 Flash CS Fallback to UTRAN..................................................................................................... 16
3.2.3 TDLOFD-081223 Ultra-Flash CSFB to UTRAN..................................................................................................... 17
3.2.4 TDLOFD-001068 CS Fallback with LAI to UTRAN...............................................................................................17
3.2.5 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering....................................................................................... 19
3.2.6 TDLOFD-001088 CS Fallback Steering to UTRAN................................................................................................ 21
3.2.7 Load-based CSFB to UTRAN................................................................................................................................... 23
3.3 Triggering Events......................................................................................................................................................... 23
3.4 Target Cell/Frequency Selection...................................................................................................................................24
3.5 Decision........................................................................................................................................................................ 30
3.5.1 Basic Decision Method..............................................................................................................................................31
3.5.2 Decision Based on System Information.................................................................................................................... 32
3.6 Execution...................................................................................................................................................................... 33
3.6.1 CSFB Policy Selection.............................................................................................................................................. 33
3.6.2 Redirection-based CSFB Optimization for UEs in Idle Mode.................................................................................. 36
3.6.3 CSFB Admission Optimization for UEs in Idle Mode..............................................................................................37
3.6.4 Retry and Penalty.......................................................................................................................................................37
4 CSFB to GERAN.......................................................................................................................... 42
4.1 Overview...................................................................................................................................................................... 43
4.2 Feature Description.......................................................................................................................................................43
4.2.1 TDLOFD-001034 CS Fallback to GERAN...............................................................................................................43
4.2.2 TDLOFD-001053 Flash CSFB to GERAN...............................................................................................................45
4.2.3 TDLOFD-001069 CS Fallback with LAI to GERAN...............................................................................................45
4.2.4 TDLOFD-001089 CS Fallback Steering to GERAN................................................................................................ 45
4.2.5 TDLOFD-081203 Ultra-Flash CSFB to GERAN..................................................................................................... 46
4.3 Triggering..................................................................................................................................................................... 47
4.4 Target Cell/Frequency Selection...................................................................................................................................47
4.5 Decision........................................................................................................................................................................ 48
4.6 Execution...................................................................................................................................................................... 48
4.7 RIM Procedure Between E-UTRAN and GERAN...................................................................................................... 50
7 Network Impact........................................................................................................................... 60
7.1 TDLOFD-001033 CS FallBack to UTRAN................................................................................................................. 60
7.2 TDLOFD-001052 Flash CS Fallback to UTRAN........................................................................................................ 61
7.3 TDLOFD-081223 Ultra-Flash CSFB to UTRAN........................................................................................................ 61
7.4 TDLOFD-001068 CS Fallback with LAI to UTRAN..................................................................................................62
7.5 TDLOFD-001088 CS Fallback Steering to UTRAN................................................................................................... 62
7.6 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering.......................................................................................... 62
7.7 TDLOFD-001034 CS Fallback to GERAN..................................................................................................................63
7.8 TDLOFD-001053 Flash CSFB to GERAN..................................................................................................................63
7.9 TDLOFD-081203 Ultra-Flash CSFB to GERAN........................................................................................................ 64
7.10 TDLOFD-001069 CS Fallback with LAI to GERAN................................................................................................64
7.11 TDLOFD-001089 CS Fallback Steering to GERAN................................................................................................. 64
8 Engineering Guidelines............................................................................................................. 65
8.1 TDLOFD-001033 CS Fallback to UTRAN..................................................................................................................65
8.1.1 When to Use CS Fallback to UTRAN.......................................................................................................................65
8.1.2 Required Information................................................................................................................................................ 65
8.1.3 Requirements............................................................................................................................................................. 66
8.1.4 Precautions.................................................................................................................................................................67
8.1.5 Data Preparation and Feature Activation...................................................................................................................67
8.1.5.1 Data Preparation..................................................................................................................................................... 67
8.1.5.2 Using the CME....................................................................................................................................................... 74
8.1.5.3 Using MML Commands......................................................................................................................................... 75
8.1.6 Activation Observation..............................................................................................................................................79
8.1.7 Deactivation...............................................................................................................................................................85
8.1.7.1 Using the CME....................................................................................................................................................... 85
8.1.7.2 Using MML Commands......................................................................................................................................... 85
8.1.8 Performance Monitoring............................................................................................................................................86
8.1.9 Parameter Optimization............................................................................................................................................. 87
8.2 RIM Procedure from E-UTRAN to UTRAN............................................................................................................... 91
8.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN...................................................................................... 91
8.2.2 Required Information................................................................................................................................................ 91
8.2.3 Requirements............................................................................................................................................................. 91
8.2.4 Precautions.................................................................................................................................................................92
8.2.5 Data Preparation and Feature Activation...................................................................................................................92
8.2.5.1 Data Preparation..................................................................................................................................................... 92
8.2.5.2 Using the CME....................................................................................................................................................... 93
8.2.5.3 Using MML Commands......................................................................................................................................... 93
8.2.6 Activation Observation..............................................................................................................................................93
8.2.7 Deactivation...............................................................................................................................................................95
8.2.7.1 Using the CME....................................................................................................................................................... 95
8.2.7.2 Using MML Commands......................................................................................................................................... 95
8.2.8 Performance Monitoring............................................................................................................................................95
8.2.9 Parameter Optimization............................................................................................................................................. 95
8.3 TDLOFD-001052 Flash CS Fallback to UTRAN........................................................................................................ 95
8.3.1 When to Use Flash CS Fallback to UTRAN............................................................................................................. 96
8.3.2 Required Information................................................................................................................................................ 96
8.3.3 Requirements............................................................................................................................................................. 97
8.3.4 Precautions.................................................................................................................................................................97
8.3.5 Data Preparation and Feature Activation...................................................................................................................97
8.3.5.1 Data Preparation..................................................................................................................................................... 97
8.3.5.2 Using the CME..................................................................................................................................................... 101
8.3.5.3 Using MML Commands....................................................................................................................................... 101
8.3.6 Activation Observation............................................................................................................................................102
8.3.7 Deactivation.............................................................................................................................................................103
8.6.7 Deactivation.............................................................................................................................................................124
8.6.7.1 Using the CME..................................................................................................................................................... 125
8.6.7.2 Using MML Commands....................................................................................................................................... 125
8.6.8 Performance Monitoring..........................................................................................................................................125
8.6.9 Parameter Optimization........................................................................................................................................... 125
8.7 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering........................................................................................ 125
8.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering............................................................................................. 125
8.7.2 Required Information.............................................................................................................................................. 126
8.7.3 Requirements........................................................................................................................................................... 126
8.7.4 Precautions...............................................................................................................................................................126
8.7.5 Data Preparation and Feature Activation.................................................................................................................127
8.7.5.1 Data Preparation................................................................................................................................................... 127
8.7.5.2 Using the CME..................................................................................................................................................... 128
8.7.5.3 Using MML Commands....................................................................................................................................... 129
8.7.6 Activation Observation............................................................................................................................................129
8.7.7 Deactivation.............................................................................................................................................................130
8.7.7.1 Using the CME..................................................................................................................................................... 130
8.7.7.2 Using MML Commands....................................................................................................................................... 130
8.7.8 Performance Monitoring..........................................................................................................................................131
8.7.9 Parameter Optimization........................................................................................................................................... 131
8.8 TDLOFD-001034 CS Fallback to GERAN................................................................................................................131
8.8.1 When to Use CS Fallback to GERAN.....................................................................................................................131
8.8.2 Required Information.............................................................................................................................................. 131
8.8.3 Requirements........................................................................................................................................................... 132
8.8.4 Precautions...............................................................................................................................................................133
8.8.5 Data Preparation and Feature Activation.................................................................................................................133
8.8.5.1 Data Preparation................................................................................................................................................... 133
8.8.5.2 Using the CME..................................................................................................................................................... 139
8.8.5.3 Using MML Commands....................................................................................................................................... 139
8.8.6 Activation Observation............................................................................................................................................145
8.8.7 Deactivation.............................................................................................................................................................148
8.8.7.1 Using MML Commands....................................................................................................................................... 148
8.8.8 Performance Monitoring..........................................................................................................................................148
8.8.9 Parameter Optimization........................................................................................................................................... 150
8.9 RIM Procedure from E-UTRAN to GERAN............................................................................................................. 151
8.9.1 When to Use RIM Procedure from E-UTRAN to GERAN.................................................................................... 151
8.9.2 Required Information.............................................................................................................................................. 152
8.9.3 Requirements........................................................................................................................................................... 152
8.9.4 Precautions...............................................................................................................................................................152
8.9.5 Data Preparation and Feature Activation.................................................................................................................152
8.9.5.1 Data Preparation................................................................................................................................................... 153
8.9.5.2 Using the CME..................................................................................................................................................... 153
9 Parameters................................................................................................................................... 187
10 Counters.................................................................................................................................... 264
11 Glossary..................................................................................................................................... 300
12 Reference Documents............................................................................................................. 301
13 Appendix................................................................................................................................... 302
13.1 Signaling Procedures Involved in CSFB to UTRAN............................................................................................... 302
13.1.1 Combined EPS/IMSI Attach Procedure................................................................................................................ 302
13.1.2 CSFB Based on PS Handover............................................................................................................................... 303
13.1.3 CSFB Based on Redirection.................................................................................................................................. 305
13.1.4 Flash CSFB............................................................................................................................................................307
13.1.5 Ultra-Flash CSFB to UTRAN............................................................................................................................... 308
13.1.6 Redirection-based CSFB Optimization for UEs in Idle Mode.............................................................................. 311
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:
l TDLOFD-001033 CS Fallback to UTRAN
l TDLOFD-001052 Flash CSFB to UTRAN
l TDLOFD-081223 Ultra-Flash CSFB to UTRAN
l TDLOFD-001068 CS Fallback with LAI to UTRAN
l TDLOFD-001088 CS Fallback Steering to UTRAN
l TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering
l TDLOFD-001034 CS Fallback to GERAN
l TDLOFD-001053 Flash CSFB to GERAN
l TDLOFD-001069 CS Fallback with LAI to GERAN
l TDLOFD-001089 CS Fallback Steering to GERAN
l TDLOFD-081203 Ultra-Flash CSFB to GERAN
This document mainly describes CSFB implementation principles on the E-UTRAN. 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:
l For the GERAN, see CS Fallback Feature Parameter Description in GBSS Feature
Documentation.
l For the UTRAN, see Interoperability Between UMTS and LTE Feature Parameter
Description 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 TDD. Any "LTE" in this document refers to LTE TDD,
and "eNodeB" refers to LTE TDD eNodeB.
Micro BTS3205E
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l 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.
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 the legacy UTRAN or GERAN to provide CS services.
Currently, CSFB and voice over IP (VoIP) over IP multimedia subsystem (IMS) are the two
standard solutions to provide voice services for UEs on LTE networks. 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 Introduction
With the CSFB solution, when a UE initiates a CS service, the mobility management entity
(MME) instructs the UE to fall back to a legacy CS network before the UE performs the
service. CSFB is a session setup procedure. The UE falls back to the CS network before the
CS session is set up, and it stays in the CS network during the CS session. For details, see
3GPP TS 23.272 V8.5.0.
After receiving CS Fallback Indicator, eNodeBs handle CSFB for different types of CS
services in a uniform way. The CS services can be voice services, short message service
(SMS), location service (LCS), and emergency calls.
2.2 Benefits
CSFB offers the following benefits:
l Facilitates voice services for LTE networks.
l Helps operators reduce costs by reusing legacy CS networks with no need to deploy an
IMS network.
Table 2-1 describes the elements of the network architecture in Figure 2-1.
SGs interface l Is an interface between the MME and the mobile switching center
(MSC) server.
l Assists mobility management and paging between the EPS and the
CS network.
l Transmits mobile originated (MO) and mobile terminated (MT)
SMS messages.
l Transmits messages related to combined attach and combined TAU/
LAU. (TAU is short for tracking area update, and LAU is short for
location area update.)
Element Function
To implement CSFB to provide CS services for E-UTRAN, all MSCs that serve overlapping
areas with the E-UTRAN coverage must be upgraded to support functions involving the SGs
interfaces between MSCs and MMEs. These functions include combined attach, combined
TAU/LAU, 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.
MSC l Support combined The requirements are the The requirements are
EPS/CS attach and same as those of R8 PS the same as those of
combined TAU/ redirection. R8 PS redirection.
LAU.
l Support the CSFB
procedure.
l R8 PS redirection
l CCO
If NACC is enabled, the RIM procedure is started during CCO from E-UTRAN to GERAN.
With this procedure, the eNodeB acquires system information about the target cell and
delivers it to the UE. The UE accesses the target cell to initiate a CS service with no need to
read the system information, reducing the delay.
l PS handover
Table 2-3 describes the requirements of the five CSFB mechanisms for networks and UEs.
3 CSFB to UTRAN
This chapter describes each CSFB to UTRAN feature, CSFB procedure, and RIM procedure
between E-UTRAN and UTRAN.
3.1 Overview
CSFB to UTRAN can be implemented in different ways and includes the following features
and functions:
CSFB Procedure
Figure 3-1 shows the CSFB to UTRAN procedure.
NOTE
Unless otherwise specified, blind handling includes PS HO, redirection, and fast redirection for CSFB to
UTRAN and includes PS HO, CCO, NACC, redirection, and fast redirection for CSFB to GERAN in
this document.
NOTE
This feature is also controlled by the UtranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
When a UE initiates a CS service in the E-UTRAN, the MME sends the eNodeB an S1-AP
message containing CS Fallback Indicator, instructing the eNodeB to transfer the UE with the
CS service to a target network. For details about MOC and MTC signaling procedures, see
13.1 Signaling Procedures Involved in CSFB to UTRAN.
NOTE
This feature is also controlled by the UtranFlashCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
UTRAN cells through RIM procedures and then sends UEs the EUTRAN-to-UTRAN
redirection messages that contain the system information. In this way, the UEs access the
UTRAN cells with no need to read the system information in the cells. This reduces the
access delay. For details about how the UTRAN sends the system information to the eNodeB
through RIM procedures, see Flash CS Fallback Based on RIM Feature Parameter
Description.
This feature requires that the eNodeB can obtain UTRAN cell information through the RIM
procedures and the networks and UEs involved should comply with 3GPP Release 9 or later.
For details about the RIM procedure, see 3.7 RIM Procedure Between E-UTRAN and
UTRAN.
Other procedures are the same as those for CS Fallback to UTRAN. For details, see 3.2.1
TDLOFD-001033 CS FallBack to UTRAN.
NOTE
If a UE does not support ultra-flash CSFB, a UE compatibility issue arises. To address this issue, select
the UltraFlashCsfbComOptSw option of the GlobalProcSwitch.UeCompatSwitch parameter.
Application Scenarios
This section describes the optional feature TDLOFD-001068 CS Fallback with LAI to
UTRAN. This feature is under license control but not under switch controll .
This feature works in the following scenarios:
l In a multi-PLMN or national roaming scenario
An LAI consists of a PLMN ID and a location area code (LAC). The PLMN ID
identifies the CS network that a UE has registered with and will fall back to.
If the serving E-UTRAN cell has multiple neighboring UTRAN or GERAN cells with
different PLMN IDs or the serving PLMN differs from the target PLMN, the operator
can use the CSFB with LAI function so that the UE will preferentially fall back to the
PLMN indicated by the LAI.
l In a tracking area (TA) that overlaps multiple location areas (LAs)
To prevent a further LAU after CSFB, the eNodeB selects a CSFB target cell with the
same LAC as that specified for the UE during attach. Therefore, the CSFB delay does
not include the LAU time.
The eNodeB derives the LAI from an Initial Context Setup Req or UE Context Mod Req
message sent by the MME.
Handover Measurement
l Selecting frequencies
During measurement configuration, the eNodeB selects only inter-RAT frequencies on
which the PLMN ID of any 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.
l Selecting neighboring cells
The eNodeB additionally filters neighboring cells in the following order after receiving
measurement reports from a UE:
a. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
b. 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 process is the
same as that when no LAI is received.
Blind Handling
l Selecting frequencies
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. For details, see 3.3
Triggering Events.
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
UEs. For details, see 3.3 Triggering Events.
l Selecting neighboring cells
The neighboring cell selection sequence is controlled by the
LaiCsfbBlindNCellSelSwitch option of the ENodeBAlgoSwitch.HoCommOptSwitch
parameter.
NOTE
When the coverage of an E-UTRAN cell is not completely included in that of a neighboring cell
with a configured blind handover priority, you are advised to select the option, thereby ensuring
the CSFB success rate and reducing the delay.
When the option is selected, the selection sequence is as follows:
a. Neighboring cells with PLMN IDs the same as those in the LAI
b. Neighboring cells with the highest blind-handover priority among a
c. Neighboring cells with LACs the same as those in the LAI among b
When the option is cleared, the selection sequence is as follows:
a. Neighboring cells with PLMN IDs the same as those in the LAI
b. Neighboring cells with LACs the same as those in the LAI among a
c. Neighboring cells with the highest blind-handover priority among b
CS Steering in CSFB
This function is an enhancement to the CS Fallback to UTRAN feature. The enhancements
are as follows:
l Frequencies with the highest CS service priority are preferentially selected for inter-RAT
measurement on the UTRAN.
This function is controlled by the UtranFreqLayerMeasSwitch option of the cell-level
parameter CellAlgoSwitch.FreqLayerSwitch.
NOTE
NOTE
l Enhancement in measurement
a. 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.
b. Among the selected frequencies, the eNodeB selects frequencies with the highest
CS service priority, which is specified by the UtranNFreq.CsPriority parameter.
c. The follow-up measurement procedure is the same as that in CS Fallback to
UTRAN. For details, see 3.4 Target Cell/Frequency Selection.
The difference is that the eNodeB additionally sorts neighboring cells in the following
order after receiving measurement reports from a UE:
a. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
b. Neighboring cells with PLMN IDs the same as that in the LAI but LACs different
from that in the LAI
c. Neighboring cells with PLMN IDs the same as the serving PLMN ID of the UE
l Enhancement in blind handling
a. The eNodeB selects frequencies whose PLMN ID is the same as the PLMN ID in
the LAI.
b. Among the selected frequencies, the eNodeB selects frequencies with the highest
CS service priority, which is specified by the UtranNFreq.CsPriority parameter.
c. The eNodeB selects a neighboring cell whose PLMN ID and LAC are the same as
those in the LAI.
d. 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.
e. The follow-up blind handling procedure is the same as that in CS Fallback to
UTRAN. For details, see 3.4 Target Cell/Frequency Selection.
NOTE
This feature is also controlled by the UtranCsfbSteeringSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
CS-Only UE
The eNodeB selects the target RAT based on the RAT priorities specified by the parameters in
Table 3-1.
Table 3-1 Target RAT priority parameter list for CSFB of CS-only UEs
Target RAT Priority for eNodeB-Level Cell-Level Parameter
CSFB of CS-only UEs Parameter
NOTE
Parameters in the CSFallBackBlindHoCfg MO are eNodeB-level. When you run ADD CNoperator
with CnOperatorId configured to add an operator, parameters in the CSFallBackBlindHoCfg MO are
automatically set to default values. Cell-level parameters for inter-RAT handovers are configured by
running ADD CELLOPHOCFG. When both CSFallBackBlindHoCfg and CellOpHoCfg are
configured, CellOpHoCfg prevails.
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 UTRAN is assigned the highest RAT priority, the eNodeB selects target frequencies based
on the setting of the UtranNFreq.CsPriority parameter. For details, see 3.2.5
TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering.
The eNodeB selects the handover policy for CSFB of CS-only UEs based on the setting of the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. PS handover takes priority
over redirection.
CS+PS UE
If the UE is a CS+PS UE, the eNodeB selects the target RAT based on the RAT priorities
specified by the parameters in Table 3-2.
Table 3-2 Target RAT priority parameter list for CSFB of CS+PS 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 UTRAN is assigned the highest RAT priority, the eNodeB selects 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.2.5 TDLOFD-001078 E-UTRAN to UTRAN CS/PS
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.
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.7 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.2.1 TDLOFD-001033
CS FallBack to UTRAN.
When selecting a target cell for CSFB to UTRAN, the eNodeB considers UTRAN cells in the
following priority order of load status: normal, congested, and overloaded.
Load-based CSFB to UTRAN affects the target cell selection at a later phase. In the
measurement phase, if necessary, cell load status does not affect frequency selection: The
eNodeB does not select a low-priority frequency because all UTRAN cells on a high-priority
frequency are overloaded.
Measurement Triggering
During CSFB, the eNodeB starts UTRAN measurements after it receives a CS Fallback
Indicator. The measurement configuration procedure is the same as that for coverage-based
handovers from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility Management in
Connected Mode.
They have different thresholds and time-to-trigger. Table 3-3 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.
The procedure shown in Figure 3-2 involves the following data configuration and
activities:
Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
The CS service priority is specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details about this parameter, see
3.2.5 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering and 3.2.6
TDLOFD-001088 CS Fallback Steering to UTRAN.
The priorities of neighboring UTRAN frequencies for connected-mode UEs are
specified by the UtranNFreq.ConnFreqPriority parameter.
The measurement priority for neighboring UTRAN cells can be automatically
optimized by ANR. The UTRAN_SWITCH option of the
ENodeBAlgoSwitch.NCellRankingSwitch parameter controls the automatic
optimization function. It is recommended that this option be selected only if ANR is
enabled.
n If this option is selected, the eNodeB automatically optimizes the
UtranNCell.NCellMeasPriority parameter for neighboring UTRAN cells.
This parameter cannot be modified manually. For details, see ANR
Management Feature Parameter Description.
n If this option is deselected, the measurement priority is specified by the
UtranNCell.CellMeasPriority parameter, which must be configured manually.
When the eNodeB selects highest-priority frequencies or cells, the number of
frequencies or cells selected is equal to the number of candidates if the number does
not exceed the maximum permissible number. If the number of candidates exceeds
the maximum permissible number, the eNodeB randomly selects the maximum
permissible number of frequencies or cells from the candidates.
The maximum permissible number of frequencies is specified by the
CellUeMeasControlCfg.MaxUtranTddMeasFreqNum parameter.
The maximum permissible number of neighboring cells is defined in section 6.4
"RRC multiplicity and type constraint values" of 3GPP TS 36.331 V10.1.0.
If CSFallBackBlindHoCfg.InterRatHighestPri or CellOpHoCfg.InterRatHighestPri
is set to UTRAN, the eNodeB performs CSFB to UTRAN.
2. The eNodeB filters frequencies and cells.
During target selection, the eNodeB filters the frequencies configured on it. It filters out
the frequencies not supported by the UE and then filters out the following neighboring
cells on the remaining frequencies:
Blacklisted neighboring cells
Neighboring cells to which handovers are prohibited as indicated by the No
handover indicator parameter for cells in neighboring cell lists
Neighboring cells with different PLMN IDs from the serving cell in neighboring
cell lists (If the inter-PLMN handover switch is on, the eNodeB does not filter out
these neighboring cells.)
Cells to which handovers are prohibited as indicated by the Handover Restriction
List IE in the INITIAL CONTEXT SETUP REQUEST message sent from the
MME
3. The eNodeB selects the target cell or frequency.
Before the eNodeB can select a cell as the target cell for the blind handover from E-
UTRAN to UTRAN, the neighboring UTRAN cell must be configured on the
eNodeB and be assigned a blind-handover priority. Figure 3-3 shows the procedure
for selecting the target cell for a blind handover.
The procedure shown in Figure 3-3 involves the following data configuration and
activities:
n The CS service priority is specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details about this parameter,
see 3.2.5 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering and 3.2.6
TDLOFD-001088 CS Fallback Steering to UTRAN.
n Neighboring UTRAN cells are configured in UtranNCell MOs.
n The blind-handover priorities of neighboring UTRAN cells are specified by
the UtranNCell.BlindHoPriority parameter.
n If there is more than one highest-priority frequency or neighboring cell, the
eNodeB randomly selects one.
Before the blind redirection from E-UTRAN to UTRAN, neighboring UTRAN
frequencies and their priorities for connected-mode UEs must be configured.
Neighboring UTRAN cell configurations are not required. Figure 3-4 shows the
procedure for selecting the target frequency for blind redirection.
The procedure shown in Figure 3-4 involves the following data configuration and
activities:
n Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
n The priorities of neighboring UTRAN frequencies for connected-mode UEs
are specified by the UtranNFreq.ConnFreqPriority parameter.
n The CS service priority is specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details about this parameter,
see 3.2.5 TDLOFD-001078 E-UTRAN to UTRAN CS/PS Steering and 3.2.6
TDLOFD-001088 CS Fallback Steering to UTRAN.
n Neighboring UTRAN cells are configured in UtranNCell MOs.
n The eNodeB selects a frequency from the candidates based on blind-handover
priorities of neighboring cells as follows:
If neighboring cells are assigned non-zero blind-handover priorities,
which is specified by UtranNCell.BlindHoPriority, the eNodeB selects
the operating frequency of the cell with the highest blind-handover
priority.
If all neighboring cells are assigned blind-handover priority 0, the
eNodeB considers frequency priorities for connected-mode UEs It
3.5 Decision
In the decision phase, the eNodeB checks the candidate cell list. Based on the check result, the
eNodeB determines whether a CSFB needs to be initiated and, if so, to which cell the UE is to
be fallen back to.
The candidate cell list generated for CSFB is controlled by the
CellHoParaCfg.L2UCsfbMRProMode parameter.
This parameter has three values: HANDOVERIMMEDIATELY,
BASEDONSIGNALSTRENGTH, and BASEDONFREQPRIORITY. Figure 3-5 shows
the candidate cell list generation procedure when parameter configurations are different.
The eNodeB sends a handover request to the target cell. If the handover request fails, the
eNodeB sends the handover request to the next target cell, as described in Table 3-5.
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.
3.6 Execution
In the execution phase, the eNodeB controls the fallback of the UE from the source cell to the
target cell or frequency.
l If blind redirection for CSFB is required, select the REDIRECTION option of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.
l The CSFB protection timer is specified by the CSFallBackHo.CsfbProtectionTimer
parameter.
If the UE does not send inter-RAT measurement reports and stays in the area covered by
the eNodeB when the timer expires, the eNodeB performs redirection for CSFB.
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.
The eNodeB preferentially selects the operating frequency of a cell to which the
eNodeB has never attempted to hand over the UE as the target frequency for
redirection.
If there is no target frequency available for redirection, the eNodeB stops the
procedure.
If flash CSFB is enabled in this situation, redirection performed by the eNodeB is
referred to as emergency redirection for CSFB. In this scenario, operators must
must set the InterRatHoComm.UtranCellNumForEmcRedirect parameter to
specify the maximum number of UTRAN cells that can be included in an
emergency redirection message.
l The eNodeB selects the target cell for redirection as it does during blind handling. For
details about the selection, see 3.4 Target Cell/Frequency Selection.
Blind handover 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 both options are selected.
Adaptive blind handover for CSFB is controlled by the
CsfbAdaptiveBlindHoSwitch option of the cell-level parameter
CellAlgoSwitch.HoAllowedSwitch.
NOTE
This function is also controlled by the UtranPsHoSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoModeSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level
parameter is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to
use the cell-level parameter.
l During a blind PS handover for CSFB, if the handover preparation in the target cell with
the highest blind handover priority fails, the eNodeB tries the cell with the second
highest blind handover priority. The eNodeB can try a maximum of eight cells. If all
these cells fail in handover preparation, the eNodeB performs emergency blind
redirection.
For details about the signaling procedure for redirection-based CSFB optimization for UEs in
idle mode, see 13.1.6 Redirection-based CSFB Optimization for UEs in Idle Mode.
NOTE
When the optimization switch is turned on and CSFB with LAI to UTRAN or GERAN is enabled, it is
recommended that the RsvdSwPara1_bit25 option of the ENBRsvdPara.RsvdSwPara1 parameter be
selected to prevent function conflicts.
To increase the CSFB success rate in this scenario, the eNodeB can preferentially admit CSFB
UEs. This function is controlled by the CSFallBackPolicyCfg.CsfbUserArpCfgSwitch
parameter.
If the emergency blind redirection procedure for CSFB is triggered, the eNodeB does not
consider whether the target cell is penalized during target cell selection.
In CSFB procedures, an eNodeB obtains the load information of external UTRAN cells from
RNCs through the RIM procedure. When the GlobalProcSwitch.UtranLoadTransChan
parameter is set to BASED_ON_RIM, the eNodeB obtains UTRAN cell load information
through the RIM procedure for target cell selection.
In flash CSFB procedures, an eNodeB obtains the system information (SI) of UTRAN cells
from RNCs through the RIM procedure.
The RIM procedure may use one of the following information exchange modes:
l 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 activated, the eNodeB sends a RIM request to the RNC
and then includes the obtained SI in a redirection message to the UE. If the eNodeB fails
to obtain SI from the RNC, the eNodeB no longer sends the RIM request.
l Multiple Report
Currently, the eNodeB triggers a RIM procedure in Multiple Report mode only if MMEs
comply with 3GPP Release 9 or later.
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 enabled, the eNodeB sends RIM requests to all
neighboring UTRAN cells every 4 seconds no matter whether the eNodeB has CSFB
services.
To ensure that the SI of a UTRAN neighboring cell can be obtained successfully, the
eNodeB starts a 4s timer when it sends a RIM request.
If the eNodeB receives a response to the RIM request before the timer expires, the
eNodeB saves the obtained SI.
If the eNodeB receives a response to the RIM request after the timer expires, the
eNodeB considers that an exception has occurred and discards the SI.
If the eNodeB does not receive a response to the RIM request even after the timer
expires, the eNodeB sends the RIM request and starts the timer again (called a
retry) 2 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
number of the retries n. For example, the first retry occurs 2 hours after the first SI
acquisition fails, the second retry occurs 4 hours after the first retry fails, and the
third retry occurs 6 hours after the second retry fails. For each retry, the eNodeB
sends a RIM request and restarts the timer.
The eNodeB may obtain incorrect SI due to errors in the UTRAN, core network, or
transport network. To avoid this situation, the eNodeB randomly selects a time point
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 the eNodeB an
END message, instructing the eNodeB to stop the RIM procedure. The eNodeB then
deletes the obtained SI and requests SI again in the next RIM procedure.
The RIM procedure can be performed through the core network or eCoordinator.
In Figure 3-9:
l The UTRAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter
controls the RIM procedure between E-UTRAN and UTRAN.
If this option is selected, the eNodeB uses the RIM procedure in Multiple Report mode
to obtain the SI of external UTRAN cells.
l The UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter specifies whether UTRAN operators
can use different mobility policies.
l The UtranNetworkCapCfg.NetworkCapCfg parameter specify the capability of SI
acquisition through RIM. If the capability is not configured for an operator or RNC, it is
supported by default.
Figure 3-9 Information exchange mode selection for the RIM procedure
The RIM procedure through the eCoordinator requires that the corresponding switches of this
function be on at all these NEs.
During this RIM procedure, each NE does not send RIM messages to the core network or
process RIM messages from the core network.
The information exchange mode for the eCoordinator-based RIM procedure is controlled by
UTRAN_RIM_SWITCH of the ENodeBAlgoSwitch.RimSwitch parameter.
l If this switch is on, the eNodeB uses the RIM procedure in Multiple Report mode to
obtain the SI of external UTRAN cells.
l If this switch is off, the eNodeB uses the RIM procedure in Single Report mode.
4 CSFB to GERAN
This chapter describes each CSFB to GERAN feature, CSFB procedure, and RIM procedure
between E-UTRAN and GERAN.
4.1 Overview
CSFB to GERAN can be implemented in different ways, and this chapter covers the following
features:
l TDLOFD-001034 CS Fallback to GERAN
l TDLOFD-001053 Flash CS Fallback to GERAN
l TDOFD-001069 CS Fallback with LAI to GERAN
l TDLOFD-001089 CS Fallback Steering to GERAN
l TDLOFD-081203 Ultra-Flash CSFB to GERAN
Figure 4-1 shows the CSFB to GERAN procedure.
NOTE
This feature is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
This feature has the same principles as CS Fallback to UTRAN, except the preceding
parameters. For details about the principles, see 3.2.1 TDLOFD-001033 CS FallBack 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 Handling
If the eNodeB-level CSFallBackBlindHoCfg.InterRatHighestPri parameter or cell-level
CellOpHoCfg.InterRatHighestPri parameter is set to GERAN(GERAN), the eNodeB
performs CSFB to GERAN. In case that both eNodeB- and cell-level parameters are
configured, the cell-level parameter settings prevail.
During blind handling, the target RAT selection procedure is different, depending on whether
neighboring GERAN cells are configured.
l 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 handling. A
larger value indicates a higher priority.
If the priorities of neighboring cells or frequencies are the same, the eNodeB
randomly selects a target cell or frequency. Due to uncertainty of random selection,
you are not advised to set the priorities to the same to ensure the blind handover
success.
l 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.
NOTE
This feature is also controlled by the GeranFlashCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
With this feature, UEs access the GERAN cells with no need to read the system information
in the cells. This reduces the access delay. For details about how the GERAN sends the
system information to the eNodeB through RIM procedures, see Interoperability Between
GSM and LTE.
This feature has the same principles as Flash CS Fallback to UTRAN. For details, see 3.2.2
TDLOFD-001052 Flash CS Fallback to UTRAN.
This feature has the same principles as CS Fallback with LAI to UTRAN. For details, see
3.2.4 TDLOFD-001068 CS Fallback with LAI to UTRAN.
NOTE
This feature is also controlled by the GeranCsfbSteeringSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
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.2.6 TDLOFD-001088 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
handover, CCO, or redirection in descending order of priority.
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 handover, CCO,
or redirection in descending order of priority.
To increase the probability of the UE entering sleep time, set DRX parameters to achieve a
longer sleep time. However, this setting affects scheduling and therefore decreases cell
throughput.
For details about how to configure measurement-specific DRX parameters, see DRX and
Signaling Control.
NOTE
If a UE does not support ultra-flash CSFB, a UE compatibility issue arises. To address this issue, select
the UltraFlashCsfbComOptSw option of the GlobalProcSwitch.UeCompatSwitch parameter.
4.3 Triggering
CSFB triggering is classified into measurement triggering and blind handling triggering. For
details, see 3.3 Triggering Events.
l When the GSM measurement is triggered by CSFB, the eNodeB releases all the inter-
frequency measurement.
l After the GSM measurement is triggered by CSFB, starting the inter-frequency
measurement is forbidden.
Unlike the UTRAN frequency selection, in the GERAN frequency selection, if the total
number of GERAN frequencies in the highest-priority frequency group to be delivered and
frequencies that have been delivered exceeds the maximum number 32, the eNodeB does not
deliver any frequency in this group. The eNodeB then evaluates whether to deliver the
GERAN frequencies in the frequency group with the second highest priority. The evaluation
stops when the number of delivered frequencies is less than or equal to the maximum number
or all frequency groups have been evaluated.
For CSFB to GERAN, no cell measurement priority is configured. If the number of cells on a
frequency exceeds the maximum permissible number, the eNodeB randomly selects cells for
measurement.
The target RAT selection procedure varies depending on whether neighboring GERAN cells
have been configured.
l If neighboring GERAN cells have been configured, the eNodeB selects a target cell with
the highest blind handover priority or a target frequency group with the highest priority
for connected-mode UEs.
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 priority for connected-mode UEs is specified by the
GeranNfreqGroup.ConnFreqPriority parameter. A larger value indicates a higher
priority.
If neighboring cells or frequencies have the same priority, the eNodeB randomly
selects one. To prevent uncertainty of random selection and increase the success
rate of blind handovers, you are not advised to set an identical priority for cells or
frequencies.
l If no neighboring GERAN cell has been configured:
Neighboring GERAN frequency groups are configured in GeranNfreqGroup
MOs.
The PLMN information about neighboring GERAN frequencies is contained in the
GeranRanShare or GeranExternalCell MOs.
4.5 Decision
The decision for CSFB to GERAN is the same as that for CSFB to UTRAN. For details, see
3.5 Decision.
4.6 Execution
When a UE in an LTE network needs to perform a voice service but the LTE network does not
support VoLTE, a procedure of CSFB to an inter-RAT network is triggered.
During a blind PS handover for CSFB, if the handover preparation in the target cell with the
highest blind handover priority fails, the eNodeB tries the cell with the second highest blind
handover priority. The eNodeB can try a maximum of eight cells. If all these cells fail in
handover preparation, the eNodeB performs emergency blind redirection.
Figure 4-3 Information exchange mode selection for the RIM procedure
When the UE in connected mode initiates the CSFB procedure during S1/X2-based handover
preparation, the CSFB procedure conflicts with the handover procedure. The eNodeB
preferentially processes the handover procedure and responds to the MME with a CSFB call
request failure message. After the handover is complete, the MME re-sends a CSFB request
message to the eNodeB to re-initiate the CSFB procedure, as stipulated by 3GPP TS 23.401.
If the MME cannot re-send the CSFB reestablishment request in such a scenario, the CSFB
call fails.
When a UE attaching to the network or in idle mode initiates a TAU procedure, a default
bearer is established. The eNodeB considers the UE in connected mode and allows the
handover procedure before completing the Attach or TAU procedure. However, the MME
allows the handover procedure only after the attach or TAU procedure is completed.
Therefore, the MME identifies the handover request from the eNodeB as inappropriate and
discards it. The eNodeB waits for the handover request response for 20s (default value
specified by the timer). If the eNodeB receives the UE CONTEXT MODIFICATION
REQUEST message with the CS Fallback Indicator IE from the MME, the eNodeB rejects the
CSFB request and therefore the CSFB call fails.
To solve CSFB call failure problems in the preceding scenarios, the eNodeB needs to
preferentially process the CSFB procedure upon the conflict. Select the
CsfbFlowFirstSwitch option of the GlobalProcSwitch.HoProcCtrlSwitch parameter so that
the eNodeB preferentially processes the CSFB procedure during handover preparation. If the
eNodeB receives the UE CONTEXT MODIFICATION REQUEST message with the CS
Fallback Indicator IE before handover indication is transmitted over the air interface, the
eNodeB sends the HANDOVER CANCEL message to the MME to cancel the handover
procedure and prioritize the CSFB procedure.
NOTE
When the CSFB procedure conflicts with the inter-eNodeB reestablishment with no context, the eNodeB
preferentially processes the reestablishment procedure.
6 Related Features
Impacted Features
Feature ID Feature Name Description
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
Feature ID Feature Name Description
Impacted Features
None
Impacted Features
Feature ID Feature Name Description
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
Feature ID Feature Name Description
7 Network Impact
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 increases the CSFB delay.
CSFB affects the access success rate as follows:
l 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.
l 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.
l 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.
l 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.
l 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.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to UTRAN by 1
second, improving user experience.
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.
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.
Network Performance
E-UTRAN to UTRAN CS/PS Steering enables an eNodeB to include only UTRAN
frequencies with the highest CS service priority in measurement configurations. This prevents
redundant measurements, reduces the measurement time, and decreases end-to-end CSFB
delay.
Consistent settings of the CS service priorities for UTRAN frequencies between the E-
UTRAN and the UTRAN help prevent further handovers for service steering after CSFB.
l 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.
l If CCO with NACC is used as the CSFB mechanism, extra signaling messages are
required only during eNodeB deployment.
l 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:
CSFB mechanisms affect 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.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to GERAN by 2s,
improving user experience.
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.
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.
8 Engineering Guidelines
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.
8.1.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-2.
8.1.4 Precautions
None
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 serves the external
UTRAN cell works in RAN sharing with common carriers mode and multiple operators
share the external UTRAN cell.
4. UtranNCell: used 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 CellHoParaCfg and
CellAlgoSwitch MOs to set the cell-level handover mode and handover allowed switches for
CS Fallback to UTRAN.
Handover CellHoP Network Set this parameter based on the network plan.
Mode araCfg. plan To activate PS handovers, select the
switch HoMode (negotiation UtranPsHoSwitch(UtranPsHoSwitch) option. If
Switch not this option is not selected, redirection will be used
required) for CSFB to UTRAN.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellHoParaCfg MOs to set eNodeB- and cell-level blind handover switches.
Handover CellHo Network To activate blind handovers for a cell under the
Mode ParaCf plan eNodeB, select the
switch g.HoMo (negotiation BlindHoSwitch(BlindHoSwitch) option of the
deSwitc not parameter. If the BlindHoSwitch(BlindHoSwitch)
h required) option is cleared, blind handovers for the cell are
invalid.
The following table describes the parameters that must be set in the CellAlgoSwitch and
CSFallBackHo MOs to set the switch for cell-level adaptive blind handover for CSFB and
the A1 threshold for adaptive blind handover for CSFB.
Handove CellAlg Network When UMTS and LTE cells are co-sited with the
r oSwitch plan same coverage, you can enable
Allowed .HoAllo (negotiation CsfbAdaptiveBlindHoSwitch. The eNodeB selects
Switch wedSwit not a measurement or blind handover to UMTS based
ch required) on the event A1 report submitted by a UE.
CSFB CSFall Network This parameter specifies the RSRP threshold of the
Adaptive BackHo plan serving cell above which a CSFB-triggered adaptive
Blind Ho .BlindH (negotiation blind handover is triggered. If the RSRP value
A1 RSRP oA1Thd not measured by a UE exceeds this threshold, the UE
Trigger Rsrp required) submits a event A1 report. If the eNodeB receives
Threshol an event A1 report, it directly enters the blind
d handling procedure. If the eNodeB does not receive
an event A1 report (the UE is located at the edge of
the E-UTRAN cell), it enters the measurement
procedure. The target measurement RAT depends on
configured RAT priorities and UE capabilities.
On the live network, set this parameter based on
network coverage.
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.
CN CSFallBack Networ Set this parameter based on the network plan. This
Operat BlindHoCfg. k plan parameter identifies the operator whose RAT blind-
or ID CnOperatorI (negoti handover priorities are to be set.
d ation
not
require
d)
Highes CSFallBack Networ Set this parameter based on the network plan. This
t BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
priority InterRatHig (negoti the highest-priority RAT to be considered in blind
InterRa hestPri ation handovers for CSFB. For CSFB to UTRAN, retain the
t not default value.
require
d)
Second CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to GERAN by default and specifies
InterRa InterRatSeco (negoti the second-highest-priority RAT to be considered in
t ndPri ation blind handovers for CSFB. Ensure that this parameter
not is set to a different value from the CSFallBackBlind-
require HoCfg.InterRatHighestPri and CSFallBackBlind-
d) HoCfg.InterRatLowestPri parameters.
Lowest CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to CDMA2000 by default and
InterRa InterRatLow (negoti specifies the lowest-priority RAT to be considered in
t estPri ation blind handovers for CSFB. Ensure that this parameter
not is set to a different value from the CSFallBackBlind-
require HoCfg.InterRatHighestPri and CSFallBackBlind-
d) HoCfg.InterRatSecondPri parameters.
UTRA CSFallBack Networ Set this parameter based on the network plan. This
N LCS BlindHoCfg. k plan parameter specifies the LCS capability of the
capabil UtranLcsCa (negoti UTRAN.
ity p ation
not
require
d)
The following table describes the parameters that must be set in the CellOpHoCfg MO to set
cell-level handover priorities of different RATs for CSFB.
Local cell CellOpHoCfg. Network Set this parameter based on the network
ID LocalCellId plan plan. This parameter identifies the cell
(negotiation whose RAT blind-handover priorities are to
not be set.
required)
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to activate load-based CSFB.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
set load-based CSFB to UTRAN.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.
CSFB CSFallBack Network plan Set this parameter based on the network
Protection Ho.CsfbPro (negotiation not plan. The default value 4 applies to a
Timer tectionTime required) GSM+UMTS+LTE network. The value
r 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 CSFallBackPolicyCfg
MO to specify the CSFB policy.
CSFB CSFallBack Network plan Set this parameter based on the network plan.
hando PolicyCfg.Cs (negotiation The default values are REDIRECTION,
ver fbHoPolicyC not required) CCO_HO, and PS_HO. You are advised to set
policy fg this parameter based on the UE capabilities and
Config network capabilities.
uratio NOTE
n 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.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
control redirection-based CSFB optimization for UEs in idle mode.
The following table describes the parameter that must be set in the CSFallBackBlindHoCfg
MO to set the round-robin switch when multiple frequencies are of the same priority for
CSFB-based blind redirections.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
set the CSFB frequency selection optimization switch.
The following table describes the parameters that must be set in the CellHoParaCfg MO to
configure the measurement report processing and waiting functions.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
set the policy for handling the conflicts between handover and CSFB procedures.
CSFB to UTRAN using blind redirection works regardless of whether neighboring UTRAN
cells are configured.
l If you want to configure a neighboring UTRAN cell, you must configure the
UtranNFreq and UtranNCell MOs. For details about parameter settings, see Inter-RAT
Mobility Management in Connected Mode.
l 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.
This function is also controlled by the UtranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will not be used in later versions. Therefore, it is recommended that the
eNodeB-level parameter be turned off and the cell-level parameter be used.
Step 2 Run the following eNodeB- and cell-level commands to enable blind handovers for CSFB to
UTRAN:
1. Run the MOD ENODEBALGOSWITCH command with the
BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter
selected.
2. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter cleared and the
REDIRECTION option of the same parameter selected.
Step 4 (Optional) If you require UTRAN to have the highest priority for CSFB, run the following
eNodeB- and cell-level commands:
1. Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority
InterRat and Second priority InterRat parameters set to UTRAN and GERAN,
respectively.
2. Run the ADD CELLOPHOCFG command with the Highest priority InterRat and
Second priority InterRat parameters set to UTRAN and GERAN, respectively.
Step 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).
Step 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).
----End
Step 1 Run MML commands to configure neighboring UTRAN frequencies and UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
This function is also controlled by the UtranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will not be used in later versions. Therefore, it is recommended that the
eNodeB-level parameter be turned off and the cell-level parameter be used.
Step 3 Run the following eNodeB- and cell-level commands to enable blind handovers for CSFB to
UTRAN:
1. Run the MOD ENODEBALGOSWITCH command with the
BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter
selected.
2. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
This function is also controlled by the UtranPsHoSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoModeSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will not be used in later versions. Therefore, it is recommended that the
eNodeB-level parameter be turned off and the cell-level parameter be used.
Step 5 Run the MOD UTRANNCELL command with the Blind handover priority parameter set
to 32.
----End
Step 1 Run MML commands to configure neighboring UTRAN frequencies and UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
NOTE
This function is also controlled by the UtranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will not be used in later versions. Therefore, it is recommended that the
eNodeB-level parameter be turned off and the cell-level parameter be used.
Step 3 Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter cleared and the
REDIRECTION option of the same parameter selected.
----End
Basic scenario 4: CSFB to UTRAN using measurement-based handovers
Step 1 Run MML commands to configure neighboring UTRAN frequencies and UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
Step 2 Run the MOD CELLALGOSWITCH command with the
UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Allowed Switch parameter
selected.
NOTE
This function is also controlled by the UtranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will not be used in later versions. Therefore, it is recommended that the
eNodeB-level parameter be turned off and the cell-level parameter be used.
Step 3 Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
Step 5 Run the MOD CELLHOPARACFG command with the
UtranPsHoSwitch(UtranPsHoSwitch) option of the Handover Mode switch parameter
selected.
NOTE
This function is also controlled by the UtranPsHoSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoModeSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will not be used in later versions. Therefore, it is recommended that the
eNodeB-level parameter be turned off and the cell-level parameter be used.
----End
Enhanced scenario 1: 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:
Step 2 Run the MOD GLOBALPROCSWITCH command with the Choose UTRAN Cell Load
Info Trans Channel parameter set to BASED_ON_RIM.
----End
----End
Enhanced scenario 3: Policy setting for handling the conflicts between handover and CSFB
procedures
To enable the eNodeB to process the CSFB procedure first, run the following command after
the commands in a basic scenario are executed:
Step 1 Run the MOD GLOBALPROCSWITCH command with the CsfbFlowFirstSwitch option
of the Handover Process Control Switch parameter selected.
----End
Basic scenario 1: CSFB to UTRAN using blind redirection (configured with no neighboring
UTRAN cell)
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch= UtranCsfbSwitch-1;
MOD ENODEBALGOSWITCH: HoModeSwitch=BlindHoSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
MOD CELLOPHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN;
MOD UTRANNFEQ: LocalCellId=0, UtranDlArfcn=9700, ConnFreqPriority=8;
MOD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=9700, Mcc="460", Mnc="20";
MOD GLOBALPROCSWITCH: ProtocolMsgOptSwitch=IdleCsfbRedirectOptSwitch-1;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;
Enhanced scenario 3: Policy setting for handling the conflicts between handover and CSFB
procedures
To enable the eNodeB to process the CSFB procedure first, run the following command after
the commands in a basic scenario are executed:
MOD GLOBALPROCSWITCH:HoProcCtrlSwitch= CsfbFlowFirstSwitch-1;
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 provide
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.
Figure 8-1 and Figure 8-2 show sample procedures for CSFB to UTRAN for a mobile-
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.
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 8-3, 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 8-3 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 8-4 shows the PS handover procedure. As shown in the
red and green boxes in Figure 8-5, in the handover command sent over the air interface, the
cs-FallbackIndicator IE is TRUE and the target RAT is UTRAN.
If the neighboring UTRAN cell load status is displayed, load-based CSFB has been activated.
Counter Observation
Table 8-3 lists the performance counters for observing functions related to CSFB to UTRAN.
8.1.7 Deactivation
Table 8-4 describes the parameters for deactivating this feature.
Table 8-7 lists the counters that indicate whether CSFB is performed through redirection or
handover.
After the CSFB protection timer expires, the eNodeB may perform a blind redirection to enter
the protection procedure. Table 8-8 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 8-8 Counter related to the number of times that the eNodeB enters the protection
procedure for CSFB
Counter ID Counter Name Description
Table 8-9 lists the counters related to CSFB for emergency calls.
The formula for calculating the CSFB handover success rate for emergency calls is as
follows:
l If GSM devices are provided by Huawei, for details about processing at the GSM side,
see Interoperability Between GSM and LTE Feature Parameter Description.
l If UMTS devices are provided by Huawei, for details about processing at the UMTS
side, see Interoperability Between UMTS and LTE Feature Parameter Description.
The following table describes the parameters in the CSFallBackBlindHoCfg MO used to set
the blind-handover priorities of different RATs for CSFB.
Highest CSFallBac Network Set this parameter based on the network plan.
priority kBlindHo plan This parameter is set to UTRAN by default and
InterRat Cfg.InterR (negotiatio specifies the highest-priority RAT to be
atHighestP n not considered in blind handovers for CSFB.
ri required)
Second CSFallBac Network Set this parameter based on the network plan.
priority kBlindHo plan This parameter is set to GERAN by default and
InterRat Cfg.InterR (negotiatio specifies the second-highest-priority RAT to be
atSecondP n not considered in blind handovers for CSFB. Ensure
ri required) that this parameter is set to a different value from
the CSFallBackBlindHoCfg.InterRatHighest-
Pri and CSFallBackBlind-
HoCfg.InterRatLowestPri parameters.
Lowest CSFallBac Network Set this parameter based on the network plan.
priority kBlindHo plan This parameter is set to CDMA2000 by default
InterRat Cfg.InterR (negotiatio and specifies the lowest-priority RAT to be
atLowestPr n not considered in blind handovers for CSFB. Ensure
i required) that this parameter is set to a different value from
the CSFallBackBlindHoCfg.InterRatHighest-
Pri and CSFallBackBlind-
HoCfg.InterRatSecondPri parameters.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellHoParaCfg MOs to set eNodeB- and cell-level blind handovers.
Handover CellHoPar Network To activate blind handovers for a cell under the
Mode switch aCfg.HoM plan eNodeB, select the
odeSwitch (negotiati BlindHoSwitch(BlindHoSwitch) option of the
on not parameter. If the
required) BlindHoSwitch(BlindHoSwitch) option is
cleared, blind handovers for the cell are invalid.
Local cell CSFallBac Network Set this parameter based on the network plan.
ID kHo.Local plan
CellId (negotiatio
n not
required)
CSFB CSFallBac Network Set this parameter based on the network plan. This
Utran kHo.CsfbH plan parameter specifies the time-to-trigger for event
EventB1 oUtranTim (negotiatio B1 in CSFB to UTRAN. When CSFB to UTRAN
Time To eToTrig n not is required, set this parameter, which is used by
Trig required) 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.
CSFB CSFallBac Network Set this parameter based on the network plan. This
UTRAN kHo.CsfbH plan parameter specifies the RSCP threshold for event
EventB1 oUtranB1T (negotiatio B1 in CSFB to UTRAN. When CSFB to UTRAN
RSCP hdRscp n not is required, set this parameter, which is used by
Trigger required) UEs as one of the conditions for triggering event
Threshold 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 CSFallBac Network Indicates the Ec/No threshold for event B1, which
UTRAN kHo.CsfbH plan is used in CS fallback to UTRAN. When CSFB to
EventB1 oUtranB1T (negotiatio UTRAN is required, set this parameter, which is
ECN0 hdEcn0 n not used by UEs as one of the conditions for
Trigger required) triggering event B1. This parameter specifies the
Threshold 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.
l Both the eNodeB and the RNC/BSC are provided by Huawei and are connected to the
same eCoordinator.
l 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.
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).
If load-based CSFB to UTRAN is used, you need to obtain load information about UTRAN
cells through the RIM procedures. If flash CSFB to UTRAN is used, you need to obtain
system information about UTRAN cells through the RIM procedures.
8.2.3 Requirements
Operating Environment
If the RIM procedure is performed through the core network, the core-network equipment
must support this feature:
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 9.
Check that software versions for the EPC are correct.
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
The operator has purchased and activated the licenses for the features listed in Table 8-10.
NOTE
If the UTRAN uses Huawei devices, corresponding licenses need to be activated. For details, see the
engineering guidelines for WRFD-150231 RIM Based UMTS Target Cell Selection for LTE in
Interoperability Between UMTS and LTE Feature Parameter Description.
8.2.4 Precautions
None
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The required data is the same as that for TDLOFD-001033 CS Fallback to UTRAN. For
details, see 8.1.5.1 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to configure the RIM procedure.
Table 8-11 Counters related to the RIM procedure between E-UTRAN and UTRAN
Counter ID Counter Name Description
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.
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-INFORMATION IE to the SGSN, you can infer that the RNC
can response to the RIM request normally.
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.
----End
If the RIM procedure is performed through the eCoordinator, trace signaling messages as
follows:
Check whether the ENB DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-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.
If after receiving the ECO DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-REQUEST IE, the RNC sends the RNC DIRECT INFORMATION
TRANSFER message containing the RAN-INFORMATION IE to the eCoordinator, you can
infer that the RNC can response to the RIM request normally.
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.
----End
8.2.7 Deactivation
Table 8-12 describes the parameters for deactivating this feature.
8.3.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 9.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-14.
NOTE
If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN. For
details, see Flash CS Fallback Based on RIM Feature Parameter Description.
8.3.4 Precautions
None
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. 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 serves the external
UTRAN cell works in RAN sharing with common carriers mode and multiple operators
share the external UTRAN cell.
4. UtranNCell: used 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 CellAlgoSwitch,
CellHoParaCfg, and ENodeBAlgoSwitch MOs to set the handover mode and handover
algorithm switches for flash CSFB to UTRAN.
Handover CellHoPara Network plan Set this parameter based on the network
Mode switch Cfg.HoMod (negotiation plan.
eSwitch not required)
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellHoParaCfg MOs to set eNodeB- and cell-level blind handover switches.
Handove CellHo Network To activate blind handovers for a cell under the
r Mode ParaCf plan eNodeB, select the
switch g.HoMo (negotiation BlindHoSwitch(BlindHoSwitch) option of the
deSwitc not parameter. If the BlindHoSwitch(BlindHoSwitch)
h required) option is cleared, blind handovers for the cell are
invalid.
The following table describes the parameter that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
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.
CN Operator CSFallB Network Set this parameter based on the network plan.
ID ackBlind plan This parameter identifies the operator whose
HoCfg.C (negotiation RAT blind-handover priorities are to be set.
nOperato not required)
rId
Highest CSFallB Network Set this parameter based on the network plan.
priority ackBlind plan This parameter is set to UTRAN by default
InterRat HoCfg.In (negotiation and specifies the highest-priority RAT to be
terRatHi not required) considered in blind handovers for CSFB. For
ghestPri CSFB to UTRAN, retain the default value.
Second CSFallB Network Set this parameter based on the network plan.
priority ackBlind plan This parameter is set to GERAN by default
InterRat HoCfg.In (negotiation and specifies the second-highest-priority RAT
terRatSec not required) to be considered in blind handovers for CSFB.
ondPri Ensure that this parameter is set to a different
value from the CSFallBackBlind-
HoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallB Network Set this parameter based on the network plan.
priority ackBlind plan This parameter is set to CDMA2000 by
InterRat HoCfg.In (negotiation default and specifies the lowest-priority RAT
terRatLo not required) to be considered in blind handovers for CSFB.
westPri Ensure that this parameter is set to a different
value from the CSFallBackBlind-
HoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
UTRAN CSFallB Network Set this parameter based on the network plan.
LCS ackBlind plan This parameter specifies the LCS capability of
capability HoCfg.U (negotiation the UTRAN.
tranLcsC not required)
ap
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 flash redirections.
Max Utran InterRatH Network plan Set this parameter based on the network plan.
cell num in oComm.C (negotiation The default value is 8. If this parameter is set
redirection ellInfoMa not required) to a small value, the flash CSFB success rate
xUtranCel decreases because UEs may not receive valid
lNum neighboring cell system information. If this
parameter is set to a large value, the size of
an RRC connection release message
increases and CSFB may fail.
Max Utran InterRatH Network plan To use flash CSFB for emergency blind
cell num in oComm.U (negotiation redirection, change the parameter value from
CSFB tranCellN not required) the default value 0 to a non-zero value.
EMC umForEm
redirection cRedirect
Step 1 (Optional) Run the MOD GLOBALPROCSWITCH command to set the RIM Coding
Policy parameter.
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.
Step 4 Run the MOD S1INTERFACE command with the MME Release parameter set to
Release_R9(Release 9).
Step 5 (Optional) Run the MOD INTERRATHOCOMM command with the Max Utran cell num
in redirection parameter set (its default value is 8).
Step 6 (Optional) Run the MOD INTERRATHOCOMM command with the Max Utran cell num
in CSFB EMC redirection parameter set, for example, to 3.
----End
Signaling Observation
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 8.1.6 Activation Observation. The difference is that the RRC
Connection Release message carries the information about neighboring UTRAN cells.
Counter Observation
Table 8-15 lists the performance counters for observing functions related to flash CSFB to
UTRAN.
8.3.7 Deactivation
Table 8-16 describes the parameters for deactivating this feature.
Use this feature in the overlapping coverage of UMTS and LTE networks when the following
conditions are met:
8.4.3 Requirements
Operating Environment
This feature is a Huawei-proprietary feature and requires that the UTRAN, eNodeB, RNC,
MME, and MSC be provided by Huawei and support this feature. This feature is used with
MME11.0 and MSC11.0.
License
The operator has purchased and activated the license for the feature listed in Table 8-17.
NOTE
The license for ultra-flash CSFB needs to be purchased and activated on the UTRAN. For detailed
operations, see the following section in Interoperability Between UMTS and LTE Feature Parameter
Description: Engineering Guidelines > WRFD-160271 Ultra-Flash CSFB.
8.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.
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
Required Data
The required data is the same as that for TDLOFD-001033 CS Fallback to UTRAN. For
details, see 8.1.5.1 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to set the handover mode and handover algorithm switch for ultra-flash CSFB to UTRAN.
The following table describes the parameter 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 following table describes the parameter that must be set in the CellHoParaCfg MO to
disable blind handover for UEs supporting ultra-flash CSFB after the blind handover function
takes effect.
Step 1 Run MML commands to configure neighboring UTRAN frequencies and UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
----End
----End
l (Optional) Perform the following operation if UE compatibility risks exist after ultra-
flash CSFB is activated.
----End
l (Optional) Perform the following operation if you need to disable blind handover and
enable measurement-based handover for UEs supporting ultra-flash CSFB after the blind
handover function takes effect.
Step 1 Run the MOD CELLHOPARACFG command with the UFCsfbBlindHoDisSwitch option
of the Handover Mode switch parameter selected.
----End
l (Optional) If 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=
UltraFlashCsfbCapCfg-0;
ADD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0, NetworkCapCfg=
UltraFlashCsfbCapCfg-0;
MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch= UtranSepOpMobilitySwitch-1;
l (Optional) Perform the following operation if UE compatibility risks exist after ultra-
flash CSFB is activated.
MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;
l (Optional) Perform the following operation if you need to disable blind handover and
enable measurement-based handover for UEs supporting ultra-flash CSFB after the blind
handover function takes effect.
MOD CELLHOPARACFG: HoModeSwitch= UFCsfbBlindHoDisSwitch-1;
Signaling Observation
The activation observation procedure for ultra-flash 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 falls
back to a UTRAN cell and completes the call.
Figure 8-6 shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-
originated call.
Figure 8-7 shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-
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 8-6 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-originated call
Figure 8-7 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-terminated call
Counter Observation
The counter listed in Table 8-18 can be viewed to check whether the feature has taken effect.
8.4.7 Deactivation
Table 8-19 describes the parameters for deactivating this feature.
2. Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN
and UTRAN cells.
3. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core
networks, and ensure that they all support CSFB and the MME supports LAI delivery.
Table 8-21 describes the requirements of CSFB with LAI to UTRAN for the core
networks.
4. 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.
Table 8-21 Requirements of CSFB with LAI to UTRAN for core networks
NE Requirement
8.5.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-22.
8.5.4 Precautions
None
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.
3. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that the UE 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 8.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:
8.5.7 Deactivation
TDLOFD-001068 CS Fallback 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 8.1.7 Deactivation.
l 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 TDLOFD-001089 CS
Fallback Steering to GERAN to improve the network efficiency.
8.6.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-23.
8.6.4 Precautions
None
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The required data is the same as that for LOFD-001033 CS Fallback to UTRAN. For details,
see 8.1.5.1 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
enable CSFB steering to UTRAN.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.
CN CSFallBa Network plan Set this parameter based on the network plan.
Operator ckBlindH (negotiation not
ID oCfg.CnO required)
peratorId
Highest CSFallBa Network plan Set this parameter based on the network plan.
priority ckBlindH (negotiation not This parameter is set to UTRAN by default
InterRat oCfg.Inte required) and specifies the highest-priority RAT to be
rRatHigh considered in blind handovers for CSFB. For
estPri CSFB to UTRAN, retain the default value.
Second CSFallBa Network plan Set this parameter based on the network plan.
priority ckBlindH (negotiation not This parameter is set to GERAN by default
InterRat oCfg.Inte required) and specifies the second-highest-priority RAT
rRatSeco to be considered in blind handovers for
ndPri CSFB. Ensure that this parameter is set to a
different value from the CSFallBackBlind-
HoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallBa Network plan Set this parameter based on the network plan.
priority ckBlindH (negotiation not This parameter is set to CDMA2000 by
InterRat oCfg.Inte required) default and specifies the lowest-priority RAT
rRatLowe to be considered in blind handovers for
stPri CSFB. Ensure that this parameter is set to a
different value from the CSFallBackBlind-
HoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
UTRAN CSFallBa Network plan Set this parameter based on the network plan.
LCS ckBlindH (negotiation not This parameter specifies the LCS capability
capability oCfg.Utra required) of the UTRAN.
nLcsCap
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Highes BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
t IdleCsfbHig (negoti the highest-priority RAT to be considered in CSFB for
priority hestPri ation UEs in idle mode. For CSFB to UTRAN, retain the
InterRa not default value.
t for require
Idle d)
UE
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Second BlindHoCfg. k plan parameter is set to GERAN by default and specifies
priority IdleCsfbSeco (negoti the second-highest-priority RAT to be considered in
InterRa ndPri ation CSFB for UEs in idle mode. Ensure that this
t for not parameter is set to a different value from the
Idle require CSFallBackBlindHoCfg.IdleCsfbHighestPri and
UE d) CSFallBackBlindHoCfg.IdleCsfbLowestPri
parameters.
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Lowest BlindHoCfg. k plan parameter is set to CDMA2000 by default and
priority IdleCsfbLow (negoti specifies the lowest-priority RAT to be considered in
InterRa estPri ation CSFB for UEs in idle mode. Ensure that this
t for not parameter is set to a different value from the
Idle require CSFallBackBlindHoCfg.IdleCsfbHighestPri and
UE d) CSFallBackBlindHoCfg.IdleCsfbSecondPri
parameters.
The following table describes the parameters that must be set in the CELLOPHOCFG MO
to set cell-level RAT priorities for CSFB triggered for RRC_CONNECTED and RRC_IDLE
UEs.
CN CellOpHoCf Networ Set this parameter based on the network plan. This
Operat g.CnOperato k plan parameter identifies the operator whose RAT blind-
or ID rId (negoti handover priorities are to be set.
ation
not
require
d)
Local CellOpHoCf Networ Set this parameter based on the network plan. This
cell ID g.LocalCellI k plan parameter identifies the cell whose RAT blind-
d (negoti handover priorities are to be set.
ation
not
require
d)
Highe CellOpHoCf Networ Set this parameter based on the network plan. This
st g.InterRatHi k plan parameter is set to UTRAN by default and specifies
priorit ghestPri (negoti the highest-priority RAT to be considered in blind
y ation handovers for CSFB. For CSFB to UTRAN, retain the
InterR not default value.
at require
d)
Secon CellOpHoCf Networ Set this parameter based on the network plan. This
d g.InterRatSe k plan parameter is set to GERAN by default and specifies
priorit condPri (negoti the second-highest-priority RAT to be considered in
y ation blind handovers for CSFB. Ensure that this parameter
InterR not is set to a different value from the CSFallBackBlind-
at require HoCfg.InterRatHighestPri and CSFallBackBlind-
d) HoCfg.InterRatLowestPri parameters.
Lowes CellOpHoCf Networ Set this parameter based on the network plan. This
t g.InterRatLo k plan parameter is set to CDMA2000 by default and
priorit westPri (negoti specifies the lowest-priority RAT to be considered in
y ation blind handovers for CSFB. Ensure that this parameter
InterR not is set to a different value from the
at require CellOpHoCfg.InterRatHighestPri and
d) CellOpHoCfg.InterRatSecondPri parameters.
CSFB CellOpHoCf Networ Set this parameter based on the network plan. This
Highe g.IdleCsfbHi k plan parameter is set to UTRAN by default and specifies
st ghestPri (negoti the highest-priority RAT to be considered in blind
priorit ation handovers for CSFB. For CSFB to UTRAN, retain the
y not default value.
InterR require
at for d)
Idle
UE
CSFB CellOpHoCf Networ Set this parameter based on the network plan. This
Secon g.IdleCsfbSe k plan parameter is set to GERAN by default and specifies
d condPri (negoti the second-highest-priority RAT to be considered in
priorit ation blind handovers for CSFB. Ensure that this parameter
y not is set to a different value from the
InterR require CellOpHoCfg.IdleCsfbHighestPri and
at for d) CellOpHoCfg.IdleCsfbLowestPri parameters.
Idle
UE
CSFB CellOpHoCf Networ Set this parameter based on the network plan. This
Lowes g.IdleCsfbLo k plan parameter is set to CDMA2000 by default and
t westPri (negoti specifies the lowest-priority RAT to be considered in
priorit ation blind handovers for CSFB. Ensure that this parameter
y not is set to a different value from the
InterR require CellOpHoCfg.IdleCsfbHighestPri and
at for d) CellOpHoCfg.IdleCsfbSecondPri parameters.
Idle
UE
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.
CS UtranNFreq Networ Set this parameter based on the network plan. If this
service .CsPriority k plan parameter is set to Priority_0(Priority 0) for the
priority (negoti UTRAN frequency, the eNodeB does not select the
ation frequency for SRVCC. The values
not Priority_16(Priority 16) and Priority_1(Priority 1)
require indicate the highest and lowest SRVCC priority,
d) respectively. Set a high priority for a UTRAN
frequency with good coverage.
The following table describes the parameter that must be set in the UtranNFreq MO to set
the CS+PS combined service priority of a neighboring UTRAN frequency for
RRC_CONNECTED UEs.
CS and UtranNFreq Network Set this parameter based on the network plan. If
PS .CsPsMixed plan this parameter is set to Priority_0(Priority 0) for
mixed Priority (negotiation the UTRAN frequency, the eNodeB does not
priority not select the frequency for SRVCC. The values
required) 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.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg
MO to set the CSFB policy for RRC_CONNECTED UEs.
CSFB CSFallBack Networ Set this parameter based on the network plan. The
handov PolicyCfg.C k plan default values are REDIRECTION, CCO_HO, and
er sfbHoPolicy (negoti PS_HO. You are advised to set this parameter based
policy Cfg ation on the UE capabilities and network capabilities. For
Config not details about how to select a CSFB handover policy,
uration require see 3.6 Execution.
d)
The following table describes the parameter that must be set in the CSFallBackPolicyCfg
MO to set the CSFB policy for RRC_IDLE UEs.
CSFB CSFallBack Networ Set this parameter based on the network plan. The
handov PolicyCfg.Id k plan default values are REDIRECTION, CCO_HO, and
er leModeCsfb (negoti PS_HO. You are advised to set this parameter based
policy HoPolicyCfg ation on the UE capabilities and network capabilities. For
Config not details about how to select a CSFB handover policy,
uration require see 3.6 Execution.
for idle d)
ue
Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous coverage.
NOTE
Step 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.
Step 3 Run the MOD CSFAllBACKPOLICYCFG command with the PS_HO option of the CSFB
handover policy Configuration parameter and the REDIRECTION option of the CSFB
handover policy Configuration for idle ue parameter selected.
----End
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.
Step 1 The feature activation procedure is as follows: Run the MOD GERANNCELL command
with the blind handover priority specified for the neighboring GERAN cell.
Step 2 To enable UTRAN CSFB steering through cell-level commands, perform the following
operations:
l Run the MOD CELLALGOSWITCH command with the
UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) and
GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) options of the Handover
Allowed Switch parameter selected.
NOTE
----End
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 CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch =
UtranCsfbSwitch-1&GeranCsfbSwitch-1, HoAllowedSwitch
=UtranCsfbSteeringSwitch-1&GeranCsfbSteeringSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0,HoModeSwitch=BlindHoSwitch-0;
MOD
CSFALLBACKBLINDHOCFG:CnOperatorId=0,InterRatHighestPri=UTRAN,InterRatSecondPri=GER
AN,IdleCsfbHighestPri=UTRAN,IdleCsfbSecondPri=GERAN;
MOD
CSFALLBACKPOLICYCFG:CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0,IdleModeCsfbHoP
olicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
If TDLOFD-001089 CS Fallback Steering to GERAN has also been activated, the activation
observation procedure is as follows:
8.6.7 Deactivation
Table 8-24 describes the parameters for deactivating this feature.
8.7.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-25.
NOTE
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN or
LOFD-001033 CS Fallback to UTRAN.
8.7.4 Precautions
None
Required Data
The required data is the same as that for LOFD-001033 CS Fallback to UTRAN. For details,
see 8.1.5.1 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
enable E-UTRAN to UTRAN CS/PS Steering.
The following table describes the parameter that must be set in the UtranNFreq MO to set
the CS service priority for a UTRAN frequency.
Step 2 Run the MOD UTRANNFREQ command with the CS service priority parameter set to
Priority_16(Priority 16).
----End
l Scenario 2: Measurement-based E-UTRAN to UTRAN CS/PS steering
Step 2 Run the MOD UTRANNFREQ command with the CS service priority parameter set to
Priority_16(Priority 16).
----End
The activation observation procedure for E-UTRAN to UTRAN CS/PS Steering is as follows:
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 the highest PS service priority for UTRAN frequency F1 and the highest
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 a UTRAN cell 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 a UTRAN cell on F1.
8.7.7 Deactivation
Table 8-26 describes the parameters for deactivating this feature.
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the
serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach,
combined EPS/IMSI detach, and
combined TAU/LAU
l Routing of CS signaling messages
l SMS over SGs
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the
SGs interface
l 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.
8.8.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-28.
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.
8.8.4 Precautions
None
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.
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 serves the external
GERAN cell works in RAN sharing with common carriers mode and multiple operators
share the external GERAN cell.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellAlgoSwitch MOs to set the handover mode and handover algorithm switches for CSFB
to GERAN.
Handover ENodeBAl Network Set this parameter based on the network plan.
Mode goSwitch. plan To activate PS handovers, select the
switch HoModeS (negotiation GeranPsHoSwitch(GeranPsHoSwitch) option.
witch not To activate CCO, select the
required) GeranCcoSwitch(GeranCcoSwitch) option.
To activate NACC, select the
GeranNaccSwitch(GeranNaccSwitch) option.
If none of the preceding options is selected,
redirection will be used for CSFB to GERAN.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellHoParaCfg MOs to set eNodeB- and cell-level blind handover switches.
Handove CellHo Network To activate blind handovers for a cell under the
r Mode ParaCf plan eNodeB, select the
switch g.HoMo (negotiation BlindHoSwitch(BlindHoSwitch) option of the
deSwitc not parameter. If the BlindHoSwitch(BlindHoSwitch)
h required) option is cleared, blind handovers for the cell are
invalid.
The following table describes the parameters that must be set in the CellAlgoSwitch and
CSFallBackHo MOs to set the switch for adaptive blind handover for CSFB and the A1
threshold for adaptive blind handover for CSFB.
Handove CellAlg Network When GSM and LTE cells are co-sited with the
r oSwitch plan same coverage, you can enable
Allowed .HoAllo (negotiation CsfbAdaptiveBlindHoSwitch. The eNodeB selects
Switch wedSwit not a measurement or blind handover to GSM based on
ch required) the event A1 report submitted by a UE.
CSFB CSFall Network This parameter specifies the RSRP threshold of the
Adaptive BackHo plan serving cell above which a CSFB-triggered adaptive
Blind Ho .BlindH (negotiation blind handover is triggered. If the RSRP value
A1 RSRP oA1Thd not measured by a UE exceeds this threshold, the UE
Trigger Rsrp required) submits a event A1 report. If the eNodeB receives
Threshol an event A1 report, it directly enters the blind
d handling procedure. If the eNodeB does not receive
an event A1 report (the UE is located at the edge of
the E-UTRAN cell), it enters the measurement
procedure. The target measurement RAT depends on
configured RAT priorities and UE capabilities.
On the live network, set this parameter based on
network coverage.
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.
Highest CSFallBackB Network Set this parameter based on the network plan.
priority lindHoCfg.Int plan This parameter is set to UTRAN by default and
InterRat erRatHighest (negotiati specifies the highest-priority RAT to be
Pri on not considered in blind handovers for CSFB. For
required) CSFB to GERAN, set this parameter to
GERAN.
Second CSFallBackB Network Set this parameter based on the network plan.
priority lindHoCfg.Int plan This parameter is set to GERAN by default and
InterRat erRatSecondP (negotiati specifies the second-highest-priority RAT to be
ri on not considered in blind handovers for CSFB. If the
required) 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 CSFallBackBlind-
HoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallBackB Network Set this parameter based on the network plan.
priority lindHoCfg.Int plan This parameter is set to CDMA2000 by default
InterRat erRatLowestP (negotiati and specifies the lowest-priority RAT to be
ri on not considered in blind handovers for CSFB.
required) Ensure that this parameter is set to a different
value from the CSFallBackBlind-
HoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
GERAN CSFallBackB Network Set this parameter based on the network plan.
LCS lindHoCfg.Ge plan This parameter specifies the LCS capability of
capability ranLcsCap (negotiati the GERAN.
on not
required)
The following table describes the parameters that must be set in the CellOpHoCfg MO to set
cell-level blind-handover priorities of different RATs for CSFB.
CN CellOpHoCf Networ Set this parameter based on the network plan. This
Operat g.CnOperato k plan parameter identifies the operator whose RAT blind-
or ID rId (negoti handover priorities are to be set.
ation
not
require
d)
Local CellOpHoCf Networ Set this parameter based on the network plan. This
cell ID g.LocalCellI k plan parameter identifies the cell whose RAT blind-
d (negoti handover priorities are to be set.
ation
not
require
d)
Highe CellOpHoCf Networ Set this parameter based on the network plan. This
st g.InterRatHi k plan parameter is set to UTRAN by default and specifies
priorit ghestPri (negoti the highest-priority RAT to be considered in blind
y ation handovers for CSFB. For CSFB to UTRAN, retain the
InterR not default value.
at require
d)
Secon CellOpHoCf Networ Set this parameter based on the network plan. This
d g.InterRatSe k plan parameter is set to GERAN by default and specifies
priorit condPri (negoti the second-highest-priority RAT to be considered in
y ation blind handovers for CSFB. Ensure that this parameter
InterR not is set to a different value from the
at require CellOpHoCfg.InterRatHighestPri and
d) CellOpHoCfg.InterRatLowestPri parameters.
Lowes CellOpHoCf Networ Set this parameter based on the network plan. This
t g.InterRatLo k plan parameter is set to CDMA2000 by default and
priorit westPri (negoti specifies the lowest-priority RAT to be considered in
y ation blind handovers for CSFB. Ensure that this parameter
InterR not is set to a different value from the
at require CellOpHoCfg.InterRatHighestPri and
d) CellOpHoCfg.InterRatSecondPri parameters.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.
CSFB CSFallBack Network plan Set this parameter based on the network
Protection Ho.CsfbPro (negotiation not plan. The default value 4 applies to a
Timer tectionTime required) GSM+UMTS+LTE network. The default
r value is also recommended for a GSM
+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 GlobalProcSwitch MO to
control redirection-based CSFB optimization for UEs in idle mode.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
set the policy for handling the conflicts between handover and CSFB procedures.
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
enable the function of deleting inter-frequency measurements when CSFB starts GERAN
measurement.
CSFB to GERAN using blind redirection works regardless of whether neighboring GERAN
cells are configured.
l If you want to configure a neighboring GERAN cell, you must configure the
GeranNFreq and GeranNCell MOs. For details about parameter settings, see Inter-RAT
Mobility Management in Connected Mode.
l 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.
Step 1 Run the following eNodeB- and cell-level commands to enable the blind handover function
for CSFB to GERAN:
1. Run the MOD ENODEBALGOSWITCH command with the
BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter
selected.
2. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter cleared and the
REDIRECTION option of the same parameter selected.
Step 4 (Optional) If you require GERAN to have the highest priority for CSFB, run the following
eNodeB- and cell-level commands:
1. Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority
InterRat and Second priority InterRat parameters set to GERAN and UTRAN,
respectively.
2. Run the MOD CELLOPHOCFG command with the Highest priority InterRat and
Second priority InterRat parameters set to GERAN and UTRAN, respectively.
Step 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).
Step 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).
Step 7 (Optional) Run the MOD GLOBALPROCSWITCH command with the
IdleCsfbRedirectOptSwitch option of the Protocol Message Optimization Switch
parameter selected.
----End
l Basic scenario 2: CSFB to GERAN using blind CCO with NACC
Step 1 Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
Step 2 Run the MOD CELLALGOSWITCH command with the
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Allowed Switch parameter
selected.
NOTE
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
----End
l Basic scenario 3: CSFB to GERAN using blind handovers
Step 1 Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
Step 2 Run the MOD CELLALGOSWITCH command with the
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Allowed Switch parameter
selected.
NOTE
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
----End
l Basic scenario 4: CSFB to GERAN using measurement-based redirection
Step 1 Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
Step 3 Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter cleared and the
REDIRECTION option of the same parameter selected.
Step 5 Run the MOD CELLALGOSWITCH command with the
CSFB_MEAS_DEL_INTERFREQ_SW option of the Measurement Optimization
Algorithm Switch parameter selected.
----End
l Basic scenario 5: CSFB to GERAN using measurement-based handovers
(recommended)
Step 1 Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
Step 2 Run the MOD CELLALGOSWITCH command with the
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Allowed Switch parameter
selected.
NOTE
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
Step 1 Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
Step 2 Run the MOD CELLALGOSWITCH command with the
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Allowed Switch parameter
selected.
NOTE
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
----End
Enhanced scenario 1: Policy setting for handling the conflicts between handover and CSFB
procedures
To enable the eNodeB to process the CSFB procedure first, run the following command after
the commands in a basic scenario are executed:
Step 1 Run the MOD GLOBALPROCSWITCH command with the CsfbFlowFirstSwitch option
of the Handover Process Control Switch parameter selected.
----End
InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;
ADD CELLOPHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;
MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12,
GeranCellId=15,BlindHoPriority=32;
MOD GLOBALPROCSWITCH: ProtocolMsgOptSwitch=IdleCsfbRedirectOptSwitch-1;
Enhanced scenario 1: Policy setting for handling the conflicts between handover and CSFB
procedures
To enable the eNodeB to process the CSFB procedure first, run the following command after
the commands in a basic scenario are executed:
MOD GLOBALPROCSWITCH:HoProcCtrlSwitch= CsfbFlowFirstSwitch-1;
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.
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 8.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 8-10 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.
Counter Observation
Table 8-29 lists the performance counters for observing functions related to CSFB to
GERAN.
8.8.7 Deactivation
Table 8-30 describes the parameters for deactivating this feature.
Table 8-33 lists the counters that indicate whether CSFB is performed through redirection or
handover.
You can check whether CCO with NACC or CCO without NACC is used as the CSFB
mechanism by viewing the counters listed in Table 8-34.
Table 8-34 Counters related to using CCO with NACC or CCO without NACC
Counter ID Counter Name Description
Table 8-35 Counter related to the number of times that the eNodeB enters the protection
procedure for CSFB
Counter ID Counter Name Description
Table 8-36 lists the counters related to CSFB for emergency calls.
The following table lists event-B1-related parameters for CSFB to GERAN in the
CSFallBackHo MO.
Local cell CSFallBac Network Set this parameter based on the network plan.
ID kHo.Local plan
CellId (negotiatio
n not
required)
CSFB CSFallBac Network Set this parameter based on the network plan. This
GERAN kHo.CsfbH plan parameter specifies the RSSI threshold for event
EventB1 oGeranB1 (negotiatio B1 in CSFB to GERAN. Event B1 is triggered
Trigger Thd n not when the measured RSSI of a GERAN cell
Threshold required) reaches the value of this parameter and all other
conditions are also met.
CSFB CSFallBac Network Set this parameter based on the network plan. This
Geran kHo.CsfbH plan parameter specifies the time-to-trigger for event
EventB1 oGeranTim (negotiatio B1 in CSFB to GERAN. When CSFB to GERAN
Time To eToTrig n not is required, set this parameter, which is used by
Trig required) UEs as one of the conditions for triggering event
B1. When a UE detects that the signal quality in at
least one 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.
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).
8.9.3 Requirements
Operating Environment
If the RIM procedure is performed through the core network, the core-network equipment
must support this feature:
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
l 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
The operator has purchased and activated the license for the feature listed in Table 8-37.
8.9.4 Precautions
None
Required Data
The required data is the same as that for TDLOFD-001033 CS Fallback to UTRAN. For
details, see 8.1.5.1 Data Preparation.
GeranExternalCell: used to configure external GERAN cells. The GeranExternalCell.Rac
parameter must be set.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to configure the RIM procedure.
Counter Observation
No matter whether the RIM procedure is performed through the core network or the
eCoordinator, performance counters listed in Table 8-38 can be used to observe whether the
RIM procedure has taken effect.
Table 8-38 Counters related to the RIM procedure between E-UTRAN and GERAN
Counter ID Counter Name Description
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.
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.
If the BSC sends the DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMATION IE over the Gb interface, you can infer that the BSC can notify the eNodeB
with the cell state change through the RIM procedure.
----End
If the RIM procedure is performed through the eCoordinator, trace signaling messages as
follows:
Check whether the ENB DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-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.
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-INFORMATION IE to the eCoordinator, you can
infer that the BSC can response to the RIM request normally.
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.
----End
8.9.7 Deactivation
Table 8-39 describes the parameters for deactivating this feature.
NE Requirement
8.10.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the licenses for the features listed in Table 8-41.
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. For detailed operations, see
section "eNACC from EUTRAN to GERAN" in Interoperability Between GSM and LTE Feature
Parameter Description.
8.10.4 Precautions
None
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
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.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellAlgoSwitch MOs to set the handover mode and handover algorithm switches for flash
CSFB to GERAN.
Handover ENodeBAlg Network Set this parameter based on the network plan.
Mode switch oSwitch.Ho plan
ModeSwitch (negotiati
on not
required)
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellHoParaCfg MOs to set eNodeB- and cell-level blind handover switches.
Handove CellHo Network To activate blind handovers for a cell under the
r Mode ParaCf plan eNodeB, select the
switch g.HoMo (negotiation BlindHoSwitch(BlindHoSwitch) option of the
deSwitc not parameter. If the BlindHoSwitch(BlindHoSwitch)
h required) option is cleared, blind handovers for the cell are
invalid.
The following table describes the parameter that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
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.
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 flash redirections.
Max Geran cell InterRatHo Network Set this parameter based on the network
num in Comm.CellI plan plan. The default value is 8. If this
redirection nfoMaxGera (negotiati parameter is set to a small value, the flash
nCellNum on not CSFB success rate decreases because UEs
required) may not receive valid neighboring cell
system information. If this parameter is set
to a large value, the size of an RRC
connection release message increases and
CSFB may fail.
Max Geran cell InterRatHo Network To use flash CSFB for emergency blind
num in CSFB Comm.Gera plan redirection, change the parameter value
EMC nCellNumF (negotiati from the default value 0 to a non-zero
redirection orEmcRedir on not value.
ect required)
Step 3 Run the MOD S1INTERFACE command with the MME Release parameter set to
Release_R9(Release 9).
Step 4 (Optional) Run the MOD INTERRATHOCOMM command with the Max Geran cell num
in redirection parameter set (its default value is 8).
Step 5 (Optional) Run the MOD INTERRATHOCOMM command with the Max Geran cell num
in CSFB EMC redirection parameter set, for example, to 3.
----End
Signaling Observation
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 8.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 8-11.
Figure 8-11 The RRC Connection Release message during flash CSFB to GERAN
Counter Observation
The counter listed in Table 8-42 can be viewed to check whether the feature has taken effect.
8.10.7 Deactivation
Table 8-43 describes the parameters for deactivating this feature.
8.11.3 Requirements
Operating Environment
This feature is a Huawei-proprietary feature and requires that the eNodeB, MME, and MSC
be provided by Huawei and support this feature. This feature is used with MME11.0 and
MSC11.0.
License
The operator has purchased and activated the licenses for the features listed in Table 8-44.
8.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.
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The required data is the same as that for TDLOFD-001034 CS Fallback to GERAN. For
details, see 8.1.5.1 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to set the eNodeB-level handover switch for ultra-flash CSFB to GERAN.
The following table describes the parameter that must be set in the CellHoParaCfg MO to set
the cell-level blind handover switch for ultra-flash CSFB to GERAN.
The following table describes the parameter that must be set in the CellHoParaCfg MO to
disable blind handover for UEs supporting ultra-flash CSFB after the blind handover function
takes effect.
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
enable the function of deleting inter-frequency measurements when CSFB starts GERAN
measurement.
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.
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 CellDrx Network When the network supports measurements and UEs
switch Para.Dr plan support DRX measurements well, measurement
for xForMe (negotiation delays are significantly reduced and the customer
measure asSwitc required) can tolerate the impact on services during
ments h measurements.
To enable the DRX switch for measurements, set
DrxForMeasSwitch to 1.
Long CellDrx Network This parameter specifies the length of the long DRX
DRX Para.Lo plan cycle specific to GERAN measurement.
Cycle for ngDrxC (negotiation
Measure ycleFor required)
ment Meas
DRX CellDrx Network This parameter specifies the length of the DRX
Inactivity Para.Dr plan Inactivity Timer specific to GERAN measurement.
Timer for xInactTi (negotiation
Measure merFor required)
ment Meas
DRX CellDrx Network This parameter specifies the length of the DRX
Retransm Para.Dr plan Retransmission Timer specific to GERAN
ission xReTxT (negotiation measurement.
Timer for imerFor required)
Measure Meas
ment
Short CellDrx Network This parameter specifies the length of the short
DRX Para.Sh plan DRX cycle specific to GERAN measurement.
Cycle for ortDrxC (negotiation
Measure ycleFor required)
ment Meas
Short CellDrx Network This parameter specifies the length of the Short
Cycle Para.Sh plan Cycle Timer specific to GERAN measurement.
Timer for ortCycle (negotiation
Measure TimerF required)
ment orMeas
The following table describes the parameter 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.
Step 1 Run MML commands to configure neighboring GERAN frequencies and GERAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
Step 2 Run the MOD ENODEBALGOSWITCH command with the
GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the Handover Algo
switch parameter selected.
Step 3 (Optional) Run the MOD GLOBALPROCSWITCH command with the
IratMeasCfgTransSwitch option of the Protocol Message Optimization Switch parameter
selected if you need to optimize "G2L Fast Return after Ultra-Flash CSFB to GERAN" based
on the E-UTRA frequency capability supported by UEs. The eNodeB transfers E-UTRA
frequency information supported by UEs to the BSC during SRVCC.
Step 4 (Optional) Run the MOD GERANEXTERNALCELL command with the Ultra-Flash
CSFB Capability Indication parameter set to BOOLEAN_FALSE if some external
GERAN cells do not support Ultra-Flash CSFB to GERAN.
Step 5 (Optional) Run the MOD CELLDRXPARA command with the DRX for Measurement
Switch parameter set to ON(On) if UEs support DRX-based measurements.
----End
l (Optional) Perform the following operation if UE compatibility risks exist after ultra-
flash CSFB is activated.
----End
l (Optional) Perform the following operation if you need to disable blind handover and
enable measurement-based handover for UEs supporting ultra-flash CSFB after the blind
handover function takes effect.
Step 1 Run the MOD CELLHOPARACFG command with the UFCsfbBlindHoDisSwitch option
of the Handover Mode switch parameter selected.
----End
l (Optional) Perform the following operation if you need to enable the function of deleting
inter-frequency measurements when CSFB starts GERAN measurement.
----End
l (Optional) Perform the following operation if UE compatibility risks exist after ultra-
flash CSFB is activated.
MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;
(Optional) Perform the following operation if you need to disable blind handover and
enable measurement-based handover for UEs supporting ultra-flash CSFB after the blind
handover function takes effect.
MOD CELLHOPARACFG: HoModeSwitch= UFCsfbBlindHoDisSwitch-1;
(Optional) Perform the following operation if you need to enable the function of deleting
inter-frequency measurements when CSFB starts GERAN measurement.
MOD CELLALGOSWITCH: MeasOptAlgoSwitch=CSFB_MEAS_DEL_INTERFREQ_SW-1;
Signaling Observation
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 an ultra-flash
CSFB to GERAN is triggered successfully.
2. The UE falls back to a GERAN cell and completes the call.
Counter Observation
The counter listed in the following table can be monitored to check whether the feature has
been activated.
8.11.7 Deactivation
Table 8-46 describes the parameters for deactivating this feature.
Table 8-48 Requirements of CSFB with LAI to GERAN for core networks
NE Requirement
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the
serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach,
combined EPS/IMSI detach, and
combined TAU/LAU
l CS signaling message routing
l SMS over SGs
l LAI delivery
NE Requirement
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the
SGs interface
l 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.
8.12.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-49.
8.12.4 Precautions
None
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 8.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:
8.12.7 Deactivation
TDLOFD-001069 CS Fallback 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 8.8.7 Deactivation.
8.13.3 Requirements
Operating Environment
l For the Huawei EPC, the EPC version for eRAN3.0 is required. If the EPC version is not
for eRAN3.0, messages may not be parsed.
l For a third party's EPC, the EPC must support CSFB complying with 3GPP Release 8.
Check that software versions for the EPC are correct.
License
The operator has purchased and activated the license for the feature listed in Table 8-50.
8.13.4 Precautions
None
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The required data is the same as that for CS Fallback to GERAN. For details, see 8.1.5.1 Data
Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
enable Handover Allowed Switch.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.
CN CSFallBack Networ Set this parameter based on the network plan. This
Operat BlindHoCfg. k plan parameter identifies the operator whose RAT blind-
or ID CnOperatorI (negoti handover priorities are to be set.
d ation
not
require
d)
Highes CSFallBack Networ Set this parameter based on the network plan. This
t BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
priority InterRatHig (negoti the highest-priority RAT to be considered in blind
InterRa hestPri ation handovers for CSFB.
t not
require
d)
Second CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to GERAN by default and specifies
InterRa InterRatSeco (negoti the second-highest-priority RAT to be considered in
t ndPri ation blind handovers for CSFB. Ensure that this parameter
not is set to a different value from the CSFallBackBlind-
require HoCfg.InterRatHighestPri and CSFallBackBlind-
d) HoCfg.InterRatLowestPri parameters.
Lowest CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to CDMA2000 by default and
InterRa InterRatLow (negoti specifies the lowest-priority RAT to be considered in
t estPri ation blind handovers for CSFB. Ensure that this parameter
not is set to a different value from the CSFallBackBlind-
require HoCfg.InterRatHighestPri and CSFallBackBlind-
d) HoCfg.InterRatSecondPri parameters.
GERA CSFallBack Networ Set this parameter based on the network plan. This
N LCS BlindHoCfg. k plan parameter specifies the LCS capability of the
capabil GeranLcsCa (negoti GERAN.
ity p ation
not
require
d)
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Highes BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
t IdleCsfbHig (negoti the highest-priority RAT to be considered in CSFB for
priority hestPri ation UEs in idle mode.
InterRa not
t for require
Idle d)
UE
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Second BlindHoCfg. k plan parameter is set to GERAN by default and specifies
priority IdleCsfbSeco (negoti the second-highest-priority RAT to be considered in
InterRa ndPri ation CSFB for UEs in idle mode. Ensure that this
t for not parameter is set to a different value from the
Idle require CSFallBackBlindHoCfg.IdleCsfbHighestPri and
UE d) CSFallBackBlindHoCfg.IdleCsfbLowestPri
parameters.
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Lowest BlindHoCfg. k plan parameter is set to CDMA2000 by default and
priority IdleCsfbLow (negoti specifies the lowest-priority RAT to be considered in
InterRa estPri ation CSFB for UEs in idle mode. Ensure that this
t for not parameter is set to a different value from the
Idle require CSFallBackBlindHoCfg.IdleCsfbHighestPri and
UE d) CSFallBackBlindHoCfg.IdleCsfbSecondPri
parameters.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg
MO to set the CSFB policy for RRC_CONNECTED UEs.
CSFB CSFallBack Networ Set this parameter based on the network plan. The
handov PolicyCfg.C k plan default values are REDIRECTION, CCO_HO, and
er sfbHoPolicy (negoti PS_HO. You are advised to set this parameter based
policy Cfg ation on the UE capabilities and network capabilities. For
Config not details about how to select a CSFB handover policy,
uration require see 4.6 Execution.
d)
The following table describes the parameter that must be set in the CSFallBackPolicyCfg
MO to set the CSFB policy for RRC_IDLE UEs.
CSFB CSFallBack Networ Set this parameter based on the network plan. The
handov PolicyCfg.Id k plan default values are REDIRECTION, CCO_HO, and
er leModeCsfb (negoti PS_HO. You are advised to set this parameter based
policy HoPolicyCfg ation on the UE capabilities and network capabilities. For
Config not details about how to select a CSFB handover policy,
uration require see 4.6 Execution.
for idle d)
ue
Step 1 Run the MOD CELLALGOSWITCH command with the GeranCsfbSteeringSwitch option
of the Handover Allowed Switch parameter selected.
NOTE
This feature is also controlled by the GeranCsfbSteeringSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
The option of the cell-level parameter takes effect only when that option of the eNodeB-level parameter
is cleared.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
Step 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.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter and the REDIRECTION option of the
CSFB handover policy Configuration for idle ue parameter selected.
----End
8.13.7 Deactivation
Table 8-51 describes the parameters for deactivating this feature.
8.14 Troubleshooting
Fault Handling
Step 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.
l If so, go to Step 2.
l If not, replace the UE with one that supports combined EPS/IMSI attach, and try again.
Step 2 Check whether the traced Attach Accept message includes the IE cs-domain-not-available.
l If it does, go to Step 3.
l If not, contact Huawei technical support.
Step 3 Contact the vendors of core network NEs to ensure the following:
l Attach procedures to the CS domain are allowed according to the subscription data on
the HSS.
l The core network supports CSFB.
l The SGs interface is correctly configured.
----End
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
Step 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.
l If it is, go to Step 2
l If not, rectify the faults and try again.
Step 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.
----End
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
Step 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
Step 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:
l If CSFB to UTRAN is required, go to Step 3.
l If CSFB to GERAN is required, go to Step 4.
Step 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.
l 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.
l If Blind handover priority is not 0, contact Huawei technical support.
Step 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.
l 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.
l If Blind handover priority is not 0, contact Huawei technical support.
----End
Fault Description
During CSFB to UTRAN procedures with the handover policy set to PS HO, the handover
preparation success rate is low.
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.
Step 1 View the counters listed in Table 8-53 to check the cause for the low handover preparation
success rate.
Step 2 Analyze the failure cause based on the values of the preceding counters for each NE.
----End
9 Parameters
CellHoP HoMode MOD LOFD-0 SRVCC Meaning: Indicates the handover method switches
araCfg Switch CELLH 01022 / to based on which the eNodeB determines handover
OPARA TDLOF UTRAN policies. BlindHoSwitch: This option specifies
CFG D-00102 SRVCC whether to enable blind handover for CSFB. Bind
LST 2 to handover for CSFB is enabled only if this option is
CELLH LOFD-0 GERAN selected. A blind handover for CSFB can be triggered
OPARA 01023 / only if both this option and the BlindHoSwitch option
CS of the HoModeSwitch parameter in the
CFG TDLOF Fallback ENodeBAlgoSwitch MO are selected.
D-00102 to
3 UtranPsHoSwitch: PS handover to UTRAN is
UTRAN supported only if this option is selected. This option
LOFD-0 CS takes effect only if the eNodeB-level option
01033 / Fallback UtranPsHoSwitch of the HoModeSwitch parameter in
TDLOF to the ENodeBAlgoSwitch MO is deselected.
D-00103 GERAN UtranSrvccSwitch: SRVCC to UTRAN is supported
3 only if this option is selected. This option takes effect
PS Inter-
LOFD-0 only if the eNodeB-level option UtranSrvccSwitch of
RAT
01034 / the HoModeSwitch parameter in the
Mobility
TDLOF ENodeBAlgoSwitch MO is deselected.
between
D-00103 GeranSrvccSwitch: SRVCC to GERAN is supported
E-
4 only if this option is selected. This option takes effect
UTRAN
only if the eNodeB-level option GeranSrvccSwitch of
LOFD-0 and
the HoModeSwitch parameter in the
01019 / UTRAN
ENodeBAlgoSwitch MO is deselected.
TDLOF PS Inter- UtranRedirectSwitch: Redirection to UTRAN is
D-00101 RAT supported only if this option is selected. This option
9 Mobility takes effect only if the eNodeB-level option
LOFD-0 between UtranRedirectSwitch of the HoModeSwitch parameter
01020 / E- in the ENodeBAlgoSwitch MO is deselected.
TDLOF UTRAN GeranRedirectSwitch: Redirection to GERAN is
D-00102 and supported only if this option is selected. This option
0 GERAN
CellAlg HoAllo MOD LBFD-0 Service Meaning: Indicates whether to enable eNodeB-level
oSwitch wedSwit CELLA 0201805 Based handovers to be activated in the cell when related
ch LGOSW / Inter- eNodeB-level handover switches are on.
ITCH TDLBF frequenc SrvBasedInterFreqHoSw: Indicates whether to enable
LST D-00201 y service-based inter-frequency handover to be activated
CELLA 805 Handov in the cell. Service-based inter-frequency handover is
LGOSW LOFD-1 er allowed to be activated in the cell only when this
ITCH 11204 Separate switch is on. GeranSepOpMobilitySwitch: Indicates
Mobility whether to differentiate mobility policies for GERAN
LOFD-0 operators. When this switch is on, different network
01033/ Policies
to policies can be applied to different GERAN operators.
TDLOF Such policies include SRVCC and SI obtaining
D-00103 GERAN
for through RIM procedures. When this switch is off,
3 different network policies cannot be applied to
Multi
LOFD-0 PLMN different GERAN operators. This option applies only
01034/ to FDD cells. UtranCsfbSwitch: Indicates whether to
TDLOF CS enable CSFB for UTRAN. When this switch is on,
D-00103 Fallback CSFB to UTRAN is allowed. When this switch is off,
4 to the UTRAN CSFB algorithm is disabled. If eNodeB-
UTRAN level UtranCsfbSwitch is on, local-cell-level
LOFD-0
01052/ CS parameter settings do not take effect. If eNodeB-level
TDLOF Fallback UtranCsfbSwitch is off, local-cell-level parameter
D-00105 to settings take effect. GeranCsfbSwitch: Indicates
2 GERAN whether to enable CSFB for GERAN. When this
Flash switch is on, CSFB to GERAN is allowed. When this
LOFD-0 switch is off, the GERAN CSFB algorithm is
01053/ CS
Fallback disabled. If eNodeB-level GeranCsfbSwitch is on,
TDLOF local-cell-level parameter settings do not take effect. If
D-00105 to
UTRAN eNodeB-level GeranCsfbSwitch is off, local-cell-level
3 parameter settings take effect. UtranFlashCsfbSwitch:
LOFD-0 Flash This switch does not take effect if UtranCsfbSwitch is
01088/ CS off. When the UtranFlashCsfbSwitch is on, flash
TDLOF Fallback CSFB to UTRAN is enabled, and UTRAN system
D-00108 to information is carried during redirection. When the
8 GERAN UtranFlashCsfbSwitch is off, flash CSFB to UTRAN
LOFD-0 CS is disabled. If eNodeB-level UtranFlashCsfbSwitch is
01089/ Fallback on, local-cell-level parameter settings do not take
TDLOF Steering effect. If eNodeB-level UtranFlashCsfbSwitch is off,
D-00108 to local-cell-level parameter settings take effect.
9 UTRAN GeranFlashCsfbSwitch: This switch does not take
CS effect if GeranCsfbSwitch is off. When the
Fallback GeranFlashCsfbSwitch is on, flash CSFB to GERAN
Steering is enabled, and GERAN system information is carried
to during redirection. When the GeranFlashCsfbSwitch
GERAN is off, flash CSFB to GERAN is disabled. If eNodeB-
level GeranFlashCsfbSwitch is on, local-cell-level
parameter settings do not take effect. If eNodeB-level
GeranFlashCsfbSwitch is off, local-cell-level
GeranCsfbSwitch, UtranFlashCsfbSwitch,
GeranFlashCsfbSwitch, CsfbAdaptiveBlindHoSwitch,
UtranCsfbSteeringSwitch, GeranCsfbSteeringSwitch
Default Value: SrvBasedInterFreqHoSw:On,
GeranSepOpMobilitySwitch:Off,
UtranCsfbSwitch:Off, GeranCsfbSwitch:Off,
UtranFlashCsfbSwitch:Off, GeranFlashCsfbS-
witch:Off, CsfbAdaptiveBlindHoSwitch:Off,
UtranCsfbSteeringSwitch:Off, GeranCsfbSteeringS-
witch:Off
ENodeB HoAlgo MOD LBFD-0 Coverag Meaning: Indicates whether to enable handover
AlgoSwi Switch ENODE 0201801 e Based algorithms. This parameter includes the following
tch BALGO / Intra- options: IntraFreqCoverHoSwitch: If this option is
SWITC TDLBF frequenc selected, coverage-based intra-frequency handovers
H D-00201 y are enabled to ensure service continuity. If this option
LST 801 Handov is deselected, coverage-based intra-frequency
ENODE LBFD-0 er handovers are disabled. InterFreqCoverHoSwitch: If
BALGO 0201802 Distance this option is selected, coverage-based inter-frequency
SWITC / Based handovers are enabled to ensure service continuity. If
H TDLBF Inter- this option is deselected, coverage-based inter-
D-00201 frequenc frequency handovers are disabled. UtranCsfbSwitch:
802 y If this option is selected, CSFB to UTRAN is enabled
Handov and UEs can fall back to UTRAN. If this option is
LBFD-0 deselected, CSFB to UTRAN is disabled.
er
0201804 GeranCsfbSwitch: If this option is selected, CSFB to
/ Service
GERAN is enabled and UEs can fall back to GERAN.
TDLBF Based
If this option is deselected, CSFB to GERAN is
D-00201 Inter-
disabled. Cdma1xRttCsfbSwitch: If this option is
804 frequenc
selected, CSFB to CDMA2000 1xRTT is enabled and
y
LBFD-0 UEs can fall back to CDMA2000 1xRTT. If this
Handov
0201805 option is deselected, CSFB to CDMA2000 1xRTT is
er
/ disabled. UtranServiceHoSwitch: If this option is
TDLBF CS selected, service-based handovers to UTRAN are
D-00201 Fallback enabled and UEs using a specific type of services can
805 to be handed over to UTRAN. If this option is
UTRAN deselected, service-based handovers to UTRAN are
LOFD-0
CS disabled. GeranServiceHoSwitch: If this option is
01033 /
Fallback selected, service-based handovers to GERAN are
TDLOF
to enabled and UEs using a specific type of services can
D-00103
GERAN be handed over to GERAN. If this option is
3
CS deselected, service-based handovers to GERAN are
LOFD-0 Fallback disabled. CdmaHrpdServiceHoSwitch: If this option is
01034 / to selected, service-based handovers to CDMA2000
TDLOF CDMA2 HRPD cells are enabled and UEs using a specific type
D-00103 000 of services can be handed over to CDMA2000 HRPD
4 1xRTT cells. If this option is deselected, service-based
LOFD-0 handovers to CDMA2000 HRPD cells are disabled.
Flash
01035 / This option is not supported in this version.
CS
TDLOF Cdma1xRttServiceHoSwitch: If this option is
Fallback
D-00103 selected, service-based handovers to CDMA2000
to
5 1xRTT are enabled and UEs using a specific type of
UTRAN
services can be handed over to CDMA2000 1xRTT. If
LOFD-0 Flash this option is deselected, service-based handovers to
01052 / CS CDMA2000 1xRTT are disabled. This option is not
TDLOF Fallback supported in this version. UlQualityInterRATHoS-
D-00105 to witch: If this option is selected, UL-quality-based
2 GERAN inter-RAT handovers are enabled and UEs can be
LOFD-0 CS handed over to inter-RAT cells to ensure service
01053 / Fallback
ForbidR8R9UeAccessB41Sw:Off,
MOUeCompatEffectSw:Off, PerExtendBitSw:Off,
InterFddTddMeasComOptSw:Off
ENodeB FreqLay MOD LOFD-0 SRVCC Meaning: This parameter includes the following three
AlgoSwi erSwtich ENODE 01087 Flexible switches: UtranFreqLayerMeasSwitch,
tch BALGO LOFD-0 Steering UtranFreqLayerBlindSwitch, and UtranSrvccSwitch.
SWITC 01078 / to The setting of UtranSrvccSwitch takes effect only
H TDLOF UTRAN when UtranFreqLayerMeasSwitch is on. If
LST D-00107 E- UtranFreqLayerMeasSwitch is on, the UTRAN
ENODE 8 UTRAN hierarchy-based measurement algorithm takes effect
BALGO to for measurements related to coverage-based and
TDLOF CSFB-triggered handovers from E-UTRAN to
SWITC D-00102 UTRAN
H CS/PS UTRAN. If UtranFreqLayerBlindSwitch is on, the
2 UTRAN hierarchy-based blind-handover algorithm
Steering
TDLOF takes effect for coverage-based and CSFB-triggered
D-00103 SRVCC blind handovers from E-UTRAN to UTRAN. If
3 to UtranSrvccSwitch is on, the UTRAN SRVCC
UTRAN hierarchy-based measurement algorithm takes effect
TDLOF
D-00105 CS for coverage-based SRVCC-triggered handovers from
2 Fallback E-UTRAN to UTRAN.
TDLOF to GUI Value Range: UtranFreqLayerMeasS-
D-00108 UTRAN witch(UtranFreqLayerMeasSwitch),
8 Flash UtranFreqLayerBlindSwitch(UtranFreqLayerBlind-
CS Switch), UtranSrvccSteeringSwitch(UtranSrvccSteer-
Fallback ingSwitch)
to Unit: None
UTRAN Actual Value Range: UtranFreqLayerMeasSwitch,
CS UtranFreqLayerBlindSwitch, UtranSrvccSteeringS-
Fallback witch
Steering Default Value: UtranFreqLayerMeasSwitch:Off,
to UtranFreqLayerBlindSwitch:Off, UtranSrvccSteer-
UTRAN ingSwitch:Off
UtranNF CsPriori ADD LOFD-0 E- Meaning: Indicates the circuit switched (CS) priority
req ty UTRAN 01078 / UTRAN of the neighboring UTRAN frequency, that is, the
NFREQ TDLOF to priority for the neighboring UTRAN frequency to
MOD D-00107 UTRAN carry CS services. During CSFB-based CS service
UTRAN 8 CS/PS handovers with UtranFreqLayerMeasSwitch being on,
NFREQ TDLOF Steering the eNodeB selects and delivers the neighboring
D-00103 CS UTRAN frequencies based on the CS priorities when
LST starting measurements. The eNodeB preferentially
UTRAN 3 Fallback
to delivers the UTRAN frequency with the highest CS
NFREQ TDLOF priority to measure. During CSFB-based CS service
D-00105 UTRAN
handovers with UtranFreqLayerBlindSwitch being on,
2 Flash the eNodeB selects the target cells for blind handovers
TDLOF CS on neighboring UTRAN frequencies based on the CS
D-00108 Fallback priorities and preferentially selects the target cell for
8 to blind handovers on the neighboring UTRAN
UTRAN frequency with the highest CS priorities. If this
CS parameter is set to Priority_0, this neighboring
Fallback UTRAN frequency is not prioritized.
Steering GUI Value Range: Priority_0(Priority 0),
to Priority_1(Priority 1), Priority_2(Priority 2),
UTRAN Priority_3(Priority 3), Priority_4(Priority 4),
Priority_5(Priority 5), Priority_6(Priority 6),
Priority_7(Priority 7), Priority_8(Priority 8),
Priority_9(Priority 9), Priority_10(Priority 10),
Priority_11(Priority 11), Priority_12(Priority 12),
Priority_13(Priority 13), Priority_14(Priority 14),
Priority_15(Priority 15), Priority_16(Priority 16)
Unit: None
Actual Value Range: Priority_0, Priority_1,
Priority_2, Priority_3, Priority_4, Priority_5,
Priority_6, Priority_7, Priority_8, Priority_9,
Priority_10, Priority_11, Priority_12, Priority_13,
Priority_14, Priority_15, Priority_16
Default Value: Priority_2(Priority 2)
TDLOF GERAN
D-00109 Enhance
0 d CS
Fallback
to
CDMA2
000
1xRTT
CellOp IdleCsfb ADD LOFD-0 CS Meaning: Indicates the highest-priority target RAT for
HoCfg Highest CELLO 01033 / Fallback CSFB initiated by UEs in idle mode. It is UTRAN by
Pri PHOCF TDLOF to default. This parameter can be set to UTRAN,
G D-00103 UTRAN GERAN, or CDMA2000.
MOD 3 CS GUI Value Range: UTRAN, GERAN, CDMA2000
CELLO LOFD-0 Fallback Unit: None
PHOCF 01034 / to
G TDLOF Actual Value Range: UTRAN, GERAN, CDMA2000
GERAN
LST D-00103 Default Value: UTRAN
CS
CELLO 4
Fallback
PHOCF LOFD-0 to
G 01035 / CDMA2
TDLOF 000
D-00103 1xRTT
5
Flash
LOFD-0 CS
01052 / Fallback
TDLOF to
D-00105 UTRAN
2
Flash
LOFD-0 CS
01053 / Fallback
TDLOF to
D-00105 GERAN
3
Enhance
LOFD-0 d CS
01090 / Fallback
TDLOF to
D-00109 CDMA2
0 000
LOFD-0 1xRTT
70202 /
Ultra-
TDLOF
Flash
D-07020
CSFB to
2
UTRAN
LOFD-0
Ultra-
81283 /
Flash
TDLOF
CSFB to
D-08120
GERAN
3
CellOp IdleCsfb ADD LOFD-0 CS Meaning: Indicates the medium-priority target RAT
HoCfg SecondP CELLO 01033 / Fallback for CSFB initiated by UEs in idle mode. It is GERAN
ri PHOCF TDLOF to by default. If this parameter is set to UTRAN,
G D-00103 UTRAN GERAN, or CDMA2000, the medium-priority target
MOD 3 CS RAT is UTRAN, GERAN, or CDMA2000,
CELLO LOFD-0 Fallback respectively. If this parameter is set to NULL, no
PHOCF 01034 / to medium-priority target RAT is specified and only the
G TDLOF GERAN highest-priority target RAT can be selected for CSFB
D-00103 initiated by UEs in idle mode.
LST CS
CELLO 4 GUI Value Range: UTRAN, GERAN, CDMA2000,
Fallback
PHOCF LOFD-0 NULL
to
G 01035 / CDMA2 Unit: None
TDLOF 000 Actual Value Range: UTRAN, GERAN, CDMA2000,
D-00103 1xRTT NULL
5
Flash Default Value: GERAN
LOFD-0 CS
01052 / Fallback
TDLOF to
D-00105 UTRAN
2
Flash
LOFD-0 CS
01053 / Fallback
TDLOF to
D-00105 GERAN
3
Enhance
LOFD-0 d CS
01090 / Fallback
TDLOF to
D-00109 CDMA2
0 000
LOFD-0 1xRTT
70202 /
Ultra-
TDLOF
Flash
D-07020
CSFB to
2
UTRAN
LOFD-0
Ultra-
81283 /
Flash
TDLOF
CSFB to
D-08120
GERAN
3
CellOp IdleCsfb ADD LOFD-0 CS Meaning: Indicates the lowest-priority target RAT for
HoCfg LowestP CELLO 01033 / Fallback CSFB initiated by UEs in idle mode. It is CDMA2000
ri PHOCF TDLOF to by default. If this parameter is set to UTRAN,
G D-00103 UTRAN GERAN, or CDMA2000, the lowest-priority target
MOD 3 CS RAT is UTRAN, GERAN, or CDMA2000,
CELLO LOFD-0 Fallback respectively. If this parameter is set to NULL, no
PHOCF 01034 / to lowest-priority target RAT is specified and only the
G TDLOF GERAN highest- or medium-priority target RAT can be
D-00103 selected for CSFB initiated by UEs in idle mode.
LST CS
CELLO 4 GUI Value Range: UTRAN, GERAN, CDMA2000,
Fallback
PHOCF LOFD-0 NULL
to
G 01035 / CDMA2 Unit: None
TDLOF 000 Actual Value Range: UTRAN, GERAN, CDMA2000,
D-00103 1xRTT NULL
5
Flash Default Value: CDMA2000
LOFD-0 CS
01052 / Fallback
TDLOF to
D-00105 UTRAN
2
Flash
LOFD-0 CS
01053 / Fallback
TDLOF to
D-00105 GERAN
3
Enhance
LOFD-0 d CS
01090 / Fallback
TDLOF to
D-00109 CDMA2
0 000
LOFD-0 1xRTT
70202 /
Ultra-
TDLOF
Flash
D-07020
CSFB to
2
UTRAN
LOFD-0
Ultra-
81283 /
Flash
TDLOF
CSFB to
D-08120
GERAN
3
CSFallB IdleMod MOD LOFD-0 CS Meaning: Indicates the CSFB policy for a UE in idle
ackPolic eCsfbHo CSFAL 01088 / Fallback mode. The policy can be PS handover, CCO, or
yCfg PolicyCf LBACK TDLOF Steering redirection.
g POLIC D-00108 to GUI Value Range: REDIRECTION, CCO_HO,
YCFG 8 UTRAN PS_HO
LST LOFD-0 CS Unit: None
CSFAL 01089 / Fallback
LBACK TDLOF Steering Actual Value Range: REDIRECTION, CCO_HO,
POLIC D-00108 to PS_HO
YCFG 9 GERAN Default Value: REDIRECTION:On, CCO_HO:On,
PS_HO:On
TDLOF to
D-00107 GERAN
3 Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN
CellOp InterRat ADD LOFD-0 CS Meaning: Indicates the highest-priority target RAT for
HoCfg Highest CELLO 01033 / Fallback handovers. It is UTRAN by default. This parameter
Pri PHOCF TDLOF to can be set to UTRAN, GERAN, or CDMA2000.
G D-00103 UTRAN GUI Value Range: UTRAN, GERAN, CDMA2000
MOD 3 CS Unit: None
CELLO LOFD-0 Fallback
PHOCF 01034 / to Actual Value Range: UTRAN, GERAN, CDMA2000
G TDLOF GERAN Default Value: UTRAN
LST D-00103 CS
CELLO 4 Fallback
PHOCF LOFD-0 to
G 01035 / CDMA2
TDLOF 000
D-00103 1xRTT
5 PS Inter-
LOFD-0 RAT
01019 / Mobility
TDLOF between
D-00101 E-
9 UTRAN
and
LOFD-0
UTRAN
01020 /
TDLOF PS Inter-
D-00102 RAT
0 Mobility
between
LOFD-0
E-
01021 /
UTRAN
TDLOF
and
D-00102
GERAN
1
PS Inter-
LOFD-0
RAT
01052 /
Mobility
TDLOF
between
D-00105
E-
2
UTRAN
LOFD-0 and
01053 / CDMA2
TDLOF 000
D-00105
Flash
3
CS
LOFD-0 Fallback
01090 / to
TDLOF UTRAN
D-00109 Flash
0 CS
Fallback
LOFD-0 to
70202 / GERAN
TDLOF Enhance
D-07020 d CS
2 Fallback
LOFD-0 to
81283 / CDMA2
TDLOF 000
D-08120 1xRTT
3 Ultra-
Flash
CSFB to
UTRAN
Ultra-
Flash
CSFB to
GERAN
TDLOF to
D-00107 GERAN
3 Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN
CellOp InterRat ADD LOFD-0 CS Meaning: Indicates the medium-priority target RAT
HoCfg SecondP CELLO 01033 / Fallback for handovers. It is GERAN by default. If this
ri PHOCF TDLOF to parameter is set to UTRAN, GERAN, or CDMA2000,
G D-00103 UTRAN the medium-priority target RAT is UTRAN, GERAN,
MOD 3 CS or CDMA2000, respectively. If this parameter is set to
CELLO LOFD-0 Fallback NULL, no medium-priority target RAT is specified
PHOCF 01034 / to and only the highest-priority target RAT can be
G TDLOF GERAN selected for handovers.
LST D-00103 CS GUI Value Range: UTRAN, GERAN, CDMA2000,
CELLO 4 Fallback NULL
PHOCF LOFD-0 to Unit: None
G 01035 / CDMA2 Actual Value Range: UTRAN, GERAN, CDMA2000,
TDLOF 000 NULL
D-00103 1xRTT
5 Default Value: GERAN
PS Inter-
LOFD-0 RAT
01019 / Mobility
TDLOF between
D-00101 E-
9 UTRAN
and
LOFD-0
UTRAN
01020 /
TDLOF PS Inter-
D-00102 RAT
0 Mobility
between
LOFD-0
E-
01021 /
UTRAN
TDLOF
and
D-00102
GERAN
1
PS Inter-
LOFD-0
RAT
01052 /
Mobility
TDLOF
between
D-00105
E-
2
UTRAN
LOFD-0 and
01053 / CDMA2
TDLOF 000
D-00105
Flash
3
CS
LOFD-0 Fallback
01090 / to
TDLOF UTRAN
D-00109 Flash
0 CS
Fallback
LOFD-0 to
70202 / GERAN
TDLOF Enhance
D-07020 d CS
2 Fallback
LOFD-0 to
81283 / CDMA2
TDLOF 000
D-08120 1xRTT
3 Ultra-
Flash
CSFB to
UTRAN
Ultra-
Flash
CSFB to
GERAN
TDLOF to
D-00107 GERAN
3 Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN
CellOp InterRat ADD LOFD-0 CS Meaning: Indicates the lowest-priority target RAT for
HoCfg LowestP CELLO 01033 / Fallback handovers. It is CDMA2000 by default. If this
ri PHOCF TDLOF to parameter is set to UTRAN, GERAN, or CDMA2000,
G D-00103 UTRAN the lowest-priority target RAT is UTRAN, GERAN,
MOD 3 CS or CDMA2000, respectively. If this parameter is set to
CELLO LOFD-0 Fallback NULL, no lowest-priority target RAT is specified and
PHOCF 01034 / to only the highest- or medium-priority target RAT can
G TDLOF GERAN be selected for handovers.
LST D-00103 CS GUI Value Range: UTRAN, GERAN, CDMA2000,
CELLO 4 Fallback NULL
PHOCF LOFD-0 to Unit: None
G 01035 / CDMA2 Actual Value Range: UTRAN, GERAN, CDMA2000,
TDLOF 000 NULL
D-00103 1xRTT
5 Default Value: CDMA2000
PS Inter-
LOFD-0 RAT
01019 / Mobility
TDLOF between
D-00101 E-
9 UTRAN
and
LOFD-0
UTRAN
01020 /
TDLOF PS Inter-
D-00102 RAT
0 Mobility
between
LOFD-0
E-
01021 /
UTRAN
TDLOF
and
D-00102
GERAN
1
PS Inter-
LOFD-0
RAT
01052 /
Mobility
TDLOF
between
D-00105
E-
2
UTRAN
LOFD-0 and
01053 / CDMA2
TDLOF 000
D-00105
Flash
3
CS
LOFD-0 Fallback
01090 / to
TDLOF UTRAN
D-00109 Flash
0 CS
Fallback
LOFD-0 to
70202 / GERAN
TDLOF Enhance
D-07020 d CS
2 Fallback
LOFD-0 to
81283 / CDMA2
TDLOF 000
D-08120 1xRTT
3 Ultra-
Flash
CSFB to
UTRAN
Ultra-
Flash
CSFB to
GERAN
UtranNF CsPsMi ADD LOFD-0 CS Meaning: Indicates the priority for the neighboring
req xedPrior UTRAN 01088 / Fallback UTRAN frequency to carry CS+PS combined
ity NFREQ TDLOF Steering services. In measurement-based CSFB to UTRAN, if
MOD D-00108 to UtranCsfbSteeringSwitch and UtranFreqLayerMeasS-
UTRAN 8 UTRAN witch are turned on, the eNodeB determines the
NFREQ LOFD-0 PS Inter- UTRAN frequency to be delivered to a UE in
01019 / RAT RRC_CONNECTED mode based on the priority
LST specified by this parameter. The eNodeB
UTRAN TDLOF Mobility
D-00101 between preferentially delivers the UTRAN frequency with the
NFREQ highest CS+PS combined service priority to the UE.
9 E-
UTRAN In blind CSFB to UTRAN, if UtranCsfbSteeringS-
TDLOF witch and UtranFreqLayerBlindSwitch are turned on,
D-00103 and
UTRAN the target cell is selected based on the priority
3 specified by this parameter. The cell on the UTRAN
TDLOF CS frequency with the highest priority is preferentially
D-00105 Fallback selected. If this parameter is set to Priority_0, the
2 to UTRAN frequency is not included in priority
UTRAN arrangement for neighboring UTRAN frequencies to
TDLOF
D-00107 Flash carry CS+PS combined services.
8 CS GUI Value Range: Priority_0(Priority 0),
Fallback Priority_1(Priority 1), Priority_2(Priority 2),
to Priority_3(Priority 3), Priority_4(Priority 4),
UTRAN Priority_5(Priority 5), Priority_6(Priority 6),
E- Priority_7(Priority 7), Priority_8(Priority 8),
UTRAN Priority_9(Priority 9), Priority_10(Priority 10),
to Priority_11(Priority 11), Priority_12(Priority 12),
UTRAN Priority_13(Priority 13), Priority_14(Priority 14),
CS/PS Priority_15(Priority 15), Priority_16(Priority 16)
steering Unit: None
Actual Value Range: Priority_0, Priority_1,
Priority_2, Priority_3, Priority_4, Priority_5,
Priority_6, Priority_7, Priority_8, Priority_9,
Priority_10, Priority_11, Priority_12, Priority_13,
Priority_14, Priority_15, Priority_16
Default Value: Priority_2(Priority 2)
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the CSFB policy for a UE in
ackPolic PolicyCf CSFAL 01033 / Fallback connected mode. If the CSFB steering function is
yCfg g LBACK TDLOF to disabled, this parameter also applies to UEs in idle
POLIC D-00103 UTRAN mode. The policy can be PS handover, CCO, or
YCFG 3 CS redirection.
LST LOFD-0 Fallback GUI Value Range: REDIRECTION, CCO_HO,
CSFAL 01034 / to PS_HO
LBACK TDLOF GERAN Unit: None
POLIC D-00103 CS
YCFG 4 Actual Value Range: REDIRECTION, CCO_HO,
Fallback PS_HO
LOFD-0 Steering
01088 / to Default Value: REDIRECTION:On, CCO_HO:On,
TDLOF UTRAN PS_HO:On
D-00108 CS
8 Fallback
LOFD-0 Steering
01089 / to
TDLOF GERAN
D-00108
9
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the RSCP threshold for event B1,
ackHo UtranB1 CSFAL 01033 / Fallback which is used in CS fallback to UTRAN. When CS
ThdRsc LBACK TDLOF to fallback to UTRAN is applicable, this parameter is set
p HO D-00103 UTRAN for UEs and used in the evaluation about whether to
LST 3 trigger event B1. This parameter indicates the RSCP
CSFAL requirement for the UTRAN cells to be included in the
LBACK measurement report. A UE sends a measurement
HO report related to event B1 to the eNodeB when the
RSCP in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For
details, see 3GPP TS 36.331.
GUI Value Range: -120~-25
Unit: dBm
Actual Value Range: -120~-25
Default Value: -106
InterRat InterRat MOD LOFD-0 PS Inter- Meaning: Indicates the quantity to be measured for
HoCom HoUtran INTER 01019 / RAT handovers to UTRAN. For details, see 3GPP TS
m B1Meas RATHO TDLOF Mobility 36.331. This parameter applies only to UTRAN FDD.
Quan COMM D-00101 between The RSCP values are relatively stable, while the
LST 9 E- Ec/No values fluctuate with the network load. The
INTER LOFD-0 UTRAN value BOTH applies only to UEs complying with
RATHO 01022 / and 3GPP Release 10. For UEs complying with 3GPP
COMM TDLOF UTRAN Release 8 or 9, the value BOTH is equivalent to the
D-00102 SRVCC value RSCP. QoE-based handover algorithms do not
2 to apply to UEs complying with 3GPP Release 8 and
UTRAN Release 9, and the parameter value is fixed as ECN0.
LOFD-0
01033 / CS GUI Value Range: RSCP, ECN0, BOTH
TDLOF Fallback Unit: None
D-00103 to Actual Value Range: RSCP, ECN0, BOTH
3 UTRAN
Default Value: ECN0
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the Ec/N0 threshold for event B1,
ackHo UtranB1 CSFAL 01033 / Fallback which is used in CS fallback to UTRAN. When CS
ThdEcn LBACK TDLOF to fallback to UTRAN is required, this parameter is set
0 HO D-00103 UTRAN for UEs and used in the evaluation about whether to
LST 3 trigger event B1. This parameter indicates the Ec/N0
CSFAL requirement for the UTRAN cells to be included in the
LBACK measurement report. A UE sends a measurement
HO report related to event B1 to the eNodeB when the
Ec/N0 in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For
a cell with large signal fading variance, set this
parameter to a large value to prevent unnecessary
handovers. For a cell with small signal fading
variance, set this parameter to a small value to ensure
timely handovers. For details, see 3GPP TS 36.331.
GUI Value Range: -48~0
Unit: 0.5dB
Actual Value Range: -24~0
Default Value: -24
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the time-to-trigger for event B1
ackHo UtranTi CSFAL 01033 / Fallback that is used in CS fallback to UTRAN. When CS
meToTri LBACK TDLOF to fallback to UTRAN is applicable, this parameter is set
g HO D-00103 UTRAN for UEs and used in the evaluation of whether to
LST 3 trigger event B1. When detecting that the signal
CSFAL quality in at least one UTRAN cell meets the entering
LBACK condition, the UE does not send a measurement report
HO to the eNodeB immediately. Instead, the UE sends a
report only when the signal quality continuously
meets the entering condition during the time-to-
trigger. This parameter helps decrease the number of
occasionally triggered event reports, the average
number of handovers, and the number of wrong
handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Default Value: 40ms
CSFallB BlindHo MOD LOFD-0 Flash Meaning: Indicates the reference signal received
ackHo A1ThdR CSFAL 01052 / CS power (RSRP) threshold for event A1 associated with
srp LBACK TDLOF Fallback CSFB-triggered adaptive blind handovers. This
HO D-00105 to parameter is set for a UE as a triggering condition of
LST 2 UTRAN event A1 measurement related to a CSFB-triggered
CSFAL LOFD-0 Flash adaptive blind handover. This parameter specifies the
LBACK 01053 / CS RSRP threshold of the serving cell above which a
HO TDLOF Fallback CSFB-triggered adaptive blind handover is triggered.
D-00105 to If the RSRP value measured by a UE exceeds this
3 GERAN threshold, the UE submits a measurement report
related to event A1.
GUI Value Range: -140~-43
Unit: dBm
Actual Value Range: -140~-43
Default Value: -80
UtranNF ConnFre ADD LOFD-0 PS Inter- Meaning: Indicates the frequency priority based on
req qPriority UTRAN 01019 / RAT which the eNodeB selects a target frequency for blind
NFREQ TDLOF Mobility redirection or contains a frequency in a measurement
MOD D-00101 between configuration. If a blind redirection is triggered and
UTRAN 9 E- the target neighboring cell is not specified, the
NFREQ TDLBF UTRAN eNodeB selects a target frequency based on this
D-00201 and priority. If a measurement configuration is to be
LST UTRAN delivered, the eNodeB preferentially delivers a
UTRAN 803
Cell frequency with the highest priority. If this priority is
NFREQ TDLOF set to 0 for a frequency, this frequency is not selected
D-00102 Selectio
n and as the target frequency for a blind redirection. A larger
2 value indicates a higher priority.
Re-
TDLOF selection GUI Value Range: 0~8
D-00103
3 SRVCC Unit: None
to Actual Value Range: 0~8
TDLOF UTRAN
D-00105 Default Value: 0
2 CS
Fallback
TDLOF to
D-00104 UTRAN
3
Flash
TDLOF CS
D-00107 Fallback
2 to
TDLOF UTRAN
D-00107 Service
8 based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
steering
ENodeB NCellRa MOD LOFD-0 Inter- Meaning: Indicates whether to enable neighboring cell
AlgoSwi nkingSw ENODE 02002/ RAT ranking. This parameter consists of the following
tch itch BALGO TDLOF ANR switches: GERAN_SWITCH: Indicates whether the
SWITC D-00200 SRVCC eNodeB prioritizes measurement priorities of
H 2 to neighboring GERAN cells based on the number of
LST LOFD-0 UTRAN each neighboring GERAN cell is measured within a
ENODE 01022/ period of time. The eNodeB prioritizes measurement
CS priorities only when this switch is on.
BALGO TDLOF Fallback
SWITC D-00102 UTRAN_SWITCH: Indicates whether the eNodeB
to prioritizes measurement priorities of neighboring
H 2 UTRAN UTRAN cells based on the number of each
LOFD-0 Flash neighboring UTRAN cell is measured within a period
01033/ CS of time. The eNodeB prioritizes measurement
TDLOF Fallback priorities of neighboring UTRAN cells based on the
D-00103 to number of each neighboring UTRAN cell is measured
3 UTRAN within a period of time only when this switch is on.
LOFD-0 Flash GUI Value Range: GERAN_SWITCH(GERAN
01052/ CS Neighboring Cell Ranking Switch),
TDLOF Fallback UTRAN_SWITCH(UTRAN Neighboring Cell
D-00105 to Ranking Switch)
2 GERAN Unit: None
LOFD-0 PS Inter-
01053/ Actual Value Range: GERAN_SWITCH,
RAT UTRAN_SWITCH
TDLOF Mobility
D-00105 between Default Value: GERAN_SWITCH:Off,
3 E- UTRAN_SWITCH:Off
LOFD-0 UTRAN
01019/ and
TDLOF UTRAN
D-00101 Service
9 based
LOFD-0 inter-
01043/ RAT
TDLOF handove
D-00104 r to
3 UTRAN
LOFD-0 Distance
01072/ based
TDLOF inter-
D-00107 RAT
2 handove
r to
UTRAN
UtranN NCellM ADD LOFD-0 Inter- Meaning: Indicates the measurement priority of the
Cell easPriori UTRAN 02002/ RAT neighboring UTRAN cell. A larger value indicates a
ty NCELL TDLOF ANR higher priority. The measurement priorities can be
DSP D-00200 SRVCC periodically and automatically arranged based on the
UTRAN 2 to number of times that each neighboring UTRAN cell is
EXTEN LOFD-0 UTRAN measured. The neighboring UTRAN cells for UTRAN
DEDNC 01022/ measurement control, UTRAN flash blind
CS redirections, and UTRAN flash-CSFB-based
ELL TDLOF Fallback
D-00102 redirections can be selected based on the measurement
LST to priorities of neighboring UTRAN cells.
UTRAN 2 UTRAN
NCELL LOFD-0 GUI Value Range: 0~128
Flash
01033/ CS Unit: None
TDLOF Fallback Actual Value Range: 0~128
D-00103 to
3 Default Value: 0
UTRAN
LOFD-0 PS Inter-
01052/ RAT
TDLOF Mobility
D-00105 between
2 E-
LOFD-0 UTRAN
01019/ and
TDLOF UTRAN
D-00101 Service
9 based
LOFD-0 inter-
01043/ RAT
TDLOF handove
D-00104 r to
3 UTRAN
LOFD-0 Distance
01072/ based
TDLOF inter-
D-00107 RAT
2 handove
r to
UTRAN
UtranN CellMea ADD LOFD-0 PS Inter- Meaning: Indicates the priority of measurement on the
Cell sPriority UTRAN 01019 RAT neighboring UTRAN cell. The eNodeB preferentially
NCELL TDLOF Mobility contains the information about a neighboring cell with
MOD D-00102 between this priority set to HIGH_PRIORITY while delivering
UTRAN 2 E- a measurement configuration.
NCELL UTRAN GUI Value Range: LOW_PRIORITY(Low Priority),
TDLOF and
LST D-00103 HIGH_PRIORITY(High Priority)
UTRAN
UTRAN 3 Unit: None
NCELL SRVCC
TDLOF Actual Value Range: LOW_PRIORITY,
to
D-00105 HIGH_PRIORITY
UTRAN
2 Default Value: LOW_PRIORITY(Low Priority)
CS
TDLOF
Fallback
D-00101
to
9
UTRAN
TDLOF
D-00104 Flash
3 CS
Fallback
TDLOF to
D-00107 UTRAN
2
PS Inter-
TDLOF RAT
D-00107 Mobility
8 between
E-
UTRAN
and
UTRAN
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
steering
CellUe MaxUtr MOD LOFD-0 PS Inter- Meaning: Indicates the maximum number of UTRAN
MeasCo anTddM CELLU 01019 / RAT TDD frequencies that can be contained in the
ntrolCfg easFreq EMEAS TDLOF Mobility measurement control messages delivered for UEs in
Num CONTR D-00101 between RRC_CONNECTED state.
OLCFG 9 E- GUI Value Range: 1~16
LST LOFD-0 UTRAN
and Unit: None
CELLU 01022 /
EMEAS TDLOF UTRAN Actual Value Range: 1~16
CONTR D-00102 SRVCC Default Value: 3
OLCFG 2 to
LOFD-0 UTRAN
01043 / Service
TDLOF based
D-00104 Inter-
3 RAT
LOFD-0 handove
01072 / r to
TDLOF UTRAN
D-00107 Distance
2 based
LOFD-0 Inter-
01033 / RAT
TDLOF handove
D-00103 r to
3 UTRAN
CS
Fallback
to
UTRAN
UtranN BlindHo ADD LOFD-0 PS Inter- Meaning: Indicates the priority of the neighboring cell
Cell Priority UTRAN 01019 RAT during blind handovers. Blind handover is a process in
NCELL TDLOF Mobility which the eNodeB instructs a UE to hand over to a
MOD D-00102 between specified neighboring cell. There are 32 priorities
UTRAN 2 E- altogether. The priority has a positive correlation with
NCELL UTRAN the value of this parameter. Note that the value 0
TDLOF and indicates that blind handovers to the neighboring cell
LST D-00103 UTRAN are not allowed.
UTRAN 3
NCELL SRVCC GUI Value Range: 0~32
TDLOF
to Unit: None
D-00105
UTRAN
2 Actual Value Range: 0~32
CS
TDLOF Default Value: 0
Fallback
D-00101
to
9
UTRAN
TDLOF
D-00104 Flash
3 CS
Fallback
TDLOF to
D-00107 UTRAN
2
PS Inter-
TDLOF RAT
D-00107 Mobility
8 between
E-
UTRAN
and
UTRAN
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
steering
CellHoP CsfbMR MOD LOFD-0 CS Meaning: Indicates the length of the timer that the
araCfg Waiting CELLH 01033 / Fallback eNodeB waits for the next measurement report after
Timer OPARA TDLOF to receiving the first measurement report for
CFG D-00103 UTRAN measurement-based CSFB to UTRAN.
LST 3 GUI Value Range: 60~1000
CELLH Unit: ms
OPARA
CFG Actual Value Range: 60~1000
Default Value: 100
InterRat CellInfo MOD LOFD-0 PS Inter- Meaning: Indicates the maximum number of UTRAN
HoCom MaxUtr INTER 01019 / RAT cell system information messages that can be
m anCellN RATHO TDLOF Mobility transmitted during a flash redirection procedure.
um COMM D-00101 between GUI Value Range: 1~16
LST 9 E-
UTRAN Unit: None
INTER TDLOF
RATHO D-00105 and Actual Value Range: 1~16
COMM 2 UTRAN Default Value: 8
Flash
CS
Fallback
to
UTRAN
CSFallB CsfbProt MOD LOFD-0 CS Meaning: Indicates the timer governing the period in
ackHo ectionTi CSFAL 01033 / Fallback which only CSFB can be performed . After the timer
mer LBACK TDLOF to expires, the eNodeB performs a blind redirection for
HO D-00103 UTRAN the UE.
LST 3 CS GUI Value Range: 1~10
CSFAL LOFD-0 Fallback Unit: s
LBACK 01033 / to
HO TDLOF GERAN Actual Value Range: 1~10
D-00103 Enhance Default Value: 4
4 d CS
LOFD-0 Fallback
01033 / to
TDLOF CDMA2
D-00109 000
0 1xRTT
InterRat UtranCe MOD LOFD-0 CS Meaning: Indicates the maximum number of UTRAN
HoCom llNumF INTER 01033 / Fallback cell system information messages that can be
m orEmcR RATHO TDLOF to transmitted during a CSFB emergency redirection
edirect COMM D-00103 UTRAN procedure.
LST 3 Flash GUI Value Range: 0~16
INTER TDLOF CS Unit: None
RATHO D-00105 Fallback
COMM 2 to Actual Value Range: 0~16
UTRAN Default Value: 0
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch
Unit: None
Actual Value Range: RrcSetupOptSwitch,
IucsRrcRecfgMcCombSwitch,
RcrpRrcRecfgMcCombSwitch,
RrcRecfgMcOptSwitch, IdleCsfbRedirectOptSwitch,
UlNasBufferSwitch, IratMeasCfgTransSwitch,
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch
Default Value: RrcSetupOptSwitch:Off,
IucsRrcRecfgMcCombSwitch:Off,
RcrpRrcRecfgMcCombSwitch:Off,
RrcRecfgMcOptSwitch:Off, IdleCsfbRedirectOptS-
witch:Off, UlNasBufferSwitch:Off,
IratMeasCfgTransSwitch:Off,
GeranAnrMcOptSwitch:Off, InactDiscardSwitch:Off,
SRVCCHoBasedUeCapSwitch:Off,
L2GPLMNChooseOptSwitch:Off,
HoInRrcRecfgMcCombSwitch:Off,
UeCapEnquiryCombSwitch:Off,
UeTraceOptSwitch:Off
ter1_bit24),
RsvdSwPara1_bit25(ReservedSwitchParame-
ter1_bit25),
RsvdSwPara1_bit26(ReservedSwitchParame-
ter1_bit26),
RsvdSwPara1_bit27(ReservedSwitchParame-
ter1_bit27),
RsvdSwPara1_bit28(ReservedSwitchParame-
ter1_bit28),
RsvdSwPara1_bit29(ReservedSwitchParame-
ter1_bit29),
RsvdSwPara1_bit30(ReservedSwitchParame-
ter1_bit30),
RsvdSwPara1_bit31(ReservedSwitchParame-
ter1_bit31),
RsvdSwPara1_bit32(ReservedSwitchParame-
ter1_bit32)
Unit: None
Actual Value Range: RsvdSwPara1_bit1,
RsvdSwPara1_bit2, RsvdSwPara1_bit3,
RsvdSwPara1_bit4, RsvdSwPara1_bit5,
RsvdSwPara1_bit6, RsvdSwPara1_bit7,
RsvdSwPara1_bit8, RsvdSwPara1_bit9,
RsvdSwPara1_bit10, RsvdSwPara1_bit11,
RsvdSwPara1_bit12, RsvdSwPara1_bit13,
RsvdSwPara1_bit14, RsvdSwPara1_bit15,
RsvdSwPara1_bit16, RsvdSwPara1_bit17,
RsvdSwPara1_bit18, RsvdSwPara1_bit19,
RsvdSwPara1_bit20, RsvdSwPara1_bit21,
RsvdSwPara1_bit22, RsvdSwPara1_bit23,
RsvdSwPara1_bit24, RsvdSwPara1_bit25,
RsvdSwPara1_bit26, RsvdSwPara1_bit27,
RsvdSwPara1_bit28, RsvdSwPara1_bit29,
RsvdSwPara1_bit30, RsvdSwPara1_bit31,
RsvdSwPara1_bit32
Default Value: RsvdSwPara1_bit1:Off,
RsvdSwPara1_bit2:Off, RsvdSwPara1_bit3:Off,
RsvdSwPara1_bit4:Off, RsvdSwPara1_bit5:Off,
RsvdSwPara1_bit6:Off, RsvdSwPara1_bit7:Off,
RsvdSwPara1_bit8:Off, RsvdSwPara1_bit9:Off,
RsvdSwPara1_bit10:Off, RsvdSwPara1_bit11:Off,
RsvdSwPara1_bit12:Off, RsvdSwPara1_bit13:Off,
RsvdSwPara1_bit14:Off, RsvdSwPara1_bit15:Off,
RsvdSwPara1_bit16:Off, RsvdSwPara1_bit17:Off,
RsvdSwPara1_bit18:Off, RsvdSwPara1_bit19:Off,
RsvdSwPara1_bit20:Off, RsvdSwPara1_bit21:Off,
RsvdSwPara1_bit22:Off, RsvdSwPara1_bit23:Off,
RsvdSwPara1_bit24:Off, RsvdSwPara1_bit25:Off,
RsvdSwPara1_bit26:Off, RsvdSwPara1_bit27:Off,
RsvdSwPara1_bit28:Off, RsvdSwPara1_bit29:Off,
RsvdSwPara1_bit30:Off, RsvdSwPara1_bit31:Off,
RsvdSwPara1_bit32:Off
CSFallB Normal MOD LBFD-0 Admissi Meaning: Indicates the allocation/retention priority
ackPolic CsfbUse CSFAL 02023 / on (ARP) of a CSFB service triggered by a common call.
yCfg rArp LBACK TDLBF Control When this parameter is set to 1, the service priority is
POLIC D-00202 the same as that of an emergency call. For details
YCFG 3 about the ARP, see 3GPP TS 23.401.
LST GUI Value Range: 1~15
CSFAL Unit: None
LBACK
POLIC Actual Value Range: 1~15
YCFG Default Value: 2
GlobalP UtranLo MOD None None Meaning: Indicates the UMTS load transmission
rocSwitc adTrans GLOBA channel. The eNodeB sends RAN-INFORMATION-
h Chan LPROC REQUEST PDUs to UTRAN cells to request multiple
SWITC reports on the load status of UTRAN cells only when
H the parameter is set to BASED_ON_RIM.The
LST function specified by the parameter value
GLOBA BASED_ON_ECO is temporarily unavailable.
LPROC GUI Value Range: NULL, BASED_ON_RIM,
SWITC BASED_ON_ECO
H Unit: None
Actual Value Range: NULL, BASED_ON_RIM,
BASED_ON_ECO
Default Value: NULL
ENodeB RimOnE MOD MRFD- eCoordi Meaning: Indicates whether the RAN information
AlgoSwi coSwitc ENODE 090211 nator management (RIM) procedure is initiated by the
tch h BALGO LOFD-0 based eCoordinator. If this parameter is set to ON, the RIM
SWITC 01052/ RIM procedure is initiated by the eCoordinator. If this
H TDLOF process parameter is set to OFF, the RIM procedure is initiated
LST D-00105 optimiza by the core network.
ENODE 2 tion GUI Value Range: OFF(Off), ON(On)
BALGO LOFD-0 Flash Unit: None
SWITC 01019/ CS
H Fallback Actual Value Range: OFF, ON
TDLOF
D-00101 to Default Value: OFF(Off)
9 UTRAN
LOFD-0 PS Inter-
01044/ RAT
TDLOF Mobility
D-00104 between
4 E-
UTRAN
LOFD-0 and
01033/ UTRAN
TDLOF
D-00103 Inter-
3 RAT
Load
Sharing
to
UTRA
N(based
on
UMTS
cell load
informat
ion)
CS
Fallback
to
UTRAN
ENodeB RimSwit MOD LOFD-0 CS Meaning: Indicates the collective switch for the RAN
AlgoSwi ch ENODE 01034 / Fallback information management (RIM) function.
tch BALGO TDLOF to UTRAN_RIM_SWITCH: Indicates the switch used to
SWITC D-00103 GERAN enable or disable the RIM procedure that requests
H 4 Flash event-driven multiple reports from UTRAN cells. If
LST LOFD-0 CS this switch is on, the eNodeB can send RAN-
ENODE 01052 / Fallback INFORMATION-REQUEST protocol data units
BALGO TDLOF to (PDUs) to UTRAN cells to request multiple event-
SWITC D-00105 UTRAN driven reports. If this switch is off, the eNodeB cannot
H 2 send RAN-INFORMATION-REQUEST PDUs to
Flash UTRAN cells to request multiple event-driven reports.
LOFD-0 CS GERAN_RIM_SWITCH: Indicates the switch used to
01053 / Fallback enable or disable the RIM procedure that requests
TDLOF to event-driven multiple reports from GERAN cells. If
D-00105 GERAN this switch is on, the eNodeB can send RAN-
3 INFORMATION-REQUEST PDUs to CERAN cells
to request multiple event-driven reports. If this switch
is off, the eNodeB cannot send RAN-
INFORMATION-REQUEST PDUs to GERAN cells
to request multiple event-driven reports.
GUI Value Range: UTRAN_RIM_SWITCH(UTRAN
RIM Switch), GERAN_RIM_SWITCH(GERAN RIM
Switch)
Unit: None
Actual Value Range: UTRAN_RIM_SWITCH,
GERAN_RIM_SWITCH
Default Value: UTRAN_RIM_SWITCH:Off,
GERAN_RIM_SWITCH:Off
ENodeB MultiOp MOD LOFD-0 SRVCC Meaning: Indicates the switch used to control whether
AlgoSwi CtrlSwit ENODE 01022 to operators can adopt different policies. This parameter
tch ch BALGO LOFD-0 UTRAN is a bit-filed-type parameter. By specifying the bit
SWITC 01087 SRVCC fields under this parameter, operators can adopt
H Flexible different policies on the corresponding RAT. This
LOFD-0 parameter applies only to LTE FDD.
LST 01033 Steering
ENODE to UtranSepOpMobilitySwitch is a switch used to
BALGO LOFD-0 UTRAN control whether operators can adopt different mobility
SWITC 01052 policies on their UTRANs. If this switch is on,
CS operators can adopt different policies (such as PS
H LOFD-0
Fallback handover capability and RIM-based system
01068
to information reading capability) on their UTRANs. If
LOFD-0 UTRAN this switch is off, operators cannot adopt different
01088 policies on their UTRANs.
Flash
LOFD-0 CS GUI Value Range: UtranSepOpMobility-
01019 Fallback Switch(UtranSepOpMobilitySwitch)
LOFD-0 to
Unit: None
01043 UTRAN
Actual Value Range: UtranSepOpMobilitySwitch
LOFD-0 CS
01072 Fallback Default Value: UtranSepOpMobilitySwitch:Off
LOFD-0 with
01078 LAI to
UTRAN
CS
Fallback
Steering
to
UTRAN
PS Inter-
RAT
Mobility
between
E-
UTRAN
and
UTRAN
Service
based
inter-
RAT
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
Steering
LOFD-0 CSFB to
70202 / GERAN
TDLOF Ultra-
D-08122 Flash
3 CSFB to
UTRAN
GeranNf ConnFre ADD LOFD-0 PS Inter- Meaning: Indicates the frequency group priority based
reqGrou qPriority GERAN 01020 / RAT on which the eNodeB selects a target frequency group
p NFREQ TDLOF Mobility for blind redirection or delivers a frequency group in
GROUP D-00102 between measurement configuration messages. If a blind
MOD 0 E- redirection is triggered and the target neighboring cell
GERAN TDLOF UTRAN is not specified, the eNodeB selects a target frequency
NFREQ D-00102 and group based on the setting of this parameter. If a
GROUP 3 GERAN measurement configuration is to be delivered, the
SRVCC eNodeB preferentially delivers the frequency group
LST TDLOF with the highest priority. If this parameter is set to 0
GERAN D-00103 to
GERAN for a frequency group, this frequency group is not
NFREQ 4 selected as the target frequency group for a blind
GROUP TDLOF CS redirection. A larger value indicates a higher priority.
D-00105 Fallback
to GUI Value Range: 0~8
3
GERAN Unit: None
Flash Actual Value Range: 0~8
CS Default Value: 0
Fallback
to
GERAN
GeranN BlindHo ADD LOFD-0 PS Inter- Meaning: Indicates the priority of the neighboring cell
cell Priority GERAN 01020 / RAT during blind handovers. Blind handover is a process in
NCELL TDLOF Mobility which the eNodeB instructs a UE to hand over to a
MOD D-00102 between specified neighboring cell. There are 32 priorities
GERAN 0 E- altogether. The priority has a positive correlation with
NCELL TDLOF UTRAN the value of this parameter. Note that the value 0
D-00102 and indicates that blind handovers to the neighboring cell
LST GERAN are not allowed.
GERAN 3
NCELL TDLOF SRVCC GUI Value Range: 0~32
D-00103 to Unit: None
4 GERAN
Actual Value Range: 0~32
TDLOF CS
Fallback Default Value: 0
D-00105
3 to
GERAN
Flash
CS
Fallback
to
GERAN
InterRat CellInfo MOD LOFD-0 PS Inter- Meaning: Indicates the maximum number of GERAN
HoCom MaxGer INTER 01020 / RAT cell system information messages that can be
m anCellN RATHO TDLOF Mobility transmitted during a flash redirection procedure.
um COMM D-00102 between GUI Value Range: 1~32
LST 0 E-
UTRAN Unit: None
INTER TDLOF
RATHO D-00105 and Actual Value Range: 1~32
COMM 3 GERAN Default Value: 8
Flash
CS
Fallback
to
GERAN
GeranEx UltraFla ADD LOFD-0 Ultra- Meaning: Indicates whether an external GERAN cell
ternalCe shCsfbI GERAN 81283 / Flash supports ultra-flash CSFB to GERAN. If this
ll nd EXTER TDLOF CSFB to parameter is set to BOOLEAN_TRUE, the external
NALCE D-08120 GERAN GERAN cell supports ultra-flash CSFB to GERAN. If
LL 3 this parameter is set to BOOLEAN_FALSE, the
MOD external GERAN cell does not support ultra-flash
GERAN CSFB to GERAN.
EXTER GUI Value Range: BOOLEAN_FALSE(False),
NALCE BOOLEAN_TRUE(True)
LL Unit: None
LST Actual Value Range: BOOLEAN_FALSE,
GERAN BOOLEAN_TRUE
EXTER
NALCE Default Value: BOOLEAN_TRUE(True)
LL
CellDrx DrxFor MOD LOFD-0 Ultra- Meaning: Indicates whether to deliver measurement-
Para MeasSw CELLD 81283 / Flash dedicated DRX parameters to a UE when GERAN
itch RXPAR TDLOF CS measurements are triggered for CSFB of the UE. If
A D-08120 Fallback this parameter is set to ON, the eNodeB delivers both
LST 3 to DRX parameters and gap-assisted GERAN
CELLD GERAN measurement configurations to the UE. If this
RXPAR parameter is set to OFF, the eNodeB delivers only
A gap-assisted GERAN measurement configurations to
the UE.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
InterRat GeranCe MOD LOFD-0 CS Meaning: Indicates the maximum number of GERAN
HoCom llNumF INTER 01034 / Fallback cell system information messages that can be
m orEmcR RATHO TDLOF to transmitted during a CSFB emergency redirection
edirect COMM D-00103 GERAN procedure.
LST 4 GUI Value Range: 0~32
INTER Unit: None
RATHO
COMM Actual Value Range: 0~32
Default Value: 0
UtranEx Rac ADD LOFD-0 PS Inter- Meaning: Indicates the routing area code.
ternalCe UTRAN 01019 / RAT GUI Value Range: 0~255
ll EXTER TDLOF Mobility
NALCE D-00101 between Unit: None
LL 9 E- Actual Value Range: 0~255
MOD LOFD-0 UTRAN Default Value: 0
UTRAN 01034 / and
EXTER TDLOF UTRAN
NALCE D-00103 CS
LL 4 Fallback
LST LOFD-0 to
UTRAN 01052 / GERAN
EXTER TDLOF Flash
NALCE D-00105 CS
LL 2 Fallback
TDLOF to
D-00103 UTRAN
3 CS
TDLOF Fallback
D-00104 to
3 UTRAN
TDLOF Service
D-00107 based
2 Inter-
RAT
TDLOF handove
D-00107 r to
8 UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
steering
CellOp CnOper ADD None None Meaning: Indicates the index of the operator.
HoCfg atorId CELLO GUI Value Range: 0~5
PHOCF
G Unit: None
CSFallB UtranLc MOD LOFD-0 CS Meaning: Indicates the LCS capability of the
ackBlin sCap CSFAL 01033 / Fallback UTRAN. If this parameter is set to ON, the UTRAN
dHoCfg LBACK TDLOF to supports LCS. If this parameter is set to OFF, the
BLIND D-00103 UTRAN UTRAN does not support LCS.
HOCFG 3 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
LBACK Actual Value Range: OFF, ON
BLIND Default Value: OFF(Off)
HOCFG
CellOp LocalCe ADD None None Meaning: Indicates the local identity of the cell. It
HoCfg llId CELLO uniquely identifies a cell within an eNodeB.
PHOCF GUI Value Range: 0~255
G
Unit: None
LST
CELLO Actual Value Range: 0~255
PHOCF Default Value: None
G
MOD
CELLO
PHOCF
G
RMV
CELLO
PHOCF
G
CSFallB UtranCs MOD LOFD-0 CS Meaning: Indicates whether the eNodeB selects the
ackBlin fbBlind CSFAL 01033/ Fallback target frequency in a round robin (RR) manner from
dHoCfg RedirRr LBACK TDLOF to frequencies with the same priority in blind
Sw BLIND D-00103 UTRAN redirections for CSFB to UTRAN. If this parameter is
HOCFG 3 Flash set to ON(On), the function of target frequency
LST LOFD-0 CS selection in an RR manner is enabled. If this
CSFAL 01052/ Fallback parameter is set to OFF(Off), this function is disabled.
LBACK TDLOF to GUI Value Range: OFF(OFF), ON(ON)
BLIND D-00105 UTRAN Unit: None
HOCFG 2
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the index of the operator.
ator atorId CNOPE 01036 Sharing GUI Value Range: 0~5
RATOR LOFD-0 with
Commo Unit: None
LST 01037
CNOPE n Actual Value Range: 0~5
LOFD-0 Carrier
RATOR 01086 Default Value: None
MOD RAN
TDLOF Sharing
CNOPE D-00111
RATOR with
2 Dedicate
RMV LOFD-0 d
CNOPE 70206 Carrier
RATOR
RAN
Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g
Hybrid
RAN
Sharing
CSFallB LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
ackHo llId CSFAL identifies a cell within a BS.
LBACK GUI Value Range: 0~255
HO
Unit: None
MOD
CSFAL Actual Value Range: 0~255
LBACK Default Value: None
HO
S1Interf MmeRel ADD LBFD-0 Star Meaning: Indicates the compliance protocol release of
ace ease S1INTE 0300101 Topolog the MME to which the eNodeB is connected through
RFACE / y the S1 interface. The eNodeB sends S1 messages
MOD TDLBF Chain complying with the protocol release specified by this
S1INTE D-00300 Topolog parameter. The value of this parameter must be the
RFACE 101 y same as the MME-complied protocol release. If the
LBFD-0 parameter value is different from the MME-complied
DSP Tree protocol release, the way in which the MME handles
S1INTE 0300102 Topolog
/ these message is subject to the MME implementation.
RFACE y
TDLBF GUI Value Range: Release_R8(Release 8),
D-00300 Release_R9(Release 9), Release_R10(Release 10),
102 Release_R11(Release 11), Release_R12(Release 12)
LBFD-0 Unit: None
0300103 Actual Value Range: Release_R8, Release_R9,
/ Release_R10, Release_R11, Release_R12
TDLBF
D-00300 Default Value: Release_R8(Release 8)
103
CSFallB CnOper LST LOFD-0 CS Meaning: Indicates the index of the operator.
ackBlin atorId CSFAL 01033 / Fallback GUI Value Range: 0~5
dHoCfg LBACK TDLOF to
BLIND D-00103 UTRAN Unit: None
HOCFG 3 CS Actual Value Range: 0~5
MOD LOFD-0 Fallback Default Value: None
CSFAL 01034 / to
LBACK TDLOF GERAN
BLIND D-00103 Flash
HOCFG 4 CS
TDLOF Fallback
D-00105 to
2 UTRAN
TDLOF Flash
D-00105 CS
3 Fallback
TDLOF to
D-00103 GERAN
5 CS
TDLOF Fallback
D-00109 to
0 CDMA2
000
1xRTT
Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
GeranEx Rac ADD LOFD-0 CS Meaning: Indicates the routing area code.
ternalCe GERAN 01034 / Fallback GUI Value Range: 0~255
ll EXTER LOFD-0 to
NALCE 01034 GERAN Unit: None
LL LOFD-0 Flash Actual Value Range: 0~255
MOD 01053 CS Default Value: 0
GERAN LOFD-0 Fallback
EXTER 01020 / to
NALCE TDLOF GERAN
LL D-00102 PS Inter-
LST 0 RAT
GERAN Mobility
EXTER between
NALCE E-
LL UTRAN
and
GERAN
CSFallB GeranLc MOD LOFD-0 CS Meaning: Indicates the LCS capability of the
ackBlin sCap CSFAL 01034 / Fallback GERAN. If this parameter is set to ON, the GERAN
dHoCfg LBACK TDLOF to supports LCS. If this parameter is set to OFF, the
BLIND D-00103 GERAN GERAN does not support LCS.
HOCFG 4 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
LBACK Actual Value Range: OFF, ON
BLIND Default Value: OFF(Off)
HOCFG
CSFallB CsfbHo MOD LOFD-0 CS Fall Meaning: Indicates the RSSI threshold for event B1
ackHo GeranB CSFAL 01034 / Back to that is used in CS fallback to GERAN. A UE sends a
1Thd LBACK TDLOF GERAN measurement report related to event B1 to the eNodeB
HO D-00103 when the RSSI in at least one GERAN cell exceeds
LST 4 this threshold and other triggering conditions are met.
CSFAL For details, see 3GPP TS 36.331.
LBACK GUI Value Range: -110~-48
HO Unit: dBm
Actual Value Range: -110~-48
Default Value: -103
CSFallB CsfbHo MOD LOFD-0 CS Fall Meaning: Indicates the time-to-trigger for event B1
ackHo GeranTi CSFAL 01034 / Back to that is used in CS fallback to GERAN. When CS
meToTri LBACK TDLOF GERAN fallback to GERAN is applicable, this parameter is set
g HO D-00103 for UEs and used in the evaluation of whether to
LST 4 trigger event B1. When detecting that the signal
CSFAL quality in at least one GERAN cell meets the entering
LBACK condition, the UE does not send a measurement report
HO to the eNodeB immediately. Instead, the UE sends a
report only when the signal quality continuously
meets the entering condition during the time-to-
trigger. This parameter helps decrease the number of
occasionally triggered event reports, the average
number of handovers, and the number of wrong
handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Default Value: 40ms
CellDrx LongDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the long DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement.
orMeas RXPAR TDLOF CS GUI Value Range: SF128(128 subframes), SF160(160
A D-08120 Fallback subframes), SF256(256 subframes), SF320(320
LST 3 to subframes), SF512(512 subframes), SF640(640
CELLD GERAN subframes), SF1024(1024 subframes), SF1280(1280
RXPAR subframes), SF2048(2048 subframes), SF2560(2560
A subframes)
Unit: subframe
Actual Value Range: SF128, SF160, SF256, SF320,
SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF160(160 subframes)
CellDrx OnDurT MOD LOFD-0 Ultra- Meaning: Indicates the length of the On Duration
Para imerFor CELLD 81283 / Flash Timer dedicated to GERAN measurement.
Meas RXPAR TDLOF CS GUI Value Range: PSF1(1 PDCCH subframe),
A D-08120 Fallback PSF2(2 PDCCH subframes), PSF3(3 PDCCH
LST 3 to subframes), PSF4(4 PDCCH subframes), PSF5(5
CELLD GERAN PDCCH subframes), PSF6(6 PDCCH subframes),
RXPAR PSF8(8 PDCCH subframes), PSF10(10 PDCCH
A subframes), PSF20(20 PDCCH subframes), PSF30(30
PDCCH subframes), PSF40(40 PDCCH subframes),
PSF50(50 PDCCH subframes), PSF60(60 PDCCH
subframes), PSF80(80 PDCCH subframes),
PSF100(100 PDCCH subframes), PSF200(200
PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200
Default Value: PSF2(2 PDCCH subframes)
CellDrx DrxInact MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX Inactivity
Para TimerFo CELLD 81283 / Flash Timer dedicated to GERAN measurement.
rMeas RXPAR TDLOF CS GUI Value Range: PSF1(1 PDCCH subframe),
A D-08120 Fallback PSF2(2 PDCCH subframes), PSF3(3 PDCCH
LST 3 to subframes), PSF4(4 PDCCH subframes), PSF5(5
CELLD GERAN PDCCH subframes), PSF6(6 PDCCH subframes),
RXPAR PSF8(8 PDCCH subframes), PSF10(10 PDCCH
A subframes), PSF20(20 PDCCH subframes), PSF30(30
PDCCH subframes), PSF40(40 PDCCH subframes),
PSF50(50 PDCCH subframes), PSF60(60 PDCCH
subframes), PSF80(80 PDCCH subframes),
PSF100(100 PDCCH subframes), PSF200(200
PDCCH subframes), PSF300(300 PDCCH
subframes), PSF500(500 PDCCH subframes),
PSF750(750 PDCCH subframes), PSF1280(1280
PDCCH subframes), PSF1920(1920 PDCCH
subframes), PSF2560(2560 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200, PSF300, PSF500,
PSF750, PSF1280, PSF1920, PSF2560
Default Value: PSF2(2 PDCCH subframes)
CellDrx DrxReT MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX
Para xTimerF CELLD 81283 / Flash Retransmission Timer dedicated to GERAN
orMeas RXPAR TDLOF CS measurement.
A D-08120 Fallback GUI Value Range: PSF1(1 PDCCH subframes),
LST 3 to PSF2(2 PDCCH subframes), PSF4(4 PDCCH
CELLD GERAN subframes), PSF6(6 PDCCH subframes), PSF8(8
RXPAR PDCCH subframes), PSF16(16 PDCCH subframes),
A PSF24(24 PDCCH subframes), PSF33(33 PDCCH
subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF4, PSF6, PSF8,
PSF16, PSF24, PSF33
Default Value: PSF4(4 PDCCH subframes)
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates whether to enable the short DRX
Para xSwFor CELLD 81283 / Flash cycle dedicated to GERAN measurement.
Meas RXPAR TDLOF CS GUI Value Range: OFF(Off), ON(On)
A D-08120 Fallback
3 to Unit: None
LST
CELLD GERAN Actual Value Range: OFF, ON
RXPAR Default Value: OFF(Off)
A
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the short DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement.
orMeas RXPAR TDLOF CS GUI Value Range: SF2(2 subframes), SF5(5
A D-08120 Fallback subframes), SF8(8 subframes), SF10(10 subframes),
LST 3 to SF16(16 subframes), SF20(20 subframes), SF32(32
CELLD GERAN subframes), SF40(40 subframes), SF64(64
RXPAR subframes), SF80(80 subframes), SF128(128
A subframes), SF160(160 subframes), SF256(256
subframes), SF320(320 subframes), SF512(512
subframes), SF640(640 subframes)
Unit: subframe
Actual Value Range: SF2, SF5, SF8, SF10, SF16,
SF20, SF32, SF40, SF64, SF80, SF128, SF160,
SF256, SF320, SF512, SF640
Default Value: SF20(20 subframes)
CellDrx ShortCy MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX Short Cycle
Para cleTime CELLD 81283 / Flash Timer dedicated to GERAN measurement.
rForMea RXPAR TDLOF CS GUI Value Range: 1~16
s A D-08120 Fallback
3 to Unit: None
LST
CELLD GERAN Actual Value Range: 1~16
RXPAR Default Value: 1
A
10 Counters
11 Glossary
12 Reference Documents
1. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC); Stage 2"
2. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"
3. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
4. 3GPP TS 36.300, "E-UTRAN Overall description"
5. 3GPP TS 48.018, "General Packet Radio Service (GPRS); Base Station System (BSS) -
Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP) "
6. VoLGA Forum Specifications
7. Emergency Call
8. Inter-RAT Mobility Management in Connected Mode
9. Interoperability Between GSM and LTE
10. Interoperability Between UMTS and LTE
11. LCS
13 Appendix
NOTE
The symbols that appear in signaling procedure figures throughout this document are explained as
follows:
l An arrow denotes the transmission of a message.
l A plain box denotes a mandatory procedure.
l A dashed box denotes an optional procedure.
Mobile-Originated Call
Figure 13-2 shows the procedure for 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. The eNodeB determines whether to perform a 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.
NOTE
For details about how the eNodeB selects a target cell and a CSFB policy, see 3.5 Decision and 3.6
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.
Mobile-Terminated Call
Figure 13-3 shows the procedure for 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.
Mobile-Originated Call
Figure 13-4 shows the procedure for CSFB to UTRAN based on redirection 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. The eNodeB determines whether to perform a blind handover based on the UE
capabilities, parameters settings, and algorithm policies.
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
For details about how the eNodeB selects a target cell and a CSFB policy, see 3.5 Decision and 3.6
Execution.
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.
Mobile-Terminated Call
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 13.1.2 CSFB
Based on PS Handover. The subsequent steps are the same as the steps in the procedure for
CSFB to UTRAN based on redirection for mobile-originated calls.
Mobile-Originated Call
Figure 13-5 shows the procedure for CSFB to UTRAN based on flash redirection for mobile-
originated calls.
Figure 13-5 CSFB to UTRAN based on flash redirection 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. The eNodeB determines whether to perform a blind handover based on the UE
capabilities, parameters settings, and algorithm policies.
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, 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
For details about how the eNodeB selects a target cell and a CSFB policy, see 3.5 Decision and 3.6
Execution. The system information of the target cell is acquired during the RIM procedure.
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.
Mobile-Terminated Call
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 13.1.2 CSFB
Based on PS Handover. The subsequent steps are the same as the steps in the procedure for
CSFB to UTRAN based on flash redirection for mobile-originated calls.
Mobile-Terminated Call
Figure 13-7 shows the procedure of ultra-flash CSFB to UTRAN for mobile-terminated calls.
For details about the standard procedure, see chapter 7 "Mobile Terminating Call" in 3GPP
TS 23.272 V10.9.0 and 3GPP TS 24.008 V11.0.0.
Steps 1 to 4b: The UE initiates voice services (mobile-originated calls and mobile-terminated
calls) on the E-UTRAN. The eNodeB triggers SRVCC to UTRAN. Special treatment has been
applied to the MME and MSC to ensure a proper procedure.
Step 3b: The RNC 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 UTRAN.
Steps 6 to 9: The UE establishes voice services on the UTRAN. Signaling is transmitted at a
speed of 13.6 kbit/s, which accelerates the transfer and reduces delays.
As shown in the preceding figures, Ultra-Flash CSFB to UTRAN excludes the following
procedures:
l Authentication procedure
The UE has been authenticated in the LTE system before CSFB to UTRAN.
l Ciphering procedure
The UE has performed ciphering as instructed during SRVCC. Therefore, the ciphering
procedure is not required after the UE is transferred to the UTRAN.
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.
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.
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.
Mobile-Originated Call
Figure 13-9 shows the procedure for CSFB to GERAN based on PS handover for mobile-
originated calls.
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
For details about how the eNodeB selects a target cell and a CSFB policy, see 4.5 Decision and 4.6
Execution.
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.
Mobile-Terminated Call
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 13.1.2 CSFB
Based on PS Handover. The subsequent steps are the same as the steps in the procedure for
CSFB to GERAN based on PS handover for mobile-originated calls.
Mobile-Originated Call
Figure 13-10 shows the procedure for CSFB to GERAN based on CCO/NACC 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. The eNodeB determines whether to perform a blind handover based on the UE
capabilities, parameters settings, and algorithm policies.
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
For details about how the eNodeB selects a target cell and a CSFB policy, see 4.5 Decision and 4.6
Execution.
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.
Mobile-Terminated Call
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 13.1.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.
Mobile-Originated Call
Figure 13-11 shows the procedure for CSFB to GERAN based on redirection for mobile-
originated calls.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a
redirection. The message contains information about a target GERAN frequency. Then,
the eNodeB initiates an S1 UE context release procedure.
NOTE
For details about how the eNodeB selects a target cell and a CSFB policy, see 4.5 Decision and 4.6
Execution.
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in
the target cell.
6. If the GERAN or UE does not support DTM, the ongoing PS services of the UE are
suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
Mobile-Terminated Call
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 13.1.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.
Mobile-Originated Call
Figure 13-12 shows the procedure for CSFB to GERAN based on flash redirection for
mobile-originated calls.
Figure 13-12 CSFB to GERAN based on flash redirection 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. The eNodeB determines whether to perform a blind redirection based on the UE
capabilities, parameters settings, and algorithm policies.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to 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
For details about how the eNodeB selects a target cell and a CSFB policy, see 4.5 Decision and 4.6
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.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
Mobile-Terminated Call
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 13.1.2 CSFB
Based on PS Handover. The subsequent steps are the same as the steps in the procedure for
CSFB to GERAN based on flash redirection for mobile-originated 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. Special treatment has been
applied to the MME and MSC to ensure a proper procedure.
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:
l Authentication procedure
The UE has been authenticated in the LTE system before CSFB to GERAN.
l Ciphering procedure
The UE has performed ciphering as instructed during SRVCC. Therefore, the ciphering
procedure is not required after the UE is transferred to the GERAN.
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.