3.1 Architecture overview

The RCS platform consists of several components which use various interfaces and protocols to realize different RCS features. Details of their technical realization are described further in the document.

The solution is divided on the RCS backend (server side), RCS clients and additional web applications. The minimal configuration comprise of a Windows 2008 or 2013 server and Linux Ubuntu machine. The picture below depicts a setup in which there is one more server dedicated for the database which is a recommended approach for service providers.

The server side software include:

Applications running on Windows

• voipswitch SIP server – location server (Registrar), SIP B2BUA, Presence server
• VoipBox – a media server responsible for IVR, Voicemail, Transcoding, Recording
• VSServices – web services responsible for SMS communication, callback, DID management
• VUP – self-care user portal with voice and video communicator

Applications hosted on Linux

• EMCI and EMCD APIs (EMC) – RCS API, set of web methods responsible for the RCS features; EMCI is for internal communication between voipswitch, VUP, VSServices and EMCI API. It is server to server communication. EMCD provides set of methods which are called directly from the RCS clients.
• PUSH service – a service connecting the RCS API with supported PUSH mechanism (Apple, Google, Blackberry, Windows Phone)
• MariaDB (formerly MYSQL) – database storing the platform’s schemas

The diagram represents the components and their interconnections. 

The RCS clients connect to the edge servers using different interfaces depending on the type of the features. The functional division is following:  

HTTPS, Web Services:

• Provisioning (Sign Up, Log in)
• Multimedia sending
• Enhanced Address Book
• My Profile
• Avatars

SIP TLS

• Calling
• Instant Messaging
• Presence