Voice Call Continuity

Description

Voice Call Continuity (VCC) is a standardized service defined by 3GPP to support the continuity of voice calls when a user equipment (UE) moves between circuit-switched (CS) domains (e.g., traditional cellular networks using GSM or UMTS) and packet-switched (PS) domains (e.g., IMS-based networks over LTE, Wi-Fi, or fixed broadband). The core functionality involves transferring an ongoing voice call from one domain to another without dropping the call, providing a seamless experience. Architecturally, VCC relies on the IMS core for control and utilizes specific functional entities: the VCC Application Server (VCC AS) acts as the anchor point for the call, managing domain selection and handover logic; the CS Adaptation Function (CSAF) facilitates interaction with legacy CS networks; and the UE includes VCC capabilities to assist in domain detection and handover procedures. The service is specified across multiple 3GPP releases, with detailed protocols in specs like 23.206 and 24.206.

How VCC works involves several phases: call origination, domain selection, and handover execution. Initially, when a UE places or receives a call, the VCC AS determines the optimal domain (CS or PS) based on factors like network availability, user preferences, and service policies. The call is anchored at the VCC AS, meaning all media and signaling pass through it. During an active call, if the UE detects that a better domain is available (e.g., moving from Wi-Fi to cellular coverage), it initiates a handover. For a CS-to-PS handover, the UE establishes a PS leg to the VCC AS while maintaining the CS leg; the VCC AS then bridges the media and switches the remote party to the new leg before releasing the old one. Conversely, for PS-to-CS handover, a CS leg is set up. Key protocols involved include SIP for IMS signaling, ISUP/BICC for CS signaling, and RTP for media transport, with enhancements for synchronization to minimize audio gaps.

The role of VCC in the network is to bridge the gap between legacy CS voice services and emerging all-IP networks, facilitating the transition to IMS-based voice solutions like VoLTE. It ensures service continuity during mobility, which is critical for user acceptance of new access technologies. VCC also supports features like dual radio operation (where the UE can communicate simultaneously over CS and PS) and single radio operation (where the UE switches radios, requiring faster handovers). By decoupling the service from the access network, VCC enables operators to leverage heterogeneous networks (HetNets) and offload traffic to Wi-Fi, improving capacity and coverage while maintaining voice quality. Its implementation involves tight integration with IMS enablers such as the Service Centralization and Continuity (SCC) AS, which evolved from VCC concepts in later releases to support richer multimedia continuity.

Purpose & Motivation

Voice Call Continuity (VCC) was created to address the challenge of maintaining voice service continuity as mobile networks evolved from circuit-switched to packet-switched architectures. With the introduction of IMS and all-IP networks like LTE, operators faced the problem of voice calls dropping when users moved between CS coverage (e.g., 2G/3G) and PS coverage (e.g., LTE or Wi-Fi). This was a significant barrier to adopting new technologies, as users expected reliable voice service. VCC, introduced in 3GPP Release 7, solved this by providing a standardized mechanism for seamless handovers between domains, ensuring that voice—a critical service—remained uninterrupted during transitions.

The historical context for VCC includes the early deployments of IMS and the need for convergence between fixed and mobile networks. Prior to VCC, proprietary solutions existed, but they lacked interoperability and scalability. VCC standardized the procedures, enabling multi-vendor deployments and reducing complexity for operators. It also addressed the limitations of previous approaches like Voice over IP (VoIP) over Wi-Fi, which often suffered from handover delays or failures when leaving Wi-Fi coverage. By anchoring calls in the IMS core, VCC provided a network-controlled handover that could leverage both CS and PS resources, improving reliability and user experience.

Motivated by the drive towards network convergence and the eventual sunset of CS networks, VCC facilitated the migration to all-IP services. It allowed operators to introduce IMS-based voice gradually, while still relying on CS for coverage in areas where PS networks were underdeveloped. This reduced rollout costs and risks. Over releases, VCC concepts evolved into broader continuity solutions, such as Single Radio Voice Call Continuity (SRVCC) for LTE-to-3G handovers and enhanced VCC for multimedia services. The purpose of VCC thus extends beyond immediate handover—it underpins the long-term strategy for unified communications, enabling operators to deliver consistent voice quality across diverse access technologies and paving the way for advanced services like VoLTE and VoWi-Fi.

Key Features

• Seamless handover of active voice calls between CS and PS domains
• IMS-based anchoring via VCC Application Server for call control
• Support for both dual radio and single radio operation modes
• Domain selection based on network conditions and policies
• Integration with legacy CS networks through adaptation functions
• Minimized audio gaps and interruptions during handover

Evolution Across Releases

Defining Specifications