EN 17870:2023

SLOVENSKI STANDARD
01-september-2023
Inteligentni transportni sistemi - e-Varnost - Koncept dodatnih podatkov e-Klica za
omejitve opreme
Intelligent transport systems - eSafety - eCall additional data concept for equipment
limitations
Intelligente Verkehrssysteme - eSicherheit - eCall OAD für Einrichtungsbegrenzungen
Systèmes de transport intelligents - eSafety - concept de données supplémentaires
d’eCall pour limitations de l’équipement
Ta slovenski standard je istoveten z: EN 17870:2023
ICS:
03.220.20 Cestni transport Road transport
13.200 Preprečevanje nesreč in Accident and disaster control
katastrof
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 17870
EUROPEAN STANDARD
NORME EUROPÉENNE
June 2023
EUROPÄISCHE NORM
ICS 03.220.20; 13.200; 35.240.60
English Version
Intelligent transport systems - eSafety - eCall additional
data concept for equipment limitations
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
de l'équipement Ausrüstungsbeschränkungen
This European Standard was approved by CEN on 30 April 2023.

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. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists 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 Management
Centre has the same status as the official versions.

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, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 17870:2023 E
worldwide for CEN national Members.

Contents Page
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
Annex B (informative) ASN.1 definition of complete MSD message with equipment
limitations . 13
Bibliography . 18

European foreword
This document (EN 17870:2023) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by December 2023, and conflicting national standards shall
be withdrawn at the latest by December 2023.
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.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: 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, Türkiye and the United
Kingdom.
Introduction
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
bring significant savings to the society in and to reduce human suffering.
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
installation.
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
emergency process and cost valuable time.
Part of eCall is (the sending of) a “Minimum Set of Data” (MSD) which is specified 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
document is mandatory.
NOTE The communications media and means of transferring the eCall MSD are not specified in this document.
See list of referenced standards.
1 Scope
This document specifies an additional data concept that can be transferred as the ‘optional additional
data’ part of an eCall MSD, see EN 15722, that can be transferred from a vehicle to a PSAP in the event of
a crash or emergency via an eCall communication session.
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
consistent and usable matter.
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
specified in this document.
NOTE 2 Additional data concepts can also be transferred, and it is advised to register any such data concepts
using a data registry as specified in EN ISO 24978 [1]. See www.esafetydata.com for an example.
2 Normative references
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.
EN 15722, Intelligent transport systems - ESafety - ECall minimum set of data
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules — Part 2: Specification of Packed
Encoding Rules (PER)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:

• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1
ASN.1
Abstract Syntax Notation One
notation that describes rules and structures for representing, encoding, transmitting and decoding data
enabling representation of objects that are independent of machine-specific encoding techniques
Note 1 to entry: See various parts of ITU Recs 8824 and 8825 (ISO/IEC 8824 and ISO/IEC 8825, various parts).
3.2
eCall
emergency call generated either automatically via activation of in-vehicle sensors or manually by the
vehicle occupants
Note 1 to entry: 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 of the vehicle and the most
appropriate 'Public Safety Answering Point'
3.3
MSD
minimum set of data
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
Note 1 to entry: This data is as specified in EN 15722.
4 Symbols and abbreviations
For the purposes of this document, the following symbols and abbreviations apply.
M mandatory
MSD minimum set of data
O optional
OID object identifier
PSAP public safety answering point
UPER unaligned packed encoding rules (ASN.1)
5 Conformance
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
concept mandatory for equipment that has limited functionality.
NOTE The mere existence of this data concept does not allow for, condone or suggest any limitation in eCall
equipment.
6 Requirements
6.1 General
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.
6.2 Concepts and formats
6.2.1 MSD data concepts
The MSD as specified 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 may be used to add information elements containing
information about the vehicle involved.
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, see
European Union and national privacy regulations pertaining at the time of the transfer of any such
personal data and the provisions of EU 2016/679 ‘General Data Protection Requirements’.
6.2.2 Representation of MSD data concepts
The MSD is represented in ‘Abstract Syntax Notation’ (ASN.1) using the ‘Unaligned Packed Encoding
Rules’ (UPER) as specified in ISO/IEC 8825-2 using the ASN.1 definitions specified in EN 15722. The
message shall be sent in the sequence specified in that same annex.
This additional data concept is also specified following the provision made in above named annex.
6.2.3 Distribution of MSD data
The MSD shall be transmitted and formed as described in EN 15722, which also means that the maximum
length of the overall MSD shall not exceed 140 bytes.
6.2.4 Equipment limitations additional data-concept ‘Object Identifier’
The object identifier uniquely identifies the format and meaning of the data which follows in the
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
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 A
...