CS Fallback eRAN3 0 04

CS Fallback eRAN3.
Feature Parameter Description
Issue Date
04 2012-09-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. 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: Email: http://www.huawei.com support@huawei.com
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.1 Network Architecture for CSFB to UTRAN/GERAN ...................................................................... 2-2 2.2 Network Architecture for CSFB to CDMA2000 1xRTT .................................................................. 2-4
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-7 3.1.6 RAN Information Management Procedure ........................................................................... 3-8 3.2 CSFB to GERAN ........................................................................................................................... 3-8 3.2.1 Combined EPS/IMSI Attach Procedure ................................................................................ 3-8 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 4.3 Decision Phase of CSFB ............................................................................................................... 4-5 4.4 Execution Phase of CSFB ............................................................................................................. 4-5
Issue 04 (2012-09-20)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
eRAN CS Fallback
Contents
4.5 CSFB Exception Handling ............................................................................................................. 4-6
5 Related Features .......................................................................................................................5-1

5.1 Required Features......................................................................................................................... 5-1 5.2 Mutually Exclusive Features ......................................................................................................... 5-1 5.3 Affected Features .......................................................................................................................... 5-1
6 Impact on the Networks ..........................................................................................................6-1

6.1 Impact on System Capacity........................................................................................................... 6-1 6.2 Impact on Network Performance................................................................................................... 6-1
7 Engineering Guidelines ...........................................................................................................7-1

7.1 When to Use CSFB ....................................................................................................................... 7-1 7.1.1 CSFB to UTRAN ................................................................................................................... 7-1 7.1.2 CSFB to GERAN .................................................................................................................. 7-1 7.1.3 CSFB to CDMA2000 1xRTT................................................................................................. 7-1 7.1.4 Flash CSFB to UTRAN ......................................................................................................... 7-1 7.1.5 Flash CSFB to GERAN ........................................................................................................ 7-2 7.1.6 CSFB with LAI to UTRAN ..................................................................................................... 7-2 7.1.7 CSFB with LAI to GERAN .................................................................................................... 7-2 7.2 Information to Be Collected ........................................................................................................... 7-2 7.2.1 CSFB to UTRAN ................................................................................................................... 7-2 7.2.2 CSFB to GERAN .................................................................................................................. 7-3 7.2.3 CSFB to CDMA2000 1xRTT................................................................................................. 7-4 7.2.4 Flash CSFB to UTRAN ......................................................................................................... 7-5 7.2.5 Flash CSFB to GERAN ........................................................................................................ 7-6 7.2.6 CSFB with LAI to UTRAN ..................................................................................................... 7-6 7.2.7 CSFB with LAI to GERAN .................................................................................................... 7-7 7.3 Deploying CSFB to UTRAN .......................................................................................................... 7-8 7.3.1 Deployment Requirements ................................................................................................... 7-8 7.3.2 Data Preparation................................................................................................................... 7-9 7.3.3 Precautions ......................................................................................................................... 7-11 7.3.4 Initial Configuration ............................................................................................................. 7-11 7.3.5 Activation Observation ........................................................................................................ 7-12 7.3.6 Deactivation ........................................................................................................................ 7-15 7.4 Deploying CSFB to GERAN ........................................................................................................ 7-15 7.4.1 Deployment Requirements ................................................................................................. 7-15 7.4.2 Data Preparation................................................................................................................. 7-16 7.4.3 Precautions ......................................................................................................................... 7-18 7.4.4 Initial Configuration ............................................................................................................. 7-18 7.4.5 Activation Observation ........................................................................................................ 7-20 7.4.6 Deactivation ........................................................................................................................ 7-20 7.5 Deploying CSFB to CDMA2000 1xRTT ...................................................................................... 7-20 7.5.1 Deployment Requirements ................................................................................................. 7-20 Issue 04 (2012-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ii
eRAN CS Fallback
Contents
7.5.2 Data Preparation................................................................................................................. 7-20 7.5.3 Precautions ......................................................................................................................... 7-22 7.5.4 Initial Configuration ............................................................................................................. 7-22 7.5.5 Activation Observation ........................................................................................................ 7-24 7.5.6 Deactivation ........................................................................................................................ 7-24 7.6 Deploying Flash CSFB to UTRAN .............................................................................................. 7-24 7.6.1 Deployment Requirements ................................................................................................. 7-24 7.6.2 Data Preparation................................................................................................................. 7-25 7.6.3 Precautions ......................................................................................................................... 7-27 7.6.4 Initial Configuration ............................................................................................................. 7-27 7.6.5 Activation Observation ........................................................................................................ 7-29 7.6.6 Deactivation ........................................................................................................................ 7-29 7.7 Deploying Flash CSFB to GERAN .............................................................................................. 7-29 7.7.1 Deployment Requirements ................................................................................................. 7-29 7.7.2 Data Preparation................................................................................................................. 7-29 7.7.3 Precautions ......................................................................................................................... 7-32 7.7.4 Initial Configuration ............................................................................................................. 7-32 7.7.5 Activation Observation ........................................................................................................ 7-34 7.7.6 Deactivation ........................................................................................................................ 7-34 7.8 Deploying CSFB with LAI to UTRAN .......................................................................................... 7-34 7.8.1 Deployment Requirements ................................................................................................. 7-34 7.8.2 Data Preparation................................................................................................................. 7-34 7.8.3 Precautions ......................................................................................................................... 7-34 7.8.4 Initial Configuration ............................................................................................................. 7-34 7.8.5 Activation Observation ........................................................................................................ 7-35 7.8.6 Deactivation ........................................................................................................................ 7-35 7.9 Deploying CSFB with LAI to GERAN .......................................................................................... 7-35 7.9.1 Deployment Requirements ................................................................................................. 7-35 7.9.2 Data Preparation................................................................................................................. 7-36 7.9.3 Precautions ......................................................................................................................... 7-36 7.9.4 Initial Configuration ............................................................................................................. 7-36 7.9.5 Activation Observation ........................................................................................................ 7-36 7.9.6 Deactivation ........................................................................................................................ 7-36 7.10 Performance Optimization ......................................................................................................... 7-36 7.10.1 Monitoring ......................................................................................................................... 7-36 7.10.2 Parameter Optimization .................................................................................................... 7-37 7.10.3 EBC Description ............................................................................................................... 7-41 7.11 Troubleshooting ......................................................................................................................... 7-42 7.11.1 Fault 1 ............................................................................................................................... 7-42 7.11.2 Fault 2 ............................................................................................................................... 7-43 7.11.3 Fault 3 ............................................................................................................................... 7-43 7.11.4 CS Fallback with LAI to UTRAN ....................................................................................... 7-44
Issue 04 (2012-09-20)
iii
eRAN CS Fallback
Contents
7.11.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 04 (2012-09-20)
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:

04 (2012-09-20) 03 (2012-06-30) 02 (2012-05-11) 01 (2012-03-30) Draft A (2012-01-10)
04 (2012-09-20)
Compared with issue 03 (2012-06-30) of eRAN3.0, issue 04 (2012-09-20) of eRAN3.0 includes the following changes. Change Type Feature change Editorial change Change Description None Parameter Change None
Modified some descriptions of initial configuration in chapter None 7 "Engineering Guidelines."
Issue 04 (2012-09-20)
1-1
eRAN CS Fallback
1 Introduction
03 (2012-06-30)
Compared with issue 02 (2012-05-11) of eRAN3.0, issue 03 (2012-06-30) of eRAN3.0 includes the following changes. Change Type Feature change Change Description Parameter Change
Modified the mechanism for an eNodeB to select Added the CsPriority frequencies to measure or a target cell. For details, see parameter. section 4.1.2 "Selecting Frequencies to Measure or a Target Cell (Without an LAI)." Modified some descriptions in sections 4.1.1 "Choosing Between a Blind Handover and a Measurement-based Handover" and 4.4 "Execution Phase of CSFB." None
Editorial change
02 (2012-05-11)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-05-11) of eRAN3.0 includes the following changes. Change Type Feature change Change Description Parameter Change
Added the UTRAN frequency layer measurement function. Added the For details, see section 4.1.2 "Selecting Frequencies to FreqLayerSwtich Measure or a Target Cell (Without an LAI)." parameter. Modified some descriptions. None
Editorial change
01 (2012-03-30)
This is the first official release. Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the following changes. Change Type Feature change Change Description Parameter Change
Modified the RAN information management (RIM) None procedure during which the eNodeB obtains the system information of the neighboring GERAN or UTRAN cells. For details, see sections 3.1.6 "RAN Information Management Procedure" and 3.2.6 "RAN Information Management Procedure." Revised chapter 7 "Engineering Guidelines." None
Editorial change
Draft A (2012-01-10)
This is a draft. Compared with issue 02 (2011-09-30) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the following changes.
Issue 04 (2012-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-2
eRAN CS Fallback
1 Introduction
Change Type Feature change
Change Description
Parameter Change
Added the description of how the eNodeB performs CSFB None based on an LAI. For details, see sections 4.1.3 "Selecting Frequencies to Measure or a Target Cell (With an LAI) " and 4.3 "Decision Phase of CSFB."
Editorial change
Optimized the organization and description of this document. Added chapters 5 "Related Features" and 6 "Impact on the Networks."
None
Issue 04 (2012-09-20)
1-3
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.
Issue 04 (2012-09-20)
2-1
eRAN CS Fallback
2 Overview of CSFB
Table 2-1 Optional features related to CSFB and corresponding chapters Feature 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 Its Basic Principles Are Described in... 3.1 "CSFB to UTRAN" 3.2 "CSFB to GERAN" 3.3 "CSFB to CDMA2000 1xRTT" 3.1.6 "RAN Information Management Procedure" 3.2.6 "RAN Information Management Procedure" Its Algorithm Details Are Described in... 4 "CSFB at the eNodeB" 4 "CSFB at the eNodeB" 4 "CSFB at the eNodeB" 4 "CSFB at the eNodeB" 4 "CSFB at the eNodeB" 4.1.3 "Selecting Frequencies to Measure or a Target Cell (With an LAI)" 4.1.3 "Selecting Frequencies to Measure or a Target Cell (With an LAI)"
LOFD-001068 CS 3.1 "CSFB to UTRAN" Fallback with LAI to UTRAN LOFD-001069 CS 3.2 "CSFB to GERAN" Fallback with LAI to GERAN
2.1 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. 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.
Issue 04 (2012-09-20)
2-2
eRAN CS Fallback
2 Overview of CSFB
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 SGs interface Function

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

UE
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.
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.
Issue 04 (2012-09-20)
2-3
eRAN CS Fallback
2 Overview of CSFB
Element E-UTRAN
Function

Forwards paging messages related to CSFB. Selects target cells for CSFB for E-UTRAN UEs. Supports one or more of the following functions:
PS PS
redirection to UTRAN or GERAN, if PS redirection is used as the CSFB mechanism handover to UTRAN or GERAN, if PS handover is used as the CSFB mechanism 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 for acquiring the system information of UTRAN or GERAN cells, in addition to PS redirection, if flash CSFB is used as the CSFB mechanism
CCO
RIM
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.
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 3GPP TS 23.401.
2.2 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.
Issue 04 (2012-09-20)
2-4
eRAN CS Fallback
2 Overview of CSFB
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. Table 2-3 Elements of the network architecture for CSFB to CDMA2000 1xRTT Element S102 interface Function

Acts as an interface between the MME and the 1xCS IWS. Provides a tunnel to carry 1xCS signaling. 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. 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.
UE
MME
Issue 04 (2012-09-20)
2-5
eRAN CS Fallback
2 Overview of CSFB
Element E-UTRAN
Function
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.
Issue 04 (2012-09-20)
2-6
eRAN CS Fallback
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

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
Issue 04 (2012-09-20)
3-1
eRAN CS Fallback
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 3GPP TS 23.401. 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 CSFB based on PS handover CSFB based on PS redirection Flash CSFB Impact on the Networks Complex Simple Medium Impact on the CS Service UEs Access Delay Complex Simple Medium Short Long Short PS Service Interruption Time Short Long Medium
Issue 04 (2012-09-20)
3-2
eRAN CS Fallback
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."
Issue 04 (2012-09-20)
3-3
eRAN CS Fallback
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 3GPP TS 23.401.
CSFB Procedure for Mobile-terminated Calls This section describes the procedure for CSFB to UTRAN based on PS handover for mobile-terminated calls, as shown in Figure 3-3. Figure 3-3 CSFB to UTRAN based on PS handover for mobile-terminated calls
The procedure is described as follows: 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 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. 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.
Issue 04 (2012-09-20)
3-4
eRAN CS Fallback
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. CSFB Procedure for Mobile-originated Calls This section describes the procedure for CSFB to UTRAN based on PS redirection for mobile-originated calls, as shown in Figure 3-4. Figure 3-4 CSFB to UTRAN based on PS redirection for mobile-originated calls
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 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
Issue 04 (2012-09-20)
3-5
eRAN CS Fallback
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. CSFB Procedure for Mobile-terminated Calls 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. CSFB Procedure for Mobile-originated Calls 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
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."
Issue 04 (2012-09-20)
3-6
eRAN CS Fallback
4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target UTRAN frequency, as well as one or more physical cell identities and their associated system information. Then, the eNodeB initiates an S1 UE context release procedure.
NOTE
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details, see chapter 4 "CSFB 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."
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. CSFB Procedure for Mobile-terminated Calls 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 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 3GPP TS 23.272.
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.
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.
Issue 04 (2012-09-20)
3-7
eRAN CS Fallback
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 3GPP TS 23.272 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 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 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. If flash CSFB to UTRAN is enabled and UTRAN_RIM_SWITCH under the 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

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."
Issue 04 (2012-09-20)
3-8
eRAN CS Fallback
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 CSFB based on PS redirection CSFB based on PS handover CSFB based on CCO/NACC Flash CSFB Impact on the Networks Simple Complex Medium Medium Impact on the CS Service UEs Access Delay Simple Complex Medium Medium Long Short Medium Short PS Service Interruption Time Long Short Medium 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. CSFB Procedure for Mobile-originated Calls This section describes the procedure for CSFB to GERAN based on PS redirection for mobile-originated calls, as shown in Figure 3-7.
Issue 04 (2012-09-20)
3-9
eRAN CS Fallback
Figure 3-7 CSFB to GERAN based on PS redirection for mobile-originated calls
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 sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target GERAN carrier frequency group. Then, the eNodeB initiates an S1 UE context release procedure.
NOTE
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target cell. 6. 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. CSFB Procedure for Mobile-terminated Calls 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 GERAN based on PS redirection for mobile-originated calls.
Issue 04 (2012-09-20)
3-10
eRAN CS Fallback
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. CSFB Procedure for Mobile-originated Calls This section describes the procedure for CSFB to GERAN based on PS handover for mobile-originated calls, as shown in Figure 3-8. Figure 3-8 CSFB to GERAN based on PS handover for mobile-originated calls
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.
Issue 04 (2012-09-20)
3-11
eRAN CS Fallback
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
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. CSFB Procedure for Mobile-terminated Calls 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 GERAN 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. CSFB Procedure for Mobile-originated Calls This section describes the procedure for CSFB to GERAN based on CCO/NACC for mobile-originated calls, as shown in Figure 3-9.
Issue 04 (2012-09-20)
3-12
eRAN CS Fallback
Figure 3-9 CSFB to GERAN based on CCO/NACC for mobile-originated calls
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 sends a Mobility From EUTRA Command message over the Uu interface to indicate the operating frequency and ID of the target GERAN cell. If the source cell has the system information of the target cell, the system information is also carried in the message.
NOTE
5. The 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. 8. The UE initiates a CS call establishment procedure in the target GERAN cell. CSFB Procedure for Mobile-terminated Calls 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
Issue 04 (2012-09-20)
3-13
eRAN CS Fallback
in Figure 3-3. The subsequent steps are the same as the steps in the procedure for CSFB to GERAN 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. CSFB Procedure for Mobile-originated Calls 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
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 sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target GERAN carrier frequency group, as well as one or
Issue 04 (2012-09-20)
3-14
eRAN CS Fallback
more physical cell identities and their associated system information. Then, the eNodeB initiates an S1 UE context release procedure.
NOTE
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target cell. 6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are suspended. 7. The UE initiates a CS call establishment procedure in the target GERAN cell. CSFB Procedure for Mobile-terminated Calls 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 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 3GPP TS 23.272.

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 Parameter Description.
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 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.
Issue 04 (2012-09-20)
3-15
eRAN CS Fallback
For details about the CSFB procedure for LCS, see 3GPP TS 23.272 and LCS Feature Parameter Description.
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 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 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. If flash CSFB to GERAN or CCO/NACC is enabled but GERAN_RIM_SWITCH under the 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.
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.
Issue 04 (2012-09-20)
3-16
eRAN CS Fallback
Figure 3-11 Preregistration procedure for CSFB to CDMA2000 1xRTT
The procedure is described as follows: 1. The UE is attached to the E-UTRAN. For details about the attach procedure, see 3GPP TS 23.401. 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 cdma2000 Tunnelling
DL S1 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.
Issue 04 (2012-09-20)
3-17
eRAN CS Fallback
Figure 3-12 CSFB to CDMA2000 1xRTT for mobile-originated calls
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 containing a CS Fallback Indicator, instructing the eNodeB to initiate a CSFB procedure. 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 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.
Issue 04 (2012-09-20)
3-18
eRAN CS Fallback
Figure 3-13 CSFB to CDMA2000 1xRTT for mobile-terminated calls
The procedure is described as follows: 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. 2. The UE sends the MME an NAS message Extended Service Request to initiate a CS service. 3. The MME sends an S1-AP Request message containing a CS Fallback Indicator, instructing the eNodeB to initiate a CSFB procedure. 4. 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." 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.
Issue 04 (2012-09-20)
3-19
eRAN CS Fallback
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.
Issue 04 (2012-09-20)
3-20
eRAN CS Fallback
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.
Issue 04 (2012-09-20)
4-1
eRAN CS Fallback
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 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 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. If the BlindHoSwitch check box under the HoModeSwitch parameter is cleared and the UE is incapable of measuring an RAT, the eNodeB directly performs CSFB in the form of a blind handover. If the BlindHoSwitch check box under the HoModeSwitch parameter is selected, the eNodeB directly performs CSFB in the form of a blind handover.
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
If LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is disabled or UtranFreqLayerBlindSwitch is turned off, 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. UtranFreqLayerBlindSwitch is a switch under the FreqLayerSwtich parameter. The priorities of RATs used in blind handovers for CSFB are specified through the InterRatHighestPri, InterRatSecondPri, and InterRatLowestPri parameters. The blind-handover priority of an inter-RAT neighboring cell is specified through the EUTRANINTERFREQNCELL.BlindHoPriority parameter. If LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is enabled and UtranFreqLayerBlindSwitch is turned on, the eNodeB first selects an RAT with the highest blind-handover priority. If the selected RAT is UTRAN, the eNodeB selects a target cell for the blind handover as follows:
If there are UE-supported frequencies with the high CS service priority, the eNodeB selects the cell with the highest blind-handover priority among the cells on these frequencies. The CS service priorities are specified by the CsPriority parameter. If there are not frequencies with the high CS service priority or the UE does not support frequencies with the high CS service priority, the eNodeB selects the cell with the highest blind-handover priority among the cells on the frequencies with the low CS service priority.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-2
Issue 04 (2012-09-20)
eRAN CS Fallback
In a Measurement-based Handover
If LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is disabled or UtranFreqLayerMeasSwitch is turned off, 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. UtranFreqLayerMeasSwitch is a switch under the FreqLayerSwtich parameter. If LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is enabled and UtranFreqLayerMeasSwitch is turned on, measurements vary as follows:
If there are UE-supported frequencies with the high CS service priority, measurements will be performed on frequencies with the high CS service priority, but not on frequencies with the low CS service priority even after measurements fail for the frequencies with the high CS service priority. If there are not frequencies with the high CS service priority, the UE does not support the frequencies with the high CS service priority, or no cell in the neighboring UTRAN cell list operates on the frequencies with the high CS service priority, then measurements will be performed on frequencies with the low CS service priority.
NOTE
UtranFreqLayerMeasSwitch controls only UTRAN frequencies but not GERAN frequencies, and therefore the eNodeB decides whether to instruct the UE to perform measurements only based on whether the UE supports the GERAN and GERAN frequencies.
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. If UTRAN is selected, LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is enabled, and UtranFreqLayerMeasSwitch is turned on, the eNodeB selects the target cell by performing the following steps: 1. Listing neighboring cells with the same PLMN ID as that indicated in the received LAI. 2. Choosing neighboring cells with high CS service priorities among the cells listed in 1. 3. Preferentially selecting neighboring cells with the same LAC as that indicated in the received LAI.
Issue 04 (2012-09-20)
4-3
eRAN CS Fallback
If there are multiple cells after the preceding steps, the eNodeB proceeds with the procedure as described in the case of a blind handover.
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)."
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. 3GPP TS 36.331 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 The The
received signal code power (RSCP) threshold for CSFB to UTRAN is specified by CsfbHoUtranB1ThdRscp. Ec/No threshold for CSFB to UTRAN is specified by CsfbHoUtranB1ThdEcn0. received signal strength indicator (RSSI) threshold for CSFB to GERAN is specified by CsfbHoGeranB1Thd.
Issue 04 (2012-09-20)
4-4
eRAN CS Fallback
The
pilot strength threshold for CSFB to CDMA2000 1xRTT is specified by 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 CsfbHoUtranTimeToTrig, CsfbHoGeranTimeToTrig, and 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.
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

Table 4-1 lists the mechanisms that are available for CSFB to UTRAN, GERAN, and CDMA2000 1xRTT. These mechanisms are laid out in descending order of priority. The applicable mechanisms are specified by the HoModeSwitch parameter. The eNodeB selects a mechanism based on both the UE capability and mechanism priority. For example, if the switch controlling PS handover from E-UTRAN to UTRAN is turned on but the UE does not support PS handover, the eNodeB checks whether the UE supports the mechanism with the second-highest priority. This process stops when the eNodeB selects a mechanism that the UE supports. Table 4-1 CSFB mechanisms Target Network UTRAN Mechanisms (in Descending Order of Priority)

PS handover Flash CSFB Redirection
Issue 04 (2012-09-20)
4-5
eRAN CS Fallback
Target Network GERAN
Mechanisms (in Descending Order of Priority)

PS handover CCO/NACC Flash CSFB Redirection
CDMA2000 1xRTT
Redirection
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 fixedly set to 4 seconds.
Issue 04 (2012-09-20)
4-6
eRAN CS Fallback
5 Related Features
5 Related Features
5.1 Required Features
As with an inter-RAT handover procedure, a typical CSFB procedure also includes the measurement phase, decision phase, and execution phase. The interactions between NEs in the three phases are the same for the two types of procedure. Therefore, the features related to CSFB depend on those related to inter-RAT handovers. In addition, among the features related to CSFB, the enhanced ones depend on the fundamental ones. The dependencies are described as follows:

LOFD-001033 CS Fallback to UTRAN depends on LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN. LOFD-001034 CS Fallback to GERAN depends on LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN. LOFD-001035 CS Fallback to CDMA2000 1xRTT depends on LOFD-001021 PS Inter-RAT Mobility between E-UTRAN and CDMA2000. LOFD-001052 Flash CS Fallback to UTRAN depends on LOFD-001033 CS Fallback to UTRAN. LOFD-001053 Flash CS Fallback to GERAN depends on LOFD-001034 CS Fallback to GERAN. LOFD-001068 CS Fallback with LAI to UTRAN depends on LOFD-001033 CS Fallback to UTRAN. LOFD-001069 CS Fallback with LAI to GERAN depends on LOFD-001034 CS Fallback to GERAN.
5.2 Mutually Exclusive Features

None
5.3 Affected Features

If the handover switch is turned on in LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN, and UEs support mobility from the E-UTRAN to the UTRAN, LOFD-001052 Flash CS Fallback to UTRAN will be disabled. That is, all inter-RAT procedures to the UTRAN including CSFB will preferentially be performed based on handovers if handovers to the UTRAN is enabled and UEs are capable of such handovers. If the handover switch is turned on in LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN, and the UE supports mobility from the E-UTRAN to the GERAN, LOFD-001053 Flash CS Fallback to GERAN will be disabled. That is, all inter-RAT procedures to the GERAN including CSFB will preferentially be based on handovers if the handover to the GERAN is enabled and the UE is capable of such handover.
Issue 04 (2012-09-20)
5-1
eRAN CS Fallback
6 Impact on the Networks
6 Impact on the Networks

6.1 Impact on System Capacity
In essence, CSFB provides CS service access for E-UTRAN UEs. Considering that the number of UEs requesting CS services within an area is relatively stable and has no correlation with the deployment of the EPS, CSFB has no impact on the total number of UEs requesting CS services within a network. CSFB mechanisms affect signaling overheads as follows:
If redirection or CCO without NACC is used as the CSFB mechanism, no extra signaling message is required from the target network or from the EPS. For the target network, a redirection or CCO-without-NACC procedure is equivalent to the initiation of a new CS service. Therefore, it does not require extra signaling. For the EPS, it does not need to interact with the target network. Therefore, the signaling overhead is negligibly low. If flash CSFB or CCO with NACC is used as the CSFB mechanism, extra signaling is required only during eNodeB deployment. From that time onwards, the signaling overhead is negligibly low because of infrequent system information updates. If PS handover is used as the CSFB mechanism, extra signaling is required from each NE in the request, preparation, and execution of each handover. However, from the perspective of traffic statistics, the number of UEs initiating CS services per second per cell during peak hours is far below the cell capacity. Therefore, the signaling overhead caused by PS handovers is low.
6.2 Impact on Network Performance

CSFB affects the access success rate as follows:
If redirection, CCO/NACC, or flash CSFB is used as the CSFB mechanism, each CSFB 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. 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 corresponding RAT. It is a little lower than the access success rate for normal CS UEs. The cause of this drop is that handover-triggered CS service access has a higher requirement for signal quality compared with normal CS service access.
Issue 04 (2012-09-20)
6-1
eRAN CS Fallback
7 Engineering Guidelines
7.1 When to Use CSFB
7.1.1 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 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. 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 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 handover to decrease the CSFB delay.
7.1.3 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. 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 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.
7.1.4 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.
Issue 04 (2012-09-20)
7-1
eRAN CS Fallback
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.5 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.
For policies on whether to use PS handover or PS redirection for CSFB, see Mobility Management in 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 handover to decrease the CSFB delay.
7.1.6 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).
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.
7.1.7 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.
7.2 Information to Be Collected

7.2.1 CSFB to UTRAN

Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and UTRAN cells. 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.
Issue 04 (2012-09-20)
7-2
eRAN CS Fallback
Table 7-1 Requirements of CSFB to UTRAN for the core networks NE MME Description 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:

Combined EPS/IMSI attach SMS over SGs Paging message forwarding over the SGs interface
SGSN
Does not activate ISR during the combined RAU/LAU procedure initiated by the UE.
Collect the following information about the UEs supporting UMTS and LTE on the live network:
Supported Whether Whether Whether
frequency bands
the UEs support redirection from E-UTRAN to UTRAN the UEs support PS handover from E-UTRAN to UTRAN 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 Feature Parameter Description.
7.2.2 CSFB to GERAN

Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and GERAN cells. 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-2 describes the requirements of CSFB to GERAN for the core networks.
Issue 04 (2012-09-20)
7-3
eRAN CS Fallback
Table 7-2 Requirements of CSFB to GERAN for the core networks NE MME Description 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:

SGSN
Collect the following information about the UEs supporting GSM and LTE on the live network:
frequency bands
the UEs support redirection from E-UTRAN to GERAN the UEs support PS handover from E-UTRAN to GERAN the UEs support GERAN measurements
This information is used to configure neighboring GERAN cells and to determine whether to perform CSFB based on handover or redirection. For details, see Mobility Management in Connected Mode Feature Parameter Description.
7.2.3 CSFB to CDMA2000 1xRTT

Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and CDMA2000 1xRTT cells. 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-3 describes the requirements of CSFB to CDMA2000 1xRTT for the core networks.
Table 7-3 Requirements of CSFB to CDMA2000 1xRTT for the core networks NE MME Description 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
Issue 04 (2012-09-20)
7-4
eRAN CS Fallback
Collect the following information about the UEs supporting CDMA2000 and LTE on the live network:
frequency bands
the UEs support redirection from E-UTRAN to CDMA2000 the UEs support PS handover from E-UTRAN to CDMA2000 the UEs support CDMA2000 measurements
This information is used to configure neighboring CDMA2000 cells and to determine whether to perform CSFB based on handover or redirection. For details, see Mobility Management in Connected Mode Feature Parameter Description.
7.2.4 Flash CSFB to UTRAN

Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and UTRAN cells. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks, and ensure that they all support CSFB and the RIM procedure. Table 7-4 describes the requirements of flash CSFB to UTRAN for the core networks.
Table 7-4 Requirements of flash CSFB to UTRAN for the core networks NE MME Description 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 RIM procedures
MSC
Supports:

Combined EPS/IMSI attach SMS over SGs Paging message forwarding over the SGs interface Does not activate ISR during the combined RAU/LAU procedure initiated by the UE. Supports RIM procedures.
SGSN
Supported Whether Whether Whether Whether
frequency bands
the UEs support redirection from E-UTRAN to UTRAN the UEs support PS handover from E-UTRAN to UTRAN the UEs support UTRAN measurements the UEs comply with 3GPP Release 9 specifications
Issue 04 (2012-09-20)
7-5
eRAN CS Fallback
7.2.5 Flash CSFB to GERAN

Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and GERAN cells. Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core networks, and ensure that they all support CSFB and the RIM procedure. Table 7-5 describes the requirements of flash CSFB to GERAN for the core networks.
Table 7-5 Requirements of flash CSFB to GERAN for the core networks NE MME Description 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 RIM procedures
MSC
Supports:

Combined EPS/IMSI attach SMS over SGs Paging message forwarding over the SGs interface Does not activate ISR during the combined RAU/LAU procedure initiated by the UE. Supports RIM procedures.
SGSN
Supported Whether Whether Whether Whether
frequency bands
the UEs support redirection from E-UTRAN to GERAN the UEs support PS handover from E-UTRAN to GERAN the UEs support GERAN measurements the UEs comply with 3GPP Release 9 specifications
7.2.6 CSFB with LAI to UTRAN
Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and UTRAN cells.
Issue 04 (2012-09-20)
7-6
eRAN CS Fallback
Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks, and ensure that they all support CSFB and the MME supports LAI delivery. Table 7-6 describes the requirements of CSFB with LAI to UTRAN for the core networks.
Table 7-6 Requirements of CSFB with LAI to UTRAN for the core networks NE MME Description 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 LAI delivery
MSC
Supports:

SGSN
frequency bands
the UEs support redirection from E-UTRAN to UTRAN the UEs support PS handover from E-UTRAN to UTRAN the UEs support UTRAN measurements
7.2.7 CSFB with LAI to GERAN

Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and GERAN cells. Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core networks, and ensure that they all support CSFB and the MME supports LAI delivery. Table 7-7 describes the requirements of CSFB with LAI to GERAN for the core networks.
Issue 04 (2012-09-20)
7-7
eRAN CS Fallback
Table 7-7 Requirements of CSFB with LAI to GERAN for the core networks NE MME Description 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 LAI delivery
MSC
Supports:

SGSN
frequency bands
the UEs support redirection from E-UTRAN to GERAN the UEs support PS handover from E-UTRAN to GERAN the UEs support GERAN measurements
7.3 Deploying CSFB to UTRAN

7.3.1 Deployment Requirements
Requirements for the Operating Environment
For this feature, the eNodeB must collaborate with core-network equipment.

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

Operators must purchase and activate the following license.
Issue 04 (2012-09-20)
7-8
eRAN CS Fallback
Table 7-8 License control item for CSFB to UTRAN Feature LOFD-001033 CS Fallback to UTRAN License Control Item Name CS Fall Back to UTRAN License Control Item ID LLT1CFBU01
7.3.2 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. 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.
Issue 04 (2012-09-20)
7-9
eRAN CS Fallback
Parameter Name
Parameter ID
Source
Setting Description
Handover HoModeSwitch Network plan Set this parameter based on the network plan. Mode switch (negotiation not To activate PS handovers, select the 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 Algo switch
HoAlgoSwitch Network plan To activate CSFB to UTRAN, select the (negotiation not UtranCsfbSwitch(UtranCsfbSwitch) check box. 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. Parameter Parameter ID Name CN Operator ID Highest priority InterRat Source Setting Description
CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This CnOperatorId (negotiation parameter specifies the ID of the operator whose not required) RAT blind-handover priorities are to be set. InterRatHighestPri Network plan Set this parameter based on the network plan. This (negotiation parameter is set to UTRAN by default and specifies not required) the high-priority RAT to be considered in blind handovers for CSFB. For CSFB to UTRAN, retain the default value. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to GERAN by default and specifies 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 InterRatHighestPri and InterRatLowestPri parameters. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to CDMA2000 by default and 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 InterRatHighestPri and InterRatSecondPri parameters.
Second priority InterRat
InterRatSecondPri
Lowest priority InterRat
InterRatLowestPri
Issue 04 (2012-09-20)
7-10
eRAN CS Fallback
Parameter Parameter ID Name UTRAN UtranLcsCap LCS capability
Source
Setting Description
Network plan Set this parameter based on the network plan. This (negotiation parameter specifies the LCS capability of the not required) UTRAN.
7.3.3 Precautions
None
7.3.4 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.3.2 "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-9, and save the parameter settings as a user-defined template. The parameters are the same as those described in section 7.3.2 "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. Table 7-9 Parameters for CSFB to UTRAN MO UTRANNFREQ Parameter Group Name UtranNFreq Parameter Local cell identity, Downlink UARFCN
Issue 04 (2012-09-20)
7-11
eRAN CS Fallback
MO
Parameter Group Name
Parameter Mobile country code, Mobile network code, UTRAN cell identity, Downlink UARFCN, RNC identity, Primary scrambling code, Location area code
UTRANEXTERNA UtranExternalCell LCELL
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 Handover Algo switch, Handover Mode switch
ENODEBALGOS ENodeBAlgoSwitch 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 Parameter Description. 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.3.5 Activation Observation

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.
Issue 04 (2012-09-20)
7-12
eRAN CS Fallback
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.
Figure 7-1 CSFB to UTRAN for a mobile-originated call
Issue 04 (2012-09-20)
7-13
eRAN CS Fallback
Figure 7-2 CSFB to UTRAN for a mobile-terminated call
If measurement-based redirection is used for CSFB to UTRAN, the eNodeB delivers the B1-related measurement configuration. If blind redirection is used for CSFB to UTRAN, the eNodeB does not deliver the B1-related measurement configuration but sends an RRC Connection Release (RRC Conn Rel in the figures) message to the UE. The procedures indicated by dashed lines are optional. During the redirection, the eNodeB initiates a UE capability enquiry procedure if the UE capability is not included in the Initial Context Setup Request (Initial Context Setup Req in the figures) message received from the MME. If the UE capability is included, the eNodeB does not initiate this procedure. 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.
Issue 04 (2012-09-20)
7-14
eRAN CS Fallback
Figure 7-3 PS handover procedure
----End
7.3.6 Deactivation
Run the MOD ENODEBALGOSWITCH command with the UtranCsfbSwitch(UtranCsfbSwitch) check box under the HoAlgoSwitch parameter cleared.
7.4 Deploying CSFB to GERAN



Operators must purchase and activate the following license. Table 7-10 License control item for CSFB to GERAN Feature LOFD-001034 CS Fallback to GERAN License Control Item Name CS Fall Back to GERAN License Control Item ID LLT1CFBG01
Issue 04 (2012-09-20)
7-15
eRAN CS Fallback


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. Collect data for the parameters in the following MOs:

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 supports blind handovers according to the network plan, the blind-handover priority of the cell must be specified by the GeranNcell.BlindHoPriority parameter.
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 GERAN.
Issue 04 (2012-09-20)
7-16
eRAN CS Fallback
Parameter Name
Parameter ID
Source
Setting Description Set this parameter based on the network plan.
Network plan Handover HoModeSwitch (negotiation If none of the preceding check boxes is selected, Mode switch not required) redirection will be used for CSFB to GERAN. 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 Algo switch HoAlgoSwitch Network plan To activate CSFB to GERAN, select the (negotiation GeranCsfbSwitch(GeranCsfbSwitch) check box. not required)
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.
CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This CnOperatorId (negotiation parameter specifies the ID of the operator whose not required) RAT blind-handover priorities are to be set. InterRatHighestPri Network plan Set this parameter based on the network plan. This (negotiation parameter is set to UTRAN by default and specifies not required) the high-priority RAT to be considered in blind handovers for CSFB. For CSFB to GERAN, set this parameter to GERAN. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to GERAN by default and specifies not required) the medium-priority RAT to be considered in blind handovers for CSFB. If the 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 InterRatHighestPri and InterRatLowestPri parameters.
InterRatSecondPri
Issue 04 (2012-09-20)
7-17
eRAN CS Fallback
Parameter Parameter ID Name Lowest priority InterRat InterRatLowestPri
Source
Setting Description
Network plan Set this parameter based on the network plan. This (negotiation parameter is set to CDMA2000 by default and 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 InterRatHighestPri and InterRatSecondPri parameters. Network plan Set this parameter based on the network plan. This (negotiation parameter specifies the LCS capability of the not required) GERAN.
GERAN GeranLcsCap LCS capability
7.4.3 Precautions
None



To configure eNodeBs in batches, perform the following steps: Step 1 On the GUI, set the parameters listed in Table 7-11, and save the parameter settings as a user-defined template. The parameters are the same as those described in section 7.4.2 "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.
Issue 04 (2012-09-20)
7-18
eRAN CS Fallback
Table 7-11 Parameters for CSFB to GERAN MO GERANNFREQGROUP Parameter Group Name GeranNfreqGroup Parameter 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 Handover Algo switch, Handover Mode switch
ENODEBALGOSWITCH CSFALLBACKBLINDHOCFG
ENodeBAlgoSwitch
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 For details about parameter settings, see Mobility Management in Connected Mode Feature Parameter Description. Step 2 Run the MOD ENODEBALGOSWITCH command to set the handover mode and handover algorithm switches for CSFB to GERAN. Step 3 Run the MOD CSFALLBACKBLINDHOCFG command to set the blind-handover priorities of different RATs for CSFB. ----End
Issue 04 (2012-09-20)
7-19
eRAN CS Fallback

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 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.3.5 "Activation Observation." ----End
7.4.6 Deactivation
Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) check box under the HoAlgoSwitch parameter cleared.
7.5 Deploying CSFB to CDMA2000 1xRTT



Operators must purchase and activate the following license. Table 7-12 License control item for CSFB to CDMA2000 1xRTT Feature License Control Item Name License Control Item ID LLT1CFBR01
LOFD-001035 CS Fallback CS Fall Back to CDMA2000 1xRTT(FDD) to CDMA2000 1xRTT


Issue 04 (2012-09-20)
7-20
eRAN CS Fallback
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. Collect data for the parameters in the following MOs:

Cdma2000BandClass: used to configure CDMA2000 band classes Cdma2000Nfreq: used to configure CDMA2000 frequencies 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.
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 CDMA2000 1xRTT. Parameter Name Parameter ID Source Setting Description
Handover HoModeSwitch Network plan Set this parameter based on the network plan. Mode switch (negotiation not To activate redirection for CSFB to CDMA2000 required) 1xRTT, select the Cdma1xRttRedirectSwitch(Cdma1xRttRedirectSwi tch) check box.
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.
To activate CSFB to CDMA2000 1xRTT, select the HoAlgoSwitch Network plan (negotiation not Cdma1xRttCsfbSwitch(Cdma1xRttCsfbSwitch) required) check box.
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.
Issue 04 (2012-09-20)
7-21
eRAN CS Fallback
Parameter Parameter ID Name
Source
Setting Description
CN CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This Operator ID CnOperatorId (negotiation parameter specifies the ID of the operator whose not required) RAT blind-handover priorities are to be set. Highest priority InterRat InterRatHighestPri Network plan Set this parameter based on the network plan. This (negotiation parameter is set to UTRAN by default and 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. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to GERAN by default and 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 InterRatHighestPri and InterRatLowestPri parameters. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to CDMA2000 by default and 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 InterRatHighestPri and InterRatSecondPri parameters. Network plan Set this parameter based on the network plan. This (negotiation parameter specifies the LCS capability of the not required) CDMA2000 1xRTT network.
InterRatSecondPri
InterRatLowestPri
CDMA2000 CdmaLcsCap LCS capability
7.5.3 Precautions
None


Issue 04 (2012-09-20)
7-22
eRAN CS Fallback

To configure eNodeBs in batches, perform the following steps: Step 1 On the GUI, set the parameters listed in Table 7-13, and save the parameter settings as a user-defined template. The parameters are the same as those described in section 7.5.2 "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. Table 7-13 Parameters for CSFB to CDMA2000 1xRTT MO CDMA2000BANDCLASS CDMA2000NFREQ CDMA2000EXTERNALCELL Parameter Group Name Cdma2000BandClass Cdma2000Nfreq Cdma2000ExternalCell Parameter Local cell identity, Band class Local cell identity, Band class, Frequency Sector identity, Band class, Frequency, Physical cell identity, CDMA2000 neighbor cell type, Mobile country code, Mobile network code
CDMA2000EXTERNALCELLPLMN Cdma2000ExternalCellPlmn Sector identity, Share mobile country code, Share mobile network code CDMA20001XRTTNCELL ENODEBALGOSWITCH CSFALLBACKBLINDHOCFG Cdma20001xrttNcell ENodeBAlgoSwitch CSFallBackBlindHoCfg Local cell identity, Sector identity, Blind handover priority Handover Algo switch, Handover Mode switch CN Operator ID, Highest priority InterRat, 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
Issue 04 (2012-09-20)
7-23
eRAN CS Fallback
For details about parameter settings, see Mobility Management in Connected Mode Feature Parameter Description. Step 2 Run the MOD ENODEBALGOSWITCH command to set the handover mode and handover algorithm switches for CSFB to CDMA2000 1xRTT. Step 3 Run the MOD CSFALLBACKBLINDHOCFG command to set the blind-handover priorities of different RATs for CSFB. ----End

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 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.3.5 "Activation Observation." ----End
7.5.6 Deactivation
Run the MOD ENODEBALGOSWITCH command with the Cdma1xRttCsfbSwitch(Cdma1xRttCsfbSwitch) check box under the HoAlgoSwitch parameter cleared.
7.6 Deploying Flash CSFB to UTRAN



Operators must purchase and activate the following licenses. Table 7-14 License control item for flash CSFB to UTRAN Feature LOFD-001033 CS Fallback to UTRAN LOFD-001052 Flash CS Fallback to UTRAN License Control Item Name License Control Item ID CS Fall Back to UTRAN LLT1CFBU01
Flash CS Fallback to UTRAN LLT1FCFBU01
Issue 04 (2012-09-20)
7-24
eRAN CS Fallback
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 5.3 "Affected Features."


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 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. 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.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the handover mode and handover algorithm switches for flash CSFB to UTRAN. Parameter Name Parameter ID Source Setting Description
Handover HoModeSwitch Network plan Set this parameter based on the network plan. Mode switch (negotiation To activate blind handovers, select the 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 success rates.
Issue 04 (2012-09-20)
7-25
eRAN CS Fallback
Parameter Name Handover Algo switch
Parameter ID
Source
Setting Description
HoAlgoSwitch Network plan To activate flash CSFB to UTRAN, select the (negotiation UtranCsfbSwitch(UtranCsfbSwitch) and not required) UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check boxes. RimSwitch Network plan UTRAN_RIM_SWITCH under this parameter (negotiation specifies whether to enable or disable the RIM procedure not required) that requests event-driven multiple reports from UTRAN cells.
RIM switch
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 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.
CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. CnOperatorId (negotiation This parameter specifies the ID of the not required) operator whose RAT blind-handover priorities are to be set. InterRatHighestPri Network plan Set this parameter based on the network plan. (negotiation This parameter is set to UTRAN by default and not required) specifies the high-priority RAT to be considered in blind handovers for CSFB. For flash CSFB to UTRAN, retain the default value.
Issue 04 (2012-09-20)
7-26
eRAN CS Fallback
Parameter Parameter ID Name Second priority InterRat InterRatSecondPri
Source
Setting Description
Network plan Set this parameter based on the network plan. (negotiation This parameter is set to GERAN by default and 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 InterRatHighestPri and InterRatLowestPri parameters. Network plan Set this parameter based on the network plan. (negotiation This parameter is set to CDMA2000 by default and 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 InterRatHighestPri and InterRatSecondPri parameters. Network plan Set this parameter based on the network plan. (negotiation This parameter specifies the LCS capability of the not required) UTRAN.
InterRatLowestPri
UTRAN LCS capability
UtranLcsCap
7.6.3 Precautions
None



To configure eNodeBs in batches, perform the following steps: Step 1 On the GUI, set the parameters listed in Table 7-15, and save the parameter settings as a user-defined template. The parameters are the same as those described in section 7.6.2 "Data Preparation." Step 2 Fill in the summary data file with the name of the user-defined template.
Issue 04 (2012-09-20)
7-27
eRAN CS Fallback
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. Table 7-15 Parameters for flash CSFB to UTRAN MO UTRANNFREQ Parameter Group Name Parameter UtranNFreq Local cell identity, Downlink UARFCN Mobile country code, Mobile network code, UTRAN cell identity, Downlink UARFCN, RNC identity, Routing area code configure indicator, Routing area code, Primary scrambling code, Location area code UTRAN cell identity, Mobile country code, Mobile network code, Share mobile country code, Share mobile network code Local cell identity, Mobile country code, Mobile network code, UTRAN cell identity, Blind handover priority Handover Algo switch, Handover Mode switch, Redirection switch, RIM switch CN Operator ID, Highest priority InterRat, Second priority InterRat, Lowest priority InterRat, UTRAN LCS capability
UTRANEXTERN UtranExternalCell ALCELL
UTRANEXTERN UtranExternalCellPlmn ALCELLPLMN UTRANNCELL UtranNCell
ENODEBALGOS ENodeBAlgoSwitch WITCH CSFALLBACKBLI CSFallBackBlindHoCfg NDHOCFG

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 Parameter Description. 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. 2. MOD ENODEBALGOSWITCH: RimSwitch=UTRAN_RIM_SWITCH-0 MOD ENODEBALGOSWITCH: RimSwitch=UTRAN_RIM_SWITCH-1
Step 3 Run the MOD CSFALLBACKBLINDHOCFG command to set the blind-handover priorities of different RATs for CSFB.
Issue 04 (2012-09-20)
7-28
eRAN CS Fallback
----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.3.5 "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.6.6 Deactivation
Run the MOD ENODEBALGOSWITCH command with the UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check box under the HoAlgoSwitch parameter cleared.
7.7 Deploying Flash CSFB to GERAN



Operators must purchase and activate the following licenses. Table 7-16 License control item for flash CSFB to GERAN Feature LOFD-001034 CS Fallback to GERAN License Control Item Name License Control Item ID CS Fall Back to GERAN LLT1CFBG01
LOFD-001053 Flash CS Fallback to GERAN Flash CS Fallback to GERAN LLT1FCFBG01
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 5.3 "Affected Features."

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.
eRAN CS Fallback
There are three types of data sources:

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 MOs, see Mobility Management in Connected Mode Feature Parameter Description. Collect data for the parameters in the following MOs:

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 supports blind handovers according to the network plan, the blind-handover priority of the cell must be specified by the GeranNcell.BlindHoPriority parameter.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the handover mode and handover algorithm switches for flash CSFB to GERAN. Parameter Name Parameter ID Source Network plan (negotiation not required) Setting Description Set this parameter based on the network plan. 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. To activate flash CSFB to GERAN, select the GeranCsfbSwitch(GeranCsfbSwitch) and GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check boxes. GERAN_RIM_SWITCH under this parameter specifies whether to enable or disable the RIM procedure that requests event-driven multiple reports from GERAN cells.
Handover HoModeSwitch Mode switch
HoAlgoSwitch
Network plan (negotiation not required) Network plan (negotiation not required)
RIM switch
RimSwitch
If this switch is turned on, the eNodeB can send
Issue 04 (2012-09-20)
7-30
eRAN CS Fallback
Parameter Name
Parameter ID
Source
Setting Description RAN-INFORMATION-REQUEST/Multiple Report PDUs to GERAN cells to request event-driven multiple reports.
If this switch is turned off, the eNodeB cannot send RAN-INFORMATION-REQUEST/Multiple Report PDUs to GERAN cells.
If this switch is turned off and the GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box under HoAlgoSwitch is selected, the eNodeB sends RAN-INFORMATION-REQUEST/Single Report PDUs to GERAN cells to request single reports. If the GERAN cells support RAN-INFORMATION-REQUEST/Multiple Report PDUs, it is recommended that you select the GERAN_RIM_SWITCH(GERAN_RIM_SWITCH) check box.
CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This CnOperatorId (negotiation parameter specifies the ID of the operator whose not required) RAT blind-handover priorities are to be set. InterRatHighestPri Network plan Set this parameter based on the network plan. This (negotiation parameter is set to UTRAN by default and specifies not required) the high-priority RAT to be considered in blind handovers for CSFB. For flash CSFB to GERAN, set this parameter to GERAN. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to GERAN by default and specifies not required) the medium-priority RAT to be considered in blind handovers for CSFB. If the 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 InterRatHighestPri and InterRatLowestPri parameters. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to CDMA2000 by default and 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 InterRatHighestPri and InterRatSecondPri parameters.
InterRatSecondPri
InterRatLowestPri
Issue 04 (2012-09-20)
7-31
eRAN CS Fallback
Parameter Parameter ID Name GERAN LCS capability GeranLcsCap
Source
Setting Description
Network plan Set this parameter based on the network plan. This (negotiation parameter specifies the LCS capability of the not required) GERAN.
7.7.3 Precautions
None



To configure eNodeBs in batches, perform the following steps: Step 1 On the GUI, set the parameters listed in Table 7-17, and save the parameter settings as a user-defined template. The parameters are the same as those described in section 7.7.2 "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. Table 7-17 Parameters for flash CSFB to GERAN MO GERANNFREQGROUP Parameter Group Name Parameter GeranNfreqGroup Local cell identity, BCCH group identity, GERAN version, Starting ARFCN, Band indicator
Issue 04 (2012-09-20)
7-32
eRAN CS Fallback
MO
Parameter Group Name Parameter
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 Handover Algo switch, Handover Mode switch, Redirection switch, RIM switch
ENODEBALGOSWITCH CSFALLBACKBLINDHOCFG
ENodeBAlgoSwitch
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 For details about parameter settings, see Mobility Management in Connected Mode Feature Parameter Description. 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 CSFALLBACKBLINDHOCFG command to set the blind-handover priorities of different RATs for CSFB. ----End
Issue 04 (2012-09-20)
7-33
eRAN CS Fallback

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.3.5 "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.7.6 Deactivation
Run the MOD ENODEBALGOSWITCH command with the GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box under the HoAlgoSwitch parameter cleared.
7.8 Deploying CSFB with LAI to UTRAN



Operators must purchase and activate the following license. Table 7-18 License control item for CSFB with LAI to UTRAN Feature License Control Item Name License Control Item ID LLT1CFLU01
LOFD-001068 CS Fallback with LAI to CS Fallback with LAI to UTRAN UTRAN

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

CSFB with LAI to UTRAN is automatically activated when two conditions are met:
Issue 04 (2012-09-20)
7-34
eRAN CS Fallback
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.3.4 "Initial Configuration."

The activation observation procedure is as follows: 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. Step 4 Enable the UE to camp on the E-UTRAN cell and receive 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.3.5 "Activation Observation." The difference is that the Initial Context Setup Request message carries the LAI that the MME delivers to the eNodeB. ----End
7.8.6 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.3.6 "Deactivation."
7.9 Deploying CSFB with LAI to GERAN


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. This feature can be deployed only when the core-network equipment supports it.

Operators must purchase and activate the following license. Table 7-19 License control item for CSFB with LAI to GERAN Feature License Control Item Name License Control Item ID LLT1CFLG01
LOFD-001069 CS Fallback with LAI to CS Fallback with LAI to GERAN GERAN
Issue 04 (2012-09-20)
7-35
eRAN CS Fallback

Data preparation for CSFB with LAI to GERAN is the same as that for CSFB to GERAN described in section 7.4.2 "Data Preparation."
7.9.3 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.4.4 "Initial Configuration."

The activation observation procedure is as follows: 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. 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. Step 4 Enable the UE to camp on the E-UTRAN cell and receive 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.3.5 "Activation Observation." The difference is that the Initial Context Setup Request message carries the LAI that the MME delivers to the eNodeB. ----End
7.9.6 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.4.6 "Deactivation."
7.10 Performance Optimization

7.10.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.
Issue 04 (2012-09-20)
7-36
eRAN CS Fallback
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.10.2 Parameter Optimization

Blind Handovers for CSFB
Compared with measurement-based handovers, blind handovers reduce access delays but cause lower handover success rates. 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. Parameter Parameter ID Name CN Operator ID Highest priority InterRat Second priority InterRat Source Setting Description
CSFallBackBlindHoCfg. Network plan Set this parameter based on the network plan. This CnOperatorId (negotiation parameter specifies the ID of the operator whose not required) RAT blind-handover priorities are to be set. InterRatHighestPri Network plan Set this parameter based on the network plan. This (negotiation parameter is set to UTRAN by default and specifies not required) the high-priority RAT to be considered in blind handovers for CSFB. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to GERAN by default and specifies 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 InterRatHighestPri and InterRatLowestPri parameters. Network plan Set this parameter based on the network plan. This (negotiation parameter is set to CDMA2000 by default and 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 InterRatHighestPri and InterRatSecondPri parameters.
InterRatSecondPri
InterRatLowestPri
The following table describes the parameter in the ENodeBAlgoSwitch MO used to activate or deactivate blind handovers.
Issue 04 (2012-09-20)
7-37
eRAN CS Fallback
Parameter Name
Parameter ID
Source
Setting Description
Handover HoModeSwitch Network plan To activate blind handovers, select the Mode switch (negotiation not BlindHoSwitch(BlindHoSwitch) check box. A blind 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 handover success rates. To deactivate blind handovers, clear the BlindHoSwitch(BlindHoSwitch) check box.
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: CsfbHoUtranB1ThdRscp, CsfbHoUtranB1ThdEcn0, and CsfbHoUtranTimeToTrig CSFB to GERAN: CsfbHoGeranB1Thd and CsfbHoGeranTimeToTrig CSFB to CDMA2000 1xRTT: CsfbHoCdmaB1ThdPs and CsfbHoCdmaTimeToTrig
These parameters belong to the CSFALLBACKHO MO and are described in the following table. Parameter Parameter ID Name Source Setting Description
Set this parameter based on the network Local cell ID CSFALLBACKHO.LocalCellId Network plan plan. (negotiation not required)
Issue 04 (2012-09-20)
7-38
eRAN CS Fallback
Parameter Parameter ID Name CSFB Utran CsfbHoUtranTimeToTrig EventB1 Time To Trig
Source
Setting Description
Network Set this parameter based on the network plan plan. This parameter specifies the (negotiation time-to-trigger for event B1 in CSFB to not required) UTRAN. When CSFB to UTRAN is required, 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 UTRAN EventB1 RSCP Trigger Threshold
CsfbHoUtranB1ThdRscp
Network Set this parameter based on the network plan plan. This parameter specifies the RSCP (negotiation threshold for event B1 in CSFB to UTRAN. not required) When CSFB to UTRAN is required, this parameter must be set, because it is used by UEs as one of the conditions for triggering event B1. Event B1 is triggered when the RSCP measured by the UE is higher than the value of this parameter and all other conditions are also met. Network This parameter specifies the Ec/No threshold plan for event B1 in CSFB to UTRAN. When (negotiation CSFB to UTRAN is required, this parameter not required) must be set, because it is used by UEs as one of the conditions for triggering event B1. Event B1 is triggered when the Ec/No measured by the UE is higher than the value of this parameter and all other conditions are also met. Set this parameter to a large value for a cell with a large signal fading variance in order to reduce the probability of unnecessary handovers. Set this parameter to a small value for a cell with a small signal fading variance in order to ensure timely handovers.
CSFB UTRAN EventB1 ECN0 Trigger Threshold
CsfbHoUtranB1ThdEcn0
Issue 04 (2012-09-20)
7-39
eRAN CS Fallback
Parameter Parameter ID Name CSFB GERAN EventB1 Trigger Threshold CsfbHoGeranB1Thd
Source
Setting Description
Network Set this parameter based on the network plan plan. This parameter specifies the RSSI (negotiation threshold for event B1 in CSFB to GERAN. not required) Event B1 is triggered when the measured RSSI of a GERAN cell reaches the value of this parameter and all other conditions are also met. Network Set this parameter based on the network plan plan. This parameter specifies the (negotiation time-to-trigger for event B1 in CSFB to not required) GERAN. When CSFB to GERAN is required, 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 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. An appropriate value for this parameter reduces the probability of random events B1 and the average number of handovers, thereby eliminating unnecessary handovers.
CSFB Geran EventB1 Time To Trig
CsfbHoGeranTimeToTrig
CSFB CsfbHoCdmaB1ThdPs CDMA2000 EventB1 Trigger Threshold
Network Set this parameter based on the network plan plan. This parameter specifies the pilot (negotiation strength threshold for event B1 in CSFB to not required) CDMA2000 1xRTT. Event B1 is triggered when the measured pilot strength of a CDMA2000 1xRTT cell reaches the value of this parameter and all other conditions are also met.
Issue 04 (2012-09-20)
7-40
eRAN CS Fallback
Parameter Parameter ID Name CSFB CDMA EventB1 Time To Trig CsfbHoCdmaTimeToTrig
Source
Setting Description
Network Set this parameter based on the network plan plan. This parameter specifies the (negotiation time-to-trigger for event B1 in CSFB to not required) CDMA2000 1xRTT. When CSFB to CDMA2000 is required, 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 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. An appropriate value for this parameter reduces the probability of random events B1 and the average number of handovers, thereby eliminating unnecessary handovers.
7.10.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 CON_REL Redirection Trigger ucCSFBHighPriority Emergency Call Indicator ucSIBInfo Indicator for Including Target Cell SIB in RRC Connection Release Message
0: CSFB 1: others 0: indicates a non-emergency-call. 1: indicates an emergency call. 0: indicates that the SIB information of the target cell is not included in the RRC Connection Release message. 1: indicates that the SIB information of the target cell is included in the RRC Connection Release message. 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.
ucTargetType
Target Cell RAT
Issue 04 (2012-09-20)
7-41
eRAN CS Fallback
Event Name
Counter Name
Counter Description Value Handover Type: Intra-Frequency/InterFrequency/Inter-RAT
PRIVATE_INTER ucHoType _RAT_HO
1: indicates an intra-frequency handover. 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. 0: indicates a reserved value. 1: indicates a distance-based handover. 2: indicates a coverage-based handover. 3: indicates a load-based handover. 0: indicates that the procedure is complete. 1: indicates that the procedure fails due to radio-network-layer faults. 2: indicates that the procedure fails due to transport-layer faults. 3: indicates that the procedure fails due to NAS faults. 4: indicates that the procedure fails due to protocol-layer faults. 5: indicates that the procedure fails due to other faults.
ucHoTrigger
Handover Trigger
ucChoice
Cause Category
ucCauseValue
Cause Value
23: S1_CS_FALLBACK

ucCSFBHighPriority Indicator for Emergency Call-Triggered CSFB
0: indicates a non-emergency-call. 1: indicates an emergency call.
7.11 Troubleshooting
7.11.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
Issue 04 (2012-09-20)
7-42
eRAN CS Fallback
"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.11.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.11.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 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.
Issue 04 (2012-09-20)
7-43
eRAN CS Fallback
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.
If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case, run the MOD GERANNCELL command with the Blind handover priority parameter set to a value other than 0. If Blind handover priority is not 0, contact Huawei technical support.
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.
If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case, run the MOD CDMA20001XRTTNCELL 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.
----End
7.11.4 CS Fallback with LAI to UTRAN

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

Table 7-22 shows the alarms related to the feature.
Issue 04 (2012-09-20)
7-44
eRAN CS Fallback
Table 7-22 Alarm list Alarm ID 29222 Alarm Name LTE-GERAN Inter-System Outgoing Cell Handover Success Rate Too Low NetWork Element eNodeB Feature ID LOFD-001069 Feature Name CS Fallback with LAI to GERAN
Issue 04 (2012-09-20)
7-45
eRAN CS Fallback
8 Parameters
8 Parameters
Table 8-1 Parameter description MO Parameter ID MML Command Feature ID Feature Name Description
EutranInterFreq BlindHoPriority NCell
ADD LOFD-001032 / Intra-LTE Load Meaning:Indicat EUTRANINTER TDLOFD-00103 Balancing es the priority of FREQNCELL 2 the neighboring Coverage Based cell during MOD LBFD-00201802 Inter-frequency handovers. The EUTRANINTER / Handover parameter FREQNCELL TDLBFD-002018 values are Selection and 02 divided into three LST Reselection value ranges, EUTRANINTER LBFD-00201803 Distance Based indicating the FREQNCELL / Inter-frequency blind-handover TDLBFD-002018 Handover priority, 03 frequency-based LBFD-00201804 Service Based -handover Inter-frequency priority, and 0. In / TDLBFD-002018 Handover the same value 04 range, a larger value indicates a LBFD-00201805 higher priority. Blind handover is a process in which the eNodeB instructs a UE to hand over to a specified neighboring cell without measurements. The value 0 indicates that blind handovers and frequency-priorit y-based handovers are not allowed. Values 1 to 16 are designated only for blind handovers. Values 17 to 32 are designated for frequency-priorit y-based handovers, including frequency-priorit
Issue 04 (2012-09-20)
8-1
eRAN CS Fallback
8 Parameters
MO
Parameter ID
MML Command Feature ID
Feature Name
Description y-based blind handovers and frequency-priorit y-based measurement-ba sed handovers. GUI Value Range:0~32 Unit:None Actual Value Range:0~32 Default Value:0
UtranNCell
BlindHoPriority
ADD LBFD-002018 / Mobility UTRANNCELL TDLBFD-002018 Management MOD UTRANNCELL LST UTRANNCELL
Meaning:Indicat es the priority of the neighboring cell during blind handovers. Blind handover is a process in which the eNodeB instructs a UE to hand over to a specified neighboring cell. There are 32 priorities altogether. The priority has a 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
Cdma20001XRT BlindHoPriority
ADD
LOFD-002001 / Automatic
Meaning:Indicat
Issue 04 (2012-09-20)
8-2
eRAN CS Fallback
8 Parameters
MO TNcell
Parameter ID
Feature Name
Description
CDMA20001XR TDLOFD-00200 Neighbour es the priority of TTNCELL 1 Relation (ANR) the neighboring cell during blind MOD LBFD-002018 / Mobility handovers. Blind CDMA20001XR TDLBFD-002018 Management handover is a TTNCELL process in which the eNodeB LST instructs a UE to CDMA20001XR hand over to a TTNCELL specified neighboring cell without measurements. There are 32 priorities altogether. The priority has a positive correlation with the value of this parameter. Note that the value 0 indicates that blind handovers to the neighboring cell are prohibited. GUI Value Range:0~32 Unit:None Actual Value Range:0~32 Default Value:0
GeranNcell
BlindHoPriority
ADD LBFD-002018 / Mobility GERANNCELL TDLBFD-002018 Management MOD LOFD-001020 / GERANNCELL TDLOFD-00102 0 LST GERANNCELL LOFD-001045 / TDLOFD-00104 5 LOFD-001046 / TDLOFD-00104 6 LOFD-001073 / TDLOFD-00107
Meaning:Indicat es the priority of the neighboring PS Inter-RAT cell during blind Mobility between handovers. Blind E-UTRAN and handover is a GERAN process in which Inter-RAT Load the eNodeB instructs a UE to Sharing to hand over to a GERAN specified Service based neighboring cell. inter-RAT There are 32 handover to priorities GERAN altogether. The priority has a Distance based
8-3
Issue 04 (2012-09-20)
eRAN CS Fallback
8 Parameters
MO
Parameter ID
MML Command Feature ID 3
Feature Name inter-RAT handover to GERAN
Description 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
CSFallBackBlind CdmaLcsCap HoCfg
LOFD-001035 CS Fallback to MOD CSFALLBACKB CDMA2000 LOFD-001047 / 1xRTT LINDHOCFG TDLOFD-00104 LST 7 LoCation CSFALLBACKB Services(LCS) LINDHOCFG
Meaning:Indicat es the Location Services (LCS) capability of the CDMA2000. If this parameter is set to ON, the CDMA2000 supports LCS. If this parameter is set to OFF, the CDMA20000 does not support LCS. GUI Value Range:OFF(Off), ON(On) Unit:None Actual Value Range:OFF, ON Default Value:OFF(Off)
CSFallBackBlind CnOperatorId HoCfg
None LST CSFALLBACKB LINDHOCFG MOD CSFALLBACKB LINDHOCFG
None
Meaning:Indicat es the index of the operator. GUI Value Range:0~5
Issue 04 (2012-09-20)
8-4
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description Unit:None Actual Value Range:0~5 Default Value:None
CSFallBackHo
LOFD-001035 CsfbHoCdmaB1 MOD ThdPs CSFALLBACKH O LST CSFALLBACKH O
CS Fallback to CDMA2000 1xRTT
Meaning:Indicat es the pilot strength threshold related to event B1, which is used in CS fallback to CDMA2000. A UE sends a measurement report related to event B1 to the eNodeB when the pilot strength in at least one CDMA2000 cell 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
CSFallBackHo
LOFD-001035 CsfbHoCdmaTi MOD meToTrig CSFALLBACKH O LST CSFALLBACKH O
CS Fallback to CDMA2000 1xRTT
Meaning:Indicat es the time-to-trigger for event B1, which is used in CS fallback to CDMA2000. When CS fallback to
8-5
Issue 04 (2012-09-20)
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description CDMA2000 is applicable, this parameter is set for UEs and used in the evaluation of whether to trigger event B1. When 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,
Issue 04 (2012-09-20)
8-6
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description 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
CSFallBackHo
CsfbHoGeranB1 MOD LOFD-001034 / CS Fall Back to Meaning:Indicat Thd CSFALLBACKH TDLOFD-00103 GERAN es the RSSI O 4 threshold for event B1 that is LST used in CS CSFALLBACKH fallback to O GERAN. A UE sends a measurement report related to event B1 to the eNodeB when the RSSI in at least one GERAN cell exceeds this threshold and other triggering conditions are met. For details, see 3GPP TS 36.331. GUI Value Range:-110~-48 Unit:dBm Actual Value Range:-110~-48
Issue 04 (2012-09-20)
8-7
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description Default Value:-103
CSFallBackHo
CsfbHoGeranTi MOD LOFD-001034 / CS Fall Back to Meaning:Indicat meToTrig CSFALLBACKH TDLOFD-00103 GERAN es the O 4 time-to-trigger for event B1 that LST is used in CS CSFALLBACKH fallback to O GERAN. When CS fallback to GERAN is applicable, this parameter is set for UEs and used in the evaluation of whether to trigger event B1. When detecting that the 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 continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers, and thus helps
Issue 04 (2012-09-20)
8-8
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description 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
CSFallBackHo
CsfbHoUtranB1 MOD LOFD-001033 / CS Fallback to ThdEcn0 CSFALLBACKH TDLOFD-00103 UTRAN O 3 LST CSFALLBACKH O
Meaning:Indicat es the Ec/No threshold for event B1, which is used in CS fallback to UTRAN. When CS fallback to UTRAN is required, this parameter is set for UEs and used in the evaluation about whether to trigger event B1. This parameter indicates the
Issue 04 (2012-09-20)
8-9
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description Ec/No 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 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
CSFallBackHo
CsfbHoUtranB1 MOD LOFD-001033 / CS Fallback to ThdRscp CSFALLBACKH TDLOFD-00103 UTRAN O 3
Meaning:Indicat es the RSCP threshold for
Issue 04 (2012-09-20)
8-10
eRAN CS Fallback
8 Parameters
MO
Parameter ID
MML Command Feature ID LST CSFALLBACKH O
Feature Name
Description event B1, which is used in CS fallback to UTRAN. When CS fallback to UTRAN is applicable, this parameter is set for UEs and used in the evaluation about whether to trigger event B1. This parameter 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
CSFallBackHo
CsfbHoUtranTim MOD LOFD-001033 / CS Fallback to eToTrig CSFALLBACKH TDLOFD-00103 UTRAN O 3 LST CSFALLBACKH
Meaning:Indicat es the time-to-trigger for event B1 that is used in CS
Issue 04 (2012-09-20)
8-11
eRAN CS Fallback
8 Parameters
MO
Parameter ID
MML Command Feature ID O
Feature Name
Description fallback to UTRAN. When CS fallback to UTRAN is applicable, this parameter is set for UEs and used in the evaluation of whether to trigger event B1. When detecting that the 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 continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers, and thus helps prevent unnecessary handovers. For details, see 3GPP TS 36.331. GUI Value Range:0ms,
Issue 04 (2012-09-20)
8-12
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description 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
UtranNFreq
CsPriority
ADD LOFD-001033 / CS Fallback to UTRANNFREQ TDLOFD-00103 UTRAN 3 MOD E-UTRAN to UTRANNFREQ LOFD-001078 / UTRAN CS/PS TDLBFD-001078 Steering LST UTRANNFREQ
Meaning:Indicat es the circuit switched (CS) priority of the neighboring UTRAN frequency, that is, the priority for the neighboring UTRAN frequency to carry CS services. It is used in CSFB-triggered handovers. When UtranFreqLayer MeasSwitch is turned on: If there are both high and low CS-priority UTRAN frequencies, the high CS-priority
Issue 04 (2012-09-20)
8-13
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description UTRAN frequencies are preferentially measured; if there are only low CS-priority UTRAN frequencies, these low CS-priority UTRAN frequencies are measured. If UtranFreqLayer BlindSwitch is turned on, the target cell for a blind handover is preferentially selected from the neighboring UTRAN cells on high CS-priority frequencies. If all neighboring UTRAN cells are on low CS-priority frequencies, the target cell is selected from all neighboring UTRAN cells. GUI Value Range:LOW_PR IORITY(Low Priority), HIGH_PRIORIT Y(High Priority) Unit:None Actual Value Range:LOW_PR IORITY, HIGH_PRIORIT Y Default Value:HIGH_PRI ORITY(High
Issue 04 (2012-09-20)
8-14
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description Priority)
ENodeBAlgoSwi FreqLayerSwtich MOD LOFD-001078 / E-UTRAN to Meaning:Indicat tch ENODEBALGO TDLOFD-00107 UTRAN CS/PS es the switch SWITCH 8 Steering used to enable or disable the LST UTRAN ENODEBALGO hierarchy-based SWITCH measurement algorithm and the UTRAN hierarchy-based blind-handover algorithm.If UtranFreqLayer MeasSwitch is turned on, the UTRAN hierarchy-based measurement algorithm takes effect for measurements related to coverage-based and CSFB-triggered handovers from the E-UTRAN to the UTRAN. If UtranFreqLayer BlindSwitch is turned on, the UTRAN hierarchy-based blind-handover algorithm takes effect for coverage-based and CSFB-triggered handovers from the E-UTRAN to the UTRAN. GUI Value Range:UtranFre qLayerMeasSwit ch(UtranFreqLay erMeasSwitch), UtranFreqLayer BlindSwitch(Utra
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description nFreqLayerBlind Switch) Unit:None Actual Value Range:UtranFre qLayerMeasSwit ch, UtranFreqLayer BlindSwitch Default Value:UtranFreq LayerMeasSwitc h:Off, UtranFreqLayer BlindSwitch:Off
CSFallBackBlind GeranLcsCap HoCfg
MOD LOFD-001034 / CS Fallback to CSFALLBACKB TDLOFD-00103 GERAN LINDHOCFG 4 LoCation LST LOFD-001047 / Services(LCS) CSFALLBACKB TDLOFD-00104 LINDHOCFG 7
Meaning:Indicat es the Location Services (LCS) capability of the GERAN. If this parameter is set to ON, the GERAN supports LCS. If this parameter is set to OFF, the GERAN does not support LCS. GUI Value Range:OFF(Off), ON(On) Unit:None Actual Value Range:OFF, ON Default Value:OFF(Off)
ENodeBAlgoSwi HoAlgoSwitch tch
MOD LBFD-00201801 Coverage Based Meaning:Indicat ENODEBALGO / Intra-frequency es the collective SWITCH TDLBFD-002018 Handover switch used to 01 enable or disable LST Coverage Based handover. ENODEBALGO LBFD-00201802 Inter-frequency SWITCH / Handover Flash CS TDLBFD-002018 fallback to Service based UTRAN: If the 02 inter-RAT switch for CS LOFD-001043 / handover to
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-16
Issue 04 (2012-09-20)
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description fallback to UTRAN is turned off, this switch does not take effect; Flash CS fallback to GERAN: If the switch for CS fallback to GERAN is turned off, this switch does not take effect. GUI Value Range:IntraFreq CoverHoSwitch(I ntraFreqCoverH oSwitch), InterFreqCoverH oSwitch(InterFre qCoverHoSwitch ), UtranCsfbSwitch (UtranCsfbSwitc h), GeranCsfbSwitc h(GeranCsfbSwi tch), Cdma1xRttCsfb Switch(Cdma20 001xRttCsfbSwit ch), UtranServiceHo Switch(UtranSer viceHoSwitch), GeranServiceHo Switch(GeranSe rviceHoSwitch), CdmaHrpdServi ceHoSwitch(Cd ma2000HrpdSer viceHoSwitch), Cdma1xRttServi ceHoSwitch(Cd ma20001xRttSer viceHoSwitch), UlQualityInterRA THoSwitch(UlQu alityInterRATHo Switch), InterPlmnHoSwit
TDLOFD-00104 UTRAN 3 Service based LOFD-001046 / inter-RAT TDLOFD-00104 handover to 6 GERAN LBFD-00201805 Service Based / Inter-frequency TDLBFD-002018 Handover 05 CS Fallback to LOFD-001033 / UTRAN TDLOFD-00103 CS Fallback to 3 GERAN LOFD-001034 / TDLOFD-00103 CS Fallback to CDMA2000 4 1xRTT LOFD-001035 / TDLOFD-00103 Flash CS Fallback to 5 UTRAN LOFD-001052 / TDLOFD-00105 Flash CS Fallback to 2 GERAN LOFD-001053 / TDLOFD-00105 3
Issue 04 (2012-09-20)
8-17
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description ch(InterPlmnHo Switch), UtranFlashCsfb Switch(UtranFla shCsfbSwitch), GeranFlashCsfb Switch(GeranFla shCsfbSwitch), ServiceBasedInt erFreqHoSwitch( ServiceBasedInt erFreqHoSwitch) , UlQualityInterFre qHoSwitch(UlQu alityInterFreqHo Switch) Unit:None Actual Value Range:IntraFreq CoverHoSwitch, InterFreqCoverH oSwitch, UtranCsfbSwitch , GeranCsfbSwitc h, Cdma1xRttCsfb Switch, UtranServiceHo Switch, GeranServiceHo Switch, CdmaHrpdServi ceHoSwitch, Cdma1xRttServi ceHoSwitch, UlQualityInterRA THoSwitch, InterPlmnHoSwit ch, UtranFlashCsfb Switch, GeranFlashCsfb Switch, ServiceBasedInt erFreqHoSwitch, UlQualityInterFre qHoSwitch Default Value:IntraFreqC
Issue 04 (2012-09-20)
8-18
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description overHoSwitch:O n, InterFreqCoverH oSwitch:On, UtranCsfbSwitch :Off, GeranCsfbSwitc h:Off, Cdma20001xRtt CsfbSwitch:Off, UtranServiceHo Switch:Off, GeranServiceHo Switch:Off, Cdma2000Hrpd ServiceHoSwitch :Off, Cdma20001xRtt ServiceHoSwitch :Off, UlQualityInterRA THoSwitch:Off, InterPlmnHoSwit ch:Off, UtranFlashCsfb Switch:Off, GeranFlashCsfb Switch:Off, ServiceBasedInt erFreqHoSwitch: Off, UlQualityInterFre qHoSwitch:Off
ENodeBAlgoSwi HoModeSwitch MOD LOFD-001019 / PS Inter-RAT Meaning:Indicat tch ENODEBALGO TDLOFD-00101 Mobility between es the switches SWITCH 9 E-UTRAN and corresponding to UTRAN the inputs based LST LOFD-001020 / on which the ENODEBALGO TDLOFD-00102 PS Inter-RAT eNodeB SWITCH 0 Mobility between determines E-UTRAN and handover LOFD-001021 / GERAN policies. Note TDLOFD-00102 that 1 PS Inter-RAT Mobility between EutranVoipCapS LOFD-001022 / E-UTRAN and witch will be TDLOFD-00102 CDMA2000 removed in the 2 later versions. In SRVCC to this version, the LOFD-001023 / UTRAN setting of this TDLOFD-00102 switch is still 3 SRVCC to synchronized GERAN between the
Issue 04 (2012-09-20)
8-19
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description M2000 and the eNodeB, but it is no longer used internally. Therefore, avoid using this switch. GUI Value Range:EutranVoi pCapSwitch(Eutr anVoipCapSwitc h), UtranVoipCapS witch(UtranVoip CapSwitch), GeranVoipCapS witch(GeranVoip CapSwitch), Cdma1xRttVoip CapSwitch(Cdm a1xRttVoipCapS witch), UtranPsHoSwitc h(UtranPsHoSwi tch), GeranPsHoSwit ch(GeranPsHoS witch), CdmaHrpdNonO tpimisedHoSwitc h(CdmaHrpdNon OtpimisedHoSwi tch), CdmaHrpdOptim isedHoSwitch(C dmaHrpdOptimis edHoSwitch), GeranNaccSwitc h(GeranNaccSwi tch), GeranCcoSwitch (GeranCcoSwitc h), UtranSrvccSwitc h(UtranSrvccSwi tch), GeranSrvccSwit ch(GeranSrvccS witch), Cdma1xRttSrvcc Switch(Cdma1x RttSrvccSwitch), UtranRedirectSw itch(UtranRedire
Issue 04 (2012-09-20)
8-20
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description ctSwitch), GeranRedirectS witch(GeranRedi rectSwitch), CdmaHrpdRedir ectSwitch(Cdma HrpdRedirectSwi tch), Cdma1xRttRedir ectSwitch(Cdma 1xRttRedirectSw itch), BlindHoSwitch(B lindHoSwitch) Unit:None Actual Value Range:EutranVoi pCapSwitch, UtranVoipCapS witch, GeranVoipCapS witch, Cdma1xRttVoip CapSwitch, UtranPsHoSwitc h, GeranPsHoSwit ch, CdmaHrpdNonO tpimisedHoSwitc h, CdmaHrpdOptim isedHoSwitch, GeranNaccSwitc h, GeranCcoSwitch , UtranSrvccSwitc h, GeranSrvccSwit ch, Cdma1xRttSrvcc Switch, UtranRedirectSw itch, GeranRedirectS witch, CdmaHrpdRedir ectSwitch, Cdma1xRttRedir ectSwitch,
Issue 04 (2012-09-20)
8-21
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description BlindHoSwitch Default Value:EutranVoi pCapSwitch:On, UtranVoipCapS witch:Off, GeranVoipCapS witch:Off, Cdma1xRttVoip CapSwitch:Off, UtranPsHoSwitc h:Off, GeranPsHoSwit ch:Off, CdmaHrpdNonO tpimisedHoSwitc h:Off, CdmaHrpdOptim isedHoSwitch:Of f, GeranNaccSwitc h:Off, GeranCcoSwitch :Off, UtranSrvccSwitc h:Off, GeranSrvccSwit ch:Off, Cdma1xRttSrvcc Switch:Off, UtranRedirectSw itch:Off, GeranRedirectS witch:Off, CdmaHrpdRedir ectSwitch:Off, Cdma1xRttRedir ectSwitch:Off, BlindHoSwitch:O ff
CSFallBackBlind InterRatHighest MOD LOFD-001019 / PS Inter-RAT Meaning:Ndicate HoCfg Pri CSFALLBACKB TDLOFD-00101 Mobility between s the LINDHOCFG 9 E-UTRAN and high-priority UTRAN system to be LST LOFD-001020 / considered in CSFALLBACKB TDLOFD-00102 PS Inter-RAT blind handovers. LINDHOCFG 0 Mobility between It is UTRAN by E-UTRAN and default. This LOFD-001021 / GERAN parameter can TDLOFD-00102 be set to 1 PS Inter-RAT Mobility between UTRAN,
Issue 04 (2012-09-20)
8-22
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description
LOFD-001044 / E-UTRAN and GERAN, or TDLOFD-00104 CDMA2000 CDMA2000. 4 Inter-RAT Load GUI Value LOFD-001045 / Sharing to Range:UTRAN, TDLOFD-00104 UTRAN GERAN, 5 CDMA2000 Inter-RAT Load LOFD-001033 / Sharing to Unit:None TDLOFD-00103 GERAN Actual Value 3 CS Fallback to Range:UTRAN, LOFD-001034 / UTRAN GERAN, TDLOFD-00103 CDMA2000 CS Fallback to 4 GERAN Default LOFD-001035 / Value:UTRAN TDLOFD-00103 CS Fallback to CDMA2000 5 1xRTT LOFD-001068 / TDLOFD-00106 CS Fallback with LAI to UTRAN 8 LOFD-001069 / CS Fallback with TDLOFD-00106 LAI to GERAN 9 Flash CS LOFD-001052 / Fallback to TDLOFD-00105 UTRAN 2 Flash CS LOFD-001053 / Fallback to TDLOFD-00105 GERAN 3 CSFallBackBlind InterRatLowestP MOD LOFD-001019 / PS Inter-RAT Meaning:Indicat HoCfg ri CSFALLBACKB TDLOFD-00101 Mobility between es the LINDHOCFG 9 E-UTRAN and low-priority UTRAN system to be LST LOFD-001020 / considered in CSFALLBACKB TDLOFD-00102 PS Inter-RAT blind handovers. LINDHOCFG 0 Mobility between It is CDMA2000 E-UTRAN and by default. This LOFD-001021 / GERAN parameter can TDLOFD-00102 be set to 1 PS Inter-RAT Mobility between UTRAN, LOFD-001044 / E-UTRAN and GERAN, or TDLOFD-00104 CDMA2000 CDMA2000. If 4 this parameter is Inter-RAT Load set to NULL, the LOFD-001045 / Sharing to system with the TDLOFD-00104 UTRAN medium blind 5 handover priority Inter-RAT Load is not specified LOFD-001033 / Sharing to and only blind
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description
TDLOFD-00103 GERAN handovers to the 3 high- and CS Fallback to medium-priority LOFD-001034 / UTRAN systems are TDLOFD-00103 CS Fallback to applicable. 4 GERAN GUI Value LOFD-001035 / Range:UTRAN, TDLOFD-00103 CS Fallback to GERAN, CDMA2000 5 CDMA2000, 1xRTT NULL LOFD-001068 / CS Fallback with TDLOFD-00106 LAI to UTRAN Unit:None 8 Actual Value LOFD-001069 / CS Fallback with Range:UTRAN, TDLOFD-00106 LAI to GERAN GERAN, 9 Flash CS CDMA2000, Fallback to NULL LOFD-001052 / UTRAN TDLOFD-00105 Default 2 Flash CS Value:CDMA200 Fallback to 0 LOFD-001053 / GERAN TDLOFD-00105 3 CSFallBackBlind InterRatSecond MOD LOFD-001019 / PS Inter-RAT Meaning:Indicat HoCfg Pri CSFALLBACKB TDLOFD-00101 Mobility between es the LINDHOCFG 9 E-UTRAN and medium-priority UTRAN system to be LST LOFD-001020 / considered in CSFALLBACKB TDLOFD-00102 PS Inter-RAT blind handovers. LINDHOCFG 0 Mobility between It is GERAN by E-UTRAN and default. This LOFD-001021 / GERAN parameter can TDLOFD-00102 be set to 1 PS Inter-RAT Mobility between UTRAN, LOFD-001044 / E-UTRAN and GERAN, or TDLOFD-00104 CDMA2000 CDMA2000. If 4 this parameter is Inter-RAT Load set to NULL, the LOFD-001045 / Sharing to system with the TDLOFD-00104 UTRAN medium blind 5 handover priority Inter-RAT Load is not specified LOFD-001033 / Sharing to and only blind TDLOFD-00103 GERAN handovers to the 3 CS Fallback to high-priority LOFD-001034 / UTRAN system are TDLOFD-00103 applicable. 4 CS Fallback to GUI Value GERAN LOFD-001035 / Range:UTRAN, TDLOFD-00103 CS Fallback to GERAN,
Issue 04 (2012-09-20)
8-24
eRAN CS Fallback
8 Parameters
MO
Parameter ID
MML Command Feature ID 5
Feature Name CDMA2000 1xRTT
Description CDMA2000, NULL
LOFD-001068 / TDLOFD-00106 CS Fallback with Unit:None 8 LAI to UTRAN Actual Value LOFD-001069 / CS Fallback with Range:UTRAN, TDLOFD-00106 LAI to GERAN GERAN, 9 CDMA2000, Flash CS NULL LOFD-001052 / Fallback to TDLOFD-00105 UTRAN Default 2 Value:GERAN Flash CS LOFD-001053 / Fallback to TDLOFD-00105 GERAN 3 CSFallBackHo LocalCellId LST LBFD-001001 / 3GPP R8 CSFALLBACKH TDLBFD-001001 Specifications O MOD CSFALLBACKH O Meaning:Indicat es the local ID of the cell. It uniquely identifies a cell within a BS. GUI Value Range:0~17 Unit:None Actual Value Range:0~17 Default Value:None UtranExternalCe Rac ll ADD LOFD-001019 / PS Inter-RAT Meaning:Indicat UTRANEXTERN TDLOFD-00101 Mobility between es the routing ALCELL 9 E-UTRAN and area code. UTRAN MOD GUI Value UTRANEXTERN Range:0~255 ALCELL Unit:None LST Actual Value UTRANEXTERN Range:0~255 ALCELL Default Value:0 GeranExternalC Rac ell ADD LOFD-001020 / PS Inter-RAT Meaning:Indicat GERANEXTER TDLOFD-00102 Mobility between es the routing NALCELL 0 E-UTRAN and area code. GERAN MOD GUI Value GERANEXTER Range:0~255
Issue 04 (2012-09-20)
8-25
eRAN CS Fallback
8 Parameters
MO
Parameter ID
MML Command Feature ID NALCELL LST GERANEXTER NALCELL
Feature Name
Description Unit:None Actual Value Range:0~255 Default Value:0 Meaning:Indicat es the collective switch for the RAN information management (RIM) function. UTRAN_RIM_S WITCH: Indicates the switch used to enable or disable the RIM procedure that requests event-driven multiple reports from UTRAN cells. If this switch is turned on, the eNodeB can send RAN-INFORMA TION-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-INFORMA TION-REQUEST PDUs to UTRAN cells to request multiple event-driven reports. GERAN_RIM_S WITCH: Indicates the
ENodeBAlgoSwi RimSwitch tch
MOD LOFD-001052 / Flash CS ENODEBALGO TDLOFD-00105 Fallback to SWITCH 2 UTRAN LST LOFD-001053 / Flash CS ENODEBALGO TDLOFD-00105 Fallback to SWITCH 3 GERAN
Issue 04 (2012-09-20)
8-26
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description 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-INFORMA TION-REQUEST PDUs to CERAN cells to request multiple event-driven reports. If this switch is turned off, the eNodeB cannot send RAN-INFORMA TION-REQUEST PDUs to GERAN cells to request multiple event-driven reports. GUI Value Range:UTRAN_ RIM_SWITCH(U TRAN RIM Switch), GERAN_RIM_S WITCH(GERAN RIM Switch) Unit:None Actual Value Range:UTRAN_ RIM_SWITCH, GERAN_RIM_S WITCH Default Value:UTRAN RIM Switch:Off, GERAN RIM
Issue 04 (2012-09-20)
8-27
eRAN CS Fallback
8 Parameters
MO
Parameter ID
Feature Name
Description Switch:Off
CSFallBackBlind UtranLcsCap HoCfg
MOD LOFD-001033 / CS Fallback to CSFALLBACKB TDLOFD-00103 UTRAN LINDHOCFG 3 LoCation LST LOFD-001047 / Services(LCS) CSFALLBACKB TDLOFD-00104 LINDHOCFG 7
Meaning:Indicat es the Location Services (LCS) capability of the UTRAN. If this parameter is set to ON, the UTRAN supports LCS. If this parameter is set to OFF, the UTRAN does not support LCS. GUI Value Range:OFF(Off), ON(On) Unit:None Actual Value Range:OFF, ON Default Value:OFF(Off)
Issue 04 (2012-09-20)
8-28
eRAN CS Fallback
9 Counters
9 Counters
Table 9-1 Counter description Counter ID Counter Name Counter Descriptio Feature ID n LOFD-001021 LOFD-001035 Feature Name
1526726988
L.IRATHO.E2C.Exe Number of cSuccOut Successful Outgoing Handovers from E-UTRAN to CDMA2000
PS Inter-RAT Mobility between E-UTRAN and CDMA2000 CS Fallback to CDMA2000 1xRTT PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN
1526726989
L.IRATHO.E2W.Pre Number of Outgoing LOFD-001019 pAttOut Handover Attempts from E-UTRAN to LOFD-001022 UTRAN LOFD-001033 TDLOFD-001019 TDLOFD-001022 TDLOFD-001033
1526726990
LOFD-001019 L.IRATHO.E2W.Exe Number of cAttOut Performed Outgoing LOFD-001022 Handovers from E-UTRAN to LOFD-001033 UTRAN TDLOFD-001019 TDLOFD-001022 TDLOFD-001033
PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN
1526726991
L.IRATHO.E2W.Exe Number of cSuccOut Successful
LOFD-001019
PS Inter-RAT Mobility between
Issue 04 (2012-09-20)
9-1
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n Outgoing Handovers from E-UTRAN to UTRAN LOFD-001022 LOFD-001033 TDLOFD-001019 TDLOFD-001022 TDLOFD-001033
Feature Name E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN
1526726992
L.IRATHO.E2G.Prep Number of Outgoing LOFD-001020 AttOut Handover Attempts from E-UTRAN to LOFD-001023 GERAN LOFD-001034 TDLOFD-001020 TDLOFD-001023 TDLOFD-001034
PS Inter-RAT Mobility between E-UTRAN and GERAN SRVCC to GERAN CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN SRVCC to GERAN CS Fallback to GERAN
1526726993
LOFD-001020 L.IRATHO.E2G.Exe Number of cAttOut Performed Outgoing LOFD-001023 Handovers from E-UTRAN to LOFD-001034 GERAN TDLOFD-001020 TDLOFD-001023 TDLOFD-001034
PS Inter-RAT Mobility between E-UTRAN and GERAN SRVCC to GERAN CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN SRVCC to GERAN CS Fallback to
Issue 04 (2012-09-20)
9-2
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n
Feature Name GERAN
1526726994
L.IRATHO.E2G.Exe Number of cSuccOut Successful Outgoing Handovers from E-UTRAN to GERAN
LOFD-001020 LOFD-001023 LOFD-001034 TDLOFD-001020 TDLOFD-001023 TDLOFD-001034
PS Inter-RAT Mobility between E-UTRAN and GERAN SRVCC to GERAN CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN SRVCC to GERAN CS Fallback to GERAN
1526727033
Handover from E-UTRAN to CDMA2000 Success Rate
LOFD-001021 Success rate of inter-RAT handovers from E-UTRAN to LOFD-001035 CDMA2000 network
PS Inter-RAT Mobility between E-UTRAN and CDMA2000 CS Fallback to CDMA2000 1xRTT
1526727034
Handover from E-UTRAN to WCDMA Success Rate
LOFD-001019 Success rate of inter-RAT handovers from E-UTRAN to LOFD-001022 WCDMA network LOFD-001033 TDLOFD-001019 TDLOFD-001022 TDLOFD-001033
PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN SRVCC to UTRAN CS Fallback to UTRAN
1526728306
L.IRATHO.E2G.Prep Number of outgoing LOFD-001034 .FailOut.MME handover preparation failures TDLOFD-001034 from E-UTRAN to
CS Fallback to GERAN CS Fallback to
Issue 04 (2012-09-20)
9-3
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n GERAN due to faults in the EPC LOFD-001020 TDLOFD-001020 LOFD-001046 TDLOFD-001046 LOFD-001073
Feature Name 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 Distance based inter-RAT handover to GERAN
1526728307
L.IRATHO.E2G.Prep Number of outgoing LOFD-001034 .FailOut.NoReply handover preparation failures TDLOFD-001034 due to no responses LOFD-001020 from GERAN TDLOFD-001020 LOFD-001046 TDLOFD-001046 LOFD-001073
CS Fallback to GERAN 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 Distance based inter-RAT handover to GERAN
1526728308
L.IRATHO.E2G.Prep Number of outgoing LOFD-001034 .FailOut.PrepFailure handover preparation failures TDLOFD-001034
CS Fallback to GERAN CS Fallback to

9-4
Issue 04 (2012-09-20)
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n due to handover LOFD-001020 preparation failures TDLOFD-001020 in GERAN LOFD-001046 TDLOFD-001046 LOFD-001073
Feature Name 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 Distance based inter-RAT handover to GERAN
1526728309
L.IRATHO.E2T.Prep Number of outgoing LOFD-001033 .FailOut.MME handover preparation failures TDLOFD-001033 from E-UTRAN to LOFD-001019 TD-SCDMA network due to faults in the TDLOFD-001019 EPC LOFD-001043 TDLOFD-001043 LOFD-001072
CS Fallback to UTRAN CS Fallback to 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 Distance based inter-RAT handover to UTRAN
1526728310
L.IRATHO.E2T.Prep Number of outgoing LOFD-001033 .FailOut.NoReply handover preparation failures TDLOFD-001033
CS Fallback to UTRAN CS Fallback to

9-5
Issue 04 (2012-09-20)
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n due to no responses LOFD-001019 from TD-SCDMA TDLOFD-001019 network LOFD-001043 TDLOFD-001043 LOFD-001072
Feature Name 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 Distance based inter-RAT handover to UTRAN
1526728311
L.IRATHO.E2T.Prep Number of outgoing .FailOut.PrepFailure handover preparation failures due to handover preparation failures in TD-SCDMA network
LOFD-001033 TDLOFD-001033 LOFD-001019 TDLOFD-001019 LOFD-001043 TDLOFD-001043 LOFD-001072
1526728312
LOFD-001033 L.IRATHO.BlindHO. Number of E2W.ExecAttOut performed outgoing TDLOFD-001033 blind handovers
CS Fallback to UTRAN CS Fallback to

9-6
Issue 04 (2012-09-20)
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n from E-UTRAN to LOFD-001019 TDLOFD-001019
Feature Name UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN
WCDMA network
1526728313
LOFD-001033 L.IRATHO.BlindHO. Number of E2W.ExecSuccOut performed outgoing TDLOFD-001033 blind handovers from E-UTRAN to LOFD-001019 TDLOFD-001019
CS Fallback to UTRAN CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN
WCDMA network
1526728314
LOFD-001034 L.IRATHO.BlindHO. Number of E2G.ExecAttOut performed outgoing TDLOFD-001034 blind handovers from E-UTRAN to LOFD-001020 TDLOFD-001020
CS Fallback to GERAN CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN
GERAN
1526728315
LOFD-001034 L.IRATHO.BlindHO. Number of E2G.ExecSuccOut successful outgoing TDLOFD-001034 blind handovers from E-UTRAN to LOFD-001020 GERAN TDLOFD-001020
CS Fallback to GERAN CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN
Issue 04 (2012-09-20)
9-7
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Feature Name PS Inter-RAT Mobility between E-UTRAN and GERAN
1526728316
L.IRATHO.E2W.Pre Number of outgoing p.FailOut.MME handover preparation failures from E-UTRAN to WCDMA network due to faults in the EPC
1526728317
L.IRATHO.E2W.Pre Number of outgoing p.FailOut.PrepFailur handover e preparation failures due to handover preparation failures in WCDMA network
CS Fallback to UTRAN CS Fallback to 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
Issue 04 (2012-09-20)
9-8
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Feature Name to UTRAN Distance based inter-RAT handover to UTRAN
1526728318
L.IRATHO.E2W.Pre Number of outgoing LOFD-001033 p.FailOut.NoReply handover preparation failures TDLOFD-001033 due to no responses LOFD-001019 from WCDMA TDLOFD-001019 network LOFD-001043 TDLOFD-001043 LOFD-001072
1526728321
L.CSFB.PrepAtt
Number of CS fallback indicators received by the eNodeB
LOFD-001033 TDLOFD-001033 LOFD-001034 TDLOFD-001034 LOFD-001035
CS Fallback to UTRAN CS Fallback to UTRAN CS Fallback to GERAN CS Fallback to GERAN CS Fallback to CDMA2000 1xRTT
1526728322
L.CSFB.PrepSucc
LOFD-001033 Number of successful CS fallback responses TDLOFD-001033 from the eNodeB LOFD-001034
CS Fallback to UTRAN CS Fallback to UTRAN CS Fallback to
Issue 04 (2012-09-20)
9-9
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n TDLOFD-001034 LOFD-001035
Feature Name GERAN CS Fallback to GERAN CS Fallback to CDMA2000 1xRTT
1526728323
L.CSFB.E2W
LOFD-001033 Number of CS fallback procedures from E-UTRAN to TDLOFD-001033 UTRAN<?Pub
CS Fallback to UTRAN CS Fallback to UTRAN
Caret?> 1526728324 L.CSFB.E2G LOFD-001034 Number of CS fallback procedures from E-UTRAN to TDLOFD-001034 GERAN CS Fallback to GERAN CS Fallback to GERAN CS Fallback to UTRAN CS Fallback to UTRAN Flash CS Fallback to UTRAN Flash CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN Distance based inter-RAT handover to UTRAN Service based inter-RAT handover to UTRAN Service based inter-RAT handover
1526728326
L.RRCRedirection.E Number of 2W redirections to WCDMA network
LOFD-001033 TDLOFD-001033 LOFD-001052 TDLOFD-001052 LOFD-001019 TDLOFD-001019 LOFD-001072 LOFD-001043 TDLOFD-001043
Issue 04 (2012-09-20)
9-10
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Feature Name to UTRAN
1526728327
L.RRCRedirection.E Number of 2G redirections to GERAN
CS Fallback to GERAN CS Fallback to GERAN Flash CS Fallback to GERAN Flash CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN Distance based inter-RAT handover to GERAN Service based inter-RAT handover to GERAN Service based inter-RAT handover to GERAN
1526728328
L.IRATHO.BlindHO. Number of outgoing LOFD-001033 E2W.PrepAttOut blind handover TDLOFD-001033 attempts from E-UTRAN to LOFD-001019 TDLOFD-001019 WCDMA network
CS Fallback to UTRAN CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN
1526728329
L.IRATHO.BlindHO. Number of outgoing LOFD-001034 E2G.PrepAttOut blind handover TDLOFD-001034 attempts from
CS Fallback to GERAN
Issue 04 (2012-09-20)
9-11
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n E-UTRAN to LOFD-001020 TDLOFD-001020
Feature Name CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN
GERAN
1526728330
L.RRCRedirection.E Number of 2W.PrepAtt redirection preparations to WCDMA network
CS Fallback to UTRAN CS Fallback to UTRAN Flash CS Fallback to UTRAN Flash CS Fallback to UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN PS Inter-RAT Mobility between E-UTRAN and UTRAN Distance based inter-RAT handover to UTRAN Service based inter-RAT handover to UTRAN Service based inter-RAT handover to UTRAN
1526728331
L.RRCRedirection.E Number of 2G.PrepAtt redirection preparations to GERAN
LOFD-001034 TDLOFD-001034 LOFD-001053 TDLOFD-001053 LOFD-001020
CS Fallback to GERAN CS Fallback to GERAN Flash CS Fallback to GERAN
Issue 04 (2012-09-20)
9-12
eRAN CS Fallback
9 Counters
Counter ID
Counter Name
Counter Descriptio Feature ID n TDLOFD-001020 LOFD-001073 LOFD-001046 TDLOFD-001046
Feature Name Flash CS Fallback to GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN PS Inter-RAT Mobility between E-UTRAN and GERAN Distance based inter-RAT handover to GERAN Service based inter-RAT handover to GERAN Service based inter-RAT handover to GERAN
Issue 04 (2012-09-20)
9-13
eRAN CS Fallback
10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 04 (2012-09-20)
10-1
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
Issue 04 (2012-09-20)
11-1

CS Fallback eRAN3 0 04

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CS Fallback eRAN3 0 04

Загружено:

Авторское право:

Доступные форматы

CS Fallback eRAN3.

Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

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

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

4.5 CSFB Exception Handling ............................................................................................................. 4-6

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

6 Impact on the Networks ..........................................................................................................6-1

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

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

7.11.5 CS Fallback with LAI to GERAN ....................................................................................... 7-44

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1.2 Intended Audience

1.3 Change History

04 (2012-09-20) 03 (2012-06-30) 02 (2012-05-11) 01 (2012-03-30) Draft A (2012-01-10)

Modified some descriptions of initial configuration in chapter None 7 "Engineering Guidelines."

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Change Type Feature change

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2.1 Network Architecture for CSFB to UTRAN/GERAN

SGSN: serving GPRS support node

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Supports one or more of the following functions:

2.2 Network Architecture for CSFB to CDMA2000 1xRTT

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Figure 2-2 Network architecture for CSFB to CDMA2000 1xRTT

S-GW: serving gateway

P-GW: PDN gateway

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

3 End-to-End Procedures for CSFB

PS redirection PS handover CCO with or without NACC (CCO/NACC)

3.1 CSFB to UTRAN

HSS: home subscriber server

VLR: visitor location register

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

3.1.2 CSFB Procedures for Mobile-originated Calls and Mobile-terminated Calls

CSFB based on PS handover CSFB based on PS redirection Flash CSFB

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

CSFB Based on PS Handover

RNC: radio network controller

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

CSFB Based on PS Redirection

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3 End-to-End Procedures for CSFB

3.1.3 CSFB Procedure for SMS

3.1.4 CSFB Procedure for Emergency Calls

3.1.5 CSFB Procedure for LCS