ImageVerifierCode 换一换
格式:PDF , 页数:46 ,大小:991.63KB ,
资源ID:592208      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。 如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-592208.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(CEN TR 16152-2011 Electronic fee collection - Personalisation and mounting of first mount OBE《电子收费 个性化和安装第一O山》.pdf)为本站会员(syndromehi216)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

CEN TR 16152-2011 Electronic fee collection - Personalisation and mounting of first mount OBE《电子收费 个性化和安装第一O山》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationPD CEN/TR 16152:2011Electronic fee collection Personalisation and mountingof first mount OBEPD CEN/TR 16152:2011 PUBLISHED DOCUMENTNational forewordThis Published Document is the

2、 UK implementation of CEN/TR 16152:2011.The UK participation in its preparation was entrusted to T e c h n i c a l C o m m i t t e e E P L / 2 7 8 , R o a d t r a n s p o r t i n f o r m a t i c s .A list of organizations represented on this committee can be obtained on request to its secretary.This

3、 publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. BSI 2011 ISBN 978 0 580 67647 5 ICS 35.240.60 Compliance with a British Standard cannot confer immunity from legal obligations.This Published Document was published

4、 under the authority of the Standards Policy and Strategy Committee on 31 May 2011.Amendments issued since publicationDate T e x t a f f e c t e dPD CEN/TR 16152:2011TECHNICAL REPORT RAPPORT TECHNIQUE TECHNISCHER BERICHT CEN/TR 16152 March 2011 ICS English Version Electronic fee collection - Persona

5、lisation and mounting of first mount OBE Perception de tlpage - Personnalisation et installation des quipements embarqus en premire monte Elektronische Gebhrenerhebung - Personalisierung und Einbau von Fahrzeuggerten der Erstausstattung This Technical Report was approved by CEN on 17 January 2011. I

6、t has been drawn up by the Technical Committee CEN/TC 278. 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, Netherl

7、ands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland 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

8、 any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TR 16152:2011: EPD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 2 Contents Page Foreword 3 Introduction .4 1 Scope 5 1.1 Background and expected benefits of first-mount OBE .5 1.2 Personalisation concept .5 2 Normative re

9、ferences 6 3 Terms and definitions .6 4 Symbols and abbreviations 6 5 Context Description .7 5.1 General 7 5.2 Actors and Roles .8 5.3 Overview of Assets . 10 5.4 Use cases 12 5.4.1 Initialisation: Mounting of OBE . 12 5.4.2 Initialisation: Assignment of individual data . 12 5.4.3 Initialisation: As

10、signment of vehicle data 13 5.4.4 Contracting of the OBE with the Service Provider 14 5.4.5 Enabling long range mobile communication . 15 5.4.6 Change of the vehicle for the same contract . 16 5.4.7 Cancellation of an existing contract . 17 5.4.8 Change of the contract for the same vehicle . 17 5.4.

11、9 Normal EFC use cases: charging and enforcement . 18 5.4.10 Repair and upgrade of the OBE 19 5.4.11 Change of vehicle properties 20 5.4.12 Decommissioning and replacement of the OBE . 21 6 Personalisation concept 22 6.1 Overall requirements 22 6.1.1 Functional requirements 22 6.1.2 Security Require

12、ments . 26 6.2 Vehicle interface requirements and constraints . 34 6.2.1 Introduction . 34 6.2.2 Installation principles . 35 7 Personalisation data . 35 7.1 EFC Attibutes 35 7.2 OBE related data . 37 7.3 Access protection information 37 7.4 Vehicle registration data 37 8 Recommendations 38 Bibliogr

13、aphy . 40 PD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 3 Foreword This document (CEN/TR 16152: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 elements of th

14、is document may be the subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights. PD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 4 Introduction With the increased use of OBE for EFC, the need for effective distribution is growing. The OBE could potentially

15、be integrated into the vehicle by the vehicle manufacturer as part of manufacturing process. The EETS provider (according to ECs European Electronic Toll Service business model) would in such a scenario be faced with the issue on how to personalize the data in the OBE, including the data related to

16、the contract between him and the user. This issue is relevant for both DSRC and satellite based OBEs. The issues addressed by the document include: 1) vehicle interfacing requirements and constraints a) vehicle data buses b) requirements and constraints from the automotive industry (e.g. in terms of

17、 electronic, mechanics) c) safety d) security 2) personalization requirements and constraints a) Access to the protected data inside the OBE e.g. ContractNumber b) Where are the EETS and contract data located? (inside the OBE or in a smart card). c) Activation and deactivation of the OBE This Techni

18、cal Report is not a substitute for regulations and standards and these should always be respected and used by manufacturers. PD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 5 1 Scope 1.1 Background and expected benefits of first-mount OBE It could be foreseen that in future the DSRC OBE will be delivered

19、by car manufacturer as a feature of the vehicle as they do today with car radio which are parts of the most sold vehicles. For the vehicle owner, the OBE supplier is the car manufacturer acting as an OEM (Original Equipment Manufacturer). The integration of first mount OBE by car manufacturer is the

20、 only way to create a future mass market for EFC application based upon DSRC as well as GNSS/CN, as at present the integration of this type of OBEs cannot be achieved except for heavy goods vehicles. Regarding DSRC, this is also an opportunity to extend the capability of todays EFC technologies by p

21、roviding increased quality of service, and possibly a greater range of services using in-vehicle electronics and resources. 1.2 Personalisation concept The personalisation procedure is the procedure where the EFC Service Provider initialize, customise, and finally activate the EFC interoperable serv

22、ice to OBE, for a customer with or without existing account. Two different kinds of personalisation methods can be defined: a) the personalisation procedure can be done “over the air”. In such case, personalisation data can be encoded in the OBE by the Service Provider over a secure air-link, or b)

23、personalisation data can be loaded directly by the driver into the OBE or Service Provider via a personal storage media. Theses are two fundamentally different approaches. The second method is perfectly fitted for critical initialisation data, such as encryption keys, to enable the driver to use the

24、 same EFC contract in different vehicles, and also to send personalisation data via post to a large number of customers. In any case, the personalisation procedure shall be implemented in a practical way. It was reminded that the very large majority of Service Provider distribution networks (and rel

25、ated point of sales) are not suited to allow point-to-point communication with vehicles. They are suited mainly for front-desk operations such as initialisation of an account, data collection of user information, and so on. For both methods, all access protection information, OBE contract informatio

26、n, shall be stored in a secure storage area within the OBE. During the personalisation procedure, any OBE and Service Provider service point will only communicate, but only further to a successful check of access rights. The use of an air-link for personalisation purposes includes some risks with re

27、spect to the security of the EFC system. The present document addresses appropriate measures to counteract these risks. Security services such as integrity protection and authentication protocols shall be defined to prevent unauthorised access to the content of the OBE memory area retaining personal

28、isation data. This statement of principles summarises essential aspects to be taken into account for the personalisation of OBE. These principles are valid: a) whether the EFC system is based upon DSRC, GNSS-CN, or a combination of both technologies; b) for permanently installed OBE; c) for both ori

29、ginal equipment manufacturers (first mount) and after sales permanently attached to the vehicle by OBE manufacturers. PD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 6 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, on

30、ly the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN ISO 14906, Road transport and traffic telematics Electronic fee collection Application interfaces definition for dedicated short-range communication (ISO 14906:2

31、004) CEN ISO/TS 175751, Electronic fee collection Application interface definition for autonomous systems Part 1: Charging (ISO/TS 17575-1:2010) ISO 11568-2, Banking Key management (retail) Part 2: Symmetric ciphers, their key management and life cycle prEN ISO 17573, Electronic fee collection Syste

32、m architecture for vehicle related tolling (ISO 17573:2010) 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 on-Board Equipment (OBE) equipment fitted within or on the outside of a vehicle and used for toll purposes 3.2 electronic fee collecti

33、on (EFC) toll charging by electronic means via a wireless interface 3.3 roadside equipment equipment located along the road transport network, for the purpose of communication and data exchanges with on-board equipments 3.4 Toll Charger legal entity charging toll for vehicles in a toll domain 3.5 To

34、ll Service Provider legal entity providing to his customers toll services on one or more toll domains for one or more classes of vehicles NOTE The Toll Service Provider may provide the OBE or may provide only a magnetic card or a smart card to be used with OBE provided by a third party (like a mobil

35、e telephone and a SIM card can be obtained from different parties). The Toll Service Provider is responsible for the operation (functioning) of the OBE. 4 Symbols and abbreviations CC Common Criteria AID Application Interface Definition BST Beacon Service Table CESARE Common EFC System for ASECAP Ro

36、ad tolling European system PD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 7 DSRC Dedicated Short-Range Communication DTCO Digital TaCOgraph EAcK Element Access Key EAuK Element Authentication Key EC European Commission ECU Electronic Control Unit EID Element Identifier EFC Electronic Fee Collection HGV H

37、eavy Goods Vehicle KVC Key Verification Code L1 Layer 1 of DSRC (Physical Layer) L2 Layer 2 of DSRC (Data Link Layer) L7 Layer 7 of DSRC (Application Layer) LLC Logical Link Control MAC Message Authentication Code MEAcK Master Element Access Key MEAuK Master Element Authentication Key MMI Man-Machin

38、e Interface OBE On-Board Equipment OBU On-Board Unit PAN Personal Account Number RSE Road-Side Equipment T-APDU Transfer-Application Protocol Data Unit VST Vehicle Service Table 5 Context Description 5.1 General In many existing systems OBEs are delivered by the Service Provider. The process to add

39、vehicle and service user data is normally a part of the contract between the Service Provider and the OBE manufacturer. In this situation there is one Security Domain within which full trust must exist. As it is foreseen that the OBE will be integrated with the vehicle the personalization process of

40、 the OBE must support that the OBE is mounted to the Vehicle when the personalisation takes place. PD CEN/TR 16152:2011CEN/TR 16152:2011 (E) 8 Furthermore, it is possible that different contracts issued by different Service Providers will be in place and related sets of personalisation assets implem

41、ented in the same OBE throughout its lifetime. 5.2 Actors and Roles The following actors have been identified as actors who are related to assets related to the OBE. a) Toll Charger. He is responsible for the collection of road usage charges on a specific part of the road infrastructure. He is inter

42、ested in personalisation data as far as he needs them for the determination or checking of the charges. His special interest is in the correctness of the vehicle data and of the Service Provider identification (assuming that the Service Provider guarantees him for the payment of the fees if he can p

43、roof the usage of the road infrastructure). b) Service Provider. He offers the EFC service to users of the road infrastructure. A user subscribing to the service will pay the fees to the Service Provider who will forward them to the appropriate toll charger according to the usage. To contribute to t

44、he determination of the road usage and the charges due, the Service Provider will operate the OBE mounted to the vehicle of the service user, after having added his personalization data to it. Anyway, the personalization data responsibility is kept by the Service Provider towards the User and the To

45、ll Charger. His interest is that only road usages of customers having subscribed his service are charged to him and that he can assign the charges to the appropriate service user. c) OBE Manufacturer. He produces the OBE and delivers it to the vehicle manufacturer to be mounted to a vehicle. d) Vehi

46、cle Manufacturer. He is responsible for the integration of the OBE into the vehicle. e) Vehicle registration authority. The involvement of this actor in the personalization of first mount OBE is to be defined. In any case it may serve as a trusted source of at least part of the vehicle data. f) EFC

47、service user. He subscribes to the EFC service of a Service Provider for a specific vehicle with an OBE. His interest is that he is charged only for his road usage. g) Mobile communication provider (in case of GNSS system). He offers a wide range communication service that may be used not only durin

48、g EFC, but also for personalization of the OBE. The OBE has to be initialized for the specific service before it can use the communication channel. These actors are present in the EFC environment independent from the issue of personalisation of first mount OBE. Not all of them must have an active ro

49、le in personalisation - some of them may just have a specific interest (like for instance the toll charger). For retrofitted OBE it is usually assumed that the overall responsibility for this OBE is at the Service Provider. This also covers the responsibility for the personalisation. The Service Provider may get the OBE from the OBE Manufacturer at a stage where part of the personalisation took place already. But as soon as the Service Provider takes over the OBE, the OBE Manufacturer is not involved any more and in case there is some information ne

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1