Professional Documents
Culture Documents
Issue 03
Date 2017-05-31
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......................................................................................................................................... 5
2.1 Introduction.................................................................................................................................................................... 6
2.2 Benefits........................................................................................................................................................................... 6
2.3 Application Scenarios.....................................................................................................................................................6
2.4 CSFB Mechanisms......................................................................................................................................................... 8
2.4.1 CSFB to UTRAN.........................................................................................................................................................9
2.4.2 CSFB to GERAN.......................................................................................................................................................10
3 CSFB to UTRAN.......................................................................................................................... 13
3.1 Overview...................................................................................................................................................................... 14
3.2 Feature Description.......................................................................................................................................................15
3.2.1 LOFD-001033 CS Fallback to UTRAN.................................................................................................................... 15
3.2.2 LOFD-001052 Flash CS Fallback to UTRAN.......................................................................................................... 15
3.2.3 LOFD-070202 Ultra-Flash CSFB to UTRAN...........................................................................................................16
3.2.4 LOFD-001068 CS Fallback with LAI to UTRAN.................................................................................................... 17
3.2.5 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering............................................................................................ 18
3.2.6 LOFD-001088 CS Fallback Steering to UTRAN......................................................................................................20
3.2.7 Load-based CSFB to UTRAN................................................................................................................................... 22
3.3 Triggering..................................................................................................................................................................... 23
3.4 Target Cell/Frequency Selection...................................................................................................................................24
3.5 Decision........................................................................................................................................................................ 30
3.5.1 Basic Decision Method..............................................................................................................................................30
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 LOFD-001034 CS Fallback to GERAN.................................................................................................................... 44
4.2.2 LOFD-001053 Flash CS Fallback to GERAN.......................................................................................................... 45
4.2.3 LOFD-001069 CS Fallback with LAI to GERAN.................................................................................................... 45
4.2.4 LOFD-001089 CS Fallback Steering to GERAN......................................................................................................46
4.2.5 LOFD-081283 Ultra-Flash CSFB to GERAN...........................................................................................................46
4.3 Triggering..................................................................................................................................................................... 47
4.4 Target Cell/Frequency Selection...................................................................................................................................48
4.5 Decision........................................................................................................................................................................ 49
4.6 Execution...................................................................................................................................................................... 49
4.7 RIM Procedure Between E-UTRAN and GERAN...................................................................................................... 51
7 Network Impact........................................................................................................................... 60
7.1 LOFD-001033 CS Fallback to UTRAN....................................................................................................................... 60
7.2 LOFD-001052 Flash CS Fallback to UTRAN............................................................................................................. 61
7.3 LOFD-070202 Ultra-Flash CSFB to UTRAN..............................................................................................................61
7.4 LOFD-001068 CS Fallback with LAI to UTRAN....................................................................................................... 62
7.5 LOFD-001088 CS Fallback Steering to UTRAN.........................................................................................................62
7.6 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering............................................................................................... 62
7.7 LOFD-001034 CS Fallback to GERAN....................................................................................................................... 63
7.8 LOFD-001053 Flash CS Fallback to GERAN............................................................................................................. 63
7.9 LOFD-081283 Ultra-Flash CSFB to GERAN..............................................................................................................64
7.10 LOFD-001069 CS Fallback with LAI to GERAN..................................................................................................... 64
7.11 LOFD-001089 CS Fallback Steering to GERAN.......................................................................................................64
8 Engineering Guidelines............................................................................................................. 66
8.1 LOFD-001033 CS Fallback to UTRAN....................................................................................................................... 66
8.1.1 When to Use.............................................................................................................................................................. 66
8.1.2 Required Information................................................................................................................................................ 66
8.1.3 Requirements............................................................................................................................................................. 67
8.1.4 Precautions.................................................................................................................................................................68
8.1.5 Data Preparation and Feature Activation...................................................................................................................68
8.1.5.1 Data Preparation..................................................................................................................................................... 68
8.1.5.2 Using the CME....................................................................................................................................................... 75
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............................................................................................................................................. 88
8.2 RIM Procedure from E-UTRAN to UTRAN............................................................................................................... 91
8.2.1 When to Use.............................................................................................................................................................. 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....................................................................................................................................................... 94
8.2.5.3 Using MML Commands......................................................................................................................................... 94
8.2.6 Activation Observation..............................................................................................................................................95
8.2.7 Deactivation...............................................................................................................................................................97
8.2.7.1 Using the CME....................................................................................................................................................... 97
8.2.7.2 Using MML Commands......................................................................................................................................... 97
8.2.8 Performance Monitoring............................................................................................................................................97
8.2.9 Parameter Optimization............................................................................................................................................. 97
8.3 LOFD-001052 Flash CS Fallback to UTRAN............................................................................................................. 98
8.3.1 When to Use.............................................................................................................................................................. 98
8.3.2 Required Information................................................................................................................................................ 98
8.3.3 Requirements............................................................................................................................................................. 98
8.3.4 Precautions.................................................................................................................................................................99
8.3.5 Data Preparation and Feature Activation...................................................................................................................99
8.3.5.1 Data Preparation..................................................................................................................................................... 99
8.3.5.2 Using the CME..................................................................................................................................................... 100
8.3.5.3 Using MML Commands....................................................................................................................................... 100
8.3.6 Activation Observation............................................................................................................................................101
8.3.7 Deactivation.............................................................................................................................................................102
8.6.7 Deactivation.............................................................................................................................................................122
8.6.7.1 Using the CME..................................................................................................................................................... 122
8.6.7.2 Using MML Commands....................................................................................................................................... 122
8.6.8 Performance Monitoring..........................................................................................................................................123
8.6.9 Parameter Optimization........................................................................................................................................... 123
8.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering............................................................................................. 123
8.7.1 When to Use............................................................................................................................................................ 123
8.7.2 Required Information.............................................................................................................................................. 123
8.7.3 Requirements........................................................................................................................................................... 124
8.7.4 Precautions...............................................................................................................................................................124
8.7.5 Data Preparation and Feature Activation.................................................................................................................124
8.7.5.1 Data Preparation................................................................................................................................................... 124
8.7.5.2 Using the CME..................................................................................................................................................... 125
8.7.5.3 Using MML Commands....................................................................................................................................... 126
8.7.6 Activation Observation............................................................................................................................................127
8.7.7 Deactivation.............................................................................................................................................................127
8.7.7.1 Using the CME..................................................................................................................................................... 127
8.7.7.2 Using MML Commands....................................................................................................................................... 127
8.7.8 Performance Monitoring..........................................................................................................................................128
8.7.9 Parameter Optimization........................................................................................................................................... 128
8.8 LOFD-001034 CS Fallback to GERAN..................................................................................................................... 128
8.8.1 When to Use............................................................................................................................................................ 128
8.8.2 Required Information.............................................................................................................................................. 128
8.8.3 Requirements........................................................................................................................................................... 129
8.8.4 Precautions...............................................................................................................................................................130
8.8.5 Data Preparation and Feature Activation.................................................................................................................130
8.8.5.1 Data Preparation................................................................................................................................................... 130
8.8.5.2 Using the CME..................................................................................................................................................... 135
8.8.5.3 Using MML Commands....................................................................................................................................... 135
8.8.6 Activation Observation............................................................................................................................................139
8.8.7 Deactivation.............................................................................................................................................................142
8.8.7.1 Using MML Commands....................................................................................................................................... 142
8.8.8 Performance Monitoring..........................................................................................................................................142
8.8.9 Parameter Optimization........................................................................................................................................... 144
8.9 RIM Procedure from E-UTRAN to GERAN............................................................................................................. 145
8.9.1 When to Use............................................................................................................................................................ 145
8.9.2 Required Information.............................................................................................................................................. 146
8.9.3 Requirements........................................................................................................................................................... 146
8.9.4 Precautions...............................................................................................................................................................146
8.9.5 Data Preparation and Feature Activation.................................................................................................................146
8.9.5.1 Data Preparation................................................................................................................................................... 146
8.9.5.2 Using the CME..................................................................................................................................................... 149
9 Parameters................................................................................................................................... 180
10 Counters.................................................................................................................................... 272
11 Glossary..................................................................................................................................... 282
12 Reference Documents............................................................................................................. 283
13 Appendix................................................................................................................................... 284
13.1 CSFB to UTRAN......................................................................................................................................................284
13.1.1 Combined EPS/IMSI Attach Procedure................................................................................................................ 284
13.1.2 CSFB Based on PS Handover............................................................................................................................... 285
13.1.3 CSFB Based on Redirection.................................................................................................................................. 287
13.1.4 Flash CSFB............................................................................................................................................................289
13.1.5 Ultra-Flash CSFB to UTRAN............................................................................................................................... 290
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 LOFD-001033 CS Fallback to UTRAN
l LOFD-001052 Flash CS Fallback to UTRAN
l LOFD-070202 Ultra-Flash CSFB to UTRAN
l LOFD-001068 CS Fallback with LAI to UTRAN
l LOFD-001088 CS Fallback Steering to UTRAN
l LOFD-001078 E-UTRAN to UTRAN CS/PS Steering
l LOFD-001034 CS Fallback to GERAN
l LOFD-001053 Flash CS Fallback to GERAN
l LOFD-001069 CS Fallback with LAI to GERAN
l LOFD-001089 CS Fallback Steering to GERAN
l LOFD-081283 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 parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
eRAN12.1 03 (2017-05-31)
This issue includes the following changes.
eRAN12.1 02 (2017-04-26)
This issue includes the following changes.
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
NOTE
2 Overview
In an early phase of evolved packet system (EPS) construction, operators who own a mature
UTRAN or GERAN can protect their investments in legacy CS networks and reduce their
investments in the EPS by using legacy CS networks to provide CS services.
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 a 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.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
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 cell, the MME sends the eNodeB an S1-
AP message that contains a 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 CSFB to UTRAN.
NOTE
This feature is also controlled by the UtranFlashCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
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 Interoperability Between UMTS and LTE 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.
When operators' network capabilities of the RIM procedure differ in the RAN sharing
scenario, you can enable LOFD-070216 Separate Mobility Policies to UTRAN for Multi
PLMN to specify whether an operator supports the RIM procedure, thereby specifying
whether LOFD-001052 Flash CS Fallback to UTRAN is enabled for the operator. For details
about the RIM procedure, see 3.7 RIM Procedure Between E-UTRAN and UTRAN.
If UEs experience incompatibility issues and flash CSFB cannot be performed, causing
service drops, LBFD-081103 Terminal Awareness Differentiation can be enabled to add the
UEs to the blacklist of flash CSFB. In this case, CSFB is performed for the UEs, thereby
decreasing the service drop rate. For details, see descriptions related to blacklist control in
Terminal Awareness Differentiation Feature Parameter Description.
Other procedures are the same as those for CS Fallback to UTRAN. For details, see 3.2.1
LOFD-001033 CS Fallback to UTRAN.
When a UE initiates a CS service setup request in an LTE network that does not support
VoLTE, this feature enables the eNodeB to hand over the UE to the UTRAN through the
SRVCC procedure. The procedure has CS resources on the UTRAN prepared in advance and
omits certain protocol-defined signaling procedures during access to the UTRAN. For the
detailed signaling procedure, see 13.1.5 Ultra-Flash CSFB to UTRAN.
The measurement procedure and blind handling procedure for this feature are the same as
those described in 3.2.1 LOFD-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.
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
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 deselected, 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
This feature can be used when service steering is required in a UTRAN with multiple
UTRAN frequencies. By setting CS service priorities for UTRAN frequencies, the operator
can achieve CSFB from E-UTRAN only to the UTRAN frequency that has the highest CS
service priority.
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 selected for inter-RAT measurement
on the UTRAN.
This function is controlled by the UtranFreqLayerMeasSwitch option of the cell-level
parameter CellAlgoSwitch.FreqLayerSwitch.
NOTE
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.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
l CS-only UE
If the MME uses the INITIAL CONTEXT SETUP REQUEST message to send the
CSFB indicator to the eNodeB, the eNodeB determines that the UE is in idle mode at the
time when the UE initiates the CS service. This UE is called a CS-only UE.
l CS+PS UE
If the MME uses the UE CONTEXT MODIFICATION REQUEST message to send the
CSFB indicator to the eNodeB, the eNodeB determines that the UE is performing PS
services at the time when the UE initiates the CS service. This UE is called a CS+PS UE.
NOTE
For a UE initiating an emergency call, the eNodeB preferentially selects RATs that support LCS
and then selects an RAT from them based on the configured RAT priorities.
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
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 LOFD-001078
E-UTRAN to UTRAN CS/PS Steering.
The eNodeB selects a handover policy for CSFB of a CS-only UE 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 LOFD-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 handling procedures are the same
as those in the CS Fallback to UTRAN feature. For details, see 3.2.1 LOFD-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.
If all cells in measurement reports received by the eNodeB are congested or overloaded and
the eNodeB selects these cells as handover target cells, handover preparation may fail due to
high load status. The BASED_ON_LOAD option of the
CellHoParaCfg.L2UCsfbMRProMode parameter can be selected to avoid this. In this case,
the eNodeB does not select congested or overloaded cells for handover or operating
frequencies of these types of cells for redirection. Instead, the eNodeB waits for medium load
or normal cells to select them as target cells until the CSFB protection timer expires,
triggering blind redirection.
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.
3.3 Triggering
CSFB triggering is classified into measurement triggering and blind handling triggering.
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 Feature Parameter Description.
Compared with coverage-based inter-RAT handover, CSFB to UTRAN uses the same set of
parameters for measurement configuration, except the threshold and time-to-trigger for event
B1 described in Table 3-3.
NOTE
When an E-UTRAN coverage area is larger than a UTRAN coverage area and E-UTRAN and
UTRAN base stations are co-sited, this function estimates the signal strength of the
neighboring UTRAN cells based on the signal strength of the serving E-UTRAN cell. The
procedure is shown in Figure 3-2.
Figure 3-3 Procedure for selecting the target cell for a measurement
The procedure shown in Figure 3-3 involves the following data configuration and
activities:
n Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
n The service priority is specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details about this parameter,
see 3.2.5 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering and 3.2.6
LOFD-001088 CS Fallback Steering to UTRAN.
n The priorities of neighboring UTRAN frequencies for connected-mode UEs
are specified by the UtranNFreq.ConnFreqPriority parameter.
n The measurement priority for UTRAN neighbor relationships 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.
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.
If this option is deselected, the neighboring cell measurement priority is
specified by the UtranNCell.CellMeasPriority parameter, which must be
configured manually.
n 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 there are several target
The procedure shown in Figure 3-4 involves the following data configuration and
activities:
n The service priority is specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details about this parameter,
The procedure shown in Figure 3-5 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 service priority is specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details about this parameter,
see 3.2.5 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering and 3.2.6
LOFD-001088 CS Fallback Steering to UTRAN.
3.5 Decision
In the decision phase, the eNodeB evaluates the candidate cell list. Based on the evaluation
result, the eNodeB determines whether a CSFB procedure needs to be initiated and, if so, to
which cell the UE is to be transferred. There are two decision methods.
Measurement Scenario
In the measurement scenario, two handling methods are provided for handover decision.
Basic handling based on a single measurement report takes effect by default. No additional
configuration is required. Comprehensive handling based on multiple measurement reports
takes effect depending on parameter settings.
l Basic handling based on a single measurement report
The eNodeB handles the reported MRs in a first-in first-out manner. The eNodeB
generates a candidate cell list based on the signaling quality in the current measurement
report in descending order.
When the CSFB policy is handover, the eNodeB sends a handover request to candidate
cells in sequence. If the handover request fails, the eNodeB sends the handover request
to the next candidate cell. If the handover request fails in all cells in the candidate cell
list, the eNodeB waits for the UE to send the next measurement report.
When the CSFB policy is redirection, the eNodeB selects the operating frequency of the
first cell in the candidate cell list for redirection.
l Comprehensive handling based on multiple measurement reports
In this handling method, the eNodeB can wait for multiple MRs. It selects candidate
cells, generates a candidate cell list, and performs handover evaluation. The evaluation is
controlled by the CellHoParaCfg.L2UCsfbMRProMode parameter.
This parameter can be set to HANDOVER_IMMEDIATELY,
BASED_ON_SIGNAL_STRENGTH, or BASED_ON_FREQ_PRIORITY. Figure
3-6 shows the candidate cell list generation and decision procedure when parameter
configurations are different. When this parameter is set to
HANDOVER_IMMEDIATELY, the comprehensive handling procedure is equal to the
basic handling procedure.
NOTE
The signal-strength-based processing mode is used when the eNodeB delivers measurement
configurations for multiple frequencies and must select the cell with the best signal strength for
handover or the frequency with the best signal strength for redirection from those included in
measurement reports. If the eNodeB delivers measurement configurations for only one frequency,
the signal-strength-based processing mode is equivalent to the immediate processing mode.
Measurement Scenario
1. The eNodeB adds other neighboring cells on the target frequency for redirection but not
in measurement reports in a random sequence to the candidate cell list generated based
on measurement reports.
2. Assume that the InterRatHoComm.CellInfoMaxUtranCellNum parameter is set to N.
If the number of target cells in the filtering result is greater than or equal to N, the
eNodeB selects the first N cells.
If the number of target cells in the filtering result is smaller than N, the eNodeB
selects all these cells.
3. The eNodeB filters out cells whose system information has not been obtained.
If the number of target cells in the filtering result is smaller than N, the eNodeB
selects all these cells.
3. The eNodeB filters out cells whose system information has not been obtained.
4. The eNodeB filters cells based on SPID-based mobility management in connected mode.
For details, see LOFD-00105401 Camp & Handover Based on SPID in Flexible User
Steering Feature Parameter Description.
3.6 Execution
In the execution phase, the eNodeB controls the handover of the UE from the source cell to
the target cell.
This function is also controlled by the UtranPsHoSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoModeSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does
not take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-
level parameter takes effect.
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 PS handover for CSFB with blind handling applied, 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.
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 avoid function conflicts.
System Information
The eNodeB obtains system information about UTRAN cells 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. The procedure does not depend on any switch.
During the procedure, the eNodeB sends a RIM request to the RNC and then includes the
obtained system information in a redirection message to the UE. If the eNodeB fails to
obtain system information from the RNC, the eNodeB no longer sends the RIM request.
The system information obtained in this mode is not stored on the eNodeB. Therefore,
operators cannot run the DSP UTRANRIMINFO command to query the status of the
RIM procedure towards neighboring cells.
l Multiple Report
The eNodeB initiates a RIM procedure in Multiple Report mode to obtain system
information if the UTRAN_RIM_SWITCH option of the
ENodeBAlgoSwitch.RimSwitch parameter is selected and the MME complies 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
including system information and load information on the target changes.
The eNodeB sends a RIM request to each external UTRAN cell in sequence every 4
seconds no matter whether the eNodeB has CSFB services.
To increase the success rate of obtaining information of an external UTRAN cell, the
eNodeB starts a 4s timer when it sends a RIM request.
If the eNodeB receives a response before the timer expires, the eNodeB saves the
obtained information.
If the eNodeB receives a response after the timer expires, the eNodeB considers that
an exception has occurred and discards the information.
If the eNodeB does not receive a response to the RIM request after the timer
expires, the eNodeB triggers the RIM retry mechanism. 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 2N hours. For example, the first retry occurs
2 hours after the first system information 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 information or a RIM request may fail 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:30 a.m. to 04:30 a.m. and deletes all the
obtained information. Then, the eNodeB requests the information of external UTRAN
cells through the RIM procedure again.
If an external UTRAN cell is faulty or deactivated, the RNC sends the eNodeB a RIM
END message, instructing the eNodeB to stop the RIM procedure. The eNodeB then
deletes the obtained information. To re-obtain information in time, the eNodeB does not
need to wait for the RIM procedure at the preceding specified time point. Instead, the
eNodeB sends a RIM request 15 minutes after receiving the RIM END message. If the
eNodeB does not receive a response, the eNodeB triggers the RIM retry mechanism. If
the eNodeB still does not receive a response after 10 retries, the RIM request fails.
Load Information
When the GlobalProcSwitch.UtranLoadTransChan parameter is set to BASED_ON_RIM,
the eNodeB obtains UTRAN cell load information through the RIM procedure in Multiple
Report mode for target cell selection. Its principle is identical to that for obtaining system
information in Multiple Report mode. For details about how to select target cells, see 3.2.7
Load-based CSFB to UTRAN.
The MME and the SGSN transfer but do not interpret information. For details, see section 8c
"Signalling procedures between RIM SAPs" in 3GPP TS 48.018 V10.0.0.
In Figure 3-10:
l The UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter specifies whether UTRAN operators
can use different mobility policies.
l The UtranNetworkCapCfg.Mcc, UtranNetworkCapCfg.Mnc, and
UtranNetworkCapCfg.RncId parameters, and the SiByRimCapCfg option of the
UtranNetworkCapCfg.NetworkCapCfg parameter specify the operator-specific
capability of obtaining system information about UTRAN through the RIM procedure. If
the capability is not configured for an operator or RNC, it is supported by default.
Figure 3-10 Information exchange mode selection for the RIM procedure
The RIM procedure through the eCoordinator requires that the 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
respond to RIM messages from the core network.
The information exchange mode for the eCoordinator-based RIM procedure is controlled by
the UTRAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter.
l If this switch is on, the eNodeB uses the RIM procedure in Multiple Report mode to
obtain the system information 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 LOFD-001034 CS Fallback to GERAN
l LOFD-001053 Flash CS Fallback to GERAN
l LOFD-001069 CS Fallback with LAI to GERAN
l LOFD-001089 CS Fallback Steering to GERAN
l LOFD-081283 Ultra-Flash CSFB to GERAN
Figure 4-1 shows the CSFB to GERAN procedure.
NOTE
Random frequency and cell selection described in this document denotes the random selection based on
probability distribution.
NOTE
This feature is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
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 following
parameters. For details about the principles, see 3.2.1 LOFD-001033 CS Fallback to
UTRAN.
Measurement
The frequency priority used during measurement object selection is specified by the
GeranNfreqGroup.ConnFreqPriority parameter. A larger value indicates a higher priority.
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.
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. If both eNodeB- and cell-level parameters are set, the cell-level
parameter settings prevail.
The target selection procedure varies depending on whether neighboring GERAN cells have
been configured.
l If neighboring GERAN cells have been 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 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.
NOTE
This feature is also controlled by the GeranFlashCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
NOTE
This feature is also controlled by the GeranCsfbSteeringSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
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, see 3.2.6 LOFD-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.
When a UE initiates a CS service setup request in an LTE network that does not support
VoLTE, this feature enables the eNodeB to hand over the UE to the GERAN through the
SRVCC procedure. The procedure has CS resources on the GERAN prepared in advance and
omits certain protocol-defined signaling procedures during access to the GERAN. For the
detailed signaling procedure, see 13.2.6 Ultra-Flash CSFB to GERAN.
The measurement procedure and blind handling procedure for this feature are the same as
those described in 3.2.1 LOFD-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.
4.3 Triggering
The procedure for triggering CSFB to GERAN is similar to that for triggering CSFB to
UTRAN. For details, see 3.3 Triggering. Table 4-1 describes the parameters related to event
B1 for CSFB to GERAN, which are different from those for CSFB to UTRAN.
If neighboring cells or frequencies have the same priority, the eNodeB randomly
selects one.
NOTE
Due to uncertainty of random selection, you are not advised to set the priorities of
neighboring cells or frequencies to the same and configure one frequency in GERAN
neighboring frequency groups of different priorities to ensure the blind handover success.
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.
CSFB from E-UTRAN to GERAN can be based on PS handover, CCO/NACC, redirection, or
fast redirection, as shown in Figure 4-2. This policy selection procedure is based on the
assumption that neighboring frequencies and cells have been configured appropriately.
During a PS handover for CSFB with blind handling applied, 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.
l If flash CSFB is enabled, you must set the number of GERAN cells carried during
emergency redirection, which is specified by the
InterRatHoComm.GeranCellNumForEmcRedirect parameter.
l Blind handover is controlled by the BlindHoSwitch option of the eNodeB-level
parameter ENodeBAlgoSwitch.HoModeSwitch and the BlindHoSwitch option of the
cell-level parameter CellHoParaCfg.HoModeSwitch. The blind handover function takes
effect only when both options are selected.
l The CSFB policies are controlled by the options of the
ENodeBAlgoSwitch.HoModeSwitch parameter:
The PS handover capability is specified by GeranPsHoSwitch.
The CCO capability is specified by GeranCcoSwitch.
The NACC capability is specified by GeranNaccSwitch.
The redirection capability is specified by GeranRedirectSwitch.
When CSFB to GERAN is based on CCO/NACC, the eNodeB obtains system
information of external cells through the RIM procedure. For details about the RIM
procedure, see 4.7 RIM Procedure Between E-UTRAN and GERAN.
l The CSFB policy is determined by different parameters, depending on whether
LOFD-001089 CS Fallback Steering to GERAN is enabled.
If this feature is enabled:
The CSFB policy for UEs in idle mode is specified by the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.
The CSFB policy for UEs in connected mode is specified by the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.
If this feature is disabled, the CSFB policy is specified by the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether UEs are in
idle or connected mode.
If a target cell experiences admission failure during a handover from E-UTRAN to
GERAN, the target cell enters the penalty and retry procedure. The penalty and retry
procedure from E-UTRAN to GERAN is the same as that from E-UTRAN to UTRAN.
For details, see 3.6.4 Retry and Penalty.
exchange modes in the same way. The operator-specific capability of obtaining SI of the
GERAN through the RIM procedure affects the CN-based RIM procedure other than the
eCoordinator-based RIM procedure.
In Figure 4-3:
l The GeranSepOpMobilitySwitch option of the CellAlgoSwitch.HoAllowedSwitch
parameter specifies whether GERAN operators can use different mobility policies.
l The GeranNetworkCapCfg.Mcc, GeranNetworkCapCfg.Mnc, and
GeranNetworkCapCfg.Lac parameters, and the SiByRimCapCfg option of the
GeranNetworkCapCfg.NetworkCapCfg parameter specify the operator-specific
capability of obtaining system information about GERAN through the RIM procedure. If
the capability is not configured for an operator or GERAN neighboring cell, it is
supported by default.
Figure 4-3 Information exchange mode selection for the RIM procedure
When the UE in connected mode initiates the CSFB procedure during S1/X2 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.
Extra signaling messages are required only during eNodeB deployment. Afterward, signaling
overhead is negligible because of infrequent system information updates.
Network Performance
This feature enables UEs to obtain information about the target UTRAN cell for redirection
before RRC connections to the LTE network are released, reducing the delay of CSFB to
UTRAN by approximately 0.2s to 0.5s. This gain varies depending on the radio network
environment and the processing capability of UEs.
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 about
0.5s to 1.5s, 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.
This feature enables UEs to obtain information about the target GERAN cell for redirection
before RRC connections to the LTE network are released, reducing the delay of CSFB to
GERAN by approximately 0.2s to 0.5s. This gain varies depending on the radio network
environment and the processing capability of UEs.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to GERAN by about
0.5s to 1.5s, 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 serve the same
area, or the UTRAN cell provides better coverage than the E-UTRAN cell, use CSFB based
on blind handling 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 CellHoPa Engineeri Set this parameter based on the network plan.
Mode raCfg.Ho ng Design To activate PS handovers, select the
switch ModeSwit UtranPsHoSwitch(UtranPsHoSwitch) option. If
ch this option is deselected, redirection will be used
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 CellHoPa Engineeri To activate blind handovers for a cell served by the
Mode raCfg.Ho ng Design eNodeB, select the
switch ModeSwit BlindHoSwitch(BlindHoSwitch) option of this
ch parameter. If this option is deselected, blind
handovers will not take effect in this cell.
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 CellAlgoS Radio When UTRAN and E-UTRAN cells are co-sited
r witch.HoA Planning with the same coverage, you can turn on
Allowed llowedSwit (Negotiati CsfbAdaptiveBlindHoS-
Switch ch on with witch(CsfbAdaptiveBlindHoSwitch). The eNodeB
the peer) decides whether to use measurement-based or blind
handovers to UTRAN based on A1 reports from
UEs.
CSFB CSFallBac Default/ This parameter specifies the RSRP threshold of the
Adaptive kHo.Blind Recomme serving cell above which a CSFB-triggered adaptive
Blind Ho HoA1Thd nded blind handover is triggered. If the RSRP value
A1 RSRP Rsrp value measured by a UE exceeds this threshold, the UE
Trigger submits an 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 CSFallBac Engineeri Set this parameter based on the network plan. This
Operator kBlindHo ng Design parameter identifies the operator whose RAT blind-
ID Cfg.CnOp handover priorities are to be set.
eratorId
Highest CSFallBac Default/ Set this parameter based on the network plan. This
priority kBlindHo Recomme parameter is set to UTRAN by default and specifies
InterRat Cfg.InterR nded the highest-priority RAT to be considered in blind
atHighestP value handovers for CSFB. For CSFB to UTRAN, set this
ri parameter to UTRAN.
Second CSFallBac Default/ Set this parameter based on the network plan. This
priority kBlindHo Recomme parameter is set to GERAN by default and specifies
InterRat Cfg.InterR nded the second-highest-priority RAT to be considered in
atSecondP value blind handovers for CSFB. Ensure that the second-
ri highest-priority RAT is different from the highest-
priority RAT and lowest-priority RAT.
Lowest CSFallBac Default/ Set this parameter based on the network plan. This
priority kBlindHo Recomme parameter is set to CDMA2000 by default and
InterRat Cfg.InterR nded specifies the lowest-priority RAT to be considered
atLowestPr value in blind handovers for CSFB. Ensure that the
i lowest-priority RAT is different from the highest-
priority RAT and second-highest-priority RAT.
UTRAN CSFallBac Default/ Set this parameter based on the network plan. This
LCS kBlindHo Recomme parameter specifies the LCS capability of the
capabilit Cfg.Utran nded UTRAN.
y LcsCap value
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.
CN CellOpHo Engineeri Set this parameter based on the network plan. This
Operator Cfg.CnOpe ng parameter identifies the operator whose RAT blind-
ID ratorId Design handover priorities are to be set.
Local CellOpHo Radio Set this parameter based on the network plan. This
cell ID Cfg.Local Planning parameter identifies the cell whose RAT blind-
CellId (Internal handover priorities are to be set.
planning)
Highest CellOpHo Default/ Set this parameter based on the network plan. This
Priority Cfg.InterR Recomme parameter is set to UTRAN by default and specifies
InterRAT atHighestP nded the highest-priority RAT to be considered in blind
ri value handovers for CSFB. For CSFB to UTRAN, set this
parameter to UTRAN.
Second CellOpHo Default/ Set this parameter based on the network plan. This
Priority Cfg.InterR Recomme parameter is set to GERAN by default and specifies
InterRAT atSecondP nded the second-highest-priority RAT to be considered in
ri value blind handovers for CSFB. Ensure that the second-
highest-priority RAT is different from the highest-
priority RAT and lowest-priority RAT.
Lowest CellOpHo Default/ Set this parameter based on the network plan. This
Priority Cfg.InterR Recomme parameter is set to CDMA2000 by default and
InterRAT atLowestPr nded specifies the lowest-priority RAT to be considered
i value in blind handovers for CSFB. Ensure that the
lowest-priority RAT is different from the highest-
priority RAT and second-highest-priority RAT.
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 CellHoParaCfg MO to set
load-based CSFB to UTRAN.
LTE To CellHoPar Radio When load-based CSFB is enabled and the value of
UTRAN aCfg.L2UC Planning the L.IRATHO.E2W.HighLoad.CSFB.PrepAttOut
CSFB sfbMRPro (Negotiat counter is great, the
Measure Mode ion with BASED_ON_LOAD(BASED_ON_LOAD) option
ment the peer) of this parameter can be selected to increase the
Processin handover preparation success rate. However, the
g Mode CSFB latency also increases.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg
MO to specify the CSFB policy.
CSFB CSFallBac Default/ Set this parameter based on the network plan. The
handover kPolicyCfg Recomme default values are REDIRECTION, CCO_HO,
policy .CsfbHoPol nded and PS_HO. You are advised to set this parameter
Configur icyCfg value based on the UE capabilities and network
ation capabilities.
NOTE
If none of the three options is selected and measurement-
based mobility is enabled, the eNodeB does not perform
CSFB for a UE until the CSFB protection timer expires.
Then the eNodeB performs blind redirection for CSFB. If
blind handling is enabled, the eNodeB directly performs
blind redirection for CSFB.
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.
This function is also controlled by the UtranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
----End
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.
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.
Step 1 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 2 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter deselected and the
REDIRECTION option of the same parameter selected.
Step 3 (Optional) If a neighboring UTRAN cell is configured, run the MOD UTRANNCELL
command with the Blind handover priority parameter set to the highest priority (for
example, 32).
Step 4 (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 (for example, 8).
----End
l Basic scenario 2: CSFB to UTRAN using blind 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 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 eNodeB-level parameter Handover
Mode switch 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 PS_HO option of the
CSFB handover policy Configuration parameter selected.
Step 4 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.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
Step 5 Run the MOD UTRANNCELL command with the Blind handover priority parameter set
to 32.
----End
l Basic scenario 3: CSFB to UTRAN using measurement-based redirection
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 CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter deselected and the
REDIRECTION option of the same parameter selected.
Step 4 Run the MOD CSFALLBACKHO command with the CSFB Protection Timer parameter
specified.
----End
l 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 CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
Step 4 Run the MOD CSFALLBACKHO command with the CSFB Protection Timer parameter
specified.
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.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
The eNodeB-level parameter will no longer be used in later versions. Therefore, you are advised to use
the cell-level parameter.
----End
Step 2 Run the MOD GLOBALPROCSWITCH command with the Choose UMTS Cell Load
Info Trans Channel parameter set to BASED_ON_RIM.
Step 3 (Optional) Run the MOD CELLHOPARACFG command with the LTE To UTRAN CSFB
Measurement Processing Mode parameter set to
BASED_ON_LOAD(BASED_ON_LOAD).
----End
----End
l Enhanced scenario 3: Policy setting for handling the conflicts between handover and
CSFB procedures
l Run the following command after the commands for a basic scenario have been
executed:
Step 1 Run the MOD GLOBALPROCSWITCH command with the CsfbFlowFirstSwitch option
of the Handover Process Control Switch parameter selected.
----End
l Enhanced scenario 4: If you need to set the highest-priority RAT for CSFB to UTRAN,
run the following commands after the commands for a basic scenario have been
executed:
Step 1 Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority
InterRat and Second priority InterRat parameters set to UTRAN and GERAN,
respectively.
Step 2 Run the ADD CELLOPHOCFG command with the Highest Priority InterRAT and
Second Priority InterRAT parameters set to UTRAN and GERAN, respectively.
----End
Basic scenario 1: CSFB to UTRAN using blind redirection (configured with neighboring
UTRAN cells)
Basic scenario 1: CSFB to UTRAN using blind redirection (without neighboring UTRAN
cells)
MOD ENODEBALGOSWITCH: HoModeSwitch=BlindHoSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=9700, ConnFreqPriority=8;
MOD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=9700, Mcc="460", Mnc="20";
Enhanced scenario 3: Policy setting for handling the conflicts between handover and CSFB
procedures
MOD GLOBALPROCSWITCH: HoProcCtrlSwitch= CsfbFlowFirstSwitch-1;
Signaling Observation
The activation observation procedure for CSFB to UTRAN is as follows:
1. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that the UE falls
back to a UTRAN cell and completes the call.
2. Enable a UE to camp on an E-UTRAN cell and receive a voice call so that the UE falls
back to a UTRAN cell and completes the call.
The activation observation procedure for load-based CSFB to UTRAN is as follows:
Two UTRAN cells A and B report MRs and are under overload control and in the normal
state, respectively. The RSCP of cell A is larger than that of cell B.
Enable a UE to perform a PS-handover-based CSFB when both cell A and cell B 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:
CSFB handover success rate for emergency calls =
L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency/
L.IRATHO.E2W.CSFB.ExecAttOut.Emergency
This feature supports quick configuration of counter collection by feature using the U2000.
The measurement for the counters related to this feature can be set in a single operation.
These counters are determined by the counter-feature relationships listed in the performance
counter reference. For details about the operations, see "Quickly Setting Performance
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 the second-highest-priority RAT is different
from the highest-priority RAT and lowest-priority
RAT.
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 the lowest-priority RAT is different from the
highest-priority RAT and second-highest-priority
RAT.
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.
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.
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
If the UTRAN uses Huawei devices, corresponding licenses need to be activated.
l If the eNodeB obtains load information through the RIM procedure, WRFD-150231
RIM Based UMTS Target Cell Selection for LTE needs to be activated. For details, see
"WRFD-150231 RIM Based UMTS Target Cell Selection for LTE" in "Engineering
Guidelines" in Interoperability Between UMTS and LTE Feature Parameter Description
of RAN Feature Documentation.
l If the eNodeB obtains system information through the RIM procedure, WRFD-140224
Fast CS Fallback Based on RIM needs to be activated. For details, see "Engineering
Guidelines" in Fast CS Fallback Based on RIM Feature Parameter Description of RAN
Feature Documentation.
8.2.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 ENodeBAlgoSwitch MO
to configure the RIM procedure.
The following table describes the parameters that must be set in the S1Interface or S1 MO to
configure the MME protocol release. To activate RIM procedures in Multiple Report mode,
set the parameter to Release_R9(Release 9) or later.
(Optional) If some operators or RNCs do not support the RIM procedure to the UTRAN, you
need to configure the RIM procedure for Separate Mobility Policies to UTRAN for Multi
PLMN.
l The following table describes the parameter that must be set in the ENodeBAlgoSwitch
MO to enable Separate Mobility Policies to UTRAN for Multi PLMN.
l The following table describes the parameters that must be set in the
UtranNetworkCapCfg MO to configure UTRAN capabilities.
Mobile UtranN Radio This parameter specifies the MCC of the base
country etwork planning station that serves the neighboring cell. If this
code CapCfg (negotiation neighboring cell works in RAN sharing
.Mcc with the peer) mode, set this parameter to the MCC of the
primary operator.
If the peer UTRAN equipment is provided by
Huawei, set this parameter to the same value
as the corresponding parameter in the
URNCBASIC MO of the peer RNC.
l (Optional) If some operators or RNCs do not support the RIM procedure to the UTRAN,
run the following commands:
ADD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0, NetworkCapCfg=
SiByRimCapCfg-0;
MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch= UtranSepOpMobilitySwitch-1;
Table 8-10 Counters related to the RIM procedure between E-UTRAN and UTRAN
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 respond 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 respond to the RIM request normally.
----End
8.2.7 Deactivation
Table 8-11 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.
l If the controller to be connected is provided by Huawei, enable RIM RSN optimization
on the controller side. For details, see Fast CS Fallback Based on RIM Feature
Parameter Description of RAN Feature Documentation.
License
The operator has purchased and activated the license for the feature listed in Table 8-13.
NOTE
If the UTRAN uses Huawei devices, Fast CS Fallback Based on RIM needs to be enabled on the
UTRAN. For details, see Fast CS Fallback Based on RIM Feature Parameter Description of RAN
Feature Documentation.
8.3.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. Neighbor relationships must be configured because only the
neighboring cells whose system information has been obtained can be target cells for flash
CSFB.
Scenario-specific Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
enable flash CSFB to UTRAN.
The following table describes the parameters that must be set in the InterRatHoComm MO
to set the maximum number of neighboring cells whose system information can be included
in a redirection message.
Max Utran InterRatH Default/ Set this parameter based on the network plan.
cell num in oComm.C Recommended The default value is 8. If this parameter is set
redirection ellInfoMa value 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 the CSFB success rate is
affected.
NOTE
Step 2 (Optional) Run the MOD INTERRATHOCOMM command with the Max Utran cell num
in redirection parameter set (its default value is 8).
Step 3 (Optional) Run the MOD INTERRATHOCOMM command with the Max Utran cell num
in CSFB EMC redirection parameter set, for example, to 3.
----End
Counter Observation
Table 8-14 lists the performance counters for observing functions related to flash CSFB to
UTRAN.
8.3.7 Deactivation
Table 8-15 describes the parameters for deactivating this feature.
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-16.
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.
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 ENodeBAlgoSwitch MO
to enable ultra-flash CSFB to UTRAN.
(Optional) If some operators or RNCs do not support ultra-flash CSFB to UTRAN, you need
to configure the ultra-flash CSFB to UTRAN capability of Separate Mobility Policies to
UTRAN for Multi PLMN.
l The following table describes the parameter that must be set in the ENodeBAlgoSwitch
MO to enable Separate Mobility Policies to UTRAN for Multi PLMN.
Parameter Parameter Data Setting Notes
Name ID Source
l The following table describes the parameters that must be set in the
UtranNetworkCapCfg MO to configure UTRAN capabilities.
Paramet Param Data Source Setting Notes
er Name eter ID
Mobile UtranN Radio This parameter specifies the MCC of the base
country etwork Planning station that serves the neighboring cell. If this
code CapCfg (Negotiation neighboring cell works in RAN sharing
.Mcc with the peer) mode, set this parameter to the MCC of the
primary operator.
If the peer UTRAN equipment is provided by
Huawei, set this parameter to the same value
as the corresponding parameter in the
URNCBASIC MO of the peer RNC.
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 UTRAN frequencies and UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
----End
Step 1 Run the ADD UTRANNETWORKCAPCFG command to set the Mcc, Mnc, and RncId
parameters, and clear the UltraFlashCsfbCapCfg option of the NetworkCapCfg parameter
for the operators or RNCs that do not support ultra-flash CSFB to UTRAN.
----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 UE compatibility risks exist after ultra-
flash CSFB is activated.
MOD GLOBALPROCSWITCH: UeCompatSwitch=UltraFlashCsfbComOptSw-1;
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-17 can be viewed to check whether the feature has taken effect.
8.4.7 Deactivation
Table 8-18 describes the parameters for deactivating this feature.
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 UTRAN neighbor relationships and to determine
whether to perform CSFB based on handover or redirection. For details, see Inter-RAT
Mobility Management in Connected Mode.
Table 8-20 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-21.
8.5.4 Precautions
None
8.5.7 Deactivation
LOFD-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.
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-22.
8.6.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 CS Fallback Steering to UTRAN.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to specify RAT priorities for CSFB triggered for RRC_CONNECTED UEs.
Highest CSFallBa Default/ Set this parameter based on the network plan.
priority ckBlindH Recommended This parameter is set to UTRAN by default
InterRat oCfg.Inte value and specifies the highest-priority RAT to be
rRatHigh considered in blind handovers for CSFB. For
estPri CSFB to UTRAN, set this parameter to
UTRAN.
Second CSFallBa Default/ Set this parameter based on the network plan.
priority ckBlindH Recommended This parameter is set to GERAN by default
InterRat oCfg.Inte value and specifies the second-highest-priority RAT
rRatSeco to be considered in blind handovers for
ndPri CSFB. Ensure that the second-highest-
priority RAT is different from the highest-
priority RAT and lowest-priority RAT.
Lowest CSFallBa Default/ Set this parameter based on the network plan.
priority ckBlindH Recommended This parameter is set to CDMA2000 by
InterRat oCfg.Inte value default and specifies the lowest-priority RAT
rRatLowe to be considered in blind handovers for
stPri CSFB. Ensure that the lowest-priority RAT is
different from the highest-priority RAT and
second-highest-priority RAT.
UTRAN CSFallBa Default/ Set this parameter based on the network plan.
LCS ckBlindH Recommended This parameter specifies the LCS capability
capability oCfg.Utra value of the UTRAN.
nLcsCap
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to specify RAT priorities for CSFB triggered for RRC_IDLE UEs.
CSFB CSFallBack Default Set this parameter based on the network plan. This
Highes BlindHoCfg. / parameter is set to UTRAN by default and specifies
t IdleCsfbHig Recom the highest-priority RAT to be considered in CSFB for
priority hestPri mended UEs in idle mode. For CSFB to UTRAN, set this
InterRa value parameter to UTRAN.
t for
Idle
UE
CSFB CSFallBack Default Set this parameter based on the network plan. This
Second BlindHoCfg. / parameter is set to GERAN by default and specifies
priority IdleCsfbSeco Recom the second-highest-priority RAT to be considered in
InterRa ndPri mended CSFB for UEs in idle mode. Ensure that the second-
t for value highest-priority RAT is different from the highest-
Idle priority RAT and lowest-priority RAT.
UE
CSFB CSFallBack Default Set this parameter based on the network plan. This
Lowest BlindHoCfg. / parameter is set to CDMA2000 by default and
priority IdleCsfbLow Recom specifies the lowest-priority RAT to be considered in
InterRa estPri mended CSFB for UEs in idle mode. Ensure that the lowest-
t for value priority RAT is different from the highest-priority
Idle RAT and second-highest-priority RAT.
UE
The following table describes the parameters that must be set in the CellOpHoCfg MO to
specify cell-level RAT priorities for CSFB triggered for RRC_CONNECTED and RRC_IDLE
UEs.
CN CellOpHoCf Engine Set this parameter based on the network plan. This
Operat g.CnOperato ering parameter identifies the operator whose RAT blind-
or ID rId Design handover priorities are to be set.
Local CellOpHoCf Radio Set this parameter based on the network plan. This
cell ID g.LocalCellI Plannin parameter identifies the cell whose RAT blind-
d g handover priorities are to be set.
(Interna
l
plannin
g)
Highe CellOpHoCf Default Set this parameter based on the network plan. This
st g.InterRatHi / parameter is set to UTRAN by default and specifies
Priorit ghestPri Recom the highest-priority RAT to be considered in blind
y mended handovers for CSFB. For CSFB to UTRAN, set this
InterR value parameter to UTRAN.
AT
Secon CellOpHoCf Default Set this parameter based on the network plan. This
d g.InterRatSe / parameter is set to GERAN by default and specifies
Priorit condPri Recom the second-highest-priority RAT to be considered in
y mended blind handovers for CSFB. Ensure that the second-
InterR value highest-priority RAT is different from the highest-
AT priority RAT and lowest-priority RAT.
Lowes CellOpHoCf Default Set this parameter based on the network plan. This
t g.InterRatLo / parameter is set to CDMA2000 by default and
Priorit westPri Recom specifies the lowest-priority RAT to be considered in
y mended blind handovers for CSFB. Ensure that the lowest-
InterR value priority RAT is different from the highest-priority RAT
AT and second-highest-priority RAT.
CSFB CellOpHoCf Default Set this parameter based on the network plan. This
Highe g.IdleCsfbHi / parameter is set to UTRAN by default and specifies
st ghestPri Recom the highest-priority RAT to be considered in blind
Priorit mended handovers for CSFB. For CSFB to UTRAN, set this
y value parameter to UTRAN.
InterR
AT for
Idle
UE
CSFB CellOpHoCf Default Set this parameter based on the network plan. This
Secon g.IdleCsfbSe / parameter is set to GERAN by default and specifies
d condPri Recom the second-highest-priority RAT to be considered in
Priorit mended blind handovers for CSFB. Ensure that the second-
y value highest-priority RAT is different from the highest-
InterR priority RAT and lowest-priority RAT.
AT for
Idle
UE
CSFB CellOpHoCf Default Set this parameter based on the network plan. This
Lowes g.IdleCsfbLo / parameter is set to CDMA2000 by default and
t westPri Recom specifies the lowest-priority RAT to be considered in
Priorit mended blind handovers for CSFB. Ensure that the lowest-
y value priority RAT is different from the highest-priority RAT
InterR and second-highest-priority RAT.
AT for
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 Engine Set this parameter based on the network plan. If this
service .CsPriority ering parameter is set to Priority_0(Priority 0) for the
priority Design UTRAN frequency, the eNodeB does not select the
frequency. The values Priority_16(Priority 16) and
Priority_1(Priority 1) indicate the highest and lowest
priorities, 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 Radio Set this parameter based on the network plan. If
PS .CsPsMixed Planning this parameter is set to Priority_0(Priority 0) for
mixed Priority (Internal the UTRAN frequency, the eNodeB does not
priority planning) select the frequency. The values
Priority_16(Priority 16) and
Priority_1(Priority 1) indicate the highest and
lowest priorities, 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 Default Set this parameter based on the network plan. The
handov PolicyCfg.C / default values are REDIRECTION, CCO_HO, and
er sfbHoPolicy Recom PS_HO. You are advised to set this parameter based
policy Cfg mended on the UE capabilities and network capabilities. For
Config value details about how to select a CSFB handover policy,
uration see 3.6 Execution.
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 Default Set this parameter based on the network plan. The
handov PolicyCfg.Id / default values are REDIRECTION, CCO_HO, and
er leModeCsfb Recom PS_HO. You are advised to set this parameter based
policy HoPolicyCfg mended on the UE capabilities and network capabilities. For
Config value details about how to select a CSFB handover policy,
uration see 3.6 Execution.
for idle
ue
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 set to UTRAN, GERAN,
GERAN, and UTRAN, respectively.
Step 3 Run the MOD CSFAllBACKPOLICYCFG command with the PS_HO check box selected
under the CSFB handover policy Configuration parameter and the REDIRECTION check
box selected under the CSFB handover policy Configuration for idle ue parameter.
----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 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&UtranCsfbSteeringSwitch-1&Gera
nCsfbSteeringSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-0;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,
InterRatSecondPri=GERAN, IdleCsfbHighestPri=UTRAN, IdleCsfbSecondPri=GERAN;
8.6.7 Deactivation
Table 8-23 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-24.
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
Step 2 Run the MOD UTRANNFREQ command with the CS service priority parameter set to
Priority_16(Priority 16).
----End
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. Enable the UE to 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. Enable the UE to 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-25 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-27.
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.
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.
5. GeranNcell: used to configure the neighbor relationship with a GERAN cell. If a
neighboring GERAN cell supports blind handovers according to the network plan, the
blind-handover priority of the cell must be specified by the GeranNcell.BlindHoPriority
parameter.
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 CS
Fallback to GERAN.
Handover ENodeBAl Engineering Set this parameter based on the network plan.
Mode goSwitch. Design To activate PS handovers, select the
switch HoModeS GeranPsHoSwitch(GeranPsHoSwitch) option.
witch To activate CCO, select the
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 Engineering To activate blind handovers for a cell served by the
r Mode ParaCf Design eNodeB, select the
switch g.HoMo BlindHoSwitch(BlindHoSwitch) option of this
deSwitc parameter. If this option is deselected, blind
h handovers will not take effect in this cell.
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 Radio When GERAN and E-UTRAN cells are co-sited
r oSwitch Planning with the same coverage, you can turn on
Allowed .HoAllo (Negotiation CsfbAdaptiveBlindHoS-
Switch wedSwit with the witch(CsfbAdaptiveBlindHoSwitch). The eNodeB
ch peer) decides whether to use measurement-based or blind
handovers to GERAN based on A1 reports from
UEs.
CSFB CSFall Default/ This parameter specifies the RSRP threshold of the
Adaptive BackHo Recommend serving cell above which a CSFB-triggered adaptive
Blind Ho .BlindH ed value blind handover is triggered. If the RSRP value
A1 RSRP oA1Thd measured by a UE exceeds this threshold, the UE
Trigger Rsrp submits an 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 Default/ Set this parameter based on the network plan.
priority lindHoCfg.Int Recomme This parameter is set to UTRAN by default and
InterRat erRatHighest nded specifies the highest-priority RAT to be
Pri value considered in blind handovers for CSFB. For
CSFB to GERAN, set this parameter to
GERAN.
Second CSFallBackB Default/ Set this parameter based on the network plan.
priority lindHoCfg.Int Recomme This parameter is set to GERAN by default and
InterRat erRatSecondP nded specifies the second-highest-priority RAT to be
ri value considered in blind handovers for CSFB. If the
highest-priority RAT has been set to GERAN,
the second-highest-priority RAT cannot be set
to GERAN. Ensure that the second-highest-
priority RAT is different from the highest-
priority RAT and lowest-priority RAT.
Lowest CSFallBackB Default/ Set this parameter based on the network plan.
priority lindHoCfg.Int Recomme This parameter is set to CDMA2000 by default
InterRat erRatLowestP nded and specifies the lowest-priority RAT to be
ri value considered in blind handovers for CSFB.
Ensure that the lowest-priority RAT is different
from the highest-priority RAT and second-
highest-priority RAT.
GERAN CSFallBackB Default/ Set this parameter based on the network plan.
LCS lindHoCfg.Ge Recomme This parameter specifies the LCS capability of
capability ranLcsCap nded the GERAN.
value
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 Engine Set this parameter based on the network plan. This
Operat g.CnOperato ering parameter identifies the operator whose RAT blind-
or ID rId Design handover priorities are to be set.
Local CellOpHoCf Radio Set this parameter based on the network plan. This
cell ID g.LocalCellI Plannin parameter identifies the cell whose RAT blind-
d g handover priorities are to be set.
(Interna
l
plannin
g)
Highe CellOpHoCf Default Set this parameter based on the network plan. This
st g.InterRatHi / parameter is set to UTRAN by default and specifies
Priorit ghestPri Recom the highest-priority RAT to be considered in blind
y mended handovers for CSFB. For CSFB to UTRAN, set this
InterR value parameter to UTRAN.
AT
Secon CellOpHoCf Default Set this parameter based on the network plan. This
d g.InterRatSe / parameter is set to GERAN by default and specifies
priorit condPri Recom the second-highest-priority RAT to be considered in
y mended blind handovers for CSFB. Ensure that the second-
InterR value highest-priority RAT is different from the highest-
at priority RAT and lowest-priority RAT.
Lowes CellOpHoCf Default Set this parameter based on the network plan. This
t g.InterRatLo / parameter is set to CDMA2000 by default and
Priorit westPri Recom specifies the lowest-priority RAT to be considered in
y mended blind handovers for CSFB. Ensure that the lowest-
InterR value priority RAT is different from the highest-priority RAT
AT and second-highest-priority RAT.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.
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.
This function is also controlled by the GeranCsfbSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
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 1: CSFB to GERAN using blind redirection
CSFB to GERAN using blind redirection works regardless of whether neighboring
GERAN cells are configured.
If you want to configure a neighboring GERAN cell, you must configure the
GeranNFreq and GeranNCell MOs. For details about parameter settings, see
Inter-RAT Mobility Management in Connected Mode.
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
cell-level parameter Handover Mode switch selected.
Step 2 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter deselected and the
REDIRECTION option of the same parameter selected.
Step 3 (Optional) If a neighboring GERAN cell is configured, run the MOD GERANNCELL
command with the Blind handover priority parameter set to the highest priority (for
example, 32).
Step 4 (Optional) If a neighboring GERAN cell is not configured, perform the following operations:
1. Run the ADD GERANNFREQGROUP command with the Frequency Priority for
Connected Mode parameter set to the highest priority (for example, 8).
2. Run the ADD GERANNFREQGROUPARFCN command to add a GERAN ARFCN
to a neighboring BCCH carrier frequency group.
Step 5 (Optional) Run the MOD GLOBALPROCSWITCH command with the
IdleCsfbRedirectOptSwitch option of the Protocol Message Optimization Switch
parameter selected.
----End
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
BlindHoSwitch(BlindHoSwitch), GeranNaccSwitch(GeranNaccSwitch), and
GeranCcoSwitch(GeranCcoSwitch) options of the Handover Mode switch parameter, and
the GERAN_RIM_SWITCH(GERAN RIM Switch) option of the RIM switch parameter
selected.
Step 3 Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO and CCO_HO
options of the CSFB handover policy Configuration parameter deselected and selected,
respectively.
Step 5 Run the MOD GERANNCELL command with the Blind handover priority parameter set
to 32.
----End
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
BlindHoSwitch(BlindHoSwitch) and GeranPsHoSwitch(GeranPsHoSwitch) options of
the Handover Mode switch parameter selected.
Step 3 Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
Step 4 (Optional) If the optional feature LOFD-001089 CS Fallback Steering to GERAN is enabled,
run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
Step 5 Run the MOD GERANNCELL command with the Blind handover priority parameter set
to 32.
----End
l Basic scenario 4: CSFB to GERAN using measurement-based redirection
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 CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter deselected and the
REDIRECTION option of the same parameter selected.
Step 4 Run the MOD CSFALLBACKHO command with the CSFB Protection Timer parameter
specified.
----End
l Basic scenario 5: CSFB to GERAN using measurement-based handovers
(recommended)
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
GeranPsHoSwitch(GeranPsHoSwitch) option of the Handover Mode switch parameter
selected.
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 (Optional) If the optional feature LOFD-001089 CS Fallback Steering to GERAN is enabled,
run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
Step 5 Run the MOD CSFALLBACKHO command with the CSFB Protection Timer parameter
specified.
----End
l Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC
(recommended)
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 3 Run the MOD S1INTERFACE command with the MME Release parameter set to
Release_R9(Release 9).
Step 4 Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter deselected for the cells to be measured.
Step 5 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO and CCO_HO
options of the CSFB handover policy Configuration parameter deselected and selected,
respectively.
Step 6 Run the MOD CSFALLBACKHO command with the CSFB Protection Timer parameter
specified.
----End
l Enhanced scenario 1: Policy setting for handling the conflicts between handover and
CSFB procedures
Run the following command after the commands for a basic scenario have been
executed:
Step 1 Run the MOD GLOBALPROCSWITCH command with the CsfbFlowFirstSwitch option
of the Handover Process Control Switch parameter selected.
----End
l Enhanced scenario 2: If you need to set the highest-priority RAT for CSFB to GERAN,
run the following commands after the commands in a basic scenario have been executed:
Step 1 Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority
InterRat and Second priority InterRat parameters set to GERAN and UTRAN,
respectively.
Step 2 Run the ADD CELLOPHOCFG command with the Highest Priority InterRAT and
Second Priority InterRAT parameters set to GERAN and UTRAN, respectively.
----End
l Basic scenario 1: CSFB to GERAN using blind redirection (configured with neighboring
GERAN cells)
MOD ENODEBALGOSWITCH: HoModeSwitch=BlindHoSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
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
MOD GLOBALPROCSWITCH: HoProcCtrlSwitch= CsfbFlowFirstSwitch-1;
Signaling Observation
The activation observation procedure is as follows:
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,
Counter Observation
Table 8-28 lists the performance counters for observing functions related to CSFB to
GERAN.
8.8.7 Deactivation
Table 8-29 describes the parameters for deactivating this feature.
Table 8-30 lists the counters related to the execution of CSFB by the eNodeB.
Table 8-32 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-33.
Table 8-33 Counters related to using CCO with NACC or CCO without NACC
After the CSFB protection timer expires, the eNodeB may perform a blind redirection to enter
the protection procedure. Table 8-34 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-34 Counter related to the number of times that the eNodeB enters the protection
procedure for CSFB
Counter ID Counter Name Description
Table 8-35 lists the counters related to CSFB for emergency calls.
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.
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, 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
procedure through eCoordinator turned on.
License
If the GERAN uses Huawei devices, GBFD-511308 eNACC Between GSM and LTE needs to
be activated. For details, see "Deploying eNACC Between GSM and LTE" in "Engineering
Guidelines" in Interoperability Between GSM and LTE Feature Parameter Description of
GBSS Feature Documentation.
8.9.4 Precautions
None
Required Data
The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For details,
see 8.8.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.
The following table describes the parameters that must be set in the S1Interface or S1 MO to
configure the MME protocol release. To activate RIM procedures in Multiple Report mode,
set the parameter to Release_R9(Release 9) or later.
(Optional) If some operators or neighboring GERAN cells do not support the RIM procedure
to the GERAN, you need to configure the RIM procedure for Separate Mobility Policies to
GERAN for Multi PLMN.
l The following table describes the parameter that must be set in the CellAlgoSwitch MO
to enable Separate Mobility Policies to GERAN for Multi PLMN.
l The following table describes the parameters that must be set in the
GeranNetworkCapCfg MO to configure GERAN capabilities.
Paramet Parameter ID Data Setting Notes
er Name Source
l (Optional) If some operators or neighboring GERAN cells do not support the RIM
procedure to the GERAN, perform the following operations:
ADD GERANNETWORKCAPCFG: Mcc="460", Mnc="32", Lac=1,
NetworkCapCfg=SiByRimCapCfg-0;
MOD CELLALGOSWITCH: LocalCellId=0,
HoAllowedSwitch=SrvBasedInterFreqHoSw-0&GeranSepOpMobilitySwitch-1;
Counter Observation
No matter whether the RIM procedure is performed through the core network or the
eCoordinator, performance counters listed in Table 8-36 can be used to observe whether the
RIM procedure has taken effect.
Table 8-36 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 respond 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 respond 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-37 describes the parameters for deactivating this feature.
Before deploying this feature, deploy the RIM procedure from E-UTRAN to GERAN. For
details, see 8.9 RIM Procedure from E-UTRAN to GERAN.
For policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT
Mobility Management in Connected Mode. If GERAN and E-UTRAN cells serve the same
area, or the GERAN cell provides better coverage than the E-UTRAN cell, use CSFB based
on blind handover to decrease the CSFB delay.
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-39.
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
Required Data
The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For details,
see 8.8.5.1 Data Preparation. Neighbor relationships must be configured because only the
neighboring cells whose system information has been obtained can be target cells for flash
CSFB.
Scenario-specific Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
enable flash CSFB to GERAN.
The following table describes the parameters that must be set in the InterRatHoComm MO
to set the maximum number of neighboring cells whose system information can be included
in a redirection message.
Max Geran cell InterRatHo Default/ Set this parameter based on the network
num in Comm.CellI Recomme plan. The default value is 8. If this
redirection nfoMaxGera nded parameter is set to a small value, the flash
nCellNum value CSFB success rate decreases because UEs
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
the CSFB success rate is affected.
Max Geran cell InterRatHo Default/ To use flash CSFB for emergency
num in CSFB Comm.Gera Recomme redirection, change the parameter value
EMC nCellNumF nded from the default value 0 to a non-zero
redirection orEmcRedir value value.
ect
Step 2 (Optional) Run the MOD INTERRATHOCOMM command with the Max Geran cell num
in redirection parameter set (its default value is 8).
Step 3 (Optional) Run the MOD INTERRATHOCOMM command with the Max Geran cell num
in CSFB EMC redirection parameter set, for example, to 3.
----End
Figure 8-11 RRC Connection Release message during flash CSFB to GERAN
Counter Observation
Table 8-40 lists the performance counters for observing functions related to flash CSFB to
GERAN.
8.10.7 Deactivation
Table 8-41 describes the parameters for deactivating this feature.
8.11.3 Requirements
Operating Environment
This feature is a Huawei-proprietary one 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-42.
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.
Required Data
The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For details,
see 8.8.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 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 parameters that must be set in the CellDrxPara MO to set
the DRX for measurement switch when UEs support DRX-based measurements.
DRX for CellDrx Engineering When the network supports measurements and UEs
Measure Para.Dr Design support DRX measurements well, measurement
ment xForMe delays are significantly reduced and the customer
Switch asSwitc can tolerate the impact on services during
h measurements.
Long CellDrx Engineering This parameter specifies the length of the long DRX
DRX Para.Lo Design cycle specific to GERAN measurement.
Cycle for ngDrxC
Measure ycleFor
ment Meas
DRX CellDrx Engineering This parameter specifies the length of the DRX
Inactivity Para.Dr Design Inactivity Timer specific to GERAN measurement.
Timer for xInactTi
Measure merFor
ment Meas
DRX CellDrx Engineering This parameter specifies the length of the DRX
Retransm Para.Dr Design Retransmission Timer specific to GERAN
ission xReTxT measurement.
Timer for imerFor
Measure Meas
ment
Short CellDrx Engineering This parameter specifies the length of the short
DRX Para.Sh Design DRX cycle specific to GERAN measurement.
Cycle for ortDrxC
Measure ycleFor
ment Meas
Short CellDrx Engineering This parameter specifies the length of the Short
Cycle Para.Sh Design Cycle Timer specific to GERAN measurement.
Timer for ortCycle
Measure TimerF
ment orMeas
(Optional) If some operators or neighboring GERAN cells do not support ultra-flash CSFB to
GERAN, you need to configure the ultra-flash CSFB to GERAN capability of Separate
Mobility Policies to GERAN for Multi PLMN.
l The following table describes the parameter that must be set in the CellAlgoSwitch MO
to enable Separate Mobility Policies to GERAN for Multi PLMN.
l The following table describes the parameters that must be set in the
GeranNetworkCapCfg MO to configure GERAN capabilities.
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 and required when some external GERAN cells do not support Ultra-Flash CSFB to
GERAN) Run the MOD GERANEXTERNALCELL command with the Ultra-Flash CSFB
Capability Indication parameter set to BOOLEAN_FALSE.
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) If some operators or neighboring GERAN cells do not support ultra-flash
CSFB to GERAN, perform the following operations:
Step 1 Run the ADD GERANNETWORKCAPCFG command with the Mcc, Mnc, and Lac
parameters set, and with the UltraFlashCsfbCapCfg option of the NetworkCapCfg
parameter deselected for the operators or neighboring GERAN cells that do not support ultra-
flash CSFB to GERAN.
Step 2 Run the MOD CELLALGOSWITCH command with the GeranSepOpMobilitySwitch
option of the HoAllowedSwitch parameter selected.
----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 UE compatibility risks exist after ultra-
flash CSFB is activated.
MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-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-44 describes the parameters for deactivating this feature.
This feature does not support the function of "Quickly Setting Performance Measurement by
Feature" of the U2000.
2. Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN
and GERAN cells. Information about coverage areas includes engineering parameters of
sites (such as latitude and longitude), TX power of cell pilot signals, and neighbor
relationship configurations.
3. Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core
networks, and ensure that they all support CSFB and the MME supports LAI delivery.
Table 8-46 describes the requirements of CSFB with LAI to GERAN for the core
networks.
4. 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 GERAN neighbor relationships and to determine
whether to perform CSFB based on handover or redirection. For details, see Inter-RAT
Mobility Management in Connected Mode.
Table 8-46 Requirements of CSFB with LAI to GERAN for core networks
NE Requirement
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-47.
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 originate a voice call so that the UE falls
back to the GERAN 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 GERAN cell with the specified LAI and completes the 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
LOFD-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-48.
8.13.4 Precautions
None
Required Data
The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For details,
see 8.8.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 specify RAT priorities for CSFB triggered for RRC_CONNECTED UEs.
CN CSFallBack Engine Set this parameter based on the network plan. This
Operat BlindHoCfg. ering parameter identifies the operator whose RAT blind-
or ID CnOperatorI Design handover priorities are to be set.
d
Highes CSFallBack Default Set this parameter based on the network plan. This
t BlindHoCfg. / parameter is set to UTRAN by default and specifies
priority InterRatHig Recom the highest-priority RAT to be considered in blind
InterRa hestPri mended handovers for CSFB.
t value
Second CSFallBack Default Set this parameter based on the network plan. This
priority BlindHoCfg. / parameter is set to GERAN by default and specifies
InterRa InterRatSeco Recom the second-highest-priority RAT to be considered in
t ndPri mended blind handovers for CSFB. Ensure that the second-
value highest-priority RAT is different from the highest-
priority RAT and lowest-priority RAT.
Lowest CSFallBack Default Set this parameter based on the network plan. This
priority BlindHoCfg. / parameter is set to CDMA2000 by default and
InterRa InterRatLow Recom specifies the lowest-priority RAT to be considered in
t estPri mended blind handovers for CSFB. Ensure that the lowest-
value priority RAT is different from the highest-priority
RAT and second-highest-priority RAT.
GERA CSFallBack Default Set this parameter based on the network plan. This
N LCS BlindHoCfg. / parameter specifies the LCS capability of the
capabil GeranLcsCa Recom GERAN.
ity p mended
value
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to specify RAT priorities for CSFB triggered for RRC_IDLE UEs.
CSFB CSFallBack Default Set this parameter based on the network plan. This
Highes BlindHoCfg. / parameter is set to UTRAN by default and specifies
t IdleCsfbHig Recom the highest-priority RAT to be considered in CSFB for
priority hestPri mended UEs in idle mode.
InterRa value
t for
Idle
UE
CSFB CSFallBack Default Set this parameter based on the network plan. This
Second BlindHoCfg. / parameter is set to GERAN by default and specifies
priority IdleCsfbSeco Recom the second-highest-priority RAT to be considered in
InterRa ndPri mended CSFB for UEs in idle mode. Ensure that the second-
t for value highest-priority RAT is different from the highest-
Idle priority RAT and lowest-priority RAT.
UE
CSFB CSFallBack Default Set this parameter based on the network plan. This
Lowest BlindHoCfg. / parameter is set to CDMA2000 by default and
priority IdleCsfbLow Recom specifies the lowest-priority RAT to be considered in
InterRa estPri mended CSFB for UEs in idle mode. Ensure that the lowest-
t for value priority RAT is different from the highest-priority
Idle RAT and second-highest-priority RAT.
UE
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 Default Set this parameter based on the network plan. The
handov PolicyCfg.C / default values are REDIRECTION, CCO_HO, and
er sfbHoPolicy Recom PS_HO. You are advised to set this parameter based
policy Cfg mended on the UE capabilities and network capabilities. For
Config value details about how to select a CSFB handover policy,
uration see 4.6 Execution.
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 Default Set this parameter based on the network plan. The
handov PolicyCfg.Id / default values are REDIRECTION, CCO_HO, and
er leModeCsfb Recom PS_HO. You are advised to set this parameter based
policy HoPolicyCfg mended on the UE capabilities and network capabilities. For
Config value details about how to select a CSFB handover policy,
uration see 4.6 Execution.
for idle
ue
This feature is also controlled by the GeranCsfbSteeringSwitch option of the eNodeB-level parameter
ENodeBAlgoSwitch.HoAlgoSwitch.
If the option of the eNodeB-level parameter is selected, the option of the cell-level parameter does not
take effect. If the option of the eNodeB-level parameter is deselected, the option of the cell-level
parameter takes effect.
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 set to UTRAN, GERAN,
GERAN, and UTRAN, respectively, based on the network conditions and policies.
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
3. Enable the UE to initiate a voice call in idle mode and in connected mode.
4. Observe the counters L.CSFB.E2G, L.RRCRedirection.E2G.CSFB, and
L.IRATHO.E2G.CSFB.ExecAttOut. If the values of the counters increase by 2, 1, and
1, respectively, CSFB steering to GERAN has been activated.
If LOFD-001088 CS Fallback Steering to UTRAN has also been activated, the activation
observation procedure is as follows:
8.13.7 Deactivation
Table 8-49 describes the parameters for deactivating this feature.
Fault Description
A UE performs cell reselection to an inter-RAT neighboring cell directly after initiating a
voice call in an E-UTRAN cell, and the S1 interface tracing result shows that CSFB is not
triggered.
Fault Handling
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 so, go to Step 2.
l If not, rectify the fault and try again. If the fault persists, contact Huawei technical
support.
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
ENODEBALGOSWITCH command with the BlindHoSwitch(BlindHoSwitch) check box
under the Handover Mode Switch parameter selected.
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
The following 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-51 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
Fault Handling
To prevent the stored system information from being outdated, the eNodeB automatically
updates the system information at a randomly selected time point within 02:30 a.m. to 04:30
a.m. every day.
Besides, when the preceding flash CSFB failure occurs, you are advised to manually delete
the outdated system information and enable the eNodeB to send a RIM request again after the
UTRAN or GERAN cells become stable. The following is the manual operation:
----End
9 Parameters
CellHoP L2UCsf MOD LOFD-0 CS Meaning: Indicates how measurement reports are
araCfg bMRPro CELLH 01033 / Fallback handled in measurement-based CSFB to UTRAN. If
Mode OPARA TDLOF to this parameter is set to
CFG D-00103 UTRAN HANDOVER_IMMEDIATELY, the eNodeB
LST 3 immediately performs handover decision after
CELLH receiving a measurement report for CSFB to UTRAN.
OPARA If this parameter is set to
CFG BASED_ON_SIGNAL_STRENGTH, the eNodeB
transfers UEs to the strongest cell. If this parameter is
set to BASED_ON_FREQ_PRIORITY, the eNodeB
hands over UEs to a cell on a frequency with a priority
as high as possible. If this parameter is set to
BASED_ON_LOAD, the eNodeB hands over UEs to
a cell with load as light as possible or redirects UEs to
the frequency of a cell with load as light as possible.
This parameter applies only to LTE FDD and LTE
TDD.
GUI Value Range:
HANDOVER_IMMEDIATELY(HANDOVER_IMM
EDIATELY),
BASED_ON_SIGNAL_STRENGTH(BASED_ON_S
IGNAL_STRENGTH),
BASED_ON_FREQ_PRIORITY(BASED_ON_FRE
Q_PRIORITY),
BASED_ON_LOAD(BASED_ON_LOAD)
Unit: None
Actual Value Range: HANDOVER_IMMEDIATELY,
BASED_ON_SIGNAL_STRENGTH,
BASED_ON_FREQ_PRIORITY,
BASED_ON_LOAD
Default Value:
HANDOVER_IMMEDIATELY(HANDOVER_IMM
EDIATELY)
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. This parameter applies only to LTE FDD and
LST 3 CS LTE TDD.
CSFAL LOFD-0 Fallback GUI Value Range: 1~10
LBACK 01034 / to Unit: s
HO TDLOF GERAN
D-00103 Actual Value Range: 1~10
Enhance
4 d CS Default Value: 4
LOFD-0 Fallback
01090 / to
TDLOF CDMA2
D-00109 000
0 1xRTT
CSFallB CsfbProt MOD LOFD-0 CS Meaning: Indicates the timer governing the period in
ackHo ectTime CSFAL 01033 / Fallback which only CSFB can be performed. After the timer
r LBACK TDLOF to expires, the eNodeB performs a blind redirection for
HO D-00103 UTRAN the UE. This parameter does not take effect when
LST 3 CS being set to 0. This option applies only to LTE FDD
CSFAL LOFD-0 Fallback and LTE TDD.
LBACK 01034 / to GUI Value Range: 0~100
HO TDLOF GERAN Unit: 100ms
D-00103 Enhance
4 Actual Value Range: 0~10000
d CS
LOFD-0 Fallback Default Value: 0
01090 / to
TDLOF CDMA2
D-00109 000
0 1xRTT
UtranCsfbSwitch:Off, GeranCsfbSwitch:Off,
UtranFlashCsfbSwitch:Off, GeranFlashCsfbS-
witch:Off, CsfbAdaptiveBlindHoSwitch:Off,
UtranCsfbSteeringSwitch:Off, GeranCsfbSteeringS-
witch:Off, ServBasedHoBackSwitch:Off,
ServiceReqInterFreqHoSwitch:Off
TDLOF Steering 1xRTT are enabled and UEs using a specific type of
D-00105 to services can be handed over to CDMA2000 1xRTT. If
3 UTRAN this option is deselected, service-based handovers to
LOFD-0 CS CDMA2000 1xRTT are disabled. This option is not
01088 / Fallback supported in this version.
TDLOF Steering
UlQualityInterRATHoSwitch: If this option is
D-00108 to
selected, UL-quality-based inter-RAT handovers are
8 GERAN
enabled and UEs can be handed over to inter-RAT
LOFD-0 Enhance cells to ensure service continuity when the UL signal
01089 / d CS quality is poor. If this option is deselected, UL-
TDLOF Fallback quality-based inter-RAT handovers are disabled.
D-00108 to
9 CDMA2 InterPlmnHoSwitch: If this option is selected, inter-
000 PLMN handovers are enabled and UEs can be handed
LOFD-0
1xRTT over to cells in other PLMNs. If this option is
01090 /
PS Inter- deselected, inter-PLMN handovers are disabled.
TDLOF
D-00109 RAT
UtranFlashCsfbSwitch: This option takes effect only
0 Mobility
when the UtranCsfbSwitch option is selected. If the
between
LOFD-0 UtranFlashCsfbSwitch option is selected, flash CSFB
E-
01019 / to UTRAN is enabled and the eNodeB sends system
UTRAN
TDLOF information of candidate target UTRAN cells to UEs
and
D-00101 during redirection. If the UtranFlashCsfbSwitch
UTRAN
9 option is deselected, flash CSFB to UTRAN is
PS Inter- disabled.
LOFD-0
RAT
01020 / GeranFlashCsfbSwitch: This option takes effect only
Mobility
TDLOF when the GeranCsfbSwitch option is selected. If the
between
D-00102 GeranFlashCsfbSwitch option is selected, flash CSFB
E-
0 to GERAN is enabled and the eNodeB sends system
UTRAN
LOFD-0 and information of candidate target GERAN cells to UEs
01043 / GERAN during redirection. If the GeranFlashCsfbSwitch
TDLOF option is deselected, flash CSFB to GERAN is
Service
D-00104 disabled.
based
3
inter- ServiceBasedInterFreqHoSwitch: If this option is
LOFD-0 RAT selected, service-based inter-frequency handovers are
01046 / handove enabled and UEs using a specific type of services can
TDLOF r to be handed over to inter-frequency cells. If this option
D-00104 UTRAN is deselected, service-based inter-frequency handovers
6 Service are disabled.
LOFD-0 based
01072 / inter- UlQualityInterFreqHoSwitch: If this option is
TDLOF RAT selected, UL-quality-based inter-frequency handovers
D-00107 handove are enabled and UEs can be handed over to inter-
2 r to frequency cells to ensure service continuity when the
LOFD-0 GERAN UL signal quality is poor. If this option is deselected,
01073 / Distance UL-quality-based inter-frequency handovers are
TDLOF based disabled.
EmcInterFreqBlindHoSwitch(EmcInterFreqBlind-
HoSwitch), EPlmnSwitch(EPlmnSwitch),
ServiceReqInterFreqHoSwitch(ServiceReqInterFreq-
HoSwitch),
VoipHoControlSwitch(VoipHoControlSwitch),
UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbS-
witch), GeranUltraFlashCsfbS-
witch(GeranUltraFlashCsfbSwitch),
RatLayerSwitch(RatLayerSwitch), ServiceBasedMul-
tiFreqHoSwitch(ServiceBasedMultiFreqHoSwitch),
SrvccRatSteeringSwitch(SrvccRatSteeringSwitch),
PsRatSteeringSwitch(PsRatSteeringSwitch)
Unit: None
Actual Value Range: IntraFreqCoverHoSwitch,
InterFreqCoverHoSwitch, UtranCsfbSwitch,
GeranCsfbSwitch, Cdma1xRttCsfbSwitch,
UtranServiceHoSwitch, GeranServiceHoSwitch,
CdmaHrpdServiceHoSwitch,
Cdma1xRttServiceHoSwitch, UlQualityInterRA-
THoSwitch, InterPlmnHoSwitch, UtranFlashCsfbS-
witch, GeranFlashCsfbSwitch, ServiceBasedInter-
FreqHoSwitch, UlQualityInterFreqHoSwitch,
CsfbAdaptiveBlindHoSwitch, UtranCsfbSteeringS-
witch, GeranCsfbSteeringSwitch,
CSFBLoadInfoSwitch, Cdma1XrttEcsfbSwitch,
EmcBlindHoA1Switch, EmcInterFreqBlindHoSwitch,
EPlmnSwitch, ServiceReqInterFreqHoSwitch,
VoipHoControlSwitch, UtranUltraFlashCsfbSwitch,
GeranUltraFlashCsfbSwitch, RatLayerSwitch,
ServiceBasedMultiFreqHoSwitch, SrvccRatSteeringS-
witch, PsRatSteeringSwitch
Default Value: IntraFreqCoverHoSwitch:On,
InterFreqCoverHoSwitch:On, UtranCsfbSwitch:Off,
GeranCsfbSwitch:Off, Cdma1xRttCsfbSwitch:Off,
UtranServiceHoSwitch:Off, GeranServiceHoS-
witch:Off, CdmaHrpdServiceHoSwitch:Off,
Cdma1xRttServiceHoSwitch:Off, UlQualityInterRA-
THoSwitch:Off, InterPlmnHoSwitch:Off,
UtranFlashCsfbSwitch:Off, GeranFlashCsfbS-
witch:Off, ServiceBasedInterFreqHoSwitch:Off,
UlQualityInterFreqHoSwitch:Off,
CsfbAdaptiveBlindHoSwitch:Off,
UtranCsfbSteeringSwitch:Off, GeranCsfbSteeringS-
witch:Off, CSFBLoadInfoSwitch:Off,
Cdma1XrttEcsfbSwitch:Off,
EmcBlindHoA1Switch:Off, EmcInterFreqBlindHoS-
witch:Off, EPlmnSwitch:Off, ServiceReqInterFreq-
HoSwitch:Off, VoipHoControlSwitch: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.
LOFD-0 UtranSepOpMobilitySwitch is an option used to
LST 01033 Steering
ENODE to control whether operators can adopt different mobility
BALGO LOFD-0 UTRAN policies on their UTRANs. If this option is selected,
SWITC 01052 operators can adopt different policies (such as PS
CS handover capability and RIM-based system
H LOFD-0
Fallback information reading capability) on their UTRANs. If
01068
to this option is deselected, operators cannot adopt
LOFD-0 UTRAN different policies on their UTRANs. This option
01088 applies only to LTE FDD.
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
LOFD-0
70216 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
Separate
Mobility
Policies
to
UTRAN
for
Multi
PLMN
UtranNF CsPriori ADD LOFD-0 E- Meaning: Indicates the priority for the UTRAN
req ty UTRAN 01078 / UTRAN frequency to carry CS services. During CSFB-based
NFREQ TDLOF to CS service handovers with UtranFreqLayerMeasS-
MOD D-00107 UTRAN witch selected, the eNodeB selects the neighboring
UTRAN 8 CS/PS UTRAN frequencies based on the CS priorities when
NFREQ LOFD-0 Steering starting measurements. The eNodeB preferentially
01033 / CS delivers the UTRAN frequency with the highest CS
LST priority to measure. During CSFB-based blind
UTRAN TDLOF Fallback
D-00103 to handovers with UtranFreqLayerBlindSwitch selected,
NFREQ the eNodeB selects the target cells for blind handovers
3 UTRAN
on neighboring UTRAN frequencies based on the CS
LOFD-0 Flash priorities and preferentially selects the target cell for
01052 / CS blind handovers on the neighboring UTRAN
TDLOF Fallback frequency with the highest CS priorities. If this
D-00105 to parameter is set to Priority_0, this neighboring
2 UTRAN UTRAN frequency is not prioritized. This parameter
LOFD-0 CS applies only to LTE FDD and LTE TDD.
01088 / Fallback GUI Value Range: Priority_0(Priority 0),
TDLOF Steering Priority_1(Priority 1), Priority_2(Priority 2),
D-00108 to Priority_3(Priority 3), Priority_4(Priority 4),
8 UTRAN 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)
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. If this parameter is set to UTRAN, GERAN,
G D-00103 UTRAN or CDMA2000, the highest-priority target RAT is
MOD 3 CS UTRAN, GERAN, or CDMA2000, respectively. This
CELLO LOFD-0 Fallback parameter applies only to LTE FDD and LTE TDD.
PHOCF 01034 / to GUI Value Range: UTRAN, GERAN, CDMA2000
G TDLOF GERAN Unit: None
LST D-00103 CS Actual Value Range: UTRAN, GERAN, CDMA2000
CELLO 4 Fallback
PHOCF to Default Value: UTRAN
LOFD-0
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
1xRTT
LOFD-0
Ultra-
70202 /
Flash
TDLOF
CSFB to
D-07020
UTRAN
2
Ultra-
LOFD-0
Flash
81283 /
CSFB to
TDLOF
GERAN
D-08120
3 CS
Fallback
TDLOF Steering
D-00108 to
8 UTRAN
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. This parameter applies
LST CS only to LTE FDD and LTE TDD.
CELLO 4 Fallback
PHOCF to GUI Value Range: UTRAN, GERAN, CDMA2000,
LOFD-0
G CDMA2 NULL
01035 /
TDLOF 000 Unit: None
D-00103 1xRTT Actual Value Range: UTRAN, GERAN, CDMA2000,
5 Flash NULL
LOFD-0 CS Default Value: GERAN
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
1xRTT
LOFD-0
Ultra-
70202 /
Flash
TDLOF
CSFB to
D-07020
UTRAN
2
Ultra-
LOFD-0
Flash
81283 /
CSFB to
TDLOF
GERAN
D-08120
3 CS
Fallback
TDLOF Steering
D-00108 to
8 UTRAN
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. This
LST CS parameter applies only to LTE FDD and LTE TDD.
CELLO 4 Fallback
PHOCF to GUI Value Range: UTRAN, GERAN, CDMA2000,
LOFD-0
G CDMA2 NULL
01035 /
TDLOF 000 Unit: None
D-00103 1xRTT Actual Value Range: UTRAN, GERAN, CDMA2000,
5 Flash NULL
LOFD-0 CS Default Value: CDMA2000
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
1xRTT
LOFD-0
Ultra-
70202 /
Flash
TDLOF
CSFB to
D-07020
UTRAN
2
Ultra-
LOFD-0
Flash
81283 /
CSFB to
TDLOF
GERAN
D-08120
3 CS
Fallback
TDLOF Steering
D-00108 to
8 UTRAN
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. This parameter applies only to LTE FDD
g POLIC D-00108 to and LTE TDD.
YCFG 8 UTRAN GUI Value Range: REDIRECTION, CCO_HO,
LST LOFD-0 CS PS_HO
CSFAL 01089 / Fallback Unit: None
LBACK TDLOF Steering
POLIC D-00108 to Actual Value Range: REDIRECTION, CCO_HO,
YCFG 9 GERAN PS_HO
to
GERAN
Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Mobility
Manage
ment
CS
Fallback
Steering
to
UTRAN
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. If this parameter
Pri PHOCF TDLOF to is set to UTRAN, GERAN, or CDMA2000, the
G D-00103 UTRAN highest-priority target RAT is UTRAN, GERAN, or
MOD 3 CS CDMA2000, respectively. This parameter applies only
CELLO LOFD-0 Fallback to LTE FDD and LTE TDD.
PHOCF 01034 / to GUI Value Range: UTRAN, GERAN, CDMA2000
G TDLOF GERAN Unit: None
LST D-00103 CS
4 Actual Value Range: UTRAN, GERAN, CDMA2000
CELLO Fallback
PHOCF LOFD-0 to Default Value: UTRAN
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-
TDLOF Flash
D-00108 CSFB to
8 UTRAN
Ultra-
Flash
CSFB to
GERAN
CS
Fallback
Steering
to
UTRAN
to
GERAN
Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Mobility
Manage
ment
CS
Fallback
Steering
to
UTRAN
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. This parameter applies only to
D-00103 LTE FDD and LTE TDD.
LST CS
CELLO 4 Fallback GUI Value Range: UTRAN, GERAN, CDMA2000,
PHOCF LOFD-0 to NULL
G 01035 / CDMA2 Unit: None
TDLOF 000 Actual Value Range: UTRAN, GERAN, CDMA2000,
D-00103 1xRTT NULL
5 PS Inter-
Default Value: GERAN
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-
TDLOF Flash
D-00108 CSFB to
8 UTRAN
Ultra-
Flash
CSFB to
GERAN
CS
Fallback
Steering
to
UTRAN
to
GERAN
Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Mobility
Manage
ment
CS
Fallback
Steering
to
UTRAN
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. This parameter applies only
D-00103 to LTE FDD and LTE TDD.
LST CS
CELLO 4 Fallback GUI Value Range: UTRAN, GERAN, CDMA2000,
PHOCF LOFD-0 to NULL
G 01035 / CDMA2 Unit: None
TDLOF 000 Actual Value Range: UTRAN, GERAN, CDMA2000,
D-00103 1xRTT NULL
5 PS Inter-
Default Value: CDMA2000
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-
TDLOF Flash
D-00108 CSFB to
8 UTRAN
Ultra-
Flash
CSFB to
GERAN
CS
Fallback
Steering
to
UTRAN
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 selected, 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-
LOFD-0 witch and UtranFreqLayerBlindSwitch are selected,
01033 / and
UTRAN the target cell is selected based on the priority
TDLOF specified by this parameter. The cell on the UTRAN
D-00103 CS frequency with the highest priority is preferentially
3 Fallback selected. If this parameter is set to Priority_0, the
TDLOF to UTRAN frequency is not included in priority
D-00105 UTRAN arrangement for neighboring UTRAN frequencies to
2 Flash carry CS+PS combined services. This parameter
LOFD-0 CS applies only to LTE FDD and LTE TDD.
01078 / Fallback GUI Value Range: Priority_0(Priority 0),
TDLOF to Priority_1(Priority 1), Priority_2(Priority 2),
D-00107 UTRAN Priority_3(Priority 3), Priority_4(Priority 4),
8 E- Priority_5(Priority 5), Priority_6(Priority 6),
UTRAN Priority_7(Priority 7), Priority_8(Priority 8),
to Priority_9(Priority 9), Priority_10(Priority 10),
UTRAN Priority_11(Priority 11), Priority_12(Priority 12),
CS/PS Priority_13(Priority 13), Priority_14(Priority 14),
steering 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)
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. This parameter applies
only to LTE FDD and LTE TDD.
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 FDD. The RSCP values are
m B1Meas RATHO TDLOF Mobility relatively stable while the Ec/N0 values fluctuate with
Quan COMM D-00101 between the network load. The value BOTH applies only to
LST 9 E- UEs complying with 3GPP Release 10. UEs
INTER LOFD-0 UTRAN complying with 3GPP Release 10 contain RSCP and
RATHO 01022 / and Ec/N0 in measurement reports. When both RSCP- and
COMM TDLOF UTRAN Ec/N0-based trigger conditions are met, handovers
D-00102 SRVCC can be triggered. For UEs complying with 3GPP
2 to Release 8 or 9, the value BOTH is equivalent to the
UTRAN value RSCP. QoE-based handover algorithms do not
LOFD-0 apply to UEs complying with 3GPP Release 8 and
01033 / CS Release 9, and the parameter value is fixed at ECN0.
TDLOF Fallback For details, see 3GPP TS 36.331. This parameter
D-00103 to applies only to LTE FDD and LTE TDD.
3 UTRAN
GUI Value Range: RSCP, ECN0, BOTH
LBFD-0 Mobility
02018 / Manage Unit: None
TDLBF ment Actual Value Range: RSCP, ECN0, BOTH
D-00201 Service Default Value: ECN0
8 based
LOFD-0 Inter-
01043 / RAT
TDLOF handove
D-00104 r to
3 UTRAN
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.
This parameter applies only to LTE FDD and LTE
TDD.
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. This
parameter applies only to LTE FDD and LTE TDD.
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
Cdma1xRttSrvccSwitch(Cdma1xRttSrvccSwitch),
UtranRedirectSwitch(UtranRedirectSwitch),
GeranRedirectSwitch(GeranRedirectSwitch),
CdmaHrpdRedirectSwitch(CdmaHrpdRedirectS-
witch),
Cdma1xRttRedirectSwitch(Cdma1xRttRedirectSwitch
), BlindHoSwitch(BlindHoSwitch),
LcsSrvccSwitch(LcsSrvccSwitch),
AutoGapSwitch(AutoGapSwitch),
UeVoipOnHspaCapSwitch(UeVoipOnHspaCapS-
witch),
UtranFddB1CapSwitch(UtranFddB1CapSwitch),
CdmaHrpdNonOptMeaHoS-
witch(CdmaHrpdNonOptMeaHoSwitch)
Unit: None
Actual Value Range: UtranVoipCapSwitch,
Cdma1xRttVoipCapSwitch, UtranPsHoSwitch,
GeranPsHoSwitch, CdmaHrpdNonOptimisedHoS-
witch, CdmaHrpdOptimisedHoSwitch,
GeranNaccSwitch, GeranCcoSwitch,
UtranSrvccSwitch, GeranSrvccSwitch,
Cdma1xRttSrvccSwitch, UtranRedirectSwitch,
GeranRedirectSwitch, CdmaHrpdRedirectSwitch,
Cdma1xRttRedirectSwitch, BlindHoSwitch,
LcsSrvccSwitch, AutoGapSwitch,
UeVoipOnHspaCapSwitch, UtranFddB1CapSwitch,
CdmaHrpdNonOptMeaHoSwitch
Default Value: UtranVoipCapSwitch:Off,
Cdma1xRttVoipCapSwitch:Off,
UtranPsHoSwitch:Off, GeranPsHoSwitch:Off,
CdmaHrpdNonOptimisedHoSwitch:Off,
CdmaHrpdOptimisedHoSwitch:Off,
GeranNaccSwitch:Off, GeranCcoSwitch:Off,
UtranSrvccSwitch:Off, GeranSrvccSwitch:Off,
Cdma1xRttSrvccSwitch:Off,
UtranRedirectSwitch:Off, GeranRedirectSwitch:Off,
CdmaHrpdRedirectSwitch:Off,
Cdma1xRttRedirectSwitch:Off, BlindHoSwitch:Off,
LcsSrvccSwitch:Off, AutoGapSwitch:Off,
UeVoipOnHspaCapSwitch:Off,
UtranFddB1CapSwitch:Off, CdmaHrpdNonOptMea-
HoSwitch:Off
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. This parameter applies only to
LOFD-0 CS LTE FDD and LTE TDD.
01033 / Fallback
TDLOF to GUI Value Range: -140~-43
D-00103 UTRAN Unit: dBm
3 CS Actual Value Range: -140~-43
LOFD-0 Fallback Default Value: -80
01034 / to
TDLOF GERAN
D-00103
4
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 LBFD-0 UTRAN eNodeB selects a target frequency based on this
0201803 and priority. If a measurement configuration is to be
LST UTRAN delivered, the eNodeB preferentially delivers a
UTRAN /
TDLBF Cell frequency with the highest priority. If this priority is
NFREQ set to 0 for a frequency, this frequency is not selected
D-00201 Selectio
803 n and as the target frequency for a blind redirection. A larger
Re- value indicates a higher priority. This parameter
TDLOF applies only to LTE FDD and LTE TDD.
D-00102 selection
2 SRVCC GUI Value Range: 0~8
TDLOF to Unit: None
D-00103 UTRAN Actual Value Range: 0~8
3 CS Default Value: 0
TDLOF Fallback
D-00105 to
2 UTRAN
LOFD-0 Flash
01043 / CS
TDLOF Fallback
D-00104 to
3 UTRAN
LOFD-0 Service
01072 / based
TDLOF Inter-
D-00107 RAT
2 handove
r to
LBFD-0 UTRAN
02018
Distance
based
Inter-
RAT
handove
r to
UTRAN
Mobility
Manage
ment
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 blind
ELL TDLOF Fallback
D-00102 redirections can be selected based on the measurement
LST to priorities of neighboring UTRAN cells. This
UTRAN 2 UTRAN parameter applies only to LTE FDD and LTE TDD.
NCELL LOFD-0
Flash GUI Value Range: 0~128
01033/
CS
TDLOF Unit: None
Fallback
D-00103 Actual Value Range: 0~128
to
3
UTRAN Default Value: 0
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
LOFD-0 r to
01019 / UTRAN
TDLOF PS Inter-
D-00101 RAT
9 Mobility
LOFD-0 between
01022 / E-
TDLOF UTRAN
D-00102 and
2 UTRAN
LOFD-0 SRVCC
01033 / to
TDLOF UTRAN
D-00103 CS
3 Fallback
LOFD-0 to
01052 / UTRAN
TDLOF Flash
D-00105 CS
2 Fallback
LBFD-0 to
02018 UTRAN
Mobility
Manage
ment
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-00101 between this priority set to HIGH_PRIORITY while delivering
UTRAN 9 E- a measurement configuration. This parameter applies
NCELL LOFD-0 UTRAN only to LTE FDD and LTE TDD.
01022 / and GUI Value Range: LOW_PRIORITY(Low Priority),
LST UTRAN
UTRAN TDLOF HIGH_PRIORITY(High Priority)
NCELL D-00102 SRVCC Unit: None
2 to
UTRAN Actual Value Range: LOW_PRIORITY,
LOFD-0 HIGH_PRIORITY
01033 / CS
TDLOF Fallback Default Value: LOW_PRIORITY(Low Priority)
D-00103 to
3 UTRAN
LOFD-0 Flash
01052 / CS
TDLOF Fallback
D-00105 to
2 UTRAN
LBFD-0 Mobility
02018 Manage
ment
CellUe MaxUtr MOD LOFD-0 PS Inter- Meaning: Indicates the maximum number of UTRAN
MeasCo anFddM CELLU 01019 / RAT FDD 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. This parameter applies
OLCFG 9 E- only to LTE FDD.
LST LOFD-0 UTRAN GUI Value Range: 1~16
CELLU 01022 / and
UTRAN Unit: None
EMEAS TDLOF
CONTR D-00102 SRVCC Actual Value Range: 1~16
OLCFG 2 to Default Value: 3
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
LBFD-0 CS
02018 / Fallback
TDLBF to
D-00201 UTRAN
8 Mobility
Manage
ment
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-00101 between specified neighboring cell. There are 32 priorities
UTRAN 9 E- altogether. The priority has a positive correlation with
NCELL LOFD-0 UTRAN the value of this parameter. Note that the value 0
01033 / and indicates that blind handovers to the neighboring cell
LST UTRAN are not allowed. This parameter applies only to LTE
UTRAN TDLOF
D-00103 CS FDD and LTE TDD.
NCELL
3 Fallback GUI Value Range: 0~32
LOFD-0 to Unit: None
01052 / UTRAN
Actual Value Range: 0~32
TDLOF Flash
D-00105 CS Default Value: 0
2 Fallback
to
UTRAN
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. This parameter
LST 3 applies only to LTE FDD and LTE TDD.
CELLH GUI Value Range: 60~1000
OPARA Unit: ms
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. This
um COMM D-00101 between parameter applies only to LTE FDD and LTE TDD.
LST 9 E- GUI Value Range: 1~16
INTER TDLOF UTRAN
and Unit: None
RATHO D-00105
COMM 2 UTRAN Actual Value Range: 1~16
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 an emergency CSFB-based
edirect COMM D-00103 UTRAN redirection procedure. This parameter applies only to
LST 3 Flash LTE FDD and LTE TDD.
INTER TDLOF CS GUI Value Range: 0~16
RATHO D-00105 Fallback Unit: None
COMM 2 to
UTRAN Actual Value Range: 0~16
Default Value: 0
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch
Default Value: RrcSetupOptSwitch:Off,
IucsRrcRecfgMcCombSwitch:Off,
RcrpRrcRecfgMcCombSwitch:Off,
RrcRecfgMcOptSwitch:Off, IdleCsfbRedirectOptS-
witch:Off, UlNasBufferSwitch:On,
IratMeasCfgTransSwitch:Off,
GeranAnrMcOptSwitch:Off, InactDiscardSwitch:Off,
SRVCCHoBasedUeCapSwitch:Off,
L2GPLMNChooseOptSwitch:Off,
HoInRrcRecfgMcCombSwitch:Off,
UeCapEnquiryCombSwitch:Off,
UeTraceOptSwitch:Off, PaDistributeMechOptS-
witch:On, InactReSyncCompatSwitch:Off,
VolteX2HoDelayOptSwitch:Off, UeUtranCapEnquir-
yOptSwitch:Off, FreqRandomOptSwitch:Off,
MrMdtMeasOptSwitch: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 Radio/ the same as that of an emergency call. For details
YCFG 3 transport about the ARP, see 3GPP TS 23.401. This parameter
LST LOFD-0 resource applies only to LTE FDD and LTE TDD.
CSFAL 0102901 pre- GUI Value Range: 1~15
LBACK / emption Unit: None
POLIC TDLOF
YCFG D-00102 Actual Value Range: 1~15
901 Default Value: 2
GlobalP UtranLo MOD TDLOF CS Meaning: Indicates the UMTS load transmission
rocSwitc adTrans GLOBA D-00103 Fallback channel. The eNodeB sends RAN-INFORMATION-
h Chan LPROC 3 to REQUEST PDUs to UTRAN cells to request multiple
SWITC UTRAN 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. This
LPROC parameter applies only to LTE FDD and LTE TDD.
SWITC GUI Value Range: NULL, BASED_ON_RIM,
H BASED_ON_ECO
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. This parameter applies only to
ENODE 2 tion LTE FDD and LTE TDD.
BALGO LOFD-0 Flash GUI Value Range: OFF(Off), ON(On)
SWITC 01019/ CS Unit: None
H TDLOF Fallback
to Actual Value Range: OFF, ON
D-00101
9 UTRAN Default Value: OFF(Off)
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
LOFD-0 Sharing
70203 to
UTRA
N(based
on
UMTS
cell load
informat
ion)
CS
Fallback
to
UTRAN
RIM
Based
LTE
Target
Cell
Selectio
n
GeranNf ConnFre ADD LOFD-0 PS Inter- Meaning: Indicates the frequency group priority used
reqGrou qPriority GERAN 01020 / RAT in selecting target groups for blind redirection and in
p NFREQ TDLOF Mobility delivering groups to measure. During blind
GROUP D-00102 between redirection, if no neighboring cell has been configured
MOD 0 E- to be suitable for blind handovers, the eNodeB selects
GERAN LOFD-0 UTRAN a target frequency group based on the priorities
NFREQ 01023 / and specified by this parameter. If this parameter is set to 0
GROUP TDLOF GERAN for a group, the eNodeB does not select this group for
D-00102 SRVCC blind redirection. During measurement configuration,
LST the eNodeB preferentially delivers the frequency
GERAN 3 to
GERAN group with the highest priority specified by this
NFREQ LOFD-0 parameter. The larger the parameter value, the higher
GROUP 01034 / CS the priority. This parameter applies only to LTE FDD
TDLOF Fallback and LTE TDD.
D-00103 to
4 GERAN GUI Value Range: 0~8
LOFD-0 Flash Unit: None
01053 / CS Actual Value Range: 0~8
TDLOF Fallback Default Value: 0
D-00105 to
3 GERAN
LBFD-0 Mobility
02018 Manage
ment
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 LOFD-0 UTRAN the value of this parameter. Note that the value 0
01023 / and indicates that blind handovers to the neighboring cell
LST GERAN are not allowed. This parameter applies only to LTE
GERAN TDLOF
D-00102 SRVCC FDD and LTE TDD.
NCELL
3 to GUI Value Range: 0~32
LOFD-0 GERAN Unit: None
01034 / CS Actual Value Range: 0~32
TDLOF Fallback
D-00103 to Default Value: 0
4 GERAN
LOFD-0 Flash
01053 / CS
TDLOF Fallback
D-00105 to
3 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. This
um COMM D-00102 between parameter applies only to LTE FDD and LTE TDD.
LST 0 E- GUI Value Range: 1~32
INTER TDLOF UTRAN
and Unit: None
RATHO D-00105
COMM 3 GERAN Actual Value Range: 1~32
Flash Default Value: 8
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. This parameter applies only to LTE
EXTER FDD and LTE TDD.
NALCE GUI Value Range: BOOLEAN_FALSE(False),
LL BOOLEAN_TRUE(True)
LST Unit: None
GERAN
Actual Value Range: BOOLEAN_FALSE,
EXTER
BOOLEAN_TRUE
NALCE
LL Default Value: BOOLEAN_TRUE(True)
GeranN Lac ADD LOFD-1 Separate Meaning: Indicates the location area code (LAC) of
etworkC GERAN 11204 Mobility the GERAN cell. It uniquely identifies a location
apCfg NETW Policies within a PLMN. A value in the range of 1-65533 and
ORKCA to 65535 indicates a specific LAC on the network, and
PCFG GERAN 4294967295 indicates all LACs under the PLMN.
LST for That is, the policy applies to all LACs under the
GERAN Multi PLMN. This parameter applies only to LTE FDD.
NETW PLMN GUI Value Range: 1~65533,65535,4294967295
ORKCA Unit: None
PCFG
Actual Value Range: 1~65533,65535,,4294967295
MOD
GERAN Default Value: None
NETW
ORKCA
PCFG
RMV
GERAN
NETW
ORKCA
PCFG
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 LBFD-0 GERAN measurement configurations to the UE. If this
RXPAR 02017 / DRX parameter is set to OFF, the eNodeB delivers only
A TDLBF gap-assisted GERAN measurement configurations to
D-00201 the UE. This parameter applies only to LTE FDD and
7 LTE TDD.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
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. This
parameter applies only to LTE FDD and LTE TDD.
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 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. This parameter
LBACK applies only to LTE FDD and LTE TDD.
HO GUI Value Range: -110~-48
Unit: dBm
Actual Value Range: -110~-48
Default Value: -103
GeranN NCellM ADD LOFD-0 Inter- Meaning: Indicates the measurement priority of the
cell easPriori GERAN 02002/ RAT neighboring GERAN cell. A larger value indicates a
ty NCELL TDLOF ANR higher priority. The measurement priorities can be
DSP D-00200 Flash periodically and automatically arranged based on the
GERAN 2 CS number of times that each neighboring GERAN cell is
EXTEN LOFD-0 Fallback measured. The neighboring GERAN cells for GERAN
DEDNC 01053/ to flash blind redirections or GERAN flash-CSFB-based
ELL TDLOF GERAN redirections can be selected based on the measurement
D-00105 priorities of neighboring GERAN cells. This
LST CS parameter applies only to LTE FDD and LTE TDD.
GERAN 3 Fallback
NCELL LOFD-0 to GUI Value Range: 0~128
01034 GERAN Unit: None
Actual Value Range: 0~128
Default Value: 0
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 an emergency CSFB-based
edirect COMM D-00103 GERAN redirection procedure. This parameter applies only to
LST 4 LTE FDD and LTE TDD.
INTER GUI Value Range: 0~32
RATHO Unit: None
COMM
Actual Value Range: 0~32
Default Value: 0
UtranEx Rac ADD LOFD-0 PS Inter- Meaning: Indicates the routing area code. This
ternalCe UTRAN 01019 / RAT parameter applies only to LTE FDD and LTE TDD.
ll EXTER TDLOF Mobility GUI Value Range: 0~255
NALCE D-00101 between
LL 9 E- Unit: None
CellOp CnOper ADD None None Meaning: Indicates the index of the operator. This
HoCfg atorId CELLO parameter applies only to LTE FDD and LTE TDD.
PHOCF GUI Value Range: 0~5
G
Unit: None
LST
CELLO Actual Value Range: 0~5
PHOCF Default Value: None
G
MOD
CELLO
PHOCF
G
RMV
CELLO
PHOCF
G
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. This parameter
HOCFG 3 SRVCC applies only to LTE FDD and LTE TDD.
LST LOFD-0 to GUI Value Range: OFF(Off), ON(On)
CSFAL 01022 UTRAN
Unit: None
LBACK LOFD-0 SRVCC
BLIND Actual Value Range: OFF, ON
01023 to
HOCFG GERAN Default Value: OFF(Off)
CellOp LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
HoCfg llId CELLO identifies a cell within an eNodeB. This parameter
PHOCF applies only to LTE FDD and LTE TDD.
G GUI Value Range: 0~255
LST Unit: None
CELLO
PHOCF Actual Value Range: 0~255
G Default Value: None
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 This parameter applies only to LTE FDD and LTE
BLIND D-00105 UTRAN TDD.
HOCFG 2 GUI Value Range: OFF(OFF), ON(ON)
Unit: None
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 TDLOF with
D-00103 Commo Unit: None
LST
CNOPE 6 n Actual Value Range: 0~5
RATOR MLOFD Carrier Default Value: None
MOD -121251 NB-IoT
CNOPE LOFD-0 RAN
RATOR 01037 / Sharing
TDLOF with
RMV Commo
CNOPE D-00103
7 n
RATOR Carrier
MLOFD
-121252 RAN
Sharing
LOFD-0 with
01086 / Dedicate
TDLOF d
D-00108 Carrier
6
NB-IoT
LOFD-0 RAN
70206 / Sharing
TDLOF with
D-08122 Dedicate
4 d
Carrier
RAN
Sharing
by More
Operator
s
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 an eNodeB. This parameter
LBACK applies only to LTE FDD and LTE TDD.
HO GUI Value Range: 0~255
MOD Unit: None
CSFAL
LBACK Actual Value Range: 0~255
HO Default Value: None
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 3GPP Release_R9(Release 9), Release_R10(Release 10),
102 R11 Release_R11(Release 11), Release_R12(Release 12),
Specific Release_R13(Release 13)
LBFD-0 ations
0300103 Unit: None
/ Actual Value Range: Release_R8, Release_R9,
TDLBF Release_R10, Release_R11, Release_R12,
D-00300 Release_R13
103
Default Value: Release_R8(Release 8)
LBFD-0
01008 /
TDLBF
D-07011
1
S1 MmeRel ADD S1 LBFD-0 Star Meaning: Indicates the compliance protocol release of
ease MOD 0300101 Topolog the MMEs to which the eNodeB is connected through
S1 / y the S1 interfaces under this S1 object. This parameter
TDLBF Chain applies only to LTE FDD and LTE TDD.
LST S1 D-00300 Topolog GUI Value Range: Release_R8(Release 8),
101 y Release_R9(Release 9), Release_R10(Release 10),
LBFD-0 Tree Release_R11(Release 11), Release_R12(Release 12),
0300102 Topolog Release_R13(Release 13)
/ y Unit: None
TDLBF
D-00300 3GPP Actual Value Range: Release_R8, Release_R9,
102 R11 Release_R10, Release_R11, Release_R12,
Specific Release_R13
LBFD-0 ations
0300103 Default Value: Release_R8(Release 8)
/
TDLBF
D-00300
103
LBFD-0
01008 /
TDLBF
D-07011
1
CSFallB CnOper LST LOFD-0 CS Meaning: Indicates the index of the operator. This
ackBlin atorId CSFAL 01033 / Fallback parameter applies only to LTE FDD and LTE TDD.
dHoCfg LBACK TDLOF to GUI Value Range: 0~5
BLIND D-00103 UTRAN
HOCFG 3 Unit: None
CS
MOD LOFD-0 Fallback Actual Value Range: 0~5
CSFAL 01034 / to Default Value: None
LBACK TDLOF GERAN
BLIND D-00103 Flash
HOCFG 4 CS
LOFD-0 Fallback
01052 / to
TDLOF UTRAN
D-00105 Flash
2 CS
LOFD-0 Fallback
01053 / to
TDLOF GERAN
D-00105 CS
3 Fallback
LOFD-0 to
01035 / CDMA2
TDLOF 000
D-00103 1xRTT
5 Enhance
LOFD-0 d CS
01090 / Fallback
TDLOF to
D-00109 CDMA2
0 000
1xRTT
GeranEx Rac ADD LOFD-0 CS Meaning: Indicates the routing area code. This
ternalCe GERAN 01034 / Fallback parameter applies only to LTE FDD and LTE TDD.
ll EXTER LOFD-0 to GUI Value Range: 0~255
NALCE 01034 GERAN
LL Unit: None
LOFD-0 Flash
MOD 01053 / CS Actual Value Range: 0~255
GERAN TDLOF Fallback Default Value: 0
EXTER D-00105 to
NALCE 3 GERAN
LL LOFD-0 PS Inter-
LST 01020 / RAT
GERAN TDLOF Mobility
EXTER D-00102 between
NALCE 0 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. This parameter
HOCFG 4 SRVCC applies only to LTE FDD and LTE TDD.
LST LOFD-0 to GUI Value Range: OFF(Off), ON(On)
CSFAL 01023 GERAN Unit: None
LBACK
BLIND Actual Value Range: OFF, ON
HOCFG Default Value: OFF(Off)
CellDrx LongDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the long DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement. This parameter
orMeas RXPAR TDLOF CS applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: SF128(128 subframes), SF160(160
LST 3 to subframes), SF256(256 subframes), SF320(320
CELLD TDLBF GERAN subframes), SF512(512 subframes), SF640(640
RXPAR D-00201 DRX subframes), SF1024(1024 subframes), SF1280(1280
A 7 subframes), SF2048(2048 subframes), SF2560(2560
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. This
Meas RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: PSF1(1 PDCCH subframe),
LST 3 to PSF2(2 PDCCH subframes), PSF3(3 PDCCH
CELLD TDLBF GERAN subframes), PSF4(4 PDCCH subframes), PSF5(5
RXPAR D-00201 DRX PDCCH subframes), PSF6(6 PDCCH subframes),
A 7 PSF8(8 PDCCH subframes), PSF10(10 PDCCH
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. This
rMeas RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: PSF1(1 PDCCH subframe),
LST 3 to PSF2(2 PDCCH subframes), PSF3(3 PDCCH
CELLD TDLBF GERAN subframes), PSF4(4 PDCCH subframes), PSF5(5
RXPAR D-00201 DRX PDCCH subframes), PSF6(6 PDCCH subframes),
A 7 PSF8(8 PDCCH subframes), PSF10(10 PDCCH
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. This parameter applies only to LTE
A D-08120 Fallback FDD and LTE TDD.
LST 3 to GUI Value Range: PSF1(1 PDCCH subframes),
CELLD TDLBF GERAN PSF2(2 PDCCH subframes), PSF4(4 PDCCH
RXPAR D-00201 DRX subframes), PSF6(6 PDCCH subframes), PSF8(8
A 7 PDCCH subframes), PSF16(16 PDCCH subframes),
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. This
Meas RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: OFF(Off), ON(On)
LST 3 to
GERAN Unit: None
CELLD TDLBF
RXPAR D-00201 DRX Actual Value Range: OFF, ON
A 7 Default Value: OFF(Off)
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the short DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement. This parameter
orMeas RXPAR TDLOF CS applies only to LTE FDD and LTE TDD.
A D-08120 Fallback GUI Value Range: SF2(2 subframes), SF5(5
LST 3 to subframes), SF8(8 subframes), SF10(10 subframes),
CELLD TDLBF GERAN SF16(16 subframes), SF20(20 subframes), SF32(32
RXPAR D-00201 DRX subframes), SF40(40 subframes), SF64(64
A 7 subframes), SF80(80 subframes), SF128(128
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. This
rForMea RXPAR TDLOF CS parameter applies only to LTE FDD and LTE TDD.
s A D-08120 Fallback GUI Value Range: 1~16
LST 3 to
GERAN Unit: None
CELLD TDLBF
RXPAR D-00201 DRX Actual Value Range: 1~16
A 7 Default Value: 1
10 Counters
11 Glossary
12 Reference Documents
1. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"
2. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC); Stage 2"
3. VoLGA Forum Specifications
4. 3GPP TS 36.300, "E-UTRAN Overall description"
5. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access "
6. 3GPP TS 48.018, "General Packet Radio Service (GPRS); Base Station System (BSS) -
Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP) "
7. VoLGA Forum Specifications Inter-RAT Mobility Management in Connected Mode
8. Emergency Call
9. LCS
10. Interoperability Between GSM and LTE
11. Interoperability Between UMTS and LTE
12. RAN Sharing
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.
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 step 5.
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. This situation is used as an example in the
preceding figure.
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.
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.
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.
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 5: The RNC receives a CSFB request and prepares CS and PS resources.
Step 6: The eNodeB receives the handover command transferred over the core network and
sends it to the UE.
Step 7: The UE is handed over to the UTRAN.
Steps 8 to 13: 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 CSFB. Therefore, the ciphering
procedure is not required after the UE is handed over 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.
1. The UE sends the MME an 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 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. 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.
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.
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.
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.
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.
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. The MME and MSC
guarantee the proper procedure through special processing.
Step 3b: The BSC receives an SRVCC request and prepares CS resources.
Step 4: The eNodeB receives the handover command transferred over the core network and
sends it to the UE.
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 encryption
procedure is not required after the UE is transferred to the GERAN.
If the Fast Return to LTE feature is enabled on the GERAN side, the UE can quickly return to
the E-UTRAN when it completes the voice service on the GERAN. To achieve this, the
Channel Release message must contain E-UTRA frequency information, based on which the
UE selects a suitable E-UTRAN cell to camp on.
When IratMeasCfgTransSwitch is set to ON, the eNodeB filters LTE frequencies supported
by the UE based on the UE capability to obtain a frequency set. During the SRVCC, the
eNodeB sends a Handover Required message containing the frequency set to the BSC of the
target cell and provides reference for the UE to accelerate the return to the E-UTRAN after
the UE completes voice services on the GERAN.
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.
If redirection is used for CSFB for emergency calls, the Channel Request message that the UE
sends when accessing the GERAN contains the indication of a CS emergency call. The
GERAN will treat this call as a common CS emergency call.
For details about admission and preemption of emergency calls, see Emergency Call.
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.