Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Rev. A 09/13
Single Radio Voice Call Continuity (SRVCC) Testing
Using Spirent CS8 Interactive Tester
Table of Contents
Executive Summary 4
SRVCC Technology Overview 5
Spirent Solutions Overview For SRVCC Testing 7
CS8 Mobile Device Tester 7
CS8 Interactive Tester 7
System Architecture 8
SRVCC Mobility Using CS8 Interactive Tester 9
Step 1: Select Appropriate Test Configuration & Network View 9
Step 2: Configure Appropriate Downlink Configuration & PDN-GW Settings 10
Step 3: Enable SRVCC In MME Test Configuration Setting 11
Step 4: Connect To Instruments/Load IMS Message Flow/Enable Call Processing 11
Step 5: Initiate Mobile Originated VoLTE Call 14
Step 6: Initiate SRVCC Procedure 16
Conclusion 19
Acronyms 20
References 21
Table of Figures 22
Single Radio Voice Call Continuity (SRVCC) Testing Using Spirent CS8 Interactive Tester
1. Executive Summary
Voice continues to be a viable source of revenue for Network Operators. Consumers have
been accustomed to assured Quality of Service (QoS) standards while using voice services on
their mobile devices. According to Infonetics Research, an international market research and
consulting firm, voice will continue to comprise 60 percent of the mobile services market by
2014, signifying $522 billion in global mobile revenues (Figure 1).
As LTE networks are continuing to be deployed alongside legacy networks such as GERAN/
UTRAN/1xRTT, the ability for multimode 3G/LTE mobile devices to connect to different network
technologies will be an important part of providing the best possible mobile voice and data
experience to customers. However, adoption of LTE and its all-Internet Protocol (IP) Radio Access
Network (RAN) has produced one of the key challenges of LTE deployment: delivery of voice
services in an all-IP network.
Three approaches were decided by the wireless industry to overcome these challenges:
VoLTE (Voice Over LTE)
CSFB (Circuit Switched Fallback)
SVLTE (Simultaneous Voice and LTE)
Unlike CSFB, VoLTE allows call continuity. With cost, size, and battery efficiency advantages
over dual radio solutions such as SVLTE, the industry is standardizing on VoLTE for the future.
VoLTE is based on the IP Multimedia Subsystem (IMS) network, with voice services being
delivered as data flows within the LTE data bearer. As a result, Single Radio Voice Call Continuity
(SRVCC) is required in order to execute a seamless handover of a voice call from an LTE network
to a 3G network and provide continuity for traditional circuit-switched networks.
This application note provides an overview of the SRVCC technology and outlines SRVCC
mobility testing using Spirent solutions. Since SRVCC implementation introduces a number of
challenges to development and test teams its testing is as important as ever.
The UE, LTE Network, and Target Legacy Networks should all support SRVCC. In addition, a
special interface known as Sv is formed between MME and MSC Server. The Sv interface is
an interface between the Mobility Management Entity (MME) or Serving GPRS Support Node
(SGSN) and 3GPP MSC server enhanced for SRVCC. The Sv interface is used to support Inter-RAT
handover from VoIP/IMS over EPS to CS domain over 3GPP UTRAN/GERAN access. To support
SRVCC the IMS network should also include application server called SCC-AS. The SCC (Service
Centralization and Continuity) AS is responsible for handling the signalling required for the
process (Figure 2).
As the UE moves away from the LTE coverage area, LTE Reference Signal Transmit Power (RSTP)
starts diminishing. The UE then notifies eNodeB about the change in the signal strength and
SRVCC handover is initiated. The LTE network determines that the active voice call needs to
be moved from the packet to the circuit domain. MME then receives the handover request
from E-UTRAN with the indication that it is for SRVCC handling, and it then triggers the SRVCC
procedure with the MSC Server via the Sv reference point.
A new voice call request is sent to the IMS using a special number known as STN-SR. STN-SR
is a unique number that is generated for each UE and is stored in the HSS. This number is sent
to the MME by the HSS when the UE first contacts with the network. Receiving STN-SR number
indicates to the SCC-AS that the corresponding call needs to be routed to a different network,
and it starts the redirection process to the legacy endpoint.
MME starts the handover of non-voice PS bearer during SRVCC procedure based on the
information received from E-UTRAN. The handover of non-voice PS bearer(s) is done according
to Inter-RAT handover procedure as defined in 3GPP Technical Specification 23.401. After the
resource preparation is completed, MME confirms the handover request provided earlier by the
eNodeB (Figure 3).
The eNodeB then transmits the confirmation to the UE and provides the required information
about the target network. When the mobile is detected in the legacy network, it switches its
internal voice processing from VoLTE to legacy-circuit voice and the call is re-established.
3GPP Performance Requirements mandate the measured Voice Interruption Time to be within
the 3GPP target of less than 0.3 seconds. Voice Interruption Time is the time between last voice
packet on LTE and first on CS domain and is measurable through Inter-RAT handover delay. With
legacy voice call retention rates typically higher than 98%, SRVCC handover is targeted to be
successful more than 99% of the time. These established QoS standards target less than 0.3
seconds Voice Interruption Time and call drop rates and handover failure rates of less than
one percent.
Network View and Test Configuration panels are used to configure network topologies. These
panels are used to configure both the Evolved Packet Core (EPC) and the Evolved UMTS
Terrestrial Radio Access Network (eUTRAN). For instance, PDN-GW, HSS, MME/SGW, and eNodeB
are all configured from within these panels.
The Test Results panel provides diagnostic interpretation of test progress and outputs real-
time interactive message exchange between network and DUT. It also logs the NAS/AS state
transitions, EPC status, and system control information.
The Message Analyzer panel displays a real-time log of all RRC/NAS messaging between
the network and the Device Under Test (DUT). The left side of the panel lists the message
sequences, while the right side shows the ASN.1-based contents for each message.
Spirent CS8 Mobile Device Tester coupled with the CS8 Interactive Tester provides emulation of
all network components and is able to handle testing requirements for SRVCC capable devices
including mobility scenarios.
Click on the Network View dropdown list from the CS8 Interactive Tester User Interface to
select from combinations of different technologies. Selecting a network topology brings
up the network components as well as configuration options for those components. Each
icon represents a network entity. Select appropriate Test Configuration based on the testing
requirement by choosing the applicable network from the Network View pane. In this example,
SRVCC from E-UTRAN to UTRAN is intended to be tested, therefore LTE, one UTRAN network
topology needs to be selected (Figure 9).
The network components for both E-UTRAN and UTRAN networks are emulated and controlled
by CS8 Interactive Tester User Interface. The Evolved Packet Core, including PDN-GW, HSS, MME,
and SGW, are all emulated by Spirents SR3620. Both EPC and E-UTRAN are controlled by a
single user interface, providing unified control and a complete emulation of the LTE network.
At this stage IMS Message Flow script (DMF file) needs to be loaded. IMS Message Flow script
is targeted for testing of IMS Applications. To load the file from CS8 Interactive Tester software
navigate to (Figure 14):
This will open the LoadIMSMsgFlow window. In this window, ensure P-CSCF #1 is selected and
click on Open File (Figure 15) to browse to the IMS Message Flow script (DMF file) located in:
This folder contains pre-defined IMS Message Flow scripts. Select one of already configured
SRVCC IMS Message Flow files. In this example, a VoLTE Mobile Originated (MO) call will be
initiated. Therefore SRVCC_verified_MO_main script is selected (Figure 16):
The eNodeB is now ready to transmit signals and the EPC is waiting for the DUT to attach. To
enable call processing, click the Enable Call Processing button (Figure 16).
Check to see if the connection to instruments succeeded, IMS Message Flow script is loaded,
and call processing is enabled (Figure 18).
Ensure UE successfully attaches to the LTE network and IMS Registration is successful by
monitoring following messages in Test Results panel (Figure 19):
Use the VoLTE Application on the DUT to initiate a VoLTE MO call. Monitor the Test Results panel
for real-time SIP messages sent and received to confirm the call is active and MO VoLTE Call is
established (Figure 20):
SIP Message is Received 180 Ring
SIP Message is Sent PRACK
SIP Message is Received 200 OK
In the Handover Command window, ensure Handover to UTRAN box is checked and correct Cell
ID is selected from the drop down menu (Figure 22).
The CS8 Interactive Tester then determines that the active voice call needs to be moved from
the packet to the circuit domain. Inter-RAT handover from LTE to UTRAN is initiated. As CS + PS
SRVCC type was selected prior to the test in MME, CS + PS type is observed in the handover
message (Figure 23).
Monitor real-time messages in Test Results panel to determine if the Inter-RAT handover from
LTE to UTRAN is successful and both CS and PS calls are established on UTRAN. Content of
handover success message indicates the SRVCC type and its status. If the SRVCC procedure fails
due to call drop or handover failure, the Test Result panel will highlight it through its real-time
logging. By analyzing the logs, it can be concluded that SRVCC procedure was successful and
both CS and PS calls were established on UTRAN (Figure 24).
Message Analyzer panel can also be examined for further investigation to measure the SRVCC
Key Performance Indicators (KPI). The left side of the panel lists the message sequences, while
the right side shows the ASN.1-based contents for each message. In this specific scenario
mobilityFromEUTRACommand message is viewed (Figure 25). It can be confirmed that the
Access Stratum Release 9 mobility from E-UTRAN to UTRAN was completed (Figure 26).
5. Conclusion
SRVCC is an extremely complicated technology. For an SRVCC call to function properly, key
factors such as MobilityForEUTRAN IEs, SRVCC Type, Carrier Frequency, and SIP Negotiation
need to be configured appropriately by the network elements. Spirents proven leadership
in Mobility and Channel Emulation in addition to expertise in VoLTE has made SRVCC testing
comprehensive and intuitive. As a result, testing cycles can be drastically decreased for the
users. As highlighted in this Application Note, SRVCC testing using CS8 Interactive Tester is
simply faster.
6. Acronyms
1xRTT 1x (Single-Carrier) Radio Transmission Technology
2G 2nd-Generation Wireless Telephone Technology
3G 3rd-Generation Wireless Telephone Technology
ASN.1 Abstract Syntax Notation One
CDMA Code Division Multiple Access
CS Circuit-Switched
CSFB Circuit-Switched Fallback
DMF Data Message Flow
DUT Device Under Test
E-HRPD Evolved High-Rate-Packet Data
E-UTRAN Evolved UMTS Terrestrial Radio Access Network
EARFCN EUTRA Absolute Radio Frequency Channel Number
ECM EPS Connection Management
EMM EPS Mobility Management
EPC Evolved Packet Core
EPS Evolved Packet System
EV-DO Evolution Data Optimized
FDD Frequency Division Multiplexing
GERAN GSM EDGE Radio Access Network
GSM Global System for Mobile Communications
HSPA High Speed Packet Access
HSS Home Subscriber Server
IMS IP Multimedia Subsystem
IP Internet Protocol
IRAT Inter-Radio Access Technology
LTE Long Term Evolution
MME Mobility Management Entity
MO Mobile Originated
MSC Mobile Switching Center
NAS Non-Access-Stratum
P-CSCF Proxy Call Session Control Function
PDN Packet Data Network
PDN-GW Packet Data Network Gateway
PS Packet-Switched
QoS Quality of Service
RACH Random Access Channel
RAN Radio-Access Network
RAT Radio-Access Technology
RRC Radio Resource Control
RSTP Reference Signal Transmit Power
SCC-AS Service Centralization and Continuity Application
SGSN Serving GPRS Support Node
SGW Serving Gateway
SIP Session Initiation Protocol
SRVCC Single Radio Voice Call Continuity
STN-SR Session Transfer Number for SRVCC
UE User Equipment
UTRAN UMTS Terrestrial Radio Access Network
VoIP Voice over IP
VoLTE Voice over LTE
WCDMA Wideband Code Division Multiple Access
7. References
1. 3GPP TS.23.216 V11.9.0 (2013-06): Single Radio Voice Call Continuity (SRVCC)
2. 3GPP TS 129 280 V8.3.0 (2010-01): Sv interface (MME to MSC, and SGSN to MSC) for SRVCC
3. 3GPP TS 22.278 V11.6.0 (2012-09): Service Requirements for the Evolved Packet System
4. 3GPP TS 23.401 V10.7.0 (2012-03): GPRS enhancements for E-UTRAN access (Release 10)
5. GSMA, 2010, IR.92 IMS Profile for Voice and SMS V3.0
6. GSMA, 2011, IR.94 IMS Profile for Conversational Video Service V1.0
7. GSMA, 2011, IR.64 IMS Service Centralization and Continuity Guidelines V2.0
8. Vittal, Shwetha. Single Radio Voice Call Continuity (SRVCC) with LTE. Radisys Corporation.
September 2011
9. QUALCOMM. (October 2012) VoLTE with SRVCC: The second phase of voice evolution for
mobile LTE devices [White Paper]. Retrieved from www.qualcomm.com/media/documents/files/
srvcc-white-paper.pdf
10. QUALCOMM. Qualcomm Chipset Powers First Successful VoIP-over-LTE Call with
Single Radio Voice Call Continuity. Retrieved from http://www.qualcomm.com/media/
releases/2012/02/02/qualcomm-chipset-powers-first-successful-voip-over-lte-call-single-radio
11. CISCO. Voice over Long Term Evolution Migration Strategies [White Paper]. Retrieved from
http://www.cisco.com/en/US/solutions/collateral/ns341/ns973/white_paper_c11-711982.html
8. Table of Figures
Figure 1: Mobile Services Market Forecast For 2014....................................................... 4