Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) –...

12
WE MAKE YOUR VIDEOS FLOW Industry Leading Streaming Solu3ons Adap3ve Media Streaming over Emerging Protocols 2014 NAB Show Broadcast Engineering Conference April 7, Las Vegas, NV, USA Dipl.Ing. Dr. Chris&an Timmerer CIO | bitmovin GmbH & AlpenAdriaUniversität Klagenfurt [email protected] blog.3mmerer.com

Transcript of Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) –...

Page 1: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

 WE  MAKE  YOUR  VIDEOS  FLOW  

Industry  Leading  Streaming  Solu3ons  

Adap3ve  Media  Streaming  over  Emerging  Protocols  

2014  NAB  Show  Broadcast  Engineering  Conference  

April  7,  Las  Vegas,  NV,  USA    Dipl.-­‐Ing.  Dr.  Chris&an  Timmerer  CIO  |  bitmovin  GmbH  &  Alpen-­‐Adria-­‐Universität  Klagenfurt  [email protected]  blog.3mmerer.com  

Page 2: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

Video  Predominant  on  the  Internet  

•  Real-­‐3me  video:  >  50%  of  the  traffic  •  Mainly  delivered  over  the  top  using  HTTP  

•  ...  but  the  user  frustra&on  is  s&ll  high!  ➪  Let’s  do  something  

2h2013,  hZps://www.sandvine.com/trends/global-­‐internet-­‐phenomena/  

Mo&va&on  1  

Page 3: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

Dynamic  Adap3ve  Streaming  over  HTTP  

•  ISO/IEC  MPEG  Standard    [ISO/IEC  23009]  –  Media  presenta3on  descrip3on  (MPD)  and  segment  

formats  (ISOBMFF,  M2TS)  •  Dynamic  adap3on  to  the  usage  environment  •  Usage  of  exis3ng  Internet  infrastructure  •  Adapta3on  logic  &  intelligence  at  the  client  ➪  Flexibility  and  scalability  

HTTP SERVERWITH VIDEO CONTENT

DIFFERENT QUALITY REPRESENTATIONS

CHANGINGBANDWITH

CHOOSE THEAPPROPRIATESEGMENT

NETWORK WITH VARIABLE BANDWITH (INTERNET)

USERWITH TABLET

TIME TIME

QUALITY QUALITY

best best

med medlow lowTIME

BANDWIDTH

DASH  2  

Page 4: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

DASH/2.0  

•  MPEG-­‐DASH  adopts  HTTP-­‐URLs  to  iden3fy  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  connec3on  –  Allows  mul3ple  streams  between  client  &  server  –  Exchange  of  frames,  compa3ble  with  HTTP/1.1  

DASH/2.0  3  

Page 5: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

DASH/2.0  Client  Support    •  MPEG-­‐DASH  VLC  plugin  

– World  first  MPEG-­‐DASH  implementa3on  –  Open  source,  part  of  well-­‐know  VLC  ➪  hZp://dash.itec.aau.at  

•  libdash  –  tree/hZp2  – MPEG-­‐DASH  reference  sokware  –  Open  source  &  sample  player  ➪  hZp://bitmovin.com/libdash  

•  Basis  for  products,  e.g.,  bitdash  –  Adapta3on  logic  with  +100%  throughput    

Clients  4  

Page 6: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

Performance  Evalua3on  

Average  Media  Throughput  using  SPDY  given  a  predefined  Bandwidth  Trajectory  for  different  RTTs    

Performance  5  

Page 7: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

Content-­‐Centric  Networking  •  From  a  host-­‐centric  to  the  content-­‐centric  

approach  –  Addressing  loca3on  vs.  content  –  Different  terminology:  ICN,  NDN,  CCN  

•  CCN  approach  –  Interest  packet:  request  for  content  –  Data  packet:  delivery  of  content  –  Network  ac3vely  par3cipates  in  the  delivery  

•  CCN  features  –  Na3ve  support  for  content  caching  –  Loca3on  independence  –  Mul3-­‐path,  mul3-­‐source  delivery  –  Security  and  trust  as  an  integral  part  of  the  network  

CCN  6  

Page 8: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

DASH  and  CCN  :=  DASC  

•  Common  elements  –  Client-­‐ini3ated  pull  approach  –  Content  being  dealt  with  in  pieces  (segments,  chunks)  

•  Two  op3ons  for  integra3on  –  Proxy  service  ac3ng  as  a  broker  between  HTTP  and  CCN  

–  DASH  client  implemen3ng  a  na3ve  CCN  interface    

•  Na3ve  approach  enabled  by  DASH  –  CCN  naming  scheme  (CCN  URIs)    

DASC  7  

Page 9: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

DASC  Client  Support    •  MPEG-­‐DASH  VLC  plugin  

– World  first  MPEG-­‐DASH  implementa3on  –  Open  source,  part  of  well-­‐know  VLC  ➪  hZp://dash.itec.aau.at  

•  libdash  –  tree/ccn  – MPEG-­‐DASH  reference  sokware  –  Open  source  &  sample  player  ➪  hZp://bitmovin.com/libdash  

•  Basis  for  products,  e.g.,  bitdash  –  Adapta3on  logic  with  +100%  throughput    

Clients  8  

Page 10: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

Performance  Evalua3on  

Average  Media  Throughput  using  CCN  given  a  predefined  Bandwidth  Trajectory  for  different  RTTs    

Performance  9  

Page 11: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

Conclusions  •  DASH/2.0  

–  HTTP/2.0  (SPDY)  ~  HTTP/1.1  with  persistent  connec3ons  &  request  pipelining  

–  Implicitly  solves  Head-­‐of-­‐Line  blocking  problem  –  HTTP/2.0:  IETF  hZpbis  WG,  proposed  standard  by  end  of  2014  

•  DASC  –  It  works,  performance  comparable  but…  –  Improvements:  request  pipelining,  caching,  encryp3on/signing  

–  ICNRG  within  IRTF  •  Join  this  ac3vity,  everyone  is  invited  –  get  involved  in  and  exited  about  DASH!  

Conclusions  10  

Tuesday,  April  8,  2-­‐4  pm  Renaissance  Hotel,  adjacent  to  the  LVCC  

hZp://www.dashif.org/  

Page 12: Adap3ve)MediaStreaming) over)Emerging)Protocols) · Conclusions • DASH/2.0) – HTTP/2.0)(SPDY))~HTTP/1.1)with) persistent connecons & requestpipelining) – Implicitly)solves)HeadKofKLineblockingproblem

 WE  MAKE  YOUR  VIDEOS  FLOW  

Industry  Leading  Streaming  Solu3ons  

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 [email protected] www.bitmovin.com | www.bitcodin.com @bitmovin facebook.com/bitmovin github.com/bitmovin