7.2.3 Off-network / Private Call / On-demand / Automatic Commencement Mode / Upgrade to Emergency Call Reject / Downgrade from Emergency Call Failure / 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

7.2.3.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate/cancel private and private emergency calls with automatic commencement in off-network environment, and, the UE is in an off-network environment, and, upon User request the UE (MCPTT Client) has requested upgrade of an established Private Call to an Emergency Private call }

ensure that {

when { the called Client rejects the upgrade requests }

then { UE (MCPTT Client) continues with the established Private call }

}

(2)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate/cancel private and private emergency calls with automatic commencement in off-network environment, and, the UE is in an off-network environment, and, upon User request the UE (MCPTT Client) has requested downgrade of an Emergency Private call to a Private call }

ensure that {

when { the UE (MCPTT Client) does not receive response to the request until the timer TFP6 (emergency private call cancel retransmission) expires }

then { UE (MCPTT Client) retransmits the PRIVATE CALL EMERGENCY CANCEL message requesting the downgrade of the emergency private call if the counter CFP6 (emergency private call cancel retransmission) has not reached its max value and increments the counter CFP6 with one, and, stops re-transmitting if the counter CFP1 (emergency private call cancel retransmission) has reached its max value and considers the private call as terminated }

}

7.2.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.379 clauses 11.2.3.4.5.4, 11.2.3.4.6.1, 11.2.3.4.6.2, 11.2.3.4.6.4, 11.2.2.4.5.9, 11.2.2.4.5.9. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 11.2.3.4.5.4]

When in the "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL REJECT message in response to PRIVATE CALL SETUP REQUEST message with Call identifier IE same as stored call identifier, the MCPTT client:

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

2) shall set the ProSe per-packet priority to the value corresponding to the MCPTT off-network private call as described in 3GPP TS 24.383 [45];

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

4) shall enter the "Q1: in-progress private call" state.

[TS 24.379, clause 11.2.3.4.6.1]

When in the "Q2: in-progress emergency private call" state, upon an indication from:

1) the caller of the emergency private call; or

…

to cancel the emergency private call, the MCPTT client:

1) shall generate a PRIVATE CALL EMERGENCY CANCEL message as specified in subclause 15.1.12. In the PRIVATE CALL EMERGENCY CANCEL 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; and

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

2) shall send the PRIVATE CALL EMERGENCY CANCEL message according to rules and procedures as specified in subclause 11.2.1.1.1;

3) shall stop TFP8 (implicit downgrade) timer;

4) shall initialize the counter CFP6 (emergency private call cancel retransmission) with the value set to 1;

5) shall start timer TFP6 (emergency private call cancel retransmission);

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

7) shall enter the "Q1: in-progress private call" state.

[TS 24.379, clause 11.2.3.4.6.2]

When in the "Q1: in-progress private call" state, upon expiry of timer TFP6 (emergency private call cancel retransmission), the MCPTT client:

1) shall generate a PRIVATE CALL EMERGENCY CANCEL message as specified in subclause 15.1.12. In the PRIVATE CALL EMERGENCY CANCEL 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 store callee ID.

2) shall send the PRIVATE CALL EMERGENCY CANCEL message according to rules and procedures as specified in subclause 11.2.1.1.1;

3) shall increment the value of the timer CFP6 (emergency private call cancel retransmission) by 1;

4) shall start timer TFP6 (emergency private call cancel retransmission); and

5) shall remain in the "Q1: in-progress private call" state.

[TS 24.379, clause 11.2.3.4.6.4]

In the "Q1: in-progress private call" state, when timer TFP6 (emergency private call cancel retransmission) expires and the value of the counter CFP6 (emergency private call cancel retransmission) is equal to the upper limit, the MCPTT client:

1) shall release the stored current call type;

2) shall release the stored Prose per-packet priority; and

3) shall enter "Q0: waiting for the call to be established".

[TS 24.379, clause 11.2.2.4.5.9]

In the "P4: part of ongoing call" state, when timer TFP6 (emergency private call cancel retransmission) expires and the value of the counter CFP6 (emergency private call cancel retransmission) is equal to the upper limit, the MCPTT client:

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

2) shall release the call type control state machine; and

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

[TS 24.379, clause 11.2.2.4.5.9]

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

1) shall clear the stored call identifier; and

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

7.2.3.3 Test description

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

Table 7.2.3.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 Automatic 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

The UE (MCPTT client) sends a PRIVATE CALL SETUP REQUEST, Commencement mode set to AUTOMATIC COMMENCEMENT MODE, Call type set to Private Call.

–>

PRIVATE CALL SETUP REQUEST

–

–

5

SS-UE1 (MCPTT Client) sends a PRIVATE CALL ACCEPT message.

<–

PRIVATE CALL ACCEPT

–

–

6

The UE (MCPTT client) send a PRIVATE CALL ACCEPT ACK.

–>

PRIVATE CALL ACCEPT ACK

–

–

7

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

NOTE 2: The UE (MCPTT User) shall keep the button pressed until otherwise written.

–

–

–

–

8

The UE (MCPTT client) sends Floor Granted message.

–>

Floor Granted

–

–

9

Make the UE (MCPTT User) to release the PTT button.

–

–

–

–

10

The UE (MCPTT client) send Floor Release message.

–>

Floor Release

–

–

11

Make the MCPTT UE (MCPTT User) request upgrade of the ongoing call to Emergency call.

NOTE: This is expected to be done via a suitable implementation dependent MMI.

–

–

–

–

12

The UE (MCPTT client) sends PRIVATE CALL SETUP REQUEST message, Call type set to EMERGENCY PRIVATE CALL.

–>

PRIVATE CALL SETUP REQUEST

1

–

13

SS-UE1 (MCPTT Client) sends a PRIVATE CALL REJECT message.

<–

PRIVATE CALL REJECT

14

Make the UE (MCPTT User) to press the PTT button requesting permission to talk.

NOTE: The UE (MCPTT User) shall keep the button pressed until otherwise written.

–

–

–

–

15

Check: Does the UE (MCPTT client) send Floor Request message, Floor Indicator set to Normal call?

NOTE: The UE continues operating in the normal Private call.

–>

Floor Request

1

P

16

SS-UE1 (MCPTT Client) sends a Floor Granted message.

<–

Floor Granted

–

–

17

Make the UE (MCPTT User) to release the PTT button.

–

–

–

–

18

The UE (MCPTT client) send Floor Release message.

–>

Floor Release

–

–

19

Make the MCPTT UE (MCPTT User) request upgrade of the ongoing call to Emergency call.

NOTE: This is expected to be done via a suitable implementation dependent MMI.

–

–

–

–

20

The UE (MCPTT client) send PRIVATE CALL SETUP REQUEST message, Call type set to EMERGENCY PRIVATE CALL.

–>

PRIVATE CALL SETUP REQUEST

–

–

21

SS-UE1 (MCPTT Client) sends a PRIVATE CALL ACCEPT message.

<–

PRIVATE CALL ACCEPT

–

–

22

The UE (MCPTT client) send PRIVATE CALL ACCEPT ACK message.

–>

PRIVATE CALL ACCEPT ACK

–

–

23

Make the UE (MCPTT User) to press the PTT button requesting permission to talk.

NOTE 1: Depending on UE implementation the PTT button may already been pressed in step 19.

NOTE 2: The UE (MCPTT User) shall keep the button pressed until otherwise written.

–

–

–

–

24

The UE (MCPTT client) send Floor Granted message, Floor Indicator set to Emergency call.

–>

Floor Granted

–

–

25

Void.

–

–

–

–

26

Make the UE (MCPTT User) to release the PTT button.

–

–

–

–

27

The UE (MCPTT client) send Floor Release message.

–>

Floor Release

–

–

28

Make the UE (MCPTT User) request downgrade of the ongoing Emergency call.

NOTE: This is expected to be done via a suitable implementation dependent MMI.

–

–

–

–

–

EXCEPTION: Steps 29-31 are repeated CFP6=3 times.

–

–

–

–

29

Check: Does the UE (MCPTT client) send PRIVATE CALL EMERGENCY CANCEL message?

NOTE: It is expected that the UE

– shall initialize the counter CFP6 (emergency private call cancel retransmission) with the value set to 1

– shall start timer TFP6 (emergency private call cancel retransmission)

–>

PRIVATE CALL EMERGENCY CANCEL

2

P

30

Start TFP6 (private call request retransmission) 40 milliseconds.

–

–

–

–

31

TFP6 expires.

NOTE: It is expected that the UE considers at this moment of time the Private call being terminated.

–

–

–

–

38

Start TFP7 (waiting for any message with same call identifier) 6 sec (value chosen to facilitate the test sequence in steps 39-43).

NOTE 1: TFP7 is expected to be started after TFP6 expires and CFP6 is equal to the upper limit.

NOTE 2: Step numbering to reflect that steps 29-31 are repeated CFP6=3 times.

–

–

–

–

39

SS-UE1 (MCPTT Client) sends a PRIVATE CALL EMERGENCY CANCEL ACK message

<–

PRIVATE CALL EMERGENCY CANCEL ACK

–

–

40

Make the UE (MCPTT User) to press the PTT button requesting permission to talk.

NOTE: The UE (MCPTT User) shall keep the button pressed until otherwise written.

–

–

–

–

41

Check: Does the UE (MCPTT client) send Floor Request message in the next 2/3 TFP7 sec?

–>

Floor Request

2

F

42

Make the UE (MCPTT User) to release the PTT button.

–

–

–

–

43

TFP7 (waiting for any message with same call identifier) expires.

–

–

–

–

–

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

NOTE: Depending on UE implementation the UE may start independently ProSe release procedure.

–

–

–

–

7.2.3.3.3 Specific message contents

Table 7.2.3.3.3-1: PRIVATE CALL SETUP REQUEST (Steps 12, 20, Table 7.2.3.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.5.8.1-1.

Information Element

Value/remark

Comment

Condition

Call type

‘00000110’B

EMERGENCY PRIVATE CALL

User location

Nor present or Any value

Table 7.2.3.3.3-2: PRIVATE CALL REJECT (Step 13, Table 7.2.3.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.5.11.2-1.

Information Element

Value/remark

Comment

Condition

Reason

‘00000001’B

MEDIA FAILURE

Table 7.2.3.3.3-3: Floor Granted (Step 8, Table 7.2.3.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

‘10000×00 0000000

Bit A=1 (Normal call)

bit F=x (Queueing supported) any value

Table 7.2.3.3.3-4: Floor Request (Step 15, Table 7.2.3.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.6.2-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

Table 7.2.3.3.3-5: Floor Granted (Step 16, Table 7.2.3.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

The UE (MCPTT client) SSRC (received in the corresponding Floor Request)

Floor priority

The same as the priority included in the corresponding Floor Request, Not Present if there was no priority included

Floor Indicator

Floor Indicator

‘10000100 0000000

Bit A=1 (Normal call)

bit F=1 (Queueing supported)

Table 7.2.3.3.3-6: Floor Release (Steps 10, 18, Table 7.2.3.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

Table 7.2.3.3.3-7: Floor Request (Step 24, Table 7.2.3.3.2-1)

Derivation Path: 36.579-1 [2], Table 5.5.6.2-1 condition OFF-NETWORK.

Information Element

Value/remark

Comment

Condition

Floor Indicator

Floor Indicator

‘00010×00 0000000

Bit D=1 (Emergency call)

bit F=x (Queueing supported) any value

Table 7.2.3.3.3-8: Floor Release (Step 27, Table 7.2.3.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

‘00010×00 0000000

Bit D=1 (Emergency call)

bit F=x (Queueing supported) any value