W3C’s Real-time Web

2,644 views
2,483 views

Published on

Published in: Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,644
On SlideShare
0
From Embeds
0
Number of Embeds
428
Actions
Shares
0
Downloads
189
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

W3C’s Real-time Web

  1. 1. W3C’s  Real-­‐,me  Web  Bryan  Sullivan,  AT&T  OMA  Brooklyn  Messaging  Workshop  July,  2012     ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  2. 2. Messaging  &  Real-­‐Time  CommunicaJons    –  an  overlapping  and  crowded  field   SaaS  Providers  Enterprise   Cloud  Frameworks  /  APIs   Operator  Key  advantages:   Unified  CommunicaJon  SoluJons   Ø One-stop shop for all communications Voice/Video  Conferencing   Ø Flexible charging / service bundling Push  to   Ø Service assurance ~   Talk   Ø Fully interworked communications Market  Segment   Mobile  Phone   ~   SMS   VOIP  Apps   MMS   Webmail       Web  &   Internet   RCS   Social  Networking    /  Media   VOIP/SIP  Consumer   Messaging   Sharing   Voice   Video   Mobile   Breadth  of  Services   Services   2   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  3. 3. Real-­‐Time  CommunicaJons  landscape  -­‐  an  ecosystem  perspecJve   Users   Subscribers   WebRTC   Service   Applica,on  developers   Over  The  Top  (OTT)   Web  PlaWorm  and  Cloud  Service  Providers   OS  PlaMorms   API  Framework  Providers   Network  Service   WebRTC  PlaMorm   WebRTC   Providers   gateway   Network  APIs   Mul,media  Infrastructure   Iden,ty   Payment   Communica,ons   Loca,on   IMS   Network   3   3   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  4. 4. What  is  WebRTC?   WebRTC  is  a  W3C  standardiza,on  ac,vity  (with  support  from  IETF)  that  enables  web   browsers  with  Real-­‐Time  Communica,ons  capabili,es  via  JavaScript  APIs.    It  allows     rich,  high  quality  applica,ons  to  be  executed  in  the  browser  using  JavaScript  APIs  and   HTML5,  without  the  need  for  any  other  na,ve  applica,on  or  plug-­‐ins.  Minimum  requirements  for  a  WebRTC  enabled  applica,on  are:  1.  A  browser  supporJng  WebRTC  WebAPIs:  –  GetUserMedia   3 2 WebRTC   PSTN  –  PeerConnec,on   Web  Server   Service   WebRTC   Gateway  –  MediaStream   PlaMorm  –  DataChannel   Webapp   Webapp  2.  A  Web  based  plaWorm  with  APIs  enabling  establishment  of  SRTP/SCTP  connec,ons   JavaScript   JavaScript  between  one  or  more  WebRTC-­‐enabled   Internet   1 Browser   Browser  devices  and  other  voice/video  clients  or   SRTP  /  SCTP  services.   Device   Device  3.  A  WebRTC  applicaJon  which  uses  JavaScript  to  access  WebRTC  APIs  exposed  by  browsers  and  WebRTC  service  plaMorms   4   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  5. 5. WebRTC  in  the  Web  Ecosystem     Social  Presence   Rou,ng   Communi,es   HTML  5   GetUserMedia   Libraries   Interworking   Network  APIs   MediaSource   SDKs   Canvas   Audio   Video   CSS   Finished  Services   APPS   Tes,ng   PeerConnec,on   Wholesale   DOM   XHR   CORS   Cer,fica,on   DataChannel   Cloud  Services   Distribu,on   Web   Java   JSEP   Iden,ty  /  Access   Sockets   Script   Updates   Management   Push   Support   Service  Assurance   Specifica,ons   Products   Developer  Support   Service  Models   Technical      Scope      Business/market  5   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  6. 6. WebRTC  Standards  and  SupporJng  FuncJons   WebRTC   Web  Server   suppor,ng   WebRTC  Call   Presence  and   PSTN   Push  Server   Web  Applica,on   func,ons   Control   Directory   Gateway   Web  app   Signaling  JS   HTML,  JS   WebRTC  suppor,ng   JSEP   func,ons  /  APIs   WebRTC  main  func,ons   PeerConnecJon   Push  NoJficaJon   GetUserMedia   API     DataChannel   MediaStream   SDP   IMS  proxy   WebRTC  suppor,ng  func,ons   Other  WebRTC   SRTP  /    SCTP   client   Audio  Codec   Video  Codec   Audio   Video   Transport   User  Agent  (Browser  or  Web  RunJme)   Device   StandardizaJon  acJviJes:   W3C  –  Web  API   IETF  –  Protocol  6   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  7. 7. WebRTC  impacts  on  IP  messaging  Key  disrupJve  facets  of  WebRTC:   Social  Media  •  Client  ubiquity  –  No  need  for  a  messaging   client  to  be  downloaded  •  Unified  communicaJons  –  Audio,  Video   Messaging   Web  Apps   and  Data  channels  •  Integrated  Web  experience  –  no  need  to   switch  between  the  app  and  messaging   client   Gaming   ALL  in  the  browser!   7   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  8. 8. WebRTC  OpportuniJes  for  Network  Operators   1.  Integrated  charging–  Users  already  have  mobile   service.  WebRTC  with  session-­‐based  charging  can   Session  Based   be  added  onto  exis,ng  service  plans.   Charging   2.  Bundling  –  Messaging  APIs  can  augment  WebRTC   apps  with  RCS  and  other  messaging  services   Bundle  APIs   developers  already  know  and  implement.   3.  Reliability  –  QoS  can  provide  assurance  to  users  and   priority  services  (enterprise,  emergency,  law   QoS   enforcement,  eHealth)  that  a  WebRTC  service  will   work  as  well  as  they  need  it  to.   Further  opportuniJes  can  be  realized  through  standards  for:   –  WebRTC  profile  of  OMA  RESTful  APIs   –  Standardized  use  of  OMA  Push  for  WebRTC   –  Anonymous  Customer  Reference  (ACR)  usage  as  calling/called  party   –  Inter-­‐operator  directory  and  rou,ng  capabili,es   –  Inter-­‐operator  charging  and  billing  including  support  for  Third  Party   –  WebRTC  signaling  gateway  into  IMS   –  QoS  RESTful  API   –  WiFi  offload  via  Network  Info  API  for  Web  apps  8   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  9. 9. WebRTC  OpportuniJes  for  Network  Operators   Third  Party  App   Payment   Messages   Locker  3rd  Party   Game   PSTN   XMPP  Gateway   Presence   Push   PlaWorms   gateway   Call  Control   IdenJty   Other  XMPP   CapabiliJes   HTTP  2   Web  Services   SIP   IMS   RESTful  APIs   Web   Sockets  to   Basic  WebRTC   SIP   Operator  APIs   WebRTC  JS  library   Clients   W3C  APIs   NaJve  iOS   Chrome     Firefox   VOLTE   Plain  Old   App   Desktop   Desktop/mobile   RCS   (Voice)   Phone   (WebView)   (WebRTC)   (WebRTC)   9   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  
  10. 10. Key  Conclusions   WebRTC  will  be  a  disrupJve  technology,  for  sure,  but…   It’s  not  so  simple  to  design  a  pure  OTT  service  with   •  Ubiquitous  service  access:  any  device,  anywhere   •  Interoperability  with  exisJng  services   •  PLMN  levels  of  quality  and  reliability     Even  so…   •  OMA  needs  to  help  drive  standards  that  complete  an   end-­‐to-­‐end  WebRTC  service  ecosystem,  fully   integraJng  it  with  exisJng  voice,  video,  and   messaging  services  10   ©  2012  AT&T  Intellectual  Property.  All  rights  reserved.  AT&T  and  the  AT&T  logo  are  trademarks  of  AT&T  Intellectual  Property.  

×