eRAN
SRVCC Feature Parameter Description
Issue
04
Date
2014-03-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in
this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this
document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all
statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address:
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
2 Overview
2.1 Introduction
2.2 Benefits
2.3 Architecture
2.3.1 SRVCC
2.3.2 eSRVCC
3 SRVCC from E-UTRAN to UTRAN
3.1 SRVCC to UTRAN
3.1.1 Causes
3.1.2 Execution
3.2 SRVCC Flexible Steering to UTRAN
3.3 SRVCC Selection Procedure
3.4 Signaling Procedure
4 SRVCC from E-UTRAN to GERAN
4.1 SRVCC to GERAN
4.2 SRVCC Selection Procedure
4.3 Signaling Procedure
5 Related Features
5.1 Features Related to LOFD-001022 SRVCC to UTRAN
5.2 Features Related to LOFD-001087 SRVCC Flexible Steering to UTRAN
5.3 Features Related to LOFD-001023 SRVCC to GERAN
6 Network Impact
6.1 LOFD-001022 SRVCC to UTRAN
6.2 LOFD-001087 SRVCC Flexible Steering to UTRAN
6.3 LOFD-001023 SRVCC to GERAN
7 Engineering Guidelines
7.1 LOFD-001022 SRVCC to UTRAN
7.1.1 When to Use SRVCC to UTRAN
7.1.2 Required Information
7.1.3 Process
7.1.4 Requirements
7.1.5 Data Preparation
7.1.6 Activation
7.1.7 Activation Observation
7.1.8 Deactivation
7.1.9 Performance Monitoring
7.1.10 Parameter Optimization
7.2 LOFD-001087 SRVCC Flexible Steering to UTRAN
7.2.1 When to Use SRVCC Flexible Steering to UTRAN
7.2.2 Required Information
7.2.3 Process
7.2.4 Requirements
7.2.5 Data Preparation
7.2.6 Activation
7.2.7 Activation Observation
7.2.8 Deactivation
7.2.9 Performance Monitoring
7.2.10 Parameter Optimization
7.3 LOFD-001023 SRVCC to GERAN
7.3.1 When to Use SRVCC to GERAN
7.3.2 Required Information
7.3.3 Process
7.3.4 Requirements
7.3.5 Data Preparation
7.3.6 Activation
7.3.7 Activation Observation
7.3.8 Deactivation
7.3.9 Performance Monitoring
7.3.10 Parameter Optimization
7.4 Troubleshooting
7.4.1 Fault 1
7.4.2 Fault 2
8 Parameters
9 Counters
10 Glossary
11 Reference Documents
1 About This Document
1.1 Scope
This document describes single radio voice call continuity (SRVCC), including its technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:
• LOFD-001022 SRVCC to UTRAN
• LOFD-001023 SRVCC to GERAN
• LOFD-001087 SRVCC Flexible Steering to UTRAN
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.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB.
1.2 Intended Audience
This document is intended for personnel who:
• Need to understand the features described herein
• Work with Huawei products
1.3 Change History
This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows:
• Feature change
Changes in features of a specific product version
• Editorial change
Changes in wording or addition of information that was not described in the earlier version
eRAN6.0 04 (2014-03-15)
This issue includes the following changes.
Change Type
Change Description
Parameter Change
Feature change None
None
Editorial change Revised the documentation.
None
eRAN6.0 03 (2013-07-30)
This issue includes the following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
Added MML command examples for feature activation and deactivation. For details, see 7 Engineering
Guidelines.
None
eRAN6.0 02 (2013-06-30)
This issue includes the following changes.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial change
Revised the impact of SRVCC flexible steering to
UTRAN on the network performance. For details, see
6.2 LOFD-001087 SRVCC Flexible Steering to UTRAN.
None
eRAN6.0 01 (2013-04-28)
This issue includes the following changes.
Change Type
Change Description
Parameter Change
Feature change
Changed the LCS-triggered SRVCC function to
configurable. For details, see 3.1.1 Causes.
Added the LcsSrvccSwitch(LcsSrvccSwitch) option to the
ENodeBAlgoSwitch.HoModeSwitch parameter.
Editorial change
None
None
eRAN6.0 Draft A (2013-01-30)
This document is created for eRAN6.0.
2 Overview
SRVCC is a solution aimed at providing continuous voice services on LTE networks. In the early phases of LTE deployment, when UEs running voice services move out
of an LTE network, the voice services can continue in the legacy circuit switched (CS) domain using SRVCC, ensuring voice service continuity.
SRVCC is a method of inter-RAT handover (RAT stands for radio access technology). It enables smooth session transfers from VoIP over the IP multimedia subsystem
(IMS) on the LTE network to CS services in the UTRAN or GERAN.
After SRVCC is deployed, bearers with QoS class identifiers (QCIs) of 1 must be used only for voice services. Therefore, when an eNodeB detects that a service running
on a UE is carried on a bearer with QCI 1, the eNodeB can determine that the UE is performing a voice service. For details, see section 4.1.2 "Architectural Principles for
3GPP UTRAN/GERAN SRVCC and vSRVCC" in 3GPP TS 23.216 V11.1.0.
If both SRVCC from E-UTRAN to UTRAN and SRVCC from E-UTRAN to GERAN are supported on an LTE network, UTRAN and GERAN frequencies are measured
simultaneously. The frequency that first reports measurement results is used for SRVCC.
2.1 Introduction
The SRVCC technology is used to ensure voice service continuity when a single-radio UE is handed over from the E-UTRAN/EPC to the UTRAN or GERAN. (EPC
stands for Evolved Packet Core.)
NOTE:
A single-radio UE is capable of working only in one of the following RATs at a time: E-UTRAN, UTRAN, or GERAN.
SRVCC requires IMS. It is used on LTE/EPC networks where voice services are enabled. When a UE running VoIP services is to be handed over from the E-UTRAN to
the UTRAN or GERAN, the mobility management entity (MME) initiates a handover request to the mobile switching center (MSC) server.
2.2 Benefits
The benefits of SRVCC are as follows:
• Before the E-UTRAN is deployed across coverage areas, SRVCC is used to ensure voice service continuity.
• At the edge of the E-UTRAN, UEs running VoIP services can be handed over to the UTRAN or GERAN using SRVCC, which transforms the VoIP services
into CS services.
• With SRVCC or enhanced SRVCC (eSRVCC), the service interruption period during a handover can be reduced to improve user experience of voice
services.
For details about eSRVCC, see 2.3.2 eSRVCC.
2.3 Architecture
2.3.1 SRVCC
SRVCC consists of the following activities:
• Access-stratum handover between bearer networks
• IMS session transfer
Figure 2-1 shows the SRVCC network architecture. The Sv interface is introduced between the MME and the MSC server that is enhanced for SRVCC (referred to as
SRVCC MSC server in this document). The overall SRVCC procedure is as follows:
1. The MME informs the SRVCC MSC server through the Sv interface that a VoIP service is to be handed over to the CS domain.
2. The SRVCC MSC server instructs the UTRAN or GERAN to prepare for the handover.
3. The SRVCC MSC server requests that the media gateway (MGW) provide the new media-plane information, including the IP address and port number. It
then notifies the service centralization and continuity application server (SCC AS) that the media stream is to be changed. The SCC AS is a control point for
the IMS session transfer.
4. The SCC AS notifies the UE of the new media-plane information.
5. The UE establishes a new VoIP media stream to the MGW and releases the original VoIP media stream.
6. The MGW may need to convert the established VoIP media stream to achieve interworking between the CS voice stream and VoIP voice stream. The
conversion occurs in protocol stacks and voice coding.
Figure 2-1 SRVCC network architecture
Table 2-1 describes the elements of the SRVCC network architecture.
Table 2-1 Elements of SRVCC network architecture
Element
Function
Sv interface
Supports SRVCC as an interface between the MME and the SRVCC MSC server.
E-UTRAN
Supports the SRVCC procedure, which in the E-UTRAN is similar to a PS handover procedure. During the SRVCC procedure, the
E-UTRAN sends an SRVCC indication to the MME, notifying the MME of whether the target cell supports SRVCC and concurrent CS and
PS handovers.
UTRAN/GERAN
• Supports incoming CS handovers for CS-only SRVCC.
• Supports concurrent incoming CS and PS handovers for CS-and-PS SRVCC.
MME
• Provides the bearer splitting function to separate the voice bearer from non-voice bearers. Then, the MME initiates a CS
handover procedure for the voice bearer towards the MSC server and initiates a PS handover procedure for the non-voice
bearers towards the serving GPRS support node (SGSN).
• Initiates an SRVCC procedure over the Sv interface for an emergency call and includes an emergency indication in the
transmitted message.
• Selects the SRVCC MSC server based on the domain name server (DNS) procedures or local configuration.
MSC
Processes CS handovers and session transfers.
SGSN
Processes PS handovers for CS-and-PS SRVCC.
Proxy-call session control
function (P-CSCF)
Acts as the first contact point for UEs in the IMS that provides the proxy function by accepting and forwarding service requests, but does
not change the Request URI field in the INVITE message. The P-CSCF also provides the user agent (UA) function by terminating and
independently creating Session Initiation Protocol (SIP) sessions when exceptions occur.
Serving-call session
Acts as the control center of the IMS, implements UE registration and authentication and session control, and provides basic session
control function (S-CSCF) routing for calling and called parties on the IMS. In addition, the S-CSCF routes value-added services to the application server (AS) and
performs service control interactions according to the IMS rules to which users are subscribed.
Interrogating-call session
control function (I-CSCF)
Assigns S-CSCFs to UEs, supports route query, and forwards SIP requests to another IMS domain.
Enables interworking between the IMS control plane and the legacy CS network.
Element
Function
Media gateway control
function (MGCF)
SCC AS
Ensures the centralization and continuity of VoIP services on the LTE network.
2.3.2 eSRVCC
Although the access-stratum handover of an SRVCC procedure can be completed within 300 ms, the session transfer cannot. As a result, the total service interruption
period during SRVCC does not meet the following requirement: The service interruption period during the handover of a real-time service between the E-UTRAN and the
UTRAN or GERAN must be less than 300 ms. For details about this requirement, see section 8.4 "Co-existence and interworking with 3GPP RAT" in 3GPP TS 25.913
V8.0.0.
To shorten the service interruption time, 3GPP Release 10 proposes eSRVCC.
eSRVCC focuses on reducing the time for session transfer because session transfer prolongs the service interruption period, especially in situations where the calling
and called parties are being served by different networks or when a UE is roaming.
Compared with the SRVCC network architecture, the eSRVCC network architecture incorporates two new elements:ATCF and ATGW between the P-CSCF and
I-CSCF/S-CSCF, as shown in Figure 2-2.
• Access Transfer Control Function (ATCF)
The ATCF acts as an anchor point for signaling messages before and after handovers. To reduce delay, the ATCF must be deployed on the serving network.
(The visited network is the serving network for roaming UEs.) The MSC server can be located close to the ATCF to shorten the time for signaling routing from
the MSC server to the ATCF.
• Access Transfer Gateway (ATGW)
The ATGW acts as a media-plane anchor point for VoIP services before and after handovers. The ATGW remains unchanged after a handover. Therefore, a
session transfer is not required, reducing the service interruption period.
For a UE running a voice service that may require SRVCC later, the media plane of the service is anchored to the ATGW. When an SRVCC procedure is initiated for this
UE, the media-plane information is updated only on the ATGW, but not on the UE, to shorten the handover duration.
Figure 2-2 eSRVCC network architecture
NOTE:
This document focuses on eNodeB functions, which are the same for SRVCC and eSRVCC. Therefore, the following sections do not distinguish between SRVCC and
eSRVCC. On live networks, eSRVCC is used.
3 SRVCC from E-UTRAN to UTRAN
3.1 SRVCC to UTRAN
This section describes the optional feature LOFD-001022 SRVCC to UTRAN. For details about the engineering guidelines for this feature, see 7.1 LOFD-001022
SRVCC to UTRAN. This feature is controlled by UtranSrvccSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter.
3.1.1 Causes
Measurements for SRVCC are triggered by various factors. For details about possible triggers, see the related documents of the features or functions.
Common Causes
Several factors may trigger SRVCC to UTRAN. For detailed measurement triggering, see the documents listed in Table 3-1.
Table 3-1 Mapping between documents and features/functions
Feature/Function
•
•
•
•
Coverage-based inter-RAT handover to UTRAN
Service-based inter-RAT handover to UTRAN
Distance-based inter-RAT handover to UTRAN
UL-quality-based inter-RAT handover to UTRAN
Document
Inter-RAT Mobility Management in
Connected Mode Feature Parameter
Description
Load-based inter-RAT handover to UTRAN
MLB Feature Parameter Description
SPID-based inter-RAT handover (SPID stands for subscriber profile ID.)
Flexible User Steering Feature Parameter
Description
Location Service (LCS)
LCS-based SRVCC is controlled by LcsSrvccSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter. It also depends on the UTRAN LCS capability, which
is controlled by the CSFallBackBlindHoCfg.UtranLcsCap parameter. LCS-based SRVCC is used when a UE triggers LCS in a LCS-incapable LTE network.
When the UE triggers LCS, the MME delivers a CS Fallback Indicator to the eNodeB. The eNodeB performs SRVCC to hand the UE over to the CS domain for LCS
while ensuring voice service continuity.
The procedure for LCS-based SRVCC is the same as that for CSFB to UTRAN, and LCS-based SRVCC is controlled by the parameters for CSFB. For details, see CS
Fallback Feature Parameter Description.
3.1.2 Execution
The UtranExternalCell.CsPsHOInd parameter, which is set based on the MME and RNC capabilities, determines which type of SRVCC the eNodeB initiates.
• If this parameter is set to BOOLEAN_TRUE(True), the eNodeB initiates a CS-and-PS SRVCC procedure.
• If this parameter is set to BOOLEAN_FALSE(False), the eNodeB initiates a CS-only SRVCC procedure.
Because there is no switch available to specify the MME capability, operators are advised to consider both the MME and RNC capabilities when setting the preceding
parameter. If either the MME or the RNC does not support concurrent CS and PS handovers, set UtranExternalCell.CsPsHOInd to BOOLEAN_FALSE(False).
The execution procedure of SRVCC is the same as that of inter-RAT mobility management. For details, see Inter-RAT Mobility Management in Connected Mode Feature
Parameter Description.
3.2 SRVCC Flexible Steering to UTRAN
This section describes the optional feature LOFD-001087 SRVCC Flexible Steering to UTRAN. For details about the engineering guidelines for this feature, see 7.2
LOFD-001087 SRVCC Flexible Steering to UTRAN. This feature is controlled by UtranSrvccSteeringSwitch under the ENodeBAlgoSwitch.FreqLayerSwtich
parameter.
This feature applies in scenarios where an operator has both an E-UTRAN and a UTRAN and the UTRAN is provided by a site that operates on multiple UTRAN
frequencies. In this scenario, SRVCC takes into account the CS service priorities of the frequencies, and the operator can achieve SRVCC from E-UTRAN to a specific
high-priority UTRAN frequency. With this feature, fewer UTRAN frequencies are measured, which reduces the measurement time and the probability of UE errors.
This feature is an enhancement of LOFD-001022 SRVCC to UTRAN and requires that LOFD-001078 E-UTRAN to UTRAN CS/PS Steering be activated. LOFD-001087
SRVCC Flexible Steering to UTRAN applies only to coverage-based handover for SRVCC.
LOFD-001087 SRVCC Flexible Steering to UTRAN uses the CS service priorities specified by UtranNFreq.CsPriority in the measurement phase. The procedure for
selecting measurement objects is the same as the procedure given in LOFD-001078 E-UTRAN to UTRAN CS/PS Steering. For details about the procedure, see InterRAT Mobility Management in Connected Mode Feature Parameter Description.
3.3 SRVCC Selection Procedure
SRVCC is one of the policies of E-UTRAN to UTRAN handover. Other policies include PS handover, redirection, and flash redirection; their selection procedures are
described in Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
Figure 3-1 shows the SRVCC selection procedure. This procedure starts with determining whether the VoIP capability switch is turned on. For subsequent detailed
procedures after deciding whether the PS handover switch or the redirection switch is turned on, see Inter-RAT Mobility Management in Connected Mode Feature
Parameter Description. The following figure describes the SRVCC selection procedure based only on the related switches, assuming that neighboring frequencies or
cells are correctly configured.
Figure 3-1 SRVCC selection procedure
The parameters mentioned in the preceding figure are described as follows:
• The UTRAN capability switches are controlled by the options of the ENodeBAlgoSwitch.HoModeSwitch parameter:
◾ The UTRAN VoIP switch is controlled by the UtranVoipCapSwitch option.
◾ The UTRAN SRVCC switch is controlled by the UtranSrvccSwitch option.
• The switch for checking whether a UE supports VoIP over HSPA is controlled by the UeVoipOnHspaCapSwitch option of the
ENodeBAlgoSwitch.HoModeSwitch parameter.
• The handover policy for a QCI is specified by the InterRatPolicyCfgGroup.UtranHoCfg parameter.
The handover policy and the QCI are associated with each other through the following parameters:
◾ InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId
◾ StandardQci.InterRatPolicyCfgGroupId or ExtendedQci.InterRatPolicyCfgGroupId
NOTE:
Retain the default policy for each QCI. Otherwise, no correct inter-RAT handover policy can be selected.
If a bearer of QCI 1 is used to carry VoIP and the corresponding InterRatPolicyCfgGroup.UtranHoCfg parameter is set to REDIRECTION, call drop may occur during
redirection. In this case, do not set the policy to REDIRECTION.
3.4 Signaling Procedure
SRVCC Triggered by Common Causes
Figure 3-2 shows the signaling procedure for SRVCC from E-UTRAN to UTRAN. (The procedure for SRVCC to GERAN is the same.) For details, see section 6.2
"E-UTRAN and 3GPP GERAN/UTRAN SRVCC" in 3GPP TS 23.216 V9.4.0.
Figure 3-2 Signaling procedure for SRVCC to UTRAN/GERAN
1. After triggering an SRVCC procedure, the eNodeB delivers the inter-RAT measurement configuration to the UE.
2. The UE responds to the eNodeB with an RRC Connection Reconfiguration Complete message.
3. After detecting that a neighboring cell meets the condition for triggering an inter-RAT handover, the UE sends a measurement report to the eNodeB.
4. The eNodeB determines that a handover should be performed and sends a Handover Required message containing an SRVCC HO Indication to the MME.
5. The MME separates the voice bearer from non-voice bearers and then sends a Relocation Request message to both the SRVCC MSC server and target
SGSN.
6. After receiving the Relocation Request message, the SRVCC MSC server identifies the target MSC server based on the target cell ID contained within the
message. The SRVCC MSC server communicates with the target MSC server on a handover. Then, the target MSC server instructs the target radio network
controller (RNC) or base station controller (BSC) to prepare for the handover. Once the resources are ready, the target RNC or BSC responds to the target
MSC server. Meanwhile, the target SGSN prepares for a handover of PS services, which is the same as an inter-RAT PS handover procedure. The UE
media plane is then transferred on the IMS.
NOTE:
If the value of the SRVCC HO Indication information element (IE) is "CS Only" in the Handover Required message sent from the eNodeB to the MME, the
MME instructs only the MSC server to prepare for a handover. If the value of the SRVCC HO Indication IE is "PS and CS", the MME instructs both the MSC
server and SGSN to prepare for a handover.
For a CS-only SRVCC procedure, if the target network is UTRAN, the PS services of the UE resume during a routing area update (RAU) procedure in the
UTRAN. If the target network is GERAN, PS service handling depends on whether the UE and BSC support Dual Transfer Mode (DTM). If both the UE and
BSC support DTM, the PS services of the UE resume during an RAU procedure in the GERAN. If either the UE or the BSC is DTM-incapable, the PS
services of the UE are suspended.
7. The MME receives a response from the target MSC server or target SGSN, indicating that the handover preparation is complete.
8. The MME delivers a handover command to the eNodeB.
9. The eNodeB delivers a handover command to the UE.
10. After receiving the handover command, the UE accesses the target network.
11. The UE sends the target radio access network (RAN) a Handover Complete message, indicating that the handover procedure for SRVCC is complete.
LCS-based SRVCC
Figure 3-3 shows the signaling procedure for LCS-based SRVCC.
Figure 3-3 Signaling procedure for LCS-based SRVCC
4 SRVCC from E-UTRAN to GERAN
4.1 SRVCC to GERAN
This section describes the optional feature LOFD-001023 SRVCC to GERAN. For details about the engineering guidelines for this feature, see 7.3 LOFD-001023
SRVCC to GERAN. This feature is controlled by GeranSrvccSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter.
Several factors may trigger SRVCC to GERAN. For detailed measurement triggering, see the documents listed in Table 4-1.
Table 4-1 Mapping between documents and features/functions
Feature/Function
•
•
•
•
Coverage-based inter-RAT handover to GERAN
Service-based inter-RAT handover to GERAN
Distance-based inter-RAT handover to GERAN
UL-quality-based inter-RAT handover to GERAN
Document
Inter-RAT Mobility Management in
Connected Mode Feature Parameter
Description
Load-based inter-RAT handover to GERAN
MLB Feature Parameter Description
SPID-based inter-RAT handover
Flexible User Steering Feature Parameter
Description
Other triggers and execution of SRVCC to GERAN are the same as those for SRVCC to UTRAN. For details, see 3.1 SRVCC to UTRAN.
4.2 SRVCC Selection Procedure
SRVCC is one of the policies of E-UTRAN to GERAN handover. Other policies include PS handover, CCO/NACC, redirection, and flash redirection; their selection
procedures are described in Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
Figure 4-1 shows the SRVCC selection procedure. This procedure starts with determining whether the VoIP capability switch is turned on. For subsequent detailed
procedures, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description. The following figure describes the SRVCC selection procedure
based only on the related switches, assuming that neighboring frequencies or cells are correctly configured.
Figure 4-1 SRVCC selection procedure
The parameters mentioned in the preceding figure are described as follows:
• The GERAN capability switches are controlled by the options of the ENodeBAlgoSwitch.HoModeSwitch parameter:
◾ The GERAN VoIP capability is controlled by the GeranVoipCapSwitch option.
◾ The GERAN SRVCC switch is controlled by the GeranSrvccSwitch option.
• The handover policy for a QCI is controlled by the InterRatPolicyCfgGroup.GeranGsmHoCfg or InterRatPolicyCfgGroup.GeranGprsEdgeHoCfg
parameter.
The handover policy and the QCI are associated with each other through the following parameters:
◾ InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId
◾ StandardQci.InterRatPolicyCfgGroupId or ExtendedQci.InterRatPolicyCfgGroupId.
NOTE:
Retain the default policy for each QCI. Otherwise, no correct inter-RAT handover policy can be selected.
If a bearer of QCI 1 is used to carry VoIP and the corresponding InterRatPolicyCfgGroup.GeranGprsEdgeHoCfg parameter is set to REDIRECTION, call drop may
occur during redirection. In this case, do not set the policy to REDIRECTION.
4.3 Signaling Procedure
The signaling procedure for SRVCC to GERAN is the same as that for SRVCC to UTRAN. For details, see 3.4 Signaling Procedure.
5 Related Features
5.1 Features Related to LOFD-001022 SRVCC to UTRAN
Prerequisite Features
None
Mutually Exclusive Features
None
Impacted Features
None
5.2 Features Related to LOFD-001087 SRVCC Flexible Steering to UTRAN
Prerequisite Features
LOFD-001087 SRVCC Flexible Steering to UTRAN requires LOFD-001022 SRVCC to UTRAN and LOFD-001078 E-UTRAN to UTRAN CS/PS Steering.
Mutually Exclusive Features
None
Impacted Features
None
5.3 Features Related to LOFD-001023 SRVCC to GERAN
Prerequisite Features
None
Mutually Exclusive Features
None
Impacted Features
None
6 Network Impact
6.1 LOFD-001022 SRVCC to UTRAN
System Capacity
No impact
Network Performance
If the target network of a CS-only SRVCC procedure is a UTRAN, only the bearer with QCI 1 is diverted to the CS domain of the target network; bearers with other QCIs
complete the RAU procedure and re-establish the PS service in the target network.
The CS-only SRVCC procedure results in a service interruption period of several seconds for PS services. However, the PS-and-CS SRVCC procedure has a service
interruption period of only hundreds of milliseconds for PS services.
6.2 LOFD-001087 SRVCC Flexible Steering to UTRAN
System Capacity
No impact
Network Performance
• SRVCC flexible steering to UTRAN reduces the measurement time because less UTRAN frequencies are measured. It also reduces the probability of UE
abnormalities caused by prolonged measurement time.
• After SRVCC flexible steering to UTRAN is activated, CS services are steered to UTRAN frequencies with high CS service priorities if the UEs support
SRVCC and SRVCC is enabled on the eNodeB.
• UEs measure only the UTRAN frequencies that have the highest CS service priority among the UE-supported frequencies. If an operator does not deploy
sufficient UTRAN frequencies with high CS service priority, the SRVCC success rate may decrease.
6.3 LOFD-001023 SRVCC to GERAN
System Capacity
No impact
Network Performance
If the target network of a CS-only SRVCC procedure is a DTM-supporting GERAN, only the bearer with QCI 1 is diverted to the CS domain of the target network; bearers
with other QCIs complete the RAU procedure and re-establish the PS service in the target network.
The CS-only SRVCC procedure results in a service interruption period of several seconds for PS services. However, the PS-and-CS SRVCC procedure has a service
interruption period of only hundreds of milliseconds for PS services.
7 Engineering Guidelines
7.1 LOFD-001022 SRVCC to UTRAN
7.1.1 When to Use SRVCC to UTRAN
Use SRVCC to UTRAN if the operator provides IMS-based VoIP services in an LTE network and voice services in a legacy UTRAN CS network and if the E-UTRAN
does not cover the entire mobile network.
7.1.2 Required Information
Collect the following information:
• Operating frequencies, coverage areas, and configurations of E-UTRAN and UTRAN cells.
• Versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks. Ensure that they all support SRVCC to UTRAN.
• Operating frequency bands, supported measurement events, and SRVCC capabilities of UMTS+LTE UEs on live networks.
7.1.3 Process
To deploy SRVCC to UTRAN, you must complete the following steps:
• Formulate a neighboring cell plan and configure the neighboring cells accordingly when both UMTS and LTE networks are deployed.
• Configure parameters of handover thresholds related to SRVCC to UTRAN.
• Prepare the license file related to SRVCC to UTRAN and configure algorithm switches related to SRVCC to UTRAN.
7.1.4 Requirements
Operating Environment
For SRVCC to UTRAN, the eNodeB must collaborate with core-network equipment.
• If the core-network equipment (including the IMS equipment) is provided by Huawei, the version must be VoLTE1.0 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 SRVCC to UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-1.
Table 7-1 License information for SRVCC to UTRAN
Feature ID
Feature Name
License Control Item
NE
Sales Unit
LOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
eNodeB
per RRC Connected User
7.1.5 Data Preparation
This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data
when necessary for a specific feature deployment scenario.
There are three types of data sources:
• Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
• Network plan (negotiation not required): parameter values planned and set by the operator
• User-defined: parameter values set by users
Required Data
Before configuring SRVCC to UTRAN, collect the data related to neighbor relationships with UTRAN cells. This section provides only the information about managed
objects (MOs) related to neighboring UTRAN cells. For more information about how to collect data for the parameters in these MOs, see Inter-RAT Mobility Management
in Connected Mode Feature Parameter Description.
Collect data for the parameters in the following MOs:
• UtranNFreq: used to configure neighboring UTRAN frequencies.
• UtranExternalCell: used to configure external UTRAN cells. The UtranExternalCell.Rac parameter must be set.
• UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared external UTRAN cell. This MO is required only if the NodeB that provides
the external UTRAN cell works in RAN sharing with common carriers mode and multiple operators share the external UTRAN cell.
• 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 parameter that must be set in the ENodeBAlgoSwitch MO to enable SRVCC to UTRAN.
Table 7-2 SRVCC to UTRAN switch
Parameter Name
Parameter ID
Data Source
Setting Notes
Handover Mode switch
ENodeBAlgoSwitch.HoModeSwitch
Network plan (negotiation not required)
To enable SRVCC to UTRAN, select the
UtranSrvccSwitch(UtranSrvccSwitch)
check box under this parameter.
The following table describes the parameters that must be set in an InterRatPolicyCfgGroup MO to configure an inter-RAT handover policy group.
Table 7-3 Inter-RAT handover policy group
Parameter Name
Parameter ID
Data Source
InterRAT policy
config group ID
InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId Network plan (negotiation not
required)
Set this parameter for use in the StandardQci MO
described in Table 7-4.
UTRAN handover
policy Configuration
InterRatPolicyCfgGroup.UtranHoCfg
Select the SRVCC check box under this parameter.
Network plan (negotiation not
required)
Setting Notes
The following table describes the parameters that must be set in the StandardQci MO to configure a QCI-based inter-RAT handover policy group.
Table 7-4 Parameters for QCI 1
Parameter Name
Parameter ID
Data Source
QoS Class Indication
StandardQci.Qci
Network plan (negotiation not required) Set this parameter as required, for example, set this
parameter to QCI1(QCI 1).
Setting Notes
InterRAT policy config
group ID
StandardQci.InterRatPolicyCfgGroupId Network plan (negotiation not required) Set this parameter to the value of the InterRAT policy
config group ID parameter in the
InterRatPolicyCfgGroup MO described in Table 7-3.
NOTE:
• For mandatory handovers, for example, coverage-based and UL-quality-based handovers, SRVCC can be triggered when SRVCC is configured in the interRAT handover policy groups for QCI 5 and QCI 1.
• For optional handovers, for example, load-based, service-based, and CSFB-based handovers, SRVCC can be triggered when SRVCC is configured in the
inter-RAT handover policy groups for all QCIs.
The following table describes the parameters that must be set to configure LCS-based SRVCC. If LCS is required when a UE is performing a service with QCI 1 in an
LTE network that supports IMS but does not support LCS, the UE needs to fall back to a CS domain to perform LCS.
Table 7-5 Parameter for LCS-triggered SRVCC
Parameter Name
Parameter ID
Data Source
Handover Mode switch
ENodeBAlgoSwitch.HoModeSwitch
Network plan (negotiation not required) Select the LcsSrvccSwitch check box.
Setting Notes
UTRAN LCS capability
CSFallBackBlindHoCfg.UtranLcsCap
Network plan (negotiation not required) Set this parameter to ON(On).
7.1.6 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-6 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the
summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
• The MOs in Table 7-6 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.
• Some MOs in Table 7-6 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.
Table 7-6 Parameters related to SRVCC to UTRAN
MO
Sheet in the Summary Data
File
Parameter Group
Remarks
UtranNFreq
UtranNFreq
Local cell identity, Downlink UARFCN
The template RNPtemplate is
recommended.
UtranExternalCell
UtranExternalCell
Mobile country code, Mobile network code, UTRAN
cell identity, Downlink UARFCN, RNC identity,
Primary scrambling code, Location area code
The template RNPtemplate is
recommended.
UtranExternalCellPlmn
UtranExternalCellPlmn
UTRAN cell identity, Mobile country code, Mobile
network code, Share mobile country code, Share
mobile network code
The template RNPtemplate is
recommended.
UtranNCell
UtranNCell
Local cell identity, Mobile country code, Mobile
network code, UTRAN cell identity, Blind handover
priority
The template RNPtemplate is
recommended.
ENodeBAlgoSwitch
User-defined sheet
ENodeBAlgoSwitch is
recommended.
HoModeSwitch
A list-type sheet is recommended.
InterRatPolicyCfgGroup User-defined sheet
InterRatPolicyCfgGroup is
recommended.
InterRatPolicyCfgGroupId, UtranHoCfg
A list-type sheet is recommended.
StandardQci
Qci, InterRatPolicyCfgGroupId
A list-type sheet is recommended.
User-defined sheet
StandardQci is recommended.
Using the CME to Perform Batch Configuration for Existing eNodeBs
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:
1. Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose Advanced > Customize Summary Data File (CME client
mode), to customize a summary data file for batch reconfiguration.
NOTE:
For context-sensitive help on a current task in the client, press F1.
2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (M2000 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.
3. In the summary data file, set the parameters in the MOs listed in Table 7-6 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (M2000 client mode), or choose LTE Application >
Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window
3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
Using MML Commands
• Scenario 1: CS-only SRVCC to UTRAN
1. Add neighboring UTRAN frequencies and neighbor relationships with UTRAN cells, and set parameters for inter-RAT measurements. For details about
parameter settings, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
2. Run the MOD ENODEBALGOSWITCH command with the UtranSrvccSwitch(UtranSrvccSwitch) check box selected under the Handover Mode switch
parameter.
3. Run the MOD INTERRATPOLICYCFGGROUP command with the InterRAT policy config group ID parameter set to 0 and with the SRVCC check box
selected under the UTRAN handover policy Configuration parameter.
4. Run the MOD STANDARDQCI command with the InterRAT policy config group ID parameter set to 0 for QCI 1 and QCI 5.
5. Run the MOD UTRANEXTERNALCELL command with the CS and PS handover indicator parameter set to BOOLEAN_FALSE(False).
• Scenario 2: CS-and-PS SRVCC to UTRAN
1. Add neighboring UTRAN frequencies and neighbor relationships with UTRAN cells, and set parameters for inter-RAT measurements. For details about
parameter settings, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
2. Run the MOD ENODEBALGOSWITCH command with the UtranSrvccSwitch(UtranSrvccSwitch) and UtranPsHoSwitch(UtranPsHoSwitch) check
boxes selected under the Handover Mode switch parameter.
3. Run the MOD INTERRATPOLICYCFGGROUP command with the InterRAT policy config group ID parameter set to 0 and with the SRVCC and PS_HO
check boxes selected under the UTRAN handover policy Configuration parameter.
4. Run the MOD STANDARDQCI command with the InterRAT policy config group ID parameter set to 0 for QCI 1 and QCI 5.
5. Run the MOD UTRANEXTERNALCELL command with the CS and PS handover indicator parameter set to BOOLEAN_TRUE(True).
• Scenario 3: LCS-based SRVCC to UTRAN
1. Run the MOD ENODEBALGOSWITCH command with the LcsSrvccSwitch check box selected under the Handover Mode switch parameter.
2. Run the MOD CSFALLBACKBLINDHOCFG command with the UTRAN LCS capability parameter set to ON(On).
MML Command Examples
• Scenario 1: CS-only SRVCC to UTRAN
MOD ENODEBALGOSWITCH: HoModeSwitch=UtranSrvccSwitch-1;
MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, UtranHoCfg=SRVCC-1;
MOD STANDARDQCI: Qci=QCI1, InterRatPolicyCfgGroupId=0;
MOD STANDARDQCI: Qci=QCI5, InterRatPolicyCfgGroupId=0;
MOD UTRANEXTERNALCELL: Mcc="460", Mnc="20", RncId=48, CellId=12, RacCfgInd=CFG, Rac=89,CsPsHOInd=BOOLEAN_FALSE;
• Scenario 2: CS-and-PS SRVCC to UTRAN
MOD ENODEBALGOSWITCH: HoModeSwitch=UtranPsHoSwitch-1&UtranSrvccSwitch-1;
MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, UtranHoCfg=PS_HO-1&SRVCC-1;
MOD STANDARDQCI: Qci=QCI1, InterRatPolicyCfgGroupId=0;
MOD STANDARDQCI: Qci=QCI5, InterRatPolicyCfgGroupId=0;
MOD UTRANEXTERNALCELL: Mcc="460", Mnc="20", RncId=48, CellId=12, RacCfgInd=CFG, Rac=89,CsPsHOInd=BOOLEAN_TRUE;
• Scenario 3: LCS-based SRVCC to UTRAN
MOD ENODEBALGOSWITCH: HoModeSwitch=LcsSrvccSwitch-1;
MOD CSFALLBACKBLINDHOCFG: UtranLcsCap=ON;
7.1.7 Activation Observation
Tracing Signaling Messages of a Single UE
Perform standard S1 interface tracing for a single UE. If the traced Handover Required message, as shown in Figure 7-2, contains the SRVCC HO Indication IE, SRVCC
to UTRAN has been activated.
Figure 7-2 SRVCC HO Indication IE contained in the Handover Required message
Figure 7-3 CS-and-PS SRVCC signaling tracing
Figure 7-4 CS-only SRVCC signaling tracing
Observing Performance Counters
Observe the counters described in Table 7-7. If the value of a counter is not 0, the related feature or function has been activated.
Table 7-7 Mapping between counters and features/functions
Feature/Function
Counter ID
Counter Name
Counter Description
SRVCC to UTRAN
1526728400
L.IRATHO.SRVCC.E2W.PrepAttOut
Number of inter-RAT handover attempts
from E-UTRAN to WCDMA network for
SRVCC
7.1.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships,
for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in "Using the CME to Perform Batch
Configuration for Existing eNodeBs." In the procedure, modify parameters according to Table 7-8.
Table 7-8 Parameters for SRVCC to UTRAN
MO
Sheet in the Summary Data File
Parameter Group
Remarks
ENodeBAlgoSwitch
User-defined sheet
ENodeBAlgoSwitch is recommended.
HoModeSwitch
Set UtranSrvccSwitch under the HoModeSwitch
parameter to 0.
Using the CME to Perform Single Configuration
On the CME, set parameters according to Table 7-8. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands
Run the MOD ENODEBALGOSWITCH command with the UtranSrvccSwitch(UtranSrvccSwitch) check box cleared under the Handover Mode switch parameter.
MML Command Examples
MOD ENODEBALGOSWITCH: HoModeSwitch=UtranSrvccSwitch-0;
7.1.9 Performance Monitoring
Table 7-9 lists the performance counters for monitoring SRVCC to UTRAN.
Table 7-9 Performance counters for monitoring SRVCC to UTRAN
Counter ID
Counter Name
Description
1526728400
L.IRATHO.SRVCC.E2W.PrepAttOut
Number of inter-RAT handover attempts from E-UTRAN to WCDMA
network for SRVCC
1526728401
L.IRATHO.SRVCC.E2W.ExecAttOut
Number of inter-RAT handover executions from E-UTRAN to WCDMA
network for SRVCC
1526728402
L.IRATHO.SRVCC.E2W.ExecSuccOut
Number of successful inter-RAT handovers from E-UTRAN to
WCDMA network for SRVCC
1526728406
L.IRATHO.SRVCC.E2T.PrepAttOut
Number of inter-RAT handover attempts from E-UTRAN to TDSCDMA network for SRVCC
1526728407
L.IRATHO.SRVCC.E2T.ExecAttOut
Number of inter-RAT handover executions from E-UTRAN to TDSCDMA for SRVCC
1526728408
L.IRATHO.SRVCC.E2T.ExecSuccOut
Number of successful inter-RAT handovers from E-UTRAN to TDSCDMA network for SRVCC
Table 7-10 lists the performance counters for monitoring LCS-based SRVCC when UEs are running services with QCI 1.
Table 7-10 Performance counters for monitoring LCS-based SRVCC
Counter ID
Counter Name
Description
1526728409
L.CSFB.LCS.PrepAtt
Number of LCS-triggered CS fallback indicators received by the
eNodeB
1526728410
L.CSFB.LCS.PrepSucc
Number of responses sent from the eNodeB to MMEs for CSFB
triggered by LCS
1526728753
L.IRATHO.SRVCC.LCS.E2W.PrepAttOut
Number of CSFB-based handover attempts from E-UTRAN to
WCDMA network for SRVCC
1526728754
L.IRATHO.SRVCC.LCS.E2W.ExecAttOut
Number of CSFB-based handover executions from E-UTRAN to
WCDMA network for SRVCC
1526728755
L.IRATHO.SRVCC.LCS.E2W.ExecSuccOut
Number of successful CSFB-based handovers from E-UTRAN to
WCDMA network for SRVCC
1526728759
L.IRATHO.SRVCC.LCS.E2T.PrepAttOut
Number of CSFB-based handover attempts from E-UTRAN to TDSCDMA network for SRVCC
1526728760
L.IRATHO.SRVCC.LCS.E2T.ExecAttOut
Number of CSFB-based handover executions from E-UTRAN to
TD-SCDMA network for SRVCC
1526728761
L.IRATHO.SRVCC.LCS.E2T.ExecSuccOut
Number of successful CSFB-based handovers from E-UTRAN to
TD-SCDMA network for SRVCC
Table 7-11 lists the performance counters for monitoring SRVCC triggered for emergency calls.
Table 7-11 Performance counters for monitoring SRVCC triggered for emergency calls
Counter ID
Counter Name
Description
1526729517
L.EMC.SRVCC.E2W.PrepAttOut
Number of handover attempts from E-UTRAN to WCDMA network
for SRVCC triggered for emergency calls
1526729518
L.EMC.SRVCC.E2W.ExecAttOut
Number of handover executions from E-UTRAN to WCDMA
network for SRVCC triggered for emergency calls
1526729519
L.EMC.SRVCC.E2W.ExecSuccOut
Number of successful handovers from E-UTRAN to WCDMA
network for SRVCC triggered for emergency calls
1526729523
L.EMC.SRVCC.E2T.PrepAttOut
Number of handover attempts from E-UTRAN to TD-SCDMA
network for SRVCC triggered for emergency calls
1526729524
L.EMC.SRVCC.E2T.ExecAttOut
Number of handover executions from E-UTRAN to TD-SCDMA
network for SRVCC triggered for emergency calls
1526729525
L.EMC.SRVCC.E2T.ExecSuccOut
Number of successful handovers from E-UTRAN to TD-SCDMA
network for SRVCC triggered for emergency calls
Calculate SRVCC preparation and execution success rates. If the results do not meet the SRVCC performance requirements of an operator, perform fault isolation and
diagnosis. Take monitoring the performance of SRVCC to UTRAN as an example. The formulas for calculating other success rates are similar to the following:
• L.IRATHO.SRVCC.E2W.ExecSuccOut/L.IRATHO.SRVCC.E2W.PrepAttOut
• L.IRATHO.SRVCC.E2W.ExecAttOut/L.IRATHO.SRVCC.E2W.PrepAttOut
7.1.10 Parameter Optimization
Event B1/B2 Trigger Thresholds
For details about how to optimize the event B1/B2 trigger thresholds for coverage- or service-based SRVCC, see Inter-RAT Mobility Management in Connected Mode
Feature Parameter Description.
For details about how to optimize the event B1 trigger threshold for LCS-based SRVCC, see CS Fallback Feature Parameter Description.
CS Service Priorities
The eNodeB generally selects the frequencies with highest CS priority and delivers the corresponding measurement configurations for SRVCC flexible steering to
UTRAN. It is recommended that the frequency with the widest coverage be assigned the highest priority for CS service to increase the SRVCC success rate.
7.2 LOFD-001087 SRVCC Flexible Steering to UTRAN
7.2.1 When to Use SRVCC Flexible Steering to UTRAN
Use SRVCC Flexible Steering to UTRAN if the operator has both an E-UTRAN and a UTRAN, and if the UTRAN is operating on multiple UTRAN frequencies, one or
some of which cover the entire UTRAN. In SRVCC Flexible Steering to UTRAN, assign the highest CS service priority to the UTRAN frequency that covers the entire
UTRAN.
7.2.2 Required Information
Collect the following information:
• Operating frequencies, coverage areas, and configurations of E-UTRAN and UTRAN cells, especially the coverage of each UTRAN frequency, which can be
used as a reference for setting CS service priorities
• Versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks. Ensure that they all support SRVCC.
• Operating frequency bands, supported measurement events, and SRVCC capabilities of UMTS+LTE UEs on live networks.
7.2.3 Process
To deploy SRVCC Flexible Steering to UTRAN, you must complete the following steps:
• Deploy the SRVCC to UTRAN feature.
• Configure parameters related to SRVCC Flexible Steering to UTRAN.
• Prepare the license file related to SRVCC Flexible Steering to UTRAN and configure algorithm switches related to SRVCC Flexible Steering to UTRAN.
7.2.4 Requirements
Operating Environment
For SRVCC Flexible Steering to UTRAN, the eNodeB must collaborate with core-network equipment.
• If the core-network equipment (including the IMS equipment) is provided by Huawei, the version must be VoLTE1.0 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 SRVCC Flexible Steering to UTRAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-12.
Table 7-12 License information for SRVCC Flexible Steering to UTRAN
Parameter ID
Parameter Name
License Control Item
NE
Sales Unit
LOFD-001087
SRVCC Flexible Steering to
UTRAN
SRVCC Flexible Steering to
UTRAN
eNodeB
per RRC Connected User
7.2.5 Data Preparation
This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data
when necessary for a specific feature deployment scenario.
There are three types of data sources:
• Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
• Network plan (negotiation not required): parameter values planned and set by the operator
• User-defined: parameter values set by users
Required Data
SRVCC Flexible Steering to UTRAN operates on the basis of SRVCC to UTRAN. Therefore, the required data for SRVCC Flexible Steering to UTRAN are all the data
required for SRVCC to UTRAN. For details, see 7.1.5 Data Preparation for SRVCC to UTRAN.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable SRVCC Flexible Steering to UTRAN.
Table 7-13 Switch for SRVCC Flexible Steering to UTRAN
Parameter Name
Parameter ID
Frequency Layer Switch
ENodeBAlgoSwitch.FreqLayerSwtich Network plan
(negotiation not
required)
Data Source
Setting Notes
Select the UtranSrvccSteeringSwitch(UtranSrvccSteeringSwitch)
check box under this parameter.
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable measurement-based handover for flexible steering.
Table 7-14 Switch of measurement-based handover for flexible steering
Parameter Name
Parameter ID
Frequency Layer Switch
ENodeBAlgoSwitch.FreqLayerSwtich Network plan (negotiation not Select the UtranFreqLayerMeasSwitch
required)
(UtranFreqLayerMeasSwitch) check box under this parameter.
Data Source
Setting Notes
The following table describes the parameter that must be set in a UtranNFreq MO to configure the CS service priority of a UTRAN frequency.
Table 7-15 CS service priority of a UTRAN frequency
Parameter Name
Parameter ID
Data Source
Setting Notes
CS service priority
UtranNFreq.CsPriority
Network plan (negotiation not required)
Set this parameter based on the
network plan. When this parameter is
set to Priority_0(Priority 0) for the
UTRAN frequency, the eNodeB does
not select the frequency for SRVCC.
The values Priority_16(Priority 16) and
Priority_1(Priority 1) indicate the
highest and lowest CS service priority,
respectively.
Set a high priority for a UTRAN
frequency with good coverage.
NOTE:
As described in section 8.1.2.1.1.1 of 3GPP TS 36.133 V10.1.0 (2010-12), a UE is capable of measuring at least three UTRAN frequencies. To be compatible with UE
capabilities, the eNodeB delivers only three neighboring UTRAN frequencies to the UE for inter-RAT measurement. Therefore, assign the highest CS service priority to
three UTRAN frequencies at most.
7.2.6 Activation
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 Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
• 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.
• 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.
Table 7-16 Parameters for SRVCC Flexible Steering to UTRAN
MO
Sheet in the Summary Data File
Parameter Group
Remarks
ENodeBAlgoSwitch
User-defined sheet
ENodeBAlgoSwitch is
recommended.
FreqLayerSwtich
A list-type sheet is recommended.
UtranNFreq
User-defined sheet
UtranNFreq is recommended.
LocalCellId, UtranDlArfcn, CsPriority
A list-type sheet is recommended.
NOTE:
You must activate and configure the SRVCC to UTRAN feature before activating the SRVCC Flexible Steering to UTRAN feature.
Using the CME to Perform Batch Configuration for Existing eNodeBs
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:
1. Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose Advanced > Customize Summary Data File (CME client
mode), to customize a summary data file for batch reconfiguration.
NOTE:
For context-sensitive help on a current task in the client, press F1.
2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (M2000 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.
3. In the summary data file, set the parameters in the MOs listed in Table 7-16 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (M2000 client mode), or choose LTE Application >
Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 7-5, select the eNodeB to which the MOs belong.
Figure 7-5 MO search and configuration window
3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
Using MML Commands
The prerequisite is that SRVCC to UTRAN has been activated.
Perform the following steps:
1. Run the MOD ENODEBALGOSWITCH command with the UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) and UtranSrvccSteeringSwitch
(UtranSrvccSteeringSwitch) check boxes selected under the Frequency Layer Switch parameter.
2. Run the MODUTRANNFREQ command with the CS service priority parameter set to Priority_16(Priority 16).
MML Command Examples
MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-1&UtranSrvccSteeringSwitch-1;
MOD UTRANNFREQ: LocalCellId=0,UtranDlArfcn=10800,CsPriority=Priority_16;
7.2.7 Activation Observation
Perform Uu interface tracing for a single UE. In the tracing result, if the eNodeB delivers only the UTRAN frequencies with the highest CS service priority to the UE, as
shown in Figure 7-6, SRVCC Flexible Steering to UTRAN has been activated.
Figure 7-6 UTRAN frequencies for measurement during SRVCC
If SRVCC Flexible Steering to UTRAN has been activated, the eNodeB delivers only the UTRAN frequency 10700, which is with the highest CS service priority, to the
UE, as shown in Figure 7-7.
Figure 7-7 Signaling tracing
7.2.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships,
for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in "Using the CME to Perform Batch
Configuration for Existing eNodeBs." In the procedure, modify parameters according to Table 7-17.
Table 7-17 Parameters for SRVCC Flexible Steering to UTRAN
MO
Sheet in the Summary Data File
Parameter Group
Remarks
ENodeBAlgoSwitch
User-defined sheet
ENodeBAlgoSwitch is recommended.
FreqLayerSwtich
Set UtranSrvccSteeringSwitch under
the FreqLayerSwtich parameter to 0.
Using the CME to Perform Single Configuration
On the CME, set parameters according to Table 7-17. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.
Using MML Commands
Run the MOD ENODEBALGOSWITCH command with the UtranSrvccSteeringSwitch(UtranSrvccSteeringSwitch) check box cleared under the Frequency Layer
Switch parameter.
MML Command Examples
MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranSrvccSteeringSwitch-0;
7.2.9 Performance Monitoring
The performance monitoring methods are the same as those for SRVCC to UTRAN. For details, see 7.1.9 Performance Monitoring.
7.2.10 Parameter Optimization
It is recommended that the frequency with the widest coverage be assigned the highest priority for CS service to increase the SRVCC success rate.
7.3 LOFD-001023 SRVCC to GERAN
7.3.1 When to Use SRVCC to GERAN
Use SRVCC to GERAN if the operator provides IMS-based VoIP services in an LTE network and voice services in a legacy GERAN CS network and if the E-UTRAN
does not cover the entire mobile network.
7.3.2 Required Information
Collect the following information:
• Operating frequencies, coverage areas, and configurations of E-UTRAN and GERAN cells.
• Versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks. Ensure that they all support SRVCC to GERAN.
• Operating frequency bands, supported measurement events, and SRVCC capabilities of GSM+LTE UEs on live networks.
7.3.3 Process
To deploy SRVCC to GERAN, you must complete the following steps:
• Formulate a neighboring cell plan and configure the neighboring cells accordingly when both GSM and LTE networks are deployed.
• Configure parameters of handover thresholds related to SRVCC to GERAN.
• Prepare the license file related to SRVCC to GERAN and configure algorithm switches related to SRVCC to GERAN.
7.3.4 Requirements
Operating Environment
For SRVCC to GERAN, the eNodeB must collaborate with core-network equipment.
• If the core-network equipment (including the IMS equipment) is provided by Huawei, the version must be VoLTE1.0 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 SRVCC to GERAN.
License
The operator has purchased and activated the license for the feature listed in Table 7-18.
Table 7-18 License information for SRVCC to GERAN
Parameter ID
Parameter Name
License Control Item
NE
Sales Unit
LOFD-001023
SRVCC to GERAN
SRVCC to GERAN
eNodeB
per RRC Connected User
7.3.5 Data Preparation
This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data
when necessary for a specific feature deployment scenario.
There are three types of data sources:
• Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
• Network plan (negotiation not required): parameter values planned and set by the operator
• User-defined: parameter values set by users
Required Data
Before configuring SRVCC to GERAN, collect the data related to neighbor relationships with GERAN cells. This section provides only the information about MOs related
to neighboring GERAN cells. For more information about how to collect data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected Mode
Feature Parameter Description.
Collect data for the parameters in the following MOs:
• GeranNfreqGroup: used to configure GERAN carrier frequency groups.
• GeranNfreqGroupArfcn: used to configure absolute radio frequency channel numbers (ARFCNs) in each GERAN carrier frequency group.
• GeranExternalCell: used to configure external GERAN cells. The GeranExternalCell.Rac parameter must be set.
• GeranExternalCellPlmn: used to configure additional PLMN IDs for each shared external GERAN cell. This MO is required only if the BTS that provides the
external GERAN cell works in RAN sharing with common carriers mode and multiple operators share the external GERAN cell.
• GeranNcell: used to configure neighbor relationships with GERAN cells. If a neighboring GERAN cell supports blind handovers according to the network
plan, the blind-handover priority of the cell must be specified by the GeranNcell.BlindHoPriority parameter.
Scenario-specific Data
The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable SRVCC to GERAN.
Table 7-19 SRVCC to GERAN switch
Parameter Name
Parameter Name
Data Source
Setting Notes
Handover Mode
switch
ENodeBAlgoSwitch.HoModeSwitch
Network plan (negotiation not
required)
To enable SRVCC to GERAN, select the GeranSrvccSwitch
(GeranSrvccSwitch) check box under this parameter.
The following table describes the parameters that must be set in an InterRatPolicyCfgGroup MO to configure an inter-RAT handover policy group.
Table 7-20 Inter-RAT handover policy group
Parameter Name
Parameter ID
InterRAT policy
config group ID
InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId Network plan (negotiation not Set this parameter for use in the StandardQci MO
required)
described in Table 7-21.
Data Source
Setting Notes
GERAN GSM
handover policy
Configuration
InterRatPolicyCfgGroup.GeranGsmHoCfg
Network plan (negotiation not Select the SRVCC check box under this parameter.
required)
GERAN GPRS
EDGE handover
policy
Configuration
InterRatPolicyCfgGroup.GeranGprsEdgeHoCfg
Network plan (negotiation not Select the SRVCC check box under this parameter.
required)
The following table describes the parameters that must be set in the StandardQci MO to configure a QCI-based inter-RAT handover policy group.
Table 7-21 Parameters for QCI 1
Parameter Name
Parameter ID
Data Source
Setting Notes
QoS Class Indication
StandardQci.Qci
Network plan (negotiation not
required)
Set this parameter as required, for example, set this parameter
to QCI1(QCI 1).
InterRAT policy config StandardQci.InterRatPolicyCfgGroupId Network plan (negotiation not
group ID
required)
Set this parameter to the value of the InterRAT policy config
group ID parameter in the InterRatPolicyCfgGroup MO
described in Table 7-20.
NOTE:
• For mandatory handovers, for example, coverage-based and UL-quality-based handovers, SRVCC can be triggered when SRVCC is configured in the interRAT handover policy groups for QCI 5 and QCI 1.
• For optional handovers, for example, load-based, service-based, and CSFB-based handovers, SRVCC can be triggered when SRVCC is configured in the
inter-RAT handover policy groups for all QCIs.
The following table describes the parameters that must be set to configure LCS-based SRVCC. If LCS is required when a UE is performing a service with QCI 1 in an
LTE network that supports IMS but does not support LCS, the UE needs to fall back to a CS domain to perform LCS.
Table 7-22 Parameters for LCS-based SRVCC
Parameter Name
Parameter ID
Data Source
Setting Notes
Handover Mode switch
ENodeBAlgoSwitch.HoModeSwitch
Network plan (negotiation not required)
Select the LcsSrvccSwitch check box.
GERAN LCS capability
CSFallBackBlindHoCfg.GeranLcsCap Network plan (negotiation not required)
Set this parameter to ON(On).
7.3.6 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-23 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the
summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the
initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
• The MOs in Table 7-23 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.
• Some MOs in Table 7-23 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.
Table 7-23 Parameters for SRVCC to GERAN
MO
Sheet in the Summary Data
File
Parameter Group
Remarks
GeranNfreqGroup
GeranNfreqGroup
Local cell identity, BCCH group identity,
GERAN version, Starting ARFCN, Band
indicator
The template RNPtemplate is recommended.
GeranNfreqGroupArfcn GeranNfreqGroupArfcn
Local cell identity, BCCH group identity,
GERAN ARFCN
The template RNPtemplate is recommended.
GeranExternalCell
Mobile country code, Mobile network code,
GERAN cell identity, Location area code,
Routing area code configure indicator,
Routing area code, Band indicator, GERAN
ARFCN, Network colour code, Base station
colour code, DTM indication
The template RNPtemplate is recommended.
GeranExternalCellPlmn GeranExternalCellPlmn
GERAN cell identity, Location area code,
Mobile country code, Mobile network code,
Share mobile country code, Share mobile
network code
The template RNPtemplate is recommended.
GeranNcell
GeranNcell
Local cell identity, Mobile country code,
Mobile network code, Location area code,
GERAN cell identity, Blind handover priority
The template RNPtemplate is recommended.
ENodeBAlgoSwitch
User-defined sheet
ENodeBAlgoSwitch is
recommended.
HoModeSwitch
A list-type sheet is recommended.
InterRatPolicyCfgGroupId, GeranGsmHoCfg,
GeranGprsEdgeHoCfg
A list-type sheet is recommended.
GeranExternalCell
InterRatPolicyCfgGroup User-defined sheet
InterRatPolicyCfgGroup is
recommended.
StandardQci
User-defined sheet
Qci, InterRatPolicyCfgGroupId
StandardQci is recommended.
A list-type sheet is recommended.
Using the CME to Perform Batch Configuration for Existing eNodeBs
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:
1. Choose CME > Advanced > Customize Summary Data File (M2000 client mode), or choose Advanced > Customize Summary Data File (CME client
mode), to customize a summary data file for batch reconfiguration.
NOTE:
For context-sensitive help on a current task in the client, press F1.
2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (M2000 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.
3. In the summary data file, set the parameters in the MOs listed in Table 7-23 and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (M2000 client mode), or choose LTE Application >
Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME.
5. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 7-8, select the eNodeB to which the MOs belong.
Figure 7-8 MO search and configuration window
3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (M2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
Using MML Commands
• Scenario 1: CS-only SRVCC to GERAN
1. Add neighboring GERAN frequencies and neighbor relationships with GERAN cells, and set parameters for inter-RAT measurements. For details about
parameter settings, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
2. Run the MOD ENODEBALGOSWITCH command with the GeranSrvccSwitch(GeranSrvccSwitch) check box selected under the Handover Mode switch
parameter.
3. Run the MOD INTERRATPOLICYCFGGROUP command with the InterRAT policy config group ID parameter set to 0 and with the SRVCC check box
selected under the GERAN GSM handover policy Configuration and GERAN GPRS EDGE handover policy Configuration parameters.
4. Run the MOD STANDARDQCI command with the InterRAT policy config group ID parameter set to 0 for QCI 1 and QCI 5.
5. Run the MOD GERANEXTERNALCELL command with the CS and PS handover indicator parameter set to BOOLEAN_FALSE(False).
• Scenario 2: CS-and-PS SRVCC to GERAN
1. Add neighboring GERAN frequencies and neighbor relationships with GERAN cells, and set parameters for inter-RAT measurements. For details about
parameter settings, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
2. Run the MOD ENODEBALGOSWITCH command with the GeranSrvccSwitch(GeranSrvccSwitch) and GeranPsHoSwitch(GeranPsHoSwitch) check
boxes selected under the Handover Mode switch parameter.
3. Run the MOD INTERRATPOLICYCFGGROUP command with the InterRAT policy config group ID parameter set to 0, with the SRVCC check box
selected under the GERAN GSM handover policy Configuration parameter, and with the SRVCC and PS_HO check boxes selected under the GERAN
GPRS EDGE handover policy Configuration parameter.
4. Run the MOD STANDARDQCI command with the InterRAT policy config group ID parameter set to 0 for QCI 1 and QCI 5.
5. Run the MOD GERANEXTERNALCELL command with the CS and PS handover indicator parameter set to BOOLEAN_TRUE(True).
• Scenario 3: LCS-based SRVCC to GERAN
1. Run the MOD ENODEBALGOSWITCH command with the LcsSrvccSwitch check box selected under the Handover Mode switch parameter.
2. Run the MOD CSFALLBACKBLINDHOCFG command with the GERAN LCS capability parameter set to ON(On).
MML Command Examples
• Scenario 1: CS-only SRVCC to GERAN
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranSrvccSwitch-1;
MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, GeranGsmHoCfg=SRVCC-1,GeranGprsEdgeHoCfg=SRVCC-1;
MOD STANDARDQCI: Qci=QCI1, InterRatPolicyCfgGroupId=0;
MOD STANDARDQCI: Qci=QCI5, InterRatPolicyCfgGroupId=0;
MOD GERANEXTERNALCELL: Mcc="460", Mnc="20", GeranCellId=15, Lac=12, RacCfgInd=NOT_CFG, BandIndicator=GSM_dcs1800,CsPsHOInd=BOOLEAN_FALSE;
• Scenario 2: CS-and-PS SRVCC to GERAN
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranPsHoSwitch-1&GeranSrvccSwitch-1;
MOD INTERRATPOLICYCFGGROUP: InterRatPolicyCfgGroupId=0, GeranGsmHoCfg=SRVCC-1,GeranGprsEdgeHoCfg=PS_HO-1&SRVCC-1;
MOD STANDARDQCI: Qci=QCI1, InterRatPolicyCfgGroupId=0;
MOD STANDARDQCI: Qci=QCI5, InterRatPolicyCfgGroupId=0;
MOD GERANEXTERNALCELL: Mcc="460", Mnc="20", GeranCellId=15, Lac=12, RacCfgInd=NOT_CFG, BandIndicator=GSM_dcs1800,CsPsHOInd=BOOLEAN_TRUE;
• Scenario 3: LCS-based SRVCC to GERAN
MOD ENODEBALGOSWITCH: HoModeSwitch=LcsSrvccSwitch-1;
MOD CSFALLBACKBLINDHOCFG: GeranLcsCap=ON;
7.3.7 Activation Observation
You can observe feature activation by tracing the signaling messages of a single UE and observing performance counters. Tracing the signaling messages of a single
UE for SRVCC to GERAN is the same as that for SRVCC to UTRAN. For details, see 7.1.7 Activation Observation.
Observe the counters described in Table 7-24. If the value of a counter is not 0, the related feature or function has been activated.
Table 7-24 Mapping between counters and features/functions
Feature/Function
Counter ID
Counter Name
SRVCC to GERAN
1526728403
L.IRATHO.SRVCC.E2G.PrepAttOut
Counter Description
Feature/Function
Counter ID
Counter Name
Counter Description
Number of inter-RAT handover attempts from E-UTRAN to
GERAN for SRVCC
7.3.8 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships,
for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in "Using the CME to Perform Batch
Configuration for Existing eNodeBs." In the procedure, modify parameters according to Table 7-25.
Table 7-25 Parameters for SRVCC to GERAN
MO
Sheet in the Summary Data File
Parameter Group
Remarks
ENodeBAlgoSwitch
User-defined sheet
ENodeBAlgoSwitch is recommended.
HoModeSwitch
Set GeranSrvccSwitch under the
HoModeSwitch parameter to 0.
Using the CME to Perform Single Configuration
On the CME, set parameters according to Table 7-25. For detailed instructions, see "Using the CME to Perform Single Configuration" described for feature activation.
Using MML Commands
Run the MOD ENODEBALGOSWITCH command with the GeranSrvccSwitch(GeranSrvccSwitch) check box cleared under the Handover Mode switch parameter.
MML Command Examples
MOD ENODEBALGOSWITCH: HoModeSwitch=GeranSrvccSwitch-0;
7.3.9 Performance Monitoring
Table 7-26 lists the performance counters for monitoring SRVCC to GERAN.
Table 7-26 Performance counters for monitoring SRVCC to GERAN
Counter ID
Counter Name
Description
1526728403
L.IRATHO.SRVCC.E2G.PrepAttOut
Number of inter-RAT handover attempts from E-UTRAN to GERAN for
SRVCC
1526728404
L.IRATHO.SRVCC.E2G.ExecAttOut
Number of inter-RAT handover executions from E-UTRAN to GERAN
for SRVCC
1526728405
L.IRATHO.SRVCC.E2G.ExecSuccOut
Number of successful inter-RAT handovers from E-UTRAN to GERAN
for SRVCC
Table 7-27 lists the performance counters for monitoring LCS-based SRVCC when UEs are running services with QCI 1.
Table 7-27 Performance counters for monitoring LCS-based SRVCC
Counter ID
Counter Name
Description
1526728409
L.CSFB.LCS.PrepAtt
Number of LCS-triggered CS fallback indicators received by the
eNodeB
1526728410
L.CSFB.LCS.PrepSucc
Number of responses sent from the eNodeB to MMEs for CSFB
triggered by LCS
1526728756
L.IRATHO.SRVCC.LCS.E2G.PrepAttOut
Number of CSFB-based handover attempts from E-UTRAN to
GERAN for SRVCC
1526728757
L.IRATHO.SRVCC.LCS.E2G.ExecAttOut
Number of CSFB-based handover executions from E-UTRAN to
GERAN for SRVCC
1526728758
L.IRATHO.SRVCC.LCS.E2G.ExecSuccOut
Number of successful CSFB-based handovers from E-UTRAN to
GERAN for SRVCC
Table 7-28 lists the performance counters for monitoring SRVCC triggered for emergency calls.
Table 7-28 Performance counters for monitoring SRVCC triggered for emergency calls
Counter ID
Counter Name
Description
1526729520
L.EMC.SRVCC.E2G.PrepAttOut
Number of handover attempts from E-UTRAN to GERAN for
SRVCC triggered for emergency calls
1526729521
L.EMC.SRVCC.E2G.ExecAttOut
Number of handover executions from E-UTRAN to GERAN for
SRVCC triggered for emergency calls
1526729522
L.EMC.SRVCC.E2G.ExecSuccOut
Number of successful handovers from E-UTRAN to GERAN for
SRVCC triggered for emergency calls
7.3.10 Parameter Optimization
In coverage- or service-based handovers for SRVCC, the measurement configuration contains handover thresholds for event B1 or B2. For details about how to optimize
these parameters, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.
In an LCS-based SRVCC procedure, the measurement configuration contains the threshold for event B1. For details about how to optimize the threshold, see the
parameter optimization section in CS Fallback Feature Parameter Description.
7.4 Troubleshooting
7.4.1 Fault 1
Fault Description
The performance monitoring results show that the SRVCC handover preparation success rate does not meet the operator requirement. The SRVCC handover
preparation success rate is calculated according to the following formula: SRVCC handover preparation success rate = Number of inter-RAT handover executions for
SRVCC/Number of inter-RAT handover attempts for SRVCC.
Fault Handling
If event-based counters (EBCs) are available, you can use EBCs to diagnose the fault as follows:
1. Obtain the measurement statistics of each handover preparation failures to locate the cause of the fault. For details about the EBCs, see eNodeB EBC
Reference.
2. Rectify the fault based on the cause.
If EBCs are not available, use performance counters to identify the cause of the fault. Counters for diagnosing faults in SRVCC to GERAN or TD-SCDMA networks are
similar to those for diagnosing faults in SRVCC to WCDMA networks. The following is the procedure for diagnosing faults in SRVCC to WCDMA networks:
1. Collect the statistics of the performance counters listed in the following table to identify the fault cause.
Counter ID
Counter Name
Description
1526730082
L.IRATHO.E2W.SRVCC.Prep.FailOut.MME
Number of SRVCC-based outgoing handover preparation failures
from E-UTRAN to WCDMA network because of the MME side
causes
1526730083
L.IRATHO.E2W.SRVCC.Prep.FailOut.PrepFailure
Number of SRVCC-based outgoing handover preparation failures
from E-UTRAN to WCDMA network because of the response of
handover preparation failure from WCDMA network
1526730084
L.IRATHO.E2W.SRVCC.Prep.FailOut.NoReply
Number of SRVCC-based outgoing handover preparation failures
from E-UTRAN to WCDMA network because of no response from
WCDMA network
2. Rectify the fault based on the cause.
7.4.2 Fault 2
Fault Description
The performance monitoring results show that the SRVCC handover success rate does not meet the operator requirement. The SRVCC handover success rate is
calculated according to the following formula: SRVCC handover success rate = (Number of successful inter-RAT handovers for SRVCC - Number of responses for
abnormal causes received by the eNodeB from the MME during inter-RAT handover executions for SRVCC)/Number of SRVCC-based outgoing handover executions for
ultra-flash CSFB.
Fault Handling
1. In the target system of handovers, check the counters related to incoming inter-RAT handovers to find out whether the UEs accessed the target system.
If the UEs accessed the target network, go to 2.
2. Check the counters related to failed inter-RAT handovers in the target system to identify whether the fault resides in the peer RAN or core network.
8 Parameters
Table 8-1 Parameters
MO
Parameter ID
MML Command
Feature
ID
Feature
Name
Description
ENodeBAlgoSwitch
HoModeSwitch
MOD ENODEBALGOSWITCH
LST ENODEBALGOSWITCH
LOFD001022 /
TDLOFD001022
LOFD001023 /
TDLOFD001023
LOFD001033 /
TDLOFD001033
LOFD001034 /
TDLOFD001034
LOFD001019 /
TDLOFD001019
LOFD001020 /
TDLOFD001020
LOFD001021 /
TDLOFD001021
TDLOFD001052
TDLOFD001088
TDLOFD001043
TDLOFD001072
TDLOFD001046
TDLOFD001073
SRVCC to
UTRAN
SRVCC to
GERAN
CS
Fallback to
UTRAN
CS
Fallback to
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
PS InterRAT
Mobility
between
E-UTRAN
and
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
CDMA2000
Flash CS
Fallback to
UTRAN
CS
Fallback
Steering to
UTRAN
Service
based
Inter-RAT
handover
to UTRAN
Distance
based
Inter-RAT
handover
to UTRAN
Meaning:
Indicates the switches corresponding to the inputs
based on which the eNodeB determines handover
policies.
EutranVoipCapSwitch: This switch will be removed in
later versions. In this version, the setting of this switch
is still synchronized between the M2000 and the
eNodeB, but it is no longer used internally. Therefore,
avoid using this switch.
UtranVoipCapSwitch: If this switch is turned on,
UTRAN supports VoIP. If this switch is turned off,
UTRAN does not support VoIP.
GeranVoipCapSwitch: If this switch is turned on,
GERAN supports VoIP. If this switch is turned off,
GERAN does not support VoIP.
Cdma1xRttVoipCapSwitch: If this switch is turned on,
CDMA2000 1xRTT supports VoIP. If this switch is
turned off, CDMA2000 1xRTT does not support VoIP.
UtranPsHoSwitch: If this switch is turned on, UTRAN
supports PS handovers. If this switch is turned off,
UTRAN does not support PS handovers.
GeranPsHoSwitch: If this switch is turned on, GERAN
supports PS handovers. If this switch is turned off,
GERAN does not support PS handovers.
CdmaHrpdNonOtpimisedHoSwitch: If this switch is
turned on, non-optimized handovers to CDMA2000
HRPD are enabled. If this switch is turned off, nonoptimized handovers to CDMA2000 HRPD are
disabled.
CdmaHrpdOptimisedHoSwitch: If this switch is turned
on, optimized handovers to CDMA2000 HRPD are
enabled. If this switch is turned off, optimized
handovers to CDMA2000 HRPD are disabled.
GeranNaccSwitch: This switch does not take effect if
GeranCcoSwitch is disabled. If this switch is turned on,
GERAN supports network assisted cell change
(NACC). If this switch is turned off, GERAN does not
support NACC.
GeranCcoSwitch: If this switch is turned on, GERAN
supports cell change order (CCO). If this switch is
turned off, GERAN does not support CCO.
UtranSrvccSwitch: If this switch is turned on, UTRAN
supports single radio voice call continuity (SRVCC). If
this switch is turned off, UTRAN does not support
SRVCC.
MO
Parameter ID
MML Command
Feature
ID
Feature
Name
Description
Service
based
Inter-RAT
handover
to GERAN
Distance
based
Inter-RAT
handover
to GERAN
GeranSrvccSwitch: If this switch is turned on, GERAN
supports SRVCC. If this switch is turned off, GERAN
does not support SRVCC.
Cdma1xRttSrvccSwitch: If this switch is turned on,
CDMA2000 1xRTT supports SRVCC. If this switch is
turned off, CDMA2000 1xRTT does not support
SRVCC.
UtranRedirectSwitch: If this switch is turned on,
redirection to UTRAN is enabled. If this switch is turned
off, redirection to UTRAN is disabled.
GeranRedirectSwitch: If this switch is turned on,
redirection to GERAN is enabled. If this switch is turned
off, redirection to GERAN is disabled.
CdmaHrpdRedirectSwitch: If this switch is turned on,
redirection to CDMA2000 HRPD is enabled. If this
switch is turned off, redirection to CDMA2000 HRPD is
disabled.
Cdma1xRttRedirectSwitch: If this switch is turned on,
redirection to CDMA2000 1xRTT is enabled. If this
switch is turned off, redirection to CDMA2000 1xRTT is
disabled.
BlindHoSwitch: If this switch is turned on, blind
handovers for CSFB are enabled. If this switch is
turned off, blind handovers for CSFB are disabled.
LcsSrvccSwitch: If this switch is turned on, an SRVCC
procedure is triggered when a UE receives a CSFB
instruction during a VoIP service. If this switch is turned
off, an SRVCC procedure is not triggered when a UE
receives a CSFB instruction during a VoIP service.
AutoGapSwitch: If this switch is turned on and UEs
support automatic measurement gap configurations on
the target frequency, the eNodeB does not deliver gap
configurations to UEs. If this switch is turned off, the
eNodeB delivers gap configurations to UEs during all
inter-frequency and inter-RAT measurements.
GUI Value Range: EutranVoipCapSwitch
(EutranVoipCapSwitch), UtranVoipCapSwitch
(UtranVoipCapSwitch), GeranVoipCapSwitch
(GeranVoipCapSwitch), Cdma1xRttVoipCapSwitch
(Cdma1xRttVoipCapSwitch), UtranPsHoSwitch
(UtranPsHoSwitch), GeranPsHoSwitch
(GeranPsHoSwitch),
CdmaHrpdNonOtpimisedHoSwitch
(CdmaHrpdNonOtpimisedHoSwitch),
CdmaHrpdOptimisedHoSwitch
(CdmaHrpdOptimisedHoSwitch), GeranNaccSwitch
(GeranNaccSwitch), GeranCcoSwitch
(GeranCcoSwitch), UtranSrvccSwitch
(UtranSrvccSwitch), GeranSrvccSwitch
(GeranSrvccSwitch), Cdma1xRttSrvccSwitch
(Cdma1xRttSrvccSwitch), UtranRedirectSwitch
(UtranRedirectSwitch), GeranRedirectSwitch
(GeranRedirectSwitch), CdmaHrpdRedirectSwitch
(CdmaHrpdRedirectSwitch), Cdma1xRttRedirectSwitch
(Cdma1xRttRedirectSwitch), BlindHoSwitch
(BlindHoSwitch), LcsSrvccSwitch(LcsSrvccSwitch),
AutoGapSwitch(AutoGapSwitch)
Unit: None
Actual Value Range: EutranVoipCapSwitch,
UtranVoipCapSwitch, GeranVoipCapSwitch,
Cdma1xRttVoipCapSwitch, UtranPsHoSwitch,
GeranPsHoSwitch, CdmaHrpdNonOtpimisedHoSwitch,
CdmaHrpdOptimisedHoSwitch, GeranNaccSwitch,
GeranCcoSwitch, UtranSrvccSwitch,
GeranSrvccSwitch, Cdma1xRttSrvccSwitch,
UtranRedirectSwitch, GeranRedirectSwitch,
CdmaHrpdRedirectSwitch, Cdma1xRttRedirectSwitch,
BlindHoSwitch, LcsSrvccSwitch, AutoGapSwitch
Default Value: EutranVoipCapSwitch:On,
UtranVoipCapSwitch:Off, GeranVoipCapSwitch:Off,
Cdma1xRttVoipCapSwitch:Off, UtranPsHoSwitch:Off,
GeranPsHoSwitch:Off,
CdmaHrpdNonOtpimisedHoSwitch:Off,
CdmaHrpdOptimisedHoSwitch:Off,
GeranNaccSwitch:Off, GeranCcoSwitch:Off,
UtranSrvccSwitch:Off, GeranSrvccSwitch:Off,
Cdma1xRttSrvccSwitch:Off, UtranRedirectSwitch:Off,
GeranRedirectSwitch:Off,
CdmaHrpdRedirectSwitch:Off,
Cdma1xRttRedirectSwitch:Off, BlindHoSwitch:Off,
LcsSrvccSwitch:Off, AutoGapSwitch:Off
CSFallBackBlindHoCfg UtranLcsCap
MOD
CSFALLBACKBLINDHOCFG
LST
CSFALLBACKBLINDHOCFG
LOFDCS
001033 / Fallback to
TDLOFD- UTRAN
001033
Meaning: Indicates the LCS capability of the UTRAN. If
this parameter is set to ON, the UTRAN supports LCS.
If this parameter is set to OFF, the UTRAN does not
support LCS.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
UtranExternalCell
ADD UTRANEXTERNALCELL
MOD UTRANEXTERNALCELL
LST UTRANEXTERNALCELL
LOFD001022 /
TDLOFD001022
LOFD001019 /
Meaning: Indicates whether the external UTRAN cell
supports single radio voice call continuity (SRVCC) for
both CS and PS services. If this parameter is set to
BOOLEAN_FALSE(False), the external UTRAN cell
does not support SRVCC for both CS and PS services.
CsPsHOInd
SRVCC to
UTRAN
PS InterRAT
Mobility
between
MO
Parameter ID
MML Command
Feature
ID
Feature
Name
Description
TDLOFD001019
TDLOFD001078
E-UTRAN
and
UTRAN
E-UTRAN
to UTRAN
CS/PS
steering
GUI Value Range: BOOLEAN_FALSE(False),
BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)
ENodeBAlgoSwitch
FreqLayerSwtich
MOD ENODEBALGOSWITCH
LST ENODEBALGOSWITCH
LOFD001087
LOFD001078 /
TDLOFD001078
TDLOFD001022
TDLOFD001033
TDLOFD001052
TDLOFD001088
SRVCC
Flexible
Steering to
UTRAN
E-UTRAN
to UTRAN
CS/PS
Steering
SRVCC to
UTRAN
CS
Fallback to
UTRAN
Flash CS
Fallback to
UTRAN
CS
Fallback
Steering to
UTRAN
Meaning: This parameter includes the following three
switches: UtranFreqLayerMeasSwitch,
UtranFreqLayerBlindSwitch, and UtranSrvccSwitch.
UtranSrvccSwitch takes effect only when
UtranFreqLayerMeasSwitch is turned on. If
UtranFreqLayerMeasSwitch is turned on, the UTRAN
hierarchy-based measurement algorithm takes effect
for measurements related to coverage-based and
CSFB-triggered handovers from EUTRAN to UTRAN. If
UtranFreqLayerBlindSwitch is turned on, the UTRAN
hierarchy-based blind-handover algorithm takes effect
for coverage-based and CSFB-triggered blind
handovers from EUTRAN to UTRAN. If
UtranSrvccSwitch is turned on, the UTRAN SRVCC
hierarchy-based measurement algorithm takes effect
for SRVCC-triggered handovers from EUTRAN to
UTRAN.
GUI Value Range: UtranFreqLayerMeasSwitch
(UtranFreqLayerMeasSwitch),
UtranFreqLayerBlindSwitch
(UtranFreqLayerBlindSwitch),
UtranSrvccSteeringSwitch(UtranSrvccSteeringSwitch)
Unit: None
Actual Value Range: UtranFreqLayerMeasSwitch,
UtranFreqLayerBlindSwitch, UtranSrvccSteeringSwitch
Default Value: UtranFreqLayerMeasSwitch:Off,
UtranFreqLayerBlindSwitch:Off,
UtranSrvccSteeringSwitch:Off
UtranNFreq
CsPriority
ADD UTRANNFREQ
MOD UTRANNFREQ
LST UTRANNFREQ
LOFD001078 /
TDLOFD001078
TDLOFD001033
TDLOFD001052
TDLOFD001088
E-UTRAN
to UTRAN
CS/PS
Steering
CS
Fallback to
UTRAN
Flash CS
Fallback to
UTRAN
CS
Fallback
Steering to
UTRAN
Meaning: Indicates the priority for a neighboring
UTRAN frequency to carry CS services. In coveragebased inter-RAT SRVCC or CSFB to UTRAN, if
UtranFreqLayerMeasSwitch is turned on, the eNodeB
determines the UTRAN frequency to be delivered to a
UE based on CS service priorities. The eNodeB
delivers the UTRAN frequency with the highest CS
priority to the UE by default.In blind handovers for
CSFB to UTRAN, if UtranFreqLayerBlindSwitch is
turned on, the target cell for a blind handover is
selected based on CS service priorities. The cell on the
UTRAN frequency with the highest CS priority is
selected by default.When this parameter is set to
Priority_0 for a UTRAN frequency, the UTRAN
frequency is not included in CS service priority
arrangement.
GUI Value Range: Priority_0(Priority 0), Priority_1
(Priority 1), Priority_2(Priority 2), Priority_3(Priority 3),
Priority_4(Priority 4), Priority_5(Priority 5), Priority_6
(Priority 6), Priority_7(Priority 7), Priority_8(Priority 8),
Priority_9(Priority 9), Priority_10(Priority 10),
Priority_11(Priority 11), Priority_12(Priority 12),
Priority_13(Priority 13), Priority_14(Priority 14),
Priority_15(Priority 15), Priority_16(Priority 16)
Unit: None
Actual Value Range: Priority_0, Priority_1, Priority_2,
Priority_3, Priority_4, Priority_5, Priority_6, Priority_7,
Priority_8, Priority_9, Priority_10, Priority_11,
Priority_12, Priority_13, Priority_14, Priority_15,
Priority_16
Default Value: Priority_2(Priority 2)
ADD
INTERRATPOLICYCFGGROUP
MOD
INTERRATPOLICYCFGGROUP
LST
INTERRATPOLICYCFGGROUP
LOFD001022 /
TDLOFD001022
LOFD001019 /
TDLOFD001019
SRVCC to
UTRAN
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
Meaning:
Indicates the policy of handovers to UTRAN.
PS_HO: indicates whether to allow PS handovers to
UTRAN.
SRVCC: indicates whether to allow transfers to UTRAN
in SRVCC mode.
REDIRECTION: indicates whether to allow redirection
to UTRAN.
GUI Value Range: PS_HO, SRVCC, REDIRECTION
Unit: None
Actual Value Range: PS_HO, SRVCC, REDIRECTION
Default Value: PS_HO:On, SRVCC:Off,
REDIRECTION:Off
InterRatPolicyCfgGroup InterRatPolicyCfgGroupId ADD
INTERRATPOLICYCFGGROUP
LST
INTERRATPOLICYCFGGROUP
MOD
INTERRATPOLICYCFGGROUP
RMV
INTERRATPOLICYCFGGROUP
LOFD001022 /
TDLOFD001022
LOFD001023 /
TDLOFD001023
LOFD001019 /
TDLOFD001019
SRVCC to
UTRAN
SRVCC to
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
PS InterRAT
Meaning: Indicates the group ID of the parameters
related to the inter-RAT handover with a specific QCI.
GUI Value Range: 0~39
Unit: None
Actual Value Range: 0~39
Default Value: None
InterRatPolicyCfgGroup UtranHoCfg
MO
Parameter ID
MML Command
Feature
ID
Feature
Name
LOFD001020 /
TDLOFD001020
LOFD001021 /
TDLOFD001021
Mobility
between
E-UTRAN
and
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
CDMA2000
Description
StandardQci
InterRatPolicyCfgGroupId MOD STANDARDQCI
LST STANDARDQCI
LOFD001019 /
TDLOFD001019
LOFD001020 /
TDLOFD001020
LOFD001021 /
TDLOFD001021
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
PS InterRAT
Mobility
between
E-UTRAN
and
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
CDMA2000
Meaning: Indicates the ID of a parameter group related
to inter-RAT handover.
GUI Value Range: 0~39
Unit: None
Actual Value Range: 0~39
Default Value: 0
ExtendedQci
InterRatPolicyCfgGroupId ADD EXTENDEDQCI
MOD EXTENDEDQCI
LST EXTENDEDQCI
LOFD001019 /
TDLOFD001019
LOFD001020 /
TDLOFD001020
LOFD001021 /
TDLOFD001021
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
PS InterRAT
Mobility
between
E-UTRAN
and
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
CDMA2000
Meaning: Indicates the group ID of the parameters
related to the inter-RAT handover with the extended
QCI.
GUI Value Range: 0~39
Unit: None
Actual Value Range: 0~39
Default Value: 0
InterRatPolicyCfgGroup GeranGsmHoCfg
ADD
INTERRATPOLICYCFGGROUP
MOD
INTERRATPOLICYCFGGROUP
LST
INTERRATPOLICYCFGGROUP
LOFD001023 /
TDLOFD001023
LOFD001020 /
TDLOFD001020
SRVCC to
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
GERAN
Meaning:
Indicates the switch used to enable or disable the
single radio voice call continuity (SRVCC) handover to
GERAN GSM.
If this switch is set to On, the UE can perform the
SRVCC handover to the GERAN GSM cell.
If this switch is set to Off, the UE cannot perform the
SRVCC handover to the GERAN GSM cell.
GUI Value Range: SRVCC
Unit: None
Actual Value Range: SRVCC
Default Value: SRVCC:On
InterRatPolicyCfgGroup GeranGprsEdgeHoCfg
ADD
INTERRATPOLICYCFGGROUP
MOD
INTERRATPOLICYCFGGROUP
LST
INTERRATPOLICYCFGGROUP
TDLOFD001023
LOFD001020 /
TDLOFD001020
SRVCC to
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
GERAN
Meaning: Indicates the policy of handovers to
GPRS/EDGE. PS_HO: Indicates whether PS
handovers to neighboring GPRS/EDGE cells are
allowed. NACC_HO: Indicates whether NACC
handovers to neighboring GPRS/EDGE cells are
allowed. This switch will be removed in the later
versions. In this version, the setting of this switch is still
synchronized between the M2000 and the eNodeB, but
it is no longer used internally. Therefore, avoid using
this parameter. CCO_HO: Indicates whether CCO
handovers to neighboring GPRS/EDGE cells are
allowed. SRVCC: Indicates whether SRVCC handovers
to neighboring GPRS/EDGE cells are allowed.
REDIRECTION: Indicates whether redirections to
neighboring GPRS/EDGE cells are allowed.
GUI Value Range: PS_HO, NACC_HO, CCO_HO,
SRVCC, REDIRECTION
Unit: None
Actual Value Range: PS_HO, NACC_HO, CCO_HO,
SRVCC, REDIRECTION
Default Value: PS_HO:On, NACC_HO:Off,
CCO_HO:Off, SRVCC:Off, REDIRECTION:Off
UtranExternalCell
ADD UTRANEXTERNALCELL
MOD UTRANEXTERNALCELL
LST UTRANEXTERNALCELL
LOFD001019 /
TDLOFD001019
PS InterRAT
Mobility
between
Meaning: Indicates the routing area code.
GUI Value Range: 0~255
Unit: None
Rac
MO
Parameter ID
MML Command
Feature
ID
Feature
Name
Description
LOFD001034 /
TDLOFD001034
LOFD001052 /
TDLOFD001052
TDLOFD001033
TDLOFD001043
TDLOFD001072
TDLOFD001078
E-UTRAN
and
UTRAN
CS
Fallback to
GERAN
Flash CS
Fallback to
UTRAN
CS
Fallback to
UTRAN
Service
based
Inter-RAT
handover
to UTRAN
Distance
based
Inter-RAT
handover
to UTRAN
E-UTRAN
to UTRAN
CS/PS
steering
Actual Value Range: 0~255
Default Value: 0
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
SRVCC to
UTRAN
CS
Fallback to
UTRAN
Flash CS
Fallback to
UTRAN
PS InterRAT
Mobility
between
E-UTRAN
and
UTRAN
Service
based
Inter-RAT
handover
to UTRAN
Distance
based
Inter-RAT
handover
to UTRAN
E-UTRAN
to UTRAN
CS/PS
steering
Meaning: Indicates the priority of the neighboring cell
during blind handovers. Blind handover is a process in
which the eNodeB instructs a UE to hand over to a
specified neighboring cell. There are 32 priorities
altogether. The priority has a positive correlation with
the value of this parameter. Note that the value 0
indicates that blind handovers to the neighboring cell
are not allowed.
GUI Value Range: 0~32
Unit: None
Actual Value Range: 0~32
Default Value: 0
UtranNCell
BlindHoPriority
ADD UTRANNCELL
MOD UTRANNCELL
LST UTRANNCELL
LOFD001019
TDLOFD001022
TDLOFD001033
TDLOFD001052
TDLOFD001019
TDLOFD001043
TDLOFD001072
TDLOFD001078
StandardQci
Qci
LST STANDARDQCI
MOD STANDARDQCI
LOFDDynamic
00101502 Scheduling
/
TDLOFD00101502
Meaning: Indicates the QoS Class Identifier (QCI) of an
EPS bearer. Different QCIs represent different QoS
specifications such as the packet delay budget, packet
error loss rate, and resource type (whether the service
is a GBR service or not). For details, see Table 6.1.7 in
3GPP TS 23.203.
GUI Value Range: QCI1(QCI 1), QCI2(QCI 2), QCI3
(QCI 3), QCI4(QCI 4), QCI5(QCI 5), QCI6(QCI 6),
QCI7(QCI 7), QCI8(QCI 8), QCI9(QCI 9)
Unit: None
Actual Value Range: QCI1, QCI2, QCI3, QCI4, QCI5,
QCI6, QCI7, QCI8, QCI9
Default Value: None
GeranExternalCell
Rac
ADD GERANEXTERNALCELL
MOD GERANEXTERNALCELL
LST GERANEXTERNALCELL
LOFD001034 /
LOFD001034
LOFD001053
LOFD001020 /
TDLOFD001020
CS
Fallback to
GERAN
Flash CS
Fallback to
GERAN
PS InterRAT
Mobility
between
E-UTRAN
and
GERAN
Meaning: Indicates the routing area code.
GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: 0
GeranNcell
BlindHoPriority
ADD GERANNCELL
MOD GERANNCELL
LST GERANNCELL
LOFD001020 /
TDLOFD001020
PS InterRAT
Mobility
between
Meaning: Indicates the priority of the neighboring cell
during blind handovers. Blind handover is a process in
which the eNodeB instructs a UE to hand over to a
specified neighboring cell. There are 32 priorities
MO
Parameter ID
CSFallBackBlindHoCfg GeranLcsCap
MML Command
MOD
CSFALLBACKBLINDHOCFG
LST
CSFALLBACKBLINDHOCFG
Feature
ID
Feature
Name
Description
TDLOFD001023
TDLOFD001034
TDLOFD001053
E-UTRAN
and
GERAN
SRVCC to
GERAN
CS
Fallback to
GERAN
Flash CS
Fallback to
GERAN
altogether. The priority has a positive correlation with
the value of this parameter. Note that the value 0
indicates that blind handovers to the neighboring cell
are not allowed.
GUI Value Range: 0~32
Unit: None
Actual Value Range: 0~32
Default Value: 0
LOFDCS
001034 / Fallback to
TDLOFD- GERAN
001034
Meaning: Indicates the LCS capability of the GERAN. If
this parameter is set to ON, the GERAN supports LCS.
If this parameter is set to OFF, the GERAN does not
support LCS.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
9 Counters
Table 9-1 Counters
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526726989
L.IRATHO.E2W.PrepAttOut
Number of inter-RAT
handover attempts from
E-UTRAN to WCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526726990
L.IRATHO.E2W.ExecAttOut
Number of inter-RAT
handover executions from
E-UTRAN to WCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526726991
L.IRATHO.E2W.ExecSuccOut
Number of successful interRAT handovers from
E-UTRAN to WCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526726992
L.IRATHO.E2G.PrepAttOut
Number of inter-RAT
handover attempts from
E-UTRAN to GERAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
1526726993
L.IRATHO.E2G.ExecAttOut
Number of inter-RAT
handover executions from
E-UTRAN to GERAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
1526726994
L.IRATHO.E2G.ExecSuccOut
Number of successful interRAT handovers from
E-UTRAN to GERAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526727034
Handover from E-UTRAN to WCDMA
Success Rate
Success rate of inter-RAT
handovers from E-UTRAN
to WCDMA network
The counter will be deleted
in later versions. It is
reported normally in the
current version but the
measurement value is
invalid. You are advised not
to use this counter.
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526727035
Handover from E-UTRAN to GERAN Success Success rate of inter-RAT
Rate
handovers from E-UTRAN
to GERAN
The counter will be deleted
in later versions. It is
reported normally in the
current version but the
measurement value is
invalid. You are advised not
to use this counter.
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
TDLOFD-001020
TDLOFD-001023
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
1526727226
L.IRATHO.E2T.PrepAttOut
Number of inter-RAT
Handover Attempts from
E-UTRAN to TD-SCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
TDLOFD-001019
TDLOFD-001022
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
1526727227
L.IRATHO.E2T.ExecAttOut
Number of inter-RAT
handover executions from
E-UTRAN to TD-SCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
TDLOFD-001019
TDLOFD-001022
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
1526727228
L.IRATHO.E2T.ExecSuccOut
Number of successful interRAT handovers from
E-UTRAN to TD-SCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
TDLOFD-001019
TDLOFD-001022
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
1526728312
L.IRATHO.BlindHO.E2W.ExecAttOut
Number of inter-RAT blind
handovers executions from
E-UTRAN to WCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728313
L.IRATHO.BlindHO.E2W.ExecSuccOut
Number of successful interRAT blind handovers from
E-UTRAN to WCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728314
L.IRATHO.BlindHO.E2G.ExecAttOut
Number of inter-RAT blind
handovers executions from
E-UTRAN to GERAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
1526728315
L.IRATHO.BlindHO.E2G.ExecSuccOut
Number of successful interRAT blind handovers from
E-UTRAN to GERAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
1526728377
L.IRATHO.E2W.PrepAttOut.PLMN
Number of inter-RAT
handover attempts from
Multi-mode: None
GSM: None
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
E-UTRAN to WCDMA
network for a specific
operator
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728378
L.IRATHO.E2W.ExecAttOut.PLMN
Number of inter-RAT
handover executions from
E-UTRAN to WCDMA
network for a specific
operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728379
L.IRATHO.E2W.ExecSuccOut.PLMN
Number of successful interRAT handovers from
E-UTRAN to WCDMA
network for a specific
operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728380
L.IRATHO.E2G.PrepAttOut.PLMN
Number of inter-RAT
handover attempts from
E-UTRAN to GERAN for a
specific operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728381
L.IRATHO.E2G.ExecAttOut.PLMN
Number of inter-RAT
handover executions from
E-UTRAN to GERAN for a
specific operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
RAN Sharing with Dedicated
Carrier
1526728382
L.IRATHO.E2G.ExecSuccOut.PLMN
Number of successful interRAT handovers from
E-UTRAN to GERAN for a
specific operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728389
L.IRATHO.BlindHO.E2W.PrepAttOut.PLMN
Number of inter-RAT blind
handover attempts from
E-UTRAN to WCDMA
network for a specific
operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728390
L.IRATHO.BlindHO.E2G.PrepAttOut.PLMN
Number of inter-RAT blind
handover attempts from
E-UTRAN to GERAN for a
specific operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728391
L.IRATHO.BlindHO.E2W.ExecAttOut.PLMN
Number of inter-RAT blind
handover executions from
E-UTRAN to WCDMA
network for a specific
operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728392
L.IRATHO.BlindHO.E2W.ExecSuccOut.PLMN Number of successful interRAT blind handover
executions from E-UTRAN
to WCDMA network for a
specific operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728393
L.IRATHO.BlindHO.E2G.ExecAttOut.PLMN
1526728394
Number of inter-RAT blind
handover executions from
E-UTRAN to GERAN for a
specific operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
L.IRATHO.BlindHO.E2G.ExecSuccOut.PLMN Number of successful interRAT blind handover
executions from E-UTRAN
to GERAN for a specific
operator
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
LOFD-001034
TDLOFD-001020
TDLOFD-001023
TDLOFD-001034
LOFD-001036
LOFD-001037
TDLOFD-001036
TDLOFD-001037
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
CS Fallback to GERAN
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
RAN Sharing with Common
Carrier
RAN Sharing with Dedicated
Carrier
1526728400
L.IRATHO.SRVCC.E2W.PrepAttOut
Number of inter-RAT
handover attempts from
E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728401
L.IRATHO.SRVCC.E2W.ExecAttOut
Number of inter-RAT
handover executions from
E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728402
L.IRATHO.SRVCC.E2W.ExecSuccOut
Number of successful interRAT handovers from
E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728403
L.IRATHO.SRVCC.E2G.PrepAttOut
Number of inter-RAT
handover attempts from
E-UTRAN to GERAN for
SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1526728404
L.IRATHO.SRVCC.E2G.ExecAttOut
Number of inter-RAT
handover executions from
E-UTRAN to GERAN for
SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1526728405
L.IRATHO.SRVCC.E2G.ExecSuccOut
Number of successful interRAT handovers from
E-UTRAN to GERAN for
SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1526728406
L.IRATHO.SRVCC.E2T.PrepAttOut
Number of inter-RAT
handover attempts from
E-UTRAN to TD-SCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728407
L.IRATHO.SRVCC.E2T.ExecAttOut
Number of inter-RAT
Multi-mode: None
handover executions from
GSM: None
E-UTRAN to TD-SCDMA for UMTS: None
SRVCC
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728408
L.IRATHO.SRVCC.E2T.ExecSuccOut
Multi-mode: None
SRVCC to UTRAN
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
Number of successful inter- GSM: None
RAT handovers from
UMTS: None
E-UTRAN to TD-SCDMA for LTE: LOFD-001022
SRVCC
TDLOFD-001022
SRVCC to UTRAN
1526728409
L.CSFB.LCS.PrepAtt
Number of LCS-triggered
CS fallback indicators
received by the eNodeB
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
LOFD-001023
TDLOFD-001023
SRVCC to UTRAN
SRVCC to UTRAN
SRVCC to GERAN
SRVCC to GERAN
1526728410
L.CSFB.LCS.PrepSucc
Number of responses sent
from the eNodeB to MMEs
for CSFB triggered by LCS
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
LOFD-001023
TDLOFD-001023
SRVCC to UTRAN
SRVCC to UTRAN
SRVCC to GERAN
SRVCC to GERAN
1526728560
L.IRATHO.E2W.NoData.ExecAttOut
Number of inter-RAT
handover executions from
E-UTRAN to WCDMA
network triggered for UEs
that do not transmit or
receive data
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001105
TDLOFD-001105
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
Dynamic DRX
Dynamic DRX
1526728561
L.IRATHO.E2W.NoData.ExecSuccOut
Number of successful interRAT handovers from
E-UTRAN to WCDMA
network triggered for UEs
that do not transmit or
receive data
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
LOFD-001105
TDLOFD-001105
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
Dynamic DRX
Dynamic DRX
1526728747
L.IRATHO.BlindHO.E2T.ExecAttOut
Number of inter-RAT blind
handover executions from
E-UTRAN to TD-SCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728748
L.IRATHO.BlindHO.E2T.ExecSuccOut
Number of successful interRAT blind handovers from
E-UTRAN to TD-SCDMA
network
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728753
L.IRATHO.SRVCC.LCS.E2W.PrepAttOut
Number of CSFB-based
handover attempts from
E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728754
L.IRATHO.SRVCC.LCS.E2W.ExecAttOut
Number of CSFB-based
handover executions from
E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728755
L.IRATHO.SRVCC.LCS.E2W.ExecSuccOut
Number of successful
CSFB-based handovers
from E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728756
L.IRATHO.SRVCC.LCS.E2G.PrepAttOut
Number of CSFB-based
handover attempts from
E-UTRAN to GERAN for
SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
1526728757
L.IRATHO.SRVCC.LCS.E2G.ExecAttOut
Number of CSFB-based
handover executions from
E-UTRAN to GERAN for
SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1526728758
L.IRATHO.SRVCC.LCS.E2G.ExecSuccOut
Number of successful
CSFB-based handovers
from E-UTRAN to GERAN
for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1526728759
L.IRATHO.SRVCC.LCS.E2T.PrepAttOut
Number of CSFB-based
handover attempts from
E-UTRAN to TD-SCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728760
L.IRATHO.SRVCC.LCS.E2T.ExecAttOut
Number of CSFB-based
Multi-mode: None
handover executions from
GSM: None
E-UTRAN to TD-SCDMA for UMTS: None
SRVCC
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728761
L.IRATHO.SRVCC.LCS.E2T.ExecSuccOut
Number of successful
Multi-mode: None
CSFB-based handovers
GSM: None
from E-UTRAN to TDUMTS: None
SCDMA network for SRVCC
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728866
L.IRATHO.G2E.PrepAttIn
Number of inter-RAT
handover attempts from
GERAN to E-UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
TDLOFD-001020
TDLOFD-001023
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
1526728867
L.IRATHO.G2E.PrepInSucc
Number of successful interRAT handover preparations
from GERAN to E-UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
TDLOFD-001020
TDLOFD-001023
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
1526728868
L.IRATHO.G2E.ExecSuccIn
Number of successful interRAT handovers from
GERAN to E-UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
TDLOFD-001020
TDLOFD-001023
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
1526728869
L.IRATHO.G2E.PrepInFail.TgtNotAllow
Number of inter-RAT
handover preparation
failures from GERAN in the
target cell due to Handover
Target not allowed
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001020
LOFD-001023
TDLOFD-001020
TDLOFD-001023
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
PS Inter-RAT Mobility
between E-UTRAN and
GERAN
SRVCC to GERAN
1526728870
L.IRATHO.T2E.PrepAttIn
Number of inter-RAT
Multi-mode: None
handover attempts from TD- GSM: None
SCDMA network to
UMTS: None
E-UTRAN
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728871
L.IRATHO.T2E.PrepInSucc
Number of successful inter- Multi-mode: None
RAT handover preparations GSM: None
from TD-SCDMA network to UMTS: None
E-UTRAN
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728872
L.IRATHO.T2E.ExecSuccIn
Number of successful interRAT handovers from TDSCDMA network to
E-UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
Counter ID
Counter Name
Counter Description
Feature ID
Feature Name
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728873
L.IRATHO.T2E.PrepInFail.TgtNotAllow
Number of inter-RAT
handover preparation
failures from TD-SCDMA
network with the cause of
"Handover Target not
allowed" in the target cell
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728874
L.IRATHO.W2E.PrepAttIn
Number of inter-RAT
handover attempts from
WCDMA network to
E-UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728875
L.IRATHO.W2E.PrepInSucc
Number of successful interRAT handover preparations
from WCDMA network to
E-UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728876
L.IRATHO.W2E.ExecSuccIn
Number of successful interRAT handovers from
WCDMA network to
E-UTRAN
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728877
L.IRATHO.W2E.PrepInFail.TgtNotAllow
Number of inter-RAT
handover preparation
failures from WCDMA
network in the target cell
due to Handover Target not
allowed
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001019
LOFD-001022
LOFD-001033
TDLOFD-001019
TDLOFD-001022
TDLOFD-001033
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
SRVCC to UTRAN
CS Fallback to UTRAN
1526728894
L.IRATHO.SRVCC.E2W.MMEAbnormRsp
Number of responses for
abnormal causes received
by the eNodeB from the
MME during inter-RAT
handover executions from
E-UTRAN to WCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
1526728895
L.IRATHO.SRVCC.E2G.MMEAbnormRsp
Number of responses for
abnormal causes received
by the eNodeB from the
MME during inter-RAT
handover executions from
E-UTRAN to GERAN for
SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001023
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1526728896
L.IRATHO.SRVCC.E2T.MMEAbnormRsp
Number of responses for
abnormal causes received
by the eNodeB from the
MME during inter-RAT
handover executions from
E-UTRAN to TD-SCDMA
network for SRVCC
Multi-mode: None
GSM: None
UMTS: None
LTE: LOFD-001022
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
11 Reference Documents
1. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC)"
2. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"
3. 3GPP TS 25.913, "Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)"
4. CS Fallback Feature Parameter Description
5. Inter-RAT Mobility Management in Connected Mode Feature Parameter Description
6. MLB Feature Parameter Description
7. Flexible User Steering Feature Parameter Description