SlideShare a Scribd company logo

WebRTC Infrastructure the Hard Parts: Media

•
•
Dialogic Inc.
Dialogic Inc.

Discussion on handling WebRTC media: -What are the main reasons to terminate WebRTC media -Media server use cases in WebRTC -Client-side media processing vs. server-side trade-offs -Potential media services for today & tomorrow -Introduction to the Media Resource Broker (MRB) for scaling and orchestrating media servers/MRF -How media handling architectures are evolving & scaling for cloud/NFV networks

Related slideshows

MediaInteractive - Born for the New World
MediaInteractive - Born for the New WorldMediaInteractive - Born for the New World
MediaInteractive - Born for the New World
 
Monetizing the 4G Investment (Mobile Data, and VoLTE Roaming and Interworking)
Monetizing the 4G Investment (Mobile Data, and VoLTE Roaming and Interworking)Monetizing the 4G Investment (Mobile Data, and VoLTE Roaming and Interworking)
Monetizing the 4G Investment (Mobile Data, and VoLTE Roaming and Interworking)
 
Video Codecs and the Future by Vince Puglia
Video Codecs and the Future by Vince PugliaVideo Codecs and the Future by Vince Puglia
Video Codecs and the Future by Vince Puglia
 
1 of 24
Download to read offline
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  1   COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.   WebRTC  Infrastructure:   THE  HARD  PARTS   WebRTC  Global  Summit  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  2   Why  Terminate  Media?   NAT  Traversal:  TURN   Gateway   Media  Server  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  3   NAT  Traversal:  TURN   Gateway   Media  Server   Why  Terminate  Media?   TURN   Server   TURN  for  NAT  Traversal  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  4   NAT  Traversal:  TURN   Gateway   Media  Server   Why  Terminate  Media?   Gateway  for  Interworking   Web   signaling   WebRTC   media   SIP   VoIP   media   GW   SIP
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  5   NAT  Traversal:  TURN   Gateway   Media  Server   Why  Terminate  Media?   Media  Servers  for…  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  6   Many  Reasons  for  a  Media  Server   Conferencing   Interworking  Transcoding   Stream  processing  Recording   Person-­‐to-­‐machine  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  7   Why  process  media  server-­‐side?  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  8   Many  Reasons  for  a  Media  Server   Conferencing   Conferencing  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  9   Mesh  model  does  not  scale   Distributed  peer-­‐to-­‐peer  mesh   Centralized  with  media  server  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  10   Many  Reasons  for  a  Media  Server   Transcoding   Transcoding   Transcoding:  because  we  live  in  an  imperfect  world  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  11   Many  Reasons  for  a  Media  Server   Server  Side  Media-­‐Processing   Server-­‐side  media  handling  for:   ¥  ApplicaYon  work-­‐flows   ¥  Security   ¥  Compliance   ¥  Performance   ¥  Reliability   Stream  processing  Recording   Person-­‐to-­‐machine  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  12   Add  value  to  terminated  media   + Today   •  Audio  &  video  conferencing   •  MulY-­‐camera  switching   •  Compliance  recording   •  Speech  detecYon   •  Audio/video  inserYon   •  Speech  recogniYon   •  Automated  IVR  navigaYon   •  Speaker  CDR  analyYcs   Not  too  far  away   •  Live  RTC  stream  distribuYon   •  Facial  recogniYon   •  Voice  fingerprinYng   •  Health  biometrics   •  Object  detecYon   •  Machine  vision   •  SenYment  analysis   •  Augmented  reality  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  13   Many  Reasons  for  a  Media  Server   Conferencing   Conferencing  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  14   TradiOonal  MCU  Resource  Usage   Worst-­‐case  process:   1.  Each  stream   decoded  at  the  MCU   2.  MCU  mixes  each   conferee   3.  MCU  encodes   individual  mix  for   each  conferee   MCU   1   1   2   2   3   3   4   4  5   5   6   6   Ingress  streams   6   Egress  streams   6   MCU  decodes   6   MCU  encodes   6  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  15   Efficient  MCU  Resource  Usage   Efficient  process:   1.  Each  stream   decoded  at  the  MCU   2.  MCU  mixes  each   conferee   3.  MCU  shares  same   encoder  for  all   conferees   MCU   1   2   3   4   5   6   Ingress  streams   6   Egress  streams   6   MCU  decodes   6   MCU  encodes   1   1   30%-­‐50%  reducYon  in  compute  resources  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  16   Newer  Approach:  SFU   SFU   SelecOve  Forwarding  Unit   (SFU)  rouOng     Clients  send  one  &  receive   many     Client  can  instruct  SFU   which  streams  to  send     High  throughput     Can  be  lots  of  downlink   bandwidth     Low  latency  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  17   Newer  Approach:  SFU   SFU   SelecOve  Forwarding  Unit   (SFU)  rouOng     Clients  send  one  &  receive   many     Client  can  instruct  SFU   which  streams  to  send     High  throughput     Can  be  lots  of  downlink   bandwidth     Low  latency  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  18   New  WebRTC  Approach:  Simulcast   SFU   High  bitrate   Low  bitrate   SelecOve  Forwarding  Unit   (SFU)  with  Simulcast     Clients  send  mulYple   streams  to  SFU     one  high-­‐bit  rate       one  or  more  lower-­‐bit       Client  directs  SFU  which   streams  to  receive     Reduces  bandwidth  vs.  SFU     Simulcast  in  WebRTC   coming  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  19   Future  Approach  with  VP9  –  SVC?   SFU   Medium  High   Low  Layered  bitrates:   SelecOve  Forwarding  Unit   (SFU)  with  Scalable  Video   Coding  (SVC)     Clients  send  layered   stream  to  SFU     Layers  have  varying  bitrates  –   Yme,  size,  quality     SFU  directs  who  gets  what     Coming  to  WebRTC   eventually  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  20   Media  server  network  model   Load   Balancer  MRB   Client   Client   Client   Client   Client   Client   App  Server   App  Server   App  Server   Media   Server   Media  Resource  Broker:   Intelligent  load  balancer  &   orchestraYon  for  media  servers  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  21   Pseudo  Call-­‐flow  with  a  media  server   AS   MRB   MS1   MS2   Client   Call  signaling   Media   control   MS1  status   MS2  status   Media   control   Media  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  22   Pseudo  Call-­‐flow  –  tradiOonal  fail-­‐over  with  RE-­‐INVITE   AS   MRB   MS1   MS2   Client   Call  signaling  –  REINVITE  with    new   addresses   Media   control   MS1  status   MS2  status   Media  control  +  call  states   Media  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  23   Pseudo  Call-­‐flow  –  fail-­‐over  the  cloud/NFV  way   AS   MRB   MS1   MS2   Client   Media   control   MS1  status   MS2  status   New  container   Media   Memcache  &  Virtual  IP   Address  
COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  24   Conclusions   ¥  TerminaYng  media  isn’t  cheap,  so  avoid  it  if  you  can   ¥  Like  it  or  not,  you  will  probably  need  server-­‐side  media  someYmes   ¥  If  you  need  server-­‐side  media,  maximize  the  value  you  get  from  it   ¥  Architectures  are  evolving  to  make  media-­‐processing  more  efficient  &  scalable  

More Related Content

WebRTC Infrastructure the Hard Parts: Media

  • 1. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  1   COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.   WebRTC  Infrastructure:   THE  HARD  PARTS   WebRTC  Global  Summit  
  • 2. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  2   Why  Terminate  Media?   NAT  Traversal:  TURN   Gateway   Media  Server  
  • 3. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  3   NAT  Traversal:  TURN   Gateway   Media  Server   Why  Terminate  Media?   TURN   Server   TURN  for  NAT  Traversal  
  • 4. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  4   NAT  Traversal:  TURN   Gateway   Media  Server   Why  Terminate  Media?   Gateway  for  Interworking   Web   signaling   WebRTC   media   SIP   VoIP   media   GW   SIP
  • 5. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  5   NAT  Traversal:  TURN   Gateway   Media  Server   Why  Terminate  Media?   Media  Servers  for…  
  • 6. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  6   Many  Reasons  for  a  Media  Server   Conferencing   Interworking  Transcoding   Stream  processing  Recording   Person-­‐to-­‐machine  
  • 7. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  7   Why  process  media  server-­‐side?  
  • 8. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  8   Many  Reasons  for  a  Media  Server   Conferencing   Conferencing  
  • 9. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  9   Mesh  model  does  not  scale   Distributed  peer-­‐to-­‐peer  mesh   Centralized  with  media  server  
  • 10. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  10   Many  Reasons  for  a  Media  Server   Transcoding   Transcoding   Transcoding:  because  we  live  in  an  imperfect  world  
  • 11. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  11   Many  Reasons  for  a  Media  Server   Server  Side  Media-­‐Processing   Server-­‐side  media  handling  for:   ¥  ApplicaYon  work-­‐flows   ¥  Security   ¥  Compliance   ¥  Performance   ¥  Reliability   Stream  processing  Recording   Person-­‐to-­‐machine  
  • 12. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  12   Add  value  to  terminated  media   + Today   •  Audio  &  video  conferencing   •  MulY-­‐camera  switching   •  Compliance  recording   •  Speech  detecYon   •  Audio/video  inserYon   •  Speech  recogniYon   •  Automated  IVR  navigaYon   •  Speaker  CDR  analyYcs   Not  too  far  away   •  Live  RTC  stream  distribuYon   •  Facial  recogniYon   •  Voice  fingerprinYng   •  Health  biometrics   •  Object  detecYon   •  Machine  vision   •  SenYment  analysis   •  Augmented  reality  
  • 13. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  13   Many  Reasons  for  a  Media  Server   Conferencing   Conferencing  
  • 14. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  14   TradiOonal  MCU  Resource  Usage   Worst-­‐case  process:   1.  Each  stream   decoded  at  the  MCU   2.  MCU  mixes  each   conferee   3.  MCU  encodes   individual  mix  for   each  conferee   MCU   1   1   2   2   3   3   4   4  5   5   6   6   Ingress  streams   6   Egress  streams   6   MCU  decodes   6   MCU  encodes   6  
  • 15. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  15   Efficient  MCU  Resource  Usage   Efficient  process:   1.  Each  stream   decoded  at  the  MCU   2.  MCU  mixes  each   conferee   3.  MCU  shares  same   encoder  for  all   conferees   MCU   1   2   3   4   5   6   Ingress  streams   6   Egress  streams   6   MCU  decodes   6   MCU  encodes   1   1   30%-­‐50%  reducYon  in  compute  resources  
  • 16. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  16   Newer  Approach:  SFU   SFU   SelecOve  Forwarding  Unit   (SFU)  rouOng     Clients  send  one  &  receive   many     Client  can  instruct  SFU   which  streams  to  send     High  throughput     Can  be  lots  of  downlink   bandwidth     Low  latency  
  • 17. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  17   Newer  Approach:  SFU   SFU   SelecOve  Forwarding  Unit   (SFU)  rouOng     Clients  send  one  &  receive   many     Client  can  instruct  SFU   which  streams  to  send     High  throughput     Can  be  lots  of  downlink   bandwidth     Low  latency  
  • 18. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  18   New  WebRTC  Approach:  Simulcast   SFU   High  bitrate   Low  bitrate   SelecOve  Forwarding  Unit   (SFU)  with  Simulcast     Clients  send  mulYple   streams  to  SFU     one  high-­‐bit  rate       one  or  more  lower-­‐bit       Client  directs  SFU  which   streams  to  receive     Reduces  bandwidth  vs.  SFU     Simulcast  in  WebRTC   coming  
  • 19. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  19   Future  Approach  with  VP9  –  SVC?   SFU   Medium  High   Low  Layered  bitrates:   SelecOve  Forwarding  Unit   (SFU)  with  Scalable  Video   Coding  (SVC)     Clients  send  layered   stream  to  SFU     Layers  have  varying  bitrates  –   Yme,  size,  quality     SFU  directs  who  gets  what     Coming  to  WebRTC   eventually  
  • 20. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  20   Media  server  network  model   Load   Balancer  MRB   Client   Client   Client   Client   Client   Client   App  Server   App  Server   App  Server   Media   Server   Media  Resource  Broker:   Intelligent  load  balancer  &   orchestraYon  for  media  servers  
  • 21. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  21   Pseudo  Call-­‐flow  with  a  media  server   AS   MRB   MS1   MS2   Client   Call  signaling   Media   control   MS1  status   MS2  status   Media   control   Media  
  • 22. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  22   Pseudo  Call-­‐flow  –  tradiOonal  fail-­‐over  with  RE-­‐INVITE   AS   MRB   MS1   MS2   Client   Call  signaling  –  REINVITE  with    new   addresses   Media   control   MS1  status   MS2  status   Media  control  +  call  states   Media  
  • 23. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  23   Pseudo  Call-­‐flow  –  fail-­‐over  the  cloud/NFV  way   AS   MRB   MS1   MS2   Client   Media   control   MS1  status   MS2  status   New  container   Media   Memcache  &  Virtual  IP   Address  
  • 24. COMPANY  CONFIDENTIAL    ©  COPYRIGHT  2015  DIALOGIC  CORPORATION.    ALL  RIGHTS  RESERVED.  24   Conclusions   ¥  TerminaYng  media  isn’t  cheap,  so  avoid  it  if  you  can   ¥  Like  it  or  not,  you  will  probably  need  server-­‐side  media  someYmes   ¥  If  you  need  server-­‐side  media,  maximize  the  value  you  get  from  it   ¥  Architectures  are  evolving  to  make  media-­‐processing  more  efficient  &  scalable