Application Detection and Control Decision

Description

The ADC decision is a fundamental concept in the 3GPP Policy and Charging Control (PCC) architecture, specifically within the Application Detection and Control (ADC) feature introduced in Release 11. It represents the information element that the Policy and Charging Rules Function (PCRF) provides to the Traffic Detection Function (TDF) to instruct it on how to detect and handle specific application traffic. The decision is not a rule itself but rather a container that references ADC rules, which are pre-provisioned in the TDF, along with associated enforcement actions for dynamic rules and TDF session attributes. This separation allows the PCRF to dynamically control application detection without having to define the detection logic itself, which is statically configured in the TDF.

Architecturally, the ADC decision is transmitted over the Sd interface (Gx variant for TDF) using Diameter protocol messages, specifically within Credit-Control-Answer (CCA) or Re-Auth-Request (RAR) messages. When a user session is established or modified, the PCRF evaluates subscriber policies and network conditions to determine which applications should be detected and how their traffic should be treated. It then constructs an ADC decision that includes references to one or more ADC rules by their identifiers. For dynamic ADC rules, the decision also carries the enforcement actions to be applied, such as gating, bandwidth limiting, or redirection. Additionally, the decision may include TDF session attributes that provide context for the session, such as the subscriber's IMSI or the APN. The TDF uses this decision to activate the referenced rules and apply the specified actions to the detected traffic.

The ADC decision plays a crucial role in enabling operators to implement fine-grained traffic management and monetization strategies. For example, an operator might use ADC decisions to detect and block peer-to-peer traffic, throttle video streaming during congestion, or apply zero-rating for specific applications. The decision-based approach allows for dynamic policy changes without requiring the TDF to be updated with new detection logic, as the PCRF can simply reference different pre-provisioned rules or provide new enforcement actions. This flexibility is essential in modern networks where application landscapes evolve rapidly.

Key components of an ADC decision include the ADC rule references, which are identifiers that map to pre-configured detection patterns in the TDF. These patterns can be based on various techniques such as IP address ranges, port numbers, protocol signatures, or deep packet inspection (DPI) heuristics. The enforcement actions for dynamic rules specify what the TDF should do when the application is detected, such as allowing, blocking, or shaping the traffic. TDF session attributes provide additional parameters that may influence detection or enforcement, such as the user's location or subscription tier. The decision is typically valid for the lifetime of the session or until a new decision is received, ensuring consistent policy application.

In terms of standardization, the ADC decision is defined in 3GPP TS 23.203 (Policy and charging control architecture) and TS 29.212 (Policy and Charging Control over Gx reference point). These specifications detail the structure, encoding, and procedures for ADC decisions. The concept has remained stable across releases from Rel-11 to Rel-19, with only minor editorial changes, indicating its maturity and continued relevance in both 4G and 5G networks. As networks evolve towards 5G, the ADC framework is being adapted to the Service-Based Architecture (SBA) with the PCF and NEF taking on similar roles, but the fundamental principles of decision-based application control persist.

Purpose & Motivation

The ADC decision was created to address the need for flexible, policy-driven application detection and control in mobile networks. Before its introduction, application detection was typically static and configured directly in gateways, lacking dynamic control from policy servers. This made it difficult for operators to adapt to changing application traffic patterns or to implement differentiated services based on real-time policy decisions. The ADC decision solves this by allowing the PCRF to dynamically instruct the TDF on which applications to detect and how to handle them, without requiring the TDF to have prior knowledge of all possible applications.

Historically, the rise of over-the-top (OTT) applications and the need for traffic management drove the development of ADC in 3GPP Release 11. Operators wanted to offer tiered services, enforce fair usage policies, and monetize specific applications, but existing PCC mechanisms were focused on IP flows rather than application awareness. The ADC decision provides a standardized way to convey application detection and enforcement instructions from the policy layer to the detection layer, enabling a clean separation of concerns. This separation allows the TDF to specialize in high-performance traffic detection while the PCRF handles policy logic, resulting in a scalable and maintainable architecture.

The ADC decision also addresses the limitation of static rule provisioning by supporting dynamic enforcement actions. While ADC rules themselves are pre-provisioned, the decision can include dynamic actions that tailor the enforcement to the current session context. This means that the same ADC rule can be used with different actions for different subscribers or network conditions, providing a high degree of flexibility. This capability is essential for implementing use cases such as temporary zero-rating during promotions or congestion-based throttling, where the enforcement needs to change without modifying the underlying detection rules.