CEN/TS 17363:2019
(Main)Intelligent transport systems - ECall optional additional data - Linked mobile phone number data concept
Intelligent transport systems - ECall optional additional data - Linked mobile phone number data concept
This document defines an eCall "Optional Additional Data" concept for the "Minimum Set of Data" (MSD) to be transferred from a vehicle to a 'Public Safety Answering Point' (PSAP) in the event of a crash or emergency via an 'eCall' communication transaction.
This document defines:
a) Protocol requirements to ensure phone user consent to the provision of the linked 'phone number to the PSAP in the event of an eCall triggering incident;
b) Definition of the OAD concept "Linked mobile Telephone Number" (LTN);
c) Privacy provisions;
d) Advice to PSAPs on the use of the eCall OAD LTN;
e) Example of an in-vehicle sequence generating the LTN OAD and forwarding it as part of the MSD.
For clarity, the communications media protocols and methods for the transmission of the eCall message are not specified in this document.
Intelligente Verkehrssysteme - Optionale zusätzliche eCall-Daten - Datenkonzept für verbundene Mobilfunknummer
Dieses Dokument legt ein Konzept für eCall zu „Optionale zusätzliche Daten“ für den minimalen Datensatz, der von einem Fahrzeug im Fall eines Unfalls oder Notfalls über einen eCall-Kommunikationsvorgang an eine Notrufzentrale übertragen werden soll.
Dieses Dokument legt Folgendes fest:
a) Protokollanforderungen zum Sicherstellen der Benutzerzustimmung zum Bereitstellen der verknüpften Telefonnummer für die Notrufzentrale im Fall eines Vorfalls, bei dem ein eCall ausgelöst wird;
b) Definition des OAD-Konzepts „verknüpfte Mobiltelefonnummer“ (en: Linked mobile Telephone Number, LTN);
c) Datenschutz;
d) Hinweise für Notrufzentralen zur Verwendung der eCall-OAD-LTN;
e) Beispiele für eine bordeigene Sequenz, bei der die LTN-OAD-Daten erzeugt werden und als Teil des minimalen Datensatzes weitergeleitet werden.
Dabei werden die Protokolle des Kommunikationsmediums und Übertragungsmethoden der eCall-Nachricht in diesem Dokument nicht spezifiziert.
Élément introductif - Élément central - Élément complémentaire
Inteligentni transportni sistemi - Izbirni dodatni podatki eKlica - Povezan koncept podatkov o mobilni telefonski številki
Ta dokument določa »izbirni dodatni podatkovni« koncept e-Klica za »minimalni nabor podatkov« (MSD), ki se prenese od vozila do »odzivne točke javne varnosti« (PSAP), če pride do trka ali nujnega primera, prek komunikacijskega prenosa v okviru elektronskega klica v sili.
Ta dokument določa:
a) zahteve protokola za zagotavljanje soglasja telefonskih uporabnikov glede posredovanja povezane telefonske številke centru za usklajevanje reševanja (PSAP) v primeru dogodka, ki sproži e-Klic;
b) definicijo izbirnega dodatnega podatkovnega koncepta »povezana mobilna telefonska številka« (LTN);
c) določbe o zasebnosti;
d) nasvete centrom za usklajevanje reševanja glede uporabe povezane mobilne telefonske številke pri izbirnem dodatnem podatkovnem konceptu e-Klica;
e) primer zaporedja v vozilu, ki generira povezano mobilno telefonsko številko pri izbirnem dodatnem podatkovnem konceptu in jo posreduje kot del minimalnega nabora podatkov.
Komunikacijski medijski protokoli in metode za prenos sporočila elektronskega klica v sili zaradi jasnosti v tem dokumentu niso opredeljeni.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2019
Inteligentni transportni sistemi - Izbirni dodatni podatki eKlica - Povezan koncept
podatkov o mobilni telefonski številki
Intelligent transport systems - ECall optional additional data - Linked mobile phone
number data concept
Intelligente Verkehrssysteme - Optionale zusätzliche eCall-Daten - Verbundenes
Mobilfunknummer Datenkonzept
Élément introductif - Élément central - Élément complémentaire
Ta slovenski standard je istoveten z: CEN/TS 17363:2019
ICS:
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.
CEN/TS 17363
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
August 2019
TECHNISCHE SPEZIFIKATION
ICS 13.200; 35.240.60
English Version
Intelligent transport systems - ECall optional additional
data - Linked mobile phone number data concept
Élément introductif - Élément central - Élément Intelligente Verkehrssysteme - Optionale zusätzliche
complémentaire eCall-Daten - Datenkonzept für verbundene
Mobilfunknummer
This Technical Specification (CEN/TS) was approved by CEN on 21 July 2019 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
© 2019 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17363:2019 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 Conformance . 6
5 Symbols and abbreviated terms . 6
6 Requirements . 7
6.1 General. 7
6.2 Registration and linking of the phone . 7
6.3 Distribution of MSD data . 8
7 Concepts and formats . 8
7.1 MSD data concepts and representation . 8
7.2 Linked phone number optional additional data concept ‘Object Identifier’ . 8
7.3 Linked phone number optional additional data concept ‘data’ . 9
7.4 Contents of the ‘Minimum Set of Data’ (MSD) . 9
8 Privacy provisions . 10
9 Advice to PSAPs on the use of the eCall OAD LTN . 11
Annex A (informative) ASN.1 definition of optional datablock . 12
Annex B (informative) ASN.1 definition of complete MSD message with LTN . 13
Annex C (informative) Example of HMI interaction . 19
Annex D (informative) Example of eCall sequence in car . 21
Bibliography . 22
European foreword
This document (CEN/TS 17363:2019) 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.
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.
Introduction
This document complements EN 15722:2015, Intelligent transport systems — ESafety — ECall minimum
set of data and provides an “Optional Additional Data” concept to be transmitted as part of the MSD
transmission in accordance with EN 15722:2015.
In the event that a vehicle triggers a 112 eCall, the MSD is sent to a “public safety answering point” (PSAP).
The PSAP operator decodes the MSD data (usually, but not necessarily, automatically placed on the
operator's screen). The operator is put in wireless communication (via a mobile phone connection) with
the occupants of the vehicle.
However, sometimes, the operator does not receive any response from the vehicle. This may be due to
one of three reasons:
a) The equipment has failed/has a fault;
b) The occupants are dead, unconscious or otherwise unable to speak;
c) The occupants have left the vehicle and moved to a place of safety (for example behind a crash
barrier or well away from the road [this would often be the advice given by a PSAP in any event]).
NOTE 1 The communications media and means of transferring the eCall MSD are not defined in this document.
See the list of referenced Standards.
As, by this stage, the Minimum Set of Data (MSD) has already been successfully sent; it is usually relatively
easy to detect an in-vehicle system problem (the line has gone totally silent, indicating a dropped call, or
there is some interference noise etc.).
If the line appears to be operational, the responding PSAP has a dilemma. He/she has no way to determine
whether the cause is (b), where it is essential to quickly get emergency response to the scene, or (c), in
which case it may not even be necessary to send an emergency response to the scene.
Based on experience with pre-eCall emergency call systems using cellular telephone links, experience is
that more than 90 % of the time, the reason is (c), but without further information, the PSAP cannot take
that risk and is to send emergency response to the site.
However, current generation vehicles generally now provide the possibility for a 'Bluetooth' link between
the mobile phone of the occupants and the car. Thus, when the registered phone user enters, or is in close
proximity, to the vehicle (usually, but not always, activated when the ignition is turned on) his/her mobile
phone connects via Bluetooth to the vehicle's audio system No information about the user itself, or
her/his phone number is exchanged, as this information is neither known to the mobile phone nor is it
part of any Bluetooth exchange mechanism. That said, the vehicle does know, at any time, which
registered user phones are in or near the vehicle and linked to it at the time of the incident.
If, by means of prior consent, the user who registers his/her phone with the vehicle system enters his/her
phone number, it is possible to provide the PSAP with that phone number as an “Optional Additional
Data” (OAD) concept as part of the MSD.
In the event of a 'silent' call, the PSAP is therefore able to telephone the mobile phone number that was
linked to the vehicle at the time of the incident. It is expected that this will significantly reduce the number
of ‘silent’ calls.
This addition does not enable the vehicle to be tracked or logged in any way other than any other linked
mobile telephone, and, of course, in 112 eCall, the eCall phone connection to the network does not occur
at all until after the event (triggering of eCall).
NOTE 2 This specification provides an optional additional concept as part of the MSD sent to the PSAP, it does
not involve making any direct connection with the telephone number provided, but simply makes that number
available to the PSAP to call if available and required.
This document defines the OAD concept, requirements to ensure the user's consent to the provision of
the linked phone number, any provisions to be made regarding privacy and advice to PSAPs on the use of
the extra information.
1 Scope
This document defines an eCall “Optional Additional Data" concept for the “Minimum Set of Data” (MSD)
to be transferred from a vehicle to a 'Public Safety Answering Point' (PSAP) in the event of a crash or
emergency via an 'eCall' communication transaction.
This document defines:
a) Protocol requirements to ensure phone user consent to the provision of the linked 'phone number
to the PSAP in the event of an eCall triggering incident;
b) Definition of the OAD concept “Linked mobile Telephone Number” (LTN);
c) Privacy provisions;
d) Advice to PSAPs on the use of the eCall OAD LTN;
e) Example of an in-vehicle sequence generating the LTN OAD and forwarding it as part of the MSD.
For clarity, the communications media protocols and methods for the transmission of the eCall message
are not specified in this document.
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:2015, Intelligent transport systems — eSafety — eCall Minimum set of Data
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/IEC 8825 (all parts), Information technology — ASN.1 encoding rules: Specification of Packed Encoding
Rules (PER)
ITU E.123, Notation for national and international telephone numbers, e-mail addresses and web addresses
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
ASN.1/Abstract Syntax Notation 1
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 EN 15722:2015, Annex B.
3.2
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'
3.3
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
3.4
public safety answering point
‘first level’ responder to whom an emergency call/eCall is directed
3.5
(Bluetooth) registered phone
phone that has been registered (via Bluetooth)
3.6
(Bluetooth) linked phone
previously registered phone that is in the near presence of the Bluetooth car kit and linked to it, enabling
bi directional access between the car and
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.