Intelligent transport systems - ECall - Operating requirements for third party support

The objective of implementing a 'Third Party' emergency call is to provide emergency assistance and an automated notification of a traffic accident, using 'Third Party Services' packages where such services are supported between the vehicle and a Third Party Service Provider in countries where such notification of an emergency are supported by PSAPs. The first objective of this TPS-eCall is to transfer an emergency message from a vehicle to a Third Party Service Provider (TPSP) in the event of a crash or an emergency, and to establish a voice channel between the in-vehicle equipment and the TPSP. The second objective of this TPS-eCall is, in case of an emergency likely to require assistance from the emergency services, for the TPSP to transfer an emergency message including the data of the Minimum Set of Data (MSD) (as defined in EN 15722) from the TPSP to the most appropriate PSAP and to make best efforts to establish a direct voice contact between that PSAP and the occupants of the vehicle if required by the PSAP. This European Standard specifies the general operating requirements and intrinsic procedures for an invehicle eCall via the services of a Third Party Service Provider (TPSP). This European Standard also provides definition of the service(s) provided to the PSAP and the method and form of service delivery.

Intelligente Verkehrssysteme - ECall - Betriebsanforderungen für den TPS eCall

Das Ziel der Implementierung des Drittparteien-Notrufs (TPS-eCall) besteht darin, Nothilfe zu leisten sowie die automatische Benachrichtigung über einen Verkehrsunfall mit Hilfe von Dritten angebotenen Dienstpake¬ten in Ländern, in denen derartige Dienste von den PSAPs unterstützt werden, sofern die¬se Benachrichtigungen zwischen dem betroffenen Fahrzeug und einem Fremddienstleister unterstützt werden.
Das erste Ziel von „TPS-eCalls“ besteht darin, im Falle eines Unfalls oder einer sonstigen Notsituation eine entsprechende Notfallmeldung vom betroffenen Fahrzeug an einen Fremddienstleister (TPSP) zu senden und einen Sprachkanal zwischen der bordeigenen Ausrüstung und dem TPSP einzurichten.
Das zweite Ziel dieser TPS-eCalls besteht darin, dass der TPSP im Falle einer Notsituation, die wahrschein¬lich einen Rettungseinsatz erfordert, eine entsprechende Notfallmeldung einschließlich der Daten des „Mini¬malen Datensatzes“ (en: Minimum Set of Data, MSD) (nach den Festlegungen in EN 15722) an die zuständige PSAP überträgt und alle vertretbaren Anstrengungen unternimmt, um eine direkte Sprachverbindung zwischen dieser PSAP und den Insassen des betroffenen Fahrzeugs herzustellen, sofern dies von der PSAP gefordert wird.
Diese Europäische Norm legt die allgemeinen Betriebsanforderungen und intrinsischen Verfahren für den bordeigenen über die Dienste eines Fremddienstleisters erfolgenden eCall fest.
Diese Europäische Norm legt auch den oder die der PSAP zur Verfügung gestellten Dienst(e) und das Verfahren und die Form dieser Diensterbringung fest.
ANMERKUNG   Ein wichtiger Bestandteil des TPS-eCalls ist der „Minimale Datensatz“ (MSD). In dieser Europäischen Norm sind die Betriebsanforderungen für den MSD, nicht aber seine Form und sein Dateninhalt festgelegt. Ein gemeinsamer Europäischer MSD für eCall ist in EN 15722 festgelegt. Es können auch zusätzliche Datenkonzepte übertragen werden, und es wird empfohlen, derartige Datenkonzepte unter Nutzung eines Datenverzeichnisses nach den Festlegungen in EN ISO 24978 zu registrieren, um sicherzustellen, dass sie vom Empfänger verstanden werden können.

Systèmes de transport intelligents - ECall - Exigences opérationnelles des services eCall de fournisseurs privés

La mise en œuvre d’un appel d’urgence de fournisseur privé a pour objectif d’assurer l’assistance et l’alerte automatique en cas d’accident de la route, grâce aux services d’urgence de fournisseurs privés lorsque ces services sont assurés entre le véhicule et un « Fournisseur de service privé » dans les pays où ces services sont pris en charge par les PSAPs. Ceci fournit un autre moyen d’assurer le service d’eCall par rapport à l’eCall paneuropéen défini dans l’EN 16072 (Systèmes de transport intelligent — eSafety — eCall paneuropéen - Exigences de fonctionnement).
Le premier objectif de ce « SFP-eCall » est de transmettre un message d’urgence d’un véhicule à un « Fournisseur de service privé » (TPSP) dans l’éventualité d’un crash ou d’une situation d’urgence, et d’établir une liaison téléphonique entre l’équipement à bord du véhicule et le TPSP.
Le deuxième objectif de ce « SFP-eCall », dans le cas d’une situation d’urgence susceptible de nécessiter du secours, est que le TPSP transmette un message d’urgence comprenant les données de l’ « Ensemble minimal de données » (MSD) (défini dans l’EN 15722 {Systèmes intelligents de transport -  eSafety - ’eCall’ ensemble minimal de données}) au PSAP le plus approprié et qu’il s’efforce d’établir un contact vocal direct entre ce PSAP et les occupants du véhicule, si le PSAP le demande.
La présente norme européenne définit les exigences générales de fonctionnement et les procédures correspondantes applicables à un eCall à bord du véhicule assuré par les services d’un fournisseur de service privé.
La présente norme fournit également la définition du ou des services assurés par le PSAP ainsi que la méthode et le mode de la prestation de service.
NOTE   Une part importante du SFP-eCall est constituée par un « ensemble minimal de données » (MSD). Les exigences de fonctionnement d’un MSD sont déterminées dans la présente Nome européenne, mais la forme et le contenu des données du MSD n’y sont pas définis.

Inteligentni transportni sistemi - Elektronski klic v sili - Operativne zahteve za podporo tretje stranke

Cilj izvajanja elektronskega klica v sili »tretje stranke« je zagotoviti nujno pomoč in samodejno obveščanje o prometni nesreči s svežnji »storitev tretje stranke«, kadar take storitve podpirata vozilo in izvajalec storitev tretje stranke v državah, v katerih taka obvestila o nujnih primerih podpirajo odzivne točke javne varnosti (PSAP). Glavni cilj elektronskega klica v sili storitve tretje stranke je prenesti sporočilo klica v sili iz vozila do izvajalca storitev tretje stranke (TPSP) ob nesreči ali nujnem dogodku ter vzpostaviti glasovni kanal med opremo v vozilu in izvajalcem storitev tretje stranke. Drugi cilj elektronskega klica v sili storitve tretje stranke je, da v primeru nujnega dogodka, zaradi katerega bodo verjetno morale posredovati intervencijske službe, izvajalec storitev tretje stranke prenese sporočilo klica v sili z vsemi podatki minimalnega nabora podatkov (MSD) (kakor je opredeljeno v standardu EN 15722) od izvajalca storitev tretje stranke do najustreznejše odzivne točke javne varnosti in si čim bolj prizadeva za vzpostavitev neposrednega glasovnega stika med to odzivno točko javne varnosti in potniki v vozilu, če tako zahteva odzivna točka javne varnosti. Ta evropski standard določa splošne operativne zahteve in notranje postopke za elektronski klic v sili iz vozila prek storitev izvajalca storitev tretje stranke. Ta evropski standard določa tudi definicijo storitev, ki se zagotavljajo za odzivno točko javne varnosti, ter metodo in obliko izvajanja storitve.

General Information

Status
Published
Public Enquiry End Date
30-Jun-2010
Publication Date
10-Jan-2012
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
30-Dec-2011
Due Date
05-Mar-2012
Completion Date
11-Jan-2012

Buy Standard

Standard
SIST EN 16102:2012
English language
53 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentni transportni sistemi - Elektronski klic v sili - Operativne zahteve za podporo tretje strankeIntelligente Verkehrssysteme - ECall - Betriebsanforderungen für den TPS eCallSystèmes de transport intelligents - ECall - Exigences opérationnelles des services eCall de fournisseurs privésIntelligent transport systems - ECall - Operating requirements for third party support43.040.15Car informatics. On board computer systems35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and trade13.200NDWDVWURIAccident and disaster controlICS:Ta slovenski standard je istoveten z:EN 16102:2011SIST EN 16102:2012en01-februar-2012SIST EN 16102:2012SLOVENSKI

STANDARD
SIST EN 16102:2012
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16102
December 2011 ICS 35.240.60 English Version

Intelligent transport systems - eCall - Operating requirements for third party support

Systèmes de transport intelligents - eCall - Exigences opérationnelles des services eCall de fournisseurs privés

Intelligente Verkehrssysteme - Notruf - Betriebsanforderungen für die Notruf-Unterstützung durch Dritte This European Standard was approved by CEN on 22 October 2011.

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, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland 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 © 2011 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 16102:2011: ESIST EN 16102:2012

EN 16102:2011 (E) 2 Contents Page FOREWORD .........................................................................................................................................................4INTRODUCTION ..................................................................................................................................................51SCOPE ....................................................................................................................................................62NORMATIVE REFERENCES ..................................................................................................................63TERMS AND DEFINITIONS ....................................................................................................................64SYMBOLS AND ABBREVIATED TERMS .......................................................................................... 105HIGH LEVEL FUNCTIONAL REQUIREMENTS .................................................................................. 115.1General high level functional requirements ..................................................................................... 115.2TPS-eCall generic architecture .......................................................................................................... 125.3TPS-eCall operation sequence .......................................................................................................... 125.4Privacy aspects ................................................................................................................................... 136TRANSMISSION FROM VEHICLE ASPECTS .................................................................................... 136.1General requirements for the transmission from vehicle .............................................................. 136.2Dual-channel transmission ................................................................................................................ 146.3Performance of the transmission ...................................................................................................... 146.3.1Performance criteria for the TPS-eCall service chain ..................................................................... 146.3.2Performance criteria for additional data .......................................................................................... 146.4Routing of a TPS-eCall ....................................................................................................................... 146.5Call back to vehicle ............................................................................................................................ 146.6Termination of the voice call ............................................................................................................. 146.7Prioritisation of a TPS-eCall .............................................................................................................. 146.8Failure situations ................................................................................................................................ 157DATA .................................................................................................................................................... 157.1Generic requirements for TPS-eCall data ........................................................................................ 157.2Location data ....................................................................................................................................... 157.2.1Generic requirements for location data ........................................................................................... 157.2.2Insufficient data provided by the GNSS system .............................................................................. 157.2.3Vehicle location................................................................................................................................... 167.3Optional additional data ..................................................................................................................... 167.4Data to transmit to PSAP: TPS-eCall set of data ............................................................................. 167.4.1General ................................................................................................................................................. 167.4.2TPS-eCall-UID definition .................................................................................................................... 177.4.3TPS-eCall-SID definition ..................................................................................................................... 178TPS IN-VEHICLE SYSTEM REQUIREMENTS ................................................................................... 178.1General TPS-IVS requirements .......................................................................................................... 178.2Modes of operation ............................................................................................................................. 178.3Triggering ............................................................................................................................................ 188.3.1Triggering overview ............................................................................................................................ 188.3.2Automatic triggering strategy ........................................................................................................... 188.3.3Manual triggering strategy ................................................................................................................. 188.4Termination of an in progress TPS-eCall ......................................................................................... 188.5Set-up of the voice call ....................................................................................................................... 188.6Call back function ............................................................................................................................... 198.7Automatic voice call retry .................................................................................................................. 198.8Post crash performance of TPS in-vehicle equipment ................................................................... 198.9Energy supply ..................................................................................................................................... 208.10In-vehicle Human Machine Interface (HMI) aspects ........................................................................ 20SIST EN 16102:2012

EN 16102:2011 (E) 3 8.10.1General ................................................................................................................................................. 208.10.2HMI aspects in the case of manual triggering .................................................................................. 208.10.3Alert of the vehicle occupants (automatically or manually triggered) ........................................... 208.11Antenna ................................................................................................................................................ 209SERVICE PROVIDER ........................................................................................................................... 219.1Generic TPSP requirements ............................................................................................................... 219.2Operators.............................................................................................................................................. 219.3Automatic Call Distribution ................................................................................................................ 219.4Map accuracy at TPSP ........................................................................................................................ 219.5Test of the data link between the carrier delivering the ‘IVS dataset’ and the ‘TPSP eCall receiver’ ................................................................................................................................................ 219.6Answering time .................................................................................................................................... 219.7Reception of data without voice call ................................................................................................. 219.8Procedures for answering the voice calls ........................................................................................ 229.9Notifying the emergency services for their intervention ................................................................. 229.10Linguistic aspects ............................................................................................................................... 229.11TPSP call back number ....................................................................................................................... 229.12Filing ..................................................................................................................................................... 239.13Backup systems .................................................................................................................................. 239.14Availability of the technical chain ...................................................................................................... 239.15Technical quality management procedures ..................................................................................... 2310TRANSMISSION OF THE EMERGENCY TO THE PSAPS ................................................................. 2310.1General requirements ......................................................................................................................... 2310.2Relevant contact details ..................................................................................................................... 2410.3Voice communication ......................................................................................................................... 2410.4Push transfer of a TPS-eCall set of data (TSD) ................................................................................ 2410.5Transitional arrangements ................................................................................................................. 2511TEST AND CONFORMANCE REQUIREMENTS................................................................................. 2612MARKING, LABELLING AND PACKAGING ....................................................................................... 26ANNEX A (NORMATIVE)

STANDARDISED DATA INTERFACE BETWEEN TPSP AND PSAP ................. 27A.2 FUNCTIONALITIES ............................................................................................................................. 27A.2.1 The application acknowledgement (ack) ......................................................................................... 28A.2.2 Authorization ...................................................................................................................................... 29A.2.3 The TPS-eCall messages ................................................................................................................... 31A.2.3.1 Push-INITIATION ................................................................................................................................. 31A.2.3.2 Request emergency data ................................................................................................................... 31A.2.3.3 Push emergency data ........................................................................................................................ 32A.2.3.4 Clear down .......................................................................................................................................... 32A.2.3.5 Communication control (Ping) .......................................................................................................... 32A.2.4 The PSAP web server wsdl file reference implementation ............................................................ 33A.2.5 The TPSP web server wsdl file as reference implementation........................................................ 37A.2.6 XML codes of the TPS-eCall set of data for the TPSP/PSAP transmission .................................. 40A.3 EUECALL_TPSECALL.XSD ............................................................................................................... 41ANNEX B (INFORMATIVE)

TRANSITIONAL ARRANGEMENTS .................................................................. 44ANNEX C (INFORMATIVE)

XML CODE FOR ADDITIONAL INFORMATION ............................................... 48BIBLIOGRAPHY ................................................................................................................................................ 53SIST EN 16102:2012

EN 16102:2011 (E) 4 Foreword This document (EN 16102:2011) has been prepared by Technical Committee CEN/TC “Road transport and traffic telematics”, 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 June 2012, and conflicting national standards shall be withdrawn at the latest by June 2012. 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. According to the CEN/CENELEC Internal Regulations, the national standards organizations 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, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. SIST EN 16102:2012

EN 16102:2011 (E) 5 Introduction The scale of death and injury on roads in Europe needs to be fully comprehended to understand the need for an automated method to alert about accidents. In 2008, there were 38 900 fatalities in the EU-27. The figure for 2009 is around 34 500 fatalities. The trend for 2001 to 2008 is around a 5 % annual reduction. Road accident Injuries are in the region of 1,7 million (2008). An automated method of accident notification has been estimated to have the potential to save up to 2 500 fatalities annually in the EU-27 when fully deployed, and reduce the severity of injuries in order to bring significant savings to society in terms of reduced costs and human suffering. Emergency calls made from vehicles can assist with the objectives of significantly reducing road deaths and injuries, but drivers often have poor (imprecise) location awareness, especially on interurban roads or abroad. Additionally, in many situations, the car occupants may not be in a position to call using a normal mobile phone. The situation is worse for those travelling abroad: a high (and increasing) number of vehicles travelling outside their home country and this is therefore also contributing to the need for an automated emergency call system in vehicles. In the EU there are over 100 million trips to another EU country per year (EU-15). 65 % of people feel less protected while abroad and most do not know which number to call in an emergency (in some countries over 60 %). Language problems are pertinent and may render communication difficult. In the most crucial cases, the victim(s) may not be able to call because they have been injured and/or trapped, do not know the local number to call, and in many cases, particularly in rural situations and late at night, there may be no witnesses who happen to have a mobile phone or a sense of community. The objective of implementing an in-vehicle emergency call system is to automate the notification of a traffic accident. One major benefit is to transmit data from the vehicle. There are two means to provide an eCall from a vehicle:  One method is to use the pan-European eCall, which sends the voice call and the data directly to the PSAP, using the emergency number 112.  Another method consists of using a ‘third party services supported eCall’, referred to as TPS-eCall in this document. This is an eCall variant which includes the transmission of data to a Third Party Service Provider or TPSP, and the establishment of a voice call with this TPSP. In the case of an emergency likely to require assistance from the emergency services, the TPSP establishes a voice connection with the most appropriate PSAP. The TPSP also forwards all relevant information concerning the event, including the information specified as mandatory by the MSD standard (EN 15722) as a minimum, to the most appropriate PSAP. The TPSP also provides voice communication between the PSAP and the vehicle occupants by setting up a conference call for example, if this is required by any of the parties involved and allowed by the PSAP. This European Standard specifies the generic operational requirements for the TPS-eCall. SIST EN 16102:2012

EN 16102:2011 (E) 6 1 Scope The objective of implementing a 'Third Party' emergency call is to provide emergency assistance and an automated notification of a traffic accident, using 'Third Party Services' packages where such services are supported between the vehicle and a Third Party Service Provider in countries where such notification of an emergency are supported by PSAPs. The first objective of this TPS-eCall is to transfer an emergency message from a vehicle to a Third Party Service Provider (TPSP) in the event of a crash or an emergency, and to establish a voice channel between the in-vehicle equipment and the TPSP. The second objective of this TPS-eCall is, in case of an emergency likely to require assistance from the emergency services, for the TPSP to transfer an emergency message including the data of the Minimum Set of Data (MSD) (as defined in EN 15722) from the TPSP to the most appropriate PSAP and to make best efforts to establish a direct voice contact between that PSAP and the occupants of the vehicle if required by the PSAP. This European Standard specifies the general operating requirements and intrinsic procedures for an in-vehicle eCall via the services of a Third Party Service Provider (TPSP). This European Standard also provides definition of the service(s) provided to the PSAP and the method and form of service delivery. NOTE An important part of the TPS-eCall is the Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this European Standard, but the form and data content of the MSD is not defined herein. The common European MSD for eCall is determined in EN 15722. Additional data concepts may also be transferred, and it is recommended that any such data concepts be registered using a data registry as defined in EN ISO 24978 to ensure that they can be understood by the recipient. 2 Normative references The following referenced documents are indispensable for the application 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:2011, Intelligent transport systems — eSafety — eCall minimum set of data (MSD) 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 112 single European emergency call number 3.2 data representations of static or dynamic objects in a formalized manner suitable for communication, interpretation, or processing by humans or by machines 3.3 data concept any of a group of data structures (i.e. object class, property, value domain, data elements, message, interface dialogue, association) referring to abstractions or things in the natural world that can be identified with explicit boundaries and meaning and whose properties and behaviour all follow the same rules SIST EN 16102:2012

EN 16102:2011 (E) 7 3.4 data dictionary organized and constructed (electronic database) compilation of descriptions of data concepts that provides a consistent means for documenting, storing and retrieving the syntactical form (i.e. representational form) and the meaning and connotation of eCall data concept NOTE A data registry provides definition of the metadata concept, it does not store the values of individual instances. For example, a data registry with a data concept 'registration plate identification of a vehicle' defines how the identification numbers/letters are represented. It does not contain a list of particular licence plates. 3.5 data element single unit of information of interest (such as a fact, proposition, observation, etc.) about some (entity) class of interest (e.g. a person, place, process, property, concept, association, state, event) considered to be indivisible in a particular context 3.6 data registry registration process to store data definitions, characterized in a consistent manner, as determined according to the provisions of an international standard, in a data dictionary NOTE Neither a data registry nor a data dictionary provides a database of specific values of instances of the use of the registry/dictionary in an implementation. 3.7 E164 ITU-T recommendation which defines the international public telecommunication numbering plan used in the PSTN and some other data networks 3.8 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 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 [EN 16072:2011] 3.9 IVS dataset minimum set of vehicle-generated data elements which are essential for the performance of the TPS-eCall NOTE 1 The format and content of this ‘IVS dataset’ is not defined by this European Standard, but it needs to be possible for the service provider to create an MSD as defined in EN 15722 based on this ‘IVS dataset’. NOTE 2 This may be a sub-set of the MSD data elements as some MSD elements can be inferred/looked-up from other elements by the TPSP. SIST EN 16102:2012

EN 16102:2011 (E) 8 3.10 Minimum Set of Data (MSD) standardised data concept, comprising data elements essential for the notification of a TPS-eCall to a PSAP [EN 15722:2011] 3.11 Network Access Device (NAD) see mobile wireless communications network device 3.12 pan-European eCall eCall provided by a ‘Teleservice 12’ mobile communication network, as defined in EN 16072 3.13 Public Safety Answering Point (PSAP) physical location where emergency calls are first received under the responsibility of a public authority or a private organisation recognised by the government (see also most appropriate PSAP) NOTE A number of different instantiations of PSAP service are supported within this European Standard. 3.14 most appropriate PSAP PSAP defined beforehand by national authorities to cover emergency calls from a certain area or for emergency calls of a certain type (see also PSAP). NOTE A number of different instantiations of PSAP service are supported within this European Standard. A PSAP may be a Public Authority or a private service provider operating under the control of a Public Authority. 3.15 PSAP emergency telephone number telephone number, generally conformant with the E164 general numbering scheme, which a TPSP can dial internationally in order to establish a voice connection to the PSAP as part of a TPS-eCall notification 3.16 PSAP emergency TSD-push address secure URL provided by a PSAP, which allows an approved TPS-eCall notifier to push a TPS-eCall set of data, including a TPS-eCall unique reference identification, to this PSAP, using methods standardised in this European Standard 3.17 TPS-eCall set of data (TSD) dataset in a format standardised within this European Standard, which can be used by a TPSP acting as a TPS-eCall notifier to forward details of a TPS-eCall to a PSAP 3.18 TPS-eCall generator occupant of a vehicle or equipment within a vehicle that has cause to trigger a TPS-eCall transaction by automatic or manual means 3.19 TPS-eCall responder organisation specifically trained for managing assistance or emergencies, which receives a TPS-eCall and notifies the vehicle or caller that the call has been received NOTE The TPS-eCall responder and TPS-eCall notifier will often be the same organisation but, to clarify the separate stages involved in a TPS-eCall, distinct roles and definitions are used in this European Standard. Within the TPS-eCall responder different organisations can handle the voice connection and the data management of an eCall event. SIST EN 16102:2012

EN 16102:2011 (E) 9 3.20 TPS-eCall notification notification from a TPS-eCall notifier to a most appropriate PSAP about a TPS-eCall likely to require assistance from the emergency services, and provision of all relevant information concerning the event (if necessary collating data from the ‘IVS dataset’ and data from other sources), including the information specified as mandatory by the MSD standard EN 15722 as a minimum 3.21 TPS-eCall notifier organisation specifically trained for managing emergencies, which performs a TPS-eCall notification; as a consequence of a TPS-eCall responder receiving a TPS-eCall likely to require assistance from the emergency services NOTE 1 The TPS-eCall notifier also makes best efforts to provide voice communication between the PSAP and the vehicle occupants, at least by setting up a conference call, if this is required by any of the parties involved. NOTE 2 The TPS-eCall responder and TPS-eCall notifier will often be the same organisation but, to clarify the separate stages involved, distinct roles and definitions are used in this standard for each stage of the TPS-eCall. Within the TPS-eCall responder, different organisations can handle the voice connection and the data management of an eCall event. 3.22 TPS-eCall service capability of a vehicle to be a TPS-eCall generator, triggering of a TPS-eCall transaction, intent of a TPSP to be a TPS-eCall responder and provision of that response including where necessary a TPS-eCall notification 3.23 TPS-eCall transaction transmission across a mobile network of a set of data from a vehicle to a TPS-eCall responder and the establishment of a voice channel between the vehicle and the TPS-eCall responder 3.24 TPS-eCall ‘third party services supported eCall’: eCall variant as described and defined in this European Standard NOTE In summary

...

Questions, Comments and Discussion

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