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

(1)

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

ensure that {

when { the MCPTT User requests to initiate an MCPTT emergency alert }

then { UE (MCPTT Client) sends a GROUP EMERGENCY ALERT message and enters the "E2: Emergency state" state }

}

(2)

with { UE (MCPTT Client) in the "E2: Emergency state" state, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { the timer TFE2 (emergency alert retransmission) expires }

then { UE (MCPTT Client) retransmits the MCPTT emergency alert by sending a GROUP EMERGENCY ALERT message}

}

(3)

with { UE (MCPTT Client) in the "E2: Emergency state" state, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { the MCPTT User requests to cancel the MCPTT emergency alert }

then { UE (MCPTT Client) sends a GROUP EMERGENCY ALERT CANCEL message and enters the "E1: Not in emergency state" state }

}

7.1.9.2 Conformance requirements

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

[TS 24.379, clause 12.2.3.1]

When in state "E1: Not in emergency state", upon receiving an indication from the MCPTT user to transmit an emergency alert for an MCPTT group ID, and the values of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyAlert/Authorised" leaf node present in the user profile and "/<x>/<x>/Common/AllowedEmergencyAlert" present in group configuration as specified in 3GPP TS 24.383 [45] are set to "true", the MCPTT client:

1) shall set the stored emergency state as "true";

2) shall set the stored MCPTT group ID to the indicated MCPTT group ID;

3) shall generate a GROUP EMERGENCY ALERT message as specified in subclause 15.1.16. In the GROUP EMERGENCY ALERT message, the MCPTT client:

a) shall set the MCPTT group ID IE to the stored MCPTT group ID;

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

c) shall set the Organization name IE to own organization name; and

d) may set the User location IE with client’s current location, if requested;

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

5) shall start timer TFE2 (emergency alert retransmission); and

6) shall enter "E2: Emergency state" state.

[TS 24.379, clause 12.2.3.2]

When in state "E2: Emergency state", upon expiry of timer TFE2 (emergency alert retransmission), the MCPTT client:

1) shall generate a GROUP EMERGENCY ALERT message as specified in subclause 15.1.16. In the GROUP EMERGENCY ALERT message, the MCPTT client:

a) shall set the MCPTT group ID IE to the stored MCPTT group ID;

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

c) shall set the Organization name IE to own organization name; and

d) may set the Location IE with client’s current location, if requested; and

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

3) shall start the timer TFE2 (emergency alert retransmission); and

4) shall remain in the current state.

[TS 24.379, clause 12.2.3.5]

When in "E2: Emergency state", upon receiving an indication from the MCPTT user to cancel an emergency alert and the value of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyAlert/Cancel" leaf node present in the user profile as specified in 3GPP TS 24.383 [45] set to "true", the MCPTT client:

1) shall set the stored emergency state as "false";

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

a) shall set the MCPTT group ID IE to the stored MCPTT group ID;

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

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

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

4) shall stop timer TFE2 (emergency alert retransmission); and

5) shall enter "E1: Not in emergency state" state.

7.1.9.3 Test description

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

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

Table 7.1.9.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)

–

–

–

–

3

Make the UE (MCPTT Client) initiate an off-network emergency alert

(NOTE 1)

–

–

–

–

–

EXCEPTION: The E-UTRA/EPC actions which are related to the MCPTT off-network call establishment are described in TS 36.579-1 [2], subclause 5.4.11 ‘Generic Test Procedure for MCPTT CO communication over ProSe direct one-to-many communication out of E-UTRA coverage / Monitoring/Discoverer procedure for group member discovery / One-to-many communication’. The test sequence below shows only the MCPTT relevant messages exchanged.

–

–

–

–

4

Check: Does the UE (MCPTT client) send a GROUP EMERGENCY ALERT message?

(NOTE 2)

–>

GROUP EMERGENCY ALERT

1

P

4A

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

–

–

–

–

5

The SS-UE1 (MCPTT client) responds to the GROUP EMERGENCY ALERT by sending a GROUP EMERGENCY ALERT ACK

<–

GROUP EMERGENCY ALERT ACK

–

–

6

Timer=10s expires

–

–

–

–

7

Check: Does the UE (MCPTT client) send a GROUP EMERGENCY ALERT message?

(NOTE 2)

–>

GROUP EMERGENCY ALERT

2

P

8

Make the UE (MCPTT Client) cancel the emergency alert

(NOTE 1), (NOTE 3)

–

–

–

–

9

Check: Does the UE (MCPTT client) send a GROUP EMERGENCY ALERT CANCEL message?

(NOTE

–>

GROUP EMERGENCY ALERT CANCEL

3

P

10

The SS-UE1 (MCPTT client) responds to the GROUP EMERGENCY ALERT CANCEL by sending a GROUP EMERGENCY ALERT CANCEL ACK

<–

GROUP EMERGENCY ALERT CANCEL ACK

–

–

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

NOTE 2: Timer TFE2 (emergency alert retransmission) is started 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 MCPTT Client retransmits the GROUP EMERGENCY ALERT message.

NOTE 3: If the MCPTT User does not perform an action before the expiry of timer TFE2 (emergency alert retransmission), then the MCPTT Client will retransmit the GROUP EMERGENCY ALERT message and the remaining steps will not be valid. Timer TFE2 (emergency alert retransmission) is started 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 MCPTT Client retransmits the GROUP EMERGENCY ALERT 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.

NOTE 4: The MCPP Client stops the TFE2 (emergency alert retransmission) timer upon the sending of the GROUP EMERGENCY ALERT CANCEL message.

7.1.9.3.3 Specific message contents

None