kSIST FprEN 17870:2023

SLOVENSKI STANDARD
oSIST prEN 17870:2022
01-september-2022

Inteligentni transportni sistemi - e-Varnost - Koncept dodatnih podatkov e-Klica za

Intelligent transport systems - eSafety - eCall additional data concept for equipment

Intelligente Verkehrssysteme - eSicherheit - eCall OAD für Einrichtungsbegrenzungen

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Systèmes de transport intelligents - eSafety - concept Intelligente Verkehrssysteme - eSicherheit - eCall

de données supplémentaires d'eCall pour limitations zusätzliches Datenkonzept für

This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee

If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations

which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other

language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,

Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without

© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17870:2022 E

European foreword ............................................................................................................................................ 3

Introduction .......................................................................................................................................................... 4

1 Scope .......................................................................................................................................................... 5

2 Normative references .......................................................................................................................... 5

3 Terms and definitions ......................................................................................................................... 5

4 Symbols and abbreviations ............................................................................................................... 6

5 Conformance ........................................................................................................................................... 6

6 Requirements ......................................................................................................................................... 6

6.1 General...................................................................................................................................................... 6

6.2 Concepts and formats .......................................................................................................................... 6

6.2.1 MSD data concepts ................................................................................................................................ 6

6.2.2 Representation of MSD data concepts ........................................................................................... 7

6.2.3 Distribution of MSD data .................................................................................................................... 7

6.2.4 Equipment limitations additional data-concept ‘Object Identifier’.................................... 7

6.2.5 Equipment limitations additional data concept ‘data’ ............................................................ 7

6.3 Contents of the ‘Minimum Set of Data’ (MSD) ............................................................................. 7

6.3.1 Context ...................................................................................................................................................... 7

6.3.2 Basic contents of MSD .......................................................................................................................... 8

6.3.3 Contents of the optionalAdditionalData ....................................................................................... 8

6.4 Mode of operation ............................................................................................................................... 10

Annex A (normative) ASN.1 definition of additional data block ..................................................... 11

limitations ............................................................................................................................................. 13

Bibliography ....................................................................................................................................................... 18

This document (prEN 17870:2022) has been prepared by Technical Committee CEN/TC 278 “Intelligent

The pan-European in-vehicle emergency call, 'eCall', is estimated to have the potential to save up to 2 500

fatalities annually in the EU when fully deployed, and furthermore to reduce the severity of injuries, to

eCall, in the context of “Intelligent Transport Systems” or “ITS”, (previously known as “Road Traffic and

Transport Telematics”) can be described as a “user instigated or automatic system to provide notification

to public safety answering points, by means of wireless communications, that a vehicle has crashed, and

to provide coordinates and a defined minimum set of data, and where possible a voice link to the PSAP”.

The installation of eCall is mandatory for each new type of passenger vehicle car which is approved after

March 2018 and the system has already proven to be beneficial. Expansion to other vehicle categories

and the possibility to retrofit equipment to existing vehicles is imminent and additional standards are

devised to support this. Such standards are needed because the existing (core) standards are focussed on

mandatory, in-factory installation in specific categories of vehicle (UNECE Category M1/N1). Projects like

HeERO, iHeERO, sAFE and others have shown that sometimes not all requirements laid out in the core

standards can be met, due to physical or other limitations related to the vehicle category or type of

Although such limitations are known at the sending side, the receiving side (i.e. the PSAP) currently does

not (always) have means to determine those. There is, to name one example, based on the core standards,

no way a PSAP can determine whether the eCall equipment in the vehicle is installed in-factory, retrofit

or even a user installed after market solution. The lack of this knowledge can interfere with the

Part of eCall is (the sending of) a “Minimum Set of Data” (MSD) which is defined in EN 15722. That

standard makes a provision for additional data that can be embedded in the MSD assuming that it follows

a(nother) standard. This document is such standard and it describes an additional data concept that can

and is expected to be used to inform the PSAP about limitations to the equipment. Such limitations are

only allowed if supported by one or more standard(s) applicable to that specific application of eCall. If

and when a standard endorses a limitation, the use of the additional data concept described in this

NOTE The communications media and means of transferring the eCall MSD are not defined in this document.

This document defines an additional data concept that can be transferred as the ‘optional additional data’

part of an eCall MSD, as defined in EN 15722, that can be transferred from a vehicle to a PSAP in the event

The purpose of this document is to provide means to notify the PSAP of any limitations to the sending

equipment that are endorsed by other standards, but not (immediately) apparent to the receiver. Lack of

knowledge about these limitations can hamper the emergency process. This document describes an

additional data concept which facilitates the inclusion of information about such limitations in a

This document can be seen as an addendum to EN 15722; it contains as little redundancy as possible.

NOTE 1 The communications media protocols and methods for the transmission of the eCall message are not

NOTE 2 Additional data concepts can also be transferred, and it is advised to register any such data concepts

using a data registry as defined in EN ISO 24978 [1]. See www.esafetydata.com for an example.

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

abstract syntax notation one as specified in the various parts of ITU Recs 8824 and 8825 (ISO/IEC 8824

emergency call generated either automatically via activation of in-vehicle sensors or manually by the

vehicle occupants; when activated it provides notification and relevant location information to the most

appropriate 'Public Safety Answering Point’, by means of mobile wireless communications networks,

carries a defined standardised ‘Minimum Set of Data’ notifying that there has been an incident that

requires response from the emergency services, and establishes an audio channel between the occupants

direct, timely data content of an eCall message to the PSAP operator receiving the emergency call

containing information about the location of the incident, providing detail characterising the vehicle, and

potentially sometimes also providing additional data that is deemed relevant, as defined in EN 15722

For the purposes of this document, the following symbols and abbreviations apply.

The conformance requirements for this document are simply that the concept conforms to EN 15722, and

that the total length of the MSD, including this additional data concept, if used, remains 140 bytes.

eCall equipment that is conformant to (only) the core standards shall not use this data concept, as its

functionality shall not be limited. Use of this data concept is reserved for eCall equipment that is and shall

be (also) conformant to additional standards that allow for such limitation, whenever such limitation

applies. Any eCall standard that endorses limitations to the core standards shall make the use of this data

NOTE The mere existence of this data concept does not allow for, condone or suggest any limitation in eCall

This document describes an addition to the standard EN 15722 for the coding of the MSD message. All

requirements from EN 15722 shall be met in respect of this additional data concept.

The MSD as defined in EN 15722 is a direct, timely message to the PSAP operator receiving the emergency

The MSD has an optional additional data block that may be used to add information elements containing

The information elements in the additional data block of the MSD will have been selected on the basis of

their relevance in an emergency rescue situation. These will in any event need to be provided in

accordance with European Union and national privacy regulations pertaining at the time of the transfer

of any such personal data and in accordance with the provisions of EU 2016/679 ‘General Data Protection

The MSD is represented in ‘Abstract Syntax Notation’ (ASN.1) using the ‘Unaligned Packed Encoding

Rules’ (UPER) as defined in ISO/IEC 8825-2 using the ASN.1 definitions defined in EN 15722. The

This additional data concept shall also be defined following the provision made in above named annex.

The MSD shall be transmitted and formed as described in EN 15722, which also means that the maximum

The object identifier uniquely identifies the format and meaning of the data which follows in the

Both the syntax of the data structure and the semantic meaning of the content is referenced via this

The uniqueness of each specific relative identifier is ensured by a specific international standardization

body, and maintained in a data registry operated in accordance with EN ISO 24978 [1]. These identifiers

are all relative to a specific root. And the root of all eCall relative OID's 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

‘Optional Additional Data concepts’ and within that subarc this additional data concept is registered as

‘.7’. The OID for the version of that concept as defined in this deliverable shall be 1.0.14817.106.2.1.2.7.1.

The OID for ‘Optional Additional Data concepts’ (1.0.14817.106.2.1.2) is fixed and shall not be transmitted

over the air as part of the additional data. The MSD data element ‘oid’ is defined as RELATIVE-OID and