7.1.7 Off-network / Group Call / Emergency Call / Imminent Peril Call / 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.7.1 Test Purpose (TP)

(1)

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

ensure that {

when { the MCPTT User requests the establishment of an MCPTT emergency group call }

then { UE (MCPTT Client) requests an MCPTT emergency group call by sending a GROUP CALL ANNOUNCEMENT message, and respects the floor control imposed by the floor control entity/arbitrator }

}

(2)

with { UE (MCPTT Client) registered and authorised for MCPTT Service, including authorised to initiate/cancel imminent peril group calls in off-network environment, and the UE (MCPTT Client) is in an off-network environment }

ensure that {

when { the MCPTT User requests the establishment of an MCPTT imminent peril group call }

then { UE (MCPTT Client) requests an MCPTT imminent peril group call by sending a GROUP CALL ANNOUNCEMENT message, and respects the floor control imposed by the floor control entity/arbitrator }

}

7.1.7.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379 clauses 10.2.2.4.2.1, 10.2.3.4.2, 10.2.3.4.6, 10.2.2.4.3.1, TS 24.380 clause 7.2.3.2.2. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 10.2.2.4.2.1]

When in the "S1: start-stop" state, upon an indication from an MCPTT user to initiate a group call for an MCPTT group ID, the MCPTT client:

1) shall store the MCPTT group ID as the MCPTT group ID of the call;

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

3) shall generate a GROUP CALL PROBE message as specified in subclause 15.1.2. In the GROUP CALL PROBE message, the MCPTT client:

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

4) shall send the GROUP CALL PROBE message as specified in subclause 10.2.1.1.1;

5) shall start timer TFG3 (call probe retransmission);

6) shall start timer TFG1 (wait for call announcement); and

7) shall enter the "S2: waiting for call announcement" state.

[TS 24.379, clause 10.2.3.4.2]

When in the "T0: waiting for the call to establish " state, upon an indication from an MCPTT user to initiate a group call probe for an MCPTT group, the MCPTT client:

1) if the stored emergency state associated with emergency alert state machine described in 12.2.2.2 is set to "true" and the value of "/<x>/<x>/Common/AllowedEmergencyCall" leaf node present in group configuration as specified in 3GPP TS 24.383 [45] is set to "true":

a) shall set the stored current call type to "EMERGENCY GROUP CALL"; and

b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency group call as described in 3GPP TS 24.383 [45];

2) if the stored emergency state associated with emergency alert state machine described in 12.2.2.2 is set to "false", and:

a) if the user initiates an MCPTT emergency call and the values of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyCall/Enabled" leaf node present in the user profile and "/<x>/<x>/Common/AllowedEmergencyCall" leaf node present in group configuration as specified in 3GPP TS 24.383 [45] are set to "true":

i) shall set the stored current call type to "EMERGENCY GROUP CALL"; and

ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency group call as described in 3GPP TS 24.383 [45];

b) if the user initiates an MCPTT imminent peril group call and the values of "/<x>/<x>/Common/MCPTTGroupCall/ImminentPerilCall/Authorised" leaf node present in the user profile "/<x>/<x>/Common/AllowedImminentPerilCall " leaf node present in group configuration as specified in 3GPP TS 24.383 [45] are set to "true":

i) shall set the stored current call type to "IMMINENT PERIL GROUP CALL"; and

ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network imminent peril group call as described in 3GPP TS 24.383 [45]; and

c) if the user initiates an MCPTT group call which is not an MCPTT emergency call and which is not an MCPTT imminent peril group call:

i) shall set the stored current call type to "BASIC GROUP CALL"; and

ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network basic group call as described in 3GPP TS 24.383 [45];

3) shall set the stored last call type change time to current UTC time;

4) shall set the last user to change call type to own MCPTT user ID; and

5) shall remain in "T0: waiting for the call to establish" state.

[TS 24.379, clause 10.2.3.4.6]

When in state "T0: waiting for the call to establish", if:

a) the MCPTT user accepts the call when MCPTT user acknowledgement is required; or

b) the MCPTT client sends a GROUP CALL ANNOUNCEMENT message on expiry of timer TFG1 (wait for call announcement) associated with the basic call control state machine;

the MCPTT client:

1) if the stored current call type is set to "EMERGENCY GROUP CALL"

a) shall start timer TFG13 (implicit downgrade emergency) with value as specified in subclause 10.2.3.4.1.1; and

b) shall enter "T1: in-progress emergency group call" state;

2) if the stored current call type is set to "IMMINENT PERIL GROUP CALL"

a) shall start timer TFG14 (implicit downgrade imminent peril) with value as specified in subclause 10.2.3.4.1.2; and

b) shall enter "T3: in-progress imminent peril group call" state; or

3) if the stored current call type is set to "BASIC GROUP CALL"

a) shall enter "T2: in-progress basic group call" state.

[TS 24.379, clause 10.2.2.4.3.1]

When in the "S2: waiting for call announcement" state, upon expiry of timer TFG1 (wait for call announcement), the MCPTT client:

1) shall stop timer TFG3 (call probe retransmission), if running;

2) shall generate an SDP body as specified in subclause 10.2.1.1.2 and store it as the SDP body of the call;

3) shall generate a random number with uniform distribution between 0 and 65535 and store it as the call identifier of the call;

4) shall select refresh interval value and store it as the refresh interval of the call;

5) shall store own MCPTT user ID as the originating MCPTT user ID of the call;

6) shall store the current UTC time as the call start time of the call;

7) shall generate a GROUP CALL ANNOUNCEMENT message as specified in subclause 15.1.3. In the GROUP CALL ANNOUNCEMENT message, the MCPTT client:

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

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

c) shall set the Refresh interval IE to the stored refresh interval of the call;

d) shall set the SDP IE to the stored SDP body of the call;

e) shall set the Originating MCPTT user ID IE to the stored originating MCPTT user ID of the call;

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

g) shall set the Call start time IE to the stored call start time of the call;

h) shall set the Last call type change time IE to the stored last call type change time of the call associated with call type control state machine;

i) shall set the Last user to change call type IE to last user to change call type associated with call type control state machine; and

j) may include the Confirm mode indication IE;

8) shall send the GROUP CALL ANNOUNCEMENT message as specified in subclause 10.2.1.1.1;

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

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

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

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

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

Note: In this release of the present document, the refresh interval of the call is fixed to 10 seconds.

[TS 24.380, clause 7.2.3.2.2]

When an MCPTT call is established with session announcement including an explicit floor request, the originating floor participant:

1. shall create an instance of a floor participant state transition diagram for basic operation state machine;

2. shall send Floor Granted message towards other floor participants. The Floor Granted message:

a. shall include the granted priority in the Floor priority field;

b. shall include the MCPTT user’s own MCPTT ID in the User ID field; and

c. if the floor request is a broadcast group call, system call, emergency call or an imminent peril call, shall include a Floor Indicator field indicating the relevant call types;

3. shall set the stored SSRC of the current florr arbitrator to its own SSRC; and

4. shall enter ‘O: has permission’ state.

7.1.7.3 Test description

7.1.7.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.7.3.2 Test procedure sequence

Table 7.1.7.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 group call

(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

The UE (MCPTT client) sends a GROUP CALL PROBE message to determine the current call status of the group

–>

GROUP CALL PROBE

–

–

–

EXCEPTION: Step 5 is executed a total of 3 times

–

–

–

–

5

At the expiration of TFG3 (call probe retransmission), the UE (MCPTT Client) send a retransmission of the GROUP CALL PROBE sent in step 4

–>

GROUP CALL PROBE

–

–

6

Check: At the expiration of TFG1 (wait for call announcement), and after receiving no response to the GROUP CALL PROBE, does the UE (MCPTT Client) send a GROUP CALL ANNOUNCEMENT message to initiate an off-network emergency group call?

–>

GROUP CALL ANNOUNCEMENT

1

P

7

The SS-UE1 (MCPTT client) sends a GROUP CALL ACCEPT accepting the GROUP CALL ANNOUNCEMENT

<–

GROUP CALL ACCEPT

–

–

8

Check: Does the UE (MCPTT Client) send a Floor Granted message towards the other floor participants?

–>

Floor Granted

1

P

9

Make the UE (MCPTT User) release the floor

(NOTE 1), (NOTE 2)

–

–

–

–

10

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

–>

Floor Release

1

P

11

Make the UE (MCPTT Client) release the emergency group call

(NOTE 1)

–

–

–

–

12

Void

–

–

–

–

13

Void

–

–

–

–

14

Make the UE (MCPTT Client) initiate an off-network imminent peril group call

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

–

–

–

–

15

Check: Does the UE (MCPTT client) send a GROUP CALL PROBE message to determine the current call status of the group?

–>

GROUP CALL PROBE

–

–

–

EXCEPTION: Step 16 is executed a total of 3 times

–

–

–

–

16

Check: At the expiration of TFG3 (call probe retransmission), does the UE (MCPTT Client) send a retransmission of the GROUP CALL PROBE sent in step 15?

–>

GROUP CALL PROBE

–

–

17

Check: At the expiration of TFG1 (wait for call announcement), and after receiving no response to the GROUP CALL PROBE, does the UE (MCPTT Client) send a GROUP CALL ANNOUNCEMENT message to initiate an off-network imminent peril group call?

–>

GROUP CALL ANNOUNCEMENT

2

P

18

The SS-UE1 (MCPTT client) sends a GROUP CALL ACCEPT accepting the GROUP CALL ANNOUNCEMENT

<–

GROUP CALL ACCEPT

–

–

19

Check: Does the UE (MCPTT Client) send a Floor Granted message towards the other floor participants?

–>

Floor Granted

2

P

20

Make the UE (MCPTT User) release the floor

(NOTE 1), (NOTE 2)

–

–

–

–

21

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

–>

Floor Release

2

P

22

Make the UE (MCPTT Client) release the imminent peril group call

(NOTE 1)

–

–

–

–

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

NOTE 2: If the MCPTT User does not perform an action before timer T207 (Stop talking) expires, then the MCPTT Client will enter the ‘O: ‘Silence’ state per 24.380 [10] and the remaining steps will not be valid. Timer T207 (Stop talking) is started upon the expiration of time T206 (Stop talking warning), which is started at the sending of the Floor Granted message. T207 (Stop talking)=3s, as defined in TS 24.380 [10], Table 11.1.2-1. And T206 (Stop talking warning)=27s, as defined in TS 24.380 [10], Table 11.1.2-1. 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.

7.1.7.3.3 Specific message contents

Table 7.1.7.3.3-1: GROUP CALL ANNOUNCEMENT (step 6, Table 7.1.7.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Call type

"00000011"

Emergency Group Call

Table 7.1.7.3.3-2: GROUP CALL ANNOUNCEMENT (step 17, Table 7.1.7.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Call type

"00000100"

Imminent Peril Group Call

Table 7.1.7.3.3-3: GROUP CALL ACCEPT (step 7, Table 7.1.7.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Call type

"00000011"

Emergency Group Call

Table 7.1.7.3.3-4: GROUP CALL ACCEPT (step 18, Table 7.1.7.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Call type

"00000100"

Imminent Peril Group Call

Table 7.1.7.3.3-5: Floor Granted (step 8, Table 7.1.7.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.6.3-1 condition OFF-NETWORK

Information Element

Value/remark

Comment

Condition

Duration

Duration

any allowed value

Floor Indicator

Floor Indicator

‘00010X0000000000’

bit D=1 (Emergency call)

bit F=X (Queueing supported) any value

Table 7.1.7.3.3-6: Floor Granted (step 19, Table 7.1.7.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.6.3-1 condition OFF-NETWORK

Information Element

Value/remark

Comment

Condition

Duration

Duration

any allowed value

Floor Indicator

Floor Indicator

‘00001X0000000000’

bit E=1 (Imminent peril call)

bit F=X (Queueing supported) any value

Table 7.1.7.3.3-7: Floor Release (step 10, Table 7.1.7.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.6.5-1 condition OFF-NETWORK

Information Element

Value/remark

Comment

Condition

Floor Indicator

Floor Indicator

‘00010X0000000000’

bit D=1 (Emergency call)

bit F=X (Queueing supported) any value

Table 7.1.7.3.3-8: Floor Release (step 21, Table 7.1.7.3.2-1)

Derivation Path: TS 36.579-1 [2], Table 5.5.6.5-1 condition OFF-NETWORK

Information Element

Value/remark

Comment

Condition

Floor Indicator

Floor Indicator

‘00001X0000000000’

bit E=1 (Imminent peril call)

bit F=X (Queueing supported) any value