12 Video Pull

24.2813GPPMission Critical Video (MCVideo) signalling controlProtocol specificationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

12.1 General

12.2 On-network video pull

12.2.1 General

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

12.2.2 MCVideo client procedures

12.2.2.1 One-to-one video pull originating procedures

In order to pull a video from another MCVideo client, the MCVideo client shall perform the procedures of the clause 10.2.2.2.1, with the following clarifications:

1) shall contain an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <session-type> element set to a value of "one-to-one video pull".

12.2.2.2 One-to-one video pull terminating procedures

Upon receipt of an initial SIP INVITE request for the one-to-one video pull call, the MCVideo client shall perform the procedures of the clause 10.2.2.2.2, with the following clarifications:

1) shall initiate the implicit transmit media request as specified in 3GPP TS 24.581 [5].

12.2.2.3 One-to-one video pull release procedures

When the MCVideo client is in an ongoing one-to-one video pull call, upon an indication from MCVideo user to release the call, the MCVideo client shall perform the procedures of the clause 10.2.4.1.

12.2.2.4 One-from-server video pull originating procedures

In order to pull a video from a MCVideo server, MCVideo client shall perform the procedures of the clause 10.2.2.2.1, with the following clarifications:

2) shall contain an application/vnd.3gpp.mcvideo-info+xml MIME body with the <mcvideoinfo> element containing the <mcvideo-Params> element with the <video-pull-url> element set to the URL of the video file to be streamed;

NOTE: How an MCVideo client is informed the URL of the video file is out of scope of the current document.

3) shall not insert in the SIP INVITE request an application/resource-lists+xml MIME with the MCVideo ID of the invited MCVideo user in the "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body; and

4) shall use the automatic commencement mode.

12.2.2.5 One-from-server video pull terminating procedures

No procedures specified.

12.2.2.6 One-from-server video pull release procedures

When the MCVideo client is in an ongoing one-from-server video pull call, upon an indication from MCVideo user to release the call, the MCVideo client shall perform the procedures of the clause 10.2.4.1.

12.2.3 MCVideo server procedures

12.2.3.1 Participating MCVideo function procedures

12.2.3.1.1 One-to-one video pull originating procedures

Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video pull", the participating MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.3.1.1.

12.2.3.1.2 One-to-one video pull terminating procedures

Upon receipt of a "SIP INVITE request for terminating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video pull", the participating MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.3.2.

12.2.3.1.3 One-to-one video pull release procedures

Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 10.2.4.

Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.5.

12.2.3.1.4 One-from-server video pull originating procedures

Upon receipt of a "SIP INVITE request for originating participating MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-from-server video pull", the participating MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.3.1.1, with the following clarifications:

1) shall not check the <allow-private-call> element of the <ruleset> element; and

2) shall use the automatic commencement mode.

12.2.3.1.5 One-from-server video pull terminating procedures

No procedures specified.

12.2.3.1.6 One-from-server video pull release procedures

Upon receiving from the MCVideo client a SIP BYE request the participating MCVideo function shall follow the procedures as specified in clause 10.2.4.

Upon receiving a SIP BYE request from the controlling MCVideo function, the participating MCVideo function shall follow the procedures as specified in clause 10.2.5.

12.2.3.2 Controlling MCVideo function procedures

12.2.3.2.1 One-to-one video pull originating procedures

No procedures specified.

12.2.3.2.2 One-to-one video pull terminating procedures

Upon receipt of a "SIP INVITE request for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-to-one video pull", the controlling MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.4.2, with following clarifications:

1) shall check whether the MCVideo ID of the MCVideo calling user in the <mcvideo-calling-user-id> is authorised to initiate the one-to-one video pull call, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps; and

2) shall check whether the MCVideo ID of the MCVideo called party user in the <mcvideo-called-party-id> is authorised to receive the one-to-one video pull call, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps.

12.2.3.2.3 One-to-one video pull release procedures

When the MCVideo session for one-to-one video pull call needs to be released, the controlling MCVideo function shall perform the procedures of the clause 10.2.5.4.

12.2.3.2.4 One-from-server video pull originating procedures

No procedures specified.

12.2.3.2.5 One-from-server video pull terminating procedures

Upon receipt of a "SIP INVITE request for controlling MCVideo function" containing an application/vnd.3gpp.mcvideo-info+xml MIME body with the <session-type> element set to a value of "one-from-server video pull", the controlling MCVideo function determine that the call is a private call and shall perform the procedures of the clause 10.2.2.4.2, with following clarifications:

1) shall check whether the MCVideo ID of the MCVideo calling user in the <mcvideo-calling-user-id> is authorised to initiate the one-from-server video pull call, and if it is not authorised the controlling MCVideo function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps; and

2) shall based on the received URL of the video file contained in <video-pull-url> element of the application/vnd.3gpp.mcvideo-info+xml MIME body, transmit media to the MCVideo client as specified in 3GPP TS 24.380 [79].

12.2.3.2.6 One-from-server video pull release procedures

When the MCVideo session for one-from-server video pull call needs to be released, the controlling MCVideo function shall perform the procedures of the clause 10.2.5.4.

12.3 Off-network video pull

12.3.1 General

The MCVideo client uses off network private call setup procedures as defined in subclasue 10.3 with clarifications given in clause 12.3.2.

12.3.2 MCVideo client procedures

12.3.2.1 Off network video pull setup

12.3.2.1.1 Initiating video pull

When in the "P0: start-stop" state or "P1: ignoring same call id", upon an indication from MCVideo User to initiate a private call and the value of "/<x>/<x>/Common/PrivateCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [4] is set to "true", the MCVideo client shall follow the procedure as defined in clause 10.3.2.4.2.1 with following clarification:

1) in step 5) of clause 10.3.2.4.2.1, shall store "PRIVATE VIDEO PULL CALL" as the current call type.

12.3.2.1.2 Video pull setup request accepted

When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCVideo client shall follow the procedure as defined in clause 10.3.2.4.2.8 with following clarification:

1) in step 7) of clause 10.3.2.4.2.8, shall not start transmission control as terminating transmission participant

12.3.2.2 Off network video pull setup in automatic commencement mode

12.3.2.2.1 Responding to video pull setup request when not participating in the ongoing call

When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Commencement mode IE set to "AUTOMATIC COMMENCEMENT MODE" and Call identifier IE different than stored call identifier and Call type IE set to "PRIVATE VIDEO PULL CALL" and media session declared in SDP body of PRIVATE CALL SETUP REQUEST message can be established, the MCVideo client shall follow the procedure as defined in clause 10.3.2.4.3.2 with following clarification:

1) in step 2) of clause 10.3.2.4.3.2, shall set the stored current call type to "PRIVATE VIDEO PULL CALL".

12.3.2.2.2 Establishing the video pull call

When in the "P5: pending" state, upon receiving a PRIVATE CALL ACCEPT ACK message or RTP media from originating user, the MCVideo client shall follow the procedure as defined in clause 10.3.2.4.3.4 with following clarification:

1) in step 2) of clause 10.3.2.4.3.4, shall not start transmission control as terminating MCVideo client.