w3c’s real-time web

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.

SaaS Providers

Cloud Frameworks / APIs

Mobile Phone

Messaging & Real-‐Time CommunicaJons – an overlapping and crowded field

Ø One-stop shop for all communications Ø Flexible charging / service bundling Ø Service assurance Ø Fully interworked communications

Breadth of Services Voice Messaging Video

Market S

egmen

t

~

~

Enterprise

Consumer

Operator Key advantages:

Web & Internet

VOIP/SIP

Mobile Services

Sharing

Voice/Video Conferencing

Unified CommunicaJon SoluJons

Push to Talk

VOIP Apps

2 © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

SMS MMS Webmail

RCS

Social Networking / Media

3

Network Service Providers

API Framework Providers

Applica,on developers

OS PlaMorms

Users Subscribers

Over T

he Top

(OTT)

Network

Infrastructure

WebRTC Service

WebRTC Network APIs

WebRTC PlaMorm gateway

Iden,ty Payment Mul,media Communica,ons Loca,on

Real-‐Time CommunicaJons landscape -‐ an ecosystem perspecJve

IMS

Web PlaWorm and Cloud Service Providers

© 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. 3

Minimum requirements for a WebRTC enabled applica,on are:

1. A browser supporJng WebRTC WebAPIs: –  GetUserMedia –  PeerConnec,on –  MediaStream –  DataChannel

2. A Web based plaWorm with APIs enabling establishment of SRTP/SCTP connec,ons between one or more WebRTC-‐enabled devices and other voice/video clients or services.

3. A WebRTC applicaJon which uses JavaScript to access WebRTC APIs exposed by browsers and WebRTC service plaMorms

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.


What is WebRTC?

Device

Browser

Webapp

JavaScript

1

WebRTC Service PlaMorm

Device

Browser

Webapp

JavaScript

Internet SRTP / SCTP

Web Server

3 2PSTN WebRTC

Gateway

HTML 5

Canvas Audio CSS

DOM XHR

Video

CORS

Web Sockets

Java Script

GetUserMedia

MediaSource

PeerConnec,on

JSEP

Push

DataChannel

Libraries

Communi,es

SDKs

Tes,ng

Distribu,on

Network APIs

Updates

Support

Cer,fica,on Cloud Services

Iden,ty / Access Management

Service Assurance

Interworking

Rou,ng

Social Presence

Specifica,ons

Developer Support

Products

Service Models

APPS Wholesale

Finished Services

Technical Scope Business/market

WebRTC in the Web Ecosystem


User Agent (Browser or Web RunJme)

WebRTC suppor,ng func,ons

PeerConnecJon

Web Server Web Applica,on

Web app HTML, JS

GetUserMedia

Device

SRTP / SCTP

WebRTC main func,ons

WebRTC suppor,ng func,ons

Signaling JS

Audio Video

WebRTC Call Control

JSEP

Push NoJficaJon API

Push Server Presence and Directory

StandardizaJon acJviJes: W3C – Web API IETF – Protocol

Audio Codec Video Codec

WebRTC suppor,ng func,ons / APIs

Transport

SDP IMS proxy


Other WebRTC client

MediaStream DataChannel

WebRTC Standards and SupporJng FuncJons

PSTN Gateway

Key disrupJve facets of WebRTC:

•  Client ubiquity – No need for a messaging client to be downloaded

•  Unified communicaJons – Audio, Video and Data channels

•  Integrated Web experience – no need to switch between the app and messaging client

Social Media

Web Apps

Gaming

Messaging

ALL in the browser!


WebRTC impacts on IP messaging

Session Based Charging

Bundle APIs

QoS

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


WebRTC OpportuniJes for Network Operators

1.   Integrated charging– Users already have mobile service. WebRTC with session-‐based charging can be added onto exis,ng service plans.

2.   Bundling – Messaging APIs can augment WebRTC apps with RCS and other messaging services developers already know and implement.

3.   Reliability – QoS can provide assurance to users and priority services (enterprise, emergency, law enforcement, eHealth) that a WebRTC service will work as well as they need it to.

Web Services RESTful APIs

Presence

Call Control

IMS

PSTN gateway

Third Party App

XMPP Gateway

IdenJty

Push

Payment Messages Locker

HTTP 2 SIP

Web Sockets to

SIP

WebRTC JS library

W3C APIs

Operator APIs

NaJve iOS App

(WebView)

Chrome Desktop (WebRTC)

Firefox Desktop/mobile

(WebRTC)

VOLTE (Voice) RCS

Other XMPP

Game PlaWorms

Plain Old Phone

Clients

CapabiliJes

Basic WebRTC

3rd Party


WebRTC OpportuniJes for Network Operators

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
