Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

CFU

Communication Forwarding Unconditional

Services →

CFU is a supplementary service that automatically forwards all incoming calls to a predetermined number without first ringing the original destination.

Introduced
Rel-4
Where
Services › IMS
Specifications
23 specs
Also in
Core Network
CFU Description Purpose What changed Neighbours Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define CFU. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 22.173Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.173: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 22.173 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-4 Initial

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

3GPP specifications that define or reference CFU, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.173 vl00 IMS Multimedia Telephony Service Rel-21 read
TS 22.273 v710 IMS Multimedia Telephony with PSTN/ISDN Simulation Rel-7 read
TS 23.018 vj00 Basic call handling in 3GPP CS domain Rel-19 read
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19 read
TS 24.186 vk10 IMS Data Channel and AR Communication Rel-20 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.404 v750 Communication Diversion Services Stage 3 Rel-7 read
TS 24.406 v810 Message Waiting Indication (MWI) Protocol Rel-8 read
TS 24.416 v700 Malicious Call Identification Service Rel-7 read
TS 24.447 v800 Advice Of Charge (AOC) Service Protocol Rel-8 read
TS 24.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 read
TS 24.516 v830 MCID Protocol Specification for NGN Rel-8 read
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 24.606 vj00 MWI Service Protocol Description Rel-19 read
TS 24.615 vj00 Communication Waiting (CW) Service Protocol Rel-19 read
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19 read
TS 24.642 vj00 CCBS/CCNR/CCNL SIP Protocol Specification Rel-19 read
TS 24.647 vj00 Advice of Charge (AOC) service protocol Rel-19 read
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19 read
TS 29.364 vj10 IMS AS Service Data Descriptions Rel-19 read
TS 29.864 v801 Application Server Service Data Definition for IMS Telephony Rel-8 read
TS 32.275 vj00 MMTel Charging Specification Rel-19 read