CEN TS 16405-2017 Intelligent transport systems - Ecall - Additional data concept specification for heavy goods vehicles《智能运输系统-ECall-为重型货车附加数据的概念规范》.pdf

1、Intelligent transport systems Ecall Additional data conceptspecification for heavy goods vehiclesPD CEN/TS 16405:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National forewordThis Published Document is the UK implementation of CEN/TS 16405:2017.It supersedes P

2、D CEN/TR 16405:2013 which is withdrawn.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all

3、the necessary provisions ofa contract. Users are responsible for its correct application. The British Standards Institution 2017.Published by BSI Standards Limited 2017ISBN 978 0 580 86428 5ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This P

4、ublished Document was published under the authority of theStandards Policy and Strategy Committee on 28 February 2017.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TS 16405:2017TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 1

5、6405 January 2017 ICS 03.220.20; 35.240.60 Supersedes CEN/TR 16405:2013English Version Intelligent transport systems - Ecall - Additional data concept specification for heavy goods vehicles Systmes de transports intelligents - Scurit - Spcification de conception de donnes additionnelles pour les poi

6、ds lourds Intelligente Verkehrssysteme - E-Sicherheit - Zustzliche Datenkonzept-Spezifikation fr Lastkraftwagen This Technical Specification (CEN/TS) was approved by CEN on 13 October 2014 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After t

7、wo years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly

8、at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Bulga

9、ria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerl

10、and, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2017 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national M

11、embers. Ref. No. CEN/TS 16405:2017 EPD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 2 Contents Page Foreword 3 Introduction 4 1 Scope 5 2 Normative References . 5 3 Terms and definitions . 5 4 Symbols and abbreviations . 6 5 Requirements . 7 5.1 General 7 5.2 Concepts and formats 7 5.2.1 MSD data concepts

12、 7 5.2.2 Representation of MSD data concepts . 7 5.2.3 Distribution of MSD data 7 5.2.4 Commercial vehicles optional additional data concept Object Identifier 7 5.2.5 Commercial vehicle optional additional data concept data 8 5.3 Contents of the Minimum Set of Data (MSD) . 8 5.3.1 Basic contents of

13、MSD 8 5.3.2 Contents of the optionalAdditionalData for Schema A 9 5.3.3 Contents of the optionalAdditionalData for Schema B . 13 Annex A (normative) ASN.1 definition of optional datablock . 16 A.1 General . 16 A.2 Definition of contents of optionalAdditionalData.data Schema A 16 A.2.1 ASN.1 definiti

14、on 16 A.2.2 Syntax check of ASN.1 definition 18 A.2.3 Example . 18 A.3 Definition of contenst of optionalAdditionalData.data Schema B 19 A.3.1 General . 19 A.3.2 ASN.1 definition 19 A.3.3 Syntax check . 20 A.3.4 Example . 20 Annex B (informative) ASN.1 definition of complete MSD message with HGV inf

15、o . 22 B.1 General . 22 B.2 ASN.1 definition of complete extended MSD message, HGV Schema A . 22 B.3 Example . 29 Bibliography . 32 PD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 3 Foreword This document (CEN/TS 16405:2017) has been prepared by Technical Committee CEN/TC 278 “Intelligent transport system

16、s”, the secretariat of which is held by NEN. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights. This document supersedes CEN/TR 16405:2013. A Technical

17、Report on this subject, proposing these specifications, was approved in 2012 (CEN/TR 16405), for field testing. The proposed specifications have subsequently been tested in the field (by EC Project HeERO and others). The semantic content of this Technical Specification remains unchanged. However the

18、 parent Standard EN 15722 (eCall Minimum Set of Data) has been revised and updated, and this Technical Specification is consistent with the layout and specifications of the revised EN 15722. According to the CEN/CENELEC Internal Regulations, the national standards organisations of the following coun

19、tries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norwa

20、y, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. PD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 4 Introduction An eCall is an emergency call generated either automatically via activation of in-vehicle sensors or manually by the vehicle o

21、ccupants; when activated, to provide notification and relevant location information to the most appropriate Public Safety Answering Points (PSAP), by means of mobile wireless communications networks and carries a defined standardized Minimum Set of Data (MSD), notifying that there has been an incide

22、nt that requires response from the emergency services and establishes an audio channel between the occupants of the vehicle and the most appropriate PSAP. The MSD (specified in EN 15722) contains static information regarding the vehicle, dynamic information regarding its location, direction of trave

23、l etc., at the time of the incident, and makes provision for additional data to be provided. This Technical Specification provides specification for an optional additional data concept for commercial vehicles to provide dynamic data about the load that it is carrying at the time of the incident that

24、 triggered the eCall, with specific emphasis on identification of dangerous goods. Two variants are provided, one (schema A) for use where information about the goods (ADR classified or not) is known in the eCall device; the second variant (schema B) is for use where information about the load has t

25、o be fetched from other sources. It is the intention that this Technical Specification is tested in demonstration projects (such as HeERO) with a view to becoming the basis for a future European or International Standard. In order to claim conformance with this Technical Specification, communication

26、 is to be established using accepted wireless communication standards, and it is to be able to demonstrate that the MSD transferred together with any standardized optional data elements defined herein comply with the specifications of this Technical Specification, to the extent that such data are av

27、ailable from the vehicle. PD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 5 1 Scope This Technical Specification defines an additional data concept that may be transferred as an optional additional data concept as defined in EN 15722 eCall MSD, that may be transferred from a goods vehicle to a PSAP in the

28、 event of a crash or emergency via an eCall communication session. Two variants are provided, one (schema A) for use where information about the goods (ADR classified or not) is known in the eCall device; the second variant (schema B) is for use where such information is to be fetched from elsewhere

29、. NOTE This Technical Specification is complementary and additional to EN 15722; and contains as little redundancy as possible. The communications media protocols and methods for the transmission of the eCall message are not specified in this Technical Specification. Additional data concepts may als

30、o be transferred, and any such data concepts should be registered using a data registry as defined in EN ISO 24978. See for an example. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited appl

31、ies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 15722, Intelligent transport systems - ESafety - ECall minimum set of data ISO/IEC 8825-2, Information technology ASN.1 encoding rules: Specification of Packed Encoding Rules (PER) Part

32、2 EN ISO 24978, Intelligent transport systems - ITS Safety and emergency messages using any available wireless media - Data registry procedures (ISO 24978) 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 112 single European emergency call num

33、ber supporting Teleservice 12 ETSI/TS 122 003 3.2 ASN.1 abstract syntax notation one as specified in the various parts of ITU Recs 8824 and 8825 (ISO 8824 and ISO 8825 various parts) PD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 6 3.3 commercial vehicle mechanically propelled road vehicle (vehicle type

34、N1, N2 or N3) that is of a construction primarily suited for the carriage of goods or burden of any kind (not including people) and travelling on a road laden Note 1 to entry: This includes vehicles designed or adapted to have a maximum weight exceeding 3,500 tonnes, but explicitly excludes busses o

35、r other vehicles designed and constructed for the carriage of passengers (ie. vehicle types M1, M2 or M3) 3.4 dangerous goods categories of goods carried by road defined by the European Agreement concerning the International Carriage of Dangerous Goods by Road (ADR) as dangerous; these are character

36、ised as articles or substances which are capable of posing a significant risk to health, safety or to property when transported 3.5 eCall emergency call generated either automatically via activation of in-vehicle sensors or manually by the vehicle occupants; when activated it provides notification a

37、nd relevant location information to the most appropriate Public Safety Answering Point, by means of mobile wireless communications networks, carries a defined standardized Minimum Set of Data notifying that there has been an incident that requires response from the emergency services, and establishe

38、s an audio channel between the occupants of the vehicle and the most appropriate Public Safety Answering Point 3.6 Kemler code ADR Hazard Identification Number (HIN), carried on placards on tank cars and tank containers running by road under international ADR regulations 3.7 uniform resource identif

39、ier URI string of characters used to identify a name or a resource on the Internet 3.8 uniform resource locator URL URI that in addition to identifying a resource provides a means of locating the resource by describing its primary access mechanism EXAMPLE Its network location 4 Symbols and abbreviat

40、ions ADR Accord europen relative au transport international des marchandises Dangereuses par Route ETSI European Telecommunications Standards Institute M Mandatory MSD Minimum set of data PD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 7 O Optional PER Packed Encoding Rules (ASN.1) PSAP Public Safety Answ

41、ering Point UPER Unaligned Packed Encoding Rules (ASN.1) 5 Requirements 5.1 General This Technical Specification describes an addendum to the standard defined in EN 15722 for the coding of the MSD message. Any requirement from EN 15722 shall be met for the exchange of information about loads in the

42、additional data block 5.2 Concepts and formats 5.2.1 MSD data concepts The MSD as defined in EN 15722 is a direct, timely message to the PSAP operator receiving the emergency call. The MSD has an optional additional data block that will be used to add information elements containing information abou

43、t the load of the vehicle involved. The information elements in the additional data block of the MSD have been selected on the basis of their relevance in an emergency rescue situation. 5.2.2 Representation of MSD data concepts The MSD is represented in Abstract Syntax Notation (ASN.1) using the Una

44、ligned Packed Encoding Rules (UPER) as defined in ISO/IEC 8825-2 using the ASN1 definitions defined in Annex A of EN 15722. The message shall be sent in the sequence defined in that same Annex. The information about the load of the vehicle sending the MSD shall be represented in ASN.1 UPER as well,

45、following the provision made in above named Annex. 5.2.3 Distribution of MSD data The MSD shall be transmitted as described in EN 15722. 5.2.4 Commercial vehicles optional additional data concept Object Identifier The object identifier uniquely identifies the format and meaning of the data which fol

46、lows in the optional additional data concept. Both the syntax of the data structure and the semantic meaning of the content is referenced via this identifier so that it can be usefully applied. The uniqueness of each specific relative identifier is ensured by a specific international standardization

47、s body, and maintained in a data registry operated in accordance with EN ISO 24978. These identifiers are all relative to a specific root. And the root of all eCall relative OIDs shall be the same. eCall has been allocated the OID 1.0.14817.106.2.1. Within this, arc .2 has been defined to contain Op

48、tional Additional Data concepts. The OID for this deliverable shall be 1.0.14817.106.2.1.2.1. PD CEN/TS 16405:2017CEN/TS 16405:2017 (E) 8 This deliverable defines two schemes that each have their own unique OID: Schema A: 1.0.14817.106.2.1.2.1.1 Schema B: 1.0.14817.106.2.1.2.1.2 The OID for Optional

49、 Additional Data concepts (1.0.14817.106.2.1.2) is fixed and shall not be transmitted over the air as part of the optional additional data. The MSD data element oid is defined as RELATIVE-OID and shall contain 1.1 if Schema A is used, or 1.2 if Scheme B is used. For further detail regarding the use of OIDs in eCall, see EN 15722. 5.2.5 Commercial vehicle optional additional data concept data The objective of the commercial vehicle data concept is to provide the PSAP with data concerning the load of th