ISO TR 22351-2015 Societal security - Emergency management - Message structure for exchange of information《社会安全 紧急管理 信息交换的消息结构》.pdf

《ISO TR 22351-2015 Societal security - Emergency management - Message structure for exchange of information《社会安全 紧急管理 信息交换的消息结构》.pdf》由会员分享，可在线阅读，更多相关《ISO TR 22351-2015 Societal security - Emergency management - Message structure for exchange of information《社会安全 紧急管理 信息交换的消息结构》.pdf（98页珍藏版）》请在麦多课文档分享上搜索。

1、 ISO 2015 Societal security Emergency management Message structure for exchange of information Scurit socitale Gestion des urgences Message structures pour changer dinformation TECHNICAL REPORT ISO/TR 22351 Reference number ISO/TR 22351:2015(E) First edition 2015-09-01 ISO/TR 22351:2015(E)ii ISO 201

2、5 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2015, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the

3、internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 0

4、9 47 copyrightiso.org www.iso.org ISO/TR 22351:2015(E)Foreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 T erms and definitions . 1 4 The EMSI message . 1 4.1 General . 1 4.2 EMSI content . 3 4.3 EMSI structure . 4 4.4 General rules for the definition of elements 5 4.5 Rules for the l

5、ist of elements . 6 4.6 Implementation of the EMSI . 6 5 The EMSI codes dictionary . 6 5.1 The role of the codes 6 5.2 Rules . 6 5.2.1 Code structure 6 5.2.2 Code elements 6 5.2.3 Examples . 6 Annex A (informative) Example of EMSI messages 8 Annex B (informative) EMSI elements and codes .17 Bibliogr

6、aphy .90 ISO 2015 All rights reserved iii Contents Page ISO/TR 22351:2015(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO

7、 technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates cl

8、osely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteri

9、a needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of p

10、atent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name u

11、sed in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical

12、Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/TC 292, Security and resilience.iv ISO 2015 All rights reserved ISO/TR 22351:2015(E) Introduction Clear situation awareness is a key factor for effective emergency r

13、esponse. The building of an operational picture is based on the integration and assessment of information collected from the different teams of responders and other information sources. It relies on exchange of information. The ability to exchange information in a timely and secure manner is critica

14、l to the effective conduct of emergency management. This Technical Report proposes a structured message in order to facilitate these exchanges. The message is flexible with regard to the regulations of nations and organizations. It helps the operational information exchange between organizations, es

15、pecially when different terminologies or different languages are used as in civilmilitary cooperation, trans-border collaboration or multi-agency emergencies. It enables all involved organizations to co-operate with a high level of interoperability as described in ISO 22320. This Technical Report is

16、 based on results from the CEN Workshop Agreement CWA 15931 published in March 2009 as the Tactical Situation Object (TSO) by a European Frame Work Program 6 project. ISO 2015 All rights reserved v Societal security Emergency management Message structure for exchange of information 1 Scope This Tech

17、nical Report describes a message structure for the exchange of information between organizations involved in emergency management. An organization can ingest the received information, based on the message structure, in its own operational picture. The structured message is called Emergency Managemen

18、t Shared Information (EMSI). This Technical Report describes the message structure built in order to facilitate interoperability between existing and new information systems. The intended audience of this Technical Report is control room engineers, information systems designers and decision makers i

19、n emergency management. NOTE The EMSI can be used complementary to other message protocols, as for example the common alert protocol (CAP). 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For

20、dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 22300, Societal security Terminology 3 T erms a nd definiti ons For the purposes of this document, the terms and definitions given in ISO 22

21、300 apply. NOTE All terms and definitions contained in ISO 22300 are available on the ISO Online Browsing Platform: www.iso.org/obp. 4 The EMSI message 4.1 General An EMSI describes a part of the operational picture at a particular time. It is exchanged between nodes in order to transfer information

22、 and describes events, resources and missions (see Figure 1). TECHNICAL REPORT ISO/TR 22351:2015(E) ISO 2015 All rights reserved 1 ISO/TR 22351:2015(E) Organization A Node A1 Fixed or mobile control room, etc. Organization B Node B1 Fixed or mobile control room, etc. EMSI Event 1 Event 3 Event 2 Nee

23、d for information exchange Figure 1 Exchange of EMSI between organizations An EMSI can be used peer-to-peer at the same level of the command hierarchy or up and down the hierarchy. This information contributes to the situational awareness of organizations involved for facilitating coordination of pl

24、ans and actions. Figure 2 describes in an object model the entities which are involved in the EMSI.2 ISO 2015 All rights reserved ISO/TR 22351:2015(E) Organization Node Event EMSI Related resources Related missions 1 Mg 0 D 0 0 D 1 D 0 D 0 D 0 Key Cardinality: 1 The element is mandatory. Only one va

25、lue can be provided. 0,1 The element is optional. If it is present, only one value can be provided. 0n The element is optional. If it is present, several values can be provided. 1n The element is mandatory. Several values can be provided. NOTE Arrows in the diagram represent relationships according

26、to cardinality but not information flows. Figure 2 EMSI described in an object model An organization owns one or more nodes. A node can manage events. The message structure is hidden from the user. The applications handling the EMSI present the information to users in their own language, applying th

27、eir own set of symbols. The objective of this Technical Report is to agree on the set of information with the following properties: useful to share between responders and that represent the situation; simple enough in order to enable agreement on use and implementation; extensive enough to support t

28、he planning and decision making process. 4.2 EMSI content The Emergency Management Information Sharing contains the following information. a) Identification of the EMSI: 1) identifier of the individual message; 2) identification of its originator; ISO 2015 All rights reserved 3 ISO/TR 22351:2015(E)

29、3) time of creation; 4) relation to any other EMSI; 5) organization level, confidentiality and urgency of the information; 6) links to external information; 7) date and time of creation of EMSI. b) Description of the event: 1) limited assessment of the event; 2) date and time when the event was decl

30、ared; 3) date and time of the observation; 4) location of the event and associated geographical information; 5) enumeration of the casualties found; 6) prediction of future casualties. c) Description of the resources: 1) resources each organization has available for the event; 2) resources in use; 3

31、) resource capabilities; 4) resource position. d) Description of the missions: 1) missions in progress; 2) missions foreseen. 4.3 EMSI structure An EMSI is organized in four elements groups. CONTEXT: identification of the EMSI; EVENT: description of the event; RESOURCE: allocated or available resour

32、ce(s) to/for the event; MISSION: description of mission(s). CONTEXT and EVENT are mandatory while RESOURCE and MISSION are optional. Figure 3 shows this structure.4 ISO 2015 All rights reserved ISO/TR 22351:2015(E) CONTEXTE VENT 1 1 RESOURCE MISSION 0n 0n EMSI Key Cardinality: 1 The element is manda

33、tory. Only one value can be provided. 0n The element is optional. If it is present, only one value can be provided. Figure 3 Content and structure of EMSI 4.4 Gener al rules for t he definition of element s An element within an EMSI is described by its name, definition, type, cardinality and value d

34、omain. An element may be subdivided hierarchically into sub elements which may be subdivided further hierarchically and so on. All sub-elements in the hierarchy are simply called elements. The following three types of elements can be used in the EMSI structure. a) Elements which are defined solely b

35、y their types: string of characters, integer value, double or float value. These values may be constrained including: limited number of characters for the strings; minimum and maximum values for numerical elements. EXAMPLES Identifiers, coordinates (latitude, longitude, height), address. b) Elements

36、 which are defined by their type (always “string of characters”), but constrained to a limited fixed list of valid values. EXAMPLES SECLASS, Security classification of the EMSI, string (enumeration), CONFID = confidential, RESTRC = restricted, SECRET = secret, TOPSRT = top secret, ISO 2015 All right

37、s reserved 5 ISO/TR 22351:2015(E) UNCLAS = unclassified, UNMARK = unmarked. c) Elements which are defined by their type (always “string of characters”), but constrained to an extensive list of valid values. EXAMPLE RTYPE CLASS, type of the resource: rescue team, vehicle, tent, water purifier, etc.,

38、string (maximum 80 characters); the complete list of values may be described in a specific part of the data elements and codes specification in the form of a dictionary. 4.5 Rules for the list of elements The content of the field reflects entities in the real world and is worded in English. It shoul

39、d not be longer than 32 characters. The use of free text in the field should be limited as it cannot be automatically interpreted or translated. A free text field should not exceed 500 characters. In case that the value domain is an extensive list, the field of the element description refers to a di

40、ctionary of codes. 4.6 Implementation of the EMSI It is recommended to use XML when implementing the EMSI. 5 The EMSI codes dictionary 5.1 The role of the codes The use of codes rather than free text gives the possibility to automatically translate information into language appropriate to the user.

41、A significant number of elements values are defined by codes representing real world concepts. 5.2 Rules 5.2.1 Code structure The code for each individual item is expressed as a hierarchical structure subdivided into code elements. The code elements are separated by a slash. 5.2.2 Code elements Code

42、 elements are composed from one up to eight characters taken from the unaccented upper case Latin alphabet (AZ) and 10 digits (09). 5.2.3 Examples EXAMPLE 1 A fire appliance in a road vehicle with breathing apparatus support. a) MAT/VEH/ROADVE/FRFGTN/BREATH MAT: material/VEH: vehicle/ROADVE: road ve

43、hicle6 ISO 2015 All rights reserved ISO/TR 22351:2015(E)/FRFGTN: fire appliance/BREATH: with breathing apparatus support EXAMPLE 2 If the observer does not know the category of the vehicle the code generated could be M AT/ V EH/ROADVE. EXAMPLE 3 An EMSI makes sure that the information can be transla

44、ted to different languages (see Figure 4). Node A1 Fixed or mobile control room, etc. Organization A (France) Tempte Tempte Node B1 Fixed or mobile control room, etc. Organization B (Germany) Sturm Sturm Node C1 Fixed or mobile control room, etc. Organization C (Poland) Burza Burza EMSI/DIS/STORM Fi

45、gure 4 Code translated automatically to the language of the operator This example shows how the event of a storm will be encoded in an EMSI message and disseminated to emergency management information systems operators in different countries./DIS/STORM will be translated to “tempte in French, “Sturm

46、 in German and “burza” in Polish on the graphical user interface. ISO 2015 All rights reserved 7 ISO/TR 22351:2015(E) Annex A (informative) Example of EMSI messages This Annex describes examples of EMSI messages using XML. Users will not, in general, manipulate the messages directly, but through int

47、eractive and user-friendly tools based on graphical windows with maps and tables for the creation and the modification of the EMSI elements. This example is based on a scenario involving a collision between a truck and a high speed train in the vicinity of a medium-size city. Figure A.1 Example NOTE

48、 In the different diagrams of this example, the Google Earth software 1)has been used for the display of the satellite image and the vector overlays. Scenario: Witnesses call the 112 emergency number and provide a first assessment of the situation. These pieces of information are entered in the information system of the Call Centre. Then the Call Centre dispatches the alert to the control rooms of two of the organizations which are involved in such incidents: the police and the