Single Radio Voice Call Continuity

Description

Single Radio Voice Call Continuity is a mobility and service continuity feature defined for handsets with a single radio transceiver. Its primary function is to manage the handover of an ongoing voice call from an IP Multimedia Subsystem (IMS)-based voice service (like Voice over LTE - VoLTE) in a packet-switched (PS) domain to a circuit-switched (CS) voice service in a 2G (GERAN) or 3G (UTRAN) network. The architecture involves close interaction between the Evolved Packet Core (EPC), the IMS core, and the legacy CS core network (MSC). Key network elements include the MME (Mobility Management Entity), MSC Server enhanced with Sv interface functionality (known as the MSC Server enhanced for SR-VCC), and the IMS Application Server (e.g., Service Centralization and Continuity Application Server - SCC AS).

The SR-VCC procedure is network-initiated and triggered based on measurement reports from the User Equipment (UE). When a UE engaged in a VoLTE call moves towards the edge of LTE coverage, it sends measurement reports indicating stronger 2G/3G signals. The LTE base station (eNodeB) forwards this to the MME. The MME, recognizing the voice bearer, initiates the SR-VCC procedure by sending a handover request via the Sv interface to the MSC Server. The MSC Server then coordinates with the target 2G/3G radio network and the CS core to prepare resources. Crucially, the MSC Server also interacts with the IMS SCC AS to perform session transfer, anchoring the call leg from the remote party to the CS network. From the UE perspective, it receives a handover command from LTE to the 2G/3G cell and re-tunes its single radio to the new frequency, where the CS voice call is already established.

SR-VCC's role is as a critical interoperability and fallback mechanism during the transition period where LTE coverage was not ubiquitous. It protects the user experience for voice, which is considered a critical service, by leveraging the extensive coverage of legacy CS networks. The procedure handles not only the radio access transfer but also the seamless transfer of the call control and media path at the IMS service layer, ensuring the call is not dropped. Specifications like TS 23.216 and TS 24.237 provide the stage 2 and stage 3 protocol details for this inter-system handover.

Purpose & Motivation

SR-VCC was created to solve a specific deployment challenge for LTE networks: how to provide reliable, ubiquitous voice service from day one, even though LTE was designed as an all-IP, packet-only network without a native circuit-switched voice domain. In early LTE deployments, coverage was limited to urban areas, while 2G and 3G networks provided near-nationwide coverage for voice. Without SR-VCC, a VoLTE call would simply drop when the user left LTE coverage, leading to a poor user experience and making VoLTE commercially unviable as a primary voice service.

The historical context is the transition from CS-based voice in 2G/3G to IP-based voice (VoIP) in 4G. Operators needed a solution that allowed them to launch LTE for high-speed data while relying on their existing CS network for voice coverage, with a smooth path to migrate voice to VoLTE over time. SR-VCC provided that bridge. It addressed the limitation of earlier voice continuity solutions like VCC (defined for 3G), which were designed for dual-radio devices and did not efficiently handle the single-radio constraint of modern smartphones.

SR-VCC's purpose was to enable the commercial launch of IMS-based voice over LTE by guaranteeing continuity, thereby accelerating LTE adoption for data and voice. It gave operators confidence to deploy VoLTE, knowing they could leverage their legacy network as a fallback. This was a crucial step in the evolution towards all-IP networks and ultimately helped pave the way for pure VoLTE/VoNR coverage as LTE networks expanded, and for the eventual sunset of legacy CS networks.

Key Features

• Seamless handover of IMS voice calls from LTE PS to 2G/3G CS domain
• Designed for User Equipment with a single radio transceiver
• Involves coordination between MME, MSC Server, and IMS SCC AS
• Uses the Sv interface between MME and MSC
• Maintains voice call continuity during inter-RAT mobility
• Critical for early VoLTE deployment and coverage extension

Evolution Across Releases

Defining Specifications