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,
q Whatsapp is stuck to personal
communications for annual
minimum fee and not opening
to A2P cases.
q Line & WeChat already testing
with enterprise to use
messaging as channel for
Couponing. Also sport brands
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
q Geo-location push enables a wide range of hyperlocal
IMS Core, RCS servers, RCS-e clients DO
NOT need any modification
API based joyn clients
for Web, WebRTC,
Firefox OS, Smart TV
A2P, P2A, M2P, CRM
cases created with the
Solaiemes Confidential Information
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-e core + REST
API exposure, currently
Solaiemes has interoperated
with a RCS-e core in the
cloud vendor this architecture
A2P – P2A, Communicating
People with Services & Brands :
CRM self-service, advertisement,
M2P, communicating people and things
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.
WebRTC unified communications
Operator IMS/RCS-e Core
ITR & WebAgent
Server are the
and all their stuff is
q A very innovative bank in Spain offering banking using many channels
eager to try “chat based” banking. Many before asked to use Whatsapp
but Whatsapp is not allowing APIs to create B2C comms.
q RCS/joyn seen as alternative to start experimenting.
q Security: they required security even when RCS was used using open Wi-
Fi. RCS matches the requirement, using SIP & MSRP over TLS.
q REST API was OK but SOAP WS preferred as it is their natural way to
create new B2C channels. Solaiemes offering also SOAP flavour.
q STATUS: Being implemented with minimal support.
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
Legacy | CRM | ERP
Creation & Admin
= 3rd Party
* using Solaiemes RCS REST API
q There is a 3rd way to access to the services: mobile web, apps and messaging as
q Texting becoming preferred communication experience in many context, and
rich messaging increases the potential for B2C rich interaction.
q Service-Contacts in the phonebook, the “new apps”…no install, no need to learn
new thing, just share UX for thousands of cases.
q B2C intensive companies (banks, utilities, governments) and B2C tech providers
interested in exploring new channels to reach their users.
q Telco still perceived as “the trusted one” when talking about privacy/security
q Telco REST APIs are they way to make the telco a real platform to W2P
(Whatever to Person) communications.
Addtional info at: