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

7.2.1 Off-network / Private Call / Automatic Commencement Mode / No response to private call setup request / Private call setup request accepted / Release call / Client Originated (CO)

7.2.1.1 Test Purpose (TP)

(1)

ensure that {

when { the MCVideo User requests the establishment of an MCVideo private call with Automatic Commencement Mode }

then { UE (MCVideo Client) sends a PRIVATE CALL SETUP REQUEST message requesting establishment of a private call with Automatic Commencement Mode }

}

(2)

with { UE (MCVideo Client) registered and authorized for MCVideo Service, including authorized to initiate/cancel private calls with automatic commencement in off-network environment, and, the UE is in an off-network environment, and, UE (MCVideo Client) having sent a PRIVATE CALL SETUP REQUEST message requesting establishment of a private call }

ensure that {

when { the UE (MCVideo Client) does not receive response to the request until the timer TFP1 (private call request retransmission) expires }

then { UE (MCVideo Client) retransmits the PRIVATE CALL SETUP REQUEST message requesting private call if the counter CFP1 (private call request retransmission) has not reached its max value and increments the counter CFP1 with one, and, stops re-transmitting if the counter CFP1 (private call request retransmission) has reached its max value and TFP1 (private call request retransmission) has expired, and, ignores a PRIVATE CALL ACCEPT message if received after the counter CFP1 (private call request retransmission) has reached its max value and TFP1 (private call request retransmission) has expired }

}

(3)

ensure that {

when { the UE (MCVideo Client) receives a PRIVATE CALL ACCEPT message }

then { UE (MCVideo Client) responds with a PRIVATE CALL ACCEPT ACK message and, respects the transmission control imposed by the transmission control entity/arbitrator }

}

(4)

with { UE (MCVideo Client) having an ongoing private call }

ensure that {

when { the MCVideo User requests to end the private call }

then { UE (MCVideo Client) sends a PRIVATE CALL RELEASE message, and, responds to a PRIVATE CALL RELEASE ACK message by starting timer TFP7 (waiting for any message with same call identifier) }

}

7.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.281 clauses 10.3.2.4.2.1, 10.3.2.4.2.2, 10.3.2.4.2.4, 10.3.2.4.5.7, 10.3.2.4.2.8, 10.3.2.4.5.1, 10.3.2.4.5.5, TS 24.581 clauses 7.2.3.2.2, 7.2.3.5.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.281, clause 10.3.2.4.2.1]

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:

1) shall generate and store the call identifier as a random number uniformly distributed between (0, 65536);

2) shall store own MCVideo user ID as caller ID;

3) shall store MCVideo user ID of the callee as callee ID;

4) shall store "AUTOMATIC COMMENCEMENT MODE" as commencement mode, if requested and the value of "/<x>/<x>/Common/PrivateCall/AutoCommence" leaf node present in the user profile as specified in 3GPP TS 24.483 [4] is set to "true". Otherwise if the value of "/<x>/<x>/Common/PrivateCall/ManualCommence" leaf node present in the user profile as specified in 3GPP TS 24.483 [4] is set to "true", store "MANUAL COMMENCEMENT MODE" as commencement mode;

5) shall store "PRIVATE CALL" as the current call type;;

6) if an end-to-end security context needs to be established then:

a) shall use keying material provided by the key management server to generate a PCK as described in 3GPP TS 33.180 [8];

b) 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];

c) shall encrypt the PCK to a UID associated to the MCVideo client using the MCVideo ID of the invited user and a time related parameter as described in 3GPP TS 33.180 [8];

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

e) 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];

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] and;

g) shall store the MIKEY-SAKKE I_MESSAGE for later inclusion in an SDP body;

7) may store current user location as user location;

8) shall set the stored current ProSe per-packet priority to value corresponding to MCVideo off-network private call as described in 3GPP TS 24.483 [4].

9) shall generate and store offer SDP, as defined in clause 10.3.1.1.2;

10) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 17.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCVideo client:

a) shall set the Call identifier IE with the stored call identifier;

b) shall set the MCVideo user ID of the caller IE with the stored caller ID;

c) shall set the MCVideo user ID of the callee IE with the stored callee ID;

d) shall set the Commencement mode IE with the stored commencement mode;

e) shall set the Call type IE with the stored current call type;

f) shall set the SDP offer IE with the stored offer SDP; and

g) may set the User location IE with the stored user location.

11) shall send the PRIVATE CALL SETUP REQUEST message towards other MCVideo client according to rules and procedures as specified in clause 10.3.1.1.1;

12) shall initialize the counter CFP1 (private call request retransmission) with the value set to 1;

13) shall start timer TFP1 (private call request retransmission); and

14) shall enter the "P2: waiting for call response" state.

[TS 24.281, clause 10.3.2.4.2.2]

When in the "P2: waiting for call response" state, upon expiry of timer TFP1 (private call request retransmission), the MCVideo client:

1) may update the stored user location with current user location;

2) shall increment the value of counter CFP1 (private call request retransmission) by 1;

3) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 17.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCVideo client:

a) shall set the Call identifier IE with the stored call identifier;

b) shall set the MCVideo user ID of the caller IE with the stored caller ID;

c) shall set the MCVideo user ID of the callee IE with the stored callee ID;

d) shall set the Commencement mode IE with the stored commencement mode;

e) shall set the Call type IE with the stored current call type;

f) shall set the SDP offer IE with the stored offer SDP; and

g) may set the User location IE with stored user location.

4) shall send the PRIVATE CALL SETUP REQUEST message towards other MCVideo client according to rules and procedures as specified in clause 10.3.1.1.1;

5) shall start timer TFP1 (private call request retransmission); and

6) shall remain in the "P2: waiting for call response" state.

[TS 24.281, clause 10.3.2.4.2.4]

In the "P2: waiting for call response" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit and the stored commencement mode is "AUTOMATIC COMMENCEMENT MODE", the MCVideo client:

1) shall start timer TFP7 (waiting for any message with same call identifier); and

2) shall enter the "P1: ignoring same call id" state.

[TS 24.281, clause 10.3.2.4.5.7]

When in the "P1: ignoring same call id" state, upon expiry of timer TFP7 (waiting for any message with same call identifier) the MCVideo client:

1) shall clear the stored call identifier; and

2) shall enter the "P0: start-stop" state.

[TS 24.281, clause 10.3.2.4.2.8]

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:

1) shall store the SDP answer IE received in the PRIVATE CALL ACCEPT message as answer SDP;

2) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 17.1.11:

a) shall set the Call identifier IE to the stored call identifier;

b) shall set the MCVideo user ID of the caller IE with the stored caller ID; and

c) shall set the MCVideo user ID of the callee IE with the stored callee ID.

3) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 10.3.1.1.1;

4) shall stop timer TFP1 (call setup retransmission), if running;

5) shall stop timer TFP2 (waiting for call response message), if running;

6) shall establish a media session based on the SDP body of the stored answer SDP;

7) shall start transmission control as terminating transmission participant as specified in clause a.b in 3GPP TS 24.581 [5];

8) shall start timer TFP5 (max duration); and

9) shall enter the "P4: part of ongoing call" state.

[TS 24.281, clause 10.3.2.4.5.1]

When in the "P4: part of ongoing call" state, upon an indication from MCVideo User to release a private call, the MCVideo client:

1) shall generate a PRIVATE CALL RELEASE message as specified in clause 17.1.9. In the PRIVATE CALL RELEASE message, the MCVideo client:

a) shall set the Call identifier IE to the stored call identifier;

b) shall set the MCVideo user ID of the caller IE with stored caller ID; and

c) shall set the MCVideo user ID of the callee IE with stored callee ID.

2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 10.3.1.1.1;

3) shall initialize the counter CFP3 (private call release retransmission) with the value set to 1;

4) shall start timer TFP3 (private call release retransmission); and

5) shall enter the "P3: waiting for release response" state.

[TS 24.281, clause 10.3.2.4.5.5]

When in the "P3: waiting for release response" state, upon receiving a PRIVATE CALL RELEASE ACK to PRIVATE CALL RELEASE message, the MCVideo client:

1) shall stop timer TFP3 (private call release retransmission), if running;

2) shall terminate the media session;

3) shall start timer TFP7 (waiting for any message with same call identifier); and

4) shall enter the "P1: ignoring same call id" state.

[TS 24.581, clause 7.2.3.2.2]

When an MCVideo call is established with session announcement including an explicit transmission request, the originating transmission participant:

1. shall create an instance of a transmission participant state transition diagram for basic operation state machine;

2. shall send Transmission Granted message towards other transmission participants. The Transmission Granted message:

a. shall include the granted priority in the Transmission priority field;

b. shall include the MCVideo user’s own MCVideo ID in the User ID field; and

c. if the transmission request is a broadcast group call, system call, emergency call or an imminent peril call, shall include a Transmission Indicator field indicating the relevant call types; and

3. shall enter ‘O: transmission arbitration’ state.

[TS 24.581, clause 7.2.3.5.5]

Upon receiving an indication from the MCVideo user to release permission to send RTP media and there is no transmitter in transmitter list, the transmission participant:

1. shall stop timer T206 (Stop talking warning), if running;

2. shall stop timer T207 (Stop talking), if running;

3. shall send a Transmission Arbitration Release message towards other transmission participants. The Transmission Arbitration Release message:

a. shall include the MCVideo ID of the MCVideo user in the User ID field; and

b. if the session is not initiated as a broadcast group call with the B-bit set to ‘1’ (Broadcast group call), shall include a Transmission Indicator field set to ‘0’ (normal call);

4. shall start timer T230 (Inactivity); and

5. shall enter ‘O: silence’ state.

7.2.1.3 Test description

7.2.1.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCVideo Client)

– For the underlying "transport bearer" over which the SS and the UE will communicate, the SS is behaving as SS-UE1 as defined in TS 36.508 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

NOTE 1: For operation in off-network environment, it needs be ensured that after the UE is powered up it considers the Geographical area #1 that is simulated by the GNSS simulator as being one of the geographical areas set in the USIM for operation when UE is "not served by E-UTRAN".

– SS-NW (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).

NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

IUT:

– UE (MCVideo Client)

– The test USIM set as defined in TS 36.579-1 [2], subclause 5.5.10 is inserted.

– For the underlying "transport bearer" over which the SS and the UE will communicate, the UE is behaving as a ProSe enabled UE as defined in TS 36.508 [24], configured for and operating as ProSe Direct Communication transmitting and receiving device.

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.2.1.3.2 Test procedure sequence

Table 7.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Power up the UE.	–	–	–	–
2	Trigger the UE to reset UTC time and location. NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).	–	–	–	–
3	Activate the MCVideo Client Application and register User A as the MCVideo User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password). (NOTE 1)	–	–	–	–
4	Make the MCVideo User request the establishment of an MCVideo private call with Automatic Commencement Mode, and with Transmission Control. (NOTE 1)	–	–	–	–
–	EXCEPTION: The E-UTRA/EPC actions which are related to the MCVideo call establishment are described in TS 36.579-1 [2], subclause 5.4.5 ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCVideo relevant messages exchanged.	–	–	–	–
–	EXCEPTION: Steps 5-7 are repeated CFP1=3 times (CFP1 defined in 36.579-1 [2] Table 5.5.8.1-1)	–	–	–	–
5	Check: Does the UE (MCVideo Client) send a PRIVATE CALL SETUP REQUEST message? NOTE: It is expected that the UE – shall initialize the counter CFP1 (private call request retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission. – shall start timer TFP1 (private call request retransmission)	–>	PRIVATE CALL SETUP REQUEST	1,2	P
6	Start TFP1 (private call request retransmission) 2000 milliseconds as defined in 36.579-1 [2] Table 5.5.8.1-1.	–	–	–	–
7	TFP1 expires.	–	–	–	–
8	Start TFP7 (waiting for any message with same call identifier) 6 sec (value chosen to facilitate the test sequence in steps 14-16) and defined in 36.579-1 [2] Table 5.5.8.1-1. NOTE: TFP7 is expected to be started after TFP1 expires and CFP1 is equal to the upper limit. NOTE: It is expected that the UE considers at this moment of time the Private call establishment attempt as failed.	–	–	–	–
9	SS-UE1 (MCVideo Client) sends a PRIVATE CALL ACCEPT message,	<–	PRIVATE CALL ACCEPT	–	–
–	EXCEPTION: Steps 10a1-10b1 depend on UE compliance; the "lower case letter" identifies a step sequence that takes place depending on UE behaviour.	–	–	–	–
10a1	Check: Does the UE (MCVideo Client) send a PRIVATE CALL ACCEPT ACK?	–>	PRIVATE CALL ACCEPT ACK	2	F
10b1	Check: Does the TFP7 (waiting for any message with same call identifier) expire?	–	–	2	P
–	EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 5.4.8, ‘Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the UE’.	–	–	–	–
11	Make the MCVideo User request the establishment of an MCVideo private call with Automatic Commencement Mode, and with Transmission Control. (NOTE 1)	–	–	–	–
–	EXCEPTION: The E-UTRA/EPC actions which are related to the MCVideo call establishment are described in TS 36.579-1 [2], subclause 5.4.5 ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCVideo relevant messages exchanged.	–	–	–	–
12	Check: Does the UE (MCVideo Client) send a PRIVATE CALL SETUP REQUEST message? NOTE: It is expected that the UE – shall initialize the counter CFP1 (private call request retransmission) with the value set to 1 on the first transmission, and, increase it by 1 with each re-transmission. – shall start timer TFP1 (private call request retransmission)	–>	PRIVATE CALL SETUP REQUEST	1	P
13	SS-UE1 (MCVideo Client) sends a PRIVATE CALL ACCEPT message.	<–	PRIVATE CALL ACCEPT	–	–
14	Check: Does the UE (MCVideo Client) send a PRIVATE CALL ACCEPT ACK message? NOTE: It is expected that the UE – shall stop timer TFP1 (call setup retransmission), if running – shall stop timer TFP2 (waiting for call response message), if running – shall start timer TFP5 (max duration)	–>	PRIVATE CALL ACCEPT ACK	3	P
15	Check: Does the UE (MCVideo Client) send a Transmission Granted message towards the other transmission participant?	–>	Transmission Granted	3	P
16	Make the MCVideo User release transmission control. (NOTE 1)	–	–	–	–
17	Check: Does the UE (MCVideo Client) send a Transmission Release message to the other transmission participants?	–>	Transmission Arbitration Release	3	P
18	Make the UE (MCVideo Client) release the private call. (NOTE 1)
19	Check: Does the UE (MCVideo Client) send a PRIVATE CALL RELEASE message towards the other transmission participant?	–>	PRIVATE CALL RELEASE	4	P
20	SS-UE1 (MCVideo Client) sends a PRIVATE CALL RELEASE ACK message. NOTE: It is expected that the UE shall start TFP7 (waiting for any message with same call identifier) upon reception of the PRIVATE CALL RELEASE ACK message.	<–	PRIVATE CALL RELEASE ACK
21	Check: Does the TFP7 (waiting for any message with same call identifier) expire?	–	–	4	P
–	EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 5.4.8, ‘Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the UE’.	–	–	–	–
NOTE 1: This is expected to be done via a suitable implementation dependent MMI.

7.2.1.3.3 Specific message contents

Table 7.2.1.3.3-1: Transmission Granted (step 15, Table 7.2.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.11.2.1-1, condition OFF-NETWORK

Table 7.2.1.3.3-2: Transmission Arbitration Release (step 17, Table 7.2.1.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.11.2.4-1, condition OFF-NETWORK

7.2.2 Off-network / Private Call / Automatic Commencement Mode / Client Terminated (CT)

7.2.2.1 Test Purpose (TP)

(1)

ensure that {

when { the UE (MCVideo Client) receives a request for establishment of an MCVideo private call with Automatic Commencement Mode via a PRIVATE CALL SETUP REQUEST message }

then { UE (MCVideo Client) sends a PRIVATE CALL ACCEPT message accepting the establishment of a private call on-demand Automatic Commencement Mode, and, respects the transmission control imposed by the transmission control entity/arbitrator }

}

(2)

ensure that {

when { the UE (MCVideo Client) does not receive response to the request until the timer TFP1 (private call request retransmission) expires }

}

(3)

ensure that {

when { the UE (MCVideo Client) receives a PRIVATE CALL ACCEPT message }

then { UE (MCVideo Client) responds with a PRIVATE CALL ACCEPT ACK message and, respects the transmission control imposed by the transmission control entity/arbitrator }

}

(4)

with { UE (MCVideo Client) having an ongoing private call }

ensure that {

when { the MCVideo User receives a PRIVATE CALL RELEASE message to end the private call }

then { UE (MCVideo Client) sends a PRIVATE CALL RELEASE ACK message }

}

7.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in:

TS 24.281 clauses 10.3.2.4.3.2, 10.3.2.4.3.4, 10.3.2.4.5.4, 10.3.2.4.5.7, TS 24.581 clauses 7.2.3.2.4, 7.2.3.4.2, 7.2.3.7.8, 7.2.3.6.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.281, clause 10.3.2.4.3.2]

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 media session declared in SDP body of PRIVATE CALL SETUP REQUEST message can be established, the MCVideo client:

1) shall store the Call identifier IE in the received message as call identifier;

2) shall set the stored current call type to "PRIVATE CALL";

3) shall set the stored current ProSe per-packet priority to value corresponding to MCVideo off-network private call as described in 3GPP TS 24.483 [4].

4) shall store the MCVideo user ID of the caller IE in the received PRIVATE CALL SETUP REQUEST message as caller ID;

5) shall store own MCVideo user ID as callee ID;

6) if the SDP offer contains an "a=key-mgmt" attribute field with a "mikey" attribute value containing a MIKEY-SAKKE I_MESSAGE:

a) shall extract the MCVideo ID of the originating MCVideo user from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [8];

b) shall convert the MCVideo ID to a UID as described in 3GPP TS 33.180 [8];

c) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [8];

d) if the validation of the signature failed, shall generate a PRIVATE CALL REJECT message as specified in clause 17.1.8. In the PRIVATE CALL REJECT message, the MCVideo client:

i) shall set the call identifier IE to the stored call identifier;

ii) shall set the MCVideo user ID of the caller IE with the stored caller ID;

iii) shall set the MCVideo user ID of the callee IE with the stored callee ID;

iv) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [4] is set to "true". Otherwise, shall set the reason IE as "E2E SECURITY CONTEXT FAILURE";

v) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 10.3.1.1.1; and

vi) shall remain in the current state;

e) if the validation of the signature was successful:

i) shall extract and decrypt the encapsulated PCK using the terminating user’s (KMS provisioned) UID key as described in 3GPP TS 33.180 [8];

ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [8];

iii) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 10.3.1.1.2;

iv) shall generate a PRIVATE CALL ACCEPT message as specified in clause 17.1.7. In the PRIVATE CALL ACCEPT message, the MCVideo client:

A) shall set the Call identifier IE to the stored call identifier; and

B) shall set the MCVideo user ID of the caller IE with stored caller ID.

C) shall set the MCVideo user ID of the callee IE with stored callee ID; and

D) shall set the SDP answer IE with the stored answer SDP;

v) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 10.3.1.1.1;

vi) shall establish a media session based on the SDP body of the stored answer SDP;

vii) shall initialize the counter CFP4 with value set to 1;

viii) shall start timer TFP4 (private call accept retransmission); and

ix) shall enter the "P5: pending" state; and

NOTE: With the PCK successfully shared between the originating MCVideo client and the terminating MCVideo client, both clients are able to use SRTP/SRTCP to create an end-to-end secure session.

7) if the SDP offer does not contain an "a=key-mgmt" attribute, the MCVideo client:

a) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 10.3.1.1.2;

b) shall generate a PRIVATE CALL ACCEPT message as specified in clause 17.1.7:

i) shall set the Call identifier IE to the stored call identifier;

ii) shall set the MCVideo user ID of the caller IE with stored caller ID.

iii) shall set the MCVideo user ID of the callee IE with stored callee ID; and

iv) shall set the SDP answer IE with the stored answer SDP;

c) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 10.3.1.1.1;

d) shall establish a media session based on the SDP body of the stored answer SDP;

e) shall initialize the counter CFP4 with value set to 1;

f) shall start timer TFP4 (private call accept retransmission); and

g) shall enter the "P5: pending" state.

[TS 24.281, clause 10.3.2.4.3.4]

When in the "P5: pending" state, upon receiving a PRIVATE CALL ACCEPT ACK message or RTP media from originating user, the MCVideo client:

1) shall stop timer TFP4 (private call accept retransmission);

2) shall start transmission control as terminating MCVideo client as specified in clause a.b in 3GPP TS 24.581 [5];

3) shall start timer TFP5 (max duration); and

4) shall enter the "P4: part of ongoing call" state.

[TS 24.281, clause 10.3.2.4.5.4]

When in the "P4: part of ongoing call" state, upon receiving a PRIVATE CALL RELEASE message, the MCVideo client:

1) shall generate a PRIVATE CALL RELEASE ACK message as specified in clause 17.1.10;

a) shall set the Call identifier IE to the stored call identifier;

b) shall set the MCVideo user ID of the caller IE the stored caller ID; and

c) shall set the MCVideo user ID of the callee IE with the stored callee ID.

2) shall send the PRIVATE CALL RELEASE ACK message in response to the request message according to rules and procedures as specified in clause 10.3.1.1.1;

3) shall terminate the media session for private call;

4) shall start timer TFP7 (waiting for any message with same call identifier); and

5) shall enter the "P1: ignoring same call id" state.

[TS 24.281, clause 10.3.2.4.5.7]

When in the "P1: ignoring same call id" state, upon expiry of timer TFP7 (waiting for any message with same call identifier) the MCVideo client:

1) shall clear the stored call identifier; and

2) shall enter the "P0: start-stop" state.

[TS 24.581, clause 7.2.3.2.4]

When an MCVideo private call is established the terminating transmission participant:

1. shall create an instance of a transmission participant state transition diagram for basic operation state machine;

2. shall start timer T203(End of RTP media); and

3. shall enter ‘O: has no permission’ state.

[TS 24.581, clause 7.2.3.4.2]

If the transmission participant receives an indication from the MCVideo user that the MCVideo user wants to send media, the transmission participant:

1. shall send the Transmission Request message to other clients. The Transmission Request message:

a. if a priority different than the default transmission priority is required, shall include the Transmission Priority field with the requested priority in the <Transmission Priority> element;

b. shall include the MCVideo ID of the MCVideo user in the User ID field; and

c. if the transmission request is a broadcast group call, system call, emergency call or an imminent peril call, shall include a Transmission Indicator field indicating the relevant call types;

2. shall initialise the counter C201 (Transmission request) with value set to 1;

3. shall start timer T201 (Transmission Request); and

4. shall enter ‘O: pending request’ state.

[TS 24.581, clause 7.2.3.7.8]

Upon receiving Transmission Granted message and if the <User ID> value in the User ID field matches its own MCVideo ID and User ID of transmission participant sending the Transmission Granted message matches the stored User ID of current transmission arbitrator, the transmission participant:

1. shall stop timer T201 (Transmission Request);

2. clear the stored current transmission arbitrator;

3. shall store the transmitter list of the Transmission Granted message;

4. may provide a transmission granted notification to the MCVideo user; and

5. shall enter ‘O: has permission’ state.

[TS 24.581, clause 7.2.3.6.4]

Upon receiving an indication from the MCVideo user to release permission to send RTP media, the transmission participant:

1. shall stop timer T206 (Stop talking warning), if running;

2. shall stop timer T207 (Stop talking), if running;

3. shall send a Transmission Release message towards other transmission participants. The Transmission Release message:

a. shall include the MCVideo ID of the MCVideo user in the User ID field; and

b. if the session is not initiated as a broadcast group call with the B-bit set to ‘1’ (Broadcast group call), shall include a Transmission Indicator field set to ‘0’ (normal call); and

4. shall enter ‘O: has no permission’ state.

7.2.2.3 Test description

7.2.2.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCVideo Client)

– GNSS simulator to simulate a location and provide a timing reference for the assistance of E-UTRAN off-network testing.

– SS-NW (MCVideo server)

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

– The GNSS simulator is configured to simulate a location in the centre of Geographical area #1 and provide a timing reference, as defined in TS 36.508 [24] Table 4.11.2-2 scenario #1.

– The UE is switched-off.

– UE States at the end of the preamble

– The UE is in state ‘switched-off’.

7.2.2.3.2 Test procedure sequence

Table 7.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Power up the UE.	–	–	–	–
2	Trigger the UE to reset UTC time and location. NOTE: The UTC time and location reset may be performed by MMI or AT command (+CUTCR).	–	–	–	–
3	Activate the MCVideo Client Application and register User A as the MCVideo User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password). (NOTE 1)	–	–	–	–
–	EXCEPTION: The E-UTRA/EPC actions which are related to the MCVideo call establishment are described in TS 36.579-1 [2], subclause 5.4.6 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-one communication out of E-UTRA coverage-establishment’. The test sequence below shows only the MCVideo relevant messages exchanged.	–	–	–	–
4	SS-UE1 (MCVideo Client) sends a PRIVATE CALL SETUP REQUEST.	<–	PRIVATE CALL SETUP REQUEST	–	–
5	Check: Does the UE (MCVideo Client) send a PRIVATE CALL ACCEPT?	–>	PRIVATE CALL ACCEPT	1	P
6	SS-UE1 (MCVideo Client) sends a PRIVATE CALL ACCEPT ACK.	<–	PRIVATE CALL ACCEPT ACK	–	–
7	SS-UE1 (MCVideo Client) sends Transmission Granted message.	<–	Transmission Granted	–	–
8	Make the MCVideo User press the PTT button requesting permission to talk. NOTE: The MCVideo User shall keep the button pressed until otherwise written.	–	–	–	–
9	Check: Does the UE (MCVideo Client) send a Transmission Request message?	–>	Transmission Request	1	P
10	SS-UE1 (MCVideo Client) sends Transmission Granted message.	<–	Transmission Granted	–	–
11	Make the MCVideo User release transmission control. (NOTE 1)	–	–	–	–
12	Check: Does the UE (MCVideo Client) send a Transmission Release message?	–>	Transmission Release	1	P
14	SS-UE1 (MCVideo Client) sends PRIVATE CALL RELEASE message.	<–	PRIVATE CALL RELEASE	–	–
15	Check: Does the UE (MCVideo Client) send a PRIVATE CALL RELEASE ACK message.	–>	PRIVATE CALL RELEASE ACK	2	P
–	EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 5.4.7, ‘Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the SS’.	–	–	–	–
NOTE 1: This is expected to be done via a suitable implementation dependent MMI.

7.2.2.3.3 Specific message contents

Table 7.2.2.3.3-1: PRIVATE CALL SETUP REQUEST (step 4, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.14.8-1
Information Element	Value/remark	Comment	Condition
MCVideo user ID of the caller	px_MCVideo_ID_User_B
MCVideo user ID of the callee	px_MCVideo_ID_User_A
SDP offer	As described in TS 36.579-1 [2], Table 5.5.3.1.4-2 with condition PRIVATE_CALL

Table 7.2.2.3.3-2: PRIVATE CALL ACCEPT (step 5, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.14.10-1
Information Element	Value/remark	Comment	Condition
MCVideo user ID of the caller	px_MCVideo_ID_User_B
MCVideo user ID of the callee	px_MCVideo_ID_User_A
SDP answer	As described in TS 36.579-1 [2], Table 5.5.3.1.3-2 with condition PRIVATE_CALL

Table 7.2.2.3.3-3: PRIVATE CALL ACCEPT ACK (step 6, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.14.14-1
Information Element	Value/remark	Comment	Condition
MCVideo user ID of the caller	px_MCVideo_ID_User_B
MCVideo user ID of the callee	px_MCVideo_ID_User_A

Table 7.2.2.3.3-4: Transmission Granted (step 7, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.11.2.1-1, condition OFF-NETWORK
Information Element	Value/remark	Comment	Condition
User ID
User ID	px_MCVideo_ID_User_B

Table 7.2.2.3.3-5: Transmission Request (step 9, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.11.1.1-1, condition OFF-NETWORK

Table 7.2.2.3.3-6: Transmission Granted (step 10, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.11.2.1-1, condition OFF-NETWORK

Table 7.2.2.3.3-7: PRIVATE CALL RELEASE (step 4, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.14.12-1
Information Element	Value/remark	Comment	Condition
MCVideo user ID of the caller	px_MCVideo_ID_User_B
MCVideo user ID of the callee	px_MCVideo_ID_User_A

Table 7.2.2.3.3-8: PRIVATE CALL RELEASE ACK (step 4, Table 7.2.2.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.14.13-1
Information Element	Value/remark	Comment	Condition
MCVideo user ID of the caller	px_MCVideo_ID_User_B
MCVideo user ID of the callee	px_MCVideo_ID_User_A

7.2.3 Off-network / Private Call / Manual Commencement Mode / Call Released before establishment completion / Call request rejected / Call establishment successful / Client Originated (CO)

7.2.3.1 Test Purpose (TP)

(1)

ensure that {

when { the MCVideo User requests the establishment of an MCVideo private call with Manual Commencement Mode }

then { UE (MCVideo Client) sends a PRIVATE CALL SETUP REQUEST message requesting the establishment of an MCVideo private call with Manual Commencement Mode }

}

(2)

with { UE (MCVideo Client) registered and authorized for MCVideo Service, including authorized to initiate/cancel private calls with manual commencement, and, the UE is in an off-network environment, and, UE (MCVideo Client) having sent a PRIVATE CALL SETUP REQUEST message requesting establishment of an MCVideo private call with Manual Commencement Mode }

ensure that {

when { the User requests termination of the call after a PRIVATE CALL RINGING message has been received but before the completion of the call establishment }

then { UE (MCVideo Client) sends a PRIVATE CALL RELEASE message and terminates the call establishment }

}

(3)

ensure that {

when { the UE (MCVideo Client) receives a PRIVATE CALL REJECT message after a PRIVATE CALL RINGING message has been received but before the completion of the call establishment }

then { UE (MCVideo Client) terminates the call establishment }

}

(4)

ensure that {

when { the UE (MCVideo Client) receives a PRIVATE CALL RINGING message followed by a PRIVATE CALL ACCEPT message }

then { UE (MCVideo Client) transmits a PRIVATE CALL ACCEPT ACK message and considers the call as being established }

}

7.2.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.281 clauses 10.3.2.4.2.1, 10.3.2.4.2.3, 10.3.2.4.2.9, 10.3.2.4.5.5, 10.3.2.4.2.7, 10.3.2.4.2.8, 10.3.2.4.5.1, TS 24.581 clauses 7.2.3.2.2, 7.2.3.5.5. Unless otherwise stated these are Rel-15 requirements.