Traffic Specification

Description

Traffic Specification (TSPEC) is a fundamental concept in 3GPP Quality of Service (QoS) architecture, defining the characteristics and requirements of a bearer or data flow. It consists of a standardized set of parameters that describe the traffic profile from the source and the QoS expectations from the network. Key parameters typically include the Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), Packet Delay Budget (PDB), Packet Error Loss Rate (PELR), and optionally, traffic shaping parameters like burst size. The TSPEC is generated by the application or the terminal and is communicated to the network during bearer establishment or modification procedures, such as the Packet Data Protocol (PDP) context activation in UMTS or the PDU Session Establishment in 5G.

Architecturally, the TSPEC is processed by multiple network functions. In the control plane, the Policy and Charging Rules Function (PCRF) in 4G or the Policy Control Function (PCF) in 5G receives the TSPEC (often via the Application Function) and uses it to derive policy decisions. These decisions are then enforced by the Packet Gateway (PGW) or Session Management Function (SMF), which instructs the radio access network (RAN) and user plane nodes to allocate resources accordingly. The RAN uses the TSPEC for scheduling, admission control, and link layer configuration to meet the specified PDB and PELR.

In operation, when a user equipment (UE) requests a service, the associated TSPEC is evaluated against network policies and available resources. The network performs admission control to determine if it can support the requested flow without degrading existing services. If accepted, the network configures queue management, scheduling algorithms, and radio bearers to comply with the TSPEC. For GBR flows, dedicated network resources are reserved, while for Non-GBR flows, resources are shared statistically. The TSPEC enables the network to treat different types of traffic (e.g., voice, video, background) appropriately, ensuring that latency-sensitive applications receive priority over best-effort data.

Purpose & Motivation

TSPEC was created to enable differentiated QoS in packet-switched mobile networks, addressing the limitation of early data services that offered only uniform, best-effort delivery. As mobile networks evolved to support diverse applications like VoIP, streaming video, and real-time gaming, each with unique bandwidth, latency, and reliability needs, a mechanism was required to communicate these requirements to the network for proper resource handling.

The introduction of TSPEC in UMTS Release 99 solved this by providing a standardized way to specify traffic demands. It allowed the network to implement intelligent admission control and resource management, preventing congestion and ensuring predictable performance for premium services. This was a significant shift from the one-size-fits-all approach, enabling operators to offer tiered services and monetize QoS. Over releases, TSPEC has evolved to support more complex scenarios like network slicing and edge computing, maintaining its role as the core descriptor for QoS flows.

Key Features

• Defines quantitative traffic parameters (GBR, MBR, PDB, PELR)
• Used for network admission control and resource reservation
• Enables differentiated treatment of data flows based on service requirements
• Standardized across 3GPP systems (UMTS, LTE, 5G)
• Integrates with policy control (PCRF/PCF) for dynamic QoS management
• Supports both Guaranteed Bit Rate and Non-Guaranteed Bit Rate flows

Evolution Across Releases

Defining Specifications