Content for TS 23.379 Word version: 19.0.0

1… 7… 7.4… 10… 10.5… 10.6… 10.6.2.2.18… 10.6.2.2.34… 10.6.2.3… 10.6.2.3.1.2… 10.6.2.3.2… 10.6.2.4… 10.6.2.4.3… 10.6.2.5… 10.6.2.5.2.3… 10.6.2.6… 10.6.2.6.2… 10.6.2.7… 10.6.2.9… 10.6.2.9.3… 10.6.2.9.4… 10.6.2.10… 10.6.3… 10.7… 10.7.2.2… 10.7.2.3… 10.7.3… 10.7.4… 10.7.5… 10.7.5.2.3a… 10.7.6… 10.7.6.2.3… 10.9… 10.9.1.3… 10.9.1.3.2… 10.9.1.3.3… 10.9.1.4… 10.9.1.5… 10.9.2… 10.9.2.6… 10.10… 10.12… 10.14… 10.15… 10.19… 10.19.3… 10.19.3.2… A… A.4… B…

A.1 General A.2 MCPTT UE configuration data A.3 MCPTT user profile configuration data
...

A (Normative) MCPTT related configuration data p. 273

A.1 General p. 273

This Annex provides information about the static data needed for configuration for the MCPTT service, which belongs to one of the following categories:

MCPTT UE configuration data (see sub-clause A.2);
MCPTT user profile configuration data (see sub-clause A.3);
MCPTT related group configuration data (see sub-clause A.4); and
MCPTT service configuration data (see sub-clause A.5).

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 MCPTT UE, MCPTT group, MCPTT user and MCPTT service configuration data refers to the information that will be stored against each MCPTT UE, MCPTT group, MCPTT user and MCPTT 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.179 or TS 22.280 or TS 23.280 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 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 MCPTT UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.

A.2 MCPTT UE configuration data p. 274

The general aspects of UE configuration are specified in TS 23.280. Data in Table A.2-1 and Table A.2-2 have to be known by the MCPTT UE after MCPTT authorization.

Data in Table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-2 contains the UE configuration required to support the use of off-network MCPTT service.

Table A.2-1: UE configuration data (on and off network)

Reference	Definition
[R-5.4.2-002] of TS 22.280	Maximum number of simultaneous group calls (Nc4)
[R-5.4.2-003] of TS 22.280	Maximum number of transmissions (Nc5) in a group
[R-5.5.2-007] of TS 22.280	Maximum number of private calls (N10)

Table A.2-2: UE configuration data (on network)

Reference	Definition
Subclause 5.2.3 of TS 23.280	Relay service (Y/N)
Subclause 5.2.3 of TS 23.280	List of allowed relayed MCPTT groups and their relay service code (as specified in TS 23.303) (optional) (see NOTE)
	> MCPTT group ID
	> Relay service code (as specified in TS 23.303)
NOTE: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed.

A.3 MCPTT user profile configuration data p. 274

The general aspects of MC service user profile configuration data are specified in TS 23.280. The MCPTT user profile configuration data is stored in the MCPTT user database. The MCPTT server obtains the MCPTT user profile configuration data from the MCPTT user database (MCPTT-2).

Table A.3-1 and Table A.3-2 contain the MCPTT user profile configuration required to support the use of on-network MCPTT service. Table A.3-1 and Table A.3-3 contain the MCPTT user profile configuration required to support the use of off-network MCPTT service. Data in Table A.3-1 and Table A.3-3 can be configured offline using the CSC-11 reference point.

Table A.3-1: MCPTT user profile data (on and off network)

Reference	Parameter description	MCPTT UE	MCPTT Server	Configuration management server	MCPTT user database
Subclause 8.1.2 of TS 23.280	MCPTT user identity (MCPTT ID)	Y	Y	Y	Y
TS 33.180	KMSUri for security domain of MCPTT ID (see NOTE 4)	Y	Y	Y	Y
Subclause 5.2.4 of TS 23.280	Pre-selected MCPTT user profile indication (see NOTE 3)	Y	Y	Y	Y
Subclause 5.2.4 of TS 23.280	MCPTT user profile index	Y	Y	Y	Y
Subclause 5.2.4 of TS 23.280	MCPTT user profile name	Y	Y	Y	Y
[R-5.19-007], [R-6.13.4-002] of TS 22.280	User profile status (enabled/disabled)		Y	Y	Y
[R-5.8-001], [R-6.9-003] of TS 22.280	Authorised to create and delete aliases of an MCPTT User and its associated user profiles.			Y	Y
[R-5.8-002], [R-6.9-003] of TS 22.280	Alphanumeric aliases of user	Y	Y	Y	Y
[R-5.10-001] of TS 22.280	Participant type of the user	Y	Y	Y	Y
[R-5.3-002], [R-5.10-001] of TS 22.280	User's Mission Critical Organization (i.e. which organization a user belongs to)	Y	Y	Y	Y
[R-5.4.2-003] of TS 22.280	Maximum number of simultaneously received group calls (Nc5)		Y	Y	Y
[R-5.6.5-004] of TS 22.179	Authorised to make a private call	Y	Y	Y	Y
[R-5.6.5-001] of TS 22.179	Authorised to make a private call with manual commencement	Y	Y	Y	Y
[R-5.6.5-003] of TS 22.179 [R-6.7.3-007] of TS 22.280	List of user(s) who can be called in private call
	> MCPTT ID	Y	Y	Y	Y
	> User info ID	Y	N	Y	Y
	> ProSe discovery group ID	Y	N	Y	Y
TS 33.180	> KMSUri for security domain of MCPTT ID (see NOTE 4)	Y	Y	Y	Y
[R-6.7.4-004] of TS 22.280	> Presentation priority relative to other users and groups (see NOTE 2)	Y	Y	Y	Y
[R-5.6.5-003] of TS 22.179	Authorised to make a private call to users not included in "list of user(s) who can be called in private call"	Y	Y	Y	Y
[R-5.6.5-002] of TS 22.179	Authorised to make a private call with automatic commencement	Y	Y	Y	Y
[R-5.6.3-011], [R-6.7.4-010] of TS 22.179	Authorisation of user to force automatic answer for a private call	Y	Y	Y	Y
[R-5.6.5-006], [R-6.7.5-002] of TS 22.179	Authorised to restrict the provision of a notification of call failure reason for private call	Y	Y	Y	Y
[R-5.13-001] of TS 22.280	Authorisation to protect confidentiality and integrity of media in a private call (see NOTE 1)	Y	Y	Y	Y
[R-5.13-001] of TS 22.280	Authorisation to protect confidentiality and integrity of floor control signalling in a private call (see NOTE 1)	Y	Y	Y	Y
[R-5.6.2.2.1-001] of TS 22.280	Authorisation to make an MCPTT emergency group call functionality enabled for user	Y	Y	Y	Y
[R-5.6.2.4.1-001] of TS 22.280	Group used on initiation of an MCPTT emergency group call (see NOTE 7)	Y	Y	Y	Y
[R-5.6.2.4.1-001] of TS 22.280	Recipient for an emergency private MCPTT call (see NOTE 7)
	> MCPTT ID	Y	Y	Y	Y
TS 33.180	> KMSUri for security domain of MCPTT ID (see NOTE 4)	Y	Y	Y	Y
[R-5.6.2.2.2-005] of TS 22.280	Authorisation to cancel an in progress emergency associated with a group	Y	Y	Y	Y
[R-5.6.2.2.3-001] of TS 22.280	Authorised to make an Imminent Peril group call	Y	Y	Y	Y
[R-5.6.2.2.3-009] of TS 22.280	Group used on initiation of an MCPTT imminent peril group call (see NOTE 8)	Y	Y	Y	Y
[R-5.6.2.2.2-002] of TS 22.280	Authorised for imminent in- peril cancelation	Y	Y	Y	Y
[R-5.6.2.3.1-001] of TS 22.179	Authorised to make an emergency private call	Y	Y	Y	Y
[R-5.6.2.3.2-001] of TS 22.179	Authorised to cancel emergency priority in a private emergency call by an authorized user	Y	Y	Y	Y
[R-5.6.2.4.1-002] of TS 22.280	Authorised to activate emergency alert	Y	Y	Y	Y
[R-5.6.2.4.1-013] of TS 22.280	Automatically trigger a MCPTT emergency communication after initiating the MCPTT emergency alert	Y	Y	Y	Y
[R-5.6.2.4.2-002] of TS 22.280	Authorisation to cancel an MCPTT emergency alert	Y	Y	Y	Y
[R-6.15.6.2-002] of TS 22.280	Authorised to activate an MCPTT ad hoc group emergency alert	Y	Y	Y	Y
[R-6.15.6.2-006] of TS 22.280	Authorisation to cancel an MCPTT ad hoc group emergency alert	Y	Y	Y	Y
	Authorised to receive the participants information of an MCPTT ad hoc group emergency alert	Y	Y	Y	Y
[R-6.15.6.2-007] of TS 22.280	Authorised to set up a group call using the ad hoc group used for the alert	Y	Y	Y	Y
[R-5.1.7-002] and [R-6.8.7.2-007] and [R-6.8.7.2-008] of TS 22.280	Priority of the user (see NOTE 9)		Y	Y	Y
[R-5.1.7-002] and [R-5.2.2-003] and [R-6.6.3-002] of TS 22.280	Authorisation to create a group-broadcast group (see NOTE 11)			Y	Y
[R-5.2.2-003] and [R-6.6.3-002] of TS 22.280	Authorisation to create a user-broadcast group (see NOTE 11)			Y	Y
[R-5.3-003], [R-6.12-001], [R-7.2-005] of TS 22.280	Authorisation to provide location information to other MCPTT users on a call when talking		Y	Y	Y
TS 23.283	Authorised to use LMR E2EE for interworking	Y	Y	Y	Y
TS 23.283	> List of supported LMR technology types
TS 23.283	>> LMR technology type (P25, TETRA etc.)	Y	N	Y	Y
TS 23.283	>> URI of LMR key management functional entity (see NOTE 6)	Y	N	Y	Y
TS 23.283	>> LMR specific identity (RSI for P25 or ITSI for TETRA) (see NOTE 5)	Y	N	Y	Y
TS 23.283	>>LMR specific security information (see NOTE 5)	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
Subclause 10.9 of TS 23.280	Authorised to request location information of another user in the primary MCPTT system (see NOTE 10)	Y	Y	Y	Y
Subclause 10.9 of TS 23.280	List of partner MCPTT systems for which user is authorised to request location information for another user
	> Identity of partner MCPTT system	Y	Y	Y	Y
NOTE 1: Security mechanisms are specified in TS 33.180. NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. NOTE 3: As specified in TS 23.280, for each MCPTT user's set of MCPTT user profiles, only one MCPTT user profile shall be indicated as being the pre-selected MCPTT user profile. NOTE 4: 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 TS 23.280. NOTE 5: This is an LMR specific parameter with no meaning within MC services. NOTE 6: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. NOTE 7: 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 MCPTT user's currently selected group will be used. NOTE 8: This group, if configured, will be used for imminent peril communication. If not configured the MCPTT user's currently selected group will be used. NOTE 9: The use of the parameter is left to implementation. NOTE 10: Further differentiation on authorisation for requesting location information based on detailed characteristics (e.g. MC organization, MC service ID, functional alias) is left to implementation. NOTE 11: This parameter applies to temporary broadcast groups built from regrouping mechanism. This authorisation automatically sets the originator of the temporary group as the only transmitting party.

Table A.3-2: MCPTT user profile data (on network)

Reference	Parameter description	MCPTT UE	MCPTT Server	Configuration management server	MCPTT user database
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. NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. 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 of TS 23.280. NOTE 4: Access information for each partner MCPTT system comprises the list of information required for initial UE configuration to access an MCPTT system, as defined in Table A.6-1 of TS 23.280. NOTE 5: The criteria may consist of conditions such as the MCPTT user location or the active functional alias of the MCPTT user. NOTE 6: The criteria may consist of conditions such MCPTT user location or time. NOTE 7: Defines the right to perform a call transfer. For call transfer the MCPTT server does not check if the initial originating MCPTT user has the right to make a private MCPTT call to the final destination MCPTT user. NOTE 8: This parameter only applies to MCPTT users which are in the same security domain. NOTE 9: Defines the right to perform a call forwarding based on manual user input. For call forwarding based on manual user input the MCPTT server does not check if the initial originating MCPTT user has the right to make a private MCPTT call to the final destination MCPTT user. NOTE 10: Either the Target MCPTT ID or the Target functional alias may be present (but not both). NOTE 11: 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.

Table A.3-3: MCPTT user profile data (off network)

Reference	Parameter description	MCPTT UE	MCPTT Server	Configuration management server	MCPTT user database
[R-7.2-003], [R-7.6-004] of TS 22.280	List of off-network MCPTT groups for use by an MCPTT user	Y	N	Y	Y
	> MCPTT Group ID	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
TS 33.180	> KMSUri for security domain of group (see NOTE 3)	Y	N	Y	Y
	> Presentation priority of the group relative to other groups and users (see NOTE 2)	Y	N	Y	Y
[R-7.3.3-008] of TS 22.179	Allowed listening of both overriding and overridden	Y	N	Y	Y
[R-7.3.3-006] of TS 22.179	Allowed transmission for override (overriding and/or overridden)	Y	N	Y	Y
[R-7.8.1-001] of TS 22.280	Authorization for participant to change an off-network group call in-progress to off-network emergency group call	Y	N	Y	Y
[R-7.8.3.1-003] of TS 22.280	Authorization for participant to change an off-network group call in-progress to off-network imminent peril group call	Y	N	Y	Y
[R-7.12-002], [R-7.12-003] of TS 22.280	Authorization for off-network services	Y	N	Y	Y
Subclauses 10.6.3, 10.7.3	User info id (as specified in TS 23.303)	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. NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. 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 of TS 23.280.