ETWS (eRAN15.1 01) PDF

eRAN
ETWS Feature Parameter

Description
Issue 01
Date 2019-06-06
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

eRAN
ETWS Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 01 (2019-06-06)............................................................................................................................................1
1.2 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 1
2 About This Document.................................................................................................................. 3

2.1 General Statements......................................................................................................................................................... 3
2.2 Applicable RAT.............................................................................................................................................................. 4
2.3 Features in This Document.............................................................................................................................................4
2.4 Feature Differences Between FDD and TDD.................................................................................................................4
3 Overview......................................................................................................................................... 5
4 ETWS................................................................................................................................................7
4.1 Principles........................................................................................................................................................................ 7
4.1.1 ETWS Warning Notification Types.............................................................................................................................7
4.1.2 ETWS Notification Area............................................................................................................................................. 8
4.1.3 ETWS Warning Notification Broadcast Procedure..................................................................................................... 9
4.1.3.1 Warning Notification Broadcast Procedure.............................................................................................................. 9
4.1.3.2 ETWS Processing in eNodeBs............................................................................................................................... 11
4.1.4 PWS Restart Indication Process................................................................................................................................ 15
4.2 Network Analysis......................................................................................................................................................... 15
4.2.1 Benefits...................................................................................................................................................................... 15
4.2.2 Impacts.......................................................................................................................................................................15
4.3 Requirements................................................................................................................................................................ 18
4.3.1 Licenses..................................................................................................................................................................... 18
4.3.2 Software.....................................................................................................................................................................18
4.3.3 Hardware................................................................................................................................................................... 19
4.3.4 Others.........................................................................................................................................................................19
4.4 Operation and Maintenance..........................................................................................................................................19
4.4.1 Data Configuration.................................................................................................................................................... 19
4.4.1.1 Data Preparation..................................................................................................................................................... 19
4.4.1.2 Using MML Commands......................................................................................................................................... 21
4.4.1.3 Using the CME....................................................................................................................................................... 22
4.5 Activation Verification................................................................................................................................................. 22
4.6 Network Monitoring..................................................................................................................................................... 23
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
ETWS Feature Parameter Description Contents
4.7 Possible Issues.............................................................................................................................................................. 23
5 Parameters..................................................................................................................................... 25
6 Counters........................................................................................................................................ 26
7 Glossary......................................................................................................................................... 27
8 Reference Documents................................................................................................................. 28
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
ETWS Feature Parameter Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 01 (2019-06-06)

This issue does not include any changes.
1.2 eRAN15.1 Draft A (2019-01-05)

This issue introduces the following changes to eRAN13.1 01 (2018-04-10).
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added support for the Added the FDD l 3900 and 5900
public warning system PwsRestartIndica- TDD series base
(PWS) restart indication tionSwitch option to the stations
function. For details, see GlobalProcSwitch.Prot l DBS3900
the following sections: ocolSupportSwitch LampSite and
l 4.1.4 PWS Restart parameter. DBS5900
Indication Process LampSite
l 4.4 Operation and l BTS3912E
Maintenance l BTS3911E
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
ETWS Feature Parameter Description 1 Change History
Editorial Changes
Changed the name of Huawei mobile element management system from U2000 to U2020.
Revised descriptions in this document.

eRAN
ETWS Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
l The technical principles of features and their related parameters

l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l Parameter configuration required for feature activation, verification of feature activation,
and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and feature
gains depend on the specifics of the network scenario where the feature is deployed. To achieve
the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document
apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a description does
not apply to all RATs, the specific RAT that it does apply to will be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-MIMO", "TDD
cells" indicates that this function cannot be used in non-TDD cells.

eRAN
ETWS Feature Parameter Description 2 About This Document
2.2 Applicable RAT

This document applies to FDD/TDD.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LBFD-002029 Earthquake and Tsunami 4 ETWS

Warning System (ETWS)
This document describes the following TDD features.
Feature ID Feature Name Section
TDLBFD-002029 Earthquake and Tsunami 4 ETWS

Warning System (ETWS)
2.4 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Section
LBFD-002029 TDLBFD-002029 None 4 ETWS

Earthquake and Earthquake and
Tsunami Warning Tsunami Warning
System (ETWS) System (ETWS)

eRAN
ETWS Feature Parameter Description 3 Overview
3 Overview
The earthquake and tsunami warning system (ETWS) enables governments or other official
organizations to broadcast warning notifications about natural disasters (for example,
earthquakes or tsunamis) to the public through public land mobile networks (PLMNs).
Figure 3-1 ETWS network architecture
ETWS is implemented on the UEs, eNodeBs, mobility management entity (MME), and cell
broadcast center (CBC) in compliance with 3GPP specifications.
The warning notification provider (WNP) refers to the government or other official
organizations that provide warning notifications. Communications between the WNP and
CBC comply with other standards, not with 3GPP specifications. One or more WNPs publish
ETWS warning notifications to a PLMN, and the PLMN broadcasts the notifications to
ETWS-capable UEs in specified areas, which are known as notification areas. After receiving
the warning notifications, the UEs alert users, for example, by sound, screen blinking, or
vibration. The following table describes the functions of network elements (NEs) related to
the ETWS feature.

eRAN
ETWS Feature Parameter Description 3 Overview
Table 3-1 Functions of NEs related to the ETWS feature

NE Function
UE Receives warning notifications in either idle or connected mode. The UE must

support ETWS.
eNodeB Processes ETWS signaling messages. For details, see section 8.12 in 3GPP
TS 36.413.
MME Processes ETWS signaling messages to be transmitted over the S1 interface.

For details, see section 4.4.2 in 3GPP TS 23.401 V8.0.0.
CBC Converts and distributes signaling messages between the PLMN and a non-
PLMN network. For details, see section 5 in 3GPP TS 23.041 V8.0.0.
WNP Publishes warning notifications.

eRAN
ETWS Feature Parameter Description 4 ETWS
4 ETWS
4.1 Principles
4.1.1 ETWS Warning Notification Types

ETWS warning notifications are classified into primary notifications (PNs) and secondary
notifications (SNs) according to purposes and urgency.
PN
PNs are used to warn users about imminent disasters as soon as possible, and to provide the
most urgent and important information.
According to 3GPP TS 23.041, the maximum size of each PN is 50 bytes. PNs are delivered
in SIB10.
SN
SNs provide additional and less urgent information, such as instructions on what to do and
where to get help. SNs are not delay-sensitive.
According to 3GPP TS 36.413, the size of an ETWS SN cannot exceed:
l Maximum bearing capability of the S1 interface (9600 bytes)

l Maximum bearing capability of the eNodeB (over the Uu interface)
If the size exceeds the maximum bearing capability of the eNodeB, the SN is fragmented
before being delivered. According to 3GPP specifications, each SN can be fragmented
into a maximum of 64 segments. Information about ETWS SNs and the number of SN
segments are carried in SIB11.
The maximum bearing capability of an eNodeB is subject to parameters such as:
l Downlink cell bandwidth

l System information (SI) window size
l Cyclic prefix (CP) formats

eRAN
l Number of logical antennas

If an ETWS SN is fragmented into 64 segments and the size of each SN segment still exceeds
the maximum bearing capability of an eNodeB, the eNodeB fails to deliver the ETWS SN.
Table 4-1 lists the maximum bearing capability of an eNodeB under common downlink cell
bandwidths when the following conditions are met:
l The SI window size is 10 ms.
l Normal CP is used.
l Two logical antennas are configured.
Table 4-1 Maximum bearing capability of the eNodeB

RAT Downlink Cell SN Segment Size Maximum ETWS SN
Bandwidth (MHz) (Byte) Size (Byte)
FDD 1.4 39 2496 (39 x 64)
FDD 3 22 1408 (22 x 64)
FDD 5 51 3264 (51 x 64)

TDD
FDD 10 115 7360 (115 x 64)

TDD
FDD 15 175 11200 (175 x 64)

TDD
FDD 20 207 13248 (207 x 64)

TDD
The target bit rate for transmitting ETWS SNs is 0.083 when 1.4 MHz bandwidth is used, and is 0.027
when other bandwidths are used. The target bit rate is specified by the CellSiMap.SiTransEcr
parameter.
4.1.2 ETWS Notification Area

A notification area specifies the scope within which ETWS warning notifications are
broadcast. Notification areas can be planned on a cell, emergency area, or tracking area basis.
Under standard conditions, an emergency area is larger than a cell, and a tracking area is
larger than an emergency area, as shown in Figure 4-1.

eRAN
Figure 4-1 ETWS notification area
The principles for planning notification areas are as follows:

l If notification areas are planned on a cell or tracking area basis, no additional parameter
settings are required.
l If notification areas are planned on an emergency area basis, operators must plan
emergency areas in advance and set the EmergencyAreaId parameter. There are two
configuration modes:
– Cell.EmergencyAreaId: This parameter is valid only when the
Cell.EmergencyAreaIdCfgInd parameter is set to CFG. One emergency area can
be configured for each single cell.
– CellEmergencyArea.EmergencyAreaId: A single cell can be configured with one
or more emergency area IDs. A maximum of 16 emergency area IDs can be
configured for each single cell.
The Cell.EmergencyAreaIdCfgInd and Cell.EmergencyAreaId parameters will be
disused in later versions. Therefore, avoid using these parameters. For eNodeBs using
the preceding two parameters, you are advised to use the
CellEmergencyArea.EmergencyAreaId parameter instead.
l It is recommended that notification areas be planned on a tracking area basis because:
– A single cell is too small for a notification area. A list of cells may meet the
coverage requirement of a notification area, but are more difficult to serve as a
notification area because the cell list must be determined by the EPC.
– Planning and defining emergency areas requires extra workload.
– A tracking area is the most suitable for a notification area, in terms of coverage
scope, maintenance, and project implementation.
4.1.3 ETWS Warning Notification Broadcast Procedure
4.1.3.1 Warning Notification Broadcast Procedure

Figure 4-2 shows the procedure for broadcasting a warning notification.

eRAN
Figure 4-2 Warning notification broadcast procedure
1. The WNP detects disaster information and decides to publish warning notifications to the
public using the PLMN.
2. The WNP sends an Emergency Broadcast Request message to the CBC.
3. The CBC converts the received Emergency Broadcast Request message into a
standardized signaling message Write-Replace Warning Request defined by 3GPP TS
29.168 and then sends the message to the MME.
4. The MME sends a Write-Replace Warning Response message to the CBC, informing the
CBC that it has started forwarding the warning notification to the eNodeB.
5. The CBC responds to the WNP with an Emergency Broadcast Response message,
informing the WNP that warning notification broadcast has been started.
6. The MME forwards the Write-Replace Warning Request message to the eNodeB within
the notification areas indicated by the Warning Area List IE in this message.
l Each eNodeB supports a maximum of 4096 notification areas. Therefore, the Warning Area
List IE in the Write-Replace Warning Request message delivered by the MME contains no
more than 4096 notification areas.
l Each eNodeB can receive a maximum of 16 Write-Replace Warning Request messages per
second. If the MME delivers more than 16 Write-Replace Warning Request messages per
second, the eNodeB will discard the redundant ones. For example, if the MME delivers 18
Write-Replace Warning Request messages within 1s, the eNodeB discards the last two
received messages.
7. The eNodeB determines whether the cells configured on the eNodeB are located in a
notification area indicated by the Warning Area List IE in the Write-Replace Warning
Request message and sends the MME a Write-Replace Warning Response message,

eRAN
notifying the MME of the areas where the eNodeB starts broadcasting the warning
notification.
8. The eNodeB pages the UEs located in the notification areas and starts broadcasting
SIB10 or SIB11.
4.1.3.2 ETWS Processing in eNodeBs
ETWS Procedure
Figure 4-3 shows ETWS processing in an eNodeB after the eNodeB receives the Write-
Replace Warning Request message.
Figure 4-3 ETWS procedure
If not all warning notifications are broadcast due to a cell restart, the notifications that are not broadcast
are cleared and not delivered after the cell restart.

eRAN
Determining a Notification Area
Figure 4-4 Determining a notification area
Upon determining that no notification areas exist, the eNodeB does not broadcast ETWS PNs
or SNs. In this case, the eNodeB responds to the MME with a Write-Replace Warning
Response message containing no Broadcast Completed Area List IE. Upon receiving this
message, the MME considers that the broadcast failed. The MME notifies the WNP of the
failure through the CBC, and then the WNP determines follow-up handling policies based on
the network plan.
Broadcasting ETWS PNs
Figure 4-5 Broadcasting ETWS PNs
CellSiMap.Sib10Period specifies the SIB10 broadcast period. CellSiMap.EtwsPnDuration

specifies the total SIB10 broadcast period. When the broadcast period expires, the eNodeB
stops broadcasting SIB10.
eNodeBs deliver ETWS PNs to the UE through SIB10. The number of broadcast times of each SIB10 is
related to the SI sending policy. SIB10 may be transmitted repeatedly in an SI window. For details, see
Idle Mode Management Feature Parameter Description.

eRAN
ETWS PN Overlap Policy
Figure 4-6 ETWS PN overlap policy
CellSiMap.EtwsPnOverlapPolicy specifies the ETWS PN overlap policy as follows:

l MERGE
The eNodeB stops ongoing PN broadcasting and starts broadcasting newly received PNs.
l DISCARD
The eNodeB discards the newly received PNs and continues ongoing PN broadcasting.
Broadcasting ETWS SNs
Figure 4-7 Broadcasting ETWS SNs

eRAN
Table 4-2 ETWS SN broadcast policies

Repetition Number of ETWS SN Broadcast Policy
Period Broadcasts
Requested
=0 =1 The eNodeB broadcasts the ETWS SN only once.
≠1 The eNodeB does not broadcast ETWS SNs.
>0 ≥1 The eNodeB broadcasts ETWS SNs at an interval specified

by Repetition Period. The number of broadcast times is
equal to Number of Broadcasts Requested.
=0 The eNodeB does not broadcast ETWS SNs.
l Both the Repetition Period and Number of Broadcasts Requested IEs are present in the Write-
Replace Warning Request message.
l CellSiMap.Sib11Period has no impact on the Repetition Period IE. The Repetition Period IE
specifies the ETWS SN broadcast period in seconds. ETWS SNs are delivered to the UE through
SIB11. CellSiMap.Sib11Period specifies the SIB11 broadcast period in multiples of 10 ms.
l The number of broadcast times of each SIB11 is related to the SI sending policy. SIB11 may be
transmitted repeatedly in an SI window. For details, see Idle Mode Management.
ETWS SN Overlap Policy
Figure 4-8 ETWS SN overlap policy
CellSiMap.EtwsSnOverlapPolicy specifies the ETWS SN overlap policy as follows:

l MERGE
The eNodeB stops ongoing SN broadcasting and starts broadcasting newly received SNs.
l DISCARD
The eNodeB discards the newly received SNs and continues ongoing SN broadcasting.

eRAN
4.1.4 PWS Restart Indication Process

The PWS restart indication process is controlled by the PwsRestartIndicationSwitch option
of the GlobalProcSwitch.ProtocolSupportSwitch parameter. If this option is selected, the
eNodeB sends a PWS Restart Indication message to the MME to instruct the CBC to reload
the warning notification after the cells served by the eNodeB are reset (that is, the cell status
changes from unavailable to available).
l When the eNodeB is connected to only one MME:
The eNodeB directly sends a PWS Restart Indication message to the MME and measures
the L.Signal.PWS.RestartIndication.Num counter.
l When the eNodeB is connected to multiple MMEs:
The eNodeB sends PWS Restart Indication messages to multiple MMEs and measures
the L.Signal.PWS.RestartIndication.Num counter for only once.
– Non-RAN sharing scenario
The eNodeB sends PWS Restart Indication messages to any two available MMEs to
avoid the case that messages fail to be sent to the CBC due to MME-CBC faults.
– RAN sharing scenario
The eNodeB sends PWS Restart Indication messages to any two available MMEs
corresponding to each PLMN. If a PLMN corresponds to only one MME, the
eNodeB only sends a PWS Restart Indication message to this MME.
4.2 Network Analysis
4.2.1 Benefits
ETWS enables the system to broadcast earthquake and tsunami warning information to users,
including when and where to evacuate, minimizing the damage caused by disasters.
4.2.2 Impacts
Network Impacts
l When the CellPdcchAlgo.PdcchSymNumSwitch parameter is not set to OFF, ETWS
may trigger PDCCH symbol adaptation. If this occurs, the downlink cell throughput may
decrease by 9%.
l Broadcasting ETWS warning notifications over the air interface occupies air interface
resources, affecting the downlink cell throughput. The impact on downlink cell
throughput depends on the volume of ETWS warning notifications, transmission bit rate,
the number of times these notifications are retransmitted, and the SIB10 or SIB11
broadcast period.

eRAN
Function Impacts
RAT Functio Function Switch Reference Description
n Name
FDD Physical N/A Physical After ETWS is triggered, SIB10,

TDD channel Channel SIB11, and paging messages are
manage Resource transmitted on the PDCCH. To
ment Manageme ensure timely and reliable delivery
nt of SIB10, SIB11, and paging
messages, the eNodeB determines
whether to adjust the number of
PDCCH symbols based on the
system bandwidth, number of
PDCCH symbols, and value of the
CellPdcchAlgo.PdcchSymNumS
witch parameter.
l When the
CellPdcchAlgo.PdcchSymNu
mSwitch parameter is set to
OFF:
PDCCH symbol adaptation is
disabled. If a small number of
PDCCH symbols are
configured, SIB10, SIB11, or
paging messages may not be
delivered timely or reliably. For
details about the setting
suggestions of the
CellPdcchAlgo.InitPdcchSym
Num parameter, see Physical
Channel Resource
Management.
l When the
CellPdcchAlgo.PdcchSymNu
mSwitch parameter is set to
ON or ECFIADAPTIONON:
PDCCH symbol adaptation is
enabled. Table 4-3 describes
the adjustment principles.

eRAN
RAT Functio Function Switch Reference Description

n Name
FDD RF CellRfShutdown. Energy After RF channel intelligent

TDD channel RfShutdownSwitc Conservati shutdown is enabled, if the
intellige h on and CellRfShutdown.RsPwrAdjOffset
nt Emission parameter is set to a non-zero
shutdow Reduction value, the number of available
n downlink RBs decreases by a
maximum of 75% due to increased
reference signal power.
Additionally, the supported length
of warning information delivered
over the Uu interface is shortened
by a maximum of 75%, and such
information may not be delivered
to UEs in the cell. This will cause
the following impacts:
l For PNs: If the length of the
warning information exceeds
the shortened length, the PN
warning information cannot be
delivered to UEs in the cell.
l For SNs: The number of
segments of the warning
information increases and more
time is required to broadcast
such information over the Uu
interface. If the number of
segments exceeds the
supported number, the SN
warning information cannot be
delivered to UEs in the cell.
FDD Adaptive l CellAlgoSwitc Energy This function affects network

power h.DynAdjVoltS Conservati performance. RF module regular
control witch on and time sleep mode enables RF
l eNodeBAutoP Emission modules to turn off and on, as
owerOff.Auto Reduction scheduled by the operator. When a
PowerOffSwitc cell enters the sleep mode, it
h cannot provide any services. The
alarm broadcast information
cannot be delivered to UEs in the
cell.

eRAN
Table 4-3 Principles for adjusting the number of PDCCH symbols

RAT System Adjusting Mode Remarks
Bandwidth
(MHz)
FDD 1.4 The number of PDCCH The number of PDCCH

symbols is not adjusted. symbols has reached the
maximum value of 4 and no
adjustment can be performed.
FDD 3 The number of PDCCH The number of PDCCH

symbols is not adjusted. symbols has reached the
maximum value of 3 and no
adjustment can be performed.
FDD 5 The number of PDCCH The number of PDCCH

TDD symbols increases only when symbols is restored to the
fewer than three PDCCH original value after ETWS is
symbols are used. complete.
FDD 10 or 15 The number of PDCCH The number of PDCCH

TDD symbols increases only when symbols is restored to the
fewer than two PDCCH original value after ETWS is
symbols are used. complete.
FDD 20 The number of PDCCH In this scenario, the number

TDD symbols is not adjusted. of PDCCH symbols does not
need to be increased.
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Prerequisite Functions
RAT Function Name Function Switch Reference
FDD 3GPP R8 None None

TDD specifications
FDD System information None Idle Mode

TDD broadcast Management

eRAN
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.3.4 Others
The MME, CBC, and UEs must support ETWS.
Before deploying this feature, ensure that the following requirements are met:
l The MME, CBC, and UEs support ETWS.
l The same notification areas are defined in WNPs and PLMNs.
– If notification areas are planned on a cell or tracking area basis, no notification area
information needs to be collected.
– If notification areas are planned on an emergency area basis, collect information
about notification areas defined in WNPs to plan the cells in the emergency areas.
For example, if a WNP defines city A as a notification area, configure emergency
area IDs for each cell in city A.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation

The following table describes the parameters that must be set in a CellEmergencyArea MO
when notification areas are planned on an emergency area basis and the operator's network
management system (NMS) supports the CellEmergencyArea MO.

eRAN
Parameter Name Parameter ID Setting Notes
Emergency Area ID CellEmergencyAr- l A maximum of 16

ea.EmergencyAreaId emergency area IDs can be
configured for each single
cell.
l Based on the configured
parameters on the live
network, set the
Cell.EmergencyAreaIdCf-
gInd parameter to
NOT_CFG and add the
Cell.EmergencyAreaId
parameter to the
CellEmergencyArea MO.
The following table describes the parameters that must be set in a Cell MO when the
operator's NMS does not support the CellEmergencyArea MO.
Parameter Name Parameter ID Setting Notes
Local Cell ID Cell.LocalCellId None
Emergency Area Id Cell.EmergencyAreaIdCfgInd l Set this parameter to CFG

indicator if notification areas are
planned on an emergency
area basis.
l Set this parameter to
NOT_CFG if notification
areas are planned on a cell
or tracking area basis.
Emergency Area ID Cell.EmergencyAreaId A maximum of one

emergency area can be
configured for each single
cell.
Parameter Parameter ID Setting Notes

Name
SIB10 period CellSiMap.Sib Set this parameter to RF16.

10Period
SIB11 period CellSiMap.Sib Set this parameter to RF32.

11Period
ETWS PN CellSiMap.Etw Set this parameter to 6.

message sPnDuration
duration time

eRAN
Parameter Parameter ID Setting Notes

Name
ETWS SN CellSiMap.Etw Set this parameter to DISCARD.

message sSnOverlapPoli
overlap policy cy
ETWS PN CellSiMap.Etw Set this parameter to DISCARD.

message sPnOverlapPoli
overlap policy cy
l The Cell.EmergencyAreaIdCfgInd and Cell.EmergencyAreaId parameters will be disused in later

versions. Therefore, avoid using these parameters. For eNodeBs using the preceding two parameters,
you are advised to use the CellEmergencyArea.EmergencyAreaId parameter instead.
l If the CellEmergencyArea.EmergencyAreaId parameter is configured in the cell, the setting of this
parameter takes effect on the cell. If the CellEmergencyArea.EmergencyAreaId parameter is not
configured and the Cell.EmergencyAreaIdCfgInd parameter is set to CFG in a cell, the setting of
the Cell.EmergencyAreaId parameter takes effect.
l A maximum of 144 different emergency area IDs in CellEmergencyArea and Cell MOs can be
configured for each eNodeB.
The following table describes the parameter that must be set in a GlobalProcSwitch MO to
enable the PWS restart indication function.
Parameter Parameter ID Option Setting Notes

Name
Protocol GlobalProcSwi PwsRestartIndicationS- Select this option.

Procedure tch.ProtocolSu witch
Support Switch pportSwitch
4.4.1.2 Using MML Commands
Activation Command Examples

//(Optional) Configuring the emergency area IDs for cells when notification areas
are planned on an emergency area basis
//(Optional) Method 1: Running the MOD CELL command
MOD CELL: LocalCellId=0, EmergencyAreaIdCfgInd=CFG, EmergencyAreaId=0;
//(Optional) Method 2: Running the ADD CELLEMERGENCYAREA command
ADD CELLEMERGENCYAREA: LocalCellId=0, EmergencyAreaId=0;
ADD CELLEMERGENCYAREA: LocalCellId=0, EmergencyAreaId=1;
//Running the MOD CELLSIMAP command to configure the PN broadcast duration, the
transmission periods for SIB10 and SIB11, and the policies of processing repeated
PN and SN broadcasts
MOD CELLSIMAP: LocalCellId=0, Sib10Period=RF16, Sib11Period=RF32,
EtwsPnDuration=7, EtwsSnOverlapPolicy=DISCARD, EtwsPnOverlapPolicy=MERGE;
//(Optional) Running the MOD GLOBALPROCSWITCH command to configure the PWS
restart indication switch
MOD GLOBALPROCSWITCH: LocalCellId=0,
ProtocolSupportSwitch=PwsRestartIndicationSwitch-1;

eRAN
Deactivation Command Examples

ETWS is a basic feature, and cannot be deactivated.
4.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.
4.5 Activation Verification

ETWS is activated successfully when ETWS message handling processes are normal over the
S1 and Uu interfaces.
To trace messages over the S1 and Uu interfaces, perform the following steps on the U2020:
Step 1 Enable the EPC to send a Write-Replace Warning Request message to eNodeBs.
Step 2 Trace the S1 messages sent to and from all eNodeBs located in the notification areas, which
are indicated in the Write-Replace Warning Request message. If the Write-Replace Warning
Request and Write-Replace Warning Response messages can be traced, the message exchange
over the S1 interfaces is normal. Figure 4-9 shows the S1 interface trace result.
Figure 4-9 S1 interface trace result
Step 3 Trace the Uu messages, including paging messages and RRC_SYS_INFO messages sent from
the eNodeBs. Figure 4-10 shows the Uu interface trace result.
Figure 4-10 Uu interface trace result
Step 4 Double-click the RRC_SYS_INFO message to check SIB10 and SIB11. If SIB10 contains a
PN and SIB11 contains an SN in the RRC_SYS_INFO message, the message exchange over
the Uu interface is normal. Figure 4-11 and Figure 4-12 show an SIB10 and an SIB11,
respectively.

eRAN
Figure 4-11 SIB10
Figure 4-12 SIB11
----End
4.6 Network Monitoring

The following table lists the counters that measure the numbers of messages and notifications
after feature activation.
Counter ID Counter Name
1526729291 L.Signal.Num.WRWR.ETWS
1526746000 L.Signal.Num.PN.ETWS
1526746001 L.Signal.Num.SN.ETWS
1526749437 L.Signal.PWS.RestartIndication.Num
4.7 Possible Issues

Fault Description
When ETWS is activated, the eNodeB cannot broadcast ETWS SNs.
Fault Handling
Step 1 Contact Huawei technical support to determine the maximum size of each ETWS SN
fragment supported by each eNodeB based on the downlink cell bandwidth, SI window size,
CP format, and number of logical antennas.

eRAN
The maximum SN size supported by each eNodeB equals the SN fragment size multiplied by
64.
Step 2 Check whether the SN to be broadcast is larger than the maximum SN size.
l If yes, the WNP reconfigures the SN delivery policies, such as adjusting the SN size or
delivering SNs in batches.
l If not, contact Huawei technical support.
----End

eRAN
ETWS Feature Parameter Description 5 Parameters
5 Parameters
The following hyperlinked EXCEL files of parameter documents match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.

l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
l eNodeBFunction Used Reserved Parameter List: contains the reserved parameters that
are in use and those that have been disused.
You can find the EXCEL files of parameter reference and used reserved parameter list for the software
version used on the live network from the product documentation delivered with that version.
FAQ 1: How do I find the parameters related to a certain feature from parameter
reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter from the used
reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT columns
to locate the reserved parameter, which may be only a bit of a parameter. View its
information, including the meaning, values, impacts, and product version in which it is
activated for use.
----End

eRAN
ETWS Feature Parameter Description 6 Counters
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1 Open the EXCEL file of performance counter reference.
Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
ETWS Feature Parameter Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
ETWS Feature Parameter Description 8 Reference Documents
8 Reference Documents
1. 3GPP TS 22.168, "Earthquake and Tsunami Warning System (ETWS) requirements;

Stage 1"
2. 3GPP TR 22.968, "Study for requirements for a Public Warning System (PWS) service"
3. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
4. 3GPP TR 23.828, "Earthquake and Tsunami Warning System (ETWS) Requirements and
Solutions;Solution Placeholder"
5. 3GPP TS 29.168, "Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage
3"
6. 3GPP TS 36.331, "Radio Resource Control (RRC); Protocol specification"
7. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
8. Idle Mode Management
9. Physical Channel Resource Management
10. Energy Conservation and Emission Reduction

ETWS (eRAN15.1 01) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ETWS (eRAN15.1 01) PDF

Uploaded by

Copyright:

Available Formats

eRAN

ETWS Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 3

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

4.7 Possible Issues.............................................................................................................................................................. 23

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

1.1 eRAN15.1 01 (2019-06-06)

1.2 eRAN15.1 Draft A (2019-01-05)

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

l The technical principles of features and their related parameters

Feature Differences Between RATs

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 3

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Section

LBFD-002029 Earthquake and Tsunami 4 ETWS

This document describes the following TDD features.

Feature ID Feature Name Section

TDLBFD-002029 Earthquake and Tsunami 4 ETWS

2.4 Feature Differences Between FDD and TDD

LBFD-002029 TDLBFD-002029 None 4 ETWS

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 4

Figure 3-1 ETWS network architecture

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 5

Table 3-1 Functions of NEs related to the ETWS feature

UE Receives warning notifications in either idle or connected mode. The UE must

MME Processes ETWS signaling messages to be transmitted over the S1 interface.

WNP Publishes warning notifications.

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 6

4.1.1 ETWS Warning Notification Types

According to 3GPP TS 36.413, the size of an ETWS SN cannot exceed:

l Maximum bearing capability of the S1 interface (9600 bytes)

The maximum bearing capability of an eNodeB is subject to parameters such as:

l Downlink cell bandwidth

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 7

l Number of logical antennas

Table 4-1 Maximum bearing capability of the eNodeB

FDD 1.4 39 2496 (39 x 64)

FDD 3 22 1408 (22 x 64)

FDD 5 51 3264 (51 x 64)

FDD 10 115 7360 (115 x 64)

FDD 15 175 11200 (175 x 64)

FDD 20 207 13248 (207 x 64)

4.1.2 ETWS Notification Area

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 8

Figure 4-1 ETWS notification area

The principles for planning notification areas are as follows:

4.1.3 ETWS Warning Notification Broadcast Procedure

4.1.3.1 Warning Notification Broadcast Procedure

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 9

Figure 4-2 Warning notification broadcast procedure

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 10

4.1.3.2 ETWS Processing in eNodeBs

Figure 4-3 ETWS procedure

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 11

Determining a Notification Area