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

Top   Top   Up   Prev   Next
1…   5…   6…   7…   7.1.2.3…   7.1.2.3.1.2…   7.1.2.3.2…   7.1.2.4…   7.1.2.5.2…   7.1.3…   7.2…   7.2.2.3…   7.2.2.4…   7.2.3…   7.3…   7.4…   7.4.3…   7.5…   7.5.2.3…   7.6…   7.7…   7.7.1.3…   7.7.1.3.2A…   7.7.1.3.4…   7.7.1.3.6…   7.7.2…   7.7.2.7…   7.7.2.9…   7.8…   7.11…   7.17…   7.19…   7.19.2.8…   7.19.3…   7.19.3.1.4…   7.19.3.2…   7.19.3.2.3…   7.19.3.2.6…   A… 
7.19.3.2 Ad hoc group call involving multiple MC systems  7.19.3.2.1 Ad hoc group call setup - Participants list determined by the MCVideo server  7.19.3.2.2 Modification of ad hoc group call participants by the MCVideo server 
...

 

7.19.3.2  Ad hoc group call involving multiple MC systems  p. 200

7.19.3.2.1  Ad hoc group call setup - Participants list determined by the MCVideo server  p. 200
Figure 7.19.3.2.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user wherein the list of participants is determined by the MCVideo server based on the criteria received from the MCVideo client and determined MCVideo users are from multiple MCVideo systems.
Pre-conditions:
  1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system share their users' information to the primary MC system.
  2. The authorized MCVideo user/dispatcher belongs to the primary MC system.
  3. The MCVideo server 1 of the primary MC system is where the authorized MCVideo user/dispatcher creates the ad hoc group.
  4. Some users of the ad hoc group belong to MCVideo server 2 of the partner MC systems.
  5. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCVideo client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
Reproduction of 3GPP TS 23.281, Fig. 7.19.3.2.1-1: Ad hoc group call setup involving multiple MCVideo systems
Figure 7.19.3.2.1-1: Ad hoc group call setup involving multiple MCVideo systems
Up
Step 1-3.
Same as described in subclause 7.19.3.1.3.
Step 4.
The MCVideo server 1 determines the list of participants from the primary MC system and determines the partner MC system to be involved in the ad hoc group call based on the information present in the information element Criteria for determining the participants. This information element carries the criteria, indicator identifying pre-defined criteria, or a combination of both.
Step 5.
If the MCVideo server 1 needs to involve the partner system based on the agreement and based on the criteria for determining the participants list, it sends the ad hoc group call get userlist request to the MCVideo server 2. This request carries the criteria specified in the step 1.
Step 6.
MCVideo server 2 evaluates the criteria and determines the participants satisfying the criteria (i.e. MCVideo client 3 and MCVideo client 4) and sends the response containing the list of MCVideo users satisfying the criteria. The partner MCVideo server may apply local policies if any while determining the participants satisfying the criteria.
Step 7.
The MCVideo server 1 compiles the list of participants to be invited for the ad hoc group call including the participants from both primary and partner MC system.
Step 8a-8b.
The MCVideo server 1 sends the ad hoc group call request towards the MCVideo client 3 and MCVideo client 4. While sending the ad hoc group call request, the MCVideo server shall remove the information elements that are not required to be conveyed to the target MCVideo clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCVideo server 1 considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
Step 9.
The MCVideo server 1 sends the ad hoc group call requests towards the MCVideo client 2. While sending the ad hoc group call request, the MCVideo server shall remove the information elements that are not required to be conveyed to the target MCVideo clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCVideo server 1 considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
Step 10a-10c.
The receiving MCVideo clients are notified about the incoming ad hoc group call.
Step 11.
The MCVideo client 2 accept the ad hoc group call request and send ad hoc group call response to the MCVideo server 1.
Step 12.
The MCVideo client 3 accepts the ad hoc group call request, and sends ad hoc group call response to the MCVideo server 1.
Step 13.
The MCVideo client 4 accepts the ad hoc group call request, and sends ad hoc group call response to the MCVideo server 1.
Step 14.
The MCVideo server 1 sends the ad hoc group call response to MCVideo client 1 through the signalling path to inform about successful call establishment.
Step 15.
The MCVideo server 1 may notify the initiating MCVideo user of all MCVideo users who acknowledged the ad hoc group call request and joined the ad hoc group call. The MCVideo server 1 more than once during the call may send this notification to the initiating MCVideo user whenever an MCVideo user joins or leaves the MCVideo ad hoc group call. If the authorized users (not shown in Figure) are configured to receive the participants information of ad hoc group call, the MCVideo server provides ad hoc group call notify about all MCVideo users who acknowledged the ad hoc group call request and joined the ad hoc group call, and when MCVideo users join or leave the MCVideo ad hoc group call.
Step 16.
The MCVideo client 1, MCVideo client 2, MCVideo client 3 and MCVideo client 4 establish media plane and transmission control resources.
Up
7.19.3.2.2  Modification of ad hoc group call participants by the MCVideo server  p. 202
Figure 7.19.3.2.2-1 below illustrates the MCVideo server modifying the ad hoc group call participants procedure involving multiple MCVideo systems.
Pre-conditions:
  1. The MCVideo user at MCVideo client 1 is authorized to initate ad hoc group call.
  2. The MCVideo server 1 of the primary and MCVideo server 2 of the partner MCVideo systems determined the participants for the ad hoc group call based on the criteria specified by the MCVideo client 1 while initiating the ad hoc group call.
  3. The MCVideo server 1 of the primary and MCVideo server 2 of the partner MCVideo 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 call.
  4. The MCVideo server 1 of the primary MCVideo system detects that the MCVideo client 3 meets the criteria and MCVideo client 2 stops to meet the criteria specified by the MCVideo client 1.
  5. The MCVideo server 2 of the partner MCVideo system detects that the MCVideo client 5 meets the criteria and MCVideo client 4 stops to meet the criteria specified by the MCVideo client 1.
Reproduction of 3GPP TS 23.281, Fig. 7.19.3.2.2-1: Modification of ad hoc group call participants by the MCVideo server
Figure 7.19.3.2.2-1: Modification of ad hoc group call participants by the MCVideo server
Up
Step 1.
The ad hoc group call is established and on-going with the participants MCVideo client 1, MCVideo client 2, and MCVideo client 4. The participants list is determined by both primary and partner systems MCVideo server based on the criteria specified by the MCVideo client 1 while initiating the call.
Step 2.
The MCVideo server 1 detects that MCVideo client 3 now meets criteria and successfully added to call.
Step 3.
The MCVideo server 1 detects that MCVideo client 2 does not meet criteria any more and successfully removed from a call.
Step 4.
The MCVideo server 2 detects that the MCVideo client 5 meets the criteria specified by the MCVideo client 1.
Step 5.
The MCVideo server 2 sends the notification to MCVideo server 1 of the primary MCVideo system to add the MCVideo user at MCVideo client 5 to on-going ad hoc group call.
Step 6.
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 meets the criteria specified by the MCVideo client 1.
Step 10.
The MCVideo server 2 detects that the MCVideo client 4 is no more satisfying the criteria to be the participant of the ad hoc group call.
Step 11.
The MCVideo server 2 sends the notification to MCVideo server 1 of the primary MCVideo system to remove the MCVideo user at MCVideo client 4 from on-going ad hoc group call.
Step 12.
The MCVideo server 1 sends the ad hoc group call leave request to the MCVideo client 4 and removes it from the on-going ad hoc group call.
Step 13.
The MCVideo client 4 notifies the user of the ad hoc group call leave request.
Step 14.
The MCVideo client 4 sends the ad hoc group call leave response to the MCVideo server 1.
Step 15.
The on-going ad hoc group call is updated by removing MCVideo client 4, which no more meets the criteria specified by the MCVideo client 1.
Up

Up   Top   ToC