Cs fall back

eRAN

CS Fallback Feature Parameter Description

Issue 02

Date 2015-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. 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: [email protected]

Contents1 About This Document

1.1 Scope

1.2 Intended Audience

1.3 Change History

1.4 Differences Between eNodeB Types

2 Overview

2.1 Overview

2.2 Benefits

2.3 Architecture

3 CSFB to UTRAN

3.1 Basic CSFB to UTRAN

3.1.1 Handover Measurement

3.1.2 Blind Handover

3.2 Flash CSFB to UTRAN

3.3 Ultra-Flash CSFB to UTRAN

3.4 CS Fallback with LAI to UTRAN

3.5 E-UTRAN to UTRAN CS Steering

3.6 CS Fallback Steering to UTRAN

3.7 Load-based CSFB to UTRAN

3.8 Handover Decision

3.8.1 Basic Handover Decision

3.8.2 Flash Redirection Decision

3.9 Handover Execution

3.9.1 Handover Policy Selection

3.9.2 Ultra-Flash CSFB to UTRAN

3.9.3 Redirection-based CSFB Optimization for UEs in Idle Mode

3.9.4 CSFB Admission Optimization for UEs in Idle Mode

3.10 RIM Procedure Between E-UTRAN and UTRAN

3.10.1 RIM Procedure Through the Core Network

3.10.2 RIM Procedure Through the eCoordinator

3.11 CSFB to UTRAN

3.11.1 Combined EPS/IMSI Attach Procedure

3.11.2 CSFB Based on PS Handover

3.11.3 Signaling procedure of redirection to CDMA2000 1xRTT

3.11.4 Flash CSFB



3.11.7 CSFB for SMS

3.11.8 Emergency Call

3.11.9 CSFB for LCS

4 CSFB to GERAN

4.1 Basic CSFB to GERAN

4.2 Flash CSFB to GERAN

4.3 CS Fallback with LAI to GERAN

4.4 CS Fallback Steering to GERAN

4.5 Ultra-Flash CSFB to GERAN



4.8 RIM Procedure Between E-UTRAN and GERAN

4.9 CSFB to GERAN



4.9.3 CSFB Based on CCO/NACC

4.9.4 CSFB Based on Redirection

4.9.5 Flash CSFB

4.9.6 Ultra-Flash CSFB to GERAN

4.9.7 CSFB for SMS


4.9.9 CSFB for LCS

5 Related Features

5.1 Features Related to LOFD-001033 CS Fallback to UTRAN

5.2 Features Related to LOFD-001052 Flash CS Fallback to UTRAN

5.3 Features Related to LOFD-070202 Ultra-Flash CSFB to UTRAN

5.4 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN

5.5 Features Related to LOFD-001088 CS Fallback Steering to UTRAN

5.6 Features Related to LOFD-001078 E-UTRAN to UTRAN CS/PS Steering

5.7 Features Related to LOFD-001034 CS Fallback to GERAN

5.8 Features Related to LOFD-001053 Flash CS Fallback to GERAN

5.9 Feature Related to LOFD-081283 Ultra-Flash CSFB to GERAN

5.10 Features Related to LOFD-001069 CS Fallback with LAI to GERAN

5.11 Features Related to LOFD-001089 CS Fallback Steering to GERAN

6 Network Impact

6.1 LOFD-001033 CS Fallback to UTRAN

6.2 LOFD-001052 Flash CS Fallback to UTRAN

6.3 LOFD-070202 Ultra-Flash CSFB to UTRAN

6.4 LOFD-001068 CS Fallback with LAI to UTRAN

6.5 LOFD-001088 CS Fallback Steering to UTRAN

6.6 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering

6.7 LOFD-001034 CS Fallback to GERAN

6.8 LOFD-001053 Flash CS Fallback to GERAN

6.9 LOFD-081283 Ultra-Flash CSFB to GERAN

6.10 LOFD-001069 CS Fallback with LAI to GERAN

6.11 LOFD-001089 CS Fallback Steering to GERAN

7 Engineering Guidelines

7.1 LOFD-001033 CS Fallback to UTRAN

7.1.1 When to Use CS Fallback to UTRAN

7.1.2 Required Information

7.1.3 Requirements

7.1.4 Precautions

7.1.5 Data Preparation and Feature Activation

7.1.5.1 Data Preparation

7.1.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

7.1.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs

7.1.5.4 Using the CME to Perform Single Configuration

7.1.5.5 Using MML Commands

7.1.6 Activation Observation

7.1.7 Deactivation

7.1.8 Performance Monitoring

7.1.9 Parameter Optimization

7.2 RIM Procedure from E-UTRAN to UTRAN

7.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN


7.2.3 Requirements

7.2.4 Precautions








7.2.7 Deactivation




7.3.1 When to Use Flash CS Fallback to UTRAN


7.3.3 Requirements

7.3.4 Precautions








7.3.7 Deactivation




7.4.1 When to Use Ultra-Flash CSFB


7.4.3 Requirements

7.4.4 Precautions








7.4.7 Deactivation




7.5.1 When to Use CS Fallback with LAI to UTRAN


7.5.3 Requirements

7.5.4 Precautions








7.5.7 Deactivation




7.6.1 When to Use CS Fallback Steering to UTRAN


7.6.3 Requirements

7.6.4 Precautions








7.6.7 Deactivation




7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering


7.7.3 Requirements

7.7.4 Precautions








7.7.7 Deactivation




7.8.1 When to Use CS Fallback to GERAN


7.8.3 Requirements

7.8.4 Precautions






7.8.5.5 Using Feature Operation and Maintenance on the CME



7.8.7 Deactivation



7.9 RIM Procedure from E-UTRAN to GERAN

7.9.1 When to Use RIM Procedure Between E-UTRAN and GERAN


7.9.3 Requirements

7.9.4 Precautions








7.9.7 Deactivation




7.10.1 When to Use Flash CS Fallback to GERAN


7.10.3 Requirements

7.10.4 Precautions








7.10.7 Deactivation




7.11.1 When to Use This Feature


7.11.3 Requirements

7.11.4 Precautions








7.11.7 Deactivation




7.12.1 When to Use CS Fallback with LAI to GERAN


7.12.3 Requirements

7.12.4 Precautions








7.12.7 Deactivation




7.13.1 When to Use CS Fallback Steering to GERAN


7.13.3 Requirements

7.13.4 Precautions








7.13.7 Deactivation



7.14 Troubleshooting

7.14.1 CSFB Calling Procedure Failure

7.14.2 eNodeB Receiving No Measurement Report

7.14.3 CSFB Blind Handover Failure

7.14.4 CSFB Handover Failure

8 Parameters

9 Counters

10 Glossary

11 Reference Documents

1 About This Document1.1 ScopeThis document describes circuit switched fallback (CSFB), including its technical principles, related features, network impact, and engineering guidelines.

This document covers the following features:

LOFD-001033 CS Fallback to UTRAN LOFD-001052 Flash CS Fallback to UTRAN LOFD-070202 Ultra-Flash CSFB to UTRAN LOFD-001068 CS Fallback with LAI to UTRAN LOFD-001088 CS Fallback Steering to UTRAN LOFD-001078 E-UTRAN to UTRAN CS/PS Steering LOFD-001034 CS Fallback to GERAN LOFD-001053 Flash CS Fallback to GERAN LOFD-001069 CS Fallback with LAI to GERAN LOFD-001089 CS Fallback Steering to GERAN LOFD-081283 Ultra-Flash CSFB to GERAN

If Huawei devices are used in the GERAN or UTRAN to which CS fallback is performed, refer to the following documents to obtain details about CSFB implementation in the corresponding network:

For the GERAN, see CSFB in GBSS Feature Documentation. For the UTRAN, see Interoperability Between UMTS and LTE in RAN Feature

Documentation.

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.

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E

BTS3203E

LampSite DBS3900

1.2 Intended AudienceThis document is intended for personnel who:

Need to understand the features described herein Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There are two types of changes:

Feature change

Changes in features and parameters of a specified version as well as the affected entities

Editorial change

Changes in wording or addition of information and any related parameters affected by editorial changes. Editorial change does not specify the affected entities.

eRAN8.1 02 (2015-06-30)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change Added the measurement-specific DRX configuration for Ultra-Flash CSFB to GERAN. For details, see 4.5 Ultra-Flash CSFB to GERAN.

None Macro, micro, and LampSite eNodeBs

Added the random procedure selection Added the Macro,

Change Type Change Description Parameter Change Affected Entity

optimization for CSFB. For details, see 7.1.5.1 Data Preparation.

RsvdSwPara1_bit23 option in the reserved parameter eNBRsvdPara. RsvdSwPara1.

micro, and LampSite eNodeBs

Editorial change

None None -

eRAN8.1 01 (2015-03-23)

This issue includes the following changes.

Change Type

Change Description Parameter Change Affected Entity

Feature change

Added the UE compatibility risk optimization for Ultra-flash CSFB. For details, see 7.11.5.1 Data Preparation.

Added the UltraFlashCsfbComOptSw option to the GlobalProcSwitch.UeCompatSwitch parameter.

Macro, micro, and LampSite eNodeBs

Editorial change

None None -

eRAN8.1 Draft A (2015-01-15)

Compared with Issue 06 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Change Type

Change Description Parameter Change Affected

Entity

Feature change

Supported the cell-level blind handling switch for CSFB in CS Fallback to UTRAN or GERAN and Flash CS Fallback to UTRAN or GERAN scenarios.

For details about the switch, see 3.1 Basic CSFB to UTRAN and 3.1.2 Blind

Added the CellHoParaCfg.HoModeSwitch parameter.


Change Type


Entity

Handover. For details about

handover policy selection, see 3.9.1 Handover Policy Selection.

For details about scenario-specific parameter preparations, see section "Data Preparation" in engineering guidelines.

For details about scenario-specific configurations, see "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and "Using MML Commands" in section "Activation" in engineering guidelines.

Added the feature LOFD-081283 Ultra-Flash CSFB to GERAN.

For details about the feature description, see 4.5 Ultra-Flash CSFB to GERAN.

For details about the signaling procedure, see 4.9.6 Ultra-Flash CSFB to GERAN.

For details about related features and network impact, see 5.9 Feature Related

Added the GeranExternalCell.UltraFlashCsfbInd parameter.

Added the GeranUltraFlashCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter.


Change Type


Entity

to LOFD-081283 Ultra-Flash CSFB to GERAN and 6.9 LOFD-081283 Ultra-Flash CSFB to GERAN.

For details about engineering guidelines, see 7.11 LOFD-081283 Ultra-Flash CSFB to GERAN.

Added the configuration of the round-robin function for L2U blind redirections.

For details about the switch, see 3.1.2 Blind Handover.

For details about scenario-specific data preparations, see 7.1.5.1 Data Preparation.

For details about the function activation, see 7.1.5.5 Using MML Commands.

Added the CSFallBackBlindHoCfg.UtranCsfbBlindRedirRrSw parameter.


Added SPID-based mobility management. For details about the function, see 3.1.2 Blind Handover, 3.8.1 Basic Handover Decision, and 3.8.2 Flash Redirection Decision.

None Macro, micro, and LampSite eNodeBs

Ultra-flash CSFB to GERAN uses the DRX-based measurement, which is controlled by the CellDrxPara.DrxForMeasSwitch

Added the CellDrxPara.DrxForMeasSwitch parameter.


Change Type


Entity

parameter.

For details about the parameter, see 4.5 Ultra-Flash CSFB to GERAN.

For details about data preparations and MML configurations, see related sections in 7.11 LOFD-081283 Ultra-Flash CSFB to GERAN.

Editorial change

Changed "blind handling" to "blind handover". For details, see descriptions of blind handover in this document.

None -

1.4 Differences Between eNodeB TypesThe features described in this document are implemented in the same way on macro, micro, and LampSite eNodeBs.

2 OverviewIn an early phase of evolved packet system (EPS) construction, operators who own a mature UTRAN or GERAN can protect their investments in legacy CS networks and reduce their investments in the EPS by using legacy CS networks to provide CS services such as the voice service, short message service (SMS), location service (LCS), and emergency calls.

Currently, CSFB and voice over IP (VoIP) over IP multimedia subsystem (IMS) are the two standard solutions to provide voice services for E-UTRAN UEs. After the technological maturity, industry chain, and deployment costs of the two methods are well weighed, CSFB is chosen to serve as an interim solution for voice service access before mature commercial use of IMS.

2.1 OverviewWith the CSFB solution, when a UE initiates a CS service, the MME instructs the UE to fall back to the legacy CS network before the UE performs the service. CSFB is a session setup

procedure. UEs fall back to CS networks before CS sessions are set up, and they always stay in the CS networks during the CS sessions. For details, see 3GPP TS 23.272 V8.5.0.

The eNodeB handles the CSFB for different types of CS services in a uniform way such as the voice service, SMS, LCS, and emergency calls.

2.2 BenefitsCSFB brings the following benefits:

Facilitates voice services for the LTE network. Helps operators reduce costs by reusing legacy CS networks and not deploying an

IMS network.

2.3 ArchitectureCSFB is applicable to scenarios where the CS network of the UTRAN/GERAN has the same or larger coverage area than E-UTRAN.

The network architecture for CSFB is simple. To implement CSFB, all mobile switching centers (MSCs) that serve overlapping areas with the E-UTRAN coverage must be upgraded to support functions involving the SGs interface. The SGs interface is between an MSC and a mobility management entity (MME), and functions involving the SGs interface include combined attach, combined TAU/LAU (TAU is short for tracking area update, and LAU is short for location area update), paging, and SMS. If the live network uses an MSC pool, only one or multiple MSCs in the MSC pool need to be upgraded to support the SGs interface.

Figure 2-1 shows the network architecture for CSFB to UTRAN/GERAN.

Figure 2-1 Network architecture for CSFB to UTRAN/GERAN

Table 2-1 describes the elements of the network architecture in Figure 2-1.

Table 2-1 Elements of the network architecture for CSFB to UTRAN/GERANElement Function

SGs interface Is an interface between the MME and the MSC server. Assists mobility management and paging between the EPS and

the CS network. Transmits mobile originated (MO) and mobile terminated (MT)

SMS messages. Transmits messages related to combined attach and combined

TAU/LAU.

UE Is capable of accessing the EPS and accessing the UTRAN, GERAN, or both.

Supports combined EPS/IMSI (IMSI is short for international mobile subscriber identity) attach, combined EPS/IMSI detach, and combined TAU/LAU.

Supports CSFB mechanisms, such as PS redirection and PS handover.

NOTE:

CSFB-capable UEs must support SMS over SGs, but UEs that support SMS over SGs are not necessarily CSFB-capable.

MME Supports the SGs interface to the MSC/VLR. Selects the VLR and location area identity (LAI) based on the

tracking area identity (TAI) of the serving cell. Forwards paging messages delivered by the MSC. Performs public land mobile network (PLMN) selection and

reselection. Supports combined EPS/IMSI attach, combined EPS/IMSI

detach, and combined TAU/LAU. Routes CS signaling. Supports SMS over SGs. Supports RIM, which is required when flash CSFB or CCO with

NACC is used as the CSFB mechanism. (CCO is short for cell change order and NACC is short for network assisted cell change.)

MSC Supports combined EPS/IMSI attach. Supports SMS over SGs. Forwards paging messages transmitted through the SGs interface.

E-UTRAN Forwards paging messages related to CSFB. Selects target cells for CSFB for E-UTRAN UEs. Supports one or more of the following functions:

o PS redirection to UTRAN or GERAN, if PS redirection is

Element Function

used as the CSFB mechanism.o PS handover to UTRAN or GERAN, if PS handover is

used as the CSFB mechanism.o CCO without NACC to GERAN, if CCO without NACC

is used as the CSFB mechanism; RIM for acquiring the system information of GERAN cells, if NACC is used as the CSFB mechanism.

o RIM for acquiring the system information of UTRAN or GERAN cells, in addition to PS redirection, if flash CSFB is used as the CSFB mechanism.

UTRAN/GERAN Supports one or more of the following functions:

Incoming handovers from the E-UTRAN, if PS handover is used as the CSFB mechanism.

RIM for delivering the system information of GERAN cells to eNodeBs, if CCO with NACC is used as the CSFB mechanism.

RIM for delivering the system information of UTRAN or GERAN cells to eNodeBs, in addition to PS redirection, if flash CSFB is used as the CSFB mechanism.

NOTE:

The UTRAN and GERAN do not need to provide extra functions to support PS redirection. The GERAN does not need to provide extra functions to support CCO without NACC.

SGSN Supports the follow-up procedures performed for the PS handover, including data forwarding, path switching, RAU, and encryption and authentication.

Supports RIM, which is required when flash CSFB or CCO with NACC is used as the CSFB mechanism.

eCoordinator Is a network element provided by Huawei, and is optional. The eCoordinator supports the RIM procedure.

3 CSFB to UTRANCSFB to UTRAN can be implemented in different ways, and this section covers the following features/functions:

LOFD-001033 CS Fallback to UTRAN LOFD-001052 Flash CS Fallback to UTRAN LOFD-070202 Ultra-Flash CSFB to UTRAN LOFD-001068 CS Fallback with LAI to UTRAN

LOFD-001078 E-UTRAN to UTRAN CS/PS Steering LOFD-001088 CS Fallback Steering to UTRAN

Load-based CSFB to UTRAN

The triggering conditions for different features are different. Basically the procedure for CSFB to UTRAN is as follows:

1. Selecting a target cell or frequency

In a measurement-based handover, the eNodeB generates a candidate cell list based on inter-RAT measurement results and selects a target cell from the list.

In a blind handover, the eNodeB selects a target cell based on the blind handover priorities of neighboring cells or selects a target frequency based on the frequency priorities.

2. Handover decision

In the handover decision phase, the eNodeB checks the target cell list.

3. Handover execution

The eNodeB controls the UE to be handed over from the serving cell to the target cell.

3.1 Basic CSFB to UTRANThis section describes the optional feature LOFD-001033 CS Fallback to UTRAN. For details about the engineering guidelines for this feature, see 7.1 LOFD-001033 CS Fallback to UTRAN. The UtranCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.

When a UE initiates a CS service in the E-UTRAN, the MME sends an S1-AP message containing CS Fallback Indicator to the eNodeB, instructing the eNodeB to transfer the UE as well as the CS service to a target network.

The eNodeB determines whether to trigger UTRAN measurements or blind handling for CSFB to UTRAN based on the status of the blind handling switch first. The blind handover switch is controlled by the BlindHoSwitch option in the eNodeB-level parameter ENodeBAlgoSwitch.HoModeSwitch and the BlindHoSwitch option in the cell-level parameter CellHoParaCfg.HoModeSwitch. The blind handover function takes effect only if the eNodeB-level BlindHoSwitch and cell-level BlindHoSwitch options are selected.

If this option is selected, the eNodeB triggers blind handover directly. If this option is cleared, the eNodeB determines whether to trigger inter-RAT

measurements or blind handover based on the UE capability:o If the UE supports UTRAN measurements, the eNodeB triggers inter-RAT

measurements.

o If the UE does not support UTRAN measurements, the eNodeB triggers a blind handover.

3.1.1 Handover Measurement

Measurement Triggering Reason

During CSFB, the eNodeB starts a UTRAN measurement after it receives a CS Fallback Indicator. The measurement configuration is the same as that for coverage-based handover from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility Management in Connected Mode.

Figure 3-1 shows the measurement object selection procedure.

Figure 3-1 Measurement object selection procedure

The configurations involved in Figure 3-1 are as follows:

Neighboring UTRAN frequencies are added by running the ADD UTRANNFREQ command.

The frequency priority is specified by the UtranNFreq.ConnFreqPriority parameter. A larger value indicates a higher priority.

The cell measurement priorities of neighboring UTRAN cells can be automatically optimized by ANR. The UTRAN_SWITCH option in the

ENodeBAlgoSwitch.NCellRankingSwitch parameter is used to enable this function. This option is recommended to be selected if ANR is enabled.

o If this option is selected, the eNodeB automatically optimizes the setting of the UtranNCell.NCellMeasPriority parameter for the cell. This parameter cannot be modified manually. For details, see ANR Management.

o If this option is cleared, the cell measurement priorities are specified by the UtranNCell.CellMeasPriority parameter, which needs to be configured manually.

The number of frequencies or cells that the eNodeB can randomly select for measurement is always equal to the allowed maximum number.

The maximum number of frequencies is specified by the CellUeMeasControlCfg.MaxUtranFddMeasFreqNum parameter.

For details about the maximum number of neighboring cells in a measurement configuration message, see section 6.4 "RRC multiplicity and type constraint values" in 3GPP TS 36.331 V10.1.0.

Triggering of CSFB

During the measurement procedure, CSFB is triggered by event B1. The principle of triggering CSFB by event B1 is the same as that of triggering the coverage-based inter-frequency handover by event B1. For details, see Inter-RAT Mobility Management in Connected Mode.

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

Table 3-1 Parameters related to event B1 for CSFB to UTRANParameter Name

Parameter ID Parameter Description

CSFB UTRAN EventB1 RSCP Trigger Threshold

CSFallBackHo.CsfbHoUtranB1ThdRscp

The InterRatHoComm.InterRATHoUtranB1MeasQuan parameter determines which threshold is to be used.

CSFB UTRAN EventB1 ECN0 Trigger Threshold

CSFallBackHo.CsfbHoUtranB1ThdEcn0

CSFB Utran EventB1

CSFallBackHo.CsfbHoUtranTimeToTrig

N/A

Parameter Name

Parameter ID Parameter Description

Time To Trig

3.1.2 Blind Handover

Triggering of Blind Handover

The blind handover switch is controlled by the BlindHoSwitch option in the ENodeBAlgoSwitch.HoModeSwitch parameter and the BlindHoSwitch option in the CellHoParaCfg.HoModeSwitch parameter. The blind handover function takes effect only if the eNodeB-level BlindHoSwitch and cell-level BlindHoSwitch options are selected.

When an E-UTRAN coverage area is larger than a UTRAN coverage area and E-UTRAN and UTRAN base stations are co-sited, adaptive-blind-handover-based CSFB estimates the signal strength of the neighboring UTRAN cell based on the signal strength of the serving E-UTRAN cell.

If the UE is located in the center of the E-UTRAN cell, the eNodeB performs the blind handover.

If the UE is located at the edge of the E-UTRAN cell, the eNodeB performs a measurement-based handover.

When the blind handover function takes effect:

If adaptive-blind-handover-based CSFB is disabled, the eNodeB directly enters the blind handover procedure.

If adaptive-blind-handover-based CSFB is enabled, the eNodeB delivers measurement configurations for event A1.

o If the eNodeB receives an event A1 report and determines that the UE is located in the center of the E-UTRAN cell, it directly enters the blind handover procedure.

o If the eNodeB does not receive an event A1 report and determines that the UE is located at the edge of the E-UTRAN cell, it enters the measurement procedure.

The event A1 threshold is specified by the CSFallBackHo.BlindHoA1ThdRsrp parameter, and other event-A1-related principles are the same as these in coverage-based handover from E-UTRAN to UTRAN. For details, see Inter-RAT Mobility Management in Connected Mode.

Target RAT Selection

During a blind handover for CSFB, the eNodeB selects the target RAT based on the RAT priorities specified by the following parameters:

CSFallBackBlindHoCfg.InterRatHighestPri: specifies the RAT with the highest priority.

CSFallBackBlindHoCfg.InterRatSecondPri: specifies the RAT with the second highest priority.

CSFallBackBlindHoCfg.InterRatLowestPri: specifies the RAT with the lowest priority.

If CSFallBackBlindHoCfg.InterRatHighestPri is set to UTRAN(UTRAN), the eNodeB performs CSFB to UTRAN.

When selecting target cells for blind handover, the eNodeB excludes the following neighboring cells:

o Blacklisted neighboring cellso Neighboring cells with a handover prohibition flago Neighboring cells that have a different PLMN from the serving cell in the

neighboring cell list. If the inter-PLMN handover switch is turned on, such cells are not excluded.

o Cells in the areas indicated by the Handover Restriction List IE in the INITIAL CONTEXT SETUP REQUEST message sent from the MME

After the preceding exclusion, the eNodeB excludes cells from the neighboring cell list based on SPID-based mobility management in connected mode. For details, see LOFD-00105401 Camp and Handover Based on SPID in Flexible User Steering Feature Parameter Description.

When selecting target frequencies for blind redirection, the eNodeB filters frequencies based on the RATs supported by the UE and PLMN information corresponding to frequencies.

After the preceding exclusion, the eNodeB filters cells from the neighboring cell list based on SPID-based mobility management in connected mode. For details, see LOFD-00105401 Camp and Handover Based on SPID in Flexible User Steering Feature Parameter Description.

During blind handover, the target selection procedure is different, depending on whether neighboring UTRAN cells are configured.

If neighboring UTRAN cells are configured, the target selection procedure is shown in Figure 3-2.

o The blind handover priority of a neighboring UTRAN cell is specified by the UtranNCell.BlindHoPriority parameter. A larger value indicates a higher priority.

o The priority of a neighboring UTRAN frequency is specified by UtranNFreq.ConnFreqPriority parameter. A larger value indicates a higher priority.

If no neighboring UTRAN cell is configured, neighboring UTRAN frequencies are configured, and the UE performs CSFB based on redirection, the target selection procedure is shown in Figure 3-3.

o Neighboring UTRAN frequencies are configured in UtranNFreq MOs.o The PLMN information of the neighboring UTRAN frequencies is contained

in the configured UtranRanShare or UtranExternalCell MOs.

Figure 3-2 Target cell selection (configured with a neighboring UTRAN cell)

Figure 3-3 Target cell selection (configured with no neighboring UTRAN cell)

When a UE performs a blind redirection, the eNodeB preferentially selects the frequency with the highest priority. If multiple frequencies are of the same priority, the eNodeB selects the blind redirection frequency in a round-robin manner. This ensures that the UE accesses each frequency equally. This function is specified by the CSFallBackBlindHoCfg.UtranCsfbBlindRedirRrSw parameter.

3.2 Flash CSFB to UTRANThis section describes the optional feature LOFD-001052 Flash CS Fallback to UTRAN. For details about the engineering guidelines for this feature, see 7.3 LOFD-001052 Flash CS Fallback to UTRAN. The UtranFlashCsfbSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.

This feature is an enhancement to the optional feature LOFD-001033 CS Fallback to UTRAN. After this feature is activated. the eNodeB obtains the UTRAN cell information through the RIM procedure and then sends the LTE-to-UMTS redirection message including the obtained UTRAN cell information to the UE. In this case, the UE can access a UTRAN cell without obtaining the UTRAN cell information. This reduces the access delay. For details about how the UTRAN cell information is delivered to the eNodeB through the RIM procedure, see Interoperability Between UMTS and LTE.

This feature requires that the eNodeB can obtain UTRAN cell information through the RIM procedures and the networks and UEs involved must support 3GPP Release 9 or later. For details about the RIM procedure, see 3.10 RIM Procedure Between E-UTRAN and UTRAN.

Other procedures are the same as those in CSFB to UTRAN. For details, see 3.1 Basic CSFB to UTRAN.

3.3 Ultra-Flash CSFB to UTRANThis section describes the optional feature LOFD-070202 Ultra-Flash CSFB to UTRAN. For details about the engineering guidelines for this feature, see 7.4 LOFD-070202 Ultra-Flash CSFB to UTRAN. The UtranUltraFlashCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature. This feature is a Huawei-proprietary feature. To enable this feature, the MME, MSC, and RNC must all provided by Huawei and support this feature.

When a UE initiates a CS service setup request in an LTE cell that does not support VoIP, this feature enables the eNodeB to hand over the UE to the UTRAN through the SRVCC handover procedure. This shortens the access delay for CS fallbacks by 1 second.

The measurement procedure and blind handover procedure for this feature are the same as those in CSFB to UTRAN. For details, see 3.1 Basic CSFB to UTRAN.

NOTE:

The following table describes the parameters that must be set in the GLOBALPROCSWITCH MO to turn on the UE compatibility switch when UEs do not support Ultra-Flash CSFB, resulting in UE compatibility problems.

3.4 CS Fallback with LAI to UTRANThis section describes the optional feature LOFD-001068 CS Fallback with LAI to UTRAN. For details about the engineering guidelines for this feature, see 7.5 LOFD-001068 CS Fallback with LAI to UTRAN. This feature is under license control and is not controlled by a switch.

This feature mainly applies to the following scenarios:

In a multi-PLMN or national roaming scenario

An LAI consists of a PLMN ID and a LAC. In the CSFB with LAI function, the PLMN ID identifies the CS network that the UE has registered with and will fall back to after fallback.

If the serving E-UTRAN cell has multiple neighboring UTRAN or GERAN cells with different PLMN IDs and the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected, or the serving PLMN differs from the target PLMN, the operator can use CSFB with LAI to achieve fallback to a specified target network.

In a tracking area (TA) that overlaps multiple location areas (LAs)

The eNodeB selects a CSFB target cell with the same LAC as that mapped to the network to which the UE has attached. An LAU is not required after CSFB, and therefore the CSFB delay does not include the LAU time.

This feature is an enhancement to the optional feature LOFD-001033 CS Fallback to UTRAN. With this feature, the eNodeB selects a target frequency or cell for measurement or blind handover based on the LAI sent by the MME.

In a measurement procedure, the eNodeB selects only an inter-RAT frequency on which the PLMN ID of a neighboring cell is the same as that in the LAI received. The follow-up measurement procedure is similar to that in CS Fallback to UTRAN. For details, see 3.1.1 Handover Measurement.

The difference is that the eNodeB sorts neighboring cells in the following order after receiving measurement reports from a UE:

1. Neighboring cells with PLMN IDs and LACs the same as those in the LAI2. Neighboring cells with PLMN IDs the same as that in the LAI but LACs

different from that in the LAI

If no frequency or neighboring cell can be selected based on the LAI, the processing is the same as that when no LAI is received.

In a blind handover procedure, the eNodeB first selects a target cell for blind handover.

If no neighboring UTRAN cell is configured, the eNodeB preferentially selects the UTRAN frequencies whose PLMN ID is the same as that in the LAI. The follow-up procedure is the same as that described in 3.1.2 Blind Handover.

If neighboring UTRAN cells are configured, the eNodeB preferentially selects the operating UTRAN frequencies of the neighboring UTRAN cells whose PLMN ID is the same as that in the LAI. The eNodeB then sorts the frequencies based on the blind handover priorities of the neighboring cells and frequency priorities for connected mode. For details, see 3.1.2 Blind Handover.

The eNodeB selects a target cell in the following order of preference:

1. Neighboring cell whose PLMN ID and LAC are the same as those in the LAI2. If no neighboring cells described in 1 exist, the eNodeB selects the

neighboring cells with PLMN IDs the same as that in the LAI but LACs different from that in the LAI.

3. If no neighboring cells described in 1 and 2 exist, the eNodeB selects the neighboring cells with PLMN IDs the same as the serving PLMN ID of the UE.

If the InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected, the eNodeB also selects cells whose PLMN IDs are in the target PLMN list.

3.5 E-UTRAN to UTRAN CS SteeringThis section describes the CS steering function in the optional feature LOFD-001078 E-UTRAN to UTRAN CS/PS Steering. For details about the engineering guidelines for this function, see 7.7 LOFD-001078 E-UTRAN to UTRAN CS/PS Steering. For details about the PS steering function in this feature, see Inter-RAT Mobility Management in Connected Mode.

This feature applies to a scenario where service steering is required in a UTRAN with multiple UTRAN frequencies. By setting CS service priorities for UTRAN frequencies, the operator can achieve CSFB from E-UTRAN only to the UTRAN frequency that has a high CS service priority.

CS Steering in CSFB

This function is an enhancement to the CS Fallback to UTRAN feature. The enhancements are as follows:

During inter-RAT measurement on the UTRAN, frequencies with a high CS service priority are preferentially measured.

The UtranFreqLayerMeasSwitch option of the ENodeBAlgoSwitch.FreqLayerSwtich parameter specifies whether to enable this function.

If the option is selected, the eNodeB preferentially selects frequencies with a high CS service priority specified by the UtranNFreq.CsPriority parameter as the measurement targets. A larger value of this parameter indicates a higher priority. If this parameter is set to Priority_0(Priority 0) for a frequency, the eNodeB does not select this frequency as the measurement target. The follow-up measurement procedure is the same as that in CS Fallback to UTRAN. For details, see 3.1.1 Handover Measurement.

During blind handover, cells working on frequencies with a high CS service priority are preferentially selected.

The UtranFreqLayerBlindSwitch option of the ENodeBAlgoSwitch.FreqLayerSwtich parameter specifies whether to enable this function.

If the option is selected, the eNodeB preferentially selects cells working on frequencies with a high CS service priority specified by the UtranNFreq.CsPriority parameter. A larger value of this parameter indicates a higher priority. If this parameter is set to Priority_0(Priority 0) for a frequency, the eNodeB does not select cells working on this frequency. The follow-up blind handover procedure is the same as that in CS Fallback to UTRAN. For details, see 3.1.2 Blind Handover.

LAI-based CS Steering in CSFB

This function is an enhancement to the CS Fallback with LAI to UTRAN feature. The enhancements are as follows:

Enhancement in measurement1. The eNodeB selects inter-RAT frequencies on which the PLMN ID of a

neighboring cell is the same as the PLMN ID in the LAI.2. Among the selected frequencies, the eNodeB selects a frequency with a high

CS service priority specified by the UtranNFreq.CsPriority parameter.3. The follow-up measurement procedure is similar to that in CS Fallback to

UTRAN. For details, see 3.1.1 Handover Measurement.

The difference is that the eNodeB sorts neighboring cells in the following order after receiving measurement reports from a UE:

4. Neighboring cells with PLMN IDs and LACs the same as those in the LAI5. Neighboring cells with PLMN IDs the same as that in the LAI but LACs

different from that in the LAI6. Neighboring cells with PLMN IDs the same as the serving PLMN ID of the

UE Enhancement in blind handover

1. The eNodeB selects frequencies whose PLMN ID is the same as the PLMN ID in the LAI.

2. Among the selected frequencies, the eNodeB selects a frequency with a high CS service priority specified by the UtranNFreq.CsPriority parameter.

3. The eNodeB selects a neighboring cell whose PLMN ID and LAC are the same as those in the LAI.

4. If such a neighboring cell is unavailable, the eNodeB selects a neighboring cell whose PLMN ID is the same as that in the LAI but LAC is different from that in the LAI.

5. The follow-up blind handover procedure is the same as that in CS Fallback to UTRAN. For details, see 3.1.2 Blind Handover.

3.6 CS Fallback Steering to UTRANThis chapter describes the optional feature LOFD-001088 CS Fallback Steering to UTRAN. For details about the engineering guidelines for this feature, see 7.6 LOFD-001088 CS Fallback Steering to UTRAN. The UtranCsfbSteeringSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.

This feature is an enhancement to the optional feature LOFD-001033 CSFB to UTRAN. In terms of the UE status at the time when the UE initiates a CS service, you can configure the target RAT and handover policy flexibly. There are two types of UEs:

CS-only UE

CS-only UE If the MME uses the INITIAL CONTEXT SETUP REQUEST message to send the CSFB indicator to the eNodeB, the eNodeB determines that the UE is in idle mode at the time when the UE initiates the CS service. This UE is called a CS-only UE.

CS+PS UE

If the MME uses the UE CONTEXT MODIFICATION REQUEST message to send the CSFB indicator to the eNodeB, the eNodeB determines that the UE is performing PS services at the time when the UE initiates the CS service. This UE is called a CS+PS UE.

CS-only UE

If the UE is a CS-only UE, the eNodeB selects the target RAT based on the RAT priorities for CSFB of CS-only UEs. The priorities are specified by the following parameters:

CSFallBackBlindHoCfg.IdleCsfbHighestPri: specifies the highest-priority RAT for CSFB of CS-only UEs.

CSFallBackBlindHoCfg.IdleCsfbSecondPri: specifies the second-highest-priority RAT for CSFB of CS-only UEs.

CSFallBackBlindHoCfg.IdleCsfbLowestPri: specifies the lowest-priority RAT for CSFB of CS-only UEs.

The eNodeB can select a neighboring cell or frequency with a lower-priority RAT only if no neighboring cell or frequency with higher-priority RATs is configured.

If the target system with the highest priority is UTRAN, the eNodeB selects the target frequencies based on the setting of the UtranNFreq.CsPriority parameter. For details, see 3.5 E-UTRAN to UTRAN CS Steering.

The eNodeB selects the handover policy for CSFB of CS-only UEs based on the setting of the CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. PS HO and redirection are selected in descending order.

CS+PS UE

The eNodeB selects the target RAT based on the RAT priorities specified by the following parameters:

CSFallBackBlindHoCfg.InterRatHighestPri: specifies the RAT with the highest priority.

CSFallBackBlindHoCfg.InterRatSecondPri: specifies the RAT with the second-highest priority.

CSFallBackBlindHoCfg.InterRatLowestPri: specifies the RAT with the lowest priority.

The eNodeB can select a neighboring cell or frequency with a lower-priority RAT only if no neighboring cell or frequency with higher-priority RATs is configured.

If the target system with the highest priority is UTRAN, the eNodeB selects the target frequencies based on the setting of the UtranNFreq.CsPsMixedPriority parameter. The UtranNFreq.CsPsMixedPriority and UtranNFreq.CsPriority parameters have similar setting principles. For details, see 3.5 E-UTRAN to UTRAN CS Steering.

The eNodeB selects the handover policy for CSFB based on the setting of the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. PS HO and redirection are selected in descending order.

3.7 Load-based CSFB to UTRANThis chapter describes load-based CSFB to UTRAN. This function is an enhancement to the CS Fallback to UTRAN feature. For details about the engineering guidelines for this feature, see 7.1 LOFD-001033 CS Fallback to UTRAN. The CSFBLoadInfoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this function.

In load-based CSFB to UTRAN, the eNodeB uses the RIM procedure in Multiple Report mode to obtain the load information about UTRAN cells. For details about the RIM procedure, see 3.10 RIM Procedure Between E-UTRAN and UTRAN. After receiving the load information about UTRAN cells, the eNodeB saves the information and uses the information to determine the target UTRAN cell for the CSFB.

In load-based CSFB to UTRAN, the measurement and blind handover procedures are the same as those in the CS Fallback to UTRAN feature. For details, see 3.1 Basic CSFB to UTRAN.

When the eNodeB selects the target UTRAN cell for the CSFB based on the load status of UTRAN cells, the eNodeB considers UTRAN cells in descending order as follows: cells whose load status is normal, cells whose load status is congested, and cells whose load status is overloaded.

Load-based CSFB to UTRAN affects the target cell selection at a later phase. If measurement is performed, the eNodeB does not select a low-priority frequency because all UTRAN cells on the high-priority frequency are overloaded.


3.8.1 Basic Handover Decision

When the handover policy is PS HO, SRVCC, or redirection (excluding flash redirection), the eNodeB does not need to obtain system information of the peer and performs the basic handover decision.

In the handover decision phase, the eNodeB checks the candidate cell list. Based on the check result, the eNodeB determines whether a handover needs to be initiated and, if so, to which cell the UE is to be handed over. If the eNodeB receives measurement reports about different RATs, it processes the reports in an FIFO manner.

The eNodeB excludes the following cells from the neighboring cell list:

Blacklisted neighboring cells Neighboring cells with a handover prohibition flag Neighboring cells that have a different PLMN from the serving cell in the neighboring

cell list

If the inter-PLMN handover switch is turned on, such cells are not excluded.

Neighboring cells in the areas indicated by the IE Handover Restriction List in the INITIAL CONTEXT SETUP REQUEST message sent from the MME

After the preceding exclusion, the eNodeB excludes cells from the neighboring cell list based on SPID-based mobility management in connected mode. For details, see LOFD-00105401 Camp & Handover Based on SPID in Flexible User Steering Feature Parameter Description.

The eNodeB then sends a handover request to the target cell at the top of the filtered candidate cell list. If the handover request fails, the eNodeB sends the handover request to the next target cell, as described in Table 3-2.

Table 3-2 Sequence of handover requests to be sent by the eNodeBCandidate Cell List

Generated bySequence of Handover Requests

Measurement A handover request is sent to the cell with the best signal quality.

Blind handover A handover request is sent to a cell or frequency that has the highest priority. If multiple cells have the highest priority, the eNodeB randomly selects a cell for blind handover.

If the handover request fails in all candidate cells:

For a measurement procedure, the eNodeB waits until the UE sends the next measurement report.

For a blind handover procedure, the eNodeB finishes the handover attempt.

3.8.2 Flash Redirection Decision

When the handover policy requires the eNodeB to obtain system information about the peer, for example, flash redirection, handover decision based on system information is performed. If the handover decision is based on system information, the eNodeB includes system information of the target cell of the corresponding RAT. Therefore, the time for reading cell system information is not required so that the UE can quickly access the target network.

Decision based on system information adheres to the following principles:

In blind handover scenarios:1. The target cell list for blind handover is selected, including other cells under

the target frequency for redirection. The UTRAN_SWITCH option of the ENodeBAlgoSwitch.NCellRankingSwitch parameter specifies the sequence of adding other cells.

When this option is selected, the eNodeB adds other cells in the target frequency according to UtranNCell.NCellMeasPriority in descending order.

When this option is cleared, the eNodeB adds other cells in the target frequency according to UtranNCell.CellMeasPriority in descending order.

2. Basic handover decision is applied. For details, see 3.8.1 Basic Handover Decision.

3. Cells whose system information is not obtained are filtered out.4. The eNodeB excludes cells from the neighboring cell list based on SPID-

based mobility management in connected mode. For details, see LOFD-00105401 Camp & Handover Based on SPID in Flexible User Steering Feature Parameter Description.

In measurement scenarios:1. Cells in the candidate cell list generated by measurement are selected, plus

cells that are not in measurement reports but work on the target frequency for redirection. The UTRAN_SWITCH option of the ENodeBAlgoSwitch.NCellRankingSwitch parameter specifies the sequence of adding other cells.

2. Basic handover decision is applied. For details, see 3.8.1 Basic Handover Decision.

3. Cells whose system information is not obtained are filtered out.

You can specify the number of UTRAN cells contained in the redirection message by setting the InterRatHoComm.CellInfoMaxUtranCellNum parameter. Assume that this parameter is set to N.

If the number of target cells after flash redirection decision is greater than N, the eNodeB selects the first N cells.

If the number of target cells after flash redirection decision is smaller than N, the eNodeB selects target cells after flash redirection decision.

The eNodeB obtains system information of target cells in the RAN information management (RIM) procedure. If a target cell does not support the RIM procedure, the eNodeB cannot obtain system information of that cell.


3.9.1 Handover Policy Selection

When a UE in an LTE system needs to perform voice service but the LTE system does not support VoIP, a CSFB to an inter-RAT network is triggered.

CSFB from E-UTRAN to UTRAN can be based on PS handover, redirection, or flash redirection, as shown in Figure 3-4. This handover policy selection procedure is based on the assumption that neighboring frequency and neighboring cell configurations are proper.

During a CSFB based on blind PS handover, if the target cell with the highest blind handover priority fails to prepare the handover, the eNodeB attempts another cell with the second highest blind handover priority. The eNodeB can attempt a maximum of eight cells. If all these cells fail in preparation, the eNodeB performs CSFB based on redirection.

Figure 3-4 E-UTRAN-to-UTRAN CSFB policy selection procedure

The parameters mentioned in the preceding figure are described as follows:

The timer length is specified by the CSFallBackHo.CsfbProtectionTimer parameter. If the UE stays in the area covered by the eNodeB before the timer expires, the eNodeB performs the CSFB based on the blind redirection,

o The eNodeB preferentially selects a system that the UE has not measured. For example, if the UE has measured the UTRAN, the eNodeB preferentially selects the GERAN for redirection.

o If a cell to which the eNodeB has never attempted to hand over the UE is reported, the eNodeB preferentially selects the operating frequency of the cell for redirection.

o The eNodeB selects the target cell for redirection as it does during blind handover. For details about how the eNodeB performs target selection during blind handover, see 3.1.2 Blind Handover.

o If there is not target frequency available for redirection, the eNodeB stops the procedure.

o If flash CSFB is enabled in this situation, redirection-based CSFB performed by the eNodeB is referred to as CSFB emergency redirection. In this scenario, you need to set the InterRatHoComm.UTRANCellNumForEmcRedirect parameter to specify the maximum number of UTRAN cell system information messages that can be transmitted during a CSFB emergency redirection procedure.

The blind handover switch is controlled by the BlindHoSwitch option in the eNodeB-level parameter ENodeBAlgoSwitch.HoModeSwitch and the BlindHoSwitch option in the cell-level parameter CellHoParaCfg.HoModeSwitch. The blind handover function takes effect only when the eNodeB-level BlindHoSwitch and cell-level BlindHoSwitch options are selected.

The adaptive-blind-handover-based CSFB switch is controlled by the CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter.

If PS handover for CSFB is required, select the UtranPsHoSwitch option of the ENodeBAlgoSwitch.HoModeSwitch parameter and the PS_HO option of the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. If either option is cleared, PS handover for CSFB is invalid. The eNodeB selects the redirection policy. If the redirection policy is invalid and the CSFB protection timer expires, the eNodeB enters the blind redirection procedure.

If blind redirection for CSFB is required, select the REDIRECTION option of the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.

The CSFB policy is specified by different parameters, depending on whether LOFD-001088 CS Fallback Steering to UTRAN is enabled.

If this feature is enabled:

o The CSFB policy for UEs in idle mode is specified by the CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.

o The CSFB policy for UEs in connected mode is specified by the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.

If this feature is not enabled, the CSFB policy is specified by the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether UEs are in idle or connected mode.


This section describes the optional feature LOFD-070202 Ultra-Flash CSFB to UTRAN. For details about the engineering guidelines for this feature, see 7.4 LOFD-070202 Ultra-Flash CSFB to UTRAN. The UtranUltraFlashCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature. This feature is a Huawei-proprietary feature. To enable this feature, the MME, MSC, and RNC must all provided by Huawei and support this feature.

When a UE initiates a CS service setup request in an LTE cell that does not support VoIP, this feature enables the eNodeB to hand over the UE to the UTRAN through the SRVCC handover procedure. This shortens the access delay for CS fallbacks by 1 second.

The measurement procedure and blind handover procedure for this feature are the same as those in CSFB to UTRAN. For details, see 3.1 Basic CSFB to UTRAN.

When a UE in an LTE system needs to perform voice service but the LTE system does not support VoIP, the eNodeB decides to perform ultra-flash CSFB if LOFD-070202 Ultra-Flash CSFB to UTRAN is enabled. Figure 3-5 shows ultra-flash CSFB to UTRAN by using the SRVCC procedure after the eNodeB performs a measurement or blind handover decision. For details about how to select other CSFB policies, see 3.9.1 Handover Policy Selection.

Figure 3-5 Ultra-Flash CSFB to UTRAN

The preceding figure is described as follows:

The ultra-flash CSFB to UTRAN switch is controlled by the UtranUltraFlashCsfbSwitch option of the ENodeBAlgoSwitch. HoAlgoSwitch parameter.

At least one neighboring UTRAN cell's RNC support ultra-flash CSFB to UTRAN.o If all neighboring UTRAN cells' RNCs support ultra-flash CSFB to UTRAN,

no configuration is required.o If some neighboring UTRAN cells' RNCs do not support ultra-flash CSFB to

UTRAN, the following configurations are required:

Select the UtranSepOpMobilitySwitch option of the ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.

For RNCs that do not support ultra-flash CSFB to UTRAN, do not select the corresponding UltraFlashCsfbCap option of the UtranNetworkCapCfg.NetworkCapCfg parameter.


To speed up CSFB for UEs in idle mode by shortening end-to-end delays and to reduce the CSFB failure rate due to initial context setup failures, redirection-based CSFB for UEs in idle mode is optimized.

The optimization is performed after the eNodeB decides to perform blind handover, as shown in Figure 3-6.

Figure 3-6 Redirection-based CSFB optimization for UEs in idle mode

The optimization switch is controlled by the IdleCsfbRedirectOptSwitch option of the GlobalProcSwitch.ProtocolMsgOptSwitch parameter.

For details about how to decide between redirection and flash redirection, see 3.9.1 Handover Policy Selection.

For the signaling procedure, see 3.11.6 Redirection-based CSFB Optimization for UEs in Idle Mode.

3.9.4 CSFB Admission Optimization for UEs in Idle Mode

UEs in idle mode only have a default bearer for data service, and the allocation/retention priority (ARP) of the default bearer is generally lower. When a UE in idle mode needs to

perform CSFB but the target cell is congested or cannot accommodate more UEs, this UE cannot preempt resources in the target cell.

To ensure the CSFB success rate in the preceding scenario, the eNodeB can preferentially admit CSFB UEs. This function is controlled by the CSFallBackPolicyCfg.CsfbUserArpCfgSwitch parameter.

A larger value of the CsFallbackPolicyCfg.NormalCsfbUserArp parameter indicates a higher probability of admission of CSFB UEs in idle mode. For details about the admission procedure, see Admission and Congestion Control.

3.10 RIM Procedure Between E-UTRAN and UTRANThe RIM procedure exchanges information between the E-UTRAN and UTRAN through the core networks.

In CSFB procedures, the eNodeB obtains the load information of external UTRAN cells from RNCs through the RIM procedure if the parameter GlobalProcSwitch.UtranLoadTransChan is set to BASED_ON_RIM.

In flash CSFB procedures, the eNodeB obtains the system information (SI) of external cells from RNCs through the RIM procedure. For details about related parameters, see 3.10.1 RIM Procedure Through the Core Network and 3.10.2 RIM Procedure Through the eCoordinator.

The RIM procedure includes the following two information exchange modes:

Single Report

In Single Report mode, the source sends a request, and then the target responds with a single report.

When flash CSFB to UTRAN is triggered, the eNodeB sends a RIM message to the RNC and then includes the obtained SI in a redirection message to send to the UE. If the SI fails to be obtained from the RNC, the eNodeB no longer attempts the RIM request.

Multiple Report

In Multiple Report mode, the target responds with a report after receiving a request from the source, and the target also sends a report to the source each time information about the target changes.

When flash CSFB to UTRAN is triggered, the eNodeB sends RIM messages to all neighboring UTRAN cells every four seconds no matter whether the eNodeB has CSFB services.

To ensure that the SI of the target cell can be obtained successfully, the eNodeB starts a four-second timer when it sends a RIM message.

o If the eNodeB receives a response to the RIM message before the timer expires, the eNodeB saves the obtained SI.

o If the eNodeB receives a response to the RIM message after the timer expires, the eNodeB considers that an exception occurs and discards the SI.

o If the eNodeB does not receive a response to the RIM message when the timer expires, the eNodeB sends the RIM message and starts the timer again (called a retry) two hours later. If the eNodeB still does not receive a response after 10 retries, the RIM request fails. The interval between the nth and (n+1)th retries is twice the interval between the (n-1)th and nth retries. For example, the first retry occurs two hours after the first SI acquisition fails, the second retry occurs four hours after the first retry fails, and the third retry occurs six hours after the second retry fails. For each retry, the eNodeB sends a RIM message and restarts the timer.

The eNodeB may obtain incorrect SI due to the abnormalities in the UTRAN, core network, or transport network. To avoid this situation, the eNodeB selects a time point randomly every day from 02:00 a.m. to 04:00 a.m and deletes all the obtained SI. Then, the eNodeB requests the SI of UTRAN cells through the RIM procedure again.

If a neighboring UTRAN cell is faulty or deactivated, the RNC sends an END message to notify the eNodeB of stopping the RIM procedure. In this case, the eNodeB deletes the obtained SI and requests SI again in the next RIM procedure.

Currently, the eNodeB triggers a RIM procedure in Multiple Report mode only if MMEs comply with 3GPP Release 9 or later.

The RIM procedure can be performed through the core network or eCoordinator.

3.10.1 RIM Procedure Through the Core Network

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is performed through the core network As shown in Figure 3-7, the RIM procedure involves the eNodeB, MME, SGSN, and RNC Among these NEs, the MME and the SGSN transfer but do not resolve information. For details, see section 8c "Signalling procedures between RIM SAPs" in 3GPP TS 48.018 V10.0.0.

Figure 3-7 Performing the RIM procedure through the core network

The preceding figure is described as follows:

The RIM procedure between EUTRAN and UTRAN is controlled by the UTRAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter.

If this option is selected, the eNodeB uses the RIM procedure in Multiple Report mode to obtain the system information of external UTRAN cells.

Whether multiple UTRAN operators can use different mobility policies is specified by the UtranSepOpMobilitySwitch option of the ENodeBAlgoSwitch.MultiOpCtrlSwitch parameter.

The RIM procedure for obtaining SI is controlled by the SiByRimCapCfg option of the UtranNetworkCapCfg.NetworkCapCfg parameter.

Figure 3-8 Information exchange mode selection for the RIM procedure

3.10.2 RIM Procedure Through the eCoordinator

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is performed through the eCoordinator. As shown in Figure 3-9, the RIM procedure through the eCoordinator involves the eNodeB, eCoordinator, and RNC. Among these NEs, the MME and the SGSN transfer but do not resolve information.

Figure 3-9 RIM procedure through the eCoordinator

The RIM procedure through the eCoordinator requires that the corresponding switches of all NEs involved to be switched on.

During the RIM procedure through the eCoordinator, the eNodeB does not send RIM messages to the EPC or process RIM messages from the EPC.

The information exchange mode for the eCoordinator-based RIM procedure is controlled by UTRAN_RIM_SWITCH under the ENodeBAlgoSwitch.RimSwitch parameter.

If this switch is on, the eNodeB uses the RIM procedure in Multiple Report mode to obtain the system information of external UTRAN cells.

If this switch is off, the eNodeB uses the RIM procedure in Single Report mode.

3.11 CSFB to UTRAN


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

Figure 3-10 Combined EPS/IMSI attach procedure

HSS: home subscriber server VLR: visitor location register

NOTE:

The symbols that appear in signaling procedure figures throughout this document are explained as follows:

An arrow denotes the transmission of a message. A plain box denotes a mandatory procedure. A dashed box denotes an optional procedure.

The combined EPS/IMSI attach procedure is described as follows:

1. The UE sends a Combined attach request message to the MME, requesting a combined EPS/IMSI attach procedure. This message also indicates whether the CSFB or SMS over SGs function is required.

2. The EPS attach procedure is performed in the same way as it is performed within the LTE system. For details, see section 5.3.2 in 3GPP TS 23.401 V9.2.0.

3. The MME allocates an LAI to the UE, and then it finds the MSC/VLR for the UE based on the LAI. If multiple PLMNs are available for the CS domain, the MME selects a PLMN based on the selected PLMN information reported by the eNodeB. Then, the MME sends the MSC/VLR a Location update request message, which contains the new LAI, IMSI, MME name, and location update type.

4. The MSC/VLR performs the location update procedure in the CS domain.5. The MSC/VLR responds with a Location update accept message that contains

information about the VLR and temporary mobile subscriber identity (TMSI). The location update procedure is successful.

6. The UE is informed that the combined EPS/IMSI attach procedure is successful. If the network supports SMS over SGs but not CSFB, the message transmitted to the UE contains the information element (IE) SMS-only. The message indicates that the combined EPS/IMSI attach procedure is successful but only SMS is supported.


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

Call procedure

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

Figure 3-11 CSFB to UTRAN based on PS handover for mobile-originated calls

1. The UE sends the MME an NAS message Extended Service Request to initiate a CS service.

2. The MME sends an S1-AP message to instruct the eNodeB to initiate a CSFB procedure. If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.

3. If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.

4. The eNodeB initiates the preparation phase for a PS handover. If the preparation is successful, the eNodeB instructs the UE to perform a handover.

NOTE:

For details about how the eNodeB selects a target cell and a CSFB policy, see 3.8 Handover Decision and 3.9 Handover Execution.

5. After the handover, the UE may initiate a CS call establishment procedure with an LAU or combined RAU/LAU procedure in the UTRAN.

6. The follow-up procedures are performed for the PS handover. These procedures include data forwarding, path switching, and RAU. This step is performed together with 5.

CSFB Procedure for Mobile-terminated Calls

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

Figure 3-12 CSFB to UTRAN based on PS handover for mobile-terminated calls

1. The MSC sends a Paging Request message from the CS domain to the MME over the SGs interface. Then, either of the following occurs:

o If the UE is in idle mode, the MME sends a Paging message to the eNodeB. Then the eNodeB sends a Paging message over the Uu interface to inform the UE of an incoming call from the CS domain.

o If the UE is in active mode, the MME sends the UE an NAS message to inform the UE of an incoming call from the CS domain.

2. The UE sends an Extended Service Request message containing a CS Fallback Indicator after receiving the paging message from the CS domain.

3. The MME instructs the eNodeB over the S1 interface to perform CSFB.4. The subsequent steps are similar to steps 3 through 6 in the procedure for CSFB to

UTRAN based on PS handover for mobile-originated calls. The only difference is that the UE sends a Paging Response message from the UTRAN cell.

3.11.3 Signaling procedure of redirection to CDMA2000 1xRTT

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

Call procedure

Figure 3-13 shows the procedure for CSFB to UTRAN based on redirection for mobile-originated calls.

Figure 3-13 CSFB to UTRAN based on redirection for mobile-originated calls




4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target UTRAN frequency. Then, the eNodeB initiates an S1 UE context release procedure.

NOTE:


5. The UE may initiate an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target cell.

6. The UE initiates a CS call establishment procedure in the target UTRAN cell.


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

3.11.4 Flash CSFB

During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it sends an RRC Connection Release message to release the UE. The message contains information about a target UTRAN frequency, as well as one or more physical cell identities and their associated system information. In this way, the UE can quickly access the target UTRAN without the need to perform the procedure for acquiring system information of the target UTRAN cell. Then, the UE can directly initiate a CS service in the UTRAN cell.

Call procedure

Figure 3-14 shows the procedure for CSFB to UTRAN based on flash redirection for mobile-originated calls.

Figure 3-14 CSFB to UTRAN based on flash redirection for mobile-originated calls




4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target UTRAN frequency, as well as one or more physical cell identities and their associated system information. Then, the eNodeB initiates an S1 UE context release procedure.

NOTE:

For details about how the eNodeB selects a target cell and a CSFB policy, see 3.8 Handover Decision and 3.9 Handover Execution. The system information of the target cell is acquired during the RIM procedure.


6. The UE initiates a CS call establishment procedure in the target UTRAN cell.


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


CSFB Procedure for Mobile-Originated Calls

Figure 3-15 shows the procedure of ultra-flash CSFB to UTRAN for mobile-originated calls. Compared with the standard procedure described in chapter 6 "Mobile Originating Call" in 3GPP TS 23.272 V10.9.0 and 3GPP TS 24.008 V11.0.0, Huawei ultra-flash CSFB to UTRAN for mobile-originated calls:

Excludes the authentication procedure because the UE has been authenticated in the LTE system before CSFB to UTRAN.

Excludes the ciphering procedure because the UE has performed ciphering as instructed during SRVCC.

Excludes the IMEI check procedure because the MME has sent the IMEI to the MSC during the preparation for SRVCC.

Excludes the CS resource setup procedure because the UTRAN system has prepared CS resources during SRVCC and therefore the UE does not need to reestablish the CS resource after SRVCC.

Figure 3-15 Flash CSFB to UTRAN for mobile-originated calls

CSFB Procedure for Mobile-Terminated Calls

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

Figure 3-16 Ultra-flash CSFB to UTRAN for mobile-terminated calls


After the NodeB receives an initial context setup request with a CS Fallback Indicator from the MME, the eNodeB does not perform the UE capability query, Uu security mode command, or RRC connection reconfiguration procedure with dashed lines in the following figure:

Figure 3-17 Redirection-based CSFB optimization for UEs in idle mode

3.11.7 CSFB for SMS

SMS services are unknown to the eNodeB because SMS messages are encapsulated in NAS messages. During interworking with the UTRAN, SMS messages are exchanged between the MME and the MSC over the SGs interface. Because a UE does not require fallback to the UTRAN to perform an SMS service, the SMS over SGs function can be used in a place covered only by the E-UTRAN.

As the SMS service is transparent to the eNodeB, the procedure is not described in this document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.


The CSFB procedure for an emergency call is the same as the CSFB procedure for a normal mobile-originated voice service. The UE sends an RRC Connection Request message over the Uu interface or the MME sends an Initial Context Setup Request or UE Context Modification Request message, which contains an IE to inform the eNodeB of the service type. Emergency calls take precedence over other services in the eNodeB.

If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in the handover restriction list when selecting the target cell. The eNodeB sends the RNC a handover request with the IE CSFB high priority in the IE Source to Target Transparent

Container. This request informs the RNC that a CSFB procedure is required for an emergency call. Upon receiving the information, the RNC preferentially processes this call when using related algorithms such as admission control.

If redirection is used for CSFB for emergency calls, the RRC Connection Request message that the UE sends when accessing the UTRAN contains the indication of a CS emergency call.

The UTRAN will treat this call as a common CS emergency call. For details about admission and preemption of emergency calls, see Emergency Call.

3.11.9 CSFB for LCS

After a UE initiates an LCS request, the MME performs an attach or combined TAU/LAU procedure to inform the UE of the LCS capability of the EPS. If the EPS does not support LCS, the UE falls back to the UTRAN to initiate LCS under the control of the EPS. The CSFB procedure is the same as the procedure for CSFB to UTRAN for mobile-originated calls.

If the UTRAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the MSC sends an LCS indicator to the MME over the SGs interface. Then, the MME instructs the eNodeB to perform CSFB for the UE. The CSFB procedure is the same as the procedure for CSFB to UTRAN for mobile-terminated calls. The UE performs the LCS service after the fallback to the UTRAN.

For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272 V10.0.0 and LCS.

4 CSFB to GERANCSFB to GERAN can be implemented in different ways, and this section covers the following features/functions:

LOFD-001034 CS Fallback to GERAN LOFD-001053 Flash CS Fallback to GERAN OFD-001069 CS Fallback with LAI to GERAN LOFD-001089 CS Fallback Steering to GERAN LOFD-081283 Ultra-Flash CSFB to GERAN

The triggering condition for different features are different. Basically the procedure is as follows:

1. Target cell/frequency selection

For a measurement, the eNodeB generates a candidate cell list based on inter-RAT measurement results.

For a blind handover, the eNodeB selects a blind handover target based on the blind handover priority or frequency priority of neighboring cells.

2. Handover decision

In the handover decision phase, the eNodeB checks the candidate cell list. Based on the check result, the eNodeB determines whether a handover needs to be initiated and, if so, to which cell the UE is to be handed over.

3. Handover execution

The eNodeB controls the UE to be handed over from the serving cell to the target cell.

4.1 Basic CSFB to GERANThis section describes the optional feature LOFD-001034 CS Fallback to GERAN. For details about the engineering guidelines for this feature, see 7.8 LOFD-001034 CS Fallback to GERAN. The GeranCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.

The blind handover switch is controlled by the BlindHoSwitch option in the eNodeB-level parameter ENodeBAlgoSwitch.HoModeSwitch and the BlindHoSwitch option in the cell-level parameter CellHoParaCfg.HoModeSwitch. The blind handover function takes effect only when the eNodeB-level BlindHoSwitch and cell-level BlindHoSwitch options are selected.

This feature has the same principle as CSFB to UTRAN, except the parameters mentioned below in this section. For details about the principle of CSFB to UTRAN, see 3.1 Basic CSFB to UTRAN.

Handover Measurement

The frequency priority used during target frequency selection is specified by the GeranNfreqGroup.ConnFreqPriority parameter. A larger value indicates a higher priority.

During the GERAN frequency selection for measurement that is different from the UTRAN frequency selection, if the total number of the GERAN frequencies that can be delivered in the frequency group with the highest priority and the frequencies that have been delivered exceeds the allowed maximum number 32, all frequencies in this frequency group cannot be delivered. The eNodeB determines whether the GERAN frequencies in the frequency group with the second highest priority can be delivered until the number of delivered frequencies is less than or equal to the maximum number of GERAN frequencies allowed for measurement or all frequency groups are determined.

In GERAN, no cell measurement priority is configured. If the number of cells working on a frequency exceeds the specification, the eNodeB randomly measures certain cells.

Blind Handover

If CSFallBackBlindHoCfg.InterRatHighestPri is set to GERAN(GERAN), the eNodeB performs CSFB to GERAN.

During blind handover, the target selection procedure is different, depending on whether neighboring GERAN cells are configured.

If neighboring GERAN cells are configured:o The blind handover priority of a GERAN neighboring cell is specified by the

GeranNcell.BlindHoPriority parameter. A larger value indicates a higher priority.

o The GERAN frequency group with the highest priority (specified by the GeranNfreqGroup.ConnFreqPriority parameter) is selected for blind handover. A larger value indicates a higher priority.

o If the priorities of neighboring GERAN cells or frequencies are the same, the eNodeB randomly selects a target cell or frequency. Due to uncertainty of random selection, to increase the probability of a successful blind handover, you are not advised to set an identical priority for neighboring GERAN cells or frequencies.

If no neighboring GERAN cell is configured:o Neighboring GERAN frequencies are configured in GeranNfreqGroup MOs.o The PLMN information of the neighboring GERAN frequency is contained in

the configured GeranRanShare or GeranExternalCell MOs.

4.2 Flash CSFB to GERANThis section describes the optional feature LOFD-001053 Flash CS Fallback to GERAN. For details about the engineering guidelines for this feature, see 7.10 LOFD-001053 Flash CS Fallback to GERAN. The GeranFlashCsfbSwitchh option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.

This feature is an enhancement to the optional feature LOFD-001034 CS Fallback to GERAN. After this feature is activated, the eNodeB obtains the GERAN cell information through the RIM procedure and then sends the LTE-to-GSM redirection message including the obtained GERAN cell information to the UE. The InterRatHoComm.CellInfoMaxGeranCellNum parameter specifies the maximum number of GERAN cells that can be contained in the redirection message, which is configurable.

In this case, the UE can access a GERAN cell without obtaining GERAN cell information. This reduces the access delay. For details about how the GERAN cell information is delivered to the eNodeB through the RIM procedure, see Interoperability Between GSM and LTE.

This feature has the same principle as flash CSFB to UTRAN. For details, see 3.2 Flash CSFB to UTRAN.

4.3 CS Fallback with LAI to GERANThis section describes the optional feature LOFD-001069 CS Fallback with LAI to GERAN. For details about the engineering guidelines for this feature, see 7.12 LOFD-001069 CS

Fallback with LAI to GERAN. This feature is under license control and is not controlled by a switch.

This feature has the same principle as CS fallback with LAI to UTRAN. For details, see 3.4 CS Fallback with LAI to UTRAN.

4.4 CS Fallback Steering to GERANThis chapter describes the optional feature LOFD-001089 CS Fallback Steering to GERAN. For details about the engineering guidelines for this feature, see 7.13 LOFD-001089 CS Fallback Steering to GERAN. The GeranCsfbSteeringSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature.

The principles of this feature are similar to the principles of the CS Fallback Steering to UTRAN feature. For details about the principles, see 3.6 CS Fallback Steering to UTRAN.

The eNodeB selects a handover policy for CSFB of a CS-only UE based on the setting of the CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter. The eNodeB selects PS HO, CCO, and redirection in descending order.

The eNodeB selects a handover policy for CSFB of a CS+PS UE based on the setting of the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter. The eNodeB selects PS HO, CCO, and redirection in descending order.

4.5 Ultra-Flash CSFB to GERANThis section describes the optional feature LOFD-081283 Ultra-Flash CSFB to GERAN. The GeranUltraFlashCsfbSwitch option in the ENodeBAlgoSwitch.HoAlgoSwitch parameter specifies whether to enable this feature. This feature is a Huawei-proprietary feature. To enable this feature, the MME, MSC, and eNodeB must be all provided by Huawei and support this feature.

When a UE initiates a voice setup request in an LTE cell that does not support VoIP, this feature enables the eNodeB to transfer the UE to the GERAN through the SRVCC handover procedure. This shortens the access delay for CS fallbacks by 2 seconds.

The measurement procedure and blind handover procedure for this feature are the same as those in CSFB to GERAN. For details, see 3.1 Basic CSFB to UTRAN.

The SRVCC handover policy for this feature is the same as that for ultra-flash CSFB to GERAN. For details, see 3.9.2 Ultra-Flash CSFB to UTRAN.

This feature requires that external GERAN cells support ultra-flash CSFB to GERAN.

If all external GERAN cells support ultra-flash CSFB to GERAN, no configuration is required.

If some external GERAN cells do not support ultra-flash CSFB to GERAN, the following configurations are required:

o Set UltraFlashCsfbInd to BOOLEAN_FALSE for external GERAN cells that do not support ultra-flash CSFB to GERAN.

o The ultra-flash CSFB to GERAN capability for external GERAN cells is specified by the GeranExternalCell.UltraFlashCsfbInd parameter.

When the UE completes voice services on the E-UTRAN after the Ultra-Flash CSFB to GERAN, you can enable the Fast Return to LTE feature on the GSM side so that the UE quickly returns to the E-UTRAN. After the UE completes voice services on the GERAN, the UE carries the LTE frequency information in a Channel Release message and selects a proper LTE cell to camp on based on the frequency information to accelerate the return to the E-UTRAN.

When IratMeasCfgTransSwitch in the GlobalProcSwitch.ProtocolMsgOptSwitch parameter is set to ON, the eNodeB filters LTE frequencies supported by the UE based on the UE capability to obtain a frequency set. During the SRVCC handover, the eNodeB sends a Handover Required message containing the frequency set to the BSC of the target cell and provides reference for the UE to accelerate the return to the E-UTRAN after the UE completes voice services on the GERAN.

When the CellDrxPara.DrxForMeasSwitch parameter is set to ON(On), the eNodeB delivers the DRX and gap-assisted measurement configurations if the following conditions are met. The UE uses the DRX measurement preferentially and makes more use of DRX sleep time continuously to accelerate the measurement and decrease the delay.

The UE cannot perform the gap-assisted measurement. In this case, the AutoGapSwitch option of the ENODEBALGOSWITCH.HoModeSwitch parameter is set to OFF(Off) or the interRAT-NeedForGaps option for the GSM frequency of the UE capability is set to TRUE(True).

The gap-assisted measurement is not configured for the UE. The UE supports DRX. The BlindHoSwitch option of the ENODEBALGOSWITCH.HoModeSwitch

parameter is set to OFF(Off).

After the DRX measurement is used, you need to set longer sleep time for measurements. Therefore, the UE is easier to enter the sleep time, affecting the scheduling by decreasing the cell throughput.

For details about how to configure measurement-specific DRX troubleshooting and related parameters, see DRX and Signaling Control.

NOTE:


4.6 Handover DecisionThe handover decision for CSFB to GERAN is the same as that for CSFB to UTRAN. For details, see 3.8 Handover Decision.

4.7 Handover ExecutionWhen a UE in an LTE system needs to perform voice service but the LTE system does not support VoIP, a CSFB to an inter-RAT network is triggered.

CSFB from E-UTRAN to GERAN can be based on PS handover, CCO/NACC, redirection, or flash redirection, as shown in Figure 4-1. This handover policy selection procedure is based on the assumption that neighboring frequency and neighboring cell configurations are proper.

During a CSFB based on blind PS handover, if the target cell with the highest blind handover priority fails to prepare the handover, the eNodeB attempts another cell with the second highest blind handover priority. The eNodeB can attempt a maximum of eight cells. If all these cells fail in preparation, the eNodeB performs CSFB based on redirection.

Figure 4-1 E-UTRAN-to-GERAN handover policy selection procedure

The parameters mentioned in the preceding figure are described as follows:

The timer length is specified by the CSFallBackHo.CsfbProtectionTimer parameter. If the UE stays in the area covered by the eNodeB before the timer expires, the eNodeB performs the CSFB based on the blind redirection,

o The eNodeB preferentially selects a system that the UE has not measured. For example, if the UE has measured the UTRAN, the eNodeB preferentially selects the GERAN for redirection.

o If there is not target frequency available for redirection, the eNodeB stops the procedure.

The BlindHoSwitch switch under the ENodeBAlgoSwitch.HoModeSwitch parameter and the BlindHoSwitch switch under the CELLHOPARACFG.HoModeSwitch parameter specify whether to enable blind handover. The CSFB blind handover is triggered only when eNodeB- and cell-level blind handover switches are enabled.

The adaptive-blind-handover-based CSFB switch is controlled by the CsfbAdaptiveBlindHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter.

The CSFB policy switches are controlled by the options of the ENodeBAlgoSwitch.HoModeSwitch parameter:

o The PS handover supporting capability is specified by GeranPsHoSwitch.o The CCO supporting capability is specified by GeranCcoSwitch.o The NACC supporting capability is specified by GeranNaccSwitch.

When CSFB to GERAN is based on CCO/NACC, the eNodeB obtains SI of external cells from RNCs through the RIM procedure. For details about the RIM procedure, see 4.8 RIM Procedure Between E-UTRAN and GERAN.

The CSFB policy is specified by different parameters, depending on whether LOFD-001089 CS Fallback Steering to GERAN is enabled.

If this feature is enabled:

o The CSFB policy for UEs in idle mode is specified by the CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg parameter.

o The CSFB policy for UEs in connected mode is specified by the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter.

If this feature is not enabled, the CSFB policy is specified by the CSFallBackPolicyCfg.CsfbHoPolicyCfg parameter, regardless of whether UEs are in idle or connected mode.

4.8 RIM Procedure Between E-UTRAN and GERANThe principles of the RIM procedure between E-UTRAN and GERAN are the same as those for UTRAN described in 3.10 RIM Procedure Between E-UTRAN and UTRAN.

The RIM procedure between E-UTRAN and GERAN is enabled by default because there is no switch for selecting a load information transfer channel.

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is performed through the core network. If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is performed through the eCoordinator. The two RIM procedures select information exchange modes in the same way.

Figure 4-2 shows the procedure of information exchange mode selection for the RIM procedure.

The preceding figure is described as follows: The RIM procedure between EUTRAN and GERAN is controlled by the GERAN_RIM_SWITCH option of the ENodeBAlgoSwitch.RimSwitch parameter.

If this option is selected, the eNodeB uses the RIM procedure in Multiple Report mode to obtain the system information of external GERAN cells.

If external GERAN cells do not support the Multiple Report mode, they do not notify the eNodeB of any system information change after the initial request.

Figure 4-2 Information exchange mode selection for the RIM procedure

4.9 CSFB to GERAN


The combined EPS/IMSI attach procedure for CSFB to GERAN is the same as that for CSFB to UTRAN. For details, see 3.11.1 Combined EPS/IMSI Attach Procedure.


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

Call procedure

Figure 4-3 shows the procedure for CSFB to GERAN based on PS handover for mobile-originated calls.

Figure 4-3 CSFB to GERAN based on PS handover for mobile-originated calls

The procedure is described as follows:

1. The UE sends the MME a NAS message Extended service request to initiate a CS service.

2. The MME instructs the eNodeB to initiate a CSFB procedure. If the MME supports the LAI-related feature, the MME also delivers the LAI to the eNodeB.

3. The eNodeB determines whether to perform blind handover based on the UE capabilities, parameters settings, and algorithm policies.

4. The eNodeB initiates the preparation phase for a PS handover. If the preparation is successful, the eNodeB instructs the UE to perform a handover. If the GERAN or UE does not support DTM, the ongoing PS services of the UE are suspended, and the SGSN update bearers with the S-GW/P-GW.

NOTE:


5. After the handover, the UE may initiate a CS call establishment procedure with an LAU or combined RAU/LAU procedure in the GERAN.

6. The follow-up procedures are performed for the PS handover. These procedures include data forwarding, path switching, and RAU, which are performed together with step 5.


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

4.9.3 CSFB Based on CCO/NACC

During CSFB based on CCO/NACC, the eNodeB receives a CS Fallback Indicator from the MME, and then it sends a Mobility From EUTRA Command message to the UE over the Uu interface. The message contains information about the operating frequency, ID, and system information of a target GERAN cell. The UE searches for a target cell based on the information it received, and then it performs initial access to the cell to initiate a CS service. It then initiates a CS service in the GERAN.

Call procedure

Figure 4-4 shows the procedure for CSFB to GERAN based on CCO/NACC for mobile-originated calls.

Figure 4-4 CSFB to GERAN based on CCO/NACC for mobile-originated calls




4. The eNodeB sends a Mobility From EUTRA Command message over the Uu interface to indicate the operating frequency and ID of the target GERAN cell. If the source cell has the system information of the target cell, the system information is also carried in the message.

NOTE:


5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target cell.

6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are suspended.

7. The UE initiates a CS call establishment procedure in the target GERAN cell.8. The eNodeB initiates an S1-based UE context release procedure.


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

4.9.4 CSFB Based on Redirection

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

CSFB Procedure for Mobile-Originated Calls

Figure 4-5 shows the procedure for CSFB to GERAN based on redirection for mobile-originated calls.

Figure 4-5 CSFB to GERAN based on redirection for mobile-originated calls

The procedure is described as follows:

1. The UE sends the MME a NAS message Extended service request to initiate a CS service.


3. The eNodeB determines whether to perform blind handover based on the UE capabilities, parameters settings, and algorithm policies.

4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target GERAN frequency. Then, the eNodeB initiates an S1 UE context release procedure.

NOTE:



6. If the GERAN or UE does not support DTM, the ongoing PS services of the UE are suspended.

7. The UE initiates a CS call establishment procedure in the target GERAN cell.


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

4.9.5 Flash CSFB

During the flash CSFB procedure, the eNodeB receives a CS Fallback Indicator, and then it sends an RRC Connection Release message to release the UE. The message contains information about a target UTRAN frequency, as well as one or more physical cell identities and their associated system information. In this way, the UE can quickly access the target UTRAN without the need to perform the procedure for acquiring system information of the target UTRAN cell. Then, the UE can directly initiate a CS service in the UTRAN cell. It then initiates a CS service in the GERAN.

Because flash CSFB complies with 3GPP Release 9, the networks and UEs involved must support 3GPP Release 9 or later.

Call procedure

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

Figure 4-6 CSFB to GERAN based on flash redirection for mobile-originated calls



3. The eNodeB determines whether to perform a blind redirection based on the UE capabilities, parameters settings, and algorithm policies.

4. The eNodeB sends an RRC Connection Release message to instruct the UE to perform a redirection. The message contains information about a target GERAN carrier frequency group, as well as one or more physical cell identities and their associated system information. Then, the eNodeB initiates an S1 UE context release procedure.

NOTE:

For details about how the eNodeB selects a target cell and a CSFB policy, see 4.6 Handover Decision and 4.7 Handover Execution. The system information of the target cell is acquired during the RIM procedure.

5. The UE initiates an LAU, a combined RAU/LAU, or both an RAU and an LAU in the target cell.

6. If DTM is not supported by the UE or GERAN, the ongoing PS services of the UE are suspended.

7. The UE initiates a CS call establishment procedure in the target GERAN cell.


In a mobile-terminated call, the MSC sends a Paging request message from the CS domain to the MME over the SGs interface. Then, the MME or eNodeB initiates a paging procedure for the UE. The paging procedure is similar to that for UTRAN described in 3.11.2 CSFB Based on PS Handover. The subsequent steps are the same as the steps in the procedure for CSFB to GERAN based on CCO/NACC for mobile-originated calls.

4.9.6 Ultra-Flash CSFB to GERAN

Ultra-Flash CSFB to GERAN is a Huawei-proprietary procedure. To enable this feature, the MSC, MME, and eNodeB must all be provided by Huawei and support this feature. Resources are prepared in advance on the GERAN using the SRVCC, and authentication and encryption procedures are excluded to reduce delays. The following figures show Ultra-Flash CSFB to GERAN of mobile-originated calls and mobile-terminated calls, respectively.

Figure 4-7 Ultra-flash CSFB to GERAN for mobile-originated calls

Figure 4-8 Ultra-flash CSFB to GERAN for mobile-terminated calls

Steps 1 to 3a: The UE initiates voice services (mobile-originated calls and mobile-terminated calls) on the E-UTRAN. The eNodeB triggers SRVCC to GERAN. The MME and MSC guarantees the proper procedure through special processing.

Step 3b: The BSC receives an SRVCC request and prepares CS resources.

Step 4: The eNodeB receives the handover command transferred over the core network and sends it to the UE.

Step 5: The UE is transferred to the GERAN.

Steps 6 to 9: The UE establishes voice services on the GERAN. Signaling is carried on the TCH, which accelerates the transfer and reduces delays.

As shown in the preceding figures, Ultra-Flash CSFB to GERAN excludes the following procedures:

Authentication procedure

The UE has been authenticated in the LTE system before CSFB to GERAN.

Ciphering procedure

The UE has performed ciphering as instructed during SRVCC. Therefore, the encryption procedure is not required after the UE is transferred to the GERAN.

IMEI query procedure

The MME has sent the IMEI to the MSC during the preparation for SRVCC. There, the procedure is not required in the GERAN after SRVCC.

CS resource setup procedure

The GSM system has prepared CS resources during SRVCC and therefore the UE does not need to reestablish the CS resource after SRVCC. There, the procedure is not required in the GERAN after SRVCC.

When the UE completes voice services in the GERAN after the Ultra-Flash CSFB to GERAN, you can enable the Fast Return to LTE feature on the GERAN side so that the UE quickly returns to the E-UTRAN. After the UE completes voice services in the GERAN, the UE carries the LTE frequency information in a Channel Release message and selects a proper LTE cell to camp on based on the frequency information to accelerate the return to the E-UTRAN.

When IratMeasCfgTransSwitch is set to ON, the eNodeB filters LTE frequencies supported by the UE based on the UE capability to obtain a frequency set. During the SRVCC, the eNodeB sends a Handover Required message containing the frequency set to the BSC of the target cell and provides reference for the UE to accelerate the return to the E-UTRAN after the UE completes voice services on the GERAN.

4.9.7 CSFB for SMS

SMS services are unknown to the eNodeB because SMS messages are encapsulated in NAS messages. During interworking with the GERAN, SMS messages are exchanged between the MME and the MSC over the SGs interface. Because a UE does not require fallback to the GERAN to perform an SMS service, the SMS over SGs function can be used in a place covered only by the E-UTRAN.

As the SMS service is transparent to the eNodeB, the procedure is not described in this document. For details about the procedure, see section 8.2 in 3GPP TS 23.272 V10.0.0.


The CSFB procedure for an emergency call is the same as the CSFB procedure for a normal mobile-originated voice service. The UE sends an RRC Connection Request message over the Uu interface or the MME sends an Initial Context Setup Request or UE Context Modification Request message, which contains an IE to inform the eNodeB of the service type. Emergency calls take precedence over other services in the eNodeB.

If PS handover is used for CSFB for emergency calls, the eNodeB does not restrict the cells in the handover restriction list when selecting the target cell.

If redirection is used for CSFB for emergency calls, the Channel Request message that the UE sends when accessing the GERAN contains the indication of a CS emergency call.

The GERAN will treat this call as a common CS emergency call. For details about admission and preemption of emergency calls, see Emergency Call.

4.9.9 CSFB for LCS

After a UE initiates an LCS request, the MME performs an attach or combined TAU/LAU procedure to inform the UE of the LCS capability of the EPS. If the EPS does not support LCS, the UE falls back to the GERAN to initiate LCS under the control of the EPS. The CSFB procedure is the same as the procedure for CSFB to GERAN for mobile-originated calls.

If the GERAN initiates an LCS request towards a UE camping on an E-UTRAN cell, the MSC sends an LCS indicator to the MME over the SGs interface. Then, the MME instructs the eNodeB to perform CSFB for the UE. The CSFB procedure is the same as the procedure for CSFB to GERAN for mobile-terminated calls. The UE performs the LCS service after the fallback to the GERAN.

For details about the CSFB procedure for LCS, see section 8.3 in 3GPP TS 23.272 V10.0.0 and LCS.

5 Related Features5.1 Features Related to LOFD-001033 CS Fallback to UTRAN

Prerequisite Features

This feature requires the optional feature LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN.

Mutually Exclusive Features

None

Impacted Features

When a UE initiates a CSFB request, the eNodeB cannot determine whether the target inter-RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN, according to 3GPP Release 9. Therefore, it is not recommended that CSFB to GERAN/UTRAN be enabled together with CSFB to CDMA2000 1xRTT. In addition, it is not recommended that this feature be enabled together with either of the following features:

LOFD-001035 CS Fallback to CDMA2000 1xRTT LOFD-001090 Enhanced CS Fallback to CDMA2000 1xRTT

If both CSFB to UTRAN and CSFB to CDMA2000 are enabled, the eNodeB attempts CSFB to UTRAN first. If the attempt fails, the eNodeB attempts CSFB to CDMA2000.

5.2 Features Related to LOFD-001052 Flash CS Fallback to UTRAN


This feature requires LOFD-001033 CS Fallback to UTRAN.


When a UE initiates a CSFB request, the eNodeB cannot determine, according to 3GPP Release 9 specifications, whether the target inter-RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN. Therefore, CSFB to GERAN/UTRAN cannot be enabled together with CSFB to CDMA2000 1xRTT. This feature does not work with the following features:


Impacted Features

None

5.3 Features Related to LOFD-070202 Ultra-Flash CSFB to UTRAN


This feature depends on the optional feature LOFD-001033 CS Fallback to UTRAN.


None

Impacted Features

None

5.4 Features Related to LOFD-001068 CS Fallback with LAI to UTRAN


This feature requires LOFD-001033 CS Fallback to UTRAN.




Impacted Features

None

5.5 Features Related to LOFD-001088 CS Fallback Steering to UTRAN


This feature requires LOFD-001033 CS Fallback to UTRAN and LOFD-001078 E-UTRAN to UTRAN CS/PS Steering.




Impacted Features

This feature affects LOFD-001089 CS Fallback Steering to GERAN. In overlapping coverage of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to UTRAN and

LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously, achieve CSFB steering to different RATs.

5.6 Features Related to LOFD-001078 E-UTRAN to UTRAN CS/PS Steering

Required Features

This feature requires LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN or LOFD-001033 CS Fallback to UTRAN.


None

Affected Features

None

5.7 Features Related to LOFD-001034 CS Fallback to GERAN


This feature requires LOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.


None

Impacted Features

When a UE initiates a CSFB request, the eNodeB cannot determine whether the target inter-RAT network is a CDMA2000 1xRTT network or a GERAN/UTRAN, according to 3GPP Release 9. Therefore, it is not recommended that CSFB to GERAN/UTRAN be enabled together with CSFB to CDMA2000 1xRTT. In addition, it is not recommended that this feature be enabled together with either of the following features:


If both CSFB to GERAN and CSFB to CDMA2000 are enabled, the eNodeB attempts CSFB to GERAN first. If the attempt fails, the eNodeB attempts CSFB to CDMA2000.

5.8 Features Related to LOFD-001053 Flash CS Fallback to GERAN


This feature requires LOFD-001034 CS Fallback to GERAN.




Impacted Features

None

5.9 Feature Related to LOFD-081283 Ultra-Flash CSFB to GERAN


This feature requires the optional feature LOFD-001034 CS Fallback to GERAN.


None

Impacted Features

None

5.10 Features Related to LOFD-001069 CS Fallback with LAI to GERAN






Impacted Features

None

5.11 Features Related to LOFD-001089 CS Fallback Steering to GERAN






Impacted Features

This feature affects LOFD-001088 CS Fallback Steering to UTRAN. In overlapping coverage of GSM, UMTS, and LTE networks, LOFD-001088 CS Fallback Steering to UTRAN and LOFD-001089 CS Fallback Steering to GERAN, if enabled simultaneously, achieve CSFB steering to different RATs.

6 Network Impact6.1 LOFD-001033 CS Fallback to UTRAN

System Capacity

In essence, CSFB provides CS service access for E-UTRAN UEs. Considering that the number of UEs that request CS services within an area is relatively stable and is not affected

by EPS deployment, CSFB has no impact on the total number of UEs that request CS services within a network.

Load-based CSFB to UTRAN prevents PS handover preparation failure caused by UTRAN cell congestion, because the eNodeB selects a target cell based on the UTRAN cell load status. This increases system capacity.

CSFB mechanisms affect signaling overhead as follows:

If redirection is used as the CSFB mechanism, no extra signaling message is required for the UTRAN because each CSFB procedure is equivalent to the initiation of a new CS service. The EPS does not need to interact with the target network, and the corresponding signaling overhead is negligible.

If PS handover is used as the CSFB mechanism, extra signaling messages are required from each NE for the request, preparation, and execution of each handover. However, from the perspective of traffic statistics, the number of UEs that initiate CS services per second per cell during peak hours is far below cell capacity. Therefore, signaling overhead caused by PS handovers is low.

Network Performance

Load-based CSFB to UTRAN prevents PS handover preparation failure caused by UTRAN cell congestion, because the eNodeB selects a target cell based on the UTRAN cell load status. This increase the CSFB delay.

CSFB affects the access success rate as follows:

CSFB affects the access success rate as follows: If redirection is used as the CSFB mechanism, each CSFB procedure is equivalent to the initiation of a new CS service. Therefore, the access success rate for CSFB UEs is theoretically the same as that for normal CS UEs in the UTRAN.

If PS handover is used as the CSFB mechanism, the access success rate for CSFB UEs depends on the success rate of handovers to the target RAT. Handover-triggered CS service access has a higher requirement for signal quality compared with normal CS service access. Therefore, the access success rate for CSFB UEs is a little lower than that for normal CS UEs in the UTRAN.


System Capacity

In essence, CSFB provides CS service access for E-UTRAN UEs. Considering that the number of UEs that request CS services within an area is relatively stable and is not affected by EPS deployment, CSFB has no impact on the total number of UEs that request CS services within a network.

Extra signaling messages are required only during eNodeB deployment.

Afterward, signaling overhead is negligible because of infrequent system information updates.

Network Performance

Flash CSFB to UTRAN decreases the CSFB delay by up to 1.28s because UEs obtain information about the target UTRAN cell for redirection before RRC connections to the LTE network are released.

Flash CSFB affects the access success rate as follows:

Each flash CSFB procedure is equivalent to the initiation of a new CS service. Therefore, the access success rate for CSFB UEs is theoretically the same as that for normal CS UEs in the UTRAN.

The RRC connection setup success rate may decrease slightly for the UTRAN. The uplink interference information contained in SIB7 in the UTRAN updates frequently. The RNC cannot update the uplink interference information in the system information sent to the LTE network based on SIB7 in the UTRAN. Therefore, the uplink interference information contained in SIB7 in the LTE network is a default value (–105 dBm). If the actual uplink interference in the UTRAN is greater than –105 dBm, the transmit power on UEs' physical random access channel (PRACH) increases and the RRC connection setup success rate may decrease.


System Capacity

Non impact.

Network Performance

Compared with standard CSFB, this feature reduces the delay of CSFB to UTRAN by 1 second, improving user experience.


System Capacity

No impact.

Network Performance

CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has attached. This prevents CSFB failure or long delay caused by incorrect target RAT selection and increases the CSFB success rate.


System Capacity

No impact.

Network Performance

Using this feature, an operator that owns inter-RAT networks can specify the target RAT and frequency for CSFB based on the network plan and network load balancing requirements and thereby improve network operating efficiency.

If the frequency with the highest priority is inappropriately configured, for example, if the highest-priority frequency has coverage holes, a UE may fail to measure this frequency and therefore the CSFB delay increases.

This feature may conflict with the service-based directed retry decision (DRD) algorithm used for UTRAN, thereby affecting user experience. For example, if a CS service is initiated for a UE that is performing PS services, the eNodeB may select a High Speed Packet Access (HSPA) frequency used in UTRAN for CSFB based on configured policies. However, if the UE requests CS bearer establishment first after the fallback, the UTRAN may transfer the UE to an R99 frequency.


System Capacity

No impact.

Network Performance

E-UTRAN to UTRAN CS/PS Steering enables an eNodeB to include only UTRAN frequencies with a high CS service priority in measurement configurations. This prevents redundant measurements, reduces the measurement time, and decreases end-to-end CSFB delay.

If the CS service priorities of UTRAN frequencies configured on the eNodeB are consistent with those configured at the UTRAN side, E-UTRAN to UTRAN CS/PS Steering prevents further intra-UTRAN handovers for service steering.


System Capacity


CSFB mechanisms affect signaling overhead as follows:

CSFB mechanisms affect signaling overhead as follows: If redirection or CCO without NACC is used as the CSFB mechanism, no extra signaling message is required for the GERAN because each CSFB procedure is equivalent to the initiation of a new CS service. The EPS does not need to interact with the target network. Therefore, signaling overhead is negligible.

If CCO with NACC is used as the CSFB mechanism, extra signaling messages are required only during eNodeB deployment.

Afterward, signaling overhead is negligible because of infrequent system information updates. If PS handover is used as the CSFB mechanism, extra signaling messages are required from each NE for the request, preparation, and execution of each handover. However, from the perspective of traffic statistics, the number of UEs that initiate CS services per second per cell during peak hours is far below cell capacity. Therefore, signaling overhead caused by PS handovers is low.

Network Performance

CSFB affects the access success rate as follows:

If redirection or CCO/NACC is used as the CSFB mechanism, each CSFB procedure is equivalent to the initiation of a new CS service. Therefore, the access success rate for CSFB UEs is theoretically the same as that for normal CS UEs in the GERAN.

If PS handover is used as the CSFB mechanism, the access success rate for CSFB UEs depends on the success rate of handovers to the target RAT. Handover-triggered CS service access has a higher requirement for signal quality compared with normal CS service access. Therefore, the access success rate for CSFB UEs is a little lower than that for normal UEs in the GERAN.


System Capacity


CSFB mechanisms affect signaling overhead as follows: Flash CSFB affects signaling overhead as follows: Extra signaling messages are required only during eNodeB deployment. Afterward, signaling overhead is negligible because of infrequent system information updates.

Network Performance

If flash CSFB is used as the CSFB mechanism, each CSFB procedure is equivalent to the initiation of a new CS service. Therefore, the access success rate for CSFB UEs is theoretically the same as that for normal CS UEs in the GERAN.

Flash CSFB to GERAN decreases the CSFB delay by up to 2s because UEs obtain information about the target GERAN cell for redirection before RRC connections to the LTE network are released.


System Capacity

When DRX measurements are used, there is a higher probability that the UE enters the DTX sleep state, affecting the scheduling by decreasing the cell throughput.

Network Performance

Compared with standard CSFB, this feature reduces the delay of CSFB to GERAN by 2 seconds, improving user experience.


System Capacity

No impact.

Network Performance

CSFB with LAI ensures that a UE can fall back to the CS network to which the UE has attached. This prevents CSFB failure or long delay caused by incorrect target RAT selection and increases the CSFB success rate.


System Capacity

No impact.

Network Performance

Using this feature, an operator that owns inter-RAT networks can specify the target RAT and frequency for CSFB based on the network plan and network load balancing requirements and thereby improve network operating efficiency.

If the frequency with the highest priority is inappropriately configured, for example, if the highest-priority frequency has coverage holes, a UE may fail to measure this frequency and therefore the CSFB delay increases.

7 Engineering Guidelines

7.1 LOFD-001033 CS Fallback to UTRANThis section provides engineering guidelines for LOFD-001033 CS Fallback to UTRAN.

7.1.1 When to Use CS Fallback to UTRAN

Use LOFD-001033 CS Fallback to UTRAN in the initial phase of LTE network deployment when both of the following conditions are met:

The operator owns a mature UTRAN network. The LTE network does not provide VoIP services, or UEs in the LTE network do not

support VoIP services.

For policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT Mobility Management in Connected Mode. If UTRAN and E-UTRAN cells cover the same area, or the UTRAN cell provides better coverage than the E-UTRAN cell, use CSFB based on blind handover to decrease the CSFB delay.


1. Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and UTRAN cells. Information about coverage areas includes engineering parameters of sites (such as latitude and longitude), TX power of cell reference signals (RSs), and neighbor relationship configurations.

2. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks, and ensure that they all support CSFB. Table 7-1 describes the requirements of CSFB to UTRAN for the core networks.

3. Collect the following information about the UEs that support UMTS and LTE on the live network:

o Supported frequency bandso Whether the UEs support redirection from E-UTRAN to UTRANo Whether the UEs support PS handover from E-UTRAN to UTRANo Whether the UEs support UTRAN measurements

This information is used to configure neighboring UTRAN cells and to determine whether to perform CSFB based on handover or redirection. For details, see Inter-RAT Mobility Management in Connected Mode.

4. Collect information about the RNC, MME, and SGSN to check whether they all support RIM procedures.

Table 7-1 Requirements of CSFB to UTRAN for core networksNE Requirement

MME Supports: SGs interface to the MSC

LAI selection based on the TAI of the serving cell

NE Requirement

MSC-initiated paging

PLMN selection and reselection

Combined EPS/IMSI attach, combined EPS/IMSI detach, and combined TAU/LAU

CS signaling message routing

SMS over SGs

MSC Supports: Combined EPS/IMSI attach

SMS over SGs

Paging message forwarding over the SGs interface

SGSN Does not activate ISR during the combined RAU/LAU procedure initiated by the UE.

7.1.3 Requirements

Operating Environment

For CSFB to UTRAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be SAE1.2 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 CSFB to UTRAN.

License

The operator has purchased and activated the license for the feature listed in Table 7-2.

Table 7-2 License control item for CSFB to UTRANFeature ID Feature

NameModel License

Control ItemNE Sales Unit

LOFD-001033 CSFB to UTRAN

LT1S00CFBU00 CS Fallback to UTRAN(FDD)

eNodeB per RRC Connected User

7.1.4 Precautions

None



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 not required): parameter values planned and set by the operator

Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment

User-defined: parameter values set by users

Required Data

Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with UTRAN cells. This section provides only the information about 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:

1. UtranNFreq: used to configure neighboring UTRAN frequencies2. UtranExternalCell: used to configure external UTRAN cells. The

UtranExternalCell.Rac parameter must be set.3. UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared

external UTRAN cell. This MO is required only if the NodeB that provides the external UTRAN cell works in RAN sharing with common carriers mode and multiple operators share the external UTRAN cell.

4. The following table describes the parameters that must be set in the UtranNCell MO to configure the neighboring relationship with a UTRAN cell. If a neighboring UTRAN cell supports blind handovers according to the network plan, the blind-handover priority of the cell must be specified by the UtranNCell.BlindHoPriority parameter.

Scenario-specific Data

The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the eNodeB-level handover mode and handover algorithm switches for CSFB to UTRAN.

Parameter Name

Parameter ID Data Source

Setting Notes

Handover Mode switch

ENodeBAlgoSwitch.HoModeSwitch

Network plan (negotiation not

Set this parameter based on the network plan.

To activate PS handovers, select

Parameter Name


Setting Notes

required)the UtranPsHoSwitch(UtranPsHoSwitch) check box. If this check box is not selected, redirection will be used for CSFB to UTRAN.

Handover Algo switch

ENodeBAlgoSwitch.HoAlgoSwitch

Network plan (negotiation not required)

To activate CSFB to UTRAN, select the UtranCsfbSwitch(UtranCsfbSwitch) check box.

To activate load-based CSFB, select the CSFBLoadInfoSwitch check box.

The following table describes the parameters that must be set in the ENodeBAlgoSwitch and CellHoParaCfg MOs to set eNodeB- and cell-level blind handovers.

Parameter Name


Setting Notes




To activate blind handovers, select the BlindHoSwitch(BlindHoSwitch) check box under the parameter. If the BlindHoSwitch(BlindHoSwitch) check box is deselected, blind handovers for all cells under the eNodeB are invalid.


CellHoParaCfg.HoModeSwitch Network plan (negotiation not required)

To activate blind handovers for a cell under the eNodeB, select the BlindHoSwitch(BlindHoSwitch) check box under the parameter. If the BlindHoSwitch(BlindHoSwitch) check box is deselected, blind handovers for the cell are invalid.

The following table describes the parameters that must be set in the CSFallBackBlindHoCfg MO to set the blind-handover priorities of different RATs for CSFB.

Parameter Name


Setting Notes

CN Operator ID

CSFallBackBlindHoCfg.CnOperatorId Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter identifies the operator whose RAT blind-handover priorities are to be set.

Highest priority InterRat

CSFallBackBlindHoCfg.InterRatHighestPri


Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the highest-priority RAT to be considered in blind handovers for CSFB. For CSFB to UTRAN, retain the default value.

Second priority InterRat

CSFallBackBlindHoCfg.InterRatSecondPri


Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.

Lowest priority InterRat

CSFallBackBlindHoCfg.InterRatLowestPri


Set this parameter based on the network plan. This parameter is set to CDMA2000 by default and

Parameter Name


Setting Notes

specifies the low-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatSecondPri parameters.

UTRAN LCS capability

CSFallBackBlindHoCfg.UtranLcsCap Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the LCS capability of the UTRAN.

The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to activate load-based CSFB.

Parameter Name


Setting Notes




To activate load-based CSFB, select the CSFBLoadInfoSwitch(CSFBLoadInfoSwitch) check box.

The following table describes the parameter that must be set in the GlobalProcSwitch MO to set load-based CSFB to UTRAN.

Parameter Name


Setting Notes

Choose UTRAN Cell Load Info Trans Channel

GlobalProcSwitch.UtranLoadTransChan Network plan (negotiation not required)

Set this parameter to BASED_ON_RIM to enable UTRAN cell load information acquisition through RIM if the RNC, MME, and SGSN

Parameter Name


Setting Notes

support RIM.

The following table describes the parameter that must be set in the CSFallBackHo MO to set the CSFB protection timer.

Parameter Name


Setting Notes

CSFB Protection Timer

CSFallBackHo.CsfbProtectionTimer Network plan (negotiation not required)

Set this parameter based on the network plan. The default value 4 applies to a GSM+UMTS+LTE network. The value 2 is recommended for a UMTS+LTE network. If this parameter is set too large, the CSFB delay increases in abnormal CSFB scenarios. If this parameter is set too small, normal measurement or handover procedures may be interrupted.

The following table describes the parameter that must be set in the InterRatHoComm MO to set the maximum number of neighboring UTRAN cells whose system information is sent to UEs for emergency redirections.

Parameter Name


Setting Notes

Max Utran cell num in CSFB EMC redirection

InterRatHoComm.UtranCellNumForEmcRedirect


The default value is 0, indicating that no system information of any neighboring UTRAN cells is sent to UEs for emergency redirections

Parameter Name


Setting Notes

. Operators can set this parameter to 0 through 16 based on the network plan. After the CSFB protection timer expires, the eNodeB performs an emergency redirection. If the signal quality of the serving cell is poor and this parameter is set to a large value, the eNodeB may fail to send the system information of neighboring UTRAN cells to UEs.

The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO to specify the CSFB policy.

Parameter Name


Setting Notes

CSFB handover policy Configuration

CSFallBackPolicyCfg.CsfbHoPolicyCfg Network plan (negotiation not required)

Set this parameter based on the network plan. The default values are REDIRECTION, CCO_HO, and PS_HO. You are

Parameter Name


Setting Notes

advised to set this parameter based on the UE capabilities and network capabilities.

NOTE:

If none of the three options is selected and measurement-based mobility is enabled, the eNodeB does not perform CSFB for a UE until the CSFB protection timer expires. Then the eNodeB performs a blind redirection for the UE. If blind handover is enabled, the eNodeB directly performs a blind redirection for the UE.

CCO_HO applies only to CSFB to GERAN.

The following table describes the parameter that must be set in the CSFALLBACKBLINDHOCFG MO to set the round-robin switch when multiple frequencies are of the same priority for CSFB-based blind redirections.

Parameter Name


Setting Notes

CSFB to UTRAN Blind Redirection RR Switch

UtranCsfbBlindRedirRrSw Network plan (negotiation not required)

Set this parameter based on the network plan. The option is cleared by default. When the UE needs to perform a blind redirection and multiple frequencies are of the same priority, the option can be selected

Parameter Name


Setting Notes

to ensure that the UE accesses each frequency equally. In addition, you are advised to plan neighboring cells on the frequencies and neighboring frequencies, and neighboring cell priorities before selecting the option.

The following table describes the parameter that must be set in the ENBRSVDPARA MO to set the random procedure selection optimization for CSFB.

Parameter Name


Setting Notes

Reserved Switch Parameter 1

ENBRSVDPARA.RsvdSwPara1 Network plan (negotiation not required)

Select the RsvdSwPara1_bit23 option when CSFB selects a target frequency or cell to enter the random selection procedure. This ensures that each frequency or cell is selected evenly.


Enter the values of the parameters listed in Table 7-3 in a summary data file, which also contains other data for the new eNodeBs to be deployed.

Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see 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 managed objects (MOs) in Table 7-3 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.

Some MOs in Table 7-3 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.

When configuring neighboring cells, you are advised to use the radio data planning file. For details about how to fill in and export the radio data planning file, see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.

Table 7-3 Parameters for CSFB to UTRAN

MO Sheet in the Summary Data File

Parameter Group

Remarks

UtranNFreq UtranNFreq See 7.1.5.1 Data Preparation.

The RNP template sheet is recommended.

UtranExternalCell UtranExternalCell See 7.1.5.1 Data Preparation.


UtranExternalCellPlmn UtranExternalCellPlmn See 7.1.5.1 Data Preparation.


UtranNCell UtranNCell See 7.1.5.1 Data Preparation.


ENodeBAlgoSwitch User-defined sheet. ENodeBAlgoSwitch is recommended.

See 7.1.5.1 Data Preparation.

This parameter must be customized on a list-type sheet of the template.

CSFallBackBlindHoCfg User-defined sheet. CSFallBackBlindHoCfg is recommended.



CellHoParaCfg User-defined sheet. CellHoParaCfg is recommended.



CSFallBackHo User-defined sheet. CSFallBackHo is recommended.



InterRatHoComm User-defined sheet. InterRatHoComm is recommended.


None


Batch Activated

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

Batch Reconfiguration

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure.

1. Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration.

2. Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file.

3. In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file.

4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME.

5. After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help.


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 (U2000 client mode),

or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.


Using MML Commands

Basic scenario 1: CSFB to UTRAN using blind redirection

CSFB to UTRAN using blind redirection works regardless of whether neighboring UTRAN cells are configured.

If you want to configure a neighboring UTRAN cell, you must configure the UtranNFreq and UtranNCell MOs. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

If you do not want to configure a neighboring UTRAN cell, you must configure the UtranRanShare or UtranExternalCell MO. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

1. Run the MOD ENODEBALGOSWITCH command with the UtranCsfbSwitch(UtranCsfbSwitch) option of the Handover Algo switch parameter selected.

2. Run the following eNodeB- and cell-level commands to enable blind handovers for CSFB to UTRAN:

a. Run the MOD ENODEBALGOSWITCH command with the BlindHoSwitch(BlindHoSwitch) option of the Handover Mode switch parameter selected.

b. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the Handover Mode switch parameter selected.

3. Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO options of the CSFB handover policy Configuration parameter deselected and the REDIRECTION option of the same parameter selected.

4. (Optional) If you require setting UTRAN as having the highest priority for CSFB, run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat parameter set to UTRAN and the Second priority InterRat parameter set to GERAN.

5. (Optional) If a neighboring UTRAN cell is configured, run the MOD UTRANNCELL command with the Blind handover priority parameter set to the highest priority (32).

6. (Optional) If no neighboring UTRAN cell is configured, run the MOD UTRANNFREQ command with the Frequency Priority for Connected Mode parameter set to the highest priority (8).

7. (Optional) Run the MOD CSFALLBACKBLINDHOCFG command to turn on the CSFB to UTRAN blind redirection RR switch.

Basic scenario 2: CSFB to UTRAN using blind handover

1. Add neighboring UTRAN frequencies and neighbor relationships with UTRAN cells. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.


3. Run the following eNodeB- and cell-level commands to enable blind handovers for CSFB to UTRAN:


b. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the Handover Mode switch parameter selected.

4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the CSFB handover policy Configuration parameter selected.

5. Run the MOD UTRANNCELL command with the Blind handover priority parameter set to 32.

Basic scenario 3: CSFB to UTRAN using measurement-based redirection



3. Run the MOD CELLHOPARACFG command with the BlindHoSwitch option of the Handover Mode switch parameter deselected for the cells to be measured.

4. Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO options of the CSFB handover policy Configuration parameter deselected and the REDIRECTION option of the same parameter selected.

Basic scenario 4: CSFB to UTRAN using measurement-based handovers


2. Run the MOD ENODEBALGOSWITCH command with the UtranCsfbSwitch(UtranCsfbSwitch) check box selected under the Handover Algo switch and the UtranPsHoSwitch(UtranPsHoSwitch) check box selected under the Handover Mode switch parameter.


4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the CSFB handover policy Configuration parameter selected.

Enhanced scenario: Load-based CSFB to UTRAN To activate load-based CSFB to UTRAN, run the following commands after the commands in a basic scenario are executed:

1. Run the MOD ENODEBALGOSWITCH command with the CSFBLoadInfoSwitch(CSFBLoadInfoSwitch) check box selected under the Handover Algo switch parameter.

2. Run the MOD GLOBALPROCSWITCH command with the Choose UTRAN Cell Load Info Trans Channel parameter set to BASED_ON_RIM.

MML Command Examples

Basic scenario 1: CSFB to UTRAN using blind redirection (configured with neighboring UTRAN cells)

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1, HoModeSwitch=BlindHoSwitch-1;MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;

MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123, BlindHoPriority=32;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;

Basic scenario 1: CSFB to UTRAN using blind redirection (configured with no neighboring UTRAN cell)

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1, HoModeSwitch=BlindHoSwitch-1;MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;MOD UTRANNFEQ: LocalCellId=0, UtranDlArfcn=9700, ConnFreqPriority=8;MOD UTRANRANSHARE: LocalCellId=0, UtranDlArfcn=9700, Mcc="460", Mnc="20";MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, UtranCsfbBlindRedirRrSw=ON;

Basic scenario 2: CSFB to UTRAN using blind handovers

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1, HoModeSwitch=UtranPsHoSwitch-1&BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-1&PS_HO-1;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN, InterRatSecondPri=GERAN;MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123, BlindHoPriority=32;

Basic scenario 3: CSFB to UTRAN using measurement-based redirection

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms, CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13, CsfbProtectionTimer=4;MOD CELLHOPARACFG: LocalCellId=1, HoModeSwitch=BlindHoSwitch-0;MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123;

Basic scenario 4: CSFB to UTRAN using measurement-based handovers

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-1&PS_HO-1;MOD CSFALLBACKHO: LocalCellId=1, CsfbHoUtranTimeToTrig=40ms, CsfbHoUtranB1ThdRscp=-106, CsfbHoUtranB1ThdEcn0=-13, CsfbProtectionTimer=4;MOD CELLHOPARACFG: LocalCellId=1, HoModeSwitch=BlindHoSwitch-0;MOD UTRANNCELL: LocalCellId=0, Mcc="460", Mnc="20", RncId=1, CellId=123;

Enhanced scenario: Load-based CSFB to UTRAN To activate load-based CSFB to UTRAN, run the following commands after the commands in a basic scenario are executed:

MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-1;MOD GLOBALPROCSWITCH: UtranLoadTransChan=BASED_ON_RIM;


Signaling Observation

The activation observation procedure for CSFB to UTRAN is as follows:

1. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that the UE falls back to a UTRAN cell and completes the call.

2. Enable a UE to camp on an E-UTRAN cell and receive a voice call so that the UE falls back to a UTRAN cell and completes the call.

The activation observation procedure for load-based CSFB to UTRAN is as follows:

Two UTRAN cells A and B report MRs and are under overload control and in the normal state, respectively. The RSCP of cell A is larger than that of cell B.

Enable a UE to perform a PS-handover-based CSFB when both cell A and cell B provides services correctly.

1. If the RSCP of cell B meets the handover requirements, the eNodeB transfers the UE to cell B.

2. If cell B is blocked and the RSCP of cell A meets the handover requirements, the eNodeB transfers the UE to cell A and the UE can access the network through preemption or queuing.

Figure 7-2 and Figure 7-3 show sample procedures for CSFB to UTRAN for a mobile-originated call and CSFB to UTRAN for a mobile-terminated call, respectively. In the examples, the UE was in idle mode before the call and is forced to fall back to the UTRAN using a redirection.

NOTE:

The same UE is shown in the left and right sides of the figure. This applies to all figures in the rest of this document. The messages on the UTRAN side are only for reference.

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

Figure 7-3 Redirection-based CSFB to UTRAN for a mobile-terminated call

If the UE capability is not included in the Initial Context Setup Request (Initial Context Setup Req in the figures) message, the eNodeB initiates a UE capability transfer procedure immediately after receiving this message from the MME. If the UE capability is included in the Initial Context Setup Request message, the eNodeB initiates a UE capability transfer procedure after sending an Initial Context Setup Response (Initial Context Setup Rsp in the figures) message to the MME.

If measurement-based redirection is used for CSFB to UTRAN, the eNodeB delivers the B1-related measurement configuration.

If blind redirection is used for CSFB to UTRAN, the eNodeB does not deliver the B1-related measurement configuration but sends an RRC Connection Release (RRC Conn Rel in the figures) message to the UE. As shown in the red and green boxes in Figure 7-4, in the RRC Connection Release message, the cause value is "other" and the target RAT is UTRAN. For an emergency call, the cause value is "CSFBhighpriority."

Figure 7-4 The RRC Connection Release message during CSFB to UTRAN

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

Figure 7-5 PS handover procedure

Figure 7-6 The MobilityFromEUTRAN message during CSFB to UTRAN

MML Command Observation

The activation observation procedure for load-based CSFB to UTRAN is as follows: Run the DSP UTRANRIMLOADINFO command to query neighboring UTRAN cell load status to check whether load-based CSFB has been activated.

If the neighboring UTRAN cell load status is displayed, load-based CSFB has been activated.

Counter Observation

Table 7-4 lists the performance counters for observing functions related to CSFB to UTRAN.

Table 7-4 Performance counters for observing CSFB to UTRANFunction Counter ID Counter Name Description

CSFB to UTRAN

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

CSFB to UTRAN triggered for emergency calls

1526728709 L.CSFB.E2W.Emergency Number of times CSFB to UTRAN is triggered for emergency calls

RIM during load-based CSFB to UTRAN

1526728949 L.RIM.Load.E2W.Req Number of load information requests sent from an eNodeB to a UMTS network

1526728950 L.RIM.Load.E2W.Resp Number of load information responses sent from a UMTS network to an eNodeB

1526728951 L.RIM.Load.E2W.Update Number of load information updates sent from a UMTS network to an eNodeB

7.1.7 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 Batch Reconfiguration. In the procedure, modify parameters according to Table 7-5.

Table 7-5 Parameters for deactivating CSFB to UTRANMO Sheet in the

Summary Data FileParameter

GroupSetting Notes


HoAlgoSwitch To deactivate CSFB to UTRAN, set UtranCsfbSwitch under the HoAlgoSwitch parameter to 0.

To deactivate only load-based CSFB to UTRAN, set CSFBLoadInfoSwitch under the HoAlgoSwitch parameter to 0.

To deactivate only adaptive-


Parameter Group

Setting Notes

blind-handover-based CSFB,

Set CsfbAdaptiveBlindHoSwitch to 0.

Using the CME to Perform Single Configuration

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

Using MML Commands

Deactivating CSFB to UTRAN

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

Deactivating only load-based CSFB to UTRAN

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

Deactivating adaptive-blind-handover-based CSFB

Run the MOD ENODEBALGOSWITCH command to with the CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlindHoSwitch) option of the Handover Algo switch parameter cleared.


Deactivating CSFB to UTRAN

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSwitch-0;

Deactivating only load-based CSFB to UTRAN

MOD ENODEBALGOSWITCH: HoAlgoSwitch=CSFBLoadInfoSwitch-0;

Deactivating adaptive-blind-handover-based CSFB

MOD ENODEBALGOSWITCH: HoAlgoSwitch=CsfbAdaptiveBlindHoSwitch-0;


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

Related counters are listed in Table 7-6.

Table 7-6 Counters related to the execution of CSFB by the eNodeBCounter ID Counter Name Description

1526728321 L.CSFB.PrepAtt Number of CSFB indicators received by the eNodeB

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

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

Table 7-7 Counter related to CSFB to UTRANCounter ID Counter Name Description

1526728323 L.CSFB.E2W Number of procedures for CSFB to WCDMA network

Table 7-8 lists the counters that indicate whether CSFB is performed through redirection or through handover.

Table 7-8 Counters related to CSFB through redirection or handoverCounter ID Counter Name Description

1526728497 L.RRCRedirection.E2W.CSFB Number of CSFB-based redirections from E-UTRANs to WCDMA network

1526728504 L.IRATHO.E2W.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover preparation attempts from E-UTRAN to WCDMA network

After the CSFB protection timer expires, the eNodeB may perform a blind redirection to enter the protection procedure. Table 7-9 lists the counter related to the number of times that the eNodeB enters the protection procedure for CSFB. A larger value of this counter indicates a longer average UE access delay during CSFB.

Table 7-9 Counter related to the number of times that the eNodeB enters the protection procedure for CSFBCounter ID Counter Name Description

1526729515 L.RRCRedirection.E2W.CSFB.TimeOut Number of CSFB-based blind

Counter ID Counter Name Description

redirections from E-UTRAN to WCDMA network caused by CSFB protection timer expiration

Table 7-10 lists the counters related to CSFB for emergency calls.

Table 7-10 Counters related to CSFB for emergency callsCounter ID Counter Name Description

1526729510 L.IRATHO.E2W.CSFB.ExecAttOut.Emergency Number of CSFB-based handover execution attempts to WCDMA network triggered for emergency calls

1526729511 L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency Number of successful CSFB-based handover executions to WCDMA network triggered for emergency calls

The formula for calculating the CSFB handover success rate for emergency calls is as follows: CSFB handover success rate for emergency calls = L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency/L.IRATHO.E2W.CSFB.ExecAttOut.Emergency


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

If GSM devices are provided by Huawei, for details about processing at the GSM side, see Interoperability Between GSM and LTE Feature Parameter Description.

If UMTS devices are provided by Huawei, for details about processing at the UMTS side, see Interoperability Between UMTS and LTE Feature Parameter Description.

Blind Handover for CSFB

Compared with measurement-based handovers, blind handovers reduce access delays but affect handover success rates.

The following table describes the parameters in the CSFallBackBlindHoCfg MO used to set the blind-handover priorities of different RATs for CSFB.

Parameter Name


Setting Notes

CN CSFallBackBlindHoCfg.CnOperatorId Network Set this parameter

Parameter Name


Setting Notes

Operator ID

plan (negotiation not required)

based on the network plan. This parameter specifies the ID of the operator whose RAT blind-handover priorities are to be set.




Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the high-priority RAT to be considered in blind handovers for CSFB.




Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the medium-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.


CSFallBackBlindHoCfg.InterRatLowestPri Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter is set to CDMA2000 by default and

Parameter Name


Setting Notes

specifies the low-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatSecondPri parameters.


Parameter Name


Setting Notes




To activate blind handovers, select the BlindHoSwitch(BlindHoSwitch) check box. A blind handover to an inter-RAT cell can be performed only if a blind-handover priority is specified for the inter-RAT cell. Compared with measurement-based handovers, blind handovers reduce access delays but affect handover success rates.

To deactivate blind handovers, clear the BlindHoSwitch(BlindHoSwitch) check box.



To activate blind handovers for a cell under the eNodeB, select the BlindHoSwitch(BlindHoSwitch) check box under the parameter. If the BlindHoSwitch(BlindHoSwitch) check box is deselected, blind handovers for the cell are

Parameter Name


Setting Notes

invalid.

Measurement-based Handovers for CSFB

An appropriate event B1 threshold for CSFB ensures that inter-RAT handovers are triggered in a timely fashion. A high threshold results in a low probability of triggering event B1, thereby affecting user experience. A low threshold results in a high probability of triggering event B1, but causes a high probability of incorrect handover decisions and a low handover success rate. Tune this parameter based on site conditions.

Event B1 for CSFB has a time-to-trigger parameter. This parameter lowers the probability of incorrect handover decisions and raises the handover success rate. However, if the value of this parameter is too large, CSFB delay is extended, affecting user experience. Tune this parameter based on site conditions.

Appropriate settings of the threshold and time-to-trigger for event B1 raise the handover success rate and lower the call drop rate. The related parameters are as follows:

Related parameters are in the CSFallBackHo MO.

Parameter Name


Setting Notes

Local cell ID

CSFallBackHo.LocalCellId Network plan (negotiation not required)


CSFB Utran EventB1 Time To Trig

CSFallBackHo.CsfbHoUtranTimeToTrig Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the time-to-trigger for event B1 in CSFB to UTRAN. When CSFB to UTRAN is required, set this parameter, which is used by UEs as one of the conditions for triggering event B1. When a UE detects that the signal quality in at least one UTRAN

Parameter Name


Setting Notes

cell meets the entering condition, it does not immediately send a measurement report to the eNodeB. Instead, the UE sends a measurement report only when the signal quality has been meeting the entering condition throughout a period defined by this parameter. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of incorrect handovers, preventing unnecessary handovers.

CSFB UTRAN EventB1 RSCP Trigger Threshold

CSFallBackHo.CsfbHoUtranB1ThdRscp Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the RSCP threshold for event B1 in CSFB to UTRAN. When CSFB to UTRAN is required, set this parameter, which is used by UEs as one of the conditions for triggering event B1. This parameter specifies the minimum required

Parameter Name


Setting Notes

RSCP of the signal quality provided by a UTRAN cell when a CSFB procedure can be initiated toward this cell. Event B1 is triggered when the RSCP measured by the UE is higher than the value of this parameter and all other conditions are also met.

CSFB UTRAN EventB1 ECN0 Trigger Threshold

CSFallBackHo.CsfbHoUtranB1ThdEcn0 Network plan (negotiation not required)

Indicates the Ec/No threshold for event B1, which is used in CS fallback to UTRAN. When CSFB to UTRAN is required, set this parameter, which is used by UEs as one of the conditions for triggering event B1. This parameter specifies the minimum required Ec/No of the signal quality provided by a UTRAN cell when a CSFB procedure can be initiated toward this cell. Event B1 is triggered when the Ec/No measured by the UE is higher than the value of this parameter and all other conditions are also met. Set this parameter to a large value for a cell with a large signal fading

Parameter Name


Setting Notes

variance in order to reduce the probability of unnecessary handovers. Set this parameter to a small value for a cell with a small signal fading variance in order to ensure timely handovers.

7.2 RIM Procedure from E-UTRAN to UTRAN

7.2.1 When to Use RIM Procedure from E-UTRAN to UTRAN

It is recommended that the RIM procedure be performed through the Huawei-proprietary eCoordinator if the following two conditions are met: 1. Both the eNodeB and the RNC/BSC are provided by Huawei and are connected to the same eCoordinator. 2. The core network that the eNodeB and the RNC/BSC are connected to does not support the RIM procedure or is not enabled with the RIM procedure. To perform the RIM procedure through the eCoordinator, set ENodeBAlgoSwitch.RimOnEcoSwitch to ON(On).

In other conditions, it is recommended that the RIM procedure be performed through the core network. In this case, set ENodeBAlgoSwitch.RimOnEcoSwitch to OFF(Off).


Check whether the RNC, MME, and SGSN support the RIM procedure, and whether an eCoordinator has been deployed.

7.2.3 Requirements


If the RIM procedure is performed through the core network, the core-network equipment must support this feature:

If the core-network equipment is provided by Huawei, the version must be SAE1.2 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 the RIM procedure from E-UTRAN to UTRAN.

If the RIM procedure is performed through the eCoordinator, the RNC/BSC, eNodeB, and eCoordinator must all be provided by Huawei and with the switch for supporting the RIM procedure through eCoordinator turned on.

To facilitate connection setup for RIM message exchange, you must enable RIM in the UTRAN before you enable it in the E-UTRAN.

License


Table 7-11 License control item for CSFB to UTRANFeature ID Feature

NameModel License


LOFD-001033 CSFB to UTRAN

LT1S00CFBU00 CS Fallback to UTRAN(FDD)


7.2.4 Precautions

None








Required Data

The required data is the same as that for LOFD-001033 CS Fallback to UTRAN. For details, see 7.1.5.1 Data Preparation.

UtranExternalCell: used to configure external UTRAN cells. The UtranExternalCell.Rac parameter must be set.


The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to configure the RIM procedure.

Parameter Name


Setting Notes

Support RIM by eCoordinator Switch

ENodeBAlgoSwitch.RimOnEcoSwitch


If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is performed through the core network.

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is performed through the eCoordinator.







Table 7-12 Parameters for the RIM procedure


Parameter Group Remarks



None


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:




4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification.








MO are displayed in area 4.5. Set the parameters in area 4 or 5.6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or

choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.


Using MML Commands

Performing the RIM procedure through the core network

Run the MOD ENODEBALGOSWITCH command with the Support RIM by eCoordinator Switch parameter set to OFF(Off).

Performing the RIM procedure through the eCoordinator

Run the MOD ENODEBALGOSWITCH command with the Support RIM by eCoordinator Switch parameter set to ON(On).



MOD ENODEBALGOSWITCH: RimOnEcoSwitch=OFF;


MOD ENODEBALGOSWITCH: RimOnEcoSwitch=ON;


Counter Observation

No matter whether the RIM procedure is performed through the core network or the eCoordinator, performance counters listed in Table 7-13 can be used to observe whether the RIM procedure has taken effect.

Table 7-13 Counters related to the RIM procedure between E-UTRAN and UTRANCounter ID Counter Name Description

1526728949 L.RIM.Load.E2W.Req Number of load information requests from an eNodeB to WCDMA network

1526728950 L.RIM.Load.E2W.Resp Number of times the eNodeB receives load information responses from WCDMA network

1526728951 L.RIM.Load.E2W.Update Number of times the eNodeB receives load information updates from WCDMA network

Signaling Tracing Result Observation

If the RIM procedure is performed through the core network, trace signaling messages as follows:

1. Start an S1 interface tracing task on the eNodeB LMT.

Check whether the eNB DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION-REQUEST IE is sent over the S1 interface. If the message is sent, you can infer that the eNodeB has sent the RIM request successfully.

2. Start an Iu interface tracing task on the RNC LMT.

If after receiving the DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION-REQUEST IE, the RNC sends the DIRECT INFORMATION TRANSFER message containing the RAN-INFORMAION IE to the SGSN, you can infer that the RNC can response to the RIM request normally.

3. Change the state of the UTRAN cell.

If the RNC sends the DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION IE over the Iu interface, you can infer that the RNC can notify the eNodeB with the cell state change through the RIM procedure.

If the RIM procedure is performed through the eCoordinator, trace signaling messages as follows:

1. Start an Se interface tracing task on the eNodeB LMT.

Check whether the ENB DIRECT INFORMATION TRANSFER message containing the RAN-INFORMAION-REQUEST IE is sent over the Se interface. If the message is sent, you can infer that the eNodeB has sent the RIM request successfully.

2. Start an Sr interface tracing task on the RNC LMT.

If after receiving the ECO DIRECT INFORMATION TRANSFER message containing the RAN-INFORMAION-REQUEST IE, the RNC sends the RNC DIRECT INFORMATION TRANSFER message containing the RAN-INFORMAION IE to the eCoordinator, you can infer that the RNC can response to the RIM request normally.

3. Change the state of the UTRAN cell.

If the RNC sends the RNC DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION IE over the Sr interface, you can infer that the RNC can notify the eNodeB with the cell state change through the RIM procedure.

7.2.7 Deactivation


Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 7.2.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to the table listed in the scenario of E-UTRAN to UTRAN CS/PS steering.

Table 7-14 Parameters for the RIM procedureMO Sheet in the


GroupSetting Notes

ENodeBAlgoSwitch (eNodeB-level switch)

User-defined sheet. ENodeBAlgoSwitch is recommended.

RimOnEcoSwitch Set this parameter to OFF(Off).



Using MML Commands











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


The parameter optimization procedure for this feature is the same as that for CSFB to UTRAN. For details, see 7.1.9 Parameter Optimization.

7.3 LOFD-001052 Flash CS Fallback to UTRANThis section provides engineering guidelines for LOFD-001052 Flash CS Fallback to UTRAN.

7.3.1 When to Use Flash CS Fallback to UTRAN

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


1. Collect information about whether LOFD-001033 CS Fallback to UTRAN has been activated.

2. Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and UTRAN cells. Information about coverage areas includes engineering parameters of sites (such as latitude and longitude), TX power of cell reference signals (RSs), and neighbor relationship configurations.

3. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks, and ensure that they all support CSFB and the RIM procedure. Table 7-15 describes the requirements of flash CSFB to UTRAN for the core networks. For details about the deployment guide on the UTRAN, see Interoperability Between UMTS and LTE Feature Parameter Description.


o Supported frequency bandso Whether the UEs support redirection from E-UTRAN to UTRANo Whether the UEs support PS handover from E-UTRAN to UTRANo Whether the UEs support UTRAN measurementso Whether the UEs comply with 3GPP Release 9 specifications


Table 7-15 Requirements of flash CSFB to UTRAN for core networksNE Requirement

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

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

7.3.3 Requirements


For flash CSFB to UTRAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be PS9.1 or later. If the core-network equipment is provided by another vendor, check with the vendor whether the equipment supports this feature. The core network must support flash CSFB to UTRAN.

License


Table 7-16 License control item for Flash CS Fallback to UTRANFeature ID Feature

NameModel License


LOFD-001033 CSFB to LT1S00CFBU00 CS Fallback to eNodeB per RRC

Feature ID Feature Name

Model License Control Item

NE Sales Unit

UTRAN UTRAN(FDD) Connected User

LOFD-001052 Flash CSFB to UTRAN

LT1S0FCFBU00 Flash CS Fallback to UTRAN


NOTE:

If the UTRAN uses Huawei devices, RIM-based flash CSFB needs to be enabled on the UTRAN.

7.3.4 Precautions

None








Required Data

Before configuring CSFB to UTRAN, collect the data related to neighbor relationships with UTRAN cells. This section provides only the information about MOs related to neighboring UTRAN cells and key parameters in these MOs. For more information about how to collect data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.

1. The following table describes the parameters that must be set in the UtranNFreq MO to configure a neighboring UTRAN frequency.

2. UtranExternalCell: used to configure external UTRAN cells. The UtranExternalCell.Rac parameter must be set.

3. UtranExternalCellPlmn: used to configure additional PLMN IDs for each shared external UTRAN cell. This MO is required only if the BTS that provides the external GERAN cell works in RAN sharing with common carriers mode and multiple operators share the external GERAN cell.

4. The following table describes the parameters that must be set in the UtranNCell MO to configure the neighboring relationship with a UTRAN cell. 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.


The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the handover mode and handover algorithm switches for flash CSFB to UTRAN.

Parameter Name


Setting Notes








To activate flash CSFB to UTRAN, select the UtranCsfbSwitch(UtranCsfbSwitch) and UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check boxes.

RIM switch

ENodeBAlgoSwitch.RimSwitch


UTRAN_RIM_SWITCH(UTRAN RIM Switch) under this parameter specifies whether to enable or disable the RIM procedure that requests event-driven multiple reports from UTRAN cells.

If this switch is turned on, the eNodeB can send RAN-INFORMATION-REQUEST/Multiple Report protocol data units (PDUs) to UTRAN cells to request event-driven multiple reports.

If this switch is turned off, the eNodeB cannot send RAN-INFORMATION-REQUEST/Multiple Report PDUs to UTRAN cells.

If this switch is turned off and UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) under ENodeBAlgoSwitch.HoAlgoSwitch is turned on, the eNodeB sends RAN-INFORMATION-REQUEST/Single

Parameter Name


Setting Notes

Report PDUs to UTRAN cells to request single reports.

If the UTRAN cells support RAN-INFORMATION-REQUEST/Multiple Report PDUs, you are advised to select the UTRAN_RIM_SWITCH(UTRAN RIM Switch) option.


Parameter Name


Setting Notes








The following table describes the parameter that must be set in the S1Interface MO to set the compliance protocol release of the MME.

Parameter Name

Parameter ID Data Source Setting Notes

MME Release S1INTERFACE.MmeRelease Network plan (negotiation not required)

To activate RIM procedures in Multiple Report

Parameter Name


mode, set the parameter to Release_R9(Release 9).


Parameter Name


Setting Notes

CN Operator ID










Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the

Parameter Name


Setting Notes

InterRatHighestPri and InterRatLowestPri parameters.




Set this parameter based on the network plan. This parameter is set to CDMA2000 by default and specifies the low-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatSecondPri parameters.




The following table describes the parameter that must be set in the InterRatHoComm MO to set the maximum number of neighboring UTRAN cells whose system information is sent to UEs for flash redirections.

Parameter Name


Setting Notes

Max Utran cell num in redirection

InterRatHoComm.CellInfoMaxUtranCellNum Network plan (negotiation not required)

Set this parameter based on the network plan. The default value is 8. If this parameter is set too small, the flash CSFB

Parameter Name


Setting Notes

success rate decreases because UEs may not receive valid neighboring cell system information. If this parameter is set too large, the size of an RRC connection release message increases and CSFB may fail.








Table 7-17 Parameters for flash CSFB to UTRANMO Sheet in the Summary

Data FileParameter Group Remarks

UtranNFreq UtranNFreq See 7.3.5.1 Data The RNP



Preparation. template sheet is recommended.







S1Interface S1Interface See 7.3.5.1 Data Preparation.














(Optional) GlobalProcSwitch

User-defined sheet. GlobalProcSwitch is recommended.









Batch Activated


















Using MML Commands

The prerequisite is that CSFB to UTRAN has been activated.

1. Run the MOD GLOBALPROCSWITCH command to set the RIM Coding Policy parameter.

If the peer device is a Huawei device, go to 2 directly.

If the peer device is not a Huawei device, you need to modify the RIM Coding Policy feature. Run the MOD GLOBALPROCSWITCH command to set the RIM Coding Policy parameter to StandardCoding.

2. Run the MOD ENODEBALGOSWITCH command with the UtranFlashCsfbSwitch(UtranFlashCsfbSwitch) check box selected under the Handover Algo switch parameter and with the UTRAN_RIM_SWITCH(UTRAN RIM Switch) check box selected under the RIM switch parameter.

3. Run the MOD S1INTERFACE command with the MME Release parameter set to Release_R9(Release 9).


MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranFlashCsfbSwitch-1,RimSwitch=UTRAN_RIM_SWITCH-1;MOD S1INTERFACE: S1InterfaceId=2,S1CpBearerId=1,CnOperatorId=0,MmeRelease=Release_R9;



Enable a UE to camp on an E-UTRAN cell and make a voice call. If the call continues and the RRC Connection Release message traced on the Uu interface carries the information about neighboring UTRAN cells, flash CSFB to UTRAN has been activated.

The signaling procedure for flash CSFB to UTRAN is similar to that for redirection-based CSFB to UTRAN described in 7.1.6 Activation Observation. The difference is that the RRC Connection Release message carries the information about neighboring UTRAN cells.


Check the status of the RIM procedure towards neighboring UTRAN cells by running the DSP UTRANRIMINFO command. If the ID of a neighboring UTRAN cell is displayed in the command output, the eNodeB has obtained the system information of this neighboring UTRAN cell.

Counter Observation

Table 7-18 lists the performance counters for observing functions related to flash CSFB to UTRAN.

Table 7-18 Performance counters for observing flash CSFB to UTRANFunction Counter ID Counter Name Description

Flash CSFB to UTRAN

1526728705 L.FlashCSFB.E2W Number of times flash CSFB to UTRAN is performed

RIM during flash CSFB to UTRAN

1526728946 L.RIM.SI.E2W.Req Number of system information requests sent from an eNodeB to a UMTS network

Function Counter ID Counter Name Description

1526728947 L.RIM.SI.E2W.Resp Number of system information responses sent from a UMTS network to an eNodeB

1526728948 L.RIM.SI.E2W.Update Number of system information updates sent from a UMTS network to an eNodeB

7.3.7 Deactivation


Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 7.3.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 7-19.

Table 7-19 Parameters for deactivating flash CSFB to UTRANMO Sheet in the Summary

Data FileParameter

GroupRemarks

ENodeBAlgoSwitch User-defined sheet HoAlgoSwitch Set UtranFlashCsfbSwitch under the HoAlgoSwitch parameter to 0.


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

Using MML Commands

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


MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranFlashCsfbSwitch-0;






7.4.1 When to Use Ultra-Flash CSFB

When LOFD-001033 CS Fallback to UTRAN has been enabled, this feature is recommended in scenarios where the eNodeB, RNC, MME, and MSC are provided by Huawei, and a proportion of of UEs in the live network support SRVCC from E-UTRAN to UTRAN.


Before deploying this feature, collect the following information:

LOFD-001033 CS Fallback to UTRAN has been activated. The eNodeB, RNC, MME, and MSC in the network are provided by Huawei and they

all support this feature. A proportion of UEs in the live network support SRVCC from E-UTRAN to

UTRAN.

7.4.3 Requirements


This feature is a Huawei-proprietary feature and requires that the UTRAN, eNodeB, RNC, MME, and MSC are provided by Huawei and support this feature. This feature is used with MME11.0 and MSC11.0.

License


Table 7-20 License information for ultra-flash CSFB to UTRANFeature ID Feature Name Model License

Control Item

NE Sales Unit

LOFD-070202 Ultra-Flash CSFB to UTRAN

LT1SUFCSFB00 Ultra-Flash CSFB to UTRAN


7.4.4 Precautions

This feature is a Huawei-proprietary feature and is not supported by devices provided by other vendors. In addition, this feature must first be activated on the RNC, MME, and MSC, and then be activated on the eNodeB. This is because this feature is triggered by the eNodeB and this avoids CSFB failures.








Required Data



The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the handover mode and handover algorithm switches for ultra-flash CSFB to UTRAN.

Parameter

Name


Setting Notes




Select the UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box.

(Optional) Multi-Operator Control Switch

ENodeBAlgoSwitch.MultiOpCtrlSwitch

Network plan (negotiation required)

If some RNCs do not support ultra-flash CSFB to UTRAN, turn on the mobility switch for corresponding operators.

If some RNCs do not support ultra-flash CSFB to UTRAN, the ultra-flash CSFB supporting capability of the UTRAN must be set in the UtranNetworkCapCfg MO.

Parameter Name


Setting Notes

Network Capability Configuration

UtranNetworkCapCfg.NetworkCapCfg


Clear the UltraFlashCsfbCapCfg check box for RNCs that do not support ultra-flash CSFB to UTRAN.


Parameter Name


Setting Notes

Ue Compatibility Switch

GlobalProcSwitch.UeCompatSwitch


Select the UltraFlashCsfbComOptSw option of the parameter when UEs on the network do not support ultra-flash CSFB.

When the MME provided by Huawei allows IMEI whitelist configurations for ultra-flash CSFB and the option is selected, the eNodeB performs ultra-flash CSFB on UEs in the IMEI whitelist. Therefore, delete the UEs that do not support ultra-flash CSFB from the whitelist before selecting the option. Otherwise, keep the option unselected.


Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs






Table 7-21 Parameters for ultra-flash CSFB to UTRAN


Parameter Group

Remarks

UtranNFreq UtranNFreq See 7.4.5.1 Data Preparation.



















This parameter must be customized on a list-type sheet of


Parameter Group

Remarks

the template.

GeranNfreqGroup User-defined sheet. GeranNfreqGroup is recommended.



GlobalProcSwitch User-defined sheet. GlobalProcSwitch is recommended.



















Using MML Commands

Ultra-Flash CSFB to UTRAN

1. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

2. Run the MOD ENODEBALGOSWITCH command with the UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box selected under the Handover Algo switch parameter.

(Optional) If some RNCs do not support ultra-flash CSFB to UTRAN, perform the following operations:

1. Run the MOD ENODEBALGOSWITCH command with the UtranSepOpMobilitySwitch(UtranSepOpMobilitySwitch) check box selected under the Multi-Operator Control Switch parameter.

2. Run the MOD UTRANNETWORKCAPCFG command with the UltraFlashCsfbCapCfg(UltraFlashCsfbCapCfg) check box cleared under the Network Capability Configuration parameter for RNCs that do not support ultra-flash CSFB to UTRAN.

(Optional) Perform the following operation if UE compatibility risks exist after ultra-flash CSFB is activated.

1. Run the MOD GLOBALPROCSWITCH command with the UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw) option of the UE Compatibility Switch parameter selected.



MOD ENODEBALGOSWITCH: HoAlgoSwitch= UtranUltraFlashCsfbSwitch-1;

(Optional) If some RNCs do not support ultra-flash CSFB to UTRAN, perform the following operations:

MOD ENODEBALGOSWITCH: MultiOpCtrlSwitch= UtranSepOpMobilitySwitch-1;MOD UTRANNETWORKCAPCFG: Mcc="460", Mnc="32", RncId=0, NetworkCapCfg= SrvccBasedCsfbCapCfg-0;

(Optional) Perform the following operation if UE compatibility risks exist after ultra-flash CSFB is activated.

MO GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;



The activation observation procedure for ultra-flash CSFB to UTRAN is as follows:

1. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that the UE falls back to a UTRAN cell and completes the call.

2. Enable a UE to camp on an E-UTRAN cell and receive a voice call so that the UE falls back to a UTRAN cell and completes the call.

Figure 7-10 shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-originated call.

Figure 7-11 shows the ultra-flash CSFB to UTRAN signaling procedure for a mobile-terminated call.

The UEs in the left and right sides of the figure are the same UE. The messages on the UTRAN side are only for reference. The UE was in idle mode before the call.

If the UE capability is not included in the Initial Context Setup Request (Initial Context Setup Req in the figures) message, the eNodeB initiates a UE capability transfer procedure immediately after receiving this message from the MME. If the UE capability is included in the Initial Context Setup Request message, the eNodeB initiates a UE capability transfer procedure after sending an Initial Context Setup Response (Initial Context Setup Rsp in the figures) message to the MME.

Figure 7-10 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-originated call

Figure 7-11 Ultra-flash CSFB to UTRAN signaling procedure for a mobile-terminated call

Counter Observation

The counter listed in Table 7-22 can be viewed to check whether the feature has taken effect.

Table 7-22 Counter related to ultra-flash CSFB to UTRAN


1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut Triggered by ultra-flash CSFB

Number of SRVCC-based outgoing handover executions from E-UTRAN to WCDMA network for ultra-flash CSFB

7.4.7 Deactivation



Table 7-23 Parameter related to ultra-flash CSFB to UTRANMO Sheet in the

Summary Data File

Parameter Group

Setting Notes



HoAlgoSwitch

Clear the UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch) check box.



Using MML Commands

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


MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranUltraFlashCsfbSwitch-0;



Table 7-24 Counter ID Counter Name Description

1526730146 L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut Number of SRVCC-based outgoing handover attempts from E-UTRAN to WCDMA network for ultra-flash CSFB

1526730147 L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut Number of SRVCC-based outgoing handover executions from E-UTRAN to WCDMA network for ultra-flash CSFB

1526730148 L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut Number of successful SRVCC-based outgoing handovers from E-UTRAN to WCDMA network for ultra-flash CSFB to UTRAN

Ultra-flash CSFB to UTRAN success rate = L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut/L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut



7.5 LOFD-001068 CS Fallback with LAI to UTRANThis section provides engineering guidelines for LOFD-001068 CS Fallback with LAI to UTRAN.

7.5.1 When to Use CS Fallback with LAI to UTRAN

Use LOFD-001068 CS Fallback with LAI to UTRAN when both of the following conditions are met:LOFD-001033 CS Fallback to UTRAN has been enabled.The E-UTRAN cell has neighboring UTRAN cells that belong to different PLMNs and supports inter-PLMN handovers, or the E-UTRAN cell has neighboring UTRAN cells that have different location area codes (LACs).

If both LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to GERAN have been enabled, you are advised to enable both LOFD-001068 CS Fallback with LAI to UTRAN and LOFD-001069 CS Fallback with LAI to GERAN.



2. Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and UTRAN cells.

3. Collect the versions and configurations of the NEs in the E-UTRAN, UTRAN, and core networks, and ensure that they all support CSFB and the MME supports LAI delivery. Table 7-25 describes the requirements of CSFB with LAI to UTRAN for the core networks.




Table 7-25 Requirements of CSFB with LAI to UTRAN for core networksNE Requirement

MME Supports: SGs interface to the MSC LAI selection based on the TAI of the

serving cell MSC-initiated paging PLMN selection and reselection Combined EPS/IMSI attach, combined

EPS/IMSI detach, and combined TAU/LAU CS signaling message routing SMS over SGs LAI delivery

MSC Supports: Combined EPS/IMSI attach SMS over SGs Paging message forwarding over the SGs

interface


7.5.3 Requirements


For CSFB with LAI to UTRAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be PS9.2 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 CSFB with LAI to UTRAN.

License


Table 7-26 License information for CSFB with LAI to UTRANFeature

IDFeature Name Model License


LOFD-001068

CS Fallback with LAI to UTRAN

LT1S0CSFLU00 CS Fallback with LAI to UTRAN


7.5.4 Precautions

None


CSFB with LAI to UTRAN is automatically activated when two conditions are met: The license for this feature has been purchased. CSFB to UTRAN has been activated.


Data preparation for activating CSFB with LAI to UTRAN is the same as that for activating CSFB to UTRAN. For details, see 7.1.5.1 Data Preparation.


For details, see 7.1.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.


For details, see 7.1.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs.


For details, see 7.1.5.4 Using the CME to Perform Single Configuration.


For details, see 7.1.5.5 Using MML Commands.


The activation observation procedure is as follows:

1. Configure two neighboring UTRAN cells with different LAIs for an E-UTRAN cell, and enable the MME to include only one of the two LAIs in the instructions that will be delivered to the eNodeB.

2. Ensure that the signal strengths of the two UTRAN cells both reach the threshold for event B1. You can query the threshold by running the LST INTERRATHOUTRANGROUP command.

3. Enable a UE to camp on an E-UTRAN cell and originate a voice call so that the UE falls back to the UTRAN cell with the specified LAI and completes the call.

4. Enable the UE to camp on the E-UTRAN cell and receive a voice call so that the UE falls back to the UTRAN cell with the specified LAI and completes the call.

You can observe the signaling procedure for CSFB with LAI to UTRAN, which is similar to that for CSFB to UTRAN described in 7.1.6 Activation Observation. The difference is that the Initial Context Setup Request or UE Context Mod Request message carries the LAI that the MME delivers to the eNodeB, as shown in the following figure:

Figure 7-12 LAI signaling tracing

7.5.7 Deactivation

CSFB with LAI to UTRAN is automatically deactivated when its license or CSFB to UTRAN is deactivated. For details about how to deactivate CSFB to UTRAN, see 7.1.7 Deactivation.





7.6 LOFD-001088 CS Fallback Steering to UTRANThis section provides engineering guidelines for LOFD-001088 CS Fallback Steering to UTRAN.

7.6.1 When to Use CS Fallback Steering to UTRAN

Use LOFD-001088 CS Fallback Steering to UTRAN to improve the network efficiency when both of the following conditions are met:

LOFD-001033 CS Fallback to UTRAN has been activated. An operator owns multiple UTRAN frequencies or the operator has different

handover policies for CS-only services and combined CS+PS services.

If the operator owns both UTRAN and GERAN, you can also activate LOFD-001089 CS Fallback Steering to GERAN to improve the network efficiency.






3. Collect information about the frequencies and frequency policies of the UTRAN. The frequency policies for UTRAN and E-UTRAN must be the same. For example, if F1 is the preferred frequency for voice services on UTRAN, the same configuration is recommended for E-UTRAN.

4. If LOFD-001089 CS Fallback Steering to GERAN is also to be activated, consider the GERAN frequencies when making frequency policies.

7.6.3 Requirements


For CSFB steering to UTRAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be SAE1.2 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 CSFB steering to UTRAN.

License


Table 7-27 License information for CSFB steering to UTRANFeature

IDFeature Name Model License Control

ItemNE Sales Unit

LOFD-001088

CS Fallback Steering to UTRAN

LT1S0CFBSU00 CS Fallback Steering to UTRAN


7.6.4 Precautions

None








Required Data



The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable CSFB steering to UTRAN.

Parameter

Name


Setting Notes



Network plan (negotiation not

Select the UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) check box under this parameter.

Parameter

Name


Setting Notes

required)

The following table describes the parameters that must be set in the CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.

Parameter Name


Setting Notes

CN Operator ID










Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.

Parameter Name


Setting Notes








The following table describes the parameters that must be set in the CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.

Parameter Name


Setting Notes

CSFB Highest priority InterRat for Idle UE

CSFallBackBlindHoCfg.IdleCsfbHighestPri


Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the high-priority RAT to be considered in CSFB for UEs in idle mode. For CSFB to UTRAN, retain the default value.

CSFB Second

CSFallBackBlindHoCfg.IdleCsfbSecondPri

Network plan

Set this parameter based on the

Parameter Name


Setting Notes

priority InterRat for Idle UE

(negotiation not required)

network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in CSFB for UEs in idle mode. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.

CSFB Lowest priority InterRat for Idle UE

CSFallBackBlindHoCfg.IdleCsfbLowestPri


Set this parameter based on the network plan. This parameter is set to CDMA2000 by default and specifies the low-priority RAT to be considered in CSFB for UEs in idle mode. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatSecondPri parameters.

The following table describes the parameter that must be set in the UtranNFreq MO to set the CS service priority of a neighboring UTRAN frequency considered for RRC_IDLE UEs.

Parameter Name


Setting Notes

CS service priority

UtranNFreq.CsPriority Network plan (negotiation not required)

Set this parameter based on the network plan. If this parameter is set to Priority_0(Priority 0) for the UTRAN frequency, the eNodeB does not select the frequency for SRVCC. The values

Parameter Name


Setting Notes

Priority_16(Priority 16) and Priority_1(Priority 1) indicate the highest and lowest SRVCC priority, respectively. Set a high priority for a UTRAN frequency with good coverage.

The following table describes the parameter that must be set in the UtranNFreq MO to set the CS+PS combined service priority of a neighboring UTRAN frequency for RRC_CONNECTED UEs.

Parameter Name


Setting Notes

CS and PS mixed priority

UtranNFreq.CsPsMixedPriority Network plan (negotiation not required)

Set this parameter based on the network plan. If 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 SRVCC priority, respectively. Set a high priority for a UTRAN frequency with good coverage.

The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO to set the CSFB policy for RRC_CONNECTED UEs.

Parameter Name


Setting Notes


CSFallBackPolicyCfg.CsfbHoPolicyCfg Network plan (negotiation not required)

Set this parameter based on the network plan. The default values are REDIRECTION, CCO_HO, and PS_HO. You are advised to set this parameter based on the UE capabilities and

Parameter Name


Setting Notes

network capabilities. For details about how to select a CSFB handover policy, see 3.9 Handover Execution.

The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO to set the CSFB policy for RRC_IDLE UEs.

Parameter Name


Setting Notes

CSFB handover policy Configuration for idle ue

CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg


Set this parameter based on the network plan. The default values are REDIRECTION, CCO_HO, and PS_HO. You are advised to set this parameter based on the UE capabilities and network capabilities. For details about how to select a CSFB handover policy, see 3.9 Handover Execution.








Table 7-28 Parameters for CS fallback steering to UTRANMO Sheet in the Summary




None



None

UtranNFreq User-defined sheet. UtranNFreq is recommended.


None

CSFallBackPolicyCfg User-defined sheet. CSFallBackPolicyCfg is recommended.


None








Using MML Commands

The configurations in this section are examples, and configurations on the live network can differ from the examples.

The prerequisite for the following operations is that E-UTRAN to UTRAN CS/PS Steering has been activated.

Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous coverage.

1. Run the MOD ENODEBALGOSWITCH command with the UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch) check box selected under the Handover Algo switch parameter.

2. Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat, Second priority InterRat, CSFB Highest priority InterRat for Idle UE, and CSFB Second priority InterRat for Idle UE parameters to UTRAN, GERAN, GERAN, and UTRAN, respectively.

3. Run the MOD UTRANNFREQ command with the CS service priority or CS and PS mixed priority parameter set to Priority_16(Priority 16) for UTRAN frequencies.

4. Run the MOD CSFAllBACKPOLICYCFG command with the PS_HO check box selected under the CSFB handover policy Configuration parameter and the REDIRECTION check box selected under the CSFB handover policy Configuration for idle ue parameter.

Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN provides contiguous coverage but the UTRAN does not. In this scenario, the eNodeB may not receive measurement reports after delivering UTRAN measurement configurations. When the CSFB protection timer expires, the UE is redirected to the GERAN.

1. The feature activation procedure is as follows: Run the MOD GERANNCELL command with the blind handover priority specified for the neighboring GERAN cell.

2. Run the MOD ENODEBALGOSWITCH command with switches set as follows:o Select the following options of the Handover Algo switch parameter:

UtranCsfbSwitch(UtranCsfbSwitch), GeranCsfbSwitch(GeranCsfbSwitch), UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch), and GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch).

o Select the UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) option of the Frequency Layer Switch parameter.

o Deselect the BlindHoSwitch option of the Handover Mode switch parameter.

3. Run the MOD CSFALLBACKBLINDHOCFG command with parameters set as follows based on the network conditions and policies: Set the Highest priority InterRat parameter to UTRAN. Set the Second priority InterRat parameter to GERAN. Set the CSFB Highest priority InterRat for Idle UE parameter to UTRAN. Set the CSFB Second priority InterRat for Idle UE parameter to GERAN.

4. Run the MOD CSFALLBACKPOLICYCFG command with the REDIRECTION option of the CSFB handover policy Configuration parameter selected.


Scenario 1: The UTRAN and GERAN cover the same area and provide contiguous coverage.

MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSteeringSwitch-1;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GERAN,IdleCsfbSecondPri=UTRAN;MOD UTRANNFREQ: LocalCellId=0,UtranDlArfcn=10800,CsPriority=Priority_16;MOD UTRANNFREQ: LocalCellId=1,UtranDlArfcn=9700,CsPsMixedPriority=Priority_16;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-1, IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;

Scenario 2: The UTRAN and GERAN cover the same area, and the GERAN provides contiguous coverage but the UTRAN does not.

MOD GERANNCELL:LocalCellId=1, Mcc="460", Mnc="20", Lac=12, GeranCellId=16,BlindHoPriority=32;MOD ENODEBALGOSWITCH:HoModeSwitch=BlindHoSwitch-0,HoAlgoSwitch=UtranCsfbSwitch-1&GeranCsfbSwitch-1,HoAlgoSwitch=UtranCsfbSteeringSwitch-1&GeranCsfbSteeringSwitch-1,FreqLayerSwtich=UtranFreqLayerMeasSwitch-1;MOD CSFALLBACKBLINDHOCFG:CnOperatorId=0,InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=UTRAN,IdleCsfbSecondPri=GERAN;MOD CSFALLBACKPOLICYCFG:CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0,IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;


The signaling procedure is the same as that for CSFB to UTRAN. After CS Fallback Steering to UTRAN is used, check whether it works as expected.

The activation observation procedure for CSFB steering to UTRAN is as follows:

1. Check that the UE supports redirection-based CSFB and handover-based CSFB.2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection

and handover, respectively.3. Enable the UE to initiate a voice call in idle mode and in connected mode.4. Observe the counters L.CSFB.E2W, L.RRCRedirection.E2W.CSFB, and

L.IRATHO.E2W.CSFB.ExecAttOut. If the values of the counters increase by 2, 1, and 1, respectively, CSFB steering to UTRAN has been activated.

If CSFB steering to GERAN has also been activated, the activation observation procedure is as follows:

1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs and

UTRAN as the highest-priority RAT for CSFB triggered for RRC_CONNECTED UEs.

3. Enable the UE to initiate a voice call in idle mode and in connected mode.4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase by

1, both CSFB steering to UTRAN and CSFB steering to GERAN have been activated.

7.6.7 Deactivation



Table 7-29 Parameters for deactivating CSFB steering to UTRANMO Sheet in the Summary

Data FileParameter

GroupRemarks



HoAlgoSwitch Set UtranCsfbSteeringSwitch under the HoAlgoSwitch parameter to 0.



Using MML Commands

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


MOD ENODEBALGOSWITCH: HoAlgoSwitch=UtranCsfbSteeringSwitch-0;






This section provides engineering guidelines for activation and activation observation of LOFD-001078 E-UTRAN to UTRAN CS/PS Steering.

7.7.1 When to Use E-UTRAN to UTRAN CS/PS Steering

Use LOFD-001078 E-TURAN to UTRAN CS/PS Steering when all of the following conditions are met: LOFD-001034 CS Fallback to UTRAN and LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN have been activated. The operator owns multiple UTRAN frequencies. The operator wants to divert CS or PS services to specific UTRAN frequencies based on the network plan and loads.


1. Determine whether LOFD-001034 CS Fallback to UTRAN and LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN have been activated.




3. Collect the operating frequencies and frequency policies of the E-UTRAN and UTRAN. The frequency policies for UTRAN and E-UTRAN must be the same. For example, if F1 is the preferred frequency for voice services on UTRAN, the same configuration is recommended for E-UTRAN.

4. Collect the configurations and versions of E-UTRAN and UTRAN equipment to check whether CSFB is supported.

7.7.3 Requirements


None

License


Table 7-30 License information for E-UTRAN to UTRAN CS/PS SteeringFeature ID Feature Name Model License Control

ItemNE Sales Unit

LOFD-001078

E-UTRAN to UTRAN

LT1SEUCSPS00 E-UTRAN to UTRAN CS/PS


Feature ID Feature Name Model License Control Item

NE Sales Unit

CS/PS Steering

Steering

7.7.4 Precautions

None








Required Data



The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable E-UTRAN to UTRAN CS/PS Steering.

Parameter

Name


Setting Notes

Frequency Layer Switch

ENodeBAlgoSwitch.FreqLayerSwtich


When CSFB to UTRAN and PS inter-RAT mobility between E-UTRAN and UTRAN have been configured, set this parameter as follows:

Select the UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) check box to enable measurement-based handover for E-UTRAN to UTRAN

Parameter

Name


Setting Notes

CS/PS Steering. Select the

UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) check box to enable blind handover for E-UTRAN to UTRAN CS/PS Steering.

The two check boxes can be simultaneously selected.

The following table describes the parameter that must be set in the UtranNFreq MO to set the CS service priority for a UTRAN frequency.

Parameter Name


CS service priority

UtranNFreq.CsPriority Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the CS service priority for the UTRAN frequency.







Table 7-31 Parameters for E-UTRAN to UTRAN CS/PS steering





None

UtranNFreq User-defined sheet. UtranNFreq is recommended.


None

















Using MML Commands

The prerequisite is that CSFB to UTRAN has been activated.

Scenario 1: Blind E-UTRAN to UTRAN CS/PS steering

1. Run the MOD ENODEBALGOSWITCH command with the UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) check box selected under the Frequency Layer Switch parameter.

2. Run the MOD UTRANNFREQ command with the CS service priority parameter set to Priority_16(Priority 16).

Scenario 2: Measurement-based E-UTRAN to UTRAN CS/PS steering

1. Run the MOD ENODEBALGOSWITCH command with UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) selected under the Frequency Layer Switch parameter.

2. Run the MOD UTRANNFREQ command with the CS service priority parameter set to Priority_16(Priority 16).


Scenario 1: Blind E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerBlindSwitch-1;MOD UTRANNFREQ: LocalCellId=0,UtranDlArfcn=10800,CsPriority=Priority_16;

Scenario 2: Measurement-based E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-1;MOD UTRANNFREQ: LocalCellId=0,UtranDlArfcn=10800,CsPriority=Priority_16;


The signaling procedure is the same as that for CSFB to UTRAN. After E-UTRAN to UTRAN CS/PS Steering is used, check whether it works as expected.


1. Verify that the UE supports CSFB and multiple UTRAN frequencies are available.2. Enable measurement-based and blind handover for E-UTRAN to UTRAN CS/PS

Steering. Set a high PS service priority for UTRAN frequency F1 and a high CS service priority for UTRAN frequency F2.

3. Have the UE camp on an LTE cell and initiate a voice call in the cell. The expected result is that the UE falls back to the UTRAN cell operating on F2.

4. Have the UE camp on the LTE cell and initiate PS services. Move the UE to the LTE cell edge. The expected result is that the UE is handed over to the UTRAN cell operating on F1.

7.7.7 Deactivation



Table 7-32 Parameters for deactivating E-UTRAN to UTRAN CS/PS Steering

MO Sheet in the Summary Data

File

Parameter Group

Remarks



FreqLayerSwtich

Clear the following options:

UtranFreqLayerMeasSwitch UtranFreqLayerBlindSwitch



Using MML Commands

Deactivating blind E-UTRAN to UTRAN CS/PS steering

Run the MOD ENODEBALGOSWITCH command with the UtranFreqLayerBlindSwitch(UtranFreqLayerBlindSwitch) check box cleared under the Frequency Layer Switch parameter.

Deactivating measurement-based E-UTRAN to UTRAN CS/PS steering

Run the MOD ENODEBALGOSWITCH command with the UtranFreqLayerMeasSwitch(UtranFreqLayerMeasSwitch) check box cleared under the Frequency Layer Switch parameter.


Deactivating blind E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerBlindSwitch-0;

Deactivating measurement-based E-UTRAN to UTRAN CS/PS steering

MOD ENODEBALGOSWITCH: FreqLayerSwtich=UtranFreqLayerMeasSwitch-0;





7.8 LOFD-001034 CS Fallback to GERANThis section provides engineering guidelines for LOFD-001034 CS Fallback to GERAN.

7.8.1 When to Use CS Fallback to GERAN

Use LOFD-001034 CS Fallback to GERAN in the initial phase of LTE network deployment when both of the following conditions are met:

The operator owns a mature GERAN network. The LTE network does not provide VoIP services, or UEs in the LTE network do not

support VoIP services.

For policies on whether to use PS handover or PS redirection for CSFB, see Inter-RAT Mobility Management in Connected Mode. If GERAN and E-UTRAN cells cover the same area, or the GERAN cell provides better coverage than the E-UTRAN cell, use CSFB based on blind handover to decrease the CSFB delay.


Collect the operating frequencies, coverage areas, and configurations of the E-UTRAN and GERAN cells. Information about coverage areas includes engineering parameters of sites (such as latitude and longitude), TX power of cell reference signals (RSs), and neighbor relationship configurations.

Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core networks, and ensure that they all support CSFB. Table 7-33 describes the requirements of CSFB to GERAN for the core networks.

Table 7-33 Requirements of CSFB to GERAN for core networks

NE Requirement

MME Supports:

o SGs interface to the MSCo LAI selection based on the TAI of

the serving cello MSC-initiated pagingo PLMN selection and reselectiono Combined EPS/IMSI attach,

combined EPS/IMSI detach, and combined TAU/LAU

o Routing of CS signaling messageso SMS over SGs

MSC Supports:

NE Requirement

o Combined EPS/IMSI attacho SMS over SGso Paging message forwarding over

the SGs interface


Collect the following information about the UEs that support GSM and LTE on the live network:

o Supported frequency bandso Whether the UEs support redirection from E-UTRAN to GERANo Whether the UEs support PS handover from E-UTRAN to GERANo Whether the UEs support GERAN measurements

This information is used to configure neighboring GERAN cells and to determine whether to perform CSFB based on handover or redirection. For details, see Inter-RAT Mobility Management in Connected Mode.

7.8.3 Requirements


For CSFB to GERAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be SAE1.2 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 CSFB to GERAN.

License


Table 7-34 License information for CSFB to GERANFeature ID Feature Name Model License

Control Item

NE Sales Unit

LOFD-001034

CS Fallback to GERAN

LT1S00CFBG00 CS Fallback to GERAN


NOTE:

If the GERAN network uses Huawei equipment, activate the license for GBFD-511313 CSFB and turn on the switch specified by the GCELLSOFT.SUPPORTCSFB parameter. This licence is used for scenarios with LAU after CSFB to GERAN.

7.8.4 Precautions

None








Required Data

Before configuring CSFB 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.

1. GeranNfreqGroup: used to configure a group of neighboring GERAN frequencies.2. GeranNfreqGroupArfcn: used to configure a neighboring BCCH frequency in a

GERAN carrier frequency group.3. GeranExternalCell: used to configure external GERAN cells. The

GeranExternalCell.Rac parameter must be set.4. 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.

5. GeranNcell: used to configure the neighboring relationship with a GERAN cell. 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.


The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the handover mode and handover algorithm switches for CSFB to GERAN.

Parameter Name


Setting Notes





To activate PS handovers, select the GeranPsHoSwitch(GeranPsHoSwitch) check box. To activate CCO, select the GeranCcoSwitch(GeranCcoSwitch) check box. To activate NACC, select the GeranNaccSwitch(GeranNaccSwitch) check box. If none of the preceding check boxes is selected, redirection will be used for CSFB to GERAN.




To activate CSFB to GERAN, select the GeranCsfbSwitch(GeranCsfbSwitch) option.


Parameter Name


Setting Notes







To activate blind handovers for a cell under the eNodeB, select the BlindHoSwitch(BlindHoSwitch) check box under the parameter. If the BlindHoSwitch(BlindHoSwitch) check box is deselected, blind handovers for the cell are

Parameter Name


Setting Notes

invalid.


Parameter Name


Setting Notes

CN Operator ID


Set this parameter based on the network plan. This parameter specifies the ID of the operator whose RAT blind-handover priorities are to be set.




Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the highest-priority RAT to be considered in blind handovers for CSFB. For CSFB to GERAN, set this parameter to GERAN.




Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in blind handovers for CSFB. If the highest-priority RAT has been set to GERAN, the second-highest-

Parameter Name


Setting Notes

priority RAT cannot be set to GERAN. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.





GERAN LCS capability

CSFallBackBlindHoCfg.GeranLcsCap Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the LCS capability of the GERAN.

The following table describes the parameter that must be set in the CSFallBackHo MO to set the CSFB protection timer.

Parameter Name


Setting Notes


CSFallBackHo.CsfbProtectionTimer Network plan (negotiation not required)

Set this parameter based on the network plan. The default value 4 applies to a GSM+UMTS+LTE

Parameter Name


Setting Notes

network. The default value is also recommended for a GSM+LTE network. If this parameter is set too large, the CSFB delay increases in abnormal CSFB scenarios. If this parameter is set too small, normal measurement or handover procedures may be interrupted.

The following table describes the parameter that must be set in the InterRatHoComm MO to set the maximum number of neighboring GERAN cells whose system information is sent to UEs for emergency redirections.

Parameter Name


Setting Notes

Max Geran cell num in CSFB EMC redirection

InterRatHoComm.GeranCellNumForEmcRedirect


The default value is 0, indicating that no system information of any neighboring UTRAN cells is sent to UEs for emergency redirections. Operators can set this parameter to 0 through 32 based on the network plan. After the CSFB protection timer expires, the eNodeB performs an

Parameter Name


Setting Notes

emergency redirection. If the signal quality of the serving cell is poor and this parameter is set to a large value, the eNodeB may fail to send the system information of neighboring UTRAN cells to UEs.








Table 7-35 Parameters for CSFB to GERAN



GeranNfreqGroup GeranNfreqGroup See 7.8.5.1 Data Preparation.


GeranNfreqGroupArfcn GeranNfreqGroupArfcn See 7.8.5.1 Data Preparation.


GeranExternalCell GeranExternalCell See 7.8.5.1 Data Preparation.


GeranExternalCellPlmn GeranExternalCellPlmn See 7.8.5.1 Data Preparation.


GeranNcell GeranNcell See 7.8.5.1 Data Preparation.













None





Batch Activated





7.8.5.5 Using Feature Operation and Maintenance on the CME

1. On the U2000 client, choose CME > Planned Area > Create Planned Area.2. In the displayed Create Planned Area dialog box, specify Planned area name,

select the eNodeB (for which CSFB to GERAN is to be activated) on the Base Station tab page under Available NEs, and click so that it is added to Selected NEs. Then, click OK.

3. Choose CME > Advanced > Feature Operation and Maintenance > Export Feature Commission Data from the main menu.

4. In the displayed dialog box, click LTE in the Category drop-down list, and select the CSFB to GERAN feature to be activated, for example, TDLOFD-001033 CSFB to GERAN. Then, click Next.

5. Under Available Base Stations in the dialog box, select the eNodeB whose data is to be exported. Click so that the eNodeB is added to Selected Base Stations. Then, click Next.

6. In the dialog box, set Export as to the format (.xls or .xlsm) in which the exported data is to be saved. Click to the right of Export path to specify the save path. Then, click Next.

7. Wait until the data is exported.8. Click the hyperlink to the save path. Alternatively, click Finish, and locate the

exported file in the save path.9. Set related parameters in the CSFB to UTRAN data file (for example, TDLOFD-

001033.xls).10. After setting the parameters, choose CME > Advanced > Feature Operation

and Maintenance > Import Feature Commission Data on the U2000 client. In the displayed dialog box, select the CSFB to GERAN data file, and click Next.

11. Wait until the file is imported. Leave the Export incremental script check box selected (default setting). Click Finish.

12. In the displayed dialog box, check that the eNodeB is displayed in the Selected NEs area. Set Encrypt script and Script Executor Operation. You are advised to set Script Executor Operation to Launch script executor and activate exported project so that the script will be executed upon it is loaded. Then, click OK.

13. In the displayed confirmation dialog box, click Yes. Data synchronization starts for the eNodeB. When Success is displayed in the Result column, the CSFB to GERAN feature has been activated.

The following table describes parameters for CSFB to GERAN: Table 7-36 Parameters for CSFB to GERAN

MO Parameter Name

Parameter ID Setting Notes

GERANNFREQGROUP Local cell ID

LocalCellId Manually configured

BCCH group ID

BcchGroupId Manually configured

GERAN versi

GeranVersion Manually configured

Starting ARFCN

StartingArfcn Manually configured

Band indicator

BandIndicator Manually configured

Cell reselection priority configure indicator

CellReselPriorityCfgInd Automatically configured as NOT_CFG

Cell reselection priority

CellReselPriority Automatically configured as 1

PMAX configure

PmaxGeranCfgInd Automatically configured as

MO Parameter Name


indicator NOT_CFG

PMAX PmaxGeran Manually configured

Minimum required RX level

QRxLevMin Automatically configured as 0

High priority threshold

ThreshXHigh Automatically configured as 7

Lower priority threshold

ThreshXLow Automatically configured as 7

Frequency offset

OffsetFreq Automatically configured as 0

NCC monitoring permitted

NccPermitted Automatically configured as 255

GERANNFREQGROUPARFCN

Local cell ID


BCCH group ID

BcchGroupId Manually configured

GERAN ARFCN

GeranArfcn Manually configured

GERANEXTERNALCELL Mobile country code

Mcc Manually configured

Mobile network code

Mnc Manually configured

GERAN cell ID

GeranCellId Manually configured

Location area code

Lac Manually configured

Routing area code configure indicator

RacCfgInd Automatically configured as NOT_CFG

Routing area code

Rac Manually configured

MO Parameter Name


Band indicator

BandIndicator Manually configured

GERAN ARFCN

GeranArfcn Manually configured

Network color code

NetworkColourCode Manually configured

Base station color code

BaseStationColourCode Manually configured

DTM indication

DtmInd Automatically configured as DTM_NOT_AVAILABLE

Cell name CellName Manually configured

CS and PS handover indication

CsPsHOInd Automatically configured as BOOLEAN_FALSE

GERANEXTERNALCELLPLMN

GERAN cell ID


Location area code


Mobile country code


Mobile network code


Share mobile country code

ShareMcc Manually configured

Share mobile network code

ShareMnc Manually configured

GERANNCELL Local cell ID


Mobile country


MO Parameter Name


code

Mobile network code


Location area code


GERAN cell ID


No handover indicator

NoHoFlag Automatically configured as PERMIT_HO_ENUM

No remove indicator

NoRmvFlag Automatically configured as PERMIT_RMV_ENUM

Blind handover priority

BlindHoPriority 0

Local cell name

LocalCellName Manually configured

Neighboring cell name

NeighbourCellName Manually configured

ENODEBALGOSWITCH Handover Algo switch

HoAlgoSwitch Automatically configured as GeranCsfbSwitch-1


HoModeSwitch Automatically configured as GeranRedirectSwitch-1&BlindHoSwitch-0&GeranPsHoSwitch-0

CSFALLBACKPOLICYCFG


CsfbHoPolicyCfg Automatically configured as REDIRECTION-1&CCO_HO-0&PS_HO-0

CSFB handover policy

IdleModeCsfbHoPolicyCfg

Automatically configured as REDIRECTION-

MO Parameter Name


Configuration for idle ue

1&CCO_HO-0&PS_HO-0

Csfb User Arp Configuration Switch

CsfbUserArpCfgSwitch Automatically configured as OFF

Normal Csfb User Arp

NormalCsfbUserArp Automatically configured as 2

CSFALLBACKBLINDHOCFG

CN operator ID

CnOperatorId Manually configured


InterRatHighestPri Automatically configured as UTRAN


InterRatSecondPri Automatically configured as GERAN


InterRatLowestPri Automatically configured as CDMA2000


GeranLcsCap Automatically configured as OFF

CSFALLBACKHO Local cell ID


CSFB Geran EventB1 Time To Trig

CsfbHoGeranTimeToTrig

Automatically configured as 40ms

CSFB GERAN EventB1 Trigger Threshold

CsfbHoGeranB1Thd Automatically configured as -103


CsfbProtectionTimer Automatically configured as 4

CELLHOPARACFG Handover HoModeSwitch Automatically

MO Parameter Name


Mode switch

configured as BlindHoSwitch-0

INTERRATHOCOMM Max Geran cell num in CSFB EMC redirection

GeranCellNumForEmcRedirect

Automatically configured as 0


MML-based Procedure

Basic scenario 1: CSFB to GERAN using blind redirection

CSFB to GERAN using blind redirection works regardless of whether neighboring GERAN cells are configured.

If you want to configure a neighboring GERAN cell, you must configure the GeranNFreqand GeranNCell MOs. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

If you do not want to configure a neighboring GERAN cell, you must configure the GeranRanShare or GeranExternalCell MO. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

1. Run the following eNodeB- and cell-level commands to enable the blind handover function for CSFB to GERAN:


b. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of the Handover Mode switch parameter selected.

2. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter selected.

3. Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO option of the CSFB handover policy Configuration parameter deselected and the REDIRECTION option of the same parameter selected.

4. (Optional) If you require setting GERAN as having the highest priority for CSFB, run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat parameter set to GERAN and the Second priority InterRat parameter set to UTRAN.

5. (Optional) If a neighboring GERAN cell is configured, run the MOD GERANNCELL command with the Blind handover priority parameter set to the highest priority (32).

6. (Optional) If no neighboring GERAN cell is configured, run the ADD GeranNfreqGroup command with the Frequency Priority for Connected Mode parameter set to the highest priority (8).

Basic scenario 2: CSFB to GERAN using blind CCO with NACC

1. Add neighboring GERAN frequencies and neighbor relationships with GERAN cells. For details about parameter settings, see Inter-RAT Mobility Management in Connected Mode.

2. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter, the BlindHoSwitch(BlindHoSwitch), GeranNaccSwitch(GeranNaccSwitch), and GeranCcoSwitch(GeranCcoSwitch) options of the Handover Mode switch parameter, and the GERAN_RIM_SWITCH(GERAN RIM Switch) option of the RIM switch parameter selected.

3. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of the Handover Mode switch parameter selected.

4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO and CCO_HO options of the CSFB handover policy Configuration parameter deselected and selected, respectively.

5. (Optional) If you require setting UTRAN as having the highest priority for CSFB, run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat parameter set to GERAN and the Second priority InterRat parameter set to UTRAN.

6. Run the MOD GERANNCELL command with the Blind handover priority parameter set to 32.

Basic scenario 3: CSFB to GERAN using blind handovers


2. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter and the BlindHoSwitch(BlindHoSwitch) and GeranPsHoSwitch(GeranPsHoSwitch) options of the Handover Mode switch parameter selected.

3. Run the MOD CellHoParaCfg command with the BlindHoSwitch option of the Handover Mode switch parameter selected.

4. (Optional) If the optional feature LOFD-001089 CS Fallback Steering to GERAN is enabled, run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the CSFB handover policy Configuration parameter selected.

5. (Optional) If you require setting GERAN as having the highest priority for CSFB, run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat parameter set to GERAN and the Second priority InterRat parameter set to UTRAN.


Basic scenario 4: CSFB to GERAN using measurement-based redirections


2. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter selected.


4. Run the MOD CSFALLBACKPOLICYCFG command with the CCO_HO and PS_HO option of the CSFB handover policy Configuration parameter deselected and the REDIRECTION option of the same parameter selected.


Basic scenario 5: CSFB to GERAN using measurement-based handovers (recommended)


2. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) check box selected under the Handover Algo switch and the GeranPsHoSwitch(GeranPsHoSwitch) check box selected under the Handover Mode switch parameter.


4. (Optional) If the optional feature LOFD-001089 CS Fallback Steering to GERAN is enabled, run the MOD CSFALLBACKPOLICYCFG command with the PS_HO option of the CSFB handover policy Configuration parameter selected.


Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC (recommended)


2. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSwitch(GeranCsfbSwitch) option of the Handover Algo switch parameter, the GeranNaccSwitch(GeranNaccSwitch) and GeranCcoSwitch(GeranCcoSwitch) options of the Handover Mode switch parameter, and the GERAN_RIM_SWITCH(GERAN RIM Switch) option of the RIM switch parameter selected.


4. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO and CCO_HO options of the CSFB handover policy Configuration parameter deselected and selected, respectively.



Basic scenario 1: CSFB to GERAN using blind redirection (configured with neighboring GERAN cells)

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1, HoModeSwitch=BlindHoSwitch-1;MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;

Basic scenario 1: CSFB to GERAN using blind redirection (configured with no neighboring GERAN cell)

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1, HoModeSwitch=BlindHoSwitch-1;MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;ADD GeranNfreqGroup: LocalCellId=0, BcchGroupId=0, StratingArfcn=0, ConnFreqPriority=8;ADD GERANNFREQGROUPARFCN: LocalCellId=0, BcchGroupId=0,GeranArfcn=0;ADD GERANRANSHARE: LocalCellId=0, BcchGroupId=0, Mcc="460", Mnc="20";

Basic scenario 2: CSFB to GERAN using blind CCO with NACC

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1, HoModeSwitch=BlindHoSwitch-1&GeranNaccSwitch-1&GeranCcoSwitch-1,RimSwitch=GERAN_RIM_SWITCH-1;MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-1&PS_HO-0;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;

Basic scenario 3: CSFB to GERAN using blind handovers

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1, HoModeSwitch=GeranPsHoSwitch-1&BlindHoSwitch-1;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-1&PS_HO-1;MOD CELLHOPARACFG: LocalCellId=0, HoModeSwitch=BlindHoSwitch-1;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=GERAN,InterRatSecondPri=UTRAN;MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;

Basic scenario 4: CSFB to GERAN using measurement-based redirections

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1;MOD CELLHOPARACFG: LocalCellId=1, HoModeSwitch=BlindHoSwitch-0;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;

Basic scenario 5: CSFB to GERAN using measurement-based handovers

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1, HoModeSwitch=GeranPsHoSwitch-1;MOD CELLHOPARACFG: LocalCellId=1, HoModeSwitch=BlindHoSwitch-0;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-1&PS_HO-1;MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;

Basic scenario 6: CSFB to GERAN using measurement-based CCO with NACC

MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-1, HoModeSwitch=GeranNaccSwitch-1&GeranCcoSwitch-1,RimSwitch=GERAN_RIM_SWITCH-1;MOD CELLHOPARACFG: LocalCellId=1, HoModeSwitch=BlindHoSwitch-0;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-1&PS_HO-0;MOD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=12, GeranCellId=15,BlindHoPriority=32;




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

You can observe the signaling procedures for CSFB to GERAN, which is similar to that for CSFB to UTRAN described in section Figure 7-16.

NOTE:

In the following figures, the UE on the left side and the UE on the right side are the same UE. The signaling on the GERAN side is for reference only. The procedure for mobile-terminated calls is similar to the procedure for mobile-originated calls except that the procedure for mobile-terminated calls includes paging.

Figure 7-16 Redirection-based CSFB to GERAN for a mobile-originated call

The signaling procedure for PS handover-based CSFB to GERAN is different from the signaling procedure for redirection-based CSFB to GERAN. The difference is as follows: In PS handover-based CSFB to GERAN, the eNodeB performs a PS handover procedure rather than an RRC connection release procedure after the UE reports measurement results to the eNodeB. For details about the signaling procedure of PS handover-based CSFB to GERAN, see 7.1.6 Activation Observation. In the signaling procedure of PS handover-based CSFB to GERAN, the CSFB indication flag is true and the CSFB target is GERAN in the MobilityFromEUTRACommand message.

In the signaling procedure for PS handover-based CSFB to GERAN, the cs-FallbackIndicator IE is TRUE and the CSFB target is GERAN in the MobilityFromEUTRACommand message. Figure 7-17 shows the signaling procedure for CCO/NACC-based CFSB to GERAN for a mobile-originated call. In the CSFB, handover preparation is absent. The MobilityFromEUTRACommand message carries the CCO/NACC information and the CSFB target is GERAN.

Figure 7-17 CCO/NACC-based CSFB to GERAN for a mobile-originated call

Counter Observation

Table 7-37 lists the performance counters for observing functions related to CSFB to GERAN.

Table 7-37 Performance counters for observing CSFB to GERANFunction Counter ID Counter Name Description

CSFB to GERAN 1526728324 L.CSFB.E2G Number of times CSFB to GERAN is performed

CSFB to GERAN triggered for emergency calls

1526728710 L.CSFB.E2G.Emergency Number of times CSFB to GERAN is triggered for emergency calls

7.8.7 Deactivation



Table 7-38 Parameters for deactivating CSFB to GERANMO Sheet in the

Summary Data FileParameter Group Remarks

ENodeBAlgoSwitch User-defined sheet HoAlgoSwitch To deactivate CSFB to GERAN, set GeranCsfbSwitch under the HoAlgoSwitch parameter to 0.



Using MML Commands

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


MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSwitch-0;


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

Related counters are listed in Table 7-39.

Table 7-39 Counters related to the execution of CSFB by the eNodeBCounter ID Counter Name Description

1526728321 L.CSFB.PrepAtt Number of CSFB indicators received by the eNodeB

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

Table 7-40 lists the counter related to CSFB to GERAN.

Table 7-40 Counter related to CSFB to GERANCounter ID Counter Name Description

1526728324 L.CSFB.E2G Number of procedures for CSFB to GERAN

Table 7-41 lists the counters that indicate whether CSFB is performed through redirection or through handover.

Table 7-41 Counters related to CSFB through redirection or handoverCounter ID Counter Name Description

1526728498 L.RRCRedirection.E2G.CSFB Number of CSFB-based redirections from E-UTRAN to GERAN

1526728507 L.IRATHO.E2G.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover preparation attempts from E-UTRAN to GERAN

You can check whether CCO with NACC or CCO without NACC is used as the CSFB mechanism by viewing the counters listed in Table 7-42.

Table 7-42 Counters related to using CCO with NACC or CCO without NACCCounter ID Counter Name Description

1526729505 L.CCOwithNACC.E2G.CSFB.ExecAttOut Number of CSFB-based CCO with NACC executions from E-UTRAN to GERAN

1526729506 L.CCOwithNACC.E2G.CSFB.ExecSuccOut Number of successful CSFB-based CCOs with NACC


from E-UTRAN to GERAN

1526729507 L.CCOwithoutNACC.E2G.CSFB.ExecAttOut Number of CSFB-based CCO without NACC executions from E-UTRAN to GERAN

The CCO success rate can be calculated in the following ways:

L.CCOwithNACC.E2G.CSFB.ExecSuccOut / L.CCOwithNACC.E2G.CSFB.ExecAttOut

L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut / L.CCOwithoutNACC.E2G.CSFB.ExecAttOut

After the CSFB protection timer expires, the eNodeB may perform a blind redirection to enter the protection procedure. Table 7-43 lists the related counter. A larger value of this counter indicates a longer average UE access delay during CSFB.

Table 7-43 Counter related to the number of times that the eNodeB enters the protection procedure for CSFBCounter ID Counter Name Description

1526729516 L.RRCRedirection.E2G.CSFB.TimeOut Number of CSFB-based blind redirections from E-UTRAN to GERAN caused by CSFB protection timer expiration

Table 7-44 lists the counters related to CSFB for emergency calls.

Table 7-44 Counters related to CSFB for emergency callsCounter ID Counter Name Description

1526729513 L.IRATHO.E2G.CSFB.ExecAttOut.Emergency Number of CSFB-based handover execution attempts to GERAN triggered for emergency calls

1526729514 L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency Number of successful CSFB-based handover executions to GERAN triggered for emergency calls

CSFB handover success rate for emergency calls = L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency/L.IRATHO.E2G.CSFB.ExecAttOut.Emergency


The blind-handover-related parameter optimization procedure for CSFB to GERAN is the same as that for CSFB to UTRAN. For details, see 7.1.9 Parameter Optimization.

The following table lists event-B1-related parameters for CSFB to GERAN in the CSFallBackHo MO.

Parameter Name


Setting Notes

Local cell ID

CSFallBackHo.LocalCellId Network plan (negotiation not required)


CSFB GERAN EventB1 Trigger Threshold

CSFallBackHo.CsfbHoGeranB1Thd Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the RSSI threshold for event B1 in CSFB to GERAN. Event B1 is triggered when the measured RSSI of a GERAN cell reaches the value of this parameter and all other conditions are also met.

CSFB Geran EventB1 Time To Trig

CSFallBackHo.CsfbHoGeranTimeToTrig Network plan (negotiation not required)

Set this parameter based on the network plan. This parameter specifies the time-to-trigger for event B1 in CSFB to GERAN. When CSFB to GERAN is required, set this parameter, which is used by UEs as one of the conditions for triggering event B1. When a UE detects that the signal quality in at

Parameter Name


Setting Notes

least one GERAN cell meets the entering condition, it does not immediately send a measurement report to the eNodeB. Instead, the UE sends a measurement report only when the signal quality has been meeting the entering condition throughout a period defined by this parameter. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of incorrect handovers, preventing unnecessary handovers.

7.9 RIM Procedure from E-UTRAN to GERAN

7.9.1 When to Use RIM Procedure Between E-UTRAN and GERAN

It is recommended that the RIM procedure be performed through the Huawei-proprietary eCoordinator if the following two conditions are met: 1. Both the eNodeB and the RNC/BSC are provided by Huawei and are connected to the same eCoordinator. 2. The core network that the eNodeB and the RNC/BSC are connected to does not support the RIM procedure or is not enabled with the RIM procedure. To perform the RIM procedure through the eCoordinator, set ENodeBAlgoSwitch.RimOnEcoSwitch to ON(On).

In other conditions, it is recommended that the RIM procedure be performed through the core network. In this case, set ENodeBAlgoSwitch.RimOnEcoSwitch to OFF(Off).


Check whether the BSC, MME, and SGSN support the RIM procedure, and whether an eCoordinator has been deployed.

7.9.3 Requirements


If the RIM procedure is performed through the core network, the core-network equipment must support this feature:

If the equipment is provided by Huawei, the version must be SAE1.2. If the core-network equipment is provided by another vendor, check with the vendor

whether the equipment supports this feature. The BSC, MME, and SGSN must support the RIM procedures. If one of the NEs does

not support, the RIM procedures fail.

NOTE:

In a multioperator core network (MOCN) scenario, the eNodeB preferentially selects the link for the primary operator when sending an RIM request. If the RIM procedure fails, the eNodeB no longer attempts to send the RIM request on other links.

If the RIM procedure is performed through the eCoordinator, the RNC/BSC, eNodeB, and eCoordinator must all be provided by Huawei and with the switch for supporting the RIM procedures through eCoordinator turned on.

License


Table 7-45 License control item for CSFB to GERANFeature



LOFD-001034

CSFB to GERAN


eNodeB per user in RRC connected mode

7.9.4 Precautions

None








Required Data


GeranExternalCell: used to configure external GERAN cells. The GeranExternalCell.Rac parameter must be set.


The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to configure the RIM procedure.

Parameter Name


Setting Notes


ENodeBAlgoSwitch.RimOnEcoSwitch


If ENodeBAlgoSwitch.RimOnEcoSwitch is set to OFF(Off), the RIM procedure is performed through the core network.

If ENodeBAlgoSwitch.RimOnEcoSwitch is set to ON(On), the RIM procedure is performed through the eCoordinator.







Table 7-46 Parameters for the RIM procedure





None

















Using MML Commands











Counter Observation

No matter whether the RIM procedure is performed through the core network or the eCoordinator, performance counters listed in Table 7-47 can be used to observe whether the RIM procedure has taken effect.

Table 7-47 Counters related to the RIM procedure between E-UTRAN and GERANCounter ID Counter Name Description

1526729661 L.RIM.SI.E2G.Req Number of times the eNodeB sends a system information request to a GERAN

1526729662 L.RIM.SI.E2G.Resp Number of times the eNodeB receives a system information response from a GERAN

1526729663 L.RIM.SI.E2G.Update Number of times the eNodeB receives a system information update from a GERAN

Signaling Tracing Result Observation

If the RIM procedure is performed through the core network, trace signaling messages as follows:

1. Start an S1 interface tracing task on the eNodeB LMT.

Check whether the eNB DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION-REQUEST IE is sent over the S1 interface. If the message is sent, you can infer that the eNodeB has sent the RIM request successfully.

2. Start a Gb interface tracing task on the BSC LMT.

If after receiving the DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION-REQUEST IE, the BSC sends the DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION IE to the SGSN, you can infer that the BSC can response to the RIM request normally.

3. Change the state of the GSM cell.

If the BSC sends the DIRECT INFORMATION TRANSFER message containing the RAN-INFORMAION IE over the Gb interface, you can infer that the BSC can notify the eNodeB with the cell state change through the RIM procedure.

If the RIM procedure is performed through the eCoordinator, trace signaling messages as follows:

1. Start an Se interface tracing task on the eNodeB LMT.

Check whether the ENB DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION-REQUEST IE is sent over the Se interface. If the message is sent, you can infer that the eNodeB has sent the RIM request successfully.

2. Start an Sg interface tracing task on the BSC LMT.

If after receiving the ECO DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION-REQUEST IE, the BSC sends the BSC DIRECT INFORMATION TRANSFER message containing the RAN-INFORMAION IE to the eCoordinator, you can infer that the BSC can response to the RIM request normally.

3. Change the state of the GSM cell.

If the BSC sends the BSC DIRECT INFORMATION TRANSFER message containing the RAN-INFORMATION IE over the Sg interface, you can infer that the BSC can notify the eNodeB with the cell state change through the RIM procedure.

7.9.7 Deactivation



Table 7-48 Parameters for the RIM procedureMO Sheet in the


GroupRemarks

ENodeBAlgoSwitch User-defined sheet. RimOnEcoSwitch Set this parameter to


Parameter Group

Remarks

ENodeBAlgoSwitch is recommended.

OFF(Off).



Using MML Commands











The performance monitoring procedure for this feature is the same as that for CSFB to GERAN. For details, see 7.8.8 Performance Monitoring.


The parameter optimization procedure for this feature is the same as that for CSFB to GERAN. For details, see 7.8.9 Parameter Optimization.

7.10 LOFD-001053 Flash CS Fallback to GERANThis section provides engineering guidelines for LOFD-001053 Flash CS Fallback to GERAN.

7.10.1 When to Use Flash CS Fallback to GERAN

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


Collect information about whether LOFD-001034 CS Fallback to GERAN has been activated.


Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core networks, and ensure that they all support CSFB and the RIM procedure. Table 7-49 describes the requirements of flash CSFB to GERAN for the core networks. For details about processing in Huawei GSM equipment, see Interoperability Between GSM and LTE in GBSS Feature Documentation.


o Supported frequency bandso Whether the UEs support redirection from E-UTRAN to GERANo Whether the UEs support PS handover from E-UTRAN to GERANo Whether the UEs support GERAN measurementso Whether the UEs comply with 3GPP Release 9 specifications


Table 7-49 Requirements of flash CSFB to GERAN for core networksNE Requirement

MME Supports CSFB and RIM procedures

SGSN Supports CSFB and RIM procedures

7.10.3 Requirements


For flash CSFB to GERAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be PS9.2 or later. If the core-network equipment is provided by another vendor, check with the vendor whether the equipment supports this feature. The core network must support flash CSFB to UTRAN.

License


Table 7-50 License information for flash CSFB to GERANFeature ID Feature

NameModel License


LOFD-001034

CSFB to GERAN



LOFD-001053

Flash CSFB to GERAN

LT1S0FCFBG00 Flash CS Fallback to GERAN


NOTE:

If the GERAN uses Huawei devices, evolved network assisted cell change (eNACC) between E-UTRAN and GERAN for CSFB needs to be enabled on the GERAN.

7.10.4 Precautions

None








Required Data

Before configuring CSFB 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 and key parameters in these MOs. For more information about how to collect data for the parameters in these MOs, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.

1. GeranNfreqGroup: used to configure a group of neighboring GERAN frequencies.2. GeranNfreqGroupArfcn: used to configure a neighboring BCCH frequency in a

GERAN carrier frequency group.3. GeranExternalCell: used to configure external GERAN cells. The

GeranExternalCell.Rac parameter must be set.

4. 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.

5. GeranNcell: used to configure the neighboring relationship with a GERAN cell. 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.


The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the handover mode and handover algorithm switches for flash CSFB to GERAN.

Parameter Name


Setting Notes








To activate flash CSFB to GERAN, select the GeranCsfbSwitch(GeranCsfbSwitch) and GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check boxes.

RIM switch

ENodeBAlgoSwitch.RimSwitch


GERAN_RIM_SWITCH(GERAN RIM Switch) under this parameter specifies whether to enable or disable the RIM procedure that requests event-driven multiple reports from GERAN cells.

If this switch is turned on, the eNodeB can send RAN-INFORMATION-REQUEST/Multiple Report PDUs to GERAN cells to request event-driven multiple reports.

If this switch is turned off, the eNodeB cannot send RAN-INFORMATION-REQUEST/Multiple Report PDUs to GERAN cells.

If this switch is turned off and GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) under

Parameter Name


Setting Notes

ENodeBAlgoSwitch.HoAlgoSwitch is turned on, the eNodeB sends RAN-INFORMATION-REQUEST/Single Report PDUs to GERAN cells to request single reports.

If the GERAN cells support RAN-INFORMATION-REQUEST/Multiple Report PDUs, you are advised to select the GERAN_RIM_SWITCH(GERAN RIM Switch) option.


Parameter Name


Setting Notes








The following table describes the parameter that must be set in the S1Interface MO to set the compliance protocol release of the MME.

Parameter Name


Setting Notes

MME Release

S1INTERFACE.MmeRelease Network plan (negotiation not required)

To activate RIM procedures in Multiple Report mode, set the parameter to Release_R9(Release 9).


Parameter Name


Setting Notes

CN Operator ID


Set this parameter based on the network plan. This parameter specifies the ID of the operator whose RAT blind-handover priorities are to be set.




Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the highest-priority RAT to be considered in blind handovers for CSFB. For flash CSFB to GERAN, set this parameter to GERAN.




Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in blind handovers for CSFB. If the

Parameter Name


Setting Notes

highest-priority RAT has been set to GERAN, the second-highest-priority RAT cannot be set to GERAN. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.








The following table describes the parameter that must be set in the InterRatHoComm MO to set the maximum number of neighboring UTRAN cells whose system information is sent to UEs for flash redirections.

Parameter Name


Setting Notes

Max Geran cell num in redirection

InterRatHoComm.CellInfoMaxGeranCellNum Network plan (negotiation not required)

Set this parameter based on the network plan. The default value is 8. If this parameter is set too small, the flash CSFB success rate decreases because UEs may not receive valid neighboring cell system information. If this parameter is set too large, the size of an RRC connection release message increases and CSFB may fail.







Table 7-51 Parameters for flash CSFB to GERANMO Sheet in the Summary












S1Interface S1Interface See 7.10.5.1 Data Preparation.












None



None





Batch Activated








5. After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME

Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help.










Using MML Commands

The prerequisite is that CSFB to GERAN has been activated. In addition to the steps in the CSFB to GERAN using blind redirections or CSFB to GERAN using measurement-based redirections scenario, perform the following steps:

1. Run the MOD ENODEBALGOSWITCH command with the GeranFlashCsfbSwitch(GeranFlashCsfbSwitch) check box selected under the Handover Algo switch parameter and with the GERAN_RIM_SWITCH(GERAN RIM Switch) check box selected under the RIM switch parameter.

2. Run the MOD S1INTERFACE command with the MME Release parameter set to Release_R9(Release 9).


MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranFlashCsfbSwitch-1,RimSwitch=GERAN_RIM_SWITCH-1;MOD S1INTERFACE: S1InterfaceId=2,S1CpBearerId=1,CnOperatorId=0,MmeRelease=Release_R9;



Enable a UE to camp on an E-UTRAN cell and originate a voice call. If so that the UE falls back to a GERAN cell and completes the call continues, and the RRC Connection Release message traced in on the Uu interface tracing carries the information of the neighboring GERAN cell. In this case, flash CSFB to GERAN has been activated successfully.

In this case, flash CSFB to GERAN has been activated successfully. The procedure of flash CS fallback to GERAN on the E-UTRAN side is the same as the procedure of redirection-based CS fallback to GERAN. For details, see 7.1.6 Activation Observation. The difference is that the RRC Connection Release message carries the system information of the neighboring GERAN cell. For details, see Figure 7-20.

Figure 7-20 The RRC Connection Release message during flash CSFB to GERAN


Check the status of the RIM procedure towards neighboring GERAN cells by running the DSP GERANRIMINFO command. If the ID of a neighboring GERAN cell is displayed in the command output, the eNodeB has obtained the system information of this neighboring GERAN cell.

Counter Observation

The counter listed in Table 7-52 can be viewed to check whether the feature has taken effect.

Table 7-52 Performance counters for observing flash CSFB to GERANFunctions Counter ID Counter Name Description

Flash CS Fallback to GERAN

1526728706 L.FlashCSFB.E2G Number of procedures for flash CSFB to GERAN

RIM during flash CSFB to GERAN

1526729661 L.RIM.SI.E2G.Req Number of times the eNodeB sends a system information request to a GERAN

1526729662 L.RIM.SI.E2G.Resp Number of times the eNodeB receives a system information response from a GERAN

1526729663 L.RIM.SI.E2G.Update Number of times the eNodeB receives a system information update from a GERAN

7.10.7 Deactivation



Table 7-53 Parameters for deactivating flash CSFB to GERANMO Sheet in the

Summary Data FileParameter Group Remarks

ENodeBAlgoSwitch User-defined sheet HoAlgoSwitch Set GeranFlashCsfbSwitch under the HoAlgoSwitch parameter to 0.



Using MML Commands

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


MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranFlashCsfbSwitch-0;





7.11 LOFD-081283 Ultra-Flash CSFB to GERANThis section provides engineering guidelines for LOFD-081283 Ultra-Flash CSFB to GERAN.

7.11.1 When to Use This Feature

The LOFD-001034 CS Fallback to GERAN feature is recommended in scenarios where the eNodeB, MME, and MSC are provided by Huawei, and a proportion of UEs in the live network support SRVCC from E-UTRAN to GERAN. It is recommended that this feature be activated in GERAN and E-UTRAN overlapping coverage areas.


Before deploying this feature, collect the following information:

Check whether LOFD-001034 CS Fallback to GERAN has been activated. Check whether the eNodeB, MME, and MSC in the network are provided by Huawei

and they all support this feature.

Check whether a proportion of UEs in the live network support SRVCC from E-UTRAN to GERAN.

7.11.3 Requirements


This feature is a Huawei-proprietary feature and requires that the eNodeB, MME, and MSC are provided by Huawei and support this feature. This feature is used with MME11.0 and MSC11.0.

License


Table 7-54 License information for ultra-flash CSFB to GERANFeature


Control Item

NE Sales Unit

LOFD-081283

Ultra-Flash CSFB to GERAN

LT1SUFCSFB20 Ultra-Flash CSFB to GERAN


7.11.4 Precautions

This feature is a Huawei-proprietary feature and is not supported by devices provided by other vendors. In addition, this feature must first be activated on the BSC, MME, and MSC, and then be activated on the eNodeB. This is because this feature is triggered by the eNodeB and this avoids CSFB failures.



This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. 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: data sources:




Required Data

The required data is the same as that for LOFD-001034 CS Fallback to GERAN. For details, see 7.8.5.1 Data Preparation.


The following table describes the parameters that must be set in the ENodeBAlgoSwitch MO to set the eNodeB-level handover mode and handover algorithm switches for ultra-flash CSFB to GERAN.

Parameter

Name


Setting Notes




Select the GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option.

The following table describes the parameters that must be set in the CellHoParaCfg MO to set the cell-level blind handover mode switches for ultra-flash CSFB to GERAN.

Parameter Name


Setting Notes


CellHoParaCfg.HoModeSwitch


To activate cell-level blind handovers, select the BlindHoSwitch(BlindHoSwitch) option. To activate blind handovers, you still need to activate eNodeB-level blind handovers.

The following table describes the parameter that must be set in the GeranExternalCell MO to set the capability of external GERAN cells when some GERAN cells do not support ultra-flash CSFB to GERAN.

Parameter Name


Setting Notes

Ultra-Flash CSFB capability indicator

GeranExternalCell.UltraFlashCsfbInd Network plan (negotiation required)

Clear the UltraFlashCsfbInd check box for external GERAN cells that do not support ultra-flash CSFB to GERAN.

The following table describes the parameter that must be set in the CellDrxPara MO to set the DRX switch for measurements when UEs support DRX-based measurements.

Parameter Name


Setting Notes

DRX switch for measurements

CellDrxPara.DrxForMeasSwitch Network plan (negotiation required)

When the network supports measurements and UEs support DRX

Parameter Name


Setting Notes

measurements well, measurement delays are significantly reduced and the customer can tolerate the impact on services during measurements.

To enable the DRX switch for measurements, set DrxForMeasSwitch to 1.

Long DRX Cycle for Measurement

CellDrxPara.LongDrxCycleForMeas Network plan (negotiation required)

This parameter specifies the length of the long DRX cycle specific to GERAN measurement.

On Duration Timer for Measurement

CellDrxPara.OnDurTimerForMeas Network plan (negotiation required)

This parameter specifies the length of the On Duration Timer specific to GERAN measurement.

DRX Inactivity Timer for Measurement

CellDrxPara.DrxInactTimerForMeas Network plan (negotiation required)

This parameter specifies the length of the DRX Inactivity Timer specific to GERAN measurement.

DRX Retransmission Timer for Measurement

CellDrxPara.DrxReTxTimerForMeas Network plan (negotiation required)

This parameter specifies the length of the DRX Retransmission Timer specific to GERAN measurement.

Short DRX Switch for Measurement

CellDrxPara.ShortDrxSwForMeas Network plan (negotiation required)

This parameter specifies whether short-period DRX is enabled for GERAN

Parameter Name


Setting Notes

measurements.

Short DRX Cycle for Measurement

CellDrxPara.ShortDrxCycleForMeas Network plan (negotiation required)

This parameter specifies the length of the short DRX cycle specific to GERAN measurement.

Short Cycle Timer for Measurement

CellDrxPara.ShortCycleTimerForMeas


This parameter specifies the length of the Short Cycle Timer specific to GERAN measurement.


Parameter Name


Setting Notes

Ue Compatibility Switch

GlobalProcSwitch.UeCompatSwitch


Select the UltraFlashCsfbComOptSw option of the parameter when UEs on the network do not support ultra-flash CSFB.

When the MME provided by Huawei allows IMEI whitelist configurations for ultra-flash CSFB and the option is selected, the eNodeB performs ultra-flash CSFB on UEs in the IMEI whitelist. Therefore, delete the UEs that do not support ultra-flash CSFB from the whitelist before selecting the option. Otherwise, keep the option unselected.







Table 7-55 Parameters for ultra-flash CSFB to UTRAN


Parameter Group

Remarks


















Parameter Group

Remarks










GlobalProcSwitch User-defined sheet. GlobalProcSwitch is recommended.




Batch Activation






Using MML Commands

Basic scenario


2. Run the MOD ENODEBALGOSWITCH command with the GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the Handover Algo switch parameter selected.

3. (Optional) Run the MOD GlobalProcSwitch command with the IratMeasCfgTransSwitch option of the ProtocolMsgOptSwitch parameter selected if you need to optimize "G2L Fast Return after Ultra-Flash CSFB to UTRAN" based on the E-UTRA frequency capability supported by UEs. The eNodeB transfers E-UTRA frequency information supported by UEs to the BSC during the SRVCC.

4. (Optional) Run the MO GERANEXTERNALCELL command with the Ultra-Flash CSFB capability indicator parameter set to BOOLEAN_FALSE if some external GERAN cells do not support ultra-flash CSFB to UTRAN.

5. (Optional) Run the MOD CELLDRXPARA command with the DRX for Measurement Switch parameter set to ON(On) if UEs support DRX-based measurements.

(Optional) Perform the following operation if UE compatibility risks exist after Ultra-Flash CSFB is activated.

1. Run the MOD GLOBALPROCSWITCH command with the UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw) option of the UE Compatibility Switch parameter selected.


Basic scenario MOD ENODEBALGOSWITCH: HoAlgoSwitch= GeranUltraFlashCsfbSwitch-1; MOD GlobalProcSwitch: ProtocolMsgOptSwitch=IratMeasCfgTransSwitch-1; MOD GERANEXTERNALCELL: Mcc="302", Mnc="220", GeranCellId=2, Lac=12,

UltraFlashCsfbInd=BOOLEAN_TRUE;MOD CELLDRXPARA: LocalCellId=0, DrxForMeasSwitch=1;LongDrxCycleForMeas=SF160, OnDurTimerForMeas=PSF2, DrxInactTimerForMeas=PSF2, DrxReTxTimerForMeas=PSF4, ShortDrxSwForMeas=1, ShortDrxCycleForMeas=SF20, ShortCycleTimerForMeas=1;

(Optional) Perform the following operation if UE compatibility risks exist after Ultra-Flash CSFB is activated.

MOD GLOBALPROCSWITCH: UeCompatSwitch= UltraFlashCsfbComOptSw-1;



To use signaling tracing to verify whether this feature has been activated, perform the following steps:

1. As shown in the following figure, the HANDOVER REQUIRED message sent from the eNodeB to the MME over the S1 interface contains handover request cause values "cs-fallback-triggered" and "sRVCCHOIndication-cSonly (1)", indicating that a ultra-flash CSFB to GERAN is triggered successfully.

2. The UE falls back to a GERAN cell and completes the call.

Figure 7-22 HANDOVER REQUIRED message

Counter Observation

The counter listed in the following table can be monitored to check whether the feature has been activated.

Table 7-56 Performance counters for ultra-flash CSFB to GERANCounter ID Counter Name Description

1526733006 L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut Number of SRVCC-based outgoing handover attempts from E-UTRAN to GERAN for ultra-flash CSFB to GERAN

7.11.7 Deactivation


Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 7.11.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to the following table.

Table 7-57 Parameter related to ultra-flash CSFB to GERANMO Sheet in the


GroupSetting Notes


HoAlgoSwitch To deactivate the Ultra-Flash CSFB to GERAN feature

Deselect the GeranUltraFlashCsfbSwitch option.



Using MML Commands

Run the MOD ENODEBALGOSWITCH command with the GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch) option of the Handover Algo switch parameter deselected.


MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranUltraFlashCsfbSwitch-0;


Table 7-58 lists the counters used to monitor the performance of ultra-flash CSFB to GERAN

Table 7-58 Counters related to ultra-flash CSFB to GERANCounter ID Counter Name Description

1526733006 L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut Number of SRVCC-based outgoing handover attempts from E-UTRAN to GERAN for ultra-flash CSFB

1526733007 L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut Number of SRVCC-


based EUTRAN-to-GERAN outgoing handover executions for ultra-flash CSFB to to GERAN

1526733008 L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut Number of successful SRVCC-based EUTRAN-to-GERAN outgoing handovers for ultra-flash CSFB to GERAN

1526733009 L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp Number of abnormal responses from the MME during EUTRAN-to-GERAN handovers for ultra-flash CSFB to GERAN

Success rate of handovers for ultra-fast CSFB to GERAN = (L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut - L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp)/L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut



7.12 LOFD-001069 CS Fallback with LAI to GERANThis section provides engineering guidelines for LOFD-001069 CS Fallback with LAI to GERAN.

7.12.1 When to Use CS Fallback with LAI to GERAN

Use LOFD-001069 CS Fallback with LAI to GERAN when both of the following conditions are met:

LOFD-001034 CS Fallback to GERAN has been enabled. The E-UTRAN cell has neighboring GERAN cells that belong to different PLMNs

and supports inter-PLMN handovers, or the E-UTRAN cell has neighboring GERAN cells that have different LACs.

If both LOFD-001033 CS Fallback to UTRAN and LOFD-001034 CS Fallback to GERAN have been enabled, you are advised to enable both LOFD-001069 CS Fallback with LAI to GERAN and LOFD-001068 CS Fallback with LAI to UTRAN.


Collect information about whether LOFD-001034 CS Fallback to GERAN has been activated.


Collect the versions and configurations of the NEs in the E-UTRAN, GERAN, and core networks, and ensure that they all support CSFB and the MME supports LAI delivery. Table 7-59 describes the requirements of CSFB with LAI to GERAN for the core networks.

Table 7-59 Requirements of CSFB with LAI to GERAN for core networks

NE Requirement

MME Supports:

o SGs interface to the MSCo LAI selection based on the TAI of

the serving cello MSC-initiated pagingo PLMN selection and reselectiono Combined EPS/IMSI attach,

combined EPS/IMSI detach, and combined TAU/LAU

o CS signaling message routingo SMS over SGso LAI delivery

MSC Supports:

o Combined EPS/IMSI attacho SMS over SGso Paging message forwarding over

the SGs interface



o Supported frequency bandso Whether the UEs support redirection from E-UTRAN to GERANo Whether the UEs support PS handover from E-UTRAN to GERAN

o Whether the UEs support GERAN measurements


7.12.3 Requirements


For this feature, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be PS9.2 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 CSFB with LAI to GERAN.

License


Table 7-60 License information for CSFB with LAI to GERANFeature ID Feature Name Model License


LOFD-001069

CS Fallback with LAI to GERAN

LT1S0CSFLG00 CS Fallback with LAI to GERAN


7.12.4 Precautions

None


This feature is automatically activated when two conditions are met: The license for this feature has been purchased. CSFB to GERAN has been activated.


Data preparation for activating CSFB with LAI to GERAN is the same as that for activating CSFB to GERAN. For details, see 7.8.5.1 Data Preparation.


For details, see 7.8.5.2 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.


For details, see 7.8.5.3 Using the CME to Perform Batch Configuration for Existing eNodeBs.


For details, see 7.8.5.4 Using the CME to Perform Single Configuration.


For details, see 7.8.5.6 Using MML Commands.



1. Configure two neighboring GERAN cells with different LAIs for an E-UTRAN cell, and enable the MME to include only one of the two LAIs in the instructions that will be delivered to the eNodeB.

2. Ensure that the signal strengths of the two GERAN cells both reach the threshold for event B1. You can query the threshold by running the LST INTERRATHOGERANGROUP command.

3. Enable a UE to camp on the E-UTRAN cell and make a voice call.4. Enable the UE to camp on the E-UTRAN cell and receive a voice call.

You can observe the signaling procedure for CSFB with LAI to GERAN, which is similar to that for CSFB to GERAN described in 7.9.6 Activation Observation. The difference is that the Initial Context Setup Request or UE Context Mod Request message carries the LAI that the MME delivers to the eNodeB, as shown in the following figure:

Figure 7-23 LAI signaling tracing

7.12.7 Deactivation

CSFB with LAI to GERAN is automatically deactivated when its license or CSFB to GERAN is deactivated. For details about how to deactivate CSFB to GERAN, see 7.8.7 Deactivation.





7.13 LOFD-001089 CS Fallback Steering to GERANThis section provides engineering guidelines for LOFD-001089 CS Fallback Steering to GERAN.

7.13.1 When to Use CS Fallback Steering to GERAN

Use LOFD-001089 CS Fallback Steering to GERAN to improve the network efficiency when both of the following conditions are met:

LOFD-001034 CS Fallback to GERAN has been activated. An operator has multiple GERAN frequencies and has different handover policies for

CS-only services and combined CS+PS services.

If the operator owns both UTRAN and GERAN, you can also activate LOFD-001088 CS Fallback Steering to UTRAN to improve the network efficiency.


1. Collect information about whether LOFD-001034 CS Fallback to GERAN has been activated.

2. Collect the following information about the UEs that support GSM and LTE on the live network:

o Supported frequency bandso Whether the UEs support redirection from E-UTRAN to GERANo Whether the UEs support PS handover from E-UTRAN to GERANo Whether the UEs support CCO from E-UTRAN to GERANo Whether the UEs support GERAN measurements

This information is used to configure neighboring GERAN cells and to determine whether to perform CSFB based on handover, redirection, or CCO. For details, see Inter-RAT Mobility Management in Connected Mode Feature Parameter Description.

3. Collect information about the frequencies and frequency policies of the GERAN. Frequency policies must be the same for GERAN and E-UTRAN.

4. If LOFD-001088 CS Fallback Steering to UTRAN is also to be activated, consider the UTRAN frequencies when making frequency policies.

7.13.3 Requirements


For CSFB steering to GERAN, the eNodeB must collaborate with core-network equipment. If the core-network equipment is provided by Huawei, the version must be SAE1.2 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 CSFB steering to GERAN.

License


Table 7-61 License information for CSFB steering to GERANFeature ID Feature Name Model License

Control Item

NE Sales Unit

LOFD-001089 CS Fallback Steering to GERAN

LT1S0CFBSG00 CS Fallback Steering to GERAN


7.13.4 Precautions

None








Required Data

The required data is the same as that for CS Fallback to GERAN. For details, see 7.8.5.1 Data Preparation.


The following table describes the parameter that must be set in the ENodeBAlgoSwitch MO to enable CSFB steering to GERAN.

Parameter

Name


Setting Notes




Select the GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) check box under this parameter.

The following table describes the parameters that must be set in the CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for RRC_CONNECTED UEs.

Parameter Name


Setting Notes

CN Operator ID






Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the highest-priority RAT to be considered in blind handovers for CSFB.




Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in blind handovers for CSFB. Ensure that this parameter is set to a different value from the

Parameter Name


Setting Notes

InterRatHighestPri and InterRatLowestPri parameters.








The following table describes the parameters that must be set in the CSFallBackBlindHoCfg MO to set RAT priorities for CSFB triggered for RRC_IDLE UEs.

Parameter Name


Setting Notes

CSFB Highest priority InterRat for Idle UE

CSFallBackBlindHoCfg.IdleCsfbHighestPri


Set this parameter based on the network plan. This parameter is set to UTRAN by default and specifies the high-priority RAT to be considered in CSFB for UEs in idle mode.

Parameter Name


Setting Notes

CSFB Second priority InterRat for Idle UE

CSFallBackBlindHoCfg.IdleCsfbSecondPri


Set this parameter based on the network plan. This parameter is set to GERAN by default and specifies the second-highest-priority RAT to be considered in CSFB for UEs in idle mode. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatLowestPri parameters.

CSFB Lowest priority InterRat for Idle UE

CSFallBackBlindHoCfg.IdleCsfbLowestPri


Set this parameter based on the network plan. This parameter is set to CDMA2000 by default and specifies the low-priority RAT to be considered in CSFB for UEs in idle mode. Ensure that this parameter is set to a different value from the InterRatHighestPri and InterRatSecondPri parameters.

The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO to set the CSFB policy for RRC_CONNECTED UEs.

Parameter Name


Setting Notes

CSFB handover policy

CSFallBackPolicyCfg.CsfbHoPolicyCfg Network plan (negotiation

Set this parameter based on the network plan. The

Parameter Name


Setting Notes

Configuration not required)

default values are REDIRECTION, CCO_HO, and PS_HO. You are advised to set this parameter based on the UE capabilities and network capabilities. For details about how to select a CSFB handover policy, see 4.7 Handover Execution.

The following table describes the parameter that must be set in the CSFallBackPolicyCfg MO to set the CSFB policy for RRC_IDLE UEs.

Parameter Name


Setting Notes

CSFB handover policy Configuration for idle ue

CSFallBackPolicyCfg.IdleModeCsfbHoPolicyCfg


Set this parameter based on the network plan. The default values are REDIRECTION, CCO_HO, and PS_HO. You are advised to set this parameter based on the UE capabilities and network capabilities. For details about how to select a CSFB handover policy, see 4.7 Handover Execution.








Table 7-62 Parameters for CSFB steering to GERANMO Sheet in the Summary



Handover Algo switch This parameter must be customized on a list-type sheet of the template.


CN Operator ID, Highest priority InterRat, Second priority InterRat, Lowest priority InterRat, CSFB Highest priority InterRat for Idle UE, CSFB Second priority InterRat for Idle UE, CSFB Lowest priority InterRat for Idle UE


CSFallBackPolicyCfg User-defined sheet. CSFallBackPolicyCfg is recommended.

CSFB handover policy Configuration, CSFB handover policy Configuration for idle ue








Using MML Commands

The configuration is just an example, and configurations on the live network can differ from this example. For MML command settings in scenarios where the UTRAN and GERAN cover the same area but only the GERAN provides contiguous coverage, see 7.6.5 Data Preparation and Feature Activation.

The prerequisite is that CSFB to GERAN has been activated.

1. Run the MOD ENODEBALGOSWITCH command with the GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch) check box selected under the Handover Algo switch parameter.

2. Run the MOD CSFALLBACKBLINDHOCFG command with the Highest priority InterRat, Second priority InterRat, CSFB Highest priority InterRat for Idle UE,

and CSFB Second priority InterRat for Idle UE parameters to UTRAN, GERAN, GERAN, and UTRAN, respectively.

3. Run the MOD CSFALLBACKPOLICYCFG command with the PS_HO check box selected under the CSFB handover policy Configuration parameter and the REDIRECTION check box selected under the CSFB handover policy Configuration for idle ue parameter.


MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-1;MOD CSFALLBACKBLINDHOCFG: CnOperatorId=0, InterRatHighestPri=UTRAN,InterRatSecondPri=GERAN,IdleCsfbHighestPri=GERAN,IdleCsfbSecondPri=UTRAN;MOD CSFALLBACKPOLICYCFG: CsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-1, IdleModeCsfbHoPolicyCfg=REDIRECTION-1&CCO_HO-0&PS_HO-0;


The signaling procedure is the same as that for CSFB to GERAN. After CS Fallback Steering to GERAN is used, check whether it works as expected.

The activation observation procedure for CSFB steering to GERAN is as follows:

1. Check that the UE supports redirection-based CSFB and handover-based CSFB.2. Set CSFB policies for RRC_IDLE UEs and RRC_CONNECTED UEs to redirection

and handover, respectively.3. Enable the UE to initiate a voice call in idle mode and in connected mode.4. Observe the counters L.CSFB.E2G, L.RRCRedirection.E2G.CSFB, and

L.IRATHO.E2G.CSFB.ExecAttOut. If the values of the counters increase by 2, 1, and 1, respectively, CSFB steering to GERAN has been activated.

If CSFB steering to UTRAN has also been activated, the activation observation procedure is as follows:

1. Check that the UE supports CSFB to GERAN and CSFB to UTRAN.2. Set GERAN as the highest-priority RAT for CSFB triggered for RRC_IDLE UEs and

UTRAN as the highest-priority RAT for CSFB triggered for RRC_CONNECTED UEs.

3. Enable the UE to initiate a voice call in idle mode and in connected mode.4. Observe the counters L.CSFB.E2W and L.CSFB.E2G. If both the values increase by

1, both CSFB steering to UTRAN and CSFB steering to GERAN have been activated.

7.13.7 Deactivation



Table 7-63 Parameters for deactivating CSFB steering to GERANMO Sheet in the


GroupRemarks


HoAlgoSwitch Set GeranCsfbSteeringSwitch under the HoAlgoSwitch parameter to 0.



Using MML Commands

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


MOD ENODEBALGOSWITCH: HoAlgoSwitch=GeranCsfbSteeringSwitch-0;





7.14 Troubleshooting

7.14.1 CSFB Calling Procedure Failure

Fault Description

A UE performs cell reselection to an inter-RAT neighboring cell directly after initiating a voice call in an E-UTRAN cell, and the S1 interface tracing result shows that CSFB is not triggered.

Fault Handling

1. Create an S1 interface tracing task, use the UE to camp on the E-UTRAN cell again, and check whether the value of the information element (IE) ePS-attach-type-value is "combined-attach" in the traced Attach Request message.

o If so, go to 2.o If not, replace the UE with one that supports combined EPS/IMSI attach, and

try again.2. Check whether the traced Attach Accept message includes the IE cs-domain-not-

available.o If it does, go to 3.o If not, contact Huawei technical support.

3. Contact the vendors of core network NEs to ensure the following:o Attach procedures to the CS domain are allowed according to the subscription

data on the HSS.o The core network supports CSFB.o The SGs interface is correctly configured.

7.14.2 eNodeB Receiving No Measurement Report

Fault Description

An eNodeB delivers an RRC Connection Reconfiguration message for measurement control to a UE that has initiated a voice call in the LTE network, but the eNodeB does not receive a measurement report.

Fault Handling

1. Check whether the RRC Connection Reconfiguration message contains B1-related measurement configurations and whether the information about the inter-RAT systems in the configuration is correct.

o If it is, go to 2o If not, rectify the faults and try again.

2. Check whether the coverage of the inter-RAT neighboring cell is satisfactory. If the coverage is unsatisfactory, adjust B1-related parameters or use CSFB based on blind handovers.

For details about how to adjust B1-related parameters, see Inter-RAT Mobility Management in Connected Mode.

7.14.3 CSFB Blind Handover Failure

Fault Description

Even when blind handovers are configured as the preferred choice according to the operator policies, instead of triggering a blind handover for CSFB, an eNodeB delivers an inter-RAT measurement configuration to a UE that has initiated a voice call.

Fault Handling

1. Run the LST ENODEBALGOSWITCH command and check the setting of BlindHoSwitch under the Handover Mode Switch parameter. If BlindHoSwitch is Off, run the MOD ENODEBALGOSWITCH command with the

BlindHoSwitch(BlindHoSwitch) check box under the Handover Mode Switch parameter selected.

2. Run the LST CELLHOPARACFG command and check the setting of BlindHoSwitch under the Handover Mode Switch parameter. If BlindHoSwitch is Off, run the MOD CELLHOPARACFG command with the BlindHoSwitch(BlindHoSwitch) check box under the Handover Mode Switch parameter selected. In addition, check the CSFB mechanism and perform the following:

o If CSFB to UTRAN is required, go to 3.o If CSFB to GERAN is required, go to 4.

3. Run the LST UTRANNCELL command and check whether Blind handover priority is 0 for a neighboring UTRAN cell that is supposed to accept incoming blind handovers.

o If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case, run the MOD UTRANNCELL command with the Blind handover priority parameter set to a value other than 0.

o If Blind handover priority is not 0, contact Huawei technical support.4. Run the LST GERANNCELL command and check whether Blind handover

priority is 0 for a neighboring GERAN cell that is supposed to accept incoming blind handovers.

o If Blind handover priority is 0, blind handovers to this cell are not allowed. In this case, run the MOD GERANNCELL command with the Blind handover priority parameter set to a value other than 0.

o If Blind handover priority is not 0, contact Huawei technical support.

7.14.4 CSFB Handover Failure

Fault Description

During CSFB to UTRAN procedures with the handover policy set to PS HO, the handover preparation success rate is low.

Table 7-64 Counters related to the handover preparation success rateCounter ID Counter Name Description

1526728504 L.IRATHO.E2W.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover preparation attempts from E-UTRAN to WCDMA network

1526728505 L.IRATHO.E2W.CSFB.ExecAttOut Number of CSFB-based inter-RAT handover execution attempts from E-UTRAN to WCDMA network

Fault Handling

Here uses the CSFB to UTRAN as an example to describe the fault handling procedure. Similar counters are provided for CSFB to GERAN or to other systems.

1. View the counters listed in Table 7-65 to check the cause for the low handover preparation success rate.

Table 7-65 Counters related to outgoing handover preparation failures


1526730076 L.IRATHO.E2W.CSFB.Prep.FailOut.MME Number of CSFB-based outgoing handover preparation failures from E-UTRAN to WCDMA network because of the MME side causes

1526730077 L.IRATHO.E2W.CSFB.Prep.FailOut.PrepFailure Number of CSFB-based outgoing handover preparation failures from E-UTRAN to WCDMA network because of the response of handover preparation failure from WCDMA network

1526730078 L.IRATHO.E2W.CSFB.Prep.FailOut.NoReply Number of CSFB-based outgoing handover preparation failures from E-UTRAN to WCDMA network because of no response from WCDMA network

2. Analyze the failure cause based on the values of the preceding counters for each NE.

8 ParametersTable 8-1 Parameters

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

eNBRsvdPara

RsvdSwPara1

MOD ENBRSVDPARA

LST ENBRSVDPARA

None None Meaning:

Indicates reserved 32-bit switch parameter 1 that is reserved for future requirements.

Note on parameter replacement: Reserved parameters are temporarily used in patch versions and will be replaced with new parameters. For example, the ID of a new parameter can signify the parameter function. Therefore, avoid using this parameter.

GUI Value Range: RsvdSwPara1_bit1(ReservedSwitchParameter1_bit1), RsvdSwPara1_bit2(ReservedSwitchParameter1_bit2), RsvdSwPara1_bit3(ReservedSwitchParameter1_bit3), RsvdSwPara1_bit4(ReservedSwitchParameter1_bit4), RsvdSwPara1_bit5(ReservedSwitchParameter1_bit5), RsvdSwPara1_bit6(ReservedSwitchParameter1_bit6), RsvdSwPara1_bit7(ReservedSwitchParameter1_bit7), RsvdSwPara1_bit8(ReservedSwitchParameter1_bit8), RsvdSwPara1_bit9(ReservedSwitchParameter1_bit9), RsvdSwPara1_bit10(ReservedSwitchParameter1_bit10), RsvdSwPara1_bit11(ReservedSwitchParameter1_bit11), RsvdSwPara1_bit12(ReservedSwitchParameter1_bit12),

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

RsvdSwPara1_bit13(ReservedSwitchParameter1_bit13), RsvdSwPara1_bit14(ReservedSwitchParameter1_bit14), RsvdSwPara1_bit15(ReservedSwitchParameter1_bit15), RsvdSwPara1_bit16(ReservedSwitchParameter1_bit16), RsvdSwPara1_bit17(ReservedSwitchParameter1_bit17), RsvdSwPara1_bit18(ReservedSwitchParameter1_bit18), RsvdSwPara1_bit19(ReservedSwitchParameter1_bit19), RsvdSwPara1_bit20(ReservedSwitchParameter1_bit20), RsvdSwPara1_bit21(ReservedSwitchParameter1_bit21), RsvdSwPara1_bit22(ReservedSwitchParameter1_bit22), RsvdSwPara1_bit23(ReservedSwitchParameter1_bit23), RsvdSwPara1_bit24(ReservedSwitchParameter1_bit24), RsvdSwPara1_bit25(ReservedSwitchParameter1_bit25), RsvdSwPara1_bit26(ReservedSwitchParameter1_bit26), RsvdSwPara1_bit27(ReservedSwitchParameter1_bit27), RsvdSwPara1_bit28(ReservedSwitchParameter1_bit28), RsvdSwPara1_bit29(ReservedSwitchParameter1_bit29), RsvdSwPara1_bit30(ReservedSwitchParameter1_bit30), RsvdSwPara1_bit31(ReservedSwitchParameter1_bit31), RsvdSwPara1_bit32(ReservedSwitchParameter1_bit32)

Unit: None

Actual Value Range: RsvdSwPara1_bit1,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

RsvdSwPara1_bit2, RsvdSwPara1_bit3, RsvdSwPara1_bit4, RsvdSwPara1_bit5, RsvdSwPara1_bit6, RsvdSwPara1_bit7, RsvdSwPara1_bit8, RsvdSwPara1_bit9, RsvdSwPara1_bit10, RsvdSwPara1_bit11, RsvdSwPara1_bit12, RsvdSwPara1_bit13, RsvdSwPara1_bit14, RsvdSwPara1_bit15, RsvdSwPara1_bit16, RsvdSwPara1_bit17, RsvdSwPara1_bit18, RsvdSwPara1_bit19, RsvdSwPara1_bit20, RsvdSwPara1_bit21, RsvdSwPara1_bit22, RsvdSwPara1_bit23, RsvdSwPara1_bit24, RsvdSwPara1_bit25, RsvdSwPara1_bit26, RsvdSwPara1_bit27, RsvdSwPara1_bit28, RsvdSwPara1_bit29, RsvdSwPara1_bit30, RsvdSwPara1_bit31, RsvdSwPara1_bit32

Default Value: RsvdSwPara1_bit1:Off, RsvdSwPara1_bit2:Off, RsvdSwPara1_bit3:Off, RsvdSwPara1_bit4:Off, RsvdSwPara1_bit5:Off, RsvdSwPara1_bit6:Off, RsvdSwPara1_bit7:Off, RsvdSwPara1_bit8:Off, RsvdSwPara1_bit9:Off, RsvdSwPara1_bit10:Off, RsvdSwPara1_bit11:Off, RsvdSwPara1_bit12:Off,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

RsvdSwPara1_bit13:Off, RsvdSwPara1_bit14:Off, RsvdSwPara1_bit15:Off, RsvdSwPara1_bit16:Off, RsvdSwPara1_bit17:Off, RsvdSwPara1_bit18:Off, RsvdSwPara1_bit19:Off, RsvdSwPara1_bit20:Off, RsvdSwPara1_bit21:Off, RsvdSwPara1_bit22:Off, RsvdSwPara1_bit23:Off, RsvdSwPara1_bit24:Off, RsvdSwPara1_bit25:Off, RsvdSwPara1_bit26:Off, RsvdSwPara1_bit27:Off, RsvdSwPara1_bit28:Off, RsvdSwPara1_bit29:Off, RsvdSwPara1_bit30:Off, RsvdSwPara1_bit31:Off, RsvdSwPara1_bit32:Off

GlobalProcSwitch

UeCompatSwitch

MOD GLOBALPROCSWITCH

LST GLOBALPROCSWITCH

None None Meaning:

Indicates whether to enable compatibility optimization functions for UEs to control the differentiated handling of abnormal UEs.

AbnormalUeHandleSwitch: This option is used to control whether to enable handling of abnormal UEs.This function is enabled only if this option is selected.

UltraFlashCsfbComOptSw: This option is used to control whether to enable the optimization of UE incompatibility risks in ultra-flash CSFB. If this option is selected, an eNodeB triggers an ultra-flash CSFB based on the private IE SRVCC based

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

eCSFB operation possible that the MME sends to the eNodeB. If this option is not selected, the eNodeB does not trigger an ultra-flash CSFB procedure based on this IE.

GUI Value Range: AbnormalUeHandleSwitch(AbnormalUeHandleSwitch), UltraFlashCsfbComOptSw(UltraFlashCsfbComOptSw)

Unit: None

Actual Value Range: AbnormalUeHandleSwitch, UltraFlashCsfbComOptSw

Default Value: AbnormalUeHandleSwitch:Off, UltraFlashCsfbComOptSw:Off

CellHoParaCfg

HoModeSwitch

MOD CELLHOPARACFG

LST CELLHOPARACFG

LOFD-001033 / LOFD-001034 / TDLOFD-001033 / TDLOFD-001034

CS Fallback to UTRAN / CS Fallback to GERAN / CS Fallback to UTRAN / CS Fallback to GERAN

Meaning:

Indicates the handover method switches based on which the eNodeB determines handover policies.

BlindHoSwitch: This option controls whether to enable blind handovers for CSFB. If both this option and the BlindHoSwitch option of the Handover Mode switch parameter of the ENodeBAlgoSwitch MO are selected, blind handovers for CSFB are enabled.

GUI Value Range: BlindHoSwitch(BlindHoSwitch)

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

Unit: None

Actual Value Range: BlindHoSwitch

Default Value: BlindHoSwitch:Off

GeranExternalCell

UltraFlashCsfbInd

ADD GERANEXTERNALCELL

MOD GERANEXTERNALCELL

LST GERANEXTERNALCELL

LOFD-081283 / TDLOFD-081203


Meaning: Indicates whether an external GERAN cell supports ultra-flash CSFB to GERAN. If this parameter is set to BOOLEAN_TRUE, the external GERAN cell supports ultra-flash CSFB to GERAN. If this parameter is set to BOOLEAN_FALSE, the external GERAN cell does not support ultra-flash CSFB to GERAN.

GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)

Unit: None

Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE

Default Value: BOOLEAN_TRUE(True)

ENodeBAlgoSwitch

HoAlgoSwitch

MOD ENODEBALGOSWITCH

LST ENODEBALGOSWITCH

LBFD-00201801 / TDLBFD-00201801

LBFD-00201802 / TDLBF

Coverage Based Intra-frequency Handover

Distance Based

Meaning: Indicates whether to enable handover algorithms. The switches are described as follows: IntraFreqCoverHoSwitch: If this switch is on, coverage-based intra-frequency handovers are enabled to ensure service continuity. If this switch is off, coverage-based intra-frequency handovers are disabled.

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

D-00201802

LBFD-00201804 / TDLBFD-00201804

LBFD-00201805 / TDLBFD-00201805

LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

LOFD-001035 / TDLOFD-001035

LOFD-001052 / TDLOF

Inter-frequency Handover

Service Based Inter-frequency Handover

CS Fallback to UTRAN


CS Fallback to CDMA2000 1xRTT

Flash CS Fallback to UTRAN

Flash CS

InterFreqCoverHoSwitch: If this switch is on, coverage-based inter-frequency handovers are enabled to ensure service continuity. If this switch is off, coverage-based inter-frequency handovers are disabled. UtranCsfbSwitch: If this switch is on, CSFB to UTRAN is enabled and UEs can fall back to UTRAN. If this switch is off, CSFB to UTRAN is disabled. GeranCsfbSwitch: If this switch is on, CSFB to GERAN is enabled and UEs can fall back to GERAN. If this switch is off, CSFB to GERAN is disabled. Cdma1xRttCsfbSwitch: If this switch is on, CSFB to CDMA2000 1xRTT is enabled and UEs can fall back to CDMA2000 1xRTT. If this switch is off, CSFB to CDMA2000 1xRTT is disabled. UtranServiceHoSwitch: If this switch is on, service-based handovers to UTRAN are enabled and UEs running a specific type of services can be handed over to UTRAN. If this switch is off, service-based handovers to UTRAN are disabled. GeranServiceHoSwitch: If this switch is on, service-based handovers to GERAN are enabled and UEs running a specific type of services can be handed over to GERAN. If this switch is off, service-based handovers to GERAN are disabled. CdmaHrpdServiceHoSwitch: If

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

D-001052

LOFD-001053 / TDLOFD-001053

LOFD-001088 / TDLOFD-001088

LOFD-001089 / TDLOFD-001089

LOFD-001090 / TDLOFD-001090

LOFD-001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020

Fallback to GERAN


CS Fallback Steering to GERAN

Enhanced CS Fallback to CDMA2000 1xRTT

PS Inter-RAT Mobility between E-UTRAN and UTRAN

this switch is on, service-based handovers to CDMA2000 HRPD cells are enabled and UEs running a specific type of services can be handed over to CDMA2000 HRPD cells. If this switch is off, service-based handovers to CDMA2000 HRPD cells are disabled.This parameter is unavailable in this version. Cdma1xRttServiceHoSwitch: If this switch is on, service-based handovers to CDMA2000 1xRTT are enabled and UEs running a specific type of services can be handed over to CDMA2000 1xRTT. If this switch is off, service-based handovers to CDMA2000 1xRTT are disabled.This parameter is unavailable in this version. UlQualityInterRATHoSwitch: If this switch is on, UL-quality-based inter-RAT handovers are enabled and UEs can be handed over to inter-RAT cells to ensure service continuity when the UL signal quality is poor. If this switch is off, UL-quality-based inter-RAT handovers are disabled. InterPlmnHoSwitch: If this switch is on, inter-PLMN handovers are enabled and UEs can be handed over to cells in other PLMNs. If this switch is off, inter-PLMN handovers are disabled. UtranFlashCsfbSwitch: This switch takes effect only when UtranCsfbSwitch is on. If UtranFlashCsfbSwitch is on, flash CSFB to UTRAN is enabled and the eNodeB sends system information of

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LOFD-001043 / TDLOFD-001043

LOFD-001046 / TDLOFD-001046

LOFD-001072 / TDLOFD-001072

LOFD-001073 / TDLOFD-001073

TDLBFD-002018

TDLOFD-001022

TDLOFD-070228

LOFD-081283 / TDLOFD-

PS Inter-RAT Mobility between E-UTRAN and GERAN

Service based inter-RAT handover to UTRAN

Service based inter-RAT handover to GERAN

Distance based inter-RAT handover to UTRAN

Distance

candidate target UTRAN cells to UEs during redirections. If UtranFlashCsfbSwitch is off, flash CSFB to UTRAN is disabled. GeranFlashCsfbSwitch: This switch takes effect only when GeranCsfbSwitch is on. If GeranFlashCsfbSwitch is on, flash CSFB to GERAN is enabled and the eNodeB sends system information of candidate target GERAN cells to UEs during redirections. If GeranFlashCsfbSwitch is off, flash CSFB to GERAN is disabled. ServiceBasedInterFreqHoSwitch: If this switch is on, service-based inter-frequency handovers are enabled and UEs running a specific type of services can be handed over to inter-frequency cells. If this switch is off, service-based inter-frequency handovers are disabled. UlQualityInterFreqHoSwitch: If this switch is on, UL-quality-based inter-frequency handovers are enabled and UEs can be handed over to inter-frequency cells to ensure service continuity when the UL signal quality is poor. If this switch is off, UL-quality-based inter-frequency handovers are disabled. CsfbAdaptiveBlindHoSwitch: This switch takes effect only when BlindHoSwitch is on. If CsfbAdaptiveBlindHoSwitch is on, adaptive blind handovers for CSFB are enabled and appropriate handover mechanisms are selected for

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

081203

LOFD-070202 / TDLOFD-070202

TDLOFD-081223

based inter-RAT handover to GERAN

Mobility Management

Coverage Based Inter-frequency Handover

SRVCC to UTRAN

Service-Request Based Inter-frequency Handover


UEs based on their locations. If CsfbAdaptiveBlindHoSwitch is off, adaptive blind handovers for CSFB are disabled. UtranCsfbSteeringSwitch: If this switch is on, CSFB steering to UTRAN is enabled and CSFB policies for UEs in idle mode can be configured. If this switch is off, CSFB steering to UTRAN is disabled. GeranCsfbSteeringSwitch: If this switch is on, CSFB steering to GERAN is enabled and CSFB policies for UEs in idle mode can be configured. If this switch is off, CSFB steering to GERAN is disabled. CSFBLoadInfoSwitch: If this switch is on, load-based CSFB is enabled and a target cell for CSFB is selected based on loads of candidate target cells. If this switch is off, load-based CSFB is disabled. Cdma1XrttEcsfbSwitch: If this switch is on, eCSFB to CDMA2000 1xRTT is enabled and UEs can fall back to CDMA2000 1xRTT through handovers. If this switch is off, eCSFB to CDMA2000 1xRTT is disabled. EmcBlindHoA1Switch: If this switch is on, blind handover event A1 measurements are enabled. If a blind handover event measurement conflicts with a handover procedure, an emergency blind handover can be triggered after the handover procedure is complete. If this switch is off, blind handover event A1 measurements are disabled. If a blind handover event measurement conflicts

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description



with a handover procedure, an emergency blind handover cannot be triggered. EmcInterFreqBlindHoSwitch: If this switch is on, the eNodeB preferentially performs an inter-frequency blind handover when an emergency blind handover is triggered. If this switch is off, the eNodeB only performs an inter-RAT blind handover when an emergency blind handover is triggered. EPlmnSwitch: Indicates whether handovers to neighboring cells under the equivalent PLMNs (EPLMNs) are allowed. When inter-PLMN handovers are allowed, handovers to neighboring cells under the EPLMNs are allowed if this switch is on, and not allowed if this switch is off. The EPLMNs are delivered by the MME to the UE. ServiceBasedInterFreqHoSwitch: If this switch is on, service-based inter-frequency handovers are enabled and UEs running a specific type of services can be handed over to inter-frequency cells. If this switch is off, service-based inter-frequency handovers are disabled. This switch takes effect only for LTE TDD cells. VoipHoControlSwitch: Indicates whether the eNodeB filters out target cells that do not support VoIP services when processing intra-RAT handovers for VoIP services. The eNodeB filters out such target cells in the preceding scenario only when this switch is on.

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

UtranUltraFlashCsfbSwitch: In this switch is on, ultra-flash CSFB to UTRAN is enabled and UEs can fall back to UTRAN based on the ultra-flash CSFB procedure. If this switch is off, ultra-flash CSFB to UTRAN is disabled. GeranUltraFlashCsfbSwitch: In this switch is on, ultra-flash CSFB to GERAN is enabled and UEs can fall back to GERAN based on the ultra-flash CSFB procedure. If this switch is off, ultra-flash CSFB to GERAN is disabled.

GUI Value Range: IntraFreqCoverHoSwitch(IntraFreqCoverHoSwitch), InterFreqCoverHoSwitch(InterFreqCoverHoSwitch), UtranCsfbSwitch(UtranCsfbSwitch), GeranCsfbSwitch(GeranCsfbSwitch), Cdma1xRttCsfbSwitch(Cdma20001xRttCsfbSwitch), UtranServiceHoSwitch(UtranServiceHoSwitch), GeranServiceHoSwitch(GeranServiceHoSwitch), CdmaHrpdServiceHoSwitch(Cdma2000HrpdServiceHoSwitch), Cdma1xRttServiceHoSwitch(Cdma20001xRttServiceHoSwitch), UlQualityInterRATHoSwitch(UlQualityInterRATHoSwitch), InterPlmnHoSwitch(InterPlmnHoSwitch), UtranFlashCsfbSwitch(UtranFlashCsfbSwitch), GeranFlashCsfbSwitch(GeranFlashCsfbSwitch),

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

ServiceBasedInterFreqHoSwitch(ServiceBasedInterFreqHoSwitch), UlQualityInterFreqHoSwitch(UlQualityInterFreqHoSwitch), CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlindHoSwitch), UtranCsfbSteeringSwitch(UtranCsfbSteeringSwitch), GeranCsfbSteeringSwitch(GeranCsfbSteeringSwitch), CSFBLoadInfoSwitch(CSFBLoadInfoSwitch), Cdma1XrttEcsfbSwitch(Cdma1XrttEcsfbSwitch), EmcBlindHoA1Switch(EmcBlindHoA1Switch), EmcInterFreqBlindHoSwitch(EmcInterFreqBlindHoSwitch), EPlmnSwitch(EPlmnSwitch), ServiceReqInterFreqHoSwitch(ServiceReqInterFreqHoSwitch), VoipHoControlSwitch(VoipHoControlSwitch), UtranUltraFlashCsfbSwitch(UtranUltraFlashCsfbSwitch), GeranUltraFlashCsfbSwitch(GeranUltraFlashCsfbSwitch)

Unit: None

Actual Value Range: IntraFreqCoverHoSwitch, InterFreqCoverHoSwitch, UtranCsfbSwitch, GeranCsfbSwitch, Cdma1xRttCsfbSwitch, UtranServiceHoSwitch, GeranServiceHoSwitch, CdmaHrpdServiceHoSwitch, Cdma1xRttServiceHoSwitch, UlQualityInterRATHoSwitch, InterPlmnHoSwitch, UtranFlashCsfbSwitch,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

GeranFlashCsfbSwitch, ServiceBasedInterFreqHoSwitch, UlQualityInterFreqHoSwitch, CsfbAdaptiveBlindHoSwitch, UtranCsfbSteeringSwitch, GeranCsfbSteeringSwitch, CSFBLoadInfoSwitch, Cdma1XrttEcsfbSwitch, EmcBlindHoA1Switch, EmcInterFreqBlindHoSwitch, EPlmnSwitch, ServiceReqInterFreqHoSwitch, VoipHoControlSwitch, UtranUltraFlashCsfbSwitch, GeranUltraFlashCsfbSwitch

Default Value: IntraFreqCoverHoSwitch:On, InterFreqCoverHoSwitch:On, UtranCsfbSwitch:Off, GeranCsfbSwitch:Off, Cdma1xRttCsfbSwitch:Off, UtranServiceHoSwitch:Off, GeranServiceHoSwitch:Off, CdmaHrpdServiceHoSwitch:Off, Cdma1xRttServiceHoSwitch:Off, UlQualityInterRATHoSwitch:Off, InterPlmnHoSwitch:Off, UtranFlashCsfbSwitch:Off, GeranFlashCsfbSwitch:Off, ServiceBasedInterFreqHoSwitch:Off, UlQualityInterFreqHoSwitch:Off, CsfbAdaptiveBlindHoSwitch:Off, UtranCsfbSteeringSwitch:Off, GeranCsfbSteeringSwitch:Off, CSFBLoadInfoSwitch:Off, Cdma1XrttEcsfbSwitch:Off, EmcBlindHoA1Switch:Off, EmcInterFreqBlindHoSwitch:O

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

ff, EPlmnSwitch:Off, ServiceReqInterFreqHoSwitch:Off, VoipHoControlSwitch:Off, UtranUltraFlashCsfbSwitch:Off, GeranUltraFlashCsfbSwitch:Off

CSFallBackBlindHoCfg

UtranCsfbBlindRedirRrSw

MOD CSFALLBACKBLINDHOCFG

LST CSFALLBACKBLINDHOCFG

LOFD-001033/TDLOFD-001033




Meaning: Indicates whether the eNodeB selects the target frequency in a round robin (RR) manner from frequencies with the same priority in blind redirections for CSFB to UTRAN. If this parameter is set to ON(On), the function of target frequency selection in an RR manner is enabled. If this parameter is set to OFF(Off), this function is disabled.

GUI Value Range: OFF(OFF), ON(ON)

Unit: None

Actual Value Range: OFF, ON

Default Value: OFF(OFF)

CellDrxPara

DrxForMeasSwitch

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203

Ultra-Flash CS Fallback to GERAN

Meaning: Indicates whether to deliver DRX parameters dedicated for measurement to UEs performing CSFB-triggered GSM measurement. If this parameter is set to OFF, the eNodeB configures only a measurement gap for UEs to perform CSFB-triggered GSM measurement. If this parameter is set to ON, the eNodeB configures both DRX parameters and measurement gaps for UEs to perform CSFB-

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

triggered GSM measurement.

GUI Value Range: OFF(Off), ON(On)

Unit: None


Default Value: OFF(Off)

ENodeBAlgoSwitch

HoModeSwitch



LOFD-001022 / TDLOFD-001022

LOFD-001023 / TDLOFD-001023

LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

LOFD-001019 / TDLOFD-001019

SRVCC to UTRAN

SRVCC to GERAN




Meaning:

Indicates whether to enable or disable different types of handovers, based on which the eNodeB determines handover policies.

UtranVoipCapSwitch: If this switch is on, UTRAN supports VoIP. If this switch is off, UTRAN does not support VoIP.

Cdma1xRttVoipCapSwitch: If this switch is on, CDMA2000 1xRTT supports VoIP. If this switch is off, CDMA2000 1xRTT does not support VoIP.

UtranPsHoSwitch: If this switch is on, UTRAN supports PS handovers. If this switch is off, UTRAN does not support PS handovers.

GeranPsHoSwitch: If this switch is on, GERAN supports PS handovers. If this switch is off, GERAN does not support PS handovers.

CdmaHrpdNonOptimisedHoSwitch: If this switch is on, non-optimized handovers to

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LOFD-001020 / TDLOFD-001020

LOFD-001021 / TDLOFD-001021

TDLOFD-001052

TDLOFD-001088

TDLOFD-001043

TDLOFD-001072

TDLOFD-001046

TDLOFD-001073


PS Inter-RAT Mobility between E-UTRAN and CDMA2000



Service based

CDMA2000 HRPD are enabled. If this switch is off, non-optimized handovers to CDMA2000 HRPD are disabled.

CdmaHrpdOptimisedHoSwitch: If this switch is turned on, optimized handovers to CDMA2000 HRPD are enabled. If this switch is off, optimized handovers to CDMA2000 HRPD are disabled.

GeranNaccSwitch: This switch does not take effect if GeranCcoSwitch is off. If this switch is on, the GERAN supports network assisted cell change (NACC). If this switch is off, the GERAN does not support NACC.

GeranCcoSwitch: If this switch is on, the GERAN supports cell change order (CCO). If this switch is off, the GERAN does not support CCO.

UtranSrvccSwitch: If this switch is on, the UTRAN supports SRVCC. If this switch is off, the UTRAN does not support SRVCC.

GeranSrvccSwitch: If this switch is on, the GERAN supports SRVCC. If this switch is off, the GERAN does not support SRVCC.

Cdma1xRttSrvccSwitch: If this switch is on, the CDMA2000 1xRTT supports SRVCC. If

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

Inter-RAT handover to UTRAN

Distance based Inter-RAT handover to UTRAN

Service based Inter-RAT handover to GERAN

Distance based Inter-RAT handover to GERAN

this switch is off, the CDMA2000 1xRTT does not support SRVCC.

UtranRedirectSwitch: If this switch is on, redirection to UTRAN is enabled. If this switch is turned off, redirection to UTRAN is disabled.

GeranRedirectSwitch: If this switch is on, redirection to GERAN is enabled. If this switch is off, redirection to GERAN is disabled.

CdmaHrpdRedirectSwitch: If this switch is on, redirection to CDMA2000 HRPD is enabled. If this switch is off, redirection to CDMA2000 HRPD is disabled.

Cdma1xRttRedirectSwitch: If this switch is on, redirection to CDMA2000 1xRTT is enabled. If this switch is off, redirection to CDMA2000 1xRTT is disabled.

BlindHoSwitch: If this switch is on, blind handovers for CSFB are enabled. If this switch is off, blind handovers for CSFB are disabled. If both this option and the BlindHoSwitch option of the Handover Mode switch parameter of the CellHoParaCfg MO are selected, blind CSFB handovers for CSFB are enabled.

LcsSrvccSwitch: If this switch

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

is on, an SRVCC procedure is triggered when a UE receives a CSFB instruction during a VoIP service. If this switch is off, an SRVCC procedure is not triggered when a UE receives a CSFB instruction during a VoIP service.

AutoGapSwitch: If this switch is 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 off, the eNodeB delivers gap configurations to UEs during all inter-frequency and inter-RAT measurements.

UeVoipOnHspaCapSwitch: If this switch is on and the eNodeB attempts to hand over UEs using voice services to UTRAN, the eNodeB checks UE capabilities when determining whether PS handover is applied. UEs must support voiceOverPS-HS-UTRA-FDD-r9 if the target UTRAN cell works in FDD mode or voiceOverPS-HS-UTRA-TDD128-r9 if the target UTRAN cell works in TDD mode. If this switch is off, the eNodeB does not check UE capabilities when handing over UEs to UTRAN based on PS handovers.

UtranFddB1CapSwitch: If this switch is on, the setting of bit 41 of FGI specifying the UE capability of event B1

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

measurement on FDD UTRAN cells must be considered. If this switch is off, the setting of bit 41 of FGI does not need to be considered.

CdmaHrpdNonOptMeaHoSwitch: If this switch is on, measurement-based non-optimized handovers to CDMA2000 HRPD are enabled. If this switch is off, measurement-based non-optimized handovers to CDMA2000 HRPD are disabled.

GUI Value Range: EutranVoipCapSwitch(EutranVoipCapSwitch), UtranVoipCapSwitch(UtranVoipCapSwitch), GeranVoipCapSwitch(GeranVoipCapSwitch), Cdma1xRttVoipCapSwitch(Cdma1xRttVoipCapSwitch), UtranPsHoSwitch(UtranPsHoSwitch), GeranPsHoSwitch(GeranPsHoSwitch), CdmaHrpdNonOptimisedHoSwitch(CdmaHrpdNonOptimisedHoSwitch), CdmaHrpdOptimisedHoSwitch(CdmaHrpdOptimisedHoSwitch), GeranNaccSwitch(GeranNaccSwitch), GeranCcoSwitch(GeranCcoSwitch), UtranSrvccSwitch(UtranSrvccSwitch), GeranSrvccSwitch(GeranSrvccSwitch), Cdma1xRttSrvccSwitch(Cdma

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

1xRttSrvccSwitch), UtranRedirectSwitch(UtranRedirectSwitch), GeranRedirectSwitch(GeranRedirectSwitch), CdmaHrpdRedirectSwitch(CdmaHrpdRedirectSwitch), Cdma1xRttRedirectSwitch(Cdma1xRttRedirectSwitch), BlindHoSwitch(BlindHoSwitch), LcsSrvccSwitch(LcsSrvccSwitch), AutoGapSwitch(AutoGapSwitch), UeVoipOnHspaCapSwitch(UeVoipOnHspaCapSwitch), UtranFddB1CapSwitch(UtranFddB1CapSwitch), CdmaHrpdNonOptMeaHoSwitch(CdmaHrpdNonOptMeaHoSwitch)

Unit: None

Actual Value Range: EutranVoipCapSwitch, UtranVoipCapSwitch, GeranVoipCapSwitch, Cdma1xRttVoipCapSwitch, UtranPsHoSwitch, GeranPsHoSwitch, CdmaHrpdNonOptimisedHoSwitch, CdmaHrpdOptimisedHoSwitch, GeranNaccSwitch, GeranCcoSwitch, UtranSrvccSwitch, GeranSrvccSwitch, Cdma1xRttSrvccSwitch, UtranRedirectSwitch, GeranRedirectSwitch, CdmaHrpdRedirectSwitch, Cdma1xRttRedirectSwitch, BlindHoSwitch,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LcsSrvccSwitch, AutoGapSwitch, UeVoipOnHspaCapSwitch, UtranFddB1CapSwitch, CdmaHrpdNonOptMeaHoSwitch

Default Value: EutranVoipCapSwitch:On, UtranVoipCapSwitch:Off, GeranVoipCapSwitch:Off, Cdma1xRttVoipCapSwitch:Off, UtranPsHoSwitch:Off, GeranPsHoSwitch:Off, CdmaHrpdNonOptimisedHoSwitch: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, UeVoipOnHspaCapSwitch:Off, UtranFddB1CapSwitch:Off, CdmaHrpdNonOptMeaHoSwitch:Off

UtranNFreq

ConnFreqPriority

ADD UTRANNFREQ

MOD UTRANNFREQ

LST UTRANNFREQ

LOFD-001019 / TDLOFD-001019

TDLBFD-002018

PS Inter-RAT Mobility between E-UTRAN and UTR

Meaning: Indicates the frequency priority based on which the eNodeB selects a target frequency for blind redirection or contains a frequency in a measurement configuration. If a blind redirection is triggered and the target neighboring cell is not specified, the eNodeB selects a target frequency based on this

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

03

TDLOFD-001022

TDLOFD-001033

TDLOFD-001052

TDLOFD-001043

TDLOFD-001072

TDLOFD-001078

AN

Cell Selection and Re-selection

SRVCC to UTRAN



Service based Inter-RAT handover to UTRAN

Distance based Inter-RAT handover to UTR

priority. If a measurement configuration is to be delivered, the eNodeB preferentially delivers a frequency with the highest priority. If this priority is set to 0 for a frequency, this frequency is not selected as the target frequency for a blind redirection. A larger value indicates a higher priority.

GUI Value Range: 0~8

Unit: None

Actual Value Range: 0~8

Default Value: 0

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

AN

E-UTRAN to UTRAN CS/PS steering

ENodeBAlgoSwitch

NCellRankingSwitch








LOFD-001019/TDLOFD-

Inter-RAT ANR

SRVCC to UTRAN




PS Inter-RAT Mobility

Meaning: Indicates whether to enable neighboring cell ranking. This parameter consists of the following switches: GERAN_SWITCH: Indicates whether the eNodeB prioritizes measurement priorities of neighboring GERAN cells based on the number of each neighboring GERAN cell is measured within a period of time. The eNodeB prioritizes measurement priorities only when this switch is on. UTRAN_SWITCH: Indicates whether the eNodeB prioritizes measurement priorities of neighboring UTRAN cells based on the number of each neighboring UTRAN cell is measured within a period of time. The eNodeB prioritizes measurement priorities of neighboring UTRAN cells based on the number of each neighboring UTRAN cell is measured within a period of time only when this switch is on.

GUI Value Range: GERAN_SWITCH(GREAN Neighboring Cell Ranking

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

001019



between E-UTRAN and UTRAN



Switch), UTRAN_SWITCH(UTRAN Neighboring Cell Ranking Switch)

Unit: None

Actual Value Range: GERAN_SWITCH, UTRAN_SWITCH

Default Value: GERAN_SWITCH:Off, UTRAN_SWITCH:Off

UtranNCell

NCellMeasPriority

ADD UTRANNCELL

LST UTRANNCELL




Inter-RAT ANR

SRVCC to UTRAN


Flash CS

Meaning: Indicates the measurement priority of the neighboring UTRAN cell. A larger value indicates a higher priority. The measurement priorities can be periodically and automatically arranged based on the number of times that each neighboring UTRAN cell is measured. The neighboring UTRAN cells for UTRAN measurement control, UTRAN flash blind redirections, and UTRAN flash-CSFB-based redirections can be selected based on the measurement priorities of

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description





Fallback to UTRAN




neighboring UTRAN cells.


Unit: None


Default Value: 0

UtranNCell

CellMeasPriority

ADD UTRANNCELL

MOD UTRANNCELL

LOFD-001019

TDLOFD-001022

PS Inter-RAT Mobility between E-

Meaning: Indicates the priority of measurement on the neighboring UTRAN cell. The eNodeB preferentially contains the information about a neighboring cell with this priority set to

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LST UTRANNCELL

TDLOFD-001033

TDLOFD-001052

TDLOFD-001019

TDLOFD-001043

TDLOFD-001072

TDLOFD-001078

UTRAN and UTRAN

SRVCC to UTRAN




Service based Inter-RAT handover to UTR

HIGH_PRIORITY while delivering a measurement configuration.

GUI Value Range: LOW_PRIORITY(Low Priority), HIGH_PRIORITY(High Priority)

Unit: None

Actual Value Range: LOW_PRIORITY, HIGH_PRIORITY

Default Value: LOW_PRIORITY(Low Priority)

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

AN



CellUeMeasControlCfg

MaxUtranFddMeasFreqNum

MOD CELLUEMEASCONTROLCFG

LST CELLUEMEASCONTROLCFG

LOFD-001019 / TDLOFD-001019

LOFD-001022 / TDLOFD-001022

LOFD-001043 / TDLOFD-001043

LOFD-001072 /


SRVCC to UTRAN

Service based Inter-RAT hando

Meaning: Indicates the maximum number of UTRAN FDD frequencies that can be contained in the measurement control messages delivered for UEs in RRC_CONNECTED state.


Unit: None


Default Value: 3

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

TDLOFD-001072

LOFD-001033 / TDLOFD-001033

ver to UTRAN



CellUeMeasControlCfg

MaxUtranTddMeasFreqNum

MOD CELLUEMEASCONTROLCFG

LST CELLUEMEASCONTROLCFG

LOFD-001019 / TDLOFD-001019

LOFD-001022 / TDLOFD-001022

LOFD-001043 / TDLOFD-001043

LOFD-001072 / TDLOF


SRVCC to UTRAN

Service based Inter-RAT handover to

Meaning: Indicates the maximum number of UTRAN TDD frequencies that can be contained in the measurement control messages delivered for UEs in RRC_CONNECTED state.


Unit: None


Default Value: 3

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

D-001072

LOFD-001033 / TDLOFD-001033

UTRAN



CSFallBackHo

CsfbHoUtranB1ThdRscp

MOD CSFALLBACKHO

LST CSFALLBACKHO

LOFD-001033 / TDLOFD-001033


Meaning: Indicates the RSCP threshold for event B1, which is used in CS fallback to UTRAN. When CS fallback to UTRAN is applicable, this parameter is set for UEs and used in the evaluation about whether to trigger event B1. This parameter indicates the RSCP requirement for the UTRAN cells to be included in the measurement report. A UE sends a measurement report related to event B1 to the eNodeB when the RSCP in at least one UTRAN cell exceeds this threshold and other triggering conditions are met. For details, see 3GPP TS 36.331.

GUI Value Range: -120~-25

Unit: dBm

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

Actual Value Range: -120~-25

Default Value: -106

InterRatHoComm

InterRatHoUtranB1MeasQuan

MOD INTERRATHOCOMM

LST INTERRATHOCOMM

LOFD-001019 / TDLOFD-001019

LOFD-001022 / TDLOFD-001022

LOFD-001033 / TDLOFD-001033


SRVCC to UTRAN


Meaning:

Indicates the quantity to be measured for handovers to UTRAN. For details, see 3GPP TS 36.331. This parameter is dedicated to UTRAN FDD. The RSCP values are relatively stable, while the ECN0 values may vary with the network load. The value BOTH applies only to UEs complying with 3GPP Release 10. For UEs complying with 3GPP Release 8 or 9, the value BOTH takes the same effect as the value RSCP. In QoE-based handovers, this parameter does not apply to UEs complying with 3GPP Release 8 or 9 and the measurement quantity is fixed to ECN0 for such UEs.

If this parameter is set to RSCP, the eNodeB delivers RSCP-based UTRAN measurement configurations to UEs. If this parameter is set to ECN0, the eNodeB delivers ECN0-based UTRAN measurement configurations to UEs. If this parameter is set to BOTH, the eNodeB delivers both RSCP- and ECN0-based UTRAN measurement configurations to UEs complying with 3GPP Release 10.

GUI Value Range: RSCP,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

ECN0, BOTH

Unit: None

Actual Value Range: RSCP, ECN0, BOTH

Default Value: ECN0

CSFallBackHo

CsfbHoUtranB1ThdEcn0

MOD CSFALLBACKHO

LST CSFALLBACKHO

LOFD-001033 / TDLOFD-001033


Meaning: Indicates the Ec/N0 threshold for event B1, which is used in CS fallback to UTRAN. When CS fallback to UTRAN is required, this parameter is set for UEs and used in the evaluation about whether to trigger event B1. This parameter indicates the Ec/N0 requirement for the UTRAN cells to be included in the measurement report. A UE sends a measurement report related to event B1 to the eNodeB when the Ec/N0 in at least one UTRAN cell exceeds this threshold and other triggering conditions are met. For a cell with large signal fading variance, set this parameter to a large value to prevent unnecessary handovers. For a cell with small signal fading variance, set this parameter to a small value to ensure timely handovers. For details, see 3GPP TS 36.331.

GUI Value Range: -48~0

Unit: 0.5dB

Actual Value Range: -24~0

Default Value: -24

CSFallBa CsfbHoUtran MOD LOFD- CS Meaning: Indicates the time-to-

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

ckHo TimeToTrig CSFALLBACKHO

LST CSFALLBACKHO

001033 / TDLOFD-001033

Fallback to UTRAN

trigger for event B1 that is used in CS fallback to UTRAN. When CS fallback to UTRAN is applicable, this parameter is set for UEs and used in the evaluation of whether to trigger event B1. When detecting that the signal quality in at least one UTRAN cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers, and thus helps to prevent unnecessary handovers. For details, see 3GPP TS 36.331.

GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms

Unit: ms

Actual Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms

Default Value: 40ms

CSFallBackHo

BlindHoA1ThdRsrp

MOD CSFALLBAC

LOFD-001052 /

Flash CS Fallba

Meaning: Indicates the reference signal received power (RSRP) threshold for event A1

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

KHO

LST CSFALLBACKHO

TDLOFD-001052

LOFD-001053 / TDLOFD-001053

ck to UTRAN


associated with CSFB-triggered adaptive blind handovers. This parameter is set for a UE as a triggering condition of event A1 measurement related to a CSFB-triggered adaptive blind handover. This parameter specifies the RSRP threshold of the serving cell above which a CSFB-triggered adaptive blind handover is triggered. If the RSRP value measured by a UE exceeds this threshold, the UE submits a measurement report related to event A1.


Unit: dBm


Default Value: -80


InterRatHighestPri



LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

LOFD-001035 / TDLOFD-001035

LOFD-




PS

Meaning:

Indicates the highest-priority RAT for handovers. It is UTRAN by default. If this parameter is set to UTRAN, GERAN, or CDMA2000, the highest-priority RAT is UTRAN, GERAN, or CDMA2000, respectively.

The value CDMA2000 is invalid in the current version. Therefore, avoid setting this parameter to CDMA2000.

GUI Value Range: UTRAN, GERAN, CDMA2000

Unit: None

Actual Value Range: UTRAN,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020

LOFD-001021

TDLOFD-001052

TDLOFD-001053

TDLOFD-001090

TDLOFD-001043

TDLOFD-001072

TDLOFD-001046

TDLOFD-001073

Inter-RAT Mobility between E-UTRAN and UTRAN



Flash CS Fallback to UTR

GERAN, CDMA2000

Default Value: UTRAN

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

AN





Service based Inter-RAT

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

handover to GERAN



InterRatSecondPri



LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

LOFD-001035 / TDLOFD-001035

LOFD-001019 / TDLOFD-001019

LOFD-001020




PS Inter-RAT Mobility between E-UTRAN

Meaning:

Indicates the medium-priority RAT for handovers. It is GERAN by default. If this parameter is set to UTRAN, GERAN, or CDMA2000, the medium-priority RAT is UTRAN, GERAN, or CDMA2000, respectively. If this parameter is set to NULL, no medium-priority RAT is specified and only the highest-priority RAT can be selected for handovers.


GUI Value Range: UTRAN, GERAN, CDMA2000, NULL

Unit: None

Actual Value Range: UTRAN, GERAN, CDMA2000, NULL

Default Value: GERAN

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

/ TDLOFD-001020

LOFD-001021

TDLOFD-001052

TDLOFD-001053

TDLOFD-001090

TDLOFD-001043

TDLOFD-001072

TDLOFD-001046

TDLOFD-001073

and UTRAN





MO Parameter ID

MML Command

Feature ID

Feature

Name

Description





Distance based Inter-

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

RAT handover to GERAN


InterRatLowestPri



LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

LOFD-001035 / TDLOFD-001035

LOFD-001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020

LOFD-001021

TDLOF






Meaning:

Indicates the lowest-priority RAT for handovers. It is CDMA2000 by default. If this parameter is set to UTRAN, GERAN, or CDMA2000, the lowest-priority RAT is UTRAN, GERAN, or CDMA2000, respectively. If this parameter is set to NULL, no lowest-priority RAT is specified and only the highest- or medium-priority RAT can be selected for handovers.



Unit: None


Default Value: CDMA2000

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

D-001052

TDLOFD-001053

TDLOFD-001090

TDLOFD-001043

TDLOFD-001072

TDLOFD-001046

TDLOFD-001073

between E-UTRAN and GERAN




Enhanced CS Fallback to CDMA2000 1xRT

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

T





UtranNCell

BlindHoPriority

ADD UTRANNCE

LOFD-001019

PS Inter-RAT

Meaning: Indicates the priority of the neighboring cell during blind handovers. Blind

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LL

MOD UTRANNCELL

LST UTRANNCELL

TDLOFD-001022

TDLOFD-001033

TDLOFD-001052

TDLOFD-001019

TDLOFD-001043

TDLOFD-001072

TDLOFD-001078

Mobility between E-UTRAN and UTRAN

SRVCC to UTRAN




Service based Inter-RAT

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.


Unit: None


Default Value: 0

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

handover to UTRAN



ENodeBAlgoSwitch

FreqLayerSwtich



LOFD-001087

LOFD-001078 / TDLOFD-001078

TDLOFD-001022

TDLOFD-001033

TDLOFD-001052

SRVCC Flexible Steering to UTRAN

E-UTRAN to UTRAN CS/PS Steering

SRVCC to UTR

Meaning: This parameter includes the following three switches: UtranFreqLayerMeasSwitch, UtranFreqLayerBlindSwitch, and UtranSrvccSwitch. The setting of UtranSrvccSwitch takes effect only when UtranFreqLayerMeasSwitch is on. If UtranFreqLayerMeasSwitch is on, the UTRAN hierarchy-based measurement algorithm takes effect for measurements related to coverage-based and CSFB-triggered handovers from E-UTRAN to UTRAN. If UtranFreqLayerBlindSwitch is on, the UTRAN hierarchy-based blind-handover algorithm takes effect for coverage-based

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

TDLOFD-001088

AN




and CSFB-triggered blind handovers from E-UTRAN to UTRAN. If UtranSrvccSwitch is on, the UTRAN SRVCC hierarchy-based measurement algorithm takes effect for coverage-based SRVCC-triggered handovers from E-UTRAN 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

LOFD-001078 / TDLOFD-001078

TDLOFD-001033

TDLOFD-001052


CS Fallback to UTR

Meaning: Indicates the circuit switched (CS) priority of the neighboring UTRAN frequency, that is, the priority for the neighboring UTRAN frequency to carry CS services. During CSFB-based CS service handovers with UtranFreqLayerMeasSwitch being on, the eNodeB selects and delivers the neighboring UTRAN frequencies based on the CS priorities when starting measurements. The eNodeB

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

TDLOFD-001088

AN



preferentially delivers the UTRAN frequency with the highest CS priority to measure. During CSFB-based CS service handovers with UtranFreqLayerBlindSwitch being on, the eNodeB selects the target cells for blind handovers on neighboring UTRAN frequencies based on the CS priorities and preferentially selects the target cell for blind handovers on the neighboring UTRAN frequency with the highest CS priorities. If this parameter is set to Priority_0, this neighboring UTRAN frequency is not prioritized.

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,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

Priority_8, Priority_9, Priority_10, Priority_11, Priority_12, Priority_13, Priority_14, Priority_15, Priority_16

Default Value: Priority_2(Priority 2)


IdleCsfbHighestPri



LOFD-001035 / TDLOFD-001035

LOFD-001088 / TDLOFD-001088

LOFD-001089 / TDLOFD-001089

TDLOFD-001090





Meaning:

Indicates the highest-priority RAT for CSFB initiated by a UE in idle mode. It is UTRAN by default. If this parameter is set to UTRAN, GERAN, or CDMA2000, the highest-priority RAT is UTRAN, GERAN, or CDMA2000, respectively.


GUI Value Range: UTRAN, GERAN, CDMA2000

Unit: None

Actual Value Range: UTRAN, GERAN, CDMA2000

Default Value: UTRAN

CSFallBa IdleCsfbSeco MOD LOFD- CS Meaning:

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

ckBlindHoCfg

ndPri CSFALLBACKBLINDHOCFG


001035 / TDLOFD-001035

LOFD-001088 / TDLOFD-001088

LOFD-001089 / TDLOFD-001089

TDLOFD-001090

Fallback to CDMA2000 1xRTT




Indicates the medium-priority RAT for CSFB initiated by a UE in idle mode. It is GERAN by default. If this parameter is set to UTRAN, GERAN, or CDMA2000, the medium-priority RAT is UTRAN, GERAN, or CDMA2000, respectively. If this parameter is set to NULL, no medium-priority RAT is specified and only the highest-priority RAT can be selected for CSFB initiated by a UE in idle mode.



Unit: None


Default Value: GERAN


IdleCsfbLowestPri



LOFD-001035 / TDLOFD-001035

LOFD-001088 / TDLOF


CS Fallba

Meaning:

Indicates the lowest-priority RAT for CSFB initiated by a UE in idle mode. It is CDMA2000 by default. If this parameter is set to UTRAN, GERAN, or CDMA2000, the lowest-priority RAT is UTRAN, GERAN, or CDMA2000, respectively. If

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

D-001088

LOFD-001089 / TDLOFD-001089

TDLOFD-001090

ck Steering to UTRAN



this parameter is set to NULL, no lowest-priority RAT is specified and only the highest- or medium-priority RAT can be selected for CSFB initiated by a UE in idle mode.



Unit: None


Default Value: CDMA2000

CSFallBackPolicyCfg

IdleModeCsfbHoPolicyCfg

MOD CSFALLBACKPOLICYCFG

LST CSFALLBACKPOLICYCFG

LOFD-001088 / TDLOFD-001088

LOFD-001089 / TDLOFD-001089



Meaning: Indicates the CSFB policy for a UE in idle mode. The policy can be PS handover, CCO, or redirection.

GUI Value Range: REDIRECTION, CCO_HO, PS_HO

Unit: None

Actual Value Range: REDIRECTION, CCO_HO, PS_HO

Default Value: REDIRECTION:On, CCO_HO:On, PS_HO:On

UtranNFreq

CsPsMixedPriority

ADD UTRANNFR

LOFD-001088

CS Fallba

Meaning: Indicates the priority for the neighboring UTRAN

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

EQ

MOD UTRANNFREQ

LST UTRANNFREQ

/ TDLOFD-001088

LOFD-001019 / TDLOFD-001019

TDLOFD-001033

TDLOFD-001052

TDLOFD-001078

ck Steering to UTRAN





frequency to carry CS+PS combined services. In measurement-based CSFB to UTRAN, if UtranCsfbSteeringSwitch and UtranFreqLayerMeasSwitch are turned on, the eNodeB determines the UTRAN frequency to be delivered to a UE in RRC_CONNECTED mode based on the priority specified by this parameter. The eNodeB preferentially delivers the UTRAN frequency with the highest CS+PS combined service priority to the UE. In blind CSFB to UTRAN, if UtranCsfbSteeringSwitch and UtranFreqLayerBlindSwitch are turned on, the target cell is selected based on the priority specified by this parameter. The cell on the UTRAN frequency with the highest priority is preferentially selected. If this parameter is set to Priority_0, the UTRAN frequency is not included in priority arrangement for neighboring UTRAN frequencies to carry CS+PS combined services.

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),

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

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)

CSFallBackPolicyCfg

CsfbHoPolicyCfg



LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

LOFD-001088 / TDLOFD-001088

LOFD-




CS Fallba

Meaning: Indicates the CSFB policy for a UE in connected mode. If the CSFB steering function is disabled, this parameter also applies to UEs in idle mode. The policy can be PS handover, CCO, or redirection.

GUI Value Range: REDIRECTION, CCO_HO, PS_HO

Unit: None

Actual Value Range: REDIRECTION, CCO_HO, PS_HO

Default Value: REDIRECTION:On, CCO_HO:On, PS_HO:On

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

001089 / TDLOFD-001089

ck Steering to GERAN

InterRatHoComm

CellInfoMaxUtranCellNum

MOD INTERRATHOCOMM

LST INTERRATHOCOMM

LOFD-001019 / TDLOFD-001019

TDLOFD-001052



Meaning: Indicates the maximum number of UTRAN cell system information messages that can be transmitted during a flash redirection procedure.


Unit: None


Default Value: 8

CSFallBackHo

CsfbProtectionTimer

MOD CSFALLBACKHO

LST CSFALLBACKHO

LOFD-001033 / TDLOFD-001033

LOFD-001033 / TDLOFD-001034

LOFD-001033 / TDLOFD-001090



Enhanced CS Fallback to CDMA2000

Meaning: Indicates the timer governing the period in which only CSFB can be performed . After the timer expires, the eNodeB performs a blind redirection for the UE.


Unit: s


Default Value: 4

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

1xRTT

InterRatHoComm

UtranCellNumForEmcRedirect

MOD INTERRATHOCOMM

LST INTERRATHOCOMM

LOFD-001033 / TDLOFD-001033

TDLOFD-001052



Meaning: Indicates the maximum number of UTRAN cell system information messages that can be transmitted during a CSFB emergency redirection procedure.


Unit: None


Default Value: 0

ENodeBAlgoSwitch

MultiOpCtrlSwitch



LOFD-001022

LOFD-001087

LOFD-001033

LOFD-001052

LOFD-001068

LOFD-001088

LOFD-001019

LOFD-001043

LOFD-001072

SRVCC to UTRAN

SRVCC Flexible Steering to UTRAN



Meaning: Indicates the switch used to control whether operators can adopt different policies. This parameter is a bit-filed-type parameter. By specifying the bit fields under this parameter, operators can adopt different policies on the corresponding RAT. UtranSepOpMobilitySwitch is a switch used to control whether operators can adopt different mobility policies on their UTRANs. If this switch is on, operators can adopt different policies (for example, PS handover capability and RIM-based system information reading capability) on their UTRANs. If this switch is off, operators cannot adopt different policies on their UTRANs.

GUI Value Range: UtranSepOpMobilitySwitch(UtranSepOpMobilitySwitch)

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LOFD-001078




Service based inter-RAT


Unit: None

Actual Value Range: UtranSepOpMobilitySwitch

Default Value: UtranSepOpMobilitySwitch:Off

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description


UtranNetworkCapCfg

NetworkCapCfg

ADD UTRANNETWORKCAPCFG

MOD UTRANNETWORKCAPCFG

LST UTRANNETWORKCAPCFG

LOFD-001022 / TDLOFD-001022

LOFD-001033 / TDLOFD-001033

LOFD-001052 / TDLOFD-001052

LOFD-001068 / TDLOFD-001068

LOFD-001088 / TDLOFD-001088

LOFD-

SRVCC to UTRAN





PS Inter-

Meaning:

Indicates the UTRAN capabilities for an operator including PS handover capability, capability of obtaining system information (SI) of the UTRAN through RAN Information Management (RIM) procedures, VoIP capability, and ultra-flash CSFB capability. If the MME, SGSN, or RNC of the operator does not support PS handovers, RIM procedures, VoIP, or ultra-flash CSFB, set this parameter to indicate the incapabilities. If this parameter is not set, UTRAN capabilities are supported by default.

PsHoCapCfg: This option indicates whether PS handovers are supported. If this option is selected, the UTRAN supports PS handovers. If this option is deselected, the UTRAN does not support PS handovers.

SiByRimCapCfg: This option indicates whether the capability of obtaining SI of the UTRAN through RIM procedures is supported. If the option is selected, obtaining SI of the UTRAN through RIM

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

001019 / TDLOFD-001019

LOFD-001043 / TDLOFD-001043

LOFD-001072 / TDLOFD-001072

LOFD-081283 / TDLOFD-081203

LOFD-070202 / TDLOFD-081223

RAT Mobility between E-UTRAN and UTRAN





procedures is supported. If the option is deselected, obtaining SI of the UTRAN through RIM procedures is not supported.

VoipCapCfg: This option indicates the VoIP capability of the UTRAN. If this option is selected, the VoIP is supported. VoIP services established in the LTE network can be transferred to the UTRAN using PS handovers so that UEs can perform voice services in the UTRAN. If this option is deselected, the UTRAN does not support VoIP. Voice services established in the LTE network cannot be transferred to the UTRAN using PS handovers.

UltraFlashCsfbCapCfg: This option indicates the SRVCC capability. If this option is selected, SRVCC is supported and voice services can continue in the UTRAN by SRVCC. If this option is deselected, SRVCC is not supported.

GUI Value Range: PsHoCapCfg(PsHoCapCfg), SiByRimCapCfg(SiByRimCapCfg), VoipCapCfg(VoipCapCfg), UltraFlashCsfbCapCfg(UltraFlashCsfbCapCfg)

Unit: None

Actual Value Range: PsHoCapCfg, SiByRimCapCfg, VoipCapCfg,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

UltraFlashCsfbCapCfg

Default Value: PsHoCapCfg:Off, SiByRimCapCfg:Off, VoipCapCfg:On, UltraFlashCsfbCapCfg:Off

CSFallBackPolicyCfg

CsfbUserArpCfgSwitch



LBFD-002023 /TDLBFD-002023

Admission Control

Meaning: Indicates whether allocation/retention priorities (ARPs) can be configured for CSFB services triggered by common calls. For details about ARPs, see 3GPP TS 23.401.


Unit: None



CSFallBackPolicyCfg

NormalCsfbUserArp



LBFD-002023 /TDLBFD-002023

Admission Control

Meaning: Indicates the allocation/retention priority (ARP) of a CSFB service triggered by a common call. When this parameter is set to 1, the service priority is the same as that of an emergency call. For details about the ARP, see 3GPP TS 23.401.


Unit: None


Default Value: 2

GlobalProcSwitch

UtranLoadTransChan

MOD GLOBALPROCSWITCH

None None Meaning: Indicates the UMTS load transmission channel. The eNodeB sends RAN-INFORMATION-REQUEST

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

LST GLOBALPROCSWITCH

PDUs to UTRAN cells to request multiple reports on the load status of UTRAN cells only when the parameter is set to BASED_ON_RIM.The function specified by the parameter value BASED_ON_ECO is temporarily unavailable.

GUI Value Range: NULL, BASED_ON_RIM, BASED_ON_ECO

Unit: None

Actual Value Range: NULL, BASED_ON_RIM, BASED_ON_ECO

Default Value: NULL

ENodeBAlgoSwitch

RimOnEcoSwitch



MRFD-090211




LOFD-001033/TDLOF

eCoordinator based RIM process optimization



Meaning: Indicates whether the RAN information management (RIM) procedure is initiated by the eCoordinator. If this parameter is set to ON, the RIM procedure is initiated by the eCoordinator. If this parameter is set to OFF, the RIM procedure is initiated by the core network.


Unit: None



MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

D-001033

UTRAN and UTRAN

Inter-RAT Load Sharing to UTRAN(based on UMTS cell load information)

CS Fallback to UTRAN (based on UMTS cell load information)

ENodeBAlgoSwitch

RimSwitch MOD ENODEBALGOSWITCH


LOFD-001034 / TDLOFD-001034

LOFD-001052


Flash CS Fallba

Meaning: Indicates the collective switch for the RAN information management (RIM) function. UTRAN_RIM_SWITCH: Indicates the switch used to enable or disable the RIM procedure that requests event-driven multiple reports from

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

/ TDLOFD-001052

LOFD-001053 / TDLOFD-001053

ck to UTRAN


UTRAN cells. If this switch is on, the eNodeB can send RAN-INFORMATION-REQUEST protocol data units (PDUs) to UTRAN cells to request multiple event-driven reports. If this switch is off, the eNodeB cannot send RAN-INFORMATION-REQUEST PDUs to UTRAN cells to request multiple event-driven reports. GERAN_RIM_SWITCH: Indicates the switch used to enable or disable the RIM procedure that requests event-driven multiple reports from GERAN cells. If this switch is on, the eNodeB can send RAN-INFORMATION-REQUEST PDUs to CERAN cells to request multiple event-driven reports. If this switch is off, the eNodeB cannot send RAN-INFORMATION-REQUEST PDUs to GERAN cells to request multiple event-driven reports.

GUI Value Range: UTRAN_RIM_SWITCH(UTRAN RIM Switch), GERAN_RIM_SWITCH(GERAN RIM Switch)

Unit: None

Actual Value Range: UTRAN_RIM_SWITCH, GERAN_RIM_SWITCH

Default Value: UTRAN_RIM_SWITCH:Off, GERAN_RIM_SWITCH:Off

GeranNfre ConnFreqPri ADD LOFD- PS Meaning: Indicates the

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

qGroup ority GERANNFREQGROUP

MOD GERANNFREQGROUP

LST GERANNFREQGROUP

001020 / TDLOFD-001020

TDLOFD-001023

TDLOFD-001034

TDLOFD-001053

Inter-RAT Mobility between E-UTRAN and GERAN

SRVCC to GERAN



frequency group priority based on which the eNodeB selects a target frequency group for blind redirection or delivers a frequency group in measurement configuration messages. If a blind redirection is triggered and the target neighboring cell is not specified, the eNodeB selects a target frequency group based on the setting of this parameter. If a measurement configuration is to be delivered, the eNodeB preferentially delivers the frequency group with the highest priority. If this parameter is set to 0 for a frequency group, this frequency group is not selected as the target frequency group for a blind redirection. A larger value indicates a higher priority.


Unit: None


Default Value: 0

GeranNcell

BlindHoPriority

ADD GERANNCELL

MOD GERANNCELL

LST GERANNCELL

LOFD-001020 / TDLOFD-001020

TDLOFD-001023

TDLOFD-


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

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

001034

TDLOFD-001053

SRVCC to GERAN



cell are not allowed.


Unit: None


Default Value: 0

InterRatHoComm

CellInfoMaxGeranCellNum

MOD INTERRATHOCOMM

LST INTERRATHOCOMM

LOFD-001020 / TDLOFD-001020

TDLOFD-001053



Meaning: Indicates the maximum number of GERAN cell system information messages that can be transmitted during a flash redirection procedure.


Unit: None


Default Value: 8

UtranExternalCell

Rac ADD UTRANEXTERNALCELL

MOD UTRANEXTERNALCEL

LOFD-001019 / TDLOFD-001019

LOFD-

PS Inter-RAT Mobility between E-UTR

Meaning: Indicates the routing area code.


Unit: None

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

L

LST UTRANEXTERNALCELL

001034 / TDLOFD-001034

LOFD-001052 / TDLOFD-001052

TDLOFD-001033

TDLOFD-001043

TDLOFD-001072

TDLOFD-001078

AN and UTRAN






E-UTR


Default Value: 0

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

AN to UTRAN CS/PS steering


CnOperatorId LST CSFALLBACKBLINDHOCFG


LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001034

TDLOFD-001052

TDLOFD-001053

TDLOFD-001035

TDLOFD-001090






Enhanced CS

Meaning: Indicates the index of the operator.


Unit: None


Default Value: None

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

Fallback to CDMA2000 1xRTT


UtranLcsCap MOD CSFALLBACKBLINDHOCFG


LOFD-001033 / TDLOFD-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.


Unit: None



CSFallBackHo

LocalCellId LST CSFALLBACKHO

MOD CSFALLBACKHO

None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.


Unit: None


Default Value: None

S1Interface

MmeRelease ADD S1INTERFACE

MOD S1INTERFACE

DSP S1INTERFA

LBFD-00300101 / TDLBFD-00300101

LBFD-003001

Star Topology

Chain Topology

Tree Topol

Meaning: Indicates the compliance protocol release of the MME to which the eNodeB is connected through the S1 interface. The eNodeB sends S1 messages complying with the protocol release specified by this parameter. The value of this parameter must be the same as the MME-complied

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

CE 02 / TDLBFD-00300102

LBFD-00300103 / TDLBFD-00300103

LBFD-001008 / TDLBFD-070111

ogy

3GPP R11 Specifications

protocol release. If the parameter value is different from the MME-complied protocol release, the way in which the MME handles these message is subject to the MME implementation.

GUI Value Range: Release_R8(Release 8), Release_R9(Release 9), Release_R10(Release 10), Release_R11(Release 11)

Unit: None

Actual Value Range: Release_R8, Release_R9, Release_R10, Release_R11

Default Value: Release_R8(Release 8)

GeranExternalCell

Rac ADD GERANEXTERNALCELL

MOD GERANEXTERNALCELL

LST GERANEXTERNALCELL

LOFD-001034 / LOFD-001034

LOFD-001053

LOFD-001020 / TDLOFD-001020



PS Inter-RAT Mobility between E-UTRAN and

Meaning: Indicates the routing area code.


Unit: None


Default Value: 0

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

GERAN


GeranLcsCap MOD CSFALLBACKBLINDHOCFG


LOFD-001034 / TDLOFD-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.


Unit: None



InterRatHoComm

GeranCellNumForEmcRedirect

MOD INTERRATHOCOMM

LST INTERRATHOCOMM

LOFD-001034 / TDLOFD-001034


Meaning: Indicates the maximum number of GERAN cell system information messages that can be transmitted during a CSFB emergency redirection procedure.


Unit: None


Default Value: 0

CSFallBackHo

CsfbHoGeranB1Thd

MOD CSFALLBACKHO

LST CSFALLBACKHO

LOFD-001034 / TDLOFD-001034

CS Fall Back to GERAN

Meaning: Indicates the RSSI threshold for event B1 that is used in CS fallback to GERAN. A UE sends a measurement report related to event B1 to the eNodeB when the RSSI in at least one GERAN cell exceeds this threshold and other triggering conditions are met. For details, see 3GPP TS

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

36.331.


Unit: dBm


Default Value: -103

CSFallBackHo

CsfbHoGeranTimeToTrig

MOD CSFALLBACKHO

LST CSFALLBACKHO

LOFD-001034 / TDLOFD-001034

CS Fall Back to GERAN

Meaning: Indicates the time-to-trigger for event B1 that is used in CS fallback to GERAN. When CS fallback to GERAN is applicable, this parameter is set for UEs and used in the evaluation of whether to trigger event B1. When detecting that the signal quality in at least one GERAN cell meets the entering condition, the UE does not send a measurement report to the eNodeB immediately. Instead, the UE sends a report only when the signal quality continuously meets the entering condition during the time-to-trigger. This parameter helps decrease the number of occasionally triggered event reports, the average number of handovers, and the number of wrong handovers, and thus helps to prevent unnecessary handovers. For details, see 3GPP TS 36.331.

GUI Value Range: 0ms, 40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms

Unit: ms

Actual Value Range: 0ms,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

40ms, 64ms, 80ms, 100ms, 128ms, 160ms, 256ms, 320ms, 480ms, 512ms, 640ms, 1024ms, 1280ms, 2560ms, 5120ms

Default Value: 40ms

CellDrxPara

LongDrxCycleForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates the length of the long DRX cycle dedicated to GERAN measurement.

GUI Value Range: SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes)

Unit: subframe

Actual Value Range: SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560

Default Value: SF160(160 subframes)

CellDrxPara

OnDurTimerForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates the length of the On Duration Timer dedicated to GERAN measurement.

GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH subframes), PSF200(200 PDCCH subframes)

Unit: subframe

Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200

Default Value: PSF2(2 PDCCH subframes)

CellDrxPara

DrxInactTimerForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates the length of the DRX Inactivity Timer dedicated to GERAN measurement.

GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

subframes), PSF200(200 PDCCH subframes), PSF300(300 PDCCH subframes), PSF500(500 PDCCH subframes), PSF750(750 PDCCH subframes), PSF1280(1280 PDCCH subframes), PSF1920(1920 PDCCH subframes), PSF2560(2560 PDCCH subframes)

Unit: subframe

Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200, PSF300, PSF500, PSF750, PSF1280, PSF1920, PSF2560


CellDrxPara

DrxReTxTimerForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates the length of the DRX Retransmission Timer dedicated to GERAN measurement.

GUI Value Range: PSF1(1 PDCCH subframes), PSF2(2 PDCCH subframes), PSF4(4 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF16(16 PDCCH subframes), PSF24(24 PDCCH subframes), PSF33(33 PDCCH subframes)

Unit: subframe

Actual Value Range: PSF1, PSF2, PSF4, PSF6, PSF8,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

PSF16, PSF24, PSF33


CellDrxPara

ShortDrxSwForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates whether to enable the short DRX cycle dedicated to GERAN measurement.


Unit: None



CellDrxPara

ShortDrxCycleForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates the length of the short DRX cycle dedicated to GERAN measurement.

GUI Value Range: SF2(2 subframes), SF5(5 subframes), SF8(8 subframes), SF10(10 subframes), SF16(16 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes)

Unit: subframe

Actual Value Range: SF2, SF5, SF8, SF10, SF16, SF20, SF32, SF40, SF64, SF80, SF128,

MO Parameter ID

MML Command

Feature ID

Feature

Name

Description

SF160, SF256, SF320, SF512, SF640

Default Value: SF20(20 subframes)

CellDrxPara

ShortCycleTimerForMeas

MOD CELLDRXPARA

LST CELLDRXPARA

LOFD-081283 / TDLOFD-081203


Meaning: Indicates the length of the DRX Short Cycle Timer dedicated to GERAN measurement.


Unit: None


Default Value: 1

9 CountersTable 9-1 CountersCounter

IDCounter Name Counter

Description

Feature ID

Feature Name

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-


SRVCC to GERAN


Counter ID

Counter Name Counter Descripti

on

Feature ID

Feature Name

001034

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034


SRVCC 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


SRVCC to GERAN



Counter ID


on

Feature ID

Feature Name

TDLOFD-001034

SRVCC to GERAN


1526726994

L.IRATHO.E2G.ExecSuccOut Number of successful inter-RAT 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


SRVCC to GERAN



SRVCC to GERAN


15267283 L.IRATHO.E2G.Prep.FailOut.MME Number Multi- CS

Counter ID


on

Feature ID

Feature Name

06 of inter-RAT handover preparation failures from E-UTRAN to GERAN because of faults on the MME side

mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001020

TDLOFD-001020

LOFD-001046

TDLOFD-001046

LOFD-001073

LOFD-001023

TDLOFD-001023

Fallback to GERAN






Distance based Inter-

Counter ID


on

Feature ID

Feature Name

RAT handover to GERAN

SRVCC to GERAN

SRVCC to GERAN

1526728307

L.IRATHO.E2G.Prep.FailOut.NoReply Number of inter-RAT handover preparation failures from E-UTRAN to GERAN because of no responses from GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001020

TDLOFD-001020

LOFD-001046

TDLOFD-001046





Service based inter-RAT

Counter ID


on

Feature ID

Feature Name

LOFD-001073

LOFD-001023

TDLOFD-001023

handover to GERAN



SRVCC to GERAN

SRVCC to GERAN

1526728308

L.IRATHO.E2G.Prep.FailOut.PrepFailure Number of inter-RAT handover preparation failures from E-UTRAN to GERAN due tobecause GERAN cells send handover preparation failure

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034




Counter ID


on

Feature ID

Feature Name

messagesLOFD-001020

TDLOFD-001020

LOFD-001046

TDLOFD-001046

LOFD-001073

LOFD-001023

TDLOFD-001023

GERAN





SRVCC to GERAN

SRVCC to GERAN

1526728309

L.IRATHO.E2T.Prep.FailOut.MME Number of inter-

Multi-mode:

CS Fallback

Counter ID


on

Feature ID

Feature Name

RAT handover preparation failures from E-UTRAN to TD-SCDMA network because of faults on the MME side

None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001019

TDLOFD-001019

LOFD-001043

TDLOFD-001043

LOFD-001072

LOFD-001022

TDLOFD-001022

to UTRAN






Distance based Inter-RAT

Counter ID


on

Feature ID

Feature Name

handover to UTRAN

SRVCC to UTRAN

SRVCC to UTRAN

1526728310

L.IRATHO.E2T.Prep.FailOut.NoReply Number of inter-RAT handover preparation failures from E-UTRAN to TD-SCDMA network due tobecause of no responses from TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001019

TDLOFD-001019

LOFD-001043

TDLOFD-001043

LOFD-





Service based inter-RAT handover

Counter ID


on

Feature ID

Feature Name

001072

LOFD-001022

TDLOFD-001022

to UTRAN



SRVCC to UTRAN

SRVCC to UTRAN

1526728311

L.IRATHO.E2T.Prep.FailOut.PrepFailure Number of inter-RAT handover preparation failures because TD-SCDMA network cells send handover preparation failure messages

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033




Counter ID


on

Feature ID

Feature Name

LOFD-001019

TDLOFD-001019

LOFD-001043

TDLOFD-001043

LOFD-001072

LOFD-001022

TDLOFD-001022

UTRAN





SRVCC to UTRAN

SRVCC to UTRAN

1526728312

L.IRATHO.BlindHO.E2W.ExecAttOut Number of inter-

Multi-mode:

PS Inter-RAT

Counter ID


on

Feature ID

Feature Name

RAT blind handovers executions from E-UTRAN to WCDMA network

None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN


1526728313

L.IRATHO.BlindHO.E2W.ExecSuccOut Number of successful inter-RAT blind handovers from E-UTRAN to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-


SRVCC to

Counter ID


on

Feature ID

Feature Name

001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN



SRVCC 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


SRVCC to GERAN


PS Inter-RAT

Counter ID


on

Feature ID

Feature Name

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034

Mobility between E-UTRAN and GERAN

SRVCC to GERAN


1526728315

L.IRATHO.BlindHO.E2G.ExecSuccOut Number of successful inter-RAT 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

TDLOF


SRVCC to GERAN



SRVCC to

Counter ID


on

Feature ID

Feature Name

D-001034

GERAN


1526728321

L.CSFB.PrepAtt Number of CSFB indicators received by the eNodeB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

TDLOFD-001035







1526728322

L.CSFB.PrepSucc Number of successful CSFB responses

Multi-mode: None

GSM:


Counter ID


on

Feature ID

Feature Name

from the eNodeB None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

TDLOFD-001035






1526728323

L.CSFB.E2W Number of procedures for CSFB to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-




Ultra-

Counter ID


on

Feature ID

Feature Name

001033

LOFD-070202

TDLOFD-081223

Flash CSFB to UTRAN

1526728324

L.CSFB.E2G Number of procedures for CSFB to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526728326

L.RRCRedirection.E2W Number of redirections from E-UTRAN to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001033

TDLOFD-




Counter ID


on

Feature ID

Feature Name

001019

TDLOFD-001033

UTRAN and UTRAN


1526728327

L.RRCRedirection.E2G Number of redirections from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001020

LOFD-001034

TDLOFD-001020

TDLOFD-001034





1526728328

L.IRATHO.BlindHO.E2W.PrepAttOut Number of inter-RAT blind handover attempts from E-UTRAN to WCDMA

Multi-mode: None

GSM: None

UMTS: None


CS Fallback to

Counter ID


on

Feature ID

Feature Name

networkLTE: LOFD-001033

TDLOFD-001033

LOFD-001019

TDLOFD-001019

UTRAN



1526728329

L.IRATHO.BlindHO.E2G.PrepAttOut Number of inter-RAT blind handover attempts from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001020

TDLOFD-001020




PS Inter-RAT Mobility between E-UTRAN

Counter ID


on

Feature ID

Feature Name

and GERAN

1526728330

L.RRCRedirection.E2W.PrepAtt Number of redirection preparations from E-UTRAN to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001033

TDLOFD-001019

TDLOFD-001033





1526728331

L.RRCRedirection.E2G.PrepAtt Number of redirection preparations from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001020

LOFD-



PS Inter-

Counter ID


on

Feature ID

Feature Name

001034

TDLOFD-001020

TDLOFD-001034

RAT Mobility between E-UTRAN and GERAN


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


SRVCC to GERAN



SRVCC to GERAN

CS

Counter ID


on

Feature ID

Feature Name

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

Fallback to GERAN

RAN Sharing with Common Carrier

RAN Sharing with Dedicated Carrier



Hybrid RAN Sharing

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


SRVCC to GERAN

Counter ID


on

Feature ID

Feature Name

LOFD-001023

LOFD-001034

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206



SRVCC to GERAN





RAN Sharing with Dedicated

Counter ID


on

Feature ID

Feature Name

Carrier

Hybrid RAN Sharing

1526728382

L.IRATHO.E2G.ExecSuccOut.PLMN Number of successful inter-RAT 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

TDLOF


SRVCC to GERAN



SRVCC to GERAN


RAN Sharing with

Counter ID


on

Feature ID

Feature Name

D-001036

TDLOFD-001037

LOFD-070206

Common Carrier




Hybrid RAN Sharing

1526728386

L.CSFB.PrepAtt.Idle Number of CSFB indicators received by the eNodeB for UEs in idle mode

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001034





Counter ID


on

Feature ID

Feature Name

TDLOFD-001034

LOFD-001035

TDLOFD-001035



1526728387

L.CSFB.PrepSucc.Idle Number of successful CSFB responses from the eNodeB for UEs in idle mode

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

TDLOFD-001035






CS Fallback to CDMA20

Counter ID


on

Feature ID

Feature Name

00 1xRTT

1526728388

L.CSFB.E2W.Idle Number of procedures for CSFB to WCDMA network for UEs in idle mode

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-070202

TDLOFD-081223





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-


SRVCC to UTRAN


Counter ID


on

Feature ID

Feature Name

001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206


SRVCC to UTRAN






Hybrid RAN Sharing

Counter ID


on

Feature ID

Feature Name

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


SRVCC to GERAN



SRVCC to GERAN




Counter ID


on

Feature ID

Feature Name

LOFD-070206

Carrier



Hybrid RAN Sharing

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


SRVCC to UTRAN



Counter ID


on

Feature ID

Feature Name

TDLOFD-001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

SRVCC to UTRAN






Hybrid RAN Sharing

1526728392

L.IRATHO.BlindHO.E2W.ExecSuccOut.PLMN

Number of successful inter-RAT blind handover executions from E-

Multi-mode: None

GSM: None

UMTS:


Counter ID


on

Feature ID

Feature Name

UTRAN to WCDMA network for a specific operator

None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

UTRAN

SRVCC to UTRAN



SRVCC to UTRAN




RAN Sharing with Common

Counter ID


on

Feature ID

Feature Name

Carrier


Hybrid RAN Sharing

1526728393

L.IRATHO.BlindHO.E2G.ExecAttOut.PLMN 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-


SRVCC to GERAN



SRVCC to GERAN

CS Fallback

Counter ID


on

Feature ID

Feature Name

001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

to GERAN





Hybrid RAN Sharing

1526728394

L.IRATHO.BlindHO.E2G.ExecSuccOut.PLMN

Number of successful inter-RAT blind handover executions from E-UTRAN to GERAN for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001020


SRVCC to GERAN

CS

Counter ID


on

Feature ID

Feature Name

LOFD-001023

LOFD-001034

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

Fallback to GERAN


SRVCC to GERAN






Counter ID


on

Feature ID

Feature Name

Carrier

Hybrid RAN Sharing

1526728497

L.RRCRedirection.E2W.CSFB Number of CSFB-based redirections from E-UTRANs to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526728498

L.RRCRedirection.E2G.CSFB Number of CSFB-based redirections from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526728500

L.RRCRedirection.E2T.CSFB Number of CSFB-based redirectio

Multi-mode: None

CS Fallback to

Counter ID


on

Feature ID

Feature Name

ns from E-UTRAN to TD-SCDMA network

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

UTRAN


1526728504

L.IRATHO.E2W.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover preparation attempts from E-UTRAN to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526728505

L.IRATHO.E2W.CSFB.ExecAttOut Number of CSFB-based inter-RAT handover execution attempts from E-UTRAN to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033



Counter ID


on

Feature ID

Feature Name

TDLOFD-001033

1526728506

L.IRATHO.E2W.CSFB.ExecSuccOut Number of successful CSFB-based inter-RAT handover executions from E-UTRAN to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526728507

L.IRATHO.E2G.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover preparation attempts from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526728508

L.IRATHO.E2G.CSFB.ExecAttOut Number of CSFB-based inter-RAT handover execution

Multi-mode: None

GSM: None


CS

Counter ID


on

Feature ID

Feature Name

attempts from E-UTRAN to GERAN

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

Fallback to GERAN

1526728509

L.IRATHO.E2G.CSFB.ExecSuccOut Number of successful CSFB-based inter-RAT handover executions from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526728510

L.IRATHO.E2T.CSFB.PrepAttOut Number of CSFB-based inter-RAT handover preparation attempts from E-UTRAN to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



Counter ID


on

Feature ID

Feature Name

1526728511

L.IRATHO.E2T.CSFB.ExecAttOut Number of CSFB-based inter-RAT handover execution attempts from E-UTRAN to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526728512

L.IRATHO.E2T.CSFB.ExecSuccOut Number of successful CSFB-based inter-RAT handover executions from E-UTRAN to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526728513

L.CSFB.PrepFail.Conflict Number of CSFB preparation failures because of process conflict

Multi-mode: None

GSM: None

UMTS: None

LTE:



CS

Counter ID


on

Feature ID

Feature Name

LOFD-001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

Fallback 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


SRVCC to UTRAN



SRVCC

Counter ID


on

Feature ID

Feature Name

TDLOFD-001033

LOFD-001105

TDLOFD-001105

to UTRAN


Dynamic DRX

Dynamic DRX

1526728561

L.IRATHO.E2W.NoData.ExecSuccOut Number of successful inter-RAT 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


SRVCC to UTRAN



SRVCC to UTRAN

Counter ID


on

Feature ID

Feature Name

LOFD-001105

TDLOFD-001105


Dynamic DRX

Dynamic DRX

1526728705

L.FlashCSFB.E2W Number of procedures for flash CSFB to WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001052

TDLOFD-001052



1526728706

L.FlashCSFB.E2G Number of procedures for flash CSFB to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001053

TDLOFD-001053



Counter ID


on

Feature ID

Feature Name

1526728707

L.CSFB.PrepAtt.Emergency Number of CSFB indicators received by the eNodeB for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

TDLOFD-001035







1526728708

L.CSFB.PrepSucc.Emergency Number of responses sent from the eNodeB for CSFB triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-



CS Fallback

Counter ID


on

Feature ID

Feature Name

001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

TDLOFD-001035

to GERAN




1526728709

L.CSFB.E2W.Emergency Number of procedures for CSFB to WCDMA network triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-070202

TDLOFD-





Counter ID


on

Feature ID

Feature Name

081223

1526728710

L.CSFB.E2G.Emergency Number of procedures for CSFB to GERAN triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526728746

L.IRATHO.BlindHO.E2T.PrepAttOut Number of inter-RAT blind handover attempts from E-UTRAN to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001019

TDLOFD-001019





Counter ID


on

Feature ID

Feature Name

UTRAN

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


SRVCC to UTRAN



SRVCC to UTRAN


1526728748

L.IRATHO.BlindHO.E2T.ExecSuccOut Number of successful inter-RAT blind handovers from E-UTRAN

Multi-mode: None

GSM: None

UMTS:


Counter ID


on

Feature ID

Feature Name

to TD-SCDMA network

None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN

SRVCC to UTRAN



SRVCC to UTRAN


1526728749

L.CSFB.E2T Number of procedures for SRVCC to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



Counter ID


on

Feature ID

Feature Name

1526728750

L.CSFB.E2T.Idle Number of procedures for SRVCC to TD-SCDMA network for UEs in idle mode

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526728751

L.RRCRedirection.E2T.PrepAtt Number of redirection preparations to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001033

TDLOFD-001019

TDLOFD-001033





15267287 L.RRCRedirection.E2T Number Multi- PS Inter-

Counter ID


on

Feature ID

Feature Name

52 of redirections to TD-SCDMA network

mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001033

TDLOFD-001019

TDLOFD-001033





1526728870

L.IRATHO.T2E.PrepAttIn Number of inter-RAT handover attempts from TD-SCDMA network to E-UTRAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033


SRVCC to UTRAN


PS Inter-

Counter ID


on

Feature ID

Feature Name

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN


1526728871

L.IRATHO.T2E.PrepInSucc Number of successful inter-RAT handover preparations from TD-SCDMA network to E-UTRAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022


SRVCC to UTRAN



SRVCC

Counter ID


on

Feature ID

Feature Name

TDLOFD-001033

to UTRAN


1526728872

L.IRATHO.T2E.ExecSuccIn Number of successful inter-RAT handovers from TD-SCDMA network to E-UTRAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN


1526728873

L.IRATHO.T2E.PrepInFail.TgtNotAllow Number of inter-

Multi-mode:

PS Inter-RAT

Counter ID


on

Feature ID

Feature Name

RAT handover preparation failures from TD-SCDMA network in the target cell due to Handover Target not allowed

None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC 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-


SRVCC to

Counter ID


on

Feature ID

Feature Name

001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN



SRVCC to UTRAN


1526728875

L.IRATHO.W2E.PrepInSucc Number of successful inter-RAT handover preparations from WCDMA network to E-UTRAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033


SRVCC to UTRAN


PS Inter-RAT

Counter ID


on

Feature ID

Feature Name

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN


1526728876

L.IRATHO.W2E.ExecSuccIn Number of successful inter-RAT 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

TDLOF


SRVCC to UTRAN



SRVCC to

Counter ID


on

Feature ID

Feature Name

D-001033

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


SRVCC to UTRAN



SRVCC to UTRAN


1526728899

L.IRATHO.E2W.CSFB.MMEAbnormRsp Number of responses

Multi-mode:

CS Fallback to

Counter ID


on

Feature ID

Feature Name

for abnormal causes received by the eNodeB from the MME during CSFB-based inter-RAT handover executions from E-UTRAN to WCDMA network

None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

UTRAN


1526728900

L.IRATHO.E2G.CSFB.MMEAbnormRsp Number of responses for abnormal causes received by the eNodeB from the MME during CSFB-based inter-RAT handover executions from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526728901

L.IRATHO.E2T.CSFB.MMEAbnormRsp Number of responses for abnormal

Multi-mode: None

GSM:


Counter ID


on

Feature ID

Feature Name

causes received by the eNodeB from the MME during CSFB-based inter-RAT handover executions from E-UTRAN to TD-SCDMA network

None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033


1526728946

L.RIM.SI.E2W.Req Number of times the eNodeB sends a system information request to a WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001052

TDLOFD-001052



1526728947

L.RIM.SI.E2W.Resp Number of times the eNodeB receives a system information response from a WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE:



Counter ID


on

Feature ID

Feature Name

LOFD-001052

TDLOFD-001052

1526728948

L.RIM.SI.E2W.Update Number of times the eNodeB receives a system information update from a WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001052

TDLOFD-001052



1526728949

L.RIM.Load.E2W.Req Number of times the eNodeB sends a load information request to a WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001044

TDLOFD-001044

Inter-RAT Load Sharing to UTRAN


1526728950

L.RIM.Load.E2W.Resp Number of times the

Multi-mode:

Inter-RAT Load

Counter ID


on

Feature ID

Feature Name

eNodeB receives a load information response from a WCDMA network

None

GSM: None

UMTS: None

LTE: LOFD-001044

TDLOFD-001044

Sharing to UTRAN


1526728951

L.RIM.Load.E2W.Update Number of times the eNodeB receives a load information update from a WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001044

TDLOFD-001044



1526729260

L.CSFB.E2G.Idle Number of procedures for CSFB to GERAN network for UEs in idle mode

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-



Counter ID


on

Feature ID

Feature Name

001034

TDLOFD-001034

1526729432

L.IRATHO.E2W.TimeAvg Average handover duration 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


SRVCC to UTRAN



SRVCC to UTRAN


1526729433

L.IRATHO.E2G.TimeAvg Average handover duration from E-

Multi-mode: None

PS Inter-RAT Mobility between

Counter ID


on

Feature ID

Feature Name

UTRAN to GERAN

GSM: None

UMTS: None

LTE: LOFD-001020

LOFD-001023

LOFD-001034

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034

E-UTRAN and GERAN

SRVCC to GERAN



SRVCC to GERAN


1526729434

L.IRATHO.E2T.TimeAvg Average handover duration from E-UTRAN to TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019


SRVCC to UTRAN

CS

Counter ID


on

Feature ID

Feature Name

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

Fallback to UTRAN


SRVCC to UTRAN


1526729503

L.RRCRedirection.E2W.PLMN Number of redirections from E-UTRAN to WCDMA network for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001033

TDLOFD-001019

TDLOFD-




Counter ID


on

Feature ID

Feature Name

001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206






Hybrid RAN Sharing

1526729504

L.RRCRedirection.E2G.PLMN Number of redirections from E-UTRAN to GERAN for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-


CS Fallback to

Counter ID


on

Feature ID

Feature Name

001020

LOFD-001034

TDLOFD-001020

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

GERAN







Hybrid RAN Sharing

15267295 L.CCOwithNACC.E2G.CSFB.ExecAttOut Number Multi- CS

Counter ID


on

Feature ID

Feature Name

05 of CSFB-based CCO with NACC executions from E-UTRAN to GERAN

mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

Fallback to GERAN


1526729506

L.CCOwithNACC.E2G.CSFB.ExecSuccOut Number of successful CSFB-based CCOs with NACC from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526729507

L.CCOwithoutNACC.E2G.CSFB.ExecAttOut Number of CSFB-based CCO without NACC executions from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-



Counter ID


on

Feature ID

Feature Name

001034

TDLOFD-001034

1526729508

L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut

Number of successful CSFB-based CCOs without NACC from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526729509

L.IRATHO.E2W.CSFB.PrepAttOut.Emergency

Number of CSFB-based handover preparation attempts to WCDMA network triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526729510

L.IRATHO.E2W.CSFB.ExecAttOut.Emergency

Number of CSFB-based handover

Multi-mode: None

CS Fallback to

Counter ID


on

Feature ID

Feature Name

execution attempts to WCDMA network triggered for emergency calls

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

UTRAN


1526729511

L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency

Number of successful CSFB-based handover executions to WCDMA network triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526729512

L.IRATHO.E2G.CSFB.PrepAttOut.Emergency

Number of CSFB-based handover preparation attempts to GERAN triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034



Counter ID


on

Feature ID

Feature Name

TDLOFD-001034

1526729513

L.IRATHO.E2G.CSFB.ExecAttOut.Emergency

Number of CSFB-based handover execution attempts to GERAN triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526729514

L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency

Number of successful CSFB-based handover executions to GERAN triggered for emergency calls

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526729515

L.RRCRedirection.E2W.CSFB.TimeOut Number of CSFB-based blind redirections from E-

Multi-mode: None

GSM: None


CS

Counter ID


on

Feature ID

Feature Name

UTRAN to WCDMA network caused by CSFB protection timer expiration

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

Fallback to UTRAN

1526729516

L.RRCRedirection.E2G.CSFB.TimeOut Number of CSFB-based blind redirections from E-UTRAN to GERAN caused by CSFB protection timer expiration

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034



1526729562

L.IRATHO.NCell.E2G.PrepAttOut Number of handover attempts from a specific E-UTRAN cell to a specific GERAN cell

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001020

LOFD-001023


SRVCC to GERAN

CS Fallback to

Counter ID


on

Feature ID

Feature Name

LOFD-001034

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034

GERAN


SRVCC to GERAN


1526729563

L.IRATHO.NCell.E2G.ExecAttOut Number of handover executions from a specific E-UTRAN cell to a specific GERAN cell

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001020

LOFD-001023

LOFD-001034

TDLOFD-001020

TDLOF


SRVCC to GERAN



Counter ID


on

Feature ID

Feature Name

D-001023

TDLOFD-001034

GERAN

SRVCC to GERAN


1526729564

L.IRATHO.NCell.E2G.ExecSuccOut Number of successful handovers from a specific E-UTRAN cell to a specific GERAN cell

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001020

LOFD-001023

LOFD-001034

TDLOFD-001020

TDLOFD-001023

TDLOFD-001034


SRVCC to GERAN



SRVCC to GERAN

CS Fallback to

Counter ID


on

Feature ID

Feature Name

GERAN

1526729565

L.IRATHO.NCell.E2W.PrepAttOut Number of handover attempts from a specific E-UTRAN cell to a specific WCDMA cell

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN


1526729566

L.IRATHO.NCell.E2W.ExecAttOut Number of handover executions from a specific E-UTRAN cell to a

Multi-mode: None

GSM: None

UMTS:


Counter ID


on

Feature ID

Feature Name

specific WCDMA cell

None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN

SRVCC to UTRAN



SRVCC to UTRAN


1526729567

L.IRATHO.NCell.E2W.ExecSuccOut Number of successful handovers from a specific E-UTRAN cell to a specific WCDMA cell

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022


SRVCC to UTRAN

CS Fallback to

Counter ID


on

Feature ID

Feature Name

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN


SRVCC to UTRAN


1526729661

L.RIM.SI.E2G.Req Number of times the eNodeB sends a system information request to a GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001053

TDLOFD-001053



1526729662

L.RIM.SI.E2G.Resp Number of times the eNodeB receives a system information response

Multi-mode: None

GSM: None

UMTS:


Flash CS Fallback to

Counter ID


on

Feature ID

Feature Name

from a GERAN None

LTE: LOFD-001053

TDLOFD-001053

GERAN

1526729663

L.RIM.SI.E2G.Update Number of times the eNodeB receives a system information update from a GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001053

TDLOFD-001053



1526730044

L.CSFB.PrepAtt.PLMN Number of CSFB indicators received by the eNodeB for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033




CS Fallback to

Counter ID


on

Feature ID

Feature Name

LOFD-001034

TDLOFD-001034

LOFD-001035

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

GERAN






Hybrid RAN Sharing

1526730045

L.CSFB.PrepSucc.PLMN Number of successful CSFB responses sent from the eNodeB

Multi-mode: None

GSM: None

UMTS:


CS Fallback to

Counter ID


on

Feature ID

Feature Name

for a specific operator

None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001034

TDLOFD-001034

LOFD-001035

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

UTRAN








Hybrid RAN

Counter ID


on

Feature ID

Feature Name

Sharing

1526730046

L.RRCRedirection.E2W.CSFB.PLMN Number of CSFB-based redirections from E-UTRAN to WCDMA network for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206







Hybrid RAN Sharing

1526730047

L.IRATHO.E2W.CSFB.PrepAttOut.PLMN Number of CSFB-based handover preparation attempts

Multi-mode: None

GSM: None


CS

Counter ID


on

Feature ID

Feature Name

from E-UTRAN to WCDMA network for a specific operator

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

Fallback to UTRAN





Hybrid RAN Sharing

1526730048

L.IRATHO.E2W.CSFB.ExecAttOut.PLMN Number of CSFB-based handover execution attempts from E-UTRAN to WCDMA network for a specific

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033



RAN Sharing with

Counter ID


on

Feature ID

Feature Name

operatorTDLOFD-001033

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

Common Carrier




Hybrid RAN Sharing

1526730049

L.IRATHO.E2W.CSFB.ExecSuccOut.PLMN Number of successful CSFB-based handover executions from E-UTRAN to WCDMA network for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

LOFD-001036





Counter ID


on

Feature ID

Feature Name

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

Carrier



Hybrid RAN Sharing

1526730050

L.RRCRedirection.E2G.CSFB.PLMN Number of CSFB-based redirections from E-UTRAN to GERAN for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036





RAN Sharing with Common

Counter ID


on

Feature ID

Feature Name

TDLOFD-001037

LOFD-070206

Carrier


Hybrid RAN Sharing

1526730051

L.IRATHO.E2G.CSFB.PrepAttOut.PLMN Number of CSFB-based handover preparation attempts from E-UTRAN to GERAN for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-







Counter ID


on

Feature ID

Feature Name

070206 Carrier

Hybrid RAN Sharing

1526730052

L.IRATHO.E2G.CSFB.ExecAttOut.PLMN Number of CSFB-based handover execution attempts from E-UTRAN to GERAN for a specific operator

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206







Hybrid RAN Sharing

1526730053

L.IRATHO.E2G.CSFB.ExecSuccOut.PLMN Number of

Multi-mode:

CS Fallback

Counter ID


on

Feature ID

Feature Name

successful CSFB-based handover executions from E-UTRAN to GERAN for a specific operator

None

GSM: None

UMTS: None

LTE: LOFD-001034

TDLOFD-001034

LOFD-001036

LOFD-001037

TDLOFD-001036

TDLOFD-001037

LOFD-070206

to GERAN






Hybrid RAN Sharing

1526730076

L.IRATHO.E2W.CSFB.Prep.FailOut.MME Number of CSFB-based outgoing handover preparation failures from E-UTRAN to

Multi-mode: None

GSM: None

UMTS: None



Counter ID


on

Feature ID

Feature Name

WCDMA network because of the MME side causes

LTE: LOFD-001033

TDLOFD-001033

1526730077

L.IRATHO.E2W.CSFB.Prep.FailOut.PrepFailure

Number of CSFB-based outgoing handover preparation failures from E-UTRAN to WCDMA network because of the response of handover preparation failure from WCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526730078

L.IRATHO.E2W.CSFB.Prep.FailOut.NoReply Number of CSFB-based outgoing handover preparation failures from E-UTRAN to WCDMA network because of no response

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOF



Counter ID


on

Feature ID

Feature Name

from WCDMA network

D-001033

1526730079

L.IRATHO.E2T.CSFB.Prep.FailOut.MME Number of CSFB-based outgoing handover preparation failures from E-UTRAN to TD-SCDMA network because of the MME side causes

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526730080

L.IRATHO.E2T.CSFB.Prep.FailOut.PrepFailure

Number of CSFB-based outgoing handover preparation failures from E-UTRAN to TD-SCDMA network because of the response of handover preparation failure from TD-SCDMA network

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



1526730081

L.IRATHO.E2T.CSFB.Prep.FailOut.NoReply Number of CSFB-

Multi-mode:

CS Fallback

Counter ID


on

Feature ID

Feature Name

based outgoing handover preparation failures from E-UTRAN to TD-SCDMA network because of no response from TD-SCDMA network

None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033

to UTRAN


1526730146

L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut Number of SRVCC-based outgoing handover attempts from E-UTRAN to WCDMA network for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-070202


1526730147

L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut Number of SRVCC-based outgoing handover executions from E-UTRAN to WCDMA network for ultra-flash

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-070202


Counter ID


on

Feature ID

Feature Name

CSFB

1526730148

L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut Number of successful SRVCC-based outgoing handovers from E-UTRAN to WCDMA network for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-070202


1526733006

L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut Number of SRVCC-based outgoing handover attempts from E-UTRAN to GERAN for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-081283

TDLOFD-081203



1526733007

L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut Number of SRVCC-based outgoing handover executions from E-UTRAN to GERAN

Multi-mode: None

GSM: None

UMTS: None

LTE:



Counter ID


on

Feature ID

Feature Name

for ultra-flash CSFB

LOFD-081283

TDLOFD-081203

1526733008

L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut Number of successful SRVCC-based outgoing handovers from E-UTRAN to GERAN for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-081283

TDLOFD-081203



1526733009

L.IRATHO.CSFB.SRVCC.E2G.MMEAbnormRsp

Number of abnormal responses from the MME during outgoing handovers from E-UTRAN to GERAN for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-081283

TDLOFD-081203



1526736728

L.IRATHO.CSFB.SRVCC.E2W.MMEAbnormRsp

Number of responses

Multi-mode:

Ultra-Flash CSFB to

Counter ID


on

Feature ID

Feature Name

for abnormal causes received by the eNodeB from the MME during handovers from the E-UTRAN to WCDMA networks for ultra-flash CSFB

None

GSM: None

UMTS: None

LTE: LOFD-070202

TDLOFD-081223

UTRAN


1526736729

L.IRATHO.E2W.CSFB.SRVCC.Prep.FailOut.MME

Number of MME-caused preparation failures of outgoing handovers to WCDMA networks for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-070202


1526736730

L.IRATHO.E2W.CSFB.SRVCC.Prep.FailOut.PrepFailure

Number of preparation failures of outgoing handovers to WCDMA networks for ultra-flash

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-


Counter ID


on

Feature ID

Feature Name

CSFB because of the response of handover preparation failure sent by the WCDMA networks

070202

1526736731

L.IRATHO.E2W.CSFB.SRVCC.Prep.FailOut.NoReply

Number of preparation failures of outgoing handovers to WCDMA networks for ultra-flash CSFB because of no response from the WCDMA networks

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-070202


1526736732

L.IRATHO.E2G.CSFB.SRVCC.Prep.FailOut.MME

Number of MME-caused preparation failures of outgoing handovers to GERANs for ultra-flash CSFB

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-081283



Counter ID


on

Feature ID

Feature Name

TDLOFD-081203

1526736733

L.IRATHO.E2G.CSFB.SRVCC.Prep.FailOut.PrepFailure

Number of preparation failures of outgoing handovers to GERANs for ultra-flash CSFB because of the response of handover preparation failure sent by the GERANs

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-081283

TDLOFD-081203



1526736734

L.IRATHO.E2G.CSFB.SRVCC.Prep.FailOut.NoReply

Number of preparation failures of outgoing handovers to GERANs for ultra-flash CSFB because of no response from the GERANs

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-081283

TDLOFD-081203



15267367 L.IRATHO.T2E.PrepInFail.AdmitFail Number Multi- PS Inter-

Counter ID


on

Feature ID

Feature Name

45 of TDSCDMA-to-EUTRAN handover preparation failures because of admission failure

mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN


1526736746

L.IRATHO.T2E.PrepInFail.FlowCtrl Number of TDSCDMA-to-EUTRAN handover preparation failures because of flow control

Multi-mode: None

GSM: None

UMTS: None

LTE:


SRVCC to

Counter ID


on

Feature ID

Feature Name

LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN



SRVCC to UTRAN


1526736747

L.IRATHO.T2E.PrepInFail.HOCancel Number of TDSCDMA-to-EUTRAN handover preparation failures because the target cell receives handover cancelation messages

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033


SRVCC to UTRAN


PS Inter-RAT

Counter ID


on

Feature ID

Feature Name

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN


1526736748

L.IRATHO.T2E.PrepInFail.disc.FlowCtrl Number of times TDSCDMA-to-EUTRAN handover messages are discarded because of flow control

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOF


SRVCC to UTRAN



SRVCC to

Counter ID


on

Feature ID

Feature Name

D-001033

UTRAN


1526736749

L.IRATHO.W2E.PrepInFail.AdmitFail Number of WCDMA-to-EUTRAN handover preparation failures because of admission failure

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN


1526736750

L.IRATHO.W2E.PrepInFail.FlowCtrl Number of WCDMA-

Multi-mode:


Counter ID


on

Feature ID

Feature Name

to-EUTRAN handover preparation failures because of flow control

None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

between E-UTRAN and UTRAN

SRVCC to UTRAN



SRVCC to UTRAN


1526736751

L.IRATHO.W2E.PrepInFail.HOCancel Number of WCDMA-to-EUTRAN handover preparation failures because the target cell receives handover

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019


SRVCC to UTRAN

Counter ID


on

Feature ID

Feature Name

cancelation messages

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033



SRVCC to UTRAN


1526736752

L.IRATHO.W2E.PrepInFail.disc.FlowCtrl Number of times WCDMA-to-EUTRAN handover messages are discarded because of flow control

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-


SRVCC to UTRAN


PS Inter-RAT Mobility between

Counter ID


on

Feature ID

Feature Name

001019

TDLOFD-001022

TDLOFD-001033

E-UTRAN and UTRAN

SRVCC to UTRAN


1526736753

L.IRATHO.G2E.PrepInFail Number of GERAN-to-EUTRAN handover preparation failures

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN

Counter ID


on

Feature ID

Feature Name


1526736754

L.IRATHO.T2E.PrepInFail Number of TDSCDMA-to-EUTRAN handover preparation failures

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033


SRVCC to UTRAN



SRVCC to UTRAN


1526736755

L.IRATHO.W2E.PrepInFail Number of WCDMA-to-EUTRAN

Multi-mode: None

GSM:


Counter ID


on

Feature ID

Feature Name

handover preparation failures

None

UMTS: None

LTE: LOFD-001019

LOFD-001022

LOFD-001033

TDLOFD-001019

TDLOFD-001022

TDLOFD-001033

UTRAN and UTRAN

SRVCC to UTRAN



SRVCC to UTRAN


1526736760

L.IRATHO.E2W.CSFB.MMEAbnormRsp.PLMN

Number of responses for abnormal causes received by the eNodeB from the MME during CSFB-based inter-RAT

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOF



Counter ID


on

Feature ID

Feature Name

handover executions from E-UTRAN to WCDMA network for a specific operator

D-001033

1526737720

L.RRCRedirection.E2T.CSFB.TimeOut Number of CSFB-based blind LTE-to-TD-SCDMA redirections triggered due to timer expiration

Multi-mode: None

GSM: None

UMTS: None

LTE: LOFD-001033

TDLOFD-001033



10 GlossaryFor the acronyms, abbreviations, terms, and definitions, see Glossary.

11 Reference Documents1. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"2. 3GPP TS 23.216, "Single Radio Voice Call Continuity (SRVCC); Stage 2"3. VoLGA Forum Specifications4. 3GPP TS 36.300, "E-UTRAN Overall description"5. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved

Universal Terrestrial Radio Access Network (E-UTRAN) access "6. 3GPP TS 48.018, "General Packet Radio Service (GPRS); Base Station System (BSS)

- Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP) "7. VoLGA Forum Specifications Inter-RAT Mobility Management in Connected Mode

8. Emergency Call 9. LCS 10. Interoperability Between GSM and LTE11. Interoperability Between UMTS and LTE

Cs fall back

Engineering

Transcript of Cs fall back