CS Fallback (ERAN17.1 03)

eRAN
CS Fallback Feature Parameter

Description
Issue 03
Date 2021-06-26
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. i

eRAN
CS Fallback Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN17.1 03 (2021-06-26)..................................................................................................................................................1
1.2 eRAN17.1 02 (2021-04-30)..................................................................................................................................................1
1.3 eRAN17.1 01 (2021-03-05)..................................................................................................................................................1
1.4 eRAN17.1 Draft A (2020-12-29)........................................................................................................................................ 2
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 3
2.3 Features in This Document.................................................................................................................................................. 3
3 General Principles....................................................................................................................5
4 CSFB to UTRAN........................................................................................................................ 7
4.1 Principles.................................................................................................................................................................................... 7
4.1.1 Blind/Measurement-based Handling Selection......................................................................................................... 8
4.1.2 CSFB Policy Selection....................................................................................................................................................... 11
4.1.3 Target Cell/Frequency Selection................................................................................................................................... 14
4.1.4 Decision................................................................................................................................................................................. 20
4.1.5 Execution.............................................................................................................................................................................. 23
4.1.6 Load-based CSFB to UTRAN.......................................................................................................................................... 25
4.2 Network Analysis.................................................................................................................................................................. 26
4.2.1 Benefits................................................................................................................................................................................. 26
4.2.2 Impacts.................................................................................................................................................................................. 26
4.3 Requirements......................................................................................................................................................................... 27
4.3.1 Licenses................................................................................................................................................................................. 27
4.3.2 Software................................................................................................................................................................................27
4.3.3 Hardware.............................................................................................................................................................................. 28
4.3.4 Others.................................................................................................................................................................................... 28
4.4 Operation and Maintenance............................................................................................................................................. 29
4.4.1 Data Configuration (FDD).............................................................................................................................................. 29
4.4.1.1 Data Preparation............................................................................................................................................................ 29
4.4.1.2 Using MML Commands............................................................................................................................................... 34
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 36
4.4.2 Activation Verification..................................................................................................................................................... 36
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
4.4.3 Network Monitoring......................................................................................................................................................... 40
5 CSFB to GERAN...................................................................................................................... 43
5.1 Principles.................................................................................................................................................................................. 43
5.1.1 Blind/Measurement-based Handling Selection.......................................................................................................44
5.1.4 Decision................................................................................................................................................................................. 52
5.1.5 Execution.............................................................................................................................................................................. 52
5.2.1 Benefits................................................................................................................................................................................. 52
5.2.2 Impacts.................................................................................................................................................................................. 53
5.3 Requirements......................................................................................................................................................................... 53
5.3.1 Licenses................................................................................................................................................................................. 53
5.3.2 Software................................................................................................................................................................................54
5.3.3 Hardware.............................................................................................................................................................................. 54
5.3.4 Others.................................................................................................................................................................................... 54
5.4.1 Data Configuration........................................................................................................................................................... 54
6 Flash CSFB to UTRAN........................................................................................................... 65

6.1 Principles.................................................................................................................................................................................. 65
6.1.2 Decision................................................................................................................................................................................. 67
6.2.1 Benefits................................................................................................................................................................................. 68
6.2.2 Impacts.................................................................................................................................................................................. 68
6.3 Requirements......................................................................................................................................................................... 68
6.3.1 Licenses................................................................................................................................................................................. 68
6.3.2 Software................................................................................................................................................................................69
6.3.3 Hardware.............................................................................................................................................................................. 69
6.3.4 Others.................................................................................................................................................................................... 69
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
7 Flash CSFB to GERAN........................................................................................................... 73

7.1 Principles.................................................................................................................................................................................. 73
7.1.2 Decision................................................................................................................................................................................. 75
7.2.1 Benefits................................................................................................................................................................................. 76
7.2.2 Impacts.................................................................................................................................................................................. 76
7.3 Requirements......................................................................................................................................................................... 76
7.3.1 Licenses................................................................................................................................................................................. 76
7.3.2 Software................................................................................................................................................................................76
7.3.3 Hardware.............................................................................................................................................................................. 77
7.3.4 Others.................................................................................................................................................................................... 77
8 Ultra-Flash CSFB to UTRAN................................................................................................ 81

8.1 Principles.................................................................................................................................................................................. 81
8.2.1 Benefits................................................................................................................................................................................. 83
8.2.2 Impacts.................................................................................................................................................................................. 83
8.3 Requirements......................................................................................................................................................................... 83
8.3.1 Licenses................................................................................................................................................................................. 83
8.3.2 Software................................................................................................................................................................................84
8.3.3 Hardware.............................................................................................................................................................................. 84
8.3.4 Others.................................................................................................................................................................................... 84
8.4.1 Data Configuration (FDD).............................................................................................................................................. 84
9 Ultra-Flash CSFB to GERAN.................................................................................................89

9.1 Principles.................................................................................................................................................................................. 89
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
9.1.3 Execution.............................................................................................................................................................................. 91
9.2.1 Benefits................................................................................................................................................................................. 92
9.2.2 Impacts.................................................................................................................................................................................. 92
9.3 Requirements......................................................................................................................................................................... 92
9.3.1 Licenses................................................................................................................................................................................. 92
9.3.2 Software................................................................................................................................................................................92
9.3.3 Hardware.............................................................................................................................................................................. 93
9.3.4 Others.................................................................................................................................................................................... 93
10 CSFB Steering to UTRAN................................................................................................... 99

10.1 Principles............................................................................................................................................................................... 99
10.2 Network Analysis............................................................................................................................................................. 101
10.2.1 Benefits.............................................................................................................................................................................101
10.2.2 Impacts............................................................................................................................................................................. 101
10.3 Requirements..................................................................................................................................................................... 101
10.3.1 Licenses............................................................................................................................................................................ 101
10.3.2 Software........................................................................................................................................................................... 102
10.3.3 Hardware......................................................................................................................................................................... 102
10.3.4 Others............................................................................................................................................................................... 102
10.4 Operation and Maintenance........................................................................................................................................ 103
10.4.1 Data Configuration...................................................................................................................................................... 103
10.4.1.1 Data Preparation....................................................................................................................................................... 103
10.4.1.2 Using MML Commands.......................................................................................................................................... 106
10.4.1.3 Using the MAE-Deployment..................................................................................................................................106
10.4.2 Activation Verification.................................................................................................................................................107
10.4.3 Network Monitoring.................................................................................................................................................... 107
11 CSFB Steering to GERAN................................................................................................. 108

11.1 Principles............................................................................................................................................................................. 108
11.2.1 Benefits.............................................................................................................................................................................108
11.2.2 Impacts............................................................................................................................................................................. 108
11.3 Requirements..................................................................................................................................................................... 108
11.3.1 Licenses............................................................................................................................................................................ 109
11.3.2 Software........................................................................................................................................................................... 109
11.3.3 Hardware......................................................................................................................................................................... 109
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. v

eRAN
11.3.4 Others............................................................................................................................................................................... 109

12 Coverage-based E-UTRAN to UTRAN CS/PS Steering.............................................. 113

12.1 Principles............................................................................................................................................................................. 113
12.2.1 Benefits.............................................................................................................................................................................114
12.2.2 Impacts............................................................................................................................................................................. 114
12.3 Requirements..................................................................................................................................................................... 115
12.3.1 Licenses............................................................................................................................................................................ 115
12.3.2 Software........................................................................................................................................................................... 115
12.3.3 Hardware......................................................................................................................................................................... 115
12.3.4 Others............................................................................................................................................................................... 115
13 CSFB with LAI to UTRAN................................................................................................. 118

13.1 Principles............................................................................................................................................................................. 118
13.2.1 Benefits.............................................................................................................................................................................120
13.2.2 Impacts............................................................................................................................................................................. 120
13.3 Requirements..................................................................................................................................................................... 120
13.3.1 Licenses............................................................................................................................................................................ 120
13.3.2 Software........................................................................................................................................................................... 120
13.3.3 Hardware......................................................................................................................................................................... 120
13.3.4 Others............................................................................................................................................................................... 121
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
14 CSFB with LAI to GERAN................................................................................................. 124

14.1 Principles............................................................................................................................................................................. 124
14.2.1 Benefits.............................................................................................................................................................................124
14.2.2 Impacts............................................................................................................................................................................. 124
14.3 Requirements..................................................................................................................................................................... 125
14.3.1 Licenses............................................................................................................................................................................ 125
14.3.2 Software........................................................................................................................................................................... 125
14.3.3 Hardware......................................................................................................................................................................... 125
14.3.4 Others............................................................................................................................................................................... 125
15 Parameters......................................................................................................................... 128
16 Counters.............................................................................................................................. 129
17 Glossary............................................................................................................................... 130
18 Reference Documents...................................................................................................... 131
19 Appendix............................................................................................................................. 132
19.1 CSFB to UTRAN................................................................................................................................................................. 132
19.1.1 Combined EPS/IMSI Attach Procedure.................................................................................................................. 132
19.1.2 CSFB Based on PS Handover.................................................................................................................................... 133
19.1.3 CSFB Based on Redirection........................................................................................................................................135
19.1.4 Flash CSFB....................................................................................................................................................................... 137
19.1.5 Ultra-Flash CSFB to UTRAN...................................................................................................................................... 138
19.1.6 Redirection-based CSFB Optimization for UEs in Idle Mode.........................................................................141
19.1.7 Signaling Procedures for SMS.................................................................................................................................. 142
19.1.8 Emergency Call.............................................................................................................................................................. 142
19.1.9 CSFB for LCS................................................................................................................................................................... 142
19.2 CSFB to GERAN................................................................................................................................................................. 143
19.2.1 Combined EPS/IMSI Attach Procedure.................................................................................................................. 143
19.2.2 CSFB Based on PS Handover.................................................................................................................................... 143
19.2.3 CSFB Based on CCO/NACC........................................................................................................................................ 144
19.2.4 CSFB Based on Redirection........................................................................................................................................146
19.2.5 Flash CSFB....................................................................................................................................................................... 147
19.2.6 Ultra-Flash CSFB to GERAN...................................................................................................................................... 149
19.2.7 Signaling Procedures for SMS.................................................................................................................................. 151
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. vii

eRAN
19.2.8 Emergency Call.............................................................................................................................................................. 151

19.2.9 CSFB for LCS................................................................................................................................................................... 151
Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
CS Fallback Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN17.1 03 (2021-06-26)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.2 eRAN17.1 02 (2021-04-30)

Technical Changes
None
Editorial Changes
1.3 eRAN17.1 01 (2021-03-05)

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
CS Fallback Feature Parameter Description 1 Change History
Technical Changes
None
Editorial Changes
1.4 eRAN17.1 Draft A (2020-12-29)

This issue introduces the following changes to eRAN16.1 01 (2020-03-30).
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Canceled the None FDD BTS3911E

compatibility with the
BTS3911E as of this
version.
Editorial Changes

eRAN
CS Fallback Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
2.2 Applicable RAT

This document applies to FDD.
2.3 Features in This Document

This document describes the following FDD features.

eRAN
CS Fallback Feature Parameter Description 2 About This Document
Feature ID Feature Name Chapter/Section
LOFD-001033 CS Fallback to UTRAN 4 CSFB to UTRAN
LOFD-001034 CS Fallback to GERAN 5 CSFB to GERAN
LOFD-001052 Flash CS Fallback to 6 Flash CSFB to UTRAN

UTRAN
LOFD-001053 Flash CS Fallback to 7 Flash CSFB to GERAN

GERAN
LOFD-070202 Ultra-Flash CSFB to 8 Ultra-Flash CSFB to UTRAN

UTRAN
LOFD-081283 Ultra-Flash CSFB to 9 Ultra-Flash CSFB to GERAN

GERAN
LOFD-001088 CS Fallback Steering to 10 CSFB Steering to UTRAN

UTRAN
LOFD-001089 CS Fallback Steering to 11 CSFB Steering to GERAN

GERAN
LOFD-001078 E-UTRAN to UTRAN 12 Coverage-based E-UTRAN to

CS/PS Steering UTRAN CS/PS Steering
LOFD-001068 CS Fallback with LAI to 13 CSFB with LAI to UTRAN

UTRAN
LOFD-001069 CS Fallback with LAI to 14 CSFB with LAI to GERAN

GERAN

eRAN
CS Fallback Feature Parameter Description 3 General Principles
3 General Principles
Overview
Circuit switched fallback (CSFB) and voice over Long Term Evolution (VoLTE) are
the two standard solutions for providing voice services to UEs on LTE networks.
Considering the technological maturity, industry chains, and deployment costs,
CSFB is preferred as an interim solution for voice service access before commercial
use of the IP multimedia subsystem (IMS) matures. CSFB allows for more efficient
use of legacy CS networks.
With the CSFB solution, when a UE initiates a CS service, such as a voice service,
short message service (SMS), location service (LCS), or emergency call, the
mobility management entity (MME) instructs the UE to fall back to a legacy CS
network before the UE accesses the service. CSFB is a session setup procedure, in
which the UE falls back to the CS network before the CS session is set up and
stays on the CS network during the CS session. For details, see 3GPP TS 23.272
V8.5.0.
Applicable Scenarios
CSFB can be used when the coverage area of the UTRAN/GERAN is at least as
large as that of the evolved universal terrestrial radio access network (E-UTRAN).
All mobile switching centers (MSCs) whose served areas overlap E-UTRAN
coverage must be upgraded to support the SGs interfaces between the MSCs and
the MMEs. After the upgrade, the MSCs can provide CSFB-related functions
including combined attach, combined tracking area update/location area update
(TAU/LAU), paging, and SMS. If the live network uses an MSC pool, only one or
several of the MSCs in the MSC pool need to be upgraded to support the SGs
interface.

eRAN
CS Fallback Feature Parameter Description 3 General Principles
Figure 3-1 Network architecture for CSFB

eRAN
CS Fallback Feature Parameter Description 4 CSFB to UTRAN
4 CSFB to UTRAN
4.1 Principles
This function is controlled by the UtranCsfbSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter. Figure 4-1 shows the procedure for
CSFB to UTRAN.

eRAN
Figure 4-1 CSFB procedure
The CSFB procedure is described in detail in the following sections:

● 4.1.1 Blind/Measurement-based Handling Selection
● 4.1.2 CSFB Policy Selection
● 4.1.3 Target Cell/Frequency Selection
● 4.1.4 Decision
● 4.1.5 Execution
An enhancement to CSFB to UTRAN is described in 4.1.6 Load-based CSFB to

UTRAN.
4.1.1 Blind/Measurement-based Handling Selection

After the eNodeB receives a CS Fallback Indicator, it selects either blind or
measurement-based handling. Figure 4-2 illustrates how this selection is
performed. If UTRAN and E-UTRAN cells cover the same area, or if the UTRAN cell
covers a larger area than the E-UTRAN cell, blind handling is recommended
because the CSFB delay is shorter.

eRAN
Figure 4-2 Blind/Measurement-based handling selection
The eNodeB- and cell-level blind handover switches described in Figure 4-2 are:
● The BlindHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch
parameter.
● The BlindHoSwitch option of the CellHoParaCfg.HoModeSwitch parameter.
Measurement-based Handling
The measurement configuration for measurement-based handling is the same as
that for coverage-based handovers from E-UTRAN to UTRAN. For details, see
Mobility Management in Connected Mode.
CSFB to UTRAN uses the same set of event-B1-related parameters as the
coverage-based inter-RAT handovers except the threshold and time-to-trigger for
event B1, which are described in Table 4-1.
Table 4-1 Parameters related to event B1 for CSFB to UTRAN
Parameter Name Parameter ID Parameter Description
CSFB UTRAN EventB1 CSFallBackHo.CsfbH The

RSCP Trigger oUtranB1ThdRscp InterRatHoComm.InterRatHo
Threshold UtranB1MeasQuan parameter
determines which threshold to
use.

eRAN
Parameter Name Parameter ID Parameter Description
CSFB UTRAN EventB1 CSFallBackHo.CsfbH

ECN0 Trigger oUtranB1ThdEcn0
Threshold
CSFB Utran EventB1 CSFallBackHo.CsfbH None

Time To Trig oUtranTimeToTrig
Blind Handling
After selecting blind handling, the eNodeB can choose whether to use adaptive
blind handling for CSFB. The CsfbAdaptiveBlindHoSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter specifies whether to enable
adaptive blind handling. This function does not take effect when optimization of
redirection-based CSFB for RRC_IDLE UEs is enabled. The optimization is controlled
by the IdleCsfbRedirectOptSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter. For details about this optimization
function, see 4.1.2 CSFB Policy Selection.
If E-UTRAN and UTRAN base stations are co-sited and the E-UTRAN coverage area
is larger than the UTRAN coverage area, the eNodeB uses adaptive blind handling
to estimate the signal strength of the neighboring UTRAN cells based on the
signal strength of the serving E-UTRAN cell. The procedure is shown in Figure 4-3.

eRAN
Figure 4-3 Adaptive blind handling for CSFB
The threshold for event A1 is specified by the CSFallBackHo.BlindHoA1ThdRsrp

parameter. The event-A1-related mechanisms are the same as those for coverage-
based handovers from E-UTRAN to UTRAN. For details, see Mobility Management
in Connected Mode.
4.1.2 CSFB Policy Selection

There are two policies for CSFB from E-UTRAN to UTRAN: PS handover and
redirection. PS handover takes priority over redirection. Figure 4-4 shows how the
policy is selected. This section assumes that neighboring frequencies and cells
have been configured appropriately.

eRAN
Figure 4-4 EUTRAN-to-UTRAN CSFB policy selection procedure
Figure 4-4 involves the following parameters:

● The CSFallBackHo.CsfbProtectTimer parameter specifies the CSFB protection
timer. If the UE fallback has not been completed by the time this timer
expires, the eNodeB takes protection measures, as described in 4.1.5
Execution.

eRAN
● If the function described in 6 Flash CSFB to UTRAN is enabled, the

InterRatHoComm.UtranCellNumForEmcRedirect parameter must be
specified.
● For parameters related to blind handling selection and adaptive blind
handling, see 4.1.1 Blind/Measurement-based Handling Selection.
● The CellHoParaCfg.HoModeSwitch parameter specifies the handover mode
switch.
For FDD, if operators have their own network capabilities for PS handover in
RAN sharing scenarios, the Separate Mobility Policies to UTRAN for Multi
PLMN function can be enabled to specify whether to select PS handover for a
particular operator. For details on how to activate this function, see Mobility
Management in Connected Mode.
– The Separate Mobility Policies to UTRAN for Multi PLMN function is
controlled by the UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.
– The PS handover capability of an operator for Separate Mobility Policies
to UTRAN for Multi PLMN is specified by the UtranNetworkCapCfg.Mcc,
UtranNetworkCapCfg.Mnc, and UtranNetworkCapCfg.RncId
parameters and the PsHoCapCfg option of the
UtranNetworkCapCfg.NetworkCapCfg parameter. If the capability is not
configured for a given operator or RNC, PS handover is supported by
default.
● The CSFB policy is determined by different parameters, depending on whether
the function described in 10 CSFB Steering to UTRAN is enabled.
– If the function is enabled, the parameter for specifying the CSFB policy
depends on the UE status:
▪ The CSFB policy for RRC_IDLE UEs is specified by the

CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.
▪ The CSFB policy for RRC_CONNECTED UEs is specified by the

CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.
– If the function is disabled, the CSFB policy is specified by the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether
UEs are in idle or connected mode.
NOTE
If the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter is set to PS_HO, the

UtranPsHoSwitch option of the CellHoParaCfg.HoModeSwitch parameter must
be selected for CSFB to UTRAN to take effect.
If neither the REDIRECTION nor PS_HO option of these CSFB-policy-related
parameters is selected and measurement-based handling is used, the eNodeB
does not apply any CSFB policy to a UE until the CSFB protection timer
expires. Upon the expiration, the eNodeB performs a blind redirection. If blind
handling is used, the eNodeB directly performs a blind redirection for CSFB.
During a blind PS handover for CSFB, if the preparation for the handover to the
cell with the highest blind-handover priority fails, the eNodeB tries the cell with
the second-highest blind-handover priority. The eNodeB can try a maximum of
eight cells. If the preparation for the handover to last cell still fails, the eNodeB
performs a blind redirection.

eRAN
If blind redirection is selected, the IdleCsfbRedirectOptSwitch option of the

CellAlgoSwitch.HoAllowedSwitch parameter can be selected to enable
optimization of redirection-based CSFB for RRC_IDLE UEs. The optimization
accelerates CSFB by reducing the end-to-end delay. It also reduces the probability
that CSFB will fail because of an initial context setup failure. For details about the
signaling procedure used for optimization of redirection-based CSFB for RRC_IDLE
UEs, see 19.1.6 Redirection-based CSFB Optimization for UEs in Idle Mode.
NOTE
When the UeCapbEnquirySecurityEnhSwitch option of the

GlobalProcSwitch.ProtocolMsgOptSwitch parameter is selected:
● If the UE capability needs to be queried, security mode activation, UE capability query,
and RRC connection release are performed in sequence.
● If the UE capability does not need to be queried, RRC connection release is performed.
4.1.3 Target Cell/Frequency Selection

In measurement-based handling for a UE, the eNodeB determines target cells for
measurement through operations described in this section and instructs the UE to
measure these cells. The eNodeB then selects a target cell for the handover or a
target frequency for the redirection through operations described in 4.1.4
Decision.
In blind handling for a UE, the eNodeB can select a target cell for the handover or
a target frequency for the redirection through operations described in this section.
The target cell or frequency selection procedure includes the following three steps,
regardless of whether measurement-based or blind handling is used:
1. The eNodeB selects the target RAT.
To prioritize a given RAT in measurement-based or blind handling, perform
the following operations:
– For measurement-based handling, enable both CSFB steering to UTRAN
and CSFB steering to GERAN. These functions allow for flexible
configuration of target RATs based on UE states. For details about the
principles, see 10 CSFB Steering to UTRAN and 11 CSFB Steering to
GERAN.
– For blind handling, set the parameters listed in Table 4-2. The eNodeB
selects a target RAT based on RAT priorities without considering UE
states. If both eNodeB- and cell-level parameters are configured, the cell-
level parameter settings are used. Alternatively, you can enable the
preceding two functions mentioned in measurement-based handling to
allow for flexible configuration of target RATs based on UE states.
Table 4-2 RAT priority parameter list
RAT Priority eNodeB-Level Parameter Cell-Level Parameter
Highest CSFallBackBlind- CellOpHoCfg.InterRa

HoCfg.InterRatHighestPri tHighestPri
Second highest CSFallBackBlind- CellOpHoCfg.InterRa
HoCfg.InterRatSecondPri tSecondPri

eRAN
RAT Priority eNodeB-Level Parameter Cell-Level Parameter
Lowest CSFallBackBlind- CellOpHoCfg.InterRa

HoCfg.InterRatLowestPri tLowestPri
2. The eNodeB filters frequencies and neighboring cells.

The eNodeB filters the frequencies configured on it. It filters out the
frequencies not supported by the UE and then filters out the following
neighboring cells on the remaining frequencies:
– Blacklisted neighboring cells
– Neighboring cells to which handovers are prohibited as indicated by the
No handover indicator parameter among cells in neighboring cell lists
– Neighboring cells that do not belong to any PLMN in the PLMN list
among cells in neighboring cell lists
A PLMN list consists of three parts:
▪ The PLMN that the serving cell belongs to
▪ The PLMNs configured in InterPlmnHoList managed objects (MOs),

when the InterPlmnHoSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected
▪ The equivalent PLMNs whose IDs are obtained by the eNodeB from
the information element (IE) Handover Restriction List (sent by the
MME), when both the InterPlmnHoSwitch and EPlmnSwitch
options of the ENodeBAlgoSwitch.HoAlgoSwitch parameter are
selected
– Cells to which handovers are forbidden as indicated by the Handover
Restriction List IE in the INITIAL CONTEXT SETUP REQUEST message sent
from the MME
3. The eNodeB selects the target cell or frequency.
– In measurement-based handling, the eNodeB delivers a measurement
configuration to the UE, instructing the UE to measure the target cells.
Figure 4-5 shows the procedure for selecting the target cells for
measurement.

eRAN
Figure 4-5 Procedure for selecting the target cells for measurement
The procedure shown in Figure 4-5 involves the following data

configuration and actions:
▪ Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
▪ UtranFreqLayerMeasSwitch is an option of the

CellAlgoSwitch.FreqLayerSwitch parameter. The service steering
priorities are specified by the UtranNFreq.CsPriority or
UtranNFreq.CsPsMixedPriority parameter. For details, see 10 CSFB
Steering to UTRAN and 12 Coverage-based E-UTRAN to UTRAN
CS/PS Steering.
▪ The priorities of neighboring UTRAN frequencies for

RRC_CONNECTED UEs are specified by the
UtranNFreq.ConnFreqPriority parameter.
▪ The measurement priorities of neighboring UTRAN cells can be

automatically optimized by the inter-RAT neighbor relationship self-
configuration function, which is controlled by the UTRAN_SWITCH
option of the ENodeBAlgoSwitch.NCellRankingSwitch parameter. It
is recommended that this option be selected only if automatic
neighbor relation (ANR) is enabled.
○ If this option is selected, the eNodeB automatically optimizes the
UtranNCell.NCellMeasPriority parameter setting for

eRAN
neighboring UTRAN cells. This parameter cannot be modified

manually. For details, see ANR Management.
○ If this option is deselected, the measurement priority of a
neighboring cell is specified by the UtranNCell.CellMeasPriority
parameter, which must be configured manually.
▪ When the eNodeB selects highest-priority frequencies or cells, the

number of frequencies or cells selected does not exceed the
maximum permissible number. It is recommended that the highest
priorities be set for the neighboring UTRAN frequencies or cells that
share the site with and have the same coverage as the E-UTRAN cell.
If there are several target frequencies with the same priority, the
UTRAN_CSFB_FREQ_CHOOSE_OPT_SW option of the
GlobalProcSwitch.CsfbFlowOptSwitch parameter can be selected
so that the eNodeB selects target frequencies at random.
▪ For FDD, the maximum permissible number of frequencies is

specified by the
CellUeMeasControlCfg.MaxUtranFddMeasFreqNum parameter.
▪ The maximum permissible number of neighboring cells is defined in

section 6.4 "RRC multiplicity and type constraint values" of 3GPP TS
36.331 V10.1.0.
NOTE
If the serving cell is not configured with neighbor relationships with UTRAN
cells and the frequency priorities for RRC_CONNECTED UEs have been
configured for neighboring UTRAN frequencies, the eNodeB selects a target
frequency for blind redirection.
If the serving cell is not configured with neighbor relationships with UTRAN
cells and the frequency priorities for RRC_CONNECTED UEs are not
configured for neighboring UTRAN frequencies, the eNodeB cannot select a
target frequency for blind redirection. In this case, the eNodeB stops the
procedure.
– If blind handover is used, neighboring UTRAN cells must be configured
on the eNodeB and be assigned blind-handover priorities before the
eNodeB can select a cell as the target cell for the blind handover. Figure
4-6 shows the selection procedure.
NOTE
If no neighboring UTRAN cell is configured and the neighboring UTRAN

frequencies are not assigned the priorities for RRC_CONNECTED UEs, the eNodeB
stops the blind handover procedure and starts the emergency blind redirection
procedure.
If no neighboring UTRAN cell is configured and the neighboring UTRAN
frequencies are assigned the priorities for RRC_CONNECTED UEs, the eNodeB
stops the blind handover procedure and starts the procedure shown in Figure 4-7
to select a target frequency for blind redirection.
If neighboring UTRAN cells are configured but blind-handover priorities are not
configured, the eNodeB stops the blind handover procedure and starts the
procedure shown in Figure 4-5 to select target cells for measurement.

eRAN
Figure 4-6 Target cell selection for a blind handover

▪ UtranFreqLayerBlindSwitch is an option of the

CS/PS Steering.
▪ Neighboring UTRAN cells are configured in UtranNCell MOs.
▪ The blind-handover priorities of neighboring UTRAN cells are

specified by the UtranNCell.BlindHoPriority parameter.
▪ If there is more than one frequency or neighboring cell of the highest

priority, the eNodeB selects one at random.
– If blind redirection is used, the target frequency for the blind redirection
can be selected, as shown in Figure 4-7.

eRAN
NOTE
If all the following conditions are met, the eNodeB stops the blind redirection
procedure and starts the procedure shown in Figure 4-5 to select target cells for
measurement.
● Neighboring UTRAN frequencies are not assigned priorities for
RRC_CONNECTED UEs.
● Neighboring UTRAN cells are configured for the E-UTRAN cell.
● Blind-handover priorities are not configured for the neighboring UTRAN cells.
Figure 4-7 Target frequency selection for blind redirection

▪ Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
▪ The priorities of neighboring UTRAN frequencies for

UtranNFreq.ConnFreqPriority parameter.
▪ UtranFreqLayerBlindSwitch is an option of the

CS/PS Steering.
▪ Neighboring UTRAN cells are configured in UtranNCell MOs.
▪ The eNodeB selects a frequency from the candidates based on blind-

handover priorities of neighboring cells as follows:
○ If neighboring cells are assigned non-zero blind-handover
priorities, specified by UtranNCell.BlindHoPriority, the eNodeB
selects the operating frequency of the cell with the highest
blind-handover priority.

eRAN
○ If all blind-handover priorities are 0, the eNodeB considers

frequency priorities for RRC_CONNECTED UEs. It selects the
frequency with the highest priority for RRC_CONNECTED UEs. If
all frequency priorities for RRC_CONNECTED UEs are 0, the
conditions for blind handling are not met. In this case, the
eNodeB delivers measurement configurations to the UE,
instructing the UE to perform measurement-based CSFB.
▪ The PLMN information about neighboring UTRAN frequencies is

contained in the UtranRanShare or UtranExternalCell MOs.
▪ If there is more than one frequency with the highest service steering
priority during final frequency selection, the eNodeB checks whether
cells on these frequencies are assigned blind-handover priorities.
○ If they are not assigned, the eNodeB selects the frequency with
the highest priority for RRC_CONNECTED UEs.
○ If they are assigned, the eNodeB selects the operating frequency
of the cell with the highest blind-handover priority.
▪ If there is more than one frequency with the highest priority for
RRC_CONNECTED UEs or with the highest blind-handover priority
during final frequency selection, the eNodeB selects one at random.
Alternatively, if the UTRAN_CSFB_FREQ_CHOOSE_OPT_SW option
of the GlobalProcSwitch.CsfbFlowOptSwitch parameter is selected,
the eNodeB randomly selects a frequency as follows:
○ If all the blind-handover priorities of the neighboring cells on all
candidate frequencies are 0, the eNodeB selects a target
frequency at random.
○ If not all blind-handover priorities of the neighboring cells on all
candidate frequencies are 0, the eNodeB selects a target
frequency based on the percentage of neighboring cells with the
highest blind-handover priority. More neighboring cells with the
highest blind-handover priority on a frequency indicate a higher
probability for the frequency to be selected.
▪ If it is found during final frequency selection that the PLMN of a

neighboring UTRAN frequency is different from the PLMN that the
UE belongs to and the PLMN is not included in the inter-PLMN list or
equivalent PLMN list, the eNodeB starts frequency selection for a
blind redirection to the second-priority RAT.
4.1.4 Decision
In measurement-based handling, the eNodeB evaluates the measurement reports
(MRs) sent from the UE and selects a target cell for handover or a target
frequency for redirection. Two evaluation methods are provided: basic handling
based on a single MR and comprehensive handling based on multiple MRs. The
former takes effect by default. No additional configuration is required. The latter
takes effect based on parameter settings.

eRAN
Basic Handling Based on a Single MR

The eNodeB handles the reported MRs in a first-in first-out manner. Based on the
current MR, the eNodeB generates a list of candidate cells arranged in order of
signal quality, from best to worst.
When the CSFB policy is handover, the eNodeB sends a handover request to
candidate cells in sequence. If the handover request for a candidate cell fails, the
eNodeB sends the handover request to the next candidate cell. If the handover
request fails in all cells in the candidate cell list, the eNodeB waits for the UE to
send the next measurement report.
When the CSFB policy is redirection, the eNodeB selects the operating frequency
of the first cell in the candidate cell list for redirection.
Comprehensive Handling Based on Multiple MRs

In this method, the eNodeB can wait for multiple MRs. It selects candidate cells
from the MRs to generate a candidate cell list and then generates a final
candidate cell list. This method is controlled by the
CellHoParaCfg.L2UCsfbMRProMode parameter.
This parameter can be set to HANDOVER_IMMEDIATELY,
BASED_ON_SIGNAL_STRENGTH, or BASED_ON_FREQ_PRIORITY. Figure 4-8
shows the candidate cell list generation and evaluation procedure under different
parameter settings. When this parameter is set to HANDOVER_IMMEDIATELY,
the comprehensive handling procedure is the same as the basic handling
procedure. For emergency call UEs, the HANDOVER_IMMEDIATELY value takes
effect no matter which value this parameter is set to.

eRAN
Figure 4-8 Candidate cell list generation and evaluation procedure
The MR waiting timer for CSFB in Figure 4-8 is specified by the

CellHoParaCfg.CsfbMRWaitingTimer parameter.
If the attempts of handover to all the cells in the final candidate cell list generated
based on signal strength (BASED_ON_SIGNAL_STRENGTH) or frequency priority

eRAN
(BASED_ON_FREQ_PRIORITY) fail, the eNodeB no longer starts the timer but

performs the handover evaluation immediately after receiving a new MR.
BASED_ON_SIGNAL_STRENGTH is suitable for scenarios where the eNodeB
delivers measurement configurations for multiple frequencies and must select the
cell with the best signal strength for a handover or the frequency with the best
signal strength for a redirection from those included in MRs. If the eNodeB
delivers measurement configurations for only one frequency,
BASED_ON_SIGNAL_STRENGTH is equivalent to HANDOVER_IMMEDIATELY.
4.1.5 Execution
This section describes CSFB protection, process optimization, penalty, and retries
during the execution.
CSFB Protection
The CSFB protection timer is specified by the CSFallBackHo.CsfbProtectTimer
parameter. If the UE fallback has not been completed by the time the CSFB
protection timer expires, the eNodeB takes protection measures as follows:
● If the fallback of a UE to UTRAN is performed through a blind PS handover,
the eNodeB delivers the operating frequency of the target UTRAN cell for the
handover to the UE for a blind redirection.
● If the fallback of a UE to UTRAN is performed through a measurement-based
PS handover or redirection, the eNodeB acts differently based on whether it
has received inter-RAT measurement reports from the UE when the timer
expires.
– If the eNodeB has received inter-RAT measurement reports from the UE,
the eNodeB delivers the operating frequency of the target UTRAN cell for
the handover to the UE for a redirection.
– If the eNodeB has not received inter-RAT measurement reports from the
UE, the eNodeB performs an emergency blind redirection in compliance
with the following rules:
▪ The eNodeB preferentially selects a system that the UE has not

measured. For example, if the UE has measured the UTRAN, the
eNodeB preferentially selects the GERAN for a blind redirection. If
only the UTRAN is available, the eNodeB still selects the UTRAN for a
blind redirection. If both systems have been measured, the eNodeB
selects a frequency based on the settings of the
CSFallBackBlindHoCfg.InterRatHighestPri and
CSFallBackBlindHoCfg.IdleCsfbHighestPri parameters.
▪ If there is no target frequency available for blind redirection, the

eNodeB stops the procedure.
Process Optimization
● Handover and CSFB procedure conflict resolution
If an RRC_CONNECTED UE initiates a CSFB procedure during the preparation
for an S1- or X2-based handover, the CSFB procedure conflicts with the
handover procedure. The eNodeB preferentially processes the handover
procedure and responds to the MME with a CSFB call request failure message.

eRAN
After the handover is complete, the MME re-sends a CSFB request message to
the eNodeB to re-initiate the CSFB procedure, as stipulated by 3GPP TS
23.401. If the MME cannot re-send the CSFB request in such a scenario, the
CSFB call fails.
When a UE is attaching to the network or one in idle mode initiates a TAU
procedure, a default bearer is established. The eNodeB considers the UE in
connected mode and allows the handover procedure before completing the
attach or TAU procedure. However, the MME allows the handover procedure
only after the attach or TAU procedure is completed. Therefore, the MME
considers the handover request from the eNodeB as inappropriate and
discards it. The eNodeB waits for a response to the handover request for 20s
(default timer value). If the eNodeB receives a UE CONTEXT MODIFICATION
REQUEST message with the CS Fallback Indicator IE from the MME within the
20s, the eNodeB rejects the CSFB request and therefore the CSFB call fails.
To resolve CSFB call failure problems in these scenarios, the eNodeB needs to
preferentially process the CSFB procedure. If the CsfbFlowFirstSwitch option
of the GlobalProcSwitch.HoProcCtrlSwitch parameter is selected, the
eNodeB preferentially processes the CSFB procedure during handover
preparation. If the eNodeB receives a UE CONTEXT MODIFICATION REQUEST
message containing the CS Fallback Indicator IE before it sends a handover
indication over the air interface, the eNodeB cancels the handover and
performs an emergency blind redirection for CSFB.
NOTE
If a CSFB procedure conflicts with a context-free inter-eNodeB reestablishment, the

eNodeB preferentially processes the reestablishment procedure.
● CSFB admission optimization for RRC_IDLE UEs
An RRC_IDLE UE only has a default bearer for data service, and the allocation
and retention priority (ARP) of the default bearer is generally low. During
CSFB to a cell that is congested or that cannot accommodate more UEs due
to the limitation on the number of UEs, this UE cannot preempt resources in
the target cell for CSFB. To increase the CSFB success rate in this scenario, the
eNodeB can preferentially admit CSFB UEs. This function is controlled by the
CSFallBackPolicyCfg.CsfbUserArpCfgSwitch parameter.
A larger value of the CSFallBackPolicyCfg.NormalCsfbUserArp parameter
indicates a higher probability that RRC_IDLE UEs are admitted to target cells
for CSFB. For details about the admission procedure, see Admission and
Congestion Control.
Retry and Penalty

For CSFB based on PS handover, if admission to the target cell fails for resource or
non-resource reasons after the eNodeB sends a handover request to the target
cell, the eNodeB penalizes the target cell. During the penalty period, the eNodeB
prohibits UEs from being handed over to that cell, preventing the transmission of
unnecessary handover requests and the increase in the handover preparation
failure rate. After the penalty period, if the target cell meets handover
requirements, the eNodeB retries handovers to that cell. For details about the
penalty and retry, see Mobility Management in Connected Mode.
If an emergency blind redirection procedure for CSFB is triggered, the eNodeB
does not consider whether the target cell is penalized during target cell selection.

eRAN
4.1.6 Load-based CSFB to UTRAN

This function is an enhancement to the CSFB to UTRAN function. The
CSFBLoadInfoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
specifies whether to enable this enhanced function.
This function enables the eNodeB to use the RIM procedure in Multiple Reports
mode to obtain the load information about UTRAN cells. For details about RIM-
related principles and parameter configurations, see the descriptions of RIM for E-
UTRAN to obtain load information of UTRAN cells in RIM. After receiving the load
information about UTRAN cells, the eNodeB stores the information and considers
the information when determining the target UTRAN cell for CSFB.
In load-based CSFB to UTRAN, the measurement-based and blind handling

procedures are the same as those in the CSFB to UTRAN function.
There are four UTRAN cell load states: Normal, Midload, Congestion, and
Overload. After load-based CSFB to UTRAN is enabled, the eNodeB selects target
cells for CSFB to UTRAN in descending order of priority in cell load status: Normal
> Midload > Congestion > Overload.
If all of the cells in a measurement report received by the eNodeB are in the
Congestion or Overload state and the eNodeB selects any of these cells as a
handover target cell, handover preparation may fail due to the high load state. To
prevent this failure, operators can select the BASED_ON_LOAD option of the
CellHoParaCfg.L2UCsfbMRProMode parameter. After this option is selected, the
eNodeB selects target cells as follows:
● In a measurement-based handover (which is the scenario where operators are

advised to select the BASED_ON_LOAD option), the eNodeB does not select
cells whose load status is Congestion or Overload in the measurement
reports. If the load status of all of the cells in a measurement report is
Congestion or Overload, the eNodeB waits for subsequent measurement
reports until it receives a measurement report that contains cells whose load
status is Normal or Midload. The eNodeB then selects one of these cells as
the target cell. If the CSFB protection timer expires while the eNodeB is
waiting for measurement reports, the eNodeB triggers a blind redirection.
● In a measurement-based redirection, the eNodeB filters out the frequencies
on which the cells are all in the Congestion or Overload state. The eNodeB
does not deliver these frequencies to the UE for redirection. The eNodeB waits
until it receives a measurement report that contains cells whose load status is
Normal or Midload. The eNodeB then delivers the operating frequencies of
these cells to the UE for redirection. If the CSFB protection timer expires
before the eNodeB can deliver appropriate frequencies to the UE, the eNodeB
triggers a blind redirection.
If flash CSFB to UTRAN is enabled, the eNodeB preferentially includes the
system information of the cells whose load status is Normal or Midload in an
RRC Connection Release message. If the number of these cells is less than the
InterRatHoComm.CellInfoMaxUtranCellNum parameter value, the eNodeB
also includes the system information of the cells whose load status is
Congestion or Overload in the message. The total number of cells whose
system information is included in the message cannot exceed the
InterRatHoComm.CellInfoMaxUtranCellNum parameter value.

eRAN
In load-based CSFB to UTRAN, cell load status affects the target cell selection for
CSFB but does not affect frequency selection for measurement, if necessary, in an
earlier phase. The eNodeB does not select a low-priority frequency for
measurement because all UTRAN cells on a high-priority frequency are
overloaded.
4.2 Network Analysis
4.2.1 Benefits
CSFB offers the following benefits:
● It facilitates CS services for LTE networks.
● It helps operators reduce costs by reusing legacy CS networks with no need to
deploy an IMS network.
4.2.2 Impacts
Network Impacts
CSFB affects the access success rate as follows:
● If redirection is used as the CSFB policy, each CSFB procedure is an access
procedure for the initiation of a new CS service in the UTRAN. Therefore, the
access success rate for CSFB UEs is theoretically the same as that for normal
CS UEs in the UTRAN.
● If PS handover is used as the CSFB policy, the access success rate for CSFB UEs
depends on the success rate of handovers to the target RAT. Handover-based
CS service access has a higher requirement for signal quality than 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.

eRAN
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD CSFB to Cdma1xRttCsf LTE- If this function is

TDD CDMA2000 bSwitch option CDMA2000 enabled together with
1xRTT of the CS Service CSFB to UTRAN, the
ENodeBAlgoS Interworking eNodeB attempts to
witch.HoAlgoS (FDD) perform CSFB to
witch UTRAN first. The
parameter eNodeB tries CSFB to
CDMA2000 1xRTT
only if the CSFB to
UTRAN fails.
Therefore, it is
recommended that
the two functions be
not enabled at the
same time.
4.3 Requirements
4.3.1 Licenses
The following are FDD license requirements.
RAT Feature ID Feature Model Sales Unit

Name
FDD LOFD-001033 CS Fallback to LT1S00CFBU00 per RRC

UTRAN Connected
User
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
Mutually Exclusive Functions

None

eRAN
4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.3.4 Others
CSFB to UTRAN has the following requirements for core networks:
● If a Huawei core network is used, a core network version compatible with
eRAN3.0 or later is required.
● If a third party's core network is used, the core network must support CSFB
complying with 3GPP Release 8. Check that core network software versions
are correct.
Table 4-3 describes the requirements for the core networks.
Table 4-3 Requirements of CSFB to UTRAN for the core networks
Network Requirement
Element (NE)
MME ● Supports the SGs interface to the MSC/visitor location

register (VLR).
● Can select the VLR and location area identity (LAI) based
on the tracking area identity (TAI) of the serving cell.
● Can forward paging messages delivered by the MSC.
● Can perform PLMN selection and reselection.
● Supports combined evolved packet system (EPS)/
international mobile subscriber identity (IMSI) attach,
combined EPS/IMSI detach, and combined TAU/LAU.
● Can route CS signaling.
● Supports SMS over SGs.
MSC ● Supports combined EPS/IMSI attach.

● Can forward paging messages over the SGs interface.
SGSN Does not activate idle mode signaling reduction (ISR) during
the combined routing area update (RAU)/LAU procedure
initiated by the UE.

eRAN
4.4 Operation and Maintenance
4.4.1 Data Configuration (FDD)
4.4.1.1 Data Preparation

Before configuring CSFB to UTRAN, collect data related to neighbor relationships
with UTRAN cells. For details about how to collect data for the parameters related
to neighboring UTRAN cells, see Mobility Management in Connected Mode. This
section only provides information about the managed objects (MOs) related to
neighboring UTRAN cells.
1. UtranNFreq: used to configure neighboring UTRAN frequencies.
2. UtranExternalCell: used to configure external UTRAN cells. The
UtranExternalCell.Rac parameter must be set.
3. UtranExternalCellPlmn: used to configure additional PLMN IDs for each
shared external UTRAN cell. This MO is required only if the NodeB that serves
the external UTRAN cell is working in RAN sharing with common carriers
mode and multiple operators share the external UTRAN cell.
4. UtranNCell: used to configure the neighbor relationship with a UTRAN cell. If
blind handovers to a neighboring UTRAN cell are allowed according to the
network plan, a blind-handover priority must be specified for the cell by
setting the UtranNCell.BlindHoPriority parameter.
Table 4-4 describes the parameters used for function activation.
Table 4-4 Parameters used for activation
Parameter Parameter ID Option Setting Notes

Name
Handover CellAlgoSwit UtranCsfbSwi Select this option.

Allowed ch.HoAllowe tch
Switch dSwitch
Handover ENodeBAlgoS BlindHoSwitc To use blind handling, select
Mode switch witch.HoMod h this option of both
eSwitch parameters.
Handover CellHoParaCf
Mode switch g.HoModeSw
itch
Handover CellHoParaCf UtranPsHoS To use PS handovers, select
Mode switch g.HoModeSw witch the UtranPsHoSwitch option
itch of the
CellHoParaCfg.HoModeSwitc
h parameter and the PS_HO
option of the

eRAN

Name
CSFB CSFallBackPo ● PS_HO CSFallBackPolicyCfg.CsfbHoP

handover licyCfg.CsfbH ● REDIRECTI olicyCfg parameter.
policy oPolicyCfg ON To use redirections, select the
Configuration REDIRECTION option of the
CSFallBackPolicyCfg.CsfbHoP
olicyCfg parameter.
CSFB Protect CSFallBackH None Set this parameter to its
Timer o.CsfbProtect recommended value.
Timer
The parameters used for function optimization are listed in the following tables.
Table 4-5 Related parameters in the CellAlgoSwitch MO

Name
Handover CellAlgoSwit CsfbAdaptive If UTRAN and E-UTRAN cells

Allowed ch.HoAllowe BlindHoSwitc are co-sited and provide the
Switch dSwitch h same coverage, you can
IdleCsfbRedir enable adaptive blind
ectOptSwitch handover for CSFB by
selecting the
CsfbAdaptiveBlindHoSwitch
option.
To shorten the CSFB delay on
the E-UTRAN side by skipping
an RRC connection
reconfiguration procedure
during blind redirection for
CSFB, select the
IdleCsfbRedirectOptSwitch
option.
Table 4-6 Related parameters in the CSFallBackHo MO

Parameter Parameter ID Setting Notes
Name
CSFB CSFallBackHo.BlindHoA1Thd This parameter is used for

Adaptive Rsrp adaptive blind handovers for
Blind Ho A1 CSFB. Set this parameter
RSRP Trigger based on network coverage.
Threshold

eRAN
Table 4-7 Related parameters in the CSFallBackBlindHoCfg MO

Name
UTRAN LCS CSFallBackBlind- Set this parameter based on

capability HoCfg.UtranLcsCap the network plan.
CN Operator CSFallBackBlind- Set this parameter based on

ID HoCfg.CnOperatorId the network plan.
Highest CSFallBackBlind- Set this parameter to its

priority HoCfg.InterRatHighestPri recommended value.
InterRat
Second CSFallBackBlind- Set this parameter to its

priority HoCfg.InterRatSecondPri recommended value.
InterRat Ensure that the second-
highest-priority RAT is
different from the highest-
priority RAT and lowest-
priority RAT.
Lowest CSFallBackBlind- Set this parameter to its

priority HoCfg.InterRatLowestPri recommended value.
InterRat Ensure that the lowest-priority
RAT is different from the
highest-priority RAT and
second-highest-priority RAT.
Table 4-8 Related parameters in the ENodeBAlgoSwitch MO

Name
Handover ENodeBAlgoS CSFBLoadInf To enable load-based CSFB to

Algo switch witch.HoAlgo oSwitch UTRAN, select this option.
Switch Load-based CSFB to UTRAN is
dependent on the RIM
procedure through which the
E-UTRAN obtains the load
information about UTRAN
cells. For details on the basic
parameter configurations
related to RIM, see data
preparation in RIM.
Multi- ENodeBAlgoS UtranSepOp If some operators or RNCs do

Operator witch.MultiO MobilitySwit not support PS handovers to
Control pCtrlSwitch ch UTRAN, select this option.
Switch

eRAN
Table 4-9 Related parameters in the GlobalProcSwitch MO

Name
Choose UMTS GlobalProcS None Set this parameter to

Cell Load Info witch.UtranL BASED_ON_RIM to enable
Trans Channel oadTransCha UTRAN cell load information
n acquisition through RIM if the
RNC, MME, and SGSN support
RIM.
CSFB Flow GlobalProcS UTRAN_CSFB This option specifies whether

Optimization witch.CsfbFlo _FREQ_CHOO to optimize target frequency
Switch wOptSwitch SE_OPT_SW selection if there are several
candidate frequencies with the
same priority. For details, see
4.1.3 Target Cell/Frequency
Selection.
Select or deselect this option
based on the network plan.
Handover GlobalProcS CsfbFlowFirst It is recommended that this

Process witch.HoProc Switch option be selected if the
Control CtrlSwitch number of CSFB preparation
Switch failures increases due to
conflicts between handover
and CSFB procedures.
The number of CSFB
preparation failures due to
procedure conflicts is indicated
by L.CSFB.PrepFail.Conflict.
Table 4-10 Related parameters in the CellHoParaCfg MO

Name
LTE To UTRAN CellHoParaCfg.L2UCsfbMRPr If load-based CSFB to UTRAN

CSFB oMode is enabled, set this parameter
Measurement to BASED_ON_LOAD.
Processing
Mode
CSFB CellHoParaCfg.CsfbMRWaiti Set this parameter to its

Measurement ngTimer recommended value.
Waiting Timer

eRAN
Table 4-11 Related parameters in the CellOpHoCfg MO

Name
Local cell ID CellOpHoCfg.LocalCellId Set this parameter based on

the network plan.
Highest CellOpHoCfg.InterRatHighes Set this parameter to its

Priority tPri recommended value.
InterRAT
Second CellOpHoCfg.InterRatSecond Set this parameter to its

Priority Pri recommended value.
InterRAT
Lowest CellOpHoCfg.InterRatLowest Set this parameter to its

InterRAT
Table 4-12 Related parameters in the UtranNetworkCapCfg MO

Name
Mobile UtranNetworkCapCfg.Mcc If the neighboring cell is

country code working in RAN sharing mode,
set this parameter to the MCC
of the primary operator.
If the peer UTRAN equipment
is provided by Huawei, set this
parameter to the same value
as the corresponding
parameter in the URNCBASIC
MO of the peer RNC.
Mobile UtranNetworkCapCfg.Mnc If the neighboring cell is

network code working in RAN sharing mode,
set this parameter to the MNC
MO of the peer RNC.

eRAN

Name
RNC ID UtranNetworkCapCfg.RncId If the peer UTRAN equipment

MO of the peer RNC.
Network UtranNetworkCapCfg.Netwo Select the PsHoCapCfg option

Capability rkCapCfg for operators or RNCs that
Configuration support PS handovers to
UTRAN.
4.4.1.2 Using MML Commands
Activation Command Examples

Before using MML commands, refer to 4.2.2 Impacts and complete the parameter
configurations for related functions based on the impact relationships between
the functions, as well as the actual network scenario.
● Common step: Enable CSFB to UTRAN.

MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=UtranCsfbSwitch-1;
● Basic scenario 1: CSFB to UTRAN using blind redirection (neighbor

relationships with UTRAN cells have been configured)
Neighbor relationships with UTRAN cells are configured using the UtranNCell
MO. For details on the parameter settings in this MO, see the MML-based
configurations for the basic functions described in Mobility Management in
Connected Mode.
//Selecting blind handling
MOD ENODEBALGOSWITCH: HoModeSwitch=BlindHoSwitch-1;
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;
//Selecting redirection as the CSFB policy
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
//Setting the blind-handover priority
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123, BlindHoPriority=32;
● Basic scenario 2: CSFB to UTRAN using blind redirection (neighbor

relationships with UTRAN cells have not been configured)
If you do not plan to configure neighbor relationships with UTRAN cells, you
must configure the UtranRanShare or UtranExternalCell MO. For details on
the parameter settings in these MOs, see the MML-based configurations for
the basic functions described in Mobility Management in Connected Mode.
//Setting the frequency priority for RRC_CONNECTED UEs
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=9700, ConnFreqPriority=8;
//Setting information about an operator that shares a neighboring frequency
MOD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=9700, Mcc="460", Mnc="20";

eRAN
● Basic scenario 3: CSFB to UTRAN using blind handover

For details on the parameter settings related to neighboring UTRA frequencies
and neighbor relationships with UTRAN cells, see the MML-based
Connected Mode.
//Selecting PS handover as the CSFB policy
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=UtranPsHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=PS_HO-1;
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123, BlindHoPriority=32;
● Basic scenario 4: CSFB to UTRAN using measurement-based redirection
Connected Mode.
//Deselecting the BlindHoSwitch option of the cell-level parameter Handover Mode switch for the
cells to be measured
//Setting the CSFB protection timer
MOD CSFALLBACKHO: LocalCellId=0, CsfbProtectTimer=20;
● Basic scenario 5: CSFB to UTRAN using measurement-based handover
Connected Mode.
//Deselecting the BlindHoSwitch option of the cell-level parameter Handover Mode switch for the
cells to be measured
//Selecting PS handover as the CSFB policy
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=UtranPsHoSwitch-1;
Optimization Command Examples

● Enhanced scenario 1: Load-based CSFB to UTRAN
Load-based CSFB to UTRAN is dependent on the RIM procedure through
which the E-UTRAN obtains the load information about UTRAN cells. For
details on the basic MML-based configurations related to RIM, see RIM.
MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-1;
MOD GLOBALPROCSWITCH: UtranLoadTransChan=BASED_ON_RIM;
MOD CELLHOPARACFG: LocalCellId=0, L2UCsfbMRProMode=BASED_ON_LOAD;
● Enhanced scenario 2: Policy setting for handling conflicts between handover
and CSFB procedures
MOD GLOBALPROCSWITCH: HoProcCtrlSwitch=CsfbFlowFirstSwitch-1;
● Enhanced scenario 3: Highest-priority RAT for CSFB set to UTRAN
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,
InterRatSecondPri=GERAN;
ADD CELLOPHOCFG: LocalCellId=0, CnOperatorId=0, InterRatHighestPri=UTRAN,
InterRatSecondPri=GERAN;
● Enhanced scenario 4: In RAN sharing scenarios, configuration of operator-
specific PS handover capabilities in case some operators do not support PS
handover

eRAN
MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch=UtranSepOpMobilitySwitch-1;

ADD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0, NetworkCapCfg= PsHoCapCfg-0;
● Enhanced scenario 5: Enabling optimization of redirection-based CSFB for
RRC_IDLE UEs
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=IdleCsfbRedirectOptSwitch-1;
Deactivation Command Examples

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Deactivating CSFB to UTRAN
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch= UtranCsfbSwitch-0;
4.4.1.3 Using the MAE-Deployment

● Fast batch activation
This function can be batch activated using the Feature Operation and
Maintenance function of the MAE-Deployment. For detailed operations, see
the following section in the MAE-Deployment product documentation or
online help: MAE-Deployment Management > MAE-Deployment
Guidelines > Enhanced Feature Management > Feature Operation and
Maintenance.
● Single/Batch configuration
This function can be activated for a single base station or a batch of base
stations on the MAE-Deployment. For detailed operations, see Feature
Configuration Using the MAE-Deployment.
4.4.2 Activation Verification

Signaling
The verification procedure is as follows:
1. Enable a UE to camp on an E-UTRAN cell, and use the UE to originate a voice
call so that the UE falls back to a UTRAN cell and completes the call.
2. Enable a UE to camp on an E-UTRAN cell, and use the UE to receive a voice
call so that the UE falls back to a UTRAN cell and completes the call.
The activation verification procedure for load-based CSFB to UTRAN is as follows:
Assume that there are two UTRAN cells A and B. They are both included in UE-
reported MRs. Cell A is under overload control and cell B in the normal state. The
RSCP of cell A is greater than that of cell B.
When measurement-based PS handover is used for CSFB to UTRAN:
1. If the RSCP of cell B meets the handover requirements, the eNodeB transfers
the UE to cell B.
2. If cell B is blocked and the RSCP of cell A meets the handover requirements,
the eNodeB transfers the UE to cell A and the UE can access the network
through preemption and queuing.
Figure 4-9 and Figure 4-10 show example procedures for CSFB to UTRAN for a
mobile-originated call and CSFB to UTRAN for a mobile-terminated call,

eRAN
respectively. In the examples, the UE was in idle mode before the call and
redirection is used for the fallback.
NOTE
In the following figures, the UE on the left side and the UE on the right side are the same
UE. The messages on the UTRAN side are only for reference.
Figure 4-9 CSFB to UTRAN using redirection for a mobile-originated call

eRAN
Figure 4-10 CSFB to UTRAN using redirection for a mobile-terminated call
If the Initial Context Setup Request message does not include UE capability
information, the eNodeB initiates a UE capability enquiry procedure immediately
after it receives the Initial Context Setup Request message.
● If the UeCapbEnquirySecurityEnhSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter is deselected, the UE
capability enquiry procedure is completed before the Uu interface security
mode is activated.
● If the UeCapbEnquirySecurityEnhSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter is selected, the UE
capability enquiry procedure is completed after the Uu interface security
mode is activated.
If the Initial Context Setup Request message includes UE capability information,

the eNodeB initiates a UE capability enquiry procedure after it responds with an
Initial Context Setup Response message.

eRAN
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. It sends an RRC Connection Release (RRC
Conn Rel in the figures) message to the UE. As shown in the red and green boxes
in Figure 4-11, 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 4-11 rrcConnectionRelease message sent during CSFB to UTRAN
If PS handover is used for CSFB to UTRAN, the eNodeB initiates a PS handover

procedure rather than send an RRC Connection Release message to the UE after
receiving a measurement report from the UE. Figure 4-12 shows the PS handover
procedure. As shown in the red and green boxes in Figure 4-13, in the handover
command sent over the air interface, the cs-FallbackIndicator IE is TRUE and the
target RAT is UTRAN.
Figure 4-12 PS handover procedure

eRAN
Figure 4-13 MobilityFromEUTRAN message sent during CSFB to UTRAN
MML Commands
To verify the activation of load-based CSFB to UTRAN, run the DSP
UTRANRIMLOADINFO command to query neighboring UTRAN cell load status
obtained through the RIM procedure.
If the neighboring UTRAN cell load status is displayed, load-based CSFB has been
activated and the eNodeB has obtained the neighboring UTRAN cell load
information.
Counters
Table 4-13 lists the performance counters used for verification.
Table 4-13 Counters for verifying functions related to CSFB to UTRAN

Function Counter ID Counter Name
CSFB to UTRAN 1526728323 L.CSFB.E2W
Emergency call in 1526728709 L.CSFB.E2W.Emergency

CSFB to UTRAN
RIM during load- 1526728949 L.RIM.Load.E2W.Req

based CSFB to
UTRAN 1526728950 L.RIM.Load.E2W.Resp
1526728951 L.RIM.Load.E2W.Update
Load-based CSFB 1526745667 L.IRATHO.E2W.HighLoad.CSFB.PrepAtt

to UTRAN Out
4.4.3 Network Monitoring

CSFB is an end-to-end service. The performance counters on the LTE side can only
indicate the success rate of the CSFB procedure on the LTE side, and they cannot

eRAN
indicate the success rate of the CSFB procedure on the target side. Therefore, the
performance counters on the LTE side cannot directly reflect user experience of the
CSFB procedure. It is recommended that you perform drive tests and use the
performance counters on the UE side to evaluate the actual user experience of the
CSFB procedure.
Table 4-14 lists CSFB-related counters.
Table 4-14 Counters related to the execution of CSFB by the eNodeB
Counter ID Counter Name
1526728321 L.CSFB.PrepAtt
1526728322 L.CSFB.PrepSucc
Table 4-15 lists the counter used for CSFB to UTRAN.
Table 4-15 Counter related to CSFB to UTRAN
1526728323 L.CSFB.E2W
Table 4-16 lists the counters that indicate whether CSFB has been performed
through redirection or handover.
Table 4-16 Counters related to CSFB through redirection or handover
1526728497 L.RRCRedirection.E2W.CSFB
1526728504 L.IRATHO.E2W.CSFB.PrepAttOut
After the CSFB protection timer expires, the eNodeB may perform a blind
redirection to begin the protection procedure. Table 4-17 lists the counter for the
number of times the eNodeB started the protection procedure for CSFB. A larger
value of this counter indicates a longer average UE access delay during CSFB.
Table 4-17 Counter related to the number of times the eNodeB started the
protection procedure for CSFB
1526729515 L.RRCRedirection.E2W.CSFB.TimeOut

eRAN
Table 4-18 lists the counters related to CSFB for emergency calls.
Table 4-18 Counters related to CSFB for emergency calls

1526729510 L.IRATHO.E2W.CSFB.ExecAttOut.Emergency
1526729511 L.IRATHO.E2W.CSFB.ExecSuccOut.Emergenc
y
CSFB handover success rate for emergency calls =

L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency/
L.IRATHO.E2W.CSFB.ExecAttOut.Emergency
NOTE
The CSFB execution success rate may be greater than 100% because CSFB triggering and
CSFB execution in a single end-to-end CSFB procedure may be counted in different
measurement periods, specifically, measurement period n and measurement period n + 1,
respectively.

eRAN
CS Fallback Feature Parameter Description 5 CSFB to GERAN
5 CSFB to GERAN
5.1 Principles
The GeranCsfbSwitch option of the CellAlgoSwitch.HoAllowedSwitch parameter
specifies whether to enable this function.

eRAN
Figure 5-1 CSFB procedure
The CSFB procedure is described in detail in the following sections:

● 5.1.1 Blind/Measurement-based Handling Selection
● 5.1.2 CSFB Policy Selection
● 5.1.3 Target Cell/Frequency Selection
● 5.1.4 Decision
● 5.1.5 Execution

After the eNodeB receives a CS Fallback Indicator, it selects either blind or
measurement-based handling. Figure 5-2 illustrates how this selection is
performed. If GERAN and E-UTRAN cells cover the same area, or if the GERAN cell
covers a larger area than the E-UTRAN cell, blind handling is recommended
because the CSFB delay is shorter.

eRAN
Figure 5-2 Blind/Measurement-based handling selection
The eNodeB- and cell-level blind handover switches described in Figure 5-2 are:
● The BlindHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch
parameter
● The BlindHoSwitch option of the CellHoParaCfg.HoModeSwitch parameter
Measurement-based Handling
The measurement configuration for measurement-based handling is the same as
that for coverage-based handovers from E-UTRAN to GERAN. For details, see
CSFB to GERAN uses the same set of event-B1-related parameters as the
coverage-based inter-RAT handovers except the threshold and time-to-trigger for
event B1, which are described in Table 5-1.
Table 5-1 Parameters related to event B1 for CSFB to GERAN

Parameter Name Parameter ID
CSFB Geran EventB1 Time CSFallBackHo.CsfbHoGeranTimeToTrig

To Trig
CSFB GERAN EventB1 CSFallBackHo.CsfbHoGeranB1Thd

Trigger Threshold

eRAN
When the CSFB_MEAS_DEL_INTERFREQ_SW option of the

CellAlgoSwitch.MeasOptAlgoSwitch parameter is selected, the eNodeB takes the
following actions for measurement optimization:
● When a GERAN measurement is triggered by CSFB, the eNodeB releases all
inter-frequency measurements of the UE.
● When a CSFB-triggered GERAN measurement is ongoing, the eNodeB no
longer instructs the UE to start inter-frequency measurements.
Blind Handling
After selecting blind handling, the eNodeB can choose whether to use adaptive
blind handling for CSFB. The CsfbAdaptiveBlindHoSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter specifies whether to enable this
adaptive blind handling function.
If E-UTRAN and GERAN base stations are co-sited and the E-UTRAN coverage area
is larger than the GERAN coverage area, the eNodeB uses this adaptive blind
handling function to estimate the signal strength of the neighboring GERAN cells
based on the signal strength of the serving E-UTRAN cell. The procedure is shown
in Figure 5-3.

eRAN
Figure 5-3 Adaptive blind handling for CSFB
The threshold for event A1 is specified by the CSFallBackHo.BlindHoA1ThdRsrp

parameter. The event-A1-related mechanisms are the same as those for coverage-
based handovers from E-UTRAN to GERAN. For details, see Mobility Management
in Connected Mode.

There are four policies for CSFB to GERAN: PS handover, cell change order (CCO)
with network assisted cell change (NACC), CCO without NACC, and redirection, in
descending order of selection priority. Figure 5-4 shows how the policy is selected.
This section assumes that neighboring frequencies and cells have been configured
appropriately.

eRAN
Figure 5-4 EUTRAN-to-GERAN CSFB policy selection procedure
Figure 5-4 involves the following parameters:

● The CSFallBackHo.CsfbProtectTimer parameter specifies the CSFB protection
timer. If the UE fallback has not been completed by the time this timer
expires, the eNodeB takes protection measures, as described in 5.1.5
Execution.

eRAN
● The InterRatHoComm.GeranCellNumForEmcRedirect parameter must be

specified if flash CSFB is enabled.
● The options of the ENodeBAlgoSwitch.HoModeSwitch parameter control the
CSFB policies:
– If PS handover is used (that is, CSFallBackPolicyCfg.CsfbHoPolicyCfg is
set to PS_HO), the GeranPsHoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter must be selected.
– If CCO is used (that is, CSFallBackPolicyCfg.CsfbHoPolicyCfg is set to
CCO_HO), the GeranCcoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter must be selected.
If the GeranFlashCsfbSwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter is selected and CCO is
used, the GeranCcoSwitch and GeranNaccSwitch options of the
ENodeBAlgoSwitch.HoModeSwitch parameter must be selected and the
RIM procedure must be used to obtain the system information of external
cells. For the principles of RIM, see RIM.
● The CSFB policy is determined by different parameters, depending on whether
the function described in 11 CSFB Steering to GERAN is enabled.
– If the function is enabled, the parameter for specifying the CSFB policy
depends on the UE status:
▪ The CSFB policy for RRC_IDLE UEs is specified by the

▪ The CSFB policy for RRC_CONNECTED UEs is specified by the

– If the function is disabled, the CSFB policy is specified by the
CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether
UEs are in idle or connected mode.
If none of the REDIRECTION, CCO_HO, and PS_HO options of these CSFB-
policy-related parameters is selected and measurement-based handling is
used, the eNodeB does not apply any CSFB policy to a UE until the CSFB
protection timer expires. Upon the expiration, the eNodeB performs a blind
redirection. If blind handling is used, the eNodeB directly performs a blind
redirection for CSFB.
If admission to the target cell fails during CSFB to GERAN, the eNodeB starts a
penalty and retry procedure for the target cell. The penalty and retry procedure for
CSFB to GERAN is the same as that for CSFB to UTRAN. For details, see Retry and
Penalty.

Target cell/frequency selection in CSFB to GERAN involves three steps. The first
two steps are the same as in CSFB to UTRAN. For details, see 4.1.3 Target Cell/
Frequency Selection. The third step, in which the eNodeB selects the target cell or
frequency, is as follows:
● Measurement-based handling
The eNodeB selects frequencies from the frequency group that has the
highest frequency priority for RRC_CONNECTED UEs. The priority is specified
by the GeranNfreqGroup.ConnFreqPriority parameter. If the number of

eRAN
frequencies in the frequency group with the highest priority exceeds the
number specified by CellUeMeasControlCfg.MaxGeranMeasFreqNum, the
eNodeB does not deliver any frequency in this group and proceeds with
evaluation on other frequency groups in descending order of frequency
priority for RRC_CONNECTED UEs.
NOTE
If the serving cell is not configured with neighbor relationships with GERAN cells and
the frequency priorities for RRC_CONNECTED UEs have been configured for
neighboring GERAN frequencies, the eNodeB selects a target frequency for blind
redirection.
If the serving cell is not configured with neighbor relationships with GERAN cells and
the frequency priorities for RRC_CONNECTED UEs are not configured for neighboring
GERAN frequencies, the eNodeB cannot select a target frequency for blind redirection.
In this case, the eNodeB stops the procedure.
● Blind handling
– If blind handover is used, neighboring GERAN cells must be configured on
the eNodeB and be assigned blind-handover priorities (specified by
GeranNcell.BlindHoPriority) before the eNodeB can select a cell as the
target cell for the blind handover. The eNodeB selects the neighboring
cell with the highest blind-handover priority for handover. If the
preparation for the handover to the cell with the highest blind-handover
priority fails, the eNodeB tries the cell with the second-highest blind-
handover priority. The eNodeB can try a maximum of eight cells. If the
preparation for the handover to the last cell still fails, the eNodeB
performs an emergency blind redirection. Neighboring GERAN cells are
configured in GeranNCell MOs. If there is more than one highest-priority
neighboring cell, the eNodeB randomly selects one.
– If blind redirection is used, neighboring GERAN frequencies and their
priorities for RRC_CONNECTED UEs must be configured before the
eNodeB can select a target frequency for blind redirection. Neighboring
GERAN cell configurations are not required. Figure 5-5 shows the
selection procedure.

eRAN
Figure 5-5 Target frequency selection for blind redirection
▪ When only the range of neighboring GERAN frequencies needs to be

specified, the GeranNfreqGroup MO needs to be configured. When
specific neighboring GERAN frequencies need to be specified, both
the GeranNfreqGroup and GeranNfreqGroupArfcn MOs need to be
configured.
▪ The priorities of neighboring GERAN frequencies for

GeranNfreqGroup.ConnFreqPriority parameter.
▪ Neighboring GERAN cells are configured in GeranNCell MOs.
▪ The eNodeB selects a frequency group from the candidates based on

blind-handover priorities of neighboring cells as follows:
○ If neighboring cells are assigned non-zero blind-handover
priorities, which are specified by GeranNcell.BlindHoPriority,
the eNodeB selects the frequency group that contains the
operating frequency of the cell with the highest blind-handover
priority.
○ If all blind-handover priorities are 0, the eNodeB considers
frequency priorities for RRC_CONNECTED UEs. It selects the

eRAN
frequency group with the highest frequency priority for

RRC_CONNECTED UEs. If all frequency priorities for
RRC_CONNECTED UEs are 0, the conditions for blind handling
are not met. In this case, the eNodeB delivers measurement
configurations to the UE, instructing the UE to perform
measurement-based CSFB.
▪ If there is more than one frequency with the highest priority for
RRC_CONNECTED UEs or with the highest blind-handover priority
during final frequency selection, the eNodeB selects one at random.
▪ If it is found during final frequency selection that the PLMN of a

neighboring GERAN frequency is different from the PLMN that the
UE belongs to and the PLMN is not included in the inter-PLMN list or
equivalent PLMN list, the eNodeB starts frequency selection for a
blind redirection to the second-priority RAT.
5.1.4 Decision
The evaluation of CSFB to GERAN is the same as that of CSFB to UTRAN, except
that CSFB to GERAN does not support comprehensive handling based on multiple
MRs. For details, see 4.1.4 Decision.
5.1.5 Execution
This section describes CSFB protection during the execution. For details about
process optimization, penalty, and retries, see 4.1.5 Execution.
CSFB Protection
The CSFB protection timer is specified by the CSFallBackHo.CsfbProtectTimer
parameter.
If the PS handover, CCO with NACC, or CCO without NACC policy is used, and the
UE has not accessed the target cell and still stays in the area covered by the
eNodeB when the timer expires, the eNodeB performs an emergency blind
redirection based on the following rules:
● The eNodeB preferentially selects a system that the UE has not measured. For
example, if the UE has measured the GERAN, the eNodeB preferentially
selects the UTRAN for a blind redirection. If only the GERAN is available, the
eNodeB still selects the GERAN for a blind redirection.
● If there is no target frequency available for blind redirection, the eNodeB
stops the procedure.
5.2.1 Benefits
The benefits are the same as those of CSFB to UTRAN. For details, see 4.2.1
Benefits.

eRAN
5.2.2 Impacts
Network Impacts
CSFB affects the access success rate as follows:
● If redirection, CCO with NACC, or CCO without NACC is used as the CSFB
policy, each CSFB procedure is an access procedure for the initiation of a new
CS service in the GERAN. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the GERAN.
● If PS handover is used as the CSFB policy, the access success rate for CSFB UEs
depends on the success rate of handovers to the target RAT. Handover-based
CS service access has a higher requirement for signal quality than normal CS
service access. Therefore, the access success rate for CSFB UEs is a little lower
than that for normal CS UEs in the GERAN.
Function Impacts
Name Switch
FDD CSFB to Cdma1xRttCsf LTE- If this function is

TDD CDMA2000 bSwitch option CDMA2000 enabled together with
1xRTT of the CS Service CSFB to GERAN, the
ENodeBAlgoS Interworking eNodeB attempts to
witch.HoAlgoS (FDD) perform CSFB to
witch GERAN first. If the
parameter attempt fails, the
eNodeB tries CSFB to
CDMA2000 1xRTT.
5.3 Requirements
5.3.1 Licenses
Name
FDD LOFD-001034 CS Fallback to LT1S00CFBG00 per RRC

GERAN Connected
User

eRAN
5.3.2 Software
None

None
5.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
5.3.4 Others
Requirements of CSFB to GERAN for core networks are the same as those of CSFB
to UTRAN. For details, see 4.3.4 Others.
5.4.1 Data Configuration

Before configuring CSFB to GERAN, collect data related to neighbor relationships
with GERAN cells. For details about how to collect data for the parameters related
to neighboring GERAN cells, see Mobility Management in Connected Mode. This
section only provides information about the MOs related to neighboring GERAN
cells.
1. GeranNfreqGroup: used to configure GERAN carrier frequency groups.
2. GeranNfreqGroupArfcn: used to configure neighboring BCCH frequencies in
a GERAN carrier frequency group.
3. GeranExternalCell: used to configure external GERAN cells. The
GeranExternalCell.Rac parameter must be set.

eRAN
4. GeranExternalCellPlmn: used to configure additional PLMN IDs for each

shared external GERAN cell. This MO is required only if the BTS that serves
the external GERAN cell is working in RAN sharing with common carriers
mode and multiple operators share the external GERAN cell.
5. GeranNcell: used to configure the neighbor relationship with a GERAN cell. If
blind handovers to a neighboring GERAN cell are allowed according to the
network plan, a blind-handover priority must be specified for the cell by
setting the GeranNcell.BlindHoPriority parameter.
The parameters used for function activation are listed in the following tables.

Name
Handover CellAlgoSwit GeranCsfbSw Select this option.

Allowed ch.HoAllowe itch
Switch dSwitch
Table 5-3 Related parameters in the ENodeBAlgoSwitch MO

Name
Handover ENodeBAlgoSwitch.HoModeS Set this parameter based on

Mode switch witch the network plan.
To use blind handling, also
select the BlindHoSwitch
option.
Table 5-4 Related parameters in the CellHoParaCfg MO

Name
Handover CellHoParaCf BlindHoSwitc To use blind handling, select

Mode switch g.HoModeSw h this option.
itch

Name


eRAN

Name
Highest CSFallBackBlind- Set this parameter to its

priority HoCfg.InterRatHighestPri recommended value.
InterRat
Second CSFallBackBlind- Set this parameter to its

priority HoCfg.InterRatSecondPri recommended value.
priority RAT.
Lowest CSFallBackBlind- Set this parameter to its

priority HoCfg.InterRatLowestPri recommended value.
GERAN LCS CSFallBackBlind- Set this parameter based on

capability HoCfg.GeranLcsCap the network plan. This
parameter specifies the LCS
capability of the GERAN.

Name
CN Operator CellOpHoCfg.CnOperatorId Set this parameter based on

ID the network plan. This
parameter identifies the
operator whose blind-
handover priorities of RATs for
CSFB are to be set.

the network plan. This
parameter identifies the cell
whose blind-handover
priorities of RATs for CSFB are
to be set.
Highest CellOpHoCfg.InterRatHighes Set this parameter to its

Priority tPri recommended value.
InterRAT

eRAN

Name
Second CellOpHoCfg.InterRatSecond Set this parameter to its

InterRAT Ensure that the second-
priority RAT.
Lowest CellOpHoCfg.InterRatLowest Set this parameter to its

InterRAT Ensure that the lowest-priority
Table 5-7 Related parameters in the CSFallBackHo MO

Name
CSFB Protect CSFallBackHo.CsfbProtectTi Set this parameter to its

Timer mer recommended value.
Table 5-8 describes the parameters used for function optimization.
Table 5-8 Parameters used for optimization

Name
Handover CellAlgoSwit CsfbAdaptive If GERAN and E-UTRAN cells

Allowed ch.HoAllowe BlindHoSwitc are co-sited and provide the
Switch dSwitch h same coverage, you can
enable adaptive blind
handover for CSFB by
selecting the
CsfbAdaptiveBlindHoSwitch
option.
CSFB CSFallBackH None This parameter is used for

Adaptive o.BlindHoA1T adaptive blind handovers for
Blind Ho A1 hdRsrp CSFB. Set this parameter
RSRP Trigger based on network coverage.
Threshold

eRAN

Name
Handover GlobalProcS CsfbFlowFirst It is recommended that this

Process witch.HoProc Switch option be selected if the
Control CtrlSwitch number of CSFB preparation
Switch failures increases due to
conflicts between handover
and CSFB procedures.
The number of CSFB
preparation failures due to
procedure conflicts is indicated
by L.CSFB.PrepFail.Conflict.
Measurement CellAlgoSwit CSFB_MEAS_ Select this option if you need

Optimization ch.MeasOptA DEL_INTERFR to enable deletion of inter-
Algorithm lgoSwitch EQ_SW frequency measurement
Switch configurations when
measurements for CSFB start.

Before using MML commands, refer to 5.2.2 Impacts and complete the parameter
configurations for related functions based on the impact relationships between
the functions, as well as the actual network scenario.
● Common step: Enable CSFB to GERAN.

For details on the parameter settings related to neighboring GERAN
frequencies and neighbor relationships with GERAN cells, see the MML-based
Connected Mode.
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=GeranCsfbSwitch-1;
● Basic scenario 1: CSFB to GERAN using blind redirection (neighbor

relationships with GERAN cells have been configured)
Neighbor relationships with GERAN cells are configured using the GeranNCell
MO. For details on the parameter settings in this MO, see the MML-based
Connected Mode.
MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15, BlindHoPriority=32;
● Basic scenario 1: CSFB to GERAN using blind redirection (neighbor

relationships with GERAN cells have not been configured)
If you do not plan to configure neighbor relationships with GERAN cells, you
must configure the GeranRanShare or GeranExternalCell MO. For details on

eRAN
the parameter settings in these MOs, see the MML-based configurations for
the basic functions described in Mobility Management in Connected Mode.
//Setting the frequency priority for RRC_CONNECTED UEs and adding a neighboring GERAN BCCH
carrier frequency group.
ADD GERANNFREQGROUP: LocalCellId=0, BcchGroupId=0, GeranVersion=GSM,
StartingArfcn=0,BandIndicator=GSM_dcs1800, ConnFreqPriority=8;
ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0, GeranArfcn=0;
//Setting information about an operator that shares the neighboring frequency group
ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="20";
● Basic scenario 2: CSFB to GERAN using blind CCO with NACC
//Selecting CCO with NACC as the CSFB policy and enabling RIM in Multiple Reports mode
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=CCO_HO-1&PS_HO-0;
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranNaccSwitch-1&GeranCcoSwitch-1,
RimSwitch=GERAN_RIM_SWITCH-1;
MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15, BlindHoPriority=32;
● Basic scenario 3: CSFB to GERAN using blind handover
//Selecting the GeranPsHoSwitch option of the Handover Mode switch parameter
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranPsHoSwitch-1;
//(Optional) Selecting the PS_HO option of the CSFB handover policy Configuration parameter if
CSFB steering to GERAN is enabled
MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;
● Basic scenario 4: CSFB to GERAN using measurement-based redirection
//Selecting measurement-based handling
● Basic scenario 5: CSFB to GERAN using measurement-based handover
//Selecting the GeranPsHoSwitch option of the Handover Mode switch parameter
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranPsHoSwitch-1;
//(Optional) Selecting the PS_HO option of the CSFB handover policy Configuration parameter if
CSFB steering to GERAN is enabled
● Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC
//Selecting the GeranNaccSwitch and GeranCcoSwitch options of the Handover Mode switch
parameter and the GERAN_RIM_SWITCH option of the RIM switch parameter
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranNaccSwitch-1&GeranCcoSwitch-1,
RimSwitch=GERAN_RIM_SWITCH-1;
//Setting the MME Release parameter to Release_R9 when link mode is used at the eNodeB for S1
setup
MOD S1INTERFACE: S1InterfaceId=2, S1CpBearerId=1, CnOperatorId=0, MmeRelease=Release_R9;
//Setting the MME Release parameter to Release_R9 when endpoint mode is used at the eNodeB for
S1 setup
MOD S1: S1Id=0, CnOperatorId=0, MmeRelease=Release_R9;
//Deselecting the PS_HO option and selecting the CCO_HO option of the CSFB handover policy

eRAN
Configuration parameter
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=CCO_HO-1&PS_HO-0;

//(Optional) Setting the policy for handling conflicts between handover and CSFB procedures
MOD GLOBALPROCSWITCH: HoProcCtrlSwitch= CsfbFlowFirstSwitch-1;
//(Optional) Setting GERAN as the highest-priority RAT for CSFB
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN, InterRatSecondPri=UTRAN;
ADD CELLOPHOCFG: LocalCellId=0, CnOperatorId=0, InterRatHighestPri=GERAN, InterRatSecondPri=UTRAN;
//(Optional) Enabling deletion of inter-frequency measurement configurations when measurements for
CSFB start
MOD CELLALGOSWITCH: LocalCellId=0, MeasOptAlgoSwitch=CSFB_MEAS_DEL_INTERFREQ_SW-1;

conditions.
//Deactivating CSFB to GERAN
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=GeranCsfbSwitch-0;

Maintenance.

Signaling
1. Enable a UE to camp on an E-UTRAN cell, and use the UE to originate a voice
call so that the UE falls back to a GERAN cell and completes the call.
2. Enable a UE to camp on an E-UTRAN cell, and use the UE to receive a voice
call so that the UE falls back to a GERAN cell and completes the call.
Figure 5-6 shows the signaling procedure for redirection-based CSFB to GERAN.
NOTE
In the following figures, the UE on the left side and the UE on the right side are the same
UE. The signaling on the GERAN side is for reference only. The procedure for mobile-
terminated calls is similar to the procedure for mobile-originated calls. The difference is
that the procedure for mobile-terminated calls includes paging.

eRAN
Figure 5-6 Redirection-based CSFB to GERAN for a mobile-originated call
The signaling procedure for PS handover-based CSFB to GERAN differs from that
for redirection-based CSFB to GERAN in that the eNodeB performs a PS handover
procedure rather than an RRC connection release procedure after the UE reports
measurement results to the eNodeB. For details about the PS handover procedure,
see 4.4.2 Activation Verification. In such a procedure for CSFB to GERAN, the cs-
FallbackIndicator IE is TRUE and the target RAT is GERAN in the
MobilityFromEUTRACommand message.
Figure 5-7 shows the signaling procedure for CCO-based CFSB (with or without
NACC) to GERAN for a mobile-originated call. In the CSFB, handover preparation
is absent. The MobilityFromEUTRACommand message carries the CCO with/
without NACC information and the CSFB target is GERAN.

eRAN
Figure 5-7 CCO-based CSFB (with or without NACC) to GERAN for a mobile-
originated call
Counters
Table 5-9 Counters used for function verification
CSFB to GERAN 1526728324 L.CSFB.E2G
Emergency call in CSFB 1526728710 L.CSFB.E2G.Emergency

to GERAN

eRAN

CSFB is an end-to-end service. The performance counters on the LTE side can only
indicate the success rate of the CSFB procedure on the LTE side, and they cannot
indicate the success rate of the CSFB procedure on the target side. Therefore, the
performance counters on the LTE side cannot directly reflect user experience of the
CSFB procedure. It is recommended that you perform drive tests and use the
performance counters on the UE side to evaluate the actual user experience of the
CSFB procedure.
Table 5-10 lists CSFB-related counters.
Table 5-10 Counters related to the execution of CSFB by the eNodeB
1526728321 L.CSFB.PrepAtt
1526728322 L.CSFB.PrepSucc
Table 5-11 lists the counter related to CSFB to GERAN.
Table 5-11 Counter related to CSFB to GERAN
1526728324 L.CSFB.E2G
through redirection or handover.
Table 5-12 Counters related to CSFB through redirection or handover
1526728498 L.RRCRedirection.E2G.CSFB
1526728507 L.IRATHO.E2G.CSFB.PrepAttOut
through CCO with NACC or CCO without NACC.
Table 5-13 Counters related to the use of CCO with NACC or CCO without NACC
1526729505 L.CCOwithNACC.E2G.CSFB.ExecAttOu
t

eRAN
1526729507 L.CCOwithoutNACC.E2G.CSFB.ExecAtt
Out
After the CSFB protection timer expires, the eNodeB may perform a blind
redirection to begin the protection procedure. Table 5-14 lists the counter for the
number of times the eNodeB started the protection procedure for CSFB. A larger
value of this counter indicates a longer average UE access delay during CSFB.
Table 5-14 Counter related to the number of times the eNodeB started the
protection procedure for CSFB
1526729516 L.RRCRedirection.E2G.CSFB.TimeOut
Table 5-15 lists the counters related to CSFB for emergency calls.
Table 5-15 Counters related to CSFB for emergency calls

1526729513 L.IRATHO.E2G.CSFB.ExecAttOut.Emer
gency
1526729514 L.IRATHO.E2G.CSFB.ExecSuccOut.Em
ergency
CSFB handover success rate for emergency calls =

L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency/
L.IRATHO.E2G.CSFB.ExecAttOut.Emergency
NOTE
The CSFB execution success rate may be greater than 100% because CSFB triggering and
CSFB execution in a single end-to-end CSFB procedure may be counted in different
measurement periods, specifically, measurement period n and measurement period n + 1,
respectively.

eRAN
CS Fallback Feature Parameter Description 6 Flash CSFB to UTRAN
6 Flash CSFB to UTRAN
6.1 Principles
The UtranFlashCsfbSwitch option of the CellAlgoSwitch.HoAllowedSwitch
parameter specifies whether to enable flash CSFB to UTRAN.
Flash CSFB to UTRAN is based on CSFB to UTRAN. In flash CSFB to UTRAN, the
eNodeB uses the RIM procedure to obtain system information of UTRAN cells and
uses a message for redirection to UTRAN to send the obtained system information
to the UE. When the UE accesses one of the UTRAN cells, it does not need to read
the system information of the UTRAN cell. This shortens access delay. Figure 6-1
shows the enhancements in flash CSFB to UTRAN in comparison with CSFB to
UTRAN.

eRAN
Figure 6-1 Enhancements in flash CSFB to UTRAN in comparison with CSFB to

UTRAN
As shown in Figure 6-1:

● After CSFB policy selection and target cell/frequency selection, the eNodeB
requests system information of UTRAN cells through a RIM procedure. For
details about the principles for RIM, see RIM.
● Flash CSFB to UTRAN can be used only if redirection is selected as the CSFB
policy. This is because the eNodeB needs to use a message for redirection to
UTRAN to send the obtained system information of UTRAN cells to the UE. If
another CSFB policy is selected, CSFB to UTRAN is performed. For details on
the procedure for selecting a CSFB policy and related parameter settings, see
4.1.2 CSFB Policy Selection.
● During target cell/frequency selection in the case of blind redirection, the
eNodeB selects cells whose system information has been obtained. For details,
see 6.1.1 Target Cell/Frequency Selection. In the decision phase of
measurement-based redirection, the eNodeB selects cells whose system
information has been obtained. For details, see 6.1.2 Decision. As the UE has
obtained system information of UTRAN cells from the RRC Connection
Release message, the UE does not need to read the system information of
UTRAN cells. This shortens the redirection delay.
For FDD, if operators' network capabilities for the RIM procedure are different in
RAN sharing scenarios, you can enable the Separate Mobility Policies to UTRAN
for Multi PLMN function (see Mobility Management in Connected Mode) to
specify whether a particular operator supports the RIM procedure and whether
flash CSFB to UTRAN is enabled for the operator.

eRAN
If flash CSFB cannot be performed for some UEs due to UE compatibility issues
and there are service drops as a result, Terminal Awareness Differentiation can be
enabled to add these UEs to the blacklist of flash CSFB. In this case, CSFB instead
of flash CSFB is performed for these UEs, decreasing the service drop rate. For
details, see descriptions related to blacklist control in Terminal Awareness
Differentiation.

In a blind redirection, in addition to the operations described in 4.1.3 Target Cell/
Frequency Selection, the eNodeB performs the following operations to select cells
whose system information has been obtained:
1. The eNodeB generates a target cell list (containing a maximum of eight cells)
based on the blind-handover priorities of neighboring cells on the target
frequency for redirection. The eNodeB then adds other neighboring cells on
the target frequency to the list. The UTRAN_SWITCH option of the
ENodeBAlgoSwitch.NCellRankingSwitch parameter controls the sequence of
adding these neighboring cells.
If this option is selected, the eNodeB adds these neighboring cells in
descending order of the priority specified by the
UtranNCell.NCellMeasPriority parameter.
If this option is deselected, the eNodeB adds these neighboring cells at
random.
2. If the InterRatHoComm.CellInfoMaxUtranCellNum and
InterRatHoComm.UtranCellNumForEmcRedirect parameters (the latter is
used only for emergency redirection) are set to N:
– If the number of target cells is greater than or equal to N, the eNodeB
selects the first N cells.
– If the number of target cells is smaller than N, the eNodeB selects all
these cells.
3. The eNodeB filters out the target cells whose system information has not
been obtained.
4. The eNodeB filters cells based on SPID-based mobility management in
connected mode. For details, see the descriptions of SPID-based camping and
handover in Flexible User Steering .
6.1.2 Decision
In a measurement-based redirection, in addition to the operations described in
4.1.4 Decision, the eNodeB performs the following operations to select cells
1. The eNodeB adds the neighboring cells on the target frequency for redirection
but not in measurement reports, in a random sequence, to the target cell list
generated based on measurement reports.
2. If the InterRatHoComm.CellInfoMaxUtranCellNum and
InterRatHoComm.UtranCellNumForEmcRedirect parameters (the latter is

eRAN
these cells.
3. The eNodeB filters out cells whose system information has not been obtained.
6.2.1 Benefits
Flash CSFB to UTRAN enables UEs to obtain information about target UTRAN cells
for redirection before RRC connections to the LTE network are released, reducing
the delay of CSFB to UTRAN by approximately 0.2s to 0.5s. This gain varies
depending on the radio network environment and the processing capability of
UEs.
6.2.2 Impacts
Network Impacts
Flash CSFB affects the access success rate as follows:
● Each flash CSFB procedure is an access procedure for the initiation of a new
CS service in the UTRAN. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the UTRAN.
● The RRC connection setup success rate may decrease slightly for the UTRAN.
The uplink interference information contained in SIB7 in the UTRAN is
updated frequently. The RNC cannot update the uplink interference
information in the system information sent to the LTE network as frequently
as the information is updated in SIB7 in the UTRAN. Therefore, the uplink
interference information obtained by the LTE network from SIB7 is a default
value (–105 dBm). If the actual uplink interference in the UTRAN is greater
than –105 dBm, the UEs' transmit power for the physical random access
channel (PRACH) increases and the RRC connection setup success rate may
decrease.
Function Impacts
None
6.3 Requirements
6.3.1 Licenses

eRAN

Name
FDD LOFD-001052 Flash CS LT1S0FCFBU00 per RRC

Fallback to Connected
UTRAN User
6.3.2 Software
RAT Function Name Function Switch Reference
FDD CSFB to UTRAN UtranCsfbSwitch option of CS Fallback

TDD the
CellAlgoSwitch.HoAllowedS
witch parameter
FDD RIM for E-UTRAN to UTRAN_RIM_SWITCH option RIM
TDD obtain system of the
information of ENodeBAlgoSwitch.RimSwitc
UTRAN/GERAN cells h parameter

None
6.3.3 Hardware
This section is the same as the corresponding section for CSFB to UTRAN. For
details, see 4.3.3 Hardware.
6.3.4 Others
Core Network
Table 6-1 describes the requirements of flash CSFB to UTRAN for core networks. If
a Huawei core network is used, a core network version compatible with eRAN3.0
or later is required.

eRAN
Table 6-1 Requirements of flash CSFB to UTRAN for core networks
NE Function Description
MME Supports CSFB and Release 9 RIM procedures
SGSN Supports CSFB and Release 9 RIM procedures
Controller
If the controller to be connected is provided by Huawei, enable RIM sequence
number (RSN) optimization on the controller side. For details, see Fast CS Fallback
Based on RIM in RAN Feature Documentation.
UTRAN
If the UTRAN uses Huawei equipment, Fast CS Fallback Based on RIM must be
enabled on the UTRAN. For details, see Fast CS Fallback Based on RIM in RAN
Feature Documentation.
UE
UEs must be compliant with 3GPP Release 9 or later.

Neighbor relationships with UTRAN cells must be configured because only the
neighboring cells whose system information has been obtained can be target cells
for flash CSFB to UTRAN. Table 6-2 and Table 6-3 describe the parameters used
for function activation and optimization, respectively.

Name
Handover CellAlgoSwit UtranFlashCs Select this option.

Allowed ch.HoAllowe fbSwitch
Switch dSwitch
Max Utran InterRatHoC None Set this parameter to its
cell num in omm.CellInfo recommended value.
redirection MaxUtranCel
lNum

eRAN
Parameter Name Parameter ID Setting Notes
Max Utran cell InterRatHoCom To use flash CSFB for emergency

num in CSFB EMC m.UtranCellNum redirection, change the parameter
redirection ForEmcRedirect value from the default value 0 to a
non-zero value.

Before using MML commands, refer to 6.3.2 Software and complete the
parameter configurations for related functions based on the dependency
relationships between the functions, as well as the actual network scenario.
//Enabling flash CSFB to UTRAN
MOD CELLALGOSWITCH: LocalCellId=0, HoAllowedSwitch=UtranFlashCsfbSwitch-1;
//Setting the number of UTRAN cells that can be contained in the redirection message to, for example, 8
MOD INTERRATHOCOMM: CellInfoMaxUtranCellNum=8;

//(Optional) Setting the number of UTRAN cells carried during CSFB emergency redirection to, for example,
3
MOD INTERRATHOCOMM: UtranCellNumForEmcRedirect=3;

conditions.
//Deactivating flash CSFB to UTRAN
MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch =UtranFlashCsfbSwitch-0;

Maintenance.

eRAN

Signaling Observation
Enable a UE to camp on an E-UTRAN cell, and use the UE to originate a voice call.
If the UE falls back to a UTRAN cell and completes the call, and the RRC
Connection Release message traced on the Uu interface carries system
information of the neighboring UTRAN cell, flash CSFB to UTRAN has been
activated.
The signaling procedure for flash CSFB to UTRAN is the same as that for
redirection-based CSFB to UTRAN described in 4.4.2 Activation Verification. The
difference is that the RRC Connection Release message carries the system
information of the neighboring UTRAN cell.
MML Command Observation

If the RIM procedure in Multiple Reports mode is used, run the DSP
UTRANRIMINFO command to query the RIM status of neighboring UTRAN cells.
If the ID of a neighboring UTRAN cell is displayed in the command output, the
eNodeB has obtained the system information of this neighboring UTRAN cell.
Counter Observation

Flash CSFB to UTRAN 1526728705 L.FlashCSFB.E2W
RIM in flash CSFB to 1526728946 L.RIM.SI.E2W.Req

UTRAN
1526728947 L.RIM.SI.E2W.Resp
1526728948 L.RIM.SI.E2W.Update

details, see 4.4.3 Network Monitoring.

eRAN
CS Fallback Feature Parameter Description 7 Flash CSFB to GERAN
7 Flash CSFB to GERAN
7.1 Principles
The GeranFlashCsfbSwitch option of the CellAlgoSwitch.HoAllowedSwitch
parameter specifies whether to enable flash CSFB to GERAN.
Flash CSFB to GERAN is based on CSFB to GERAN. In flash CSFB to GERAN, the
eNodeB uses the RIM procedure to obtain system information of GERAN cells and
uses a message for redirection to GERAN to send the obtained system information
to the UE. When the UE accesses one of the GERAN cells, it does not need to read
the system information of the GERAN cell. This shortens access delay. Figure 7-1
shows the enhancements in flash CSFB to GERAN in comparison with CSFB to
GERAN.

eRAN
Figure 7-1 Enhancements in flash CSFB to GERAN in comparison with CSFB to

GERAN
As shown in Figure 7-1:

● After CSFB policy selection and target cell/frequency selection, the eNodeB
requests system information of GERAN cells through a RIM procedure. For
details about the principles for RIM, see RIM.
● Flash CSFB to GERAN can be used only if redirection is selected as the CSFB
policy. This is because the eNodeB needs to use a message for redirection to
GERAN to send the obtained system information of GERAN cells to the UE. If
another CSFB policy is selected, CSFB to GERAN is performed. For details on
the procedure for selecting a CSFB policy and related parameter settings, see
5.1.2 CSFB Policy Selection.
● During target cell/frequency selection in the case of blind redirection, the
eNodeB selects cells whose system information has been obtained. For details,
see 7.1.1 Target Cell/Frequency Selection. In the decision phase of
measurement-based redirection, the eNodeB selects cells whose system
information has been obtained. For details, see 7.1.2 Decision. As the UE has
obtained system information of GERAN cells from the RRC Connection
Release message, the UE does not need to read the system information of
GERAN cells. This shortens the redirection delay.
If operators' network capabilities for the RIM procedure are different in RAN
sharing scenarios, you can enable the Separate Mobility Policies to GERAN for
Multi PLMN function (see Mobility Management in Connected Mode) to specify
whether a particular operator supports the RIM procedure and whether flash CSFB
to GERAN is enabled for the operator.

eRAN

In a blind redirection, in addition to the operations described in 5.1.3 Target Cell/
Frequency Selection, the eNodeB performs the following operations to select cells
1. The eNodeB generates a target cell list (containing a maximum of eight cells)
based on the blind-handover priorities of neighboring cells on the target
frequency for redirection. The eNodeB then adds other neighboring cells on
the target frequency to the list. The GERAN_SWITCH option of the
ENodeBAlgoSwitch.NCellRankingSwitch parameter controls the sequence of
adding these neighboring cells.
If this option is selected, the eNodeB adds these neighboring cells in
descending order of the priority specified by the
GeranNcell.NCellMeasPriority parameter.
If this option is deselected, the eNodeB adds these neighboring cells at
random.
2. If the InterRatHoComm.CellInfoMaxGeranCellNum and
InterRatHoComm.GeranCellNumForEmcRedirect parameters (the latter is
these cells.
4. The eNodeB filters cells based on SPID-based mobility management in
connected mode. For details, see the descriptions of SPID-based camping and
handover in Flexible User Steering.
7.1.2 Decision
In a measurement-based redirection, in addition to the operations described in
5.1.4 Decision, the eNodeB performs the following operations to select cells
1. The eNodeB adds the neighboring cells on the target frequency for redirection
but not in measurement reports, in a random sequence, to the target cell list
generated based on measurement reports.
2. If the InterRatHoComm.CellInfoMaxGeranCellNum and
InterRatHoComm.GeranCellNumForEmcRedirect parameters (the latter is
these cells.

eRAN
7.2.1 Benefits
Flash CSFB to GERAN enables UEs to obtain information about target GERAN cells
for redirection before RRC connections to the LTE network are released, reducing
the delay of CSFB to GERAN by approximately 0.2s to 0.5s. This gain varies
depending on the radio network environment and the processing capability of
UEs.
7.2.2 Impacts
Network Impacts
Each flash CSFB procedure is an access procedure for the initiation of a new CS
service in the GERAN. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the GERAN.
Function Impacts
None
7.3 Requirements
7.3.1 Licenses

Name
FDD LOFD-001053 Flash CS LT1S0FCFBG0 per RRC Connected

Fallback to 0 User
GERAN
7.3.2 Software
FDD CSFB to GERAN GeranCsfbSwitch option of CS Fallback

TDD the
CellAlgoSwitch.HoAllowed
Switch parameter

eRAN
FDD RIM for E-UTRAN GERAN_RIM_SWITCH RIM

TDD to obtain system option of the
information of ENodeBAlgoSwitch.RimSwi
UTRAN/GERAN tch parameter
cells

None
7.3.3 Hardware
This section is the same as the corresponding section for CSFB to GERAN. For
7.3.4 Others
Core Network
Table 7-1 describes the requirements of flash CSFB to GERAN for core networks. If
a Huawei core network is used, a core network version compatible with eRAN3.0
or later is required.
Table 7-1 Requirements of flash CSFB to GERAN for core networks
MME Supports CSFB and Release 9 RIM procedures
SGSN Supports CSFB and Release 9 RIM procedures
GERAN
If the GERAN uses Huawei equipment, evolved network assisted cell change
(eNACC) between E-UTRAN and GERAN for CSFB must be enabled on the GERAN.
For detailed operations, see the description of eNACC from E-UTRAN to GERAN in
Interoperability Between GSM and LTE Feature Parameter Description of GBSS
feature documentation.
UE
UEs must be compliant with 3GPP Release 9 or later.

eRAN

Neighbor relationships with GERAN cells must be configured because only the
neighboring cells whose system information has been obtained can be target cells
for flash CSFB to GERAN. Table 7-2 and Table 7-3 describe the parameters used
for function activation and optimization, respectively.

Name
Handover CellAlgoSwit GeranFlashCs Select this option.

Allowed ch.HoAllowe fbSwitch
Switch dSwitch
Max Geran InterRatHoC None Set this parameter to its
cell num in omm.CellInfo recommended value.
redirection MaxGeranCel
lNum
Parameter Name Parameter ID Setting Notes
Max Geran cell InterRatHoCom To use flash CSFB for emergency

num in CSFB EMC m.GeranCellNum redirection, change the parameter
redirection ForEmcRedirect value from the default value 0 to a
non-zero value.

//Enabling flash CSFB to GERAN
MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch=GeranFlashCsfbSwitch-1;
//Setting the number of GERAN cells that can be contained in the redirection message to, for example, 8
MOD INTERRATHOCOMM: CellInfoMaxGeranCellNum=8;

//(Optional) Setting the number of GERAN cells carried during CSFB emergency redirection to, for example,
3
MOD INTERRATHOCOMM: GeranCellNumForEmcRedirect=3;

eRAN

conditions.
//Deactivating flash CSFB to GERAN
MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch=GeranFlashCsfbSwitch-0;

Maintenance.

Enable a UE to camp on an E-UTRAN cell, and use the UE to originate a voice call.
If the UE falls back to a GERAN cell and completes the call, and the RRC
Connection Release message traced on the Uu interface carries system
information of the neighboring GERAN cell, flash CSFB to GERAN has been
activated.
On the LTE side, the signaling procedure for flash CSFB to GERAN is the same as
that for redirection-based CSFB to GERAN described in 5.4.2 Activation
Verification. The difference is that the RRC Connection Release message carries
the system information of the neighboring GERAN cell.
MML Command Observation

If the RIM procedure in Multiple Reports mode is used, run the DSP
GERANRIMINFO command to query the RIM status of neighboring GERAN cells. If
the ID of a neighboring GERAN cell is displayed in the command output, the
eNodeB has obtained the system information of this neighboring GERAN cell.
Counter Observation

eRAN

Flash CSFB to GERAN 1526728706 L.FlashCSFB.E2G
RIM in flash CSFB to 1526729661 L.RIM.SI.E2G.Req

GERAN
1526729662 L.RIM.SI.E2G.Resp
1526729663 L.RIM.SI.E2G.Update

details, see 5 CSFB to GERAN.

eRAN
CS Fallback Feature Parameter Description 8 Ultra-Flash CSFB to UTRAN
8 Ultra-Flash CSFB to UTRAN
8.1 Principles
The UtranUltraFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch
parameter specifies whether to enable ultra-flash CSFB to UTRAN. Use this
function in areas where UMTS and LTE coverage areas overlap if the following
conditions are met: The eNodeB, RNC, MME, and MSC are provided by Huawei,
and a proportion of UEs support single radio voice call continuity (SRVCC) from E-
UTRAN to UTRAN.
This function has the following enhancements to CSFB to UTRAN:
The function of disabling blind handling is added to blind/measurement-based

handling selection. For details, see 8.1.1 Blind/Measurement-based Handling
Selection.
The eNodeB can select SRVCC as the CSFB policy to hand over the UE to the
UTRAN using an SRVCC procedure. The procedure has CS resources on the UTRAN
prepared in advance and omits certain protocol-defined signaling procedures
during access to the UTRAN. For details, see 8.1.2 CSFB Policy Selection.

The blind/measurement-based handling selection for ultra-flash CSFB to UTRAN is
the same as that for CSFB to UTRAN except that measurement-based handling
can be used for ultra-flash CSFB even if blind handling has been selected.
If blind handling is selected for a UE supporting ultra-flash CSFB, the eNodeB

further checks whether to use blind handling for the UE based on the
UFCsfbBlindHoDisSwitch option setting of the CellHoParaCfg.HoModeSwitch
parameter.
● If this option is selected, the eNodeB disables blind handling and performs a
measurement-based CSFB procedure for the UE.
● If this option is deselected, the eNodeB performs a blind CSFB procedure for
the UE.

eRAN

Ultra-flash CSFB to UTRAN uses the SRVCC procedure. Figure 8-1 shows the
policy selection.
Figure 8-1 EUTRAN-to-UTRAN ultra-flash CSFB policy selection procedure
Ultra-flash CSFB to UTRAN is controlled by the UtranUltraFlashCsfbSwitch

option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter. Other parameter
settings for ultra-flash CSFB to UTRAN are consistent with those for CSFB to
UTRAN described in 4.1.2 CSFB Policy Selection.

eRAN
If a UE does not support ultra-flash CSFB, there will be UE compatibility issues. To

address the issues, select the UltraFlashCsfbComOptSw option of the
GlobalProcSwitch.UeCompatSwitch parameter. When the
UltraFlashCsfbComOptSw option is selected, the eNodeB supports ultra-flash
CSFB only after it receives the bitSrvccBasedEcsfbOperationPossible IE from the
MME through a Huawei proprietary message.
For FDD, if operators' network capabilities for ultra-flash CSFB to UTRAN are
different in RAN sharing scenarios, the Separate Mobility Policies to UTRAN for
Multi PLMN function can be enabled to specify whether to use ultra-flash CSFB to
UTRAN for a particular operator. For details on how to activate the Separate
Mobility Policies to UTRAN for Multi PLMN function, see Mobility Management in
Connected Mode.
● The Separate Mobility Policies to UTRAN for Multi PLMN function is
controlled by the UtranSepOpMobilitySwitch option of the
ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.
● The ultra-flash CSFB capability of operators for Separate Mobility Policies to
UTRAN for Multi PLMN is controlled by the UtranNetworkCapCfg.Mcc,
UtranNetworkCapCfg.Mnc, and UtranNetworkCapCfg.RncId parameters,
and the UltraFlashCsfbCapCfg option of the
UtranNetworkCapCfg.NetworkCapCfg parameter. If ultra-flash CSFB is not
configured for a given operator or RNC, ultra-flash CSFB is supported by
default.
8.2.1 Benefits
This function shortens the delay of CSFB to UTRAN by approximately 0.5s to 1.5s,
improving user experience.
8.2.2 Impacts
Network Impacts
None
Function Impacts
None
8.3 Requirements
8.3.1 Licenses

eRAN

Name
FDD LOFD-070202 Ultra-Flash LT1SUFCSFB0 per RRC Connected

CSFB to 0 User
UTRAN
8.3.2 Software

TDD the
Switch parameter

None
8.3.3 Hardware
8.3.4 Others
This function requires the following conditions to be met: The eNodeB, RNC, MME,
and MSC are provided by Huawei, the MME and MSC software versions are 11.0
or later, and a proportion of UEs support SRVCC from E-UTRAN to UTRAN.
This function is a Huawei-proprietary function and is incompatible with equipment

provided by other vendors. This function is triggered by the eNodeB. To prevent
fallback failures, ultra-flash CSFB to UTRAN must be activated first on the RNC,
MME, and MSC before it is activated on the eNodeB.
8.4.1 Data Configuration (FDD)

eRAN

Table 8-1 and Table 8-2 describe the parameters used for function activation and
optimization, respectively.

Name
Handover ENodeBAlgoS UtranUltraFl Select this option.

Algo switch witch.HoAlgo ashCsfbSwitc
Switch h

Name
Ue GlobalProcS UltraFlashCsf Select this option if some UEs

Compatibility witch.UeCom bComOptSw on the network do not support
Switch patSwitch ultra-flash CSFB to UTRAN.
When this option is selected,
the eNodeB performs ultra-
flash CSFB on UEs in the
international mobile
equipment identity (IMEI)
whitelist for ultra-flash CSFB if
the MME provided by Huawei
allows for IMEI whitelist
configurations for ultra-flash
CSFB. Therefore, you must
delete all UEs that do not
support ultra-flash CSFB from
this whitelist before selecting
this option. If these UEs are
not deleted from the whitelist,
keep the option unselected.
Multi- ENodeBAlgoS UtranSepOp If some operators or RNCs do

Operator witch.MultiO MobilitySwit not support ultra-flash CSFB
Control pCtrlSwitch ch to UTRAN, this option needs
Switch to be selected.

eRAN

Name
Mobile UtranNetwor None If the neighboring cell is

country code kCapCfg.Mcc working in RAN sharing mode,
set this parameter to the MCC
MO of the peer RNC.
Mobile UtranNetwor None If the neighboring cell is

network code kCapCfg.Mnc working in RAN sharing mode,
set this parameter to the MNC
MO of the peer RNC.
RNC ID UtranNetwor None If the peer UTRAN equipment

kCapCfg.RncI is provided by Huawei, set this
d parameter to the same value
MO of the peer RNC.
Network UtranNetwor UltraFlashCsf Select this option for operators

Capability kCapCfg.Net bCapCfg or RNCs that support ultra-
Configuration workCapCfg flash CSFB to UTRAN.
Handover CellHoParaCf UFCsfbBlind After the blind handover

Mode switch g.HoModeSw HoDisSwitch function for a cell takes effect,
itch select this option if you want
to disable blind handover and
enable measurement-based
handover for UEs supporting
ultra-flash CSFB.
If this option is deselected, the
blind handover function still
takes effect for UEs supporting
ultra-flash CSFB in the cell
where the blind handover
function has taken effect.

eRAN

//Enabling ultra-flash CSFB to UTRAN
MOD ENODEBALGOSWITCH: HoAlgoSwitch= UtranUltraFlashCsfbSwitch-1;

//(Optional) If there is a risk of UE compatibility issues after ultra-flash CSFB to UTRAN is enabled, run the
following command:
MOD GLOBALPROCSWITCH: UeCompatSwitch=UltraFlashCsfbComOptSw-1;
//(Optional, for FDD only) If some operators or RNCs do not support ultra-flash CSFB to UTRAN, run the
following commands:
ADD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0, NetworkCapCfg= UltraFlashCsfbCapCfg-0;
MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch=UtranSepOpMobilitySwitch-1;
//(Optional) If you want to disable blind handover and enable measurement-based handover for UEs
supporting ultra-flash CSFB after the blind handover function takes effect, run the following command:
MOD CELLHOPARACFG: LocalCellId=0,HoModeSwitch=UFCsfbBlindHoDisSwitch-1;

conditions.
//Deactivating ultra-flash CSFB to UTRAN
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranUltraFlashCsfbSwitch-0;

For detailed operations, see Feature Configuration Using the MAE-Deployment.

Check the Handover Required message sent from the eNodeB to the MME over
the S1 interface. If this message contains the handover request cause value "cs-
fallback-triggered" and also contains "sRVCCHOIndication-pSandCS", an ultra-
flash CSFB to UTRAN procedure has been successfully triggered.
Counter Observation
Table 8-3 lists the performance counter used for verifying whether this function
has taken effect.
Table 8-3 Related counters

1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut

eRAN

Table 8-4 lists the performance counters related to this function.

1526730146 L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut
1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut
1526730148 L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOu
t
1526736728 L.IRATHO.CSFB.SRVCC.E2W.MMEAbnor
mRsp
Execution success rate of handovers for ultra-flash CSFB to UTRAN =

(L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut –
L.IRATHO.CSFB.SRVCC.E2W.MMEAbnormRsp)/
L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut

eRAN
CS Fallback Feature Parameter Description 9 Ultra-Flash CSFB to GERAN
9 Ultra-Flash CSFB to GERAN
9.1 Principles
The GeranUltraFlashCsfbSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable ultra-
flash CSFB to GERAN. Use this function in areas where GSM and LTE coverage
areas overlap if the following conditions are met: The eNodeB, BSC, MME, and
MSC are provided by Huawei, and a proportion of UEs support SRVCC from E-
UTRAN to GERAN.
This function works when external GERAN cells support ultra-flash CSFB to
GERAN.
● If all external GERAN cells support ultra-flash CSFB to GERAN, no
configuration on the eNodeB is required.
● If some external GERAN cells do not support ultra-flash CSFB to GERAN, set
the GeranExternalCell.UltraFlashCsfbInd parameter to BOOLEAN_FALSE for
these external GERAN cells.
This function has the following enhancements to CSFB to GERAN:

● The function of disabling blind handling is added to blind/measurement-
based handling selection. For details, see 9.1.1 Blind/Measurement-based
Handling Selection.
● The eNodeB can select SRVCC as the CSFB policy to hand over the UE to the
GERAN using an SRVCC procedure. The procedure has CS resources on the
GERAN prepared in advance and omits certain protocol-defined signaling
procedures during access to the GERAN. For details, see 9.1.2 CSFB Policy
Selection. As for the signaling procedure of this function, see 19.1.5 Ultra-
Flash CSFB to UTRAN.
● The following enhancements have been added to the execution phase:
– The UE quickly returns to the LTE network after completing the voice
service.
– The UE performs measurements in consecutive sections of sleep time in
DRX to accelerate the measurements and decrease the delay.
For details, see 9.1.3 Execution.

eRAN

The blind/measurement-based handling selection for ultra-flash CSFB to GERAN
includes a function for disabling blind handling, which is not included in regular
CSFB to GERAN. This function is the same as the corresponding function for ultra-
flash CSFB to UTRAN. For details, see 8.1.1 Blind/Measurement-based Handling
Selection.

Ultra-flash CSFB to GERAN uses the SRVCC procedure. Figure 9-1 illustrates the
policy selection procedure.
Figure 9-1 EUTRAN-to-GERAN ultra-flash CSFB policy selection procedure

eRAN
Ultra-flash CSFB to GERAN is controlled by the GeranUltraFlashCsfbSwitch

option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter. Other parameter
settings for ultra-flash CSFB to GERAN are consistent with those for CSFB to
GERAN described in 5.1.2 CSFB Policy Selection.
If a UE does not support ultra-flash CSFB, there will be UE compatibility issues. To
address the issues, select the UltraFlashCsfbComOptSw option of the
GlobalProcSwitch.UeCompatSwitch parameter. When the
UltraFlashCsfbComOptSw option is selected, the eNodeB supports ultra-flash
CSFB only after it receives the bitSrvccBasedEcsfbOperationPossible IE from the
MME through a Huawei proprietary message.
If operators' network capabilities for ultra-flash CSFB to GERAN are different in
RAN sharing scenarios, the Separate Mobility Policies to GERAN for Multi PLMN
function can be enabled to specify whether to use ultra-flash CSFB to GERAN for a
particular operator. For details on how to activate this function, see Mobility
Management in Connected Mode.
● The Separate Mobility Policies to GERAN for Multi PLMN function is
controlled by the GeranSepOpMobilitySwitch option of the
CellAlgoSwitch.HoAllowedSwitch parameter.
● The ultra-flash CSFB capability of operators for Separate Mobility Policies to
GERAN for Multi PLMN is controlled by the GeranNetworkCapCfg.Mcc,
GeranNetworkCapCfg.Mnc, and GeranNetworkCapCfg.Lac parameters, and
the UltraFlashCsfbCapCfg option of the
GeranNetworkCapCfg.NetworkCapCfg parameter. If ultra-flash CSFB is not
configured for a given operator or neighboring GERAN cell, ultra-flash CSFB is
supported by default.
9.1.3 Execution
Compared with CSFB to GERAN, this function has the following enhancements:
● Fast Return to LTE
If the Fast Return to LTE feature is enabled on the GERAN side, the UE can
quickly return to the E-UTRAN when it completes the voice service on the
GERAN. For this purpose, the Channel Release message must contain E-UTRA
frequency information, which the UE uses to select a suitable E-UTRAN cell to
camp on.
When the IratMeasCfgTransSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter is selected, the eNodeB
filters E-UTRA frequencies supported by the UE to obtain a frequency set.
During the SRVCC procedure, the eNodeB sends the target BSC a Handover
Required message containing the frequency set, which serves as a reference
for the fast return procedure.
● Measurement acceleration
If the CellDrxPara.DrxForMeasSwitch parameter is set to ON, the eNodeB
delivers the DRX and gap-assisted measurement configurations in a certain
scenario. The UE performs measurements preferentially in consecutive
sections of sleep time in DRX to accelerate the measurements and decrease
the delay. In that specific scenario, all the following conditions must be met:
– The UE cannot autonomously perform gap-assisted measurements. In
this case, the AutoGapSwitch option of the

eRAN
ENodeBAlgoSwitch.HoModeSwitch parameter is deselected or the

interRAT-NeedForGaps IE for the GERAN frequency is TRUE in the UE
capability message.
– The UE supports DRX.
– The BlindHoSwitch option of at least one of the
ENodeBAlgoSwitch.HoModeSwitch and CellHoParaCfg.HoModeSwitch
parameters is deselected.
For details about how to configure measurement-specific DRX parameters,
see DRX and Signaling Control.
9.2.1 Benefits
This function shortens the delay of CSFB to GERAN by approximately 0.5s to 1.5s,
improving user experience.
9.2.2 Impacts
Network Impacts
When DRX is used for measurements, there is a higher probability that UEs enter
sleep time. This affects scheduling and therefore decreases cell throughput.
Function Impacts
None
9.3 Requirements
9.3.1 Licenses

Name
FDD LOFD-081283 Ultra-Flash LT1SUFCSFB2 per RRC Connected

CSFB to 0 User
GERAN
9.3.2 Software

eRAN

TDD the
Switch parameter

None
9.3.3 Hardware
9.3.4 Others
This function requires that the eNodeB, BSC, MME, and MSC all be provided by
Huawei, they support ultra-flash CSFB to GERAN, and the MME and MSC software
versions be 11.0 or later.
This function is incompatible with equipment provided by other vendors. This

function is triggered by the eNodeB. To prevent fallback failures, ultra-flash CSFB
to GERAN must be activated first on the BSC, MME, and MSC before it is activated
on the eNodeB.

Table 9-1 and Table 9-2 describe the parameters used for function activation and
optimization, respectively.

Name
Handover ENodeBAlgoS GeranUltraFl Select this option.

Algo switch witch.HoAlgo ashCsfbSwitc
Switch h

eRAN

Name
Ultra-Flash GeranExterna None Set this parameter to

CSFB lCell.UltraFla BOOLEAN_FALSE for external
Capability shCsfbInd GERAN cells that do not
Indication support ultra-flash CSFB to
GERAN.
Handover CellAlgoSwit GeranSepOp If some operators or

Allowed ch.HoAllowe MobilitySwit neighboring GERAN cells do
Switch dSwitch ch not support ultra-flash CSFB
to GERAN, this option needs
to be selected.
Mobile GeranNetwor None This parameter specifies the

country code kCapCfg.Mcc MCC of the base station that
serves the neighboring cell.
If the peer GERAN equipment
parameter in the GCELL MO
of the peer BSC.
Mobile GeranNetwor None This parameter specifies the

network code kCapCfg.Mnc MNC of the base station that
serves the neighboring cell.
If the peer GERAN equipment
parameter in the GCELL MO
of the peer BSC.
Location Area GeranNetwor None This parameter specifies the

Code kCapCfg.Lac location area code (LAC) of
the GERAN cell. If the peer
GERAN equipment is provided
by Huawei, set this parameter
to the same value as the
corresponding parameter in
the GCELL MO of the peer
BSC.
Network GeranNetwor UltraFlashCsf Deselect this option for

Capability kCapCfg.Net bCapCfg operators or neighboring
Configuration workCapCfg GERAN cells that do not
support ultra-flash CSFB to
GERAN. This option is selected
by default.

eRAN

Name
Ue GlobalProcS UltraFlashCsf Select this option if some UEs

Compatibility witch.UeCom bComOptSw on the network do not support
Switch patSwitch ultra-flash CSFB.
When this option is selected,
the eNodeB performs ultra-
flash CSFB on UEs in the
international mobile
equipment identity (IMEI)
whitelist for ultra-flash CSFB if
the MME provided by Huawei
allows for IMEI whitelist
configurations for ultra-flash
CSFB. Therefore, you must
delete all UEs that do not
support ultra-flash CSFB from
this whitelist before selecting
this option. If these UEs are
not deleted from the whitelist,
keep the option unselected.

Name
DRX for CellDrxPara.DrxForMeasSwit When the network uses

Measurement ch measurement-based handling
Switch and UEs support DRX
measurements well, turning
on the switch can reduce
measurement delays
significantly. However, the
throughput of services
decreases because of the
measurements.
Long DRX CellDrxPara.LongDrxCycleFor Set this parameter to its

Cycle for Meas recommended value.
Measurement
On Duration CellDrxPara.OnDurTimerFor Set this parameter to its

Timer for Meas recommended value.
Measurement
DRX Inactivity CellDrxPara.DrxInactTimerFo Set this parameter to its

Timer for rMeas recommended value.
Measurement

eRAN

Name
DRX CellDrxPara.DrxReTxTimerFo Set this parameter to its

Retransmissio rMeas recommended value.
n Timer for
Measurement
Short DRX CellDrxPara.ShortDrxSwForM Set this parameter to its

Switch for eas recommended value.
Measurement
Short DRX CellDrxPara.ShortDrxCycleFo Set this parameter to its

Cycle for rMeas recommended value.
Measurement
Short Cycle CellDrxPara.ShortCycleTimer Set this parameter to its

Timer for ForMeas recommended value.
Measurement
Handover CellHoParaCfg.HoModeSwitc After the blind handover

Mode switch h function takes effect in a cell,
select the
UFCsfbBlindHoDisSwitch
option if you want to disable
blind handovers and enable
measurement-based
handovers for UEs supporting
ultra-flash CSFB in this cell.

//Enabling ultra-flash CSFB to GERAN
MOD ENODEBALGOSWITCH: HoAlgoSwitch= GeranUltraFlashCsfbSwitch-1;

//(Optional) Enabling optimization of fast return from GERAN to E-UTRAN after ultra-flash CSFB to GERAN
based on UEs' LTE frequency capabilities. With the optimization, during SRVCC procedures, the eNodeB
sends the information of the LTE frequencies that a UE can measure to the BSC.
MOD GLOBALPROCSWITCH: ProtocolMsgOptSwitch=IratMeasCfgTransSwitch-1;
//(Optional) If some external GERAN cells do not support ultra-flash CSFB to GERAN, run the following
command:
MOD GERANEXTERNALCELL: Mcc="302", Mnc="220", GeranCellId=2, Lac=12,
UltraFlashCsfbInd=BOOLEAN_TRUE;
//(Optional) If UEs support DRX-based measurements, run the following command:
MOD CELLDRXPARA: LocalCellId=0, DrxForMeasSwitch=ON, LongDrxCycleForMeas=SF160,
OnDurTimerForMeas=PSF2, DrxInactTimerForMeas=PSF2, DrxReTxTimerForMeas=PSF4,
ShortDrxSwForMeas=ON, ShortDrxCycleForMeas=SF20, ShortCycleTimerForMeas=1;
//(Optional) If some operators or neighboring GERAN cells do not support ultra-flash CSFB to GERAN, run

eRAN
the following commands:

ADD GERANNETWORKCAPCFG: Mcc="460", Mnc="32", Lac=1, NetworkCapCfg= UltraFlashCsfbCapCfg-0;
MOD CELLALGOSWITCH: LocalCellId=0,
HoAllowedSwitch=SrvBasedInterFreqHoSw-0&GeranSepOpMobilitySwitch-1;
//(Optional) If you want to disable blind handover and enable measurement-based handover for UEs
supporting ultra-flash CSFB after the blind handover function takes effect, run the following command:
MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch= UFCsfbBlindHoDisSwitch-1;
//(Optional) If there is a risk that UE compatibility issues arise after ultra-flash CSFB to GERAN is enabled,
run the following command:
MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;

conditions.
//Deactivating ultra-flash CSFB to GERAN
MOD ENODEBALGOSWITCH: HoAlgoSwitch= GeranUltraFlashCsfbSwitch-0;

Check the Handover Required message sent from the eNodeB to the MME over
the S1 interface. If this message contains the handover request cause value "cs-
fallback-triggered" and also contains "sRVCCHOIndication-cSonly", an ultra-flash
CSFB to GERAN procedure has been successfully triggered.
Counter Observation
The following table lists the performance counter used to verify whether this
function has taken effect.
Table 9-3 Performance counter used to verify ultra-flash CSFB to GERAN
1526733007 L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut

Table 9-4 lists the performance counters related to this function.
1526733006 L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut

eRAN
1526733007 L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut
1526733008 L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOu
t
1526733009 L.IRATHO.CSFB.SRVCC.E2G.MMEAbnor
mRsp
Execution success rate of handovers for ultra-flash CSFB to GERAN =

(L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut –
L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp)/
L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut

eRAN
CS Fallback Feature Parameter Description 10 CSFB Steering to UTRAN
10 CSFB Steering to UTRAN
10.1 Principles
The UtranCsfbSteeringSwitch option of the CellAlgoSwitch.HoAllowedSwitch
parameter specifies whether to enable this function.
This function is based on CSFB to UTRAN. It can improve network efficiency if an

operator has different requirements for target RATs, target frequencies, and CSFB
policies for CS-only services and CS+PS services. If the operator owns both UTRAN
and GERAN networks and preferential measurement of only UTRAN is required,
CSFB steering to UTRAN and CSFB steering to GERAN must be both activated.
There are two types of CSFB UEs based on their status:

● RRC_IDLE CSFB UEs
If the MME uses an INITIAL CONTEXT SETUP REQUEST message to send the
CS Fallback Indicator to the eNodeB, the eNodeB determines that the UE is in
idle mode at the time when the UE initiates the CS service. This UE is called
an RRC_IDLE CSFB UE.
● RRC_CONNECTED CSFB UEs
If the MME uses a UE CONTEXT MODIFICATION REQUEST message to send
the CS Fallback Indicator to the eNodeB, the eNodeB determines that the UE
is performing PS services at the time when the UE initiates the CS service. This
UE is called an RRC_CONNECTED CSFB UE.
This function allows for flexible parameter settings for the two types of CSFB UEs.
NOTE
For a UE initiating an emergency call, the eNodeB preferentially selects RATs that support
LCS and then selects a RAT from them based on the configured RAT priorities.
Target RAT Configuration

If a UE is an RRC_IDLE CSFB UE, the eNodeB selects a target RAT for the UE based
on the RAT priorities specified by the parameters in Table 10-1.

eRAN
Table 10-1 Target RAT priority parameter list for RRC_IDLE CSFB UEs
Target RAT eNodeB-Level Parameter Cell-Level Parameter

Priority
Highest CSFallBackBlind- CellOpHoCfg.IdleCsfbHighest-

HoCfg.IdleCsfbHighestPri Pri
Second CSFallBackBlind- CellOpHoCfg.IdleCsfbSecondP
highest HoCfg.IdleCsfbSecondPri ri
Lowest CSFallBackBlind- CellOpHoCfg.IdleCsfbLowestP
HoCfg.IdleCsfbLowestPri ri
If a UE is an RRC_CONNECTED CSFB UE, the eNodeB selects a target RAT for the
UE based on the RAT priorities specified by the parameters in Table 10-2.
Table 10-2 Target RAT priority parameter list for RRC_CONNECTED CSFB UEs
Target RAT eNodeB-Level Parameter Cell-Level Parameter

Priority
Highest CSFallBackBlind- CellOpHoCfg.InterRatHighest-

HoCfg.InterRatHighestPri Pri
Second highest CSFallBackBlind- CellOpHoCfg.InterRatSecondP
HoCfg.InterRatSecondPri ri
Lowest CSFallBackBlind- CellOpHoCfg.InterRatLowestPr
HoCfg.InterRatLowestPri i
NOTE
● Parameters in the CSFallBackBlindHoCfg MO are eNodeB-level parameters. When you

run the ADD CNoperator command with CnOperatorId specified to add an operator,
parameters in the CSFallBackBlindHoCfg MO are automatically set to their default
values. Cell-level operator-specific parameters for inter-RAT handovers are set by
running the ADD CELLOPHOCFG command. When both the CSFallBackBlindHoCfg
and CellOpHoCfg MOs are configured, the CellOpHoCfg MO configuration prevails.
● If CSFB with LAI is enabled, the eNodeB preferentially selects the frequency of inter-RAT
cells with the same PLMN ID as that contained in the LAI. When the eNodeB determines
the RAT priority, it considers whether only one of or both of CSFB with LAI to GERAN
and CSFB with LAI to UTRAN are enabled. If, for example, only CSFB with LAI to GERAN
is enabled, the eNodeB preferentially selects a GERAN cell or frequency. If both of CSFB
with LAI to GERAN and CSFB with LAI to UTRAN are enabled, the eNodeB selects the
target cell or frequency based on the RAT priorities configured using the parameters in
the preceding tables.
Target Frequency Configuration

The eNodeB can select a neighboring cell or frequency of a lower-priority RAT
only if no neighboring cell or frequency of a higher-priority RAT can be selected.

eRAN
For RRC_IDLE CSFB UEs, if UTRAN is assigned the highest RAT priority, the eNodeB
selects target frequencies based on the setting of the UtranNFreq.CsPriority
parameter.
For RRC_CONNECTED CSFB UEs, if UTRAN is assigned the highest RAT priority, the
eNodeB selects target frequencies based on the setting of the
UtranNFreq.CsPsMixedPriority parameter.
CSFB Policy Configuration

The CSFB policy for RRC_IDLE CSFB UEs is specified by the
The CSFB policy for RRC_CONNECTED CSFB UEs is specified by the

10.2.1 Benefits
This function allows operators that own inter-RAT networks to specify the target
RAT and frequency for CSFB based on the network plan and network load
balancing requirements to improve network operating efficiency.
10.2.2 Impacts
Network Impacts
If a high- or medium-priority frequency is configured inappropriately, for example,
if the frequency has coverage holes, a UE may fail to measure this frequency and
therefore the CSFB delay increases.
This function may conflict with the service-based directed retry decision (DRD)
algorithm used for UTRAN, affecting user experience. For example, if a CS service
is initiated for a UE that is performing PS services, the eNodeB may select a High
Speed Packet Access (HSPA) frequency used in UTRAN for CSFB based on
configured policies. However, if the UE requests CS bearer establishment first after
the fallback, the UTRAN may further transfer the UE to an R99 frequency.
Function Impacts
None
10.3 Requirements
10.3.1 Licenses

eRAN

Name
FDD LOFD-001088 CS Fallback LT1S0CFBSU00 per RRC

Steering to Connected
UTRAN User
10.3.2 Software
Name Switch
FDD CSFB to UtranCsfbSwi CS None

TDD UTRAN tch option of Fallback
the
CellAlgoSwit
ch.HoAllowe
dSwitch
parameter
FDD Coverage UtranFreqLay CS This function is required if

TDD -based erMeasSwitc Fallback you plan to configure service
E-UTRAN h option of priorities of target
to the frequencies based on UE
UTRAN CellAlgoSwit status.
CS/PS ch.FreqLayer
steering Switch
parameter

None
10.3.3 Hardware
10.3.4 Others
Collect information about the frequencies and frequency policies of the UTRAN.
The frequency policies for UTRAN and E-UTRAN must be the same. If a frequency,
for example F1, is the preferred frequency for voice services on the UTRAN, F1
must be set as the preferred frequency for CSFB on the E-UTRAN side.

eRAN
If CSFB steering to GERAN is also to be activated, the frequency policies for

UTRAN and GERAN must also be the same.


Name
Handover CellAlgoSwit UtranCsfbSte Select this option.

Allowed ch.HoAllowe eringSwitch
Switch dSwitch

Name

Highest CSFallBackBlind- Set this parameter based on

priority HoCfg.InterRatHighestPri the network plan.
InterRat
Second CSFallBackBlind- Set this parameter based on

priority HoCfg.InterRatSecondPri the network plan.
priority RAT.
Lowest CSFallBackBlind- Set this parameter based on

priority HoCfg.InterRatLowestPri the network plan.
UTRAN LCS CSFallBackBlind- Set this parameter based on

capability HoCfg.UtranLcsCap the network plan.

eRAN

Name
CSFB Highest CSFallBackBlind- Set this parameter based on

priority HoCfg.IdleCsfbHighestPri the network plan.
InterRat for
Idle UE
CSFB Second CSFallBackBlind- Set this parameter based on

priority HoCfg.IdleCsfbSecondPri the network plan.
InterRat for Ensure that the second-
Idle UE highest-priority RAT is
priority RAT.
CSFB Lowest CSFallBackBlind- Set this parameter based on

priority HoCfg.IdleCsfbLowestPri the network plan.
InterRat for Ensure that the lowest-priority
Idle UE RAT is different from the

Name
CN Operator CellOpHoCfg.CnOperatorId Set this parameter based on

ID the network plan.

the network plan.
Highest CellOpHoCfg.InterRatHighes Set this parameter based on

Priority tPri the network plan.
InterRAT
Second CellOpHoCfg.InterRatSecond Set this parameter based on

Priority Pri the network plan.
InterRAT Ensure that the second-
priority RAT.

eRAN

Name
Lowest CellOpHoCfg.InterRatLowest Set this parameter based on

InterRAT Ensure that the lowest-priority
CSFB Highest CellOpHoCfg.IdleCsfbHighest Set this parameter based on

InterRAT for
Idle UE
CSFB Second CellOpHoCfg.IdleCsfbSecond Set this parameter based on

InterRAT for Ensure that the second-
priority RAT.
CSFB Lowest CellOpHoCfg.IdleCsfbLowest Set this parameter based on

InterRAT for Ensure that the lowest-priority
Table 10-6 Related parameters in the UtranNFreq MO

Name
CS service UtranNFreq.CsPriority Set these parameters based on

priority the network plan.
CS and PS UtranNFreq.CsPsMixedPriori- Set a high priority for a

mixed priority ty UTRAN frequency with good
coverage.

eRAN
Table 10-7 Related parameters in the CSFallBackPolicyCfg MO

Name
CSFB CSFallBackPolicyCfg.CsfbHoP Set this parameter based on

handover olicyCfg the network plan.
policy
Configuration
CSFB CSFallBackPolicyCfg.IdleMod Set this parameter based on

handover eCsfbHoPolicyCfg the network plan.
policy
Configuration
for idle ue

● Scenario 1: The UTRAN and GERAN cover the same area and both provide
contiguous coverage.
HoAllowedSwitch=UtranCsfbSteeringSwitch-1&GeranCsfbSteeringSwitch-1;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN,
IdleCsfbHighestPri=GERAN, IdleCsfbSecondPri=UTRAN;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-1,
IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;
● Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN
provides contiguous coverage but the UTRAN does not.
MOD GERANNCELL:LocalCellId=1, Mcc="460", Mnc="20", Lac=12, GeranCellId=16, BlindHoPriority=32;
HoAllowedSwitch=UtranCsfbSwitch-1&GeranCsfbSwitch-1&UtranCsfbSteeringSwitch-1&GeranCsfbSteeringS
witch-1;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN,
IdleCsfbHighestPri=UTRAN, IdleCsfbSecondPri=GERAN;

conditions.
//Deactivating CSFB steering to UTRAN
MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch=UtranCsfbSteeringSwitch-0;


eRAN

The signaling procedure for this function is the same as that for CSFB to UTRAN.
After this function is enabled, check whether it has taken effect.
1. Check that the UE supports redirection and PS handover.
2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection
and handover, respectively.
3. Enable the UE to initiate a voice call in idle mode and a voice call in
connected mode.
4. Observe the counters L.CSFB.E2W, L.RRCRedirection.E2W.CSFB, and
L.IRATHO.E2W.CSFB.ExecAttOut. If the values of the counters increase by 2,
1, and 1, respectively, CSFB steering to UTRAN has taken effect.
If CSFB steering to GERAN is also enabled, the activation verification procedure is
as follows:
1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.
2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs,
and set UTRAN as the highest-priority RAT for CSFB triggered for
RRC_CONNECTED UEs.
connected mode.
4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If the values of both
counters increase by 1, both CSFB steering to UTRAN and CSFB steering to
GERAN have taken effect.

You can review network logs to observe delivered frequencies and target RATs for
CSFB.

eRAN
CS Fallback Feature Parameter Description 11 CSFB Steering to GERAN
11 CSFB Steering to GERAN
11.1 Principles
The GeranCsfbSteeringSwitch option of the CellAlgoSwitch.HoAllowedSwitch
parameter specifies whether to enable this function.
The principles for this function are the same as those for CSFB steering to UTRAN
except that this function does not support target frequency configuration based
on UE status. For details on the principles, see 10.1 Principles.
11.2.1 Benefits
This function allows operators that own inter-RAT networks to specify the target
RAT and frequency for CSFB based on the network plan and network load
balancing requirements to improve network operating efficiency.
11.2.2 Impacts
Network Impacts
If a high- or medium-priority frequency is configured inappropriately, for example,
if the frequency has coverage holes, a UE may fail to measure this frequency and
therefore the CSFB delay increases.
Function Impacts
None
11.3 Requirements

eRAN
11.3.1 Licenses

Name
FDD LOFD-001089 CS Fallback LT1S0CFBSG00 per RRC

Steering to Connected
GERAN User
11.3.2 Software

TDD the
Switch parameter

None
11.3.3 Hardware
11.3.4 Others
Collect information about the frequencies and frequency policies of the GERAN.
The frequency policies for GERAN and E-UTRAN must be the same. If a frequency,
for example F1, is the preferred frequency for voice services on the GERAN, F1
must be set as the preferred frequency for CSFB on the E-UTRAN side.
If CSFB steering to UTRAN is also to be activated, the frequency policies for

UTRAN and GERAN must also be the same.

eRAN


Name
Handover CellAlgoSwit GeranCsfbSte Select this option.

Allowed ch.HoAllowe eringSwitch
Switch dSwitch

Name

Highest CSFallBackBlind- Set this parameter based on

priority HoCfg.InterRatHighestPri the network plan.
InterRat
Second CSFallBackBlind- Set this parameter based on

priority HoCfg.InterRatSecondPri the network plan.
priority RAT.
Lowest CSFallBackBlind- Set this parameter based on

priority HoCfg.InterRatLowestPri the network plan.
GERAN LCS CSFallBackBlind- Set this parameter based on

capability HoCfg.GeranLcsCap the network plan.
CSFB Highest CSFallBackBlind- Set this parameter based on

priority HoCfg.IdleCsfbHighestPri the network plan.
InterRat for
Idle UE

eRAN

Name
CSFB Second CSFallBackBlind- Set this parameter based on

priority HoCfg.IdleCsfbSecondPri the network plan.
InterRat for Ensure that the second-
priority RAT.
CSFB Lowest CSFallBackBlind- Set this parameter based on

priority HoCfg.IdleCsfbLowestPri the network plan.
InterRat for Ensure that the lowest-priority
Table 11-3 Related parameters in the CSFallBackPolicyCfg MO

Name
CSFB CSFallBackPolicyCfg.CsfbHoP Set this parameter based on

handover olicyCfg UE capabilities and network
policy capabilities.
Configuration
CSFB CSFallBackPolicyCfg.IdleMod Set this parameter based on

handover eCsfbHoPolicyCfg UE capabilities and network
policy capabilities.
Configuration
for idle ue

MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch=GeranCsfbSteeringSwitch-1;
MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0,
InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GERAN,IdleCsfbSecondPri=UTRAN;

eRAN

conditions.
//Deactivating CSFB steering to GERAN
MOD CELLALGOSWITCH: LocalCellId=0,HoAllowedSwitch=GeranCsfbSteeringSwitch-0;


The signaling procedure for this function is the same as that for CSFB to GERAN.
1. Check that the UE supports redirection-based CSFB and handover-based CSFB.
2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection
and handover, respectively.
connected mode.
4. Observe the counters L.CSFB.E2G, L.RRCRedirection.E2G.CSFB, and
L.IRATHO.E2G.CSFB.ExecAttOut. If the values of the counters increase by 2,
1, and 1, respectively, CSFB steering to GERAN has taken effect.
If CSFB steering to UTRAN is also enabled, the activation verification procedure is
as follows:
1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.
2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs,
and set UTRAN as the highest-priority RAT for CSFB triggered for
RRC_CONNECTED UEs.
connected mode.
4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If the values of both
counters increase by 1, both CSFB steering to UTRAN and CSFB steering to
GERAN have taken effect.

You can review network logs to observe delivered frequencies and target RATs for
CSFB.

eRAN 12 Coverage-based E-UTRAN to UTRAN CS/PS
CS Fallback Feature Parameter Description Steering
12 Coverage-based E-UTRAN to UTRAN

CS/PS Steering
12.1 Principles
This chapter describes the CS service steering function in coverage-based E-UTRAN
to UTRAN CS/PS steering. For details on the PS service steering function, see
This function can be used when service steering is required in a UTRAN with
multiple UTRAN frequencies. By setting CS service priorities for UTRAN
frequencies, the operator can ensure that UEs fall back to the UTRAN frequencies
that have the highest CS service priority.
CS Steering in CSFB
This function has the following enhancements to CSFB to UTRAN:
● Frequencies with the highest CS service priority are selected for inter-RAT
measurement on the UTRAN.
This selection is controlled by the UtranFreqLayerMeasSwitch option of the
cell-level parameter CellAlgoSwitch.FreqLayerSwitch.
If this option is selected, the eNodeB selects frequencies with the highest CS
service priority, which is specified by the UtranNFreq.CsPriority parameter,
for measurement. A larger value of this parameter indicates a higher priority.
If this parameter is set to Priority_0 for a frequency, the eNodeB does not
select this frequency for measurement.
● Cells on the frequencies with the highest CS service priority are selected as
the target cells for blind handling.
This selection is controlled by the UtranFreqLayerBlindSwitch option of the
cell-level parameter CellAlgoSwitch.FreqLayerSwitch.
If this option is selected, the eNodeB selects a frequency with the highest
UtranNFreq.CsPriority parameter value or a cell on the frequency for blind
handling. A larger value of this parameter indicates a higher priority. If this
parameter is set to Priority_0 for a frequency, this frequency is not involved in
frequency prioritization.

LAI-based CS Steering in CSFB

Target selection is enhanced when CSFB with LAI to UTRAN is enabled. The
enhancements are as follows:
● Enhancement in measurement
a. The eNodeB selects inter-RAT frequencies where there are neighboring
cells whose PLMN IDs are the same as the PLMN ID in the LAI.
b. The eNodeB selects the frequencies with the highest CS service priority,
which is specified by the UtranNFreq.CsPriority parameter, from the
previously selected frequencies.
The difference is that the eNodeB additionally sorts neighboring cells in the
following order after receiving measurement reports from the UE:
a. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
b. Neighboring cells with PLMN IDs the same as that in the LAI but LACs
different from that in the LAI
c. Neighboring cells with PLMN IDs the same as the serving PLMN ID of the
UE
● Enhancement in blind handling
a. The eNodeB selects frequencies whose PLMN ID is the same as the PLMN
ID in the LAI.
b. The eNodeB selects the frequencies with the highest CS service priority,
which is specified by the UtranNFreq.CsPriority parameter, from the
previously selected frequencies.
c. The eNodeB selects a neighboring cell whose LAC is the same as that in
the LAI.
d. If such a neighboring cell is unavailable, the eNodeB selects a
neighboring cell whose LAC is different from that in the LAI.
12.2.1 Benefits
E-UTRAN to UTRAN CS steering enables an eNodeB to include only UTRAN
frequencies with the highest CS service priority in measurement configurations.
This prevents redundant measurements, reduces the measurement time, and
decreases end-to-end CSFB delay.
Consistent settings of the CS service priorities for UTRAN frequencies between the
E-UTRAN and the UTRAN help prevent further handovers for service steering after
CSFB.
12.2.2 Impacts
Network Impacts
None

Function Impacts
None
12.3 Requirements
12.3.1 Licenses

Name
FDD LOFD-001078 E-UTRAN to LT1SEUCSPS0 per RRC Connected

UTRAN 0 User
CS/PS
Steering
12.3.2 Software

TDD the
Switch parameter

None
12.3.3 Hardware
12.3.4 Others
Collect information about the operating frequencies and frequency policies of the
E-UTRAN and UTRAN. The frequency policies must be the same for UTRAN and E-
UTRAN. If a frequency, for example F1, is the preferred frequency for voice services

on the UTRAN, F1 must be set as the preferred frequency for CSFB on the E-
UTRAN side.


Name
Frequency CellAlgoSwit ● UtranFreq ● To enable measurement-

Layer Switch ch.FreqLayer LayerMeas based E-UTRAN to UTRAN
Switch Switch CS steering, select the
● UtranFreq UtranFreqLayerMeasS-
LayerBlind witch option.
Switch ● To enable blind E-UTRAN
to UTRAN CS steering,
select the
UtranFreqLayerBlind-
Switch option.
CS service UtranNFreq.C None Set this parameter based on

priority sPriority the network plan.

Scenario 1: Blind handling
MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerBlindSwitch-1;
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10800, CsPriority=Priority_16;
Scenario 2: Measurement-based handling

MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerMeasSwitch-1;
MOD UTRANNFREQ: LocalCellId=0, UtranDlArfcn=10800, CsPriority=Priority_16;


conditions.
Scenario 1: Blind handling
MOD CELLALGOSWITCH: LocalCellId=0,FreqLayerSwitch=UtranFreqLayerBlindSwitch-0;
Scenario 2: Measurement-based handling

MOD CELLALGOSWITCH: LocalCellId=0, FreqLayerSwitch=UtranFreqLayerMeasSwitch-0;


The signaling procedure for this function is the same as that for CSFB to UTRAN.
1. Verify that the UE supports CSFB and multiple UTRAN frequencies are
available.
2. Enable measurement-based and blind handover for E-UTRAN to UTRAN
CS/PS Steering. Set the highest PS service priority for UTRAN frequency F1
and the highest CS service priority for UTRAN frequency F2.
3. Enable the UE to camp on an LTE cell and initiate a voice call in the cell. The
expected result is that the UE falls back to a UTRAN cell on F2.
4. Enable the UE to camp on the LTE cell and initiate a data service. Move the
UE to the LTE cell edge. The expected result is that the UE is handed over to a
UTRAN cell on F1.

You can review network logs to observe delivered frequencies.

eRAN
CS Fallback Feature Parameter Description 13 CSFB with LAI to UTRAN
13 CSFB with LAI to UTRAN
13.1 Principles
This function is enabled when the LAI_BASED_CSFB_TO_UTRAN_SW option of
the CellAlgoExtSwitch.HoAllowedSwitch parameter is selected.
This function works in the following scenarios:
● In a multi-PLMN or national roaming scenario

An LAI consists of a PLMN ID and a location area code (LAC). The PLMN ID
identifies the CS network that a UE has registered with and will fall back to.
If the serving E-UTRAN cell has multiple neighboring UTRAN or GERAN cells
with different PLMN IDs or the serving PLMN differs from the target PLMN,
the operator can use the CSFB with LAI function so that the UE will
preferentially fall back to the PLMN indicated by the LAI.
● In a tracking area (TA) that overlaps multiple location areas (LAs)
To prevent a further LAU after CSFB, the eNodeB selects a CSFB target cell
with the same LAC as that specified for the UE during attach. Therefore, the
CSFB delay does not include the LAU time.
The eNodeB derives the LAI from an Initial Context Setup Req or UE Context Mod
Req message sent by the MME.
The eNodeB selects target frequencies or cells for measurement or blind handling
based on LAIs sent by the MME. The following describes target selection for
measurement and blind handling.
NOTE
If the LAI_BASED_CSFB_TO_UTRAN_SW or LAI_BASED_CSFB_TO_GERAN_SW option of

the CellAlgoExtSwitch.HoAllowedSwitch parameter is selected, the eNodeB selects target
frequencies or cells for measurement or blind handling only based on the LAIs sent by the
MME. In this scenario, the eNodeB does not deliver measurement configurations related to
the RAT indicated in the option that is deselected. Therefore, it is recommended that both
the LAI_BASED_CSFB_TO_UTRAN_SW and LAI_BASED_CSFB_TO_GERAN_SW options be
selected if LAI-based CSFB is used.

eRAN
Measurement
● Selecting frequencies
During measurement configuration, the eNodeB only selects inter-RAT
frequencies where there are neighboring cells whose PLMN IDs are the same
as that in the LAI that was received. The follow-up measurement procedure is
similar to that in CSFB to UTRAN.
● Selecting neighboring cells
The eNodeB selects neighboring cells in the following order after receiving
measurement reports from a UE:
a. Neighboring cells with PLMN IDs and LACs the same as those in the LAI
b. Neighboring cells with PLMN IDs the same as that in the LAI but LACs
different from that in the LAI
If no frequency or neighboring cell can be selected based on the LAI, the
process is the same as that when no LAI is received.
Blind Handling
● Selecting frequencies
If no neighboring UTRAN cell is configured, the eNodeB preferentially selects
the UTRAN frequencies whose PLMN ID is the same as that in the LAI. For
details, see 4.1.3 Target Cell/Frequency Selection.
If neighboring UTRAN cells are configured, the eNodeB preferentially selects
the operating UTRAN frequencies of the neighboring UTRAN cells whose
PLMN ID is the same as that in the LAI. The eNodeB then sorts the
frequencies based on the blind-handover priorities of the neighboring cells
and frequency priorities for RRC_CONNECTED UEs. For details, see 4.1.3
Target Cell/Frequency Selection.
● Selecting neighboring cells
The neighboring cell selection sequence is controlled by the
LaiCsfbBlindNCellSelSwitch option of the
ENodeBAlgoSwitch.HoCommOptSwitch parameter.
NOTE
When the coverage of an E-UTRAN cell is not completely included in that of a

neighboring cell with a configured blind-handover priority, you are advised to select
the option to ensure the CSFB success rate and reduce the delay.
When the option is selected, neighboring cells are selected in the following
sequence:
a. Neighboring cells with PLMN IDs the same as those in the LAI
b. Neighboring cells with the highest blind-handover priority among a
c. Neighboring cells with LACs the same as those in the LAI among b
When the option is deselected, neighboring cells are selected in the following
sequence:
a. Neighboring cells with PLMN IDs the same as those in the LAI
b. Neighboring cells with LACs the same as those in the LAI among a
c. Neighboring cells with the highest blind-handover priority among b

eRAN
13.2.1 Benefits
CSFB with LAI ensures that a UE can fall back to the CS network that the UE has
attached to. This prevents CSFB failure or long delay caused by incorrect target
RAT selection and increases the CSFB success rate.
13.2.2 Impacts
Network Impacts
None
Function Impacts
None
13.3 Requirements
13.3.1 Licenses

Name
FDD LOFD-001068 CS Fallback LT1S0CSFLU0 per RRC Connected

with LAI to 0 User
UTRAN
13.3.2 Software
None

None
13.3.3 Hardware

eRAN
13.3.4 Others
Table 13-1 describes the requirements for the core networks.
Table 13-1 Requirements of CSFB with LAI to UTRAN for core networks
MME ● Supports the SGs interface to the MSC/

VLR.
● Can select the VLR and LAI based on the
TAI of the serving cell.
● Can forward paging messages delivered
by the MSC.
● Can perform PLMN selection and
reselection.
● Supports combined EPS/IMSI attach,
combined EPS/IMSI detach, and
combined TAU/LAU.
● Can route CS signaling.
● Supports LAI delivery.
MSC ● Supports combined EPS/IMSI attach.

● Can forward paging messages over the
SGs interface.
SGSN Does not activate ISR during the combined

RAU/LAU procedure initiated by the UE.


eRAN

Name
Handover CellAlgoExtS LAI_BASED_C Select this option.

Allowed witch.HoAllo SFB_TO_UTR
Switch wedSwitch AN_SW

MOD CELLALGOEXTSWITCH: LocalCellId=0, HoAllowedSwitch=LAI_BASED_CSFB_TO_UTRAN_SW-1;

MOD CELLALGOEXTSWITCH: LocalCellId=0, HoAllowedSwitch=LAI_BASED_CSFB_TO_UTRAN_SW-0;


1. Configure two neighboring UTRAN cells with different LAIs for an E-UTRAN
cell, and enable the MME to include only one of the two LAIs in the
instructions that will be delivered to the eNodeB.
2. Ensure that the signal strengths of the two UTRAN cells both reach the
threshold for event B1. You can query the threshold by running the LST
INTERRATHOUTRANGROUP command.
3. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that
the UE falls back to the UTRAN cell with the specified LAI and completes the
call.
4. Enable the UE to camp on the E-UTRAN cell and receive a voice call so that
the UE falls back to the UTRAN cell with the specified LAI and completes the
call.
The Initial Context Setup Request or UE Context Modification Request
message carries the LAI that the MME delivers to the eNodeB, as shown in
the following figure.
Figure 13-1 LAI signaling tracing

eRAN

You can observe delivered frequencies or cells based on network logs.

eRAN
CS Fallback Feature Parameter Description 14 CSFB with LAI to GERAN
14 CSFB with LAI to GERAN
14.1 Principles
This function is enabled when the LAI_BASED_CSFB_TO_GERAN_SW option of the
CellAlgoExtSwitch.HoAllowedSwitch parameter is selected.
NOTE
If the LAI_BASED_CSFB_TO_UTRAN_SW or LAI_BASED_CSFB_TO_GERAN_SW option of

the CellAlgoExtSwitch.HoAllowedSwitch parameter is selected, the eNodeB selects target
frequencies or cells for measurement or blind handling only based on the LAIs sent by the
MME. In this scenario, the eNodeB does not deliver measurement configurations related to
the RAT indicated in the option that is deselected. Therefore, it is recommended that both
the LAI_BASED_CSFB_TO_UTRAN_SW and LAI_BASED_CSFB_TO_GERAN_SW options be
selected if LAI-based CSFB is used.
The basic principles of this function are the same as those of CSFB with LAI to
UTRAN. For details, see 13.1 Principles.
14.2.1 Benefits
CSFB with LAI ensures that a UE can fall back to the CS network that the UE has
attached to. This prevents CSFB failure or long delay caused by incorrect target
RAT selection and increases the CSFB success rate.
14.2.2 Impacts
Network Impacts
None
Function Impacts
None

eRAN
14.3 Requirements
14.3.1 Licenses

Name
FDD LOFD-001069 CS Fallback LT1S0CSFLG00 per RRC

with LAI to Connected
GERAN User
14.3.2 Software
None

None
14.3.3 Hardware
14.3.4 Others
This function has the same requirements for core networks as CSFB with LAI to
UTRAN. For details, see 13.3.4 Others.


eRAN

Name
Handover CellAlgoExtS LAI_BASED_C Select this option.

Allowed witch.HoAllo SFB_TO_GER
Switch wedSwitch AN_SW

MOD CELLALGOEXTSWITCH: LocalCellId=0, HoAllowedSwitch=LAI_BASED_CSFB_TO_GERAN_SW-1;

MOD CELLALGOEXTSWITCH: LocalCellId=0, HoAllowedSwitch=LAI_BASED_CSFB_TO_GERAN_SW-0;


1. Configure two neighboring GERAN cells with different LAIs for an E-UTRAN
cell, and enable the MME to include only one of the two LAIs in the
instructions that will be delivered to the eNodeB.
2. Ensure that the signal strengths of the two GERAN cells both reach the
threshold for event B1. You can query the threshold by running the LST
INTERRATHOGERANGROUP command.
3. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that
the UE falls back to the GERAN cell with the specified LAI and completes the
call.
4. Enable the UE to camp on the E-UTRAN cell and receive a voice call so that
the UE falls back to the GERAN cell with the specified LAI and completes the
call.
The Initial Context Setup Request or UE Context Modification Request message
carries the LAI that the MME delivers to the eNodeB, as shown in the following
figure.

eRAN
Figure 14-1 LAI signaling tracing

You can observe delivered frequencies or cells based on network logs.

eRAN
CS Fallback Feature Parameter Description 15 Parameters
15 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
CS Fallback Feature Parameter Description 16 Counters
16 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
CS Fallback Feature Parameter Description 17 Glossary
17 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
CS Fallback Feature Parameter Description 18 Reference Documents
18 Reference Documents
1. 3GPP TS 23.272 V8.5.0

2. 3GPP TS 23.401 V9.2.0
3. 3GPP TS 36.331 V10.1.0
4. Mobility Management in Connected Mode
5. ANR Management
6. Admission and Congestion Control
7. RIM
8. LTE-CDMA2000 CS Service Interworking (FDD)
9. Terminal Awareness Differentiation
10. Flexible User Steering
11. Fast CS Fallback Based on RIM
12. Interoperability Between GSM and LTE
13. DRX and Signaling Control
14. LCS
15. Emergency Call

eRAN
CS Fallback Feature Parameter Description 19 Appendix
19 Appendix
19.1 CSFB to UTRAN
19.1.1 Combined EPS/IMSI Attach Procedure

The combined EPS/IMSI attach procedure is performed by exchanging non-access
stratum (NAS) messages. Therefore, this procedure is transparent to the eNodeBs.
After a CSFB-capable UE is powered on in the E-UTRAN, the UE initiates a
combined EPS/IMSI attach procedure, as shown in Figure 19-1.
Figure 19-1 Combined EPS/IMSI attach procedure

eRAN
NOTE
The symbols that appear in signaling procedure figures throughout this document are
explained as follows:
● An arrow denotes the transmission of a message.
● A plain box denotes a mandatory procedure.
● 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
SMS over SGs or CSFB function or both the SMS over SGs and CSFB functions
are 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.
19.1.2 CSFB Based on PS Handover

During CSFB based on PS handover, the UE is transferred from the E-UTRAN to the
UTRAN by performing a PS handover. It then initiates a CS service in the UTRAN.
CSFB Procedure for Mobile-Originated Calls

Figure 19-2 shows the procedure for CSFB to UTRAN based on PS handover for
mobile-originated calls.

eRAN
Figure 19-2 CSFB to UTRAN based on PS handover for mobile-originated calls
1. The UE sends the MME an NAS message Extended Service Request to initiate
a CS service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB
procedure. If the MME supports the LAI-related function, the MME also
delivers the LAI to the eNodeB.
3. The eNodeB determines whether to perform a blind handover based on the
UE capabilities, parameters settings, and algorithm policies.
4. The eNodeB initiates a PS handover preparation. If the preparation is
successful, the eNodeB instructs the UE to perform a handover.
NOTE
For details about how the eNodeB selects a target cell and a CSFB policy, see 4.1.3
Target Cell/Frequency Selection and 4.1.2 CSFB Policy Selection.
5. After the handover, the UE initiates a CS call establishment procedure. The
procedure may be accompanied 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, which are
performed together with step 5.
CSFB Procedure for Mobile-Terminated Calls

Figure 19-3 shows the procedure for CSFB to UTRAN based on PS handover for
mobile-terminated calls.

eRAN
Figure 19-3 CSFB to UTRAN based on PS handover for mobile-terminated calls
1. The MSC sends a Paging Request message from the CS domain to the MME
over the SGs interface. Then, either of the following occurs:
– If the UE is in idle mode, the MME sends a Paging message to the
eNodeB. Then the eNodeB sends a Paging message over the Uu interface
to inform the UE of an incoming call from the CS domain. This situation
is used as an example in the preceding figure.
– If the UE is in active mode, the MME sends the UE an NAS message to
inform the UE of an incoming call from the CS domain.
2. The UE sends an Extended Service Request message containing a CS Fallback
Indicator after receiving the paging message from the CS domain.
3. The MME instructs the eNodeB over the S1 interface to perform CSFB.
4. The subsequent steps are similar to steps 3 through 6 in the procedure for
CSFB to UTRAN based on PS handover for mobile-originated calls. The only
difference is that the UE sends a Paging Response message in the UTRAN cell.
19.1.3 CSFB Based on Redirection

During CSFB based on redirection, the eNodeB receives a CS Fallback Indicator,
and then it sends an RRC Connection Release message to release the UE. The
message contains information about a target UTRAN frequency, reducing the time
for the UE to search for a target network. After selecting the UTRAN, the UE
acquires the system information of a UTRAN cell. Then, the UE performs initial
access to the cell to initiate a CS service. For the UTRAN, the UE is an initially
accessing user.

Figure 19-4 shows the procedure for CSFB to UTRAN based on redirection for

eRAN
Figure 19-4 CSFB to UTRAN based on redirection for mobile-originated calls
a CS service.
3. The eNodeB determines whether to perform a blind redirection based on the
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-based UE context release
procedure.
NOTE
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an
LAU in the target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.

In a mobile-terminated call, the MSC sends a Paging Request message from the
CS domain to the MME over the SGs interface, and then the MME or eNodeB
initiates a paging procedure for the UE. The paging procedure is similar to that for
CSFB to UTRAN based on PS handover for mobile-terminated calls described in
19.1.2 CSFB Based on PS Handover. The subsequent steps are the same as the

eRAN
steps in the procedure for CSFB to UTRAN based on redirection for mobile-
originated calls.
19.1.4 Flash CSFB

After the eNodeB receives a CS Fallback Indicator, it sends an RRC Connection
Release message to release the UE. The message contains information about a
target UTRAN frequency, physical cell identities of target cells working on this
frequency, and system information of the target cells. In this way, the UE can
quickly access the target UTRAN without the need to perform the procedure for
acquiring system information of UTRAN cells. Then, the UE can directly initiate a
CS service in a target UTRAN cell.

Figure 19-5 shows the procedure for flash CSFB to UTRAN based on redirection
for mobile-originated calls.
Figure 19-5 Flash CSFB to UTRAN based on redirection for mobile-originated calls
a CS service.

eRAN
UTRAN frequency, cell identities of target UTRAN cells, and system

information of the target cells. Then, the eNodeB initiates an S1-based UE
context release procedure.
NOTE
Target Cell/Frequency Selection and 4.1.2 CSFB Policy Selection. The system
information of the target cell is acquired during the RIM procedure.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.

steps in the procedure for flash CSFB to UTRAN based on redirection for mobile-
originated calls.
19.1.5 Ultra-Flash CSFB to UTRAN

Figure 19-6 shows the procedure of ultra-flash CSFB to UTRAN for mobile-
originated calls. For details about the standard procedure, see chapter 6 "Mobile
Originating Call" in 3GPP TS 23.272 V10.9.0 and 3GPP TS 24.008 V11.0.0.

eRAN
Figure 19-6 Ultra-flash CSFB to UTRAN for mobile-originated calls

Figure 19-7 shows the procedure of ultra-flash CSFB to UTRAN for mobile-
terminated calls. The paging procedure is excluded from the figure. For details
about the paging procedure, see step 1 in Figure 19-3. For details about the
standard procedure, see chapter 7 "Mobile Terminating Call" in 3GPP TS 23.272
V10.9.0 and 3GPP TS 24.008 V11.0.0.

eRAN
Figure 19-7 Ultra-flash CSFB to UTRAN for mobile-terminated calls
Steps 1 to 4b: The UE initiates voice services (mobile-originated calls and mobile-
terminated calls) on the E-UTRAN. The eNodeB triggers SRVCC to UTRAN. The
MME and MSC use special handling to ensure a normal SRVCC procedure.
Step 5: The RNC receives a CSFB request and prepares CS and PS resources.
Step 6: The eNodeB receives the handover command transferred over the core
network and sends it to the UE.
Step 7: The UE is handed over to the UTRAN.
Steps 8 to 13: The UE establishes voice services on the UTRAN. Signaling is

transmitted at a speed of 13.6 kbit/s, which accelerates the transfer and reduces
delays.
As shown in the preceding figures, ultra-flash CSFB to UTRAN excludes the

following procedures:
● Authentication procedure
The UE has been authenticated in the LTE system before CSFB to UTRAN.
● Ciphering procedure

eRAN
The UE has performed ciphering as instructed during CSFB. Therefore, the

ciphering procedure is not required after the UE is handed over to the UTRAN.
● IMEI check procedure
The MME has sent the IMEI to the MSC during the preparation for CSFB. The
procedure is not required in the UTRAN after SRVCC.
● CS resource setup procedure
The UTRAN system has prepared CS resources during SRVCC and therefore
the UE does not need to reestablish the CS resource after SRVCC. The
procedure is not required in the UTRAN after SRVCC.
19.1.6 Redirection-based CSFB Optimization for UEs in Idle

Mode
After the eNodeB receives an Initial Context Setup Request message with a CS
Fallback Indicator from the MME, the eNodeB does not perform the UE capability
enquiry, Uu interface security mode, or RRC connection reconfiguration procedure
indicated by dashed lines in the following figure. If the eNodeB fails to obtain the
UE capability information before performing CSFB, the eNodeB still needs to
initiate a UE capability enquiry procedure but does not need to perform the Uu
interface security mode or RRC connection reconfiguration procedure.
Figure 19-8 Redirection-based CSFB optimization for UEs in idle mode

eRAN
19.1.7 Signaling Procedures for SMS

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

The CSFB procedure for an emergency call is the same as the CSFB procedure for a
normal mobile-originated voice service. The UE sends an RRC Connection Request
message over the Uu interface or the MME sends an Initial Context Setup Request
or UE Context Modification Request message, which contains an IE to inform the
eNodeB of the service type. Emergency calls take precedence over other services in
the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict
the cells in the handover restriction list when selecting the target cell. The eNodeB
sends the RNC a handover request with the IE CSFB high priority in the IE Source
to Target Transparent Container. This request informs the RNC that a CSFB
procedure is required for an emergency call. Upon receiving the information, the
RNC preferentially processes this call when using related algorithms such as
admission control.
If redirection is used for CSFB for emergency calls, the RRC Connection Request
message that the UE sends when accessing the UTRAN contains the indication of
a CS emergency call. The UTRAN will treat this call as a common CS emergency
call.
For details about admission and preemption of emergency calls, see Emergency
Call.
19.1.9 CSFB for LCS

After a UE initiates an LCS request, the MME performs an attach or combined
TAU/LAU procedure to inform the UE of the LCS capability of the EPS. If the EPS
does not support LCS, the UE falls back to the UTRAN to initiate LCS under the
control of the EPS. The CSFB procedure is the same as the procedure for CSFB to
UTRAN for mobile-originated calls. If the UTRAN initiates an LCS request towards
a UE camping on an E-UTRAN cell, the MSC sends an LCS indicator to the MME
over the SGs interface. Then, the MME instructs the eNodeB to perform CSFB for
the UE. The CSFB procedure is the same as the procedure for CSFB to UTRAN for
mobile-terminated calls. The UE performs the LCS service after the fallback to the
UTRAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272
V10.0.0 and LCS.

eRAN
19.2 CSFB to GERAN
19.2.1 Combined EPS/IMSI Attach Procedure

The combined EPS/IMSI attach procedure for CSFB to GERAN is the same as that
for CSFB to UTRAN. For details, see 19.1.1 Combined EPS/IMSI Attach Procedure.
19.2.2 CSFB Based on PS Handover

During CSFB based on PS handover, the UE is transferred from the E-UTRAN to the
GERAN by performing a PS handover. It then initiates a CS service in the GERAN. If
the GERAN or UE does not support dual transfer mode (DTM, in which CS and PS
services run simultaneously), the ongoing PS services of the UE are suspended
before a CS service is set up.

Figure 19-9 shows the procedure for CSFB to GERAN based on PS handover for
Figure 19-9 CSFB to GERAN based on PS handover for mobile-originated calls
a CS service.
2. The MME instructs the eNodeB to initiate a CSFB procedure. If the MME
supports the LAI-related function, the MME also delivers the LAI to the
eNodeB.

eRAN

4. The eNodeB initiates a PS handover preparation. If the preparation is
successful, the eNodeB instructs the UE to perform a handover. If the GERAN
or UE does not support DTM, the ongoing PS services of the UE are
suspended. Meanwhile, the SGSN updates the bearers toward the S-GW/P-
GW.
NOTE
5. After the handover, the UE initiates a CS call establishment procedure. The
procedure may be accompanied with an LAU or combined RAU/LAU
procedure in the GERAN.
6. The follow-up procedures are performed for the PS handover. These
procedures include data forwarding, path switching, and RAU, which are
performed together with step 5.

steps in the procedure for CSFB to GERAN based on PS handover for mobile-
originated calls.
19.2.3 CSFB Based on CCO/NACC

During CSFB based on CCO/NACC, the eNodeB receives a CS Fallback Indicator
from the MME, and then it sends a Mobility From EUTRA Command message to
the UE over the Uu interface. The message contains information about the
operating frequency, ID, and system information of a target GERAN cell. It then
initiates a CS service in the GERAN. 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 UE does not support DTM, the ongoing PS services of
the UE are suspended before a CS service is set up.

Figure 19-10 shows the procedure for CSFB to GERAN based on CCO/NACC for

eRAN
Figure 19-10 CSFB to GERAN based on CCO/NACC for mobile-originated calls
a CS service.
4. The eNodeB sends a Mobility From EUTRA Command message over the Uu
interface to indicate the operating frequency and ID of the target GERAN cell.
If the source cell has the system information of the target cell, the system
information is also carried in the message.
NOTE
5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in
the target cell.
6. If the GERAN or UE does not support DTM, the ongoing PS services of the UE
are suspended.
7. The UE initiates a CS call establishment procedure in the target GERAN cell.
8. The eNodeB initiates an S1-based UE context release procedure.


eRAN
steps in the procedure for CSFB to GERAN based on CCO/NACC for mobile-
originated calls.
19.2.4 CSFB Based on Redirection

During CSFB based on redirection, the eNodeB receives a CS Fallback Indicator,
and then it sends an RRC Connection Release message to release the UE. The
message contains information about a target GERAN frequency, reducing the time
for the UE to search for a target network. After selecting the GERAN, the UE
acquires the system information of a GERAN cell. Then, the UE performs initial
access to the cell to initiate a CS service. For the GERAN, the UE is an initially
accessing user.

Figure 19-11 shows the procedure for CSFB to GERAN based on redirection for
Figure 19-11 CSFB to GERAN based on redirection for mobile-originated calls
a CS service.

eRAN

GERAN carrier frequency group. Then, the eNodeB initiates an S1-based UE
context release procedure.
NOTE
6. If the GERAN or UE does not support DTM, in which CS and PS services run
simultaneously, the ongoing PS services of the UE are suspended.

steps in the procedure for CSFB to GERAN based on redirection for mobile-
originated calls.
19.2.5 Flash CSFB

After the eNodeB receives a CS Fallback Indicator, it sends an RRC Connection
Release message to release the UE. The message contains information about a
target GERAN frequency, physical cell identities of target cells working on this
frequency, and system information of the target cells. In this way, the UE can
quickly access the target GERAN without the need to perform the procedure for
acquiring system information of GERAN cells. Then, the UE can directly initiate a
CS service in a target GERAN cell. If the GERAN or UE does not support DTM, the
ongoing PS services of the UE are suspended before a CS service is set up.
The UEs involved must comply with 3GPP Release 9 or later and the networks
involved must comply with 3GPP Release 8 or later.

Figure 19-12 shows the procedure for flash CSFB to GERAN based on redirection
for mobile-originated calls.

eRAN
Figure 19-12 Flash CSFB to GERAN based on redirection for mobile-originated

calls
a CS service.
GERAN carrier frequency group, physical cell identities of GERAN cells
working on the frequencies, and system information of the cells. Then, the
eNodeB initiates an S1-based UE context release procedure.
NOTE
Target Cell/Frequency Selection and 5.1.2 CSFB Policy Selection. The system
information of the target cell is acquired during the RIM procedure.
5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in
the target cell.
6. If the GERAN or UE does not support DTM, the ongoing PS services of the UE
are suspended.

eRAN

steps in the procedure for flash CSFB to GERAN based on redirection for mobile-
originated calls.
19.2.6 Ultra-Flash CSFB to GERAN

Ultra-flash CSFB to GERAN is a Huawei-proprietary procedure. To enable this
function, the MSC, MME, and eNodeB must be all provided by Huawei and
support this function. Resources are prepared in advance on the GERAN during the
SRVCC, and authentication and ciphering procedures are excluded to reduce
delays. The following figures show the procedure of ultra-flash CSFB to GERAN for
mobile-originated calls and that for mobile-terminated calls. The paging
procedure is excluded from the figure for mobile-terminated calls. For details
about the paging procedure, see step 1 in Figure 19-3.
Figure 19-13 Ultra-flash CSFB to GERAN for mobile-originated calls

eRAN
Figure 19-14 Ultra-flash CSFB to GERAN for mobile-terminated calls
Steps 1 to 3a: The UE initiates voice services (mobile-originated calls and mobile-
terminated calls) on the E-UTRAN. The eNodeB triggers SRVCC to GERAN. The
MME and MSC use special handling to ensure a normal SRVCC procedure.
Step 3b: The BSC receives an SRVCC request and prepares CS resources.
Step 4: The eNodeB receives the handover command transferred over the core
network and sends it to the UE.
Step 5: The UE is transferred to the GERAN.
Steps 6 to 9: The UE establishes voice services on the GERAN. Signaling is carried

on the traffic channel (TCH), which accelerates the transfer and reduces delays.
As shown in the preceding figures, ultra-flash CSFB to GERAN excludes the

following procedures:
● Authentication procedure
The UE has been authenticated in the LTE system before CSFB to GERAN.
● Ciphering procedure
The UE has performed ciphering as instructed during SRVCC. Therefore, the
ciphering procedure is not required after the UE is handed over to the GERAN.

eRAN
● IMEI check procedure

The MME has sent the IMEI to the MSC during the preparation for SRVCC.
There, the procedure is not required in the GERAN after SRVCC.
● CS resource setup procedure
The GSM network has prepared CS resources during the SRVCC procedure and
therefore does not need to trigger the CS resource setup procedure for the UE
after CSFB.
If the Fast Return to LTE feature is enabled on the GERAN side, the UE can quickly
return to the E-UTRAN when it completes the voice service on the GERAN. For this
purpose, the Channel Release message must contain E-UTRA frequency
information, which the UE uses to select a suitable E-UTRAN cell to camp on.
When the IratMeasCfgTransSwitch option is selected, the eNodeB filters LTE
frequencies supported by the UE based on the UE capability to obtain a frequency
set. During the SRVCC, the eNodeB sends a Handover Required message
containing the frequency set to the BSC of the target cell. The BSC uses the
frequency set as a reference for LTE frequency selection for fast return to E-UTRAN
after the UE completes voice services on the GERAN.
19.2.7 Signaling Procedures for SMS

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

The CSFB procedure for an emergency call is the same as the CSFB procedure for a
normal mobile-originated voice service. The UE sends an RRC Connection Request
message over the Uu interface or the MME sends an Initial Context Setup Request
or UE Context Modification Request message, which contains an IE to inform the
eNodeB of the service type. Emergency calls take precedence over other services in
the eNodeB.
If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict
the cells in the handover restriction list when selecting the target cell.
If redirection is used for CSFB for emergency calls, the Channel Request message
that the UE sends when accessing the GERAN contains the indication of a CS
emergency call. The GERAN will treat this call as a common CS emergency call.
For details about admission and preemption of emergency calls, see Emergency
Call.
19.2.9 CSFB for LCS

After a UE initiates an LCS request, the MME performs an attach or combined
TAU/LAU procedure to inform the UE of the LCS capability of the EPS. If the EPS

eRAN
does not support LCS, the UE falls back to the GERAN to initiate LCS under the
control of the EPS. The CSFB procedure is the same as the procedure for CSFB to
GERAN for mobile-originated calls. If the GERAN initiates an LCS request towards
a UE camping on an E-UTRAN cell, the MSC sends an LCS indication to the MME
over the SGs interface. Then, the MME instructs the eNodeB to perform CSFB for
the UE. The CSFB procedure is the same as the procedure for CSFB to GERAN for
mobile-terminated calls. The UE performs the LCS service after the fallback to the
GERAN.
For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272
V10.0.0 and LCS.

CS Fallback (ERAN17.1 03)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS Fallback (ERAN17.1 03)

Uploaded by

Copyright:

Available Formats

eRAN

CS Fallback Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................3

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. ii

4.4.3 Network Monitoring......................................................................................................................................................... 40

6 Flash CSFB to UTRAN........................................................................................................... 65

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. iii

7 Flash CSFB to GERAN........................................................................................................... 73

8 Ultra-Flash CSFB to UTRAN................................................................................................ 81

9 Ultra-Flash CSFB to GERAN.................................................................................................89

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. iv

10 CSFB Steering to UTRAN................................................................................................... 99

11 CSFB Steering to GERAN................................................................................................. 108

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. v

11.3.4 Others............................................................................................................................................................................... 109

12 Coverage-based E-UTRAN to UTRAN CS/PS Steering.............................................. 113

13 CSFB with LAI to UTRAN................................................................................................. 118

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. vi

14 CSFB with LAI to GERAN................................................................................................. 124

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. vii

19.2.8 Emergency Call.............................................................................................................................................................. 151

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. viii

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN17.1 03 (2021-06-26)

1.2 eRAN17.1 02 (2021-04-30)

1.3 eRAN17.1 01 (2021-03-05)

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 1

1.4 eRAN17.1 Draft A (2020-12-29)

Canceled the None FDD BTS3911E

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

● The technical principles of features and their related parameters

2.2 Applicable RAT

2.3 Features in This Document

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 3

Feature ID Feature Name Chapter/Section

LOFD-001033 CS Fallback to UTRAN 4 CSFB to UTRAN

LOFD-001034 CS Fallback to GERAN 5 CSFB to GERAN

LOFD-001052 Flash CS Fallback to 6 Flash CSFB to UTRAN

LOFD-001053 Flash CS Fallback to 7 Flash CSFB to GERAN

LOFD-070202 Ultra-Flash CSFB to 8 Ultra-Flash CSFB to UTRAN

LOFD-081283 Ultra-Flash CSFB to 9 Ultra-Flash CSFB to GERAN

LOFD-001088 CS Fallback Steering to 10 CSFB Steering to UTRAN

LOFD-001089 CS Fallback Steering to 11 CSFB Steering to GERAN

LOFD-001078 E-UTRAN to UTRAN 12 Coverage-based E-UTRAN to

LOFD-001068 CS Fallback with LAI to 13 CSFB with LAI to UTRAN

LOFD-001069 CS Fallback with LAI to 14 CSFB with LAI to GERAN

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 4

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 5

Figure 3-1 Network architecture for CSFB

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 6

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 7

Figure 4-1 CSFB procedure

The CSFB procedure is described in detail in the following sections:

An enhancement to CSFB to UTRAN is described in 4.1.6 Load-based CSFB to

4.1.1 Blind/Measurement-based Handling Selection

Issue 03 (2021-06-26) Copyright © Huawei Technologies Co., Ltd. 8

Figure 4-2 Blind/Measurement-based handling selection