Application Detection and Control Rule

Description

The ADC rule is a core building block of the Application Detection and Control (ADC) framework in 3GPP Policy and Charging Control (PCC). It is a static configuration in the Traffic Detection Function (TDF) that contains the logic to identify a particular application's traffic and the actions to take upon detection. Unlike dynamic rules that are provided in real-time, ADC rules are provisioned directly into the TDF by the operator, typically through management interfaces. The PCRF then references these rules by their identifiers in ADC decisions to activate them for specific sessions. This design allows the TDF to perform high-speed detection using optimized patterns while the PCRF maintains centralized policy control.

An ADC rule consists of several key elements: a rule identifier, application detection information, and enforcement actions. The rule identifier is a unique string that the PCRF uses to reference the rule. The application detection information specifies how to detect the application, which can include IP address ranges, port numbers, protocol types, domain names, or deep packet inspection (DPI) signatures. The enforcement actions define what the TDF should do when the application is detected, such as allowing, blocking, shaping, or redirecting the traffic. These actions can be static (part of the rule) or dynamic (provided in the ADC decision). The rule may also include a precedence value to resolve conflicts when multiple rules match the same traffic.

In operation, the TDF receives ADC decisions from the PCRF over the Sd interface. When a decision references an ADC rule, the TDF activates that rule for the session. As traffic flows through the TDF, it inspects packets against the active rules. When a match is found, the TDF applies the enforcement actions and may report the detection to the PCRF via a Credit-Control-Request (CCR) message. This reporting enables the PCRF to make further policy decisions, such as charging or notifying other network functions. The TDF can handle multiple rules simultaneously, and the precedence ensures that the most specific or highest-priority rule is applied.

The ADC rule concept was introduced in 3GPP Release 11 as part of the broader ADC feature. It is defined in TS 23.203 (Policy and charging control architecture) and TS 29.212 (Policy and Charging Control over Gx reference point). The specifications detail the structure, encoding, and procedures for ADC rules. The definition has remained stable across releases from Rel-11 to Rel-19, with only minor editorial changes, reflecting its maturity and continued relevance. In 5G networks, similar functionality is provided by the PCF and the NEF, but the fundamental principles of pre-provisioned detection rules referenced by policy decisions persist.

Key advantages of ADC rules include their efficiency and scalability. By pre-provisioning detection logic in the TDF, operators avoid the overhead of transmitting complex detection patterns over signaling interfaces for every session. The PCRF only needs to send lightweight references, reducing signaling load and latency. Additionally, the separation of detection and policy allows the TDF to be optimized for high-throughput packet inspection, while the PCRF focuses on policy logic. This modularity is essential for handling the increasing volume and variety of application traffic in modern mobile networks.

Purpose & Motivation

The ADC rule was created to provide a standardized, efficient mechanism for application detection and control in mobile networks. Prior to its introduction, application detection was often implemented in an ad-hoc manner within gateways, lacking a unified framework for policy control. Operators struggled to dynamically manage application traffic because detection logic was tightly coupled with enforcement, making it difficult to update or customize per subscriber. The ADC rule solves this by separating the detection logic (pre-provisioned in the TDF) from the enforcement policy (controlled by the PCRF), enabling flexible and scalable application-aware policy control.

Historically, the proliferation of over-the-top (OTT) applications and the need for differentiated services drove the development of ADC in 3GPP Release 11. Operators wanted to offer tiered data plans, enforce fair usage policies, and monetize specific applications, but existing PCC mechanisms were flow-based and lacked application awareness. The ADC rule provides a way to define application detection patterns once and reuse them across many sessions, while allowing the PCRF to apply different enforcement actions based on subscriber profiles or network conditions. This separation of concerns is a key enabler for advanced traffic management and monetization strategies.

The ADC rule also addresses the limitation of static enforcement by allowing dynamic actions to be specified in ADC decisions. While the detection logic is static, the enforcement can be tailored per session, providing a balance between efficiency and flexibility. This means that the same ADC rule can be used to block traffic for one subscriber and throttle it for another, depending on the policy decision. This capability is essential for implementing use cases such as parental controls, zero-rating, and congestion management, where the enforcement needs to vary without changing the underlying detection rules.