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.282  Word version:  19.3.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.1.13…   7.7.2.2…   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…   7.17…   7.17.2.13…   7.17.3…   7.17.3.1.4…   7.17.3.2…   7.17.3.2.4…   7.17.3.2.6…   7.17.4…   7.17.6…   7.17.7…   A…   B… 
7.17.3.2.4 Modifying of ad hoc group data communication participants by the MCData server  7.17.3.2.5 Release ad hoc group data communication and stop determining the ad hoc group data communication participants by partner MCData system - Participants list determined by the MCData server 
...

 

7.17.3.2.4  Modifying of ad hoc group data communication participants by the MCData server  p. 248
Figure 7.17.3.2.4-1 below illustrates the MCData server modifying the ad hoc group data communication participants procedure involving multiple MCData systems.
Pre-conditions:
  1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication.
  2. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication.
  3. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, and MCData client 4. The participants list is determined by both primary and partner MC systems.
  4. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication.
  5. The MCData server 1 of the primary MCData system detects that the MCData client 3 meets the criteria and MCData client 2 stops to meet the criteria specified by the MCData client 1.
  6. The MCData server 2 of the partner MCData system detects that the MCData client 5 meets the criteria and MCData client 4 stops to meet the criteria specified by the MCData client 1.
Reproduction of 3GPP TS 23.282, Fig. 7.17.3.2.4-1: Modification of ad hoc group data communication participants by the MCData server
Figure 7.17.3.2.4-1: Modification of ad hoc group data communication participants by the MCData server
Up
Step 1.
The MCData server 1 detects that MCData client 3 now meets criteria and successfully added to group data communication.
Step 2.
The MCData server 1 detects that MCData client 2 does not meet criteria any more and successfully removed from a group data communication.
Step 3.
The MCData server 2 detects that the MCData client 5 meets the criteria specified by the MCData client 1.
Step 4.
The MCData server 2 sends the notification to MCData server 1 of the primary MCData system to add the MCData user at MCData client 5 to on-going ad hoc group data communication.
Step 5.
The MCData server 1 sends the ad hoc group data session request to the MCData client 5.
Step 6.
The MCData client 5 notifies the user about the incoming ad hoc group data communication.
Step 7.
The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server 1.
Step 8.
The on-going ad hoc group data communication is updated by adding MCData client 5 which meets the criteria specified by the MCData client 1.
Step 9.
The MCData server 2 detects that the MCData client 4 is no longer satisfying the criteria to be the participant of the ad hoc group data communication.
Step 10.
The MCData server 2 sends the notification to MCData server 1 of the primary MCData system to remove the MCData user at MCData client 4 from on-going ad hoc group data communication.
Step 11.
The MCData server 1 sends the ad hoc group data session leave request to the MCData client 4 and removes it from the on-going ad hoc group data communication.
Step 12.
The MCData client 4 notifies the user of the ad hoc group data session leave request.
Step 13.
The MCData client 4 sends the ad hoc group data session leave response to the MCData server 1.
Step 14.
The on-going ad hoc group data communication is updated by removing MCData client 4, which no longer meets the criteria specified by the MCData client 1.
Up
7.17.3.2.5  Release ad hoc group data communication and stop determining the ad hoc group data communication participants by partner MCData system - Participants list determined by the MCData server  p. 250
Figure 7.17.3.2.5-1 below illustrates the release of ad hoc group data communication and stopping of MCData server at the partner MC system from determining the ad hoc group data communication participants' procedure once involving multiple MCData systems. This procedure, in particular describes about how the partner MC system is notified about ad hoc group data communication release to cease the determining of the participants by the partner MC system.
Pre-conditions:
  1. The MCData user at MCData client 1 is authorized to initate ad hoc group data communication.
  2. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, MCData client 3, and MCData client 4.
  3. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication.
  4. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication.
Reproduction of 3GPP TS 23.282, Fig. 7.17.3.2.5-1: MCData server releases an ad hoc group data communication and stops the determination of ad hoc group data communication participants involving multiple MCData systems
Figure 7.17.3.2.5-1: MCData server releases an ad hoc group data communication and stops the determination of ad hoc group data communication participants involving multiple MCData systems
Up
Step 1.
The MCData server 1 detects that the ad hoc group data communication which is ongoing is to be released e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCData group members are not present.
Step 2.
The MCData server 1 sends the ad hoc group data session release notification to MCData server 2 of the partner MCData system about the ad hoc group data communication release to stop determining the participants list by MCData server 2 of the partner MCData system.
Step 3a-3d.
The MCData server 1 sends ad hoc group data session release request to all the participants of the ad hoc group data communication.
Step 4a-4d.
The MCData clients notifies the user about the release of the ad hoc group data communication.
Step 5a-5d.
All the participants of the ad hoc group data communication receives the ad hoc group data session release request and sends the ad hoc group data session release response to the MCData server 1 of the primary MCData server.
Up

Up   Top   ToC