Description
Single Radio Voice Call Continuity (SRVCC) is a complex mobility procedure defined by 3GPP to maintain an active voice call when a User Equipment (UE) moves from a packet-switched (PS) LTE or 5G NR access network, which supports voice over IP (VoIP) via IMS (VoLTE/VoNR), to a legacy circuit-switched (CS) network like GERAN, UTRAN, or 1xRTT. The core challenge SRVCC addresses is that the UE has only a single radio transceiver, meaning it cannot simultaneously maintain the PS VoIP call on LTE and perform measurements or signaling on the target CS network. The procedure is orchestrated by the network, requiring tight coordination between the Evolved Packet Core (EPC) or 5G Core (5GC), the IMS, and the CS core network (MSC).
Architecturally, SRVCC introduces several key functional entities and reference points. In the EPC, the MME plays a central role. It receives measurement reports from the eNodeB indicating deteriorating LTE signal strength and the availability of a suitable CS target cell. The MME then initiates the SRVCC procedure by sending an SRVCC PS to CS Request message to the MSC Server (enhanced for SRVCC, often called an MSC Server enhanced for SRVCC or eMSC). This MSC Server interfaces with the IMS network via the Sv interface to the SRVCC Application Server (SRVCC AS) or the Service Centralization and Continuity Application Server (SCC AS) in the IMS. The SCC AS is the anchor point for the voice call session in IMS, enabling it to manipulate the media path.
During the handover execution, the MSC Server performs a CS handover procedure with the target BSS/RNS and establishes a CS bearer path. Concurrently, it signals the SCC AS via the Sv interface (or using ISUP/SIP interworking) to transfer the IMS leg of the call from the PS access to the newly established CS access. The SCC AS updates the remote end's media path to point to the CS network's Media Gateway (MGW). From the UE perspective, it receives a handover command from the LTE network, tunes its single radio to the target CS frequency/channel, and accesses the CS network, where it sends a handover complete message. The voice media is then seamlessly switched from the VoIP packet flow over LTE to the CS voice channel. For the calling party, this transition is nearly imperceptible, with only a very brief potential audio interruption.
SRVCC also encompasses variants like enhanced SRVCC (eSRVCC), introduced in 3GPP Release 10, which significantly reduces handover interruption time by anchoring the call locally in the serving network's MSC and IMS architecture, rather than involving the home network's SCC AS for the media update. Reverse SRVCC (rSRVCC) handles mobility from CS back to LTE/5G. In 5G systems, SRVCC principles are extended for handover from 5G NR (VoNR) to EPS (VoLTE) or to UTRAN/GERAN, with the AMF and N26 interface (when present) playing roles analogous to the MME and Sv interface.
Purpose & Motivation
SRVCC was created to solve a critical business and technical problem during the initial rollout of 4G LTE networks. LTE was designed as a pure packet-switched (PS) network, optimized for high-speed data, with no native circuit-switched (CS) domain for voice telephony. The industry's solution for voice over LTE was to use Voice over IP (VoIP) via the IP Multimedia Subsystem (IMS), known as VoLTE. However, LTE coverage was not ubiquitous at launch and often lagged behind the extensive 2G and 3G CS coverage. Without a continuity mechanism, a VoLTE call would simply drop when a user moved out of LTE coverage, leading to a poor user experience that was unacceptable for a primary telephony service.
The primary motivation was to enable mobile operators to deploy LTE as a data-optimized network while leveraging their existing, widespread CS networks for voice service continuity. This allowed for a phased migration strategy. Operators could launch LTE for high-speed data and VoLTE in dense urban areas, while relying on SRVCC to provide seamless voice service in suburban and rural areas still covered only by 2G/3G. It protected the operator's substantial investment in CS infrastructure and spectrum, while meeting customer expectations for reliable, uninterrupted voice calls.
Prior to SRVCC, dual-radio devices could use Circuit Switched Fallback (CSFB) to place or receive calls by temporarily falling back to a 2G/3G network, but this was not suitable for handover of an active call. SRVCC specifically addressed the active call continuity scenario for single-radio devices, which are the norm due to cost and complexity. It was a foundational enabler for the commercial success of VoLTE, as it guaranteed that the voice service quality and reliability on LTE would be at least as good as on legacy networks, thereby removing a major barrier to LTE adoption for voice.
What changed in its specifications
The latest release-to-release comparison of specifications that define SRVCC. Each summary describes the whole specification, not only this term.
Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.
Full comparison in TS 23.167 →Rel-19 brings only minor changes to TS 23.216: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.216 →Technology family
Voice service evolution · Services › IMS
- R96 CS voice
- Rel-8 1xCSFB, CSFB, ICS, SRVCC
- Rel-9 VoLTE
- Rel-10 SRVCC enhanced with ATCF
- Rel-11 CS to PS SRVCC, vSRVCC
- Rel-12 DRVCC
- Rel-15 Emergency Services Fallback, EPS fallback, VoNR
- Rel-16 5G-SRVCC
- SRVCC extended by vSRVCC
“Single Radio Video Call Continuity (vSRVCC): Video call continuity from E-UTRAN to UTRAN-CS for calls that are anchored in the IMS” TS 23.216
- SRVCC extended by 5G-SRVCC
“For 5G-SRVCC from NG-RAN to UTRAN, AMF first receives the handover request from NG-RAN with the indication that this is for 5G-SRVCC handling, and then AMF sends the forward relocation request with 5G-SRVCC HO Indication to MME_SRVCC together with STN-SR and C-MSISDN.” TS 23.216
- SRVCC extended by CS to PS SRVCC
“CS to PS Single Radio Voice Call Continuity (CS to PS SRVCC): SRVCC from UTRAN to E-UTRAN, and SRVCC from GERAN to UTRAN/E-UTRAN.” TS 23.216
- SRVCC coexists with DRVCC
“Emergency Session Transfer Number for DRVCC: A number used by the UE to request the EATF AS to perform Session Transfer from PS to CS access. The E-STN-DR is dynamically assigned by EATF during IMS emergency session procedure with WLAN.” TS 23.237
- SRVCC extended by SRVCC enhanced with ATCF
“When (5G-)SRVCC enhanced with ATCF is used, an Access Transfer Control Function (ATCF) and an Access Transfer Gateway (ATGW) may be used in the serving network (visited if roaming).” TS 23.237
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 11 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
SRVCC is specified for the first time: TS 23.216 defines the architecture for voice call continuity from E-UTRAN/UTRAN (HSPA) to UTRAN/GERAN CS, with IMS anchoring, an enhanced MSC Server and the Sv interface.
- “The present document specifies the architecture enhancements for Single Radio Voice Call Continuity (SRVCC) between E‑UTRAN access and 3GPP2's 1xCS” TS 23.216 v8.8.0
- “The Sv reference point provides SRVCC support between 3GPP E-UTRAN/UTRAN (HSPA) and 3GPP UTRAN/GERAN.” TS 23.216 v8.8.0
- “Voice call continuity between IMS over PS access and CS access for calls that are anchored in IMS” TS 23.216 v8.8.0
Rel-9 extends SRVCC with emergency session transfer (E-STN-SR, EATF), limited service mode support, SIP-interface MSC server procedures, and S3/S4/S16 Suspend/Resume signalling for SRVCC.
- “4.2.4 SRVCC for IMS emergency sessions” TS 23.216 v9.9.0
- “When an MSC server enhanced for SRVCC using SIP interface receives an indication for a session transfer” TS 24.237 v9.20.0
- “The Suspend Notification message shall be sent on the S3 interface by the SGSN to the MME” TS 29.274 v9.14.0
SRVCC was extended in Rel-10 with ATCF-enhanced SRVCC (ATCF management URI, SRVCC information sent to the ATCF) and new MSC selection and session-transfer error handling for SRVCC handover.
- “In order to provide the SRVCC related information to the ATCF, the SCC AS shall perform the role of an AS acting as originating UA” TS 24.237 v10.20.0
- “MME/SGSN may take that indication into account to prevent further SRVCC handover attempts.” TS 23.216 v10.6.0
- SRVCC Enhancements TS 29.328CR0340
Rel-11 extends SRVCC with CS to PS (reverse) SRVCC, ATCF-enhanced SRVCC anchoring and vSRVCC, with new MSC server, UE and Sv/GTP signalling behaviour.
- “CS to PS Single Radio Voice Call Continuity (CS to PS SRVCC): SRVCC from UTRAN to E-UTRAN, and SRVCC from GERAN to UTRAN/E-UTRAN.” TS 23.216 v11.11.0
- “The Sv reference point provides additionally SRVCC support from CS to PS.” TS 23.216 v11.11.0
- Introduction of SRVCC from CS to PS TS 23.216CR0235
Rel-12 extends SRVCC with return to E-UTRAN after SRVCC, SRVCC before ringing/pre-alerting, voice+video fallback, and CS to PS SRVCC procedures and signalling.
- “When configured to support the return to E-UTRAN after SRVCC, the MSC shall indicate this to GERAN/UTRAN during the release of an RR connection” TS 23.216 v12.4.0
- SRVCC before ringing (brSRVCC) TS 23.237CR0444
- “PS to CS SRVCC for originating calls in pre-alerting phase: feature enabling PS to CS SRVCC of a session with speech media component” TS 24.237 v12.14.0
SRVCC behaviour changed in Rel-13: SRVCC for IMS emergency sessions is possible regardless of HPLMN subscription, and the MME can update the eNodeB's 'SRVCC operation possible' indication.
- “SRVCC for IMS emergency session can be supported regardless of the subscription data from the HPLMN.” TS 23.216 v13.2.0
- “the MME shall immediately provide the updated "SRVCC operation possible" value in use to eNodeB by modifying an existing UE context.” TS 23.216 v13.2.0
- Updating SRVCC operation possible in E-UTRAN TS 23.216CR0332
SRVCC gained eCall over IMS support and optional MSC server enhancements: codec inquiry before and codec re-negotiation after PS to CS SRVCC access transfer, to minimise transcoding.
- “SRVCC is supported for handover of the voice channel of an eCall Over IMS from E-UTRAN/UTRAN (HSPA) to 3GPP UTRAN/GERAN.” TS 23.216 v14.0.0
- “In order to perform the codec inquiry prior to PS to CS SRVCC access transfer, the MSC server shall send a SIP OPTIONS request” TS 24.237 v14.7.0
- SRVCC transcoding minimization TS 23.237CR0496
Rel-15 extends SRVCC to PS-to-CS transfer of emergency sessions in early dialogue (alerting/pre-alerting) and terminating pre-alerting calls, adds 5GS-to-EPS SRVCC enabling, and SRVCC failure handling.
- “PS to CS SRVCC for terminating calls in pre-alerting phase: feature enabling PS to CS SRVCC of a session with speech media component” TS 24.237 v15.6.0
- “6c.2.2 SRVCC session transfer of an IMS emergency session in early dialogue phase for PS to CS” TS 23.237 v15.2.0
- PS to CS SRVCC for emergency session in alerting or pre-alerting phase TS 24.237CR1271
Rel-16 extends SRVCC to 5G: 5G-SRVCC from NG-RAN to UTRAN via AMF and MME_SRVCC over N26, with new SCC AS capability checks and ATCF handling.
- “For 5G-SRVCC from NG-RAN to UTRAN, AMF first receives the handover request from NG-RAN with the indication that this is for 5G-SRVCC handling” TS 23.216 v16.7.0
- Adding 5G SRVCC description to scope and definition to 23.216 TS 23.216CR0352
- “the UE 5G SRVCC Capability (see 3GPP TS 29.328 [6]) of the UE has value UE-5G-SRVCC-CAPABILITY-SUPPORTED;” TS 24.237 v16.4.0
SRVCC from NR to UTRAN gained failure-case handling, a (v)SRVCC rejected cause, SRVCC enabled after 5G-to-4G handover, and an NG-RAN session re-establishment indicator after cancelled handover.
- “the AMF shall attempt to have the MME-SRVCC trigger, at the MSC Server enhanced for SRVCC, handover cancellation procedures.” TS 23.216 v17.1.0
- “This IE shall be sent by the MME_SRVCC on the N26 interface during a 5G-SRVCC from NG-RAN to UTRAN handover” TS 29.274 v17.12.0
- SRVCC handover cancelled, IMS session re-establishment required indicator via NG-RAN TS 24.237CR1303
SRVCC behaviour was specified for IMS data channel sessions: during PS-CS SRVCC and vSRVCC, IMS data channel media is not transferred, and only associated voice/video may move to UTRAN.
- “IMS data channel media component(s) of session(s) are not getting transferred.” TS 24.237 v18.0.0
- “SRVCC is not applicable for IMS Data Channel. Only associated voice and/or video media may get transferred to UTRAN.” TS 23.216 v18.0.0
Defining Specifications
3GPP specifications that define or reference SRVCC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.167 vk10 | IMS Emergency Services | Rel-20 read |
| TS 23.216 vj00 | SRVCC Architecture Enhancements | Rel-19 read |
| TS 23.237 vj00 | IMS Service Continuity (ISC) Stage 2 | Rel-19 read |
| TS 23.272 vk00 | CS Fallback and SMS over SGs | Rel-20 read |
| TS 23.334 vj00 | IMS-ALG to IMS-AGW Interface (Iq) Stage 2 | Rel-19 read |
| TS 23.885 vb00 | Reverse SRVCC Feasibility Study | Rel-11 read |
| TS 23.886 va00 | Video SRVCC Feasibility Study | Rel-10 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.237 vj00 | IMS Service Continuity Protocol Details | Rel-19 read |
| TS 24.802 vc10 | II-NNI Traversal Scenario Determination | Rel-12 read |
| TS 25.300 vj00 | UTRA Radio Interface Enhancements Overview | Rel-19 read |
| TS 25.306 vj00 | UE Radio Access Capabilities Specification | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 26.114 vk11 | IMS Multimedia Telephony Client | Rel-20 read |
| TR 26.919 vj00 | Study on 5G Conversational Media Handling | Rel-19 read |
| TR 26.954 vj00 | UE Headset Electrical Interface Testing | Rel-19 read |
| TS 29.165 vk00 | Inter-IMS Network-to-Network Interface (II-NNI) | Rel-20 read |
| TS 29.238 vj00 | H.248 Profile for IBCF-TrGW Interface | Rel-19 read |
| TS 29.277 vj00 | S102 Interface Protocol Specification | Rel-19 read |
| TS 29.334 vj00 | IMS-ALG to IMS-AGW Interface Protocol | Rel-19 read |
| TS 29.806 vc10 | P-CSCF Restoration Analysis & Solutions | Rel-12 read |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 read |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 read |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.838 vb00 | PUCI High-Level Solution Study | Rel-11 read |
| TS 33.856 vg10 | Security for 5G to 3G Voice Continuity | Rel-16 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 25.331 vj01 | UTRAN Radio Resource Control Protocol | Rel-19 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |