CMAS(eRAN7.0_03).pdf

eRAN

CMAS Feature ParameterDescription

Issue 03

Date 2015-07-25

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2015-07-25) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................11.4 Differences Between eNodeB Types..............................................................................................................................4

2 Overview.........................................................................................................................................52.1 Introduction....................................................................................................................................................................52.2 Benefits...........................................................................................................................................................................52.3 Architecture....................................................................................................................................................................5

3 Technical Description...................................................................................................................83.1 CMAS Warning Notification Type................................................................................................................................83.2 CMAS Notification Area................................................................................................................................................93.3 CMAS Warning Notification Broadcast Procedure.....................................................................................................103.3.1 Warning Notification Broadcast Procedure...............................................................................................................103.3.2 CMAS Processing in eNodeBs..................................................................................................................................123.4 CMAS Warning Notification Stop Procedure..............................................................................................................153.4.1 Warning Notification Stop Procedure.......................................................................................................................153.4.2 CMAS Processing in eNodeBs..................................................................................................................................17

4 Related Features...........................................................................................................................19

5 Network Impact...........................................................................................................................20

6 Engineering Guidelines.............................................................................................................216.1 When to Use CMAS.....................................................................................................................................................216.2 Required Information...................................................................................................................................................216.3 Planning........................................................................................................................................................................216.3.1 RF Planning...............................................................................................................................................................216.3.2 Network Planning......................................................................................................................................................226.3.3 Hardware Planning....................................................................................................................................................226.4 Deployment..................................................................................................................................................................226.4.1 Process.......................................................................................................................................................................226.4.2 Requirements.............................................................................................................................................................22

eRANCMAS Feature Parameter Description Contents


ii

6.4.3 Data Preparation........................................................................................................................................................236.4.4 Precautions.................................................................................................................................................................236.4.5 Activation..................................................................................................................................................................246.4.6 Activation Observation..............................................................................................................................................266.4.7 Reconfiguration.........................................................................................................................................................276.4.8 Deactivation...............................................................................................................................................................276.5 Performance Monitoring...............................................................................................................................................286.6 Parameter Optimization................................................................................................................................................286.7 Troubleshooting............................................................................................................................................................28

7 Parameters.....................................................................................................................................29

8 Counters........................................................................................................................................34

9 Glossary.........................................................................................................................................35

10 Reference Documents...............................................................................................................36

eRANCMAS Feature Parameter Description Contents


iii

1 About This Document

1.1 ScopeThis document describes LOFD-001092 CMAS Support, including its technical principles,related features, network impact, and engineering guidelines.

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E and BTS3203E

LampSite DBS3900

Any managed objects (MOs), parameters, alarms, or counters described herein correspond tothe software release delivered with this document. Any future updates will be described in theproduct documentation delivered with future software releases.

This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and"eNodeB" refers to LTE FDD eNodeB.

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described hereinl Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes:

eRANCMAS Feature Parameter Description 1 About This Document


1

l Feature changeChanges in features and parameters of a specified version as well as the affected entities

l Editorial changeChanges in wording or addition of information and any related parameters affected byeditorial changes. Editorial change does not specify the affected entities.

eRAN7.0 03 (2015-07-25)This issue includes the following changes.

ChangeType

Change Description ParameterChange

AffectedEntity

Featurechange

None None N/A

Editorialchange

Revised 3.3.1 Warning Notification BroadcastProcedure.

None N/A

eRAN7.0 02 (2014-09-30)This issue includes the following changes.

ChangeType


AffectedEntity

Featurechange

Added the commercial mobile alert system(CMAS) processing mechanism used by eNodeBswhen the Message Identifier and Serial NumberIEs in the Write-Replace Warning Requestmessage are the same as those in the CMASwarning notification being broadcast and thenotification area specified in the Write-ReplaceWarning Request message differs from thatspecified in the CMAS warning notification beingbroadcast. For details, see 3.3.2 CMASProcessing in eNodeBs.

None N/A

Editorialchange

Revised 3.4.1 Warning Notification StopProcedure.

None N/A

eRAN7.0 01 (2014-04-26)This issue does not include any changes.

eRAN7.0 Draft C (2014-03-07)This issue includes the following changes.



2

ChangeType

Change Description Parameter Change

Affected Entity

Featurechange

None None N/A

Editorialchange

Added 1.4 Differences Between eNodeBTypes, which describes differences infeature support between eNodeB types.

None N/A

eRAN7.0 Draft B (2014-02-28)This issue includes the following changes.

ChangeType


Featurechange

Added the principle for adaptively adjusting the numberof PDCCH symbols in CMAS scenarios with differentsystem bandwidths. For details, see the following sectionsand chapters:l 3.3.2 CMAS Processing in eNodeBsl 4 Related Featuresl 5 Network Impactl 6.4.4 Precautions

None

Editorialchange

None None

eRAN7.0 Draft A (2014-01-20)Compared with Issue 01 (2013-04-28) of eRAN6.0, Draft A (2014-01-20) of eRAN7.0 includesthe following changes.

Change Type Change Description Parameter Change

Feature change Changed the name of Huawei mobileelement management system fromM2000 to U2000.

None

Editorial change Optimized the descriptions of CMASprocessing in eNodeBs. For details,see 3.3.2 CMAS Processing ineNodeBs.

None



3

1.4 Differences Between eNodeB TypesThe features described in this document are implemented in the same way on macro, micro andLampSite eNodeBs.



4

2 Overview

2.1 IntroductionCMAS enables the government or other official organizations to broadcast warning notificationsabout emergencies (for example, an emergency speech by the President, an imminent terroristattack, or a child abduction) to the public through public land mobile networks (PLMNs).

2.2 BenefitsPeople can use their mobile phones to learn about potential threats as soon as possible. Thissystem helps mitigate damage by alerting people more quickly than other forms ofcommunication.

2.3 ArchitectureFigure 2-1 shows the CMAS network architecture.

eRANCMAS Feature Parameter Description 2 Overview


5

Figure 2-1 CMAS network architecture

CBC: cell broadcast center MME: mobility management entity

eNodeB: E-UTRAN NodeB WNP: warning notification provider

As shown in Figure 2-1:

l CMAS belongs to one or more PLMNs and is composed of eNodeBs, MMEs, and CBCs.l The WNP (government or other official organizations) provides warning notifications.

One or more WNPs publish CMAS warning notifications to a PLMN, and the PLMN broadcaststhe notifications to CMAS-capable user equipment (UEs) in specified areas, known asnotification areas. After receiving the warning notifications, the UEs alert users, for example,by sound, screen blinking, and vibration. Users can then act immediately to evacuate, mitigatedamage, and seek assistance.

Table 2-1 describes the functions of network elements (NEs) related to the CMAS feature.

Table 2-1 Functions of related NEs

NE Function

UE Receives CMAS warning notifications ineither idle or connected mode.



6

NE Function

eNodeB Receives CMAS warning notifications overthe S1 interface and broadcasts CMASwarning notifications contained in SIB12over the Uu interface. For details, see section8.12 in 3GPP TS 36.413 V9.2.0.

MME Processes CMAS signaling messages to betransmitted over the S1 interface. For details,see section 4.4.2 in 3GPP TS 23.401.

CBC Converts and distributes signaling messagesbetween the PLMN and a non-PLMNnetwork. The conversion enables the PLMNto receive information delivered by the WNP.For details, see chapter 5 in 3GPP TS 23.041.

WNP Generates warning notifications. WNPs areusually the government or other officialorganizations.



7

3 Technical Description

3.1 CMAS Warning Notification TypeCMAS warning notifications are delivered to UEs using system information block type 12(SIB12).

A warning notification or warning notification segments are delivered in SIB12 informationelements (IEs) in SystemInformation messages.

If a warning notification is larger than the size of SIB12, the warning notification can befragmented before being delivered. The size of each warning notification segment is determinedby the size of SIB12. The total size of segments per warning notification cannot exceed 9600bytes.

The warning notification segment size is specified by parameters such as the downlink cellbandwidth, system information (SI) window size, cyclic prefix (CP) format, and number oflogical antennas.

If a warning notification contains a large amount of information, the warning notification needsto be fragmented before being delivered. However, limited by system resources and parametersettings, the warning notification segment size may be too small to carry the warning notification.When this occurs, the eNodeB cannot broadcast the warning notification.

Table 3-1 lists the CMAS warning notification fragment size and maximum warning notificationsize under common downlink cell bandwidths when the SI window size is 10 ms, normal CP isused, and two logical antennas are configured. A CMAS warning notification can be fragmentedinto a maximum of 64 segments according to 3GPP specifications. Therefore, the maximumwarning notification size equals the warning notification fragment size x 64.

Table 3-1 CMAS warning notification fragment size and maximum warning notification sizeunder common downlink cell bandwidths

Downlink CellBandwidth (MHz)

Warning NotificationFragment Size (Byte)

Maximum WarningNotification Size (Byte)

5 51 3264

eRANCMAS Feature Parameter Description 3 Technical Description


8

Downlink CellBandwidth (MHz)

Warning NotificationFragment Size (Byte)

Maximum WarningNotification Size (Byte)

10 115 7360

15 175 11200

20 207 13248

For details about how to calculate the maximum warning notification fragment size supportedby system resources, contact Huawei technical support.

3.2 CMAS Notification AreaA notification area specifies the scope within which CMAS warning notifications are broadcast.Notification areas can be planned on a cell, emergency area, or tracking area basis. Generally,an emergency area is larger than a cell, and a tracking area is larger than an emergency area, asshown in Figure 3-1.

Figure 3-1 CMAS notification areas

The principles for planning notification areas are as follows:

l If notification areas are planned on a cell or tracking area basis, no addition parametersettings are required.

l If notification areas are planned on an emergency area basis, operators must plan emergencyareas and set the Cell.EmergencyAreaId parameter. This parameter is valid only when theCell.EmergencyAreaIdCfgInd parameter is set to CFG. Emergency areas planned in thecore network must be the same as those configured in the radio access network.

l It is recommended that notification areas be planned on a tracking area basis:

– A single cell is too small for a notification area. A list of cells may meet the coveragearea requirement of a notification area, but it is much more difficult to implement a list



9

of cells as a notification area because the cell list must be determined by the evolvedpacket core (EPC).

– Planning and defining emergency areas requires extra workload.

– A tracking area is the most suitable for a notification area, in terms of the coverage area,maintenance, and project implementation.

3.3 CMAS Warning Notification Broadcast Procedure

3.3.1 Warning Notification Broadcast ProcedureThe CMAS feature can be enabled by setting the ENodeBAlgoSwitch.CmasSwitchparameter. Figure 3-2 shows the procedure for broadcasting a CMAS warning notification afterthis feature is enabled.

Figure 3-2 Warning notification broadcast procedure

If a WNP detects a threat and decides to publish CMAS warning notifications to operators'PLMNs, the procedure is as follows:

1. The WNP sends an Emergency Broadcast Request message to the operators' PLMNs. Therequest contains the warning content, warning notification areas, and warning notificationmode.



10

2. After receiving the Emergency Broadcast Request message from the WNP, the CBCconverts the request into a standard signaling message Write-Replace Warning Requestdefined by 3GPP TS 29.168 and then sends the message to the MME.

3. The MME sends a Write-Replace Warning Response message to the CBC, informing theCBC that a warning notification has started to be forwarded to the eNodeB.

4. The CBC sends an Emergency Broadcast Response message to the WNP, informing theWNP that the warning notification has started to be forwarded to the eNodeB.

5. The MME constructs a new Write-Replace Warning Request message and sends it to theeNodeB within the notification areas indicated by the Warning TA List IE in the originalWrite-Replace Warning Request message.

NOTE

In the Write-Replace Warning Request message delivered by the MME, the Warning Area List IEcontains no more than 4096 notification areas.

6. The eNodeB sends a Write-Replace Warning Response message to the MME, notifyingthe MME of the areas where the warning notification has been successfully broadcast.

NOTE

The implementation of WNPs and the interface between the WNP and CBC are not defined in 3GPPspecifications. Operators can define the implementation.

7. The eNodeB determines whether the cells under the eNodeB belong to the notification areasindicated by the Warning Area List IE in the Write-Replace Warning Request message.

If... Then...

The cells belong to the notification areas The eNodeB determines that whether awarning notification can be broadcast in 64segments:l If it can be broadcast, the eNodeB sends

paging messages to the UEs served byit, notifying the UEs of the warningnotification.

l If it cannot be broadcast, the eNodeBdoes not broadcast the warningnotification and sends a Write-ReplaceWarning Response message that doesnot contain the Broadcast CompletedArea List IE to the MME. Afterreceiving this message, the MMEconsiders that the broadcast failed.

NOTEThe MME uses the CBC to inform the WNPthat the eNodeB cannot broadcast this warningnotification, and then the WNP takes actions asplanned.

The cells do not belong to any notificationarea

The eNodeB does not perform anyoperations indicated in the Write-ReplaceWarning Request message.



11

8. The eNodeB broadcasts the CMAS warning notification contained in SIB12s. If UEsreceive the SIB12s, they alert users by sound, vibration, or other methods.

3.3.2 CMAS Processing in eNodeBsAfter receiving a Write-Replace Warning Request message, an eNodeB starts CMAS processingas follows:

1. The eNodeB determines whether the notification area configured on this eNodeB matchesany notification area in this message.l If the notification area configured on this eNodeB matches a notification area in this

message, the eNodeB performs step 2.l If the notification area configured on this eNodeB does not match any notification area

in this message, the eNodeB responds with a Write-Replace Warning Response messageand does not broadcast the warning notification.For details about the configuration principles of the notification area, see 3.2 CMASNotification Area.

2. The eNodeB determines the CMAS notification content and method based on IEs containedin the Write-Replace Warning Request message as follows:

l If the Write-Replace Warning Request message contains the Data Coding Scheme andWarning Message Contents IEs, the eNodeB determines whether to broadcast the SIB12containing a CMAS warning notification and the number of broadcasts as follows:a. If the value of the Repetition Period IE is greater than 0 and the value of the Number ofBroadcasts Requested IE is greater than 1, the eNodeB broadcasts the CMAS warningnotification at the interval specified by the Repetition Period IE for the number of timesspecified by the Number of Broadcasts Requested IE.b. If the value of the Repetition Period IE is 0 and the value of the Number of BroadcastsRequested IE is 1, the eNodeB broadcasts the CMAS warning notification only once.c. If the value of the Repetition Period IE is 0 and the value of the Number of BroadcastsRequested IE is not 1, the eNodeB does not broadcast the CMAS warning notification.d. If the Write-Replace Warning Request message contains the Concurrent WarningMessage Indicator IE, the value of the Repetition Period IE is greater than 0, and the valueof the Number of Broadcasts Requested IE is 0, the eNodeB consecutively broadcasts theCMAS warning notification until it receives a Stop Warning Request message.

l If a CMAS warning notification needs to be broadcast, the eNodeB sends a paging messageto UEs before broadcasting the warning notification, and then checks the IEs contained inthe Write-Replace Warning Request message.



12

If... Then...

Both of the following conditions are met:l The Message Identifier or Serial

Number IE in the Write-ReplaceWarning Request message differs fromthe Message Identifier or SerialNumber IE in the CMAS warningnotification being broadcast

l The Write-Replace Warning Requestmessage contains the ConcurrentWarning Message Indicator IE

The eNodeB needs to schedule resourcesfor both the CMAS warning notificationrequested by the Write-Replace WarningRequest message and the CMAS warningnotification being broadcast.

Both of the following conditions are met:l The Message Identifier and Serial

Number IEs in the Write-ReplaceWarning Request message are the sameas those in the CMAS warningnotification being broadcast

l The notification area specified in theWrite-Replace Warning Requestmessage is the same as that specified inthe CMAS warning notification beingbroadcast

The eNodeB discards the newly receivedCMAS warning notification withoutinterrupting the ongoing CMAS warningnotification broadcast.

Both of the following conditions are met:l The Message Identifier and Serial

Number IEs in the Write-ReplaceWarning Request message are the sameas those in the CMAS warningnotification being broadcast

l The notification area specified in theWrite-Replace Warning Requestmessage differs from that specified inthe CMAS warning notification beingbroadcast

The eNodeB needs to schedule resourcesfor the CMAS warning notificationrequested by the Write-Replace WarningRequest message in the notification areaspecified by this message, withoutinterrupting the ongoing CMAS warningnotification broadcast.

If a CMAS warning notification needs to be segmented before being broadcast, the SIB12s arebroadcast at intervals specified by the CellSiMap.Sib12Period parameter.

NOTE

The CellSiMap.Sib12Period parameter is irrelevant to the Repetition Period IE in the Write-ReplaceWarning Request message. The CellSiMap.Sib12Period parameter specifies the interval at which theSIB12s are transmitted over the Uu interface. The unit is 10 milliseconds. The Repetition Period IE specifiesthe interval at which the CMAS warning notification is broadcast. The unit is second.

Currently, the eNodeB can process a maximum of 16 received Write-Replace Warning Request messagesper second. If the number of Write-Replace Warning Request messages delivered to the eNodeB exceedsthe processing capability of the eNodeB, the excessive messages may be discarded.



13

The eNodeB supports the processing of concurrent CMAS warning notifications. Thesenotifications are classified into the following types according to the time when the eNodeBreceives the notifications and their broadcast status:

l The latest notification indicates the CMAS warning notification that is newly received bythe eNodeB but has not been broadcast yet.

l A to-be-broadcast notification meets either of the following conditions:

– The notification is not newly received by the eNodeB and has not been broadcast yet.

– The notification has been broadcast but the number of broadcasts does not reach thebroadcast number indicated by the Number of Broadcasts Requested IE.

l A broadcast-postponed notification meets all of the following conditions:

– The notification has been broadcast.

– The number of broadcasts does not reach the broadcast number indicated by the Numberof Broadcasts Requested IE.

– The current system time is later than the sum of the time that the notification is lastlybroadcast and the value of the Repetition Period IE.

The broadcast priority of the latest notification, to-be-broadcast notification, and broadcast-postponed notification ranks in a descending order.

If an eNodeB receives multiple CMAS warning notifications from the MME, the eNodeBbroadcasts these notifications based on their priorities.

NOTE

l If there are multiple to-be-broadcast CMAS warning notifications, the eNodeB preferentiallybroadcasts the notification whose received time is closest to the current time.

l If there are multiple broadcast-postponed CMAS warning notifications, the eNodeB preferentiallybroadcasts the notification with the longest postponed duration.

l An eNodeB can process a maximum of 64 concurrent CMAS warning notifications.

If the CELLPDCCHALGO.PdcchSymNumSwitch parameter is set to ON(On) orECFIADAPTIONON(Enhanced CFI Adaption On), the eNodeB determines whether toincrease the number of PDCCH symbols based on the current system bandwidth and PDCCHsymbols of the cell after receiving CMAS warning notifications from the MME. This ensuresthat the cell has sufficient PDCCH resources to broadcast CMAS warning notifications or pagingmessages accurately and promptly. Considering both actual situations and system performance,the eNodeB adaptively adjusts the number of PDCCH symbols as described in Table 3-2 inCMAS scenarios with different system bandwidths.

Table 3-2 Principle for adaptively adjusting the number of PDCCH symbols in CMAS scenarioswith different system bandwidths

SystemBandwidth

How the Number of PDCCHSymbols Is Adjusted

Remarks

1.4 MHz The number of PDCCH symbols is notadjusted.

The number of PDCCH symbolshas reached the maximum fourand no adjustment can beperformed.



14

SystemBandwidth

How the Number of PDCCHSymbols Is Adjusted

Remarks

3 MHz The number of PDCCH symbols is notadjusted.

The number of PDCCH symbolshas reached the maximum threeand no adjustment can beperformed.

5 MHz If the current number of PDCCH symbolsis less than three when CMAS is triggered,the eNodeB increases the number.

After the CMAS warningnotification broadcast stops, theeNodeB restores the principle foradaptively adjusting the numberof PDCCH symbols.

10 MHz If the current number of PDCCH symbolsis less than two when CMAS is triggered,the eNodeB increases the number.


15 MHz If the current number of PDCCH symbolsis less than two when CMAS is triggered,the eNodeB increases the number.


20 MHz The number of PDCCH symbols is notadjusted.

In this scenario, the number ofPDCCH symbols does not need tobe increased.

NOTE

If the CELLPDCCHALGO.PdcchSymNumSwitch parameter is set to OFF(Off), the adaptive increasein the number of PDCCH symbols cannot be triggered by CMAS.

3.4 CMAS Warning Notification Stop Procedure

3.4.1 Warning Notification Stop ProcedureFigure 3-3 shows the procedure for stopping CMAS warning notification broadcast.



15

Figure 3-3 Warning notification stop procedure

If the WNP detects that no threat is present and decides to stop CMAS warning notificationsbeing broadcast to the public, the procedure is as follows:

1. The WNP sends a Stop Emergency Broadcast Request message to the operators' PLMNs.The request contains the warning content and warning notification areas.

2. After receiving the Stop Emergency Broadcast Request message from the WNP, the CBCconverts the request into a standard signaling message Stop Warning Request and thensends the message to the MME. The Stop Warning Request message indicates the MessageIdentifier and Serial Number IEs of the CMAS warning notification that does not need tobe broadcast and the areas where the CMAS warning notification does not need to bebroadcast.

3. The MME sends a Stop Warning Response message to the CBC, informing the CBC thatthe Stop Warning Request message has been forwarded to the eNodeB.

4. The CBC sends a Stop Emergency Broadcast Response message to the WNP, informingthe WNP that the CMAS notification stop procedure has been started.

5. The MME sends a Kill Request message to the eNodeB within the notification areasindicated by the Warning TA List IE in the Stop Warning Request message.

6. The eNodeB determines whether the cells under the eNodeB belong to the notification areasindicated by the Warning Area List IE in the Kill Request message.



16

If... Then...

Both of the following conditions are met:l The cells belong to the notification

areasl The Message Identifier and Serial

Number IEs contained in the KillRequest message are the same as thosein a CMAS warning notification beingbroadcast

The eNodeB stops broadcasting thewarning notification, stops sending pagingmessages for the warning notification, anddiscards the warning notification.

The cells do not belong to any notificationarea

The eNodeB does not perform anyoperation indicated in the Kill Requestmessage.

The Kill Request message does not specifyany notification area

The eNodeB stops broadcasting thewarning notification and sending pagingmessages for the warning notification in allcells, and discards the warningnotification.

7. The eNodeB sends a Kill Response message to the MME, notifying the MME of the areas

where the warning notification broadcast has been stopped.

NOTE

The implementation of WNPs and the interface between the WNP and CBC are not defined in 3GPPspecifications. Operators can define the implementation.

3.4.2 CMAS Processing in eNodeBsAfter receiving a Kill Request message, an eNodeB starts CMAS processing as follows:

1. The eNodeB determines whether the notification area configured on this eNodeB matchesany notification area in this message.l If the notification area configured on this eNodeB matches a notification area in this

message, the eNodeB performs step 2.l If the notification area configured on this eNodeB does not match any notification area

in this message, the eNodeB responds with a Kill Response message and continues tobroadcast the warning notification.

2. The eNodeB determines the broadcast stop method based on IEs contained in the KillRequest message.



17

If... Then...

Both of the following conditions are met:l The Kill Request message contains the

Warning Area List IEl The Message Identifier and Serial

Number IEs contained in the KillRequest message are the same as thosein a CMAS warning notification beingbroadcast

The eNodeB stops broadcasting thewarning notification, stops sending pagingmessages for it, and discards it.

The Kill Request message does not containthe Warning Area List IE

The eNodeB stops broadcasting thewarning notification with the sameMessage Identifier and Serial Number IEsin the Kill Request message, stops sendingpaging messages for the warningnotification, and discards the warningnotification in all the cells under theeNodeB.



18

4 Related Features

Prerequisite FeaturesThe CMAS feature depends on the following features:

l LBFD-001007 3GPP R9 Specificationl LBFD-002009 Broadcast of system information

Mutually Exclusive FeaturesNone

Impacted FeaturesLBFD-002003 Physical Channel Management

In CMAS scenarios, the number of PDCCH symbols is adaptively adjusted if the systembandwidth is 5, 10, or 15 MHz and the PDCCH symbol number adaptation adjustment is enabled.For details about how the number is adjusted, see 3.3.2 CMAS Processing in eNodeBs.

eRANCMAS Feature Parameter Description 4 Related Features


19

5 Network Impact

System CapacityNo impact.

Network PerformanceIf the system bandwidth is 5, 10, or 15 MHz and PDCCH symbol number adaptation adjustmentis enabled for a cell, the number of PDCCH symbols may be increased in the cell after CMASis enabled for this cell. In this case, the downlink throughput of the cell may decrease up to 9%.

The preceding impact occurs only during the broadcast of CMAS warning notifications. Afterthe notifications are broadcast, the threshold for enabling the PDCCH symbol number adaptationadjustment restores to the value before the notifications are broadcast.

eRANCMAS Feature Parameter Description 5 Network Impact


20

6 Engineering Guidelines

6.1 When to Use CMASThe operator is advised to activate CMAS when the government or other official organizationsneed to broadcast warning notifications about emergencies to the public through PLMNs.

6.2 Required Informationl Collect information about whether the MME, CBC, and UE support CMAS.

l Collect information to ensure that the MME must comply with 3GPP Release 9 or later forLTE and the MME release of the S1 interface of the eNodeB must be consistent with theprotocol version of the peer EPC.

NOTE

CMAS is introduced based on 3GPP Release 9 for LTE and therefore the involved NEs must complywith 3GPP Release 9 or later for LTE to support CMAS.

l Collect information to ensure that the same notification areas are defined in WNPs andPLMNs.

– If notification areas are planned on a cell or tracking area basis, no notification areainformation needs to be collected.

– If notification areas are planned on an emergency area basis, collect information aboutnotification areas defined in WNPs to configure emergency areas. For example, if aWNP defines city A as a notification area, configure emergency area IDs for each cellin city A.

6.3 Planning

6.3.1 RF PlanningN/A

eRANCMAS Feature Parameter Description 6 Engineering Guidelines


21

6.3.2 Network PlanningN/A

6.3.3 Hardware PlanningThe MME, CBC, and UE must support CMAS. CMAS has no requirements for other eRANhardware.

6.4 Deployment

6.4.1 ProcessThe deployment process is as follows:

1. Install eNodeBs and core network equipment.2. Initially configure eNodeBs and core network equipment.3. (Optional) Configure emergency area IDs for cells. Perform this step only when notification

areas are planned on an emergency area basis.4. Turn on the CMAS switch.

6.4.2 Requirements

Operating Environment

Before deploying CMAS, ensure that the MME, CBC, and UE support CMAS. CMAS has nospecial requirements for hardware installation and the default installation is applicable.

CMAS is a standard feature that can be used on Huawei or other vendors' core networkequipment.

Transmission Topology

Before deploying CMAS, determine the notification areas and ensure that the same notificationareas are defined in WNPs and PLMNs.

License

The operator has purchased and activated the license for the feature listed in Table 6-1. Fordetails about how to activate a license, see License Management Feature ParameterDescription.

Table 6-1 License information for CMAS

Feature ID Feature Name LicenseControl Item

NE Sales Unit

LOFD-001092 CMAS Support CMAS Support(per cell)

eNodeB per cell



22

6.4.3 Data PreparationTable 6-2 describes the parameters that must be set in Cell and EnodeBAlgoSwitch MOs toconfigure emergency area IDs for cells and turn on the CMAS switch.

Table 6-2 CMAS parameter description

Parameter Name Parameter ID Source Setting Notes

Local cell ID Cell.LocalCellId Network plan(negotiation notrequired)

This parameterspecifies the localidentity of a cell. Ituniquely identifies acell within aneNodeB.

Emergency Area Idindicator

Cell.EmergencyAr-eaIdCfgInd

Network plan(negotiationrequired)

This parameterspecifies whether toset an emergencyarea ID. Theparameter settingmust be consistentwith that planned inthe core network.

Emergency Area ID Cell.EmergencyAreaId

Network plan(negotiationrequired)

This parameterspecifies theemergency area ID.This parameter isoptional, dependingon the setting ofCell.EmergencyAr-eaIdCfgInd. Theparameter settingmust be consistentwith that planned inthe core network.

CMAS Switch EnodeBAlgoSwitch.CmasSwitch

Network plan(negotiation notrequired)

This parameterspecifies the CMASswitch, which isturned off by default.

6.4.4 PrecautionsIf the CELLPDCCHALGO.PdcchSymNumSwitch parameter is set to OFF(Off) to disable theadaptation adjustment of the number of PDCCH symbols, set the



23

CELLPDCCHALGO.InitPdcchSymNum parameter by following the setting notes providedin Physical Channel Resource Management Feature Parameter Description.

6.4.5 Activation

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 6-3 in a summary data file, which also containsother data for the new eNodeBs to be deployed. Then, import the summary data file into theConfiguration Management Express (CME) for batch configuration. For detailed instructions,see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.

The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:

l The managed objects (MOs) in Table 6-3 are contained in a scenario-specific summarydata file. In this situation, set the parameters in the MOs, and then verify and save the file.

l Some MOs in Table 6-3 are not contained in a scenario-specific summary data file. In thissituation, customize a summary data file to include the MOs before you can set theparameters.

Table 6-3 Parameters for activation

MO Sheet in theSummary DataFile

Parameter Group Remarks

Cell Cell Local cell ID,Emergency Area Idindicator,Emergency Area ID

Configureemergency area IDsfor cells based on thenetwork plan.

EnodeBAlgoSwitch ENodeBAlgoSwitch CmasSwitch Turn on this switch toactivate CMAS.

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure is as follows:

Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or chooseAdvanced > Customize Summary Data File (U2000 client mode), to customize a summarydata file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk ConfigurationData (U2000 client mode), or choose LTE Application > Export Data > Export Base Station



24

Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CMEinto the customized summary data file.

Step 3 In the summary data file, set the parameters in the MOs listed in Figure 6-1 and close the file.

Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk ConfigurationData (U2000 client mode), or choose LTE Application > Import Data > Import Base StationBulk Configuration Data (CME client mode), to import the summary data file into the CME.

Step 5 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or chooseArea Management > Planned Area > Export Incremental Scripts (CME client mode), toexport and activate the incremental scripts.

----End

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.The procedure is as follows:

Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.

Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.

Figure 6-1 MO search and configuration window

NOTE

l To view descriptions of the parameters in the MO, click in area 4 and press F1.

l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button toshow or hide this area.



25

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.

Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO aredisplayed in area 4.

Step 5 Set the parameters in area 4 or 5.

Step 6 Choose CME > Planned Area > Export Incremental Scripts, or choose Area Management> Planned Area > Export Incremental Scripts, to export and activate the incremental scripts.

----End

Using MML Commands

Step 1 (Optional) Run the MOD CELL command to configure emergency area IDs for cells.

NOTE

Perform this step only when notification areas are planned on an emergency area basis.

Step 2 Run the MOD ENODEBALGOSWITCH command with the CmasSwitch parameter set toON(On).

----End

6.4.6 Activation ObservationTrace messages over the S1 and Uu interfaces on the U2000 client to verify whether CMAS isactivated.

To trace messages over the S1 and Uu interfaces, perform the following steps:

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 included in the notification areas, whichare indicated in the Write-Replace Warning Request message.

If the Write-Replace Warning Request and the Write-Replace Warning Response messages canbe traced, the message exchange over the S1 interfaces is normal.

Figure 6-2 shows S1 messages.

Figure 6-2 S1 messages

Step 3 Trace the Uu messages, including paging messages and system information updates sent fromthe eNodeBs.

Figure 6-3 shows Uu messages.



26

Figure 6-3 Uu messages

Step 4 Double-click RRC_SYS_INFO.

If the SIB12 contains a CMAS warning notification, the message exchange over the Uu interfaceis normal.

----End

In summary, if CMAS messages can be successfully transmitted over the S1 and Uu interfaces,CMAS is activated.

6.4.7 ReconfigurationN/A

6.4.8 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature oneNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure for feature deactivation is similar to that forfeature activation described in Using the CME to Perform Batch Configuration for ExistingeNodeBs. In the procedure, modify the parameter according to Table 6-4.

Table 6-4 Parameter for deactivation

MO Sheet in theSummary DataFile

Parameter Group Setting Notes

EnodeBAlgoSwitch ENodeBAlgoSwitch CmasSwitch Turn off this switchto deactivate CMAS.

Using the CME to Perform Single Configuration

On the CME, set the parameter according to Table 6-4. For detailed instructions, see Using theCME to Perform Single Configuration in 6.4.5 Activation.



27

Using MML CommandsRun the MOD ENODEBALGOSWITCH command with the CmasSwitch parameter set toOFF(Off).

6.5 Performance MonitoringThe performance of CMAS is monitored by verifying messages traced over the S1 and Uuinterfaces. For details, see 6.4.6 Activation Observation.

6.6 Parameter OptimizationN/A

6.7 Troubleshooting

Fault DescriptionWhen CMAS is activated, the eNodeB cannot broadcast CMAS warning notifications.

Fault Handling

Step 1 Determine the maximum warning notification size supported by the system according to thesettings of parameters such as the downlink cell bandwidth, SI window size, CP format, andnumber of logical antennas.

The maximum warning notification size equals the warning notification fragment size x 64. Fordetails, see 3.1 CMAS Warning Notification Type.

Step 2 Check whether the warning notification to be broadcast is larger than the maximum warningnotification size.l If yes, reconfigure the warning notification broadcast policy (by reducing the warning

notification size or broadcasting the warning notification separately) according to themaximum warning notification size supported by the system.

l If no, collect information about the downlink cell bandwidth, SI window size, CP format,and number of logical antennas and then contact Huawei technical support.

----End



28

7 Parameters

Table 7-1 Parameter description

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Cell EmergencyAreaId

ADDCELLMODCELLLSTCELL

LBFD-002029 /TDLBFD-002029LOFD-001092 /TDLOFD-001092LBFD-002009 /TDLBFD-002009

Earthquake andTsunamiWarningSystem(ETWS)CMASSupportBroadcast ofsysteminformation

Meaning: Indicates the ID of the notification area withinwhich a warning notification is broadcast. The areaconsists of one or more cells and can be customized byoperators. For details about this parameter, see 3GPPTS 36.413.GUI Value Range: 0~16777215Unit: NoneActual Value Range: 0~16777215Default Value: 0

eRANCMAS Feature Parameter Description 7 Parameters


29

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Cell EmergencyAreaIdCfgInd

ADDCELLMODCELLLSTCELL

LBFD-002029 /TDLBFD-002029LOFD-001092 /TDLOFD-001092LBFD-002009 /TDLBFD-002009

Earthquake andTsunamiWarningSystem(ETWS)CMASSupportBroadcast ofsysteminformation

Meaning: Indicates whether to set an emergency areaID.GUI Value Range: NOT_CFG(Not configure), CFG(Configure)Unit: NoneActual Value Range: NOT_CFG, CFGDefault Value: NOT_CFG(Not configure)

ENodeBAlgoSwitch

CmasSwitch

MODENODEBALGOSWITCHLSTENODEBALGOSWITCH

LOFD-001092 /TDLOFD-001092

CMASSupport

Meaning: Indicates the switch used to enable or disablethe eNodeB-level commercial mobile alert system(CMAS).GUI Value Range: OFF(Off), ON(On)Unit: NoneActual Value Range: OFF, ONDefault Value: OFF(Off)

CellSiMap

Sib12Period

MODCELLSIMAPLSTCELLSIMAP

LOFD-001092 /TDLOFD-001092LBFD-002009 /TDLBFD-002009

CMASSupportBroadcast ofsysteminformation

Meaning: Indicates the transmission period for systeminformation block type 12 (SIB12). For details, see3GPP TS 36.331.GUI Value Range: RF8(8 radio frames), RF16(16 radioframes), RF32(32 radio frames), RF64(64 radioframes), RF128(128 radio frames), RF256(256 radioframes), RF512(512 radio frames)Unit: NoneActual Value Range: RF8, RF16, RF32, RF64, RF128,RF256, RF512Default Value: RF32(32 radio frames)



30

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellPdcchAlgo

PdcchSymNumSwitch

MODCELLPDCCHALGOLSTCELLPDCCHALGO

LBFD-002003 /TDLBFD-002003

PhysicalChannelManagement

Meaning: Indicates the switch used to enable or disabledynamic adjustment on the number of orthogonalfrequency division multiplexing (OFDM) symbolsoccupied by the physical downlink control channel(PDCCH). If this parameter is set to OFF, the numberof OFDM symbols occupied by the PDCCH is fixed andcannot be dynamically adjusted. If this parameter is setto ON, the number of OFDM symbols occupied by thePDCCH is dynamically adjusted based on the requirednumber of PDCCH control channel elements (CCEs).If this parameter is set to ECFIADAPTIONON, thenumber of OFDM symbols occupied by the PDCCH isdynamically adjusted based on the cell downlinkthroughput, and the adjustment performance is the bestamong the three methods.GUI Value Range: OFF(Off), ON(On),ECFIADAPTIONON(Enhanced CFI Adaption On)Unit: NoneActual Value Range: OFF, ON, ECFIADAPTIONONDefault Value: ON(On)



31

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Cell LocalCellId

ACTCELL

ADDCELL

ADDCELLBAND

BLKCELL

DEACELL

DSPCELL

DSPCELLPHYTOPO

DSPCELLULCOMPCLUSTER

DSPPRIBBPADJUST

LSTCELL

LSTCELLBAND

MODCELL

RMVCELL

RMVCELLBAND

STRCELLRFLOOPBACK

None None Meaning: Indicates the local ID of the cell. It uniquelyidentifies a cell within a BS.GUI Value Range: 0~255Unit: NoneActual Value Range: 0~255Default Value: None



32

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

STRCELLSELFTESTSTRPRIBBPADJUSTUBLCELLDSPPRIBBPRESINFO

CellPdcchAlgo

InitPdcchSymNum

MODCELLPDCCHALGOLSTCELLPDCCHALGO

LBFD-002003 /TDLBFD-002003

PhysicalChannelManagement

Meaning: Indicates the number of OFDM symbolsinitially occupied by the PDCCH. If the switch fordynamic adjustment of the number of OFDM symbolsoccupied by the PDCCH is turned off, this parameterindicates the number of OFDM symbols that are alwaysoccupied by the PDCCH. If the switch is turned on andthe bandwidth is 1.4 MHz or 3 MHz, the PDCCHoccupies 4 or 3 OFDM symbols, in this scenario, thisparameter cannot be manually set.. If the switch isturned on and the bandwidth is 5 MHz, 10 MHz, 15MHz, or 20 MHz, the eNodeB adjusts the number ofOFDM symbols in the range of 1, 2, and 3 when thisparameter is set to the default value 1, or in the range of2 and 3 when this parameter is set to 2 or 3.GUI Value Range: 1~4Unit: NoneActual Value Range: 1~4Default Value: 1



33

8 Counters

There are no specific counters associated with this feature.

eRANCMAS Feature Parameter Description 8 Counters


34

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRANCMAS Feature Parameter Description 9 Glossary


35

10 Reference Documents

1. 3GPP TS 22.268, "Public Warning System (PWS) requirements"2. 3GPP TS 23.041, "Technical realization of Cell Broadcast Service (CBS)"3. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"4. 3GPP TS 36.331, "Radio Resource Control (RRC); Protocol specification"5. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved

Universal Terrestrial Radio Access Network (E-UTRAN) access"6. 3GPP TS 29.168, "Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage

3"

eRANCMAS Feature Parameter Description 10 Reference Documents


36