7.1.8 Off-network / Group Call / Emergency Call / Imminent Peril 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.8.1 Test Purpose (TP)
(1)
with { UE (MCPTT Client) registered and authorised for MCPTT Service, including authorised to receive emergency group calls in off-network environment, and the UE (MCPTT Client) is in an off-network environment }
ensure that {
when { the UE (MCPTT Client) receives GROUP CALL ANNOUNCEMENT to initiate an MCPTT emergency group call }
then { UE (MCPTT Client) responds by sending a GROUP CALL ACCEPT 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 receive imminent peril group calls in off-network environment, and the UE (MCPTT Client) is in an off-network environment }
ensure that {
when { the UE (MCPTT Client) receives GROUP CALL ANNOUNCEMENT to initiate an MCPTT imminent peril group call }
then { UE (MCPTT Client) responds by sending a GROUP CALL ACCEPT message, and respects the floor control imposed by the floor control entity/arbitrator }
}
7.1.8.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.379 clauses 10.2.2.4.3.3, 10.2.3.4.5, 10.2.3.4.6. Unless otherwise stated these are Rel-13 requirements.
[TS 24.379, clause 10.2.2.4.3.3]
When in the "S1: start-stop" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE not matching MCPTT group ID of the call stored for other state machines, 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 MCPTT group ID IE of the GROUP CALL ANNOUNCEMENT message as the MCPTT group ID of the call;
6) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
7) shall create a call type control state machine as described in subclause 10.2.3.2;
8) if the terminating UE is configured that the terminating MCPTT user acknowledgement is required upon a terminating call request reception:
a) shall start timer TFG4 (waiting for the user);
b) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE, shall enter the "S5: pending user action with confirm indication" state; and
c) if the GROUP CALL ANNOUNCEMENT message does not contains the Confirm mode indication IE, shall enter the "S4: pending user action without confirm indication" state; and
9) if the terminating UE is configured that the terminating MCPTT user acknowledgement is not required upon a terminating call request reception:
a) shall establish a media session based on the stored SDP body of the call;
b) shall start floor control as terminating floor participant as specified in subclause 7.2 in 3GPP TS 24.380 [5];
c) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE:
i) shall generate a GROUP CALL ACCEPT message as specified in subclause 15.1.4. In the GROUP CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier of the call;
B) shall set the Sending MCPTT user ID IE to own MCPTT user id;
C) shall set the Call type IE to the stored current call type associated with the call type control state machine; and
D) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and
ii) shall send the GROUP CALL ACCEPT message as specified in subclause 10.2.1.1.1;
d) shall start timer TFG6 (max duration) with value as specified in subclause 10.2.2.4.1.2;
e) shall start timer TFG2 (call announcement) with value as specified in subclause 10.2.2.4.1.1.1; and
f) shall enter the "S3: part of ongoing call" state.
[TS 24.379, clause 10.2.3.4.5]
When in the "T0: waiting for the call to establish" state, upon receipt of a GROUP CALL ANNOUNCEMENT message by an idle MCPTT client when MCPTT user acknowledgement is not required, the MCPTT client:
1) shall set the stored last call type change time to the Last call type change time IE of the GROUP CALL ANNOUNCEMENT message;
2) shall set the last user to change call type to the Last user to change call type IE of the GROUP CALL ANNOUNCEMENT message;
3) if the Call type IE of the received GROUP CALL ANNOUNCEMENT message is set to "EMERGENCY GROUP CALL":
a) shall set the stored current call type to "EMERGENCY GROUP CALL";
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];
c) shall start timer TFG13 (implicit downgrade emergency) with value as specified in subclause 10.2.3.4.1.1; and
d) shall enter "T1: in-progress emergency group call" state;
4) if the Call type IE of the received GROUP CALL ANNOUNCEMENT message is set to "IMMINENT PERIL GROUP CALL":
a) shall set the stored current call type to "IMMINENT PERIL GROUP CALL";
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network imminent peril group call as described in3GPP TS 24.383 [45];
c) shall start timer TFG14 (implicit downgrade imminent peril) with value as specified in subclause 10.2.3.4.1.2; and
d) shall enter "T3: in-progress imminent peril group call" state; and
5) if the Call type IE of the received GROUP CALL ANNOUNCEMENT message is set to "BASIC GROUP CALL":
a) shall set the stored current call type to "BASIC GROUP CALL";
b) 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]; and
c) shall enter "T2: in-progress basic group call" 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.
7.1.8.3 Test description
7.1.8.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 is configured that the terminating MCPTT user acknowledgement is not required upon a terminating call request reception
– TFG1 (wait for call announcement) set to 150 ms (default value) ("/<x>/OffNetwork/Counters/TFG1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [13])
– TFG3 (call probe retransmission) set to 40 ms (default value) ("/<x>/OffNetwork/Counters/TFG3" 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.8.3.2 Test procedure sequence
Table 7.1.8.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 ANNOUNCEMENT for the initiation of an emergency group call |
<– |
GROUP CALL ANNOUNCEMENT |
– |
– |
4 |
Check: Does the UE (MCPTT Client) send a GROUP CALL ACEEPT message? (NOTE 2) |
–> |
GROUP CALL ACCEPT |
1 |
P |
5 |
Void |
– |
– |
1 |
P |
6 |
SS-UE1 (MCPTT client) sends a Floor Granted message |
<– |
Floor Granted |
– |
– |
7 |
Make the UE (MCPTT User) request the floor (NOTE 1) |
– |
– |
– |
– |
8 |
Check: Does the UE (MCPTT Client) send a Floor Request message to the floor participants? |
—> |
Floor Request |
1 |
P |
9 |
SS-UE1 (MCPTT client) sends a Floor Deny message |
<– |
Floor Deny |
– |
– |
10 |
SS-UE1 (MCPTT client) sends a Floor Release message |
<– |
Floor Release |
– |
– |
11 |
Make the UE (MCPTT Client) release the group call (NOTE 1) |
– |
– |
– |
– |
12 |
Void |
– |
– |
– |
– |
13 |
Void |
– |
– |
– |
– |
– |
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. |
– |
– |
– |
– |
14 |
SS-UE1 (MCPTT client) sends a GROUP CALL ANNOUNCEMENT for the initiation of an imminent peril group call |
<– |
GROUP CALL ANNOUNCEMENT |
– |
– |
15 |
Check: Does the UE (MCPTT Client) send a GROUP CALL ACEEPT message? (NOTE 2) |
–> |
GROUP CALL ACCEPT |
2 |
P |
16 |
Void |
– |
– |
2 |
P |
17 |
SS-UE1 (MCPTT client) sends a Floor Granted message |
<– |
Floor Granted |
– |
– |
18 |
Make the UE (MCPTT User) request the floor (NOTE 1) |
– |
– |
– |
– |
19 |
Check: Does the UE (MCPTT Client) send a Floor Request message to the floor participants? |
—> |
Floor Request |
2 |
P |
20 |
SS-UE1 (MCPTT client) sends a Floor Deny message |
<– |
Floor Deny |
– |
– |
21 |
SS-UE1 (MCPTT client) sends a Floor Release message |
<– |
Floor Release |
– |
– |
22 |
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: The UE (MCPTT Client) enters the "S3: part of ongoing call" state as a terminating floor participant |
7.1.8.3.3 Specific message contents
Table 7.1.8.3.3-1: GROUP CALL ANNOUNCEMENT (step 3, Table 7.1.8.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 |
|
Originating MCPTT user ID |
"sip:mcptt-client-B@mcptt-op.gov" |
pre-set MCPTT user ID |
Table 7.1.8.3.3-2: GROUP CALL ANNOUNCEMENT (step 14, Table 7.1.8.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 |
|
Originating MCPTT user ID |
"sip:mcptt-client-B@mcptt-op.gov" |
pre-set MCPTT user ID |
Table 7.1.8.3.3-3: GROUP CALL ACCEPT (step 4, Table 7.1.8.3.2-1)
Derivation Path: TS 36.579-1 [2], Table 5.5.5.3.1-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Call type |
"00000011" |
Emergency Group Call |
Table 7.1.8.3.3-4: GROUP CALL ACCEPT (step 15, Table 7.1.8.3.2-1)
Derivation Path: TS 36.579-1 [2], Table 5.5.5.3.1-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Call type |
"00000100" |
Imminent Peril Group Call |
Table 7.1.8.3.3-5: Floor Granted (step 6, Table 7.1.8.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 |
any allowed value |
||
User ID |
|||
User ID |
"sip:mcptt-client-B@mcptt-op.gov" |
||
Queue Size |
|||
Queue Size |
"0" |
the numbers of queued MCPTT clients in the MCPTT call |
|
SSRC of queued floor participant |
Not present |
||
Queued User ID |
Not present |
||
Queued User ID |
Not present |
||
Queue Info |
Not present |
||
Queue Position Info |
Not present |
||
Queue Priority Level |
Not present |
||
Floor Indicator |
|||
Floor Indicator |
‘0001000000000000’ |
bit D=1 (Emergency call) |
Table 7.1.8.3.3-6: Floor Granted (step 17, Table 7.1.8.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 |
any allowed value |
||
User ID |
|||
User ID |
"sip:mcptt-client-B@mcptt-op.gov" |
||
Queue Size |
|||
Queue Size |
"0" |
the numbers of queued MCPTT clients in the MCPTT call |
|
SSRC of queued floor participant |
Not present |
||
Queued User ID |
Not present |
||
Queued User ID |
Not present |
||
Queue Info |
Not present |
||
Queue Position Info |
Not present |
||
Queue Priority Level |
Not present |
||
Floor Indicator |
|||
Floor Indicator |
‘0000100000000000’ |
bit E=1 (Imminent peril call) |
Table 7.1.8.3.3-7: Floor Request (step 8, Table 7.1.8.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 |
User ID |
|||
User ID |
"sip:mcptt-client-A@mcptt-op.gov" |
||
Floor Indicator |
|||
Floor Indicator |
‘00010X0000000000’ |
bit D=1 (Emergency call) bit F=X (Queueing supported) any value |
Table 7.1.8.3.3-8: Floor Request (step 19, Table 7.1.8.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 |
User ID |
|||
User ID |
"sip:mcptt-client-A@mcptt-op.gov" |
||
Floor Indicator |
|||
Floor Indicator |
‘00001X0000000000’ |
bit E=1 (Imminent peril call) bit F=X (Queueing supported) any value |
Table 7.1.8.3.3-9: Floor Deny (step 9, Table 7.1.8.3.2-1)
Derivation Path: TS 36.579-1 [2], Table 5.5.6.4-1 condition OFF-NETWORK |
|||
Information Element |
Value/remark |
Comment |
Condition |
Reject Cause |
|||
Reject Phrase |
"Another MCPTT client has permission" |
||
User ID |
|||
User ID |
"sip:mcptt-client-A@mcptt-op.gov" |
||
Floor Indicator |
|||
Floor Indicator |
‘0001000000000000’ |
bit D=1 (Emergency call) |
Table 7.1.8.3.3-10: Floor Deny (step 20, Table 7.1.8.3.2-1)
Derivation Path: TS 36.579-1 [2], Table 5.5.6.4-1 condition OFF-NETWORK |
|||
Information Element |
Value/remark |
Comment |
Condition |
Reject Cause |
|||
Reject Phrase |
"Another MCPTT client has permission" |
||
User ID |
|||
User ID |
"sip:mcptt-client-A@mcptt-op.gov" |
||
Floor Indicator |
|||
Floor Indicator |
‘0000100000000000’ |
bit E=1 (Imminent peril call) |
Table 7.1.8.3.3-11: Floor Release (step 10, Table 7.1.8.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 |
User ID |
|||
User ID |
"sip:mcptt-client-B@mcptt-op.gov" |
||
Floor Indicator |
|||
Floor Indicator |
‘0001000000000000’ |
bit D=1 (Emergency call) |
Table 7.1.8.3.3-12: Floor Release (step 21, Table 7.1.8.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 |
User ID |
|||
User ID |
"sip:mcptt-client-B@mcptt-op.gov" |
||
Floor Indicator |
|||
Floor Indicator |
‘0000100000000000’ |
bit E=1 (Imminent peril call) |