Dynamic Adaptive Streaming over HTTP

Description

Dynamic Adaptive Streaming over HTTP (DASH) is an international standard for adaptive bitrate streaming that delivers media content from conventional HTTP web servers. Its architecture is client-driven, where the client autonomously selects media segments from different representations (bitrates, resolutions, codecs) listed in a Media Presentation Description (MPD) file. The MPD is an XML document that describes the structure of the media presentation, including timing, URLs, and characteristics of available media segments. The client periodically fetches this MPD and then requests individual media segments (typically a few seconds in duration) via standard HTTP GET requests. The core intelligence resides in the client's adaptation logic, which monitors real-time network conditions (like available bandwidth) and device parameters (like CPU load and screen resolution) to choose the next segment from the most appropriate representation, aiming to maximize quality while minimizing rebuffering.

The protocol operates by dividing the media content into a sequence of small HTTP-based file segments. Each segment contains a short interval of playback time, and for each interval, multiple alternative segments are encoded at different bitrates and resolutions. The client downloads these segments one by one. After downloading a segment, the client assesses conditions and decides which bitrate to select for the next segment. This decision happens seamlessly during playback, allowing for adaptation to changing network throughput, such as when a user moves from a 5G to a Wi-Fi network. DASH is codec-agnostic, supporting common video and audio codecs like AVC/H.264, HEVC/H.265, and AAC, and it can deliver both live and on-demand content.

Key components include the DASH client (the media player with adaptation logic), the HTTP server(s) hosting the segments and MPD, and the MPD itself. The MPD describes the temporal structure (Periods, Adaptation Sets, Representations, and Segments), accessibility (URL templates), and media characteristics (codec, resolution, bitrate). DASH's role in 3GPP networks is as a service enabler for media delivery, particularly for Multimedia Broadcast/Multicast Service (MBMS) and unicast streaming. It is integrated into the 3GPP Packet-Switched Streaming Service (PSS) and Multimedia Telephony Service (MTSI), providing a standardized method for efficient, scalable, and high-quality video streaming over mobile and fixed networks. Its use of HTTP allows it to leverage existing web infrastructure, including CDNs and caching proxies, making deployment straightforward and cost-effective.

Purpose & Motivation

DASH was created to address the challenges of delivering high-quality video over best-effort IP networks, particularly the Internet and mobile networks, where bandwidth fluctuates significantly. Prior to adaptive streaming, video was delivered via progressive download or real-time streaming protocols like RTSP, which often led to frequent buffering or poor quality when network conditions degraded. These methods typically locked the client into a single bitrate for the entire session, resulting in a suboptimal user experience. DASH solves this by enabling the client to adapt the media bitrate in real-time, ensuring continuous playback by trading off instantaneous video quality against the risk of rebuffering.

The historical context includes the proliferation of proprietary adaptive streaming solutions (like Apple's HLS and Microsoft's Smooth Streaming) which fragmented the market. 3GPP, in collaboration with MPEG, standardized DASH to create a single, interoperable solution. This was motivated by the need for a universal standard that could be deployed across different networks (3G, 4G, 5G, fixed) and devices, reducing complexity for content providers and enabling innovation in client adaptation algorithms. Standardization through 3GPP and ISO/IEC (as MPEG-DASH) ensured wide industry adoption.

DASH specifically addresses limitations of previous approaches by being purely HTTP-based, which simplifies traversal of firewalls and NATs, leverages ubiquitous HTTP caching for scalability, and decouples the streaming logic from the transport protocol. It gives content providers control over the offered representations and clients the intelligence to choose optimally, creating a robust system for delivering media in dynamic network environments, which is essential for mobile video consumption.

Key Features

• HTTP-based delivery using standard web servers and caches
• Client-driven adaptive bitrate selection based on real-time conditions
• XML Media Presentation Description (MPD) for media structure
• Codec-agnostic support for various video and audio formats
• Support for both live and on-demand streaming services
• Segmented media files enabling flexible CDN distribution

Evolution Across Releases

Defining Specifications