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.3 Video pull  7.3.1 General  7.3.2 On-network video pull  7.3.2.1 General  7.3.2.2 Information flows for on-network video pull  7.3.2.3 One-to-one video pull  7.3.2.4 One-from-server video pull  7.3.3 Off-network video pull  7.3.3.1 General  7.3.3.2 Information flows for off-network video pull  7.3.3.3 Video pull to self 
...

 

7.3  Video pull  p. 88

7.3.1  General  p. 88

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

7.3.2  On-network video pull  p. 88

7.3.2.1  General  p. 88

A MCVideo user triggers its MCVideo client to pull a video either from another MCVideo client or from a MCVideo server.

7.3.2.2  Information flows for on-network video pull  p. 88

The following information flows for private call specified in subclause 7.2.2.2 is used for on-network video pull:
  • 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.3.2.2.1  MCVideo pull from server request  p. 89
Table 7.3.2.2.1-1 describes the information flow MCVideo pull from server request from the MCVideo client to the MCVideo server.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the calling party
File URLMURL of the video file to be streamed
SDP offerMMedia parameters of MCVideo client
Requested priorityOApplication priority level requested for this call
Up
7.3.2.2.2  MCVideo pull from server response  p. 89
Table 7.3.2.2.2-1 describes the information flow MCVideo pull from server response from the MCVideo server to the MCVideo client.
Information Element Status Description
MCVideo IDMThe MCVideo ID of the calling party
SDP answerMMedia parameters selected
Up
7.3.2.2.3  MCVideo pull from server complete request  p. 89
Table 7.3.2.2.3-1 describes the information flow MCVideo pull from 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.3.2.2.4  MCVideo pull from server complete response  p. 89
Table 7.3.2.2.4-1 describes the information flow MCVideo pull from 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.3.2.3  One-to-one video pull  p. 90

7.3.2.3.1  General  p. 90
One-to-one video pull is a private call that only allows the called party to transmit video to the calling party, and the private call ends when the video transmission is completed.
7.3.2.3.2  One-to-one video pull - call setup  p. 90
The procedure describes the case where an MCVideo user is initiating an MCVideo private call to pull video from called MCVideo user in an automatic or manual commencement mode. Only the called party is allowed to transmit video.
Procedures in Figure 7.3.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 pull.
Pre-conditions:
  1. Optionally, MCVideo client 1 may have a functional alias activated to be used.
  2. 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.3.2.3.2-1: One-to-one video pull
Figure 7.3.2.3.2-1: One-to-one video pull
Up
Step 1.
MCVideo user on MCVideo client 1 initiates video pull from MCVideo client 2, by sending 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 pull. The MCVideo private call request contains MCVideo ID of invited user, an SDP offer containing one or more media types and the video pull indication to indicate that invited user is requested to transmit video to the requester. 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 pull, and that MCVideo user at MCVideo client 2 is authorized to receive the private call for video pull. 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 pull. If a functional alias of the calling user is included it is displayed.
Step 6.
The receiving MCVideo client 2 accepts the private call for video pull, and sends an MCVideo private call response to the MCVideo server with an implicit transmit media request.
Step 7.
Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request for video pull, 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.3.2.3.3  One-to-one video pull - call release  p. 91
The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video pull call release.

7.3.2.4  One-from-server video pull  p. 91

7.3.2.4.1  General  p. 91
One-from-server video pull is a private call between the calling party and the MCVideo server that allows the calling party to request streaming of a video from the server where it is stored in a file. The one-from-server video pull ends typically when the end of the video file has been reached or when the transmission is stopped by the calling user or by the MCVideo server.
7.3.2.4.2  Procedure  p. 91
Procedure in Figure 7.3.2.4.2-1 is the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo video pull from 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.
  3. MCVideo client 1 has been received the URL of a video file available on the MCVideo server, e.g. within an MCData SDS.
Reproduction of 3GPP TS 23.281, Fig. 7.3.2.4.2-1: One-from-server video pull
Figure 7.3.2.4.2-1: One-from-server video pull
Up
Step 1.
MCVideo user on MCVideo client 1 initiates the pull of a video from the server and sends an MCVideo pull from server request to the MCVideo server. The request contains the URL of the video file and an SDP offer with media description.
Step 2.
MCVideo server checks whether MCVideo client 1 is authorized to pull the requested video from the server.
Step 3.
MCVideo server accepts the pull from server request and sends an MCVideo pull from server response. The response contains the SDP answer.
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 server to MCVideo client 1. The MCVideo client 1 may be able to remote control the video stream, subject to SDP negotiation.
Step 6.
MCVideo user on MCVideo client 1 stops the video pull from the server and sends an MCVideo pull from server complete request.
Step 7.
MCVideo server acknowledges the end of the communication.
Up

7.3.3  Off-network video pull  p. 92

7.3.3.1  General  p. 92

A MCVideo client pulls a video from another MCVideo client directly, i.e. without involving the network.
Off-network video pull communications are based on ProSe capabilities as described in clause 7.18.

7.3.3.2  Information flows for off-network video pull  p. 93

The following information flows for private call specified in subclause 7.2.3.2 are used for off-network video pull:
  • Private communication request; and
  • Private communication answer response.

7.3.3.3  Video pull to self  p. 93

7.3.3.3.1  General  p. 93
A MCVideo user requests another MCVideo user to deliver a video from its MCVideo client.
7.3.3.3.2  Procedure  p. 93
Figure 7.3.3.3.2-1 describes procedures for an off-network MCVideo video pull, inititated by MCVideo user A at MCVideo client A with another MCVideo client B, to pull a video to MCVideo client A.
MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure should be followed.
Pre-conditions:
  1. MCVideo user A has initiated MCVideo video pull with MCVideo user B.
  2. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
  3. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
Reproduction of 3GPP TS 23.281, Fig. 7.3.3.3.2-1: Off-network video pull to self
Figure 7.3.3.3.2-1: Off-network video pull to self
Up
Step 1.
The MCVideo client A sends a Private communication request towards the MCVideo client B. The Private communication request includes a video pull request and indicates MCVideo client A as the intended recipient of the video pull. Private communication request contains the SDP offer.
Step 2a.
The MCVideo client B notifies the MCVideo user B about the incoming video pull request.
Step 2b.
The MCVideo client B automatically accepts the video pull request, and sends a Private communication answer response indicating the acceptance of the video pull request. The Private communication answer response contains SDP answer.
Step 3.
The MCVideo client A notifies MCVideo user A about the incoming Private communication answer response as an indication of acceptance of MCVideo video pull request.
Step 4.
The MCVideo client A and the MCVideo client B establish the media plane for communication.
Step 5.
Media is transmitted from MCVideo client B to MCVideo client A and presented to the MCVideo user A.
Up

Up   Top   ToC