Your SlideShare is downloading. ×
Adaptive Media Streaming over Emerging Protocols
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Adaptive Media Streaming over Emerging Protocols

7,692
views

Published on

Published in: Technology

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

No Downloads
Views
Total Views
7,692
On Slideshare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
38
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • … consequently, DASH does not mandate TCP at all!
  • Transcript

    • 1. WE MAKE YOUR VIDEOS FLOW Industry Leading Streaming Solutions Adaptive Media Streaming over Emerging Protocols 2014 NAB Show Broadcast Engineering Conference April 7, Las Vegas, NV, USA Dipl.-Ing. Dr. Christian Timmerer CIO | bitmovin GmbH & Alpen-Adria-Universität Klagenfurt christian.timmerer@bitmovin.com blog.timmerer.com
    • 2. Video Predominant on the Internet • Real-time video: > 50% of the traffic • Mainly delivered over the top using HTTP • ... but the user frustration is still high! ➪ Let’s do something 2h2013, https://www.sandvine.com/trends/global-internet-phenomena/ Motivation 1
    • 3. Dynamic Adaptive Streaming over HTTP • ISO/IEC MPEG Standard [ISO/IEC 23009] – Media presentation description (MPD) and segment formats (ISOBMFF, M2TS) • Dynamic adaption to the usage environment • Usage of existing Internet infrastructure • Adaptation logic & intelligence at the client ➪ Flexibility and scalability DASH 2
    • 4. DASH/2.0 • MPEG-DASH adopts HTTP-URLs to identify segments within the MPD but… … does not mandate its usage … does not mandate a version • HTTP/2.0 currently under development within IETF (based on SPDY) – Based on TCP, single persistent connection – Allows multiple streams between client & server – Exchange of frames, compatible with HTTP/1.1 DASH/2.0 3
    • 5. DASH/2.0 Client Support • MPEG-DASH VLC plugin – World first MPEG-DASH implementation – Open source, part of well-know VLC ➪ http://dash.itec.aau.at • libdash – tree/http2 – MPEG-DASH reference software – Open source & sample player ➪ http://bitmovin.com/libdash • Basis for products, e.g., bitdash – Adaptation logic with +100% throughput Clients 4
    • 6. Performance Evaluation Average Media Throughput using SPDY given a predefined Bandwidth Trajectory for different RTTs Performance 5
    • 7. Content-Centric Networking • From a host-centric to the content-centric approach – Addressing location vs. content – Different terminology: ICN, NDN, CCN • CCN approach – Interest packet: request for content – Data packet: delivery of content – Network actively participates in the delivery • CCN features – Native support for content caching – Location independence – Multi-path, multi-source delivery – Security and trust as an integral part of the network CCN 6
    • 8. DASH and CCN := DASC • Common elements – Client-initiated pull approach – Content being dealt with in pieces (segments, chunks) • Two options for integration – Proxy service acting as a broker between HTTP and CCN – DASH client implementing a native CCN interface • Native approach enabled by DASH – CCN naming scheme (CCN URIs) DASC 7
    • 9. DASC Client Support • MPEG-DASH VLC plugin – World first MPEG-DASH implementation – Open source, part of well-know VLC ➪ http://dash.itec.aau.at • libdash – tree/ccn – MPEG-DASH reference software – Open source & sample player ➪ http://bitmovin.com/libdash • Basis for products, e.g., bitdash – Adaptation logic with +100% throughput Clients 8
    • 10. Performance Evaluation Average Media Throughput using CCN given a predefined Bandwidth Trajectory for different RTTs Performance 9
    • 11. Conclusions • DASH/2.0 – HTTP/2.0 (SPDY) ~ HTTP/1.1 with persistent connections & request pipelining – Implicitly solves Head-of-Line blocking problem – HTTP/2.0: IETF httpbis WG, proposed standard by end of 2014 • DASC – It works, performance comparable but… – Improvements: request pipelining, caching, encryption/signing – ICNRG within IRTF • Join this activity, everyone is invited – get involved in and exited about DASH! Conclusions 10 Tuesday, April 8, 2-4 pm Renaissance Hotel, adjacent to the LVCC http://www.dashif.org/
    • 12. WE MAKE YOUR VIDEOS FLOW Industry Leading Streaming Solutions Bitmovin We make your media flow Bitdash/Libdash bitmovin GmbH Lakeside Science and Technology Park Building B01 9020 Klagenfurt Austria | Europe T +43 463 27008747 E office@bitmovin.net www.bitmovin.com | www.bitcodin.com @bitmovin facebook.com/bitmovin github.com/bitmovin

    ×