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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (112 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the PDV function was enhanced through QoS flow binding for URLLC services and the clarification on the support of the Delay Critical GBR resource type, which provides packet transport with strict bounds on latency and reliability. These enhancements were part of broader 5G QoS fixes for URLLC attributes, including Packet Delay Budget (PDB), to ensure stringent performance for time-sensitive communications.
- PS Data Off supporting non-IP data packet TS 23.501CR0680
- Corrections to RQoS logic when receiving DL packet with RQI TS 23.501CR0011
- Proposal of Specifying Packet Detection Rule TS 23.501CR0027
- Corrections and clarifications for the usage of Packet Filter Set TS 23.501CR0035
- Traffic mapping information that disallows UL packets TS 23.501CR0053
- 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI TS 23.501CR0087
+ 9 more changes
In Release 16, the PDV function was enhanced within the broader context of Ultra-Reliable Low Latency Communication (URLLC) support and QoS monitoring. Key introductions included explicit mechanisms for QoS monitoring to assist URLLC services and the reporting of bridge delay information for improved delay variation management. These enhancements provided more precise tools for ensuring bounded latency and reliability, particularly for isochronous communication and time-sensitive networking (TSN) interworking.
- New clause for URLLC supporting TS 23.501CR0810
- Introduction of QoS Monitoring to assist URLLC Service TS 23.501CR0990
- QoS Monitoring to assist URLLC Service TS 23.503CR0227
- Description of URLLC features in NF description clauses TS 29.514CR0249
- 5G URLLC: Optimizing Redundancy TS 23.501CR1217
- Clarifications on URLLC support TS 23.501CR1643
+ 25 more changes
In Release 17, key enhancements for the Packet Delay Variation function included improved handling for satellite access and backhaul to accommodate long delays, clarifications and corrections for bridge delay and residence time calculations, and the introduction of a mechanism for deriving uplink packet filters from downlink encapsulated IPsec protected packets. These updates provided more robust delay analytics and measurements, particularly for URLLC services and time-sensitive networking integrations.
- Enchantments for supporting Supported Analytics Delay mechanism TS 23.501CR2530
- Adding the usage of Redundant Transmission Experience analytics for URLLC service TS 23.501CR2581
- Packet Loss Rate measurements TS 23.501CR2587
- Correcting the residence time calculation for the delay measurements TS 23.501CR3198
- Handling of long delays for satellite access and backhaul TS 23.503CR0508
- Requested 5GS delay and UE-DS-TT residence time TS 23.503CR0599
+ 12 more changes
In Release 18, the Packet Delay Variation (PDV) function was newly introduced as a QoS monitoring parameter that can be reported to an Application Function (AF). This was enabled by extending Policy Control Function (PCF) support to monitor PDV values based on the existing QoS monitoring mechanism, allowing the system to provide specific bounds on latency and variation as part of the QoS characteristics for a flow. The release also included clarifications and corrections to the description of PDV and its alignment with related delay budget concepts for both 3GPP and non-3GPP access.
- PCF support of 5GS Packet Delay Variation monitoring based on QoS monitoring mechanism and exposed to AF TS 23.501CR3792
- Non-3GPP QoS and delay budget - 23.501 TS 23.501CR3912
- 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
+ 28 more changes
In Release 19, the enhancements for the Packet Delay Variation (PDV) function primarily focused on enabling and refining N6 delay measurement and indication. Key additions included support for the AF to request N6 delay measurement, enhancements to PCC rules to support this measurement, and procedures for the SMF to trigger N6 delay measurements. Furthermore, the release introduced an "Indication of considering N6 delay" for AF requests and provided clarifications and corrections for the handling and protocols used in these measurements.
- Adding the NAT information exposure and Packet Inspection functionality in the UPF NF profile TS 23.501CR5420
- Support of L-PSA UPF Selection Considering N6 Delay TS 23.501CR5437
- AF request and functionalities enhancement to support N6 delay measurement TS 23.501CR5443
- PCC rule enhancement to support N6 delay measurement TS 23.503CR1325
- Support of the N6 delay indication TS 29.514CR0702
- Update the n6 delay indication handling in the PATCH TS 29.514CR0764
+ 8 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.
| Specification | Title | Release |
|---|---|---|
| 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 |