Why Entertainment Live Streaming Needs DASH and How It Works

Why Entertainment Live Streaming Needs DASH

Television live streaming generates over $250 billion annually and remains a core revenue source despite the shift of audiences to mobile terminals, tablets, and PCs. High‑quality live services are still in demand, and DASH (Dynamic Adaptive Streaming over HTTP) offers a robust solution.

China Situation

Regulation (Document 181) prohibits OTT providers from offering live services; companies use NVOD, recorded playback, or edge‑case OTT apps that skirt the rules.

Examples: LeTV uses NVOD to schedule approved content as live; China Mobile, after obtaining an IPTV license in 2016, provides live channels via recorded playback; major OTT apps (TVHome, VST, TVLive, TVCat) claim PAD‑focused designs to stay near the regulatory edge.

Tencent Video TV live uses recorded playback.

Overseas Situation

Integrated operators combine DVB/OTT or IPTV/OTT, typically preserving DVB or IPTV for live delivery and adding OTT for VOD. When 4K arrives, operators must decide between broadcasting over traditional DVB frequencies or migrating entirely to OTT‑based IP delivery.

Key DASH Technology

DASH, also known as MPEG‑DASH, is a standard for adaptive bitrate streaming over HTTP, similar to Apple HLS. It segments video into short fragments described by a Media Presentation Description (MPD), allowing clients to switch bitrates seamlessly based on network conditions.

Advantages of DASH over HLS/HSS

Supports multiple codecs (H.265, H.264, VP9, etc.).

Multi‑DRM support (PlayReady, Widevine) with common encryption, reducing DRM costs.

Various container formats (MPEG‑4, MPEG‑2 TS).

Standardized CDN integration across vendors.

Native browser support without plugins; can be transcoded to HLS/HDS/HSS for legacy devices.

Rich feature set: live, VOD, recording, timeshift.

Smooth multi‑bitrate switching.

Compact MPD for fast startup.

Client‑side and server‑side ad insertion.

Vendor and Platform Support

Android native ExoPlayer.

Major OTT services: YouTube, Netflix.

Modern browsers using MSE/EME.

Smart TV manufacturers: Samsung, LG, Philips, Sony.

Open‑Source Clients and Server Solutions

Client : GStreamer, dash.js, libdash (Android/iOS).

Server : Akamai CDN, Amazon Elastic Transcoder, Azure Media Service, Brightcove Zencoder, Nginx RTMP module, Wowza Streaming Engine.

Typical End‑to‑End DASH System

A complete pipeline includes an Encoder, DASH Server, Origin Server, Edge Server, and DASH Client.

MPD Structure

The Media Presentation Description defines the hierarchy: MPD → Period → Adaptation Set (Video/Audio) → Representation (multiple bitrates) → Segment.

OTT DASH vs. IPTV

Network : IPTV uses managed networks with low latency and guaranteed bandwidth; OTT relies on unmanaged public networks with variable quality.

Terminals : IPTV terminals are operator‑defined STBs; OTT terminals vary widely across devices.

Business : IPTV focuses on low‑latency live multicast; OTT emphasizes tolerance to variable network conditions.

Technology : IPTV uses UDP multicast (firewall‑blocked, prone to mosaic on loss); OTT uses HTTP over TCP (firewall‑friendly, may buffer).

Handling High‑Concurrency Live Events

Massive events (World Cup, national ceremonies) strain OTT unicast delivery. Two mitigation strategies are presented.

Solution 1: ABR Multicast

DASH Origin Server streams are converted to UDP multicast via a Multicast Server, allowing multicast‑capable clients to receive the stream. Standards exist for DASH over broadcast and eMBMS networks.

Solution 2: P2P

Peer‑to‑peer nodes share video chunks, offloading up to 90 % of CDN traffic, reducing bandwidth costs and alleviating network congestion. The approach works well on Android/iOS devices with minimal storage, using memory caching and Wi‑Fi‑based peer connections.