CSFB

CS Fallback
eRAN3.0
Feature Parameter Description
Issue 02
Date 2013-05-16
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 the 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: [email protected]
eRAN
CS Fallback Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview of CSFB.....................................................................................................................2-1
2.2 Introduction.................................................................................................................................... 2-2
2.3 Benefits ......................................................................................................................................... 2-2
2.4 Network Architecture for CSFB to UTRAN/GERAN ...................................................................... 2-2
2.5 Network Architecture for CSFB to CDMA2000 1xRTT .................................................................. 2-5
3 End-to-End Procedures for CSFB ........................................................................................3-1

3.1 CSFB to UTRAN ........................................................................................................................... 3-1
3.1.1 Combined EPS/IMSI Attach Procedure ................................................................................ 3-1
3.1.2 CSFB Procedures for Mobile-originated Calls and Mobile-terminated Calls ....................... 3-2
3.1.3 CSFB Procedure for SMS .................................................................................................... 3-7
3.1.4 CSFB Procedure for Emergency Calls ................................................................................. 3-7
3.1.5 CSFB Procedure for LCS ..................................................................................................... 3-8
3.1.6 RAN Information Management Procedure ........................................................................... 3-8
3.2 CSFB to GERAN ........................................................................................................................... 3-9
3.2.1 Combined EPS/IMSI Attach Procedure ................................................................................ 3-9
3.2.2 CSFB Procedures for Mobile-originated Calls and Mobile-terminated Calls ....................... 3-9
3.2.3 CSFB Procedure for SMS .................................................................................................. 3-15
3.2.4 CSFB Procedure for Emergency Calls ............................................................................... 3-15
3.2.5 CSFB Procedure for LCS ................................................................................................... 3-15
3.2.6 RAN Information Management Procedure ......................................................................... 3-16
3.3 CSFB to CDMA2000 1xRTT ....................................................................................................... 3-16
3.3.1 Preregistration Procedure................................................................................................... 3-16
3.3.2 CSFB Procedure for Mobile-originated Calls ..................................................................... 3-17
3.3.3 CSFB Procedure for Mobile-terminated Calls .................................................................... 3-18
3.3.4 CSFB Procedure for SMS .................................................................................................. 3-20
3.3.5 CSFB Procedure for Emergency Calls ............................................................................... 3-20
4 CSFB at the eNodeB ................................................................................................................4-1

4.1 Triggering Phase of CSFB ............................................................................................................ 4-2
4.1.1 Choosing Between a Blind Handover and a Measurement-based Handover...................... 4-2
4.1.2 Selecting Frequencies to Measure or a Target Cell (Without an LAI) .................................. 4-2
4.1.3 Selecting Frequencies to Measure or a Target Cell (With an LAI) ....................................... 4-3
4.2 Measurement Phase of CSFB ...................................................................................................... 4-4
4.2.1 Measurement Configuration ................................................................................................. 4-4
4.2.2 Measurement Reporting ....................................................................................................... 4-4
Issue 02 (2013-05-16) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
4.3 Decision Phase of CSFB ............................................................................................................... 4-5

4.4 Execution Phase of CSFB ............................................................................................................. 4-5
4.5 CSFB Exception Handling ............................................................................................................. 4-8
5 Related Features .......................................................................................................................5-1

5.1 Features Related to LOFD-001033 CS Fallback to UTRAN ......................................................... 5-1
5.2 Features Related to LOFD-001034 CS Fallback to GERAN ........................................................ 5-1
5.3 Features Related to LOFD-001035 CS Fallback to CDMA2000 1xRTT ....................................... 5-1
5.4 Features Related to LOFD-001052 Flash CS Fallback to UTRAN ............................................... 5-2
5.5 Features Related to LOFD-001053 Flash CS Fallback to GERAN .............................................. 5-2
5.6 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN ........................................... 5-3
5.7 Features Related to LOFD-001069 CS Fallback with LAI to GERAN .......................................... 5-3
6 Network Impact..........................................................................................................................6-1
6.1 LOFD-001033 CS Fallback to UTRAN ......................................................................................... 6-1
6.2 LOFD-001034 CS Fallback to GERAN ......................................................................................... 6-1
6.3 LOFD-001034 CS Fallback to GERAN ......................................................................................... 6-2
6.4 LOFD-001052 Flash CS Fallback to UTRAN ................................................................................ 6-2
6.5 LOFD-001053 Flash CS Fallback to GERAN ............................................................................... 6-3
6.6 LOFD-001068 CS Fallback with LAI to UTRAN ............................................................................ 6-3
6.7 LOFD-001069 CS Fallback with LAI to GERAN ........................................................................... 6-3
7 Engineering Guidelines ...........................................................................................................7-1

7.1 Deploying CSFB to UTRAN .......................................................................................................... 7-1
7.1.1 When to Use CSFB to UTRAN ............................................................................................. 7-1
7.1.2 Information to Be collected ................................................................................................... 7-1
7.1.3 Deployment Requirements ................................................................................................... 7-2
7.1.4 Data Preparation................................................................................................................... 7-2
7.1.5 Precautions ........................................................................................................................... 7-4
7.1.6 Initial Configuration ............................................................................................................... 7-4
7.1.7 Activation Observation .......................................................................................................... 7-5
7.1.8 Deactivation .......................................................................................................................... 7-9
7.2 Deploying CSFB to GERAN .......................................................................................................... 7-9
7.2.1 When to Use CSFB to GERAN ............................................................................................ 7-9
7.2.2 Information to Be collected ................................................................................................. 7-10
7.2.3 Deployment Requirements ................................................................................................. 7-10
7.2.4 Data Preparation................................................................................................................. 7-11
7.2.5 Precautions ......................................................................................................................... 7-13
7.2.6 Initial Configuration ............................................................................................................. 7-13
7.2.7 Activation Observation ........................................................................................................ 7-15
7.2.8 Deactivation ........................................................................................................................ 7-15
7.3 Deploying CSFB to CDMA2000 1xRTT ...................................................................................... 7-15
7.3.1 When to Use CSFB to CDMA2000 1xRTT ......................................................................... 7-15
Issue 02 (2013-05-16) Huawei Proprietary and Confidential ii

eRAN

7.3.5 Precautions ......................................................................................................................... 7-18
7.3.8 Deactivation ........................................................................................................................ 7-20
7.4 Deploying Flash CSFB to UTRAN .............................................................................................. 7-20
7.4.1 When to Use Flash CSFB to UTRAN ................................................................................. 7-20
7.4.5 Precautions ......................................................................................................................... 7-24
7.4.8 Deactivation ........................................................................................................................ 7-26
7.5 Deploying Flash CSFB to GERAN .............................................................................................. 7-26
7.5.1 When to Use Flash CSFB to GERAN ................................................................................ 7-26
7.5.5 Precautions ......................................................................................................................... 7-30
7.5.8 Deactivation ........................................................................................................................ 7-32
7.6 Deploying CSFB with LAI to UTRAN .......................................................................................... 7-32
7.6.1 When to Use CSFB with LAI to UTRAN ............................................................................. 7-32
7.6.5 Precautions ......................................................................................................................... 7-34
7.6.8 Deactivation ........................................................................................................................ 7-35
7.7 Deploying CSFB with LAI to GERAN .......................................................................................... 7-35
7.7.1 When to Use CSFB with LAI to GERAN ............................................................................ 7-35
7.7.5 Precautions ......................................................................................................................... 7-36
7.7.8 Deactivation ........................................................................................................................ 7-37
Issue 02 (2013-05-16) Huawei Proprietary and Confidential iii

eRAN
7.8 Performance Optimization ........................................................................................................... 7-37

7.8.1 Monitoring ........................................................................................................................... 7-37
7.8.2 Parameter Optimization ...................................................................................................... 7-37
7.8.3 EBC Description ................................................................................................................. 7-41
7.9 Troubleshooting ........................................................................................................................... 7-42
7.9.1 Fault 1 ................................................................................................................................. 7-42
7.9.2 Fault 2 ................................................................................................................................. 7-43
7.9.3 Fault 3 ................................................................................................................................. 7-43
7.9.4 CS Fallback with LAI to UTRAN ......................................................................................... 7-44
7.9.5 CS Fallback with LAI to GERAN ........................................................................................ 7-44
8 Parameters..................................................................................................................................8-1
9 Counters ......................................................................................................................................9-1
10 Glossary ..................................................................................................................................10-1
11 Reference Documents .........................................................................................................11-1
Issue 02 (2013-05-16) Huawei Proprietary and Confidential iv

eRAN
CS Fallback 1 Introduction
1 Introduction
1.1 Scope
This document describes the principles and procedures of Circuit Switched Fallback (CSFB), and it
illustrates the functions provided by Huawei E-UTRAN NodeBs (eNodeBs) during CSFB procedures. It
also provides engineering guidelines for setting the essential parameters related to CSFB.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
1.2 Intended Audience

This document is intended for:
 Personnel who need to understand CSFB
 Personnel who work with Huawei Long Term Evolution (LTE) products
1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change: refers to a change in the CSFB feature of a specific product version.
 Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version.
Document Issues
The document issues are as follows:
 02 (2013-05-16)
 01 (2013-04-12)
 Draft B (2012-11-02)
 Draft A (2012-06-29)
02 (2013-05-16)
Compared with 01 (2013-04-12), 02 (2013-05-16) includes the following changes.
Change Type Change Description Parameter Change

Feature change None None
Editorial change Added the description of End-to-end CSFB delay. For None
details, see section 7.8 "Performance Optimization."
01 (2013-04-12)
This is the official release.
Compared with draft B (2012-11-02) of eRAN3.0, 01 (2013-04-12) of eRAN3.0 incorporates no changes.
Issue 02 (2013-05-16) Huawei Proprietary and Confidential 1-1

eRAN
CS Fallback 1 Introduction
Draft B (2012-11-02)
Compared with draft A (2012-06-29), draft B (2012-11-02) includes the following changes.
Change Type Change Description Parameter Change

Feature change Modified the handling methods for CSFB exceptions. For None
details, see section 4.5 "CSFB Exception Handling."
Editorial change  Modified some descriptions of initial configuration in None
chapter 7 "Engineering Guidelines."
 Added flowcharts of CSFB execution. For details, see
section 4.4 "Execution Phase of CSFB."
 Deleted the license control item IDs.
Draft A (2012-06-29)
This is a draft.

eRAN
CS Fallback 2 Overview of CSFB
2 Overview of CSFB
This chapter illustrates the network architectures for CSFB to UTRAN/GERAN/CDMA2000 1xRTT and
describes the function of each network element (NE).
In the early phase of EPS construction, operators who own a mature UTRAN, GERAN, or CDMA2000
1xRTT network can protect their investments in legacy CS networks and reduce their investments in the
EPS by using legacy CS networks to provide CS services and using the EPS to provide PS services.
From a technological perspective, CSFB and VoIP over IMS are the two standard solutions to provide
CS 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 CS service access
before mature commercial use of IMS.
NOTE
 EPS: evolved packet system
 UTRAN: universal terrestrial radio access network
 GERAN: GSM/EDGE radio access network
 CDMA2000 1xRTT: CDMA2000 1x Radio Transmission Technology
 CS: circuit switched
 PS: packet switched
 VoIP: voice over IP
 IMS: IP multimedia subsystem
 UE: user equipment
CSFB enables E-UTRAN UEs to fall back to CS networks to receive CS services, better utilizing legacy
CS networks. Examples of CS services include voice services and location services (LCS). 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.
CSFB applies to scenarios in which the coverage area of the UTRAN/GERAN/CDMA2000 1xRTT
network is the same as or includes that of the E-UTRAN. It requires a simpler network architecture
compared with VoIP over IMS.
To implement CSFB, all mobile switching centers (MSCs) that serve overlapping areas with the
E-UTRAN coverage must be upgraded to support functions involving the SGs interface. The SGs
interface is between an MSC and a mobility management entity (MME). 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 short message service (SMS). If an MSC pool is used in
the legacy CS network, the upgrade of one or several MSCs in the pool is sufficient.
The optional features addressed in this document are as follows:
 LOFD-001033 CS Fallback to UTRAN
 LOFD-001034 CS Fallback to GERAN
 LOFD-001035 CS Fallback to CDMA2000 1xRTT
 LOFD-001052 Flash CS Fallback to UTRAN
 LOFD-001053 Flash CS Fallback to GERAN
 LOFD-001068 CS Fallback with LAI to UTRAN
 LOFD-001069 CS Fallback with LAI to GERAN
Table 2-1 lists the optional features addressed in this document and the corresponding chapters
describing related principles and algorithms.

eRAN
Table 2-1 Optional features related to CSFB and corresponding chapters

Feature Its Basic Principles Its Algorithm Details Are Described in...
Are Described in...
LOFD-001033 CS Fallback 3.1 "CSFB to UTRAN" 4 "CSFB at the eNodeB"
to UTRAN
LOFD-001034 CS Fallback 3.2 "CSFB to GERAN" 4 "CSFB at the eNodeB"
to GERAN
LOFD-001035 CS Fallback 3.3 "CSFB to CDMA2000 4 "CSFB at the eNodeB"
to CDMA2000 1xRTT 1xRTT"
LOFD-001052 Flash CS 3.1.6 "RAN Information 4 "CSFB at the eNodeB"
Fallback to UTRAN Management Procedure"
LOFD-001053 Flash CS 3.2.6 "RAN Information 4 "CSFB at the eNodeB"
Fallback to GERAN Management Procedure"
LOFD-001068 CS 3.1 "CSFB to UTRAN" 4.1.3 "Selecting Frequencies to Measure or
Fallback with LAI to UTRAN a Target Cell (With an LAI)"
LOFD-001069 CS 3.2 "CSFB to GERAN" 4.1.3 "Selecting Frequencies to Measure or
Fallback with LAI to GERAN a Target Cell (With an LAI)"
2.2 Introduction
As specified in 3GPP TS 23.272 V8.5.0, CSFB is a solution that enables a UE to register with both an
EPS network and a legacy CS network. When such a UE initiates a voice service, the EPS network
instructs the UE to fall back to the legacy CS network before performing the service.
When a UE sends or receives an SMS message, the message is transmitted between the EPS network
and the legacy CS network without requiring CSFB. This is achieved by SMS over SGs.
2.3 Benefits
CSFB brings the following benefits:
 Facilitates voice services for the LTE network.
 Facilitates SMS and LCS services for the LTE network.
 Helps operators reduce costs by reusing legacy CS networks and not requiring IMS network
deployment.
2.4 Network Architecture for CSFB to UTRAN/GERAN

To implement CSFB to UTRAN/GERAN, an SGs interface is required between the MME and the MSC
server. Figure 2-2 shows the network architecture for CSFB to UTRAN/GERAN.

eRAN
Figure 2-1 Network architecture for CSFB to UTRAN/GERAN
SGSN: serving GPRS support node
After a UE is powered on in the E-UTRAN as shown in Table 2-2, it initiates a combined EPS/IMSI attach
procedure. Then, the MME performs a UE location update over the SGs interface so that the core
network of the UTRAN or GERAN learns about the UE location.
If a UE is camping on an E-UTRAN cell, it periodically initiates a combined TAU/LAU procedure, which
allows for simultaneous UE location updates both in the MME and in the core network of the UTRAN or
GERAN.
The combined EPS/IMSI attach and combined TAU/LAU procedures are performed by exchanging
non-access stratum (NAS) messages. Therefore, they are transparent to the E-UTRAN (the E-UTRAN is
unaware of them). When a mobile-originated or mobile-terminated CS service is initiated, the
E-UTRAN works with other elements in the networks to perform CSFB.
Table 2-2 describes the elements of the network architecture for CSFB to UTRAN/GERAN.
Table 2-2 Elements of the network architecture for CSFB to UTRAN/GERAN
Element Function
SGs interface  Acts as an interface between the MME and the MSC server.
 Assists mobility management and paging between the EPS and the CS network.
 Transmits SMS messages.
 Transmits messages related to combined attach and combined TAU/LAU.
UE  Is capable of accessing the EPS and accessing the UTRAN, GERAN, or both.
 Supports combined EPS/IMSI attach, combined EPS/IMSI detach, and combined
TAU/LAU.
 Supports CSFB mechanisms, such as PS redirection and PS handover.
NOTE
 IMSI is short for international mobile subscriber identity.
 CSFB-capable UEs must support SMS over SGs, but UEs that support SMS over SGs are not
necessarily CSFB-capable.

eRAN
Element Function
MME  Supports the SGs interface to the MSC.
 Selects the location area identity (LAI) based on the tracking area identity (TAI) of
the serving cell.
 Supports the ability to forward paging messages delivered by the MSC.
 Performs public land mobile network (PLMN) selection and reselection.
 Supports combined EPS/IMSI attach, combined EPS/IMSI detach, and combined
TAU/LAU.
 Routes CS signaling.
 Supports SMS over SGs.
 Supports RIM if flash CSFB or CCO with NACC is used as the CSFB mechanism.
NOTE
 CCO: cell change order
 NACC: network assisted cell change
 RIM: RAN information management
MSC  Supports combined EPS/IMSI attach.

 Supports SMS over SGs.
 Forwards paging messages transmitted through the SGs interface.
E-UTRAN  Forwards paging messages related to CSFB.
 Selects target cells for CSFB for E-UTRAN UEs.
 Supports one or more of the following functions:
− PS redirection to UTRAN or GERAN, if PS redirection is used as the CSFB
mechanism
− PS handover to UTRAN or GERAN, if PS handover is 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/GERAN Supports one or more of the following functions:
 Incoming handovers from the E-UTRAN, if PS handover is used as the CSFB
mechanism
 RIM for delivering the system information of GERAN cells to eNodeBs, if NACC is
used as the CSFB mechanism
 RIM for delivering the system information of UTRAN or GERAN cells to eNodeBs,
in addition to PS redirection, if flash CSFB is 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.

eRAN
Element Function
SGSN  Does not activate Idle Mode Signaling Reduction (ISR) during the combined
RAU/LAU procedure initiated by the UE. RAU is short for routing area update.
 Supports RIM if flash CSFB or CCO with NACC is used as the CSFB mechanism.
NOTE
ISR is a mechanism for reducing the inter-RAT cell reselection signaling of a UE in idle mode.
RAT is short for radio access technology. For details about ISR, see Annex J in 3GPP TS 23.401
V9.2.0.
2.5 Network Architecture for CSFB to CDMA2000 1xRTT

Figure 2-2 shows the network architecture for CSFB to CDMA2000 1xRTT. This CSFB function is
implemented based on the S102 interface between the MME and the 1xCS IWS. The S102 interface
provides a tunnel between the MME and the 1xCS IWS to relay 3GPP2 1xCS signaling. 1xCS IWS is
short for Circuit Switched Fallback Interworking Solution Function for 3GPP2 1xCS.
Figure 2-2 Network architecture for CSFB to CDMA2000 1xRTT
S-GW: serving gateway P-GW: PDN gateway
After a UE is powered on and attached to the evolved packet core (EPC), as shown in Figure 2-2, the
MME is informed of the UE's CSFB capability. Then, the serving E-UTRAN cell broadcasts system
information to indicate whether the E-UTRAN supports CSFB to CDMA2000 1xRTT. If the E-UTRAN
supports CSFB to CDMA2000 1xRTT, the UE initiates preregistration with the CDMA2000 1xCS domain
through the E-UTRAN and MME. After the preregistration, the CDMA2000 1xCS domain is informed of
the UE location. When a mobile-originated or mobile-terminated CS service is initiated, the
E-UTRAN works with other elements in the networks to perform CSFB.
Table 2-3 describes the elements of the network architecture for CSFB to CDMA2000 1xRTT.

eRAN
Table 2-3 Elements of the network architecture for CSFB to CDMA2000 1xRTT
Element Function
S102 interface  Acts as an interface between the MME and the 1xCS IWS.
 Provides a tunnel to carry 1xCS signaling.
UE  Is capable of accessing the EPS and CDMA2000 1xCS domain.
 Preregisters with the CDMA2000 1xCS domain while camping on an E-UTRAN cell
and reregisters with the CDMA2000 1xCS domain while moving.
 Supports CSFB mechanisms.
 Supports mobile-originated and mobile-terminated SMS over S102.
MME  Sends and receives 1xCS signaling over the S102 interface, buffers data, and
performs tunnel reestablishment.
 Redirects inter-MME S102 tunnels in the case of MME relocation.
E-UTRAN  Broadcasts system information that contains CDMA2000 1xCS domain information
to trigger UEs' preregistration with the CDMA2000 1xCS domain.
 Transmits 1xCS signaling.
 Transmits paging messages from the 1xCS domain.

eRAN
CS Fallback 3 End-to-End Procedures for CSFB
3 End-to-End Procedures for CSFB

This chapter describes the functions that a Huawei eNodeB performs during end-to-end procedures for
CSFB, including the following:
 Combined EPS/IMSI attach
 Preregistration
 CSFB procedure for mobile-originated calls
 CSFB procedure for mobile-terminated calls
 CSFB procedure for SMS
 CSFB procedure for emergency calls
 CSFB procedure for LCS
Regarding the capabilities of UEs and networks, Huawei provides the following mechanisms for
eNodeBs to perform CSFB to UTRAN, GERAN, or CDMA2000 1xRTT for mobile-originated calls and
mobile-terminated calls:
 PS redirection
 PS handover
 CCO with or without NACC (CCO/NACC)
3.1 CSFB to UTRAN

For details about engineering guidelines for CSFB to UTRAN, see section 7.1 "Deploying CSFB to
UTRAN."
3.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 3-1.
Figure 3-1 Combined EPS/IMSI attach procedure
HSS: home subscriber server VLR: visitor location register

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

1. The UE sends an 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 CS 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 services are supported.
3.1.2 CSFB Procedures for Mobile-originated Calls and

Mobile-terminated Calls
Based on the capabilities of UEs and networks, the following mechanisms are available for an eNodeB
to perform CSFB to UTRAN:
 CSFB based on PS handover
 CSFB based on PS redirection
 Flash CSFB
Table 3-1 lists the advantages and disadvantages of the preceding mechanisms in terms of impacts on
the UEs, impacts on the networks, CS service access delay, and PS service interruption time. The
preceding mechanisms can be based on the measurement or blind mode, and they are compared here
based on the same mode.
Table 3-1 Comparison of fallback mechanisms for CSFB to UTRAN
Fallback Mechanism Impact on the Impact on the CS Service PS Service
Networks UEs Access Delay Interruption Time
CSFB based on PS Complex Complex Short Short
handover
CSFB based on PS Simple Simple Long Long
redirection
Flash CSFB Medium Medium Short Medium

eRAN
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.
CSFB Procedure for Mobile-originated Calls
This section describes the procedure for CSFB to UTRAN based on PS handover for mobile-originated
calls, as shown in Figure 3-2.
Figure 3-2 CSFB to UTRAN based on PS handover for mobile-originated calls
RNC: radio network controller
The procedure is described as follows:

1. The UE sends the MME an NAS message Extended Service Request to initiate a CS service.
2. The MME sends an S1-AP Request message to instruct the eNodeB to initiate a CSFB procedure. If
the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the UE capabilities,
parameters settings, and algorithm policies. For details, see section 4.1.1 "Choosing Between a Blind
Handover and a Measurement-based Handover."
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
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details, see chapter 4 "CSFB
at the eNodeB."

eRAN
5. After the handover, the UE may initiate a CS call establishment procedure with an LAU or combined
RAU/LAU procedure in the UTRAN.
6. The follow-up procedures are performed for the PS handover. These procedures include data
forwarding, path switching, and RAU. This step is performed together with step 5.
NOTE
For details about the PS handover procedure, see Mobility Management in Connected Mode Feature
Parameter Description and section 5.5.2 in 3GPP TS 23.401 V9.2.0.
CSFB Procedure for Mobile-terminated Calls

This section describes the procedure for CSFB to UTRAN based on PS handover for mobile-terminated
Figure 3-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.

eRAN
CSFB Based on PS Redirection

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.
This section describes the procedure for CSFB to UTRAN based on PS redirection for mobile-originated
Figure 3-4 CSFB to UTRAN based on PS redirection for mobile-originated calls

4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a redirection.
The message contains information about a target UTRAN frequency. Then, the eNodeB initiates an
S1 UE context release procedure.
NOTE
at the eNodeB."

eRAN
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. Then, the MME or the eNodeB initiates a paging procedure for the UE, as shown
in Figure 3-3. The subsequent steps are the same as the steps in the procedure for CSFB to UTRAN
based on PS redirection for mobile-originated calls.
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.
NOTE
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must support 3GPP Release 9 or
later.

This section describes the procedure for flash CSFB to UTRAN for mobile-originated calls, as shown in
Figure 3-5.
Figure 3-5 Flash CSFB to UTRAN for mobile-originated calls


eRAN
The message contains information about a target UTRAN frequency, as well as one or more physical
cell identities and their associated system information. Then, the eNodeB initiates an S1 UE context
release procedure.
NOTE
at the eNodeB."
The system information of the target cell is acquired during the RIM procedure. For details, see section 3.1.6 "RAN
Information Management Procedure."
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.
in Figure 3-3. The subsequent steps are the same as the steps in the procedure for flash CSFB to
UTRAN for mobile-originated calls.
3.1.3 CSFB Procedure 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.
3.1.4 CSFB Procedure for Emergency Calls

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 S1-AP message, which contains an IE to inform the eNodeB of the
service type. Emergency calls take precedence over other services in the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in the
handover restriction list when selecting the target cell. The eNodeB sends the RNC a handover
request with the IE CSFB high priority in the IE Source to Target Transparent Container. This request
informs the RNC that a CSFB procedure is required for an emergency call. Upon receiving the
information, the RNC preferentially processes this call when using related algorithms such as admission
control.
If redirection is used for CSFB for emergency calls, the RRC Connection Request message that the UE
sends when accessing the UTRAN contains the indication of an 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 Feature
Parameter Description.

eRAN
3.1.5 CSFB Procedure 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
Feature Parameter Description.
3.1.6 RAN Information Management Procedure

The RIM procedure, as shown in Figure 3-6, exchanges information between E-UTRAN and
GERAN/UTRAN through the core networks. The procedure involves the eNodeB, MME, SGSN, and
RNC/base station controller (BSC). Among these NEs, the MME and the SGSN transfer but do not
resolve information.
Figure 3-6 RIM procedure
The RIM procedure supports two information exchange modes: Single Report and Multiple Report. In
Single Report mode, the source sends a request, and then the target responds with a single report. In
Multiple Report mode, the target responds with a report after receiving a request from the source, and it
also sends a report to the source each time the system information changes. For details, see section 8c
in 3GPP TS 48.018.
The Huawei eNodeB supports the two information exchange modes, and it acquires the system
information of UTRAN cells during the RIM procedure. The Multiple Report mode is enabled or disabled
by setting the ENodeBAlgoSwitch.RimSwitch parameter, while the Single Report mode is not
configurable. The RIM procedure and parameter settings are described as follows:
 If a neighboring UTRAN cell supports the Multiple Report mode and UTRAN_RIM_SWITCH under the
ENodeBAlgoSwitch.RimSwitch parameter is turned on, the RIM procedure in Multiple Report mode
is performed as follows: After an external UTRAN cell corresponding to the neighboring UTRAN cell is
configured, the eNodeB sends a request for system information to the neighboring UTRAN cell. After
the neighboring UTRAN cell receives the request or the system information changes, this cell sends
the system information to the eNodeB.
NOTE
Whether an RIM procedure in Multiple Report mode can be triggered is based on the settings of the RIM switch and
external UTRAN cells. For example, the RIM procedure cannot be triggered if the RIM switch is turned on but no external
UTRAN cell is configured. If an external UTRAN cell has been configured, an RIM procedure is triggered each time the
RIM switch is turned on.

eRAN
 If flash CSFB to UTRAN is enabled and UTRAN_RIM_SWITCH under the

ENodeBAlgoSwitch.RimSwitch parameter is turned off, the eNodeB obtains the system information
of the neighboring UTRAN cells by performing an RIM procedure in Single Report mode.
3.2 CSFB to GERAN

For details about engineering guidelines for CSFB to GERAN, see section 7.2 "Deploying CSFB to
GERAN."
3.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 section 3.1.1 "Combined EPS/IMSI Attach Procedure."
3.2.2 CSFB Procedures for Mobile-originated Calls and

Mobile-terminated Calls
Based on the capabilities of UEs and networks, the following mechanisms are available for an eNodeB
to perform CSFB to GERAN:
 CSFB based on PS redirection
 CSFB based on PS handover
 CSFB based on CCO/NACC
 Flash CSFB
Table 3-2 lists the advantages and disadvantages of the preceding mechanisms in terms of impacts on
the UEs, impacts on the networks, CS service access delay, and PS service interruption time.
Table 3-2 Comparison of fallback mechanisms for CSFB to GERAN
Fallback Mechanism Impact on the Impact on the CS Service PS Service
Networks UEs Access Delay Interruption Time
CSFB based on PS Simple Simple Long Long
redirection
CSFB based on PS Complex Complex Short Short
handover
CSFB based on Medium Medium Medium Medium
CCO/NACC
Flash CSFB Medium Medium Short Medium
CSFB Based on PS Redirection

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 GERAN carrier frequency group, 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 a user that initially accesses
the network.

eRAN
This section describes the procedure for CSFB to GERAN based on PS redirection for mobile-originated
Figure 3-7 CSFB to GERAN based on PS redirection for mobile-originated calls

The message contains information about a target GERAN carrier frequency group. Then, the
eNodeB initiates an S1 UE context release procedure.
NOTE
at the eNodeB."
6. If the UE or GERAN does not support dual transfer mode (DTM), in which CS and PS services run
simultaneously, the ongoing PS services of the UE are suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.

eRAN
in Figure 3-3. The subsequent steps are the same as the steps in the procedure for CSFB to GERAN
based on PS redirection for mobile-originated calls.
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 some
GERAN-supporting UEs do not support DTM, the ongoing PS services must be suspended before the
CS services can be established.
This section describes the procedure for CSFB to GERAN based on PS handover for mobile-originated
Figure 3-8 CSFB to GERAN based on PS handover for mobile-originated calls


eRAN
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 DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are suspended.
Meanwhile, the SGSN updates the bearers towards the S-GW/P-GW.
NOTE
at the eNodeB."
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. This step is performed together with step 5.
based on PS handover for mobile-originated calls.
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. If the GERAN or some GERAN-supporting UEs do not support DTM,
the ongoing PS services must be suspended before the CS services can be established.
This section describes the procedure for CSFB to GERAN based on CCO/NACC for mobile-originated

eRAN
Figure 3-9 CSFB to GERAN based on CCO/NACC for mobile-originated calls

4. The eNodeB sends a Mobility From EUTRA Command message over the Uu interface to indicate the
operating frequency and ID of the target GERAN cell. If the source cell has the system information of
the target cell, the system information is also carried in the message.
NOTE
at the eNodeB."
5. The MME initiates an S1 UE context release procedure.
6. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target cell.
7. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are suspended.

eRAN
based on CCO/NACC for mobile-originated calls.
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
GERAN carrier frequency group, as well as one or more physical cell identities and their associated
system information. 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. If the GERAN or some GERAN-supporting UEs
do not support DTM, the ongoing PS services must be suspended before the CS services can be
established.
NOTE
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must support 3GPP Release 9 or
later.

This section describes the procedure for flash CSFB to GERAN for mobile-originated calls, as shown in
Figure 3-10.
Figure 3-10 Flash CSFB to GERAN for mobile-originated calls


eRAN
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
at the eNodeB."
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are suspended.
in Figure 3-3. The subsequent steps are the same as the steps in the procedure for flash CSFB to
GERAN for mobile-originated calls.

SMS services are unknown to the eNodeB because SMS messages are encapsulated in NAS
messages. During interworking with the GERAN, SMS messages are exchanged between the MME and
the MSC over the SGs interface. Because a UE does not require fallback to the GERAN to perform an
SMS service, the SMS over SGs function can be used in a place covered only by the E-UTRAN.
As the SMS service is transparent to the eNodeB, the procedure is not described in this document. For
details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.

The CSFB procedure for an emergency call is the same as the CSFB procedure for a normal
mobile-originated voice service. The UE sends an RRC Connection Request message over the Uu
interface or the MME sends an S1-AP 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 an 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 Feature
3.2.5 CSFB Procedure for LCS

After a UE initiates an LCS request, the MME performs an attach or combined TAU/LAU procedure to
inform the UE of the LCS capability of the EPS. If the EPS does not support LCS, the UE falls back to the
GERAN to initiate LCS under the control of the EPS. The CSFB procedure is the same as the procedure
for CSFB to GERAN for mobile-originated calls.
If the GERAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the MSC sends an
LCS indicator to the MME over the SGs interface. Then, the MME instructs the eNodeB to perform CSFB

eRAN
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
3.2.6 RAN Information Management Procedure

The RIM procedure for CSFB to GERAN is the same as that for CSFB to UTRAN. For details, see
section 3.1.6 "RAN Information Management Procedure."
The Huawei eNodeB supports two information exchange modes, and it acquires the system information
of GERAN cells during the RIM procedure. The Multiple Report mode is enabled or disabled by setting
the ENodeBAlgoSwitch.RimSwitch parameter, while the Single Report mode is not configurable. The
RIM procedure and parameter settings are described as follows:
 If a neighboring GERAN cell supports the Multiple Report mode and GERAN_RIM_SWITCH under the
ENodeBAlgoSwitch.RimSwitch parameter is turned on, the RIM procedure in Multiple Report mode
is performed as follows: After an external GERAN cell corresponding to the neighboring GERAN cell is
configured, the eNodeB sends a request for system information to the neighboring GERAN cell. After
the neighboring GERAN cell receives the request or the system information changes, this cell sends
the system information to the eNodeB.
NOTE
Whether an RIM procedure in Multiple Report mode can be triggered is based on the settings of the RIM switch and
external GERAN cells. For example, the RIM procedure cannot be triggered if the RIM switch is turned on but no external
GERAN cell is configured. If an external GERAN cell has been configured, an RIM procedure is triggered each time the
RIM switch is turned on.
 If flash CSFB to GERAN or CCO/NACC is enabled but GERAN_RIM_SWITCH under the
ENodeBAlgoSwitch.RimSwitch parameter is turned off, the eNodeB obtains the system information
of the neighboring GERAN cells by performing the RIM procedure in Single Report mode.
3.3 CSFB to CDMA2000 1xRTT

Huawei eNodeBs support CSFB to CDMA2000 1xRTT based on PS redirection.
For details about engineering guidelines for CSFB to CDMA2000 1xRTT, see section 7.3 "Deploying
CSFB to CDMA2000 1xRTT."
3.3.1 Preregistration Procedure

To perform CSFB to CDMA2000 1xRTT from an E-UTRAN cell, a 1xCS CSFB-capable UE must initiate
preregistration with the CDMA2000 1xRTT CS network through the E-UTRAN. However, the UE can
initiate the preregistration only if the E-UTRAN supports CSFB to CDMA2000 1xRTT as indicated in the
system information block type 8 (SIB8) broadcast by eNodeBs. The preregistration procedure is shown
in Figure 3-11.

eRAN
Figure 3-11 Preregistration procedure for CSFB to CDMA2000 1xRTT

1. The UE is attached to the E-UTRAN. For details about the attach procedure, see section 5.3.2 in
3GPP TS 23.401 V9.2.0.
2. After receiving the SIB8, the UE decides to initiate preregistration with the CDMA2000 1xRTT CS
network. Meanwhile, the UE sends a CSFB Parameters Request CDMA2000 message to the
eNodeB to obtain preregistration-related parameters.
3. The UE sends a 1xRTT CS Registration Request message through the E-UTRAN. The eNodeB
transmits the request in a UL S1 cdma2000 Tunnelling message to the MME, with the IE CDMA2000
Sector ID in the message containing the IE CDMA2000 Reference Cell ID. Based on the received
CDMA2000 Reference Cell ID, the MME selects a 1xCS IWS (short for Circuit Switched Fallback
Interworking Solution Function for 3GPP2 1xCS). The MME sends the 1xCS IWS an S102/A21-1x Air
Interface Signaling message containing the IEs IMSI and 1xCS message.
4. The 1xCS IWS performs the preregistration as specified in 3GPP2 A.S0008.
5. The 1xCS IWS responds to the UE with a 1xRTT CS Registration Response message. The message
is carried in the following messages:
− S102 Direct Transfer
− DL S1 cdma2000 Tunnelling
− DL Information Transfer
3.3.2 CSFB Procedure for Mobile-originated Calls

This section describes the procedure for CSFB to CDMA2000 1xRTT for mobile-originated calls, as
shown in Figure 3-12.

eRAN
Figure 3-12 CSFB to CDMA2000 1xRTT for mobile-originated calls

2. The MME sends an S1-AP Request message containing a CS Fallback Indicator, instructing the
eNodeB to initiate a CSFB procedure.
4. The eNodeB sends an RRC Connection Release message that contains the IE redirectedCarrierInfo,
instructing the UE to perform a redirection to the 1xRTT CS domain.
5. The eNodeB sends the MME an S1 UE Context Release Request message containing the IE
Cause with the value of "CS Fallback triggered".
6. The UE initiates a CS call establishment procedure to make a call in the 1xRTT CS domain, as
specified in 3GPP2 A.S0013.
When the CS call is complete, the UE performs a cell reselection to return to the E-UTRAN cell.
3.3.3 CSFB Procedure for Mobile-terminated Calls

This section describes the procedure for CSFB to CDMA2000 1xRTT for mobile-terminated calls, as
shown in Figure 3-13.

eRAN
Figure 3-13 CSFB to CDMA2000 1xRTT for mobile-terminated calls

1. The 1xRTT MSC sends a Paging Request message to the 1xCS IWS. The message also contains
the calling number, if any. Then, the 1xCS IWS transmits the paging request to the MME through the
S102 tunnel. If the UE is in idle mode, the MME sends a network-initiated service request, which
enables the UE to transit to active mode. The MME sends the paging request in DL S1 cdma2000
Tunnelling and DL Information Transfer messages to the UE.
3. The MME sends an S1-AP Request message containing a CS Fallback Indicator, instructing the
eNodeB to initiate a CSFB procedure.
5. The eNodeB sends an RRC Connection Release message that contains the IE redirectedCarrierInfo,
instructing the UE to perform a redirection to the 1xRTT CS domain.

eRAN
6. The eNodeB sends the MME an S1 UE Context Release Request message containing the IE
Cause with the value of "CS Fallback triggered".
7. The UE sends a 1xRTT Paging Response message from the 1xRTT CS domain.
8. The UE initiates a CS call establishment procedure to receive a call in the 1xRTT CS domain, as
specified in 3GPP2 A.S0013.
When the CS call is complete, the UE performs a cell reselection to return to the E-UTRAN cell.

During the CSFB procedure, the SMS messages are exchanged between the UE and the eNodeB over
the Uu interface, between the eNodeB and the MME over the S1 interface, and between the MME and
the 1xCS IWS over the S102 interface. The UE does not require fallback to the CDMA2000 1xRTT
network to perform the SMS service.

If CSFB to CDMA2000 1xRTT is required for an emergency call, the UE sends the MME an NAS
message Extended Service Request containing the IE Service Type, indicating an incoming emergency
call. Then, the MME sends the eNodeB an S1 UE Context Modification Request message containing a
CS Fallback Indicator, indicating that the high-priority emergency call requires CSFB to CDMA2000
1xRTT. Upon receiving the information, the eNodeB preferentially processes this call.

eRAN
CS Fallback 4 CSFB at the eNodeB
4 CSFB at the eNodeB

This chapter describes the CSFB procedure performed by Huawei eNodeB and provides the setting
descriptions for the parameters involved. Figure 4-1 shows the CSFB procedure performed by the
eNodeB.
Figure 4-1 CSFB procedure performed by the eNodeB
The CSFB procedure consists of the following phases:

1. Triggering phase
After receiving a CS Fallback Indicator from the MME, the eNodeB decides whether to perform CSFB
in the form of a blind handover based on the UE capabilities and the setting of the blind handover
switch. Compared with measurement-based handovers, blind handovers have shorter access delays
but a lower handover success rate.
2. Measurement phase
The eNodeB delivers the inter-RAT measurement configuration to the UE, and the UE performs
inter-RAT measurements as instructed.
3. Decision phase
The eNodeB evaluates the measurement results and generates a list of candidate cells.
4. Execution phase
The eNodeB executes CSFB to enable the UE to initiate the CS service in the target cell.

eRAN
NOTE
To simplify statements, "handover" mentioned in this chapter is a generic term for both normal handover and redirection.
4.1 Triggering Phase of CSFB

4.1.1 Choosing Between a Blind Handover and a
Measurement-based Handover
After a UE initiates a CS service in an E-UTRAN cell, the MME sends the eNodeB an S1-AP Request
message that contains a CS Fallback Indicator, notifying the eNodeB that the UE should be transferred
to the target network. The target networks to which CSFB can be performed are specified by the
ENodeBAlgoSwitch.HoAlgoSwitch parameter.
After receiving the CS Fallback Indicator, the eNodeB checks the blind-handover switch setting and UE
capabilities for each RAT and performs accordingly:
 If the BlindHoSwitch check box under the ENodeBAlgoSwitch.HoModeSwitch parameter is
cleared, blind handovers are prohibited. Under this condition, if the UE is capable of measuring an RAT,
the eNodeB delivers the inter-RAT measurement configuration to the UE, instructing the UE to perform
measurements on this RAT.
cleared and the UE is incapable of measuring an RAT, the eNodeB directly performs CSFB in the form
of a blind handover.
selected, the eNodeB directly performs CSFB in the form of a blind handover.
If the PS handover switch is turned on, it is recommended that the blind handover switch be turned off to
increase the CSFB success rate. The UtranPsHoSwitch and GeranPsHoSwitch options under the
ENodeBAlgoSwitch.HoModeSwitch parameter specify whether to enable PS handover to UTRAN and
GERAN, respectively.
4.1.2 Selecting Frequencies to Measure or a Target Cell (Without an

LAI)
If the eNodeB has not received any LAIs from the MME, it performs blind handovers and
measurement-based handovers differently.
In a Blind Handover
The eNodeB selects a target cell for the blind handover by taking both the following priorities into
consideration: the blind-handover priority of the target RAT and the blind-handover priority of the
specified cell. The eNodeB selects an RAT with the highest priority first and then selects a cell with the
highest priority in this RAT. If CSFB is triggered for an emergency call, an LCS-supporting RAT takes
precedence over a non-LCS-supporting RAT.
− The
priorities of RATs used in blind handovers for CSFB are specified through the
CSFallBackBlindHoCfg.InterRatHighestPri, CSFallBackBlindHoCfg.InterRatSecondPri, and
CSFallBackBlindHoCfg.InterRatLowestPri parameters.
− Theblind-handover priority of an inter-RAT neighboring cell is specified through the
UtranNCell.BlindHoPriority parameter.

eRAN
In a Measurement-based Handover
The eNodeB selects a UE-supported RAT and frequency in the configurations of neighboring
frequencies and neighboring cells, and then includes the information in the measurement configuration
to the UE.
4.1.3 Selecting Frequencies to Measure or a Target Cell (With an

LAI)
If the MME delivers an LAI to the eNodeB, the eNodeB also takes this LAI into account, in addition to the
principles described in the preceding section. This section describes the LAI-based principles.
In a Blind Handover
The eNodeB checks all inter-RAT neighboring cells of the cell serving the UE and considers the following
three sets (in descending order of priority) based on the LAI:
 Set 1 consists of neighboring cells with the same PLMN ID and LAC as those indicated in the received
LAI.
 Set 2 consists of neighboring cells with the same PLMN ID but different LACs as those indicated in the
received LAI.
 Set 3 consists of neighboring cells located in the same PLMN as the serving PLMN of the UE.
The eNodeB selects the CSFB target cell from the set that has the highest priority among all non-empty
sets. If there are multiple neighboring cells in the highest-priority non-empty set, the eNodeB selects the
neighboring cell with the highest blind handover priority as the CSFB target cell. If the three sets are all
empty, the eNodeB delivers the inter-RAT measurement configuration to the UE. This CSFB will be
performed in the form of a measurement-based handover.
If the neighboring GERAN and UTRAN cells have the same PLMN ID as that indicated in the received
LAI, the eNodeB selects the RAT with the higher blind-handover priority as the target RAT for CSFB.
In a Measurement-based Handover
The eNodeB delivers information about an inter-RAT frequency in the measurement configuration to the
UE if both the following conditions are met:
 The PLMN ID of any inter-RAT neighboring cell on this frequency is the same as the PLMN indicated
in the LAI.
 The UE supports this RAT.
 The UE is capable of measuring this frequency.
Note that only the frequencies that the UE is capable of measuring are delivered in the measurement
configuration.
NOTE
If the eNodeB fails to select the frequencies and target cells according to the LAI delivered by the MME, the eNodeB
proceeds with the procedure as described in section 4.1.2 "Selecting Frequencies to Measure or a Target Cell (Without an
LAI)."

eRAN
4.2 Measurement Phase of CSFB

4.2.1 Measurement Configuration
The measurement configuration procedure and measurement gap configuration for CSFB to
UTRAN/GERAN/CDMA2000 1xRTT are the same as those for inter-RAT handovers. For details, see
Mobility Management in Connected Mode Feature Parameter Description.
4.2.2 Measurement Reporting

CSFB is triggered by event B1, which is reported in event-triggered periodical reporting mode.
The triggering of event B1 indicates that the signal quality is higher than a specified threshold in at least
one neighboring cell. Section 5.5.4.7 in 3GPP TS 36.331 V10.0.0 defines the entering and leaving
conditions of event B1 as follows:
 Entering condition: Mn + Ofn - Hys > Thresh
 Leaving condition: Mn + Ofn + Hys < Thresh
where
 Mn is the measurement result of the neighboring cell.
 Ofn is the frequency-specific offset for the frequency of the neighboring cell. It is contained in the
associated measurement object IE in the measurement configuration.
 Hys is the hysteresis for event B1. The hysteresis values for CSFB to UTRAN, GERAN, and
CDMA2000 1xRTT are contained in the measurement configuration.
 Thresh is the threshold for event B1. The values of Thresh are set based on the measurement
quantities for each RAT, as follows:
− The
received signal code power (RSCP) threshold for CSFB to UTRAN is specified by
CSFallBackHo.CsfbHoUtranB1ThdRscp.
− The Ec/No threshold for CSFB to UTRAN is specified by CSFallBackHo.CsfbHoUtranB1ThdEcn0.
− The
received signal strength indicator (RSSI) threshold for CSFB to GERAN is specified by
CSFallBackHo.CsfbHoGeranB1Thd.
− The
pilot strength threshold for CSFB to CDMA2000 1xRTT is specified by
CSFallBackHo.CsfbHoCdmaB1ThdPS.
If the entering condition of event B1 is continuously met during a period known as time-to-trigger, the UE
reports information about the cells that meet the condition to the eNodeB. The time-to-trigger for event
B1 related to CS fallback to UTRAN/GERAN/CDMA2000 1xRTT is specified by the
CSFallBackHo.CsfbHoUtranTimeToTrig, CSFallBackHo.CsfbHoGeranTimeToTrig, and
CSFallBackHo.CsfbHoCdmaTimeToTrig parameters, respectively.
The following parameters related to event B1 for CSFB are the same as those related to event B1 for
inter-RAT handovers:
 Frequency-specific offset for the frequency of the neighboring cell
 Hysteresis
 Reporting interval
 Maximum number of cells contained in one report
 Number of periodic reports
For details, see Mobility Management in Connected Mode Feature Parameter Description.

eRAN
4.3 Decision Phase of CSFB

In the decision phase of a measurement-based handover for CSFB, the eNodeB checks the
measurement results reported by the UE. Based on the result, the eNodeB determines whether CSFB is
to be initiated and, if so, determines the target cell for the CSFB.
After having received the B1 measurement reports for CSFB, the way in which the eNodeB determines
the target cell for the CSFB varies depending on whether an LAI has been received, as follows:
 If no LAI has been received, the eNodeB generates a list of candidate cells for CSFB based on the
received reports. It selects the cell with the highest signal quality from this list.
If an LAI has been received, the eNodeB considers the candidate cells in sets 1, 2, and 3. It sorts cells in
each list by signal quality, and it selects a target cell from the three lists in descending order of priority.
For details about sets 1, 2, and 3, see section 4.1.3 "Selecting Frequencies to Measure or a Target Cell
(With an LAI)."
4.4 Execution Phase of CSFB

Figure 4-2, Figure 4-3, and Figure 4-4 show the procedures for executing CSFB to GERAN, UTRAN,
and CDMA2000 1xRTT, respectively. Parameters in the figures are specified by switches under the
ENodeBAlgoSwitch.HoModeSwitch parameter. The eNodeB selects a CSFB mechanism based on
both the UE capability and mechanism priority.

eRAN
Figure 4-2 Procedure for executing CSFB to GERAN

eRAN
Figure 4-3 Procedure for executing CSFB to UTRAN

eRAN
Figure 4-4 Procedure for executing CSFB to CDMA2000 1xRTT
4.5 CSFB Exception Handling

The eNodeB starts a timer after receiving the CS Fallback Indicator. If the UE remains in the coverage of
the eNodeB when the timer expires, the eNodeB performs a blind redirection procedure for CSFB.
Currently the timer is set to a fixed value of 4 seconds.
If the eNodeB determines to perform CSFB in the form of a blind handover but the target candidate
cell with the highest blind-handover priority fails the handover preparation, the eNodeB selects another
cell based on the blind-handover priorities in descending order. The eNodeB can initiate handover
attempts to a maximum of eight candidate cells that are configured with blind-handover priorities. If no
candidate cell meets the conditions for a blind handover, the eNodeB performs a blind redirection for
CSFB.

eRAN
CS Fallback 5 Related Features
5 Related Features
5.1 Features Related to LOFD-001033 CS Fallback to UTRAN
Required Features
This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN.
Mutually Exclusive Features

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. To prevent this problem, CSFB to GERAN/UTRAN cannot be enabled together with
CSFB to CDMA2000 1xRTT.
This feature does not work with the following features:
 LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT
Affected Features
None
5.2 Features Related to LOFD-001034 CS Fallback to GERAN

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

Affected Features
None
5.3 Features Related to LOFD-001035 CS Fallback to CDMA2000

1xRTT
Required Features
This feature requires LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000.


eRAN
 LOFD-001033 CS Fallback to UTRAN
 LOFD-001034 CS Fallback to GERAN
Affected Features
None
5.4 Features Related to LOFD-001052 Flash CS Fallback to

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

Affected Features
None
5.5 Features Related to LOFD-001053 Flash CS Fallback to

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

Affected Features
None

eRAN
5.6 Features Related to LOFD-001068 CS Fallback with LAI to

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

Affected Features
None
5.7 Features Related to LOFD-001069 CS Fallback with LAI to

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

Affected Features
None

eRAN
CS Fallback 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.
CSFB mechanisms affect signaling overhead as follows:
 If redirection is used as the CSFB mechanism, no extra signaling message is required for the UTRAN
because each CSFB procedure is equivalent to the initiation of a new CS service. The EPS does not
need to interact with the target network, and the corresponding signaling overhead is negligible.
 If PS handover is used as the CSFB mechanism, extra signaling messages are required from each NE
for the request, preparation, and execution of each handover. However, from the perspective of traffic
statistics, the number of UEs that initiate CS services per second per cell during peak hours is far
below cell capacity. Therefore, signaling overhead caused by PS handovers is low.
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.
Network Performance
CSFB affects the access success rate as follows:
 If redirection is used as the CSFB mechanism, each CSFB procedure is equivalent to the initiation of a
new CS service. Therefore, the access success rate for CSFB UEs is theoretically the same as that for
normal CS UEs in the UTRAN.
 If PS handover is used as the CSFB mechanism, the access success rate for CSFB UEs depends on
the success rate of handovers to the target RAT. Handover-triggered CS service access has a higher
requirement for signal quality compared with normal CS service access. Therefore, the access
success rate for CSFB UEs is a little lower than that for normal CS UEs in the UTRAN.
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
decreases the CSFB delay.
6.2 LOFD-001034 CS Fallback to GERAN

System Capacity
CSFB mechanisms affect signaling overhead as follows:
 If redirection or CCO without NACC is used as the CSFB mechanism, no extra signaling message is
required for the GERAN because each CSFB procedure is equivalent to the initiation of a new CS
service. The EPS does not need to interact with the target network. Therefore, signaling overhead is
negligible.
 If CCO with NACC is used as the CSFB mechanism, extra signaling messages are required only
during eNodeB deployment. Afterward, signaling overhead is negligible because of infrequent system
information updates.

eRAN
 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
 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.
success rate for CSFB UEs is a little lower than that for normal UEs in the GERAN.
6.3 LOFD-001034 CS Fallback to GERAN

System Capacity
Network Performance
 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 CDMA2000.
success rate for CSFB UEs is a little lower than that for normal UEs in the CDMA2000.
6.4 LOFD-001052 Flash CS Fallback to UTRAN

System Capacity
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
Flash CSFB affects the access success rate as follows:
 Each flash CSFB procedure is equivalent to the initiation of a new CS service. Therefore, the access
success rate for CSFB UEs is theoretically the same as that for normal CS UEs in the UTRAN.
 The RRC connection setup success rate may decrease slightly for the UTRAN. The uplink
interference information contained in SIB7 in the UTRAN updates frequently. The RNC cannot update

eRAN
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.
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.
6.5 LOFD-001053 Flash CS Fallback to GERAN

System Capacity
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.6 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.7 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.

eRAN
CS Fallback 7 Engineering Guidelines
7 Engineering Guidelines
7.1 Deploying CSFB to UTRAN
7.1.1 When to Use CSFB to UTRAN
Use LOFD-001033 CS Fallback to UTRAN in the initial phase of LTE network deployment when both of
the following conditions are met:
 The operator owns a mature UTRAN network.
 The LTE network does not provide VoIP services, or UEs in the LTE network do not support VoIP
services.
For policies on whether to use PS handover or PS redirection for CSFB, see Mobility Management in
Connected Mode Feature Parameter Description. If the UTRAN cell and E-UTRAN cell 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 Information to Be collected

 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.
 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.
Table 7-1 Requirements of CSFB to UTRAN for the core networks
NE Description
MME Supports:
 SGs interface to the MSC
 LAI selection based on the TAI of the serving cell
 MSC-initiated paging
 PLMN selection and reselection
 Combined EPS/IMSI attach, combined EPS/IMSI detach, and combined TAU/LAU
 Routing of CS signaling messages
 SMS over SGs
MSC Supports:
 SMS over SGs
 Paging message forwarding over the SGs interface
SGSN Does not activate ISR during the combined RAU/LAU procedure initiated by the UE.
 Collect the following information about the UEs supporting UMTS and LTE on the live network:
− Supported frequency bands
− Whether the UEs support redirection from E-UTRAN to UTRAN

eRAN
− Whether the UEs support PS handover from E-UTRAN to UTRAN

− Whether the UEs support UTRAN measurements
This information is used to configure neighboring UTRAN cells and to determine whether to perform
CSFB based on handover or redirection. For details, see Mobility Management in Connected Mode
7.1.3 Deployment Requirements

Requirements for the Operating Environment
For this feature, the eNodeB must collaborate with the core-network equipment.
 If the core-network equipment is provided by Huawei, the version must be SAE1.2 or later.
 If the core-network equipment is provided by another vendor, check with the vendor whether the
equipment supports this feature.
Requirements for Licenses

Operators must purchase and activate the following license.
Table 7-2 License control item for CSFB to UTRAN
Feature License Control Item Name
LOFD-001033 CS Fallback to UTRAN CS Fall Back to UTRAN
7.1.4 Data Preparation

This section describes generic data and scenario-specific data to be collected. Generic data is
necessary for all scenarios and must always be collected. Scenario-specific data is collected only when
necessary for a specific scenario.
There are three types of data sources:
 Network plan (negotiation required): Parameters are planned by operators and negotiated with the
EPC or peer transmission equipment.
 Network plan (negotiation not required): Parameters are planned and set by operators.
 User-defined: Parameters are set as required by users.
Generic 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 Mobility
Management in Connected Mode Feature Parameter Description.
Collect data for the parameters in the following MOs:
 UtranNFreq: used to configure neighboring UTRAN frequencies.
 UtranExternalCell: used to configure external UTRAN cells. If PS handover is used, the
UtranExternalCell.Rac parameter must be set.
 UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared external UTRAN cell.
This MO is required only if the NodeB providing the external UTRAN cell works in RAN sharing with
common carriers mode and multiple operators share the external UTRAN cell.

eRAN
 UtranNCell: used to configure neighbor relationships with UTRAN cells. If a neighboring UTRAN cell
supports blind handovers according to the network plan, the blind-handover priority of the cell must be
specified by the UtranNCell.BlindHoPriority parameter.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the
handover mode and handover algorithm switches for CSFB to UTRAN.
Parameter Parameter ID Source Setting Description

Name
Handover ENodeBAlgoS Network plan Set this parameter based on the network plan.
Mode switch witch.HoModeS (negotiation not  To activate PS handovers, select the
witch required) UtranPsHoSwitch(UtranPsHoSwitch) check box. If
this check box is not selected, redirection will be used
for CSFB to UTRAN.
 To activate blind handovers, select the
BlindHoSwitch(BlindHoSwitch) check box. A blind
handover to an inter-RAT cell can be performed only if
a blind-handover priority is specified for the inter-RAT
cell. Compared with measurement-based handovers,
blind handovers reduce access delays but cause
lower handover success rates.
Handover ENodeBAlgoS Network plan To activate CSFB to UTRAN, select the
Algo switch witch.HoAlgoS (negotiation not UtranCsfbSwitch(UtranCsfbSwitch) check box.
witch required)
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg MO to set
the blind-handover priorities of different RATs for CSFB.

Name
CN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
Operator CnOperatorId (negotiation parameter specifies the ID of the operator whose
ID not required) RAT blind-handover priorities are to be set.
Highest CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
priority InterRatHighestPri (negotiation parameter is set to UTRAN by default and specifies
InterRat not required) the high-priority RAT to be considered in blind
handovers for CSFB. For CSFB to UTRAN, retain the
default value.
Second CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
priority InterRatSecondPri (negotiation parameter is set to GERAN by default and specifies
InterRat not required) the medium-priority RAT to be considered in blind
handovers for CSFB. Ensure that this parameter is
set to a different value from the
CSFallBackBlindHoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.

eRAN

Name
Lowest CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
priority InterRatLowestPri (negotiation parameter is set to CDMA2000 by default and
InterRat not required) specifies the low-priority RAT to be considered in
blind handovers for CSFB. Ensure that this
parameter is set to a different value from the
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
UTRAN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
LCS UtranLcsCap (negotiation parameter specifies the LCS capability of the
capability not required) UTRAN.
7.1.5 Precautions
None
7.1.6 Initial Configuration

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB in the general configuration window on the Configuration Management
Express (CME) based on the MOs and parameters as described in section 7.1.4 "Data Preparation."
See the M2000 Help for more information about operations in the general configuration window. Press
F1 to launch M2000 Help. Navigate to Introduction to the LTE General Configuration Window and refer
to the generic procedure for setting parameters using the CME graphical user interface (GUI).
To find MOs in the planned area, use either of the following methods:
 In the Object Group pane, find MOs in the navigation tree. This method applies to users who are
familiar with the navigation tree.
 In the Search pane, search an MO. This method applies to users who are unfamiliar with the
navigation tree.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in Table 7-3, and save the parameter settings as a
user-defined template.
The parameters are the same as those described in section 7.1.4 "Data Preparation."
Step 2 Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.

eRAN
Table 7-3 Parameters for CSFB to UTRAN

MO Parameter Group Parameter
Name
UTRANNFREQ UtranNFreq Local cell identity, Downlink UARFCN
UTRANEXTERNA UtranExternalCell Mobile country code, Mobile network code, UTRAN cell
LCELL identity, Downlink UARFCN, RNC identity, Primary
scrambling code, Location area code
UTRANEXTERNA UtranExternalCellPlmn UTRAN cell identity, Mobile country code, Mobile network
LCELLPLMN code, Share mobile country code, Share mobile network
code
UTRANNCELL UtranNCell Local cell identity, Mobile country code, Mobile network
code, UTRAN cell identity, Blind handover priority
ENODEBALGOS ENodeBAlgoSwitch Handover Algo switch, Handover Mode switch
WITCH
CSFALLBACKBLI CSFallBackBlindHoCfg CN Operator ID, Highest priority InterRat, Second priority
NDHOCFG InterRat, Lowest priority InterRat, UTRAN LCS capability
Configuring a Single eNodeB Using MML Commands

The configuration procedure is as follows:
Step 1 Run the following commands to add neighbor relationships with UTRAN cells:
1. ADD UTRANNFREQ
2. ADD UTRANEXTERNALCELL
3. ADD UTRANEXTERNALCELLPLMN
4. ADD UTRANNCELL
For details about parameter settings, see Mobility Management in Connected Mode Feature
Step 2 Run the MOD ENODEBALGOSWITCH command to set the handover mode and handover
algorithm switches for CSFB to UTRAN.
Step 3 Run the MOD CSFALLBACKBLINDHOCFG command to set the blind-handover priorities of
different RATs for CSFB.
----End
7.1.7 Activation Observation

The CSFB procedure for an LCS request initiated by a UE is the same as the CSFB procedure for a
normal mobile-originated call. The CSFB procedure for an LCS request instructed by the MSC towards a
UE camping on an E-UTRAN cell is the same as the CSFB procedure for a normal mobile-terminated
call.
The following uses the CSFB procedure for a mobile-originated call and that for a mobile-terminated call
as an example.

eRAN
The activation observation procedure is as follows:

Step 1 Enable a UE to camp on an E-UTRAN cell and originate a voice call.
Step 2 Enable the UE to camp on the E-UTRAN cell and receive a voice call.
If the calls continue until they are ended, CSFB to UTRAN takes effect. You can observe the signaling
procedures for CSFB to UTRAN.
Figure 7-1 and Figure 7-2 show sample procedures for CSFB to UTRAN for a mobile-originated call and
CSFB to UTRAN for a mobile-terminated call, respectively. In the examples, the UE was in idle mode
before the call and is forced to fall back to the UTRAN using a redirection.
NOTE
The same UE is shown in the left and right sides of the figure. This applies to all figures in the rest of this document. The
messages on the UMTS side are only for reference.

eRAN
Figure 7-1 CSFB to UTRAN for a mobile-originated call

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

eRAN
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. The procedures indicated by dashed lines are optional.
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-3 shows the PS handover procedure.
Figure 7-3 PS handover procedure
----End
7.1.8 Deactivation
Run the MOD ENODEBALGOSWITCH command with the UtranCsfbSwitch(UtranCsfbSwitch) check
box under the ENodeBAlgoSwitch.HoAlgoSwitch parameter cleared.
7.2 Deploying CSFB to GERAN

7.2.1 When to Use CSFB to GERAN
Use LOFD-001034 CS Fallback to GERAN in the initial phase of LTE network deployment when both of
the following conditions are met:
 The operator owns a mature GERAN network.
services.
Connected Mode Feature Parameter Description. If the GERAN cell and E-UTRAN cell cover the same
area, or the GERAN cell provides better coverage than the E-UTRAN cell, use CSFB based on blind

eRAN

 Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and GERAN
 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-4 describes the requirements of CSFB to GERAN for the
core networks.
Table 7-4 Requirements of CSFB to GERAN for the core networks
NE Description
MME Supports:
 SMS over SGs
MSC Supports:
 SMS over SGs
 Collect the following information about the UEs supporting 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


eRAN

Table 7-5 License control item for CSFB to GERAN
LOFD-001034 CS Fallback to GERAN CS Fall Back to GERAN

Generic 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 Mobility Management in
Connected Mode Feature Parameter Description.
 GeranNfreqGroup: used to configure GERAN carrier frequency groups.
 GeranNfreqGroupArfcn: used to configure absolute radio frequency channel numbers (ARFCNs) in
each GERAN carrier frequency group.
 GeranExternalCell: used to configure external GERAN cells. If PS handover is used, the
GeranExternalCell.Rac parameter must be set.
 GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared external GERAN
cell. This MO is required only if the BTS providing the external GERAN cell works in RAN sharing with
common carriers mode and multiple operators share the external GERAN cell.
 GeranNcell: used to configure neighbor relationships with GERAN cells. If a neighboring GERAN cell
specified by the GeranNcell.BlindHoPriority parameter.
handover mode and handover algorithm switches for CSFB to GERAN.

eRAN
Parameter Parameter ID
Source Setting Description
Name
Set this parameter based on the network plan.

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

blind handovers reduce access delays but cause lower
handover success rates.
ENodeBAlgoSwi Network plan
Handover To activate CSFB to GERAN, select the
tch.HoAlgoSwitc (negotiation
Algo switch GeranCsfbSwitch(GeranCsfbSwitch) check box.
h not required)
Name
handovers for CSFB. For CSFB to GERAN, set this
parameter to GERAN.
handovers for CSFB. If the
CSFallBackBlindHoCfg.InterRatHighestPri
parameter is set to GERAN, this parameter cannot
be set to GERAN. Ensure that this parameter is set
to a different value from the
parameters.

eRAN
Name
parameters.
GERAN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
LCS GeranLcsCap (negotiation parameter specifies the LCS capability of the
capability not required) GERAN.
7.2.5 Precautions
None

navigation tree.

----End

eRAN
Table 7-6 Parameters for CSFB to GERAN

MO Parameter Group Parameter
Name
GERANNFREQGROUP GeranNfreqGroup Local cell identity, BCCH group identity,
GERAN version, Starting ARFCN, Band
indicator
GERANNFREQGROUPARFCN GeranNfreqGroupArfcn Local cell identity, BCCH group identity,
GERAN ARFCN
GERANEXTERNALCELL GeranExternalCell Mobile country code, Mobile network code,
GERAN cell identity, Location area code,
Routing area code configure indicator, Band
indicator, GERAN ARFCN, Network colour
code, Base station colour code, DTM
indication
GERANEXTERNALCELLPLMN GeranExternalCellPlmn GERAN cell identity, Location area code,
Mobile country code, Mobile network code,
Share mobile country code, Share mobile
network code
GERANNCELL GeranNcell Local cell identity, Mobile country code,
Mobile network code, Location area code,
GERAN cell identity, Blind handover priority
ENODEBALGOSWITCH ENodeBAlgoSwitch Handover Algo switch, Handover Mode switch
CSFALLBACKBLINDHOCFG CSFallBackBlindHoCfg CN Operator ID, Highest priority InterRat,
Second priority InterRat, Lowest priority
InterRat, GERAN LCS capability

Step 1 Run the following commands to add neighbor relationships with GERAN cells:
1. ADD GERANNFREQGROUP
2. ADD GERANNFREQGROUPARFCN
3. ADD GERANEXTERNALCELL
4. ADD GERANEXTERNALCELLPLMN
5. ADD GERANNCELL
algorithm switches for CSFB to GERAN.
----End

eRAN

If the calls continue until they are ended, CSFB to GERAN takes effect. You can observe the signaling
procedures for CSFB to GERAN, which is the same as that for CSFB to UTRAN described in section
7.1.7 "Activation Observation."
----End
7.2.8 Deactivation
Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch)
check box under the ENodeBAlgoSwitch.HoAlgoSwitch parameter cleared.
7.3 Deploying CSFB to CDMA2000 1xRTT

7.3.1 When to Use CSFB to CDMA2000 1xRTT
Use LOFD-001035 CS Fallback to CDMA2000 1xRTT in the initial phase of LTE network
deployment when both of the following conditions are met:
 The operator owns a mature CDMA2000 1xRTT network.
services.
Connected Mode Feature Parameter Description. If the CDMA2000 1xRTT cell and E-UTRAN cell cover
the same area, or the CDMA2000 1xRTT cell provides better coverage than the E-UTRAN cell, use
CSFB based on blind handover to decrease the CSFB delay.

 Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and
CDMA2000 1xRTT 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.
 Collect the versions and configurations of the NEs in the E-UTRAN, CDMA2000 1xRTT, and core
networks, and ensure that they all support CSFB. Table 7-7 describes the requirements of CSFB to
CDMA2000 1xRTT for the core networks.
Table 7-7 Requirements of CSFB to CDMA2000 1xRTT for the core networks
NE Description
MME Supports:
 1xCS signaling transfer over the S102 interface, data buffering, and tunnel
reestablishment
 Redirection of inter-MME S102 tunnels in the case of MME relocation

eRAN
 Collect the following information about the UEs supporting CDMA2000 and LTE on the live network:
− Whether the UEs support redirection from E-UTRAN to CDMA2000
− Whether the UEs support PS handover from E-UTRAN to CDMA2000
− Whether the UEs support CDMA2000 measurements
This information is used to configure neighboring CDMA2000 cells and to determine whether to perform


Table 7-8 License control item for CSFB to CDMA2000 1xRTT
LOFD-001035 CS Fallback to CDMA2000 1xRTT CS Fall Back to CDMA2000 1xRTT(FDD)

Generic Data
Before configuring CSFB to CDMA2000 1xRTT, collect the data related to neighbor relationships with
CDMA2000 1xRTT cells. This section provides only the information about MOs related to neighboring
CDMA2000 1xRTT cells. For more information about how to collect data for the parameters in these
MOs, see Mobility Management in Connected Mode Feature Parameter Description.
 Cdma2000BandClass: used to configure CDMA2000 band classes
 Cdma2000Nfreq: used to configure CDMA2000 frequencies

eRAN
 Cdma2000ExternalCell: used to configure external CDMA2000 cells

 Cdma2000ExternalCellPlmn: used to configure additional PLMN IDs for each shared external
CDMA2000 cell. This MO is required only if the base station providing the external CDMA2000
cell works in RAN sharing with common carriers mode and multiple operators share the external
CDMA2000 cell.
 Cdma20001XRTTNcell: used to configure neighbor relationships with CDMA2000 1xRTT cells. If a
neighboring CDMA2000 1xRTT cell supports blind handovers according to the network plan, the
blind-handover priority of the cell must be specified by the Cdma20001XRTTNcell.BlindHoPriority
parameter.
handover mode and handover algorithm switches for CSFB to CDMA2000 1xRTT.
Name
Mode switch witch.HoModeS (negotiation not  To activate redirection for CSFB to CDMA2000
witch required) 1xRTT, select the
Cdma1xRttRedirectSwitch(Cdma1xRttRedirectSwi
tch) check box.
blind handovers reduce access delays but cause
lower handover success rates.
Handover ENodeBAlgoS Network plan To activate CSFB to CDMA2000 1xRTT, select the
Algo switch witch.HoAlgoS (negotiation not Cdma1xRttCsfbSwitch(Cdma1xRttCsfbSwitch)
witch required) check box.
Name
Operator ID CnOperatorId (negotiation parameter specifies the ID of the operator whose
not required) RAT blind-handover priorities are to be set.
priority InterRatHighestPri (negotiation parameter is set to UTRAN by default and
InterRat not required) specifies the high-priority RAT to be considered in
blind handovers for CSFB. For CSFB to
CDMA2000 1xRTT, set this parameter to
CDMA2000.

eRAN
Name
priority InterRatSecondPri (negotiation parameter is set to GERAN by default and
InterRat not required) specifies the medium-priority RAT to be considered
in blind handovers for CSFB. Ensure that this
parameters.
parameters.
CDMA2000 CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
LCS CdmaLcsCap (negotiation parameter specifies the LCS capability of the
capability not required) CDMA2000 1xRTT network.
7.3.5 Precautions
None

navigation tree.


eRAN
----End
Table 7-9 Parameters for CSFB to CDMA2000 1xRTT
MO Parameter Group Name Parameter
CDMA2000BANDCLASS Cdma2000BandClass Local cell identity, Band class
CDMA2000NFREQ Cdma2000Nfreq Local cell identity, Band class, Frequency
CDMA2000EXTERNALC Cdma2000ExternalCell Sector identity, Band class, Frequency, Physical
ELL cell identity, CDMA2000 neighbor cell type,
Mobile country code, Mobile network code
CDMA2000EXTERNALC Cdma2000ExternalCellPlmn Sector identity, Share mobile country code,
ELLPLMN Share mobile network code
CDMA20001XRTTNCEL Cdma20001xrttNcell Local cell identity, Sector identity, Blind
L handover priority
ENODEBALGOSWITCH ENodeBAlgoSwitch Handover Algo switch, Handover Mode switch
CSFALLBACKBLINDHO CSFallBackBlindHoCfg CN Operator ID, Highest priority InterRat,
CFG Second priority InterRat, Lowest priority InterRat,
CDMA2000 LCS capability

Step 1 Run the following commands to add neighbor relationships with CDMA2000 1xRTT cells:
1. ADD CDMA2000BANDCLASS
2. ADD CDMA2000NFREQ
3. ADD CDMA2000EXTERNALCELL
4. ADD CDMA2000EXTERNALCELLPLMN
5. ADD CDMA20001XRTTNCELL
algorithm switches for CSFB to CDMA2000 1xRTT.
----End

eRAN

If the calls continue until they are ended, CSFB to CDMA2000 1xRTT takes effect. You can observe the
signaling procedures for CSFB to CDMA2000 1xRTT, which is the same as that for CSFB to UTRAN
described in section 7.1.7 "Activation Observation."
----End
7.3.8 Deactivation
Run the MOD ENODEBALGOSWITCH command with the
Cdma1xRttCsfbSwitch(Cdma1xRttCsfbSwitch) check box under the
ENodeBAlgoSwitch.HoAlgoSwitch parameter cleared.
7.4 Deploying Flash CSFB to UTRAN

7.4.1 When to Use Flash CSFB 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.
 UEs comply with 3GPP Release 9.
 The core networks support the RIM procedure.
Connected Mode Feature Parameter Description. If the UTRAN cell and E-UTRAN cell cover the same
area, or the UTRAN cell provides better coverage than the E-UTRAN cell, use CSFB based on blind

ensure that they all support CSFB and the RIM procedure. Table 7-10 describes the requirements of
flash CSFB to UTRAN for the core networks.
Table 7-10 Requirements of flash CSFB to UTRAN for the core networks
NE Description
MME Supports:
 CSFB
 RIM procedures in compliance with 3GPP Release 9

eRAN
NE Description
SGSN Supports:
 CSFB
 RIM procedures in compliance with 3GPP Release 9
− Whether the UEs comply with 3GPP Release 9 specifications

 If the core-network equipment is provided by Huawei, the version must be PS8.2 or later.

Operators must purchase and activate the following licenses.
Table 7-11 License control item for flash CSFB to UTRAN
LOFD-001033 CS Fallback to UTRAN CS Fall Back to UTRAN
LOFD-001052 Flash CS Fallback to UTRAN Flash CS Fallback to UTRAN
NOTE
If PS handover for CSFB to UTRAN is enabled, CSFB to UTRAN based on PS handover instead of flash CSFB to UTRAN
is used for UEs that support PS handovers. For details, see section 6.4 "LOFD-001052 Flash CS Fallback to UTRAN."


eRAN
Generic Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with UTRAN cells.
This section provides only the information about MOs related to neighboring UTRAN cells and key
parameters in these MOs. For more information about how to collect data for the parameters in these
 UtranNFreq: used to configure neighboring UTRAN frequencies.
 UtranExternalCell: used to configure external UTRAN cells. If PS handover is used, the
UtranExternalCell.Rac parameter must be set.
 UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared external UTRAN cell.
This MO is required only if the NodeB providing the external UTRAN cell works in RAN sharing with
common carriers mode and multiple operators share the external UTRAN cell.
 UtranNCell: used to configure neighbor relationships with UTRAN cells. If a neighboring UTRAN cell
specified by the UtranNCell.BlindHoPriority parameter.
handover mode and handover algorithm switches for flash CSFB to UTRAN.

Name
Mode switch witch.HoMode (negotiation To activate blind handovers, select the
Switch not required) BlindHoSwitch(BlindHoSwitch) check box. A blind
handover to an inter-RAT cell can be performed only if a
blind-handover priority is specified for the inter-RAT cell.
Compared with measurement-based handovers, blind
handovers reduce access delays but cause lower
Handover ENodeBAlgoS Network plan To activate flash CSFB to UTRAN, select the
Algo switch witch.HoAlgoS (negotiation UtranCsfbSwitch(UtranCsfbSwitch) and
witch not required) UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check
boxes.

eRAN

Name
RIM switch ENodeBAlgoS Network plan UTRAN_RIM_SWITCH under this parameter
witch.RimSwitc (negotiation specifies whether to enable or disable the RIM procedure
h not required) 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 the
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check
box under ENodeBAlgoSwitch.HoAlgoSwitch is
selected, 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, it
is recommended that you select the
UTRAN_RIM_SWITCH(UTRAN_RIM_SWITCH) check
box.
The following table describes the parameters that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
Name
MME S1Interface.MmeRelease Network plan To active the multiple RIM, set the parameter to
Release (negotiation Release_R9(Release 9).
not required)
Name
CN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan.
Operator CnOperatorId (negotiation This parameter specifies the ID of the
ID not required) operator whose RAT blind-handover priorities are
to be set.

eRAN
Name
Highest CSFallBackBlindHoCfg.I Network plan Set this parameter based on the network plan.
priority nterRatHighestPri (negotiation This parameter is set to UTRAN by default and
InterRat not required) specifies the high-priority RAT to be considered in
blind handovers for CSFB. For flash CSFB to
UTRAN, retain the default value.
Second CSFallBackBlindHoCfg.I Network plan Set this parameter based on the network plan.
priority nterRatSecondPri (negotiation This parameter is set to GERAN by default and
InterRat not required) specifies the medium-priority RAT to be
considered in blind handovers for CSFB. Ensure
that this parameter is set to a different value from
the CSFallBackBlindHoCfg.InterRatHighestPri
and CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallBackBlindHoCfg.I Network plan Set this parameter based on the network plan.
priority nterRatLowestPri (negotiation This parameter is set to CDMA2000 by default and
parameters.
UTRAN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan.
LCS UtranLcsCap (negotiation This parameter specifies the LCS capability of the
capability not required) UTRAN.
7.4.5 Precautions
None

navigation tree.

eRAN

----End
Table 7-12 Parameters for flash CSFB to UTRAN
UTRANNFREQ UtranNFreq Local cell identity, Downlink UARFCN
UTRANEXTERN UtranExternalCell Mobile country code, Mobile network code, UTRAN cell
ALCELL identity, Downlink UARFCN, RNC identity, Routing area
code configure indicator, Routing area code, Primary
scrambling code, Location area code
UTRANEXTERN UtranExternalCellPlmn UTRAN cell identity, Mobile country code, Mobile network
ALCELLPLMN code, Share mobile country code, Share mobile network
code
UTRANNCELL UtranNCell Local cell identity, Mobile country code, Mobile network
code, UTRAN cell identity, Blind handover priority
S1Interface S1Interface MME Release
ENODEBALGOS ENodeBAlgoSwitch Handover Algo switch, Handover Mode switch, Redirection
WITCH switch, RIM switch
CSFALLBACKBLI CSFallBackBlindHoCfg CN Operator ID, Highest priority InterRat, Second priority
NDHOCFG InterRat, Lowest priority InterRat, UTRAN LCS capability

Step 1 Run the following commands to add neighbor relationships with UTRAN cells:
1. ADD UTRANNFREQ
2. ADD UTRANEXTERNALCELL
3. ADD UTRANEXTERNALCELLPLMN
4. ADD UTRANNCELL

eRAN
Step 2 Run the MOD ENODEBALGOSWITCH command to set the handover mode, handover
algorithm switches, redirection algorithm switch, and RIM procedure switch for flash CSFB to
UTRAN.
NOTE
To manually trigger an RIM procedure, run the following commands to turn off and then turn on the RIM procedure switch:
1. MOD ENODEBALGOSWITCH: RimSwitch=UTRAN_RIM_SWITCH-0
2. MOD ENODEBALGOSWITCH: RimSwitch=UTRAN_RIM_SWITCH-1
Step 3 Run the MOD S1INTERFACE command to set the compliance protocol release of the MME.
----End

Enable a UE to camp on an E-UTRAN cell and originate a voice call. If the call continues and the RRC
Connection Release message traced on the Uu interface carries the information of the neighboring
UTRAN cell, flash CSFB to UTRAN has been activated successfully.
The signaling procedure for flash CSFB to UTRAN is similar to that for CSFB to UTRAN described in
section 7.1.7 "Activation Observation." The difference is that the RRC Connection Release message
carries the information of the neighboring UTRAN cell.
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.
7.4.8 Deactivation
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check box under the
7.5 Deploying Flash CSFB to GERAN

7.5.1 When to Use Flash CSFB to GERAN
When LOFD-001034 CS Fallback to GERAN has been enabled, use LOFD-001053 Flash CS Fallback
to GERAN if all the following conditions are met:
 The E-UTRAN and GERAN support the RIM with SIB procedure.
 UEs comply with 3GPP Release 9.
 The core networks support the RIM procedure.
Connected Mode Feature Parameter Description. If the GERAN cell and E-UTRAN cell cover the same
area, or the GERAN cell provides better coverage than the E-UTRAN cell, use CSFB based on blind

eRAN

ensure that they all support CSFB and the RIM procedure. Table 7-13 describes the requirements of
flash CSFB to GERAN for the core networks.
Table 7-13 Requirements of flash CSFB to GERAN for the core networks
NE Description
MME Supports:
 CSFB
 RIM procedures in compliance with 3GPP Release.
SGSN Supports:
 CSFB
 RIM procedures in compliance with 3GPP Release.
− Whether the UEs comply with 3GPP Release 9 specifications


Operators must purchase and activate the following licenses.
Table 7-14 License control item for flash CSFB to GERAN
LOFD-001034 CS Fallback to GERAN CS Fall Back to GERAN
LOFD-001053 Flash CS Fallback to GERAN Flash CS Fallback to GERAN

eRAN
NOTE
If PS handover for CSFB to GERAN is enabled, CSFB to GERAN based on PS handover instead of flash CSFB to
GERAN is used for UEs that support PS handovers. For details, see section 6.5 "LOFD-001053 Flash CS Fallback to
GERAN."

Generic 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
 GeranNfreqGroup: used to configure GERAN carrier frequency groups.
 GeranNfreqGroupArfcn: used to configure ARFCNs in each GERAN carrier frequency group.
 GeranExternalCell: used to configure external GERAN cells. If PS handover is used, the
GeranExternalCell.Rac parameter must be set.
 GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared external GERAN
cell. This MO is required only if the BTS providing the external GERAN cell works in RAN sharing with
common carriers mode and multiple operators share the external GERAN cell.
 GeranNcell: used to configure neighbor relationships with GERAN cells. If a neighboring GERAN cell
specified by the GeranNcell.BlindHoPriority parameter.
handover mode and handover algorithm switches for flash CSFB to GERAN.

Name
Handover ENodeBAlgoSwit Network plan Set this parameter based on the network plan.
Mode switch ch.HoModeSwitc (negotiation not To activate blind handovers, select the
h required) BlindHoSwitch(BlindHoSwitch) check box. A
blind handover to an inter-RAT cell can be
performed only if a blind-handover priority is
specified for the inter-RAT cell. Compared with
measurement-based handovers, blind handovers

eRAN

Name
reduce access delays but cause lower handover
success rates.
Handover ENodeBAlgoSwit Network plan To activate flash CSFB to GERAN, select the
Algo switch ch.HoAlgoSwitch (negotiation not GeranCsfbSwitch(GeranCsfbSwitch) and
required) GeranFlashCsfbSwitch(GeranFlashCsfbSwitch)
check boxes.
RIM switch ENodeBAlgoSwit Network plan GERAN_RIM_SWITCH under this parameter
ch.RimSwitch (negotiation not specifies whether to enable or disable the RIM
required) procedure that requests event-driven multiple
reports from GERAN cells.
 If this switch is turned on, the eNodeB can send
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 the
GeranFlashCsfbSwitch(GeranFlashCsfbSwitch)
check box under
ENodeBAlgoSwitch.HoAlgoSwitch is selected,
the eNodeB sends
RAN-INFORMATION-REQUEST/Single Report
PDUs to GERAN cells to request single reports.
If the GERAN cells support
PDUs, it is recommended that you select the
GERAN_RIM_SWITCH(GERAN_RIM_SWITCH)
check box.
The following table describes the parameters that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
Name
MME S1Interface.MmeRelease Network plan To active the multiple RIM, set the parameter to
Release (negotiation Release_R9(Release 9).
not required)

eRAN

Name
handovers for CSFB. For flash CSFB to GERAN,
set this parameter to GERAN.
handovers for CSFB. If the
CSFallBackBlindHoCfg.InterRatHighestPri
parameter is set to GERAN, this parameter cannot
be set to GERAN. Ensure that this parameter is set
to a different value from the
parameters.
parameters.
GERAN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This
LCS GeranLcsCap (negotiation parameter specifies the LCS capability of the
capability not required) GERAN.
7.5.5 Precautions
None


eRAN
navigation tree.

----End
Table 7-15 Parameters for flash CSFB to GERAN
GERANNFREQGROUP GeranNfreqGroup Local cell identity, BCCH group identity,
GERAN version, Starting ARFCN, Band
indicator
GERANNFREQGROUPARFCN GeranNfreqGroupArfcn Local cell identity, BCCH group identity,
GERAN ARFCN
GERANEXTERNALCELL GeranExternalCell Mobile country code, Mobile network code,
GERAN cell identity, Location area code,
Routing area code configure indicator,
Routing area code, Band indicator, GERAN
ARFCN, Network colour code, Base station
colour code, DTM indication
GERANEXTERNALCELLPLMN GeranExternalCellPlmn GERAN cell identity, Location area code,
Mobile country code, Mobile network code,
Share mobile country code, Share mobile
network code
GERANNCELL GeranNcell Local cell identity, Mobile country code,
Mobile network code, Location area code,
GERAN cell identity, Blind handover priority
S1Interface S1Interface MME Release
ENODEBALGOSWITCH ENodeBAlgoSwitch Handover Algo switch, Handover Mode
switch, Redirection switch, RIM switch
CSFALLBACKBLINDHOCFG CSFallBackBlindHoCfg CN Operator ID, Highest priority InterRat,
Second priority InterRat, Lowest priority
InterRat, GERAN LCS capability

eRAN

Step 1 Run the following commands to add neighbor relationships with GERAN cells:
1. ADD GERANNFREQGROUP
2. ADD GERANNFREQGROUPARFCN
3. ADD GERANEXTERNALCELL
4. ADD GERANEXTERNALCELLPLMN
5. ADD GERANNCELL
Step 2 Run the MOD ENODEBALGOSWITCH command to set the handover mode, handover
algorithm switches, redirection algorithm switch, and RIM procedure switch for flash CSFB to
GERAN.
Step 3 Run the MOD S1INTERFACE command to set the compliance protocol release of the MME.
----End

Enable a UE to camp on an E-UTRAN cell and originate a voice call. If the call continues and the RRC
Connection Release message traced on the Uu interface carries the information of the neighboring
GERAN cell, flash CSFB to GERAN has been activated successfully.
The signaling procedure for flash CSFB to GERAN is similar to that for CSFB to UTRAN described in
section 7.1.7 "Activation Observation." The difference is that the RRC Connection Release message
carries the information of the neighboring GERAN cell.
Check the status of the RIM procedure towards neighboring GERAN cells by running the DSP
GERANRIMINFO command. If the ID of a neighboring GERAN cell is displayed in the command output,
the eNodeB has obtained the system information of this neighboring GERAN cell.
7.5.8 Deactivation
GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box under the
7.6 Deploying CSFB with LAI to UTRAN

7.6.1 When to Use CSFB 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).

eRAN
Use LOFD-001068 CS Fallback with LAI to UTRAN also when both of the following conditions are met:
 LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to GERAN have been enabled.
 The neighboring UTRAN and GERAN cells of the E-UTRAN cell have different LAIs.

ensure that they all support CSFB and the MME supports LAI delivery. Table 7-16 describes the
requirements of CSFB with LAI to UTRAN for the core networks.
Table 7-16 Requirements of CSFB with LAI to UTRAN for the core networks
NE Description
MME Supports:
 SMS over SGs
 LAI delivery
MSC Supports:
 SMS over SGs


eRAN

Table 7-17 License control item for CSFB with LAI to UTRAN
LOFD-001068 CS Fallback with LAI to UTRAN CS Fallback with LAI to UTRAN

Data preparation for CSFB with LAI to UTRAN is the same as that for CSFB to UTRAN described in
section 7.1.4 "Data Preparation."
7.6.5 Precautions
None

CSFB with LAI to UTRAN is automatically activated when two conditions are met:
The license for this feature has been activated.
CSFB to UTRAN has been activated. For details about how to activate CSFB to UTRAN, see section
7.1.6 "Initial Configuration."

Step 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 in
Step 3 and Step 4.
Step 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.
Step 3 Enable a UE to camp on the E-UTRAN cell and originate a voice call.
If the calls continue until they are ended, CSFB with LAI to UTRAN takes effect. You can observe the
signaling procedure for CSFB with LAI to UTRAN, which is similar to that for CSFB to UTRAN described
in section 7.1.7 "Activation Observation." The difference is that the Initial Context Setup Request
message carries the LAI that the MME delivers to the eNodeB.
----End

eRAN
7.6.8 Deactivation
CSFB with LAI to UTRAN is automatically deactivated when its license or CSFB to UTRAN is
deactivated. For details about how to deactivate CSFB to UTRAN, see section 7.1.8 "Deactivation."
7.7 Deploying CSFB with LAI to GERAN

7.7.1 When to Use CSFB with LAI to GERAN
Use LOFD-001069 CS Fallback with LAI to GERAN when both of the following conditions are met:
 LOFD-001034 CS Fallback to GERAN has been enabled.
 The E-UTRAN cell has neighboring GERAN cells that belong to different PLMNs and supports
inter-PLMN handovers, or the E-UTRAN cell has neighboring GERAN cells that have different LACs.
Use LOFD-001069 CS Fallback with LAI to GERAN also when both of the following conditions are met:
 LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to GERAN have been enabled.
 The neighboring UTRAN and GERAN cells of the E-UTRAN cell have different LAIs.

ensure that they all support CSFB and the MME supports LAI delivery. Table 7-18 describes the
requirements of CSFB with LAI to GERAN for the core networks.
Table 7-18 Requirements of CSFB with LAI to GERAN for the core networks
NE Description
MME Supports:
 SMS over SGs
 LAI delivery
MSC Supports:
 SMS over SGs

eRAN


equipment supports this feature. This feature can be deployed only when the core-network equipment
supports it.

Table 7-19 License control item for CSFB with LAI to GERAN
LOFD-001069 CS Fallback with LAI to GERAN CS Fallback with LAI to GERAN

Data preparation for CSFB with LAI to GERAN is the same as that for CSFB to GERAN described in
section 7.2.4 "Data Preparation."
7.7.5 Precautions
None

This feature is automatically activated when two conditions are met:
The license for this feature has been activated.
CSFB to GERAN has been activated. For details about how to activate CSFB to GERAN, see section
7.2.6 "Initial Configuration."

Step 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 in
Step 3 and Step 4.

eRAN
Step 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.
Step 3 Enable a UE to camp on the E-UTRAN cell and originate a voice call.
If the calls continue until they are ended, CSFB with LAI to GERAN takes effect. You can observe the
signaling procedure for CSFB with LAI to GERAN, which is similar to that for CSFB to UTRAN described
in section 7.1.7 "Activation Observation." The difference is that the Initial Context Setup Request
message carries the LAI that the MME delivers to the eNodeB.
----End
7.7.8 Deactivation
CSFB with LAI to GERAN is automatically deactivated when its license or CSFB to GERAN is
deactivated. For details about how to deactivate CSFB to GERAN, see section 7.2.8 "Deactivation."
7.8 Performance Optimization

End-to-end CSFB delay includes the processing time at the LTE side and that at the GSM or UMTS side.
Processing at any side may affect the end-to-end delay and user experience.
 For details about processing in Huawei GSM equipment, see Interoperability Between GSM and LTE
 For details about processing in Huawei UMTS equipment, see Interoperability Between UMTS and
LTE Feature Parameter Description.
7.8.1 Monitoring
CSFB allows UEs under LTE coverage to shift to CS networks when CS services arrive. Use the
L.CSFB.PrepAtt and L.CSFB.PrepSucc counters to monitor CSFB performance. Use the L.CSFB.E2W
and L.CSFB.E2G counters (corresponding to UMTS and GSM, respectively) to distinguish between the
target CS networks.
Use the L.RRCRedirection.E2W, L.RRCRedirection.E2G, L.IRATHO.E2W.PrepAttOut, and
L.IRATHO.E2G.PrepAttOut counters to monitor the CSFB mechanisms including redirections and
handovers.
NOTE
The L.RRCRedirection.E2W and L.RRCRedirection.E2G counters measure all redirections including those caused by
factors other than CSFB. The L.IRATHO.E2W.PrepAttOut and L.IRATHO.E2G.PrepAttOut counters measure all
handovers including those caused by factors other than CSFB.
CSFB is an end-to-end service. The performance counters on the LTE side only indicate the success rate of the CSFB
procedure on the LTE side. Therefore, the performance counters on the LTE side cannot directly show the 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.
7.8.2 Parameter Optimization

Blind Handovers for CSFB
Compared with measurement-based handovers, blind handovers reduce access delays but cause lower

eRAN
Set blind-handover priorities of different RATs according to the operator's policy. When the handover
success rate or service setup success rate is low due to poor UTRAN or GERAN coverage, adjust the
blind-handover priorities for different RATs or deactivate blind handovers to improve CSFB performance.
The following table describes the parameters in the CSFallBackBlindHoCfg MO used to set the
blind-handover priorities of different RATs for CSFB.
Name
handovers for CSFB.
handovers for CSFB. Ensure that this parameter is
set to a different value from the
parameters.
parameters.
The following table describes the parameter in the ENodeBAlgoSwitch MO used to activate or
deactivate blind handovers.
Name
Handover ENodeBAlgoS Network plan To activate blind handovers, select the
Mode switch witch.HoModeS (negotiation not BlindHoSwitch(BlindHoSwitch) check box. A blind
witch required) handover to an inter-RAT cell can be performed only if a
blind-handover priority is specified for the inter-RAT cell.
Compared with measurement-based handovers, blind
handovers reduce access delays but cause lower
To deactivate blind handovers, clear the
BlindHoSwitch(BlindHoSwitch) check box.

eRAN
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 the threshold 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:
 CSFB to UTRAN: CSFallBackHo.CsfbHoUtranB1ThdRscp,
CSFallBackHo.CsfbHoUtranB1ThdEcn0, and CSFallBackHo.CsfbHoUtranTimeToTrig
 CSFB to GERAN: CSFallBackHo.CsfbHoGeranB1Thd and
CSFallBackHo.CsfbHoGeranTimeToTrig
 CSFB to CDMA2000 1xRTT: CSFallBackHo.CsfbHoCdmaB1ThdPs and
CSFallBackHo.CsfbHoCdmaTimeToTrig
These parameters belong to the CSFallBackHo MO and are described in the following table.
Name
Local cell ID CSFallBackHo.Lo Network plan Set this parameter based on the network plan.
calCellId (negotiation
not required)
CSFB Utran CSFallBackHo.Cs Network plan Set this parameter based on the network plan. This
EventB1 fbHoUtranTimeTo (negotiation parameter specifies the time-to-trigger for event B1 in
Time To Trig not required) CSFB to UTRAN. When CSFB to UTRAN is required,
Trig this parameter must be set, because it is used by UEs
as one of the conditions for triggering event B1.
When a UE detects that the signal quality in at least one
UTRAN cell meets the entering condition, it does not
immediately send a measurement report to the eNodeB.
Instead, the UE sends a measurement report only when
the signal quality has been meeting the entering
condition throughout a period defined by this parameter.
An appropriate value for this parameter reduces the
probability of random events B1 and the average
number of handovers, thereby eliminating unnecessary
handovers.
CSFB CSFallBackHo.Cs Network plan Set this parameter based on the network plan. This
UTRAN fbHoUtranB1Thd (negotiation parameter specifies the RSCP threshold for event B1 in
EventB1 Rscp not required) CSFB to UTRAN. When CSFB to UTRAN is required,
RSCP this parameter must be set, because it is used by UEs
Trigger as one of the conditions for triggering event B1. Event
Threshold 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.

eRAN
Name
CSFB CSFallBackHo.Cs Network plan This parameter specifies the Ec/No threshold for event
UTRAN fbHoUtranB1Thd (negotiation B1 in CSFB to UTRAN. When CSFB to UTRAN is
EventB1 Ecn0 not required) required, this parameter must be set, because it is used
ECN0 by UEs as one of the conditions for triggering event B1.
Trigger Event B1 is triggered when the Ec/No measured by the
Threshold 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.
GERAN fbHoGeranB1Thd (negotiation parameter specifies the RSSI threshold for event B1 in
EventB1 not required) CSFB to GERAN. Event B1 is triggered when the
Trigger measured RSSI of a GERAN cell reaches the value of
Threshold this parameter and all other conditions are also met.
Geran fbHoGeranTimeT (negotiation parameter specifies the time-to-trigger for event B1 in
EventB1 oTrig not required) CSFB to GERAN. When CSFB to GERAN is required,
Time To this parameter must be set, because it is used by UEs
Trig as one of the conditions for triggering event B1.
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.
handovers.
CDMA2000 fbHoCdmaB1Thd (negotiation parameter specifies the pilot strength threshold for event
EventB1 Ps not required) B1 in CSFB to CDMA2000 1xRTT. Event B1 is
Trigger triggered when the measured pilot strength of a
Threshold CDMA2000 1xRTT cell reaches the value of this
parameter and all other conditions are also met.

eRAN
Name
CDMA fbHoCdmaTimeT (negotiation parameter specifies the time-to-trigger for event B1 in
EventB1 oTrig not required) CSFB to CDMA2000 1xRTT. When CSFB to
Time To CDMA2000 is required, this parameter must be set,
Trig because it is used by UEs as one of the conditions for
triggering event B1.
CDMA2000 1xRTT 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.
handovers.
7.8.3 EBC Description

Table 7-20 describes the event-based counters (EBCs) for CSFB.
Table 7-20 EBCs for CSFB
Event Name Counter Name Counter Description Value
PRIVATE_RRC_ ucRedirectionTrigger Indicator for  0: CSFB
CON_REL Redirection Trigger  1: others
ucCSFBHighPriority Emergency Call  0: indicates a non-emergency-call.
Indicator  1: indicates an emergency call.
ucSIBInfo Indicator for Including  0: indicates that the SIB information of
Target Cell SIB in the target cell is not included in the
RRC Connection RRC Connection Release message.
Release Message  1: indicates that the SIB information of
the target cell is included in the RRC
Connection Release message.
ucTargetType Target Cell RAT  0: indicates that the target cell is an
E-UTRAN cell.
 1: indicates that the target cell is a
UTRAN cell.
 2: indicates that the target cell is a
GERAN cell.

eRAN
Event Name Counter Name Counter Description Value

PRIVATE_INTER ucHoType Handover Type:  1: indicates an intra-frequency
_RAT_HO Intra-Frequency/Inter- handover.
Frequency/Inter-RAT  2: indicates an inter-frequency
handover.
 3: indicates a handover to UTRAN.
 4: indicates a handover to TD-SCDMA.
 5: indicates a handover to CDMA2000.
 6: indicates a handover to GERAN.
ucHoTrigger Handover Trigger  0: indicates a reserved value.
 1: indicates a distance-based
handover.
 2: indicates a coverage-based
handover.
 3: indicates a load-based handover.
ucChoice Cause Category  0: indicates that the procedure is
complete.
 1: indicates that the procedure fails due
to radio-network-layer faults.
to transport-layer faults.
to NAS faults.
to protocol-layer faults.
to other faults.
ucCauseValue Cause Value 23: S1_CS_FALLBACK
ucCSFBHighPriority Indicator for  0: indicates a non-emergency-call.
Emergency  1: indicates an emergency call.
Call-Triggered CSFB
7.9 Troubleshooting
7.9.1 Fault 1
Fault Description
A UE reselects an inter-RAT neighboring cell directly after initiating a voice call in an E-UTRAN cell, and
the S1 interface tracing result shows that CSFB is not triggered.
Fault Handling
Step 1 Create an S1 interface tracing task, use the UE to camp on the E-UTRAN cell again, and
check whether the value of the information element (IE) ePS-attach-type-value is

eRAN
"combined-attach" in the traced Attach Request message. If so, go to Step 2. 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. If it
does, go to Step 3. If not, contact Huawei technical support.
Step 3 Contact the vendors of core network NEs to ensure the following:
 Attach procedures to the CS domain are allowed according to the subscription data on the
HSS.
 The core network supports CSFB.
 The SGs interface is correctly configured.
----End
7.9.2 Fault 2
Fault Description
An eNodeB delivers an RRC Connection Reconfiguration message 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. If it is, go to Step 2. If not, rectify the faults and try again.
Step 2 Check whether the coverage of the inter-RAT neighboring cell is good enough. If the coverage is
not good enough, adjust B1-related parameters or use CSFB based on blind handovers.
For details about how to adjust B1-related parameters, see Mobility Management in Connected
Mode Feature Parameter Description.
----End
7.9.3 Fault 3
Fault Description
Even when blind handovers are configured as the preferred choice in the operator's policy, instead of
triggering a blind handover for CSFB, an eNodeB delivers an inter-RAT measurement configuration to a
UE that has initiated a voice call.
Fault Handling
Step 1 Run the LST ENODEBALGOSWITCH command and check the setting of BlindHoSwitch under
the Handover Mode switch parameter. If BlindHoSwitch is Off, run the MOD
ENODEBALGOSWITCH command with the BlindHoSwitch(BlindHoSwitch) check box under
the ENodeBAlgoSwitch.HoModeSwitch parameter selected. In addition, check the CSFB
mechanism and perform the following:
 If CSFB to UTRAN is required, go to Step 2.
 If CSFB to GERAN is required, go to Step 3.
 If CSFB to CDMA2000 1xRTT is required, go to Step 4.

eRAN
Step 2 Run the LST UTRANNCELL command and check whether Blind handover priority is 0 for a
neighboring UTRAN cell that is supposed to accept incoming blind handovers.
 If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case, run
the MOD UTRANNCELL command with the Blind handover priority parameter set to a value
other than 0.
 If Blind handover priority is not 0, contact Huawei technical support.
Step 3 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.
the MOD GERANNCELL command with the Blind handover priority parameter set to a value
other than 0.
Step 4 Run the LST CDMA20001XRTTNCELL command to check whether Blind handover priority is
0 for a neighboring CDMA2000 1xRTT cell that is supposed to accept incoming blind handovers.
the MOD CDMA20001XRTTNCELL command with the Blind handover priority parameter
set to a value other than 0.
----End
7.9.4 CS Fallback with LAI to UTRAN

Table 7-21 shows the alarms related to the feature.
Table 7-21 Alarm list
Alarm ID Alarm Name Network Element Feature ID Feature Name
29221 LTE-WCDMA Inter-System eNodeB LOFD-001068 CS Fallback with LAI
Outgoing Cell Handover Success to UTRAN
Rate Too Low
7.9.5 CS Fallback with LAI to GERAN

Table 7-22 shows the alarms related to the feature.
Table 7-22 Alarm list
Alarm ID Alarm Name Network Element Feature ID Feature Name
29222 LTE-GERAN Inter-System eNodeB LOFD-001069 CS Fallback with LAI
Outgoing Cell Handover Success to GERAN
Rate Too Low

eRAN
CS Fallback 8 Parameters
8 Parameters
Table 8-1 Parameter description
MO Parameter MML Feature Feature Description
ID Command ID Name
Cdma20001 BlindHoPrio ADD LOFD-0 Automati Meaning:Indicates the priority of the

XRTTNcell rity CDMA20001XR 02001 / c neighboring cell during blind handovers.
TTNCELL TDLOF Neighbo Blind handover is a process in which the
D-00200 ur eNodeB instructs a UE to hand over to a
MOD 1 Relation specified neighboring cell without
CDMA20001XR (ANR) measurements. There are 32 priorities
TTNCELL LBFD-0 altogether. The priority has a positive
02018 / Mobility correlation with the value of this
LST TDLBFD Manage parameter. Note that the value 0 indicates
CDMA20001XR -002018 ment
TTNCELL that blind handovers to the neighboring
cell are prohibited.
GUI Value Range:0~32
Unit:None
Actual Value Range:0~32
Default Value:0
UtranNCell BlindHoPrio ADD LBFD-0 Mobility Meaning:Indicates the priority of the

rity UTRANNCELL 02018 / Manage neighboring cell during blind handovers.
TDLBFD ment Blind handover is a process in which the
MOD -002018 eNodeB instructs a UE to hand over to a
UTRANNCELL specified neighboring cell. There are 32
LST priorities altogether. The priority has a
UTRANNCELL positive correlation with the value of this
parameter. Note that the value 0 indicates
that blind handovers to the neighboring
cell are not allowed.
GUI Value Range:0~32
Unit:None
Actual Value Range:0~32
Default Value:0
GeranNcell BlindHoPrio ADD LBFD-0 Mobility Meaning:Indicates the priority of the

rity GERANNCELL 02018 / Manage neighboring cell during blind handovers.
TDLBFD ment Blind handover is a process in which the
MOD -002018 eNodeB instructs a UE to hand over to a
GERANNCELL PS specified neighboring cell. There are 32
LOFD-0 Inter-RA priorities altogether. The priority has a
LST 01020 / T
GERANNCELL TDLOF Mobility positive correlation with the value of this
parameter. Note that the value 0 indicates
D-00102 between that blind handovers to the neighboring
0 E-UTRA cell are not allowed.
N and

eRAN

ID Command ID Name
LOFD-0 GERAN GUI Value Range:0~32
01045 /
TDLOF Inter-RA Unit:None
D-00104 T Load Actual Value Range:0~32
5 Sharing
to Default Value:0
LOFD-0 GERAN
01046 /
TDLOF Service
D-00104 based
6 inter-RA
T
LOFD-0 handove
01073 / r to
TDLOF GERAN
D-00107
3 Distance
based
inter-RA
T
handove
r to
GERAN
CSFallBackB CdmaLcsC MOD LOFD-0 CS Meaning:Indicates the Location Services

lindHoCfg ap CSFALLBACKB 01035 Fallback (LCS) capability of the CDMA2000. If this
LINDHOCFG to parameter is set to ON, the CDMA2000
LOFD-0 CDMA2 supports LCS. If this parameter is set to
LST 01047 / 000 OFF, the CDMA20000 does not support
CSFALLBACKB TDLOF 1xRTT LCS.
LINDHOCFG D-00104
7 LoCatio GUI Value Range:OFF(Off), ON(On)
n
Services Unit:None
(LCS) Actual Value Range:OFF, ON
Default Value:OFF(Off)
CSFallBackB CnOperator LST None None Meaning:Indicates the index of the

lindHoCfg Id CSFALLBACKB operator.
LINDHOCFG
GUI Value Range:0~5
MOD
CSFALLBACKB Unit:None
LINDHOCFG Actual Value Range:0~5
Default Value:None
CSFallBackH CsfbHoCd MOD LOFD-0 CS Meaning:Indicates the pilot strength

o maB1ThdP CSFALLBACKH 01035 Fallback threshold related to event B1, which is
s O to used in CS fallback to CDMA2000. A UE
CDMA2 sends a measurement report related to
LST 000 event B1 to the eNodeB when the pilot

eRAN

ID Command ID Name
CSFALLBACKH 1xRTT strength in at least one CDMA2000 cell
O exceeds this threshold and other triggering
conditions are met. For details, see 3GPP
TS 36.331.
GUI Value Range:-63~0
Unit:0.5dB
Actual Value Range:-31.5~0, step:0.5
Default Value:-34
CSFallBackH CsfbHoCd MOD LOFD-0 CS Meaning:Indicates the time-to-trigger for

o maTimeToT CSFALLBACKH 01035 Fallback event B1, which is used in CS fallback to
rig O to CDMA2000. When CS fallback to
CDMA2 CDMA2000 is applicable, this parameter is
LST 000 set for UEs and used in the evaluation
CSFALLBACKH 1xRTT of whether to trigger event B1. When
O detecting that the signal quality in at least
one CDMA2000 cell meets the entering
condition, the UE does not send a
measurement report 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 reduce the number of occasionally
triggered event reports, the average
number of handovers, and the number
of wrong handovers, and hence helps
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
CSFallBackH CsfbHoGer MOD LOFD-0 CS Fall Meaning:Indicates the RSSI threshold for
o anB1Thd CSFALLBACKH 01034 / Back to event B1 that is used in CS fallback to
O TDLOF GERAN GERAN. A UE sends a measurement
D-00103 report related to event B1 to the
LST 4 eNodeB when the RSSI in at least one
CSFALLBACKH GERAN cell exceeds this threshold and

eRAN

ID Command ID Name
O other triggering conditions are met. For
GUI Value Range:-110~-48
Unit:dBm
Actual Value Range:-110~-48
Default Value:-103
CSFallBackH CsfbHoGer MOD LOFD-0 CS Fall Meaning:Indicates the time-to-trigger for

o anTimeToTr CSFALLBACKH 01034 / Back to event B1 that is used in CS fallback to
ig O TDLOF GERAN GERAN. When CS fallback to GERAN is
D-00103 applicable, this parameter is set for UEs
LST 4 and used in the evaluation of whether to
CSFALLBACKH trigger event B1. When detecting that the
O signal quality in at least one GERAN cell
meets the entering condition, the UE does
not send a measurement report to the
eNodeB immediately. Instead, the UE
sends a report only when the signal quality
helps decrease the number of occasionally
of wrong handovers, and thus helps
80ms, 100ms, 128ms, 160ms, 256ms,
320ms, 480ms, 512ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
Unit:ms
80ms, 100ms, 128ms, 160ms, 256ms,
320ms, 480ms, 512ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
Default Value:40ms
CSFallBackH CsfbHoUtra MOD LOFD-0 CS Meaning:Indicates the Ec/No threshold for

o nB1ThdEcn CSFALLBACKH 01033 / Fallback event B1, which is used in CS fallback to
0 O TDLOF to UTRAN. When CS fallback to UTRAN is
D-00103 UTRAN required, this parameter is set for UEs and
LST 3 used in the evaluation about whether to
CSFALLBACKH trigger event B1. This parameter indicates
O the Ec/No requirement for the UTRAN
cells to be included in the measurement
report. A UE sends a measurement report

eRAN

ID Command ID Name
related to event B1 to the eNodeB when
the Ec/No 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, step:0.5
Default Value:-13
CSFallBackH CsfbHoUtra MOD LOFD-0 CS Meaning:Indicates the RSCP threshold for

o nB1ThdRsc CSFALLBACKH 01033 / Fallback event B1, which is used in CS fallback to
p O TDLOF to UTRAN. When CS fallback to UTRAN is
D-00103 UTRAN applicable, this parameter is set for UEs
LST 3 and used in the evaluation about whether
CSFALLBACKH to trigger event B1. This parameter
O indicates the RSCP requirement for the
UTRAN cells to be included in the
measurement report. A UE sends a
measurement 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
CSFallBackH CsfbHoUtra MOD LOFD-0 CS Meaning:Indicates the time-to-trigger for

o nTimeToTri CSFALLBACKH 01033 / Fallback event B1 that is used in CS fallback to
g O TDLOF to UTRAN. When CS fallback to UTRAN is
D-00103 UTRAN applicable, this parameter is set for UEs
LST 3 and used in the evaluation of whether to
CSFALLBACKH trigger event B1. When detecting that the
O signal quality in at least one UTRAN cell
meets the entering condition, the UE does
not send a measurement report to the
eNodeB immediately. Instead, the UE
sends a report only when the signal quality

eRAN

ID Command ID Name
helps decrease the number of occasionally
of wrong handovers, and thus helps
80ms, 100ms, 128ms, 160ms, 256ms,
320ms, 480ms, 512ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
Unit:ms
80ms, 100ms, 128ms, 160ms, 256ms,
320ms, 480ms, 512ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
Default Value:40ms
CSFallBackB GeranLcsC MOD LOFD-0 CS Meaning:Indicates the Location Services

lindHoCfg ap CSFALLBACKB 01034 / Fallback (LCS) capability of the GERAN. If this
LINDHOCFG TDLOF to parameter is set to ON, the GERAN
D-00103 GERAN supports LCS. If this parameter is set to
LST 4 OFF, the GERAN does not support LCS.
CSFALLBACKB LoCatio
LINDHOCFG LOFD-0 n GUI Value Range:OFF(Off), ON(On)
01047 / Services
TDLOF (LCS) Unit:None
D-00104 Actual Value Range:OFF, ON
7
ENodeBAlgo HoAlgoSwit MOD LBFD-0 Coverag Meaning:Indicates the collective switch

Switch ch ENODEBALGO 0201801 e Based used to enable or disable handover.
SWITCH / Intra-fre
TDLBFD quency Flash CS fallback to UTRAN: If the switch
LST -002018 Handov for CS fallback to UTRAN is turned off, this
ENODEBALGO 01 er switch does not take effect;
SWITCH
LBFD-0 Coverag Flash CS fallback to GERAN: If the switch
0201802 e Based for CS fallback to GERAN is turned off, this
/ Inter-fre switch does not take effect.
TDLBFD quency GUI Value
-002018 Handov Range:IntraFreqCoverHoSwitch(IntraFreq
02 er CoverHoSwitch),
LOFD-0 Service InterFreqCoverHoSwitch(InterFreqCoverH
01043 / based oSwitch),
TDLOF inter-RA UtranCsfbSwitch(UtranCsfbSwitch),
D-00104 T GeranCsfbSwitch(GeranCsfbSwitch),
handove Cdma1xRttCsfbSwitch(Cdma20001xRttCs

eRAN

ID Command ID Name
3 r to fbSwitch),
UTRAN UtranServiceHoSwitch(UtranServiceHoSw
LOFD-0 itch),
01046 / Service GeranServiceHoSwitch(GeranServiceHoS
TDLOF based witch),
D-00104 inter-RA CdmaHrpdServiceHoSwitch(Cdma2000Hr
6 T pdServiceHoSwitch),
handove Cdma1xRttServiceHoSwitch(Cdma20001
LBFD-0 r to
0201805 GERAN xRttServiceHoSwitch),
/ UlQualityInterRATHoSwitch(UlQualityInter
TDLBFD Service RATHoSwitch),
-002018 Based InterPlmnHoSwitch(InterPlmnHoSwitch),
05 Inter-fre UtranFlashCsfbSwitch(UtranFlashCsfbSwi
quency tch),
LOFD-0 Handov GeranFlashCsfbSwitch(GeranFlashCsfbS
01033 / er witch),
TDLOF ServiceBasedInterFreqHoSwitch(ServiceB
D-00103 CS asedInterFreqHoSwitch),
3 Fallback UlQualityInterFreqHoSwitch(UlQualityInter
to FreqHoSwitch)
LOFD-0 UTRAN
01034 / Unit:None
TDLOF CS
D-00103 Fallback Actual Value
4 to Range:IntraFreqCoverHoSwitch,
GERAN InterFreqCoverHoSwitch,
LOFD-0 UtranCsfbSwitch, GeranCsfbSwitch,
01035 / CS Cdma1xRttCsfbSwitch,
TDLOF Fallback UtranServiceHoSwitch,
D-00103 to GeranServiceHoSwitch,
5 CDMA2 CdmaHrpdServiceHoSwitch,
000 Cdma1xRttServiceHoSwitch,
LOFD-0 1xRTT UlQualityInterRATHoSwitch,
01052 / InterPlmnHoSwitch,
TDLOF Flash UtranFlashCsfbSwitch,
D-00105 CS GeranFlashCsfbSwitch,
2 Fallback ServiceBasedInterFreqHoSwitch,
to
LOFD-0 UTRAN UlQualityInterFreqHoSwitch
01053 / Default
TDLOF Flash Value:IntraFreqCoverHoSwitch:On,
D-00105 CS InterFreqCoverHoSwitch:On,
3 Fallback UtranCsfbSwitch:Off,
to GeranCsfbSwitch:Off,
GERAN Cdma20001xRttCsfbSwitch:Off,
UtranServiceHoSwitch:Off,
GeranServiceHoSwitch:Off,
Cdma2000HrpdServiceHoSwitch:Off,
Cdma20001xRttServiceHoSwitch:Off,
UlQualityInterRATHoSwitch:Off,
InterPlmnHoSwitch:Off,
UtranFlashCsfbSwitch:Off,
GeranFlashCsfbSwitch:Off,

eRAN

ID Command ID Name
ServiceBasedInterFreqHoSwitch:Off,
UlQualityInterFreqHoSwitch:Off
ENodeBAlgo HoModeSw MOD LOFD-0 PS Meaning:Indicates the switches

Switch itch ENODEBALGO 01019 / Inter-RA corresponding to the inputs based
SWITCH TDLOF T on which the eNodeB determines
D-00101 Mobility handover policies.
LST 9 between
ENODEBALGO E-UTRA Note that EutranVoipCapSwitch will be
SWITCH LOFD-0 N and removed in the later versions. In this
01020 / UTRAN version, the setting of this switch is still
TDLOF synchronized between the M2000 and the
D-00102 PS eNodeB, but it is no longer used internally.
0 Inter-RA Therefore, avoid using this switch.
T
LOFD-0 Mobility GUI Value
01021 / between Range:EutranVoipCapSwitch(EutranVoip
TDLOF E-UTRA CapSwitch),
D-00102 N and UtranVoipCapSwitch(UtranVoipCapSwitch
1 GERAN ),
GeranVoipCapSwitch(GeranVoipCapSwitc
LOFD-0 PS h),
01022 / Inter-RA Cdma1xRttVoipCapSwitch(Cdma1xRttVoi
TDLOF T pCapSwitch),
D-00102 Mobility UtranPsHoSwitch(UtranPsHoSwitch),
2 between GeranPsHoSwitch(GeranPsHoSwitch),
LOFD-0 E-UTRA CdmaHrpdNonOtpimisedHoSwitch(Cdma
01023 / N and HrpdNonOtpimisedHoSwitch),
TDLOF CDMA2 CdmaHrpdOptimisedHoSwitch(CdmaHrpd
D-00102 000 OptimisedHoSwitch),
3 GeranNaccSwitch(GeranNaccSwitch),
SRVCC GeranCcoSwitch(GeranCcoSwitch),
to UtranSrvccSwitch(UtranSrvccSwitch),
UTRAN GeranSrvccSwitch(GeranSrvccSwitch),
SRVCC Cdma1xRttSrvccSwitch(Cdma1xRttSrvcc
to Switch),
GERAN UtranRedirectSwitch(UtranRedirectSwitch
),
GeranRedirectSwitch(GeranRedirectSwitc
h),
CdmaHrpdRedirectSwitch(CdmaHrpdRedi
rectSwitch),
Cdma1xRttRedirectSwitch(Cdma1xRttRe
directSwitch),
BlindHoSwitch(BlindHoSwitch)
Unit:None
Actual Value
Range:EutranVoipCapSwitch,
UtranVoipCapSwitch,
GeranVoipCapSwitch,
Cdma1xRttVoipCapSwitch,

eRAN

ID Command ID Name
UtranPsHoSwitch, GeranPsHoSwitch,
CdmaHrpdNonOtpimisedHoSwitch,
CdmaHrpdOptimisedHoSwitch,
GeranNaccSwitch, GeranCcoSwitch,
UtranSrvccSwitch, GeranSrvccSwitch,
Cdma1xRttSrvccSwitch,
UtranRedirectSwitch,
GeranRedirectSwitch,
CdmaHrpdRedirectSwitch,
Cdma1xRttRedirectSwitch, BlindHoSwitch
Default Value:EutranVoipCapSwitch:On,
UtranVoipCapSwitch:Off,
GeranVoipCapSwitch:Off,
Cdma1xRttVoipCapSwitch:Off,
UtranPsHoSwitch:Off,
GeranPsHoSwitch:Off,
CdmaHrpdNonOtpimisedHoSwitch:Off,
CdmaHrpdOptimisedHoSwitch:Off,
GeranNaccSwitch:Off,
GeranCcoSwitch:Off,
UtranSrvccSwitch:Off,
GeranSrvccSwitch:Off,
Cdma1xRttSrvccSwitch:Off,
UtranRedirectSwitch:Off,
GeranRedirectSwitch:Off,
CdmaHrpdRedirectSwitch:Off,
Cdma1xRttRedirectSwitch:Off,
BlindHoSwitch:Off
CSFallBackB InterRatHig MOD LOFD-0 PS Meaning:Ndicates the high-priority system

lindHoCfg hestPri CSFALLBACKB 01019 / Inter-RA to be considered in blind handovers. It is
LINDHOCFG TDLOF T UTRAN by default. This parameter can be
D-00101 Mobility set to UTRAN, GERAN, or CDMA2000.
LST 9 between
CSFALLBACKB E-UTRA GUI Value Range:UTRAN, GERAN,
LINDHOCFG LOFD-0 N and CDMA2000
01020 / UTRAN
TDLOF Unit:None
D-00102 PS Actual Value Range:UTRAN, GERAN,
0 Inter-RA CDMA2000
T
LOFD-0 Mobility Default Value:UTRAN
01021 / between
TDLOF E-UTRA
D-00102 N and
1 GERAN
LOFD-0 PS
01044 / Inter-RA
TDLOF T
D-00104 Mobility
4 between

eRAN

ID Command ID Name
LOFD-0 E-UTRA
01045 / N and
TDLOF CDMA2
D-00104 000
5
Inter-RA
LOFD-0 T Load
01033 / Sharing
TDLOF to
D-00103 UTRAN
3
Inter-RA
LOFD-0 T Load
01034 / Sharing
TDLOF to
D-00103 GERAN
4
CS
LOFD-0 Fallback
01035 / to
TDLOF UTRAN
D-00103
5 CS
Fallback
LOFD-0 to
01068 / GERAN
TDLOF
D-00106 CS
8 Fallback
to
LOFD-0 CDMA2
01069 / 000
TDLOF 1xRTT
D-00106
9 CS
Fallback
LOFD-0 with
01052 / LAI to
TDLOF UTRAN
D-00105
2 CS
Fallback
LOFD-0 with
01053 / LAI to
TDLOF GERAN
D-00105
3 Flash
CS
Fallback
to
UTRAN
Flash
CS
Fallback

eRAN

ID Command ID Name
to
GERAN
CSFallBackB InterRatLo MOD LOFD-0 PS Meaning:Indicates the low-priority system

lindHoCfg westPri CSFALLBACKB 01019 / Inter-RA to be considered in blind handovers. It is
LINDHOCFG TDLOF T CDMA2000 by default. This parameter can
D-00101 Mobility be set to UTRAN, GERAN, or CDMA2000.
LST 9 between If this parameter is set to NULL, the
CSFALLBACKB E-UTRA system with the medium blind handover
LINDHOCFG LOFD-0 N and priority is not specified and only blind
01020 / UTRAN handovers to the high- and
TDLOF medium-priority systems are applicable.
D-00102 PS
0 Inter-RA GUI Value Range:UTRAN, GERAN,
T CDMA2000, NULL
LOFD-0 Mobility
01021 / between Unit:None
TDLOF E-UTRA
D-00102 N and Actual Value Range:UTRAN, GERAN,
1 CDMA2000, NULL
GERAN
LOFD-0 PS Default Value:CDMA2000
01044 / Inter-RA
TDLOF T
D-00104 Mobility
4 between
LOFD-0 E-UTRA
01045 / N and
TDLOF CDMA2
D-00104 000
5 Inter-RA
LOFD-0 T Load
01033 / Sharing
TDLOF to
D-00103 UTRAN
3 Inter-RA
LOFD-0 T Load
01034 / Sharing
TDLOF to
D-00103 GERAN
4 CS
LOFD-0 Fallback
01035 / to
TDLOF UTRAN
D-00103 CS
5 Fallback
LOFD-0 to
01068 / GERAN
TDLOF CS
D-00106

eRAN

ID Command ID Name
8 Fallback
to
LOFD-0 CDMA2
01069 / 000
TDLOF 1xRTT
D-00106
9 CS
Fallback
LOFD-0 with
01052 / LAI to
TDLOF UTRAN
D-00105
2 CS
Fallback
LOFD-0 with
01053 / LAI to
TDLOF GERAN
D-00105
3 Flash
CS
Fallback
to
UTRAN
Flash
CS
Fallback
to
GERAN
CSFallBackB InterRatSec MOD LOFD-0 PS Meaning:Indicates the medium-priority

lindHoCfg ondPri CSFALLBACKB 01019 / Inter-RA system to be considered in blind
LINDHOCFG TDLOF T handovers. It is GERAN by default. This
D-00101 Mobility parameter can be set to UTRAN, GERAN,
LST 9 between or CDMA2000. If this parameter is set to
CSFALLBACKB E-UTRA NULL, the system with the medium blind
LINDHOCFG LOFD-0 N and handover priority is not specified and only
01020 / UTRAN blind handovers to the high-priority system
TDLOF are applicable.
D-00102 PS
0 Inter-RA GUI Value Range:UTRAN, GERAN,
T CDMA2000, NULL
LOFD-0 Mobility
01021 / between Unit:None
TDLOF E-UTRA
D-00102 N and Actual Value Range:UTRAN, GERAN,
1 CDMA2000, NULL
GERAN
LOFD-0 PS Default Value:GERAN
01044 / Inter-RA
TDLOF T
D-00104 Mobility
4 between
LOFD-0 E-UTRA

eRAN

ID Command ID Name
01045 / N and
TDLOF CDMA2
D-00104 000
5
Inter-RA
LOFD-0 T Load
01033 / Sharing
TDLOF to
D-00103 UTRAN
3
Inter-RA
LOFD-0 T Load
01034 / Sharing
TDLOF to
D-00103 GERAN
4
CS
LOFD-0 Fallback
01035 / to
TDLOF UTRAN
D-00103
5 CS
Fallback
LOFD-0 to
01068 / GERAN
TDLOF
D-00106 CS
8 Fallback
to
LOFD-0 CDMA2
01069 / 000
TDLOF 1xRTT
D-00106
9 CS
Fallback
LOFD-0 with
01052 / LAI to
TDLOF UTRAN
D-00105
2 CS
Fallback
LOFD-0 with
01053 / LAI to
TDLOF GERAN
D-00105
3 Flash
CS
Fallback
to
UTRAN
Flash
CS
Fallback
to

eRAN

ID Command ID Name
GERAN
CSFallBackH LocalCellId LST LBFD-0 3GPP Meaning:Indicates the local ID of the cell.
o CSFALLBACKH 01001 / R8 It uniquely identifies a cell within a BS.
O TDLBFD Specific
-001001 ations GUI Value Range:0
MOD
CSFALLBACKH Unit:None
O Actual Value Range:0
Default Value:None
S1Interface MmeReleas ADD LBFD-0 3GPP Meaning:Indicates the compliance

e S1INTERFACE 01001 / R8 protocol release of the MME to which the
TDLBFD Specific eNodeB is connected through the S1
MOD -001001 ations interface. The value of this parameter must
S1INTERFACE be the same as the MME-complied
DSP protocol release. The eNodeB sends S1
S1INTERFACE messages complying with the protocol
release specified by this parameter. If the
parameter value is different from the
MME-complied protocol release, the way
in which the MME handles these message
is subject to the MME implementation.
GUI Value Range:Release_R8(Release
8), Release_R9(Release 9),
Release_R10(Release 10)
Unit:None
Actual Value Range:Release_R8,
Release_R9, Release_R10
Default Value:Release_R8(Release 8)
UtranExterna Rac ADD LOFD-0 PS Meaning:Indicates the routing area code.

lCell UTRANEXTER 01019 / Inter-RA
NALCELL TDLOF T GUI Value Range:0~255
D-00101 Mobility Unit:None
MOD 9 between
UTRANEXTER E-UTRA Actual Value Range:0~255
NALCELL N and
LST UTRAN Default Value:0
UTRANEXTER
NALCELL
GeranExtern Rac ADD LOFD-0 PS Meaning:Indicates the routing area code.

alCell GERANEXTER 01020 / Inter-RA
NALCELL TDLOF T GUI Value Range:0~255
D-00102 Mobility Unit:None
MOD between

eRAN

ID Command ID Name
GERANEXTER 0 E-UTRA Actual Value Range:0~255
NALCELL N and
GERAN Default Value:0
LST
GERANEXTER
NALCELL
ENodeBAlgo RimSwitch MOD LOFD-0 Flash Meaning:Indicates the collective switch for
Switch ENODEBALGO 01052 / CS the RAN information management (RIM)
SWITCH TDLOF Fallback function.
D-00105 to
LST 2 UTRAN UTRAN_RIM_SWITCH: Indicates the
ENODEBALGO switch used to enable or disable the RIM
SWITCH LOFD-0 Flash procedure that requests event-driven
01053 / CS multiple reports from UTRAN cells.
TDLOF Fallback
D-00105 to If this switch is turned on, the eNodeB can
3 GERAN send RAN-INFORMATION-REQUEST
protocol data units (PDUs) to UTRAN cells
to request multiple event-driven reports.
If this switch is turned off, the eNodeB
cannot send
RAN-INFORMATION-REQUEST PDUs to
UTRAN cells to request multiple
event-driven reports.
GERAN_RIM_SWITCH: Indicates the
switch used to enable or disable the RIM
procedure that requests event-driven
multiple reports from GERAN cells.
If this switch is turned on, the eNodeB can
send RAN-INFORMATION-REQUEST
PDUs to CERAN cells to request multiple
If this switch is turned off, the eNodeB
cannot send
RAN-INFORMATION-REQUEST PDUs to
GERAN cells to request multiple
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,

eRAN

ID Command ID Name
GERAN RIM Switch:Off
CSFallBackB UtranLcsCa MOD LOFD-0 CS Meaning:Indicates the Location Services

lindHoCfg p CSFALLBACKB 01033 / Fallback (LCS) capability of the UTRAN. If this
LINDHOCFG TDLOF to parameter is set to ON, the UTRAN
D-00103 UTRAN supports LCS. If this parameter is set to
LST 3 OFF, the UTRAN does not support LCS.
CSFALLBACKB LoCatio
LINDHOCFG LOFD-0 n GUI Value Range:OFF(Off), ON(On)
01047 / Services
TDLOF (LCS) Unit:None
D-00104 Actual Value Range:OFF, ON
7

eRAN
CS Fallback 9 Counters
9 Counters
Table 9-1 Counter description
Counter ID Counter Name Counter Description Feature ID Feature
Name
1526726988 L.IRATHO.E2C.ExecSuccOut Number of LOFD-001021 PS

Successful Outgoing Inter-RAT
Handovers from LOFD-001035 Mobility
E-UTRAN to between
CDMA2000 E-UTRAN
and
CDMA2000
CS
Fallback to
CDMA2000
1xRTT
1526727033 Handover from E-UTRAN to CDMA2000 Success rate of LOFD-001021 PS

Success Rate inter-RAT handovers Inter-RAT
from E-UTRAN to LOFD-001035 Mobility
CDMA2000 network between
E-UTRAN
and
CDMA2000
CS
Fallback to
CDMA2000
1xRTT
1526727034 Handover from E-UTRAN to WCDMA Success rate of LOFD-001019 PS

Success Rate inter-RAT handovers Inter-RAT
from E-UTRAN to LOFD-001022 Mobility
WCDMA network LOFD-001033 between
E-UTRAN
TDLOFD-001019 and
UTRAN
TDLOFD-001022
SRVCC to
TDLOFD-001033 UTRAN
CS
Fallback to
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN

eRAN

Name
SRVCC to
UTRAN
CS
Fallback to
UTRAN
1526728306 L.IRATHO.E2G.Prep.FailOut.MME Number of outgoing LOFD-001034 CS

handover preparation Fallback to
failures from TDLOFD-001034 GERAN
E-UTRAN to GERAN LOFD-001020
due to faults in the CS
EPC TDLOFD-001020 Fallback to
GERAN
LOFD-001046
PS
TDLOFD-001046 Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
Service
based
inter-RAT
handover
to GERAN
Service
based
inter-RAT
handover
to GERAN
1526728307 L.IRATHO.E2G.Prep.FailOut.NoReply Number of outgoing LOFD-001034 CS

failures due to no TDLOFD-001034 GERAN
responses from LOFD-001020 CS
GERAN
TDLOFD-001020 Fallback to
GERAN
LOFD-001046
PS
Mobility

eRAN

Name
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
Service
based
inter-RAT
handover
to GERAN
Service
based
inter-RAT
handover
to GERAN
1526728308 L.IRATHO.E2G.Prep.FailOut.PrepFailure Number of outgoing LOFD-001034 CS

failures due to TDLOFD-001034 GERAN
handover preparation LOFD-001020
failures in GERAN CS
GERAN
LOFD-001046
PS
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
Service
based
inter-RAT
handover
to GERAN

eRAN

Name
Service
based
inter-RAT
handover
to GERAN
1526728309 L.IRATHO.E2T.Prep.FailOut.MME Number of outgoing LOFD-001033 CS

failures from TDLOFD-001033 UTRAN
E-UTRAN to LOFD-001019 CS
TD-SCDMA network
due to faults in the TDLOFD-001019 Fallback to
EPC UTRAN
LOFD-001043
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728310 L.IRATHO.E2T.Prep.FailOut.NoReply Number of outgoing LOFD-001033 CS

failures due to no TDLOFD-001033 UTRAN
TD-SCDMA network
UTRAN
LOFD-001043
PS
Mobility
between

eRAN

Name
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728311 L.IRATHO.E2T.Prep.FailOut.PrepFailure Number of outgoing LOFD-001033 CS

failures due to TDLOFD-001033 UTRAN
failures in CS
TD-SCDMA network TDLOFD-001019 Fallback to
UTRAN
LOFD-001043
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service

eRAN

Name
based
inter-RAT
handover
to UTRAN
1526728312 L.IRATHO.BlindHO.E2W.ExecAttOut Number of performed LOFD-001033 CS

outgoing blind Fallback to
handovers from TDLOFD-001033 UTRAN
UTRAN
PS
WCDMA network Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
1526728313 L.IRATHO.BlindHO.E2W.ExecSuccOut Number of performed LOFD-001033 CS

handovers from TDLOFD-001033 UTRAN
UTRAN
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN

eRAN

Name
1526728314 L.IRATHO.BlindHO.E2G.ExecAttOut Number of performed LOFD-001034 CS

handovers from TDLOFD-001034 GERAN
GERAN
PS
GERAN Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
1526728315 L.IRATHO.BlindHO.E2G.ExecSuccOut Number of successful LOFD-001034 CS

handovers from TDLOFD-001034 GERAN
E-UTRAN to GERAN LOFD-001020
CS
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
1526728316 L.IRATHO.E2W.Prep.FailOut.MME Number of outgoing LOFD-001033 CS

failures from TDLOFD-001033 UTRAN
E-UTRAN to WCDMALOFD-001019
network due to faults CS

eRAN

Name
in the EPC TDLOFD-001019 Fallback to
UTRAN
LOFD-001043
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728317 L.IRATHO.E2W.Prep.FailOut.PrepFailure Number of outgoing LOFD-001033 CS

failures due to TDLOFD-001033 UTRAN
failures in WCDMA CS
network TDLOFD-001019 Fallback to
UTRAN
LOFD-001043
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN

eRAN

Name
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728318 L.IRATHO.E2W.Prep.FailOut.NoReply Number of outgoing LOFD-001033 CS

failures due to no TDLOFD-001033 UTRAN
WCDMA network
UTRAN
LOFD-001043
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728321 L.CSFB.PrepAtt Number of CS LOFD-001033 CS

fallback indicators Fallback to
received by the TDLOFD-001033 UTRAN
eNodeB LOFD-001034 CS
Fallback to

eRAN

Name
TDLOFD-001034 UTRAN
LOFD-001035 CS
Fallback to
GERAN
CS
Fallback to
GERAN
CS
Fallback to
CDMA2000
1xRTT
1526728322 L.CSFB.PrepSucc Number of successful LOFD-001033 CS

CS fallback Fallback to
responses from the TDLOFD-001033 UTRAN
eNodeB LOFD-001034 CS
UTRAN
LOFD-001035
CS
Fallback to
GERAN
CS
Fallback to
GERAN
CS
Fallback to
CDMA2000
1xRTT
1526728323 L.CSFB.E2W Number of CS LOFD-001033 CS

fallback procedures Fallback to
from E-UTRAN to TDLOFD-001033 UTRAN
UTRAN<?Pub
CS
Fallback to
UTRAN
Caret?>
1526728324 L.CSFB.E2G Number of CS LOFD-001034 CS

fallback procedures Fallback to
from E-UTRAN to TDLOFD-001034 GERAN
GERAN
CS
Fallback to
GERAN

eRAN

Name
1526728326 L.RRCRedirection.E2W Number of LOFD-001033 CS

redirections to Fallback to
WCDMA network TDLOFD-001033 UTRAN
LOFD-001052 CS
UTRAN
LOFD-001019
Flash CS
UTRAN
LOFD-001043
Flash CS
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728327 L.RRCRedirection.E2G Number of LOFD-001034 CS

redirections to Fallback to
GERAN TDLOFD-001034 GERAN
LOFD-001053 CS
GERAN
LOFD-001020
Flash CS

eRAN

Name
LOFD-001046 GERAN
TDLOFD-001046 Flash CS
Fallback to
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
Service
based
inter-RAT
handover
to GERAN
Service
based
inter-RAT
handover
to GERAN
1526728328 L.IRATHO.BlindHO.E2W.PrepAttOut Number of outgoing LOFD-001033 CS

blind handover Fallback to
attempts from TDLOFD-001033 UTRAN
UTRAN
PS
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN

eRAN

Name
and
UTRAN
1526728329 L.IRATHO.BlindHO.E2G.PrepAttOut Number of outgoing LOFD-001034 CS

blind handover Fallback to
attempts from TDLOFD-001034 GERAN
GERAN
PS
GERAN Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
1526728330 L.RRCRedirection.E2W.PrepAtt Number of redirection LOFD-001033 CS

preparations to Fallback to
WCDMA network TDLOFD-001033 UTRAN
LOFD-001052 CS
UTRAN
LOFD-001019
Flash CS
UTRAN
LOFD-001043
Flash CS
UTRAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
UTRAN
PS
Inter-RAT
Mobility

eRAN

Name
between
E-UTRAN
and
UTRAN
Service
based
inter-RAT
handover
to UTRAN
Service
based
inter-RAT
handover
to UTRAN
1526728331 L.RRCRedirection.E2G.PrepAtt Number of redirection LOFD-001034 CS

preparations to Fallback to
GERAN TDLOFD-001034 GERAN
LOFD-001053 CS
GERAN
LOFD-001020
Flash CS
GERAN
LOFD-001046
Flash CS
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
PS
Inter-RAT
Mobility
between
E-UTRAN
and
GERAN
Service
based
inter-RAT
handover
to GERAN

eRAN

Name
Service
based
inter-RAT
handover
to GERAN

eRAN
CS Fallback 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
CS Fallback 11 Reference Documents
11 Reference Documents
This chapter lists the reference documents related to CSFB:
[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] eNodeB MO Reference
[8] eNodeB Performance Counter Reference
[9] Mobility Management in Connected Mode Feature Parameter Description
[10] Idle Mode Management Feature Parameter Description
[11] eNodeB Initial Configuration Guide
[12] eNodeB Reconfiguration Guide


CSFB

Uploaded by

Document Informationclick to expand document informationHuawei feature eran

Document Informationclick to expand document information

Copyright:

Available Formats

CSFB

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CSFB

Uploaded by

Copyright:

Available Formats

CS Fallback

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB ........................................................................................3-1

4 CSFB at the eNodeB ................................................................................................................4-1

Issue 02 (2013-05-16) Huawei Proprietary and Confidential i

4.3 Decision Phase of CSFB ............................................................................................................... 4-5

5 Related Features .......................................................................................................................5-1

7 Engineering Guidelines ...........................................................................................................7-1

Issue 02 (2013-05-16) Huawei Proprietary and Confidential ii

7.3.3 Deployment Requirements ................................................................................................. 7-16

Issue 02 (2013-05-16) Huawei Proprietary and Confidential iii

7.8 Performance Optimization ........................................................................................................... 7-37

Issue 02 (2013-05-16) Huawei Proprietary and Confidential iv

1.2 Intended Audience

1.3 Change History

Change Type Change Description Parameter Change

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 1-1

Change Type Change Description Parameter Change

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 1-2

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 2-1

Table 2-1 Optional features related to CSFB and corresponding chapters

2.4 Network Architecture for CSFB to UTRAN/GERAN

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 2-2

Figure 2-1 Network architecture for CSFB to UTRAN/GERAN

SGSN: serving GPRS support node

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 2-3

MSC  Supports combined EPS/IMSI attach.

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 2-4

2.5 Network Architecture for CSFB to CDMA2000 1xRTT

S-GW: serving gateway P-GW: PDN gateway

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 2-5

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 2-6

3 End-to-End Procedures for CSFB

3.1 CSFB to UTRAN

3.1.1 Combined EPS/IMSI Attach Procedure

HSS: home subscriber server VLR: visitor location register

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-1

The combined EPS/IMSI attach procedure is described as follows:

3.1.2 CSFB Procedures for Mobile-originated Calls and

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-2

CSFB Based on PS Handover

RNC: radio network controller

The procedure is described as follows:

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-3

CSFB Procedure for Mobile-terminated Calls

The procedure is described as follows:

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-4

CSFB Based on PS Redirection

The procedure is described as follows:

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-5

CSFB Procedure for Mobile-originated Calls

The procedure is described as follows:

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-6

3.1.3 CSFB Procedure for SMS

3.1.4 CSFB Procedure for Emergency Calls

Issue 02 (2013-05-16) Huawei Proprietary and Confidential 3-7