Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.281  Word version:  17.6.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.2.3…   7.2.3…   7.3…   7.4…   7.4.3…   7.5…   7.6…   7.7…   7.7.1.3…   7.7.2…   7.8…   7.11…   7.17…   A…

 

7.2.2.3  Private call within one MC system

7.2.2.3.1  Private call setup in automatic commencement mode
The procedure describes the scenario where an MCVideo user is initiating an MCVideo private call for communicating with another MCVideo user, with or without transmission control enabled, in an automatic commencement mode.
Procedures in Figure 7.2.2.3.1-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user.
Pre-conditions:
  1. MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service.
  2. The calling MCVideo user has selected automatic commencement mode for the call; or
  3. The called MCVideo client is set to automatic commencement mode.
  4. Optionally, the MCVideo client 1 may have a functional alias activated to be used.
  5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
(not reproduced yet)
Figure 7.2.2.3.1-1: Private call setup in automatic commencement mode- MCVideo users in the same MC system
Up
Step 1.
User at MCVideo client 1 would like to initiate an MCVideo private call for the chosen MCVideo user. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call.
Step 2.
MCVideo client 1 sends an MCVideo private call request towards the MCVideo server (via SIP core) using a service identifier as defined in TS 23.228 for MCVideo, for establishing a private call with the chosen MCVideo user. The MCVideo private call request contains the MCVideo ID or the functional alias of invited user, an SDP offer containing one or more media types. The MCVideo client 1 may include a Requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user.
Step 3.
MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call, and that MCVideo user at MCVideo client 2 is authorized to receive the private call. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCVideo private call request contains a functional alias instead of an MCVideo ID as called party, the MCVideo server shall resolve the functional alias to the corresponding MCVideo ID(s) for which the functional alias is active. The MCVideo server shall also check whether MCVideo client 1 is allowed to use the functional alias of MCVideo client 2 to setup a private call and whether MCVideo client 2 is allowed to receive a private call from MCVideo client 1 using the functional alias. If the MCVideo private call request requested automatic commencement mode then the MCVideo server also checks whether the MCVideo user at MCVideo client 1 is authorized to initiate a private call in automatic commencement mode.
Step 4a.
If the MCVideo private call request contains only the functional alias instead of an MCVideo ID for the called party, the MCVideo server responds with a functional alias resolution response message that contains the resolved MCVideo ID back to MCVideo client 1.
Step 4b.
If the MCVideo server replies with a MCVideo functional alias resolution response message, the MCVideo client 1 sends a new MCVideo private call request towards the resolved MCVideo ID.
Step 5.
MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
Step 6.
If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MC service ID and, if available the functional alias of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE.
Step 7.
The receiving MCVideo client 2 notifies the user about the incoming private call. If the functional alias of the calling user is included, it is displayed.
Step 8.
The receiving MCVideo client 2 accepts the private call automatically, and an MCVideo private call response is sent to the MCVideo server (via SIP core).
Step 9.
Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request, the MCVideo server informs the MCVideo client 1 about successful call establishment.
Step 10.
MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for communication and both users can transmit media.
Up
7.2.2.3.2  Private call setup in manual commencement modeWord‑p. 70
7.2.2.3.2.1  Description
Figure 7.2.2.3.2.2-1 describes the basic procedure for the MCVideo client initiating an MCVideo private call that uses manual commencement mode. The flow may use a transmit media request in the MCVideo private call request indicating that the originator will be granted permission to transmit when the call starts and eliminates the need for a separate initial transmit media request message during media plane establishment. Alternatively, the call initiation may be sent without the transmit media request, which allows the called party to transmit media request first.
Up
7.2.2.3.2.2  Procedure
Both clients are served by the primary MC service provider in Figure 7.2.2.3.2.2-1.
Pre-conditions:
  1. MCVideo client 1 and MCVideo client 2 are both registered and their respective users, MCVideo user 1 and MCVideo user 2, are authenticated and authorized to use the MCVideo service.
  2. The calling MCVideo user has selected manual commencement mode or has not specified a commencement mode for the call; and
  3. The called MCVideo client is set to manual commencement mode.
  4. Optionally, the MCVideo client 1 may have a functional alias activated to be used.
  5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
(not reproduced yet)
Figure 7.2.2.3.2.2-1: MCVideo private call in manual commencement mode- MCVideo users in the same MC system
Up
Step 1.
MCVideo user at MCVideo client 1 would like to initiate an MCVideo private call for the selected MCVideo user. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call.
Step 2.
MCVideo client 1 sends an MCVideo private call request addressed to the MC service ID of MCVideo user 2 using an MCVideo service identifier as defined in TS 23.228 (possible for the SIP core to route the request to the MCVideo server). The MCVideo private call request contains the MC service ID or the functional alias of invited user and an SDP offer containing one or more media types. The MCVideo client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user.
Step 3.
The MCVideo server confirms that both MCVideo users are authorized for the private call. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCVideo private call request contains a functional alias instead of an MCVideo ID as called party, the MCVideo server shall resolve the functional alias to the corresponding MCVideo ID(s) for which the functional alias is active. The MCVideo server shall also check whether MCVideo client 1 is allowed to use the functional alias of MCVideo client 2 to setup a private call and whether MCVideo client 2 is allowed to receive a private call from MCVideo client 1 using the functional alias. The MCVideo server checks the commencement mode setting of the called MCVideo client and also checks whether the MCVideo user at MCVideo client 1 is authorized to initiate a call in manual commencement mode.
Step 4a.
If the MCVideo private call request contains only the functional alias instead of an MCVideo ID for the called party, the MCVideo server responds with a functional alias resolution response message that contains the resolved MCVideo ID back to MCVideo client 1.
Step 4b.
If the MCVideo server provided the corresponding MCVideo ID, the MCVideo client 1 sends a new MCVideo private call request containing the resolved MCVideo ID.
Step 5.
The MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request and sends an MCVideo private call request for the call to MCVideo client 2, including the MC service ID, and, if available the functional alias of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE.
Step 6.
MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
Step 7a.
The MCVideo user is alerted. MCVideo client 2 sends an MCVideo ringing to the MCVideo server.
Step 7b.
The MCVideo server sends an MCVideo ringing to MCVideo client 1, indicating that MCVideo client 2 is being alerted. If the functional alias of the calling user is included, it is displayed.
Step 8.
MCVideo user 2 is notified and has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface).
Step 9.
The MCVideo client 2 sends an MCVideo private call response to the MCVideo server. If MCVideo user 2 has not accepted the incoming call, the MCVideo client 2 sends a call failure response to the MCVideo server without adding reason for call failure.
Step 10.
The MCVideo server sends an MCVideo private call response to MCVideo client 1 indicating that MCVideo user 2 has accepted the call, including the accepted media parameters.
Step 11.
The media plane and transmission control for communication is established.
Up
7.2.2.3.3  Private call releaseWord‑p. 72
7.2.2.3.3.1  Client initiated
The procedure describes the scenario where an MCVideo client is requesting to release an ongoing MCVideo private call (with or without transmission control) and the call established in either of the two commencement modes (manual or automatic).
Procedures in Figure 7.2.2.3.3.1-1 are the basic signalling control plane procedures for the MCVideo client initiating the release of an ongoing MCVideo private call.
Pre-condition:
  1. It is assumed that MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service and are involved in private call as described in subclause 7.2.2.3.1 and subclause 7.2.2.3.2.
(not reproduced yet)
Figure 7.2.2.3.3.1-1: Private call release - client initiated
Up
Step 1.
User at MCVideo client 1 would like to release an ongoing MCVideo private call with MCVideo client 2.
Step 2.
MCVideo client 1 sends an MCVideo call end request towards the MCVideo server (via SIP core), for tearing down the private call with the other client.
Step 3.
MCVideo server sends the corresponding MCVideo call end request towards the MCVideo client specified in the original MCVideo call end request.
Step 4.
MCVideo user is notified about the release of the private call.
Step 5.
The receiving MCVideo client 2 acknowledges the MCVideo call end request with a MCVideo call end response.
Step 6.
After receiving the MCVideo call end response from MCVideo client 2, the MCVideo server generates an MCVideo call end response for the MCVideo client 1's MCVideo call end request.
Step 7.
MCVideo clients release all the media plane resources used for the private call. Further, if the private call was established with transmission control, transmission control resources are released.
Up
7.2.2.3.3.2  Server initiatedWord‑p. 73
The procedure describes the scenario where an MCVideo server is terminating an ongoing MCVideo private call and the call established in either of the two commencement modes (manual or automatic), upon conditions to terminate call e.g., MCVideo administrator configured maximum duration for MCVideo private calls has expired or timed out due to MCVideo private call without transmission/reception.
Procedures in Figure 7.2.2.3.3.2-1 are the basic signalling control plane procedures for the MCVideo server initiating termination of an ongoing MCVideo private call.
Pre-condition:
  1. It is assumed that MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service and are involved in private call established either in manual or automatic commencement mode.
(not reproduced yet)
Figure 7.2.2.3.3.2-1: End private call - server initiated
Up
Step 1.
Upon conditions to terminate call e.g., MCVideo administrator configured maximum duration for MCVideo private calls has expired or timed out due to MCVideo private call without transmission/reception, the MCVideo server decides to initiate termination of an ongoing MCVideo private call between MCVideo client 1 and MCVideo client 2.
Step 2.
MCVideo server sends an MCVideo call end request towards the MCVideo clients 1 and 2 (via SIP core), for tearing down the private call between them.
Step 3.
MCVideo users at client 1 and client 2 are notified about the termination of the private call.
Step 4.
The MCVideo call end request receiving MCVideo clients 1 and 2 acknowledge the request with MCVideo call end response.
Step 5.
MCVideo clients release all the media plane resources used for the private call. Further, if the private call was established with transmission control, transmission control resources are released.
Up

7.2.2.4  MCVideo emergency private call |R15|Word‑p. 74

7.2.2.4.1  MCVideo emergency private call commencement
This procedure describes the case where an authorized MCVideo user is initiating an MCVideo emergency private call with unicast signalling for communicating with another MCVideo user. An MCVideo client in the MCVideo emergency state gains elevated access privilege for all of the MCVideo user's mission critical applications.
Procedures in Figure 7.2.2.4.1-1 are the procedures for the MCVideo client initiating establishment of an MCVideo emergency private call.
Pre-conditions:
  1. Both members of the MCVideo private call belong to the same MCVideo system.
  2. The initiating MCVideo client 1 has been configured to send an MCVideo emergency alert prior to initiating an MCVideo emergency private call.
  3. Optionally, the MCVideo client 1 may have a functional alias activated to be used.
  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.
(not reproduced yet)
Figure 7.2.2.4.1-1: MCVideo emergency private call
Up
Step 1.
The user at the MCVideo client 1 initiates an MCVideo emergency private call. MCVideo client 1 sets its MCVideo emergency state. MCVideo client 1 retains the MCVideo emergency state until explicitly cancelled by the user of MCVideo client 1.
Step 2.
MCVideo client 1 sends an MCVideo emergency private call request towards the MCVideo server. The request contains an indication of the MCVideo emergency. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo emergency private call. The MCVideo server verifies whether the provided functional alias can be used. The MCVideo server records the identity of the MCVideo user that initiated the MCVideo emergency private call until the MCVideo emergency is cancelled. If the MCVideo client is configured to send an MCVideo emergency alert when initiating an MCVideo emergency private call, the request also contains an indication that an MCVideo emergency alert is to be initiated.
Step 3.
MCVideo server sends the MCVideo emergency private call request towards the target MCVideo client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCVideo emergency alert if the request from the originator indicated MCVideo emergency alert. If available the request contains the functional alias of the calling MCVideo user 1.
Step 4.
The MCVideo user on MCVideo client 2 is notified of the incoming MCVideo emergency private call. If the functional alias of the calling user is included it is displayed.
Step 5.
The receiving MCVideo client acknowledges the MCVideo emergency private call request to the MCVideo server via a MCVideo emergency private call response.
Step 6.
The MCVideo server adjusts the priority of the underlying bearer.
Step 7.
The MCVideo server informs MCVideo client 1 about the successful MCVideo emergency private call establishment via a MCVideo emergency private call response.
Step 8.
MCVideo client 1 and MCVideo client 2 establish the media plane and transmission control for video communication.
Up
7.2.2.4.2  MCVideo private call emergency upgradeWord‑p. 76
This procedure describes the case where an authorized MCVideo user is upgrading a private call to an MCVideo emergency private call while the private call is already in progress.
Procedures in Figure 7.2.2.4.2-1 are the signalling procedures for the MCVideo client upgrading a private call to an MCVideo emergency private call.
Pre-conditions:
  1. Both members of the private call belong to the same MCVideo system.
  2. A private call is already in progress.
(not reproduced yet)
Figure 7.2.2.4.2-1: MCVideo private call upgrade
Up
Step 1.
The MCVideo user at MCVideo client 1 initiates an emergency. MCVideo client 1 sets its MCVideo emergency state. MCVideo client 1 retains the MCVideo emergency state until explicitly cancelled by the user of MCVideo client 1.
Step 2.
MCVideo client 1 requests the MCVideo server to upgrade the private call to in-progress emergency by sending an MCVideo emergency private call request. If configured to send an MCVideo alert when initiating an MCVideo emergency upgrade, the request also contains an indication that an MCVideo alert is to be initiated. The request may contain an indication of an implicit transmit media request.
Step 3.
MCVideo server sends the MCVideo emergency request towards MCVideo client 2, the MCVideo client of the other participant.
Step 4.
The MCVideo user of MCVideo client 2 is notified of the in-progress emergency of the MCVideo emergency private call.
Step 5.
The receiving MCVideo client acknowledges the MCVideo emergency request to the MCVideo server.
Step 6.
The MCVideo server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends.
Step 7.
The MCVideo server confirms the upgrade request to MCVideo client 1. If the MCVideo emergency request contained an implicit transmit media request, the MCVideo emergency private call response message contains the result of the implicit transmit media request.
Step 8.
MCVideo client 1 and MCVideo client 2 continue with the private call, which has been transformed into an MCVideo emergency private call. MCVideo client 1 can override MCVideo client 2 unless MCVideo client 2 is also in the MCVideo emergency state.
Up

Up   Top   ToC