Webrtc workshop from Alan Quayle
Upcoming SlideShare
Loading in...5
×
 

Webrtc workshop from Alan Quayle

on

  • 1,848 views

WebRTC Workshop from Alan Quayle given at the WebRTC pre-conference workshop at Rich Communications in Berlin, 28th Oct 2013

WebRTC Workshop from Alan Quayle given at the WebRTC pre-conference workshop at Rich Communications in Berlin, 28th Oct 2013

Statistics

Views

Total Views
1,848
Views on SlideShare
1,185
Embed Views
663

Actions

Likes
1
Downloads
68
Comments
0

6 Embeds 663

http://alanquayle.com 612
http://cloud.feedly.com 19
http://reader.aol.com 12
http://newsblur.com 8
http://www.newsblur.com 8
http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Webrtc workshop from Alan Quayle Webrtc workshop from Alan Quayle Presentation Transcript

  • 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 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 it and what it is not, 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 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 • Extending enhanced communications services to web browsers 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!
  • H.264/5 VP8/9 Video Codec Wars?
  • VP8/9 will be everywhere H.264 is mobile handsets Agree to Disagree and Let the Market Decide © 2013 Alan Quayle Business and Service Development 20
  • Will IETF’s history in voice codecs (Opus) be repeated in video?
  • WebRTC is NOT Everywhere Browser GetUserMedia PeerConnection DataChannel Yes Yes Yes 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 Chrome Chrome for mobile 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
  • Supporting Devices Ecosystem Support Customer Needs Interoperability Use Cases IPR Business Technology Latency Efficiency Resilience Performance Implementation Complexity
  • Optional Codec Diversity will Reign
  • And With Transcoding Comes Cost Delay Third Parties Quality Loss Packet Loss 30
  • There’s No Approval Process
  • In The Limit Which Browser Gives you the Best Experience?
  • Device base supporting WebRTC 4000 Million 3500 Tablets 3000 Smartphones 2500 PCs 2000 1500 1000 500 0 Source: Disruptive Analysis WebRTC Strategy Report, Feb 2013 Definitions & methodology in report - See disruptivewireless.blogspot.com for details Copyright Disruptive Analysis Ltd 2013 Feb 2013
  • The WebRTC Train has left the station and it isn’t going to wait for Telecom
  • WebRTC is a car without wheels!
  • WebRTC Triangle Web Server The wheels! (Application) Peer Connection (Audio, Video, and/or Data) Browser L Browser M (Running HTML5 Application from Web Server) (Running HTML5 Application from Web Server) • 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 Intro to WebRTC February 2013 36
  • 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 o Unified communications across voice, video and data o • No need to for a messaging client to be downloaded 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