III.

Specifications of Part I of the Registration Certificate in smart card format (Alternative to the specimen in paper format described in Chapter II) III.1 Card format and data legible with the eye Being a microprocessor card, the chip card shall be designed in accordance with the standards mentioned in Chapter III.5. The data stored on the card should be legible with normal reading devices (such as for tachograph cards). Printed on the front and back of the card shall be at least the data specified in Chapters II.4 and II.5; these data shall be legible with the eye (minimum character height: 6 points) and printed on as follows. (Examples of possible lay-outs are presented in Figure 1 at the end of this section.) A. Basic imprint The basic data shall contain the following: Front (a) To the right of the chip location: in the language(s) of the Member State issuing the Registration Certificate — the words ‘European Community’; — the name of the Member State issuing the Registration Certificate; — the words ‘Part I of the Registration Certificate’, or, if the certificate consists of one part only, the words ‘Registration Certificate’ printed in large type; — another (e.g. previous national) designation of the equivalent document (optional); — the name of the competent authority (alternatively, also in the form of a personalisation imprint as per Letter B); — the unambiguous consecutive number of the document as used within the Member State (alternatively, also in the form of a personalisation imprint as per Letter B); (b) Above the chip location: the distinguishing mark of the Member State issuing the Registration Certificate, white in a blue rectangle and surrounded by twelve yellow stars: B Belgium ▼M2 BG Bulgaria ▼M1 DK Denmark D Germany GR Greece E Spain F France ▼M3 HR Croatia ▼M1 IRL Ireland I Italy L Luxembourg NL The Netherlands A Austria P Portugal ▼M2 RO Romania ▼M1 FIN Finland S Sweden UK United Kingdom (c) Member States might consider adding, at the lower edge in small type and in their national language(s), the note: ‘This document should be produced to any authorised person requesting it.’ (d) The basic colour of the card is green (Pantone 362); alternatively, a green-to-white transition is possible. (e) A symbol representing a wheel (see proposed lay-out in Fig.1) shall be printed within the printing area in the bottom left corner of the card front. In other respects, the provisions of Chapter III.13 shall apply. B. Personalisation imprint The personalisation imprint shall contain the following information: Front (a) the name of the competent authority — see also Letter Aa) (b) the name of the authority issuing the Registration Certificate (optional) (c) the unambiguous consecutive number of the document as used within the Member State — see also Letter Aa) (d) The following data from Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised Community codes:



Code Reference (A) registration number (official licence number) (B) date of first registration of the vehicle (I) date of the registration to which this certificate refers personal data (C.1) holder of the Registration Certificate (C.1.1) surname or business name (C.1.2) other name(s) or initial(s) (where appropriate) (C.1.3) address in the Member State of registration on the date of issue of the document (C.4) Where the particulars specified in Chapter II.6, code C.2 are not included in the imprint of the Registration Certificate defined in the Letters A and B, reference to the fact that the holder of the Registration Certificate (a) is the vehicle owner; (b) is not the vehicle owner; (c) is not identified as the vehicle owner in the Registration Certificate; Back The back shall bear at least the remaining data specified in Chapter II.5; in accordance with Chapter II.7, individual national codes may be added to the preceding harmonised Community codes. In detail, these data are:



Code Reference Vehicle Data (in consideration of the notes in Chapter II.5) (D.1) make (D.2) type (variant/version, where appropriate) (D.3) commercial description(s) (E) vehicle identification number (F.1) max. technically permissible laden mass, except for motorcycles (kg) (G) mass of the vehicle in service with bodywork, and with coupling device in the case of a towing vehicle in service from any category other than M1 (kg) (H) period of validity, if not unlimited (K) type-approval number (if available) (P.1) displacement (cm3) (P.2) nominal power (kW) (P.3) type of fuel or power source (Q) power/weight ratio (in kW/kg) (only for motorcycles) (S.1) number of seats, including driver's seat (S.2) number of standing places (where appropriate) Optionally, additional data from II.6 (with the harmonised codes) and II.7 may be added on the back of the card. C. Physical security features of the smart card The threats to the physical security of documents are: — Production of false cards: creating a new object which bears great resemblance to the document, either by making it from scratch or by copying an original document. — Material alteration: changing a property of an original document, e.g. modifying some of the data printed on the document. The material used for Part I of the Registration Certificate shall be made secure against forgery by using at least three of the following techniques: — microprinting, — guilloche printing*, — iridescent printing, — laser engraving, — ultraviolet fluorescent ink, — inks with viewing angle — dependent colour*, — inks with temperature — dependent colour*, — custom holograms*, — variable laser images, — optical variable images. Member States are free to introduce additional security features. As a basis, the techniques indicated with an asterisk are to be preferred as they enable the law enforcement officers to check the validity of the card without any special means. Figure 1: Examples of possible lay-outs of the mandatory data

(more optional and additional data may be added to the back side of the card) III.2. Data storage and protection Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1: (A) Data as per Chapters II.4 and II.5 All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card. (B) Other data as per Chapter II.6 Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent. (C) Other data as per Chapter II.7 Optionally, additional information may be stored on the card. The data from the letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according to their requirements. There are no read restrictions on these files. Write access to these files shall be restricted to the national competent authorities (and their authorised agencies) in the Member State issuing the smart card. Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a security module (e.g. a security module card) of the national competent authorities (or their authorised agencies). Thereby card verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The card verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field). The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card. The specification of the files and commands needed for the authentication process and the writing process is under the responsibility of the Member States. The security assurance has to be approved by common criteria evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant. (D) Verification data for authenticity of registration data The issuing authority calculates its electronic signature about the complete data of a file containing the data of the letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data: — electronic signature of registration data related to letter A, — electronic signature of registration data related to letter B, For verification of these electronic signatures the card shall store: — certificates of the issuing authority calculating the signatures about the data of letters A, B. Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities. III.3. Interface External contacts should be used for interfacing. A combination of external contacts with a transponder is optional. III.4. Storage capacity of the card The card shall have sufficient capacity to store the data mentioned in Chapter III.2. III.5. Standards The chip card and reading devices used shall comply with the following standards: — ISO 7810: Standards for identification cards (plastic cards): Physical characteristics — ISO 7816-1 and –2: Physical characteristics of chip cards, dimensions and location of contacts — ISO 7816-3: Electrical characteristics of contacts, transmission protocols — ISO 7816-4: Communication contents, chip card data structure, safety architecture, access mechanisms — ISO 7816-5: Structure of application identifiers, selection and execution of application identifiers, registration procedure for application identifiers (numbering system) — ISO 7816-6: Inter-industry data elements for interchange — ISO 7816-8: Integrated circuit(s) cards with contacts — Security related inter-industry commands — ISO 7816-9: Integrated circuit(s) cards with contacts — Enhanced inter-industry commands III.6. Technical Characteristics and Transmission Protocols The format shall be ID-1 (normal size, see ISO/IEC 7810). The card shall support transmission protocol T=1 in compliance with ISO/IEC 7816-3. Additionally other transmission protocols may be supported, e.g. T=0, USB or contactless protocols. For bit transmission the ‘direct convention’ shall be applied (see ISO/IEC 7816-3). (A) Supply voltage, programming voltage The card shall work with Vcc = 3V (+/0.3V) or with Vcc = 5V (+/0,5V). The card shall not require a programming voltage at pin C6. (B) Answer to reset The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘80h’ (=128 bytes). (C) Protocol parameter selection The support of Protocol parameter selection (PPS) according to ISO/IEC 7816-3 is mandatory. It is used for selecting T=1, if T=0 is additionally present in the card, and to negotiate the Fi/Di parameters for achieving higher transmission rates. (D) Transmission protocol T = 1 The support of chaining is mandatory. The following simplifications are allowed: — NAD Byte: not used (NAD should be set to ‘00’), — S-Block ABORT: not used, — S-Block VPP state error: not used. The information field size device (IFSD) shall be indicated from the IFD immediately after ATR, i.e. the IFD shall transmit the S-Block IFS Request after ATR and the card shall send back S-Block IFS. The recommended value for IFSD is 254 bytes. III.7. Temperature range The registration certificate in smart card format shall properly function under all climatic conditions usually prevailing in the territories of the community and at least in the temperature range specified in ISO 7810. The cards shall be capable of operating correctly in the humidity range 10 % to 90 %. III.8. Physical lifetime If used in accordance with the environmental and electricity-related specifications, the card must function properly for a period of ten years. The material of the card must be chosen in such a way that this lifetime is ensured. III.9. Electrical characteristics During operation, the cards shall conform to Commission Directive 95/54/EC of 31 October 1995 ( 13 ), related to electromagnetic compatibility, and shall be protected against electrostatic discharges. III.10. File structure Table 1 lists the mandatory elementary files (EF) of the application DF (see ISO/IEC 7816-4) DF.Registration. All these files have a transparent structure. The access requirements are described in Chapter III.2. The file sizes are specified by the Member States according their requirements.



Table 1 Filename File Identifier Description EF.Registration_A ‘D001’ Registration data according to the Chapters II.4 and II.5 EF.Signature_A ‘E001’ Electronic Signature about complete data content of EF.Registration_A EF.C.IA_A.DS ‘C001’ X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_A EF.Registration_B ‘D011’ Registration data according Chapter II.6 EF.Signature_B ‘E011’ Electronic Signature about complete data content of EF.Registration_B EF.C.IA_B.DS ‘C011’ X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_B III.11. Data structure The stored certificates are in the X.509v3 format according ISO/IEC 9594-8. The electronic signatures are stored transparently. The registration data is stored as BER-TLV data objects (see ISO/IEC 7816-4) in the corresponding elementary files. The value fields are coded as ASCII character as defined by ISO/IEC 8824-1, the values ‘C0’-‘FF’ are defined by ISO/IEC 8859-1 (Latin1 character set), ISO/IEC 8859-7 (Greek character set) or ISO/IEC 8859-5 (Cyrillic character set). The format of dates is YYYYMMDD. Table 2 lists the Tags identifying the data objects corresponding to the registration data of the Chapters II.4 and II.5 together with additional data from Chapter III.1. Unless otherwise stated, the data objects listed in Table 2 are mandatory. Optional data objects may be omitted. The column of the Tag indicates the level of nesting.



Table 2 Tag Description ‘78’ Compatible tag allocation authority, nesting object ‘4F’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) ‘4F’ Application identifier (see ISO/IEC 7816-4) ‘71’ Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to mandatory data of the registration certificate Part 1, nesting all following objects ‘80’ Version of Tag definition ‘9F33’ Name of the Member State issuing the registration certificate Part 1 ‘9F34’ Another (e.g. previous national) designation of the equivalent document (optional) ‘9F35’ Name of the competent authority ‘9F36’ Name of the authority issuing the registration certificate (optional) ‘9F37’ Character set used: ‘00’: ISO/IEC 8859-1 (Latin1 character set) ‘01’: ISO/IEC 8859-5 (Cyrillic character set) ‘02’: ISO/IEC 8859-7 (Greek character set) ‘9F38’ Unambiguous consecutive number of the document as used within the Member State ‘81’ Registration number ‘82’ Date of first registration ‘A1’ Personal data, nesting objects ‘A2’ and ‘86’ ‘A2’ Holder of the registration certificate, nesting objects ‘83’, ‘84’ and ‘85’ ‘83’ Surname or business name ‘84’ Other names or initials (optional) ‘85’ Address in the Member State ‘86’ ‘00’: is the vehicle owner ‘01’: is not the vehicle owner ‘02’: is not identified as the vehicle owner ‘A3’ Vehicle, nesting objects ‘87’, ‘88’ and ‘89’ ‘87’ Vehicle make ‘88’ Vehicle type ‘89’ Vehicle commercial descriptions ‘8A’ Vehicle identification number ‘A4’ Mass nesting ‘8B’ ‘8B’ Mass maximum technically permissible laden mass ‘8C’ Mass of the vehicle in service with bodywork ‘8D’ Period of validity ‘8E’ Date of the registration to which this certificate refers ‘8F’ Type approval number ‘A5’ Engine, nesting objects ‘90’, ‘91’, and ‘92’ ‘90’ Engine capacity ‘91’ Engine maximum net power ‘92’ Engine type of fuel ‘93’ Power weight ratio ‘A6’ Seating capacity nesting objects ‘94’ and ‘95’ ‘94’ Number of seats ‘95’ Number of standing places Table 3 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.6. The data objects listed in Table 3 are optional.



Table 3 Tag Description ‘78’ Compatible tag allocation authority, nesting object ‘4F’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) ‘4F’ Application Identifier (see ISO/IEC 7816-4) ‘72’ Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to optional data of the registration certificate Part 1, Chapter II.6, nesting all following objects ‘80’ Version of Tag definition ‘A1’ Personal data nesting objects ‘A7’, ‘A8’ and ‘A9’ ‘A7’ Vehicle owner, nesting objects ‘83’, ‘84’ and ‘85’ .. ‘A8’ Second vehicle owner, nesting objects ‘83’, ‘84’ and ‘85’ .. ‘A9’ Person who may use the vehicle by virtue of legal right other than ownership nesting objects ‘83’, ‘84’, and ‘85’ .. ‘A4’ Mass, nesting ‘96’ and ‘97’ ‘96’ Maximum permissible laden mass of the vehicle in service ‘97’ Maximum permissible laden mass of the whole vehicle in service ‘98’ Vehicle category ‘99’ Number of axles ‘9A’ Wheelbase ‘AD’ Distribution of the maximum permissible laden mass among the axles, nesting objects ‘9F1F’, ‘9F20’, ‘9F21’, ‘9F22’ and ‘9F23’ ‘9F1F’ Axle 1 ‘9F20’ Axle 2 ‘9F21’ Axle 3 ‘9F22’ Axle 4 ‘9F23’ Axle 5 ‘AE’ Technically permissible maximum towable mass of the trailer, nesting objects ‘9B’ and ‘9C’ ‘9B’ Braked ‘9C’ Unbraked ‘A5’ Engine, nesting objects ‘9D’ and ‘9E’ ‘9D’ Rated speed ‘9E’ Engine identification number ‘9F24’ Colour of the vehicle ‘9F25’ Maximum speed ‘AF’ Sound level, nesting objects ‘DF26’, ‘DF27’ and ‘DF28’ ‘9F26’ Stationary ‘9F27’ Engine speed ‘9F28’ Drive by ‘B0’ Exhaust emissions, nesting objects ‘9F29’, ‘9F2A’, ‘9F2B’, ‘9F2C’, ‘9F2D’, ‘9F2E’, ‘9F2F’, ‘9F30’ and ‘9F31’ ‘9F29’ CO ‘9F2A’ HC ‘9F2B’ NOX ‘9F2C’ HC+NOX ‘9F2D’ Particulates of diesel ‘9F2E’ Corrected absorption coefficient for diesel ‘9F2F’ CO2 ‘9F30’ Combined fuel consumption ‘9F31’ Indication of the environmental category of EC type-approval ‘9F32’ Fuel tanks capacity Structure and format of the data according Chapter II.7 are specified by the Member States. III.12. Reading the registration data A. Application selection The application ‘Vehicle Registration’ shall be selectable by a SELECT DF (by name, see ISO/IEC 7816-4) with its application identifier (AID). The AID value is requested from a laboratory selected by the European Commission. B. Reading data from files The files corresponding to Chapter II, Letters A, B and D, shall be selectable by SELECT (see ISO/IEC 7816-4) with the command parameters P1 set to ‘02’, P2 set to ‘04’ and the command data field containing the file identifier (see Chapter X, Table 1). The returned FCP template contains the file size which can be useful for reading these files. These files shall be readable with READ BINARY (see ISO/IEC 7816-4) with an absent command data field and Le set to the length of the expected data, using a short Le. C. Verification of data authenticity To verify the authenticity of the stored registration data, the corresponding electronic signature may be verified. This means that besides the registration data also the corresponding electronic signature may be read from the registration card. The public key for signature verification can be retrieved by reading the corresponding issuing authority certificate from the registration card. Certificates contain the public key and the identity of the corresponding authority. The signature verification may be performed by another system than the registration card. The Member States are free to retrieve the public keys and certificates for verifying the issuing authority certificate. III.13. Special provisions Irrespective of the other provisions herein, the Member States, after notifying the European Commission, may add colours, marks or symbols. In addition, for certain data of Chapter III.2 Letter C, the Member States may allow XML format and may allow access via TCP/IP. Member States may, with the agreement of the European Commission, add other applications for which no harmonised rules or documents exist yet at EU level (e.g. roadworthiness certificate), on the vehicle registration card to realise additional vehicle related services.