1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication PD CEN/TR 16092:2011 Electronic fee collection Requirements for pre-payment systemsPD CEN/TR 16092:2011 PUBLISHED DOCUMENT National foreword This Published Document is the UK
2、implementation of CEN/TR 16092:2011. The UK participation in its preparation was entrusted to Technical Committee EPL/278, Road transport informatics. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all t
3、he necessary provisions of a contract. Users are responsible for its correct application. BSI 2011 ISBN 978 0 580 67649 9 ICS 03.220.20; 35.240.60 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Document was published under the authority of the Standa
4、rds Policy and Strategy Committee on 31 March 2011. Amendments issued since publication Date Text affectedPD CEN/TR 16092:2011TECHNICAL REPORT RAPPORT TECHNIQUE TECHNISCHER BERICHT CEN/TR 16092 March 2011 ICS 03.220.20; 35.240.60 English Version Electronic fee collection - Requirements for pre-payme
5、nt systems Perception de tlpage - Exigences relatives aux systmes de pr-paiement Elektronische Gebhrenerfassung - Anforderungen fr Systeme zur Vorauszahlung This Technical Report was approved by CEN on 16 August 2010. It has been drawn up by the Technical Committee CEN/TC 278. CEN members are the na
6、tional 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, Switz
7、erland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR 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.
8、CEN/TR 16092:2011: EPD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 2 Contents Page Foreword 4 Introduction . 5 1 Scope 6 2 Normative references 6 3 Terms and definitions . 7 4 Abbreviations . 9 5 Interoperability Issues . 10 5.1 Interoperability based on EFC Roles Model . 10 5.2 Interoperability and Pay
9、ment . 11 6 Classification of Pre-Pay solutions . 11 6.1 Pre-Pay Account held in Central System 11 6.2 Pre-Pay Account held on OBE . 12 7 Requirements for Pre-Pay account held in Central Systems 13 7.1 General 13 7.2 Business Process Requirements . 13 7.2.1 General 13 7.2.2 Issuing of an EFC contrac
10、t to the Service User . 13 7.2.3 Personalisation of OBE . 15 7.2.4 Loading of value onto an account . 15 7.2.5 Charging of Toll . 17 7.2.6 Invoicing of the Service User . 17 7.2.7 Refund of residual amount . 17 7.2.8 Clearing of Transactions . 18 7.2.9 Handling of Complaints 18 7.2.10 Security Consi
11、derations . 18 7.3 Technical Requirements . 18 7.3.1 Requirements for OBE 18 7.3.2 Requirements for POS Networks . 18 7.3.3 Requirements for Information and Payment Flow (Interfaces) . 19 7.4 Legal and Functional Constraints 19 7.4.1 Legal Considerations 19 7.4.2 Functional Constraints 21 8 Requirem
12、ents for Pre-Pay account held on OBE . 22 8.1 Prerequisites 22 8.2 Business Process Requirements . 22 8.2.1 Issuing of the Pre-Pay mode 22 8.2.2 Personalisation of OBE . 22 8.2.3 Loading of stored value onto a VBD 23 8.2.4 Loading of stored value into the OBE . 23 8.2.5 Charging of the toll 24 8.2.6
13、 Clearing of transactions 26 8.2.7 Hotlisting / Enforcement . 27 8.2.8 Invoicing of the Service User . 27 8.2.9 Refund of residual amount . 28 8.2.10 Proof of Transactions 28 8.2.11 Handling of Complaints 28 8.2.12 Security Considerations . 28 8.3 Technical Requirements . 29 8.3.1 Requirements for V
14、alue Unit bearing User Media 29 PD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 3 8.3.2 Requirements for OBE 30 8.3.3 Requirements for POS Networks . 31 8.3.4 Requirements for Information and Payment Flow (Interfaces) . 31 8.4 Legal and Functional Constraints 31 8.4.1 Legal Considerations 31 8.4.2 Functi
15、onal constraints 33 9 Invoicing of the Service User . 34 9.1 General 34 9.2 VAT considerations . 34 9.3 Business model considerations 35 9.4 Invoice considerations 35 10 Gaps in terms of Standards and recommendations 37 10.1 Pre-Pay Account held in Central System 37 10.2 Pre-Pay Account held on OBE
16、. 37 10.3 Recommendation for next steps 37 Annex A (informative) Examples of implementations . 38 Bibliography 40 PD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 4 Foreword This document (CEN/TR 16092:2011) has been prepared by Technical Committee CEN/TC 278 “Road Transport and Traffic Telematics”, the s
17、ecretariat of which is held by NEN. 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. This document has been prepared under a mandate gi
18、ven to CEN by the European Commission and the European Free Trade Association. PD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 5 Introduction The discussion on payment-modes within the environment of electronic fee collection at present is based on the existence of a post-payment contract between the Tol
19、l Service Provider (TSP) and the Service User (SU). Pre-conditions of such a contractual agreement are sufficient creditworthiness of the SU, and existence of a bank account with the SU. Questions arise in the context of the access to an EFC system for SUs not being able to meet the aforementioned p
20、re-conditions; SUs with occasional needs to use an EFC system (mainly from the private sector) not willing to open a bank account; not able to open a bank account (by reasons what so ever) and therefore not allowed to participate; from countries with limited access to the card market to participate
21、in an interoperable EFC system, which may otherwise not be open to them. To meet the requirements of this clientele, one or more suitable ways of pre-payments have to be established for EFC to grant interoperability: stored value on an electronic medium; stored value in a central account. As far as
22、private users are concerned legislation could ask for anonymous payment modes as nobody can be forced to open or communicate a bank account. On the other hand such payment modes help Toll Service Providers to offer an interoperable EFC service to customers with a limited monetary risk. Before defini
23、ng necessary standards in that field the requirements of a universal Pre-Payment system able to communicate with the OBE have to be evaluated, especially with regard to validity and feasibility for private users. PD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 6 1 Scope This technical report (TR) analyse
24、s requirements for a universal Pre-Pay account system for EFC including the following issues: relations to other existing standards in this domain; the core requirements and functionality that must be provided. This technical report will show an analysis of the requirements for a universal prepay sy
25、stem and categorise possible different types of pre-pay solutions, in terms of functionality, technical and legal considerations. As far as legal requirements are concerned it will be clarified whether the pre-payment means fall within the scope of European Directive 2000/46/EC on the taking up, pur
26、suit of and prudential supervision of the business of electronic money institutions and whether the medium-issuing organisation has to act as a financial institution and falls within the scope of the Payment Service Directive 2007/64/EC. The latter applying exactly to payment activities undertaken b
27、y entities but do not require a full bank license. The technical report will describe the current state-of-affairs of EFC pre-payment systems, including the demand for standards and inventory of provisions provided by standards. It will identify and prioritize gaps in terms of standards or other ena
28、blers needed in order for the market to provide viable pre-payment solutions in a European context. There are two general approaches to represent the content of the TR: a) allocate each requirement under each pre-pay solution; b) allocate each pre-pay solution under each requirement. To achieve a be
29、tter understanding and readability alternative a) has been decided (this refers to Clause 8 and Clause 9 only). The TR does not give any decision on how or whether one of the pre-payment solutions described is commercially feasible to be considered as an implementable offer to the Service User. The
30、return for invest for any TSP regarding the system architecture requirements and other obligations (refunding of SU) is questionable. This TR just gives a summary of the requirements of possible pre-pay solutions. It is up to decision makers to evaluate the alternatives in the light of their individ
31、ual preconditions of their tolling regime and of market acceptance. 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 doc
32、ument (including any amendments) applies. EN 15509, Road transport and traffic telematics Electronic fee collection Interoperability application profile for DSRC prEN ISO 12855, Electronic fee collection Information exchange between service provision and toll charging (ISO/DIS 12855:2009) EN ISO 149
33、06, Road transport and traffic telematics Electronic fee collection Application interface definition for dedicated short-range communication (ISO 14906:2004) prEN ISO 17573, Electronic fee collection System architecture for vehicle related tolling (ISO/DIS 17573:2009) PD CEN/TR 16092:2011 CEN/TR 160
34、92:2011 (E) 7 CEN ISO/TS 25110, Electronic fee collection Interface definition for on-board account using integrated circuit card (ICC) (ISO/TS 25110:2008) ISO 4217, Codes for the representation of currencies and funds ISO/IEC 7810, Identification cards Physical characteristics ISO/IEC 7816-1, Ident
35、ification cards Integrated circuit(s) cards with contacts Part 1: Physical characteristics ISO/IEC 7816-2, Identification cards Integrated circuit cards Part 2: Cards with contacts Dimensions and location of the contacts ISO/IEC 7816-3, Identification cards Integrated circuit cards Part 3: Cards wit
36、h contacts Electrical interface and transmission protocols ISO/IEC 7816-4, Identification cards Integrated circuit cards Part 4: Organization, security and commands for interchange ISO/IEC 7816-6, Identification cards Integrated circuit cards Part 6: Inter-industry data elements for interchange ISO/
37、IEC 7816-8, Identification cards Integrated circuit cards Part 8: Commands for security operations ISO/IEC 14443-1, Identification cards Contactless integrated circuit cards Proximity cards - Part 1: Physical characteristics ISO/IEC 14443-2, Identification cards Contactless integrated circuit cards
38、Proximity cards Part 2: Radio frequency power and signal interface ISO/IEC 14443-3, Identification cards Contactless integrated circuit(s) cards Proximity cards Part 3: Initialization and anticollision ISO/IEC 14443-4, Identification cards Contactless integrated circuit cards Proximity cards Part 4:
39、 Transmission protocol ISO/IEC 15693-1, Identification cards Contactless integrated circuit cards Vicinity cards Part 1: Physical characteristics ISO/IEC 15693-2, Identification cards Contactless integrated circuit cards Vicinity cards Part 2: Air interface and initialization ISO/IEC 15693-3, Identi
40、fication cards Contactless integrated circuit cards Vicinity cards Part 3: Anticollision and transmission protocol ISO/IEC 18092, Information technology Telecommunications and information exchange between systems Near Field Communication Interface and Protocol (NFCIP-1) 3 Terms and definitions For t
41、he purpose of this document, the following terms and definitions apply. 3.1 Electronic Fee Collection (EFC) toll charging by electronic means via a wireless interface 3.2 enforcement process of compelling observance of a law, regulation, etc. PD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 8 3.3 Interope
42、rability ability of systems to provide services to and accept services from other systems and to use the services so exchanged to enable them to operate effectively together EXAMPLE For tolling interoperability aims at enabling a vehicle to drive through various toll domains while having only one OB
43、E operating under one contract with a toll service provider. 3.4 Onboard equipment (OBE) equipment fitted within or on the outside of a vehicle and used for toll purposes 3.5 tariff Scheme set of rules to determine the fee due for a vehicle in a toll domain for a EFC object at a certain day and time
44、 3.6 toll charge, a tax, a fee, or a duty in connection with using a vehicle within a toll domain 3.7 toll charger legal entity charging toll for vehicles in a toll domain 3.8 toll declaration (from OBE) statement (from the OBE of a vehicle) to a toll charger, not necessarily transmitted via a direc
45、t communication channel, that confirms the presence of a vehicle in a toll domain in a format agreed between the toll service provider and the toll charger 3.9 toll domain area or part of a road network where a EFC regime is applied 3.10 EFC point location within a toll domain where the OBE has to i
46、ssue a toll declaration 3.11 EFC regime set of rules, including enforcement rules, governing the collection of toll in a toll domain 3.12 toll schema generic term used for EFC regime and/or toll domain and/or toll system depending on the context 3.13 toll service service enabling users having only o
47、ne contract and one set of OBE to use a vehicle in one or more toll domains 3.14 toll service provider legal entity providing to his customers toll services on one or more toll domains for one or more classes of vehicles 3.15 toll system off board equipment and possible other provisions used by a to
48、ll charger for the collection of toll for vehicles PD CEN/TR 16092:2011 CEN/TR 16092:2011 (E) 9 3.16 EFC object distinguished part of a toll domain for which one or more tariff schema applies EXAMPLE An EFC object may be e.g. an area, all public roads within an area, a bridge, a zone, or a stretch of a road (network). 3.17 service user gener
