Completion of Communications to Busy Subscriber

Description

Completion of Communications to Busy Subscriber (CCBS) is a network-managed supplementary service standardized by 3GPP. When a calling party (User A) attempts to establish a call to a called party (User B) who is busy (e.g., engaged in another call), and CCBS is invoked, the network stores the call request. The network then monitors the status of User B. Once User B becomes idle (i.e., finishes the ongoing call and becomes available for new calls), the network automatically initiates a new call setup attempt from User A to User B. This process is orchestrated by the network without requiring User A to manually redial.

The architectural implementation of CCBS involves several core network (CN) functional entities, primarily within the Home Subscriber Server (HSS) and the Mobile Switching Center (MSC) or IP Multimedia Subsystem (IMS) nodes in later releases. When CCBS is activated for a call attempt, the MSC serving User A acts as the CCBS originator. It records the call request details, including the identities of User A and User B, and registers a CCBS request with the HSS or a dedicated CCBS application server. The serving MSC for User B (or a monitoring function) is notified to track User B's status. This status monitoring is achieved through registration and call state supervision mechanisms.

Key operational components include the CCBS Request, CCBS Recall, and CCBS Call procedures. The CCBS Request is initiated by the calling user, typically via a specific DTMF sequence or service code, prompting the network to store the request. The network then enters a monitoring phase. Upon detecting User B's transition to an idle state, the network triggers a CCBS Recall towards User A, notifying them that the called party is now available and seeking authorization to proceed with the automatic call setup. If User A accepts (often by going off-hook), the network executes the CCBS Call procedure, establishing the call to User B. Throughout this process, timers manage the request's validity period, and the service maintains priority and queuing logic if multiple CCBS requests exist for the same busy subscriber.

In the IMS architecture (from Release 5 onwards), CCBS functionality is implemented as an Application Server (AS) within the IMS service layer. The CCBS AS interacts with the Serving-Call Session Control Function (S-CSCF) using the ISC interface and leverages SIP protocols for service control. The AS stores the request, subscribes to the called party's registration and dialog state events (using SIP SUBSCRIBE/NOTIFY), and initiates the call setup when conditions are met. This transition to an IMS-based, SIP-controlled service allowed for greater integration with other multimedia services and more flexible service logic compared to the earlier circuit-switched (CS) implementation.

Purpose & Motivation

CCBS was created to solve the user experience problem of repeatedly and manually dialing a number that is frequently busy. Before its introduction, callers had to remember to retry the call later, often leading to missed connections and frustration. This was particularly inefficient in business contexts or for time-sensitive communications. The service automates this retry process, transferring the burden from the user to the network, thereby increasing the likelihood of successful connection and saving user time and effort.

From a network operator perspective, CCBS also serves to increase network utilization and call completion rates. By managing call completion requests in an orderly, queued fashion, it can reduce the volume of repeated, simultaneous call attempts that occur when a busy subscriber becomes free, which could cause signaling spikes. It provides a controlled mechanism for call completion that can be managed for fairness and priority. Historically, similar concepts existed in fixed networks, and 3GPP standardized CCBS to bring this valuable convenience feature to mobile users, enhancing the service portfolio and competitiveness of GSM and UMTS networks.

The motivation for its creation in Release 99 was part of a broader effort to enrich the basic telephony service with intelligent supplementary services, moving beyond simple voice calls to offer features that mimic or improve upon the user experience of fixed-line services. It addressed the limitation of the basic mobile call model, where a busy condition was a terminal event requiring entirely new user action. CCBS introduced statefulness and proactivity into the network's call handling logic for these scenarios.

Key Features

• Automatic call re-attempt upon called party availability
• Network-based request storage and subscriber status monitoring
• User notification (recall) to the calling party before final setup
• Configurable request duration with timer-based expiration
• Priority handling and queuing for multiple requests
• Support in both circuit-switched (CS) and IP Multimedia Subsystem (IMS) domains

Evolution Across Releases

Defining Specifications