Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  19.1.0

Top   Top   Up   Prev   Next

 

A (Normative)  MCPTT related configuration datap. 263

A.1  Generalp. 263

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

A.2  MCPTT UE configuration datap. 264

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.
Reference Definition
[R-5.4.2-002] of TS 22.280Maximum number of simultaneous group calls (Nc4)
[R-5.4.2-003] of TS 22.280Maximum number of transmissions (Nc5) in a group
[R-5.5.2-007] of TS 22.280Maximum number of private calls (N10)
 
Reference Definition
Subclause 5.2.3 of TS 23.280Relay service (Y/N)
Subclause 5.2.3 of TS 23.280List 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.
Up

A.3  MCPTT user profile configuration datap. 264

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.
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) YYYY
TS 33.180 KMSUri for security domain of MCPTT ID (see NOTE 4) YYYY
Subclause 5.2.4 of TS 23.280 Pre-selected MCPTT user profile indication (see NOTE 3) YYYY
Subclause 5.2.4 of TS 23.280 MCPTT user profile index YYYY
Subclause 5.2.4 of TS 23.280 MCPTT user profile name YYYY
[R-5.19-007],
[R-6.13.4-002] of TS 22.280
User profile status (enabled/disabled) YYY
[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. YY
[R-5.8-002],
[R-6.9-003] of TS 22.280
Alphanumeric aliases of user YYYY
[R-5.10-001] of TS 22.280 Participant type of the user YYYY
[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) YYYY
[R-5.4.2-003] of TS 22.280 Maximum number of simultaneously received group calls (Nc5) YYY
[R-5.6.5-004] of TS 22.179 Authorised to make a private call YYYY
[R-5.6.5-001] of TS 22.179 Authorised to make a private call with manual commencement YYYY

[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 YYYY
> User info ID YNYY
> ProSe discovery group ID YNYY
TS 33.180 > KMSUri for security domain of MCPTT ID (see NOTE 4) YYYY
[R-6.7.4-004] of TS 22.280 > Presentation priority relative to other users and groups (see NOTE 2) YYYY
[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" YYYY
[R-5.6.5-002] of TS 22.179 Authorised to make a private call with automatic commencement YYYY
[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 YYYY
[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 YYYY
[R-5.13-001] of TS 22.280 Authorisation to protect confidentiality and integrity of media in a private call (see NOTE 1) YYYY
[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) YYYY
[R-5.6.2.2.1-001] of TS 22.280 Authorisation to make an MCPTT emergency group call functionality enabled for user YYYY
[R-5.6.2.4.1-001] of TS 22.280 Group used on initiation of an MCPTT emergency group call (see NOTE 7) YYYY
[R-5.6.2.4.1-001] of TS 22.280 Recipient for an emergency private MCPTT call (see NOTE 7)
> MCPTT ID YYYY
TS 33.180 > KMSUri for security domain of MCPTT ID (see NOTE 4) YYYY
[R-5.6.2.2.2-005] of TS 22.280 Authorisation to cancel an in progress emergency associated with a group YYYY
[R-5.6.2.2.3-001] of TS 22.280 Authorised to make an Imminent Peril group call YYYY
[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) YYYY
[R-5.6.2.2.2-002] of TS 22.280 Authorised for imminent in- peril cancelation YYYY
[R-5.6.2.3.1-001] of TS 22.179 Authorised to make an emergency private call YYYY
[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 YYYY
[R-5.6.2.4.1-002] of TS 22.280 Authorised to activate emergency alert YYYY
[R-5.6.2.4.1-013] of TS 22.280 Automatically trigger a MCPTT emergency communication after initiating the MCPTT emergency alert YYYY
[R-5.6.2.4.2-002] of TS 22.280 Authorisation to cancel an MCPTT emergency alert YYYY
[R-6.15.6.2-002] of TS 22.280 Authorised to activate an MCPTT ad hoc group emergency alert YYYY
[R-6.15.6.2-006] of TS 22.280 Authorisation to cancel an MCPTT ad hoc group emergency alert YYYY
Authorised to receive the participants information of an MCPTT ad hoc group emergency alert NYYY
[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 YYYY
Authorised to modify the list of participants and criteria for an MCPTT ad hoc group emergency alert YYYY
[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) YYY
[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) YY
[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) YY
[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 YYY
TS 23.283 Authorised to use LMR E2EE for interworking YYYY
TS 23.283 > List of supported LMR technology types
TS 23.283 >> LMR technology type (P25, TETRA etc.) YNYY
TS 23.283 >> URI of LMR key management functional entity (see NOTE 6) YNYY
TS 23.283 >> LMR specific identity (RSI for P25 or ITSI for TETRA) (see NOTE 5) YNYY
TS 23.283 >>LMR specific security information (see NOTE 5) YNYY
[R-6.12-003] of TS 22.280 Authorised to restrict the dissemination of the location information YYYY
Subclause 10.9 of TS 23.280 Authorised to request location information of another user in the primary MCPTT system (see NOTE 10) YYYY
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 YYYY
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.
 
Reference Parameter description MCPTT UE MCPTT Server Configuration management server MCPTT user database
[R-5.1.5-001],
[R-5.1.5-002],
[R-5.10-001],
[R-6.4.7-002],
[R-6.8.1-008] of TS 22.280
List of on-network MCPTT groups for use by an MCPTT user
> MCPTT Group IDYYYY
> Application plane server identity information of group management server where group is defined
>> Server URIYNYY
> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)
>> Server URIYNYY
TS 33.180> KMSUri for security domain of group (see NOTE 3)YYYY
> Presentation priority of the group relative to other groups and users (see NOTE 2)YYYY
[R-6.2.3.7.2-006] of TS 22.179> Authorisation of an MCPTT user to change the maximum number of simultaneous talkersYYYY
Subclause 5.2.5 of TS 23.280List of groups user implicitly affiliates to after MCPTT service authorization for the user
> MCPTT Group IDsYYYY
[R-6.4.2-006] of TS 22.280Authorisation of an MCPTT user to request a list of which groups an MCPTT user has affiliated toYYY
[R-6.4.6.1-002],
[R-6.4.6.1-003] of TS 22.280
Authorisation to change affiliated groups of other specified user(s)YYY
[R-6.4.6.2-001],
[R-6.4.6.2-002] of TS 22.280
Authorisation to recommend to specified user(s) to affiliate to specific group(s)YYY
[R-6.6.1-004] of TS 22.280Authorisation to perform regroupingYYYY
[R-6.7.2-001] of TS 22.280Presence status is available/not available to other usersYYYY
[R-6.7.1-002],
[R-6.7.2-002] of TS 22.280
List of MCPTT users that an MCPTT user is authorised to obtain presence of
> MCPTT IDsYYYY
[R-6.7.2-003] of TS 22.280User is able/ unable to participate in private callsYYYY
[R-6.7.1-004],
[R-6.7.2-003],
[R-6.7.2-004] of TS 22.280
Authorisation to query whether MCPTT User is available for private callsYYY
[R-6.7.1-010] of TS 22.179Authorisation to override transmission in a private callYYYY
[R-6.7.1-013] of TS 22.179Authorisation to restrict provision of private call set-up failure cause to the callerYYY
[R-6.7.6-001] of TS 22.179Authorized to make a private call-back requestYYYY
[R-6.7.6-004] of TS 22.179Authorized to cancel a private call-back requestYYYY
[R-6.8.7.4.2-001],
[R-6.8.7.4.2-002] of TS 22.280
Authorisation of an MCPTT user to cancel an emergency alert on any MCPTT UE of any MCPTT userYYY
[R-6.13.4-001] of TS 22.280Authorisation for a MCPTT user to enable/disable an MCPTT userYYY
[R-6.13.4-003],
[R-6.13.4-005],
[R-6.13.4-006],
[R-6.13.4-007] of TS 22.280
Authorisation for an MCPTT user to (permanently / temporarily) enable/disable a UEYYY
[R-6.2.3.4-001] of TS 22.179Authorisation to revoke permission to transmitYYY
[R-7.14-002],
[R-7.14-003] of TS 22.280
Authorization for manual switch to off-network while in on-networkYYYY
[R-5.1.5-004] of TS 22.280Limitation of number of affiliations per user (N2)NYYY
[R-5.5.2-009] of TS 22.179Maximum number of simultaneous transmissions received in one group call for override (N7)YYY
[R-6.4.6.1-001],
[R-6.4.6.1-004] of TS 22.280
List of MCPTT users whose selected groups are authorized to be remotely changed
> MCPTT IDsYYYY
Subclause 10.15.3Authorization to make a first-to-answer callYYYY
[R-6.15.2.2.2-001] of TS 22.280 Authorization to make a remotely initiated ambient listening private callYYYY
[R-6.15.2.2.3-001] of TS 22.280Authorization to make a locally initiated ambient listening private callYYYY
[R-6.15.3.2-001] of TS 22.280Authorization to make a remotely initiated private callYYYY
[R-6.15.3.2-003] of TS 22.280Authorization to make a remotely initiated group callYYYY
[R-5.9a-013] of TS 22.280Authorised to request association between active functional alias(es) and MCPTT ID(s)YYY
[R-5.9a-012] of TS 22.280Authorised to take over a functional alias from another MCPTT userYYY
List of functional alias(es) of the MCPTT user
[R-5.9a-005] of TS 22.280> Functional aliasYYYY
[R-5.4.2-007a] of TS 22.280 >> Maximum number of parallel emergency group callsYYY
[R-5.9a-018] of TS 22.280>> Criteria for automatic activation by the MCPTT server (see NOTE 6)NYYY
[R-5.9a-017],
[R-5.9a-018] of TS 22.280
>> Criteria for automatic de-activation by the MCPTT server (see NOTE 6)NYYY
[R-5.9a-019] of TS 22.280>> Location criteria for activationYYY
[R-5.9a-019] of TS 22.280>> Location criteria for de-activationYYY
>> Manual de-activation is not allowed if the location criteria are metYYY
[R-5.9a-020] of TS 22.280List of functional aliases to which first-to-answer calls and private calls are allowed when using a certain functional alias
> Used functional aliasYYYY
>> List of functional aliases which can be called
>>> Functional aliasYYYY
[R-5.9a-021] of TS 22.280List of functional aliases from which first-to-answer calls and private calls can be received when using a certain functional alias
> Used functional aliasNYYY
>> List of functional aliases from which calls can be received
>>> Functional aliasNYYY
[R-6.7.3-007a] of TS 22.280List of user(s) from which private calls can be received
> MCPTT IDYYYY
TS 33.180> KMSUri for security domain of MCPTT IDYYYY
[R-6.7.4-004] of TS 22.280> Presentation priority relative to other users and groupsYYYY
Authorised to receive private calls from any other MCPTT ID (see NOTE 8)YYYY
Subclause 5.2.9 of TS 23.280List of partner MCPTT systems in which this profile is valid for use during migration
Subclause 5.2.9 of TS 23.280> Identity of partner MCPTT systemYYYY
Subclause 10.1.1 of TS 23.280> Access information for partner MCPTT system (see NOTE 4)YYY
Subclause 10.6.2.9Authorized to initiate or cancel group regrouping using a preconfigured regroup groupYYYY
[R-6.6.4.2-002a] and [R-6.6.4.2-002b] of TS 22.280List of groups the client affiliates/de-affiliates when one or multiple criteria are met
> MCPTT Group IDYYYY
>> Criteria for affiliation (see NOTE 5)YYYY
>> Criteria for de-affiliation (see NOTE 5)YYYY
>> Manual de-affiliation is not allowed if the criteria for affiliation are metYYYY
[R-6.6.4.2-002] of TS 22.280List of groups the client affiliates after receiving an emergency alert
> MCPTT Group IDYYYY
>> Manual de-affiliation is not allowed if the criteria for affiliation are metYYYY
[R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
Allow private call forwardingYYY
[R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
Call Forwarding NoAnswer TimeoutYYY
[R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
Call forwarding turned onYYY
R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
Target of the MCPTT private call forwarding
R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
> Target MCPTT ID (see NOTE 10)YYY
R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
> Target functional alias (see NOTE 10)YYY
R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
ConditionYYY
[R-5.6.3-014],
[R-6.7.4-015] of TS 22.179
Allow private call transfer (see NOTE 7)YYYY
[R-5.6.3-014],
[R-6.7.4-015] of TS 22.179
List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer
[R-5.6.3-014],
[R-6.7.4-015] of TS 22.179
> MCPTT IDYYY
[R-5.6.3-014],
[R-6.7.4-015] of TS 22.179
List of functional aliases that the MCPTT user is authorised to use as targets for call transfer
[R-5.6.3-014],
[R-6.7.4-015] of TS 22.179
> Functional aliasYYY
[R-5.6.3-014],
[R-6.7.4-015] of TS 22.179
Authorised to transfer private calls to any MCPTT userYYYY
[R-5.6.3-015],
[R-6.7.4-016] of TS 22.179
Authorised to forward private calls based on manual input to any MCPTT user (see NOTE 9)YYYY
[R-5.10-001b] of TS 22.280Maximum number of successful simultaneous MCPTT service authorizations for this user (see NOTE 11)NYYY
ad hoc group call authorizations
[R-6.15.5.3-001] of TS 22.280> Authorised to initiate ad hoc group callYYYY
R-6.15.5.3-003] of TS 22.280> Authorised to participate in ad hoc group callYYYY
> Authorised to initiate emergency ad hoc group callYYYY
> Authorised to initiate imminent peril ad hoc group callYYYY
> Authorised to receive the participants information of an ad hoc group callNYYY
> Authorised to modify the list of participants and criteria for an ad hoc group callYYYY
> Authorised to release ongoing ad hoc group callsYYYY
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.
 
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 YNYY
> MCPTT Group ID YNYY
> Application plane server identity information of group management server where group is defined
>> Server URI YNYY
> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)
>> Server URI YNYY
TS 33.180 > KMSUri for security domain of group (see NOTE 3) YNYY
> Presentation priority of the group relative to other groups and users (see NOTE 2) YNYY
[R-7.3.3-008] of TS 22.179 Allowed listening of both overriding and overridden YNYY
[R-7.3.3-006] of TS 22.179 Allowed transmission for override (overriding and/or overridden) YNYY
[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 YNYY
[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 YNYY
[R-7.12-002],
[R-7.12-003] of TS 22.280
Authorization for off-network services YNYY
Subclauses 10.6.3, 10.7.3 User info id (as specified in TS 23.303) YNYY
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.
Up

Up   Top   ToC