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

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-5, normative work from Rel-15.

Rel-15 27 changes

In Release 15, the ADC function was enhanced with new Policy Control Request triggers, including for RAT Type Change and Time Zone Change, and saw the introduction of procedures for QoS notification control. Corrections were made to the authorization for QoS notification control and to the application error codes. Furthermore, capabilities for reporting when PFDs are removed or modified were added for both the Application Function and the Traffic Detection Function.

  • Policy and Charging Control over Rx interface in the 5GS TS 29.214CR1609
  • Adding General information for Diameter Overload Control TS 32.299CR0803
  • Introduction of AVP for Overload Control TS 32.299CR0812
  • Policy control request trigger definition update TS 29.512CR0018
  • Correction to the AF influence traffic steering control TS 29.512CR0063
  • Correction to the QoS notification control authorization TS 29.512CR0071

+ 21 more changes

Rel-16 34 changes

In Release 16, the ADC function was enhanced with new policy control request triggers for wireline access and Time-Sensitive Networking (TSN), alongside specific support for applications with explicit QoS hints. It also introduced improved control for ATSSS, including usage monitoring and the inclusion of Application IDs within PCC rules. Furthermore, new procedures were defined for QoS monitoring control and for managing application reports when PFDs are modified or removed.

  • Support of applications with specific QoS hints TS 29.213CR0742
  • Support of applications with specific QoS hints TS 29.214CR1643
  • DN Authorization for Policy Control TS 29.512CR0222
  • Usage Monitoring Control for ATSSS TS 29.512CR0352
  • Correction to the QoS monitoring Control TS 29.512CR0384
  • Policy Control Request Triggers for wireline access TS 29.512CR0411

+ 28 more changes

Rel-17 26 changes

In Release 17, the ADC function was enhanced with new policy control request triggers, including location change (serving cell) and application detection for dynamic Access and Mobility policy changes. It also introduced controls for user plane inactivity detection and reporting over the N4mb interface, and extended policy control to cover specific scenarios like satellite access and 5G-LAN type services. Furthermore, corrections and clarifications were made to usage monitoring control and other policy control request triggers.

  • Support policy and QoS control for satellite access TS 29.212CR1707
  • PCRF control of MPS for DTS TS 29.213CR0743
  • AF Session for Control of MPS for DTS TS 29.214CR1654
  • User Plane (In)Activity Detection and Reporting over N4mb TS 29.244CR0608
  • Traffic steering control for 5G-LAN type of services TS 29.512CR0549
  • Satellite backhaul change policy control request trigger TS 29.512CR0681

+ 20 more changes

Rel-18 18 changes

In Release 18, the ADC function was enhanced with new controls for users with eRedcap/Redcap subscriptions and for managing group-related and maximum group data rate policies. It also introduced support for exposing application detection events and for policy control tailored to L4S (Low Latency, Low Loss, Scalable Throughput) requirements. Furthermore, the release included updates for user plane inactivity detection and clarifications for policy control request triggers and round-trip latency-based controls.

  • Access control for users with eRedcap/Redcap subscriptions TS 29.212CR1714
  • Access control for users with eRedcap/Redcap subscriptions TS 29.214CR1687
  • Generalization of QoS monitoring control description TS 29.244CR0723
  • User plane inactivity detection update TS 29.244CR0731
  • Group related data rate policy control TS 29.512CR1056
  • Applicability of the policy control request trigger for convergence scenario TS 29.512CR1060

+ 12 more changes

Rel-19 27 changes

In Release 19, the ADC function was enhanced to support a standalone Data Channel (DC), including procedures for network-initiated peer-to-peer application data channel establishment and ADC multiplexing at the IMS AS. It introduced specific handling for application data channel interworking via the DC AS for the originating UE and clarified procedures for application detection information reporting and the start or stop of an application instance.

  • Update session control and DC application related requirement to support the standalone DC TS 24.186CR0039
  • Procedure of network initiated P2P application data channel establishment TS 24.186CR0062
  • Procedure of application data channel interworking via DC AS for originating UE TS 24.186CR0065
  • 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
  • The requirement of the UE related to DC application in 8.1 TS 24.186CR0087

+ 21 more changes

Explore further

Broader topics and technologies where ADC plays a role.

Topics
MEC (Edge Computing)Policy & ChargingLawful InterceptSMS & MessagingManagement & OperationsServices & Applications

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