Description
RAN User Plane Congestion Information (RUCI) is a standardized mechanism within 3GPP networks that enables the Radio Access Network (RAN) to communicate real-time congestion status in the user plane to core network elements, primarily the Policy and Charging Rules Function (PCRF) and Packet Data Network Gateway (PGW). This information exchange allows the network to implement proactive and reactive measures to manage traffic during periods of high load or resource scarcity. RUCI works by defining specific signaling procedures and information elements that convey congestion indicators, such as congestion levels (e.g., low, medium, high), affected areas (e.g., cell-level or RAN node), and timestamps, which are transmitted from RAN nodes like eNodeBs in LTE or gNBs in 5G to the core network over standardized interfaces.
Architecturally, RUCI leverages existing interfaces, such as the S1 interface in LTE (between eNodeB and MME/SGW) or the N2 interface in 5G (between gNB and AMF), with extensions to support congestion reporting. In the core network, the PCRF uses this information to dynamically adjust policy decisions, potentially triggering actions like throttling data rates, prioritizing certain services, or redirecting traffic. Key components include the RAN congestion detection function, which monitors metrics like radio resource utilization or buffer occupancy, and the congestion reporting function, which formats and sends RUCI messages. The process involves detection, reporting, policy enforcement, and potential feedback loops to alleviate congestion.
RUCI's role is integral to end-to-end quality of service (QoS) management and network optimization. By providing visibility into RAN conditions, it enables more intelligent traffic steering and resource allocation, aligning with concepts like network slicing and service-aware operations. For example, during congestion, RUCI can help ensure that critical services like emergency communications maintain performance while non-essential traffic is deprioritized. Its implementation supports both LTE and 5G systems, enhancing adaptability in heterogeneous networks and contributing to efficient spectrum usage and improved user experience.
Purpose & Motivation
RUCI was developed to address the challenge of inefficient resource management during user plane congestion in mobile networks, where traditional methods lacked real-time coordination between RAN and core network policies. Prior to RUCI, congestion handling was often localized to the RAN, with limited ability to influence end-to-end traffic flows or apply service-specific adjustments from the core. This could lead to suboptimal QoS, wasted resources, and poor user experience during peak loads.
Introduced in 3GPP Release 13, RUCI was motivated by the growing data traffic demands and the need for more dynamic, holistic congestion management. It solves these problems by establishing a standardized feedback mechanism, enabling the core network to react to RAN conditions with granular policy controls. This allows for better support of diverse services, including mission-critical and latency-sensitive applications, and aligns with trends towards software-defined networking and automated traffic optimization in evolving 4G and 5G deployments.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (20 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the RUCI function was not newly introduced. The provided Change Request titles for this release describe other features and corrections, such as Early Data Transmission for Control Plane CIoT EPS optimization and a correction for the Control Plane back-off timer, but none pertain to the introduction of RAN User Plane Congestion Information.
In Release 16, the RUCI function was enhanced to include Caller and Callee information in its reporting. It also introduced the use of Early Data Transmission (EDT) within the User Plane CIOT EPS Optimisation procedure for congestion-related messaging. Furthermore, the release provided a correction to a reference in the Control Plane NAS congestion control mechanism.
In Release 17, the new RUCI (RAN User Plane Congestion Information) function was not introduced or modified based on the provided change requests. The listed enhancements for this release instead include corrections to enable the retrieval of Network Provided Location information within a MESSAGE request. Other updates involve EPS User Plane Integrity Protection and the PCRF control of MPS for DTS.
- EPS User Plane Integrity Protection with minimal core network changes TS 23.401CR3645
- PCRF control of MPS for DTS TS 29.213CR0743
- Acceptance and Rejection of Paging Restriction Information TS 23.401CR3696
- ULI provision with PScell information TS 23.401CR3703
- Correction to enable retrieval of Network Provided Location information in a MESSAGE request TS 29.212CR1711
- Correction to enable retrieval of Network Provided Location information in a MESSAGE request TS 29.213CR0747
In Release 18, the RUCI function was expanded to include new procedures for handling congestion control and related UE behavior. Furthermore, the scope of RUCI was broadened to convey Satellite Coverage Availability Information specifically for IoT devices over Non-Terrestrial Networks (IoT NTN).
In Release 19, the RUCI function was enhanced with a subscription control mechanism for the delivery of time reference information within the EPS. Furthermore, a new condition was introduced for the PCRF to detect a PCEF failure in a timely manner, and clarifications were provided on congestion control procedures.
Explore further
Broader topics and technologies where RUCI plays a role.
Defining Specifications
3GPP specifications that define or reference RUCI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 29.213 vj20 | PCC Signalling Flows and QoS Mapping | Rel-19 |
| TS 29.217 vj00 | Policy and Charging Control (PCC) for Np Interface | Rel-19 |