Description
Application Detection and Control (ADC) is a sophisticated network capability defined within the 3GPP Policy and Charging Control (PCC) architecture. Its primary function is to perform deep packet inspection (DPI) or use other detection methods to identify the specific application or traffic type associated with a user's data session. Once an application is detected, ADC works in conjunction with the Policy and Charging Rules Function (PCRF) to enforce dynamic policy rules. These rules can govern Quality of Service (QoS) parameters, such as allocating guaranteed bitrate for a video streaming service or applying traffic shaping to peer-to-peer file sharing. ADC also provides critical input for charging functions, enabling application-aware billing models like zero-rating for specific apps or volume-based charging tiers.
The architectural implementation of ADC is typically integrated with the Traffic Detection Function (TDF) or the PCEF (Policy and Charging Enforcement Function) in the user plane. The PCRF, residing in the control plane, provisions detection and control rules to the TDF/PCEF via the Gx or Sd reference points. The detection mechanisms can be signature-based, analyzing packet headers and payloads, or use behavioral analysis, machine learning, and collaboration with application servers. Upon detecting a designated application, the enforcement point can trigger actions like redirecting traffic, blocking it, modifying its priority, or generating specific charging data records (CDRs) for offline billing systems.
Key components involved in ADC include the TDF, which is a dedicated node for application detection, and the PCEF, often colocated with the Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway (PGW). The PCRF acts as the brain, deciding which policies to apply based on the detected application, subscriber profile, and network conditions. The Online Charging System (OCS) and Offline Charging System (OFCS) receive application-specific usage reports for real-time credit control and post-processing billing, respectively. This integrated system allows for granular, real-time control over network traffic at the application layer.
ADC's role extends beyond simple traffic management. It is fundamental to implementing service differentiation strategies, such as creating "service passes" for social media or gaming. It supports parental controls by blocking inappropriate content and enables enterprise services by guaranteeing performance for business applications. In modern networks, ADC is essential for managing the explosion of diverse traffic from Over-the-Top (OTT) applications, ensuring that critical services receive necessary resources while optimizing overall network efficiency and enabling new revenue streams for operators.
Purpose & Motivation
ADC was created to address the fundamental challenge of the "dumb pipe" phenomenon, where mobile network operators risked becoming mere connectivity providers without the ability to differentiate or monetize the vast array of applications flowing over their infrastructure. Prior to ADC, policy control was largely based on static subscriber profiles or Access Point Name (APN) settings, offering little to no granularity based on the actual application being used. This made it impossible to offer innovative service plans, guarantee performance for latency-sensitive apps like VoIP, or manage network congestion caused by specific high-bandwidth applications.
The introduction of ADC, starting in 3GPP Release 5 within the broader PCC framework, empowered operators to move from a one-size-fits-all data service to an intelligent, application-aware network. It solved the problem of network resource contention by allowing operators to identify and control traffic at the application layer. This enabled fair usage policies, the creation of tiered service offerings (e.g., "Social Media Pack"), and the technical foundation for sponsored data or zero-rating, where specific application traffic does not count against a user's data allowance. Furthermore, ADC provided the tools for regulatory compliance, such as implementing lawful interception triggers based on application use.
Key Features
- Deep Packet Inspection (DPI) for application signature detection
- Dynamic policy enforcement based on real-time application identification
- Integration with PCC architecture via Gx and Sd interfaces
- Support for application-aware charging and billing models
- Traffic optimization through gating, redirection, and bandwidth management
- Generation of application-specific usage records for charging (CDRs)
Evolution Across Releases
Introduced the foundational Policy and Charging Control (PCC) architecture, establishing the core framework for application-aware policy. While not explicitly named "ADC" yet, this release defined the PCEF and PCRF functions, enabling basic service data flow detection and policy enforcement based on static rules, laying the groundwork for future application-specific control.
Enhanced PCC with the introduction of the Spending Limit Reporting function, allowing for more dynamic charging control. This release strengthened the linkage between policy decisions and charging, a critical enabler for the monetization aspects of ADC, such as notifying users or applying policies when they approach data caps for specific applications.
Formally introduced the standalone Traffic Detection Function (TDF) and the Sd reference point between the PCRF and TDF. This was a major evolution for ADC, decoupling deep packet inspection and application detection from the gateway (PCEF), allowing for more flexible, scalable, and centralized application detection and control across the network.
Integrated ADC principles into the 5G System (5GS) architecture. The functions evolved into the Session Management Function (SMF) with PCF (Policy Control Function) guidance and the new Network Data Analytics Function (NWDAF) for enhanced application and traffic pattern analytics. This enabled more intelligent, data-driven ADC policies in 5G cores.
Further enhanced application detection capabilities for 5G-Advanced, focusing on support for new immersive services (e.g., XR), network slicing, and edge computing scenarios. Improvements likely include more efficient detection algorithms for encrypted traffic and tighter integration with AI/ML for predictive policy enforcement.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.203 | 3GPP TS 23.203 |
| TS 24.186 | 3GPP TS 24.186 |
| TS 26.110 | 3GPP TS 26.110 |
| TS 26.115 | 3GPP TS 26.115 |
| TS 26.131 | 3GPP TS 26.131 |
| TS 26.132 | 3GPP TS 26.132 |
| TS 26.264 | 3GPP TS 26.264 |
| TS 26.933 | 3GPP TS 26.933 |
| TS 29.212 | 3GPP TS 29.212 |
| TS 29.213 | 3GPP TS 29.213 |
| TS 29.214 | 3GPP TS 29.214 |
| TS 29.215 | 3GPP TS 29.215 |
| TS 29.244 | 3GPP TS 29.244 |
| TS 29.512 | 3GPP TS 29.512 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.298 | 3GPP TR 32.298 |
| TS 32.299 | 3GPP TR 32.299 |
| TS 33.790 | 3GPP TR 33.790 |
| TS 38.774 | 3GPP TR 38.774 |
| TS 38.831 | 3GPP TR 38.831 |
| TS 38.869 | 3GPP TR 38.869 |
| TS 38.877 | 3GPP TR 38.877 |
| TS 43.050 | 3GPP TR 43.050 |