3 Definitions, symbols and abbreviations

23.2823GPPFunctional architecture and information flows to support Mission Critical Data (MCData)Release 18Stage 2TS

3.1 Definitions

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

Auto-receive: A mechanism where data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server i.e. without waiting for the receiving user to indicate a present need for the data.

Conversation identifier: A universally unique identifier that identifies a series of related MCData transactions.

Data stream: A sequence of data that is agnostic to any underlying media (e.g. audio, video, telemetry data), on which processing of data (e.g. semantic, syntactic, save or filter operation) can begin before all the content is received.

FD disposition: is one of "not downloaded" and "download completed".

Folder Identifier: A unique identifier that identifies a folder in the MCData message store

IP Data: Structured or unstructured payload that is transparent to the MCData transport service.

MCData client: An instance of an MC service client that provides the client application function for the MCData service.

MCData emergency communication: An MC service emergency group communication or MC service emergency private communication within the MCData service.

MCData group: An MC service group configured for MCData service.

MCData group affiliation: An MC service group affiliation for MCData.

MCData group communication: A one-to-many communication using an MCData service.

MCData group de-affiliation: An MC service group de-affiliation for MCData.

MCData ID: An instance of an MC service ID within the MCData service.

MCData imminent peril communication: An MC service imminent peril group communication within the MCData service.

MCData server: An instance of an MC service server that provides the server application function for the MCData service.

MCData service: A data communication service comprising at least one underlying generic capability (e.g. SDS, file distribution, data streaming) with strong security, high availability, reliability and priority handling to support applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways).

MCData UE: An MC service UE that can be used to participate in MCData services.

MCData user: An MC service user who is authorized for MCData services suite via an MCData UE.

Metadata: data associated with a transmitted or stored SDS, file or data stream, consisting of information from messages (e.g. MCData IDs, conversation ID) and other related information (e.g. size, type).

Object: An MCData communication information (such as a message or a file) that is stored in the MCData message store with its associated metadata.

Object identifier: A unique identifier that identifies an object stored in the MCData message store.

Reception control: A mechanism that allows the MCData service to regulate data reception to the receiving MCData clients.

Reply identifier: A reference to the original MCData transaction to which the current transaction is a reply.

SDS data: A payload with limited size and variable content type used in SDS transactions.

SDS disposition: is one of "undelivered", "delivered" and "read".

Standalone communication: A unidirectional one-to-one or group data communication completed after one transaction.

Transaction identifier: A unique identifier that identifies a MCData transaction within a conversation.

Transmission control: A mechanism that allows the MCData service to regulate data transmission requests from the sending MCData users, either prior to or after active sending from the MCData UE.

For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply:

Mission Critical

Mission Critical Applications

Mission Critical Service

Mission Critical Organization

For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.282 [3] apply:

MCData system

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [5] apply:

MC service client

MC service group

MC service group affiliation

MC service group de-affiliation

MC service ID

MC service server

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.203 [14] apply:

Dynamic PCC rule

3.2 Abbreviations

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

DS Data Streaming

E2EE End to End Encryption

FD File Distribution

ITSI Individual TETRA Subscriber Identity

LMR Land Mobile Radio

MC Mission Critical

MCData ID MCData user identity

PCC Policy and Charging Control

PCRF Policy and Charging Rules Function

QCI QoS Class Identifier

RSI Radio Set Identity

SDS Short Data Service

UM Unacknowledged Mode