this ppt-brochure explains the RCS Thin Client Server product and its difference goal and complementariety with RCS Solution Gateway.

1. RCS Thin Client Server
for:
 RCS Web Client
 RCS TV Client
 RCS embedded communication for apps
 RCS Clients with no need of implementing
telco protocol stack.

2. What is RCS Thin Client Server ?
Solaiemes RCS Thin Client Server is the platform creating “subscriber virtual
RCS clients” in the cloud and the framework to create the personal client based
on javascript to make feasible RCS browser based in your laptop, tablet,
smartphone and also your TV.
The idea is splitting the telco side of Rich Suite Clients from the “visual interface”,
trying to avoid the telco protocol management in the final device.
Also, the the RCS Thin Client Server allows an embedded mechanism to use
RCS as communications for apps in a transparent and UNI way.

3. RCS Thin Client Server vs
RCS Solution Gateway.
Is it the same approach ?
Solaiemes RCS Thin Client Server and Solaiemes RCS Solution Gateway share the
same “core” component allowing to translate from telco protocols (SIP,XDM, MSRP) to
internet API (SOA WS, Rest, etc), creating virtual RCS clients “user to network interface”
based.We could say they are familiar platforms.
The difference is the different goal pursuit:
RCS Solution Gateway: creating virtual RCS clients meaning “service-users”.
The goal is increasing the use cases on top of RCS by 3rd party developers.
RCS Thin Client Server: instancing virtual RCS Clients meaning “personal- users”.
The goal is to make RCS ubiquitous and multi-device way of communicating.

4. RCS Thin Client types
RCS Web Client
RCS TV Client
RCS embedded communication for apps
RCS Clients with no need of implementing telco
protocol stack.

5. Architecture (I)
RCS Thin Client Server
virtual RCS clients
MSRP SIP XDM
MSRP SIP XDM
MSRP SIP XDM
Web Server
Layouts
Web Server
WS/API
UNI Internet

6. Architecture (II)
TV Widgets
Server
(Connected
TV)
Widget
enabled TV
Presence
IMCarrier
core XDM
IMS
mobile
and fixed
RCS
clients
UNI
UNI
RCS THIN CLIENT SERVER
Apps & Native
clients embedding
RCS comms
RCS Web ClientInternet

7. RCS Support Level
 Currently adapted to RCS Release 2.0
 Supporting:
 Presence & Contacts management
 Instant Messaging (Chat). Several simultaneous sessions per user
 File Transfer. Several simultaneous sessions per user

8. RCS Web Client
 Javascript/AJAX based.
 Highly customizable
 Different layouts and themes, the look & feek is pure CSS based.
 Suitable for computer browser, tablet (iPad), and even smartphones
 RCS Client becomes an URL
 RCS partial clients to use as RCS virtual assistant for e-commerce or banking sites
with “carrier authentication”
http://www.youtube.com/watch?v=zrDy1PipiDw

9. RCS TV Client
 Widget based.
 JavaScript based, local Widget uses WS to create real time RCS TV client,
widget can reside at TV or STB. (tested with Connected TV widget).
 Different layouts and themes
 Allows real time communication from/to mobile to/from TVs and/or
browsers
 The way for telcos to create a pure half duplex triple play.
http://www.youtube.com/watch?v=Qb8ugLJ44ag

10. RCS embedded communications for apps
 Transparent use of RCS communication capabilities integrated with apps, i.e:
multiparty gaming alerts, on demand media search, etc
 Allow carriers to standardize the communications for many apps keeping a
role and using a “network efficient use” framework as RCS.
 As the “final user” and “service users” are authenticated the apps will be
more secure.
 Better approach that “device API” to use RCS features embedded in apps.

11. RCS Clients with no Telco protocol stack
 Allows the development of many RCS Clients for different platforms (iOS,
Android, Symbian, etc) only taking care about the “look & feel”
 Using WS/API the applications are provided with real time communication
with the “virtual mirrored client” keeping the telco side in the cloud.
 Reduces the entry cost of creating very customized RCS Clients as
applications.

12. What is different from IMS
vendors Web Clients?
 IMS/RCS Core providers usually offer web client and social media
connectivity “locked-in” to their core infrastructure, not UNI approach, then,
it is not possible to replace any of the core elements without losing the web
or the social media connector capabilities.
 UNI approach is the only one that allows both, the carriers and the final
developers to become fully independent.

13. Scalability & Supply Mode.
 The RCS Thin Client Server uses mature enterprise scalable technologies.
 RCS Thin Client Server can be provided on premises or as a Cloud
Communication platform as a Service.
 It could be placed everywhere and the entry point of “virtual clients” to the
telco core will be trough the SBC (“session border controller”), it means UNI
interface.

14. Interoperability
 Solaiemes virtual-client base technology participated in RCS test-fest events.
 Also the Solaiemes RCS technology has been used for e2e use cases
interoperated with SBC, XDM, Presence, IMS servers and handset and
desktop clients. See this joint PR.
http://www.solaiemes.com/assets/pr/RCS%20Asia%20Ecosystem%20PR%202010_08092010_final.pdf

15. Roadmap
Solaiemes is working to add in the next months features as:
VideoShare Support
Enhanced O&M interface
Billing rules interface
User defined analytics
Lawful Intercept Administration Node (LIAN)
Visual Layout Composition Tool

16. www.solaiemes.com
Addtional info:
http://www.youtube.com/solaiemes
http://www.slideshare.com/solaiemes
http://blog.solaiemes.com