7.1.10 Off-network / Group Call / Emergency Alert / Emergency Alert Retransmission / Cancel Emergency Alert / 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.10.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, including authorised to receive emergency alerts in off-network environment, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { UE (MCPTT Client) receives an MCPTT emergency alert via a GROUP EMERGENCY ALERT message }

then { UE (MCPTT Client) responds by sending a GROUP EMERGENCY ALERT ACK }

}

(2)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, having received an MCPTT emergency alert, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { UE (MCPTT Client) receives a GROUP EMERGENCY ALERT message from the same MCPTT Client that sent the previous GROUP EMERGENCY ALERT message, and the timer TFE1 (Emergency Alert) has yet to expire }

then { UE (MCPTT Client) shall not send a GROUP EMERGENCY ALERT ACK in response }

}

(3)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, having received an MCPTT emergency alert, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { UE (MCPTT Client) receives a GROUP EMERGENCY ALERT message from the same MCPTT Client that sent the previous GROUP EMERGENCY ALERT message, and the timer TFE1 (Emergency Alert) expired }

then { UE (MCPTT Client) responds by sending a GROUP EMERGENCY ALERT ACK }

}

(4)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, having received an MCPTT emergency alert, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { UE (MCPTT Client) receives a GROUP EMERGENCY ALERT CANCEL message from the same MCPTT Client that sent the previous GROUP EMERGENCY ALERT message }

then { UE (MCPTT Client) responds by sending a GROUP EMERGENCY ALERT CANCEL ACK }

}

7.1.10.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379 clauses 12.2.3.3, 12.2.3.4, 12.2.3.6, 12.2.3.7. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 12.2.3.3]

When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCPTT user ID IE not stored in the list of users in emergency, the MCPTT client:

1) shall store the Originating MCPTT user ID IE and location IE in the list of users in emergency;

2) shall generate a GROUP EMERGENCY ALERT ACK message as specified in subclause 15.1.17. In the GROUP EMERGENCY ALERT ACK message, the MCPTT client:

a) shall set the MCPTT group ID IE to the MCPTT group ID IE of the received GROUP EMERGENCY ALERT message;

b) shall set the Sending MCPTT user ID IE to own MCPTT user ID; and

c) shall set the Originating MCPTT user ID IE to the Originating MCPTT user ID IE of the received GROUP EMERGENCY ALERT message; and

3) shall send the GROUP EMERGENCY ALERT ACK message as specified in subclause 10.2.1.1.1;

4) shall start timer TFE1 (Emergency Alert); and

5) shall remain in the current state.

NOTE: Each instance of timer TFE1 is per MCPTT user ID.

[TS 24.379, clause 12.2.3.4]

When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCPTT user ID IE stored in the list of users in emergency, the MCPTT client:

1) may update the stored location of the user with the received Location IE;

2) shall restart the associated timer TFE1 (Emergency Alert); and

3) shall remain in the current state.

[TS 24.379, clause 12.2.3.6]

When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT CANCEL message with the Originating MCPTT user ID IE stored in the list of users in emergency, the MCPTT client:

1) shall remove the MCPTT user ID and associated location information from the stored list of users in emergency;

2) shall generate a GROUP EMERGENCY ALERT CANCEL ACK message as specified in subclause 15.1.19. In the GROUP EMERGENCY ALERT CANCEL ACK message, the MCPTT client:

a) shall set the MCPTT group ID IE to the MCPTT group ID IE of the received GROUP EMERGENCY ALERT CANCEL message; and

b) shall set the Sending MCPTT user ID IE to own MCPTT user ID; and

c) shall set the Originating MCPTT user ID IE to the Originating MCPTT user ID IE of the received GROUP EMERGENCY ALERT message;

3) shall send the GROUP EMERGENCY ALERT CANCEL ACK message as specified in subclause 10.2.1.1.1;

4) shall stop the associated timer TFE1 (Emergency Alert); and5) shall remain in the current state.

[TS 24.379, clause 12.2.3.7]

When in state "E1: Not in emergency state" or in "E2: Emergency state", upon expiry of timer TFE1 (Emergency Alert) associated with a stored MCPTT user ID, the MCPTT client:

1) shall remove the MCPTT user ID and associated location information from the stored list of users in emergency; and

2) shall remain in the current state.

7.1.10.3 Test description

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

– TFE1(emergency alert) set to 15 seconds ("/<x>/OffNetwork/Timers/TFE1" 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.10.3.2 Test procedure sequence

Table 7.1.10.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 EMERGENCY ALERT

(NOTE 2), (NOTE 3), (NOTE 4)

<–

GROUP EMERGENCY ALERT

–

–

3A

SS starts Timer=10s (TFE2 (emergency alert retransmission))

–

–

–

–

3B

SS starts Timer=15s (TFE1 (Emergency Alert))

4

Void

–

–

–

–

5

Check: Does the UE (MCPTT Client) respond to the GROUP EMERGENCY ALERT by sending a GROUP EMERGENCY ALERT ACK?

–>

GROUP EMERGENCY ALERT ACK

1

P

5A

Timer=10s expires (TFE2 (emergency alert retransmission))

–

–

–

–

6

Upon expiry of the timer TFE2 (emergency alert retransmission), the SS-UE1 (MCPTT client) retransmits the emergency alert by sending a GROUP EMERGENCY ALERT

<–

GROUP EMERGENCY ALERT

–

–

6A

SS starts Timer=10s (TFE2 (emergency alert retransmission))

–

–

–

–

7

Check: Does the UE (MCPTT Client) respond to the GROUP EMERGENCY ALERT by sending in the next 5 seconds a GROUP EMERGENCY ALERT ACK?

–>

GROUP EMERGENCY ALERT ACK

2

F

7A

Wait 5 seconds for GROUP EMERGENCY ALERT ACK

–

–

–

–

8

Timer=15s expires (TFE1 (Emergency Alert))

(NOTE 5)

–

–

–

–

8A

Wait 5 seconds for expiration of timer TFE2 (emergency alert retransmission)

8B

Timer=10s expires (TFE2 (emergency alert retransmission))

–

–

–

–

9

SS-UE1 (MCPTT client) sends a GROUP EMERGENCY ALERT

(NOTE 4)

<–

GROUP EMERGENCY ALERT

–

–

10

Void

–

–

–

–

11

Check: Does the UE (MCPTT Client) respond to the GROUP EMERGENCY ALERT by sending a GROUP EMERGENCY ALERT ACK?

–>

GROUP EMERGENCY ALERT ACK

3

P

12

SS-UE1 (MCPTT client) sends a GROUP EMERGENCY ALERT

<–

GROUP EMERGENCY ALERT CANCEL

–

–

13

Void

–

–

–

–

14

Check: Does the UE (MCPTT Client) respond to the GROUP EMERGENCY ALERT CANCEL by sending a GROUP EMERGENCY ALERT CANCEL ACK?

–>

GROUP EMERGENCY ALERT CANCEL ACK

4

P

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

NOTE 2: Timer TFE1(emergency alert) is started by the MCPTT Client upon the receiving of the GROUP EMERGENCY ALERT message. Timer TFE1 (emergency alert)=15s, as defined as defined in the Pre-test conditions. At the expire of TFE1, the MCPTT Client assumes the end of the emergency state and removes the associated user from the list.

NOTE 3: Timer TFE2 (emergency alert retransmission) is started by the SS upon the sending of the GROUP EMERGENCY ALERT message. Timer TFE2 (emergency alert retransmission)=10s, as defined in TS 36.579-1 [2], Table 5.5.8.1-1. At the expire of TFE2, the SS retransmits the GROUP EMERGENCY ALERT message.

NOTE 4: The UE (MCPTT Client) stores the Originating MCPTT user ID IE in the list of users in emergency.

NOTE 5: Upon expiry of the timer TFE1 (Emergency Alert), the UE (MCPTT Client) removes the MCPTT user ID from the stored list of users in emergency

7.1.10.3.3 Specific message contents

None