Description
Communication session Forwarding on No Logged-in (CFNL) is a standardized 3GPP supplementary service that operates within the IP Multimedia Subsystem (IMS) architecture. When a user's User Equipment (UE) is not registered with the network—either because it is switched off, out of coverage, or has not performed an initial registration—the network cannot establish a direct session to that UE. CFNL provides a mechanism to intercept these incoming session requests and redirect them to a pre-configured alternative destination, such as another telephone number, voicemail system, or application server. The service is invoked by the Serving-Call Session Control Function (S-CSCF) when it detects that the target user is not currently logged into the network, based on registration status information maintained in the Home Subscriber Server (HSS).
The technical implementation of CFNL involves several network elements working in coordination. When an incoming Session Initiation Protocol (SIP) INVITE request arrives at the S-CSCF for a user who is not registered, the S-CSCF checks the user's service profile retrieved from the HSS. If CFNL is active for that user, the S-CSCF applies the appropriate forwarding logic based on the user's configuration. The forwarding destination is specified in the user's service data, which can include conditions such as time-of-day restrictions or different forwarding targets for different calling parties. The S-CSCF then modifies the SIP request by replacing the original Request-URI with the forwarding address and continues the session establishment toward the new destination.
CFNL operates in conjunction with other forwarding services like Communication Forwarding Unconditional (CFU), Communication Forwarding on Busy User (CFB), and Communication Forwarding on Not Reachable (CFNRc) to provide comprehensive session management capabilities. Unlike CFNRc, which handles cases where the user is registered but unreachable (e.g., due to radio conditions), CFNL specifically addresses the scenario where no registration exists at all. The service supports both voice and multimedia sessions within IMS, making it applicable to VoLTE, VoNR, and other IMS-based communication services. Configuration and activation of CFNL can be performed through Ut interface using XCAP protocol or via network-initiated procedures, giving users flexibility in managing their forwarding preferences.
From a network architecture perspective, CFNL relies heavily on the integration between the S-CSCF and HSS. The HSS stores the CFNL service data as part of the user's IMS service profile, including the forwarding address and any applicable conditions. When the S-CSCF receives an initial filter criteria (iFC) trigger for an unregistered user, it executes the appropriate Service Point Trigger (SPT) that invokes the CFNL application server logic. The application server, which may be integrated within the S-CSCF or implemented as a separate AS, then processes the forwarding decision. This architecture ensures that CFNL operates consistently across different network deployments and vendor implementations while maintaining compliance with 3GPP specifications.
Purpose & Motivation
CFNL was introduced to address a fundamental limitation in mobile communication systems: the inability to reach users when their devices are not actively registered with the network. Before CFNL standardization, networks would typically reject incoming sessions for unregistered users with error responses like "480 Temporarily Unavailable" or "404 Not Found," resulting in missed communications and poor user experience. This was particularly problematic as users increasingly relied on mobile devices as their primary communication means and expected reliable connectivity even when their devices were temporarily offline.
The service solves the problem of communication loss during periods when User Equipment cannot maintain network registration due to various reasons including power conservation, extended out-of-coverage situations, or manual device shutdown. By providing a standardized mechanism to forward sessions to alternative destinations, CFNL ensures that important communications are not lost but rather redirected according to user preferences. This capability is especially valuable for business users who cannot afford to miss critical calls and for emergency communication scenarios where reliable contact is essential.
CFNL's creation was motivated by the evolution toward all-IP networks and IMS architecture in 3GPP Release 7. As networks transitioned from circuit-switched to packet-switched domains, there was a need to replicate and enhance traditional supplementary services in the new IP-based environment. CFNL represents the IMS equivalent of the circuit-switched "Forwarding on Mobile Subscriber Not Reachable" service but with enhanced capabilities for multimedia sessions. The service addresses the growing expectation of "always available" communication in modern mobile networks while providing users with control over how their communications are handled during offline periods.
Key Features
- Redirects incoming sessions when user equipment is not registered with the network
- Supports both voice and multimedia communication sessions within IMS
- Configurable forwarding destinations including numbers, voicemail, or application servers
- Integrates with HSS for subscriber data and S-CSCF for session control
- Operates based on initial filter criteria and service point triggers in IMS
- Can be configured and activated via Ut interface using XCAP protocol
Evolution Across Releases
Initial introduction of CFNL as part of IMS supplementary services specification. Defined basic architecture where S-CSCF detects unregistered users and forwards sessions to configured destinations. Supported voice sessions with basic forwarding logic and integration with HSS for subscriber data management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.173 | 3GPP TS 22.173 |
| TS 22.273 | 3GPP TS 22.273 |
| 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 |