Monetizing Joyn with the REST API

download Monetizing Joyn with the REST API

of 14

  • date post

  • Category


  • view

  • download


Embed Size (px)


This deck was our presentation during the GSMA Joyn Innovation Challenge presentation in Berlin Nov, 8th, 2012 to the developers audience. It is explained briefly our architecture to exoser RCS as REST API and use cases as example.

Transcript of Monetizing Joyn with the REST API

  • 1.Monetizing joyn with the API.Involving 3rd parties in the joynbusiness modelJose Recio Berlin, November 8th, 2012

2. Less Philosophicall Provide enterprise and public sector with mobile multimedia services thatreally help them with their daily choresl Give operators weapons to find use cases where OTT can not reach(yet):l Based on phone numbers, existing agendasl Universal: not linked to specific handset models, no appl Ubiquitous: accessible from any screen ($$ even with no SIM card)l Enterprise - Customer communication: enterprise happy to pay to get theproblem solvedl Value added services: customers customed to pay (till 1 per SMS). Perhapsthe trend for RCS-e: much more services but cheaper, addressing the longtail.l We provide the tools so operator can engage innovation out there withoutlosing control 3. Our Vision: RCS-e as a Platforml RCS-e = OTT chat clone? Only if kept cagedand chainedl Telco added value: beyond person-to-person,exploring A2P & P2Al Object communicationsl OTT not doing that (yet) 4. Whats missing?l Open enablers to innovationengine. APIs as tools sotinkerers can tinker.l Operators: able to opendeveloper accounts by themillions.l Developers: start quickly, withno telco expertise required.Credit:: 5. Towards the Service Storel Service Store vs App Storel No fragmentation, totally portable across platformsl Telco playing leading role, articulating ecosystem & fair revenue sharingwith developers Device/OS manufactures leading roleTelco leading role 6. APIs: Putem on the UNI !!!l Reuse provisioning, policy, security, firewall, accounting, billing, rating,l Totally independent from the core. No impact on redesigns, upgrades,changes of vendors.l Naturally cloudy. Same platform serves different OpCos, even withmismatching service characteristics.l Put the same trust in your developer as in other customers.l Very easy to use: modelled from OTT APIs, no telco expertise needed.l Could be deployed without lengthy carrier approval process.l It works !!! 7. RCS-e/joyn UNI 3rd API Exposuretelco Friendly Telco Border RCS-e Core FTB Rich RCS-e Solu5on Gateway messaging access to SIP internet tools REST API MSRP IMS RCS-e LiveServe internet RTP/ Instant Messaging RTCP CRM AS 3rd party services SBC IMS Core, RCS servers, RCS-e clients DO NOT need any modification UNI 8. Ok,but what can be donewith the joyn API? 9. API to create services. Example: airline customer careSend a boarding pass to a customer by the airline (push)Screen captures from Summitech client for thisdemo proof of concept 10. API to create services. Example: telco customer care l Lorem ipsum dolor sit ametScreen captures from Summitech client for thisdemo proof of concept 11. API to create clients: Web Client for PC & Smartphone 12. API to create clients: Smart TV app clientTV smart APP joyn client 13. See videodemos of joyn basedservices and web/TV joyn clientscreated with the API at: 14. Thanks JFind more about us