rcs-e api exposure
DESCRIPTION
RCS-e API exposure:A valuable asset to create application innovation & revenue generation?Solaimes keynote at IMS Global Congress 2011 (Madrid, 5/OCt/2011)TRANSCRIPT
![Page 1: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/1.jpg)
RCS-e API exposure:A valuable asset to create application innovation & revenue generation?
Madrid, 5th October 2011
![Page 2: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/2.jpg)
Lessons from the past
Communications are more than person to person
![Page 3: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/3.jpg)
Lessons from the past
All device-tiers & all MNO’s services tend to
succeed
![Page 4: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/4.jpg)
Lessons from the past
When the enabler is “usable” by the ecosystem
to create cases on top, it is enriched with not
initially thought use cases.
![Page 5: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/5.jpg)
Lessons from the past
Telcos got huge revenues from
ecosystem created use cases
![Page 6: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/6.jpg)
Lessons from the past
Yes, the SMS
![Page 7: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/7.jpg)
Lessons from the past
Oops!
![Page 8: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/8.jpg)
The present…
Does it matters NOW ?
![Page 9: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/9.jpg)
The present…
YES!
![Page 10: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/10.jpg)
The present…
RCS-e
![Page 11: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/11.jpg)
The present…
RCS-e is:
Instant Messaging
File Transfer
VideoShare
….all from your phonebook
![Page 12: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/12.jpg)
The present…
RCS-e aims to:
Be present in all device tiers
Be offered by all/most of MNOs
![Page 13: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/13.jpg)
The present…
The delay of the RCS launch brings an
interesting scenario
![Page 14: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/14.jpg)
The present…
OTTs already launched successfully
• Huddle
• iMessage
• Blackberry Messenger
• …others
![Page 15: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/15.jpg)
The present…
Not bad… OTTs did the harsh task of
evangelizing
![Page 16: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/16.jpg)
The next future…
RCS-e becomes REAL
![Page 17: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/17.jpg)
The next future…
G5 Telcos expected to
launch soon
(Q411 to Q2/12)
![Page 18: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/18.jpg)
The next future…
Could telcos compete with
stablished OTT messaging
competitors ?
![Page 19: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/19.jpg)
The next future…
Yes, of course
![Page 20: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/20.jpg)
The next future…
Focusing in replicate
SMS strengths
![Page 21: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/21.jpg)
The next future…
All device tiers capable
![Page 22: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/22.jpg)
The next future…
Universal service
![Page 23: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/23.jpg)
The next future…
Openness
![Page 24: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/24.jpg)
The next future…
Thinking in RCS-e as
enabler, not as final
application
![Page 25: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/25.jpg)
The next future…
In SMS is was done
with SMS Gateways
![Page 26: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/26.jpg)
The next future…
Lots of cases created
with simple APIs
![Page 27: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/27.jpg)
The next future…
Alerts (banking, etc)
SMS to TV
M-commerce: ringtones, wallpapers
Voting
Etc…
![Page 28: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/28.jpg)
The next future…
Remember !!!
![Page 29: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/29.jpg)
The next future…
Friendly APIs for the
developers ecosystems
![Page 30: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/30.jpg)
The next future…
You know…REST, WS…
![Page 31: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/31.jpg)
The next future…
![Page 32: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/32.jpg)
The next future…
Not PARLAY ! please
![Page 33: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/33.jpg)
Apps vs Enabler
Ok, ok, but App model
already succeed, doesn’t it?
![Page 34: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/34.jpg)
Apps vs Enabler
Not really!
![Page 35: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/35.jpg)
Apps vs Enabler
Smartphone growth is real
![Page 36: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/36.jpg)
Apps vs Enabler
The model 1 use case 1 app
not so successful
![Page 37: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/37.jpg)
Apps vs Enabler
The most successful apps are:
Browser
Messaging Apps
![Page 38: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/38.jpg)
Apps vs Enabler
YES, communication enablers
![Page 39: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/39.jpg)
Apps vs Enabler
Make RCS-e a “app-solution” driver
![Page 40: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/40.jpg)
The telco business
From downloadable Apps
to
“phonebook service contacts”
![Page 41: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/41.jpg)
Easing Innovation
The telco business
![Page 42: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/42.jpg)
Attracting 3rd party Innovation to
empower the telco enabler
The telco business
![Page 43: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/43.jpg)
App Stores are owned and
managed by device/OS
manufacturers
The telco business
![Page 44: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/44.jpg)
“Service Contact Stores” would be
owned and managed by MNO’s
The telco business
![Page 45: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/45.jpg)
A great difference !
The telco business
![Page 46: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/46.jpg)
And also possible win-win revenue
sharing with “service contact” use
case developers
The telco business
![Page 47: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/47.jpg)
Could exist a middle point?
The telco business
![Page 48: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/48.jpg)
YES, apps using RCS-e APIs as
comms enabler
The telco business
![Page 49: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/49.jpg)
Telco still being more than mere pipe
The telco business
![Page 50: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/50.jpg)
And offering API’s as OTT comms, it
is easier to optimize the network
usage.
The telco business
![Page 51: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/51.jpg)
Ok, Ok, but…when this scenario with
RCS-e APIs would become real in
the field ?
The telco business
![Page 52: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/52.jpg)
Let’s say….
The telco business
![Page 53: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/53.jpg)
TODAY !
THE HOPE
![Page 54: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/54.jpg)
examples
mash-up Google Weather via RCS-e: http://www.youtube.com/watch?v=iiIcoJUNcTMmash-up Google Translate via RCS-e: http://www.youtube.com/watch?v=bt7CKoCHl_sCRM m-banking demo: http://www.youtube.com/watch?v=DQGINTJEEmYCouponing mash-up: http://www.youtube.com/watch?v=J2CTNliGL0oSocial Plug/connector (FB y Twitter): http://www.youtube.com/watch?v=BatGfIpjMHARCS-e WebClient JQuery: http://www.youtube.com/watch?v=tY8M1t1F2P4Securizing payments http://www.youtube.com/watch?v=5wR9SeM3WE0Bridging XMPP & RCS-e http://www.youtube.com/watch?v=zF_roI2IOA0
![Page 55: RCS-e API Exposure](https://reader034.vdocuments.site/reader034/viewer/2022052321/554bfbd5b4c9058e098b486f/html5/thumbnails/55.jpg)
www.solaiemes.com
Addtional info:
http://www.rcseopenandubiquitous.com/
http://www.youtube.com/solaiemes
http://www.slideshare.com/solaiemes
http://blog.solaiemes.com