1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationPD CEN/TR 16092:2011Electronic fee collection Requirements for pre-paymentsystemsPD CEN/TR 16092:2011 PUBLISHED DOCUMENTNational forewordThis Published Document is the UK impleme
2、ntation of CEN/TR16092:2011.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Road transport informatics.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryp
3、rovisions of a contract. Users are responsible for its correctapplication. BSI 2011ISBN 978 0 580 67649 9ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strate
4、gy Committee on 31 March 2011.Amendments issued since publicationDate 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-payment systems Perception d
5、e 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 national standards bodies
6、 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 Kingd
7、om. 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. CEN/TR 16092:2011: EPD
8、CEN/TR 16092:2011CEN/TR 16092:2011 (E) 2 Contents Page Foreword 4Introduction . 51 Scope 62 Normative references 63 Terms and definitions . 74 Abbreviations . 95 Interoperability Issues . 105.1 Interoperability based on EFC Roles Model . 105.2 Interoperability and Payment . 116 Classification of Pre
9、-Pay solutions . 116.1 Pre-Pay Account held in Central System 116.2 Pre-Pay Account held on OBE . 127 Requirements for Pre-Pay account held in Central Systems 137.1 General 137.2 Business Process Requirements . 137.2.1 General 137.2.2 Issuing of an EFC contract to the Service User . 137.2.3 Personal
10、isation of OBE . 157.2.4 Loading of value onto an account . 157.2.5 Charging of Toll . 177.2.6 Invoicing of the Service User . 177.2.7 Refund of residual amount . 177.2.8 Clearing of Transactions . 187.2.9 Handling of Complaints 187.2.10 Security Considerations . 187.3 Technical Requirements . 187.3
11、.1 Requirements for OBE 187.3.2 Requirements for POS Networks . 187.3.3 Requirements for Information and Payment Flow (Interfaces) . 197.4 Legal and Functional Constraints 197.4.1 Legal Considerations 197.4.2 Functional Constraints 218 Requirements for Pre-Pay account held on OBE . 228.1 Prerequisit
12、es 228.2 Business Process Requirements . 228.2.1 Issuing of the Pre-Pay mode 228.2.2 Personalisation of OBE . 228.2.3 Loading of stored value onto a VBD 238.2.4 Loading of stored value into the OBE . 238.2.5 Charging of the toll 248.2.6 Clearing of transactions 268.2.7 Hotlisting / Enforcement . 278
13、.2.8 Invoicing of the Service User . 278.2.9 Refund of residual amount . 288.2.10 Proof of Transactions 288.2.11 Handling of Complaints 288.2.12 Security Considerations . 288.3 Technical Requirements . 298.3.1 Requirements for Value Unit bearing User Media 29PD CEN/TR 16092:2011CEN/TR 16092:2011 (E)
14、 3 8.3.2 Requirements for OBE 308.3.3 Requirements for POS Networks . 318.3.4 Requirements for Information and Payment Flow (Interfaces) . 318.4 Legal and Functional Constraints 318.4.1 Legal Considerations 318.4.2 Functional constraints 339 Invoicing of the Service User . 349.1 General 349.2 VAT co
15、nsiderations . 349.3 Business model considerations 359.4 Invoice considerations 3510 Gaps in terms of Standards and recommendations 3710.1 Pre-Pay Account held in Central System 3710.2 Pre-Pay Account held on OBE . 3710.3 Recommendation for next steps 37Annex A (informative) Examples of implementati
16、ons . 38Bibliography 40PD CEN/TR 16092:2011CEN/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 secretariat of which is held by NEN. Attention is drawn to the possibility that some of the e
17、lements 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 given to CEN by the European Commission and the European Free Trade Association. PD CEN/TR 160
18、92:2011CEN/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 Toll Service Provider (TSP) and the Service User (SU). Pre-conditions of such a contractual agre
19、ement 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 pre-conditions; SUs with occasional needs to use an EFC system (mainly from the private sector
20、) 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 in an interoperable EFC system, which may otherwise not be open to them. To meet the requirem
21、ents 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 private users are concerned legislation could ask for anonymous payment modes as nobody can b
22、e 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 defining necessary standards in that field the requirements of a universal Pre-Payment system able
23、to communicate with the OBE have to be evaluated, especially with regard to validity and feasibility for private users. PD CEN/TR 16092:2011CEN/TR 16092:2011 (E) 6 1 Scope This technical report (TR) analyses requirements for a universal Pre-Pay account system for EFC including the following issues:
24、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 system and categorise possible different types of pre-pay solutions, in terms of functionality,
25、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, pursuit of and prudential supervision of the business of electronic money institutions and whethe
26、r 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 by entities but do not require a full bank license. The technical report will describe the curr
27、ent 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 enablers needed in order for the market to provide viable pre-payment solutions in a European con
28、text. 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 better understanding and readability alternative a) has been decided (this refers to Clause 8 an
29、d 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 return for invest for any TSP regarding the system architecture requirements and other obligat
30、ions (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 individual preconditions of their tolling regime and of market acceptance. 2 Normative references The
31、 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 15509, Road transport and traffic telematics Elec
32、tronic 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 14906, Road transport and traffic telematics Electronic fee collection Application interface defi
33、nition 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:2011CEN/TR 16092:2011 (E) 7 CEN ISO/TS 25110, Electronic fee collection Interface definition for on-board acc
34、ount 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, Identification cards Integrated circuit(s) cards with contacts Part 1: Physical characteristics ISO/
35、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 with contacts Electrical interface and transmission protocols ISO/IEC 7816-4, Identification cards
36、 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/IEC 7816-8, Identification cards Integrated circuit cards Part 8: Commands for security operati
37、ons 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 Proximity cards Part 2: Radio frequency power and signal interface ISO/IEC 14443-3, Identificat
38、ion 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: Transmission protocol ISO/IEC 15693-1, Identification cards Contactless integrated circuit car
39、ds 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, Identification cards Contactless integrated circuit cards Vicinity cards Part 3: Anticollision and tr
40、ansmission 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 the purpose of this document, the following terms and definitions apply. 3.1 Electronic Fee Coll
41、ection (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:2011CEN/TR 16092:2011 (E) 8 3.3 Interoperability ability of systems to provide services to and accept services from other systems and to
42、 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 OBE operating under one contract with a toll service provider. 3.4 Onboard equipment (OBE) equipme
43、nt 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 3.6 toll charge, a tax, a fee, or a duty in connection with using a vehicle within a toll domai
44、n 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 direct communication channel, that confirms the presence of a vehicle in a toll domain in a format ag
45、reed 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 issue a toll declaration 3.11 EFC regime set of rules, including enforcement rules, governing the
46、 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 one contract and one set of OBE to use a vehicle in one or more toll domains 3.14 toll service pr
47、ovider 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 toll charger for the collection of toll for vehicles PD CEN/TR 16092:2011CEN/TR 16092:2011 (E) 9 3
48、.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 generic term used for the customer of a toll service provider, one liable for toll, the owner of the vehicle, a fleet operator, a driver etc. depending on the context 3.18 value units bearing device (VBD) device in the hand of the Service user that contains value units 4
