ATIS 0700010-2018 Enhanced Wireless Emergency Alert (eWEA) via EPS Public Warning System Specification (Version 2).pdf

《ATIS 0700010-2018 Enhanced Wireless Emergency Alert (eWEA) via EPS Public Warning System Specification (Version 2).pdf》由会员分享，可在线阅读，更多相关《ATIS 0700010-2018 Enhanced Wireless Emergency Alert (eWEA) via EPS Public Warning System Specification (Version 2).pdf（37页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0700010.v002 ATIS Standard on - Enhanced Wireless Emergency Alert (eWEA) via EPS Public Warning System Specification ATIS-0700010.v002 ii Foreword The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers, customers, and manu

2、facturers. The Wireless Technologies and Systems Committee (WTSC) develops and recommends standards and technical reports related to wireless and/or mobile services and systems, including service descriptions and wireless technologies. WTSC develops and recommends positions on related subjects under

3、 consideration in other North American, regional, and international standards bodies. The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation r

4、epresents a goal currently identifiable as having distinct compatibility or performance advantages. The word may denotes an optional capability that could augment the standard. The standard is fully functional without the incorporation of this optional capability. Suggestions for improvement of this

5、 document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, WTSC 1200 G Street NW, Suite 500, Washington, DC 20005. At the time of consensus on this document, WTSC, which was responsible for its development, had the following leadership: D. Zelmer, WTSC Chai

6、r (AT April 9, 2008.2Ref 3 FCC 08-164, Federal Communications Commission Second Report and Order and Further Notice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System; July 8, 2008.2 Ref 4 FCC 08-184, Federal Communications Commission Third Report and Order and Further Notice

7、 of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System; August 7, 2008.2 Ref 5 FCC 08-166, Federal Communications Commission Order on Reconsideration and Erratum In the Matter of The Commercial Mobile Alert System; July 15,2008.2Ref 6 INCITS 31-2009R2014, Codes for the Identific

8、ation of Counties and Equivalent Areas of the United States, Puerto Rico, and the Insular Areas; International Committee for Information Technology Standards (INCITS).3Ref 7 ATIS-0700006.v002, eWEA via GSM/UMTS Cell Broadcast Service Specification.4Ref 8 ATIS-0700008.v002, Cell Broadcast Entity (CBE

9、) to Cell Broadcast Center (CBC) Interface Specification.4Ref 9 ATIS-0700036, Enhanced Wireless Emergency Alert (eWEA) Mobile Device Behavior (MDB) Specification (a revised version of J-STD-100).5Ref 10 ATIS-0700037, Enhanced Wireless Emergency Alert (eWEA) Federal Alert Gateway to CMSP Gateway Inte

10、rface Specification (a revised version of J-STD-101).5Ref 11 FCC 16-127, Federal Communications Commission Report and Order and Further Notice of Proposed Rulemaking In the Matter of Wireless Emergency Alerts Amendments to Part 11 of the Commissions Rules Regarding the Emergency Alert System; Septem

11、ber 29, 2016.2Ref 12 3GPP TS 29.168, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3.5Ref 13 3GPP TS 36.413, 3rd Generation Partnership Project; Technical Specification Group Radio Ac

12、cess Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP).6Ref 14 3GPP TS 36.331, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC);

13、 Protocol specification.6Ref 15 3GPP TS 23.041, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Technical realization of Cell Broadcast Service (CBS).6Ref 16 3GPP TS 23.038, 3rd Generation Partnership Project; Technical Specification Group Core Network a

14、nd Terminals; Alphabets and language-specific information.61This document is available from the U.S. Government Printing Office . 2This document is available from the Federal Communications Commission. 3This document is available from the International Committee for Information Technology Standards

15、(INCITS) at 4This document is currently awaiting publication by the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. . 5This document is available from the 3rd Generation Partnership Project (3GPP) . ATIS-0700010.v002 3 Ref 17 ISO/IEC 10

16、646:2017, Information technology - Universal Coded Character Set (UCS).6Ref 18 3GPP TS 22.268, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Public Warning System (PWS) Requirements.6Ref 19 ATIS-0700035, Enhanced Wireless Emergency Alert (eWEA) Servic

17、e Description.4Ref 20 ATIS-0700025.v002, Enhanced Wireless Emergency Alert (eWEA) International Roaming Specification.4Ref 21 IETF RFC 3986, Uniform Resource Identifier (URI).73 Definitions, Acronyms, the boroughs and census areas of Alaska; the District of Columbia; the independent cities of Maryla

18、nd, Missouri, Nevada, and Virginia; that part of Yellowstone National Park in Montana; and various entities in the possessions and associated areas. Per the International Committee for Information Technology Standards (INCITS) 31-2009 standard Ref 6, the Federal Information Processing Standards (FIP

19、S) codes for county and county equivalents are maintained by the American National Standards Institute (ANSI) and are publicly available at . As of 30 June 2017, there were 3,235 identified county and county equivalents. 3.1.6 Enhanced Wireless Emergency Alert (eWEA): A continued provision of effect

20、ive WEA Alert Messages while leveraging advancements in technology to improve WEAs capabilities as defined in the September 29th, 2016 FCC Report and Order on WEA Enhancements, FCC 16-127 Ref 11. 3.1.7 Participating Commercial Mobile Service Provider: A Participating Commercial Mobile Service Provid

21、er (or a Participating CMS Provider) is a Commercial Mobile Service Provider that has voluntarily elected to transmit Alert Messages. 3.1.8 State/Local WEA Test Message. End-to-end system test message initiated by state/local emergency managers and terminating with members of the public who opt in t

22、o receiving them. 6This document is available from the International Organization for Standardization (ISO) . 7This document is available from the Internet Engineering Task Force (IETF). ATIS-0700010.v002 4 3.2 Acronyms clause 4.2.4.) Geographic targeting (geo-targeting): Participating CMS Providers

23、 are required to target alerts at the county-level as recommended by the CMSAAC (amended by FCC 16-127; clause 4.2.4). Accessibility for people with disabilities and the elderly: Participating CMS Providers must include an audio attention signal and vibration cadence on CMAS-capable handsets. Multi-

24、language Alerting: Participating CMS Providers will not be required at this time to transmit alerts in languages other than English (amended by FCC 16-127; clause 4.2.4). Availability of CMAS alerts while roaming: Subscribers receiving services pursuant to a roaming agreement will receive alert mess

25、ages on the roamed-upon network if the operator of the roamed-upon network is a Participating CMS provider and the subscribers mobile device is configured for and technically capable of receiving alert messages from the roamed upon network. Preemption of calls in progress: CMAS alerts may not preemp

26、t a voice or data session in progress. Initial implementation: Participating CMS Providers must comply with these rules no later than 10 months from the date the FCC announces the selection of a Federal Government entity to perform the Alert Aggregator and Federal Alert Gateway functions required to

27、 implement the CMAS. The FCC First Report and Order, FCC 08-99 Ref 2 specifies rules governing those sections of the eWEA architecture that are within the control of electing CMS providers. These include the CMS Provider Gateway, CMS provider infrastructure, and CMS provider handsets. The rules requ

28、ire each individual CMS Provider Gateway to be able to receive alerts from the Federal Alert Gateway over a secure interface (i.e., Reference Point “C” Interface). NOTE: On July 14, 2008, the FCC issued an Order on Reconsideration and Erratum Ref 5. 4.2.2 FCC Second Report and Order The FCC released

29、 the Second Report and Order for the CMAS, FCC 08-164, on July 8, 2008, FCC 08-164 Ref 3. In the Second Report and Order, the FCC developed rules to be in compliance with section 602(c) of the WARN Act, which require non-commercial educational (NCE) and public broadcast television station licensees

30、and permittees “to install necessary equipment and technologies on, or as part of, any broadcast television digital signal 23WARN Act 602(e)(1)(B) ATIS-0700010.v002 7 transmitter to enable the distribution of geographically targeted alerts by commercial mobile service providers that have elected to

31、transmit emergency alerts. . .” Requirements and a further description of the NCE and public broadcast television station distribution of eWEA alerts is provided in clause 4.2.3 of this specification. The Second Report and Order also defines rules to implement section 602(f) of the WARN Act which re

32、quires “technical testing for commercial mobile service providers that elect to transmit emergency alerts and for the devices and equipment used by such providers for transmitting such alerts”. This technical testing is defined by the FCC rules to be a “Required Monthly Test” and “Periodic Interface

33、 Testing”. The Required Monthly Test (RMT) is initiated by the Federal Alert Gateway Administrator and defines rules for the CMSP to schedule the distribution of the RMT to their WEA coverage area over a 24-hour period commencing upon receipt of the RMT at the CMSP Gateway. A CMSP may provide mobile

34、 devices with the capability of receiving RMT messages. The Periodic Interface Testing is a test message between the Federal Alert Gateway and the CMSP Gateway and is intended to ensure the availability and viability of both gateway functions. The Periodic Interface Test is not designed to test the

35、CMSPs infrastructure or the mobile devices. The CMSP Gateway shall send an acknowledgement to the Federal Alert Gateway upon receipt of such an interface test message. 4.2.3 FCC Third Report and Order The FCC released the Third Report and Order for CMAS, FCC 08-164, on August 7, 2008, FCC 08-184 Ref

36、 4. In the Third Report and Order, the FCC adopted rules implementing Section 602(b) of the WARN Act. Specifically, the Third Report and Order adopts: Notification requirements for CMS providers that elect not to participate, or to participate only in part, with respect to new and existing subscribe

37、rs. Procedures by which CMS providers may elect to transmit emergency alerts and to withdraw such elections. A rule governing the provision of alert opt-out capabilities for subscribers. A compliance timeline under which participating CMS providers must begin eWEA deployment. The rule governing the

38、provision of alert opt-out capabilities for subscribers specifies: CMS providers may provide their subscribers with the option to opt out of either or both of the “Child Abduction Emergency/AMBER Alert” and “Imminent Threat Alert” classes of Alert Messages. CMS providers shall provide their subscrib

39、ers with a clear indication of what each option means and provide examples of the types of messages the customer may not receive as a result of opting-out. Requirements and specifications for the subscribers right to opt out as defined in the Third Report and Order may be found in ATIS-0700036 Ref 9

40、. 4.2.4 FCC Report and Order on WEA Enhancements On September 29, 2016, the FCC issued the FCC Report this mapping is described in this Standard. This Standard also illustrates the mapping of the CBEM elements and the CBC message elements. 8.2 Warning Message Delivery Service & eWEA The Warning mess

41、ages delivered over the air interface are specified in 3GPP TS 23.041 Ref 15 and 3GPP TS 36.331 Ref 14. This standard utilizes these messages to broadcast eWEA alert messages. The following sub-clauses provide an overview of the Warning message structures for the EPS. This standard specifies how the

42、 parameters of the Warning Message Delivery WRITE-REPLACE and STOP primitives are populated based upon the CBEM elements. The Warning messages associated with the EPS air interface are described in the relevant 3GPP specifications. The following general requirements apply to Warning Message Delivery

43、: 1. The long 360-character maximum message shall be broadcast on LTE and beyond networks. 2. The short 90-character maximum message shall be broadcast on pre-LTE networks. ATIS-0700010.v002 25 8.3 Overview of eWEA Element Mapping The following table illustrates which CMAC elements are used to deriv

44、e CBEM elements and Warning message elements and are ultimately delivered to the mobile device. Note that only a small portion of the CMAC elements are ultimately delivered to the mobile device. Most CMAC elements are used by the network entities supporting the eWEA and/or Warning Message Delivery s

45、ervice. The clauses that follow describe in detail the element mapping from the CMAC to CBEM and CBEM to Warning messages. Table 8.1: Element Mapping from CMAC to CBEM to Mobile Device CMAC Element Mapped to CBEM? Mapped to Warning Message? Delivered to Mobile Device? CMAC_area_description No No No

46、CMAC_cap_alert_uri No No NoCMAC_cap_identifier No No NoCMAC_cap_sent_date_time No No No CMAC_category No No NoCMAC_certainty Yes (see Note 1) Yes (see Note 1) Yes (see Note 1) CMAC_circle Yes Yes No CMAC_cmas_geocode Yes Yes No CMAC_Digital_Signature No No NoCMAC_expires_date_time Yes (see Note 2) Y

47、es (see Note 2) No CMAC_gnis Yes Yes No CMAC_message_number Yes Yes NoCMAC_message_type Yes No CMAC_note No No NoCMAC_polygon Yes Yes No CMAC_protocol_version No No No CMAC_referenced_message_cap_identifier No No No CMAC_referenced_message_number Yes Yes NoCMAC_response_code No No NoCMAC_response_ty

48、pe No No No CMAC_sender No No NoCMAC_sender_name No No NoCMAC_sending_gateway_id No No No CMAC_sent_date_time No No NoCMAC_severity Yes (see Note 1) Yes (see Note 1) Yes (see Note 1) CMAC_special_handling Yes (see Note 1) Yes (see Note 1) Yes (see Note 1) CMAC_status No No No CMAC_short_text_alert_m

49、essage Yes Yes Yes CMAC_short_text_alert_message_length No Yes (see Note 3) Yes (see Note 3) CMAC_long_text_alert_message Yes Yes Yes CMAC_long_text_alert_message_length Yes Yes (see Note 3) Yes (see Note 3) ATIS-0700010.v002 26 CMAC Element Mapped to CBEM? Mapped to Warning Message? Delivered to Mobile Device? CMAC_text_language Yes Yes (see Note 1, Note 4) Yes (see Note 4) CMAC_urgency Yes (see Note 1) Yes (see Note 1) Yes (see Note 1) NOTE 1: The CMAC_special_handling, CMAC_severity, CMAC_certainty,