WebRTC Workshop The HTML5 Real-Time Web

October 28th 2013

Pre-conference Workshop for Rich Communications

Alan Quayle

alan@alanquayle.com

www.alanquayle.com/blog

10/29/2013 © 2013 Alan Quayle Business and Service Development 1

Objectives

• Bring together deep technical and deep business thought leadership

on WebRTC with Tim Panton, Juan Mateu, Victor Pascual Ávila and

Alan Quayle with a unique independent workshop.

• Provide a deep-dive quantified analysis of the WebRTC status,

enabling attendees to understand what is likely to emerge over the

next 18 months to 2 years, in this complex rapidly emerging

ecosystem and what it will mean to their business.

• Provide attendees with a series of WebRTC demonstrations, to share

their experiences on implementing WebRTC.

10/29/2013 © 2013 Alan Quayle Business and Service Development 2

Structure • Introduction to WebRTC and Initial Market Review - Alan

o What is it and what it is not,

o Cutting through the mis-information and hype

o Non-technical introduction

o Web browser implementation status

o Taxonomy of suppliers / service providers

o Codecs and devices – is certification necessary?

o What is Google’s aim?

• Technology deep dive – Tim (plus demo)

o Quick review of the standards

o Peer connect API

o Setting up local media and media flow

o Protocols

o WebRTC triangle / trapezoid

o SIP, Jingle and the PSTN.

Structure

• What WebRTC means to Service Providers and RCS: Juan (plus demo)

o Extending enhanced communications services to web browsers

o Impact on OTT (Over The Top) and existing voice, messaging, video and VAS

o Impact of device compliance

o Customer experiences and behaviors

o Revenue, churn and relevance impacts

• What WebRTC means to enterprises: Victor (plus demo)

o Impact on Unified Communication and the Contact Center

o Impact on company’s website

o Security and operational issues

o Potential cost savings and innovations

Introduction to WebRTC and Initial Market Review

What The Geeks Say

Open, Nothing Proprietary

No Plugs-Ins

Multi Platform / Device

Real-time stuff for your browser with no plug-ins

M2M and Telematics

Surveillance & Monitoring

Lots & Lots & Lots of Devices

Embedding Communications

Everywhere!

Video Codec Wars?

VP8/9 H.264/5

© 2013 Alan Quayle Business and Service Development 20

VP8/9 will be

everywhere

H.264 is mobile

handsets

Agree to Disagree and Let the Market Decide

Will IETF’s history in voice codecs (Opus) be repeated in video?

Browser GetUserMedia PeerConnection DataChannel

Chrome Yes Yes Yes

Chrome for mobile Yes (March ‘13) Yes (March ‘13) Yes

Firefox (desktop) Yes Yes Yes (first one)

Firefox (mobile) Yes Yes Yes (first one)

Opera Yes Yes 2014

Opera Mini Yes 2014 2014

IE (desktop) Chrome Frame / 2014

Chrome Frame / 2014

Chrome Frame / 2014

IE (mobile) 2014/2015 2014/2015 2014/2015

Safari (desktop) 2014/2015 2014/2015 2014/2015

Safari (mobile) 2014/2015 2014/2015 2014/2015

WebRTC is NOT Everywhere

Increasingly see WebRTC native on the device

Lies, Damned Lies, and Statistics

Regardless IE Matters

Microsoft IE still accounts for over 82.3% of Enterprise Browsers

Mobile is Even More Complex

Native browser Natively in OS 2nd browser 3rd party SDK

Business

Technology

Business

Technology Latency Efficiency Resilience Performance Implementation Complexity

Supporting Devices Ecosystem Support

Customer Needs Interoperability

Use Cases IPR

Optional Codec Diversity will Reign

And With Transcoding Comes

30

Delay

Third Parties

Packet Loss

Quality Loss

Cost

There’s No Approval Process

In The Limit Which Browser Gives you the Best Experience?

Device base supporting WebRTC

Copyright Disruptive Analysis Ltd 2013

Feb 2013

Mil

lio

n

Source: Disruptive Analysis WebRTC Strategy Report, Feb 2013 Definitions & methodology in report - See disruptivewireless.blogspot.com for details

0

500

1000

1500

2000

2500

3000

3500

4000

Tablets

Smartphones

PCs

The WebRTC Train has left the station and it isn’t going to wait for Telecom

WebRTC is a car without wheels!

WebRTC Triangle

• Both browsers running the same web application from web server

• Peer Connection media session is established between them

• Signaling is not standardized, could be SIP, Jingle, proprietary. Uses HTTP or WebSockets for transport

Web Server (Application)

Browser M (Running HTML5 Application

from Web Server)

Browser L (Running HTML5 Application

from Web Server)

Peer Connection (Audio, Video, and/or Data)

36 Intro to WebRTC February 2013

The wheels!

The Beauty and Value of WebRTC is when we mash it up with other stuff

A Telcos Two Unique Assets

Keep Calm and

Do SOMETHING

(Just NOT THROUGH

THE GSMA or TMF)

HMS Government Advisory

Impact of WebRTC?

• Voice becomes just like all your other communications: organized into your

preferred social or office tools.

• It will be important for the IMS/RCS world to inter-operate with the

WebRTC world, currently these browsers will be a closed book to IMS. For

RCS to become pervasive, it cannot remain trapped in phones that have

implemented the IMS/RCS client.

• For all the OTT (Over The Top) applications, they can now use their

"directory service" i.e. your list of contacts also using their service to enable

Viber / Skype / Whatsapp everywhere. On your PC, smartphone, tablet, TV;

and they can offer chargeable services without Apple taking 30%.

• As long as you're data connected, communications is in the cloud, people

need only break out to PSTN when the other person is not data connected,

or the call quality is too low due to their internet connection. PSTN

becomes the communications path of last resort!

Impact of WebRTC?

• The company's website now becomes its call center front end. A weblog

becomes your personal communications assistant.

o Lots of start-ups in this space

• Communication service aggregators save customers running multiple clients

on their phone, that would run in the cloud and be controlled from the

browser.

• Click to call doesn't require an operator's voice network, just access to the

internet.

• Communications becomes like using any application on a smartphone,

users can add features, capabilities, people throughout a call, e.g. N-way

calling finally becomes simple and obvious with a simple point and swipe.

• Directory services become critical sources of value in connecting all the

different IDs: telephone numbers, SIP IDs (IDentifier), web session IDs,

other OTT IDs, etc.

Impact of WebRTC?

• VAS (Value Added Services) leaves telco. Any web developer can create value and

solve problems for customers, it the customer who will decide, and those developers

who fail fastest win the innovation race.

• Advertising finally enters the communications space, opening up business model

innovation.

• New CRM (Customer Relationship Management) methods: click from email, from

webpage, from app, from TV. The ability to communicate becomes embedded in

most transactions.

• QoS (Quality of Service) remains an issue, but for the people using Vonage and Skype

over the years will attest, QoS is rarely an issue.

• Your phone number is no longer relevant anymore. It's a gateway to the past.

Customers will only know the PSTN is involved because of the poor audio quality

(G.711) – BUT it is the customers only unique ID that they own.

• Gaming becomes interesting as all the devices become controllers using gesture

controls as well as the more traditional methods for network-based games.

Other Telco Impacts

• Impact of WebRTC on IP Messaging

o No need to for a messaging client to be downloaded

o Unified communications across voice, video and data

o Integrated experience across the web and communications client

• Opportunities

o Integrated charging

o Bundle APIs: WebRTC, RCS API, payment API, Call Control APIs

o QoS for those willing to pay (those running their business on your network)

• QoS API? NO! keep that for YOUR / PARTNER SERVICES

o Extend network services over the web

o Enhance enterprise Unified Communication offers

o Enhance OTT? Why they’re competitors!

o Gateway for the WebRTC codec mess – enable successful communications

o Web phone for existing customers

Key Points

• Voice traffic is going to be through the web

• Browsers are the new endpoints

• A website of a company can be the call center

• An individual’s website (Facebook Page) their communications

assistant

• Security, identity and privacy are very important

o Telephone number is not important unless operators pull their finger out!

• New business opportunities abound

DO Communications

better thaN the

competition

ELSE BE AN ISP

HMS Government Advisory