7.1.5 Off-network / Group Call / MCPTT User Acknowledgement Required / Without Confirm Indication / MCPTT User Reject / MCPTT User Accept / Client Terminated (CT)

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

7.1.5.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, including authorised to receive group calls in off-network environment, and the UE (MCPTT Client) is configured such that user acknowledgement is required upon a terminating call request reception, and the UE (MCPTT Client) is in an off-network environment and the UE (MCPTT Client) receives an off-network group call request via a GROUP CALL ANNOUNCEMENT message that does not contains the Confirm mode indication IE, and the MCPTT User accepts the call }

ensure that {
when { the MCPTT User requests the floor }

then { the UE (MCPTT Client) sends a Floor Request nessage to the floor participants and respects the floor control imposed by the floor control entity/arbitrator }

}

7.1.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379 clauses 10.2.2.4.3.3, 10.2.2.4.3.7, 10.2.2.4.3.5. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 10.2.2.4.3.3]

When in the "S1: start-stop" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE not matching MCPTT group ID of the call stored for other state machines, the MCPTT client:

1) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;

2) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;

3) shall store the value of the Originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the originating MCPTT user ID of the call;

4) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;

5) shall store the value of the MCPTT group ID IE of the GROUP CALL ANNOUNCEMENT message as the MCPTT group ID of the call;

6) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;

7) shall create a call type control state machine as described in subclause 10.2.3.2;

8) if the terminating UE is configured that the terminating MCPTT user acknowledgement is required upon a terminating call request reception:

a) shall start timer TFG4 (waiting for the user);

b) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE, shall enter the "S5: pending user action with confirm indication" state; and

c) if the GROUP CALL ANNOUNCEMENT message does not contains the Confirm mode indication IE, shall enter the "S4: pending user action without confirm indication" state; and

9) if the terminating UE is configured that the terminating MCPTT user acknowledgement is not required upon a terminating call request reception:

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

b) shall start floor control as terminating floor participant as specified in subclause 7.2 in 3GPP TS 24.380 [5];

c) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE:

i) shall generate a GROUP CALL ACCEPT message as specified in subclause 15.1.4. In the GROUP CALL ACCEPT message, the MCPTT client:

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

B) shall set the Sending MCPTT user ID IE to own MCPTT user id;

C) shall set the Call type IE to the stored current call type associated with the call type control state machine; and

D) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and

ii) shall send the GROUP CALL ACCEPT message as specified in subclause 10.2.1.1.1;

d) shall start timer TFG6 (max duration) with value as specified in subclause 10.2.2.4.1.2;

e) shall start timer TFG2 (call announcement) with value as specified in subclause 10.2.2.4.1.1.1; and

f) shall enter the "S3: part of ongoing call" state.

[TS 24.379, clause 10.2.2.4.3.7]

When in the "S5: pending user action with confirm indication" state or the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to reject the incoming group call, the MCPTT client:

1) shall stop timer TFG4 (waiting for the user);

2) shall start timer TFG5 (not present incoming call announcements); and

3) shall enter the "S6: ignoring incoming call announcements" state.

[TS 24.379, clause 10.2.2.4.3.5]

When in the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to accept the incoming group call, the MCPTT client:

1) shall establish a media session based on the stored SDP body of the call;

2) shall start floor control as terminating floor participant as specified in subclause 7.2 in 3GPP TS 24.380 [5];

3) shall start timer TFG6 (max duration) with value as specified in subclause 10.2.2.4.1.2;

4) shall start timer TFG2 (call announcement) with value as specified in subclause 10.2.2.4.1.1.1; and

5) shall enter the "S3: part of ongoing call" state.

7.1.5.3 Test description

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

– 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 UE has performed the Generic Test Procedure for MCPTT UE registration as specified in TS 36.579-1 [2], subclause 5.4.2.

– UE (MCPTT Client) is configured such that user acknowledgement is required upon a terminating call request reception

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

– UE States at the end of the preamble

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

7.1.5.3.2 Test procedure sequence

Table 7.1.5.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 1)

–

–

–

–

–

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.10 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-many communication out of E-UTRA coverage / Announcing/Discoveree procedure for group member discovery / One-to-many communication’. The test sequence below shows only the MCPTT relevant messages exchanged.

–

–

–

–

3

SS-UE1 (MCPTT client) sends a GROUP CALL ANNOUNCEMENT

(NOTE 2)

<–

GROUP CALL ANNOUNCEMENT

–

–

4

Void

–

–

–

–

5

While the UE (MCPTT Client) is in the "S4: pending user action without confirm indication" state, make the UE (MCPTT Client) reject the call request

(NOTE 1), (NOTE 3)

–

–

–

–

6

Void

–

–

–

–

7

Void

–

–

–

–

–

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.10 ‘Generic Test Procedure for MCPTT CT communication over ProSe direct one-to-many communication out of E-UTRA coverage / Announcing/Discoveree procedure for group member discovery / One-to-many communication’. The test sequence below shows only the MCPTT relevant messages exchanged.

–

–

–

–

8

SS-UE1 (MCPTT client) sends a GROUP CALL ANNOUNCEMENT

(NOTE 2)

<–

GROUP CALL ANNOUNCEMENT

–

–

9

Void

–

–

–

–

10

While the UE (MCPTT Client) is in the "S4: pending user action without confirm indication" state, make the UE (MCPTT Client) accept the call request

(NOTE 1), (NOTE 3)

–

–

–

–

10A

Make the UE (MCPTT Client) request the floor

(NOTE 1)

–>

Floor Request

11

Check: Does the UE (MCPTT Client) send a Floor Request message to the floor participants?

–

–

1

P

11A

The SS-UE1 (MCPTT client) responds with a Floor Deny message

<–

Floor Deny

–

–

12

Make the UE (MCPTT Client) release the group call

(NOTE 1)

–

–

–

–

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

NOTE 2: The UE (MCPTT Client) enters the "S4: pending user action without confirm indication" state

NOTE 3: If the MCPTT User does not act before the expiration of timer TFG4 (waiting for the user), then the MCPTT Client will enter the "S6: ignoring incoming call announcements" state and the remaining steps will not be valid. Timer TFG4 (waiting for the user)=20s as defined in TS 36.579-1 [2], Table 5.5.8.1-1 and is started upon the receiving of the GROUP CALL ANNOUNCEMENT message. If during test execution it is found that the specified timer value is not large enough, then a new value needs to be specified.

7.1.5.3.3 Specific message contents

Table 7.1.5.3.3-1: GROUP CALL ANNOUNCEMENT (steps 3, 8, Table 7.1.5.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.5.2.2-1

Information Element

Value/remark

Comment

Condition

Confirm mode indication

Not present

The terminating MCPTT client is expected to confirm call acceptance