Description
The Traffic Flow Template (TFT) is a core policy and traffic management construct in 3GPP packet core networks, including GPRS, UMTS, and Evolved Packet System (EPS). It operates at the Gateway GPRS Support Node (GGSN) in UMTS or the Packet Data Network Gateway (P-GW) in EPS. A TFT is essentially a collection of up to eight packet filters (in the downlink direction) that are installed as part of a PDP context (UMTS) or PDN connection/EPS bearer (EPS). Each packet filter contains matching criteria such as source/destination IP addresses and port numbers, protocol type (e.g., TCP/UDP), IPsec Security Parameter Index (SPI), and Type of Service (TOS) field bits.
Architecturally, the TFT is created by the UE or the network (via the Policy and Charging Rules Function - PCRF) and is signaled to the gateway node (GGSN/P-GW) during PDP context activation or modification procedures. In the downlink, when a packet arrives from the external packet data network (e.g., the internet), the GGSN/P-GW performs packet classification by evaluating the packet header against all active TFT filters associated with the user's PDP contexts. The packet is then directed to the specific PDP context (and its associated radio bearer) whose TFT contains the matching filter. This creates a binding between an IP flow (e.g., a VoIP call, a video stream) and a specific bearer that has the requisite Quality of Service (QoS) characteristics (e.g., guaranteed bit rate, priority).
Its role is critical for enabling multiple simultaneous services with different QoS requirements over a single user's IP address. For example, a user can have a default bearer for best-effort internet browsing and a dedicated bearer with a TFT matching their VoIP traffic to ensure low latency and jitter. The TFT mechanism allows the network to apply distinct QoS policies, charging rules, and even routing treatments (like offload to a local breakout) on a per-service-flow basis. In the uplink direction, the UE uses the TFT packet filters to map its own outgoing IP traffic to the correct bearer. The TFT is thus the fundamental tool for implementing flow-based QoS and policy control in 3GPP networks.
Purpose & Motivation
The TFT was introduced to solve the problem of supporting multiple IP-based services, each with distinct Quality of Service (QoS) needs, within a single Packet Data Protocol (PDP) context that traditionally had only one IP address and one set of QoS parameters. Early GPRS/UMTS data services primarily offered a single 'pipe' for all traffic, which was insufficient for real-time services like Voice over IP (VoIP) or video conferencing that require guaranteed bandwidth and low delay amidst other background traffic.
The creation of the TFT, standardized from Release 99 onwards, was motivated by the vision of All-IP networks and multimedia services. It enables the network to identify and differentiate between individual traffic flows (e.g., separate TCP connections for email, web, and a VoIP stream) originating from the same user equipment. By classifying packets into flows, the network can then map each flow to a dedicated bearer with optimized QoS characteristics, a process essential for the 3GPP's standardized QoS architecture. This addressed the limitations of the earlier, service-agnostic 'best-effort' data pipe, allowing operators to offer tiered services, implement sophisticated charging models (e.g., different rates for video vs. chat), and ensure a consistent user experience for latency-sensitive applications.
What changed in its specifications
The latest release-to-release comparison of specifications that define TFT. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.060 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
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 sourcesDocumented changes in 17 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.
TFT is specified for the first time: packet filters sent with secondary PDP context activation, modification and deletion, used by the GGSN to classify downlink packets, with TFT-specific error causes.
- “The TFT contains attributes that specify an IP header filter that is used to direct data packets received from the interconnected external packet data network” TS 23.060 v3.17.0
- “TFT is sent transparently through the SGSN to the GGSN to enable packet classification for downlink data transfer.” TS 23.060 v3.17.0
- “# 46: PDP context without TFT already activated;” TS 24.008 v3.20.0
TFT handling in 24008 was corrected, covering abnormal cases, maximum TFT IE length, and its presence in Activate Secondary PDP Context Request; 23060 also removed text on the GGSN removing the TFT on GTP v0 updates.
- “Abnormal cases for TFT handling, TFT IE maximum length” TS 24.008 v4.17.0
- “Presence of TFT IE in Activate Secondary PDP Context Request” TS 24.008 v4.17.0
- “the GGSN shall remove the TFT if present when it receives the GTP v0 Update PDP Context Request message” TS 23.060 v4.11.0
Rel-5 extends the TFT IE with a new 'No TFT operation' code, a parameters list carrying Authorization Tokens for IMS, and revised error conditions and packet filter list rules.
- “In addition, this information element may be used to transfer extra parameters to the network (e.g. the Authorization Token; see 3GPP TS 24.229).” TS 24.008 v5.16.0
- “The TFT operation code "No TFT operation" shall be used if a parameters list is included but no packet filter list is included” TS 24.008 v5.16.0
- “Upgrading TFT for supporting IMS services” TS 24.008 v5.16.0
TFT handling was extended: secondary PDP contexts may be activated without a TFT, at most one context per PDP address/APN pair has no TFT, and TFT error checks and precedence rules now cover the APN and more operations.
- “Among the PDP contexts that share the same PDP address and APN pair there shall be a maximum of one PDP context without an associated TFT.” TS 23.060 v6.15.0
- “When the TFT operation = "Create a new TFT" or "Add packet filters to existing TFT" or "Replace packet filters in existing TFT"” TS 24.008 v6.20.0
- “after successful deletion of the TFT, deactivate the old PDP context with the same PDP address and APN without a TFT” TS 24.008 v6.20.0
In Rel-7, TFT handling was extended with a Bearer Control Mode ('MS only' or 'MS/NW') so the network can also create, modify and delete TFTs and network-initiated secondary PDP context activation can carry a TFT.
- “The message contains the required QoS, Linked TI, and optionally protocol configuration options and a TFT.” TS 24.008 v7.15.0
- “Depending on the selected Bearer Control Mode, the MS or the network may also create and delete a TFT in an active PDP context.” TS 24.008 v7.15.0
- “Only the entity that sets a packet filter in the TFT (either MS or GGSN) is allowed to modify or delete this packet filter.” TS 23.060 v7.11.0
TFT handling was extended for EPS interworking: default PDP contexts may lack a TFT, TFTs carry packet filter identifiers, and the 23.060 modification rules now cover the P-GW as well as the GGSN.
- “The MS shall, when modifying the QoS of a PDP context, include a TFT with at least packet filter identifiers” TS 23.060 v8.17.0
- “If the BCM is MS/NW, the TFT shall contain packet filter identifiers and PDN GW shall include the SDF filter identifier(s)” TS 23.060 v8.17.0
- “The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer if the TFT contains packet filters for the uplink direction.” TS 24.301 v8.10.0
TFT handling was extended: UE may now add packet filters to an existing TFT in bearer modification requests, with new network handling of that operation code and new TFT-related error handling.
- “the UE shall set the TFT operation code in the Traffic flow aggregate IE to "Replace packet filters in existing TFT" or "Add packet filters to existing TFT"” TS 24.301 v9.11.0
- “the network shall process the new request as a request with TFT operation = "Create a new TFT".” TS 24.301 v9.11.0
- TFT related error handling TS 29.274CR0423
TFT handling was changed: MS/NW-mode uplink filter evaluation and the requirement that a TFT include an uplink packet filter for downlink-only services were added, along with a related TFT-check procedure in the UE.
- “If the PDP context is to be used for services having downlink IP flows only, then the TFT needs to include a packet filter for the uplink direction” TS 23.060 v10.14.0
- “Correction on existence of uplink packet filter in TFT” TS 23.060 v10.14.0
- “only for the PDP context(s) that have a TFT that includes packet filter(s) set by the MS, the PDP context may be preserved” TS 23.060 v10.14.0
In Rel-11 the TFT rules changed: the network must always include a TFT in secondary PDP context activation, the MS must include an uplink packet filter, and an extended TFT filter format was added.
- “The network shall always include a TFT in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message.” TS 24.008 v11.17.1
- “The MS shall include a request for a TFT comprising at least one packet filter applicable for the uplink direction.” TS 24.008 v11.17.1
- “The MS indicates support of the extended TFT filter format through the Extended TFT Support UE (ETFTU) parameter” TS 23.060 v11.12.0
TFT handling was changed in Rel-12: TFT error checks for secondary PDP context activation were extended (e.g. precedence-value conflicts across TFTs) and TFT modification rejection cases were added, with CRs correcting TFT packet filter descriptions.
- “2) When the TFT operation is "Create a new TFT" and two or more packet filters in all TFTs associated with this PDP address and APN” TS 24.008 v12.15.0
- “If a TFT modification was requested and the MS requests to modify or delete packet filters which were added by the network” TS 24.008 v12.15.0
- Definition for a valid state of the TFT setting TS 23.060CR1801
Rel-13 changed TFT behaviour: a new 'Ignore this IE' TFT operation code, abnormal-case handling of TFT on PDP context modification timer expiry, and TFT handling clarifications and requirements for secondary PDP contexts.
- “The TFT operation code "Ignore this IE" shall be used by the MS if the Traffic flow aggregate information element has presence requirement "M"” TS 24.008 v13.13.0
- “on the fifth expiry of timer T3381, the MS may continue to use the previously negotiated QoS and TFT” TS 24.008 v13.13.0
- Requiring to always have TFT in Secondary PDP context for E-UTRAN capable device TS 23.060CR1924
TFT handling was changed in Rel-14: the TFT operation code value "0" was defined in the traffic flow template IE, and TFT operation rules were added for header compression re-negotiation and PS data off.
- Definition of value "0" of the TFT operation code in the traffic flow template IE TS 24.008CR3026
- “TFT operation for header compression re-negotiation and PS data off” TS 24.301 v14.10.0
The UE must now check TFT IEs in mapped EPS bearer contexts for semantic and syntactical errors and react, e.g. by requesting deletion of the mapped EPS bearer context with 5GSM cause #41.
- “the UE shall check the traffic flow template for different types of TFT IE errors as specified in subclause 6.3.2.3.” TS 24.501 v15.7.0
- “the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context” TS 24.501 v15.7.0
- TFT checking and error handling in WLCP bearer setup and modify procedures TS 24.244CR0051
TFT error handling was corrected by removing invalid cases, and a Local address in TFT capability was added and negotiated for 5GS-EPS interworking.
- “0011H (MS support of Local address in TFT indicator) (see NOTE 4);” TS 24.008 v16.7.0
- “When the TFT operation = "Create a new TFT", "Add packet filters to existing TFT", or "Replace packet filters in existing TFT"” TS 24.301 v16.9.0
- Remove invalid cases in error handling for TFT operation in EPS TS 24.301CR3350
The TFT IE size note was corrected to 36-byte IPv4 and 54-byte IPv6 maximum packet filters, and TFT checks and local IP address handling in TFT were corrected.
- “A maximum size IPv4 packet filter can be 36 bytes. Therefore, 7 maximum size IPv4 type packet filters can fit into one TFT IE” TS 24.008 v17.9.0
- Correction on the number of the maximum size packet filters in TFT TS 24.008CR3267
- Correction to TFT check for PDU session establishment procedure TS 24.501CR4388
TFT handling was corrected in Rel-18: empty packet filter list handling in 3G and 4G, 'No TFT operation' for default bearers, and TFT semantic and syntactic error checks in 5GS.
TFT IE and TFT operation handling were corrected: the packet filter list must be empty for the 'Ignore this IE' operation, and the error-case rules now cover 'Add' and 'Replace' packet filter operations.
- “For the "Ignore this IE" operation, the "delete existing TFT" operation and the "no TFT operation", operation, the packet filter list shall be empty.” TS 24.008 v19.5.0
- “In case 2, if the TFT operation is "Replace packet filters in existing TFT" or "Add packet filters to existing TFT", the network shall process the new request as a request with TFT operation = "Create new TFT".” TS 24.301 v19.8.0
- Correction to the TFT IE TS 24.008CR3346
Defining Specifications
3GPP specifications that define or reference TFT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 read |
| TS 23.802 v700 | Enhanced End-to-End QoS Architecture | Rel-7 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 read |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 read |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 read |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 read |
| TS 29.274 vk00 | GTPv2-C Control Plane Protocol | Rel-20 read |
| TS 34.109 vj00 | UE Conformance Test Functions for UMTS | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 read |