7.1.3 Off-network / Group Call / Leave Group Call when GROUP CALL PROBE sent / Initiate Group Call for Released Call / Receive GROUP CALL ANNOUNCEMENT for Released call / No GROUP CALL ANNOUNCEMENT for Released Call / Receive Response to GROUP CALL PROBE
36.579-23GPPMission Critical (MC) services over LTEPart 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specificationRelease 15TS
7.1.3.1 Test Purpose (TP)
(1)
with { UE (MCPTT Client) registered and authorised for MCPTT Service, including authorised to initiate/cancel 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 pre-arranged group call and UE (MCPTT Client) requests a pre-arranged group call by sending a GROUP CALL PROBE message and the MCPTT User requests the release of the call before the expiration of the TFG3 (call probe retransmission)timer }
then { the UE (MCPTT Client) releases the call and enters the "S7: Waiting for call announcement after call release" state and does not send a GROUP CALL PROBE at the expiry of the TFG3 (call probe retransmission)timer }
}
(2)
with { UE (MCPTT Client) in the "S7: Waiting for call announcement after call release" state }
ensure that {
when { the MCPTT User requests the establishment of an MCPTT pre-arranged group call }
then { the UE (MCPTT Client) sends a GROUP CALL PROBE message and enters the "S2: waiting for call announcement" state }
}
(3)
with { UE (MCPTT Client) in the "S2: waiting for call announcement" state }
ensure that {
when { the UE (MCPTT Client receives a GROUP CALL ANNOUNCEMENT message }
then { the UE (MCPTT Client) enters the "S3: part of ongoing call" state as a terminating floor participant and respects the floor control imposed by the floor control entity/arbitrator }
}
7.1.3.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.2.4.5.5, 10.2.2.4.5.6, 10.2.2.4.5.7, 10.2.2.4.5.4, 10.2.2.4.5.8, 10.2.2.4.3.2, TS 24.380 clause 7.2.3.2.3. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core spec they have been copied from. 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.2.4.5.5]
When in the "S2: waiting for call announcement" state, upon an indication from the MCPTT user to release the group call, the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission); and
2) shall enter the "S7: Waiting for call announcement after call release" state.
[TS 24.379, clause 10.2.2.4.5.6]
When in the "S7: Waiting for call announcement after call release" state, upon an indication from the MCPTT user to initiate a group call for an MCPTT group ID matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall stop timer TFG1 (wait for call announcement);
2) 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; and
3) shall send the GROUP CALL PROBE message as specified in subclause 10.2.1.1.1;
4) shall start timer TFG3 (call probe retransmission);
5) shall start timer TFG1 (wait for call announcement); and
6) shall enter the "S2: waiting for call announcement" state.
[TS 24.379, clause 10.2.2.4.5.7]
When in the "S7: Waiting for call announcement after call release" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID 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 stop timer TFG1 (wait for call announcement);
7) shall start timer TFG5 (not present incoming call announcements); and
8) shall enter the "S6: ignoring incoming call announcements" state.
[TS 24.379, clause 10.2.2.4.5.4]
When in the "S6: ignoring incoming call announcements" state, upon expiration of timer TFG5 (not present incoming call announcements), the MCPTT client:
1) shall release the stored SDP body of the call;
2) shall release the stored call identifier of the call;
3) shall release the stored originating MCPTT user ID of the call;
4) shall release the stored refresh interval of the call;
5) shall release the stored MCPTT group ID of the call;
6) shall release the call start time of the call;
7) shall destroy the call type control state machine as specified in subclause 10.2.3.4.10 or 10.2.3.4.11; and
8) shall enter the "S1: start-stop" state.
[TS 24.379, clause 10.2.2.4.5.8]
When in the "S7: Waiting for call announcement after call release" state, upon expiration of timer TFG1 (wait for call announcement), the MCPTT client:
1) shall release the stored MCPTT group ID of the call;
2) shall destroy the call type control state machine as specified in subclause 10.2.3.4.11; and
3) shall enter the "S1: start-stop" state.
[TS 24.379, clause 10.2.2.4.3.2]
When in the "S2: waiting for call announcement" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission);
2) shall stop timer TFG1 (wait for call announcement);
3) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
4) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
5) 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;
6) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
7) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
8) shall establish a media session based on the stored SDP body of the call;
9) shall start floor control as terminating floor participant as specified in subclause 7.2 in 3GPP TS 24.380 [5];
10) shall start timer TFG6 (max duration) with value as specified in subclause 10.2.2.4.1.2;
11) shall start timer TFG2 (call announcement) with value as specified in subclause 10.2.2.4.1.1.1; and
12) shall enter 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.3.3 Test description
7.1.3.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.
– TFG1 (wait for call announcement) set to 25 seconds (25,000 ms) ("/<x>/OffNetwork/Timers/TFG1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [13]; related to the D2D Sidelink period)
– TFG3 (call probe retransmission) set to 15 seconds (15,000 ms) ("/<x>/OffNetwork/Counters/TFG3" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [13])
– TFG5 (not present incoming call announcement) set to 30 seconds ("/<x>/OffNetwork/Timers/TFG5" 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.3.3.2 Test procedure sequence
Table 7.1.3.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 |
The UE (MCPTT client) sends a GROUP CALL PROBE message to determine the current call status of the group (NOTE 2) |
–> |
GROUP CALL PROBE |
– |
– |
4A |
SS starts Timer=15s (TFG3 (call probe retransmission)) |
– |
– |
– |
– |
5 |
Make the UE (MCPTT Client) release the off-network basic group call (NOTE 1), (NOTE 3) |
– |
– |
– |
– |
5A |
Timer=15s expires |
– |
– |
– |
– |
6 |
Check: Does the UE (MCPTT Client) in the next 5 seconds send a retransmission of the GROUP CALL PROBE sent in step 4? |
–> |
GROUP CALL PROBE |
1 |
F |
6A |
Wait 5 seconds GROUP CALL PROBE message |
– |
– |
– |
– |
7 |
Make the UE (MCPTT Client) initiate an off-network basic group call (NOTE 1), (NOTE 4) |
– |
– |
– |
– |
8 |
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 |
2 |
P |
9 |
Make the UE (MCPTT Client) release the off-network basic group call (NOTE 1), (NOTE 3) |
– |
– |
– |
– |
10 |
The SS-UE1 (MCPTT client) sends a GROUP CALL ANNOUNCEMENT message to the UE (MCPTT Client) with the MCPTT group ID IE matching the stored MCPTT group ID of the released call |
<– |
GROUP CALL ANNOUNCEMENT |
– |
– |
11 |
Void |
– |
– |
– |
– |
12 |
Void |
– |
– |
– |
– |
13 |
Void |
– |
– |
– |
– |
14 |
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. |
– |
– |
– |
– |
15 |
The UE (MCPTT client) sends a GROUP CALL PROBE message to determine the current call status of the group (NOTE 2) |
–> |
GROUP CALL PROBE |
– |
– |
15A |
SS starts Timer=25s (TFG1 (wait for call announcement)) |
– |
– |
– |
– |
16 |
Make the UE (MCPTT Client) release the off-network basic group call (NOTE 1), (NOTE 3) |
– |
– |
– |
– |
16A |
Timer=25s expires |
– |
– |
– |
– |
17 |
Void |
– |
– |
4 |
P |
18 |
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. |
– |
– |
– |
– |
19 |
The UE (MCPTT client) sends a GROUP CALL PROBE message to determine the current call status of the group (NOTE 2) |
–> |
GROUP CALL PROBE |
– |
– |
20 |
The SS-UE1 (MCPTT client) sends a GROUP CALL ANNOUNCEMENT message to the UE (MCPTT Client) with the MCPTT group ID IE matching the stored MCPTT group ID of the released call (NOTE 5) |
<– |
GROUP CALL ANNOUNCEMENT |
– |
– |
20A |
Make the UE (MCPTT Client) request the floor (NOTE 1) |
– |
– |
– |
– |
21 |
Check: Does the UE (MCPTT Client) send a Floor Request message to the floor participants? |
– |
– |
5 |
P |
21A |
The SS-UE1 (MCPTT client) responds with a Floor Deny message |
<– |
Floor Deny |
– |
– |
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: Timer TFG3 (call probe retransmission)=15s as defined in the Pre-test conditions and TFG1 (wait for call announcement)=25s as defined in the Pre-test conditions are started upon the sending of the GROUP CALL PROBE message. NOTE 3: If the MCPTT User does not release the call before timer TFG3 (call probe retransmission) expires, then the MCPTT Client will resend the GROUP CALL PROBE message per TS 24.379 [9] and the remaining steps will not be valid. 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: If the MCPTT User does not perform an action before timer TFG1 (wait for call announcement) expires, then the MCPTT Client will enter the "S1: start-stop" state per TS 24.379 [9] and the remaining steps will not be valid. 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: Timer TFG6 (max duration) and timer TFG2 (call announcement) are started upon the receiving of the GROUP CALL ANNOUNCEMENT message while in the "S2: waiting for call announcement" state. The value of TFG6 (max duration) is a variable equation as defined in TS 36.379 [2], clause 10.2.2.4.1.2. The value of TFG2 (call announcement) is a variable equation as defined in TS 36.379 [2], clause 10.2.2.4.1.1. |
7.1.3.3.3 Specific message contents
Table 7.1.3.3.3-1: GROUP CALL ANNOUNCEMENT (step 20, Table 7.1.1.3.2-1)
Derivation Path: TS 36.579-1 [2], Table 5.5.5.2.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Probe response |
present |
GROUP CALL ANNOUNCEMENT is in response to a GROUP CALL PROBE |