Completion of Communication sessions on No Reply

Description

Completion of Communication sessions on No Reply (CCNR) is a standardized supplementary service within 3GPP networks that provides automatic call completion functionality when initial call attempts fail due to the called party being busy or not answering. The service operates through a network-based queuing mechanism where the calling party's request is stored and monitored until the called subscriber becomes available for communication. When activated, CCNR intercepts failed call attempts and places them in a waiting state rather than terminating the connection immediately.

Architecturally, CCNR is implemented within the core network elements, primarily involving the Home Subscriber Server (HSS) for subscriber data management and the Mobile Switching Center (MSC) or IP Multimedia Subsystem (IMS) nodes for call processing. The service relies on specific signaling procedures defined in 3GPP specifications to establish, maintain, and terminate the completion request. When a user activates CCNR for a failed call, the network creates a completion record containing the calling and called party identities, timestamp, and service parameters. This record is stored in the appropriate network element based on the called party's registration status and network configuration.

The service operates through a monitoring mechanism that tracks the called party's availability status. When the called subscriber transitions from busy or unavailable to idle and registered, the network detects this state change and initiates the completion procedure. The network then attempts to establish the communication session automatically, notifying both parties through specific tones or indications. The implementation includes timers and counters to prevent indefinite queuing, with configurable expiration periods and maximum retry attempts. CCNR integrates with other supplementary services like call forwarding and call barring, with defined precedence rules to avoid conflicts between different services.

Key technical components include the CCNR activation/deactivation procedures, completion request storage and management, availability monitoring mechanisms, and automatic call establishment protocols. The service supports both voice and multimedia sessions in IMS environments, with specific adaptations for different session types. Security measures ensure that only authorized users can activate the service and that completion attempts follow proper authentication procedures. CCNR's implementation varies between circuit-switched and packet-switched domains, with IMS-based implementations offering enhanced flexibility and integration with other multimedia services.

Purpose & Motivation

CCNR was developed to address the common problem of failed communication attempts in mobile networks, particularly when users encounter busy signals or no answer situations. Before CCNR, callers had to repeatedly attempt connections manually, which was inefficient and frustrating. The service automates this process, allowing users to request automatic completion once the called party becomes available, thereby improving communication success rates and user convenience.

Historically, similar services existed in fixed-line networks (often called 'call completion to busy subscriber' or CCBS), but 3GPP standardized CCNR specifically for mobile environments where subscriber mobility and registration states added complexity. The service addresses limitations of basic call handling where failed attempts simply terminated without recourse. By introducing network-managed completion queues, CCNR reduces missed connections and improves overall network utilization by ensuring communication attempts eventually succeed when conditions permit.

The creation of CCNR was motivated by the need to enhance basic telephony services in mobile networks to match or exceed fixed-line capabilities. It solves the problem of inefficient manual retry attempts and improves customer satisfaction by ensuring important communications aren't missed due to temporary unavailability. In business contexts, CCNR ensures critical calls are completed without requiring constant monitoring by the calling party, making it particularly valuable for time-sensitive communications.

Key Features

• Automatic call completion when called party transitions from busy/unavailable to available
• Network-based queuing mechanism with configurable timeout periods
• Support for both circuit-switched and IMS-based multimedia sessions
• Integration with other supplementary services through defined precedence rules
• Subscriber-controlled activation/deactivation with standardized procedures
• Availability monitoring through registration and state tracking mechanisms

Evolution Across Releases

Defining Specifications