Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.283  Word version:  19.0.0

Top   Top   Up   Prev   None
1…   10…   10.2…   10.3…   10.3.2   10.3.3…   10.3.4…   10.3.5…   10.3.6…   10.3.7…   10.3.8…   10.4…   10.5…   10.6…   10.6.2…   10.6.3…   10.7…   10.8…   10.11…   10.12…   10.14…   10.15…   10.17… 
10.17 Ad hoc group call  10.17.1 General  10.17.2 Information flows for ad hoc group call  10.17.3 Procedures  10.17.3.1 Ad hoc group call initiated by an MCPTT user with MCPTT server determining the participant list  10.17.3.2 Ad hoc group call initiated by an LMR user with MCPTT server determining the participant list  10.17.3.3 IWF ad hoc group call released by the MC system  10.17.3.4 IWF ad hoc group call released by the LMR system  10.17.3.5 IWF ad hoc group call initiated by an MCPTT user using a participants list  $ Change history 

 

10.17  Ad hoc group call |R19|  p. 182

10.17.1  General  p. 182

The following clauses define information flows and signalling procedures for ad hoc group calls, where the ad hoc group call is established based on criteria or based on a list of participants provided by the call initiator. The MCPTT server determines the list of users. The list consists of MCPTT users and one LMR user that is representing a group in LMR system (GSM-R) Then the MCPTT server acts as the call control server and individually calls each MCPTT user that the specific LMR user via the IWF.
Up

10.17.2  Information flows for ad hoc group call  p. 182

10.17.2.1  General  p. 182

The following clauses define information flows for ad hoc group calls on the IWF-1 interface. Ad hoc group call related information flows on reference points other than IWF-1 are defined in TS 23.379.

10.17.2.2  IWF ad hoc group call request (MCPTT server - IWF and IWF - MCPTT server)  p. 182

Table 10.17.2.2-1 describes the information flow IWF ad hoc group call request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Information element Status Description
MCPTT IDMThe MCPTT ID of the calling party.
Functional aliasOThe functional alias of the calling party.
MCPTT ad hoc group IDMThe MCPTT group ID to be associated with the ad hoc group communication.
Preconfigured MCPTT group IDOIndicates pre-configured group configuration to be used for the ad hoc group call.
MCPTT IDOMCPTT ID of the participant being invited for the ad hoc group call.
SDP offerMOffered Media parameters.
Implicit floor request (see NOTE 1)OWhen originating client requests the floor, this element shall be included.
Broadcast indicator (see NOTE 2)OIndicates that the ad hoc group call request is for a broadcast ad hoc group call.
Imminent peril indicator (see NOTE 2)OIndicates that the ad hoc group call request is an MCPTT imminent peril ad hoc group call.
Emergency Indicator (see NOTE 2)OIndicates that the ad hoc group call request is an MCPTT emergency ad hoc group call.
Location informationOLocation of the calling party.
Criteria for determining the participants (see NOTE 3)OCarries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area.
Additional application specific data (see NOTE 4)OSome LMR systems use additional information at the application layer.
Requested priorityOApplication priority level requested for this group call.
NOTE 1:
This element is included only when the originating client requests the floor.
NOTE 2:
If used, only one of these information elements is present.
NOTE 3:
This element can be used by the IWF together with the LMR system to determine the users to be invited in the LMR system.
NOTE 4:
This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
Up

10.17.2.3  IWF ad hoc group call response (IWF - MCPTT server and MCPTT server - IWF)  p. 183

Table 10.17.2.3-1 describes the information flow IWF ad hoc group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Information element Status Description
MCPTT IDMThe MCPTT ID of the calling party.
Functional aliasOThe functional alias of the calling party.
MCPTT ad hoc group IDMThe MCPTT group ID associated with the ad hoc group call.
SDP answerOMedia parameters selected and present if the Result is success.
ResultMResult of the group call request (success or failure).
Additional application specific data (see NOTE)OSome LMR systems use additional information at the application layer.
NOTE:
This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
Up

10.17.2.4  IWF ad hoc group call release request (MCPTT server - IWF and IWF - MCPTT server)  p. 184

Table 10.17.2.4-1 describes the information flow IWF ad hoc group call release request from the MCPTT server to the IWF from the IWF to the MCPTT server.
Information element Status Description
MCPTT IDMThe MCPTT ID of the user authorized to release the ad hoc group call.
Functional aliasOThe functional alias of the authorized user requesting to release the ad hoc group call.
MCPTT ad hoc group IDMThe MCPTT group ID of the ad hoc group call on which call is released.
Additional application specific data (see NOTE)OSome LMR systems use additional information at the application layer.
NOTE:
This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
Up

10.17.2.5  IWF ad hoc group call release response (IWF - MCPTT server)  p. 184

Table 10.17.2.5-1 describes the information flow IWF ad hoc group call release response from the IWF to the MCPTT server.
Information element Status Description
MCPTT IDMThe MCPTT ID of the ad hoc group call participant.
Functional aliasOThe functional alias of the ad hoc group call participant.
MCPTT ad hoc group IDMThe MCPTT group ID of the ad hoc group call that is released.
Additional application specific data (see NOTE)OSome LMR systems use additional information at the application layer.
NOTE:
This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
Up

10.17.3  Procedures  p. 185

10.17.3.1  Ad hoc group call initiated by an MCPTT user with MCPTT server determining the participant list  p. 185

In this procedure, an MCPTT user is initiating an ad hoc group call based on criteria involving both MCPTT users and LMR users.
Pre-conditions:
  1. The MCPTT user at MCPTT client 1 is authorized to initiate ad hoc group call.
  2. The MCPTT user at MCPTT client 1 wants to invite MCPTT and LMR users who are satisfying certain criteria for the ad hoc group call.
  3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.17.3.1-1: Ad hoc group call setup initiated by an MCPTT user in the MCPTT system
Figure 10.17.3.1-1: Ad hoc group call setup initiated by an MCPTT user in the MCPTT system
Up
The procedure and information flows as defined in clause 10.19.3.1.1 of TS 23.379 is applied with the following differences:
Step 1-7.
Same as clause 10.19.3.1.3 in TS 23.379.
Step 8.
The MCPTT server sends the IWF ad hoc group call request to the IWF.
Step 9.
The IWF returns with an IWF ad hoc group call response to the MCPTT server.
Step 10.
Same as step 10 in clause 10.19.3.1.3 in TS 23.379.
Step 11.
The MCPTT server may notify the initiating MCPTT user of all MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT ad hoc group call. The authorized users (not shown in Figure), who are configured to receive the participants information of ad hoc group call, are notified to receive the MCPTT IDs of the MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call, when the MCPTT users joins late or leave the MCPTT ad hoc group call.
Step 12.
MCPTT client 1, MCPTT client 2, and the LMR users establish media plane and floor control resources.
Up

10.17.3.2  Ad hoc group call initiated by an LMR user with MCPTT server determining the participant list  p. 187

In this procedure, an LMR user is initiating an ad hoc group call based on criteria involving both MCPTT users and LMR users.
Pre-conditions:
  1. The LMR user is authorized to initiate ad hoc group call.
  2. An LMR user want to invite MCPTT users who are satisfying certain criteria for the ad hoc group call.
  3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.17.3.2-1: Ad hoc group call setup initiated by an LMR user in the MCPTT system
Figure 10.17.3.2-1: Ad hoc group call setup initiated by an LMR user in the MCPTT system
Up
The procedure and information flows as defined in clause 10.19.3.1.1 of TS 23.379 is applied with the IWF acting as a MCPTT client.

10.17.3.3  IWF ad hoc group call released by the MC system  p. 188

In this procedure, the ad hoc group call is released by the MC system due to the release conditions or the ad hoc group call is released by an authorized user.
Pre-conditions:
  1. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
  2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.17.3.3-1: Release IWF ad hoc group call by the MC system
Figure 10.17.3.3-1: Release IWF ad hoc group call by the MC system
Up
The procedure and information flows as defined in clause 10.19.3.1.2 and 10.19.3.1.2a of TS 23.379 are applied to the interactions between the MCPTT client and the MCPTT server. In addition, new step 2a and 2b are introduced.
Step 1.
The IWF ad hoc group call is releasing at the MCPTT system either initiated by the server due to the release conditions are met as described in clause 10.19.3.1.2 in TS 23.379 or by an authorized user as described in clause 10.19.3.1.2a in TS 23.379.
Step 2a-2b.
The MCPTT server sends the IWF ad hoc group call release request to the IWF (2a), and the IWF returns the IWF ad hoc group call release response (2b).
Step 3.
MCPTT client 1, client 2 and LMR users have successfully released the floor control and media plane resources associated with the ad hoc group call that is terminated and the ad hoc group ceases to exist (i.e., further call is not possible over the same ad hoc group).
Up

10.17.3.4  IWF ad hoc group call released by the LMR system  p. 189

In this procedure, the ad hoc group call is released by the LMR system due to a release condition on the LMR system.
Pre-conditions:
  1. The LMR user that is sending the ad hoc group call release request to the MCPTT server is an authorized user as described in clause 10.19.3.1.2a in TS 23.379.
  2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.17.3.4-1: Release IWF ad hoc group call by the LMR system
Figure 10.17.3.4-1: Release IWF ad hoc group call by the LMR system
Up
The procedure and information flows as defined in clause 10.19.3.1.2a of TS 23.379 are applied to the interactions between the LMR user and the MCPTT server.

10.17.3.5  IWF ad hoc group call initiated by an MCPTT user using a participants list  p. 190

In this procedure, an MCPTT user is initiating an ad hoc group call with both MCPTT users and LMR users.
Pre-conditions:
  1. The MCPTT client 1 knows the MCPTT IDs of the participants, including both MCPTT users and LMR users, to be involved in this call.
  2. MCPTT client 1 and MCPTT client 2 are registered, and their respective users are authenticated and authorized to use the MCPTT service.
Reproduction of 3GPP TS 23.283, Fig. 10.17.3.5-1: Ad hoc group call setup initiated by an MCPTT user in the MCPTT system
Figure 10.17.3.5-1: Ad hoc group call setup initiated by an MCPTT user in the MCPTT system
Up
The procedure and information flows as defined in clause 10.19.3.1.1 of TS 23.379 is applied with the following differences:
Step 1-3.
Same as clause 10.19.3.1.1 in TS 23.379.
Step 4a-4b.
For each of the LMR users, the MCPTT server sends the IWF ad hoc group call request to the IWF. The IWF returns the IWF ad hoc group call response to the MCPTT server.
Step 5.
Same as clause 10.19.3.1.1 in TS 23.379.
Step 6.
If the initiating MCPTT user requires the acknowledgement from the invited MCPTT users, and the required MCPTT users do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCPTT server may proceed with or abandon the call and then notify the initiating MCPTT user that the acknowledgements did not include all required members according to ad hoc group call policy from the user profile configuration. The MCPTT server may notify the initiating MCPTT user of all MCPTT users who did not acknowledge the ad hoc group call request within the configured time. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT ad hoc group call.
Step 7.
MCPTT client 1, MCPTT client 2, and the LMR users establish media plane and floor control resources.
Up

$  Change history  p. 192

Up   Top