Delay Budget Information

Description

Delay Budget Information (DBI) is a standardized Quality of Service (QoS) parameter defined within the 5G System (5GS) framework. It represents the maximum allowable packet delay budget, expressed in milliseconds, for a specific Protocol Data Unit (PDU) session or QoS Flow. The DBI is a scalar value that forms part of the 5G QoS Identifier (5QI) characteristics or can be explicitly signaled as part of a QoS profile. It is a key input for network functions, particularly the Access and Mobility Management Function (AMF), Session Management Function (SMF), and the Radio Access Network (RAN), to enforce latency guarantees.

Architecturally, DBI is propagated through the core network and to the RAN via the N2 and N11 reference points. When a PDU session is established or modified, the SMF determines the required QoS parameters, including the DBI, based on subscription data, policy control rules from the Policy Control Function (PCF), and application function requests. The SMF then provides this information to the AMF, which forwards it to the (R)AN node (gNB) during the PDU session establishment procedure. The RAN uses the DBI, along with other parameters like the Packet Error Rate (PER) and Guaranteed Flow Bit Rate (GFBR), to perform packet scheduling, admission control, and radio resource management. For instance, a flow with a very small DBI (e.g., 1 ms for factory automation) will be prioritized for scheduling over a flow with a larger DBI (e.g., 100 ms for video streaming).

At the RAN, the DBI is crucial for implementing latency-aware scheduling algorithms. The gNB's scheduler considers the remaining packet delay budget for each queued packet. Packets approaching their delay budget limit are given higher priority to be transmitted over the air interface. This mechanism is essential for supporting time-sensitive communication (TSC) and URLLC services defined in 3GPP. Furthermore, DBI is integral to end-to-end network slicing. A network slice instance created for a vertical like industrial IoT can have a QoS profile with a stringent DBI, ensuring the slice's resources are configured and managed to consistently meet that latency target across the user plane functions.

The DBI works in concert with other QoS mechanisms. While the 5QI provides a standardized mapping to default QoS characteristics (including a default DBI), the QoS profile for a specific flow can override this with an explicit DBI value. This allows for fine-grained service differentiation. The management of DBI is also tied to the 5G QoS model's reflective QoS feature, where a User Equipment (UE) can derive uplink QoS rules, including an implicit understanding of latency requirements, from observing the downlink traffic. In summary, DBI is not just a static descriptor but an active parameter that drives dynamic network behavior to fulfill contractual service level agreements (SLAs) for latency-sensitive applications.

Purpose & Motivation

DBI was created to address the fundamental challenge of supporting deterministic latency and ultra-reliable low-latency communication (URLLC) in 5G and beyond. Previous cellular generations (4G/LTE) primarily optimized for high data rates and best-effort mobile broadband. Their QoS framework, centered on the QCI (QoS Class Identifier), included a Packet Delay Budget, but it was not designed or signaled in a way that could guarantee the extreme reliability and sub-10ms latencies required by new vertical industries such as factory automation, remote surgery, autonomous vehicles, and smart grids.

The motivation for standardizing DBI as an explicit, actionable information element stems from the need for end-to-service assurance. Applications in industrial IoT and tactile internet have strict, non-negotiable deadlines for data delivery. Without a clear, quantified delay budget communicated from the core network to the RAN, the gNB scheduler cannot intelligently prioritize time-critical packets over less urgent ones. DBI provides this common language. It solves the problem of opaque latency requirements by making the application's timing constraint a first-class citizen in the QoS negotiation and enforcement chain, enabling proactive rather than reactive network behavior.

Historically, latency management was often an afterthought or handled through over-provisioning. DBI, as part of the enhanced 5G QoS framework introduced in Release 16 for verticals and TSC, represents a shift towards precise, quantifiable, and enforceable latency guarantees. It addresses the limitations of previous approaches by being an integral part of the PDU session and QoS flow establishment signaling, ensuring that every network node involved in the data path is aware of the latency budget and can contribute to meeting it. This was a necessary evolution to transform 5G from a connectivity platform into a reliable service platform for critical communications.