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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, the CFU function was enhanced as part of the broader work on "IMS multimedia telephony communication service and supplementary services." This included the integration of supplementary services like Communication Waiting (CW) and Malicious Communication Identification (MCID) using the IP Multimedia (IM) Core Network subsystem. Furthermore, specifications for the Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) services were also completed within this framework.
- IMS multimedia telephony communication service and supplementary services TS 24.173CR0122
- Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.615CR0073
- Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.616CR0026
- Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.642CR0088
In Release 19, the updates to Communication Forwarding Unconditional (CFU) were specifically focused on enhancing the procedure for avatar communication. The changes involved multiple updates to the technical specifications governing avatar communication interactions. Furthermore, the release included the removal of a specific normative requirement (EN) related to this avatar communication procedure.
Explore further
Broader topics and technologies where CFU plays a role.
Defining Specifications
3GPP specifications that define or reference CFU, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.173 vk00 | IMS Multimedia Telephony Service Definition | Rel-20 |
| TS 22.273 v1700 | IMS Multimedia Telephony with PSTN/ISDN Simulation | Rel-7 |
| TS 23.018 vj00 | Basic call handling in 3GPP CS domain | Rel-19 |
| TS 24.173 vj00 | Multimedia Telephony Service and Supplementary Services in IMS | Rel-19 |
| TS 24.186 vj60 | IMS Data Channel applications | Rel-19 |
| TS 24.292 vj00 | IMS Centralized Services (ICS) Protocol | Rel-19 |
| TS 24.404 v1700 | Communication Diversion Services (CDIV) | Rel-7 |
| TS 24.406 v810 | Message Waiting Indication (MWI) Protocol | Rel-8 |
| TS 24.416 v1700 | Malicious Call Identification Service | Rel-7 |
| TS 24.447 v800 | Advice Of Charge (AOC) Service Protocol | Rel-8 |
| TS 24.504 v8m0 | Communication Diversion Services Stage 3 | Rel-8 |
| TS 24.516 v830 | MCID Protocol Specification for NGN | Rel-8 |
| TS 24.604 vj00 | Communications Diversion (CDIV) Protocol Spec | Rel-19 |
| TS 24.606 vj00 | MWI Service Protocol Description | Rel-19 |
| TS 24.615 vj00 | Communication Waiting (CW) Service Protocol | Rel-19 |
| TS 24.616 vj00 | Malicious Call Identification (MCID) Protocol | Rel-19 |
| TS 24.642 vj00 | CCBS/CCNR/CCNL SIP Protocol Specification | Rel-19 |
| TS 24.647 vj00 | Advice of Charge (AOC) service protocol | Rel-19 |
| TS 29.292 vj00 | IMS Centralized Services (ICS) Interworking | Rel-19 |
| TS 29.364 vj10 | IMS AS Service Data Descriptions | Rel-19 |
| TS 29.864 v801 | Application Server Service Data Definition for IMS Telephony | Rel-8 |
| TS 32.275 vj00 | MMTel Charging Specification | Rel-19 |