Rich Communication Suite (RCS) and RCS-e aims to seamlessly unify the communications experience by integrating traditional mobile telephony with new interactive services such as presence, instant messaging and content sharing enabled by the enhanced address book of the mobile phone.

1. Rich Communication Suite
Components , Functions and
Arcitecture solution
- Altanai Bisht , ASE , Tata Consultancy Services

2. Introduction
• Rich Communication Suite (RCS) and RCS-e aims to seamlessly unify the communications
experience by integrating traditional mobile telephony with new interactive services such
as presence, instant messaging and content sharing enabled by the enhanced address
book of the mobile phone.
• RCS leverages the 3GPP IMS architecture and uses SIP signaling to establish sessions to
exchange instant messages, presence information, video and files
An RCS server and clients suite needs to fulfil the
requirements of allowing the subscribers to place
and receive Voice and Video calls, send Instant
message, share files , so on .
Points taken from : Andrxen specification document
Open n/w
home
subscriber

3. RCS /Joyn
What is RCS / Joyn ?
GSMA has developed a joyn innovation accelerator platform that offers global access to
developers on a precommercial basis to RCS.
Courtesy : Orange_RCSVoLTE_IOT_Event_vf2 paper

4. Solution Overview
• RCS solution is required to bear its Net-Net session border controller (SBC) deployed at the
access border of the SIP or IMS service network. SBC should provides critical control functions to
deliver interactive communications services—voice, video and multimedia sessions—over the IP
3G RAN. On the other side of direct internet reach , the process is much alike .
3G RAN internet
MSC
GGSN PCRF
MSG
SBC
P-CSCF
I-CSCF
S-CSCF
Application
server
Media server
IMS Core
Backbone
Points taken from : APKT_SB_RichCommSuite Acme Packet paper

5. Development paths
1. RCS e-stack ( Orange Labs ) – installed
and testing the originally present
features with android 4.2.2
https://code.google.com/p/android-rcs-ims-stack/
2. RCS oenapi ( GSMA ) – registered with
developer license to use the non
commercially API’s , attempts to run
the same
http://rcs.oneapi-gw.gsma.com/

6. Challenges
There are technical challenges and requirements for RCS IP interactive communications:
• Service reach: Deliver service to handsets and clients on networks with differing or conflicting network
characteristics such as IP addresses, signaling and transport protocols and encryption.
• Security: Protect network resources from attack and overloads and ensure privacy of communications.
• Revenue and cost optimization: Protect against theft and abuse of service and capture session data for
billing, traffic management and planning.
• Regulatory compliance: Enable emergency service routing and lawful intercept in order to comply with
government regulations for VoIP and interactive communications.
• SLA assurance: Handle latency sensitive traffic with high priority and maintain service availability during
abnormal busy periods.