6.5 Video Push
36.579-63GPPMission Critical (MC) services over LTEPart 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specificationRelease 15TS
6.5.1 On-network / Video push call / One-to-one video push call / Client Originated (CO)
6.5.1.1 Test Purpose (TP)
(1)
with { the UE (MCVideo Client) registered and authorised for MCVideo Service }
ensure that {
when { the MCVideo User requests the establishment of an MCVideo video push call to push a video to another MCVideo client }
then { the UE (MCVideo Client) requests a video push call by sending a SIP INVITE message and, responds to a SIP 200 (OK) message with a SIP ACK message }
}
(2)
with { the UE (MCVideo Client) having established a MCVideo Video push call }
ensure that {
when { the MCVideo User engages in communication with the invited MCVideo User }
then { the UE (MCVideo Client) respects the Transmission Control imposed by the SS (MCVideo Server) (Transmission Granted, Transmission End Request, Transmission End Response) and provides transmission granted notification to the MCVideo User }
}
(3)
with { the UE (MCVideo Client) having an ongoing MCVideo video push call }
ensure that {
when { the MCVideo User requests to terminate the ongoing MCVideo video push call }
then { the UE (MCVideo Client) sends a SIP BYE message, and leaves the MCVideo Session }
}
6.5.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in TS 24.281, clauses 13.2.2.1, 13.2.2.3; and TS 24.581, clauses 6.2.4.2.2, 6.2.4.4.6, 6.2.4.5.3, 6.2.4.6.4. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core spec they have been copied from. Unless otherwise stated, these are Rel-15 requirements.
[TS 24.281, clause 13.2.2.1]
In order to push a video to another MCVideo client, the MCVideo client shall perform the procedures of 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 push"; and
2) shall interact with the media plane as specified in 3GPP TS 24.581 [5] clause 6.2.
[TS 24.281, clause 13.2.2.3]
When the MCVideo client is in an ongoing one-to-one video push call, upon an indication from MCVideo user to release the call, the MCVideo client shall perform the procedures of clause 10.2.4.1.
[TS 24.581, clause 6.2.4.2.2]
When a call is initiated as described in 3GPP TS 24.281 [2], the transmission participant:
1. shall create an instance of the ‘Transmission participant state transition diagram for basic transmission control operation’;
2. if the originating transmission participant receives a transmission control message before it receives the SIP 200 (OK) response, shall store the transmission control message;
NOTE: The originating transmission participant might receive a transmission control message before the SIP 200 (OK) response when initiating, joining or rejoining a call because of processing delays of the SIP 200 (OK) response in the SIP core.
3. if the established MCVideo call is a chat group call and the SIP INVITE request is not an implicit Transmission request, shall enter the ‘U: has no permission to transmit’ state;
4. if for the established MCVideo call the SIP INVITE request is an implicit Transmission request:
a. shall start timer T100 (Transmission Request) and initialise counter C100 (Transmission Request) to 1;
b. shall enter the ‘U: pending request to transmit’ state; and
c. if the transmission participant has received and stored a transmission control message before the reception of the SIP 200 (OK) response, shall act as if the transmission control message was received in the ‘U: pending request to transmit’ state after entering the ‘U: pending request to transmit’ state; and
5. if the established MCVideo call is a broadcast group call, shall enter the ‘U: has permission to transmit’ state.
When the transmission participant is rejoining an ongoing MCVideo call as described in 3GPP TS 24.281 [2] the transmission participant shall enter the ‘U: has no permission to transmit’ state.
[TS 24.581, clause 6.2.4.4.6]
Upon receiving a Transmission Granted message from the transmission control server, the transmission participant:
1. if the first bit in the subtype of the Transmission Granted message is set to ‘1’ (Acknowledgment is required) as described in subclause 9.2.2.1, shall send a Transmission control Ack message. The Transmission control Ack message:
a. shall include the Message Type field set to ‘0’ (Transmission Granted); and
b. shall include the Source field set to ‘0’ (the transmission participant is the source);
2. shall store the SSRC of granted transmission participant received in the Transmission Granted message and use it in the RTP media packets until the transmission is released;
3. shall provide Transmission granted notification to the user, if not already done;
4. shall stop timer T100 (Transmission Request); and
5. shall enter the ‘U: has permission to transmit’ state.
[TS 24.581, clause 6.2.4.5.3]
Upon receiving an indication from the user to end the permission to send RTP media, the transmission participant:
1. shall send a Transmission end request message towards the transmission control server. The Transmission end request message, if the session is a broadcast call and if the session was established as a normal call, shall include the Transmission Indicator with the A-bit set to ‘1’ (Normal call);
2. shall start timer T101 (Transmission End Request) and initialize counter C101 (Transmission End Request) to 1; and
3. shall enter the ‘U: pending end of transmission’ state.
[TS 24.581, clause 6.2.4.6.4]
Upon receiving a Transmission end response message, the transmission participant:
1. if the first bit in the subtype of the Transmission end response message to ‘1’ (Acknowledgment is required) as described in subclause 9.2.2.1, shall send a Transmission control Ack message. The Transmission control Ack message:
a. shall include the Message Type field set to ‘1’ (Transmission end response); and
b. shall include the Source field set to ‘0’ (the transmission participant is the source);
2. may provide a Transmission end notification to the MCVideo user;
3. if the Transmission Indicator field is included and the B-bit set to ‘1’ (Broadcast group call), shall provide a notification to the user indicating the type of call;
4. shall stop timer T101 (Transmission End Request);
5. if the session is not a broadcast group call or if the A-bit in the Transmission Indicator field is set to ‘1’ (Normal call), shall enter the ‘U: has no permission to transmit’ state; and
6. if the session was initiated as a broadcast group call:
a. shall indicate to the MCVideo client the media transmission is completed; and
b shall enter the ‘Call releasing’ state.
6.5.1.3 Test description
6.5.1.3.1 Pre-test conditions
System Simulator:
– SS (MCVideo server)
– For the underlying "transport bearer" over which the SS and the UE will communicate Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in TS 36.508 [24] clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCVideo operation in the MCVideo configuration document).
IUT:
– UE (MCVideo Client)
– The test USIM set as defined in TS 36.579-1 [2], subclause 5.5.10 is inserted.
– UE (MCVideo Client) has a pre-recorded video that is available to push to another client.
Preamble:
– The UE has performed the Generic Test Procedure for MCVideo UE registration as specified in TS 36.579-1 [2], subclause 5.4.2A.
– The MCVideo User performs the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2A.
– UE States at the end of the preamble
– The UE is in E-UTRA Registered, Idle Mode state.
– The MCVideo Client Application has been activated and User has registered-in as the MCVideo User with the Server as active user at the Client.
6.5.1.3.2 Test procedure sequence
Table 6.5.1.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|---|---|---|---|---|---|
|
U – S |
Message |
||||
|
1 |
Make the MCVideo User request to initiate a video push call to push a video from another MCVideo client. (NOTE 1) |
– |
– |
– |
– |
|
2 |
Check: Does the UE (MCVideo Client) correctly perform test procedure ‘MCVideo CO session establishment/modification without provisional responses other than 100 Trying’ as described in TS 36.579-1 [2] Table 5.3B.1.3-1 to push a video to another MCVideo client? |
– |
– |
1 |
– |
|
3 |
Check: Does the UE (MCVideo Client provide transmission granted notification to the MCVideo User? (NOTE 1) |
– |
– |
2 |
P |
|
4 |
Make the MCVideo User request to end Transmission. (NOTE1) |
– |
– |
– |
– |
|
5 |
Check: Does the UE (MCVideo Client) correctly perform test procedure MCVideo transmission End Request CO as described in TS 36.579-1 [2] Table 5.3B.7.3-1? |
– |
– |
2 |
– |
|
6 |
Make the UE (MCVideo Client) request to end the video push call. (NOTE 1) |
– |
– |
– |
– |
|
7 |
Check: Does the UE (MCVideo Client) correctly perform test procedure MCX CO call release as described in TS 36.579-1 [2] Table 5.3.10.3-1? |
– |
– |
3 |
– |
|
NOTE 1: This action is expected to be done via a suitable implementation-dependent MMI. |
|||||
6.5.1.3.3 Specific message contents
Table 6.5.1.3.3-1: SIP INVITE (Step 2, Table 6.5.1.3.2-1; Step 2, S 36.579-1 [2] Table 5.3B.1.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.5.1-1, condition PRIVATE-CALL |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
SDP message |
|||
|
MIME-part-headers |
||||
|
Content-Type |
"application/sdp" |
|||
|
MIME-part-body |
SDP Message as described in Table 6.5.1.3.3-2 |
|||
|
MIME body part |
MCVideo Info |
|||
|
MIME-part-headers |
||||
|
Content-Type |
"application/vnd.3gpp.mcvideo-info+xml" |
|||
|
MIME-part-body |
MCVideo-Info as described in Table 6.5.1.3.3-3 |
|||
|
MIME body part |
Resource list |
|||
|
MIME-part-headers |
||||
|
Content-Type |
"application/resource-lists+xml" |
|||
|
MIME-part-body |
Resource-lists as described in Table 6.5.1.3.3-4 |
|||
Table 6.5.1.3.3-2: SDP in SIP INVITE (Table 6.5.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.1-2, condition FIRST_SDP_FROM_UE, PRIVATE-CALL, SDP_OFFER, IMPLICIT_GRANT_REQUESTED |
|---|
Table 6.5.1.3.3-3: MCVideo-Info in SIP INVITE (Table 6.5.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-2, condition PRIVATE-CALL, INVITE_REFER |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
mcvideoinfo |
||||
|
mcvideo-Params |
||||
|
session-type |
"one-to-one video push" |
TS 24.281 [26] clause 13.2.2.1 |
||
Table 6.5.1.3.3-4: Resource-lists in SIP INVITE (Table 6.5.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.3.1-2, condition PRIVATE-CALL |
|---|
Table 6.5.1.3.3-5: SIP 200 (OK) (Step 2, Table 6.5.1.3.2-1; Step 4, TS 36.579-1 [2] Table 5.3B.1.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.17.1.2-1, condition INVITE-RSP |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
SDP message |
SDP message as described in Table 6.5.1.3.3-6 |
|||
Table 6.5.1.3.3-6: SDP in SIP 200 (OK) (Table 6.5.1.3.3-5)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.2-2, condition FIRST_SDP_FROM_SS, SDP_ANSWER, IMPLICIT_GRANT_REQUESTED |
|---|
Table 6.5.1.3.3-7: SIP BYE (Step 7, Table 6.5.1.3.2-1; Step 1, TS 36.579-1 [2] Table 5.3.10.3-1)
|
Derivation Path: 36.579-1 [2], Table 5.5.2.2.1-1, condition MO_CALL |
|---|