EN 16102:2011

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
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

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

Automatic Call Distribution
CLI
Caller Line Identifier
GIS
Geographic Information System
GNSS
Global Navigation Satellite System
GSM
Global System for Mobile communications
HMI
Human Machine Interface
TPS-IVS
TPS In-Vehicle System
Minimum Set of Data
MNO
Mobile Network Operator
NAD
Network Access Device (e.g. a GSM or UMTS module)
PSAP
Public Safety Answering Point
SID
Session Identification
TPS
Third Party Services
TPSP
Third Party Service Provider
TSD
TPS-eCall set of data 5 High level functional requirements 5.1 General high level functional requirements The high level functional requirements of the TPS-eCall service are as follows:  in the event of an accident, the TPS-IVS shall automatically determine whether or not to trigger a TPS-eCall and, when appropriate, make such a call automatically;  a TPS-eCall shall also be able to be triggered manually;  the TPS In-Vehicle System shall include an integrated Network Access Device (NAD), e.g. a GSM module (including a valid and activated SIM Card) and a GNSS system. Upon triggering a TPS-eCall, as defined in 8.2, the TPS-IVS shall attempt to send an ‘IVS dataset’ to the relevant TPS-eCall responder; NOTE 1 If some data elements can be accurately inferred by the TPSP (e.g. vehicle type based on a VIN), these elements may not necessarily be sent from the vehicle. Additional information may be provided by the TPSP.  in countries for which the necessary organisation has been set up, a Third Party Service Provider shall act as a TPS-eCall responder to receive and respond to a TPS-eCall transaction from the vehicle, including determining whether or not there is a need to notify the most appropriate PSAP about the incident;  in case of an emergency likely to require assistance from the emergency services, a TPSP:  shall act as a TPS-eCall notifier to request such assistance from the most appropriate PSAP; to provide the most appropriate PSAP with all relevant information (as determined in this European Standard);  shall make best efforts to establish a voice connection initially between the vehicle and the relevant TPSP and subsequently shall make best efforts to make a direct voice connection between the occupants of the vehicle and the PSAP if this is required by the PSAP (see also 5.3); NOTE 2 Additional information may be provided to the PSAP.  the TPSP shall be able to attempt to re-establish the voice communication with the vehicle as long as the VehiclePhoneNumber is known. NOTE 3
Although normally available, due to the nature of the mobile networks, it cannot be 100 % technically guaranteed that the VehiclePhoneNumber is known in all cases. SIST EN 16102:2012

Figure 1 — TPS-eCall system overview The relationship between the TPS-eCall and the pan-European eCall is shown in Figure 2 below:
Figure 2 — End-to-end pan-European eCall and TPS-eCall systems connected to an eCall enabled PSAP 5.3 TPS-eCall operation sequence The generic TPS-eCall functional operational sequence is as follows: The TPS-eCall generator initiates the TPS-eCall by whatever means (such as sensors/vehicle-processors) automatically triggered and/or manually triggered. The TPS-eCall (between car and TPSP) consists of two elements:  the data (‘IVS dataset’) provided by the TPS-IVS;  a voice (audio) call between the TPSP and the occupants of the vehicle. SIST EN 16102:2012

After the trigger has been distributed, and the TPS-IVS has registered with a suitable mobile network, the ‘IVS dataset’ begins to be transmitted, and the voice call is established between car and TPSP. It is noted that, in some poor radio coverage areas, the data will be successfully transmitted, but no conversation will be possible even if a telephone circuit can be established with TPSP. The data transmission of the ‘IVS dataset’ shall typically be completed within 20 s, this time being measured from the successful establishment of the voice call. 6.3.2 Performance criteria for additional data There is no requirement specified concerning the time for the transmission of any additional data. 6.4 Routing of a TPS-eCall The TPS-eCall may be routed to a TPSP which is not located in the country from which the car is calling, provided this TPSP is compliant with this standard. The final destination of the data and the voice call shall be the same TPSP operator. Matching the data to the relevant voice call is the responsibility of the TPSP. This standard does not specify the method that is to be used to achieve this. 6.5 Call back to vehicle In the event of a disconnection of the voice communication, a call-back voice connection shall be possible between the TPSP and the TPS-IVS, as long as the VehiclePhoneNumber is known. This call-back functionality is described in 8.6 and 9.11. 6.6 Termination of the voice call An in-progress voice call shall not be interrupted by the TPS-IVS. 6.7 Prioritisation of a TPS-eCall A TPS-eCall, whether generated automatically or manually, shall normally be given the highest priority on the use of whatever wireless networks are used by the ‘TPS in-vehicle system’ for a TPS-eCall transaction, except where the same radio medium is required for higher priority time-critical active safety messages. SIST EN 16102:2012
...