CDIV

Communication DIVersion

Services
Introduced in Rel-7
A suite of supplementary services allowing a user to divert incoming communication sessions (calls, messages) based on configurable rules. It enables flexible call handling, improving user availability and network efficiency by redirecting sessions to alternative destinations like voicemail or other numbers.

Description

Communication DIVersion (CDIV) is a standardized set of supplementary services within the 3GPP IP Multimedia Subsystem (IMS) framework that provides dynamic control over the routing of incoming communication sessions. These sessions primarily include voice calls but can extend to other multimedia sessions like video calls and messaging, depending on the service configuration. The core principle involves intercepting an incoming session request (e.g., a SIP INVITE) at a network control point—typically the Serving-Call Session Control Function (S-CSCF) in the IMS core—and applying user-defined logic to determine whether to complete the call to the original destination or divert it elsewhere. This logic is executed by an Application Server (AS) hosting the CDIV service logic, which queries subscriber data and rules stored in the Home Subscriber Server (HSS) or a dedicated service profile repository.

The service operates based on a comprehensive set of diversion criteria and conditions defined in 3GPP specifications. Key diversion triggers include Busy (when the user's line is engaged), No Reply (when the user does not answer within a configurable time), Not Reachable (when the user's device is detached from the network or in a radio shadow area), and Unconditional (diverting all incoming sessions regardless of state). Additionally, more advanced conditions like diversion on user-not-logged-in or based on the calling party's identity (e.g., specific numbers or anonymous calls) can be configured. When a trigger condition is met, the CDIV AS instructs the S-CSCF to reroute the session signaling to a new destination address, which could be another telephone number, a voicemail server, or an instant messaging inbox. This rerouting is performed using standard SIP redirection responses (e.g., 302 Moved Temporarily) or by the AS acting as a back-to-back user agent (B2BUA) to establish a new leg to the diversion target.

Architecturally, CDIV is deeply integrated with the IMS service delivery platform. The initial Filter Criteria (iFC) in the user's service profile, downloaded from the HSS to the S-CSCF during registration, ensure that all relevant session initiation requests are forwarded to the designated CDIV Application Server for processing. The service logic on the AS evaluates the subscriber's active diversion settings, which the user can typically manage via Ut interface (XCAP) for self-provisioning or through operator-administered profiles. CDIV plays a critical role in the IMS service layer by decoupling the user's public identity (the dialed number) from the actual endpoint, enabling rich personal mobility and service personalization. Its implementation must also handle interactions with other supplementary services like Communication Waiting (CW) and Communication Hold (HOLD), following standardized precedence rules to avoid conflicts, and ensure proper charging records (CDRs) are generated for both the original and diverted call legs.

Purpose & Motivation

CDIV was created to provide a standardized, network-based call diversion capability for IP-based multimedia services, addressing the limitations of legacy circuit-switched diversion services and enabling seamless service continuity in the evolving IMS architecture. Prior to IMS, diversion features like Call Forwarding were implemented in circuit-switched mobile networks (GSM) and fixed networks, but these were often proprietary, limited in scope, and difficult to integrate with new IP-based applications. The transition to all-IP networks required a new, flexible mechanism that could work across diverse access networks (e.g., LTE, 5G, WLAN) and support multimedia sessions beyond simple voice calls. CDIV solves the problem of user accessibility and service personalization in a complex, multi-device environment by allowing users to define intelligent routing rules that reflect their availability and preferences.

The primary motivation was to replicate and enhance the popular call forwarding features from legacy systems within the IMS framework, ensuring backward compatibility for service providers migrating their networks while also enabling new, richer diversion scenarios. It addresses key user needs such as avoiding missed calls, screening unwanted communications, and creating a single point of contact that can reach the user on any device. From a network operator perspective, CDIV improves network resource utilization by efficiently redirecting sessions that would otherwise result in failed call attempts and unnecessary signaling load. By standardizing CDIV within 3GPP starting in Release 7, it ensured interoperability between different vendors' IMS equipment and allowed for the creation of a consistent user experience across various service providers and device types, forming a foundational service for commercial VoLTE and VoNR deployments.

Key Features

  • Unconditional diversion of all incoming sessions to a pre-defined address
  • Conditional diversion based on subscriber state (Busy, No Reply, Not Reachable)
  • Diversion based on the identity of the calling party (e.g., from specific numbers or anonymous calls)
  • Support for diversion to different target addresses depending on the triggering condition
  • Integration with IMS core via Initial Filter Criteria (iFC) and Application Server (AS)
  • User provisioning via Ut interface (XCAP) for self-management of diversion rules

Evolution Across Releases

Rel-7 Initial

Introduced CDIV as a core IMS supplementary service, defining the basic architecture where an Application Server (AS) executes diversion logic based on triggers like busy, no reply, and not reachable. It specified integration with the S-CSCF using initial Filter Criteria and standardized the service scenarios and procedures in the IMS service control model.

Defining Specifications

SpecificationTitle
TS 22.173 3GPP TS 22.173
TS 22.273 3GPP TS 22.273
TS 22.401 3GPP TS 22.401
TS 24.173 3GPP TS 24.173
TS 24.186 3GPP TS 24.186
TS 24.196 3GPP TS 24.196
TS 24.292 3GPP TS 24.292
TS 24.315 3GPP TS 24.315
TS 24.404 3GPP TS 24.404
TS 24.405 3GPP TS 24.405
TS 24.406 3GPP TS 24.406
TS 24.407 3GPP TS 24.407
TS 24.408 3GPP TS 24.408
TS 24.410 3GPP TS 24.410
TS 24.411 3GPP TS 24.411
TS 24.416 3GPP TS 24.416
TS 24.429 3GPP TS 24.429
TS 24.447 3GPP TS 24.447
TS 24.454 3GPP TS 24.454
TS 24.504 3GPP TS 24.504
TS 24.505 3GPP TS 24.505
TS 24.508 3GPP TS 24.508
TS 24.516 3GPP TS 24.516
TS 24.529 3GPP TS 24.529
TS 24.604 3GPP TS 24.604
TS 24.605 3GPP TS 24.605
TS 24.606 3GPP TS 24.606
TS 24.607 3GPP TS 24.607
TS 24.608 3GPP TS 24.608
TS 24.610 3GPP TS 24.610
TS 24.611 3GPP TS 24.611
TS 24.615 3GPP TS 24.615
TS 24.616 3GPP TS 24.616
TS 24.629 3GPP TS 24.629
TS 24.642 3GPP TS 24.642
TS 24.647 3GPP TS 24.647
TS 24.654 3GPP TS 24.654
TS 29.163 3GPP TS 29.163
TS 29.165 3GPP TS 29.165
TS 29.292 3GPP TS 29.292
TS 29.364 3GPP TS 29.364
TS 29.864 3GPP TS 29.864
TS 29.935 3GPP TS 29.935
TS 32.260 3GPP TR 32.260
TS 32.275 3GPP TR 32.275
TS 32.298 3GPP TR 32.298
TS 32.850 3GPP TR 32.850