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.379  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.13…   10.6.2.2.24…   10.6.2.3…   10.6.2.3.1.2…   10.6.2.3.2…   10.6.2.4…   10.6.2.4.3…   10.6.2.5…   10.6.2.5.2.3…   10.6.2.6…   10.6.2.6.2…   10.6.2.7…   10.6.2.10…   10.6.3…   10.7…   10.7.2.2…   10.7.2.3…   10.7.3…   10.7.4…   10.7.5…   10.7.5.2.3a…   10.7.6…   10.7.6.2.3…   10.9…   10.9.1.3…   10.9.1.3.2…   10.9.1.3.3…   10.9.1.4…   10.9.1.5…   10.9.2…   10.9.2.6…   10.10…   10.12…   10.14…   10.15…   10.19…   10.19.2.11…   10.19.3…   10.19.3.1.4…   10.19.3.2…   10.19.3.2.4…   10.19.3.2.6…   A…   A.4…   B… 
10.6.2.6.2 MCPTT imminent peril group call  10.6.2.6.2.1 MCPTT imminent peril group call commencement  10.6.2.6.2.2 Imminent peril group call upgrade  10.6.2.6.2.3 MCPTT in-progress imminent peril group state cancel  10.6.2.6.3 MCPTT emergency alert (on-network)  10.6.2.6.3a MCPTT ad hoc group emergency alert (on-network) 
...

 

10.6.2.6.2  MCPTT imminent peril group call  p. 87
10.6.2.6.2.1  MCPTT imminent peril group call commencement  p. 87
The procedure focuses on the case where an authorized MCPTT user is initiating an imminent peril group call for communicating with the affiliated MCPTT members of that MCPTT group. This procedure will gain elevated access privilege for the MCPTT client if it is not already in that state. The access privilege for other applications will not necessarily be affected.
Procedures in Figure 10.6.2.6.2.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an imminent peril group call with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server.
Pre-conditions:
  1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group.
  2. All members of the MCPTT group belong to the same MCPTT system.
  3. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated in the provisioning to be used for imminent peril communications.
  4. Optionally, MCPTT client 1 may use an activated functional alias for the group communication.
  5. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.6.2.1-1: MCPTT imminent peril group call
Figure 10.6.2.6.2.1-1: MCPTT imminent peril group call
Up
Step 1.
The user at the MCPTT client 1 initiates an imminent peril group call. The MCPTT user at MCPTT client 1 may select a functional alias used for the call.
Step 2.
MCPTT client 1 sends an MCPTT imminent peril group call request towards the MCPTT server. The request contains an indication of the in-progress imminent peril. The MCPTT server records the identity of the MCPTT user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCPTT group is considered to be in an in-progress imminent peril state until cancelled. The request may contain an indication of an implicit floor request. If the group call request includes an implicit floor request it may also include location information.
Step 3.
The MCPTT server implicitly affiliates MCPTT client 1 to the imminent peril group if the client is not already affiliated.
Step 4.
MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of imminent peril group calls on the indicated MCPTT group, and if authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. The MCPTT server checks whether the provided functional alias, if present, can be used and has been activated for the user.
Step 5.
The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group.
Step 6.
MCPTT server sends the imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress imminent peril. If location information was included in the imminent peril group call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
Step 7.
MCPTT users are notified of the incoming imminent peril call. The functional alias of the group call initiating MCPTT user may be displayed.
Step 8.
The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the imminent peril call request. For a multicast call, these acknowledgements are not set.
Step 9.
The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to inform the successful imminent peril call establishment.
MCPTT client 1, MCPTT client 2 and MCPTT client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane, while the other MCPTT clients receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the imminent peril call will be receiving that media.
Up
10.6.2.6.2.2  Imminent peril group call upgrade  p. 89
The procedure focuses on the case where an authorized MCPTT user is upgrading an MCPTT group call to an imminent peril group call while the MCPTT group call is already in progress.
Procedures in Figure 10.6.2.6.2.2-1 are the signalling control plane procedures for the MCPTT client upgrading an MCPTT group call on an MCPTT group to an imminent peril group call.
Pre-conditions:
  1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group.
  2. All members of the MCPTT group belong to the same MCPTT system.
  3. An MCPTT group call is already in progress.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.6.2.2-1: MCPTT group call upgrade to an imminent peril group call
Figure 10.6.2.6.2.2-1: MCPTT group call upgrade to an imminent peril group call
Up
Step 1.
The MCPTT user at MCPTT client 1 initiates an imminent peril call.
Step 2.
MCPTT client 1 requests the MCPTT server to upgrade the MCPTT group to an in-progress imminent peril state by sending an MCPTT imminent peril group call request. The request may contain an indication of an implicit floor request. If the imminent peril group call request includes an implicit floor request it may also include location information.
Step 3.
The MCPTT server adjusts the priority of the underlying bearer for all participants in the MCPTT group.
Step 4.
The MCPTT server sends the MCPTT imminent peril group call request towards the MCPTT clients of the affiliated MCPTT group members. If location information was included in the imminent peril group call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
Step 5.
MCPTT users are notified of the in-progress imminent peril state of the MCPTT group.
Step 6.
The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the MCPTT imminent peril group call request. For a multicast call, these acknowledgements are not set.
Step 7.
The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to confirm the upgrade request.
MCPTT client 1, MCPTT client 2 and MCPTT client 3 continue with the MCPTT group call, which has been transformed into an imminent peril group call.
Up
10.6.2.6.2.3  MCPTT in-progress imminent peril group state cancel  p. 91
The procedure focuses on the case where an authorized MCPTT user cancels an MCPTT group's in-progress imminent peril state.
Procedures in Figure 10.6.2.6.2.3-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT group's in-progress imminent peril state.
Pre-conditions:
  1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group.
  2. All members of the MCPTT group belong to the same MCPTT system.
  3. The MCPTT group is in an in-progress imminent peril state and has prioritized bearer support.
  4. MCPTT group members have been notified about the MCPTT group's in-progress imminent peril state.
  5. MCPTT client 1 previously initiated the in-progress imminent peril.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.6.2.3-1: MCPTT in-progress imminent peril group state cancel
Figure 10.6.2.6.2.3-1: MCPTT in-progress imminent peril group state cancel
Up
Step 1.
The user at the MCPTT client 1 initiates an in-progress imminent peril group state cancel.
Step 2.
MCPTT client 1 sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT server.
Step 3.
The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCPTT server cancels/resets the in-progress imminent peril group state.
Step 4.
MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based upon the information from group management server.
Step 5.
The MCPTT server sends an MCPTT imminent peril group state cancel request to the MCPTT group members.
Step 6.
MCPTT group members are notified of the in-progress imminent peril group state cancel.
Step 7.
The receiving MCPTT group members send the MCPTT in-progress imminent peril group state cancel response to the MCPTT server to acknowledge the MCPTT in-progress imminent peril group state cancel request. For a multicast scenario, these acknowledgements are not set.
Step 8.
The MCPTT server sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT user 1 to confirm the MCPTT in-progress imminent peril group state cancel request.
Up
10.6.2.6.3  MCPTT emergency alert (on-network)  p. 92
The MCPTT service shall support the procedures and related information flows as specified in subclauses 10.10.1 of TS 23.280 with the following clarifications:
  • The MC service client is the MCPTT client;
  • The MC service server is the MCPTT server;
  • The MC service group ID is the MCPTT Group ID; and
  • The MC service user profile index is the MCPTT user profile index.
10.6.2.6.3a  MCPTT ad hoc group emergency alert (on-network) |R18|  p. 92
The MCPTT service shall support the procedures and related information flows as specified in subclauses 10.10.3 of TS 23.280 with the following clarifications:
  • The MC service client is the MCPTT client;
  • The MC service server is the MCPTT server;
  • The MC service group ID is the MCPTT Group ID; and
  • The MC service user profile index is the MCPTT user profile index.

Up   Top   ToC