1、BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Intelligent Transport Systems - eSafety - ProForma eCall Agreement between TPSP and EROPD CEN/TS 17148:2018National forewordThis Published Document is the UK implementation of CEN/TS 17148:2018.The UK participation in i
2、ts preparation was entrusted to Technical Committee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible
3、for its correct application. The British Standards Institution 2018 Published by BSI Standards Limited 2018ISBN 978 0 580 98153 1ICS 35.240.60Compliance with a British Standard cannot confer immunity from legal obligations.This Published Document was published under the authority of the Standards Po
4、licy and Strategy Committee on 28 February 2018.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TS 17148:2018TECHNICAL SPECIFICATIONSPCIFICATION TECHNIQUETECHNISCHE SPEZIFIKATIONCEN/TS 17148January 2018ICS 35.240.60EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT
5、EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGCEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2018 CEN Ref. No. CEN/TS 17148:2018: EAll rights of exploitation in any form and by any means reserved worldwide for CEN national MembersIntelligent Transport Systems - eSafety - Pr
6、oForma eCall Agreement between TPSP and EROSystmes de transport intelligent - ESafety - Accord type entre fournisseur de service eCall et centres de secours durgenceIntelligente Verkehrssysteme - ESicherheit - Pro-forma Abkommen zwischen Leitstellen und dritter DienstanbieterThis Technical Specifica
7、tion (CEN/TS) was approved by CEN on 27 November 2017 for provisional application.The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted
8、 into a European Standard.CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) u
9、ntil the final decision about the possible conversion of the CEN/TS into an EN is reached.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary,
10、Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.English VersionCEN/TS 17148:2018 (E)European foreword 3Introduction . 41 Scope . 52 Normative references 53
11、 Terms and definitions . 54 Symbols and abbreviations 105 Overview - eCall background 106 PARES: TPSP Arrangements .126.1 Need for Agreement between PARES and TPSP 126.2 Who should sign the Agreement. 126.3 Contact and boundaries data . 137 Requirements .147.1 General context 147.2 Pro-Forma Templat
12、e for Operational Support Agreement between an PARES and an eCall TPSP . 14Annex A (informative) Pro-Forma Template for Operational Support Agreement between a Public Authority responsible for Emergency Services” (PARES) and an eCall Third Party Service Provider Organization 15Bibliography .242Conte
13、nts PagePD CEN/TS 17148:2018CEN/TS 17148:2018 (E)European forewordThis document (CEN/TS 17148:2018) has been prepared by Technical Committee CEN/TC 278 “Intelligent transport systems”, the secretariat of which is held by NEN.Attention is drawn to the possibility that some of the elements of this doc
14、ument may be the subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights.According to the CEN-CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, Belgiu
15、m, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden,
16、Switzerland, Turkey and the United Kingdom.3PD CEN/TS 17148:2018CEN/TS 17148:2018 (E)IntroductionAn eCall is an 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 info
17、rmation to the most appropriate public safety answering points (PSAP), by means of mobile wireless communications networks, carries a defined standardized minimum set of data, notifying that there has been an incident that requires response from the emergency services and establishes a voice channel
18、 between the occupants of the vehicle and the most appropriate PSAP.There are two variants of eCalls:a) 112-eCalls;b) Third Party Service supported eCalls (TPS eCalls).112-eCalls progress automatically from the vehicle to the “Public Safety Answering Point” (PSAP).Third Party Service Provider (TPS)
19、involve the services and support of a “Third Party Assistance Provider” (TPSP) who may filter out false calls, determine if an emergency call requires the emergency services or other services (such as breakdown assistance), and may provide additional information requested by the owner of the vehicle
20、 to be passed to emergency services in the event of an emergency Call, or where the vehicle does not have the capability to send the full set of MSD data, may add data and consolidate the MSD before forwarding it to the PSAP.TPS assisted eCalls are therefore more complex to manage and require an agr
21、eement between each TPSP and each “Public Authority responsible for Emergency Services” (PARES). Up till the development of this document there has been no standard agreement, nor guidance, and it is left to the TPSP to work out what information it provides to the PARES when requesting an agreement,
22、 and to the PARES to work out what information it needs from the TPSP.While the decision as to whether or not to accept an eCall from a particular TPSP, and the terms under which such calls are accepted from any particular TPSP remain firmly in the hands of the PARES and the jurisdiction under which
23、 it operates, it is considered to be advantageous to start such negotiations from a standard template. This document provides a pro-forma template which a PARES can require from any applicant TPSP, or an applicant TPSP can offer to any PARES that it approaches to request an agreement to accept their
24、 eCalls.4PD CEN/TS 17148:2018CEN/TS 17148:2018 (E)1 ScopeThis document provides a pro-forma template “Operational Support Agreement” (OSA) for guidance of “Public Authorities responsible for Emergency Services” (PARES) and Third Party Service Providers (TPSP) of third party assisted eCalls who are c
25、onsidering a formal agreement to accept eCall messages from a TPSP.While the decision as to whether or not to accept eCall from a particular TPSP, and the terms under which such calls are accepted from any particular TPSP remain firmly in the hands of the PARES and the jurisdiction under which it op
26、erates, it is considered to be advantageous to start such negotiations from a standard template. This document provides a pro-forma template which a PARES can require from any applicant TPSP, or an applicant TPSP can offer to any PARES that it approaches to request an agreement to accept their eCall
27、s.NOTE This pro-forma template is presented as a start point to a formal agreement between a PARES and a TPSP, not the format of the conditions of a final agreement.CAVEAT: The template that is the subject of this deliverable is advisory, and any agreement between a TPSP and a PARES should be checke
28、d by someone legally competent in the jurisdiction that the agreement covers. This document does not claim to be a statement or interpretation of EU law or the national law of any EU Member State. This document is entirely without prejudice to the views of relevant national statutory authorities and
29、 their legal functions and powers, whether under EU law or the national law of their Member State.2 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited ap
30、plies. For undated references, the latest edition of the referenced document (including any amendments) applies.EN 15722:2015, Intelligent transport systems ESafety ECall minimum set of dataEN 16062:2015, Intelligent transport systems ESafety eCall high level application requirements (HLAP) using GS
31、M/UMTS circuit switched networksEN 16072:2015, Intelligent transport systems ESafety Pan-European eCall operating requirementsEN 16102:2011, Intelligent transport systems eCall Operating requirements for third party supportEN 16454:2015, Intelligent transport systems ESafety ECall end to end conform
32、ance testingETSI/TS 122 003, Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Circuit Teleservices supported by a Public Land Mobile Network (PLMN) (3GPP TS 22.003 version 8.0.0 Release 8)3 Terms and definitionsFor the purposes of this do
33、cument, the following terms and definitions apply.3.1112single European emergency call number3.2112-eCalleCall provided by a Teleservice 12 mobile communication network, as defined in EN 16072 Intelligent transport systems eSafety Pan European eCall operating requirements5PD CEN/TS 17148:2018CEN/TS
34、17148:2018 (E)3.3agent of the PARESofficially designated PARES service provider such as a PSAP, emergency rescue organisation, emergency service such as police, ambulance, paramedics, fire brigade, etc. as notified by the PARES to the TPSP3.4call line identifiers (CLI)calling line identification (CL
35、ID), calling number delivery (CND), calling number identification (CNID) or calling line identification presentation (CLIP), is a telephone service, available in analogue and digital phone systems and most voice over Internet Protocol (VoIP) applications, that transmits a callers number to the calle
36、d partys telephone equipment during the ringing signal, or when the call is being set up but before the call is answered (A modem can pass CLID information to a computer for purposes of call logging) or blocking,3.5clientparty with whom a TPSP has a valid contact for the provision of eCall TPS servi
37、ces for an equipped vehicle3.6datarepresentations of static or dynamic objects in a formalized manner suitable for communication, interpretation, or processing by humans or by machines3.7data dictionaryorganized and constructed (electronic data base) compilation of descriptions of data concepts that
38、 provides a consistent means for documenting, storing and retrieving the syntactical form (i.e. representational form) and the meaning and connotation of eCall data conceptNOTE A data registry provides definition of the metadata concept, it does not store the values of individual instances. For exam
39、ple 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.8data elementsingle unit of information of interest (such as a fact, proposition, observati
40、on, 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 context3.9data registryregistration process to store data definitions, characterized in a consistent manner, as determined accor
41、ding to the provisions of an international standard, in a data dictionaryNOTE 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.10E112emergency communications service using the single Europea
42、n emergency call number, 112, which is enhanced with location information of the calling userNOTE See European Commission Recommendation C 2657 (2003).3.11E164ITU-T recommendation which defines the international public telecommunication numbering plan used in the PSTN and some other data networks6 P
43、D CEN/TS 17148:2018CEN/TS 17148:2018 (E)3.12eCalldefined in EN 16072 Intelligent transport systems eSafety Pan European eCall operating requirements as “emergency call generated either automatically via activation of in-vehicle sensors or manually by the vehicle occupants; when activated, it provide
44、s notification and relevant location information to the most appropriate public safety answering points (PSAP), 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
45、 services and establishes a voice channel between the occupants of the vehicle and the most appropriate PSAP3.13emergency callcall from a user to an emergency control centre including and especially E1123.14emergency control centrefacilities used by emergency organizations to accept and handle emerg
46、ency callsNOTE A PSAP forwards emergency calls to the emergency control centres.3.15emergency response organisationauthority in charge of emergency services within a jurisdiction/Member State; referred to as a Public Authority responsible for Emergency Services” (PARES) within this document3.16equip
47、ped vehiclevehicle equipped with operational means to trigger a TPS eCall3.17IVS datasetminimum set of vehicle-generated data elements which are essential for the performance of the TPS-eCall. The format and content of this IVS dataset is not defined by EN 16102, but it must be possible for the serv
48、ice provider to create an MSD as defined in EN 15722 (Intelligent transport systems eSafety eCall minimum set of data) based on this IVS datasetNOTE 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.3.18most appropriate PSA
49、PPSAP defined beforehand by national authorities to cover emergency calls from a certain area or for emergency calls of a certain typeNOTE A number of different instantiations of PSAP service are supported within this Technical Specification. A PSAP may be a Public Authority or a private service provider operating under the control of a Public Authority.3.19minimum set of data (MSD)standardised data concept, as specified in EN 15722 (Intelligent transport systems eSafety eCall minimum set of data), comprisin
