PPT by Jose Recio presented at IMTC 2025 Forum, during the Triple Play in the living room panel. In this ppt is explained how using currently available javascript frameworks for tv widgets or STB apps, you can create a view of a more complex Rich Communication Suite client in a shared platform in the cloud, becoming feasible a real triple play and making true common experience for enhanced mesaging and UC also in the TV screen.

1. Triple Play in The Living Room
Day 1 – April 7th 2010
Live: 11:10‐11:35
Rich communication services on TV
A light client approach
Jose M Recio
Co‐Founder, Solaiemes

2. Agenda
• Triple play and communication services
• GSMA RichCommunicationSuite
• UNI‐based integration. Light clients.
• Demo video

3. Introduction
• Triple play carriers offering services tied to the TV
screen, that customers can use directly from the
TV/STB remote
– Beyond voice and bare broadband
• Integration with social networks, messaging, access
to customer management, marketing ...

4. Web? Browser!
• STB and TV browsers still limited: difficult to convey
the desktop web experience
– And user expectations for “web” is clear
• Carriers uneasy about pure browser solutions
• Browser based? Could be for web‐based user
experiences. But for communications?
• Some users need something easier than browser

5. Temptations
• Temptation exists to follow well trodden paths
– “we know better”?
• Create own services: potential for highest integration and
user experience control
• But also require significant effort: design services, user
interfaces, service flow, engaging vendors, long development
cycles, testing ...
• Expensive !!!
• Innovation is out there: How do you convince a college
student to use your proprietary interface?

6. And … in the customer hands?
• Full clients on STB: complex porting from another
environments, proprietary middleware and APIs,
vendor engagement
– significant up‐front investment
• TV sets too limited right now to run a full
communications client
• Other devices (game consoles …)

7. Capabilities exist
• “Internet TVs” frameworks:
– Yahoo! Widgets/ConnectedTV): cinematic Internet”™
experience
• Set Top Box middleware: easy and quick
development of attractive small apps
– MHP, TiVo, SDKs …
• Integrated in the user experience. Carrier managed

8. Services are there
• Don’t reinvent the wheel …
• GSMA Rich Communication Suite:
“collaborative effort to speed up and facilitate the introduction of
commercial IMS based rich communication services […]”
• Rich agenda, presence, rich messaging, file transfer, video sharing.
• Mobile and fixed access. Standalone or combined with voice calls.
• Use cases and user experience key aspects in the service definition
process.
• Wide industry support, interoperability effort. Ongoing trials. Launches
very soon.
• Built‐in differentiation capabilities.

9. Rich services on the TV the easy way
• Use RCS services: industry backed, well understood, tested, available.
• Light TV or STB client: rendering engine, focused on user experience
– Existing capabilities in STB and TV widgets good enough for this
– Not implementing protocols. Heavy lifting done in the network
• Solaiemes RCS gateway implementing virtual RCS clients in the cloud
– Performing actual protocol work on behalf of the TV/STB
• Keeping the same user experience and service model as with other mobile
and fixed RCS access.
Carriers offering triple play can also offer communication
capabilities directly on the TV screen. RCS becomes seamless.

10. Riding the UNI for service development
• IP based services: smart endpoints = rich user to network interfaces
(UNI)
• UNI‐based integration with the core: independent from core and
clients
– Does not depend on server proprietary interfaces
– Neither core nor clients need special modifications or configurations
• And offering APIs the way Internet developers see them
– Engage 3rd parties, enterprises: the innovation engine
– Makes life easy for the carrier: no need to IOT with every 3rd party
• Painless to experiment and test new services and business models
• Unlocks SMS business model for rich services

11. Smoothly merging telco and internet spaces
RCS Solution
UNI (user to Gateway
Carrier XDM network
core IM interface)
MSRP
MSRP SIP
SIP XDM
XDM
Video share IMS MSRP SIP XDM
MSRP
MSRP SIP
SIP XDM
XDM
virtual MSRP SIP XDM
Presence RCS
clients
RESTful and web
push APIs
UNI (user to network interface)
mobile Enterprises
and fixed
Internet
RCS ecosystem
clients Developers

12. Application to RCS TV Widget
RCS Solution Gateway
RCS widget
virtual backend
RCS MSRP SIP XDM
MSRP
MSRP SIP
SIP XDM
XDM
clients
RCS APIs (presence,
UNI messaging, picture
transfer)
Presence
Carrier IM
core IMS Widget
XDM
Widgets enabled TV
UNI server
RCS Widget management (widget
mobile catalogue, download …)
and fixed
RCS
clients

13. Results
• Same user experience and service model as with other mobile
and fixed RCS access.
• Carriers offering triple play can also offer communication
capabilities directly on the TV screen. RCS becomes seamless.
• Extremely quick development and deployment on the
customer end
– Days, not months
• Painless integration with the core and “regular” RCS clients

14. And it works: Sample use case
• Unveiled in RCS DevChallenge (jan. 2010)
• Integrated with Tier‐1 IMS & RCS core
– No additional configuration needed on core, no
extra configuration on clients
• RCS chat and picture transfer mobile ↔ TV
http://www.youtube.com/watch?v=Qb8ugLJ44ag

15. Conclusions
• Many bricks are there: build on them to save costs, accelerate
time to market
• The UNI is probably rich enough for you want to do
• Light clients at the customer end: faster to deploy, easier to
manage, lean on resources
• Engage developers. Innovation is there. Make their life easy.
– How long (and $€¥) would it take for a 5‐person company to deploy a
service in your favourite carrier’s network?
– And to deploy an app in your favourite smartphone app store?

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