3GPP Dynamic Adaptive Streaming over HTTP

Description

3GP-DASH is a comprehensive media delivery specification that defines formats and protocols for adaptive streaming over HTTP. The architecture is client-driven and based on a manifest file called the Media Presentation Description (MPD). The MPD is an XML document that describes the structure of the media presentation, including timing, URLs for media segments, and the available alternative representations (e.g., different bitrates, resolutions, and codecs). The client, or DASH player, is responsible for fetching and parsing the MPD, then autonomously selecting and downloading media segments from the HTTP server. The core operational principle involves the client monitoring its own buffer status and estimating available network bandwidth. Based on this real-time assessment, it selects the next media segment from the most appropriate representation listed in the MPD to avoid rebuffering while maximizing playback quality. Segments are typically short, independent files (e.g., 2-10 seconds) containing media data formatted according to the ISO Base Media File Format (ISOBMFF) for on-demand content or MPEG-2 Transport Stream (M2TS) for live streaming. Key components include the DASH client (the media player), the HTTP web server (or CDN) hosting the MPD and media segments, and the MPD itself which acts as the 'recipe' for the presentation. In a 3GPP network, 3GP-DASH operates as an application-layer service, typically delivered over the IP Multimedia Subsystem (IMS) or directly over the bearer network. It interfaces with the core network's Policy and Charging Control (PCC) framework, which can provide network-assistance information to the client or apply QoS policies to the streaming session. The protocol's reliance on standard HTTP makes it firewall-friendly and easily cacheable by standard CDNs, which is fundamental to its scalability for mass-market video services.

Purpose & Motivation

3GP-DASH was created to standardize and optimize video delivery over mobile networks, addressing the challenges of fluctuating bandwidth and diverse device capabilities inherent to the wireless environment. Prior to DASH, proprietary adaptive streaming solutions (like Apple's HLS or Microsoft's Smooth Streaming) created fragmentation, requiring content providers to encode and store multiple versions of their media for different ecosystems. This increased complexity and cost. The primary motivation was to establish a single, international standard for adaptive streaming that would work seamlessly across all devices and networks, promoting interoperability and reducing overhead for service providers. It solves the problem of video stuttering and long buffering times by allowing the client to dynamically switch between different quality levels during playback. Historically, progressive download or non-adaptive streaming would either waste bandwidth (if the fixed bitrate was too low) or cause constant interruptions (if it was too high for the current link). 3GP-DASH gives control to the client to make the best quality decision based on its immediate context, fundamentally improving the Quality of Experience (QoE) for the end-user. Its development within 3GPP, starting in Release 10, was driven by the explosive growth of mobile video traffic and the need for a network-aware, efficient delivery mechanism that could be integrated with 3GPP's QoS and policy management frameworks.

Key Features

• Client-driven adaptive bitrate logic based on MPD manifest
• Standardized Media Presentation Description (MPD) XML schema
• Support for both ISO Base Media File Format (ISOBMFF) and MPEG-2 TS segment formats
• Integration with 3GPP Policy and Charging Control (PCC) for network assistance
• Efficient CDN and HTTP caching compatibility
• Support for live, on-demand, and time-shifted media presentations

Evolution Across Releases

Defining Specifications