ARA

Aggregated RUCI Report Answer

Management
Introduced in Rel-13
ARA is a management protocol message defined in 3GPP for Policy and Charging Control (PCC). It is a response from the Policy and Charging Rules Function (PCRF) to the Traffic Detection Function (TDF), confirming the aggregated reporting of user plane traffic events. This enables efficient policy enforcement and charging based on application detection and usage.

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.

Key Features

  • Diameter-based protocol message on the Sd interface
  • Response to Aggregated RUCI Report Request (ARR) from TDF
  • Enables acknowledgment of aggregated application event reports
  • Supports dynamic policy updates from PCRF to TDF
  • Reduces signaling overhead via event aggregation
  • Integral part of 3GPP Application Detection and Control (ADC) feature

Evolution Across Releases

Rel-13 Initial

Introduced the ARA as part of the new Application Detection and Control (ADC) feature. It defined the initial architecture where the TDF sends aggregated application usage reports (ARR) to the PCRF, and the PCRF responds with the ARA for acknowledgment and policy feedback. This enabled efficient, application-aware policy enforcement without excessive signaling.

Defining Specifications

SpecificationTitle
TS 29.213 3GPP TS 29.213
TS 29.217 3GPP TS 29.217