Intelligent transport systems - eSafety - Pan-European eCall operating requirements

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.
NOTE 1   Private third party in-vehicle emergency supporting services may also provide a similar eCall function by other means. The provision of such services are being defined in prEN 16102 (in ballot), and are outside the scope of this European Standard.
NOTE 2   The communications protocols and methods for the transmission of the eCall message are not specified in this European Standard.
NOTE 3   This European Standard specifies the operating requirements for an eCall service. An important part of the eCall service is a 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. A common European MSD is determined in
EN 15722.

Intelligente Transportsysteme - Elektronische Sicherheit - Paneuropäische Notruf-Betriebsanforderungen

Das Ziel der Implementierung des gesamteuropäischen bordeigenen Notrufsystems (eCall) besteht darin, die Benachrichtigung über den Eintritt eines Verkehrsunfallereignisses europaweit mit denselben technischen Normen und denselben Dienstgütezielen durch Nutzung eines Mobilfunknetzes (en: Public Land Mobile Net-work, PLMN) (wie z. B. GSM oder 3G), welches die europäische zuvor zugeordnete Notzieladresse (siehe die Normativen Verweisungen) unterstützt, zu automatisieren. Zusätzlich soll ein Hilfsmittel für die manuelle Auslösung der Benachrichtigung über den Eintritt eines Notfalls zur Verfügung gestellt werden. Diese Europäische Norm legt die allgemeinen Betriebsanforderungen und intrinsischen Verfahren für fahrzeuginterne Notruf(eCall)-Dienste mit dem Ziel fest, im Falle eines Unfalls oder eines sonstigen Notfalls über eine eCall-Kommunikationssitzung einen Notruf vom Fahrzeug an eine Notrufzentrale (PSAP) zu übermitteln und eine Sprachverbindung zwischen der fahrzeugseitigen Ausrüstung und der PSAP herzustellen. ANMERKUNG 1 Von Dritten bereitgestellte, private fahrzeuginterne Dienste zur Unterstützung in Notfällen können eine ähnliche eCall-Funktion auch mit anderen Mitteln zur Verfügung stellen. Derartige Dienste sind in prEN 16102 (derzeit in der Abstimmung) festgelegt und nicht Gegenstand des vorliegenden Dokuments. ANMERKUNG 2 Die Kommunikationsprotokolle und die Verfahren für die Übertragung der eCall-Nachricht sind in der vorliegenden Norm nicht festgelegt. ANMERKUNG 3 Diese Europäische Norm legt die Betriebsanforderungen für eCall-Dienste fest. Ein wichtiger Bestand-teil des eCall-Dienstes ist der "Minimale Datensatz" (en: Minimum Set of Data, MSD). In der vorliegenden Europäischen Norm sind die Betriebsanforderungen für den MSD, nicht aber seine Form und sein Dateninhalt festgelegt. Ein gemein-samer Europäischer MSD ist in EN 15722 festgelegt.

Systèmes intelligents de transport - ESafety - eCall paneuropéen - Exigences de fonctionnement

Dans le cadre de l'appel d'urgence "pan-européen" (exigences opérationnelles définies dans l'EN
160702, "Systèmes intelligents de transport - eCall - Exigences opérationnelles de l'appel d'urgence
pan-européen"), la présente Norme européenne définit les protocoles, procédures et processus d'application
de haut niveau requis pour la fourniture du service eCall en utilisant un appel d'urgence du TS12 via un
réseau de communication pour mobiles.
L'implémentation du système embarqué d'appel d'urgence pan-européen (eCall) a pour objectif d'automatiser
la notification d'un accident routier, quel que soit le lieu de cet accident en Europe, avec les mêmes critères
techniques et les mêmes objectifs de qualité de service en utilisant un réseau de communication pour mobiles
(moyen ETSI par exemple) qui prend en charge le numéro d'urgence 112/E112 harmonisé
(TS12 ETSI TS 122 003), ainsi que de fournir un moyen pour déclencher manuellement la notification d'un
incident nécessitant une réponse rapide.
NOTE Les exigences HLAP relatives au service SFP-eCall sont spécifiées dans le document "Exigences
opérationnelles des services d'appel d'urgence de fournisseurs privés", et ont été développées conjointement au présent
document et de manière cohérente avec l'interface du PSAP. Le document susmentionné fait référence à ces dispositions
mais ne les expose pas dans le détail.

Inteligentni transportni sistemi - e-Varnost - Zahteve za delovanje vseevropskega elektronskega klica v sili

Cilj vpeljave vseevropskega sistema za klic v sili v vozilih (elektronski klic) je avtomatizirati obveščanje ob prometni nesreči, kjer koli v Evropi, z enakimi tehničnimi standardi in enako kakovostjo ciljev storitev z uporabo »javnih kopenskih mobilnih omrežij« (PLMN) (kot so GSM in 3G), ki podpirajo evropske vnaprej dodeljene ciljne naslove za nujne primere (glej normativne sklice) in zagotavljajo način ročnega pošiljanja obvestila ob prometni nesreči. Ta evropski standard določa splošne zahteve delovanja in notranje postopke za storitve za klic v sili v vozilih (elektronski klic) za prenos sporočila klica v sili iz vozila do odzivne točke javne varnosti (PSAP) ob nesreči ali nujnem dogodku prek komunikacije z elektronskim klicem in za vzpostavitev glasovnega kanala med opremo v vozilu in PSAP.

General Information

Status
Withdrawn
Publication Date
27-Sep-2011
Withdrawal Date
21-Apr-2015
Current Stage
9960 - Withdrawal effective - Withdrawal
Completion Date
22-Apr-2015

RELATIONS

Buy Standard

Standard
EN 16072:2011
English language
28 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 - 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
SIST EN 16072:2011
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

EN 16072:2011 (E) 2 Contents Page Foreword ..............................................................................................................................................................4Introduction .........................................................................................................................................................51 Scope ......................................................................................................................................................62 Conformance ..........................................................................................................................................73 Normative references ............................................................................................................................74 Terms and definitions ...........................................................................................................................85 Symbols and abbreviations ............................................................................................................... 116 High level functional requirements ................................................................................................... 126.1 General high level functional requirements ..................................................................................... 126.1.1 General ................................................................................................................................................. 126.1.2 Linguistic aspects............................................................................................................................... 126.1.3 High level In-Vehicle System requirements ..................................................................................... 136.1.4 eCall architecture ................................................................................................................................ 136.1.5 eCall operation sequence .................................................................................................................. 136.2 eCall service chain.............................................................................................................................. 146.2.1 General ................................................................................................................................................. 146.2.2 Actors in eCall service provision ...................................................................................................... 146.2.3 Privacy aspects ................................................................................................................................... 146.2.4 Use of location and heading at PSAP ............................................................................................... 147 Operational requirements .................................................................................................................. 157.1 General ................................................................................................................................................. 157.2 Liability ................................................................................................................................................ 157.3 Routing of an eCall ............................................................................................................................. 167.3.1 General ................................................................................................................................................. 167.3.2 eCall 'flag' ............................................................................................................................................ 167.3.3 eCall routing to PSAP ......................................................................................................................... 177.4 Prioritisation of an eCall .................................................................................................................... 177.5 Post crash performance of in-vehicle equipment ........................................................................... 177.6 Location and direction ....................................................................................................................... 177.6.1 Location data ....................................................................................................................................... 177.6.2 Data concerning direction and location ........................................................................................... 187.6.3 Optional data regarding location and direction ............................................................................... 187.7 Minimum Set of Data (MSD) ............................................................................................................... 197.7.1 Data within the MSD ........................................................................................................................... 197.7.2 Optional additional data ..................................................................................................................... 197.8 Modes of operation for automatic triggered eCall .......................................................................... 197.9 In-vehicle Human Machine Interface (HMI) aspects ........................................................................ 207.9.1 General ................................................................................................................................................. 207.9.2 HMI aspects in the case of automatic triggering ............................................................................. 207.9.3 HMI aspects in the case of manual triggering ................................................................................. 207.9.4 Alerting of initiated eCall (automatically or manually triggered) ................................................... 207.10 Triggering ............................................................................................................................................ 207.10.1 Automatic eCall triggering strategy .................................................................................................. 207.10.2 Manual eCall triggering strategy ....................................................................................................... 217.10.3 Manual termination of eCall by vehicle occupants before trigger confirmation .......................... 217.11 Termination of an in progress eCall ................................................................................................. 217.12 Requirements to physical layer ......................................................................................................... 217.12.1 Transport protocol .............................................................................................................................. 21SIST EN 16072:2011

EN 16072:2011 (E) 3 7.12.2 Performance requirements- time required to transmit data ........................................................... 217.12.3 End-to-end performance criteria ........................................................................................................ 227.12.4 Performance criteria – Wireless network .......................................................................................... 227.12.5 Performance criteria – PSAP .............................................................................................................. 227.13 Establish voice channel ...................................................................................................................... 237.13.1 General ................................................................................................................................................. 237.13.2 Coverage issues .................................................................................................................................. 237.13.3 Roaming requirements for service .................................................................................................... 237.14 Acknowledgement of eCall ................................................................................................................. 237.15 Continuing availability ........................................................................................................................ 237.16 PSAP response .................................................................................................................................... 237.17 eCall termination ................................................................................................................................. 237.17.1 General ................................................................................................................................................. 237.17.2 IVS redial .............................................................................................................................................. 247.17.3 PSAP call-back .................................................................................................................................... 247.17.4 Record transaction .............................................................................................................................. 248 Defences against attack ...................................................................................................................... 248.1 Call line security .................................................................................................................................. 248.2 Hoax calls ............................................................................................................................................. 258.3 Denial of service attack ....................................................................................................................... 258.4 Malicious attack on PSAP................................................................................................................... 259 Different requirements for HGVs ....................................................................................................... 2510 Different requirements for 2 wheel vehicles ..................................................................................... 2511 Test and conformance requirements ................................................................................................ 2511.1 General ................................................................................................................................................. 2511.2 eCall conformance .............................................................................................................................. 2611.3 In-vehicle equipment conformance ................................................................................................... 2611.4 Network conformance ......................................................................................................................... 2611.5 PSAP conformance ............................................................................................................................. 2611.6 Interoperability conformance ............................................................................................................. 2712 Marking, labelling and packaging ...................................................................................................... 27Bibliography ...................................................................................................................................................... 28 SIST EN 16072:2011

EN 16072:2011 (E) 4 Foreword This document (EN 16072:2011) has been prepared by Technical Committee CEN/TC 278 “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 March 2012, and conflicting national standards shall be withdrawn at the latest by March 2012. 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 16072:2011

EN 16072:2011 (E) 5 Introduction The scale of death and injury on roads in Europe needs to be fully comprehended to understand the need for 'Emergency Call' (eCall). In 2008 there were 38 900 fatalities in EU-27. The figure for 2009 is around 34 500 fatalities. The trend 2001 to 2008 is around 5 % reduction annually. Road accident injuries are in the region of 1,7 million (2008). Roads remain unsafe and further efforts are needed. The pan-European in-vehicle emergency call, eCall, is estimated to have the potential to save up to 2 500 fatalities annually in EU-27 when fully deployed and furthermore to reduce the severity of injuries, to bring significant savings to the society in and to reduce human suffering. Emergency calls made from vehicles or mobile telephones using wireless technologies 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 is thus also contributing to the need for automated emergency call system in vehicles. In EU there are over 100 million trips to another EU country per year (EU-15). 65 % 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 proper communication difficult. Yet, in the most crucial cases, the victim(s) may not be able to call because they have been injured/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 and a sense of community. eCall, in the context of 'Road Traffic and Transport Telematics' (otherwise known as 'Intelligent Transport Systems' or 'ITS'), can be described as an 'automatic or user instigated system to provide notification to Public Safety Answering Points (PSAP), by means of wireless communications, that a vehicle has crashed, and to provide coordinates, a defined Minimum Set of Data, and where possible a voice link to the PSAP'. The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in the European Union and associated countries, with the same technical standards and the same quality of services objectives of other emergency (TS12) services. Definition of the Minimum Set of Data, the communications media and means of transferring the data are not specified in this European Standard. This European Standard specifies the generic operational requirements for the provision of an eCall service. The practical provision and operation of eCall service and equipment is dependent on the communications medium being available throughout the lifetime of equipment installed in vehicles. NOTE The term PSAP, which is most widely used in the eCall documentation, European Commission documents etc., equates to the term emergency call response centre. The European Committee for Standardization (CEN) draws attention to the fact that it is claimed that compliance with this European Standard may involve the use of patents concerning eCall given in this European Standard. CEN takes no position concerning the evidence, validity and scope of these patent rights. SIST EN 16072:2011

EN 16072:2011 (E) 6 The holder of these patent rights has assured to CEN that he/she is willing to negotiate licenses under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holders of these patent rights are registered with CEN. Information may be obtained from: Mr. Thomas R. Rouse VP QTL Patent Counsel QUALCOMM Incorported 5775 Morehouse Drive San Diego, California 92121 Phone: +1-858-587-1121 Fax: +1-858-658-2503 Email: trouse@qualcomm.com URL: www.qualcomm.com

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 16072:2011 (E) 7 NOTE 1 Private third party in-vehicle emergency supporting services may also provide a similar eCall function by other means. The provision of such services are being defined in EN 16102, and are outside the scope of this European Standard. NOTE 2 The communications protocols and methods for the transmission of the eCall message are not specified in this European Standard. NOTE 3 This European Standard specifies the operating requirements for an eCall service. An important part of the eCall service is a 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. A common European MSD is determined in

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

EN 16072:2011 (E) 8 4 Terms and definitions For the purposes of this document, the following terms and definitions apply. 4.1 112 single European emergency call number supporting Teleservice 12 [ETSI TS 122 003] 4.2 E112 emergency communications service using the single European emergency call number, 112, which is enhanced with location information of the calling user 4.3 association data concept; structural relationship 4.4 cellular network wireless communications network consisting of multiple adjacent access points (cells) with the capability of homogeneous transfer of a communications session instance to an adjacent cell without significant interruption to the session 4.5 data representations of static or dynamic objects in a formalized manner suitable for communication, interpretation, or processing by humans or by machines 4.6 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 4.7 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 4.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 4.9 eCall generator occupant of a vehicle or equipment within a vehicle that has cause to trigger an eCall transaction by automatic or manual means SIST EN 16072:2011

EN 16072:2011 (E) 9 4.10 eCall identifier one of two information element bits (flags) included in the emergency call set-up message that may be used by the mobile network to filter and route automatically and manually initiated eCalls to a designated PSAP

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

EN 16072:2011 (E) 10 4.20 Minimum Set of Data standardised data concept comprising data elements of relevant vehicle generated data essential for the performance of the eCall service 4.21 mobile telecommunication network operator (MNO) provider of a mobile wireless communications network that supports TS12 emergency services [ETSI TS 122 003] 4.22 mobile wireless communications network wireless communications network with homogeneous handover between network access points 4.23 most appropriate PSAP PSAP defined beforehand by the responsible authorities to cover emergency calls from a certain area or for emergency calls of a certain type NOTE 1 See also PSAP. NOTE 2 A number of different instantiations of PSAP service are supported within this European Standard. A PSAP can be a Public Authority or a private service provider operating under the control of a Public Authority. 4.24 Network Access Device device providing communications to a mobile wireless communications network with homogeneous handover between network access points 4.25 network access points beacon, antenna or similar source of signal propagation and receipt together with equipment to manage communication sessions with users operating within the operating reach of the network access point and provide connectivity for the users within the operating reach of the single access point to a wider communications network NOTE A network access point may or may not provide homogeneous or heterogeneous handover to another network access point. 4.26 pan-European eCall eCall sent directly using ETSI defined Teleservice 12 over mobile telephone networks designed to work throughout European Union Member States 4.27 prime medium wireless medium defined in an ETSI standard to be suitable for transmission of an eCall transaction (ETSI TS 122 101, ETSI TS 124 008, ETSI TS 126 267, ETSI TS 12

...

Questions, Comments and Discussion

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