EN 16072:2011

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentni transportni sistemi - e-Varnost - Zahteve za delovanje vseevropskega elektronskega klica v siliIntelligente Transportsysteme - ESicherheit - Paneuropäische Notruf-BetriebsanforderungenSystèmes intelligents de transport - ESafety - Exigences HLAP pour l'eCallIntelligent transport systems - eSafety - Pan-European eCall operating requirements43.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 16072:2011SIST EN 16072:2011en01-november-2011SIST EN 16072:2011SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16072
September 2011 ICS 03.220.20; 13.200; 35.240.60; 43.040.15 English Version
Intelligent transport systems - eSafety - Pan-European eCall operating requirements
Systèmes intelligents de transport - ESafety - Exigences HLAP pour l'eCall
Intelligente Transportsysteme - ESicherheit - Paneuropäische Notruf-Betriebsanforderungen This European Standard was approved by CEN on 18 August 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 16072:2011: ESIST EN 16072:2011

Mr. Thomas W. Davis Jr. General Council AIRBIQUITY Incorporated 1011 Western Avenue, Suite 600 Seattle, Washington 98104
USA Phone: +1.206.219.2700 Fax: +1.206.842.9259 Toll-Free:+1.888.334.7741 Email: tdavis@airbiquity.com URL: www.airbiquity.com Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above. CEN shall not be held responsible for identifying any or all such patent rights. 1 Scope The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using 'Public Land Mobile Networks'(PLMN) (such as GSM and 3G), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident. This European Standard specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP. SIST EN 16072:2011

EN 15722. 2 Conformance Test requirements and conformance requirements are described in Clause 11. Conformance procedures will be specified in a separate deliverable and are outside of the scope of this European Standard. 3 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) EN 16062:2011, Intelligent transport systems — eSafety — eCall high level application requirements (HLAP) EN ISO 24978, Intelligent transport systems — ITS safety and emergency messages using any available wireless media — Data registry procedures (ISO 24978:2009) ETSI TS 122 101, Universal Mobile Telecommunications System (UMTS); LTE; Service aspects; Service principles (Release 8) ETSI TS 124 008, Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE;Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 8) ETSI TS 126 267, Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); eCall data transfer; In-band modem solution; General description (Release 8) ETSI TS 126 268, Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); eCall data transfer; In-band modem solution; ANSI-C reference code (Release 8) ETSI TS 126 269, Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); eCall data transfer; In-band modem solution; Conformance testing (Release 8) SIST EN 16072:2011

4.11 eCall service capability of in-vehicle equipment to be an eCall generator, triggering of an eCall transaction, intent of a PSAP to be an eCall responder and provision of that response 4.12 eCall transaction establishment of a mobile wireless communications session across a public wireless communications network and the transmission of a Minimum Set of Data from a vehicle to a Public Safety Answering Point and the establishment of a voice channel between the vehicle and the PSAP 4.13 eCall trigger signal emanating from within the vehicle to the eCall in-vehicle equipment which requests to start an eCall transaction 4.14 emergency call response centre Term used in ITS Implementation Directive to mean ‘Public Safety Answering Point’ (PSAP) 4.15 identifier any label, symbol or token that names or identifies an entity or a collection of data or the means of designating or referring to a specific instance of a data concept 4.16 ignition-on first action taken by a driver to make the car operate NOTE This is typically the turning of a key in an ignition sequence or other methods of vehicle operation as specified by vehicle manufacturer. 4.17 in-vehicle equipment equipment within the vehicle that provides or has access to in-vehicle data required for the Minimum Set of Data and any other data that is to be sent as part of or complementary to the Minimum Set of Data to effect the eCall transaction via a public mobile wireless communications network providing a link between the vehicle and a means of enacting the eCall service via a public mobile wireless communications network 4.18 in-vehicle equipment provider provider of eCall in-vehicle equipment which is given access to the relevant Minimum Set of Data by the vehicle manufacturer, or which is providing the relevant Minimum Set of Data in order to effect the eCall service NOTE The in-vehicle equipment provider can be the vehicle manufacturer or the provider of aftermarket equipment. 4.19 In-Vehicle System in-vehicle equipment together with the means to trigger, manage and effect the eCall transaction SIST EN 16072:2011

Figure 1 — eCall system overview (Source: European Commission)
6.1.5 eCall operation sequence The MNO system shall treat the eCall as any other TS12 call, and shall include caller line identification and caller location information. NOTE 1 This caller line identification and caller location information is obtained from the network and is in addition to the vehicle calculation of location that is included in the MSD. The generic eCall functional operational sequence is as follows: a) the eCall generator initiates the eCall by sensors triggered and/or manually, sends the in-vehicle triggered eCall to a PSAP. The eCall consists of two elements: 1) the Minimum Set of Data (MSD), and 2) a voice (audio) telephone call based on TS12; b) the eCall carried through the wireless communications network, is recognized by the wireless communications network operator (MNO) system as a TS12 emergency call. An eCall compliant MNO system shall make use of an eCall flag, as specified in ETSI TS 124 008 [Release 8 or later], received in the emergency call set-up message, to differentiate eCalls from other TS12 emergency calls. eCall flags may be used to filter and route eCalls to a dedicated destination if required; SIST EN 16072:2011

The exact order of voice establishment / data exchange is defined by the appropriate the high level application protocols for eCall (EN 16062). 6.2 eCall service chain 6.2.1 General eCall involves a number of different stakeholders all with separate responsibilities and tasks, which may overlap. 6.2.2 Actors in eCall service provision The principal actors in an eCall system are:  in-vehicle equipment provider(s);  mobile telecommunication network operator (MNO);  Public Safety Answering Point (PSAP). 6.2.3 Privacy aspects eCall shall be considered as a public service operating as part of the public emergency call service, where the first part of service provision is a Public Safety Answering Point (which may be a public or private organization under public delegation as determined within nation states). All stakeholders involved shall comply with all EU and national regulations related to the protection of data and the privacy of the citizens in relation to emergency service support. The eCall service shall only operate from the point of service demand (automatic or manual) triggering of the eCall. eCall shall therefore be a 'sleeping' application and shall not be used to monitor the movement of vehicles other than at the point of eCall message triggering as defined in EN 16062. For detail of network registration, see ETSI TS 122 101. NOTE Article 29 Working Party on the protection of the individuals with regards to the processing of personal data have provided an interpretation of these requirements, and the attention of implementers is directed to these interpretations. See http://ec.europa.eu/information_society/activities/esafety/index_en.htm. 6.2.4 Use of location and heading at PSAP In the case of an emergency call it is critical to identify the location of the caller from the coordinates provided in the MSD and to derive a location which can be sent to the emergency service vehicle. The most appropriate PSAP shall have access to an appropriate Geographic Information Service (GIS) so that the operator can identify the location and heading supporting the full resolution as received in the MSD coordinates (see EN 15722). SIST EN 16072:2011

ETSI TS 122 101, ETSI TS 124 008, ETSI TS 126 267, ETSI TS 126 268, ETSI TS 126 269
[Release 8 or later] to be suitable for transmission of an eCall (the prime medium) that is able to sustain both data transfer and voice communication. The IVS shall identify the eCall communications with the eCall 'flag' as specified in ETSI TS 124 008 [Release 8 or later]. 7.3.2 eCall 'flag' NOTE The purpose of the eCall 'flag' is to enable a serving 'Mobile Switching Centre' (MSC), that supports this functionality, to differentiate between speech only Teleservice 12 emergency calls e.g. 112 / E112, and eCalls. Additionally, when supported by the mobile network, the MSC may also be able to discriminate between Manually Initiated eCalls and Automatically Initiated eCalls. An In-Vehicle System, or other user equipment designed to support eCall functionality, shall include in the emergency call set-up information that the present call is either a 'Manually Initiated eCall' (MIeC) or an 'Automatically Initiated eCall' (AIeC). This indication is provided by the eCall 'flag' as specified in ETSI TS 124 008 [Release 8 or later]. PLMNs shall make use of the eCall 'flag', received in the emergency call set-up, to differentiate eCalls from other TS12 emergency calls. The eCall flag may be used to route eCalls to a dedicated PSAP operator. The above service requirements are as specified in 3GPP TS 122.101 and a detailed description of the 'Call Set-up Service Category Information Element' can be found in ETSI TS 124 008 [Release 8 or later]. Although primarily intended to facilitate the filtering and routing of eCalls to an operator defined PSAP, MNO systems might also use the eCall 'Service Category identifiers' for call record/statistical purposes to determine:  the number and ratio of eCalls to TS12 (112/E112, 911, other) emergency calls;  the number and ratio of manually initiated to automatically initiated eCalls; Even a PLMN which does not yet fully support eCall differentiation from a normal TS12 call shall ensure that a call setup from an IVS using an eCall flag gets routed to the most appropriate PSAP as a TS12 call. This should be ensured even outside of the EU-27. NOTE It may be noted that although an indication of manual or automatic eCall initiation is included in the MSD, this information is not used by the mobile network for routing eCalls to a particular PSAP, but may be used by the receiving PSAP. SIST EN 16072:2011
...