WebRTC-Telco Monetization Webinar by Solaiemes

4,123 views
4,070 views

Published on

Slides from our Webinar about WebRTC-Telco monetization.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,123
On SlideShare
0
From Embeds
0
Number of Embeds
2,391
Actions
Shares
0
Downloads
62
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

WebRTC-Telco Monetization Webinar by Solaiemes

  1. 1. WebRTC for Telcos Monetization Webinar slides. Feb, 11th 2014
  2. 2. The  Goal   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
  3. 3. What  is  WebRTC   WebRTC (Web Real-Time Communication) is an API definition being drafted by the World Wide Web Consortium (W3C) to enable browser-tobrowser applications for voice calling, video chat, and P2P file sharing without plugins.
  4. 4. Only  browser  to  browser?   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.
  5. 5. WebRTC    as  a  Carrier  Killer?  
  6. 6. In  the  other  hand?   telcos traditionally Chained to physical end-points….
  7. 7. THIS  WILL  CHANGE  
  8. 8. Telcos  can  broke  the  chains  
  9. 9. Telcos  already  pursuing  the  ubiquity   with mobile or desktop apps
  10. 10. Then……   best communication ubiquity will be the Web based ubiquity
  11. 11. ….but…   Is telco-WebRTC just only about making telco comms ubiquitous ?
  12. 12. NO!
  13. 13. It  is  something  else   WebRTC is the way to create new services and find value added spaces where customers will be happy to pay.
  14. 14. WebRTC  can  enable   ü  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.
  15. 15. MoneIzaIon  models   ü  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.
  16. 16. Solaiemes  WebRTC-­‐Telco  Gateway  
  17. 17. WebRTC-­‐Telco  Gateway  architecture   internet     WebRTC  signalling  &  media   WebRTC   TELCO   Gateway               IMS     OR       SBC   Voice Core Telco  signalling  &  Media   telco   SoMSwitch             UNI   IMS Core or SoftSwitches supporting SIP access DO NOT need any modification
  18. 18. 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
  19. 19. 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.
  20. 20. 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.
  21. 21. 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 preexisting style. Modules include now: •  Simple dialer •  NAB •  Call register •  …more coming soon…
  22. 22. WebPhone.  IniIal  User  Inteface.   Videodemo: https://www.youtube.com/watch?v=q0vClE774aE UI/UX as it is web based could be fully redesigned easily
  23. 23. RCS  Full  (messaging,  voice,  video)  Web  Client       Videodemo: https://www.youtube.com/watch?v=V-DvXcngHnk Combined with RCS Thin Client Server product it is possible to build a RCS web client with all the features, voice+RCS UI/UX as it is web based could be fully redesigned easily
  24. 24. Totally  customizable  UX.  Also  for  mobile  and  tablets  
  25. 25. 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.
  26. 26. 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.
  27. 27. Call-­‐Flows     Example: WebRTC originating voice call
  28. 28. The  key,  the  SDK,  the  new  generaIon  SDP  
  29. 29. The  key?   SDK
  30. 30. 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
  31. 31. SDK  use  cases:  WebRTC  Service  Market   Portal to buy prepaid VAS using WebRTC as callme services hiding your real number, international calls or authorizing SN friends to call you without knowing your number.
  32. 32. 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 nontelco identities.
  33. 33. How  to  make  WebRTC   successful  telcos?  The  keys  
  34. 34. 1    Forget  about  WebRTC  as  a    “service  itself”.  It’s  just  a    technology  that  telcos  can  also    use  for  their  own  business.  
  35. 35. 2    Think  in  WebRTC  as  the    “common  plaQorm  for  media”,    beaer  than  N  different  mobile    and  desktop  OS  ecosystems.  
  36. 36. 3    Think  about  how  old  services    as  PSTN  become  radically    different  were  exposed    through  the  web.    
  37. 37. 4    Unified  CommunicaIons  are    easy  combining  telco  assets,    voice,  video  and  RCS    messaging,  and  available  in  the    browser.  
  38. 38. 5    Not  all  the  legs  of  a    communicaIon  have  to  be    e164,  take  the  most    interconnecIng  different    worlds.  
  39. 39. 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.  
  40. 40. 7    Think  about  different  models    for  VAS  based  and  open  SDK  to    developers  to  build  services  on    top.  
  41. 41. 8    Extend  the  “reach”  of  telco    based  services  making  telco    mulI-­‐screen.  Wherever  you    have  a  screen  you  can  use  your    telco  services.    
  42. 42. 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.  
  43. 43. 10    TIME  IS  MONEY.      ACT  NOW.  
  44. 44. more  about  Solaiemes  
  45. 45. 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
  46. 46. Key  Facts   •  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.
  47. 47. Why  us?   ü 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.
  48. 48. www.solaiemes.com www.webrtcfortelcos.com http://blog.solaiemes.com http://www.youtube.com/solaiemes

×