Planned Data Transfer with QoS requirements

Description

Planned Data Transfer with QoS requirements (PDTQ) is a service capability introduced in 3GPP Release 18, defined within the 5G System (5GS) architecture. It enables an Application Function (AF) to request the network to schedule a future data transfer for a User Equipment (UE) with specific QoS guarantees. The core mechanism involves the AF sending a request to the Policy Control Function (PCF) via the Network Exposure Function (NEF), detailing the required data volume, target time window, QoS parameters (such as 5QI, Guaranteed Flow Bit Rate, Maximum Flow Bit Rate), and the destination Data Network Name (DNN). The PCF then authorizes this request and translates it into policy rules for the Session Management Function (SMF). The SMF is responsible for establishing or modifying the appropriate Protocol Data Unit (PDU) Session to fulfill the planned transfer, coordinating with the User Plane Function (UPF) and the Access and Mobility Management Function (AMF) to ensure the UE is reachable and resources are allocated in the Radio Access Network (RAN) at the scheduled time.

Architecturally, PDTQ leverages the existing 5G service-based interfaces, primarily Nnef (between NEF and AF) and Npcf (between NEF and PCF). The PCF uses the Npcf_SMPolicyControl service to provision the authorized policy to the SMF. A key component is the 'Planned Data Transfer' policy control request trigger, which instructs the SMF to prepare for the future session activity. The SMF may pre-establish QoS Flows and notify the RAN via the AMF about the upcoming data transfer, allowing for advanced radio resource scheduling. This proactive orchestration distinguishes PDTQ from reactive QoS mechanisms.

The role of PDTQ in the network is to optimize resource utilization and enhance user experience for non-real-time, bulk data applications. By shifting predictable, large data transfers to off-peak hours or periods of low network congestion, it helps in traffic smoothing and load balancing. It ensures that applications like operating system updates, large file downloads, or media content pre-caching are completed reliably and within a specified time frame without contending with latency-sensitive services like voice or video streaming. This makes it a foundational enabler for efficient network slicing and differentiated service offerings.

Purpose & Motivation

PDTQ was created to address the growing demand for efficient and predictable handling of background data traffic in 5G networks. Prior to its introduction, background data transfers (e.g., software updates, cloud backups) competed for resources with foreground user applications in a best-effort manner, often leading to unpredictable completion times, potential battery drain on the UE due to repeated retries, and congestion during peak hours. Network operators lacked a standardized mechanism to schedule and guarantee QoS for such planned transfers, limiting their ability to manage network load proactively.

The historical context stems from the evolution of smart devices and IoT, which generate significant amounts of deferrable data. The motivation for PDTQ was to provide a standardized interface for over-the-top (OTT) application providers and enterprise services to negotiate guaranteed data delivery slots with the mobile network. This solves the problem of inefficient 'background' data handling, transforming it into a 'planned' network-managed service. It addresses limitations of previous approaches like basic QoS Class Identifiers (QCIs/5QIs) applied reactively, which could not account for future time-based scheduling, and proprietary solutions that lacked interoperability.

Ultimately, PDTQ enables new business models and service level agreements (SLAs) for scheduled data delivery. It allows operators to offer premium 'assured delivery' services to content providers and enterprises, improving network efficiency through traffic shaping and creating new revenue streams. It is a key step towards making the 5G network a more intelligent and programmable platform for diverse data services.

Key Features

• Time-based scheduling of data transfers with start and stop timers
• Support for guaranteed QoS parameters (5QI, GBR, MFBR) for the planned transfer
• Integration with 5G Policy Control Framework (PCF, SMF) for authorization and enforcement
• Network Exposure Function (NEF) mediated interface for Application Function (AF) requests
• Support for both immediate and deferred policy provisioning to the SMF
• Mechanisms for UE reachability management and notification for the planned session

Evolution Across Releases

Defining Specifications