1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0700012.v002 ATIS Implementation Guidelines for CMAS Supplemental Information Retrieval Revision 2As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the
2、top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M, cyber securit
3、y, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, open source solutions, and interoperabil
4、ity testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a member of and major U.S. contributor to the Inte
5、rnational Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, conse
6、nsus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a sim
7、ple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether
8、he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American Natio
9、nal Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title pag
10、e of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards
11、 may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer October, 2009 including J-STD-101.a, Supplement A to J-STD-101, Joint ATIS/TIA CMAS Alert Gateway to CMSP Gateway Interface Specification, August 2011 and including
12、 J-STD-101.b, Supplement B to J-STD-101, Joint ATIS/TIA CMAS Alert Gateway to CMSP Gateway Interface Specification, December 2012.1Ref 2 FCC 08-99, Federal Communications Commission First Report and Order In the Matter of The Commercial Mobile Alert System; April 9, 2008.2Ref 3 WARN Act, Security an
13、d Accountability For Every Port Act of 2006 (SAFE Port Act), Pub.L. 109-347, Title VI-Commercial Mobile Service Alerts (WARN Act).31This document is available from the Alliance for Telecommunications Industry Solutions (ATIS) . 2This document is available from the Federal Communications Commission.
14、. ATIS-0700012.v002 2 3 Definitions, Acronyms, & Abbreviations 3.1 Definitions For a list of common communications terms and definitions, please visit the ATIS Telecom Glossary, which is located at . 3.2 Acronyms & Abbreviations ATIS Alliance for Telecommunications Industry Solutions CAP Common Aler
15、ting Protocol CMAC Commercial Mobile Alert for C Interface CMAM Commercial Mobile Alert Message CMAS Commercial Mobile Alert System CMSP Commercial Mobile Service Provider FCC Federal Communications Commission HTTP Hypertext Transfer Protocol TIA Telecommunications Industry Association URI Uniform R
16、esource Identifier URL Universal Resource Locator WARN Warning, Alert, & Response Network XML eXtensible Markup Language 4 CMAS Supplemental Information Retrieval Process When a CMAS Alert, Update, or Cancel message is generated by the Federal Alert Gateway, the CMAC message that is delivered to the
17、 CMSP Gateway across the Reference Point “C” interface contains the Uniform Resource Identifier (URI) for the location of the original CAP message in the CMAC_cap_alert_uri element of the CMAC_Alert_Attributes segment Ref 1. The CMSP Gateway may retrieve the original CAP message (Alert, Update, or C
18、ancel) that triggered a particular CMAC message (Alert, Update, or Cancel). CAP message retrieval is not performed using the CMAC protocol. The CMSP Gateway will use the HTTP GET method with the CMAC_cap_alert_uri provided in the CMAC message to retrieve the CAP message. The HTTP GET method will con
19、tain a Host request_header, whose value is the host part of the CMAC_cap_alert_uri. The HTTP GET method may also contain Connection and If_Unmodified_Since request headers. An example of the CMAC_cap_alert_uri is , where CMAM1056 is the identifier for the associated CMAC message. The retrieval of CM
20、AS Supplemental Information is an optional CMSP Gateway capability using the CAP retrieval process, where the URI is provided in the element. An example of the URI provided in CMAC_note for CMAS Supplemental Information/Spanish is as follows: The CMAC_message_number element present in the CMAS Suppl
21、emental Information retrieved from the Federal Alert Gateway shall be used within the CMSP Gateway to validate that the retrieved CMAS Supplemental Information in fact corresponds to the associated CMAC (CMAC_Alert or CMAC_Update) message received from the Federal Alert Gateway. If the CMAC_message_
22、number present in the retrieved CMAS Supplemental Information does not match CMAC_message_number received in the CMAC message, then the CMAC message 3This document is available from the U.S. Government Printing Office ATIS-0700012.v002 3 shall still be processed as normal message (CMAC_Alert or CMAC
23、_Update) and the handling of CMAS Supplemental Information retrieval shall be continued according to the CMSP policies. 4.1 CMAS Supplemental Information Retrieval Requirements The following are the requirements for CMAS supplemental information retrieval, if CMAS supplemental information is availab
24、le: 1. Within the Unites States and it territories, each CMAS Alert or CMAS Update message may have alert text in Spanish language in addition to the alert text in English language. When such a Spanish language alert text is associated with a CMAS Alert or CMAS Update message, for each CMAC_Alert or
25、 CMAC_Update message generated by the Federal Alert Gateway, the Federal Alert Gateway shall provide a corresponding alert text in Spanish language that will not exceed 150 characters. This presence of Spanish version of the CMAS alert text shall available via an URI provided within a CMAC_note entr
26、y to the English version CMAC_Alert or CMAC_Update message. The CMAC_note shall start with the word “SPANISH” to indicate the presence of Spanish language text and an URI address which the CMSP Gateway has to supply to the Federal Alert Gateway to retrieve the Spanish language text: i.e., SPANISH .
27、NOTE: Alert messages in Spanish may be transmitted without supporting accented characters (including the tilde). NOTE: In most cases the alert text in Spanish language takes more text characters than the equivalent alert text in English language. See Annex A for some examples. 2. If there is no asso
28、ciated Spanish version of the CMAS Alert or CMAS Update, then the corresponding CMAC_note entry shall be absent in the CMAC_Alert or CMAC_Update message generated by the Federal Alert Gateway and the CMSP Gateway shall not treat the lack of Spanish as an error condition. 3. All parameters of the ori
29、ginal Alert or Update message contained in the CMAC_Alert_Info and CMAC_Alert_Area segments including category, event code, priority, severity, urgency, expiration time, and alert area are identical for the alert information transmitted in Spanish and are therefore not provided in the supplemental i
30、nformation. 4. If a CMSP chooses to transmit a CMAS alert message in Spanish language, a Cancel message of the CMAC_Alert or CMAC_Update message shall apply to the Spanish language version of the message as well, and the CMSP Gateway shall cancel the Spanish language version of the message according
31、ly. If a CMAC_Alert message has a CMAC_note indicating the presence of an associated Spanish language text, the CMAC_Update may or may not have CMAC_note. In other words, the CMAS update message may or may not have an associated Spanish language text. This is not a typical case, but it can happen. 4
32、.2 CMAS Supplemental Information Retrieval Concepts As described in clause 4.1, the CMAS Supplemental Information Retrieval method is used by the CMSP Gateway to retrieve the alert text in Spanish language from the Federal Alert Gateway. The Federal Alert Gateway would indicate the presence of an as
33、sociated alert text in Spanish language in the CMAC message that it sends to the CMSP Gateway for the CMAC Alert (or CMAC Update) within the CMAC_note field along with a pointer (in the form of an URI) to the address where the Spanish alert text is stored. If no associated Spanish alert text is pres
34、ent, then the associated CMAC_note would be absent in the CMAC_Alert (or CMAC_Update message). Annex B illustrates this concept in the form of a process flow diagram. 5 CMAS Supplemental Information Retrieval Process Call Flow 5.1 CMAC Alert or Update Message with Supplemental Information Retrieval
35、The following call flow is an example of a CMSP Gateway retrieving CMAS Supplemental Information upon receipt of a CMAC_Alert or CMAC_Update message. This flow is based on the call flows for a CMAS Alert or CMAS Update message described in the Joint ATIS-TIA J-STD-101, CMAS Federal Alert Gateway to
36、CMSP Gateway Interface Specification Ref 1. ATIS-0700012.v002 4 Figure 5.1 CMAS Supplemental Information Retrieval Process Call Flow The CMAC_note is included in the CMAC_Alert or CMAC_Update message (see J-STD-101 Ref 1) at step 5 of the flow. The following is an example of XML code that contains t
37、his CMAC_note: SPANISH http:/10.12.130.148/CMSPInterface/Spanish?cmacmsgnumber=12345678 ATIS-0700012.v002 5 5.2 CMAC Alert or Update Message with No Supplemental Information Retrieved The following call flow is an example of no CMAS Supplemental Information available to the CMSP Gateway upon receipt
38、 of a CMAC_Alert or CMAC_Update message. This will occur when no Spanish language text is available. The steps shown in this call flow are identical to the steps shown in the call flows for a CMAS Alert or CMAS Update message described in the Joint ATIS-TIA J-STD-101, CMAS Federal Alert Gateway to C
39、MSP Gateway Interface Specification Ref 1, and are shown here for completeness only. Figure 5.2 CMAS Supplemental Information Retrieval Process Call Flow No Spanish Available Note that there is no CMAC_note included in the CMAC message and hence, the CMSP Gateway does attempt to retrieve the Supplem
40、ental Information/Spanish from the Federal Alert Gateway even if the CMSP policy supports the CMAS alert broadcasts in Spanish language text. ATIS-0700012.v002 6 6 XML Schemas 6.1 XML Schema for CMAS Supplemental Information The following provides the XML schema for the supplemental information stor
41、age: CMAS Supplemental Information (version 1.0) 6.2 Example to Show to XML Schema for CMAS Supplemental Information/Spanish This sub-clause gives an example of XML schema usage for CMAS Supplemental Information/Spanish retrieval with the Spanish language text being available at the Federal Alert Ga
42、teway. 00001056 Spanish 97 Advertencia de seguridad Publica Esta area es afectada hasta 3:00pm EDT Evacucion inmediata NYPD ATIS-0700012.v002 7 Annex A: Generation of Spanish Language CMAS Messages (informative) Spanish language text is always composed by the alert originator and it should be noted
43、that in most cases the Spanish version requires more characters than the English version. As an example: “Public Safety Warning This area is affected until 3:00pm EDT Evacuate Now NYPD”. In English, this requires 78 characters. The Spanish equivalent is: “Advertencia de seguridad pblica Esta rea es
44、afectada hasta 3:00pm EDT Evacuacin inmediata NYPD”. In Spanish, this requires 97 characters. The following is an example of a longest presumed Spanish language CMAS message: Aviso de las autoridades de la ley Esta rea es afectada hasta 12:00AM PDT Compruebe nedios de noticias para informacin NYPD T
45、his message requires 125 characters. NOTE: The corresponding English message requires 79 characters and is: “Law Enforcement Warning in this area until 12:00AM PDT Monitor Radio or TV NYPD”. ATIS-0700012.v002 8 Annex B: Spanish Language Support Process Flow (informative) This informative Annex descr
46、ibes the process flow involved in the handling of CMAS alert broadcast in Spanish language text. As such this annex focuses on the interaction between the Federal Alert Gateway and the CMSP Gateway. A CAP message arriving at the Federal Alert Gateway always has the alert text in English language and
47、 may optionally have the alert text in Spanish language. The Federal Alert Gateway always includes only the alert text in English in the CMAC message that it sends to the CMSP Gateway. If the CMSP supports the broadcast of CMAS alert in Spanish, then the CMSP Gateway would retrieve the Spanish langu
48、age alert text from the Federal Alert Gateway using the CAP Retrieval mechanism. However, since not all CMAS alerts may have associated Spanish text, the Federal Alert Gateway has the capability to indicate to the CMSP Gateway that the CMAS alert has an associated Spanish language alert text. The Fe
49、deral Alert Gateway and CMSP Gateway operate using the following concept: If the incoming CAP message carries the alert text in Spanish, the Federal Alert Gateway extracts the Spanish text from the CAP message and stores internally at a database. Federal Alert Gateway includes a CMAC_note in the CMAC message sent to the CMSP Gateway. The CMAC_note will have “SPANISH” followed by the address where the Spanish text was stored in the form an URI. The use of “SPANISH” will tell the CMSP Gateway that the CMAS alert has an associated Spanish alert text stored at t
