Below are the steps how do UE read when there is a ETWS notification from NW.
SIB 10 and SIB 11 are the responsible SIB's for ETWS.
Where SIB10 carry info about primary notification and SIB11 will carry info for secondary notification.
This we can get from below test case according 3GPP spec TS-36.523-1
14.1 ETWS reception in RRC_IDLE state / Duplicate detection
14.2 ETWS reception in RRC_CONNECTED state / Duplicate detection
According the Test Case Below is the steps included for the Test case,
SIB 10 and SIB 11 are the responsible SIB's for ETWS.
Where SIB10 carry info about primary notification and SIB11 will carry info for secondary notification.
This we can get from below test case according 3GPP spec TS-36.523-1
14.1 ETWS reception in RRC_IDLE state / Duplicate detection
14.2 ETWS reception in RRC_CONNECTED state / Duplicate detection
According the Test Case Below is the steps included for the Test case,
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 (NOTE1).
|
<--
|
Paging
|
-
|
-
|
2
|
Check: Does the UE indicate the contents of the
"warning message" to the user, and alert or activate alerting the
user (NOTE2)?
|
-
|
-
|
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 (NOTE1).
|
<--
|
Paging
|
-
|
-
|
5
|
Check: Does the UE indicate the contents of the
"warning message" to the user, or alert or activate alerting the
user (NOTE2)?
|
-
|
-
|
1
|
F
|
NOTE1: SystemInformationBlockType11 contain 3 segments.
NOTE2: The data indication and
user alerting are the UE implementation issues.
|
Paging Message for the test case will be as below,
Derivation Path: 36.508 Table 4.6.1-7
|
|||
Information Element
|
Value/remark
|
Comment
|
Condition
|
Paging ::= SEQUENCE {
|
|||
pagingRecordList
|
Not present
|
Not needed as this is for all the UE
|
|
systemInfoModification
|
Not present
|
||
etws-Indication
|
true
|
This filed will be true for ETWS notification
|
|
nonCriticalExtension SEQUENCE {}
|
Not present
|
||
}
|
SIB1 Content will be like below,
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
|
|
}
|
1. Paging to UE for ETWS (Paging will be there for both Idle and Connected Mode)
2. UE Reads SIB1 , where "systemInfoValueTag" will be 1 and will contain scheduling info about
3. SIB10 and SIB11.
4. UE reads other SIB's accordingly
5. User will be notified via alert messages/tones/both as per UE implementation.
2. UE Reads SIB1 , where "systemInfoValueTag" will be 1 and will contain scheduling info about
3. SIB10 and SIB11.
4. UE reads other SIB's accordingly
5. User will be notified via alert messages/tones/both as per UE implementation.
Source: 3GPP TS-36.523-1
No comments:
Post a Comment