Description
Maximum Data Burst Volume (MDBV) is a key parameter within the 5G Quality of Service (QoS) framework, specifically associated with the 5G QoS Identifier (5QI). It quantifies, in bytes, the maximum amount of data that the network is required to handle as a single burst while still meeting the latency and reliability guarantees defined for that 5QI. The MDBV works in conjunction with the Maximum Burst Duration (MBD), which defines the time window for this burst. Essentially, for a given QoS flow, the network must be engineered to ensure that a data burst of size up to the MDBV can be delivered within the MBD without violating the packet delay budget.
Technically, the MDBV is used by the packet scheduler in the Radio Access Network (RAN) and the QoS enforcement mechanisms in the User Plane Function (UPF). When a QoS flow is established, these network elements are aware of its associated 5QI, which carries the MDBV value (either standardized per 5QI or signaled dynamically). The scheduler uses this information to allocate radio resources. For example, for an Ultra-Reliable Low Latency Communication (URLLC) service, a small MDBV (e.g., corresponding to a single industrial control command) and a very short MBD are defined. The scheduler must prioritize these packets and ensure sufficient resources are available instantaneously to clear the burst within the strict time limit.
Its role is fundamental for traffic shaping and admission control. The Session Management Function (SMF) may use the MDBV during QoS flow establishment to determine if the network has sufficient resources to admit a new flow with stringent requirements. In the user plane, it helps prevent scenarios where a large, unexpected burst of data could cause queueing delays for latency-sensitive packets. By defining the 'burstiness' a service can exhibit, MDBV allows the network to plan resource allocation more accurately than with average bit rate parameters alone, which is crucial for the deterministic performance required by industrial IoT, autonomous vehicles, and real-time gaming.
Purpose & Motivation
The MDBV was introduced to address the stringent and deterministic QoS requirements of new 5G use cases, particularly Ultra-Reliable Low Latency Communication (URLLC) and industrial IoT. Previous cellular generations (4G/LTE) primarily used parameters like Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR), which are effective for continuous streams (like video) but insufficient for characterizing bursty, latency-critical traffic. A constant bit rate guarantee does not ensure that a sudden burst of data will be delivered within a few milliseconds.
The core problem MDBV solves is providing a quantifiable bound on 'burstiness' for latency-sensitive services. In URLLC scenarios, data transmissions are often sporadic but must be delivered with extreme reliability and minimal delay (e.g., 1 ms). The network needs to know the maximum size of such a burst to reserve the appropriate resources (radio slots, processing capacity) to handle it instantly. Without MDBV, the network would either over-provision resources for the worst-case continuous rate (inefficient) or risk failing to deliver bursts on time (unreliable).
Its creation was motivated by the need to translate application-level requirements (e.g., 'deliver a 200-byte packet within 5 ms with 99.999% reliability') into concrete network parameters that schedulers can act upon. MDBV, together with MBD and Packet Delay Budget (PDB), forms a complete model for bursty latency-sensitive traffic. This enables 5G systems to offer true performance guarantees, moving beyond 'best-effort' or 'prioritized' service towards deterministic connectivity, which is a foundational requirement for vertical industries adopting 5G for mission-critical operations.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Maximum Data Burst Volume (MDBV) function was newly introduced as a mandatory QoS parameter exclusively for GBR QoS Flows using the Delay-critical resource type. Its enforcement was defined, specifying that a packet delayed beyond the Packet Delay Budget is only counted as lost if the data burst does not exceed the MDBV within that budget and the flow does not exceed the Guaranteed Flow Bit Rate (GFBR). Furthermore, the relationship between GFBR and MDBV was clarified, noting that the SMF can ensure the GFBR is achievable given the MDBV through QoS Flow binding.
In Release 16, the MDBV function was enhanced with specific clarifications and mapping procedures for Time-Sensitive Communication (TSC) QoS Flows. The corrections and revisions ensured accurate derivation of MDBV from traffic parameters like TSC Burst Size and clarified its relationship with the Packet Delay Budget for proper QoS enforcement. Furthermore, the updates defined how MDBV is configured and signaled for TSC flows, including its role in interworking with TSN networks.
Explore further
Broader topics and technologies where MDBV plays a role.
Defining Specifications
3GPP specifications that define or reference MDBV, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |