7.1.6 Off-network / Group Call / Merge Two Calls

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

7.1.6.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) having established an off-network MCPTT Pre-arranged Group Call }

ensure that {

when { the UE (MCPTT Client) receives a GROUP CALL ANNOUNCEMENT message with the same call type as the current call, the same start time as the current call, but with a lower Call identifier IE }

then { UE (MCPTT Client) merges the two calls and restarts floor control as a terminating floor participant and respects the floor control imposed by the floor control entity/arbitrator }

}

7.1.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.379 clause 10.2.2.4.6.1, TS 24.380 clause 7.2.3.2.3. Unless otherwise stated these are Rel-13 requirements.

[TS 24.379, clause 10.2.2.4.6.1]

When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call and:

1) the Originating MCPTT user ID IE is different from the stored originating MCPTT user ID of the call; or

2) the Call identifier IE is different from the stored call identifier of the call;

then:

1) if the stored current call type associated with the call type control state machine is "BASIC GROUP CALL" and the value of the Call type IE of GROUP CALL ANNOUNCEMENT message is either "IMMINENT PERIL GROUP CALL" or "EMERGENCY GROUP CALL";

2) if the stored current call type associated with the call type control state machine is "IMMINENT PERIL GROUP CALL" and the value of the Call type IE of GROUP CALL ANNOUNCEMENT message is "EMERGENCY GROUP CALL";

3) if the stored current call type associated with the call type control state machine being equal to the Call type IE of the GROUP CALL ANNOUNCEMENT message and the Call start time IE of the GROUP CALL ANNOUNCEMENT message being lower than the stored call start time of the call; or

4) if the stored current call type associated with the call type control state machine being equal to the Call type IE of the GROUP CALL ANNOUNCEMENT message and the Call start time IE of the GROUP CALL ANNOUNCEMENT message being equal to the stored call start time of the call and the Call identifier IE of the GROUP CALL ANNOUNCEMENT message being lower than the stored call identifier of the call;

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 Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;

6) shall adjust the media session based on the stored SDP body of the call and restart floor control as terminating floor participant as specified in subclause 7.2 in 3GPP TS 24.380 [5];

7) shall stop timer TFG6 (max duration);

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

9) shall stop timer TFG2 (call announcement); and

10) shall start timer TFG2 (call announcement) with value according to rules and procedures as specified in subclause 10.2.2.4.1.1.1; and

11) shall remain in the "S3: part of ongoing call" state.

[TS 24.380, clause 7.2.3.2.3]

When an MCPTT call is established the terminating floor participant:

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

2. shall start timer T230 (Inactivity); and

3. shall enter ‘O: silence’ state.

7.1.6.3 Test description

7.1.6.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.6.3.2 Test procedure sequence

Table 7.1.6.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 basic 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

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

(NOTE 2)

–>

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) sends a retransmission of the GROUP CALL PROBE sent in step 4

–>

GROUP CALL PROBE

–

–

6

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

–>

GROUP CALL ANNOUNCEMENT

–

–

7

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

<–

GROUP CALL ACCEPT

–

–

8

The UE (MCPTT Client) sends a Floor Granted message towards the other floor participants

–>

Floor Granted

–

–

9

Void

–

–

–

–

10

The SS-UE1 (MCPTT client) sends a GROUP CALL ANNOUNCEMENT message with the same call type as the current call, the same start time as the current call, but with a lower Call identifier IE

<–

GROUP CALL ANNOUNCEMENT

–

–

11

The SS-UE1 (MCPTT client) sends a Floor Granted message to the UE (MCPTT Client)

(NOTE 3)

<–

Floor Granted

–

–

12

Void

–

–

–

–

13

Make the UE (MCPTT User) request the floor

(NOTE 4)

–

–

–

–

14

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

–>

Floor Request

1

P

15

The SS-UE1 (MCPTT client) sends a Floor Granted message granting the floor to the UE (MCPTT Client)

<–

Floor Granted

–

–

16

Make the UE (MCPTT User) release the floor (NOTE 1), (NOTE5)

–

–

–

–

17

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

–>

Floor Release

1

P

18

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: Timer TFG3 (call probe retransmission)=40ms as defined in TS 36.579-1 [2], Table 5.5.8.1-1 and TFG1 (wait for call announcement)=150ms as defined in TS 36.579-1 [2], Table 5.5.8.1-1 are started upon the sending of the GROUP CALL PROBE message

NOTE 3: The UE (MCPTT Client) merges the 2 calls and relinquishes floor control to the sender of the GROUP CALL ANNOUNCEMENT in step 10

NOTE 4: If the MCPTT User does not perform an action before timer T230 (Inactivity) expires, then the MCPTT Client will enter the ‘O: ‘Start-stop” state per 24.380 [10] and the remaining steps will not be valid. Timer T230 (Inactivity) is started upon the receiving of the Floor Granted message. Timer T230 (Inactivity)=10s, as defined in TS 36.579-1 [2], Table 5.5.8.1-1. 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 5: If the MCPTT User does not release the floor before timer T207 (Stop talking) expires, then the MCPTT Client will enter the ‘O: silence’ state per TS 24.380 [10] and the remaining steps will not be valid. Timer T206 (Stop talking warning) is started upon the receiving of the Floor Granted message. Timer T207 (Stop talking) starts upon the expiration of Timer T206 (Stop talking warning). Timer T206 (Stop talking warning)=10s is set to TransmitTimeout=60s, as defined in TS 36.579-1 [2], Table 5.5.8.4-1, minus TransmissionWarning=50s, as defined in TS 36.579-1 [2], Table 5.5.8.4-1. Timer T207 (Stop talking)=50s is set to TransmissionWarning=50s, as defined in TS 36.579-1 [2], Table 5.5.8.4-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.6.3.3 Specific message contents

Table 7.1.6.3.3-1: GROUP CALL ANNOUNCEMENT (step 10, Table 7.1.6.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Call identifier

A value less than the Call identifier used in the GROUP CALL ANNOUNCEMENT sent in step 5

Call start time

The same Call start time used in the GROUP CALL ANNOUNCEMENT sent in step 5

Table 7.1.6.3.3-2: Floor Granted (step 8, Table 7.1.6.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 priority

"0"

Floor Indicator

Floor Indicator

‘10000X0000000000’

bit A=1 (Normal call)

bit F=X (Queueing supported) any value

Table 7.1.6.3.3-3: Floor Granted (step 10, Table 7.1.6.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 priority

"0"

User ID

User ID

Px_MCPTT_User_B_ID

Floor Indicator

Floor Indicator

‘1000010000000000’

bit A=1 (Normal call)

bit F=1 (Queueing supported) any value

Table 7.1.6.3.3-4: Floor Granted (step 14, Table 7.1.6.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 priority

"0"

Floor Indicator

Floor Indicator

‘1000010000000000’

bit A=1 (Normal call)

bit F=1 (Queueing supported) any value

Table 7.1.6.3.3-5: Floor Request (step 13, Table 7.1.6.3.2-1)

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

Information Element

Value/remark

Comment

Condition

Floor Indicator

Floor Indicator

‘10000X0000000000’

bit A=1 (Normal call)

bit F=X (Queueing supported) any value

Table 7.1.6.3.3-6: Floor Release (step 16, Table 7.1.6.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

‘10000X0000000000’

bit A=1 (Normal call)

bit F=X (Queueing supported) any value