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.
Key Features
- Reports real-time RAN congestion status to core network
- Enables dynamic policy adjustments by PCRF/PGW
- Supports congestion levels and geographic area indicators
- Works over LTE S1 and 5G N2 interfaces
- Facilitates service-aware traffic management during overload
- Enhances end-to-end QoS and resource efficiency
Evolution Across Releases
Introduced RUCI as a new capability for LTE networks, defining procedures for RAN to report user plane congestion information to the core network via enhanced S1 signaling. It enabled PCRF-based policy control during congestion, initializing support for coordinated congestion management between access and core.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.203 | 3GPP TS 23.203 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 29.212 | 3GPP TS 29.212 |
| TS 29.213 | 3GPP TS 29.213 |
| TS 29.217 | 3GPP TS 29.217 |