CSFB

Contents
3.6.1 CSFB

GSM BSS
GBSS21.1
CSFB Feature Parameter Description

Issue 01
Date 2019-06-06
 HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: https:/

Email: support@huawei.com

3.6.1 Contents
1 About This Document
1.1 Scope
1.2 General Statements
1.3 Change History

2 Overview
2.1 Background
2.2 Introduction
2.2.1 CSFB
2.2.2 Ultra-Flash CSFB
2.3 Benefits
2.3.1 CSFB
2.3.2 Ultra-Flash CSFB
2.4 Feature Support by NE

3 Technical Description
3.1 CSFB
3.1.1 MOC CSFB
3.1.2 MTC CSFB
3.2 Ultra-Flash CSFB

4 Related Features
4.1 GBFD-511313 CSFB
4.2 GBFD-171212 Ultra-Flash CSFB

5 Network Impact
5.1 GBFD-511313 CSFB
5.2 GBFD-171212 Ultra-Flash CSFB

6 Engineering Guidelines
6.1 GBFD-511313 CSFB
6.1.1 When to Use CSFB
6.1.2 Required Information
6.1.3 Planning
6.1.4 Deploying CSFB
6.1.4.1 Deployment Requirements
6.1.4.2 Data Preparation and Feature Activation
6.1.4.2.1 Data Preparation
6.1.4.2.2 Using MML Commands
6.1.4.2.3 MML Command Examples
6.1.4.2.4 Using the CME
6.1.4.3 Activation Observation
6.1.4.4 Feature Deactivation
6.1.4.4.1 Using MML Commands
6.1.4.4.2 MML Command Examples
6.1.4.4.3 Using the CME
6.1.5 Performance Monitoring
6.1.6 Parameter Optimization
6.1.7 Troubleshooting
6.2 GBFD-171212 Ultra-Flash CSFB
6.2.1 When to Use Ultra-Flash CSFB
6.2.2 Required Information
6.2.3 Network Planning
6.2.4 Deploying Ultra-Flash CSFB
6.2.4.1 Deployment Requirements
6.2.4.2 Data Preparation and Feature Activation
6.2.4.2.1 Data Preparation
6.2.4.2.2 Using MML Commands
6.2.4.2.3 MML Command Examples
6.2.4.2.4 Using the CME
6.2.4.3 Activation Observation
6.2.4.4 Feature Deactivation
6.2.4.4.1 Using MML Commands
6.2.4.4.2 MML Command Examples
6.2.4.4.3 Using the CME
6.2.5 Performance Monitoring
6.2.6 Parameter Optimization
6.2.7 Troubleshooting

7 Parameters

8 Counters

9 Glossary

10 Reference Documents
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.
This document covers the following features:
 GBFD-511313 CSFB
 GBFD-171212 Ultra-Flash CSFB
1.2 General Statements

Purpose

Feature Parameter Description documents are intended to acquaint readers with:

 The technical principles of features and their related parameters
 The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
 Requirements of the operating environment that must be met before feature activation
 Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance

This document only provides guidance for feature activation. Feature deployment and feature gains depend
on the specifics of the network scenario where the feature is deployed. To achieve the desired gains, contact
Huawei professional service engineers.

Software Interfaces

Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter
Description documents apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
1.3 Change History

This section provides information about the changes in different document versions. There
are two types of changes:
 Feature change
Changes in features and parameters of a specified version
 Editorial change
 Changes in wording or addition of information and any related parameters affected by
editorial changes

01 (2019-06-06)

This issue does not include any changes.

Draft A (2018-12-30)

GBSS21.1 Draft A (2018-12-30) introduces the following changes to GBSS19.1 01 (2016-

12-30).

Change Type Change Description Parameter Change

Feature Added the dependency description None

change about the eNACC Between GSM
and LTE feature. For details, see 4.1
GBFD-511313 CSFB.

Editorial None None

change

2 Overview

With the development of radio communication technologies, operators start to deploy LTE
networks. The coexistence of the GSM and LTE networks inevitably involves the
interoperations between them. Therefore, Huawei provides GSM/LTE interoperability
features.

 UEs in this document refer to dual-mode or multimode UEs supporting both GSM and LTE networks.
 This document applies to LTE FDD and LTE TDD. Any "LTE" in this document refers to both LTE
FDD and LTE TDD.

2.1 Background

As an IP network, an LTE network is typically deployed with an IP multimedia subsystem

(IMS) to support circuit switched (CS) services. At the initial stage of LTE network
deployment, some operators expect to provide CS services without deploying an IMS. If the
core network (CN) is not deployed with an IMS, the LTE network cannot use voice over IP
(VoIP) to carry CS services.
2.2 Introduction

2.2.1 CSFB
 With CSFB, a UE initiating CS services in an LTE cell is migrated to a GSM cell and then
performs CS services on the GSM network.
2.2.2 Ultra-Flash CSFB

When CSFB is enabled, a UE in an LTE cell must migrate to a GSM cell to perform CS
services, increasing the call setup delay.
The Ultra-Flash CSFB feature is introduced to speed up the CSFB procedure. When Ultra-
Flash CSFB is enabled, the GSM network prepares CS resources in advance for a UE using
the single radio voice call continuity (SRVCC) handover procedure. This way, the CS
resource establishment procedure is not required after the UE migrates to the GSM network.
In addition, Ultra-Flash CSFB eliminates the authentication, encryption, and international
mobile equipment identity (IMEI) query procedures on the GSM network, decreasing the call
setup delay and improving user experience.
2.3 Benefits

2.3.1 CSFB

The CSFB feature provides the following benefits:

 Allows operators to provide CS services without deploying an IMS at the initial stage
of LTE network deployment.
 Allows UEs in areas covered by both GSM and LTE networks to process CS services
on the GSM network, fully utilizing legacy GSM networks.
2.3.2 Ultra-Flash CSFB

In addition to benefits provided by CSFB, Ultra-Flash CSFB reduces the LTE-to-GSM CSFB
delay by 1s to 2s, improving user experience.
2.4 Feature Support by NE

Table 2-1 Feature support by NE

Feature BSC6900 BSC6910 GBTS eGBTS

CSFB √ √ √ √

Ultra-Flash √ √ √ √
CSFB

√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.

3 Technical Description

3.1 CSFB
On a CSFB-enabled network, the CS service of a UE camping on an LTE cell is migrated to a
GSM cell after the UE originates a CS call or receives a CS paging message. A CSFB call
follows the same procedure as that when the UE camps on a GSM cell.
3.1.1 MOC CSFB

A UE in idle mode or during a PS service initiates a CS call on an LTE network. To proceed

with the call procedure, the eNodeB initiates mobile originated call (MOC) CSFB to migrate
the CS service of the UE to a GSM cell through PS handover, cell change order (CCO), or
redirection. Figure 3-1 shows the MOC CSFB procedure.
Figure 3-1 MOC CSFB procedure
In Figure 3-1, the procedures enclosed in the white dotted line frame are optional and those enclosed in the gray
dotted line frame have branch procedures.
 1. A UE sends an Extended Service Request message carrying the CS Fallback Indicator
information element (IE) to the mobility management entity (MME), instructing the
MME to initiate CSFB.

The UE sends an Extended Service Request message only when both the following conditions are met:
 The UE is attached to the CS domain with a combined EPS Attach.
 The UE cannot initiate IMS voice services.

2. The MME sends an S1-AP Request message carrying the CS Fallback Indicator IE to
the eNodeB, instructing the eNodeB to migrate the UE to a GSM cell.
3. The eNodeB selects a target GSM cell for the UE based on the measurement result or
LTE network configuration.
For details, see CS Fallback Feature Parameter Description.
4. (Optional) If GBFD-511308 eNACC Between GSM and LTE has been enabled on a
GSM network, and the LTE network and CN support the RAN information management
(RIM) procedure, the eNodeB starts the RIM procedure.
4a to 4c. The eNodeB requests the GSM system information (SI) from the BSS using the
RIM procedure.
4d to 4f. The BSC sends the GSM SI to the eNodeB. If CSFBIDENTIFYMOSW (BSC6900,
BSC6910) has been set to ON(On), the BSC changes the new establishment causes indication
(NECI) and sends SIB3 carrying the NECI to the eNodeB.
5. The eNodeB instructs the UE to access the target GSM cell as follows:
 5a. If both the UE and the network support PS handovers, the eNodeB initiates an
LTE-to-GSM PS handover.
 5b. If both the UE and the network support LTE-to-GSM CCO instead of PS
handovers, the eNodeB sends a MobilityFromEUTRACommand message to the UE. The
MobilityFromEUTRACommand message indicates that the purpose is cellChangeOrder. If
the LTE-to-GSM eNACC procedure is used, the MobilityFromEUTRACommand
message carries the GSM cell ID and the SI (including SIB1, SIB3, and SIB13). If this
procedure is not used, the message carries only the GSM cell ID.
 5c. If redirection is allowed, the eNodeB sends an RRC connection release message to
redirect the UE to the target GSM cell.
6. The eNodeB releases the S1 UE Context.
7. The UE sends a Channel Request message to the BSC.
If the location area (LA) has changed, the BSC proceeds with 9.
If the LA remains unchanged and CSFBIDENTIFYMOSW (BSC6900, BSC6910) is set to
ON(On), the UE sends a Channel Request message with a specific cause value according to
the modified NECI in the RIM procedure in 4.
 If the cause value is the same as that corresponding to the NECI in the GSM system,
the BSC determines that the call is processed within the GSM system.
 If the cause value is the same as that corresponding to the NECI in the RIM
procedure, the BSC determines that the call is a CSFB call. This process is referred to as
CSFB MOC identification.
If the LA remains unchanged and CSFBIDENTIFYMOSW (BSC6900, BSC6910) is set to
OFF(Off), this call is not identified as a CSFB call.
8. (Optional) If the CSFBIMMASSENSW parameter involved in the GBFD-160203
CSFB QoS feature is set to ON(On), the BSC starts the TCH immediate assignment
procedure. For details about the CSFB QoS, see CSFB QoS Feature Parameter Description.
9. (Optional) If the LA has changed, a location area update (LAU) procedure or
combined routing area update (RAU)/LAU procedure is performed.
The BSC determines whether the call is a CSFB call based on the value of CSMO in the
"Additional update parameters" IE contained in the RAU or LAU message.
 If the call is not a CSFB call, the BSC processes the call following the
common call access procedure.
 If the call is a CSFB call and SUPPORTCSFB (BSC6900, BSC6910) has been
set to SUPPORT(Support), the BSC proceeds with subsequent steps.
 If the call is a CSFB call but SUPPORTCSFB (BSC6900, BSC6910) has been
set to UNSUPPORT(Not Support), the BSC rejects the call.

Some UEs cannot report the "Additional update parameters" IE to the BSC. Without this IE, the BSC
processes the call following the common call access procedure.

10 to 13. (Optional) If the UE is processing PS services before initiating a call, and neither
the UE nor the network supports Dual Transfer Mode (DTM), the UE suspends the PS
services.
14 to 19. The UE initiates a CS call setup procedure.
The BSC determines whether the call is a CSFB call based on the value of CSMO in the
"Additional update parameters" IE contained in the CM Service Request message.
 If the call is not a CSFB call, the BSC processes the call following the common call
access procedure.
 If the call is a CSFB call and SUPPORTCSFB (BSC6900, BSC6910) has been set to
SUPPORT(Support), the BSC proceeds with subsequent steps.
 If the call is a CSFB call but SUPPORTCSFB (BSC6900, BSC6910) has been set to
UNSUPPORT(Not Support), the BSC rejects the call.

Some UEs cannot report the "Additional update parameters" IE to the BSC. Without this IE, the BSC processes
the call following the common call access procedure.

If the MSC that the UE was attached to in the LTE cell before CSFB is not the MSC that the
UE was attached to in the GSM cell after CSFB, and if the UE has not performed any
location updates, the MSC rejects the MOC. After receiving a CM Service Reject message,
the UE performs an LAU procedure and then proceeds with the call procedure.
If a UMTS network is available, set SendUtranECSCFlag (BSC6900, BSC6910) to
YES(Yes) to allow UEs to proactively report 3G classmarks to the BSC. However,
Classmark reporting increases the call setup delay. To shorten this delay, set
UTRANCMDELAYFORCSFBSW (BSC6900, BSC6910) to ON(On) for CSFB calls. This
setting prohibits UEs from reporting 3G classmarks to the BSC. If an early assignment
procedure is used, the BSC proactively queries 3G classmarks after the alerting procedure. If
a late assignment procedure is used, the BSC proactively queries 3G classmarks after
assignment is complete.
20. (Optional) After the CS call is complete:
 If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is enabled,
the UE quickly returns to an LTE cell. If there are suspended PS services, the UE restores
the PS services in the LTE cell.
 If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is disabled,
the UE continues to camp on the GSM cell. If there are suspended PS services, the UE
initiates an RAU in the GSM cell to restore the PS services.
3.1.2 MTC CSFB

A UE in idle mode or during a PS service receives a paging message on an LTE network. To

proceed with the call procedure, the eNodeB initiates mobile terminated call (MTC) CSFB to
migrate the UE to a GSM cell through PS handover, CCO, or redirection. Figure 3-2 shows the
MTC CSFB procedure.
Figure 3-2 MTC CSFB procedure

In Figure 3-2, the procedures enclosed in the white dotted line frame are optional and those enclosed in the gray
dotted line frame have branch procedures.
1 to 3. An UE in an LTE cell receives a paging message.
 Upon detecting that the UE is in idle mode, the eNodeB sends a Paging request
message carrying an SAE-temporary mobile subscriber identity (S-TMSI) or international
mobile subscriber identity (IMSI), to the UE.
 Upon detecting that the UE is in connected mode, the eNodeB sends a CS Paging
Notification message to the UE.
4. The UE sets up a radio resource control (RRC) connection and sends an Extended Service
Request message that carries the "CS Fallback Indicator" IE to inform the MME to initiate
CSFB.
5. The MME sends an SGs Service Request message to stop the MSC from resending paging
messages over the SGs interface.
6. The MME sends an Initial UE Context Setup message carrying the CS Fallback Indicator
IE to instruct the eNodeB to migrate the UE to a GSM cell.
7. The eNodeB selects a target GSM cell for the UE based on the measurement result or LTE
network configuration.
For details, see CS Fallback Feature Parameter Description.
8. (Optional) If both the GSM and LTE networks support the RIM procedure, the eNodeB
starts the RIM procedure.
9. The eNodeB instructs the UE to access the target GSM cell as follows:
 9a. If both the UE and the network support PS handovers, the eNodeB initiates an
LTE-to-GSM PS handover.
 9b. If both the UE and the network support LTE-to-GSM CCO instead of PS
handovers, the eNodeB sends a MobilityFromEUTRACommand message to the UE. The
MobilityFromEUTRACommand message indicates that the purpose is cellChangeOrder. If
the LTE-to-GSM eNACC procedure is used, the MobilityFromEUTRACommand
message carries the GSM cell ID and the SI (including SIB1, SIB3, and SIB13). If this
procedure is not used, the message carries only the GSM cell ID.
 9c. If the UE or the network supports neither LTE-to-GSM CCO nor PS handovers,
the eNodeB sends an RRC connection release message to redirect the UE to a GSM cell.
10. The eNodeB releases the S1 UE Context.
11. The UE sends a Channel Request message to the BSC.
If the LA changes, the BSC proceeds with step 13.
If the LA remains unchanged and CSFBIDENTIFYMTSW (BSC6900, BSC6910) is set to
ON(On), the BSC identifies the CSFB MTC based on the cause value contained in the
Channel Request message.

This process is referred to as CSFB MTC identification. According to 3GPP TS 44.018 v8.9.0, depending on the
Paging Indication value contained in the paging message from the GSM network, the called UE contains any
cause value (except the value corresponding to "Any channel") in the Channel Request message. On the LTE
network, however, the paging message from the eNodeB does not contain the Paging Indication IE, and a UE
that falls back to the GSM network contains the cause value corresponding to "Any channel" in the Channel
Request message.

12. (Optional) If the CSFBIMMASSENSW parameter involved in the GBFD-160203 CSFB

QoS feature is set to ON(On), the BSC starts the TCH immediate assignment procedure. For
details about the CSFB QoS, see CSFB QoS Feature Parameter Description.
13. (Optional) If the LA changes after the UE accesses the GSM cell, the UE performs an
LAU procedure or combined RAU/LAU procedure.
The BSC determines whether the call is a CSFB call based on the value of circuit switched
fallback mobile terminated call (CSMT) in the "Additional update parameters" IE contained
in the RAU or LAU message.
 If the call is not a CSFB call, the BSC processes the call following the common call
access procedure.
 If the call is a CSFB call and SUPPORTCSFB (BSC6900, BSC6910) has been set to
SUPPORT(Support), the BSC proceeds with subsequent steps.
 If the call is a CSFB call but SUPPORTCSFB (BSC6900, BSC6910) has been set to
UNSUPPORT(Not Support), the BSC rejects the call.
If a UE cannot report the "Additional update parameters" IE, it uses the paging-based CSFB
call identification function to identify a CSFB MTC. When CSFBPagingIdentifySw
(BSC6900, BSC6910) is set to ON(On), if the BSC receives a paging message from the MSC:
 The BSC buffers the paging message carrying the temporary mobile subscriber
identity (TMSI).
Upon receiving a paging response message from the UE, the BSC will match the paging
response message and the buffered paging message. Based on the matching result, the
BSC determines whether the MTC is a CSFB MTC.
 If the paging response message and the buffered paging message match, the
BSC determines that the MTC is not a CSFB MTC.
 If the paging response message and the buffered paging message do not
match, the BSC determines that the MTC is a CSFB MTC. This is because the paging
message of a CSFB call is not included in buffered paging messages but delivered from
the LTE network.
 If the LA changes, the UE performs an LAU or combined RAU/LAU
procedure before initiating a call. In this case, the BSC needs to determine whether the
UE initiates an MTC based on the subsequent call procedure. If the UE initiates an
MTC, and the paging response message and the buffered paging message match, the
BSC determines that the call is not a CSFB MTC. Otherwise, the BSC determines that
the call is a CSFB MTC.
 The BSC does not buffer the paging message carrying the IMSI.
If such a call cannot be identified based on the CSMT or using the very early identification
mode, the BSC determines that the call is not a CSFB MTC.
When CSFBPagingIdentifySw (BSC6900, BSC6910) is set to OFF(Off), the BSC
processes the call following the common call access procedure.
 14 to 17. (Optional) If the UE is processing PS services before initiating a call, and neither
the UE nor the network supports Dual Transfer Mode (DTM), the UE suspends the PS
services.
18 and 19. The UE sends a paging response message to the MSC through the BSS.
The BSC determines whether the call is a CSFB call based on the value of CSMT in the
"Additional update parameters" IE carried in the paging response message. The determination
process is the same as that described in step 13.
In MSC pool networking mode, after receiving a message in response to the CSFB paging
message from a UE accessing a GSM cell, the BSC performs either of the following
operations:
 If the CSFB paging response message delivered by the eNodeB carries the Temporary
Mobile Subscriber Identity (TMSI), the BSC obtains the DSP of the MSC according to the
NRI in the TMSI information and sends a paging response message to the MSC.
 If the CSFB paging response message delivered by the eNodeB carries the IMSI
(International Mobile Subscriber Identity): When the CSFBPAGRSPBCSWITCH
(BSC6900, BSC6910) parameter is set to YES (namely, the MSC supports Roaming Retry),
the BSC randomly selects an MSC from the MSC pool and sends the paging response
message to the MSC. When the CSFBPAGRSPBCSWITCH (BSC6900, BSC6910)
parameter is set to NO (namely, the MSC does not support Roaming Retry), the BSC
discards the CSFB paging response message.
20 to 22. (Optional) If the UE does not register with the MSC or the UE is not allowed to
access the LA, the MSC rejects the paging response and releases the A interface links. The
BSC then releases the signaling channel over the Um interface. After the signaling channel
over the Um interface is released, the UE obtains the location area identity (LAI) and
performs an LAU procedure.
23. The MSC initiates a CS call setup procedure.
If a UMTS network is available, set SendUtranECSCFlag (BSC6900, BSC6910) to
YES(Yes) to allow UEs to proactively report 3G classmarks to the BSC. However,
Classmark reporting increases the call setup delay. To shorten this delay, set
UTRANCMDELAYFORCSFBSW (BSC6900, BSC6910) to ON(On) for CSFB calls. This
setting prohibits UEs from reporting 3G classmarks to the BSC. If an early assignment
procedure is used, the BSC proactively queries 3G classmarks after the alerting procedure. If
a late assignment procedure is used, the BSC proactively queries 3G classmarks after
assignment is complete.
24. (Optional) The UE performs an LAU or combined RAU/LAU procedure.
 If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is enabled,
the UE quickly returns to an LTE cell. If there are suspended PS services, the UE restores
the PS services in the LTE cell.
 If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is disabled,
the UE continues to camp on the GSM cell. If there are suspended PS services, the UE
initiates an RAU in the GSM cell to restore the PS services.
3.2 Ultra-Flash CSFB
This section describes Ultra-Flash CSFB implementation only on a GSM network. For
information about its implementation on an LTE network, see CS Fallback Feature
Parameter Description in eRAN Feature Documentation.
When UltraFlashCSFBSw (BSC6900, BSC6910) is set to ON(On), the BSC supports Ultra-
Flash CSFB. Figure 3-3 illustrates the MOC Ultra-Flash CSFB procedure. Figure 3-4 illustrates
the MTC Ultra-Flash CSFB procedure.
Figure 3-3 MOC Ultra-Flash CSFB procedure
Figure 3-4 MTC Ultra-Flash CSFB procedure

1a to 3a. A UE initiates a CS service in an LTE cell. The eNodeB triggers an LTE-to-GSM

SRVCC handover for the UE.

In the MTC Ultra-Flash CSFB procedure, the MSC sends the Paging request or CS Paging Notification message
to the UE before the UE sends the Extend Service Request message to the MME.

3b. After receiving the SRVCC handover request from the MSC, the BSC identifies the
Ultra-Flash CSFB call and prepares CS resources for the call.
The BSC checks whether the configurations of MCC, MNC, LAC, and SAC in the service
area identifier (SAI) for a call are consistent with those configured on the MSC server. If they
are, the BSC determines the call is an Ultra Flash CSFB call. If they are not, the BSC
determines that the UE performed a UMTS-to-GSM inter-RAT handover.
The MCC, MNC, LAC, and SAC can be configured using parameters in the
GCELLCSFBPARA or GSAIFORLTE MO. The details are as follows:
 MCC: UltraFlashCSFBSAIMCC (BSC6900, BSC6910) (GCELLCSFBPARA MO)
or SAIMCC (BSC6900, BSC6910) (GSAIFORLTE MO)
 MNC: UltraFlashCSFBSAIMNC (BSC6900, BSC6910) (GCELLCSFBPARA MO)
or SAIMNC (BSC6900, BSC6910) (GSAIFORLTE MO)
 LAC: UltraFlashCSFBSAILAC (BSC6900, BSC6910) (GCELLCSFBPARA MO) or
SAILAC (BSC6900, BSC6910) (GSAIFORLTE MO)
 SAC: UltraFlashCSFBSAISAC (BSC6900, BSC6910) (GCELLCSFBPARA MO) or
SAISAC (BSC6900, BSC6910) (GSAIFORLTE MO)
In the MME pool or MOCN scenarios, if a BSC is connected to multiple MSC servers, which
are configured with different SAI values, the BSC also needs to be configured with multiple
SAI values. The GCELLCSFBPARA MO can only be used to configure one set of SAI
parameters. To add more SAI values, the GSAIFORLTE MO can be used. The MCC, MNC,
LAC, and SAC on the BSC are the combination of the GCELLCSFBPARA MO and
GSAIFORLTE MO.

When no SAI parameter has been configured through the GCELLCSFBPARA MO, the GSAIFORLTE MO
can also be used to configure multiple sets of SAI parameters.

4. The CN sends the Handover Command message to the eNodeB, and the eNodeB sends the
message to the UE.
5. The UE is handed over to the GSM network.
6 to 9. The UE establishes CS services on the GSM network.
 Signaling is carried by traffic channels (TCHs), accelerating signaling transmission.
 In the MOC Ultra-Flash CSFB and MTC Ultra-Flash CSFB procedures, before
sending or receiving the Alerting message, the MSC sends the UE a Disconnect message,
instructing the UE to release a default session generated during the SRVCC handover.
This mechanism helps prevent interference on subsequent session establishment. After the
UE is handed over to a GSM cell, if the UE sends the Disconnect message to the MSC to
release the default session, the MSC does not send the Disconnect message to the UE
before sending or receiving the Alerting message.
Ultra-Flash CSFB eliminates the dimmed signaling procedures shown in Figure 3-3 and Figure
3-4. The following details the reasons why these signaling procedures are eliminated:

 Authentication
The UE has been authenticated on the LTE side before it is handed over from an LTE cell
to a GSM cell.
 Encryption
The UE has performed encryption as instructed during the SRVCC handover.
 IMEI query
The MME has sent the IMEI to the MSC during the preparation for the SRVCC handover.
 CS resource establishment
 The GSM network has prepared CS resources during the SRVCC handover procedure and
the UE does not need to reestablish CS resources after the SRVCC handover.

4 Related Features

4.1 GBFD-511313 CSFB

Prerequisite Features

Feature ID Feature Name Description

GBFD-511308 eNACC Between GSM CSFB and access delay decrease with
and LTE unreported 3G classmark in the RIM
procedure depend on GBFD-511308
eNACC Between GSM and LTE. If the
prerequisite feature is not enabled, the
CSFB delay is likely to increase, affecting
user experience.

LOFD-001034 CS Fallback to GERAN CSFB takes effect only when both GBFD-
511313 CSFB and LOFD-001034 CS
Fallback to GERAN are enabled.

Mutually Exclusive Features

None

Impacted Features

Feature ID Feature Name Impact

GBFD-511312 Fast LTE Reselection at 2G CS It is recommended that CSFB be

Call Release enabled together with Fast LTE
Reselection at 2G CS Call
Release. This ensures that an
MS can quickly returns to an LTE
cell after the CS call is complete
in the GSM cell.

GBFD-171212 Ultra-Flash CSFB When Ultra-Flash CSFB and

CSFB are simultaneously
enabled and a call supports both
features, only the Ultra-Flash
CSFB feature takes effect for the
call.

4.2 GBFD-171212 Ultra-Flash CSFB

Prerequisite Features

Feature ID Feature Name Description

LOFD-081283 Ultra-Flash CSFB to -

GERAN

Mutually Exclusive Features

None

Impacted Features

Feature ID Feature Name Impact

GBFD-511312 Fast LTE It is recommended that Ultra-Flash CSFB be

Reselection at enabled together with Fast LTE Reselection at
2G CS Call 2G CS Call Release. This ensures that an MS
Release can quickly returns to an LTE cell after the CS
call is complete in the GSM cell.

GBFD-511309 SRVCC When both Ultra-Flash CSFB and SRVCC are

simultaneously enabled, if the SAI for SRVCC
is the same as that for Ultra-Flash CSFB, the
BSC processes Ultra-Flash CSFB calls as
SRVCC calls. In this situation, handovers are
not affected, but counter measurement is
affected.

GBFD-511313 CSFB When Ultra-Flash CSFB and CSFB are

simultaneously enabled and a call supports
both features, only the Ultra-Flash CSFB
feature takes effect for the call.

5 Network Impact

5.1 GBFD-511313 CSFB

System Capacity

When both the GBFD-511312 Fast LTE Reselection at 2G CS Call Release and GBFD-
511313 CSFB features are enabled, the duration of UEs camping on GSM cells and the
number of times that UEs initiate services in the GSM cell can be reduced, improving the
overall network capacity of GSM and LTE networks.

Network Performance
  Deteriorating PS service experience
If a UE initiates a CS call or receives a paging message during a PS service in an LTE cell,
the UE reselects a GSM cell using CSFB to perform the CS service. The PS service will
be interrupted or the PS user rate decreases.
If the UE supports only the full rate, CSFB calls may be mistakenly identified, increasing
the TCH congestion rate.
 Prolonging the call setup delay
In CSFB, a UE in an LTE cell must reselect to a GSM cell to perform CS services. This
prolongs the call setup delay.
In scenarios where a UE sends the Utran Classmark Change message to the BSC when
accessing the GSM network, enabling the "access delay decrease with unreported 3G
classmark in the RIM procedure" function helps decrease the CSFB MOC or CSFB MTC
setup delay by 0.47s to 1.2s.
 Increasing the signaling load
The number of LAUs or RAUs increases. If the CSFB is performed through PS handovers,
the number of PS handovers also increases.
 Increasing the CPU load
When CSFB MTC identification is used, the paging message carrying the TMSI is to be
buffered and queried during call access. If this function is enabled, CPU load will increase
by up to 1%.
5.2 GBFD-171212 Ultra-Flash CSFB

System Capacity

When both the GBFD-511312 Fast LTE Reselection at 2G CS Call Release and GBFD-
171212 Ultra-Flash CSFB features are enabled, the duration of UEs camping on GSM cells
and the number of times that UEs initiate services in the GSM cell can be reduced, improving
the overall network capacity of GSM and LTE networks.

Network Performance

The CSFB call setup delay when the Ultra-Flash CSFB feature is used is 1s to 2s shorter than
that when the CSFB feature is used.

6 Engineering Guidelines

6.1 GBFD-511313 CSFB

6.1.1 When to Use CSFB

CSFB helps provide voice services on an LTE network without the IMS. It is recommended
that this feature be enabled when operators expect to provide CS services without deploying
an IMS at the initial stage of LTE network deployment.
If a UE does not comply with 3GPP TS 44.018 v8.9.0 when sending the Channel Request
message to the BSC, the BSC may identify a CSFB call as a non-CSFB call, which cannot
experience CSFB services. Alternatively, the BSC may identify a non-CSFB call as a CSFB
call, which unexpectedly occupies TCHs, increasing the TCH congestion rate.
 If the proportion of MOCs not complying with 3GPP TS 44.018 v8.9.0 exceeds 5% in
a cell, you are advised not to enable CSFB MOC identification.
MOC protocol noncompliance is determined when MOC signaling over the Um interface
meets either of the following conditions:
 When NECI is 1, the cause value of the Channel Request IE is 111xxxxx.
 When NECI is 0, the cause value of the Channel Request IE is 0100xxxx.
 If the proportion of MTCs not complying with 3GPP TS 44.018 v8.9.0 exceeds 5% in
a cell, you are advised not to enable CSFB MTC identification.
MTC protocol noncompliance is determined when MTC signaling over the Um interface
meets either of the following conditions:
 The Paging request message on the network side does not contain the Paging
Indication IE.
 The Paging request message on the network side contains the Paging
Indication IE, and the cause value of the Channel Request IE for the MTC is 0001xxxx,
0010xxxx, or 0011xxxx.
If the proportion of UEs not supporting half rate exceeds 5% in a cell, you are advised not to
enable CSFB MOC identification.
6.1.2 Required Information

Before deploying CSFB, check whether the MSC supports MSC Pool networking.
6.1.3 Planning

The cells to be enabled with CSFB must be covered by both GSM and LTE networks.
It is a good practice to jointly plan LTE tracking areas (TAs) and GSM LAs if the CSFB
MOC and MTC identification is required. This ensures that CSFB MOCs and CSFB MTCs
are correctly identified even when location updates occur in the CSFB procedure.
The capacity of GSM cells depends on the proportion of calls made by LTE subscribers.
6.1.4 Deploying CSFB

6.1.4.1 Deployment Requirements

Table 6-1 Deployment requirements

Aspect Requirement

Related See 4 Related Features.

features Prerequisite features have been enabled.
Aspect Requirement

BSC None

BTS None

GSM This feature can be enabled only when the E-UTRAN network covers the
networking same area as the GERAN network.

UE UEs support GSM and LTE networks and CSFB.

If CSFB MOC identification is required, UEs must support R9 redirection.
If CSFB MTC identification is required, UEs must comply with 3GPP TS
44.018 v 8 GP-092464 CR 0825 and 3GPP TS 44.018 v9 GP-092229 CR
0826.
If the "access delay decrease with unreported 3G classmark in the RIM
procedure" function is required, UEs must comply with 3GPP TS 44.018.

MSC The MSC must support CSFB.

License The license controlling this feature has been activated. For details about
how to activate the license, see License Management Feature Parameter Description.
For details about license items, see License Control Item Description.

Others The SGs interface has been configured between the MSC server and the
MME.
The LTE network must support CSFB.

6.1.4.2 Data Preparation and Feature Activation

6.1.4.2.1 Data Preparation

Table 6-2 and Table 6-3 detail data to prepare for deploying CSFB.
Table 6-2 Data to prepare for the GCELLSOFT MO
Parameter Name Parameter ID Setting Notes Data
Source

CSFB Support SUPPORTCSFB Set this parameter to Networ

(BSC6900, BSC6910) SUPPORT(Support). k plan
(negotia
tion not
require
d)

Query RIM- UTRANCMDELAYFO This parameter is set to OFF by default. Networ

based UTRAN RCSFBSW (BSC6900, You are advised to set this parameter to k plan
ClassMark BSC6910) ON(On) in the following scenario: (negotia
Delay Switch The UTRAN classmark reporting tion not
function takes effect in a cell, indicating require
that SendUtranECSCFlag (BSC6900, d)
BSC6910) has been set to YES(Yes).
The SendUtranECSCFlag (BSC6900,
BSC6910) parameter is valid only if
Parameter Name Parameter ID Setting Notes Data
Source

ECSC (BSC6900, BSC6910) has been set

to YES(Yes).
After this parameter is set to ON(On),
UEs do not proactively report the
UTRAN classmark. After the alerting
procedure is complete, the BSC
proactively queries the UTRAN
classmark, reducing the CSFB
establishment delay.
If the UTRAN classmark reporting
function does not take effect in a cell,
you are advised not to set this
parameter to ON(On).
NOTE:
Before setting this parameter to ON(On), ensure
that the RIM function has been enabled on GSM
and LTE networks and UEs comply with the R9
protocol.

CSFB MOC CSFBIDENTIFYMOS This parameter specifies the function of Networ

Identification W (BSC6900, BSC6910) identifying CSFB MOC very early. k plan
Switch Identified CSFB MOCs are for the very (negotia
early TCH assignment for CSFB and tion not
CSFB voice quality guarantee functions require
in the GBFD-160203 CSFB QoS d)
feature. If the two functions in this
feature have been enabled, or CSFB
performance counters need to be
calculated, set CSFB MOC
Identification Switch to ON(On). This
parameter is set to OFF by default.
NOTE:
Before enabling CSFB MOC identification,
ensure that UEs comply with the R9 protocol
and that no LAU has been performed before a
channel request message is sent.

CSFB MTC CSFBIDENTIFYMTS This parameter specifies the function of Networ

Identification W (BSC6900, BSC6910) identifying CSFB MOC very early. k plan
Switch Identified CSFB MTCs are for the very (negotia
early TCH assignment for CSFB and tion not
CSFB voice quality guarantee functions require
in the GBFD-160203 CSFB QoS d)
feature. If the two functions in this
feature have been enabled, or CSFB
performance counters need to be
calculated, set CSFB MTC
Identification Switch to ON(On). This
parameter is set to OFF by default.
Parameter Name Parameter ID Setting Notes Data
Source

NOTE:
Before enabling CSFB MTC identification,
ensure that UEs comply with 3GPP 44.018 v8
GP-092464 CR 0825 or 3GPP 44.018 v9 GP-
092229 CR 0826, and that no LAU is performed
before a channel request message is sent.

Unknown CSFBPAGRSPBCSW This parameter is set to NO by default. Networ

Paging ITCH (BSC6900, In MSC pool scenarios, you are advised k plan
Response BSC6910) to set this parameter to YES(Yes). (negotia
Support tion not
require
d)

Table 6-3 Data to prepare for the BSCEXSOFTPARA MO

Parameter Name Parameter ID Setting Notes Data
Source

CSFB Paging CSFBPagingIdentify This parameter specifies the function of Networ

Identify Switch Sw (BSC6910, BSC6900) CSFB MTC identification based on a k plan
paging response. Identified CSFB (negotia
MTCs are for the very early TCH tion not
assignment for CSFB and CSFB voice require
quality guarantee functions in the d)
GBFD-160203 CSFB QoS feature. If the
two functions in this feature have been
enabled, or CSFB performance
counters need to be calculated, set
CSFB MTC Identification Switch to
ON(On).

6.1.4.2.2 Using MML Commands

1. On the BSC LMT, run the SET GCELLSOFT command with CSFB Support set to
SUPPORT(Support) for a target cell.
 To enable the "access delay decrease with unreported 3G classmark in the
RIM procedure" function, set Query RIM-based UTRAN ClassMark Delay Switch
to ON(On).
 To enable CSFB in MSC pool networking mode, set Unknown Paging
Response Support to YES(Yes).
 To enable CSFB MOC identification, set CSFB MOC Identification Switch
to ON(On).
 To enable CSFB MTC identification, set CSFB MTC Identification Switch
to ON(On).
2. (Optional) To enable CSFB call identification based on paging, run the SET
BSCEXSOFTPARA command with CSFB Paging Identify Switch set to ON(On).
 6.1.4.2.3 MML Command Examples
//Enabling CSFB
SET GCELLSOFT: IDTYPE=BYID, CELLID=1, CSFBPAGRSPBCSWITCH=YES,
SUPPORTCSFB=SUPPORT, UTRANCMDELAYFORCSFBSW=ON, CSFBIDENTIFYMOSW=ON,
CSFBIDENTIFYMTSW=ON;

//(Optional) Enabling CSFB call identification based on paging

SET BSCEXSOFTPARA: CSFBPagingIdentifySw=ON;

6.1.4.2.4 Using the CME

Using the CME (Method 1)

When configuring the feature on the CME, perform a single configuration first, and then perform batch
modifications if required. Configure the parameters of a single object before a batch modification. Perform a
batch modification before logging out of the parameter setting interface.

1. Configure a single object on the CME.

Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-4.
For detailed operations, see CME-based Feature Configuration.
2. (Optional) Modify objects in batches on the CME. (CME batch modification center)

To modify objects (BTS/GSM cell/TRX/BSC/external GSM cell) in batches, click on the

CME to start the batch modification wizard.

For instructions on how to perform a batch modification, click on the wizard interface to
obtain online help.
Table 6-4 Configuring parameters on the CME

SN MO NE Parameter Name Configurable in

CME Batch
Modification
Center

1 GCELLSOFT BSC6900/BSC6 See Table 6-2. Yes

910

2. (Optional) To BSCEXSOFTPA BSC6900/BSC6 See Table 6-3. Yes

enable CSFB RA 910
call identification
based on
paging, perform
this step.

Using the CME (Method 2)

This feature can be activated in batches on the CME. For detailed operations, see the online
help or the following section in the CME product documentation: Managing the CME >
CME Guidelines > Enhanced Feature Management > Feature Operation and
Maintenance.
6.1.4.3 Activation Observation

1. On the BSC LMT, start single-subscriber CS message tracing for a UE. In this step,
set the IMSI or TMSI of the test UE.
2. Enable CSFB for LTE NEs on the E-UTRAN side and for the MSC on the GERAN
side.

For instructions on how to enable CSFB for LTE NEs and for the MSC, see the related feature
configuration guide.

3. Trigger a CS paging to the UE after the UE performs services properly on the E-

UTRAN network.
4. View the single-subscriber CS message tracing result.
Expected result: The UE successfully sets up a call at the BSC side. Both signaling and
the CS paging are processed properly.
6.1.4.4 Feature Deactivation

6.1.4.4.1 Using MML Commands

On the BSC LMT, run the SET GCELLSOFT command with CSFB Support set to
UNSUPPORT(Not Support) for a target cell.
6.1.4.4.2 MML Command Examples

SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SUPPORTCSFB=UNSUPPORT;

6.1.4.4.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

6.1.5 Performance Monitoring

 Monitor the number of LAUs during CSFB. If the number is excessively large,
optimize core network configurations. Table 6-5 lists the counters related to the number of
LAUs.
Table 6-5 Counters related to the number of LAUs

Counter Description

CELL.LUA.TIMES.NORMAL LA300: Number of Location Update Requests

(Normal Location Update)

CELL.LUA.TIMES.PERIOD LA301: Number of Location Update Requests

(Periodic Location Update)

CELL.LUA.TIMES.IMSI.ATTACH LA302: Number of Location Update Requests

(IMSI Attach)
  Monitor TCH assignment for CSFB calls and CSFB call identification. Table 6-6 lists
the counters related to TCH assignment for CSFB calls and CSFB call identification.
Table 6-6 Counters related to TCH assignment for CSFB calls and CSFB call identification

Counter Description

CELL.ESTB.IND.CSMO A3039A: Number of Call Setup Indications (CSFB

MOC)

CELL.ESTB.IND.CSMT A3039B: Number of Call Setup Indications (CSFB

MTC)

CELL.ASS.CMPL.CSMO.TCH A3170A: Number of Completed TCH Assignments

(CSFB MOC)

CELL.ASS.CMPL.CSMT.TCH A3170B: Number of Completed TCH Assignments

(CSFB MTC)

CELL.CH.REQ.CSFB.MOC A300M: Number of Channel Requests (Early

Identification of CSFB MOC)

CELL.CH.REQ.CSFB.MTC A300N: Number of Channel Requests (Early

Identification of CSFB MTC)

CELL.CH.BUSY.NUM.FR.TRAF.CSFB. AR3553: Average Number of Busy TCHFs

AVR (CSFB)

CELL.CH.BUSY.NUM.HR.TRAF.CSFB. AR3554: Average Number of Busy TCHHs

AVR (CSFB)

6.1.6 Parameter Optimization

None
6.1.7 Troubleshooting

None
6.2 GBFD-171212 Ultra-Flash CSFB

6.2.1 When to Use Ultra-Flash CSFB

It is recommended that this feature be enabled when operators wish to provide CS services
without deploying an IMS at the initial stage of LTE network deployment and have high
requirements on the call setup delay. This feature decreases the call setup delay more
significantly than the CSFB feature.
6.2.2 Required Information

Before deploying the Ultra-Flash CSFB feature, collect the following information:
 Proportion of areas covered by both GSM and LTE networks
 Proportion of MSs supporting LTE-to-GSM SRVCC handovers
6.2.3 Network Planning
 The cells to be enabled with Ultra-Flash CSFB must be covered by both GSM and
LTE networks.
 The capacity of GSM cells depends on the proportion of calls made by LTE
subscribers.
6.2.4 Deploying Ultra-Flash CSFB

6.2.4.1 Deployment Requirements

Table 6-7 Deployment requirements

Aspect Requirement

Related See 4 Related Features.

features

BSC None

BTS None

GSM This feature can be enabled only when the E-UTRAN network covers the
networking same area as the GERAN network.

UE MSs support LTE-to-GSM SRVCC handovers.

MSC The MSC supports Ultra-Flash CSFB and is provided by Huawei.

License The license controlling this feature has been activated. For details about
how to activate the license, see License Management Feature Parameter Description.
For details about license items, see License Control Item Description.

Others The Sv interface has been configured between the MSC server and the
mobile management entity (MME). The MME and eNodeB are provided by
Huawei and support Ultra-Flash CSFB.

6.2.4.2 Data Preparation and Feature Activation

6.2.4.2.1 Data Preparation

Configure GSM parameters (under the GCELLCSFBPARA MO) related to LTE-to-GSM

Ultra-Flash CSFB to allow Ultra-Flash CSFB both on LTE and GSM networks properly work
with each other.
Table 6-8 Data to be prepared for the GCELLCSFBPARA MO
Parameter Parameter ID Setting Notes Data Source
Name

Ultra-Flash UltraFlashCSFBS If LTE-to-GSM Ultra-Flash CSFB is Network

CSFB w (BSC6900, required, set this parameter to ON(On). plan
Switch BSC6910) (negotiation
not required)

Ultra-Flash UltraFlashCSFBS If performance counters related to Ultra- Network

CSFB SAI AIMCC (BSC6900, Flash CSFB need to be calculated, and plan
MCC BSC6910) UEs can perform fast return to an LTE (negotiation
Parameter Parameter ID Setting Notes Data Source
Name

cell after ongoing Ultra-Flash CSFB- required)

based CS services are complete, set this
Ultra-Flash UltraFlashCSFBS parameter as required. Ensure that the Network
CSFB SAI AIMNC (BSC6900, parameter setting is consistent with the plan
MNC BSC6910) SAI value on the MSC server. (negotiation
This parameter is dedicated to Ultra- required)
Flash CSFB calls, and its setting does
Ultra-Flash UltraFlashCSFBS not affect handover implementation. Network
CSFB SAI AILAC (BSC6900, NOTE: plan
LAC BSC6910) (negotiation
For details about fast return, see Fast LTE required)
Reselection at 2G CS Call Release.
Ultra-Flash UltraFlashCSFBS Network
CSFB SAI AISAC (BSC6900, plan
SA BSC6910) (negotiation
required)

Inter-RAT In UFCSFBStatInterR This parameter specifies whether Network

HO Ultra- anHo (BSC6900, incoming Ultra-Flash CSFB handovers plan
Flash CSFB BSC6910) are included for calculating the (negotiation
Stat Switch CELL.INTERRAN.INCELL.HO.REQ not required)
counter related to incoming UMTS-to-
GSM inter-cell handover statistics. To
ensure stable performance counters, if
Ultra-Flash CSFB calls are not identified,
incoming Ultra-Flash CSFB handovers
are included for calculating the
CELL.INTERRAN.INCELL.HO.RE
counter; if Ultra-Flash CSFB calls have
been identified, such handovers are
included for calculating the
CELL.ULTRA.FLASH.CSFB.HO.REQ
counter.

(Optional) In the MME pool or MOCN scenarios, if a BSC is connected to multiple MSC
servers, which are configured with different SAI values, the BSC also needs to be configured
with multiple SAI values using the GSAIFORLTE MO.
Table 6-9 Data to be prepared for the GSAIFORLTE MO
Parameter Name Parameter ID Setting Notes Data Source

LTE SAI Index LTESAIIndex (BSC6900, - Radio network plan

BSC6910) (internal plan)

CN Node Index CNNODEIDX (BSC6900, Ensure that the Radio network plan
BSC6910) parameter setting is (internal plan)
consistent with the
configuration of
CNNODEIDX
(BSC6900, BSC6910).
Parameter Name Parameter ID Setting Notes Data Source

HANDOVER HoType (BSC6900, Set this parameter to Radio network plan

type BSC6910) ULTRAFLASHCSFB( (internal plan)
Ultra-Flash CSFB).

SAI MCC SAIMCC (BSC6900, Ensure that the Radio network plan
BSC6910) parameter setting is (internal plan)
consistent with the
SAI MNC SAIMNC (BSC6900, SAI value on the Radio network plan
BSC6910) MSC server. (internal plan)

SAI LAC SAILAC (BSC6900, Radio network plan

BSC6910) (internal plan)

SAI SAC SAISAC (BSC6900, Radio network plan

BSC6910) (internal plan)

6.2.4.2.2 Using MML Commands

1. Run the BSC MML command SET GCELLCSFBPARA to set the cell-level CSFB
parameters.
2. (Optional) Run the BSC MML command ADD GSAIFORLTE to configure
extended SAI values. For the conditions of this step, see 6.2.4.2.1 Data Preparation.
6.2.4.2.3 MML Command Examples
//Setting cell-level CSFB parameters
SET GCELLCSFBPARA: IDTYPE=BYID, CELLID=0, UltraFlashCSFBSw=ON,
UltraFlashCSFBSAIMCC="454", UltraFlashCSFBSAIMNC="12",
UltraFlashCSFBSAILAC=1, UltraFlashCSFBSAISAC=1, UFCSFBStatInterRanHo=ON;
//(Optional) Configuring extended SAI values
ADD GSAIFORLTE: LTESAIIndex=0, CNNODEIDX=0, HoType=ULTRAFLASHCSFB,
SAIMCC="454", SAIMNC="12", SAILAC=1, SAISAC=0;

6.2.4.2.4 Using the CME

When configuring Ultra-Flash CSFB on the CME, perform a single configuration first, and then perform batch
modifications if required. Configure the parameters of a single object before a batch modification. Perform a
batch modification before logging out of the parameter setting interface.

1. Configure a single object on the CME. (CME single configuration)

Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-10.
For detailed operations, see CME-based Feature Configuration.
2. (Optional) Modify objects in batches on the CME. (CME batch modification center)

To modify objects (BTS/GSM cell/TRX/BSC/external GSM cell) in batches, click on the

CME to start the batch modification wizard.
For instructions on how to perform a batch modification, click on the wizard interface to
obtain online help.
Table 6-10 Configuring parameters on the CME
SN MO NE Parameter Name Configurable in
CME Batch
Modification
Center

1 GCELLCSFBPARA BSC6900/BSC69 See Table 6-8. Yes

10

2 GSAIFORLTE BSC6900/BSC69 See Table 6-9. Yes

10

6.2.4.3 Activation Observation

1. On the BSC LMT, start single-subscriber CS message tracing for a UE. In this step,
set the IMSI or TMSI of the test UE.
2. Enable Ultra-Flash CSFB for LTE NEs at the E-UTRAN side and for the MSC at the
GERAN side.

For details about how to enable Ultra-Flash CSFB for LTE NEs and for the MSC, see the feature
configuration guide for Ultra-Flash CSFB.

3. Trigger a CS paging to the UE after the UE performs services properly on the E-

UTRAN network.
4. View the single-subscriber CS message tracing result.
Expected result: The UE successfully sets up a call at the BSC side. Both signaling and
the CS paging are processed properly.
5. Monitor the counter listed in Table 6-11. If the value of this counter is not 0, the Ultra-
Flash CSFB feature has taken effect.
Table 6-11 Counter to be observed
Counter Name Counter Description

CELL.ULTRA.FLASH.CSFB.HO.REQ H360: Number of Ultra-Flash CSFB Handover

Requests

6.2.4.4 Feature Deactivation

6.2.4.4.1 Using MML Commands

On the BSC LMT, run the SET GCELLCSFBPARA command with Ultra-Flash CSFB
Switch set to OFF(Off) for a target cell.
6.2.4.4.2 MML Command Examples

SET GCELLCSFBPARA: IDTYPE=BYID, CELLID=0, UltraFlashCSFBSw =OFF;

6.2.4.4.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

6.2.5 Performance Monitoring

Monitor the counters listed in Table 6-12 to observe the number of handover requests,
handover responses, and successful handovers of Ultra-Flash CSFB users.
Table 6-12 Counters related to Ultra-Flash CSFB
Counter Name Counter Description

CELL.ULTRA.FLASH.CSFB.HO.REQ H360: Number of Ultra-Flash CSFB Handover

Requests

CELL.ULTRA.FLASH.CSFB.HO.ACK H361: Number of Ultra-Flash CSFB Handover

Responses

CELL.ULTRA.FLASH.CSFB.HO.SUCC H363: Number of Successful Ultra-Flash CSFB

Handovers

6.2.6 Parameter Optimization

None
6.2.7 Troubleshooting

None

7 Parameters

The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
Base station controller parameter reference
 BSC6900 GSM Parameter Reference: contains the parameters related to the BSC6900
equipment, transport, and radio access functions.
 BSC6910 GSM Parameter Reference: contains the parameters related to the BSC6910
equipment, transport, and radio access functions.
eGBTS Parameter reference
 Node Parameter Reference: contains base station equipment and transport parameters.
 GBTSFunction Parameter Reference:contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
You can find the EXCEL files of parameter reference for the software version on the live network from the
product documentation delivered with that version.

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

8 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
Base station controller performance counter reference
 BSC6900 GSM Performance Counter Reference: contains the counters related to the
BSC6900 equipment, transport, and radio access functions.
 BSC6910 GSM Performance Counter Reference:
contains the counters related to the
BSC6910 equipment, transport, and radio access functions.
eGBTS performance counter reference
 Node Performance Counter Summary: contains base station equipment and transport
counters.
 GBTSFunction Performance Counter Summary:
contains all counters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.

You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1: Open the EXCEL file of performance counter reference.
Step 2: On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, GBFD-200201.
Step 3: Click OK. All counters related to the feature are displayed.
9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

10 Reference Documents

1. 3GPP TS 45.008 Radio subsystem link control

2. 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control
(RRC) protocol
3. 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS)
interface; Layer 3 specification