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

Glossary term · Management

RCAF

RAN Congestion Awareness Function

Management →

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.

Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Specifications
15 specs
Also in
Services
RCAF Description Purpose What changed Neighbours 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.

What changed in its specifications

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

TS 23.060Rel-18 → Rel-19

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

Full comparison in TS 23.060 →
TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →

Release Timeline

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-13 Initial

Initial introduction of RCAF within the PCC architecture for EPC. Defined its role in monitoring RAN congestion and reporting to the PCRF via the Rx interface to enable congestion-aware policy decisions.

Enhanced RCAF capabilities for additional scenarios and refined reporting mechanisms. Integration considerations for network slicing and further alignment with evolving policy frameworks.

Adapted RCAF for 5G System (5GS) interoperability, defining interactions with the PCF and support for NR congestion reporting. Alignment with service-based interfaces.

Further enhancements for coexistence with NWDAF, clarifying roles and ensuring RCAF can provide specific congestion inputs to 5G analytics. Support for edge computing scenarios.

Continued evolution for integrated access and backhaul (IAB) and non-terrestrial networks (NTN), extending congestion reporting to these new RAN deployments.

Maintenance and updates to ensure compatibility with advanced 5G-Advanced features, including enhanced network automation and AI/ML-driven policy control.

Ongoing support and refinement, ensuring RCAF remains relevant for hybrid network environments and new service requirements.

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 Stage 2 Service Description Rel-19 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 29.122 vk10 T8 SCEF Service Exposure APIs Rel-20 read
TS 29.153 vj00 Ns Reference Point Protocol between SCEF and RCAF Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TS 29.217 vj00 Policy and Charging Control (PCC) for Np Interface Rel-19 read
TS 29.219 vj00 Sy Reference Point Stage 3 Specification Rel-19 read
TS 29.405 vj00 Nq-AP Protocol Specification Rel-19 read
TS 29.810 vd00 Diameter Load Control Study Rel-13 read
TS 32.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read