Description
Communication Forwarding Unconditional (CFU) is a fundamental supplementary service within the 3GPP architecture that provides automatic call forwarding functionality. The service operates at the network level, intercepting incoming communication sessions before they reach the intended subscriber's device and redirecting them to a preconfigured forwarding destination. This redirection occurs unconditionally for all incoming sessions, meaning the forwarding logic doesn't depend on the subscriber's status, location, or any other conditional factors.
Architecturally, CFU is implemented within the core network's service control functions, specifically in the Home Location Register (HLR) for circuit-switched domains and Home Subscriber Server (HSS) for packet-switched domains. When a communication session arrives at the Mobile Switching Center (MSC) or IP Multimedia Subsystem (IMS) core, the network queries the subscriber's service profile stored in the HLR/HSS. If CFU is active, the network retrieves the forwarding number and immediately redirects the session without attempting to establish a connection to the original destination. The forwarding process is transparent to the calling party, who experiences normal call setup procedures.
Key components involved in CFU implementation include the service control point (HLR/HSS), service switching point (MSC/IMS-CSCF), and the subscriber's service profile database. The service profile contains critical parameters such as the CFU activation status, forwarding destination number, and service subscription validity. When activated, CFU takes precedence over most other supplementary services, ensuring consistent forwarding behavior. The service supports both voice calls and multimedia sessions in IMS environments, maintaining compatibility across different network generations from 2G through 5G.
CFU's operation involves several protocol interactions between network elements. When an incoming session arrives, the MSC or IMS-CSCF sends a query to the HLR/HSS using Mobile Application Part (MAP) or Diameter protocols. The HLR/HSS responds with the subscriber's service profile, including CFU parameters if active. The network then establishes the session to the forwarding destination using standard call setup procedures. This process occurs within milliseconds, ensuring minimal impact on call setup times while providing reliable forwarding functionality.
Purpose & Motivation
CFU was created to address the fundamental need for communication reliability and accessibility in mobile networks. Before its introduction, subscribers who were unavailable would miss important calls, leading to communication gaps and potential business losses. The service solves this problem by ensuring all incoming communications reach an alternative destination where the subscriber can receive them, whether that's another phone, office line, or voicemail system.
Historically, CFU emerged as part of the GSM supplementary services framework in the early 1990s, building upon similar concepts from fixed-line telephony. It addressed limitations of earlier mobile systems that lacked sophisticated call handling capabilities. The unconditional nature of CFU provides simplicity and reliability compared to conditional forwarding services, making it suitable for scenarios where subscribers need consistent redirection regardless of their circumstances, such as during extended absences or when using a secondary device exclusively.
The service also supports network efficiency by reducing failed call attempts and unnecessary paging procedures. When subscribers activate CFU, the network can immediately redirect sessions without expending resources trying to locate unavailable devices. This optimization becomes particularly valuable in congested networks or during peak usage periods. Additionally, CFU enables various business applications, including virtual office setups, call center routing, and personal number services that require reliable call forwarding capabilities.
Key Features
- Unconditional forwarding of all incoming sessions
- Network-based implementation requiring no device support
- Transparent operation to calling parties
- Precedence over most other supplementary services
- Support for both circuit-switched and packet-switched domains
- Compatibility across 2G, 3G, 4G, and 5G networks
Evolution Across Releases
Introduced CFU as a standardized supplementary service within the GSM/UMTS architecture. Initial implementation focused on circuit-switched voice calls with support through HLR-based service control. The architecture established basic activation/deactivation procedures and forwarding number management through standardized network interfaces and protocols.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.173 | 3GPP TS 22.173 |
| TS 22.273 | 3GPP TS 22.273 |
| TS 23.018 | 3GPP TS 23.018 |
| TS 24.173 | 3GPP TS 24.173 |
| TS 24.186 | 3GPP TS 24.186 |
| TS 24.292 | 3GPP TS 24.292 |
| TS 24.404 | 3GPP TS 24.404 |
| TS 24.406 | 3GPP TS 24.406 |
| TS 24.416 | 3GPP TS 24.416 |
| TS 24.447 | 3GPP TS 24.447 |
| TS 24.504 | 3GPP TS 24.504 |
| TS 24.516 | 3GPP TS 24.516 |
| TS 24.604 | 3GPP TS 24.604 |
| TS 24.606 | 3GPP TS 24.606 |
| TS 24.615 | 3GPP TS 24.615 |
| TS 24.616 | 3GPP TS 24.616 |
| TS 24.642 | 3GPP TS 24.642 |
| TS 24.647 | 3GPP TS 24.647 |
| TS 29.292 | 3GPP TS 29.292 |
| TS 29.364 | 3GPP TS 29.364 |
| TS 29.864 | 3GPP TS 29.864 |
| TS 32.275 | 3GPP TR 32.275 |