ADC

Application Detection and Control

Services →
Introduced in Rel-5 Also in: Services, User Equipment, Radio Access Network

ADC is a network function that identifies specific applications or traffic types and applies policy-based controls to manage resources, implement charging, and ensure quality of service.

Category
Services
Introduced
Rel-5
Where
Core Network › 5G Core
Also touches
3 segments
Specifications
24 specs
ADC Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofPCRF
Related approachesPCEF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change

In Release 15, the standardization of the Application Detection and Control (ADC) function was advanced through the introduction of Predefined Rules for PCC and ADC. These Predefined Rules provide a standardized framework for network operators to implement consistent application detection and policy control. This allows for the deployment of ADC functionality based on common, pre-configured rule sets.

  • Predefined Rules PCC/ADC Rules TS 29.244CR0148
Rel-16 1 change

In Release 16, the primary change to the Application Detection and Control (ADC) function was a correction. This indicates that the work focused on rectifying errors or clarifying ambiguities present in the initial Release 16 specifications, rather than introducing new procedures or capabilities. The update aimed to ensure the ADC function's technical documentation was accurate and unambiguous for implementation.

Rel-17 2 changes

In Release 17, the work on the Application Detection and Control (ADC) function focused on making corrections to the feature's specification. This included addressing an update related to the mute indication procedure, which was ultimately rejected and not included in the standard. Therefore, the primary outcome was the correction and stabilization of existing ADC functionality rather than the introduction of new capabilities.

  • Rejection of the update of mute indication for ADC TS 29.512CR0966
  • Corrections to Application Detection and Control TS 29.512CR0911
Rel-19 4 changes

In Release 19, the ADC function was enhanced to address specific operational procedures and correct handling details. The new work included defining the procedure for ADC multiplexing at the IMS Application Server and solving the scenario for closing ADC during DC (Dual Connectivity) multiplexing. Furthermore, corrections were made to the description and setup handling of Session Description Protocol (SDP) for ADC.

  • Solve the EN on closing ADC in the case of DC multiplexing TS 24.186CR0075
  • Procedure of ADC multiplexing at IMS AS TS 24.186CR0079
  • Correction on the description of SDP handling for ADC TS 24.186CR0055
  • Correction on the SDP handling for ADC setup TS 24.186CR0037

Explore further

Broader topics and technologies where ADC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 24.186 vj60 IMS Data Channel applications Rel-19
TS 26.110 vj00 3G-324M Multimedia Codecs for Circuit Switched Networks Rel-19
TS 26.115 vj00 3GPP TS 26115: Echo Control Requirements Rel-19
TS 26.131 vj00 Terminal Acoustic Performance Requirements Rel-19
TS 26.132 vj00 Terminal Acoustic Test Methods Rel-19
TS 26.264 vj20 IMS-based AR Real-Time Communication Rel-19
TR 26.933 vj00 Study on Diverse Audio Capturing System Rel-19
TS 29.212 vj00 Gx/Gxx/Sd/St Diameter Protocol Rel-19
TS 29.213 vj20 PCC Signalling Flows and QoS Mapping Rel-19
TS 29.214 vj20 Policy and Charging Control over Rx Rel-19
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.512 vj40 5G Session Management Policy Control Service Rel-19
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19
TS 33.790 vj10 Security for Next-Gen Real-Time Communication Phase 2 Rel-19
TS 38.774 vj00 Rel-19 LP-WUS/WUR RF Requirements TR Rel-19
TS 38.831 vg10 UE RF Requirements for FR2 Enhancements Rel-16
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18
TR 38.877 vi10 Technical Report Rel-18
TS 43.050 vj00 GSM Transmission Planning for Speech Services Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.