6.2 Private Calls

36.579-63GPPMission Critical (MC) services over LTEPart 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specificationRelease 15TS

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

6.2.1 On-network / Private Call / On-demand / Automatic Commencement Mode / With Transmission Control / Upgrade to Emergency Call / Cancellation of Emergency on User Request / Client Originated (CO)

6.2.1.1 Test Purpose (TP)

(1)

with { the UE (MCVideo Client) registered and authorised for MCVideo Service, including authorised to initiate/cancel Private and Private Emergency Calls with Automatic Commencement }

ensure that {

when { the MCVideo User requests the establishment of a MCVideo Private Call, On-demand Automatic Commencement Mode, no force of Automatic Commencement, applying end-to-end communication security with Transmission Control }

then { UE (MCVideo Client) sends a SIP INVITE message requesting Private Call On-demand Automatic Commencement Mode, applying end-to-end communication security, and offering a media-level section for a media-transmission control entity, and, after indication from the SS (MCVideo Server) that Transmission is granted, the UE (MCVideo Client) provides transmission granted notification to the user, sends an acknowledgement to the SS (MCVideo Server) }

}

(2)

with { UE (MCVideo Client) having established a MCVideo Private Call, On-demand Automatic Commencement Mode with Transmission Control }

ensure that {

when { the MCVideo User engages in communication with the invited MCVideo User }

then { UE (MCVideo Client) respects the Transmission Control imposed by the MCVideo Server (Transmission Granted, Transmission Control ACK, Transmission End Request, Transmission End Response, Transmission Idle) }

}

(3)

with { UE (MCVideo Client) having established a MCVideo Private Call, On-demand Automatic Commencement Mode with Transmission Control }

ensure that {

when { the MCVideo User requests to upgrade the ongoing MCVideo Private Call to a MCVideo Emergency Private Call with Transmission Control }

then { UE (MCVideo Client) sends a SIP re-INVITE message requesting Private Emergency Call On-demand Automatic Commencement Mode offering a media-level section for a media-transmission control entity and, upon receipt of a SIP 200 (OK) response, considers the call as being upgraded to an Emergency Private Call }

}

(4)

with { UE (MCVideo Client) having upgraded a MCVideo Private Call, On-demand Automatic Commencement Mode with Transmission Control to Emergency Private Call with Transmission Control }

ensure that {

when { the MCVideo User engages in communication with the invited MCVideo User }

then { UE (MCVideo Client) respects the Transmission Control imposed by the SS (MCVideo Server) including override of the invited MCVideo User (who is not in MCVideo emergency state) and applying Transmission Control confidentiality and integrity protection }

}

(5)

with { UE (MCVideo Client) having upgraded a MCVideo Private Call, On-demand Automatic Commencement Mode with Transmission Control to Emergency Private Call with Transmission Control }

ensure that {

when { the MCVideo User requests to downgrade the ongoing MCVideo Emergency Private Call }

then { UE (MCVideo Client) sends a SIP re-INVITE request }

and, upon receipt of a SIP 200 (OK) response, considers the emergency condition ended and the call being reverted back to MCVideo Private Call }

}

(6)

with { UE (MCVideo Client) having an ongoing MCVideo Private Call, On-demand Automatic Commencement Mode with Transmission Control }

ensure that {

when { the MCVideo User requests to terminate the ongoing MCVideo Private Call }

then { UE (MCVideo Client) sends a SIP BYE request and after receiving a SIP 200 (OK) leaves the MCVideo session }

}

6.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.281, clauses 10.2.2.2.1, 10.2.2.2.4, 10.2.2.2.5, and in TS24.581, clauses 6.2.5.5.3, 6.2.5.5.3a.. 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-14 requirements.

[TS 24.281, clause 10.2.2.2.1]

Upon receiving a request from an MCVideo user to establish an MCVideo private call the MCVideo client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [11], with the clarifications given below.

The MCVideo client:

1) shall set the Request-URI of the SIP INVITE request to a public service identity of the participating MCVideo function serving the MCVideo user;

2) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [11];

3) shall include the g.3gpp.mcvideo media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [22];

4) shall include an Accept-Contact header field containing the g.3gpp.mcvideo media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20];

5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14] in the SIP INVITE request;

6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref contain with the value of "urn:urn-7:3gpp-service.ims.icsi.mcvideo" along with parameters "require" and "explicit" according to IETF RFC 3841 [20];

7) for the establishment of a private call shall insert in the SIP INVITE request a MIME resource-lists body with the MCVideo ID of the invited MCVideo user, according to rules and procedures of IETF RFC 5366 [37];

8) if an end-to-end security context needs to be established and if the MCVideo user is initiating a private call then:

a) if necessary, shall instruct the key management client to request keying material from the key management server as described in 3GPP TS 33.180 [8];

b) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [8];

c) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty-eight bits being randomly generated as described in 3GPP TS 33.180 [8];

d) shall encrypt the PCK to a UID associated to the MCVideo client using the MCVideo ID and KMS URI of the invited user as determined by the procedures of subclause 6.2.8.3.9 and a time related parameter as described in 3GPP TS 33.180 [8];

e) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [8]; and

g) shall add the MCVideo ID of the originating MCVideo to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [8]; and

f) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCVideo user’s signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [8].

9) shall include an SDP offer according to 3GPP TS 24.229 [11] with the clarification given in subclause 6.2.1 and with a media stream of the offered media-transmission control entity;

10) if implicit transmission control is required, shall comply with the conditions specified in subclause 6.4;

11) if the MCVideo user is initiating a private call then:

a) if force of automatic commencement mode at the invited MCVideo client is requested by the MCVideo user, shall include in the SIP INVITE request a Priv-Answer-Mode header field with the value "Auto" according to the rules and procedures of IETF RFC 5373 [27];

b) if force of automatic commencement mode at the invited MCVideo client is not requested by the MCVideo user and:

i) if automatic commencement mode at the invited MCVideo client is requested by the MCVideo user, shall include in the SIP INVITE request an Answer-Mode header field with the value "Auto" according to the rules and procedures of IETF RFC 5373 [27]; and

ii) if manual commencement mode at the invited MCVideo client is requested by the MCVideo user, shall include in the SIP INVITE request an Answer-Mode header field with the value "Manual" according to the rules and procedures of IETF RFC 5373 [27]; and

c) 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 "private";

12) if the MCVideo emergency private call state is set to either "MVEPC 2: emergency-pc-requested" or "MVEPC 3: emergency-pc-granted" or the MCVideo emergency private priority state for this private call is set to "MVEPP 2: in-progress", the MCVideo client shall comply with the procedures in subclause 6.2.8.3.3; and

13) shall send SIP INVITE request towards the MCVideo server according to 3GPP TS 24.229 [11].

Upon receiving a SIP 183(Session Progress) response to the SIP INVITE request the MCVideo client:

1) may indicate the progress of the session establishment to the inviting MCVideo user.

Upon receiving a SIP 200 (OK) response to the SIP INVITE request the MCVideo client:

1) shall interact with the media plane as specified in 3GPP TS 24.581 [5];

2) if the MCVideo emergency private call state is set to "MVEPC 2: emergency-pc-requested" or "MVEPC 3: emergency-pc-granted", shall perform the actions specified in subclause 6.2.8.3.4; and

3) shall notify the user that the call has been successfully established.

On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request:

1) if the MCVideo emergency private call state is set to "MVEPC 2: emergency-pc-requested"; or

2) if the MCVideo emergency private call state is set to "MVEPC 3: emergency-pc-granted";

the MCVideo client shall perform the actions specified in subclause 6.2.8.3.5.

On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing session, the MCVideo client shall follow the actions specified in subclause 6.2.8.3.7.

[TS 24.281, clause 10.2.2.2.4]

This subclause covers on-demand session.

Upon receiving a request from an MCVideo user to cancel the in-progress emergency condition on an MCVideo emergency private call, the MCVideo client shall generate a SIP re-INVITE request by following the UE session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.

The MCVideo client:

1) if the MCVideo user is not authorised to cancel the in-progress emergency condition on an MCVideo emergency private call as determined by the procedures of subclause 6.2.8.3.1.2, the MCVideo client:

a) should indicate to the MCVideo user that they are not authorised to cancel the in-progress emergency condition on an MCVideo emergency private call; and

b) shall skip the remaining steps of the current subclause;

2) shall, if the MCVideo user is cancelling an in-progress emergency condition and optionally an MCVideo emergency alert originated by the MCVideo user, include an application/vnd.3gpp.mcvideo-info+xml MIME body populated as specified in subclause 6.2.8.3.6;

3) shall, if the MCVideo user is cancelling an in-progress emergency condition and optionally an MCVideo emergency alert originated by another MCVideo user, include an application/vnd.3gpp.mcvideo-info+xml MIME body populated as specified in subclause 6.2.8.3.8;

4) shall include a Resource-Priority header field and comply with the procedures in subclause 6.2.8.3.3;

5) shall include in the SIP re-INVITE request an SDP offer the media parameters as currently established;

NOTE 1: The SIP re-INVITE request can be sent within an on-demand session or a pre-established session associated with an MCVideo group session. If the SIP re-INVITE request is sent within a pre-established session, the media-level section for the offered MCVideo video media stream and the media-level section of the offered media-transmission control entity are expected to be the same as was negotiated in the existing pre-established session.

6) if an implicit transmission request is required, shall indicate this as specified in subclause 6.4; and

7) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4].

On receiving a SIP 2xx response to the SIP re-INVITE request, the MCVideo client:

1) shall interact with the user plane as specified in 3GPP TS 24.380 [5];

2) shall set the MCVideo emergency private priority state of the MCVideo private call to "MVEPP 1: no-emergency";

3) shall set the MCVideo emergency private call state of the call to "MVEPC 1: emergency-pc-capable"; and

4) if the MCVideo emergency alert state is set to "MVPEA 4: Emergency-alert-cancel-pending", the sent SIP re-INVITE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body and the SIP 2xx response to the SIP request for a priority group call does not contain a Warning header field as specified in subclause 4.4 with the warning text containing the mcvideo-warn-code set to "149", shall set the MCVideo emergency alert state to "MVPEA 1: no-alert".

On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request:

1) if the SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <emergency-ind> element set to a value of "true", the MCVideo client shall set the MCVideo emergency private priority state as "MVEPP 2: in-progress";

2) if the SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcvideo-info+xml MIME body with an <alert-ind> element set to a value of "true" and the sent SIP re-INVITE request did not contain an <originated-by> element in the application/vnd.3gpp.mcvideo-info+xml MIME body, the MCVideo client shall set the MCVideo emergency alert state to "MVPEA 3: emergency-alert-initiated"; and

3) if the SIP 4xx response, SIP 5xx response or SIP 6xx response did not contain an application/vnd.3gpp.mcvideo-info+xml MIME body, shall set the MCVideo emergency private priority state as "MVEPP 2: in-progress" and the MCVideo emergency alert (MPEA) state shall revert to its value prior to entering the current procedure.

NOTE 2: If the in-progress emergency private priority state cancel request is rejected, the state of the session does not change, i.e. continues with MCVideo emergency private call level priority.

On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in subclause 6.2.8.3.7.

[TS 24.281, clause 10.2.2.2.5]

This subclause covers both on-demand session and pre-established sessions.

Upon receiving a request from an MCVideo user to upgrade the ongoing MCVideo private call to an MCVideo emergency private call, the MCVideo client shall generate a SIP re-INVITE request as specified in 3GPP TS 24.229 [4], with the clarifications given below.

1) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body populated as specified in subclause 6.2.8.3.2;

2) shall include a Resource-Priority header field and comply with the procedures in subclause 6.2.8.3.3.

3) shall include an SDP offer with the media parameters as currently established according to 3GPP TS 24.229 [4];

NOTE: The SIP re-INVITE request can be sent within an on-demand session or a pre-established session associated with an MCVideo private call. If the SIP re-INVITE request is sent within a pre-established session, the media-level section for the offered MCVideo video media stream and the media-level section of the offered media-transmission control entity are expected to be the same as was negotiated in the existing pre-established session.

4) if an implicit transmission request is required, shall indicate this as specified in subclause 6.4; and

5) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4].

On receiving a SIP 2xx response to the SIP re-INVITE request the MCVideo client:

1) shall interact with the user plane as specified in 3GPP TS 24.380 [5]; and

2) shall perform the actions specified in subclause 6.2.8.3.4.

On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request, the MCVideo client shall perform the actions specified in subclause 6.2.8.3.5.

On receiving a SIP INFO request where the Request-URI contains an MCVideo session ID identifying an ongoing group session, the MCVideo client shall follow the actions specified in subclause 6.2.8.3.7

[TS 24.581, clause 6.3.5.5.3]

Upon receiving a Transmission End Request message from the associated transmission participant, the transmission control interface towards the MCVideo client in the transmission control server:

1. if the first bit in the subtype of the Transmission End Request 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 ‘4’ (Transmission End Request); and

b. shall include the Source field set to ‘2’ (the controlling MCVideo function is the source);

2. shall forward the Transmission End Request message to the general transmission control operation state machine of the transmission control arbitration logic in the MCVideo server with the first bit in the subtype of the Transmission End Request message set to ‘0’ (Acknowledgment is not required), if not already set; and

3. shall remain in the ‘U: permitted’ state.

[TS 24.581, clause 6.3.5.5.3a]

Upon receiving a Transmission End Response message from the transmission control server, the transmission control interface towards the MCVideo client in the transmission control server:

1. shall forward the Transmission End Response message to the associated transmission participant; and

2. shall enter the state ‘U: not permitted and Transmit Idle’.

6.2.1.3 Test description

6.2.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.

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.2.1.3.2 Test procedure sequence

Table 6.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Make the MCVideo User request the establishment of a MCVideo Private Call, On-demand Automatic Commencement Mode, no force of Automatic Commencement, applying End-to-end Communication Security with Transmission Control. (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’ according to option b,ii of NOTE 1 as described in TS 36.579-1 [2] Table 5.3B.1.3-1to establish of an MCVideo Private Call, On-demand Automatic Commencement Mode, no force of Automatic Commencement, applying End-to-End Communication Security with Transmission Control?	–	–	1,2	P
3-7	Void	–	–	–	–
8	Check: Does the UE (MCVideo Client) notify the MCVideo User that the call has been successfully established? (NOTE 1)	–	–	1	P
8A	Make the MCVideo User request to end the transmission. (NOTE 1)	–	–	–	–
8B	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	P
9	Make the UE (MCVideo Client) request an upgrade of the MCVideo Private Call to an MCVideo Private Emergency Call. (NOTE 1)	–	–	–	–
10	Check: Does the UE (MCVideo Client) correctly perform test procedure ‘MCVideo CO session modification with implicit TransmissionControl’ as described in TS 36.579-1 [2] Table 5.3B.11.3-1 to upgrade an MCVideo Private Call to an MCVideo Private Emergency Call?	–	–	3,4	P
11-15	Void	–	–	–	–
16	Check: Does the UE (MCVideo Client) notify the MCVideo User that the call has been successfully upgraded to an emergency state? (NOTE 1)	–	–	3	P
16A	Make the MCVideo User request to end the transmission. (NOTE 1)	–	–	–	–
16B	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	P
17	Make the UE (MCVideo User) downgrade the MCVideo Emergency Private Call. (NOTE 1)	–	–
18	Check: Does the UE (MCVideo Client) correctly perform test procedure ‘MCVideo CO session modification with implicit TransmissionControl’ as described in TS 36.579-1 [2] Table 5.3B.11.3-1 to downgrade the MCVideo Private Emergency Call?	–	–	5	P
19-23	Void	–	–	–	–
24	Check: Does the UE (MCVideo Client) notify the MCVideo User that the call has been successfully downgraded? (NOTE 1)	–	–	5	P
25	Make the MCVideo User request to release transmission. (NOTE 1)	–	–	–	–
26	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?	–	–	6	P
27-29	Void	–	–	–	–
30	Make the UE (MCVideo Client) request to end the Private Call. (NOTE 1)	–	–	–	–
31	Check: Does the UE (MCVideo Client) correctly perform test procedure for MCX CO call release as described in TS 36.579-1 [2] Table 5.3.10.3-1 to end the Private Call?	–	–	6	P
32	Void	–	–	–	–
NOTE 1: This action is expected to be done via a suitable implementation-dependent MMI..

6.2.1.3.3 Specific message contents

Table 6.2.1.3.3-1: SIP INVITE (Step 2, Table 6.2.1.3.2-1; Step 2, TS 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-body	SDP Message as described in Table 6.2.1.3.3-1A
MIME body part		MCVideo Info
MIME-part-body	MCVideo-Info as described in Table 6.2.1.3.3-2

Table 6.2.1.3.3-1A: SDP message in SIP INVITE (Table 6.2.1.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.1-2, condition FIRST_SDP_FROM_UE, INITIAL_SDP_OFFER, PRIVATE-CALL, IMPLICIT_GRANT_REQUESTED

Table 6.2.1.3.3-2: MCVideo-Info in SIP INVITE (Table 6.2.1.3.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-2, condition PRIVATE-CALL, INVITE_REFER

Table 6.2.1.3.3-3: SIP 200 (OK) (Step 2, Table 6.2.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.2.1.3.3-3A

Table 6.2.1.3.3-3A: SDP message in SIP 200 (OK) (Table 6.2.1.3.3-3)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.2-2, condition FIRST_SDP_FROM_SS, SDP_ANSWER, PRIVATE-CALL, IMPLICIT_GRANT_REQUESTED

Table 6.2.1.3.3-4-5: Void

Table 6.2.1.3.3-6: SIP INVITE (Step 10, Table 6.2.1.3.2-1; Step 2, TS 36.579-1 [2] Table 5.3B.11.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.5.1-1, condition PRIVATE-CALL, EMERGENCY-CALL, re_INVITE
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo Info
MIME-part-body	As described in Table 6.2.1.3.3-7

Table 6.2.1.3.3-7: MCVideo-Info in SIP INVITE (Table 6.2.1.3.3-6)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-2, condition PRIVATE-CALL, EMERGENCY-CALL, INVITE_REFER

Table 6.2.1.3.3-8: Void

Table 6.2.1.1.3.3-9: Transmission Granted (Step 10, Table 6.2.1.1.3.2-1; Step 5, TS 36.579-1 [2] Table 5.3B.11.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.11.2.1-1 condition ACK, EMERGENCY-CALL

Table 6.2.1.3.3-10: SIP INVITE (Step 18, Table 6.2.1.3.2-1; Step 2, TS 36.579-1 [2] Table 5.3B.11.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.5.1-1, condition PRIVATE-CALL, re_INVITE
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCVideo
MIME-part-body	MCVideo-Info as described in Table 6.2.1.3.3-12

Table 6.2.1.3.3-11: MCVideo-Info in SIP INVITE (Table 6.2.1.3.3-11)

Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-2, condition PRIVATE-CALL, INVITE_REFER

Table 6.2.1.3.3-11A: SIP 200 (OK) (Step 18, Table 6.2.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.2.1.3.3-8A

Table 6.2.1.3.3-12-14: TVoid

Table 6.2.1.3.3-15: SIP BYE (Step 31, Table 6.2.1.3.2-1; Step 1, TS 36.579-1 [2] Table 5.3.10.3-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.2.2-1, condition MO_CALL

Table 6.2.1.3.3-16: Void

6.2.2 On-network / Private Call / On-demand / Automatic Commencement Mode / With Transmission Control / Upgrade to Emergency Call / Cancellation of Emergency on User request / Client Terminated (CT)

6.2.2.1 Test Purpose (TP)

(1)

with { UE (MCVideo Client) registered and authorised for MCVideo Service, including authorised to receive private and private emergency calls with Automatic Commencement }

ensure that {

when { the McVideo User receives a request to establish a MCVideo private call, On-demand Automatic Commencement Mode, no force of Automatic Commencement, applying End-to-end communication security with Transmission Control }

then { UE (MCVideo Client) responds by sending a SIP 200 (OK) accepting the establishment of the MCVideo private call, On-demand Automatic Commencement Mode applying End-to-end communication security with Transmission Control, and notifies the user of the call establishment }

}

(2)

with { UE (MCVideo Client) having an ongoing On-demand Automatic Commencement Mode private call with Transmission Control }

ensure that {

when { the MCVideo User engages in communication with the inviting MCVideo User }

then { UE (MCVideo Client) respects the Reception Control imposed by the SS (MCVideo Server) (Media Transmission Notification, Receive Media Request, Receive Media Response, Media Reception End Request, Media Reception End Response }

}

(3)

with { UE (MCVideo Client) having an ongoing On-demand Automatic Commencement Mode private call with Transmission Control }

ensure that {

when { the MCVideo User receives a request for upgrade of the ongoing MCVideo private call to a MCVideo emergency private call with Transmission Control }

then { UE (MCVideo Client) accepts the request and, upon sending SIP 200 (OK) message, considers the call as being upgraded to emergency private call (emergency private call state = "MEPC 3: emergency-pc-granted") and notifies the MCVideo User of the upgraded call if pc_MCX_DisplayInfoEmergencyCall }

}

(4)

with { UE (MCVideo Client) having an On-demand Automatic Commencement Mode private call with Transmission Control upgraded to an emergency private call }

ensure that {

when { the MCVideo User continues communication with the invited MCVideo User }

then { UE (MCVideo Client) respects the transmission control imposed by the MCVideo Server including being able to handle override requested by the inviting MCVideo user and applying Transmission Control confidentiality and integrity protection }

}

(5)

with { UE (MCVideo Client) having an On-demand Automatic Commencement Mode private call with Transmission Control that was upgraded to an emergency private call }

ensure that {

when { the MCVideo User receives a request to cancel the ongoing MCVideo emergency condition on a private call }

then { UE (MCVideo Client) accepts the request and after sending a SIP 200 (OK) response considers the emergency condition cancelled and the call being reverted back to MCVideo private call and notifies the MCVideo User of the downgraded call, and respects Reception Control (Transmission }

}

(6)

with { UE (MCVideo Client) having an ongoing On-demand Automatic Commencement Mode private call }

ensure that {

when { the MCVideo User requests to end the Private Call, the UE (MCVideo Client) sends a Transmission End Request message and, upon receiving a Transmission End Response from the SS (MCVideo Server) }

then { the UE (MCVideo Client) sends a SIP BYE request and the SS (MCVideo Server) responds with a SIP 200 (OK) and leaves the MCVideo session }

}

6.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.281 clauses 10.2.2.2.1, 10.2.2.2.2, 10.2.2.2.3, 10.2.2.3.1.3, 6.2.3.1.1; in TS 24.581, clause 6.3.5.4.9. 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-14 requirements.