Internet copy

Transcription

1 EasyGo+ OBU personalisation, configuration and operating parameters Enclosure B to Document 202 Roadside and on board equipment This copy of the document was published on and is for information purposes only. It may change without further notice. Date 2 May 2013 Page 1 of 24

2 Table of contents DOCUMENT REVISION HISTORY... 3 ABBREVIATIONS INTRODUCTION PURPOSE OF THE DOCUMENT ATTRIBUTE DATA ATTRIBUTE 0: EFC-CONTEXT MARK ATTRIBUTE 32: PAYMENTMEANS ATTRIBUTE 4: CONTRACTAUTHENTICATOR ATTRIBUTE 16: VEHICLELICENCEPLATENUMBER ATTRIBUTE 17: VEHICLE CLASS ATTRIBUTE 18: VEHICLE DIMENSIONS ATTRIBUTE 19: VEHICLE AXLES ATTRIBUTE 20: VEHICLE WEIGHT LIMITS ATTRIBUTE 22: VEHICLE SPECIFIC CHARACTERISTICS ATTRIBUTE 23: VEHICLEAUTHENTICATOR ATTRIBUTE 24: EQUIPMENTOBU ID ATTRIBUTE 26: EQUIPMENTSTATUS ATTRIBUTE 33: RECEIPT DATA ATTRIBUTE 34: RECEIPT DATA OPERATING AND CONFIGURATION PARAMETERS MANUFACTURERID AND EQUIPMENTCLASS SETMMI SECURITY FEATURES KEYS INITIAL DATA EX WORKS REFERENCES STANDARDS AND EXTERNAL DOCUMENTS EASYGO DOCUMENTS Date 2 May 2013 Page 2 of 24

3 Document revision history Version Date Author Main changes V HHA First draft V HHA Draft for comments V RL, HHA Minor changes after review by RL V HHA Default data ex works added V HHA Data req. for Sund&Belt, Öresundsbron added V HHA Minor changes in ch , 2.4.1, and 5 V HHA No changes to V0.23, RC version V HHA Doc. release V HHA Ch. 2.4 LPN length corrected to 14 V1.50 HHA Adaptation as enclosure to EasyGo document 202 V HHA VehicleSpecificCharacteristics.EnvironmentalCharacteristics. EuroValue: Value of 15 for EEV vehicles added V HHA Editorial changes V HHA Ch : Exception for coding AT and DE LPN removed HHA Context data for test period added HHA Chapter 2.7.1: value for VehicleAxlesNumber.NumberOfAxles.Tractor restricted to 2, 3, HHA Ch EFCContextMark data added for S&B HHA References updated Approved by steering committee Date 2 May 2013 Page 3 of 24

4 Abbreviations Abbreviation, Term Description TSP CI SU TC PSP Penalty Fee EETS POS RSE OBU EFC MLFF PAN SP HGV MII IIN Toll Service Provider, Contract issuer, issuer Toll Service Provider, Contract issuer, issuer Service User, customer, Toll Charger, Operator Payment Service Provider Fee to be paid by enforced users to avoid prosecution ( Ersatzmaut ) European Electronic Toll Service Point of Sales Roadside Equipment On Board Unit Electronic Fee Collection Multi Lane Free Flow Personal Account Number Service Provider Heavy Goods Vehicle Major Industry Identifier Issuer Identifier Number Date 2 May 2013 Page 4 of 24

5 1 Introduction This document specifies in detail data content and use of this data for interoperable OBU dedicated for EASYGO+. Note: There can be differences between OBU requirements on attributes and the data format specified in this document, but this shouldn t be contradictional. 1.1 Purpose of the document ATTRIBUTES (EID>0) AttrId Type Length in bytes Read Write Remarks CONTRACT Information associated with the service rights of the Toll Service Provider (TSP=CI) EFC Context Mark Yes No Contains the TSP Identification (transmitted as part of the VST) PAYMENT Data associated with the Payment transaction. Includes: the Personal Account Number, including PaymentMeans the Payment Means Issuer (identified by Yes No (including PAN) the IIN), The PAN Expiry Date The payment means Usage Control Contract Authenticator Yes No Value defined by the CI (acc. to EN15509, Attribute is not ) VEHICLE Information pertaining to the identification and characteristics of the vehicle. Fixed to Length of the Attribute, incl. country code, VehicleLicencePlateNu = 17 Yes No Alphabet Indicator and length. **) mber bytes VehicleClass Yes No VehicleDimensions Yes No VehicleAxles Yes No VehicleWeightLimits Yes No VehicleSpecificCharacte ristics Yes No VehicleAuthenticator Yes No Value defined by the CI (acc. to EN15509, Attribute is not ) EQUIPMENT Information pertaining to the OBU. EquipmentOBUId (=4+1) Yes No Length of EquipmentOBUID is fixed to 4+1 bytes as specified in EN EquipmentStatus Yes Yes Include transaction counter and black list flag RECEIPT Information associated with a specific session, including both financial and operational data. ReceiptData1 (last) Yes Yes ReceiptData2 (penultimate) Yes Yes **) Acc. to EN15509 the length of this Attribute is fixed to 17 bytes, but for compatibility reasons only the first. 10 significant characters can be used (see chapter 2.4) Date 2 May 2013 Page 5 of 24

6 Read and Write define access rights to a given Attribute for GET, GET Stamped or SET used by RSE. Each Attribute contains one or several data fields according to EN Personalisation must be made by the Contract Issuer according to the rules as specified in this specification. For further details on specification of Attributes and security features which have to be implemented and supported by the OBU, see [IAP] and [OBU_req]. 2 Attribute data The general structure of Attributes and their data elements is shown in Annex A. Further information see [EFC API], chapter EFC attributes. 2.1 Attribute 0: EFC-Context Mark General The EFC-ContextMark denotes a specific EFC in the OBE, comprising the organisation that issued the contract, the type of contract and the version. EFC- ContextMark data is transmitted in VST as part of the ApplicationContextMark to enable the RSU to select the suitable EFC application as well the appropriate OBU data element, if the OBU is presenting more data elements. ContractProvider TypeOfContract Identifies the organisation that issued the service rights given in the Contract, i.e. the Toll Service Provider. Numbers shall be assigned on a national basis. It is outside the scope of this standard to identify the data that specify the service rights. ContractProvider-specific designation of the rules that apply to the Contract. Allows, e.g., for the determination of the tariff or designating the type of purse associated with the contract. ContextVersion ContextVersion denotes the implementation version of the concerned contract within the of the given ContractProvider, value assigned at the discretion of the ContractProvider. The ContextVersion may also be used as a security key reference. To differentiate between test contracts and operational user contracts, different data is provided; for historical reasons in EasyGo differentiation in EFC-ContextMark for OBU from different manufacturers for the same TSP is required for the time being. Date 2 May 2013 Page 6 of 24

7 2.1.2 Initial personalization for OBU issued by ASFINAG as TSP OBU Type OBU3021-G from Kapsch TrafficCom (KAPSCH AT) ManufacturerId: 01 h EquipmentClass: 7106 h Data element Use in ASFINAG Data for testphase Data for production phase ContractProvider C04001 h C04001 h TypeOfContract F200 h 7100 h ContextVersion 05 h 05 h OBU Type FZ3458-GO from EFKON (FENRITS) ManufacturerId: 1B h EquipmentClass: 0340 h Data element Use in ASFINAG Data for testphase Data for production phase ContractProvider C04001 h C04001 h TypeOfContract F200 h 7100 h ContextVersion 06 h 06 h Initial personalization for OBU issued by BroBizz Remark Remark OBU Type OBU K from Kapsch TrafficCom (KAPSCH SE) ManufacturerId: 03 h EquipmentClass: 7324 h Data element Use in ASFINAG Data for testphase Data for production phase Remark ContractProvider h h TypeOfContract ContextVersion Date 2 May 2013 Page 7 of 24

8 2.2 Attribute 32: PaymentMeans General The attribute PaymentMeans holds contract data as PAN, ExpiryDate and UsageControl: PersonalAccount Number (PAN) PaymentMeans ExpiryDate PaymentMeans UsageControl Coded according to financial institutions, consists of the Major Industry Identifier (MII), the Issuer Identifier Number (IIN, including the MII), the account number and a check digit (calculated with the Luhn algorithm).; acc. to ISO7812 Expiring date of payment means. Payment means expires at 24h of PaymentMeans ExpiryDate. Indicates issuer s specified restrictions on the geographic usage and services allowed for the applications Information about use in ASFINAG- Information about use in ASFINAG- Data element PersonalAccount Number (PAN) PaymentMeans ExpiryDate PaymentMeans UsageControl Use in ASFINAG set to zero Optional (or set to Data xxxxxxxxxxxxx d Date of personalization + 5 years 0000 h Information about use in XXX- See ASFINAG. 2.3 Attribute 4: ContractAuthenticator Remark General This attribute is not specified in EN If implemented in OBU, it can be used for compatibility reasons in existing tolling s. Contract Authenticator Coding up to the SP set to zero Date 2 May 2013 Page 8 of 24

9 2.3.2 Information about use in ASFINAG- Not used Information about use in XXX- See ASFINAG. 2.4 Attribute 16: VehicleLicencePlateNumber General This attribute is holding information about the vehicles licence plate content (LPN) and the registering country. The licence plate information can have up to 14 characters acc. to 15509, but for compatibility reasons only up to 10 characters can be used for identification, because in some systems only the first 10 characters will be processed after RSE. The licence plate information always shall be padded with NUL characters after the last significant character to achieve the total length of 14. For the LPN only latinalphabetno1 and upper case letters, numbers (without any spaces and hyphens!) and shall be used in personalisation. Non Latin-1 characters are to be coded as lower case letters applying a translation table acc. to ISO/DIS140906:2008. CountryCode Two letter countrycode(iso alpha-2 code). coded in ITA-2 alphabet acc. to EN14816 AlphabetIndicator Latin alphabet No1(ISO8859-1) Length determinant 14 LPN Up to10 significant characters, padded with NUL to achieve 14 chars Information about use in ASFINAG- Use of only latinalphabetno1 and upper case characters shall be used in personalisation. Non Latin-1 characters to be coded as lower case letters applying a translation table acc. to ISO/DIS140906:2008. If LPN contains a non Latin-1 AlphabetIndicator, characters are remapped at RSE acc. to special rules (see pren ISO 14906: , AnnexE [EFC_API] ). Although LPN length is defined by EN15509 with a fixed length of 14characters, the data element should contain only max. 10 significant characters, because LPN information is truncated to 10 characters at RSE for historical reasons. Shorter LPN are always padded with NUL to the maximum length (14chars.). Date 2 May 2013 Page 9 of 24

10 Data element Use in ASFINAG Data CountryCode xx xxxx xxxx b AlphabetIndicator b Length determinant b LPN xxxx xxxx xxxx xxxx xxxx h Information about use in XXX- See ASFINAG. 2.5 Attribute 17: Vehicle Class Remark General The attribute VehicleClass is holding information about trailer presence, the vehicles Harmonised European vehicle Class and a local class, if defined by the SP (see [CARDME]). The data element Trailer Presence Indicator is used to indicate whether the vehicle is towing a trailer (Trailer not present = 0, trailer present= 1). If the OBU allows to manually declare additional trailer axles, TrailerPresencerIndicator shall be set to 0 at initial personalization; the TrailerPresencerIndicator will be automatically set to 1 by the OBU logic, if additional axles are declared. The data element EuropeanVehicleGroup is based on UNECE vehicle classes [UNECE]. European Vehicle Group Description Characteristics UNECE Class 0 Motorcycles 2 or 3 wheels L 1 small passenger vehicles seats 8+driver M1 (See note 1) 2 Light goods vehicles weight < 3.5 t N1 (See note 2) 3 Large passenger vehicles seats > 8 + driver M2, M3 (See note 3) 4 heavy goods vehicles (up to 12 t) weight > 3.5 t and <= 12 t N2 5 heavy goods vehicles (over 12 t) weight > 12 t N3 6 Not used 7 other vehicles weight > 3.5 t See note 4 Note 1: Assumed to be 3.5 tonnes, otherwise assigned to group 7 Note 2: Assumed to have 2 axles, otherwise the vehicle is assigned to group 7 Note 3: Note that a few of these vehicles may be 3.5 tonnes Date 2 May 2013 Page 10 of 24

11 Note 4: Any vehicle not defined in European Vehicle Groups 0-5. This includes small passenger vehicles weighing more than 3.5 tonnes. Weight is the information F2 in the European Certificate of Immatriculation for vehicles according to [Reg_doc]. TrailerPresencerIndi cator EuropeanVehicle Group Trailer no/yes European vehicle group based on UNECE LocalVehicleClass Local vehicle class, defined by the SP Optional (or set to Information about use in ASFINAG- The data element Trailer Presence Indicator is set to 0 at initial personalization. The data element EuropeanVehicleGroup is used to distinguish between trucks, bus (both > 3.5 t) and other vehicles. Vehicles in European Vehicle Groups 3, 4, 5 and 7 are considered to be heavy vehicles in terms of the EETS (weighing more than 3.5 tonnes); they are relevant for the truck tolling system in Austria. Data element Use in ASFINAG Data Remark TrailerPresencerIndicator EuropeanVehicle Group xxxx b LocalVehicleClass Not used (set to 0000 b Information about use in XXX- See ASFINAG. 2.6 Attribute 18: Vehicle Dimensions General The attribute VehicleDimensions is holding information about the nominal overall dimensions of the vehicle acc. to ISO b VehicleLengthOve rall VehicleHeightOve rall Nominal maximum overall length of the vehicle according to ISO 612, in dm, rounded to the next dm. Nominal overall unladen height, according to ISO 612, in dm, rounded to the next dm. Optional (or set to Optional (or set to Date 2 May 2013 Page 11 of 24

12 VehicleWidthOver all Nominal overall width, according to ISO 612, in dm, rounded to the next dm Information about use in ASFINAG- Not used Information about use in XXX- See ASFINAG. 2.7 Attribute 19: Vehicle Axles Optional (or set to General The attribute VehicleAxles is holding information about the first axle s height, the usage of dual tyres and the number of axles (including drop axles) for tractor vehicle and trailer. VehicleFirstAxleHeight Bonnet height, measured over the front axle, in dm, rounded to the next dm Optional (or set to VehicleAxlesNumber VehicleAxlesNumber.TyreType: Claimed tyre type Optional (or set to VehicleAxlesNumber VehicleAxlesNumber VehicleAxlesNumber.NumberOfAxles.Trailer: number of axles on trailer including drop axles VehicleAxlesNumber. NumberOfAxles.Tractor: number of axles of the tractor unit including drop axles If the OBU allows to manually declare trailer axles, VehicleAxlesNumber.NumberOfAxles.Trailer shall be set to 0 at initial personalization; VehicleAxlesNumber.NumberOfAxles.Trailer will be automatically set by the OBU logic, if additional axles are declared. If not other agreed for EasyGo+, VehicleAxlesNumber.NumberOfAxles.Tractor shall be set to values 2, 3, 4 only at personalization (Value4 will be interpreted as 4 or more axles at the tractor vehicle). If the attribute VehicleClass. EuropeanVehicle Group is set to 3 (Large passenger vehicles), declaration of additional trailer axles by user is prevented by the OBU logic Information about use in ASFINAG- Vehicle classification is based in Austria on the number of axles of the complete HGV combination tractor + trailer. There is class 2, 3 and 4+ corresponding to the sum of axles Date 2 May 2013 Page 12 of 24

13 number (4 and more axles give class 4+). For bus the axles of a trailer will not be counted at classification. The number of axles of the towing vehicle (tractor) is stored in VehicleAxlesNumber. NumberOfAxles.Tractor at initial personalization (called the base class ); user declared axles will be stored in ehicleaxlesnumber.numberofaxles.trailer Information about use in XXX- See ASFINAG. 2.8 Attribute 20: Vehicle Weight Limits General The attribute VehicleWeightLimits is holding information about vehicle weight limits acc. to ISO1176. VehicleMaxLadenW eight VehicleTrainMaxim umweight VehicleWeightUnlad en Maximum permissible total weight including payload, according to ISO kg units, rounded down to the next 10kg step. Maximum permissible weight of the complete vehicle train, as defined in ISO kg units, rounded down to the next 10kg step. Nominal unladen weight, according to ISO 1176 in 10 kg units, rounded down to the next 10 kg step Information about use in ASFINAG- Not used Information about use in XXX- See ASFINAG. Optional (or set to Optional (or set to Optional (or set to Date 2 May 2013 Page 13 of 24

14 2.9 Attribute 22: Vehicle Specific Characteristics General The attribute VehicleSpecificCharacteristics is holding information about environmental characteristic (emission class), engine type and other vehicle characteristics. EnvironmentalCharact eristics.eurovalue EnvironmentalCharact eristics.copvalue Euro value as defined in EC directive 88/77/EEC and consecutive amendments Cop value as defined in EC directive 2003/127/EEC. Optional (or set to EngineCharacteristics Claimed engine type Optional (or set to DescriptiveCharacterist ics Vehicle shapes for silhouette Optional (or set to FutureCharacteristics Reserved for future use Optional (or set to Coding of VehicleSpecificCharacteristics.EnvironmentalCharacteristics.EuroValue: The EURO emission class is to be coded 1:1 as value to this data field, for EEV classified vehicles value 15 shall be used Information about use in ASFINAG- In ASFINAG only the data element EnvironmentalCharacteristics.EuroValue is used to determine the EURO Emission Class. The EURO emission class, coded in VehicleSpecificCharacteristics.EnvironmentalCharacteristics.EuroValue is interpreted at RSE for tariff calculation as follows: EuroValue ASFINAG Tariff class 0= no entry EEV C C C C B B A A Information about use in XXX- See ASFINAG. Date 2 May 2013 Page 14 of 24

15 2.10 Attribute 23: VehicleAuthenticator General This attribute is not specified in EN If implemented in OBU, it can be used for compatibility reasons in existing tolling s. VehicleAuthenticator Coding up to the SP Information about use in ASFINAG- Not used Information about use in XXX- See ASFINAG Attribute 24: EquipmentOBU ID set to zero General The EquipmentOBUId shall be a unique identification number assigned to OBU by the manufacturer during the production process. EquipmentOBUId Coding and personalization by the manufacturer Information about use in ASFINAG- The EquipmentOBUId is used to identify a specific OBU together with the ManufacturerId (submitted in VST) and EFC-ContextMark.ContractProvider e.g. for blacklisting purposes. Data element EquipmentOBUId Use in ASFINAG Data Remark Information about use in XXX- See ASFINAG. Date 2 May 2013 Page 15 of 24

16 2.12 Attribute 26: EquipmentStatus General The attribute EquipmentStatus is holding EFC application-related information pertaining to the status of the equipment. The coding of the data element EquipmentStatus is left to the toll charger. The coding of EquipmentStatus has the bit ordered substructure LBLL CCCC CCCC CCCC, where: CCCC CCCC CCCC: The lower 12 bits of this attribute are used for a transaction counter (increased by RSE at each transaction), which can be used for proving some instances of fraud. LBLL = 4 bits for local use (coding and use is at the discretion of the operator). Bit B can be used for blacklisting purposes ( Blacklist Bit ). CCCC CCCC CCCC Transaction Counter LBLL Where B= Blacklist Bit Set to zero at initial personalization If the BlistBit= 1, the OBU can be treated as blacklisted (Use (set/ reset and interpretation up to agreements betweeen SP and TC) Information about use in ASFINAG- Data element TransactionCounter BlacklistBit Use in ASFINAG Mandatory update at RSE Interpretation at RSE for blacklisting optional Optional (or set to Data Remark Due to the limited benefit of the transaction counter of an OBU operating in different toll s, there is no automated interpretation active. Blacklist bit: At Austrian RSE set/reset of the BlacklistBit is possible, but no procedures are defined yet to do it so (Setting/ resetting the BlacklistBit is reserved to the TSP, or have to be agreed between TSP and TC). Anyway, if the BlacklistBit is set, the OBU is treated like to be on the blacklist Information about use in XXX- See ASFINAG. Date 2 May 2013 Page 16 of 24

17 2.13 Attribute 33: Receipt Data General The attribute ReceiptData1 contains information associated with the last transaction, including both financial and operational data according to EN ISO This attribute is written by RSE only; initial personalization shall be done with zeros. It is used only by the TC who has written it Information about use in ASFINAG- The attribute ReceiptData1 contains information associated with the last transaction, including both financial and operational data according to EN ISO This attribute is written by RSE only; initial personalization shall be done with zeros. It is used for enforcement purposes only by ASFINAG Information about use in XXX- See ASFINAG Attribute 34: Receipt Data General The attribute ReceiptData2 contains information associated with the penultimate transaction, including both financial and operational data according to EN ISO This attribute is written by RSE only; initial personalization shall be done with zeros. It is used only by the TC who has written it Information about use in ASFINAG- The attribute ReceiptData2 contains information associated with the penultimate transaction, including both financial and operational data according to EN ISO This attribute is written by RSE only; initial personalization shall be done with zeros. It is used for enforcement purposes only by ASFINAG Information about use in XXX- See ASFINAG. Date 2 May 2013 Page 17 of 24

18 3 Operating and configuration parameters 3.1 ManufacturerId and EquipmentClass Manufacturer identifier (ManufacturerId) and EquipmentClass are written by the manufacturer to the OBU. This information is submitted in VST and can be used at RSE e.g. to select transaction operating parameters suitable for this OBU. ManufacturerId Value assignment see ENV ISO Register of manufacturers. EquipmentClass Shall be used to showdifferent OBU versions from same manufacturer 3.2 SetMMI In different versions of EN14906 different ActionParameters for SetMMI were defined. For EASYGO+ the RSE shall use Container choice = 69 dec. 3.3 Security features Use of AccessCredentials Acc. to EN use of AccessCredentials is not, it is allowed to choose the security level. For EASYGO+ use of security level 1(= use of AccessCredentials) is KeyReferences For EASYGO+ the key reference range for TSP Authenticator (CI authenticator, KeyRef to be used in the first GET_STAMPED.request) is 111 to 114. For EASYGO+ the key reference range for TC Authenticator (Operator authenticator, KeyRef to be used in the second GET_STAMPED.request) is 115 to Keys For the test phase use of a test key set different to the operating keys is recommended. Date 2 May 2013 Page 18 of 24

19 5 Initial data ex works Unpersonalised OBU shall be delivered ex works with the following default settings : AID: Unpersonalised OBU must always come with AID = 0 so it can not cause transactions with the RSE in transit. EquipmentClass, ManufacturerId, ObeStatus: Data settings up to the manufacturer. TypeOfContract: FF 00 h Attribute data: Data element ContractProvider TypeOfContract EquipmentOBUId Setting ex works Coding acc. to purchasers requirements FF 00 h Coding and personalization by the manufacturer All other attribute data shall be zero for OBU ex works (apart from EquipmentObuId, or when otherwise agreed between supplier and SP. Date 2 May 2013 Page 19 of 24

20 6 References Standards and external documents For dated references, subsequent amendments to or revisions of any of these publications apply only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. Reference Document Ref Date / Version Document title [L1] EN Road Transport and Traffic Telematics (RTTT) Dedicated Short-Range Communication (DSRC) Physical layer using microwave at 5.8 GHz [L2] EN Road Transport and Traffic Telematics (RTTT) Dedicated Short-Range Communication (DSRC) DSRC data link layer: Medium access and logical link control 2007/ 2003 ISO15628 / EN12834 Road Transport and Traffic Telematics (RTTT) Dedicated Short-Range Communication (DSRC) DSRC Application Layer 2004 EN Road Transport and Traffic Telematics (RTTT) Dedicated Short-Range Communication (DSRC) Profiles for RTTT applications [AVI No] EN ISO Road Traffic and Transport Telematics (RTTT) Automatic Vehicle and Equipment Identification Numbering and Data Structures [EFC API] ISO/DIS Road Traffic and Transport Telematics (RTTT) Electronic Fee Collection Application interface definition for dedicated short range communication [OBU DSRC tests] CEN ISO/TS Road Traffic and Transport Telematics (RTTT) Electronic Fee Collection Testprocedures for user and fixed equipment - Part 2: EFC application interface conformance test specification [ETSI] EN Electromagnetic Compatibility and Radio Spectrum Matters (ERM) - RTTT -DSRC- transmission equipment Date 2 May 2013 Page 20 of 24

21 Reference Document Ref Date / Version Document title [ISO CC] EN ISO Codes for the representation of names of countries and their subdivisions Part 1: Country code [ISO 4217] ISO 4217 Codes for the representation of currencies and funds [ISO ] EN ISO/IEC Identification cards - Identification of issuers - Part 1: Numbering system [ISO ] ISO Banking -- Approved algorithms for message authentication -- Part 1: DEA [ASN.1] ISO/IEC Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation [ASN.1 PER] ISO/IEC Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER) [CEI EN ] IEC Primary batteries - Part 4: Safety standards for lithium batteries [EN ] EN V 1.4.1:2002 Electromagnetic compatibility and Radio spectrum Matters (ERM) - ElectroMagnetic Compatibility (EMC) standard for radio equipment and services - Part 3: Specific conditions for Short-Range Devices (SRD) operating on frequencies between 9 khz and 40 GHz; V1.4.1 :2002 [EN 60950] EN Information technology equipment - Safety Date 2 May 2013 Page 21 of 24

22 Reference Document Ref Date / Version Document title [Env Class] EN Classification of environmental conditions Part 3: Classification of groups of environmental parameters and their severities [ENV tests] EN IEC Environmental testing Part 2 [IAP] EN EN 15509:2007 Road Traffic and Transport Telematics (RTTT) Electronic Fee Collection Interoperability application profile for DSRC [TS L2] ETSI TS V1.1.1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Road Transport and Traffic Telematics (RTTT); Test specifications for DSRC transmission equipment; Part 1: DSRC data link layer: medium access and logical link control; Sub parts 1-3 [TS L7] ETSI TS V1.1.1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Road Transport and Traffic Telematics (RTTT); Test specifications for DSRC transmission equipment; Part 2: DSRC application layer; Sub parts 1-3 [MOPTT] MOPTT V1.0:2002 Conformance tests to the specification for interoperability in the beacon transponder transaction (Public Works, Transport and Telecommunications Ministry, Chile, Version 1.0, , CEN/TC278/WG1 N677) [CARDME] CARDME 2002 CARDME-4/ D4.1 The CARDME concept (Final, 1 June 2002) [GSS] GSS V3.2:2003 Global Specification for Short Range Communication (Kapsch TrafficCom AB, Kapsch Telecom GmbH, Thales e-transactions CGA SA, version 3.2, , Date 2 May 2013 Page 22 of 24

23 Reference Document Ref Date / Version Document title [CESARE] CEASARE 2002 CEASRE II D032.1 Detailed CESARE Technical Specification Version 3, [A1] A A1 - Interoperable EFC Transaction using Central Account based on DSRC European Commission DG XIII - Telematics Applications Programme TR4001 June 12, 1999 (Version ER9_1.3) [EG2] Definition of parameters to be stored in on-board equipment designed for use with the European Electronic Toll Service - Prepared by: Expert Group 2: Vehicle Classification - Working to support the European Commission DG TREN [EG11] Definition of the EFC Application for the EETS Based on Microwave Technologies - Prepared by Expert Group 11 - Working to support the European Commission on the work on Directive 2004/52/EC [UNECE] [Reg_doc] ECONOMIC COMMISSION FOR EUROPE - INLAND TRANSPORT COMMITTEE - Working Party on the Construction of Vehicles TRANS/WP.29/78/Rev.1/Amend.2 - CONSOLIDATED RESOLUTION ON THE CONSTRUCTION OF VEHICLES (R.E.3) Directive 1999/37/EC on Registration Documents Date 2 May 2013 Page 23 of 24

24 EasyGo documents Reference Document Ref Date / Version Document title [PROCESS] 401 Business Process Definitions for EasyGo+ [OBU_req] 202-A EasyGo+: OBU Functional requirements [OBU_data] 202-B EasyGo+: OBU Data description (EasyGo+ OBU Personalization, Configuration and Operating Parameters ) [DSRC] 202-C EasyGo+: DSRC Transaction for Tolling and Enforcement 202-D EASYGO+: RSE Functional Requirements 202-E EASYGO+: OBU Compatibility Tests Date 2 May 2013 Page 24 of 24