7.1.13 Off-network / Group Call / Broadcast Group Call / MCPTT User Ack Required / MCPTT User Reject / MCPTT User Accept / MCPTT User Releases Call / 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.13.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, including authorised to receive broadcast calls in off-network environment, and the UE (MCPTT Client) configured that MCPTT user acknowledgement is required upon a terminating call request reception, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { UE (MCPTT Client) receives a GROUP CALL BROADCAST message with a Call identifier that has not been previously received}

then { UE (MCPTT Client) enters the "B3: pending user action" state and requests the user to reject or accept the incoming broadcast call }

}

(2)

with { UE (MCPTT Client) having received a GROUP CALL BROADCAST message }

ensure that {

when { the MCPTT User rejects the incoming off-network broadcast call}

then { UE (MCPTT Client) enters the "B4: ignoring same call ID" state and ignores subsequent GROUP CALL BROADCAST messages that match with the stored Call identifier }

}

7.1.13.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379 clauses 10.3.2.4.2, 10.3.2.4.4, 10.3.2.4.8, 10.3.2.4.3, 10.3.2.4.6, 10.3.2.4.10, 10.3.2.4.11. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 10.3.2.4.2]

When in the "B1: start-stop" state, upon receiving a GROUP CALL BROADCAST message with the Call identifier IE not matching any in-progress broadcast group call, the MCPTT client:

1) shall store the value of the Call identifier IE of the GROUP CALL BROADCAST message as the call identifier of the call;

2) shall store the value of the Call type IE of the GROUP CALL BROADCAST message as the received current call type;

3) shall store the value of the SDP IE of the GROUP CALL BROADCAST message as the SDP body of the call;

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

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

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

i) shall start timer TFB3 (waiting for the user); and

ii) shall enter the "B3: pending user action" state; and

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

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

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

iii) shall start timer TFB1 (max duration); and

iv) shall enter the "B2: in-progress broadcast group call" state.

[TS 24.379, clause 10.3.2.4.4]

When in the "B3: pending user action" state, upon an indication from the MCPTT user to reject the incoming broadcast group call, the MCPTT client:

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

2) shall start timer TFB1 (max duration); and

3) shall enter the "B4: ignoring same call ID" state.

[TS 24.379, clause 10.3.2.4.8]

When in the "B2: in-progress broadcast group call" state or "B4: ignoring same call ID" state, upon receiving GROUP CALL BROADCAST END message with the same Call identifier IE as the stored call identifier, the MCPTT client:

1) shall release media session;

2) shall stop timer TFB1 (max duration);

3) shall clear the stored call identifier;

4) shall stop floor control, if running; and

5) shall enter the "B1: start-stop" state.

[TS 24.379, clause 10.3.2.4.3]

When in the "B3: pending user action" state, upon indication from the MCPTT user to accept the incoming broadcast 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 described specified in subclause 7.2 in 3GPP TS 24.380 [5];

3) shall stop timer TFB3 (waiting for the user);

4) shall start timer TFB1 (max duration); and

5) shall enter the "B2: in-progress broadcast group call" state.

[TS 24.379, clause 10.3.2.4.6]

When in the "B2: in-progress broadcast group call" state, upon an indication from the terminating MCPTT user to release the in-progress broadcast group call, the MCPTT client:

1) shall release the media session;

2) shall stop floor control; and

3) shall enter the "B4: ignoring same call ID" state.

[TS 24.379, clause 10.3.2.4.10]

When in the "B4: ignoring same call ID" state, upon receiving GROUP CALL BROADCAST message and if the call identifier in GROUP CALL BROADCAST message matches with the stored call identifier the MCPTT client:

1) shall restart timer TFB1 (max duration); and

2) shall remain in "B4: ignoring same call ID" state.

[TS 24.379, clause 10.3.2.4.11]

When in the "B2: in-progress broadcast group call" state or "B4: ignoring same call ID" state, upon expiry of timer TFB1 (max duration) the MCPTT client:

1) shall release the media session;

2) shall clear the stored call identifier;

3) shall stop floor control, if running; and

4) shall enter the "B1: start-stop" state.

7.1.13.3 Test description

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

– TFB1 (max duration) set to 60 seconds ("/<x>/OffNetwork/Timers/TFB1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [13])

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

Table 7.1.13.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 BROADCAST

(NOTE 2)

<–

GROUP CALL BROADCAST

–

–

4

Check: Does the UE (MCPTT Client) enter the "B3: pending user action" state and notifies the MCPTT User of an incoming broadcast call?

(NOTE 3).

–

–

1

P

5

Make the UE (MCPTT Client) reject the incoming off-network broadcast call

(NOTE 1), (NOTE 4)

–

–

–

–

6

Void

–

–

–

–

7

SS-UE1 (MCPTT client) sends a GROUP CALL BROADCAST with the same Call identifier as used in step 3

<–

GROUP CALL BROADCAST

–

–

8

Check: Does the UE (MCPTT Client) notify the MCPTT User in the next 60 seconds of an incoming broadcast call?

(NOTE 3)

–

–

2

F

9

Wait 60 seconds (TFB1 (max duration))

–

–

–

–

10

Void

–

–

3

P

11

SS-UE1 (MCPTT client) sends a GROUP CALL BROADCAST with a different Call identifier as used in step 3

<–

GROUP CALL BROADCAST

–

–

12

Check: Does the UE (MCPTT Client) notify the MCPTT User of an incoming broadcast call?

(NOTE 3)

–

–

1

P

13

Make the UE (MCPTT Client) accept the incoming off-network broadcast call

(NOTE 1), (NOTE 5)

–

–

–

–

14

Void

–

–

4

P

15

Void

–

–

–

–

16

Void

–

–

–

–

17

SS-UE1 (MCPTT client) sends a GROUP CALL BROADCAST END

(NOTE 6)

<–

GROUP CALL BROADCAST END

–

–

18

Void

–

–

3

P

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

NOTE 2: Timer TFB3 (waiting for the user) is started by the MCPTT Client upon the receiving of the GROUP CALL BROADCAST message. Timer TFB3 (waiting for the user)=20s, as defined in TS 36.579-1 [2], Table 5.5.8.1-1. At the expire of TFB3 (waiting for the user), the MCPTT Client will terminate the incoming call notification.

NOTE 3: Notification to the MCPTT User that there is an incoming call requiring user approval or rejection is expected to be done via a suitable implementation dependent MMI

NOTE 4: If the MCPTT User does not perform an action before timer TFB3 (waiting for the user) expires, then, the MCPTT Client will terminate the incoming call notification. Timer TFB1 (max duration) is started upon the MCPTT User rejecting the terminating call. Timer TFB1 (max duration)=60s, as defined in the Pre-test conditions. The MCPTT Client stops timer TFB3 (waiting for the user) upon rejecting the call. If during test execution it is found that the specified timer(s) value(s) are not large enough, then new value(s) need to be specified.

NOTE 5: Timer TFB1 (max duration) is started upon the MCPTT User accepting the terminating call. Timer TFB1 (max duration)=60s, as defined in the Pre-test conditions. The MCPTT Client stops timer TFB3 (waiting for the user).

NOTE 6: The MCPTT Client stops stop timer TFB1 (max duration).

7.1.13.3.3 Specific message contents

Table 7.1.13.3.3-1: GROUP CALL BROADCAST (steps 7, 11, Table 7.1.13.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Call identifier

Use the same Call identifier as used in the GROUP CALL BROADCAST message sent in step 2