1、 ATIS-0700033 ATIS Standard on - ATIS Supplement C to J-STD-101, Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Specification ATIS-0700033 ii Foreword The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers,
2、customers, and manufacturers. 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 rel
3、ated subjects under 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, t
4、he recommendation represents 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
5、improvement of this 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
6、. Zelmer, WTSC Chair (AT Child Abduction messages require special handling to bypass checks on embedded telephone numbers or URLs. 2.8 Modification to Table 15 CMAC_Digital_Signature Segment Element Definition in Clause 7.3.4 The CMAC_Digital_Signature element of Table 15, CMAC_Digital_Signature Seg
7、ment Element Definition of Clause 7.3.4, CMAC_Digital_Signature Segment Element Definition, is modified as shown below: Table 15: CMAC_Digital_Signature Segment Element Definition CMAC Element Mandatory/ Optional/ Conditional CMAC Definition CMAC_Digital_Signature C XML digital signature elements an
8、d syntax are defined by W3C recommendations Ref 38. CMAC_Digital_Signature is mandatory for the CMSP Federal Alert Gateway to support non-repudiation and will be applied to Alert, Update, Cancel, and RMT messages. CMAC_Digital_Signature may be used by the CMSP Gateway to support non-repudiation. Chi
9、ld of . 2.9 Modifications to Table 27 Elements of Alert Info Segment for RMT Message in Clause 7.5.7 Table 27, Elements of Alert Info Segment for RMT Message of Clause 7.5.7, RMT Message, is modified as shown below: Table 27: Elements of Alert Info Segment for RMT Message CMAC Element Mandatory/ Opt
10、ional/ Conditional Value CMAC_category M Value of “Other”. CMAC_event_code M Value of “RMT”. CMAC_severity M Value of “Severe”. CMAC_urgency M Value of “Expected”. CMAC_certainty M Value of “Likely”. ATIS-0700033 5 CMAC Element Mandatory/ Optional/ Conditional Value CMAC_expires_date_time M Date and
11、 time in UTC the Alert Message expires in XML dateTime format (24 hours after initiation). CMAC_sender_name O Indicates the name or other identification of the RMT initiator at the Federal Alert Gateway. May be used for CMSP Gateway logging purposes only. CMAC_text_language M Value of “English”. CMA
12、C_text_alert_message_length M Length in characters of the text message (74 characters for message specified in CMAC_text_alert_message). CMAC_text_alert_message M Text message per Table 13: CMAC_Alert_Info Segment Element Definition of Clause 7.3.2, CMAC_Alert_Info Segment Element Definition. Value
13、of “This is a test of the Commercial Mobile Alert System. This is only a test. ” 2.10 Modification to Clause 7.6, Transport Protocol The first paragraph of Clause 7.6, Transport Protocol, is modified as shown below: Transmission Control Protocol (TCP) Ref 23 is the transport protocol used to transmi
14、t XML Alert Messages, RMT Messages, and system messages between the Federal Alert Gateway and the CMSP Gateway on the Reference Point “C” interface. 2.11 Modification to Table 31 CAP Value Field Mapping to CMAC_text_alert_message in Annex A The sender entry of Table 31, CAP Value Field Mapping to CM
15、AC_text_alert_message, in Annex A is modified as shown below: Who is sending the alert CAP Field Value Text String sender Identifies the originator of this alert. Guaranteed by assigner to be unique globally; e.g., may be based on an Internet Fully Qualified Domain Name - could also come from the se
16、nders name in the Trust Model. Translated by the Federal Alert Gateway to an acronym or short abbreviation picked by the sender Note NOTE: URLs, phone numbers, and email addresses of the sender are not sent to the mobile device. 2.12 Modifications to Table 32 Reference Point “C” Interface Requiremen
17、ts Traceability Table in Annex C.5 1. The “Clause 5.1.1 item #3” entry of Table 32, Reference Point “C” Interface Requirements Traceability Table, of Annex C.5 is modified as shown below: ATIS-0700033 6 Clause 5.1.1 item #3: The Federal Alert Gateway will only send CMAMs over the Reference Point “C”
18、 interface that meet the classification of alerts in the First Report and Order Ref 9 section 10.330. Specifically, the Federal Alert Gateway will only generate CMAMs for Presidential alerts, Imminent Threat Alerts (where the corresponding CAP message Severity is extreme or severe, Urgency is immedi
19、ate or expected, and Certainty is observed or likely), or a Child Abduction Emergency/AMBER Alert. Alerts not meeting this classification will not be sent over Reference Point “C”. Clause 7.1.1 item #2: JCMAS-C-RQMT-2510 Each Alert message shall contain the mandatory message elements and associated
20、values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 16: Elements of Alert Attributes Segment for Alert Message Table 17: Elements of Alert Info Segment for Alert Message Table 18: Elements of Alert Area Segment for Alert Message Clause 7.7.3.2 i
21、tem #1: JCMAS-C-RQMT-3600 Messages containing information that conflicts with the CMAC protocol shall be logged and discarded. 2. The “Clause 5.1.1 item #4” entry of Table 32, Reference Point “C” Interface Requirements Traceability Table, of Annex C.5 is modified as shown below: Clause 5.1.1 item #4
22、: The Federal Alert Gateway will generate a CMAM text message to be provided over the Reference Point “C” interface that does not exceed 90 English characters of alphanumeric text (see the First Report and Order Ref 9, section 10.430). Clause 7.1.1 item #2: JCMAS-C-RQMT-2510 Each Alert message shall
23、 contain the mandatory message elements and associated values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 16: Elements of Alert Attributes Segment for Alert Message Table 17: Elements of Alert Info Segment for Alert Message Table 18: Elements o
24、f Alert Area Segment for Alert Message Clause 7.7.3.2 item #1: JCMAS-C-RQMT-3600 Messages containing information that conflicts with the CMAC protocol shall be logged and discarded. 3. The “Clause 5.1.1 item #5” entry of Table 32, Reference Point “C” Interface Requirements Traceability Table, of Ann
25、ex C.5 is modified as shown below: ATIS-0700033 7 Clause 5.1.1 item #5: In 47 CFR Section 10.441 of Appendix A Final Rules of the FCC Report and Order on WEA Enhancements Ref 41, all restrictions have been removed for all WEA messages regarding embedded references (e.g., URL or telephone number). Em
26、bedded references are allowed in all WEA messages. The previous 47 CFR Section 10.440 defining the embedded restrictions has been removed in Appendix A Final Rules of the FCC Report and Order on WEA Enhancements Ref 41. NOTE: Even though a WEA alert may contain embedded references, having this infor
27、mation in the broadcast WEA message may increase the likelihood of causing severe network congestion resulting in the inability of subscribers to make calls. The Federal Alert Gateway will ensure that, except for Presidential alert messages, the generated CMAM text message does not contain an embedd
28、ed reference, such as a Uniform Resource Locator (URL) or telephone number in accordance with the First Report and Order Ref 9 section 10.440. Although not explicitly addressed in the First Report and Order Ref 9, the inclusion of a telephone number in child abduction emergency messages should be al
29、lowed. Outside the scope of this Standard. 4. The “Clause 5.1.2 item #7” entry of Table 32, Reference Point “C” Interface Requirements Traceability Table, of Annex C.5 is modified as shown below: Clause 5.1.2 item #7: The CMS Provider Gateway may reject CMAMs received over the Reference Point “C” In
30、terface that do not meet the Alert Message Requirements of the First Report and Order Ref 9 Subpart D. Specifically, CMAMs may be rejected: if the Alert does not meet the classification of Section 10.400 of the First Report and Order Ref 9 o Presidential o Imminent Threat where the CAP Severity is e
31、xtreme or severe, Urgency is immediate or expected, and Certainty is observed or likely o Child Abduction Alert/AMBER Alert if the CMAM text exceeds 90 English characters (section 10.430 of the First Report and Order Ref 9) if the CMAM text contains an embedded reference, such as a Uniform Resource
32、Locator (URL) or a telephone number (Section 10.440 of the First Report and Order Ref 9) except for Presidential alerts or child abduction emergency messages (see clause 5.2 Federal Alert Gateway Requirements) if the CMAM does not contain one or more geocodes required by the CMSP to perform geograph
33、ic targeting (Section 10.450 of the First Report and Order Ref 9) Clause 7.1.1 item #2: JCMAS-C-RQMT-2510 Each Alert message shall contain the mandatory message elements and associated values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 16: Elem
34、ents of Alert Attributes Segment for Alert Message Table 17: Elements of Alert Info Segment for Alert Message Table 18: Elements of Alert Area Segment for Alert Message Clause 7.7.3.2 item #1: JCMAS-C-RQMT-3600 Messages containing information that conflicts with the CMAC protocol shall be logged and
35、 discarded. 5. The “Clause 5.1.4.2 item #7” entry of Table 32, Reference Point “C” Interface Requirements Traceability Table, of Annex C.5 is modified as shown below: ATIS-0700033 8 Clause 5.1.4.2 item #3: Real event codes or alert messages will not be used for this periodic interface testing. Claus
36、e 7.1.1 item #8: JCMAS-C-RQMT-2570 Each RMT message shall contain the mandatory message elements and associated values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 26: Elements of Alert Attributes Segment for RMT Message Table 27: Elements of Al
37、ert Info Segment for RMT Message 6. The “Clause 5.1.4.3 item #1” entry of Table 32, Reference Point “C” Interface Requirements Traceability Table, of Annex C.5 is modified as shown below: Clause 5.1.4.3 item #1: The Federal Alert Gateway will support the capability to initiate an RMT on the Referenc
38、e Point “C” interface using a defined test message. Real event codes or alert messages will not be used for the CMAS RMT message. Clause 7.1.1 item #8: JCMAS-C-RQMT-2570 Each RMT message shall contain the mandatory message elements and associated values provided in the following tables: Table 15: CM
39、AC_Digital_Signature Segment Element Definition Table 26: Elements of Alert Attributes Segment for RMT Message Table 27: Elements of Alert Info Segment for RMT Message 2.13 Modifications to Table 33 Requirements Matrix in Annex C.6 1. The JCMAS-C-RQMT-2510 requirement entry of Table 33, Requirements
40、 Matrix, of Annex C.6 is modified as shown below: 7.1.1 JCMAS-C-RQMT-2510 Each Alert message shall contain the mandatory message elements and associated values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 16: Elements of Alert Attributes Segment
41、 for Alert Message Table 17: Elements of Alert Info Segment for Alert Message Table 18: Elements of Alert Area Segment for Alert Message 2. The JCMAS-C-RQMT-2520 requirement entry of Table 33, Requirements Matrix, of Annex C.6 is modified as shown below: 7.1.1 JCMAS-C-RQMT-2520 Each Update message s
42、hall contain the mandatory message elements and associated values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 19: Elements of Alert Attributes Segment for Update Message Table 20: Elements of Alert Info Segment for Update Message Table 21: Elem
43、ents of Alert Area Segment for Update Message 3. The JCMAS-C-RQMT-2560 requirement entry of Table 33, Requirements Matrix, of Annex C.6 is modified as shown below: 7.1.1 JCMAS-C-RQMT-2560 Each Cancel message shall contain the mandatory message elements and associated values provided in the following
44、 table tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 22: Elements of Alert Attributes Segment for Cancel Message ATIS-0700033 9 4. The JCMAS-C-RQMT-2570 requirement entry of Table 33, Requirements Matrix, of Annex C.6 is modified as shown below: 7.1.1 JCMAS-C-RQMT-2570 Ea
45、ch RMT message shall contain the mandatory message elements and associated values provided in the following tables: Table 15: CMAC_Digital_Signature Segment Element Definition Table 26: Elements of Alert Attributes Segment for RMT Message Table 27: Elements of Alert Info Segment for RMT Message 3 Ad
46、ditions 3.1 Addition of New Preface Clause The following new Preface is added after the Table of Contents and before Clause 1, Introduction: Preface The authority-to-individuals emergency alerting capability to mobile devices was originally called Commercial Mobile Alert System (CMAS) in the first t
47、hree Reports and Orders from the FCC. This standard was originally developed based upon the CMAS terminology and CMAS was operational in April 2012. However, in February 2013, the FCC renamed Commercial Mobile Alert System (CMAS) to Wireless Emergency Alerts (WEA) with associated updates to the appr
48、opriate sections of Part 11 of the 47 CFR. Subsequently, the FCC has issued additional enhancements and rules for this government-to-citizen emergency alerting capability to mobile devices capability and these are identified as modifications to WEA. Consequently, this specification may use both the
49、term CMAS and the term WEA. These terms should be considered as equivalent terms with WEA being the preferred term. 3.2 Addition of New Ref 41 in Clause 2, Normative References An additional reference Ref 41 is added to Clause 2, Normative References, as shown below: Ref 41 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 Commission
