Professional Documents
Culture Documents
USN9810 Product Documentation
Product Version: V900R013C00
Library Version: 01
Date: 04/25/2014
For any question, please contact us .
Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
WSFD110701 SRVCC
Contents
4.6.3.14.7.2.1 WSFD110701 SRVCC
4.6.3.14.7.2.1 WSFD110701 SRVCC
Applicable NEs
Definition
Benefits
Requirements
Impact on the System
Application Limitations
Interaction with Other Features
Application Scenario
Implementation Principles
Charging and CDR
Feature Specifications
Standards Compliance
Release History
Related Topics
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 1/9
2/27/2017 HEEX Startpage
Applicable NEs
MME
Definition
Single radio voice call continuity (SRVCC) ensures voice call continuity when a subscriber requires a
handover from Long Term Evolution (LTE) to global system for mobile communications/universal mobile
telecommunications system (GSM/UMTS). Huawei USN9810 and UGW9811 provide an SRVCC
solution, ensuring voice call continuity in a handover from LTE to GSM/UMTS.
Benefits
Table 1 Benefits of this feature
For... Benefits
Carriers This feature helps carriers to achieve voice call continuity in handovers from
LTE to GSM/UMTS, enhancing networking flexibility, reducing operation
expenditures, and increasing subscriber satisfaction.
Subscribers This feature ensures voice call continuity, improving quality of experience.
Requirements
NEs Involved
Table 2 NEs involved in this feature
UE eNodeB MME Gn/Gp S4 SGSN SGW/P MSC HSS IMS
SGSN GW
√ √ √ √ √ √ √
NOTE:
In Table 2, "√" indicates that the NE is required, and "" indicates that the NE is not required.
Table 3 NE functions
NE Function
UE Is SRVCCcapable.
Indicates its SRVCC capability.
eNodeB Is short for EUTRAN NodeB, which identifies subscribers and
forwards messages for radio access.
MME Receives handover requests from eNodeBs, and sends the
voice and data handover indications included in the handover
requests to the MSC.
Executes voice bearer switchover.
MSC Supports handover requests sent by the MME.
Supports handovers from PS to CS.
Anchors voice sessions on the IMS network.
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 2/9
2/27/2017 HEEX Startpage
NE Function
SGW/PGW Notifies the IP multimedia subsystem (IMS) of the removal of the
voice bearer from the SGW/PGW.
HSS Resolves and stores the SRVCC indicator (indicating that the MME
supports SRVCC) in Update Location Request (ULR) messages.
IMS Serves as an IMS handover anchor.
Supporting Versions
Table 4 USN9810 and UGW9811 versions that support this feature
Product Supporting Version
USN9810 V900R011C00 and later
UGW9811 V900R001C05 and later
License Requirement
This feature is optional for the USN9810, and the license control item is VoLTE Entry Feature.
This is an optional feature of the UGW9811; a license is required.
NOTE:
The license item VoLTE Entry Feature contains IMSbased VoLTE, SRVCC, and Shortest Path Prefer Based VoLTE.
Impact on the System
None
Application Limitations
Only packet switched (PS)tocircuit switched (CS) handovers are supported.
Only LTEtoGSM/UMTS handovers are supported.
Only voice service handovers are supported.
Only handovers in nonemergency sessions are supported.
Interaction with Other Features
WSFD1107081 IMSbased VoLTE must be enabled before this feature is enabled.
It is recommended that WSFD110122 Default MSC over SGs and Sv be enabled with this feature.
In this manner, the MME attempts to use the default location area identity (LAI) to resolve the
domain name of the default MSC if the resolution of the domain name of the target MSC fails in
the SRVCC procedure, which improves the service success rate.
Application Scenario
The SRVCC feature is mainly applied to hybrid networks. When a subscriber roams to a GSM/UMTS
network from an LTE network, this feature is used to ensure voice call continuity in a handover from LTE
to GSM/UMTS.
Implementation Principles
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 3/9
2/27/2017 HEEX Startpage
This section contains the following contents:
Related Concepts
System Implementation
Service Flow
Parameter Description
Related Concepts
SRVCC is performed through the Sv interface that is between the MME and the MSC. Figure 1 shows
the protocol stack used on the Sv interface.
Figure 1 Sv interface protocol stack
System Implementation
When a UE performing a voice service moves from the EUTRAN to the GERAN or UTRAN, the
MME uses the SRVCC solution to switch the voice service to the GERAN or UTRAN to ensure that the
voice service is not interrupted, as shown in Figure 2. Data services will resume in a later RAU or TAU
procedure without being switched.
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 4/9
2/27/2017 HEEX Startpage
Figure 2 SRVCC solution
Service Flow
The target network of an SRVCC procedure can be a GERAN or UTRAN. Based on the target
network type and UE capability, the SRVCC solution applies to the following scenarios:
Scenario 1: SRVCC from an EUTRAN to a GERAN, and DTM not supported
This scenario requires that the eNodeB be capable of determining that the UE or target
GERAN does not support DTM.
NOTE:
If both the UE and GERAN support DTM, the UE can perform voice and data services
simultaneously in the GERAN.
If either the UE or GERAN does not support DTM, the data service will be suspended when the
UE performs the voice service in the GERAN.
Scenario 2: SRVCC from an EUTRAN to a GERAN, DTM supported, but PS handover not
supported
This scenario requires that the eNodeB be capable of determining that the target GERAN
supports DTM but does not support PS handover and the UE supports DTM.
Scenario 3: SRVCC from an EUTRAN to a UTRAN, and PS handover not supported
This scenario requires that the eNodeB be capable of determining that the target UTRAN does
not support PS handover.
Scenario 1 is used as an example to describe the SRVCC procedure.
Scenario 1: SRVCC from an EUTRAN to a GERAN, and DTM not supported
Figure 3 shows the SRVCC procedure in scenario 1.
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 5/9
2/27/2017 HEEX Startpage
Figure 3 Procedure for SRVCC from an EUTRAN to a GERAN (DTM not supported)
1. The UE sends a measurement report to the eNodeB.
2. Based on the UE measurement report, the eNodeB decides to trigger an SRVCC procedure to the
GERAN.
3. The eNodeB sends a Handover Required message to the MME. The message contains IEs such as
Target ID, generic Source to Target Transparent Container, and SRVCC HO Indication. The Target ID
IE contains the LAI. The value of the SRVCC HO Indication IE is CS only, indicating that the GERAN
or UE does not support DTM and only a CSonly handover can be performed.
4. The MME separates the voice bearer (QCI = 1) from PS bearers based on the value of the SRVCC
HO Indication IE and QCIs of the bearers.
5. The MME selects the SRVCC MSC (the MSC server shown in Figure 3) based on the Target ID IE in
the Handover Required message and then sends a SRVCC PS to CS Request message to the MSC
server. The SRVCC PS to CS Request message contains information such as the IMSI, Target ID, STN
SR (handover number of the SRVCC session), CMSSIDN, and MM context (including the CS security
key). The STNSR and CMSISDN are obtained from the subscription data of the UE.
NOTE:
The domain name service (DNS) is used in the process of selecting the SRVCC MSC.
612. After receiving the SRVCC PS to CS Request message, the MSC server instructs the target MSC
to prepare CS radio bearer resources. Then, the MSC server initiates a Session Transfer procedure. The
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 6/9
2/27/2017 HEEX Startpage
IMS performs the Session Transfer procedure, notifies the peer end of the information about the local CS
access leg, and releases the local IMS access leg.
13. The MSC server sends a PS to CS Response message to the MME, informing the MME that that
CS radio bearer resources have been allocated.
14. The MME sends a Handover Command (Target to Source Transparent Container) message to the
eNodeB. The message contains only the voice information.
15. The eNodeB sends a Handover from EUTRAN Command message to the UE to instruct the UE to
start the handover.
16. The UE attempts to access the CS domain of the GERAN.
17. The target BSS detects that the UE has accessed the target cell. The UE sends an Handover
Complete message to the target MSC through the target BSS.
18. The UE cannot access the data service after the handover because the GERAN or UE does not
support DTM. The UE sends a Suspend message to the target BSS. The target BSS forwards the
Suspend message to the target SGSN. Then, the SGSN sends a Suspend Notification message to the
source MME, and the MME responds with a Suspend Acknowledge message.
1922. The target BSS sends a Handover Complete message to the target MSC, informing the target
MSC that the UE has been successfully handed over. The target MSC sends an SES (Handover
Complete) message to the MSC server. The MSC server sends a SRVCC PS to CS Complete
Notification message to the MME, informing the MME that the handover is complete.
22a. The MME initiates a Dedicated Bearer Deactivation procedure to deactivate the voice bearer and
other GBR bearers and suspends the nonGBR bearer.
23a23b. If the UE has not registered with the MSC server, the MSC server initiates a TMSI relocation
procedure for the UE and then initiates a MAP Update Location procedure to the HLR/HSS.
24. If an emergency call is handed over, both the MME and MSC server need to send a Subscriber
Location Report message containing the MSC server number to the GMLC.
Scenarios 2 and 3
The SRVCC procedures in scenarios 2 and 3 are different from the SRVCC procedure in scenario 1 as
follows:
The Suspend procedure is not involved, that is, 18 and 22a are absent.
In 22a, the MME deactivates only the voice bear.
Differences Between an Attach Procedure in the SRVCC Solution and a Normal Attach
Procedure
The Attach Request message sent by the UE carries the IE MS network capability. This IE
indicates whether the SRVCC function is supported.
The Update Location Response message sent from the HSS to the MME carries the IEs STN
SR and MSISDN. The MME saves the values of the IEs STRSN and MSISDN in EPS
contexts.
If the MME supports the SRVCC service, the Initial Context Setup Req from MME to E
UTRAN message sent by the MME carries "SRVCC is possible." This indicates that both the
UE and the MME support the SRVCC service.
The MME sends the HSS the Update Location Request message with the IE UESRVCC
Capability carrying the UE's SRVCC capabilities and the MME's Homogeneous Support of
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 7/9
2/27/2017 HEEX Startpage
IMS Voice Over PS Sessions capabilities (set by running SET IMSVOPS).
NOTE:
In TAU and service request procedures, the UE also carries the SRVCC flag to notify the MME that the UE supports
the SRVCC service.
Parameter Description
Table 5 Parameters
Category Parameter Command
SVMSGTYPE=Message Type
PSTOCSREQ=IE Type of SRVCC PS to CS
Request
STNSR=Coding Type
V2MSGCLS=MM
V2SMMMSGTYPE=SRVCC_PS_CS_REQ
T3RES=T3RESPONSE(s)
N3REQ=N3REQUEST(times)
Charging and CDR
None
Feature Specifications
None
Standards Compliance
This feature complies with the following standards:
3GPP TS 23.216 Single Radio Voice Call Continuity (SRVCC); Stage 2
3GPP TS 23.401 General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (EUTRAN) access
3GPP TS 23.402 Architecture enhancements for non3GPP accesses
3GPP TS 23.237 IP Multimedia Subsystem (IMS) Service Continuity; Stage 2
3GPP TS 24.237 IP Multimedia Subsystem (IMS) Service Continuity; Stage 3
3GPP TS 29.280 Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and
SGSN to MSC) for SRVCC
3GPP TS 29.292 Interworking between the IP Multimedia (IM) Core Network (CN)
subsystem and MSC Server for IMS Centralized Services (ICS)
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 8/9
2/27/2017 HEEX Startpage
3GPP TS 23.292 IP Multimedia Subsystem (IMS) centralized services; Stage 2
3GPP TS 24.292 IP Multimedia Subsystem (IMS) centralized services; Stage 3
3GPP TS 23.060 General Packet Radio Service (GPRS); Service description; Stage 2
3GPP TS 29.272 Mobility Management Entity (MME) and Serving GPRS Support Node
(SGSN) related interfaces based on Diameter protocol (Release 10)
Release History
Table 6 Release history and enhancement
Feature Version Product Version Details
Related Topics
Feature Deployment
Configuring the SRVCC Feature (WSFD110701)
Commands
Add GTPC V2 Compatibility (ADD GTPCV2CMPT)
Set Compatibility of Diameter Interface (SET DMCMPT)
Set GTPC T3/N3 Parameter (SET T3N3)
Alarms
None.
Performance Counters
117492512 S1 mode SRVCC request times
117492513 S1 mode SRVCC success times
Software Parameters
None.
Parent topic: WSFD1107082 VoLTE Extended Package
http://localhost:7890/printtopics.html?time=Mon%20Feb%2027%202017%2017:22:30%20GMT+0330%20(Iran%20Standard%20Time) 9/9