Call Forwarding on mobile subscriber Busy

Description

Call Forwarding on mobile subscriber Busy (CFB) is a fundamental supplementary service within the 3GPP architecture that operates at the core network level, specifically within the Home Location Register (HLR) and Mobile Switching Center (MSC) or IP Multimedia Subsystem (IMS) call session control functions. When an incoming call arrives for a subscriber who has activated CFB and whose line is currently engaged in another call, the network detects the busy condition through call state monitoring at the MSC server or telephony application server. The service logic then intercepts the call setup attempt and redirects it to a pre-configured forwarding number stored in the HLR or as a subscriber profile in the Home Subscriber Server (HSS). This redirection occurs before the caller receives any audible indication, creating a seamless transition.

The technical implementation involves several key signaling protocols. In circuit-switched networks, the service utilizes Mobile Application Part (MAP) signaling between the HLR and MSC/VLR to retrieve and verify forwarding information. When the busy condition is detected, the MSC generates a MAP_SEND_ROUTING_INFORMATION_FOR_SM message or equivalent to obtain the forwarding destination. In IMS-based networks, CFB is implemented using SIP (Session Initiation Protocol) where the Serving-Call Session Control Function (S-CSCF) evaluates initial filter criteria and invokes application server logic when the called party's registration status indicates busy. The S-CSCF then modifies the SIP INVITE request to redirect to the forwarded-to address.

CFB interacts with other call forwarding variants through a priority hierarchy defined in 3GPP specifications. When multiple forwarding conditions exist simultaneously (such as CFB along with Call Forwarding Unconditional or Call Forwarding No Reply), the network follows standardized conflict resolution rules. The service supports both basic forwarding to a single number and more advanced scenarios like sequential forwarding where multiple numbers can be tried. Activation and deactivation occur through USSD codes, supplementary service control procedures, or via web interfaces, with the status stored persistently in the network database.

From a network architecture perspective, CFB requires tight integration between call control functions and subscriber data management. The MSC or CSCF must have real-time access to subscriber busy status while simultaneously consulting forwarding configuration data. This creates a distributed service logic that spans multiple network elements while maintaining call setup timing requirements. Performance considerations include minimizing additional latency introduced by the forwarding decision process and ensuring forwarding information remains current despite subscriber mobility across location areas or tracking areas.

Purpose & Motivation

CFB was created to address the fundamental limitation of traditional telephony where callers would receive a busy signal when the called party was engaged in another conversation, resulting in missed communication opportunities and inefficient call attempts. Before the implementation of call forwarding services, mobile subscribers had no way to ensure important calls would reach them or an alternative contact when they were unavailable. This was particularly problematic in business contexts where missed calls could mean lost opportunities or delayed decision-making.

The service emerged as part of the GSM supplementary services framework in early 3GPP releases, building upon similar concepts from fixed-line telephony but adapted for mobile environments with unique challenges like subscriber mobility and varying network conditions. CFB solved the problem of communication continuity by providing a systematic way to redirect calls based on specific conditions, allowing users to maintain accessibility even during periods of unavailability. This was especially valuable in the era of circuit-switched voice where alternative communication methods were limited compared to today's multi-modal messaging options.

Beyond individual convenience, CFB supported operational requirements for organizations needing to maintain customer contact channels. It enabled call center overflow routing, executive assistant screening, and basic call distribution without requiring complex PBX systems. The service also formed a foundation for more advanced call handling features that would evolve in later 3GPP releases, establishing the architectural patterns for conditional call routing that would later be extended to IMS and VoLTE/VoNR implementations.

Key Features

• Conditional call redirection based on called party busy status
• Network-based implementation requiring no special handset capabilities
• Configurable forwarding destination number stored in HLR/HSS
• Integration with other supplementary services through standardized priority rules
• Support for both circuit-switched and IMS-based network architectures
• Real-time invocation based on call state monitoring at MSC or CSCF

Evolution Across Releases

Defining Specifications