IEEE 1512 1-2006 en IEEE Standard for Common Traffic Incident Management Message Sets for Use by Emergency Management Centers《供紧急事务管理中心使用的常见交通事故管理消息集》.pdf

《IEEE 1512 1-2006 en IEEE Standard for Common Traffic Incident Management Message Sets for Use by Emergency Management Centers《供紧急事务管理中心使用的常见交通事故管理消息集》.pdf》由会员分享，可在线阅读，更多相关《IEEE 1512 1-2006 en IEEE Standard for Common Traffic Incident Management Message Sets for Use by Emergency Management Centers《供紧急事务管理中心使用的常见交通事故管理消息集》.pdf（117页珍藏版）》请在麦多课文档分享上搜索。

1、IEEE Std 1512.1-2006(Revision of IEEE Std 1512.1-2003)IEEE Standard for Common TrafficIncident Management Message Setsfor Use by Emergency ManagementCentersI E E E3 Park Avenue New York, NY 10016-5997, USA2 November 2006IEEE Standards Coordinating Committee 32Sponsored by theIEEE Standards Coordinat

2、ing Committee 32 onIntelligent Transportation SystemsIEEE Std 1512.1-2006(Revision ofIEEE Std 1512.1-2003)IEEE Standard for Common Traffic Incident Management Message Sets for Use by Emergency Management CentersSponsorIntelligent Transportation Systems Committeeof theIEEE Vehicular Technology Societ

3、yApproved 31 October 2006IEEE-SA Standards BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2006 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 2 November 2006. Printed in the United Sta

4、tes of America.IEEE and 1512 are registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy portions ofany individual standard for educational classroom use can also be obtained through the Copyright ClearanceCenter.ivCopyright 2006 IEEE. All rights reserved.IntroductionThe In

5、cident Management Working Group was formed from a cross section of ITS (IntelligentTransportation System) and incident management practitioners in 1997 to address the problems andconcerns of dispatching traffic management centers interacting with each other in the resolution of(primarily) roadway se

6、rvices disruptions (and certain other events on the highway)generically referred toas incidents. Advancing the greater coordination of these centers and their cross servicing over variousjurisdictional boundaries is the primary objective of this Working Group.This standard is one of several related

7、standards in this area and deals primarily with the communication ofvital data of a public safety and/or emergency management nature involved in transportation-related events.It is a companion volume to a Base Standard: IEEE Std 1512-2006. Other categories of communication,having to do with transpor

8、tation management, hazardous material, and other cargo are addressed in othercompanion volumes generated by the Working Group. The Base Standard, this volume, and othercompanion volumes together comprise what shall be known as the IEEE 1512 Family of Standards.The Base Standard includes more general

9、 introductory material for the family of standards, including theother companion volumes and the relationship between the family of standards and other ITS standards andthe National ITS Architecture. That material will not be repeated here. Rather, the remainder of this sectionwill present a stateme

10、nt of the problem this companion volume is to address and its goal.Problem statementThis standard provides a framework for exchange of data in message sets for use by centers involved intransportation-related incident management, specific to traffic management communications, in particular,for excha

11、nges of data between a traffic management center (TMC) and other involved agencies.This standard supplements IEEE Std 1512-2006, henceforth called the “Base Standard” for the family ofincident management message sets. The overview, scope, and purpose of IEEE Std 1512-2006 will not berepeated in this

12、 standard.In the course of managing many transportation-related incidents, there is a need for distributing andmanaging the often complex and partial information about the traffic flows, infrastructure, and trafficmanagement assets involved in an incident. Often there are large gaps between the avai

13、lable information andwhat the incident commander and other involved agencies need to know in order to best manage the incidentwith regard to traffic management and infrastructure. In the intelligent transportation systems (ITS) world,those gaps will often be able to be spanned by exchanges of inform

14、ation of five kinds:a) Traffic-related information: collected from those other agencies for collation and analysis to supportthe second exchange.b) Current and predicted traffic conditions: made available to the many agencies that may be involvedin the incident-in particular, route information for r

15、outing traffic and response vehicles.c) The need for cleanup, repair, and replacement of damaged infrastructure: to support responses tocarry out that cleanup, repair, and replacement.d) Plans for traffic management, evacuation management, and infrastructure cleanup, repair, andreplacement.e) Asset

16、management information: to coordinate traffic control assets between agencies.This introduction is not part of IEEE Std 1512.1-2006, IEEE Standard For Common Traffic Incident ManagementMessage Sets for Use by Emergency Management Centers.vCopyright 2006 IEEE. All rights reserved.Managing the operati

17、onal complexities of collecting the data, collating and analyzing it, and thendisseminating the results as necessary is a task for the local implementation. The task for this standard is toprovide the framework for communication among the TMC and other agencies to provide a flexible basis forthe fiv

18、e types of information exchange listed here.That presents us with the basis for stating the goal.Goal of this companion volumeThe goal of this companion volume is to specify message sets to support the exchange of the five types ofinformation just listed. More precisely, it is to specify the message

19、 sets that support that exchange, incombination with the message sets specified in the rest of the IEEE 1512 Family of Standards. As of thiswriting, that IEEE 1512 Family of Standards includes Base Standard: IEEE Std 1512-2006, Standard for Common Incident Management Message Sets forUse by Emergency

20、 Management Centers Companion Volume: IEEE Std 1512.2-2005, Standard for Public Safety Incident ManagementMessage Sets for Use by Emergency Management Centers Companion Volume: IEEE Std 1512.3-2006, Standard for Hazardous Material Incident Manage-ment Message Sets for Use by Emergency Management Cen

21、ters A companion volume dealing with issues of communication and coordination with mobile assetsdeployed in response to such events is now being developed as wellAs part of its support of that exchange, this companion volume will support existing conventions andnomenclature for established practices

22、 in public safety incident management, in particular the NationalIncident Management System (NIMS),aand existing formats for incident action plans. At the same time, themessage sets will not require that the local implementation use NIMS or any particular format for anincident action plan. Although

23、in some local implementations any multi-agency incident is coordinated witha single plan, in other local implementations conventions are oriented around each agency having its ownplan without any single, explicitly integrated plan. Both of those cases are supported by this standard.References to ICS

24、 and UCS in this volume shall be taken to also refer to the NIMS.Companion volumesThis document provides information on additional messages, data frames, and data elements beyond thoseappearing in the Base Standard (IEEE Std 1512-2006) and the companion volumes listed above. In order tomake full use

25、 of this information the Base Standard, companion volumes and other references to ITS andindustry standards may also need to be employed. That is particularly true in the area of message set re-usewhere the contents of various elements have been taken from well established practices, both within and

26、outside that of the ITS and the public safety industries.The standard and use with data registriesThe standard was developed in conjunction with entries designed to be made into a data registry. Thefollowing information may be useful to persons wishing to track the data structures described in thiss

27、tandard with those entries or in other similar registries.aU.S. Department of Homeland Security, www.dhs.gov, March 1, 2004. As of this writing, exact URL: www.dhs.gov/interweb/assetl-ibrary/NIMS-90-web.pdf.viCopyright 2006 IEEE. All rights reserved.In each of the data structures found in Clause 5 t

28、hrough Clause 9 of this standard, the following meta datafields are used and are equivalent to the named fields in a data registry. The mapping between these fields isas follows. The specific clause numbering and name of an entry is also the DESCRIPTIVE NAME of thatentry in the registry (the part th

29、at follows after the “:” is the name used). The one or more paragraphs thatthen follow, headed “Use,” form the DESCRIPTION entry. The final one or more paragraphs, headed“Remarks,” form the REMARKS entry. The section headed “Used by,” contains linkages to other datastructures that in turn refer to t

30、his one. In a data registry, the fields RELATED DATA CONCEPT andRELATIONSHIP TYPE may be used to convey this information, along with other relationships. The sectionheaded by “ASN.1 Representation,” contains all ASN.1 defining code. In a data registry, this information isbroken up among the fields:

31、ASN.1 NAME, DATA TYPE, VALID VALUE RULE, and BODY. TheASN.1 NAME contains the formal ASN.1 Type Definition name of the object. The DATA TYPE containsthe base type from which it is defined. The VALID VALUE RULE, or the BODY, then contains the variousconstraints, declared constants, enumerations value

32、s, and comments of the rest of the definition. In the caseof data element entries, this information is found in the VALID VALUE RULE, whereas in the case of dataframes and messages, this information is placed into the BODY field. Other fields used in a data registry (such as UNITS or FORMULA) are, t

33、ypically, not provided with contentfrom this standard, or they are self-evident and constant in nature. The SOURCE field is an example of this,and its value for all entries from this standard is IEEE 1512.1-2006.Notice to usersErrataErrata, if any, for this and all other standards can be accessed at

34、 the following URL: http:/standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL forerrata periodically.InterpretationsCurrent interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/index.html.PatentsAttention is

35、called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for

36、 identifyingpatents or patent applications for which a license may be required to implement an IEEE standard or forconducting inquiries into the legal validity or scope of those patents that are brought to its attention.viiCopyright 2006 IEEE. All rights reserved.ParticipantsAt the time this standar

37、d was completed, the Incident Management Working Group for IntelligentTransportation Systems had the following membership and officers: Ann R. Lorscheider, ChairGerald W. Althauser, Vice ChairMichael Ritchie, Hazmat Sub-ChairWayne Gisler, SecretaryThe following members of the individual balloting co

38、mmittee voted on this standard. Balloters may havevoted for approval, disapproval, or abstention. The Working Group wishes to acknowledge the assistance of SubCarrier Systems Corp (SCSC) and theirITSware tool suite in the preparation of the document. This standard was prepared using the ITSware Mini

39、-Edit automated tools to create and manage the text and the ASN.1 and XML productions found in thestandard, and to ensure synchronization between these entries and those of the data registry and otherstandards. The Working Group also wishes to acknowledge the assistance of Bancroft Scott and Paul Th

40、orpeof OSS Nokalva, Inc. in providing the use of their ASN.1 tool suite compiler. The ASN.1 syntax appearingin this standard was validated using that tool suite compiler.bbThis information is given for the convenience of users of this standard and does not constitute an endorsement by the IEEE of th

41、ese products. Equivalent products may be used if they can be shown to lead to the same results.George AkeKurt AufschneiderRobert M. BarrettCharles R. BergerRick GlasscoPatrick ChanChester H. Chandler IIIJames CheeksBruce W. ChurchillDavid CopeJohn CorbinRobert B. Franklin Jr.Michael GranadosDavid He

42、lmanKyle HortinRon IceManny InsignaresValerie KalhammerDavid KelleyDavid KingeryThomas M. KuriharaEva Lerner-LamJohn LathropRoger MaddenChuck ManuelEd MarkHarlin McEwenTom MerkleJames A. MonaSriram NatarajanMichael OgdenRobert RauschAnita C. RickettsRich RobertsDoug RoremSharon SandersAndrew M. Scho

43、kaSheldon G. StricklandPaul ThorpeThomas J. TimchoKen VaughnSteven VerbilApril WalkerGerald W. AlthauserLee R. ArmstrongKurt AufschneiderAli Al AwaziDennis R. BrundageDanila ChernetsovKeith ChowBruce W. ChurchillTommy P. CooperThomas J. DineenMarc EmmelmannTip FranklinIgnacio Marin GarciaWayne Gisle

44、rRandall C. GrovesLarry GruginskiGloria G. GwynneWerner HoelzlDennis HorwitzPiotr KarockiJeremy A. LandtAnn R. LorscheiderG. L. LuriCharles ManuelEdward MarkThomas J. MerkleGary L. MichelJames MonaMichael S. NewmanRichard H. NoensDonald M. ParkerMichael RitchieRobert A. RobinsonRandall M. SafierBart

45、ien SayogoLuca SpotornoGerald J. StueveDouglas TaylorThomas A. TulliaScott A. ValcourtOren YurenviiiCopyright 2006 IEEE. All rights reserved.The IEEE 1512 Family of Standards is dedicated to the memory of those who lost their lives responding to the tragic events of September 11, 2001. The Working G

46、roup honors the men and women who continue to maintain vigilance in protecting freedom and security. It is our hope and expectation that these standards will enhance multijurisdictional communications.When the IEEE-SA Standards Board approved this standard on 31 October 2006, it had the followingmem

47、bership:Steve M. Mills, ChairRichard H. Hulett, Vice ChairDon Wright, Past ChairJudith Gorman, Secretary*Member Emeritus 2001 The Record, (Bergen County, NJ), Thomas E. Franklin, Staff Photographer. (www.groundzerospirit.org) Mark D. BowmanDennis B. BrophyJoseph BruderRichard CoxBob DavisJulian Fors

48、ter*Joanna N. GueninMark S. HalpinRaymond HapemanWilliam B. HopfLowell G. JohnsonHerman KochJoseph L. Koepfinger*David J. LawDaleep C. MohlaPaul NikolichT. W. OlsenGlenn ParsonsRonald C. PetersenGary S. RobinsonFrank StoneMalcolm V. ThadenRichard L. TownsendJoe D. WatsonHoward L. WolfmanixCopyright

49、2006 IEEE. All rights reserved.Also included are the following nonvoting IEEE-SA Standards Board liaisons:Satish K. Aggarwal, NRC RepresentativeRichard DeBlasio, DOE RepresentativeAlan H. Cookson, NIST RepresentativeDon MessinaIEEE Standards Project EditorMatthew CegliaIEEE Standards Program Manager, Technical Program DevelopmentPatricia A. GerdonProgram Administration Managerx Copyright 2006 IEEE. All rights reserved. Contents 1. Overview .1 1.1 Scope .2 1.2 Purpose 22. Normative references.2 3. Definitions, acronyms, and abbreviations .3 3.1 Definitions.3 3.2 Acr