Subclause 8.1.2 of 3GPP TS 23.280 [5]

MCData identity (MCData ID)

Y

Y

Y

Y

3GPP TS 33.180 [13]

KMSUri for security domain of MCData ID (see NOTE 1)

Y

Y

Y

Y

Subclause 5.2.4 of 3GPP TS 23.280 [5]

Pre‑selected MCData user profile indication (see NOTE 2)

Y

Y

Y

Y

Subclause 5.2.4 of 3GPP TS 23.280 [5]

MCData user profile index

Y

Y

Y

Y

Subclause 5.2.4 of 3GPP TS 23.280 [5]

MCData user profile name

Y

Y

Y

Y

[R-5.17-007],

[R-6.13.4-002] of 3GPP TS 22.280 [2]

User profile status (enabled/disabled)

Y

Y

Y

[R-5.7-001],

[R-6.9-003] of 3GPP TS 22.280 [2]

Authorised to create and delete aliases of an MCData user and its associated user profiles.

Y

Y

[R-5.7-002],

[R-6.9-003] of 3GPP TS 22.280 [2]

Alphanumeric aliases of user

Y

Y

Y

Y

[R-5.1.1-005],

[R-5.9-001] of 3GPP TS 22.280 [2]

Participant type of the user

Y

Y

Y

Y

[R-5.1.8-006],

[R-5.3-002],

[R-5.9-001],

[R-5.16.2-001],

[R-5.16.2-002] of 3GPP TS 22.280 [2]

User’s Mission Critical Organization (i.e. which organization a user belongs to)

Y

Y

Y

Y

[R-5.2.2-003] of 3GPP TS 22.280 [2]

Authorisation to create a group-broadcast group

Y

Y

[R-5.2.2-003] of 3GPP TS 22.280 [2]

Authorisation to create a user-broadcast group

Y

Y

[R-5.6.2.4.1-002] of 3GPP TS 22.280 [2]

Authorised to activate MCData emergency alert

Y

Y

Y

Y

[R-5.6.2.4.1-013] of 3GPP TS 22.280 [17]

Automatically trigger a MCData emergency communication after initiating the MCData emergency alert

Y

Y

Y

Y

[R-5.6.2.4.1-004]

[R-5.6.2.4.1-008]

[R-5.6.2.4.1-012] of 3GPP TS 22.280 [2]

Group used on initiation of an MCData emergency group communication (see NOTE 3)

[R-5.6.2.4.1-004], [R-5.6.2.4.1-008], [R-5.6.2.4.1-012] of 3GPP TS 22.280 [17]

Recipient for an MCData emergency private communication (see NOTE 3)

> MCData ID

Y

Y

Y

Y

3GPP TS 33.180 [19]

> KMSUri for security domain of MCData ID (see NOTE 1)

Y

Y

Y

Y

[R-5.6.2.4.2-002] of 3GPP TS 22.280 [2]

Authorisation to cancel an MCData emergency alert

Y

Y

Y

Y

[R-6.1.1.2-005],

[R-6.1.1.2-006],

[R-6.1.1.2-007] of 3GPP TS 22.282 [3]

Individual conversation hang time

Y

Y

Y

Y

One-to-one communication

[R-6.3.1.2-007] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13]

> List of MCData users this MCData user is authorized to initiate a one‑to-one communication

>> MCData ID

Y

N

Y

Y

>> Discovery Group ID

Y

N

Y

Y

>> User info ID (as specified in 3GPP TS 23.303 [7])

Y

N

Y

Y

>> KMSUri for security domain of MCData ID (see NOTE 1)

Y

Y

Y

Y

[R-6.7.3-007] of 3GPP TS 22.280 [2]

Authorised to make one-to-one communications towards users not included in "list of MCData user(s) this MCData user is authorized to initiate a one‑to-one communication"

Y

Y

Y

Y

File distribution

[R-5.3.2-010] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13]

> List of MCData users this MCData user is allowed to cancel distribution of files being sent or waiting to be sent

>> MCData ID

Y

Y

Y

Y

>> KMSUri for security domain of MCData ID (see NOTE 1)

Y

Y

Y

Y

Transmission and reception control

[R-6.2.2.1-001] of 3GPP TS 22.282 [3]

> Whether the MCData user is permitted to transmit data

Y

Y

Y

Y

[R-6.2.3-005] of 3GPP TS 22.282 [3]

> Maximum amount of data that the MCData user can transmit in a single request during one-to-one communication

Y

Y

Y

Y

[R-6.2.3-005] and [R‑6.3.1.2-008] of 3GPP TS 22.282 [3]

> Maximum amount of time that the MCData user can transmit in a single request during one-to-one communication

Y

Y

Y

Y

[R-6.2.3-001] of 3GPP TS 22.282 [3]

> List of MCData users this MCData user is allowed to request the release of an ongoing transmission that this MCData user is participating in

>> MCData ID

Y

Y

Y

Y

[R-5.1.7-002] and

[R-6.8.7.2-007] and [R-6.8.7.2-008] of 3GPP TS 22.280 [2]

Priority of the user (see NOTE 4)

Y

Y

Y

Lossless communication for private communication

Y

Y

Y

Y

Store communication in Message Store (see NOTE 5)

Y

Y

Y

Y

Store private communication in Message Store (see NOTE 6)

Y

Y

Y

Y

[R-6.12-003] of 3GPP TS 22.280 [17]

Authorised to restrict the dissemination of the location information

Y

Y

Y

Y

NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].

NOTE 2: As specified in 3GPP TS 23.280 [5], for each MCData user’s set of MCData user profiles, only one MCData user profile shall be indicated as being the pre‑selected MCData user profile.

NOTE 3: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCData user’s currently selected group will be used.

NOTE 4: The use of the parameter is left to implementation.

NOTE 5: This is the top-level control parameter to determine whether MCData communications will be stored or not. When this parameter is set; the second level control parameter is used to determine whether a specific MCData communication (private or which group) will be stored and MCData user can request for all or selected of his/her MCData communication shall be stored in the MCData message store or not.

NOTE 6: This is the second level control parameter to determine whether a private communication will be stored when the Store communication in Message Store top level control parameter is set.

[R-5.1.5-001],

[R-5.1.5-002],

[R-5.10-001],

[R-6.4.7-002],

[R-6.8.1-008],

[R-6.7.4-002] of 3GPP TS 22.280 [2]

List of on-network MCData groups for use by an MCData user

> MCData Group ID

Y

Y

Y

Y

> Store group communication in Message Store (see NOTE 11)

Y

Y

Y

Y

> Application plane server identity information of group management server where group is defined

>> Server URI

Y

Y

Y

Y

> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)

>> Server URI

Y

Y

Y

Y

3GPP TS 33.180 [13]

> KMSUri for security domain of group (see NOTE 2)

Y

Y

Y

Y

> Presentation priority of the group relative to other groups and users (see NOTE 3)

Y

N

Y

Y

> Transmission and reception control

>> Whether MCData user is permitted to transmit data in the group

Y

Y

Y

Y

>> Maximum amount of data that the MCData user can transmit in a single request during group communication

Y

Y

Y

Y

>> Maximum amount of time that the MCData user can transmit in a single request during group communication

Y

Y

Y

Y

Subclause 5.2.5 of 3GPP TS 23.280 [5]

List of groups user implicitly affiliates to after MCData service authorization for the user

> MCData Group ID

Y

Y

Y

Y

[R-6.4.2-006] of 3GPP TS 22.280 [2]

Authorisation of an MCData user to request a list of which MCData groups a user has affiliated to

Y

Y

Y

[R-6.4.6.1-002],

[R-6.4.6.1-003] of 3GPP TS 22.280 [2]

Authorisation to change affiliated groups of other specified user(s)

Y

Y

Y

[R-6.4.6.2-001],

[R-6.4.6.2-002] of 3GPP TS 22.280 [2]

Authorisation to recommend to specified user(s) to affiliate to specific group(s)

Y

Y

Y

[R-6.6.1-004] of 3GPP TS 22.280 [2]

Authorisation to perform regrouping

Y

Y

Y

Y

[R-6.7.2-001] of 3GPP TS 22.280 [2]

Presence status is available/not available to other users

Y

Y

Y

Y

[R-6.7.1-002],

[R-6.7.2-002] of 3GPP TS 22.280 [2]

List of MCData users that MCData user is authorised to obtain presence of

> MCData IDs

Y

Y

Y

Y

[R-6.8.7.4.2-001],
[R-6.8.7.4.2-002] of 3GPP TS 22.280 [2]

Authorisation of a user to cancel an emergency alert on any MCData UE of any user

Y

Y

Y

[R-6.13.4-001] of 3GPP TS 22.280 [2]

Authorisation for an MCData user to enable/disable an MCData user

Y

Y

Y

[R-6.13.4-003],
[R-6.13.4-005],
[R-6.13.4-006],
[R-6.13.4-007] of 3GPP TS 22.280 [2]

Authorisation for an MCData user to (permanently /temporarily) enable/disable a UE

Y

Y

Y

[R-7.14-002],

[R-7.14-003] of 3GPP TS 22.280 [2]

Authorization for manual switch to off-network while in on-network

Y

Y

Y

Y

[R-5.1.5-004] of 3GPP TS 22.280 [2]

Limitation of number of affiliations per user (N2)

N

Y

Y

Y

[R-6.4.6.1-001],

[R-6.4.6.1-004] of 3GPP TS 22.280 [2]

List of MCData users whose selected groups are authorized to be remotely changed

> MCData ID

Y

Y

Y

Y

[R-6.7.3-007a] of 3GPP TS 22.280 [2] and 3GPP TS 33.180 [13]

List of MCData users this MCData user is authorized to receive a one‑to-one communication

> MCData ID

Y

Y

Y

Y

> KMSUri for security domain of MCData ID

Y

Y

Y

Y

Conversation management

[R-6.1.1.2-009] of 3GPP TS 22.282 [3].

> List of MCData users to be sent message delivered disposition notifications in addition to the message sender

N

Y

Y

Y

>> MCData ID

N

Y

Y

Y

[R-6.1.1.2-009] of 3GPP TS 22.282 [3].

> List of MCData users to be sent message read disposition notifications in addition to the message sender

N

Y

Y

Y

>> MCData ID

N

Y

Y

Y

3GPP TS 23.283 [18]

Authorised to use LMR E2EE for interworking

Y

Y

Y

Y

3GPP TS 23.283 [18]

> List of supported LMR technology types

3GPP TS 23.283 [18]

>> LMR technology type (P25, TETRA etc.)

Y

N

Y

Y

3GPP TS 23.283 [18]

>> URI of LMR key management functional entity (see NOTE 4 )

Y

N

Y

Y

3GPP TS 23.283 [18]

>> LMR specific identity (RSI for P25 or ITSI for TETRA) (see NOTE 5)

Y

N

Y

Y

3GPP TS 23.283 [18]

>> LMR specific security information (see NOTE 5)

Y

N

Y

Y

List of servers used in the private and group communications

> MCData content server where the HTTP FD file is uploaded

>> Server URI

Y

Y

Y

Y

> MCData message store where the communication history stores

>> Server URI

Y

Y

Y

Y

Subclause 5.2.9 of 3GPP TS 23.280 [16]

List of partner MCData systems in which this profile is valid for use during migration

Subclause 5.2.9 of 3GPP TS 23.280 [16]

> Identity of partner MCData system

Y

Y

Y

Y

Subclause 10.1.1 of 3GPP TS 23.280 [16]

> Access information for partner MCData system (see NOTE 6)

Y

Y

Y

[R-5.9a-012] of 3GPP TS 22.280 [2]

[R-5.9a-013] of 3GPP TS 22.280 [2]

Authorised to request information query of the association between active functional alias(es) and the MCData ID(s)

Y

Y

Y

[R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [2]

List of groups the client affiliates/de-affiliates when criteria is met

> MCData Group ID

Y

Y

Y

Y

>> Criteria for affiliation (see NOTE 7)

Y

Y

Y

Y

>> Criteria for de-affiliation (see NOTE 7)

Y

Y

Y

Y

>> Manual de-affiliation is not allowed if criteria for affiliation are met

Y

Y

Y

Y

[R-6.6.4.2-002] of 3GPP TS 22.280 [2]

List of groups the client affiliates after receiving an emergency alert

> MCData Group ID

Y

Y

Y

Y

>> Manual de-affiliation is not allowed if criteria for affiliation are met

Y

Y

Y

Y

List of functional alias(es) of the MCData user

[R-5.9a-005] of 3GPP TS 22.280 [2]

> Functional alias

Y

Y

Y

Y

[R-5.9a-018] of 3GPP TS 22.280 [2]

>> Trigger criteria for activation by the MCData server (see NOTE 8)

N

Y

Y

Y

[R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [2]

>> Trigger criteria for de-activation by the MCData server (see NOTE 8)

N

Y

Y

Y

[R-5.9a-019] of 3GPP TS 22.280 [2]

>> Trigger criteria for activation by the MCData client (see NOTE 8)

Y

Y

Y

Y

[R-5.9a-019] of 3GPP TS 22.280 [2]

>> Trigger criteria for de-activation by the MCData client (see NOTE 8)

Y

Y

Y

Y

>> Manual de-activation is not allowed if the criteria are met (see NOTE 8)

Y

Y

Y

Y

[R-5.9a-012] of 3GPP TS 22.280 [2]

Authorised to take over a functional alias from another MCData user

Y

Y

Y

Authorised to participate in an IP connectivity session

Y

Y

Y

Y

[R-5.5.2-003],

[R-5.5.2-004] 3GPP TS 22.282 [3]

>List of MCData users which can be included in IP connectivity sessions.

>> MCData ID

Y

Y

Y

Y

3GPP TS 33.180 [13]

>> KMSUri for security domain of the MCData ID

Y

Y

Y

Y

>>List of associated data host IP information

>>>IP information (see NOTE 9)

Y

Y

Y

Y

[R-5.5.2-003] 3GPP TS 22.282 [3]

Authorised to initiate remote point-to-point IP connectivity sessions

N

Y

Y

Y

>List of MCData users which can be addressed in a remote initiated IP connectivity session;

>> MCData ID

N

Y

Y

Y

[R-5.5.2-003] 3GPP TS 22.282 [3]

Authorised to tear down point-to-point IP connectivity sessions

N

Y

Y

Y

>List of MCData users which can be addressed in a remote initiated IP connectivity session tear down;

>> MCData ID

N

Y

Y

Y

[R-5.5.2-006]

3GPP TS 22.282 [3]

Authorised to request remotely application priority modification of established point-to-point IP connectivity sessions;

>List of MCData users which can be addressed remotely to change the application priority of established IP connectivity sessions;

Y

Y

Y

Y

[R-5.10-001b] 3GPP TS 22.280 [2]

Maximum number of successful simultaneous MCData service authorizations for this user (see NOTE 10)

N

Y

Y

Y

NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].

NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].

NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document.

NOTE 4: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document.

NOTE 5: This is an LMR specific parameter with no meaning within MC services.

NOTE 6: Access information for each partner MCData system comprises the list of information required for initial UE configuration to access an MCData system, as defined in table A.6-1 of 3GPP TS 23.280 [16]

NOTE 7: The criteria may consist conditions such as the location of the MCData user or the active functional alias of the MCData user.

NOTE 8: The criteria may consist of conditions such as MCData user location or time.

NOTE 9: IP information may contain IP addresses, corresponding subnet masks, gateway and DNS settings.

NOTE 10: If configured, this value has precedence over the system level parameter "maximum number of successful simultaneous service authorisations" in table A.5-2. If not configured, the corresponding parameter from table A.5-2 shall be used.

NOTE 11: This is the second level control parameter to determine whether this group communication will be stored in the MCData message store when the Store communication in Message Store top level control parameter is set.

[R-7.2-003],

[R-7.6-004] of 3GPP TS 22.280 [2]

List of off-network MCData groups for use by this MCData user

> MCData Group ID

Y

N

Y

Y

> Store group communication in Message Store (see NOTE 4)

Y

N

Y

Y

> Application plane server identity information of group management server where group is defined

>> Server URI

Y

N

Y

Y

> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)

>> Server URI

Y

N

Y

Y

3GPP TS 33.180 [13]

> KMSUri for security domain of group (see NOTE 2)

Y

N

Y

Y

> Presentation priority of the group relative to other groups and users (see NOTE 3)

Y

N

Y

Y

[R-7.12-002],

[R-7.12-003] of 3GPP TS 22.280 [2]

Authorization for off-network services

Y

N

Y

Y

Subclause 7.16.1

User info ID (as specified in 3GPP TS 23.303 [7])

Y

N

Y

Y

NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of TS 23.280 [5].

NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].

NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document.

NOTE 4: This is the second level control parameter to determine whether this group communication will be stored in the MCData message store when the Store communication in Message Store top level control parameter is set.