Glossary term · Services

ADC

Application Detection and Control

Services →

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.

Introduced
Rel-5
Where
Core Network › 5G Core
Specifications
24 specs
Also in
Services, User Equipment, Radio Access Network
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 (9 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change
  • Predefined Rules PCC/ADC Rules TS 29.244CR0148
Rel-16 1 change
Rel-17 2 changes
  • Rejection of the update of mute indication for ADC TS 29.512CR0966
  • Corrections to Application Detection and Control TS 29.512CR0911
Rel-19 5 changes
  • 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
  • ADC App download indication correction TS 24.186CR0118
  • 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 vj20 3GPP Terminology and Definitions Rel-19
TS 23.203 vk00 Policy and Charging Control Architecture Rel-20
TS 24.186 vk00 IMS Multimedia Telephony Communication Services with IMS Data Channel Rel-20
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 vk00 Terminal Acoustic Test Methods for Telephony Rel-20
TS 26.264 vj30 IMS-based Conversational AR Services Rel-19
TR 26.933 vj00 Study on Diverse Audio Capturing System Rel-19
TS 29.212 vj10 Diameter-based Gx, Gxx, Sd, St Interfaces Rel-19
TS 29.213 vj30 PCC Procedures and Flows Rel-19
TS 29.214 vj30 Rx Reference Point Stage 3 Specification Rel-19
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19
TS 29.244 vk00 Packet Forwarding Control Protocol (PFCP) Specification Rel-20
TS 29.512 vk00 Session Management Policy Control Service Rel-20
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 32.298 vk00 Charging Data Record Parameter Description Rel-20
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 vj20 RF Requirements for Low-Power Wake-up Signal and Receiver 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