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.4.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.7…   7.4.3…   7.5…   7.5.2.5…   7.5.2.10…   7.5.3…   7.6…   7.7…   7.8…   7.9…   7.13…   7.13.3.14…   7.13.4…   7.14…   7.17…   7.17.3.1.4…   7.17.3.2…   7.17.3.2.5…   7.17.4…   7.17.6…   A…   B… 
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.6 Modification of ad hoc group data communication participants by an authorized user  7.17.3.2.7 Modification of ad hoc group data session criteria by an authorized user 
...

 

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. 251
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
7.17.3.2.6  Modification of ad hoc group data communication participants by an authorized user  p. 252
Figure 7.17.3.2.6-1 below illustrates the MCData user modifying the ad hoc group data communication participants procedure involving multiple MCData systems.
Pre-conditions:
  1. An MCData ad hoc group data communication is already in progress the participants list provided by the originating MCData user while initiating the MCData ad hoc group data communication.
  2. The participants of the MCData ad hoc group data communication belongs to the multiple MCData system.
  3. The MCData user at MCData client 1 determines that the MCData client 3 needs to be invited to on-going ad hoc group data communication and MCData client 2 needs to be removed from the on-going ad hoc group data communication from the primary MCData system.
  4. The MCData user at MCData client 1 determines that the MCData client 5 needs to be invited to on-going ad hoc group data communication and MCData client 4 needs to be removed from the on-going ad hoc group data communication from the partner MCData system.
Reproduction of 3GPP TS 23.282, Fig. 7.17.3.2.6-1: Modification of ad hoc group data communication participants by an authorized user
Figure 7.17.3.2.6-1: Modification of ad hoc group data communication participants by an authorized user
Up
Step 1.
The MCData client 1 sends the modify ad hoc group data session participants request to the MCData server 1 to remove both MCData client 2 and MCData client 4 from the on-going ad hoc group data communication and to add both MCData client 3 and MCData client 5 into on-going ad hoc group data communication.
Step 2.
The MCData server 1 verifies whether the MCData client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group data communication.
Step 3.
The MCData server 1 sends modify ad hoc group data session participants response to the MCData client 1.
Step 4.
The MCData server 1 determines that MCData client 1 has requested that MCData client 3 from the primary MC system be invited to an on-going ad hoc group data communication and successfully added to the data communication according to the procedure defined in clause 7.17.3.1.4.
Step 5.
The MCData server 1 determines that MCData client 1 has requested that MCData client 2 from the primary MC system be removed from the on-going ad hoc group data communication and successfully removed from data communication according to the procedure defined in clause 7.17.3.1.4.
Step 6.
The MCData server 1 determines that MCData client 1 has requested that MCData client 5 from the partner MC system be invited to an on-going ad hoc group data communication. The MCData server 1 sends the ad hoc group data session request to the MCData client 5.
Step 7.
The MCData client 5 notifies the user about the incoming ad hoc group data communication.
Step 8.
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 9.
The on-going ad hoc group data communication is updated by adding MCData client 5 which is based on the modify participant list provided by the MCData client 1.
Step 10.
The MCData server 1 determines that MCData client 1 has requested that MCData client 4 from the partner MC system be removed from the on-going ad hoc group data communication. The MCData server 1 sends the ad hoc group data session leave request to the MCData client 4.
Step 11.
The MCData client 4 notifies the user of the ad hoc group data session leave request.
Step 12.
The MCData client 4 sends the ad hoc group data session leave response to the MCData server 1.
Step 13.
The on-going ad hoc group data communication is updated by removing MCData client 4, which is based on the modify participant list provided by the MCData client 1.
Step 14.
The MCData server 1 may notify the initiating MCData user of all the users who are added to the on-going ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the ad hoc group data communication.
Step 15.
The MCData server 1 may notify the authorized participants about the change in the participants list of on-going ad hoc group data communication.
Up
7.17.3.2.7  Modification of ad hoc group data session criteria by an authorized user |R19|  p. 254
Figure 7.17.3.2.7-1 illustrates the modification of ad hoc group data session criteria procedure by the initiator of the ad hoc group data session between multiple MC systems.
Preconditions:
  • The MCData user at the MCData client 1 is authorized to modify the criteria.
  • The MCData server A and MCData server B are aware of the criteria related to the ongoing ad hoc group data session.
  • MC system A and MC system B are interconnected.
Reproduction of 3GPP TS 23.282, Fig. 7.17.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group data session between multiple MC systems
Figure 7.17.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group data session between multiple MC systems
Up
Step 1.
An ad hoc group data session has been established based on criteria sent by an authorized MCData client upon initiating the ad hoc group data session.
Step 2.
The MCData user at the MCData client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group data session participants.
Step 3a/b.
The MCData server A receives the modify ad hoc group data session criteria request and forwards the request to MCData server B at MC system B.
Step 4a/b.
The MCData server A receives the ad hoc group data session criteria modify response and forwards the response to MCData client 1 in MC system A
Step 5.
MCData server B detects that MCData client 3 meets the criteria for the ongoing ad hoc group data session initiated at MC system A.
Step 5a.
MCData server B sends an ad hoc group data session add user notification message towards MCData server A.
Step 5b.
MCData server A sends an ad hoc group data session request towards MCData client 3.
Step 5c.
The MCData user 3 is notified of entering an ongoing ad hoc group data session.
Step 5d.
MCData client 3 sends an ad hoc group data session response towards MCData server A.
Step 5e.
MCData server B sends an ad hoc group data session remove user notification message towards MCData server A.
Step 5f.
MCData server A sends an ad hoc group data session leave request towards MCData client 4.
Step 5g.
The MCData user 4 is notified of leaving an ongoing ad hoc group data session.
Step 5h.
MCData client 4 sends an ad hoc group data session leave response towards MCData server A.
Step 6.
The MCData server A may notify the authorised MCData user of all the users who are added to the on-going ad hoc group data session. This notification may be sent to the authorised MCData user by the MCData server A more than once during the data session when MCData users join or leave the ad hoc group data session.
Step 7.
The MCData server A adds MCData client 3 to the ad hoc group data session and removes MCData client 4 from the ad hoc group data session.
The MCData servers continuously check whether other MCData clients meet or if participating MCData clients no longer meet the criteria for the ad hoc group data session.
Up

Up   Top   ToC