Packet Delay Budget

Description

The Packet Delay Budget (PDB) is a fundamental Quality of Service (QoS) parameter in the 5G System (5GS), defined in 3GPP TS 23.501. It specifies the maximum allowable end-to-end packet delay for a QoS Flow, measured from the UE to the User Plane Function (UPF) that terminates the N6 interface (towards the Data Network), or vice-versa. The PDB is not a guaranteed delay but a target used by the network's packet scheduling and resource management functions. It is intrinsically linked to a standardized 5G QoS Identifier (5QI), where each 5QI value has a default PDB (and Packet Error Rate) assigned, as per Annex A of TS 23.501.

Operationally, the PDB influences decisions across the RAN and core network. In the Radio Access Network (RAN), the gNB uses the PDB for uplink and downlink scheduling. For example, packets belonging to a QoS Flow with a tight PDB (e.g., 10 ms for URLLC) are prioritized over those with a lax PDB (e.g., 300 ms for buffered streaming). The PDB helps determine scheduling priorities, Hybrid ARQ (HARQ) configurations, and potentially the selection of numerology and slot format. In the core network, the Session Management Function (SMF) may use the PDB during QoS Flow establishment and for policy control interactions with the PCF.

The parameter works in conjunction with other QoS attributes like Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), and Averaging Window. The network aims to ensure that the 95th percentile of the packet delay distribution does not exceed the PDB for the QoS Flow. For Non-GBR QoS Flows, the PDB indicates a packet delay tolerance used for scheduling. The PDB is a critical enabler for service differentiation, allowing the network to simultaneously support diverse applications from massive IoT to ultra-reliable low-latency communications (URLLC) on a common infrastructure.

Purpose & Motivation

The PDB was introduced to provide a standardized, quantifiable latency target for QoS management in 5G, addressing the need for predictable performance for latency-critical applications. Previous generations (4G LTE) had QoS Class Identifiers (QCIs) with implied performance targets, but 5G's expanded use cases—particularly Industrial IoT, autonomous vehicles, and real-time gaming—required more explicit and stringent delay parameters for reliable network behavior.

It solves the problem of inefficient or unpredictable latency handling for mixed traffic types. By assigning a concrete PDB value to each standardized 5QI, network equipment from different vendors can implement consistent scheduling and admission control algorithms. This ensures interoperability and allows application developers and vertical industries to rely on specific network performance levels. The PDB is a cornerstone of 5G's network slicing capability, as different slices can be configured with different latency budgets to serve distinct service level agreements (SLAs).