Content for TS 23.280 Word version: 19.5.0

1… 5… 6 7… 8… 9… 10… 10.1.5… 10.2… 10.2.6… 10.3… 10.6… 10.7… 10.7.3.8… 10.8… 10.9… 10.9.3.9… 10.10… 10.10.3 10.11… 10.12… 10.13… 10.14… 10.15… 10.16… 10.17… 10.18… 10.19… 11… 11.5… A… B… C… E…

A.1 General A.2 MC service UE configuration data A.3 MC service user profile configuration data A.4 Group configuration data A.5 MC service configuration data A.6 Initial MC service UE configuration data A.7 Initial MC gateway UE configuration data A.8 Location user profile configuration data A.9 ACM client user profile configuration data A.10 Initial recording admin UE and/or replay UE configuration data A.11 Recording admin and/or replay service user profile configuration data
...

A (Normative) Configuration data for MC services p. 395

A.1 General p. 395

This Annex provides information about the static data needed for configuration for MC services, which belong to one of the following categories:

MC service UE configuration data (see subclause A.2);
MC service user profile data (see subclause A.3);
MC service group configuration data (see subclause A.4);
MC service configuration data (see subclause A.5); and
Initial MC service UE configuration data (see subclause A.6).
Initial recording admin UE and/or replay UE configuration data (see subclause A.10).

For each configuration category, data is split between configuration data that is applicable to both on-network and off-network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MC service UE, MC service group, MC service user and MC service configuration data refers to the information that will be stored against each MC service UE, MC service group, MC service user and MC service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element.

The columns in the tables have the following meanings:

Reference: the reference of the corresponding requirement in TS 22.280 or TS 22.281 or TS 22.282 or TS 22.179 or the corresponding subclause from the present document.
Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy.
When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used:
- "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column.
- "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column.

Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all the three tables of on-network and off-network, on-network only and off-network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top-most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters.

Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.

A.2 MC service UE configuration data p. 396

MC service UE configuration data has to be known by an MC service UE after MC service authorization. The CSC-4 reference point is used for configuration between the configuration management server and the configuration management client on the MC service UE when the MC service UE is on-network.

MC service UE configuration data can be configured offline using the CSC-11 reference point.

MC service UE configuration data is specific to each MC service and is specified as follows:

MCPTT UE configuration data is specified in TS 23.379;
MCVideo UE configuration data is specified in TS 23.281; and
MCData UE configuration data is specified in TS 23.282.

Within each MC service, the MC service UE configuration data can be the same or different across MC service UEs.

A.3 MC service user profile configuration data p. 396

The MC service user profile configuration data is stored in the MC service user database. The configuration management server is used to configure the MC service user profile configuration data to the MC service user database (CSC-13) and MC service UE (CSC-4).

MC service user profile configuration data can be configured offline using the CSC-11 reference point.

MC service user profile configuration data is specific to each MC service and is specified as follows:

MCPTT user profile configuration data is specified in TS 23.379;
MCVideo user profile configuration data is specified in TS 23.281;
MCData user profile configuration data is specified in TS 23.282; and
Location user profile configuration data is specified in clause A.8.
Recording admin and/or replay service user profile configuration data is specified in clause A.11.

A.4 Group configuration data p. 396

The group configuration data is stored in the group management server. The group management server is used to configure the group configuration data to the MC service UE (CSC-2), recording admin UE (CSC-2), replay UE (CSC-2), MC service server (CSC-3) and the recording server (REC-5).

A single group can support one or multiple MC service configurations. Hence, the MC service group configuration data is divided into common group configuration data and MC service specific group configuration data.

The group configuration data can be configured offline using the CSC-12 reference point.

The common group configuration data are specified in Table A.4-1. Table A.4-1 and Table A.4-2 contain the group configuration required to support the use of on-network MC service. Table A.4-1 and Table A.4-3 contain the group configuration required to support the use of off-network MC service.

The MC service related group configuration data specific to each MC service is specified as follows:

MCPTT related group configuration data is specified in TS 23.379;
MCVideo related group configuration data is specified in TS 23.281; and
MCData related group configuration data is specified in TS 23.282;

Table A.4-1: Common group configuration data (on and off network)

Reference	Parameter description	MC service UE	Rec. admin UE & Replay UE (see NOTE 9)	MC service Server	Group management server	Recording server
[R-5.17-004], [R-6.4.3-001], [R-6.4.3-002], [R-6.9-004] and [R-5.1.3-002] of TS 22.280	MC service group ID	Y	Y	Y	Y	Y
[R-5.17-004], [R-6.4.3-001], [R-6.4.3-002] and [R-6.9-004] of TS 22.280	Group Alias (Contact URIs)	Y		Y	Y
	List of group members (see NOTE 1) (see NOTE 8)
[R-5.1.3-001], [R-5.1.5-001], [R-6.4.5-005] and [R-6.4.5-006] of TS 22.280	> MCPTT
	>> MCPTT ID (see NOTE 2)	N	Y	Y	Y
3GPP TS 33.180	>> KMSUri for security domain of the MCPTT ID (see NOTE 3)	N		Y	Y
[R-6.2.2-001] and [R-7.6-007] of TS 22.280, [R-6.2.3.7.4.1-002] and [R-6.2.3.7.4.1-006] of TS 22.179	>> User priority for the group	N		Y	Y
[R-5.1.3-001] of TS 22.280	>> Participant type for the group (group membership information). The particpant type values are defined and configured by the Mission Critical Organisation (e.g.first responder, second responder, dispatcher, dispatch supervisor, MC service administrator).	N	Y	Y	Y
[R-5.1.3-001], [R-5.1.5-001], [R-6.4.5-005] and [R-6.4.5-006] of TS 22.280	> MCVideo
	>> MCVideo ID (see NOTE 2)	N	Y	Y	Y
3GPP TS 33.180	>> KMSUri for security domain of the MCVideo ID (see NOTE 3)	N		Y	Y
[R-6.2.2-001] and [R-7.6-007] of TS 22.280	>> User priority for the group	N		Y	Y
[R-5.1.3-001] of TS 22.280	>> Participant type for the group (group membership information). The particpant type values are defined and configured by the Mission Critical Organisation (e.g.first responder, second responder, dispatcher, dispatch supervisor, MC service administrator).	N	Y	Y	Y
[R-5.1.3-001], [R-5.1.5-001], [R-6.4.5-005] and [R-6.4.5-006] of TS 22.280	> MCData
	>> MCData ID (see NOTE 2)	N	Y	Y	Y
3GPP TS 33.180	>> KMSUri for security domain of the MCData ID (see NOTE 3)	N		Y	Y
[R-6.2.2-001] and [R-7.6-007] of TS 22.280	>> User priority for the group	N		Y	Y
[R-5.1.3-001] of TS 22.280	>> Participant type for the group (group membership information). The particpant type values are defined and configured by the Mission Critical Organisation (e.g.first responder, second responder, dispatcher, dispatch supervisor, MC service administrator).	N	Y	Y	Y
[R-5.16.2-001] and [R-5.16.2-002] of TS 22.280	Group's owner (Mission Critical Organisation)	Y	Y	Y	Y	Y
Subclause 8.3.2, 10.2.3	MC service specific configuration (see NOTE 4)
	> MCPTT configuration (see NOTE 5)
	> MCVideo configuration (see NOTE 6)
	> MCData configuration (see NOTE 7)
	List of subordinate groups
[R-5.2.2-002] of TS 22.280	> MC service group ID	N	Y	Y	Y
	Group broadcast information
[R-5.2.2-001] of TS 22.280	Level within group hierarchy	N		Y	Y
[R-5.2.3-001] of TS 22.280	Level within user hierarchy	N		Y	Y
Subclause 10.6.2.9 of TS 23.379	Group is a preconfigured regroup group	Y	Y	Y	Y
[R-5.2.1-002] of TS 22.280	Group is a broadcast group	Y	Y	Y	Y
[R-6.15.4-001…010] of TS 22.280	Group is a target for recording	Y (see NOTE 11)	Y	Y	Y	Y
[R-6.15.4-001…010] of TS 22.280	Recording server address (URI) (see NOTE 10)	Y (see NOTE 11)	Y	Y	Y
NOTE 1: The list of group members is provided to an authorized user only upon request and not by default. NOTE 2: MC service IDs for all configured MC services shall be provided for the configured group member. NOTE 3: 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. NOTE 4: An MC service specific configuration shall be provided for all of the MC services for which the group is enabled. At least one MC service shall be enabled for a group. NOTE 5: This parameter is a parent parameter whose child parameters are defined in TS 23.379. NOTE 6: This parameter is a parent parameter whose child parameters are defined in TS 23.281. NOTE 7: This parameter is a parent parameter whose child parameters are defined in TS 23.282. NOTE 8: The list of group members comprises all group members in primary and in partner MC systems of the MC service group. NOTE 9: This is the recording admin UE and/or replay UE of a user who is authorized to set this MC service group as a target for recording and/or authorized to replay this MC service group's recordings. NOTE 10: If this parameter is absent, the Recording server URI shall be that identified in the initial MC service UE configuration data (on-network, Table A.6-1) or in the initial recording admin and replay UE configuration data (on-network, Table A.10-1). NOTE 11: These parameters, when provided to an MC service UE, are relevant only for recording administrators and replay users.

Table A.4-2: Common group configuration data (on-network)

Reference	Parameter description	MC service UE	MC service Server	Group management server
[R-6.1-001] of TS 22.280	Maximum number of group members (Nc6)	N	Y	Y
[R-6.1-003] of TS 22.280	Enabled/disabled group (basic status)	Y	Y	Y
[R-6.6.1-006] of TS 22.280	Temporary group indication	Y	Y	Y
[R-6.4.5-005] and [R-6.15.4-001…010] of TS 22.280	List of authorised users who can request the list of members of an MC service group	Y	Y	Y
	> MCPTT IDs			Y
	> MCVideo IDs			Y
	> MCData IDs			Y
	> MCRec IDs			Y
	MC service specific configuration
	> MCPTT configuration (see NOTE 1)
	> MCVideo configuration (see NOTE 2)
	> MCData configuration (see NOTE 3)
[R-6.4.9-006] of TS 22.280	Geographic area within which affiliation to the group is permitted (see NOTE 4)	Y	Y	Y
[R-6.4.9-006] of TS 22.280	Geographic area outside which de-affiliation from the group is mandatory (see NOTE 4)	Y	Y	Y
Subclause 10.2.5 and [R-6.15.4-001…010] of TS 22.280	List of authorised users who can retrieve the group information
> MCPTT IDs				Y
> MCVideo IDs				Y
> MCData IDs				Y
> MCRec IDs				Y
Subclause 5.2.3	Associated relay service code (as specified in TS 23.303)	Y	N	Y
Subclause 5.2.9 of TS 23.280	List of partner MC systems from which interconnection is permitted for the group
Subclause 5.2.9 of TS 23.280	> Identity of partner MCPTT system		Y	Y
Subclause 5.2.9 of TS 23.280	> Identity of partner MCVideo system		Y	Y
Subclause 5.2.9 of TS 23.280	> Identity of partner MCData system		Y	Y
[R-6.4.4-003] of TS 22.280	List of functional aliases which prevents de-affiliating
> Functional alias		N	Y	Y
[R-6.4.4-004] of TS 22.280	List of functional aliases which prevents de-affiliating, if only one user has bound the functional alias to the group
	> Functional alias	N	Y	Y
NOTE 1: This parameter is a parent parameter whose child parameters are defined in TS 23.379. NOTE 2: This parameter is a parent parameter whose child parameters are defined in TS 23.281. NOTE 3: This parameter is a parent parameter whose child parameters are defined in TS 23.282. NOTE 4: The geographic area may consist of a union of regions that are non-contiguous or contain holes.

Table A.4-3: Common group configuration data (off-network)

Reference	Parameter description	MC service UE	MC service server	Group management server
Subclause 8.1.3.2	ProSe layer-2 group ID (as specified in TS 23.303)	Y	N	Y
Subclause 8.1.3.2	ProSe group IP multicast address (as specified in TS 23.303)	Y	N	Y
Subclause 8.1.3.2	Indication of whether the UE shall use Ipv4 or Ipv6 for the MC service group (as specified in TS 23.303)	Y	N	Y
	MC service specific configuration
	> MCPTT configuration (see NOTE 1)
	> MCVideo configuration (see NOTE 2)
	> MCData configuration (see NOTE 3)
NOTE 1: This parameter is a parent parameter whose child parameters are defined in TS 23.379. NOTE 2: This parameter is a parent parameter whose child parameters are defined in TS 23.281. NOTE 3: This parameter is a parent parameter whose child parameters are defined in TS 23.282.

A.5 MC service configuration data p. 403

The MC service configuration data is stored in the MC service server. The configuration management server is used to configure the MC service configuration data to the MC service server (CSC-5) and the MC service UE (CSC-4).

The MC service configuration data can be configured offline using the CSC-11 reference point.

The MC service configuration data is specific to each MC service and hence the detailed list of MC service configuration data is listed as follows:

MCPTT service configuration data is specified in TS 23.379;
MCVideo service configuration data is specified in TS 23.281; and
MCData service configuration data is specified in TS 23.282;

A.6 Initial MC service UE configuration data p. 403

The initial MC service UE configuration data is essential to the MC service UE to successfully connect to the MC system. The initial MC service UE configuration data can be the same or different across MC service UEs.

Data in Table A.6-1 is provided to the MC service UE's clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client, replay client) during the bootstrap process (see subclause 10.1.1), and can be configured on the MC service UE offline using the CSC-11 reference point or via other means e.g. as part of the MCPTT client's provisioning on the UE, using a device management procedure.

Table A.6-1: Initial MC service UE configuration data (on-network)

Reference	Parameter description
Subclause 10.1.1	PDN connectivity information
	> HPLMN ID and optionally VPLMN ID to which the data pertains
	> MC services PDN
	>> APN
	>> PDN access credentials
	> MC common core services PDN
	>> APN
	>> PDN access credentials
	> MC identity management service PDN
	>> APN
	>> PDN access credentials
Subclause 10.1.1	Application plane server identity information
	> Identity management server
	>> Server URI
	> Configuration management server
	>> Server URI
	> Key management server
	>> Server URI (also known as KMSUri for security domain managed by KMS)
	> Indication of whether the UE shall use Ipv4 or Ipv6 for on-network MCPTT
	> MCPTT Server
	>> Server URI
	> Indication of whether the UE shall use Ipv4 or Ipv6 for on-network MCData
	> MCData Server
	>> Server URI
	> Indication of whether the UE shall use Ipv4 or Ipv6 for on-network MCVideo
	> MCVideo Server
	>> Server URI
	> Location management server
	>> Server URI
	> Recording server (see NOTE 1)
	>> Server URI
Subclause 10.1.1	Operational information
	> MC service UE label (see NOTE 2)
NOTE 1: This parameter shall be present only if this MC service UE contains a replay client. NOTE 2: The MC service UE label is optional.

A.7 Initial MC gateway UE configuration data |R19| p. 405

A.8 Location user profile configuration data |R18| p. 405

The location user profile configuration data is stored in the location user database. The location management server obtains the location user profile configuration data via the configuration management server (CSC-24).

Table A.8-1 contains the location user profile configuration required to support the use of on-network location service. Data in Table A.8-1 can be configured offline using the CSC-11 reference point.

Table A.8-1: location user profile data (on and off network)

Reference	Parameter description	Location UE	Location Server	Configuration management server	Location user database
[R-5.11-007] of TS 22.280 Clause 10.9.3.3	Authorization to set a trigger at a LMC
	> List of MC service IDs for which a trigger is authorized to be set	Y	Y	Y	Y
	>> MCPTT ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData ID (see NOTE 1)	Y	Y	Y	Y
	> List of MC service group IDs for which a trigger is authorized to be set	Y	Y	Y	Y
	>> MCPTT group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData group ID (see NOTE 1)	Y	Y	Y	Y
[R-5.11-008] of TS 22.280	Authorization to cancel a trigger at a LMC
	> List of MC service IDs for which a trigger is authorized to be cancelled	Y	Y	Y	Y
	>> MCPTT ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData ID (see NOTE 1)	Y	Y	Y	Y
	> List of MC service group IDs for which a trigger is authorized to be cancelled	Y	Y	Y	Y
	>> MCPTT group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData group ID (see NOTE 1)	Y	Y	Y	Y
Clause 10.9.3.5 Clause 10.9.3.7	Authorization to subscribe to location information for an MC user
	> List of MC service IDs for which subscription and subscription cancellation is authorized	Y	Y	Y	Y
	>> MCPTT ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData ID (see NOTE 1)	Y	Y	Y	Y
	> List of MC service group IDs for which subscription and subscription cancellation is authorized	Y	Y	Y	Y
	>> MCPTT group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData group ID (see NOTE 1)	Y	Y	Y	Y
Clause 10.9	Authorised to request location information of another user in the primary MC system (see NOTE 3)	Y	Y	Y	Y
	> List of MC service IDs for which requesting location information is authorised
	>> MCPTT ID	Y	Y	Y	Y
	>> MCVideo ID	Y	Y	Y	Y
	>> MCData ID	Y	Y	Y	Y
Clause 10.9	Authorised to share the location information with an MC service user (NOTE 3)
	> List of MC service IDs for which sharing location information is authorised (NOTE 4)
	>> MCPTT ID	Y	Y	Y	Y
	>> MCVideo ID	Y	Y	Y	Y
	>> MCData ID	Y	Y	Y	Y
	> List of MC service group IDs for which obtaining location information is authorized
	>> MCPTT group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCVideo group ID (see NOTE 1)	Y	Y	Y	Y
	>> MCData group ID (see NOTE 1)	Y	Y	Y	Y
Clause 10.9.3.10.6 Clause 10.9.3.11	Authorization to modify the location user profile of an MC user
	> Modification to the location user profile is permanent/temporary	Y	N	Y	Y
	>> Duration of time for temporary modification	Y	N	Y	Y
	> List of MC service IDs for which modifying the location reporting configuration is authorized	Y	N	Y	Y
	>> MCPTT ID (see NOTE 1)	Y	N	Y	Y
	>> MCVideo ID (see NOTE 1)	Y	N	Y	Y
	>> MCData ID (see NOTE 1)	Y	N	Y	Y
[R-6.12-003] of TS 22.280	Authorised to restrict the dissemination of the location information	Y	Y	Y	Y
Clause 10.9	List of partner MC systems for which an MC user is authorised to request location information for another MC user
	> Identity of partner MCPTT system	Y	Y	Y	Y
	> Identify of partner MCVideo system	Y	Y	Y	Y
	> Identity of partner MCData system	Y	Y	Y	Y
Clause 10.9.3.12.2 Clause 10.9.3.12.3	List of MC service IDs for which trigger overriding and cancelling an override is authorized
	> MCPTT ID (see NOTE 1)	Y	Y	Y	Y
	> MCVideo ID (see NOTE 1)	Y	Y	Y	Y
	> MCData ID (see NOTE 1)	Y	Y	Y	Y
Clause 10.9.1	Default location reporting configuration
	> Requested non-emergency location information (see NOTE 5)	Y	Y	Y	Y
	> Requested emergency location information (see NOTE 5)	Y	Y	Y	Y
	> Triggering criteria in non- emergency cases (see NOTE 5)	Y	Y	Y	Y
	> Triggering criteria in emergency cases (see NOTE 5)	Y	Y	Y	Y
	> Minimum time between consecutive reports for emergency cases (see NOTE 5)	Y	Y	Y	Y
	> Minimum time between consecutive reports for non-emergency cases (see NOTE 5)	Y	Y	Y	Y
	> Handling criteria in not reporting location information cases (see NOTE 5)	Y	Y	Y	Y
	> Triggering criteria in not reporting location information cases (see NOTE 5)	Y	Y	Y	Y
NOTE 1: There can be zero or more. NOTE 2: The default authorization applies to all MC users not listed as specifically authorized or not authorized. The intent of this parameter is to avoid having to list all MC users as specifically authorized or not authorized and allowing the administrator to only indicate specific authorization statuses. NOTE 3: Further differentiation on authorisation for location information based on detailed characteristics (e.g. MC organization, MC service ID, functional alias) is left to implementation. NOTE 4: If the list of MC service IDs, for which sharing location information is authorised, is empty, then the MC service user shares their location information with any requesting MC service user. NOTE 5: For a description of this parameter see Table 10.9.2.1-1 Location reporting configuration.

A.9 ACM client user profile configuration data |R19| p. 409

The ACM client user profile configuration data is stored at the MC system's ACM server and at the Configuration management server. The authorisations of requesting ACM clients will be verified based on valid entries in Table A.9-1.

Table A.9-1: MC service user profile configurations for authorisation of ACM (on-network)

Reference	Parameter description	ACMC	ACMS	Configuration management server
Subclause 5.16.4 of TS 22.280	Authorised to perform ACM transactions	Y	Y	Y
Subclause 5.16.4 of TS 22.280	List of permitted partner MC systems
	> Identity of partner MC service system	Y	Y	Y
Subclause 5.16.4 of TS 22.280	>> Access information for ACMS	Y	Y	Y
Subclause 5.16.4 of TS 22.280	>> List of authorized actions
	>>> Action	Y	Y	Y
	>>> Request to provide interconnection MC service group ID to partner MC system	Y	Y	Y
	>>> Request to update members of an interconnection MC service group	Y	Y	Y
	>>> Request to query interconnection MC service group ID from partner MC system	Y	Y	Y
	>>> Request to add MC service users of its primary MC system for migration to partner MC system	Y	Y	Y
	>>> Request to delete MC service users of its primary MC system from migration to partner MC system	Y	Y	Y
	>>> Request to update MC service UE initial configuration of its primary MC system for MC service users at partner MC system which are permitted to migrate	Y	Y	Y
	>>> Request to update MC service user profiles assigned by partner MC system for primary MC system's user permitted to migrate	Y	Y	Y

A.10 Initial recording admin UE and/or replay UE configuration data |R19| p. 410

The initial recording admin UE and/or replay UE configuration data is essential to the recording admin UEs and replay UEs to successfully connect to the MC system.

Data in Table A.10-1 is provided to the recording admin UEs and replay UEs clients (identity management client, configuration management client, replay client) during the bootstrap process of a recording admin UE and/or replay UE (see subclause 10.18.1.2 and 10.18.1.3) and can be configured offline using the CSC-11 reference point or via other means e.g. as part of the recording client's or replay client's provisioning on the UE, using a device management procedure.

Table A.10-1: Initial recording admin UE and/or replay UE configuration data (on-network)

Reference	Parameter description
Subclause 10.1.1	PDN connectivity information (NOTE 1)
	> HPLMN ID and optionally VPLMN ID to which the data pertains
	> MC common core services PDN
	>> APN
	>> PDN access credentials
	> MC identity management service PDN
	>> APN
	>> PDN access credentials
	Non-3GPP access network connectivity information (NOTE 2)
Subclause 10.1.1	Application plane server identity information
	> Identity management server
	>> Server URI
	> Configuration management server
	>> Server URI
	> Recording server (NOTE 3)
	>> Server URI
Subclause 10.1.1	Operational information
	> Recording admin and replay UE label (see NOTE 4)
NOTE 1: The PDN connectivity information is included only when this UE uses 3GPP network to access the MC servers. NOTE 2: This parameter is included only when this UE uses non-3GPP access network to access the MC servers. The detailed parameters are out of scope of the present document. NOTE 3: This parameter shall be present only if this UE contains a replay client. NOTE 4: The Recording admin and replay UE label is optional.

A.11 Recording admin and/or replay service user profile configuration data |R19| p. 411

The recording admin and/or replay service user profile configuration data is stored in the configuration management server. The recording server and the group management server obtain the recording admin and/or replay service user profile configuration data from the configuration management server.

Table A.11-1 contains the recording admin and/or replay service user profile configuration required to support the use of on-network recording and replay service. Data in Table A.11-1 can be configured offline using the CSC-11 reference point.

Table A.11-1: Recording admin and/or replay service user profile configuration data (on-network)

Reference	Parameter description	Rec. admin UE & Replay UE	Recording server	Configuration management server	Group management server
[R-6.15.4-001…010] of TS 22.280 and subclause 5.2.4a	Recording admin and replay user identity (MCRec ID)	Y	Y	Y	Y
Subclause 5.2.4a	Recording admin and/or replay user profile name	Y		Y
Subclause 5.2.4a	User profile status (enabled/disable)	Y	Y	Y	Y
[R-6.15.4-001] of TS 22.280 and subclause 5.2.4a	User's Mission Critical Organization	Y	Y	Y	Y
[R-6.15.4-001] - [R-6.15.4-010] of TS 22.280 and subclause 5.2.4a	Authorized to set and modify target MC service users for recording in his/her organization (yes/no)	Y		Y
	> All MC service users (see NOTE 1)
	>> MCPTT	Y		Y
	>> MCVideo	Y		Y
	>> MCData	Y		Y
	> All MC service users with exceptions (see NOTE 1)
	>> List of exceptions (see NOTE 5)
	>>> MCPTT ID	Y		Y
	>>> MCVideo ID	Y		Y
	>>> MCData ID	Y		Y
	> Only the listed MC service users (see NOTE 1)
	>> List of users (see NOTE 5)
	>>> MCPTT ID	Y		Y
	>>> MCVideo ID	Y		Y
	>>> MCData ID	Y		Y
[R-6.15.4-001] - [R-6.15.4-010] of TS 22.280 and subclause 5.2.4a	Authorized to set and modify target groups for recording in his/her organization (yes/no)	Y		Y	Y
	> All MC service groups (see NOTE 2)
	>> MCPTT	Y		Y	Y
	>> MCVideo	Y		Y	Y
	>> MCData	Y		Y	Y
	> All MC service groups with exceptions (see NOTE 2)
	>> List of exceptions (see NOTE 5)
	>>> MC service group ID	Y		Y	Y
	>>> Group management server URI	Y		Y	Y
	> Only the listed MC service groups (see NOTE 2)
	>> List of groups (see NOTE 5)
	>>> MC service group ID	Y		Y	Y
	>>> Group management server URI	Y		Y	Y
[R-6.15.4-001] - [R-6.15.4-010] of TS 22.280 and subclause 5.2.4a	Authorized to replay recordings of users in his/her organization (yes/no)	Y	Y	Y
	> All MC service users (see NOTE 3)
	>> MCPTT	Y	Y	Y
	>> MCVideo	Y	Y	Y
	>> MCData	Y	Y	Y
	> All MC service users with exceptions (see NOTE 3)
	>> List of exceptions (see NOTE 5)
	>>> MCPTT ID	Y	Y	Y
	>>> MCVideo ID	Y	Y	Y
	>>> MCData ID	Y	Y	Y
	> Only the listed MC service users (see NOTE 3)
	>> List of users (see NOTE 5)
	>>> MCPTT ID	Y	Y	Y
	>>> MCVideo ID	Y	Y	Y
	>>> MCData ID	Y	Y	Y
[R-6.15.4-001] - [R-6.15.4-010] of TS 22.280 and subclause 5.2.4a	Authorized to replay recordings of MC service groups in his/her organization (yes/no)	Y	Y	Y
	> All groups (see NOTE 4)
	>> MCPTT	Y	Y	Y
	>> MCVideo	Y	Y	Y
	>> MCData	Y	Y	Y
	> All MC service groups with exceptions (see NOTE 4)
	>> List of exceptions (see NOTE 5)
	>>> MC service group ID	Y	Y	Y
	>>> Group management server URI	Y	Y	Y
	> Only the listed groups (see NOTE 4)
	>> List of groups (see NOTE 5)
	>>> MC service group ID	Y	Y	Y
	>>> Group management server URI	Y	Y	Y
NOTE 1: If authorized to set and modify target MC service users for recording, one and only one of these parameter sets shall be set. NOTE 2: If authorized to set and modify target groups for recording, one and only one of these parameter sets shall be set. NOTE 3: If authorized to replay recordings of users, one and only one of these parameter sets shall be set. NOTE 4: If authorized to replay recordings of groups, one and only one of these parameter sets shall be set. NOTE 5: The list may contain zero or more of each of its subitems, but if included, the list shall not be empty.