ITU-T X 1303-2007 Common alerting protocol (CAP 1 1) (Study Group 17)《共同告警协议(CAP 1 1)17号研究组》.pdf

1、 International Telecommunication Union ITU-T X.1303TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2007) SERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY Telecommunication security Common alerting protocol (CAP 1.1) ITU-T Recommendation X.1303 ITU-T X-SERIES RECOMMENDATIONS DATA

2、NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY PUBLIC DATA NETWORKS Services and facilities X.1X.19 Interfaces X.20X.49 Transmission, signalling and switching X.50X.89 Network aspects X.90X.149 Maintenance X.150X.179 Administrative arrangements X.180X.199 OPEN SYSTEMS INTERCONNECTION Model and no

3、tation X.200X.209 Service definitions X.210X.219 Connection-mode protocol specifications X.220X.229 Connectionless-mode protocol specifications X.230X.239 PICS proformas X.240X.259 Protocol Identification X.260X.269 Security Protocols X.270X.279 Layer Managed Objects X.280X.289 Conformance testing X

4、.290X.299 INTERWORKING BETWEEN NETWORKS General X.300X.349 Satellite data transmission systems X.350X.369 IP-based networks X.370X.379 MESSAGE HANDLING SYSTEMS X.400X.499DIRECTORY X.500X.599 OSI NETWORKING AND SYSTEM ASPECTS Networking X.600X.629 Efficiency X.630X.639 Quality of service X.640X.649 N

5、aming, Addressing and Registration X.650X.679 Abstract Syntax Notation One (ASN.1) X.680X.699 OSI MANAGEMENT Systems Management framework and architecture X.700X.709 Management Communication Service and Protocol X.710X.719 Structure of Management Information X.720X.729 Management functions and ODMA

6、functions X.730X.799 SECURITY X.800X.849 OSI APPLICATIONS Commitment, Concurrency and Recovery X.850X.859 Transaction processing X.860X.879 Remote operations X.880X.889 Generic applications of ASN.1 X.890X.899 OPEN DISTRIBUTED PROCESSING X.900X.999 TELECOMMUNICATION SECURITY X.1000 For further detai

7、ls, please refer to the list of ITU-T Recommendations. ITU-T Rec. X.1303 (09/2007) i ITU-T Recommendation X.1303 Common alerting protocol (CAP 1.1) Summary The common alerting protocol (CAP) is a simple but general format for exchanging all-hazard emergency alerts and public warnings over all kinds

8、of networks. CAP allows a consistent warning message to be disseminated simultaneously over many different warning systems, thus increasing warning effectiveness while simplifying the warning task. CAP also facilitates the detection of emerging patterns in local warnings of various kinds, such as mi

9、ght indicate an undetected hazard or hostile act. CAP also provides a template for effective warning messages based on best practices identified in academic research and real-world experience. ITU-T Recommendation X.1303 also provides both an XSD specification and an equivalent ASN.1 specification (

10、that permits a compact binary encoding) and allows the use of ASN.1 as well as XSD tools for the generation and processing of CAP messages. This Recommendation enables existing systems, such as H.323 systems, to more readily encode, transport and decode CAP messages. Source ITU-T Recommendation X.13

11、03 was approved on 13 September 2007 by ITU-T Study Group 17 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. X.1303 (09/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and

12、communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basi

13、s. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolu

14、tion 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration a

15、nd a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are me

16、t. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possib

17、ility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Re

18、commendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest informat

19、ion and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. X.1303 (09/2007) iii CONTENTS Page 1

20、Scope 1 2 References. 2 3 Definitions 3 4 Abbreviations and acronyms 3 5 Conventions 3 6 Design principles and concepts 3 6.1 Design philosophy 3 6.2 Examples of requirements for design. 4 6.3 Examples of use scenarios 4 7 Alert message structure. 6 7.1 Document object model 6 7.2 Data dictionary .

21、6 7.3 Implementation considerations. 17 7.4 XML schema 18 8 Use of ASN.1 to specify and encode the CAP alert message. 21 8.1 General . 21 8.2 Formal mappings and specification 21 Appendix I CAP alert message examples. 27 I.1 Homeland security advisory system alert. 27 I.2 Severe thunderstorm warning

22、. 28 I.3 Earthquake report . 29 I.4 AMBER alert (Including EAS activation) . 30 Bibliography. 31 iv ITU-T Rec. X.1303 (09/2007) Introduction Provides a brief introduction to the common alerting protocol (the current specification is identified as CAP 1.1). Purpose The common alerting protocol (CAP)

23、provides an open, non-proprietary message format for all types of alerts and notifications. It does not address any particular application or telecommunications method. The CAP format is compatible with emerging techniques, such as web services and the ITU-T fast web services, as well as existing fo

24、rmats including the specific area message encoding (SAME) used for the United States National Oceanic and Atmospheric Administration (NOAA) weather radio and the emergency alert system (EAS), while offering enhanced capabilities that include: flexible geographic targeting using latitude/longitude sh

25、apes and other geospatial representations in three dimensions; multilingual and multi-audience messaging; phased and delayed effective times and expirations; enhanced message update and cancellation features; template support for framing complete and effective warning messages; compatible with digit

26、al encryption and signature capability; and facility for digital images and audio. CAP provides reduction of costs and operational complexity by eliminating the need for multiple custom software interfaces to the many warning sources and dissemination systems involved in all-hazard warning. The CAP

27、message format can be converted to and from the “native“ formats of all kinds of sensor and alerting technologies, forming a basis for a technology-independent national and international “warning Internet“. CAP history The National Science and Technology Council report on “Effective Disaster Warning

28、s“ released in November, 2000 recommended that “a standard method should be developed to collect and relay instantaneously and automatically all types of hazard warnings and reports locally, regionally and nationally for input into a wide variety of dissemination systems.“ An international working g

29、roup of more than 130 emergency managers and information technology and telecommunications experts convened in 2001 and adopted the specific recommendations of the National Science and Technology Council (NSTC) report as a point of departure for the design of a common alerting protocol (CAP). Their

30、draft went through several revisions and was tested in demonstrations and field trials in Virginia (supported by the ComCARE Alliance) and in California (in cooperation with the California Office of Emergency Services) during 2002 and 2003. Geographic locations in CAP are defined using b-WGS 84 (Wor

31、ld Geodetic System 1984). CAP does not assign responsibilities for coordinate transformations from and to other Spatial Reference Systems. See clause 5, below, for the format of coordinate pairs within CAP elements. In 2002, the CAP initiative was endorsed by the national non-profit Partnership for

32、Public Warning, which sponsored its contribution in 2003 to the OASIS standards process. In 2004, CAP version 1.0 was adopted as an OASIS Standard. ITU-T Rec. X.1303 (09/2007) v Structure of the CAP Alert Message Each CAP Alert Message consists of an segment, which may contain one or more segments,

33、each of which may include one or more segments. Under most circumstances, CAP messages with a value of “Alert“ should include at least one element. (See the document object model diagram in clause 7.1, below.) The segment provides basic information about the current message: its purpose, its source

34、and its status, as well as a unique identifier for the current message and links to any other related messages. An segment may be used alone for message acknowledgements, cancellations or other system functions, but most segments will include at least one segment. The segment describes an anticipate

35、d or actual event in terms of its urgency (time available to prepare), severity (intensity of impact) and certainty (confidence in the observation or prediction), as well as providing both categorical and textual descriptions of the subject event. It may also provide instructions for an appropriate

36、response by message recipients and various other details (hazard duration, technical parameters, contact information, links to additional information sources, etc.). Multiple segments may be used to describe differing parameters or to provide the information in multiple languages. The segment provid

37、es an optional reference to additional information related to the segment within which it appears, in the form of a digital asset such as an image or audio file. The segment describes a geographic area to which the segment in which it appears applies. Textual and coded descriptions (such as postal c

38、odes) are supported, but the preferred representations use geospatial shapes (polygons and circles) and an altitude or altitude range, expressed in standard latitude/longitude/altitude terms in accordance with a specified geospatial datum. Applications of the CAP Alert Message The primary use of the

39、 CAP Alert Message is to provide a single input to activate all kinds of alerting and public warning systems. This reduces the workload associated with using multiple warning systems while enhancing technical reliability and target-audience effectiveness. It also helps ensure consistency in the info

40、rmation transmitted over multiple delivery systems, another key to warning effectiveness. A secondary application of CAP is to normalize warnings from various sources so they can be aggregated and compared in tabular or graphic form as an aid to situational awareness and pattern detection. Although

41、primarily designed as an interoperability standard for use among warning systems and other emergency information systems, the CAP Alert Message can be delivered directly to alert recipients over various networks, including data broadcasts. Location-aware receiving devices could use the information i

42、n a CAP Alert Message to determine, based on their current location, whether that particular message was relevant to their users. The CAP Alert Message can also be used by sensor systems as a format for reporting significant events to collection and analysis systems and centers. ITU-T Rec. X.1303 (0

43、9/2007) 1 ITU-T Recommendation X.1303 Common alerting protocol (CAP 1.1) 1 Scope This Recommendation defines the common alerting protocol (CAP) version 1.1 which is a simple but general format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks. CAP allows a con

44、sistent warning message to be disseminated simultaneously over many different warning systems, thus increasing warning effectiveness while simplifying the warning task. CAP facilitates the detection of emerging patterns in local warnings of various kinds, such as might indicate an undetected hazard

45、or hostile act. CAP provides a template for effective warning messages based on best practices identified in academic research and real-world experience. The common alerting protocol (CAP) provides an open, non-proprietary digital message format for various types of alerts and notifications. CAP pro

46、vides the following capabilities: flexible geographic targeting using latitude/longitude shapes and other geospatial representations in three dimensions; multilingual and multi-audience messaging; phased and delayed effective times and expirations; enhanced message update and cancellation features;

47、template support for framing complete and effective warning messages; compatible with digital encryption and signature capability; and facility for digital images and audio. CAP provides reduction of costs and operational complexity by eliminating the need for multiple custom software interfaces to

48、the many warning sources and dissemination systems involved in all-hazard warning. The CAP message format can be converted to and from the “native“ formats of all kinds of sensor and alerting technologies, forming a basis for a technology-independent national and international “warning Internet“. Th

49、is Recommendation also provides both an XSD schema and an ASN.1 specification for the common alerting protocol. NOTE The ASN.1 specification defines the same message information content and XML encoding as that defined by the XSD schema, but permits a compact binary encoding and the use of ASN.1 as well as XSD tools for the generation and processing of CAP messages. This Recommendation is technically equivalent to the OASIS Common Alerting Protocol v.1.1 with the Errata approved on 2 October 2007. This Recom