Downloaded 96 times
Uploaded bySolaiemes
RCS-e API Exposure
The document discusses the RCS-e API as a significant asset for driving application innovation and revenue generation for telcos. It emphasizes the potential of RCS-e to enhance communication services and compete with established OTT messaging platforms by leveraging existing SMS strengths and creating new use cases. Furthermore, it outlines the necessity of friendly APIs for developers to foster innovation and collaboration within the telecommunications ecosystem.
More Related Content
![[Mobile Future] Craig Marschall-Nicholls, Jibe Mobile](https://cdn.slidesharecdn.com/ss_thumbnails/jibemobile-121203063206-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
RCS-e API Exposure
- 1. RCS-e API exposure: A valuable asset to create application innovation & revenue generation? Madrid, 5th October 2011
- 2. Lessons from thepast Communications are more than person to person
- 3. Lessons from thepast All device-tiers & all MNO’s services tend to succeed
- 4. Lessons from thepast When the enabler is “usable” by the ecosystem to create cases on top, it is enriched with not initially thought use cases.
- 5. Lessons from thepast Telcos got huge revenues from ecosystem created use cases
- 6. Lessons from thepast Yes, the SMS
- 7. Lessons from thepast Oops!
- 8. The present… Does itmatters NOW ?
- 9.
- 10.
- 11. The present… RCS-e is: Instant Messaging File Transfer VideoShare ….all from your phonebook
- 12. The present… RCS-e aims to: Be present in all device tiers Be offered by all/most of MNOs
- 13. The present… The delayof the RCS launch brings an interesting scenario
- 14. The present… OTTsalready launched successfully • WhatsApp • Huddle • iMessage • Blackberry Messenger • …others
- 15. The present… Not bad…OTTs did the harsh task of evangelizing
- 16. The next future… RCS-ebecomes REAL
- 17. The next future… G5Telcos expected to launch soon (Q411 to Q2/12)
- 18. The next future… Couldtelcos compete with stablished OTT messaging competitors ?
- 19. The next future… Yes,of course
- 20. The next future… Focusingin replicate SMS strengths
- 21. The next future… Alldevice tiers capable
- 22. The next future… Universalservice
- 23.
- 24. The next future… Thinkingin RCS-e as enabler, not as final application
- 25. The next future… InSMS is was done with SMS Gateways
- 26. The next future… Lotsof cases created with simple APIs
- 27. The next future… Alerts(banking, etc) SMS to TV M-commerce: ringtones, wallpapers Voting Etc…
- 28.
- 29. The next future… Friendly APIs for the developers ecosystems
- 30. The next future… Youknow…REST, WS…
- 31.
- 32. The next future… NotPARLAY ! please
- 33. Apps vs Enabler Ok, ok, but App model already succeed, doesn’t it?
- 34. Apps vs Enabler Notreally!
- 35. Apps vs Enabler Smartphonegrowth is real
- 36. Apps vs Enabler Themodel 1 use case 1 app not so successful
- 37. Apps vs Enabler Themost successful apps are: Browser Email Messaging Apps
- 38. Apps vs Enabler YES,communication enablers
- 39. Apps vs Enabler MakeRCS-e a “app-solution” driver
- 40. The telco business From downloadable Apps to “phonebook service contacts”
- 41. The telco business EasingInnovation
- 42. The telco business Attracting3rd party Innovation to empower the telco enabler
- 43. The telco business AppStores are owned and managed by device/OS manufacturers
- 44. The telco business “ServiceContact Stores” would be owned and managed by MNO’s
- 45. The telco business Agreat difference !
- 46. The telco business Andalso possible win-win revenue sharing with “service contact” use case developers
- 47. The telco business Couldexist a middle point?
- 48. The telco business YES,apps using RCS-e APIs as comms enabler
- 49. The telco business Telcostill being more than mere pipe
- 50. The telco business Andoffering API’s as OTT comms, it is easier to optimize the network usage.
- 51. The telco business Ok,Ok, but…when this scenario with RCS-e APIs would become real in the field ?
- 52.
- 53.
- 54. examples mash-up Google Weathervia RCS-e: http://www.youtube.com/watch?v=iiIcoJUNcTM mash-up Google Translate via RCS-e: http://www.youtube.com/watch?v=bt7CKoCHl_s CRM m-banking demo: http://www.youtube.com/watch?v=DQGINTJEEmY Couponing mash-up: http://www.youtube.com/watch?v=J2CTNliGL0o Social Plug/connector (FB y Twitter): http://www.youtube.com/watch?v=BatGfIpjMHA RCS-e WebClient JQuery: http://www.youtube.com/watch?v=tY8M1t1F2P4 Securizing payments http://www.youtube.com/watch?v=5wR9SeM3WE0 Bridging XMPP & RCS-e http://www.youtube.com/watch?v=zF_roI2IOA0
- 55.