CS Fallback (Pico10.1 - Draft A)

Pico LTE
CS Fallback Feature Parameter

Description
Issue Draft A
Date 2015-11-30
HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
2 Overview......................................................................................................................................... 2
2.1 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 3
2.3 Architecture.................................................................................................................................................................... 3
2.4 Overall Process............................................................................................................................................................... 5
3 CSFB to UTRAN............................................................................................................................ 7
3.1 Basic CSFB to UTRAN..................................................................................................................................................8
3.1.1 Measurement............................................................................................................................................................... 8
3.1.2 Blind Handling............................................................................................................................................................ 9
3.2 Flash CSFB to UTRAN................................................................................................................................................ 11
3.3 Handover Decision....................................................................................................................................................... 12
3.3.1 Basic Handover Decision.......................................................................................................................................... 12
3.3.2 Decision Based on System Information.................................................................................................................... 12
3.4 Execution...................................................................................................................................................................... 13
3.4.1 Handover Policy Selection........................................................................................................................................ 13
3.4.2 Redirection-based CSFB Optimization for UEs in Idle Mode.................................................................................. 15
3.4.3 CSFB Admission Optimization for UEs in Idle Mode..............................................................................................16
3.5 RIM Procedure Between E-UTRAN and UTRAN...................................................................................................... 16
3.5.1 RIM Procedure Through the Core Network.............................................................................................................. 17
3.6 CSFB to UTRAN..........................................................................................................................................................18
3.6.1 Combined EPS/IMSI Attach Procedure.................................................................................................................... 18
3.6.2 CSFB Based on PS Handover................................................................................................................................... 19
3.6.3 CSFB Based on Redirection...................................................................................................................................... 21
3.6.4 Flash CSFB................................................................................................................................................................22
3.6.5 Redirection-based CSFB Optimization for UEs in Idle Mode.................................................................................. 24
3.6.6 CSFB Procedure for SMS..........................................................................................................................................24
3.6.7 CSFB for Emergency Calls....................................................................................................................................... 24
4 CS Fallback to GERAN...............................................................................................................26
Issue Draft A (2015-11-30) Huawei Proprietary and Confidential ii

Pico LTE
4.1 CS Fallback to GERAN................................................................................................................................................27

4.2 Execution...................................................................................................................................................................... 27
5 Related Features...........................................................................................................................29
5.1 CSFB to UTRAN..........................................................................................................................................................29
5.2 CSFB to GERAN..........................................................................................................................................................29
6 Network Impact........................................................................................................................... 30
6.1 CSFB to UTRAN..........................................................................................................................................................30
6.2 CSFB to GERAN..........................................................................................................................................................31
7 Engineering Guidelines............................................................................................................. 32
7.1 CS Fallback to UTRAN................................................................................................................................................32
7.1.1 When to Use CS Fallback to UTRAN.......................................................................................................................32
7.1.2 Required Information................................................................................................................................................ 32
7.1.3 Requirements............................................................................................................................................................. 33
7.1.4 Data Preparation........................................................................................................................................................ 34
7.1.5 Precautions.................................................................................................................................................................36
7.1.6 Activation.................................................................................................................................................................. 36
7.1.6.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................36
7.1.6.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 38
7.1.6.3 Using the CME to Perform Single Configuration.................................................................................................. 39
7.1.6.4 Using MML Commands......................................................................................................................................... 39
7.1.7 Activation Observation..............................................................................................................................................41
7.1.8 Deactivation...............................................................................................................................................................45
7.1.9 Performance Monitoring............................................................................................................................................46
7.1.10 Parameter Optimization........................................................................................................................................... 48
7.2 Flash CS Fallback to UTRAN...................................................................................................................................... 51
7.2.1 When to Use Flash CS Fallback to UTRAN............................................................................................................. 51
7.2.3 Requirements............................................................................................................................................................. 52
7.2.5 Precautions.................................................................................................................................................................55
7.2.6 Activation.................................................................................................................................................................. 55
7.2.8 Deactivation...............................................................................................................................................................60
7.3 CS Fallback to GERAN................................................................................................................................................61
7.3.1 When to Use CS Fallback to GERAN.......................................................................................................................61
Issue Draft A (2015-11-30) Huawei Proprietary and Confidential iii

Pico LTE

7.3.3 Requirements............................................................................................................................................................. 62
7.3.5 Precautions.................................................................................................................................................................65
7.3.6 Activation.................................................................................................................................................................. 65
7.3.8 Deactivation...............................................................................................................................................................70
8 Parameters..................................................................................................................................... 74
9 Counters........................................................................................................................................ 83
10 Glossary..................................................................................................................................... 106
11 Reference Documents............................................................................................................. 107
Issue Draft A (2015-11-30) Huawei Proprietary and Confidential iv

Pico LTE
CS Fallback Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes circuit switched fallback (CSFB), including its technical principles,
related features, network impact, and engineering guidelines.
"Pico", "eNodeB", or "base station" as used in this document refers to Huawei BTS3911B.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes
Pico10.1 Draft A (2015-11-30)

This document is created for Pico10.1.
Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 1

Pico LTE
CS Fallback Feature Parameter Description 2 Overview
2 Overview
In an early phase of evolved packet system (EPS) construction, operators who own a mature
UTRAN can protect their investments in legacy CS networks and reduce their investments in
the EPS by using legacy CS networks to provide CS services such as voice services, short
message services (SMSs), location services (LCSs), and emergency calls.
Currently, two solutions CSFB and voice over IP (VoIP) over IP multimedia subsystem (IMS)
are available for providing voice services for E-UTRAN UEs. After technological maturity,
industry chain, and deployment costs of the two methods are well weighed, CSFB is chosen
to serve as an interim solution for voice service access before mature commercial use of IMS.

Pico LTE
2.1 Introduction
With the CSFB solution, when a UE initiates a CS service, the MME instructs the UE to fall
back to the legacy CS network before the UE performs the service. CSFB is a session setup
procedure. UEs fall back to CS networks before CS sessions are set up, and they always stay
in the CS networks during the CS sessions. For details, see 3GPP TS 23.272 V8.5.0.
The eNodeB uniformly handles the CSFB for different types of CS services.
2.2 Benefits
CSFB offers the following benefits:
l Facilitates voice services on the LTE network.
l Helps operators reduce costs by reusing legacy CS networks and not requiring IMS
network deployment.
2.3 Architecture
CSFB is applicable to scenarios where the CS network of the UTRAN/GERAN has the same
or larger coverage area than the E-UTRAN.
The network architecture for CSFB is simple. To implement CSFB, all mobile switching
centers (MSCs) that serve overlapping areas with the E-UTRAN coverage must be upgraded
to support functions involving the SGs interface. The SGs interface is between an MSC and a
mobility management entity (MME), and functions involving the SGs interface include
combined attach, combined TAU/LAU (TAU is short for tracking area update, and LAU is
short for location area update), paging, and short message service (SMS). If the live network
uses an MSC pool, only one or multiple MSC servers in the MSC pool need to be upgraded to
support the SGs interface.
Figure 2-1 shows the architecture for CSFB to UTRAN/GERAN.

Pico LTE
Figure 2-1 Architecture for CSFB to UTRAN/GERAN
Table 1 lists the NEs and interface involved in CSFB to UTRAN/GERAN.
Table 2-1 NEs and interface involved in CSFB to UTRAN/GERAN

NE and Function
Interface
SGs interface Links the MME and the MSC server and provides the following
functions:
l Assists mobility management and paging between the EPS and the
CS network.
l Transmits mobile originated and mobile terminated SMS messages.
l Transmits messages related to combined attach and combined TAU/
LAU.
UE l Accesses the EPS and the UTRAN.

l Supports combined EPS/IMSI attach, combined EPS/IMSI detach,
and combined TAU/LAU. IMSI is short for international mobile
subscriber identity
l Supports CSFB mechanisms, such as redirections and handovers.
NOTE
CSFB-capable UEs must support SMS over SGs, but UEs that support SMS over
SGs are not necessarily CSFB-capable.

Pico LTE
NE and Function
Interface
MME l Supports the SGs interface to the MSC server/VLR.

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

l Supports SMS over SGs.
l Forwards paging messages transmitted through the SGs interface.
E-UTRAN l Forwards paging messages related to CSFB.

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

l Incoming handovers from the E-UTRAN, if PS handover is used as
the CSFB mechanism.
l RIM for delivering the system information of UTRAN or GERAN
cells to eNodeBs, in addition to PS redirection, if flash CSFB is
used as the CSFB mechanism.
SGSN Supports follow-up procedures performed for PS handovers, including

data forwarding, path switching, RAU, and encryption and
authentication.
Supports RIM (required for flash CSFB).
2.4 Overall Process

When a UE in an LTE system needs to perform voice service but the LTE system does not
support VoIP, a CSFB to an inter-RAT network is triggered. CSFB to UTRAN can be
implemented through measurement-based handovers or blind handovers, while CSFB to
GERAN can be implemented only through blind redirections.

Pico LTE
During the CSFB to UTRAN/GERAN, you need to check whether blind handling switch is
enabled. The BlindHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch parameter
specifies whether to enable blind handling. For details, see Table 2-2.
Table 2-2 CSFB to UTRAN/GERAN

Process CSFB to UTRAN CSFB to GERAN
Normal Procedure Measurement-based Supported Not supported

handover
(BlindHoSwitch is
set to OFF)
Blind handover Supported Supported

(BlindHoSwitch is
set to ON)
The timer expires. Blind redirection Supported Supported
During CSFB blind handling, the eNodeB selects the target RAT based on the RAT priorities
specified by the following parameters:
l CellOpHoCfg.InterRatHighestPri
l CellOpHoCfg.InterRatSecondPri
CSFB to UTRAN is performed if co-coverage neighboring UTRAN cells are configured, the
UE can work in the UTRAN, and CellOpHoCfg.InterRatHighestPri is set to UTRAN. For
details, see 3.1.2 Blind Handling. If the UE does not support UTRAN or no frequency of the
highest-priority RAT is available for blind redirections, CSFB is performed to the RAT of the
second highest priority.
CSFB to GERAN is performed if co-coverage neighboring GERAN cells are configured, the
UE can work in the GERAN, and CellOpHoCfg.InterRatHighestPri is set to GERAN. For
details, see 4 CS Fallback to GERAN. If the UE does not support GERAN or no frequency
of the highest-priority RAT is available for blind redirections, CSFB is performed to the RAT
of the second highest priority.
If the UE stays in the area covered by the eNodeB after the timer expires, the eNodeB
performs a redirection for CSFB. If the UE has completed UTRAN measurement, the eNodeB
preferably redirects the UE to the GERAN. For details, see 3.4.1 Handover Policy Selection
or 4.2 Execution.

Pico LTE
CS Fallback Feature Parameter Description 3 CSFB to UTRAN
3 CSFB to UTRAN
Though the triggering conditions vary depending on CSFB features, the overall CSFB
procedure is as follows:
1. Measurements or blind handling triggering
The eNodeB triggers inter-RAT measurements or blind handling based on the triggering
conditions for each feature, and generates a candidate cell list based on measurement
results.
2. Handover decision
In the handover decision phase, the eNodeB checks the candidate cell list and determines
whether a handover needs to be initiated and, if so, to which cell the UE is to be handed
over.
3. Handover execution
The eNodeB instructs the UE to be handed over from the serving cell to the target cell.

Pico LTE
3.1 Basic CSFB to UTRAN

The UtranCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies
whether to enable this function.
When a UE initiates a CS service in the E-UTRAN, the MME sends an S1-AP message
containing CS Fallback Indicator to the eNodeB, instructing the eNodeB to transfer the UE as
well as the CS service to a target network.
The eNodeB first checks the status of the blind handling switch to determine whether to
trigger UTRAN measurements or blind handling for CSFB to UTRAN. The blind handling
switch is controlled by the BlindHoSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter.
l If this option is selected, the eNodeB triggers blind handling directly.
l If this option is deselected, the eNodeB determines whether to trigger inter-RAT
measurements or blind handling based on the UE capability:
If the UE supports UTRAN measurements, the eNodeB triggers inter-RAT
measurements.
If the UE does not support UTRAN measurements, the eNodeB triggers blind
handling.
3.1.1 Measurement
Measurement Triggering Conditions
During CSFB, the eNodeB starts UTRAN measurement after it receives a CS Fallback
Indicator. The measurement configuration is the same as that for coverage-based handover
from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description.
The related configurations are as follows:
l Neighboring UTRAN frequencies are added by running the ADD UTRANNFREQ
command.
l The frequency priority is specified by the UtranNFreq.ConnFreqPriority parameter. A
larger value indicates a higher priority.
l The cell measurement priority of neighboring UTRAN cells is specified by the
UtranNCell.CellMeasPriority parameter, which must be configured manually.
l The number of frequencies or cells that the eNodeB can randomly select for
measurement is always equal to the maximum number allowed.
l For details about the maximum number of neighboring cells in a measurement
configuration message, see section 6.4 "RRC multiplicity and type constraint values" in
3GPP TS 36.331 V10.1.0.
Triggering of CSFB
During a measurement, CSFB is triggered by event B1. The principle of event-B1-triggered
CSFB is the same as that of event-B1-triggered coverage-based inter-frequency handover. For
details, see Inter-RAT Mobility Management in Connected Mode Feature Parameter
Description.

Pico LTE
They have different thresholds and time-to-trigger. Table 3-1 lists the thresholds and time-to-
trigger related to event B1 for CSFB to UTRAN. Other parameters are the same as those
related to event B1 for coverage-based inter-frequency handovers.
Table 3-1 Parameters related to event B1 for CSFB to UTRAN

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

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

Time To Trig UtranTimeToTrig
3.1.2 Blind Handling
Triggering of Blind Handling

The BlindHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch parameter specifies
whether to enable blind handling.
Target Cell Selection

When selecting target cells for blind handovers, the eNodeB excludes the following
neighboring cells:
l Blacklisted neighboring cells

l Neighboring cells with a handover prohibition flag
l Neighboring cells that have a different PLMN from the serving cell in the neighboring
cell list. If the inter-PLMN handover switch is turned on, such cells are not excluded.
l Cells in the areas indicated by the "Handover Restriction List" IE in the INITIAL
CONTEXT SETUP REQUEST message sent from the MME
When selecting the target frequency for blind redirections, the eNodeB filters the frequencies
based on the UE-support RAT and PLMN information.
l Figure 3-1 shows the target cell selection procedure when neighboring UTRAN cells are
configured during blind handling.
The UtranNCell.BlindHoPriority parameter specifies blind handover priority of a
neighboring UTRAN cell. A larger value indicates a higher priority.
The UtranNFreq.ConnFreqPriority parameter specifies the priority of a
neighboring UTRAN frequency. A larger value indicates a higher priority.
If the priorities of neighboring cells or frequencies are the same, the eNodeB
randomly selects a target cell or frequency. Due to uncertainty of random selection,
you are not advised to set the priorities to the same to ensure the blind handover
success.

Pico LTE
l Figure 3-1 shows the target cell selection procedure when no neighboring UTRAN cell
is configured.
Neighboring UTRAN frequencies are configured in UtranNFreq MOs.
The PLMN information of the neighboring UTRAN frequencies is contained in the
configured UtranRanShare or UtranExternalCell MOs.
Figure 3-1 Target cell selection (configured with a neighboring UTRAN cell)

Pico LTE
Figure 3-2 Target cell selection (configured with no neighboring UTRAN cell)
3.2 Flash CSFB to UTRAN

The UtranFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter
specifies whether to enable this function.
If this function is activated, the eNodeB obtains the UTRAN cell information through the
RIM procedure and sends the LTE-to-UMTS redirection message including the obtained
UTRAN cell information to the UE. The UE can access a UTRAN cell without obtaining the
UTRAN cell information, which is favorable to a small access delay.
To use this feature, the eNodeB must obtain UTRAN cell information through the RIM
procedures in Multiple Report mode. For details about the RIM procedure, see 3.5 RIM
Procedure Between E-UTRAN and UTRAN.
Other procedures are the same as those in CSFB to UTRAN. For details, see 3.1 Basic CSFB
to UTRAN.

Pico LTE
3.3 Handover Decision
3.3.1 Basic Handover Decision

When the handover policy is PS HO, SRVCC, or redirection (excluding flash redirection), the
eNodeB directly performs the basic handover decision, without the need for obtaining system
information of the peer.
Based on the check result, the eNodeB determines whether to initiate a handover and, if
needed, which cell the UE is to be handed over to. If the eNodeB receives measurement
reports about different RATs, it processes the reports in an FIFO manner.
The eNodeB excludes the following cells from the neighboring cell list
l Blacklisted neighboring cells

l Neighboring cells with a handover prohibition flag
l Neighboring cells that have a different PLMN from the serving cell in the neighboring
cell list. If the inter-PLMN handover switch is turned on, such cells are not excluded.
l Neighboring cells in the areas indicated by the IE Handover Restriction List in the
INITIAL CONTEXT SETUP REQUEST message sent from the MME
The eNodeB then sends a handover request to the target cell that is at the top of the filtered
candidate cell list. If the handover request fails, the eNodeB sends the handover request to the
next target cell, as described in Table 3-2.
Table 3-2 Sequence of handover requests to be sent by the eNodeB

Candidate Cell List Sequence of Handover Requests
Generated by
Measurement A handover request is sent to the cell with the highest quality of
signals.
Blind handling A handover request is sent to a cell or frequency that has the
highest priority. If multiple cells have the highest priority, the
eNodeB randomly selects a cell for blind handover.
If the handover request fails in all candidate cells:
l For a measurement procedure, the eNodeB waits until the UE sends the next
measurement report.
l For a blind handling procedure, the eNodeB completes the handover attempt.
3.3.2 Decision Based on System Information

If the eNodeB has to obtain system information about the peer, for example, flash redirection
as required in the handover policy, handover decision based on system information is
performed. If the handover decision is based on system information, the eNodeB includes
system information of the target cell of the corresponding RAT. Therefore, the time for

Pico LTE
reading cell system information is not required so that the UE can quickly access the target
network.
Decision based on system information adheres to the following principles:
l In blind handling scenarios:

a. The target cell list for blind handling is selected, including other cells running on
the target frequency for redirection.
The eNodeB selects the cells with a high cell measurement priority (specified by
UtranNCell.CellMeasPriority) from other cells running on the target frequency.
b. Basic handover decisions are applied. For details, see 3.3.1 Basic Handover
Decision.
c. Cells whose system information is not obtained are filtered out.
d. Cells whose PLMN is not in the list of PLMNs that the UE is allowed to access are
filtered out.
l In measurement scenarios:
a. Cells in the candidate cell list generated by measurement are selected, plus cells that
are not in measurement reports but work on the target frequency for redirection.
b. Basic handover decisions are applied. For details, see 3.3.1 Basic Handover
Decision.
c. Cells whose system information is not obtained are filtered out.
d. Cells whose PLMN is not in the list of PLMNs that the UE is allowed to access are
filtered out.
The eNodeB supports a maximum number of 16 UTRAN cells contained in a redirection

message.
l If the number of target cells after a decision is greater than 16, the eNodeB selects the
first 16 cells.
l If the number of target cells after a decision is smaller than 16, the eNodeB selects the
required target cells.
The eNodeB obtains system information of target cells in the RAN information management
(RIM) procedure. If a target cell does not support the RIM procedure, the eNodeB cannot
obtain system information of that cell.
3.4 Execution
3.4.1 Handover Policy Selection

CSFB from E-UTRAN to UTRAN can be based on PS handover, redirection, or flash
redirection, as shown in Figure 3-3. This handover policy selection procedure is performed
based on the assumption that neighboring frequency and neighboring cell configurations are
proper.
During a CSFB based on blind PS handover, if the target cell with the highest blind handover
priority fails to prepare the handover, the eNodeB turns to a cell with the second highest blind
handover priority. The eNodeB can retry a maximum of eight cells. If all these cells fail in
preparation, the eNodeB performs CSFB based on redirection.

Pico LTE
Figure 3-3 E-UTRAN-to-UTRAN handover policy selection procedure
The parameters in Figure 3-3 are described as follows:

l The timer is fixed at 4 seconds. If the UE stays in the area covered by the eNodeB after
the timer expires, the eNodeB performs a redirection for CSFB.
If the UE has completed UTRAN measurement, the eNodeB preferably redirects
the UE to the GERAN.
If there is no target frequency available for redirection, the eNodeB stops the
procedure.

Pico LTE
l The BlindHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch parameter

specifies whether to enable a blind handover.
l Both the UtranPsHoSwitch(UtranPsHoSwitch) option of the HoModeSwitch
parameter in the ENodeBAlgoSwitch MO and the PS_HO(PS_HO) option of the CSFB
handover policy Configuration parameter in the CsfbHoPolicyCfg MO control
whether to enable CSFB based on the PS handover. If either of the options is not
selected, CSFB to UTRAN based on the PS handover will fail and a redirection is
required. If the redirection also fails, an emergency blind redirection is applied after the
timer expires.
l The REDIRECTION(REDIRECTION) option of the CsfbHoPolicyCfg parameter in
the CSFallBackPolicyCfg MO specifies whether to enable redirection-based CSFB.
l The CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter specifies the CSFB handover
policy.
3.4.2 Redirection-based CSFB Optimization for UEs in Idle Mode

To speed up CSFB for UEs in idle mode by shortening end-to-end delays and to reduce the
CSFB failure rate due to initial context setup failures, the eNodeB optimizes redirection-based
CSFB for UEs in idle mode.
The optimization is performed after the eNodeB decides to perform blind handling, as shown
Figure 3-4.
l The optimization switch is controlled by the IdleCsfbRedirectOptSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter.
l For details about how to decide between normal redirection and flash redirection, see
3.4.1 Handover Policy Selection.

Pico LTE
Figure 3-4 Redirection-based CSFB optimization for UEs in idle mode
3.4.3 CSFB Admission Optimization for UEs in Idle Mode

UEs in idle mode only have a default bearer for data services, and the default bearer generally
has a low allocation/retention priority (ARP). When a UE in idle mode needs to perform
CSFB but the target cell is congested or cannot accommodate more UEs, this UE cannot
preempt resources in the target cell. To ensure the CSFB success rate in the preceding
scenario, the eNodeB preferentially admits CSFB UEs. This function is controlled by the
CSFallBackPolicyCfg.CsfbUserArpCfgSwitch parameter.
A large value of the CsFallbackPolicyCfg.NormalCsfbUserArp parameter indicates a higher
probability of admission of CSFB UEs in idle mode. For details about the admission
procedure, see Admission and Congestion Control Feature Parameter Description.
3.5 RIM Procedure Between E-UTRAN and UTRAN

In a RIM procedure, the E-UTRAN and UTRAN exchange information through the core
network.
In flash CSFB procedures, the eNodeB obtains the system information (SI) of external cells
from RNCs through the RIM procedure. For details about related parameters, see 3.5.1 RIM
Procedure Through the Core Network.

Pico LTE
The RIM procedure includes the following two information exchange modes:
l Single Report
In Single Report mode, the source cell sends a request, and then the target cell responds
with a single report.
When flash CSFB to UTRAN is triggered, the eNodeB sends a RIM message to the
RNC and includes the obtained SI in a redirection message to send to the UE. If the SI
fails to be obtained from the RNC, the eNodeB no longer attempts the RIM request.
l Multiple Report
In Multiple Report mode, the target cell responds with a report after receiving a request
from the source cell, and the target cell also sends a report to the source cell each time
information about the target cell changes.
When flash CSFB to UTRAN is triggered, the eNodeB sends RIM messages to all
neighboring UTRAN cells every 4 seconds no matter whether the eNodeB has CSFB
services.
To ensure that the SI of the target cell can be obtained successfully, the eNodeB starts a
four-second timer when it sends a RIM message.
If the eNodeB receives a response to the RIM message before the timer expires, the
eNodeB saves the obtained SI.
If the eNodeB receives a response to the RIM message after the timer expires, the
eNodeB considers that an exception has occurred and it discards the SI.
If the eNodeB does not receive a response to the RIM message after the timer
expires, the eNodeB sends the RIM message and starts the timer again (called a
retry) one hour later. If the eNodeB still does not receive a response after 10 retries,
the RIM request fails. The interval between the nth and (n+1)th retries is twice the
interval between the (n-1)th and nth retries. For example, the first retry occurs one
hour after the first SI acquisition fails, the second retry occurs two hours after the
first retry fails, and the third retry occurs four hours after the second retry fails. For
each retry, the eNodeB sends a RIM message and restarts the timer.
The eNodeB may obtain incorrect SI due to the abnormalities in the UTRAN, core
network, or transport network. To avoid this situation, the eNodeB randomly selects a
time between 02:00 a.m. and 04:00 a.m. to delete the system information that it has
obtained. Then, the eNodeB requests the SI of UTRAN cells through the RIM procedure
again.
If a neighboring UTRAN cell is faulty or deactivated, the RNC sends an END message
to notify the eNodeB of stopping the RIM procedure. In this case, the eNodeB deletes
the obtained SI and requests SI again in the next RIM procedure.
Currently, the eNodeB triggers a RIM procedure in Multiple Report mode only if MMEs
comply with 3GPP Release 9 or later.
3.5.1 RIM Procedure Through the Core Network

As shown in Figure 3-5, the RIM procedure involves the eNodeB, MME, SGSN, and RNC
Among these NEs, the MME and the SGSN transfer but do not resolve information. For
details, see section 8c "Signalling procedures between RIM SAPs" in 3GPP TS 48.018
V10.0.0.

Pico LTE
Figure 3-5 RIM procedure through the core network
The RIM procedure between E-UTRAN and UTRAN is controlled by the

UTRAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter. If this
option is selected, the eNodeB uses the RIM procedure in Multiple Report mode to obtain the
system information of external UTRAN cells.
3.6 CSFB to UTRAN
3.6.1 Combined EPS/IMSI Attach Procedure

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

Pico LTE
NOTE
The symbols that appear in signaling procedure figures throughout this document are explained as
follows:
l An arrow denotes the transmission of a message.
l A plain box denotes a mandatory procedure.
l A dashed box denotes an optional procedure.
The combined EPS/IMSI attach procedure is described as follows:

1. The UE sends a Combined attach request message to the MME, requesting a combined
EPS/IMSI attach procedure. This message also indicates whether the CSFB or SMS over
SGs function is required.
2. The EPS attach procedure is performed in the same way as 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.
3.6.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 3-7 shows the procedure for CSFB to UTRAN based on PS handover for mobile-
originated calls.

Pico LTE
Figure 3-7 CSFB to UTRAN based on PS handover for mobile-originated calls
1. The UE sends the MME an NAS message Extended Service Request to initiate a CS
service.
2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure.
If the MME supports the LAI-related feature, the MME also delivers the LAI to the
eNodeB.
3. The eNodeB determines whether to perform blind handling based on the UE capabilities,
parameters settings, and algorithm policies.
4. The eNodeB initiates a PS handover preparation phase. If the preparation is successful,
the eNodeB instructs the UE to perform a handover.
5. After the handover, the UE initiates a CS call establishment procedure with an LAU or
combined RAU/LAU procedure in the UTRAN.
6. The follow-up procedures are performed for the PS handover. These procedures include
data forwarding, path switching, and RAU. This step is performed together with step 5.
CSFB Procedure for Mobile-Terminated Calls

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

Pico LTE
Figure 3-8 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. Either of the following will occur:
If the UE is in idle mode, the MME sends a Paging message to the eNodeB. Then
the eNodeB sends a Paging message over the Uu interface to inform the UE of an
incoming call from the CS domain.
If the UE is in active mode, the MME sends the UE an NAS message to inform the
UE of an incoming call from the CS domain.
2. The UE sends an Extended Service Request message containing a CS Fallback Indicator
after receiving the paging message from the CS domain.
3. The MME instructs the eNodeB over the S1 interface to perform CSFB.
4. The subsequent steps are similar to steps 3 through 6 in the procedure for CSFB to
UTRAN based on PS handover for mobile-originated calls. The only difference is that
the UE sends a Paging Response message from the UTRAN cell.
3.6.3 CSFB Based on Redirection

During CSFB based on PS redirection, the eNodeB receives a CS Fallback Indicator, and
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 3-9 shows the procedure for CSFB to UTRAN based on redirection for mobile-
originated calls.

Pico LTE
Figure 3-9 CSFB to UTRAN based on redirection for mobile-originated calls
service.
eNodeB.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a
redirection. The message contains information about a target UTRAN frequency. Then,
the eNodeB initiates an S1 UE context release procedure.
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 the MME or eNodeB then initiates a paging procedure
for the UE. The paging procedure is similar to that for UTRAN described in 3.6.2 CSFB
Based on PS Handover. The subsequent steps are the same as those in the procedure for
CSFB to UTRAN based on PS handover for mobile-originated calls.
3.6.4 Flash CSFB

During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and sends an
RRC Connection Release message to release the UE. The message contains information about

Pico LTE
a target UTRAN frequency, and multiple physical cell identities and their associated system
information. In this way, the UE can quickly access the target UTRAN without the need to
perform the procedure for acquiring system information of the target UTRAN cell. Then, the
UE can directly initiate a CS service in the UTRAN cell.

Figure 3-10 shows the procedure for CSFB to UTRAN based on flash redirection for mobile-
originated calls.
Figure 3-10 CSFB to UTRAN based on flash redirection for mobile-originated calls
service.
eNodeB.
4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a
redirection. The message contains information about a target UTRAN frequency, and
multiple physical cell identities and their associated system information. Then, the
eNodeB initiates an S1 UE context release procedure.
5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in
the target cell.
6. The UE initiates a CS call establishment procedure in the target UTRAN cell.

Pico LTE

In a mobile-terminated call, the MSC sends a Paging request message from the CS domain to
the MME over the SGs interface, and the MME or eNodeB then initiates a paging procedure
for the UE. The paging procedure is similar to that for UTRAN. The subsequent steps are the
same as those in the procedure for CSFB to UTRAN based on PS handover for mobile-
originated calls.
3.6.5 Redirection-based CSFB Optimization for UEs in Idle Mode

Figure 3-11 shows the procedure for redirection-based CSFB optimization for UEs in idle
mode. After the eNodeB receives an initial context setup request with a CS Fallback Indicator
from the MME, the eNodeB does not perform the Uu security mode command or RRC
connection reconfiguration procedure.
Figure 3-11 Redirection-based CSFB optimization for UEs in idle mode
3.6.6 CSFB Procedure for SMS

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

The CSFB procedure for an emergency call is the same as that for a normal mobile-originated
voice service. The UE sends an RRC Connection Request message over the Uu interface or

Pico LTE
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 an emergency call.
The UTRAN will treat this call as a common CS emergency call.
For details about admission and preemption of emergency calls, see Emergency Call Feature
Parameter Description.

Pico LTE
CS Fallback Feature Parameter Description 4 CS Fallback to GERAN
4 CS Fallback to GERAN
CSFB to GERAN can be achieved only through blind redirections. The GeranCsfbSwitch
option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this
function.

Pico LTE
4.1 CS Fallback to GERAN

During the blind redirection for CSFB to GERAN, if GERAN frequencies are configured, the
eNodeB selects the frequency group with the highest GeranNfreqGroup.ConnFreqPriority
parameter value. The GeranNfreqGroup.ConnFreqPriority parameter specifies the priority
of a frequency used for blind redirections. A higher parameter value indicates a higher
priority.
4.2 Execution
CSFB to GERAN can be achieved only through redirections. Figure 4-1 shows the CSFB to
GERAN procedure.
Figure 4-1 CSFB to GERAN
The parameters in Figure 4-1 are described as follows:
l The timer is fixed at 4 seconds. If the UE stays in the area covered by the eNodeB after
the timer expires, the eNodeB performs a redirection for CSFB.
If the UE has completed UTRAN measurement, the eNodeB preferably redirects
the UE to the GERAN.

Pico LTE
If there is no target frequency available for the redirection, the eNodeB stops the
procedure.
l The BlindHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch parameter
specifies whether to enable a blind handover.
The eNodeB selects the target frequency for blind redirections based on the PLMN and
frequency priority through the following operations: filtering the frequencies based on
the value of the GeranRanShare parameter, prioritizing the filtered frequencies based
on the value of the ConnFreqPriority parameter, and selecting the frequency of the
highest priority. for redirections.

Pico LTE
CS Fallback Feature Parameter Description 5 Related Features
5 Related Features
5.1 CSFB to UTRAN

Prerequisite Features
PLBFD-003001 Inter-RAT Mobility between E-UTRAN and UTRAN
Mutually Exclusive Features

None
Affected Features
None
5.2 CSFB to GERAN

Prerequisite Features
None
Mutually Exclusive Features

None
Affected Features
None

Pico LTE
CS Fallback Feature Parameter Description 6 Network Impact
6 Network Impact
6.1 CSFB to UTRAN

System Capacity
CSFB provides CS service access for E-UTRAN UEs. Considering that the number of UEs
that request CS services within an area is relatively stable and is not affected by EPS
deployment, CSFB has no impact on the total number of UEs that request CS services within
a network.
CSFB mechanisms affect signaling overhead as follows:
If redirection is used as the CSFB mechanism, no extra signaling message is required for the
UTRAN because each CSFB procedure is equivalent to the initiation of a new CS service.
The EPS does not need to interact with the target network, and the corresponding signaling
overhead is negligible.
If PS handover is used as the CSFB mechanism, extra signaling messages are required from
each NE for the request, preparation, and execution of each handover. However, from the
perspective of traffic statistics, the number of UEs that initiate CS services per second per cell
during peak hours is far below cell capacity. Therefore, signaling overhead caused by PS
handovers is low.
If flash CSFB is used as the CSFB mechanism, extra signaling messages are required only
during eNodeB deployment. From that time onwards, the signaling overhead is negligibly low
because of infrequent system information updates.
Network Performance
CSFB affects the access success rate as follows:
l If redirection is used as the CSFB mechanism, each CSFB procedure is equivalent to the
initiation of a new CS service. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the UTRAN.
l If PS handover is used as the CSFB mechanism, the access success rate for CSFB UEs
depends on the success rate of handovers to the target RAT. Handover-triggered CS
service access has a higher requirement for signal quality compared with normal CS

Pico LTE
CS Fallback Feature Parameter Description 6 Network Impact
service access. Therefore, the access success rate for CSFB UEs is a little lower than that
for normal CS UEs in the UTRAN.
Each flash CSFB procedure is equivalent to the initiation of a new CS service. Therefore, the
access success rate for CSFB UEs is theoretically the same as that for normal CS UEs in the
UTRAN.
The RRC connection setup success rate may decrease slightly for the UTRAN. The uplink
interference information contained in SIB7 in the UTRAN updates frequently. The RNC
cannot update the uplink interference information in the system information sent to the LTE
network based on SIB7 in the UTRAN. Therefore, the uplink interference information
contained in SIB7 in the LTE network is a default value (-105 dBm). If the actual uplink
interference in the UTRAN is greater than -105 dBm, the transmit power on UEs' physical
random access channel (PRACH) increases and the RRC connection setup success rate may
decrease.
6.2 CSFB to GERAN

System Capacity
CSFB provides CS service access for E-UTRAN UEs. Considering that the number of UEs
that request CS services within an area is relatively stable and is not affected by EPS
deployment, CSFB has no impact on the total number of UEs that request CS services within
a network.
CSFB mechanisms affect signaling overhead as follows:
If redirection is used as the CSFB mechanism, no extra signaling message is required for the
GERAN because each CSFB procedure is equivalent to the initiation of a new CS service.
The EPS does not need to interact with the target network, and the corresponding signaling
overhead is negligible.
Network Performance
After the deployment of the EPS, CSFB affects the access success rate as follows:
If redirection is used as the CSFB mechanism, each CSFB procedure is equivalent to the
initiation of a new CS service. Therefore, the access success rate for CSFB UEs is
theoretically the same as that for normal CS UEs in the GERAN.

Pico LTE
CS Fallback Feature Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 CS Fallback to UTRAN
7.1.1 When to Use CS Fallback to UTRAN

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

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

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

Pico LTE
This information is used to configure neighboring UTRAN cells and to determine

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

NE Function
MME Supports:
l SGs interface to the MSC/VLR
l VLR and LAI selection based on the TAI of the serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach, combined EPS/IMSI detach, and combined
TAU/LAU
l CS signaling message routing
l SMS over SGs
MSC Supports:
l Combined EPS/IMSI attach
l SMS over SGs
l Paging message forwarding over the SGs interface
SGSN Does not activate ISR during the combined RAU/LAU procedure initiated by
the UE.
7.1.3 Requirements
Operating Environment
For CSFB to UTRAN, the eNodeB must collaborate with core-network equipment.
l If the core-network equipment is provided by Huawei, the version must be SAE1.2 or
later.
l If the core-network equipment is provided by another vendor, check whether the
equipment supports CSFB to UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-2.

Pico LTE
Table 7-2 License control item for Voice Services

Feature ID Feature License Control NE Sales Unit
Name Item
PLOFD-00100 Voice Services Voice Services eNodeB Per Pico

1 (per Pico)
This license
control item is
required for
ROHC and
SRVCC when
VoIP is not
supported and for
CSFB when VoIP
is supported.
7.1.4 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for
a specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with
UTRAN cells. This section provides only the information about MOs related to neighboring
UTRAN cells. For more information about how to collect data for the parameters in these
MOs, see Inter-RAT Mobility Management in Connected Mode Feature Parameter
Description.
Collect data for the parameters in the following MOs:
l UtranNFreq: used to configure neighboring UTRAN frequencies.
l UtranExternalCell: used to configure external UTRAN cells. The
UtranExternalCell.Rac parameter must be set.
l UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external UTRAN cell. This MO is required only if the NodeB that serves the external
UTRAN cell works in RAN sharing with common carriers mode and multiple operators
share the external UTRAN cell.
l UtranNCell: used to configure neighbor relationships with UTRAN cells. If a
neighboring UTRAN cell supports blind handovers according to the network plan, the
blind-handover priority of the cell must be specified by the
UtranNCell.BlindHoPriority parameter.

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

er Name ter ID Source
Handover ENodeB Network Set this parameter based on the network plan.
Mode AlgoSwi plan To activate PS handovers, select the
switch tch.Ho (negotiation UtranPsHoSwitch(UtranPsHoSwitch) option. If
ModeSw not this option is not selected, redirection will be used
itch required) for CSFB to UTRAN.
To activate blind handovers, select the
BlindHoSwitch(BlindHoSwitch) option. A blind
handover to an inter-RAT cell can be performed
only if a blind-handover priority is specified for the
inter-RAT cell. Compared with measurement-based
handovers, blind handovers reduce access delays
but cause lower handover success rates.
Handover ENodeB Network To activate CSFB to UTRAN, select the

Algo AlgoSwi plan UtranCsfbSwitch(UtranCsfbSwitch) option.
switch tch.HoA (negotiation
lgoSwitc not
h required)
The following table describes the parameters that must be set in the CSFallBackPolicyCfg
MO to specify the CSFB policy.
Para Parameter Data Source Setting Notes

meter ID
Name
CSFB CSFallBack Network plan Set this parameter based on the network plan.
Hando PolicyCfg.Cs (negotiation By default, both
ver fbHoPolicyC not required) REDIRECTION(REDIRECTION) and
Policy fg PS_HO(PS_HO) are selected. You are advised
Config to set this parameter based on the UE
uratio capabilities and network capabilities.
n
The following table describes the parameters that must be set in the CellOpHoCfg MO to set
the blind handover priorities of different RATs for CSFB.

Pico LTE
Paramete Parameter Data Setting Notes

r Name ID Source
CN CellOpHoCfg Networ Set this parameter based on the network plan.

Operator .CnOperatorI k plan This parameter specifies the ID of the operator
ID d (negoti whose RAT blind-handover priorities are to be
ation set.
not
require
d)
Highest CellOpHoCfg Networ Set this parameter based on the network plan.
priority .InterRatHigh k plan This parameter specifies the RAT of the highest
InterRat estPri (negoti priority used for blind handovers in CSFB and is
ation set to UTRAN(UTRAN) by default.
not
require
d)
Second CellOpHoCfg Networ Set this parameter based on the network plan.
priority .InterRatSeco k plan This parameter specifies the RAT of the second
InterRat ndPri (negoti highest priority used for blind handovers in CSFB
ation and is set to GERAN(GERAN) by default.
not Values of Highest priority InterRat and Second
require priority InterRat must be different.
d)
7.1.5 Precautions
None
7.1.6 Activation
7.1.6.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 7-3 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see "Configuring Data in a Summary Data File" in "Site Deployment" in
BTS3911B Deployment Guide, which is available in the eNodeB product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The MOs in Table 7-3 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 7-3 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.

Pico LTE
When configuring neighboring cells, you are advised to use the radio data planning file. For
details about how to fill in and export the radio data planning file, see section "Creating
eNodeBs in Batches" in the initial configuration guide for the eNodeB.
Table 7-3 Parameters for CSFB to UTRAN

MO Sheet in the Parameter Group Re
Summary Data mar
File ks
UtranNFreq UtranNFreq Local cell identity/Downlink UARFCN N/A
UtranExternal UtranExternalCe Mobile country code/Mobile network code/ N/A

Cell ll UTRAN cell identity/Downlink UARFCN/
RNC identity/Primary scrambling code/
Location area code
UtranExternal UtranExternalCe UTRAN cell identity/Mobile country code/ N/A

CellPlmn llPlmn Mobile network code/Share mobile country
code/Share mobile network code
UtranNCell UtranNCell Local cell identity/Mobile country code/Mobile N/A

network code/UTRAN cell identity/Blind
handover priority
ENodeBAlgo User-defined Handover Algo switch/Handover Mode switch N/A

Switch sheet
EnodeBAlgoSwi
tch is
recommended.
CellOpHoCfg User-defined CN Operator ID/Highest priority InterRat/ This

sheet Second priority InterRat para
CellOpHoCfg is met
recommended. er
mus
t be
cust
omi
zed
on a
list-
type
shee
t of
the
tem
plat
e.

Pico LTE
7.1.6.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch Activation
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
Batch Reconfiguration
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Open an existing planned area or create a new planned area.
Choose Area Management > Planned Area > Open Planned Area (CME client mode), or
choose CME > Planned Area > Open Planned Area (U2000 client mode), to open an
existing planned area.
Choose Area Management > Planned Area > Create Planned Area (CME client mode), or
choose CME > Planned Area > Create Planned Area (U2000 client mode), to create a new
planned area. Ensure that the target NE is present in the new planned area.
Step 2 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs." For detailed
operations, press F1 in a CME window and navigate to Managing the CME > CME
Guidelines > LTE Application Management > eNodeB Related Operations >
Customizing a Summary Data File for Batch eNodeB Configuration in the CME online
help.
NOTE
It is good practice to use the list style to customize a summary data file when using the CME to perform
batch configuration for existing eNodeBs.
Step 3 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 4 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Step 5 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
Step 6 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts. For
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End

Pico LTE
7.1.6.3 Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or
choose Area Management > Planned Area > Export Incremental Scripts (CME client
mode), to export and activate the incremental scripts.
----End
7.1.6.4 Using MML Commands
Procedure
l Basic scenario 1: CSFB to UTRAN using blind redirections
Step 1 Add neighboring UTRAN frequencies and neighbor relationships with UTRAN cells or
enable inter-RAT blind redirection triggered by no neighboring cells. For details about

Pico LTE
parameter settings, see Inter-RAT Mobility Management in Connected Mode Feature

Parameter Description.
Step 2 Run the MOD ENODEBALGOSWITCH command with both the

UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter and
the BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter
selected.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option deselected
and the REDIRECTION option of the CSFB handover policy Configuration parameter
selected.
Step 4 Run the MOD UTRANNCELL command with the Blind handover priority parameter set
to 32.
----End
l Basic scenario 2: CSFB to UTRAN using blind handovers
Step 1 Add neighboring UTRAN frequencies and neighbor relationships with UTRAN cells. For
details about parameter settings, see Inter-RAT Mobility Management in Connected Mode
Feature Parameter Description.

UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter, and
the BlindHoSwitch(BlindHoSwitch) and UtranPsHoSwitch(UtranPsHoSwitch) options of
the Handover Mode switch parameter selected.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
to 32.
----End
l Basic scenario 3: CSFB to UTRAN using measurement-based redirections
Step 2 Run the MOD ENODEBALGOSWITCH command with the

UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter
selected and the BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch
parameter deselected.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option deselected
and the REDIRECTION option of the CSFB handover policy Configuration parameter
selected.
to 32.
----End
l Basic scenario 4: CSFB to UTRAN using measurement-based handovers

Pico LTE
Step 2 Run the MOD ENODEBALGOSWITCH command with the

UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter and
the UtranPsHoSwitch(UtranPsHoSwitch) option of the Handover Mode switch
parameter selected, and the BlindHoSwitch(BlindHoSwitch) option of the Handover
Mode switch parameter deselected.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the
CSFB handover policy Configuration parameter selected.
to 32.
----End
MML Command Examples

l Basic scenario 1: CSFB to UTRAN using blind redirections
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1,
HoModeSwitch=BlindHoSwitch-1;
MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&PS_HO-0;
MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1,
CellId=123,BlindHoPriority=32;
l Basic scenario 2: CSFB to UTRAN using blind handovers

HoModeSwitch=UtranPsHoSwitch-1&BlindHoSwitch-1;
l Basic scenario 3: CSFB to UTRAN using measurement-based redirections

HoModeSwitch=BlindHoSwitch-0;
MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms,
CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13;
l Basic scenario 4: CSFB to UTRAN using measurement-based handovers

HoModeSwitch=UtranPsHoSwitch-1&BlindHoSwitch-0;
MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms,
CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13;
7.1.7 Activation Observation
Signaling Observation
The activation observation procedure for CSFB to UTRAN is as follows:
1. Enable a UE to camp on an E-UTRAN cell and initiate a voice call.

2. Enable the UE to camp on an E-UTRAN cell and receive a voice call.

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

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

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

Pico LTE
Figure 7-6 MobilityFromEUTRAN message during CSFB to UTRAN
Counter Observation
Table 7-4 lists the performance counters for observing functions related to CSFB to UTRAN.
Table 7-4 Performance counters for observing CSFB to UTRAN

Function Counter Counter Description
ID Name
CS Fallback to 152672832 L.CSFB.E2W Number of times CSFB to UTRAN is

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

UTRAN 9 Emergency triggered for emergency calls
triggered for
emergency calls
7.1.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in 7.1.6.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 7-5.

Pico LTE
Table 7-5 Parameters for deactivating CSFB to UTRAN

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

ch EnodeBAlgoSwitch is ch UTRAN, set
recommended. UtranCsfbSwitch under the
HoAlgoSwitch parameter to
0.
Using the CME to Perform Single Configuration

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

l Deactivating CSFB to UTRAN
Run the MOD ENODEBALGOSWITCH command with the
UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter
deselected.

l Deactivating CSFB to UTRAN
MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-0;
7.1.9 Performance 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 indicate the success
rate of the CSFB procedure on the radio network side. Therefore, the performance counters on
the LTE side cannot directly show user experience of the CSFB procedure. It is recommended
that you perform drive tests and use the performance counters on the UE side to determine the
actual user experience of the CSFB procedure.
Related counters are listed in Table 7-6.
Table 7-6 Counters related to CSFB execution by the eNodeB

Counter ID Counter Name Description
1526728321 L.CSFB.PrepAtt Number of CSFB requests received by the

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

from the eNodeB
Table 7-7 lists the counter related to CSFB to UTRAN.

Pico LTE
Table 7-7 Counter related to CSFB to UTRAN

1526728323 L.CSFB.E2W Number of times CSFB to UTRAN is

performed
Table 7-8 lists the counters that indicate whether CSFB is performed through redirections or
through handovers.
Table 7-8 Counters related to CSFB through redirections or handovers

1526728497 L.RRCRedirection Number of CSFB-based redirections from E-

.E2W.CSFB UTRAN to UTRAN
1526728504 L.IRATHO.E2W.C Number of CSFB-based handover

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

.E2W.CSFB.Time from E-UTRAN to UTRAN caused by
Out CSFB protection timer expiration
Table 7-10 lists the counters related to CSFB for emergency calls.
Table 7-10 Counters related to CSFB for emergency calls

1526729510 L.IRATHO.E2W.C Number of CSFB-based handover attempts

SFB.ExecAttOut.E to UTRAN triggered for emergency calls
mergency
1526729511 L.IRATHO.E2W.C Number of successful CSFB-based

SFB.ExecSuccOut. handovers to UTRAN triggered for
Emergency emergency calls

Pico LTE
CSFB handover success rate for emergency calls =

L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency/
L.IRATHO.E2W.CSFB.ExecAttOut.Emergency
7.1.10 Parameter Optimization

CSFB end-to-end delay includes the processing time at the LTE side and that at the side after
fallback. Processing at any side may affect the CSFB end-to-end delay and user experience.
Blind Handling for CSFB

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

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

Operator Cfg.CnOpe plan This parameter specifies the ID of the operator
ID ratorId (negotiatio whose RAT blind-handover priorities are to be
n not set.
required)
Highest CellOpHo Network Set this parameter based on the network plan.
priority Cfg.InterR plan This parameter specifies the RAT of the highest
InterRat atHighestP (negotiatio priority used for blind handovers in CSFB and is
ri n not set to UTRAN(UTRAN) by default.
required)
Second CellOpHo Network Set this parameter based on the network plan.
priority Cfg.InterR plan This parameter specifies the RAT of the second
InterRat atSecondP (negotiatio highest priority used for blind handovers in CSFB
ri n not and is set to GERAN(GERAN) by default.
required) Values of Highest priority InterRat and Second
priority InterRat must be different.
The following table describes the parameters in the ENodeBAlgoSwitch MO used to activate
or deactivate blind handovers.

Pico LTE
Parameter Paramete Data Setting Notes

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

Mode switch lgoSwitch. plan BlindHoSwitch(BlindHoSwitch) option. A blind
HoModeS (negotiati handover to an inter-RAT neighboring cell can
witch on not succeed only if a blind-handover priority is
required) specified for the inter-RAT neighboring cell.
Compared with measurement-based handovers,
blind handovers reduce access delays but cause
lower handover success rates.
To deactivate blind handovers, clear the
BlindHoSwitch(BlindHoSwitch) option.
Measurement-based Handovers for CSFB

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

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

Pico LTE
Paramet Parameter Data Setting Notes

er Name ID Source
CSFB CSFallBac Network Set this parameter based on the network plan. This
Utran kHo.CsfbH plan parameter specifies the time-to-trigger for event
EventB1 oUtranTim (negotiatio B1 in CSFB to UTRAN. When CSFB to UTRAN
Time To eToTrig n not is required, set this parameter, which is used by
Trig required) UEs as one of the conditions for triggering event
B1. When a UE detects that the signal quality in at
least one UTRAN cell meets the entering
condition, the UE does not immediately send a
measurement report to the eNodeB. Instead, the
UE sends a measurement report only when the
signal quality has been meeting the entering
condition throughout a period defined by this
parameter. This parameter helps decrease the
number of occasionally triggered event reports,
the average number of handovers, and the number
of incorrect handovers, preventing unnecessary
handovers.
CSFB CSFallBac Network Set this parameter based on the network plan. This
UTRAN kHo.CsfbH plan parameter specifies the RSCP threshold for event
EventB1 oUtranB1T (negotiatio B1 in CSFB to UTRAN. When CSFB to UTRAN
RSCP hdRscp n not is required, set this parameter, which is used by
Trigger required) UEs as one of the conditions for triggering event
Threshold B1. This parameter specifies the minimum
required RSCP of the signal quality provided by a
UTRAN cell when a CSFB procedure can be
initiated toward this cell. Event B1 is triggered
when the RSCP measured by the UE is higher
than the value of this parameter and all other
conditions are also met.
CSFB CSFallBac Network This parameter specifies the Ec/No threshold for
UTRAN kHo.CsfbH plan event B1, which is used in CS fallback to
EventB1 oUtranB1T (negotiatio UTRAN. When CSFB to UTRAN is required, set
ECN0 hdEcn0 n not this parameter, which is used by UEs as one of the
Trigger required) conditions for triggering event B1. This parameter
Threshold specifies the minimum required Ec/No of the
signal quality provided by a UTRAN cell when a
CSFB procedure can be initiated toward this cell.
Event B1 is triggered when the Ec/No measured
by the UE is higher than the value of this
parameter and all other conditions are also met.
Set this parameter to a large value for a cell with a
large signal fading variance in order to reduce the
probability of unnecessary handovers. Set this
parameter to a small value for a cell with a small
signal fading variance in order to ensure timely
handovers.

Pico LTE
7.2 Flash CS Fallback to UTRAN
7.2.1 When to Use Flash CS Fallback to UTRAN

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

l Collect information about whether CS Fallback to UTRAN has been activated.
and UTRAN cells. Information about coverage areas includes engineering parameters of
sites (such as latitude and longitude), pilot TX power, and neighbor relationship
configurations.
l Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core
networks, and ensure that they all support CSFB and the RIM procedure. Table 7-11
describes the requirements of flash CSFB to UTRAN for the core networks. For details
about processing in Huawei UMTS equipment, see Interoperability Between UMTS and
LTE Feature Parameter Description in RAN Feature Documentation.
network:
Whether the UEs support redirections from E-UTRAN to UTRAN
Whether the UEs support PS handovers from E-UTRAN to UTRAN
Whether the UEs support UTRAN measurements
Whether the UEs comply with 3GPP Release 9 specifications
This information is used to configure neighboring UTRAN cells and to determine
whether to perform CSFB based on handover or redirection. For details, see Inter-RAT
Mobility Management in Connected Mode Feature Parameter Description.
Table 7-11 Requirements of flash CSFB to UTRAN for core networks

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

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

Release 9

Pico LTE
7.2.3 Requirements
For flash CSFB to UTRAN, the eNodeB must collaborate with core-network equipment. If
the core-network equipment is provided by Huawei, the version must be PS9.1 or later. If the
core-network equipment is provided by another vendor, check with the vendor whether the
equipment supports this feature. The core network must support flash CSFB to UTRAN.
License
The operator has purchased and activated the license for the feature listed in the following
table.
Feature ID Feature Name License NE Sales Unit

Control
Item
PLOFD-001001 Voice Services Voice eNodeB Per Pico

Services (per
Pico)
This license
control item is
required for
ROHC and
SRVCC when
VoIP is not
supported and
for CSFB
when VoIP is
supported.
NOTE
If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN.

operator

Pico LTE
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with
UTRAN cells. This section provides only the information about MOs related to neighboring
UTRAN cells and key parameters in these MOs. For more information about how to collect
data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description.
Collect data for the parameters in the following MOs:
l UtranNFreq: used to configure neighboring UTRAN frequencies.

l UtranExternalCell: used to configure external UTRAN cells. The
UtranExternalCell.Rac parameter must be set.
l UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared
external UTRAN cell. This MO is required only if the NodeB that serves the external
UTRAN cell works in RAN sharing with common carriers mode and multiple operators
share the external UTRAN cell.
l UtranNCell: used to configure neighbor relationships with UTRAN cells. If a
neighboring UTRAN cell supports blind handovers according to the network plan, the
blind-handover priority of the cell must be specified by the
UtranNCell.BlindHoPriority parameter.
to set the handover mode and handover algorithm switches for flash CSFB to UTRAN.
Parameter Parameter Data Source Setting Notes

Name ID
Handover ENodeBAlg Network plan Set this parameter based on the network
Mode switch oSwitch.Ho (negotiation plan.
ModeSwitch not required) To activate blind handovers, select the
BlindHoSwitch(BlindHoSwitch)
option. A blind handover to an inter-
RAT cell can be performed only if a
blind-handover priority is specified for
the inter-RAT cell. Compared with
measurement-based handovers, blind
handovers reduce access delays but
cause lower handover success rates.
Handover Algo ENodeBAlg Network plan To activate flash CSFB to UTRAN,

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

Pico LTE
Parameter Parameter Data Source Setting Notes

Name ID
RIM switch ENodeBAlg Network plan UTRAN_RIM_SWITCH under this

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

r Name ID Source

Operator .CnOperatorI k plan This parameter specifies the ID of the operator
ID d (negoti whose RAT blind-handover priorities are to be
ation set.
not
require
d)

Pico LTE

r Name ID Source
ation set to UTRAN(UTRAN) by default.
not
require
d)
d)
7.2.5 Precautions
None
7.2.6 Activation
eNodeBs
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see "Configuring Data in a Summary Data File" in "Site Deployment" in
BTS3911B Deployment Guide, which is available in the eNodeB product documentation.
parameters.
When configuring neighboring cells, you are advised to use the radio data planning file.

Pico LTE
Table 7-12 Parameters for flash CSFB to UTRAN

MO Sheet in the Parameter Group Remar
Summary ks
Data File
UtranNFre UtranNFreq Local cell identity/Downlink UARFCN N/A

q
UtranExter UtranExternalC Mobile country code/Mobile network code/ N/A

nalCell ell UTRAN cell identity/Downlink
UARFCN/RNC identity/Routing area code
configure indicator/Routing area code/Primary
scrambling code/Location area code
UtranExter UtranExternalC UTRAN cell identity/Mobile country code/ N/A

nalCellPlm ellPlmn Mobile network code/Share mobile country
n code/Share mobile network code
UtranNCell UtranNCell Local cell identity/Mobile country code/ N/A

Mobile network code/UTRAN cell identity/
Blind handover priority
ENodeBAl User-defined Handover Algo switch/Handover Mode N/A

goSwitch sheet switch/Redirection switch/RIM switch/
EnodeBAlgoS BlindHoSwitch
witch is
recommended.
CellOpHo User-defined CN Operator ID/Highest priority InterRat/ This

Cfg sheet Second priority InterRat paramet
CellOpHoCfg er must
is be
recommended. customi
zed on a
list-type
sheet of
the
template
.
Batch Activation

Pico LTE
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Open an existing planned area or create a new planned area.
Choose Area Management > Planned Area > Open Planned Area (CME client mode), or
choose CME > Planned Area > Open Planned Area (U2000 client mode), to open an
existing planned area.
Choose Area Management > Planned Area > Create Planned Area (CME client mode), or
choose CME > Planned Area > Create Planned Area (U2000 client mode), to create a new
planned area. Ensure that the target NE is present in the new planned area.
Step 2 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs." For detailed
operations, press F1 in a CME window and navigate to Managing the CME > CME
Guidelines > LTE Application Management > eNodeB Related Operations >
Customizing a Summary Data File for Batch eNodeB Configuration in the CME online
help.
NOTE
It is good practice to use the list style to customize a summary data file when using the CME to perform
batch configuration for existing eNodeBs.
Step 4 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
Step 6 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts. For
detailed operations, see Managing the CME > CME Guidelines > Script File Management
> Exporting Incremental Scripts from a Planned Data Area in the CME online help.
----End

window.

Pico LTE
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
----End
Procedure
The prerequisite is that CSFB to UTRAN has been activated.
Step 1 Run the MOD GLOBALPROCSWITCH command to set the RIM Coding Policy
parameter.
If the peer device is a Huawei device, go to Step 2.
If the peer device is not a Huawei device, modify the RIM Coding Policy parameter. Run the
MOD GLOBALPROCSWITCH command to set the RIM Coding Policy parameter to
StandardCoding.

UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) option of the Handover Algo switch

Pico LTE
parameter and the UTRAN_RIM_SWITCH(UTRAN RIM Switch) option of the RIM

switch parameter selected.
----End

MOD ENODEBALGOSWITCH:
HoAlgoSwitch=UtranFlashCsfbSwitch-1,RimSwitch=UTRAN_RIM_SWITCH-1;
Enable a UE to camp on an E-UTRAN cell and initiate a voice call. If the call continues and
the RRC Connection Release message traced on the Uu interface carries the information about
neighboring UTRAN cells, flash CSFB to UTRAN has been activated.
The signaling procedure for flash CSFB to UTRAN is similar to that for redirection-based
CSFB to UTRAN described in 7.1.7 Activation Observation. The difference is that the RRC
Connection Release message carries the information about neighboring UTRAN cells.
MML Command Observation

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

ID
FLash CS 152672870 L.FlashCSFB.E2W Number of times flash

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

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

7 information responses sent
from a UMTS network to an
eNodeB

Pico LTE

ID
152672894 L.RIM.SI.E2W.Update Number of system

8 information updates sent
from a UMTS network to an
eNodeB
7.2.8 Deactivation

eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in 7.2.6.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 7-14.
Table 7-14 Parameters for deactivating flash CSFB to UTRAN

ENodeBAlgoSwit User-defined sheet HoAlgoSwit Set UtranFlashCsfbSwitch

ch EnodeBAlgoSwitch is ch under the HoAlgoSwitch
recommended. parameter to 0.

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

Run the MODENODEBALGOSWITCH command with the
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) option of the Handover Algo switch
parameter deselected.

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranFlashCsfbSwitch-0;

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

Pico LTE

The parameter optimization procedure for this function is the same as that for CSFB to
UTRAN. For details, see 7.1.10 Parameter Optimization.
7.3 CS Fallback to GERAN
7.3.1 When to Use CS Fallback to GERAN

Use CS Fallback to GERAN in the initial phase of LTE network deployment when both of the
l The operator owns a mature GERAN.

l The LTE network does not provide VoIP services, or UEs in the LTE network do not
support VoIP services.

and GERAN cells. Information about coverage areas includes engineering parameters of
sites (such as latitude and longitude), TX power of cell reference signals (RSs), and
neighbor relationship configurations.
l Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core
networks, and ensure that they all support CSFB. Table 7-15 describes the requirements
of CSFB to GERAN for the core networks.
network:
Whether the UEs support redirections from E-UTRAN to GERAN
Table 7-15 Requirements of CSFB to GERAN for the core networks

NE Function
MME Supports
l SGs interface to the MSC/VLR.
l LAI selection based on the TAI of the serving cell
l MSC-initiated paging
l PLMN selection and reselection
l Combined EPS/IMSI attach, combined EPS/IMSI detach, and
combined TAU/LAU
l CS signaling message routing
l SMS over SGs
MSC problem l Combined EPS/IMSI attach

analysis l SMS over SGs
l Paging message forwarding over the SGs interface

Pico LTE
NE Function
SGSN Does not activate ISR during the combined RAU/LAU procedure
initiated by the UE.
7.3.3 Requirements
For CSFB to GERAN, the eNodeB must collaborate with core-network equipment. If the
core-network equipment is provided by Huawei, the version must be PS9.1 or later. If the
core-network equipment is provided by another vendor, check with the vendor whether the
equipment supports this feature. The core network must support flash CSFB to UTRAN.
License
The operator has purchased and activated the license for the feature listed in the following
table.
Feature ID Feature Name License NE Sales Unit

Control
Item
PLOFD-001001 Voice Services Voice eNodeB Per Pico

Services (per
Pico)
This license
control item is
required for
ROHC and
SRVCC when
VoIP is not
supported and
for CSFB
when VoIP is
supported.

operator

Pico LTE
Required Data
Before configuring CSFB to GERAN, collect the data related to neighboring GERAN
frequencies. This section provides only the information about MOs related to neighboring
GERAN frequencies.
l Collect data for the parameters in the following MOs: GeranNfreqGroup: used to
configure GERAN carrier frequency groups.
l GeranNfreqGroupArfcn: used to configure absolute radio frequency channel numbers
(ARFCNs) in each GERAN carrier frequency group.
l GeranRanShare: used to configure information about an operator that shares a
neighboring GERAN carrier frequency group.
to set the handover mode and handover algorithm switches for CSFB to GERAN.
Para Para Data Setting Notes

met mete Source
er r ID
Na
me
Han ENod Network To activate CSFB to GERAN, select

dove eBAl plan GeranCsfbSwitch(GeranCsfbSwitch) under this parameter.
r goSw (negotiat
Algo itch. ion not
swit HoAl required
ch goSw )
itch
Han ENod Network Set this parameter based on the network plan.
dove eBAl plan To activate redirection, select
r goSw (negotiat BlindHoSwitch(BlindHoSwitch) under this parameter.
Mod itch. ion not Compared with blind handovers, blind redirections reduce
e HoM required access delays but cause lower handover success rates.
swit odeS )
ch witch

Pico LTE

r Name ID Source
Local cell CellOpHoCfg Networ Set this parameter based on the network plan.
ID .LocalCellId k plan This parameter specifies the ID of the local cell
(negoti where CSFB based on blind handovers are
ation performed.
not
require
d)

Operator .CnOperatorI k plan This parameter specifies the ID of an operator.
ID d (negoti
ation
not
require
d)
ation set to UTRAN(UTRAN) by default. If CSFB to
not GERAN is used, set this parameter to
require GERAN(GERAN).
d)
d)
The following table describes the parameters that must be set in the CSFallBackPolicyCfg
MO to specify the CSFB policy.
Para Parameter Data Source Setting Notes

meter ID
Name
CSFB CSFallBack Network plan Set this parameter based on the network plan.
Hando PolicyCfg.Cs (negotiation By default, both
ver fbHoPolicyC not required) REDIRECTION(REDIRECTION) and
Policy fg PS_HO(PS_HO) are selected.
Config NOTE
uratio If REDIRECTION(REDIRECTION) and
n PS_HO(PS_HO) are not selected and CSFB based
on blind handovers is enabled, the eNodeB performs
CSFB based on blind redirections.

Pico LTE
7.3.5 Precautions
None
7.3.6 Activation
eNodeBs
into the CME for batch configuration. For detailed instructions, see "Configuring Data in a
Summary Data File" in "Site Deployment" in BTS3911B Deployment Guide, which is
available in the eNodeB product documentation.
parameters.
Table 7-16 Parameters for CSFB to GERAN
MO Sheet in Parameter Group Remarks

the
Summary
Data File
GeranNfreqGr GeranNfreq Local cell ID/BCCH group The RNP template sheet
oup Group ID/GERAN version/Starting is recommended.
ARFCN/Band indicator/
Frequency Priority for
Connected Mode
GeranNfreqGr GeranNfreq Local cell ID/BCCH group The RNP template sheet
oupArfcn GroupArfcn ID/GERAN ARFCN is recommended.
GeranRanShar GeranRanSh Local cell ID/BCCH group The RNP template sheet
e are ID/Mobile country code/ is recommended.
Mobile network code
ENodeBAlgoS User- Handover Algo switch/ This parameter must be

witch defined Handover Mode switch customized on a list-type
sheet sheet of the template.
EnodeBAlg
oSwitch is
recommend
ed.

Pico LTE
MO Sheet in Parameter Group Remarks

the
Summary
Data File
CellOpHoCfg User- Local cell ID/CN Operator This parameter must be

defined ID/Highest priority InterRat/ customized on a list-type
sheet Second priority InterRat sheet of the template.
CellOpHoC
fg is
recommend
ed.
CSFallBackPol User- CSFB handover policy This parameter must be

icyCfg defined Configuration customized on a list-type
sheet sheet of the template.
CSFallBack
PolicyCfg is
recommend
ed.
Batch Activation
Batch reconfiguration using the CME can be used to activate the feature on existing eNodeBs.
This method reconfigures all data for multiple eNodeBs in a single procedure. The procedure
is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or
choose Advanced > Customize Summary Data File (CME client mode), to customize a
summary data file for batch reconfiguration.
In the summary data file, set the parameters in the MOs listed in the table in 7.3.6.1 Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs and then close the
file.
Import Base Station Bulk Configuration Data (CME client mode), to export the eNodeB

Pico LTE
----End

window.
----End
Step 1 On the Search tab page in area 2, enter an MO name.
----End

Pico LTE
Procedure
l To implement CSFB to GERAN through a blind redirection, perform the following
steps:
Step 1 Run the ADD GERANNFREQGROUP command to add a neighboring GERAN carrier
frequency group. In this step, set Frequency Priority for Connected Mode to 0.
GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter and
the BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter
selected.
Step 3 (Optional) Run the MOD CSFALLBACKPOLICYCFG command with the
REDIRECTION(REDIRECTION) option of the CSFB handover policy Configuration
parameter selected.
Step 4 Run the ADD CELLOPHOCFG command to add the priorities of systems to be considered
in handovers. In this step, set Highest priority InterRat to GERAN and Second priority
InterRat to UTRAN.
----End

l CSFB to GERAN based on the blind redirection
ADD
GERANNFREQGROUP:LOCALCELLID=0,BCCHGROUPID=0,GERANVERSION=GSM,STARTINGARFCN=530,BAN
DINDICATOR=GSM_PCS1900,CELLRESELPRIORITYCFGIND=NOT_CFG,PMAXGERANCFGIND=NOT_CFG,CON
NFREQPRIORITY=5;
ADD GERANNFREQGROUPARFCN:LOCALCELLID=0,BCCHGROUPID=0,GERANARFCN=531;
ADD GERANRANSHARE:LOCALCELLID=0,BCCHGROUPID=0,MCC="460",MNC="03";
MOD ENODEBALGOSWITCH:HOALGOSWITCH=GERANCSFBSWITCH-1,HOMODESWITCH=BLINDHOSWITCH-1;
(Optional) MOD CSFALLBACKPOLICYCFG:CSFBHOPOLICYCFG=REDIRECTION-1;
ADD
CELLOPHOCFG:LOCALCELLID=0,CNOPERATORID=0,INTERRATHIGHESTPRI=GERAN,INTERRATSECONDPR
I=UTRAN;

The activation observation procedure for CSFB to GERAN is as follows:
1. Enable a UE to camp on an E-UTRAN cell and initiate a voice call.
2. Enable the UE to camp on an E-UTRAN cell and receive a voice call. If the calls
continue until they are ended, CSFB to GERAN takes effect. You can observe the
signaling procedures for CSFB to GERAN.
Figure 7-9 describes the signaling procedure of redirection-based CSFB to GERAN.

Pico LTE
NOTE
In this procedure and follow-up procedures, the UEs in the left and right are the same UE. The signaling
process on the GERAN is for reference only. Compared with the redirection-based CSFB to GERAN
process on the mobile-originated call, the process on the mobile-terminated call incorporates the paging
process.
Figure 7-9 Redirection-based CSFB to GERAN for a mobile-originated call
If the UE capability is not included in the Initial Context Setup Request (Initial Context Setup
Req in the figure) message, the eNodeB initiates a UE capability transfer procedure
immediately after receiving this message from the MME. If the UE capability is included in
the Initial Context Setup Request message, the eNodeB initiates a UE capability transfer
procedure after sending an Initial Context Setup Response (Initial Context Setup Rsp in the
figures) message to the MME.
If the blind redirection is used for CSFB to GERAN, the eNodeB does not deliver the B1-
related measurement configuration but sends an RRC Connection Release (RRC Conn Rel in

Pico LTE
the figure) message to the UE. As shown in the red and green boxes in Figure 7-10, in the
RRC Connection Release message, the cause value is "other" and the target RAT is GERAN.
Figure 7-10 RRC Connection Release message during CSFB to GERAN
Counter Observation
Figure 7-9 lists the performance counters for observing functions related to CSFB to
GERAN.
Table 7-17 Performance counters for observing CSFB to GERAN

ID
CS Fallback to 152672832 L.CSFB.E2G Number of procedures for

GERAN 4 CSFB to GERAN
CSFB to 152672871 L.CSFB.E2G.Emergency Number of CSFB-based

GERAN 0 emergency calls from E-
Triggered for UTRAN to GERAN
Emergency
Calls
7.3.8 Deactivation
eNodeBs. This method reconfigures all data for multiple eNodeBs in a single procedure. The
procedure for feature deactivation is similar to that for feature activation described in 7.3.6.2
Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure,
modify parameters according to Table 7-18.

Pico LTE
Table 7-18 Parameters for deactivating CSFB to GERAN

ENodeBAlgoSwit User-defined sheet HoAlgoSwit To deactivate CSFB to

ch EnodeBAlgoSwitch is ch GERAN, set
recommended. GeranCsfbSwitch(GeranCs
fbSwitch) under the
Handover Algo switch
parameter to 0.

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

Run the MOD ENODEBALGOSWITCH command with the
GeranCsfbSwitch(GeranCsfbSwitch) check box cleared under the Handover Algo switch
parameter.

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-0;

CSFB is an end end-to to-end service. The performance counters on the LTE side can only
indicate the success rate of the CSFB procedure on the LTE side, and. they cannot indicate the
success rate of the CSFB procedure on the target side. Therefore, the performance counters on
the LTE side cannot directly show user experience of the CSFB procedure. It is recommended
that you perform drive tests and use the performance counters on the UE side to indicate the
actual user experience of the CSFB procedure.
Table 7-19 lists the counter related to CSFB to GERAN.
Table 7-19 Counter related to CSFB to GERAN

1526728324 L.CSFB.E2G Number of procedures for CSFB to GERAN
Table 7-20 lists the counter related to redirection-based CSFB to GERAN.

Pico LTE
Table 7-20 Counter related to redirection-based CSFB to GERAN
1526728498 L.RRCRedirection Number of CSFB-based redirections from E-

.E2G.CSFB UTRAN to GERAN
After the timer expires, the eNodeB may perform a blind redirection to enter the protection
procedure. Table 7-21 lists the counter related to the number of times that the eNodeB enters
the protection procedure for CSFB. A larger value of this counter indicates a longer average
UE access delay during CSFB.
Table 7-21 Counter related to the number of times that the eNodeB enters the protection
procedure for CSFB
1526729516 L.RRCRedirection Number of CSFB-based blind redirections

.E2G.CSFB.Time from E-UTRAN to UTRAN caused by timer
Out expiry

CSFB end-to-end delay includes the processing time at the LTE side and that at the side after
fallback. Processing at any side may affect the CSFB end-to-end delay and user experience.
Blind Handling for CSFB

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

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

Operator Cfg.CnOpe plan This parameter specifies the ID of the operator
ID ratorId (negotiatio whose RAT blind-handover priorities are to be
n not set.
required)
Highest CellOpHo Network Set this parameter based on the network plan.
priority Cfg.InterR plan This parameter specifies the RAT of the highest
InterRat atHighestP (negotiatio priority used for blind handovers in CSFB and is
ri n not set to UTRAN(UTRAN) by default.
required)

Pico LTE

r Name ID Source
Second CellOpHo Network Set this parameter based on the network plan.
priority Cfg.InterR plan This parameter specifies the RAT of the second
InterRat atSecondP (negotiatio highest priority used for blind handovers in CSFB
ri n not and is set to GERAN(GERAN) by default.
required) Values of Highest priority InterRat and Second
priority InterRat must be different.
The following table describes the parameters in the ENodeBAlgoSwitch MO used to activate
or deactivate blind handovers.
Parameter Paramete Data Setting Notes

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

Mode switch lgoSwitch plan BlindHoSwitch(BlindHoSwitch) option.
.HoMode (negotiati Compared with measurement-based handovers,
Switch on not blind handovers reduce access delays but cause
required) lower handover success rates.
To deactivate blind handovers, clear the
BlindHoSwitch(BlindHoSwitch) option.

Pico LTE
CS Fallback Feature Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
ENodeB HoAlgo MOD PLBFD- Coverag Meaning:

AlgoSwi Switch ENODE 002004 e-based Indicates whether to enable handover algorithms. The
tch BALGO PLOFD- Intra- switches are described as follows:
SWITC 001001 frequenc
H y IntraFreqCoverHoSwitch: If this switch is on,
PLBFD- Handov coverage-based intra-frequency handovers are enabled
LST 003001
ENODE er to ensure service continuity. If this switch is off,
BALGO PLBFD- Voice coverage-based intra-frequency handovers are
SWITC 002005 Services disabled.
H Inter- InterFreqCoverHoSwitch: If this switch is on,
RAT coverage-based inter-frequency handovers are enabled
Mobility to ensure service continuity. If this switch is off,
between coverage-based inter-frequency handovers are
E- disabled.
UTRAN
and UtranCsfbSwitch: If this switch is on, CSFB to
UTRAN UTRAN is enabled and UEs can fall back to UTRAN.
If this switch is off, CSFB to UTRAN is disabled.
Coverag
e-based UtranFlashCsfbSwitch: This switch takes effect only
Inter- when UtranCsfbSwitch is on. If UtranFlashCsfbS-
frequenc witch is on, flash CSFB to UTRAN is enabled and the
y eNodeB sends system information of candidate target
Handov UTRAN cells to UEs during redirection. If
er UtranFlashCsfbSwitch is off, flash CSFB to UTRAN
is disabled.
UtranCoverHoSwitch: If this switch is on, coverage-
based UTRAN handovers are enabled to ensure
service continuity. If this switch is off, coverage-based
UTRAN handovers are disabled.

Pico LTE

nd
GeranCsfbSwitch: If this switch is on, CSFB to

GERAN is enabled and UEs can fall back to GERAN.
If this switch is off, CSFB to GERAN is disabled.
GUI Value Range: IntraFreqCoverHoS-
witch(IntraFreqCoverHoSwitch), InterFreqCoverHoS-
witch(InterFreqCoverHoSwitch),
UtranCsfbSwitch(UtranCsfbSwitch),
UtranFlashCsfbSwitch(UtranFlashCsfbSwitch),
UtranCoverHoSwitch(UtranCoverHoSwitch),
GeranCsfbSwitch(GeranCsfbSwitch)
Unit: None
Actual Value Range: IntraFreqCoverHoSwitch,
InterFreqCoverHoSwitch, UtranCsfbSwitch,
UtranFlashCsfbSwitch, UtranCoverHoSwitch,
GeranCsfbSwitch
Default Value: IntraFreqCoverHoSwitch:On,
InterFreqCoverHoSwitch:Off, UtranCsfbSwitch:Off,
UtranFlashCsfbSwitch:Off, UtranCoverHoSwitch:Off,
GeranCsfbSwitch:Off

Pico LTE

nd
ENodeB HoMode MOD PLOFD- Voice Meaning:

AlgoSwi Switch ENODE 001001 Services Indicates the switches corresponding to the inputs
tch BALGO PLBFD- Inter- based on which the eNodeB determines handover
SWITC 003001 RAT policies.
H Mobility
LST between UtranVoipCapSwitch: If this switch is turned on,
ENODE E- UTRAN supports VoIP. If this switch is turned off,
BALGO UTRAN UTRAN does not support VoIP.
SWITC and UtranPsHoSwitch: If this switch is turned on, UTRAN
H UTRAN supports PS handovers. If this switch is turned off,
UTRAN does not support PS handovers.
UtranSrvccSwitch: If this switch is turned on, the
UTRAN supports single radio voice call continuity
(SRVCC). If this switch is turned off, the UTRAN
does not support SRVCC.
UtranRedirectSwitch: If this switch is turned on,
redirection to UTRAN is enabled. If this switch is
turned off, redirection to UTRAN is disabled.
BlindHoSwitch: If this switch is turned on, blind
handovers for CSFB are enabled. If this switch is
turned off, blind handovers for CSFB are disabled.
UeVoipOnHspaCapSwitch: If this switch is turned on
and the eNodeB attempts to hand over UEs using
voice services to UTRAN, the eNodeB checks UE
capabilities when determining whether PS handover is
applied. UEs must support voiceOverPS-HS-UTRA-
FDD-r9 if the target UTRAN cell works in FDD mode
or voiceOverPS-HS-UTRA-TDD128-r9 if the target
UTRAN cell works in TDD mode. If this switch is
turned off, the eNodeB does not check UE capabilities
when handing over UEs to UTRAN based on PS
handovers.
GUI Value Range:
UtranVoipCapSwitch(UtranVoipCapSwitch),
UtranPsHoSwitch(UtranPsHoSwitch),
UtranSrvccSwitch(UtranSrvccSwitch),
UtranRedirectSwitch(UtranRedirectSwitch),
BlindHoSwitch(BlindHoSwitch),
UeVoipOnHspaCapSwitch(UeVoipOnHspaCapS-
witch)
Unit: None
Actual Value Range: UtranVoipCapSwitch,
UtranPsHoSwitch, UtranSrvccSwitch,

Pico LTE

nd
UtranRedirectSwitch, BlindHoSwitch,
UeVoipOnHspaCapSwitch
Default Value: UtranVoipCapSwitch:Off,
UtranPsHoSwitch:Off, UtranSrvccSwitch:Off,
UtranRedirectSwitch:Off, BlindHoSwitch:Off,
UeVoipOnHspaCapSwitch:Off
CellOp InterRat ADD None None Meaning: Indicates the highest-priority RAT for
HoCfg Highest CellOp handovers. It is UTRAN by default. If this parameter
Pri HoCfg is set to UTRAN, GERAN, the highest-priority RAT
MOD is UTRAN, GERAN, respectively.
CellOp GUI Value Range: UTRAN(UTRAN),
HoCfg GERAN(GERAN)
LST Unit: None
CellOp Actual Value Range: UTRAN, GERAN
HoCfg
Default Value: UTRAN(UTRAN)
CellOp InterRat ADD None None Meaning: Indicates the medium-priority RAT for
HoCfg SecondP CellOp handovers. It is GERAN by default. If this parameter
ri HoCfg is set to UTRAN, GERAN, or CDMA2000, the
MOD medium-priority RAT is UTRAN, GERAN,
CellOp respectively. If this parameter is set to NULL, no
HoCfg medium-priority RAT is specified and only the
highest-priority RAT can be selected for handovers.
LST
CellOp GUI Value Range: UTRAN(UTRAN),
HoCfg GERAN(GERAN), NULL(NULL)
Unit: None
Actual Value Range: UTRAN, GERAN, NULL
Default Value: GERAN(GERAN)

Pico LTE

nd
UtranNF ConnFre ADD PLBFD- Inter- Meaning: Indicates the frequency priority based on
req qPriority UTRAN 003001 RAT which the eNodeB selects a target frequency for blind
NFREQ PLBFD- Mobility redirection or contains a frequency in a measurement
MOD 002006 between configuration. If a blind redirection is triggered and
UTRAN E- the target neighboring cell is not specified, the
PLOFD- UTRAN eNodeB selects a target frequency based on this
NFREQ 001001 and priority. If a measurement configuration is to be
LST UTRAN delivered, the eNodeB preferentially delivers a
UTRAN frequency with the highest priority. If this priority is
NFREQ Cell
Selectio set to 0 for a frequency, this frequency is not selected
n and as the target frequency for a blind redirection. A larger
Reselect value indicates a higher priority.
ion GUI Value Range: 0~8
Voice Unit: None
Services Actual Value Range: 0~8
Default Value: 0
UtranN CellMea ADD PLBFD- Inter- Meaning: Indicates the priority of measurement on the
Cell sPriority UTRAN 003001 RAT neighboring UTRAN cell. The eNodeB preferentially
NCELL PLOFD- Mobility contains the information about a neighboring cell with
MOD 001001 between this priority set to HIGH_PRIORITY while delivering
UTRAN E- a measurement configuration.
NCELL UTRAN GUI Value Range: LOW_PRIORITY(Low Priority),
and HIGH_PRIORITY(High Priority)
LST UTRAN
UTRAN Unit: None
NCELL Voice
Services Actual Value Range: LOW_PRIORITY,
HIGH_PRIORITY
Default Value: LOW_PRIORITY(Low Priority)
CSFallB CsfbHo MOD PLOFD- Voice Meaning: Indicates the RSCP threshold for event B1,
ackHo UtranB1 CSFAL 001001 Services which is used in CS fallback to UTRAN. When CS
ThdRsc LBACK fallback to UTRAN is applicable, this parameter is set
p HO for UEs and used in the evaluation about whether to
LST trigger event B1. This parameter indicates the RSCP
CSFAL requirement for the UTRAN cells to be included in the
LBACK measurement report. A UE sends a measurement
HO report related to event B1 to the eNodeB when the
RSCP in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For
details, see 3GPP TS 36.331.
GUI Value Range: -120~-25
Unit: dBm
Actual Value Range: -120~-25
Default Value: -106

Pico LTE

nd
InterRat InterRat MOD PLBFD- Inter- Meaning: Indicates the quantity to be included in the
HoCom HoUtran INTER 003001 RAT measurements for handovers to UTRAN. This
m B1Meas RATHO PLOFD- Mobility parameter is dedicated to UTRAN FDD. The RSCP
Quan COMM 001001 between values are relatively stable, while the Ec/No values
LST E- may vary with the network load. The value BOTH
INTER UTRAN applies only to UEs complying with 3GPP Release 10.
RATHO and For UEs complying with 3GPP Release 8 or 9, the
COMM UTRAN value BOTH takes the same effect as the value RSCP.
Voice For details, see 3GPP TS 23.003.
Services GUI Value Range: RSCP(RSCP), ECN0(ECN0),
BOTH(BOTH)
Unit: None
Actual Value Range: RSCP, ECN0, BOTH
Default Value: ECN0(ECN0)
CSFallB CsfbHo MOD PLOFD- Voice Meaning: Indicates the Ec/N0 threshold for event B1,
ackHo UtranB1 CSFAL 001001 Services which is used in CS fallback to UTRAN. When CS
ThdEcn LBACK fallback to UTRAN is required, this parameter is set
0 HO for UEs and used in the evaluation about whether to
LST trigger event B1. This parameter indicates the Ec/N0
CSFAL requirement for the UTRAN cells to be included in the
LBACK measurement report. A UE sends a measurement
HO report related to event B1 to the eNodeB when the
Ec/N0 in at least one UTRAN cell exceeds this
threshold and other triggering conditions are met. For
a cell with large signal fading variance, set this
parameter to a large value to prevent unnecessary
handovers. For a cell with small signal fading
variance, set this parameter to a small value to ensure
timely handovers. For details, see 3GPP TS 36.331.
GUI Value Range: -48~0
Unit: 0.5dB
Actual Value Range: -24~0
Default Value: -24

Pico LTE

nd
CSFallB CsfbHo MOD PLOFD- Voice Meaning: Indicates the time-to-trigger for event B1
ackHo UtranTi CSFAL 001001 Services that is used in CS fallback to UTRAN. When CS
meToTri LBACK fallback to UTRAN is applicable, this parameter is set
g HO for UEs and used in the evaluation of whether to
LST trigger event B1. When detecting that the signal
CSFAL quality in at least one UTRAN cell meets the entering
LBACK condition, the UE does not send a measurement report
HO to the eNodeB immediately. Instead, the UE sends a
report only when the signal quality continuously
meets the entering condition during the time-to-
trigger. This parameter helps decrease the number of
occasionally triggered event reports, the average
number of handovers, and the number of wrong
handovers, and thus helps to prevent unnecessary
handovers. For details, see 3GPP TS 36.331.
GUI Value Range: 0ms(0ms), 40ms(40ms),
64ms(64ms), 80ms(80ms), 100ms(100ms),
128ms(128ms), 160ms(160ms), 256ms(256ms),
320ms(320ms), 480ms(480ms), 512ms(512ms),
640ms(640ms), 1024ms(1024ms), 1280ms(1280ms),
2560ms(2560ms), 5120ms(5120ms)
Unit: ms
Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms,
1024ms, 1280ms, 2560ms, 5120ms
Default Value: 40ms(40ms)
UtranN BlindHo ADD PLBFD- Inter- Meaning: Indicates the priority of the neighboring cell
Cell Priority UTRAN 003001 RAT during blind handovers. Blind handover is a process in
NCELL PLOFD- Mobility which the eNodeB instructs a UE to hand over to a
MOD 001001 between specified neighboring cell. There are 32 priorities
UTRAN E- altogether. The priority has a positive correlation with
NCELL UTRAN the value of this parameter. Note that the value 0
and indicates that blind handovers to the neighboring cell
LST UTRAN are not allowed.
UTRAN
NCELL Voice GUI Value Range: 0~32
Services Unit: None
Actual Value Range: 0~32
Default Value: 0

Pico LTE

nd
CSFallB CsfbHo MOD PLOFD- Voice Meaning: Indicates the CSFB policy for a UE in
ackPolic PolicyCf CSFAL 001001 Services connected mode. If the CSFB steering function is
yCfg g LBACK disabled, this parameter also applies to UEs in idle
POLIC mode. The policy can be PS handover, or redirection.
YCFG GUI Value Range: REDIRECTION(REDIRECTION),
LST PS_HO(PS_HO)
CSFAL Unit: None
LBACK
POLIC Actual Value Range: REDIRECTION, PS_HO
YCFG Default Value: REDIRECTION:On, PS_HO:On
CSFallB CsfbUse MOD PLBFD- System Meaning: Indicates whether allocation/retention

ackPolic rArpCfg CSFAL 001001 Capabili priorities (ARPs) can be configured for CSFB services
yCfg Switch LBACK ty triggered by common calls. For details about ARPs,
POLIC see 3GPP TS 23.401.
YCFG GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
LBACK Actual Value Range: OFF, ON
POLIC Default Value: OFF(Off)
YCFG
CSFallB Normal MOD PLBFD- System Meaning: Indicates the allocation/retention priority
ackPolic CsfbUse CSFAL 001001 Capabili (ARP) of a CSFB service triggered by a common call.
yCfg rArp LBACK ty When this parameter is set to 1, the service priority is
POLIC the same as that of an emergency call. For details
YCFG about the ARP, see 3GPP TS 23.401.
LST GUI Value Range: 1~15
CSFAL Unit: None
LBACK
POLIC Actual Value Range: 1~15
YCFG Default Value: 2

Pico LTE

nd
ENodeB RimSwit MOD PLOFD- Voice Meaning: Indicates the collective switch for the RAN
AlgoSwi ch ENODE 001001 Services information management (RIM) function.
tch BALGO UTRAN_RIM_SWITCH: Indicates the switch used to
SWITC enable or disable the RIM procedure that requests
H event-driven multiple reports from UTRAN cells. If
LST this switch is turned on, the eNodeB can send RAN-
ENODE INFORMATION-REQUEST protocol data units
BALGO (PDUs) to UTRAN cells to request multiple event-
SWITC driven reports. If this switch is turned off, the eNodeB
H cannot send RAN-INFORMATION-REQUEST PDUs
to UTRAN cells to request multiple event-driven
reports.
GUI Value Range: UTRAN_RIM_SWITCH(UTRAN
RIM Switch)
Unit: None
Actual Value Range: UTRAN_RIM_SWITCH
Default Value: UTRAN_RIM_SWITCH:Off
UtranEx Rac ADD PLBFD- Inter- Meaning: Indicates the routing area code.
ternalCe UTRAN 003001 RAT GUI Value Range: 0~255
ll EXTER Mobility
NALCE between Unit: None
LL E- Actual Value Range: 0~255
MOD UTRAN Default Value: 0
UTRAN and
EXTER UTRAN
NALCE
LL
LST
UTRAN
EXTER
NALCE
LL
CSFallB LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
ackHo llId CSFAL identifies a cell within a BS.
LBACK GUI Value Range: 0~255
HO
Unit: None
MOD
CSFAL Actual Value Range: 0~255
LBACK Default Value: None
HO

Pico LTE
CS Fallback Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726989 L.IRATHO.E2W.Pr Number of inter- Multi-mode: None Voice Services

epAttOut RAT handover GSM: None Inter-RAT Mobility
attempts from E- between E-UTRAN
UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
PLOFD-001001
PLBFD-003001
1526726990 L.IRATHO.E2W.Ex Number of inter- Multi-mode: None Voice Services

ecAttOut RAT handover GSM: None Inter-RAT Mobility
executions from E- between E-UTRAN
UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
PLOFD-001001
PLBFD-003001
1526726991 L.IRATHO.E2W.Ex Number of Multi-mode: None Voice Services

ecSuccOut successful inter- GSM: None Inter-RAT Mobility
RAT handovers between E-UTRAN
from E-UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
PLOFD-001001
PLBFD-003001
1526727034 Handover from E- Success rate of Multi-mode: None Voice Services

UTRAN to inter-RAT GSM: None Inter-RAT Mobility
WCDMA Success handovers from E- between E-UTRAN
Rate UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
PLOFD-001001
PLBFD-003001

Pico LTE

Description
1526727226 L.IRATHO.E2T.Pre Number of inter- Multi-mode: None Voice Services

pAttOut RAT Handover GSM: None Inter-RAT Mobility
Attempts from E- between E-UTRAN
UTRAN to TD- UMTS: None
and UTRAN
SCDMA network LTE:
PLOFD-001001
PLBFD-003001
1526727227 L.IRATHO.E2T.Ex Number of inter- Multi-mode: None Voice Services

ecAttOut RAT handover GSM: None Inter-RAT Mobility
and UTRAN
SCDMA network LTE:
PLOFD-001001
PLBFD-003001
1526727228 L.IRATHO.E2T.Ex Number of Multi-mode: None Voice Services

ecSuccOut successful inter- GSM: None Inter-RAT Mobility
and UTRAN
TD-SCDMA LTE:
network PLOFD-001001
PLBFD-003001
1526727349 L.PDCP.DL.RoHC. Compression rate of Multi-mode: None Voice Services

HdrCompRatio headers of all GSM: None
downlink PDCP
SDUs after the UMTS: None
ROHC LTE:
PLOFD-001001
1526727350 L.PDCP.DL.RoHC. Compression rate of Multi-mode: None Voice Services

PktCompRatio all downlink PDCP GSM: None
SDUs (including
headers and UMTS: None
payloads) after the LTE:
ROHC PLOFD-001001
1526727351 L.PDCP.UL.RoHC. Decompression Multi-mode: None Voice Services

FailDecompRatio failure rate of all GSM: None
uplink PDCP SDUs
after the ROHC UMTS: None
LTE:
PLOFD-001001

Pico LTE

Description

p.FailOut.MME RAT handover GSM: None Inter-RAT Mobility
preparation failures between E-UTRAN
and UTRAN
TD-SCDMA LTE:
network because of PLOFD-001001
faults on the MME PLBFD-003001
side

p.FailOut.NoReply RAT handover GSM: None Inter-RAT Mobility
and UTRAN
TD-SCDMA LTE:
network due PLOFD-001001
tobecause of no PLBFD-003001
responses from TD-
SCDMA network

p.FailOut.PrepFailu RAT handover GSM: None Inter-RAT Mobility
re preparation failures between E-UTRAN
because TD- UMTS: None
and UTRAN
SCDMA network LTE:
cells send handover PLOFD-001001
preparation failure PLBFD-003001
messages
1526728312 L.IRATHO.BlindH Number of inter- Multi-mode: None Voice Services

O.E2W.ExecAttOut RAT blind GSM: None Inter-RAT Mobility
handovers between E-UTRAN
executions from E- UMTS: None
and UTRAN
UTRAN to LTE:
WCDMA network PLOFD-001001
PLBFD-003001
1526728313 L.IRATHO.BlindH Number of Multi-mode: None Voice Services

O.E2W.ExecSuccO successful inter- GSM: None Inter-RAT Mobility
ut RAT blind between E-UTRAN
handovers from E- UMTS: None
and UTRAN
UTRAN to LTE:
PLBFD-003001

Pico LTE

Description

ep.FailOut.MME RAT handover GSM: None Inter-RAT Mobility
and UTRAN
WCDMA network LTE:
because of faults on PLOFD-001001
the MME side PLBFD-003001

ep.FailOut.PrepFail RAT handover GSM: None Inter-RAT Mobility
ure preparation failures between E-UTRAN
and UTRAN
WCDMA network LTE:
because WCDMA PLOFD-001001
network cells send PLBFD-003001
handover
preparation failure
messages

ep.FailOut.NoReply RAT handover GSM: None Inter-RAT Mobility
and UTRAN
WCDMA network LTE:
because of no PLOFD-001001
responses from PLBFD-003001
WCDMA network
1526728321 L.CSFB.PrepAtt Number of CSFB Multi-mode: None Voice Services

indicators received GSM: None
by the eNodeB
UMTS: None
LTE:
PLOFD-001001
1526728322 L.CSFB.PrepSucc Number of Multi-mode: None Voice Services

successful CSFB GSM: None
responses from the
eNodeB UMTS: None
LTE:
PLOFD-001001
1526728323 L.CSFB.E2W Number of Multi-mode: None Voice Services

procedures for GSM: None
CSFB to WCDMA
network UMTS: None
LTE:
PLOFD-001001

Pico LTE

Description
1526728326 L.RRCRedirection. Number of Multi-mode: None Voice Services

E2W redirections from E- GSM: None Inter-RAT Mobility
UTRAN to between E-UTRAN
WCDMA network UMTS: None
and UTRAN
LTE:
PLOFD-001001
PLBFD-003001

O.E2W.PrepAttOut RAT blind GSM: None Inter-RAT Mobility
handover attempts between E-UTRAN
and UTRAN
WCDMA network LTE:
PLOFD-001001
PLBFD-003001

E2W.PrepAtt redirection GSM: None Inter-RAT Mobility
preparations from between E-UTRAN
E-UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
PLOFD-001001
PLBFD-003001

epAttOut.PLMN RAT handover GSM: None Inter-RAT Mobility
attempts from E- between E-UTRAN
UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
for a specific PLOFD-001001 RAN Sharing
operator PLBFD-003001
PLOFD-003001
1526728378 L.IRATHO.E2W.Ex Number of inter- Multi-mode: None Voice Services

ecAttOut.PLMN RAT handover GSM: None Inter-RAT Mobility
UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
PLOFD-003001

Pico LTE

Description
1526728379 L.IRATHO.E2W.Ex Number of Multi-mode: None Voice Services

ecSuccOut.PLMN successful inter- GSM: None Inter-RAT Mobility
and UTRAN
WCDMA network LTE:
PLOFD-003001
1526728387 L.CSFB.PrepSucc.I Number of Multi-mode: None Voice Services

dle successful CSFB GSM: None
responses from the
eNodeB for UEs in UMTS: None
idle mode LTE:
PLOFD-001001
1526728388 L.CSFB.E2W.Idle Number of Multi-mode: None Voice Services

CSFB to WCDMA
network for UEs in UMTS: None
idle mode LTE:
PLOFD-001001

O.E2W.PrepAttOut. RAT blind GSM: None Inter-RAT Mobility
PLMN handover attempts between E-UTRAN
and UTRAN
WCDMA network LTE:
PLOFD-003001

O.E2W.ExecAttOut RAT blind GSM: None Inter-RAT Mobility
.PLMN handover between E-UTRAN
and UTRAN
UTRAN to LTE:
WCDMA network PLOFD-001001 RAN Sharing
for a specific PLBFD-003001
operator
PLOFD-003001

Pico LTE

Description

O.E2W.ExecSuccO successful inter- GSM: None Inter-RAT Mobility
ut.PLMN RAT blind between E-UTRAN
handover UMTS: None
and UTRAN
executions from E- LTE:
UTRAN to RAN Sharing
PLOFD-001001
WCDMA network
for a specific PLBFD-003001
operator PLOFD-003001
1526728400 L.IRATHO.SRVCC Number of inter- Multi-mode: None Voice Services

.E2W.PrepAttOut RAT handover GSM: None
attempts from E-
UTRAN to UMTS: None
WCDMA network LTE:
for SRVCC PLOFD-001001

.E2W.ExecAttOut RAT handover GSM: None
executions from E-
UTRAN to UMTS: None
WCDMA network LTE:
1526728402 L.IRATHO.SRVCC Number of Multi-mode: None Voice Services

.E2W.ExecSuccOut successful inter- GSM: None
RAT handovers
WCDMA network LTE:

.E2T.PrepAttOut RAT handover GSM: None
attempts from E-
SCDMA network LTE:

.E2T.ExecAttOut RAT handover GSM: None
executions from E-
SCDMA for LTE:
SRVCC PLOFD-001001

.E2T.ExecSuccOut successful inter- GSM: None
RAT handovers
TD-SCDMA LTE:
network for SRVCC PLOFD-001001

Pico LTE

Description
1526728497 L.RRCRedirection. Number of CSFB- Multi-mode: None Voice Services

E2W.CSFB based redirections GSM: None
from E-UTRANs to
LTE:
PLOFD-001001

E2T.CSFB based redirections GSM: None
from E-UTRAN to
TD-SCDMA UMTS: None
network LTE:
PLOFD-001001
1526728504 L.IRATHO.E2W.C Number of CSFB- Multi-mode: None Voice Services

SFB.PrepAttOut based inter-RAT GSM: None
handover
preparation UMTS: None
attempts from E- LTE:
UTRAN to PLOFD-001001
WCDMA network

SFB.ExecAttOut based inter-RAT GSM: None
handover execution
attempts from E- UMTS: None
UTRAN to LTE:
1526728506 L.IRATHO.E2W.C Number of Multi-mode: None Voice Services

SFB.ExecSuccOut successful CSFB- GSM: None
based inter-RAT
handover UMTS: None
UTRAN to PLOFD-001001
WCDMA network
1526728510 L.IRATHO.E2T.CS Number of CSFB- Multi-mode: None Voice Services

FB.PrepAttOut based inter-RAT GSM: None
handover
preparation UMTS: None
attempts from E- LTE:
UTRAN to TD- PLOFD-001001
SCDMA network

FB.ExecAttOut based inter-RAT GSM: None
handover execution
UTRAN to TD- LTE:
SCDMA network PLOFD-001001

Pico LTE

Description
1526728512 L.IRATHO.E2T.CS Number of Multi-mode: None Voice Services

FB.ExecSuccOut successful CSFB- GSM: None
based inter-RAT
handover UMTS: None
UTRAN to TD- PLOFD-001001
SCDMA network
1526728513 L.CSFB.PrepFail.C Number of CSFB Multi-mode: None Voice Services

onflict preparation failures GSM: None
because of process
conflict UMTS: None
LTE:
PLOFD-001001
1526728522 L.PDCP.UL.RoHC. Compression rate of Multi-mode: None Voice Services

HdrCompRatio headers of all GSM: None
uplink PDCP SDUs
UMTS: None
LTE:
PLOFD-001001
1526728523 L.PDCP.UL.RoHC. Compression rate of Multi-mode: None Voice Services

PktCompRatio all uplink PDCP GSM: None
SDUs (including
headers and UMTS: None
payloads) after the LTE:
ROHC. PLOFD-001001
1526728524 L.Traffic.User.RoH Maximum number Multi-mode: None Voice Services

C.Max of UEs on which GSM: None
ROHC takes effect
in a cell UMTS: None
LTE:
PLOFD-001001
1526728525 L.Traffic.User.RoH Average number of Multi-mode: None Voice Services

C.Avg UEs on which GSM: None
ROHC takes effect
in a cell UMTS: None
LTE:
PLOFD-001001
1526728560 L.IRATHO.E2W.N Number of inter- Multi-mode: None Voice Services

oData.ExecAttOut RAT handover GSM: None Inter-RAT Mobility
UTRAN to UMTS: None
and UTRAN
WCDMA network LTE:
triggered for UEs PLOFD-001001
that do not transmit PLBFD-003001
or receive data

Pico LTE

Description
1526728561 L.IRATHO.E2W.N Number of Multi-mode: None Voice Services

oData.ExecSuccOut successful inter- GSM: None Inter-RAT Mobility
and UTRAN
WCDMA network LTE:
triggered for UEs PLOFD-001001
that do not transmit PLBFD-003001
or receive data
1526728707 L.CSFB.PrepAtt.E Number of CSFB Multi-mode: None Voice Services

mergency indicators received GSM: None
by the eNodeB for
emergency calls UMTS: None
LTE:
PLOFD-001001
1526728708 L.CSFB.PrepSucc. Number of Multi-mode: None Voice Services

Emergency responses sent from GSM: None
the eNodeB for
CSFB triggered for UMTS: None
emergency calls LTE:
PLOFD-001001
1526728709 L.CSFB.E2W.Emer Number of Multi-mode: None Voice Services

gency procedures for GSM: None
CSFB to WCDMA
network triggered UMTS: None
for emergency calls LTE:
PLOFD-001001

O.E2T.PrepAttOut RAT blind GSM: None Inter-RAT Mobility
handover attempts between E-UTRAN
and UTRAN
TD-SCDMA LTE:
network PLOFD-001001
PLBFD-003001

O.E2T.ExecAttOut RAT blind GSM: None Inter-RAT Mobility
handover between E-UTRAN
and UTRAN
UTRAN to TD- LTE:
PLBFD-003001

Pico LTE

Description

O.E2T.ExecSuccOu successful inter- GSM: None Inter-RAT Mobility
t RAT blind between E-UTRAN
and UTRAN
UTRAN to TD- LTE:
PLBFD-003001
1526728749 L.CSFB.E2T Number of Multi-mode: None Voice Services

SRVCC to TD-
SCDMA network UMTS: None
LTE:
PLOFD-001001
1526728750 L.CSFB.E2T.Idle Number of Multi-mode: None Voice Services

SRVCC to TD-
for UEs in idle LTE:
mode PLOFD-001001

E2T.PrepAtt redirection GSM: None Inter-RAT Mobility
preparations to TD- between E-UTRAN
and UTRAN
LTE:
PLOFD-001001
PLBFD-003001

E2T redirections to TD- GSM: None Inter-RAT Mobility
SCDMA network between E-UTRAN
UMTS: None
and UTRAN
LTE:
PLOFD-001001
PLBFD-003001
1526728870 L.IRATHO.T2E.Pre Number of inter- Multi-mode: None Voice Services

pAttIn RAT handover GSM: None Inter-RAT Mobility
attempts from TD- between E-UTRAN
SCDMA network to UMTS: None
and UTRAN
E-UTRAN LTE:
PLOFD-001001
PLBFD-003001

Pico LTE

Description
1526728871 L.IRATHO.T2E.Pre Number of Multi-mode: None Voice Services

pInSucc successful inter- GSM: None Inter-RAT Mobility
RAT handover between E-UTRAN
preparations from UMTS: None
and UTRAN
TD-SCDMA LTE:
network to E- PLOFD-001001
UTRAN PLBFD-003001
1526728872 L.IRATHO.T2E.Ex Number of Multi-mode: None Voice Services

ecSuccIn successful inter- GSM: None Inter-RAT Mobility
from TD-SCDMA UMTS: None
and UTRAN
network to E- LTE:
UTRAN PLOFD-001001
PLBFD-003001
1526728873 L.IRATHO.T2E.Pre Number of inter- Multi-mode: None Voice Services

pInFail.TgtNotAllo RAT handover GSM: None Inter-RAT Mobility
w preparation failures between E-UTRAN
from TD-SCDMA UMTS: None
and UTRAN
network in the LTE:
target cell due to PLOFD-001001
Handover Target PLBFD-003001
not allowed
1526728874 L.IRATHO.W2E.Pr Number of inter- Multi-mode: None Voice Services

epAttIn RAT handover GSM: None Inter-RAT Mobility
attempts from between E-UTRAN
and UTRAN
to E-UTRAN LTE:
PLOFD-001001
PLBFD-003001
1526728875 L.IRATHO.W2E.Pr Number of Multi-mode: None Voice Services

epInSucc successful inter- GSM: None Inter-RAT Mobility
RAT handover between E-UTRAN
preparations from UMTS: None
and UTRAN
WCDMA network LTE:
to E-UTRAN PLOFD-001001
PLBFD-003001
1526728876 L.IRATHO.W2E.E Number of Multi-mode: None Voice Services

xecSuccIn successful inter- GSM: None Inter-RAT Mobility
from WCDMA UMTS: None
and UTRAN
network to E- LTE:
UTRAN PLOFD-001001
PLBFD-003001

Pico LTE

Description
1526728877 L.IRATHO.W2E.Pr Number of inter- Multi-mode: None Voice Services

epInFail.TgtNotAll RAT handover GSM: None Inter-RAT Mobility
ow preparation failures between E-UTRAN
from WCDMA UMTS: None
and UTRAN
network in the LTE:
target cell due to PLOFD-001001
Handover Target PLBFD-003001
not allowed

.E2W.MMEAbnor responses for GSM: None
mRsp abnormal causes
received by the UMTS: None
eNodeB from the LTE:
MME during inter- PLOFD-001001
RAT handover
executions from E-
UTRAN to
WCDMA network
for SRVCC

.E2T.MMEAbnorm responses for GSM: None
Rsp abnormal causes
MME during inter- PLOFD-001001
RAT handover
executions from E-
UTRAN to TD-
SCDMA network
for SRVCC

SFB.MMEAbnorm responses for GSM: None
Rsp abnormal causes
MME during PLOFD-001001
CSFB-based inter-
RAT handover
executions from E-
UTRAN to
WCDMA network

Pico LTE

Description
1526728900 L.IRATHO.E2G.CS Number of Multi-mode: None Voice Services

FB.MMEAbnormR responses for GSM: None
sp abnormal causes
CSFB-based inter-
RAT handover
executions from E-
UTRAN to
GERAN
1526728901 L.IRATHO.E2T.CS Number of Multi-mode: None Voice Services

FB.MMEAbnormR responses for GSM: None
sp abnormal causes
CSFB-based inter-
RAT handover
executions from E-
UTRAN to TD-
SCDMA network
1526729432 L.IRATHO.E2W.Ti Average handover Multi-mode: None Voice Services

meAvg duration from E- GSM: None Inter-RAT Mobility
and UTRAN
LTE:
PLOFD-001001
PLBFD-003001
1526729434 L.IRATHO.E2T.Ti Average handover Multi-mode: None Voice Services

meAvg duration from E- GSM: None Inter-RAT Mobility
UTRAN to TD- between E-UTRAN
and UTRAN
LTE:
PLOFD-001001
PLBFD-003001

E2W.PLMN redirections from E- GSM: None Inter-RAT Mobility
and UTRAN
for a specific LTE:
operator PLOFD-001001 RAN Sharing
PLBFD-003001
PLOFD-003001

Pico LTE

Description

SFB.PrepAttOut.E based handover GSM: None
mergency preparation
attempts to UMTS: None
WCDMA network LTE:
triggered for PLOFD-001001
emergency calls

SFB.ExecAttOut.E based handover GSM: None
mergency execution attempts
to WCDMA UMTS: None
network triggered LTE:
for emergency calls PLOFD-001001

SFB.ExecSuccOut. successful CSFB- GSM: None
Emergency based handover
executions to UMTS: None
WCDMA network LTE:
emergency calls

E2W.CSFB.TimeO based blind GSM: None
ut redirections from E-
UTRAN to UMTS: None
WCDMA network LTE:
caused by CSFB PLOFD-001001
protection timer
expiration
1526729517 L.EMC.SRVCC.E2 Number of Multi-mode: None Voice Services

W.PrepAttOut handover attempts GSM: None
from E-UTRAN to
for SRVCC LTE:
emergency calls

W.ExecAttOut handover GSM: None
executions from E-
UTRAN to UMTS: None
WCDMA network LTE:
triggered for
emergency calls

Pico LTE

Description

W.ExecSuccOut successful GSM: None
handovers from E-
UTRAN to UMTS: None
WCDMA network LTE:
triggered for
emergency calls

T.PrepAttOut handover attempts GSM: None
from E-UTRAN to
TD-SCDMA UMTS: None
network for SRVCC LTE:
emergency calls

T.ExecAttOut handover GSM: None
executions from E-
SCDMA network LTE:
triggered for
emergency calls

T.ExecSuccOut successful GSM: None
handovers from E-
SCDMA network LTE:
triggered for
emergency calls
1526729565 L.IRATHO.NCell.E Number of Multi-mode: None Voice Services

2W.PrepAttOut handover attempts GSM: None Inter-RAT Mobility
from a specific E- between E-UTRAN
UTRAN cell to a UMTS: None
and UTRAN
specific WCDMA LTE:
cell PLOFD-001001
PLBFD-003001

2W.ExecAttOut handover GSM: None Inter-RAT Mobility
executions from a between E-UTRAN
specific E-UTRAN UMTS: None
and UTRAN
cell to a specific LTE:
WCDMA cell PLOFD-001001
PLBFD-003001

Pico LTE

Description

2W.ExecSuccOut successful GSM: None Inter-RAT Mobility
handovers from a between E-UTRAN
specific E-UTRAN UMTS: None
and UTRAN
cell to a specific LTE:
WCDMA cell PLOFD-001001
PLBFD-003001
1526730044 L.CSFB.PrepAtt.PL Number of CSFB Multi-mode: None Voice Services

MN indicators received GSM: None RAN Sharing
by the eNodeB for a
specific operator UMTS: None
LTE:
PLOFD-001001
PLOFD-003001
1526730045 L.CSFB.PrepSucc.P Number of Multi-mode: None Voice Services

LMN successful CSFB GSM: None RAN Sharing
responses sent from
the eNodeB for a UMTS: None
specific operator LTE:
PLOFD-001001
PLOFD-003001

E2W.CSFB.PLMN based redirections GSM: None RAN Sharing
from E-UTRAN to
for a specific LTE:
PLOFD-003001

SFB.PrepAttOut.PL based handover GSM: None RAN Sharing
MN preparation
UTRAN to LTE:
for a specific PLOFD-003001
operator

SFB.ExecAttOut.P based handover GSM: None RAN Sharing
LMN execution attempts
WCDMA network LTE:

Pico LTE

Description

SFB.ExecSuccOut. successful CSFB- GSM: None RAN Sharing
PLMN based handover
UTRAN to LTE:
operator
1526730054 L.IRATHO.SRVCC Number of SRVCC- Multi-mode: None Voice Services

.E2W.PrepAttOut.P based outgoing GSM: None RAN Sharing
LMN handover attempts
WCDMA network LTE:
1526730055 L.IRATHO.SRVCC Number of SRVCC- Multi-mode: None Voice Services

.E2W.ExecAttOut.P based outgoing GSM: None RAN Sharing
LMN handover
UTRAN to LTE:
operator

.E2W.ExecSuccOut. successful SRVCC- GSM: None RAN Sharing
PLMN based outgoing
UTRAN to LTE:
operator

SFB.Prep.FailOut. based outgoing GSM: None
MME handover
preparation failures UMTS: None
from E-UTRAN to LTE:
because of the
MME side causes

Pico LTE

Description

SFB.Prep.FailOut.P based outgoing GSM: None
repFailure handover
because of the
response of
handover
preparation failure
from WCDMA
network

SFB.Prep.FailOut.N based outgoing GSM: None
oReply handover
because of no
response from
WCDMA network

FB.Prep.FailOut.M based outgoing GSM: None
ME handover
TD-SCDMA PLOFD-001001
network because of
the MME side
causes

FB.Prep.FailOut.Pr based outgoing GSM: None
epFailure handover
network because of
the response of
handover
preparation failure
from TD-SCDMA
network

Pico LTE

Description

FB.Prep.FailOut.No based outgoing GSM: None
Reply handover
network because of
no response from
TD-SCDMA
network
1526730082 L.IRATHO.E2W.S Number of SRVCC- Multi-mode: None Voice Services

RVCC.Prep.FailOut based outgoing GSM: None
.MME handover
because of the
MME side causes

.PrepFailure handover
because of the
response of
handover
preparation failure
from WCDMA
network

.NoReply handover
because of no
response from
WCDMA network

Pico LTE

Description
1526730085 L.IRATHO.E2T.SR Number of SRVCC- Multi-mode: None Voice Services

VCC.Prep.FailOut. based outgoing GSM: None
MME handover
network because of
the MME side
causes

PrepFailure handover
network because of
the response of
handover
preparation failure
from TD-SCDMA
network

NoReply handover
network because of
no response from
TD-SCDMA
network
1526730091 L.IRATHO.SRVCC Number of CS-only Multi-mode: None Voice Services

.CSonly.E2W.Prep SRVCC-based GSM: None
AttOut outgoing handover
UTRAN to LTE:

.CSonly.E2W.Exec SRVCC-based GSM: None
AttOut outgoing handover
UTRAN to LTE:

Pico LTE

Description

.CSonly.E2W.Exec successful CS-only GSM: None
SuccOut SRVCC-based
outgoing handovers UMTS: None

.CSonly.E2T.PrepA SRVCC-based GSM: None
ttOut outgoing handover
UTRAN to TD- LTE:

.CSonly.E2T.ExecA SRVCC-based GSM: None
ttOut outgoing handover
UTRAN to TD- LTE:

.CSonly.E2T.ExecS successful CS-only GSM: None
uccOut SRVCC-based
outgoing handovers UMTS: None
network
1526730146 L.IRATHO.CSFB.S Number of SRVCC- Multi-mode: None Voice Services

RVCC.E2W.PrepAt based outgoing GSM: None
tOut handover attempts
WCDMA network LTE:
for ultra-flash PLOFD-001001
CSFB
1526730147 L.IRATHO.CSFB.S Number of SRVCC- Multi-mode: None Voice Services

RVCC.E2W.ExecAt based outgoing GSM: None
tOut handover
UTRAN to LTE:
for ultra-flash
CSFB

Pico LTE

Description
1526730148 L.IRATHO.CSFB.S Number of Multi-mode: None Voice Services

RVCC.E2W.ExecS successful SRVCC- GSM: None
uccOut based outgoing
UTRAN to LTE:
for ultra-flash
CSFB

Pico LTE
CS Fallback Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

Pico LTE
CS Fallback Feature Parameter Description 11 Reference Documents
11 Reference Documents
1. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"
2. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC); Stage 2"
3. VoLGA Forum Specifications
4. 3GPP TS 36.300, "E-UTRAN Overall description"
5. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
6. 3GPP TS 48.018, "General Packet Radio Service (GPRS); Base Station System (BSS) -
Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP)"
7. Inter-RAT Mobility Management in Connected Mode Feature Parameter Description
8. Emergency Call Feature Parameter Description


CS Fallback (Pico10.1 - Draft A)

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 (Pico10.1 - Draft A)

Uploaded by

Copyright:

Available Formats

Pico LTE

CS Fallback Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential ii

4.1 CS Fallback to GERAN................................................................................................................................................27

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential iii

7.3.2 Required Information................................................................................................................................................ 61

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential iv

1 About This Document

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Pico10.1 Draft A (2015-11-30)

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 1

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 2

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 3

Figure 2-1 Architecture for CSFB to UTRAN/GERAN

Table 1 lists the NEs and interface involved in CSFB to UTRAN/GERAN.

Table 2-1 NEs and interface involved in CSFB to UTRAN/GERAN

UE l Accesses the EPS and the UTRAN.

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 4

MME l Supports the SGs interface to the MSC server/VLR.

MSC l Supports combined EPS/IMSI attach.

E-UTRAN l Forwards paging messages related to CSFB.

UTRAN Supports one or more of the following functions:

SGSN Supports follow-up procedures performed for PS handovers, including

2.4 Overall Process

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 5

Table 2-2 CSFB to UTRAN/GERAN

Normal Procedure Measurement-based Supported Not supported

Blind handover Supported Supported

The timer expires. Blind redirection Supported Supported

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 6

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 7

3.1 Basic CSFB to UTRAN

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 8

Table 3-1 Parameters related to event B1 for CSFB to UTRAN

CSFB UTRAN EventB1 CSFallBackHo.CsfbHo The

CSFB Utran EventB1 CSFallBackHo.CsfbHo -

3.1.2 Blind Handling

Triggering of Blind Handling

Target Cell Selection

l Blacklisted neighboring cells

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 9

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 10

3.2 Flash CSFB to UTRAN

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 11

3.3 Handover Decision

3.3.1 Basic Handover Decision

l Blacklisted neighboring cells

Table 3-2 Sequence of handover requests to be sent by the eNodeB

If the handover request fails in all candidate cells:

3.3.2 Decision Based on System Information

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 12

Decision based on system information adheres to the following principles:

l In blind handling scenarios:

The eNodeB supports a maximum number of 16 UTRAN cells contained in a redirection

3.4.1 Handover Policy Selection

Issue Draft A (2015-11-30) Huawei Proprietary and Confidential 13