Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
eRAN6.0
Issue 03
Date 2013-06-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview.........................................................................................................................................4
2.1 Introduction....................................................................................................................................................................6
2.2 Benefits...........................................................................................................................................................................6
2.3 Architecture....................................................................................................................................................................6
5 Related Features...........................................................................................................................45
5.1 Features Related to LOFD-001033 CS Fallback to UTRAN.......................................................................................45
5.2 Features Related to LOFD-001034 CS Fallback to GERAN.......................................................................................45
5.3 Features Related to LOFD-001052 Flash CS Fallback to UTRAN.............................................................................46
5.4 Features Related to LOFD-001053 Flash CS Fallback to GERAN.............................................................................46
5.5 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN.......................................................................47
5.6 Features Related to LOFD-001069 CS Fallback with LAI to GERAN.......................................................................47
5.7 Features Related to LOFD-001078 E-UTRAN to UTRAN CS/PS Steering...............................................................48
5.8 Features Related to LOFD-001088 CS Fallback Steering to UTRAN.........................................................................48
5.9 Features Related to LOFD-001089 CS Fallback Steering to GERAN.........................................................................49
6 Network Impact...........................................................................................................................50
6.1 LOFD-001033 CS Fallback to UTRAN.......................................................................................................................50
6.2 LOFD-001034 CS Fallback to GERAN.......................................................................................................................51
6.3 LOFD-001052 Flash CS Fallback to UTRAN.............................................................................................................51
6.4 LOFD-001053 Flash CS Fallback to GERAN.............................................................................................................52
6.5 LOFD-001068 CS Fallback with LAI to UTRAN.......................................................................................................53
6.6 LOFD-001069 CS Fallback with LAI to GERAN.......................................................................................................53
6.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering...............................................................................................53
6.8 LOFD-001088 CS Fallback Steering to UTRAN.........................................................................................................53
6.9 LOFD-001089 CS Fallback Steering to GERAN.........................................................................................................54
7 Engineering Guidelines.............................................................................................................55
7.1 LOFD-001033 CS Fallback to UTRAN.......................................................................................................................55
7.1.1 When to Use CS Fallback to UTRAN.......................................................................................................................55
7.1.2 Required Information................................................................................................................................................55
7.1.3 Requirements.............................................................................................................................................................56
7.1.4 Data Preparation........................................................................................................................................................57
7.1.5 Precautions.................................................................................................................................................................60
7.1.6 Initial Configuration..................................................................................................................................................60
7.1.7 Activation Observation..............................................................................................................................................64
7.1.8 Deactivation...............................................................................................................................................................69
7.2 LOFD-001034 CS Fallback to GERAN.......................................................................................................................69
7.2.1 When to Use CS Fallback to GERAN.......................................................................................................................70
7.2.2 Required Information................................................................................................................................................70
7.2.3 Requirements.............................................................................................................................................................71
7.2.4 Data Preparation........................................................................................................................................................71
7.2.5 Precautions.................................................................................................................................................................76
7.2.6 Initial Configuration..................................................................................................................................................76
7.2.7 Activation Observation..............................................................................................................................................80
7.2.8 Deactivation...............................................................................................................................................................81
7.3 LOFD-001052 Flash CS Fallback to UTRAN.............................................................................................................81
7.3.1 When to Use Flash CS Fallback to UTRAN.............................................................................................................81
7.3.2 Required Information................................................................................................................................................82
7.3.3 Requirements.............................................................................................................................................................83
7.3.4 Data Preparation........................................................................................................................................................83
7.3.5 Precautions.................................................................................................................................................................88
7.3.6 Initial Configuration..................................................................................................................................................88
7.3.7 Activation Observation..............................................................................................................................................92
7.3.8 Deactivation...............................................................................................................................................................93
7.4 LOFD-001053 Flash CS Fallback to GERAN.............................................................................................................94
7.4.1 When to Use Flash CS Fallback to GERAN.............................................................................................................94
7.4.2 Required Information................................................................................................................................................94
7.4.3 Requirements.............................................................................................................................................................95
7.4.4 Data Preparation........................................................................................................................................................95
7.4.5 Precautions...............................................................................................................................................................100
7.4.6 Initial Configuration................................................................................................................................................100
7.4.7 Activation Observation............................................................................................................................................104
7.4.8 Deactivation.............................................................................................................................................................105
7.5 LOFD-001068 CS Fallback with LAI to UTRAN.....................................................................................................106
7.5.1 When to Use CS Fallback with LAI to UTRAN.....................................................................................................106
7.5.2 Required Information..............................................................................................................................................107
7.5.3 Requirements...........................................................................................................................................................108
7.5.4 Data Preparation......................................................................................................................................................108
7.5.5 Precautions...............................................................................................................................................................108
7.5.6 Initial Configuration................................................................................................................................................108
7.5.7 Activation Observation............................................................................................................................................108
7.5.8 Deactivation.............................................................................................................................................................109
7.6 LOFD-001069 CS Fallback with LAI to GERAN.....................................................................................................109
7.6.1 When to Use CS Fallback with LAI to GERAN.....................................................................................................109
7.6.2 Required Information..............................................................................................................................................109
7.6.3 Requirements...........................................................................................................................................................110
7.6.4 Data Preparation......................................................................................................................................................111
7.6.5 Precautions...............................................................................................................................................................111
7.6.6 Initial Configuration................................................................................................................................................111
7.6.7 Activation Observation............................................................................................................................................111
7.6.8 Deactivation.............................................................................................................................................................112
7.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering.............................................................................................112
7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering.............................................................................................112
7.7.2 Required Information..............................................................................................................................................112
7.7.3 Requirements...........................................................................................................................................................112
7.7.4 Data Preparation......................................................................................................................................................113
7.7.5 Precautions...............................................................................................................................................................115
7.7.6 Initial Configuration................................................................................................................................................115
7.7.7 Activation Observation............................................................................................................................................117
7.7.8 Deactivation.............................................................................................................................................................117
7.8 LOFD-001088 CS Fallback Steering to UTRAN.......................................................................................................118
7.8.1 When to Use CS Fallback Steering to UTRAN......................................................................................................118
7.8.2 Required Information..............................................................................................................................................119
7.8.3 Requirements...........................................................................................................................................................119
7.8.4 Data Preparation......................................................................................................................................................119
7.8.5 Precautions...............................................................................................................................................................126
7.8.6 Initial Configuration................................................................................................................................................126
7.8.7 Activation Observation............................................................................................................................................129
7.8.8 Deactivation.............................................................................................................................................................129
7.9 LOFD-001089 CS Fallback Steering to GERAN.......................................................................................................130
7.9.1 When to Use CS Fallback Steering to GERAN......................................................................................................130
7.9.2 Required Information..............................................................................................................................................130
7.9.3 Requirements...........................................................................................................................................................131
7.9.4 Data Preparation......................................................................................................................................................131
7.9.5 Precautions...............................................................................................................................................................135
7.9.6 Initial Configuration................................................................................................................................................135
7.9.7 Activation Observation............................................................................................................................................138
7.9.8 Deactivation.............................................................................................................................................................139
7.10 Performance Optimization........................................................................................................................................139
7.10.1 Performance Monitoring........................................................................................................................................139
7.10.2 Parameter Optimization.........................................................................................................................................140
7.11 Troubleshooting........................................................................................................................................................149
7.11.1 Fault 1....................................................................................................................................................................150
7.11.2 Fault 2....................................................................................................................................................................150
7.11.3 Fault 3....................................................................................................................................................................151
8 Parameters...................................................................................................................................152
9 Counters......................................................................................................................................202
10 Glossary.....................................................................................................................................236
11 Reference Documents.............................................................................................................237
1.1 Scope
This document describes the principles and procedures for circuit switched fallback (CSFB) to
universal terrestrial radio access network (UTRAN) or GSM/EDGE radio access network
(GERAN). It elaborates the functions provided by Huawei E-UTRAN NodeBs (eNodeBs)
during CSFB procedures. This document also provides engineering guidelines for setting the
essential parameters related to CSFB.
For details about CSFB to CDMA2000 1x Radio Transmission Technology (1xRTT), see LTE-
CDMA2000 CS Service Interworking Feature Parameter Description.
Any managed objects (MOs), parameters, alarms, or counters described below correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with the latest software release.
This document applies only to LTE FDD. Any "L"or "LTE" in this document refers to LTE
FDD, and "eNodeB" refers to LTE FDD eNodeB.
l Feature change: refers to a change in the CSFB feature of a specific product version.
l Editorial change: refers to a change in wording or the addition of information that was not
described in the earlier version.
Document Versions
The document versions are as follows:
l 02 (2013-05-31)
l 01 (2013-04-28)
l Draft A (2013-01-30)
02 (2013-05-31)
Compared with 01 (2013-04-28) of eRAN6.0, Issue 02 (2013-05-31) of eRAN6.0 includes the
following changes.
01 (2013-04-28)
This is the first official release.
Draft A (2013-01-30)
This is a draft for eRAN6.0.
Feature change Added the following features: Added the following parameters:
l LOFD-001088 CS Fallback l CSFallBackBlindHoCfg.
Flexible Steering to UTRAN IdleCsfbHighestPri
For details, see 4.5 CSFB l CSFallBackBlindHoCfg.
Flexible Steering. IdleCsfbSecondPri
l LOFD-001089 CS Fallback l CSFallBackBlindHoCfg.
Flexible Steering to GERAN IdleCsfbLowestPri
For details, see 4.5 CSFB
Flexible Steering. l CSFallBackBlindHoCfg.
InterRatHighestPri
l CSFallBackBlindHoCfg.
InterRatSecondPri
l CSFallBackBlindHoCfg.
InterRatLowestPri
l CSFallBackPolicyCfg.
IdleModeCsfbHoPolicyCfg
l CSFallBackPolicyCfg.
CsfbHoPolicyCfg
l UtranNFreq.
CsPsMixedPriority
l InterRatHoComm.
CellInfoMaxUtranCellNum
l InterRatHoComm.
CellInfoMaxGeranCellNum
Added the UtranCsfbSteer-
ingSwitch and
GeranCsfbSteeringSwitch
options to the
ENodeBAlgoSwitch.HoAlgoS
witchparameter.
2 Overview
This chapter describes the network architectures for CSFB to UTRAN/GERAN and the function
of each network element (NE).
In an early phase of EPS construction, operators who own a mature UTRAN or GERAN can
protect their investments in legacy CS networks and reduce their investments in the EPS by
using legacy CS networks to provide CS services 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
CSFB enables E-UTRAN UEs to fall back to CS networks to receive CS services, which helps
operators better utilize 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 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.
Table 2-1 lists the optional features described in this document and the corresponding chapters
describing related principles and algorithms.
2.1 Introduction
As specified in 3GPP TS 23.272 V8.5.0, CSFB is a solution that enables a UE to register with
both an EPS network and a legacy CS network. When such a UE initiates a voice service, the
EPS network instructs the UE to fall back to the legacy CS network before the UE performs the
service.
When a UE sends or receives an SMS message, the message is transmitted between the EPS
network and the legacy CS network without requiring CSFB. This is achieved by SMS over
SGs.
2.2 Benefits
CSFB brings the following benefits:
l Facilitates voice services for the LTE network.
l Facilitates SMS and LCS services for the LTE network.
l Helps operators reduce costs by reusing legacy CS networks and not requiring IMS network
deployment.
2.3 Architecture
To implement CSFB to UTRAN/GERAN, an SGs interface is required between the MME and
the MSC server. Figure 2-1 shows the network architecture for CSFB to UTRAN/GERAN.
After a UE is powered on in the E-UTRAN shown in Figure 2-1, it initiates a combined EPS/
IMSI attach procedure. Then, the MME performs a UE location update over the SGs interface
so that the UMTS or GSM core network learns about the UE location.
If a UE is camping on an E-UTRAN cell, it periodically initiates a combined TAU/LAU
procedure, which allows simultaneous UE location updates both in the MME and in the UMTS
or GSM core network.
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.
SGs interface l Is an interface between the MME and the MSC server.
l Assists mobility management and paging between the EPS and the CS
network.
l Transmits SMS messages.
l Transmits messages related to combined attach and combined TAU/
LAU.
Element Function
Element Function
SGSN l 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.
l Supports RIM, which is required when flash CSFB or CCO with NACC
is used as the CSFB mechanism.
NOTE
ISR is a mechanism for reducing the inter-RAT cell reselection signaling of a UE in
idle mode. RAT is short for radio access technology. For details about ISR, see Annex
J in 3GPP TS 23.401 V9.2.0.
This chapter describes the functions that a Huawei eNodeB performs during end-to-end
procedures for CSFB, including the following:
l Combined EPS/IMSI attach
l CSFB procedure for mobile-originated calls
l CSFB procedure for mobile-terminated calls
l CSFB procedure for SMS
l CSFB procedure for emergency calls
l CSFB procedure for LCS
Regarding the capabilities of UEs and networks, Huawei provides the following mechanisms
for eNodeBs to perform CSFB to UTRAN or GERAN for mobile-originated calls and mobile-
terminated calls:
l PS redirection
l PS handover
l CCO with or without NACC (CCO/NACC)
NOTE
The symbols that appear in signaling procedure figures throughout this document are explained as follows:
l An arrow denotes the transmission of a message.
l A plain box denotes a mandatory procedure.
l A dashed box denotes an optional procedure.
1. The UE sends a Combined attach request message to the MME, requesting a combined
EPS/IMSI attach procedure. This message also indicates whether the CSFB or SMS over
SGs function is required.
2. The EPS attach procedure is performed in the same way as it is performed within the LTE
system. For details, see section 5.3.2 in 3GPP TS 23.401 V9.2.0.
3. The MME allocates an LAI to the UE, and then it finds the MSC/VLR for the UE based
on the LAI. If multiple PLMNs are available for the CS domain, the MME selects a PLMN
based on the selected PLMN information reported by the eNodeB. Then, the MME sends
the MSC/VLR a Location update request message, which contains the new LAI, IMSI,
MME name, and location update type.
4. The MSC/VLR performs the location update procedure in the CS domain.
5. The MSC/VLR responds with a Location update accept message that contains information
about the VLR and temporary mobile subscriber identity (TMSI). The location update
procedure is successful.
6. The UE is informed that the combined EPS/IMSI attach procedure is successful. If the
network supports SMS over SGs but not CSFB, the message transmitted to the UE contains
the information element (IE) SMS-only. The message indicates that the combined EPS/
IMSI attach procedure is successful but only SMS is supported.
This section describes the procedure for CSFB to UTRAN based on PS handover for mobile-
originated calls, as shown in Figure 3-2.
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details,
see chapter 4 CSFB at the eNodeB.
5. After the handover, the UE may initiate a CS call establishment procedure with an LAU
or combined RAU/LAU procedure in the UTRAN.
6. The follow-up procedures are performed for the PS handover. These procedures include
data forwarding, path switching, and RAU. This step is performed together with step 5.
NOTE
For details about the PS handover procedure, see Mobility Management in Connected Mode Feature
Parameter Description and section 5.5.2 in 3GPP TS 23.401 V9.2.0.
network. After selecting the UTRAN, the UE acquires the system information of a UTRAN cell.
Then, the UE performs initial access to the cell to initiate a CS service. For the UTRAN, the UE
is an initially accessing user.
This section describes the procedure for CSFB to UTRAN based on PS redirection for mobile-
originated calls, as shown in 3.1.2 CSFB Procedures for Mobile-originated Calls and Mobile-
terminated Calls.
1. The UE sends the MME a NAS message Extended service request to initiate a CS service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure.
If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the UE capabilities,
parameters settings, and algorithm policies. For details, see section 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
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details,
see chapter 4 CSFB at the eNodeB.
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in the
target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.
In a mobile-terminated call, the MSC sends a Paging Request message from the CS domain to
the MME over the SGs interface. Then, the MME or the eNodeB initiates a paging procedure
for the UE, as shown in Figure 3-3. The subsequent steps are the same as the steps in the
procedure for CSFB to UTRAN based on PS redirection for mobile-originated calls.
Flash CSFB
During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it
sends an RRC Connection Release message to release the UE. The message contains information
about a target UTRAN frequency, as well as one or more physical cell identities and their
associated system information. In this way, the UE can quickly access the target UTRAN without
the need to perform the procedure for acquiring system information of the target UTRAN cell.
Then, the UE can directly initiate a CS service in the UTRAN cell.
NOTE
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must support 3GPP
Release 9 or later.
This section describes the procedure for flash CSFB to UTRAN for mobile-originated calls, as
shown in Figure 3-5.
1. The UE sends the MME a NAS message Extended service request to initiate a CS service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure.
If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the UE capabilities,
parameters settings, and algorithm policies. For details, see section 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, 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.
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.
As the SMS service is transparent to the eNodeB, the procedure is not described in this document.
For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in
the handover restriction list when selecting the target cell. The eNodeB sends the RNC a
handover request with the IE CSFB high priority in the IE Source to Target Transparent
Container. This request informs the RNC that a CSFB procedure is required for an emergency
call. Upon receiving the information, the RNC preferentially processes this call when using
related algorithms such as admission control.
If redirection is used for CSFB for emergency calls, the RRC Connection Request message that
the UE sends when accessing the UTRAN contains the indication of 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.
The RIM procedure supports two information exchange modes: Single Report and Multiple
Report. In Single Report mode, the source sends a request, and then the target responds with a
single report. In Multiple Report mode, the target responds with a report after receiving a request
from the source, and it also sends a report to the source each time the system information changes.
For details, see section 8c in 3GPP TS 48.018.
The Huawei eNodeB supports the two information exchange modes, and it acquires the system
information of UTRAN cells during the RIM procedure. The Multiple Report mode is enabled
or disabled by setting the ENodeBAlgoSwitch.RimSwitch parameter, while the Single Report
mode is not configurable. The RIM procedure and parameter settings are described as follows:
l If UTRAN_RIM_SWITCH under the ENodeBAlgoSwitch.RimSwitch parameter is
turned on, the RIM procedure in Multiple Report mode is performed as follows: After an
external UTRAN cell corresponding to the neighboring UTRAN cell is configured, the
eNodeB sends a request for system information to the neighboring UTRAN cell. If the
neighboring UTRAN cell supports Multiple Report mode, after the neighboring UTRAN
cell receives the request or the system information changes, this cell sends the system
information to the eNodeB.
NOTE
The multiple report RIM procedure can be triggered only when the MME supports 3GPP Release 9
or later. Whether an RIM procedure in Multiple Report mode can be triggered is based on the settings
of the RIM switch and external UTRAN cells. For example, the RIM procedure cannot be triggered
if the RIM switch is turned on but no external UTRAN cell is configured. If an external UTRAN cell
has been configured, an RIM procedure is triggered each time the RIM switch is turned on.
l If flash CSFB to UTRAN is enabled and UTRAN_RIM_SWITCH under the
ENodeBAlgoSwitch.RimSwitch parameter is turned off, the eNodeB obtains the system
information of the neighboring UTRAN cells by performing an RIM procedure in Single
Report mode.
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.
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details,
see chapter 4 CSFB at the eNodeB.
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 3.1.2 CSFB Procedures for Mobile-originated Calls and Mobile-
terminated Calls. The subsequent steps are the same as the steps in the procedure for CSFB to
GERAN based on PS redirection for mobile-originated calls.
NOTE
The eNodeB selects a fallback mechanism and a target cell using the CSFB algorithm. For details,
see chapter 4 CSFB at the eNodeB.
5. After the handover, the UE may initiate a CS call establishment procedure with an LAU
or combined RAU/LAU procedure in the GERAN.
6. The follow-up procedures are performed for the PS handover. These procedures include
data forwarding, path switching, and RAU. This step is performed together with step 5.
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.
1. The UE sends the MME a NAS message Extended service request to initiate a CS service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure.
If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the UE capabilities,
parameters settings, and algorithm policies. For details, see section 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
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 initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target
cell.
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are
suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
8. The MME initiates an S1 UE context release procedure.
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 CCO/NACC for mobile-originated calls.
Flash CSFB
During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it
sends an RRC Connection Release message to release the UE. The message contains information
about a target GERAN carrier frequency group, as well as one or more physical cell identities
and their associated system information. The UE searches for a target cell based on the
information it received, and then it performs initial access to the cell to initiate a CS service. If
the GERAN or some GERAN-supporting UEs do not support DTM, the ongoing PS services
must be suspended before the CS services can be established.
NOTE
Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must support 3GPP
Release 9 or later.
This section describes the procedure for flash CSFB to GERAN for mobile-originated calls, as
shown in Figure 3-10.
1. The UE sends the MME a NAS message Extended Service Request to initiate a CS service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure.
If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the UE capabilities,
parameters settings, and algorithm policies. For details, see section 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 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 initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target
cell.
6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are
suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
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.
As the SMS service is transparent to the eNodeB, the procedure is not described in this document.
For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in
the handover restriction list when selecting the target cell.
If redirection is used for CSFB for emergency calls, the Channel Request message that the UE
sends when accessing the GERAN contains the indication of 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.
If the GERAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the MSC
sends an LCS indicator to the MME over the SGs interface. Then, the MME instructs the eNodeB
to perform CSFB for the UE. The CSFB procedure is the same as the procedure for CSFB to
GERAN for mobile-terminated calls. The UE performs the LCS service after the fallback to the
GERAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272 V10.0.0 and
LCS Feature Parameter Description.
The multiple report RIM procedure can be triggered only when the MME supports 3GPP Release 9
or later. Whether an RIM procedure in Multiple Report mode can be triggered is based on the settings
of the RIM switch and external GERAN cells. For example, the RIM procedure cannot be triggered
if the RIM switch is turned on but no external GERAN cell is configured. If an external GERAN cell
has been configured, an RIM procedure is triggered each time the RIM switch is turned on.
l If flash CSFB to GERAN or CCO/NACC is enabled but GERAN_RIM_SWITCH under
the ENodeBAlgoSwitch.RimSwitch parameter is turned off, the eNodeB obtains the
system information of the neighboring GERAN cells by performing the RIM procedure in
Single Report mode when CCO/NACC or PS redirection is used as a mechanism for CSFB.
This chapter describes the CSFB procedure performed by Huawei eNodeB and provides the
setting descriptions for the parameters involved.
The enhanced CSFB functions described in subsequent sections are based on the CSFB functions described
in this section.
As shown in the figure, 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
In this chapter, "handover" is a generic term used to refer to normal handover, CCO/NACC, and
redirection.
CSFB mechanisms include PS redirection, PS handover, and CCO/NACC. No matter which CSFB
mechanism is adopted, both measurement-based handovers and blind handovers are applicable, and
the blind handover switch is specified by BlindHoSwitch under the
ENodeBAlgoSwitch.HoModeSwitch 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 flash CSFB is enabled and blind handovers are allowed, the principles for choosing between a
blind handover and a measurement-based handover differ from the principles described in this
section. For details, see section 4.2 Flash CSFB.
If the PS handover switch is turned on, it is recommended that the blind handover switch be
turned off to increase the CSFB success rate. The UtranPsHoSwitch and GeranPsHoSwitch
options under the ENodeBAlgoSwitch.HoModeSwitch parameter specify whether to enable PS
handover to UTRAN and GERAN, respectively.
NOTE
If CSFB with LAI or E-UTRAN to UTRAN CS/PS Steering is enabled, the principles for selecting
frequencies to measure or a target cell differ from the principles described in this section. For details, see
sections 4.3 CSFB with LAI and 4.4 E-UTRAN to UTRAN CS/PS Steering.
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. As defined in section 5.5.4.7 in 3GPP TS 36.331 V10.0.0, the
entering and leaving conditions of event B1 are as follows:
l Entering condition: Mn + Ofn - Hys > Thresh
l Leaving condition: Mn + Ofn + Hys < Thresh
where
l Mn is the measurement result of the neighboring cell.
l 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.
l Hys is the hysteresis for event B1. The hysteresis values for CSFB to UTRAN and GERAN
are contained in the measurement configuration.
l Thresh is the threshold for event B1. The values of Thresh are set based on the measurement
quantities for each RAT, as follows:
The received signal code power (RSCP) threshold for CSFB to UTRAN is specified by
CSFallBackHo.CsfbHoUtranB1ThdRscp.
The Ec/No threshold for CSFB to UTRAN is specified by
CSFallBackHo.CsfbHoUtranB1ThdEcn0.
The received signal strength indicator (RSSI) threshold for CSFB to GERAN is
specified by CSFallBackHo.CsfbHoGeranB1Thd.
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 is specified by the
CSFallBackHo.CsfbHoUtranTimeToTrig and CSFallBackHo.CsfbHoGeranTimeToTrig
parameters, respectively.
The following parameters related to event B1 for CSFB are the same as those related to event
B1 for inter-RAT handovers:
For details, see Mobility Management in Connected Mode Feature Parameter Description.
After having received the B1 measurement reports for CSFB, the eNodeB generates a list of
candidate cells for CSFB and selects the cell with the highest signal quality from this list as the
target cell.
NOTE
If CSFB with LAI is enabled, the decision phase of CSFB may be different. For details, see 4.3 CSFB with
LAI.
If load-based CSFB is enabled, the principles for determining CSFB may be different. For details,
see 4.6 Load-based CSFB.
Flash CSFB provides a fast CSFB mechanism. It shortens the end-to-end latency and therefore
improves user experience with CS service access. Flash CSFB uses either of the following
methods:
Flash CSFB requires basic CSFB functions and also has enhanced blind handover and redirection
functions.
Enhanced Redirection
During a redirection procedure, an eNodeB can deliver the system information of a certain
number of cells. The maximum number (indicated by N in this section) is specified by the
InterRatHoComm.CellInfoMaxUtranCellNum parameter for UTRAN cells or the
InterRatHoComm.CellInfoMaxGeranCellNum parameter for GERAN cells.
l In a blind handover
Among cells that operate on the target UTRAN frequency or GERAN carrier frequency
group, the eNodeB queues candidate cells for the handover in the following sequence: (1)
cells that are assigned blind-handover priorities in descending order; (2) other cells.
l In a measurement-based handover
Among cells that operate on the target UTRAN frequency or GERAN carrier frequency
group, the eNodeB queues candidate cells in the following sequence: (1) neighboring cells
indicated in the measurement report, in descending order of signal strength; (2) other cells.
In either scenario, the eNodeB then filters out cells to which handovers are prohibited and cells
whose system information has not been obtained. If the number of qualified cells in the queue
exceeds N, the eNodeB selects the first N cells. If the number of qualified cells is equal to or
less than N, the eNodeB selects all these cells.
For engineering guidelines, see section 7.6 LOFD-001069 CS Fallback with LAI to
GERAN.
NOTE
CSFB with LAI is under license control, but not switch control.
CSFB with LAI applies to target network selection in multi-PLMN scenarios or location area
code (LAC) selection in multi-LAC scenarios, as follows:
The MME delivers the LAI information to the eNodeB in the IE Registered LAI contained in
an Initial Context Setup Request or UE Context Modification Request message. After receiving
the LAI information, the eNodeB takes the following actions for a handover (in addition to those
described in section 4.1 Basic Functions):
l In a blind handover
The eNodeB checks all inter-RAT neighboring cells of the cell serving the UE and considers
the following three sets of cells (in descending order of priority) based on the LAI:
Set 1: neighboring cells with the same PLMN ID and LAC as those indicated in the LAI
received.
Set 2: neighboring cells with the same PLMN ID as, but different LACs from, those
indicated in the LAI received.
Set 3: neighboring cells located in the serving PLMN of the UE. If the
InterPlmnHoSwitch option under the ENodeBAlgoSwitch.HoAlgoSwitch parameter
is selected, neighboring cells in other PLMNs in the PLMN list are also considered.
The eNodeB selects the CSFB target cell from the set that has the highest priority among
all sets whose criteria apply to at least one cell. 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 to be the CSFB target cell. If the three sets are all empty,
the eNodeB delivers the inter-RAT measurement configuration to the UE, and CSFB
will be performed in the form of a measurement-based handover.
l In a measurement-based handover
The eNodeB delivers information about an inter-RAT frequency in the measurement
configuration to the UE if all the following conditions are met:
The PLMN ID of any inter-RAT neighboring cell on this frequency is the same as the
PLMN ID in the LAI received.
The UE supports this RAT.
The UE is capable of measuring this frequency.
After receiving a measurement report from the UE, the eNodeB considers the candidate
cells in sets 1 and 2. The eNodeB sorts cells in each candidate cell list by signal quality and
selects a target cell from the lists in descending order of signal quality. For details about
sets 1 and 2, see the previous description of a blind handover.
NOTE
If the eNodeB fails to select frequencies and target cells based on the LAI information delivered by the
MME, the eNodeB performs the procedure, as in scenarios where the eNodeB does not receive an LAI,
described in section Selecting Frequencies to Measure or a Target Cell.
Basic Functions
The eNodeB selects a target UTRAN frequency for CSFB based on whether UEs are performing
CS services and on the CS service priorities of UTRAN frequencies. In addition to the principles
described in section 4.1 Basic Functions, the eNodeB adopts the following principles for a blind
handover or a measurement-based handover:
l In a blind handover
If LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is enabled and the
UtranFreqLayerBlindSwitch option under the ENodeBAlgoSwitch.FreqLayerSwtich
parameter is selected, the eNodeB first selects a RAT with the highest blind-handover
priority. If the selected RAT is UTRAN, the eNodeB performs E-UTRAN to UTRAN CS
steering to select a target frequency or cell for the blind handover, following the principles
illustrated in Figure 4-4.
Figure 4-4 Target frequency/cell selection for a blind handover using E-UTRAN to UTRAN
CS steering
The eNodeB first selects UTRAN frequencies with the highest CS service priority
(specified by the UTRANNFREQ.CsPriority parameter). If there are multiple UE-
supported frequencies with the highest CS service priority, the eNodeB queues candidate
cells on these frequencies in the following sequence: (1) cells with blind-handover priorities
(specified by the UTRANNCELL.BlindHoPriority parameter) in descending order; (2)
cells on frequencies with priorities for RRC_CONNECTED UEs (specified by the
UTRANNFREQ.ConnFreqPriority parameter) in descending order. If there are still
multiple frequencies with the same priority, the eNodeB randomly selects a target frequency
for a blind handover.
If the UE does not support the frequencies with the highest CS service priority, the eNodeB
selects UTRAN frequencies with the second highest CS service priority for evaluation
shown in Figure 4-4.
l In a measurement-based handover
If LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is enabled and the
UtranFreqLayerMeasSwitch option under the ENodeBAlgoSwitch.FreqLayerSwtich
parameter is selected, the eNodeB selects UTRAN frequencies to measure based on the
following principles:
If the UE supports the frequencies with the highest CS service priority, the eNodeB
instructs the UE to measure only the frequencies with the highest CS service priority,
but not frequencies with lower CS service priorities even if measurements fail for the
frequencies with the highest CS service priority.
If the UE does not support the frequencies with the highest CS service priority or no
neighboring UTRAN cell operates on the frequencies with the highest CS service
priority, the eNodeB evaluates frequencies with lower CS service priorities. The
eNodeB delivers measurement configurations to the UE only when the eNodeB finds
a UE-supported UTRAN frequency on which a neighboring UTRAN cell operates.
NOTE
Figure 4-5 Target frequency/cell selection for a blind handover using CSFB with LAI and E-
UTRAN to UTRAN CS steering
l In a measurement-based handover
The eNodeB selects the frequencies that meet all the following conditions:
The PLMN ID of any inter-RAT neighboring cell on a frequency is the same as the
PLMN ID in the received LAI.
The UE supports this RAT.
The UE is capable of measuring the frequency.
Then, in the measurement configuration to the UE, the eNodeB delivers information
about inter-RAT frequencies with the highest CS service priority.
CSFB flexible steering provides a flexible method to select a target frequency for CSFB. Based
on the network plan and load balancing requirements, operators that have both E-UTRAN and
inter-RAT networks can transfer UEs to specified RATs and frequencies. Flexible steering can
be performed based on the following factors:
l Priorities of UTRAN frequencies in carrying CS services and CS+PS services. For example,
R99 frequencies preferentially carry CS services, and High Speed Packet Access (HSPA)
frequencies preferentially carry CS+PS services.
l CSFB mechanisms, including handover-based CSFB, redirection-based CSFB, and CCO-
based CSFB
CSFB flexible steering applies to UEs in idle mode and connected mode. If the
UtranCsfbSteeringSwitch or GeranCsfbSteeringSwitch option under the
ENodeBAlgoSwitch.HoAlgoSwitchparameter is selected, the eNodeB verifies UE status after
receiving a CS Fallback Indicator as follows:
l If the CS Fallback Indicator is contained in an Initial Context Setup Request message, the
eNodeB determines that the UE is in idle mode, that is, only a CS service is requested.
l If the CS Fallback Indicator is contained in a UE Context Modification Request message,
the eNodeB determines that the UE is in connected mode, that is, both CS and PS services
are requested.
l The eNodeB selects a target RAT based on the RAT priorities specified by the
CSFallBackBlindHoCfg.IdleCsfbHighestPri,
CSFallBackBlindHoCfg.IdleCsfbSecondPri, and
CSFallBackBlindHoCfg.IdleCsfbLowestPri parameters.
If the selected target RAT is UTRAN, the eNodeB selects a target frequency based on the
setting of the UtranNFreq.CsPriorityparameter. For details, see section 4.4 E-UTRAN to
UTRAN CS/PS Steering.
l The eNodeB selects a CSFB mechanism based on the setting of the
CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter: handover, CCO, or
redirection in descending order.
respectively, and sends these two IEs to the eNodeB through a RAN-INFORMATION
message that contains the IE Multiple Report-Initial.
NOTE
When the UTRAN cell load status is normal, the RNC does not include the IE overload flag in the
RAN-INFORMATION message that contains the IE Multiple Report-Initial.
Huawei RNCs extend the overload flag IE value specified in 3GPP specifications: from overload to
overload and congestion.
3. After sending the RAN-INFORMATION message that contains the IE Multiple Report-
Initial, if the UTRAN cell load status changes, the RNC notifies the eNodeB about the
updated UTRAN cell load status through a RAN-INFORMATION message that contains
the IE Multiple Report.
The eNodeB saves the UTRAN cell load value and load status and uses this information to select
a target UTRAN cell for CSFB.
NOTE
measured UTRAN cells, the eNodeB preferentially selects GERAN cells for the emergency
redirection.
If flash CSFB is enabled, the eNodeB sends system information about the neighboring GERAN
or UTRAN cells to UEs for redirections after the CSFB protection timer expires. The maximum
number of neighboring GERAN or UTRAN cells whose system information can be included in
one redirection message sent to a UE is specified by the
INTERRATHOCOMM.GeranCellNumForEmcRedirect or
INTERRATHOCOMM.UtranCellNumForEmcRedirect parameter, respectively.
If the eNodeB determines to perform CSFB in the form of a blind handover, but the candidate
cell with the highest blind-handover priority fails the handover preparation, the eNodeB selects
another cell based on the blind-handover priorities in descending order. The eNodeB can initiate
handover attempts to a maximum of eight candidate cells that are configured with blind-handover
priorities. If all attempts fail, the eNodeB performs a blind redirection procedure for CSFB.
5 Related Features
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Affected Features
None
Impacted Features
This feature affects LOFD-001089 CS Fallback Steering to GERAN. In overlapping coverage
of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to UTRAN and
LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously, achieve CSFB
steering to different RATs.
Impacted Features
This feature affects LOFD-001088 CS Fallback Steering to UTRAN. In overlapping coverage
of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to UTRAN and
LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously, achieve CSFB
steering to different RATs.
6 Network Impact
l If redirection is used as the CSFB mechanism, no extra signaling message is required for
the UTRAN because each CSFB procedure is equivalent to the initiation of a new CS
service. The EPS does not need to interact with the target network, and the corresponding
signaling overhead is negligible.
l If PS handover is used as the CSFB mechanism, extra signaling messages are required from
each NE for the request, preparation, and execution of each handover. However, from the
perspective of traffic statistics, the number of UEs that initiate CS services per second per
cell during peak hours is far below cell capacity. Therefore, signaling overhead caused by
PS handovers is low.
Load-based CSFB to UTRAN prevents PS handover preparation failure caused by UTRAN cell
congestion, because the eNodeB selects a target cell based on the UTRAN cell load status. This
increases system capacity.
Network Performance
CSFB affects the access success rate as follows:
l If redirection is used as the CSFB mechanism, each CSFB procedure is equivalent to the
initiation of a new CS service. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the UTRAN.
l If PS handover is used as the CSFB mechanism, the access success rate for CSFB UEs
depends on the success rate of handovers to the target RAT. Handover-triggered CS service
access has a higher requirement for signal quality compared with normal CS service access.
Therefore, the access success rate for CSFB UEs is a little lower than that for normal CS
UEs in the UTRAN.
Load-based CSFB to UTRAN prevents PS handover preparation failure caused by UTRAN cell
congestion, because the eNodeB selects a target cell based on the UTRAN cell load status. This
decreases the CSFB delay.
Network Performance
CSFB affects the access success rate as follows:
l If redirection or CCO/NACC is used as the CSFB mechanism, each CSFB procedure is
equivalent to the initiation of a new CS service. Therefore, the access success rate for CSFB
UEs is theoretically the same as that for normal CS UEs in the GERAN.
l If PS handover is used as the CSFB mechanism, the access success rate for CSFB UEs
depends on the success rate of handovers to the target RAT. Handover-triggered CS service
access has a higher requirement for signal quality compared with normal CS service access.
Therefore, the access success rate for CSFB UEs is a little lower than that for normal UEs
in the GERAN.
Network Performance
Flash CSFB affects the access success rate as follows:
l Each flash CSFB procedure is equivalent to the initiation of a new CS service. Therefore,
the access success rate for CSFB UEs is theoretically the same as that for normal CS UEs
in the UTRAN.
l The RRC connection setup success rate may decrease slightly for the UTRAN. The uplink
interference information contained in SIB7 in the UTRAN updates frequently. The RNC
cannot update the uplink interference information in the system information sent to the LTE
network based on SIB7 in the UTRAN. Therefore, the uplink interference information
contained in SIB7 in the LTE network is a default value (105 dBm). If the actual uplink
interference in the UTRAN is greater than 105 dBm, the transmit power on UEs' physical
random access channel (PRACH) increases and the RRC connection setup success rate
may decrease.
Flash CSFB to UTRAN decreases the CSFB delay by up to 1.28s because UEs obtain information
about the target UTRAN cell for redirection before RRC connections to the LTE network are
released.
Network Performance
If flash CSFB is used as the CSFB mechanism, each CSFB procedure is equivalent to the
initiation of a new CS service. Therefore, the access success rate for CSFB UEs is theoretically
the same as that for normal CS UEs in the GERAN.
Flash CSFB to GERAN decreases the CSFB delay by up to 2s because UEs obtain information
about the target GERAN cell for redirection before RRC connections to the LTE network are
released.
Network Performance
CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has attached.
This prevents CSFB failure or long delay caused by incorrect target RAT selection and increases
the CSFB success rate.
Network Performance
CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has attached.
This prevents CSFB failure or long delay caused by incorrect target RAT selection and increases
the CSFB success rate.
Network Performance
E-UTRAN to UTRAN CS/PS Steering enables an eNodeB to include only UTRAN frequencies
with a high CS service priority in measurement configurations. This prevents redundant
measurements, reduces the measurement time, and decreases end-to-end CSFB delay.
If the CS service priorities of UTRAN frequencies configured on the eNodeB are consistent with
those configured at the UTRAN side, E-UTRAN to UTRAN CS/PS Steering prevents further
intra-UTRAN handovers for service steering. This improves user experience.
Network Performance
If the frequency with the highest priority is inappropriately configured, for example, if the
highest-priority frequency has coverage holes, a UE may fail to measure this frequency and
therefore the CSFB delay increases.
Network Performance
If the frequency with the highest priority is inappropriately configured, for example, if the
highest-priority frequency has coverage holes, a UE may fail to measure this frequency and
therefore the CSFB delay increases.
7 Engineering Guidelines
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach, combined EPS/IMSI detach, and combined
TAU/LAU
l CS signaling message routing
l SMS over SGs
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the SGs interface
SGSN Does not activate ISR during the combined RAU/LAU procedure initiated
by the UE.
l Collect the following information about the UEs that support UMTS and LTE on the live
network:
Supported frequency bands
Whether the UEs support redirection from E-UTRAN to UTRAN
Whether the UEs support PS handover from E-UTRAN to UTRAN
Whether the UEs support UTRAN measurements
This information is used to configure neighboring UTRAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Mobility
Management in Connected Mode Feature Parameter Description.
l Collect information about the RNC, MME, and SGSN to check whether they all support
RIM procedures. This information is used to determine whether to enable load-based CSFB.
7.1.3 Requirements
Operating Environment
For CSFB to UTRAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be SAE1.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB to
UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-2.
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with
UTRAN cells. This section provides only the information about managed objects (MOs) related
to neighboring UTRAN cells. For more information about how to collect data for the parameters
in these MOs, see Mobility Management in Connected Mode Feature Parameter Description.
Collect data for the parameters in the following MOs:
l UtranNFreq: used to configure neighboring UTRAN frequencies.
l UtranExternalCell: used to configure external UTRAN cells. If PS handover is used, the
UtranExternalCell.Rac parameter must be set.
l UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared external
UTRAN cell. This MO is required only if the NodeB that provides the external UTRAN
cell works in RAN sharing with common carriers mode and multiple operators share the
external UTRAN cell.
l 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.
Handover ENodeBA Network Set this parameter based on the network plan.
Mode lgoSwitch. plan l To activate PS handovers, select the
switch HoModeS (negotiatio UtranPsHoSwitch(UtranPsHoSwitch) check
witch n not box. If this check box is not selected, redirection
required) will be used for CSFB to UTRAN.
l 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.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set the blind-handover priorities of different RATs for CSFB.
CN CSFallBa Network Set this parameter based on the network plan. This
Operator ckBlindH plan parameter identifies the operator whose RAT blind-
ID oCfg. (negotiatio handover priorities are to be set.
CnOperat n not
orId required)
Highest CSFallBa Network Set this parameter based on the network plan. This
priority ckBlindH plan parameter is set to UTRAN by default and specifies
InterRat oCfg. (negotiatio the high-priority RAT to be considered in blind
InterRatH n not handovers for CSFB. For CSFB to UTRAN, retain
ighestPri required) the default value.
Second CSFallBa Network Set this parameter based on the network plan. This
priority ckBlindH plan parameter is set to GERAN by default and specifies
InterRat oCfg. (negotiatio the second-highest-priority RAT to be considered in
InterRatSe n not blind handovers for CSFB. Ensure that this
condPri required) parameter is set to a different value from the
CSFallBackBlindHoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallBa Network Set this parameter based on the network plan. This
priority ckBlindH plan parameter is set to CDMA2000 by default and
InterRat oCfg. (negotiatio specifies the low-priority RAT to be considered in
InterRatL n not blind handovers for CSFB. Ensure that this
owestPri required) parameter is set to a different value from the
CSFallBackBlindHoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
UTRAN CSFallBa Network Set this parameter based on the network plan. This
LCS ckBlindH plan parameter specifies the LCS capability of the
capability oCfg. (negotiatio UTRAN.
UtranLcs n not
Cap required)
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
activate load-based CSFB.
The following table describes the parameter that must be set in the GLOBALPROCSWITCH
MO to set load-based CSFB to UTRAN.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.
CSFB CSFallBac Network Set this parameter based on the network plan. The
Protection kHo. plan default value 4 applies to a GSM+UMTS+LTE
Timer CsfbProtec (negotiatio network. The value 2 is recommended for a UMTS
tionTimer n not +LTE network. If this parameter is set too large, the
required) CSFB delay increases in abnormal CSFB
scenarios. If this parameter is set too small, normal
measurement or handover procedures may be
interrupted.
The following table describes the parameter that must be set in the InterRatHoComm MO to
set the maximum number of neighboring UTRAN cells whose system information is sent to UEs
for emergency redirections.
7.1.5 Precautions
None
l The managed objects (MOs) in Table 7-3 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 7-3 are not contained in a scenario-specific summary data file. In this
situation, customize a summary data file to include the MOs before you can set the
parameters.
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-3 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
Step 1 Run the following commands to add neighbor relationships with UTRAN cells:
l ADD UTRANNFREQ
l ADD UTRANEXTERNALCELL
l ADD UTRANEXTERNALCELLPLMN
l 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.
Step 4 (Optional) Run the MOD CSFALLBACKHO command to set the CSFB protection timer.
Step 5 (Optional) Run the MOD INTERRATHOCOMM command to set the maximum number of
neighboring UTRAN cells whose system information is to be sent to UEs for emergency
redirections.
Step 6 (Optional) Run the MOD ENODEBALGOSWITCH command with the
CSFBLoadInfoSwitch(CSFBLoadInfoSwitch) check box selected to enable load-based
CSFB.
Step 7 (Optional) Run the MOD GLOBALPROCSWITCH command with the Choose UMTS Cell
Load Info Trans Channel parameter set to BASED_ON_RIM.
----End
the UE was in idle mode before the call and is forced to fall back to the UTRAN using a
redirection.
NOTE
The same UE is shown in the left and right sides of the figure. This applies to all figures in the rest of this
document. The messages on the UMTS side are only for reference.
If the UE capability is not included in the Initial Context Setup Request (Initial Context Setup
Req in the figures) message, the eNodeB initiates a UE capability transfer procedure immediately
after receiving this message from the MME. If the UE capability is included in the Initial Context
Setup Request message, the eNodeB initiates a UE capability transfer procedure after sending
an Initial Context Setup Response (Initial Context Setup Rsp in the figures) message to the MME.
If measurement-based redirection is used for CSFB to UTRAN, the eNodeB delivers the B1-
related measurement configuration.
If blind redirection is used for CSFB to UTRAN, the eNodeB does not deliver the B1-related
measurement configuration but sends an RRC Connection Release (RRC Conn Rel in the
figures) message to the UE. The procedures indicated by dashed lines in Figure 7-2 and Figure
7-3 are optional. As shown in the red and green boxes in Figure 7-4, in the RRC Connection
Release message, the cause value is "other" and the target RAT is UTRAN. For an emergency
call, the cause value is "CSFBhighpriority."
Figure 7-4 The RRC Connection Release message during CSFB to UTRAN
If PS handover is used for CSFB to UTRAN, the eNodeB initiates a PS handover procedure
after receiving a measurement report from the UE, instead of sending an RRC Connection
Release message to the UE. Figure 7-5 shows the PS handover procedure. As shown in the red
and green boxes in Figure 7-6, in the handover command sent over the air interface, the cs-
FallbackIndicator IE is TRUE and the target RAT is UTRAN.
Counter Observation
Table 7-4 lists the performance counters for observing functions related to CSFB to UTRAN.
7.1.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-5.
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the
serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach, combined
EPS/IMSI detach, and combined TAU/
LAU
l Routing of CS signaling messages
l SMS over SGs
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the
SGs interface
l Collect the following information about the UEs that support GSM and LTE on the live
network:
7.2.3 Requirements
Operating Environment
For CSFB to GERAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be SAE1.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB to
GERAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-7.
NOTE
If the GERAN network uses Huawei equipment, activate the license for GBFD-511313 CSFB and turn on
the switch specified by the GCELLSOFT.SUPPORTCSFB parameter.
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the operator
l User-defined: parameter values set by users
Required Data
Before configuring CSFB to GERAN, collect the data related to neighbor relationships with
GERAN cells. This section provides only the information about MOs related to neighboring
GERAN cells. For more information about how to collect data for the parameters in these MOs,
see Mobility Management in Connected Mode Feature Parameter Description.
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 GERAN.
Handover ENodeBA Network Set this parameter based on the network plan.
Mode lgoSwitch plan l To activate PS handovers, select the
switch . (negotiation GeranPsHoSwitch(GeranPsHoSwitch)
HoModeS not required) check box. To activate CCO, select the
witch GeranCcoSwitch(GeranCcoSwitch) check
box. To activate NACC, select the
GeranNaccSwitch(GeranNaccSwitch)
check box.
If none of the preceding check boxes is
selected, redirection will be used for CSFB
to GERAN.
l 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.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set the blind-handover priorities of different RATs for CSFB.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the CSFB protection timer.
The following table describes the parameter that must be set in the InterRatHoComm MO to
set the maximum number of neighboring GERAN cells whose system information is sent to UEs
for emergency redirections.
Max Geran cell num InterRatHoComm. Network plan The default value is
in CSFB EMC GeranCellNumFor- (negotiation not 0, indicating that no
redirection EmcRedirect required) system information
of any neighboring
GERAN cells is sent
to UEs for
emergency
redirections.
Operators can set this
parameter to 0
through 32 based on
the network plan.
After the CSFB
protection timer
expires, the eNodeB
performs an
emergency
redirection. If the
signal quality of the
serving cell is poor
and this parameter is
set to a large value,
the eNodeB may fail
to send the system
information of
neighboring
GERAN cells to
UEs.
7.2.5 Precautions
None
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-8 in a summary data file, which also contains
other data for the new eNodeBs to be deployed. Then, import the summary data file into the
Configuration Management Express (CME) for batch configuration. For detailed instructions,
see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 7-8 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 7-8 are not contained in a scenario-specific summary data file. In this
situation, customize a summary data file to include the MOs before you can set the
parameters.
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-8 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-7, select the eNodeB to which the MOs belong.
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
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.
Step 4 (Optional) Run the MOD CSFALLBACKHO command to set the CSFB protection timer.
Step 5 (Optional) Run the MOD INTERRATHOCOMM command to set the maximum number of
neighboring GERAN cells whose system information is to be sent to UEs for emergency
redirections.
----End
Signaling Observation
The activation observation procedure is as follows:
Step 2 Enable the UE to camp on an 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 similar to that for CSFB to UTRAN
described in section 7.1.7 Activation Observation. The only difference is the target RAT.
----End
Counter Observation
Table 7-9 lists the performance counters for observing functions related to CSFB to GERAN.
7.2.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-10.
l The E-UTRAN and UTRAN support the RIM with SIB procedure.
l 3GPP Release 9 UEs are used on the live network.
l 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 UTRAN and E-UTRAN
cells cover the same area, or the UTRAN cell provides better coverage than the E-UTRAN cell,
use CSFB based on blind handover to decrease the CSFB delay.
NE Requirement
MME Supports:
l CSFB
l RIM procedures in compliance with
3GPP Release 9
SGSN Supports:
l CSFB
l RIM procedures in compliance with
3GPP Release 9
l Collect the following information about the UEs that support UMTS and LTE on the live
network:
Supported frequency bands
Whether the UEs support redirection from E-UTRAN to UTRAN
Whether the UEs support PS handover from E-UTRAN to UTRAN
Whether the UEs support UTRAN measurements
Whether the UEs comply with 3GPP Release 9 specifications
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.3.3 Requirements
Operating Environment
For flash CSFB to UTRAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be PS9.1 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support flash CSFB
to UTRAN.
License
The operator has purchased and activated the licenses for the features listed in Table 7-12.
NOTE
If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN.
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with
UTRAN cells. This section provides only the information about MOs related to neighboring
UTRAN cells and key parameters in these MOs. For more information about how to collect data
for the parameters in these MOs, see Mobility Management in Connected Mode Feature
Parameter Description.
Collect data for the parameters in the following MOs:
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 flash CSFB to UTRAN.
Handov ENodeBAlgoSw Network plan Set this parameter based on the network
er itch. (negotiation not plan.
Mode HoModeSwitch required) To activate blind handovers, select the
switch 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.
The following table describes the parameters that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
MME S1Interface. Network To active the multiple RIM, set the parameter
Release MmeRelease plan to Release_R9(Release 9).
(negotiation
not 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.
Highest CSFallBack Network Set this parameter based on the network plan.
priority BlindHoCfg. plan This parameter is set to UTRAN by default and
InterRat InterRatHig (negotiation specifies the high-priority RAT to be
hestPri not required) considered in blind handovers for CSFB. For
flash CSFB to UTRAN, retain the default
value.
Second CSFallBack Network Set this parameter based on the network plan.
priority BlindHoCfg. plan This parameter is set to GERAN by default and
InterRat InterRatSeco (negotiation specifies the second-highest-priority RAT to be
ndPri not required) considered in blind handovers for CSFB.
Ensure that this parameter is set to a different
value from the
CSFallBackBlindHoCfg.InterRatHighestPri
and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallBack Network Set this parameter based on the network plan.
priority BlindHoCfg. plan This parameter is set to CDMA2000 by default
InterRat InterRatLow (negotiation and specifies the low-priority RAT to be
estPri not required) considered in blind handovers for CSFB.
Ensure that this parameter is set to a different
value from the
CSFallBackBlindHoCfg.InterRatHighestPri
and
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
UTRAN CSFallBack Network Set this parameter based on the network plan.
LCS BlindHoCfg. plan This parameter specifies the LCS capability of
capability UtranLcsCap (negotiation the UTRAN.
not required)
The following table describes the parameter that must be set in the InterRatHoComm MO to
set the maximum number of neighboring UTRAN cells whose system information is sent to UEs
for flash redirections.
Max Utran cell num InterRatHoComm. Network plan Set this parameter
in redirection CellInfoMaxUtran- (negotiation not based on the network
CellNum required) plan. The default
value is 8. If this
parameter is set too
small, the flash
CSFB success rate
decreases because
UEs may not receive
valid neighboring
cell system
information. If this
parameter is set too
large, the size of an
RRC connection
release message
increases and CSFB
may fail.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to enable adaptive blind CSFB.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the RSRP threshold for event A1 associated with adaptive blind CSFB.
7.3.5 Precautions
None
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-13 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-8, select the eNodeB to which the MOs belong.
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
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.
Step 3 Run the MOD S1INTERFACE command to set the compliance protocol release of the MME.
Step 4 Run the MOD CSFALLBACKBLINDHOCFG command to set the blind-handover priorities
of different RATs for CSFB.
Step 5 Run the MOD INTERRATHOCOMM command to set the maximum number of neighboring
UTRAN cells whose system information is sent to UEs for flash redirections.
----End
To activate adaptive blind CSFB, perform the following steps:
Step 1 Run the MOD ENODEBALGOSWITCH command to turn on the blind handover switch and
adaptive blind CSFB switch.
Step 2 Run the MOD CSFALLBACKHO command to set the RSRP threshold for event A1 associated
with adaptive blind CSFB.
----End
Counter Observation
Table 7-14 lists the performance counters for observing functions related to flash CSFB to
UTRAN.
7.3.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-15.
To deactivate adaptive blind CSFB, run the MOD ENODEBALGOSWITCH command with
the CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlindHoSwitch) check box cleared under the
Handover Algo switch parameter.
l The E-UTRAN and GERAN support the RIM with SIB procedure.
l 3GPP Release 9 UEs are used on the live network.
l 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 GERAN and E-UTRAN
cells cover the same area, or the GERAN cell provides better coverage than the E-UTRAN cell,
use CSFB based on blind handover to decrease the CSFB delay.
NE Requirement
MME Supports:
l CSFB
l RIM procedures in compliance with 3GPP Release.
SGSN Supports:
l CSFB
l RIM procedures in compliance with 3GPP Release.
l Collect the following information about the UEs that support GSM and LTE on the live
network:
Supported frequency bands
Whether the UEs support redirection from E-UTRAN to GERAN
Whether the UEs support PS handover from E-UTRAN to GERAN
Whether the UEs support GERAN measurements
Whether the UEs comply with 3GPP Release 9 specifications
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.4.3 Requirements
Operating Environment
For flash CSFB to GERAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be PS8.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support flash CSFB
to GERAN.
License
The operator has purchased and activated the licenses for the features listed in Table 7-17.
NOTE
If the GERAN uses Huawei devices, evolved network assisted cell change (eNACC) between E-UTRAN
and GERAN for CSFB needs to be enabled on the GERAN.
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the operator
l User-defined: parameter values set by users
Required Data
Before configuring CSFB to GERAN, collect the data related to neighbor relationships with
GERAN cells. This section provides only the information about MOs related to neighboring
GERAN cells and key parameters in these MOs. For more information about how to collect data
for the parameters in these MOs, see Mobility Management in Connected Mode Feature
Parameter Description.
Collect data for the parameters in the following MOs:
l GeranNfreqGroup: used to configure GERAN carrier frequency groups.
l GeranNfreqGroupArfcn: used to configure ARFCNs in each GERAN carrier frequency
group.
l GeranExternalCell: used to configure external GERAN cells. If PS handover is used, the
GeranExternalCell.Rac parameter must be set.
l GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared external
GERAN cell. This MO is required only if the BTS that provides the external GERAN cell
works in RAN sharing with common carriers mode and multiple operators share the
external GERAN cell.
l 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.
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 flash CSFB to GERAN.
Hando ENodeBAlgoSwi Network plan Set this parameter based on the network
ver tch. (negotiation not plan.
Mode HoModeSwitch required) To activate blind handovers, select the
switch 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.
The following table describes the parameters that must be set in the S1Interface MO to set the
compliance protocol release of the MME.
MME S1Interface. Network To active the multiple RIM, set the parameter
Release MmeRelease plan to Release_R9(Release 9).
(negotiation
not 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.
CN CSFallBac Network plan Set this parameter based on the network plan.
Operator kBlindHoC (negotiation This parameter identifies the operator whose
ID fg. not required) RAT blind-handover priorities are to be set.
CnOperato
rId
Highest CSFallBac Network plan Set this parameter based on the network plan.
priority kBlindHoC (negotiation This parameter is set to UTRAN by default and
InterRat fg. not required) specifies the high-priority RAT to be considered
InterRatHi in blind handovers for CSFB. For flash CSFB to
ghestPri GERAN, set this parameter to GERAN.
Second CSFallBac Network plan Set this parameter based on the network plan.
priority kBlindHoC (negotiation This parameter is set to GERAN by default and
InterRat fg. not required) specifies the second-highest-priority RAT to be
InterRatSe considered in blind handovers for CSFB. Ensure
condPri that this parameter is set to a different value from
the CSFallBackBlindHoCfg.InterRatHighest-
Pri and
CSFallBackBlindHoCfg.InterRatLowestPri
parameters.
Lowest CSFallBac Network plan Set this parameter based on the network plan.
priority kBlindHoC (negotiation This parameter is set to CDMA2000 by default
InterRat fg. not required) and specifies the low-priority RAT to be
InterRatLo considered in blind handovers for CSFB. Ensure
westPri that this parameter is set to a different value from
the CSFallBackBlindHoCfg.InterRatHighest-
Pri and
CSFallBackBlindHoCfg.InterRatSecondPri
parameters.
GERAN CSFallBac Network plan Set this parameter based on the network plan.
LCS kBlindHoC (negotiation This parameter specifies the LCS capability of
capabilit fg. not required) the GERAN.
y GeranLcsC
ap
The following table describes the parameter that must be set in the InterRatHoComm MO to
set the maximum number of neighboring GERAN cells whose system information is sent to UEs
for flash redirections.
Max Geran cell num InterRatHoComm. Network plan Set this parameter
in redirection CellInfoMaxGeran- (negotiation not based on the network
CellNum required) plan. The default
value is 8.
If this parameter is
set too small, the
flash CSFB success
rate decreases
because UEs may not
receive valid
neighboring cell
system information.
If this parameter is
set too large, the size
of an RRC
connection release
message increases
and CSFB may fail.
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to enable adaptive blind CSFB.
The following table describes the parameter that must be set in the CSFallBackHo MO to set
the RSRP threshold for event A1 associated with adaptive blind CSFB.
7.4.5 Precautions
None
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-18 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-9, select the eNodeB to which the MOs belong.
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
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 S1INTERFACE command to set the compliance protocol release of the MME.
Step 4 Run the MOD CSFALLBACKBLINDHOCFG command to set the blind-handover priorities
of different RATs for CSFB.
Step 5 Run the MOD INTERRATHOCOMM command to set the maximum number of neighboring
GERAN cells whose system information is sent to UEs for flash redirections.
----End
Step 1 Run the MOD ENODEBALGOSWITCH command to turn on the blind handover switch and
adaptive blind CSFB switch.
Step 2 Run the MOD CSFALLBACKHO command to set the RSRP threshold for event A1 associated
with adaptive blind CSFB.
----End
Signaling Observation
Enable a UE to camp on an E-UTRAN cell and make a voice call. If the call continues and the
RRC Connection Release message traced on the Uu interface carries the information about
neighboring GERAN cells, flash CSFB to GERAN has been activated successfully.
The signaling procedure for flash CSFB to GERAN is similar to that for CSFB to UTRAN
described in section 7.1.7 Activation Observation. The difference is that the RRC Connection
Release message carries the information about neighboring GERAN cells. Figure 7-10 shows
the content of the RRC Connection Release message during flash CSFB to GERAN.
Figure 7-10 The RRC Connection Release message during flash CSFB to GERAN
Counter Observation
Observe the counter L.FlashCSFB.E2G, which indicates the number of procedures for flash
CSFB to GERAN. If the counter value is not 0, flash CSFB to GERAN has been activated.
7.4.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-19.
To deactivate adaptive blind CSFB, run the MOD ENODEBALGOSWITCH command with
the CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlindHoSwitch) check box cleared under the
Handover Algo switch parameter.
Use LOFD-001068 CS Fallback with LAI to UTRAN also when both of the following conditions
are met:
Table 7-20 Requirements of CSFB with LAI to UTRAN for core networks
NE Requirement
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach, combined EPS/IMSI detach,
and combined TAU/LAU
l CS signaling message routing
l SMS over SGs
l LAI delivery
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the SGs interface
l Collect the following information about the UEs that support UMTS and LTE on the live
network:
Supported frequency bands
Whether the UEs support redirection from E-UTRAN to UTRAN
Whether the UEs support PS handover from E-UTRAN to UTRAN
Whether the UEs support UTRAN measurements
This information is used to configure neighboring UTRAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Mobility
Management in Connected Mode Feature Parameter Description.
7.5.3 Requirements
Operating Environment
For CSFB with LAI to UTRAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be PS9.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB with
LAI to UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-21.
7.5.5 Precautions
None
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 make 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 7.1.7
Activation Observation The difference is that the Initial Context Setup Request message carries
the LAI that the MME delivers to the eNodeB.
----End
7.5.8 Deactivation
CSFB with LAI to UTRAN is automatically deactivated when its license or CSFB to UTRAN
is deactivated. For details about how to deactivate CSFB to UTRAN, see 7.1.8 Deactivation.
Use LOFD-001069 CS Fallback with LAI to GERAN also when both of the following conditions
are met:
Table 7-22 Requirements of CSFB with LAI to GERAN for core networks
NE Requirement
MME Supports:
l SGs interface to the MSC
l LAI selection based on the TAI of the
serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach, combined
EPS/IMSI detach, and combined TAU/
LAU
l CS signaling message routing
l SMS over SGs
l LAI delivery
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the
SGs interface
l Collect the following information about the UEs that support GSM and LTE on the live
network:
Supported frequency bands
Whether the UEs support redirection from E-UTRAN to GERAN
Whether the UEs support PS handover from E-UTRAN to GERAN
Whether the UEs support GERAN measurements
This information is used to configure neighboring GERAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Mobility
Management in Connected Mode Feature Parameter Description.
7.6.3 Requirements
Operating Environment
For this feature, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be PS9.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB with
LAI to GERAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-23.
7.6.5 Precautions
None
l The license for CSFB with LAI to GERAN has been activated.
l CSFB to GERAN has been activated. For details about how to activate CSFB to GERAN,
see 7.2.6 Initial Configuration.
Step 1 Configure two neighboring GERAN cells with different LAIs for an E-UTRAN cell, and enable
the MME to include only one of the two LAIs in the instructions that will be delivered to the
eNodeB in Step 3 and Step 4.
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 make 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 7.1.7
Activation Observation The difference is that the Initial Context Setup Request message carries
the LAI that the MME delivers to the eNodeB.
----End
7.6.8 Deactivation
CSFB with LAI to GERAN is automatically deactivated when its license or CSFB to GERAN
is deactivated. For details about how to deactivate CSFB to GERAN, see 7.2.8 Deactivation.
Collect the configurations and versions of E-UTRAN and UTRAN equipment to check whether
CSFB is supported.
7.7.3 Requirements
l If the core-network equipment is provided by Huawei, the version must be SAE1.2 or later.
l If the core-network equipment is provided by another vendor, ask the vendor whether the
equipment supports CS Fallback to UTRAN.
Table 7-24 License control item for E-UTRAN to UTRAN CS/PS Steering
Feature License Control Item Name
Generic Data
Generic data preparation for LOFD-001078 E-UTRAN to UTRAN CS/PS Steering is the same
as for LOFD-001033 CS Fallback to UTRAN. For details, see 7.1.4 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
enable E-UTRAN to UTRAN CS/PS Steering.
The following table describes the parameter that must be set in a UtranNFreq MO to set the
CS service priority for a UTRAN frequency.
7.7.5 Precautions
None
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-25 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
----End
Step 1 Verify that the UE supports CSFB and multiple UTRAN frequencies are available.
Step 2 Enable measurement-based and blind handover for E-UTRAN to UTRAN CS/PS Steering. Set
a high PS service priority for UTRAN frequency F1 and a high CS service priority for UTRAN
frequency F2.
Step 3 Have the UE camp on an LTE cell and initiate a voice call in the cell.
The expected result is that the UE falls back to the UTRAN cell operating on F2.
Step 4 Have the UE camp on the LTE cell and initiate PS services. Move the UE to the LTE cell edge.
The expected result is that the UE is handed over to the UTRAN cell operating on F1.
----End
7.7.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-26.
If the operator owns both UTRAN and GERAN, you can also activate LOFD-001089 CS
Fallback Steering to GERAN to improve the network efficiency.
7.8.3 Requirements
Operating Environment
For CSFB steering to UTRAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be SAE1.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB steering
to UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-27.
Required Data
Required data preparation for CSFB steering to UTRAN is the same as that for CSFB to UTRAN.
For details, see 7.1.4 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
enable CSFB steering to UTRAN.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.
The following table describes the parameter that must be set in the UtranNFreq MO to set the
CS service priority of a neighboring UTRAN frequency considered for RRC_IDLE UEs.
The following table describes the parameter that must be set in the UtranNFreq MO to set the
CS+PS combined service priority of a neighboring UTRAN frequency for RRC_CONNECTED
UEs.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO
to set the CSFB policy for RRC_CONNECTED UEs.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO
to set the CSFB policy for RRC_IDLE UEs.
7.8.5 Precautions
None
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-28 in a summary data file, which also contains
other data for the new eNodeBs to be deployed. Then, import the summary data file into the
Configuration Management Express (CME) for batch configuration. For detailed instructions,
see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 7-28 are contained in a scenario-specific summary
data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 7-28 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-28 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-12, select the eNodeB to which the MOs belong.
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
7.8.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-29.
7.9.3 Requirements
Operating Environment
For CSFB steering to GERAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be SAE1.2 or later.
l If the core-network equipment is provided by another vendor, check with the vendor
whether the equipment supports this feature. The core network must support CSFB steering
to GERAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-30.
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the operator
l User-defined: parameter values set by users
Required Data
Required data preparation for CSFB steering to GERAN is the same as that for CSFB to GERAN.
For details, see section 7.2.4 Data Preparation.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to
enable CSFB steering to GERAN.
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.
Highest CSFallBackBl Network Set this parameter based on the network plan.
priority indHoCfg. plan This parameter is set to UTRAN by default
InterRat InterRatHighe (negotiation and specifies the high-priority RAT to be
stPri not considered in blind handovers for CSFB. For
required) CSFB steering to GERAN, set this parameter
to GERAN.
Second CSFallBackBl Network Set this parameter based on the network plan.
priority indHoCfg. plan This parameter is set to GERAN by default
InterRat InterRatSecon (negotiation and specifies the second-highest-priority RAT
dPri not to be considered in blind handovers for CSFB.
required) Ensure that this parameter is set to a different
value from the
CSFallBackBlindHoCfg.InterRatHighest-
Pri and
CSFallBackBlindHoCfg.InterRatLowest-
Pri parameters.
Lowest CSFallBackBl Network Set this parameter based on the network plan.
priority indHoCfg. plan This parameter is set to CDMA2000 by
InterRat InterRatLowe (negotiation default and specifies the low-priority RAT to
stPri not be considered in blind handovers for CSFB.
required) Ensure that this parameter is set to a different
value from the
CSFallBackBlindHoCfg.InterRatHighest-
Pri and
CSFallBackBlindHoCfg.InterRatSecond-
Pri parameters.
GERAN CSFallBackBl Network Set this parameter based on the network plan.
LCS indHoCfg. plan This parameter specifies the LCS capability of
capability GeranLcsCap (negotiation the GERAN.
not
required)
The following table describes the parameters that must be set in the CSFallBackBlindHoCfg
MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.
CSFB CSFallB Network plan Set this parameter based on the network plan. This
Highest ackBlin (negotiation parameter is set to UTRAN by default and
priority dHoCfg. not required) specifies the high-priority RAT to be considered
InterRat for IdleCsfb in CSFB for UEs in idle mode. For CSFB steering
Idle UE Highest to GERAN, set this parameter to GERAN.
Pri
CSFB CSFallB Network plan Set this parameter based on the network plan. This
Second ackBlin (negotiation parameter is set to GERAN by default and
priority dHoCfg. not required) specifies the second-highest-priority RAT to be
InterRat for IdleCsfb considered in CSFB for UEs in idle mode. Ensure
Idle UE SecondP that this parameter is set to a different value from
ri the CSFallBackBlindHoCfg.IdleCsfbHighest-
Pri and CSFallBackBlind-
HoCfg.IdleCsfbLowestPri parameters.
CSFB CSFallB Network plan Set this parameter based on the network plan. This
Lowest ackBlin (negotiation parameter is set to CDMA2000 by default and
priority dHoCfg. not required) specifies the low-priority RAT to be considered in
InterRat for IdleCsfb CSFB for UEs in idle mode. Ensure that this
Idle UE LowestP parameter is set to a different value from the
ri CSFallBackBlindHoCfg.IdleCsfbHighestPri
and CSFallBackBlindHoCfg.IdleCsfbSecond-
Pri parameters.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO
to set the CSFB policy for RRC_CONNECTED UEs.
The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO
to set the CSFB policy for RRC_IDLE UEs.
7.9.5 Precautions
None
Step 1 Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch reconfiguration.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data
(M2000 client mode), or choose Advanced > Base Station Bulk Configuration > Export Data
(CME client mode), to export the eNodeB data stored on the CME into the customized summary
data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-31 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data
(M2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-13, select the eNodeB to which the MOs belong.
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
----End
Example
//To set GeranCsfbSteeringSwitch under the Handover Algo switch parameter
MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-1;
//To set RAT priorities for CSFB triggered for RRC_CONNECTED and RRC_IDLE UEs
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,
IdleCsfbHighestPri=UTRAN;
Step 1 Check that the UE supports redirection-based CSFB and handover-based CSFB.
Step 2 Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection and
handover, respectively.
Step 3 Enable the UE to initiate a voice call in idle mode and in connected mode.
Step 4 Observe the counters L.CSFB.E2G, L.RRCRedirection.E2G.CSFB, and
L.IRATHO.E2G.CSFB.ExecAttOut. If the values of the counters increase by 2, 1, and 1,
respectively, CSFB steering to GERAN has been activated.
----End
If CSFB steering to UTRAN has also been activated, the activation observation procedure is as
follows:
Step 1 Check that the UE supports CSFB to GERAN and CSFB to UTRAN.
Step 2 Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs and UTRAN
as the highest-priority RAT for CSFB triggered for RRC_CONNECTED UEs.
Step 3 Enable the UE to initiate a voice call in idle mode and in connected mode.
Step 4 Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase by 1, both
CSFB steering to UTRAN and CSFB steering to GERAN have been activated.
----End
7.9.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for Existing
eNodeBs. In the procedure, modify parameters according to Table 7-32.
NOTE
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.
Set blind-handover priorities of different RATs according to the operator policies. When the
handover success rate or service setup success rate is low because of 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.
The following table describes the parameter in the ENodeBAlgoSwitch MO used to activate or
deactivate blind handovers.
7.11 Troubleshooting
7.11.1 Fault 1
Fault Description
A UE performs cell reselection to an inter-RAT neighboring cell directly after initiating a voice
call in an E-UTRAN cell, and the S1 interface tracing result shows that CSFB is not triggered.
Fault Handling
Step 1 Create an S1 interface tracing task, use the UE to camp on the E-UTRAN cell again, and check
whether the value of the information element (IE) ePS-attach-type-value is "combined-attach"
in the traced Attach Request message.
l If so, go to Step 2.
l If not, replace the UE with one that supports combined EPS/IMSI attach, and try again.
Step 2 Check whether the traced Attach Accept message includes the IE cs-domain-not-available.
l If it does, go to Step 3.
l If not, contact Huawei technical support.
Step 3 Contact the vendors of core network NEs to ensure the following:
l Attach procedures to the CS domain are allowed according to the subscription data on the
HSS.
l The core network supports CSFB.
l The SGs interface is correctly configured.
----End
7.11.2 Fault 2
Fault Description
An eNodeB delivers an RRC Connection Reconfiguration message for measurement control to
a UE that has initiated a voice call in the LTE network, but the eNodeB does not receive a
measurement report.
Fault Handling
Step 1 Check whether the RRC Connection Reconfiguration message contains B1-related measurement
configurations and whether the information about the inter-RAT systems in the configuration is
correct.
l If it is, go to Step 3.
l If not, rectify the faults and try again.
Step 2 Check whether the coverage of the inter-RAT neighboring cell is satisfactory. If the coverage
is unsatisfactory, adjust B1-related parameters or use CSFB based on blind handovers.
Step 3 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 according to the operator
policies, instead of triggering a blind handover for CSFB, an eNodeB delivers an inter-RAT
measurement configuration to a UE that has initiated a voice call.
Fault Handling
Step 1 Run the LST ENODEBALGOSWITCH command and check the setting of BlindHoSwitch
under the Handover Mode Switch parameter. If BlindHoSwitch is Off, run the MOD
ENODEBALGOSWITCH command with the BlindHoSwitch(BlindHoSwitch) check box
under the Handover Mode Switch parameter selected. In addition, check the CSFB mechanism
and perform the following:
l If CSFB to UTRAN is required, go to Step 2.
l If CSFB to GERAN is required, go to Step 3.
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.
l If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case,
run the MOD UTRANNCELL command with the Blind handover priority parameter set
to a value other than 0.
l If Blind handover priority is not 0, contact Huawei technical support.
Step 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.
l If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case,
run the MOD GERANNCELL command with the Blind handover priority parameter set
to a value other than 0.
l If Blind handover priority is not 0, contact Huawei technical support.
----End
8 Parameters
handover to
GERAN
handover to
GERAN
handover to
GERAN
UTRAN
frequency with
the highest CS
+PS combined
service priority
is selected by
default.When
this parameter is
set to Priority_0
for a UTRAN
frequency, the
UTRAN
frequency is not
included in CS
+PS combined
service priority
arrangement.
GUI Value
Range:Priority_
0(Priority 0),
Priority_1
(Priority 1),
Priority_2
(Priority 2),
Priority_3
(Priority 3),
Priority_4
(Priority 4),
Priority_5
(Priority 5),
Priority_6
(Priority 6),
Priority_7
(Priority 7),
Priority_8
(Priority 8),
Priority_9
(Priority 9),
Priority_10
(Priority 10),
Priority_11
(Priority 11),
Priority_12
(Priority 12),
Priority_13
(Priority 13),
Priority_14
(Priority 14),
Priority_15
(Priority 15),
Priority_16
(Priority 16)
Unit:None
Actual Value
Range:Priority_
0, Priority_1,
Priority_2,
Priority_3,
Priority_4,
Priority_5,
Priority_6,
Priority_7,
Priority_8,
Priority_9,
Priority_10,
Priority_11,
Priority_12,
Priority_13,
Priority_14,
Priority_15,
Priority_16
Default
Value:Priority_
2(Priority 2)
,
UtranCsfbSteer-
ingSwitch
(UtranCsfbSteer
ingSwitch),
GeranCsfbSteer
ingSwitch
(GeranCsfbStee
ringSwitch),
CSFBLoadInfo
Switch
(CSFBLoadInfo
Switch),
Cdma1XrttEcsf
bSwitch
(Cdma1XrttEcsf
bSwitch),
EmcBlindHoA1
Switch
(EmcBlindHoA
1Switch),
EmcInterFreq-
BlindHoSwitch
(EmcInterFreq-
BlindHoSwitch)
Unit:None
Actual Value
Range:IntraFreq
CoverHoSwitch
,
InterFreqCover-
HoSwitch,
UtranCsfbSwitc
h,
GeranCsfbSwitc
h,
Cdma1xRttCsfb
Switch,
UtranServiceHo
Switch,
GeranServiceH
oSwitch,
CdmaHrpdServi
ceHoSwitch,
Cdma1xRttServ
iceHoSwitch,
UlQualityInter-
RATHoSwitch,
InterPlmnHoS-
witch,
UtranFlashCsfb
Switch,
GeranFlashCsfb
Switch,
ServiceBasedIn-
terFreqHoSwitc
h,
UlQualityInter-
FreqHoSwitch,
CsfbAdaptive-
BlindHoSwitch,
UtranCsfbSteer-
ingSwitch,
GeranCsfbSteer
ingSwitch,
CSFBLoadInfo
Switch,
Cdma1XrttEcsf
bSwitch,
EmcBlindHoA1
Switch,
EmcInterFreq-
BlindHoSwitch
Default
Value:IntraFreq
CoverHoSwitch
:On,
InterFreqCover
HoSwitch:On,
UtranCsfbSwitc
h:Off,
GeranCsfbSwitc
h:Off,
Cdma20001xRtt
CsfbSwitch:Off,
UtranServiceHo
Switch:Off,
GeranServiceH
oSwitch:Off,
Cdma2000Hrpd
ServiceHoSwitc
h:Off,
Cdma20001xRtt
ServiceHoSwitc
h:Off,
UlQualityInterR
ATHoSwitch:O
ff,
requests event-
driven multiple
reports from
GERAN cells. If
this switch is
turned on, the
eNodeB can
send RAN-
INFORMATIO
N-REQUEST
PDUs to
CERAN cells to
request multiple
event-driven
reports. If this
switch is turned
off, the eNodeB
cannot send
RAN-
INFORMATIO
N-REQUEST
PDUs to
GERAN cells to
request multiple
event-driven
reports.
GUI Value
Range:UTRAN
_RIM_SWITC
H(UTRAN RIM
Switch),
GERAN_RIM_
SWITCH
(GERAN RIM
Switch)
Unit:None
Actual Value
Range:UTRAN
_RIM_SWITC
H,
GERAN_RIM_
SWITCH
Default
Value:UTRAN
RIM
Switch:Off,
GERAN RIM
Switch:Off
Switch),
GeranVoipCapS
witch
(GeranVoipCap
Switch),
Cdma1xRttVoip
CapSwitch
(Cdma1xRttVoi
pCapSwitch),
UtranPsHoSwit
ch
(UtranPsHoSwit
ch),
GeranPsHoSwit
ch
(GeranPsHoSwi
tch),
CdmaHrpdNon
OtpimisedHoS-
witch
(CdmaHrpdNon
OtpimisedHoS-
witch),
CdmaHrpdOpti
misedHoSwitch
(CdmaHrpdOpti
misedHoSwitch
),
GeranNaccSwit
ch
(GeranNaccSwi
tch),
GeranCcoSwitc
h
(GeranCcoSwit
ch),
UtranSrvccSwit
ch
(UtranSrvccS-
witch),
GeranSrvccSwit
ch
(GeranSrvccS-
witch),
Cdma1xRttSrvc
cSwitch
(Cdma1xRttSrv
ccSwitch),
UtranRedirectS-
witch
(UtranRedirectS
witch),
GeranRedirectS
witch
(GeranRedirect
Switch),
CdmaHrpdRedi
rectSwitch
(CdmaHrpdRed
irectSwitch),
Cdma1xRttRedi
rectSwitch
(Cdma1xRttRed
irectSwitch),
BlindHoSwitch
(BlindHoSwitch
),
LcsSrvccSwitch
(LcsSrvccSwitc
h),
AutoGapSwitch
(AutoGapSwitc
h)
Unit:None
Actual Value
Range:Eutran-
VoipCapSwitch
,
UtranVoipCapS
witch,
GeranVoipCapS
witch,
Cdma1xRttVoip
CapSwitch,
UtranPsHoSwit
ch,
GeranPsHoSwit
ch,
CdmaHrpdNon
OtpimisedHoS-
witch,
CdmaHrpdOpti
misedHoSwitch
,
GeranNaccSwit
ch,
GeranCcoSwitc
h,
UtranSrvccSwit
ch,
GeranSrvccSwit
ch,
Cdma1xRttSrvc
cSwitch,
UtranRedirectS-
witch,
GeranRedirectS
witch,
CdmaHrpdRedi
rectSwitch,
Cdma1xRttRedi
rectSwitch,
BlindHoSwitch,
LcsSrvccSwitch
,
AutoGapSwitch
Default
Value:EutranVo
ipCapSwitch:O
n,
UtranVoipCapS
witch:Off,
GeranVoipCapS
witch:Off,
Cdma1xRttVoip
CapSwitch:Off,
UtranPsHoSwit
ch:Off,
GeranPsHoSwit
ch:Off,
CdmaHrpdNon
OtpimisedHoS
witch:Off,
CdmaHrpdOpti
misedHoSwitch
:Off,
GeranNaccSwit
ch:Off,
GeranCcoSwitc
h:Off,
UtranSrvccSwit
ch:Off,
GeranSrvccSwit
ch:Off,
Cdma1xRttSrvc
cSwitch:Off,
UtranRedirectS
witch:Off,
GeranRedirectS
witch:Off,
CdmaHrpdRedi
rectSwitch:Off,
Cdma1xRttRedi
rectSwitch:Off,
BlindHoSwitch:
Off,
LcsSrvccSwitch
:Off,
AutoGapSwitch
:Off
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
thus helps
prevent
unnecessary
handovers. For
details, see
3GPP TS
36.331.
GUI Value
Range:0ms,
40ms, 64ms,
80ms, 100ms,
128ms, 160ms,
256ms, 320ms,
480ms, 512ms,
640ms, 1024ms,
1280ms,
2560ms,
5120ms
Unit:ms
Actual Value
Range:0ms,
40ms, 64ms,
80ms, 100ms,
128ms, 160ms,
256ms, 320ms,
480ms, 512ms,
640ms, 1024ms,
1280ms,
2560ms,
5120ms
Default Value:
40ms
thus helps
prevent
unnecessary
handovers. For
details, see
3GPP TS
36.331.
GUI Value
Range:0ms,
40ms, 64ms,
80ms, 100ms,
128ms, 160ms,
256ms, 320ms,
480ms, 512ms,
640ms, 1024ms,
1280ms,
2560ms,
5120ms
Unit:ms
Actual Value
Range:0ms,
40ms, 64ms,
80ms, 100ms,
128ms, 160ms,
256ms, 320ms,
480ms, 512ms,
640ms, 1024ms,
1280ms,
2560ms,
5120ms
Default Value:
40ms
ch is turned on,
the UTRAN
SRVCC
hierarchy-based
measurement
algorithm takes
effect for
SRVCC-
triggered
handovers from
EUTRAN to
UTRAN.
GUI Value
Range:UtranFre
qLayerMeasSwi
tch
(UtranFreqLaye
rMeasSwitch),
UtranFreqLayer
BlindSwitch
(UtranFreqLaye
rBlindSwitch),
UtranSrvccSteer
ingSwitch
(UtranSrvcc-
SteeringSwitch)
Unit:None
Actual Value
Range:UtranFre
qLayerMeasSwi
tch,
UtranFreqLayer
BlindSwitch,
UtranSrvccSteer
ingSwitch
Default
Value:UtranFre
qLayerMeasSwi
tch:Off,
UtranFreqLayer
BlindSwitch:Of
f,
UtranSrvccSteer
ingSwitch:Off
set to Priority_0
for a UTRAN
frequency, the
UTRAN
frequency is not
included in CS
service priority
arrangement.
GUI Value
Range:Priority_
0(Priority 0),
Priority_1
(Priority 1),
Priority_2
(Priority 2),
Priority_3
(Priority 3),
Priority_4
(Priority 4),
Priority_5
(Priority 5),
Priority_6
(Priority 6),
Priority_7
(Priority 7),
Priority_8
(Priority 8),
Priority_9
(Priority 9),
Priority_10
(Priority 10),
Priority_11
(Priority 11),
Priority_12
(Priority 12),
Priority_13
(Priority 13),
Priority_14
(Priority 14),
Priority_15
(Priority 15),
Priority_16
(Priority 16)
Unit:None
Actual Value
Range:Priority_
0, Priority_1,
Priority_2,
Priority_3,
Priority_4,
Priority_5,
Priority_6,
Priority_7,
Priority_8,
Priority_9,
Priority_10,
Priority_11,
Priority_12,
Priority_13,
Priority_14,
Priority_15,
Priority_16
Default
Value:Priority_
2(Priority 2)
Actual Value
Range:0~8
Default Value:0
Default
Value:Release_
R8(Release 8)
handovers, and
hence helps
prevent
unnecessary
handovers. For
details, see
3GPP TS
36.331.
GUI Value
Range:0ms,
40ms, 64ms,
80ms, 100ms,
128ms, 160ms,
256ms, 320ms,
480ms, 512ms,
640ms, 1024ms,
1280ms,
2560ms,
5120ms
Unit:ms
Actual Value
Range:0ms,
40ms, 64ms,
80ms, 100ms,
128ms, 160ms,
256ms, 320ms,
480ms, 512ms,
640ms, 1024ms,
1280ms,
2560ms,
5120ms
Default Value:
40ms
9 Counters
10 Glossary
11 Reference Documents
1. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC); Stage 2"
2. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"
3. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
4. 3GPP TS 36.300, "E-UTRAN Overall description"
5. 3GPP TS 48.018, "General Packet Radio Service (GPRS); Base Station System (BSS)-
Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)"
6. VoLGA Forum Specifications
7. Idle Mode Management Feature Parameter Description
8. Mobility Management in Connected Mode Feature Parameter Description
9. eNodeB Initial Configuration Guide
10. eNodeB MO Reference
11. eNodeB Performance Counter Reference
12. eNodeB Reconfiguration Guide