CS Fallback (ERAN8.1 04)

eRAN
CS Fallback Feature Parameter

Description
Issue 04
Date 2015-12-30
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2015-12-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eRAN
CS Fallback Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 2
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between eNodeB Types.............................................................................................................................. 5
2 Overview......................................................................................................................................... 6
2.1 Overview........................................................................................................................................................................ 7
2.2 Benefits........................................................................................................................................................................... 7
2.3 Architecture.................................................................................................................................................................... 7
2.4 CSFB Mechanisms....................................................................................................................................................... 10
2.4.1 CSFB to UTRAN.......................................................................................................................................................10
2.4.2 CSFB to GERAN.......................................................................................................................................................11
3 CSFB to UTRAN.......................................................................................................................... 14
3.1 Overview...................................................................................................................................................................... 15
3.2 Feature Classification................................................................................................................................................... 16
3.2.1 Basic CSFB to UTRAN.............................................................................................................................................16
3.2.2 Flash CSFB to UTRAN............................................................................................................................................. 16
3.2.3 Ultra-Flash CSFB to UTRAN................................................................................................................................... 16
3.2.4 CS Fallback with LAI to UTRAN............................................................................................................................. 17
3.2.5 E-UTRAN to UTRAN CS Steering...........................................................................................................................18
3.2.6 CS Fallback Steering to UTRAN.............................................................................................................................. 19
3.2.7 Load-based CSFB to UTRAN................................................................................................................................... 21
3.3 Triggering Events......................................................................................................................................................... 21
3.4 Target Cell/Frequency Selection...................................................................................................................................22
3.5 Handover Decision....................................................................................................................................................... 27
3.5.1 Basic Handover Decision.......................................................................................................................................... 27
3.5.2 Flash Redirection Decision........................................................................................................................................28
3.6 Handover Execution..................................................................................................................................................... 29
3.6.1 Handover Policy Selection........................................................................................................................................ 29
3.6.2 Ultra-Flash CSFB to UTRAN................................................................................................................................... 31
3.6.3 Redirection-based CSFB Optimization for UEs in Idle Mode.................................................................................. 33
3.6.4 CSFB Admission Optimization for UEs in Idle Mode..............................................................................................33
Issue 04 (2015-12-30) Huawei Proprietary and Confidential ii

eRAN
3.7 RIM Procedure Between E-UTRAN and UTRAN...................................................................................................... 34

3.7.1 RIM Procedure Through the Core Network.............................................................................................................. 35
3.7.2 RIM Procedure Through the eCoordinator................................................................................................................36
4 CSFB to GERAN.......................................................................................................................... 38
4.1 Overview...................................................................................................................................................................... 39
4.2 Feature Classification................................................................................................................................................... 39
4.2.1 Basic CSFB to GERAN.............................................................................................................................................39
4.2.2 Flash CSFB to GERAN............................................................................................................................................. 40
4.2.3 CS Fallback with LAI to GERAN............................................................................................................................. 40
4.2.4 CS Fallback Steering to GERAN.............................................................................................................................. 40
4.2.5 Ultra-Flash CSFB to GERAN................................................................................................................................... 41
4.3 Triggering Events......................................................................................................................................................... 42
4.4 Target Cell/Frequency Selection...................................................................................................................................42
4.5 Handover Decision....................................................................................................................................................... 43
4.6 Handover Execution..................................................................................................................................................... 43
4.7 RIM Procedure Between E-UTRAN and GERAN...................................................................................................... 45
5 Related Features...........................................................................................................................47
5.1 Features Related to LOFD-001033 CS Fallback to UTRAN....................................................................................... 47
5.2 Features Related to LOFD-001052 Flash CS Fallback to UTRAN............................................................................. 47
5.3 Features Related to LOFD-070202 Ultra-Flash CSFB to UTRAN..............................................................................48
5.4 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN....................................................................... 48
5.5 Features Related to LOFD-001088 CS Fallback Steering to UTRAN.........................................................................49
5.6 Features Related to LOFD-001078 E-UTRAN to UTRAN CS/PS Steering............................................................... 49
5.7 Features Related to LOFD-001034 CS Fallback to GERAN....................................................................................... 50
5.8 Features Related to LOFD-001053 Flash CS Fallback to GERAN............................................................................. 50
5.9 Feature Related to LOFD-081283 Ultra-Flash CSFB to GERAN............................................................................... 51
5.10 Features Related to LOFD-001069 CS Fallback with LAI to GERAN..................................................................... 51
5.11 Features Related to LOFD-001089 CS Fallback Steering to GERAN.......................................................................51
6 Network Impact........................................................................................................................... 53
6.1 LOFD-001033 CS Fallback to UTRAN....................................................................................................................... 53
6.2 LOFD-001052 Flash CS Fallback to UTRAN............................................................................................................. 54
6.3 LOFD-070202 Ultra-Flash CSFB to UTRAN..............................................................................................................54
6.4 LOFD-001068 CS Fallback with LAI to UTRAN....................................................................................................... 55
6.5 LOFD-001088 CS Fallback Steering to UTRAN.........................................................................................................55
6.6 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering............................................................................................... 55
6.7 LOFD-001034 CS Fallback to GERAN....................................................................................................................... 56
6.8 LOFD-001053 Flash CS Fallback to GERAN............................................................................................................. 56
6.9 LOFD-081283 Ultra-Flash CSFB to GERAN..............................................................................................................57
6.10 LOFD-001069 CS Fallback with LAI to GERAN..................................................................................................... 57
6.11 LOFD-001089 CS Fallback Steering to GERAN.......................................................................................................57
7 Engineering Guidelines............................................................................................................. 59
Issue 04 (2015-12-30) Huawei Proprietary and Confidential iii

eRAN
7.1 LOFD-001033 CS Fallback to UTRAN....................................................................................................................... 59

7.1.1 When to Use CS Fallback to UTRAN.......................................................................................................................59
7.1.2 Required Information................................................................................................................................................ 59
7.1.3 Requirements............................................................................................................................................................. 60
7.1.4 Precautions.................................................................................................................................................................61
7.1.5 Data Preparation and Feature Activation...................................................................................................................61
7.1.5.1 Data Preparation..................................................................................................................................................... 61
7.1.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................66
7.1.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 67
7.1.5.4 Using the CME to Perform Single Configuration.................................................................................................. 68
7.1.5.5 Using MML Commands......................................................................................................................................... 69
7.1.6 Activation Observation..............................................................................................................................................72
7.1.7 Deactivation...............................................................................................................................................................78
7.1.8 Performance Monitoring............................................................................................................................................79
7.1.9 Parameter Optimization............................................................................................................................................. 80
7.2 RIM Procedure from E-UTRAN to UTRAN............................................................................................................... 84
7.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN...................................................................................... 84
7.2.3 Requirements............................................................................................................................................................. 84
7.2.4 Precautions.................................................................................................................................................................85
7.2.6 Activation Observation..............................................................................................................................................88
7.2.7 Deactivation...............................................................................................................................................................89
7.2.8 Performance Monitoring............................................................................................................................................90
7.2.9 Parameter Optimization............................................................................................................................................. 90
7.3 LOFD-001052 Flash CS Fallback to UTRAN............................................................................................................. 90
7.3.1 When to Use Flash CS Fallback to UTRAN............................................................................................................. 91
7.3.3 Requirements............................................................................................................................................................. 92
7.3.4 Precautions.................................................................................................................................................................92
7.3.6 Activation Observation............................................................................................................................................100
Issue 04 (2015-12-30) Huawei Proprietary and Confidential iv

eRAN
7.3.7 Deactivation.............................................................................................................................................................101
7.3.8 Performance Monitoring..........................................................................................................................................102
7.3.9 Parameter Optimization........................................................................................................................................... 102
7.4 LOFD-070202 Ultra-Flash CSFB to UTRAN............................................................................................................102
7.4.1 When to Use Ultra-Flash CSFB.............................................................................................................................. 102
7.4.2 Required Information.............................................................................................................................................. 102
7.4.3 Requirements........................................................................................................................................................... 102
7.4.4 Precautions...............................................................................................................................................................103
7.4.5 Data Preparation and Feature Activation.................................................................................................................103
7.4.5.1 Data Preparation................................................................................................................................................... 103
7.4.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................105
7.4.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................. 106
7.4.5.4 Using the CME to Perform Single Configuration................................................................................................ 107
7.4.5.5 Using MML Commands....................................................................................................................................... 108
7.4.7 Deactivation............................................................................................................................................................. 112
7.5 LOFD-001068 CS Fallback with LAI to UTRAN..................................................................................................... 113
7.5.1 When to Use CS Fallback with LAI to UTRAN..................................................................................................... 113
7.5.2 Required Information...............................................................................................................................................113
7.5.3 Requirements........................................................................................................................................................... 114
7.5.4 Precautions...............................................................................................................................................................115
7.5.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs..............................................................115
7.5.6 Activation Observation............................................................................................................................................ 115
7.5.7 Deactivation............................................................................................................................................................. 116
7.6 LOFD-001088 CS Fallback Steering to UTRAN.......................................................................................................116
7.6.1 When to Use CS Fallback Steering to UTRAN.......................................................................................................117
7.6.2 Required Information...............................................................................................................................................117
7.6.3 Requirements........................................................................................................................................................... 117
7.6.4 Precautions...............................................................................................................................................................118
Issue 04 (2015-12-30) Huawei Proprietary and Confidential v

eRAN

7.6.7 Deactivation.............................................................................................................................................................126
7.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering............................................................................................. 127
7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering............................................................................................. 127
7.7.3 Requirements........................................................................................................................................................... 128
7.7.4 Precautions...............................................................................................................................................................128
7.7.7 Deactivation.............................................................................................................................................................133
7.8 LOFD-001034 CS Fallback to GERAN..................................................................................................................... 134
7.8.1 When to Use CS Fallback to GERAN.....................................................................................................................134
7.8.3 Requirements........................................................................................................................................................... 135
7.8.4 Precautions...............................................................................................................................................................136
7.8.5.5 Using Feature Operation and Maintenance on the CME......................................................................................143
7.8.7 Deactivation.............................................................................................................................................................155
7.9 RIM Procedure from E-UTRAN to GERAN............................................................................................................. 158
7.9.1 When to Use RIM Procedure Between E-UTRAN and GERAN............................................................................159
7.9.3 Requirements........................................................................................................................................................... 159
7.9.4 Precautions...............................................................................................................................................................160
Issue 04 (2015-12-30) Huawei Proprietary and Confidential vi

eRAN

7.9.7 Deactivation.............................................................................................................................................................164
7.10 LOFD-001053 Flash CS Fallback to GERAN......................................................................................................... 165
7.10.1 When to Use Flash CS Fallback to GERAN......................................................................................................... 165
7.10.2 Required Information............................................................................................................................................ 166
7.10.3 Requirements......................................................................................................................................................... 166
7.10.4 Precautions.............................................................................................................................................................167
7.10.5 Data Preparation and Feature Activation...............................................................................................................167
7.10.5.1 Data Preparation................................................................................................................................................. 167
7.10.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..............................................171
7.10.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs........................................................... 173
7.10.5.4 Using the CME to Perform Single Configuration.............................................................................................. 174
7.10.5.5 Using MML Commands..................................................................................................................................... 174
7.10.6 Activation Observation..........................................................................................................................................175
7.10.7 Deactivation...........................................................................................................................................................176
7.10.8 Performance Monitoring........................................................................................................................................177
7.10.9 Parameter Optimization......................................................................................................................................... 177
7.11 LOFD-081283 Ultra-Flash CSFB to GERAN..........................................................................................................177
7.11.1 When to Use This Feature..................................................................................................................................... 177
7.11.2 Required Information.............................................................................................................................................177
7.11.3 Requirements......................................................................................................................................................... 178
7.11.4 Precautions.............................................................................................................................................................178
7.11.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................183
7.11.6 Activation Observation.......................................................................................................................................... 185
7.11.7 Deactivation........................................................................................................................................................... 186
7.12 LOFD-001069 CS Fallback with LAI to GERAN................................................................................................... 188
7.12.1 When to Use CS Fallback with LAI to GERAN................................................................................................... 188
Issue 04 (2015-12-30) Huawei Proprietary and Confidential vii

eRAN

7.12.3 Requirements......................................................................................................................................................... 189
7.12.4 Precautions.............................................................................................................................................................190
7.12.7 Deactivation...........................................................................................................................................................191
7.13 LOFD-001089 CS Fallback Steering to GERAN.....................................................................................................191
7.13.1 When to Use CS Fallback Steering to GERAN.................................................................................................... 191
7.13.3 Requirements......................................................................................................................................................... 192
7.13.4 Precautions.............................................................................................................................................................192
7.13.7 Deactivation...........................................................................................................................................................199
7.14 Troubleshooting........................................................................................................................................................ 200
7.14.1 CSFB Calling Procedure Failure........................................................................................................................... 200
7.14.2 eNodeB Receiving No Measurement Report........................................................................................................ 201
7.14.3 CSFB Blind Handover Failure.............................................................................................................................. 201
7.14.4 CSFB Handover Failure........................................................................................................................................ 202
8 Parameters................................................................................................................................... 204
9 Counters...................................................................................................................................... 254
10 Glossary..................................................................................................................................... 313
11 Reference Documents............................................................................................................. 314
12 Appendix................................................................................................................................... 315
12.1 CSFB to UTRAN......................................................................................................................................................315
12.1.1 Combined EPS/IMSI Attach Procedure................................................................................................................ 315
Issue 04 (2015-12-30) Huawei Proprietary and Confidential viii

eRAN
12.1.2 CSFB Based on PS Handover............................................................................................................................... 316

12.1.3 Signaling procedure of redirection to CDMA2000 1xRTT...................................................................................318
12.1.4 Flash CSFB............................................................................................................................................................320
12.1.5 Ultra-Flash CSFB to UTRAN............................................................................................................................... 321
12.1.6 Redirection-based CSFB Optimization for UEs in Idle Mode.............................................................................. 323
12.1.7 CSFB for SMS.......................................................................................................................................................324
12.1.8 Emergency Call..................................................................................................................................................... 324
12.1.9 CSFB for LCS....................................................................................................................................................... 325
12.2 CSFB to GERAN......................................................................................................................................................325
12.2.1 Combined EPS/IMSI Attach Procedure................................................................................................................ 325
12.2.2 CSFB Based on PS Handover............................................................................................................................... 325
12.2.3 CSFB Based on CCO/NACC................................................................................................................................ 327
12.2.4 CSFB Based on Redirection.................................................................................................................................. 328
12.2.5 Flash CSFB............................................................................................................................................................330
12.2.6 Ultra-Flash CSFB to GERAN............................................................................................................................... 331
12.2.7 CSFB for SMS.......................................................................................................................................................334
12.2.8 Emergency Call..................................................................................................................................................... 334
12.2.9 CSFB for LCS....................................................................................................................................................... 334
Issue 04 (2015-12-30) Huawei Proprietary and Confidential ix

eRAN
CS Fallback Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes circuit switched fallback (CSFB), including its technical principles,
related features, network impact, and engineering guidelines.
This document covers the following features:
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
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 GERAN: CS Fallback Feature Parameter Description in GBSS Feature Documentation.
l UTRAN: Interoperability Between UMTS and LTE Feature Parameter Description in
RAN Feature Documentation.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.
Issue 04 (2015-12-30) Huawei Proprietary and Confidential 1

eRAN
eNodeB Type Model
Macro 3900 series eNodeB
Micro BTS3202E
BTS3203E
LampSite DBS3900
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN 8.1 04 (2015-12-30)

This issue includes the following changes.
Change Change Description Parameter Change Affecte

Type d Entity
Feature None None None

change
Editorial Optimized the descriptions throughout None -

change this document.
eRAN8.1 03 (2015-08-31)

eRAN
Change Change Description Parameter Change Affecte

Type d Entity
Feature None None None

change
Editorial Revised descriptions in this document None -

change and adjusted the document structure.
eRAN8.1 02 (2015-06-30)
Change Change Description Parameter Change Affected

Type Entity
Feature Added the measurement-specific None Macro,

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

optimization switch for CSFB. For RsvdSwPara1_bit23 micro, and
details, see 3.4 Target Cell/ option in the reserved LampSite
Frequency Selection and 7.1.5.1 parameter eNodeBs
Data Preparation. eNBRsvdPara.
RsvdSwPara1.
Editorial None None -

change
eRAN8.1 01 (2015-03-23)
Change Type Change Description Parameter Affected Entity

Change
Feature change Added the UE compatibility Added the Macro, micro,

risk optimization for ultra-flash UltraFlashCsfbC and LampSite
CSFB. For details, see 7.11.5.1 omOptSw option eNodeBs
Data Preparation. to the
GlobalProcSwitc
h.UeCompatSwitc
h parameter.
Editorial None None -

change

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

Compared with Issue 06 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1
includes the following changes.
Chang Change Description Parameter Affected

e Type Change Entity
Feature Supported the cell-level blind handling switch for Added the Macro,
change CSFB in CS Fallback to UTRAN or GERAN and CellHoParaCf micro,
Flash CS Fallback to UTRAN or GERAN g.HoModeSwit and
scenarios. ch parameter. LampSite
l For details about the switch, see 3.2.1 Basic eNodeBs
CSFB to UTRAN and 3.4 Target Cell/
Frequency Selection.
l For details about handover policy selection,
see 3.6.1 Handover Policy Selection.
l For details about scenario-specific parameter
preparations, see section "Data Preparation" in
engineering guidelines.
l For details about scenario-specific
configurations, see "Using the CME to
Perform Batch Configuration for Newly
Deployed eNodeBs" and "Using MML
Commands" in section "Activation" in
engineering guidelines.
Added the feature LOFD-081283 Ultra-Flash l Added the Macro,

CSFB to GERAN. GeranExte micro,
l For details about the feature description, see rnalCell.Ul and
4.2.5 Ultra-Flash CSFB to GERAN. traFlashCs LampSite
fbInd eNodeBs
l For details about the signaling procedure, see parameter.
12.2.6 Ultra-Flash CSFB to GERAN.
l Added the
l For details about related features and network GeranUltr
impact, see 5.9 Feature Related to aFlashCsfb
LOFD-081283 Ultra-Flash CSFB to Switch
GERAN and 6.9 LOFD-081283 Ultra-Flash option in
CSFB to GERAN. the
l For details about engineering guidelines, see ENodeBAl
7.11 LOFD-081283 Ultra-Flash CSFB to goSwitch.
GERAN. HoAlgoSwi
tch
parameter.

eRAN
Chang Change Description Parameter Affected

e Type Change Entity
Added the configuration of the round-robin Added the Macro,

function for L2U blind redirections. CSFallBackBl micro,
l For details about the switch, see 3.4 Target indHoCfg.Utr and
Cell/Frequency Selection. anCsfbBlindR LampSite
edirRrSw eNodeBs
l For details about scenario-specific data parameter.
preparations, see 7.1.5.1 Data Preparation.
l For details about the function activation, see
7.1.5.5 Using MML Commands.
Added SPID-based mobility management. For None Macro,

details about the function, see 3.4 Target Cell/ micro,
Frequency Selection, 3.5.1 Basic Handover and
Decision, and 3.5.2 Flash Redirection Decision. LampSite
eNodeBs
Ultra-flash CSFB to GERAN uses the DRX- Added the Macro,

based measurement, which is controlled by the CellDrxPara. micro,
CellDrxPara.DrxForMeasSwitch parameter. DrxForMeasS and
l For details about the parameter, see 4.2.5 witch LampSite
Ultra-Flash CSFB to GERAN. parameter. eNodeBs
l For details about data preparations and MML
configurations, see related sections in 7.11
LOFD-081283 Ultra-Flash CSFB to
GERAN.
Editoria Changed "blind handling" to "blind handover". None -

l change For details, see descriptions of blind handover in
this document.
1.4 Differences Between eNodeB Types

The features described in this document are implemented in the same way on macro, micro,
and LampSite eNodeBs.

eRAN
CS Fallback Feature Parameter Description 2 Overview
2 Overview
In an early phase of 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 E-UTRAN UEs. After the technological
maturity, industry chain, and deployment costs of the two methods are well weighed, CSFB is
chosen to serve as an interim solution for voice service access before mature commercial use
of IMS.

eRAN
2.1 Overview
With the CSFB solution, when a UE initiates a CS service, the mobility management entity
(MME) instructs the UE to fall back to the legacy CS network before the UE performs the
service. CSFB is a session setup procedure. UEs fall back to CS networks before CS sessions
are set up, and they always stay in the CS networks during the CS sessions. For details, see
3GPP TS 23.272 V8.5.0.
The eNodeB handles the CSFB for different types of CS services in a uniform way such as the
voice service, SMS, LCS, and emergency calls.
2.2 Benefits
CSFB brings the following benefits:
l Facilitates voice services for the LTE network.

l Helps operators reduce costs by reusing legacy CS networks and not deploying an IMS
network.
2.3 Architecture
CSFB is applicable to scenarios where the CS network of the UTRAN/GERAN has the same
or larger coverage area than that of the E-UTRAN.
Figure 2-1 shows the network architecture for CSFB to UTRAN/GERAN.
Figure 2-1 Network architecture for CSFB to UTRAN/GERAN
Table 2-1 describes the elements of the network architecture in Figure 2-1.

eRAN
Table 2-1 Elements of the network architecture for CSFB to UTRAN/GERAN

NE Function
SGs interface l Is an interface between the MME and the 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.
UE l Is capable of accessing the EPS and accessing the UTRAN,

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

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

l Forwards paging messages transmitted through the SGs interface.

eRAN
NE Function
E-UTRAN l Forwards paging messages related to CSFB.

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

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

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

eCoordinator supports the RIM procedure.
To implement CSFB to provide CS services for UEs on the E-UTRAN, all mobile switching
centers (MSCs) that serve overlapping areas with the E-UTRAN coverage must be upgraded
to support functions involving the SGs interface. The SGs interface is between an MSC and a
mobility management entity (MME), and functions involving the SGs interface include
combined attach, combined TAU/LAU (TAU is short for tracking area update, and LAU is
short for location area update), paging, and SMS. If the live network uses an MSC pool, only
one or multiple MSCs in the MSC pool need to be upgraded to support the SGs interface.

eRAN
2.4 CSFB Mechanisms
2.4.1 CSFB to UTRAN

Based on the capabilities of UEs and networks, three fallback mechanisms are available for an
eNodeB to perform CSFB to UTRAN:
l R8 PS Redirection
After receiving a CS Fallback Indicator, the eNodeB sends an RRC Connection Release
message containing frequency information about the target UTRAN to the UE. Based on the
received frequency information, the UE searches for a UTRAN cell, obtains the system
information of the UTRAN cell, and initiates initial access and CS services.
l R9 PS Redirection (Flash CSFB)
After receiving a CS Fallback Indicator, the eNodeB sends an RRC Connection Release
message containing information about a target UTRAN frequency as well as system
information about multiple target cells to the UE. Based on the received frequency
information, the UE searches for a UTRAN cell. As the UE obtains system information about
the target cell, the UE initiates initial access and CS services in the target cell, thereby
reducing voice delay.
l PS Handover
The UE is handed over to the UMTS network through the PS handover procedure between the
eNodeB and the UMTS network. After the handover, the UE initiates CS services in the target
cell.
Table 2-2 describes the requirements of the three CSFB mechanisms on the network side and
UEs.
Table 2-2 Requirements of CSFB to UTRAN on the network side and UEs
NE R8 PS Redirection R9 Redirection (Flash PS Handover

CSFB)
UE l Support combined l Support R9 PS l Support PS

EPS/CS attach and Redirection with SIB. Handover.
combined TA/LA l The other l The other
update. requirements are the requirements are
l Support CSFB by R8 same as those of R8 the same as those
PS Redirection. PS Redirection. of R8 PS
Redirection.
eNodeB Support CSFB by R8 PS l Support the RIM Support PS Handover.

Redirection. procedure.
l The other
requirements are the
same as those of R8
PS Redirection.

eRAN
NE R8 PS Redirection R9 Redirection (Flash PS Handover

CSFB)
UTRAN N/A Support the RIM Support PS Handover.

procedure.
MME l Support combined l Support the RIM Support PS Handover.

EPS/CS attach and procedure.
combined TA/LA l The other
update. requirements are the
l Support the CSFB same as those of R8
procedure. PS Redirection.
SGSN N/A Support the RIM Support PS Handover.

procedure.
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 TA/LA Redirection. R8 PS Redirection.
update.
l Support the CSFB
procedure.
2.4.2 CSFB to GERAN

Based on the capabilities of UEs and networks, five fallback mechanisms are available for an
eNodeB to perform CSFB to GERAN:
l R8 PS Redirection
For details, see 2.4.1 CSFB to UTRAN.
l R9 PS Redirection (Flash CSFB)
l CCO
After receiving a CS Fallback Indicator, the eNodeB sends a MobilityFromEUTRACommand
message containing information about a target GERAN cell to the UE, and instructs the UE to
access the target cell. The UE needs to be synchronized to the specified cell, obtains system
information about the target cell, and accesses the cell to initiate CS services.
l CCO with NACC
When the LTE-to-GSM RIM procedure is enabled, which indicates that NACC is enabled, the
eNodeB delivers system information about the target cell when triggering CCO. The UE
directly initiates access and a CS service to the target cell and does not need to read system
information about the target cell, shortening delays.
l PS Handover
Table 2-3 describes the requirements of the five CSFB mechanisms on the network side and
UEs.

eRAN
Table 2-3 Requirements of CSFB to GERAN on the network side and UEs
NE R8 PS R9 Redirection CCO CCO with PS
Redirection (Flash CSFB) NACC Handover
UE l Support l Support R9 l Support l Support l Support

combined PS CCO. NACC PS
EPS/CS Redirection l The l The Handov
attach and with SIB. other other er.
combined l The other require requirem l The
TA/LA requirements ments ents are other
update. are the same are the the same require
l Support as those of same as as those ments
CSFB by R8 PS those of of R8 PS are the
R8 PS Redirection. R8 PS Redirecti same as
Redirection. Redirect on. those of
ion. R8 PS
Redirect
ion.
eNodeB Support CSFB l Support the Support l Support Support PS

by R8 PS RIM CCO. the RIM Handover.
Redirection. procedure. procedur
l The other e.
requirements l The
are the same other
as those of requirem
R8 PS ents are
Redirection. the same
as those
of R8 PS
Redirecti
on.
GERAN N/A Support the RIM N/A Support the Support PS

procedure. RIM Handover.
procedure.
MME l Support l Support the The l Support Support PS

combined RIM requiremen the RIM Handover.
EPS/CS procedure. ts are the procedur
attach and l The other same as e.
combined requirements those of R8 l The
TA/LA are the same PS other
update. as those of Redirection requirem
l Support the R8 PS . ents are
CSFB Redirection. the same
procedure. as those
of R8 PS
Redirecti
on.

eRAN
NE R8 PS R9 Redirection CCO CCO with PS

Redirection (Flash CSFB) NACC Handover
SGSN N/A Support the RIM N/A Support the Support PS

procedure. RIM Handover.
procedure.
MSC l Support The The The The

combined requirements are requiremen requirement requiremen
EPS/CS the same as ts are the s are the ts are the
attach and those of R8 PS same as same as same as
combined Redirection. those of R8 those of R8 those of R8
TA/LA PS PS PS
update. Redirection Redirection. Redirection
l Support the . .
CSFB
procedure.

eRAN
CS Fallback Feature Parameter Description 3 CSFB to UTRAN
3 CSFB to UTRAN
This chapter describes each CSFB to UTRAN feature, CSFB procedure, and RIM procedure
between E-UTRAN and UTRAN.

eRAN
3.1 Overview
CSFB to UTRAN can be implemented in different ways and includes the following features/
functions:
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-001078 E-UTRAN to UTRAN CS/PS Steering
l LOFD-001088 CS Fallback Steering to UTRAN
l Load-based CSFB to UTRAN
CSFB Procedure
Figure 3-1 shows the CSFB to UTRAN procedure.
Figure 3-1 CSFB to UTRAN procedure
Measurement and Blind Handover

The eNodeB determines whether to trigger UTRAN measurements or blind handling for
CSFB to UTRAN based on the status of the blind handling switch first.

eRAN
l If this option is selected, the eNodeB triggers blind handover directly.

l If this option is cleared, the eNodeB determines whether to trigger inter-RAT
measurements or blind handover based on the UE capability:
If the UE supports UTRAN measurements, the eNodeB triggers inter-RAT
measurements.
If the UE does not support UTRAN measurements, the eNodeB triggers a blind
handover.
For details about the measurement and handover, see Overview of Mobility Management in
Connected Mode Feature Parameter Description.
3.2 Feature Classification
3.2.1 Basic CSFB to UTRAN

This section describes the optional feature LOFD-001033 CS Fallback to UTRAN. The
UtranCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies
whether to enable this feature.
When a UE initiates a CS service in the E-UTRAN, the MME sends an S1-AP message
containing CS Fallback Indicator to the eNodeB, instructing the eNodeB to transfer the UE as
well as the CS service to a target network. For details about signaling procedures of MOC and
MTC, see 12.1 CSFB to UTRAN.
3.2.2 Flash CSFB to UTRAN

This section describes the optional feature LOFD-001052 Flash CS Fallback to UTRAN. The
UtranFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
specifies whether to enable this feature.
This feature is an enhancement to the optional feature LOFD-001033 CS Fallback to
UTRAN. When this feature is activated after enabled LOFD-001033 CS Fallback to UTRAN,
the eNodeB obtains the UTRAN cell information through the RIM procedures and then sends
the EUTRAN-to-UTRAN redirection message including the obtained UTRAN cell
information to the UE. In this case, the UE can access a UTRAN cell without obtaining
UTRAN cell information. This reduces the access delay. For details about how the UTRAN
cell information is delivered to the eNodeB through the RIM procedure, see Interoperability
Between UMTS and LTE Feature Parameter Description.
This feature requires that the eNodeB can obtain UTRAN cell information through the RIM
procedures and the networks and UEs involved must comply with 3GPP Release 9 or later.
For details about the RIM procedure, see 3.7 RIM Procedure Between E-UTRAN and
UTRAN.
Other procedures are the same as those in CSFB to UTRAN. For details, see 3.2.1 Basic
CSFB to UTRAN.
3.2.3 Ultra-Flash CSFB to UTRAN

This section describes the optional feature LOFD-070202 Ultra-Flash CSFB to UTRAN. The
UtranUltraFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
specifies whether to enable this feature. This feature is a Huawei-proprietary feature. To

eRAN
enable this feature, the MME, MSC, and RNC must be all provided by Huawei and support
this feature.
When a UE initiates a CS service setup request in an LTE cell that does not support VoIP, this
feature enables the eNodeB to hand over the UE to the UTRAN through the SRVCC
procedure. It prepares CS resources on the UTRAN in advance and omits unnecessary
signaling processes during UTRAN access, thereby shortening the access delay for CSFB by
1s and improving user experience significantly. Compared with the standard procedure, the
ultra-flash CSFB to UTRAN procedure for Huawei omits certain signaling processes. For
details, see 12.1.5 Ultra-Flash CSFB to UTRAN.
The measurement procedure and blind handover procedure for this feature are the same as
those in CSFB to UTRAN. For details, see 3.2.1 Basic CSFB to UTRAN.
NOTE
The following table describes the parameters that must be set in the GLOBALPROCSWITCH MO to
turn on the UE compatibility switch when UEs do not support Ultra-Flash CSFB, resulting in UE
compatibility problems.
3.2.4 CS Fallback with LAI to UTRAN

This section describes the optional feature LOFD-001068 CS Fallback with LAI to UTRAN.
This feature is under license control and is not controlled by a switch.
This feature mainly applies to the following scenarios:
l In a multi-PLMN or national roaming scenario
An LAI consists of a PLMN ID and a LAC. In the CSFB with LAI function, the PLMN
ID identifies the CS network that the UE has registered with and will fall back to after
fallback.
If the serving E-UTRAN cell has multiple neighboring UTRAN or GERAN cells with
different PLMN IDs or the serving PLMN differs from the target PLMN, the operator
can use CSFB with LAI to achieve CSFB to a PLMN of the LAI preferentially.
l In a tracking area (TA) that overlaps multiple location areas (LAs)
The eNodeB selects a CSFB target cell with the same LAC as that mapped to the
network to which the UE has attached. An LAU is not required after CSFB, and
therefore the CSFB delay does not include the LAU time.
The eNodeB obtains the value of the LAI from the MME using an Initial Context Setup Req
or UE Context Mod Req message.
UTRAN. With this feature, the eNodeB selects a target frequency or cell for measurement or
blind handover based on the LAI sent by the MME.
l In a measurement procedure, the eNodeB selects only an inter-RAT frequency on which
the PLMN ID of a neighboring cell is the same as that in the LAI received. The follow-
up measurement procedure is similar to that in CS Fallback to UTRAN. For details, see
3.4 Target Cell/Frequency Selection.
The difference is that the eNodeB sorts neighboring cells in the following order after
receiving measurement reports from a UE:
a. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
b. Neighboring cells with PLMN IDs the same as that in the LAI but LACs different
from that in the LAI

eRAN
If no frequency or neighboring cell can be selected based on the LAI, the processing is
the same as that when no LAI is received.
l In a blind handover procedure, the eNodeB first selects a target cell for blind handover.
If no neighboring UTRAN cell is configured, the eNodeB preferentially selects the
UTRAN frequencies whose PLMN ID is the same as that in the LAI. The follow-up
procedure is the same as that described in 3.4 Target Cell/Frequency Selection.
If neighboring UTRAN cells are configured, the eNodeB preferentially selects the
operating UTRAN frequencies of the neighboring UTRAN cells whose PLMN ID is the
same as that in the LAI. The eNodeB then sorts the frequencies based on the blind
handover priorities of the neighboring cells and frequency priorities for connected mode.
For details, see 3.4 Target Cell/Frequency Selection.
The eNodeB selects a target cell in the following order of preference:
a. Neighboring cell whose PLMN ID and LAC are the same as those in the LAI
b. If no neighboring cells described in a exist, the eNodeB selects the neighboring
cells with PLMN IDs the same as that in the LAI but LACs different from that in
the LAI.
c. If no neighboring cells described in a and b exist, the eNodeB selects the
neighboring cells with PLMN IDs the same as the serving PLMN ID of the UE.
If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter is selected, the eNodeB also selects cells whose PLMN IDs are in the
target PLMN list.
3.2.5 E-UTRAN to UTRAN CS Steering

This section describes the CS steering function in the optional feature LOFD-001078 E-
UTRAN to UTRAN CS/PS Steering. For details about the PS steering function in this feature,
see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
This feature applies to a scenario where service steering is required in a UTRAN with
multiple UTRA frequencies. By setting CS service priorities for UTRA frequencies, the
operator can achieve CSFB from E-UTRAN only to the UTRA frequency that has a high CS
service priority.
CS Steering in CSFB
This function is an enhancement to the CS Fallback to UTRAN feature. The enhancements
are as follows:
l During inter-RAT measurement on the UTRAN, frequencies with a high CS service

priority are preferentially measured.
The UtranFreqLayerMeasSwitch option of the ENodeBAlgoSwitch.FreqLayerSwtich
parameter specifies whether to enable this function.
If the option is selected, the eNodeB preferentially selects frequencies with a high CS
service priority specified by the UtranNFreq. CsPriority parameter as the measurement
targets. A larger value of this parameter indicates a higher priority. If this parameter is set
to Priority_0(Priority 0) for a frequency, the eNodeB does not select this frequency as
the measurement target. The follow-up measurement procedure is similar to that in CS
Fallback to UTRAN. For details, see 3.4 Target Cell/Frequency Selection.
l During blind handover, cells working on frequencies with a high CS service priority are
preferentially selected.

eRAN
The UtranFreqLayerBlindSwitch option of the ENodeBAlgoSwitch.FreqLayerSwtich

parameter specifies whether to enable this function.
If the option is selected, the eNodeB preferentially selects cells working on frequencies
with a high CS service priority specified by the UtranNFreq.CsPriority parameter. A
larger value of this parameter indicates a higher priority. If this parameter is set to
Priority_0(Priority 0) for a frequency, the eNodeB does not select cells working on this
frequency. The follow-up blind handover procedure is the same as that in CS Fallback to
UTRAN. For details, see 3.4 Target Cell/Frequency Selection.
LAI-based CS Steering in CSFB

This function is an enhancement to the CS Fallback with LAI to UTRAN feature. The
enhancements are as follows:
l Enhancement in measurement
a. The eNodeB selects inter-RAT frequencies on which the PLMN ID of a
neighboring cell is the same as the PLMN ID in the LAI.
b. Among the selected frequencies, the eNodeB selects a frequency with a high CS
service priority specified by the UtranNFreq.CsPriority parameter.
c. The follow-up measurement procedure is similar to that in CS Fallback to UTRAN.
For details, see 3.4 Target Cell/Frequency Selection.
The difference is that the eNodeB sorts neighboring cells in the following order after
receiving measurement reports from a UE:
a. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
b. Neighboring cells with PLMN IDs the same as that in the LAI but LACs different
from that in the LAI
c. Neighboring cells with PLMN IDs the same as the serving PLMN ID of the UE
l Enhancement in blind handover
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 a frequency with a high CS
service priority 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 handover procedure is the same as that in CS Fallback to
UTRAN. For details, see 3.4 Target Cell/Frequency Selection.
3.2.6 CS Fallback Steering to UTRAN

This chapter describes the optional feature LOFD-001088 CS Fallback Steering to UTRAN.
The UtranCsfbSteeringSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
This feature is an enhancement to the optional feature LOFD-001033 CSFB to UTRAN. In
terms of the UE status at the time when the UE initiates a CS service, you can configure the
target RAT and handover policy flexibly. There are two types of UEs:

eRAN
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.
CS-only UE
If the UE is a CS-only UE, the eNodeB selects the target RAT based on the RAT priorities for
CSFB of CS-only UEs. The priorities are specified by the following parameters:
l CSFallBackBlindHoCfg.IdleCsfbHighestPri: specifies the highest-priority RAT for
CSFB of CS-only UEs.
l CSFallBackBlindHoCfg.IdleCsfbSecondPri: specifies the second-highest-priority RAT
for CSFB of CS-only UEs.
l CSFallBackBlindHoCfg.IdleCsfbLowestPri: specifies the lowest-priority RAT for
CSFB of CS-only UEs.
The eNodeB can select a neighboring cell or frequency with a lower-priority RAT only if no
neighboring cell or frequency with higher-priority RATs is configured.
If the target system with the highest priority is UTRAN, the eNodeB selects the target
frequencies based on the setting of the UtranNFreq.CsPriority parameter. For details, see
3.2.5 E-UTRAN to UTRAN CS Steering.
The eNodeB selects a handover policy for CSFB of a CS-only UE based on the setting of the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. The eNodeB selects PS HO
and redirection in descending order.
CS+PS UE
The eNodeB selects the target RAT based on the RAT priorities specified by the following
parameters:
l CSFallBackBlindHoCfg.InterRatHighestPri: specifies the RAT with the highest
priority.
l CSFallBackBlindHoCfg.InterRatSecondPri: specifies the RAT with the second highest
priority.
l CSFallBackBlindHoCfg.InterRatLowestPri: specifies the RAT with the lowest priority.
The eNodeB can select a neighboring cell or frequency with a lower-priority RAT only if no
neighboring cell or frequency with higher-priority RATs is configured.
If the target system with the highest priority is UTRAN, the eNodeB selects the target
frequencies based on the setting of the UtranNFreq.CsPsMixedPriority parameter. The
UtranNFreq.CsPsMixedPriority and UtranNFreq.CsPriority parameters have similar
setting principles. For details, see 3.2.5 E-UTRAN to UTRAN CS Steering.
The eNodeB selects a handover policy for CSFB of a CS+PS UE based on the setting of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. The eNodeB selects PS HO and
redirection in descending order.

eRAN
3.2.7 Load-based CSFB to UTRAN

This chapter describes load-based CSFB to UTRAN. This feature is an enhancement to to the
CS Fallback to UTRAN feature. The CSFBLoadInfoSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.
In load-based CSFB to UTRAN, the eNodeB uses the RIM procedure in Multiple Report
mode to obtain the load information about UTRAN cells. For details about the RIM
procedure, see 3.7 RIM Procedure Between E-UTRAN and UTRAN. After receiving the
load information about UTRAN cells, the eNodeB saves the information and uses the
information to determine the target UTRAN cell for the CSFB.
In load-based CSFB to UTRAN, the measurement and blind handover procedures are the
same as those in the CS Fallback to UTRAN feature. For details, see 3.2.1 Basic CSFB to
UTRAN.
When the eNodeB selects the target UTRAN cell for the CSFB based on the load status of
UTRAN cells, the eNodeB considers UTRAN cells in descending order as follows: cells
whose load status is normal, cells whose load status is congested, and cells whose load status
is overloaded.
Load-based CSFB to UTRAN affects the target cell selection at a later phase. If measurement
is performed, the eNodeB does not select a low-priority frequency because all UTRAN cells
on the high-priority frequency are overloaded.
3.3 Triggering Events

CSFB triggering is classified into measurement triggering and blind handover triggering.
Measurement Triggering
During CSFB, the eNodeB starts UTRAN measurement after it receives a CS Fallback
Indicator. The measurement configuration is the same as that for coverage-based handover
from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description.
They have different thresholds and time-to-trigger. Table 3-1 lists the thresholds and time-to-
trigger related to event B1 for CSFB to UTRAN. Other parameters are the same as those
related to event B1 for coverage-based inter-frequency handovers.
Table 3-1 Parameters related to event B1 for CSFB to UTRAN

Parameter Name Parameter ID Parameter Description
CSFB UTRAN EventB1 CSFallBackHo.CsfbHo The

RSCP Trigger Threshold UtranB1ThdRscp InterRatHoComm.InterRATHoUt
ranB1MeasQuan parameter
CSFB UTRAN EventB1 CSFallBackHo.CsfbHo determines which threshold is to be
ECN0 Trigger Threshold UtranB1ThdEcn0 used.
CSFB Utran EventB1 CSFallBackHo.CsfbHo -

Time To Trig UtranTimeToTrig

eRAN
Blind Handover Triggering

Blind handover is controlled by the BlindHoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter and the BlindHoSwitch option of the
CellHoParaCfg.HoModeSwitch parameter. The blind handover function takes effect only
when both options are selected.
When an E-UTRAN coverage area is larger than a UTRAN coverage area and E-UTRAN and
UTRAN base stations are co-sited, adaptive-blind-handover-based CSFB estimates the signal
strength of the neighboring UTRAN cell based on the signal strength of the serving E-
UTRAN cell. Adaptive-blind-handover-based CSFB is controlled by the
CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter.
l If the UE is located in the center of the E-UTRAN cell, the eNodeB performs the blind
handover.
l If the UE is located at the edge of the E-UTRAN cell, the eNodeB performs a
measurement-based handover.
When the blind handover function takes effect:
l If adaptive-blind-handover-based CSFB is disabled, the eNodeB directly enters the blind
handover procedure.
l If adaptive-blind-handover-based CSFB is enabled, the eNodeB delivers measurement
configurations for event A1.
If the eNodeB receives an event A1 report and determines that the UE is located in
the center of the E-UTRAN cell, it directly enters the blind handover procedure.
If the eNodeB does not receive an event A1 report and determines that the UE is
located at the edge of the E-UTRAN cell, it enters the measurement procedure.
The event A1 threshold is specified by the CSFallBackHo.BlindHoA1ThdRsrp
parameter.
3.4 Target Cell/Frequency Selection

Measurement Object Selection
For a measurement, the eNodeB generates a candidate cell list based on inter-RAT
measurement results.
Figure 3-2 shows the measurement object selection procedure. When the eNodeB delivers
measurement configuration messages to select frequencies of a target system:
l If CS Fallback Steering to UTRAN or GERAN is enabled and the highest-priority RAT
is configured, the eNodeB delivers only frequencies of the highest-priority RAT. For
example, if the CSFallBackBlindHoCfg.IdleCsfbHighestPri parameter is set to
UTRAN, the eNodeB delivers only UTRAN frequencies.
l If CS Fallback Steering to UTRAN or GERAN is disabled, the eNodeB delivers
frequencies of all qualified RATs to the UE for handover measurement.

eRAN
Figure 3-2 Measurement object selection procedure
The configurations involved in Figure 3-2 are as follows:
l Neighboring UTRA frequencies are added by running the ADD UTRANNFREQ

command.
l The frequency priority is specified by the UtranNFreq.ConnFreqPriority parameter. A
larger value indicates a higher priority.

eRAN
l The cell measurement priority of neighboring UTRAN cells can be automatically

optimized by ANR. The UTRAN_SWITCH option under the
ENodeBAlgoSwitch.NCellRankingSwitch parameter is used to enable this function.
This option is recommended to be selected if ANR is enable.
If this option is selected, the eNodeB automatically optimizes the setting of the
UtranNCell.NCellMeasPriority parameter for the cell. This parameter cannot be
modified manually. For details, see ANR Management Feature Parameter
Description.
If this option is cleared, the cell measurement priority is specified by the
UtranNCell.CellMeasPriority parameter, which needs to be configured manually.
l The number of frequencies or cells that the eNodeB can randomly select for
measurement is always equal to the allowed maximum number.
l The maximum number of frequencies is specified by the
CellUeMeasControlCfg.MaxUtranFddMeasFreqNum parameter.
l For details about the maximum number of neighboring cells in a measurement
configuration message, see section 6.4 "RRC multiplicity and type constraint values" in
3GPP TS 36.331 V10.1.0.
Blind Handover Object Selection

During a blind handover for CSFB, the eNodeB selects the target RAT based on the RAT
priorities specified by the following parameters:
l CSFallBackBlindHoCfg.InterRatHighestPri: specifies the RAT with the highest
priority.
l CSFallBackBlindHoCfg.InterRatSecondPri: specifies the RAT with the second highest
priority.
l CSFallBackBlindHoCfg.InterRatLowestPri: specifies the RAT with the lowest priority.
If CSFallBackBlindHoCfg.InterRatHighestPri is set to UTRAN(UTRAN), the eNodeB
performs CSFB to UTRAN.
l When selecting target cells for blind handover, the eNodeB excludes the following
neighboring cells:
Blacklisted neighboring cells
Neighboring cells with a handover prohibition flag
Neighboring cells that have a different PLMN from the serving cell in the
neighboring cell list. If the inter-PLMN handover switch is turned on, such cells are
not excluded.
Cells in the areas indicated by the Handover Restriction List IE in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME
After the preceding exclusion, the eNodeB excludes cells from the neighboring cell list
based on SPID-based mobility management in connected mode. For details, see
LOFD-00105401 Camp and Handover Based on SPID in Flexible User Steering Feature
Parameter Description.
l When selecting target frequencies for blind redirection, the eNodeB filters frequencies
based on the RATs supported by the UE and PLMN information corresponding to
frequencies.
After the preceding exclusion, the eNodeB excludes cells from the neighboring cell list
based on SPID-based mobility management in connected mode. For details, see

eRAN
LOFD-00105401 Camp and Handover Based on SPID in Flexible User Steering Feature
During blind handover, the target selection procedure is different, depending on whether
neighboring UTRAN cells are configured.
l If neighboring UTRAN cells are configured, the target selection procedure is shown in
Figure 3-3.
The blind handover priority of a neighboring UTRAN cell is specified by the
UtranNCell.BlindHoPriority parameter. A larger value indicates a higher priority.
The priority of a neighboring UTRA frequency is specified by
UtranNFreq.ConnFreqPriority parameter. A larger value indicates a higher
priority.
l If no neighboring UTRAN cell is configured, neighboring UTRA frequencies are
configured, and the UE performs CSFB based on redirection, the target selection
procedure is shown in Figure 3-4.
Neighboring UTRA frequencies are configured in UtranNFreq MOs.
The PLMN information of the neighboring UTRA frequencies is contained in the
configured UtranRanShare or UtranExternalCell MOs.
Figure 3-3 Target cell selection (configured with a neighboring UTRAN cell)

eRAN
Figure 3-4 Target cell selection (configured with no neighboring UTRAN cell)
When a UE performs an E-UTRAN-to-UTRAN blind handover, neighboring UTRAN cells

must be configured. When the UE performs an E-UTRAN-to-UTRAN blind redirection,
neighboring UTRAN frequencies and connect frequency priorities other than neighboring
UTRAN cells must be configured.
During frequency selection, the eNodeB preferentially frequencies on which neighboring cells
operate. Then, the eNodeB selects frequencies based on blind handover priorities.
l If no blind handover priority is 0, the eNodeB preferentially selects the frequency
corresponding to the cell that has a higher blind handover priority.
l If all blind handover priorities are 0, the eNodeB selects the frequency based on connect
frequency priorities. It preferentially selects the frequency with the highest connect
frequency priority. If multiple frequencies are of the same priority, the eNodeB selects
the blind redirection frequency in a round-robin manner. This ensures that the UE
accesses each frequency equally. This function is specified by the
CSFallBackBlindHoCfg.UtranCsfbBlindRedirRrSw parameter.
The equal and random selection function will be enhanced later. When the UE initiates the
measurement- or blind-handover-based E-UTRAN-to-UTRAN CSFB procedure and
implements random selection of target frequencies or cells, the RsvdSwPara1_bit23 option

eRAN
of the eNBRsvdPara.RsvdSwPara1 parameter can be selected so as to select frequencies or

cells equally. It is recommended that the RsvdSwPara1_bit23 option be used.
CSFallBackBlindHoCfg.UtranCsfbBlindRedirRrSw is not recommended.
3.5 Handover Decision

In the handover decision phase, the eNodeB checks the candidate cell list. Based on the check
result, the eNodeB determines whether a handover needs to be initiated and, if so, to which
cell the UE is to be handed over.
3.5.1 Basic Handover Decision

When the handover policy is PS HO, SRVCC, or redirection (excluding flash redirection), the
eNodeB does not need to obtain system information of the peer and performs the basic
handover decision.
In the handover decision phase, the eNodeB checks the candidate cell list. Based on the check
result, the eNodeB determines whether a handover needs to be initiated and, if so, to which
cell the UE is to be handed over. If the eNodeB receives measurement reports about different
RATs, it processes the reports in an FIFO manner.
The eNodeB excludes the following cells from the neighboring cell list:
l Blacklisted neighboring cells

l Neighboring cells with a handover prohibition flag
l Neighboring cells that have a different PLMN from the serving cell in the neighboring
cell list
If the inter-PLMN handover switch is turned on, such cells are not excluded.
l Neighboring cells in the areas indicated by the IE Handover Restriction List in the
INITIAL CONTEXT SETUP REQUEST message sent from the MME
After the preceding exclusion, the eNodeB excludes cells from the neighboring cell list based
on SPID-based mobility management in connected mode. For details, see LOFD-00105401
Camp & Handover Based on SPID in Flexible User Steering Feature Parameter
Description.
The eNodeB then sends a handover request to the target cell at the top of the filtered candidate
cell list. If the handover request fails, the eNodeB sends the handover request to the next
target cell, as described in Table 3-2.
Table 3-2 Sequence of handover requests to be sent by the eNodeB

Candidate Cell List Sequence of Handover Requests
Generated by
Measurement A handover request is sent to the cell with the best signal
quality.
Blind handover A handover request is sent to a cell or frequency that has the
highest priority. If multiple cells have the highest priority, the
eNodeB randomly selects a cell for blind handover.

eRAN
If the handover request fails in all candidate cells:
l For a measurement procedure, the eNodeB waits until the UE sends the next
measurement report.
l For a blind handover procedure, the eNodeB finishes the handover attempt.
3.5.2 Flash Redirection Decision

When the handover policy requires the eNodeB to obtain system information about the peer,
for example, flash redirection, handover decision based on system information is performed.
If the handover decision is based on system information, the eNodeB includes system
information of the target cell of the corresponding RAT. Therefore, the time for reading cell
system information is not required so that the UE can quickly access the target network.
Decision based on system information adheres to the following principles:
l In blind handover scenarios:

a. The target cell list for blind handover is selected, including other cells under the
target frequency for redirection. The UTRAN_SWITCH option of the
ENodeBAlgoSwitch.NCellRankingSwitch parameter specifies the sequence of
adding other cells.
When this option is selected, the eNodeB adds other cells in the target frequency
according to UtranNCell.NCellMeasPriority in descending order.
When this option is cleared, the eNodeB adds other cells in the target frequency
according to UtranNCell.CellMeasPriority in descending order.
b. Basic handover decision is applied. For details, see 3.5.1 Basic Handover
Decision.
c. Cells whose system information is not obtained are filtered out.
d. The eNodeB excludes cells from the neighboring cell list based on SPID-based
mobility management in connected mode. For details, see LOFD-00105401 Camp
& Handover Based on SPID in Flexible User Steering Feature Parameter
Description.
l In measurement scenarios:
a. Cells in the candidate cell list generated by measurement are selected, plus cells that
are not in measurement reports but work on the target frequency for redirection.
The UTRAN_SWITCH option of the ENodeBAlgoSwitch.NCellRankingSwitch
parameter specifies the sequence of adding other cells.
b. Basic handover decision is applied. For details, see 3.5.1 Basic Handover
Decision.
c. Cells whose system information is not obtained are filtered out.
You can specify the number of UTRAN cells contained in the redirection message by setting
the InterRatHoComm.CellInfoMaxUtranCellNum parameter. Assume that this parameter is
set to N.
l If the number of target cells after flash redirection decision is greater than N, the eNodeB
selects the first N cells.
l If the number of target cells after flash redirection decision is smaller than N, the
eNodeB selects target cells after flash redirection decision.

eRAN
The eNodeB obtains system information of target cells in the RAN information management
(RIM) procedure. If a target cell does not support the RIM procedure, the eNodeB cannot
obtain system information of that cell.
3.6 Handover Execution

The eNodeB controls the UE to be handed over from the serving cell to the target cell.
3.6.1 Handover Policy Selection

CSFB from E-UTRAN to UTRAN can be based on PS handover, redirection, or flash
redirection, as shown in Figure 3-5. This handover policy selection procedure is based on the
assumption that neighboring frequency and neighboring cell configurations are proper.
The CSFB policy is specified by different parameters, depending on whether LOFD-001088
CS Fallback Steering to UTRAN is enabled.
If this feature is enabled:
l The CSFB policy for UEs in idle mode is specified by the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.
l 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.

eRAN
Figure 3-5 E-UTRAN-to-UTRAN handover policy selection procedure
The parameters in Figure 3-5 are described as follows:
The timer length is specified by the CSFallBackHo.CsfbProtectionTimer parameter.
l If the UE does not report inter-RAT MRs and stays in the area covered by the eNodeB
before the timer expires, the eNodeB performs the CSFB based on the blind redirection.
If blind redirection for CSFB is required, select the REDIRECTION option of the
The eNodeB preferentially selects a system that the UE has not measured. For
example, if the UE has measured the UTRAN, the eNodeB preferentially selects the
GERAN for redirection.
If a cell to which the eNodeB has never attempted to hand over the UE is reported,
the eNodeB preferentially selects the operating frequency of the cell for redirection.

eRAN
If there is not target frequency available for redirection, the eNodeB stops the
procedure.
If flash CSFB is enabled in this situation, redirection-based CSFB performed by the
eNodeB is referred to as CSFB emergency redirection. In this scenario, you need to
set the InterRatHoComm.UTRANCellNumForEmcRedirect parameter to specify
the maximum number of UTRAN cell system information messages that can be
transmitted during a CSFB emergency redirection procedure.
l The eNodeB selects the target cell for redirection as it does during blind handover. For
details about how the eNodeB performs target selection during blind handover, see 3.4
Target Cell/Frequency Selection.
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.
Adaptive-blind-handover-based CSFB is controlled by the
CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter.
l If PS handover for CSFB is required, select the UtranPsHoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter and the PS_HO option of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. If either option is cleared, PS
handover for CSFB is invalid. The eNodeB selects the redirection policy. If the
redirection policy is invalid and the CSFB protection timer expires, the eNodeB enters
the blind redirection procedure.
l During a CSFB based on blind PS handover, if the target cell with the highest blind
handover priority fails to prepare the handover, the eNodeB attempts another cell with
the second highest blind handover priority. The eNodeB can attempt a maximum of eight
cells. If all these cells fail in preparation, the eNodeB performs the emergent blind
redirection.

The measurement procedure and blind handover procedure for this feature are the same as
those in CSFB to UTRAN. For details, see 3.2.1 Basic CSFB to UTRAN.
When a UE in an LTE system needs to perform voice service but the LTE system does not
support VoIP, the eNodeB decides to perform ultra-flash CSFB if LOFD-070202 Ultra-Flash
CSFB to UTRAN is enabled. Figure 3-6 shows ultra-flash CSFB to UTRAN by using the
SRVCC procedure after the eNodeB performs a measurement or blind handover decision. For
details about how to select other CSFB policies, see 3.6.1 Handover Policy Selection.

eRAN
Figure 3-6 Ultra-Flash CSFB to UTRAN
The preceding figure is described as follows:

l The ultra-flash CSFB to UTRAN switch is controlled by the
UtranUltraFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter.
l At least one neighboring UTRAN cell's RNC support ultra-flash CSFB to UTRAN.
If all neighboring UTRAN cells' RNCs support ultra-flash CSFB to UTRAN, no
configuration is required.
If some neighboring UTRAN cells' RNCs do not support ultra-flash CSFB to
UTRAN, the following configurations are required:
Select the UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.
For RNCs that do not support ultra-flash CSFB to UTRAN, do not select the
corresponding UltraFlashCsfbCap option of the
UtranNetworkCapCfg.NetworkCapCfg parameter.

eRAN
3.6.3 Redirection-based CSFB Optimization for UEs in Idle Mode

To speed up CSFB for UEs in idle mode by shortening end-to-end delays and to reduce the
CSFB failure rate due to initial context setup failures, redirection-based CSFB for UEs in idle
mode is optimized.
The optimization is performed after the eNodeB decides to perform blind handover, as shown
in Figure 3-7.
Figure 3-7 Redirection-based CSFB optimization for UEs in idle mode
The optimization switch is controlled by the IdleCsfbRedirectOptSwitch option of the

GlobalProcSwitch.ProtocolMsgOptSwitch parameter.
For details about how to decide between redirection and flash redirection, see 3.6.1 Handover
Policy Selection.
For the signaling procedure, see 12.1.6 Redirection-based CSFB Optimization for UEs in
Idle Mode.
3.6.4 CSFB Admission Optimization for UEs in Idle Mode

UEs in idle mode only have a default bearer for data service, and the allocation/retention
priority (ARP) of the default bearer is generally lower. When a UE in idle mode needs to

eRAN
perform CSFB but the target cell is congested or cannot accommodate more UEs, this UE
cannot preempt resources in the target cell.
To ensure the CSFB success rate in the preceding scenario, the eNodeB can preferentially
admit CSFB UEs. This function is controlled by the
CSFallBackPolicyCfg.CsfbUserArpCfgSwitch parameter.
A larger value of the CsFallbackPolicyCfg.NormalCsfbUserArp parameter indicates a
higher probability of admission of CSFB UEs in idle mode. For details about the admission
procedure, see Admission and Congestion Control.
3.7 RIM Procedure Between E-UTRAN and UTRAN

The RIM procedure exchanges information between the E-UTRAN and UTRAN through the
core networks.
In CSFB procedures, the eNodeB obtains the load information of external UTRAN cells from
RNCs through the RIM procedure if the parameter GlobalProcSwitch.UtranLoadTransChan
is set to BASED_ON_RIM.
In flash CSFB procedures, the eNodeB obtains the system information (SI) of external cells
from RNCs through the RIM procedure. For details about related parameters, see 3.7.1 RIM
Procedure Through the Core Network and 3.7.2 RIM Procedure Through the
eCoordinator.
The RIM procedure includes the following two information exchange modes:
l Single Report
In Single Report mode, the source sends a request, and then the target responds with a
single report.
When flash CSFB to UTRAN is triggered, the eNodeB sends a RIM message to the
RNC and then includes the obtained SI in a redirection message to send to the UE. If the
SI fails to be obtained from the RNC, the eNodeB no longer attempts the RIM request.
l Multiple Report
In Multiple Report mode, the target responds with a report after receiving a request from
the source, and the target also sends a report to the source each time information about
the target changes.
When flash CSFB to UTRAN is triggered, the eNodeB sends RIM messages to all
neighboring UTRAN cells every four seconds no matter whether the eNodeB has CSFB
services.
To ensure that the SI of the target cell can be obtained successfully, the eNodeB starts a
four-second timer when it sends a RIM message.
If the eNodeB receives a response to the RIM message before the timer expires, the
eNodeB saves the obtained SI.
If the eNodeB receives a response to the RIM message after the timer expires, the
eNodeB considers that an exception occurs and discards the SI.
If the eNodeB does not receive a response to the RIM message when the timer
expires, the eNodeB sends the RIM message and starts the timer again (called a
retry) two hours later. If the eNodeB still does not receive a response after 10
retries, the RIM request fails. The interval between the nth and (n-1)th retries is
twice the number of the retries n. For example, the first retry occurs two hours after
the first SI acquisition fails, the second retry occurs four hours after the first retry

eRAN
fails, and the third retry occurs six hours after the second retry fails. For each retry,
the eNodeB sends a RIM message and restarts the timer.
The eNodeB may obtain incorrect SI due to the abnormalities in the UTRAN, core
network, or transport network. To avoid this situation, the eNodeB selects a time point
randomly every day from 02:00 a.m. to 04:00 a.m and deletes all the obtained SI. Then,
the eNodeB requests the SI of UTRAN cells through the RIM procedure again.
If a neighboring UTRAN cell is faulty or deactivated, the RNC sends an END message
to notify the eNodeB of stopping the RIM procedure. In this case, the eNodeB deletes
the obtained SI and requests SI again in the next RIM procedure.
Currently, the eNodeB triggers a RIM procedure in Multiple Report mode only if MMEs
comply with 3GPP Release 9 or later.
The RIM procedure can be performed through the core network or eCoordinator.
3.7.1 RIM Procedure Through the Core Network

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

l The RIM procedure between EUTRAN and UTRAN is controlled by the
UTRAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter.
If this option is selected, the eNodeB uses the RIM procedure in Multiple Report mode
to obtain the system information of external UTRAN cells.
l Whether multiple UTRAN operators can use different mobility policies is specified by
the UtranSepOpMobilitySwitch option of the ENodeBAlgoSwitch.MultiOpCtrlSwitch
parameter.
l The RIM procedure for obtaining SI is controlled by the SiByRimCapCfg option of the
UtranNetworkCapCfg.NetworkCapCfg parameter.

eRAN
Figure 3-9 Information exchange mode selection for the RIM procedure
3.7.2 RIM Procedure Through the eCoordinator

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is performed
through the eCoordinator. As shown in Figure 3-10, the RIM procedure through the
eCoordinator involves the eNodeB, eCoordinator, and RNC. Among these NEs, the MME and
the SGSN transfer but do not resolve information.
Figure 3-10 RIM procedure through the eCoordinator

eRAN
The RIM procedure through the eCoordinator requires that the corresponding switches of all
NEs involved to be switched on.
During the RIM procedure through the eCoordinator, the eNodeB does not send RIM
messages to the EPC or process RIM messages from the EPC.
The information exchange mode for the eCoordinator-based RIM procedure is controlled by
UTRAN_RIM_SWITCH under the ENodeBAlgoSwitch.RimSwitch parameter.
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.

eRAN
CS Fallback Feature Parameter Description 4 CSFB to GERAN
4 CSFB to GERAN
This chapter describes each CSFB to GERAN feature, CSFB procedure, and RIM procedure
between E-UTRAN and GERAN.

eRAN
4.1 Overview
CSFB to GERAN can be implemented in different ways, and this section covers the following
features/functions:
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.
Figure 4-1 CSFB to GERAN procedure
4.2 Feature Classification
4.2.1 Basic CSFB to GERAN

This section describes the optional feature LOFD-001034 CS Fallback to GERAN. The
GeranCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies
whether to enable this feature.

eRAN
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
This feature has the same principle as CSFB to UTRAN, except the parameters mentioned
below in this section. For details about the principle of CSFB to UTRAN, see 3.2.1 Basic
CSFB to UTRAN.
4.2.2 Flash CSFB to GERAN

This section describes the optional feature LOFD-001053 Flash CS Fallback to GERAN. The
GeranFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter

GERAN. After this feature is activated, the eNodeB obtains the GERAN cell information
through the RIM procedure and then sends the LTE-to-GSM redirection message including
the obtained GERAN cell information to the UE. The
InterRatHoComm.CellInfoMaxGeranCellNum parameter specifies the maximum number
of GERAN cells that can be contained in the redirection message, which is configurable.
In this case, the UE can access a GERAN cell without obtaining GERAN cell information.
This reduces the access delay. For details about how the GERAN cell information is delivered
to the eNodeB through the RIM procedure, see Interoperability Between GSM and LTE.
This feature has the same principle as flash CSFB to UTRAN. For details, see 3.2.2 Flash
CSFB to UTRAN.
4.2.3 CS Fallback with LAI to GERAN

This section describes the optional feature LOFD-001069 CS Fallback with LAI to GERAN.
This feature is under license control and is not controlled by a switch.
This feature has the same principle as CS fallback with LAI to UTRAN. For details, see 3.2.4
CS Fallback with LAI to UTRAN.
4.2.4 CS Fallback Steering to GERAN

This chapter describes the optional feature LOFD-001089 CS Fallback Steering to GERAN.
The GeranCsfbSteeringSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
The principles of this feature are similar to the principles of the CS Fallback Steering to
UTRAN feature. For details about the principles, see 3.2.6 CS Fallback Steering to
UTRAN.
The eNodeB selects a handover policy for CSFB of a CS-only UE based on the setting of the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. The eNodeB selects PS HO,
CCO, and redirection in descending order.
The eNodeB selects a handover policy for CSFB of a CS+PS UE based on the setting of the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. The eNodeB selects PS HO, CCO, and
redirection in descending order.

eRAN
4.2.5 Ultra-Flash CSFB to GERAN

This section describes the optional feature LOFD-081283 Ultra-Flash CSFB to GERAN. The
GeranUltraFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
specifies whether to enable this feature. This feature is a Huawei-proprietary feature. To
enable this feature, the MME, MSC, and eNodeB must be all provided by Huawei and support
this feature.
When a UE initiates a CS service setup request in a VoLTE-incapable cell, this feature enables
the eNodeB to hand over the UE to the GERAN through the SRVCC procedure. It prepares
CS resources on the GERAN in advance and omits unnecessary signaling processes during
GERAN access, thereby shortening the access delay for CSFB by 2s and improving user
experience significantly. Compared with the standard procedure, the ultra-flash CSFB to
GERAN procedure for Huawei omits certain signaling processes. For details, see 12.2.6
Ultra-Flash CSFB to GERAN.
l The measurement procedure and blind handover procedure for this feature are the same
as those in CSFB to GERAN. For details, see 3.2.1 Basic CSFB to UTRAN.
l The SRVCC handover policy for this feature is the same as that for ultra-flash CSFB to
GERAN. For details, see 3.6.2 Ultra-Flash CSFB to UTRAN.
This feature requires that external GERAN cells support ultra-flash CSFB to GERAN.
l If all external GERAN cells support ultra-flash CSFB to GERAN, no configuration is
required.
l If some external GERAN cells do not support ultra-flash CSFB to GERAN, the
following configurations are required:
Set UltraFlashCsfbInd to BOOLEAN_FALSE for external GERAN cells that do
not support ultra-flash CSFB to GERAN.
The ultra-flash CSFB to GERAN capability for external GERAN cells is specified
by the GeranExternalCell.UltraFlashCsfbInd parameter.
When the UE completes voice services on the GERAN after ultra-flash CSFB to GERAN is
performed, you can enable the Fast Return to LTE feature on the GSM side so that the UE
quickly returns to the E-UTRAN. After the UE completes voice services on the GERAN, the
UE carries the LTE frequency information in a Channel Release message and selects a proper
LTE cell to camp on based on the frequency information to accelerate the return to the E-
UTRAN.
When IratMeasCfgTransSwitch in the GlobalProcSwitch.ProtocolMsgOptSwitch parameter
is set to ON, the eNodeB filters LTE frequencies supported by the UE based on the UE
capability to obtain a frequency set. During the SRVCC handover, the eNodeB sends a
Handover Required message containing the frequency set to the BSC of the target cell and
provides reference for the UE to accelerate the return to the E-UTRAN after the UE
completes voice services on the GERAN.
When the CellDrxPara.DrxForMeasSwitch parameter is set to ON(On), the eNodeB
delivers the DRX and gap-assisted measurement configurations if the following conditions
are met. The UE uses the DRX measurement preferentially and makes more use of DRX sleep
time continuously to accelerate the measurement and decrease the delay.
l The UE cannot perform the gap-assisted measurement. In this case, the AutoGapSwitch
option of the ENODEBALGOSWITCH.HoModeSwitch parameter is set to OFF(Off)
or the interRAT-NeedForGaps option for the GSM frequency of the UE capability is
set to TRUE(True).

eRAN
l The gap-assisted measurement is not configured for the UE.

l The UE supports DRX.
l The BlindHoSwitch option of the ENODEBALGOSWITCH.HoModeSwitch
parameter is set to OFF(Off).
After the DRX measurement is used, you need to set longer sleep time for measurements.
Therefore, the UE is easier to enter the sleep time, affecting the scheduling by decreasing the
cell throughput.
For details about how to configure measurement-specific DRX troubleshooting and related
parameters, see DRX and Signaling Control.
NOTE
The following table describes the parameters that must be set in the GLOBALPROCSWITCH MO to
turn on the UE compatibility switch when UEs do not support Ultra-Flash CSFB, resulting in UE
compatibility problems.
4.3 Triggering Events

CSFB triggering is classified into measurement triggering and blind handover triggering. For
details, see 3.3 Triggering Events.
4.4 Target Cell/Frequency Selection

Measurement Object Selection
The frequency priority used during target frequency selection is specified by the
GeranNfreqGroup.ConnFreqPriority parameter. A larger value indicates a higher priority.
During the GERAN frequency selection for measurement that is different from the UTRA
frequency selection, if the total number of the GERAN frequencies that can be delivered in
the frequency group with the highest priority and the frequencies that have been delivered
exceeds the allowed maximum number 32, all frequencies in this frequency group cannot be
delivered. The eNodeB determines whether the GERAN frequencies in the frequency group
with the second highest priority can be delivered until the number of delivered frequencies is
less than or equal to the maximum number of GERAN frequencies allowed for measurement
or all frequency groups are determined.
In GERAN, no cell measurement priority is configured. If the number of cells working on a
frequency exceeds the specification, the eNodeB randomly measures certain cells.
Blind Handover Object Selection

If CSFallBackBlindHoCfg.InterRatHighestPri is set to GERAN(GERAN), the eNodeB
performs CSFB to GERAN.
During blind handover, the target selection procedure is different, depending on whether
neighboring GERAN cells are configured.
l If neighboring GERAN cells are configured,
The blind handover priority of a neighboring GERAN cell is specified by the
GeranNcell.BlindHoPriority parameter. A larger value indicates a higher priority.

eRAN
The GERAN frequency group with the highest priority (specified by the
GeranNfreqGroup.ConnFreqPriority parameter) is selected for blind handover. A
larger value indicates a higher priority.
If the priorities of neighboring cells or frequencies are the same, the eNodeB
randomly selects a target cell or frequency. Due to uncertainty of random selection,
you are not advised to set the priorities to the same to ensure the blind handover
success.
l If no neighboring GERAN cell is configured,
Neighboring GERAN frequencies are configured in GeranNfreqGroup MOs.
The PLMN information of the neighboring GERAN frequency is contained in the
configured GeranRanShare or GeranExternalCell MOs.
4.5 Handover Decision

The handover decision for CSFB to GERAN is the same as that for CSFB to UTRAN. For
details, see 3.5 Handover Decision.
4.6 Handover Execution

When a UE in an LTE system needs to perform voice service but the LTE system does not
support VoIP, a CSFB to an inter-RAT network is triggered.
CSFB from E-UTRAN to GERAN can be based on PS handover, CCO/NACC, redirection, or
flash redirection, as shown in Figure 4-2. This handover policy selection procedure is based
on the assumption that neighboring frequency and neighboring cell configurations are proper.
The CSFB policy is specified by different parameters, depending on whether LOFD-001089
CS Fallback Steering to GERAN is enabled.
l 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
l 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.

eRAN
Figure 4-2 E-UTRAN-to-GERAN handover policy selection procedure
The parameters in Figure 4-2 are described as follows:

The timer length is specified by the CSFallBackHo.CsfbProtectionTimer parameter.
l If the UE stays in the area covered by the eNodeB before the timer expires, the eNodeB
performs the CSFB based on the blind redirection.
The eNodeB preferentially selects a system that the UE has not measured. For
example, if the UE has measured the UTRAN, the eNodeB preferentially selects the
GERAN for redirection.
If there is not target frequency available for redirection, the eNodeB stops the
procedure.
l Blind handover is controlled by the BlindHoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter and the BlindHoSwitch option of the
CellHoParaCfg.HoModeSwitch parameter. The CSFB blind handover is triggered only
l Adaptive-blind-handover-based CSFB is controlled by the
CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter.

eRAN
l The CSFB policy switches are controlled by the options of the

ENodeBAlgoSwitch.HoModeSwitch parameter:
The PS handover supporting capability is specified by GeranPsHoSwitch.
The CCO supporting capability is specified by GeranCcoSwitch.
The NACC supporting capability is specified by GeranNaccSwitch.
When CSFB to GERAN is based on CCO/NACC, the eNodeB obtains SI of
external cells from RNCs through the RIM procedure. For details about the RIM
procedure, see 4.7 RIM Procedure Between E-UTRAN and GERAN.
l During a CSFB based on blind PS handover, if the target cell with the highest blind
handover priority fails to prepare the handover, the eNodeB attempts another cell with
the second highest blind handover priority. The eNodeB can attempt a maximum of eight
cells. If all these cells fail in preparation, the eNodeB performs the emergent blind
redirection.
4.7 RIM Procedure Between E-UTRAN and GERAN

The principles of the RIM procedure between E-UTRAN and GERAN are the same as those
for UTRAN described in 3.7 RIM Procedure Between E-UTRAN and UTRAN.
The RIM procedure between E-UTRAN and GERAN is enabled by default because there is
no switch for selecting a load information transfer channel.
If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is
performed through the core network. If ENodeBAlgoSwitch.RimOnEcoSwitch is set to
ON(On), the RIM procedure is performed through the eCoordinator. The two RIM
procedures select information exchange modes in the same way.
Figure 4-3 shows the procedure of information exchange mode selection for the RIM
procedure.
The RIM procedure between EUTRAN and GERAN is controlled by the
GERAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter.
If this option is selected, the eNodeB uses the RIM procedure in Multiple Report mode to
obtain the system information of external GERAN cells.

eRAN
Figure 4-3 Information exchange mode selection for the RIM procedure

eRAN
CS Fallback Feature Parameter Description 5 Related Features
5 Related Features
5.1 Features Related to LOFD-001033 CS Fallback to

UTRAN
Prerequisite Features
This feature requires the optional feature LOFD-001019 PS Inter-RAT Mobility between E-
UTRAN and UTRAN.
Mutually Exclusive Features

None
Impacted Features
When a UE initiates a CSFB request, the eNodeB cannot determine whether the target inter-
RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN, according to 3GPP
Release 9. Therefore, it is not recommended that CSFB to GERAN/UTRAN be enabled
together with CSFB to CDMA2000 1xRTT. In addition, it is not recommended that this
feature be enabled together with either of the following features:
l LOFD-001035 CS Fallback to CDMA2000 1xRTT
l LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT
If both CSFB to UTRAN and CSFB to CDMA2000 are enabled, the eNodeB attempts CSFB
to UTRAN first. If the attempt fails, the eNodeB attempts CSFB to CDMA2000.
5.2 Features Related to LOFD-001052 Flash CS Fallback to

UTRAN
This feature requires LOFD-001033 CS Fallback to UTRAN.

eRAN

When a UE initiates a CSFB request, the eNodeB cannot determine, according to 3GPP
Release 9 specifications, whether the target inter-RAT network is a CDMA2000 1xRTT
network or a GERAN/UTRAN. Therefore, CSFB to GERAN/UTRAN cannot be enabled
together with CSFB to CDMA2000 1xRTT. This feature does not work with the following
features:

Impacted Features
None
5.3 Features Related to LOFD-070202 Ultra-Flash CSFB to

UTRAN
This feature depends on the optional feature LOFD-001033 CS Fallback to UTRAN.

None
Impacted Features
None
5.4 Features Related to LOFD-001068 CS Fallback with LAI

to UTRAN
This feature requires LOFD-001033 CS Fallback to UTRAN.

features:


eRAN
Impacted Features
None
5.5 Features Related to LOFD-001088 CS Fallback Steering

to UTRAN
This feature requires LOFD-001033 CS Fallback to UTRAN and LOFD-001078 E-UTRAN
to UTRAN CS/PS Steering.

features:

Impacted Features
This feature affects LOFD-001089 CS Fallback Steering to GERAN. In overlapping coverage
of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to UTRAN and
LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously, achieve CSFB
steering to different RATs.
5.6 Features Related to LOFD-001078 E-UTRAN to

UTRAN CS/PS Steering
Required Features
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
or LOFD-001033 CS Fallback to UTRAN.

None
Affected Features
None

eRAN
5.7 Features Related to LOFD-001034 CS Fallback to

GERAN
This feature requires LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.

None
Impacted Features
When a UE initiates a CSFB request, the eNodeB cannot determine whether the target inter-
RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN, according to 3GPP
Release 9. Therefore, it is not recommended that CSFB to GERAN/UTRAN be enabled
together with CSFB to CDMA2000 1xRTT. In addition, it is not recommended that this
feature be enabled together with either of the following features:
If both CSFB to GERAN and CSFB to CDMA2000 are enabled, the eNodeB attempts CSFB
to GERAN first. If the attempt fails, the eNodeB attempts CSFB to CDMA2000.
5.8 Features Related to LOFD-001053 Flash CS Fallback to

GERAN
This feature requires LOFD-001034 CS Fallback to GERAN.

features:

Impacted Features
None

eRAN
5.9 Feature Related to LOFD-081283 Ultra-Flash CSFB to

GERAN
This feature requires the optional feature LOFD-001034 CS Fallback to GERAN.

None
Impacted Features
None
5.10 Features Related to LOFD-001069 CS Fallback with

LAI to GERAN

features:

Impacted Features
None
5.11 Features Related to LOFD-001089 CS Fallback

Steering to GERAN

eRAN

features:
Impacted Features
This feature affects LOFD-001088 CS Fallback Steering to UTRAN. In overlapping coverage
of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to UTRAN and
LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously, achieve CSFB
steering to different RATs.

eRAN
CS Fallback Feature Parameter Description 6 Network Impact
6 Network Impact
6.1 LOFD-001033 CS Fallback to UTRAN

System Capacity
In essence, CSFB provides CS service access for E-UTRAN UEs. Considering that the
number of UEs that request CS services within an area is relatively stable and is not affected
by EPS deployment, CSFB has no impact on the total number of UEs that request CS services
within a network.
Load-based CSFB to UTRAN prevents PS handover preparation failure caused by UTRAN
cell congestion, because the eNodeB selects a target cell based on the UTRAN cell load
status. This increases system capacity.
CSFB mechanisms affect signaling overhead as follows:
l If redirection is used as the CSFB mechanism, no extra signaling message is required for
the UTRAN because each CSFB procedure is equivalent to the initiation of a new CS
service. The EPS does not need to interact with the target network, and the
corresponding signaling overhead is negligible.
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
Load-based CSFB to UTRAN prevents PS handover preparation failure caused by UTRAN
cell congestion, because the eNodeB selects a target cell based on the UTRAN cell load
status. This increase the CSFB delay.
CSFB affects the access success rate as follows:
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.

eRAN
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.
6.2 LOFD-001052 Flash CS Fallback to UTRAN

System Capacity
within a network.
Extra signaling messages are required only during eNodeB deployment.
l Afterward, signaling overhead is negligible because of infrequent system information

updates.
Network Performance
Flash CSFB to UTRAN decreases the CSFB delay by up to 1.28s because UEs obtain
information about the target UTRAN cell for redirection before RRC connections to the LTE
network are released.
Flash CSFB affects the access success rate as follows:
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.
6.3 LOFD-070202 Ultra-Flash CSFB to UTRAN

System Capacity
No impact.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to UTRAN by 1
second, improving user experience.

eRAN
6.4 LOFD-001068 CS Fallback with LAI to UTRAN

System Capacity
No impact.
Network Performance
CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has
attached. This prevents CSFB failure or long delay caused by incorrect target RAT selection
and increases the CSFB success rate.
6.5 LOFD-001088 CS Fallback Steering to UTRAN

System Capacity
No impact.
Network Performance
Using this feature, an operator that owns inter-RAT networks can specify the target RAT and
frequency for CSFB based on the network plan and network load balancing requirements and
thereby improve network operating efficiency.
If the frequency with the highest priority is inappropriately configured, for example, if the
highest-priority frequency has coverage holes, a UE may fail to measure this frequency and
therefore the CSFB delay increases.
This feature may conflict with the service-based directed retry decision (DRD) algorithm used
for UTRAN, thereby affecting user experience. For example, if a CS service is initiated for a
UE that is performing PS services, the eNodeB may select a High Speed Packet Access
(HSPA) frequency used in UTRAN for CSFB based on configured policies. However, if the
UE requests CS bearer establishment first after the fallback, the UTRAN may transfer the UE
to an R99 frequency.
6.6 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering

System Capacity
No impact.
Network Performance
E-UTRAN to UTRAN CS/PS Steering enables an eNodeB to include only UTRAN
frequencies with a high CS service priority in measurement configurations. This prevents
redundant measurements, reduces the measurement time, and decreases end-to-end CSFB
delay.

eRAN
If the CS service priorities of UTRAN frequencies configured on the eNodeB are consistent
with those configured at the UTRAN side, E-UTRAN to UTRAN CS/PS Steering prevents
further intra-UTRAN handovers for service steering.
6.7 LOFD-001034 CS Fallback to GERAN

System Capacity
within a network.
CSFB mechanisms affect signaling overhead as follows:
l CSFB mechanisms affect signaling overhead as follows: If redirection or CCO without

NACC is used as the CSFB mechanism, no extra signaling message is required for the
GERAN because each CSFB procedure is equivalent to the initiation of a new CS
service. The EPS does not need to interact with the target network. Therefore, signaling
overhead is negligible.
l If CCO with NACC is used as the CSFB mechanism, extra signaling messages are
required only during eNodeB deployment.
l Afterward, signaling overhead is negligible because of infrequent system information
updates. If PS handover is used as the CSFB mechanism, extra signaling messages are
required from each NE for the request, preparation, and execution of each handover.
However, from the perspective of traffic statistics, the number of UEs that initiate CS
services per second per cell during peak hours is far below cell capacity. Therefore,
signaling overhead caused by PS handovers is low.
Network Performance
CSFB affects the access success rate as follows:
l If redirection or CCO/NACC is used as the CSFB mechanism, each CSFB procedure is

equivalent to the initiation of a new CS service. Therefore, the access success rate for
CSFB UEs is theoretically the same as that for normal CS UEs in the GERAN.
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 UEs in the GERAN.
6.8 LOFD-001053 Flash CS Fallback to GERAN

System Capacity
within a network.

eRAN
CSFB mechanisms affect signaling overhead as follows: Flash CSFB affects signaling
overhead as follows: Extra signaling messages are required only during eNodeB deployment.
Afterward, signaling overhead is negligible because of infrequent system information updates.
Network Performance
If flash CSFB is used as the CSFB mechanism, each CSFB procedure is equivalent to the
initiation of a new CS service. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the GERAN.
Flash CSFB to GERAN decreases the CSFB delay by up to 2s because UEs obtain
information about the target GERAN cell for redirection before RRC connections to the LTE
network are released.
6.9 LOFD-081283 Ultra-Flash CSFB to GERAN

System Capacity
When DRX measurements are used, there is a higher probability that the UE enters the DTX
sleep state, affecting the scheduling by decreasing the cell throughput.
Network Performance
Compared with standard CSFB, this feature reduces the delay of CSFB to GERAN by 2
seconds, improving user experience.
6.10 LOFD-001069 CS Fallback with LAI to GERAN

System Capacity
No impact.
Network Performance
CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has
attached. This prevents CSFB failure or long delay caused by incorrect target RAT selection
and increases the CSFB success rate.
6.11 LOFD-001089 CS Fallback Steering to GERAN

System Capacity
No impact.
Network Performance
Using this feature, an operator that owns inter-RAT networks can specify the target RAT and
frequency for CSFB based on the network plan and network load balancing requirements and
thereby improve network operating efficiency.

eRAN
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.

eRAN
CS Fallback Feature Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 LOFD-001033 CS Fallback to UTRAN

This section provides engineering guidelines for LOFD-001033 CS Fallback to UTRAN.
7.1.1 When to Use CS Fallback to UTRAN

Use LOFD-001033 CS Fallback to UTRAN in the initial phase of LTE network deployment
when both of the following conditions are met:
l The operator owns a mature UTRAN network.

l The LTE network does not provide VoIP services, or UEs in the LTE network do not
support VoIP services.
For policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT
Mobility Management in Connected Mode. If UTRAN and E-UTRAN cells cover the same
area, or the UTRAN cell provides better coverage than the E-UTRAN cell, use CSFB based
on blind handover to decrease the CSFB delay.
7.1.2 Required Information

1. Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN
and UTRAN cells. Information about coverage areas includes engineering parameters of
sites (such as latitude and longitude), TX power of cell reference signals (RSs), and
neighbor relationship configurations.
2. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core
networks, and ensure that they all support CSFB. Table 7-1 describes the requirements
of CSFB to UTRAN for the core networks.
3. Collect the following information about the UEs that support UMTS and LTE on the live
network:
Supported frequency bands
Whether the UEs support redirection from E-UTRAN to UTRAN
Whether the UEs support PS handover from E-UTRAN to UTRAN
Whether the UEs support UTRAN measurements

eRAN
This information is used to configure neighboring UTRAN cells and to determine

whether to perform CSFB based on handover or redirection. For details, see Inter-RAT
Mobility Management in Connected Mode.
4. Collect information about the RNC, MME, and SGSN to check whether they all support
RIM procedures.
Table 7-1 Requirements of CSFB to UTRAN for core networks

NE Requirement
MME l Supports: SGs interface to the MSC

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

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

RAU/LAU procedure initiated by the UE.
7.1.3 Requirements
Operating Environment
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 7-2.

eRAN
Table 7-2 License control item for CSFB to UTRAN

Feature ID Feature Model License NE Sales Unit
Name Control
Item
LOFD-001033 CSFB to LT1S00C CS Fallback eNodeB per RRC

UTRAN FBU00 to Connected
UTRAN(FD User
D)
7.1.4 Precautions
None
7.1.5 Data Preparation and Feature Activation
7.1.5.1 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for
a specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
Before configuring CSFB to 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 UTRA frequencies.
2. UtranExternalCell: used to configure external UTRAN cells. The
UtranExternalCell.Rac parameter must be set.
3. UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external UTRAN cell. This MO is required only if the NodeB that provides the external
UTRAN cell works in RAN sharing with common carriers mode and multiple operators
share the external UTRAN cell.
4. The following table describes the parameters that must be set in the UtranNCell MO to
configure the neighbor 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.

eRAN
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to set the eNodeB-level handover mode and handover algorithm switches for CSFB to
UTRAN.
Paramet Parame Data Setting Notes

er Name ter ID Source
Handover ENodeB Network Set this parameter based on the network plan.
Mode AlgoSwi plan To activate PS handovers, select the
switch tch.Ho (negotiation UtranPsHoSwitch(UtranPsHoSwitch) check box.
ModeSw not If this check box is not selected, redirection will be
itch required) used for CSFB to UTRAN.
Handover ENodeB Network To activate CSFB to UTRAN, select the

Algo AlgoSwi plan UtranCsfbSwitch(UtranCsfbSwitch) check box.
switch tch.HoA (negotiation To activate load-based CSFB, select the
lgoSwitc not CSFBLoadInfoSwitch check box.
h required)
The following table describes the parameters that must be set in the ENodeBAlgoSwitch and
CellHoParaCfg MOs to set eNodeB- and cell-level blind handovers.

Handover ENodeB Network To activate blind handovers, select the

Mode AlgoSwi plan BlindHoSwitch(BlindHoSwitch) check box under
switch tch.Ho (negotiation the parameter. If the
ModeSw not BlindHoSwitch(BlindHoSwitch) check box is
itch required) deselected, blind handovers for all cells under the
eNodeB are invalid.
Handover CellHo Network To activate blind handovers for a cell under the
Mode ParaCf plan eNodeB, select the
switch g.HoMo (negotiation BlindHoSwitch(BlindHoSwitch) check box under
deSwitc not the parameter. If the
h required) BlindHoSwitch(BlindHoSwitch) check box is
deselected, blind handovers for the cell are invalid.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set the blind-handover priorities of different RATs for CSFB.

eRAN
Param Parameter Data Setting Notes

eter ID Source
Name
CN CSFallBack Networ Set this parameter based on the network plan. This
Operat BlindHoCfg. k plan parameter identifies the operator whose RAT blind-
or ID CnOperatorI (negoti handover priorities are to be set.
d ation
not
require
d)
Highes CSFallBack Networ Set this parameter based on the network plan. This
t BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
priority InterRatHig (negoti the highest-priority RAT to be considered in blind
InterRa hestPri ation handovers for CSFB. For CSFB to UTRAN, retain the
t not default value.
require
d)
Second CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to GERAN by default and specifies
InterRa InterRatSeco (negoti the second-highest-priority RAT to be considered in
t ndPri ation blind handovers for CSFB. Ensure that this parameter
not is set to a different value from the InterRatHighest-
require Pri and InterRatLowestPri parameters.
d)
Lowest CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to CDMA2000 by default and
InterRa InterRatLow (negoti specifies the low-priority RAT to be considered in
t estPri ation blind handovers for CSFB. Ensure that this parameter
require Pri and InterRatSecondPri parameters.
d)
UTRA CSFallBack Networ Set this parameter based on the network plan. This
N LCS BlindHoCfg. k plan parameter specifies the LCS capability of the
capabil UtranLcsCa (negoti UTRAN.
ity p ation
not
require
d)
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO
to activate load-based CSFB.

eRAN
Paramete Parameter Data Source Setting Notes

r Name ID
Handover ENodeBAlg Network plan To activate load-based CSFB, select the

Algo oSwitch.Ho (negotiation not CSFBLoadInfoSwitch(CSFBLoadInfo
switch AlgoSwitch required) Switch) check box.
The following table describes the parameter that must be set in the GlobalProcSwitch MO to
set load-based CSFB to UTRAN.
Parameter Parameter Data Setting Notes

Name ID Source
Choose GlobalProcS Network Set this parameter to BASED_ON_RIM to

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

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

eRAN

r Name ID
Max Utran InterRatHoC Network plan The default value is 0, indicating that no
cell num omm.UtranC (negotiation system information of any neighboring
in CSFB ellNumForE not required) UTRAN cells is sent to UEs for
EMC mcRedirect emergency redirections. Operators can set
redirection this parameter to 0 through 16 based on
the network plan. After the CSFB
protection timer expires, the eNodeB
performs an emergency redirection. If the
signal quality of the serving cell is poor
and this parameter is set to a large value,
the eNodeB may fail to send the system
information of neighboring UTRAN cells
to UEs.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg
MO to specify the CSFB policy.
Para Parameter Data Source Setting Notes

meter ID
Name
CSFB CSFallBack Network plan Set this parameter based on the network plan.
hando PolicyCfg.Cs (negotiation The default values are REDIRECTION,
ver fbHoPolicyC not required) CCO_HO, and PS_HO. You are advised to set
policy fg this parameter based on the UE capabilities and
Config network capabilities.
uratio NOTE
n If none of the three options is selected and
measurement-based mobility is enabled, the eNodeB
does not perform CSFB for a UE until the CSFB
protection timer expires. Then the eNodeB performs
a blind redirection for the UE. If blind handover is
enabled, the eNodeB directly performs a blind
redirection for the UE.
CCO_HO applies only to CSFB to GERAN.
The following table describes the parameter that must be set in the CSFallBackBlindHoCfg
MO to set the round-robin switch when multiple frequencies are of the same priority for
CSFB-based blind redirections.

eRAN
Para Parameter Data Source Setting Notes

meter ID
Name
CSFB CSFallBack Network plan Set this parameter based on the network plan.
to BlindHoCfg. (negotiation The option is cleared by default. When the UE
UTRA UtranCsfbBl not required) needs to perform a blind redirection and
N indRedirRrS multiple frequencies are of the same priority,
Blind w the option can be selected to ensure that the UE
Redire accesses each frequency equally. In addition,
ction you are advised to plan neighboring cells on the
RR frequencies and neighboring frequencies, and
Switch neighboring cell priorities before selecting the
option.
The following table describes the parameter that must be set in the ENBRSVDPARA MO to
set the random procedure selection optimization for CSFB.
Paramete Parameter ID Data Source Setting Notes

r Name
Reserved ENBRSVDPARA.Rs Network plan Select the RsvdSwPara1_bit23

Switch vdSwPara1 (negotiation option when CSFB selects a target
Parameter not required) frequency or cell to enter the
1 random selection procedure. This
ensures that each frequency or cell
is selected evenly.
7.1.5.2 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 7-3 in a summary data file, which also
contains other data for the new eNodeBs to be deployed.
Then, import the summary data file into the Configuration Management Express (CME) for
batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in
the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 7-3 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the
file.
l Some MOs in Table 7-3 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
When configuring neighboring cells, you are advised to use the radio data planning file. For
details about how to fill in and export the radio data planning file, see section "Creating
eNodeBs in Batches" in the initial configuration guide for the eNodeB.

eRAN
Table 7-3 Parameters for CSFB to UTRAN
MO Sheet in the Parameter Group Remarks

Summary Data
File
UtranNFreq UtranNFreq See 7.1.5.1 Data The RNP template sheet is

Preparation. recommended.
UtranExternal UtranExternalCe See 7.1.5.1 Data The RNP template sheet is

Cell ll Preparation. recommended.
UtranExternal UtranExternalCe See 7.1.5.1 Data The RNP template sheet is

CellPlmn llPlmn Preparation. recommended.
UtranNCell UtranNCell See 7.1.5.1 Data The RNP template sheet is

ENodeBAlgo User-defined See 7.1.5.1 Data This parameter must be

Switch sheet. Preparation. customized on a list-type
ENodeBAlgoSw sheet of the template.
itch is
recommended.
CSFallBackB User-defined See 7.1.5.1 Data This parameter must be

lindHoCfg sheet. Preparation. customized on a list-type
CSFallBackBlin sheet of the template.
dHoCfg is
recommended.
CellHoParaCf User-defined See 7.1.5.1 Data This parameter must be

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

o sheet. Preparation. customized on a list-type
CSFallBackHo sheet of the template.
is recommended.
InterRatHoCo User-defined See 7.1.5.1 Data None

mm sheet. Preparation.
InterRatHoCo
mm is
recommended.
7.1.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch Activated
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.

eRAN
Batch Reconfiguration
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure.
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press
F1 when a CME window is active, and select Managing the CME > CME Guidelines >
LTE Application Management > eNodeB Related Operations > Customizing a Summary
Data File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts. For
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End
7.1.5.4 Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.

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

Basic scenario 1: CSFB to UTRAN using blind redirection
CSFB to UTRAN using blind redirection works regardless of whether neighboring UTRAN
cells are configured.
l If you want to configure a neighboring UTRAN cell, you must configure the
UtranNFreq and UtranNCell MOs. For details about parameter settings, see Inter-RAT
l If you do not want to configure a neighboring UTRAN cell, you must configure the
UtranRanShare or UtranExternalCell MO. For details about parameter settings, see
Inter-RAT Mobility Management in Connected Mode.
Step 1 Run the MOD ENODEBALGOSWITCH command with the

UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter
selected.
Step 2 Run the following eNodeB- and cell-level commands to enable blind handovers for CSFB to
UTRAN:

eRAN
1. Run the MOD ENODEBALGOSWITCH command with the

BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter
selected.
2. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Handover Mode switch parameter selected.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO
options of the CSFB handover policy Configuration parameter deselected and the
REDIRECTION option of the same parameter selected.
Step 4 (Optional) If you require setting UTRAN as having the highest priority for CSFB, run the
MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat
parameter set to UTRAN and the Second priority InterRat parameter set to GERAN.
Step 5 (Optional) If a neighboring UTRAN cell is configured, run the MOD UTRANNCELL
command with the Blind handover priority parameter set to the highest priority (32).
Step 6 (Optional) If no neighboring UTRAN cell is configured, run the MOD UTRANNFREQ
command with the Frequency Priority for Connected Mode parameter set to the highest
priority (8).
Step 7 (Optional) Run the MOD CSFALLBACKBLINDHOCFG command to turn on the CSFB to
UTRAN blind redirection RR switch.
----End
Basic scenario 2: CSFB to UTRAN using blind handover
Step 1 Add neighboring UTRAN frequencies and neighbor relationships with UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

selected.
Step 3 Run the following eNodeB- and cell-level commands to enable blind handovers for CSFB to
UTRAN:
selected.
2. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
Step 5 Run the MOD UTRANNCELL command with the Blind handover priority parameter set
to 32.
----End
Basic scenario 3: CSFB to UTRAN using measurement-based redirection

eRAN

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.
options of the CSFB handover policy Configuration parameter deselected and the
----End
Basic scenario 4: CSFB to UTRAN using measurement-based handovers
UtranCsfbSwitch(UtranCsfbSwitch) check box selected under the Handover Algo switch
and the UtranPsHoSwitch(UtranPsHoSwitch) check box selected under the Handover
Mode switch parameter.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
----End
Enhanced scenario: Load-based CSFB to UTRAN To activate load-based CSFB to UTRAN,
run the following commands after the commands in a basic scenario are executed:

CSFBLoadInfoSwitch(CSFBLoadInfoSwitch) check box selected under the Handover
Algo switch parameter.
Step 2 Run the MOD GLOBALPROCSWITCH command with the Choose UTRAN Cell Load
Info Trans Channel parameter set to BASED_ON_RIM.
----End
MML Command Examples

Basic scenario 1: CSFB to UTRAN using blind redirection (configured with neighboring
UTRAN cells)
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1,
HoModeSwitch=BlindHoSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,
InterRatSecondPri=GERAN;
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123,

eRAN
BlindHoPriority=32;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;
Basic scenario 1: CSFB to UTRAN using blind redirection (configured with no neighboring
UTRAN cell)
MOD UTRANNFEQ: LocalCellId=0, UtranDlArfcn=9700, ConnFreqPriority=8;
MOD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=9700, Mcc="460", Mnc="20";
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;
Basic scenario 2: CSFB to UTRAN using blind handovers

HoModeSwitch=UtranPsHoSwitch-1&BlindHoSwitch-1;
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123,
BlindHoPriority=32;
Basic scenario 3: CSFB to UTRAN using measurement-based redirection

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

MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms,
CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13, CsfbProtectionTimer=4;
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123;
Enhanced scenario: Load-based CSFB to UTRAN To activate load-based CSFB to UTRAN,

run the following commands after the commands in a basic scenario are executed:
MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-1;
MOD GLOBALPROCSWITCH: UtranLoadTransChan=BASED_ON_RIM;
7.1.6 Activation Observation
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
The activation observation procedure for load-based CSFB to UTRAN is as follows:

eRAN
Two UTRAN cells A and B report MRs and are under overload control and in the normal
state, respectively. The RSCP of cell A is larger than that of cell B.
Enable a UE to perform a PS-handover-based CSFB when both cell A and cell B provides
services correctly.
1. If the RSCP of cell B meets the handover requirements, the eNodeB transfers the UE to
cell B.
2. If cell B is blocked and the RSCP of cell A meets the handover requirements, the
eNodeB transfers the UE to cell A and the UE can access the network through
preemption or queuing.
Figure 7-2 and Figure 7-3 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.

eRAN
Figure 7-2 Redirection-based CSFB to UTRAN for a mobile-originated call

eRAN
Figure 7-3 Redirection-based CSFB to UTRAN for a mobile-terminated call
If the UE capability is not included in the Initial Context Setup Request (Initial Context Setup
Req in the figures) message, the eNodeB initiates a UE capability transfer procedure
immediately after receiving this message from the MME. If the UE capability is included in
the Initial Context Setup Request message, the eNodeB initiates a UE capability transfer
procedure after sending an Initial Context Setup Response (Initial Context Setup Rsp in the
figures) message to the MME.
If measurement-based redirection is used for CSFB to UTRAN, the eNodeB delivers the B1-
related measurement configuration.
If blind redirection is used for CSFB to UTRAN, the eNodeB does not deliver the B1-related
measurement configuration but sends an RRC Connection Release (RRC Conn Rel in the
figures) message to the UE. As shown in the red and green boxes in Figure 7-4, in the RRC
Connection Release message, the cause value is "other" and the target RAT is UTRAN. For an
emergency call, the cause value is "CSFBhighpriority."

eRAN
Figure 7-4 The RRC Connection Release message during CSFB to UTRAN
If PS handover is used for CSFB to UTRAN, the eNodeB initiates a PS handover procedure
after receiving a measurement report from the UE, instead of sending an RRC Connection
Release message to the UE. Figure 7-5 shows the PS handover procedure. As shown in the
red and green boxes in Figure 7-6, in the handover command sent over the air interface, the
cs-FallbackIndicator IE is TRUE and the target RAT is UTRAN.
Figure 7-5 PS handover procedure

eRAN
Figure 7-6 The MobilityFromEUTRAN message during CSFB to UTRAN
MML Command Observation

The activation observation procedure for load-based CSFB to UTRAN is as follows: Run the
DSP UTRANRIMLOADINFO command to query neighboring UTRAN cell load status to
check whether load-based CSFB has been activated.
If the neighboring UTRAN cell load status is displayed, load-based CSFB has been activated.
Counter Observation
Table 7-4 lists the performance counters for observing functions related to CSFB to UTRAN.
Table 7-4 Performance counters for observing CSFB to UTRAN
Function Counter Counter Description

ID Name
CSFB to 152672832 L.CSFB.E2W Number of times CSFB to UTRAN is

UTRAN 3 performed
CSFB to 152672870 L.CSFB.E2W. Number of times CSFB to UTRAN is

UTRAN 9 Emergency triggered for emergency calls
triggered for
emergency calls
RIM during 152672894 L.RIM.Load. Number of load information requests

load-based 9 E2W.Req sent from an eNodeB to a UMTS
CSFB to network
UTRAN
152672895 L.RIM.Load. Number of load information responses
0 E2W.Resp sent from a UMTS network to an
eNodeB
152672895 L.RIM.Load. Number of load information updates

1 E2W.Update sent from a UMTS network to an
eNodeB

eRAN
7.1.7 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Batch Reconfiguration. In the procedure, modify parameters
according to Table 7-5.
Table 7-5 Parameters for deactivating CSFB to UTRAN

MO Sheet in the Parameter Setting Notes
Summary Data File Group
ENodeBAlgoSwit User-defined sheet. HoAlgoSwit To deactivate CSFB to

ch ENodeBAlgoSwitch ch UTRAN, set
is recommended. UtranCsfbSwitch under the
HoAlgoSwitch parameter to
0.
To deactivate only load-
based CSFB to UTRAN, set
CSFBLoadInfoSwitch
under the HoAlgoSwitch
parameter to 0.
To deactivate only adaptive-
blind-handover-based CSFB,
set CsfbAdaptiveBlindHoS-
witch to 0.
Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 7-5. For detailed instructions, see 7.1.5.4
Using the CME to Perform Single Configuration for feature activation.
Using MML Commands

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

eRAN

l Deactivating CSFB to UTRAN
l Deactivating only load-based CSFB to UTRAN

MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-0;
l Deactivating adaptive-blind-handover-based CSFB

MOD ENODEBALGOSWITCH: HoAlgoSwitch=CsfbAdaptiveBlindHoSwitch-0;
7.1.8 Performance Monitoring

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

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

from the eNodeB
Table 7-7 lists the counter related to CSFB to UTRAN.
Table 7-7 Counter related to CSFB to UTRAN
1526728323 L.CSFB.E2W Number of procedures for CSFB to

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

n.E2W.CSFB UTRANs to WCDMA network

eRAN
1526728504 L.IRATHO.E2W. Number of CSFB-based inter-RAT handover

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

n.E2W.CSFB.Tim from E-UTRAN to WCDMA network
eOut caused by CSFB protection timer expiration
Table 7-10 lists the counters related to CSFB for emergency calls.
Table 7-10 Counters related to CSFB for emergency calls

1526729510 L.IRATHO.E2W. Number of CSFB-based handover execution

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

CSFB.ExecSuccO executions to WCDMA network triggered
ut.Emergency 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
7.1.9 Parameter Optimization

CSFB end-to-end delay includes the processing time at the LTE side and that at the side after
fallback. Processing at any side may affect the CSFB end-to-end delay and user experience.
l If GSM devices are provided by Huawei, for details about processing at the GSM side,
see Interoperability Between GSM and LTE Feature Parameter Description.
l If UMTS devices are provided by Huawei, for details about processing at the UMTS
side, see Interoperability Between UMTS and LTE Feature Parameter Description.

eRAN
Blind Handover for CSFB

Compared with measurement-based handovers, blind handovers reduce access delays but
affect handover success rates.
The following table describes the parameters in the CSFallBackBlindHoCfg MO used to set
the blind-handover priorities of different RATs for CSFB.

Name ID Source
CN CSFallBac Network Set this parameter based on the network plan.

Operator kBlindHo plan This parameter specifies the ID of the operator
ID Cfg.CnOpe (negotiatio whose RAT blind-handover priorities are to be
ratorId n not set.
required)
Highest CSFallBac Network Set this parameter based on the network plan.
priority kBlindHo plan This parameter is set to UTRAN by default and
InterRat Cfg.InterR (negotiatio specifies the highest-priority RAT to be
atHighestP n not considered in blind handovers for CSFB.
ri required)
Second CSFallBac Network Set this parameter based on the network plan.
priority kBlindHo plan This parameter is set to GERAN by default and
InterRat Cfg.InterR (negotiatio specifies the second-highest-priority RAT to be
atSecondP n not considered in blind handovers for CSFB. Ensure
ri required) that this parameter is set to a different value from
the InterRatHighestPri and InterRatLowestPri
parameters.
Lowest CSFallBac Network Set this parameter based on the network plan.
priority kBlindHo plan This parameter is set to CDMA2000 by default
InterRat Cfg.InterR (negotiatio and specifies the low-priority RAT to be
atLowestPr n not considered in blind handovers for CSFB. Ensure
i required) that this parameter is set to a different value from
the InterRatHighestPri and InterRatSecondPri
parameters.

eRAN
Parameter Paramete Data Setting Notes

Name r ID Source
Handover ENodeBA Network To activate blind handovers, select the

Mode switch lgoSwitch. plan BlindHoSwitch(BlindHoSwitch) check box. A
HoModeS (negotiati blind handover to an inter-RAT cell can be
witch on not performed only if a blind-handover priority is
required) specified for the inter-RAT cell. Compared with
measurement-based handovers, blind handovers
reduce access delays but affect handover success
rates.
To deactivate blind handovers, clear the
BlindHoSwitch(BlindHoSwitch) check box.
Handover CellHoPar Network To activate blind handovers for a cell under the
Mode switch aCfg.HoM plan eNodeB, select the
odeSwitch (negotiati BlindHoSwitch(BlindHoSwitch) check box
on not under the parameter. If the
required) BlindHoSwitch(BlindHoSwitch) check box is
deselected, blind handovers for the cell are
invalid.
Measurement-based Handovers for CSFB

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

er Name ID Source
Local cell CSFallBac Network Set this parameter based on the network plan.
ID kHo.Local plan
CellId (negotiatio
n not
required)

eRAN

er Name ID Source
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.
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.

eRAN
7.2 RIM Procedure from E-UTRAN to UTRAN
7.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN

It is recommended that the RIM procedure be performed through the Huawei-proprietary
eCoordinator if the following two conditions are met: 1. Both the eNodeB and the RNC/BSC
are provided by Huawei and are connected to the same eCoordinator. 2. The core network that
the eNodeB and the RNC/BSC are connected to does not support the RIM procedure or is not
enabled with the RIM procedure. To perform the RIM procedure through the eCoordinator, set
ENodeBAlgoSwitch.RimOnEcoSwitch to ON(On).
In other conditions, it is recommended that the RIM procedure be performed through the core
network. In this case, set ENodeBAlgoSwitch.RimOnEcoSwitch to OFF(Off).
If load-based CSFB to UTRAN is used, you need to obtain load information about UTRAN
cells through the RIM procedures. If flash CSFB to UTRAN is used, you need to obtain
system information about UTRAN cells through the RIM procedures.

Check whether the RNC, MME, and SGSN support the RIM procedure, and whether an
eCoordinator has been deployed.
7.2.3 Requirements
If the RIM procedure is performed through the core network, the core-network equipment
must support this feature:
If the 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

eRAN
Table 7-11 License control item for CSFB to UTRAN

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

UTRAN FBU00 to Connected
UTRAN(FD User
D)
NOTE
If the UTRAN uses Huawei devices, corresponding licenses need to be activated. For details, see the
engineering guidelines for WRFD-150231 RIM Based UMTS Target Cell Selection for LTE in
Interoperability Between UMTS and LTE Feature Parameter Description.
7.2.4 Precautions
None

operator
Required Data
The required data is the same as that for LOFD-001033 CS Fallback to UTRAN. For details,
see 7.1.5.1 Data Preparation.
UtranExternalCell: used to configure external UTRAN cells. The UtranExternalCell.Rac

parameter must be set.
to configure the RIM procedure.

eRAN

Name ID Source
Support RIM ENodeBAlg Network If ENodeBAlgoSwitch.RimOnEcoSwitch

by oSwitch.Rim plan is set to OFF(Off), the RIM procedure is
eCoordinator OnEcoSwitc (negotiatio performed through the core network.
Switch h n not If ENodeBAlgoSwitch.RimOnEcoSwitch
required) is set to ON(On), the RIM procedure is
performed through the eCoordinator.
eNodeBs
file.
parameters.
Table 7-12 Parameters for the RIM procedure

Summary Data
File
ENodeBAlgoSwit User-defined sheet. See 7.2.5.1 Data None

ch ENodeBAlgoSwitc Preparation.
h is recommended.
multiple eNodeBs in a single procedure. The procedure is as follows:

eRAN
data file into the CME, and then start the data verification.
----End

window.

eRAN
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
Using MML Commands

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

MOD ENODEBALGOSWITCH: RimOnEcoSwitch=OFF;

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

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

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

Update information updates from WCDMA network

eRAN
Signaling Tracing Result Observation

If the RIM procedure is performed through the core network, trace signaling messages as
follows:
Step 1 Start an S1 interface tracing task on the eNodeB LMT.

Check whether the eNB DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-REQUEST IE is sent over the S1 interface. If the message is sent, you
can infer that the eNodeB has sent the RIM request successfully.
Step 2 Start an Iu interface tracing task on the RNC LMT.
If after receiving the DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMATION-REQUEST IE, the RNC sends the DIRECT INFORMATION TRANSFER
message containing the RAN-INFORMAION IE to the SGSN, you can infer that the RNC
can response to the RIM request normally.
Step 3 Change the state of the UTRAN cell.
If the RNC sends the DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMATION IE over the Iu interface, you can infer that the RNC can notify the eNodeB
with the cell state change through the RIM procedure.
----End
If the RIM procedure is performed through the eCoordinator, trace signaling messages as
follows:
Step 1 Start an Se interface tracing task on the eNodeB LMT.

Check whether the ENB DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMAION-REQUEST IE is sent over the Se interface. If the message is sent, you
Step 2 Start an Sr interface tracing task on the RNC LMT.
If after receiving the ECO DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMAION-REQUEST IE, the RNC sends the RNC DIRECT INFORMATION
TRANSFER message containing the RAN-INFORMAION IE to the eCoordinator, you can
infer that the RNC can response to the RIM request normally.
Step 3 Change the state of the UTRAN cell.
If the RNC sends the RNC DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION IE over the Sr interface, you can infer that the RNC can notify the
eNodeB with the cell state change through the RIM procedure.
----End
7.2.7 Deactivation
feature activation described in 7.2.5.3 Using the CME to Perform Batch Configuration for

eRAN
Existing eNodeBs. In the procedure, modify parameters according to the table listed in the
scenario of E-UTRAN to UTRAN CS/PS steering.

Summary Data Group
File
ENodeBAlgoS User-defined RimOnEcoSwitc Set this parameter to OFF(Off).

witch sheet. h
(eNodeB-level ENodeBAlgoSwi
switch) tch is
recommended.

Using MML Commands




The performance monitoring procedure for this feature is the same as that for CSFB to
UTRAN. For details, see 7.1.8 Performance Monitoring.

The parameter optimization procedure for this feature is the same as that for CSFB to
UTRAN. For details, see 7.1.9 Parameter Optimization.
7.3 LOFD-001052 Flash CS Fallback to UTRAN

This section provides engineering guidelines for LOFD-001052 Flash CS Fallback to
UTRAN.

eRAN
7.3.1 When to Use Flash CS Fallback to UTRAN

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

1. Collect information about whether LOFD-001033 CS Fallback to UTRAN has been
activated.
and UTRAN cells. Information about coverage areas includes engineering parameters of
networks, and ensure that they all support CSFB and the RIM procedure. Table 7-15
describes the requirements of flash CSFB to UTRAN for the core networks. For details
about the deployment guide on the UTRAN, see Interoperability Between UMTS and
LTE Feature Parameter Description.
network:
Whether the UEs comply with 3GPP Release 9 specifications
Table 7-15 Requirements of flash CSFB to UTRAN for core networks

NE Requirement
MME Supports CSFB and RIM procedures in compliance with 3GPP

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

Release 9

eRAN
7.3.3 Requirements
License
Table 7-16 License control item for Flash CS Fallback to UTRAN

Name Control
Item
LOFD-001052 Flash CSFB LT1S0FC Flash CS eNodeB per RRC

to UTRAN FBU00 Fallback to Connected
UTRAN User
NOTE
If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN. For
details, see Flash CS Fallback Based on RIM Feature Parameter Description.
7.3.4 Precautions
None

operator
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with
UTRAN cells. This section provides only the information about MOs related to neighboring

eRAN
UTRAN cells and key parameters in these MOs. For more information about how to collect
data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description. Collect data for the parameters in the following MOs:
1. UtranNFreq: used to configure neighboring UTRA 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 BTS that provides the external
GERAN cell works in RAN sharing with common carriers mode and multiple operators
share the external GERAN cell.
4. The following table describes the parameters that must be set in the UtranNCell MO to
configure the neighbor 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.
to set the handover mode and handover algorithm switches for flash CSFB to UTRAN.
Parameter Parameter Data Source Setting Notes

Name ID
Handover ENodeBAlg Network plan Set this parameter based on the network
Mode switch oSwitch.Ho (negotiation plan.
ModeSwitch not required)
Handover Algo ENodeBAlg Network plan To activate flash CSFB to UTRAN,

switch oSwitch.Ho (negotiation select the
AlgoSwitch not required) UtranCsfbSwitch(UtranCsfbSwitch)
and UtranFlashCsfbS-
witch(UtranFlashCsfbSwitch) check
boxes.

eRAN
Parameter Parameter Data Source Setting Notes

Name ID
RIM switch ENodeBAlg Network plan UTRAN_RIM_SWITCH(UTRAN

oSwitch.Ri (negotiation RIM Switch) under this parameter
mSwitch not required) specifies whether to enable or disable
the RIM procedure that requests event-
driven multiple reports from UTRAN
cells.
If this switch is turned on, the eNodeB
can send RAN-INFORMATION-
REQUEST/Multiple Report protocol
data units (PDUs) to UTRAN cells to
request event-driven multiple reports.
If this switch is turned off, the eNodeB
cannot send RAN-INFORMATION-
REQUEST/Multiple Report PDUs to
UTRAN cells.
If this switch is turned off and
UtranFlashCsfbS-
witch(UtranFlashCsfbSwitch) under
ENodeBAlgoSwitch.HoAlgoSwitch is
turned on, the eNodeB sends RAN-
INFORMATION-REQUEST/Single
Report PDUs to UTRAN cells to
request single reports.
If the UTRAN cells support RAN-
INFORMATION-REQUEST/Multiple
Report PDUs, you are advised to select
the UTRAN_RIM_SWITCH(UTRAN
RIM Switch) option.

Handove ENodeB Network To activate blind handovers, select the

r Mode AlgoSwi plan BlindHoSwitch(BlindHoSwitch) check box under
eNodeB are invalid.

eRAN

Handove CellHo Network To activate blind handovers for a cell under the
r Mode ParaCf plan eNodeB, select the
The following table describes the parameter that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
Parameter Name Parameter ID Data Source Setting Notes
MME Release S1INTERFACE.M Network plan To activate RIM

meRelease (negotiation not procedures in
required) Multiple Report
mode, set the
parameter to
Release_R9(Releas
e 9).
Parameter Paramet Data Setting Notes

Name er ID Source
CN Operator CSFallB Network Set this parameter based on the network plan.
ID ackBlind plan This parameter identifies the operator whose
HoCfg.C (negotiation RAT blind-handover priorities are to be set.
nOperato not required)
rId
Highest CSFallB Network Set this parameter based on the network plan.
priority ackBlind plan This parameter is set to UTRAN by default
InterRat HoCfg.In (negotiation and specifies the highest-priority RAT to be
terRatHi not required) considered in blind handovers for CSFB. For
ghestPri CSFB to UTRAN, retain the default value.
Second CSFallB Network Set this parameter based on the network plan.
priority ackBlind plan This parameter is set to GERAN by default
InterRat HoCfg.In (negotiation and specifies the second-highest-priority RAT
terRatSec not required) to be considered in blind handovers for CSFB.
ondPri Ensure that this parameter is set to a different
value from the InterRatHighestPri and
InterRatLowestPri parameters.

eRAN
Parameter Paramet Data Setting Notes

Name er ID Source
Lowest CSFallB Network Set this parameter based on the network plan.
priority ackBlind plan This parameter is set to CDMA2000 by
InterRat HoCfg.In (negotiation default and specifies the low-priority RAT to
terRatLo not required) be considered in blind handovers for CSFB.
westPri Ensure that this parameter is set to a different
InterRatSecondPri parameters.
UTRAN CSFallB Network Set this parameter based on the network plan.
LCS ackBlind plan This parameter specifies the LCS capability of
capability HoCfg.U (negotiation the UTRAN.
tranLcsC not required)
ap
set the maximum number of neighboring UTRAN cells whose system information is sent to
UEs for redirections.
Paramete Paramete Data Source Setting Notes

r Name r ID
Max Utran InterRatH Network plan Set this parameter based on the network plan.
cell num in oComm.C (negotiation The default value is 8. If this parameter is set
redirection ellInfoMa not required) too small, the flash CSFB success rate
xUtranCel decreases because UEs may not receive valid
lNum neighboring cell system information. If this
parameter is set too large, the size of an RRC
connection release message increases and
CSFB may fail.
eNodeBs
file.

eRAN
parameters.
Table 7-17 Parameters for flash CSFB to UTRAN

Summary
Data File
UtranNFre UtranNFreq See 7.3.5.1 Data The RNP template sheet

q Preparation. is recommended.
UtranExter UtranExternalC See 7.3.5.1 Data The RNP template sheet

nalCell ell Preparation. is recommended.
UtranExter UtranExternalC See 7.3.5.1 Data The RNP template sheet

nalCellPlm ellPlmn Preparation. is recommended.
n
UtranNCell UtranNCell See 7.3.5.1 Data The RNP template sheet

Preparation. is recommended.
S1Interface S1Interface See 7.3.5.1 Data This parameter must be

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

goSwitch sheet. Preparation. customized on a list-type
ENodeBAlgoS sheet of the template.
witch is
recommended.
CSFallBac User-defined See 7.3.5.1 Data This parameter must be

kBlindHoC sheet. Preparation. customized on a list-type
fg CSFallBackBli sheet of the template.
ndHoCfg is
recommended.
InterRatHo User-defined See 7.3.5.1 Data This parameter must be

Comm sheet. Preparation. customized on a list-type
InterRatHoCo sheet of the template.
mm is
recommended.
CSFallBac User-defined See 7.3.5.1 Data This parameter must be

kHo sheet. Preparation. customized on a list-type
is
recommended.

eRAN

Summary
Data File
(Optional) User-defined See 7.3.5.1 Data This parameter must be

GlobalProc sheet. Preparation. customized on a list-type
Switch GlobalProcSwi sheet of the template.
tch is
recommended.
CellHoPara User-defined See 7.3.5.1 Data This parameter must be

Cfg sheet. Preparation. customized on a list-type
is
recommended.
Batch Activated

eRAN
----End

window.
----End
Using MML Commands

The prerequisite is that CSFB to UTRAN has been activated.

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

MOD ENODEBALGOSWITCH:
HoAlgoSwitch=UtranFlashCsfbSwitch-1,RimSwitch=UTRAN_RIM_SWITCH-1;
MOD S1INTERFACE:
S1InterfaceId=2,S1CpBearerId=1,CnOperatorId=0,MmeRelease=Release_R9;

Enable a UE to camp on an E-UTRAN cell and make a voice call. If the call continues and the
RRC Connection Release message traced on the Uu interface carries the information about
neighboring UTRAN cells, flash CSFB to UTRAN has been activated.
The signaling procedure for flash CSFB to UTRAN is similar to that for redirection-based
CSFB to UTRAN described in 7.1.6 Activation Observation. The difference is that the RRC
Connection Release message carries the information about neighboring UTRAN cells.

Check the status of the RIM procedure towards neighboring UTRAN cells by running the
DSP UTRANRIMINFO command. If the ID of a neighboring UTRAN cell is displayed in
the command output, the eNodeB has obtained the system information of this neighboring
UTRAN cell.
Counter Observation
Table 7-18 lists the performance counters for observing functions related to flash CSFB to
UTRAN.

eRAN
Table 7-18 Performance counters for observing flash CSFB to UTRAN

Function Counter Counter Name Description
ID
Flash CSFB to 152672870 L.FlashCSFB.E2W Number of times flash

UTRAN 5 CSFB to UTRAN is
performed
RIM during 152672894 L.RIM.SI.E2W.Req Number of system

flash CSFB to 6 information requests sent
UTRAN from an eNodeB to a UMTS
network
152672894 L.RIM.SI.E2W.Resp Number of system

7 information responses sent
from a UMTS network to an
eNodeB
152672894 L.RIM.SI.E2W.Update Number of system

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

MO Sheet in the Parameter Remarks
ENodeBAlgoSwit User-defined sheet HoAlgoSwit Set UtranFlashCsfbSwitch

ch ch under the HoAlgoSwitch
parameter to 0.

Using the CME to Perform Single Configuration described for feature activation.

eRAN
Using MML Commands

UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check box cleared under the Handover

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranFlashCsfbSwitch-0;

UTRAN. For details, see 7.1.8 Performance Monitoring.

7.4 LOFD-070202 Ultra-Flash CSFB to UTRAN
7.4.1 When to Use Ultra-Flash CSFB

When LOFD-001033 CS Fallback to UTRAN has been enabled, this feature is recommended
in scenarios where the eNodeB, RNC, MME, and MSC are provided by Huawei, and a
proportion of of UEs in the live network support SRVCC from E-UTRAN to UTRAN.

Before deploying this feature, collect the following information:
l LOFD-001033 CS Fallback to UTRAN has been activated.

l The eNodeB, RNC, MME, and MSC in the network are provided by Huawei and they all
support this feature.
l A proportion of UEs in the live network support SRVCC from E-UTRAN to UTRAN.
7.4.3 Requirements
This feature is a Huawei-proprietary feature and requires that the UTRAN, eNodeB, RNC,
MME, and MSC are provided by Huawei and support this feature. This feature is used with
MME11.0 and MSC11.0.
License

eRAN
Table 7-20 License information for ultra-flash CSFB to UTRAN
Feature ID Feature Name Model License NE Sales Unit

Control
Item
LOFD-070202 Ultra-Flash LT1SUFC Ultra-Flash eNodeB per RRC

CSFB to SFB00 CSFB to Connected
UTRAN UTRAN User
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.
7.4.4 Precautions
This feature is a Huawei-proprietary feature and is not supported by devices provided by other
vendors. In addition, this feature must first be activated on the RNC, MME, and MSC, and
then be activated on the eNodeB. This is because this feature is triggered by the eNodeB and
this avoids CSFB failures.

operator
Required Data
to set the handover mode and handover algorithm switches for ultra-flash CSFB to UTRAN.

eRAN

Name ID Source
Handover ENodeBAl Network Select the UtranUltraFlashCsfbS-

Algo switch goSwitch. plan witch(UtranUltraFlashCsfbSwitch) check
HoAlgoSw (negotiation box.
itch not required)
(Optional) ENodeBAl Network If some RNCs do not support ultra-flash

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

Network UtranN Network Clear the UltraFlashCsfbCapCfg check box for

Capabilit etwork plan RNCs that do not support ultra-flash CSFB to
y CapCfg. (negotiation UTRAN.
Configur Network required)
ation CapCfg
The following table describes the parameters that must be set in the
GLOBALPROCSWITCH MO to turn on the UE compatibility switch when UEs do not
support Ultra-Flash CSFB, resulting in UE compatibility problems.

Ue GlobalP Network Select the UltraFlashCsfbComOptSw option of

Compati rocSwit plan the parameter when UEs on the network do not
bility ch.UeC (negotiation support ultra-flash CSFB.
Switch ompatS required) When the MME provided by Huawei allows IMEI
witch whitelist configurations for ultra-flash CSFB and the
option is selected, the eNodeB performs ultra-flash
CSFB on UEs in the IMEI whitelist. Therefore,
delete the UEs that do not support ultra-flash CSFB
from the whitelist before selecting the option.
Otherwise, keep the option unselected.

eRAN
eNodeBs
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
file.
parameters.
Table 7-21 Parameters for ultra-flash CSFB to UTRAN

Summary
Data File
UtranNFreq UtranNFreq See 7.4.5.1 Data The RNP template sheet is

UtranExtern UtranExternalC See 7.4.5.1 Data The RNP template sheet is

alCell ell Preparation. recommended.
UtranExtern UtranExternalC See 7.4.5.1 Data The RNP template sheet is

alCellPlmn ellPlmn Preparation. recommended.
UtranNCell UtranNCell See 7.4.5.1 Data The RNP template sheet is

ENodeBAlg User-defined See 7.4.5.1 Data This parameter must be

oSwitch sheet. Preparation. customized on a list-type
witch is
recommended.
CSFallBack User-defined See 7.4.5.1 Data This parameter must be

BlindHoCfg sheet. Preparation. customized on a list-type
CSFallBackBli sheet of the template.
ndHoCfg is
recommended.

eRAN

Summary
Data File

Ho sheet. Preparation. customized on a list-type
is
recommended.
InterRatHoC User-defined See 7.4.5.1 Data This parameter must be

omm sheet. Preparation. customized on a list-type
mm is
recommended.
GeranNfreq User-defined See 7.4.5.1 Data This parameter must be

Group sheet. Preparation. customized on a list-type
GeranNfreqGr sheet of the template.
oup is
recommended.
GlobalProcS User-defined See 7.4.5.1 Data This parameter must be

witch sheet. Preparation. customized on a list-type
GlobalProcSwi sheet of the template.
tch is
recommended.

eRAN
----End

window.
----End

eRAN
Using MML Commands

l Ultra-Flash CSFB to UTRAN
Step 1 For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.
UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box selected under the
Handover Algo switch parameter.
----End
l (Optional) If some RNCs do not support ultra-flash CSFB to UTRAN, perform the
following operations:

UtranSepOpMobilitySwitch(UtranSepOpMobilitySwitch) check box selected under the
Multi-Operator Control Switch parameter.
Step 2 Run the MOD UTRANNETWORKCAPCFG command with the
UltraFlashCsfbCapCfg(UltraFlashCsfbCapCfg) check box cleared under the Network
Capability Configuration parameter for RNCs that do not support ultra-flash CSFB to
UTRAN.
----End
l (Optional) Perform the following operation if UE compatibility risks exist after ultra-
flash CSFB is activated.
Step 1 Run the MOD GLOBALPROCSWITCH command with the

UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw) option of the UE Compatibility
Switch parameter selected.
----End

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

The activation observation procedure for ultra-flash CSFB to UTRAN is as follows:

eRAN
2. Enable a UE to camp on an E-UTRAN cell and receive a voice call so that the UE falls
Figure 7-10 shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-
originated call.
Figure 7-11 shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-
terminated call.
The UEs in the left and right sides of the figure are the same UE. The messages on the
UTRAN side are only for reference. The UE was in idle mode before the call.
If the UE capability is not included in the Initial Context Setup Request (Initial Context Setup
Req in the figures) message, the eNodeB initiates a UE capability transfer procedure
immediately after receiving this message from the MME. If the UE capability is included in
the Initial Context Setup Request message, the eNodeB initiates a UE capability transfer
procedure after sending an Initial Context Setup Response (Initial Context Setup Rsp in the
figures) message to the MME.

eRAN
Figure 7-10 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-originated call

eRAN
Figure 7-11 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-terminated call
Counter Observation
The counter listed in Table 7-22 can be viewed to check whether the feature has taken effect.

eRAN
Table 7-22 Counter related to ultra-flash CSFB to UTRAN

1526730147 L.IRATHO.CSFB.S Triggered by ultra-flash CSFB

RVCC.E2W.ExecAt Number of SRVCC-based outgoing handover
tOut executions from E-UTRAN to WCDMA
network for ultra-flash CSFB
7.4.7 Deactivation

ENodeBAlgoSwit User-defined sheet. HoAlgoSwit Clear the

ch (eNodeB-level ENodeBAlgoSwitch ch UtranUltraFlashCsfbS-
switch) is recommended. witch(UtranUltraFlashCsfb
Switch) check box.

Using MML Commands

UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box cleared under the

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranUltraFlashCsfbSwitch-0;

UTRAN. For details, see 7.1.8 Performance Monitoring. For the performance counters
related to the ultra-flash CSFB feature, see Table 7-24.

eRAN
Table 7-24 Performance counters related to ultra-flash CSFB

1526730146 L.IRATHO.CSFB.S Number of SRVCC-based outgoing handover

RVCC.E2W.PrepAt attempts from E-UTRAN to WCDMA
tOut network for ultra-flash CSFB

RVCC.E2W.ExecAt executions from E-UTRAN to WCDMA
tOut network for ultra-flash CSFB
1526730148 L.IRATHO.CSFB.S Number of successful SRVCC-based outgoing

RVCC.E2W.ExecS handovers from E-UTRAN to WCDMA
uccOut network for ultra-flash CSFB to UTRAN
Ultra-flash CSFB to UTRAN success rate = L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut/

L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut

7.5 LOFD-001068 CS Fallback with LAI to UTRAN

This section provides engineering guidelines for LOFD-001068 CS Fallback with LAI to
UTRAN.
7.5.1 When to Use CS Fallback with LAI to UTRAN

Use LOFD-001068 CS Fallback with LAI to UTRAN when both of the following conditions
are met:LOFD-001033 CS Fallback to UTRAN has been enabled.The E-UTRAN cell has
neighboring UTRAN cells that belong to different PLMNs and supports inter-PLMN
handovers, or the E-UTRAN cell has neighboring UTRAN cells that have different location
area codes (LACs).
If both LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to GERAN
have been enabled, you are advised to enable both LOFD-001068 CS Fallback with LAI to
UTRAN and LOFD-001069 CS Fallback with LAI to GERAN.

activated.
and UTRAN cells.
networks, and ensure that they all support CSFB and the MME supports LAI delivery.
Table 7-25 describes the requirements of CSFB with LAI to UTRAN for the core
networks.

eRAN
network:
Table 7-25 Requirements of CSFB with LAI to UTRAN for core networks
NE Function
MME l Supports the SGs interface to the MSC/VLR.

l Selects the VLR and location area identity
(LAI) based on the tracking area identity (TAI)
of the serving cell.
l Forwards paging messages delivered by the
MSC.
l Performs public land mobile network (PLMN)
selection and reselection.
l Supports combined EPS/IMSI attach,
combined EPS/IMSI detach, and combined
TAU/LAU.
l Routes CS signaling.
l Supports LAI delivery.
MSC l Supports combined EPS/IMSI attach.

l Forwards paging messages transmitted through
the SGs interface.
SGSN Does not activate ISR during the combined

RAU/LAU procedure initiated by the UE.
7.5.3 Requirements

eRAN
License
Table 7-26 License information for CSFB with LAI to UTRAN
Feature Feature Name Model License NE Sales Unit

ID Control Item
LOFD-00 CS Fallback with LT1S0CS CS Fallback eNode per RRC

1068 LAI to UTRAN FLU00 with LAI to B Connected
UTRAN User
7.5.4 Precautions
None

CSFB with LAI to UTRAN is automatically activated when two conditions are met: The
license for this feature has been purchased. CSFB to UTRAN has been activated.

Data preparation for activating CSFB with LAI to UTRAN is the same as that for activating
CSFB to UTRAN. For details, see 7.1.5.1 Data Preparation.
eNodeBs
For details, see 7.1.5.2 Using the CME to Perform Batch Configuration for Newly
Deployed eNodeBs.
For details, see 7.1.5.3 Using the CME to Perform Batch Configuration for Existing
eNodeBs.

For details, see 7.1.5.4 Using the CME to Perform Single Configuration.

For details, see 7.1.5.5 Using MML Commands.

The activation observation procedure is as follows:

eRAN
1. Configure two neighboring UTRAN cells with different LAIs for an E-UTRAN cell, and
enable the MME to include only one of the two LAIs in the instructions that will be
delivered to the eNodeB.
2. Ensure that the signal strengths of the two UTRAN cells both reach the threshold for
event B1. You can query the threshold by running the LST
INTERRATHOUTRANGROUP command.
back to the UTRAN cell with the specified LAI and completes the call.
4. Enable the UE to camp on the E-UTRAN cell and receive a voice call so that the UE
falls back to the UTRAN cell with the specified LAI and completes the call.
You can observe the signaling procedure for CSFB with LAI to UTRAN, which is
similar to that for CSFB to UTRAN described in 7.1.6 Activation Observation. The
difference is that the Initial Context Setup Request or UE Context Mod Request message
carries the LAI that the MME delivers to the eNodeB, as shown in the following figure:
Figure 7-12 LAI signaling tracing
7.5.7 Deactivation
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 7.1.7 Deactivation.

UTRAN. For details, see 7.1.8 Performance Monitoring. You can observe delivered
frequencies or cells based on network logs.

7.6 LOFD-001088 CS Fallback Steering to UTRAN

This section provides engineering guidelines for LOFD-001088 CS Fallback Steering to
UTRAN.

eRAN
7.6.1 When to Use CS Fallback Steering to UTRAN

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

activated.
network:
3. Collect information about the frequencies and frequency policies of the UTRAN. The
frequency policies for UTRAN and E-UTRAN must be the same. For example, if F1 is
the preferred frequency for voice services on UTRAN, the same configuration is
recommended for E-UTRAN.
4. If LOFD-001089 CS Fallback Steering to GERAN is also to be activated, consider the
GERAN frequencies when making frequency policies.
7.6.3 Requirements
License
Table 7-27 License information for CSFB steering to UTRAN

ID Control Item
LOFD-001 CS Fallback LT1S0C CS Fallback eNode per RRC

088 Steering to FBSU00 Steering to B Connected
UTRAN UTRAN User

eRAN
7.6.4 Precautions
None

operator
Required Data
to enable CSFB steering to UTRAN.
Paramet Paramet Data Setting Notes

er Name er ID Source
Handover ENodeB Network Select the UtranCsfbSteeringS-

Algo AlgoSwit plan witch(UtranCsfbSteeringSwitch) check box
switch ch.HoAlg (negotiatio under this parameter.
oSwitch n not
required)
MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.

eRAN
Paramet Paramete Data Source Setting Notes

er Name r ID
CN CSFallBa Network plan Set this parameter based on the network plan.
Operator ckBlindH (negotiation not
ID oCfg.CnO required)
peratorId
Highest CSFallBa Network plan Set this parameter based on the network plan.
priority ckBlindH (negotiation not This parameter is set to UTRAN by default
InterRat oCfg.Inte required) and specifies the highest-priority RAT to be
rRatHigh considered in blind handovers for CSFB. For
estPri CSFB to UTRAN, retain the default value.
Second CSFallBa Network plan Set this parameter based on the network plan.
priority ckBlindH (negotiation not This parameter is set to GERAN by default
InterRat oCfg.Inte required) and specifies the second-highest-priority RAT
rRatSeco to be considered in blind handovers for
ndPri CSFB. Ensure that this parameter is set to a
different value from the InterRatHighestPri
and InterRatLowestPri parameters.
Lowest CSFallBa Network plan Set this parameter based on the network plan.
priority ckBlindH (negotiation not This parameter is set to CDMA2000 by
InterRat oCfg.Inte required) default and specifies the low-priority RAT to
rRatLowe be considered in blind handovers for CSFB.
stPri Ensure that this parameter is set to a different
UTRAN CSFallBa Network plan Set this parameter based on the network plan.
LCS ckBlindH (negotiation not This parameter specifies the LCS capability
capability oCfg.Utra required) of the UTRAN.
nLcsCap
MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.

eter ID Source
Name
CSFB CSFallBack Networ Set this parameter based on the network plan. This
Highes BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
t IdleCsfbHig (negoti the highest-priority RAT to be considered in CSFB for
priority hestPri ation UEs in idle mode. For CSFB to UTRAN, retain the
InterRa not default value.
t for require
Idle d)
UE

eRAN

eter ID Source
Name
Second BlindHoCfg. k plan parameter is set to GERAN by default and specifies
priority IdleCsfbSeco (negoti the second-highest-priority RAT to be considered in
InterRa ndPri ation CSFB for UEs in idle mode. Ensure that this
t for not parameter is set to a different value from the
Idle require InterRatHighestPri and InterRatLowestPri
UE d) parameters.
Lowest BlindHoCfg. k plan parameter is set to CDMA2000 by default and
priority IdleCsfbLow (negoti specifies the lowest-priority RAT to be considered in
InterRa estPri ation CSFB for UEs in idle mode. Ensure that this
Idle require InterRatHighestPri and InterRatSecondPri
UE d) parameters.
The following table describes the parameter that must be set in the UtranNFreq MO to set
the CS service priority of a neighboring UTRA frequency considered for RRC_IDLE UEs.

eter ID Source
Name
CS UtranNFreq Networ Set this parameter based on the network plan. If this
service .CsPriority k plan parameter is set to Priority_0(Priority 0) for the
priority (negoti UTRA frequency, the eNodeB does not select the
ation frequency for SRVCC. The values
not Priority_16(Priority 16) and Priority_1(Priority 1)
require indicate the highest and lowest SRVCC priority,
d) respectively. Set a high priority for a UTRA frequency
with good coverage.
the CS+PS combined service priority of a neighboring UTRA frequency for
RRC_CONNECTED UEs.

eRAN

eter ID Source
Name
CS and UtranNFreq Network Set this parameter based on the network plan. If
PS .CsPsMixed plan this parameter is set to Priority_0(Priority 0) for
mixed Priority (negotiation the UTRA frequency, the eNodeB does not select
priority not the frequency for SRVCC. The values
required) Priority_16(Priority 16) and
Priority_1(Priority 1) indicate the highest and
lowest SRVCC priority, respectively. Set a high
priority for a UTRA frequency with good
coverage.
MO to set the CSFB policy for RRC_CONNECTED UEs.

eter ID Source
Name
CSFB CSFallBack Networ Set this parameter based on the network plan. The
handov PolicyCfg.C k plan default values are REDIRECTION, CCO_HO, and
er sfbHoPolicy (negoti PS_HO. You are advised to set this parameter based
policy Cfg ation on the UE capabilities and network capabilities. For
Config not details about how to select a CSFB handover policy,
uration require see 3.6 Handover Execution.
d)
MO to set the CSFB policy for RRC_IDLE UEs.

eter ID Source
Name
handov PolicyCfg.Id k plan default values are REDIRECTION, CCO_HO, and
er leModeCsfb (negoti PS_HO. You are advised to set this parameter based
policy HoPolicyCfg ation on the UE capabilities and network capabilities. For
for idle d)
ue

eRAN
eNodeBs
file.
parameters.
Table 7-28 Parameters for CS fallback steering to UTRAN

Summary
Data File
ENodeBAlgoSwitch User-defined See 7.6.5.1 Data None

sheet. Preparation.
ENodeBAlgo
Switch is
recommended.
CSFallBackBlind- User-defined See 7.6.5.1 Data None

HoCfg sheet. Preparation.
CSFallBackB
lindHoCfg is
recommended.
UtranNFreq User-defined See 7.6.5.1 Data None

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

g sheet. Preparation.
CSFallBackP
olicyCfg is
recommended.

eRAN
----End

window.

eRAN
----End
Using MML Commands

The configurations in this section are examples, and configurations on the live network can
differ from the examples.
The prerequisite for the following operations is that E-UTRAN to UTRAN CS/PS Steering
has been activated.
Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous coverage.

UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) check box selected under the
Step 2 Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority
InterRat, Second priority InterRat, CSFB Highest priority InterRat for Idle UE, and
CSFB Second priority InterRat for Idle UE parameters to UTRAN, GERAN, GERAN,
and UTRAN, respectively.

eRAN
Step 3 Run the MOD UTRANNFREQ command with the CS service priority or CS and PS
mixed priority parameter set to Priority_16(Priority 16) for UTRA frequencies.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO check box
selected under the CSFB handover policy Configuration parameter and the
REDIRECTION check box selected under the CSFB handover policy Configuration for
idle ue parameter.
----End
Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN provides
contiguous coverage but the UTRAN does not. In this scenario, the eNodeB may not receive
measurement reports after delivering UTRAN measurement configurations. When the CSFB
protection timer expires, the UE is redirected to the GERAN.
Step 1 The feature activation procedure is as follows: Run the MOD GERANNCELL command
with the blind handover priority specified for the neighboring GERAN cell.
Step 2 Run the MOD ENODEBALGOSWITCH command with switches set as follows:
l Select the following options of the Handover Algo switch parameter:
UtranCsfbSwitch(UtranCsfbSwitch), GeranCsfbSwitch(GeranCsfbSwitch),
UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch), and
GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch).
l Select the UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) option of the
Frequency Layer Switch parameter.
l Deselect the BlindHoSwitch option of the Handover Mode switch parameter.
Step 3 Run the MOD CSFALLBACKBLINDHOCFG command with parameters set as follows
based on the network conditions and policies: Set the Highest priority InterRat parameter to
UTRAN. Set the Second priority InterRat parameter to GERAN. Set the CSFB Highest
priority InterRat for Idle UE parameter to UTRAN. Set the CSFB Second priority
InterRat for Idle UE parameter to GERAN.
Step 4 Run the MOD CSFALLBACKPOLICYCFG command with the REDIRECTION option
of the CSFB handover policy Configuration parameter selected.
----End

Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous coverage.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSteeringSwitch-1;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0,
InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GERAN,IdleCsfb
SecondPri=UTRAN;
MOD UTRANNFREQ: LocalCellId=0,UtranDlArfcn=10800,CsPriority=Priority_16;
MOD UTRANNFREQ: LocalCellId=1,UtranDlArfcn=9700,CsPsMixedPriority=Priority_16;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-1,
IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN provides
contiguous coverage but the UTRAN does not.
MOD GERANNCELL: LocalCellId=1, Mcc="460", Mnc="20", Lac=12,
GeranCellId=16,BlindHoPriority=32;
MOD
ENODEBALGOSWITCH:HoModeSwitch=BlindHoSwitch-0,HoAlgoSwitch=UtranCsfbSwitch-1&Geran
CsfbSwitch-1,HoAlgoSwitch=UtranCsfbSteeringSwitch-1&GeranCsfbSteeringSwitch-1,Freq

eRAN
LayerSwtich=UtranFreqLayerMeasSwitch-1;
MOD
CSFALLBACKBLINDHOCFG:CnOperatorId=0,InterRatHighestPri=UTRAN,InterRatSecondPri=GER
AN,IdleCsfbHighestPri=UTRAN,IdleCsfbSecondPri=GERAN;
MOD
CSFALLBACKPOLICYCFG:CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0,IdleModeCsfbHoP
olicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;

The signaling procedure is the same as that for CSFB to UTRAN. After CS Fallback Steering
to UTRAN is used, check whether it works as expected.
The activation observation procedure for CSFB steering to UTRAN is as follows:
1. Check that the UE supports redirection-based CSFB and handover-based CSFB.

2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection and
handover, respectively.
3. Enable the UE to initiate a voice call in idle mode and in connected mode.
4. Observe the counters L.CSFB.E2W, L.RRCRedirection.E2W.CSFB, and
L.IRATHO.E2W.CSFB.ExecAttOut. If the values of the counters increase by 2, 1, and 1,
respectively, CSFB steering to UTRAN has been activated.
If LOFD-001089 CS Fallback Steering to GERAN has also been activated, the activation
observation procedure is as follows:
1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.

2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs and
UTRAN as the highest-priority RAT for CSFB triggered for RRC_CONNECTED UEs.
4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase by 1,
both CSFB steering to UTRAN and CSFB steering to GERAN have been activated.
7.6.7 Deactivation

Table 7-29 Parameters for deactivating CSFB steering to UTRAN

ENodeBAlgoSwit User-defined sheet. HoAlgoSwit Set UtranCsfbSteeringS-

ch (eNodeB-level ENodeBAlgoSwitch ch witch under the
switch) is recommended. HoAlgoSwitch parameter to
0.

eRAN

Using MML Commands

UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) check box cleared under the

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSteeringSwitch-0;

frequencies and fallback RATs based on network logs.

7.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering

This section provides engineering guidelines for activation and activation observation of
LOFD-001078 E-UTRAN to UTRAN CS/PS Steering.
7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering

Use LOFD-001078 E-TURAN to UTRAN CS/PS Steering when all of the following
conditions are met: LOFD-001034 CS Fallback to UTRAN and LOFD-001019 PS Inter-RAT
Mobility between E-UTRAN and UTRAN have been activated. The operator owns multiple
UTRAN frequencies. The operator wants to divert CS or PS services to specific UTRAN
frequencies based on the network plan and loads.

1. Determine whether LOFD-001034 CS Fallback to UTRAN and LOFD-001019 PS Inter-
RAT Mobility between E-UTRAN and UTRAN have been activated.
network:

eRAN
3. Collect the operating frequencies and frequency policies of the E-UTRAN and UTRAN.
The frequency policies for UTRAN and E-UTRAN must be the same. For example, if F1
is the preferred frequency for voice services on UTRAN, the same configuration is
recommended for E-UTRAN.
4. Collect the configurations and versions of E-UTRAN and UTRAN equipment to check
whether CSFB is supported.
7.7.3 Requirements
License
Table 7-30 License information for E-UTRAN to UTRAN CS/PS Steering

Name Control Item
LOFD-0010 E-UTRAN to LT1SEU E-UTRAN to eNode per RRC

78 UTRAN CSPS00 UTRAN CS/PS B Connected User
CS/PS Steering
Steering
NOTE
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN or
LOFD-001033 CS Fallback to UTRAN.
7.7.4 Precautions
None

operator

eRAN
Required Data
to enable E-UTRAN to UTRAN CS/PS Steering.
Frequency Layer ENodeBAlgoSwitc Network plan When CSFB to

Switch h.FreqLayerSwtich (negotiation not UTRAN and PS
required) inter-RAT mobility
between E-UTRAN
and UTRAN have
been configured, set
this parameter as
follows:
l Select the
UtranFreqLaye
rMeasSwitch(Ut
ranFreqLayerM
easSwitch)
check box to
enable
measurement-
based handover
for E-UTRAN to
UTRAN CS/PS
Steering.
l Select the
UtranFreqLaye
rBlindSwitch(Ut
ranFreqLayerBl
indSwitch)
check box to
enable blind
handover for E-
UTRAN to
UTRAN CS/PS
Steering.
The two check
boxes can be
simultaneously
selected.

eRAN
the CS service priority for a UTRA frequency.
Paramet Parameter ID Data Source Setting Notes

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

service y (negotiation network plan. This parameter
priority not required) specifies the CS service priority
for the UTRA frequency.
eNodeBs
file.
parameters.
Table 7-31 Parameters for E-UTRAN to UTRAN CS/PS steering

Summary Data
File
ENodeBAlgoSwit User-defined sheet. See 7.7.5.1 Data None

ch ENodeBAlgoSwitc Preparation.
h is recommended.
UtranNFreq User-defined sheet. See 7.7.5.1 Data None

UtranNFreq is Preparation.
recommended.

eRAN
----End

window.

eRAN
----End
Using MML Commands

The prerequisite is that CSFB to UTRAN has been activated.
l Scenario 1: Blind E-UTRAN to UTRAN CS/PS steering

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

UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) selected under the Frequency
Layer Switch parameter.
Step 2 Run the MOD UTRANNFREQ command with the CS service priority parameter set to
Priority_16(Priority 16).
----End

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

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-1;

The signaling procedure is the same as that for CSFB to UTRAN. After E-UTRAN to
UTRAN CS/PS Steering is used, check whether it works as expected.
The activation observation procedure for E-UTRAN to UTRAN CS/PS Steering is as follows:

eRAN
1. Verify that the UE supports CSFB and multiple UTRA frequencies are available.
2. Enable measurement-based and blind handover for E-UTRAN to UTRAN CS/PS
Steering. Set a high PS service priority for UTRA frequency F1 and a high CS service
priority for UTRA frequency F2.
3. Have the UE camp on an LTE cell and initiate a voice call in the cell. The expected result
is that the UE falls back to the UTRAN cell operating on F2.
4. Have the UE camp on the LTE cell and initiate PS services. Move the UE to the LTE cell
edge. The expected result is that the UE is handed over to the UTRAN cell operating on
F1.
7.7.7 Deactivation

Table 7-32 Parameters for E-UTRAN to UTRAN CS/PS steering

Summary Data Group
File
ENodeBAlgoS User-defined FreqLayerSwtic Clear the following options:

witch sheet. h l UtranFreqLayerMeasSwitch
(eNodeB-level ENodeBAlgoSwi
switch) tch is l UtranFreqLayerBlindSwitch
recommended.

Using MML Commands

l Deactivating blind E-UTRAN to UTRAN CS/PS steering
UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) check box cleared under
the Frequency Layer Switch parameter.
l Deactivating measurement-based E-UTRAN to UTRAN CS/PS steering
UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) check box cleared under
the Frequency Layer Switch parameter.

eRAN

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

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-0;

frequencies based on network logs.

7.8 LOFD-001034 CS Fallback to GERAN

This section provides engineering guidelines for LOFD-001034 CS Fallback to GERAN.
7.8.1 When to Use CS Fallback to GERAN

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

l Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN
and GERAN cells. Information about coverage areas includes engineering parameters of
l Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core
networks, and ensure that they all support CSFB. Table 7-33 describes the requirements
of CSFB to GERAN for the core networks.

eRAN
Table 7-33 Requirements of CSFB to GERAN for core networks

NE Requirement
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the
serving cell
l 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
SGSN Does not activate ISR during the

combined RAU/LAU procedure initiated
by the UE.
l Collect the following information about the UEs that support GSM and LTE on the live
network:
Whether the UEs support redirection from E-UTRAN to GERAN
Whether the UEs support PS handover from E-UTRAN to GERAN
Whether the UEs support GERAN measurements
This information is used to configure neighboring GERAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Inter-
RAT Mobility Management in Connected Mode.
7.8.3 Requirements
License

eRAN
Table 7-34 License information for CSFB to GERAN

ID Control
Item
LOFD-001 CS Fallback to LT1S00CF CS Fallback eNodeB per RRC

034 GERAN BG00 to GERAN Connected User
NOTE
If the GERAN network uses Huawei equipment, activate the license for GBFD-511313 CSFB and turn
on the switch specified by the GCELLSOFT.SUPPORTCSFB parameter. This license is used for
scenarios with LAU after CSFB to GERAN.
7.8.4 Precautions
None

operator
Required Data
Before configuring CSFB to GERAN, collect the data related to neighbor relationships with
GERAN cells. This section provides only the information about MOs related to neighboring
GERAN cells. For more information about how to collect data for the parameters in these
MOs, see Inter-RAT Mobility Management in Connected Mode Feature Parameter
Description.
1. GeranNfreqGroup: used to configure a group of neighboring GERAN frequencies.
2. GeranNfreqGroupArfcn: used to configure a neighboring BCCH frequency in a
GERAN carrier frequency group.
3. GeranExternalCell: used to configure external GERAN cells. The
GeranExternalCell.Rac parameter must be set.
4. GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external GERAN cell. This MO is required only if the BTS that provides the external

eRAN
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.
to set the eNodeB-level handover mode and handover algorithm switches for CSFB to
GERAN.
Paramete Parameter Data Setting Notes

r Name ID Source
Handover ENodeBAl Network Set this parameter based on the network plan.
Mode goSwitch. plan To activate PS handovers, select the
switch HoModeS (negotiation GeranPsHoSwitch(GeranPsHoSwitch) check
witch not box. To activate CCO, select the
required) GeranCcoSwitch(GeranCcoSwitch) check
box. To activate NACC, select the
GeranNaccSwitch(GeranNaccSwitch) check
box. If none of the preceding check boxes is
selected, redirection will be used for CSFB to
GERAN.
Handover ENodeBAl Network To activate CSFB to GERAN, select the

Algo goSwitch. plan GeranCsfbSwitch(GeranCsfbSwitch) option.
switch HoAlgoSw (negotiation
itch not
required)


eNodeB are invalid.

eRAN
Paramete Parameter Data Setting Notes

r Name ID Source
CN CSFallBackB Network Set this parameter based on the network plan.

Operator lindHoCfg.Cn plan This parameter specifies the ID of the operator
ID OperatorId (negotiati whose RAT blind-handover priorities are to be
on not set.
required)
Highest CSFallBackB Network Set this parameter based on the network plan.
priority lindHoCfg.Int plan This parameter is set to UTRAN by default and
InterRat erRatHighest (negotiati specifies the highest-priority RAT to be
Pri on not considered in blind handovers for CSFB. For
required) CSFB to GERAN, set this parameter to
GERAN.
Second CSFallBackB Network Set this parameter based on the network plan.
priority lindHoCfg.Int plan This parameter is set to GERAN by default and
InterRat erRatSecondP (negotiati specifies the second-highest-priority RAT to be
ri on not considered in blind handovers for CSFB. If the
required) highest-priority RAT has been set to GERAN,
the second-highest-priority RAT cannot be set
to GERAN. Ensure that this parameter is set to
a different value from the InterRatHighestPri
and InterRatLowestPri parameters.
Lowest CSFallBackB Network Set this parameter based on the network plan.
priority lindHoCfg.Int plan This parameter is set to CDMA2000 by default
InterRat erRatLowestP (negotiati and specifies the low-priority RAT to be
ri on not considered in blind handovers for CSFB.
required) Ensure that this parameter is set to a different
GERAN CSFallBackB Network Set this parameter based on the network plan.
LCS lindHoCfg.Ge plan This parameter specifies the LCS capability of
capability ranLcsCap (negotiati the GERAN.
on not
required)
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.

eRAN

r Name ID
CSFB CSFallBack Network plan Set this parameter based on the network
Protection Ho.CsfbPro (negotiation not plan. The default value 4 applies to a
Timer tectionTime required) GSM+UMTS+LTE network. The default
r value is also recommended for a GSM
+LTE network. If this parameter is set
too large, the CSFB delay increases in
abnormal CSFB scenarios. If this
parameter is set too small, normal
measurement or handover procedures
may be interrupted.
set the maximum number of neighboring GERAN cells whose system information is sent to
UEs for emergency redirections.
Max Geran cell num InterRatHoComm. Network plan The default value is
in CSFB EMC GeranCellNumFor- (negotiation not 0, indicating that no
redirection EmcRedirect required) system information
of any neighboring
UTRAN cells is sent
to UEs for
emergency
redirections.
Operators can set
this parameter to 0
through 32 based on
the network plan.
After the CSFB
protection timer
expires, the eNodeB
performs an
emergency
redirection. If the
signal quality of the
serving cell is poor
and this parameter is
set to a large value,
the eNodeB may fail
to send the system
information of
neighboring
UTRAN cells to
UEs.

eRAN
eNodeBs
file.
parameters.
Table 7-35 Parameters for CSFB to GERAN

MO Sheet in Parameter Group Remarks
the
Summary
Data File
GeranNfreqGr GeranNfreq See 7.8.5.1 Data The RNP template sheet

oup Group Preparation. is recommended.
GeranNfreqGr GeranNfreq See 7.8.5.1 Data The RNP template sheet

oupArfcn GroupArfcn Preparation. is recommended.
GeranExternal GeranExtern See 7.8.5.1 Data The RNP template sheet

Cell alCell Preparation. is recommended.
GeranExternal GeranExtern See 7.8.5.1 Data The RNP template sheet

CellPlmn alCellPlmn Preparation. is recommended.
GeranNcell GeranNcell See 7.8.5.1 Data The RNP template sheet

Preparation. is recommended.
ENodeBAlgoS User- See 7.8.5.1 Data This parameter must be

witch defined Preparation. customized on a list-type
sheet. sheet of the template.
ENodeBAlg
oSwitch is
recommend
ed.

eRAN
MO Sheet in Parameter Group Remarks

the
Summary
Data File
CSFallBackBli User- See 7.8.5.1 Data This parameter must be

ndHoCfg defined Preparation. customized on a list-type
CSFallBack
BlindHoCf
g is
recommend
ed.
CSFallBackHo User- See 7.8.5.1 Data This parameter must be

defined Preparation. customized on a list-type
CSFallBack
Ho is
recommend
ed.
InterRatHoCo User- See 7.8.5.1 Data None

mm defined Preparation.
sheet.
InterRatHo
Comm is
recommend
ed.
CellHoParaCfg User- See 7.8.5.1 Data This parameter must be

defined Preparation. customized on a list-type
CellHoPara
Cfg is
recommend
ed.
Batch Activated

eRAN
----End

window.

eRAN
----End
7.8.5.5 Using Feature Operation and Maintenance on the CME

Step 1 On the U2000 client, choose CME > Planned Area > Create Planned Area.
Step 2 In the displayed Create Planned Area dialog box, specify Planned area name, select the
eNodeB (for which CSFB to GERAN is to be activated) on the Base Station tab page under
Available NEs, and click so that it is added to Selected NEs. Then, click OK.
Step 3 Choose CME > Advanced > Feature Operation and Maintenance > Export
Feature Commission Data from the main menu.
Step 4 In the displayed dialog box, click LTE in the Category drop-down list, and select the CSFB
to GERAN feature to be activated, for example, TDLOFD-001033 CSFB to GERAN. Then,
click Next.
Step 5 Under Available Base Stations in the dialog box, select the eNodeB whose data is to be
exported. Click so that the eNodeB is added to Selected Base Stations. Then, click
Next.
Step 6 In the dialog box, set Export as to the format (.xls or .xlsm) in which the exported data is to
be saved. Click to the right of Export path to specify the save path. Then, click Next.
Step 7 Wait until the data is exported.
Step 8 Click the hyperlink to the save path. Alternatively, click Finish, and locate the exported file in
the save path.
Step 9 Set related parameters in the CSFB to UTRAN data file (for example, TDLOFD-001033.xls).
Step 10 After setting the parameters, choose CME > Advanced > Feature Operation and
Maintenance > Import Feature Commission Data on the U2000 client. In the displayed
dialog box, select the CSFB to GERAN data file, and click Next.
Step 11 Wait until the file is imported. Leave the Export incremental script check box selected
(default setting). Click Finish.
Step 12 In the displayed dialog box, check that the eNodeB is displayed in the Selected NEs area. Set
Encrypt script and Script Executor Operation. You are advised to set Script Executor
Operation to Launch script executor and activate exported project so that the script will
be executed upon it is loaded. Then, click OK.

eRAN
Step 13 In the displayed confirmation dialog box, click Yes. Data synchronization starts for the
eNodeB. When Success is displayed in the Result column, the CSFB to GERAN feature has
been activated.
----End
The following table describes parameters for CSFB to GERAN:
Table 7-36 Parameters for CSFB to GERAN

MO Paramet Parameter ID Setting Notes
er Name
GERANNFR Local cell LocalCellId Manually configured

EQGROUP ID
BCCH BcchGroupId Manually configured

group ID
GERAN GeranVersion Manually configured

version
Starting StartingArfcn Manually configured

ARFCN
Band BandIndicator Manually configured

indicator
Cell CellReselPriori- Automatically configured as NOT_CFG

reselectio tyCfgInd
n priority
configure
indicator
Cell CellReselPriori- Automatically configured as 1

reselectio ty
n priority
PMAX PmaxGeranCfg Automatically configured as NOT_CFG

configure Ind
indicator
PMAX PmaxGeran Manually configured
Minimum QRxLevMin Automatically configured as 0

required
RX level
High ThreshXHigh Automatically configured as 7

priority
threshold
Lower ThreshXLow Automatically configured as 7

priority
threshold

eRAN

er Name
Frequenc OffsetFreq Automatically configured as 0

y offset
NCC NccPermitted Automatically configured as 255

monitorin
g
permitted
GERANNFR Local cell LocalCellId Manually configured

EQGROUPA ID
RFCN
BCCH BcchGroupId Manually configured
group ID
GERAN GeranArfcn Manually configured

ARFCN
GERANEXT Mobile Mcc Manually configured

ERNALCEL country
L code
Mobile Mnc Manually configured

network
code
GERAN GeranCellId Manually configured

cell ID
Location Lac Manually configured

area code
Routing RacCfgInd Automatically configured as NOT_CFG

area code
configure
indicator
Routing Rac Manually configured

area code
Band BandIndicator Manually configured

indicator
GERAN GeranArfcn Manually configured

ARFCN
Network NetworkColour Manually configured

color Code
code
Base BaseStationCol Manually configured

station ourCode
color
code

eRAN

er Name
DTM DtmInd Automatically configured as

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

PS BOOLEAN_FALSE
handover
indicator
GERANEXT GERAN GeranCellId Manually configured

ERNALCEL cell ID
LPLMN
area code
Mobile Mcc Manually configured

country
code

network
code
Share ShareMcc Manually configured

mobile
country
code
Share ShareMnc Manually configured

mobile
network
code
GERANNCE Local cell LocalCellId Manually configured

LL ID
Mobile Mcc Manually configured

country
code

network
code

area code
GERAN GeranCellId Manually configured

cell ID
No NoHoFlag Automatically configured as

handover PERMIT_HO_ENUM
indicator

eRAN

er Name
No NoRmvFlag Automatically configured as

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

name
Neighbori NeighbourCell Manually configured

ng cell Name
name
ENODEBAL Handover HoAlgoSwitch Automatically configured as

GOSWITCH Algo GeranCsfbSwitch-1
switch
Handover HoModeSwitch Automatically configured as

Mode GeranRedirectSwitch-1&BlindHoSwitch-
switch 0&GeranPsHoSwitch-0
CSFALLBAC CSFB CsfbHoPolicyC Automatically configured as

KPOLICYCF handover fg REDIRECTION-1&CCO_HO-0&PS_H
G policy O-0
Configura
tion
CSFB IdleModeCsfbH Automatically configured as

handover oPolicyCfg REDIRECTION-1&CCO_HO-0&PS_H
policy O-0
Configura
tion for
idle ue
Csfb User CsfbUserArpCf Automatically configured as OFF

Arp gSwitch
Configura
tion
Switch
Normal NormalCsfbUse Automatically configured as 2

Csfb User rArp
Arp
CSFALLBAC CN CnOperatorId Manually configured

KBLINDHO Operator
CFG ID
Highest InterRatHighest Automatically configured as UTRAN

priority Pri
InterRat

eRAN

er Name
Second InterRatSecond Automatically configured as GERAN

priority Pri
InterRat
Lowest InterRatLowest Automatically configured as CDMA2000

priority Pri
InterRat
GERAN GeranLcsCap Automatically configured as OFF

LCS
capability
CSFALLBAC Local cell LocalCellId Manually configured

KHO ID
CSFB CsfbHoGeranTi Automatically configured as 40 ms

Geran meToTrig
EventB1
Time To
Trig
CSFB CsfbHoGeranB Automatically configured as -103

GERAN 1Thd
EventB1
Trigger
Threshold
CSFB CsfbProtection Automatically configured as 4

Protection Timer
Timer
CELLHOPA Handover HoModeSwitch Automatically configured as

RACFG Mode BlindHoSwitch-0
switch
INTERRATH Max GeranCellNum Automatically configured as 0

OCOMM Geran cell ForEmcRedirec
num in t
CSFB
EMC
redirectio
n
Using MML Commands

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.

eRAN
l If you want to configure a neighboring GERAN cell, you must configure the
GeranNFreq and GeranNCell MOs. For details about parameter settings, see Inter-RAT
l If you do not want to configure a neighboring GERAN cell, you must configure the
GeranRanShare or GeranExternalCell MO. For details about parameter settings, see
Inter-RAT Mobility Management in Connected Mode.
Step 1 Run the following eNodeB- and cell-level commands to enable the blind handover function
for CSFB to GERAN:
selected.
2. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of the

GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter
selected.
option of the CSFB handover policy Configuration parameter deselected and the
Step 4 (Optional) If you require setting GERAN as having the highest priority for CSFB, run the
parameter set to GERAN and the Second priority InterRat parameter set to UTRAN.
Step 5 (Optional) If a neighboring GERAN cell is configured, run the MOD GERANNCELL
command with the Blind handover priority parameter set to the highest priority (32).
Step 6 (Optional) If no neighboring GERAN cell is configured, run the ADD GeranNfreqGroup
command with the Frequency Priority for Connected Mode parameter set to the highest
priority (8).
----End
l Basic scenario 2: CSFB to GERAN using blind CCO with NACC
Step 1 Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For

GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter, the
BlindHoSwitch(BlindHoSwitch), GeranNaccSwitch(GeranNaccSwitch), and
GeranCcoSwitch(GeranCcoSwitch) options of the Handover Mode switch parameter, and
the GERAN_RIM_SWITCH(GERAN RIM Switch) option of the RIM switch parameter
selected.
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.

eRAN
Step 5 (Optional) If you require setting UTRAN as having the highest priority for CSFB, run the
Step 6 Run the MOD GERANNCELL command with the Blind handover priority parameter set
to 32.
----End
l Basic scenario 3: CSFB to GERAN using blind handovers

GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter and
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
Step 5 (Optional) If you require setting GERAN as having the highest priority for CSFB, run the
to 32.
----End
l Basic scenario 4: CSFB to GERAN using measurement-based redirections

GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter
selected.
option of the CSFB handover policy Configuration parameter deselected and the
to 32.
----End
l Basic scenario 5: CSFB to GERAN using measurement-based handovers

(recommended)

eRAN
GeranCsfbSwitch(GeranCsfbSwitch) check box selected under the Handover Algo switch
and the GeranPsHoSwitch(GeranPsHoSwitch) check box selected under the Handover
Mode switch parameter.
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
to 32.
----End
l Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC
(recommended)
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter, the
GeranNaccSwitch(GeranNaccSwitch) and GeranCcoSwitch(GeranCcoSwitch) options of
the Handover Mode switch parameter, and the GERAN_RIM_SWITCH(GERAN RIM
Switch) option of the RIM switch parameter selected.
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.
to 32.
----End

l Basic scenario 1: CSFB to GERAN using blind redirection (configured with neighboring
GERAN cells)
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1,
InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;
l Basic scenario 1: CSFB to GERAN using blind redirection (configured with no

neighboring GERAN cell)

eRAN

ADD GeranNfreqGroup: LocalCellId=0, BcchGroupId=0, StratingArfcn=0,
ConnFreqPriority=8;
ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0,GeranArfcn=0;
ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="20";
l Basic scenario 2: CSFB to GERAN using blind CCO with NACC

HoModeSwitch=BlindHoSwitch-1&GeranNaccSwitch-1&GeranCcoSwitch-1,RimSwitch=GERAN_RI
M_SWITCH-1;
l Basic scenario 3: CSFB to GERAN using blind handovers

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

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

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

HoModeSwitch=GeranNaccSwitch-1&GeranCcoSwitch-1,RimSwitch=GERAN_RIM_SWITCH-1;
1. Enable a UE to camp on an E-UTRAN cell and make a voice call.

2. Enable the UE to camp on an E-UTRAN cell and receive a voice call.
You can observe the signaling procedures for CSFB to GERAN, which is similar to that for
CSFB to UTRAN described in section Figure 7-16.

eRAN
NOTE
In the following figures, the UE on the left side and the UE on the right side are the same UE. The
signaling on the GERAN side is for reference only. The procedure for mobile-terminated calls is similar
to the procedure for mobile-originated calls except that the procedure for mobile-terminated calls
includes paging.
Figure 7-16 Redirection-based CSFB to GERAN for a mobile-originated call
The signaling procedure for PS handover-based CSFB to GERAN is different from the
signaling procedure for redirection-based CSFB to GERAN. The difference is as follows: In
PS handover-based CSFB to GERAN, the eNodeB performs a PS handover procedure rather
than an RRC connection release procedure after the UE reports measurement results to the
eNodeB. For details about the signaling procedure of PS handover-based CSFB to GERAN,
see 7.1.6 Activation Observation. In the signaling procedure of PS handover-based CSFB to
GERAN, the CSFB indication flag is true and the CSFB target is GERAN in the
MobilityFromEUTRACommand message.
In the signaling procedure for PS handover-based CSFB to GERAN, the cs-FallbackIndicator
IE is TRUE and the CSFB target is GERAN in the MobilityFromEUTRACommand message.

eRAN
Figure 7-17 shows the signaling procedure for CCO/NACC-based CFSB to GERAN for a
mobile-originated call. In the CSFB, handover preparation is absent. The
MobilityFromEUTRACommand message carries the CCO/NACC information and the CSFB
target is GERAN.
Figure 7-17 CCO/NACC-based CSFB to GERAN for a mobile-originated call
Counter Observation
Table 7-37 lists the performance counters for observing functions related to CSFB to
GERAN.

eRAN
Table 7-37 Performance counters for observing CSFB to GERAN

Function Counter Counter Name Description
ID
CSFB to 152672832 L.CSFB.E2G Number of times CSFB to

GERAN 4 GERAN is performed
CSFB to 152672871 L.CSFB.E2G.Emergenc Number of times CSFB to

GERAN 0 y GERAN is triggered for
triggered for emergency calls
emergency calls
7.8.7 Deactivation
Table 7-38 Parameters for deactivating CSFB to GERAN

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

to GERAN, set
GeranCsfbSwitch
under the
HoAlgoSwitch
parameter to 0.

Using MML Commands

GeranCsfbSwitch(GeranCsfbSwitch) check box cleared under the Handover Algo switch
parameter.

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-0;

eRAN

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

1526728321 L.CSFB.PrepAtt Number of CSFB indicators received by

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

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

1526728324 L.CSFB.E2G Number of procedures for CSFB to GERAN
Table 7-41 lists the counters that indicate whether CSFB is performed through redirection or
through handover.
Table 7-41 Counters related to CSFB through redirection or handover

1526728498 L.RRCRedirectio Number of CSFB-based redirections from E-

n.E2G.CSFB UTRAN to GERAN
1526728507 L.IRATHO.E2G. Number of CSFB-based inter-RAT handover

CSFB.PrepAttOu preparation attempts from E-UTRAN to
t GERAN
You can check whether CCO with NACC or CCO without NACC is used as the CSFB
mechanism by viewing the counters listed in Table 7-42.

eRAN
Table 7-42 Counters related to using CCO with NACC or CCO without NACC
1526729505 L.CCOwithNAC Number of CSFB-based CCO with NACC

C.E2G.CSFB.Exe executions from E-UTRAN to GERAN
cAttOut
1526729506 L.CCOwithNAC Number of successful CSFB-based CCOs

C.E2G.CSFB.Exe with NACC from E-UTRAN to GERAN
cSuccOut
1526729507 L.CCOwithoutN Number of CSFB-based CCO without

ACC.E2G.CSFB. NACC executions from E-UTRAN to
ExecAttOut GERAN
The CCO success rate can be calculated in the following ways:
l L.CCOwithNACC.E2G.CSFB.ExecSuccOut/
L.CCOwithNACC.E2G.CSFB.ExecAttOut
l L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut/
L.CCOwithoutNACC.E2G.CSFB.ExecAttOut
After the CSFB protection timer expires, the eNodeB may perform a blind redirection to enter
the protection procedure. Table 7-43 lists the related counter. A larger value of this counter
indicates a longer average UE access delay during CSFB.
Table 7-43 Counter related to the number of times that the eNodeB enters the protection
procedure for CSFB
1526729516 L.RRCRedirectio Number of CSFB-based blind redirections

n.E2G.CSFB.Tim from E-UTRAN to GERAN caused by
eOut CSFB protection timer expiration
Table 7-44 lists the counters related to CSFB for emergency calls.
Table 7-44 Counters related to CSFB for emergency calls
1526729513 L.IRATHO.E2G. Number of CSFB-based handover execution

CSFB.ExecAttOu attempts to GERAN triggered for emergency
t.Emergency calls
1526729514 L.IRATHO.E2G. Number of successful CSFB-based handover

CSFB.ExecSuccO executions to GERAN triggered for
ut.Emergency emergency calls

eRAN
CSFB handover success rate for emergency calls =

L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency/
L.IRATHO.E2G.CSFB.ExecAttOut.Emergency

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

er Name ID Source
Local cell CSFallBac Network Set this parameter based on the network plan.
ID kHo.Local plan
CellId (negotiatio
n not
required)
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.
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.
7.9 RIM Procedure from E-UTRAN to GERAN

eRAN
7.9.1 When to Use RIM Procedure Between E-UTRAN and

GERAN
It is recommended that the RIM procedure be performed through the Huawei-proprietary
eCoordinator if the following two conditions are met: 1. Both the eNodeB and the RNC/BSC
are provided by Huawei and are connected to the same eCoordinator. 2. The core network that
the eNodeB and the RNC/BSC are connected to does not support the RIM procedure or is not
enabled with the RIM procedure. To perform the RIM procedure through the eCoordinator, set
ENodeBAlgoSwitch.RimOnEcoSwitch to ON(On).
In other conditions, it is recommended that the RIM procedure be performed through the core
network. In this case, set ENodeBAlgoSwitch.RimOnEcoSwitch to OFF(Off).

Check whether the BSC, MME, and SGSN support the RIM procedure, and whether an
eCoordinator has been deployed.
7.9.3 Requirements
If the RIM procedure is performed through the core network, the core-network equipment
must support this feature:
l The BSC, MME, and SGSN must support the RIM procedures. If one of the NEs does
not support, the RIM procedures fail.
NOTE
In a multioperator core network (MOCN) scenario, the eNodeB preferentially selects the link for
the primary operator when sending an RIM request. If the RIM procedure fails, the eNodeB no
longer attempts to send the RIM request on other links.
If the RIM procedure is performed through the eCoordinator, the RNC/BSC, eNodeB, and
eCoordinator must all be provided by Huawei and with the switch for supporting the RIM
procedure through eCoordinator turned on.
License
Table 7-45 License information for CSFB to GERAN

Feature Feature Model License NE Sales Unit
ID Name Control Item
LOFD-001 CSFB to LT1S00C CS Fallback to eNodeB per RRC

034 GERAN FBG00 GERAN Connected User

eRAN
7.9.4 Precautions
None

operator
Required Data
GeranExternalCell: used to configure external GERAN cells. The GeranExternalCell.Rac

parameter must be set.
to configure the RIM procedure.

Name ID Source
Support RIM ENodeBAlg Network If ENodeBAlgoSwitch.RimOnEcoSwitch

by oSwitch.Rim plan is set to OFF(Off), the RIM procedure is
eCoordinator OnEcoSwitc (negotiatio performed through the core network.
Switch h n not If ENodeBAlgoSwitch.RimOnEcoSwitch
required) is set to ON(On), the RIM procedure is
performed through the eCoordinator.
eNodeBs

eRAN
file.
parameters.

Summary Data
File
ENodeBAlgoSwit User-defined sheet. Support RIM by None

ch ENodeBAlgoSwitc eCoordinator Switch
h is recommended.

eRAN
----End

window.
----End
Using MML Commands


eRAN



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

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

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

eNodeB receives a system
information update from a
GERAN
Signaling Tracing Result Observation

If the RIM procedure is performed through the core network, trace signaling messages as
follows:
Step 1 Start an S1 interface tracing task on the eNodeB LMT.
Check whether the eNB DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-REQUEST IE is sent over the S1 interface. If the message is sent, you
Step 2 Start a Gb interface tracing task on the BSC LMT.

eRAN
If after receiving the DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMATION-REQUEST IE, the BSC sends the DIRECT INFORMATION TRANSFER
message containing the RAN-INFORMATION IE to the SGSN, you can infer that the BSC
can response to the RIM request normally.
Step 3 Change the state of the GSM cell.
If the BSC sends the DIRECT INFORMATION TRANSFER message containing the RAN-
INFORMAION IE over the Gb interface, you can infer that the BSC can notify the eNodeB
with the cell state change through the RIM procedure.
----End
If the RIM procedure is performed through the eCoordinator, trace signaling messages as
follows:
Step 1 Start an Se interface tracing task on the eNodeB LMT.

Check whether the ENB DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-REQUEST IE is sent over the Se interface. If the message is sent, you
Step 2 Start an Sg interface tracing task on the BSC LMT.
If after receiving the ECO DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION-REQUEST IE, the BSC sends the BSC DIRECT INFORMATION
TRANSFER message containing the RAN-INFORMAION IE to the eCoordinator, you can
infer that the BSC can response to the RIM request normally.
Step 3 Change the state of the GSM cell.
If the BSC sends the BSC DIRECT INFORMATION TRANSFER message containing the
RAN-INFORMATION IE over the Sg interface, you can infer that the BSC can notify the
eNodeB with the cell state change through the RIM procedure.
----End
7.9.7 Deactivation

eRAN

Summary Data Group
File
ENodeBAlgoS User-defined RimOnEcoSwitc Set this parameter to OFF(Off).

witch sheet. h
ENodeBAlgoSwi
tch is
recommended.

Using MML Commands




GERAN. For details, see 7.8.8 Performance Monitoring.

GERAN. For details, see 7.8.9 Parameter Optimization.
7.10 LOFD-001053 Flash CS Fallback to GERAN

This section provides engineering guidelines for LOFD-001053 Flash CS Fallback to
GERAN.
7.10.1 When to Use Flash CS Fallback to GERAN

When LOFD-001034 CS Fallback to GERAN has been enabled, use LOFD-001053 Flash CS
Fallback to GERAN if all the following conditions are met:The E-UTRAN and GERAN

eRAN
support the RIM with SIB procedure.3GPP Release 9 UEs are used on the live network.The
core networks support the RIM procedure. For policies on whether to use PS handover or PS
redirection for CSFB, see Inter-RAT Mobility Management in Connected Mode. If GERAN
and E-UTRAN cells cover the same area, or the GERAN cell provides better coverage than
the E-UTRAN cell, use CSFB based on blind handover to decrease the CSFB delay.

l Collect information about whether LOFD-001034 CS Fallback to GERAN has been
activated.
networks, and ensure that they all support CSFB and the RIM procedure. Table 7-49
describes the requirements of flash CSFB to GERAN for the core networks. For details
about processing in Huawei GSM equipment, see Interoperability Between GSM and
LTE in GBSS Feature Documentation.
network:
Whether the UEs comply with 3GPP Release 9 specifications
l This information is used to configure neighboring GERAN cells and to determine
Table 7-49 Requirements of flash CSFB to GERAN for core networks
NE Requirement
MME Supports CSFB and RIM procedures
SGSN Supports CSFB and RIM procedures
7.10.3 Requirements

eRAN
License
Table 7-50 License information for flash CSFB to GERAN

Name Control Item
LOFD-0010 Flash LT1S0FC Flash CS eNodeB per RRC

53 CSFB to FBG00 Fallback to Connected User
GERAN GERAN
NOTE
If the GERAN uses Huawei devices, evolved network assisted cell change (eNACC) between E-
UTRAN and GERAN for CSFB needs to be enabled on the GERAN. For detailed operations, see
section "eNACC from EUTRAN to GERAN" in Interoperability Between GSM and LTE Feature
7.10.4 Precautions
None

operator
Required Data
Before configuring CSFB to GERAN, collect the data related to neighbor relationships with
GERAN cells. This section provides only the information about MOs related to neighboring
GERAN cells and key parameters in these MOs. For more information about how to collect
data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description.
1. GeranNfreqGroup: used to configure a group of neighboring GERAN frequencies.

2. GeranNfreqGroupArfcn: used to configure a neighboring BCCH frequency in a
GERAN carrier frequency group.

eRAN
3. GeranExternalCell: used to configure external GERAN cells. The

GeranExternalCell.Rac parameter must be set.
4. GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external GERAN cell. This MO is required only if the BTS that provides the external
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.
to set the handover mode and handover algorithm switches for flash CSFB to GERAN.

Name ID Source
Handover ENodeBAlg Network Set this parameter based on the network plan.
Mode switch oSwitch.Ho plan
ModeSwitch (negotiati
on not
required)
Handover ENodeBAlg Network To activate flash CSFB to GERAN, select the

Algo switch oSwitch.Ho plan GeranCsfbSwitch(GeranCsfbSwitch) and
AlgoSwitch (negotiati GeranFlashCsfbSwitch(GeranFlashCsfbS-
on not witch) check boxes.
required)

eRAN

Name ID Source
RIM switch ENodeBAlg Network GERAN_RIM_SWITCH(GERAN RIM

oSwitch.Ri plan Switch) under this parameter specifies whether
mSwitch (negotiati to enable or disable the RIM procedure that
on not requests event-driven multiple reports from
required) GERAN cells.
If this switch is turned on, the eNodeB can
send RAN-INFORMATION-REQUEST/
Multiple Report PDUs to GERAN cells to
request event-driven multiple reports.
If this switch is turned off, the eNodeB cannot
send RAN-INFORMATION-REQUEST/
Multiple Report PDUs to GERAN cells.
If this switch is turned off and
GeranFlashCsfbSwitch(GeranFlashCsfbS-
witch) under
ENodeBAlgoSwitch.HoAlgoSwitch is turned
on, the eNodeB sends RAN-INFORMATION-
REQUEST/Single Report PDUs to GERAN
cells to request single reports.
If the GERAN cells support RAN-
INFORMATION-REQUEST/Multiple Report
PDUs, you are advised to select the
GERAN_RIM_SWITCH(GERAN RIM
Switch) option.


eNodeB are invalid.

eRAN
The following table describes the parameter that must be set in the S1Interface MO to set the
compliance protocol release of the MME.

r Name ID
MME S1INTERF Network plan To activate RIM procedures in Multiple

Release ACE.Mme (negotiation Report mode, set the parameter to
Release not required) Release_R9(Release 9).
Parameter Parameter ID Data Setting Notes

Name Source
CN CSFallBackBlind- Network Set this parameter based on the

Operator ID HoCfg.CnOperato plan network plan. This parameter
rId (negotiation specifies the ID of the operator
not required) whose RAT blind-handover priorities
are to be set.
Highest CSFallBackBlind- Network Set this parameter based on the

priority HoCfg.InterRatHi plan network plan. This parameter is set to
InterRat ghestPri (negotiation UTRAN by default and specifies the
not required) highest-priority RAT to be considered
in blind handovers for CSFB. For
flash CSFB to GERAN, set this
parameter to GERAN.
Second CSFallBackBlind- Network Set this parameter based on the

priority HoCfg.InterRatSe plan network plan. This parameter is set to
InterRat condPri (negotiation GERAN by default and specifies the
not required) second-highest-priority RAT to be
considered in blind handovers for
CSFB. If the highest-priority RAT
has been set to GERAN, the second-
highest-priority RAT cannot be set to
GERAN. Ensure that this parameter
is set to a different value from the
InterRatHighestPri and
InterRatLowestPri parameters.
Lowest CSFallBackBlind- Network Set this parameter based on the

priority HoCfg.InterRatLo plan network plan. This parameter is set to
InterRat westPri (negotiation CDMA2000 by default and specifies
not required) the low-priority RAT to be
considered in blind handovers for
CSFB. Ensure that this parameter is
set to a different value from the
InterRatHighestPri and

eRAN
Parameter Parameter ID Data Setting Notes

Name Source
GERAN CSFallBackBlind- Network Set this parameter based on the

LCS HoCfg.GeranLcsC plan network plan. This parameter
capability ap (negotiation specifies the LCS capability of the
not required) GERAN.
set the maximum number of neighboring GERAN cells whose system information is sent to
UEs for redirections.

Name ID Source
Max Geran cell InterRatHo Network Set this parameter based on the network
num in Comm.CellI plan plan. The default value is 8. If this
redirection nfoMaxGera (negotiati parameter is set too small, the flash CSFB
nCellNum on not success rate decreases because UEs may
required) not receive valid neighboring cell system
information. If this parameter is set too
large, the size of an RRC connection
release message increases and CSFB may
fail.
eNodeBs
file.
parameters.

eRAN
Table 7-51 Parameters for flash CSFB to GERAN

Summary
Data File
GeranNfreqGroup GeranNfreqGr See 7.10.5.1 Data The RNP

oup Preparation. template sheet is
recommended.
GeranNfreqGroupAr GeranNfreqGr See 7.10.5.1 Data The RNP

fcn oupArfcn Preparation. template sheet is
recommended.
GeranExternalCell GeranExternal See 7.10.5.1 Data The RNP

Cell Preparation. template sheet is
recommended.
GeranExternalCellPl GeranExternal See 7.10.5.1 Data The RNP

mn CellPlmn Preparation. template sheet is
recommended.
GeranNcell GeranNcell See 7.10.5.1 Data The RNP

Preparation. template sheet is
recommended.
S1Interface S1Interface See 7.10.5.1 Data This parameter

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

sheet. Preparation. must be
ENodeBAlgo customized on a
Switch is list-type sheet of
recommended. the template.
CSFallBackBlind- User-defined See 7.10.5.1 Data This parameter

HoCfg sheet. Preparation. must be
CSFallBackB customized on a
lindHoCfg is list-type sheet of
InterRatHoComm User-defined See 7.10.5.1 Data None

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

sheet. Preparation.
CSFallBackH
o is
recommended.

eRAN

Summary
Data File
CellHoParaCfg User-defined See 7.10.5.1 Data This parameter

sheet. Preparation. must be
CellHoParaC customized on a
fg is list-type sheet of
Batch Activated
----End

eRAN

window.
----End
Using MML Commands

The prerequisite is that CSFB to GERAN has been activated. In addition to the steps in the
CSFB to GERAN using blind redirections or CSFB to GERAN using measurement-based
redirections scenario, perform the following steps:

GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box selected under the Handover
Algo switch parameter and with the GERAN_RIM_SWITCH(GERAN RIM Switch) check
box selected under the RIM switch parameter.

eRAN
Step 2 Run the MOD S1INTERFACE command with the MME Release parameter set to
Release_R9(Release 9).
----End

MOD ENODEBALGOSWITCH:
HoAlgoSwitch=GeranFlashCsfbSwitch-1,RimSwitch=GERAN_RIM_SWITCH-1;
MOD S1INTERFACE:
S1InterfaceId=2,S1CpBearerId=1,CnOperatorId=0,MmeRelease=Release_R9;

Enable a UE to camp on an E-UTRAN cell and originate a voice call. If so that the UE falls
back to a GERAN cell and completes the call continues, and the RRC Connection Release
message traced in on the Uu interface tracing carries the information of the neighboring
GERAN cell. In this case, flash CSFB to GERAN has been activated successfully.
In this case, flash CSFB to GERAN has been activated successfully. The procedure of flash
CS fallback to GERAN on the E-UTRAN side is the same as the procedure of redirection-
based CS fallback to GERAN. For details, see 7.1.6 Activation Observation. The difference
is that the RRC Connection Release message carries the system information of the
neighboring GERAN cell. For details, see Figure 7-20.
Figure 7-20 The RRC Connection Release message during flash CSFB to GERAN

Check the status of the RIM procedure towards neighboring GERAN cells by running the
DSP GERANRIMINFO command. If the ID of a neighboring GERAN cell is displayed in

eRAN
the command output, the eNodeB has obtained the system information of this neighboring
GERAN cell.
Counter Observation
The counter listed in Table 7-52 can be viewed to check whether the feature has taken effect.
Table 7-52 Performance counters for observing flash CSFB to GERAN

Functions Counter ID Counter Name Description
Flash CS Fallback to 1526728706 L.FlashCSFB.E2G Number of

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

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

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

date eNodeB receives a
system information
update from a
GERAN
7.10.7 Deactivation
feature activation described in 7.10.5.3 Using the CME to Perform Batch Configuration
for Existing eNodeBs. In the procedure, modify parameters according to Table 7-53.

eRAN
Table 7-53 Parameters for deactivating flash CSFB to GERAN

Summary Data
File
ENodeBAlgoSwitch User-defined sheet HoAlgoSwitch Set

GeranFlashCsfbS-
witch under the
HoAlgoSwitch
parameter to 0.

Using MML Commands

GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box cleared under the Handover

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranFlashCsfbSwitch-0;


7.11 LOFD-081283 Ultra-Flash CSFB to GERAN

This section provides engineering guidelines for LOFD-081283 Ultra-Flash CSFB to
GERAN.
7.11.1 When to Use This Feature

The LOFD-001034 CS Fallback to GERAN feature is recommended in scenarios where the
eNodeB, MME, and MSC are provided by Huawei, and a proportion of UEs in the live
network support SRVCC from E-UTRAN to GERAN. It is recommended that this feature be
activated in GERAN and E-UTRAN overlapping coverage areas.

Before deploying this feature, collect the following information:

eRAN
l Check whether LOFD-001034 CS Fallback to GERAN has been activated.

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

ID Control
Item
LOFD-08 Ultra-Flash CSFB LT1SUFCS Ultra-Flash eNodeB per RRC

1283 to GERAN FB20 CSFB to Connected
GERAN User
7.11.4 Precautions
This feature is a Huawei-proprietary feature and is not supported by devices provided by other
vendors. In addition, this feature must first be activated on the BSC, MME, and MSC, and
then be activated on the eNodeB. This is because this feature is triggered by the eNodeB and
this avoids CSFB failures.

data that you must collect for all scenarios. Required data is data that you must collect for all
scenarios. Collect scenario-specific data when necessary for a specific feature deployment
scenario.
There are three types of data sources: data sources:
operator

eRAN
Required Data
The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For details,
to set the eNodeB-level handover mode and handover algorithm switches for ultra-flash
CSFB to GERAN.

Name ID Source
Handover ENodeBAl Network Select the GeranUltraFlashCsfbS-

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

Handove CellHo Network To activate cell-level blind handovers, select the

r Mode ParaCf plan BlindHoSwitch(BlindHoSwitch) option. To
switch g.HoMo (negotiation activate blind handovers, you still need to activate
deSwitc not eNodeB-level blind handovers.
h required)
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.

Ultra- GeranE Network Clear the UltraFlashCsfbInd check box for

Flash xternal plan external GERAN cells that do not support ultra-
CSFB Cell.Ult (negotiation flash CSFB to GERAN.
capabilit raFlash required)
y CsfbInd
indicator

eRAN
The following table describes the parameter that must be set in the CellDrxPara MO to set
the DRX switch for measurements when UEs support DRX-based measurements.

DRX CellDrx Network When the network supports measurements and UEs
switch Para.Dr plan support DRX measurements well, measurement
for xForMe (negotiation delays are significantly reduced and the customer
measure asSwitc required) can tolerate the impact on services during
ments h measurements.
To enable the DRX switch for measurements, set
DrxForMeasSwitch to 1.
Long CellDrx Network This parameter specifies the length of the long DRX
DRX Para.Lo plan cycle specific to GERAN measurement.
Cycle for ngDrxC (negotiation
Measure ycleFor required)
ment Meas
On CellDrx Network This parameter specifies the length of the On

Duration Para.O plan Duration Timer specific to GERAN measurement.
Timer for nDurTi (negotiation
Measure merFor required)
ment Meas
DRX CellDrx Network This parameter specifies the length of the DRX
Inactivity Para.Dr plan Inactivity Timer specific to GERAN measurement.
Timer for xInactTi (negotiation
Measure merFor required)
ment Meas
DRX CellDrx Network This parameter specifies the length of the DRX
Retransm Para.Dr plan Retransmission Timer specific to GERAN
ission xReTxT (negotiation measurement.
Timer for imerFor required)
Measure Meas
ment
Short CellDrx Network This parameter specifies whether short-period DRX

DRX Para.Sh plan is enabled for GERAN measurements.
Switch ortDrxS (negotiation
for wForMe required)
Measure as
ment
Short CellDrx Network This parameter specifies the length of the short
DRX Para.Sh plan DRX cycle specific to GERAN measurement.
Cycle for ortDrxC (negotiation
Measure ycleFor required)
ment Meas

eRAN

Short CellDrx Network This parameter specifies the length of the Short
Cycle Para.Sh plan Cycle Timer specific to GERAN measurement.
Timer for ortCycle (negotiation
Measure TimerF required)
ment orMeas
The following table describes the parameters that must be set in the
GLOBALPROCSWITCH MO to turn on the UE compatibility switch when UEs do not
support Ultra-Flash CSFB, resulting in UE compatibility problems.

Ue GlobalP Network Select the UltraFlashCsfbComOptSw option of

Compati rocSwit plan the parameter when UEs on the network do not
bility ch.UeC (negotiation support ultra-flash CSFB.
Switch ompatS required) When the MME provided by Huawei allows IMEI
witch whitelist configurations for ultra-flash CSFB and the
option is selected, the eNodeB performs ultra-flash
CSFB on UEs in the IMEI whitelist. Therefore,
delete the UEs that do not support ultra-flash CSFB
from the whitelist before selecting the option.
Otherwise, keep the option unselected.
eNodeBs
file.
parameters.

eRAN

Summary
Data File
GeranNfreq GeranNfreqGro See 7.11.5.1 Data The RNP template sheet is

Group up Preparation. recommended.
GeranNfreq GeranNfreqGro See 7.11.5.1 Data The RNP template sheet is

GroupArfcn upArfcn Preparation. recommended.
GeranExtern GeranExternalC See 7.11.5.1 Data The RNP template sheet is

alCell ell Preparation. recommended.
GeranExtern GeranExternalC See 7.11.5.1 Data The RNP template sheet is

alCellPlmn ellPlmn Preparation. recommended.
GeranNcell GeranNcell See 7.11.5.1 Data The RNP template sheet is

ENodeBAlg User-defined See 7.11.5.1 Data This parameter must be

oSwitch sheet. Preparation. customized on a list-type
witch is
recommended.
CellHoPara User-defined See 7.11.5.1 Data This parameter must be

Cfg sheet. Preparation. customized on a list-type
is
recommended.

BlindHoCfg sheet. Preparation. customized on a list-type
CSFallBackBli sheet of the template.
ndHoCfg is
recommended.

Ho sheet. Preparation. customized on a list-type
is
recommended.
InterRatHoC User-defined See 7.11.5.1 Data This parameter must be

omm sheet. Preparation. customized on a list-type
mm is
recommended.
GlobalProcS User-defined See 7.11.5.1 Data This parameter must be

witch sheet. Preparation. customized on a list-type
GlobalProcSwi sheet of the template.
tch is
recommended.

eRAN
Batch Activation
----End

window.

eRAN
----End
Using MML Commands

l Basic scenario
GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the Handover Algo
switch parameter selected.
Step 3 (Optional) Run the MOD GlobalProcSwitch command with the IratMeasCfgTransSwitch
option of the ProtocolMsgOptSwitch parameter selected if you need to optimize "G2L Fast
Return after Ultra-Flash CSFB to UTRAN" based on the E-UTRA frequency capability
supported by UEs. The eNodeB transfers E-UTRA frequency information supported by UEs
to the BSC during the SRVCC.
Step 4 (Optional) Run the MO GERANEXTERNALCELL command with the Ultra-Flash CSFB
capability indicator parameter set to BOOLEAN_FALSE if some external GERAN cells do
not support ultra-flash CSFB to UTRAN.

eRAN
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
Step 1 Run the MOD GLOBALPROCSWITCH command with the

UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw) option of the UE Compatibility
Switch parameter selected.
----End

l Basic scenario
MOD ENODEBALGOSWITCH: HoAlgoSwitch= GeranUltraFlashCsfbSwitch-1;
MOD GlobalProcSwitch: ProtocolMsgOptSwitch=IratMeasCfgTransSwitch-1;
MOD GERANEXTERNALCELL: Mcc="302", Mnc="220", GeranCellId=2, Lac=12,
UltraFlashCsfbInd=BOOLEAN_TRUE;
MOD CELLDRXPARA: LocalCellId=0, DrxForMeasSwitch=1;LongDrxCycleForMeas=SF160,
OnDurTimerForMeas=PSF2, DrxInactTimerForMeas=PSF2, DrxReTxTimerForMeas=PSF4,
ShortDrxSwForMeas=1, ShortDrxCycleForMeas=SF20, ShortCycleTimerForMeas=1;
MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;

To use signaling tracing to verify whether this feature has been activated, perform the
following steps:
1. As shown in the following figure, the HANDOVER REQUIRED message sent from the
eNodeB to the MME over the S1 interface contains handover request cause values "cs-
fallback-triggered" and "sRVCCHOIndication-cSonly (1)", indicating that a ultra-flash
CSFB to GERAN is triggered successfully.
2. The UE falls back to a GERAN cell and completes the call.

eRAN
Figure 7-22 HANDOVER REQUIRED message
Counter Observation
The counter listed in the following table can be monitored to check whether the feature has
been activated.
Table 7-56 Performance counters for ultra-flash CSFB to GERAN


RVCC.E2G.PrepAt attempts from E-UTRAN to GERAN for ultra-
tOut flash CSFB to GERAN
7.11.7 Deactivation
for Existing eNodeBs. In the procedure, modify parameters according to the following table.

eRAN
Table 7-57 Parameter related to ultra-flash CSFB to GERAN

ENodeBAlgoSwit User-defined sheet. HoAlgoSwit To deactivate the Ultra-Flash

ch ENodeBAlgoSwitch ch CSFB to GERAN feature
is recommended. Deselect the
GeranUltraFlashCsfbS-
witch option.

Using MML Commands

GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the Handover Algo
switch parameter deselected.

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranUltraFlashCsfbSwitch-0;

Table 7-58 lists the counters used to monitor the performance of ultra-flash CSFB to GERAN
Table 7-58 Counters related to ultra-flash CSFB to GERAN

1526733006 L.IRATHO.CSFB Number of SRVCC-based outgoing

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

.SRVCC.E2G.Exe GERAN outgoing handover executions for
cAttOut ultra-flash CSFB to to GERAN
1526733008 L.IRATHO.CSFB Number of successful SRVCC-based

.SRVCC.E2G.Exe EUTRAN-to-GERAN outgoing handovers
cSuccOut for ultra-flash CSFB to GERAN
1526733009 L.IRATHO.CSFB Number of abnormal responses from the

.SRVCC.E2G.M MME during EUTRAN-to-GERAN
MEAbnormRsp handovers for ultra-flash CSFB to GERAN
Success rate of handovers for ultra-fast CSFB to GERAN =

(L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut -

eRAN
L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp)/
L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut

7.12 LOFD-001069 CS Fallback with LAI to GERAN

This section provides engineering guidelines for LOFD-001069 CS Fallback with LAI to
GERAN.
7.12.1 When to Use CS Fallback with LAI to GERAN

Use LOFD-001069 CS Fallback with LAI to GERAN when both of the following conditions
are met:
l LOFD-001034 CS Fallback to GERAN has been enabled.
l The E-UTRAN cell has neighboring GERAN cells that belong to different PLMNs and
supports inter-PLMN handovers, or the E-UTRAN cell has neighboring GERAN cells
that have different LACs.
If both LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to GERAN
have been enabled, you are advised to enable both LOFD-001069 CS Fallback with LAI to
GERAN and LOFD-001068 CS Fallback with LAI to UTRAN.

l Collect information about whether LOFD-001034 CS Fallback to GERAN has been
activated.
networks, and ensure that they all support CSFB and the MME supports LAI delivery.
Table 7-59 describes the requirements of CSFB with LAI to GERAN for the core
networks.

eRAN
Table 7-59 Requirements of CSFB with LAI to GERAN for core networks
NE Requirement
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the
serving cell
l Combined EPS/IMSI attach,
combined EPS/IMSI detach, and
combined TAU/LAU
l CS signaling message routing
l SMS over SGs
l LAI delivery
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the
SGs interface
SGSN Does not activate ISR during the

combined RAU/LAU procedure initiated
by the UE.
network:
whether to perform CSFB based on handover or redirection. For details, see Inter-
RAT Mobility Management in Connected Mode.
7.12.3 Requirements
License

eRAN
Table 7-60 License information for CSFB with LAI to GERAN

Feature Feature Name Mode License NE Sales Unit
ID l Control Item
LOFD-001 CS Fallback with LT1S0 CS Fallback eNode per RRC

069 LAI to GERAN CSFL with LAI to B Connected User
G00 GERAN
7.12.4 Precautions
None

This feature is automatically activated when two conditions are met: The license for this
feature has been purchased. CSFB to GERAN has been activated.

Data preparation for activating CSFB with LAI to GERAN is the same as that for activating
CSFB to GERAN. For details, see 7.8.5.1 Data Preparation.
eNodeBs
For details, see 7.8.5.2 Using the CME to Perform Batch Configuration for Newly
Deployed eNodeBs.
For details, see 7.8.5.3 Using the CME to Perform Batch Configuration for Existing
eNodeBs.

For details, see 7.8.5.4 Using the CME to Perform Single Configuration.

For details, see 7.8.5.6 Using MML Commands.

1. Configure two neighboring GERAN cells with different LAIs for an E-UTRAN cell, and
enable the MME to include only one of the two LAIs in the instructions that will be
delivered to the eNodeB.
2. Ensure that the signal strengths of the two GERAN cells both reach the threshold for
event B1. You can query the threshold by running the LST
INTERRATHOGERANGROUP command.

eRAN
3. Enable a UE to camp on the E-UTRAN cell and make a voice call.

4. Enable the UE to camp on the E-UTRAN cell and receive a voice call.
You can observe the signaling procedure for CSFB with LAI to GERAN, which is similar to
that for CSFB to GERAN described in 7.9.6 Activation Observation. The difference is that
the Initial Context Setup Request or UE Context Mod Request message carries the LAI that
the MME delivers to the eNodeB, as shown in the following figure:
Figure 7-23 LAI signaling tracing
7.12.7 Deactivation
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 7.8.7 Deactivation.


7.13 LOFD-001089 CS Fallback Steering to GERAN

This section provides engineering guidelines for LOFD-001089 CS Fallback Steering to
GERAN.
7.13.1 When to Use CS Fallback Steering to GERAN

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

eRAN

1. Collect information about whether LOFD-001034 CS Fallback to GERAN has been
activated.
2. Collect the following information about the UEs that support GSM and LTE on the live
network:
Whether the UEs support CCO from E-UTRAN to GERAN
whether to perform CSFB based on handover, redirection, or CCO. For details, see Inter-
RAT Mobility Management in Connected Mode Feature Parameter Description.
3. Collect information about the frequencies and frequency policies of the GERAN.
Frequency policies must be the same for GERAN and E-UTRAN.
4. If LOFD-001088 CS Fallback Steering to UTRAN is also to be activated, consider the
UTRAN frequencies when making frequency policies.
7.13.3 Requirements
License
Table 7-61 License information for CSFB steering to GERAN

Feature ID Feature Name Model License NE Sales Unit
Control
Item
LOFD-001089 CS Fallback LT1S0CF CS Fallback eNode per RRC

Steering to BSG00 Steering to B Connected
GERAN GERAN User
7.13.4 Precautions
None

eRAN

operator
Required Data
The required data is the same as that for CS Fallback to GERAN. For details, see 7.8.5.1 Data
Preparation.
to enable CSFB steering to GERAN.

Handover ENodeB Network Select the GeranCsfbSteeringS-

Algo AlgoSwi plan witch(GeranCsfbSteeringSwitch) check box
switch tch.HoA (negotiation under this parameter.
lgoSwitc not
h required)
MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.

eter ID Source
Name
CN CSFallBack Networ Set this parameter based on the network plan. This
Operat BlindHoCfg. k plan parameter identifies the operator whose RAT blind-
or ID CnOperatorI (negoti handover priorities are to be set.
d ation
not
require
d)

eRAN

eter ID Source
Name
Highes CSFallBack Networ Set this parameter based on the network plan. This
t BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
priority InterRatHig (negoti the highest-priority RAT to be considered in blind
InterRa hestPri ation handovers for CSFB.
t not
require
d)
Second CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to GERAN by default and specifies
InterRa InterRatSeco (negoti the second-highest-priority RAT to be considered in
t ndPri ation blind handovers for CSFB. Ensure that this parameter
require Pri and InterRatLowestPri parameters.
d)
Lowest CSFallBack Networ Set this parameter based on the network plan. This
priority BlindHoCfg. k plan parameter is set to CDMA2000 by default and
InterRa InterRatLow (negoti specifies the low-priority RAT to be considered in
t estPri ation blind handovers for CSFB. Ensure that this parameter
require Pri and InterRatSecondPri parameters.
d)
GERA CSFallBack Networ Set this parameter based on the network plan. This
N LCS BlindHoCfg. k plan parameter specifies the LCS capability of the
capabil GeranLcsCa (negoti GERAN.
ity p ation
not
require
d)
MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.

eter ID Source
Name
Highes BlindHoCfg. k plan parameter is set to UTRAN by default and specifies
t IdleCsfbHig (negoti the highest-priority RAT to be considered in CSFB for
priority hestPri ation UEs in idle mode.
InterRa not
t for require
Idle d)
UE

eRAN

eter ID Source
Name
Second BlindHoCfg. k plan parameter is set to GERAN by default and specifies
priority IdleCsfbSeco (negoti the second-highest-priority RAT to be considered in
InterRa ndPri ation CSFB for UEs in idle mode. Ensure that this
Idle require InterRatHighestPri and InterRatLowestPri
UE d) parameters.
Lowest BlindHoCfg. k plan parameter is set to CDMA2000 by default and
priority IdleCsfbLow (negoti specifies the lowest-priority RAT to be considered in
InterRa estPri ation CSFB for UEs in idle mode. Ensure that this
Idle require InterRatHighestPri and InterRatSecondPri
UE d) parameters.
MO to set the CSFB policy for RRC_CONNECTED UEs.

eter ID Source
Name
handov PolicyCfg.C k plan default values are REDIRECTION, CCO_HO, and
er sfbHoPolicy (negoti PS_HO. You are advised to set this parameter based
policy Cfg ation on the UE capabilities and network capabilities. For
d)
MO to set the CSFB policy for RRC_IDLE UEs.

eRAN

eter ID Source
Name
handov PolicyCfg.Id k plan default values are REDIRECTION, CCO_HO, and
er leModeCsfb (negoti PS_HO. You are advised to set this parameter based
policy HoPolicyCfg ation on the UE capabilities and network capabilities. For
for idle d)
ue
eNodeBs
file.
parameters.
Table 7-62 Parameters for CSFB steering to GERAN

Summary
Data File
ENodeBAlgoSwitc User-defined Handover Algo switch This parameter

h sheet. must be
ENodeBAlgoS customized on a
witch is list-type sheet of

eRAN

Summary
Data File
CSFallBackBlind- User-defined CN Operator ID, Highest This parameter

HoCfg sheet. priority InterRat, Second must be
CSFallBackBli priority InterRat, Lowest customized on a
ndHoCfg is priority InterRat, CSFB list-type sheet of
recommended. Highest priority InterRat for the template.
Idle UE, CSFB Second
priority InterRat for Idle UE,
CSFB Lowest priority
InterRat for Idle UE
CSFallBackPolicy User-defined CSFB handover policy This parameter

Cfg sheet. Configuration, CSFB must be
CSFallBackPoli handover policy customized on a
cyCfg is Configuration for idle ue list-type sheet of
----End

eRAN

window.
----End
Using MML Commands

The configuration is just an example, and configurations on the live network can differ from
this example. For MML command settings in scenarios where the UTRAN and GERAN
cover the same area but only the GERAN provides contiguous coverage, see 7.6.5 Data
Preparation and Feature Activation.
The prerequisite is that CSFB to GERAN has been activated.

eRAN

GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) check box selected under the
Step 2 Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority
InterRat, Second priority InterRat, CSFB Highest priority InterRat for Idle UE, and
CSFB Second priority InterRat for Idle UE parameters to UTRAN, GERAN, GERAN,
and UTRAN, respectively.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO 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

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-1;
InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GERAN,IdleCsfb
SecondPri=UTRAN;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-1,
IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;

The signaling procedure is the same as that for CSFB to GERAN. After CS Fallback Steering
to GERAN is used, check whether it works as expected.
The activation observation procedure for CSFB steering to GERAN is as follows:
1. Check that the UE supports redirection-based CSFB and handover-based CSFB.
2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection and
handover, respectively.
4. Observe the counters L.CSFB.E2G, L.RRCRedirection.E2G.CSFB, and
L.IRATHO.E2G.CSFB.ExecAttOut. If the values of the counters increase by 2, 1, and 1,
respectively, CSFB steering to GERAN has been activated.
If LOFD-001088 CS Fallback Steering to UTRAN has also been activated, the activation
observation procedure is as follows:
1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.
2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs and
UTRAN as the highest-priority RAT for CSFB triggered for RRC_CONNECTED UEs.
4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase by 1,
both CSFB steering to UTRAN and CSFB steering to GERAN have been activated.
7.13.7 Deactivation

eRAN
for Existing eNodeBs. In the procedure, modify parameters according to Table 7-63.
Table 7-63 Parameters for deactivating CSFB steering to GERAN

Summary Data Group
File
ENodeBAlgoSwitch User-defined HoAlgoSwitc Set GeranCsfbSteeringS-

sheet. h witch under the
ENodeBAlgoSwit HoAlgoSwitch parameter
ch is to 0.
recommended.

Using MML Commands

GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) check box cleared under the

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-0;


7.14 Troubleshooting
7.14.1 CSFB Calling Procedure Failure

Fault Description
A UE performs cell reselection to an inter-RAT neighboring cell directly after initiating a
voice call in an E-UTRAN cell, and the S1 interface tracing result shows that CSFB is not
triggered.

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

eRAN
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
7.14.4 CSFB Handover Failure
Fault Description
During CSFB to UTRAN procedures with the handover policy set to PS HO, the handover
preparation success rate is low.
Table 7-64 Counters related to the handover preparation success rate

1526728504 L.IRATHO.E2W.CSFB.Pre Number of CSFB-based inter-RAT

pAttOut handover preparation attempts from
E-UTRAN to WCDMA network
1526728505 L.IRATHO.E2W.CSFB.Exe Number of CSFB-based inter-RAT

cAttOut handover execution attempts from E-
UTRAN to WCDMA network

eRAN
Fault Handling
Here uses the CSFB to UTRAN as an example to describe the fault handling procedure.
Similar counters are provided for CSFB to GERAN or to other systems.
Step 1 View the counters listed in Table 7-65 to check the cause for the low handover preparation
success rate.
Table 7-65 Counters related to outgoing handover preparation failures

1526730076 L.IRATHO.E2W.CSFB.Pre Number of CSFB-based outgoing

p.FailOut.MME handover preparation failures from E-
UTRAN to WCDMA network because
of the MME side causes

p.FailOut.PrepFailure handover preparation failures from E-
of the response of handover preparation
failure from WCDMA network

p.FailOut.NoReply handover preparation failures from E-
of no response from WCDMA network
Step 2 Analyze the failure cause based on the values of the preceding counters for each NE.
----End

eRAN
CS Fallback Feature Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
eNBRsv RsvdSw MOD None None Meaning:

dPara Para1 ENBRS Indicates reserved 32-bit switch parameter 1 that is
VDPAR reserved for future requirements.
A
LST Note on parameter replacement: Reserved parameters
ENBRS are temporarily used in patch versions and will be
VDPAR replaced with new parameters. For example, the ID of
A a new parameter can signify the parameter function.
Therefore, avoid using this parameter.
GUI Value Range:
RsvdSwPara1_bit1(ReservedSwitchParameter1_bit1),
RsvdSwPara1_bit10(ReservedSwitchParame-
ter1_bit10),
ter1_bit11),
ter1_bit12),
ter1_bit13),
ter1_bit14),
ter1_bit15),

eRAN

nd
ter1_bit16),
ter1_bit17),
ter1_bit18),
ter1_bit19),
ter1_bit20),
ter1_bit21),
ter1_bit22),
ter1_bit23),
ter1_bit24),
ter1_bit25),
ter1_bit26),
ter1_bit27),
ter1_bit28),
ter1_bit29),
ter1_bit30),
ter1_bit31),
ter1_bit32)
Unit: None
Actual Value Range: RsvdSwPara1_bit1,
RsvdSwPara1_bit2, RsvdSwPara1_bit3,

eRAN

nd
RsvdSwPara1_bit32
Default Value: RsvdSwPara1_bit1:Off,
RsvdSwPara1_bit2:Off, RsvdSwPara1_bit3:Off,
RsvdSwPara1_bit32:Off

eRAN

nd
GlobalP UeCom MOD None None Meaning:

rocSwitc patSwitc GLOBA Indicates whether to enable compatibility optimization
h h LPROC functions for UEs to control the differentiated
SWITC handling of abnormal UEs.
H
LST AbnormalUeHandleSwitch: This option is used to
GLOBA control whether to enable handling of abnormal
LPROC UEs.This function is enabled only if this option is
SWITC selected.
H UltraFlashCsfbComOptSw: This option is used to
control whether to enable the optimization of UE
incompatibility risks in ultra-flash CSFB. If this
option is selected, an eNodeB triggers an ultra-flash
CSFB based on the private IE SRVCC based eCSFB
operation possible that the MME sends to the eNodeB.
If this option is not selected, the eNodeB does not
trigger an ultra-flash CSFB procedure based on this
IE.
GUI Value Range: AbnormalUeHandleS-
witch(AbnormalUeHandleSwitch), UltraFlashCsfbCo-
mOptSw(UltraFlashCsfbComOptSw)
Unit: None
Actual Value Range: AbnormalUeHandleSwitch,
UltraFlashCsfbComOptSw
Default Value: AbnormalUeHandleSwitch:Off,
UltraFlashCsfbComOptSw:Off
CellHoP HoMode MOD LOFD-0 CS Meaning:

araCfg Switch CELLH 01033 / Fallback Indicates the handover method switches based on
OPARA LOFD-0 to which the eNodeB determines handover policies.
CFG 01034 / UTRAN
LST TDLOF / CS BlindHoSwitch: This option controls whether to
CELLH D-00103 Fallback enable blind handovers for CSFB. If both this option
OPARA 3/ to and the BlindHoSwitch option of the Handover Mode
CFG TDLOF GERAN switch parameter of the ENodeBAlgoSwitch MO are
D-00103 / CS selected, blind handovers for CSFB are enabled.
4 Fallback GUI Value Range: BlindHoSwitch(BlindHoSwitch)
to
UTRAN Unit: None
/ CS Actual Value Range: BlindHoSwitch
Fallback Default Value: BlindHoSwitch:Off
to
GERAN

eRAN

nd
GeranEx UltraFla ADD LOFD-0 Ultra- Meaning: Indicates whether an external GERAN cell
ternalCe shCsfbI GERAN 81283 / Flash supports ultra-flash CSFB to GERAN. If this
ll nd EXTER TDLOF CSFB to parameter is set to BOOLEAN_TRUE, the external
NALCE D-08120 GERAN GERAN cell supports ultra-flash CSFB to GERAN. If
LL 3 this parameter is set to BOOLEAN_FALSE, the
MOD external GERAN cell does not support ultra-flash
GERAN CSFB to GERAN.
EXTER GUI Value Range: BOOLEAN_FALSE(False),
NALCE BOOLEAN_TRUE(True)
LL Unit: None
LST Actual Value Range: BOOLEAN_FALSE,
GERAN BOOLEAN_TRUE
EXTER
NALCE Default Value: BOOLEAN_TRUE(True)
LL

eRAN

nd
ENodeB HoAlgo MOD LBFD-0 Coverag Meaning: Indicates whether to enable handover
AlgoSwi Switch ENODE 0201801 e Based algorithms. The switches are described as follows:
tch BALGO / Intra- IntraFreqCoverHoSwitch: If this switch is on,
SWITC TDLBF frequenc coverage-based intra-frequency handovers are enabled
H D-00201 y to ensure service continuity. If this switch is off,
LST 801 Handov coverage-based intra-frequency handovers are
ENODE LBFD-0 er disabled. InterFreqCoverHoSwitch: If this switch is
BALGO 0201802 Distance on, coverage-based inter-frequency handovers are
SWITC / Based enabled to ensure service continuity. If this switch is
H TDLBF Inter- off, coverage-based inter-frequency handovers are
D-00201 frequenc disabled. UtranCsfbSwitch: If this switch is on, CSFB
802 y to UTRAN is enabled and UEs can fall back to
Handov UTRAN. If this switch is off, CSFB to UTRAN is
LBFD-0 disabled. GeranCsfbSwitch: If this switch is on, CSFB
er
0201804 to GERAN is enabled and UEs can fall back to
/ Service
GERAN. If this switch is off, CSFB to GERAN is
TDLBF Based
disabled. Cdma1xRttCsfbSwitch: If this switch is on,
D-00201 Inter-
CSFB to CDMA2000 1xRTT is enabled and UEs can
804 frequenc
fall back to CDMA2000 1xRTT. If this switch is off,
y
LBFD-0 CSFB to CDMA2000 1xRTT is disabled.
Handov
0201805 UtranServiceHoSwitch: If this switch is on, service-
er
/ based handovers to UTRAN are enabled and UEs
TDLBF CS running a specific type of services can be handed over
D-00201 Fallback to UTRAN. If this switch is off, service-based
805 to handovers to UTRAN are disabled.
UTRAN GeranServiceHoSwitch: If this switch is on, service-
LOFD-0
CS based handovers to GERAN are enabled and UEs
01033 /
Fallback running a specific type of services can be handed over
TDLOF
to to GERAN. If this switch is off, service-based
D-00103
GERAN handovers to GERAN are disabled.
3
CS CdmaHrpdServiceHoSwitch: If this switch is on,
LOFD-0 Fallback service-based handovers to CDMA2000 HRPD cells
01034 / to are enabled and UEs running a specific type of
TDLOF CDMA2 services can be handed over to CDMA2000 HRPD
D-00103 000 cells. If this switch is off, service-based handovers to
4 1xRTT CDMA2000 HRPD cells are disabled.This parameter
LOFD-0 is unavailable in this version.
Flash
01035 / Cdma1xRttServiceHoSwitch: If this switch is on,
CS
TDLOF service-based handovers to CDMA2000 1xRTT are
Fallback
D-00103 enabled and UEs running a specific type of services
to
5 can be handed over to CDMA2000 1xRTT. If this
UTRAN
switch is off, service-based handovers to CDMA2000
LOFD-0 Flash 1xRTT are disabled.This parameter is unavailable in
01052 / CS this version. UlQualityInterRATHoSwitch: If this
TDLOF Fallback switch is on, UL-quality-based inter-RAT handovers
D-00105 to are enabled and UEs can be handed over to inter-RAT
2 GERAN cells to ensure service continuity when the UL signal
LOFD-0 CS quality is poor. If this switch is off, UL-quality-based
01053 / Fallback

eRAN

nd
TDLOF Steering inter-RAT handovers are disabled.

D-00105 to InterPlmnHoSwitch: If this switch is on, inter-PLMN
3 UTRAN handovers are enabled and UEs can be handed over to
LOFD-0 CS cells in other PLMNs. If this switch is off, inter-
01088 / Fallback PLMN handovers are disabled. UtranFlashCsfbS-
TDLOF Steering witch: This switch takes effect only when
D-00108 to UtranCsfbSwitch is on. If UtranFlashCsfbSwitch is
8 GERAN on, flash CSFB to UTRAN is enabled and the eNodeB
sends system information of candidate target UTRAN
LOFD-0 Enhance
cells to UEs during redirections. If UtranFlashCsfbS-
01089 / d CS
witch is off, flash CSFB to UTRAN is disabled.
TDLOF Fallback
GeranFlashCsfbSwitch: This switch takes effect only
D-00108 to
when GeranCsfbSwitch is on. If GeranFlashCsfbS-
9 CDMA2
witch is on, flash CSFB to GERAN is enabled and the
000
LOFD-0 eNodeB sends system information of candidate target
1xRTT
01090 / GERAN cells to UEs during redirections. If
TDLOF PS Inter- GeranFlashCsfbSwitch is off, flash CSFB to GERAN
D-00109 RAT is disabled. ServiceBasedInterFreqHoSwitch: If this
0 Mobility switch is on, service-based inter-frequency handovers
between are enabled and UEs running a specific type of
LOFD-0
E- services can be handed over to inter-frequency cells. If
01019 /
UTRAN this switch is off, service-based inter-frequency
TDLOF
and handovers are disabled. UlQualityInterFreqHoSwitch:
D-00101
UTRAN If this switch is on, UL-quality-based inter-frequency
9
PS Inter- handovers are enabled and UEs can be handed over to
LOFD-0 inter-frequency cells to ensure service continuity when
RAT
01020 / the UL signal quality is poor. If this switch is off, UL-
Mobility
TDLOF quality-based inter-frequency handovers are disabled.
between
D-00102 CsfbAdaptiveBlindHoSwitch: This switch takes effect
E-
0 only when BlindHoSwitch is on. If
UTRAN
LOFD-0 and CsfbAdaptiveBlindHoSwitch is on, adaptive blind
01043 / GERAN handovers for CSFB are enabled and appropriate
TDLOF handover mechanisms are selected for UEs based on
Service
D-00104 their locations. If CsfbAdaptiveBlindHoSwitch is off,
based
3 adaptive blind handovers for CSFB are disabled.
inter-
LOFD-0 RAT UtranCsfbSteeringSwitch: If this switch is on, CSFB
01046 / handove steering to UTRAN is enabled and CSFB policies for
TDLOF r to UEs in idle mode can be configured. If this switch is
D-00104 UTRAN off, CSFB steering to UTRAN is disabled.
6 GeranCsfbSteeringSwitch: If this switch is on, CSFB
Service steering to GERAN is enabled and CSFB policies for
LOFD-0 based UEs in idle mode can be configured. If this switch is
01072 / inter- off, CSFB steering to GERAN is disabled.
TDLOF RAT CSFBLoadInfoSwitch: If this switch is on, load-based
D-00107 handove CSFB is enabled and a target cell for CSFB is selected
2 r to based on loads of candidate target cells. If this switch
LOFD-0 GERAN is off, load-based CSFB is disabled.
01073 / Distance Cdma1XrttEcsfbSwitch: If this switch is on, eCSFB to
TDLOF based

eRAN

nd
D-00107 inter- CDMA2000 1xRTT is enabled and UEs can fall back
3 RAT to CDMA2000 1xRTT through handovers. If this
TDLBF handove switch is off, eCSFB to CDMA2000 1xRTT is
D-00201 r to disabled. EmcBlindHoA1Switch: If this switch is on,
8 UTRAN blind handover event A1 measurements are enabled. If
Distance a blind handover event measurement conflicts with a
TDLOF handover procedure, an emergency blind handover
D-00102 based
inter- can be triggered after the handover procedure is
2 complete. If this switch is off, blind handover event
RAT
TDLOF A1 measurements are disabled. If a blind handover
handove
D-07022 event measurement conflicts with a handover
r to
8 procedure, an emergency blind handover cannot be
GERAN
LOFD-0 triggered. EmcInterFreqBlindHoSwitch: If this switch
Mobility is on, the eNodeB preferentially performs an inter-
81283 /
Manage frequency blind handover when an emergency blind
TDLOF
ment handover is triggered. If this switch is off, the eNodeB
D-08120
3 Coverag only performs an inter-RAT blind handover when an
e Based emergency blind handover is triggered. EPlmnSwitch:
LOFD-0 Indicates whether handovers to neighboring cells
70202 / Inter-
frequenc under the equivalent PLMNs (EPLMNs) are allowed.
TDLOF When inter-PLMN handovers are allowed, handovers
D-07020 y
Handov to neighboring cells under the EPLMNs are allowed if
2 this switch is on, and not allowed if this switch is off.
er
TDLOF The EPLMNs are delivered by the MME to the UE.
D-08122 SRVCC ServiceReqInterFreqHoSwitch: If this switch is on,
3 to service request-based inter-frequency handovers are
UTRAN enabled and UEs using a specific type of services can
Service- be handed over to inter-frequency cells. If this switch
Request is off, service request-based inter-frequency handovers
Based are disabled. This option applies only to LTE TDD
Inter- networks. VoipHoControlSwitch: Indicates whether
frequenc the eNodeB filters out target cells that do not support
y VoIP services when processing intra-RAT handovers
Handov for VoIP services. The eNodeB filters out such target
er cells in the preceding scenario only when this switch
Ultra- is on. UtranUltraFlashCsfbSwitch: In this switch is on,
Flash ultra-flash CSFB to UTRAN is enabled and UEs can
CSFB to fall back to UTRAN based on the ultra-flash CSFB
GERAN procedure. If this switch is off, ultra-flash CSFB to
UTRAN is disabled. GeranUltraFlashCsfbSwitch: In
Ultra- this switch is on, ultra-flash CSFB to GERAN is
Flash enabled and UEs can fall back to GERAN based on
CSFB to the ultra-flash CSFB procedure. If this switch is off,
UTRAN ultra-flash CSFB to GERAN is disabled.
Ultra- GUI Value Range: IntraFreqCoverHoS-
Flash witch(IntraFreqCoverHoSwitch), InterFreqCoverHoS-
CSFB to witch(InterFreqCoverHoSwitch),
UTRAN UtranCsfbSwitch(UtranCsfbSwitch),

eRAN

nd
GeranCsfbSwitch(GeranCsfbSwitch),
Cdma1xRttCsfbSwitch(Cdma20001xRttCsfbSwitch),
UtranServiceHoSwitch(UtranServiceHoSwitch),
GeranServiceHoSwitch(GeranServiceHoSwitch),
CdmaHrpdServiceHoS-
witch(Cdma2000HrpdServiceHoSwitch),
Cdma1xRttServiceHoSwitch(Cdma20001xRttService
HoSwitch), UlQualityInterRATHoS-
witch(UlQualityInterRATHoSwitch),
InterPlmnHoSwitch(InterPlmnHoSwitch),
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch),
GeranFlashCsfbSwitch(GeranFlashCsfbSwitch),
ServiceBasedInterFreqHoSwitch(ServiceBasedInter-
FreqHoSwitch), UlQualityInterFreqHoS-
witch(UlQualityInterFreqHoSwitch),
CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlind-
HoSwitch), UtranCsfbSteeringS-
witch(UtranCsfbSteeringSwitch),
GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch),
CSFBLoadInfoSwitch(CSFBLoadInfoSwitch),
Cdma1XrttEcsfbSwitch(Cdma1XrttEcsfbSwitch),
EmcBlindHoA1Switch(EmcBlindHoA1Switch),
EmcInterFreqBlindHoSwitch(EmcInterFreqBlind-
HoSwitch), EPlmnSwitch(EPlmnSwitch),
ServiceReqInterFreqHoSwitch(ServiceReqInterFreq-
HoSwitch),
VoipHoControlSwitch(VoipHoControlSwitch),
UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbS-
witch), GeranUltraFlashCsfbS-
witch(GeranUltraFlashCsfbSwitch)
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

eRAN

nd
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,
UtranUltraFlashCsfbSwitch:Off,
GeranUltraFlashCsfbSwitch:Off
CSFallB UtranCs MOD LOFD-0 CS Meaning: Indicates whether the eNodeB selects the
ackBlin fbBlind CSFAL 01033/ Fallback target frequency in a round robin (RR) manner from
dHoCfg RedirRr LBACK TDLOF to frequencies with the same priority in blind
Sw BLIND D-00103 UTRAN redirections for CSFB to UTRAN. If this parameter is
HOCFG 3 Flash set to ON(On), the function of target frequency
LST LOFD-0 CS selection in an RR manner is enabled. If this
CSFAL 01052/ Fallback parameter is set to OFF(Off), this function is disabled.
LBACK TDLOF to GUI Value Range: OFF(OFF), ON(ON)
BLIND D-00105 UTRAN Unit: None
HOCFG 2
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
CellDrx DrxFor MOD LOFD-0 Ultra- Meaning: Indicates whether to deliver DRX
Para MeasSw CELLD 81283 / Flash parameters dedicated for measurement to UEs
itch RXPAR TDLOF CS performing CSFB-triggered GSM measurement. If
A D-08120 Fallback this parameter is set to OFF, the eNodeB configures
LST 3 to only a measurement gap for UEs to perform CSFB-
CELLD GERAN triggered GSM measurement. If this parameter is set
RXPAR to ON, the eNodeB configures both DRX parameters
A and measurement gaps for UEs to perform CSFB-
triggered GSM measurement.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

eRAN

nd
ENodeB FreqLay MOD LOFD-0 SRVCC Meaning: This parameter includes the following three
AlgoSwi erSwtich ENODE 01087 Flexible switches: UtranFreqLayerMeasSwitch,
tch BALGO LOFD-0 Steering UtranFreqLayerBlindSwitch, and UtranSrvccSwitch.
SWITC 01078 / to The setting of UtranSrvccSwitch takes effect only
H TDLOF UTRAN when UtranFreqLayerMeasSwitch is on. If
LST D-00107 E- UtranFreqLayerMeasSwitch is on, the UTRAN
ENODE 8 UTRAN hierarchy-based measurement algorithm takes effect
BALGO to for measurements related to coverage-based and
TDLOF CSFB-triggered handovers from E-UTRAN to
SWITC D-00102 UTRAN
H CS/PS UTRAN. If UtranFreqLayerBlindSwitch is on, the
2 UTRAN hierarchy-based blind-handover algorithm
Steering
TDLOF takes effect for coverage-based and CSFB-triggered
D-00103 SRVCC blind handovers from E-UTRAN to UTRAN. If
3 to UtranSrvccSwitch is on, the UTRAN SRVCC
UTRAN hierarchy-based measurement algorithm takes effect
TDLOF
D-00105 CS for coverage-based SRVCC-triggered handovers from
2 Fallback E-UTRAN to UTRAN.
TDLOF to GUI Value Range: UtranFreqLayerMeasS-
D-00108 UTRAN witch(UtranFreqLayerMeasSwitch),
8 Flash UtranFreqLayerBlindSwitch(UtranFreqLayerBlind-
CS Switch), UtranSrvccSteeringSwitch(UtranSrvccSteer-
Fallback ingSwitch)
to Unit: None
UTRAN Actual Value Range: UtranFreqLayerMeasSwitch,
CS UtranFreqLayerBlindSwitch, UtranSrvccSteeringS-
Fallback witch
Steering Default Value: UtranFreqLayerMeasSwitch:Off,
to UtranFreqLayerBlindSwitch:Off, UtranSrvccSteer-
UTRAN ingSwitch:Off

eRAN

nd
UtranNF CsPriori ADD LOFD-0 E- Meaning: Indicates the circuit switched (CS) priority
req ty UTRAN 01078 / UTRAN of the neighboring UTRAN frequency, that is, the
NFREQ TDLOF to priority for the neighboring UTRAN frequency to
MOD D-00107 UTRAN carry CS services. During CSFB-based CS service
UTRAN 8 CS/PS handovers with UtranFreqLayerMeasSwitch being on,
NFREQ TDLOF Steering the eNodeB selects and delivers the neighboring
D-00103 CS UTRAN frequencies based on the CS priorities when
LST starting measurements. The eNodeB preferentially
UTRAN 3 Fallback
to delivers the UTRAN frequency with the highest CS
NFREQ TDLOF priority to measure. During CSFB-based CS service
D-00105 UTRAN
handovers with UtranFreqLayerBlindSwitch being on,
2 Flash the eNodeB selects the target cells for blind handovers
TDLOF CS on neighboring UTRAN frequencies based on the CS
D-00108 Fallback priorities and preferentially selects the target cell for
8 to blind handovers on the neighboring UTRAN
UTRAN frequency with the highest CS priorities. If this
CS parameter is set to Priority_0, this neighboring
Fallback UTRAN frequency is not prioritized.
Steering GUI Value Range: Priority_0(Priority 0),
to Priority_1(Priority 1), Priority_2(Priority 2),
UTRAN Priority_3(Priority 3), Priority_4(Priority 4),
Priority_5(Priority 5), Priority_6(Priority 6),
Priority_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_14, Priority_15, Priority_16
Default Value: Priority_2(Priority 2)

eRAN

nd
CSFallB IdleCsfb MOD LOFD-0 CS Meaning:

ackBlin Highest CSFAL 01035 / Fallback Indicates the highest-priority RAT for CSFB initiated
dHoCfg Pri LBACK TDLOF to by a UE in idle mode. It is UTRAN by default. If this
BLIND D-00103 CDMA2 parameter is set to UTRAN, GERAN, or CDMA2000,
HOCFG 5 000 the highest-priority RAT is UTRAN, GERAN, or
LST LOFD-0 1xRTT CDMA2000, respectively.
CSFAL 01088 / CS
LBACK TDLOF Fallback The value CDMA2000 is invalid in the current
BLIND D-00108 Steering version. Therefore, avoid setting this parameter to
HOCFG 8 to CDMA2000.
LOFD-0 UTRAN GUI Value Range: UTRAN, GERAN, CDMA2000

01089 / CS Unit: None
TDLOF Fallback Actual Value Range: UTRAN, GERAN, CDMA2000
D-00108 Steering
9 to Default Value: UTRAN
TDLOF GERAN
D-00109 Enhance
0 d CS
Fallback
to
CDMA2
000
1xRTT

ackBlin SecondP CSFAL 01035 / Fallback Indicates the medium-priority RAT for CSFB initiated
dHoCfg ri LBACK TDLOF to by a UE in idle mode. It is GERAN by default. If this
BLIND D-00103 CDMA2 parameter is set to UTRAN, GERAN, or CDMA2000,
HOCFG 5 000 the medium-priority RAT is UTRAN, GERAN, or
LST LOFD-0 1xRTT CDMA2000, respectively. If this parameter is set to
CSFAL 01088 / CS NULL, no medium-priority RAT is specified and only
LBACK TDLOF Fallback the highest-priority RAT can be selected for CSFB
BLIND D-00108 Steering initiated by a UE in idle mode.
HOCFG 8 to
UTRAN The value CDMA2000 is invalid in the current
LOFD-0 version. Therefore, avoid setting this parameter to
01089 / CS CDMA2000.
TDLOF Fallback
D-00108 Steering GUI Value Range: UTRAN, GERAN, CDMA2000,
9 to NULL
TDLOF GERAN Unit: None

D-00109 Enhance Actual Value Range: UTRAN, GERAN, CDMA2000,
0 d CS NULL
Fallback Default Value: GERAN
to
CDMA2
000
1xRTT

eRAN

nd

ackBlin LowestP CSFAL 01035 / Fallback Indicates the lowest-priority RAT for CSFB initiated
dHoCfg ri LBACK TDLOF to by a UE in idle mode. It is CDMA2000 by default. If
BLIND D-00103 CDMA2 this parameter is set to UTRAN, GERAN, or
HOCFG 5 000 CDMA2000, the lowest-priority RAT is UTRAN,
LST LOFD-0 1xRTT GERAN, or CDMA2000, respectively. If this
CSFAL 01088 / CS parameter is set to NULL, no lowest-priority RAT is
LBACK TDLOF Fallback specified and only the highest- or medium-priority
BLIND D-00108 Steering RAT can be selected for CSFB initiated by a UE in
HOCFG 8 to idle mode.
LOFD-0 UTRAN
The value CDMA2000 is invalid in the current
01089 / CS version. Therefore, avoid setting this parameter to
TDLOF Fallback CDMA2000.
D-00108 Steering
9 to GUI Value Range: UTRAN, GERAN, CDMA2000,
GERAN NULL
TDLOF
D-00109 Enhance Unit: None
0 d CS Actual Value Range: UTRAN, GERAN, CDMA2000,
Fallback NULL
to Default Value: CDMA2000
CDMA2
000
1xRTT
CSFallB IdleMod MOD LOFD-0 CS Meaning: Indicates the CSFB policy for a UE in idle
ackPolic eCsfbHo CSFAL 01088 / Fallback mode. The policy can be PS handover, CCO, or
yCfg PolicyCf LBACK TDLOF Steering redirection.
g POLIC D-00108 to GUI Value Range: REDIRECTION, CCO_HO,
YCFG 8 UTRAN PS_HO
LST LOFD-0 CS Unit: None
CSFAL 01089 / Fallback
LBACK TDLOF Steering Actual Value Range: REDIRECTION, CCO_HO,
POLIC D-00108 to PS_HO
YCFG 9 GERAN Default Value: REDIRECTION:On, CCO_HO:On,
PS_HO:On

eRAN

nd
CSFallB InterRat MOD LOFD-0 CS Meaning:

ackBlin Highest CSFAL 01033 / Fallback Indicates the highest-priority RAT for handovers. It is
dHoCfg Pri LBACK TDLOF to UTRAN by default. If this parameter is set to
BLIND D-00103 UTRAN UTRAN, GERAN, or CDMA2000, the highest-
HOCFG 3 CS priority RAT is UTRAN, GERAN, or CDMA2000,
LST LOFD-0 Fallback respectively.
CSFAL 01034 / to
LBACK TDLOF GERAN The value CDMA2000 is invalid in the current
BLIND D-00103 version. Therefore, avoid setting this parameter to
CS CDMA2000.
HOCFG 4 Fallback
to GUI Value Range: UTRAN, GERAN, CDMA2000
LOFD-0
01035 / CDMA2 Unit: None
TDLOF 000 Actual Value Range: UTRAN, GERAN, CDMA2000
D-00103 1xRTT
Default Value: UTRAN
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-00105 GERAN
2 PS Inter-
TDLOF RAT
D-00105 Mobility
3 between
E-
TDLOF
UTRAN
D-00109
and
0
CDMA2
TDLOF 000
D-00104
Flash
3
CS
TDLOF Fallback
D-00107 to
2 UTRAN
TDLOF Flash
D-00104 CS
6 Fallback

eRAN

nd
TDLOF to
D-00107 GERAN
3 Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN

eRAN

nd

ackBlin SecondP CSFAL 01033 / Fallback Indicates the medium-priority RAT for handovers. It is
dHoCfg ri LBACK TDLOF to GERAN by default. If this parameter is set to
BLIND D-00103 UTRAN UTRAN, GERAN, or CDMA2000, the medium-
HOCFG 3 CS priority RAT is UTRAN, GERAN, or CDMA2000,
LST LOFD-0 Fallback respectively. If this parameter is set to NULL, no
CSFAL 01034 / to medium-priority RAT is specified and only the
LBACK TDLOF GERAN highest-priority RAT can be selected for handovers.
BLIND D-00103 CS
HOCFG 4 The value CDMA2000 is invalid in the current
Fallback version. Therefore, avoid setting this parameter to
LOFD-0 to CDMA2000.
01035 / CDMA2
000 GUI Value Range: UTRAN, GERAN, CDMA2000,
TDLOF
1xRTT NULL
D-00103
5 PS Inter- Unit: None
LOFD-0 RAT Actual Value Range: UTRAN, GERAN, CDMA2000,
01019 / Mobility NULL
TDLOF between Default Value: GERAN
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-00105 GERAN
2 PS Inter-
TDLOF RAT
D-00105 Mobility
3 between
E-
TDLOF
UTRAN
D-00109
and
0
CDMA2
TDLOF 000
D-00104
Flash
3
CS
TDLOF Fallback
D-00107 to
2 UTRAN
TDLOF Flash
D-00104 CS
6 Fallback

eRAN

nd
TDLOF to
D-00107 GERAN
3 Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN

eRAN

nd

ackBlin LowestP CSFAL 01033 / Fallback Indicates the lowest-priority RAT for handovers. It is
dHoCfg ri LBACK TDLOF to CDMA2000 by default. If this parameter is set to
BLIND D-00103 UTRAN UTRAN, GERAN, or CDMA2000, the lowest-priority
HOCFG 3 CS RAT is UTRAN, GERAN, or CDMA2000,
LST LOFD-0 Fallback respectively. If this parameter is set to NULL, no
CSFAL 01034 / to lowest-priority RAT is specified and only the highest-
LBACK TDLOF GERAN or medium-priority RAT can be selected for
BLIND D-00103 CS handovers.
HOCFG 4 Fallback The value CDMA2000 is invalid in the current
LOFD-0 to version. Therefore, avoid setting this parameter to
01035 / CDMA2 CDMA2000.
TDLOF 000
1xRTT GUI Value Range: UTRAN, GERAN, CDMA2000,
D-00103
NULL
5 PS Inter-
RAT Unit: None
LOFD-0
01019 / Mobility Actual Value Range: UTRAN, GERAN, CDMA2000,
TDLOF between NULL
D-00101 E- Default Value: CDMA2000
9 UTRAN
and
LOFD-0 UTRAN
01020 /
TDLOF PS Inter-
D-00102 RAT
0 Mobility
between
LOFD-0 E-
01021 UTRAN
TDLOF and
D-00105 GERAN
2 PS Inter-
TDLOF RAT
D-00105 Mobility
3 between
E-
TDLOF
UTRAN
D-00109
and
0
CDMA2
TDLOF 000
D-00104
Flash
3
CS
TDLOF Fallback
D-00107 to
2 UTRAN
TDLOF Flash
D-00104 CS
6 Fallback

eRAN

nd
TDLOF to
D-00107 GERAN
3 Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
Service
based
Inter-
RAT
handove
r to
GERAN
Distance
based
Inter-
RAT
handove
r to
GERAN

eRAN

nd
UtranNF CsPsMi ADD LOFD-0 CS Meaning: Indicates the priority for the neighboring
req xedPrior UTRAN 01088 / Fallback UTRAN frequency to carry CS+PS combined
ity NFREQ TDLOF Steering services. In measurement-based CSFB to UTRAN, if
MOD D-00108 to UtranCsfbSteeringSwitch and UtranFreqLayerMeasS-
UTRAN 8 UTRAN witch are turned on, the eNodeB determines the
NFREQ LOFD-0 PS Inter- UTRAN frequency to be delivered to a UE in
01019 / RAT RRC_CONNECTED mode based on the priority
LST specified by this parameter. The eNodeB
UTRAN TDLOF Mobility
D-00101 between preferentially delivers the UTRAN frequency with the
NFREQ highest CS+PS combined service priority to the UE.
9 E-
UTRAN In blind CSFB to UTRAN, if UtranCsfbSteeringS-
TDLOF witch and UtranFreqLayerBlindSwitch are turned on,
D-00103 and
UTRAN the target cell is selected based on the priority
3 specified by this parameter. The cell on the UTRAN
TDLOF CS frequency with the highest priority is preferentially
D-00105 Fallback selected. If this parameter is set to Priority_0, the
2 to UTRAN frequency is not included in priority
UTRAN arrangement for neighboring UTRAN frequencies to
TDLOF
D-00107 Flash carry CS+PS combined services.
8 CS GUI Value Range: Priority_0(Priority 0),
Fallback Priority_1(Priority 1), Priority_2(Priority 2),
E- Priority_7(Priority 7), Priority_8(Priority 8),
CS/PS Priority_15(Priority 15), Priority_16(Priority 16)
steering Unit: None
Actual Value Range: Priority_0, Priority_1,
Priority_14, Priority_15, Priority_16
Default Value: Priority_2(Priority 2)

eRAN

nd
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the CSFB policy for a UE in
ackPolic PolicyCf CSFAL 01033 / Fallback connected mode. If the CSFB steering function is
yCfg g LBACK TDLOF to disabled, this parameter also applies to UEs in idle
POLIC D-00103 UTRAN mode. The policy can be PS handover, CCO, or
YCFG 3 CS redirection.
LST LOFD-0 Fallback GUI Value Range: REDIRECTION, CCO_HO,
CSFAL 01034 / to PS_HO
LBACK TDLOF GERAN Unit: None
POLIC D-00103 CS
YCFG 4 Actual Value Range: REDIRECTION, CCO_HO,
Fallback PS_HO
LOFD-0 Steering
01088 / to Default Value: REDIRECTION:On, CCO_HO:On,
TDLOF UTRAN PS_HO:On
D-00108 CS
8 Fallback
LOFD-0 Steering
01089 / to
TDLOF GERAN
D-00108
9
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the RSCP threshold for event B1,
ackHo UtranB1 CSFAL 01033 / Fallback which is used in CS fallback to UTRAN. When CS
ThdRsc LBACK TDLOF to fallback to UTRAN is applicable, this parameter is set
p HO D-00103 UTRAN for UEs and used in the evaluation about whether to
LST 3 trigger event B1. This parameter indicates the RSCP
CSFAL requirement for the UTRAN cells to be included in the
LBACK measurement report. A UE sends a measurement
HO report related to event B1 to the eNodeB when the
RSCP in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For
details, see 3GPP TS 36.331.
GUI Value Range: -120~-25
Unit: dBm
Actual Value Range: -120~-25
Default Value: -106

eRAN

nd
InterRat InterRat MOD LOFD-0 PS Inter- Meaning:

HoCom HoUtran INTER 01019 / RAT Indicates the quantity to be measured for handovers to
m B1Meas RATHO TDLOF Mobility UTRAN. For details, see 3GPP TS 36.331. This
Quan COMM D-00101 between parameter is dedicated to UTRAN FDD. The RSCP
LST 9 E- values are relatively stable, while the ECN0 values
INTER LOFD-0 UTRAN may vary with the network load. The value BOTH
RATHO 01022 / and applies only to UEs complying with 3GPP Release 10.
COMM TDLOF UTRAN For UEs complying with 3GPP Release 8 or 9, the
D-00102 SRVCC value BOTH takes the same effect as the value RSCP.
2 to In QoE-based handovers, this parameter does not
LOFD-0 UTRAN apply to UEs complying with 3GPP Release 8 or 9
01033 / CS and the measurement quantity is fixed to ECN0 for
TDLOF Fallback such UEs.
D-00103 to If this parameter is set to RSCP, the eNodeB delivers
3 UTRAN RSCP-based UTRAN measurement configurations to
UEs. If this parameter is set to ECN0, the eNodeB
delivers ECN0-based UTRAN measurement
configurations to UEs. If this parameter is set to
BOTH, the eNodeB delivers both RSCP- and ECN0-
based UTRAN measurement configurations to UEs
complying with 3GPP Release 10.
GUI Value Range: RSCP, ECN0, BOTH
Unit: None
Actual Value Range: RSCP, ECN0, BOTH
Default Value: ECN0
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the Ec/N0 threshold for event B1,
ackHo UtranB1 CSFAL 01033 / Fallback which is used in CS fallback to UTRAN. When CS
ThdEcn LBACK TDLOF to fallback to UTRAN is required, this parameter is set
0 HO D-00103 UTRAN for UEs and used in the evaluation about whether to
LST 3 trigger event B1. This parameter indicates the Ec/N0
CSFAL requirement for the UTRAN cells to be included in the
LBACK measurement report. A UE sends a measurement
HO report related to event B1 to the eNodeB when the
Ec/N0 in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For
a cell with large signal fading variance, set this
parameter to a large value to prevent unnecessary
handovers. For a cell with small signal fading
variance, set this parameter to a small value to ensure
timely handovers. For details, see 3GPP TS 36.331.
GUI Value Range: -48~0
Unit: 0.5dB
Actual Value Range: -24~0
Default Value: -24

eRAN

nd
CSFallB CsfbHo MOD LOFD-0 CS Meaning: Indicates the time-to-trigger for event B1
ackHo UtranTi CSFAL 01033 / Fallback that is used in CS fallback to UTRAN. When CS
meToTri LBACK TDLOF to fallback to UTRAN is applicable, this parameter is set
g HO D-00103 UTRAN for UEs and used in the evaluation of whether to
LST 3 trigger event B1. When detecting that the signal
CSFAL quality in at least one UTRAN cell meets the entering
LBACK condition, the UE does not send a measurement report
HO to the eNodeB immediately. Instead, the UE sends a
report only when the signal quality continuously
meets the entering condition during the time-to-
trigger. This parameter helps decrease the number of
occasionally triggered event reports, the average
number of handovers, and the number of wrong
handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Default Value: 40ms

eRAN

nd
ENodeB HoMode MOD LOFD-0 SRVCC Meaning:

AlgoSwi Switch ENODE 01022 / to Indicates whether to enable or disable different types
tch BALGO TDLOF UTRAN of handovers, based on which the eNodeB determines
SWITC D-00102 SRVCC handover policies.
H 2 to
LST LOFD-0 GERAN UtranVoipCapSwitch: If this switch is on, UTRAN
ENODE 01023 / supports VoIP. If this switch is off, UTRAN does not
CS support VoIP.
BALGO TDLOF Fallback
SWITC D-00102 to Cdma1xRttVoipCapSwitch: If this switch is on,
H 3 UTRAN CDMA2000 1xRTT supports VoIP. If this switch is
LOFD-0 off, CDMA2000 1xRTT does not support VoIP.
CS
01033 /
Fallback UtranPsHoSwitch: If this switch is on, UTRAN
TDLOF
to supports PS handovers. If this switch is off, UTRAN
D-00103
GERAN does not support PS handovers.
3
PS Inter-
LOFD-0 GeranPsHoSwitch: If this switch is on, GERAN
RAT
01034 / supports PS handovers. If this switch is off, GERAN
Mobility
TDLOF does not support PS handovers.
between
D-00103
E- CdmaHrpdNonOptimisedHoSwitch: If this switch is
4
UTRAN on, non-optimized handovers to CDMA2000 HRPD
LOFD-0 and are enabled. If this switch is off, non-optimized
01019 / UTRAN handovers to CDMA2000 HRPD are disabled.
TDLOF
PS Inter-
D-00101 CdmaHrpdOptimisedHoSwitch: If this switch is
RAT
9 turned on, optimized handovers to CDMA2000 HRPD
Mobility
LOFD-0 are enabled. If this switch is off, optimized handovers
between
01020 / to CDMA2000 HRPD are disabled.
E-
TDLOF UTRAN GeranNaccSwitch: This switch does not take effect if
D-00102 and GeranCcoSwitch is off. If this switch is on, the
0 GERAN GERAN supports network assisted cell change
LOFD-0 PS Inter- (NACC). If this switch is off, the GERAN does not
01021 / RAT support NACC.
TDLOF Mobility
D-00102 GeranCcoSwitch: If this switch is on, the GERAN
between
1 supports cell change order (CCO). If this switch is off,
E-
the GERAN does not support CCO.
TDLOF UTRAN
D-00105 and UtranSrvccSwitch: If this switch is on, the UTRAN
2 CDMA2 supports SRVCC. If this switch is off, the UTRAN
TDLOF 000 does not support SRVCC.
D-00108 Flash GeranSrvccSwitch: If this switch is on, the GERAN
8 CS supports SRVCC. If this switch is off, the GERAN
TDLOF Fallback does not support SRVCC.
D-00104 to
3 UTRAN Cdma1xRttSrvccSwitch: If this switch is on, the
CS CDMA2000 1xRTT supports SRVCC. If this switch is
Fallback off, the CDMA2000 1xRTT does not support SRVCC.

eRAN

nd
TDLOF Steering UtranRedirectSwitch: If this switch is on, redirection

D-00107 to to UTRAN is enabled. If this switch is turned off,
2 UTRAN redirection to UTRAN is disabled.
TDLOF Service GeranRedirectSwitch: If this switch is on, redirection
D-00104 based to GERAN is enabled. If this switch is off, redirection
6 Inter- to GERAN is disabled.
TDLOF RAT
D-00107 handove CdmaHrpdRedirectSwitch: If this switch is on,
3 r to redirection to CDMA2000 HRPD is enabled. If this
UTRAN switch is off, redirection to CDMA2000 HRPD is
Distance disabled.
based Cdma1xRttRedirectSwitch: If this switch is on,
Inter- redirection to CDMA2000 1xRTT is enabled. If this
RAT switch is off, redirection to CDMA2000 1xRTT is
handove disabled.
r to
UTRAN BlindHoSwitch: If this switch is on, blind handovers
for CSFB are enabled. If this switch is off, blind
Service
handovers for CSFB are disabled. If both this option
based
and the BlindHoSwitch option of the Handover Mode
Inter-
switch parameter of the CellHoParaCfg MO are
RAT
selected, blind CSFB handovers for CSFB are
handove
enabled.
r to
GERAN LcsSrvccSwitch: If this switch is on, an SRVCC
Distance procedure is triggered when a UE receives a CSFB
based instruction during a VoIP service. If this switch is off,
Inter- an SRVCC procedure is not triggered when a UE
RAT receives a CSFB instruction during a VoIP service.
handove
AutoGapSwitch: If this switch is on and UEs support
r to
automatic measurement gap configurations on the
GERAN
target frequency, the eNodeB does not deliver gap
configurations to UEs. If this switch is off, the
eNodeB delivers gap configurations to UEs during all
inter-frequency and inter-RAT measurements.
UeVoipOnHspaCapSwitch: If this switch is on and the
eNodeB attempts to hand over UEs using voice
services to UTRAN, the eNodeB checks UE
capabilities when determining whether PS handover is
applied. UEs must support voiceOverPS-HS-UTRA-
FDD-r9 if the target UTRAN cell works in FDD mode
or voiceOverPS-HS-UTRA-TDD128-r9 if the target
UTRAN cell works in TDD mode. If this switch is off,
the eNodeB does not check UE capabilities when
handing over UEs to UTRAN based on PS handovers.
UtranFddB1CapSwitch: If this switch is on, the
setting of bit 41 of FGI specifying the UE capability

eRAN

nd
of event B1 measurement on FDD UTRAN cells must

be considered. If this switch is off, the setting of bit 41
of FGI does not need to be considered.
CdmaHrpdNonOptMeaHoSwitch: If this switch is on,

measurement-based non-optimized handovers to
CDMA2000 HRPD are enabled. If this switch is off,
measurement-based non-optimized handovers to
CDMA2000 HRPD are disabled.
GUI Value Range:
EutranVoipCapSwitch(EutranVoipCapSwitch),
UtranVoipCapSwitch(UtranVoipCapSwitch),
GeranVoipCapSwitch(GeranVoipCapSwitch),
Cdma1xRttVoipCapSwitch(Cdma1xRttVoipCapSwitc
h), UtranPsHoSwitch(UtranPsHoSwitch),
GeranPsHoSwitch(GeranPsHoSwitch),
CdmaHrpdNonOptimisedHoS-
witch(CdmaHrpdNonOptimisedHoSwitch),
CdmaHrpdOptimisedHoSwitch(CdmaHrpdOptimised-
HoSwitch), GeranNaccSwitch(GeranNaccSwitch),
GeranCcoSwitch(GeranCcoSwitch),
UtranSrvccSwitch(UtranSrvccSwitch),
GeranSrvccSwitch(GeranSrvccSwitch),
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: EutranVoipCapSwitch,
UtranVoipCapSwitch, GeranVoipCapSwitch,
Cdma1xRttVoipCapSwitch, UtranPsHoSwitch,
GeranPsHoSwitch, CdmaHrpdNonOptimisedHoS-
witch, CdmaHrpdOptimisedHoSwitch,
GeranNaccSwitch, GeranCcoSwitch,
UtranSrvccSwitch, GeranSrvccSwitch,
Cdma1xRttSrvccSwitch, UtranRedirectSwitch,
GeranRedirectSwitch, CdmaHrpdRedirectSwitch,
Cdma1xRttRedirectSwitch, BlindHoSwitch,

eRAN

nd
LcsSrvccSwitch, AutoGapSwitch,
UeVoipOnHspaCapSwitch, UtranFddB1CapSwitch,
CdmaHrpdNonOptMeaHoSwitch
Default Value: EutranVoipCapSwitch:On,
UtranVoipCapSwitch:Off, GeranVoipCapSwitch: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.
GUI Value Range: -140~-43
Unit: dBm
Default Value: -80

eRAN

nd
UtranNF ConnFre ADD LOFD-0 PS Inter- Meaning: Indicates the frequency priority based on
req qPriority UTRAN 01019 / RAT which the eNodeB selects a target frequency for blind
NFREQ TDLOF Mobility redirection or contains a frequency in a measurement
MOD D-00101 between configuration. If a blind redirection is triggered and
UTRAN 9 E- the target neighboring cell is not specified, the
NFREQ TDLBF UTRAN eNodeB selects a target frequency based on this
D-00201 and priority. If a measurement configuration is to be
LST UTRAN delivered, the eNodeB preferentially delivers a
UTRAN 803
Cell frequency with the highest priority. If this priority is
NFREQ TDLOF set to 0 for a frequency, this frequency is not selected
D-00102 Selectio
n and as the target frequency for a blind redirection. A larger
2 value indicates a higher priority.
Re-
TDLOF selection GUI Value Range: 0~8
D-00103
3 SRVCC Unit: None
to Actual Value Range: 0~8
TDLOF UTRAN
D-00105 Default Value: 0
2 CS
Fallback
TDLOF to
D-00104 UTRAN
3
Flash
TDLOF CS
D-00107 Fallback
2 to
TDLOF UTRAN
D-00107 Service
8 based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
steering

eRAN

nd
ENodeB NCellRa MOD LOFD-0 Inter- Meaning: Indicates whether to enable neighboring cell
AlgoSwi nkingSw ENODE 02002/ RAT ranking. This parameter consists of the following
tch itch BALGO TDLOF ANR switches: GERAN_SWITCH: Indicates whether the
SWITC D-00200 SRVCC eNodeB prioritizes measurement priorities of
H 2 to neighboring GERAN cells based on the number of
LST LOFD-0 UTRAN each neighboring GERAN cell is measured within a
ENODE 01022/ period of time. The eNodeB prioritizes measurement
CS priorities only when this switch is on.
BALGO TDLOF Fallback
SWITC D-00102 UTRAN_SWITCH: Indicates whether the eNodeB
to prioritizes measurement priorities of neighboring
H 2 UTRAN UTRAN cells based on the number of each
LOFD-0 Flash neighboring UTRAN cell is measured within a period
01033/ CS of time. The eNodeB prioritizes measurement
TDLOF Fallback priorities of neighboring UTRAN cells based on the
D-00103 to number of each neighboring UTRAN cell is measured
3 UTRAN within a period of time only when this switch is on.
LOFD-0 Flash GUI Value Range: GERAN_SWITCH(GREAN
01052/ CS Neighboring Cell Ranking Switch),
TDLOF Fallback UTRAN_SWITCH(UTRAN Neighboring Cell
D-00105 to Ranking Switch)
2 GERAN Unit: None
LOFD-0 PS Inter-
01053/ Actual Value Range: GERAN_SWITCH,
RAT UTRAN_SWITCH
TDLOF Mobility
D-00105 between Default Value: GERAN_SWITCH:Off,
3 E- UTRAN_SWITCH:Off
LOFD-0 UTRAN
01019/ and
TDLOF UTRAN
D-00101 Service
9 based
LOFD-0 inter-
01043/ RAT
TDLOF handove
D-00104 r to
3 UTRAN
LOFD-0 Distance
01072/ based
TDLOF inter-
D-00107 RAT
2 handove
r to
UTRAN

eRAN

nd
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
LST D-00200 SRVCC periodically and automatically arranged based on the
UTRAN 2 to number of times that each neighboring UTRAN cell is
NCELL LOFD-0 UTRAN measured. The neighboring UTRAN cells for UTRAN
01022/ measurement control, UTRAN flash blind
CS redirections, and UTRAN flash-CSFB-based
TDLOF Fallback
D-00102 redirections can be selected based on the measurement
to priorities of neighboring UTRAN cells.
2 UTRAN
LOFD-0 GUI Value Range: 0~128
Flash
01033/ CS Unit: None
TDLOF Fallback Actual Value Range: 0~128
D-00103 to
3 Default Value: 0
UTRAN
LOFD-0 PS Inter-
01052/ RAT
TDLOF Mobility
D-00105 between
2 E-
LOFD-0 UTRAN
01019/ and
TDLOF UTRAN
D-00101 Service
9 based
LOFD-0 inter-
01043/ RAT
TDLOF handove
D-00104 r to
3 UTRAN
LOFD-0 Distance
01072/ based
TDLOF inter-
D-00107 RAT
2 handove
r to
UTRAN

eRAN

nd
UtranN CellMea ADD LOFD-0 PS Inter- Meaning: Indicates the priority of measurement on the
Cell sPriority UTRAN 01019 RAT neighboring UTRAN cell. The eNodeB preferentially
NCELL TDLOF Mobility contains the information about a neighboring cell with
MOD D-00102 between this priority set to HIGH_PRIORITY while delivering
UTRAN 2 E- a measurement configuration.
NCELL UTRAN GUI Value Range: LOW_PRIORITY(Low Priority),
TDLOF and
LST D-00103 HIGH_PRIORITY(High Priority)
UTRAN
UTRAN 3 Unit: None
NCELL SRVCC
TDLOF Actual Value Range: LOW_PRIORITY,
to
D-00105 HIGH_PRIORITY
UTRAN
2 Default Value: LOW_PRIORITY(Low Priority)
CS
TDLOF
Fallback
D-00101
to
9
UTRAN
TDLOF
D-00104 Flash
3 CS
Fallback
TDLOF to
D-00107 UTRAN
2
PS Inter-
TDLOF RAT
D-00107 Mobility
8 between
E-
UTRAN
and
UTRAN
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN

eRAN

nd
CS/PS
steering
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.
OLCFG 9 E- GUI Value Range: 1~16
LST LOFD-0 UTRAN
and Unit: None
CELLU 01022 /
EMEAS TDLOF UTRAN Actual Value Range: 1~16
CONTR D-00102 SRVCC Default Value: 3
OLCFG 2 to
LOFD-0 UTRAN
01043 / Service
TDLOF based
D-00104 Inter-
3 RAT
LOFD-0 handove
01072 / r to
TDLOF UTRAN
D-00107 Distance
2 based
LOFD-0 Inter-
01033 / RAT
TDLOF handove
D-00103 r to
3 UTRAN
CS
Fallback
to
UTRAN

eRAN

nd
UtranN BlindHo ADD LOFD-0 PS Inter- Meaning: Indicates the priority of the neighboring cell
Cell Priority UTRAN 01019 RAT during blind handovers. Blind handover is a process in
NCELL TDLOF Mobility which the eNodeB instructs a UE to hand over to a
MOD D-00102 between specified neighboring cell. There are 32 priorities
UTRAN 2 E- altogether. The priority has a positive correlation with
NCELL UTRAN the value of this parameter. Note that the value 0
TDLOF and indicates that blind handovers to the neighboring cell
LST D-00103 UTRAN are not allowed.
UTRAN 3
NCELL SRVCC GUI Value Range: 0~32
TDLOF
to Unit: None
D-00105
UTRAN
2 Actual Value Range: 0~32
CS
TDLOF Default Value: 0
Fallback
D-00101
to
9
UTRAN
TDLOF
D-00104 Flash
3 CS
Fallback
TDLOF to
D-00107 UTRAN
2
PS Inter-
TDLOF RAT
D-00107 Mobility
8 between
E-
UTRAN
and
UTRAN
Service
based
Inter-
RAT
handove
r to
UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN

eRAN

nd
CS/PS
steering
InterRat CellInfo MOD LOFD-0 PS Inter- Meaning: Indicates the maximum number of UTRAN
HoCom MaxUtr INTER 01019 / RAT cell system information messages that can be
m anCellN RATHO TDLOF Mobility transmitted during a flash redirection procedure.
um COMM D-00101 between GUI Value Range: 1~16
LST 9 E-
UTRAN Unit: None
INTER TDLOF
RATHO D-00105 and Actual Value Range: 1~16
COMM 2 UTRAN Default Value: 8
Flash
CS
Fallback
to
UTRAN
CSFallB CsfbProt MOD LOFD-0 CS Meaning: Indicates the timer governing the period in
ackHo ectionTi CSFAL 01033 / Fallback which only CSFB can be performed . After the timer
mer LBACK TDLOF to expires, the eNodeB performs a blind redirection for
HO D-00103 UTRAN the UE.
LST 3 CS GUI Value Range: 1~10
CSFAL LOFD-0 Fallback Unit: s
LBACK 01033 / to
HO TDLOF GERAN Actual Value Range: 1~10
D-00103 Enhance Default Value: 4
4 d CS
LOFD-0 Fallback
01033 / to
TDLOF CDMA2
D-00109 000
0 1xRTT
InterRat UtranCe MOD LOFD-0 CS Meaning: Indicates the maximum number of UTRAN
HoCom llNumF INTER 01033 / Fallback cell system information messages that can be
m orEmcR RATHO TDLOF to transmitted during a CSFB emergency redirection
edirect COMM D-00103 UTRAN procedure.
LST 3 Flash GUI Value Range: 0~16
INTER TDLOF CS Unit: None
RATHO D-00105 Fallback
COMM 2 to Actual Value Range: 0~16
UTRAN Default Value: 0

eRAN

nd
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 a switch used to
LST 01033 Steering
ENODE to control whether operators can adopt different mobility
BALGO LOFD-0 UTRAN policies on their UTRANs. If this switch is on,
SWITC 01052 operators can adopt different policies (for example, PS
CS handover capability and RIM-based system
H LOFD-0
Fallback information reading capability) on their UTRANs. If
01068
to this switch is off, operators cannot adopt different
LOFD-0 UTRAN policies on their UTRANs.
01088
Flash GUI Value Range: UtranSepOpMobility-
LOFD-0 CS Switch(UtranSepOpMobilitySwitch)
01019 Fallback
Unit: None
LOFD-0 to
01043 UTRAN Actual Value Range: UtranSepOpMobilitySwitch
LOFD-0 CS Default Value: UtranSepOpMobilitySwitch:Off
01072 Fallback
LOFD-0 with
01078 LAI to
UTRAN
CS
Fallback
Steering
to
UTRAN
PS Inter-
RAT
Mobility
between
E-
UTRAN
and
UTRAN
Service
based
inter-
RAT
Distance
based
Inter-
RAT
handove
r to
UTRAN

eRAN

nd
E-
UTRAN
to
UTRAN
CS/PS
Steering

eRAN

nd
UtranNe Network ADD LOFD-0 SRVCC Meaning:

tworkCa CapCfg UTRAN 01022 / to Indicates the UTRAN capabilities for an operator
pCfg NETW TDLOF UTRAN including PS handover capability, capability of
ORKCA D-00102 CS obtaining system information (SI) of the UTRAN
PCFG 2 Fallback through RAN Information Management (RIM)
MOD LOFD-0 to procedures, VoIP capability, and ultra-flash CSFB
UTRAN 01033 / UTRAN capability. If the MME, SGSN, or RNC of the
NETW TDLOF Flash operator does not support PS handovers, RIM
ORKCA D-00103 CS procedures, VoIP, or ultra-flash CSFB, set this
PCFG 3 Fallback parameter to indicate the incapabilities. If this
LST LOFD-0 to parameter is not set, UTRAN capabilities are
UTRAN 01052 / UTRAN supported by default.
NETW TDLOF PsHoCapCfg: This option indicates whether PS
CS
ORKCA D-00105 handovers are supported. If this option is selected, the
Fallback
PCFG 2 UTRAN supports PS handovers. If this option is
with
LOFD-0 LAI to deselected, the UTRAN does not support PS
01068 / UTRAN handovers.
TDLOF
CS SiByRimCapCfg: This option indicates whether the
D-00106
Fallback capability of obtaining SI of the UTRAN through
8
Steering RIM procedures is supported. If the option is selected,
LOFD-0 to obtaining SI of the UTRAN through RIM procedures
01088 / UTRAN is supported. If the option is deselected, obtaining SI
TDLOF of the UTRAN through RIM procedures is not
PS Inter-
D-00108 supported.
RAT
8
Mobility
LOFD-0 VoipCapCfg: This option indicates the VoIP capability
between
01019 / of the UTRAN. If this option is selected, the VoIP is
E-
TDLOF supported. VoIP services established in the LTE
UTRAN
D-00101 network can be transferred to the UTRAN using PS
and
9 handovers so that UEs can perform voice services in
UTRAN
the UTRAN. If this option is deselected, the UTRAN
LOFD-0 Service does not support VoIP. Voice services established in
01043 / based the LTE network cannot be transferred to the UTRAN
TDLOF inter- using PS handovers.
D-00104 RAT
3 handove UltraFlashCsfbCapCfg: This option indicates the
LOFD-0 r to SRVCC capability. If this option is selected, SRVCC
01072 / UTRAN is supported and voice services can continue in the
TDLOF UTRAN by SRVCC. If this option is deselected,
Distance SRVCC is not supported.
D-00107 based
2 Inter- GUI Value Range: PsHoCapCfg(PsHoCapCfg),
LOFD-0 RAT SiByRimCapCfg(SiByRimCapCfg),
81283 / handove VoipCapCfg(VoipCapCfg),
TDLOF r to UltraFlashCsfbCapCfg(UltraFlashCsfbCapCfg)
D-08120 UTRAN Unit: None
3 Ultra- Actual Value Range: PsHoCapCfg, SiByRimCapCfg,
Flash VoipCapCfg, UltraFlashCsfbCapCfg

eRAN

nd
LOFD-0 CSFB to Default Value: PsHoCapCfg:Off,

70202 / GERAN SiByRimCapCfg:Off, VoipCapCfg:On,
TDLOF Ultra- UltraFlashCsfbCapCfg:Off
D-08122 Flash
3 CSFB to
UTRAN
CSFallB CsfbUse MOD LBFD-0 Admissi Meaning: Indicates whether allocation/retention

ackPolic rArpCfg CSFAL 02023 / on priorities (ARPs) can be configured for CSFB services
yCfg Switch LBACK TDLBF Control triggered by common calls. For details about ARPs,
POLIC D-00202 see 3GPP TS 23.401.
YCFG 3 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
LBACK Actual Value Range: OFF, ON
POLIC Default Value: OFF(Off)
YCFG
CSFallB Normal MOD LBFD-0 Admissi Meaning: Indicates the allocation/retention priority
ackPolic CsfbUse CSFAL 02023 / on (ARP) of a CSFB service triggered by a common call.
yCfg rArp LBACK TDLBF Control When this parameter is set to 1, the service priority is
POLIC D-00202 the same as that of an emergency call. For details
YCFG 3 about the ARP, see 3GPP TS 23.401.
LST GUI Value Range: 1~15
CSFAL Unit: None
LBACK
POLIC Actual Value Range: 1~15
YCFG Default Value: 2
GlobalP UtranLo MOD None None Meaning: Indicates the UMTS load transmission
rocSwitc adTrans GLOBA channel. The eNodeB sends RAN-INFORMATION-
h Chan LPROC REQUEST PDUs to UTRAN cells to request multiple
SWITC reports on the load status of UTRAN cells only when
H the parameter is set to BASED_ON_RIM.The
LST function specified by the parameter value
GLOBA BASED_ON_ECO is temporarily unavailable.
LPROC GUI Value Range: NULL, BASED_ON_RIM,
SWITC BASED_ON_ECO
H Unit: None
Actual Value Range: NULL, BASED_ON_RIM,
BASED_ON_ECO
Default Value: NULL

eRAN

nd
ENodeB RimOnE MOD MRFD- eCoordi Meaning: Indicates whether the RAN information
AlgoSwi coSwitc ENODE 090211 nator management (RIM) procedure is initiated by the
tch h BALGO LOFD-0 based eCoordinator. If this parameter is set to ON, the RIM
SWITC 01052/ RIM procedure is initiated by the eCoordinator. If this
H TDLOF process parameter is set to OFF, the RIM procedure is initiated
LST D-00105 optimiza by the core network.
ENODE 2 tion GUI Value Range: OFF(Off), ON(On)
BALGO LOFD-0 Flash Unit: None
SWITC 01019/ CS
H Fallback Actual Value Range: OFF, ON
TDLOF
D-00101 to Default Value: OFF(Off)
9 UTRAN
LOFD-0 PS Inter-
01044/ RAT
TDLOF Mobility
D-00104 between
4 E-
UTRAN
LOFD-0 and
01033/ UTRAN
TDLOF
D-00103 Inter-
3 RAT
Load
Sharing
to
UTRA
N(based
on
UMTS
cell load
informat
ion)
CS
Fallback
to
UTRAN
(based
on
UMTS
cell load
informat
ion)

eRAN

nd
ENodeB RimSwit MOD LOFD-0 CS Meaning: Indicates the collective switch for the RAN
AlgoSwi ch ENODE 01034 / Fallback information management (RIM) function.
tch BALGO TDLOF to UTRAN_RIM_SWITCH: Indicates the switch used to
SWITC D-00103 GERAN enable or disable the RIM procedure that requests
H 4 Flash event-driven multiple reports from UTRAN cells. If
LST LOFD-0 CS this switch is on, the eNodeB can send RAN-
ENODE 01052 / Fallback INFORMATION-REQUEST protocol data units
BALGO TDLOF to (PDUs) to UTRAN cells to request multiple event-
SWITC D-00105 UTRAN driven reports. If this switch is off, the eNodeB cannot
H 2 send RAN-INFORMATION-REQUEST PDUs to
Flash UTRAN cells to request multiple event-driven reports.
LOFD-0 CS GERAN_RIM_SWITCH: Indicates the switch used to
01053 / Fallback enable or disable the RIM procedure that requests
TDLOF to event-driven multiple reports from GERAN cells. If
D-00105 GERAN this switch is on, the eNodeB can send RAN-
3 INFORMATION-REQUEST PDUs to CERAN cells
to request multiple event-driven reports. If this switch
is off, the eNodeB cannot send RAN-
INFORMATION-REQUEST PDUs to GERAN cells
to request multiple event-driven reports.
GUI Value Range: UTRAN_RIM_SWITCH(UTRAN
RIM Switch), GERAN_RIM_SWITCH(GERAN RIM
Switch)
Unit: None
Actual Value Range: UTRAN_RIM_SWITCH,
GERAN_RIM_SWITCH
Default Value: UTRAN_RIM_SWITCH:Off,
GERAN_RIM_SWITCH:Off
InterRat CellInfo MOD LOFD-0 PS Inter- Meaning: Indicates the maximum number of GERAN
HoCom MaxGer INTER 01020 / RAT cell system information messages that can be
m anCellN RATHO TDLOF Mobility transmitted during a flash redirection procedure.
um COMM D-00102 between GUI Value Range: 1~32
LST 0 E-
UTRAN Unit: None
INTER TDLOF
RATHO D-00105 and Actual Value Range: 1~32
COMM 3 GERAN Default Value: 8
Flash
CS
Fallback
to
GERAN

eRAN

nd
GeranNf ConnFre ADD LOFD-0 PS Inter- Meaning: Indicates the frequency group priority based
reqGrou qPriority GERAN 01020 / RAT on which the eNodeB selects a target frequency group
p NFREQ TDLOF Mobility for blind redirection or delivers a frequency group in
GROUP D-00102 between measurement configuration messages. If a blind
MOD 0 E- redirection is triggered and the target neighboring cell
GERAN TDLOF UTRAN is not specified, the eNodeB selects a target frequency
NFREQ D-00102 and group based on the setting of this parameter. If a
GROUP 3 GERAN measurement configuration is to be delivered, the
SRVCC eNodeB preferentially delivers the frequency group
LST TDLOF with the highest priority. If this parameter is set to 0
GERAN D-00103 to
GERAN for a frequency group, this frequency group is not
NFREQ 4 selected as the target frequency group for a blind
GROUP TDLOF CS redirection. A larger value indicates a higher priority.
D-00105 Fallback
to GUI Value Range: 0~8
3
GERAN Unit: None
Flash Actual Value Range: 0~8
CS Default Value: 0
Fallback
to
GERAN
GeranN BlindHo ADD LOFD-0 PS Inter- Meaning: Indicates the priority of the neighboring cell
cell Priority GERAN 01020 / RAT during blind handovers. Blind handover is a process in
NCELL TDLOF Mobility which the eNodeB instructs a UE to hand over to a
MOD D-00102 between specified neighboring cell. There are 32 priorities
GERAN 0 E- altogether. The priority has a positive correlation with
NCELL TDLOF UTRAN the value of this parameter. Note that the value 0
D-00102 and indicates that blind handovers to the neighboring cell
LST GERAN are not allowed.
GERAN 3
NCELL TDLOF SRVCC GUI Value Range: 0~32
D-00103 to Unit: None
4 GERAN
Actual Value Range: 0~32
TDLOF CS
Fallback Default Value: 0
D-00105
3 to
GERAN
Flash
CS
Fallback
to
GERAN

eRAN

nd
UtranEx Rac ADD LOFD-0 PS Inter- Meaning: Indicates the routing area code.
ternalCe UTRAN 01019 / RAT GUI Value Range: 0~255
ll EXTER TDLOF Mobility
NALCE D-00101 between Unit: None
LL 9 E- Actual Value Range: 0~255
MOD LOFD-0 UTRAN Default Value: 0
UTRAN 01034 / and
EXTER TDLOF UTRAN
NALCE D-00103 CS
LL 4 Fallback
LST LOFD-0 to
UTRAN 01052 / GERAN
EXTER TDLOF Flash
NALCE D-00105 CS
LL 2 Fallback
TDLOF to
D-00103 UTRAN
3 CS
TDLOF Fallback
D-00104 to
3 UTRAN
TDLOF Service
D-00107 based
2 Inter-
RAT
TDLOF handove
D-00107 r to
8 UTRAN
Distance
based
Inter-
RAT
handove
r to
UTRAN
E-
UTRAN
to
UTRAN
CS/PS
steering

eRAN

nd
CSFallB CnOper LST LOFD-0 CS Meaning: Indicates the index of the operator.
ackBlin atorId CSFAL 01033 / Fallback GUI Value Range: 0~5
dHoCfg LBACK TDLOF to
BLIND D-00103 UTRAN Unit: None
HOCFG 3 CS Actual Value Range: 0~5
MOD LOFD-0 Fallback Default Value: None
CSFAL 01034 / to
LBACK TDLOF GERAN
BLIND D-00103 Flash
HOCFG 4 CS
TDLOF Fallback
D-00105 to
2 UTRAN
TDLOF Flash
D-00105 CS
3 Fallback
TDLOF to
D-00103 GERAN
5 CS
TDLOF Fallback
D-00109 to
0 CDMA2
000
1xRTT
Enhance
d CS
Fallback
to
CDMA2
000
1xRTT
CSFallB UtranLc MOD LOFD-0 CS Meaning: Indicates the LCS capability of the
ackBlin sCap CSFAL 01033 / Fallback UTRAN. If this parameter is set to ON, the UTRAN
dHoCfg LBACK TDLOF to supports LCS. If this parameter is set to OFF, the
BLIND D-00103 UTRAN UTRAN does not support LCS.
HOCFG 3 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
BLIND Default Value: OFF(Off)
HOCFG

eRAN

nd
CSFallB LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
ackHo llId CSFAL identifies a cell within a BS.
LBACK GUI Value Range: 0~255
HO
Unit: None
MOD
CSFAL Actual Value Range: 0~255
LBACK Default Value: None
HO
S1Interf MmeRel ADD LBFD-0 Star Meaning: Indicates the compliance protocol release of
ace ease S1INTE 0300101 Topolog the MME to which the eNodeB is connected through
RFACE / y the S1 interface. The eNodeB sends S1 messages
MOD TDLBF Chain complying with the protocol release specified by this
S1INTE D-00300 Topolog parameter. The value of this parameter must be the
RFACE 101 y same as the MME-complied protocol release. If the
LBFD-0 parameter value is different from the MME-complied
DSP Tree protocol release, the way in which the MME handles
S1INTE 0300102 Topolog
/ these message is subject to the MME implementation.
RFACE y
TDLBF GUI Value Range: Release_R8(Release 8),
D-00300 3GPP Release_R9(Release 9), Release_R10(Release 10),
102 R11 Release_R11(Release 11)
Specific
LBFD-0 ations Unit: None
0300103 Actual Value Range: Release_R8, Release_R9,
/ Release_R10, Release_R11
TDLBF
D-00300 Default Value: Release_R8(Release 8)
103
LBFD-0
01008 /
TDLBF
D-07011
1

eRAN

nd
GeranEx Rac ADD LOFD-0 CS Meaning: Indicates the routing area code.
ternalCe GERAN 01034 / Fallback GUI Value Range: 0~255
ll EXTER LOFD-0 to
NALCE 01034 GERAN Unit: None
LL LOFD-0 Flash Actual Value Range: 0~255
MOD 01053 CS Default Value: 0
GERAN LOFD-0 Fallback
EXTER 01020 / to
NALCE TDLOF GERAN
LL D-00102 PS Inter-
LST 0 RAT
GERAN Mobility
EXTER between
NALCE E-
LL UTRAN
and
GERAN
CSFallB GeranLc MOD LOFD-0 CS Meaning: Indicates the LCS capability of the
ackBlin sCap CSFAL 01034 / Fallback GERAN. If this parameter is set to ON, the GERAN
dHoCfg LBACK TDLOF to supports LCS. If this parameter is set to OFF, the
BLIND D-00103 GERAN GERAN does not support LCS.
HOCFG 4 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
BLIND Default Value: OFF(Off)
HOCFG
InterRat GeranCe MOD LOFD-0 CS Meaning: Indicates the maximum number of GERAN
HoCom llNumF INTER 01034 / Fallback cell system information messages that can be
m orEmcR RATHO TDLOF to transmitted during a CSFB emergency redirection
edirect COMM D-00103 GERAN procedure.
LST 4 GUI Value Range: 0~32
INTER Unit: None
RATHO
COMM Actual Value Range: 0~32
Default Value: 0

eRAN

nd
CSFallB CsfbHo MOD LOFD-0 CS Fall Meaning: Indicates the RSSI threshold for event B1
ackHo GeranB CSFAL 01034 / Back to that is used in CS fallback to GERAN. A UE sends a
1Thd LBACK TDLOF GERAN measurement report related to event B1 to the eNodeB
HO D-00103 when the RSSI in at least one GERAN cell exceeds
LST 4 this threshold and other triggering conditions are met.
CSFAL For details, see 3GPP TS 36.331.
LBACK GUI Value Range: -110~-48
HO Unit: dBm
Default Value: -103
CSFallB CsfbHo MOD LOFD-0 CS Fall Meaning: Indicates the time-to-trigger for event B1
ackHo GeranTi CSFAL 01034 / Back to that is used in CS fallback to GERAN. When CS
meToTri LBACK TDLOF GERAN fallback to GERAN is applicable, this parameter is set
g HO D-00103 for UEs and used in the evaluation of whether to
LST 4 trigger event B1. When detecting that the signal
CSFAL quality in at least one GERAN cell meets the entering
LBACK condition, the UE does not send a measurement report
HO to the eNodeB immediately. Instead, the UE sends a
report only when the signal quality continuously
meets the entering condition during the time-to-
trigger. This parameter helps decrease the number of
occasionally triggered event reports, the average
number of handovers, and the number of wrong
handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.
GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Unit: ms
Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Default Value: 40ms

eRAN

nd
CellDrx LongDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the long DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement.
orMeas RXPAR TDLOF CS GUI Value Range: SF128(128 subframes), SF160(160
A D-08120 Fallback subframes), SF256(256 subframes), SF320(320
LST 3 to subframes), SF512(512 subframes), SF640(640
CELLD GERAN subframes), SF1024(1024 subframes), SF1280(1280
RXPAR subframes), SF2048(2048 subframes), SF2560(2560
A subframes)
Unit: subframe
Actual Value Range: SF128, SF160, SF256, SF320,
SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF160(160 subframes)
CellDrx OnDurT MOD LOFD-0 Ultra- Meaning: Indicates the length of the On Duration
Para imerFor CELLD 81283 / Flash Timer dedicated to GERAN measurement.
Meas RXPAR TDLOF CS GUI Value Range: PSF1(1 PDCCH subframe),
A D-08120 Fallback PSF2(2 PDCCH subframes), PSF3(3 PDCCH
LST 3 to subframes), PSF4(4 PDCCH subframes), PSF5(5
CELLD GERAN PDCCH subframes), PSF6(6 PDCCH subframes),
RXPAR PSF8(8 PDCCH subframes), PSF10(10 PDCCH
A subframes), PSF20(20 PDCCH subframes), PSF30(30
PDCCH subframes), PSF40(40 PDCCH subframes),
PSF50(50 PDCCH subframes), PSF60(60 PDCCH
subframes), PSF80(80 PDCCH subframes),
PSF100(100 PDCCH subframes), PSF200(200
PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200
Default Value: PSF2(2 PDCCH subframes)

eRAN

nd
CellDrx DrxInact MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX Inactivity
Para TimerFo CELLD 81283 / Flash Timer dedicated to GERAN measurement.
rMeas RXPAR TDLOF CS GUI Value Range: PSF1(1 PDCCH subframe),
A D-08120 Fallback PSF2(2 PDCCH subframes), PSF3(3 PDCCH
LST 3 to subframes), PSF4(4 PDCCH subframes), PSF5(5
CELLD GERAN PDCCH subframes), PSF6(6 PDCCH subframes),
RXPAR PSF8(8 PDCCH subframes), PSF10(10 PDCCH
A subframes), PSF20(20 PDCCH subframes), PSF30(30
PDCCH subframes), PSF40(40 PDCCH subframes),
PSF50(50 PDCCH subframes), PSF60(60 PDCCH
PDCCH subframes), PSF300(300 PDCCH
PDCCH subframes), PSF1920(1920 PDCCH
subframes), PSF2560(2560 PDCCH subframes)
Unit: subframe
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200, PSF300, PSF500,
PSF750, PSF1280, PSF1920, PSF2560
CellDrx DrxReT MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX
Para xTimerF CELLD 81283 / Flash Retransmission Timer dedicated to GERAN
orMeas RXPAR TDLOF CS measurement.
A D-08120 Fallback GUI Value Range: PSF1(1 PDCCH subframes),
LST 3 to PSF2(2 PDCCH subframes), PSF4(4 PDCCH
CELLD GERAN subframes), PSF6(6 PDCCH subframes), PSF8(8
RXPAR PDCCH subframes), PSF16(16 PDCCH subframes),
A PSF24(24 PDCCH subframes), PSF33(33 PDCCH
subframes)
Unit: subframe
PSF16, PSF24, PSF33
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates whether to enable the short DRX
Para xSwFor CELLD 81283 / Flash cycle dedicated to GERAN measurement.
Meas RXPAR TDLOF CS GUI Value Range: OFF(Off), ON(On)
A D-08120 Fallback
3 to Unit: None
LST
CELLD GERAN Actual Value Range: OFF, ON
RXPAR Default Value: OFF(Off)
A

eRAN

nd
CellDrx ShortDr MOD LOFD-0 Ultra- Meaning: Indicates the length of the short DRX cycle
Para xCycleF CELLD 81283 / Flash dedicated to GERAN measurement.
orMeas RXPAR TDLOF CS GUI Value Range: SF2(2 subframes), SF5(5
A D-08120 Fallback subframes), SF8(8 subframes), SF10(10 subframes),
LST 3 to SF16(16 subframes), SF20(20 subframes), SF32(32
CELLD GERAN subframes), SF40(40 subframes), SF64(64
RXPAR subframes), SF80(80 subframes), SF128(128
A subframes), SF160(160 subframes), SF256(256
subframes), SF320(320 subframes), SF512(512
subframes), SF640(640 subframes)
Unit: subframe
Actual Value Range: SF2, SF5, SF8, SF10, SF16,
SF20, SF32, SF40, SF64, SF80, SF128, SF160,
SF256, SF320, SF512, SF640
Default Value: SF20(20 subframes)
CellDrx ShortCy MOD LOFD-0 Ultra- Meaning: Indicates the length of the DRX Short Cycle
Para cleTime CELLD 81283 / Flash Timer dedicated to GERAN measurement.
rForMea RXPAR TDLOF CS GUI Value Range: 1~16
s A D-08120 Fallback
3 to Unit: None
LST
CELLD GERAN Actual Value Range: 1~16
RXPAR Default Value: 1
A

eRAN
CS Fallback Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726989 L.IRATHO.E2W.Pr Number of inter- Multi-mode: UL Unified Video

epAttOut RAT handover MRFD-101401 Steering
attempts from E- GSM: None
UTRAN to PS Inter-RAT
WCDMA network UMTS: None Mobility between
LTE: E-UTRAN and
LOFD-001019 UTRAN
LOFD-001022 SRVCC to UTRAN
LOFD-001033 CS Fallback to
TDLOFD-001019 UTRAN
TDLOFD-001022 PS Inter-RAT
Mobility between
TDLOFD-001033 E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526726990 L.IRATHO.E2W.Ex Number of inter- Multi-mode: UL Unified Video

ecAttOut RAT handover MRFD-101401 Steering
executions from E- GSM: None
LTE: E-UTRAN and
LOFD-001019 UTRAN
TDLOFD-001019 UTRAN
Mobility between
UTRAN
SRVCC to UTRAN
CS Fallback to
UTRAN
1526726991 L.IRATHO.E2W.Ex Number of Multi-mode: UL Unified Video

ecSuccOut successful inter- MRFD-101401 Steering
RAT handovers GSM: None
from E-UTRAN to PS Inter-RAT
LTE: E-UTRAN and
LOFD-001019 UTRAN
TDLOFD-001019 UTRAN
Mobility between
UTRAN
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526726992 L.IRATHO.E2G.Pr Number of inter- Multi-mode: None PS Inter-RAT

epAttOut RAT handover GSM: None Mobility between
attempts from E- E-UTRAN and
UTRAN to UMTS: None GERAN
GERAN LTE: SRVCC to GERAN
LOFD-001020
CS Fallback to
LOFD-001023 GERAN
LOFD-001034 PS Inter-RAT
TDLOFD-001020 Mobility between
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN
1526726993 L.IRATHO.E2G.Ex Number of inter- Multi-mode: None PS Inter-RAT

ecAttOut RAT handover GSM: None Mobility between
executions from E- E-UTRAN and
LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN
1526726994 L.IRATHO.E2G.Ex Number of Multi-mode: None PS Inter-RAT

ecSuccOut successful inter- GSM: None Mobility between
RAT handovers E-UTRAN and
from E-UTRAN to UMTS: None GERAN
LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN

eRAN

Description
1526728306 L.IRATHO.E2G.Pr Number of inter- Multi-mode: None CS Fallback to

ep.FailOut.MME RAT handover GSM: None GERAN
preparation failures CS Fallback to
from E-UTRAN to UMTS: None
GERAN
GERAN because of LTE:
faults on the MME LOFD-001034 PS Inter-RAT
side Mobility between
LOFD-001020 GERAN
LOFD-001046 Mobility between
E-UTRAN and
TDLOFD-001046 GERAN
LOFD-001073 Service based inter-
LOFD-001023 RAT handover to
TDLOFD-001023 GERAN
Service based Inter-
RAT handover to
GERAN
Distance based
Inter-RAT handover
to GERAN
SRVCC to GERAN
SRVCC to GERAN

eRAN

Description

ep.FailOut.NoReply RAT handover GSM: None GERAN
GERAN
GERAN because of LTE:
no responses from LOFD-001034 PS Inter-RAT
GERAN Mobility between
LOFD-001020 GERAN
E-UTRAN and
TDLOFD-001046 GERAN
TDLOFD-001023 GERAN
RAT handover to
GERAN
Distance based
Inter-RAT handover
to GERAN
SRVCC to GERAN
SRVCC to GERAN

eRAN

Description

ep.FailOut.PrepFail RAT handover GSM: None GERAN
ure preparation failures CS Fallback to
GERAN
GERAN due LTE:
tobecause GERAN LOFD-001034 PS Inter-RAT
cells send handover Mobility between
preparation failure
messages LOFD-001020 GERAN
E-UTRAN and
TDLOFD-001046 GERAN
TDLOFD-001023 GERAN
RAT handover to
GERAN
Distance based
Inter-RAT handover
to GERAN
SRVCC to GERAN
SRVCC to GERAN

eRAN

Description
1526728309 L.IRATHO.E2T.Pre Number of inter- Multi-mode: None CS Fallback to

p.FailOut.MME RAT handover GSM: None UTRAN
UTRAN
TD-SCDMA LTE:
network because of LOFD-001033 PS Inter-RAT
faults on the MME Mobility between
side
LOFD-001019 UTRAN
E-UTRAN and
TDLOFD-001043 UTRAN
TDLOFD-001022 UTRAN
RAT handover to
UTRAN
Distance based
Inter-RAT handover
to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

eRAN

Description

p.FailOut.NoReply RAT handover GSM: None UTRAN
UTRAN
TD-SCDMA LTE:
network due LOFD-001033 PS Inter-RAT
tobecause of no Mobility between
responses from TD-
SCDMA network LOFD-001019 UTRAN
E-UTRAN and
TDLOFD-001043 UTRAN
TDLOFD-001022 UTRAN
RAT handover to
UTRAN
Distance based
Inter-RAT handover
to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

eRAN

Description

p.FailOut.PrepFailu RAT handover GSM: None UTRAN
re preparation failures CS Fallback to
because TD- UMTS: None
UTRAN
SCDMA network LTE:
cells send handover LOFD-001033 PS Inter-RAT
preparation failure Mobility between
messages
LOFD-001019 UTRAN
E-UTRAN and
TDLOFD-001043 UTRAN
TDLOFD-001022 UTRAN
RAT handover to
UTRAN
Distance based
Inter-RAT handover
to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN
1526728312 L.IRATHO.BlindH Number of inter- Multi-mode: None PS Inter-RAT

O.E2W.ExecAttOut RAT blind GSM: None Mobility between
handovers E-UTRAN and
executions from E- UMTS: None UTRAN
UTRAN to LTE: SRVCC to UTRAN
WCDMA network LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526728313 L.IRATHO.BlindH Number of Multi-mode: None PS Inter-RAT

O.E2W.ExecSuccO successful inter- GSM: None Mobility between
ut RAT blind E-UTRAN and
handovers from E- UMTS: None UTRAN
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

O.E2G.ExecAttOut RAT blind GSM: None Mobility between
handovers E-UTRAN and
executions from E- UMTS: None GERAN
UTRAN to LTE: SRVCC to GERAN
GERAN LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN

O.E2G.ExecSuccO successful inter- GSM: None Mobility between
ut RAT blind E-UTRAN and
handovers from E- UMTS: None GERAN
GERAN LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN

eRAN

Description

ep.FailOut.MME RAT handover MRFD-101401 Steering
preparation failures GSM: None
from E-UTRAN to CS Fallback to
WCDMA network UMTS: None UTRAN
because of faults on LTE: CS Fallback to
the MME side LOFD-001033 UTRAN
UTRAN
LOFD-001043
PS Inter-RAT
LOFD-001072 E-UTRAN and
LOFD-001022 UTRAN
TDLOFD-001022 Service based inter-
RAT handover to
UTRAN
RAT handover to
UTRAN
Distance based
Inter-RAT handover
to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

eRAN

Description

ep.FailOut.PrepFail RAT handover MRFD-101401 Steering
ure preparation failures GSM: None
because WCDMA LTE: CS Fallback to
network cells send LOFD-001033 UTRAN
handover TDLOFD-001033
preparation failure PS Inter-RAT
messages LOFD-001019 Mobility between
UTRAN
LOFD-001043
PS Inter-RAT
LOFD-001022 UTRAN
RAT handover to
UTRAN
RAT handover to
UTRAN
Distance based
Inter-RAT handover
to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

eRAN

Description

ep.FailOut.NoReply RAT handover MRFD-101401 Steering
preparation failures GSM: None
because of no LTE: CS Fallback to
responses from LOFD-001033 UTRAN
WCDMA network TDLOFD-001033 PS Inter-RAT
UTRAN
LOFD-001043
PS Inter-RAT
LOFD-001022 UTRAN
RAT handover to
UTRAN
RAT handover to
UTRAN
Distance based
Inter-RAT handover
to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN
1526728321 L.CSFB.PrepAtt Number of CSFB Multi-mode: None CS Fallback to

indicators received GSM: None UTRAN
by the eNodeB CS Fallback to
UMTS: None
UTRAN
LTE:
CS Fallback to
LOFD-001033
GERAN
TDLOFD-001033 CS Fallback to
LOFD-001034 GERAN
CDMA2000 1xRTT
LOFD-001035
CS Fallback to
TDLOFD-001035 CDMA2000 1xRTT

eRAN

Description
1526728322 L.CSFB.PrepSucc Number of Multi-mode: None CS Fallback to

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

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

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

E2W redirections from E- GSM: None Mobility between
UTRAN to E-UTRAN and
LTE: CS Fallback to
LOFD-001019 UTRAN
UTRAN
CS Fallback to
UTRAN

eRAN

Description

E2G redirections from E- GSM: None Mobility between
GERAN UMTS: None GERAN
LTE: CS Fallback to
LOFD-001020 GERAN
GERAN
CS Fallback to
GERAN
1526728328 L.IRATHO.BlindH Number of inter- Multi-mode: None CS Fallback to

O.E2W.PrepAttOut RAT blind GSM: None UTRAN
handover attempts CS Fallback to
UTRAN
WCDMA network LTE:
Mobility between
LOFD-001019 UTRAN
Mobility between
E-UTRAN and
UTRAN

O.E2G.PrepAttOut RAT blind GSM: None GERAN
GERAN
GERAN LTE:
Mobility between
LOFD-001020 GERAN
Mobility between
E-UTRAN and
GERAN

eRAN

Description

E2W.PrepAtt redirection GSM: None Mobility between
preparations from E-UTRAN and
E-UTRAN to UMTS: None UTRAN
WCDMA network LTE: CS Fallback to
LOFD-001019 UTRAN
UTRAN
CS Fallback to
UTRAN

E2G.PrepAtt redirection GSM: None Mobility between
preparations from E-UTRAN and
E-UTRAN to UMTS: None GERAN
GERAN LTE: CS Fallback to
LOFD-001020 GERAN
GERAN
CS Fallback to
GERAN

eRAN

Description

epAttOut.PLMN RAT handover MRFD-101401 Steering
attempts from E- GSM: None
for a specific LTE: E-UTRAN and
operator LOFD-001019 UTRAN
TDLOFD-001019 UTRAN
Mobility between
LOFD-001036 UTRAN
TDLOFD-001037 UTRAN
LOFD-070206 RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526728378 L.IRATHO.E2W.Ex Number of inter- Multi-mode: UL Unified Video

ecAttOut.PLMN RAT handover MRFD-101401 Steering
executions from E- GSM: None
TDLOFD-001019 UTRAN
Mobility between
LOFD-001036 UTRAN
TDLOFD-001037 UTRAN
Common Carrier
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526728379 L.IRATHO.E2W.Ex Number of Multi-mode: UL Unified Video

ecSuccOut.PLMN successful inter- MRFD-101401 Steering
RAT handovers GSM: None
from E-UTRAN to PS Inter-RAT
TDLOFD-001019 UTRAN
Mobility between
LOFD-001036 UTRAN
TDLOFD-001037 UTRAN
Common Carrier
RAN Sharing with
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526728380 L.IRATHO.E2G.Pr Number of inter- Multi-mode: None PS Inter-RAT

epAttOut.PLMN RAT handover GSM: None Mobility between
attempts from E- E-UTRAN and
GERAN for a LTE: SRVCC to GERAN
specific operator LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
TDLOFD-001036 RAN Sharing with
TDLOFD-001037 Common Carrier
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526728381 L.IRATHO.E2G.Ex Number of inter- Multi-mode: None PS Inter-RAT

ecAttOut.PLMN RAT handover GSM: None Mobility between
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526728382 L.IRATHO.E2G.Ex Number of Multi-mode: None PS Inter-RAT

ecSuccOut.PLMN successful inter- GSM: None Mobility between
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
1526728386 L.CSFB.PrepAtt.Idl Number of CSFB Multi-mode: None CS Fallback to

e indicators received GSM: None UTRAN
by the eNodeB for CS Fallback to
UEs in idle mode UMTS: None
UTRAN
LTE:
CS Fallback to
LOFD-001033
GERAN
LOFD-001034 GERAN
CDMA2000 1xRTT
LOFD-001035
CS Fallback to

eRAN

Description
1526728387 L.CSFB.PrepSucc.I Number of Multi-mode: None CS Fallback to

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

network for UEs in UMTS: None
UTRAN
idle mode LTE:
to UTRAN
TDLOFD-001033
Ultra-Flash CSFB
TDLOFD-081223

eRAN

Description

O.E2W.PrepAttOut. RAT blind GSM: None Mobility between
PLMN handover attempts E-UTRAN and
from E-UTRAN to UMTS: None UTRAN
WCDMA network LTE: SRVCC to UTRAN
for a specific LOFD-001019
operator CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

O.E2G.PrepAttOut. RAT blind GSM: None Mobility between
PLMN handover attempts E-UTRAN and
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

O.E2W.ExecAttOut RAT blind GSM: None Mobility between
.PLMN handover E-UTRAN and
for a specific CS Fallback to
LOFD-001022 UTRAN
operator
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

O.E2W.ExecSuccO successful inter- GSM: None Mobility between
ut.PLMN RAT blind E-UTRAN and
handover UMTS: None UTRAN
executions from E- LTE: SRVCC to UTRAN
UTRAN to LOFD-001019
WCDMA network CS Fallback to
LOFD-001022 UTRAN
for a specific
operator LOFD-001033 PS Inter-RAT
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

O.E2G.ExecAttOut. RAT blind GSM: None Mobility between
PLMN handover E-UTRAN and
executions from E- UMTS: None GERAN
GERAN for a LOFD-001020
specific operator CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

O.E2G.ExecSuccO successful inter- GSM: None Mobility between
ut.PLMN RAT blind E-UTRAN and
handover UMTS: None GERAN
executions from E- LTE: SRVCC to GERAN
GERAN for a CS Fallback to
LOFD-001023 GERAN
specific operator
GERAN
TDLOFD-001034
SRVCC to GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing
1526728497 L.RRCRedirection. Number of CSFB- Multi-mode: None CS Fallback to

E2W.CSFB based redirections GSM: None UTRAN
from E-UTRANs to CS Fallback to
WCDMA network UMTS: None
UTRAN
LTE:
LOFD-001033
TDLOFD-001033

E2G.CSFB based redirections GSM: None GERAN
GERAN UMTS: None
GERAN
LTE:
LOFD-001034
TDLOFD-001034

eRAN

Description

E2T.CSFB based redirections GSM: None UTRAN
TD-SCDMA UMTS: None
UTRAN
network LTE:
LOFD-001033
TDLOFD-001033
1526728504 L.IRATHO.E2W.C Number of CSFB- Multi-mode: None CS Fallback to

SFB.PrepAttOut based inter-RAT GSM: None UTRAN
handover CS Fallback to
preparation UMTS: None
UTRAN
attempts from E- LTE:
WCDMA network TDLOFD-001033

SFB.ExecAttOut based inter-RAT GSM: None UTRAN
handover execution CS Fallback to
attempts from E- UMTS: None
UTRAN
UTRAN to LTE:
TDLOFD-001033
1526728506 L.IRATHO.E2W.C Number of Multi-mode: None CS Fallback to

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

FB.PrepAttOut based inter-RAT GSM: None GERAN
GERAN
GERAN TDLOFD-001034

FB.ExecAttOut based inter-RAT GSM: None GERAN
GERAN
UTRAN to LTE:
GERAN LOFD-001034
TDLOFD-001034

eRAN

Description
1526728509 L.IRATHO.E2G.CS Number of Multi-mode: None CS Fallback to

FB.ExecSuccOut successful CSFB- GSM: None GERAN
handover UMTS: None
GERAN
GERAN TDLOFD-001034
1526728510 L.IRATHO.E2T.CS Number of CSFB- Multi-mode: None CS Fallback to

FB.PrepAttOut based inter-RAT GSM: None UTRAN
UTRAN
UTRAN to TD- LOFD-001033
SCDMA network TDLOFD-001033

FB.ExecAttOut based inter-RAT GSM: None UTRAN
UTRAN
UTRAN to TD- LTE:
SCDMA network LOFD-001033
TDLOFD-001033
1526728512 L.IRATHO.E2T.CS Number of Multi-mode: None CS Fallback to

FB.ExecSuccOut successful CSFB- GSM: None UTRAN
handover UMTS: None
UTRAN
UTRAN to TD- LOFD-001033
SCDMA network TDLOFD-001033
1526728513 L.CSFB.PrepFail.C Number of CSFB Multi-mode: None CS Fallback to

onflict preparation failures GSM: None UTRAN
because of process CS Fallback to
conflict UMTS: None
UTRAN
LTE:
GERAN
TDLOFD-001033
CS Fallback to
LOFD-001034 GERAN
LOFD-001035 CDMA2000 1xRTT

eRAN

Description
1526728560 L.IRATHO.E2W.N Number of inter- Multi-mode: None PS Inter-RAT

oData.ExecAttOut RAT handover GSM: None Mobility between
UTRAN to UMTS: None UTRAN
triggered for UEs LOFD-001019
that do not transmit CS Fallback to
LOFD-001022 UTRAN
or receive data
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001105
CS Fallback to
TDLOFD-001105 UTRAN
Dynamic DRX
Dynamic DRX
1526728561 L.IRATHO.E2W.N Number of Multi-mode: None PS Inter-RAT

oData.ExecSuccOut successful inter- GSM: None Mobility between
from E-UTRAN to UMTS: None UTRAN
triggered for UEs LOFD-001019
that do not transmit CS Fallback to
LOFD-001022 UTRAN
or receive data
UTRAN
TDLOFD-001033
SRVCC to UTRAN
LOFD-001105
CS Fallback to
TDLOFD-001105 UTRAN
Dynamic DRX
Dynamic DRX
1526728705 L.FlashCSFB.E2W Number of Multi-mode: None Flash CS Fallback

procedures for flash GSM: None to UTRAN
CSFB to WCDMA Flash CS Fallback
network UMTS: None
to UTRAN
LTE:
LOFD-001052
TDLOFD-001052

eRAN

Description
1526728706 L.FlashCSFB.E2G Number of Multi-mode: None Flash CS Fallback

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

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

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

gency procedures for GSM: None UTRAN
network triggered UMTS: None
UTRAN
for emergency calls LTE:
to UTRAN
TDLOFD-001033
Ultra-Flash CSFB
TDLOFD-081223

eRAN

Description
1526728710 L.CSFB.E2G.Emer Number of Multi-mode: None CS Fallback to

gency procedures for GSM: None GERAN
triggered for UMTS: None
GERAN
emergency calls LTE:
LOFD-001034
TDLOFD-001034

O.E2T.PrepAttOut RAT blind GSM: None UTRAN
UTRAN
TD-SCDMA LTE:
network LOFD-001033 PS Inter-RAT
Mobility between
LOFD-001019 UTRAN
Mobility between
E-UTRAN and
UTRAN

O.E2T.ExecAttOut RAT blind GSM: None Mobility between
handover E-UTRAN and
UTRAN to TD- LTE: SRVCC to UTRAN
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description

O.E2T.ExecSuccOu successful inter- GSM: None Mobility between
t RAT blind E-UTRAN and
handovers from E- UMTS: None UTRAN
UTRAN to TD- LTE: SRVCC to UTRAN
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526728749 L.CSFB.E2T Number of Multi-mode: None CS Fallback to

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

SRVCC to TD- CS Fallback to
SCDMA network UMTS: None
UTRAN
for UEs in idle LTE:
mode LOFD-001033
TDLOFD-001033

E2T.PrepAtt redirection GSM: None Mobility between
preparations to TD- E-UTRAN and
SCDMA network UMTS: None UTRAN
LTE: CS Fallback to
LOFD-001019 UTRAN
UTRAN
CS Fallback to
UTRAN

eRAN

Description

E2T redirections to TD- GSM: None Mobility between
SCDMA network E-UTRAN and
UMTS: None UTRAN
LTE: CS Fallback to
LOFD-001019 UTRAN
UTRAN
CS Fallback to
UTRAN
1526728870 L.IRATHO.T2E.Pre Number of inter- Multi-mode: None PS Inter-RAT

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

pInSucc successful inter- GSM: None Mobility between
RAT handover E-UTRAN and
preparations from UMTS: None UTRAN
TD-SCDMA LTE: SRVCC to UTRAN
network to E- LOFD-001019
UTRAN CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526728872 L.IRATHO.T2E.Ex Number of Multi-mode: None PS Inter-RAT

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

pInFail.TgtNotAllo RAT handover GSM: None Mobility between
w preparation failures E-UTRAN and
from TD-SCDMA UMTS: None UTRAN
network in the LTE: SRVCC to UTRAN
target cell due to LOFD-001019
Handover Target CS Fallback to
LOFD-001022 UTRAN
not allowed
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526728874 L.IRATHO.W2E.Pr Number of inter- Multi-mode: None PS Inter-RAT

epAttIn RAT handover GSM: None Mobility between
attempts from E-UTRAN and
to E-UTRAN LTE: SRVCC to UTRAN
LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526728875 L.IRATHO.W2E.Pr Number of Multi-mode: None PS Inter-RAT

epInSucc successful inter- GSM: None Mobility between
RAT handover E-UTRAN and
preparations from UMTS: None UTRAN
to E-UTRAN LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526728876 L.IRATHO.W2E.E Number of Multi-mode: None PS Inter-RAT

xecSuccIn successful inter- GSM: None Mobility between
from WCDMA UMTS: None UTRAN
network to E- LTE: SRVCC to UTRAN
UTRAN LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526728877 L.IRATHO.W2E.Pr Number of inter- Multi-mode: None PS Inter-RAT

epInFail.TgtNotAll RAT handover GSM: None Mobility between
ow preparation failures E-UTRAN and
from WCDMA UMTS: None UTRAN
network in the LTE: SRVCC to UTRAN
target cell due to LOFD-001019
Handover Target CS Fallback to
LOFD-001022 UTRAN
not allowed
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description

SFB.MMEAbnorm responses for GSM: None UTRAN
Rsp abnormal causes CS Fallback to
received by the UMTS: None
UTRAN
eNodeB from the LTE:
MME during LOFD-001033
CSFB-based inter- TDLOFD-001033
RAT handover
executions from E-
UTRAN to
WCDMA network

FB.MMEAbnormR responses for GSM: None GERAN
sp abnormal causes CS Fallback to
GERAN
RAT handover
executions from E-
UTRAN to
GERAN
1526728901 L.IRATHO.E2T.CS Number of Multi-mode: None CS Fallback to

FB.MMEAbnormR responses for GSM: None UTRAN
sp abnormal causes CS Fallback to
UTRAN
RAT handover
executions from E-
UTRAN to TD-
SCDMA network
1526728946 L.RIM.SI.E2W.Req Number of times Multi-mode: None Flash CS Fallback

the eNodeB sends a GSM: None to UTRAN
system information Flash CS Fallback
request to a UMTS: None
to UTRAN
WCDMA network LTE:
LOFD-001052
TDLOFD-001052

eRAN

Description
1526728947 L.RIM.SI.E2W.Res Number of times Multi-mode: None Flash CS Fallback

p the eNodeB GSM: None to UTRAN
receives a system Flash CS Fallback
information UMTS: None
to UTRAN
response from a LTE:
TDLOFD-001052
1526728948 L.RIM.SI.E2W.Upd Number of times Multi-mode: None Flash CS Fallback

ate the eNodeB GSM: None to UTRAN
information update UMTS: None
to UTRAN
from a WCDMA LTE:
network LOFD-001052
TDLOFD-001052
1526728949 L.RIM.Load.E2W. Number of times Multi-mode: None Inter-RAT Load

Req the eNodeB sends a GSM: None Sharing to UTRAN
load information Inter-RAT Load
Sharing to UTRAN
WCDMA network LTE:
LOFD-001044
TDLOFD-001044

Resp the eNodeB GSM: None Sharing to UTRAN
receives a load Inter-RAT Load
Sharing to UTRAN
TDLOFD-001044

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

procedures for GSM: None GERAN
network for UEs in UMTS: None
GERAN
idle mode LTE:
LOFD-001034
TDLOFD-001034

eRAN

Description
1526729432 L.IRATHO.E2W.Ti Average handover Multi-mode: None PS Inter-RAT

meAvg duration from E- GSM: None Mobility between
LTE: SRVCC to UTRAN
LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526729433 L.IRATHO.E2G.Ti Average handover Multi-mode: None PS Inter-RAT

GERAN UMTS: None GERAN
LTE: SRVCC to GERAN
LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN
1526729434 L.IRATHO.E2T.Ti Average handover Multi-mode: None PS Inter-RAT

UTRAN to TD- E-UTRAN and
SCDMA network UMTS: None UTRAN
LTE: SRVCC to UTRAN
LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description

E2W.PLMN redirections from E- GSM: None Mobility between
for a specific LTE: CS Fallback to
UTRAN
LOFD-001036
CS Fallback to
LOFD-001037 UTRAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

E2G.PLMN redirections from E- GSM: None Mobility between
GERAN for a UMTS: None GERAN
specific operator LTE: CS Fallback to
LOFD-001020 GERAN
GERAN
LOFD-001036
CS Fallback to
LOFD-001037 GERAN
Dedicated Carrier
RAN Sharing with
Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526729505 L.CCOwithNACC. Number of CSFB- Multi-mode: None CS Fallback to

E2G.CSFB.ExecAtt based CCO with GSM: None GERAN
Out NACC executions CS Fallback to
GERAN
GERAN LTE:
LOFD-001034
TDLOFD-001034
1526729506 L.CCOwithNACC. Number of Multi-mode: None CS Fallback to

E2G.CSFB.ExecSu successful CSFB- GSM: None GERAN
ccOut based CCOs with CS Fallback to
NACC from E- UMTS: None
GERAN
UTRAN to LTE:
GERAN LOFD-001034
TDLOFD-001034
1526729507 L.CCOwithoutNAC Number of CSFB- Multi-mode: None CS Fallback to

C.E2G.CSFB.Exec based CCO without GSM: None GERAN
AttOut NACC executions CS Fallback to
GERAN
GERAN LTE:
LOFD-001034
TDLOFD-001034
1526729508 L.CCOwithoutNAC Number of Multi-mode: None CS Fallback to

C.E2G.CSFB.Exec successful CSFB- GSM: None GERAN
SuccOut based CCOs CS Fallback to
without NACC UMTS: None
GERAN
from E-UTRAN to LTE:
GERAN LOFD-001034
TDLOFD-001034

SFB.PrepAttOut.E based handover GSM: None UTRAN
mergency preparation CS Fallback to
attempts to UMTS: None
UTRAN
WCDMA network LTE:
triggered for LOFD-001033
emergency calls TDLOFD-001033

SFB.ExecAttOut.E based handover GSM: None UTRAN
mergency execution attempts CS Fallback to
to WCDMA UMTS: None
UTRAN
network triggered LTE:
for emergency calls LOFD-001033
TDLOFD-001033

eRAN

Description

SFB.ExecSuccOut. successful CSFB- GSM: None UTRAN
Emergency based handover CS Fallback to
executions to UMTS: None
UTRAN
WCDMA network LTE:
triggered for LOFD-001033
emergency calls TDLOFD-001033

FB.PrepAttOut.Em based handover GSM: None GERAN
ergency preparation CS Fallback to
attempts to GERAN UMTS: None
GERAN
triggered for LTE:
emergency calls LOFD-001034
TDLOFD-001034

FB.ExecAttOut.Em based handover GSM: None GERAN
ergency execution attempts CS Fallback to
to GERAN UMTS: None
GERAN
triggered for LTE:
emergency calls LOFD-001034
TDLOFD-001034

FB.ExecSuccOut.E successful CSFB- GSM: None GERAN
mergency based handover CS Fallback to
executions to UMTS: None
GERAN
GERAN triggered LTE:
for emergency calls LOFD-001034
TDLOFD-001034

E2W.CSFB.TimeO based blind GSM: None UTRAN
ut redirections from E- CS Fallback to
UTRAN to UMTS: None
UTRAN
WCDMA network LTE:
caused by CSFB LOFD-001033
protection timer TDLOFD-001033
expiration

E2G.CSFB.TimeOu based blind GSM: None GERAN
t redirections from E- CS Fallback to
UTRAN to UMTS: None
GERAN
GERAN caused by LTE:
CSFB protection LOFD-001034
timer expiration TDLOFD-001034

eRAN

Description
1526729562 L.IRATHO.NCell.E Number of Multi-mode: None PS Inter-RAT

2G.PrepAttOut handover attempts GSM: None Mobility between
from a specific E- E-UTRAN and
UTRAN cell to a UMTS: None GERAN
specific GERAN LTE: SRVCC to GERAN
cell LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN

2G.ExecAttOut handover GSM: None Mobility between
executions from a E-UTRAN and
specific E-UTRAN UMTS: None GERAN
cell to a specific LTE: SRVCC to GERAN
GERAN cell LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN

2G.ExecSuccOut successful GSM: None Mobility between
handovers from a E-UTRAN and
specific E-UTRAN UMTS: None GERAN
cell to a specific LTE: SRVCC to GERAN
GERAN cell LOFD-001020
CS Fallback to
LOFD-001023 GERAN
GERAN
TDLOFD-001034
SRVCC to GERAN
CS Fallback to
GERAN

eRAN

Description

2W.PrepAttOut handover attempts GSM: None Mobility between
from a specific E- E-UTRAN and
UTRAN cell to a UMTS: None UTRAN
specific WCDMA LTE: SRVCC to UTRAN
cell LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

2W.ExecAttOut handover GSM: None Mobility between
executions from a E-UTRAN and
specific E-UTRAN UMTS: None UTRAN
cell to a specific LTE: SRVCC to UTRAN
WCDMA cell LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

2W.ExecSuccOut successful GSM: None Mobility between
handovers from a E-UTRAN and
specific E-UTRAN UMTS: None UTRAN
cell to a specific LTE: SRVCC to UTRAN
WCDMA cell LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526729661 L.RIM.SI.E2G.Req Number of times Multi-mode: None Flash CS Fallback

the eNodeB sends a GSM: None to GERAN
system information Flash CS Fallback
to GERAN
GERAN LTE:
LOFD-001053
TDLOFD-001053
1526729662 L.RIM.SI.E2G.Res Number of times Multi-mode: None Flash CS Fallback

p the eNodeB GSM: None to GERAN
to GERAN
GERAN LOFD-001053
TDLOFD-001053
1526729663 L.RIM.SI.E2G.Upd Number of times Multi-mode: None Flash CS Fallback

ate the eNodeB GSM: None to GERAN
to GERAN
from a GERAN LTE:
LOFD-001053
TDLOFD-001053
1526730044 L.CSFB.PrepAtt.PL Number of CSFB Multi-mode: None CS Fallback to

MN indicators received GSM: None UTRAN
by the eNodeB for a CS Fallback to
specific operator UMTS: None
UTRAN
LTE:
GERAN
TDLOFD-001033
CS Fallback to
LOFD-001034 GERAN
LOFD-001037 Common Carrier
Dedicated Carrier
TDLOFD-001037
RAN Sharing with
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description
1526730045 L.CSFB.PrepSucc.P Number of Multi-mode: None CS Fallback to

LMN successful CSFB GSM: None UTRAN
responses sent from CS Fallback to
the eNodeB for a UMTS: None
UTRAN
specific operator LTE:
GERAN
TDLOFD-001033
CS Fallback to
LOFD-001034 GERAN
Dedicated Carrier
TDLOFD-001037
RAN Sharing with
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

E2W.CSFB.PLMN based redirections GSM: None UTRAN
WCDMA network UMTS: None
UTRAN
for a specific LTE:
operator LOFD-001033 RAN Sharing with
Common Carrier
TDLOFD-001033
RAN Sharing with
LOFD-001036 Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

SFB.PrepAttOut.PL based handover GSM: None UTRAN
MN preparation CS Fallback to
UTRAN
UTRAN to LTE:
WCDMA network LOFD-001033 RAN Sharing with
for a specific Common Carrier
TDLOFD-001033
operator RAN Sharing with
Hybrid RAN
Sharing

SFB.ExecAttOut.P based handover GSM: None UTRAN
LMN execution attempts CS Fallback to
UTRAN
WCDMA network LTE:
for a specific LOFD-001033 RAN Sharing with
operator Common Carrier
TDLOFD-001033
RAN Sharing with
Hybrid RAN
Sharing

SFB.ExecSuccOut. successful CSFB- GSM: None UTRAN
PLMN based handover CS Fallback to
executions from E- UMTS: None
UTRAN
UTRAN to LTE:
WCDMA network LOFD-001033 RAN Sharing with
for a specific Common Carrier
TDLOFD-001033
operator RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

E2G.CSFB.PLMN based redirections GSM: None GERAN
GERAN for a UMTS: None
GERAN
specific operator LTE:
Common Carrier
TDLOFD-001034
RAN Sharing with
Hybrid RAN
Sharing

FB.PrepAttOut.PL based handover GSM: None GERAN
MN preparation CS Fallback to
GERAN
UTRAN to LTE:
GERAN for a LOFD-001034 RAN Sharing with
specific operator Common Carrier
TDLOFD-001034
RAN Sharing with
Hybrid RAN
Sharing

FB.ExecAttOut.PL based handover GSM: None GERAN
MN execution attempts CS Fallback to
GERAN
GERAN for a LTE:
specific operator LOFD-001034 RAN Sharing with
Common Carrier
TDLOFD-001034
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

FB.ExecSuccOut.P successful CSFB- GSM: None GERAN
LMN based handover CS Fallback to
GERAN
UTRAN to LTE:
GERAN for a LOFD-001034 RAN Sharing with
specific operator Common Carrier
TDLOFD-001034
RAN Sharing with
Hybrid RAN
Sharing

SFB.Prep.FailOut. based outgoing GSM: None UTRAN
MME handover CS Fallback to
preparation failures UMTS: None
UTRAN
because of the TDLOFD-001033
MME side causes

SFB.Prep.FailOut.P based outgoing GSM: None UTRAN
repFailure handover CS Fallback to
UTRAN
because of the TDLOFD-001033
response of
handover
preparation failure
from WCDMA
network

SFB.Prep.FailOut.N based outgoing GSM: None UTRAN
oReply handover CS Fallback to
UTRAN
because of no TDLOFD-001033
response from
WCDMA network

eRAN

Description

FB.Prep.FailOut.M based outgoing GSM: None UTRAN
ME handover CS Fallback to
UTRAN
TD-SCDMA LOFD-001033
network because of TDLOFD-001033
the MME side
causes

FB.Prep.FailOut.Pr based outgoing GSM: None UTRAN
epFailure handover CS Fallback to
UTRAN
the response of
handover
preparation failure
from TD-SCDMA
network

FB.Prep.FailOut.No based outgoing GSM: None UTRAN
Reply handover CS Fallback to
UTRAN
no response from
TD-SCDMA
network
1526730146 L.IRATHO.CSFB.S Number of SRVCC- Multi-mode: None Ultra-Flash CSFB

RVCC.E2W.PrepAt based outgoing GSM: None to UTRAN
tOut handover attempts
WCDMA network LTE:
for ultra-flash LOFD-070202
CSFB

RVCC.E2W.ExecAt based outgoing GSM: None to UTRAN
tOut handover
UTRAN to LTE:
for ultra-flash
CSFB

eRAN

Description
1526730148 L.IRATHO.CSFB.S Number of Multi-mode: None Ultra-Flash CSFB

RVCC.E2W.ExecS successful SRVCC- GSM: None to UTRAN
uccOut based outgoing
handovers from E- UMTS: None
UTRAN to LTE:
for ultra-flash
CSFB

RVCC.E2G.PrepAtt based outgoing GSM: None to GERAN
Out handover attempts Ultra-Flash CSFB
to GERAN
GERAN for ultra- LTE:
flash CSFB LOFD-081283
TDLOFD-081203

RVCC.E2G.ExecAt based outgoing GSM: None to GERAN
tOut handover Ultra-Flash CSFB
to GERAN
UTRAN to LTE:
GERAN for ultra- LOFD-081283
flash CSFB TDLOFD-081203

RVCC.E2G.ExecSu successful SRVCC- GSM: None to GERAN
ccOut based outgoing Ultra-Flash CSFB
handovers from E- UMTS: None
to GERAN
UTRAN to LTE:
GERAN for ultra- LOFD-081283
flash CSFB TDLOFD-081203

RVCC.E2G.MMEA abnormal responses GSM: None to GERAN
bnormRsp from the MME Ultra-Flash CSFB
during outgoing UMTS: None
to GERAN
handovers from E- LTE:
GERAN for ultra- TDLOFD-081203
flash CSFB

eRAN

Description

RVCC.E2W.MME responses for GSM: None to UTRAN
AbnormRsp abnormal causes Ultra-Flash CSFB
to UTRAN
handovers from the TDLOFD-081223
E-UTRAN to
WCDMA networks
for ultra-flash
CSFB
1526736729 L.IRATHO.E2W.C Number of MME- Multi-mode: None Ultra-Flash CSFB

SFB.SRVCC.Prep.F caused preparation GSM: None to UTRAN
ailOut.MME failures of outgoing
handovers to UMTS: None
WCDMA networks LTE:
CSFB
1526736730 L.IRATHO.E2W.C Number of Multi-mode: None Ultra-Flash CSFB

SFB.SRVCC.Prep.F preparation failures GSM: None to UTRAN
ailOut.PrepFailure of outgoing
WCDMA networks LTE:
CSFB because of
the response of
handover
preparation failure
sent by the
WCDMA networks
1526736731 L.IRATHO.E2W.C Number of Multi-mode: None Ultra-Flash CSFB

SFB.SRVCC.Prep.F preparation failures GSM: None to UTRAN
ailOut.NoReply of outgoing
WCDMA networks LTE:
CSFB because of
no response from
the WCDMA
networks

eRAN

Description
1526736732 L.IRATHO.E2G.CS Number of MME- Multi-mode: None Ultra-Flash CSFB

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

FB.SRVCC.Prep.Fa preparation failures GSM: None to GERAN
ilOut.PrepFailure of outgoing Ultra-Flash CSFB
to GERAN
flash CSFB because LOFD-081283
of the response of TDLOFD-081203
handover
preparation failure
sent by the
GERANs
1526736734 L.IRATHO.E2G.CS Number of Multi-mode: None Ultra-Flash CSFB

FB.SRVCC.Prep.Fa preparation failures GSM: None to GERAN
ilOut.NoReply of outgoing Ultra-Flash CSFB
to GERAN
flash CSFB because LOFD-081283
of no response from TDLOFD-081203
the GERANs

pInFail.AdmitFail TDSCDMA-to- GSM: None Mobility between
EUTRAN handover E-UTRAN and
preparation failures UMTS: None UTRAN
because of LTE: SRVCC to UTRAN
admission failure LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description

pInFail.FlowCtrl TDSCDMA-to- GSM: None Mobility between
because of flow LTE: SRVCC to UTRAN
control LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

pInFail.HOCancel TDSCDMA-to- GSM: None Mobility between
because the target LTE: SRVCC to UTRAN
cell receives LOFD-001019
LOFD-001022 UTRAN
cancelation
messages LOFD-001033 PS Inter-RAT
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526736748 L.IRATHO.T2E.Pre Number of times Multi-mode: None PS Inter-RAT

pInFail.disc.FlowCt TDSCDMA-to- GSM: None Mobility between
rl EUTRAN handover E-UTRAN and
messages are UMTS: None UTRAN
discarded because LTE: SRVCC to UTRAN
of flow control LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description

epInFail.AdmitFail WCDMA-to- GSM: None Mobility between
because of LTE: SRVCC to UTRAN
admission failure LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

epInFail.FlowCtrl WCDMA-to- GSM: None Mobility between
because of flow LTE: SRVCC to UTRAN
control LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

epInFail.HOCancel WCDMA-to- GSM: None Mobility between
because the target LTE: SRVCC to UTRAN
cell receives LOFD-001019
LOFD-001022 UTRAN
cancelation
messages LOFD-001033 PS Inter-RAT
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description
1526736752 L.IRATHO.W2E.Pr Number of times Multi-mode: None PS Inter-RAT

epInFail.disc.Flow WCDMA-to- GSM: None Mobility between
Ctrl EUTRAN handover E-UTRAN and
messages are UMTS: None UTRAN
discarded because LTE: SRVCC to UTRAN
of flow control LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN
1526736753 L.IRATHO.G2E.Pr Number of Multi-mode: None PS Inter-RAT

epInFail GERAN-to- GSM: None Mobility between
LTE: SRVCC to UTRAN
LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

pInFail TDSCDMA-to- GSM: None Mobility between
LTE: SRVCC to UTRAN
LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

eRAN

Description

epInFail WCDMA-to- GSM: None Mobility between
LTE: SRVCC to UTRAN
LOFD-001019
CS Fallback to
LOFD-001022 UTRAN
UTRAN
TDLOFD-001033
SRVCC to UTRAN
CS Fallback to
UTRAN

SFB.MMEAbnorm responses for GSM: None UTRAN
Rsp.PLMN abnormal causes CS Fallback to
UTRAN
RAT handover
executions from E-
UTRAN to
WCDMA network
for a specific
operator

E2T.CSFB.TimeOu based blind LTE-to- GSM: None UTRAN
t TD-SCDMA CS Fallback to
redirections UMTS: None
UTRAN
triggered due to LTE:
timer expiration LOFD-001033
TDLOFD-001033

eRAN
CS Fallback Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

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

eRAN
CS Fallback Feature Parameter Description 12 Appendix
12 Appendix
12.1 CSFB to UTRAN
12.1.1 Combined EPS/IMSI Attach Procedure

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

eRAN
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.
The combined EPS/IMSI attach procedure is described as follows:

1. The UE sends a Combined attach request message to the MME, requesting a combined
EPS/IMSI attach procedure. This message also indicates whether the CSFB or SMS over
SGs function is required.
2. The EPS attach procedure is performed in the same way as it is performed within the
LTE system. For details, see section 5.3.2 in 3GPP TS 23.401 V9.2.0.
3. The MME allocates an LAI to the UE, and then it finds the MSC/VLR for the UE based
on the LAI. If multiple PLMNs are available for the CS domain, the MME selects a
PLMN based on the selected PLMN information reported by the eNodeB. Then, the
MME sends the MSC/VLR a Location update request message, which contains the new
LAI, IMSI, MME name, and location update type.
4. The MSC/VLR performs the location update procedure in the CS domain.
5. The MSC/VLR responds with a Location update accept message that contains
information about the VLR and temporary mobile subscriber identity (TMSI). The
location update procedure is successful.
6. The UE is informed that the combined EPS/IMSI attach procedure is successful. If the
network supports SMS over SGs but not CSFB, the message transmitted to the UE
contains the information element (IE) SMS-only. The message indicates that the
combined EPS/IMSI attach procedure is successful but only SMS is supported.
12.1.2 CSFB Based on PS Handover

During CSFB based on PS handover, the UE is transferred from the E-UTRAN to the
UTRAN by performing a PS handover. It then initiates a CS service in the UTRAN.
Call procedure
Figure 12-2 shows the procedure for CSFB to UTRAN based on PS handover for mobile-
originated calls.

eRAN
Figure 12-2 CSFB to UTRAN based on PS handover for mobile-originated calls
1. The UE sends the MME an NAS message Extended Service Request to initiate a CS
service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure.
If the MME supports the LAI-related feature, the MME also delivers the LAI to the
eNodeB.
3. If the MME supports the LAI-related feature, the MME also delivers the LAI to the
eNodeB.
4. The eNodeB initiates the preparation phase for a PS handover. If the preparation is
successful, the eNodeB instructs the UE to perform a handover.
NOTE
For details about how the eNodeB selects a target cell and a CSFB policy, see 3.5 Handover
Decision and 3.6 Handover Execution.
5. After the handover, the UE may initiate a CS call establishment procedure with an LAU
or combined RAU/LAU procedure in the UTRAN.
6. The follow-up procedures are performed for the PS handover. These procedures include
data forwarding, path switching, and RAU. This step is performed together with 5.
CSFB Procedure for Mobile-terminated Calls

Figure 12-3 shows the procedure for CSFB to UTRAN based on PS handover for mobile-
terminated calls.

eRAN
Figure 12-3 CSFB to UTRAN based on PS handover for mobile-terminated calls
1. The MSC sends a Paging Request message from the CS domain to the MME over the
SGs interface. Then, either of the following occurs:
If the UE is in idle mode, the MME sends a Paging message to the eNodeB. Then
the eNodeB sends a Paging message over the Uu interface to inform the UE of an
incoming call from the CS domain.
If the UE is in active mode, the MME sends the UE an NAS message to inform the
UE of an incoming call from the CS domain.
2. The UE sends an Extended Service Request message containing a CS Fallback Indicator
after receiving the paging message from the CS domain.
3. The MME instructs the eNodeB over the S1 interface to perform CSFB.
4. The subsequent steps are similar to steps 3 through 6 in the procedure for CSFB to
UTRAN based on PS handover for mobile-originated calls. The only difference is that
the UE sends a Paging Response message from the UTRAN cell.
12.1.3 Signaling procedure of redirection to CDMA2000 1xRTT

During CSFB based on PS redirection, the eNodeB receives a CS Fallback Indicator, and then
it sends an RRC Connection Release message to release the UE. The message contains
information about a target UTRAN frequency, reducing the time for the UE to search for a
target network. After selecting the UTRAN, the UE acquires the system information of a
UTRAN cell. Then, the UE performs initial access to the cell to initiate a CS service. For the
UTRAN, the UE is an initially accessing user.
Call procedure
Figure 12-4 shows the procedure for CSFB to UTRAN based on redirection for mobile-
originated calls.

eRAN
Figure 12-4 CSFB to UTRAN based on redirection for mobile-originated calls
service.
eNodeB.
eNodeB.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a
redirection. The message contains information about a target UTRAN frequency. Then,
the eNodeB initiates an S1 UE context release procedure.
NOTE
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in
the target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.

In a mobile-terminated call, the MSC sends a Paging request message from the CS domain to
the MME over the SGs interface, and then the MME or eNodeB initiates a paging procedure
for the UE. The paging procedure is similar to that for UTRAN described in 12.1.2 CSFB
Based on PS Handover. The subsequent steps are the same as the steps in the procedure for
CSFB to UTRAN based on PS handover for mobile-originated calls.

eRAN
12.1.4 Flash CSFB

During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it
sends an RRC Connection Release message to release the UE. The message contains
information about a target UTRAN frequency, as well as one or more physical cell identities
and their associated system information. In this way, the UE can quickly access the target
UTRAN without the need to perform the procedure for acquiring system information of the
target UTRAN cell. Then, the UE can directly initiate a CS service in the UTRAN cell.
Call procedure
Figure 12-5 shows the procedure for CSFB to UTRAN based on flash redirection for mobile-
originated calls.
Figure 12-5 CSFB to UTRAN based on flash redirection for mobile-originated calls
service.
eNodeB.
eNodeB.
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.

eRAN
NOTE
Decision and 3.6 Handover Execution. The system information of the target cell is acquired
during the RIM procedure.
the target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.

CSFB to UTRAN based on PS handover for mobile-originated calls.

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

eRAN
Figure 12-6 Flash CSFB to UTRAN for mobile-originated calls
CSFB Procedure for Mobile-Terminated Calls

Figure 12-7 shows the procedure of ultra-flash CSFB to UTRAN for mobile-terminated calls.
Ultra-flash CSFB for mobile-terminated calls excludes the same procedures as ultra-flash
CSFB for mobile-originated calls. For details about the standard procedure, see chapter 7
"Mobile Terminating Call" in 3GPP TS 23.272 V10.9.0 and 3GPP TS 24.008 V11.0.0.

eRAN
Figure 12-7 Ultra-flash CSFB to UTRAN for mobile-terminated calls
12.1.6 Redirection-based CSFB Optimization for UEs in Idle

Mode
After the NodeB receives an initial context setup request with a CS Fallback Indicator from
the MME, the eNodeB does not perform the UE capability query, Uu security mode
command, or RRC connection reconfiguration procedure with dashed lines in the following
figure:

eRAN
Figure 12-8 Redirection-based CSFB optimization for UEs in idle mode
12.1.7 CSFB for SMS

SMS services are unknown to the eNodeB because SMS messages are encapsulated in NAS
messages. During interworking with the UTRAN, SMS messages are exchanged between the
MME and the MSC over the SGs interface. Because a UE does not require fallback to the
UTRAN to perform an SMS service, the SMS over SGs function can be used in a place
covered only by the E-UTRAN.
As the SMS service is transparent to the eNodeB, the procedure is not described in this
document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
12.1.8 Emergency Call

The CSFB procedure for an emergency call is the same as the CSFB procedure for a normal
mobile-originated voice service. The UE sends an RRC Connection Request message over the
Uu interface or the MME sends an Initial Context Setup Request or UE Context Modification
Request message, which contains an IE to inform the eNodeB of the service type. Emergency
calls take precedence over other services in the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in
the handover restriction list when selecting the target cell. The eNodeB sends the RNC a
handover request with the IE CSFB high priority in the IE Source to Target Transparent
Container. This request informs the RNC that a CSFB procedure is required for an emergency

eRAN
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.
12.1.9 CSFB for LCS

After a UE initiates an LCS request, the MME performs an attach or combined TAU/LAU
procedure to inform the UE of the LCS capability of the EPS. If the EPS does not support
LCS, the UE falls back to the UTRAN to initiate LCS under the control of the EPS. The
CSFB procedure is the same as the procedure for CSFB to UTRAN for mobile-originated
calls.
If the UTRAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the
MSC sends an LCS indicator to the MME over the SGs interface. Then, the MME instructs
the eNodeB to perform CSFB for the UE. The CSFB procedure is the same as the procedure
for CSFB to UTRAN for mobile-terminated calls. The UE performs the LCS service after the
fallback to the UTRAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272 V10.0.0
and LCS.
12.2 CSFB to GERAN
12.2.1 Combined EPS/IMSI Attach Procedure

The combined EPS/IMSI attach procedure for CSFB to GERAN is the same as that for CSFB
to UTRAN. For details, see 12.1.1 Combined EPS/IMSI Attach Procedure.
12.2.2 CSFB Based on PS Handover

During CSFB based on PS handover, the UE is transferred from the E-UTRAN to the
GERAN by performing a PS handover. It then initiates a CS service in the GERAN. If the
GERAN or UE does not support dual transfer mode (DTM, in which CS and PS services run
simultaneously), the ongoing PS services of the UE are suspended before a CS service is set
up.
Call procedure
Figure 12-9 shows the procedure for CSFB to GERAN based on PS handover for mobile-
originated calls.

eRAN
Figure 12-9 CSFB to GERAN based on PS handover for mobile-originated calls
The procedure is described as follows:

1. The UE sends the MME a NAS message Extended service request to initiate a CS
service.
2. The MME instructs the eNodeB to initiate a CSFB procedure. If the MME supports the
LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform blind handover based on the UE
capabilities, parameters settings, and algorithm policies.
4. The eNodeB initiates the preparation phase for a PS handover. If the preparation is
successful, the eNodeB instructs the UE to perform a handover. If the GERAN or UE
does not support DTM, the ongoing PS services of the UE are suspended, and the SGSN
update bearers with the S-GW/P-GW.
NOTE
5. After the handover, the UE may initiate a CS call establishment procedure with an LAU
or combined RAU/LAU procedure in the GERAN.
6. The follow-up procedures are performed for the PS handover. These procedures include
data forwarding, path switching, and RAU, which are performed together with step 5.

CSFB to GERAN based on PS handover for mobile-originated calls.

eRAN
12.2.3 CSFB Based on CCO/NACC

During CSFB based on CCO/NACC, the eNodeB receives a CS Fallback Indicator from the
MME, and then it sends a Mobility From EUTRA Command message to the UE over the Uu
interface. The message contains information about the operating frequency, ID, and system
information of a target GERAN cell. The UE searches for a target cell based on the
information it received, and then it performs initial access to the cell to initiate a CS service. It
then initiates a CS service in the GERAN.
Call procedure
Figure 12-10 shows the procedure for CSFB to GERAN based on CCO/NACC for mobile-
originated calls.
Figure 12-10 CSFB to GERAN based on CCO/NACC for mobile-originated calls
service.
eNodeB.
eNodeB.
4. The eNodeB sends a Mobility From EUTRA Command message over the Uu interface
to indicate the operating frequency and ID of the target GERAN cell. If the source cell
has the system information of the target cell, the system information is also carried in the
message.

eRAN
NOTE
5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the
target cell.
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are
suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
8. The eNodeB initiates an S1-based UE context release procedure.

CSFB to GERAN based on CCO/NACC for mobile-originated calls.
12.2.4 CSFB Based on Redirection

During CSFB based on redirection, the eNodeB receives a CS Fallback Indicator, and then it
information about a target GERAN frequency, reducing the time for the UE to search for a
target network. After selecting the GERAN, the UE acquires the system information of a
GERAN cell. Then, the UE performs initial access to the cell to initiate a CS service. For the
GERAN, the UE is an initially accessing user.
CSFB Procedure for Mobile-Originated Calls

Figure 12-11 shows the procedure for CSFB to GERAN based on redirection for mobile-
originated calls.

eRAN
Figure 12-11 CSFB to GERAN based on redirection for mobile-originated calls
The procedure is described as follows:
1. The UE sends the MME a NAS message Extended service request to initiate a CS
service.
eNodeB.
3. The eNodeB determines whether to perform blind handover based on the UE
redirection. The message contains information about a target GERAN frequency. Then,
the eNodeB initiates an S1 UE context release procedure.
NOTE
the target cell.
6. If the GERAN or UE does not support DTM, the ongoing PS services of the UE are
suspended.

the MME over the SGs interface. Then, the MME or eNodeB initiates a paging procedure for

eRAN
the UE. The paging procedure is similar to that for UTRAN described in 12.1.2 CSFB Based
on PS Handover. The subsequent steps are the same as the steps in the procedure for CSFB
to GERAN based on redirection for mobile-originated calls.
12.2.5 Flash CSFB

During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it
information about a target UTRAN frequency, as well as one or more physical cell identities
and their associated system information. In this way, the UE can quickly access the target
UTRAN without the need to perform the procedure for acquiring system information of the
target UTRAN cell. Then, the UE can directly initiate a CS service in the UTRAN cell. It then
initiates a CS service in the GERAN.
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must
support 3GPP Release 9 or later.
Call procedure
Figure 12-12 shows the procedure for CSFB to GERAN based on flash redirection for
mobile-originated calls.
Figure 12-12 CSFB to GERAN based on flash redirection for mobile-originated calls
service.
eNodeB.

eRAN
3. The eNodeB determines whether to perform a blind redirection based on the UE

redirection. The message contains information about a target GERAN carrier frequency
group, as well as one or more physical cell identities and their associated system
information. Then, the eNodeB initiates an S1 UE context release procedure.
NOTE
Decision and 4.6 Handover Execution. The system information of the target cell is acquired
during the RIM procedure.
5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the
target cell.
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are
suspended.

the MME over the SGs interface. Then, the MME or eNodeB initiates a paging procedure for
the UE. The paging procedure is similar to that for UTRAN described in 12.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.
12.2.6 Ultra-Flash CSFB to GERAN

Ultra-Flash CSFB to GERAN is a Huawei-proprietary procedure. To enable this feature, the
MSC, MME, and eNodeB must all be provided by Huawei and support this feature.
Resources are prepared in advance on the GERAN using the SRVCC, and authentication and
encryption procedures are excluded to reduce delays. The following figures show Ultra-Flash
CSFB to GERAN of mobile-originated calls and mobile-terminated calls, respectively.

eRAN
Figure 12-13 Ultra-flash CSFB to GERAN for mobile-originated calls

eRAN
Figure 12-14 Ultra-flash CSFB to GERAN for mobile-terminated calls
Steps 1 to 3a: The UE initiates voice services (mobile-originated calls and mobile-terminated
calls) on the E-UTRAN. The eNodeB triggers SRVCC to GERAN. The MME and MSC
guarantees the proper procedure through special processing.
Step 3b: The BSC receives an SRVCC request and prepares CS resources.
Step 4: The eNodeB receives the handover command transferred over the core network and
sends it to the UE.
Step 5: The UE is transferred to the GERAN.
Steps 6 to 9: The UE establishes voice services on the GERAN. Signaling is carried on the
TCH, which accelerates the transfer and reduces delays.
As shown in the preceding figures, Ultra-Flash CSFB to GERAN excludes the following
procedures:
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.

eRAN
l IMEI query procedure

The MME has sent the IMEI to the MSC during the preparation for SRVCC. There, the
procedure is not required in the GERAN after SRVCC.
l CS resource setup procedure
The GSM system has prepared CS resources during SRVCC and therefore the UE does
not need to reestablish the CS resource after SRVCC. There, the procedure is not
required in the GERAN after SRVCC.
When the UE completes voice services in the GERAN after the Ultra-Flash CSFB to
GERAN, you can enable the Fast Return to LTE feature on the GERAN side so that the UE
quickly returns to the E-UTRAN. After the UE completes voice services in the GERAN, the
UE carries the LTE frequency information in a Channel Release message and selects a proper
LTE cell to camp on based on the frequency information to accelerate the return to the E-
UTRAN.
When IratMeasCfgTransSwitch is set to ON, the eNodeB filters LTE frequencies supported
by the UE based on the UE capability to obtain a frequency set. During the SRVCC, the
eNodeB sends a Handover Required message containing the frequency set to the BSC of the
target cell and provides reference for the UE to accelerate the return to the E-UTRAN after
the UE completes voice services on the GERAN.
12.2.7 CSFB for SMS

SMS services are unknown to the eNodeB because SMS messages are encapsulated in NAS
messages. During interworking with the GERAN, SMS messages are exchanged between the
MME and the MSC over the SGs interface. Because a UE does not require fallback to the
GERAN to perform an SMS service, the SMS over SGs function can be used in a place
covered only by the E-UTRAN.
As the SMS service is transparent to the eNodeB, the procedure is not described in this
document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
12.2.8 Emergency Call

The CSFB procedure for an emergency call is the same as the CSFB procedure for a normal
mobile-originated voice service. The UE sends an RRC Connection Request message over the
Uu interface or the MME sends an Initial Context Setup Request or UE Context Modification
Request message, which contains an IE to inform the eNodeB of the service type. Emergency
calls take precedence over other services in the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in
the handover restriction list when selecting the target cell.
If redirection is used for CSFB for emergency calls, the Channel Request message that the UE
sends when accessing the GERAN contains the indication of a CS emergency call.
The GERAN will treat this call as a common CS emergency call. For details about admission
and preemption of emergency calls, see Emergency Call.
12.2.9 CSFB for LCS

After a UE initiates an LCS request, the MME performs an attach or combined TAU/LAU
procedure to inform the UE of the LCS capability of the EPS. If the EPS does not support
LCS, the UE falls back to the GERAN to initiate LCS under the control of the EPS. The

eRAN
CSFB procedure is the same as the procedure for CSFB to GERAN for mobile-originated
calls.
If the GERAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the
MSC sends an LCS indicator to the MME over the SGs interface. Then, the MME instructs
the eNodeB to perform CSFB for the UE. The CSFB procedure is the same as the procedure
for CSFB to GERAN for mobile-terminated calls. The UE performs the LCS service after the
fallback to the GERAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272 V10.0.0
and LCS.


CS Fallback (ERAN8.1 04)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS Fallback (ERAN8.1 04)

Uploaded by

Copyright:

Available Formats

eRAN

CS Fallback Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2015-12-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 04 (2015-12-30) Huawei Proprietary and Confidential ii

3.7 RIM Procedure Between E-UTRAN and UTRAN...................................................................................................... 34

Issue 04 (2015-12-30) Huawei Proprietary and Confidential iii

7.1 LOFD-001033 CS Fallback to UTRAN....................................................................................................................... 59

Issue 04 (2015-12-30) Huawei Proprietary and Confidential iv

Issue 04 (2015-12-30) Huawei Proprietary and Confidential v

7.6.5.4 Using the CME to Perform Single Configuration................................................................................................ 123

Issue 04 (2015-12-30) Huawei Proprietary and Confidential vi

7.9.5 Data Preparation and Feature Activation.................................................................................................................160

Issue 04 (2015-12-30) Huawei Proprietary and Confidential vii

7.12.2 Required Information............................................................................................................................................ 188

Issue 04 (2015-12-30) Huawei Proprietary and Confidential viii

12.1.2 CSFB Based on PS Handover............................................................................................................................... 316

Issue 04 (2015-12-30) Huawei Proprietary and Confidential ix

1 About This Document

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 1

eNodeB Type Model

Macro 3900 series eNodeB

1.2 Intended Audience

1.3 Change History

eRAN 8.1 04 (2015-12-30)

Change Change Description Parameter Change Affecte

Feature None None None

Editorial Optimized the descriptions throughout None -

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change Affecte

Feature None None None

Editorial Revised descriptions in this document None -

Change Change Description Parameter Change Affected

Feature Added the measurement-specific None Macro,

Added the random selection Added the Macro,

Editorial None None -

Change Type Change Description Parameter Affected Entity

Feature change Added the UE compatibility Added the Macro, micro,

Editorial None None -

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 3

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

Chang Change Description Parameter Affected

Added the feature LOFD-081283 Ultra-Flash l Added the Macro,

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 4

Chang Change Description Parameter Affected

Added the configuration of the round-robin Added the Macro,

Added SPID-based mobility management. For None Macro,

Ultra-flash CSFB to GERAN uses the DRX- Added the Macro,

Editoria Changed "blind handling" to "blind handover". None -

1.4 Differences Between eNodeB Types

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 5

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 6

l Facilitates voice services for the LTE network.

Figure 2-1 Network architecture for CSFB to UTRAN/GERAN

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 7

Table 2-1 Elements of the network architecture for CSFB to UTRAN/GERAN

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

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

MSC l Supports combined EPS/IMSI attach.

Issue 04 (2015-12-30) Huawei Proprietary and Confidential 8