Next Application Data Unit

Description

The Next Application Data Unit (NADU) is a term defined within 3GPP specifications for streaming services, most notably in TS 26.234 for the Packet-switched Streaming Service (PSS). It represents the upcoming data unit that a streaming client application (e.g., a media player) is scheduled to decode and render, based on the presentation timeline. Technically, the NADU is not a protocol header field but a logical entity used by the streaming client and server to manage data flow and synchronization. It is closely associated with the Real-time Transport Protocol (RTP) payloads or other formatted media chunks that constitute the streaming session.

In operation, the client maintains a playout buffer that stores incoming media data units. The NADU is the next unit in sequence that will be consumed from this buffer for playback. The client uses knowledge of the NADU to generate feedback reports, such as in RTCP (RTP Control Protocol) or via 3GPP-specific signaling, to inform the server about its current reception status and anticipated needs. This can influence server behavior, like adjusting transmission rates, prioritizing certain packets, or triggering retransmissions in case of loss before the playout deadline. The NADU concept is integral to adaptive streaming mechanisms where the server may switch between different bitrate representations based on client buffer levels and network conditions.

Architecturally, the NADU interacts with components like the streaming client's buffer manager, decoder scheduler, and QoS management module. It helps in implementing features like fast forward, rewind, and trick modes by allowing the client to signal which data unit it requires next when seeking to a new position in the timeline. In the context of 3GPP's PSS and Multimedia Broadcast/Multicast Service (MBMS), proper NADU management ensures smooth playback, minimizes rebuffering events, and optimizes radio resource usage by allowing the network to pre-fetch or prioritize delivery of the most urgently needed data.

Purpose & Motivation

The NADU concept was introduced to address challenges in delivering real-time streaming services over unreliable and bandwidth-varying packet-switched mobile networks. Early streaming solutions often suffered from playback interruptions due to jitter, packet loss, and fluctuating throughput, leading to poor user experience. The NADU provides a clear reference point for both client and server to coordinate data delivery in alignment with the application's real-time demands.

It solves the problem of inefficient buffer management and lack of application-aware scheduling in the network. By identifying the next required data unit, the system can prioritize its transmission over less critical data, apply forward error correction or retransmissions selectively, and adapt the media encoding rate proactively. This is particularly important in mobile environments where radio conditions change rapidly and resources are shared among many users.

Historically, its specification in Release 8 as part of PSS enhancements was motivated by the growing popularity of mobile video streaming and the need for standardized mechanisms to improve quality of service. The NADU concept enabled more sophisticated client-server interactions beyond basic RTP/RTCP, allowing 3GPP streaming services to compete with internet streaming platforms by offering robust, network-aware delivery. While later technologies like Dynamic Adaptive Streaming over HTTP (DASH) have introduced different paradigms, the underlying principle of tracking the next needed data segment remains relevant for real-time streaming optimization.

Key Features

• Logical identifier for the upcoming media data unit in streaming playback
• Used for client buffer management and playout synchronization
• Enables application-aware QoS and prioritization in the network
• Supports adaptive streaming and rate switching decisions
• Facilitates trick mode operations (fast forward/rewind) in streaming services
• Integrates with 3GPP PSS and MBMS delivery mechanisms

Evolution Across Releases

Defining Specifications