DDDS

Downlink Data Delivery Status

Core Network →
Introduced in Rel-8

DDDS is a 5G Core Network mechanism that provides notification about the delivery status of downlink data when buffering occurs at the UPF.

Category
Core Network
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
3 specs
DDDS Description Purpose Related Classification Detected Changes Specifications

Description

DDDS (Downlink Data Delivery Status) is a sophisticated notification mechanism within the 5G Core Network that operates in conjunction with User Plane Function (UPF) buffering capabilities. When downlink data arrives for a UE that is in idle or inactive mode, the UPF buffers this data and triggers a notification procedure to inform the UE about pending data delivery. The mechanism involves coordinated signaling between the UPF, Session Management Function (SMF), and Access and Mobility Management Function (AMF) to manage the UE's state transitions and data delivery timing.

The architecture involves the UPF detecting downlink data for a UE that is not in connected mode. Instead of immediately paging the UE, the UPF buffers the data and sends a Downlink Data Notification (DDN) to the SMF. The SMF then evaluates whether to trigger immediate paging or utilize DDDS based on configured policies, UE capabilities, and network conditions. When DDDS is invoked, the network sends a notification to the UE indicating that buffered data is available, prompting the UE to transition to connected mode to receive the data.

Key components include the UPF's buffering capability, the SMF's policy decision function for DDDS triggering, and the AMF's role in managing UE mobility and state transitions. The UPF maintains buffering contexts for UEs, including timer management for how long data should be buffered before being discarded or delivered through alternative means. The SMF configures these buffering parameters and makes decisions based on subscription data, network policies, and real-time conditions.

DDDS operates through specific N4 interface procedures between the UPF and SMF, defined in 3GPP TS 29.244. The UPF reports buffering events and delivery status through PFCP (Packet Forwarding Control Protocol) session modification procedures. The mechanism supports different notification modes, including immediate notification, deferred notification based on timers, and conditional notification based on data characteristics or UE behavior patterns.

The technology plays a critical role in 5G's power saving features, particularly for IoT devices and smartphones with intermittent data traffic patterns. By reducing unnecessary paging and connection establishment procedures, DDDS minimizes signaling overhead while maintaining efficient data delivery. The buffering capability at the UPF ensures data integrity and proper sequencing even when UEs are in power-saving states for extended periods.

Purpose & Motivation

DDDS was created to address the fundamental challenge of balancing UE power consumption with efficient data delivery in mobile networks. In previous generations (4G/LTE), when downlink data arrived for an idle UE, the network would immediately page the UE, forcing it to establish a connection regardless of whether the data was time-critical. This approach caused unnecessary power consumption, particularly for IoT devices and smartphones with intermittent background traffic.

The technology solves the problem of 'always-on' connectivity requirements that drain UE batteries. By introducing intelligent buffering at the network edge (UPF) and selective notification mechanisms, DDDS allows UEs to remain in power-saving states longer while ensuring timely delivery of important data. This is especially valuable for massive IoT deployments where devices may only transmit or receive data sporadically but need to maintain years of battery life.

Historical context shows that earlier approaches like Power Saving Mode (PSM) in LTE provided extended sleep periods but made devices unreachable during those times. DDDS represents an evolution that maintains reachability while optimizing power consumption. The motivation came from 5G's requirements to support diverse use cases with varying latency and power consumption needs, from ultra-reliable low-latency communications to massive machine-type communications with extreme energy efficiency requirements.

Classification

Related approachesUPFSMF

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the DDDS function was enhanced to include the reporting of the QoS Flow Identifier (QFI) within the Downlink Data Report, allowing the control plane to identify the specific QoS flow for reported downlink packets. Furthermore, the capability for a Downlink Data Notification Delay was introduced, enabling the UP function to buffer a suggested number of downlink data packets when extended buffering is required.

  • QFI in Downlink Data Report TS 29.244CR0137
  • Downlink Data Notification Delay TS 29.244CR0149
Rel-16 4 changes

In Release 16, the Downlink Data Delivery Status (DDDS) function was enhanced with new reporting capabilities for discarded packets and packet rate status. Specifically, it introduced mechanisms for the UPF to notify the CP function about the first and subsequent discarded downlink packets. Additionally, new instructions within the URR (Usage Reporting Rule) enabled reporting and control of the downlink packet rate.

  • Packet Rate Status Reporting and Control TS 29.244CR0386
  • Downlink data reordering - new feature definition TS 29.244CR0427
  • First discarded downlink packet notification TS 29.244CR0391
  • Notify the discarded downlink packet TS 29.244CR0501
Rel-17 1 change

In Release 17, the DDDS function was enhanced with essential clarifications on Gate Status procedures. This provided more precise instructions for the UPF regarding the forwarding or buffering of downlink data packets based on this status. The update ensured clearer QoS enforcement and traffic handling for specific PDRs within the PFCP framework.

  • Essential clarification on Gate Status TS 29.244CR0666
Rel-18 1 change

In Release 18, the Downlink Data Delivery Status (DDDS) function was refined with a specific clarification on its operation. This clarification provided more precise instructions for the UPF to report the sum of downlink data packet sizes per QoS flow when sending a Downlink Data Report, particularly when triggered by Mobile Terminated Small Data Transmission (MD-SDT) control information. The update ensured consistent reporting behavior for downlink traffic associated with different QoS flows within the same forwarding rule.

  • Clarification on Downlink data delivery status feature TS 29.244CR0854
Rel-19 1 change

In Release 19, the Downlink Data Delivery Status (DDDS) function was enhanced with a clarification on the Downlink Data Notification Delay for the 5G Core (5GC). This provides specific guidance on the timing and reporting mechanisms for notifications related to downlink data delivery. The update ensures consistent implementation of delay reporting for downlink traffic across network functions.

  • Clarification on the Downlink Data Notification Delay for 5GC TS 29.244CR0869

Explore further

Broader topics and technologies where DDDS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.303 vj10 DNS Procedures for Evolved Packet System Rel-19
TS 38.823 vg00 Enhancement Study for Disaggregated gNB Rel-16