7.2.4 Off-network / Private Call / On-demand / Manual Commencement Mode / Call Released before establishment completion / Call request Rejected / Call establishment successful / Client Originated (CO)

36.579-23GPPMission Critical (MC) services over LTEPart 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specificationRelease 15TS

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

7.2.4.1 Test Purpose (TP)

(1)

ensure that {

when { the MCPTT User requests the establishment of an MCPTT private call, on-demand Manual Commencement Mode }

then { UE (MCPTT Client) sends a PRIVATE CALL SETUP REQUEST message requesting the establishment of an MCPTT private call, on-demand Manual Commencement Mode }

}

(2)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate/cancel private calls with manual commencement, and, the UE is in an off-network environment, and, UE (MCPTT Client) having sent a PRIVATE CALL SETUP REQUEST message requesting establishment of an MCPTT private call, on-demand 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 (MCPTT Client) sends a PRIVATE CALL RELEASE message and terminates the call establishment }

}

(3)

ensure that {

when { the UE (MCPTT 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 (MCPTT Client) terminates the call establishment }

}

(4)

ensure that {

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

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

}

7.2.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.379 clauses 11.2.1.1.1, 11.2.1.1.2, 11.2.2.4.4.1, 11.2.2.4.2.7, 11.2.2.4.2.8, 11.2.2.4.4.8. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 11.2.1.1.1]

In order to participate in a private call, the MCPTT client:

1) shall send the MONP message as a UDP message to the local IP address of the MCPTT user, on UDP port TBD, with an IP time-to-live set to 255; and

Editor’s note [CT1#95, C1-160392]: Port number for the message is FFS.

2) shall treat UDP messages received on the port TBD as received MONP messages.

NOTE: An MCPTT client that supports IPv6 is supposed to listen to the IPv6 addresses.

[TS 24.379, clause 11.2.1.1.2]

For an off-network MCPTT session, only MCPTT speech is used.

One off-network MCPTT session includes one media-floor control entity.

The MCPTT client shall generate an SDP body for a private call in accordance with rules and procedures of IETF RFC 4566 [12] and IETF RFC 3264 [44].

The MCPTT client:

1) shall include in the session-level section:

a) the "o=" field with the <username> portion set to a dash;

b) the "s=" field with the <session name> portion set to a dash; and

c) the "c=" field with the <nettype> portion set to "IN", the <addrtype> portion set to the IP version of the unicast IP address of the MCPTT client and the <connection-address> portion set to the unicast IP address of the MCPTT client;

2) shall include the media-level section for MCPTT speech consisting of:

a) the "m=" field with the <media> portion set to "audio", the <port> portion set to a port number for MCPTT speech of the MCPTT group, the <proto> field set to "RTP/AVP" and <fmt> portion set indicating RTP payload type numbers;

b) the "i=" field with the <session description> portion set to "speech";

c) the "a=fmtp:" attribute(s), the "a=rtpmap:" attribute(s) or both, indicating the codec(s) and media parameters of the MCPTT speech; and

d) the "a=rtcp:" attribute indicating port number to be used for RTCP at the MCPTT client selected according to the rules and procedures of IETF RFC 3605 [13], if the media steam uses other than the default IP address;

3) shall include the media-level section for media-floor control entity consisting of:

a) an "m=" line, with the <media> portion set to "application", the <port> portion set to a port number for media-floor control entity of the MCPTT group, the <proto> field set to "udp" and <fmt> portion set to "MCPTT"; and

b) the "a=fmtp:MCPTT" attribute indicating the parameters of the media-floor control entity as specified 3GPP TS 24.380 [5]; and

4) shall include the MIKEY-SAKKE I_MESSAGE, if generated by the MCPTT client, in an "a=key-mgmt" attribute as a "mikey" attribute value in the SDP offer as specified in IETF RFC 4567 [47].

[TS 24.379, clause 11.2.2.4.4.1]

When in the "P0: start-stop" state or "P1: ignoring same call id", upon an indication from MCPTT 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.383 [45] is set to "true", the MCPTT client:

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

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

3) shall store MCPTT 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.383 [45] 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.383 [45] is set to "true", store "MANUAL COMMENCEMENT MODE" as commencement mode;

5) shall create a call type control state machine as described in subclause 11.2.3.2;

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.179 [46];

b) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0011" 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.179 [46];

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

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

e) shall add the MCPTT ID of the originating MCPTT to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.179 [46];

f) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT 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.179 [46] 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 generate and store offer SDP, as defined in subclause 11.2.1.1.2;

9) shall generate a PRIVATE CALL SETUP REQUEST message as specified in subclause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:

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

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

c) shall set the MCPTT 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 associated with the call type control state machine;

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 if the stored current call type associated with the call type control state machine is "EMERGENCY PRIVATE CALL".

10) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in subclause 11.2.1.1.1;

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

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

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

[TS 24.379, clause 11.2.2.4.2.7]

When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL REJECT message in response to PRIVATE CALL SETUP REQUEST message with Call identifier IE same as the stored call identifier, the MCPTT client:

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

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

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

4) shall release the call control state machine; and

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

[TS 24.379, clause 11.2.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 MCPTT 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 subclause 15.1.11:

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

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

c) shall set the MCPTT 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 subclause 11.2.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 floor control as terminating floor participant as specified in subclause 7.2 in 3GPP TS 24.380 [5];

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

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

[TS 24.379, clause 11.2.2.4.4.8]

When in the "P5: pending" state or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL RELEASE message, the MCPTT client:

1) shall generate a PRIVATE CALL RELEASE ACK message as specified in subclause 15.1.10. In the PRIVATE CALL RELEASE ACK message, the MCPTT client:

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

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

c) shall set the MCPTT 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 subclause 11.2.1.1.1;

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

4) shall stop timer TFP4 (private call accept retransmission) if running;

5) shall release the call type control state machine, if the current state is "P5: pending" state; and

6) shall enter the "P1: ignoring same call id" state, if the current state is "P5: pending" state.

7.2.4.3 Test description

7.2.4.3.1 Pre-test conditions

System Simulator:

– SS-UE1 (MCPTT 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 (MCPTT server) in the Preamble

– 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 MCPTT operation in the MCPTT configuration document).

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

IUT:

– UE (MCPTT 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 MCPTT User performs the Generic Test Procedure for MCPTT 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 (state 1) according to TS 36.508 [24].

7.2.4.3.2 Test procedure sequence

Table 7.2.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Power up the UE.	–	–	–	–
1A	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).	–	–	–	–
2	Activate the MCPTT Client Application and register User A as the MCPTT User (TS 36.579-5 [5], px_MCPTT_User_A_username, px_MCPTT_User_A_password). NOTE: This is expected to be done via a suitable implementation dependent MMI.	–	–	–	–
3	Make the UE (MCPTT User) request the establishment of an MCPTT private call, on-demand Manual Commencement Mode, with Floor Control. NOTE: This is expected to be done via a suitable implementation dependent MMI.	–	–	–	–
–	EXCEPTION: The E-UTRA/EPC actions which are related to the MCPTT 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 MCPTT relevant messages exchanged.	–	–	–	–
4	Check: Does the UE (MCPTT client) send a PRIVATE CALL SETUP REQUEST, Commencement mode set to MANUAL COMMENCEMENT MODE?	–>	PRIVATE CALL SETUP REQUEST	1	P
5	SS-UE1 (MCPTT Client) sends a PRIVATE CALL RINGING message.	<–	PRIVATE CALL RINGING	–	–
6	Make the MCPTT UE (MCPTT User) request termination of the MCPTT private call. NOTE: This is expected to be done via a suitable implementation dependent MMI.	–	–	–	–
7	Check: Does the UE (MCPTT client) send PRIVATE CALL RELEASE message?	–>	PRIVATE CALL RELEASE	2	P
8	SS-UE1 (MCPTT Client) sends a PRIVATE CALL RELEASE ACK message	<–	PRIVATE CALL RELEASE ACK	–	–
–	EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCPTT call release are described in TS 36.579-1 [2], subclause 5.4.8, ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-release by the UE’.	–	–	–	–
9	Wait for 5 sec to ensure the UE is in stable state – scanning for incoming ProSe messages.	–	–	–	–
10	Make the MCPTT UE (MCPTT User) request the establishment of an MCPTT private call, on-demand Manual Commencement Mode, with Floor Control. NOTE: This is expected to be done via a suitable implementation dependent MMI.	–	–	–	–
–	EXCEPTION: The E-UTRA/EPC actions which are related to the MCPTT 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 MCPTT relevant messages exchanged.	–	–	–	–
11	Check: Does the UE (MCPTT client) send a PRIVATE CALL SETUP REQUEST, Commencement mode set to MANUAL COMMENCEMENT MODE?	–>	PRIVATE CALL SETUP REQUEST	1	P
12	SS-UE1 (MCPTT Client) sends a PRIVATE CALL RINGING message.	<–	PRIVATE CALL RINGING	–	–
12A	Wait for 3 sec to ensure that the UE receives the message sent in step 12 before the one sent in step 13.	–	–	–	–
13	SS-UE1 (MCPTT Client) sends a PRIVATE CALL ACCEPT message.	<–	PRIVATE CALL REJECT	–	–
13A	Wait for 3 sec to ensure that the UE receives the message sent in step 13 before the one sent in step 14.	–	–	–	–
14	SS-UE1 (MCPTT Client) sends a PRIVATE CALL ACCEPT message.	<–	PRIVATE CALL ACCEPT	–	–
15	Check: Does the UE (MCPTT client) send a PRIVATE CALL ACCEPT ACK in the next 1 sec? NOTE: It is expected that upon receipt of the message sent in step 13 the UE has entered the "P1: ignoring same call id" state and therefore it shall ignore the message sent in step 14.	–>	PRIVATE CALL ACCEPT ACK	3	F
–	EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCPTT call release are described in TS 36.579-1 [2], subclause 5.4.8, ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-release by the UE’.	–	–	–	–
16	Wait for 5 sec to ensure the UE is in stable state – scanning for incoming ProSe messages.	–	–	–	–
17	Make the MCPTT UE (MCPTT User) request the establishment of an MCPTT private call, on-demand Manual Commencement Mode, with Floor Control. NOTE: This is expected to be done via a suitable implementation dependent MMI.	–	–	–	–
–	EXCEPTION: The E-UTRA/EPC actions which are related to the MCPTT 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 MCPTT relevant messages exchanged.	–	–	–	–
18	Check: Does the UE (MCPTT client) send a PRIVATE CALL SETUP REQUEST, Commencement mode set to MANUAL COMMENCEMENT MODE?	–>	PRIVATE CALL SETUP REQUEST	1	P
19	SS-UE1 (MCPTT Client) sends a PRIVATE CALL RINGING message.	<–	PRIVATE CALL RINGING	–	–
19A	Wait for 3 sec to ensure that the UE receives the message sent in step 19 before the one sent in step 20.	–	–	–	–
20	SS-UE1 (MCPTT Client) sends a PRIVATE CALL ACCEPT message.	<–	PRIVATE CALL ACCEPT	–	–
21	Check: Does the UE (MCPTT client) send a PRIVATE CALL ACCEPT ACK?	–>	PRIVATE CALL ACCEPT ACK	4	P
22	Make the UE (MCPTT User) press the PTT button requesting permission to talk. NOTE 1: Depending on UE implementation the PTT button may already been pressed in step 17. NOTE 2: The UE (MCPTT User) shall keep the button pressed until otherwise written.	–	–	–	–
23	Does the UE (MCPTT client) send a Floor Granted message?	–>	Floor Granted	4	P
24	Make the UE (MCPTT User) release the PTT button.	–	–	–	–
25	Check: Does the UE (MCPTT client) sends a Floor Release message?	–>	Floor Release	4	P
26	Make the MCPTT UE (MCPTT User) request termination of the MCPTT private call. NOTE: This is expected to be done via a suitable implementation dependent MMI.	–	–	–	–
27	The UE (MCPTT client) send PRIVATE CALL RELEASE message.	–>	PRIVATE CALL RELEASE	–	–
28	SS-UE1 (MCPTT Client) sends a PRIVATE CALL RELEASE ACK message.	<–	PRIVATE CALL RELEASE ACK	–	–
–	EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCPTT call release are described in TS 36.579-1 [2], subclause 5.4.8, ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-one communication out of E-UTRA coverage-release by the SS’.	–	–	–	–

7.2.4.3.3 Specific message contents

Table 7.2.4.3.3-1: PRIVATE CALL SETUP REQUEST (Steps 4, 11, 18, Table 7.2.4.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.5.8.1-1.
Information Element	Value/remark	Comment	Condition
Commencement mode	‘00000001’B	MANUAL COMMENCEMENT MODE
User location	Nor present or Any value

Table 7.2.4.3.3-2: Floor Granted (Step 23, Table 7.2.4.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.6.3-1 condition OFF-NETWORK.
Information Element	Value/remark	Comment	Condition
SSRC of granted floor participant	UE (MCPTT client) SSRC
Floor Indicator
Floor Indicator
Floor Indicator	‘10000×00 0000000	Bit A=1 (Normal call) bit F=x (Queueing supported) any value

Table 7.2.4.3.3-3: Floor Release (Step 25, Table 7.2.4.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.6.5-1 condition OFF-NETWORK.
Information Element	Value/remark	Comment	Condition
Floor Indicator
Floor Indicator	‘10000×00 0000000	Bit A=1 (Normal call) bit F=x (Queueing supported) any value