WebRTC - On Standards, Identity and Telco Strategy

On Standards, Identity
and Telco Strategy

CTO, Voxeo Labs
Software Developer for 15 years
10 Years Designing Telco APIs

@loopingrage
jose@voxeolabs.com

Headquartered in Menlo Park, California
Creators of Tropo.com
We bridge the gap between Telco and Web
Editors of the WebRTC Speciﬁcation
http://voxeolabs.com

WebRTC is a new API for embedding real-time
communications into web sites and browser-based applications

Voice, Video and even Screen Sharing become
standard capabilities of the modern web browser

Generous Donation of Codecs and Media Framework

http://webrtc.org

API or VoIP 2.0?
WebRTC is more than an API...

It’s a simpliﬁed proﬁle for real-time communications on the Web

Expect a wave of ‘WebRTC-compatible’ devices and non-browser platforms

Mobile, desktop embedded systems will soon begin shipping with compatible
stacks, thereby increasing the already staggering number of RTC-ready platforms
and devices.

Impact of WebRTC
✓ ‘Calling’ becomes a common feature within social networks and business
applications like Facebook, LinkedIn, and SalesForce.com

✓ Company websites become the contact center (i.e. real click to call)

✓ Tons of new collaboration and ‘virtual meeting’ sites will give products like
GoToMeeting and WebEx a run for their money.

✓ Mobile games makers will further incorporate live video and real-time image
processing to provide immersive augmented-reality experiences

✓ Home surveillance and remote monitoring are more convenient and affordable as
sensors, video codecs and network stacks become commoditized

✓ Expect terms like ‘life streaming’ and ‘crowd vision’ to enter the our lives

WebRTC RTCWeb
JavaScript Bindings RTP/SRTP
<video> <audio> SDP
GetUserMedia ICE/TURN
PeerConnection API Codecs
DataChannel API DTLS

ROAP vs JSEP
ROAP was the initial attempt at providing an offer/answer model for
WebRTC. After some experimentation the working group
concluded that ROAP put too much state in the browser making it
difﬁcult, and in some cases impossible, to implement a variety of
advanced use cases and failover models.
JSEP was introduced in Feb‘2012 to address these shortcomings
and is now the standard model for setting up PeerConnections
A great retrospective can be found in the JSEP proposal:
http://tools.ietf.org/html/draft-uberti-rtcweb-jsep-02

MediaConstraint

getUserMedia() getUserMedia()

PeerConnection
MediaConstraint

getUserMedia() getUserMedia()

Putting it all together...
Caller creates new PeerConnection
• Invokes getUserMedia()
• Adds Stream to PeerConnection
• Sends stream ‘description’ to remote party
Callee received description and invokes createAnswer()
• Sends his own description to caller
Caller uses remote description to complete the connection

Demos
GetUserMedia
http://simpl.info/getusermedia/

PeerConnection
http://www.simpl.info/rtcpeerconnection/

MediaConstraints
https://code.google.com/p/webrtc-samples/source/browse/trunk/
demos/html/constraints-and-stats.html

Screen Sharing
https://webrtc-experiment.appspot.com/Pluginfree-Screen-Sharing/

Face Recognition
https://github.com/auduno/headtrackr

Signaling?!?
I thought WebRTC was P2P!

This is a common misunderstanding
WebRTC enables peer-to-peer media but the connection
must still be setup via some form of signaling.
Typical signaling involves the help of a web server with
enough context to route session descriptions to each
participating browser or network.

WebRTC Signaling Triangle

Web Thingy

1 2
4 3

5

Bob Alice

So what’s the protocol?

It’s whatever you want :-)
WebRTC does not specify a signaling protocol
The reasons are simple:
• WebRTC is a media technology (i.e. not just for calls)
• SIP is ﬂexible but way too complicated
• Many sites like Facebook already do signaling

Facebook Signaling

Bob likes your
status “Finally!”

Bob Alice

Facebook Signaling

Call Alice Bob is Calling...

Bob Alice

Picking a Web-signaling protocol
Web signaling introduces new challenges not generally
addressed by traditional signaling protocols
Some dimensions to consider when shopping for a
WebRTC stack:
✓ Single Sign-on
✓ Connection Resume
✓ Multi-endpoint Registration
✓ Mobile Notiﬁcations / App ‘Background’ Support
✓ Chattiness / Battery Life

Anonymous Identity

Web Identity

Telco Identity

Web Ordering. Sponsored Calls.
Dominos Pizza
http://dominos.com Google

S
O
Call Now

IN
M
O
)D
00
(8

URLs = Conference Rooms

http://meet.here/e1qn7

Google Google

Social Network Social Network

http://socialsite.cool Google http://socialsite.cool Google

Bob Alice
San Francisco New York

Web Identity = Web Context

Google

Jorge Rodriguez Acct #772635

Please describe the accident: “Hello Mr. Rodriguez, I see you
Call Now
Call Now got into a fender bender... “

Need help? Click to speak with an agent.
Call Now

Web Partners = Subscriber Value
Google

Robert Scoble

Answer Ignore

* AT&T logo used as a placeholder for demonstration purposes

Google

WebRTC Client SDK

WebRTC Gateway

SBG
Mobile
GW
HSS CSCF

WebRTC Frameworks
The lack of signaling coupled with incompatibilities between
WebRTC implementations has created a need for libraries and
frameworks to accelerate development and lower the barrier of
entry for new applications.
Just as jQuery normalized HTML rendering and event models
between browsers, this new wave of WebRTC frameworks will
provide longevity and backwards compatibility for developers;
allowing them to focus on features and creating value for their
users.

WebRTC Frameworks

Open Source Commercial

http://phono.com http://js.att.io

http://webrtc2sip.org http://zingaya.com
http://resiprocate.org http://tokbox.com

WebRTC Gateways
WebRTC Gateways are server-side nodes that bridge Web clients into an existing
network (e.g. Telco or Enterprise)

WebRTC Gateways will often perform basic protocol conversion and media
adaptation to ensure that both side can communicate without modiﬁcation (e.g.
converting from SRTP to RTP)

However, not all gateways are created equal. Simply delivering SIP to the browser
and performing basic media conversion does not make for a quality user or
developer experience (especially on mobile).

Be sure to ﬁnd a vendor with equal Web and Telco experience.

Gateway Evaluation Criteria
What is the signaling protocol? How well does it work on mobile connections and what is
the impact on battery life?

Does it was with both IMS and legacy MSC/CS network?

What identity models are supported? Telco only? Is that OK?

What codecs are supported? Opus to the endpoints is key for a quality experience.

What happens when users close their browser tab? How long does it take the network to
realize it’s gone?

How are users authenticated? Do they have to log in twice? How are credentials treated in
the browser? Are DTLS certiﬁcates used to verify identity?

What about mobile? How are incoming calls signaled when the app or browser is in the
background?

And most importantly: how quick can my vendor apply ﬁxes and updates? WebRTC is still
evolving but the telco industry can’t afford to sit and wait. Gateway vendors must be able to
adapt quickly to web browser changes, regressions and incompatibilities.

Today - Innovation on Devices

Carrier
Your Carrier
Network

Developers Consumers

© Voxeo Corporation | CONFIDENTIAL
© Voxeo Corporation
42

Today - OTT Players

Your
Network

Infrastructure

43

CaaS - Communications as a Service

Apps
APIs
Your
Network! WebRTC

Services

Developers
Subscribers

44

Strategy #1 - Network Exposure

Developers

$

Location Payment Voice Messaging APIs

HSS S-CSCF I-CSCF P-CSCF Network


46

Use Cases: User Calls App

Conference Line

Conferencing Contact Center

Surveys + Voting Self-Service

Voice Search Info Lookup

13

Use Cases: App Calls User

Appointment
Reminder

Appointment Reminder Click-to-Call

Voice Broadcast Emergency Response

Conditional Dial Security Veriﬁcation

14

Strategy #1 - Network Exposure

This is the most common API approach being taken by carriers

The idea is simple: open the network and charge for transactions and usage.

The main targets for this model are:
• 3rd Party Developers - Long Tail and Enterprise Customers
• 2nd Party Developers - Cloud Partners and System Integrators
• 1st Party Developer - Internal Teams use APIs to launch services
The challenge with this approach is that the focus is on the network instead of users

Networks are becoming commoditized. Aligning a strategy around the network does
not create incremental value for end users.

Strategy #2 - User Centric
Rather that build a platform around the network, start with amazing services and then
build a platform / developer ecosystem around your users

Model repeatedly proven by Internet companies
• Facebook was a website before it was a platform
• LinkedIn was a website before it was a platform
• Apple set out to build the world’s coolest phone before even considering an App Store
Happy users attract developers. Developers and apps attract more users.

User-Centric Network Eﬀect
Users are the operator’s most valuable asset

Users represent data and potential customers for developers

In other words... users attract developers

Ameche enables developers to enhance the mobile experience thereby creating value

Value comes in the form of user satisfaction, new users and new revenue

Happy users produce more users; which attracts more developers

The cycle creates a positive network effect

Developer Developer Portal Operator CMO Network Apps Catalog Subscriber

Users Attract Developers

* AT&T logo used as a placeholder for demonstration purposes

CRM Integration

The Problem The Solution - Integrated Call Logging
Sales people forget to log their calls in their CRM When a sales person receives a call, this triggers a look-up using the called number and
(e.g. SalesForce.com) resulting in incomplete preferred CRM package. If the number matches one of the clients’ phone numbers, this
analytics and missed business opportunities. creates a further trigger to display the calling client’s information. In addition, all
communications with clients are recorded and uploaded in real-time to Salesforce.com or
the preferred CRM package.

Retail Price - $5-7 per user/month

8

In-Call Assistant

The Problem The Solution - Voice Activated In-Call Assistant
Taking notes while driving is dangerous. What if Through the power of your voice: record calls, take notes that upload to Evernote, listen
you could activate an in-call assistant to take and send email / SMS / IM / Tweet / to do list / blog posts, receive whisper meeting alerts
notes, transcribe the call to text and send you an during calls that only you hear, add people to calls, divert calls to other devices, check your
email or MMS message when you hang up? calendar to add or change appointments, and lots more…

Retail Price - $1-3 per user/month

[CHIME] “This call is being
“Record this call” recorded...”
“Recording sent”

8

Social Weaving

The Opportunity The Solution - Social Call Activity. Social Caller ID.
Social Networking sites like Facebook and With Ameche, operators can weave real-time voice and text conversations into social
LinkedIn have changed the way people streams. For example, a service can be created that logs call activity and SMS messages to
communicate. the user’s
Rather than ﬁght this movement, operators have public or private activity feed on Facebook, allowing then to see all their conversations in
an opportunity to integrate the mobile one place. Called you mom on her birthday? You get a ‘good daughter’ badge :-)
experience with these services to create brand
continuity and stickiness with consumers. Another service could trigger a real-time call Social Caller ID window on LinkedIn with the
caller’s proﬁles and latest activity steam. Ameche makes these types of real-time interaction
very simple for operators to deploy using public APIs.

8

WebRTC - On Standards, Identity and Telco Strategy

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à WebRTC - On Standards, Identity and Telco Strategy

Similaire à WebRTC - On Standards, Identity and Telco Strategy (20)

Dernier

Dernier (20)

WebRTC - On Standards, Identity and Telco Strategy