webrtc-telco monetization webinar by solaiemes
DESCRIPTION
Slides from our Webinar about WebRTC-Telco monetization.TRANSCRIPT
WebRTC for Telcos Monetization
Webinar slides. Feb, 11th 2014
q Helping telcos to add value to their current services and enabling new services.
q Making fix & mobile voice available using a web-browser ubiquitously
q Engage the customers & reduced the churn
The Goal
WebRTC (Web Real-Time Communication) is an API definition being drafted by the World Wide Web Consortium (W3C) to enable browser-to-browser applications for voice calling, video chat, and P2P file sharing without plugins.
What is WebRTC
NO!
It could be implemented a WebRTC – Telco Gateway to as a bridge between Web and fix/mobile operator networks allowing service providers to extend their communication services to the Internet. It means creating web-based telco end-points.
Only browser to browser?
WebRTC as a Carrier Killer?
telcos
traditionally
Chained to
physical
end-points….
In the other hand?
THIS WILL CHANGE
Telcos can broke the chains
with mobile
or desktop apps
Telcos already pursuing the ubiquity
best communication ubiquity will be the Web based ubiquity
Then……
Is telco-WebRTC just only about making telco comms ubiquitous ?
….but…
NO!
WebRTC is the way to create new services and find value added spaces where customers will be happy to pay.
It is something else
ü Home Office customized communication.
ü Customer care use cases.
ü Interconnecting social identities with telco identities
ü Enable concepts as “callable” while keeping private the phone number (e.164).
ü Creating “non physical second lines”, no wire, no SIM
ü And put to work external talent with SDK for developers.
WebRTC can enable
ü Reducing churn and defending current prices adding value. A PSTN ubiquitous in the browser is more than a PSTN
ü New services that could be charged by “minute”, prepaid international calling cards accessible via WebRTC, etc
ü New services that could be charged to the called party by making them callable without disclosing the number.
MoneIzaIon models
Solaiemes WebRTC-‐Telco Gateway
internet WebRTC TELCO Gateway
Web
RTC sig
nalling & m
edia
Voice Core OR
IMS
SoMSwitch
SBC
UNI
IMS Core or SoftSwitches supporting SIP access DO NOT need any modification
telco
WebRTC-‐Telco Gateway architecture
Telco sig
nalling & M
edia
Feasible as Cloud based architecture
The WebRTC-Telco GW can be deployed outside the telco premise, in a public or private cloud as the access to the network core is UNI based
The plaQorm. WebRTC-‐Telco GW
q Hardware. Intel based server architecture running Linux (Dell, HP, IBM), no special HW needed, also deployable in public clouds as AWS and virtualized environment for cloud computing as Cisco UCS.
q Scalable to the number of concurrent calls and users online needed .
q A single platform could serve different cores, multi-tenancy available.
q A single platform could serve different UX for different customers profiles.
q It could be combined with RCS Thin Client Server to provide an all-in-one Unified Communications experience: voice, video and enriched messaging.
q Supporting current WebRTC capable Web-Browsers: Google Chrome & Mozilla Firefox for Windows, Mac & Linux and Chrome for Android.
Features q Via WebRTC instanced e-164 identity based phone
q Outgoing voice-calls / Incoming voice-calls
q UI/UX modules
ü Dialer
ü NAB (network address book) . Possible easy integration with 3rd party NAB.
ü Call History (starting time, call duration, missed/answered/rejected icons)
q UI/UX customizable with customer logo and colors. Also possible full re-design
q UI/UX could include RCS capabilities when combined with RCS Thin Client Server Product
q RCS Videoshare and IP Videocall capable
q For the of RCS services with separated voice & RCS cores, dual register capable.
q Login with credentials not exposing real IMS/Softswitch credentias). Security.
q HTTPS available for signalling.
q Plug&Play on top of SIP Servers, SoftSwitch with SIP access, IMS. Proven in 3 telcos from 3 countries. Also could be integrated with legacy PSTN.
SDK and embeddable modules
q The javascropt SDK allows to use Voice/Videocapabilities in your website freely.
q Embeddable modules make even easier to add WebRTC to third party websites or applications. Just embedding the pre-designed modules with CSS3 configuration to adapt to whatever UX pre-existing style. Modules include now:
• Simple dialer
• NAB
• Call register
• …more coming soon…
WebPhone. IniIal User Inteface.
Videodemo: https://www.youtube.com/watch?v=q0vClE774aE
UI/UX as it is web based could be fully redesigned easily
RCS Full (messaging, voice, video) Web Client
Videodemo: https://www.youtube.com/watch?v=V-DvXcngHnk
UI/UX as it is web based could be fully redesigned easily
Combined with RCS Thin Client Server product it is possible to build a RCS web client with all the features, voice+RCS
Totally customizable UX. Also for mobile and tablets
RCS vs WebRTC
WebRTC is not a rival service of RCS nor telco communications, instead it is a great tool for telcos to extend their end-point portfolio, and leverage a more ubiquitous reach of their enablers.
WebRTC-‐Telco GW internal architecture
The platform includes the web-server to serve the “WebPhone” but it could be served from other server as in the case of future WebRTC cases using the SDK.
Call-‐Flows
Example: WebRTC originating voice call
The key, the SDK, the new generaIon SDP
The key?
SDK
Telco services deployed in days
Javascript SDK as tool to create easily telco services as: • prepaid call-me
services. • creating casual
access to telco comms
• interworking with OTTs, etc
SDK use cases: WebRTC Service Market
Portal to buy prepaid VAS using WebRTC as call-me services hiding your real number, international calls or authorizing SN friends to call you without knowing your number.
The business?
A market of WebRTC services based on telco capabilities, causal services to engage the users and extending the reach of telco driven comms. Self-service web based market of premium services based on WebRTC. Innovation connecting telco and non-telco identities.
How to make WebRTC successful telcos? The keys
1 Forget about WebRTC as a “service itself”. It’s just a technology that telcos can also use for their own business.
2 Think in WebRTC as the “common plaQorm for media”, beaer than N different mobile and desktop OS ecosystems.
3 Think about how old services as PSTN become radically different were exposed through the web.
4 Unified CommunicaIons are easy combining telco assets, voice, video and RCS messaging, and available in the browser.
5 Not all the legs of a communicaIon have to be e164, take the most interconnecIng different worlds.
6 In a mulI-‐idenIty scenario e.164 could become the last resort of privacy, use WebRTC to enable ways to reach e.164 without knowing the e.164 to be called.
7 Think about different models for VAS based and open SDK to developers to build services on top.
8 Extend the “reach” of telco based services making telco mulI-‐screen. Wherever you have a screen you can use your telco services.
9 Don’t be concerned about the latest feature of a given OTT, make them concerned about your last blue ocean discovered thanks to the WebRTC SDK.
10 TIME IS MONEY. ACT NOW.
more about Solaiemes
Team Juan developed his career in several companies as Motorola (Networks and Mobile Devices divisions), DMR Consulting (now Everis), ICEX (Spanish Foreign Trade Office) and Colortex. Juan holds an MSc degrees in Telecom Engineering from Polytechnics University of Valencia (Spain), an MSc in Economics from UNED (Spain) and a Diploma in Politics from the University of London (Lead College, LSE). http://www.linkedin.com/in/juanmateu
Jose has developed his career in Motorola and Ceselsa-Indra Mr. Recio holds an MSc in Telecom Engineering from Universidad Politécnica de Madrid and an MSc (Distinction) in Information Security from Royal Holloway College, University of London. http://www.linkedin.com/in/chema
Luis had previous roles at Motorola and Alcatel. developing Switching, GSM coverage planning and IMS software. Also worked at Textil Bondrap. Mr. Valencia holds an MSc degree in Telecommunications Engineering from the Polytechnics University of Valencia (Spain). http://www.linkedin.com/in/luisvalencia
David developed his career in Motorola, Altran SDB and Consum SCV. David holds an MSc degree in Telecom Engineering from Polytechnics University of Valencia (Spain) and an executive MBA from EOI Business School (Spain). http://www.linkedin.com/in/davidculebras
• Started activities in 2007 trying to open Push to Talk and IMS VideoShare as REST API. Pivoted to RCS API exposure in 2010, 1st to market solution and editors of the GSMA spec on RCS API.
• Awarded in 2011 as pioneers in the area: GSMA RCS Innovation Winner.
• Staff: 15. Growth planned. HQ in Madrid (Spain).
• Currently with contracts in 4 tier-1 telco groups and several opportunities opened in 3 continents.
• GSMA API provider for Joyn Innovation Accelerator.
• Accreditation for API GW and Web Solution submitted.
Key Facts
ü Solaiemes is solving a real problem telcos have. To find a new role and make their assets a platform in the way that developers can use them, as API. Solaiemes is recognized by pioneering this field in the next telco messaging, RCS joyn & also the use of WebRTC with Telco approach
ü Solaiemes team is experienced, visionary, with international experience in several continents and able to do more with less and execute.
Why us?
www.solaiemes.com
www.webrtcfortelcos.com
http://blog.solaiemes.com
http://www.youtube.com/solaiemes