SIST-TP CEN/TR 16405:2013

SLOVENSKI STANDARD
SIST-TP CEN/TR 16405:2013
01-marec-2013
Inteligentni transportni sistemi - e-Varnost - Izbirni nabor dodatnih podatkov pri e-
klicu za sistem e-klica v težkih tovornih vozilih
Intelligent transport systems - ESafety - ECall additional optional data set for heavy
goods vehicles eCall
Intelligente Transportsysteme - eSicherheit - Zusätzliche optionale Datenmenge im
Schwerkraftverkehr für eCall
Systèmes de Transports Intelligents - ESafety - Ensemble optionnel de données
additionnelles ECall pour l'ECall des poids Lourds
Ta slovenski standard je istoveten z: CEN/TR 16405:2013
ICS:
13.200 3UHSUHþHYDQMHQHVUHþLQ Accident and disaster control
NDWDVWURI
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
43.040.15 $YWRPRELOVNDLQIRUPDWLND Car informatics. On board
9JUDMHQLUDþXQDOQLãNLVLVWHPL computer systems
SIST-TP CEN/TR 16405:2013 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TP CEN/TR 16405:2013

---------------------- Page: 2 ----------------------

SIST-TP CEN/TR 16405:2013


TECHNICAL REPORT
CEN/TR 16405

RAPPORT TECHNIQUE

TECHNISCHER BERICHT
January 2013
ICS 03.220.20; 35.240.60
English Version
Intelligent transport systems - ESafety - ECall additional optional
data set for heavy goods vehicles eCall
Systèmes de Transports Intelligents - ESafety - Ensemble Intelligente Transportsysteme - eSicherheit - Zusätzliche
optionnel de données additionnelles ECall pour l'ECall des optionale Datenmenge im Schwerkraftverkehr für eCall
poids Lourds


This Technical Report was approved by CEN on 30 July 2012. It has been drawn up by the Technical Committee CEN/TC 278.

CEN members are the national standards bodies of 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, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United
Kingdom.





EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2013 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 16405:2013: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Contents Page
Foreword . 3
Introduction . 4
1 Scope . 5
2 Conformance . 5
3 Normative references . 5
4 Terms and definitions . 5
5 Symbols and abbreviations . 6
6 General overview of the eCall HGV/GV data concept within the context of eCall . 7
7 Requirements . 8
7.1 Concepts and formats . 8
7.1.1 MSD data concepts . 8
7.1.2 Format definition of MSD data concepts . 8
7.1.3 HGV/GV optional additional data concept ‘Object Identifier’ . 8
7.1.4 Sequence of MSD data concepts . 8
7.1.5 Data presentation of MSD . 8
7.2 Minimum set of data (MSD) . 9
7.2.1 General . 9
7.2.2 Order of bits and bytes . 9
7.2.3 Contents of MSD . 9
7.2.4 MSD ‘Optional additional data’ . 10
7.3 HGV/GV data concept  General . 10
7.4 eCall HGV/GV data concept definition . 11
7.4.1 eCall HGV Schema A : ADR Goods . 11
7.4.2 eCall HGV Schema B : Other Goods (non ADR) . 15
7.5 eCall HGV/GV data concept presentation . 17
Annex A (normative) ASN.1 PER representation of MSD including Schema A  ASN.1 PER
representation of MSD including Schema A . 18
Annex B (normative) ASN.1 PER representation of MSD including Schema B  ASN.1 PER
representation of MSD including Schema B . 27
Bibliography. 36

2

---------------------- Page: 4 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Foreword
This document (CEN/TR 16405:2013) has been prepared by Technical Committee CEN/TC 278 “Road
transport and traffic telematics”, 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 [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
3

---------------------- Page: 5 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Introduction
An eCall is an emergency call generated either automatically via activation of in-vehicle sensors or manually
by the vehicle occupants; 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 standardised Minimum Set of Data (MSD), 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 PSAP.
The MSD (specified in EN 15722) contains static information regarding the vehicle, dynamic information
regarding its location, direction of travel etc., at the time of the incident, and makes provision for additional
data to be provided.
This Technical Report provides potential specification for an optional additional data concept for HGVs to
provide dynamic data about the load that it is carrying at the time of the incident that triggered the eCall, with
specific emphasis on identification of dangerous goods. Two variants are provided, one (schema A) for use
where dangerous goods (ADR classified); the second variant (schema B) is for use where no ADR classified
load is known.
It is the intention that the specification in this Technical Report is tested in demonstration projects (such as
HeERO) with a view to becoming the basis for a future European or International Standard.
NOTE The communications media protocols and methods for the transmission of the eCall message are not
specified in this Technical Report.
Additional data concepts may also be transferred, and any such data concepts should be registered using a
data registry as defined in EN ISO 24978.
4

---------------------- Page: 6 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
1 Scope
This Technical Report defines an additional data concept that may be transferred as an ‘optional additional
data concept’ as defined in ‘Block 12’ of CEN 15722 eCall MSD, that may be transferred from a goods vehicle
to a PSAP in the event of a crash or emergency via an eCall communication session. Two variants are
provided, one (schema A) for use where dangerous goods (ADR classified); the second variant (schema B) is
for use where no ADR classified load is known.
NOTE The communications media protocols and methods for the transmission of the eCall message are not
specified in this Technical Report.
Additional data concepts may also be transferred, and any such data concepts should be registered using a
data registry as defined in EN ISO 24978.
2 Conformance
In order to claim conformance with this deliverable, communication is to be established using accepted
wireless communication standards, and it is to be able to demonstrate that the MSD transferred together with
any standardised optional data elements defined herein comply with the specifications of this Technical
Report, to the extent that such data is available from the vehicle.
3 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
EN 15722:2011, Intelligent transport systems  eSafety  eCall minimum set of data (MSD)
EN 16062, Intelligent transport systems  eSafety  eCall high level application requirements (HLAP)
EN 16072, Intelligent transport systems  eSafety  Pan European eCall operating requirements
EN 16102, Intelligent transport systems  eCall  Operating requirements for third party support
EN ISO 24978, Intelligent transport systems  ITS Safety and emergency messages using any available
wireless media  Data registry procedures (ISO 24978)
ISO/IEC 8825-2, Information technology  ASN.1 encoding rules: Specification of Packed Encoding Rules
(PER)
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
112
single European emergency call number supporting Teleservice 12
[SOURCE: ETSI TS 122 003]
5

---------------------- Page: 7 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
4.2
ASN.1
abstract syntax notation one as specified in the various parts of ITU Recs 8824 and 8825 (ISO 8824 and 8825
various parts)
4.3
eCall
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
PSAP, by means of mobile wireless communications networks, carries a defined standardised MSD 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 PSAP
4.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 characterised as articles or substances which
are capable of posing a significant risk to health, safety or to property when transported
4.5
goods vehicle
GV
mechanically propelled road vehicle that is of a construction primarily suited for the carriage of goods or
burden of any kind and travelling on a road laden
4.6
heavy goods vehicle
HGV
mechanically propelled road vehicle that is of a construction primarily suited for the carriage of goods or
burden of any kind and designed or adapted to have a maximum weight exceeding 3,500 kilograms when in
normal use and travelling on a road laden
4.7
uniform resource identifier
URI
string of characters used to identify a name or a resource on the Internet
4.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 (e.g., its network location)
5 Symbols and abbreviations
ADR European Agreement concerning the International Carriage of Dangerous Goods by Road
MSD Minimum Set of Data
PER Packed Encoding Rules (ASN.1 :ITU/Rec 8825-2/X/691)
PSAP Public Safety Answering Points
6

---------------------- Page: 8 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
6 General overview of the eCall HGV/GV data concept within the context of eCall
In the introduction to this European Technical Report, eCall was described as "an emergency call generated
either automatically via activation of in-vehicle sensors or manually by the vehicle occupants (the eCall
generator); when activated, it provides notification and relevant location information to the most appropriate
PSAP, by means of mobile wireless communications networks and carries a defined standardised MSD,
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 PSAP".
Pan-European eCall effects this service using a ‘Circuit Teleservice’ supported by a ‘Public Land Mobile
Network’ (PLMN) (Teleservice 12/TS12) ETSI TS 122 003 as specified in EN 16062 and EN 16072.

Figure 1 — Relationship of eCall transaction to standards
EN 16102 provides specification for Third party services supporting eCall.
7

---------------------- Page: 9 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
7 Requirements
NOTE The MSD is important information to assist the provision of the most appropriate services to the crash or
emergency site and to speed up the response. The MSD makes it possible for the PSAP operator to respond to the eCall
even without the voice connection.
7.1 Concepts and formats
7.1.1 MSD data concepts
The MSD as defined in EN 15722 is a direct, timely message to the PSAP operator receiving the emergency
call.
7.1.2 Format definition of MSD data concepts
The definitions shown in this Technical Report are defined in EN 15722. Data presentation is to be as
determined in 6.1.4 of EN 15722:2011.
The real position of the element in the data-stream is defined by the ASN1 definition in Annex A of
EN 15722:2011, and enhanced in Annex A of this Technical Report to include the optional HGV/GV data
concept. The representations in this Technical Report are displayed to provide semantic meaning. However,
as data is transferred using ASN.1 ‘Packed Encoding Rules’, elements do not necessarily start or end on a
byte boundary.
The following clauses define the position and definition of the HGV optional additional data concept.
7.1.3 HGV/GV optional additional data concept ‘Object Identifier’
The object identifier uniquely identifies the format and meaning of the data that follows in the optional
additional data concept.
The uniqueness of each specific relative identifier needs to be ensured by a specific international
standardisations body, and maintained in a data registry operated in accordance with EN ISO 24978.
These identifiers are all relative to a specific root that should be agreed in advance. In addition, the root of all
eCall relative OID's must be the same.
Not only the syntax of the data structure should be referenced via this identifier but also the semantic meaning
of the content so that it can be usefully applied.
The user must ensure that the size of this element is restricted to ensure that the total ECallMessage is small
enough for the relevant transmission medium.
Until such a registry is maintained, the OID for the HGV/GV data concept is to be one byte, and assumes that
the OID for main MSD is binary value 00000001, 0000010 for Schema A and binary value 0000011 for
Schema B.
7.1.4 Sequence of MSD data concepts
The sequence of data presentation is to be as specified in 6.2 of EN 15722:2011.
7.1.5 Data presentation of MSD
As specified in EN 15722, the MSD is transmitted using one or more wireless communications media as
defined in EN 16072 which defines one or more ETSI air interface Standards suitable for the transmission of
eCall and EN 16062 (eCall high level application protocols), and is to be presented in Abstract Syntax
8

---------------------- Page: 10 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Notation, ASN.1 ‘Packed Encoding Rules’ (PER unaligned) as defined in ISO/IEC 8825-2 using the ASN.1
definitions defined in Annex A.
The MSD may also be transferred to the PSAP as defined in EN 16102.
NOTE It is assumed that the integrity of the transmitted data is assured by the underlying communication interface
standard used.
7.2 Minimum set of data (MSD)
7.2.1 General
The following sub-clauses provide the definition of an additional eCall HGV/GV data concept that may be sent
as optional additional data within the MSD message from an HGV vehicle in case of an emergency call.
7.2.2 Order of bits and bytes
The message is to be sent in the sequence defined within the ASN.1 definition determined in EN 15722.
7.2.3 Contents of MSD
EN 15722 defines the elements (referred to as ‘Blocks’ in EN 15722) of the MSD data concept.
NOTE The real position and type of the elements in the data stream is defined by the formal ASN1 definition in
Annex A of EN 15722:2011.
The elements of the MSD data concept specified in EN 15722 are:
a) ID (MSD format version);
b) Message identifier;
c) Control;
d) Vehicle identification (WMI/VDS/VIS);
e) Vehicle propulsion storage type;
f) Time stamp;
g) Vehicle location;
h) Vehicle direction;
i) Recent Vehicle Location n-1;
j) Recent Vehicle Location n-2;
k) N° of passengers;
l) Optional additional data.
Further detail of data elements 1 – 11 can be found in EN 15722, including definition of which elements are
mandatory, and which are optional.
9

---------------------- Page: 11 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
7.2.4 MSD ‘Optional additional data’
Table 1 of EN 15722:2011 defines ‘optional additional data’ as:
Table 1 — ‘Optional additional data’ as defined in Table 1 of EN 15722:2011
Block Name Type Unit Description
N°
12 Optional String As  O Further 103 bytes of data encoded
additional specified as in ASN.1 definition.
data
NOTE 1 ASN1 provides already the
indication of whether optional data is
included by simply identifying the
optional additional data field as
OPTIONAL
NOTE 2 Additional data field may
include an address where other relevant
related data or functions are available.
NOTE 3 The framework format of
this field is defined in the ASN1
definition later in this document, which
includes a method to uniquely identify
the exact format of the data and may
also be found in a data registry that is
compliant to EN ISO 24978.

NOTE Except where explicitly specified or determined in a reference standard, negative values are not allowed.
7.3 HGV/GV data concept  General
Bearing in mind that there may also be a requirement for a UN-ECE data concept for HGV/GV data, and it is
uncertain at this stage whether that will be an additional or alternative data concept, the HGV/GV data concept
defined herein is defined to occupy less than 50 bytes of data when transmitted in ASN.1 PER.
The objective of the HGV/GV data concept is to provide the PSAP with data concerning the load of the
affected vehicle transmitting the MSD.
Two variants are provided, one (schema A) for use where dangerous goods (ADR classified); the second
variant (schema B) is for use where no ADR classified load is known.
Paramount priority is given to the transmission of data relating to dangerous/dangerous goods (in most cases
electronically providing a link to the full set of data of the load), although providing the possibility to identify the
goods and a contact telephone number where this is not possible. This data concept is defined as ‘eCall HGV
Schema A’.
Provision is also made in ‘eCall HGV Schema B’ to transfer data concerning other (non ADR) cargos. While
these cargoes may not be classified as dangerous/dangerous, in the event of an accident they may cause
increased risk of accident or problems for the emergency services – for example livestock; small materials
such as ball bearings, liquids, manure or other materials likely to affect the surface tension of the roadway
surface or present obstacles on the roadway.
10

---------------------- Page: 12 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
7.4 eCall HGV/GV data concept definition
7.4.1 eCall HGV Schema A : ADR Goods
The HGV/GV data concept is to semantically comprise the elements specified in Table 2.
Table 2 — Contents/format of the eCall HGV/GV Schema A: ADR goods data concept
Block Name Type Unit Description
N°
12-A0 OID Integer 1 byte M Optional additional data concept identifier
binary value 0000010 identifying HGV
Schema A (until allocated a revised OID from
a central register)
12-A1 ID Integer 1 byte M HGV Schema A data concept format version
set to 1 to discriminate from later HGV
Schema A data concept formats
Later versions to be backwards compatible
with existing versions.
Systems receiving an HGV Schema A data
concept to support all standardised HGV
Schema A data concept versions, which are
each uniquely identified using an HGV
Schema A data concept format version
parameter which will always be contained in
the first byte of all[current and future] HGV
Schema A Data concept versions.
12-A2 Tanker or Octet string  00000000- O The first binary position of the octet to
other vehicle 10001100 indicate whether the affected vehicle is a
type plus (1 Byte) tanker or other type of vehicle where
number of
dangerous 1nnnnnnn = Tanker
Binary
goods on- 0nnnnnnn = Other type of vehicle
board
The remaining 7 binary positions of the octet
to identify the number of types of dangerous
goods being carried

1 - 10 (0000000 – 0001010) = number of
types of dangerous goods present on board
(in binary representation)

0 (0000000) = no dangerous goods on board

12 (0001100) = empty but uncleaned

11 (0001011) = mixed load (unspecified
number of types of dangerous goods present
on-board, but number unknown)

10 (0001010) = 10 or more types of
goods present on-board

0 0000000-
1 0001100

11

---------------------- Page: 13 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Block Name Type Unit Description
N°
Concatenated as octet:

00000000 –
10001100
12-A3 ADR data Octet string As O scheme://domain:port/path?query_string#frag
address URL 35 bytes) specified ment_id

i.e.: The scheme name (commonly called
(information
endpoint) protocol), followed by :// then, depending on
scheme, a domain name (alternatively, IP
address) : a port number, and / the path of the
resource to be fetched or the program to be
run.

If the scheme name is http, the ‘http://’ is
assumed

EXAMPLE
www.example.com/path/to/name
https://example.com/47.35868
telnet://192.0.2.16:80/

The information endpoint to be contacted and
respond in a standardized* way using an
access to a standardized method to retrieve
data,
*the standardized way this is done to be set
elsewhere and is outside of the scope of this
deliverable.
12-A4 Phone Integer (16) As O Consignor contact telephone number or
contact specified telephone number displayed on goods
number container as contact number in case of
emergency.

Countrycode/areacode/number
As :
000 0000 0000000000
Represented as integer
0000000000000000
12-A5 Alarm Octet string  O Any alarm information from on-board sensors
information (pressure, leakage, shock, temperature etc)
(1 Byte)
Binary Flag 0 = no alarm
          1 = alarm
00000000
Binary position
1
L F T S P O R Z

L = Leakage alarm
F = Fire alarm
T = Temperature alarm
S = Shock alarm
12

---------------------- Page: 14 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Block Name Type Unit Description
N°
P = Pressure alarm
O = Orientation alarm
1
R = reserved for future use
   Z = Other alarm
IMPORTANT NOTE: Emergency services
need to be aware that the absence of an alarm
indicates only that there was no alarm showing
as activated at the time of compiling the data.
Alarms raised post the population of/sending of
the MSD will not be transmitted. These codes
therefore only indicate status before or at the
point of the incident, and cannot be taken as
the current status post incident.
12-A6 UN code of Integer (7) 0000 00 0 O Up to 4 materials (most dangerous
hazardous (based on response code), within same
goods response code prioritised to most impact
in fire or largest volume) semantically
identified as:
*1 UN Code;
*2 quantity in tonnes or 1000 cubic
metres ;grossmass/net mass;
*3; packaging group

0000 00 0;
0000 00 0;
0000 00 0;
0000 00 0
as
0000000, 0000000, 0000000, 0000000

No/no more Hazardous goods identified
by
‘0000000’


*1 Issued by UN. May be obtained from
http://live.unece.org/trans/danger/publi/ad
r/adr2011/11contentse.html
or
http://the-
ncec.com/assets/Resources/EAClist2011.pdf

*2 Identify quantity as Gross Mass=1;
Net Mass=2

*3 packaging group
I, 2 or 3 (representing groups I,II,III)
1      I
2      II
3      III

13

---------------------- Page: 15 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Block Name Type Unit Description
N°
12-A6 UN code of Integer (4) 0000 O Up to 10 materials identified by UN ADR
dangerous code, most dangerous listed first (based
goods on response code- same response code
prioritised to most impact in fire or largest
volume) semantically identified as:

0000
0000
0000
0000
0000
0000
0000
0000
0000
0000


No/no more Dangerous goods identified
by
‘0000’

*1 Issued by UN. May be obtained from
http://live.unece.org/trans/danger/publi/ad
r/adr2011/11contentse.html
or
http://the-
ncec.com/assets/Resources/EAClist2011.pdf
M Mandatory data field (the entire eCall HGV/GV data concept is optional, but if presented, M elements are
to be given).
O Optional data field.

14

---------------------- Page: 16 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
7.4.2 eCall HGV Schema B : Other Goods (non ADR)
Table 3 — Contents/format of the eCall HGV/GV Schema B: Other Goods (non ADR)
Block Name Type Unit Description
N°
12-B0 OID Integer 1 M Additional data concept identifier
byte
binary value 0000011 identifying HGV
Schema B (until allocated a revised OID from
a central register)
12-B1 ID Integer 1 M HGV Schema B data concept format version
byte set to 1 to discriminate from later HGV
Schema B data concept formats
Later versions to be backwards compatible
with existing versions.
Systems receiving an HGV Schema B Data
concept to support all standardised HGV
Schema B data concept versions, which are
each uniquely identified using an HGV
Schema B data concept format version
parameter which will always be contained in
the first byte of all [current and future] HGV
Schema B data concept versions.
12-B2 URL address Octet string As O scheme://domain:port/path?query_string#frag
(information 35 bytes) specified ment_id
endpoint)
i.e.: The scheme name (commonly called
Providing
URL protocol), followed by '://' then, depending on
scheme, a domain name (alternatively, IP
address) : a port number, and / the path of the
resource to be fetched or the program to be
run.

If the scheme name is http, the ‘http://’ is
assumed

EXAMPLE
www.example.com/path/to/name
https://example.com/47.35868
telnet://192.0.2.16:80/
The information endpoint to be contacted and
respond in a standardized* way using an
access to a standardized method to retrieve
data,
*the standardized way this is done to be set
elsewhere and is outside of the scope of this
deliverable.
15

---------------------- Page: 17 ----------------------

SIST-TP CEN/TR 16405:2013
CEN/TR 16405:2013 (E)
Block Name Type Unit Description
N°
12-B3 Consignor Integer (16) As O Consignor contact telephone number or
or Operator specified telephone number displayed on goods
phone containe
...