Technology Update: MPEG-Dash

943 views

Published on

De presentatie van TNO op de Technology Update over MPEG-Dash

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
943
On SlideShare
0
From Embeds
0
Number of Embeds
135
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Technology Update: MPEG-Dash

  1. 1. Introduction HTTP Adaptive Streaming 1997 RealVideo 1999 – Windows Media Player 6.4 – Apple Quicktime 4 2002 Adobe Flash(RTMP) Those solutions made Internet video accessible for the masses, but did have some characteristics; - Stateful streaming session to each client - Specific protocol and ports(eventually a roll-over to port 80) - Specific streaming server required for video distribution Internet Video T h e b e g in n in g Anton Havekes, Victor Klos MPEG-DASH
  2. 2. Anton Havekes, Victor Klos MPEG-DASH However most internet traffic is between HTTP servers and clients communicating stateless via TCP/HTTP over port 80  TCP/HTTP data on port 80  Standard HTTP webserver technology  Client in control  Dynamically adapts to actual network performance The solution; a sequence of HTTP downloads of media segments: Introduction HTTP Adaptive Streaming HTTP Request for media segment HTTP Response with media segment Mediaplayer Webserver
  3. 3. Anton Havekes, Victor Klos MPEG-DASH Different types of HAS Early inventors of HTTP Adaptive Streaming • 2007; Move Networks start HAS service • 2007; Swarmcast; p2p network in operation 2008; The big three developed their own HAS variant • Microsoft – HTTP Smooth Streaming(HSS) • Apple – HTTP Live Streaming(HLS) • Adobe(Flash) – HTTP Dynamic Streaming(HDS) HAS standardization • 2009; 3GPP standardized a HAS variant; 3GPP HAS • 2010; ISO-MPEG developed MPEG-DASH based on the early 3GPP HAS standard • 2012: OIPF and 3GPP build on MPEG DASH
  4. 4. Anton Havekes, Victor Klos MPEG-DASH The MPD fileMedia Presentation Description Period ID = 1 Start = 0 sec. Period ID = 2 Start = 60 sec. Period ID = 3 Start = 120 sec. Splicing of arbitrary content Period ID = # Adaptation set 0 Video Adaptation set 1 Audio Media components (audio, video, metadata, subtitles, etc) Adaptation set 0 Representation 1 720p50 – 8Mbps Representation 2 640x…  – 5Mbps Representation 3 640x…  – 3Mbps Representation 4 320x…  – 1Mbps Different representations, the player can switch the quality by switching the representation Segment info Duration = 60 seconds Initialization segment http://s1.com/c.mp4 Media segment 1 Start = 0 seconds http://s1.com/p1.mp4 Media segment 3 Start = 40 seconds http://s1.com/p3.mp4 Media segment 2 Start = 20 seconds http://s1.com/p2.mp4 Content chunks in temporal sequence
  5. 5. Anton Havekes, Victor Klos MPEG-DASH End2End DASH delivery chain
  6. 6. Anton Havekes, Victor Klos MPEG-DASH Shopping list Single channel, Multi-bitrate; Max 10.000 viewers(simul.) MAKE BUY Media-as-a-Service Encoder(on-site) Standard PC 700$ (Multi-bitrate encoding) 10.000-30.000$ (Multi-bitrate encoding) 1.000-5.000$ (Single bitrate) Multi-bitrate(cloud); Fastly, Livetranscoding.com: 500$/month Segmentation/ Encryption/ Origin NGiNX (no encryption) 55$/month or 2000$ perpetual By distribution partner. Distribute Leaseweb server: 399$/month with 250TB/month; 0,0016$/month Leaseweb server: 399$/month with 250TB/month; 0,0016$/month CDN777, Fastly, Cloudfront: 0.06-0.12$ per GB

×