monetizing joyn with the rest api

Monetizing joyn with the API. Involving 3rd parties in the joyn business model

Jose Recio

Berlin, November 8th, 2012

Less Philosophical…

l  Provide enterprise and public sector with mobile multimedia services that really help them with their daily chores

l  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 Platform

l RCS-e = OTT chat clone? Only if kept caged and chained

l Telco added value: beyond person-to-person, exploring A2P & P2A

l Object communications l 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 platforms

l  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

internet  

SIP  

MSRP  

RTP/  RTCP  

REST  API  

RCS-­‐e  Solu5on  Gateway  RCS-­‐e  Core                            

IMS  

Instant  Messaging  AS  

SBC  

RCS-­‐e  LiveServe  

Friendly  Telco  Border  

FTB    

UNI  

IMS Core, RCS servers, RCS-e clients DO NOT need any modification

Rich  messaging  access  to  internet  tools  

3rd  party  services  

CRM  

telco  

Ok, but what can be done with the joyn API?

API to create services. Example: airline customer care

Send a boarding pass to a customer by the airline (push)

Screen captures from Summitech client for this demo proof of concept

API to create services. Example: telco customer care

l  Lorem ipsum dolor sit amet

Screen captures from Summitech client for this demo proof of concept

http://www.youtube.com/watch?v=vn1hqFmN4Q4

API to create clients: Web Client for PC & Smartphone

http://www.youtube.com/watch?v=iNyh3KN57S8

API to create clients: Smart TV app client TV smart APP joyn client

http://www.youtube.com/watch?v=hTevrcYeKh0

See videodemos of joyn based services and web/TV joyn clients created with the API at: http://www.youtube.com/solaiemes

Thanks J Find more about us at www.solaiemes.com