Thursday, 15 September 2016

SRVCC Feature Parameter


Overview
SRVCC is a solution to provide voice services on LTE networks. In the early phase of LTE deployment, when UEs running voice services move out of an LTE network, the voice services can continue in the legacy circuit switched (CS) domain by means of SRVCC, thereby ensuring voice service continuity.

2.1 Introduction

The SRVCC technology is used to ensure voice service continuity when a single-radio UE is handed over from the E-UTRAN to the UTRAN or GERAN.
NOTE:
A single-radio UE is capable of working only in one of the following RATs at a given time: E-UTRAN, UTRAN or GERAN.
After a UE accesses the E-UTRAN, its packet switched (PS) bearers are established by the mobility management entity (MME), serving gateway (S-GW), and PDN gateway (P-GW). Then, this UE can use one of the PS bearers to access the IMS for a voice over IP (VoIP) service. When the UE moves out of the E-UTRAN, the UE must continue its voice service on the legacy CS domain in a UMTS or GSM network where the mobile switching center (MSC) server is responsible for voice communication. When the UE with an ongoing session is to be handed over from the E-UTRAN to the UTRAN or GERAN, the MME initiates a handover request to the MSC server to transfer the session without interruption. This is an SRVCC procedure.
SRVCC is a means of inter-RAT handover. RAT is short for radio access technology. It enables a smooth session transfer from VoIP over IMS on the LTE network to CS services in the UTRAN or GERAN.

2.2 Benefits

Before the E-UTRAN is deployed across the operator's coverage areas, SRVCC is used to ensure voice service continuity. At the edge of the E-UTRAN, UEs running VoIP services can be handed over to the UTRAN or GERAN by means of SRVCC, which transforms the VoIP services into CS services. SRVCC or enhanced SRVCC (eSRVCC) reduces the service interruption period during a handover to improve user experience with voice services.
For details about eSRVCC, see 2.3.2 eSRVCC.

2.3 Architecture

2.3.1 SRVCC

The SRVCC technology is achieved by access-stratum handovers between bearer networks, and IMS session transfer. To support SRVCC, the Sv interface between the MSC server and MME is added to the network. Figure 2-1 shows the SRVCC network architecture.
Figure 2-1 SRVCC network architecture
Table 2-1 describes the elements of the SRVCC network architecture
Table 2-1 Elements of the SRVCC network architecture
Element
Function
Sv interface
Supports SRVCC as an interface between the MME and MSC server.
E-UTRAN
During the SRVCC procedure, the E-UTRAN sends an SRVCC indication to the MME, notifying the MME whether the target cell supports SRVCC and concurrent CS and PS handovers.
UTRAN/GERAN
  • Supports incoming CS handovers for CS-only SRVCC.
  • Supports concurrent incoming CS and PS handovers for CS-and-PS SRVCC.
MME
  • Provides the bearer splitting function to separate the voice bearer from non-voice bearers. Then, the MME initiates a CS handover procedure for the voice bearer towards the MSC server and initiates a PS handover procedure for the non-voice bearers towards the serving GPRS support node (SGSN).
  • Initiates an SRVCC procedure over the Sv interface for an emergency call and includes an emergency indication in the transmitted message.
  • Selects the MSC server that is enhanced for SRVCC (shown as SRVCC MSC server in Figure 2-1) based on the domain name server (DNS) procedures or MME configuration.
SRVCC MSC server
Processes CS handovers and session transfer.
SGSN
Processes PS handovers for PS services during the CS-and-PS SRVCC procedure.
Proxy-call session control function (P-CSCF)
Acts as the first contact point for the UE within the IMS:
  • Provides the proxy function by accepting and forwarding service requests, but cannot modify the Request URI field in the INVITE message.
  • Provides the user agent (UA) function by terminating and independently creating Session Initiation Protocol (SIP) sessions when exceptions occur.
Serving-call session control function (S-CSCF)
Acts as the control center of the IMS:
  • Processes registration and authentication requests from UEs and controls sessions.
  • Provides basic session routing for calling and called parties on the IMS.
  • Routes value-added services to the application server (AS) and performs service control interactions according to the IMS rules to which users are subscribed.
Interrogating-call session control function (I-CSCF)
Assigns S-CSCFs to UEs, supports route query, and forwards SIP requests to another IMS domain.
Media gateway control function (MGCF)
Enables interworking between the IMS control plane and legacy CS network.
Service centralization and continuity application server (SCC AS)
Ensures the centralization and continuity of VoIP services on the LTE network.
The procedure is as follows:
  1. The MME informs the SRVCC MSC server over the Sv interface that a voice service is to be handed over to the CS domain.
  2. The SRVCC MSC server performs the following operations:
    • Instructs the UTRAN/GERAN to prepare for the handover.
    • Requests the media gateway (MGW) to provide new media-plane information, including the IP address and port number.
    • Notifies the SCC AS (that is a control point for the IMS session transfer) that the media stream is to be changed.
  3. The SCC AS provides the UE with new media-plane information.
  4. The UE establishes a new VoIP media stream with the MGW and releases the original VoIP media stream.
  5. The MGW converts the established VoIP media stream, if required, to achieve interworking between the CS voice stream and VoIP voice stream. The conversion occurs in protocol stacks and voice coding.

2.3.2 eSRVCC

As defined in section 8.4 in 3GPP TS 25.913 V8.0.0 (2008-12), the service interruption period during a handover of real-time services between the E-UTRAN and the UTRAN or GERAN must be less than 300 ms. Theoretically, the service interruption period during the access-stratum handover in an SRVCC procedure meets the requirement, but the session transfer in the SRVCC procedure cannot be completed within 300 ms. As a result, the total service interruption period is longer than 300 ms. To resolve this issue, 3GPP Release 10 proposes eSRVCC.
eSRVCC focuses on reducing the time for session transfer because session transfer prolongs the service interruption period, especially when the calling and called parties are served by different networks or when a subscriber is roaming.
Compared with the SRVCC network architecture, the eSRVCC network architecture incorporates two new elements:
  • Access transfer control function (ATCF)
    The ATCF acts as an anchor point for signaling messages before and after handovers. To reduce delay, the ATCF must be deployed on the serving network, which is the visited network for roaming subscribers. The MSC server can be located close to the ATCF to shorten the time for signaling routing from the MSC server to the ATCF.
  • Access transfer gateway (ATGW)
    The ATGW acts as a media-plane anchor point for VoIP services before and after handovers. Because the ATGW remains unchanged after a handover, session transfer is not required.
Figure 2-2 shows the eSRVCC network architecture, where the ATCF and ATGW are deployed between the P-CSCF and I-CSCF/S-CSCF.
Figure 2-2 eSRVCC network architecture
For a UE running a voice service that may require SRVCC later, the media plane of the service is anchored to the ATGW. When an SRVCC procedure is initiated for this UE, the media plane information is updated only on the ATGW and not on the UE, thereby shortening the handover duration.
NOTE:
This document focuses on eNodeB functions, which are the same for SRVCC and eSRVCC. Therefore, the following chapters do not distinguish between SRVCC and eSRVCC.

3 SRVCC Procedure and Principles

This chapter describes the standard signaling procedure for SRVCC and the SRVCC algorithm on the eNodeB.

3.1 Signaling Procedure

Figure 3-1 shows the signaling procedure for SRVCC from the E-UTRAN to the UTRAN or GERAN. For details about the procedure, see section 6.2 in 3GPP TS 23.216 V9.4.0.
Figure 3-1 Signaling procedure for SRVCC from the E-UTRAN to the UTRAN or GERAN
  1. After triggering an SRVCC procedure, the eNodeB delivers the inter-RAT measurement configuration to the UE.
  2. Upon detecting that a neighboring cell meets the condition for triggering an inter-RAT handover, the UE sends a measurement report to the eNodeB.
  3. The eNodeB determines to perform a handover and sends the Handover Required message containing an SRVCC HO Indication to the source MME.
  4. The MME separates the voice bearer from non-voice bearers and then sends the Relocation Request message to both the SRVCC MSC server and target SGSN.
  5. After receiving the Relocation Request message, the MSC server instructs the target radio network controller (RNC) or base station controller (BSC) to prepare for a handover. After resources are ready, the target RNC or BSC responds to the target MSC server. The SGSN prepares for a handover of PS services, which is similar to that for an inter-RAT PS handover procedure. The UE session is transferred on the IMS.
    NOTE:
    If the value of the information element (IE) SRVCC HO Indication is "CS Only" in the Handover Required message that the eNodeB sent to the MME, the MME instructs only the MSC server to prepare for a handover. If the value of the IE SRVCC HO Indication is "PS and CS", the MME instructs both the MSC server and SGSN to prepare for a handover.
    For a CS-only SRVCC procedure, if the target network is UTRAN, the PS services of the UE resume during a routing area update (RAU) procedure in the UTRAN. If the target network is GERAN, PS service handling depends on whether the UE and BSC support the Dual Transfer Mode (DTM). If both the UE and BSC support DTM, the PS services of the UE resume during an RAU procedure in the GERAN. If only the UE or BSC supports DTM, the PS services of the UE are suspended.
  6. The MME receives a response from the target MSC server or target SGSN, indicating that the handover preparation is complete.
  7. The MME delivers a handover command to the eNodeB.
  8. The eNodeB delivers a handover command to the UE.
  9. After receiving the handover command, the UE accesses the target network.
  10. The UE sends the target radio access network (RAN) a Handover Complete message, indicating that the handover procedure for SRVCC is complete.

3.2 Basic SRVCC Functions of eNodeBs

This section describes the basic algorithm and parameters for SRVCC involving the following Huawei eNodeB features:
  • TDLOFD-001022 SRVCC to UTRAN
  • TDLOFD-001023 SRVCC to GERAN

3.2.1 Algorithm Framework

SRVCC is an inter-RAT procedure for voice services. Figure 3-2 shows the framework of the SRVCC algorithm.
Figure 3-2 Framework of the SRVCC algorithm
SRVCC consists of the following phases:
  • Triggering
    When a UE is running a voice service, a coverage-, service-, load-, or CSFB-based handover may be required for the UE. CSFB is short for circuit switched fallback. For the handover, the eNodeB triggers an SRVCC procedure based on the UE capabilities and related switch status on the eNodeB.
  • Measurement
    The eNodeB delivers the measurement configuration to the UE based on UE capabilities, and the UE starts measuring the inter-RAT neighboring cells that meet the requirements.
  • Determination and execution
    Based on the measurement report sent by the UE, the eNodeB determines the target cell and performs the handover procedure for SRVCC.

3.2.2 Triggering Phase

Conditions for Triggering the SRVCC Procedure

The eNodeB triggers the SRVCC procedure when all the following conditions are met:
  • The UE is running a voice service.
NOTE:
As defined in section 4.1.2 in 3GPP TS 23.216 V11.1.0, when SRVCC is deployed, bearers with QoS class identifier (QCI) 1 must be used only for voice services. The eNodeB determines that a UE is running a voice service when it detects a service with QCI 1 running on the UE.
  • The UtranSrvccSwitch or GeranSrvccSwitch check box under the HoModeSwitch parameter is selected to enable SRVCC to UTRAN or GERAN, respectively.
  • The UE supports SRVCC.
    Table 3-1 and Table 3-2 list the feature group indicators (FGIs) of SRVCC to UTRAN and GERAN, respectively.
Table 3-1 FGIs of SRVCC to UTRAN
Bit Number
Definition
Remarks
8
The UE supports E-UTRA RRC_CONNECTED to UTRA CELL_DCH PS handover.
This bit number can be set to 1 if bit number 22 is set to 1.
22
The UE in E-UTRA RRC_CONNECTED mode can measure UTRAN cells, report the measurement results, and support event B2 for the measurement.
N/A
27
The UE supports E-UTRA RRC_CONNECTED to UTRA CELL_DCH CS handover.
This bit number is related to SRVCC.
It can be set to 1 if bit number 8 is set to 1.
Table 3-2 FGIs of SRVCC to GERAN
Bit Number
Definition
Remarks
9
The UE supports E-UTRA RRC_CONNECTED to GERAN GSM_Dedicated handover.
This bit number is related to SRVCC.
It can be set to 1 if bit number 23 is set to 1.
23
The UE in E-UTRA RRC_CONNECTED mode can measure GERAN cells, report the measurement results, and support event B2 for the measurement.
N/A
  • The UtranVoipCapSwitch or GeranVoipCapSwitch check box under the HoModeSwitch parameter is cleared, indicating that the UTRAN or GERAN does not support VoIP.
NOTE:
In Huawei eNodeB, VoIP services are carried by bearers with QCI 1 by default.
If both the UtranVoipCapSwitch check box under the HoModeSwitch parameter and the PS_HO check box under the UtranHoCfg parameter are selected, the eNodeB preferentially performs PS handovers for VoIP services. The PS_HO check box indicates the switch for the PS handover of QCI-1 services to UTRAN.

Typical Scenarios for Triggering the SRVCC Procedure

  • Coverage-based
    A coverage-based handover for SRVCC is similar to that for common PS services. When a UE running a VoIP service moves to the edge of the E-UTRAN and the signal quality of the serving cell is lower than a predefined threshold, the eNodeB triggers an SRVCC procedure to ensure voice service continuity for the UE.
  • Uplink-quality-based
    When the eNodeB detects that the uplink signal quality is poor and the UE is running a VoIP service, the eNodeB may trigger an SRVCC procedure based on the measurement result reported by the UE. For details about the uplink-quality-based inter-RAT handover algorithm, see Mobility Management in Connected Mode Feature Parameter Description.
  • Distance-based
    In a distance-based inter-RAT handover, the deviation in the estimated distance between the UE and eNodeB is about 100 meters to 150 meters. This type of handover applies when all the following conditions are met:
    • Both LTE and non-LTE systems are deployed.
    • The LTE system causes severe cross-cell coverage to the non-LTE system.
    • The RF signals from an E-UTRAN cell travel a distance that is much longer than the distance between sites designed in the network plan.
    Distance-based inter-RAT handover can reduce the probability of the UEs being handed over to an inter-RAT cell with which the E-UTRAN cell does not have neighbor relationships but both the cells overlap in coverage. When a distance-based inter-RAT handover is triggered and the UE is running a VoIP service, the eNodeB may trigger an SRVCC procedure according to the measurement result reported by the UE. For details about the distance-based inter-RAT handover algorithm, see Mobility Management in Connected Mode Feature Parameter Description.
  • SPID-based
    In an SPID-based handover, a UE can be handed over from the visited PLMN to its HPLMN when it moves back to the home E-UTRAN. In this scenario, the eNodeB may trigger an SRVCC procedure when the UE is running a VoIP service. For details about the algorithm of SPID-based handover back to the HPLMN, see Flexible User Steering Feature Parameter Description.
  • Service-based
    During a service-based handover for SRVCC, the eNodeB can transfer a UE to an appropriate RAT system based on the services that are running on the UE. A service-based inter-RAT handover policy group can be created for each operator. The groups are specified for different QCIs. In each group, the InterRatHoState parameter defines a service-based handover mode: NO_HO, PERMIT_HO, or MUST_HO.
    For example, if the handover mode is set to MUST_HO for QCI 1, the eNodeB will trigger an SRVCC procedure for the UE running a service with QCI 1.
  • Load-based
    When the eNodeB load reaches a threshold, mobility load balancing (MLB) is triggered. The eNodeB will trigger an SRVCC procedure for the UEs running a service with QCI 1. For details about MLB principles and parameters, see MLB Feature Parameter Description.
  • CSFB-based
    A CSFB-based handover for SRVCC is used when a UE running a VoIP service for an emergency call requires the location service (LCS) in a non-LCS-capable LTE network. When the UE location is requested, the MME delivers a CSFB indicator to the eNodeB. When the UE is running a service with QCI 1, the eNodeB determines whether to trigger an SRVCC procedure based on the setting of LcsSrvccSwitch under the HoModeSwitch parameter. When the eNodeB triggers an SRVCC procedure, the UE falls back to an appropriate CS domain to perform LCS without interrupting voice services. Figure 3-3 shows a CSFB-based handover procedure for SRVCC. For details about the procedure, see section 8.3 in 3GPP TS 23.272 V10.0.0.
    NOTE:
    CSFB-based handover for SRVCC is under the same license and switch control as SRVCC in other scenarios and requires basic SRVCC functions. The scenarios in which a CSFB-based handover for SRVCC is triggered are the same as those for common CSFB services, and CSFB-based handover for SRVCC is controlled by some of the parameters for common CSFB, such as parameters related to event B1 measurement and CSFB steering.
    Figure 3-3 CSFB-based handover procedure for SRVCC

3.2.3 Measurement Phase

The measurement configuration delivered by the eNodeB varies depending on the triggering causes.

3.2.4 Decision and Execution Phase

When the eNodeB receives measurement reports about different RATs and different frequencies, it processes the reports in a first in first out (FIFO) manner. After receiving a measurement report associated with event B1 or B2 from the UE, the eNodeB generates a list of candidate cells, which are indicated by the report. The eNodeB then initiates a handover to the best cell among the candidate cells.
Based on parameter settings, the eNodeB performs the SRVCC procedure as listed in Table 3-3. The parameters are set based on the MME and RNC/BSC capabilities.
Table 3-3 Parameter settings and SRVCC procedure
Target RAT
Parameter
Setting
SRVCC Procedure
UTRAN
BOOLEAN_TRUE
PS-and-CS
BOOLEAN_FALSE
CS-only
GERAN
BOOLEAN_TRUE
PS-and-CS
BOOLEAN_FALSE
CS-only
NOTE:
Because there is no switch to indicate the MME capability, it is recommended that the MME and RNC/BSC capabilities be indicated by the same switch. For example, if either the MME or RNC does not support concurrent CS and PS handovers, set the CsPsHOInd parameter to BOOLEAN_FALSE(False).

4 Related Features

4.1 Features Related to TDLOFD-001022 SRVCC to UTRAN

Prerequisite Features

TDLOFD-001022 SRVCC to UTRAN requires TDLOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN.

Mutually Exclusive Features

None

Impacted Features

None

4.2 Features Related to TDLOFD-001023 SRVCC to GERAN

Prerequisite Features

TTDLOFD-001023 SRVCC to GERAN requires TDLOFD-001020 PS Inter-RAT Mobility between E-UTRAN and GERAN.

Mutually Exclusive Features

None

Impacted Features

None

5 Network Impact

5.1 TDLOFD-001022 SRVCC to UTRAN

System Capacity

No impact.

Network Performance

If the target network of a CS-only SRVCC procedure is a UTRAN, only the bearer with QCI 1 is transferred to the CS domain of the UTRAN, and PS bearers resume during an RAU procedure in the PS domain of the UTRAN. The CS-only SRVCC procedure results in a PS service interruption period of several seconds. However, the PS-and-CS SRVCC procedure results in a PS service interruption period of only hundreds of milliseconds.

5.2 TDLOFD-001023 SRVCC to GERAN

System Capacity

No impact.

Network Performance

If the target network of a CS-only SRVCC procedure is a DTM-supporting GERAN, only the bearer with QCI 1 is transferred to the CS domain of the GERAN, and PS bearers resume during an RAU procedure in the PS domain of the GERAN. The CS-only SRVCC procedure results in a PS service interruption period of several seconds. However, the PS-and-CS SRVCC procedure results in a PS service interruption period of only hundreds of milliseconds.

6 Parameters

Table 6-1 Parameter description
MO
Parameter ID
MML Command
Feature ID
Feature Name
Description
ENodeBAlgoSwitch
HoModeSwitch
MOD ENODEBALGOSWITCH
LST ENODEBALGOSWITCH
LOFD-001019 / TDLOFD-001019
LOFD-001020 / TDLOFD-001020
LOFD-001021
LOFD-001022 / TDLOFD-001022
LOFD-001023 / TDLOFD-001023
LOFD-001033 / TDLOFD-001033
LOFD-001034 / TDLOFD-001034
LOFD-001035
LOFD-001043 / TDLOFD-001043
LOFD-001044 / TDLOFD-001044
LOFD-001045 / TDLOFD-001045
LOFD-001046 / TDLOFD-001046
PS Inter-RAT Mobility between E-UTRAN and UTRAN
PS Inter-RAT Mobility between E-UTRAN and GERAN
PS Inter-RAT Mobility between E-UTRAN and CDMA2000
SRVCC to UTRAN
SRVCC to GERAN
CS Fallback to UTRAN
CS Fallback to GERAN
CS Fallback to CDMA2000 1xRTT
Service based inter-RAT handover to UTRAN
Inter-RAT Load Sharing to UTRAN
Inter-RAT Load Sharing to GERAN
Service based inter-RAT handover to GERAN
Meaning: Indicates the switches corresponding to the inputs based on which the eNodeB determines handover policies. EutranVoipCapSwitch: This switch will be removed in later versions. In this version, the setting of this switch is still synchronized between the M2000 and the eNodeB, but it is no longer used internally. Therefore, avoid using this switch. BlindHoSwitch: This switch controls whether to enable or disable blind handovers during CS fallback. GeranNaccSwitch: This switch does not take effect if GeranCcoSwitch is disabled.
GUI Value Range: EutranVoipCapSwitch(EutranVoipCapSwitch), UtranVoipCapSwitch(UtranVoipCapSwitch), GeranVoipCapSwitch(GeranVoipCapSwitch), Cdma1xRttVoipCapSwitch(Cdma1xRttVoipCapSwitch), UtranPsHoSwitch(UtranPsHoSwitch), GeranPsHoSwitch(GeranPsHoSwitch), CdmaHrpdNonOtpimisedHoSwitch(CdmaHrpdNonOtpimisedHoSwitch), CdmaHrpdOptimisedHoSwitch(CdmaHrpdOptimisedHoSwitch), GeranNaccSwitch(GeranNaccSwitch), GeranCcoSwitch(GeranCcoSwitch), UtranSrvccSwitch(UtranSrvccSwitch), GeranSrvccSwitch(GeranSrvccSwitch), Cdma1xRttSrvccSwitch(Cdma1xRttSrvccSwitch), UtranRedirectSwitch(UtranRedirectSwitch), GeranRedirectSwitch(GeranRedirectSwitch), CdmaHrpdRedirectSwitch(CdmaHrpdRedirectSwitch), Cdma1xRttRedirectSwitch(Cdma1xRttRedirectSwitch), BlindHoSwitch(BlindHoSwitch), LcsSrvccSwitch(LcsSrvccSwitch), AutoGapSwitch(AutoGapSwitch)
Unit: None
Actual Value Range: EutranVoipCapSwitch, UtranVoipCapSwitch, GeranVoipCapSwitch, Cdma1xRttVoipCapSwitch, UtranPsHoSwitch, GeranPsHoSwitch, CdmaHrpdNonOtpimisedHoSwitch, CdmaHrpdOptimisedHoSwitch, GeranNaccSwitch, GeranCcoSwitch, UtranSrvccSwitch, GeranSrvccSwitch, Cdma1xRttSrvccSwitch, UtranRedirectSwitch, GeranRedirectSwitch, CdmaHrpdRedirectSwitch, Cdma1xRttRedirectSwitch, BlindHoSwitch, LcsSrvccSwitch, AutoGapSwitch
Default Value: EutranVoipCapSwitch:On, UtranVoipCapSwitch:Off, GeranVoipCapSwitch:Off, Cdma1xRttVoipCapSwitch:Off, UtranPsHoSwitch:Off, GeranPsHoSwitch:Off, CdmaHrpdNonOtpimisedHoSwitch:Off, CdmaHrpdOptimisedHoSwitch:Off, GeranNaccSwitch:Off, GeranCcoSwitch:Off, UtranSrvccSwitch:Off, GeranSrvccSwitch:Off, Cdma1xRttSrvccSwitch:Off, UtranRedirectSwitch:Off, GeranRedirectSwitch:Off, CdmaHrpdRedirectSwitch:Off, Cdma1xRttRedirectSwitch:Off, BlindHoSwitch:Off, LcsSrvccSwitch:Off, AutoGapSwitch:Off
InterRatPolicyCfgGroup
UtranHoCfg
ADD INTERRATPOLICYCFGGROUP
MOD INTERRATPOLICYCFGGROUP
LST INTERRATPOLICYCFGGROUP
LOFD-001022 / TDLOFD-001022
LOFD-001019 / TDLOFD-001019
SRVCC to UTRAN
PS Inter-RAT Mobility between E-UTRAN and UTRAN
Meaning: Indicates the policy of handovers to UTRAN. PS_HO: indicates whether to allow PS handovers to UTRAN. SRVCC: indicates whether to allow transfers to UTRAN in SRVCC mode. REDIRECTION: indicates whether to allow redirection to UTRAN.
GUI Value Range: PS_HO, SRVCC, REDIRECTION
Unit: None
Actual Value Range: PS_HO, SRVCC, REDIRECTION
Default Value: PS_HO:On, SRVCC:Off, REDIRECTION:Off
ServiceIrHoCfgGroup
InterRatHoState
ADD SERVICEIRHOCFGGROUP
MOD SERVICEIRHOCFGGROUP
LST SERVICEIRHOCFGGROUP
LOFD-001043 / TDLOFD-001043
LOFD-001046 / TDLOFD-001046
Service based inter-RAT handover to UTRAN
Service based inter-RAT handover to GERAN
Meaning: Indicates whether service-based inter-RAT handovers are required, allowed, or not allowed for a QCI.
GUI Value Range: NO_HO, PERMIT_HO, MUST_HO
Unit: None
Actual Value Range: NO_HO, PERMIT_HO, MUST_HO
Default Value: NO_HO
UtranExternalCell
CsPsHOInd
ADD UTRANEXTERNALCELL
MOD UTRANEXTERNALCELL
LST UTRANEXTERNALCELL
LOFD-001019 / TDLOFD-001019
PS Inter-RAT Mobility between E-UTRAN and UTRAN
Meaning: Indicates whether the external UTRAN cell supports single radio voice call continuity (SRVCC) for both CS and PS services. If this parameter is set to BOOLEAN_FALSE(False), the external UTRAN cell does not support SRVCC for both CS and PS services.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)
GeranExternalCell
CsPsHOInd
ADD GERANEXTERNALCELL
MOD GERANEXTERNALCELL
LST GERANEXTERNALCELL
LOFD-001020 / TDLOFD-001020
LOFD-001046 / TDLOFD-001046
PS Inter-RAT Mobility between E-UTRAN and GERAN
Service based inter-RAT handover to GERAN
Meaning: Indicates whether the external GERAN cell supports single radio voice call continuity (SRVCC) for both CS and PS services. If this parameter is set to BOOLEAN_FALSE(False), the external GERAN cell does not support SRVCC for both CS and PS services.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

7 Counters

There are no specific counters associated with this feature.

Budi Prasetyo

About Budi Prasetyo

All About LTE

Subscribe to this Blog via Email :