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.3.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.4 Video push  7.4.1 General  7.4.2 On-network video push  7.4.2.1 General  7.4.2.2 Information flows for on-network video push  7.4.2.2.1 Remote video push request  7.4.2.2.2 Remote video push response  7.4.2.2.3 Remote video push release request  7.4.2.2.4 MCVideo push to server request  7.4.2.2.5 MCVideo push to server response  7.4.2.2.6 MCVideo push to server complete request  7.4.2.2.7 MCVideo push to server complete response  7.4.2.3 One-to-one video push  7.4.2.3.1 General  7.4.2.3.2 One-to-one video push - call setup  7.4.2.3.3 One-to-one video push - call release  7.4.2.4 One-to-server video push  7.4.2.4.1 General  7.4.2.4.2 Procedure  7.4.2.5 Remotely initiated video push  7.4.2.5.1 General  7.4.2.5.2 Remotely initiated video push - call setup  7.4.2.5.3 Remotely initiated video push - call release by authorized user  7.4.2.6 Remotely initiated video push to group  7.4.2.6.1 General  7.4.2.6.2 Remotely initiated video push to group - call setup  7.4.2.6.3 Remotely initiated video push to group - call release by authorized user 
...

 

7.4  Video push  p. 95

7.4.1  General  p. 95

MCVideo push is enabled in both on-network and off-network mode.
For on-network MCVideo push is supported between MCVideo clients, or between a MCVideo client and a MCVideo server.
For off-network MCVideo push is supported between MCVideo clients only.

7.4.2  On-network video push  p. 95

7.4.2.1  General  p. 95

A MCVideo user triggers its MCVideo client to push a video to another MCVideo client or a MCVideo server.
A MCVideo user triggers its MCVideo client to trigger a remote video push, i.e. a second MCVideo client pushes a video to a third MCVideo client or to a MCVideo group.

7.4.2.2  Information flows for on-network video push  p. 95

The following information flows for private call specified in subclause 7.2.2.2 is used for on-network video push:
  • MCVideo private call request (MCVideo client - MCVideo server)
  • MCVideo private call request (MCVideo server - MCVideo client)
  • MCVideo private call response (MCVideo client - MCVideo server)
  • MCVideo private call response (MCVideo server - MCVideo client)
  • MCVideo call end request
7.4.2.2.1  Remote video push request  p. 95
Table 7.4.2.2.1-1 describes the information flow remote video push request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the call originating party
Functional aliasOThe functional alias of the originating party
MCVideo IDMThe MCVideo ID of the source party who should transmit media
MCVideo IDO (see Note)The MCVideo ID of the destination party who should receive media
MCVideo group IDO (see Note)The MCVideo group ID of the destination group whose affiliated group members should receive media
SDP offerOMedia parameters of MCVideo client.
Requested commencement modeOAn indication that is included if the user is requesting a particular commencement mode
Requested priorityOApplication priority level requested for this call
NOTE:
MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested.
Up
7.4.2.2.2  Remote video push response  p. 96
Table 7.4.2.2.2-1 describes the information flow remote video push request from the MCVideo server to the MCVideo client and from the MCVideo client to the MCVideo server.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the call originating party
MCVideo IDMThe MCVideo ID of the source party who should transmit media
MCVideo IDO (see Note)The MCVideo ID of the destination party who should receive media
MCVideo group IDO (see Note)The MCVideo group ID of the destination group whose affiliated group members should receive media
Acceptance confirmationOAn indication whether the user or group members have positively accepted the call.
SDP answerMMedia parameters selected
NOTE:
MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested.
Up
7.4.2.2.3  Remote video push release request  p. 96
Table 7.4.2.2.3-1 describes the information flow Remote video push release request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the call originating party
MCVideo IDMThe MCVideo ID of the source party who should transmit media
MCVideo IDO (see Note)The MCVideo ID of the destination party who should receive media
MCVideo group IDO (see Note)The MCVideo group ID of the destination group whose affiliated group members should receive media
NOTE:
MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested.
Up
7.4.2.2.4  MCVideo push to server request  p. 97
Table 7.4.2.2.4-1 describes the information flow MCVideo push to server request from the MCVideo client to the MCVideo server.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the calling party
Time limitORequested duration of the stream to be recorded
SDP offerMMedia parameters of MCVideo client
Requested priorityOApplication priority level requested for this call
Up
7.4.2.2.5  MCVideo push to server response  p. 97
Table 7.4.2.2.5-1 describes the information flow MCVideo push to server response from the MCVideo server to the MCVideo client.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the calling party
Time limitOAccepted or imposed duration limit of the stream to be recorded
File URLMURL of the file the stream will be recorded to
SDP answerMMedia parameters selected
Up
7.4.2.2.6  MCVideo push to server complete request  p. 97
Table 7.4.2.2.6-1 describes the information flow MCVideo push to server complete request from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the calling party
CauseMEnd of communication cause
Up
7.4.2.2.7  MCVideo push to server complete response  p. 98
Table 7.4.2.2.7-1 describes the information flow MCVideo push to server complete response from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the calling party
Up

7.4.2.3  One-to-one video push  p. 98

7.4.2.3.1  General  p. 98
One-to-one video push is a private call that only allows the calling party to transmit video to the called party, and the private call ends when the video transmission is completed.
7.4.2.3.2  One-to-one video push - call setup  p. 98
Procedures in Figure 7.4.2.3.2-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user for video push.
Pre-conditions:
  1. This procedure is initiated either manually by the authorized MCVideo users at MCVideo client 1, or automatically due to triggers set by authorized MCVideo users at MCVideo client 1.
  2. Optionally, MCVideo client 1 may have a functional alias activated to be used.
  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.
Reproduction of 3GPP TS 23.281, Fig. 7.4.2.3.2-1: One-to-one video push
Figure 7.4.2.3.2-1: One-to-one video push
Up
Step 1.
MCVideo client 1 initiates push video to MCVideo client 2, and sends a private call request to the MCVideo server using a service identifier as defined in TS 23.228 for MCVideo, for establishing a private call with the chosen MCVideo user for video push. The MCVideo private call request contains MCVideo ID of invited user, an SDP offer containing one or more media types and the video push indication to indicate that requestor is requesting to transmit video to the called party. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call request.
Step 2.
MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call for video push, and that MCVideo user at MCVideo client 2 is authorized to receive the private call for video push. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user.
Step 3.
MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
Step 4.
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 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 MCVideo 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 5.
The MCVideo client 2 notifies the user about the incoming private call for video push. If the functional alias of the calling user is included it is displayed.
Step 6.
The MCVideo client 2 accepts the private call for video push, and sends an MCVideo private call response to the MCVideo server.
Step 7.
Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request for video push, the MCVideo server informs the MCVideo client 1 about successful call establishment via a private call response message.
Step 8.
MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication.
Up
7.4.2.3.3  One-to-one video push - call release  p. 99
The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video push call release.

7.4.2.4  One-to-server video push  p. 99

7.4.2.4.1  General  p. 99
One-to-server video push is a private call between the calling party and the MCVideo server that allows the calling party to transmit video to the server for it to be recorded to a file. The one-to-server video push ends when the video transmission is stopped by the calling party or by the MCVideo server.
7.4.2.4.2  Procedure  p. 99
Procedure in Figure 7.4.2.4.2-1 is the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo video push to the MCVideo server.
Pre-conditions:
  1. MCVideo user 1 on MCVideo client 1 has been authenticated and authorized to use MCVideo service.
  2. MCVideo client 1 is registered.
Reproduction of 3GPP TS 23.281, Fig. 7.4.2.4.2-1: One-to-server video push
Figure 7.4.2.4.2-1: One-to-server video push
Up
Step 1.
MCVideo user on MCVideo client 1 initiates the push of a video to the server and sends an MCVideo push to server request to the MCVideo server. The request contains an SDP offer with media.
Step 2.
MCVideo server checks whether MCVideo client 1 is authorized to push a video to the server.
Step 3.
MCVideo server accepts the push to server request and sends an MCVideo push to server response. The response contains the SDP answer and the URL of the file where the video stream will be recorded.
Step 4.
MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream.
Step 5.
Video stream is transmitted from MCVideo client 1 to MCVideo server. The MCVideo server records the stream to the file whose URL has been given in the MCVideo push to server response.
Step 6.
MCVideo user on MCVideo client 1, or MCVideo client 1 based on pre-defined criteria (e.g. duration), stops the video push to the server and sends an MCVideo push to server complete request.
Step 7.
MCVideo server acknowledges the end of the communication.
Up

7.4.2.5  Remotely initiated video push  p. 101

7.4.2.5.1  General  p. 101
Remotely initiated video push is a private call remotely initiated by a user that only allows a source user to transmit video to a destination, and the private call ends when the video transmission is completed or released by the authorized user who remotely initiated video push call.
7.4.2.5.2  Remotely initiated video push - call setup  p. 101
The procedure describes the case where an authorized MCVideo user is initiating an remotely initiated video push call from source MCVideo user to a destination MCVideo user. Only the source user is allowed to transmit video to the destination user.
Procedures in Figure 7.4.2.5.2-1 are the basic signalling control plane procedures for the MCVideo client remotely initiating establishment of MCVideo private call between the source and destination MCVideo users.
Reproduction of 3GPP TS 23.281, Fig. 7.4.2.5.2-1: Remotely initiated video push - call setup
Figure 7.4.2.5.2-1: Remotely initiated video push - call setup
Up
Step 1.
MCVideo user on MCVideo client 3 initiates remote video push from MCVideo client 1 to MCVideo client 2, by sending a remote video push request to the MCVideo server for establishing a one-to-one video push call between MCVideo client 1 and MCVideo client 2. The remote video push call request contains MCVideo ID of source (MCVideo client 1) and destination (MCVideo client 2) users
Step 2.
MCVideo server checks whether the MCVideo user at MCVideo client 3 is authorized to remotely initiate video push call between the source user and the destination user. MCVideo server also checks if there is any on-going call between the source user and the destination user.
Step 3.
If MCVideo client 3 is authorized and there is no on-ongoing private call between source user and destination user, the MCVideo server sends the remote video push request message to MCVideo client 1 including the information of MCVideo ID of source and destination users.
Step 4.
The MCVideo client 1 accepts the remote video push request and establishes a one-to-one video push call between MCVideo client 1 and MCVideo client 2 as described in the subclause 7.4.2.3.2. The video is transmitted from MCVideo client 1 to MCVideo Client 2.
Step 5.
The MCVideo client 1 sends a remote video push response message to MCVideo server indicating success or failure of call establishment between MCVideo client 1 and MCVideo client 2.
Step 6.
Upon receiving the remote video push response from MCVideo client 1, the MCVideo server informs the MCVideo client 3 about success or failure of the call establishment by sending a remote video push response message.
Up
7.4.2.5.3  Remotely initiated video push - call release by authorized user  p. 102
The procedure describes the case where an authorized MCVideo user is releasing an remotely initiated video push call.
Procedures in Figure 7.4.2.5.3-1 are the basic signalling control plane procedures for the MCVideo client releasing the remotely initiated video push call between the source and destination users.
Reproduction of 3GPP TS 23.281, Fig. 7.4.2.5.3-1: Remotely initiated video push - call release by authorized user
Figure 7.4.2.5.3-1: Remotely initiated video push - call release by authorized user
Up
Step 1.
MCVideo user on MCVideo client 3 initiates release of remotely initiated video push call between MCVideo client 1 and MCVideo client 2, by sending a remote video push release request to the MCVideo server for releasing a one-to-one video push call between MCVideo client 1 and MCVideo client 2. The remote video push release request contains MCVideo ID of source user (MCVideo client 1) and destination user (MCVideo client 2).
Step 2.
MCVideo server checks whether the MCVideo user at MCVideo client 3 is authorized to release the remotely initiated video push call between MCVideo client 1 and MCVideo client 2, and whether there is any on-going one-to-one video push call between MCVideo client 1 and MCVideo client 2.
Step 3.
MCVideo server sends the remote video push release request to MCVideo client 1 for releasing the on-going one-to-one video push call between MCVideo client 1 and MCVideo client 2.
Step 4.
The MCVideo client 1 accepts the remote video push release request and performs the release procedure for the one-to-one video push call between MCVideo client 1 and MCVideo client 2 as described in the subclause 7.4.2.3.3.
Step 5.
The MCVideo client 1 sends a remote video push release response to the MCVideo server indicating the release of the one-to-one video push call between MCVideo client 1 and MCVideo client 2.
Step 6.
Upon receiving the remote video push release response from MCVideo client 1, the MCVideo server informs the MCVideo client 3 about the one-to-one video push call release by sending a remote video push release response message.
Up

7.4.2.6  Remotely initiated video push to group  p. 103

7.4.2.6.1  General  p. 103
Remotely initiated video push to group is a type of broadcast group call that only allows the originating user to remotely request a source user to transmit video to the group, and the group call ends when the video transmission is completed or the authorized user releases the remotely initiated video push to group call.
7.4.2.6.2  Remotely initiated video push to group - call setup  p. 103
The procedure describes the case where an authorized MCVideo user is initiating video push to group call for transmitting video from a source MCVideo user to the group. Only the source MCVideo user is allowed to transmit video.
Procedures in Figure 7.4.2.6.2-1 are the basic signalling control plane procedures for the MCVideo client remotely initiating a video push to group call.
Pre-conditions:
  1. MCVideo client 1 and MCVideo client 2 are affiliated members of the group X.
  2. The user on MCVideo client 1 is authorized to remotely initiate a video push to group call to enable transmitting the video from the user on MCVideo client 2.
Reproduction of 3GPP TS 23.281, Fig. 7.4.2.6.2-1: Remotely initiated video push to group - call setup procedure
Figure 7.4.2.6.2-1: Remotely initiated video push to group - call setup procedure
Up
Step 1.
MCVideo user on MCVideo client 1 remotely initiates a video push to group from MCVideo client 2, by sending a remote video push request to the MCVideo server. The remote video push request contains MCVideo ID of the source user (user of MCVideo client 2) and the MCVideo group ID of the group X to which the video transmission is requested.
Step 2.
MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to remotely initiate a video push to group, and also checks whether MCVideo client 2 is transmitting video in any on-going MCVideo group call on group X. If MCVideo client 2 is already transmitting video to group X then a suitable response is provided in step 6 to MCVideo client 1.
Step 3.
The MCVideo server sends a remote video push request initiated by MCVideo client 1 to MCVideo client 2. The remote video push request contains MCVideo ID of the source user, the MCVideo group ID of the group X to which the video transmission is to be initiated by the source user and an SDP offer containing one or more media types.
Step 4.
MCVideo client 2 initiates a MCVideo broadcast group call on group X. The MCVideo client 2 begins to transmit video to the group X.
Step 5.
The MCVideo client 2 sends a remote video push response message to MCVideo server indicating success or failure in remotely initiating the video push to group X.
Step 6.
The MCVideo server sends a remote video push response message to MCVideo client 1 indicating success or failure in remotely initiating the video push to group X by the MCVideo client 2.
Up
7.4.2.6.3  Remotely initiated video push to group - call release by authorized user  p. 104
The procedure describes the case where an MCVideo user is remotely releasing a video push to group call for ending the video transmission from the source MCVideo user.
Procedures in Figure 7.4.2.6.3-1 are the basic signalling control plane procedures for the MCVideo client remotely releasing a video push to group call.
Pre-condition:
  • MCVideo client 1 and MCVideo client 2 are affiliated members of the group X and there is an on-going broadcast group call on group X from MCVideo client 2 remotely initiated by MCVideo client 1 as described in subclause 7.4.2.6.2.
Reproduction of 3GPP TS 23.281, Fig. 7.4.2.6.3-1: Remotely initiated video push to group - call release by authorized user
Figure 7.4.2.6.3-1: Remotely initiated video push to group - call release by authorized user
Up
Step 1.
MCVideo user on MCVideo client 1 remotely initiates a release of the video push to group call from MCVideo client 2, by sending a remote video push release request to the MCVideo server. The remote video push release request contains MCVideo ID of the source user (user of MCVideo client 2) and the MCVideo group ID of the group X to which the video transmission is to be released.
Step 2.
MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to remotely release a video push to group call, and also checks whether MCVideo client 2 is transmitting video in an on-going MCVideo group call on group X remotely initiated by MCVideo client 1. If MCVideo client 2 is not transmitting video on group X then a suitable response is provided in step 5 to MCVideo client 1.
Step 3.
The MCVideo server sends a remote video push release request initiated by MCVideo client 1 to MCVideo client 2. The remote video push release request contains MCVideo ID of the source user, the MCVideo group ID of the group X to which the video transmission is to be released.
Step 4.
The MCVideo client 2 sends a remote video push release response message to MCVideo server indicating the release of video push to group call.
Step 5.
The MCVideo server sends a remote video push release response message to MCVideo client 1 indicating the release of video push to group call.
Step 6.
MCVideo client 2 stops the video transmission to the group X and releases the MCVideo broadcast group call on group X remotely initiated by MCVideo client 1.
Up

Up   Top   ToC