RCAF

RAN Congestion Awareness Function

Management →
Introduced in Rel-13 Also in: Services

RCAF is a network function that monitors and reports radio access network congestion to enable policy-based traffic management and QoS adjustments during high load.

Category
Management
Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Also touches
1 segments
Specifications
15 specs
RCAF Description Purpose Related Classification Detected Changes Specifications

Description

The RAN Congestion Awareness Function (RCAF) is a functional entity introduced in 3GPP Release 13, primarily defined within the Policy and Charging Control (PCC) architecture. It operates as a logical function that can be integrated within the Radio Access Network (RAN), such as in an eNodeB or gNB, or as a standalone network element. Its primary role is to detect and quantify congestion conditions on specific radio resources, such as cells, tracking areas, or radio access technologies. RCAF monitors key performance indicators like radio resource utilization, number of active users, and traffic load, translating these raw metrics into standardized congestion reports. These reports are then communicated to the core network's Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) via standardized interfaces, such as Rx or N5, depending on the network generation (EPC or 5GC). This communication allows the policy framework to be aware of real-time RAN conditions, a capability that was largely absent in earlier releases. The RCAF does not directly enforce policies itself; instead, it acts as an information provider, enabling intelligent, context-aware policy decisions in the core network. In the 5G system, RCAF principles are integrated into the Network Data Analytics Function (NWDAF) for more holistic analytics, but the standalone RCAF remains specified for certain deployments and interfaces, ensuring backward compatibility and specific congestion reporting scenarios. Its architecture is designed to be scalable and technology-agnostic, supporting congestion reporting for LTE, NR, and even non-3GPP access types when relevant interfaces are established.

Purpose & Motivation

RCAF was created to address the critical gap between RAN load conditions and core network policy enforcement. Prior to its introduction, policy decisions in the PCC architecture were primarily based on subscriber profiles, service data flows, and core network conditions, with limited real-time insight into the radio interface congestion. This often led to inefficient resource allocation, where high-priority services could be throttled or blocked during RAN congestion without the policy system being aware of the root cause, or conversely, policies could not proactively alleviate congestion by adjusting traffic. The motivation stemmed from the increasing demand for mobile data and the need for more sophisticated traffic management to ensure Quality of Experience (QoE), especially for delay-sensitive services like voice over LTE (VoLTE) or real-time gaming. By providing RAN congestion awareness to the PCRF/PCF, operators gained the ability to implement dynamic policy rules that respond to network load. For example, during congestion, the policy system could temporarily restrict bandwidth-heavy, low-priority applications or prioritize emergency services, thereby optimizing overall network utilization and maintaining service quality for critical users. This represented a significant evolution towards more intelligent, condition-aware networks, paving the way for later analytics-driven functions in 5G.

Classification

Part ofNWDAF
Related approachesPCRFPCCQoSRAN

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-13, normative work from Rel-16.

Rel-16 1 change

In Release 16, the primary update for the RCAF involved a correction to its documentation. Specifically, this correction addressed an inaccurate reference within the procedures for Control Plane NAS congestion control.

  • Correction of reference in Control Plane NAS congestion control TS 23.401CR3473
Rel-17 1 change

In Release 17, the enhancement for the RCAF function specifically introduced PCRF control of MPS for DTS. This new capability allows the Policy and Charging Rules Function to manage the Multimedia Priority Service for Data Transfer Services.

  • PCRF control of MPS for DTS TS 29.213CR0743
Rel-18 5 changes

In Release 18, the RCAF function was enhanced to support the measurement and reporting of congestion information, including data rate and congestion reports. New procedures were defined for handling congestion control and related UE behaviour. Furthermore, the release specified interactions between ECN marking for L4S and Congestion Monitoring, while also resolving editorial details for QoS monitoring in the context of congestion.

  • Support of the congestion information measurement and reporting TS 29.122CR0741
  • Interactions between ECN marking for L4S and Congestion Monitoring TS 29.122CR0793
  • Handling on congestion control and UE behaviour TS 23.401CR3745
  • Resolve the Editor’s Notes for QoS monitoring for congestion TS 29.122CR0789
  • Data rate and congestion report TS 29.122CR0849
Rel-19 3 changes

In Release 19, the enhancements for the RCAF function focused on improving reliability and clarifying behavior during network element failures. Specifically, the release introduced a new condition for the PCRF to detect a PCEF failure in a timely manner and provided clarifications on the PCRF's behavior in the event of a PGW failure. Furthermore, the specifications included general clarification on congestion control procedures.

  • Add a new condition for the PCRF detecting PCEF failure in time TS 29.213CR0751
  • Clarify the behavior of the PCRF in the case of PGW failure TS 29.214CR1704
  • Clarification on congestion control TS 23.401CR3828

Explore further

Broader topics and technologies where RCAF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 29.122 vj40 T8 Reference Point for Northbound APIs Rel-19
TS 29.153 vj00 Ns Reference Point Protocol between SCEF and RCAF Rel-19
TS 29.212 vj00 Gx/Gxx/Sd/St Diameter Protocol Rel-19
TS 29.213 vj20 PCC Signalling Flows and QoS Mapping Rel-19
TS 29.214 vj20 Policy and Charging Control over Rx Rel-19
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19
TS 29.217 vj00 Policy and Charging Control (PCC) for Np Interface Rel-19
TS 29.219 vj00 Sy Reference Point Stage 3 Specification Rel-19
TS 29.405 vj00 Nq-AP Protocol Specification Rel-19
TS 29.810 vd00 Diameter Load Control Study Rel-13
TS 32.254 vj21 Charging for Northbound APIs Rel-19
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19