ARA

Aggregated RUCI Report Answer

Management →
Introduced in Rel-13

ARA is a PCC protocol message from the PCRF to the TDF that confirms the aggregated reporting of user plane traffic events for policy and charging.

Category
Management
Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Specifications
2 specs
ARA Description Purpose Related Classification Detected Changes Specifications

Description

The Aggregated RUCI Report Answer (ARA) is a Diameter-based protocol message specified within the 3GPP Policy and Charging Control (PCC) architecture, primarily documented in TS 29.213 and TS 29.217. It operates on the Sd reference point, which is the interface between the Traffic Detection Function (TDF) and the Policy and Charging Rules Function (PCRF). The ARA is a critical component in the Application Detection and Control (ADC) feature, allowing the network to monitor and enforce policies on application-specific traffic in the user plane.

Architecturally, the TDF is responsible for inspecting user data traffic, identifying specific applications or services (e.g., video streaming, social media), and reporting these events to the PCRF. The PCRF is the central policy decision entity that dictates how traffic should be treated for QoS, gating, and charging. When the TDF sends an Aggregated RUCI Report Request (ARR) to the PCRF, it provides a consolidated report of multiple user plane events, such as application starts, stops, or volume thresholds being reached, for one or more user sessions. The ARA is the PCRF's response to this request, acknowledging receipt and providing any necessary instructions or confirmations back to the TDF.

The ARA message contains several key AVPs (Attribute-Value Pairs) that facilitate its function. These include the Session-Id, which identifies the specific Diameter session; the Origin-Host and Origin-Realm, identifying the PCRF; and the Result-Code, indicating the success or failure of the ARR processing. It may also include Charging-Rule-Report AVPs if the PCRF needs to update or remove charging rules based on the aggregated report, or Event-Trigger AVPs to instruct the TDF on new reporting triggers. The message ensures that the PCRF and TDF remain synchronized in their view of user activity, enabling dynamic policy adjustments.

In operation, the ARA completes a transaction initiated by the TDF's periodic or event-triggered reporting. By aggregating multiple events into a single report (ARR), the system reduces signaling overhead compared to reporting each event individually. The PCRF processes this aggregated data, correlates it with subscriber policies, and responds with the ARA. This response may contain new policy decisions, such as modifying bandwidth, applying traffic shaping, or triggering charging events. The ARA thus plays a vital role in enabling efficient, real-time policy enforcement based on application awareness, contributing to optimized network resource utilization and enhanced user experience.

Purpose & Motivation

The ARA was introduced to address the growing need for intelligent application-aware policy control in mobile networks, particularly with the rise of diverse Over-The-Top (OTT) applications. Prior to its introduction, policy control in 3GPP networks was primarily based on bearer-level attributes (e.g., APN, QoS) rather than deep packet inspection (DPI) of application content. This limitation made it difficult for operators to implement granular policies for specific services, such as blocking or throttling certain apps, offering sponsored data, or applying differentiated charging.

The creation of the Application Detection and Control (ADC) feature in Release 13, which includes the ARA, was motivated by operators' demands for more sophisticated traffic management capabilities. The TDF, acting as a DPI engine, could detect applications, but efficient communication with the PCRF was essential. The ARA, as part of the Sd interface protocol, solves the problem of signaling efficiency by enabling aggregated reporting. Instead of the TDF sending a separate message for every single application event (which would create excessive signaling load), it bundles multiple events into an Aggregated RUCI Report Request. The ARA provides the necessary acknowledgment and potential policy updates from the PCRF, ensuring the system scales effectively even with high volumes of application traffic.

This mechanism allows operators to deploy advanced service offerings, such as zero-rating for specific apps, parental controls, or enterprise service plans, without overwhelming the core network with signaling. It also supports compliance with regulatory requirements for traffic management. By providing a standardized way to handle aggregated application reports, the ARA facilitates interoperability between different vendor equipment for TDF and PCRF, promoting a multi-vendor ecosystem and enabling consistent policy enforcement across the network.

Classification

Part ofTDF

Detected Changes Across Releases

from 3GPP Change Requests

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

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

Rel-17 1 change

In Release 17, the ARA function was newly introduced to enable PCRF control of MPS for DTS, as indicated by the Change Request title. This addition operates within the established Policy and Charging Control (PCC) framework where the PCRF manages sessions via the Gx interface. The specific procedural details for this control are integrated into the existing PCRF mechanisms for session and policy management.

  • PCRF control of MPS for DTS TS 29.213CR0743
Rel-19 1 change

In Release 19, the enhancement to the Aggregated RUCI Report Answer (ARA) function introduced a new condition for the PCRF to detect a PCEF failure in a timely manner. This addition is part of the broader PCRF Failure and Restoration procedures, ensuring the PCRF can appropriately handle scenarios where the PCEF becomes unavailable. The update specifically defines how the PCRF should react within the established Gx session framework when such a failure condition is met.

  • Add a new condition for the PCRF detecting PCEF failure in time TS 29.213CR0751

Explore further

Broader topics and technologies where ARA plays a role.

Defining Specifications

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

SpecificationTitleRelease
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