Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.282  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.1.10…   7.4.2.2…   7.4.2.5…   7.4.2.8…   7.4.3…   7.5…   7.5.2.1.12…   7.5.2.2…   7.5.2.4…   7.5.2.6…   7.5.2.8…   7.5.2.11…   7.5.2.14…   7.5.3…   7.6   7.7…   7.7.2.3…   7.8…   7.9…   7.13…   7.13.3.1.19…   7.13.3.2…   7.13.3.8…   7.13.3.16…   7.13.4…   7.14…   7.14.2.2…   A…   B…

 

7.5.2.11  One-to-one FD communication upgrade to an emergency FD communication |R16|p. 131

7.5.2.11.1  Generalp. 131
This clause is for adding procedures related to upgrading an existing one-to-one FD communication to an emergency one-to-one FD communication.
7.5.2.11.2  Procedurep. 132
The procedure in Figure 7.5.2.11.2-1 describes the case where an authorized MCData user is upgrading a MCData one-to-one FD communication to a MCData emergency one-to-one FD communication. This procedure is applicable only when MCData one-to-one file distribution communication is established as described in subclause 7.5.2.5 "One-to-one file distribution using media plane".
Pre-conditions:
  1. Both members of the one-to-one FD communication belong to the same MCData system.
  2. One-to-one FD communication is already in progress.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.5.2.11.2-1: One-to-one FD communication upgrade to an emergency one-to-one FD communication
Up
Step 1.
The MCData user at MCData client 1 initiates an emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client is retained until explicitly cancelled by the user of MCData client 1.
Step 2.
MCData client 1 requests the MCData server to upgrade the MCData one-to-one FD communication to in-progress emergency by sending a MCData one-to-one FD upgrade request.
Step 3.
The MCData server sends the MCData one-to-one FD upgrade request towards MCData client 2.
Step 4.
The MCData user of MCData client 2 is notified of the in-progress emergency of the MCData emergency one-to-one FD communication.
Step 5.
The MCData client 2 acknowledges the MCData one-to-one FD upgrade request and sends MCData one-to-one FD upgrade response to the MCData server.
Step 6.
The MCData server adjusts the priority of the underlying bearer for both participants of the MCData one-to-one FD communication. The priority is retained until the communication ends.
Step 7.
The MCData server sends MCData one-to-one FD upgrade response to MCData client 1.
Step 8.
MCData client 1 and MCData client 2 continue with the MCData one-to-one FD communication, which has been transformed into an MCData emergency one-to-one FD communication.
Up

7.5.2.12  Group FD communication upgrade to an emergency group FD communication |R16|p. 133

7.5.2.12.1  Generalp. 133
This clause is for adding procedures related to upgrading an existing MCData group FD communication to an MCData emergency group FD communication.
7.5.2.12.2  Procedurep. 133
The procedure in Figure 7.5.2.12.2-1 describes the case where an authorized MCData user is upgrading an onging MCData group FD communication to an MCData emergency group FD communication. This procedure is applicable only when group MCData FD communication is established as described in subclause 7.5.2.7 "Group standalone file distribution using media plane".
Pre-conditions:
  1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 are affiliated to that MCData group.
  2. All members of the MCData group belong to the same MCData system.
  3. An MCData group FD communication is already in progress.
  4. The initiating MCData client 1 has been configured to send an MCData emergency alert when upgrading an MCData emergency group communication.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.5.2.12.2-1: MCData group FD communication upgraded to an MCData emergency group FD communcation
Up
Step 1.
The MCData user at MCData client 1 initiates a group emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1.
Step 2.
MCData client 1 requests the MCData server to upgrade the MCData group to an in-progress emergency state by sending a MCData group FD upgrade request. The MCData client 1 sets the emergency indicator in the request. If configured to send an MCData alert when initiating an MCData emergency upgrade, the request also contains an indication that an MCData alert is to be initiated.
Step 3.
The MCData server sets the emergency state of the MCData group and adjusts the priority of the underlying bearer for all or selected participants in the MCData group FD communication that receive the communication over unicast.
Step 4.
MCData server sends the MCData group FD upgrade request towards the MCData clients of each of those affiliated MCData group members. The request contains an indication of an MCData emergency alert if the request from the originator indicated MCData emergency alert.
Step 5.
MCData users are notified of the in-progress emergency state of the MCData group.
Step 6.
The receiving MCData clients send the MCData group FD upgrade response to the MCData server to acknowledge the MCData group emergency request. For a multicast call, these acknowledgements are not sent.
Step 7.
The MCData server sends the MCData group FD upgrade response to the MCData user 1 to confirm the upgrade request.
MCData client 1, MCData client 2 and MCData client 3 continue with the MCData group FD communication, which has been transformed into an MCData emergency group FD communication.
Up

7.5.2.13  Group FD communication in-progress emergency group state cancel |R16|p. 135

7.5.2.13.1  Generalp. 135
This clause describes procedures related to an MCData in-progress emergency group state cancel. The emergency state of the group can also be cancelled by the group SDS in-progress emergency state cancellation procedure in subclause 7.4.2.10.2, or by the emergency alert cancellation procedure specified in TS 23.280, subclause 10.10.1.2.2.2.
Up
7.5.2.13.2  Procedurep. 135
The procedure in Figure 7.5.2.13.2-1 describes the case where an authorized MCData user cancels MCData group's in-progress emergency.
Pre-conditions:
  1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group.
  2. All members of the MCData group belong to the same MCData system.
  3. MCData group members have been notified about the in-progress emergency.
  4. The MCData group is in the in-progress emergency state and has prioritized bearer support.
  5. MCData client 1 previously initiated the in-progress emergency for the group.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.5.2.13.2-1: MCData group FD in-progress emergency group state cancel
Up
Step 1.
The user at the MCData client 1 initiates an MCData group FD in-progress emergency group state cancel.
Step 2.
The MCData client 1 sends an MCData group FD in-progress priority state cancel request to the MCData server. The MCData client 1 also resets emergency indicator in the request to inform MCData server about cancellation of in-progress emergency group state.
Step 3.
The MCData server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCData server cancels/resets the emergency in-progress state of the MCData group.
Step 4.
The MCData server sends an MCData group FD in-progress priority state cancel request to the MCData group members.
Step 5.
MCData group members are notified of the MCData group FD in-progress emergency state cancel.
Step 6.
The receiving MCData clients send the MCData group FD in-progress priority state cancel response to the MCData server to acknowledge the MCData in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent.
Step 7.
The MCData server sends the MCData group FD in-progress priority state cancel response to the MCData user 1 to confirm the MCData in-progress emergency group state cancel. If the MCData in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCData client 1 resets its local emergency status.
Up

Up   Top   ToC