Aggregated RUCI Report Request

Description

The Aggregated RUCI Report Request (ARR) is a standardized procedure defined within 3GPP's Policy and Charging Control (PCC) architecture, specifically in the Gx and Gxx reference points. It functions as a command from the Policy and Charging Rules Function (PCRF) to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Reporting Function (BBERF). The core purpose is to request a consolidated report containing Resource Usage and Control Information from one or multiple user sessions or bearers, rather than generating separate reports for each individual entity. This aggregation is crucial for scalable network management in environments with high session density.

Architecturally, ARR operates within the PCC framework where the PCRF acts as the central policy decision point. When the PCRF requires comprehensive resource usage data—for instance, to evaluate the impact of a policy change, perform traffic analysis, or monitor Quality of Service (QoS) compliance—it sends an ARR command via the Gx interface (to PCEF in the PDN Gateway) or Gxx interface (to BBERF in the Serving Gateway or access network). The request specifies the aggregation criteria, such as a group of subscribers, a specific Access Point Name (APN), a service data flow aggregate, or a set of QoS parameters. The receiving function (PCEF/BBERF) then collects the relevant RUCI data, which includes metrics like data volume (uplink/downlink), duration, QoS class identifier usage, and event triggers, and compiles them into a single aggregated report sent back to the PCRF.

The mechanism works by utilizing specific Attribute-Value Pairs (AVPs) within the Diameter protocol used on Gx/Gxx interfaces. Key AVPs include the Aggregated-RUCI-Report-Request AVP itself, which may contain sub-AVPs defining the scope of aggregation (e.g., User-Equipment-Info, APN-Aggregate-Max-Bitrate-DL). Upon receipt, the enforcement function identifies all active sessions or bearers matching the criteria, extracts the requested RUCI parameters, and performs the aggregation (e.g., summing total data volumes, calculating average bitrates). This aggregated data is then formatted into an Aggregated-RUCI-Report AVP and transmitted in a Diameter answer message. The process reduces the number of individual report transactions, conserving signaling bandwidth and processing resources on both the PCRF and enforcement functions.

ARR's role in the network is primarily operational and analytical. It supports functions like policy optimization, where the PCRF can adjust charging rules or QoS policies based on aggregated traffic patterns. It aids in capacity planning by providing summarized resource consumption across user groups or network segments. Furthermore, it enhances troubleshooting and performance monitoring by allowing network operators to request consolidated snapshots of resource usage without generating excessive signaling load. The aggregation logic is typically timer-based or event-triggered, ensuring reports are generated at appropriate intervals or when specific thresholds are met, balancing timeliness with efficiency.

Purpose & Motivation

ARR was introduced to address the scalability challenges in collecting resource usage data from a rapidly growing number of user sessions and bearers in 3GPP networks. Prior to its introduction, monitoring resource utilization often required individual queries or reports for each session, leading to significant signaling overhead on the Gx/Gxx interfaces and processing load on the PCRF and enforcement functions. As networks evolved to support higher user densities and more complex services (like IMS and mobile broadband), this per-session reporting model became inefficient and could impact network performance, especially during peak usage or large-scale policy audits.

The primary problem ARR solves is the reduction of Diameter signaling traffic associated with resource reporting. By enabling aggregated reports, a single request-response transaction can replace dozens or hundreds of individual report transactions. This is particularly valuable for operational tasks like auditing policy compliance across a subscriber group, monitoring aggregate bandwidth consumption for a corporate APN, or gathering statistics for network optimization. The motivation for its creation stemmed from the need for more efficient Operations, Administration, and Maintenance (OAM) capabilities within the PCC framework, ensuring that management functions could scale alongside user traffic without becoming a bottleneck.

Historically, as 3GPP Release 6 solidified the PCC architecture, the focus was on enabling dynamic policy control per subscriber session. However, network operators quickly identified the need for bulk operations and summarized views for efficient management. ARR, introduced in Rel-6, provided this capability by extending the existing RUCI reporting mechanisms defined in earlier PCC specifications. It addressed the limitation of purely session-centric reporting, allowing network management systems and the PCRF itself to obtain a holistic view of resource usage, which is essential for traffic engineering, billing reconciliation, and proactive capacity management in evolving packet core networks.