hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.4.2 Procedure
|
Figure 7.2.3.4.2-1 describes procedures to establish an off-network automatic commencement private communication between MCVideo user A MCVideo user B.
Pre-conditions:
1. MCVideo user A has initiated automatic commencement private communication with MCVideo user B.
2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo private communications.
3. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
NOTE: How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is implementation specific.
Figure 7.2.3.4.2-1: Off-network automatic commencement private communication
1. The MCVideo client A sends the Private communication request towards MCVideo client associated with MCVideo user B. The Private communication request contains an indication for automatic commencement and the SDP offer.
2. On receiving a Private communication request with an indication for automatic commencement, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications.
3a. The designated MCVideo client B automatically accepts the Private communication request, and sends a Private communication answer response, indicating the successful receipt of communication request to the MCVideo client A. The Private communication answer response contains the SDP answer.
3b. The designated MCVideo client B notifies the MCVideo user B about the incoming Private communication request.
NOTE 1: Step 3a and step 3b can occur in any order.
4. The MCVideo client A and the MCVideo client B establish the media plane for Private Communication.
NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client.
5. MCVideo media is transmitted from the MCVideo client A to the MCVideo client B and is presented to the MCVideo user B.
NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.5 Manual commencement private communication
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.5.1 General
|
A private call request is sent by a MCVideo client directly to another MCVideo client, which checks the request, establishes the MCVideo session without further user interaction and notifies its user about the incoming MCVideo session request. The MCVideo user may accept, reject or ignore the MCVideo session request.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.5.2 Procedure – Communication accepted
|
Figure 7.2.3.5.2-1 describes procedures to establish an off-network manual commencement private communication between MCVideo user A MCVideo user B, which is accepted by the MCVideo user B.
Pre-conditions:
1. MCVideo user A has initiated manual commencement private communication with MCVideo user B.
2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo private communications, if the MCVideo user B has signed on to the MCVideo service with multiple MCVideo clients.
3. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client A has discovered MCVideo clients B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
NOTE: How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is implementation specific.
Figure 7.2.3.5.2-1: Off-network manual commencement private communication – Accepted
1. The MCVideo client A sends the Private communication request towards MCVideo client associated with MCVideo user B. The Private communication request contains an indication for manual commencement and the SDP offer.
2. On receiving a Private communication request, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications.
3a. The designated MCVideo client B presents the incoming Private communication request to the MCVideo user B.
3b. The MCVideo client B sends back a Private communication ringing response to the MCVideo client A.
NOTE 1: Step 3a and step 3b can occur in any order.
4. The MCVideo client A notifies the ringing status to the MCVideo user A.
5. The MCVideo user B accepts the Private communication request.
6. The MCVideo client B sends the Private communication answer response to the MCVideo client A. The Private communication response contains the SDP answer.
7. The MCVideo client A and the MCVideo client B establish the media plane for Private communication.
NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client.
8. MCVideo media is transmitted from the MCVideo client A to the MCVideo client B and is presented to the MCVideo user B.
NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.5.3 Procedure – Communication rejected/ignored
|
Figure 7.2.3.5.3-1 describes procedures to initiate an off-network manual commencement private communication between MCVideo user A MCVideo user B, which is rejected or ignored by the MCVideo user B.
Pre-conditions:
1. MCVideo user A has initiated manual commencement private communication with MCVideo user B.
2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo Private Communications, if the MCVideo user B has signed on to the MCVideo service with multiple MCVideo clients.
3. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client A has discovered MCVideo clients B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
Figure 7.2.3.5.3-1: Off-network manual commencement private communication – Rejected or Ignored
1. The MCVideo client A sends the private communication request towards MCVideo client associated with MCVideo user B. The private communication request contains an indication for manual commencement and the SDP offer.
2. On receiving a Private communication request, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications.
3a. The designated MCVideo client B presents the incoming Private communication request to the MCVideo user B.
3b. The MCVideo client B sends back a Private communication ringing response to the MCVideo client A.
NOTE 1: Step 3a and step 3b can occur in any order.
4. The MCVideo client A notifies the ringing status to the MCVideo user A.
5. The MCVideo user B rejects (or ignores) the Private communication request.
NOTE 2: The MCVideo client B determines that the MCVideo user B has ignored the Private communication request, if the MCVideo user B does not respond within a configured time limit.
6. The MCVideo client B sends a Private communication reject response to the MCVideo client A. The Private communication reject response may indicate that the MCVideo user B has ignored the Private communication request.
7. The MCVideo client A notifies the MCVideo user A that the Private communication request was rejected (or ignored).
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.6 Private communication release
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.6.1 General
|
Either of the MCVideo users involved in a private communication may release the unidirectional media plane or the whole private communication at any time.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.2.3.6.2 Procedure
|
Figure 7.2.3.6.2-1 describes procedures to release an ongoing MCVideo Private communication (either automatic commencement private communication or manual commencement private communication).
Either of the MCVideo users, the initiator or the receiver of the Private communication can request to release the Private communication.
The Private communication release request can be to release an individual (unidirectional) media plane or to terminate the Private communication. Based on the request the requested media plane or both the media planes are terminated in step 3.
Pre-conditions:
1. MCVideo client A and MCVideo client B are engaged in a Private communication.
2. MCVideo user A at MCVideo client A initiates release of the Private communication.
Figure 7.2.3.6.2-1: Off-network Private communication release
1, The MCVideo client A sends the Private communication release request to the MCVideo client B.
2a. The MCVideo client B sends a Private communication release response indicating successful receipt of the request to the MCVideo client A.
2b. The MCVideo client B notifies the MCVideo user B about the Private communication release request.
NOTE: Step 2a and step 2b can occur in any order.
3. MCVideo client A and MCVideo client B release the requested media plane. If both the media planes are released, the Private communication is terminated.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3 Video pull
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2 On-network video pull
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.1 General
|
A MCVideo user triggers its MCVideo client to pull a video either from another MCVideo client or from a MCVideo server.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.2 Information flows for on-network video pull
|
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
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.2.1 MCVideo pull from server request
|
Table 7.3.2.2.1-1 describes the information flow MCVideo pull from server request from the MCVideo client to the MCVideo server.
Table 7.3.2.2.1-1: MCVideo pull from server request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
File URL
M
URL of the video file to be streamed
SDP offer
M
Media parameters of MCVideo client
Requested priority
O
Application priority level requested for this call
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.2.2 MCVideo pull from server response
|
Table 7.3.2.2.2-1 describes the information flow MCVideo pull from server response from the MCVideo server to the MCVideo client.
Table 7.3.2.2.2-1: MCVideo pull from server response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
SDP answer
M
Media parameters selected
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.2.3 MCVideo pull from server complete request
|
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.
Table 7.3.2.2.3-1: MCVideo pull from server complete request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Cause
M
End of communication cause
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.2.4 MCVideo pull from server complete response
|
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.
Table 7.3.2.2.4-1: MCVideo pull from server complete response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.3 One-to-one video pull
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.3.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.3.2 One-to-one video pull – call setup
|
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.
Figure 7.3.2.3.2-1: One-to-one video pull
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 3GPP TS 23.228 [5] 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.
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.
3. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
NOTE 1: Step 3 can occur at any time following step 4, and prior to step 6.
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.
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.
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.
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.
8. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication.
NOTE 2: When the video transmission is completed, the private call is released.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.3.3 One-to-one video pull – call release
|
The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video pull call release.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.4 One-from-server video pull
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.4.1 General
|
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.
NOTE: This procedure fulfills the requirements for the stage 1 replay of stored video feature.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.2.4.2 Procedure
|
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.
Figure 7.3.2.4.2-1: One-from-server video pull
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.
2. MCVideo server checks whether MCVideo client 1 is authorized to pull the requested video from the server.
3. MCVideo server accepts the pull from server request and sends an MCVideo pull from server response. The response contains the SDP answer.
NOTE 1: The SDP may contain a media description that allows the receiving party to remote control the stream (e.g. rewind, fast forward).
4. MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream.
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.
6. MCVideo user on MCVideo client 1 stops the video pull from the server and sends an MCVideo pull from server complete request.
7. MCVideo server acknowledges the end of the communication.
NOTE 2: Alternatively, based on internal criteria (e.g. maximum duration of the video playback, end of the video file), the MCVideo server can end the transmission.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.3 Off-network video pull
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.3.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.3.2 Information flows for off-network video pull
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.3.3 Video pull to self
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.3.3.1 General
|
A MCVideo user requests another MCVideo user to deliver a video from its MCVideo client.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.3.3.3.2 Procedure
|
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.
Figure 7.3.3.3.2-1: Off-network video pull to self
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.
2a. The MCVideo client B notifies the MCVideo user B about the incoming video pull request.
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.
NOTE 1: Step 2a and step 2b can occur in any order.
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.
4. The MCVideo client A and the MCVideo client B establish the media plane for communication.
NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client.
5. Media is transmitted from MCVideo client B to MCVideo client A and presented to the MCVideo user A.
NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4 Video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2 On-network video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2 Information flows for on-network video push
|
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
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.1 Remote video push request
|
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.
Table 7.4.2.2.1-1: Remote video push request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the call originating party
Functional alias
O
The functional alias of the originating party
MCVideo ID
M
The MCVideo ID of the source party who should transmit media
MCVideo ID
O
(see NOTE)
The MCVideo ID of the destination party who should receive media
MCVideo group ID
O
(see NOTE)
The MCVideo group ID of the destination group whose affiliated group members should receive media
SDP offer
O
Media parameters of MCVideo client.
Requested commencement mode
O
An indication that is included if the user is requesting a particular commencement mode
Requested priority
O
Application 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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.2 Remote video push response
|
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.
Table 7.4.2.2.2-1: Remote video push response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the call originating party
MCVideo ID
M
The MCVideo ID of the source party who should transmit media
MCVideo ID
O
(see NOTE)
The MCVideo ID of the destination party who should receive media
MCVideo group ID
O
(see NOTE)
The MCVideo group ID of the destination group whose affiliated group members should receive media
Acceptance confirmation
O
An indication whether the user or group members have positively accepted the call.
SDP answer
M
Media 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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.3 Remote video push release request
|
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.
Table 7.4.2.2.3-1: Remote video push release request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the call originating party
MCVideo ID
M
The MCVideo ID of the source party who should transmit media
MCVideo ID
O
(see NOTE)
The MCVideo ID of the destination party who should receive media
MCVideo group ID
O
(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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.4 MCVideo push to server request
|
Table 7.4.2.2.4-1 describes the information flow MCVideo push to server request from the MCVideo client to the MCVideo server.
Table 7.4.2.2.4-1: MCVideo push to server request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Time limit
O
Requested duration of the stream to be recorded
SDP offer
M
Media parameters of MCVideo client
Requested priority
O
Application priority level requested for this call
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.5 MCVideo push to server response
|
Table 7.4.2.2.5-1 describes the information flow MCVideo push to server response from the MCVideo server to the MCVideo client.
Table 7.4.2.2.5-1: MCVideo push to server response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Time limit
O
Accepted or imposed duration limit of the stream to be recorded
File URL
M
URL of the file the stream will be recorded to
SDP answer
M
Media parameters selected
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.6 MCVideo push to server complete request
|
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.
Table 7.4.2.2.6-1: MCVideo push to server complete request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Cause
M
End of communication cause
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.2.7 MCVideo push to server complete response
|
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.
Table 7.4.2.2.7-1: MCVideo push to server complete response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.3 One-to-one video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.3.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.3.2 One-to-one video push – call setup
|
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.
Figure 7.4.2.3.2-1: One-to-one video push
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 3GPP TS 23.228 [5] 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.
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.
3. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
NOTE 1: Step 3 can occur at any time following step 4, and prior to step 6.
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.
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.
6. The MCVideo client 2 accepts the private call for video push, and sends an MCVideo private call response to the MCVideo server.
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.
8. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication.
NOTE 2: When the video transmission is completed, the private call is released.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.3.3 One-to-one video push – call release
|
The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video push call release.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.4 One-to-server video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.4.1 General
|
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.
NOTE: This procedure fulfils part of the requirements for the stage 1 video processing capabilities feature.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.4.2 Procedure
|
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.
Figure 7.4.2.4.2-1: One-to-server video push
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.
2. MCVideo server checks whether MCVideo client 1 is authorized to push a video to the server.
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.
NOTE 1: Push request and response can include a negotiated maximum duration for the transmission.
4. MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream.
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.
NOTE 2: Notifications of new media availability can be sent by the initiating MCVideo user or by the MCVideo server using the URL received in the MCVideo push to server response.
NOTE 3: MCVideo clients which receive the notification can initiate a pull of the video stream from the server using the URL provided in the notification, at their convenience, using the procedure defined in subclause 7.3.2.4.2.
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.
7. MCVideo server acknowledges the end of the communication.
NOTE 4: Alternatively, based on internal criteria (e.g. maximum duration of the recorded video), the MCVideo server can end the transmission.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.5 Remotely initiated video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.5.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.5.2 Remotely initiated video push – call setup
|
The procedure describes the case where an authorized MCVideo user is initiating a 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.
Figure 7.4.2.5.2-1: Remotely initiated video push – call setup
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
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.
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.
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.
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.
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.
NOTE: Steps 5 and 6 can occur before step 4.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.5.3 Remotely initiated video push – call release by authorized user
|
The procedure describes the case where an authorized MCVideo user is releasing a 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.
Figure 7.4.2.5.3-1: Remotely initiated video push – call release by authorized user
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).
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.
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.
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.
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.
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.
NOTE: Steps 5 and 6 can occur before step 4.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.6 Remotely initiated video push to group
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.6.1 General
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.6.2 Remotely initiated video push to group – call setup
|
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.
Figure 7.4.2.6.2-1: Remotely initiated video push to group – call setup procedure
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.
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.
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.
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.
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.
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.
NOTE: Steps 5 and 6 can occur before step 4.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.2.6.3 Remotely initiated video push to group – call release by authorized user
|
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.
Figure 7.4.2.6.3-1: Remotely initiated video push to group – call release by authorized user
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.
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.
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.
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.
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.
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.
NOTE: Step 6 can occur before steps 4 and 5.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3 Off-network video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.1 General
|
A MCVideo user triggers its MCVideo client to push a video to another MCVideo client.
A MCVideo user triggers its MCVideo client to trigger a remote video push, which requests a second MCVideo client to push a video to a third MCVideo client or to a MCVideo group.
Off-network remote video push works without involving the network.
Off-network video push communications are based on ProSe capabilities as described in clause 7.18.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.2 Information flows for off-network video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.2.1 Remote video push request
|
Table 7.4.3.2.1-1 describes the information flow for the remote video push request sent from one MCVideo client to other MCVideo client(s).
Table 7.4.3.2.1-1: Remote video push request
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user remotely requesting the video push
MCVideo ID
M
The identity of the MCVideo user from whom the video push is requested
Video information
O
Information identifying the video
MCVideo group ID
O
The MCVideo group ID to which the video is to be transmitted.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.2.2 Video push trying response
|
Table 7.4.3.2.2-1 describes the information flow for the video push trying response sent from one MCVideo client to another MCVideo client.
Table 7.4.3.2.2-1: Video push trying response
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user sending the trying response
MCVideo ID
M
The identity of the MCVideo user to whom the trying response is sent
MCVideo ID
M
The identity of the MCVideo user to whom the video is attempted
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.2.3 Notification of video push
|
Table 7.4.3.2.3-1 describes the information flow for the notification of video push sent from one MCVideo client to another MCVideo client.
Table 7.4.3.2.3-1: Notification of video push
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user sending the notification
MCVideo ID
M
The identity of the MCVideo user to whom the notification is sent
MCVideo ID
M
The identity of the MCVideo user to whom the video is pushed
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.3 Video push to another MCVideo user
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.3.1 General
|
The MCVideo Push is the capability of a MCVideo user to push a video to another MCVideo user. A MCVideo user can push a video which is:
- being received by the MCVideo user from another a MCVideo client; or
- being recorded live on the MCVideo client.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.3.2 Procedure
|
Figure 7.4.3.3.2-1 describes procedures for an off-network MCVideo video push, inititated by MCVideo client B with another MCVideo client C, to push a video received from MCVideo client A to MCVideo client C.
MCVideo client A or MCVideo client C or both can be autonomous MCVideo clients or can be human controlled MCVideo clients. In any such combination, following the procedure is followed.
MCVideo client A and MCVideo client B may belong to the same MCVideo user.
Pre-conditions:
1. MCVideo client A and MCVideo client B are engaged in MCVideo communication, where MCVideo client B is receiving media from MCVideo client A.
2. MCVideo user B has initiated MCVideo video push with MCVideo user C.
3. MCVideo client B and MCVideo client C are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client B has discovered MCVideo client C in proximity, associated with MCVideo user C, using ProSe Discovery procedures.
Figure 7.4.3.3.2-1: Off-network Video push to another MCVideo user
1. The MCVideo client B sends a Private communication request towards MCVideo client C. The Private communication request indicates that the request is for video push and contains the SDP offer.
2a. The MCVideo client C may notify the MCVideo user C about the MCVideo Push request (if the MCVideo client C is human controlled)
2b. The MCVideo client C automatically accepts the Private communication request for video push and sends a Private communication answer response to MCVideo client B. The Private communication answer response contains SDP answer.
NOTE 1: Step 2a and step 2b can occur in any order.
3a. If configured, the MCVideo client B notifies MCVideo client A about the video being pushed to MCVideo client C by sending a notification message to MCVideo client A.
3b. If configured, the MCVideo client A may notify the MCVideo user A about the video being pushed to MCVideo client C.
4. The MCVideo client B and MCVideo client C establish the media plane for communication.
5. Video being received by MCVideo client B from MCVideo client A is transmitted from MCVideo client B to MCVideo client C and presented to the MCVideo user C.
NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client(s).
NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.4 Remotely initiated video push
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.4.1 General
|
The MCVideo push is the capability of a MCVideo user to push a video from a second MCVideo user to a third MCVideo user.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.4.2 Procedure
|
Figure 7.4.3.4.2-1 describes procedures for a remotely initiated off-network MCVideo video push, inititated by MCVideo user A at MCVideo client A with another MCVideo client B, to push a video to MCVideo client C.
MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure is followed.
Pre-conditions:
1. MCVideo user A has remotely initiated MCVideo video push 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.
Figure 7.4.3.4.2-1: Remotely initiated off-network video push
1. The MCVideo client A sends a Video push request towards the MCVideo client B. The Video push request indicates MCVideo client C as the intended recipient.
2a. The MCVideo client B checks whether there is on-going priviate communication with MCVideo client C. If there is on-going private communication with MCVideo client C, then step 3, step 4 and step 5 are skipped, else MCVideo client B enables ProSe layer to discover MCVideo client C as specified in subclause 7.2.3.
NOTE 1: MCVideo client A may provide the IP address of the MCVideo client C as part of the Video push request to the MCVideo B client. If such is the case, MCVideo client B does not require discovering MCVideo client C.
2b. The MCVideo client B notifies the MCVideo user B about the incoming Video push request (if MCVideo client B is human controlled).
2c. The MCVideo client B sends a video push trying response to MCVideo client A indicating that it is attempting to establish a connection with MCVideo client C,
NOTE 2: Step 2a, 2b and 2c can occur in any order.
3. Once the required details of MCVideo client C are obtained (either by discovery or from MCVideo client A) the MCVideo client B accepts the Video push request, and sends a Private communication request to MCVideo client C. The Private communication request indicates that the request was in response to the video push request from the MCVideo client A. The Private communication request contains the SDP offer.
4a. MCVideo client C sends a Private communication answer response to MCVideo client B in response to the Private communication request. The Private communication answer response contains the SDP answer.
4b: The MCVideo client C notifies MCVideo user C about the incoming Private communication request as an indication of incoming video.
NOTE 3: Step 4a and step 4b can occur in any order.
5. Upon receiving a Private communication answer response from the MCVideo client C, the MCVideo client B sends a notification message to the MCVideo client A indicating that MCVideo client C has accepted the request.
6. MCVideo client A notifies the MCVideo user A about the acceptance of the request by MCVideo client C (if the MCVideo client A is human controlled)
7. The MCVideo client B and the MCVideo client C establish the media plane for communication.
NOTE 4: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client.
8: Media is transmitted from MCVideo client B to MCVideo client C and presented to the MCVideo user C.
NOTE 5: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
NOTE 6: If the MCVideo client B fails to transmit the video to MCVideo client C, it should send a notification to MCVideo client A, indicating the reason.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.5 Remotely initiated video push to a group
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.5.1 General
|
The MCVideo push is the capability of a MCVideo user to push a video from a second MCVideo user to a MCVideo group.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.4.3.5.2 Procedure
|
Figure 7.4.3.5.2-1 describes procedures for an off-network remote video push request, initiated by MCVideo user A at MCVideo client A towards a MCVideo client B, to initiate a video push to MCVideo group G.
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 client A and MCVideo client B are members of MCVideo group G.
2. MCVideo user A has initiated remote video push request with MCVideo user B to initiate a video push to MCVideo group G.
Figure 7.4.3.5.2-1: Remotely initiated video push to a group
1. MCVideo client A sends a remote video push request towards the MCVideo group. The remote video push request indicates MCVideo client B as the intended target of the request and MCVideo group G as the intended recipient.
2. Upon receiving the remote video push request as the intended target of the request, the MCVideo client B notifies the MCVideo user B of the remote video push request, if the MCVideo client B is human controlled. Other MCVideo group members notify their respective MCVideo users of the remote video push request.
3. The MCVideo client B automatically accepts the remote video push request and sends a group communication announcement message with video push indication towards the MCVideo group, as described in subclause 7.1.3.3. The group communication announcement message contains an SDP body and an indication that the group communication announcement is for video push.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5 Capability information sharing
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.1 General
|
The MCVideo UE can store its capabilities information at the MCVideo server which can be retrieved by authorized users or MCVideo group members during on-network operations. The MCVideo UE can share their capabilities periodically or on-demand to another MCVideo UE or to MCVideo group members during off-network operations.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2 On-network capability information sharing
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.1 General
|
The MCVideo UE can store and update its capabilities information at the MCVideo server. Authorized MCVideo users or MCVideo group members can retrieve the capabilities information from the MCVideo server directly or via subscription and notification.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2 Information flows for on-network capability information sharing
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.1 Update MCVideo capabilities info request
|
Table 7.5.2.2.1-1 describes the information flow update MCVideo capabilities info request from the MCVideo client to the MCVideo server.
Table 7.5.2.2.1-1: Update MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the MCVideo user who is logged into the MCVideo UE
MCVideo capabilities
M
List of capabilities available at the MCVideo UE
NOTE: The device identification associated with MCVideo UE used for providing the MCVideo capabilities when the user logs on to multiple MCVideo UEs is specified by stage 3.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.2 Update MCVideo capabilities info response
|
Table 7.5.2.2.2-1 describes the information flow update MCVideo capabilities info response from the MCVideo server to the MCVideo client.
Table 7.5.2.2.2-1: Update MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.3 Get MCVideo capabilities info request
|
Table 7.5.2.2.3-1 describes the information flow get MCVideo capabilities info request from the MCVideo client to the MCVideo server.
Table 7.5.2.2.3-1: Get MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the requesting MCVideo user
MCVideo ID list (see NOTE)
O
List of Identities of the target MCVideo users
MCVideo group ID list (see NOTE)
O
List of Identities of the target MCVideo groups
NOTE: At least one of the information elements shall be present.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.4 Get MCVideo capabilities info response
|
Table 7.5.2.2.4-1 describes the information flow get MCVideo capabilities info response from the MCVideo server to the MCVideo client.
Table 7.5.2.2.4-1: Get MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
MCVideo ID (see NOTE)
M
Identity of the MCVideo user whose MCVideo capabilities are requested
MCVideo capabilities (see NOTE)
M
List of capabilities available at the requested MCVideo user's UE
NOTE: The MCVideo capabilities correspond to the MCVideo ID. MCVideo ID and MCVideo capabilities information elements shall not be present if the Result is failure. Multiple pairs of MCVideoID and MCVideo capabilities information elements may be appended. Only the affiliated group members in the requested MCVideo group ID list are returned.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.5 Subscribe MCVideo capabilities info request
|
Table 7.5.2.2.5-1 describes the information flow subscribe MCVideo capabilities info request from the MCVideo client to the MCVideo server.
Table 7.5.2.2.5-1: Subscribe MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the requesting MCVideo user
MCVideo ID
O
Identity of the target MCVideo user
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.6 Subscribe MCVideo capabilities info response
|
Table 7.5.2.2.6-1 describes the information flow subscribe MCVideo capabilities info response from the MCVideo server to the MCVideo client.
Table 7.5.2.2.6-1: Subscribe MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.7 Notify MCVideo capabilities info request
|
Table 7.5.2.2.7-1 describes the information flow notify MCVideo capabilities info request from the MCVideo server to the MCVideo client.
Table 7.5.2.2.7-1: Notify MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the MCVideo user logged in at the target MCVideo UE
MCVideo capabilities
M
List of capabilities available at the target MCVideo user's UE
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.2.8 Notify MCVideo capabilities info response
|
Table 7.5.2.2.8-1 describes the information flow notify MCVideo capabilities info response from the MCVideo client to the MCVideo server.
Table 7.5.2.2.8-1: Notify MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.3 Update MCVideo capabilities information at the MCVideo server
|
The procedure for updating the MCVideo capabilities information at the MCVideo server is described in figure 7.5.2.3-1.
Figure 7.5.2.3-1: Update MCVideo capabilities information at the MCVideo server
1. The MCVideo client sends an update MCVideo capabilities info request message to MCVideo server to update the capabilities information available at the MCVideo client
2. The MCVideo server stores the updated MCVideo capabilities information received from the MCVideo client.
3. The MCVideo server provides an update MCVideo capabilities info response indicating success or failure.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.4 Retrieve MCVideo capabilities information by the MCVideo client
|
The procedure for retrieval of MCVideo capabilities information by the MCVideo client is described in figure 7.5.2.4-1.
Pre-conditions:
- The MCVideo server has received MCVideo capabilities information from MCVideo clients and has stored this information;
- The MCVideo user is authorized to access the MCVideo capabilities information from the MCVideo server.
- The requesting MCVideo user is within the same MCVideo system as the requested MCVideo users and the requested MCVideo groups.
Figure 7.5.2.4-1: Retrieve MCVideo capabilities information by the MCVideo client
1. The MCVideo client requests the MCVideo capabilities information by specifying some criteria (e.g. parameters, MCVideo ID).
2. The MCVideo server checks whether the user of the MCVideo client is authorized to retrieve the requested MCVideo capabilities information.
3. If authorized, the MCVideo server provides the requested MCVideo capabilities information to the MCVideo client.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.2.5 Subscription and notification for MCVideo capabilities information
|
The procedure for subscription for MCVideo capabilities information as described in figure 7.5.2.5-1 is used by the MCVideo client to indicate to the MCVideo server that it wishes to receive updates of MCVideo capabilities information for which it is authorized.
Pre-conditions:
- The MCVideo server has some MCVideo capabilities information stored.
Figure 7.5.2.5-1: Subscription for MCVideo capabilities information
1. The MCVideo client subscribes to the MCVideo capabilities information stored at the MCVideo server using the subscribe MCVideo capabilities info request.
2. The MCVideo server provides a subscribe MCVideo capabilities info response to the MCVideo client indicating success or failure of the request.
The procedure for notification of MCVideo capabilities information as described in figure 7.5.2.5-2 is used by the MCVideo server to inform the MCVideo client that new or updated MCVideo capabilities information is available.
Pre-conditions:
- The MCVideo client has subscribed to the MCVideo capabilities information
- The MCVideo server has received and stored new or updated MCVideo capabilities information.
Figure 7.5.2.5-2: Notification of MCVideo capabilities information
1. The MCVideo server provides the notification to the MCVideo client, who previously subscribed for the MCVideo capabilities information.
2. The MCVideo client provides a notify MCVideo capabilities info response to the MCVideo server.
If the MCVideo server has notified the MCVideo client about new or updated MCVideo capabilities information through this procedure, the MCVideo client may then follow the procedure described in subclause 7.5.2.4 in order to retrieve that MCVideo capabilities information.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3 Off-network capability information sharing
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.1 General
|
Each MCVideo client within a MCVideo group needs to share its video capabilities with other members of the MCVideo group.
Video capability sharing can be done by sending information periodically as described in subclause 7.5.3.3 or on request as described in subclause 7.5.3.4.
The receiving MCVideo clients need to store and update the video capability information from the sharing MCVideo client.
Off-network video capability information sharing is based on ProSe capabilities as described in clause 7.18.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.2 Information flows for Off-network capability information sharing
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.2.1 Capability request
|
Table 7.5.3.2.1-1 describes the information flow for the capability request sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.1-1: Capability request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the capabilities
MCVideo ID
O
The identity of the MCVideo user towards whom the capability request was sent.
MCVideo group ID
O
The MCVideo group ID towards which the request was sent
Search criteria
O
A criteria filter for the capability request (e.g. category tags, video capabilities etc.)
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.2.2 Capability announcement
|
Table 7.5.3.2.2-1 describes the information flow for the capability announcement sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.2-1: Capability announcement
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user announcing the capabilities
MCVideo ID
O
The identity of the MCVideo user towards whom the capability announcement was sent.
MCVideo group ID
O
The MCVideo group ID towards which the announcement was sent
Category tags
O
Category tags associated with a specific MCVideo UE or a video
Video capabilities
O
Set of video capabilities (e.g. codecs), camera capabilities (e.g. self-activated camera, wide field of view etc.)
Location
O
The location of the MCVideo user announcing the capabilities, if known
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.2.3 Activity status request
|
Table 7.5.3.2.3-1 describes the information flow for the activity status request sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.3-1: Activity status request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the activity status
MCVideo ID
O
The identity of the MCVideo user towards whom the activity status request was sent.
MCVideo group ID
O
The MCVideo group ID towards which the activity status request was sent
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.2.4 Activity status announcement
|
Table 7.5.3.2.4-1 describes the information flow for the activity status announcement sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.4-1: Activity status announcement
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user announcing the activity status
Activity status
M
Current status of MCVideo UE's activities (e.g. receiving video, transmitting video, or recording video)
Video details
O
Details of the video like category tags or bit rate.
MCVideo ID
O
The identity of the MCVideo user towards whom the activity status announcement was sent.
MCVideo group ID
O
The MCVideo group ID towards which the activity status announcement was sent
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.3 Periodic capability announcements
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.3.1 General
|
The MCVideo client periodically provides its video capability information to other members of the MCVideo group.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.3.2 Procedure
|
Figure 7.5.3.3.2-1 describes procedures for periodic capability announcements.
Each MCVideo client periodically sends a Capability announcement messages to the MCVideo group. This Capability announcement message is received by all other members of MCVideo group members.
Upon receiving such a Capability announcement message, the MCVideo client stores/updates the information about the transmitting MCVideo client.
Pre-conditions:
1. Information for ProSe direct communications corresponding to the MCVideo group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCVideo client 1.
2. MCVideo client 1 to MCVideo client N are members of the same MCVideo group.
Figure 7.5.3.3.2-1: Periodic capability announcements
1. MCVideo client 1 periodically sends a Capability announcement message, which contains its capability information with other relevant information.
2. Other MCVideo clients, upon receiving a Capability announcement message from MCVideo client 1, cache its presence and capability information along with other relevant information.
NOTE: Capability announcement may include specific category tags (e.g. certain video camera), video capabilities of the client, location, camera angles, camera orientation, etc.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.4 Request capabilities from client(s)
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.4.1 General
|
The MCVideo client requests video capability information from other members of the MCVideo group.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.