3 Definitions, symbols and abbreviations

24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS

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].

An MCData user is affiliated to an MCData group: The MCData user has expressed interest in an MCData group it is a member of, and both the MCData server serving the MCData user and the MCData server owning the MCData group have authorized the MCData user’s interest in the MCData group communication.

An MCData user is affiliated to an MCData group at an MCData client: The MCData user is affiliated to the MCData group, the MCData client has a registered IP address for an IMPU related to the MCData ID, and the MCData server serving the MCData user has authorised the MCData user’s interest in the MCData group at the MCData client.

Affiliation status: Applies for an MCData user to an MCData group and has one of the following states:

a) the "not-affiliated" state indicating that the MCData user is not interested in the MCData group and the MCData user is not affiliated to the MCData group;

b) the "affiliating" state indicating that the MCData user is interested in the MCData group but the MCData user is not affiliated to the MCData group yet;

c) the "affiliated" state indicating that the MCData user is affiliated to the MCData group and there was no indication that MCData user is no longer interested in the MCData group; and

d) the "deaffiliating" state indicating that the MCData user is no longer interested in the MCData group but the MCData user is still affiliated to the MCData group.

Group document: when the group is not a regroup based on a preconfigured regroup, the term "group document" used within the present document refers to the group document for that group within the GMS as specified in 3GPP TS 24.481 [11]; when the group is a regroup based on a preconfigured group, the term "group document" used within the present document refers to the group document for the preconfigured group as specified in 3GPP TS 24.481 [11] restricted to the users or groups included in the regroup stored by the MCData server at the time of the regroup creation, see clause 23.

Group identity: An MCData group identity or a temporary MCData group identity.

In-progress emergency private communication state: the state of two participants when an MCData emergency one‑to‑one communication is in progress.

In-progress imminent peril group state: the state of a group when an MCData imminent peril group communication is in progress.

MCData client ID: is a globally unique identification of a specific MCData client instance. MCData client ID is a UUID URN as specified in IETF RFC 4122 [14].

MCData emergency alert: A notification from the MCData client to the MCData service that the MCData user has an emergency condition.

MCData emergency alert state: MCData client internal perspective of the state of an MCData emergency alert.

MCData emergency group state: MCData client internal perspective of the in-progress emergency state of an MCData group maintained by the controlling MCData function.

MCData emergency group communication: An urgent MCData group communication that highlights a situation of potential death or serious injury.

MCData emergency group communication state: MCData client internal perspective of the state of an MCData emergency group communication.

MCData emergency state: MCData client internal perspective of the state of an MCData emergency associated with an alert, group communication or one‑to‑one (private) communication.

MCData emergency private communication state: MCData client internal perspective of the state of an MCData emergency one‑to‑one communication, initiated with emergency indication, or without emergency indication, when the MCData emergency state is already set.

MCData emergency private priority state: MCData client internal perspective of the in-progress emergency private communication state of the two participants of an MCData emergency one‑to‑one communication maintained by the controlling MCData function.

MCData imminent peril group communication state: MCData client internal perspective of the state of an MCData imminent peril group communication.

MCData imminent peril group state: MCData client internal perspective of the state of an MCData imminent peril group.

MCData private emergency alert state: MCData client internal perspective of the state of an MCData private one‑to‑one emergency alert targeted to an MCData user.

Functional alias status: Applies for the status of a functional alias for an MCData user and has one of the following states:

a) the "not-activated" state indicating that the MCData user has not activated the functional alias;

b) the "activating" state indicating that the MCData user is interested in using the functional alias but the functional alias is not yet activated for the MCData user;

c) the "activated" state indicating that the MCData user has activated the functional alias;

d) the "deactivating" state indicating that the MCData user is no longer interested in using the functional alias but the functional alias is still activated for the MCData user; and

e) the "take-over-possible" state indicating that the MCData user is interested in using the functional alias but the functional alias is already activated and used by another MCData user.

User Requested Application Priority: The requested priority as defined in 3GPP TS 23.280 [3]. How the server determines the priority for the requested communication based on requested priority and in combination with other factors is up to MCData server implementation.

For the purpose of the present document, the following terms and definitions given in 3GPP TS 33.180 [26] apply:

Client Server Key (CSK)

Multicast Signalling Key (MuSiK)

Multicast Signalling Key Identifier (MuSiK-ID)

MBMS subchannel control key (MSCCK)

MBMS subchannel control key identifier (MSCCK-ID)

Private Call Key (PCK)

Signalling Protection Key (SPK)

XML Protection Key (XPK)

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

Functional alias

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].

CSK Client-Server Key

IMPU P Multimedia Public User identity

IPEG In-Progress Emergency Group

IPEPC In-Progress Emergency Private Call

IPIG In-Progress Imminent peril Group

MBMS Multimedia Broadcast and Multicast Service

MC Mission Critical

MCS Mission Critical Service

MCData Mission Critical Data

MCData group ID MCData group Identity

MDEA MCData Emergency Alert

MDEG MCData Emergency Group

MDEGC MCData Emergency Group Communication

MDEPC MCData Emergency Private (one‑to‑one) Communication

MDEPP MCData Emergency Private (one‑to‑one) Priority

MDES MCData Emergency State

MDIG MCData Imminent peril Group

MDIGC MCData Imminent peril Group Communication

MDPEA MCData Private (one‑to‑one) Emergency Alert

MIME Multipurpose Internet Mail Extensions

MONP MCPTT Off-Network Protocol

QCI QoS Class Identifier

RTP Real-time Transport Protocol

SAI Service Area Identifier

SDP Session Description Protocol

SIP Session Initiation Protocol

SPK Signalling Protection Key

URI Uniform Resource Identifier

URN Uniform Resource Name

UUID Universally Unique IDentifier

XPK XML Protection Key