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.1.2.3.1.2 Chat group call  7.1.2.3.1.2.1 General  7.1.2.3.1.2.2 Chat group call setup  7.1.2.3.1.2.3 Release chat group call  7.1.2.3.1.2.5 Late entry chat group call, newly joined group member  7.1.2.3.1.2.6 Late entry chat group call, MCVideo client coming back from out of coverage 
...

 

7.1.2.3.1.2  Chat group call  p. 34
7.1.2.3.1.2.1  General  p. 34
In a chat group (restricted) call model, the MCVideo user individually joins a group call without being explicitly invited by the MCVideo server. The establishment of a chat group (restricted) call does not result in other group members being invited.
Figure 7.1.2.3.1.2.2-1 describes the basic procedure for the MCVideo client initiating an MCVideo group call which uses the chat group (restricted) call model. The chat group (restricted) call model can be used to realize the video conferencing service where only users that have been configured as participants for the video conferencing group are allowed to join the group communications for the given group.
Chat group join mechanism:
  • Each MCVideo client sends a group join request when the MCVideo user wants to participate in the group communication for the group. (This message does not impact the MCVideo user's membership in the group; the MCVideo server will verify that the MCVideo user is an authorized member of the group.)
  • The group join request may include a transmit media request. If the group join request includes a request to transmit media it may also include location information. It is assumed that the group join request will be delivered from MCVideo client to MCVideo server using SIP.
  • If location information was included in the group join request, the MCVideo server checks the privacy policy of the MCVideo user to decide if the location information of MCVideo client 1 can be provided to other users on the call.
  • The group join request is used to indicate to the MCVideo server that the MCVideo user associated with the given MCVideo client wishes to participate (begin to receive notifications for media transmissions) from the group.
  • The group join request shall cause the MCVideo server to generate an implicit affiliation for the MCVideo user to the group, if the user is not already affiliated to the group.
  • The group join request contains the information needed to negotiate media parameters (on demand) or to associate a pre-established session between MCVideo server and MCVideo client for the group call. The group join request can take the form of a SIP invite.
  • A selected functional alias is not changed by a MCVideo client during the whole participation within a chat group call, i.e. a MCVideo client uses the same functional alias selected when joining the chat group call until the chat group call is released or the MCVideo client leaves the chat group call.
Subsequent participation in a group call when the group is using the chat model:
  • Once an MCVideo client successfully joins a group call which is using the chat model, the MCVideo client connects to the media plane for the media transmission if the media transmission is currently ongoing.
  • If the MCVideo group call is not currently ongoing (i.e.: when MCVideo clients on the group call are not sending or receiving media, and the time out between transmission control exchanges has expired) then the newly joined MCVideo client will only have pre-established its media parameters for the call.
  • If the newly joined MCVideo user wishes to transmit media to the other joined users of the group using the chat model, then the MCVideo client shall use a normal transmission control procedure for transmitting the media.
  • Subsequent group call media transmissions are controlled using transmission control signalling.
  • The MCVideo server may tear down the media plane between successive group calls using the chat model, or the MCVideo server may allow the media plane to remain up between successive group calls using the chat model depending on resources.
Leaving and releasing a chat group:
  • When a user wants to leave a chat group call, the client shall send a group call leave request to the server and release the media plane.
  • The server can release a chat group call by sending a group call release to all joined clients. A server initiated release also releases the media plane for all joined clients.
Up
7.1.2.3.1.2.2  Chat group call setup  p. 35
MCVideo client 1, client 2, and client 3 are served by the home MCVideo service provider in Figure 7.1.2.3.1.2.2-1.
Pre-conditions:
  1. MCVideo user 2 and MCVideo user 3 have previously joined (affiliated) to the group call. MCVideo client 1, client 2, and client 3 are registered and all users (MCVideo user 1, user 2, and user 3) have been authenticated and authorized to use the MCVideo service.
  2. MCVideo client 1, MCVideo client 2 and MCVideo client 3 may have activated functional alias(es) configured to be used during the group call communication. No call is currently in progress for the group.
  3. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
  4. The MCVideo user on MCVideo client 1 may have bound a functional alias to the MCVideo group ID (TS 23.280).
Reproduction of 3GPP TS 23.281, Fig. 7.1.2.3.1.2.2-1: MCVideo chat group call
Figure 7.1.2.3.1.2.2-1: MCVideo chat group call
Up
Step 1.
MCVideo user 1 indicates to join the group communication for the group. This may include a transmit media request.
Step 1a.
MCVideo client 1 sends a group join request with the MCVideo group ID of the desired group. It contains the MCVideo user's MCVideo ID and the MCVideo client media parameters. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo group join request. If there is a request for media transmission, then the group join request contains an indication of an implicit transmit media request. If the group join request includes an implicit transmit media request it may also include location information.
Step 1b.
The MCVideo server receives the group join request. MCVideo server generates an implicit affiliation (if the MCVideo user is not already affiliated to the group) and verifies that MCVideo user 1 is authorized to affiliate to the group by following the affiliation procedure for MCVideo. If a functional alias is present, the MCVideo server checks whether it is allowed to be used and if it has been activated for the user.
If the functional alias is provided only in the group join request, or via binding, the MCVideo server proceeds with the value that is provided. If the functional alias is provided in both the group join request and via binding, it is up to the MCVideo server implementation to determine a value for the functional alias to be used.
If location information was included in the group join request, the MCVideo server checks the privacy policy of the MCVideo user to decide if the location information of MCVideo client 1 can be provided to other users on the call.
Step 1c.
The MCVideo server replies with a group join response indicating the acceptance of the group join request and also returns the MCVideo server selected media parameters for the group call in the group join response.
Step 2.
If MCVideo user 1 requests to transmit media by sending transmit media request to MCVideo server, the MCVideo server establishes the media plane (if not already established) for the call.
Step 3.
Transmission control will continue to be used by the transmission control participants associated with MCVideo client 1, MCVideo client 2 and MCVideo client 3 for the duration of the call. .If present, the functional alias of MCVideo client 1, MCVideo client 2 and MCVideo client 3 are displayed where appropriate.
Up
7.1.2.3.1.2.3  Release chat group call  p. 35
The procedure describes the case where the MCVideo server releases an ongoing MCVideo group call for all the participants of that group call, since at least one of the conditions for release are met e.g. due to chat duration expiry, last participant leaving or initiator leaving.
Procedures in Figure 7.1.2.3.1.2.3-1 are the procedures for the MCVideo server initiating the release of an ongoing MCVideo group call.
The following precondition applies:
  • A group call is ongoing between MCVideo clients 1, 2 and 3
Reproduction of 3GPP TS 23.281, Fig. 7.1.2.3.1.2.3-1: Release chat group call
Figure 7.1.2.3.1.2.3-1: Release chat group call
Up
Step 1.
MCVideo server would like to release the MCVideo group call which is ongoing e.g., due to chat duration expiry, last participant leaving, or initiator leaving.
Step 2.
MCVideo server identifies the participants of the ongoing group call and generates group call release request to release the ongoing session.
Step 3.
MCVideo server sends a group call release request towards each participant of the ongoing group call.
Step 4.
MCVideo users are notified about the release of the group call.
Step 5.
Optionally the MCVideo client(s) receiving group call release request, may send a group call release response to the MCVideo server.
Step 6.
MCVideo client 1, client 2 and client 3 release the transmission control and media plane resources associated with the group call that is released. Successful release of the group call does not affect the status of affiliation of any of the clients.
Up
7.1.2.3.1.2.4  Void
7.1.2.3.1.2.5  Late entry chat group call, newly joined group member  p. 38
Procedures in Figure 7.1.2.3.1.2.5-1 are those for a group member entering an ongoing MCVideo group call, i.e. performing a late entry.
Pre-conditions:
  1. MCVideo user 2 and MCVideo user 3 have previously joined to the group. MCVideo client 1, client 2, and client 3 are registered and all users (MCVideo user 1, user 2, and user 3) have been authenticated and authorized to use the MCVideo service.
  2. MCVideo user 1 indicates to join the group communication for the group.
  3. MCVideo users using MCVideo client 1 to MCVideo client n may have activated functional alias(es) configured to be used during the group call communication.
  4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
  5. The MCVideo user on MCVideo client 1 may have bound a functional alias to the MCVideo group ID (TS 23.280).
Reproduction of 3GPP TS 23.281, Fig. 7.1.2.3.1.2.5-1: Late entry of a newly joined group member
Figure 7.1.2.3.1.2.5-1: Late entry of a newly joined group member
Up
Step 1.
MCVideo client 1 sends a group join request with the MCVideo group ID of the desired group. It contains the MCVideo user's MCVideo ID and the MCVideo client media parameters. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo group join request. If there is a request to transmit, then the group join request contains an indication of an implicit transmit media request.
Step 2.
The MCVideo server receives the group join request. MCVideo server generates an implicit affiliation (if the MCVideo user is not already affiliated to the group) and verifies that MCVideo user 1 is authorized to affiliate to the group. If a functional alias is present, the MCVideo server checks whether it is allowed to be used and if it has been activated for the user.
If the functional alias is provided only in the group join request, or via binding, the MCVideo server proceeds with the value that is provided. If the functional alias is provided in both the group join request and via binding, it is up to the MCVideo server implementation to determine a value for the functional alias to be used.
Step 3.
The MCVideo server replies with a group join response indicating the acceptance of the group join request.
Step 4.
Media plane between MCVideo client 1 and MCVideo server is established using media plane control signalling.
Step 5.
MCVideo users at MCVideo client 2 and MCVideo client 3 may be notified about the MCVideo client 1 joining the group call, and the functional alias of MCVideo client 1 may be displayed.
Step 6.
The MCVideo server may send (6a) Media transmission notification to MCVideo client 1, indicating the current transmitter. Alternatively the MCVideo server may send (6b) Transmit media granted, (6b) Transmit media rejected or (6d) Queue position info.
Step 7.
Transmission control will continue to be used by the transmission control participants associated with MCVideo client 1, MCVideo client 2 and MCVideo client 3. If present, the functional alias of MCVideo client 1, MCVideo client 2 and MCVideo client 3 are displayed where appropriate.
Up
7.1.2.3.1.2.6  Late entry chat group call, MCVideo client coming back from out of coverage  p. 39
Procedures in Figure 7.1.2.3.1.2.6-1 are those for an MCVideo client coming back from out of coverage during an ongoing MCVideo group call.
Pre-conditions:
  1. MCVideo users using MCVideo client 1, MCVideo client 2 and MCVideo client 3 are in an ongoing group call when MCVideo client1 goes out of radio coverage.
  2. MCVideo client1 returns from out of coverage while the group call is still ongoing.
  3. MCVideo users using MCVideo client 1 to MCVideo client n may have activated functional alias(es) configured to be used during the group call communication.
  4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Reproduction of 3GPP TS 23.281, Fig. 7.1.2.3.1.2.6-1: Late entry of an MCVideo client returning from out of coverage
Figure 7.1.2.3.1.2.6-1: Late entry of an MCVideo client returning from out of coverage
Up
Step 1.
MCVideo client 1 or MCVideo server detects that MCVideo client 1 has returned from out of coverage.
Step 2.
Media plane between MCVideo client 1 and MCVideo server is re-established using media plane control signalling.
Step 3.
The MCVideo server may send (3a) Media transmission notification to MCVideo client 1, indicating the current transmitter. Alternatively, the MCVideo server may send (3b) Transmit media granted, (3c) Transmit media rejected or (3d) Queue position info.
Step 4.
MCVideo users at MCVideo client 2 and MCVideo client 3 may be notified about the MCVideo client 1 returning to the group call, and the functional alias of MCVideo client 1 may be displayed.
Step 5.
Transmission control will continue to be used by the transmission control participants associated with MCVideo client 1, MCVideo client 2 and MCVideo client 3. If present, the functional alias of MCVideo client 1, MCVideo client 2 and MCVideo client 3 are displayed where appropriate.
Up

Up   Top   ToC