[PDF] RCC.71 - RCS Universal Profile Service Definition Document

View - Download RCC.71 - RCS Universal Profile Service Definition Document

Previous PDF

Next PDF

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 1 of 260

This is a Non-binding Permanent Reference Document of the GSMA

Security Classification: Non-confidential

Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the

Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and

information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted

under the security classification without the prior written approval of the Association.

Copyright Notice

Copyright © 2019 GSM Association

Disclaimer

does not accept

any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document.

The information contained in this document may be subject to change without prior notice.

Antitrust Notice

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 2 of 260

Table of Contents

1 Introduction 7

1.1 Purpose of the Universal Profile 7

1.1.1 Structure of this document 7

1.1.2 Universal Profile 2.4 client scope 7

1.2 Conventions 8

1.3 Requirement and Technical Realisation Classification 8

1.4 Terms and Abbreviations 8

1.5 Table of references 15

2 Device Provisioning 17

2.1 Description 17

2.2 User Stories and Feature Requirements 18

2.2.1 Activation of RCS services 18

2.2.2 Configuration of the user´s primary device by requesting user identity 18

2.2.3 Multiple RCS clients 20

2.2.4 SIM swap 20

2.2.5 User consent 21

2.2.6 Secondary Devices 23

2.2.7 Error Management 23

2.2.8 Provisioning push 24

2.2.9 Dual SIM Devices 24

2.3 Technical Information 25

2.3.1 Overview 25

2.3.2 Technical Implementation of User Stories and Service requirements 26

3 Capability Discovery and Service Availability 31

3.1 Description 31

3.2 User Stories and Feature Requirements 32

3.3 Technical Information 34

3.3.1 Overview 34

3.3.2 Configuration Parameters 35

3.3.3 Handling of capability exchange triggers in messaging 37

3.3.4 Capability information for IP Video Call 37

3.3.5 Technical implementation of user stories and requirements 38

4 Operator Messaging 39

5 1-to-1 Messaging 39

5.1 Description 39

5.2 User Stories and Feature Requirements 39

5.3 Technical information 54

5.3.1 Overview 54

5.3.2 Network Fallback Support Capability 55

5.3.3 Chat Message revocation 55

5.3.4 Configuration Parameters 55

5.3.5 Technical Implementation of User Stories and Service Requirements 61

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 3 of 260

6 Group Chat 66

6.1 Description 66

6.2 User Stories and Feature Requirements 67

6.3 Technical Information 77

6.3.1 Overview 77

6.3.2 Technical Implementation of User Stories and Service requirements 78

7 File Transfer 82

7.1 Description 82

7.2 User Stories and Feature Requirements 82

7.3 Technical Information 93

7.3.1 Overview 93

7.3.2 Configuration Parameters 94

7.3.3 Technical Implementation of User Stories and Service requirements 95

8 Audio Messaging 101

8.1 Description 101

8.2 User Stories and Feature Requirements 101

8.3 Technical Information 104

8.3.1 Overview 104

8.3.2 Technical Implementation of User Stories and Service Requirements 105

9 Messaging for Multi-Device 107

9.1 Description 107

9.2 User Stories and Feature Requirements 107

9.3 Technical Information 112

9.3.1 Overview 112

9.3.2 Technical Implementation of User Stories and Service Requirements 113

10 Green Button Promise for Voice 116

10.1 Description 116

10.2 User Stories and Feature Requirements 116

10.3 Technical Information 119

10.3.1 Overview 119

10.3.2 Configuration parameters 119

10.3.3 Technical Implementation of User Stories and Service Requirements 122

11 Green Button Promise for IP Video Call Services 124

11.1 Description 124

11.2 User Stories and Feature Requirements 124

11.3 Technical Information 128

11.3.1 Overview 128

11.3.2 Configuration parameters 128

11.3.3 Technical Implementation of User Stories and Service Requirements 129

12 Enriched Calling 131

12.1 Description 131

12.2 General 131

12.3 Technical Information for the General Requirements 131

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 4 of 260

12.4 User Stories and Feature Requirements for the Enriched Pre-call

experience 133

12.5 Technical Information for the Enriched Pre-call experience 136

12.5.1 Overview 136

12.5.2 Technical Implementation of User Stories and Service Requirements 136

12.6 User Stories and Feature Requirements for the Enriched In-call experience 136

12.6.1 General Requirements 136

12.6.2 137

12.6.3 Share any file during call 139

12.6.4 Exchanging messages 141

12.6.5 Location Push 141

12.6.6 Enriched Calling In-call sharing with Non-Enriched Calling enabled

contacts 142

12.7 Technical Information for the Enriched In-call experience 142

12.7.1 Overview 142

12.7.2 Technical Implementation of User Stories and Service Requirements 143

12.8 User Stories and Feature Requirements for Interactive In-call experience 145

12.8.1 Live Sketch Sharing 145

12.8.2 Specific Requirements for a live sketch on an image 148

12.8.3 Specific Requirements for a live sketch on a map 149

12.9 Technical Information for Interactive In-call services 150

12.9.1 Overview 150

12.9.2 Shared Sketch 150

12.9.3 Specific Shared Image Sketch Requirements 151

12.9.4 Specific Shared Map Sketch Requirements 151

12.10 User Stories and Feature Requirements for the Enriched Post-call

experience 151

12.10.1 Enriched Calling Post-call experience with Non-Enriched Calling enabled

contacts 152

12.11 Technical Information for the Enriched Post-call experience 153

12.11.1 Overview 153

12.11.2 User Stories and Feature Requirements for the Enriched Post-call

experience 153

12.11.3 Enriched Calling Post-Call experience with Non-Enriched Calling

enabled contacts 153

12.12 User Stories and Feature Requirements for Enriched Call content in Logs

and media contact centric view 153

12.12.1 Technical Information for Enriched Call Logs experience 155

13 rcsVVM Service 156

14 APIs 156

14.1 Description 156

14.2 User Stories and Feature Requirements 156

14.3 User Stories and Feature Requirements of Terminal API 157

14.4 User Stories and Feature Requirements of Network API 158

15 Messaging as a Platform: Chatbots 158

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 5 of 260

15.1 Introduction 158

15.2 Chatbots 159

15.2.1 Technical Information for the realisation of Chatbots 193

15.3 Void 207

16 Security against Malware 207

16.1 Description 207

16.2 User Stories and Feature Requirements 207

16.3 Technical Information 208

16.3.1 Client authenticity verification 208

16.3.2 User Authentication 208

16.3.3 Encryption 209

16.3.4 Storage of Authentication and Identification Data 209

16.3.5 SIM State Handling 209

16.3.6 Applicability of Authentication Methods 210

16.3.7 Technical Implementation of User Stories and Service requirements 212

17 Data Off 216

17.1 Description 216

17.2 User Stories and Feature Requirements 216

17.3 Technical Information 217

17.3.1 Overview 217

17.3.2 Technical Implementation of User Stories and Service requirements 218

18 RCS Settings 220

18.1 Description 220

18.2 User Stories and Feature Requirements 220

18.3 Technical Information 225

18.3.1 Technical Implementation of User Stories and Service Requirements 225

19 Multi Device Voice and Video 231

19.1 Description 231

19.2 User Stories and Feature Requirements 231

Annex A Supporting requirements 237

A.1 Emoticon conversion table 237

A.2 238

A.3 Panoramic photo view 239

Annex B OS/Platform Specific Functionality 242

B.1 242

B.1.1 242

B.1.2 243

B.2 ent Authenticity Verification Procedure 246

Annex C Configuration Parameters 247

Annex D Features supported per Chatbot application version 259

Annex E Document Management 260

E.1 Document History 260

E.2 Other Information 260

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 6 of 260

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 7 of 260

1 Introduction

1.1 Purpose of the Universal Profile

The Rich Communication Services (RCS) Universal Profile 2.4 represents an update of globally shared RCS specifications. This Service Definition Document (SDD) lists all the User Stories and Feature Requirements, based on the Universal Profile 2.0 specification. The Universal Profile describes a single, global RCS implementation that will be deployed worldwide. The aim of this profile is to reduce the variation that exists today across various RCS profiles in order to simplify large-scale deployment. The Universal Profile is targeted at Operating System (OS) developers and Original Equipment Manufacturers (OEM) for open market device implementations. The focus of requirements is on native device implementations implemented at the OS or device manufacturer level. It is acknowledged that downloadable applications may face limitations that prevent such implementations from fulfilling the complete feature set. The SDD provides user stories and feature requirements and is complemented by the RCS Universal Profile 2.4 technical specification to describe a prioritized set of features which

Mobile Network Operators (MNOs) can launch.

1.1.1 Structure of this document

The document details how features are to be implemented from a functional requirements point of view and details specifics that may influence how certain functions behave, creating an overall guide for OEMs and application developers.

1.1.2 Universal Profile 2.4 client scope

The Universal Profile can be delivered in two ways for users:

1. Implemented natively within the device by the OS developer or OEM, tightly integrating

the capabilities and services within the address book and many other native touch points across the device.

2. Implemented as a downloadable application that can be downloaded from Application

In most cases, implementation of features is identical for both native and downloadable clients and this document for the most part will not differentiate between the two. In cases where implementation of a feature in a downloadable client differs from the native experience, these are described separately within the relevant section. The profile includes some sections that come without a technical realisation (14 and 19). As such, they are not in scope for implementations in this version of the universal profile. The requirements are indicative only since they may change following the technical feasibility assessment and are provided for information in case this information on future evolutions would be relevant for the design decisions of an implementation. In addition to maintenance of the core features of RCS, this SDD starts support of 3rd party developer applications who use interfaces to deliver their services using RCS as an enabler

GSM Association Non-confidential

Official Document RCC.71 - RCS Universal Profile Service Definition Document

V2.4 Page 8 of 260

Any major changes in comparison to the Universal Profile 2.0 are listed in the introduction section of each chapter.

1.2 Conventions

It is a shared understanding by the standardising RCS MNOs that any service described in the RCS standard may or may not be offered by any given MNO. NOTE: For device manufacturers and client developers requirements are classified based on the conventions defined in section 1.3 of this document. For the purpose of this document, user stories are identified using the following numbering N--2-1. Sub requirements will appear as a third level e.g.

R-2-2US.

For requirements and parts of requirements that are in italics, no realisation is provided in this version of the document.

1.3 Requirement and Technical Realisation Classification

Term Description

Shall These terms dictate that a functionality and/or process is Mandatory Shall/Shall Not These terms dictate that a functionality and/or process is Mandatory Required These terms dictate that a functionality and/or process is Mandatory

Should/Should

Not This term dictates that the functionality and or/process is Highly Recommendedquotesdbs_dbs42.pdfusesText_42

[PDF] trouver numero rcs

[PDF] signification siren

[PDF] numéro rcs c'est quoi

[PDF] numéro rcs siret

[PDF] numéro rcs d'une entreprise

[PDF] définition siret

[PDF] numero rm

[PDF] prix jawaz maroc

[PDF] prix jawaz autoroute maroc

[PDF] jawaz maroc tarif

[PDF] avenue azzaitoune hay riad rabat

[PDF] adm jawaz prix

[PDF] solde jawaz

[PDF] biologie et microbiologie appliquées bac pro assp

[PDF] les constituants alimentaires et leurs roles