HTTP Streaming and Download

Description

HTTP Streaming and Download (HSD) is a 3GPP service enabler defined in TS 26.247. It standardizes the delivery of multimedia content using HTTP-based protocols, primarily to support adaptive streaming over mobile networks. The architecture is client-server based, where the media content is prepared as segmented files (e.g., MPEG-DASH or 3GPP Adaptive HTTP Streaming formats) and hosted on a conventional HTTP web server or a dedicated streaming server. The client, typically a User Equipment (UE) with a media player application, uses HTTP GET or partial GET requests to retrieve media segments and manifest files (like MPD in DASH). A key component is the adaptation logic in the client, which monitors network conditions and selects the appropriate bitrate segment to ensure smooth playback without buffering interruptions.

The technology works by breaking the media into small, independently decodable segments encoded at multiple bitrates. A manifest file describes these segments and their characteristics. The client initially fetches the manifest, then begins requesting segments. Based on available throughput, buffer status, and device capabilities, the client's adaptation engine dynamically chooses the next segment's bitrate. This allows the stream quality to adapt in real-time to network congestion or improvements, providing a consistent user experience. For progressive download, the entire file is downloaded via HTTP, but playback can start before the download completes if the file format permits.

HSD's role in the network is as an application-layer service enabler that sits above the transport layer provided by the packet core (EPC, 5GC). It leverages the underlying IP connectivity service. It does not define radio or core network procedures but relies on them for efficient IP packet delivery. The specification ensures interoperability between content preparation tools, servers, and client devices from different vendors, which was crucial for the ecosystem growth of mobile video services. It integrates with other 3GPP services like Multimedia Broadcast/Multicast Service (MBMS) for broadcast delivery enhancements.

Purpose & Motivation

HSD was created to address the growing demand for efficient and reliable video delivery over mobile networks. Prior to its standardization, proprietary streaming solutions led to fragmentation, requiring specific client-server pairs and complicating content distribution. The primary problem was delivering video over best-effort IP networks, which suffer from variable bandwidth and latency, causing frequent buffering and poor quality of experience (QoE) for users.

The motivation was to leverage the ubiquitous HTTP protocol, which traverses firewalls and Network Address Translation (NAT) easily, unlike specialized streaming protocols (e.g., RTSP). Standardizing an adaptive HTTP-based approach allowed clients to adjust video quality based on real-time network conditions, a significant improvement over fixed-bitrate streaming. This was introduced in Release 10, aligning with the rise of smartphones and mobile data consumption. It solved the limitation of earlier 3GPP packet-switched streaming (PSS) which was more complex and less adaptive, providing a more internet-friendly and scalable solution for on-demand and live streaming services.

Key Features

• Standardized adaptive bitrate streaming using HTTP/1.1
• Support for MPEG-DASH and 3GPP Adaptive HTTP Streaming (AHS) profiles
• Client-driven quality adaptation based on network and buffer metrics
• Use of manifest files (Media Presentation Description) for content description
• Support for both on-demand and live streaming service modes
• Integration capabilities with 3GPP QoS and broadcast (MBMS) mechanisms

Evolution Across Releases

Defining Specifications