This pdf describes the Solaiemes approach to create RCS based services, merging telco and web capabilities, and making feasible smooth "connection" between carrier core and internet services, and enabling the mobile user to have a lot of use cases with a common enabler/feature
Handwritten Text Recognition for manuscripts and early printed texts
Solaiemes RCS Solution Gateway
1. RCS Solutions Gateway
for:
UGC & Social Media
CRM
Web Tools access
Advertisement
2. RCS, what’s that?
Rich Communication Suite is a suite of rich communication services that can be
launched from a capability enhanced phonebook.
The awareness of the supported capabilities together with availability and other
presence information will improve the user experience and will promote the usage
of the rich communication services.
The RCS Initiative has chosen for an approach where no new services are
defined, but through efficient bundling and profiling of existing standardized
services a balanced offering can be made.
3. RCS Components and Goal
RCS Components
1. Enhanced phonebook. In the enhanced phonebook the contact information
is extended with capability and presence information.
2. Enriched call. The enriched call features allow sharing information during an
ongoing voice call
3. Enhanced messaging. The enhanced messaging offers conversation
experience.
The goal of the RCS service is to provide a common
framework for a service that is interoperable among mobile
operators and devices.
4. Solaiemes Approach
RCS Solution Gateway opens RCS to internet ecosystem
& enterprise…
… in the same way that SMS became a huge success
from the beginning:
• adoption
• usage
• revenue
5. Architecture
RCS Solution
CARRIER IM
Gateway
IMS Presence
VS
CRM Social Mobile Ad Web tools
texting access
Media n Engine
Smoothly merging telco and internet spaces
6. RCS Solution Gateway
RCS Solution Gateway
CARRIER CRM
MSRP
Streaming
IMS/RCS info
SIP API’s Mobile Ad
CORE Engine
XDM RESTful
API’s
Social
dedicated RCS Media
Clients
3rd party
Internet
ecosystem
IMS Core, RCS servers, RCS clients DO NOT need any modification
7. UGC & Social Media case
Provide a common user experience for multiple Social Media connectors
entities enabling a multi-channel (IM, Voice, Video, File Transfer) common
way to update/upload media and receive status updates for their social
networks (Twitter, Facebook, Tuenti, Keteke, Linkedin, etc).
Fully integrated with the phonebook, each SM becomes a phonebook entry
With the presence is easy “disconnect” from receiving updates
Better approach than external apps to manage multiple social networks
interactions (i.e: MotoBlur), or individual social networks apps, not always
portable.
8. The role of RCS UGC/Social Media Gateway
1. Provide a user autoprovisión system to include their favourite Social Media
own accounts to be used two-way (updating/receiving status updates), each
social media site becomes a phonebook entry.
2. Billing module to charge with flexible system (interaction cycle, push,
customers accessed, etc, etc)
3. The RCS uses Social Media sites API’s to interconnect mobile users without
needing external apps. A carriers services become a true common enabler.
4. Co-Advertisment agreement possible when including SM site advertistment
in the status updates served using RCS.
5. Increasing the mobile users of Social Media.
9. CRM case
Provide a common user experience for multiple CRM entities enabling a
multi-channel (IM, Voice, Video, File Transfer)
Fully integrated with the phonebook
In outbound use cases “presence” prevent from intrusiveness
The user learns once how to use and with every CRM (bank, telco, utility) is
the same (same as SMS, once learnt you can text, vote, buy ringtones, sms-
to-TV, etc)
10. The role of RCS CRM Gateway
1. Provide APIs to be used for third party CRM entities to communicate with
their customers using RCS features (IM, voice, videoshare, push-to-view,
file transfer, etc).
2. Provide statistics/analytic web based access for each third party CRM to
check their usage per type of interaction
3. Billing module to charge with flexible system (interaction cycle, push,
customers accessed, etc, etc)
4. Provide optional module to Carrier platforms API’s as Location, to add
location to fully customized CRM interaction.
11. Web tools alternative access case
Provide for most of web tools an alternative access based on natural texting
Allow developers to just mash-up’ing API’s from its own service and the RCS
Solution Gateway to increase the potential base of users
Create revenue sharing models to monetize web tools (weather, translators,
etc) long tail.
12. Web tools via RCS. Examples
Google Weather (video)
Google Translate (video)
Google Currency (video)
13. Advertisement case
RCS can be used for mobile marketing / advertisement.
Segmented by user and also by “format type preferred” using RCS.
Presence is a key feature to avoid intrusiveness,
It could be linked to LBS to offer eating & entertaiment places around a
“non typical” location of the user.
Possible youth price plans based on discounts if accepting and interacting
with ads.
14. The role of RCS Advertisement Gateway
1. Provide APIs to be access the adserver from advertiser.
2. Provide filters and rules engine to avoid spam or intrussivenes
3. BI module to trace advertisment interaction to mesure efectiveness.
4. Billing module with different implemented approaches (impacts, impacts-
followed-by-user interaction, campaign tagged fix price).
5. Interface with coupon server to ad campaigns to possible return.
6. Mobile subscriber and Advertiser full statistics module.