hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.7.3.2 Procedure
|
The procedure in figure 7.17.7.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone file distribution to multiple MCData users, with or without download completed report request from the MCData user. Pre-conditions: 1. The security aspects of sharing the user information between primary and partner MCData systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MCData system share their users' information to the primary MCData system. 2. MCData users on MCData clients 1 to M belong to the primary MCData system and MCData users on MCData clients 1 to N belong to the partner MCData system and are already registered for receiving MCData service. 3. The MCData server of the primary MCData system is where the authorized MCData user/dispatcher creates the ad hoc group. 4. Number of ad hoc group members receiving the file data is within the configured limit. 5. The file to be distributed is uploaded to the media storage function on the MCData content server using the procedures defined in subclause 7.5.2.2. The ad hoc group identity and preconfigured group identity of preconfigured group from which the configurations to be used (e.g. security related information) are determined using the procedures defined in subclause 7.17.6.2.1. 6. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client and other MCData users of ad hoc group have also received the relevant security related information. Figure 7.17.7.3.2-1: Ad hoc group standalone file distribution involving multiple MCData system 1. The user at MCData client 1 of the primary MCData system wants initiate ad hoc standalone file distribution to ad hoc group members from primary and partner MCData systems. 2-6. Same steps as described in the steps 2 to 6 of subclause 7.17.7.2.2. 7a-7b. The MCData server of the primary MCData system initiates an Ad hoc group standalone FD request towards each of the target MCData users in the primary MCData system and the partner MCData system. While sending the Ad hoc group standalone FD requests, the MCData server of the primary MCData system shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list). The request should contain the ad hoc group ID, pre-configured group if end-to-end encryption is required and time to live value for the ad hoc group. The primary MCData server removes the ad hoc group information from the dynamic data once the time to live value is expired and thus the ad hoc group ceases to exist then the procedure stops. 8a-8b. The receiving MCData clients 2 to M and MCData clients 1 to N notify the user about the incoming Ad hoc group standalone FD request (including file metadata, if present) which may be either accepted or rejected or ignored. 9a-9b. If the target MCData user on MCData clients 2 to M and MCData clients 1 to N provides a response (accept or reject) to the notification, then respective MCData clients send the Ad hoc group standalone FD response to the MCData server. The MCData clients 2 to M and MCData clients 1 to N automatically sends accepted Ad hoc group standalone FD response when the incoming request included mandatory download indication. 10a-10b. The MCData server forwards the Ad hoc group standalone FD response to the MCData client 1. 11a-11d. The receiving MCData clients 2 to M and MCData clients 1 to N download the file followed by providing download completed reports for reporting file download completed using the procedure as described in the step 9 to step 12 of subclause 7.5.2.6. Annex A (normative): MCData related configuration data A.1 General This Annex provides information about the static data needed for configuration for the MCData service, which belongs to one of the following categories: - MCData UE configuration data (see subclause A.2); - MCData user profile configuration data (see subclause A.3); - MCData related group configuration data (see subclause A.4); and - MCData service configuration data (see subclause 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 MCData UE, MCData group, MCData user and MCData service configuration data refers to the information that will be stored against each MCData UE, MCData group, MCData user and MCData 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 3GPP TS 22.282 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced 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 MCData UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. A.2 MCData UE configuration data The general aspects of UE configuration are specified in 3GPP TS 23.280 [5]. Data in tables A.2-1 and A.2-2 have to be known by the MCData UE after MCData authorization. Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCData service. Table A.2-1: UE configuration data (on and off network) Reference Parameter description Short data service [R-5.4.2-002] of 3GPP TS 22.280 [2] > Maximum number of simultaneous SDS transactions (Nc4) [R-5.4.2-004] of 3GPP TS 22.280 [2] > Requested presentation priority of SDS messages received (see NOTE) File distribution [R-5.4.2-002] of 3GPP TS 22.280 [2] > Maximum number of simultaneous file distribution transactions (Nc4) Transmission control [R-5.4.2-002] of 3GPP TS 22.280 [2] > Maximum number of simultaneous data transmissions (Nc4) [R-5.4.2-003] of 3GPP TS 22.280 [2] > Maximum number of data transmissions (Nc5) in a group Reception control [R-5.4.2-002] of 3GPP TS 22.280 [2] > Maximum number of simultaneous data receptions (Nc4) [R-5.4.2-003] of 3GPP TS 22.280 [2] > Maximum number of data receptions (Nc5) in a group NOTE: Priority of SDS messages includes enhanced status updates, since enhanced status updates utilise the SDS mechanism. Table A.2-2: UE configuration data (on network) Reference Parameter description Subclause 5.2.3 of 3GPP TS 23.280 [6] Relay service (Y/N) Subclause 5.2.3 of 3GPP TS 23.280 [6] List of allowed relayed MCData groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) > MCData group ID > Relay service code (as specified in 3GPP TS 23.303 [7]) NOTE: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. A.3 MCData user profile configuration data The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [5]. The MCData user profile configuration data is stored in the MCData user database. The MCData server obtains the MCData user profile configuration data from the MCData user database (MCData-2). Tables A.3-1 and A.3-2 contain the MCData user profile configuration required to support the use of on-network MCData service. Tables A.3-1 and A.3-3 contain the MCData user profile configuration required to support the use of off-network MCData service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. Table A.3-1: MCData user profile configuration data (on and off network) Reference Parameter description MCData UE MCData Server Configuration management server MCData user database 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] and [R6.6.3-002] of 3GPP TS 22.280 [2] Authorisation to create a group-broadcast group (see NOTE 7) Y Y [R-5.2.2-003] and [R6.6.3-002] of 3GPP TS 22.280 [2] Authorisation to create a user-broadcast group (see NOTE 7) 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.15.6.2-002] of 3GPP TS 22.280 [2] Authorised to activate an MCData ad hoc group emergency alert Y Y Y Y [R-6.15.6.2-006] of 3GPP TS 22.280 [2] Authorisation to cancel an MCData ad hoc group emergency alert Y Y Y Y [R-6.15.6.2-007] of 3GPP TS 22.280 [2] Authorised to set up an MCData group communication using the ad hoc group used for the alert Y Y Y Y Authorised to receive the participants information of an MCData ad hoc group emergency alert N Y Y Y Authorised to modify the list of participants and criteria for an MCData ad hoc group 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 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. NOTE 7: 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: MCData user profile configuration data (on network) Reference Parameter description MCData UE MCData Server Configuration management server MCData 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], [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 ad hoc group data communication authorizations [R-6.15.5.3-001] of 3GPP TS 22.280 [2] > Authorised to initiate ad hoc group data communication Y Y Y Y R-6.15.5.3-003] of 3GPP TS 22.280 [2] > Authorised to participate in ad hoc group data communication Y Y Y Y > Authorised to initiate emergency ad hoc group data communication Y Y Y Y > Authorised to initiate imminent peril ad hoc group data communication Y Y Y Y > Authorised to receive the participants information of an ad hoc group data communication N Y Y Y > Authorised to modify the list of participants and criteria for an ad hoc group data communication Y Y Y Y > Authorised to release ongoing ad hoc group data communications Y 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. Table A.3-3: MCData user profile configuration data (off network) Reference Parameter description MCData UE MCData Server Configuration management server MCData user database [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. A.4 MCData related Group configuration data The general aspects of group configuration are specified in 3GPP TS 23.280 [5]. Parameters specified in table A.4-1 are child parameters of the "MCData configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-2 are child parameters of the "MCData configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-3 are child parameters of the "MCData configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [5]. Table A.4-1: Group configuration data (on and off network) Reference Parameter description MCData UE MCData Server Group management server [R-5.12-001] of 3GPP TS 22.280 [2] >> Media confidentiality and integrity protection (see NOTE) Y Y Y [R-5.12-001] of 3GPP TS 22.280 [2] >> Transmission control confidentiality and integrity protection (see NOTE) Y Y Y [R-5.12-001] of 3GPP TS 22.280 [2] >> Group media protection security material (see NOTE) Y N Y Subclause 5 >> MCData sub-services and features enabled for the group >>> Short data service enabled Y Y Y >>> File distribution enabled Y Y Y >>> IP connectivity enabled Y Y Y >>> Conversation management enabled Y Y Y >>> Transmission control enabled Y Y Y >>> Reception control enabled Y Y Y >>> Enhanced status enabled Y Y Y >> Enhanced status [R-6.1.3.2-002] of 3GPP TS 22.282 [3] >>> List of operational status values Y N Y [R-6.1.1.2-011] of 3GPP TS 22.282 [2] >> Lossless communication Y Y Y [R-6.1.1.2-007] of 3GPP TS 22.282 [5] >> Conversation hang time Y Y Y NOTE: Security mechanisms are specified in 3GPP TS 33.180 [13]. Table A.4-2: Group configuration data (on network) Reference Parameter description MCData UE MCData Server Group management server [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [2] >> Authorisation of a user to request a list of affiliated members of a group Y Y Y [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006], [R-6.8.7.2-003] of 3GPP TS 22.280 [2] >> Priority of the group N Y Y Subclause 6.2.2 of 3GPP TS 22.282 [3] >> Transmission and reception control >>> Maximum data size for SDS Y Y Y >>> Maximum data size for FD Y Y Y >>> Maximum data size for auto-receive N Y Y 3GPP TS 23.283 [18] >> Indication whether use of LMR E2EE is permitted on the MCData group Y N Y 3GPP TS 23.283 [18] >> LMR specific identity for MCData group (see NOTE 1) Y N Y 3GPP TS 23.283 [18] >> Group to key binding (see NOTE 1) Y N Y [R-6.2.2.1-001] of 3GPP TS 22.282 [3], [R-5.2.1-001] of 3GPP TS22.280 [2] >> List of group members which are allowed to transmit data (see NOTE 2) >>> MCData ID Y Y Y NOTE 1: This is an LMR specific parameter with no meaning within MC services. NOTE 2: This parameter sets the authorization to transmit data in pre-arranged groups used in broadcast calls. Table A.4-3: Group configuration data (off network) Reference Parameter description MCData UE MCData Server Group management server Subclause 10.10 of 3GPP TS 23.280 [5] >> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values >>> MCData group call signalling Y N Y >>> MCData group call media Y N Y A.5 MCData service configuration data The general aspects of MC service configuration are specified in 3GPP TS 23.280 [5]. The MCData service configuration data is stored in the MCData server. Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCData service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCData service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point. Table A.5-1: MCData service configuration data (on and off network) Reference Parameter description MCData UE MCData Server Configuration management server Table A.5-2: MCData service configuration data (on network) Reference Parameter description MCData UE MCData Server Configuration management server Subclause 6.2.2 of 3GPP TS 22.282 [3] Transmission and reception control > Maximum data size for SDS Y Y Y > Maximum payload data size for SDS over signalling control plane (see NOTE 1) Y Y Y > Maximum data size for FD Y Y Y [R-6.2.2.1-002d], [R-6.2.2.4-003] of 3GPP TS 22.282 [3] > Time limit for the temporarily stored data waiting to be delivered to a receiving user N Y Y [R-6.2.2.3-001] of 3GPP TS 22.282 [3] > Timer for periodic announcement with the list of available recently invited data group communications N Y Y > Maximum data size for auto-receive N Y Y List of functional alias identities [R-5.9a-005] of 3GPP TS 22.280 [17] > Functional alias N Y Y [R-5.9a-005] of 3GPP TS 22.280 [17] >> Limit number of simultaneous activations N Y Y [R-5.9a-005] of 3GPP TS 22.280 [17] >> This functional alias can be taken over N Y Y >> List of users who can activate this functional alias [R-5.9a-005] of 3GPP TS 22.280 [17] >>> MCData ID N Y Y [R-5.9a-016] of 3GPP TS 22.280 [17] >> Communication priority (see NOTE 2) N Y Y [R-5.10-001a] of 3GPP TS 22.280 [2] Maximum number of successful simultaneous service authorizations of clients from a user N Y Y MCData notification server > Server URI(s) Y Y Y Ad hoc group data communication configurations [R-6.15.5.3-005] of 3GPP TS 22.280 [2] > Support of ad hoc group data communication (enabled/disabled) (see NOTE 3) Y Y Y [R-6.15.5.3-002] of 3GPP TS 22.280 [2] > Maximum number of participants allowed to participate in an ad hoc group data communication Y Y Y [R-6.15.5.3-004] of 3GPP TS 22.280 [2] > Hang timer for ad hoc group data communication N Y Y > Maximum duration for ad hoc group data communication Y Y Y > List of preferred media codecs for ad hoc group data communication Y Y Y NOTE 1: The maximum payload data size for SDS over signalling control plane shall be less than or equal to the maximum data size for SDS. NOTE 2: The usage of this parameter by the MCData server is up to implementation. NOTE 3: If the support for ad hoc group data communication is disabled by the MC system then all other configurations related to ad hoc group data communication are not applicable Table A.5-3: MCData service configuration data (off network) Reference Parameter description MCData UE MCData Server Configuration management server Subclause 10.10 of 3GPP TS 23.280 [5] Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values > MCData one-to-one call signalling Y N Y > MCData one-to-one call media Y N Y Annex B (informative): Transmission control for MCData B.1 Overview of transmission control process The MCData server may receive several simultaneous requests for data transmission, which may be associated with different types of communication e.g. group, private, 1-to-many. For each communication, how the requests are processed may be different. The requests that are not authorized shall be rejected by the transmission control function. For message requests over the signalling control plane, the processing should be immediate and is delivered to the recipients either via unicast or broadcast. However, for message requests over the media plane, transmission control arbitration (see Annex B.2) will be necessary. Subsequent to transmission control arbitration, and subject to the policy e.g. store and forward, the data is either delivered directly to the recipient MCData user or stored in the network repository and a corresponding URL is delivered. The end-to-end transmission control process is illustrated in figure B.1-1. Figure B.1-1: Transmission control process B.2 Transmission control arbitration The transmission control arbitration is a central function of the transmission control process and is implementation specific. In a typical deployment, multiple or simultaneous requests can be received at the transmission control arbitration function. Each of these requests may be categorized into different request types with different queuing priorities, and therefore each request type will be maintained with separate queues. Each request shall not be present in more than one queue at any given time. The queue types and the order of queues may be configured by the MCData administrator, as described below. - Transmission control queue: It is the primary queue from which the request is processed for transmission e.g. emergency communication requests may result in this queue and processed at the highest priority. - Communication type queue: This queue may be sorted in the order of the communication type associated with the request. For example, the group communication requests may always take precedence over one-to-many or private communication requests. - Static attribute queue: This queue may be formed based on the static attributes associated with the request e.g. group priority, user priority, which may be pre-configured by the MCData administrator. - Dynamic attribute queue: This queue may be formed based on the dynamic attributes associated with the request e.g. location of the sending user, content size, etc. Annex C: Void Annex D (informative): Example of a User Message Storage Area The figure in subclause 7.13.1 illustrates the high-level structure of the MCData message store where objects are stored in a flat structure in the user storage area. This flat data structure provides maximum flexibility for UI implementation to present stored objects to the user. However, a folder hierarchy structure provides a better visual presentation of the stored objects to the MCData user. Figure D-1: User message storage area example In figure D-1 the MCData user 1 message storage area in the MCData message store is constructed in folder hierarchical way. A system default folder, Inbox, is configured to receive all new objects coming from active communications. The MCData user 1 creates Group 1, Group 2 and Group N folders to store communication history for different group communications that he is a member of. Once the Group 1 folder is created the MCData user 1 can then move all the objects related to Group 1 communication from the Inbox to the Group 1 folder. The MCData user 1 can also create child folders in Group 1 folder to further divide the stored objects into different groupings such as with different subjects, Subject 1 and Subject 2. Similarly, the MCData user 1 creates child folders, Date 1 and Date 2, in Group N folder to store communication history in group N occurred in different dates. With this hierarchical folder structure, the MCData user 1 can browse his user account in the MCData message store interactively and navigate to the information he would like to see. For example, the MCData user 1 can start with the top-level root folder and traverse down the folder hierarchy to reach to Date 2 folder and see the communication history of group N in that particular date. Annex E (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-07 Initial version. 0.0.0 2016-08 Update following SA6#12 incorporating the following pCRs: S6-160810; S6-160875; S6-160876 0.1.0 2016-10 Update following SA6#13 incorporating the following pCRs: S6-161169; S6-161170; S6-161243; S6-161265; S6-161085; S6-161173; S6-161174; S6-161245; S6-161176; S6-161248; S6-161177; S6-161178; S6-161266; S6-161267; S6-161184 0.2.0 2016-11 Update following SA6#14 incorporating the following pCRs: S6-161316; S6-161586; S6-161609; S6-161587; S6-161589; S6-161506; S6-161576; S6-161507; S6-161326; S6-161508; S6-161577; S6-161511; S6-161512; S6-161616; S6-161514; S6-161515; S6-161516; S6-161580; S6-161581; S6-161519; S6-161498; S6-161642 0.3.0 2016-11 SA#74 SP-160878 Submitted for Approval at SA#74 1.0.0 2016-12 SA#74 SP-160878 MCC Editorial update for publication after TSG SA approval (SA#74) 14.0.0 2017-03 SA#75 SP-170071 0002 2 F Alignment of definitions 14.1.0 2017-03 SA#75 SP-170071 0003 2 F Alignment of group affiliation and de-affiliation requirements 14.1.0 2017-03 SA#75 SP-170071 0004 1 F Alignment of bearer management 14.1.0 2017-03 SA#75 SP-170071 0005 2 D Adding descriptive text for the FD procedure section 14.1.0 2017-03 SA#75 SP-170071 0006 2 D Resolving editor's notes for the short data service feature 14.1.0 2017-03 SA#75 SP-170071 0007 1 D Adding references for the signalling control plane 14.1.0 2017-03 SA#75 SP-170071 0008 2 D Adding descriptive text for the transmission and reception control section 14.1.0 2017-03 SA#75 SP-170071 0009 F MCData correction of reference 14.1.0 2017-03 SA#75 SP-170071 0010 F Alignment of business relationships, identities, and application of functional model to deployments 14.1.0 2017-03 SA#75 SP-170071 0011 3 F file download editorials 14.1.0 2017-03 SA#75 SP-170071 0013 1 F Off-network conversation management 14.1.0 2017-03 SA#75 SP-170071 0014 1 D Editorial corrections 14.1.0 2017-03 SA#75 SP-170071 0015 1 F Resolving EN in Scope 14.1.0 2017-03 SA#75 SP-170071 0016 5 F Resolving EN in Functional model 14.1.0 2017-03 SA#75 SP-170071 0017 1 F Resolving EN in SDS procedures 14.1.0 2017-03 SA#75 SP-170071 0018 F Referring generic procedures from CFA 14.1.0 2017-03 SA#75 SP-170071 0020 2 F Conversation management definitions 14.1.0 2017-03 SA#75 SP-170071 0021 2 F Disposition alignments and corrections in SDS and FD 14.1.0 2017-03 SA#75 SP-170071 0022 1 F Tx and Rx control procedure corrections 14.1.0 2017-03 SA#75 SP-170071 0025 1 F MCData functional model alignment 14.1.0 2017-03 SA#75 SP-170071 0027 1 F Moving configuration data to on-network only 14.1.0 2017-03 SA#75 SP-170071 0028 3 F Resolve SDS on-network information flows EN 14.1.0 2017-03 SA#75 SP-170071 0030 1 F Resolve FD information flows EN 14.1.0 2017-03 SA#75 SP-170071 0031 2 F Adding end-to-end encryption requirements 14.1.0 2017-03 SA#75 SP-170071 0032 1 F Resolve transmission control information flows EN 14.1.0 2017-03 SA#75 SP-170071 0033 2 F Resolve conversation management EN 14.1.0 2017-03 SA#75 SP-170071 0034 1 F Addition of definition for MCData ID 14.1.0 2017-03 SA#75 SP-170071 0035 F Addition of definition for MCData ID 14.1.0 2017-03 SA#75 SP-170071 0036 3 F Off-network information flows for SDS 14.1.0 2017-03 SA#75 SP-170071 0037 1 F Resolve communication release information flows EN 14.1.0 2017-03 SA#75 SP-170071 0038 1 F Conditions for using SDS media plane 14.1.0 2017-06 SA#76 SP-170392 0039 2 F Correction on MCData reference points when using MBMS 14.2.0 2017-06 SA#76 SP-170392 0048 D Additions to Definition and Abbreviations 14.2.0 2017-06 SA#76 SP-170392 0049 2 F Clarifications to section 5 Arcitecture requirements 14.2.0 2017-06 SA#76 SP-170392 0051 1 F Clarifications to section 6.5.1 that SDS Distribution function in MCData server talks to SDS function in MCData client not UE 14.2.0 2017-06 SA#76 SP-170392 0052 F Clarifications to section 6.5.3.1.2 14.2.0 2017-06 SA#76 SP-170392 0054 1 D Correct wrong reference in section 7.2 14.2.0 2017-06 SA#76 SP-170392 0056 3 F Correct the MCData data disposition notification IEs 14.2.0 2017-06 SA#76 SP-170392 0058 1 D Consistent use of pre-condition in section 7.4.2.2.2 14.2.0 2017-06 SA#76 SP-170392 0059 1 F Inconsistent use of MCData group ID or list of recipients in request 14.2.0 2017-06 SA#76 SP-170392 0061 3 F Content reference URL should be a mandatory IE when uploading a file 14.2.0 2017-06 SA#76 SP-170392 0062 5 F Addition of new configuration and miscellaneous corrections 14.2.0 2017-06 SA#76 SP-170392 0063 5 F Addition of identity management server address per group 14.2.0 2017-06 SA#76 SP-170392 0064 F Correction on sending data with mandatory download 14.2.0 2017-06 SA#76 SP-170392 0070 2 F Inclusion of KMSUri to allow multiple security domains 14.2.0 2017-06 SA#76 SP-170392 0071 4 F Clarification to Auto-send 14.2.0 2017-06 SA#76 SP-170392 0076 F Corrections to Group configuration data for all MC services 14.2.0 2017-06 SA#76 SP-170392 0078 2 F CR to 23.282 on Auto-receive 14.2.0 2017-06 SA#76 SP-170394 0040 4 B Information flow of File Distribution for off-network 15.0.0 2017-06 SA#76 SP-170394 0041 1 B Functional model of File Distribution for off-network 15.0.0 2017-06 SA#76 SP-170394 0075 1 C Functional model of File Distribution for off-network 15.0.0 2017-09 SA#76 SP-170682 0079 2 B Introduction of SDS application type identifiers 15.1.0 2017-09 SA#76 SP-170685 0080 1 B Addition of IWF and IWF-2 15.1.0 2017-09 SA#76 SP-170681 0083 1 A File size check for FD 15.1.0 2017-09 SA#76 SP-170681 0085 1 A Correction to configuration for Auto-receive parameter 15.1.0 2018-01 SA#78 SP-170891 0087 1 F SDS location field: Alignment of Stage 2 with Stage 1 & Stage 3 15.2.0 2018-01 SA#78 SP-170891 0088 1 D Editorial changes to MCData stage 2 15.2.0 2018-01 SA#78 SP-170895 0089 1 F Adding application identifier in media plane SDSs 15.2.0 2018-01 SA#78 SP-170891 0090 1 F Off-network Conversation Management clarifications 15.2.0 2018-01 SA#78 SP-170889 0094 2 A PSI configuration for MCData service 15.2.0 2018-01 SA#78 SP-170891 0095 1 F Completion of Communication Release 15.2.0 2018-01 SA#78 SP-170894 0096 1 F MBMS packet recovery 15.2.0 2018-04 SA#79 SP-180148 0099 1 A Correction of security specification references 15.3.0 2018-04 SA#79 SP-180155 0100 3 B LMR E2EE user profile and group parameters 15.3.0 2018-04 SA#79 SP-180148 0102 2 A Payload size limit for standalone SDS over signalling control plane 15.3.0 2018-04 SA#79 SP-180151 0103 1 F Update of references to stage 1 specifications 15.3.0 2018-04 SA#79 SP-180148 0107 1 A Duplicated procedure name for MCData Group SDS 15.3.0 2018-06 SA#80 SP-180367 0109 A Clarification for presentation priority in MCData UE configuration 15.4.0 2018-06 SA#80 SP-180370 0110 3 A Modify MCData download data response 15.4.0 2018-09 SA#81 SP-180677 0111 2 C Media storage function in the MCData server 16.0.0 2018-09 SA#81 SP-180677 0113 3 C Adding the Network base Message Store 16.0.0 2018-12 SA#82 SP-181178 0116 1 F Corrections on CR implementation errors 16.1.0 2018-12 SA#82 SP-181178 0117 1 F Configuration parameters to support requirement [R-6.1.1.2-009] are incorrect 16.1.0 2018-12 SA#82 SP-181178 0118 2 F Corrections to Table A.2-1, Table A.4-2 and Table A.5-2 16.1.0 2018-12 SA#82 SP-181178 0119 4 F Corrections to "Release of MCData communication using HTTP" procedures 16.1.0 2018-12 SA#82 SP-181178 0120 1 F Alignment with the MCData content server 16.1.0 2018-12 SA#82 SP-181178 0121 1 F There is no file download when using media plane for FD 16.1.0 2018-12 SA#82 SP-181178 0122 2 B Procedures for MCData message store operations 16.1.0 2018-12 SA#82 SP-181178 0123 1 F Correct misalignment on MCData user usage 16.1.0 2019-03 SA#83 SP-190074 0124 - F Correct the location of MCData content server and MCData message store configuration parameters in table A.3-2 configuration table 16.2.0 2019-03 SA#83 SP-190074 0125 - D Editorial correction on the term of MCData 16.2.0 2019-03 SA#83 SP-190074 0126 2 B Additional architecture requirement for MCData message store 16.2.0 2019-03 SA#83 SP-190074 0127 2 B Generic SDS procedure with MCData message store 16.2.0 2019-03 SA#83 SP-190074 0128 3 B Providing data for a user entering an ongoing MCData group conversation 16.2.0 2019-03 SA#83 SP-190075 0130 1 B MCData user profile migration information 16.2.0 2019-03 SA#83 SP-190074 0131 2 F Message store object and metadata 16.2.0 2019-03 SA#83 SP-190075 0132 1 B Introduction of gateway MC server for interconnection 16.2.0 2019-03 SA#83 SP-190074 0133 2 B Example of user storage area with folder hierarchy structure 16.2.0 2019-03 SA#83 SP-190074 0134 2 C Making data sync between MCData message store and message store client bi-directional 16.2.0 2019-03 SA#83 SP-190074 0135 1 B Add more operations to the MCData message store 16.2.0 2019-03 SA#83 SP-190074 0136 1 B Off-network SDS with MCData message store 16.2.0 2019-06 SA#84 SP-190488 0137 1 B Restricting incoming private communications 16.3.0 2019-06 SA#84 SP-190486 0138 2 B Interconnection for file distribution 16.3.0 2019-06 SA#84 SP-190486 0139 1 B Interconnection and migration with message store 16.3.0 2019-06 SA#84 SP-190488 0140 2 B User configuration for functional alias information query for MCData 16.3.0 2019-06 SA#84 SP-190488 0141 1 B User requested priority in 23.281 16.3.0 2019-06 SA#84 SP-190488 0142 3 B Criteria based automatic group affiliation and deaffiliation 16.3.0 2019-06 SA#84 SP-190488 0143 2 B MCData configuration for functional alias 16.3.0 2019-06 SA#84 SP-190488 0144 4 B Functional alias support configuration items 16.3.0 2019-06 SA#84 SP-190488 0145 3 B Functional alias supplements for the MCData transmission and reception control procedures 16.3.0 2019-06 SA#84 SP-190488 0147 2 B Functional alias support for Short Data Service (SDS) 16.3.0 2019-06 SA#84 SP-190488 0148 3 B MC Data User IP connectivity service capability– part 1 Functional Architecture 16.3.0 2019-06 SA#84 SP-190488 0149 1 C MCData transport capabilties for IP connectivity service 16.3.0 2019-06 SA#84 SP-190485 0150 6 B MCData File Distribution using the MBMS download delivery method 16.3.0 2019-06 SA#84 SP-190485 0151 - C Remove the procedure in 7.5.2.9 File removal using HTTP by MCData server 16.3.0 2019-06 SA#84 SP-190485 0152 2 F Remove the duplicated MCData server URI in UE configuration table 16.3.0 2019-06 SA#84 SP-190485 0153 3 F Add lossless communication to network group configuration and fix missing configuration parameter 16.3.0 2019-06 SA#84 SP-190485 0154 2 F Resolution proposals for some Editor's Notes 16.3.0 2019-06 SA#84 SP-190488 0155 B MCData client performs automatic activation and deactivation of functional aliases based on location 16.3.0 2019-06 SA#84 SP-190488 0156 B MCData server limits the number of simultaneous successful service authorisations 16.3.0 2019-06 SA#84 SP-190488 0157 3 B Functional alias support for MCData File Distribution 16.3.0 2019-06 SA#84 SP-190488 0159 3 B MC Data User IP connectivity service capability– part 2 IP connectivity for Point-to-Point and Group communication 16.3.0 2019-09 SA#85 SP-190729 0161 3 F Correct the configuration parameters for the MCData emergency alert procedures 16.4.0 2019-09 SA#85 SP-190729 0169 1 F Fix omission of location services in MCData 16.4.0 2019-09 SA#85 SP-190729 0170 2 B EPS bearer for emergency 16.4.0 2019-09 SA#85 SP-190729 0171 2 B Emergency support for one-to-one SDS 16.4.0 2019-09 SA#85 SP-190729 0172 2 B Emergency and imminent peril support for group SDS 16.4.0 2019-09 SA#85 SP-190729 0173 2 B Emergency support for off-network SDS 16.4.0 2019-09 SA#85 SP-190729 0174 2 C Addition of Location infomation to SDS and Enhance Status 16.4.0 2019-09 SA#85 SP-190732 0177 1 F Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation 16.4.0 2019-09 SA#85 SP-190732 0178 F Stage 1 requirement reference correction in the user profile data 16.4.0 2019-09 SA#85 SP-190729 0179 2 F Clarification and corrections to support transmission control 16.4.0 2019-09 SA#85 SP-190729 0180 2 F Corrections to the transmission and reception control procedures 16.4.0 2019-09 SA#85 SP-190729 0183 1 B One-to-one SDS Session upgrade to emergency session 16.4.0 2019-09 SA#85 SP-190729 0184 1 B Group SDS Session upgrade to emergency/imminent-peril session and cancel in-progress emergency/ imminent-peril group state 16.4.0 2019-09 SA#85 SP-190729 0185 2 B One-to-One Emergency MCData FD 16.4.0 2019-09 SA#85 SP-190729 0186 1 B Group emergency MCData FD 16.4.0 2019-09 SA#85 SP-190729 0187 1 B One-to-one FD Session upgrade to emergency session 16.4.0 2019-09 SA#85 SP-190729 0188 1 B Group FD communication upgrade to emergency/imminent-peril communication and cancel in-progress emergency/imminent-peril group state 16.4.0 2019-09 SA#85 SP-190735 0162 2 B Point-to-Point IP connectivitity using functional alias to address the target MCData user 17.0.0 2019-09 SA#85 SP-190735 0163 2 B SDS addressing based on functional alias 17.0.0 2019-09 SA#85 SP-190735 0164 4 B Remote initiation of Point-to-Point IP connectivity 17.0.0 2019-09 SA#85 SP-190735 0165 4 B Remote tear down of point-to-point IP connectivity 17.0.0 2019-09 SA#85 SP-190735 0166 1 B Communication priority for functional aliases 17.0.0 2019-09 SA#85 SP-190735 0181 3 B File distribution addressing based on functional alias 17.0.0 2019-09 SA#85 SP-190735 0182 2 B IP connectivity for group communication (unicast) 17.0.0 2019-09 SA#85 SP-190735 0189 3 B Capability to change remotely the priority of the point-to-point IP connectivity communication 17.0.0 2019-12 SA#86 SP-191113 0190 2 F Requested Priority in IP connectivity point to point communication 17.1.0 2019-12 SA#86 SP-191113 0191 1 B Enhancing SDS data requests with application priority capabilities in on-network mode 17.1.0 2019-12 SA#86 SP-191113 0193 2 B Priority of the user 17.1.0 2019-12 SA#86 SP-191108 0196 A File repair with the content storage function 17.1.0 2020-03 SA#87-E SP-200113 0197 2 A Correction of internal clause references for Enhanced Status transmission 17.2.0 2020-03 SA#87-E SP-200117 0199 2 C Corrections and enhancements to IP Connectivity 17.2.0 2020-03 SA#87-E SP-200113 0200 2 A Enhancements and clarifications for file repair and file delivery using MBMS 17.2.0 2020-03 SA#87-E SP-200113 0201 2 A Clarification on prepending the MCData content server URI 17.2.0 2020-03 SA#87-E SP-200113 0202 1 A Local policies at Partner MCData system is not applied 17.2.0 2020-03 SA#87-E SP-200117 0208 1 F Clarifications for MCData file distribution over MBMS 17.2.0 2020-04 - - - - - MCC editorial correction, adding missing line break in clause 6.6.2 17.2.1 2020-07 SA#88-E SP-200341 0212 1 B Add the network MCData notification Server 17.3.0 2020-07 SA#88-E SP-200341 0213 1 B Add new "search folder" and "retrieve folder content" operations 17.3.0 2020-07 SA#88-E SP-200341 0214 F Pre-emption of EPS bearers by a new MCData bearer 17.3.0 2020-07 SA#88-E SP-200341 0215 F Miscellaneous small corrections 17.3.0 2020-07 SA#88-E SP-200341 0216 1 F Corrections to the one-to-one SDS information elements 17.3.0 2020-07 SA#88-E SP-200341 0217 1 F Minor editorial corrections 17.3.0 2020-07 SA#88-E SP-200341 0218 F Corrections to the one-to-one SDS and FD communication upgrade flows 17.3.0 2020-07 SA#88-E SP-200341 0219 F Corrections to the MCData group standalone FD request information elements 17.3.0 2020-07 SA#88-E SP-200341 0220 F Corrections to the group SDS informational elements 17.3.0 2020-07 SA#88-E SP-200341 0221 F Corrections to the group FD upgrade and FD in-progress priority state cancel request 17.3.0 2020-07 SA#88-E SP-200341 0222 F MCData corrections in off-network SDS procedures 17.3.0 2020-09 SA#89-E SP-200843 0226 1 B Limit the number of simultaneous logins on per user basis 17.4.0 2020-09 SA#89-E SP-200839 0227 1 A Removal of content reference IE from the FD requests using media plane 17.4.0 2020-09 SA#89-E SP-200845 0228 1 F Functional alias handling for 1-1 FD requests 17.4.0 2020-09 SA#89-E SP-200845 0229 1 F Functional alias handling for one-one session SDS requests 17.4.0 2020-09 SA#89-E SP-200845 0230 1 F Functional alias handling for one-one standalone SDS requests 17.4.0 2020-09 SA#89-E SP-200845 0231 1 F Functional alias handling for IPCon 17.4.0 2020-09 SA#89-E SP-200845 0232 1 B Providing stored files in MCData content server for FD over MBMS 17.4.0 2020-09 SA#89-E SP-200845 0233 1 C Enhancement of MBMS user service usage procedures 17.4.0 2020-09 SA#89-E SP-200845 0234 1 C Enhancement of Group standalone FD using MBMS 17.4.0 2020-09 SA#89-E SP-200845 0236 1 F MCData emergency group communication clarifications 17.4.0 2020-09 SA#89-E SP-200845 0237 1 F MCData one-to-one emergency communication clarifications 17.4.0 2020-09 SA#89-E SP-200845 0238 1 F Clarifications on the use of ProSe in off-network MCData communications 17.4.0 2020-09 SA#89-E SP-200845 0239 1 F Apply transmission and reception control to all FD HTTP procedures consistently 17.4.0 2020-09 SA#89-E SP-200845 0240 F Functional alias handling for 1-1 FD requests using HTTP 17.4.0 2020-12 SA#90-E SP-200989 0242 1 A Align Annex B with changes to "auto-send" 17.5.0 2020-12 SA#90-E SP-200989 0243 2 A Correction to the transmission control configuration parameters 17.5.0 2020-12 SA#90-E SP-200996 0246 F Various corrections 17.5.0 2020-12 SA#90-E SP-200989 0248 A IP connectivity, SDS and FD functional model correction 17.5.0 2020-12 SA#90-E SP-200996 0249 B Application specific metadata container 17.5.0 2020-12 SA#90-E SP-200996 0250 1 F Removal of duplicate MCData disposition notification information flow 17.5.0 2020-12 SA#90-E SP-200996 0251 F Corrections to FD using procedures and editorials 17.5.0 2020-12 SA#90-E SP-200996 0252 1 B Depositing file contents distributed via FD communication using HTTP into MCData message store 17.5.0 2020-12 SA#90-E SP-200996 0253 1 B Distribution of file residing in MCData message store account of the MCData user 17.5.0 2021-04 SA#91-E SP-210178 0255 1 B Message Store control 17.6.0 2021-04 SA#91-E SP-210178 0256 1 F Corrections to FD using media plane 17.6.0 2021-04 SA#91-E SP-210178 0257 F Correction to Deposit an Object procedure 17.6.0 2021-04 SA#91-E SP-210178 0258 D Correct typos on information tables 17.6.0 2021-04 SA#91-E SP-210178 0259 1 F Correction and clarification on file upload using HTTP procedure 17.6.0 2021-04 SA#91-E SP-210178 0260 F Correction to message names in some procedures 17.6.0 2021-04 SA#91-E SP-210178 0261 1 F Add the IE of Emergency indicator in the message of MCData FD request 17.6.0 2021-04 SA#91-E SP-210178 0263 1 B Addition of MBMS delivery via MB2 interface for MCData 17.6.0 2021-04 SA#91-E SP-210178 0264 1 F Corrections to the file distribution using HTTP procedures 17.6.0 2021-04 SA#91-E SP-210178 0265 1 B MCData file upload using HTTP including request of network resources with required QoS 17.6.0 2021-06 SA#92-E SP-210487 0263 3 B Corrections and enhancements to the Notification procedures 17.7.0 2021-06 SA#92-E SP-210487 0269 2 F Aggregated notifications and reports 17.7.0 2021-06 SA#92-E SP-210487 0270 1 F Correct misuse of the term "transmission control" 17.7.0 2021-06 SA#92-E SP-210487 0271 1 B MCData file download including request of network resources with required QoS 17.7.0 2021-06 SA#92-E SP-210487 0272 1 C Enhancement and corrections to group file distribution using HTTP 17.7.0 2021-06 SA#92-E SP-210487 0273 1 C Enhancement and corrections to one-to-one file distribution using HTTP 17.7.0 2021-06 SA#92-E SP-210567 0274 1 F Correction to MCData-5 reference point description 17.7.0 2021-06 SA#92-E SP-210487 0275 1 F EN resolutions in clause 5 17.7.0 2021-06 SA#92-E SP-210487 0276 1 F EN resolutions in clause 6 17.7.0 2021-06 SA#92-E SP-210487 0277 1 F EN resolutions in clause 7 17.7.0 2021-06 SA#92-E SP-210487 0278 1 F EN resolution in B.1 17.7.0 2021-06 SA#92-E SP-210487 0279 2 F Proposal on Data Streaming service 17.7.0 2021-09 SA#93-E SP-210962 0281 F Various fixes for 23.282 17.8.0 2021-09 SA#93-E SP-210962 0282 F Notification URL correction 17.8.0 2021-09 SA#93-E SP-210962 0283 F Clarify the supports of stored and forward functionality 17.8.0 2021-09 SA#93-E SP-210962 0284 1 F Correction of preconditions and statements related to storing of MCData communication into Message store 17.8.0 2021-09 SA#93-E SP-210962 0285 1 F Clarifying the use of deposit file indication IE in MCData FD request using HTTP 17.8.0 2021-09 SA#93-E SP-210962 0286 1 F Clarifying the lossless communication 17.8.0 2021-12 SA#94-E SP-211523 0287 F Clarify MCData service delivery for offline users and delivery notification 17.9.0 2021-12 SA#94-E SP-211523 0288 1 F Missing information table for the notification message 17.9.0 2021-12 SA#94-E SP-211523 0289 2 F Disposition Type of specified MCData users 17.9.0 2021-12 SA#94-E SP-211523 0291 1 F Clarification on the use of MCData notification server(s) 17.9.0 2021-12 SA#94-E SP-211529 0290 1 B Connection authorisation configuration data 18.0.0 2022-06 SA#96 SP-220476 0294 F Corrections to the use of MC service system 18.1.0 2022-06 SA#96 SP-220477 0295 1 B Decoupling signalling and media for MCData service capabilities 18.1.0 2022-06 SA#96 SP-220476 0296 B Allow the user to restrict the dissemination of the location information – MCData Configuration 18.1.0 2022-09 SA#97-E SP-220924 0297 1 F MCData communication to a FA user 18.2.0 2022-09 SA#97-E SP-220924 0298 1 B Call connect and disconnect over MBMS for MCData 18.2.0 2023-03 SA#99 SP-230289 0300 2 B User profile configuration data to support MCData ad hoc group emergency alerts 18.3.0 2023-03 SA#99 SP-230287 0303 2 C MCData user profile configuration parameters for location information 18.3.0 2023-03 SA#99 SP-230289 0304 2 B Information flows and procedures for the ad hoc group data communication for SDS and FD services of MCData 18.3.0 2023-03 SA#99 SP-230289 0305 1 B Description for the terms used in the Ad hoc Group Communication procedures 18.3.0 2023-03 SA#99 SP-230289 0306 1 B Configuration parameters of Ad hoc group data communication for MCData 18.3.0 2023-06 SA#100 SP-230709 0307 1 B Adds user profile data for allowing subsequent MCData communications after an adhoc group emergency alert 18.4.0 2023-06 SA#100 SP-230709 0308 1 B Configuration for receiving the adhoc group emergency alert participants list notification (MCData) 18.4.0 2023-06 SA#100 SP-230709 0309 3 F Example of MCData services which are not handled by SIP core 18.4.0 2023-06 SA#100 SP-230709 0310 B Notifying authorized user about adhoc group participants list involving single MC systems - MCData 18.4.0 2023-06 SA#100 SP-230709 0311 2 B Information flows and procedures involving multiple systems for the ad hoc group data session in MCData 18.4.0 2023-06 SA#100 SP-230709 0312 2 F Corrections for ad hoc group data communication setup 18.4.0 2023-06 SA#100 SP-230709 0313 2 F Correct MCData ID usage in information flow table 18.4.0 2023-06 SA#100 SP-230709 0314 1 F MCData ad hoc group ID correction 18.4.0 2023-06 SA#100 SP-230709 0315 2 F Remove unnecessary information flow tables 18.4.0 2023-06 SA#100 SP-230709 0316 1 B Updates adhoc group call procedures for allowing a subsequent MCData communication after an adhoc group emergency alert 18.4.0 2023-09 SA#101 SP-230998 0319 1 F Adding references on group definitions (MCData) 18.5.0 2023-09 SA#101 SP-231004 0323 1 F Missing configuration for ad hoc group MCData communication 18.5.0 2023-09 SA#101 SP-231004 0324 1 F Missing pre-conditions and steps for ad hoc group MCData communication 18.5.0 2023-09 SA#101 SP-231002 0317 3 B Information flows and procedures to support ad hoc group standalone short data service using signalling control plane 19.0.0 2023-09 SA#101 SP-230999 0318 1 B Addition of location Information Element to FD message 19.0.0 2023-09 SA#101 SP-231002 0320 1 B Modify list of participants by changing the criteria during an ongoing MCData ad hoc group communication (single MC system) 19.0.0 2023-09 SA#101 SP-230999 0321 1 B Clarifications on temporary and pre-arranged MCData Broadcast Groups 19.0.0 2023-12 SA#102 SP-231556 0325 1 F Correction in procedure on changing the criteria during an ongoing MCData ad hoc group communication (single MC system) 19.1.0 2023-12 SA#102 SP-231556 0326 2 B Changing the criteria during an ongoing MCData ad hoc group data session (multiple MC systems) 19.1.0 2023-12 SA#102 SP-231558 0331 1 A Configuration for authorising modification of ad hoc group data communication participants - mcdata 19.1.0 2023-12 SA#102 SP-231556 0332 1 B Configuration for authorising modification of ad hoc group emergency alert participants - mcdata 19.1.0 2023-12 SA#102 SP-231556 0333 F Corrections to file availability request flow between Content and MCData server 19.1.0 2023-12 SA#102 SP-231556 0334 F Corrections to clause reference and updating the descriptive text box of ad hoc group procedure figures 19.1.0 2023-12 SA#102 SP-231558 0336 1 A Modification of ad hoc group data communication participants involving multiple MCData systems 19.1.0 2023-12 SA#102 SP-231558 0339 1 A Correction to modification of ad hoc group data communication participants procedure 19.1.0 2023-12 SA#102 SP-231556 0341 1 F Corrections on modifying the criteria during an ad hoc group data communication (MCData) 19.1.0 2023-12 SA#102 SP-231558 0343 1 B Adhoc group data communication release by an authorized user (MCData) 19.1.0 2024-03 SA#103 SP-240314 0342 2 B Change list of participants when criteria was used to setup the ad hoc group call (MCData) 19.2.0 2024-06 SA#104 SP-240768 0349 1 B Information flows and procedures to support ad hoc group standalone file distribution using HTTP procedures 19.3.0 2024-06 SA#104 SP-240758 0355 1 A Removal of GW MC service ID 19.3.0 2024-06 SA#104 SP-240757 0357 1 A Ambiguity on routing request message 19.3.0 2024-06 SA#104 SP-240757 0360 1 A IP address(es) of target data host(s) or server(s) 19.3.0 2024-09 SA#105 SP-241224 0361 1 B Include application data in MCData IPcon request and response 19.4.0 2024-09 SA#105 SP-241218 0363 1 A Clarification on Message store 19.4.0 2024-09 SA#105 SP-241224 0365 1 F Update the pre-conditions of clause 7.17.3.1.4 19.4.0 2024-09 SA#105 SP-241224 0366 1 B Migration during Ad hoc group call procedure 19.4.0 2024-12 SA#106 SP-241722 0367 1 B Target MCData user configuration for recording 19.5.0 2024-12 SA#106 SP-241723 0368 1 C Adding information elements to ad hoc group data session 19.5.0 2024-12 SA#106 SP-241722 0369 1 C Clarification for Location user profile for MCData 19.5.0 2024-12 SA#106 SP-241707 0371 A Corrections to the FD file removal procedures 19.5.0 2024-12 SA#106 SP-241723 0373 1 F Update the ad-hoc group call modify procedures 19.5.0 2024-12 SA#106 SP-241722 0374 1 F Corrections of MCPTT term used in MCData 19.5.0 2025-03 SA#107 SP-250211 0376 1 F Remove MCData recording from Rel-19 19.6.0 2025-03 SA#107 SP-250199 0378 1 A Adding the Off-network functional model 19.6.0
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
1 Scope
|
The objective of this technical specification is to specify interworking between MC systems and LMR systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [3], MCCoRe requirements in 3GPP TS 22.280 [2] and the MCData requirements (SDS only) in 3GPP TS 22.282 [4].
The present document refers to an InterWorking Function (IWF). The structure and functionality of the IWF is out of scope of the present document. The definition of reference points between the IWF and MC systems and the interactions between the IWF and MC systems are in scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[3] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[4] 3GPP TS 22.282: "Mission Critical Data services".
[5] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[6] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[7] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[8] 3GPP TS 33.180: "Security of the mission critical service"
[9] TIA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards".
[10] ETSI TS 103 389: "Rail Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol (SIP) on the Network Switching Subsystem (NSS) to Fixed Terminal Subsystem (FTS) interface for GSM Operation on Railways".
[11] ETSI TS 102 610: "Railways Telecommunications (RT); Global System for Mobile communications (GSM); Usage of the User-to-User Information Element for GSM Operation on Railways".
[12] ETSI TS 100 392-19-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 19: Interworking between TETRA and Broadband systems; Sub-part 1: Protocol specification for Interworking with 3GPP mission critical services"
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
3 Definitions, symbols and abbreviations
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
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].
End‑to‑End Encryption: encryption that is applied by an originating terminal or client and is decrypted only by chosen terminating terminals or clients.
User homed in the IWF: is an MC service ID that represents an LMR user in the MC system.
Interworking: a means of communication between mission critical systems and LMR systems whereby MC users obtaining service from a mission critical system can communicate with LMR users who are obtaining service from one or more LMR systems.
Interworking function: adapts LMR Systems to mission critical systems via the IWF interface and supports interworking between LMR systems and mission critical systems.
Interworking group: a group, which is composed of group members from the MC system and the LMR system and defined in the MC system or the LMR system.
LMR system: the collection of applications, services, and enabling capabilities providing a land mobile radio service offering group and private communications.
LMR user: a user of a device which allows participation in an LMR system.
NOTE: The term LMR user is defined for discussion purposes only and is out of scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
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].
E2EE End-to-End Encryption
IWF InterWorking Function
KEK Key Encryption Key (TETRA)
KMS Key Management Service
MC Mission Critical
MCPTT Mission Critical Push To Talk
LMR Land Mobile Radio
LMC Location Management Client
LMS Location Management Server
OTAK Over-The-Air-Key Management (TETRA)
OTAR Over-The-Air Rekeying (P25)
P25 Project 25
SDS Short Data Service
TETRA TErrestrial Trunked Radio
UE User Equipment
UKEK Unique Key Encryption Key (P25)
URI Uniform Resource Identifier
UUI User-to-User Information
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
4 Introduction
|
Mission critical users currently employ a wide range of LMR mission critical Push To Talk services, and associated data capabilities where available.
The present document describes the architecture to support the interworking between the MC system and the LMR system to satisfy interworking requirements specified in 3GPP TS 22.179 [3] and 3GPP TS 22.282 [4]. Other LMR technologies may interwork as long as they conform to the present document.
The IWF, along with its LMR system, will appear as a peer interconnected MC system. This is meant as an approach for defining interactions on the IWF interface but is not intended to specify the functionality of the IWF nor meant to mandate a deployment model.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
5 Assumptions and architectural requirements
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
5.1 Key management
|
Interworking requirements for key management for encrypted interworking include:
a) a mechanism to securely (i.e. authenticity, integrity, confidentiality) share an LMR E2EE traffic key for a private call sessions between a party in an MCPTT system and a party in the LMR system;
b) a mechanism to securely convey to group members, the LMR E2EE key or set of LMR E2EE keys associated with an MC service group or set of MC service groups, to be used for encryption of interworking group calls spanning the multiple systems;
c) a mechanism to securely share with temporary group members in MC systems, the LMR E2EE key(s) associated with a temporary MC service group to be used in interworking group calls spanning the multiple systems;
d) key management solutions shall not preclude the ability of an IWF to allow one or more individual Mission Critical Organizations from having sole control over and sole access to LMR E2EE traffic keys used for the entity's media traffic and users' key encryption keys (UKEKs or KEKs);
e) key management solutions shall support the ability of the IWF to decrypt/reencrypt the media traffic for zero or more groups; and,
f) for deployments where Mission Critical Organizations wish to use LMR E2EE mechanisms when interworking with LMR users:
i) a mechanism to securely provision an MC service client with the user's UKEK or KEK; and,
ii) a mechanism to convey LMR OTAR or OTAK message contents.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
5.2 Packet format
|
Each LMR technology defines its own packet format for voice media transmission. For interworking sessions, there might be cases where LMR formatted media is required to be transferred between the IWF and LMR aware MCPTT clients. An example of such a case is where E2EE is used and thus the IWF is not able to decrypt the media. In such cases, media that is sent over the IWF-1 interface needs to be routed within MCPTT systems to/from LMR aware MCPTT clients using methods described in 3GPP TS 23.379 [7].
Requirements for media transmission across the IWF-1 interface include:
a) media transmission to carry the LMR formatted media between the IWF and LMR aware MCPTT clients; and
b) the MCPTT system, along with the IWF, may choose to encrypt the LMR formatted media using 3GPP mechanisms.
NOTE: The contents of the LMR formatted media is out of scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
6 Involved business relationships
|
No business relationships have been identified.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
7 Functional model
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.1 General
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.2 Functional model description
|
Figure 7.2‑1 shows the functional model for the application plane for interworking between MC systems and LMR systems. Functional entities and interfaces depicted on the right-hand side of the IWF‑x interfaces are defined in 3GPP TS 23.280 [5], 3GPP TS 23.379 [7], and 3GPP TS 23.282 [6].
Figure 7.2-1: Functional model for application plane for interworking
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.3 Functional entities description
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.3.1 IWF
|
The IWF supports most of the functionality of peer MCPTT and MCData systems, with some differences, as specified in the present document. The IWF supports any necessary protocol translation and identity mapping between the MC systems and the IWF. The internal function of the IWF is out of scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.4 Reference points
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.4.1 Reference point IWF‑1 (between the IWF and the MCPTT server)
|
The IWF‑1 reference point, which exists between the IWF and the MCPTT server, provides peer to peer interconnection between an LMR system and the MCPTT system. IWF‑1 supports a subset of MCPTT‑3 as defined in 3GPP TS 23.379 [7], with some differences, as specified in the present document. The IWF‑1 interface is supported by the same signalling plane protocol(s) as defined for MCPTT‑3 except as specified in the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.4.2 Reference point IWF‑2 (between the IWF and the MCData server)
|
The IWF‑2 reference point, which exists between the IWF and the MCData server, provides SDS interconnection between an LMR system and the MCData system. IWF‑2 supports a subset of the functionality of MCData‑SDS‑1 and MCData‑SDS‑2, as defined in 3GPP TS 23.282 [6] with some differences, as specified in the present document. The IWF‑2 interface is supported by the same signalling plane protocol(s) as defined for MCData‑3 except as specified in the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.4.3 Reference point IWF‑3 (between the IWF and the group management server)
|
The IWF‑3 reference point, which exists between the IWF and the group management server, provides group management interconnection between an LMR system and the MC system. IWF‑3 is based upon CSC‑16, as defined in 3GPP TS 23.280 [5] with some differences, as specified in the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
7.4.4 Reference point IWF‑4 (between the IWF and the LMS)
|
The IWF‑4 reference point, which exists between the IWF and the LMS, provides location information exchange between an LMR system and the MC system. Support of the IWF-4 reference point is optional, since there is no guarantee that the interworked LMR system can support location information.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
8 Identities
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
8.1 Identity mapping
|
The IWF provides centralised support for interworking between an MCPTT or MCData system and an LMR system. In MCPTT systems, the identity of an LMR user is provided as an MCPTT ID, and the identity of an LMR group is provided as an MCPTT group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system. Similarly, in MCData systems, the identity of an LMR user is provided as an MCData ID, and the identity of an LMR group is provided as an MCData group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system.
Identities provided on IWF-x reference points are described in clause 8 of 3GPP TS 23.280 [5].
The IWF can perform the identity mapping between an MCPTT system or MCData system and an LMR system during exchange of signalling and media messages.
The assignment of a functional alias that belongs to the MC system to a user homed in the IWF enables the mapping to corresponding role-based addressing schemes applicable in the LMR system.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
9 Application of functional model to deployments
|
No applications of functional model to deployments have been identified.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10 Procedures and information flows
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1 Affiliation
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.1 Information flows for affiliation
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.1.1 General
|
The following subclauses define information flows for affiliation on the IWF-1 interface. Affiliation related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.1.2 IWF group affiliation request
|
Table 10.1.1.2-1 describes the information flow IWF group affiliation request between the IWF and an MC service server and between an MC service server and the IWF.
Table 10.1.1.2-1: IWF group affiliation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group affiliation request. (see NOTE)
MC service group ID list
M
A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system.
MC service type
M
The type(s) of service(s) for which the request is intended (e.g. MCData or MCPTT or both)
NOTE: The IWF is configured with an MC service ID for use when the IWF is affiliating itself to the group on behalf of the LMR system.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.1.3 IWF group affiliation response
|
Table 10.1.1.3-1 describes the information flow IWF group affiliation response between the IWF and an MC service server and between an MC service server and the IWF.
Table 10.1.1.3-1: IWF group affiliation response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator (LMR user or MC service user) who triggered the MC service group affiliation request.
MC service group ID list
M
A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system.
Affiliation status per MC service group ID
M
Indicates the affiliation result for every MC service group ID in the list.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.1.4 IWF group de-affiliation request
|
Table 10.1.1.4-1 describes the information flow IWF group de-affiliation request between the IWF and an MC service server and between an MC service server and the IWF.
Table 10.1.1.4-1: IWF group de-affiliation request
Information element
Status
Description
MC service ID
M
The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group de-affiliation request. (see NOTE)
MC service group ID list
M
A list of one or more MC service group IDs to which the originator intends to de-affiliate.
MC service type
M
The type(s) of service(s) for which the request is intended (e.g. MCData or MCPTT or both)
NOTE: The IWF is configured with an MC service ID for use when the IWF is de-affiliating from the group on behalf of the LMR system.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.1.5 IWF group de-affiliation response
|
Table 10.1.1.5-1 describes the information flow IWF group de-affiliation response between the IWF and an MC service server and between an MC service server and the IWF.
Table 10.1.1.5-1: IWF group de-affiliation response
Information element
Status
Description
MC service ID
M
The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group de-affiliation request.
MC service group ID list
M
A list of one or more MC service group IDs to which the originator intends to de-affiliate.
De-affiliation status per MC service group ID
M
Indicates the de-affiliation result for every MC service group ID in the list.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.2 Affiliation procedures
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.2.1 General
|
When an interworking group is defined in the MCPTT system, the LMR system (via the IWF) informs the MCPTT system of group affiliations in one of the following ways:
- Every group affiliation in the LMR system results in an affiliation sent to the MCPTT system, which contains the identity (with appropriate translation by the IWF) of the affiliating group member; or
- A group affiliation is sent on behalf of the group's LMR users (via the IWF) to the MCPTT system when the first group member affiliates to the designated group in the LMR system, and a group de-affiliation is sent on behalf of the group's LMR users (via the IWF) to the MCPTT system when the last group member de-affiliates, and no other group affiliation signalling is sent.
The first and second options may be used at the same time, such that some group members may explicitly affiliate while the IWF may affiliate on behalf of other group members.
In the second option, when the IWF is configured to affiliate on behalf of the group's LMR members then:
a) the group list in the MCPTT system contains the IWF's MCPTT ID. This ID is recognized (through configuration) as having the ability to affiliate on behalf of the group's LMR users associated with this IWF;
b) the IWF affiliates with its MCPTT ID to the group defined in the MCPTT system;
c) the MCPTT system recognizes the affiliation as being from an IWF on behalf of the group's LMR users;
d) when the IWF has affiliated to the group, the MCPTT system:
i) considers any LMR user associated with the IWF to be affiliated to the group on which the IWF has affiliated. The IWF's users need not be listed ahead of time in the group list for this group in the MCPTT system;
ii) allows requests such as call setup or floor request, from MCPTT IDs,with or without functional alias, representing LMR users associated with the IWF for actions on the group to which the IWF has affiliated;
iii) does not carry out an additional affiliation on behalf of LMR users when those users make call requests, and therefore does not send additional messages to those users (e.g. release messages to both the IWF affiliated identity and the LMR user identity performing the action), via the IWF, during call processing;
iv) recognizes which LMR users are associated with the IWF because their MCPTT IDs belong to the same system as the IWF; and,
v) uses special rules for the IWF for limits such as "Limitation of number of affiliations per user (N2)".
e) requests from LMR users to the MCPTT system are identified with their individual MCPTT IDs (as translated by the IWF):
i) a user in the LMR system can affiliate on its own (via the IWF) as long as the user is a group member (i.e. in the group list), even if the IWF has affiliated to the group.
f) the IWF may make requests on behalf of a group's LMR users using the IWF MCPTT ID like a normal group member including, for example, group join requests for groups using the chat model;
g) the IWF is not allowed to affiliate to a group that is not configured with the IWF's MCPTT ID in the group member list; and,
h) if the IWF has not affiliated to an MCPTT group, then call requests to this group from LMR users on the system associated with the IWF, can only be accepted if the LMR user's MCPTT ID is in the group list, and has already affiliated.
MC service group affiliation and de-affiliation can be achieved using explicit or implicit methods as defined in TS 23.280 [5]. When the MC service server uses implicit affiliation/de-affiliation for an interworking group defined in the LMR system, the MC service server informs the IWF of the affiliation/de-affiliation.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.2.2 Group affiliation to a group defined in the MC system
|
The LMR system may affiliate its group members to an interworking group defined in the MC system via the IWF.
For group regroup, the affiliated group members are automatically affiliated to the temporary group.
The signalling procedure of interworking group affiliation is described in figure 10.1.2.2-1.
Pre-conditions:
1. The group to be affiliated to is defined in the MC system.
2. The IWF is connected to and is authorized to interwork with the MC system.
3. The interworking group information is available at the IWF.
4. The mapping relationship of group and user identities between MC system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.2-1: Group affiliation to a group defined in the MC system
1. The IWF sends an IWF group affiliation request to the MC service server on behalf of the LMR system.
2a. The MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then the MC service server requests the group policy from the group management server.
2b. The MC service server receives the group policy from the group management server.
3. Based on the group policy, the MC service server checks if the MC service group(s) is not disabled and if the user identified by the MCPTT ID supplied by the IWF is authorised to affiliate to the requested MC service group(s).
4. Based on the group policy and user subscription, the MC service server affiliates the IWF to the group. If a separate affiliation for each LMR user is expected, the status of the affiliating user is stored by the MC service server as the status associated with an MC service ID provided by the IWF that corresponds to the identity of that LMR user. If a separate affiliation for each LMR user is not expected, an affiliation status for the group using the MC service ID provided by the IWF is stored.
5. The MCPTT server sends the group affiliation status update message to the group management server, the group management server stores and updates the group affiliation status.
6. The MC service server returns an IWF group affiliation response to the IWF.
NOTE 2: How the LMR user(s) affiliates to a group is outside the scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.2.3 Group de-affiliation from a group defined in the MC system
|
The signalling procedure of interworking group de-affiliation from a group defined in the MC system is described in figure 10.1.2.3-1.
The LMR system manages the individual de-affiliation requests from the LMR users. The LMR system can de-affiliate its group members from the interworking group via the IWF.
Pre-conditions:
1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
2. The affiliation procedure described in subclause 10.1.2.2 was previously performed.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.3-1: Group de-affiliation from group defined in the MC system
1. The IWF sends an IWF group de-affiliation request to the MC service server on behalf of the LMR system.
2. If a separate de-affiliation from each LMR user is expected and based on the group policy and user subscription, the MC service server may de-affiliate the LMR group member from the group. Further, the MC service server may store the affiliation status of the user(s) for the requested MC service group(s). If a separate de-affiliation from each LMR user is not expected, the de-affiliation signalling de-affiliates the IWF and therefore the entire LMR system from the group.
3. The MC service server sends the group de-affiliation status update message to the group management server, the group management server stores and updates the group affiliation status.
4. The MC service server returns an IWF group de-affiliation response to the IWF.
NOTE 2: How the LMR user(s) de-affiliate from a group is outside the scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.2.4 Group affiliation to group defined in the LMR system
|
The MC system may affiliate its group members to an interworking group defined in the LMR system via the IWF.
The signalling procedure of group affiliation via the IWF is described in figure 10.1.2.4‑1.
Pre-conditions:
1. The group to be affiliated to is defined in the LMR system.
2. The IWF is connected to and is authorized to work with the MC system.
3. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.4-1: Group affiliation to group defined in the LMR system
1. The MC service client sends a MC service group affiliation request, including the MC service group ID(s), to the MC service server.
2. The MC service server checks if the MC service group ID(s) is an interworking group defined in the LMR system.
3. The MC service server sends an IWF group affiliation request to the IWF.
NOTE 2: The IWF can forward the request to the LMR system that could check whether the MC service client is authorized to affiliate to this interworking group.
NOTE 3: The IWF can reject the affiliation if the MC service group ID is either unknown to the IWF or not mapped to an LMR group identity in the IWF configuration.
4. The IWF returns an IWF group affiliation response to the MC service server, informing the successful affiliation to the LMR group.
5. The MC service server stores the group affiliation status of the MC service client for the requested interworking group.
6. The MC service server sends an MC service group affiliation response to the MC service client.
NOTE 4: How the affiliation is conducted on the LMR system is outside the scope of the present document.
NOTE 5: If an MC service client is implicitly affiliated to an MC service group defined in the LMR system the MC service server only performs steps 3, 4, and 5.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.1.2.5 Group de-affiliation from a group defined in the LMR system
|
The signalling procedure of interworking group de-affiliation from a group defined in the LMR system is described in figure 10.1.2.5-1.
The MC system manages the individual de-affiliation requests from the MC service users. The MC system may de-affiliate its group members from the interworking group via the IWF.
Pre-conditions:
1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
2. The affiliation procedure described in subclause 10.1.2.4 was previously performed.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.5-1: Group de-affiliation from a group defined in the LMR system
1. The MC service client of the MC service user sends an MC service group de-affiliation request to the MC service server. The MC service client shall provide the initiating MC service ID and the MC service group ID(s) being de-affiliated from.
2. Based on the user subscription and stored group policy, the MC service server checks if the user of the MC service client is affiliated to the requested MC service group(s). The MC service server checks if the MC service group(s) is an interworking group.
3a. If the MC service group(s) is an interworking group, the MC service server sends an IWF group de-affiliation request to the IWF.
3b. The IWF returns an IWF group de-affiliation response to the MC service server.
4. If the user of the MC service client is authorized to de-affiliate from the requested MC service group(s), the MC service server removes the affiliation status of the user for the requested MC service group(s).
5. The MC service server returns an MC service group de-affiliation response to the MC service client.
NOTE 2: If an MC service client is implicitly de-affiliated from an MC service group defined in the LMR system the MC service server only performs steps 3a, 3b, and 4.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2 Group management
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1 Information flows for group management
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.1 General
|
The following subclauses define information flows for group management on the IWF-1 interface. Group management related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.2 IWF group regroup teardown notification
|
Table 10.2.1.2-1 describes the information flow IWF group regroup teardown notification between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.2-1: IWF group regroup teardown notification
Information element
Status
Description
MC service group ID
M
MC service group ID of the temporary group which is torn down
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.3 IWF group regroup teardown notification response
|
Table 10.2.1.3-1 describes the information flow IWF group regroup teardown notification response between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.3-1: IWF group regroup teardown notification response
Information element
Status
Description
MC service group ID
M
MC service group ID of the temporary group which was torn down
Result
M
Indicates success or failure of the notification
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.4 IWF group regroup request
|
Table 10.2.1.4-1 describes the information flow IWF group regroup request between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.4-1: IWF group regroup request
Information element
Status
Description
MC service group ID list
M
List of constituent MC service group IDs
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.5 IWF group regroup response
|
Table 10.2.1.5-1 describes the information flow IWF group regroup response between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.5-1: IWF group regroup response
Information element
Status
Description
MC service group ID
O (see NOTE)
MC service group ID of the temporary group
MC service group ID list
M
List of constituent MC service group IDs.
Result
M
Indicates whether the IWF group regroup was accepted or rejected.
NOTE: Shall be present if the Result information element indicates that the group regroup operation is successful. Otherwise MC service group ID shall not be present.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.6 IWF group regroup notification
|
Table 10.2.1.6-1 describes the information flow IWF group regroup notification between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.6-1: IWF group regroup notification
Information element
Status
Description
MC service group ID list
M
List of constituent MC service group IDs
MC service group ID
M
MC service group ID of the temporary group
Priority level
O
Required priority level for the temporary group
Security level (see NOTE)
O
Required security level for the temporary group
NOTE: Security level refers to the configuration of media and floor control protection parameters as listed in 3GPP TS 23.280 [5]
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.7 IWF group regroup notification response
|
Table 10.2.1.7-1 describes the information flow IWF group regroup notification response between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.7-1: IWF group regroup notification response
Information element
Status
Description
MC service group ID list
M
List of constituent MC service group IDs
MC service group ID
M
MC service group ID of the temporary group
Priority level
M
Required priority level for the temporary group
Security level
M
Required security level for the temporary group
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.8 IWF group information request
|
Table 10.2.1.8-1 describes the IWF group information request from the IWF to the group management server or from the group management server to the IWF.
Table 10.2.1.8-1: IWF group information request
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.9 IWF group information response
|
Table 10.2.1.9-1 describes the IWF group information response from the group management server to the IWF or the IWF to the group management server.
Table 10.2.1.9-1: IWF group information response
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
MC service group provisioning information
O (see NOTE 1)
The group information retrieved from the group management server or from the IWF in the case where the IWF is performing the provision.
Result
O (see NOTE 2)
Indicates reason for failure to provide MC service group configuration information
NOTE 1: Shall be present if the request can be fulfilled.
NOTE 2: Shall be present if the request cannot be fulfilled.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.10 IWF group information provision request
|
Table 10.2.1.10-1 describes the IWF group information provision request from the group management server to the IWF or the IWF to the group management server.
Table 10.2.1.10-1: IWF group information provision request
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
MCPTT group configuration information
M
The group information retrieved from the group management server or from the IWF in the case where the group is defined in the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.11 IWF group information provision response
|
Table 10.2.1.11-1 describes the IWF group information provision response from the IWF to the group management server or from the group management server to the IWF.
Table 10.2.1.11-1: IWF group information provision response
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
Result
M
Indicates success or failure of reception, modification and storage of MC service group configuration information
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.12 IWF group information subscribe request
|
Table 10.2.1.12-1 describes the information flow IWF group information subscribe request from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group.
Table 10.2.1.12-1: IWF group information subscribe request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC services requested
O
Service(s) for which group configuration is requested; one or more of MCPTT, MCData
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.13 IWF group information subscribe response
|
Table 10.2.1.13-1 describes the information flow IWF group information subscribe response from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group.
Table 10.2.1.13-1: IWF group information subscribe response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indicates success or failure of the subscribe request
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.14 IWF group information notify request
|
Table 10.2.1.14-1 describes the information flow IWF group information notify request from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group.
Table 10.2.1.14-1: IWF group information notify request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group information reference (see NOTE)
O
Reference to information stored relating to the MC service group
Group related key material (see NOTE)
O
Key material for use with the MC service group
NOTE: At least one of these information elements shall be present.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.1.15 IWF group information notify response
|
Table 10.2.1.15-1 describes the information flow IWF group information notify response from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group.
Table 10.2.1.15-1: IWF group information notify response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indicates success or failure of the notification request
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2 Group regrouping
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2.1 General
|
The procedures in 3GPP TS 23.280 [5] are followed, but with changes required for interworking. The IWF will behave on the interface as if it is a peer MC service server with a peer group management client and peer group management server.
Exceptions to the 3GPP TS 23.280 [5] procedures are detailed in the subclauses below.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2.2 MC system initiates the group regroup
|
The MC system can initiate a group regroup that includes groups defined at the IWF. The IWF is informed and may reject the regroup if conditions do not allow it to support the regroup. This is described in figure 10.2.2.2-1.
Pre-conditions:
1. The group management client has retrieved the group configurations of the groups to be regrouped.
2. At least one MC service group has been defined in the MC system.
3. At least one MC service group has been defined in the IWF.
Figure 10.2.2.2-1: Group regrouping to an IWF
1. The group management client of the MC service user (e.g. dispatcher) requests group regroup operation to the group management server (which is the group management server of one of the MC service groups to be regrouped). The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group.
2. The group management server checks whether group regroup operation is performed by an authorised MC service user, based on group policy. The group management server checks whether the group is a temporary group. If the group is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed.
3. The group management server forwards the IWF group regroup request to the IWF with the information about the IWF's groups.
4. The IWF provides an IWF group regroup response. Due to security aspects concerning sharing information among different MC systems, the IWF does not share the users' information of the groups under its management to the group management server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping)
5. The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, off-network information, and the MC service IDs of the groups being combined, the priority level of the temporary group, and the security level of the temporary group. If the authorised MC service user does not specify the security level and the priority level, the group management server shall set the lower security level and the higher priority of the constituent groups.
6. The group management server notifies the IWF about its group regroup operation.
NOTE: How the IWF uses the MC service group ID that identifies the temporary group is outside the scope of the present document.
7. The IWF acknowledges the group management server.
8. The group management server notifies the MC service server of the temporary group creation with the information of the constituent groups.
9. The MC service server acknowledges the notification from the group management server.
10. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of lower security level.
11. The group management server provides a group regroup response to the group management client of the authorised MC service user (e.g. dispatcher).
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2.3 IWF initiates the group regroup
|
The procedure in 3GPP TS 23.280 [5] is followed, except for steps 1 and 2. The IWF will behave on the interface as if it is a peer MC service server with a peer group management server. This is described in figure 10.2.2.3-1.
Pre-conditions:
1. At least one MC service group has been defined in the MC system.
2. At least one MC service group has been defined in the IWF.
Figure 10.2.2.3-1: Group regrouping from an IWF
1. The IWF sends an IWF group regroup request to the group management server.
2. The group management server checks whether the group can be included in a temporary group.
3. The group management server provides an IWF group regroup response.
NOTE: Due to security aspects concerning sharing information among different systems, the group management server does not share the users' information of the groups under its management to the IWF.
4. The IWF notifies the group management server regarding the temporary group creation with information of the constituent groups.
5. The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups.
6. The MC service server acknowledges the notification from the group management server. The MC service server may reject the IWF group regroup, e.g. if one of its constituent groups is already in a regroup.
7. The group management server acknowledges the notification from the IWF.
8. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of a lower security level.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2.4 Ownership of the group regroup
|
The group management server that performs the group regroup operation owns the temporary group created by the regroup, as implied in 3GPP TS 23.280 [5].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2.5 Simultaneous group regroup requests from each side of the IWF-1 interface
|
To prevent routing issues and complexity that could result from regrouping the same users from both sides of the interface, the following rules can be applied:
- If group regrouping signalling using temporary groups is used on the MC system, the IWF must prevent the regroup signalling from propagating to the LMR system if the LMR system does not support regrouping;
- the IWF must handle the translation between temporary group identities on the MC system and the original interworking group identities used on the LMR system; and
- the regrouping rules in subclause 10.2.4.4 of 3GPP TS 23.280 [5] also apply.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.2.6 Resolution of vocoder and encryption mode for the group regroup
|
If one of the LMR groups to be included in a group regroup requires the use of LMR E2EE the preferred voice codecs for an MCPTT temporary group should be LMR codecs. If any of the mission critical users to be included in this MCPTT temporary group do not support LMR E2EE or the preferred LMR codecs, voice calls using LMR E2EE will fail for those users.
NOTE 1: How the MC system determines that the temporary group needs to support LMR E2EE is outside the scope of the present document.
NOTE 2: How the MC system determines that the temporary group needs to support an LMR codec is outside the scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3 Group configuration for interworking
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.1 Overview
|
The procedures in the following subclauses describe the process for sharing group configuration from an MC system to an IWF where the IWF needs to make use of the MC service group and from an IWF to an MC system where the MC system's clients need to make use of the group. The procedures in this subclause are based upon subclause 10.2.7 in 3GPP TS 23.280 [5].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.2 MC system provides group configuration to the IWF
|
Figure 10.2.3.2-1 below illustrates the case where the MC system provides the group configuration to the IWF, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the IWF.
Pre-conditions:
1. The MC service group is defined in the MC system.
2. One or more LMR users are members of the group.
3. The MC system of the MC service group has been configured with addressing information for the group management function in the IWF.
4. The MC system of the MC service group is authorized to provide group configuration information to the IWF.
NOTE: The MC system of the MC service group could be configured with an address of the IWF which is a proxy address.
Figure 10.2.3.2-1: MC system provides group configuration to the IWF
1. The group management server in the MC system of the MC service group provides the configuration information related to the MC service group to the IWF.
2. The IWF responds to the group management server of the MC system of the MC service group that the configuration has been received and stored correctly.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.3 IWF requests group configuration from the MC system
|
Figure 10.2.3.3-1 below illustrates the case where the IWF requests the group configuration from the MC system, for example because a user on the IWF is a member of the group.
Pre-conditions:
1. The MC service group is defined in the MC system.
2. One or more LMR users are members of the group.
3. The IWF does not have the configuration for the MC service group stored.
Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system
1. The IWF requests the group configuration from the group management server in the primary MC system of the MC service group.
2. The group management server in the MC system of the MC service group provides the requested group configuration information.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.4 IWF provides group configuration to the MC system
|
Figure 10.2.3.4-1 below illustrates the case where the IWF provides the group configuration to the MC system, e.g. due to an action by an administrator or because some of the IWF's MC service group members are homed on the MC system.
Pre-conditions:
1. The group is defined in the IWF.
2. One or more MC service users are members of the group.
NOTE: The group management server within the MC system is responsible for providing group configuration information to group members for whom the MC system is their serving MC system.
Figure 10.2.3.4-1: MC system provides group configuration to the IWF
1. The IWF provides the configuration information related to the group to the group management server in the MC system.
2. The group management server in the MC system responds to the IWF that the configuration has been received and stored correctly.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.5 MC system requests group configuration from the IWF
|
Figure 10.2.3.5-1 below illustrates the case where the MC system requests the group configuration from the IWF, for example because an MC service user receiving service in the MC system has the group configured in the user profile.
Pre-conditions:
1. The MC service group is defined in the IWF.
2. One or more MC service users are members of the group.
3. The group management server in the MC system does not have the configuration for the MC service group stored.
4. The MC system has been configured with addressing information for the group management function in the IWF.
NOTE: The group management server within the MC system is responsible for providing group configuration information to MC service group members for whom the MC system is their serving MC system.
Figure 10.2.3.5-1: Partner MC system requests group configuration from primary MC system
1. The MC system requests the group configuration from the group management function in the IWF.
2. The IWF provides the requested group configuration information.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.6 IWF subscribes to group configuration
|
The procedure for subscription from IWF for group configuration information to the group management server in the primary MC system of the MC service group is shown in figure 10.2.3.6-1.
Pre-conditions:
1. The MC service group is defined in its MC system.
2. One or more group members are defined in the LMR system.
3. The IWF has received group information from the GMS in the primary MC system of the MC service group.
Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration
1. The IWF subscribes to the group configuration information stored in the group management server in the primary MC system of the MC service group.
2. The group management server in the primary MC system of the MC service group sends an IWF group information subscribe response to IWF indicating success or failure of the request.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.7 MC system notifies group configuration
|
The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the IWF is shown in figure 10.2.3.7-1.
Pre-conditions:
1. The IWF has subscribed to the group configuration information for the MC service group in the group management server in the primary MC system of the MC service group.
2. The group management server in the primary MC system of the MC service group has received and stored new group configuration information for the MC service group.
Figure 10.2.3.7-1: Notification of group configuration information to the IWF
1. The group management server in the primary MC system of the MC service group sends an IWF group information notify request to the IWF.
2. The IWF sends an IWF group information notify response to the group management server in the primary MC system of the MC service group indicating the success or failure of the notification.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.8 MC system subscribes to group configuration
|
The procedure for subscription by the group management server in the MC system to the IWF for group configuration information is shown in figure 10.2.3.8-1.
Pre-conditions:
1. The group is defined in the LMR system.
2. One or more group members are defined in the MC system.
3. The group management server in the MC system has received group information from the IWF.
Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration
1. The group management server of the MC system subscribes to the group configuration information stored in the IWF.
2. The IWF provides an IWF group information subscribe response to group management server of the MC system indicating success or failure of the request.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.2.3.9 IWF notifies group configuration
|
The procedure for notification of group information from the IWF to the group management server in the MC system is shown in figure 10.2.3.9-1.
Pre-conditions:
1. The group management server of the MC system has subscribed to the group configuration information for the group in the IWF.
2. The IWF has new information for the group.
Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group
1. The IWF sends an IWF group information notify request to the group management server in the MC system.
2. The group management server in the MC system sends an IWF notify group information notify response to the IWF indicating the success or failure of the notification.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3 Group call
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.1 General
|
The following subclauses define information flows and signaling procedures for group calls and broadcast group calls.
Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF group call request / IWF group call release request message is sent to the IWF at the commencement / release of a group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document.
Where the group is defined in the LMR system, the IWF shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2 Information flows for group call over interworking group
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.1 General
|
The following subclauses define information flows for group calls on the IWF-1 interface. Group call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.2 IWF group call request
|
Table 10.3.2.2-1 describes the information flow IWF group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.2-1: IWF group call request information elements
Information Element
Status
Description
MCPTT ID
(see NOTE 1)
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID of the interworking group on which the call is initiated
SDP offer
M
Media parameters of MCPTT server
Implicit floor request
(see NOTE 2)
O
Indicates that the originator requests the floor.
Broadcast indicator
O
Indicates that the group call request is for a broadcast group call
Location
O
Location of the calling party
NOTE 1: If the LMR system does not provide the calling party identity when the group call is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for LMR user at the IWF.
NOTE 2: This element shall be included only when the originating client requests the floor.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.3 IWF group call response (IWF – MCPTT server)
|
Table 10.3.2.3-1 describes the information flow IWF group call response from the MCPTT server to the IWF and from the IWF to MCPTT server.
Table 10.3.2.3-1: IWF group call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is requested
SDP answer
M
Media parameters selected
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.4 IWF Group-broadcast group call setup request
|
Table 10.3.2.4-1 describes the information flow IWF group-broadcast group call setup request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.4-1: IWF Group-broadcast group call setup request information elements
Information Element
Status
Description
MCPTT ID
(see NOTE 1)
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID of the group on which the call is requested
SDP offer
M
Media parameters of MCPTT clients
Implicit floor request
(see NOTE 2)
O
Indicates that the originating client requests the floor
Location
O
Location of the calling party
NOTE 1: If the LMR system does not provide the calling party identity when the group-broadcast group call setup request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF.
NOTE 2: This element shall be included only when the originating client requests the floor.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.5 IWF Group-broadcast group call setup response
|
Table 10.3.2.5-1 describes the information flow IWF group-broadcast group call setup response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.5-1: IWF Group-broadcast group call setup response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT group ID
M
The MCPTT group ID of the group on which the call is requested
SDP answer
M
Media parameters selected
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.6 IWF Group-broadcast group call release request
|
Table 10.3.2.6-1 describes the information flow IWF group-broadcast group call release request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.6-1: IWF Group-broadcast group call release request information elements
Information Element
Status
Description
MCPTT ID
M (see NOTE)
The MCPTT ID of the MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released
NOTE: If the LMR system does not provide the calling party identity when the group-broadcast group call release request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.7 IWF group-broadcast group call release response
|
Table 10.3.2.7-1 describes the information flow IWF group-broadcast group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.7-1: IWF Group-broadcast group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.8 IWF group join request
|
Table 10.3.2.8-1 describes the information flow IWF group join request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.8-1: IWF group join request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the originator of the request.
(see NOTE 1)
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID of the group to which the group communication is requested
SDP offer
M
Media parameters of originator
Implicit floor request
(see NOTE 2)
O
Indicates that the originating client requests the floor.
NOTE 1: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system.
NOTE 2: This element is included only when the originating client requests the floor.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.9 IWF group join response
|
Table 10.3.2.9-1 describes the information flow group join response from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.9-1: IWF group join response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the originator of the request.
(see NOTE)
MCPTT group ID
M
The MCPTT group ID of the group to which the group communication is requested
SDP answer
M
Media parameters selected
NOTE: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.10 IWF group call leave request
|
Table 10.3.2.10-1 describes the information flow IWF group call leave request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.10-1: IWF group call leave request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group from which the user is leaving
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.11 IWF group call leave response
|
Table 10.3.2.11-1 describes the information flow IWF group call leave response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.11-1: IWF group call leave response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group from which the user is leaving
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.12 IWF group call release request
|
Table 10.3.2.12-1 describes the information flow IWF group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.12-1: IWF group call release request information elements
Information element
Status
Description
MCPTT ID
(see NOTE)
O
The MCPTT ID of the initiating MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released
Release reason
O
The reason why the call is released
NOTE: This IE is not included if the group call release is initiated by the server (e.g. due to timeout)
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.13 IWF group call release response
|
Table 10.3.2.13-1 describes the information flow IWF group call release response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.13-1: IWF group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.14 IWF pre-configured regroup request
|
Table 10.3.2.14-1 describes the information flow IWF pre-configured regroup request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.14-1 IWF pre-configured regroup request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester
MCPTT group ID
M
MCPTT group ID of the regroup group
MCPTT group ID
M
MCPTT group ID of the MCPTT group from which configuration is to be taken
MCPTT group ID list
O
(see NOTE)
List of MCPTT groups to be regrouped into the pre-configured regroup group
MCPTT ID list
O
(see NOTE)
List of MCPTT IDs to be regrouped into the pre-configured user regroup group
NOTE: One and only one of these shall be present.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.15 IWF pre-configured regroup response
|
Table 10.3.2.15-1 describes the information flow IWF pre-configured regroup response from IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.15-1 IWF pre-configured regroup response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester of the regrouping operation
MCPTT group ID
M
MCPTT group ID of the regroup group
Result
M
Result of the regrouping operation
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.16 IWF pre-configured regroup cancel request
|
Table 10.3.2.16-1 describes the information flow pre-configured regroup cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.16-1 IWF pre-configured regroup cancel request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester
MCPTT group ID
M
MCPTT group ID of the regroup group
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.17 IWF pre-configured regroup cancel response
|
Table 10.3.2.17-1 describes the information flow IWF pre-configured regroup cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.17-1 IWF pre-configured regroup cancel response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester of the regroup removal
MCPTT group ID
M
MCPTT group ID of the regroup group
Result
M
Result of the regroup removal operation
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.2.18 IWF pre-configured regroup reject (IWF – MCPTT server, MCPTT server - IWF)
|
Table 10.3.2.18-1 describes the information flow IWF pre-configured regroup reject from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.18-1 IWF pre-configured regroup reject information elements
Information Element
Status
Description
MCPTT group ID
M
MCPTT group ID of the regroup group
Reject reason
M
Reason for rejecting the regrouping operation
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3 Pre-arranged group call
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.1 General
|
The subclauses 10.3.3.2 and 10.3.3.3 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the MCPTT system. The subclauses 10.3.3.4 and 10.3.3.5 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the LMR system. The subclause 10.3.3.7 describes the late entry procedures and subclause 10.3.3.8 describes the group call release procedures. Group calls can use MC media encryption between the IWF and the MCPTT clients as described in 3GPP TS 33.180 [8]. A call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys.
The procedures in the present subclause are applicable to the following non-broadcast group call types: pre-configured group regroup calls, pre-configured user regroup calls and group regroup calls.
NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.2 Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system
|
In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.2-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.2-1: Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system
1. MCPTT user at MCPTT client 1 initiates a group call for the selected interworking group identified by MCPTT group ID.
2. MCPTT client 1 sends a group call request to the MCPTT server.
3. MCPTT server checks whether the user of MCPTT client 1 is authorized to initiate a group call on the selected interworking group.
4. MCPTT server proceeds group call setup procedures towards the affiliated MCPTT system users as described in 3GPP TS 23.379 [7].
5. MCPTT server sends IWF group call request(s) towards the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call request is sent (to the IWF) for each affiliated LMR user.
NOTE 2: How the LMR users are called is outside the scope of the present document.
NOTE 3: Steps 4 and 5 can occur in any order.
6. The IWF returns IWF group call response(s) to the MCPTT server. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
7. The MCPTT server sends group call response to the MCPTT client 1 about successful call establishment.
8. The group call on the interworking group has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.3 Group call setup initiated by LMR user on an interworking group defined in MCPTT system.
|
In this procedure, an LMR user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.3-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in MCPTT system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the interworking group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. LMR user initiates a group call.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.3-1: Group call initiated by LMR user on an interworking group defined in MCPTT system
1. The IWF sends an IWF group call request to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information.
2. MCPTT server calls the affiliated users from MCPTT system as described in 3GPP TS 23.379 [7]. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user.
NOTE 2: Steps 2 and 3 can occur in any order.
NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document.
4. The IWF returns IWF group call response(s) to the MCPTT server.
5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF.
NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document.
6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control.
NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.4 Group call setup initiated by MCPTT user on an interworking group defined in the LMR system
|
In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.4-1.
This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.4-1: Group call initiated by MCPTT user on an interworking group defined in the LMR system
1. MCPTT user at MCPTT client 1 initiates a group call on the selected interworking group identified by MCPTT group ID.
2. MCPTT client 1 sends a group call request to the MCPTT server.
3. As the interworking group is defined in the LMR system the MCPTT server sends an IWF group call request to the IWF.
4. The IWF sends individual IWF group call request(s) to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the user in MCPTT client 2.
NOTE 2: How the LMR users are called is outside the scope of the present document.
5. The MCPTT server sends a group call request to the MCPTT client 2.
6. The MCPTT client 2 acknowledges towards the MCPTT server by sending a group call response.
7. The MCPTT server acknowledges towards the IWF by sending an IWF group call response.
8. The IWF sends an IWF group call response to the MCPTT server to acknowledge the IWF group call request received in step 3.
9. The MCPTT server sends a group call response to the initiating MCPTT user. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
10. The group call over the interworking group has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.5 Group call setup initiated by LMR user on an interworking group defined in the LMR system.
|
In this procedure, an LMR user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.5-1.
This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. LMR user initiates a group call.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.5-1: Group call initiated by LMR user on an interworking group defined in the LMR system
1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information.
2. MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7].
3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response.
4. The MCPTT server acknowledges the IWF group call request(s) by sending a IWF group call response(s) to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document.
5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.3.3.6 Encrypted group call with transcoding
|
Pre-conditions:
1. An MCPTT session is established between an MCPTT client, the interworked LMR system (represented by the IWF), and the MCPTT server.
2. There is an ongoing media transmission.
3. An SDP negotiation has occurred between the IWF and MCPTT Server to establish both the vocoder and the security parameters for the call.
4. The IWF is configured to perform transcoding of voice media and has obtained key material from the MCPTT system using the procedures in 3GPP TS 33.180 [8].
Figure 10.3.3.6-1: Encrypted group call with transcoding
1. The MCPTT client has been given the floor and is transmitting voice media.
2. The MCPTT client encodes audio using a codec defined for the MCPTT group, encrypts the encoded voice using procedures in 3GPP TS 33.180 [8], and forwards the encrypted voice media to the MCPTT server.
3. The MCPTT server forwards the encrypted voice media to other participants in the group call including the IWF.
4. The IWF decrypts the voice media from the MCPTT client using the procedures in 3GPP TS 33.180 [8]. The IWF transcodes the voice to a LMR codec. If needed, the IWF re-encrypts the transcoded voice media using LMR security procedures (these are out-of-scope of this specification), and forwards the voice media to the LMR system.
NOTE: Where transcoding occurs is outside the scope of this specification. In this procedure, it is assumed to take place internal to the IWF.
5. Sometime later the floor becomes idle.
6. The LMR system (represented by the IWF in figure 10.3.3.6‑1) requests and is granted the floor.
7. The IWF has been given the floor and is transmitting voice media.
8. The IWF receives voice media from the LMR system. If the voice media is encrypted, the IWF decrypts the voice media using LMR security procedures (these are out-of-scope of this specification). The IWF transcodes the voice to the group's MCPTT codec. The IWF re-encrypts the transcoded voice using the procedures in 3GPP TS 33.180 [8].
9. The IWF forwards the voice media to the MCPTT server.
10. The MCPTT server forwards the voice media to other participants in the group call.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.