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.
Monetizing joyn with the API.Involving 3rd parties in the joynbusiness modelJose Recio Berlin, November 8th, 2012
Less Philosophical…l Provide enterprise and public sector with mobile multimedia services that really 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 agendas l Universal: not linked to specific handset models, no app l Ubiquitous: accessible from any screen ($$ even with no SIM card) l Enterprise - Customer communication: enterprise happy to pay to get the problem solved l Value added services: customers customed to pay (till 1€ per SMS). Perhaps the trend for RCS-e: much more services but cheaper, addressing the long tail.l We provide the tools so operator can engage innovation out there without losing control
Our Vision: RCS-e as a Platforml RCS-e = OTT chat clone? Only if kept caged and chainedl Telco added value: beyond person-to-person, exploring A2P & P2Al Object communicationsl OTT not doing that (yet)
What’s missing?l Open enablers to innovation engine. APIs as tools so tinkerers can tinker.l Operators: able to open developer accounts by the millions.l Developers: start quickly, with no telco expertise required. Credit:: www.freedigitalphotos.net
Towards the “Service Store”l “Service Store” vs “App Store”l No fragmentation, totally portable across platformsl Telco playing leading role, articulating ecosystem & fair revenue sharing with developers Device/OS manufactures leading role Telco leading role
APIs: Put’em 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 with mismatching 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 !!! www.rcse.tv
RCS-e/joyn UNI 3rd API Exposure telco 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