RCS Business Messaging (RBM)

In this lecture, we talk about the features and functions which Businesses/ Brands would like to see in the RBM Ecosystem that will be attractive for them to use it for their customers.

Lets describe a typical User story when they call a Customer Service Phone number. What type of interaction can take place between the Business and the customer that will give more Customer Satisfaction and also increaser the Business Revenue.

Businesses want End to End Security and Privacy when their systems are talking to their customers.  Here we discuss how RCS based Messaging System provides that to the brands.

Since HTTP is the main protocol that we shall be using when it comes to transfer of contents using RCS Framework.  Next few slides we want to build a good understanding of why HTTP is Chosen protocol and what are its main functions that are attractive for RBM.

Here we talk a high-level Call Flow that takes place between the sender RCS client and the Receiver RCS Client and how they interact with the Content Server that is part of the RCS Framework.

Lets briefly touch upon the different versions of HTTP protocol as they evolved over time and how it brought more functionality in Content Transfer. We shall refer to the related RFCs that will be helpful for students if they need deeper dive when dissecting their projects.

Before Ending this Section on RBM Background Information, lets at least see what types of files are supported for transfer in RCS Framework and what are not Supported.   That will be useful when we start talking about so many content transfers as move to next section of this course.

This is a quick refresher of FT Architecture by going over the Architecture Diagram give n GSMA Document.

Here we look at a typical SIP IMS REGISTRATION Message and focus mainly related to RCS and File Transfer operation.

SUBSCRIBE/NOTIFY are the main messages that get exchanged to do Capability Checks. Here we want to go over the NOTIFY message but focus and discuss FT related parameters.

When we setup a Chat session to transfer the file related Meta Data to the recipient, there are a number of FT related parameters that are included in INVITE message. Lets discuss those here in this lecture.

Lets have a quick overview of what happens on the Recipient side to download the file contents from the Content Server.

To get a better feel of what happens on Recipient side for the file,  we want to go over some sample HTTP request and responses that take place between the RCS client and the Content Server.

Here we are talking about the overall Architecture that makes RCS based Business Messaging Possible.

In this lecture, we are trying to explain the role played by the IMS Data Channel Server that makes multimedia contents flow between Chatbots and the end user.