Professional Documents
Culture Documents
Issue Draft A
Date 2015-11-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 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
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.2 Required Information................................................................................................................................................ 51
7.2.3 Requirements............................................................................................................................................................. 52
7.2.4 Data Preparation........................................................................................................................................................ 52
7.2.5 Precautions.................................................................................................................................................................55
7.2.6 Activation.................................................................................................................................................................. 55
7.2.6.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................55
7.2.6.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 56
7.2.6.3 Using the CME to Perform Single Configuration.................................................................................................. 57
7.2.6.4 Using MML Commands......................................................................................................................................... 58
7.2.7 Activation Observation..............................................................................................................................................59
7.2.8 Deactivation...............................................................................................................................................................60
7.2.9 Performance Monitoring............................................................................................................................................60
7.2.10 Parameter Optimization........................................................................................................................................... 61
7.3 CS Fallback to GERAN................................................................................................................................................61
7.3.1 When to Use CS Fallback to GERAN.......................................................................................................................61
8 Parameters..................................................................................................................................... 74
9 Counters........................................................................................................................................ 83
10 Glossary..................................................................................................................................... 106
11 Reference Documents............................................................................................................. 107
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.
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.
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.
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.
NE and Function
Interface
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.
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.
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.
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.
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.
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.
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)
Figure 3-2 Target cell selection (configured with no neighboring UTRAN cell)
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.
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.
reading cell system information is not required so that the UE can quickly access the target
network.
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
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.
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.
NOTE
The symbols that appear in signaling procedure figures throughout this document are explained as
follows:
l An arrow denotes the transmission of a message.
l A plain box denotes a mandatory procedure.
l A dashed box denotes an optional procedure.
1. The UE sends 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.
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.
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 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.
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 CSFB to UTRAN based on flash redirection 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 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.
As the SMS service is transparent to the eNodeB, the procedure is not described in this
document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.
the 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.
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.
4.2 Execution
CSFB to GERAN can be achieved only through redirections. Figure 4-1 shows the CSFB to
GERAN procedure.
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 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.
5 Related Features
Affected Features
None
Affected Features
None
6 Network Impact
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
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.
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.
7 Engineering Guidelines
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.
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.
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.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to set the handover mode and handover algorithm switches for CSFB to UTRAN.
Handover 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.
The following table describes the parameters that must be set in the CSFallBackPolicyCfg
MO to specify the CSFB policy.
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.
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.
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.
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:
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
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
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
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
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.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO 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
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.
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
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.
Step 3 Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO 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
Signaling Observation
The activation observation procedure for CSFB to UTRAN is as follows:
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."
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.
Counter Observation
Table 7-4 lists the performance counters for observing functions related to CSFB to UTRAN.
7.1.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in 7.1.6.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 7-5.
Table 7-8 lists the counters that indicate whether CSFB is performed through redirections or
through handovers.
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
Counter ID Counter Name Description
Table 7-10 lists the counters related to CSFB for emergency calls.
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.
Local cell CSFallBac Network Set this parameter based on the network plan.
ID kHo.Local plan
CellId (negotiatio
n not
required)
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.
7.2.3 Requirements
Operating Environment
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.
NOTE
If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN.
Required Data
Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with
UTRAN cells. This section provides only the information about MOs related to neighboring
UTRAN cells and key parameters in these MOs. For more information about how to collect
data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected
Mode Feature Parameter Description.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to set the handover mode and handover algorithm switches for flash CSFB to UTRAN.
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.
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.
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.2.5 Precautions
None
7.2.6 Activation
7.2.6.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 7-12 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-12 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-12 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.
When configuring neighboring cells, you are advised to use the radio data planning file.
7.2.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:
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
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 7-7, select the eNodeB to which the MOs belong.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or
choose Area Management > Planned Area > Export Incremental Scripts (CME client
mode), to export and activate the incremental scripts.
----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 not a Huawei device, modify the RIM Coding Policy parameter. Run the
MOD GLOBALPROCSWITCH command to set the RIM Coding Policy parameter to
StandardCoding.
----End
Signaling Observation
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.
Counter Observation
Table 7-13 lists the performance counters for observing functions related to flash CSFB to
UTRAN.
7.2.8 Deactivation
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
NE Function
SGSN Does not activate ISR during the combined RAU/LAU procedure
initiated by the UE.
7.3.3 Requirements
Operating Environment
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.
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.
Scenario-specific Data
The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO
to set the handover mode and handover algorithm switches for CSFB to GERAN.
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
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.
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)
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. If CSFB to
not GERAN is used, set this parameter to
require GERAN(GERAN).
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)
The following table describes the parameters that must be set in the CSFallBackPolicyCfg
MO to specify the CSFB policy.
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.
7.3.5 Precautions
None
7.3.6 Activation
7.3.6.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 7-16 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 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-16 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-16 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.
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
7.3.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 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.
Step 2 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.
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.
Step 3 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 export the eNodeB
data stored on the CME into the customized summary data file.
Step 4 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
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 7-8, select the eNodeB to which the MOs belong.
----End
Step 2 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 4 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
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.
Step 2 Run the MOD ENODEBALGOSWITCH command with both the
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
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;
ADD
CELLOPHOCFG:LOCALCELLID=0,CNOPERATORID=0,INTERRATHIGHESTPRI=GERAN,INTERRATSECONDPR
I=UTRAN;
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.
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
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.
Counter Observation
Figure 7-9 lists the performance counters for observing functions related to CSFB to
GERAN.
7.3.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data 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.
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
The following table describes the parameters in the CellOpHoCfg MO used to set the blind
handover priorities of different RATs for CSFB.
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.
8 Parameters
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)
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
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
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
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 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
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
9 Counters
10 Glossary
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