Intelligent Transport Systems - eSafety - eCall Interface for PSAPs to access cargo and dangerous goods databases

Within the context of 112-eCall (operating requirements defined in EN 16072), this document defines specifications for the provision of 112-eCall for regulated commercial vehicles, including rigid body trucks and variants thereof, prime mover and trailer combinations (sometimes called “semi’s”, road trains [one prime mover with multiple trailers]) and other regulated commercial vehicles (for example vans carrying medical supplies or radioactive material).
The work of CEN/TS 16405 is adopted and extended in this document. (A revised version of CEN/TS 16405 will remain the principal reference document for the content and definition of the commercial vehicle optional additional data set).
As with the existing provisions for 112-eCall for Category M1/N1 vehicles, these are specified within the paradigm of being OEM fit equipment supplied with new vehicles.
The scope of this specification is limited to the provision of eCall from a commercial vehicle prime mover /rigid body truck ) designed for conveying cargo. (UNECE Category N).
This document specifies the requirements for the use of 112-eCall  by a commercial vehicle prime mover /rigid body truck and defines the interface between the PSAPs and an external transport database.
Unless superseded by European Regulation at some future date, all data schemas specified herein and defined in a revision of CEN/TS 16405 are “Optional Additional Data” (OAD) concepts, as enabled in accordance with EN 15722:2020 as part of the minimum set of data As OAD they, and the elements within them, are, by definition, “optional” with use at the discretion of the operator of the vehicle.
This document defines how eCall for commercial vehicles is expected to interact with the future eFTI standards and the prerequisites for these standards to allow the access to the relevant freight information for the PSAPSs in case of an eCall.
NOTE 1   The provision of eCall from IVS located within trailers is not included in this document, but could be the subject of a further standards deliverable.
NOTE 2   The provision of eCall for vehicles via the aftermarket (post sale and registration) will be the subject of other work, and in respect of the operational requirements for any such aftermarket solutions for commercial vehicles, will use this document as a principle reference point.
NOTE 3   The 112-eCall paradigm involves a direct call from the vehicle to the most appropriate PSAP (Third party service provision by comparison, involves the support of an intermediary third party service provider before the call is forwarded to the PSAP). The specifications herein relate only to the provision of 112-eCall or IMS-112-eCall, and do not provide specifications for third party service provision of eCall, although in the case of 112-eCall for commercial vehicles, links to third party provision of service aspects (such as cargo contents) could be required.

Intelligente Verkehrssysteme - eSicherheit - eCall Schnittstelle zwischen PSAPS und Gefahrgut- oder Transportdatenbanken

Im Kontext von 112 eCall (in EN 16072 festgelegte Betriebsanforderungen) legt dieses Dokument Spezifikationen für die Bereitstellung von 112 eCall für regulierte Nutzkraftwagen, einschließlich Starrrahmen-Lastwagen und deren Varianten, Kombinationen aus Antriebsmaschine und Anhänger (manchmal als „Sattelschlepper“ bezeichnet, Lastkraftwagenzüge [eine Antriebsmaschine mit mehreren Anhängern]) und andere regulierte Nutzkraftwagen (z. B. Lieferwagen, die medizinische Verbrauchsartikel oder radioaktives Material befördern) fest.
Die Arbeit der CEN/TS 16405 wird in dieser Technischen Spezifikation übernommen und erweitert. (Eine überarbeitete Version der CEN/TS 16405 ist weiterhin das maßgebliche Referenzdokument für Inhalt und Festlegung des optionalen ergänzenden Datensatzes des Nutzkraftwagens.)
Wie bei den bereits bestehenden Bestimmungen zu 112 eCall für Fahrzeuge der Kategorie M1/N1 werden diese innerhalb des Paradigmas spezifiziert, dass es sich um eine Ausrüstung handelt, die vom Originalfahrzeughersteller in Neufahrzeuge eingebaut wird.
Der Anwendungsbereich dieser Spezifikation beschränkt sich auf die Bereitstellung von eCall bei einer Nutzkraftwagen-Antriebsmaschine / einem Starrrahmen-Lastwagen zur Beförderung von Ladung. (UNECE Kategorie N).
Dieses Dokument legt die Anforderungen an die Nutzung des 112 eCall durch eine Nutzkraftwagen-Antriebsmaschine / einen Starrahmen-Lastwagen und die Schnittstellen zwischen Notrufzentralen und einer externen Transport-Datenbank fest.
Sofern sie nicht durch eine spätere Europäische Verordnung außer Kraft gesetzt werden, sind alle hierin angegebenen und in einer Überarbeitung von CEN/TS 16405 festgelegten Datenschemata „optionale zusätzliche Daten“ (OAD, en: Optional Additional Data) in Übereinstimmung mit EN 15722:2020 als Teil des Mindestdatensatzes. Als OAD sind diese Schemata und die darin enthaltenen Elemente per Darstellung „optional“ mit Anwendung nach Ermessen des Fahrzeugbedieners.
Dieses Dokument legt fest, wie der eCall für Nutzfahrzeuge erwartungsgemäß mit den zukünftigen eFTI Normen interagieren soll, und die Voraussetzungen für diese Normen, um den Zugang zu relevanten Frachtinformationen für Notrufzentralen im Fall eines eCalls zu erlauben.
ANMERKUNG 1   Die Bereitstellung des eCall durch IVS in Anhängern ist nicht in diesem Dokument enthalten, könnte aber Gegenstand einer zukünftigen Normen-Zielsetzung sein.
ANMERKUNG 2   Die Bereitstellung von eCall für Fahrzeuge über den Nachrüstmarkt (nach Verkauf und Zulassung) wird den Gegenstand einer anderen Arbeit bilden, die im Hinblick auf die betrieblichen Anforderungen für derartige Nachrüstlösungen für Nutzkraftwagen dieses Dokument als Hauptanhaltspunkt verwenden wird.
ANMERKUNG 3   Das 112 eCall-Paradigma beinhaltet einen direkten Anruf von dem Fahrzeug an die am besten geeignete Notrufzentrale (Drittanbieter-Dienstleistung durch Vergleich, beinhaltet die Unterstützung eines zwischengeschalteten Drittanbieter-Dienstleisters, bevor der Anruf an die Notrufzentrale weitergeleitet wird). Die hierin enthaltenen Spezifikationen beziehen sich nur auf die Bereitstellung von 112 eCall oder IMS 112 eCall und bieten keine Spezifikationen für die Erbringung von eCall-Dienstleistungen durch Dritte, obwohl im Fall von 112 eCall für Nutzkraftwagen die Verknüpfung mit der Bereitstellung von Dienstleistungsaspekten (wie z. B. Ladungsinhalte) durch Dritte erforderlich sein könnte.

Systèmes de transport intelligents - eSafety - Interface eCall entre PSAPS et bases de données sur le fret et les marchandises dangereuses

Inteligentni transportni sistemi - e-Varnost - Vmesnik elektronskega klica v sili za center za usklajevanje reševanja (PSAP) za dostop do zbirk podatkov o tovoru in nevarnem blagu

General Information

Status
Published
Publication Date
30-Aug-2021
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
17-Aug-2021
Due Date
22-Oct-2021
Completion Date
31-Aug-2021

Buy Standard

Technical specification
SIST-TS CEN/TS 17642:2021 - BARVE na PDF-str 12,15,18,19,20,22,23
English language
25 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 17642:2021
01-oktober-2021

Inteligentni transportni sistemi - e-Varnost - Vmesnik elektronskega klica v sili za

center za usklajevanje reševanja (PSAP) za dostop do zbirk podatkov o tovoru in
nevarnem blagu

Intelligent Transport Systems - eSafety - eCall Interface for PSAPs to access cargo and

dangerous goods databases

Intelligente Verkehrssysteme - eSicherheit - eCall Schnittstelle zwischen PSAPS und

Gefahrgut- oder Transportdatenbanken

Systèmes de transport intelligents - eSafety - Interface eCall entre PSAPS et bases de

données sur le fret et les marchandises dangereuses
Ta slovenski standard je istoveten z: CEN/TS 17642:2021
ICS:
13.300 Varstvo pred nevarnimi Protection against dangerous
izdelki goods
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST-TS CEN/TS 17642:2021 en,fr,de

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

---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 17642:2021
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
August 2021
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version
Intelligent Transport Systems - eSafety - eCall Interface for
PSAPs to access cargo and dangerous goods databases

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

eCall entre PSAPS et bases de données sur le fret et les Schnittstelle zwischen PSAPS und Gefahrgut- oder

marchandises dangereuses Transportdatenbanken

This Technical Specification (CEN/TS) was approved by CEN on 23 May 2021 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two 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 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, 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

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

© 2021 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17642:2021 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
Contents Page

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

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

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

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

3 Terms and definitions ......................................................................................................................... 6

4 Symbols and abbreviations ............................................................................................................... 8

5 Conformance ........................................................................................................................................... 9

6 General overview ................................................................................................................................ 10

7 Exchange of data .................................................................................................................................. 11

7.1 General.................................................................................................................................................... 11

7.2 The basic standard CEN/TS 16405:2017 .................................................................................... 11

7.3 Available approaches to encode and exchange data .............................................................. 12

7.3.1 General.................................................................................................................................................... 12

7.3.2 eFTI .......................................................................................................................................................... 12

7.3.3 EUCARIS .................................................................................................................................................. 13

7.3.4 UN/CEFACT ............................................................................................................................................ 14

7.4 Envisaged configurations ................................................................................................................. 16

7.4.1 General.................................................................................................................................................... 16

7.4.2 CEN/TS 16405:2017 with EUCARIS .............................................................................................. 16

7.4.3 CEN/TS 16405:2017 with eFTI ....................................................................................................... 17

7.4.4 CEN/TS 16405:2017 with EUCARIS and eFTI combined ....................................................... 18

8 Standards to be updated .................................................................................................................. 18

9 Privacy considerations ..................................................................................................................... 18

Annex A (informative) The electronic Freight Transport Information regulation .................. 19

Annex B (informative) UN/CEFACT XML Encoding .............................................................................. 22

Bibliography ....................................................................................................................................................... 25

---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
European foreword

This document (CEN/TS 17642:2021) has been prepared by Technical Committee CEN/TC 278

“Intelligent Transport Systems”, 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.

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 announce this Technical Specification: 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 the United

Kingdom.
---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
Introduction

This document is a companion document to CEN/TS 16405, Intelligent transport systems - eCall -

Additional data concept specification for heavy goods vehicles.

eCall (an emergency call generated either automatically via activation of in-vehicle sensors or manually

by the vehicle occupants; which, when activated provides notification and relevant location information

to the most appropriate Public Safety Answering Point, by means of mobile wireless communications

networks, and carrying a defined standardized minimum set of data (MSD) notifying that there has been

an incident), as defined in EN 16072, EN 16062, EN 15722, and EN 16454, became a regulated

requirement (for new model vehicles of Category M1 and N1 [cars and light vans]) under European

regulation as from April 2018.

As a system, eCall is not limited to vehicles of named categories and application in other categories are

foreseen and actively supported by additional standards. One of these is CEN/TS 16405 which focuses on

implementing eCall in commercial vehicles (Category N2 and N3), both highlighting triggering issues and

offering means to include cargo related information inside the MSD. Named standard contains a so called

additional data concept that allows for properly defined information elements being inserted in the MSD.

The so called ‘Schema A’ defines means to have information about the cargo directly inside the MSD,

Schema B (also part of CEN/TS 16405) offers a mechanism to inform the PSAP about where and how to

retrieve information of the cargo from a remote source. The underlying document focuses on this last

Schema.

When a PSAP receives an eCall from a vehicle, the PSAP system will “intercept” the MSD and decode its

contents for further use in the emergency process. As long as the information can be used directly (e.g.

number of occupants, direction of travel, last known location) this can be displayed to the operator.

However, the MSD does contain elements of data that trigger a lookup of information. The basic MSD

contains the VIN number that should be looked up using EUCARIS to get the most up to date vehicle

registration information. If the MSD contains additional data, the PSAP system needs to apply the correct

decoding template which results in either directly usable information (like the cargo information in

Schema A) or information that again triggers a lookup, or both.

As previously mentioned, CEN/TS 16405 Schema B offers means to inform the PSAP about how and

where to retrieve the cargo information, but this was purposely left flexible. There is however a need, or

at least a strong wish, to standardize the way cargo information can be retrieved from a remote source.

This document addresses this need.

The European Commission has launched a legislative process to harmonize the electronic freight

transport information (eFTI) and to provide the legislative framework and a basic architecture for the

exchange of freight transport information. The access of PSAPs to freight information as the information

about the loaded dangerous goods should follow the future eFTI standards to avoid the handling of

several interfaces of authorities to freight data.

The goal of this document is to prepare the eCall interfaces for the new eFTI standards and define

prerequisites for the eFTI standards that need to be fulfilled by eFTI to allow the access to the necessary

information for eCall.
---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
1 Scope

Within the context of 112-eCall (operating requirements defined in EN 16072), this document defines

specifications for the provision of 112-eCall for regulated commercial vehicles, including rigid body trucks

and variants thereof, prime mover and trailer combinations (sometimes called “semi’s”, road trains [one

prime mover with multiple trailers]) and other regulated commercial vehicles (for example vans carrying

medical supplies or radioactive material).

The work of CEN/TS 16405 is adopted and extended in this document. (A revised version of

CEN/TS 16405 will remain the principal reference document for the content and definition of the

commercial vehicle optional additional data set).

As with the existing provisions for 112-eCall for Category M1/N1 vehicles, these are specified within the

paradigm of being OEM fit equipment supplied with new vehicles.

The scope of this specification is limited to the provision of eCall from a commercial vehicle prime mover

/rigid body truck) designed for conveying cargo. (UNECE Category N).

This document specifies the requirements for the use of 112-eCall by a commercial vehicle prime mover

/rigid body truck and defines the interface between the PSAPs and an external transport database.

Unless superseded by European Regulation at some future date, all data schemas specified herein and

defined in a revision of CEN/TS 16405 are “Optional Additional Data” (OAD) concepts, as enabled in

accordance with EN 15722:2020 as part of the minimum set of data As OAD they, and the elements within

them, are, by definition, “optional” with use at the discretion of the operator of the vehicle.

This document defines how eCall for commercial vehicles is expected to interact with the future eFTI

standards and the prerequisites for these standards to allow the access to the relevant freight information

for the PSAPSs in case of an eCall.

NOTE 1 The provision of eCall from IVS located within trailers is not included in this document, but could be the

subject of a further standards deliverable.

NOTE 2 The provision of eCall for vehicles via the aftermarket (post sale and registration) will be the subject of

other work, and in respect of the operational requirements for any such aftermarket solutions for commercial

vehicles, will use this document as a principle reference point.

NOTE 3 The 112-eCall paradigm involves a direct call from the vehicle to the most appropriate PSAP (third party

service provision by comparison, involves the support of an intermediary third party service provider before the

call is forwarded to the PSAP). The specifications herein relate only to the provision of 112-eCall or IMS-112-eCall,

and do not provide specifications for third party service provision of eCall, although in the case of 112-eCall for

commercial vehicles, links to third party provision of service aspects (such as cargo contents) could be required.

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:2020, Intelligent transport systems - ESafety - ECall minimum set of data

EN 16072:2015, Intelligent transport systems - ESafety - Pan-European eCall operating requirements

EN 16062:2015, Intelligent transport systems - ESafety - eCall high level application requirements (HLAP)

using GSM/UMTS circuit switched networks

EN 16454:2015, Intelligent transport systems - ESafety - ECall end to end conformance testing

---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)

CEN/TS 16405:2017, Intelligent transport systems - Ecall - Additional data concept specification for heavy

goods vehicles

CEN/TS 17240:2018, Intelligent transport systems - ESafety - ECall end to end conformance testing for IMS

packet switched based systems
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:

— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/
3.1
112-eCall

‘eCall’ provided by a ‘Teleservice 12’ mobile communication network, as defined in EN 16072:2015 and

EN 16062:2015 or CEN/TS 17184
3.2
Agreement concerning the International Carriage of Dangerous Goods by Road
ADR

European agreement concerning the international carriage of dangerous goods by road

Note 1 to entry: The French name is Accord Européen Relatif Au Transport International Des Marchandises

Dangereuses Par Route (ADR).
3.3
CAN-BUS

data-bus standard for vehicles designed to allow microcontrollers and devices to communicate with each

other in applications without a host computer
3.4
commercial vehicle

mechanically propelled road vehicle (vehicle type 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 laden on a road

Note 1 to entry: This includes vehicles designed or adapted to have a maximum weight exceeding 3 500 tonnes,

but explicitly excludes busses or other vehicles designed and constructed for the carriage of passengers (i.e. vehicle

types M1, M2 or M3).
Note 2 to entry: See also 3.16 Regulated Commercial Vehicle.
3.5
dangerous goods

categories of goods carried by road as stated in the ‘Agreement concerning the International Carriage of

Dangerous Goods by Road’ (ADR) as dangerous; these are characterized as articles or substances which

are capable of posing a significant risk to health, safety or to property when transported

Note 1 to entry: The exact categories can be found in the ‘Agreement concerning the International Carriage of

Dangerous Goods by Road’ (ADR).
---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
3.6
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 '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 establishes an audio channel between the occupants

of the vehicle and the most appropriate 'Public Safety Answering Point' (EN 16072:2015)

3.7
e-CMR

electronic CMR (Convention on the Contract for the International Carriage of Goods by Road)

Note 1 to entry: The French title is Convention relative au contrat de transport international de Marchandises par

Route.
3.8
electronic freight transport information
eFTI

initiative of the European Commission to establish a European platform that allows authorities to get

access to freight transport information
3.9
In-vehicle system
IVS

in-vehicle equipment together with the means to trigger, manage and effect the eCall transaction

3.10
journey

leg of a trip (a trip comprises one or more journeys), which starts when the vehicle is powered up (ignition

on in the case of a hydrocarbon driven vehicle, other action in the case of electric, hybrid and stop-start

technology vehicles) and ends when the vehicle is next powered down
3.11
minimum set of data
MSD

standardized data concept comprising data elements of relevant vehicle generated data essential for the

performance of the eCall service, as defined in EN 15722
3.12
optional additional data
OAD

presentation of additional data concept(s) within an MSD message, to further assist the PSAP to respond

appropriately; such data is always optionally presented

EXAMPLE Additional data can contain a reference to an external source of relevant information (such as a

phone number, a website URL, etc. where further information can be found, or additional data specific to the vehicle

or incident [e.g. battery temperature in the case of an electric vehicle, URL of wiring diagram in case of electric

vehicle/hybrid vehicle, cargo information of an HGV or URL to obtain such data]).

---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
3.13
Original Equipment Manufacturer
OEM

entity which first assembles the vehicle and provides eCall equipment as part of its specification and

subsequently sells the vehicle directly or via an agent
3.14
Public Safety Answering Point
PSAP

physical location working on behalf of the national authorities where emergency calls are first received

under the responsibility of a public authority or a private organization recognized by the national

government
3.15
prime mover

vehicle with engine, not prepared for carrying load, but to be used for towing trailer(s)

3.16
regulated commercial vehicle

commercial vehicle transporting goods covered by ADR regulations or other regulatory controls imposed

by the administration
3.17
rigid body truck

single chassis automotive vehicle designed primarily for the transportation of goods

3.18
road train

equipage consisting of vehicle (rigid body truck / prime mover) and more than one trailer

3.19
trip

movement from one location to another (usually, but not always, to a plan or schedule); and which may

comprise one or more legs (called ‘journeys’)
Note 1 to entry: A ‘return trip’ ends at the same location that it started.
4 Symbols and abbreviations
ADR Agreement concerning the International Carriage of Dangerous Goods by Road
(dangerous goods)
CCn Commercial Cargo (sequential reference number)
CAN Controller Area Network
CAN-BUS Controller Area Network Bus
CEF Connecting Europe Facility
CEN European Committee for Standardization (Comité Européen de Normalisation)
EC European Commission

e-CMR electronic version of a CMR (Convention on the Contract for the International

Carriage of Goods by Road)
---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
eFTI electronic Freight Transport Information
EN European Standard
EO Economic Operator
EUCARIS European CAR and driving licence Information System
GSM Global System Mobile (communications)
HGV Heavy Goods Vehicle
IMS IP-Multimedia Subsystem
IP Internet Protocol
ITC Inland Transport Committee (UNECE)
ITS Intelligent Transport Systems
IVS In-Vehicle System
MSD Minimum Set of Data
NA National Authority
NEN Nederlands Normalisatie-Instituut
OAD Optional Additional Data
OEM Original Equipment Manufacturer
OID ISO object identifier
PSAP Public Safety Answering Point
TPS Third Party Service
TR Technical Report
TS Technical Specification
UMTS Universal Mobile Telecommunications System
UNECE United Nations Economic Commission for Europe
UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business
UPER Unaligned Packed Encoding Rules
URL Uniform Resource Locator
VIN Vehicle Identification Number
5 Conformance

Conformance to the requirements of this document's Deliverable for eCall for heavy goods vehicles and

other commercial vehicles is met by conformance to EN 16454:2015 or CEN/TS 17240:2018 and by

validation of the selected OAD variant complying to the provisions of CEN/TS 16405:2017 and being

successfully parsed through an ASN.1 compiler.

This document makes no conformance specifications or requirements in respect of TPS eCall operating

requirements. TPS eCall specifications and requirements can be found in EN 16102 and EN 16454:2015.

---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
6 General overview

Following EN 15722 an eCall MSD can optionally contain additional data that shall be decoded using an

ASN.1 decoding recipe referenced by the so called OID data element. After decoding the receiving system

can use that additional data in the emergency process. The inclusion of cargo related data are supported

by CEN/TS 16405:2017 which contains two Schema’s for additional data: Schema A and Schema B.

Schema A includes all data in the MSD. If Schema B is used, the receiving system receives data elements

that can be used to retrieve data from a remote source. The relevant data elements are in Figure 1.

Figure 1 — The relevant data elements

The envisaged mode of operation is that a receiving system uses the endpointProtocol-identifier to

determine how and where to get the cargo information and how the retrieved information is encoded.

The endpointParameters contain the parameters necessary to do the retrieval. Amongst the parameters

can be: a URI (if the protocol does not use a fixed URI), a key specific for the vehicle and any other

parameters needed. The proposed mechanism offers a very flexible way of disclosing cargo information

in an emergency situation. Pretty much every freight/cargo information system used by transport

companies to manage their transports, that complies with the requirements specified in this document,

can be used to offer the data, as long as any PSAP system is able to reach the information end point and

has the correct procedures implemented.

The harsh reality is that most emergency services have systems that are not able to freely connect to

every system and not every transport company wants to open up their systems to anyone. Also, the

burden for both PSAP system developers as those of transport management systems (TMS) to reinvent

the wheel over and over again is considered counterproductive. This document offers the means to

standardize parts of the information exchange process, without limiting the flexibility offered by

CEN/TS 16405:2017.

Addressing the retrieval of cargo information, three elements can be identified that are open to

standardization: the cargo information end point itself (i.e. a more or less central source of information),

the way the PSAP connects to the end point (i.e. the connect and exchange mechanism) and, thirdly, the

way the data are coded and should be decoded. This document offers a standardized approach for the

latter two, and includes a suggestion for the first, whilst using existing solutions.

---------------------- Page: 12 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
7 Exchange of data
7.1 General

In order to be able to receive accurate information about the loaded goods the PSAP needs the actual and

relevant information about the current freight transport that activated the eCall.

The European Commission has launched a legislative process to harmonize the electronic freight

transport information (eFTI) and to provide the legislative framework and a basic architecture for the

exchange of freight transport information. This specification also serves as a list of eCall requirements

and specification to be taken into account when preparing the technical specifications for eFTI

(see Annex A).

Within the eCall paradigm CEN/TS 16405:2017 lays down the specification to embed cargo related

information in the data packet sent as part of the Minimum Set of Data.
7.2 The basic standard CEN/TS 16405:2017

CEN/TS 16405:2017 uses the optional additional data concept that is part of the eCall MSD as

standardized in EN 15722 to include cargo related data. The PSAP receives and can decode this

information, to cover the requirements expressed in point 3 of the previous paragraph.

Two schemas are defined in CEN/TS 16405:2017 for that purpose: A and B. Schema A is designed to

include cargo information directly in the MSD. As a result of the limited space available, the information

itself is limited as well. However, Schema A has some advantages like the immediate availability of

information to the emergency process and its applicability to fixed transports.

Schema B lessens the need for alterations to the implementation in the vehicles by offering the

information from a remote source (i.e. not the vehicle itself). The optional additional data part of the MSD

contains information for a receiving system to retrieve the cargo information from that source:

endpointProtocolID and endpointParameters.

The endpointProtocolID serves as an identification that can (programmatically) be used to know where

to retrieve the data, how the endpointParameters fit into the retrieval process and how the received data

shall be decoded. As an example:
From the MSD
endpointProtocolID 31.5
endpointParameters V = 2415;K = 68ef8998–1e15–4189–8466–497b2039bbe4
---------------------- Page: 13 ----------------------
SIST-TS CEN/TS 17642:2021
CEN/TS 17642:2021 (E)
From the “library”
endpontProtocolID 31.5
retrieval method HTTP POST
- base URI https://nl.cargo.info/eCallRequest
- GET parameters -
- POST parameters * vehicle = endpointParameters.V
* key = endpointParameter.K
* vin = VIN
- request body (empty)
encoding of response XML
- XSD https://nl.cargo.info/xsd/encoding.xsd
NOTE The URLs are only examples and do not link to anything existing.

With the library information already implemented, the PSAP system can use the information from the

MSD to (a) determine which implemented profile to use, (b) embed the parameters from the MSD into

the request, (c) obtain and decode the data and (d) present the data to the operator and send it through

to the emergency services.
7.3 Available approaches to encode and exchange data
7.3.1 General

The aim of this specification is designed to (re)use existing approaches for both encoding and exchanging

of (cargo) data (in order to limit the amount of time and money needed to implement the standard with

all st
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.