Stages inter-entreprises
 

Objectifs : Gain knowledge on the RCS UP architecture and services and convergence of RCS UP with VoLTE/VoWiFi/ViLTE/ViWiFi. Understand how chatbots are handled by RCS UP.

Public : Telecommunication Engineers, Network Architects, Telecommunication Consultants, Information System Architects

Pré-requis : Knowledge on IMS network and service architectures

Durée : 2

Date :

Lieu :

RCS UP : Rich Communication Suite Universal Profile

The GSMA’s Universal Profile is a single, industry-agreed set of features and technical enablers developed to simplify the product development and global operator deployment of RCS (Rich Communication Suite). Marking a new era of operator service interoperability, the Universal Profile will enable the industry to deliver a consistent and more advanced messaging experience for billions of consumers worldwide. The Universal Profile contains core features such as capability discovery (which will be interoperable between regions), chat, group chat, standalone messaging, file transfer, audio messaging, video share, multi-device, enriched calling, location share and live sketching. It also introduces the key enablers for Messaging as a Platform (MaaP). This includes support for Application-to-Person (A2P) messaging, chatbot, Rich Cards, privacy control and spam protection. RCS UP has the significant advantage of working across networks and devices, unlike siloed OTT services that typically can be used only by those subscribers who have downloaded the relevant app to their device. For operators with an IMS core, RCS devices connect via the appropriate access network, be it Wi-Fi, LTE, 3G, etc. The device must then register and authenticate prior to accessing to the RCS Services. Authentication, registration and SIP routing are all handled by different components of the IMS core. Once a device is registered, the IMS core routes all RCS messages to the RCS Converged IP Messaging Server and other IMS networks. The goal of this course is to present the RCS UP architecture and Services, the convergence with VoLTE/VoWiFi/ViLTE/ViWiFi services, and emphasizes the Chatbot architecture and services.

1. RCS UP basics

  • 1.1. Why RCS UP and what is RCS UP?
  • 1.2. RCS UP principles
  • 1.3. RCS UP functionalities
  • 1.4. RCS UP simplified architecture
  • 1.5. Previous RCS releases and comparison with RCS UP
    • 1.5.1. RCS/John hotfixes
    • 1.5.2. RCS/Joyn Blackbird
    • 1.5.3. RCS/Joyn Crane
    • 1.5.4. RCS North American Profile
  • 1.6. RCS UP deployment options for mobile operators
    • 1.6.1. Own IMS
    • 1.6.2. Google's hosted service
    • 1.6.3. Other hosted service

2. CPM : Converged IP Messaging

  • 2.1. CPM enabler
  • 2.2. CPM architecture
    • 2.2.1. CPM Client
    • 2.2.2. Participating function
    • 2.2.3. Controlling function
    • 2.2.4. Message storage server
    • 2.2.5. Interworking selection function
    • 2.2.6. Interworking function
  • 2.3. CPM services
    • 2.3.1. Standalone messaging
    • 2.3.2. 1-to-1 chat and group Chat
    • 2.3.3. File transfer based on MSRP
  • 2.4. Support enablers : Presence, XDM, Push and DM

3. RCS UP services

  • 3.1. Device configuration for RCS based on service provider configuration (RCC 14)
  • 3.2. Capability discovery
    • 3.2.1. SIP OPTIONS method
    • 3.2.2. Presence method
    • 3.2.3. Feature Tags versus Service Ids
  • 3.3. 1-to-1 messaging
    • 3.3.1. 1-to-1 chat
    • 3.3.2. Standalone messaging
    • 3.3.3. xMS (i.e., SMS and MMS)
  • 3.4. 1-to-many standalone messaging
  • 3.5. Group Chat
  • 3.6. Messaging for multidevice
  • 3.7. File transfer based on HTTP
  • 3.8. Audio messaging
  • 3.9. Geolocation push
  • 3.10. Green button promise for voice
    • 3.10.1. IP voice call based on VoLTE/VoWiFi
    • 3.10.2. RCS IP voice call
    • 3.10.3. CS voice
  • 3.11. Green button promise for video
    • 3.11.1. IP video call based on ViLTE/ViWiFi
    • 3.11.2. RCS IP video call
  • 3.12. Multidevice voice and video
  • 3.13. Enriched Voice Call
    • 3.13.1. Pre-call services
    • 3.13.2. In-call services including video share, shared map and shared sketch
    • 3.13.3. Post-call services
  • 3.14. Chatbot
  • 3.15. Plugins
  • 3.16. Call flows for the different services

4. Convergence between VoLTE/VoWiFi/ViLTE/ViWiFi and RCS services

  • 4.1. Single registration via IMS APN
  • 4.2. Two registrations via IMS APN and HOS APN/non EPC integrated WiFi
  • 4.3. Resource reservation for RCS services
    • 4.3.1. IMS APN : QCI 5, 7, 1, 2, 8-9
    • 4.3.2. HOS APN : QCI 8-9
  • 4.4. Authentication
    • 4.4.1. Authentication for single registration
    • 4.4.2. Authentications for two registrations
  • 4.5. Protection of SIP signaling exchange for each registration and two registrations
  • 4.6. Advantages and drawbacks of single registration and two registrations

5. Chatbot service architecture

  • 5.1. Chatbot definition
  • 5.2. Chatbot addressing
  • 5.3. RCS service provider network and chatbot platform
  • 5.4. Chatbot architecture entities
    • 5.4.1. Chatbot directory
    • 5.4.2. Chatbot information
    • 5.4.3. Messaging server
    • 5.4.4. Capability exchange AS and capability exchange filtering
    • 5.4.5. Alias Function
    • 5.4.6. Spam report
    • 5.4.7. Sapn block
  • 5.5. RCS 1-to-1 chat between client and chatbot
  • 5.6. Exchanged information
    • 5.6.1. Ordinary message
    • 5.6.2. Rich card
    • 5.6.3. Suggested chip list


 Informations  |  Inscription  |  Contact  |  Accueil 

webmaster ~ www.efort.com
© EFORT Un service serveurs.net !  Ø  /=<