Content for TS 24.582 Word version: 18.2.0

3.1 Definitions 3.2 Abbreviations 4.1 Overview 4.2 Other considerations 5.1 General for MCData functional entities 5.2 Functional entities for SDS 5.3 Functional entities for FD 5.4 Functional entities for IP Connectivity
...

1 Scope p. 8

The present document specifies the media plane control protocols and interactions with the media needed to support Mission Critical Data (MCData) services, which are IP Connectivity, Short Data Service (SDS) and File Distribution (FD).

Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.

The MCData service and its associated media plane control protocols can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).

The present document is applicable to User Equipment (UE) supporting MCData client functionality and to servers in the MCData system.

2 References p. 8

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData) Stage-2".

[3]

TS 23.280: "Common functional architecture to support mission critical services Stage-2".

[4]

TS 24.481: "Mission Critical Services (MCS) group management; Protocol Specifications".

[5]

TS 24.482: "Mission Critical Services (MCS) identity management; Protocol Specifications".

[6]

TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".

[7]

TS 24.484: "Mission Critical Services (MCS) configuration management; Protocol Specifications ".

[8]

TS 24.282: "Mission Critical Services (MCS) signalling control; Protocol Specifications ".

[9]

RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".

[10]

RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".

[11]

RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)".

[12]

RFC 6135 (February 2011): "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)".

[13]

RFC 6714 (August 2012): "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)".

[14]

RFC 4976 (September 2007): "Relay Extensions for the Message Session Relay Protocol (MSRP)".

[15]

TS 33.180: "Security of mission critical services".

[16]

RFC 3550 (July 2003): "RTP: A Transport Protocol for Real-Time Applications".

[17]

RFC 3711 (March 2004): "The Secure Real-time Transport Protocol (SRTP)".

[18]

TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".

[19]

RFC 2784 (March 2000): "Generic Routing Encapsulation (GRE).

[20]

RFC 2790 (September2000): "Key and Sequence Number Extensions to GRE.

[21]

RFC 791 (September 1981): "INTERNET PROTOCOL".

[22]

RFC 8200 (July 2017): "Internet Protocol, Version 6 (IPv6) Specification".

[23]

RFC 8086 (March 2017): "GRE-in-UDP Encapsulation.

[24]

TS 24.501: "Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".

3 Definitions and abbreviations p. 9

3.1 Definitions p. 9

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

example:

text used to clarify abstract rules by applying them literally.

3.2 Abbreviations p. 9

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

CSK

Client-Server Key

CSK-ID

Client-Server Key Identifier

DPCK

MCData Payload Cipher Key

DPCK-ID

MCData Payload Cipher Key Identifier

DPKK

MCData Payload Protection Key

DPKK-ID

MCData Payload Protection Key Identifier

File Distribution

GMK

Group Master Key

GMK-ID

Group Master Key Identifier

GRE

Generic Routing Encapsulation

KMS

Key Management Server

KPAK

KMS Public Authentication Key

MBS

Multicast/Broadcast Service

PCK

Private Call Key

PCK-ID

Private Call Key Identifier

PVT

Public Validation Token

SDS

Short Data Service

SPK

Signalling Protection Key

SPK-ID

Signalling Protection Key Identifier

SSK

Secret Signing Key

4 General p. 10

4.1 Overview p. 10

4.1.1 Short data service p. 10

The media plane control procedures, both for one-to-one and group short data services, take place for on-network only, when standalone short data is sent using media plane or when the short data is sent after an SDS session is established. In both cases the media plane is established as specified in TS 24.282.

The media plane uses the MSRP protocol as specified in RFC 4975, RFC 4976, RFC 6135, and RFC 6714.

In a standalone SDS using media plane, a single SDS message is sent by the originating MCData client as specified in this document. The procedure is terminated as specified in TS 24.282.

When an SDS session is established any MCData client with appropriate permissions, which participates this SDS session, can initiate the transmission of and SDS message until the termination of the SDS session. The termination of an SDS session is specified in TS 24.282.

An SDS message sent using media plane is carried in the body of an MSRP SEND request. The media control parameters and the data of an SDS message are carried in separate bodies in the same MSRP SEND request.

The Conversation ID,the Message ID, the optional InReplyTo message ID, the optional SDS disposition request type and the optional Application identifier are communicated by the MCData client which sends the SDS message in the media control part of the body in the MSRP SEND request. The data is carried in a separate body of the MSRP SEND request.

For standalone SDS using media plane, the disposition notification is communicated as specified in TS 24.282.

For SDS during an SDS session the disposition notification is communicated using the procuderes specified in the current document until the SDS session is terminated. After the termination of the SDS session the disposition notification, if any, is communicated as specified in TS 24.282.

4.1.2 File distribution p. 10

The media plane control procedures, both for one-to-one and group file distribution using media plane, take place for on-network only. The media plane for FD is established as specified in TS 24.282.

The media plane uses the MSRP protocol as specified in RFC 4975, RFC 4976, RFC 6135, and RFC 6714.

A file is sent using media plane by the originating MCData client as specified in this document. The procedure is terminated as specified in TS 24.282.

The Conversation ID , the Message ID, the optional InReplyTo message ID, the optional FD disposition request type, the optional Application ID, the optional Mandatory download and the optional Metadata are communicated by the MCData client which sends the file using the procedures specified in TS 24.282 while establishing the media plane.

The file is carried in the body of the MSRP SEND request as specified in this document.

The disposition notification is communicated as specified in TS 24.282.

4.1.3 Void

4.1.4 IP Connectivity |R16| p. 11

The media plane control procedures for one-to-one IP Connectivity service using media plane, take place for on-network only. The media plane for IP Connectivity is established and terminated as specified in TS 24.282.

The media plane uses the IP protocol as specified in RFC 791 and RFC 8200.

The IP Connectivity media plane is established by the originating MCData client as specified in this document.

IP Connectivity provides a media plane for exchange of any kind of IP data between IP applications. Once the media plane is established along with IP Connectivity the IP applications can exchange IP data.

4.2 Other considerations p. 11

When an SDS message is sent using media plane, the body included in the MSRP SEND request, which carries media control information or which carries notification information, is protected between each entity separately if protection is applied. On the other hand the body included in the MSRP SEND request which carries the data is end to end protected. The procedures for the protection of the media control information or notification or of the data are specified in this document.

When a file is is sent using media plane, the file or file portion, included in the body of the MSRP SEND request, is end to end protected. The procedure for the protection of the file is specified in this document.

5 Functional entities p. 11

5.1 General for MCData functional entities p. 11

5.1.1 SDS and FD |R16| p. 11

Media plane control is conducted between the MCData server and MCData UE. MCData server has capability functions for SDS and FD. MCData UE incorporates the MCData client. MCData user or MCData user application may feed or consume data transmitted or received via the capability functions in the MCData client. The capability function in the MCData client provides SDS and FD services.

The capability functions of the MCData server are specified for the controlling MCData function and the participating MCData function. The capability functions of the MCData UE are specified for the MCData client.

Data to be transmitted either by the MCData user or by a MCData user application using media plane shall be transmitted by the MCData client to the participating MCData function. The participating MCData function shall forward the data to the controlling MCData function. The controlling MCData function shall distribute the data to the destination MCData client for one-to-one MCData service and to the MCData clients of the affiliated group members for group MCData service via the participating MCData functions serving each destination MCData client. A participating MCData function may serve one or more MCData clients. Based on deployment, controlling MCData function may be in communication with zero, one or more participating MCData functions. If a participating MCData function is collocated with the controlling MCData function, the controlling MCData function may perform the functions of this co-located participating MCData function. In this case the controlling MCData function and this co-located participating MCData function shall act as a single entity.

In the media plane the MCData client and the controlling MCData function shall act as MSRP clients. If and when a participating MCData function is in the communication path as a separate entity between the controlling MCData function and one or more MCData clients, it shall act as an MSRP relay.

5.1.2 IP Connectivity |R16| p. 12

IP Connectivity provides a media plane for exchange of any kind of IP data between IP applications. These IP applications may reside on external non-3GPP hosts connected via an IP interface to the MCData UE that incorporates the MCData client, or they may be running on the MCData UE. The participating MCData function and the controlling MCData functions may be in the path of the data exchange between the authorized MC Data users.

5.2 Functional entities for SDS p. 12

The capability function for SDS for media plane in the MCData server is composed of SDS distribution function and the Transmission/Reception control. In the media plane the functions of SDS distribution and the Transmission/Reception control are specified for the controlling MCData function and the participating MCData function. The functions of the SDS are specified for the SDS function in MCData client.

For SDS, data is composed of short data in the form of text, hypertext, binary string or location information. Short data generated in the MCData client and sent using media plane follows the path for the originating MCData client to the terminating MCData clients as explained in clause 5.1.1.

5.3 Functional entities for FD p. 12

The capability function for FD for media plane in the MCData server is composed of FD function and the Transmission/Reception control. The file distribution over media plane functionalities in the MCData server are specified for the controlling MCData function and the participating MCData function. The functions of the FD are specified for the FD function in the MCData client.

For FD, data is composed of a file. A file provided at the MCData client and sent using media plane follows the path from the originating MCData client to the terminating MCData clients as explained in clause 5.1.1.

5.4 Functional entities for IP Connectivity |R16| p. 12

For IP Connectivity, the transmitted data may consist of any kind of IP data. IP Connectivity data sent by the MCData client using media plane follows the path from the originating MCData client to the terminating MCData client as explained in clause 5.1.2.