Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

TDF

Traffic Detection Function

Core Network →

TDF is a network function that performs application detection, gating, and redirection for traffic to enable policy and charging control.

Introduced
Rel-11
Where
Core Network › Evolved Packet Core
Specifications
18 specs
Also in
Services, Management
TDF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Traffic Detection Function (TDF) is a specialized network element within the 3GPP Policy and Charging Control (PCC) architecture. Its primary role is to perform deep packet inspection (DPI) on user plane traffic to identify specific applications and services, such as streaming video, social media, or peer-to-peer applications. The TDF operates by analyzing packet headers and payloads against a set of pre-defined detection rules, which can be based on signatures, behavioral patterns, or other heuristics. Upon detecting a specific application, the TDF can report this information to the Policy and Charging Rules Function (PCRF) via the Sd reference point. The PCRF can then use this information to dynamically install or modify PCC rules in the Policy and Charging Enforcement Function (PCEF), enabling real-time policy enforcement like bandwidth throttling, blocking, or charging for the detected application flow.

Architecturally, the TDF can be deployed in two modes: as an Application Function (AF) within the PCC framework or as a standalone node. In the standalone deployment, it interacts directly with the PCRF. The TDF contains key functional components including the Traffic Detection Engine, which performs the actual DPI, and a reporting function that communicates with the PCRF. It also maintains a database of application detection rules, which can be updated by the operator. The TDF's operation is governed by ADC (Application Detection and Control) rules provisioned by the PCRF, which specify what applications to look for and what actions to take upon detection, such as reporting, gating (blocking), or redirecting the traffic.

In the network, the TDF is typically placed in the data path, often integrated with a Gateway GPRS Support Node (GGSN) or a Packet Data Network Gateway (PGW) in 4G, or the User Plane Function (UPF) in 5G. Its integration allows for granular, application-aware policy enforcement beyond simple bearer-level controls. For example, an operator can use the TDF to detect a video streaming service and apply a specific Quality of Service (QoS) policy to ensure a smooth user experience, or to identify and limit bandwidth for a file-sharing application during network congestion. The TDF's ability to provide application-level visibility is crucial for implementing service differentiation, zero-rating offers, and parental controls.

Purpose & Motivation

The TDF was created to address the growing need for operators to manage and monetize diverse internet application traffic beyond the capabilities of traditional bearer-level PCC. Prior to its introduction, policy control was primarily based on IP 5-tuple information (source/destination IP/port, protocol), which is insufficient for accurately identifying specific applications, especially those using dynamic ports, encryption, or sharing common servers. This limitation made it difficult for operators to implement fair usage policies, offer application-specific data plans, or ensure quality of experience for latency-sensitive services.

The motivation for standardizing the TDF in 3GPP Release 11 was to provide a unified, vendor-interoperable method for deep packet inspection and application-aware policy enforcement within the PCC framework. It solved the problem of application blindness in the core network, enabling new business models like sponsored data, where an application provider pays for the data usage, or tiered services where premium subscribers get better quality for specific apps. The TDF also provides the technical foundation for regulatory requirements, such as lawful interception of specific services or compliance with net neutrality rules through transparent traffic management.

Historically, operators relied on proprietary DPI solutions that were not integrated with the standardized PCC architecture, leading to operational complexity and limited scalability. The TDF standardizes the interfaces (e.g., Sd, Gx) and procedures for application detection and control, allowing operators to deploy multi-vendor solutions and ensuring that policy decisions based on application detection are consistent and enforceable across the network. It represents a key evolution from simple volume-based charging to intelligent, service-aware network management.

What changed in its specifications

The latest release-to-release comparison of specifications that define TDF. Each summary describes the whole specification, not only this term.

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 23.214Rel-14 → Rel-15

Rel-15 added a functional split between Radio and Core, incorporating UE capabilities including dual connectivity with NR support into PGW-U and SGW-U selection.

Full comparison in TS 23.214 →

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-11 introduced

The TDF is specified for the first time, performing application detection and reporting to the PCRF, with enforcement actions, usage monitoring and Sd-interface ADC rule handling.

  • “The TDF is a functional entity that performs application detection and reporting of detected application and its service data flow description to the PCRF.” TS 23.203 v11.15.0
  • “the TDF shall perform charging, gating, redirection and bandwidth limitation for the detected applications, as defined in the ADC rule” TS 23.203 v11.15.0
  • “the TDF shall initiate the TDF Session Establishment procedure with the PCRF.” TS 29.213 v11.16.0
Rel-12 specification text

TDF gained online charging and credit management with the OCS, plus time-based usage monitoring with thresholds and reporting to the PCRF, alongside volume-based monitoring.

  • “The PCEF/TDF shall request a credit for each charging key occurring in a PCC/ADC rule.” TS 23.203 v12.11.0
  • “The TDF shall be able to support volume and time measurements simultaneously for a given application(s).” TS 29.212 v12.14.0
  • “For the solicited application reporting, the TDF shall support application based charging by having online and offline charging interactions.” TS 29.212 v12.14.0
Rel-13 1 CR

Rel-13 extends TDF with traffic steering policy enforcement in the (S)Gi-LAN, DSCP marking of downlink traffic, and exclusion of applications from TDF session-level usage monitoring.

  • “When the PCRF provides a Traffic Steering Policy Identifier(s) in an ADC rule, the TDF shall enforce the referenced traffic steering policy for the application.” TS 23.203 v13.10.0
  • “The TDF shall be able to mark detected downlink application traffic with a DSCP value received within an installed ADC Rule matching this traffic.” TS 23.203 v13.10.0
  • TDF support for downlink's bearer selection and bearer binding procedures TS 23.203CR0953
Rel-14 1 CR

Rel-14 extends the TDF with sponsored data connectivity support, PFD retrieval from the PFDF, encrypted traffic detection, and removes Presence Reporting Area and AULC handling for the TDF.

  • “This feature indicates support for sponsored data connectivity feature. If the TDF supports this feature, the PCRF may authorize sponsored data connectivity to the subscriber.” TS 29.212 v14.11.0
  • Management of PFDs to PCEF/TDF TS 23.203CR1036
  • “PCEF/TDF shall fetch from the PFDF the PFDs for the Application Identifier(s) by sending Fetch PFD Request” TS 23.203 v14.6.0
Rel-15 1 CR

TDF QoS enforcement for ADC rules and TDF sessions was extended to also allow Extended-Max-Requested-BW AVPs, and TDF charging and application reporting behaviour was enhanced.

  • “If QoS-Information is provided for an ADC rule, the TDF shall enforce the corresponding policy for the detected application's traffic.” TS 29.212 v15.9.0
  • “When the TDF session is being established in solicited mode and if the PCRF supports the Extended-BW-NR feature” TS 29.212 v15.9.0
  • Charging enhancement on TDF for eFMSS TS 32.251CR0501
Rel-16 specification text

For dynamic ADC rules with flow information for both UE IPv4 address and IPv6 prefix for the same application identifier, two Redirect-Information AVPs may be provided when ADC-Add-Redirection is supported.

  • “If a dynamic ADC rule includes flow informations for UE IPv4 address and IPv6 prefix address related to the same application identifier” TS 29.212 v16.4.0
  • “if ADC-Add-Redirection feature is supported, two Redirect-Information AVPs may be pr” TS 29.212 v16.4.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.139 vj00 3GPP-Fixed Broadband Interworking Stage 2 Rel-19 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.214 vj00 Control and User Plane Separation for EPC Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.250 vj00 Nu Reference Point Stage 3 Specification Rel-19 read
TS 29.251 vj00 Gw/Gwn Reference Points Stage 3 Specification Rel-19 read
TS 29.810 vd00 Diameter Load Control Study Rel-13 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 32.843 vd00 Inter-PLMN Online Charging for Roaming Rel-13 read
TS 32.869 vf00 Diameter Overload Control for Charging Interfaces Rel-15 read