Description
Dual Radio Voice Call Continuity (DRVCC) is a mobility solution standardized by 3GPP to ensure uninterrupted voice service when a User Equipment (UE) moves between a 3GPP Packet Switched (PS) network (such as LTE) and a non-3GPP Circuit Switched (CS) network (such as CDMA 1xRTT). Unlike Single Radio Voice Call Continuity (SRVCC), which requires the UE to have a single radio transceiver capable of switching between access technologies, DRVCC is designed for UEs equipped with two independent radio transceivers. This architecture allows one radio to maintain the active voice call on the CS network while the other radio manages the PS data session on the LTE network. The handover process is coordinated by the network, specifically involving the Mobility Management Entity (MME) in the Evolved Packet Core (EPC) and the Interworking Function (IWF) that interfaces with the legacy CS network.
The core technical procedure involves a handover preparation phase triggered when the UE, connected to an LTE network for a Voice over LTE (VoLTE) call, detects that it is moving out of LTE coverage and into a legacy CDMA coverage area. The UE reports these measurements to the eNodeB, which forwards the information to the MME. The MME, recognizing the UE's DRVCC capability, initiates a session transfer procedure towards the IMS network via the Sv interface to the MSC Server enhanced for SRVCC (eMSC). The key difference in DRVCC is that the UE itself uses its second radio to establish a new CS call leg directly with the target CDMA network, in parallel with the ongoing PS bearer in LTE. The network then coordinates the switching of the media path in the IMS core from the PS access leg to the newly established CS access leg, completing the handover.
DRVCC's role is critical in early VoLTE deployments, particularly in regions where LTE coverage was not ubiquitous and operators relied on CDMA 1x networks as a fallback for voice. It provides a standardized, network-controlled handover mechanism that maintains the voice call's quality and continuity without requiring the UE to drop the PS data session. The solution is defined across multiple 3GPP specifications covering stage 1 requirements, stage 2 architecture, and stage 3 protocols for the core network and UE behavior, ensuring interoperability between multi-radio devices and heterogeneous network infrastructures.
Purpose & Motivation
DRVCC was created to solve the critical problem of voice call continuity for multi-radio devices in early 4G LTE deployments. As operators began rolling out LTE networks optimized for high-speed data (PS), voice service initially relied on Circuit Switched Fallback (CSFB) to legacy 2G/3G networks or the eventual deployment of VoLTE over IMS. However, in markets dominated by CDMA technology (which lacks a native CS core compatible with GSM/UMTS), a specific interworking solution was needed for UEs capable of VoLTE. The primary motivation was to enable a seamless user experience where a voice call started on VoLTE could be handed over to the ubiquitous CDMA 1x network as the user moved out of LTE coverage, without dropping the call.
This addressed a significant limitation of the earlier SRVCC solution, which was designed for UEs with a single radio that could only operate on one access technology at a time. Many early LTE smartphones, especially in North America, were equipped with separate LTE and CDMA radios to support simultaneous voice and data. DRVCC provided the standardized network procedures to leverage this dual-radio hardware for seamless mobility. It solved the business and technical challenge of launching VoLTE services without a fully built-out LTE coverage layer, allowing operators to offer high-definition voice on LTE where available while guaranteeing reliability through a robust CDMA fallback, thereby accelerating VoLTE adoption.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-12, normative work from Rel-15.
In Release 15, the enhancement for DRVCC introduced support for the transfer of an IMS emergency session from the PS to the CS domain specifically during the early dialogue phase. This is detailed alongside SRVCC procedures in the specification for IMS emergency session continuity. The update ensures emergency session continuity is maintained when a call needs to be handed over from a packet-switched to a circuit-switched access.
- PS to CS SRVCC for IMS emergency session in early dialogue phase TS 23.237CR0504
In Release 16, the enhancements for DRVCC primarily focused on extending SRVCC procedures to support 5G systems and emergency calls. Specifically, this included the introduction of 5G-SRVCC for call establishment and the derivation of associated security keys (CK and IK). Furthermore, the release enabled SRVCC for emergency calls transferred to EPS and introduced support for multiple EATF instances within emergency SRVCC procedures.
- Introduction of support of multiple EATF instances in Emergency SRVCC procedures TS 23.237CR0509
- CK and IK derivation for 5G-SRVCC TS 24.008CR3200
- Call establishment for 5G-SRVCC TS 24.008CR3201
- Completing introducing of 5G SRVCC TS 23.237CR0510
- Enabling SRVCC for emergency call transferred to EPS TS 23.237CR0512
In Release 17, the DRVCC function received specific clarifications and corrections. These included a clarification on the use of the voice domain preference information element for domain selection during emergency session attempts. Additionally, a correction was made regarding the call state to be chosen following a b-SRVCC call transfer procedure.
Explore further
Broader topics and technologies where DRVCC plays a role.
Defining Specifications
3GPP specifications that define or reference DRVCC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.167 vj11 | IMS Emergency Sessions | Rel-19 |
| TS 23.237 vj00 | IMS Service Continuity (ISC) Stage 2 | Rel-19 |
| TS 24.008 vj50 | 3GPP TS 24008: Core Network Protocols | Rel-19 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 |
| TS 29.165 vj10 | Inter-IMS Network to Network Interface (NNI) | Rel-19 |