VCC Domain Transfer Number

Description

The VCC Domain Transfer Number (VDN) is a critical identifier within the 3GPP Voice Call Continuity (VCC) architecture specified in Release 7. VCC enables seamless handover of a voice call between a circuit-switched network (like legacy GSM/UMTS CS) and a packet-switched IMS network (supporting VoIP). The VDN is a telephone number, typically an E.164 number, assigned to the VCC Application in the IMS network. It serves as a stable routing point or anchor for the call during the transfer process between domains.

How it works: When a VCC-capable UE is engaged in a voice call and needs to transfer the call from the CS domain to the IMS domain (or vice versa), the network initiates a domain transfer procedure. The VDN is used as the target address in this procedure. For example, when transferring from CS to IMS, the CS leg of the call is redirected (e.g., via a GSM Supplementary Service like Explicit Call Transfer) to the VDN. This call to the VDN is routed to the VCC Application in IMS. The VCC Application, recognizing the VDN and correlating it with the ongoing call context, connects the incoming CS leg to the existing IMS leg, completing the transfer. The VDN essentially provides a well-known, static contact point in the IMS for the CS network to 'hand off' the call.

Key components involved include the VCC Application (a SIP Application Server in the IMS), the UE with VCC capabilities, and the CS core network (MSC). The VDN is configured in the VCC Application and is known to the UE's VCC logic. Its role is purely for network control and routing during the transfer; it is not dialed by the end-user. The specifications define how the VDN is provisioned, how it is used in signaling (e.g., in SIP INVITE messages or ISUP signaling), and its management as part of the subscriber's VCC service data.

Purpose & Motivation

The VCC Domain Transfer Number was created to solve the technical challenge of seamlessly transferring an active voice call between two fundamentally different network domains: the circuit-switched (CS) domain and the IP Multimedia Subsystem (IMS) packet-switched domain. This capability was essential for the initial deployment of IMS-based Voice over IP (VoIP) services, as it allowed operators to offer voice continuity when a user moved between areas of IMS coverage (e.g., Wi-Fi or early LTE) and legacy CS coverage (2G/3G).

Without a mechanism like VDN, transferring a call would require complex and non-transparent methods, such as putting one leg on hold and establishing a new call, leading to interruptions, delays, and potential call drops. The VDN provides a standardized, network-controlled anchor point. It solves the routing problem by giving the CS network a specific number to call to 'find' the IMS-based call session, enabling the network to merge the two legs seamlessly from the user's perspective.

Historically, VCC and the VDN were pivotal in Release 7 as part of the Fixed Mobile Convergence (FMC) and early VoLTE preparation efforts. They addressed the transition period where both CS and IMS voice coexisted. The VDN enabled a smooth user experience for dual-mode phones, encouraging adoption of IMS services. While later superseded by Single Radio Voice Call Continuity (SRVCC) for LTE-to-3G/2G handovers, which uses different mechanisms, the VDN concept was foundational in demonstrating controlled domain transfer within 3GPP architectures.

Key Features

• E.164 number serving as a static routing anchor for the VCC Application in IMS
• Used as the target address for call redirection during CS-to-IMS or IMS-to-CS domain transfer
• Enables network-controlled, seamless call continuity without user intervention
• Configured as part of subscriber service data in the VCC Application
• Utilized in both CS signaling (e.g., ISUP) and IMS signaling (SIP) during transfer
• Critical for correlating the CS leg and IMS leg of the same end-to-end call

Evolution Across Releases

Defining Specifications