14 ETWS
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
14.1 ETWS reception in RRC_IDLE state / Duplicate detection
14.1.1 Test Purpose (TP)
(1)
with { UE in RRC_IDLE state and follow the reception of Paging message with etws-Indication }
ensure that {
when { UE start to acquire ETWS message from SIB10 and SIB11 }
then { UE successfully received the ETWS message and activated the “User Alerting” popup display }
}
14.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.2.2.4, 5.2.2.17, 5.2.2.18, 5.3.2.3; TS 23.041 clause 9.1.2.
[TS 36.331, clause 5.2.2.4]
The UE shall:
…
1> if the UE is ETWS capable:
2> upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:
3> discard any previously buffered warningMessageSegment;
3> clear, if any, the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2> when the UE acquires SystemInformationBlockType1 following ETWS indication, upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:
3> if schedulingInfoList indicates that SystemInformationBlockType10 is present:
4> start acquiring SystemInformationBlockType10 immediately;
3> if schedulingInfoList indicates that SystemInformationBlockType11 is present:
4> start acquiring SystemInformationBlockType11 immediately;
NOTE 2: UEs shall start acquiring SystemInformationBlockType10 and SystemInformationBlockType11 as described above even when systemInfoValueTag in SystemInformationBlockType1 has not changed.
[TS 36.331, clause 5.2.2.17]
Upon receiving SystemInformationBlockType10, the UE shall:
1> forward the received warningType, warningSecurityInfo (if present), messageIdentifier and serialNumber to upper layers;
[TS 36.331, clause 5.2.2.18]
Upon receiving SystemInformationBlockType11, the UE shall:
1> if there is no current value for messageIdentifier and serialNumber for SystemInformationBlockType11; or
1> if either the received value of messageIdentifier or of serialNumber or of both are different from the current values of messageIdentifier and serialNumber for SystemInformationBlockType11:
2> use the received values of messageIdentifier and serialNumber for SystemInformationBlockType11 as the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2> discard any previously buffered warningMessageSegment;
2> if all segments of a warning message have been received:
3> assemble the warningMessage from the received warningMessageSegment;
3> forward the received warningMessage, messageIdentifier, serialNumber and dataCodingScheme to upper layers;
3> stop reception of SystemInformationBlockType11;
3> discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2> else:
3> store the received warningMessageSegment;
3> continue reception of SystemInformationBlockType11;
1> else if all segments of a warning message have been received:
2> assemble the warningMessage from the received warningMessageSegment;
2> forward the received complete warningMessage, messageIdentifier, serialNumber and dataCodingScheme to upper layers;
2> stop reception of SystemInformationBlockType11;
2> discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
1> else:
2> store the received warningMessageSegment;
2> continue reception of SystemInformationBlockType11;
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall:
…
1> if the etws-Indication is included and the UE is ETWS capable:
2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information modification period boundary;
2> if the schedulingInfoList indicates that SystemInformationBlockType10 is present:
3> acquire SystemInformationBlockType10;
2> if the schedulingInfoList indicates that SystemInformationBlockType11 is present:
3> acquire SystemInformationBlockType11;
[TS 23.041, clause 9.1.2]
…
Figure 4b
…
6. The UE alert the user immediately, using "warning type" value,
– upon the reception of the paging message, if the UE has been configured to receive ETWS warnings over the paging message, and the UE has authenticated the core network of the NodeB it is camped on, or
– if the UE has not been configured to receive ETWS warnings over the paging message, and it received the optional primary notification and security checks based on "timestamp" and "digital signature" for this notification passed.
NOTE: If the UE received the ETWS warnings over the paging and also received the optional primary notification, it will silently discard the optional primary notification.
NOTE: When the "warning type" is ‘test’, the UE silently discards the paging message, and the optional primary notification, and do not perform the reception of the broadcast message described below. However, the UE specially designed for testing purposes may perform user alerting described above and proceed to the reception of the broadcast message described below
NOTE: If the UE has been configured to receive ETWS warnings over paging message but it has not authenticated the core network of the NodeB it is camped on, the UE does not receive the paging message and the optional primary notification, and do not perform the reception of the broadcast message described below.
Upon the reception of the paging message, whether the UE is configured to receive ETWS warnings over paging message or not, the UE activates the reception of the broadcast messages containing the "warning message" as the secondary notification, as follows:
– If both the "digital signature" and "timestamp" are present in the "warning message" and security checks fail, then the UE notifies the user of this fact and stops the user alerting.
– If both the "digital signature" and "timestamp" are present and security checks pass, then the UE indicates the contents of the "warning message" to the user along with an indication that the message has been authenticated.
– In other cases, the UE indicates the contents of the "warning message" to the user along with an indication that the message has not been authenticated.
Unless both the "digital signature" and "timestamp" are present and the security checks pass, the UE shall ignore the message, return to normal idle mode, and ignore paging messages with the "ETWS indication" for the next [X] seconds.
NOTE: Repetition period [X] is subject to regulatory requirements.
The UE shall consider a message duplicated if the combination of "message identifier" and "serial number" matches that of the previous message received from the same PLMN. The UE shall ignore messages detected as duplicated. If both the "digital signature" and "timestamp" are present, the UE shall perform security check before duplicate message detection. Duplicate message detection shall be performed independently for primary and secondary notifications.
7. The RNC node sends a BMC REPORT-SUCCESS to the CBC in response to Write-Replace.
8. CBC sends acknowledgement message to CBE.
14.1.3 Test description
14.1.3.1 Pre-test conditions
System Simulator:
- Cell 1
UE:
None.
Preamble:
– The UE is in state Registered, Idle mode (state 2) according to [18].
14.1.3.2 Test procedure sequence
Table 14.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
– |
– |
||
|
1 |
The SS include an ETWS message with new messageIdentifier and serialNumber in SystemInformationBlockType10 and SystemInformationBlockType11 and transmit a Paging message including etws-Indication on Cell 1 (NOTE 1). |
<– |
Paging |
– |
– |
|
2 |
Check: Does the UE indicate the contents of the "warning message" to the user, and alert or activate alerting the user (NOTE 2)? |
– |
– |
1 |
P |
|
3 |
The SS wait for 10s. |
– |
– |
– |
– |
|
4 |
The SS include an ETWS message with same messageIdentifier and serialNumber in SystemInformationBlockType10 and SystemInformationBlockType11 and transmit a Paging message including etws-Indication on Cell 1 (NOTE 1). |
<– |
Paging |
– |
– |
|
5 |
Check: Does the UE indicate the contents of the "warning message" to the user, or alert or activate alerting the user. (NOTE 2)? |
– |
– |
1 |
F |
|
NOTE 1: SystemInformationBlockType11 contain 3 segments. NOTE 2: The data indication and user alerting are the UE implementation issues. |
|||||
14.1.3.3 Specific message contents
Table 14.1.3.3-1: SystemInformationBlockType1 for Cell 1 (all steps, Table 14.1.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.2-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType1 ::= SEQUENCE { |
|||
|
schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {} |
Combination 8 in TS 36.508 section 4.4.3.1 |
SIB2, SIB3, SIB10 and SIB11 are transmitted |
|
|
} |
|||
Table 14.1.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell 1 (all steps when UE under test is CAT M1, Table 14.1.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.2-3A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType1-BR-r13 ::= SEQUENCE { |
|||
|
schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {} |
Combination 8 in TS 36.508 section 4.4.3.1 |
SIB2, SIB3, SIB10 and SIB11 are transmitted |
|
|
} |
|||
Table 14.1.3.3-2: Void
Table 14.1.3.3-3: Void
Table 14.1.3.3-4: Void
Table 14.1.3.3-5: Void
Table 14.1.3.3-6: Paging (step 1 and step 4, Table 14.1.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-7 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Paging ::= SEQUENCE { |
|||
|
pagingRecordList |
Not present |
||
|
systemInfoModification |
Not present |
||
|
etws-Indication |
true |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
||
|
} |
|||
14.2 ETWS reception in RRC_CONNECTED state / Duplicate detection
14.2.1 Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state and follow the reception of Paging message with etws-Indication }
ensure that {
when { UE start to acquire ETWS message from SIB10 and SIB11 }
then { UE successfully received the ETWS message and activated the “User Alerting” popup display }
}
14.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.2.2.4, 5.2.2.17, 5.2.2.18, 5.3.2.3; TS 23.041 clause 9.1.2.
[TS 36.331, clause 5.2.2.4]
The UE shall:
…
1> if the UE is ETWS capable:
2> upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:
3> discard any previously buffered warningMessageSegment;
3> clear, if any, the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2> when the UE acquires SystemInformationBlockType1 following ETWS indication, upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:
3> if schedulingInfoList indicates that SystemInformationBlockType10 is present:
4> start acquiring SystemInformationBlockType10 immediately;
3> if schedulingInfoList indicates that SystemInformationBlockType11 is present:
4> start acquiring SystemInformationBlockType11 immediately;
NOTE 2: UEs shall start acquiring SystemInformationBlockType10 and SystemInformationBlockType11 as described above even when systemInfoValueTag in SystemInformationBlockType1 has not changed.
[TS 36.331, clause 5.2.2.17]
Upon receiving SystemInformationBlockType10, the UE shall:
1> forward the received warningType, warningSecurityInfo (if present), messageIdentifier and serialNumber to upper layers;
[TS 36.331, clause 5.2.2.18]
Upon receiving SystemInformationBlockType11, the UE shall:
1> if there is no current value for messageIdentifier and serialNumber for SystemInformationBlockType11; or
1> if either the received value of messageIdentifier or of serialNumber or of both is different from the current values of messageIdentifier and serialNumber for SystemInformationBlockType11:
2> use the received values of messageIdentifier and serialNumber for SystemInformationBlockType11 as the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2> discard any previously buffered warningMessageSegment;
2> if all segments of a warning message have been received:
3> assemble the warningMessage from the received warningMessageSegment;
3> forward the received warningMessage, messageIdentifier, serialNumber and dataCodingScheme to upper layers;
3> stop reception of SystemInformationBlockType11;
3> discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2> else:
3> store the received warningMessageSegment;
3> continue reception of SystemInformationBlockType11;
1> else if all segments of a warning message have been received:
2> assemble the warningMessage from the received warningMessageSegment;
2> forward the received complete warningMessage, messageIdentifier, serialNumber and dataCodingScheme to upper layers;
2> stop reception of SystemInformationBlockType11;
2> discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
1> else:
2> store the received warningMessageSegment;
2> continue reception of SystemInformationBlockType11;
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall:
…
1> if the etws-Indication is included and the UE is ETWS capable:
2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information modification period boundary;
2> if the schedulingInfoList indicates that SystemInformationBlockType10 is present:
3> acquire SystemInformationBlockType10;
2> if the schedulingInfoList indicates that SystemInformationBlockType11 is present:
3> acquire SystemInformationBlockType11;
[TS 23.041, clause 9.1.2]
…
Figure 4b
…
6. The UE alert the user immediately, using "warning type" value,
– upon the reception of the paging message, if the UE has been configured to receive ETWS warnings over the paging message, and the UE has authenticated the core network of the NodeB it is camped on, or
– if the UE has not been configured to receive ETWS warnings over the paging message, and it received the optional primary notification and security checks based on "timestamp" and "digital signature" for this notification passed.
NOTE: If the UE received the ETWS warnings over the paging and also received the optional primary notification, it will silently discard the optional primary notification.
NOTE: When the "warning type" is ‘test’, the UE silently discards the paging message, and the optional primary notification, and do not perform the reception of the broadcast message described below. However, the UE specially designed for testing purposes may perform user alerting described above and proceed to the reception of the broadcast message described below
NOTE: If the UE has been configured to receive ETWS warnings over paging message but it has not authenticated the core network of the NodeB it is camped on, the UE does not receive the paging message and the optional primary notification, and do not perform the reception of the broadcast message described below.
Upon the reception of the paging message, whether the UE is configured to receive ETWS warnings over paging message or not, the UE activates the reception of the broadcast messages containing the "warning message" as the secondary notification, as follows:
– If both the "digital signature" and "timestamp" are present in the "warning message" and security checks fail, then the UE notifies the user of this fact and stops the user alerting.
– If both the "digital signature" and "timestamp" are present and security checks pass, then the UE indicates the contents of the "warning message" to the user along with an indication that the message has been authenticated.
– In other cases, the UE indicates the contents of the "warning message" to the user along with an indication that the message has not been authenticated.
Unless both the "digital signature" and "timestamp" are present and the security checks pass, the UE shall ignore the message, return to normal idle mode, and ignore paging messages with the "ETWS indication" for the next [X] seconds.
NOTE: Repetition period [X] is subject to regulatory requirements.
The UE shall consider a message duplicated if the combination of "message identifier" and "serial number" matches that of the previous message received from the same PLMN. The UE shall ignore messages detected as duplicated. If both the "digital signature" and "timestamp" are present, the UE shall perform security check before duplicate message detection. Duplicate message detection shall be performed independently for primary and secondary notifications.
7. The RNC node sends a BMC REPORT-SUCCESS to the CBC in response to Write-Replace.
8. CBC sends acknowledgement message to CBE.
14.2.3 Test description
14.2.3.1 Pre-test conditions
System Simulator:
- Cell 1
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) according to [18].
14.2.3.2 Test procedure sequence
Table 14.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
– |
– |
||
|
1 |
The SS include an ETWS message with new messageIdentifier and serialNumber in SystemInformationBlockType10 and SystemInformationBlockType11 and transmit a Paging message including etws-Indication on Cell 1 (NOTE 1). |
<– |
Paging |
– |
– |
|
2 |
Check: Does the UE indicate the contents of the "warning message" to the user, and alert or activate alerting the user (NOTE 2)? |
– |
– |
1 |
P |
|
3 |
The SS wait for 10s. |
– |
– |
– |
– |
|
4 |
The SS include an ETWS message with same messageIdentifier and serialNumber in SystemInformationBlockType10 and SystemInformationBlockType11 and transmit a Paging message including etws-Indication on Cell 1 (NOTE 1). |
<– |
Paging |
– |
– |
|
5 |
Check: Does the UE indicate the contents of the "warning message" to the user, or alert or activate alerting the user (NOTE 2)? |
– |
– |
1 |
F |
|
NOTE 1: SystemInformationBlockType11 contain 3 segments. NOTE 2: The data indication and user alerting are the UE implementation issues. |
|||||
14.2.3.3 Specific message contents
Table 14.2.3.3-1: SystemInformationBlockType1 for Cell 1 (all steps, Table 14.2.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.2-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType1 ::= SEQUENCE { |
|||
|
schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {} |
Combination 8 in TS 36.508 section 4.4.3.1 |
SIB2, SIB3, SIB10 and SIB11 are transmitted |
|
|
} |
|||
Table 14.2.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell 1 (all steps when UE under test is CAT M1, Table 14.2.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.2-3A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType1-BR-r13 ::= SEQUENCE { |
|||
|
schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {} |
Combination 8 in TS 36.508 section 4.4.3.1 |
SIB2, SIB3, SIB10 and SIB11 are transmitted |
|
|
} |
|||
Table 14.2.3.3-2: Void
Table 14.2.3.3-3: Void
Table 14.2.3.3-4: Void
Table 14.2.3.3-5: Void
Table 14.2.3.3-6: Paging (step 1 and step 4, Table 14.2.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-7 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Paging ::= SEQUENCE { |
|||
|
pagingRecordList |
Not present |
||
|
systemInfoModification |
Not present |
||
|
etws-Indication |
true |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
||
|
} |
|||