SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
q OTTs succeed gaining traction among users, being multi-platform.
q OTTs have imposed a free or very cheap service that makes
difficult for telcos to charge the person to person messaging
q OTTs still perceived as less secure by enterprise but it is changing.
q Different business models being tested: Telco partnership, internal
games, annual fee,
Offering only person to person
communications for annual minimum fee and
not exposing API for B2C use cases cases
WeChat & Line among
others are opening
messaging to B2C cases
A couple of examples about how enterprise is using IM (Whatsapp in
this case) “rudimentary” for business purposes.
Take Away fast food
rudimentary to take
orders, just reading
the app client, no
with their order
Why not having API to integrate IM with IT back-ends?
Why not RCS to fulfil this market demand?
to get feedback
Just reading the
IM client, no IT
could add value
q Coca-Cola VP Marketing asked in the RCS Seminar (MWC 2013)
to use joyn as channel.
q In the meantime Coca-Cola tested with Line.
q Nobody will be waiting for telcos anymore…brands prefer telcos,
enterprises rely more in telco security…but it is not an stopper. If
telcos do not offer what they need they will look somewhere out.
Sirs, it is happening right now
q Due the easiness of the new messaging alternatives, and
data connectivity almost “always” there, people is
starting to consider intrusive to make a call if it could be
solve by texting.
q Texting cheaper than voice
q Young people likes texting, they text as fast as they can
talk, then it is preferred
q The texting “remains”, local history. It helps personal
Voxeo CXP is a Self-Service Application Lifecycle Management suite,
and RCS/joyn as a new delivery channel was included using RCS
network API to reach RCS users.
RCS API GW
A2P – P2A, Communicating
People with Services & Brands :
M2P, communicating people and things
CRM self-service, advertisement,
Internet tools as joyn
Combining content API & joyn
Example: own telco self-service
Example: using joyn by airline to provide 2 hours befor flight the boarding
card and likely a plan to arrive to the gate. It could be done.
LBS self-service, bus real time information. Sending location to bus company,
info of nearest stop & its line and waiting times delivered real time.
q If the customer supports multi-device environment, RCS Thin
Client Server API can be used to embed joyn chat and file
transfer in mobile apps as REST.
q App developers will have a communication framework to
embed chat, FT, location push,etc without needing a mobile
base with mobile joyn clients powering “device API”.
q It could help to boost telco messaging for in-app 2 in-app
communications cross platform and acquire joyn users via in
It is not possible to charge RCS/joyn to
the users as SMS in the past, as today’s
alternatives (OTTs) make it impossible.
Needed to rethink the messaging
While voice and SMS are commoditized and
offered as fix bundle, voice & SMS charged by
message and minute still work for A2P
(application to person).
Tropo & Twilio are examples of independent
voice & SMS providers as API with a lot of
developers registered & revenue.
q Enterprise with high traffic and perhaps dedicated
GWs as Banks, Utilities etc
q Verticals as mobile journalism, m-health, advertising,
q Long Tail of developers.
q CRM self-service interaction, adding chat/file transfer
as additions channel for customer service.
q Chat based games and leisure cases.
q Advertisement (non-intrusive better)
q Vertical cases telco powered (real time streaming to
online media: mobile ENG, multimedia task reporting)
q Long tail developers will add thousands of cases.
Can be sponsored with additional message from the
sponsor/advertisement -> SMART advertisement
The telcos can “sell” to
trusted partners via API the
EUC feature to get real time
confirmation for transactions
(even with PIN).
Telco as Notary.
Adding RCS to the PSTN and access to
messaging via Smart TV and make it
accessible via WebRTC can add value to
the users, reduce churn and perhaps
induce more revenues due the usage of
chat based services
RCS can use SIP URI identities.
Then a new business appears: the premium names, for
big companies & also to be acquired for new services:
Annual fee for premium identities.
A2P, P2A, M2P, CRM
cases created with the
API based joyn clients
for Web, WebRTC,
Firefox OS, Smart TV
IMS Core, RCS servers, RCS-e clients DO
NOT need any modification
The API exposure platform is in the
cloud (public or private) as the
platform only needs connectivity to
P-CSCF or SBC, just as device clients
Full cloud RCS core + REST API
exposure, currently Solaiemes
has interoperated with a RCS
core in the cloud vendor this
Solaiemes RCS API is easy to integrate with
leading API management solutions and also
embed a testbed for testing the API based
services created. Could be offered purely
cloud based or on telco premises.
Example: integration with
RCS Store can be integrated with RCS client or
run as a separated App.
It allows to search for chat-based use cases
created with the API for developers or
enterprises and add them as entries in the
phonebook to start using them.
Also, the RCS Store allows rating and providing
feedback regarding the each published use
case and could introduce some side
monetization as “promoted” chat based cases.
Solaiemes developed an advertising engine with 2
sides, the advertiser side (as web front-end & the
developer side as API.
We aim to build a look-alike Google Adwords/Adsense
model for a new contextual media: the chat-based
services as information services, chat-based games,
casual services and creating a revenue share model
for telcos and developers. Use cases will soar RCS users,
and interactions could get monetized from 3rd parties
highly targeted advertising based on textual context
Solaiemes API allows to create not
only A2P cases but also group chat
casual cases as inviting a chat
based game, playing it and the
game-buddy will leave the group
after the game.
Can be used for other VAS
monetizable services as real time
multiparty translator, etc.
q Messaging is preferred for personal communication as
being perceived as less intrusive, but too much
messaging becomes overwhelming & intrusive.
q White/Black list is not effective way to “configure” who
can message me.
q Timeframes, levels of urgency, etc are new axis to
determine which messages could be real time.
q Managing off-line responses and incoming messages
treatment is needed.
Deliver a premium
service allowing the user
to configure who can
message him/her at
which times, create
auto-responses and a
message center to
answer at their
Juan developed his career in several companies as Motorola (Networks and Mobile Devices divisions), DMR
Consulting (now Everis), ICEX (Spanish Foreign Trade Office) and Colortex.
Juan holds an MSc degrees in Telecom Engineering from Polytechnics University of Valencia (Spain), an MSc in
Economics from UNED (Spain) and a Diploma in Politics from the University of London (Lead College, LSE).
Jose has developed his career in Motorola and Ceselsa-Indra
Mr. Recio holds an MSc in Telecom Engineering from Universidad Politécnica de Madrid and an MSc (Distinction) in
Information Security from Royal Holloway College, University of London.
Luis had previous roles at Motorola and Alcatel. developing Switching, GSM coverage planning and IMS software.
Also worked at Textil Bondrap.
Mr. Valencia holds an MSc degree in Telecommunications Engineering from the Polytechnics University of Valencia
David developed his career in Motorola, Altran SDB and Consum SCV.
David holds an MSc degree in Telecom Engineering from Polytechnics University of Valencia (Spain) and an
executive MBA from EOI Business School (Spain).
• Started activities in 2007 trying to open Push to Talk and IMS
VideoShare as REST API. Pivoted to RCS API exposure in 2010, 1st
to market solution and editors of the GSMA spec on RCS API.
• Awarded in 2011 as pioneers in the area: GSMA RCS Innovation
• Staff: 15. Growth planned. HQ in Madrid (Spain).
• Currently with contracts in 4 tier-1 telco groups and several
opportunities opened in 3 continents.
• GSMA API provider for Joyn Innovation Accelerator.
Accreditation for API GW and Web Solution submitted.
ü Solaiemes is solving a real problem telcos have. To find
a new role and make their assets a platform in the
way that developers can use them, as API. Solaiemes
is recognized by pioneering this field in the next telco
messaging, RCS joyn.
ü Solaiemes team is experienced, visionary, with
international experience in several continents and
able to do more with less and execute.