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.281  Word version:  19.4.0

Top   Top   Up   Prev   Next
1…   5…   6…   7…   7.1.2.3…   7.1.2.4…   7.1.3…   7.2…   7.2.3…   7.3…   7.4…   7.5…   7.6…   7.7…   7.7.1.3.5…   7.7.2…   7.8…   7.17…   7.19…   7.19.3…   7.19.3.1.4…   7.19.3.2…   7.19.3.2.5…   A… 
7.19.3.2.5 Procedure for ad hoc group call release by MCVideo server - Participants list provided by the Initiator  7.19.3.2.6 Modification of ad hoc group call participants by an authorized user  7.19.3.2.7 Modification of ad hoc group call criteria by an authorized user 

 

7.19.3.2.5  Procedure for ad hoc group call release by MCVideo server - Participants list provided by the Initiator  p. 207
This procedure focuses on the case where an MCVideo server initiates the termination of an ongoing MCVideo ad hoc group call for all the participants of that group call, since at least one of the termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCVideo group members are not present.
Procedures in Figure 7.19.3.2.5-1 are the signalling control plane procedures for the MCVideo server initiating termination of an ongoing MCVideo ad hoc group call.
Pre-condition:
  • The MCVideo client 1 and MCVideo client 2 belong to primary MC system. The MCVideo client 3 belongs to partner MC system.
Reproduction of 3GPP TS 23.281, Fig. 7.19.3.2.5-1: Ad hoc group call release
Figure 7.19.3.2.5-1: Ad hoc group call release
Up
Step 1.
The MCVideo users on MCVideo client 1, client 2 and client 3 are already part of the ongoing ad hoc group call (e.g. as a result of ad hoc group call setup as specified in clause 7.19.3.2.4).
Step 2.
The MCVideo server would like to release the ad hoc group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCVideo group members are not present.
Step 3.
The MCVideo server identifies the participants of the ongoing ad hoc group call and generates ad hoc group call release request to release ongoing session.
Step 4.
The MCVideo server sends a ad hoc group call release request via SIP core towards each participant of the ongoing group call. If the participants belong to partner MC system, then ad hoc group call release request is routed to the MCVideo clients of the partner MC system via the partner MCVideo server.
Step 5.
The MCVideo users are notified about the release of the ad hoc group call.
Step 6.
The MCVideo client(s) receiving ad hoc group call release request, send acknowledgement towards the MCVideo server by sending a ad hoc group call release response.
Step 7.
The MCVideo client 1, client 2 and client 3 have successfully released the transmission control and media plane resources associated with the ad hoc group call that is terminated. The MCVideo servers remove the ad hoc group information from the dynamic data held in the MCVideo servers and the ad hoc group ceases to exist, otherwise if the ad hoc group call follows an ad hoc group emergency alert the MCVideo servers keep the dynamic data and the ad hoc group continues to exist.
Up
7.19.3.2.6  Modification of ad hoc group call participants by an authorized user  p. 209
Figure 7.19.3.2.6-1 below illustrates the MCVideo user modifying the ad hoc group call participants procedure involving multiple MCVideo systems.
Pre-conditions:
  1. An MCVideo ad hoc group call is already in progress and the participants list provided by the originating MCVideo user while initiating the MCVideo ad hoc group call.
  2. The participants of the MCVideo ad hoc group call belongs to the multiple MCVideo system.
  3. The MCVideo user at MCVideo client 1 determines that the MCVideo client 3 needs to be invited to on-going ad hoc group call and MCVideo client 2 needs to be removed from the on-going ad hoc group call from the primary MCVideo system.
  4. The MCVideo user at MCVideo client 1 determines that the MCVideo client 5 needs to be invited to on-going ad hoc group call and MCVideo client 4 needs to be removed from the on-going ad hoc group call from the partner MCVideo system.
Reproduction of 3GPP TS 23.281, Fig. 7.19.3.2.6-1: Modification of ad hoc group call participants by an authorized user
Figure 7.19.3.2.6-1: Modification of ad hoc group call participants by an authorized user
Up
Step 1.
The MCVideo client 1 sends the modify ad hoc group call participants request to the MCVideo server 1 to remove both MCVideo client 2 and MCVideo client 4 from the on-going ad hoc group call and to add both MCVideo client 3 and MCVideo client 5 into on-going ad hoc group call.
Step 2.
The MCVideo server 1 verifies whether the MCVideo client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group call.
Step 3.
The MCVideo server 1 sends modify ad hoc group call participants response to the MCVideo client 1.
Step 4.
The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 3 from the primary MC system be invited to an on-going ad hoc group call and successfully added to the call according to the procedure defined in clause 7.19.3.1.4.
Step 5.
The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 2 from the primary MC system be removed from the on-going ad hoc group call and successfully removed from call according to the procedure defined in clause 7.19.3.1.4.
Step 6.
The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 5 from the partner MC system be invited to an on-going ad hoc group call. The MCVideo server 1 sends the ad hoc group call request to the MCVideo client 5.
Step 7.
The MCVideo client 5 notifies the user about the incoming ad hoc group call.
Step 8.
The MCVideo client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCVideo server 1.
Step 9.
The on-going ad hoc group call is updated by adding MCVideo client 5 which is based on the modify participant list provided by the MCVideo client 1.
Step 10.
The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 4 from the partner MC system be removed from the on-going ad hoc group call. The MCVideo server 1 sends the ad hoc group call leave request to the MCVideo client 4.
Step 11.
The MCVideo client 4 notifies the user of the ad hoc group call leave request.
Step 12.
The MCVideo client 4 sends the ad hoc group call leave response to the MCVideo server 1.
Step 13.
The on-going ad hoc group call is updated by removing MCVideo client 4, which is based on the modify participant list provided by the MCVideo client 1.
Step 14.
The MCVideo server 1 may notify the initiating MCVideo user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the ad hoc group call.
Step 15.
The MCVideo server 1 may notify the authorized participants about the change in the participants list of on-going ad hoc group call.
Up
7.19.3.2.7  Modification of ad hoc group call criteria by an authorized user |R19|  p. 211
Figure 7.19.3.2.7-1 illustrates the modification of ad hoc group call criteria procedure by the initiator of the ad hoc group call between multiple MC systems.
Preconditions:
  • The MCVideo user at the MCVideo client 1 is authorized to modify the criteria.
  • The MCVideo server A and MCVideo server B are aware of the criteria related to the ongoing ad hoc group call.
  • MC system A and MC system B are interconnected.
Reproduction of 3GPP TS 23.281, Fig. 7.19.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group call between multiple MC systems
Figure 7.19.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group call between multiple MC systems
Up
Step 1.
An ad hoc group call has been established based on criteria sent by an authorized MCVideo client upon initiating the ad hoc group call.
Step 2.
The MCVideo user at the MCVideo client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group call participants.
Step 3a/b.
The MCVideo server A receives the modify ad hoc group call criteria request and forwards the request to MCVideo server B at MC system B.
Step 4a/b.
The MCVideo server A receives the ad hoc group call criteria modify response and forwards the response to MCVideo client 1 in MC system A.
Step 5.
MCVideo server B detects that MCVideo client 3 meets the criteria for the ongoing ad hoc group call initiated at MC system A.
Step 5a.
MCVideo server B sends an ad hoc group call add user notification message towards MCVideo server A.
Step 5b.
MCVideo server A sends an ad hoc group call request towards MCVideo client 3.
Step 5c.
The MCVideo user 3 is notified of entering an ongoing ad hoc group call.
Step 5d.
MCVideo client 3 sends an ad hoc group call response towards MCVideo server A.
Step 5e.
MCVideo server B sends an ad hoc group call remove user notification message towards MCVideo server A.
Step 5f.
MCVideo server A sends an ad hoc group call leave request towards MCVideo client 4.
Step 5g.
The MCVideo user 4 is notified of leaving an ongoing ad hoc group call.
Step 5h.
MCVideo client 4 sends an ad hoc group call leave response towards MCVideo server A.
Step 6.
The MCVideo server A may notify the authorised MCVideo user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the authorised MCVideo user by the MCVideo server A more than once during the call when MCVideo users join or leave the ad hoc group call.
Step 7.
The MCVideo server A adds MCVideo client 3 to the ad hoc group call and removes MCVideo client 4 from the ad hoc group call.
The MCVideo servers continuously check whether other MCVideo clients meet or if participating MCVideo clients no longer meet the criteria for the ad hoc group call.
Up

Up   Top   ToC