7.3 Emergency Alert
36.579-63GPPMission Critical (MC) services over LTEPart 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specificationRelease 15TS
7.3.1 Off-network / Emergency Alert / Client Originated (CO)
7.3.1.1 Test Purpose (TP)
(1)
with { UE (MCVideo Client) registered and authorized for MCVideo Service, including authorized to initiate/cancel private calls with automatic commencement in off-network environment, and, the UE is in an off-network environment }
ensure that {
when { the MCVideo User requests to transmit an emergency alert for an MCVideo group ID }
then { UE (MCVideo Client) sends a GROUP EMERGENCY ALERT message, and, starts timer TFE2 (emergency alert retransmission) }
}
(2)
with { UE (MCVideo Client) having sent a GROUP EMERGENCY ALERT message }
ensure that {
when { TFE2 (emergency alert retransmission) timer expires }
then { UE (MCVideo Client) sends a GROUP EMERGENCY ALERT message, and, starts timer TFE2 (emergency alert retransmission) }
}
(3)
with { UE (MCVideo Client) having sent a GROUP EMERGENCY ALERT message }
ensure that {
when { MCVideo User cancels the Emergency Alert }
then { UE (MCVideo Client) sends a GROUP EMERGENCY ALERT CANCEL message, and, stops timer TFE2 (emergency alert retransmission) }
}
7.3.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.281 clauses 11.3.3.1, 11.3.3.2, 11.3.3.5. Unless otherwise stated these are Rel-15 requirements.
[TS 24.281, clause 11.3.3.1]
When in state "E1: Not in emergency state", upon receiving an indication from the MCVideo user to transmit an emergency alert for an MCVideo group ID and the value of "/<x>/<x>/Common/AllowedActivateAlert" leaf node present in the user profile as specified in 3GPP TS 24.483 [4] is set to "true", the MCVideo client:
1) shall set the stored emergency state as "true";
2) shall set the stored MCVideo group ID to the indicated MCVideo group ID;
3) shall generate a GROUP EMERGENCY ALERT message as specified in clause 17.1.14. In the GROUP EMERGENCY ALERT message, the MCVideo client:
a) shall set the MCVideo group ID IE to the stored MCVideo group ID;
b) shall set the Originating MCVideo user ID IE to own MCVideo 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 clause 9.3.1.1.1;
5) shall start timer TFE2 (emergency alert retransmission); and
6) shall enter "E2: Emergency state" state.
[TS 24.281, clause 11.3.3.2]
When in state "E2: Emergency state", upon expiry of timer TFE2 (emergency alert retransmission), the MCVideo client:
1) shall generate a GROUP EMERGENCY ALERT message as specified in clause 17.1.14. In the GROUP EMERGENCY ALERT message, the MCVideo client:
a) shall set the MCVideo group ID IE to the stored MCVideo group ID;
b) shall set the originating MCVideo user ID IE to own MCVideo 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 clause 9.3.1.1.1;
3) shall start the timer TFE2 (emergency alert retransmission); and
4) shall remain in the current state.
[TS 24.281, clause 11.3.3.5]
When in "E2: Emergency state", upon receiving an indication from the MCVideo user to cancel an emergency alert and the value of "/<x>/<x>/Common/AllowedCancelAlert" leaf node present in the user profile as specified in 3GPP TS 24.483 [4] is set to "true", the MCVideo client:
1) shall set the stored emergency state as "false";
2) shall generate a GROUP EMERGENCY ALERT CANCEL message as specified in clause 17.1.16. In the GROUP EMERGENCY ALERT CANCEL message, the MCVideo client:
a) shall set the MCVideo group ID IE to the stored MCVideo group ID; and
b) shall set the Originating MCVideo user ID IE to own MCVideo user ID; and
3) shall send the GROUP EMERGENCY ALERT CANCEL message as specified in clause 9.3.1.1.1;
4) shall stop timer TFE2 (emergency alert retransmission); and
5) shall enter "E1: Not in emergency state" state.
7.3.1.3 Test description
7.3.1.3.1 Pre-test conditions
System Simulator:
– SS-UE1 (MCVideo 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 (MCVideo 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 MCVideo operation in the MCVideo configuration document).
NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.
IUT:
– UE (MCVideo 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 MCVideo UE registration as specified in TS 36.579-1 [2], subclause 5.4.2A.
– The MCVideo User performs the Generic Test Procedure for MCVideo 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.3.1.3.2 Test procedure sequence
Table 7.3.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Power up the UE. |
– |
– |
– |
– |
|
2 |
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). |
– |
– |
– |
– |
|
3 |
Activate the MCVideo Client Application and register User A as the MCVideo User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password). (NOTE 1) |
– |
– |
– |
– |
|
4 |
Make the MCVideo User request to transmit an emergency alert for Group A. (NOTE 1) |
– |
– |
– |
– |
|
– |
EXCEPTION: The E-UTRA/EPC actions which are related to the MCVideo 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 MCVideo relevant messages exchanged. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 5a1-5b1 describe behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that takes place when the UE (MCVideo Client) includes user location information in the GROUP EMRGENCY ALERT message or not. |
– |
– |
– |
– |
|
5a1 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT message without user location? NOTE: It is expected that the UE shall start timer TFE2 (emergency alert retransmission). |
–> |
GROUP EMERGENCY ALERT |
1 |
P |
|
5b1 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT message with user location? NOTE: It is expected that the UE shall start timer TFE2 (emergency alert retransmission). |
–> |
GROUP EMERGENCY ALERT |
1 |
P |
|
6 |
Start TFE2 (emergency alert retransmission) 10 seconds as defined in 36.579-1 [2] Table 5.5.8.1-1. |
– |
– |
– |
– |
|
7 |
SS-UE1 (MCVideo Client) sends a GROUP EMERGENCY ALERT ACK message. |
<– |
GROUP EMERGENCY ALERT ACK |
– |
– |
|
8 |
TFE2 expires. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 9a1-9b1 describe behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that takes place when the UE (MCVideo Client) includes user location information in the GROUP EMRGENCY ALERT message or not. |
||||
|
9a1 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT message without user location? NOTE: It is expected that the UE shall start timer TFE2 (emergency alert retransmission). |
–> |
GROUP EMERGENCY ALERT |
2 |
P |
|
9b1 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT message with user location? NOTE: It is expected that the UE shall start timer TFE2 (emergency alert retransmission). |
–> |
GROUP EMERGENCY ALERT |
2 |
P |
|
10 |
Before timer TFE2 expires, make the MCVideo User request to cancel the emergency alert for Group A. (NOTE 1) |
– |
– |
– |
– |
|
11 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT CANCEL message? NOTE: It is expected that the UE shall stop timer TFE2 (emergency alert retransmission). |
–> |
GROUP EMERGENCY ALERT CANCEL |
3 |
P |
|
12 |
SS-UE1 (MCVideo Client) sends a GROUP EMERGENCY ALERT CANCEL ACK message. |
<– |
GROUP EMERGENCY ALERT CANCEL ACK |
– |
– |
|
– |
EXCEPTION: UE releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 5.4.8, ‘Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the UE’. |
– |
– |
– |
– |
|
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. |
|||||
7.3.1.3.3 Specific message contents
Table 7.3.1.3.3-1: GROUP EMERGENCY ALERT (steps 5b1, 9b1, Table 7.3.1.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.14.15.1-1, condition USER_LOC |
7.3.2 Off-network / Emergency Alert / Client Terminated (CO)
7.3.2.1 Test Purpose (TP)
(1)
with { UE (MCVideo Client) registered and authorized for MCVideo Service, including authorized to initiate/cancel private calls with automatic commencement in off-network environment, and, the UE is in an off-network environment }
ensure that {
when { UE (MCVideo Client) receives a GROUP EMERGENCY ALERT message }
then { UE (MCVideo Client) sends a GROUP EMERGENCY ALERT ACK message, and, starts timer TFE1 (Emergency Alert) }
}
(2)
with { UE (MCVideo Client) having received a GROUP EMERGENCY ALERT message }
ensure that {
when { UE (MCVideo Client) receives a retransmission of the original GROUP EMERGENCY ALERT message }
then { UE (MCVideo Client) does not send a GROUP EMERGENCY ALERT ACK message }
}
(3)
with { UE (MCVideo Client) having received a GROUP EMERGENCY ALERT message }
ensure that {
when { UE (MCVideo Client) receives a GROUP EMERGENCY ALERT CANCEL message }
then { UE (MCVideo Client) sends a GROUP EMERGENCY ALERT CANCEL ACK message, and, stops timer TFE1 (Emergency Alert) }
}
7.3.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.281 clauses 11.3.3.3, 11.3.3.4, 11.3.3.6. Unless otherwise stated these are Rel-15 requirements.
[TS 24.281, clause 11.3.3.3]
When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCVideo user ID IE not stored in the list of users in emergency, the MCVideo client:
1) shall store the Originating MCVideo user ID IE and location IE in the list of users in emergency;
2) shall generate a GROUP EMERGENCY ALERT ACK message as specified in clause 17.1.15. In the GROUP EMERGENCY ALERT ACK message, the MCVideo client:
a) shall set the MCVideo group ID IE to the MCVideo group ID IE of the received GROUP EMERGENCY ALERT message;
b) shall set the Sending MCVideo user ID IE to own MCVideo user ID; and
c) shall set the Originating MCVideo user ID IE to the Originating MCVideo user ID IE of the received GROUP EMERGENCY ALERT message; and
3) shall send the GROUP EMERGENCY ALERT ACK message as specified in clause 9.3.1.1.1;
4) shall start timer TFE1 (Emergency Alert); and
5) shall remain in the current state.
NOTE: Each instance of timer TFE1 is per MCVideo user ID.
[TS 24.281, clause 11.3.3.4]
When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCVideo user ID IE stored in the list of users in emergency and Location IE different than the stored location of the user, the MCVideo client:
1) may update the stored location of the user with the received Location IE;
2) shall restart the associated timer TFE1 (Emergency Alert); and
3) shall remain in the current state.
[TS 24.281, clause 11.3.3.6]
When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT CANCEL message with the Originating MCVideo user ID IE stored in the list of users in emergency, the MCVideo client:
1) shall remove the MCVideo user ID and associated location information from the stored list of users in emergency;
2) shall generate a GROUP EMERGENCY ALERT CANCEL ACK message as specified in clause 17.1.17. In the GROUP EMERGENCY ALERT CANCEL ACK message, the MCVideo client:
a) shall set the MCVideo group ID IE to the MCVideo group ID IE of the received GROUP EMERGENCY ALERT CANCEL message; and
b) shall set the Sending MCVideo user ID IE to own MCVideo user ID; and
c) shall set the Originating MCVideo user ID IE to the Originating MCVideo user ID IE of the received GROUP EMERGENCY ALERT message;
3) shall send the GROUP EMERGENCY ALERT CANCEL ACK message as specified in clause 9.3.1.1.1;
4) shall stop the associated timer TFE1 (Emergency Alert); and
5) shall remain in the current state.
7.3.2.3 Test description
7.3.2.3.1 Pre-test conditions
System Simulator:
– SS-UE1 (MCVideo 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 (MCVideo 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 MCVideo operation in the MCVideo configuration document).
NOTE 2: The SS operation as NW (MCVideo server) is needed only for the Preamble if the UE has to perform the Generic Test Procedure for MCVideo Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.
IUT:
– UE (MCVideo 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 MCVideo UE registration as specified in TS 36.579-1 [2], subclause 5.4.2A.
– The MCVideo User performs the Generic Test Procedure for MCVideo 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.3.2.3.2 Test procedure sequence
Table 7.3.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Power up the UE. |
– |
– |
– |
– |
|
2 |
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). |
– |
– |
– |
– |
|
3 |
Activate the MCVideo Client Application and register User A as the MCVideo User (TS 36.579-5 [5], px_MCX_User_A_username, px_MCX_User_A_password). (NOTE 1) |
– |
– |
– |
– |
|
– |
EXCEPTION: The E-UTRA/EPC actions which are related to the MCVideo 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’. The test sequence below shows only the MCVideo relevant messages exchanged. |
– |
– |
– |
– |
|
4 |
SS-UE1 (MCVideo Client) sends a PRIVATE CALL SETUP REQUEST message. |
<– |
GROUP EMERGENCY ALERT |
– |
– |
|
5 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT ACK message? NOTE: It is expected that the UE shall start timer TFE1 (Emergency Alert). |
–> |
GROUP EMERGENCY ALERT ACK |
1 |
P |
|
6 |
Start TFE1 (Emergency Alert) 30 seconds as defined in 36.579-1 [2] Table 5.5.8.1-1. |
||||
|
7 |
Wait for 10 seconds (value of TFE2 (emergency alert retransmission) as defined in 36.579-1 [2] Table 5.5.8.1-1). |
– |
– |
– |
– |
|
8 |
SS-UE1 (MCVideo Client) sends a PRIVATE CALL SETUP REQUEST message. |
<– |
GROUP EMERGENCY ALERT |
– |
– |
|
9 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT ACK message? |
–> |
GROUP EMERGENCY ALERT ACK |
2 |
F |
|
10 |
SS-UE1 (MCVideo Client) sends a PRIVATE CALL SETUP REQUEST message. |
<– |
GROUP EMERGENCY ALERT CANCEL |
– |
– |
|
11 |
Check: Does the UE (MCVideo Client) send a GROUP EMERGENCY ALERT CANCEL message? NOTE: It is expected that the UE shall stop timer TFE1 (Emergency Alert). |
–> |
GROUP EMERGENCY ALERT CANCEL ACK |
3 |
P |
|
– |
EXCEPTION: SS releases the E-UTRA connection. The E-UTRA/EPC actions which are related to the MCVideo call release are described in TS 36.579-1 [2], subclause 5.4.7, ‘Generic Test Procedure for MCPTT communication over ProSe direct one-to-one communication out of E-UTRA coverage – release by the SS’. |
– |
– |
– |
– |
|
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. |
|||||
7.3.2.3.3 Specific message contents
Table 7.3.2.3.3-1: GROUP EMERGENCY ALERT (steps 4, 8, Table 7.3.2.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.14.15.1-1 |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
Originating MCVideo user ID |
px_MCVideo_ID_User_B |
||||
Table 7.3.2.3.3-2: GROUP EMERGENCY ALERT ACK (steps 5, 9, Table 7.3.2.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.14.16.1-1 |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
Originating MCVideo user ID |
px_MCVideo_ID_User_B |
||||
Table 7.3.2.3.3-3: GROUP EMERGENCY ALERT CANCEL (step 10, Table 7.3.2.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.14.17.1-1 |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
Originating MCVideo user ID |
px_MCVideo_ID_User_B |
||||
|
Sending MCVideo user ID |
px_MCVideo_ID_User_B |
||||
Table 7.3.2.3.3-4: GROUP EMERGENCY ALERT CANCEL ACK (step 11, Table 7.3.2.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.14.18.1-1 |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
Originating MCVideo user ID |
px_MCVideo_ID_User_B |
||||
|
Sending MCVideo user ID |
px_MCVideo_ID_User_A |
||||
Annex A (informative):
Change history
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-08 |
RAN5#80 |
R5-184607 |
– |
– |
– |
Introduction of TS 36.579-6 |
0.0.2 |
|
2018-08 |
RAN5#80 |
R5-184990 |
– |
– |
– |
New Test Case for 36.579-6 – 6.1.1.8 |
0.0.3 |
|
2018-08 |
RAN5#80 |
R5-185142 |
– |
– |
– |
Draft TS 36.579-6 v003 |
0.0.3 |
|
2019-06 |
RAN5#83 |
R5-195214 |
– |
– |
– |
New TC for 36.579-6 – 6.1.1.3 Group Call Manual CO |
0.0.4 |
|
2019-06 |
RAN5#83 |
R5-195215 |
– |
– |
– |
New TC for 36.579-6 – 6.1.1.4 Group Call Manual CT |
0.0.4 |
|
2019-06 |
RAN5#83 |
R5-194733 |
– |
– |
– |
Draft TS 36.579-6 v004 |
0.0.4 |
|
2019-09 |
RAN5#84 |
R5-196351 |
– |
– |
– |
Draft TS 36.579-6 v010 |
0.1.0 |
|
2019-11 |
RAN5#85 |
R5-198828 |
– |
– |
– |
Draft TS 36.579-6 v0.2.1 |
0.2.1 |
|
2020-05 |
RAN5#87 |
R5-202050 |
– |
– |
– |
Draft TS 36.579-6 v0.3.0 |
0.3.0 |
|
2020-07 |
RAN#88 |
RP-200716 |
– |
– |
– |
Draft version for information purposes to the RAN Plenary |
1.0.0 |
|
2020-08 |
RAN5#88 |
R5-203528 |
– |
– |
– |
draft TS 36.579-6 v1.1.0 |
1.1.0 |
|
2020-09 |
RAN#89 |
RP-201796 |
– |
– |
– |
Draft version for approval to move the spec under revision control to the RAN Plenary |
2.0.0 |
|
2020-09 |
RAN#89 |
– |
– |
– |
– |
upgraded to v14.0.0 with small editorial changes |
14.0.0 |
|
2021-03 |
RAN#91 |
R5-211269 |
0002 |
– |
F |
Correction to MCVideo Test Case 6.2.6 |
14.1.0 |
|
2021-03 |
RAN#91 |
R5-211546 |
0001 |
1 |
F |
Correction to MCVideo Test Case 6.1.1.9 |
14.1.0 |
|
2021-06 |
RAN#92 |
R5-212357 |
0005 |
– |
F |
Correction to MCVideo Test Case 6.1.1.1 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212358 |
0006 |
– |
F |
Correction to MCVideo Test Case 6.1.1.2 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212359 |
0007 |
– |
F |
Correction to MCVideo Test Case 6.1.1.3 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212360 |
0008 |
– |
F |
Correction to MCVideo Test Case 6.1.1.4 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212361 |
0009 |
– |
F |
Correction to MCVideo Test Case 6.1.1.5 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212362 |
0010 |
– |
F |
Correction to MCVideo Test Case 6.1.1.6 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212363 |
0011 |
– |
F |
Correction to MCVideo Test Case 6.1.1.7 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212364 |
0012 |
– |
F |
Correction to MCVideo Test Case 6.1.1.8 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212365 |
0013 |
– |
F |
Correction to MCVideo Test Case 6.1.1.9 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212366 |
0014 |
– |
F |
Correction to MCVideo Test Case 6.1.1.10 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-212367 |
0015 |
– |
F |
Correction to MCVideo Test Case 6.1.1.11 |
14.2.0 |
|
2021-06 |
RAN#92 |
R5-213256 |
0016 |
– |
F |
Addition of new MCVideo test case 6.1.1.12 On-network / On-demand Pre-arranged Group Call / Transmission Control State Transitions / Client Originated (CO) |
15.0.0 |
|
2021-06 |
RAN#92 |
R5-213257 |
0017 |
– |
F |
Addition of new MCVideo test case 6.1.1.13 On-network / On-demand Pre-arranged Group Call / Reception Control State Transitions / Client Terminated (CT) |
15.0.0 |
|
2021-09 |
RAN#93 |
R5-215593 |
0024 |
– |
F |
Correction to MCVideo Test Case 6.2.3 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-215594 |
0025 |
– |
F |
Correction to MCVideo Test Case 6.2.4 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-215595 |
0026 |
– |
F |
Correction to MCVideo Test Case 6.2.5 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-215596 |
0027 |
– |
F |
Correction to MCVideo Test Case 6.2.6 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-215599 |
0030 |
– |
F |
Addition of MCVideo Test Case 6.1.2.5 On-network / On-demand Pre-arranged Group Call / Emergency Group Call / Client Originated (CO) |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216344 |
0018 |
1 |
F |
Correction to MCVideo Test Case 6.1.2.1 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216345 |
0019 |
1 |
F |
Correction to MCVideo Test Case 6.1.2.2 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216346 |
0020 |
1 |
F |
Correction to MCVideo Test Case 6.1.2.3 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216347 |
0021 |
1 |
F |
Correction to MCVideo Test Case 6.1.2.4 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216348 |
0022 |
1 |
F |
Correction to MCVideo Test Case 6.2.1 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216349 |
0023 |
1 |
F |
Correction to MCVideo Test Case 6.2.2 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216350 |
0028 |
1 |
F |
Correction to MCVideo Test Case 6.2.7 |
15.1.0 |
|
2021-09 |
RAN#93 |
R5-216351 |
0029 |
1 |
F |
Correction to MCVideo Test Case 6.2.8 |
15.1.0 |
|
2022-03 |
RAN#95 |
R5-220489 |
0036 |
– |
F |
Correction of MCVideo Test Case 5.1 |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-220490 |
0037 |
– |
F |
Correction of MCVideo Test Case 5.2 |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-220491 |
0038 |
– |
F |
Correction of MCVideo Test Case 5.3 |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-220492 |
0039 |
– |
F |
Correction of MCVideo Test Case 5.4 |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-220493 |
0040 |
– |
F |
MCVideo condition clarification |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221546 |
0032 |
1 |
F |
New MCVideo TC 6.4.1 Video Pull |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221547 |
0033 |
1 |
F |
New MCVideo TC 6.5.1 Video Push |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221548 |
0034 |
1 |
F |
New MCVideo TC 6.3.1 Emergency Alert CO |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221549 |
0035 |
1 |
F |
New MCVideo TC 6.7.1 Remote Initiated Ambient Viewing CO |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221550 |
0041 |
1 |
F |
New MCVideo TC 6.7.2 Remote Initiated Ambient Viewing CT |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221551 |
0042 |
1 |
F |
New MCVideo TC Selected Group Change of Targeted User CO |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221552 |
0043 |
1 |
F |
New MCVideo TC Selected Group Change of Targeted User CT |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221553 |
0044 |
1 |
F |
New MCVideo TC Conference Event Package |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221554 |
0045 |
1 |
F |
New MCVideo TC 6.3.2 Emergency Alert CT |
15.2.0 |
|
2022-03 |
RAN#95 |
R5-221555 |
0046 |
1 |
F |
New MCVideo TC MBMS |
15.2.0 |
|
2022-06 |
RAN#96 |
R5-222149 |
0047 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.1.1 Off-network Basic Group Call CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222150 |
0048 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.1.2 Off-network Basic Group Call CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222151 |
0049 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.1.3 Off-network Emergency Call CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222152 |
0050 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.1.4 Off-network Emergency Call CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222153 |
0051 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.1.5 Off-network Imminent Peril Call CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222154 |
0052 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.1.6 Off-network Imminent Peril Call CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222155 |
0053 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.2.1 Off-network Broadcast Call CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222156 |
0054 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.1.2.2 Off-network Broadcast Call CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222157 |
0055 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.2.1 Off-network Auto Private Call CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222158 |
0056 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.2.2 Off-network Auto Private Call CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222159 |
0057 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.2.3 Off-network Manual Private Call CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222160 |
0058 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.2.4 Off-network Manual Private Call CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222161 |
0059 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.3.1 Off-network Emergency Alert CO |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222162 |
0060 |
– |
F |
New MCVIDEO OFF-NETWORK TC 7.3.2 Off-network Emergency Alert CT |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222370 |
0061 |
– |
F |
Correction of Emergency Alert Test Cases in clause 6.3 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222371 |
0062 |
– |
F |
Correction of MCVideo Test Cases clause 6.7 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222372 |
0063 |
– |
F |
Correction of test case 6.1.4.1 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222373 |
0064 |
– |
F |
Correction of test case 6.1.4.2 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222374 |
0065 |
– |
F |
Correction of Video Pull Test Cases in clause 6.4 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222375 |
0066 |
– |
F |
Correction of Video Push Test Cases in clause 6.5 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-222404 |
0067 |
– |
F |
Correction of Group Call Test Cases in clause 6.1 |
15.3.0 |
|
2022-06 |
RAN#96 |
R5-223479 |
0068 |
1 |
F |
Correction of Private Call Test Cases in clause 6.2 |
15.3.0 |
|
2022-09 |
RAN#97 |
R5-223961 |
0069 |
– |
F |
Correction of test cases in clause 6.1.1 – Pre-Arranged Group Call |
15.4.0 |
|
2022-09 |
RAN#97 |
R5-223962 |
0070 |
– |
F |
Correction of test cases in clause 6.1.4 – Remote change of selected group |
15.4.0 |