PDV

Packet Delay Variation

QoS →
Introduced in Rel-18

PDV is a key Quality of Service metric that measures the variation in latency between packets in a data flow.

Category
QoS
Introduced
Rel-18
Where
Core Network › 5G Core
Specifications
4 specs
PDV Description Purpose Related Classification Detected Changes Specifications

Description

Packet Delay Variation (PDV), often synonymous with jitter in IP networks, is formally defined in 3GPP as the difference in the end-to-end delay between selected packets in a flow, with any lost packets being ignored. It is a statistical measure, typically calculated as the difference between the maximum and minimum packet delays observed over a specific measurement interval or window. In 5G systems, PDV is a fundamental parameter for Ultra-Reliable Low-Latency Communication (URLLC) services and deterministic networking. The network uses PDV requirements, specified in service level agreements (SLAs) or 5G QoS Indicators (5QIs), to allocate resources and configure scheduling algorithms in both the Radio Access Network (RAN) and the Core Network to ensure packets are delivered within a bounded delay window.

Architecturally, PDV management involves coordination across multiple network functions. The Policy Control Function (PCF) defines PDV policies based on subscription data and application function requests. The Session Management Function (SMF) enforces these policies by configuring appropriate QoS flows and rules for the User Plane Function (UPF) and the gNB. In the RAN, packet scheduling algorithms, such as time-aware shaping defined in IEEE 802.1Qbv, are employed to minimize queueing delays and variations. The UPF performs traffic policing and marking to ensure non-conforming packets do not adversely affect the PDV of other flows.

PDV is measured end-to-end, from the source application server to the UE, or on specific network segments. Measurement methodologies are defined in specifications like 29.122 (N5 interface) and 29.514 (CAPIF), which provide frameworks for exposure and analytics. Key components in PDV assurance include the Network Data Analytics Function (NWDAF), which can collect PDV metrics and predict violations, and the 5G-AN (Access Network), which must provide low and predictable latency through techniques like mini-slots, grant-free uplink, and pre-emption. Its role is to enable deterministic performance, which is a cornerstone for transforming 5G from a best-effort data pipe into a platform for critical communication services.

Purpose & Motivation

PDV was introduced to address the stringent requirements of emerging real-time and interactive applications in 5G and beyond networks. Traditional mobile networks optimized for throughput and average latency were insufficient for applications like autonomous vehicles, remote surgery, and tactile internet, where not just low latency but predictable, consistent latency is paramount. High PDV (jitter) can cause buffer overflows/underflows, degraded audio/video quality, and control instability in cyber-physical systems. The creation of PDV as a standardized QoS parameter in Rel-18 was motivated by the need to formally quantify, manage, and guarantee this aspect of performance within the 3GPP framework.

Historically, jitter was managed at the application layer or within isolated enterprise networks. The limitation was the lack of network-aware, standardized control. 3GPP's standardization of PDV allows the network to be intrinsically aware of an application's delay variation tolerance and to reserve and configure resources accordingly across the entire mobile packet core and RAN. This solves the problem of best-effort treatment for critical data flows in a shared infrastructure, enabling network slicing for vertical industries with precise timing needs. It represents a shift from reactive congestion management to proactive deterministic service assurance.

Classification

Part of5QI
Related approachesURLLC

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (13 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-18 13 changes

In Release 18, 3GPP introduced standardized support for per-flow Packet Delay Variation (PDV) monitoring and policy control within the 5GS, based on AF-provided requirements. This allows the PCF to support PDV monitoring using the QoS monitoring mechanism, with the results exposed to the AF. The PDV is defined as the variation of packet delay measured between the UE and the PSA UPF, and it was formally added to the set of QoS monitoring parameters.

  • PCF support of 5GS Packet Delay Variation monitoring based on QoS monitoring mechanism and exposed to AF TS 23.501CR3792
  • Update about the Packet Delay Variation description and add PDV in QoS monitoring parameters TS 23.501CR4506
  • PCF support of 5GS Packet Delay Variation value monitoring based on QoS monitoring mechanism and exposed to AF TS 23.503CR0781
  • Policy control support for Packet Delay Variation monitoring and reporting TS 23.503CR0955
  • Support of Packet Delay Variation monitoring and reporting TS 29.122CR0707
  • Support of the Packet Delay Variation monitoring TS 29.122CR0742

+ 7 more changes

Explore further

Broader topics and technologies where PDV plays a role.

Defining Specifications

3GPP specifications that define or reference PDV, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.503 vk00 5G Policy and Charging Control Framework Rel-20
TS 29.122 vj40 T8 Reference Point for Northbound APIs Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.